https://qa.mandrakesoft.com/show_bug.cgi?id=957
Product: gnome2
Component: gnome2
Summary: Object activation failing
Version: 2.1.90-1mdk
Platform: PC
OS/Version: All
Status: UNCONFIRMED
Severity: critical
Priority: P2
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
Frequently (about 95% of the time), whenever I log into my Gnome2 desktop, I get
a "Settings daemon started too many times" message, and also significant
components of the desktop itself (applets, various other embedded
objects--including the Nautilus sidebars, and the GTK HTML composer window for
Evolution) simply do not function. The desktop functions, but has lost a great
deal of its usability.
My applets generate a dialog complaining about an unknown exception id (sorry, I
don't have details in front of me right now--I'll add them when I get back
home), and asking if I want to delete it from the session.
Based on observed behavior, I am suspecting that glibc is somehow at fault (I've
seen other applications, notably gst-register, complain about structure
mismatches); however, this is purely guesswork, as I do not yet know how to
trace errors like this through a debugger (a skill I fully intend to obtain).
I am, as of now, running the latest Cooker release (pulled from the Cooker
archive, not the beta1 or beta2 ISO images), on a Pentium 233 MMX with 256MB. I
attempted to fix this by restoring a standard 9.0 build, replacing everything
but my /home partitions, and then reinstalling the latest updated packages from
Cooker (as of approx. a week ago). This did not fix the problem, which leads me
to believe that there is an error in a package somewhere.
One reason I suspect that glibc may be the culprit is that my system was working
perfectly before (approx.) December 26, 2002--the same day that glibc was
originally installed (glibc-2.3.1-6mdk); of course, this is not proof, but it is
a coincidence.
I also attempted to rebuild glibc from the source package, and the build failed
with an Illegal Instruction error while in build-i686-...
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
