GNOME Bugzilla – Bug 577459
crash in Deskbar: clicked on deskbar icon ...
Last modified: 2009-03-31 13:57:04 UTC
What were you doing when the application crashed? clicked on deskbar icon and search bar appeared. Ignored that and right clicked on deskbar icon again, then clicked on bottom button. Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.3 2008-07-09 (Ubuntu) BugBuddy Version: 2.22.0 System: Linux 2.6.24-23-generic #1 SMP Mon Jan 26 00:13:11 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Mac4Lin_GTK_v1.0_RC Icon Theme: Mac4Lin_Icons_v1.0_RC Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors (201 sec old) --------------------- Start IM through /home/rleung/.xinput.d/en_US linked to /etc/X11/xinit/xinput.d/scim-bridge. SESSION_MANAGER=local/rleung-laptop:/tmp/.ICE-unix/5886 Shutdown failed or nothing to shut down. xrdb: "*Label.background" on line 220 overrides entry on line 150 xrdb: "*Text.background" on line 226 overrides entry on line 191 xrdb: "*Label.foreground" on line 232 overrides entry on line 151 xrdb: "*Text.foreground" on line 238 overrides entry on line 192 Window manager warning: Failed to read saved session file /home/rleung/.metacity/sessions/default0.ms: Failed to open file '/home/rleung/.metacity/sessions/default0.ms': No such file or directory Connection failure: Connection refused Initializing nautilus-share extension seahorse nautilus module initialized ** (nautilus:6063): WARNING **: Unable to add monitor: Not supported PID TTY TIME CMD PID TTY TIME CMD -------------------------------------------------- Traceback (most recent call last):
+ Trace 214045
self.module_list.move_module_to_bottom(iter)
self.move_after(iter, self.get_iter(self._bottom_enabled_path))
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 488665 ***