[xdg-desktop-portal-kde] [Bug 460484] New: Whole system crash after launching any games when some time passed after boot
https://bugs.kde.org/show_bug.cgi?id=460484 Bug ID: 460484 Summary: Whole system crash after launching any games when some time passed after boot Classification: Plasma Product: xdg-desktop-portal-kde Version: 5.26.0 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: erikdr...@gmail.com CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- SUMMARY When some time passed after a boot, launching any game (heavy and light ones) results in a system crash. The crash appear with a black screen on my primary screen, a greenish screen on the secondary. From a sound prospective I can hear the last second of the audio being reproduced in loop until it finally shuts itself down and reboots the whole pc. This does not happens every time, only when enough time after a boot has passed. If I launch a game right after booting there is absolutely no issue (I tested for a couple of months). LOGS kde intensive care: https://katb.in/uyuwikehaqu coredumpctl gdb output: https://katb.in/ebolazubequ STEPS TO REPRODUCE 1. boot 2. wait 30 minutes 3. launch a game (example: csgo) 4. system crash SOFTWARE/OS VERSIONS Linux: 6.0.1-arch2-1 (present even in previous version 5.19 and 5.18) KDE Plasma Version: 5.26.0 (present even in previous version 5.25) KDE Frameworks Version: 5.99 Qt Version: 5.15.6 ADDITIONAL INFORMATION https://katb.in/eqexutunida -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482925] New: On external screens when window is off-screen, mouse gets an offset
https://bugs.kde.org/show_bug.cgi?id=482925 Bug ID: 482925 Summary: On external screens when window is off-screen, mouse gets an offset Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bozic.e...@gmail.com Target Milestone: --- Created attachment 166740 --> https://bugs.kde.org/attachment.cgi?id=166740&action=edit screen capture (video) of bug SUMMARY (Upgraded to KDE6, using X11) When using external screens, but not the built-in laptop screen cursor gets an offset if the window is off screen. If the whole window is fullscreen of inside the screen it's accurate. Also if I enable my bultin-monitor, but keep the window on the external (and partly on the built-in) it works fine. See attached video (first the brave window is off-screen a bit and the mouse get's an offset. Then I move it back fully on-screen and it's accurate again - e.g. it click where the cursor is) It reproduces every time I try it. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux on kernel 6.7.9-arch1-1 (64bit) (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Running X11 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 449857] Lockscreen window does not get focus by default on X11
https://bugs.kde.org/show_bug.cgi?id=449857 Erik changed: What|Removed |Added CC||eeco...@qirx.org --- Comment #57 from Erik --- Others in this thread pointed out the piece of code that is responsible (/usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:231), which makes a lot of sense: > visible: opacity > 0 > enabled: visible Set visible to true if the it is not transparent. Enable when visible. This seems to be introduced in https://invent.kde.org/plasma/plasma-workspace/-/commit/c4a3a4e5b974fb309a6da61252b2b830d2d90683 with comment: > // changing enabled will toggle if an item can have activeFocus, which > otherwise > //keeps the text cursor blinking even when invisble I however changed `enabled: visible` to `enabled: true` and (as expected) this restored the behavior for me. I do not see any evidence of a blinking cursor. I don't have any understanding of versioning or policy. I am on Kubuntu 20.04 and there are no updates in the Updates tab of Discover. The kinfocenter tells me I am on version 5.18.8 for the KDE Plasma. It would be nice (at least for other people who did not yet find this thread) to update the line, but as I said, I am not sure if the policy allows such a change -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 449857] Lockscreen window does not get focus by default on X11
https://bugs.kde.org/show_bug.cgi?id=449857 --- Comment #60 from Erik --- I previously linked the wrong commit, this is the one that introduced to it to this version: https://invent.kde.org/plasma/plasma-workspace/-/commit/c4a3a4e5b974fb309a6da61252b2b830d2d90683 This was a revert of https://invent.kde.org/plasma/plasma-workspace/-/commit/13057013d55ae19e76d29b9edc96510e52da2a7a Which was a 'fix' of https://invent.kde.org/plasma/plasma-workspace/-/commit/45e0a722fb85bb5d1ab8bef92080e934254b13aa where it was introduced as an 'optimization'. What I don't understand is how it can be that it manifested only a few months ago in 20.04. And if I understand you correctly you are saying this will not be fixed in 20.04. Maybe naive, but I don't understand why. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 458494] Plasma Does Not Integrate With Snap Firefox
https://bugs.kde.org/show_bug.cgi?id=458494 Erik changed: What|Removed |Added CC||estei...@gmail.com --- Comment #1 from Erik --- I notice the same after an upgrade from Kubuntu 20.04 to 22.04. Although I'm sure it's a bug in Plasma Browser Integration. AFAIK There is a broader issue with communication between snapped Firefox and other applications (for example KeepassXC). The fix for this is not in stable channel of the Firefox snap yet if I understand the following thread in Ubuntu Discourse correctly: https://discourse.ubuntu.com/t/call-for-testing-native-messaging-support-in-the-firefox-snap/29759/57 That thread is an interesting read anyway ;) -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 458494] Plasma Does Not Integrate With Snap Firefox
https://bugs.kde.org/show_bug.cgi?id=458494 --- Comment #2 from Erik --- (In reply to Erik from comment #1) Can't find a way to edit my comment so a reply instead. Made a typo, I meant to say: "Although I'm NOT sure it's a bug in Plasma Browser Integration" -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 457726] kscreen_backend_launcher block entering Screen Energy saving
https://bugs.kde.org/show_bug.cgi?id=457726 --- Comment #1 from Erik --- Update and more info: OBSERVED RESULT: When the screen forcefully wake up from the very short sleep, all the open windows are moved into the primary display. EXPECTED RESULT: With "kscreen_backend_launcher" process killed, the windows are not rearranged and the windows stays as before the sleep. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 457726] New: kscreen_backend_launcher block entering Screen Energy saving
https://bugs.kde.org/show_bug.cgi?id=457726 Bug ID: 457726 Summary: kscreen_backend_launcher block entering Screen Energy saving Product: KScreen Version: 5.25.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: erikdr...@gmail.com Target Milestone: --- SUMMARY When the system enter the Screen Energy Saving mode, both the connected monitors powers off but after a couple of seconds they wake up again. STEPS TO REPRODUCE 1. Into "settings > power managment > energy saving" enable "Screen Energy Saving" and set a timer OBSERVED RESULT After the timer expires, screens go black but after a couple of seconds, both of my monitors turn on again without any interaction from me. While debugging the issue I found out that killing the "kscreen_backend_launcher" process solves the issue and let the monitor sleep successfully. EXPECTED RESULT After the timer expires, screens go black and stays powered off until it detect an user interaction SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION System is up do date. I have 2 monitors connected, the primary one with DP and the other one with HDMI. The gpu is a radeon rx6600xt. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 457726] kscreen_backend_launcher block entering Screen Energy saving
https://bugs.kde.org/show_bug.cgi?id=457726 Erik changed: What|Removed |Added Version|5.25.4 |5.26.1 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 457726] kscreen_backend_launcher block entering Screen Energy saving
https://bugs.kde.org/show_bug.cgi?id=457726 --- Comment #3 from Erik --- UPDATE: Still happening in 5.26.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449349] New: Black wallpaper on primary screen only at login
https://bugs.kde.org/show_bug.cgi?id=449349 Bug ID: 449349 Summary: Black wallpaper on primary screen only at login Product: plasmashell Version: 5.23.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: erikdr...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 STEPS TO REPRODUCE 1. Dual monitor setup with primary screen on display port and the secondary one on HDMI 2. Login with Xorg OBSERVED RESULT Primary screen: Wallpaper is completely black, task manager bar and mouse are showing correctly. Right click with the mouse doesn't work and notifications appear in the middle-left side of the screen. Secondary screen: Wallpaper shows correctly and all behave as normal. After the login, if I disconnect the Display port and then reconnect it after a couple of seconds the wallpaper reappear in the primary screen and all works as intended until the next restart. On restart/logoff the issue repeats. EXPECTED RESULT Wallpaper shows correctly in the primary screen with no issues. SOFTWARE/OS VERSIONS Linux/KDE Plasma: ArchLinux with KDE 5.23.5 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Both screens have set the same kde default wallpaper so permission issues are not the cause. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419227] Can't resize windows (often but not always those run over NX (X2Go))
https://bugs.kde.org/show_bug.cgi?id=419227 Erik changed: What|Removed |Added CC||erik.ben...@develerik.dev --- Comment #7 from Erik --- Hi, I can reproduce this under KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 nx-libs version: 3.5.99.26 Is there any update about this issue? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435023] New: Drawing with the active lenovo pen on a lenovo laptop you can't draw at all
https://bugs.kde.org/show_bug.cgi?id=435023 Bug ID: 435023 Summary: Drawing with the active lenovo pen on a lenovo laptop you can't draw at all Product: krita Version: 4.4.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: grave Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: erik.fei...@hotmail.it Target Milestone: --- Created attachment 137106 --> https://bugs.kde.org/attachment.cgi?id=137106&action=edit i just tried to draw with the pen using the pencil tool called "_Pencil-2" SUMMARY STEPS TO REPRODUCE 1. open the programm 2. start a new drawing 3. drawing OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Lenovo ideapad Flex 5 - laptop Lenovo active pen 2 - pen -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 458494] Plasma Does Not Integrate With Snap Firefox
https://bugs.kde.org/show_bug.cgi?id=458494 --- Comment #3 from Erik --- Would it be possible to re-open this bug or should I create a new one? Browser Integration still doesn't seem to work with the Snap version of Firefox 107.0.1. Support for native messaging is added to the stable version of the snap now so therefore I expected Browser Integration to work as well. Got a prompt when starting Firefox to allow Plasma Browser Integration and I clicked OK. When inspecting from Firefox's about:debugging I see the following error message in the console: Uncaught (in promise) Error: Attempt to postMessage on disconnected port sendPortMessage moz-extension://f2a3fa37-c27f-4678-90f5-94eadb4bc46c/extension-utils.js:51 sendSettings moz-extension://f2a3fa37-c27f-4678-90f5-94eadb4bc46c/extension.js:45 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 405165] Sistem Setting Crash with driver propierty NVIDIA
https://bugs.kde.org/show_bug.cgi?id=405165 erik changed: What|Removed |Added CC||costamagna.e...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 399282] Random freezes when capturing an area running multiple gpu's
https://bugs.kde.org/show_bug.cgi?id=399282 Erik changed: What|Removed |Added CC||e...@meldco.dk --- Comment #4 from Erik --- Mager bug Debian 10 KDE Freezes when taking area shut can't press enter only option to restart pc or kill spectacle ctrl+alt+f1 //start terminal htop //start htop kill spectacle ctrl+alt+f7 //back to desktop -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 309773] Kpatience crashes after selecting a game of "Simple Simon"
https://bugs.kde.org/show_bug.cgi?id=309773 Erik changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 from Erik --- I'm not sure what to do with this old bug report. I don't have the same setup as 6 years ago so it's impossible to create the same circumstances. Still have KPatience installed (on Ubuntu MATE) but selecting a game of Simple Simon seems to work fine. Version of kpat is still the same (3.6) but Qt is at 5.9.5 now. So I'll mark it as resolved and worksforme. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 403222] KDE Partition Manager is using device name's for fstab entries instead of uuids.
https://bugs.kde.org/show_bug.cgi?id=403222 Erik changed: What|Removed |Added Version|unspecified |3.3 Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 403222] New: KDE Partition Manager is using device name's for fstab entries instead of uuids.
https://bugs.kde.org/show_bug.cgi?id=403222 Bug ID: 403222 Summary: KDE Partition Manager is using device name's for fstab entries instead of uuids. Product: partitionmanager Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: stiko...@kde.org Reporter: e...@erikgranger.name Target Milestone: --- SUMMARY KDE Partition Manager is using the device name instead of the uuid when updating partition mount points in fstab STEPS TO REPRODUCE 1. Put in a flash drive 2. Open KDE Partition Manager 3. Unmount the flash drive 4. Change the mount point of the flash drive 5. Apply 6. "Save Changes" 7. less /etc/fstab 8. Look at the bottom, it should say something like: /dev/sdh /home/me/test vfatdefaults0 0 OBSERVED RESULT Device name is used to define the partition in the fstab EXPECTED RESULT Uuid is used to define the partition in the fstab SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.2 Kernel: 4.19.0 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 403222] KDE Partition Manager is using device name's for fstab entries instead of uuids.
https://bugs.kde.org/show_bug.cgi?id=403222 Erik changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from Erik --- I've been very tired recently. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 501954] New: crash after applying a new global theme
https://bugs.kde.org/show_bug.cgi?id=501954 Bug ID: 501954 Summary: crash after applying a new global theme Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: erikdero...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-32-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: i deleted 2 global themes, then directly afterwards applied a newly downloaded global theme (Reactionary). then crash The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #5 0x7fb333c47342 in QQuickItemPrivate::addToDirtyList() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fb333c4bb4e in QQuickItemPrivate::dirty(QQuickItemPrivate::DirtyType) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fb333c4d5e2 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7fb333c4d651 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7fb333c4d783 in QQuickItemPrivate::setVisible(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 371760] New: Amarok crashes while updating tags with MusicBrainz
https://bugs.kde.org/show_bug.cgi?id=371760 Bug ID: 371760 Summary: Amarok crashes while updating tags with MusicBrainz Product: amarok Version: 2.8.0 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: techni...@posteo.de Target Milestone: 2.9 Application: amarok (2.8.0) KDE Platform Version: 4.14.5 Qt Version: 4.8.6 Operating System: Linux 4.4.26-desktop-1.mga5 x86_64 Distribution: "Mageia 5" -- Information about the crash: My Music is located on my NAS and when i updating my tags with MusicBrainz Amarok crashes. The crash can be reproduced every time. -- Backtrace: Application: Amarok (amarok), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe97e8ae800 (LWP 11708))] Thread 15 (Thread 0x7fe954ec4700 (LWP 11710)): #0 0x7fe97b5c1d6d in poll () from /lib64/libc.so.6 #1 0x7fe970fcfc81 in poll_func () from /lib64/libpulse.so.0 #2 0x7fe970fc1891 in pa_mainloop_poll () from /lib64/libpulse.so.0 #3 0x7fe970fc1ece in pa_mainloop_iterate () from /lib64/libpulse.so.0 #4 0x7fe970fc1f80 in pa_mainloop_run () from /lib64/libpulse.so.0 #5 0x7fe970fcfc33 in thread () from /lib64/libpulse.so.0 #6 0x7fe969129198 in internal_thread_func () from /usr/lib64/pulseaudio/libpulsecommon-5.0.so #7 0x7fe9798fd5bd in start_thread () from /lib64/libpthread.so.0 #8 0x7fe97b5cd62d in clone () from /lib64/libc.so.6 Thread 14 (Thread 0x7fe93f9c7700 (LWP 11711)): #0 0x7fe979902a28 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe94a677a8c in my_service_thread_sleep () from /lib64/libmysqld.so.18 #2 0x7fe94a68e657 in ma_checkpoint_background () from /lib64/libmysqld.so.18 #3 0x7fe9798fd5bd in start_thread () from /lib64/libpthread.so.0 #4 0x7fe97b5cd62d in clone () from /lib64/libc.so.6 Thread 13 (Thread 0x7fe93f191700 (LWP 11712)): #0 0x7fe979902a28 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe97bc114d2 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQtCore.so.4 #2 0x7fe97d8deda6 in AbstractDirectoryWatcher::run() () from /lib64/libamaroklib.so.1 #3 0x7fe9789d9942 in ThreadWeaver::JobRunHelper::runTheJob(ThreadWeaver::Thread*, ThreadWeaver::Job*) () from /lib64/libthreadweaver.so.4 #4 0x7fe9789d9b38 in ThreadWeaver::Job::execute(ThreadWeaver::Thread*) () from /lib64/libthreadweaver.so.4 #5 0x7fe9789d933b in ThreadWeaver::Thread::run() () from /lib64/libthreadweaver.so.4 #6 0x7fe97bc10fff in QThreadPrivate::start(void*) () from /lib64/libQtCore.so.4 #7 0x7fe9798fd5bd in start_thread () from /lib64/libpthread.so.0 #8 0x7fe97b5cd62d in clone () from /lib64/libc.so.6 Thread 12 (Thread 0x7fe93e990700 (LWP 11713)): #0 0x7fe97b5c1d6d in poll () from /lib64/libc.so.6 #1 0x7fe974a31eb4 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7fe974a31fbc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7fe97bd3ee3e in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQtCore.so.4 #4 0x7fe97bd10931 in QEventLoop::processEvents(QFlags) () from /lib64/libQtCore.so.4 #5 0x7fe97bd10c45 in QEventLoop::exec(QFlags) () from /lib64/libQtCore.so.4 #6 0x7fe97bc0e899 in QThread::exec() () from /lib64/libQtCore.so.4 #7 0x7fe97bcf23d3 in QInotifyFileSystemWatcherEngine::run() () from /lib64/libQtCore.so.4 #8 0x7fe97bc10fff in QThreadPrivate::start(void*) () from /lib64/libQtCore.so.4 #9 0x7fe9798fd5bd in start_thread () from /lib64/libpthread.so.0 #10 0x7fe97b5cd62d in clone () from /lib64/libc.so.6 Thread 11 (Thread 0x7fe93d809700 (LWP 11714)): #0 0x7fe97990267f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe97bc114f4 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQtCore.so.4 #2 0x7fe9789d7abc in ThreadWeaver::WeaverImpl::blockThreadUntilJobsAreBeingAssigned(ThreadWeaver::Thread*) () from /lib64/libthreadweaver.so.4 #3 0x7fe9789da623 in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, ThreadWeaver::Job*) () from /lib64/libthreadweaver.so.4 #4 0x7fe9789da63c in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, ThreadWeaver::Job*) () from /lib64/libthreadweaver.so.4 #5 0x7fe9789da63c in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, ThreadWeaver::Job*) () from /lib64/libthreadweaver.so.4 #6 0x7fe9789da63c in ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, ThreadWeaver::Job*) () from /lib64/libthreadweaver.so.4 #7 0x7fe9789d929f in ThreadWeaver::Thread::run() () from /lib64/libthreadweaver
[frameworks-kconfig] [Bug 360561] KConfig warnings cannot be silenced
https://bugs.kde.org/show_bug.cgi?id=360561 --- Comment #5 from Erik Quaeghebeur --- (In reply to Martin Gräßlin from comment #3) > > I can confirm this. It seems kwin_x11 is logging this. > > why do you think KWin is logging this? Can you please change the debug > pattern to include the actual process? Sorry, I seem to have missed this comment, but got alerted by comment #4. In any case, if it is still useful: okt 27 18:36:13 kwin_x11[2215]: "\"fsrestore1\" - conversion of \"0,0,0,0\" to QRect failed" okt 27 18:36:13 kwin_x11[2215]: "\"fsrestore2\" - conversion of \"481,481,0,0\" to QRect failed" okt 27 18:36:13 kwin_x11[2215]: "\"fsrestore3\" - conversion of \"481,481,0,0\" to QRect failed" okt 27 18:36:13 kwin_x11[2215]: "\"fsrestore4\" - conversion of \"481,481,0,0\" to QRect failed" okt 27 18:36:13 kwin_x11[2215]: "\"restore5\" - conversion of \"0,0,0,0\" to QRect failed" okt 27 18:36:13 kwin_x11[2215]: "\"fsrestore5\" - conversion of \"0,0,0,0\" to QRect failed" okt 27 18:36:13 kwin_x11[2215]: "\"fsrestore6\" - conversion of \"0,0,0,0\" to QRect failed" okt 27 18:36:13 kwin_x11[2215]: "\"restore7\" - conversion of \"-4,0,797,0\" to QRect failed" okt 27 18:36:13 kwin_x11[2215]: "\"fsrestore7\" - conversion of \"0,0,0,0\" to QRect failed" okt 27 18:36:13 kwin_x11[2215]: "\"restore8\" - conversion of \"1010,0,797,0\" to QRect failed" okt 27 18:36:13 kwin_x11[2215]: "\"fsrestore8\" - conversion of \"0,0,0,0\" to QRect failed" -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 372066] New: kmail mangles the mime structure of some IMAP messages
https://bugs.kde.org/show_bug.cgi?id=372066 Bug ID: 372066 Summary: kmail mangles the mime structure of some IMAP messages Product: kmail2 Version: 4.14.10 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: kdeb...@equaeghe.nospammail.net Target Milestone: --- Created attachment 102027 --> https://bugs.kde.org/attachment.cgi?id=102027&action=edit A diff of the sources of a mail that is mangled by KMail Some mime message structures of IMAP messages are mangled by KMail or the IMAP Akonadi component (please change the component in that case). Namely, border strings are modified(!) and added, resulting in a message with invalid mime, which cannot be parsed correctly anymore by KMail. An example is given in attachment with a diff between the source as returned by Thunderbird and as returned by KMail. My guess is that KMail chokes on mime borders that are very similar or that it cannot distinguish for some reason. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 372074] New: cantor/octave: calling quit() and then stopping calculation crashes whole desktop
https://bugs.kde.org/show_bug.cgi?id=372074 Bug ID: 372074 Summary: cantor/octave: calling quit() and then stopping calculation crashes whole desktop Product: cantor Version: 16.04 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: octave-backend Assignee: m...@noughmad.eu Reporter: kdeb...@equaeghe.nospammail.net CC: alexanderrie...@gmail.com, fil...@kde.org Target Milestone: --- Using the octave backend: when calling `quit()`, cantor keeps on ‘calculating’. Then, when stopping the calculation (clicking the red circle with a cross), the whole desktop crashes. First, all window decorations disappear and an X-styled message window appears (and some windowless password dialogues appear as well, but I think that is not important). The message window says that the ksmserver could not be (re?)started. When clicking that message window's close button, I get thrown back to the login screen. This repeats every time one is stupid enough to try and call quit(). -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 372075] New: cantor/python: application crash when calling quit()
https://bugs.kde.org/show_bug.cgi?id=372075 Bug ID: 372075 Summary: cantor/python: application crash when calling quit() Product: cantor Version: 16.04 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: python2-backend Assignee: fil...@kde.org Reporter: kdeb...@equaeghe.nospammail.net CC: alexanderrie...@gmail.com Target Milestone: --- Created attachment 102030 --> https://bugs.kde.org/attachment.cgi?id=102030&action=edit backtrace Using the python2 backend, when calling `quit()`, cantor crashes. This repeats every time one is stupid enough to call quit(). (probably useless backtrace from DrKonqi in attachment) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 371072] Edit Advanced Search does not show selected labels
https://bugs.kde.org/show_bug.cgi?id=371072 --- Comment #5 from Erik Herlé --- Tested v5.3.0 and it works OK. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 371635] Unable to use keyboard only to process imported photos
https://bugs.kde.org/show_bug.cgi?id=371635 Erik Herlé changed: What|Removed |Added Version|5.2.0 |5.3.0 --- Comment #1 from Erik Herlé --- Discovered this bug in v5.2.0, but is also present in v5.3.0 (just tested on Windows 10 64-bit). -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 372370] New: Kdenlive 16.04.2 reports render time as greater than 24 hours when midnight is crossed during rendering
https://bugs.kde.org/show_bug.cgi?id=372370 Bug ID: 372370 Summary: Kdenlive 16.04.2 reports render time as greater than 24 hours when midnight is crossed during rendering Product: kdenlive Version: 16.04.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: e...@nordstroem.no Target Milestone: --- I started rendering a video just before midnight. When the video was done rendering a few minutes later, the time to render was reported as "1 day 00:08:05". -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 372370] Kdenlive 16.04.2 reports render time as greater than 24 hours when midnight is crossed during rendering
https://bugs.kde.org/show_bug.cgi?id=372370 --- Comment #1 from Erik Nordstrøm --- Created attachment 102179 --> https://bugs.kde.org/attachment.cgi?id=102179&action=edit Photo of notifiaction -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 372370] Kdenlive 16.04.2 reports render time as greater than 24 hours when midnight is crossed during rendering
https://bugs.kde.org/show_bug.cgi?id=372370 Erik Nordstrøm changed: What|Removed |Added Attachment #102179|Photo of notifiaction |Photo of notification description|| -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 372370] Kdenlive 16.04.2 reports render time as greater than 24 hours when midnight is crossed during rendering
https://bugs.kde.org/show_bug.cgi?id=372370 --- Comment #2 from Erik Nordstrøm --- Created attachment 102180 --> https://bugs.kde.org/attachment.cgi?id=102180&action=edit Screenshot of render dialog -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 372370] Kdenlive 16.04.2 reports render time as greater than 24 hours when midnight passes during rendering
https://bugs.kde.org/show_bug.cgi?id=372370 Erik Nordstrøm changed: What|Removed |Added Summary|Kdenlive 16.04.2 reports|Kdenlive 16.04.2 reports |render time as greater than |render time as greater than |24 hours when midnight is |24 hours when midnight |crossed during rendering|passes during rendering -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 372496] New: Support tmux control mode
https://bugs.kde.org/show_bug.cgi?id=372496 Bug ID: 372496 Summary: Support tmux control mode Product: yakuake Version: 3.0.2 Platform: unspecified OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: h...@kde.org Reporter: kdeb...@equaeghe.nospammail.net Target Milestone: --- It would be very nice to have tmux ‘back’ yakuake. Namely, let yakuake tabs be tmux windows and yakuake split screens correspond to tmux split screens. It seems this is possible using ‘control mode’: http://man7.org/linux/man-pages/man1/tmux.1.html#CONTROL_MODE It has been implemented in iTerm2 for Mac: https://gitlab.com/gnachman/iterm2/wikis/TmuxIntegration It would be more convenient to use than tmux itself (better KDE integration) and provides an extra layer in case of window manager/X/yakuake crashes. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 372497] New: plasma-discover crashes while in background
https://bugs.kde.org/show_bug.cgi?id=372497 Bug ID: 372497 Summary: plasma-discover crashes while in background Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: erik.itl...@gmail.com Target Milestone: --- Application: plasma-discover (5.8.3) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.4.0-47-generic x86_64 Distribution: KDE neon User Edition 5.8 -- Information about the crash: - What I was doing when the application crashed: Installing Netbeans on a clean (just installed Neon and only updates + JDK IIRC) -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f565c2348c0 (LWP 1628))] Thread 7 (Thread 0x7f5623fb5700 (LWP 1644)): #0 0x7f5658b0fb5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f56545b339c in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f561c04ec60, timeout=, context=0x7f561c000990) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:4135 #2 0x7f56545b339c in g_main_context_iterate (context=context@entry=0x7f561c000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3835 #3 0x7f56545b34ac in g_main_context_iteration (context=0x7f561c000990, may_block=1) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901 #4 0x7f565974323b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f56596edcea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5659512fb4 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f5659517b98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f565645a70a in start_thread (arg=0x7f5623fb5700) at pthread_create.c:333 #9 0x7f5658b1b82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f5639a99700 (LWP 1633)): #0 0x7fff539b6ab0 in clock_gettime () #1 0x7f5658b29c86 in __GI___clock_gettime (clock_id=1, tp=0x7f5639a98a60) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7f56595bd1c1 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f5659740eb9 in QTimerInfoList::updateCurrentTime() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f5659741425 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f56597427ee in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f56545b292d in g_main_context_prepare (context=context@entry=0x7f5628000990, priority=priority@entry=0x7f5639a98bc0) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3442 #7 0x7f56545b32cb in g_main_context_iterate (context=context@entry=0x7f5628000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3820 #8 0x7f56545b34ac in g_main_context_iteration (context=0x7f5628000990, may_block=1) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901 #9 0x7f565974323b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f56596edcea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f5659512fb4 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f5659517b98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f565645a70a in start_thread (arg=0x7f5639a99700) at pthread_create.c:333 #14 0x7f5658b1b82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f563a29b700 (LWP 1632)): #0 0x7f5658b0fb5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f56545b339c in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f563007e5e0, timeout=, context=0x7f563990) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:4135 #2 0x7f56545b339c in g_main_context_iterate (context=context@entry=0x7f563990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3835 #3 0x7f56545b34ac in g_main_context_iteration (context=0x7f563990, may_block=1) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901 #4 0x7f565974323b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f56596edcea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5659512fb4 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f565bae7aa6 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f565
[kde] [Bug 372499] New: plasma-discover crashes on finishing installation
https://bugs.kde.org/show_bug.cgi?id=372499 Bug ID: 372499 Summary: plasma-discover crashes on finishing installation Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: erik.itl...@gmail.com Target Milestone: --- Application: plasma-discover (5.8.3) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.4.0-47-generic x86_64 Distribution: KDE neon User Edition 5.8 -- Information about the crash: - What I was doing when the application crashed: installed git-cola. As soon as the installation finished the application failed. I reported this a few minutes ago, this report adds to or replaces the previous. The crash can be reproduced sometimes. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f07c4ac18c0 (LWP 14804))] Thread 7 (Thread 0x7f078da8f700 (LWP 14822)): #0 0x7f07bce86ac9 in g_mutex_lock (mutex=mutex@entry=0x7f0788000990) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gthread-posix.c:1335 #1 0x7f07bce41ddc in g_main_context_check (context=context@entry=0x7f0788000990, max_priority=2147483647, fds=fds@entry=0x7f07880404e0, n_fds=n_fds@entry=1) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3683 #2 0x7f07bce42340 in g_main_context_iterate (context=context@entry=0x7f0788000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3837 #3 0x7f07bce424ac in g_main_context_iteration (context=0x7f0788000990, may_block=1) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901 #4 0x7f07c1fd223b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f07c1f7ccea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f07c1da1fb4 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f07c1da6b98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f07bece970a in start_thread (arg=0x7f078da8f700) at pthread_create.c:333 #9 0x7f07c13aa82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f07a2322700 (LWP 14810)): #0 0x7f07c1fd03be in QTimerInfoList::repairTimersIfNeeded() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f07c1fd0433 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f07c1fd17ee in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f07bce4192d in g_main_context_prepare (context=context@entry=0x7f079990, priority=priority@entry=0x7f07a2321bc0) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3442 #4 0x7f07bce422cb in g_main_context_iterate (context=context@entry=0x7f079990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3820 #5 0x7f07bce424ac in g_main_context_iteration (context=0x7f079990, may_block=1) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901 #6 0x7f07c1fd223b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f07c1f7ccea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f07c1da1fb4 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f07c1da6b98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f07bece970a in start_thread (arg=0x7f07a2322700) at pthread_create.c:333 #11 0x7f07c13aa82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f07a2b23700 (LWP 14809)): #0 0x7f07c139a69d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f07bce85740 in g_wakeup_acknowledge (__nbytes=16, __buf=0x7f07a2b22a80, __fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44 #2 0x7f07bce85740 in g_wakeup_acknowledge (wakeup=0x7f079c002390) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gwakeup.c:210 #3 0x7f07bce41e84 in g_main_context_check (context=context@entry=0x7f0798000990, max_priority=2147483647, fds=fds@entry=0x7f079805e7d0, n_fds=n_fds@entry=1) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3632 #4 0x7f07bce42340 in g_main_context_iterate (context=context@entry=0x7f0798000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3837 #5 0x7f07bce424ac in g_main_context_iteration (context=0x7f0798000990, may_block=1) at /build/glib2.0-7IO_Yw/glib2.0-2.48.1/./glib/gmain.c:3901 #6 0x7f07c1fd223b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/lib
[cantor] [Bug 372074] cantor/octave: calling quit() and then stopping calculation crashes whole desktop
https://bugs.kde.org/show_bug.cgi?id=372074 --- Comment #1 from Erik Quaeghebeur --- I had the same type of crash with the Qt5 GUI included with Octave 4.2.0. Perhaps that means the issue is with Octave, or perhaps a similar bug is present there as well: https://savannah.gnu.org/bugs/?func=detailitem&item_id=49609 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 445516] Cache-related visual glitches when Plasma theme SVGs or Plasma Components are updated
https://bugs.kde.org/show_bug.cgi?id=445516 Erik Quaeghebeur changed: What|Removed |Added CC|bugs.kde@e3q.eu | -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 454833] Dutch translation of updates (Bijwerkelement) is a bit awkward
https://bugs.kde.org/show_bug.cgi?id=454833 Erik Quaeghebeur changed: What|Removed |Added CC||bugs.kde@e3q.eu --- Comment #11 from Erik Quaeghebeur --- (In reply to Freek de Kruijf from comment #10) > In all English->Dutch translations of KDE, the words Update or Updates has > been translated as "Element(en) voor bijwerken". […] That sounds quite wrong or at least incomprehensible. I think most Dutch speakers would better understand "updaten" en "een update"/"updates". -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433732] Google Maps labelled "For development purposes only"
https://bugs.kde.org/show_bug.cgi?id=433732 Erik Krause changed: What|Removed |Added CC||erik.kra...@gmx.de --- Comment #28 from Erik Krause --- As a workaround, there should be a possibility for anyone who wants to use Google Maps to supply their own maps API key. This way, anyone will be below the limit... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433732] Google Maps labelled "For development purposes only"
https://bugs.kde.org/show_bug.cgi?id=433732 --- Comment #30 from Erik Krause --- Of course anyone should know about that possibility. However, I doubt a single person will exceed 28,000 map loads a month with just geotagging their images. And you can set a quota limit to avoid unwanted costs. But I concur that in the long run another API should be used, f.e. leaflet.js -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433732] Google Maps labelled "For development purposes only"
https://bugs.kde.org/show_bug.cgi?id=433732 --- Comment #32 from Erik Krause --- Works. Many thanks! For windows the path is \digiKam\data\digikam\geoiface\backend-googlemaps.html Erik -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 440123] Dolphin complains of not enough disk space
https://bugs.kde.org/show_bug.cgi?id=440123 Erik Näslund changed: What|Removed |Added CC||e...@naslund.co --- Comment #2 from Erik Näslund --- I'm experiencing the same thing with a Backblaze bucket mounted using s3fs-fuse. `df` reports 16 exabytes(!) free, and copying files using shell commands work just fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466193] New: Panel disappears after reboot since Frameworks 5.102.0 update
https://bugs.kde.org/show_bug.cgi?id=466193 Bug ID: 466193 Summary: Panel disappears after reboot since Frameworks 5.102.0 update Classification: Plasma Product: plasmashell Version: 5.26.5 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: bugs.kde@e3q.eu CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY Since updating KDE Frameworks from 5.99.0 to 5.102.0 and after rebooting, my panel is gone. I re-created the panel, but after the next boot, it is gone again. This is quite bothersome. I cannot keep on recreating the panel every time, certainly because I do modify it quite a bit from the default. STEPS TO REPRODUCE 1. KDE Frameworks from 5.99.0 to 5.102.0 2. Reboot OBSERVED RESULT No panel EXPECTED RESULT Panel SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION It may be that starting a new session is enough to trigger the issue. But I have not tried that yet. Plasma-related entries in my logs: --- plasmashell[1162]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running. plasmashell[1162]: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable. […] plasmashell[1162]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running. plasmashell[1162]: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable. […] plasmashell[1162]: kf.plasma.quick: Applet preload policy set to 1 […] plasmashell[1162]: org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout --- Here, all but the 5th line are at the error level. The fifth line is at the info level. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466193] Panel disappears after reboot since Frameworks 5.102.0 update
https://bugs.kde.org/show_bug.cgi?id=466193 Erik Quaeghebeur changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Erik Quaeghebeur --- (In reply to Nate Graham from comment #1) > > plasmashell[1162]: Aborting shell load: The activity manager daemon > > (kactivitymanagerd) is not running. > This indicates that your system is broken, so Plasma doesn't load properly. > kactivitymanagerd needs to be running. Any idea why it might not be? I looked a bit broader and kactivitymanagerd is running: --- dbus-daemon[1035]: [session uid=1000 pid=1035] Activating via systemd: service name='org.kde.ActivityManager' unit='plasma-kactivitymanagerd.service' requested by ':1.14' (uid=1000 pid… … systemd[1013]: Starting plasma-kactivitymanagerd.service... … plasmashell[1131]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running. plasmashell[1131]: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable. … dbus-daemon[1035]: [session uid=1000 pid=1035] Successfully activated service 'org.kde.ActivityManager' systemd[1013]: Started plasma-kactivitymanagerd.service. plasmashell[1131]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running. plasmashell[1131]: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable. --- So the first seems to be a race condition: plasmashell expects kactivitymanagerd to be ready while it is still loading. I guess the second time the warning is logged may also be a race condition, but then with output arriving in the log once it has already been resolved (this is all happening within the same second). So it seems that plasmashell should explicitly be told to wait for kactivitymanagerd to be loaded, which is likely another bug. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 466233] New: KMail crashes after restart after akonadi-restart when mail was not being sent
https://bugs.kde.org/show_bug.cgi?id=466233 Bug ID: 466233 Summary: KMail crashes after restart after akonadi-restart when mail was not being sent Classification: Applications Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- Application: kmail (5.21.3 (22.08.3)) (Compiled from sources) Qt Version: 5.15.8 Frameworks Version: 5.102.0 Operating System: Linux 6.1.12-gentoo-c x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.26.5 [KCrashBackend] -- Information about the crash: I tried to send a mail using KMail, but it did not do that. So I restarted akonadi (the go-to solution for most issues…). Then KMail's folder list became empty. So I quit it and restarted. Then KMail crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KMail (kmail), signal: Aborted [KCrash Handler] #4 0x770ecf6b0f9c in () at /usr/lib64/libc.so.6 #5 0x770ecf663b62 in raise () at /usr/lib64/libc.so.6 #6 0x770ecf64e471 in abort () at /usr/lib64/libc.so.6 #7 0x770ecf49e99f in () at /usr/lib/gcc/x86_64-pc-linux-gnu/12/libstdc++.so.6 #8 0x770ecf4aa5d6 in () at /usr/lib/gcc/x86_64-pc-linux-gnu/12/libstdc++.so.6 #9 0x770ecf4aa641 in () at /usr/lib/gcc/x86_64-pc-linux-gnu/12/libstdc++.so.6 #10 0x770ecf4aa8a2 in () at /usr/lib/gcc/x86_64-pc-linux-gnu/12/libstdc++.so.6 #11 0x770ecf890f96 in qBadAlloc() () at /var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/src/corelib/global/qglobal.cpp:3371 #12 0x770ecf89397e in QListData::detach_grow(int*, int) (this=this@entry=0x5d4cd94a8110, idx=idx@entry=0x7ffd8a8d799c, num=num@entry=1) at /var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/src/corelib/tools/qlist.cpp:97 #13 0x770ed056f1ac in QList::detach_helper_grow(int, int) (this=0x5d4cd94a8110, i=, i@entry=2147483647, c=c@entry=1) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/include/QtCore/../../src/corelib/tools/qlist.h:803 #14 0x770ed056f2ad in QList::append(QWidget* const&) (this=, t=@0x7ffd8a8d79f0: 0x5d4ce23f5e40) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/include/QtCore/../../src/corelib/tools/qlist.h:623 #15 0x770ed059d4b0 in QWidget::insertAction(QAction*, QAction*) (this=this@entry=0x5d4ce23f5e40, before=, before@entry=0x0, action=0x5d4cd94bdbd0) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/kernel/qwidget.cpp:3138 #16 0x770ecf3ba982 in KXMLGUI::ActionList::plug(QWidget*, int) const (this=this@entry=0x5d4ce547c9e0, container=0x5d4ce23f5e40, index=) at /var/tmp/portage/kde-frameworks/kxmlgui-5.102.0/work/kxmlgui-5.102.0/src/kxmlguifactory_p.cpp:33 #17 0x770ecf3bf0c3 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&, QTypedArrayData::iterator const&) (this=this@entry=0x5d4cdd7b2050, state=..., mergingIdxIt=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.102.0/work/kxmlgui-5.102.0/src/kxmlguifactory_p.cpp:209 #18 0x770ecf3bf302 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) (this=0x5d4cdd7b2050, state=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.102.0/work/kxmlgui-5.102.0/src/kxmlguifactory_p.cpp:181 #19 0x770ecf3bf335 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) (this=, state=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.102.0/work/kxmlgui-5.102.0/src/kxmlguifactory_p.cpp:185 #20 0x770ecf3bf335 in KXMLGUI::ContainerNode::plugActionList(KXMLGUI::BuildState&) (this=, state=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.102.0/work/kxmlgui-5.102.0/src/kxmlguifactory_p.cpp:185 #21 0x770ecf3b8027 in KXMLGUIFactory::plugActionList(KXMLGUIClient*, QString const&, QList const&) (this=0x5d4ce91e9a90, client=client@entry=0x5d4ce4e1d100, name=..., actionList=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.102.0/work/kxmlgui-5.102.0/src/kxmlguifactory.cpp:564 #22 0x770ecf3aec0d in KXMLGUIClient::plugActionList(QString const&, QList const&) (this=this@entry=0x5d4ce4e1d100, name=..., actionList=...) at /var/tmp/portage/kde-frameworks/kxmlgui-5.102.0/work/kxmlgui-5.102.0/src/kxmlguiclient.cpp:697 #23 0x770ece49d28b in PimCommon::PluginInterface::initializePluginActions(QString const&, KXMLGUIClient*) (this=, prefix=..., guiClient=0x5d4ce4e1d100) at /var/tmp/portage/kde-apps/pimcommon-22.08.3/work/pimcommon-22.08.3/src/pimcommonakonadi/genericplugins/plugininterface.cpp:152 #24 0x770ed8a0beae in KMMainWidget::initializePluginActions() (this=) at /var/tmp/portage/kde-apps/kmail-22.08.3-r2/work/kmail-22.08.3/src/kmmainwidget.cpp:
[Discover] [Bug 466449] New: Discover crashes when manually installing RPM.
https://bugs.kde.org/show_bug.cgi?id=466449 Bug ID: 466449 Summary: Discover crashes when manually installing RPM. Classification: Applications Product: Discover Version: 5.27.0 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: erik.nie...@outlook.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.27.0) Qt Version: 5.15.2 Frameworks Version: 5.103.0 Operating System: Linux 6.1.12-1271.native x86_64 Windowing System: X11 Distribution: Clear Linux OS DrKonqi: 5.27.0 [KCrashBackend] -- Information about the crash: When installing a third party RPM, like Google Chrome, Discover immediately crashes. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #6 doActivate () at kernel/qobject.cpp:3803 #7 0x55a62211c152 in ResultsStream::resourcesFound () at /builddir/build/BUILD/discover-5.27.0/clr-build/libdiscover/DiscoverCommon_autogen/3YJK5W5UP7/moc_AbstractResourcesBackend.cpp:159 #8 0x55a5f4fc7137 in operator() () at /builddir/build/BUILD/discover-5.27.0/libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp:1586 #9 call () at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #10 call, void> () at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #11 impl () at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #12 0x55a61f7eda85 in QObject::event () at kernel/qobject.cpp:1347 #13 0x55a621640543 in QApplicationPrivate::notify_helper () at kernel/qapplication.cpp:3637 #14 0x55a61f7c2778 in QCoreApplication::notifyInternal2 () at kernel/qcoreapplication.cpp:1064 #15 0x55a61f7c2a06 in QCoreApplication::sendEvent () at kernel/qcoreapplication.cpp:1462 #16 QCoreApplicationPrivate::sendPostedEvents () at kernel/qcoreapplication.cpp:1821 #17 0x55a61f81ad40 in QCoreApplication::sendPostedEvents () at kernel/qcoreapplication.cpp:1680 #18 postEventSourceDispatch () at kernel/qeventdispatcher_glib.cpp:277 #19 0x55a61ebdc141 in g_main_dispatch () at ../glib/gmain.c:3454 #20 g_main_context_dispatch () at ../glib/gmain.c:4172 #21 0x55a61ec6955b in g_main_context_iterate.constprop.0 () at ../glib/gmain.c:4248 #22 0x55a61ebda0d5 in g_main_context_iteration () at ../glib/gmain.c:4313 #23 0x55a61f819bfe in QEventDispatcherGlib::processEvents () at kernel/qeventdispatcher_glib.cpp:423 #24 0x55a61f7bfda6 in QEventLoop::processEvents () at kernel/qeventloop.cpp:139 #25 QEventLoop::exec () at kernel/qeventloop.cpp:232 #26 0x55a61f7c2f83 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1375 #27 0x55a6222c2278 in main () at /builddir/build/BUILD/discover-5.27.0/discover/main.cpp:224 [Inferior 1 (process 11767) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466193] Panel disappears after reboot since Frameworks 5.102.0 update
https://bugs.kde.org/show_bug.cgi?id=466193 --- Comment #4 from Erik Quaeghebeur --- (In reply to Nate Graham from comment #3) > Hmm, kactivitymanagerd's service file has this in it: > > Before=graphical-session.target But is graphical-session.target the one that matters here? I have the feeling it is not. In the log, I see --- systemd[1128]: Starting plasma-kactivitymanagerd.service... systemd[1128]: Started plasma-plasmashell.service. --- So plasmashell is started essentially concurrently with kactivitymanagerd. This is not strange, as we can see from their unit sections in their service files: ---plasma-plasmashell.service--- [Unit] Description=KDE Plasma Workspace After=plasma-ksmserver.service plasma-kcminit.service PartOf=graphical-session.target --- ---plasma-kactivitymanagerd.service--- [Unit] Description=KActivityManager Activity manager Service PartOf=graphical-session.target Before=graphical-session.target --- So AFAIU, in plasma-plasmashell.service, we should have the following as the ‘After’ line: --- After=plasma-ksmserver.service plasma-kcminit.service plasma-kactivitymanagerd.service --- -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 463222] kalendarac crashes when restarting Akonadi
https://bugs.kde.org/show_bug.cgi?id=463222 --- Comment #1 from Erik Quaeghebeur --- Created attachment 156794 --> https://bugs.kde.org/attachment.cgi?id=156794&action=edit New crash information added by DrKonqi kalendarac (5.21.3) using Qt 5.15.8 I restarted Akonadi and then the reminder app crashed -- Backtrace (Reduced): #7 0x718694e91d6b in qt_message_fatal (message=..., context=...) at /var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/src/corelib/global/qlogging.cpp:1914 #8 QMessageLogger::fatal (this=this@entry=0x76840ed0, msg=msg@entry=0x718693f2f258 "QWidget: Cannot create a QWidget without QApplication") at /var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/src/corelib/global/qlogging.cpp:893 #9 0x718693b57cad in QWidgetPrivate::init (this=0x5b1fb3876d30, parentWidget=0x0, f=...) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/kernel/qwidget.cpp:983 #10 0x718693d78c90 in QDialog::QDialog (this=0x5b1fad64b9d0, parent=0x0, f=...) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/include/QtCore/../../src/corelib/tools/qsharedpointer_impl.h:679 #11 0x7186942c49df in KMessageBox::sorry(QWidget*, QString const&, QString const&, QFlags) () from /usr/lib64/libKF5WidgetsAddons.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 463222] kalendarac crashes when restarting Akonadi
https://bugs.kde.org/show_bug.cgi?id=463222 Erik Quaeghebeur changed: What|Removed |Added CC||bugs.kde@e3q.eu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466649] New: Panel activity switcher text disappears
https://bugs.kde.org/show_bug.cgi?id=466649 Bug ID: 466649 Summary: Panel activity switcher text disappears Classification: Plasma Product: plasmashell Version: 5.26.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bugs.kde@e3q.eu CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 156865 --> https://bugs.kde.org/attachment.cgi?id=156865&action=edit Screenshot showing invisible text in panel activity switcher SUMMARY I found myself without activity names in the panel activity switcher (not the one at the side of the screen, but the plasmoid one with a list of activity names one can put in the panel). Namely, all text was gone, while the highlight of the current activity was still there and while one could still click the (invisible) activity names to switch (please see attached screenshot). Removing and readding the plasmoid fixed it for me for now. The only atypical thing is that before I had used a projector as an additional screen for a while. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 452789] Krusader crashes when F3-viewing docx file
https://bugs.kde.org/show_bug.cgi?id=452789 Erik Quaeghebeur changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #2 from Erik Quaeghebeur --- It does not happen anymore for me with 2.8.0. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466193] Panel disappears after reboot since Frameworks 5.102.0 update
https://bugs.kde.org/show_bug.cgi?id=466193 --- Comment #7 from Erik Quaeghebeur --- Created attachment 156989 --> https://bugs.kde.org/attachment.cgi?id=156989&action=edit Journal output until and including issue (In reply to David Edmundson from comment #6) > > If you get the error listed it means plasmashell explicitly thinks kamd > failed to start rather than a race. Can you attach the non-abridged logs. These are the non-abridged logs up until and including the issue. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 466913] New: Feature request: select only some calendars in collection
https://bugs.kde.org/show_bug.cgi?id=466913 Bug ID: 466913 Summary: Feature request: select only some calendars in collection Classification: Frameworks and Libraries Product: Akonadi Version: 5.21.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: DAV Resource Assignee: kdepim-b...@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- Caldav collections can have multiple calendars. Sometimes one does not wish to synchronize all of them. (I have one which very often causes the resource to get stuck…) It would be convenient to have the possibility to only synchronize a selected subset of the available calendars. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 467050] New: Crash after mail composition
https://bugs.kde.org/show_bug.cgi?id=467050 Bug ID: 467050 Summary: Crash after mail composition Classification: Applications Product: trojita Version: git Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Other Assignee: trojita-b...@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- After mail composition (which itself works), Trojitá crashes. From the stack trace (at end), I have the impression it is related to Sonnet integration. This started happening after updating Frameworks to 5.102. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 STACK TRACE Stack trace of thread 281971: #0 0x72e9bb2b4cb0 _ZNKSt13__atomic_baseIiE4loadESt12memory_order (libQt5Core.so.5 + 0x2b4cb0) #1 0x72e98e2b9f26 _ZN6Sonnet19SpellCheckDecoratorD1Ev (libKF5SonnetUi.so.5 + 0x21f26) #2 0x72e98e2b9f59 _ZN6Sonnet19SpellCheckDecoratorD0Ev (libKF5SonnetUi.so.5 + 0x21f59) #3 0x72e9bb2af422 _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5 + 0x2af422) #4 0x72e9c07a2926 _ZN7QWidgetD2Ev (libQt5Widgets.so.5 + 0x1a2926) #5 0x5cf8300efef4 n/a (trojita + 0xa1ef4) #6 0x72e9bb2af422 _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5 + 0x2af422) #7 0x72e9c07a2926 _ZN7QWidgetD2Ev (libQt5Widgets.so.5 + 0x1a2926) #8 0x72e9c091f089 _ZN9QSplitterD0Ev (libQt5Widgets.so.5 + 0x31f089) #9 0x72e9bb2af422 _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5 + 0x2af422) #10 0x72e9c07a2926 _ZN7QWidgetD2Ev (libQt5Widgets.so.5 + 0x1a2926) #11 0x5cf8300fd109 n/a (trojita + 0xaf109) #12 0x72e9bb2af61f _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2af61f) #13 0x72e9c076344e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x16344e) #14 0x72e9bb283ef8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x283ef8) #15 0x72e9bb287433 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x287433) #16 0x72e9bb2d6693 postEventSourceDispatch (libQt5Core.so.5 + 0x2d6693) #17 0x72e9b922cdc8 g_main_context_dispatch (libglib-2.0.so.0 + 0x55dc8) #18 0x72e9b922d068 n/a (libglib-2.0.so.0 + 0x56068) #19 0x72e9b922d0fc g_main_context_iteration (libglib-2.0.so.0 + 0x560fc) #20 0x72e9bb2d6196 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d6196) #21 0x72e9bb28291b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x28291b) #22 0x72e9bb28abf6 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x28abf6) #23 0x5cf8300e1238 n/a (trojita + 0x93238) #24 0x72e9bae4f34a n/a (libc.so.6 + 0x2334a) #25 0x72e9bae4f3fc __libc_start_main (libc.so.6 + 0x233fc) #26 0x5cf8300e2c71 n/a (trojita + 0x94c71) Stack trace of thread 281972: #0 0x72e9baf2268f __poll (libc.so.6 + 0xf668f) #1 0x72e9b900ad82 n/a (libxcb.so.1 + 0xcd82) #2 0x72e9b900d23a xcb_wait_for_event (libxcb.so.1 + 0xf23a) #3 0x72e9b69204e8 _ZN14QXcbEventQueue3runEv (libQt5XcbQpa.so.5 + 0x664e8) #4 0x72e9bb0cbc77 _ZN14QThreadPrivate5startEPv (libQt5Core.so.5 + 0xcbc77) #5 0x72e9baeaf36a n/a (libc.so.6 + 0x8336a) #6 0x72e9baf303bc n/a (libc.so.6 + 0x1043bc) Stack trace of thread 281974: #0 0x72e9baeabef6 n/a (libc.so.6 + 0x7fef6) #1 0x72e9baeae73f pthread_cond_wait (libc.so.6 + 0x8273f) #2 0x72e9aeecb7a9 n/a (radeonsi_dri.so + 0xcb7a9) #3 0x72e9aee7d16b n/a (radeonsi_dri.so + 0x7d16b) #4 0x72e9aeecb6e7 n/a (radeonsi_dri.so + 0xcb6e7) #5 0x72e9baeaf36a n/a (libc.so.6 + 0x8336a) #6 0x72e9baf303bc n/a (libc.so.6 + 0x1043bc) Stack trace of thread 281981: #0 0x72e9baeabef6 n/a (libc.so.6 + 0x7fef6) #1 0x72e9baeae73f pthread_cond_wait (libc.so.6 + 0x8273f) #2 0x72e9baca8b03 _ZNSt18condition_variable4waitERSt11unique_lockISt5mutexE (libs #3 0x72e9bce9eaea _ZN3WTF10ParkingLot17parkConditionallyEPKvSt8functionIFbvEES3_IFvvEENSt6chrono10time_pointINS8_3_V212steady_clockENS8_8durationIlSt5ratioILl1ELl10EE (libQt5WebKit.so.5 + 0x109eaea) #4 0x72e9bce9cd58 n/a (libQt5WebKit.so.5 + 0x109cd58) #5 0x72e9bcea1d83 n/a (libQt5WebKit.so.5 + 0x10a1d83) #6 0x72e9bcecae9b n/a (libQt5WebKit.so.5 + 0x10cae9b) #7 0x72e9baeaf36a n/a (libc.so.6 + 0x8336a) #8 0x72e9baf303bc n/a (libc.so.6 + 0x1043bc) Stack trace of thread 281984: #0 0x72e9baeabef6 n/a (libc.so.6 + 0x7fef6) #1 0x72e9baeae73f pthread_cond_wait (libc.so.6 + 0x8273f) #2 0x72e9baca8b03 _ZNSt18condition_variable4waitERSt11unique_lockISt5mutexE (libstdc++.so.6 + 0xa8b03) #3 0x72e9bce9eaea _ZN3WTF10ParkingLot17parkConditionallyEPKvSt8functionIFbvEES3_IFvvEENSt6chrono10time_pointINS8_3_V212steady_clockENS8_8durationIlSt5ratioILl1ELl100
[trojita] [Bug 467051] New: Crash when typing in a recipient box when using Akonadi Contact plugin
https://bugs.kde.org/show_bug.cgi?id=467051 Bug ID: 467051 Summary: Crash when typing in a recipient box when using Akonadi Contact plugin Classification: Applications Product: trojita Version: git Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Other Assignee: trojita-b...@kde.org Reporter: bugs.kde@e3q.eu CC: trojita-b...@kde.org Target Milestone: --- SUMMARY During mail composition, Trojitá crashes when typing in a recipient box (To, Cc,…). From the stack trace (at end), I have the impression it is related to Akonadi Contact integration. This started happening after updating Trojita to the latest git version (was using a git checkout of a few years old before). SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 STACK TRACE Stack trace of thread 282058: #0 0x77c9f51079b5 _Z5qHashRK7QStringj (libQt5Core.so.5 + 0x1079b5) #1 0x77c9e006756b n/a (trojita_plugin_AkonadiAddressbookPlugin.so + 0x756b) #2 0x77c9e00660ad n/a (trojita_plugin_AkonadiAddressbookPlugin.so + 0x60ad) #3 0x77c9f52b79c4 _ZN9QtPrivate15QSlotObjectBase4callEP7QObjectPPv (libQt5Core.so.5 + 0x2b79c4) #4 0x77c9ef48b6b3 _ZN4KJob6resultEPS_NS_14QPrivateSignalE (libKF5CoreAddons.so.5 + 0x6e6b3) #5 0x77c9ef48cb8b _ZN4KJob9finishJobEb (libKF5CoreAddons.so.5 + 0x6fb8b) #6 0x77c9f52af874 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2af874) #7 0x77c9fa76344e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x16344e) #8 0x77c9f5283ef8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x283ef8) #9 0x77c9f5287433 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x287433) #10 0x77c9f52d6693 postEventSourceDispatch (libQt5Core.so.5 + 0x2d6693) #11 0x77c9f3126dc8 g_main_context_dispatch (libglib-2.0.so.0 + 0x55dc8) #12 0x77c9f3127068 n/a (libglib-2.0.so.0 + 0x56068) #13 0x77c9f31270fc g_main_context_iteration (libglib-2.0.so.0 + 0x560fc) #14 0x77c9f52d6196 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2d6196) #15 0x77c9f528291b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x28291b) #16 0x77c9f528abf6 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x28abf6) #17 0x610d7274e238 n/a (trojita + 0x93238) #18 0x77c9f4e4f34a n/a (libc.so.6 + 0x2334a) #19 0x77c9f4e4f3fc __libc_start_main (libc.so.6 + 0x233fc) #20 0x610d7274fc71 n/a (trojita + 0x94c71) Stack trace of thread 282068: #0 0x77c9f4eabef6 n/a (libc.so.6 + 0x7fef6) #1 0x77c9f4eae73f pthread_cond_wait (libc.so.6 + 0x8273f) #2 0x77c9f4ca8b03 _ZNSt18condition_variable4waitERSt11unique_lockISt5mutexE (libstdc++.so.6 + 0xa8b03) #3 0x77c9f6e9eaea _ZN3WTF10ParkingLot17parkConditionallyEPKvSt8functionIFbvEES3_IFvvEENSt6chrono10time_pointINS8_3_V212steady_clockENS8_8durationIlSt5ratioILl1ELl10EE (libQt5WebKit.so.5 + 0x109eaea) #4 0x77c9f6e9cd58 n/a (libQt5WebKit.so.5 + 0x109cd58) #5 0x77c9f6ea1d83 n/a (libQt5WebKit.so.5 + 0x10a1d83) #6 0x77c9f6ecae9b n/a (libQt5WebKit.so.5 + 0x10cae9b) #7 0x77c9f4eaf36a n/a (libc.so.6 + 0x8336a) #8 0x77c9f4f303bc n/a (libc.so.6 + 0x1043bc) Stack trace of thread 282062: #0 0x77c9f4eabef6 n/a (libc.so.6 + 0x7fef6) #1 0x77c9f4eae73f pthread_cond_wait (libc.so.6 + 0x8273f) #2 0x77c9ed8cb7a9 n/a (radeonsi_dri.so + 0xcb7a9) #3 0x77c9ed87d16b n/a (radeonsi_dri.so + 0x7d16b) #4 0x77c9ed8cb6e7 n/a (radeonsi_dri.so + 0xcb6e7) #5 0x77c9f4eaf36a n/a (libc.so.6 + 0x8336a) #6 0x77c9f4f303bc n/a (libc.so.6 + 0x1043bc) Stack trace of thread 282071: #0 0x77c9f4eabef6 n/a (libc.so.6 + 0x7fef6) #1 0x77c9f4eae73f pthread_cond_wait (libc.so.6 + 0x8273f) #2 0x77c9f4ca8b03 _ZNSt18condition_variable4waitERSt11unique_lockISt5mutexE (libstdc++.so.6 + 0xa8b03) #3 0x77c9f6e9eaea _ZN3WTF10ParkingLot17parkConditionallyEPKvSt8functionIFbvEES3_IFvvEENSt6chrono10time_pointINS8_3_V212steady_clockENS8_8durationIlSt5ratioILl1ELl10EE (libQt5WebKit.so.5 + 0x109eaea) #4 0x77c9f6e9cd58 n/a (libQt5WebKit.so.5 + 0x109cd58) #5 0x77c9f6ea1d83 n/a (libQt5WebKit.so.5 + 0x10a1d83) #6 0x77c9f6ecae9b n/a (libQt5WebKit.so.5 + 0x10cae9b) #7 0x77c9f4eaf36a n/a (libc.so.6 + 0x8336a) #8 0x77c9f4f303bc n/a (libc.so.6 + 0x1043bc) Stack trace of thread 282060: #0 0x77c9f4eabef6 n/a (libc.so.6 + 0x7fef6) #1 0x77c9f4eae73f pthread_cond_wait (libc.so.6 + 0x8273f) #2 0x77c9ed8cb7a9 n/a (radeonsi_dri.so + 0xcb7a9) #3 0x77c9ed87d16b n/a (radeonsi_dri.so + 0x7d16b) #4 0x77c9ed8cb6e7 n/a (radeonsi_dri.so + 0xcb6e7) #5 0x77c9f4e
[trojita] [Bug 436157] Outdated path for *.po files in «l10n-fetch-po-files.py»
https://bugs.kde.org/show_bug.cgi?id=436157 Erik Quaeghebeur changed: What|Removed |Added Resolution|--- |FIXED CC||bugs.kde@e3q.eu Status|REPORTED|RESOLVED --- Comment #1 from Erik Quaeghebeur --- Fixed with https://invent.kde.org/pim/trojita/-/commit/e6d5a4472fce80f4028a1125e06d5766bab73cf2 -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 467051] Crash when typing in a recipient box when using Akonadi Contact plugin
https://bugs.kde.org/show_bug.cgi?id=467051 --- Comment #1 from Erik Quaeghebeur --- To be clear: the crash does not happen when the Akonadi contact integration plugin is not compiled-in. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 467050] Crash after mail composition
https://bugs.kde.org/show_bug.cgi?id=467050 --- Comment #1 from Erik Quaeghebeur --- To be clear: the crash does not happen when the Sonnet plugin is not compiled-in. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 391718] ASSERT: "it != ptrToInternal.constEnd()" in file trojita/src/Imap/Model/ThreadingMsgListModel.cpp, line 1488
https://bugs.kde.org/show_bug.cgi?id=391718 Erik Quaeghebeur changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO CC||bugs.kde@e3q.eu Resolution|--- |WORKSFORME --- Comment #4 from Erik Quaeghebeur --- (In reply to Jan Kundrát from comment #3) > > 1) activate threading > 2) open a mailbox > 3) perform a search which returns something > 4) switch to another mailbox where that search doesn't return anything > 5) the threading is still preserved, and trojita assert-crashes: > > ASSERT: "it != ptrToInternal.constEnd()" in file > trojita/src/Imap/Model/ThreadingMsgListModel.cpp, line 1488 I cannot reproduce this with my current Trojitá (~git master). So unless someone can reproduce it with a recent version (from git), I suggest we close this. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 467266] New: KMail crashes when saving a pdf attachment
https://bugs.kde.org/show_bug.cgi?id=467266 Bug ID: 467266 Summary: KMail crashes when saving a pdf attachment Classification: Applications Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- Application: kmail (5.21.3 (22.08.3)) (Compiled from sources) Qt Version: 5.15.8 Frameworks Version: 5.102.0 Operating System: Linux 6.1.12-gentoo-d x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.26.5 [KCrashBackend] -- Information about the crash: KMail crashed when saving a pdf attachment. The crash happens after the save file dialog has been opened and the moment the button to Save is pressed. (The file is not saved.) This has happened before a few times now. But it also happens that saving does work. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 0x70dc6574049e in QVector::begin(QTypedArrayData::const_iterator) const (this=) at /usr/include/qt5/QtCore/qvector.h:220 #5 KMime::Content::headerByType(char const*) const (this=this@entry=0x630ae9dec5b0, type=0x70dc6575ca0c "Content-Transfer-Encoding") at /var/tmp/portage/kde-apps/kmime-22.08.3/work/kmime-22.08.3/src/kmime_content.cpp:617 #6 0x70dc65741a19 in KMime::Content::header(bool) (create=true, this=0x630ae9dec5b0) at /var/tmp/portage/kde-apps/kmime-22.08.3/work/kmime-22.08.3/src/kmime_content.h:681 #7 KMime::Content::contentTransferEncoding(bool) (this=0x630ae9dec5b0, create=) at /var/tmp/portage/kde-apps/kmime-22.08.3/work/kmime-22.08.3/src/kmime_content.cpp:874 #8 0x70dc65741aa3 in KMime::Content::decodedContent() (this=0x630ae9dec5b0) at /var/tmp/portage/kde-apps/kmime-22.08.3/work/kmime-22.08.3/src/kmime_content.cpp:316 #9 0x70dc6631627e in MessageViewer::Util::saveContent(QWidget*, KMime::Content*, QUrl const&) (parent=0x630ae4cae770, content=, url=...) at /var/tmp/portage/kde-apps/messagelib-22.08.3/work/messagelib-22.08.3/messageviewer/src/utils/messageviewerutil.cpp:421 #10 0x70dc66317f1e in MessageViewer::Util::saveContents(QWidget*, QVector const&, QList&) (parent=0x630ae4cae770, contents=..., urlList=...) at /var/tmp/portage/kde-apps/messagelib-22.08.3/work/messagelib-22.08.3/messageviewer/src/utils/messageviewerutil.cpp:324 #11 0x70dc662d3a61 in MessageViewer::ViewerPrivate::slotHandleAttachment(int) (this=0x630ae4d71460, choice=) at /var/tmp/portage/kde-apps/messagelib-22.08.3/work/messagelib-22.08.3/messageviewer/src/viewer/viewer_p.cpp:2611 #12 0x70dc672b79c4 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffcd657e5b0, r=0x630ae4d71460, this=0x630ae83e2890) at /var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate(QObject*, int, void**) (sender=0x630ae6cd8d80, signal_index=4, argv=0x7ffcd657e5b0) at /var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/src/corelib/kernel/qobject.cpp:3923 #14 0x70dc672b1707 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x630ae6cd8d80, m=m@entry=0x70dc6828fd00 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffcd657e5b0) at /var/tmp/portage/dev-qt/qtcore-5.15.8-r3/work/qtbase-everywhere-src-5.15.8/src/corelib/kernel/qobject.cpp:3983 #15 0x70dc67d5c8b2 in QAction::triggered(bool) (this=this@entry=0x630ae6cd8d80, _t1=) at .moc/moc_qaction.cpp:376 #16 0x70dc67d5f64b in QAction::activate(QAction::ActionEvent) (this=0x630ae6cd8d80, event=) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/kernel/qaction.cpp:1161 #17 0x70dc67eeea8a in QMenuPrivate::activateCausedStack(QVector > const&, QAction*, QAction::ActionEvent, bool) (this=this@entry=0x630aee197cc0, causedStack=..., action=action@entry=0x630ae6cd8d80, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/widgets/qmenu.cpp:1384 #18 0x70dc67ef6aec in QMenuPrivate::activateAction(QAction*, QAction::ActionEvent, bool) (this=0x630aee197cc0, action=0x630ae6cd8d80, action_e=QAction::Trigger, self=) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/widgets/qmenu.cpp:1461 #19 0x70dc67da7028 in QWidget::event(QEvent*) (this=0x7ffcd657f3c0, event=0x7ffcd657ebc0) at /var/tmp/portage/dev-qt/qtwidgets-5.15.8-r2/work/qtbase-everywhere-src-5.15.8/src/widgets/kernel/qwidget.cpp:9045 #20 0x70dc67d6344e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0x630ae48451e0, receiv
[kmail2] [Bug 467266] KMail crashes when saving a pdf attachment
https://bugs.kde.org/show_bug.cgi?id=467266 Erik Quaeghebeur changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Erik Quaeghebeur --- *** This bug has been marked as a duplicate of bug 454257 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 454257] Crash on save of attachment (tar.gz)
https://bugs.kde.org/show_bug.cgi?id=454257 Erik Quaeghebeur changed: What|Removed |Added CC||bugs.kde@e3q.eu --- Comment #2 from Erik Quaeghebeur --- *** Bug 467266 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 454257] Crash on save of attachment
https://bugs.kde.org/show_bug.cgi?id=454257 Erik Quaeghebeur changed: What|Removed |Added Summary|Crash on save of attachment |Crash on save of attachment |(tar.gz)| --- Comment #3 from Erik Quaeghebeur --- (In reply to Erik Quaeghebeur from comment #2) > *** Bug 467266 has been marked as a duplicate of this bug. *** My encounter shows it is not limited to tar.gz, but can also occur, e.g., with pdfs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466193] Panel disappears after reboot since Frameworks 5.102.0 update
https://bugs.kde.org/show_bug.cgi?id=466193 Erik Quaeghebeur changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396665] Font browser crash
https://bugs.kde.org/show_bug.cgi?id=396665 --- Comment #6 from Erik Quaeghebeur --- (In reply to Justin Zobel from comment #5) > […] if you can reproduce the crash with a recent software version? I cannot reproduce it currently. Perhaps k...@trummer.xyz can have a look, as they seemed to have tested it more extensively. -- You are receiving this mail because: You are watching all bug changes.
[Reminder Daemon] [Bug 453676] Meeting reminder flood and sometimes kalendarac crashes after login
https://bugs.kde.org/show_bug.cgi?id=453676 --- Comment #2 from Erik Quaeghebeur --- Created attachment 152330 --> https://bugs.kde.org/attachment.cgi?id=152330&action=edit New crash information added by DrKonqi kalendarac (5.20.3) using Qt 5.15.5 - What I was doing when the application crashed: I was restaring the akonadi server via akonadiconsole -- Backtrace (Reduced): #7 0x795014e07cd7 in qt_message_fatal (message=..., context=...) at /var/tmp/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/global/qlogging.cpp:1914 #8 QMessageLogger::fatal (this=this@entry=0x7fffb4012a00, msg=msg@entry=0x795013ef8198 "QWidget: Cannot create a QWidget without QApplication") at /var/tmp/portage/dev-qt/qtcore-5.15.5-r3/work/qtbase-everywhere-src-5.15.5/src/corelib/global/qlogging.cpp:893 #9 0x795013b21d42 in QWidgetPrivate::init (this=, parentWidget=, f=...) at /var/tmp/portage/dev-qt/qtwidgets-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/src/widgets/kernel/qwidget.cpp:981 #10 0x795013d413bf in QDialog::QDialog (this=0x639898de1050, parent=0x0, f=...) at /var/tmp/portage/dev-qt/qtwidgets-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/src/widgets/dialogs/qdialog.cpp:400 #11 0x7950141c0ece in KMessageBox::sorry(QWidget*, QString const&, QString const&, QFlags) () from /usr/lib64/libKF5WidgetsAddons.so.5 -- You are receiving this mail because: You are watching all bug changes.
[Reminder Daemon] [Bug 453676] Meeting reminder flood and sometimes kalendarac crashes after login
https://bugs.kde.org/show_bug.cgi?id=453676 Erik Quaeghebeur changed: What|Removed |Added CC||bugs.kde@e3q.eu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459594] New: desktop grid prevents lock screen and lid close suspend activation
https://bugs.kde.org/show_bug.cgi?id=459594 Bug ID: 459594 Summary: desktop grid prevents lock screen and lid close suspend activation Classification: Plasma Product: kwin Version: 5.24.6 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- SUMMARY When the desktop grid effect is active, the lock screen does not activate after the normal timeout and upon laptop lid close the configured suspend action is not activated. This means that when the desktop grid effect is (unintendedly) active, I run a security risk and there is also a risk of hardware damage (true story: sliding mouse on train activates desktop grid without me knowing, I close the laptop lid to get off, put the laptop in the sleeve and then it just starts heating up; scary as hell when two hours later you notice the laptop is very hot and there is a black screen). STEPS TO REPRODUCE 1. activate desktop grid 2. wait for lock screen timeout or close laptop lid OBSERVED RESULT computer stays on in desktop grid EXPECTED RESULT computer goes to lock screen or suspends SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459594] desktop grid prevents lock screen and lid close suspend activation
https://bugs.kde.org/show_bug.cgi?id=459594 --- Comment #2 from Erik Quaeghebeur --- (In reply to veggero from comment #1) > Cannot reproduce by turning on desktop grid (via touchpad gesture) and > closing the laptop lid on any of my laptops Hmm, I'll test that again. What about the lock screen not appearing? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459594] desktop grid prevents lock screen activation
https://bugs.kde.org/show_bug.cgi?id=459594 Erik Quaeghebeur changed: What|Removed |Added Summary|desktop grid prevents lock |desktop grid prevents lock |screen and lid close|screen activation |suspend activation | --- Comment #3 from Erik Quaeghebeur --- (In reply to Erik Quaeghebeur from comment #2) > (In reply to veggero from comment #1) > > Cannot reproduce by turning on desktop grid (via touchpad gesture) and > > closing the laptop lid on any of my laptops > > Hmm, I'll test that again. I can't reproduce it again either. Either this was fixed recently, or there is another reason for the non-suspending behavior. The lock screen activation not working is easy to reproduce for me. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459594] desktop grid prevents lock screen activation
https://bugs.kde.org/show_bug.cgi?id=459594 --- Comment #5 from Erik Quaeghebeur --- (In reply to Nate Graham from comment #4) > Was this happening on Wayland or X11? X11. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466649] Panel activity switcher text disappears
https://bugs.kde.org/show_bug.cgi?id=466649 --- Comment #2 from Erik Quaeghebeur --- (In reply to Nate Graham from comment #1) > > *** This bug has been marked as a duplicate of bug 445828 *** I very much doubt this is a duplicate of the linked report. What made you decide it is? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466649] Panel activity switcher text disappears
https://bugs.kde.org/show_bug.cgi?id=466649 --- Comment #4 from Erik Quaeghebeur --- (In reply to Nate Graham from comment #3) > Similar symptoms as Bug 445828. Does the text re-appear when the panel is > made taller? If not, then I was wrong and it's something else. I cannot reproduce it myself. It sometimes happens. However, it was not related to panel height changes and the text became invisible, but could still be clicked, which is different from the other report. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 392440] UID consistency error
https://bugs.kde.org/show_bug.cgi?id=392440 Erik Quaeghebeur changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 468482] New: UnrecognizedResponseKind: HIGHESTMODSEQ
https://bugs.kde.org/show_bug.cgi?id=468482 Bug ID: 468482 Summary: UnrecognizedResponseKind: HIGHESTMODSEQ Classification: Applications Product: trojita Version: git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: IMAP Assignee: trojita-b...@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- Trojitá told me to report the following: --- UnrecognizedResponseKind: HIGHESTMODSEQ * STATUS INBOX (UIDVALIDITY 1164751602 UNSEEN 0 HIGHESTMODSEQ 5796796) --- This is on a Fastmail connection. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 468482] UnrecognizedResponseKind: HIGHESTMODSEQ
https://bugs.kde.org/show_bug.cgi?id=468482 --- Comment #2 from Erik Quaeghebeur --- (In reply to Jan Kundrát from comment #1) > Can you please provide a bit larger context, including the IMAP command to > which Fastmail replied with this response, as well as the full error message > as reported by Trojita? Context from protocol log: --- 22:09:37.239 Imap::Mailbox::ExpungeMailboxTask Activated 22:09:37.239 >>> y389 EXPUNGE␍␊ 22:09:37.364 <<< * VANISHED 10635:10637␍␊ 22:09:37.365 <<< y389 OK [HIGHESTMODSEQ 5796805] Completed␍␊ 22:09:37.367 Imap::Mailbox::ExpungeMailboxTask Completed 22:09:43.463 >>> y390 IDLE␍␊ 22:09:43.571 <<< + idling␍␊ 22:09:43.675 <<< * STATUS INBOX (UIDVALIDITY 1164751602 UNSEEN 0 HIGHESTMODSEQ 5796796)␍␊ 22:09:43.675 UnrecognizedResponseKind HIGHESTMODSEQ␊* STATUS INBOX (UIDVALIDITY 1164751602 UNSEEN 0 HIGHESTMODSEQ 5796796)␍␊␊ ^ here 22:09:43.676 conn Logged out. 22:09:43.685 *** Connection killed. --- I don't have the full error message. It was the standard one, paraphrasing, “I've encountered an issue which is likely on the server side but may be a Trojita bug, so report it anyway.” and then the log excerpt I gave, with the ‘^ here’ pointing at the end of the number 5796796. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 468482] UnrecognizedResponseKind: HIGHESTMODSEQ
https://bugs.kde.org/show_bug.cgi?id=468482 --- Comment #4 from Erik Quaeghebeur --- (In reply to Jan Kundrát from comment #3) > and just to double-check, this was while you had your INBOX open, right? Likely, but not sure. I came back to the Trojita window from another virtual desktop and the message was there. I didn't pay attention to the opened folder. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466649] [Activity Pager] Panel activity switcher text sometimes disappears
https://bugs.kde.org/show_bug.cgi?id=466649 --- Comment #7 from Erik Quaeghebeur --- (In reply to Nate Graham from comment #6) > ...But you say you can't reproduce it now? Is this after upgrading to a new > Plasma version, or is it magically working now with no obvious changes to > the system? No Plasma update in the meantime. However, my laptop finds itself in so many different setups (two different setups with an extra display, connecting to projectors, etc.) that it is hard to reproduce the situations that may trigger bugs like these. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 468482] UnrecognizedResponseKind: HIGHESTMODSEQ
https://bugs.kde.org/show_bug.cgi?id=468482 --- Comment #5 from Erik Quaeghebeur --- I encountered it again and I thought I had copied the full error message, but it is not in my clipboard… Anyway, from the logs: --- 13:25:52.852 Imap::Mailbox::ObtainSynchronizedMailboxTask STATE_WAIT_FOR_CONN INBOX/A/B Activated 13:25:52.852 conn Waiting for another mailbox... 13:25:52.859 Imap::Mailbox::ObtainSynchronizedMailboxTask STATE_SELECTING INBOX/A/B Synchronizing mailbox 13:25:52.864 >>> y738 SELECT "INBOX/A/B" (QRESYNC (1580119498 5801022 (3,5 2142,2217)))␍␊ 13:25:52.968 <<< * OK [CLOSED] Ok␍␊ 13:25:52.968 <<< * 5 EXISTS␍␊ 13:25:52.968 <<< * 0 RECENT␍␊ 13:25:52.968 <<< * FLAGS (\Answered \Flagged \Draft \Deleted \Seen $X-ME-Annot-2 prive $HasAttachment $ATTACHMENT [EDITED OUT])␍␊ 13:25:52.968 <<< * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen $X-ME-Annot-2 prive $HasAttachment $ATTACHMENT [EDITED OUT] \*)] Ok␍␊ 13:25:52.968 <<< * OK [UNSEEN 5] Ok␍␊ 13:25:52.968 <<< * OK [UIDVALIDITY 1580119498] Ok␍␊ 13:25:52.968 <<< * OK [UIDNEXT 2218] Ok␍␊ 13:25:52.968 <<< * OK [HIGHESTMODSEQ 5801022] Ok␍␊ 13:25:52.968 <<< * OK [MAILBOXID (ea021f72-3f97-4cb8-8df5-9f873545481d)] Ok␍␊ 13:25:52.969 <<< * OK [URLMECH INTERNAL] Ok␍␊ 13:25:52.969 <<< * OK [ANNOTATIONS 65536] Ok␍␊ 13:25:52.969 <<< y738 OK [READ-WRITE] Completed␍␊ 13:25:52.969 conn Opening mailbox... 13:25:52.969 Warning: unhandled untagged OK with a response code 13:25:52.969 Warning: unhandled untagged OK with a response code 13:25:52.969 Warning: unhandled untagged OK with a response code 13:25:52.969 Warning: unhandled untagged OK with a response code 13:25:52.969 conn Synchronizing mailbox... 13:25:52.970 Imap::Mailbox::ObtainSynchronizedMailboxTask STATE_SELECTING INBOX/A/B First interesting message at 5 ($X-ME-Annot-2) 13:25:52.970 conn Mailbox opened. 13:25:52.970 Imap::Mailbox::ObtainSynchronizedMailboxTask STATE_SELECTING INBOX/A/B Completed 13:25:52.970 Imap::Mailbox::KeepMailboxOpenTask attached to INBOX/A/B Activated 13:25:58.789 >>> y739 IDLE␍␊ 13:25:58.883 <<< + idling␍␊ 13:25:58.977 <<< * STATUS INBOX/C (UIDVALIDITY 1580127289 UNSEEN 0 HIGHESTMODSEQ 5801104)␍␊ 13:25:58.977 UnrecognizedResponseKind HIGHESTMODSEQ␊* STATUS INBOX/C (UIDVALIDITY 1580127289 UNSEEN 0 HIGHESTMODSEQ 5801104)␍␊␊ ^ here 13:25:58.977 conn Logged out. 13:25:58.977 *** Connection killed. --- Trojita was in folder INBOX/A/B, but the error seems to be about folder INBOX/C. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 468801] New: org.kde.pim.mimetreeparser: unknown mimetype "text/x-moz-deleted"
https://bugs.kde.org/show_bug.cgi?id=468801 Bug ID: 468801 Summary: org.kde.pim.mimetreeparser: unknown mimetype "text/x-moz-deleted" Classification: Applications Product: kmail2 Version: 5.22.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- In my log, I find multiple repetitions of the following warning: --- kmail[6994]: org.kde.pim.mimetreeparser: unknown mimetype "text/x-moz-deleted" --- Given that kmail itself produces attached with such a mimetype when an attachment is deleted, I think it would be a good idea to support this type in some way, so as to at least not trigger a warning. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 468482] UnrecognizedResponseKind: HIGHESTMODSEQ
https://bugs.kde.org/show_bug.cgi?id=468482 --- Comment #7 from Erik Quaeghebeur --- (In reply to Jan Kundrát from comment #6) > […] Do you feel like writing that, Erik? I've created a Todo, but likely this will not be anything that I'm going to look at soon, due to the effort required to find out where in the code the fix should be applied and then how to apply it. (Other things are higher priority or more fun.) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 469694] New: KMail crash when akonadiserver is restarted
https://bugs.kde.org/show_bug.cgi?id=469694 Bug ID: 469694 Summary: KMail crash when akonadiserver is restarted Classification: Applications Product: kmail2 Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- Application: kmail (5.22.3 (22.12.3)) (Compiled from sources) Qt Version: 5.15.9 Frameworks Version: 5.104.0 Operating System: Linux 6.1.27-gentoo-r1-a x86_64 Windowing System: X11 Distribution: "Gentoo Linux" DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: As often happens, an akonadi resource was stuck synchronizing, blocking the whole of akonadi. My solution for this is to restart akonadiserver in akonadiconsole. This crash occurred when I restarted akonadiserver in such a way. The crash can be reproduced sometimes. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #4 std::__atomic_base::operator--() (this=0x630031) at /usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/atomic_base.h:392 #5 QAtomicOps::deref(std::atomic&) (_q_value=) at /usr/include/qt5/QtCore/qatomic_cxx11.h:289 #6 QBasicAtomicInteger::deref() (this=0x630031) at /usr/include/qt5/QtCore/qbasicatomic.h:119 #7 QSharedDataPointer::~QSharedDataPointer() (this=0x5984d1702d50, __in_chrg=) at /usr/include/qt5/QtCore/qshareddata.h:93 #8 Akonadi::Item::~Item() (this=0x5984d1702d50, __in_chrg=) at /var/tmp/portage/kde-apps/akonadi-22.12.3/work/akonadi-22.12.3/src/core/item.cpp:56 #9 0x7e4023707e1c in QHashData::free_helper(void (*)(QHashData::Node*)) (this=0x7e401409d9a0, node_delete=0x7e4021797cc0 ::RefCountedValue >::deleteNode2(QHashData::Node*)>) at /var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/tools/qhash.cpp:572 #10 0x7e402178f38f in QHash::RefCountedValue >::freeData(QHashData*) (x=, this=) at /usr/include/qt5/QtCore/qhash.h:617 #11 QHash::RefCountedValue >::~QHash() (this=, __in_chrg=) at /usr/include/qt5/QtCore/qhash.h:250 #12 QHash::RefCountedValue >::~QHash() (this=, __in_chrg=) at /usr/include/qt5/QtCore/qhash.h:250 #13 QHash::RefCountedValue >::operator=(QHash::RefCountedValue >&&) (other=, this=0x5984d1bac5b8) at /usr/include/qt5/QtCore/qhash.h:255 #14 QHash::RefCountedValue >::clear() (this=0x5984d1bac5b8) at /usr/include/qt5/QtCore/qhash.h:625 #15 RefCountedHash::clear() (this=0x5984d1bac5b0) at /var/tmp/portage/kde-apps/akonadi-22.12.3/work/akonadi-22.12.3/src/core/models/entitytreemodel_p.h:109 #16 Akonadi::EntityTreeModelPrivate::endResetModel() (this=0x5984d1bac5a0) at /var/tmp/portage/kde-apps/akonadi-22.12.3/work/akonadi-22.12.3/src/core/models/entitytreemodel_p.cpp:1722 #17 0x7e40238b7b4c in doActivate(QObject*, int, void**) (sender=0x5984d0418c60, signal_index=3, argv=0x7ffdd7c568c0) at /var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qobject.cpp:3935 #18 0x7e40238b1767 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=, m=m@entry=0x7e402182a500 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at /var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qobject.cpp:3983 #19 0x7e4021711e80 in Akonadi::ServerManager::started() (this=) at /var/tmp/portage/kde-apps/akonadi-22.12.3/work/akonadi-22.12.3_build/src/core/KF5AkonadiCore_autogen/include/moc_servermanager.cpp:167 #20 0x7e4021715659 in Akonadi::ServerManagerPrivate::setState(Akonadi::ServerManager::State) (this=0x7e4021832560 <(anonymous namespace)::Q_QGS_sInstance::innerFunction()::holder>, state=Akonadi::ServerManager::Running) at /var/tmp/portage/kde-apps/akonadi-22.12.3/work/akonadi-22.12.3/src/core/servermanager.cpp:75 #21 0x7e40238af8d4 in QObject::event(QEvent*) (this=0x5984d0418c60, e=0x5984d84960e0) at /var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qobject.cpp:1347 #22 0x7e402436344e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x5984d0418c60, e=0x5984d84960e0) at /var/tmp/portage/dev-qt/qtwidgets-5.15.9/work/qtbase-everywhere-src-5.15.9/src/widgets/kernel/qapplication.cpp:3640 #23 0x7e4023883f58 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x5984d0418c60, event=0x5984d84960e0) at /var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1064 #24 0x7e402388414e in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=, event=) at /var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1462 #25 0x7e4023887493 in QCoreApplicationPrivate::sendPostedEvents(Q
[Akonadi] [Bug 469789] New: Akonadi crashes when akonadiserver is restarted
https://bugs.kde.org/show_bug.cgi?id=469789
Bug ID: 469789
Summary: Akonadi crashes when akonadiserver is restarted
Classification: Frameworks and Libraries
Product: Akonadi
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: server
Assignee: kdepim-b...@kde.org
Reporter: bugs.kde@e3q.eu
CC: c...@carlschwan.eu
Target Milestone: ---
Application: akonadiserver (5.22.3 (22.12.3))
(Compiled from sources)
Qt Version: 5.15.9
Frameworks Version: 5.104.0
Operating System: Linux 6.1.27-gentoo-r1-a x86_64
Windowing System: X11
Distribution: "Gentoo Linux"
DrKonqi: 5.27.4 [KCrashBackend]
-- Information about the crash:
Akonadi resources often get stuck synchronizing. One way of working around that
is to restart akonadiserver. Sometimes akonadi then crashes, as with this
crash.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Segmentation fault
[KCrash Handler]
#4 std::default_delete::operator() (__ptr=0x211,
this=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/unique_ptr.h:89
#5 std::unique_ptr >::~unique_ptr
(this=, __in_chrg=) at
/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/unique_ptr.h:396
#6 std::__new_allocator >
>::destroy > > (__p=,
this=0x7ffd41125ae8) at
/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/new_allocator.h:181
#7
std::allocator_traits > >
>::destroy > > (__p=,
__a=...) at
/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/alloc_traits.h:535
#8 std::vector >,
std::allocator > > >::_M_erase
(__position=std::unique_ptr = {...},
this=0x7ffd41125ae8) at
/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/vector.tcc:181
#9 std::vector >,
std::allocator > > >::erase
(__position=std::unique_ptr = {...},
this=0x7ffd41125ae8) at
/usr/lib/gcc/x86_64-pc-linux-gnu/12/include/g++-v12/bits/stl_vector.h:1530
#10 Akonadi::Server::AkonadiServer::connectionDisconnected
(this=0x7ffd41125a60) at
/var/tmp/portage/kde-apps/akonadi-22.12.3/work/akonadi-22.12.3/src/server/akonadi.cpp:234
#11 0x787ce9aaf8d4 in QObject::event (this=0x7ffd41125a60,
e=0x787c3c02dfe0) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qobject.cpp:1347
#12 0x787ce9a83f25 in doNotify (event=0x787c3c02dfe0,
receiver=0x7ffd41125a60) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1154
#13 QCoreApplication::notify (event=, receiver=,
this=) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1140
#14 QCoreApplication::notifyInternal2 (receiver=0x7ffd41125a60,
event=0x787c3c02dfe0) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1064
#15 0x787ce9a8414e in QCoreApplication::sendEvent (receiver=, event=) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1462
#16 0x787ce9a87493 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x65001f79d9c0) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1821
#17 0x787ce9a87738 in QCoreApplication::sendPostedEvents
(receiver=, event_type=) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qcoreapplication.cpp:1680
#18 0x787ce9ad66f3 in postEventSourceDispatch (s=0x65001f7a0550) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qeventdispatcher_glib.cpp:277
#19 0x787ce858f51c in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#20 0x787ce858f7c8 in ?? () from /usr/lib64/libglib-2.0.so.0
#21 0x787ce858f85c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#22 0x787ce9ad61f6 in QEventDispatcherGlib::processEvents
(this=0x65001f7a02e0, flags=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/src/corelib/kernel/qeventdispatcher_glib.cpp:423
#23 0x787ce9a8297b in QEventLoop::exec (this=this@entry=0x7ffd41125940,
flags=..., flags@entry=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/include/QtCore/../../src/corelib/global/qflags.h:69
#24 0x787ce9a8ac56 in QCoreApplication::exec () at
/var/tmp/portage/dev-qt/qtcore-5.15.9/work/qtbase-everywhere-src-5.15.9/include/QtCore/../../src/corelib/global/qflags.h:121
#25 0x65001dee2d45 in AkApplicationBase::exec
(this=this@entry=0x7ffd41125a30) at
/var/tmp/portage/kde-apps/akonadi-22.12.3/work/akonadi-22.12.3/src/shared/akapplication.cpp:109
#26 0x65001dd6e8a0 in main (argc=, argv=) at
/var/t
[kmail2] [Bug 415576] kmail crashes after restarting because no new mail was being fetched
https://bugs.kde.org/show_bug.cgi?id=415576 Erik Quaeghebeur changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #2 from Erik Quaeghebeur --- KMail crashes are hard to reproduce even if they are not resolved. In any case, I haven't come across something like this crash for a while, so I'll mark it as WORKSFORME. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 414922] crash of akonadictl
https://bugs.kde.org/show_bug.cgi?id=414922 Erik Quaeghebeur changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #2 from Erik Quaeghebeur --- I haven't had this crash for a while, so marking as WORKSFORME. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 414588] KMail crashes when restarting after closing when syncing is stuck at 99%
https://bugs.kde.org/show_bug.cgi?id=414588 Erik Quaeghebeur changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #2 from Erik Quaeghebeur --- I haven't had a crash like this for a while, so I'll mark it WORKSFORME. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 418784] kmail crashes is unresponsive after startup, then crashes when restarting
https://bugs.kde.org/show_bug.cgi?id=418784 Erik Quaeghebeur changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460035] New: Yakuake not shown in desktop grid
https://bugs.kde.org/show_bug.cgi?id=460035 Bug ID: 460035 Summary: Yakuake not shown in desktop grid Classification: Plasma Product: kwin Version: 5.25.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- Since a recent update, yakuake does not show any more in the desktop grid effect. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION I'm using X11 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 413271] Unexpected Konsole crash
https://bugs.kde.org/show_bug.cgi?id=413271 Erik Johansen changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #2 from Erik Johansen --- Cannot reproduce -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 413271] Unexpected Konsole crash
https://bugs.kde.org/show_bug.cgi?id=413271 Erik Johansen changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 460409] New: Regression: Cannot copy-paste from missing debug package file list
https://bugs.kde.org/show_bug.cgi?id=460409 Bug ID: 460409 Summary: Regression: Cannot copy-paste from missing debug package file list Classification: Applications Product: drkonqi Version: 5.25.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bugs.kde@e3q.eu Target Milestone: --- SUMMARY The new qtquick(?) version of DrKonqi has the following regression: it is not possible any more to copy-paste from the dialog that pops up when you click the link concerning missing debug packages. (The text can be dragged left and right, but that is useless.) I see this happening more generally: applications are converted to qtquick and default copy-paste functionality gets lost because of the use of fake dialogs. :-( So one way to fix this class of bugs: please use real dialogs instead of faked ones. Perhaps ‘make sure copy-paste functionality is preserved’ should become one of the checkboxes when converting applications to qtquick. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 209699] azerty+qwerty keyboard layout switch does not switch ctrl-z/ctrl-w ctrl-a/ctrl-q
https://bugs.kde.org/show_bug.cgi?id=209699 Erik Quaeghebeur changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #14 from Erik Quaeghebeur --- (In reply to Justin Zobel from comment #13) > Thank you for reporting this bug in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? It seems to have been fixed! (I had fully switched to QWERTY in the mean time, so didn't follow-up.) -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 434117] Tab autocomplete issue
https://bugs.kde.org/show_bug.cgi?id=434117 Erik Quaeghebeur changed: What|Removed |Added Status|REPORTED|RESOLVED CC||bugs.kde@e3q.eu Resolution|--- |DUPLICATE --- Comment #2 from Erik Quaeghebeur --- *** This bug has been marked as a duplicate of bug 390323 *** -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 390323] Tab completion broken: inserts full completion after initial characters
https://bugs.kde.org/show_bug.cgi?id=390323 Erik Quaeghebeur changed: What|Removed |Added CC||hqu...@outlook.com --- Comment #1 from Erik Quaeghebeur --- *** Bug 434117 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 453854] Please follow BinaryUnitDialect, appropriately
https://bugs.kde.org/show_bug.cgi?id=453854 --- Comment #4 from Erik Quaeghebeur --- (In reply to David Redondo from comment #3) > There is no UI for this setting That is the topic of the linked bug report: https://bugs.kde.org/show_bug.cgi?id=364321 This is a chicken-and-egg problem: as long as applications to not support it, the value of a GUI is limited and developers will not find it urgent, and application developers will point to the lack of a GUI to say that it is not urgent > it is not even global, only KIO reads it I cannot comment on this. I guess that means it is harder to implement? AFAIU previously, it was just a matter of using existing framework functions that do support it. Then perhaps a new bug report is in order to request for better support for this in a framework. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 478631] Printing settings are ignored
https://bugs.kde.org/show_bug.cgi?id=478631 Erik Quaeghebeur changed: What|Removed |Added CC||bugs.kde@e3q.eu Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Erik Quaeghebeur --- *** This bug has been marked as a duplicate of bug 449709 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 449709] Print Color Mode: not possible to print in black-white
https://bugs.kde.org/show_bug.cgi?id=449709 Erik Quaeghebeur changed: What|Removed |Added CC||aman...@kde.org --- Comment #8 from Erik Quaeghebeur --- *** Bug 478631 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 449709] Print Color Mode: not possible to print in black-white
https://bugs.kde.org/show_bug.cgi?id=449709 Erik Quaeghebeur changed: What|Removed |Added CC||bugs.kde@e3q.eu --- Comment #9 from Erik Quaeghebeur --- Created attachment 171292 --> https://bugs.kde.org/attachment.cgi?id=171292&action=edit system-config-printer printer option window on job options page with print-color-mode option highlighted My guess is, that this bug is related to a changed CUPS behavior. See https://github.com/OpenPrinting/cups/issues/421 and https://github.com/OpenPrinting/system-config-printer/issues/312. Namely, a default job option is set (print-color-mode monochrome/color) that does not seem to be overridden when selecting the color mode in the Advanced settings tab. It is not clear to me whether Okular is at fault here, but it possibly is, as system-config-printer does expose this job option. In any case—but this is likely bigger than this bug—it would be good if the print dialog also exposes the color mode for physical printers as it now does for print-to-pdf in the Options tab, next to the Double Sided Printing option. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433732] Google Maps labelled "For development purposes only"
https://bugs.kde.org/show_bug.cgi?id=433732 Erik Krause changed: What|Removed |Added CC|erik.kra...@gmx.de | -- You are receiving this mail because: You are watching all bug changes.
