GNOME Bugzilla – Bug 562104
crash in Document Viewer: reading web mail
Last modified: 2008-11-24 20:06:16 UTC
Version: 2.22.2 What were you doing when the application crashed? reading web mail Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Sat Oct 18 16:22:25 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 59813888 vsize: 59813888 resident: 37277696 share: 12034048 rss: 37277696 rss_rlim: 4294967295 CPU usage: start_time: 1227521375 rtime: 42 utime: 34 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evince' [Thread debugging using libthread_db enabled] [New Thread 0xb6ad7700 (LWP 20243)] [New Thread 0xb6957b90 (LWP 20244)] 0xb7f89424 in __kernel_vsyscall ()
+ Trace 210173
Thread 2 (Thread 0xb6957b90 (LWP 20244))
----------- .xsession-errors (191113 sec old) --------------------- ** (nm-applet:23072): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.597" is not allowed to own the service "org.freedesktop.Netw ** (nm-applet:23072): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.597" is not allowed to own the service "org.freedesktop.Netw ** (nm-applet:23072): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.597" is not allowed to own the service "org.freedesktop.Netw ** (nm-applet:23072): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.597" is not allowed to own the service "org.freedesktop.Netw ...Too much output, ignoring rest... --------------------------------------------------
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 555375 ***