GNOME Bugzilla – Bug 445394
crash in Text Editor: Clicked "print"
Last modified: 2007-06-10 19:41:51 UTC
Version: 2.18.0 What were you doing when the application crashed? Clicked "print" Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 364638208 vsize: 364638208 resident: 21745664 share: 12836864 rss: 21745664 rss_rlim: 18446744073709551615 CPU usage: start_time: 1181286543 rtime: 126 utime: 116 stime: 10 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gedit' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496411552 (LWP 6868)] (no debugging symbols found) 0x0000003b89a0d89f in waitpid () from /lib64/libpthread.so.0
+ Trace 139288
Thread 1 (Thread 46912496411552 (LWP 6868))
No plugin installed in $HOME. ----------- .xsession-errors (21 sec old) --------------------- (evolution:31800): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:31800): camel-WARNING **: camel_exception_get_id called with NULL parameter. camel-Message: -- camel-Message: -- camel-Message: -- camel-Message: -- camel-Message: -- camel-Message: -- Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x5c03298 (OpenOffice) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. (evolution:31800): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1 (evolution:31800): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1 Writing new pickle set PageSize = Letter --------------------------------------------------
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 437238 ***