GNOME Bugzilla – Bug 548781
crash in Deskbar: nothing
Last modified: 2008-08-21 13:17:42 UTC
What were you doing when the application crashed? nothing Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.3 2008-07-09 (Ubuntu) BugBuddy Version: 2.22.0 System: Linux 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Raptor (4e copie) Icon Theme: nuoveXT.2.2 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 --------------------- This program is free software and comes without any warranty. It is licensed under version 2 or later of the General Public License which can be viewed at http://www.gnu.org/licenses/gpl.txt Initialising tracker... Could not set idle IO priority...attempting best effort 7 priority starting HAL detection for ac adaptors...11 found /org/freedesktop/Hal/devices/computer_power_supply_ac_adapter_ACAD Throttle level is 10 Window manager warning: Could not open session file '/home/kevin/.metacity/sessions/1100000840000121929527500000172900002.ms' for writing: Permission denied ** (nautilus:17376): WARNING **: Unable to add monitor: Not supported ERROR: execution of prepared query SetOption failed due to unable to open database file with return code 14 ** (trackerd:17423): WARNING **: could not open /home/kevin/.local/share/tracker/tracker.log -------------------------------------------------- Traceback (most recent call last):
+ Trace 205472
tray = DeskbarTray(applet)
self.__setup_mvc()
self.__core.run()
self._setup_keybinder()
self.set_keybinding( self.get_keybinding() )
self._gconf.set_keybinding(binding)
self._client.set_string(self.GCONF_KEYBINDING, binding)
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 486549 ***