[akregator] [Bug 458116] Articles spilling from one feed to another
https://bugs.kde.org/show_bug.cgi?id=458116 Jeroen changed: What|Removed |Added CC||jrfo...@xs4all.nl --- Comment #11 from Jeroen --- I'm currently experiencing the same issue on KDE Neon. It happens at seemingly random times, and not just after a crash or anything. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 458912] Akregator fetches old feeds and stores them in wrong news folders
https://bugs.kde.org/show_bug.cgi?id=458912 Jeroen changed: What|Removed |Added Resolution|--- |DUPLICATE CC||jrfo...@xs4all.nl Status|REPORTED|RESOLVED --- Comment #1 from Jeroen --- *** This bug has been marked as a duplicate of bug 458116 *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 458116] Articles spilling from one feed to another
https://bugs.kde.org/show_bug.cgi?id=458116 Jeroen changed: What|Removed |Added CC||andreas.hen...@mailbox.org --- Comment #12 from Jeroen --- *** Bug 458912 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 458757] Archive mixed up between feeds
https://bugs.kde.org/show_bug.cgi?id=458757 Jeroen changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||jrfo...@xs4all.nl --- Comment #1 from Jeroen --- *** This bug has been marked as a duplicate of bug 458116 *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 458116] Articles spilling from one feed to another
https://bugs.kde.org/show_bug.cgi?id=458116 Jeroen changed: What|Removed |Added CC||thomas.rah...@mailbox.org --- Comment #13 from Jeroen --- *** Bug 458757 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481204] New: Notifications stay pinned on screen
https://bugs.kde.org/show_bug.cgi?id=481204 Bug ID: 481204 Summary: Notifications stay pinned on screen Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: alpenblauw...@gmail.com CC: k...@privat.broulik.de Target Milestone: 1.0 Created attachment 165741 --> https://bugs.kde.org/attachment.cgi?id=165741&action=edit Notifications stay pinned on screen Sometimes KDE notifications stay pinned on the screen. Take attached screenshot as an example. The scenario is that I open a password-protected archive and enter the wrong password. The notifications I get stay on the screen forever. I expect them to fade away automatically. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485478] New: Flood of popup notifications telling me that a restart is required
https://bugs.kde.org/show_bug.cgi?id=485478 Bug ID: 485478 Summary: Flood of popup notifications telling me that a restart is required Classification: Applications Product: Discover Version: 5.24.7 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifier Assignee: plasma-b...@kde.org Reporter: alpenblauw...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 168453 --> https://bugs.kde.org/attachment.cgi?id=168453&action=edit KDE annoying restart notifications On Kubuntu 22.04.4 LTS I have set Update software to Automatically in System Settings > Software Update. Periodically I'm being notified of updates. But if there are updates that require a restart, my desktop is flooded with identical popup notifications that I should restart. See the screenshot in the attachment or the popup text below. This flooding goes on for minutes, which is very annoying. One popup notification is more than enough. Besides the popup there is a specific notification pinned in my task bar that reminds me. -- KDE Deamon System Notification Helper A system restart is needed to complete the update process -- -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484624] New: Desktop grid not an option for screen edge
https://bugs.kde.org/show_bug.cgi?id=484624 Bug ID: 484624 Summary: Desktop grid not an option for screen edge Classification: Applications Product: systemsettings Version: 6.0.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kwinscreenedges Assignee: kwin-bugs-n...@kde.org Reporter: jrfo...@xs4all.nl CC: plasma-b...@kde.org Target Milestone: --- Created attachment 167865 --> https://bugs.kde.org/attachment.cgi?id=167865&action=edit Screen Edge selection options SUMMARY Since the update to plasma 6 the Desktop Grid view is no longer an option in the Mouse & Touchpad > Screen Edges menu. STEPS TO REPRODUCE 1. Go to Mouse & Touchpad > Screen Edges menu. 2. Select a screen edge OBSERVED RESULT Grid is not an option, only the generic "Overview" EXPECTED RESULT Grid is an option, like with plasma 5. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 426640] Kdenlive 20.08.1 freezes when opening some projects created by 19.08.1 but not others
https://bugs.kde.org/show_bug.cgi?id=426640 Jeroen changed: What|Removed |Added CC||vds.jer...@gmail.com --- Comment #5 from Jeroen --- I have the same problem in 20.08.1 (installer version). Application freezes at "Loading clips" when opening my project. Tested with nightly build 524 as well (standalone), with the same result. https://binary-factory.kde.org/job/Kdenlive_Nightly_mingw64/524/ I also removed the local cache folder, but that did not help. Windows 10 1809 What output would be helpful to debug this problem? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 426640] Kdenlive 20.08.1 freezes when opening some projects created by 19.08.1 but not others
https://bugs.kde.org/show_bug.cgi?id=426640 --- Comment #7 from Jeroen --- Created attachment 131892 --> https://bugs.kde.org/attachment.cgi?id=131892&action=edit Project created in 20.04.0 which freezes I have added my project file which leads to the freeze as well -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 441411] New: Album list Not Showing
https://bugs.kde.org/show_bug.cgi?id=441411 Bug ID: 441411 Summary: Album list Not Showing Product: digikam Version: 7.3.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Database-Albums Assignee: digikam-bugs-n...@kde.org Reporter: de_witte_jer...@hotmail.com Target Milestone: --- SUMMARY When I go to the duplicate search and try to select only the 2 parent folder and not any of the sub folders. STEPS TO REPRODUCE 1. Add NAS hard drive as a drive in windows 2. Add the drive as an external hard drive in digikam (tried as network drive but lost my database twice already) 3. Wait until all files and folders are added 4. Go to duplicate search and open folders OBSERVED RESULT Only the Main folder is shown EXPECTED RESULT Main folder and all subfolders are shown so I can select a limited amount of files to do the duplicate search SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 441411] Album list Not Showing
https://bugs.kde.org/show_bug.cgi?id=441411 jeroen changed: What|Removed |Added CC||de_witte_jer...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 441411] Album list Not Showing
https://bugs.kde.org/show_bug.cgi?id=441411 --- Comment #3 from jeroen --- It's not that the albums are not visible, they are not there. In the text above it also just says 1 of 2 albums selected, when there are more then 100 albums selected. I did change the drive from a network drive to a external drive while the pictures where imported -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 441411] Album list Not Showing
https://bugs.kde.org/show_bug.cgi?id=441411 --- Comment #5 from jeroen --- The import is completed, all 834 albums are visible in the album layout. If I set the checkbox full collection on true the duplicate search does work and all duplicates are found. It's just that the I wanted to filter out some albums from the duplicate search (timelaps) but when I open the view it only show 2 albums. The 2 main folders -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 441411] Album list Not Showing
https://bugs.kde.org/show_bug.cgi?id=441411 --- Comment #8 from jeroen --- Yes, It was fixed. Ik did a lot of things trying to fix this so not sure if it was thé double click of something else -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 426640] Kdenlive 20.08.1 freezes when opening some projects created by 19.08.1 but not others
https://bugs.kde.org/show_bug.cgi?id=426640 --- Comment #8 from Jeroen --- Seems to be fixed with build #544. ahiijny can you check as well? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425213] New: encrypted root with separate boot automatically decrypted during system startup.
https://bugs.kde.org/show_bug.cgi?id=425213 Bug ID: 425213 Summary: encrypted root with separate boot automatically decrypted during system startup. Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: jrfo...@xs4all.nl CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Created attachment 130779 --> https://bugs.kde.org/attachment.cgi?id=130779&action=edit screenshots during install SUMMARY Calamares unlocks / with a key file, even if /boot is intentionally unencrypted. Not sure if this is a bug in Calamares or the setup that KDE Neon uses. I think the error is in the expectation that /boot is encrypted as well, in which case a key file for / is useful. But when /boot is unencrypted, this is an rather severe error. STEPS TO REPRODUCE Install KDE Neon with the following setup: 1. Select "Manual partitioning" 2. Select "New Partition Table" and choose MBR 3. Create new partition of size 1024 MiB, Primary, File System Ext4, Mount Point /boot. 4. Create new partition of remaining size, Primary, File System btrfs, Encrypt, Mount Point /. 5. Next 6. Read message about GPT 7. Read message about separate boot with encrypted root. 8. Fill out Users form. Do not login automatically. 9. Install. 10. Reboot. OBSERVED RESULT A luks device is created and a single slot is filled at the beginning of the installation, when the disks are prepared. At the end of the installation, there are 2 key slots in use and there is a definition for decryption of / with a key file in /etc/crypttab. After a reboot, / is automatically decrypted. EXPECTED RESULT A luks device is created and a single slot is filled at the beginning of the installation, when the disks are prepared. At the end of the installation, there is still only 1 key slot in use. After a reboot, after grub and loading the kernel and initramfs, there is a prompt for my password. SOFTWARE/OS VERSIONS Linux/KDE Plasma: neon-user-20200810-1423 (available in About System) KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.72.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION I'm not sure how initram is able to get the key file, seeing how the decryption key for root is also on root. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 425213] encrypted root with separate boot automatically decrypted during system startup.
https://bugs.kde.org/show_bug.cgi?id=425213 --- Comment #1 from Jeroen --- It is possible the following is related, in which case I would like a big fat warning that it is not only less secure but completely insecure: https://github.com/calamares/calamares/issues/1311#issuecomment-579741764 Right now it is written in a way to make people aware of the evil maid attack (which is fine by me, because if somebody steals my laptop I woun't be able to type in my password anyway), not the "we put the decryption key in the initram so your encrypted root is useless unless you encrypt your /boot as well". Why would you even put your decryption key in initram by default? Is a workaround for now to remove the entry from /etc/crypttap and remove the key from initram? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 477179] New: Upon entering a wrong password the password field is locked too long
https://bugs.kde.org/show_bug.cgi?id=477179 Bug ID: 477179 Summary: Upon entering a wrong password the password field is locked too long Classification: Plasma Product: kscreenlocker Version: 5.24.7 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: alpenblauw...@gmail.com Target Milestone: --- Upon entering a wrong password the system shows "Login failed" or "Unlocking failed", whereby the password field is locked for about 4 seconds. I don't need 4 seconds to realise what this simple message means, it's quite obvious I made a mistake so I want to retry immediately. Note that the system behaves slightly different when providing a wrong password on initial logon or at unlocking: - A wrong password at initial logon results in a locked password field for 4 seconds, after which the message "Login failed" is shown. - A wrong password at unlocking results directly in a message "Unlocking failed", after which the password field is locked for 4 seconds. The preferred solution to this is to show either the "Login failed" or "Unlocking failed" message directly (which could be faded away after a few seconds if the user takes no action), and NOT to lock the password field so the user can try again immediately. An alternative would be the Windows 10 approach: upon entering the wrong password a message is shown with an OK button; it gives perfect feedback of what went wrong and by hitting Enter you can try again immediately. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 477181] New: Minor annoyances in KDE when switching to another logged in user
https://bugs.kde.org/show_bug.cgi?id=477181 Bug ID: 477181 Summary: Minor annoyances in KDE when switching to another logged in user Classification: Plasma Product: kscreenlocker Version: 5.24.7 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: alpenblauw...@gmail.com Target Milestone: --- There are two minor annoyances in Kubuntu/KDE when switching to another logged in user: Steps: - Kubuntu with at least two accounts configured - Login into a user - Switch to another user - Login into this other user - Switch user Issue: The system shows the other logged in user. The displayed username is: USER (on TTY1 (Display :0)) No ordinary user is interested in "(on TTY1 (Display :0))" or can even interpret what this means. This is technical nerd stuff. So either hide this information or show it below the username using a (far) smaller fontsize. Step: - Press "Switch To This Session". Issue: -Personally I Don't Like This Typical American Way Of Showing Messages, but anyway, after pressing the button the password field is shown a few milliseconds and fades away immediately. Why? I want to switch user, so I want to enter the password without moving my mouse first to wake up the login screen. Like stated before, only minor annoyances but resolving them makes Kubuntu/KDE computing friendlier ;-) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 477179] Upon entering a wrong password the password field is locked too long
https://bugs.kde.org/show_bug.cgi?id=477179 Jeroen changed: What|Removed |Added Resolution|DOWNSTREAM |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #2 from Jeroen --- I get your point, but we're talking about the (latest) Kubuntu LTS release here, 22.04. Anyway, I just reproduced this on KDE Neon with KDE 5.27.9. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 477179] Upon entering a wrong password the password field is locked too long
https://bugs.kde.org/show_bug.cgi?id=477179 Jeroen changed: What|Removed |Added Version|5.24.7 |5.27.9 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 477181] Minor annoyances in KDE when switching to another logged in user
https://bugs.kde.org/show_bug.cgi?id=477181 Jeroen changed: What|Removed |Added Version|5.24.7 |5.27.9 --- Comment #1 from Jeroen --- I encounter this on Kubuntu LTS 22.04 but I just reproduced it on KDE Neon with KDE 5.27.9. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407473] Don't disable password field for a few seconds after entering the wrong password
https://bugs.kde.org/show_bug.cgi?id=407473 --- Comment #6 from Jeroen --- My experience of this bug (from #477179): Upon entering a wrong password the system shows "Login failed" or "Unlocking failed", whereby the password field is locked for about 4 seconds. I don't need 4 seconds to realise what this simple message means, it's quite obvious I made a mistake so I want to retry immediately. Note that the system behaves slightly different when providing a wrong password on initial logon or at unlocking: - A wrong password at initial logon results in a locked password field for 4 seconds, after which the message "Login failed" is shown. - A wrong password at unlocking results directly in a message "Unlocking failed", after which the password field is locked for 4 seconds. The preferred solution to this is to show either the "Login failed" or "Unlocking failed" message directly (which could be faded away after a few seconds if the user takes no action), and NOT to lock the password field so the user can try again immediately. An alternative would be the Windows 10 approach: upon entering the wrong password a message is shown with an OK button; it gives perfect feedback of what went wrong and by hitting Enter you can try again immediately. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407473] Don't disable password field for a few seconds after entering the wrong password
https://bugs.kde.org/show_bug.cgi?id=407473 --- Comment #7 from Jeroen --- So what happened 4 years after the commit for a possible solution? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423107] Systray elements are missing after update - broken config?
https://bugs.kde.org/show_bug.cgi?id=423107 Jeroen changed: What|Removed |Added CC||jrfo...@xs4all.nl --- Comment #17 from Jeroen --- Created attachment 129552 --> https://bugs.kde.org/attachment.cgi?id=129552&action=edit nohub plasmashell --replace Jeroen Rijken -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423107] Systray elements are missing after update - broken config?
https://bugs.kde.org/show_bug.cgi?id=423107 Jeroen changed: What|Removed |Added Resolution|DOWNSTREAM |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #18 from Jeroen --- Hi, My systray is also completely broken, no items are available at all. Also those pop-ups I usually get for media controls (for example when I connect my bluetooth speakers you get a pop-up) are completely gone. I have attempted various manual changes to the plasma-org.kde.plasma.desktop-appletsrc and while I was able to remove some widgets that even after removing were still present by deleting the configurations from this file, it had no effect on my systray at all. After a desparate attempt to fix this by deleting the whole .config and .cache folders, I still have no systay but I cannot change my background anymore either. When I right-click on the desktop and select "Configure Desktop...". It throws an error saying "Layout changes must be applied before ...". The menu is empty and apply now does nothing. Everythis is grayed out. Also my keyboard shortcuts are no longer working. Creating a new user via the system settings only copies over files from /etc/skel to the new user, it does not setup plasma (another bug?). Logging in anyway gives me an empty desktop with a default background and no panel / widgets / icons whatsoever. Creating the systray widget on the desktop gives me and empty box with no systray items. I have no plasmoids installed. I do have latte-dock. Removing it has no effect. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423107] Systray elements are missing after update - broken config?
https://bugs.kde.org/show_bug.cgi?id=423107 --- Comment #19 from Jeroen --- Sorry, first time using Bugzilla. The attachment above is from my "nohup plasmashell --replace". I'm running KDE Neon. Let me know what else you need. Jeroen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423558] New: System tray has no items after update to 5.19.1
https://bugs.kde.org/show_bug.cgi?id=423558 Bug ID: 423558 Summary: System tray has no items after update to 5.19.1 Product: plasmashell Version: 5.19.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: jrfo...@xs4all.nl Target Milestone: 1.0 Created attachment 129707 --> https://bugs.kde.org/attachment.cgi?id=129707&action=edit Contains files for debugging: plasmashell replace nohup, screenshot of system tray, plasmoidviewer systemtray, plasma-org.kde.plasma.desktop-appletsrc SUMMARY My systray is completely broken, no items are available at all. Also those pop-ups I usually get for media controls (for example when I connect my bluetooth speakers you get a pop-up) are completely gone. I have attempted various manual changes to the plasma-org.kde.plasma.desktop-appletsrc and while I was able to remove some widgets that even after removing were still present by deleting the configurations from this file, it had no effect on my systray at all. After a desparate attempt to fix this by deleting the whole .config and .cache folders, I still have no systay but I cannot change my background anymore either. When I right-click on the desktop and select "Configure Desktop...". It throws an error saying "Layout changes must be applied before ...". The menu is empty and apply now does nothing. Everythis is grayed out. Also my keyboard shortcuts are no longer working. Creating a new user via the system settings only copies over files from /etc/skel to the new user, it does not setup plasma (another bug?). Logging in anyway gives me an empty desktop with a default background and no panel / widgets / icons whatsoever. Creating the systray widget on the desktop gives me and empty box with no systray items. Creating a new user seems to be broken as well it seems, but that's a different issue. I didn't install any additional plasmoids, my . I do have latte-dock. Removing it has no effect. Updating to 5.19.2 doesn't solve my issue. I was advised to no longer use bug 423107 but to create a new one. STEPS TO REPRODUCE 1. Update to 5.19.1 2. Reboot 2. All plasma systray items are gone, my own like transgui and keepass are still there 3. Reboot 4. All systray items are gone OBSERVED RESULT No Items in system tray EXPECTED RESULT Items in system tray SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.19 (available in About System) KDE Plasma Version: 5.19.2 KDE Frameworks Version: 5.71.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423558] System tray has no items after update to 5.19.1
https://bugs.kde.org/show_bug.cgi?id=423558 --- Comment #2 from Jeroen --- Hi Konrad, Thanks for the reply. My system is fully updated with no broken packages. I did try a reïnstall of all KDE package with the following commands: find /var/cache/apt/archives/ -name "*5.19.2*" | xargs sudo dpkg -i --force-overwrite --refuse-downgrade find /var/cache/apt/archives/ -name "*5.71.0*" | xargs sudo dpkg -i --force-overwrite --refuse-downgrade find /var/cache/apt/archives/ -name "*5.14.2*" | xargs sudo dpkg -i --force-overwrite --refuse-downgrade This made no difference, unfortunately. Deleting ~/.cache and ~/.config completely make no difference either. Do you have any clue whatsoever where I should be looking for the problem? Jeroen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423558] System tray has no items after update to 5.19.1
https://bugs.kde.org/show_bug.cgi?id=423558 --- Comment #4 from Jeroen --- Created attachment 129791 --> https://bugs.kde.org/attachment.cgi?id=129791&action=edit plasmoidviewer org.kde.plasma.systemtray Here's the output. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423558] System tray has no items after update to 5.19.1
https://bugs.kde.org/show_bug.cgi?id=423558 Jeroen changed: What|Removed |Added Attachment #129791|0 |1 is obsolete|| --- Comment #6 from Jeroen --- Created attachment 129964 --> https://bugs.kde.org/attachment.cgi?id=129964&action=edit nohub QT_LOGGING_RULES (In reply to Konrad Materka from comment #5) > (In reply to Jeroen from comment #4) > > Created attachment 129791 [details] > > plasmoidviewer org.kde.plasma.systemtray > > > > Here's the output. > > Did you run it with: QT_LOGGING_RULES="*=true" > You can firstly run: > export QT_LOGGING_RULES="*=true" > then: > nohup plasmoidviewer --applet org.kde.plasma.systemtray > > Output should be in nohup.out file I did run it with that QT rule, but with the export the output is different. Please see attachment. The file was to big (8,8Mb) so I compressed it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423558] System tray has no items after update to 5.19.1
https://bugs.kde.org/show_bug.cgi?id=423558 Jeroen changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #8 from Jeroen --- (In reply to Konrad Materka from comment #7) > I found suspicious file: > /usr/share/plasma/plasmoids/kpluginindex.json > > Remove or move it somewhere else and check again. > > Did you run Plasma as root? > > Probably this is duplicate of Bug 389297 After moving this file to .bak, my systray is back again. I have never run plasma as root, this happened after the update from 5.19.0 to 5.19.1. Maybe an issue with the .deb packages? I cannot thank you enough for helping me, you really saved me! Thank you! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423558] System tray has no items after update to 5.19.1
https://bugs.kde.org/show_bug.cgi?id=423558 --- Comment #10 from Jeroen --- (In reply to Konrad Materka from comment #9) > Good to know it helped. > > Unfortunately I don't know what caused it - was it broken package or > something else. I have the same distribution and it works correctly. > > If you want you can investigate further: > * This will show if file belongs to any installed deb package (probably not): > dpkg -S /usr/share/plasma/plasmoids/kpluginindex.json > * Was the file created recently or long time ago? > * Is it in compressed format or plain JSON text? Probably a text, which > suggests it is a very old, not it is compressed. > * What are the privileges to the file. Is it root:root 644 (-rw-r--r--)? > > Probably we won't know but it is worth to check, maybe someone else will > stumble on this bug with an idea. After moving the file to .bak fixed the issue, I removed it. I do remember the file command saying it was a bzip2 compressed file and owned by root. But that's all I have for you. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 489933] New: Crash when turning display off
https://bugs.kde.org/show_bug.cgi?id=489933
Bug ID: 489933
Summary: Crash when turning display off
Classification: Applications
Product: plasma-systemmonitor
Version: 6.1.1
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: ksysguard-b...@kde.org
Reporter: jeroen1602+kdeb...@live.nl
CC: ahiems...@heimr.nl, plasma-b...@kde.org
Target Milestone: ---
Application: plasma-systemmonitor (6.1.1)
Qt Version: 6.7.2
Frameworks Version: 6.3.0
Operating System: Linux 6.9.7-200.fc40.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 40 (KDE Plasma)"
DrKonqi: 6.1.1 [CoredumpBackend]
-- Information about the crash:
Sometimes when I turn a display on or off some kde application carshes.
My display is connected via display port so when turning it on or off the
desktop has to resize. I think that that might be part of the problem.
Some command outputs (I hope they are usefull for debugging the problem):
```
$ loginctl show-session 2 -p Type
Type=wayland
```
```
$ nvidia-smi
+-+
| NVIDIA-SMI 555.58.02 Driver Version: 555.58.02 CUDA
Version: 12.5 |
|-++--+
( Leaving the rest out )
```
```
$ lspci | grep VGA
0a:00.0 VGA compatible controller: NVIDIA Corporation TU106 [GeForce RTX 2070]
(rev a1)
```
The crash can be reproduced sometimes.
-- Backtrace:
Application: System Monitor (plasma-systemmonitor), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
Downloading separate debug info for /usr/bin/plasma-systemmonitor...
Downloading separate debug info for
/home/jeroen/.cache/debuginfod_client/a90f9ddf0a573c7fe7f471ef6a404cdd8e52ff8c/debuginfo...
[New LWP 27727]
[New LWP 27735]
[New LWP 27730]
[New LWP 27728]
[New LWP 27729]
[New LWP 27739]
[New LWP 28122]
[New LWP 27750]
[New LWP 28121]
Downloading separate debug info for
/usr/lib64/qt6/qml/QtCore/libqtqmlcoreplugin.so...
Downloading separate debug info for /lib64/libQt6QmlCore.so.6...
Downloading separate debug info for
/usr/lib64/qt6/qml/QtQuick/Dialogs/libqtquickdialogsplugin.so...
Downloading separate debug info for /lib64/libQt6QuickDialogs2.so.6...
Downloading separate debug info for /lib64/libQt6QuickDialogs2QuickImpl.so.6...
Downloading separate debug info for /lib64/libQt6QuickDialogs2Utils.so.6...
Downloading separate debug info for
/usr/lib64/qt6/qml/org/kde/newstuff/libnewstuffqmlplugin.so...
Downloading separate debug info for
/home/jeroen/.cache/debuginfod_client/edb8af3a58aedcb4fdb5d4208566d6cda1c18bb5/debuginfo...
Downloading separate debug info for /lib64/libKF6NewStuffCore.so.6...
Downloading separate debug info for /lib64/libKF6Attica.so.6...
Downloading separate debug info for /lib64/libKF6Syndication.so.6...
Downloading separate debug info for
/usr/lib64/qt6/qml/org/kde/ksysguard/page/libPlasmaSystemMonitorPageplugin.so...
Downloading separate debug info for /lib64/libPlasmaSystemMonitorPage.so...
Downloading separate debug info for /lib64/libKSysGuardSensorFaces.so.2...
Downloading separate debug info for /lib64/libKSysGuardSensors.so.2...
Downloading separate debug info for /lib64/libKSysGuardSystemStats.so.2...
Downloading separate debug info for /lib64/libsensors.so.4...
Downloading separate debug info for
/home/jeroen/.cache/debuginfod_client/490117e99ff6d638ce1a5411eccce1564ef4feeb/debuginfo...
Downloading separate debug info for
/usr/lib64/qt6/qml/org/kde/kitemmodels/libitemmodelsplugin.so...
Downloading separate debug info for
/usr/lib64/qt6/qml/org/kde/iconthemes/libiconthemesplugin.so...
Downloading separate debug info for
/usr/lib64/qt6/qml/org/kde/qqc2desktopstyle/private/libqqc2desktopstyleplugin.so...
Downloading separate debug info for
/usr/lib64/qt6/qml/org/kde/desktop/private/liborg_kde_desktop_private.so...
Downloading separate debug info for
/usr/lib64/qt6/qml/org/kde/sonnet/libsonnetquickplugin.so...
Downloading separate debug info for
/usr/lib64/qt6/qml/org/kde/kirigami/private/libKirigamiPrivatePlugin.so...
Downloading separate debug info for
/usr/lib64/qt6/qml/Qt/labs/platform/libqtlabsplatformplugin.so...
Downloading separate debug info for
/usr/lib64/qt6/qml/QtQuick/Shapes/libqmlshapesplugin.so...
Downloading separate debug info for /lib64/libQt6QuickShapes.so.6...
Downloading separate debug info for
/usr/lib64/qt6/plugins/kf6/kirigami/platform/org.kde.desktop.so...
Downloading separate debug info for
/usr/lib64/qt6/qml/org/kde/ksysguard/faces/libFacesPlugin.so...
Downloading separate debug info for
/usr/lib64/qt6/qml/org/kde/ksysguard/sensors/libSensorsPlugin.so...
Downloading separate debug info for
/usr/lib64/qt6/p
[kpat] [Bug 416503] New: freecel indicator (display) error
https://bugs.kde.org/show_bug.cgi?id=416503 Bug ID: 416503 Summary: freecel indicator (display) error Product: kpat Version: 3.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: solver Assignee: co...@kde.org Reporter: jeroen.zijls...@ziggo.nl CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. play freecel 2. play a multicard planned move 3. OBSERVED RESULT Move indicator on the bottom left: "Het spel is niet meer te winnen" Its a last move indicator that says No More Moves. EXPECTED RESULT When the game says its over, it should be over SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 416503] freecel indicator (display) error
https://bugs.kde.org/show_bug.cgi?id=416503 --- Comment #2 from Jeroen Zijlstra --- A multi-card planned move for me is planning a strategy consisting of 12 to 15 single or duo cards ahead. I like to play the game in my head before doing it. Only half, if you reach te calculated switch-point in the game its only consolidating of the rest. Impossible to loose at Freecel. In short i calculate 15 moves and know it wil work, but the game gives me that message and my moves work anyway. 1 move after the message (only 1 move) after the message. But that message shoudnt be there. (just a small detail). But its a shame to abort the game if i listen to the warning. Op 21-01-2020 om 19:02 schreef Albert Astals Cid: > https://bugs.kde.org/show_bug.cgi?id=416503 > > Albert Astals Cid changed: > > What|Removed |Added > > Status|REPORTED|NEEDSINFO > CC||aa...@kde.org > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Albert Astals Cid --- > Can you please explain what do you mean by a "a multicard planned move" ? > > I think you know better than me how to play this game :) > -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 416503] freecel indicator (display) error
https://bugs.kde.org/show_bug.cgi?id=416503 --- Comment #4 from Jeroen Zijlstra --- Correct Op 21-01-2020 om 21:48 schreef Albert Astals Cid: > https://bugs.kde.org/show_bug.cgi?id=416503 > > --- Comment #3 from Albert Astals Cid --- > Ah, you mean the game is telling you you can't win, but you still were able to > win? > -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 416503] freecel indicator (display) error
https://bugs.kde.org/show_bug.cgi?id=416503 --- Comment #6 from Jeroen Zijlstra --- I will try the new version Yes it happens often. if i play 6 games 1 of those will reproduce. I will try the flathub version. I am used to it now, that little change in de left corner of my eye, i almost don't pay attention to it anymore. But i will check the flatbed version. Op 21-01-2020 om 21:54 schreef Albert Astals Cid: > https://bugs.kde.org/show_bug.cgi?id=416503 > > --- Comment #5 from Albert Astals Cid --- > Does it happen often? > Can you reproduce? > Could you try with the version in flathub? (that i understand is newer than > the > one you're using) > > https://flathub.org/apps/details/org.kde.kpat > -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 397917] New: Cannot autojoin +r channels on freenode.net
https://bugs.kde.org/show_bug.cgi?id=397917 Bug ID: 397917 Summary: Cannot autojoin +r channels on freenode.net Product: konversation Version: 1.7.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: j.bak...@atmind.nl Target Milestone: --- When "Join on connect" is enabled for an +r channels on irc.freenode.net the channel is denied (you need to be identified), before the identification has been completed. The channel at hand in #blendercoders. See here an example log [08:22] [Mode] You have set personal modes: +Ri [08:22] [Notice] -NickServ- This nickname is registered. Please choose a different nickname, or identify via /msg NickServ identify . [08:22] [Channel] Cannot join channel (+r) - you need to be identified with services - see https://freenode.net/kb/answer/registration [08:22] [Notice] -NickServ- You are now identified for . Manual joining afterwards still works. Looks like to start "Join on connect" after identification has been completed should be able to fix the issue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393464] New: Feature Request: Add api for closing view and for setting a view document.
https://bugs.kde.org/show_bug.cgi?id=393464 Bug ID: 393464 Summary: Feature Request: Add api for closing view and for setting a view document. Product: krita Version: 4.0.1 Platform: RedHat RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: jhoolm...@gmail.com Target Milestone: --- There are API options for creating new views for documents. But opening documents into an empty view is not possible at the moment. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393754] New: Feature Request: Add api for changing document background color and opacity.
https://bugs.kde.org/show_bug.cgi?id=393754 Bug ID: 393754 Summary: Feature Request: Add api for changing document background color and opacity. Product: krita Version: 4.0.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: jhoolm...@gmail.com Target Milestone: --- Something in the lines of Document.setBackground(QColor color, float opacity) maybe? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 393771] New: Bug: EXR files coming from Nuke or Maya have wrong channel orders.
https://bugs.kde.org/show_bug.cgi?id=393771 Bug ID: 393771 Summary: Bug: EXR files coming from Nuke or Maya have wrong channel orders. Product: krita Version: 4.0.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: jhoolm...@gmail.com Target Milestone: --- Created attachment 112376 --> https://bugs.kde.org/attachment.cgi?id=112376&action=edit Example EXR Nuke writes out extra layer channels as 'layer.red' instead of 'layer.R'. I have attached an EXR showing the behaviour. The main layer is written as R G B A, but additional layers are red green blue. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394015] New: Closing documents through API leaves empty tabs behind
https://bugs.kde.org/show_bug.cgi?id=394015 Bug ID: 394015 Summary: Closing documents through API leaves empty tabs behind Product: krita Version: 4.0.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Scripting Assignee: krita-bugs-n...@kde.org Reporter: jhoolm...@gmail.com Target Milestone: --- Closing a document through python does not close the tab. Test plan: 1. Create or open a document 2. Run python script: from krita import Krita kt = Krita.instance() document = kt.activeDocument() document.close() -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394015] Closing documents through API leaves empty tabs behind
https://bugs.kde.org/show_bug.cgi?id=394015 --- Comment #1 from Jeroen Hoolmans --- Created attachment 112652 --> https://bugs.kde.org/attachment.cgi?id=112652&action=edit Simply tell the view that's about to close to close it's subwindow. Attaching the patch here since Phabricator is down. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394261] New: API: Loading documents in batchmode still show dialogs.
https://bugs.kde.org/show_bug.cgi?id=394261
Bug ID: 394261
Summary: API: Loading documents in batchmode still show
dialogs.
Product: krita
Version: 4.0.3
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Scripting
Assignee: krita-bugs-n...@kde.org
Reporter: jhoolm...@gmail.com
Target Milestone: ---
Created attachment 112657
--> https://bugs.kde.org/attachment.cgi?id=112657&action=edit
Proposed patch to set documents
Loading certain EXR files still show the alpha modified warning while opening.
It listens to the Documents fileBatchmode, but the api won't let you load a
file through a Document object.
Tested with:
from krita import Krita
kt = Krita.instance()
kt.setBatchmode(True)
doc = kt.openDocument("file_with_low_alphas.exr")
kt.setBatchmode(False)
The supplied patch will set the Documents fileBatchmode to match active Krita
batchmode() before loading, and sets it back to false when done.
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 394261] API: Loading documents in batchmode still show dialogs.
https://bugs.kde.org/show_bug.cgi?id=394261 --- Comment #1 from Jeroen Hoolmans --- Created attachment 112658 --> https://bugs.kde.org/attachment.cgi?id=112658&action=edit Sample low alpha exr (16-bit float) -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 379625] New: KDE cannot authenticate with Google
https://bugs.kde.org/show_bug.cgi?id=379625 Bug ID: 379625 Summary: KDE cannot authenticate with Google Product: libkgapi Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: General Assignee: dvra...@kde.org Reporter: jeroenmathon...@gmail.com Target Milestone: --- As of recently google has changed their authentication procedure. This causes the Google Authentication Window(Where you allow KDE Apps to gain access to the account) to disappear before you can enter your account's details. With already authorized apps and ip's this does not pose a problem because those are already authenticated. -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 379625] KDE cannot authenticate with Google
https://bugs.kde.org/show_bug.cgi?id=379625 Jeroen Mathon changed: What|Removed |Added CC||jeroenmathon...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 378263] solver says "this game cannot be won" while it is still possible to win the game
https://bugs.kde.org/show_bug.cgi?id=378263 --- Comment #3 from jeroen j van beele --- i did write some text - Forwarded message from bugzilla_nore...@kde.org - Date: Sun, 19 Mar 2023 12:55:50 + From: bugzilla_nore...@kde.org To: jer...@guts4roses.org Subject: Re: [kpat] [Bug 378263] solver says "this game cannot be won" while it is still possible to win the game Your message did not contain any text, as far as we could tell. jeroen wrote: > > hello stephan > > > > great to hear from you again > > > > as it has been about 6 years since i filed this bug, i can't find the saved > > games anymore that exhibited the bug > > > > so unfortunately i can?t test the new solver against old cases > > > > also i don't play spider that often anymore > > > > when i do i will for sure check whether i can still win the game while the > > solver says it is impossible and report to you with any remarks > > > > regards > > > > jeroen j van beele, olifantswerf 2, 1018 js amsterdam > > +31 20 7858 909, +31 6 484 72527, jer...@guts2trust.org, guts2trust.org > > > > NOTE: some platforms remove the line breaks i have placed > > restore these line breaks so that you regain the original formatting > > > > > > On Thu, Mar 09, 2023 at 05:24:01AM +, Stephan Kulow wrote: > > > https://bugs.kde.org/show_bug.cgi?id=378263 > > > > > > Stephan Kulow changed: > > > > > >What|Removed |Added > > > > > > Resolution|--- |FIXED > > > Status|REPORTED|RESOLVED > > > > > > --- Comment #2 from Stephan Kulow --- > > > I rewrote the spider solver from scratch, so if you could test later > > > versions, > > > that would be awesome.Without save games I can't tell if it solves your > > > situation. - End forwarded message - -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 378263] New: solver says "this game cannot be won" while it is still possible to win the game
https://bugs.kde.org/show_bug.cgi?id=378263 Bug ID: 378263 Summary: solver says "this game cannot be won" while it is still possible to win the game Product: kpat Version: 3.6 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: solver Assignee: co...@kde.org Reporter: jer...@guts4roses.org CC: kde-games-b...@kde.org Target Milestone: --- the kpatience/spider solver says "this game cannot be won" while it is still possible to win the game. i experienced this quite a few times: i'm playing spider and at some point the solver says that the game can't be won anymore. i just go on playing and i can still win the game. i guess the algorithm to determine the winnability of a specific game has some flaws. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 378263] solver says "this game cannot be won" while it is still possible to win the game
https://bugs.kde.org/show_bug.cgi?id=378263 jeroen j van beele changed: What|Removed |Added CC||jer...@guts4roses.org -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 362582] New: LLVM build instructions not
https://bugs.kde.org/show_bug.cgi?id=362582 Bug ID: 362582 Summary: LLVM build instructions not Product: clazy Version: unspecified Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jeru...@gmail.com CC: smart...@kde.org Following instrucions in the README, BUILD INSTRUCTIONS (Windows): When I try to build with: cmake -DCMAKE_INSTALL_PREFIX=c:\my_install_folder\llvm\ -DLLVM_TARGETS_TO_BUILD="X64" -DCMAKE_BUILD_TYPE=Release -G "NMake Makefiles JOM" .. llvm-build: error: invalid target to enable: 'X64' (not in project) It appears that this target does not exist. Only "X86" exists. I googled for this target and found on this website http://lists.llvm.org/pipermail/cfe-dev/2015-March/042128.html that there is no x64 target at all. -- You are receiving this mail because: You are watching all bug changes.
