Bug 48000 - KMail crashes when i use the shotcuts to mark message as read
Summary: KMail crashes when i use the shotcuts to mark message as read
Status: RESOLVED FIXED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.4.7
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Ellis Whitehead
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-09-18 08:29 UTC by pch
Modified: 2002-09-22 21:18 UTC (History)
0 users

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 pch 2002-09-18 08:29:14 UTC
Version:           1.4.7 (using KDE 3.0.7 (KDE 3.1 beta2))
Installed from:    compiled sources
Compiler:          gcc version 2.95.4 20011002 (Debian prerelease)
OS:          Linux (i686) release 2.4.17

I assigned KP_Subtract to "Mark Message as Read". if i use it kmail crashes
nothing happen if i use the popup menu.
Comment 1 Ingo Klöcker 2002-09-18 18:47:48 UTC
Please provide the backtrace you get after the crash. If you didn't configure 
KMail with --enable-debug=full then please do so and recompile KMail. Else the 
backtrace won't be useful. 
 
Comment 2 pch 2002-09-19 15:49:07 UTC
Subject: Re:  KMail crashes when i use the shotcuts to mark message
 as read       

[New Thread 1024 (LWP 10316)]
0x415daa39 in wait4 () from /lib/libc.so.6
#0  0x415daa39 in wait4 () from /lib/libc.so.6
#1  0x41651e48 in __check_rhosts_file () from /lib/libc.so.6
#2  0x4146d453 in waitpid () from /lib/libpthread.so.0
#3  0x40bbd253 in KCrash::defaultCrashHandler (sig=11) at kcrash.cpp:235
#4  0x4146af54 in pthread_sighandler () from /lib/libpthread.so.0
#5  0x415636b8 in sigaction () from /lib/libc.so.6
#6  0x40ba5dab in KShortcut::contains (this=0xc, seq=@0xbfffeb44)
    at kshortcut.cpp:542
#7  0x40ba5c4d in KShortcut::contains (this=0xc, key=@0xbfffebd8)
    at kshortcut.cpp:526
#8  0x40bb1300 in KAccelPrivate::slotKeyPressed (this=0x839a3c0, id=-82)
    at kaccel.cpp:181
#9  0x40bb2e30 in KAccelPrivate::qt_invoke (this=0x839a3c0, _id=2,
    _o=0xbfffecc0) at kaccelprivate.moc:113
#10 0x40f1bf52 in QObject::activate_signal (this=0x83a61c8,
clist=0x8399710,
    o=0xbfffecc0) at kernel/qobject.cpp:2080
#11 0x40f1c122 in QObject::activate_signal (this=0x83a61c8, signal=2,
    param=-82) at kernel/qobject.cpp:2130
#12 0x411e850a in QAccel::activated (this=0x83a61c8, t0=-82)
    at .moc/debug-mt/moc_qaccel.cpp:84
#13 0x40eb9615 in QAccel::eventFilter (this=0x83a61c8, o=0x8248f20,
    e=0xbffff0e4) at kernel/qaccel.cpp:535
#14 0x40f19c38 in QObject::activate_filters (this=0x8248f20, e=0xbffff0e4)
    at kernel/qobject.cpp:779
#15 0x40f19a6d in QObject::event (this=0x8248f20, e=0xbffff0e4)
    at kernel/qobject.cpp:655
#16 0x40f4f685 in QWidget::event (this=0x8248f20, e=0xbffff0e4)
    at kernel/qwidget.cpp:4122
#17 0x40ffbdb4 in QMainWindow::event (this=0x8248f20, e=0xbffff0e4)
    at widgets/qmainwindow.cpp:1604
#18 0x40ebd9f8 in QApplication::internalNotify (this=0xbffff5c0,
    receiver=0x8248f20, e=0xbffff0e4) at kernel/qapplication.cpp:2306
#19 0x40ebd6d8 in QApplication::notify (this=0xbffff5c0,
receiver=0x8248f20,
    e=0xbffff0e4) at kernel/qapplication.cpp:2254
#20 0x40b46903 in KApplication::notify (this=0xbffff5c0,
receiver=0x8248f20,
    event=0xbffff0e4) at kapplication.cpp:421
#21 0x411e90c4 in QApplication::sendSpontaneousEvent (receiver=0x8248f20,
    event=0xbffff0e4) at .moc/debug-mt/../../kernel/qapplication.h:455
#22 0x40e5d483 in QETWidget::translateKeyEvent (this=0x82feea0,
    event=0xbffff38c, grab=false) at kernel/qapplication_x11.cpp:5625
#23 0x40e586ab in QApplication::x11ProcessEvent (this=0xbffff5c0,
    event=0xbffff38c) at kernel/qapplication_x11.cpp:3670
#24 0x40e571e9 in QApplication::processNextEvent (this=0xbffff5c0,
    canWait=true) at kernel/qapplication_x11.cpp:3168
#25 0x40ebf5bf in QApplication::enter_loop (this=0xbffff5c0)
    at kernel/qapplication.cpp:3180
#26 0x40e570e3 in QApplication::exec (this=0xbffff5c0)
    at kernel/qapplication_x11.cpp:3123
#27 0x081b9622 in main (argc=7, argv=0xbffff744) at main.cpp:341

On 18 Sep 2002, Ingo Kl
Comment 3 Ingo Klöcker 2002-09-21 18:31:13 UTC
Subject: Re:  KMail crashes when i use the shotcuts to mark message as read

On Thursday 19 September 2002 15:49, pch@freeshell.org wrote:
> #6  0x40ba5dab in KShortcut::contains (this=0xc, seq=@0xbfffeb44)
>     at kshortcut.cpp:542
> #7  0x40ba5c4d in KShortcut::contains (this=0xc, key=@0xbfffebd8)
>     at kshortcut.cpp:526
> #8  0x40bb1300 in KAccelPrivate::slotKeyPressed (this=0x839a3c0,
> id=-82) at kaccel.cpp:181

Looks like a bug in KAccel. But when I try to reproduce this I get the 
message "Ambiguous '-' not handled" when I press KP_Subtract. The 
reason for this is that both minus keys are bound to "previous unread 
message". But the shortcut config dialog doesn't seem to know this when 
you bind KP_Subtract to another action.

Is your kdelibs up-to-date? If not, please update to the current cvs 
version and try if you can still reproduce the problem.

Regards,
Ingo

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9jIPNGnR+RTDgudgRAr1qAJ0ZbCkx/TTocos3wURIdM3DT7gnmwCfTnGH
pFWsUVOVH8G+06VDlZDR9xg=
=yLW+
-----END PGP SIGNATURE-----

Comment 4 pch 2002-09-22 10:36:11 UTC
Subject: Re:  KMail crashes when i use the shotcuts to mark message
 as read         

Hi Ingo,
apparently no way i tried with the lastest kdelibs
but the crash is still present with KB_SUBSTRACT
(it crash also if i bind crtl+KB_SUBSTRACT for mark all as read)
peraphs it work for example with F2
Patrick
On 21 Sep 2002, Ingo Kl
Comment 5 Ellis Whitehead 2002-09-22 21:18:46 UTC
QAccel can't handle KP_Subtract.  I've committed changes to kdelibs which 
prevent assigning such keys to application shortcuts now.   
 
However, if there are crashes still occuring on key conflict, that problem will 
continue to exist (I couldn't reproduce it).