GNOME Bugzilla – Bug 449959
crash in Take Screenshot: Screenshot of Acrobat
Last modified: 2008-03-23 23:38:34 UTC
What were you doing when the application crashed? Screenshot of Acrobat Distribution: Slackware Slackware 11.0.0 Gnome Release: 2.18.1 2007-05-10 (Dropline GNOME) BugBuddy Version: 2.18.1 System: Linux 2.6.18.1 #4 SMP PREEMPT Thu Oct 26 11:38:19 MDT 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 60900000 Selinux: No Accessibility: Disabled GTK+ Theme: Simple Icon Theme: gnome Memory status: size: 40542208 vsize: 40542208 resident: 17186816 share: 8720384 rss: 17186816 rss_rlim: 4294967295 CPU usage: start_time: 1182491169 rtime: 16 utime: 14 stime: 2 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-screenshot' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225681216 (LWP 14503)] (no debugging symbols found) 0xb79d704e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 142817
Thread 1 (Thread -1225681216 (LWP 14503))
----------- .xsession-errors (304267099 sec old) --------------------- X connection to :0.0 broken (explicit kill or server shutdown). ICE default IO error handler doing an exit(), pid = 656, errno = 0 X connection to :0.0 broken (explicit kill or server shutdown). xterm: fatal IO error 2 (Broken pipe) or KillClient on X server ":0.0" --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
*** Bug 450205 has been marked as a duplicate of this bug. ***
*** Bug 461137 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** Bug 462612 has been marked as a duplicate of this bug. ***
*** Bug 463785 has been marked as a duplicate of this bug. ***
*** Bug 488101 has been marked as a duplicate of this bug. ***
*** Bug 487052 has been marked as a duplicate of this bug. ***
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
*** Bug 502948 has been marked as a duplicate of this bug. ***
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 bug has been marked as a duplicate of 383623 ***