[korganizer] [Bug 404275] Crash on startup
https://bugs.kde.org/show_bug.cgi?id=404275 --- Comment #17 from Kishore Gopalakrishnan --- (In reply to gesf02 from comment #15) > (In reply to Wolfgang Bauer from comment #10) > > (In reply to Christoph Feck from comment #9) > > > This is possibly fixed with > > > https://code.qt.io/cgit/qt/qtbase.git/commit/src/corelib/ > > > tools?id=82ad4be4a2e0c2bccb6cd8ea2440aefee4ec48ec in Qt 5.12.4. > > > > It seems that the crash is actually already fixed in Qt 5.12.3. > > At least I was able to reproduce it with 5.12.2 (by setting /etc/localtime > > to point to Asia/Tokyo), and korganizer starts fine now after I updated to > > Qt 5.12.3. > > How to update to Qt 5.12.3 without default repository? I'm using Fedora 30. Ask the fedora maintainers to update Qt or backport the fix. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 404275] Crash on startup
https://bugs.kde.org/show_bug.cgi?id=404275 --- Comment #16 from Seijiro Moriyama --- I have confirmed that Korganizer works as before after an update. Thank you so much. Seijiro Moriyama -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 409128] KOrganizer crashes when starting
https://bugs.kde.org/show_bug.cgi?id=409128 --- Comment #2 from ges...@gmail.com --- (In reply to Wolfgang Bauer from comment #1) > What Qt version are you using? > > Even though the debug symbols are missing, your backtrace looks pretty much > like bug#404275. > That was a bug in Qt (the crash only occurs with certain time zones), and > should be fixed in Qt 5.12.3. Thanks. It does seem exactly the same. I tried to change the timezone from Asia/Tokyo to Asia/Shanghai or America/New_York. But it does not work. Do you know how to update to Qt 5.12.3 without default repository? I'm using Fedora 30. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 404275] Crash on startup
https://bugs.kde.org/show_bug.cgi?id=404275 ges...@gmail.com changed: What|Removed |Added CC||ges...@gmail.com --- Comment #15 from ges...@gmail.com --- (In reply to Wolfgang Bauer from comment #10) > (In reply to Christoph Feck from comment #9) > > This is possibly fixed with > > https://code.qt.io/cgit/qt/qtbase.git/commit/src/corelib/ > > tools?id=82ad4be4a2e0c2bccb6cd8ea2440aefee4ec48ec in Qt 5.12.4. > > It seems that the crash is actually already fixed in Qt 5.12.3. > At least I was able to reproduce it with 5.12.2 (by setting /etc/localtime > to point to Asia/Tokyo), and korganizer starts fine now after I updated to > Qt 5.12.3. How to update to Qt 5.12.3 without default repository? I'm using Fedora 30. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 409128] KOrganizer crashes when starting
https://bugs.kde.org/show_bug.cgi?id=409128 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at --- Comment #1 from Wolfgang Bauer --- What Qt version are you using? Even though the debug symbols are missing, your backtrace looks pretty much like bug#404275. That was a bug in Qt (the crash only occurs with certain time zones), and should be fixed in Qt 5.12.3. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 390781] KMail is blank!
https://bugs.kde.org/show_bug.cgi?id=390781 --- Comment #3 from Christoph Feck --- The reporter decided to close his own bug. If you are still affected with a recent version (KMail 5.11), you could clone the ticket as your own bug. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 406251] Korganizer preview and print do not shows events
https://bugs.kde.org/show_bug.cgi?id=406251 Peer Frank changed: What|Removed |Added CC||peer.fr...@web.de --- Comment #2 from Peer Frank --- same problem using OpenSuse Leap 15.1 korganizer 5.10.3 (KDE FW 5.55) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 390781] KMail is blank!
https://bugs.kde.org/show_bug.cgi?id=390781 --- Comment #2 from Martin Schnitkemper --- Why has the state changed to "RESOLVED"? It's still not resolved, it happen to me every few days that kmail starts with a blank screen and no contents. After closing, there still remains a process named "kmail" and I have to kill it, before I can start starting a next kmail-session. -- You are receiving this mail because: You are the assignee for the bug.
[kdepim] [Bug 346175] KDE PIM 15.08 release tracking bug
https://bugs.kde.org/show_bug.cgi?id=346175 Laurent Montel changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||mon...@kde.org -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 409134] New: Suggestion: Show notification by default only for preferred folders.
https://bugs.kde.org/show_bug.cgi?id=409134 Bug ID: 409134 Summary: Suggestion: Show notification by default only for preferred folders. Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ci3...@gmail.com Target Milestone: --- Currently, Kmail (19.04.2) notifies about mails in all folders. This can be configured per folder settings -> "Act on new/unread mail in this folder". Maybe you can connect this with the preferred folders panel: The notification/setting is off by default but enabled if the folder is added to the preferred folders. Of course, the config option can be switched manually, too, but I think, the preferred folder approach is more user friendly (especially, when having a lot of folders). -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409122] Akonadi sometimes doesn't send email (GMail)
https://bugs.kde.org/show_bug.cgi?id=409122 Martin Steigerwald changed: What|Removed |Added CC||mar...@lichtvoll.de --- Comment #1 from Martin Steigerwald --- Hi Tom. Thanks for your report. How is that report different from your other report Bug 390733 - KMail cannot send mails using gmail smtp ? -- You are receiving this mail because: You are on the CC list for the bug.
[korganizer] [Bug 409128] New: KOrganizer crashes when starting
https://bugs.kde.org/show_bug.cgi?id=409128 Bug ID: 409128 Summary: KOrganizer crashes when starting Product: korganizer Version: 5.11.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: ges...@gmail.com Target Milestone: --- Hi, I just upgraded from Fedora 29 to Fedora 30 and am using KDE. After upgrade, the Korganizer cannot open again and every time crashes before the windows appears. The error message is: Executable: korganizer PID: 9137 Signal: Segmentation fault (11) Time: 6/23/19 12:51:47 and the generated crash information is Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe7f70f1180 (LWP 9137))] Thread 5 (Thread 0x7fe7e2dee700 (LWP 9144)): #0 0x7fe7fd5bb2b7 in poll () from /lib64/libc.so.6 #1 0x7fe7fac791de in ?? () from /lib64/libglib-2.0.so.0 #2 0x7fe7fac79313 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7fe7fdb5d413 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7fe7fdb072bb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7fe7fd960675 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7fe7fd9617c6 in ?? () from /lib64/libQt5Core.so.5 #7 0x7fe7fb67d5a2 in start_thread () from /lib64/libpthread.so.0 #8 0x7fe7fd5c6023 in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fe7e35ef700 (LWP 9142)): #0 0x7fe7fd5bb2b7 in poll () from /lib64/libc.so.6 #1 0x7fe7fac791de in ?? () from /lib64/libglib-2.0.so.0 #2 0x7fe7fac79313 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7fe7fdb5d413 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7fe7fdb072bb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7fe7fd960675 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7fe7fd9617c6 in ?? () from /lib64/libQt5Core.so.5 #7 0x7fe7fb67d5a2 in start_thread () from /lib64/libpthread.so.0 #8 0x7fe7fd5c6023 in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fe7e9072700 (LWP 9140)): #0 0x7fe7fd5bb2b7 in poll () from /lib64/libc.so.6 #1 0x7fe7fac791de in ?? () from /lib64/libglib-2.0.so.0 #2 0x7fe7fac79313 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7fe7fdb5d413 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7fe7fdb072bb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7fe7fd960675 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7fe7fd20ff4a in ?? () from /lib64/libQt5DBus.so.5 #7 0x7fe7fd9617c6 in ?? () from /lib64/libQt5Core.so.5 #8 0x7fe7fb67d5a2 in start_thread () from /lib64/libpthread.so.0 #9 0x7fe7fd5c6023 in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fe7e9e02700 (LWP 9139)): #0 0x7fe7fd5bb2b7 in poll () from /lib64/libc.so.6 #1 0x7fe7fac0b38a in ?? () from /lib64/libxcb.so.1 #2 0x7fe7fac0cffa in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7fe7e9ff4908 in ?? () from /lib64/libQt5XcbQpa.so.5 #4 0x7fe7fd9617c6 in ?? () from /lib64/libQt5Core.so.5 #5 0x7fe7fb67d5a2 in start_thread () from /lib64/libpthread.so.0 #6 0x7fe7fd5c6023 in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fe7f70f1180 (LWP 9137)): [KCrash Handler] #6 0x7fe7fd9ff673 in ?? () from /lib64/libQt5Core.so.5 #7 0x7fe7fd9f9719 in ?? () from /lib64/libQt5Core.so.5 #8 0x7fe7fd9a41ad in ?? () from /lib64/libQt5Core.so.5 #9 0x7fe7fd9a4554 in ?? () from /lib64/libQt5Core.so.5 #10 0x7fe7fd9a49b5 in QDateTime::QDateTime(QDate const&, QTime const&, QTimeZone const&) () from /lib64/libQt5Core.so.5 #11 0x7fe7fed0db68 in KCalCore::MemoryCalendar::rawEvents(QDate const&, QDate const&, QTimeZone const&, bool) const () from /lib64/libKF5CalendarCore.so.5 #12 0x7fe7fecc00ce in KCalCore::Calendar::events(QDate const&, QDate const&, QTimeZone const&, bool) const () from /lib64/libKF5CalendarCore.so.5 #13 0x7fe7ff0a7562 in ?? () from /lib64/libkorganizerprivate.so.5 #14 0x7fe7ff0a7b78 in ?? () from /lib64/libkorganizerprivate.so.5 #15 0x7fe7ff09ed05 in ?? () from /lib64/libkorganizerprivate.so.5 #16 0x7fe7ff098789 in ?? () from /lib64/libkorganizerprivate.so.5 #17 0x7fe7ff08f986 in CalendarView::CalendarView(QWidget*) () from /lib64/libkorganizerprivate.so.5 #18 0x559d25cf9ce3 in ?? () #19 0x559d25cfb202 in ?? () #20 0x559d25cfbd19 in ?? () #21 0x7fe7ff140575 in KontactInterface::PimUniqueApplication::start(QStringList const&, bool) () from /lib64/libKF5KontactInterface.so.5 #22 0x559d25cf89e7 in ?? () #23 0x7fe7fd4eef33 in __libc_start_main () from
[kmail2] [Bug 390733] KMail cannot send mails using gmail smtp
https://bugs.kde.org/show_bug.cgi?id=390733 --- Comment #17 from Tom Kijas --- KDE 5.16.1 the bug still exists, KMail is still unusable with GMail (google apps) account. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409122] New: Akonadi sometimes doesn't send email (GMail)
https://bugs.kde.org/show_bug.cgi?id=409122 Bug ID: 409122 Summary: Akonadi sometimes doesn't send email (GMail) Product: Akonadi Version: GIT (master) Platform: Neon Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Gmail resource Assignee: dvra...@kde.org Reporter: t.ki...@gmail.com CC: kdepim-bugs@kde.org Target Milestone: --- SUMMARY Akonadi sometimes doesn't send email using properly configured GMail account, the email stays in "Outgoing" folder for ages and I do not know why. Please tell me how to help you resolve this bug, because it makes it unusable. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are on the CC list for the bug.
[kmailtransport] [Bug 400195] Some emails stays in outgoing folder
https://bugs.kde.org/show_bug.cgi?id=400195 Tom Kijas changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from Tom Kijas --- For years... this bug exists for years... nothing changes. God, that's crazy. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 385807] KMail doesn't synchronise gmail again
https://bugs.kde.org/show_bug.cgi?id=385807 Tom Kijas changed: What|Removed |Added CC||t.ki...@gmail.com Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 390781] KMail is blank!
https://bugs.kde.org/show_bug.cgi?id=390781 Tom Kijas changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED CC||t.ki...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 377521] regression: system tray icon no longer shows number of new mails
https://bugs.kde.org/show_bug.cgi?id=377521 --- Comment #29 from Éric Brunet --- Created attachment 121110 --> https://bugs.kde.org/attachment.cgi?id=121110=edit patch to reenable numbers, v19.04 Updated version of the patch to re-enable numbers in systray for kmail. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 409001] when opened message (incapsulated by outlook) kmail crashes
https://bugs.kde.org/show_bug.cgi?id=409001 --- Comment #7 from Diego Ercolani --- The document it's on its way to you. Thank you -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409110] Akonadi Server crash after some time of having Kontact running
https://bugs.kde.org/show_bug.cgi?id=409110 Robby Engelmann changed: What|Removed |Added CC||robby.engelmann@r-engelmann ||.de Version|unspecified |5.11.2 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 409110] New: Akonadi Server crash after some time of having Kontact running
https://bugs.kde.org/show_bug.cgi?id=409110 Bug ID: 409110 Summary: Akonadi Server crash after some time of having Kontact running Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: robby.engelm...@r-engelmann.de Target Milestone: --- Created attachment 121108 --> https://bugs.kde.org/attachment.cgi?id=121108=edit crash information from Drkonqi SUMMARY Akonadi Server crash after some time of having Kontact running. I do not observe any special events going on, when it happens. Also akonadictl fschk / vacuum does not solve it (worked often in the past to solve such crashes for me). STEPS TO REPRODUCE 1. Start Kontact 2. Have E-mail coming in from time to time 3. see the crash OBSERVED RESULT crash EXPECTED RESULT no crash All crash information attached... -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 409001] when opened message (incapsulated by outlook) kmail crashes
https://bugs.kde.org/show_bug.cgi?id=409001 --- Comment #6 from Volker Krause --- Okular being able to display the document is indeed an important observation, could be a bug in the extractor plugin after all, or a different way of using Popppler. Providing the affected document in private is perfectly fine of course, you can send it to vkra...@kde.org (GPG key 0x7F96CCD64D12D247 if you want to encrypt it) and I'll delete as soon as the problem has been debugged. Thanks! -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 409001] when opened message (incapsulated by outlook) kmail crashes
https://bugs.kde.org/show_bug.cgi?id=409001 --- Comment #5 from Diego Ercolani --- pc-diego:~ # rpm -qf /usr/lib64/qt5/plugins/messageviewer/bodypartformatter/messageviewer_bodypartformatter_semantic.so kdepim-addons-18.12.3-lp151.3.1.x86_64 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 409001] when opened message (incapsulated by outlook) kmail crashes
https://bugs.kde.org/show_bug.cgi?id=409001 --- Comment #4 from Diego Ercolani --- @Volker, I did it: pc-diego:~ # mv /usr/lib64/qt5/plugins/messageviewer/bodypartformatter/messageviewer_bodypartformatter_semantic.so /usr/lib64/qt5/plugins/messageviewer/bodypartformatter/messageviewer_bodypartformatter_semantic.so.bak Restarting kontact and I can read the mail without crashing. I can also read the pdf documents attached without any problem using okular. To answer your request, I can provide you the original e-mail message, but, although it is not containing "secrets" it contain contractual information so I can not divulgate publically so I need an email address or a personal contact of you Thank you Diego -- You are receiving this mail because: You are the assignee for the bug.
