gnome-screenshot crashed with SIGSEGV in XInternAtom()

Bug #349520 reported by nakki
8
Affects Status Importance Assigned to Milestone
at-spi (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gnome-utils

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gnome-screenshot
Package: gnome-utils 2.26.0-0ubuntu1
ProcCmdline: gnome-screenshot --window
ProcEnviron:
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-utils
StacktraceTop:
 XInternAtom () from /usr/lib/libX11.so.6
 ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so
 ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so
 ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: gnome-screenshot crashed with SIGSEGV in XInternAtom()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
nakki (titibanjekistan) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:XInternAtom (dpy=0x0, name=0xb711f19e "AT_SPI_IOR", onlyIfExists=0)
spi_atk_bridge_get_registry () at bridge.c:391
spi_atk_bridge_do_registration () at bridge.c:276
atk_bridge_init (argc=0xb7f87418, argv=0xb7f8741c)
default_display_notify_cb (display_manager=0x9133590)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in gnome-utils:
importance: Undecided → Medium
visibility: private → public
affects: gnome-utils (Ubuntu) → at-spi (Ubuntu)
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu development version (10.04). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 349520.

Also, could you give us the steps to reproduce this issue, please?

Changed in at-spi (Ubuntu):
status: New → Incomplete
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
nakki (titibanjekistan) wrote :

Sorry but i don't remember...the bug was found by apport in the 9.04 aplhaX and i don't know how to reproduce it and if it is solved now...sorry for my english and i reported a very recent bug:
https://bugs.launchpad.net/ubuntu/+bug/579839

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in at-spi (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.