After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 450205 - crash in Take Screenshot: screenshot (beryl)
crash in Take Screenshot: screenshot (beryl)
Status: RESOLVED DUPLICATE of bug 449959
Product: gnome-utils
Classification: Deprecated
Component: screenshot
unspecified
Other All
: High critical
: ---
Assigned To: Jonathan Blandford
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-22 21:34 UTC by yiorgos
Modified: 2007-06-22 22:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description yiorgos 2007-06-22 21:34:48 UTC
What were you doing when the application crashed?
screenshot (beryl)


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 26492928 vsize: 26492928 resident: 9474048 share: 5566464 rss: 9474048 rss_rlim: 4294967295
CPU usage: start_time: 1182548024 rtime: 5 utime: 3 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208330528 (LWP 9583)]
(no debugging symbols found)
0x005dd402 in __kernel_vsyscall ()

Thread 1 (Thread -1208330528 (LWP 9583))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 screenshot_get_pixbuf
  • #5 _start
  • #0 __kernel_vsyscall


----------- .xsession-errors (127 sec old) ---------------------
  Major opcode:  2
  Minor opcode:  0
  Resource id:  0x3201018
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  2
  Minor opcode:  0
  Resource id:  0x320103c
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x28000a1
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x28000a1
--------------------------------------------------
Comment 1 Susana 2007-06-22 22:24:35 UTC
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 449959 ***