Bug 191707 - Kmail crash after mouse click close to window edge
Summary: Kmail crash after mouse click close to window edge
Status: RESOLVED NOT A BUG
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-05 18:08 UTC by giacof
Modified: 2010-09-19 21:03 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description giacof 2009-05-05 18:08:53 UTC
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Ubuntu Packages

I wasn't doing anything special: just reading a message, then I clicked somewhere within the Kmail window (if I remember well it was near the window border) and it crashed. Here is the trace:

Applicazione: Kontact (kontact), segnale SIGABRT
[Current thread is 0 (LWP 5344)]

Thread 4 (Thread 0xac7f1b90 (LWP 7170)):
#0  0xb8065430 in __kernel_vsyscall ()
#1  0xb59c07b1 in select () from /lib/tls/i686/cmov/libc.so.6
#2  0xb5c94380 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb5bc296e in ?? () from /usr/lib/libQtCore.so.4
#4  0xb51b94ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5  0xb59c849e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 3 (Thread 0xabdffb90 (LWP 7882)):
#0  0xb8065430 in __kernel_vsyscall ()
#1  0xb59d7643 in ?? () from /lib/tls/i686/cmov/libc.so.6
#2  0xb5958f5d in ?? () from /lib/tls/i686/cmov/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 2 (Thread 0xab13eb90 (LWP 7910)):
[KCrash Handler]
#6  0xb8065430 in __kernel_vsyscall ()
#7  0xb590f6d0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb5911098 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb594d24d in ?? () from /lib/tls/i686/cmov/libc.so.6
#10 0xb5953604 in ?? () from /lib/tls/i686/cmov/libc.so.6
#11 0xb59565b6 in ?? () from /lib/tls/i686/cmov/libc.so.6
#12 0xb59579c5 in malloc () from /lib/tls/i686/cmov/libc.so.6
#13 0xb5bbd0bd in qMalloc () from /usr/lib/libQtCore.so.4
#14 0xb5bc6525 in QByteArray::QByteArray () from /usr/lib/libQtCore.so.4
#15 0xb5bba0e1 in qgetenv () from /usr/lib/libQtCore.so.4
#16 0xb5f7ec39 in ?? () from /usr/lib/libkdecore.so.5
#17 0xb5f7ef78 in ?? () from /usr/lib/libkdecore.so.5
#18 0xb5f93908 in ?? () from /usr/lib/libkdecore.so.5
#19 0xb5f93c15 in KLocale::translateQt () from /usr/lib/libkdecore.so.5
#20 0xb6db1e60 in ?? () from /usr/lib/libkdeui.so.5
#21 0xb5cd43d1 in QTranslator::translate () from /usr/lib/libQtCore.so.4
#22 0xb5cba2ea in QCoreApplication::translate () from /usr/lib/libQtCore.so.4
#23 0xb5cba736 in QCoreApplication::translate () from /usr/lib/libQtCore.so.4
#24 0xb5cbd752 in QMetaObject::tr () from /usr/lib/libQtCore.so.4
#25 0xb6b053b6 in ?? () from /usr/lib/libQtNetwork.so.4
#26 0xb6afb263 in QHostInfo::fromName () from /usr/lib/libQtNetwork.so.4
#27 0xb70e4c4d in ?? () from /usr/lib/libkio.so.5
#28 0xb70e5b61 in ?? () from /usr/lib/libkio.so.5
#29 0xb5bb8dd4 in ?? () from /usr/lib/libQtCore.so.4
#30 0xb5bc296e in ?? () from /usr/lib/libQtCore.so.4
#31 0xb51b94ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#32 0xb59c849e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb48d3700 (LWP 5344)):
#0  0xb8065430 in __kernel_vsyscall ()
#1  0xb59d7643 in ?? () from /lib/tls/i686/cmov/libc.so.6
#2  0xb5958f5d in ?? () from /lib/tls/i686/cmov/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Comment 1 Dario Andres 2009-05-08 15:02:39 UTC
What is your Qt4 version ?
Thanks
Comment 2 giacof 2009-05-14 12:56:38 UTC
$apt-cache policy libqt4-core
libqt4-core:
  Installato: 4.5.0-0ubuntu4.1
  Candidato: 4.5.0-0ubuntu4.1
  Tabella versione:
 *** 4.5.0-0ubuntu4.1 0
        500 http://it.archive.ubuntu.com jaunty-updates/main Packages
        100 /var/lib/dpkg/status
     4.5.0-0ubuntu4 0
        500 http://it.archive.ubuntu.com jaunty/main Packages

Hope this helps, thank you!
Comment 3 Pino Toscano 2009-05-18 23:40:49 UTC
This looks like the same problem of bug #191122. Waiting for a better backtrace.
Comment 4 Dario Andres 2009-06-26 16:11:33 UTC
giacof: are you still getting this issue? Thanks
Comment 5 Dario Andres 2009-07-15 02:04:36 UTC
Marking as WAITINGFORINFO
Comment 6 Christophe Marin 2010-09-19 21:03:27 UTC
No feedback. Closing.