lxappearance-obconf plugin causes lxappearance 0.6.1-1 to segfault
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxappearance (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
lxappearance-obconf (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I just don't understand it.
Towards 0.2.2-1, lxappearance-obconf plugin 0.2.2-2 only seems to have undergone a cosmetical change (i. e. information update).
But lxappearance 0.6.1-1 works perfectly with 0.2.2-1 here on Wily.
(Using Openbox 3.5.2-8.)
However lxappearance 0.6.1-1 with plugin version 0.2.2-2 makes it crash!
So if you can reproduce the crash, LEAVE lxappearance at its latest version and only do a minimal downgrade of lxappearance-
gdb
...
Reading symbols from lxappearance...(no debugging symbols found)...done.
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) run
Starting program: /usr/bin/
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-
Program received signal SIGSEGV, Segmentation fault.
0xb6927f65 in preview_theme () from /usr/lib/
(gdb) bt full
#0 0xb6927f65 in preview_theme () from /usr/lib/
No symbol table info available.
#1 0xb692878e in preview_update_all () from /usr/lib/
No symbol table info available.
#2 0xb6928f71 in theme_load_all () from /usr/lib/
No symbol table info available.
#3 0xb6926b78 in plugin_load () from /usr/lib/
No symbol table info available.
#4 0x0804f270 in plugins_init ()
No symbol table info available.
#5 0x0804ba78 in main ()
No symbol table info available.
Related branches
summary: |
- lxappearance-obconf plugin causes lxappearance 0.6.1.-1 to segfault + lxappearance-obconf plugin causes lxappearance 0.6.1-1 to segfault |
description: | updated |
SUCCESS!
Managed to "fix" it myself.
However, I had to install openbox 3.6.0 first (yet marked unstable) and the new dependencies (since lxappearance-obconf 0.2.2.3) libobrender31 and libobt4.
Works now, but should not be closed, as openbox 3.6.0 is still a little "futuristic" ;)