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 701033 - at-spi2-registryd crashes with SIGSEGV
at-spi2-registryd crashes with SIGSEGV
Status: RESOLVED FIXED
Product: at-spi
Classification: Platform
Component: at-spi2-core
unspecified
Other Linux
: Normal normal
: ---
Assigned To: At-spi maintainer(s)
At-spi maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-05-26 09:52 UTC by Michael Mess
Modified: 2014-09-01 15:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Michael Mess 2013-05-26 09:52:02 UTC 
See Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1173033

Dependencies:
coreutils 8.13-3ubuntu3.2
debconf 1.5.42ubuntu1
dpkg 1.16.1.2ubuntu7.1
gcc-4.6-base 4.6.3-1ubuntu5
libacl1 2.2.51-5ubuntu1
libatspi2.0-0 2.4.2-0ubuntu0.1
libattr1 1:2.4.46-5ubuntu1
libbz2-1.0 1.0.6-1
libc-bin 2.15-0ubuntu10.4
libc6 2.15-0ubuntu10.4
libdbus-1-3 1.4.18-1ubuntu1.3
libffi6 3.0.11~rc1-5
libgcc1 1:4.6.3-1ubuntu5
libglib2.0-0 2.32.3-0ubuntu1
liblzma5 5.1.1alpha+20110809-3
libpcre3 8.12-4
libselinux1 2.1.0-4.1ubuntu1
libtinfo5 5.9-4
libx11-6 2:1.4.99.1-0ubuntu2
libx11-data 2:1.4.99.1-0ubuntu2
libxau6 1:1.0.6-4
libxcb1 1.8.1-1ubuntu0.1
libxdmcp6 1:1.1.0-4
libxext6 2:1.3.0-3build1
libxtst6 2:1.2.0-4
lsb-base 4.0-0ubuntu20.2
multiarch-support 2.15-0ubuntu10.4
ncurses-bin 5.9-4
perl-base 5.14.2-6ubuntu2.3
sed 4.2.1-9
tar 1.26-4ubuntu1
tzdata 2012e-0ubuntu0.12.04.1
x11-common 1:7.6+12ubuntu2
xz-utils 5.1.1alpha+20110809-3
zlib1g 1:1.2.3.4.dfsg-3ubuntu4
Comment 1 André Klapper 2013-08-14 10:08:42 UTC 
[Mass-resetting default assignee, see bug 705890. Please reclaim this bug report by setting the assignee to yourself if you still plan to work on this. Thanks!]
Comment 2 Patrick Welche 2014-09-01 15:40:25 UTC 
The ubuntu bug suggests that the problem has been fixed. (So closing this bug - feel free to reopen if this is still an issue.)