You are not logged in.
Today it seems all gtk2 applications fail to start and just say: "segmentation fault (core dumped)"
doing some debugging the issues seem to be with libgdk-x11-2.0.so.0.2400.31
Everything seemed to be working fine yesterday. Here are the packages that have been updated since then:
upgraded python2-acme (0.9.0-1 -> 0.9.1-1)]
upgraded certbot (0.9.0-1 -> 0.9.1-1)
upgraded certbot-apache (0.9.0-1 -> 0.9.1-1)
upgraded certbot-nginx (0.9.0-1 -> 0.9.1-1)
upgraded texinfo (6.1-4 -> 6.3-1)
upgraded weechat (1.5-2 -> 1.6-1)
upgraded wine (1.9.19-1 -> 1.9.20-1)
upgraded youtube-dl (2016.10.02-1 -> 2016.10.07-1)
upgraded conky (1.10.4-1 -> 1.10.5-1)
upgraded wpa_supplicant (1:2.5-3 -> 1:2.6-1)
...nothing seems significant. any ideas would be appreciated, thanks
Offline
I have a similar problem. Try downgrading libxi to 1.7.6 https://archive.archlinux.org/packages/ … pkg.tar.xz
Last edited by Waldteufel (2016-10-09 15:20:05)
Offline
after having some time to do some more debugging, I've isolated the issue to having an xbox 360 controller plugged in. When I remove the controller, things work fine. As soon as I plug in the controller, gtk2 applications segfault. If I remove the controller, no segfault and things work again.
here's an example stack trace from gdb:
#0 0x00007ffff78898ce in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#1 0x00007ffff7864f28 in gdk_display_open () from /usr/lib/libgdk-x11-2.0.so.0
#2 0x00007ffff7834732 in gdk_display_open_default_libgtk_only ()
from /usr/lib/libgdk-x11-2.0.so.0
#3 0x00007ffff2176275 in gtk_init () from /usr/lib/libgtk-x11-2.0.so.0
#4 0x00007ffff7228f28 in Gtk::Main::init(int*, char***, bool) ()
from /usr/lib/libgtkmm-2.4.so.1
#5 0x00007ffff7228f8f in Gtk::Main::Main(int&, char**&, bool) ()
from /usr/lib/libgtkmm-2.4.so.1
#6 0x0000000000412231 in ?? ()
#7 0x00007ffff50c3291 in __libc_start_main () from /usr/lib/libc.so.6
#8 0x0000000000413e69 in ?? ()
xbox controller is using the xpad driver. This is on a dell xps 13 9343
Offline
yeah, downgrading libxi seems to fix the issue
Offline
Then it's certainly the same issue. In my case the offending device was the touchscreen, so blacklisting the 'wacom' module provided a temporary workaround.
Thanks for opening the bug report.
Offline