GNOME Bugzilla – Bug 562105
crash in Document Viewer:
Last modified: 2008-11-24 20:06:15 UTC
Version: 2.22.2 What were you doing when the application crashed? 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: 59822080 vsize: 59822080 resident: 37412864 share: 12083200 rss: 37412864 rss_rlim: 4294967295 CPU usage: start_time: 1227521866 rtime: 44 utime: 36 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 0xb6b2d700 (LWP 20288)] [New Thread 0xb69adb90 (LWP 20289)] 0xb7fdf424 in __kernel_vsyscall ()
+ Trace 210174
Thread 2 (Thread 0xb69adb90 (LWP 20289))
----------- .xsession-errors (191603 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 ***