GNOME Bugzilla – Bug 453943
crash in Panel: logging in
Last modified: 2007-07-05 17:07:10 UTC
Version: 2.18.2 What were you doing when the application crashed? logging in Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 35966976 vsize: 35966976 resident: 19038208 share: 16084992 rss: 19038208 rss_rlim: 4294967295 CPU usage: start_time: 1183641634 rtime: 28 utime: 24 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208731936 (LWP 3409)] (no debugging symbols found) 0x005c1402 in __kernel_vsyscall ()
+ Trace 145886
Thread 1 (Thread -1208731936 (LWP 3409))
----------- .xsession-errors --------------------- localuser:baron being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/3386 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name (gnome-panel:3409): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 446183 ***
Not clear what other report you mean, or what questions. This was reported by an automatic bug reporting tool. All I did was to approve the report. And the only symptom of the "crash" that I noticed was that I got the popup window asking if I wanted to report the bug, and all I said was "yes" and that I was logging in. After I sent the report, the login completed with no problems. (Some of the items on the panel seem to have moved, but I'm not sure.) This is all I know.
(In reply to comment #2) > Not clear what other report you mean, or what questions. The other bug report is bug 446183. To sum up a bit the issue: this is a but that is happening to a lot of people, but the developers can't reproduce it and need a bit more information. We've asked a few questions in bug 446183 to help us solve the issue.
(In reply to comment #3) > (In reply to comment #2) > > Not clear what other report you mean, or what questions. > > The other bug report is bug 446183. To sum up a bit the issue: this is a but > that is happening to a lot of people, but the developers can't reproduce it and > need a bit more information. We've asked a few questions in bug 446183 to help > us solve the issue. Sorry but I can't find the questions. I also cannot reproduce the bug. I've logged in several times and it happened only once. Perhaps one other piece of information is that I did quite a bit of reconfiguration of the panel. I removed the bottom panel and put the other one vertically on the left side and made it much thicker. (Screen is a weird shape.) Also, this computer is now being used by someone else, for a couple of months, so I won't be able to do any further testing.
(In reply to comment #4) > Also, this computer is now being used by someone else, for a couple of months, > so I won't be able to do any further testing. No problem, and thanks for your help!