[kmail2] [Bug 481135] New: Closing KMail window with system tray icon enabled doesn't always close the window
https://bugs.kde.org/show_bug.cgi?id=481135 Bug ID: 481135 Summary: Closing KMail window with system tray icon enabled doesn't always close the window Classification: Applications Product: kmail2 Version: 5.240.95 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: stefano.cro...@alice.it Target Milestone: --- SUMMARY In KF5, when the system tray icon is enabled in KMail, closing the window with Alt+F4 or with the X button on the title bar used to close the window, leaving only the system tray icon. However, with KF6 version of KMail, this only happens a few times (often only once) after the application has been launched. After that, closing the window minimizes it instead, leaving it on the task bar. When this starts to happen, there's no way to restore the correct behaviour except quitting KMail altogether (using the File/Quit menu entry). This doesn't seem to happen if closing the window by clicking on the KMail icon in the system tray. When the behaviour described above starts happening, clicking on the KMail icon in the system tray shows the window again, but it forget its maximized state. This doesn't happen when restoring it by clicking on the corresponding entry in the task. STEPS TO REPRODUCE 1. Launch KMail and ensure that the "enable system tray icon" option is checked 2. Close the KMail window using the X button on the title bar or the Alt+F4 shortcut. It may be necessary to display the window and repeat this a couple of times to trigger the bug OBSERVED RESULT KMail window is minimized and still visible in the task bar. When clicking on the system tray icon to show it again, the window is not maximized, even if it was maximized when I closed it EXPECTED RESULT KMail window gets closed and it disappear from the task bar. When clicking on its system tray icon, KMail window is restored keeping the previous maximized state. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION Gentoo doesn't provide official packages for the KF6 version of KDE Gear, so I installed them using the Gentoo KDE overlay -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 412629] Akonadi refuses to start after upgrade to PostgreSQL 12: column "version" of relation "schemaversiontable" already exists
https://bugs.kde.org/show_bug.cgi?id=412629 Stefano Crocco changed: What|Removed |Added CC||stefano.cro...@alice.it -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278446] New: Random KMail crash when downloading mail
https://bugs.kde.org/show_bug.cgi?id=278446 Summary: Random KMail crash when downloading mail Product: kmail2 Version: unspecified Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: stefano.cro...@alice.it Application: kmail (2.1.96) KDE Platform Version: 4.6.95 (4.7 RC2) Qt Version: 4.7.3 Operating System: Linux 2.6.39-gentoo-r1 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: KMail was sitting in system tray and automatically downloading mail from a POP account when it suddenly crashed The crash can be reproduced some of the time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0x7fea0c6af760 (LWP 2953))] Thread 2 (Thread 0x7fe9f4ac3700 (LWP 3277)): #0 0x7fea077ef49c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe9fe6444bd in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x7fe9fe6445b9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x7fea077eabda in start_thread () from /lib64/libpthread.so.0 #4 0x7fea0996f0bd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fea0c6af760 (LWP 2953)): [KCrash Handler] #6 operator!= (this=0x5dbf868, kiddo=value optimized out) at /usr/include/qt4/QtCore/qbasicatomic.h:75 #7 detach (this=0x5dbf868, kiddo=value optimized out) at /usr/include/qt4/QtCore/qmap.h:202 #8 remove (this=0x5dbf868, kiddo=value optimized out) at /usr/include/qt4/QtCore/qmap.h:660 #9 KPIM::ProgressItem::removeChild (this=0x5dbf868, kiddo=value optimized out) at /var/tmp/paludis/kde-base-kdepim-common-libs-4.6.95/work/kdepim-common-libs-4.6.95/libkdepim/progressmanager.cpp:72 #10 0x7fea037fe08f in KPIM::ProgressItem::setComplete (this=0x5d58800) at /var/tmp/paludis/kde-base-kdepim-common-libs-4.6.95/work/kdepim-common-libs-4.6.95/libkdepim/progressmanager.cpp:57 #11 0x7fea037ff97b in KPIM::AgentProgressMonitor::Private::instanceStatusChanged (this=0x5e25440, instance=...) at /var/tmp/paludis/kde-base-kdepim-common-libs-4.6.95/work/kdepim-common-libs-4.6.95/libkdepim/agentprogressmonitor.cpp:87 #12 0x7fea037ffbaa in KPIM::AgentProgressMonitor::qt_metacall (this=0x1d5b7d0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff50202af0) at /var/tmp/paludis/kde-base-kdepim-common-libs-4.6.95/work/kdepim-common-libs-4.6.95_build/libkdepim/agentprogressmonitor.moc:78 #13 0x7fea0a2c964f in QMetaObject::activate (sender=0xc58a80, m=value optimized out, local_signal_index=value optimized out, argv=0x1) at kernel/qobject.cpp:3278 #14 0x7fea05dae905 in Akonadi::AgentManager::instanceStatusChanged (this=0xb20020, _t1=value optimized out) at /var/tmp/paludis/kde-base-kdepimlibs-4.6.95/work/kdepimlibs-4.6.95_build/akonadi/agentmanager.moc:177 #15 0x7fea05db4700 in Akonadi::AgentManagerPrivate::agentInstanceStatusChanged (this=0x9cfc60, identifier=value optimized out, status=0, msg=...) at /var/tmp/paludis/kde-base-kdepimlibs-4.6.95/work/kdepimlibs-4.6.95/akonadi/agentmanager.cpp:129 #16 0x7fea05db4ee6 in Akonadi::AgentManager::qt_metacall (this=0xc58a80, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff50202ca0) at /var/tmp/paludis/kde-base-kdepimlibs-4.6.95/work/kdepimlibs-4.6.95_build/akonadi/agentmanager.moc:131 #17 0x7fea0a2c964f in QMetaObject::activate (sender=0xc662a0, m=value optimized out, local_signal_index=value optimized out, argv=0x1) at kernel/qobject.cpp:3278 #18 0x7fea05ec35bb in OrgFreedesktopAkonadiAgentManagerInterface::agentInstanceStatusChanged (this=0xb20020, _t1=value optimized out, _t2=0, _t3=value optimized out) at /var/tmp/paludis/kde-base-kdepimlibs-4.6.95/work/kdepimlibs-4.6.95_build/akonadi/agentmanagerinterface.moc:285 #19 0x7fea05ec3b8f in OrgFreedesktopAkonadiAgentManagerInterface::qt_metacall (this=0xc662a0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff502033e0) at /var/tmp/paludis/kde-base-kdepimlibs-4.6.95/work/kdepimlibs-4.6.95_build/akonadi/agentmanagerinterface.moc:167 #20 0x7fea07a26879 in QDBusConnectionPrivate::deliverCall (this=value optimized out, object=value optimized out, msg=value optimized out, metaTypes=..., slotIdx=value optimized out) at qdbusintegrator.cpp:941 #21 0x7fea07a3063f in QDBusCallDeliveryEvent::placeMetaCall (this=0x7fea000a, object=0x20) at qdbusintegrator_p.h:103 #22 0x7fea0a2c389e in QObject::event (this=0xc662a0, e=0xb20020) at kernel/qobject.cpp:1217 #23 0x7fea0a7aa69c in QApplicationPrivate::notify_helper (this=0xae5ba0, receiver=0xc662a0, e=0x5935ff0) at kernel/qapplication.cpp:4462 #24 0x7fea0a7afa3d in QApplication::notify
[Bug 277454] New: new messages in ignored thread sometimes not marked as ignored
https://bugs.kde.org/show_bug.cgi?id=277454 Summary: new messages in ignored thread sometimes not marked as ignored Product: kmail2 Version: 2.0.95 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: stefano.cro...@alice.it Version: 2.0.95 OS:Linux If there's a thread marked as ignored, when I download new mail, any new messages belonging to it should be marked as ignored as well. Usually this happens. Sometimes, however, the new messages, while being correctly inserted in the thread, are not marked as ignored. When this happens, the thread seems to loose its ignored status, since any message later added to it aren't marked as ignored. When this happens, I have to toggle the ignored status on the thread twice to get it back to the current status: the first time, the thread becomes not ignored, the second time it becomes correctly ignored again Reproducible: Sometimes Steps to Reproduce: Mark a thread as ignored, then download new mail containing messages which belong to the ignored thread Actual Results: Sometimes, the new messages in the thread are not marked as ignored Expected Results: The new messages in the thread should be marked as ignored -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 273949] Akonadi Resource always seen as readonly
https://bugs.kde.org/show_bug.cgi?id=273949 Stefano Crocco stefano.cro...@alice.it changed: What|Removed |Added CC||stefano.cro...@alice.it --- Comment #1 from Stefano Crocco stefano crocco alice it 2011-06-20 17:47:31 --- The same is happening to me with a resource of type VCard directory. I'm using KDE 4.7 beta 1 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 257977] New: messages in threads marked as ignored are treated as unread
https://bugs.kde.org/show_bug.cgi?id=257977 Summary: messages in threads marked as ignored are treated as unread Product: kmail2 Version: 2.0.89 Platform: Gentoo Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: stefano.cro...@alice.it Version: 2.0.89 OS:Linux If there's a thread containing more than one message, and some of them are unread, marking the whole thread as ignored doesn't make the unread messages read like it did in KMail 1. Now the unread messsages in the ignored thread are listed in the unread column in the folder list and in the message list even when the filter is set to Unread. If I select the messages in the message list after marking the thread as ignored seems to correctly mark them as read, but as soon as the folder is synced again (which happens the next time mail is checked) they're again marked as unread. The same happens using the Mark all mail as read or Mark thread as read menu entries Reproducible: Always OS: Linux (i686) release 2.6.36-gentoo Compiler: i686-pc-linux-gnu-gcc -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 187593] Pressing ESC while fetching mail causes a crash
https://bugs.kde.org/show_bug.cgi?id=187593 Stefano Crocco stefano.cro...@alice.it changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||FIXED --- Comment #3 from Stefano Crocco stefano crocco alice it 2009-07-17 17:13:19 --- The crash has disappeared some time ago. Sorry for not closing this bug sooner. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 187593] New: Pressing ESC while fetching mail causes a crash
https://bugs.kde.org/show_bug.cgi?id=187593 Summary: Pressing ESC while fetching mail causes a crash Product: kmail Version: 1.11.90 Platform: unspecified OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: stefano.cro...@alice.it Version: 1.11.90 (using 4.2.67 (KDE 4.2.67 (KDE 4.3 = 20090318)), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS:Linux (i686) release 2.6.28-gentoo-r3 While fetching message, if I press Esc to stop the operation, KMail crashes. Using the button near the progress bar to do the same, instead, works. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 187593] Pressing ESC while fetching mail causes a crash
https://bugs.kde.org/show_bug.cgi?id=187593
--- Comment #1 from Stefano Crocco stefano crocco alice it 2009-03-19
13:11:14 ---
Here's the backtrace for the crash:
Application: KMail (kmail), signal SIGSEGV
Thread 1 (Thread 0xb44b2700 (LWP 2757)):
[KCrash Handler]
#6 0xb72aafab in KPIM::ProgressItem::cancel (this=0x2f86c381) at
/var/tmp/paludis/kde-base-libkdepim-scm/work/libkdepim/libkdepim/progressmanager.cpp:83
#7 0xb72ab360 in KPIM::ProgressManager::slotAbortAll (this=0x868bb90) at
/var/tmp/paludis/kde-base-libkdepim-scm/work/libkdepim/libkdepim/progressmanager.cpp:240
#8 0xb72ab45e in KPIM::ProgressManager::qt_metacall (this=0x868bb90,
_c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbf81297c)
at
/var/tmp/paludis/kde-base-libkdepim-scm/work/libkdepim_build/libkdepim/progressmanager.moc:219
#9 0xb65e49c1 in QMetaObject::activate (sender=0x868b7a8,
from_signal_index=value optimized out, to_signal_index=6, argv=0xbf81297c) at
kernel/qobject.cpp:3057
#10 0xb65e4cd0 in QMetaObject::activate (sender=0x868b7a8, m=0xb635c208,
from_local_signal_index=1, to_local_signal_index=2, argv=0xbf81297c) at
kernel/qobject.cpp:3154
#11 0xb5cd7393 in QAction::triggered (this=0x868b7a8, _t1=false) at
.moc/release-shared/moc_qaction.cpp:236
#12 0xb5cd8492 in QAction::activate (this=0x868b7a8, event=QAction::Trigger) at
kernel/qaction.cpp:1160
#13 0xb5cda533 in QAction::event (this=0x868b7a8, e=0xbf812d84) at
kernel/qaction.cpp:1079
#14 0xb7d7cb9d in KAction::event (this=0x868b7a8, event=0xbf812d84) at
/var/tmp/paludis/kde-base-kdelibs-scm/work/kdelibs-scm/kdeui/actions/kaction.cpp:88
#15 0xb5cdc4db in QApplicationPrivate::notify_helper (this=0x8077900,
receiver=0x868b7a8, e=0xbf812d84) at kernel/qapplication.cpp:4084
#16 0xb5ce3822 in QApplication::notify (this=0xbf813bf8, receiver=0x868b7a8,
e=0xbf812d84) at kernel/qapplication.cpp:3631
#17 0xb7e55d55 in KApplication::notify (this=0xbf813bf8, receiver=0x868b7a8,
event=0xbf812d84) at
/var/tmp/paludis/kde-base-kdelibs-scm/work/kdelibs-scm/kdeui/kernel/kapplication.cpp:307
#18 0xb65d35c2 in QCoreApplication::notifyInternal (this=0xbf813bf8,
receiver=0x868b7a8, event=0xbf812d84) at kernel/qcoreapplication.cpp:598
#19 0xb5d0cc7f in QShortcutMap::dispatchEvent (this=0x80779a0, e=0xbf8130fc) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#20 0xb5d0e75e in QShortcutMap::tryShortcutEvent (this=0x80779a0, o=0x883ce48,
e=0xbf8130fc) at kernel/qshortcutmap.cpp:369
#21 0xb5ce4b3e in QApplication::notify (this=0xbf813bf8, receiver=0x883ce48,
e=0xbf8130fc) at kernel/qapplication.cpp:3673
#22 0xb7e55d55 in KApplication::notify (this=0xbf813bf8, receiver=0x883ce48,
event=0xbf8130fc) at
/var/tmp/paludis/kde-base-kdelibs-scm/work/kdelibs-scm/kdeui/kernel/kapplication.cpp:307
#23 0xb65d35c2 in QCoreApplication::notifyInternal (this=0xbf813bf8,
receiver=0x883ce48, event=0xbf8130fc) at kernel/qcoreapplication.cpp:598
#24 0xb5cdd807 in qt_sendSpontaneousEvent (receiver=0x883ce48, event=0x868bb90)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216
#25 0xb5d5f6fd in QKeyMapper::sendKeyEvent (keyWidget=0x883ce48, grab=false,
type=QEvent::KeyPress, code=16777216, modifiers={i = -1082051652},
te...@0xbf8133e8, autorepeat=value optimized out,
count=1, nativeScanCode=9, nativeVirtualKey=65307, nativeModifiers=16) at
kernel/qkeymapper_x11.cpp:1675
#26 0xb5d6145e in QKeyMapperPrivate::translateKeyEvent (this=0x80e71d8,
keyWidget=0x883ce48, event=0xbf8138ac, grab=129) at
kernel/qkeymapper_x11.cpp:1645
#27 0xb5d3da64 in QApplication::x11ProcessEvent (this=0xbf813bf8,
event=0xbf8138ac) at kernel/qapplication_x11.cpp:3436
#28 0xb5d62b50 in x11EventSourceDispatch (s=0x807a308, callback=0,
user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#29 0xb4aef3b5 in IA__g_main_context_dispatch (context=0x8079890) at
gmain.c:2144
#30 0xb4af2667 in g_main_context_iterate (context=0x8079890, block=1,
dispatch=1, self=0x80771d0) at gmain.c:2778
#31 0xb4af2808 in IA__g_main_context_iteration (context=0x8079890, may_block=1)
at gmain.c:2841
#32 0xb65f83f4 in QEventDispatcherGlib::processEvents (this=0x804fc18, flags={i
= -1082049944}) at kernel/qeventdispatcher_glib.cpp:323
#33 0xb5d623cb in QGuiEventDispatcherGlib::processEvents (this=0x804fc18,
flags={i = -1082049896}) at kernel/qguieventdispatcher_glib.cpp:202
#34 0xb65d2000 in QEventLoop::processEvents (this=0xbf813b00, flags={i =
-1082049832}) at kernel/qeventloop.cpp:149
#35 0xb65d21a6 in QEventLoop::exec (this=0xbf813b00, flags={i = -1082049784})
at kernel/qeventloop.cpp:196
#36 0xb65d406e in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#37 0xb5cdc387 in QApplication::exec () at kernel/qapplication.cpp:3553
#38 0x0804a9b7 in main (argc=) at
/var/tmp/paludis/kde-base-kmail-scm/work/kmail/kmail/main.cpp:146
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug
[Bug 172362] New: external editor program opened needlessly
http://bugs.kde.org/show_bug.cgi?id=172362 Summary: external editor program opened needlessly Product: kmail Version: unspecified Platform: Compiled Sources OS/Version: unspecified Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: [EMAIL PROTECTED] Version:(using Devel) Installed from:Compiled sources I think this is the same bug as bug 48841 but, since that was for another version of KMail, I decided to create a new one. Sorry if I should have done otherwise. Using an external editor in the composer, if I press keys like Ctrl, Shift or Alt (alone), the external editor is launched, even if it shouldn't. I noticed it when I pressed Ctrl+Enter to send the mail and got the The external editor is still running. message box, but it happens for all keys (of course, the focus should be in the message widget, not in the From, To, Subject or other widgets). -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 171268] New: disabling word wrapping in composer window only for some lines
http://bugs.kde.org/show_bug.cgi?id=171268 Summary: disabling word wrapping in composer window only for some lines Product: kmail Version: unspecified Platform: Compiled Sources OS/Version: unspecified Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: [EMAIL PROTECTED] Version:(using Devel) Installed from:Compiled sources It would be nice to have the ability to turn off word wrapping for only some lines in the composer window. This feature would be very useful, for example, when sending e-mails containing some kind of source code: if word wrapping is on, then long lines of code will be split in two lines, maybe producing broken code. Turning off word wrapping for the whole e-mail solves this problem but forces the user to manually insert line breaks, if he wants to avoid long lines in the parts of the message which aren't source code. -- Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
