GTK segfault

Added by Audacious User2 over 10 years ago

Here's one more vote that you should switch to Qt. Every time I find a gtk theme I like, a gtk upgrade breaks it. Now, I can't even run audacious. It seems to be the only program affected and I tried different gtk themes. No dice...

If you need more info or want me to file a formal bug report, let me know.

Debian sid x86-64
gtk 3.12.0
Audacious 3.6 from git (updated today)

Program received signal SIGSEGV, Segmentation fault.
0x00007fffeeba1449 in gtk_style_context_get_background_color (context=context@entry=0xc85100, state=state@entry=GTK_STATE_FLAG_DIR_LTR, color=color@entry=0x7fffffffde30)
at /tmp/buildd/gtk+3.0-3.12.0/./gtk/gtkstylecontext.c:3427
3427 /tmp/buildd/gtk+3.0-3.12.0/./gtk/gtkstylecontext.c: No such file or directory.
(gdb) bt
#0 0x00007fffeeba1449 in gtk_style_context_get_background_color (context=context@entry=0xc85100, state=state@entry=GTK_STATE_FLAG_DIR_LTR, color=color@entry=0x7fffffffde30)
at /tmp/buildd/gtk+3.0-3.12.0/./gtk/gtkstylecontext.c:3427
#1 0x00007fffeebd5526 in gtk_text_view_set_attributes_from_style (text_view=text_view@entry=0xc762d0, values=values@entry=0x64a0e0)
at /tmp/buildd/gtk+3.0-3.12.0/./gtk/gtktextview.c:7193
#2 0x00007fffeebd9db0 in gtk_text_view_ensure_layout (text_view=text_view@entry=0xc762d0) at /tmp/buildd/gtk+3.0-3.12.0/./gtk/gtktextview.c:7303
#3 0x00007fffeebd9f78 in gtk_text_view_set_vadjustment_values (text_view=text_view@entry=0xc762d0) at /tmp/buildd/gtk+3.0-3.12.0/./gtk/gtktextview.c:8092
#4 0x00007fffeebe35c3 in gtk_text_view_set_vadjustment (adjustment=0xc7dd70, text_view=0xc762d0) at /tmp/buildd/gtk+3.0-3.12.0/./gtk/gtktextview.c:8032
#5 gtk_text_view_set_property (object=0xc762d0, prop_id=<optimized out>, value=<optimized out>, pspec=<optimized out>) at /tmp/buildd/gtk+3.0-3.12.0/./gtk/gtktextview.c:3345
#6 0x00007ffff73dc789 in object_set_property (nqueue=0x8ec230, value=<optimized out>, pspec=0xc6d020, object=0xc762d0) at /tmp/buildd/glib2.0-2.40.0/./gobject/gobject.c:1378
#7 g_object_new_internal (class=class@entry=0xc6dc20, params=params@entry=0x0, n_params=n_params@entry=0) at /tmp/buildd/glib2.0-2.40.0/./gobject/gobject.c:1757
#8 0x00007ffff73de10d in g_object_newv (object_type=object_type@entry=11874816, n_parameters=n_parameters@entry=0, parameters=parameters@entry=0x0)
at /tmp/buildd/glib2.0-2.40.0/./gobject/gobject.c:1868
#9 0x00007ffff73de8bc in g_object_new (object_type=11874816, first_property_name=first_property_name@entry=0x0) at /tmp/buildd/glib2.0-2.40.0/./gobject/gobject.c:1568
#10 0x00007fffeebd8099 in gtk_text_view_new () at /tmp/buildd/gtk+3.0-3.12.0/./gtk/gtktextview.c:1593
#11 0x00007fffd7e41e4b in build_widget () at lyricwiki.c:293
#12 0x00007fffd7e42563 in init () at lyricwiki.c:376
#13 0x00007ffff7bc4b49 in general_plugin_start (plugin=<optimized out>) at plugin-init.c:40
#14 0x00007ffff7bc4c89 in start_multi_cb (p=0x6649e0, type=0x6) at plugin-init.c:134
#15 0x00007ffff7bc6c27 in aud_plugin_for_each (type=type@entry=6, func=func@entry=0x7ffff7bc6310 <plugin_for_enabled_cb>, data=data@entry=0x7fffffffe280) at plugin-registry.c:670
#16 0x00007ffff7bc6d1c in aud_plugin_for_enabled (type=type@entry=6, func=func@entry=0x7ffff7bc4c60 <start_multi_cb>, data=data@entry=0x6) at plugin-registry.c:734
#17 0x00007ffff7bc4d8d in start_plugins (type=<optimized out>) at plugin-init.c:154
#18 0x00007ffff7bc500e in start_plugins_two () at plugin-init.c:180
#19 0x00007ffff7bc8306 in aud_run () at runtime.c:317
#20 0x0000000000404c54 in main (argc=<optimized out>, argv=<optimized out>) at main.c:381

Replies (8)

RE: GTK segfault - Added by John Lindgren over 10 years ago

Did the crash clearly start with the GTK+ 3.12 update -- that is, you can make it go away by downgrading to 3.10.x? If that's the case, then opening a report on bugzilla.gnome.org would be the thing to do.

RE: GTK segfault - Added by Audacious User2 over 10 years ago

I can't remember when it started. Probably about last Friday, April 14, and gtk 3.12.x had been in sid for about a week or two before that (so it's possible that the gtk upgrade broke it. It could have also been this commit: https://github.com/audacious-media-player/audacious/commit/5fd4cb76c66e341ac2f39f35c38b97c1a3cb3c78

I'm not really in the mood to bisect since Clementine and gmusicbrowser work fairly well for me. Downgrading a major foundational package in Debian sid sounds like a recipe for disaster (and it's far more time/effort than I'm willing to put into it since I seem to be the only one experiencing the issue).

I'm just curious why Audacious is the only program I'm running that has issues (and why I get the error even when running audacious with headless switch).
Usually, when I upgrade GTK and theming breaks, I have other programs segfaulting (Synaptic comes to mind).

Thanks anyway. Maybe other Debian users (especially the maintainers) will hit this bug and have a better idea what it is.

RE: GTK segfault - Added by John Lindgren over 10 years ago

LyricWiki shouldn't be doing anything with GTK+ in headless mode, so that is probably the cause. Anyway, if you don't want to deal with bugs, you should be using the stable version, not compiling from Git.

RE: GTK segfault - Added by Audacious User2 over 10 years ago

Yes, something appears to be awry with lyricwiki. I disabled it and audacious started. I enabled the lyricwiki plugin again, but it "fails to parse" whatever I throw at it. Tried different combinations of transport plugins, but the only difference is that disabling neon transport changes error to "failed to fetch".

RE: GTK segfault - Added by Audacious User2 over 10 years ago

Lyricwiki seems to be fetching okay now. I do have to close it manually before closing audacious or it will segfault on the next start.

If anyone else is having the issue, you can disable lyricwiki by editing ~/.config/audacious/plugin-registry and changing "enabled=0" under the section for lyricwiki.