Bug 218251 - click email or folder - kmail becomes unstable
Summary: click email or folder - kmail becomes unstable
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-11 10:32 UTC by dave
Modified: 2009-12-15 11:37 UTC (History)
1 user (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 dave 2009-12-11 10:32:40 UTC
Application that crashed: kmail
Version of the application: 1.12.4
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-16-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
Was creating a new email.
had taken @ 6 snapshots of my screen - various changes - to send to a friend.
I had just completed it all (think i was also d/ling updates too) when i got a signal 11 initially i reloaded kmail and when i clicked on a email it fell over again.

seems stable enough until i - move folders or click on an email


 -- Backtrace:
Application: KMail (kmail), signal: Aborted
[KCrash Handler]
#6  0x00a0a422 in __kernel_vsyscall ()
#7  0x090fd4d1 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0x09100932 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0x009744df in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6
#10 0x00972415 in ?? () from /usr/lib/libstdc++.so.6
#11 0x00972452 in std::terminate() () from /usr/lib/libstdc++.so.6
#12 0x0097250b in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#13 0x06f685e1 in QMetaObject::activate (sender=0xa8a2018, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3123
#14 0x06f68ec2 in QMetaObject::activate (sender=0xa8a2018, m=0x7042908, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#15 0x06f6d387 in QSingleShotTimer::timeout (this=0xa8a2018) at .moc/release-shared/qtimer.moc:76
#16 0x06f6d49c in QSingleShotTimer::timerEvent (this=0xa8a2018) at kernel/qtimer.cpp:298
#17 0x06f623bf in QObject::event (this=0xa8a2018, e=0xbfc69e30) at kernel/qobject.cpp:1075
#18 0x030a8f54 in QApplicationPrivate::notify_helper (this=0x9e2ea00, receiver=0xa8a2018, e=0xbfc69e30) at kernel/qapplication.cpp:4056
#19 0x030b067c in QApplication::notify (this=0xbfc6a230, receiver=0xa8a2018, e=0xbfc69e30) at kernel/qapplication.cpp:3603
#20 0x005df1aa in KApplication::notify (this=0xbfc6a230, receiver=0xa8a2018, event=0xbfc69e30) at ../../kdeui/kernel/kapplication.cpp:302
#21 0x06f526cb in QCoreApplication::notifyInternal (this=0xbfc6a230, receiver=0xa8a2018, event=0xbfc69e30) at kernel/qcoreapplication.cpp:610
#22 0x06f7f7ce in QCoreApplication::sendEvent (this=0x9e04844) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#23 QTimerInfoList::activateTimers (this=0x9e04844) at kernel/qeventdispatcher_unix.cpp:572
#24 0x06f7d0e0 in timerSourceDispatch (source=0x9e04810) at kernel/qeventdispatcher_glib.cpp:165
#25 0x01a03e78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#26 0x01a07720 in ?? () from /lib/libglib-2.0.so.0
#27 0x01a07853 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#28 0x06f7d02c in QEventDispatcherGlib::processEvents (this=0x9dd3180, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#29 0x03149be5 in QGuiEventDispatcherGlib::processEvents (this=0x9dd3180, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#30 0x06f50c79 in QEventLoop::processEvents (this=0xbfc6a0f4, flags=) at kernel/qeventloop.cpp:149
#31 0x06f510ca in QEventLoop::exec (this=0xbfc6a0f4, flags=...) at kernel/qeventloop.cpp:201
#32 0x06f5353f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#33 0x030a8dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#34 0x0804a702 in _start ()

Reported using DrKonqi
Comment 1 Björn Ruberg 2009-12-13 00:19:25 UTC
Can you give as a step-by-step guide to reproduce your crash?
Comment 2 dave 2009-12-13 06:30:38 UTC
Originally (prior to the crashing all the time)....
was sending 6 screen shots via email to a friend.
clicked send and got a signal 6 error for Kmail. didn't have any debug
libraries installed at that time.

Now as soon as i click on a message (be it opened or unopened) it gets to
the point of rendering the message text and suddenly crashes.
I have just started it now and include the crash info below

 Application: KMail (kmail), signal: Aborted

[KCrash Handler]

#6 0x009f4422 in __kernel_vsyscall ()

#7 0x011ca4d1 in raise () from /lib/tls/i686/cmov/libc.so.6

#8 0x011cd932 in abort () from /lib/tls/i686/cmov/libc.so.6

#9 0x009994df in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib/libstdc++.so.6

#10 0x00997415 in ?? () from /usr/lib/libstdc++.so.6

#11 0x00997452 in std::terminate() () from /usr/lib/libstdc++.so.6

#12 0x0099750b in __cxa_rethrow () from /usr/lib/libstdc++.so.6

#13 0x086a25e1 in QMetaObject::activate (sender=0xa89bfe0,
from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3123

#14 0x086a2ec2 in QMetaObject::activate (sender=0xa89bfe0, m=0x877c908,
local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187

#15 0x086a7387 in QSingleShotTimer::timeout (this=0xa89bfe0) at
.moc/release-shared/qtimer.moc:76

#16 0x086a749c in QSingleShotTimer::timerEvent (this=0xa89bfe0) at
kernel/qtimer.cpp:298

#17 0x0869c3bf in QObject::event (this=0xa89bfe0, e=0xbfd4c890) at
kernel/qobject.cpp:1075

#18 0x05ea3f54 in QApplicationPrivate::notify_helper (this=0x9e23ed8,
receiver=0xa89bfe0, e=0xbfd4c890) at kernel/qapplication.cpp:4056

