After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 549071 - crash in Deskbar: opening firefox
crash in Deskbar: opening firefox
Status: RESOLVED DUPLICATE of bug 486549
Product: deskbar-applet
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Deskbar Applet Maintainer(s)
Deskbar Applet Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-08-22 23:41 UTC by skopp888
Modified: 2008-11-13 14:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description skopp888 2008-08-22 23:41:03 UTC 
What were you doing when the application crashed?
opening firefox


Distribution: Ubuntu 8.04 (hardy)
Gnome Release: 2.22.3 2008-07-09 (Ubuntu)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-21-generic #1 SMP Tue Aug 12 13:37:22 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: kde4-oxygen
Icon Theme: Slick

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 (51 sec old) ---------------------
XIO:  fatal IO error 0 (Success) on X server ":0.0"
      after 12 requests (12 known processed) with 0 events remaining.
The application 'nautilus' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
gnome-terminal: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
gnome-screensaver: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
bluetooth-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
tracker-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
search: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
applet.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
evolution-alarm-notify: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
--------------------------------------------------
Traceback (most recent call last):

+ Trace 205555

  • File "/usr/lib/deskbar-applet/deskbar-applet", line 30 in applet_factory 
    tray = DeskbarTray(applet)
  • File "/usr/lib/python2.5/site-packages/deskbar/ui/DeskbarTray.py", line 47 in __init__ 
    self.__setup_mvc()
  • File "/usr/lib/python2.5/site-packages/deskbar/ui/DeskbarTray.py", line 88 in __setup_mvc 
    self.__core.run()
  • File "/usr/lib/python2.5/site-packages/deskbar/core/CoreImpl.py", line 54 in run 
    self._setup_keybinder()
  • File "/usr/lib/python2.5/site-packages/deskbar/core/CoreImpl.py", line 75 in _setup_keybinder 
    self.set_keybinding( self.get_keybinding() )
  • File "/usr/lib/python2.5/site-packages/deskbar/core/CoreImpl.py", line 167 in set_keybinding 
    self._gconf.set_keybinding(binding)
  • File "/usr/lib/python2.5/site-packages/deskbar/core/GconfStore.py", line 178 in set_keybinding 
    self._client.set_string(self.GCONF_KEYBINDING, binding)
GError: Can't overwrite existing read-only value: Can't overwrite existing read-only value: Value for `/apps/deskbar/keybinding' set in a read-only source at the front of your configuration path 






Comment 1


palfrey





          2008-11-13 14:05:03 UTC
        



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 ***