FS#39262 - [rednotebook] Segfault in libQtCore.so.4.8.5
Attached to Project:
Arch Linux
Opened by Dan Liew (delcypher) - Monday, 10 March 2014, 11:40 GMT
Last edited by Andrea Scarpino (BaSh) - Tuesday, 18 March 2014, 11:14 GMT
Opened by Dan Liew (delcypher) - Monday, 10 March 2014, 11:40 GMT
Last edited by Andrea Scarpino (BaSh) - Tuesday, 18 March 2014, 11:14 GMT
|
Details
Description:
I use an application called Rednotebook (AUR: https://aur.archlinux.org/packages/rednotebook/ ) and I've noticed that it has started triggering a segfault in libQtCore.so which is weird because Rednotebook is written in Python and AFAIK uses GTK not Qt. Additional info: * qt4 4.8.5-7 * rednotebook 1.8.0-1 (AUR) * KDE 4.12.3 * I'm using kde-gtk-config to control GTK appearance is KDE Steps to reproduce: 1. Install build and install rednotebook package from AUR 2. Run rednotebook from your terminal 3. The rednotebook GUI will appear, exit the usual way by clicking the [X] in the window 4. On exit the rednotebook process SEGFAULTS in libQtCore.so.4.8.5 (output from dmesg) [ 219.442756] rednotebook[1634]: segfault at 0 ip 00007f2857306f74 sp 00007fff2f25eee0 error 4 in libQtCore.so.4.8.5[7f28571e2000+2d5000] Apologies if this is not the right place to report this. I tried downgrading the qt4 package and unfortunately that didn't fixing anything but the segfault is happening in libQtCore according to the output of dmesg. Based on looking at the output of strace the last thing that happens before segfaulting is stat("/usr/lib/kde4/plugins", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 I've attached the whole output of running $ rednotebook 2>&1 | tee rednotebook-segfault.txt Any guidance on how to debug this would be helpful? Should I rebuild libQtCore.so with debug symbols and then attach to the python process and hope that that will catch the segfault? 
rednotebook-segfault.txt
(1.56 MiB)
|
This task depends upon
Closed by Andrea Scarpino (BaSh)
Tuesday, 18 March 2014, 11:14 GMT
Reason for closing: Upstream
Additional comments about closing: rednotebook is not supported
Tuesday, 18 March 2014, 11:14 GMT
Reason for closing: Upstream
Additional comments about closing: rednotebook is not supported
s/attach to the python process/attach gdb to the python process/
I removed qt4 and ran rednotebook and no segfault. I then reinstalled qt4 and tried rednotebook and as before it is segfaulting in rednotebook when I exit.
I've just noticed however that if I strip out a particular environment variable then the segfault does not happen, i.e.
```
$ env --unset=KDE_FULL_SESSION rednotebook
```
When I use my normal environment (contains KDE_FULL_SESSION=true) then when I run rednotebook from the command line it segfaults in libQtCore on exit.