[kmail2] [Bug 316107] big regression: kmail IMAP connection and message display problems
https://bugs.kde.org/show_bug.cgi?id=316107 Colin J Thomson changed: What|Removed |Added CC|colin.thom...@g6avk.co.uk | -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 379036] attendees icons not dhown
https://bugs.kde.org/show_bug.cgi?id=379036 --- Comment #5 from Allen Winter --- no, Breeze. I don't see how this could be a problem with KOrganizer itself. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 379036] attendees icons not dhown
https://bugs.kde.org/show_bug.cgi?id=379036 --- Comment #4 from Martin Koller --- And you're using Oxygen icons ? -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 377395] Kontact is crashing during start up
https://bugs.kde.org/show_bug.cgi?id=377395 Christoph Feck changed: What|Removed |Added CC||robby.engelm...@igfs-ev.de --- Comment #11 from Christoph Feck --- *** Bug 379623 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 379623] Kontact crashed after trying to open a link with middle-mouse click out of an email in Kmail
https://bugs.kde.org/show_bug.cgi?id=379623 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 377395 *** -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 353240] Day numbers are cropped at the bottom in month view in korganizer
https://bugs.kde.org/show_bug.cgi?id=353240 Christoph Feck changed: What|Removed |Added CC||mle...@wrrc.us --- Comment #20 from Christoph Feck --- *** Bug 379676 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 379676] calendar manager
https://bugs.kde.org/show_bug.cgi?id=379676 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 353240 *** -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 379036] attendees icons not dhown
https://bugs.kde.org/show_bug.cgi?id=379036 Allen Winter changed: What|Removed |Added CC||win...@kde.org --- Comment #3 from Allen Winter --- works fine for me. no idea why this would be happening. I'm using self-compiled from master. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 379720] Kmail crashes when opening a saved e-mail (.eml) saved off Microsoft OWA
https://bugs.kde.org/show_bug.cgi?id=379720 Christoph Feck changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #3 from Christoph Feck --- Crash is in nouveau OpenGL driver, not handling multiple threads correctly. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 379626] crashing Kmail during closing of the window
https://bugs.kde.org/show_bug.cgi?id=379626 Christoph Feck changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 371507 *** -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 380394] New: Akonadi crash in 5.4.3 while updating folders
https://bugs.kde.org/show_bug.cgi?id=380394 Bug ID: 380394 Summary: Akonadi crash in 5.4.3 while updating folders Product: Akonadi Version: 5.4.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: mike...@gmail.com Target Milestone: --- Application: akonadiserver (5.4.3) Qt Version: 5.7.1 Frameworks Version: 5.34.0 Operating System: Linux 4.10.0-21-generic x86_64 Distribution: Ubuntu 17.04 -- Information about the crash: - What I was doing when the application crashed: I instructed Akonadi to update a folder (and all subfolders) of my Archive folder. There are many tens of thousands of messages in that folder tree. The crash can be reproduced every time. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff1559e1080 (LWP 14543))] Thread 47 (Thread 0x7ff0e5ffb700 (LWP 16156)): #0 0x7ff150adc553 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ff150adea0b in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff150adf49b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff150adf68c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff1542f2f2b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff15429c88a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff1540c9fe3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7ff1540cec98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff1525e16da in start_thread (arg=0x7ff0e5ffb700) at pthread_create.c:456 #9 0x7ff1537c417f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 46 (Thread 0x7ff0e7fff700 (LWP 15066)): #0 0x7ff1540d2057 in qstrcmp(QByteArray const&, char const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7ff15432afe0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7ff15431b14d in QMimeType::aliases() const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x55c0d9aa88c8 in Akonadi::Server::NotificationSubscriber::isMimeTypeMonitored (this=this@entry=0x7ff13c0bf5d0, mimeType=...) at ./src/server/notificationsubscriber.cpp:332 #4 0x55c0d9aa952e in Akonadi::Server::NotificationSubscriber::acceptsItemNotification (this=this@entry=0x7ff13c0bf5d0, notification=...) at ./src/server/notificationsubscriber.cpp:410 #5 0x55c0d9aaca0a in Akonadi::Server::NotificationSubscriber::acceptsNotification (this=this@entry=0x7ff13c0bf5d0, notification=...) at ./src/server/notificationsubscriber.cpp:636 #6 0x55c0d9aacb3b in Akonadi::Server::NotificationSubscriber::notify (this=0x7ff13c0bf5d0, notification=...) at ./src/server/notificationsubscriber.cpp:663 #7 0x55c0d9aa6c0f in NotifyRunnable::run (this=0x7ff13c010a40) at ./src/server/notificationmanager.cpp:152 #8 0x7ff1540cb03f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7ff1540cec98 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7ff1525e16da in start_thread (arg=0x7ff0e7fff700) at pthread_create.c:456 #11 0x7ff1537c417f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 45 (Thread 0x7ff0e67fc700 (LWP 15065)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7ff1540c615f in QBasicMutex::unlockInternal() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7ff1540c61b7 in QMutex::unlock() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7ff15431a01b in QMimeDatabase::mimeTypeForName(QString const&) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x55c0d9aa886b in Akonadi::Server::NotificationSubscriber::isMimeTypeMonitored (this=this@entry=0x7ff13c092160, mimeType=...) at ./src/server/notificationsubscriber.cpp:327 #5 0x55c0d9aa952e in Akonadi::Server::NotificationSubscriber::acceptsItemNotification (this=this@entry=0x7ff13c092160, notification=...) at ./src/server/notificationsubscriber.cpp:410 #6 0x55c0d9aaca0a in Akonadi::Server::NotificationSubscriber::acceptsNotification (this=this@entry=0x7ff13c092160, notification=...) at ./src/server/notificationsubscriber.cpp:636 #7 0x55c0d9aacb3b in Akonadi::Server::NotificationSubscriber::notify (this=0x7ff13c092160, notification=...) at ./src/server/notificationsubscriber.cpp:663 #8 0x55c0d9aa6c0f in NotifyRunnable::run (this=0x7ff13c2eb340) at ./src/server/notificationmanager.cpp:152 #9 0x7ff1540cb03f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7ff1540cec98 in ?? () from /usr/lib/x86_64-linux-gnu/l
[kontact] [Bug 374923] cannot used Ctrl-n in kontact to create new mail
https://bugs.kde.org/show_bug.cgi?id=374923 luisfe changed: What|Removed |Added CC||lui...@lftabera.es --- Comment #3 from luisfe --- I can confirm this problem with kontact 5.5.1 compiled from sources. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 376032] Emails not being moved from "new" to "cur"
https://bugs.kde.org/show_bug.cgi?id=376032 luisfe changed: What|Removed |Added CC||lui...@lftabera.es --- Comment #1 from luisfe --- I have explored this problem. Moving messages between local accounts always leave them in the new folder. Once you read or mark as unread the message, they move to the cur folder. Not sure if this is the correct behavior or not. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 378809] +q does not work after +Q has been used.
https://bugs.kde.org/show_bug.cgi?id=378809 luisfe changed: What|Removed |Added CC||lui...@lftabera.es --- Comment #1 from luisfe --- In fact, this is not only +q anf +q, this shortcut set focus on the quicksearch bar. If you set focus on this bar, for instance clicking on it with the mouse, then +q does not work. But neither does other shortcuts, like +l to check new mail. So, while the search bar is focused, shortcuts do not work. I think that this is a deeper known problem in kde applications, similar to the fact that if a menu is active, ckick for instance in File menu, while the menu is active +q does not work, neither other common shortcuts. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 379584] Old "delete" shortcut doesn't work anymore
https://bugs.kde.org/show_bug.cgi?id=379584 --- Comment #3 from luisfe --- This bug looks like a duplicate of 379189 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 379584] Old "delete" shortcut doesn't work anymore
https://bugs.kde.org/show_bug.cgi?id=379584 luisfe changed: What|Removed |Added CC||lui...@lftabera.es --- Comment #2 from luisfe --- I can confirm this behavior with kmail 5.5.1 If it is intended then it is annoying. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 380179] Regression kMail 5.5.1: Moving messages (DnD) does not work reliably any more
https://bugs.kde.org/show_bug.cgi?id=380179 luisfe changed: What|Removed |Added CC||lui...@lftabera.es --- Comment #1 from luisfe --- I can confirm the bug. It may be related to Bug 380182 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 380182] deleting several messages doesn't remove them from the message list
https://bugs.kde.org/show_bug.cgi?id=380182 luisfe changed: What|Removed |Added CC||lui...@lftabera.es --- Comment #3 from luisfe --- I can confirm the bug, but I cannot reproduce it reliably. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 376156] Deleting messages in IMAP account with server side folders enabled isn't possible
https://bugs.kde.org/show_bug.cgi?id=376156 --- Comment #5 from Allan Sandfeld --- Seems to be the inbox folder specifically that sometimes get the wrong ACL. It can be fixed by going into the akonadiconsole, to the browser tab, right clicking on the affected inbox and change the ACL settings to allow all the basic operations that are allowed on all other folders. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 376156] Deleting messages in IMAP account with server side folders enabled isn't possible
https://bugs.kde.org/show_bug.cgi?id=376156 Allan Sandfeld changed: What|Removed |Added CC||k...@carewolf.com --- Comment #4 from Allan Sandfeld --- I have the same problem. What is more odd is that it happened to 3 out of 4 IMAP accounted I added all from the exact same provider (different aliases). So it is not consistent -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 380388] moving a mail to a folder, no more the ability to explore a folder
https://bugs.kde.org/show_bug.cgi?id=380388 --- Comment #1 from Philippe ROUBACH --- Created attachment 105792 --> https://bugs.kde.org/attachment.cgi?id=105792&action=edit no more "+" to explore "fodegi" folder -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 380388] New: moving a mail to a folder, no more the ability to explore a folder
https://bugs.kde.org/show_bug.cgi?id=380388 Bug ID: 380388 Summary: moving a mail to a folder, no more the ability to explore a folder Product: kmail2 Version: 5.5.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: philippe.roub...@free.fr Target Milestone: --- Created attachment 105791 --> https://bugs.kde.org/attachment.cgi?id=105791&action=edit fodegi folder contents in kmail i select a mail then i click on "M" on the keyboard then i search a folder "fodegi" but i can't explore "fodegi" for selecting a folder "charge" inside where to move the mail. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 380182] deleting several messages doesn't remove them from the message list
https://bugs.kde.org/show_bug.cgi?id=380182 Antonio Rojas changed: What|Removed |Added Summary|deleting a message thread |deleting several messages |doesn't remove it from the |doesn't remove them from |message list|the message list -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 380182] deleting a message thread doesn't remove it from the message list
https://bugs.kde.org/show_bug.cgi?id=380182 --- Comment #2 from Antonio Rojas --- Actually this is unrelated to threading. The issue happens whenever one selects more than one message from the list and tries to delete them -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 380182] deleting a message thread doesn't remove it from the message list
https://bugs.kde.org/show_bug.cgi?id=380182 Kenny Fairweather changed: What|Removed |Added CC||ken...@engineer.com --- Comment #1 from Kenny Fairweather --- I can confirm this bug. Same software version, same description. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 380387] New: Crash on marking feed read
https://bugs.kde.org/show_bug.cgi?id=380387 Bug ID: 380387 Summary: Crash on marking feed read Product: kontact Version: 5.2.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: k...@itr.no Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.6.1 Frameworks Version: 5.33.0 Operating System: Linux 4.4.0-78-generic x86_64 Distribution: Ubuntu 16.04.2 LTS -- Information about the crash: Crashes semi consitently when wrying to mark a feed read. Usually ends up with several cash entries corrupted. Not allways the same feed. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc7c57d5940 (LWP 28431))] Thread 40 (Thread 0x7fc6a8bfc700 (LWP 31581)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7fc6fa3a5cbc in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #2 0x7fc6fa06674d in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #3 0x7fc6fa3a5a88 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #4 0x7fc6fa3a5abe in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #5 0x7fc6fa3a5b20 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #6 0x7fc7d5abb6ba in start_thread (arg=0x7fc6a8bfc700) at pthread_create.c:333 #7 0x7fc7dbb3182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 39 (Thread 0x7fc6a93fd700 (LWP 31580)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7fc6fa3a5cbc in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #2 0x7fc6fa06674d in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #3 0x7fc6fa3a5a88 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #4 0x7fc6fa3a5abe in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #5 0x7fc6fa3a5b20 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #6 0x7fc7d5abb6ba in start_thread (arg=0x7fc6a93fd700) at pthread_create.c:333 #7 0x7fc7dbb3182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 38 (Thread 0x7fc6aa20a700 (LWP 31579)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7fc6fa3a5cbc in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #2 0x7fc6fa06674d in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #3 0x7fc6fa3a5a88 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #4 0x7fc6fa3a5abe in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #5 0x7fc6fa3a5b20 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #6 0x7fc7d5abb6ba in start_thread (arg=0x7fc6aa20a700) at pthread_create.c:333 #7 0x7fc7dbb3182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 37 (Thread 0x7fc6aaa0b700 (LWP 31578)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 #1 0x7fc6fa3a5cbc in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #2 0x7fc6fa06674d in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #3 0x7fc6fa3a5a88 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #4 0x7fc6fa3a5abe in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #5 0x7fc6fa3a5b20 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #6 0x7fc7d5abb6ba in start_thread (arg=0x7fc6aaa0b700) at pthread_create.c:333 #7 0x7fc7dbb3182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 36 (Thread 0x7fc6ab4fe700 (LWP 31573)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc6fa3a5cfc in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #2 0x7fc6fa15e93c in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #3 0x7fc6fa3a5a88 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #4 0x7fc6fa3a5abe in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #5 0x7fc6fa3a5b20 in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #6 0x7fc7d5abb6ba in start_thread (arg=0x7fc6ab4fe700) at pthread_create.c:333 #7 0x7fc7dbb3182d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 35 (Thread 0x7fc6abcff700 (LWP 31572)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fc6fa3a5cfc in ?? () from /usr/lib/adobe-flashplugin/libflashplayer.so #2 0x7fc6fa15e93c in ?? () from /usr/lib/adobe-flashplug
[kontact] [Bug 378659] Kontact crash after switching from calendar to email
https://bugs.kde.org/show_bug.cgi?id=378659 --- Comment #1 from Diego --- Created attachment 105788 --> https://bugs.kde.org/attachment.cgi?id=105788&action=edit New crash information added by DrKonqi kontact (5.4.3) using Qt 5.7.1 - What I was doing when the application crashed: I think I clicked and hold on "Reply" to reply to all when I got this crash. -- Backtrace (Reduced): #6 0x7f284921b5f5 in QMenuSloppyState::childLeave() () at /lib64/libQt5Widgets.so.5 #8 0x7f2849223b54 in QMenuPrivate::mouseEventTaken(QMouseEvent*) () at /lib64/libQt5Widgets.so.5 #9 0x7f2849224cbb in QMenu::mouseMoveEvent(QMouseEvent*) () at /lib64/libQt5Widgets.so.5 #10 0x7f28490f77c0 in QWidget::event(QEvent*) () at /lib64/libQt5Widgets.so.5 #11 0x7f2849226753 in QMenu::event(QEvent*) () at /lib64/libQt5Widgets.so.5 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 378659] Kontact crash after switching from calendar to email
https://bugs.kde.org/show_bug.cgi?id=378659 Diego changed: What|Removed |Added CC||diego...@zoho.com -- You are receiving this mail because: You are the assignee for the bug.