Summary: | kde-base/kmail-4.10.2 stuck on startup | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Fabio Coatti <fabio.coatti> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | ago |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugs.kde.org/show_bug.cgi?id=318093 | ||
Whiteboard: | tracking upstream | ||
Package list: | Runtime testing required: | --- |
Description
Fabio Coatti
2013-04-08 09:30:54 UTC
Could you try with a sane CFLAGS environment? Already done, with "-march=native -mtune=native -O2 -pipe" that worked for every version of kmail so far. Same result: two kmail process but nothing shows up 6183 ? S 0:00 /usr/bin/kmail -caption KMail 6184 ? Rl 1:12 /usr/bin/kmail -caption KMail Please submit a bug at bugs.kde.org and link to it here; I fear there is not much that we can do. The problem turned out to be a clash with glibc. I moved from glibc 2.16 to 2.17 and this broke in some way qtwebkit, used by many apps. Here the gdb thread status: The problem turned out to be a clash with glibc. I moved from glibc 2.16 to 2.17 and this broke in some way qtwebkit, used by many apps. Here the gdb thread status: Id Target Id Frame 3 Thread 0x7f909cd1a700 (LWP 9511) "kmail" 0x00007f90b63efcfc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 2 Thread 0x7f909c519700 (LWP 9512) "QThread" 0x00007f90b85e369d in poll () from /lib64/libc.so.6 * 1 Thread 0x7f90bb273780 (LWP 5766) "kmail" 0x00007f90ab78a1b9 in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 recompiling qtwebkit solved the issue |