Bug#540624: Segmentation fault with synaptic

thebickhams

unread,

Aug 19, 2009, 6:20:11 AM8/19/09

to

apt-cache policy synaptic
synaptic:
Installed: 0.62.7+b1
Candidate: 0.62.7+b1
Version table:
*** 0.62.7+b1 0
500 http://ftp.de.debian.org sid/main Packages
100 /var/lib/dpkg/status
0.62.7 0
500 http://ftp.de.debian.org testing/main Packages

I have the segmentation error. The report below occurs when I type p+h
to take me to phonon. No susch problem with s + y to take me to
synaptic. Sometimes scrolling causes the same problem.

usr/sbin/synaptic

(synaptic:4423): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display:
assertion `atom != GDK_NONE' failed

Regards,

D R Bickham

--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Michael Vogt

unread,

Aug 19, 2009, 9:10:11 AM8/19/09

to

On Wed, Aug 19, 2009 at 11:08:51AM +0100, thebickhams wrote:
> apt-cache policy synaptic
> synaptic:
> Installed: 0.62.7+b1
> Candidate: 0.62.7+b1
> Version table:
> *** 0.62.7+b1 0
> 500 http://ftp.de.debian.org sid/main Packages
> 100 /var/lib/dpkg/status
> 0.62.7 0
> 500 http://ftp.de.debian.org testing/main Packages
>
> I have the segmentation error. The report below occurs when I type p+h
> to take me to phonon. No susch problem with s + y to take me to
> synaptic. Sometimes scrolling causes the same problem.
>
> usr/sbin/synaptic
>
> (synaptic:4423): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display:
> assertion `atom != GDK_NONE' failed
>
> (synaptic:4423): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display:
> assertion `atom != GDK_NONE' failed
>
> (synaptic:4423): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display:
> assertion `atom != GDK_NONE' failed

I just looked at this and it does not look as if synaptic is doing
something wrong here, I suspect there is something strange in
libgtk. BTW, what G_DEBUG environment do you use? For me it just
crashes when I set "G_DEBUG=fatal_criticals".

Cheers,
Michael

Mark Petersen

unread,

Aug 20, 2009, 11:30:23 AM8/20/09

to

This bug is a duplicate of bug 540004. I am the 540004 bug reporter. You may merge it with this bug.

The seg fault problem started with the upgrade from 0.62.7 to 0.62.7+b1.

Mark