#19 0x05eab67c in QApplication::notify (this=0xbfd4cc90, receiver=0xa89bfe0,
e=0xbfd4c890) at kernel/qapplication.cpp:3603

#20 0x002e31aa in KApplication::notify (this=0xbfd4cc90, receiver=0xa89bfe0,
event=0xbfd4c890) at ../../kdeui/kernel/kapplication.cpp:302

#21 0x0868c6cb in QCoreApplication::notifyInternal (this=0xbfd4cc90,
receiver=0xa89bfe0, event=0xbfd4c890) at kernel/qcoreapplication.cpp:610

#22 0x086b97ce in QCoreApplication::sendEvent (this=0x9df0e34) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213

#23 QTimerInfoList::activateTimers (this=0x9df0e34) at
kernel/qeventdispatcher_unix.cpp:572

#24 0x086b70e0 in timerSourceDispatch (source=0x9df0e00) at
kernel/qeventdispatcher_glib.cpp:165

#25 0x01797e78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0

#26 0x0179b720 in ?? () from /lib/libglib-2.0.so.0

#27 0x0179b853 in g_main_context_iteration () from /lib/libglib-2.0.so.0

#28 0x086b702c in QEventDispatcherGlib::processEvents (this=0x9dc8180,
flags=...) at kernel/qeventdispatcher_glib.cpp:327

#29 0x05f44be5 in QGuiEventDispatcherGlib::processEvents (this=0x9dc8180,
flags=...) at kernel/qguieventdispatcher_glib.cpp:202

#30 0x0868ac79 in QEventLoop::processEvents (this=0xbfd4cb54, flags=) at
kernel/qeventloop.cpp:149

#31 0x0868b0ca in QEventLoop::exec (this=0xbfd4cb54, flags=...) at
kernel/qeventloop.cpp:201

#32 0x0868d53f in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:888

#33 0x05ea3dd7 in QApplication::exec () at kernel/qapplication.cpp:3525

#34 0x0804a702 in _start ()


crash tonight at 6:28pm sunday 13th Dec 2009.

Note i thought for what ever reason it might've been an indexing issue and
have since (from initial failure to just before posting the original bug)
recreated the indexes for all directories regardless of how many emails
where in them - to no avail.

dave.

ps can do a screencast to show you the fault it you REALLY want :)

2009/12/13 Björn Ruberg <bjoern@ruberg-wegener.de>

> https://bugs.kde.org/show_bug.cgi?id=218251
>
>
> Björn Ruberg <bjoern@ruberg-wegener.de> changed:
>
>           What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                 CC|                            |bjoern@ruberg-wegener.de
>
>
>
>
> --- Comment #1 from Björn Ruberg <bjoern ruberg-wegener de>  2009-12-13
> 00:19:25 ---
> Can you give as a step-by-step guide to reproduce your crash?
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
Comment 3 Björn Ruberg 2009-12-13 10:51:35 UTC
So you are saying that kmail always crahs now when you want to use it?
Comment 4 dave 2009-12-13 19:15:35 UTC
As of Thursday 17th dec 2009 yes.

it seems stable enough doing anything BUT clicking on a message.

IE i can click on menus and (e.g. File move up and down the list slide
across to the next one etc etc). But as soon as i click on a message Bang it
crashes.
I was updating my system when the initial crash happened so i'm wondering if
i should uninstall Kmail and then reinstall it.

At work at present so tonight i'll test what've said about roaming around
the menus and their lists tonight and report back if I am wrong.

rgds,

2009/12/13 Björn Ruberg <bjoern@ruberg-wegener.de>

> https://bugs.kde.org/show_bug.cgi?id=218251
>
>
>
>
>
> --- Comment #3 from Björn Ruberg <bjoern ruberg-wegener de>  2009-12-13
> 10:51:35 ---
> So you are saying that kmail always crahs now when you want to use it?
>
> --
>  Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>
Comment 5 dave 2009-12-15 08:08:57 UTC
I am not entirely sure what the hell has happened!!!!

My wife has informed me that she tried loaded Kcontact and all of a sudden
kmail started to download emails etc. She was able to send off some emails
also.

So my question here is this....

if you have Kmail running and then run Kcontact would this somehow create a
conflict that would cause Kmail to fall over when it is run as an
independent program?

I have kmail loaded and running 99% of the time and also have a short cut on
the desktop so when or if Kmail falls over the user "just clicks" on the
icon to get Kmail back up.

When i started my desktop up again tonight i had Kcontact & Kmail on the
ribbon bar and when I closed Kcontact Kmail did not fall over as it has in
the recent 4 or so days.

Because of this I would like to ask for this bug to be closed, Unless i have
hit upon a flaw in how Kcontact runs with Kmail when Kmail is running and
then Kcontact is started.

many thanks for the reply Bjorn.

Dave.

2009/12/14 Björn Ruberg <bjoern@ruberg-wegener.de>

> https://bugs.kde.org/show_bug.cgi?id=218251
>
>
> Björn Ruberg <bjoern@ruberg-wegener.de> changed:
>
>           What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>             Status|UNCONFIRMED                 |NEW
>     Ever Confirmed|0                           |1
>
>
>
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>