GNOME Bugzilla – Bug 647376
crash in Document Viewer: application close
Last modified: 2011-04-11 00:32:32 UTC
Version: 2.32.0 What were you doing when the application crashed? application close Distribution: Gentoo Base System release 2.0.2 Gnome Release: 2.32.1 2011-03-19 (Gentoo) BugBuddy Version: 2.32.0 System: Linux 2.6.38-gentoo-r1 #1 SMP Tue Mar 29 00:46:45 EEST 2011 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 11000902 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome GTK+ Modules: gnomesegvhandler, canberra-gtk-module Memory status: size: 577581056 vsize: 577581056 resident: 87953408 share: 20340736 rss: 87953408 rss_rlim: 18446744073709551615 CPU usage: start_time: 1302464733 rtime: 588 utime: 447 stime: 141 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 0x7f4aad80d700 (LWP 11119)] [New Thread 0x7f4aa385b700 (LWP 25578)] [New Thread 0x7f4aae80f700 (LWP 25571)] 0x00007f4ab8a1e08d in waitpid () from /lib64/libpthread.so.0
+ Trace 226676
Thread 1 (Thread 0x7f4abba55940 (LWP 25569))
A debugging session is active. Inferior 1 [process 25569] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (24 sec old) --------------------- Warning: QWidget::insertAction: Attempt to insert null action Warning: QSystemTrayIcon::setVisible: No Icon set Warning: QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.111' Object::connect: No such signal QDBusAbstractInterface::StateChanged(uint) kbuildsycoca4 running... Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3000009 specified for 0x3000f01 (Scan resul). (nautilus:3318): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion `format != NULL' failed ktorrent is already running ! unnamed app(26030): Communication problem with "ktorrent" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the FatalAssert(ę) FatalAssert(ę) kbuildsycoca4 running... --------------------------------------------------
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 bug 638312 ***