[kontact] [Bug 421505] Kontact gets unexpectedly closed when KMail within Kontact is manually closed. Factory error in Akonadi log
https://bugs.kde.org/show_bug.cgi?id=421505 prox changed: What|Removed |Added CC||arbeitosau...@arcor.de -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 421505] Kontact gets unexpectedly closed when KMail within Kontact is manually closed. Factory error in Akonadi log
https://bugs.kde.org/show_bug.cgi?id=421505 --- Comment #2 from prox --- I have enabled the Akonadi console logging feature before the error message reported above popped up the last time. These are the last lines of the output of this Akonadi logging feature that was running while the error message popped up: [...] [1979-11-12T23:35:30.000] kontact org.kde.pim.kmail Last resource finished syncing, mail check done [1979-11-13T12:41:25.000] korgac org.kde.pim.koalarmclient Check: "Do. Mai 14 11:39:41 2020" - "Do. Mai 14 11:40:40 2020" [1979-11-14T05:21:20.000] korgac org.kde.pim.koalarmclient Check: "Do. Mai 14 11:40:41 2020" - "Do. Mai 14 11:41:40 2020" [1979-11-14T22:01:17.000] korgac org.kde.pim.koalarmclient Check: "Do. Mai 14 11:41:41 2020" - "Do. Mai 14 11:42:40 2020" [1979-11-15T14:41:17.000] korgac org.kde.pim.koalarmclient Check: "Do. Mai 14 11:42:41 2020" - "Do. Mai 14 11:43:40 2020" [1979-11-16T07:21:15.000] korgac org.kde.pim.koalarmclient Check: "Do. Mai 14 11:43:41 2020" - "Do. Mai 14 11:44:40 2020" [1979-11-17T00:01:15.000] korgac org.kde.pim.koalarmclient Check: "Do. Mai 14 11:44:41 2020" - "Do. Mai 14 11:45:40 2020" [1979-11-17T15:34:37.000] akonadi_imap_resource org.kde.pim.imapresource Restarting IDLE to prevent server from disconnecting me! [1979-11-17T15:39:36.000] akonadi_imap_resource org.kde.pim.imapresource IDLE dropped maybe we should reconnect? [1979-11-17T15:39:36.000] akonadi_imap_resource org.kde.pim.imapresource Restarting the IDLE session! [1979-11-17T16:41:33.000] korgac org.kde.pim.koalarmclient Check: "Do. Mai 14 11:45:41 2020" - "Do. Mai 14 11:46:40 2020" [1979-11-17T17:33:58.000] kontact kf5.kxmlgui 0x558a556fb230 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. [1979-11-17T17:34:07.000] kontact org.kde.pim.kmail Closing last KMMainWin: stopping mail check [1979-11-17T17:37:45.000] kontact default QIODevice::read (QLocalSocket): device not open [1979-11-17T17:37:45.000] akonadiserver org.kde.pim.akonadiserver Subscriber "MessageViewerMonitor - 94052626273424" disconnected [1979-11-17T17:37:57.000] kontact default QIODevice::read (QLocalSocket): device not open [1979-11-17T17:39:47.000] kontact default QIODevice::read (QLocalSocket): device not open [1979-11-17T17:39:47.000] akonadiserver org.kde.pim.akonadiserver Subscriber "MessageListTagMonitor - 94052627360240" disconnected [1979-11-17T17:42:33.000] akonadiserver org.kde.pim.akonadiserver Subscriber "KMail Kernel ETM - 94052627637056" disconnected [1979-11-17T17:42:32.000] kontact default QIODevice::read (QLocalSocket): device not open [1979-11-17T17:42:33.000] kontact default QIODevice::read (QLocalSocket): device not open [1979-11-17T17:42:36.000] kontact default QIODevice::read (QLocalSocket): device not open [1979-11-17T17:42:37.000] akonadiserver org.kde.pim.akonadiserver Subscriber "TagActionManagerMonitor - 94052632941392" disconnected [1979-11-17T17:42:42.000] kontact kf5.kxmlgui 0x558a555dd138 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. [1979-11-17T17:42:43.000] kontact kf5.kxmlgui 0x558a557947f0 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. [1979-11-17T17:42:43.000] kontact kf5.kxmlgui 0x558a5571b758 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. [1979-11-17T17:42:45.000] kontact kf5.kxmlgui 0x558a555f3ac8 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. [1979-11-17T17:42:46.000] kontact kf5.kxmlgui 0x558a557f26f8 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. [1979-11-17T17:42:46.000] kontact org.kde.pim.akregator Part::~Part() enter [1979-11-17T17:46:51.000] kontact org.kde.pim.akregator Part::~Part(): leaving [1979-11-17T17:46:59.000] kontact kf5.kxmlgui 0x558a5566ba98 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. [1979-11-17T17:47:00.000] kontact kf5.kxmlgui 0x558a5578f748 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. [1979-11-17T17:47:02.000] kontact kf5.kxmlgui 0x558a556b0e70 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. [1979-11-17T17:47:29.000] kontact default QIODevice::read (QLocalSocket): device not open [1979-11-17T17:47:29.000] kontact default QIODevice::read (QLocalSocket): device not open [1979-11-17T17:47:29.000
[kontact] [Bug 421505] Kontact gets unexpectedly closed when KMail within Kontact is manually closed. Factory error in Akonadi log
https://bugs.kde.org/show_bug.cgi?id=421505 --- Comment #1 from prox --- This is what the KDE bug reporting assistant has collected about this behaviour: 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 0x7f0b45ef4f00 (LWP 2248))] Thread 25 (Thread 0x7f0af1ffb700 (LWP 3437)): #0 0x7f0b58ea33f9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f0b52c38847 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #2 0x7f0b52c3b10a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #3 0x7f0b52c3b1f2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f0b52c3f781 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f0b52c40c61 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f0b52c49971 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f0b58e9cfa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f0b5a05a4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 24 (Thread 0x7f0a5ef43700 (LWP 2340)): #0 0x7f0b58ea33f9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f0b52c38847 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #2 0x7f0b52c3b10a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #3 0x7f0b52c3b1f2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f0b52c3f781 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f0b52c40c61 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f0b52c49971 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f0b58e9cfa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f0b5a05a4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 23 (Thread 0x7f0a65737700 (LWP 2277)): #0 0x7f0b5a04b537 in write () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f0b59fdc3bd in _IO_file_write () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7f0b59fdb75f in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #3 0x7f0b59fdcaee in _IO_file_xsputn () from /lib/x86_64-linux-gnu/libc.so.6 #4 0x7f0b59fb3932 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x7f0b59fb0eb2 in vfprintf () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x7f0b5a069536 in __fprintf_chk () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x7f0b4e38ca5a in event_logv_ () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #8 0x7f0b4e38cc34 in event_warn () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #9 0x7f0b4e38e588 in ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #10 0x7f0b4e384329 in event_base_loop () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #11 0x7f0b52c0d529 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #12 0x7f0b52c2cafb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #13 0x7f0b52c4deeb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #14 0x7f0b52c49971 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #15 0x7f0b58e9cfa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #16 0x7f0b5a05a4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 22 (Thread 0x7f0af27fc700 (LWP 2275)): #0 0x7f0b58ea300c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f0b4e9f8e6a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f0b4e9f8e89 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f0b58e9cfa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7f0b5a05a4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 21 (Thread 0x7f0af2ffd700 (LWP 2274)): #0 0x7f0b5a04f819 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f0b4413e131 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f0b4412f9a0 in pa_mainloop_poll () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f0b4412ffee in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f0b441300a0 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f0b4413e079 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f0b440d5468 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so #7 0x7f0b58e9cfa3 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f0b5a05a4cf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 20 (Thread 0x7f0af77fe700 (LWP 2273)): #0 0x7f0b4e38e588 in ?? () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #1 0x7f0b4e384329 in event_base_loop () from /usr/lib/x86_64-linux-gnu/libevent-2.1.so.6 #2 0x7f0b52c0d529 in
[kontact] [Bug 421505] New: Kontact gets unexpectedly closed when KMail within Kontact is manually closed. Factory error in Akonadi log
https://bugs.kde.org/show_bug.cgi?id=421505 Bug ID: 421505 Summary: Kontact gets unexpectedly closed when KMail within Kontact is manually closed. Factory error in Akonadi log Product: kontact Version: 5.9.2 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: arbeitosau...@arcor.de Target Milestone: --- Application: kontact (5.9.3) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-9-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) Sometimes, when I manually close KMail within PIM, an error message pops up in my KDE desktop environment. This message says that Kontact unexpectedly has been closed. I recently have re-configured KMail to access two IMAP mail accounts. Before that I used POP3, and as far as I can remember, then this error message did not pop up. Debian 10.4 does not offer a package called kdepim-dbg and kontact-dbg and kmail-dbg, so I cannot backtrace this behaviour. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407289] KDEConnect crashes upon trying to 'Add storage location' from 'Filesystem expose settings'
https://bugs.kde.org/show_bug.cgi?id=407289 --- Comment #10 from prox --- I just noticed that I can now access my smartphone via Kdeconnect from my Debian (KDE) box using Dolphin. Probably a reboot of my Debian machine was necessary to make this possible. I did not restart my smartphone yet. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407289] KDEConnect crashes upon trying to 'Add storage location' from 'Filesystem expose settings'
https://bugs.kde.org/show_bug.cgi?id=407289 --- Comment #9 from prox --- Update to comments #7 and #8: I managed to define a storage location within Kdeconnect. Now it is the home directory in my smartphone. I did not notice the burger or sandwich symbol at the top in the left corner in the "Storage location" screen, where I could now define a storage location (maybe it this burger or sandwich symbol wasn't there before because I formerly had deactivated certain Google apps, which I just have activated again). But now a new behaviour: When I open the Kde-Connect app, the option "Filesystem expose" is not displayed any more. So I cannot change the storage location. And I cannot see it within the Kdeconnect app. And I still cannot establish a connection in Dolphin (KDE being part of Debian 10.3 on my computer) with my smartphone. Dolphin tells me that the filesystem of the device (here: my smartphone) cannot get mounted. The Kdeconnect app on my smartphone now has version 14.1.2 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407289] KDEConnect crashes upon trying to 'Add storage location' from 'Filesystem expose settings'
https://bugs.kde.org/show_bug.cgi?id=407289 --- Comment #8 from prox --- (In reply to prox from comment #7) > I have a similar problem on my LG K50s smartphone with Android 9 Pie: > > Whenever I want to define a storage location within KDE Connect (downloaded > from within F-DROID; KDE Connect currently has version 1.14.1), I cannot > define a storage location via "Filesystem expose" > "Add storage location" > and the greyed-out field "Select": The next message tells me "No Elements", > and I cannot select a storage location. Additional information: And having tried to select a new storage location, I cannot create a new folder via the three-dot-icon at the top in the right corner: The menu entry "New folder" is greyed. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407289] KDEConnect crashes upon trying to 'Add storage location' from 'Filesystem expose settings'
https://bugs.kde.org/show_bug.cgi?id=407289 prox changed: What|Removed |Added CC||arbeitosau...@arcor.de --- Comment #7 from prox --- I have a similar problem on my LG K50s smartphone with Android 9 Pie: Whenever I want to define a storage location within KDE Connect (downloaded from within F-DROID; KDE Connect currently has version 1.14.1), I cannot define a storage location via "Filesystem expose" > "Add storage location" and the greyed-out field "Select": The next message tells me "No Elements", and I cannot select a storage location. Although I have activated in the general Settings App > General > Apps & Messages > App Info > KDE Connect > Rights > the "Storage" option. This behaviour also occured in KDE-Connect version 1.13.1. This was the first version I had installed on my smartphone. -- You are receiving this mail because: You are watching all bug changes.
