[kmail2] [Bug 484599] Name of UI element too long (Hide/Show Sidebar)
https://bugs.kde.org/show_bug.cgi?id=484599 --- Comment #6 from Matthias --- I am just confused -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 484599] Name of UI element too long (Hide/Show Sidebar)
https://bugs.kde.org/show_bug.cgi?id=484599 --- Comment #4 from Matthias --- So it will show 'Hide Sidebar' when open? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 484599] Name of UI element too long (Hide/Show Sidebar)
https://bugs.kde.org/show_bug.cgi?id=484599 --- Comment #2 from Matthias --- Do I understand this right, that the text now says 'Show Sidebar' both when its already open, and when its closed? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 484599] New: Name of UI element too long (Hide/Show Sidebar)
https://bugs.kde.org/show_bug.cgi?id=484599 Bug ID: 484599 Summary: Name of UI element too long (Hide/Show Sidebar) Classification: Applications Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- Created attachment 167845 --> https://bugs.kde.org/attachment.cgi?id=167845=edit UI Element SUMMARY The current name for the toolbar element to show and hide the sidebar is unnecessary long: Hide/Show the component sidebar This makes it uneasy, to use this as a dedicated button in the toolbar. (See screenshot) First, there is no other sidebar, so "component" is superfluous to begin with. Second, other buttons have the option to change, depending on the state. Like in Dolphin, where the "Split" element changes into "Close" and vice versa. We could implement, to do the same here. Otherwise, I suggest to rename the element simply into "Sidebar" and call it a day. Also consider, that this causes the translators to do work, so let us decide on this with foresight. :) Thanks a lot STEPS TO REPRODUCE 1. Open Kontact, switch to the KMail panel (I assume standalone Kmail is the same) 2. Add the 'Hide/Show the component sidebar' element to the toolbar. 3. Acknowledge, that it takes much space. Operating System: NixOS 24.05 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.6.22 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800U with Radeon Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 478474] Kmail ask for sieve passworts on every start
https://bugs.kde.org/show_bug.cgi?id=478474 --- Comment #2 from Matthias Fehring --- I also tried to disable “Reuse host login configuration“. No matter if I use “IMAP user and password“ or give “User name and password“ in the Sieve config, it asks for the password when trying to connect to the Sieve server. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 478474] Kmail ask for sieve passworts on every start
https://bugs.kde.org/show_bug.cgi?id=478474 Matthias Fehring changed: What|Removed |Added CC||buschman...@opensuse.org --- Comment #1 from Matthias Fehring --- Same here with kmail2 6.0.0 (24.02.0) on Plasma 6.0.1 and KDE Frameworks 6.0.0. Log shows the following lines for every account: We have an error during reading password "Entry not found" org.kde.pim.kmail: An error occurred while reading password: "Entry not found" -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 435992] Akonadi crashed : Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=435992 Matthias Welwarsky changed: What|Removed |Added CC||ma...@welwarsky.de -- You are receiving this mail because: You are the assignee for the bug.
[kmailtransport] [Bug 437908] Kmail doesn't move messages on server
https://bugs.kde.org/show_bug.cgi?id=437908 --- Comment #1 from Matthias Mueller --- Just tried to get more info out of akonadi console, but if i move a message there, the same issue arises -- You are receiving this mail because: You are the assignee for the bug.
[kmailtransport] [Bug 437908] New: Kmail doesn't move messages on server
https://bugs.kde.org/show_bug.cgi?id=437908 Bug ID: 437908 Summary: Kmail doesn't move messages on server Product: kmailtransport Version: 5.17.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: mat.muel...@mailbox.org Target Milestone: --- SUMMARY Kmail sometimes doesn't move (move to other folder or delete with trash set to the trash folder on the imap server) messages. So when i delete a message, the next time i look for mails it pops up as unread again. Same goes for moving a message to another folder - on the server it still resides in the old folder, in kmail it's displayed in the new AND the old folder after i hit "look for mails". Seems to me as if the communication with the server is uni-directional and kmail doesn't send actions to the server? It happens with all three providers i've got set up (mailbox.org, web.de and gmx.net) - but only occasionally. If it happens, there is no error message. I couldn't find any kmail logs, so if there is more information i could provide, please tell me. I'm also not sure if kmailtransport or kmail2 is the right place - kmail2 doesn't offer the 5.17.1 version though ;) SOFTWARE/OS VERSIONS KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 KMail Version: 5.17.1 (21.04.1) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 381257] KMail does not remember window size or position
https://bugs.kde.org/show_bug.cgi?id=381257 --- Comment #4 from Matthias Mueller --- it's gotten much more rare for me that it doesn't remember the correct size and position, that much i can confirm. I'd say the instances where it is launched in the wrong place are mostly after crashes or forced reboots or the like, but i'm not 100% positive. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 437111] New: Kontact crashed on quit
https://bugs.kde.org/show_bug.cgi?id=437111 Bug ID: 437111 Summary: Kontact crashed on quit Product: kontact Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: matthias.h.na...@gmail.com Target Milestone: --- Application: kontact (5.16.3 (20.12.3)) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.10.1-gentoo-r1 x86_64 Windowing system: X11 Distribution: Gentoo/Linux -- Information about the crash: - What I was doing when the application crashed: Nothing in particular, just closing the application. It is sometimes reproducible (estimate: 1 out of 20). The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fe6f6a57ec0 (LWP 1853))] [KCrash Handler] #6 0x7fe65110e321 in KMReaderMainWin::~KMReaderMainWin() (this=this@entry=0x7fe67c02a490, __in_chrg=, __vtt_parm=) at /var/tmp/portage/kde-apps/kmail-20.12.3/work/kmail-20.12.3/src/kmreadermainwin.cpp:115 #7 0x7fe65110e409 in KMReaderMainWin::~KMReaderMainWin() (this=0x7fe67c02a490, __in_chrg=, __vtt_parm=) at /var/tmp/portage/kde-apps/kmail-20.12.3/work/kmail-20.12.3/src/kmreadermainwin.cpp:117 #8 0x7fe709aa4d8f in QObject::event(QEvent*) (this=this@entry=0x7fe67c02a490, e=e@entry=0x7fe67c06c370) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qobject.cpp:1301 #9 0x7fe70a4b57c3 in QWidget::event(QEvent*) (this=this@entry=0x7fe67c02a490, event=event@entry=0x7fe67c06c370) at /var/tmp/portage/dev-qt/qtwidgets-5.15.2/work/qtbase-everywhere-src-5.15.2/src/widgets/kernel/qwidget.cpp:9080 #10 0x7fe70a5c9734 in QMainWindow::event(QEvent*) (this=this@entry=0x7fe67c02a490, event=event@entry=0x7fe67c06c370) at /var/tmp/portage/dev-qt/qtwidgets-5.15.2/work/qtbase-everywhere-src-5.15.2/src/widgets/widgets/qmainwindow.cpp:1341 #11 0x7fe70accfedb in KMainWindow::event(QEvent*) (this=this@entry=0x7fe67c02a490, ev=ev@entry=0x7fe67c06c370) at /var/tmp/portage/kde-frameworks/kxmlgui-5.80.0/work/kxmlgui-5.80.0/src/kmainwindow.cpp:913 #12 0x7fe70ad19fb7 in KXmlGuiWindow::event(QEvent*) (this=0x7fe67c02a490, ev=0x7fe67c06c370) at /var/tmp/portage/kde-frameworks/kxmlgui-5.80.0/work/kxmlgui-5.80.0/src/kxmlguiwindow.cpp:109 #13 0x7fe70a473d3f in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x55f6cdd183f0, receiver=receiver@entry=0x7fe67c02a490, e=e@entry=0x7fe67c06c370) at /var/tmp/portage/dev-qt/qtwidgets-5.15.2/work/qtbase-everywhere-src-5.15.2/src/widgets/kernel/qapplication.cpp:3632 #14 0x7fe70a47c950 in QApplication::notify(QObject*, QEvent*) (this=0x7ffeaf399a20, receiver=0x7fe67c02a490, e=0x7fe67c06c370) at /var/tmp/portage/dev-qt/qtwidgets-5.15.2/work/qtbase-everywhere-src-5.15.2/src/widgets/kernel/qapplication.cpp:3156 #15 0x7fe709a79817 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x7fe67c02a490, event=0x7fe67c06c370) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qcoreapplication.cpp:1063 #16 0x7fe709a7c340 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x55f6cdd08f90) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qcoreapplication.cpp:1817 #17 0x7fe709acee73 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x55f6cdd92b50) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qeventdispatcher_glib.cpp:277 #18 0x7fe7003e1c7c in g_main_dispatch (context=0x7fe6f0005000) at ../glib-2.66.7/glib/gmain.c:3325 #19 g_main_context_dispatch (context=context@entry=0x7fe6f0005000) at ../glib-2.66.7/glib/gmain.c:4043 #20 0x7fe7003e1ef8 in g_main_context_iterate (context=context@entry=0x7fe6f0005000, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib-2.66.7/glib/gmain.c:4119 #21 0x7fe7003e1f8f in g_main_context_iteration (context=0x7fe6f0005000, may_block=may_block@entry=1) at ../glib-2.66.7/glib/gmain.c:4184 #22 0x7fe709acec20 in QEventDispatcherGlib::processEvents(QFlags) (this=0x55f6cdd8e230, flags=...) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qeventdispatcher_glib.cpp:423 #23 0x7fe709a78663 in QEventLoop::exec(QFlags) (this=this@entry=0x7ffeaf399900, flags=..., flags@entry=...) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/include/QtCore/../../src/corelib/global/qflags.h:69 #24 0x7fe709a805a0 in QCoreApplication::exec() () at
[kmail2] [Bug 423189] Cannot make default script active
https://bugs.kde.org/show_bug.cgi?id=423189 --- Comment #5 from Matthias Heinz --- After digging around in the code a bit I think I found the problem. In ksieveui/managescriptsjob/generateglobalscriptjob.cpp is the function GenerateGlobalScriptJob::writeUserScript(), which is called by the start() function. In the writeUserScript() function a put() is called to kmanagesieve/sievejob.cpp SieveJob *SieveJob::put. And if you look closely it has two booleans as input. One to set a script active, one to deactivate it. And in writeUserScript() both bools are "false", which is wrong. The first one should "true". -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 423189] Cannot make default script active
https://bugs.kde.org/show_bug.cgi?id=423189 Matthias Heinz changed: What|Removed |Added CC||m.he...@gmx.net --- Comment #4 from Matthias Heinz --- Hi, I just stumbled about that problem as well. Since sieve is a relatively simple protocol I first thought this would be dovecots fault. But no, the problem seems to be kmails sieve editor here. I could just activate the script with SETACTIVE "USER" over an openssl s_client connection and now it works. Easiest fix would probably be to run SETACTIVE "USER" on every connection or so... -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 429134] Kmail doesn't remember window position after session restore
https://bugs.kde.org/show_bug.cgi?id=429134 --- Comment #1 from Matthias Mueller --- I have to add to that report - it seems that Kmail now remembers the position it had when exiting kmail through the tray. So that might be a workaround if someone encounters the same problem :) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 429134] New: Kmail doesn't remember window position after session restore
https://bugs.kde.org/show_bug.cgi?id=429134 Bug ID: 429134 Summary: Kmail doesn't remember window position after session restore Product: kmail2 Version: 5.15.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: mat.muel...@mailbox.org Target Milestone: --- SUMMARY I use session restore on reboot and usually have kmail on the right half of my second monitor. After boot, kmail is opened in the top left corner of the main screen. Exiting Kmail and starting it (or closing the window and opening it from tray) works fine, the issue only occurs on boot. I'm not sure if its a kmail or kwin/plasma issue, but i only observed this behaviour on kmail yet. To make matters worse, window rules don't work properly for kmail (i tried "apply on initialization" for position and size) - reported in https://bugs.kde.org/show_bug.cgi?id=381257 STEPS TO REPRODUCE 1. position kmail main window to your hearts content 2. reboot with option "restore session" active 3. observe wrong placement of kmail main window OBSERVED RESULT Kmail is positioned in the top left corner of the main screen EXPECTED RESULT Kmail should be where it was on shutdown SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro testing KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 381257] KMail does not remember window size or position
https://bugs.kde.org/show_bug.cgi?id=381257 Matthias Mueller changed: What|Removed |Added CC||mat.muel...@mailbox.org --- Comment #2 from Matthias Mueller --- I can confirm this, too - Manjaro testing with 5.15.3 currently -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 Matthias changed: What|Removed |Added CC||walter.matth...@posteo.de --- Comment #47 from Matthias --- I am affected by the same bug/behaviour as the original author. I can set up the CalDav ressource (in my case caldav.icloud.com), the list of calendars is pulled correctly, but nothing (no event) is synchronising. I can not get any valuable information from akonadiconsole on what exactly the problem is. Currently i am on Kubuntu 20.04 with Kontact 5.11.3 and Kio 5.68.0, but the same behaviour is shown by an openSuse Tumbleweed install with Kontact 5.13.3 and Kio 5.68.0. -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 387804] Create folder in KAddressBook fails
https://bugs.kde.org/show_bug.cgi?id=387804 --- Comment #5 from Matthias Weiss --- Created attachment 125801 --> https://bugs.kde.org/attachment.cgi?id=125801=edit Saved log from akonadiconsole -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 387804] Create folder in KAddressBook fails
https://bugs.kde.org/show_bug.cgi?id=387804 Matthias Weiss changed: What|Removed |Added CC||matthias_we...@gmx.at --- Comment #4 from Matthias Weiss --- I am using kaddressbook 5.12.3 with "akonadictl --version" also reports 5.12.3 Both are the latest versions from "Debian Testing". I have a similar error message when clicking "Add Address Book Folder..." I get "Could not create address book folder: Could not create collection [XYZ], resourceId: 38" I used akonadiconsole and found error messages in the logging tab. I will try to attach the log. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 414794] kmail crashing in kitinerary when opening a mail
https://bugs.kde.org/show_bug.cgi?id=414794 Jan-Matthias Braun changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REPORTED --- Comment #2 from Jan-Matthias Braun --- It probably was a stupid idea to just set the status to resolved, as kde applications 19.08 are going to be around a bit longer. I am setting this back to reported and leave the decision on the status to people who actually know how and when to do this. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 414794] kmail crashing in kitinerary when opening a mail
https://bugs.kde.org/show_bug.cgi?id=414794 Jan-Matthias Braun changed: What|Removed |Added Component|general |mail -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 414794] kmail crashing in kitinerary when opening a mail
https://bugs.kde.org/show_bug.cgi?id=414794 Jan-Matthias Braun changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Jan-Matthias Braun --- This seems to be fixed in kde-applications 19.11.90. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 414794] New: kmail crashing in kitinerary when opening a mail
https://bugs.kde.org/show_bug.cgi?id=414794 Bug ID: 414794 Summary: kmail crashing in kitinerary when opening a mail Product: kontact Version: 5.12.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jan_br...@gmx.net Target Milestone: --- Application: kontact (5.12.3) Qt Version: 5.14.0 Frameworks Version: 5.64.0 Operating System: Linux 5.4.1 x86_64 Distribution: "Gentoo Base System release 2.6" -- Information about the crash: - What I was doing when the application crashed: I was opening a mail from the my inbox. I could repeat this several times on the same mail, i.e., there are mails I cannot read. Compiler flags are (this is gentoo after all) "-O2 -fomit-frame-pointer -march=native", so quite standard. The e-mail contains two parts, one is text/html, and the other is a pdf attachment. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5f8b57da40 (LWP 35527))] Thread 71 (Thread 0x7f5eae7fc700 (LWP 50226)): #0 0x7f5f9b05ed2d in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5f94e18f66 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x2e3b0450 in () #3 0x000553ec in () #4 0x2e3b1008 in () #5 0x in () Thread 70 (Thread 0x7f5db4b68700 (LWP 36127)): #0 0x7f5f9bfc7a6b in poll () at /lib64/libc.so.6 #1 0x7f5f9a65017e in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0 #2 0x7f5f9a65029f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f5f9c60d2eb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f5f9c5b5c1b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f5f9c400fde in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f5f9c40202f in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #7 0x7f5f9b057427 in start_thread () at /lib64/libpthread.so.0 #8 0x7f5f9bfd3d5f in clone () at /lib64/libc.so.6 Thread 69 (Thread 0x7f5db6ffd700 (LWP 35693)): #0 0x7f5f9b05e9f7 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5f8912b68b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f5f8912b297 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f5f9b057427 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5f9bfd3d5f in clone () at /lib64/libc.so.6 Thread 68 (Thread 0x7f5db77fe700 (LWP 35692)): #0 0x7f5f9b05e9f7 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5f8912b68b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f5f8912b297 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f5f9b057427 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5f9bfd3d5f in clone () at /lib64/libc.so.6 Thread 67 (Thread 0x7f5db7fff700 (LWP 35691)): #0 0x7f5f9b05e9f7 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5f8912b68b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f5f8912b297 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f5f9b057427 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5f9bfd3d5f in clone () at /lib64/libc.so.6 Thread 66 (Thread 0x7f5dccba1700 (LWP 35690)): #0 0x7f5f9b05e9f7 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5f8912b68b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f5f8912b297 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f5f9b057427 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5f9bfd3d5f in clone () at /lib64/libc.so.6 Thread 65 (Thread 0x7f5dcd3a2700 (LWP 35689)): #0 0x7f5f9b05e9f7 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5f8912b68b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f5f8912b297 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f5f9b057427 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5f9bfd3d5f in clone () at /lib64/libc.so.6 Thread 64 (Thread 0x7f5dcdba3700 (LWP 35688)): #0 0x7f5f9b05e9f7 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5f8912b68b in util_queue_thread_func () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f5f8912b297 in impl_thrd_routine () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f5f9b057427 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5f9bfd3d5f in clone () at /lib64/libc.so.6 Thread 63 (Thread 0x7f5dce8d6700
[korganizer] [Bug 413316] Can't see the contents of my Nextcloud calendar
https://bugs.kde.org/show_bug.cgi?id=413316 --- Comment #5 from Matthias Fehring --- Hey David Faure, your fix works for me. :) With the changes applied, the calendar data is visible and Nextcloud stops throwing the exception about a bad request. -- You are receiving this mail because: You are the assignee for the bug.
[korganizer] [Bug 413316] Can't see the contents of my Nextcloud calendar
https://bugs.kde.org/show_bug.cgi?id=413316 Matthias Fehring changed: What|Removed |Added CC||buschmann@huessenbergnetz.d ||e --- Comment #1 from Matthias Fehring --- I have the same issue since upgrading my Nextcloud to version 17. At least I think that started after the upgrade as I only recognized the issue with Kontact/Korganizer today as it is working on my phone as expected. Nextcloud throws an exception about a bad request with the following message: "A calendar-query REPORT on a calendar with a Depth: 0 is undefined. Set Depth to 1" My system: - openSUSE Tumbleweed - Qt 5.13.1 - KDE Frameworks: 5.63.0 - KDE Plasma: 5.17 - KDE Applications: 19.08.2 - Kontact: 5.12.2 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 399245] Restore UI functionality related to "Show HTML side bar"
https://bugs.kde.org/show_bug.cgi?id=399245 Matthias changed: What|Removed |Added CC||shaloksha...@protonmail.ch --- Comment #11 from Matthias --- Now as this is a popular vote, what is happening? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 411850] Strg+U said to be used multiple times in German translation.
https://bugs.kde.org/show_bug.cgi?id=411850 Matthias changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Matthias --- I think this is solved. I updated my system and did not reboot, now its fixed. Thanks a lot -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 411850] New: Strg+U said to be used multiple times in German translation.
https://bugs.kde.org/show_bug.cgi?id=411850 Bug ID: 411850 Summary: Strg+U said to be used multiple times in German translation. Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- Created attachment 122623 --> https://bugs.kde.org/attachment.cgi?id=122623=edit KDE Keybinding showing usage for Ctrl+U SUMMARY When pressing Ctrl+U in the default KMail configuration with no keybindings readjusted, it says it is already in use. Opening the bespoken shortcuts menu, the search feature lists only this one command. This only happens in German translation. STEPS TO REPRODUCE 1. Open KMail 2. Press Ctrl+U 3. Open the keybinding menu in order to see its the only binding for Ctrl+U OBSERVED RESULT Double keybinding reported EXPECTED RESULT Keybinding is working SOFTWARE/OS VERSIONS KDE Plasma Version: 5.16.5 KDE Frameworks Version: 19.08.1 Qt Version: 5.13.0 ADDITIONAL INFORMATION Translations should be checked on this kind of error. Is there any CI or something? If not, can we do it? Also: The available versions for this product is bonkers. Not only does it name the plasma version for KMail (?) it is also outdated. Thanks a lot -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 411147] IMAP resource permanently offline "Cannot read password. User denied access to wallet"
https://bugs.kde.org/show_bug.cgi?id=411147
--- Comment #1 from Matthias Nagel ---
This is the debug console output of akonadi, if I try to toggle the
online/offline state:
org.kde.pim.akonadiserver: New notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7f29f01e1070) )
org.kde.pim.akonadiserver: Subscriber
Akonadi::Server::NotificationSubscriber(0x7f29f01e1070) identified as
"AgentBaseChangeRecorder - 94879028254112"
org.kde.pim.imapresource: online= false
org.kde.pim.imapresource: online= true
org.kde.kgapi: Bad request, Google replied ' "{\n \"error\":
\"invalid_grant\",\n \"error_description\": \"Bad Request\"\n}" '
org.kde.pim.imapresource: online= false
The interesting line is from "org.kde.kgapi". As a workaround I changed the
authentication method from Google to PLAIN and now it works again. This seems
to be a regression in libkgapi.
--
You are receiving this mail because:
You are the assignee for the bug.
[kmail2] [Bug 411147] New: IMAP resource permanently offline "Cannot read password. User denied access to wallet"
https://bugs.kde.org/show_bug.cgi?id=411147 Bug ID: 411147 Summary: IMAP resource permanently offline "Cannot read password. User denied access to wallet" Product: kmail2 Version: 5.11.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: matthias.h.na...@gmail.com Target Milestone: --- After upgrading to version 5.1.3 (kde-apps/kmail-19.04.3 in Gentoo) the IMAP resource for my Gmail IMAP account is permanently offline. When I try to restart the akonadi resource, try to toggle the online/offline state, I get the error "Cannot read password. User denied access to wallet." Then the resource turns offline again. I already have tried to re-enter the password in the settings. I also tried to entirely delete the IMAP resource and re-create it again, in case there is some odd configuration error. The error remains. Interestingly, this only happens with Gmail. I have three other IMAP accounts at different providers that all work and use Kwallet as the password storage. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.60.0 Qt Version: 5.12 -- 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 Matthias Welwarsky changed: What|Removed |Added CC||ma...@welwarsky.de -- You are receiving this mail because: You are the assignee for the bug.
[kaddressbook] [Bug 410011] New: Sfl-phone, Ring and Jami
https://bugs.kde.org/show_bug.cgi?id=410011 Bug ID: 410011 Summary: Sfl-phone, Ring and Jami Product: kaddressbook Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: shaloksha...@protonmail.ch CC: to...@kde.org Target Milestone: --- See this screenshot: https://i.imgur.com/eveoicd.png Sflphone is no more. It got renamed Ring several years ago. Then it got renamed again and it is called Jami by now. Can we adjust accordingly, assuming the API is still working? And how is that with Ekiga and Skype? They changed a lot in these times as well.. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 410010] New: Kube 0.9 release or no release?
https://bugs.kde.org/show_bug.cgi?id=410010 Bug ID: 410010 Summary: Kube 0.9 release or no release? Product: kontact Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: shaloksha...@protonmail.ch Target Milestone: --- Kube has a new version released according to their homepage and not released on Github And it has also no section here on KDE Bugs https://kube-project.com/ -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 406202] New: Kontact crashes on exit
https://bugs.kde.org/show_bug.cgi?id=406202 Bug ID: 406202 Summary: Kontact crashes on exit Product: kontact Version: 5.10.3 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: matth...@heizmann.name Target Milestone: --- Application: kontact (5.10.3) (Compiled from sources) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.27-gentoo-r1 x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: Not a new problem, occurred in preceding versions of Kontact The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe2e4c30980 (LWP 5847))] Thread 29 (Thread 0x7fe15e0bd700 (LWP 5967)): #0 0x7fe2e16950a3 in poll () from /lib64/libc.so.6 #1 0x7fe2db4ff436 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe2db4ff55c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe2e2213f1b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fe2e21c4653 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fe2e203e016 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fe2e2046f5a in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #7 0x7fe2dd40e093 in start_thread () from /lib64/libpthread.so.0 #8 0x7fe2e16a13af in clone () from /lib64/libc.so.6 Thread 28 (Thread 0x7fe178b97700 (LWP 5950)): #0 0x7fe2dd415169 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe2d2ac38d7 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fe2d2ac4e37 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fe2d2ac4f22 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fe2d2ac9fa1 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fe2d2acb529 in base::internal::SchedulerWorker::Thread::ThreadMain() () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7fe2d2ad5f41 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7fe2dd40e093 in start_thread () from /lib64/libpthread.so.0 #8 0x7fe2e16a13af in clone () from /lib64/libc.so.6 Thread 27 (Thread 0x7fe19285c700 (LWP 5894)): #0 0x7fe2e16950a3 in poll () from /lib64/libc.so.6 #1 0x7fe2db4ff436 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe2db4ff55c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe2e2213f1b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7fe2e21c4653 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7fe2e203e016 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7fe2e2046f5a in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #7 0x7fe2dd40e093 in start_thread () from /lib64/libpthread.so.0 #8 0x7fe2e16a13af in clone () from /lib64/libc.so.6 Thread 26 (Thread 0x7fe193cbc700 (LWP 5892)): #0 0x7fe2e1690990 in read () from /lib64/libc.so.6 #1 0x7fe2db544af0 in g_wakeup_acknowledge () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe2db4fef0f in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe2db4ff3e0 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #4 0x7fe2db4ff55c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7fe2e2213f1b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7fe2e21c4653 in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7fe2e203e016 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7fe2e2046f5a in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #9 0x7fe2dd40e093 in start_thread () from /lib64/libpthread.so.0 #10 0x7fe2e16a13af in clone () from /lib64/libc.so.6 Thread 25 (Thread 0x7fe1a67c8700 (LWP 5876)): #0 0x7fe2e16b057b in __lll_lock_wait_private () from /lib64/libc.so.6 #1 0x7fe2e16b274c in __fprintf_chk () from /lib64/libc.so.6 #2 0x7fe2c8e62ff0 in event_logv_.part () from /usr/lib64/libevent-2.1.so.6 #3 0x7fe2c8e631dc in event_warn () from /usr/lib64/libevent-2.1.so.6 #4 0x7fe2c8e648e4 in epoll_dispatch () from /usr/lib64/libevent-2.1.so.6 #5 0x7fe2c8e5a6d5 in event_base_loop () from /usr/lib64/libevent-2.1.so.6 #6
[Akonadi] [Bug 380012] CalDAV-sync not working with Communigate
https://bugs.kde.org/show_bug.cgi?id=380012 --- Comment #4 from Matthias Mueller --- just found seemingly related: https://phabricator.kde.org/D8843 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 380012] CalDAV-sync not working with Communigate
https://bugs.kde.org/show_bug.cgi?id=380012 Matthias Mueller changed: What|Removed |Added CC||saldo...@mailbox.org --- Comment #3 from Matthias Mueller --- can confirm behaviour (CalDAV and CardDAV) on a Mailbox.org server with KAddressBook/KOrganizer Version 5.10.1 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #127 from Matthias Kretz --- The fact that I can have an inconsistent state stored in my Akonadi DB is telling. Apparently, while clients interact with Akonadi, the DB goes through inconsistent states. Those appear to be open to races, and unfortunate interrupts (crash, system hang, power loss). What I'd do (and I'm guessing from a far away distance in the hopes it helps inspire a real fix, hoping not to step on any toes): 1. Update the DB schema to enforce consistent state. In particular all foreign keys need to be defined so that it's impossible to DELETE FROM parttable while something in pimitemtable still holds a key to it. 2. Presumably this will break clients which rely on the DB to allow inconsistent intermediate states. DB updates therefore need to be fixed to atomically go from one consistent state to the next. E.g. use DELETE together with INNER JOIN. 3. Races like "unread -> read -> unread" need to be guarded against via compare-exchange atomic operations using some modification counter. E.g. mailcheck create id=X, state=unread kmail read id=X, state=unread kmail write state=read WHERE id=X mailcheck update id=X, state=unread (why would this happen anyway, can the IMAP server indicate some update of metadata?) If we add a version the UPDATE could be predicated on the version column still storing the same value as when it was SELECTED before. E.g. the mail client does `UPDATE foo SET state=read WHERE id=X AND version=1` instead of `UPDATE foo SET state=read WHERE id=X`. I actually expect Akonadi already has such a facility and Allans guess is incorrect. I have another guess from looking at my logs. I have lots of: org.kde.pim.akonadiserver: DB error: "Lock wait timeout exceeded; try restarting transaction" org.kde.pim.akonadiserver: Error text: "Lock wait timeout exceeded; try restarting transaction QMYSQL3: Unable to execute statement" I.e. KMail updates the UI to read state, tries to reflect the state change with Akonadi, but the DB is locked up. The UPDATE fails, and the KMail UI reverts to the state stored in Akonadi. These locks might also be the reason why inconsistent entries in tables remain. A first DELETE goes through, the second (to make it consistent again) times out. I have no clue where the locks come from though. One data point: After my DELETE FROM statement above I've not seen a single DB error message about lock timeouts again. Before I had lots. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #123 from Matthias Kretz --- (In reply to Allan Sandfeld from comment #122) > With my patch in place the duplicates can be removed by simply calling > "remove duplicates" from KMail. "Folder -> Remove Duplicates"? If that removes stales in the pimitemtable it's somewhat misleadingly named. I was expecting it to search for copies of the same mail (i.e. different local & remote ID but equal payload data). -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 Matthias Kretz changed: What|Removed |Added CC||kr...@kde.org --- Comment #121 from Matthias Kretz --- I'm fed up with wiping my Akonadi data every other month so I'm trying to once again to understand the cause or find a workaround. Anyway, I was following the SQL hints on debugging the state of my Akonadi data and found three instances of duplicated (well, rather "multiplicated") pimitemtable.remoteIds, on the order of hundreds of different pimitemtable.ids. I then tried to find the corresponding data in parttable via INNER JOIN parttable ON pimitemtable.id = parttable.pimItemId. Interestingly enough there's a single pimitemtable.id per pimitemtable.remoteId left (with three different parttable.id per pimitemtable.id, which seems to be correct for normal entries). So it seems there are stale entries in pimitemtable. The query SELECT pimitemtable.*, collectiontable.name FROM pimitemtable INNER JOIN collectiontable ON pimitemtable.collectionId = collectiontable.id LEFT JOIN parttable ON pimitemtable.id = parttable.pimItemId WHERE parttable.id IS NULL lists the same remoteIds that the query looking for dups found, minus the ones that have a match in parttable. Useful information: there are no additional stale entries in pimitemtable than the dups. Next step, I tried to remove the stale entries in pimitemtable with the following query: DELETE pimitemtable FROM pimitemtable LEFT JOIN parttable ON pimitemtable.id = parttable.pimItemId WHERE parttable.id IS NULL However, the query hangs akonadiconsole for ~1 minute and then returns "Lock wait timeout exceeded; try restarting transaction QMYSQL: Unable to execute query". An `akonadictl restart` in this case did the trick and the query then got through. All dups gone. In any case the hangs on reading mails in KMail that I experienced since yesterday are gone. Let's see whether it helps. Maybe the DELETE query is a useful addition to `akonadictl fsck` until the root cause can be fixed? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[kontact] [Bug 403417] New: kontact crashed after akonadictl restart
https://bugs.kde.org/show_bug.cgi?id=403417 Bug ID: 403417 Summary: kontact crashed after akonadictl restart Product: kontact Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: matth...@heizmann.name Target Milestone: --- Application: kontact (5.9.3) (Compiled from sources) Qt Version: 5.11.3 Frameworks Version: 5.52.0 Operating System: Linux 4.19.14-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: I executed akonadictl restart - Unusual behavior I noticed: akonadiserver was consuming 25% of my memory -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4e1647f800 (LWP 24877))] Thread 34 (Thread 0x7f4c94b3b700 (LWP 18812)): #0 0x7f4e0ce10ea4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #1 0x7f4e0cdcaf96 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7f4e0cdcb0ec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f4e13a7a12b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f4e13a2611a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f4e13888aea in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f4e1389254f in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #7 0x7f4e0ecc396a in start_thread () from /lib64/libpthread.so.0 #8 0x7f4e12f0c1af in clone () from /lib64/libc.so.6 Thread 33 (Thread 0x7f4cacbc4700 (LWP 18811)): #0 0x7f4e12f005d3 in poll () from /lib64/libc.so.6 #1 0x7f4e0cdcafd9 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #2 0x7f4e0cdcb0ec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f4e13a7a12b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f4e13a2611a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f4e13888aea in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f4e1389254f in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #7 0x7f4e0ecc396a in start_thread () from /lib64/libpthread.so.0 #8 0x7f4e12f0c1af in clone () from /lib64/libc.so.6 Thread 32 (Thread 0x7f4cc3dba700 (LWP 18787)): #0 0x7f4e0ecca8aa in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4e0445e8d7 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f4e0445fe37 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f4e0445ff22 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f4e04464fa1 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f4e0446633f in base::internal::SchedulerWorker::Thread::ThreadMain() () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f4e04470f41 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f4e0ecc396a in start_thread () from /lib64/libpthread.so.0 #8 0x7f4e12f0c1af in clone () from /lib64/libc.so.6 Thread 31 (Thread 0x7f4cbaf13700 (LWP 18786)): #0 0x7f4e0ecca8aa in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4e0445e8d7 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f4e0445fe37 in base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f4e0445ff22 in base::WaitableEvent::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f4e04464fa1 in base::internal::SchedulerWorker::Delegate::WaitForWork(base::WaitableEvent*) () from /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f4e04466529 in base::internal::SchedulerWorker::Thread::ThreadMain() () from /usr/lib64/libQt5WebEngineCore.so.5 #6 0x7f4e04470f41 in base::(anonymous namespace)::ThreadFunc(void*) () from /usr/lib64/libQt5WebEngineCore.so.5 #7 0x7f4e0ecc396a in start_thread () from /lib64/libpthread.so.0 #8 0x7f4e12f0c1af in clone () from /lib64/libc.so.6 Thread 30 (Thread 0x7f4cdb7fe700 (LWP 18785)): #0 0x7f4e0ecca8aa in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4e0445e8d7 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () from /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f4e0445fe37 in
[kmail2] [Bug 362493] quoting with blockquote
https://bugs.kde.org/show_bug.cgi?id=362493 Matthias Nagel changed: What|Removed |Added CC||matthias.h.na...@gmail.com --- Comment #1 from Matthias Nagel --- I am in support of this feature. If this feature is implemented, I would prefer to have not only for replying or relaying other mails but also to be able to insert custom with the tool bar. I often discuss 3rd party literature via mail and having a feature like this would help to distinguish between my own text and the citation. There is a loosely related feature request that asks for real left indention of paragraphs without unintentionally creating a bullet list. See bug #341961. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 388149] New: Kmail crash 5min after start
https://bugs.kde.org/show_bug.cgi?id=388149 Bug ID: 388149 Summary: Kmail crash 5min after start Product: kmail2 Version: 5.6.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: m...@fuckl.de Target Milestone: --- Application: kmail (5.6.3) Qt Version: 5.9.2 Frameworks Version: 5.40.0 Operating System: Linux 4.14.7-300.fc27.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: Kmail crashes every time 5min after I start it. In this 5min I can do what I like, everything seems to work just fine. But after 5min it crashes... The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb38cb0d340 (LWP 4237))] Thread 26 (Thread 0x7fb2435f6700 (LWP 4301)): #0 0x7fb382376c4b in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb37984ee85 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () at /lib64/libQt5WebEngineCore.so.5 #2 0x7fb37984f367 in base::SequencedWorkerPool::Worker::Run() () at /lib64/libQt5WebEngineCore.so.5 #3 0x7fb379850101 in base::SimpleThread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #4 0x7fb37984c7cb in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #5 0x7fb382370619 in start_thread () at /lib64/libpthread.so.0 #6 0x7fb3864568bf in clone () at /lib64/libc.so.6 Thread 25 (Thread 0x7fb2c3fff700 (LWP 4300)): #0 0x7fb382376c4b in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fb36783b604 in QTWTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5Script.so.5 #2 0x7fb36783b649 in () at /lib64/libQt5Script.so.5 #3 0x7fb382370619 in start_thread () at /lib64/libpthread.so.0 #4 0x7fb3864568bf in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7fb2ca4a3700 (LWP 4287)): #0 0x7fb38644a30b in poll () at /lib64/libc.so.6 #1 0x7fb3711d0ed9 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7fb3711d0fec in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7fb3872b535b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7fb3872630ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7fb3870b48ba in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7fb3870b8b92 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #7 0x7fb382370619 in start_thread () at /lib64/libpthread.so.0 #8 0x7fb3864568bf in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7fb300ff9700 (LWP 4275)): #0 0x7fb38644a30b in poll () at /lib64/libc.so.6 #1 0x7fb365d796f1 in poll_func () at /lib64/libpulse.so.0 #2 0x7fb365d6b0b0 in pa_mainloop_poll () at /lib64/libpulse.so.0 #3 0x7fb365d6b740 in pa_mainloop_iterate () at /lib64/libpulse.so.0 #4 0x7fb365d6b7d0 in pa_mainloop_run () at /lib64/libpulse.so.0 #5 0x7fb365d79639 in thread () at /lib64/libpulse.so.0 #6 0x7fb3637b3ac8 in internal_thread_func () at /usr/lib64/pulseaudio/libpulsecommon-11.1.so #7 0x7fb382370619 in start_thread () at /lib64/libpthread.so.0 #8 0x7fb3864568bf in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7fb3017fa700 (LWP 4274)): #0 0x7fb38644592b in write () at /lib64/libc.so.6 #1 0x7fb3863c23fd in _IO_new_file_write () at /lib64/libc.so.6 #2 0x7fb3863c2d9f in __GI__IO_file_xsputn () at /lib64/libc.so.6 #3 0x7fb386395c17 in buffered_vfprintf () at /lib64/libc.so.6 #4 0x7fb386392c56 in vfprintf () at /lib64/libc.so.6 #5 0x7fb386467206 in __fprintf_chk () at /lib64/libc.so.6 #6 0x7fb36ada63e0 in _warn_helper () at /lib64/libevent-2.0.so.5 #7 0x7fb36ada65a4 in event_warn () at /lib64/libevent-2.0.so.5 #8 0x7fb36adaad40 in epoll_dispatch () at /lib64/libevent-2.0.so.5 #9 0x7fb36ad958de in event_base_loop () at /lib64/libevent-2.0.so.5 #10 0x7fb37981fcb9 in base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () at /lib64/libQt5WebEngineCore.so.5 #11 0x7fb37981bf88 in base::MessageLoop::RunHandler() () at /lib64/libQt5WebEngineCore.so.5 #12 0x7fb3798389cb in base::RunLoop::Run() () at /lib64/libQt5WebEngineCore.so.5 #13 0x7fb3798506c6 in base::Thread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #14 0x7fb37984c7cb in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #15 0x7fb382370619 in start_thread () at /lib64/libpthread.so.0 #16 0x7fb3864568bf in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7fb301ffb700 (LWP 4273)): #0 0x7fb382376c4b in pthread_cond_wait@@GLIBC_2.3.2 () at
[kmail2] [Bug 323900] Page-margins in KDE-printer-settings
https://bugs.kde.org/show_bug.cgi?id=323900 matth...@hiltpold.ch <matth...@hiltpold.ch> changed: What|Removed |Added CC||matth...@hiltpold.ch --- Comment #1 from matth...@hiltpold.ch <matth...@hiltpold.ch> --- Hello my wish is, that Marco's 'ideal thing' "set the margins for printing e-mails and other things to work with to 10 mm at the top, the bottom an the right/outer margin. The left/inner margin should be 20 mm by default, because the pages get perforated." is soon accepted and realized. Thank you Matthias -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 --- Comment #2 from Jan-Matthias Braun <jan_br...@gmx.net> --- For another account using SMTP, I am seeing another error in the notification widget. Instead of getting a "1", as for the original report, I am seeing "Serverfehler", the German translation of Server error, in the notification window, but unluckily no debug output in the terminal. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 --- Comment #1 from Jan-Matthias Braun <jan_br...@gmx.net> --- Further tests with another account revealed, that sending via the EWS resource works. So does sending via a local mail dispatcher, like ssmtp or nullmailer. Although akonadi/kmail2 seems to run into problems with sendmail compatibility issues of those. -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added Severity|normal |grave -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 387926] New: Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 Bug ID: 387926 Summary: Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1 Product: Akonadi Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Mail Dispatcher Agent Assignee: kdepim-bugs@kde.org Reporter: jan_br...@gmx.net Target Milestone: --- When trying to send an e-Mail since trying out the 17.12 pre-releases, I am unable to send e-Mails. In the official release, I have now recreated the SMTP but the problem persists, no mail gets out. The only debug message I am seeing after enabling diverse output in kdebugdialog5 is org.kde.pim.ksmtp: Socket error: 1 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 362817] Kontact crash on open addressbook from the email window
https://bugs.kde.org/show_bug.cgi?id=362817 --- Comment #16 from Matthias Kretz <kr...@kde.org> --- FWIW, I'm on KMail/Kontact 5.5.3, akonadiserver 5.5.3, KDE neon User Edition 5.10, and I'm not seeing the crash anymore. I have not replaced config files, Mail storage, or anything else. Just regular updates through KDE neon. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 364670] kmail crash on search
https://bugs.kde.org/show_bug.cgi?id=364670
--- Comment #8 from Jan-Matthias Braun <jan_br...@gmx.net> ---
Created attachment 106677
--> https://bugs.kde.org/attachment.cgi?id=106677=edit
New crash information added by DrKonqi
kontact (5.5.3) using Qt 5.7.1
I was entering a search term in a mail folder. I am unsure if I have pressed
the enter button, but in general the procedure seems like the one layed out
above.
Distribution: Gentoo with standard buld flags ("-O2 -march=native").
-- Backtrace (Reduced):
#8 0x7f7fdef72cad in __gnu_cxx::__verbose_terminate_handler () at
/var/tmp/portage/sys-devel/gcc-6.3.0/work/gcc-6.3.0/libstdc++-v3/libsupc++/vterminate.cc:95
#9 0x7f7fdef70a16 in __cxxabiv1::__terminate (handler=) at
/var/tmp/portage/sys-devel/gcc-6.3.0/work/gcc-6.3.0/libstdc++-v3/libsupc++/eh_terminate.cc:47
#10 0x7f7fdef70a61 in std::terminate () at
/var/tmp/portage/sys-devel/gcc-6.3.0/work/gcc-6.3.0/libstdc++-v3/libsupc++/eh_terminate.cc:57
#11 0x7f7fdef70c79 in __cxxabiv1::__cxa_throw (obj=obj@entry=0x54eae90,
tinfo=0x7f7fdf0b2890 , dest=0x7f7fdef86cb0
<std::logic_error::~logic_error()>) at
/var/tmp/portage/sys-devel/gcc-6.3.0/work/gcc-6.3.0/libstdc++-v3/libsupc++/eh_throw.cc:87
#12 0x7f7fdef9b73f in std::__throw_logic_error (__s=0x7f7ed88afd28
"basic_string::_M_construct null not valid") at
/var/tmp/portage/sys-devel/gcc-6.3.0/work/gcc-6.3.0/libstdc++-v3/src/c++11/functexcept.cc:74
--
You are receiving this mail because:
You are the assignee for the bug.
[kontact] [Bug 364670] kmail crash on search
https://bugs.kde.org/show_bug.cgi?id=364670 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added CC||jan_br...@gmx.net -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367998] quick-search field does not receive some keys
https://bugs.kde.org/show_bug.cgi?id=367998 --- Comment #4 from Jan-Matthias Braun <jan_br...@gmx.net> --- (In reply to Jan-Matthias Braun from comment #3) > 2. Whenever I enter text into the search field, right after updating the > message list, the focus seems to go to the mail view, too. Of course, any > keystrokes won't go to the search field anymore. This is similar to the > original problem here and can be reproduced reliably without any folder > change. When there is no mail displayed in the message view, e.g., one of akonadi's i-m-not-serving-any-requests-periods, then the focus won't leave the search field. -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case
https://bugs.kde.org/show_bug.cgi?id=222878 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added CC||jan_br...@gmx.net --- Comment #37 from Jan-Matthias Braun <jan_br...@gmx.net> --- And another (rather short) one for kontact 16.12.0 (gdb) bt #0 0x7f15af07199d in poll () from /lib64/libc.so.6 #1 0x7f15a8041266 in g_main_context_iterate.isra.42.lto_priv () from /usr/lib64/libglib-2.0.so.0 #2 0x7f15a7fc8a3c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f15acd8e7af in QEventDispatcherGlib::processEvents (this=0x1236fd0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #4 0x7f15acd3a7ba in QEventLoop::exec (this=this@entry=0x7fffa171af30, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f15acd42bfd in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1261 #6 0x00404203 in main (argc=, argv=) at /var/tmp/portage/kde-apps/kontact-16.12.0/work/kontact-16.12.0/src/main.cpp:227 Cheers, Jan -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 367998] quick-search field does not receive some keys
https://bugs.kde.org/show_bug.cgi?id=367998 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added CC||jan_br...@gmx.net --- Comment #3 from Jan-Matthias Braun <jan_br...@gmx.net> --- Hi! I am not sure, if this really is the same problem, but as I see it, I do see a general problem with the focus strategy. :-) 1. Whenever I select an e-Mail, the mail view is focused. This means, that actions like delete don't work anymore. Only when I select an e-Mail a second time, things are back to normal and the focus stays in the message list. 2. Whenever I enter text into the search field, right after updating the message list, the focus seems to go to the mail view, too. Of course, any keystrokes won't go to the search field anymore. This is similar to the original problem here and can be reproduced reliably without any folder change. The description of where the focus goes has been derived from ticking shift-tab until I was back at the search field. Assuming "Search Field" - "Message List" - "Message View" tab order. I.e., I went back and forth to see where the focus has ended up. My kde installation is up to date. I.e., kmail 16.12.0, plasma 5.8.5, and frameworks 5.29. The patch noted in Comment 1 is already applied, as far as I can see. I am not sure, when this started. Probably with the qtwebengine version? Does the mail view now focus itself? I really like kmail, so thanks for looking into this! -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 362817] Kontact crash on open addressbook from the email window
https://bugs.kde.org/show_bug.cgi?id=362817 Matthias Kretz <kr...@kde.org> changed: What|Removed |Added CC||kr...@kde.org --- Comment #6 from Matthias Kretz <kr...@kde.org> --- I can reproduce the issue every time I do: * open composer * press "Select" button for To/CC/BCC address * crash. kmail, kontact, and akonadiserver report version 5.4.0 (I have a KDE neon User Edition 5.8 installation). -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372022] kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2.
https://bugs.kde.org/show_bug.cgi?id=372022 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #6 from Jan-Matthias Braun <jan_br...@gmx.net> --- (In reply to Jan-Matthias Braun from comment #5) > Update: I recompiled with "-fno-delete-null-pointer-checks -fno-lifetime-dse > -fno-schedule-insns2", but the crash still happens. Yeah, looks like I did not rccompile with these CFLAGS. Now I did and it looks quite a lot better. qtwebengine is still using wrong CFLAGS for gcc 6. :-( -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 372034] Kontact crashes with segmentation fault when a mail from the message list is selected
https://bugs.kde.org/show_bug.cgi?id=372034 --- Comment #2 from Matthias Nagel <matthias.h.na...@gmail.com> --- Some snippet from .xsession-error: kontact: /var/tmp/portage/x11-libs/libdrm-2.4.70/work/libdrm-2.4.70/nouveau/pushbuf.c:727: nouveau_pushbuf_data: Assertion »kref« failed. *** KMail got signal 6 (Exiting) *** Dead letters dumped. [1105/184917:ERROR:gles2_cmd_decoder.cc(2109)] [.CommandBufferContext.RenderWorker-0x1a44370]GL ERROR :GL_OUT_OF_MEMORY : ScopedTextureBinder::dtor: <- error from previous GL command [1105/184917:ERROR:gles2_cmd_decoder.cc(4471)] Error: 5 for Command kCopySubTextureCHROMIUM [1105/184917:ERROR:gles2_cmd_decoder.cc(3579)] GLES2DecoderImpl: Trying to make lost context current. KCrash: Application 'kontact' crashing... -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 372034] Kontact crashes with segmentation fault when a mail from the message list is selected
https://bugs.kde.org/show_bug.cgi?id=372034 --- Comment #1 from Matthias Nagel <matthias.h.na...@gmail.com> --- This is the dmesg output: [ 61.624346] nouveau :01:00.0: kontact[1214]: Unknown handle 0x0017 [ 61.624355] nouveau :01:00.0: kontact[1214]: validate_init [ 61.624359] nouveau :01:00.0: kontact[1214]: validate: -2 [ 64.845955] nouveau :01:00.0: kontact[1214]: Unknown handle 0x0014 [ 64.845966] nouveau :01:00.0: kontact[1214]: validate_init [ 64.845971] nouveau :01:00.0: kontact[1214]: validate: -2 -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 372034] Kontact crashes with segmentation fault when a mail from the message list is selected
https://bugs.kde.org/show_bug.cgi?id=372034 Matthias Nagel <matthias.h.na...@gmail.com> changed: What|Removed |Added Summary|Kontact crashes with|Kontact crashes with |segmentation fault when a |segmentation fault when a |mail from the message list |mail from the message list ||is selected -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 372034] New: Kontact crashes with segmentation fault when a mail from the message list
https://bugs.kde.org/show_bug.cgi?id=372034 Bug ID: 372034 Summary: Kontact crashes with segmentation fault when a mail from the message list Product: kontact Version: 5.3.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: matthias.h.na...@gmail.com Target Milestone: --- Created attachment 102012 --> https://bugs.kde.org/attachment.cgi?id=102012=edit Backtrace Qt Version: 5.7.0 Frameworks Version: 5.26.0 Operating System: Linux 4.4.26-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: Select a mail from the message list. Kontact tries to show the mail in the preview window below the message list. Kontact crashes. After that I experience a lot of display flicker and disturbances across the whole desktop and other applications (for example in Firefox). Plasma Desktop effects do not work as expected anymore. Therefore I believe the bug is somehow related to the graphics stack. The crash can be reproduced sometimes. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372022] kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2.
https://bugs.kde.org/show_bug.cgi?id=372022 --- Comment #5 from Jan-Matthias Braun <jan_br...@gmx.net> --- Update: I recompiled with "-fno-delete-null-pointer-checks -fno-lifetime-dse -fno-schedule-insns2", but the crash still happens. Then I took a look at kdepim git and found at, that there is a KF5WebEngineViewerConfig in the works. So it looks like everything will change in git, right? -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372022] kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2.
https://bugs.kde.org/show_bug.cgi?id=372022 --- Comment #4 from Jan-Matthias Braun <jan_br...@gmx.net> --- In a side-note, the secondary crash happens when grabbing selected text: #0 0x7fffeedae224 in QtWebEngineCore::WebContentsAdapter::selectedText() const () from /usr/lib64/libQt5WebEngineCore.so.5 #1 0x760eb321 in QWebEnginePage::selectedText() const () from /usr/lib64/libQt5WebEngineWidgets.so.5 #2 0x760f8547 in QWebEngineView::selectedText() const () from /usr/lib64/libQt5WebEngineWidgets.so.5 #3 0x7fff027e5991 in MessageViewer::Viewer::selectedText() const (this=) at /var/tmp/portage/kde-apps/messagelib-16.08.2/work/messagelib-16.08.2/messageviewer/src/viewer/viewer.cpp:248 #4 0x7fff02e78600 in KMReaderWin::copyText() const (this=) at /var/tmp/portage/kde-apps/kmail-16.08.2/work/kdepim-16.08.2/kmail/src/kmreaderwin.cpp:399 #5 0x7fff02ed0508 in KMail::MessageActions::replyCommand (this=0x3bd4fc0, strategy=MessageComposer::ReplySmart) at /var/tmp/portage/kde-apps/kmail-16.08.2/work/kdepim-16.08.2/kmail/src/messageactions.cpp:477 #6 0x76ef3d1c in QtPrivate::QSlotObjectBase::call (a=0x7fffc930, r=0x3bd4fc0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:130 #7 QMetaObject::activate (sender=0x3bd0160, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3723 #8 0x77a4dea2 in QAction::triggered(bool) () from /usr/lib64/libQt5Widgets.so.5 #9 0x77a539ff in QAction::activate(QAction::ActionEvent) () from /usr/lib64/libQt5Widgets.so.5 #10 0x77a53aec in QAction::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #11 0x77a5c32c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #12 0x77a61739 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #13 0x76ec8f18 in QCoreApplication::notifyInternal2 (receiver=0x3bd0160, event=event@entry=0x7fffcc00) at kernel/qcoreapplication.cpp:988 #14 0x7723ef96 in QCoreApplication::sendEvent (event=0x7fffcc00, receiver=) at /usr/include/qt5/QtCore/qcoreapplication.h:231 #15 QShortcutMap::dispatchEvent (this=this@entry=0x449968, e=e@entry=0x7fffccb0) at kernel/qshortcutmap.cpp:674 #16 0x7723f069 in QShortcutMap::tryShortcut (this=this@entry=0x449968, e=e@entry=0x7fffccb0) at kernel/qshortcutmap.cpp:351 #17 0x771fad5f in QWindowSystemInterface::handleShortcutEvent (window=, window@entry=0xca8120, timestamp=, keyCode=82, modifiers=..., nativeScanCode=27, nativeVirtualKey=114, nativeModifiers=0, text=..., autorepeat=false, count=1) at kernel/qwindowsysteminterface.cpp:235 #18 0x77210fcc in QGuiApplicationPrivate::processKeyEvent (e=0x419f800) at kernel/qguiapplication.cpp:2008 #19 0x77216285 in QGuiApplicationPrivate::processWindowSystemEvent (e=e@entry=0x419f800) at kernel/qguiapplication.cpp:1699 #20 0x771f596b in QWindowSystemInterface::sendWindowSystemEvents (flags=...) at kernel/qwindowsysteminterface.cpp:654 #21 0x7fffe7a26900 in userEventSourceDispatch (source=) at eventdispatchers/qeventdispatcher_glib.cpp:76 #22 0x74a6bd17 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #23 0x74a6c788 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #24 0x74a6c91c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #25 0x76f1aeef in QEventDispatcherGlib::processEvents (this=0x4bb6d0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #26 0x76ec704a in QEventLoop::exec (this=this@entry=0x7fffd010, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #27 0x76ecf48d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1261 #28 0x004042c3 iat /var/tmp/portage/kde-apps/kontact-16.08.2/work/kdepim-16.08.2/kontact/src/main.cpp:223 n main (argc=, argv=) -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372022] kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2.
https://bugs.kde.org/show_bug.cgi?id=372022 --- Comment #3 from Jan-Matthias Braun <jan_br...@gmx.net> --- Looking at the stack trace again, I just remembered that v8 has problems with gcc 6 due to programming practices. I am recompiling qtwebengine with appropriate compiler flags to check if this is the underlying problem here... -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372022] kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2.
https://bugs.kde.org/show_bug.cgi?id=372022 --- Comment #2 from Jan-Matthias Braun <jan_br...@gmx.net> --- Sorry for being incoherent: I am using qt 5.7.0, plasma 5.8.3, kde apps 16.08.2, and frameworks 5.27. The compiler is gcc 6.2.0. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372022] kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2.
https://bugs.kde.org/show_bug.cgi?id=372022 --- Comment #1 from Jan-Matthias Braun <jan_br...@gmx.net> --- Side note: For all messages I see this error message in the logs: js: Uncaught ReferenceError: qt is not defined js: Uncaught ReferenceError: qt is not defined js: Uncaught ReferenceError: qt is not defined but it does not seem to interrupt kmail. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 372022] New: kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2.
https://bugs.kde.org/show_bug.cgi?id=372022 Bug ID: 372022 Summary: kmail2: message is displayed and blanked after short delay. Mail actions then crash kmail2. Product: kmail2 Version: 5.3.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: UI Assignee: kdepim-bugs@kde.org Reporter: jan_br...@gmx.net Target Milestone: --- When selecting a mail in message view, the message is displayed and then disappears after a variable delay. Changing to another mail and then back does not triggering this behaviour. The disappearing message happens in the embedded message view as well as in an extra window (after double clicking the message). If the mail display is blank and I trigger any message related, e.g., reply, forward, delete, kmail crashes. But if I redisplay the message and do the same action while the display is intact, everything will work fine. Nonetheless, this mail focuses on the disappearing of the displayed mail. I see the following backtrace, which seems to lead into the depths of QtWebEngine. Received signal 11 SEGV_MAPERR 0008 #0 0x74cb3b3e base::debug::StackTrace::StackTrace() #1 0x74cb3c2b base::debug::(anonymous namespace)::StackDumpSignalHandler() #2 0x722cc2b0 #3 0x733785b0 v8::internal::IncrementalMarking::ActivateIncrementalWriteBarrier() #4 0x733787e7 v8::internal::IncrementalMarking::StartMarking() #5 0x73378943 v8::internal::IncrementalMarking::Start() #6 0x7368ac9f v8::internal::MemoryReducer::TimerTask::RunInternal() #7 0x74d46869 base::debug::TaskAnnotator::RunTask() #8 0x7541b323 scheduler::TaskQueueManager::ProcessTaskFromWorkQueue() #9 0x7541bda0 scheduler::TaskQueueManager::DoWork() #10 0x74d46869 base::debug::TaskAnnotator::RunTask() #11 0x74cd79d5 base::MessageLoop::RunTask() #12 0x74cd99ab base::MessageLoop::DoDelayedWork() #13 0x74cdaaaf base::MessagePumpDefault::Run() #14 0x74cefffd base::RunLoop::Run() #15 0x74cd6f65 base::MessageLoop::Run() #16 0x74a07baf content::RendererMain() #17 0x73dc4cdb content::RunZygote() #18 0x73dc5034 content::ContentMainRunnerImpl::Run() #19 0x73dc34e1 content::ContentMain() #20 0x7311d514 QtWebEngine::processMain() #21 0x00400703 main #22 0x722b9681 __libc_start_main #23 0x00400749 _start What additional information can I provide? Jan -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 371859] Segfault of kmail when removing a mail
https://bugs.kde.org/show_bug.cgi?id=371859 --- Comment #3 from Jan-Matthias Braun <jan_br...@gmx.net> --- (In reply to Michael.Calmer from comment #2) > (In reply to Jan-Matthias Braun from comment #1) > > I do have a question. I am experiencing problems with current QtWebEngine > > based kmail too: Sometimes, the mail display will become empty after a short > > delay. Changing to another mail and then back has a slight chance of not > > triggering this behaviour. If the mail display is blank and I trigger any > > message related, e.g., reply, forward, delete, kmail crashes. > > My crash happens not only while removing a mail. action, I wanted to write: any nessage releted action. ^^ > > But if I redisplay the message and do the same action while the display is > > intact, everything will work fine. > > Well, I cannot make the message visible. "redisplay" is not really working > for me. So you never see the message? I can at least see it shortly before it vanishes... > > Do you observe similar behaviour? Or should I file a new bug. > > Sounds a bit similar to what I see. > > > My backtrace hints to QtWebEngine. But unfortunately, I am using > > self-compiled qt 5.7 and the debug build for QtWebEngine is exhausting my > > disk space, i.e., my backtrace is worthless. > > I also saw other bugreports which point to this component together with the > use of the "nouveau" driver. I am using an up-to-date proprietary nvidia driver. I will try to get some useful debug information. -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 371859] Segfault of kmail when removing a mail
https://bugs.kde.org/show_bug.cgi?id=371859 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added CC||jan_br...@gmx.net --- Comment #1 from Jan-Matthias Braun <jan_br...@gmx.net> --- Hi Michael, I do have a question. I am experiencing problems with current QtWebEngine based kmail too: Sometimes, the mail display will become empty after a short delay. Changing to another mail and then back has a slight chance of not triggering this behaviour. If the mail display is blank and I trigger any message related, e.g., reply, forward, delete, kmail crashes. But if I redisplay the message and do the same action while the display is intact, everything will work fine. Do you observe similar behaviour? Or should I file a new bug. My backtrace hints to QtWebEngine. But unfortunately, I am using self-compiled qt 5.7 and the debug build for QtWebEngine is exhausting my disk space, i.e., my backtrace is worthless. Cheers, Jan -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 369651] New: kmail crashes at start
https://bugs.kde.org/show_bug.cgi?id=369651 Bug ID: 369651 Summary: kmail crashes at start Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: matthias.kopczyn...@gmx.de Application: kmail (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.7.4-2-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: kmail crashes at start or short time after the program started but at the latest on the first user interaction. This prevents using the program completely. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcada17f940 (LWP 21919))] Thread 34 (Thread 0x7fca01926700 (LWP 24034)): #0 0x7fcaccdc210f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fcac32a8d49 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7fcac32a9460 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7fcac32a9630 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7fcac32a623d in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7fcaccdbc454 in start_thread () at /lib64/libpthread.so.0 #6 0x7fcad6f323ff in clone () at /lib64/libc.so.6 Thread 33 (Thread 0x7fca02956700 (LWP 24013)): #0 0x7fcaccdc210f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fcabdd6a7e4 in () at /usr/lib64/libQt5Script.so.5 #2 0x7fcabdd6a829 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fcaccdbc454 in start_thread () at /lib64/libpthread.so.0 #4 0x7fcad6f323ff in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7fca03bc2700 (LWP 23994)): #0 0x7fcacc595d33 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #1 0x7fcacc59679b in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fcacc59698c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fcad7a68aab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fcad7a106fa in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fcad78363c3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fcad783b2e8 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fcaccdbc454 in start_thread () at /lib64/libpthread.so.0 #8 0x7fcad6f323ff in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7fca14b9d700 (LWP 22453)): #0 0x7fcacc5dbea4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fcacc59671d in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fcacc59698c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fcad7a68aab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fcad7a106fa in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fcad78363c3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fcad783b2e8 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fcaccdbc454 in start_thread () at /lib64/libpthread.so.0 #8 0x7fcad6f323ff in clone () at /lib64/libc.so.6 Thread 30 (Thread 0x7fca173ee700 (LWP 22001)): #0 0x7fcad6f296ed in poll () at /lib64/libc.so.6 #1 0x7fcacc596876 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fcacc59698c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fcad7a68aab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fcad7a106fa in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fcad78363c3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fcad783b2e8 in () at /usr/lib64/libQt5Core.so.5 #7 0x7fcaccdbc454 in start_thread () at /lib64/libpthread.so.0 #8 0x7fcad6f323ff in clone () at /lib64/libc.so.6 Thread 29 (Thread 0x7fca17bef700 (LWP 21994)): #0 0x7fcacc5dbe89 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fcacc5958a4 in g_main_context_release () at /usr/lib64/libglib-2.0.so.0 #2 0x7fcacc59682a in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fcacc59698c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fcad7a68aab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fcad7a106fa in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fcad78363c3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fcad783b2e8 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fcaccdbc454 in start_thread () at /lib64/libpthread.so.0 #9 0x7fcad6f323ff in clone () at /lib64/libc.so.6 Thread 28 (Thread 0x7fca1f7fd700 (LWP 21987)): #0 0x7fcaccdc210f in pthread_cond_wait@@GLIBC_2.3.2 () at
[kmail2] [Bug 286703] Kmail2 makes multiple (>30) duplicates of new, unread mails from IMAP account.
https://bugs.kde.org/show_bug.cgi?id=286703 Matthias Mailänder <matth...@mailaender.name> changed: What|Removed |Added CC|matth...@mailaender.name| -- You are receiving this mail because: You are the assignee for the bug.
[kontact] [Bug 368186] New: Kontact crashes when displaying content of message or akregator news
https://bugs.kde.org/show_bug.cgi?id=368186 Bug ID: 368186 Summary: Kontact crashes when displaying content of message or akregator news Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: matz.fu...@gmx.at Application: kontact (5.3.0 (QtWebEngine)) Qt Version: 5.6.1 Frameworks Version: 5.25.0 Operating System: Linux 4.7.2-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: I clicked on a message in the message list (to show its content in widget below). The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f28389d0940 (LWP 2672))] Thread 33 (Thread 0x7f26e3baa700 (LWP 2752)): #0 0x7f283123509f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f28289a4129 in () at /usr/lib64/libQt5WebEngineCore.so.5 #2 0x7f28289a4840 in () at /usr/lib64/libQt5WebEngineCore.so.5 #3 0x7f28289a4a10 in () at /usr/lib64/libQt5WebEngineCore.so.5 #4 0x7f28289a15cd in () at /usr/lib64/libQt5WebEngineCore.so.5 #5 0x7f283122f474 in start_thread () at /lib64/libpthread.so.0 #6 0x7f28353883ed in clone () at /lib64/libc.so.6 Thread 32 (Thread 0x7f26e9683700 (LWP 2726)): #0 0x7f2830623034 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f28305de57c in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f28305def5b in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f28305df14c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f2835ec2aeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2835e6a76a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f2835c903b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f2835c952d8 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f283122f474 in start_thread () at /lib64/libpthread.so.0 #9 0x7f28353883ed in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7f26e9e84700 (LWP 2724)): #0 0x7f283537fa1d in poll () at /lib64/libc.so.6 #1 0x7f28305df036 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f28305df14c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2835ec2aeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f2835e6a76a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2835c903b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f2835c952d8 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f283122f474 in start_thread () at /lib64/libpthread.so.0 #8 0x7f28353883ed in clone () at /lib64/libc.so.6 Thread 30 (Thread 0x7f26f9421700 (LWP 2716)): #0 0x7f2830623034 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f28305de57c in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f28305def5b in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f28305df14c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f2835ec2aeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2835e6a76a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f2835c903b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f2835c952d8 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f283122f474 in start_thread () at /lib64/libpthread.so.0 #9 0x7f28353883ed in clone () at /lib64/libc.so.6 Thread 29 (Thread 0x7f26f9c22700 (LWP 2714)): #0 0x7f283537ba7d in read () at /lib64/libc.so.6 #1 0x7f2830621c70 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f28305deb06 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f28305defd4 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f28305df14c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f2835ec2aeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f2835e6a76a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f2835c903b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f2835c952d8 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f283122f474 in start_thread () at /lib64/libpthread.so.0 #10 0x7f28353883ed in clone () at /lib64/libc.so.6 Thread 28 (Thread 0x7f26fa863700 (LWP 2711)): #0 0x7fff1e38fadc in clock_gettime () #1 0x7f28353950a6 in clock_gettime () at /lib64/libc.so.6 #2 0x7f2835d40d96 in () at /usr/lib64/libQt5Core.so.5 #3 0x7f2835ec0699 in
[Akonadi] [Bug 367892] During folder synchronisation Akonadi blocks out other operations like deleting or viewing mails
https://bugs.kde.org/show_bug.cgi?id=367892 Matthias Dahl <ua_bugz_...@binary-island.eu> changed: What|Removed |Added CC||ua_bugz_kde@binary-island.e ||u -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 363741] akonadi server 16.04.2: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 --- Comment #13 from Jan-Matthias Braun <jan_br...@gmx.net> --- it looks like my problem is somehow related to akonadi/kmail producing and not coping with invalid xapian searches. Right now, I have not seen another akonadi crash. The search that was crashing akonadi had a debug output representation (using the qdebug overload of operator << on term()) over half a screen, i.e., many lines with many many columns. I have no Idea where it came from -- and now it is gone. -- 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
[Akonadi] [Bug 363741] akonadi server 16.04.2: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 --- Comment #12 from Jan-Matthias Braun <jan_br...@gmx.net> --- Okay, I was able to remove a very reproducible crash (with the above mentioned segfault) during startup of akonadi (without any client running) by removing a search from the search folder in kmail. Since then, it is running for at least eight minutes (!) now and I haven't seen a SEGV up to now. By the way, is it normal, that different searches have the same name? In the logs I am seeing the Executing search "foo-1186278907-bar" lines. And the crashing search had the same name, as the search running before, which was much, much simpler. And checking now I see, that different searches often have the same search name in the logs, although from time to time the name seems to change. Revisiting older logs, the crash always happend with a reused search-name. But I cannot tell if it was the same search, always, because only now I went to instrument the code around the backtrace end in the akonadi-search code (xapian/xapiansearchstore.cpp:177) with lots of output. -- 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
[Akonadi] [Bug 363741] akonadi server 16.04.1: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 --- Comment #11 from Jan-Matthias Braun <jan_br...@gmx.net> --- I do see the same backtrace for xapian 1.3.7. -- 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
[Akonadi] [Bug 363741] akonadi server 16.04.1: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 --- Comment #10 from Jan-Matthias Braun <jan_br...@gmx.net> --- Ok, I have seen this one three times in a row, now, -- 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
[Akonadi] [Bug 363741] akonadi server 16.04.1: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 --- Comment #9 from Jan-Matthias Braun <jan_br...@gmx.net> --- Connecting into the running process indeed provides a better backtrace, although -- why? :-) Here it is: #0 0x in ?? () #1 0x7f6ef42d333b in ExternalPostList::ExternalPostList (this=0x7f6f0835a170, db=..., source_=, factor_=, matcher=0x7f6f137fcd30) at matcher/externalpostlist.cc:40 #2 0x7f6ef41e6d6b in Xapian::Internal::QueryPostingSource::postlist (this=, qopt=0x7f6f137fc650, factor=1) at api/queryinternal.cc:739 #3 0x7f6ef41e50a1 in Xapian::Query::Internal::postlist_sub_xor (this=, ctx=..., qopt=, factor=) at api/queryinternal.cc:634 #4 0x7f6ef41e6553 in Xapian::Internal::QueryBranch::do_or_like (this=this@entry=0x7f6f0807b490, ctx=..., qopt=qopt@entry=0x7f6f137fc650, factor=factor@entry=1, elite_set_size=elite_set_size@entry=0, first=first@entry=1) at api/queryinternal.cc:1186 #5 0x7f6ef41e6b1a in Xapian::Internal::QueryAndMaybe::postlist (this=0x7f6f0807b490, qopt=0x7f6f137fc650, factor=1) at api/queryinternal.cc:1550 #6 0x7f6ef42d35fa in LocalSubMatch::get_postlist (this=0x7f6f0807af50, matcher=0x7f6f137fcd30, total_subqs_ptr=0x7f6f137fc7bc) at matcher/localsubmatch.cc:204 #7 0x7f6ef42d9a51 in MultiMatch::get_mset (this=this@entry=0x7f6f137fcd30, first=first@entry=0, maxitems=10, check_at_least=check_at_least@entry=10, mset=..., stats=..., mdecider=0x0, sorter=0x0) at matcher/multimatch.cc:419 #8 0x7f6ef41d55e1 in Xapian::Enquire::Internal::get_mset (this=0x7f6f0807ad10, first=, maxitems=, check_at_least=, check_at_least@entry=0, rset=rset@entry=0x0, mdecider=0x0) at api/omenquire.cc:548 #9 0x7f6ef41d5924 in Xapian::Enquire::get_mset (this=this@entry=0x7f6f137fd050, first=, maxitems=, check_at_least=check_at_least@entry=0, rset=rset@entry=0x0, mdecider=0x0) at api/omenquire.cc:906 #10 0x7f6ee05e968d in Akonadi::Search::XapianSearchStore::exec (this=0x7f6ef009bf50, query=...) at /var/tmp/portage/kde-apps/akonadi-search-16.04.49./work/akonadi-search-16.04.49./xapian/xapiansearchstore.cpp:177 #11 0x7f6f12df8065 in Akonadi::Search::Query::exec (this=this@entry=0x7f6f137fd2c0) at /var/tmp/portage/kde-apps/akonadi-search-16.04.49./work/akonadi-search-16.04.49./core/query.cpp:252 #12 0x7f6f180fff7d in SearchPlugin::search (this=, akonadiQuery=..., collections=..., mimeTypes=...) at /var/tmp/portage/kde-apps/akonadi-search-16.04.49./work/akonadi-search-16.04.49./akonadiplugin/searchplugin.cpp:348 #13 0x0055b4eb in Akonadi::Server::SearchRequest::searchPlugins (this=this@entry=0x7f6f137fd900) at /var/tmp/portage/kde-apps/akonadi-16.04.49./work/akonadi-16.04.49./src/server/search/searchrequest.cpp:112 #14 0x0055b893 in Akonadi::Server::SearchRequest::exec (this=this@entry=0x7f6f137fd900) at /var/tmp/portage/kde-apps/akonadi-16.04.49./work/akonadi-16.04.49./src/server/search/searchrequest.cpp:123 #15 0x00444788 in Akonadi::Server::SearchManager::updateSearchImpl (this=0x27003f0, collection=..., cond=) at /var/tmp/portage/kde-apps/akonadi-16.04.49./work/akonadi-16.04.49./src/server/search/searchmanager.cpp:350 #16 0x7f6f1f8deaa9 in QObject::event (this=0x27003f0, e=) at kernel/qobject.cpp:1263 #17 0x7f6f1f8b2b5b in doNotify (event=0x7f6f08031ea0, receiver=0x27003f0) at kernel/qcoreapplication.cpp:1063 #18 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1049 #19 QCoreApplication::notifyInternal2 (receiver=0x27003f0, event=event@entry=0x7f6f08031ea0) at kernel/qcoreapplication.cpp:988 #20 0x7f6f1f8b526b in QCoreApplication::sendEvent (event=0x7f6f08031ea0, receiver=) at kernel/qcoreapplication.h:231 #21 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x2700600) at kernel/qcoreapplication.cpp:1649 #22 0x7f6f1f8b56d8 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1503 #23 0x7f6f1f9063f3 in postEventSourceDispatch (s=0x7f6f080012d0) at kernel/qeventdispatcher_glib.cpp:276 #24 0x7f6f1dd2eb17 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #25 0x7f6f1dd2f4f8 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #26 0x7f6f1dd2f68c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #27 0x7f6f1f9067ff in QEventDispatcherGlib::processEvents (this=0x7f6f080008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #28 0x7f6f1f8b0b1a in QEventLoop::exec (this=this@entry=0x7f6f137fde80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210 #29 0x7f6f1f6d2214 in QThread::exec (this=) at thread/qthread.cpp:507 #30 0x7f6f1f6d6e78 in QThreadPrivate::start (arg=0x27004c0) at thread/qthread_unix.cpp:344 #31 0x7f6f1e
[Akonadi] [Bug 363741] akonadi server 16.04.1: crashing every few seconds
https://bugs.kde.org/show_bug.cgi?id=363741 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added CC||jan_br...@gmx.net --- Comment #8 from Jan-Matthias Braun <jan_br...@gmx.net> --- Hi! I am seeing similar behaviour since 16.04.x, and checked up to 16.04.2 and 16.04-git. I am using qt 5.7, xapian 1.4, frameworks 5.23, and mariadb 10.1.14 on gentoo, too. One of my backtraces looks like this and is only partially usable: 0: akonadiserver() [0x4ac960] 1: akonadiserver() [0x4acc5f] 2: /lib64/libc.so.6(+0x33250) [0x7f025e5b3250] 3: /usr/lib64/libxapian.so.30(+0x1b2508) [0x7f0248531508] 4: /usr/lib64/libxapian.so.30(+0x7554b) [0x7f02483f454b] 5: /usr/lib64/libxapian.so.30(_ZNK6Xapian5Query8Internal20postlist_sub_or_likeERNS_8Internal9OrContextEP14QueryOptimiserd+0x21) [0x7f02483f1e21] 6: /usr/lib64/libxapian.so.30(+0x745a3) [0x7f02483f35a3] 7: /usr/lib64/libxapian.so.30(+0x74e1a) [0x7f02483f3e1a] 8: /usr/lib64/libxapian.so.30(+0x1b266a) [0x7f024853166a] 9: /usr/lib64/libxapian.so.30(+0x1c2991) [0x7f0248541991] 10: /usr/lib64/libxapian.so.30(_ZNK6Xapian7Enquire8Internal8get_msetEjjjPKNS_4RSetEPKNS_12MatchDeciderE+0x1c1) [0x7f02483dd8f1] 11: /usr/lib64/libxapian.so.30(_ZNK6Xapian7Enquire8get_msetEjjjPKNS_4RSetEPKNS_12MatchDeciderE+0x24) [0x7f02483ddc34] 12: /usr/lib64/libKF5AkonadiSearchXapian.so.5(_ZN7Akonadi6Search17XapianSearchStore4execERKNS0_5QueryE+0x8b6) [0x7f02481725d6] 13: /usr/lib64/libKF5AkonadiSearchCore.so.5(_ZN7Akonadi6Search5Query4execEv+0x245) [0x7f0258235a55] 14: /usr/lib64/qt5/plugins/akonadi/akonadi_search_plugin.so(+0x400c) [0x7f025844000c] 15: akonadiserver() [0x4cba6f] 16: akonadiserver() [0x44aaa8] 17: akonadiserver() [0x4835d0] 18: /usr/lib64/libQt5Core.so.5(_ZN7QObject5eventEP6QEvent+0xe9) [0x7f025e085aa9] 19: /usr/lib64/libQt5Core.so.5(_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent+0xfb) [0x7f025e059b5b] 20: /usr/lib64/libQt5Core.so.5(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x2db) [0x7f025e05c26b] 21: /usr/lib64/libQt5Core.so.5(+0x2de3f3) [0x7f025e0ad3f3] 22: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x297) [0x7f025c86eb17] 23: /usr/lib64/libglib-2.0.so.0(+0x294f8) [0x7f025c86f4f8] 24: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f025c86f68c] 25: /usr/lib64/libQt5Core.so.5(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x5f) [0x7f025e0ad7ff] 26: /usr/lib64/libQt5Core.so.5(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xfa) [0x7f025e057b1a] 27: /usr/lib64/libQt5Core.so.5(_ZN7QThread4execEv+0xb4) [0x7f025de79214] 28: /usr/lib64/libQt5Core.so.5(+0xaee78) [0x7f025de7de78] 29: /lib64/libpthread.so.0(+0x7434) [0x7f025d99c434] 30: /lib64/libc.so.6(clone+0x6d) [0x7f025e667ded] Now I have installed all debug symbols, but now I can only see mini-backtraces with even less information: 0: akonadiserver() [0x572666] 1: akonadiserver() [0x572982] 2: /lib64/libc.so.6(+0x33250) [0x7fa0e1fe9250] which leaves me at a loss for useful info. (I am not even getting dr konqi, I have to grab the debug info from the akonadi logs.) I am using a bunch of imap-servers including one akonadi-ews account. I have contacts and calendars in owncloud. These seem to get disabled all the while. What can I do to improve debugging information? Cheers, Jan -- 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
[kontact] [Bug 363547] New: Copying calender folder to owncloud leads to crash
https://bugs.kde.org/show_bug.cgi?id=363547 Bug ID: 363547 Summary: Copying calender folder to owncloud leads to crash Product: kontact Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: m.de...@gmx.de Application: kontact (5.1.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-22-generic x86_64 Distribution: Ubuntu 16.04 LTS -- Information about the crash: - What I was doing when the application crashed: 1. Opened Kontact 2. Switched to Calendar View 3. Selected a calendar, right click, copy folder to 4. Selected an ownCloud CalDAV target 5. Application crashed (but calendar seemd to have copied successfully) -- 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 0x7fb7e6cce940 (LWP 2445))] Thread 37 (Thread 0x7fb7c5d97700 (LWP 2458)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb7e22f088b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7fb7e22f08c9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fb7de0b46fa in start_thread (arg=0x7fb7c5d97700) at pthread_create.c:333 #4 0x7fb7e4079b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 36 (Thread 0x7fb77e731700 (LWP 2473)): #0 0x7fb7dd8873c4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb7dd889c7a in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb7dd88a2c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb7dd88a42c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb7e4bb0a9b in QEventDispatcherGlib::processEvents (this=0x7fb7780008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x7fb7e4b57dea in QEventLoop::exec (this=this@entry=0x7fb77e730c80, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fb7e49748a4 in QThread::exec (this=) at thread/qthread.cpp:503 #7 0x7fb7e497984e in QThreadPrivate::start (arg=0xb6bdd0) at thread/qthread_unix.cpp:331 #8 0x7fb7de0b46fa in start_thread (arg=0x7fb77e731700) at pthread_create.c:333 #9 0x7fb7e4079b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 35 (Thread 0x7fb777fff700 (LWP 2541)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb7e1ffea74 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7fb7e2320541 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fb7de0b46fa in start_thread (arg=0x7fb777fff700) at pthread_create.c:333 #4 0x7fb7e4079b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 34 (Thread 0x7fbfe700 (LWP 2542)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb7e1fffaa3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7fb7e2320541 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fb7de0b46fa in start_thread (arg=0x7fbfe700) at pthread_create.c:333 #4 0x7fb7e4079b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 33 (Thread 0x7fb776ffd700 (LWP 2543)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb7e1fffaa3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7fb7e2320541 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fb7de0b46fa in start_thread (arg=0x7fb776ffd700) at pthread_create.c:333 #4 0x7fb7e4079b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 32 (Thread 0x7fb7767fc700 (LWP 2544)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fb7e1fffaa3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7fb7e2320541 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7fb7de0b46fa in start_thread (arg=0x7fb7767fc700) at pthread_create.c:333 #4 0x7fb7e4079b5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 31 (Thread 0x7fb75cc60700 (LWP 2599)): #0 0x7fb7dd8cea64 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fb7dd889eba in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fb7dd88a380 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb7dd88a42c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb7e4bb0a9b in QEventDispatcherGlib::processEvents (this=0x7fb7540008c0, flags=...) at
[kdepim] [Bug 362317] Some dialogs from various KDE PIM applications 16.04. freeze when being opened
https://bugs.kde.org/show_bug.cgi?id=362317 --- Comment #5 from Matthias Nagel <mh-na...@web.de> --- Created attachment 98857 --> https://bugs.kde.org/attachment.cgi?id=98857=edit xsession-errors after kontact tried to open the confirmation dialog to delete emails -- 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
[Akonadi] [Bug 351814] Kmail 15.08 will not sync Outlook365 IMAP Folders
https://bugs.kde.org/show_bug.cgi?id=351814 --- Comment #28 from Jan-Matthias Braun <jan_br...@gmx.net> --- Okay, I think I have answered my own question: It is there and therefore I should better open a new but. Please excuse the noise... :-/ -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 351814] Kmail 15.08 will not sync Outlook365 IMAP Folders
https://bugs.kde.org/show_bug.cgi?id=351814 --- Comment #27 from Jan-Matthias Braun <jan_br...@gmx.net> --- Hi! I do have the impression that this issue came back with 15.12.: My outlook imap is not syncing anymore. Does somebody else see the same behaviour? Can the fix somehow have evaded going into 15.12 or should I open a new bug report? All the best, Jan -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 283682] KMail duplicates filtered messages
https://bugs.kde.org/show_bug.cgi?id=283682 Matthias Mailänder <matth...@mailaender.name> changed: What|Removed |Added CC|matth...@mailaender.name| -- 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
[kontact] [Bug 356116] Kmail crashes when forwarding mails
https://bugs.kde.org/show_bug.cgi?id=356116 Matthias Kretz <kr...@kde.org> changed: What|Removed |Added CC||kr...@kde.org --- Comment #2 from Matthias Kretz <kr...@kde.org> --- I just got a very similar crash backtrace on the following activity: * new mail * click 'Select' button on To: field * the dialog opens and is unresponsive, waiting for the contact data to come in (this blocking UI - and the time it takes might be worth a bug report itself). * the dialog shows the contact data for half a second * crash ## Comment on the backtrace The `0x0` in `#31 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0` looks suspicious. ## 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 0x7f885ef7f880 (LWP 25653))] Thread 7 (Thread 0x7f883ce89700 (LWP 25655)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f885b26d48b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f885b26d4c9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f88569ec6aa in start_thread (arg=0x7f883ce89700) at pthread_create.c:333 #4 0x7f885c15feed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f87f57d1700 (LWP 25656)): #0 0x7f885c15049d in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f8855db24e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8855d6ecd4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8855d6f190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f8855d6f2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f885cc9529b in QEventDispatcherGlib::processEvents (this=0x7f87f8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0x7f885cc3b75a in QEventLoop::exec (this=this@entry=0x7f87f57d0d40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7f885ca593d4 in QThread::exec (this=) at thread/qthread.cpp:503 #8 0x7f885ca5e2be in QThreadPrivate::start (arg=0xb59a60) at thread/qthread_unix.cpp:337 #9 0x7f88569ec6aa in start_thread (arg=0x7f87f57d1700) at pthread_create.c:333 #10 0x7f885c15feed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f87efcb2700 (LWP 25657)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f885af7b5b4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f885b29d341 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f88569ec6aa in start_thread (arg=0x7f87efcb2700) at pthread_create.c:333 #4 0x7f885c15feed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f87ef4b1700 (LWP 25658)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f885af7c5e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f885b29d341 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f88569ec6aa in start_thread (arg=0x7f87ef4b1700) at pthread_create.c:333 #4 0x7f885c15feed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f87eecb0700 (LWP 25659)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f885af7c5e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f885b29d341 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f88569ec6aa in start_thread (arg=0x7f87eecb0700) at pthread_create.c:333 #4 0x7f885c15feed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f87ee4af700 (LWP 25660)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f885af7c5e3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #2 0x7f885b29d341 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 #3 0x7f88569ec6aa in start_thread (arg=0x7f87ee4af700) at pthread_create.c:333 #4 0x7f885c15feed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f885ef7f880 (LWP 25653)): [KCrash Handler] #6 QSortFilterProxyModelPrivate::index_to_iterator (this=0x3609120, proxy_index=...) at itemmodels/qsortfilterproxymodel.cpp:185 #7 QSortFilterProxyModelPrivate::proxy_to_source (proxy_index=..., this=0x3609120) at itemmodels/qsortfilterproxymodel.cpp:375 #8 QSortFilterProxyModel::mapToSource (proxyIndex=..., this=0x70737c0) at itemmodels/qsortfilterproxymodel.cpp:2716 #9 QSortFilterProxyModelPrivate::store_persistent_indexes (thi
[Akonadi] [Bug 358467] on session start mysqld goes into 100% CPU and is not killable
https://bugs.kde.org/show_bug.cgi?id=358467 Matthias Apitz <g...@unixarea.de> changed: What|Removed |Added CC||g...@unixarea.de -- 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
[Akonadi] [Bug 358467] New: on session start mysqld goes into 100% CPU and is not killable
https://bugs.kde.org/show_bug.cgi?id=358467 Bug ID: 358467 Summary: on session start mysqld goes into 100% CPU and is not killable Product: Akonadi Version: 1.13.0 Platform: FreeBSD Ports OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: g...@unixarea.de I have created a new user in FreeBSD, provided him a ~/.xinitrc which starts kde4 on 'startx'; the KDE environment is created fine and desktop comes up; but the isqld running for akonadi goes in 100% CPU loop and you can not kill it, not even with -9; a reboot ends up in PANIC because 1 vnode can not synced to disk; The other (already existing account) works fine and does not show this problem; Reproducible: Always Steps to Reproduce: 1. create new user in FreeBSD system 2. create ~/.xinitrc as: exec /usr/local/bin/startkde 3. login as this user and issue 'startx' 4. check mysql with 'ps ax | fgrep mysql' 5. try shutdwon, remains 1 unsync-able vnode -- 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
[kdepimlibs] [Bug 353326] Korganizer crashed when trying to add a new event.
https://bugs.kde.org/show_bug.cgi?id=353326 Matthias Hoffmann <bugs.kde@m-hoffmann.net> changed: What|Removed |Added CC||bugs.kde@m-hoffmann.net --- Comment #2 from Matthias Hoffmann <bugs.kde@m-hoffmann.net> --- Created attachment 95377 --> https://bugs.kde.org/attachment.cgi?id=95377=edit VCard used to reproduce crash I was able to reproduce this crash on an empty kaddressbook. I've imported the attached VCard and directly after, kaddressbook crashed (will attach backtrace). It kept on crashing directly after each restart. Also KOrganizer crashes if I try to add a new event. System information: Kubuntu Wily Werewolf KDE FW 5.15.0 Qt 5.4.2 -- 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
[kdepimlibs] [Bug 353326] Korganizer crashed when trying to add a new event.
https://bugs.kde.org/show_bug.cgi?id=353326 --- Comment #3 from Matthias Hoffmann <bugs.kde@m-hoffmann.net> --- Created attachment 95378 --> https://bugs.kde.org/attachment.cgi?id=95378=edit Backtrace during crash of kaddressbook -- 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
[kmail2] [Bug 351814] Kmail 15.08 will not sync Outlook365 IMAP Folders
https://bugs.kde.org/show_bug.cgi?id=351814 --- Comment #17 from Jan-Matthias Braun <jan_br...@gmx.net> --- Hi! (In reply to jat255 from comment #16) > (In reply to Jan-Matthias Braun from comment #7) [...] > This sounds like you may want to open another bug report. To keep this one > clean, it would probably be best to keep it to people whose IMAP folders are > not getting updated at all. Actually, I am not convinced that these are two distinct behaviours. For the first, the imap-logs seem to be the same as in the original report, i.e., I would suspect a higher load of the corresponding resource for all these cases, at least it seems to be logging activity all the time. For the second---as an update, my INBOX right now hasn't been updated since 23rd of September, the resource being online and working all the while. This makes every update a stochastic event at best and the time lag has jumped from almost daily over after three days to not in all since 23rd of September. In other words, there is no reliable working component, but the symptoms seem similar, which makes it seem that I sometimes get lucky for small folders with 1-3 (!) e-Mails in them. > On another note, has anyone from the kmail team seen/commented on this bug? > There seem to be a lot people willing to help diagnose the problem, but very > few suggestions at this point. As Orion noted, this is a showstopper and I > have completely stopped using kmail because it is useless to me under > plasma. I wonder if there's a better way to get the devs' attention? Probably irc? I don't know and won't have time to check for a little longer. All the best and good luck, Jan -- 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
[kimap] [Bug 351814] Kmail 15.08 will not sync Outlook365 IMAP Folders
https://bugs.kde.org/show_bug.cgi?id=351814 --- Comment #22 from Jan-Matthias Braun <jan_br...@gmx.net> --- Whatever---it works! Thank you very much Daniel! All the best, Jan -- 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
[kmail2] [Bug 351814] Kmail 15.08 will not sync Outlook365 IMAP Folders
https://bugs.kde.org/show_bug.cgi?id=351814 --- Comment #13 from Jan-Matthias Braun <jan_br...@gmx.net> --- The funny thing is, that smaller folders, like the Junk-Mail-Folder, updates occur. The inbox folder is quite huge, so I tried to move two years worth of e-Mails, but this action never got synced and probably made things only worse. -- 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
[kmail2] [Bug 351814] Kmail 15.08 will not sync Outlook365 IMAP Folders
https://bugs.kde.org/show_bug.cgi?id=351814 --- Comment #12 from Jan-Matthias Braun <jan_br...@gmx.net> --- Hi, I cannot tell for bug #351993, as I am only experiencing this problem with our corporate exchange server. All other accounts are working flawlessly and respond fast. The same goes for bug #352701 -- this is a very localised one resource-only problem for me. For this exchange server imap idle never really seemed to have worked and now fetching mails seems to be stuck with some demanding operation which never seems to end. So I guess there is a general problem with the exchange server. -- 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
[kmail2] [Bug 351395] kmail 4.81beta1 crashes when opening the composer window
https://bugs.kde.org/show_bug.cgi?id=351395 --- Comment #9 from Jan-Matthias Braun <jan_br...@gmx.net> --- So, I got it! I don't know how but I used the heuristic approach to track the offender. As the crash happens in slotEditorTextChanged I moved the connect back in the constructor, as is was obviously too early to work when not replying to anything. This worked out and then I just invested the 5 minutes to find the earliest non-offending position in the constructor, which is exactly after the call to readConfig() (and before setupStatusBar(...)). I hope this helps someone who actually knows what is happening. The patch I am going to attach now has the connect a hand full of lines later, as there are a lot of connects already so I think it is fitting. Honestly, it doesn't crash right now so I am happy. :-) -- 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
[kmail2] [Bug 351395] kmail 4.81beta1 crashes when opening the composer window
https://bugs.kde.org/show_bug.cgi?id=351395 --- Comment #10 from Jan-Matthias Braun <jan_br...@gmx.net> --- Created attachment 94740 --> https://bugs.kde.org/attachment.cgi?id=94740=edit Moved the connect of the crashing slot back in code, so it could complete and the window opens. -- 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
[kmail2] [Bug 351395] kmail 4.81beta1 crashes when opening the composer window
https://bugs.kde.org/show_bug.cgi?id=351395 --- Comment #11 from Jan-Matthias Braun <jan_br...@gmx.net> --- Created attachment 94741 --> https://bugs.kde.org/attachment.cgi?id=94741=edit Similar patch, using the new api for KMComposerEditorNg. Caution! I don't know what I am doing, but it is not crashing on hitting "new mail". :-) Just the same thing, but this time I used the new api after renaming the class and removing the comment and the old connect statement. -- 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
[kmail2] [Bug 351395] kmail 15.08.1 crashes when opening the composer window
https://bugs.kde.org/show_bug.cgi?id=351395 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added Summary|kmail 4.81beta1 crashes |kmail 15.08.1 crashes when |when opening the composer |opening the composer window |window | -- 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
[kmail2] [Bug 351395] kmail 15.08.1 crashes when opening the composer window
https://bugs.kde.org/show_bug.cgi?id=351395 --- Comment #12 from Jan-Matthias Braun <jan_br...@gmx.net> --- On a side note: The crash in slotEditorTextChanged() depended on the local bool textIsNotEmpty = !mComposerBase->editor()->document()->isEmpty(); The crash happend directly in the next call to mFindText->setEnabled(textIsNotEmpty); In my testing, the boolean condition was opposite when hitting reply and when hitting new message and only in the latter case it crashed in the call to setEnabled(...). -- 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
[kmail2] [Bug 351814] Kmail 15.08 will not sync Outlook365 IMAP Folders
https://bugs.kde.org/show_bug.cgi?id=351814 --- Comment #11 from Jan-Matthias Braun <jan_br...@gmx.net> --- Another observation is, that the corresponding akondi_imap_resource is quite CPU-demanding; most of the time with around 15 % on my system. The Outlook resource is at 50 minutes compute time right now, in comparison to below 10 seconds for my three other resources. Nonetheless, I won't see new mails for days. Today (Wednesday) I saw the first update since Friday. The outlook resource has always been a bit slower with updates than the others, but only with the current version I am seeing no updates at all. Is there any specific diagnostic I can run? For example to better understand the imap logs? -- 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
[Akonadi] [Bug 351515] Akonadi-Resource 15.08 (&15.07.90) crash in background (probably while checking mails)
https://bugs.kde.org/show_bug.cgi?id=351515 --- Comment #3 from Jan-Matthias Braun <jan_br...@gmx.net> --- I am unsure, if this possibly is something like an updated version of bug #341860 . -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 345748] IMAP Crash Checking Gmail
https://bugs.kde.org/show_bug.cgi?id=345748 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added CC||jan_br...@gmx.net --- Comment #3 from Jan-Matthias Braun <jan_br...@gmx.net> --- Could be a duplicate of 341860 -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 341860] akonadi_imap_resource (4.14) segfault
https://bugs.kde.org/show_bug.cgi?id=341860 Jan-Matthias Braun <jan_br...@gmx.net> changed: What|Removed |Added CC||jan_br...@gmx.net --- Comment #4 from Jan-Matthias Braun <jan_br...@gmx.net> --- Looks like bug #345748 is a duplicate and my bug #351515 could be the current state of the same bug. I don't know the code, but from the backtrace they both seem to trigger after receiving something. I know this is a hand-waving argument. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
