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 492291 - crash in Deskbar: ligar um pc em rede wind...
crash in Deskbar: ligar um pc em rede wind...
Status: RESOLVED DUPLICATE of bug 478758
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: 2007-11-01 08:38 UTC by barcellagiuseppe
Modified: 2007-11-01 14:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description barcellagiuseppe 2007-11-01 08:38:13 UTC 
What were you doing when the application crashed?
ligar um pc em rede windows xp		


Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.20.0 2007-09-17 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Human
Icon Theme: Human

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 (142 sec old) ---------------------
** (update-notifier:5651): WARNING **: no cdrom: disk
cairo context error: out of memory
** (update-notifier:5651): WARNING **: no cdrom: disk
(trackerd:5660): GLib-CRITICAL **: g_hash_table_insert: assertion `hash_table->ref_count > 0' failed
(trackerd:5660): GLib-CRITICAL **: g_hash_table_insert: assertion `hash_table->ref_count > 0' failed
** (nautilus:5552): CRITICAL **: dbus_g_proxy_cancel_call: assertion `pending != NULL' failed
--------------------------------------------------
Traceback (most recent call last):

+ Trace 174310

  • File "/var/lib/python-support/python2.5/dbus/connection.py", line 562 in msg_reply_handler 
    *message.get_args_list()))
  • File "/var/lib/python-support/python2.5/dbus/proxies.py", line 401 in _introspect_error_handler 
    self._introspect_execute_queue()
  • File "/var/lib/python-support/python2.5/dbus/proxies.py", line 373 in _introspect_execute_queue 
    proxy_method(*args, **keywords)
  • File "/var/lib/python-support/python2.5/dbus/proxies.py", line 127 in __call__ 
    **keywords)
  • File "/var/lib/python-support/python2.5/dbus/connection.py", line 568 in call_async 
    require_main_loop=require_main_loop) MemoryError






Comment 1


Christoph Wolk





          2007-11-01 14:47:06 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

This problem is probably caused by D-Bus not running, you should be able to fix it by logging out, then in again.

*** This bug has been marked as a duplicate of 478758 ***