[Powerdevil] [Bug 476540] Screens dims but doesn't un-dim after screens were switched off
https://bugs.kde.org/show_bug.cgi?id=476540 --- Comment #13 from Danny --- Looks/sounds like it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480721] Extra widget appeared in taskbar after update to RC2
https://bugs.kde.org/show_bug.cgi?id=480721 Danny changed: What|Removed |Added CC||dbarron...@yahoo.com --- Comment #4 from Danny --- Created attachment 166053 --> https://bugs.kde.org/attachment.cgi?id=166053&action=edit Panel showing dup -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480721] Extra widget appeared in taskbar after update to RC2
https://bugs.kde.org/show_bug.cgi?id=480721 --- Comment #5 from Danny --- Comment on attachment 166053 --> https://bugs.kde.org/attachment.cgi?id=166053 Panel showing dup The 2nd and 3rd position on the panel both are Dolphins and exhibit the same behavior and tooltips. There's some variance as to exactly what of my other icons will show up, but dolphin seems to have a higher change than anything else. My panel is set to autohide, and when first opened it showed two dolphins one in position two and one perhaps position five, then it spontaneously jumped to position 2 and 3 as shown in the screenshot. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 435845] New: Shutdown/Restart & Apply Updates
https://bugs.kde.org/show_bug.cgi?id=435845 Bug ID: 435845 Summary: Shutdown/Restart & Apply Updates Product: Discover Version: 5.21.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Updates (unattended) Assignee: lei...@leinir.dk Reporter: da...@thefallenphoenix.net CC: aleix...@kde.org Target Milestone: --- SUMMARY Both the GNOME (AFAIK) & Windows (for sure) implementations of Offline Updates provide a very useful feature that IMO is essential if we want to reduce user frustration around offline updates. That feature is that as well as the usual Shutdown/Restart menu options there is also "Apply Updates & Shutdown" & "Apply Updates & Restart" options available after preparing an offline update. These do as you might expect; the first reboots into the offline environment, applies the updates and then shuts the system down, the second does the same but reboots instead of shutting the system down. This lets people "walk away" at the end of the day for example with the first option knowing that updates will be applied and their machine turned off. Crucially though they will not suffer additional "boot-up" time when they next use their machines. The second option provides a similar benefit, I see that more as a "I have a second so lets get these updates applied" scenario. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 435845] Option to shut down/restart without applying pending offline updates
https://bugs.kde.org/show_bug.cgi?id=435845 --- Comment #2 from da...@thefallenphoenix.net --- Agreed re: having the option to just Shutdown/Restart remain as options. This is actually how Windows 10 does it. -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 424876] New: Number tracks as 1/12 instead of just number and remove leading 0
https://bugs.kde.org/show_bug.cgi?id=424876 Bug ID: 424876 Summary: Number tracks as 1/12 instead of just number and remove leading 0 Product: kid3 Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: uflei...@users.sourceforge.net Reporter: just_jee...@yahoo.com Target Milestone: --- SUMMARY I have to manually add /12 (or whatever the total tracks are) in the track number field. I assumed that checking the total number of tracks in the number tracks window would add the total tracks after the track number (i.e. 1/1, 2/12, etc). If this is added it would be nice to also have an option to remove the leading 0 so instead of 01/12 it would be 1/12. -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 425200] New: Add [year] to album tag
https://bugs.kde.org/show_bug.cgi?id=425200 Bug ID: 425200 Summary: Add [year] to album tag Product: kid3 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: uflei...@users.sourceforge.net Reporter: just_jee...@yahoo.com Target Milestone: --- SUMMARY I want to add [year] before the album title in the tag 2 section and just wondered if there was a way to automate it. I had just realized that the album year would be helpful when browsing on my car head unit since it only displays artist, title and album. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT [1980] Back in Black 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.
[plasmashell] [Bug 435845] Option to shut down/restart without applying pending offline updates
https://bugs.kde.org/show_bug.cgi?id=435845 --- Comment #11 from da...@thefallenphoenix.net --- (In reply to Kai Uwe Broulik from comment #10) > When an offline update has been scheduled, turn the "Restart" button > into an "Install Updates & Restart" button and let the regular "Restart" > button cancel the pending update. > This is great but doesn't fulfil the aim of "being able to walk away at the end of the day". Specifically that would require an apply updates and Shutdown, not Restart. In fact I'm not sure how apply updates and restart is different to just Restart. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476540] Screens dims but doesn't un-dim after screens were switched off
https://bugs.kde.org/show_bug.cgi?id=476540 Danny changed: What|Removed |Added CC||dbarron...@yahoo.com --- Comment #4 from Danny --- I can confirm this behavior myself. Affected since pre-beta Arch build, continues to be an issue in 5.90.0-2 beta. Also using AMDGPU. -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 425518] New: Can't run English Title Case
https://bugs.kde.org/show_bug.cgi?id=425518 Bug ID: 425518 Summary: Can't run English Title Case Product: kid3 Version: 3.8.x Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: uflei...@users.sourceforge.net Reporter: just_jee...@yahoo.com Target Milestone: --- SUMMARY When I try to run English Title Case I get the following error: qml: could not find a Qt installation of '' STEPS TO REPRODUCE 1. Right click on an mp3 file (within Kid3) 2. Select English Title Case 3. OBSERVED RESULT qml: could not find a Qt installation of '' EXPECTED RESULT Capitalizing the title tag SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux Mint 20 x86_64 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.12.8 in /usr/lib/x86_64-linux-gnu ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 425518] Can't run English Title Case
https://bugs.kde.org/show_bug.cgi?id=425518 --- Comment #2 from Danny --- I've tried the version 3.8.3 from the Linux Mint 20 Software Manager and tried via the repo (ppa:ufleisch/kid3). No, the other QML script context menu functions do not work. Should I try the Flatpak version?On Wednesday, August 19, 2020, 04:46:27 AM EDT, Urs Fleisch wrote: https://bugs.kde.org/show_bug.cgi?id=425518 --- Comment #1 from Urs Fleisch --- Which version are you using exactly, a deb package from https://launchpad.net/~ufleisch/+archive/ubuntu/kid3, a deb package from an official repository or the binary package kid3-3.8.3-Linux.tgz? Are the other QML script context menu functions (Resize Album Art, Extract Album Art, Embed Album Art, Embed Lyrics, QML Console, ReplayGain to SoundCheck, Text Encoding ID3v1, Export CSV, Import CSV, Export Playlist Folder, ID3v1 to ASCII) working? -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 425518] Can't run English Title Case
https://bugs.kde.org/show_bug.cgi?id=425518 --- Comment #4 from Danny --- I ran the install and it was missing the layouts module, after the install I restarted and if still didn't work. I ran the ldd and I don't see any 'not found' libraries. Here's the print out:linux-vdso.so.1 (0x7ffdd0b4f000) libkid3-core.so.3.8.3 => /usr/lib/kid3/libkid3-core.so.3.8.3 (0x7fe4b6dc9000) libQt5Quick.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 (0x7fe4b68d6000) libQt5Qml.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 (0x7fe4b63f7000) libQt5Gui.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 (0x7fe4b5e0c000) libQt5Core.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 (0x7fe4b58c3000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7fe4b56e2000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7fe4b56c5000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fe4b54d3000) libQt5Network.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 (0x7fe4b5312000) libQt5DBus.so.5 => /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 (0x7fe4b5276000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fe4b5127000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fe4b5104000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fe4b50fc000) libGL.so.1 => /usr/lib/x86_64-linux-gnu/libGL.so.1 (0x7fe4b5074000) libpng16.so.16 => /usr/lib/x86_64-linux-gnu/libpng16.so.16 (0x7fe4b503c000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fe4b502) libharfbuzz.so.0 => /usr/lib/x86_64-linux-gnu/libharfbuzz.so.0 (0x7fe4b4f1b000) libicui18n.so.66 => /usr/lib/x86_64-linux-gnu/libicui18n.so.66 (0x7fe4b4c1c000) libicuuc.so.66 => /usr/lib/x86_64-linux-gnu/libicuuc.so.66 (0x7fe4b4a34000) libpcre2-16.so.0 => /usr/lib/x86_64-linux-gnu/libpcre2-16.so.0 (0x7fe4b49b1000) libdouble-conversion.so.3 => /usr/lib/x86_64-linux-gnu/libdouble-conversion.so.3 (0x7fe4b499b000) libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x7fe4b4872000) /lib64/ld-linux-x86-64.so.2 (0x7fe4b6f86000) libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x7fe4b4821000) libGLdispatch.so.0 => /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0 (0x7fe4b4767000) libGLX.so.0 => /usr/lib/x86_64-linux-gnu/libGLX.so.0 (0x7fe4b4733000) libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 (0x7fe4b4674000) libgraphite2.so.3 => /usr/lib/x86_64-linux-gnu/libgraphite2.so.3 (0x7fe4b4647000) libicudata.so.66 => /usr/lib/x86_64-linux-gnu/libicudata.so.66 (0x7fe4b2b86000) libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7fe4b2b11000) libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x7fe4b2a64000) libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x7fe4b2927000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fe4b291c000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fe4b28f3000) liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 (0x7fe4b28d) libgcrypt.so.20 => /usr/lib/x86_64-linux-gnu/libgcrypt.so.20 (0x7fe4b27b2000) libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x7fe4b2788000) libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x7fe4b2765000) libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x7fe4b275f000) libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x7fe4b2755000) libbsd.so.0 => /usr/lib/x86_64-linux-gnu/libbsd.so.0 (0x7fe4b273b000) I don't know how to start kid3 with strace. On Wednesday, August 19, 2020, 01:57:58 PM EDT, Urs Fleisch wrote: https://bugs.kde.org/show_bug.cgi?id=425518 --- Comment #3 from Urs Fleisch --- Using the binary package kid3-3.8.3-Linux.tgz or the flatpak may work, but it will not solve the problem. Linux Mint is based on Ubuntu and on my Ubuntu installation it is working. Maybe there are some dependencies missing. Could you check if you have the following packages installed or try to install them using sudo apt install libqt5quick5 libqt5qml5 qml-module-qtquick-layouts qml-module-qtquick2 If this still does not help, check if "ldd /usr/lib/kid3/plugins/libqmlcommand.so" reports some "not found" libraries. If this still does not help, you could start kid3 with strace and check if it tries to load some files or libraries which are missing. -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 425518] Can't run English Title Case
https://bugs.kde.org/show_bug.cgi?id=425518 --- Comment #5 from Danny --- Ok, since what you mentioned didn't work I tried something. I ran: sudo apt remove kid-qt sudo apt autoremove kid3-qt sudo apt purge kid3-qt Then added the repo and installed. Now I get "Could not execute @qml /usr/share/kid3/qml/script/TitleCase.qml" So I reran sudo apt install libqt5quick5 libqt5qml5 qml-module-qtquick-layouts qml-module-qtquick2 libqt5qml5 is already the newest version (5.12.8-0ubuntu1).libqt5quick5 is already the newest version (5.12.8-0ubuntu1).qml-module-qtquick-layouts is already the newest version (5.12.8-0ubuntu1).qml-module-qtquick2 is already the newest version (5.12.8-0ubuntu1).0 upgraded, 0 newly installed, 0 to remove and 59 not upgraded. ldd /usr/lib/kid3/plugins/libqmlcommand.so linux-vdso.so.1 (0x7ffd8dfaf000) libkid3-core.so.3.8.3 => /usr/lib/kid3/libkid3-core.so.3.8.3 (0x7fd8d0556000) libQt5Quick.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 (0x7fd8d0065000) libQt5Qml.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 (0x7fd8cfb86000) libQt5Gui.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 (0x7fd8cf59b000) libQt5Core.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 (0x7fd8cf052000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7fd8cee71000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7fd8cee54000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fd8cec62000) libQt5Network.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 (0x7fd8ceaa1000) libQt5DBus.so.5 => /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 (0x7fd8cea05000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fd8ce8b6000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fd8ce893000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fd8ce88b000) libGL.so.1 => /usr/lib/x86_64-linux-gnu/libGL.so.1 (0x7fd8ce803000) libpng16.so.16 => /usr/lib/x86_64-linux-gnu/libpng16.so.16 (0x7fd8ce7cb000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fd8ce7af000) libharfbuzz.so.0 => /usr/lib/x86_64-linux-gnu/libharfbuzz.so.0 (0x7fd8ce6aa000) libicui18n.so.66 => /usr/lib/x86_64-linux-gnu/libicui18n.so.66 (0x7fd8ce3ab000) libicuuc.so.66 => /usr/lib/x86_64-linux-gnu/libicuuc.so.66 (0x7fd8ce1c3000) libpcre2-16.so.0 => /usr/lib/x86_64-linux-gnu/libpcre2-16.so.0 (0x7fd8ce14) libdouble-conversion.so.3 => /usr/lib/x86_64-linux-gnu/libdouble-conversion.so.3 (0x7fd8ce12a000) libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x7fd8ce001000) /lib64/ld-linux-x86-64.so.2 (0x7fd8d0713000) libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x7fd8cdfb) libGLdispatch.so.0 => /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0 (0x7fd8cdef6000) libGLX.so.0 => /usr/lib/x86_64-linux-gnu/libGLX.so.0 (0x7fd8cdec2000) libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 (0x7fd8cde03000) libgraphite2.so.3 => /usr/lib/x86_64-linux-gnu/libgraphite2.so.3 (0x7fd8cddd6000) libicudata.so.66 => /usr/lib/x86_64-linux-gnu/libicudata.so.66 (0x7fd8cc315000) libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7fd8cc2a) libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x7fd8cc1f3000) libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x7fd8cc0b6000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fd8cc0ab000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fd8cc082000) liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 (0x7fd8cc05f000) libgcrypt.so.20 => /usr/lib/x86_64-linux-gnu/libgcrypt.so.20 (0x7fd8cbf41000) libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x7fd8cbf17000) libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x7fd8cbef4000) libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x7fd8cbeee000) libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x7fd8cbee4000) libbsd.so.0 => /usr/lib/x86_64-linux-gnu/libbsd.so.0 (0x7fd8cbeca000) Does this help any?On Aug 19, 2020, 1:57 PM -0400, Urs Fleisch , wrote: https://bugs.kde.org/show_bug.cgi?id=425518 --- Comment #3 from Urs Fleisch --- Using the binary package kid3-3.8.3-Linux.tgz or the flatpak may work, but it will not solve the problem. Linux Mint is based on Ubuntu and on my Ubuntu installation it is working. Maybe there are some dependencies missing. Could you check if you have the following packages installed or try to install them using sudo apt install libqt5quick5 libqt5qml5 qml-module-qtquick-layouts qml-module-qtquick2 If this still does not help, check if "ldd /usr/lib/kid3/plugins/libqmlcommand.so" reports some "not found" libraries. If this still does not help, you could start kid3 with strace and check if it tries to load some files or libraries which are missing. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 425518] Can't run English Title Case
https://bugs.kde.org/show_bug.cgi?id=425518 --- Comment #8 from Danny --- Ok, since what you mentioned didn't work I tried something. I ran: sudo apt remove kid-qt sudo apt autoremove kid3-qt sudo apt purge kid3-qt Then added the repo and installed. Now I get "Could not execute @qml /usr/share/kid3/qml/script/TitleCase.qml" -O|||O- Have fun out there. Jeep Jeeps I've owned: 1986 Jeep CJ-7 1995 Jeep YJ Wrangler Rio Grande On Aug 19, 2020, 1:57 PM -0400, Urs Fleisch , wrote: https://bugs.kde.org/show_bug.cgi?id=425518 --- Comment #3 from Urs Fleisch --- Using the binary package kid3-3.8.3-Linux.tgz or the flatpak may work, but it will not solve the problem. Linux Mint is based on Ubuntu and on my Ubuntu installation it is working. Maybe there are some dependencies missing. Could you check if you have the following packages installed or try to install them using sudo apt install libqt5quick5 libqt5qml5 qml-module-qtquick-layouts qml-module-qtquick2 If this still does not help, check if "ldd /usr/lib/kid3/plugins/libqmlcommand.so" reports some "not found" libraries. If this still does not help, you could start kid3 with strace and check if it tries to load some files or libraries which are missing. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 425518] Can't run English Title Case
https://bugs.kde.org/show_bug.cgi?id=425518 --- Comment #10 from Danny --- Fist off, sorry. I was having issues with my email client sending and didn't know it sent twice. I don't know how to check if it's using the default config and I also don't know how to run a debug log. I was thinking that I may just wipe the hard drive and reinstall the OS as I want to put the Home folder on a different partition so that should fix the issue and make future issues easier. I do have Timeshift backing up both home and root but not sure how far back I could go (I may check later today). Thanks for all your help! -O|||O- Have fun out there. Jeep Jeeps I've owned: 1986 Jeep CJ-7 1995 Jeep YJ Wrangler Rio Grande On Aug 22, 2020, 2:46 AM -0400, Urs Fleisch , wrote: > https://bugs.kde.org/show_bug.cgi?id=425518 > > Urs Fleisch changed: > > What |Removed |Added > > Status|REPORTED |NEEDSINFO > Resolution|--- |FIXED > > --- Comment #9 from Urs Fleisch --- > Comment 8 is the same as Comment 5. Could you please answer the following > questions: > > - Does it work with default configuration `KID3_CONFIG_FILE= kid3-qt`? > - Attach the output of `QT_DEBUG_PLUGINS=1 QML_IMPORT_TRACE=1 kid3-qt` (and > make sure to run "English Title Case" while logging the output). > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 425518] Can't run English Title Case
https://bugs.kde.org/show_bug.cgi?id=425518 Danny changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|FIXED |NOT A BUG --- Comment #12 from Danny --- I never figured out exactly what it was but I used Timeshift and went back a week before my first issue and everything is working now. I wonder if uninstalling something created the problem. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 426437] New: Prepackaged compressed cached tiles using webp?
https://bugs.kde.org/show_bug.cgi?id=426437 Bug ID: 426437 Summary: Prepackaged compressed cached tiles using webp? Product: marble Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: riverheart...@gmail.com Target Milestone: --- Hey guys! One of the really great features of Marble is that it can be used offline, but large amounts of map data can be extremely large, and there's not really a good way to do bulk downloads. To make this easier, a feature could be added allowing either png or webp tiles, choosing png if available, along with a second feature defining a simple .zip format for packaging complete complete maps, tiles, metadata, points of interest, and all. A quick test of this shows that a lot of the larger OSM tiles can still be compressed 3x or more, despite not being photographic, with most seeming to be around 2x, with decent enough quality for something largely functional like a map. The files could then be distributed via Torrents much like Kiwix .zim files currently are. This would even enable some educational distros to include low-res maps out of the box! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408624] New: When doing panel widget adds or removes, I have had sporadic but repeated crashes.
https://bugs.kde.org/show_bug.cgi?id=408624 Bug ID: 408624 Summary: When doing panel widget adds or removes, I have had sporadic but repeated crashes. Product: plasmashell Version: 5.16.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-wayland Assignee: plasma-b...@kde.org Reporter: dbarron...@yahoo.com Target Milestone: 1.0 SUMMARY When adding/removing widgets, I've experienced repeated crashes, but application does restart after. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Neon 5.16.0 (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.
[plasmashell] [Bug 408624] When doing panel widget adds or removes, I have had sporadic but repeated crashes.
https://bugs.kde.org/show_bug.cgi?id=408624 Danny changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|BACKTRACE |--- --- Comment #2 from Danny --- (In reply to David Edmundson from comment #1) > Crashes should have a backtrace. > > See the sad face icon in the panel after plasma restart. Unfortunately, the crash reporter failed to be able to add symbols for plasmashell, thus no backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408624] When doing panel widget adds or removes, I have had sporadic but repeated crashes.
https://bugs.kde.org/show_bug.cgi?id=408624 Danny changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 419890] Case Conversion - Proper English Title Capitalization
https://bugs.kde.org/show_bug.cgi?id=419890 --- Comment #5 from Danny --- Thank you. I'll give it a try and let you know if I notice anything weird. -O|||O- Have fun out there. Jeep Jeeps I've owned: 1986 Jeep CJ-7 1995 Jeep YJ Wrangler Rio Grande On Apr 12, 2020, 11:06 AM -0400, Urs Fleisch , wrote: > https://bugs.kde.org/show_bug.cgi?id=419890 > > --- Comment #4 from Urs Fleisch --- > After looking at other solutions for the title case problem, I think that it > is > better to use a script which could be adapted by the user, than being hard > coded in some C++ class. I have attached an example QML script, which can be > added as a user action to Kid3. > > Just store it somewhere and then go to the "User Actions" settings in Kid3 and > add it with name "Title Case" and command "@qml /path/to/TitleCase.qml". You > can then invoke it using the file list context menu or assign it to a keyboard > shortcut in the settings. > > Note that the script is based on titleCaps.js by John Resig and will not touch > most words which are in upper case or have mixed upper and lower case letters > (as opposed to some other solutions), but this brings the advantage of not > having to deal with an endless list of words which have to remain untouched. > Feel free to modify the script (you just have to know a little bit of > JavaScript) and give some feedback. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 402704] Dolphin is slow to send to trash several small files located in a NTFS partition
https://bugs.kde.org/show_bug.cgi?id=402704 Danny changed: What|Removed |Added CC||riverheart...@gmail.com --- Comment #3 from Danny --- Does this have something to do with size limiting the recycle bin? On Reddit we seem to have all noticed a slowdown when recycling via Dolphin, if the size limit is enabled. It's possible the bug only takes effect with a full bin, I don't know on that one. Is there any change KIO could be iterating the entire trash folder to determine current size? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 370356] very slow when delete photos and albums
https://bugs.kde.org/show_bug.cgi?id=370356 Danny changed: What|Removed |Added CC||riverheart...@gmail.com --- Comment #3 from Danny --- On Reddit we are discussing the possibility that slow delete performance may be related to the size limit option. Performance seems to be greatly increased. Is it possible that every delete operation iterates the entire contents of the recycling bin to determine the size, or there's some other slow code path that happens through that option? I also noticed that file move operations are similarly much faster with the option unchecked, so this issue could be bigger than it seems. This may be related to #402704 -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 417364] New: Possible to accidentally drag all points of entire track
https://bugs.kde.org/show_bug.cgi?id=417364 Bug ID: 417364 Summary: Possible to accidentally drag all points of entire track Product: marble Version: 2.5 (KDE Applications 18.04) Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: riverheart...@gmail.com Target Milestone: --- SUMMARY It is possible to drag around an entire track/route/polyline thing created via the edit map window STEPS TO REPRODUCE 1. Create a track 2. Try to drag it by dragging the line itself 3. OBSERVED RESULT You can move the entire track at once, which seems like a highly unlikely thing to want to do(It doesn't seem geographically meaningful), and there is no undo button. EXPECTED RESULT The points should be ediable, but the entire trace should by locked, with ideally a "Offset entire track" menu option to enable the old behavior, for the odd cases in which it is desired. Either that, or an "Undo move" capability. -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 419890] New: Case Conversion - Proper English Title Capitalization
https://bugs.kde.org/show_bug.cgi?id=419890 Bug ID: 419890 Summary: Case Conversion - Proper English Title Capitalization Product: kid3 Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: uflei...@users.sourceforge.net Reporter: just_jee...@yahoo.com Target Milestone: --- Created attachment 127413 --> https://bugs.kde.org/attachment.cgi?id=127413&action=edit Text file with script code I'm a Mac user making the switch to Linux (although longtime Kid3 user) and I used an iTunes script to give song titles proper english capitalization. It would auto capitalize the correct words and not every word or first of a sentence. Not sure it this could be implemented into Kid3 along with the other case conversion options. EXAMPLES: Original ID3 tag title = "Rock And Roll" Would change to = "Rock and Roll" Or "The Song Remains The Same" to "The Song Remains the Same" Currently that can't happen with the options right now. I've attached the older script that I used (in txt format). -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 419890] Case Conversion - Proper English Title Capitalization
https://bugs.kde.org/show_bug.cgi?id=419890 --- Comment #2 from Danny --- THANK YOU! It will get tricky. I'm trying the most recent version of that script and it has an exemption section to add words that are always lower case and a section to add words that are never modified. I added state abbreviations (because I have lots of bootleg concerts) then realized that the states of ME and IN won't work as those are also words so I added IN) and ME) as that's how they tend to be. -O|||O- Have fun out there. Jeep Jeeps I've owned: 1986 Jeep CJ-7 1995 Jeep YJ Wrangler Rio Grande On Apr 10, 2020, 2:21 AM -0400, Urs Fleisch , wrote: > https://bugs.kde.org/show_bug.cgi?id=419890 > > Urs Fleisch changed: > > What |Removed |Added > > Ever confirmed|0 |1 > Status|REPORTED |ASSIGNED > > --- Comment #1 from Urs Fleisch --- > Thanks for the suggestion. I think that this would be a useful addition and I > will implement it. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 449822] New: Vurnability to CVE-2021-44228 in Apache Log4j framework
https://bugs.kde.org/show_bug.cgi?id=449822 Bug ID: 449822 Summary: Vurnability to CVE-2021-44228 in Apache Log4j framework Product: kdenlive Version: 21.04.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Installation Assignee: vpi...@kde.org Reporter: danny.zwa...@kronoberg.se Target Milestone: --- SUMMARY I work for the regional government "Region Kronoberg" (www.kronoberg.se) and in our healthcare organisation we your program KDenlive version 21.04.3 . Recently it became known that there is a vulnerability in the framework for JAVA called Apache Log4j. JAVA. Log4J is a log management framework that can be used in JAVA. We now examining all systems and software used in our organisation to see if these systems / software use Log4j. I would appriciate if the following questions can be answered: - Does your product Kdenlive version 21.04.3 contain the Log4J framework? - Is your product vulnerable to CVE-2021-44228? More information is available at: NVD - CVE-2021-44228 (nist.gov) If the answer on one of these questions is "Yes" answer even the following questions: - how do you intend to deal with the vulnerability? - How should we act as a user? - If there is no resolution availble at this moment WHEN is will a resolution be released and WHAT do you suggest we do in the meantime? Since this is a serious vulnerability I hope to get an answer very soon. With kind regards, Danny Zwaard SOFTWARE/OS VERSIONS Windows: 10 (Version 10.0.18363.2037) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 449822] Vurnability to CVE-2021-44228 in Apache Log4j framework
https://bugs.kde.org/show_bug.cgi?id=449822 Danny Z changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 449822] Vurnability to CVE-2021-44228 in Apache Log4j framework
https://bugs.kde.org/show_bug.cgi?id=449822 --- Comment #2 from Danny Z --- Our IT dept was not fully satisfied with the answer given. According to them there is a risk that Java is used embedded in other programming languages and therefore a possiblilty that Log4j is used somewhere embedded. They would like to get a statement that Kdenlive version 21.04.3 is NOT affected by vurnerabilities in Log4j (CVE-2021-44228). Can you confirm this statement? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 449822] Vurnability to CVE-2021-44228 in Apache Log4j framework
https://bugs.kde.org/show_bug.cgi?id=449822 Danny Z changed: What|Removed |Added Blocks||450294 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=450294 [Bug 450294] Vurnability to CVE-2021-44228 in Apache Log4j framework -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 450294] New: Vurnability to CVE-2021-44228 in Apache Log4j framework
https://bugs.kde.org/show_bug.cgi?id=450294 Bug ID: 450294 Summary: Vurnability to CVE-2021-44228 in Apache Log4j framework Product: kdenlive Version: 21.04.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Installation Assignee: vpi...@kde.org Reporter: danny.zwa...@kronoberg.se CC: vpi...@kde.org Depends on: 449822 Target Milestone: --- +++ This bug was initially created as a clone of Bug #449822 +++ SUMMARY Our IT dept was not fully satisfied with the answer given on Bug#449822 . According to them there is a risk that Java is used embedded in other programming languages and therefore a possiblilty that Log4j is used somewhere embedded in the programming language used for Kdenlive. They would like to get a statement that "Kdenlive version 21.04.3 is NOT affected by vurnerabilities in Log4j (CVE-2021-44228)". Can you confirm this statement? SOFTWARE/OS VERSIONS Windows: 10 (Version 10.0.18363.2037) Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=449822 [Bug 449822] Vurnability to CVE-2021-44228 in Apache Log4j framework -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 450294] Vurnability to CVE-2021-44228 in Apache Log4j framework
https://bugs.kde.org/show_bug.cgi?id=450294 Danny Z changed: What|Removed |Added Status|RESOLVED|VERIFIED -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 450925] New: Jittery cursor after suspend/hibernate
https://bugs.kde.org/show_bug.cgi?id=450925 Bug ID: 450925 Summary: Jittery cursor after suspend/hibernate Product: Powerdevil Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lyrix...@gmx.com Target Milestone: --- I have encountered this bug, apparently it has been here for a while. Not kde speciffic, not sure what it is but I can confirm that when the system goes to suspend and after i turn it back on the cursor movement is extremelly jittery and laggy. I ran a dmesg and a usb bus would say that it disconnected. Then i would look in the touchpad settings and the touchpad device would not be there. Maybe is the way it suspends? I found out that once that happens you have to invoke a " sudo systemctl suspend " then turn it back on and the problem would be solved immediately. Maybe whatever mechanism its being used to suspend can append a workarround for this? The laptop that has this issue is my Thinkpad T480, with my T470 I dont recall having this issue. STEPS TO REPRODUCE 1. wait for the system to suspend 2. turn it back on 3. touchpad /mouse cursor will have the issue (happens very often but i cant say it will be 100% all the time) OBSERVED RESULT If i invoke a " sudo systemctl suspend " and bring the computer back on, the issue is gone. If i dont the issue remains. Operating System: openSUSE Tumbleweed 20220225 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.10-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 488636] New: Allow for window to scale to picture automatically
https://bugs.kde.org/show_bug.cgi?id=488636 Bug ID: 488636 Summary: Allow for window to scale to picture automatically Classification: Applications Product: gwenview Version: 24.05.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: lyrix...@gmx.com Target Milestone: --- Created attachment 170580 --> https://bugs.kde.org/attachment.cgi?id=170580&action=edit On opening (Left) , 'Scaled' (Right) Please add the option to allow gwenview to automatically "scale" its window to picture dimensions. I think it'll look more snappier. Ive attached an example. - Operating System: openSUSE Tumbleweed 20240613 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-1240P Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Framework Product Name: Laptop (12th Gen Intel Core) System Version: A4 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 487773] New: Nightlight not working after suspend/sleep
https://bugs.kde.org/show_bug.cgi?id=487773 Bug ID: 487773 Summary: Nightlight not working after suspend/sleep Classification: Applications Product: systemsettings Version: 6.0.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_nightcolor Assignee: plasma-b...@kde.org Reporter: lyrix...@gmx.com CC: kwin-bugs-n...@kde.org Target Milestone: --- *** After system goes into suspend, the nightlight remains "off" setting it and unsettling it does not make it behave as it should, it always stays off. STEPS TO REPRODUCE 1. go into suspend/sleep mode 2. engage it / or wait for it if configured on a certain time/location OBSERVED RESULT Nightlight remains off; cant activate it, only reboot fixes it. __ Operating System: openSUSE Tumbleweed 20240524 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.9.1-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-1240P Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Framework Product Name: Laptop (12th Gen Intel Core) System Version: A4 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486271] New: [Request] Please add a time based "do not disturb" option
https://bugs.kde.org/show_bug.cgi?id=486271 Bug ID: 486271 Summary: [Request] Please add a time based "do not disturb" option Classification: Applications Product: systemsettings Version: 6.0.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_notify Assignee: plasma-b...@kde.org Reporter: lyrix...@gmx.com CC: k...@privat.broulik.de Target Milestone: --- Created attachment 168982 --> https://bugs.kde.org/attachment.cgi?id=168982&action=edit Add a from: and a to: for a time based duration. SUMMARY Allow to set a schedule for do not disturb mode ei: just like android has. OBSERVED RESULT currently Do no disturb mode activates only via screen sharing ,when screens are mirrored, and manually via shortcut. EXPECTED RESULT The ability to set a time based schedule. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486271] [Request] Please add a time based "do not disturb" option
https://bugs.kde.org/show_bug.cgi?id=486271 Danny Medina changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Danny Medina --- *** This bug has been marked as a duplicate of bug 412471 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412471] Make Do not disturb times configurable with a repeating schedule
https://bugs.kde.org/show_bug.cgi?id=412471 Danny Medina changed: What|Removed |Added CC||lyrix...@gmx.com --- Comment #6 from Danny Medina --- *** Bug 486271 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 407771] CSV import with automatic char for delimnate rows/columns does not work
https://bugs.kde.org/show_bug.cgi?id=407771 Danny Schneider changed: What|Removed |Added CC||Danny_Schneider_Hessen@web. ||de --- Comment #1 from Danny Schneider --- Guess its related, I tried to import CSV Files. Its hard to reproduce but it seems when I import a file the first time and set separators and decimal-char correct, the import works fine. Any second attempt fails. Even when I close and reopen Labplot2. I even tried the same CSV data with different separators. No change. I played around for about an hour with two different Computers - behaviour was same. Over all CSV Import seems pretty broken. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 453678] New: Starup extremelly laggy and slow
https://bugs.kde.org/show_bug.cgi?id=453678 Bug ID: 453678 Summary: Starup extremelly laggy and slow Product: Elisa Version: 22.04.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: baloo Assignee: matthieu_gall...@yahoo.fr Reporter: lyrix...@gmx.com Target Milestone: --- Created attachment 148748 --> https://bugs.kde.org/attachment.cgi?id=148748&action=edit This is how it looks when you try to use it upon launching.. SUMMARY *** Elisa conducts a startup scan [which in my opinion should be in the options to toggle on/off] I have alot of music and i find myself having to wait almost a minute to actually operate the UI otherwise there will be alot of UI latency and sluggishness. I tried setting elisa to use direct scanning to see if the issue remained but it still does it. *** STEPS TO REPRODUCE 1. close and quit Elisa 2. launch elisa 3. behold OBSERVED RESULT Sluggishnes, click delays, top-right notification in elisa says "Scanning music..." for somewhat of a long time until it finishes. EXPECTED RESULT The UI is responsive after it finished scanning for music.. this happens every single time elisa is launched. Naturally there would be some UI sluggishness because its scanning, but it doesnt need to scan every single time i launch it, it hurts the experience. Operating System: openSUSE Tumbleweed 20220509 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 Kernel Version: 5.17.5-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION Nothing else pertaining to this but, as an addition, the music player clementine has the option to allow you to continue playing from the track you left off and is quick and responsive and allows you to conduct on demand scanning to not slow things down. Elisa should be able to do the same indeed, but this scanning issue is preventing that from happening [I think if you have alot of music in your home folder this happens since it scans all music upon startup] -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 453678] Starup extremelly laggy and slow
https://bugs.kde.org/show_bug.cgi?id=453678 --- Comment #1 from Danny Medina --- Created attachment 148749 --> https://bugs.kde.org/attachment.cgi?id=148749&action=edit This is how it looks when you try to use it upon launching. This is how it looks when you try to use it upon launching.. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 453986] New: Elisa tray icon + media player applet
https://bugs.kde.org/show_bug.cgi?id=453986 Bug ID: 453986 Summary: Elisa tray icon + media player applet Product: Elisa Version: 22.04.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: lyrix...@gmx.com Target Milestone: --- Created attachment 148953 --> https://bugs.kde.org/attachment.cgi?id=148953&action=edit elisa tray It would be nice if the tray icon of elisa could be integrated or merged to the media player applet, that way there would only be one icon to manage instead of the elisa's icon alongside it since its a little redundant. Also if the tray icon merge request is denied then I think the option to keep elisa running in the background should be seperate. System info| Operating System: openSUSE Tumbleweed 20220516 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Kernel Version: 5.17.5-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 453986] Elisa tray icon + media player applet
https://bugs.kde.org/show_bug.cgi?id=453986 --- Comment #2 from Danny Medina --- Created attachment 148955 --> https://bugs.kde.org/attachment.cgi?id=148955&action=edit media player applet menu? there are many seperate options that should be all condenced. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 453986] Elisa tray icon + media player applet
https://bugs.kde.org/show_bug.cgi?id=453986 --- Comment #3 from Danny Medina --- Created attachment 148956 --> https://bugs.kde.org/attachment.cgi?id=148956&action=edit Elisa options There are two options into one tick to use the tray icon to keep playing in the background after a close -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 453986] Elisa tray icon + media player applet
https://bugs.kde.org/show_bug.cgi?id=453986 --- Comment #1 from Danny Medina --- Created attachment 148954 --> https://bugs.kde.org/attachment.cgi?id=148954&action=edit media player applet -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login
https://bugs.kde.org/show_bug.cgi?id=427861 Danny Medina changed: What|Removed |Added CC||lyrix...@gmx.com --- Comment #72 from Danny Medina --- I am able to reproduce this BUT, it happens sometimes.. its difficult to pin point exactly when. This is my system info: Operating System: openSUSE Tumbleweed 20220402 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 Kernel Version: 5.16.15-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[knemo] [Bug 456033] New: SHow QR code button for plasma tray thingy for wired networks
https://bugs.kde.org/show_bug.cgi?id=456033 Bug ID: 456033 Summary: SHow QR code button for plasma tray thingy for wired networks Product: knemo Version: 0.7.6 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: jst...@mehercule.net Reporter: djpipe...@gmail.com Target Milestone: --- Created attachment 150188 --> https://bugs.kde.org/attachment.cgi?id=150188&action=edit bug.jpeg.png.org.xlsx SUMMARY Wired networks have a show QR code button in the plasma tray thingy (think this is the right place to post bug) when they shouldn't. *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Connect to wired network 2. Open the network plasma tray thingy 3. Click the "V" icon to look at the side of the wired network 4. Has a show QR code button OBSERVED RESULT Has a show QR code button EXPECTED RESULT No show QR code button SOFTWARE/OS VERSIONS Windows: no macOS: no Linux/KDE Plasma: yes (available in About System) KDE Plasma Version: 5.25.1 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421700] Plasma crashed in QScreen::name()/ShellCorona::addOutput()/ShellCorona::load()/KActivities::Consumer::serviceStatusChanged after I've switched from main laptop to external m
https://bugs.kde.org/show_bug.cgi?id=421700 Danny Medina changed: What|Removed |Added CC||lyrix...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421700] Plasma crashed in QScreen::name()/ShellCorona::addOutput()/ShellCorona::load()/KActivities::Consumer::serviceStatusChanged after I've switched from main laptop to external m
https://bugs.kde.org/show_bug.cgi?id=421700 --- Comment #38 from Danny Medina --- Created attachment 141512 --> https://bugs.kde.org/attachment.cgi?id=141512&action=edit New crash information added by DrKonqi plasmashell (5.22.5) using Qt 5.15.2 Just logged in normally on the wayland session. -- Backtrace (Reduced): #6 0x7f63a9b1e810 in QScreen::name (this=0x558977dad340) at kernel/qscreen.cpp:195 #7 0x5589772bd38a in ShellCorona::addOutput (this=this@entry=0x558977deb030, screen=, screen@entry=0x558977dad340) at /usr/src/debug/plasma5-workspace-5.22.5-1.1.x86_64/shell/shellcorona.cpp:1251 #8 0x5589772be00b in ShellCorona::load (this=) at /usr/src/debug/plasma5-workspace-5.22.5-1.1.x86_64/shell/shellcorona.cpp:701 #9 0x7f63a96d4033 in QtPrivate::QSlotObjectBase::call (a=0x7ffd3535ca60, r=0x558977deb030, this=0x558977fa9fa0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #10 doActivate (sender=0x558977f44450, signal_index=4, argv=0x7ffd3535ca60) at kernel/qobject.cpp:3886 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 442998] New: konqueror opens pages in other application or spawns multiple windows
https://bugs.kde.org/show_bug.cgi?id=442998 Bug ID: 442998 Summary: konqueror opens pages in other application or spawns multiple windows Product: konqueror Version: 21.08.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: danny_schneider_hes...@web.de Target Milestone: --- SUMMARY My Enviroment is XCFE + KDE. When I try to open a webpage, its not opened in konqueror, but in Firefox. Open pages worked fine (last used it some weeks ago), so something must have changed due one of the last package updates, as I have not changed the OS preferences. When I change the OS standard application from firefox to e.g. w3m, konqueror starts w3m in a consoleWhen I change the OS standard application from firefox to konqueror, opening a page in konqueror spawns new windows until I kill the parent thread STEPS TO REPRODUCE 1. Open konqueror 2. open a webpage (via addressbar or menue) OBSERVED RESULT Page is opend in default application e.g. firefox, or spawns new windows in case of konqueror EXPECTED RESULT Just load the page in konqueror, no matter what is the default application (like it was some weeks ago!) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) Kernel Linux 5.14.6-arch1-1 (x86_64) Version #1 SMP PREEMPT Sat, 18 Sep 2021 16:19:35 + C-Library GNU C Library / (GNU libc) 2.33 DistributionArch Linux KDE Plasma Version: KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 451452] New: Auto suspend activities on idle time
https://bugs.kde.org/show_bug.cgi?id=451452 Bug ID: 451452 Summary: Auto suspend activities on idle time Product: kactivitymanagerd Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: lyrix...@gmx.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 147471 --> https://bugs.kde.org/attachment.cgi?id=147471&action=edit activities I use? This is a wishlist report to please allow us to set something like an auto suspend for activities that havent been used for xx ammount of time. If you guys think this is a good idea than yay, if not.. yay! but to me it is since i have been noticing on my use case that i would leave some programs open on one activity and instead of closing down everything i would manually suspend the activity until im in at that said workflow again. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 451452] Auto suspend activities on idle time
https://bugs.kde.org/show_bug.cgi?id=451452 --- Comment #1 from Danny Medina --- it may also help wth powersavings.. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 451454] New: Battery levels (thresholds) reset after a 0% Drain.
https://bugs.kde.org/show_bug.cgi?id=451454 Bug ID: 451454 Summary: Battery levels (thresholds) reset after a 0% Drain. Product: Powerdevil Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lyrix...@gmx.com Target Milestone: --- Please allow for the charging thresholds to remain after the battery drains completely to 0. I noticed that after the battery reachers 0% (for example unattended, in a task, or w.e.) after i put it to charge the battery charging thresholds/limits reset to " always charge" an dthe limit to 100% * I have a T480 and set my thresholds 70%-80% and after the 0% battery; they're gone! STEPS TO REPRODUCE 1. Drain battery to 0% 2. plug in charger + let the PC boot ofcourse 3. go to systemsettings5 > advaced power settings > thresholds are indeed reset. (Battery levels) OBSERVED RESULT Same as stated. EXPECTED RESULT Same as stated. Operating System: openSUSE Tumbleweed 20220310 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.11-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 450925] Jittery cursor after suspend/hibernate
https://bugs.kde.org/show_bug.cgi?id=450925 --- Comment #1 from Danny Medina --- (In reply to Danny Medina from comment #0) > I have encountered this bug, apparently it has been here for a while. Not > kde speciffic, not sure what it is but I can confirm that when the system > goes to suspend and after i turn it back on the cursor movement is > extremelly jittery and laggy. I ran a dmesg and a usb bus would say that it > disconnected. Then i would look in the touchpad settings and the touchpad > device would not be there. > > Maybe is the way it suspends? > I found out that once that happens you have to invoke a " sudo systemctl > suspend " then turn it back on and the problem would be solved immediately. > > Maybe whatever mechanism its being used to suspend can append a workarround > for this? > > The laptop that has this issue is my Thinkpad T480, with my T470 I dont > recall having this issue. > > > STEPS TO REPRODUCE > 1. wait for the system to suspend > 2. turn it back on > 3. touchpad /mouse cursor will have the issue (happens very often but i cant > say it will be 100% all the time) > > OBSERVED RESULT > If i invoke a " sudo systemctl suspend " and bring the computer back on, the > issue is gone. > If i dont the issue remains. > > Operating System: openSUSE Tumbleweed 20220225 > KDE Plasma Version: 5.24.2 > KDE Frameworks Version: 5.91.0 > Qt Version: 5.15.2 > Kernel Version: 5.16.10-1-default (64-bit) > Graphics Platform: Wayland > Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz > Memory: 31.2 GiB of RAM > Graphics Processor: Mesa Intel® UHD Graphics 620 It apperas the issue is the trackpoint?? I had to disable it in the BIOS so my mouse would work.. Havent noticed in on other DEs though.. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442380] Session restore does not remember which windows were on which virtual desktop on X11
https://bugs.kde.org/show_bug.cgi?id=442380 Danny Baumann changed: What|Removed |Added CC||dannybaum...@web.de -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 445122] New: Task window Switcher crash
https://bugs.kde.org/show_bug.cgi?id=445122 Bug ID: 445122 Summary: Task window Switcher crash Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: danailgeorg...@protonmail.com Target Milestone: --- Application: systemsettings5 (5.22.5) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.14.15-200.fc34.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.22.5 Distribution: "Fedora release 34 (Thirty Four)" -- Information about the crash: - What I was doing when the application crashed: I went to System Settings > Window management > Task switcher. When I chose another type of switching, the System Settings app crashed - Custom settings of the application: I changed from Breeze dark to Fedora switcher The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x7f4e65bf06a4 in QWaylandClientExtensionPrivate::handleRegistryGlobal(void*, wl_registry*, unsigned int, QString const&, unsigned int) () from /lib64/libQt5WaylandClient.so.5 #5 0x7f4e65bdd1b9 in QtWaylandClient::QWaylandDisplay::registry_global(unsigned int, QString const&, unsigned int) () from /lib64/libQt5WaylandClient.so.5 #6 0x7f4e65bf9af3 in QtWayland::wl_registry::handle_global(void*, wl_registry*, unsigned int, char const*, unsigned int) () from /lib64/libQt5WaylandClient.so.5 #7 0x7f4e634a8c04 in ffi_call_unix64 () from /lib64/libffi.so.6 #8 0x7f4e634a8107 in ffi_call () from /lib64/libffi.so.6 #9 0x7f4e65b4ad10 in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0 #10 0x7f4e65b4b42b in dispatch_event.isra () from /lib64/libwayland-client.so.0 #11 0x7f4e65b4b61c in wl_display_dispatch_queue_pending () from /lib64/libwayland-client.so.0 #12 0x7f4e65bd56a3 in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib64/libQt5WaylandClient.so.5 #13 0x7f4e681f33f0 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #14 0x7f4e681f5b4a in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib64/libQt5Core.so.5 #15 0x7f4e681f6363 in QSocketNotifier::event(QEvent*) () from /lib64/libQt5Core.so.5 #16 0x7f4e68d92443 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #17 0x7f4e681bf798 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #18 0x7f4e682115ff in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #19 0x7f4e65f474cf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #20 0x7f4e65f9b4f8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #21 0x7f4e65f44c03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #22 0x7f4e68210b78 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #23 0x7f4e681be1a2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #24 0x7f4e681c66e4 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #25 0x55727611a58c in main () [Inferior 1 (process 10185) detached] Possible duplicates by query: bug 445019, bug 444698, bug 444521, bug 444230, bug 443346. Reported using DrKonqi This report was filed against 'kde' because the product 'systemsettings' could not be located in Bugzilla. Add it to drkonqi's mappings file! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 445506] New: Desktop wallpaper overlap with more than one screen connected.
https://bugs.kde.org/show_bug.cgi?id=445506 Bug ID: 445506 Summary: Desktop wallpaper overlap with more than one screen connected. Product: KScreen Version: 5.23.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: lyrix...@gmx.com Target Milestone: --- Created attachment 143558 --> https://bugs.kde.org/attachment.cgi?id=143558&action=edit Overlapped wallpaper that is supposed to go on the screen at the bottom SUMMARY *** Everytime i connect another monitor to my laptop (Lenovo Thinkpad T480) The wallpaper of the extra monitor(s) overlap with the primary desktop, also obstructing the icons. The menus on the non-primary displays also cannot be accessed, I click and nothing happens unless, I right click on the overlapped wallpaper(s). I cant provide any backtraces because i do not know where to look for this specific issue. *** STEPS TO REPRODUCE 1. Connect another display; witness. 2. Try to right click on the non-primary screens; witness no menu appearing. 3. Right click on the overlapped wallpapers; witness the menu(s) for the appropiate screen(s) appear. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211107 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION I have a MOKIN USB-C Dock with many inputs/outputs, I also used to have a Pinebook pro Dock in which i also connected my peripherals includig my screens. And both of them had that issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444218] New: Upon 1-time click the PIM events will not show on the calendar.
https://bugs.kde.org/show_bug.cgi?id=444218 Bug ID: 444218 Summary: Upon 1-time click the PIM events will not show on the calendar. Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: lyrix...@gmx.com Target Milestone: 1.0 Created attachment 142750 --> https://bugs.kde.org/attachment.cgi?id=142750&action=edit After plasma starts "No events" SUMMARY When the digital clock is clicked and the calendar pops up, i can see the blue dots (which should be the same theme accent color ;D) but my events are not shown. It says "No events to display when it should have events to display therefore, I have to select another date for my events to show up; the events should show up everytime. STEPS TO REPRODUCE 1. kill plasmashell 2. start plasmashell & upon starting click on the digital clock & viola! "No events to display" OBSERVED RESULT I can confirm the bug reproduces that way, upon plasmashell startup. EXPECTED RESULT Same SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211016 KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.11-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444218] Upon 1-time click the PIM events will not show on the calendar.
https://bugs.kde.org/show_bug.cgi?id=444218 --- Comment #1 from Danny Medina --- Created attachment 142751 --> https://bugs.kde.org/attachment.cgi?id=142751&action=edit AFter clicking some random date; events now appear Purpose of this screenshot is for the sake of comparison. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 440947] New: Option to delay shutdown prompt/poweroff activation
https://bugs.kde.org/show_bug.cgi?id=440947 Bug ID: 440947 Summary: Option to delay shutdown prompt/poweroff activation Product: Powerdevil Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lyrix...@gmx.com Target Milestone: --- Created attachment 140701 --> https://bugs.kde.org/attachment.cgi?id=140701&action=edit Example Keyboard Layout (not restricted to pinebookpro) Please add the option to delay the activation of the shutdown prompt. For example I have a laptop that has the power button right on top of the delete/backspace key and very frequently when I'm typing i accidentally tap the power button; only to be presented with the shutdown screen and sometimes as i continue to type the laptop shuts down due to this. Operating System: Manjaro-ARM KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.13.7-1-MANJARO-ARM (64-bit) Graphics Platform: Wayland Processors: 6 Memory: 3.8 GiB of RAM Graphics Processor: Mali T860 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 440947] Option to delay shutdown prompt/poweroff activation
https://bugs.kde.org/show_bug.cgi?id=440947 --- Comment #2 from Danny Medina --- (In reply to Méven Car from comment #1) > The option you are asking is a too niche to be implemented IMO. > > I guess what you need is not a delay (there is a delay when the shutdown > fullscreen dialog shows up) but a sound so that you can stop typing when > this happens. > > Or we could interpret keys, not arrows or enter to make a sound or dismiss > the dialog then. > > Or you could change the key association of your unconventionally placed > shutdown button in the shorctuts settings. The idea is to prevent accidental shutdowns, so a delay instead of a tap to bring up the shutdown prompt I believe would be able to squash this.. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 438716] Lid close leads to suspend even when external monitor is attached
https://bugs.kde.org/show_bug.cgi?id=438716 Danny Medina changed: What|Removed |Added CC||lyrix...@gmx.com --- Comment #3 from Danny Medina --- I can confirm that this happens to me. i close the laptop lid while an external monitor i plugged in and i immediately get put on Lockscreen, then the laptop suspends. It only happens on the Wayland session, here are my specs: Operating System: openSUSE Tumbleweed 20210810 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.13.8-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa DRI Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 440947] Option to delay shutdown prompt/poweroff activation
https://bugs.kde.org/show_bug.cgi?id=440947 --- Comment #4 from Danny Medina --- (In reply to Nate Graham from comment #3) > I understand how annoying this must be! > > The thing is, implementing the kind of delay you want needs to be > implemented at a lower level: in hardware, in upower, or in the kernel > drivers. My laptop for example already does implement this at one of those > levels. If we implemented a different delay on top of it, I would have to > press for even longer, and would risk accidentally force-shutting-down the > machine. > > Please report this issue upstream to one of the aforementioned locations. Oh ok, now i get it. Yeah ill have to do that! -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 440067] New: Akondai Crash at start of session
https://bugs.kde.org/show_bug.cgi?id=440067 Bug ID: 440067 Summary: Akondai Crash at start of session Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: lyrix...@gmx.com Target Milestone: --- Application: akonadiserver (5.17.3 (21.04.3)) Qt Version: 5.15.2 Frameworks Version: 5.84.0 Operating System: Linux 5.13.1-1-default x86_64 Windowing System: Wayland Drkonqi Version: 5.22.3 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Resumed my laptop to the KDE wayland session - Unusual behavior I noticed: Attached Screens would not pick up the signal until the laptop lid was opened. After that i logged in and the crash appeared. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f78648da840 (LWP 3649))] [KCrash Handler] #6 0x55f312a5e0c3 in ?? () #7 0x7f786744af5e in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #8 0x7f786741e93f in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #9 0x7f78674219b7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #10 0x7f78674767d3 in ?? () from /lib64/libQt5Core.so.5 #11 0x7f786565980f in g_main_dispatch (context=0x55f313b07a30) at ../glib/gmain.c:3337 #12 g_main_context_dispatch (context=0x55f313b07a30) at ../glib/gmain.c:4055 #13 0x7f7865659b98 in g_main_context_iterate (context=context@entry=0x55f313b07a30, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131 #14 0x7f7865659c4f in g_main_context_iteration (context=0x55f313b07a30, may_block=1) at ../glib/gmain.c:4196 #15 0x7f7867475e54 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #16 0x7f786741d36b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #17 0x7f7867425650 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #18 0x55f312a543d9 in ?? () #19 0x7f7866d68b35 in __libc_start_main (main=0x55f312a53720, argc=1, argv=0x7fff56d8d468, init=, fini=, rtld_fini=, stack_end=0x7fff56d8d458) at ../csu/libc-start.c:332 #20 0x55f312a56fbe in ?? () [Inferior 1 (process 3649) detached] The reporter indicates this bug may be a duplicate of or related to bug 439597. Possible duplicates by query: bug 439991, bug 439928, bug 439916, bug 439901, bug 439800. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 438625] New: Please add a sidebar embedded category for files
https://bugs.kde.org/show_bug.cgi?id=438625 Bug ID: 438625 Summary: Please add a sidebar embedded category for files Product: Elisa Version: unspecified Platform: OpenBSD Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: lyrix...@gmx.com Target Milestone: --- Created attachment 139311 --> https://bugs.kde.org/attachment.cgi?id=139311&action=edit Visual representation Im submitting this fetaure request because it would be an easier option to search for the folders in which you have your music in through the sidebar instead f the middle section of elisa; sort of how clementine has it. I've come to this conclusion over and over because not all my music has its metadata like it should and alot of songs from the same folder are under different albums and genres thereby making it harder to navegate from a specific project -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 438625] Please add a sidebar embedded category for files
https://bugs.kde.org/show_bug.cgi?id=438625 Danny Medina changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 438625] Please add a sidebar embedded category for files
https://bugs.kde.org/show_bug.cgi?id=438625 Danny Medina changed: What|Removed |Added Platform|OpenBSD Packages|unspecified -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 438625] Please add a sidebar embedded category for files/Directories
https://bugs.kde.org/show_bug.cgi?id=438625 Danny Medina changed: What|Removed |Added Summary|Please add a sidebar|Please add a sidebar |embedded category for files |embedded category for ||files/Directories -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 438873] New: Please add an opaque setting in the Dashboard plugin configuration
https://bugs.kde.org/show_bug.cgi?id=438873 Bug ID: 438873 Summary: Please add an opaque setting in the Dashboard plugin configuration Product: kdeplasma-addons Version: 5.22.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Application Dashboard Assignee: h...@kde.org Reporter: lyrix...@gmx.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 139495 --> https://bugs.kde.org/attachment.cgi?id=139495&action=edit with transparency & blur turned off Please add an option to make the Dashboard plugin opaque. For users with low end devices turning off blur and or transparency makes the desktop experience faster, but in doing so it will also leave the dash to dock applet in a transparent/dimmed state instead of it being opaque/black. * Also, upon taking a screenshot of it the dashboard turns opaque as I believe it should remain. STEPS TO REPRODUCE 1. turn off transparency & blur in effects section 2. activate the dashboard menu plugin 3. observe SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenSUSE Tumbleweed 20210615 (available in About System) KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Lenovo Thinkpad T470 Intel Core i5-7300u Intel HD 620 (i915|KBL GT2) -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 438873] Please add an opaque setting in the Dashboard plugin configuration
https://bugs.kde.org/show_bug.cgi?id=438873 --- Comment #1 from Danny Medina --- Created attachment 139496 --> https://bugs.kde.org/attachment.cgi?id=139496&action=edit This is how its supposed to be. It appears like that if you screenshoot it. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 438876] New: KDE Connect Crashes upon startup/system startup
https://bugs.kde.org/show_bug.cgi?id=438876 Bug ID: 438876 Summary: KDE Connect Crashes upon startup/system startup Product: kdeconnect Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: lyrix...@gmx.com Target Milestone: --- Application: kdeconnectd (21.04.2) Qt Version: 5.15.2 Frameworks Version: 5.83.0 Operating System: Linux 5.12.10-1-default x86_64 Windowing System: Wayland Drkonqi Version: 5.22.0 Distribution: "openSUSE Tumbleweed" -- Information about the crash: I just rebooted my system and i see that it segfaults. Everytime i log into the system it does it. It happened out of nowhere weather X11 or wayland it doesnt matter, It still happens. The crash can be reproduced every time. -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fd8c4288d00 (LWP 2508))] [KCrash Handler] #6 QCA::Certificate::Certificate (this=, opts=..., key=..., provider=..., this=, opts=..., key=..., provider=...) at /usr/src/debug/qca-qt5-2.3.3-2.1.x86_64/src/qca_cert.cpp:1466 #7 0x7fd8c812d681 in KdeConnectConfig::generateCertificate (this=this@entry=0x7fd8c814bdf0 , certPath=...) at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/kdeconnectconfig.cpp:347 #8 0x7fd8c812dbfc in KdeConnectConfig::loadCertificate (this=this@entry=0x7fd8c814bdf0 ) at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/kdeconnectconfig.cpp:287 #9 0x7fd8c812e01c in KdeConnectConfig::KdeConnectConfig (this=, this=) at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/kdeconnectconfig.cpp:92 #10 0x7fd8c812e1d5 in KdeConnectConfig::instance () at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/kdeconnectconfig.cpp:65 #11 KdeConnectConfig::instance () at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/kdeconnectconfig.cpp:65 #12 0x7fd8c81312b2 in Daemon::init (this=0x7ffe30419520) at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/daemon.cpp:89 #13 0x7fd8c6bb009e in QObject::event (this=0x7ffe30419520, e=0x55b6500e3ba0) at kernel/qobject.cpp:1314 #14 0x7fd8c77d3a5f in QApplicationPrivate::notify_helper (this=, receiver=0x7ffe30419520, e=0x55b6500e3ba0) at kernel/qapplication.cpp:3632 #15 0x7fd8c6b83aaa in QCoreApplication::notifyInternal2 (receiver=0x7ffe30419520, event=0x55b6500e3ba0) at kernel/qcoreapplication.cpp:1063 #16 0x7fd8c6b86af7 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55b6500808a0) at kernel/qcoreapplication.cpp:1817 #17 0x7fd8c6bdba73 in postEventSourceDispatch (s=s@entry=0x55b6500b5a30) at kernel/qeventdispatcher_glib.cpp:277 #18 0x7fd8c505e80f in g_main_dispatch (context=0x55b6500d4f40) at ../glib/gmain.c:3337 #19 g_main_context_dispatch (context=0x55b6500d4f40) at ../glib/gmain.c:4055 #20 0x7fd8c505eb98 in g_main_context_iterate (context=context@entry=0x55b6500d4f40, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131 #21 0x7fd8c505ec4f in g_main_context_iteration (context=0x55b6500d4f40, may_block=1) at ../glib/gmain.c:4196 #22 0x7fd8c6bdb0f4 in QEventDispatcherGlib::processEvents (this=0x55b6500b99d0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #23 0x7fd8c6b824bb in QEventLoop::exec (this=this@entry=0x7ffe30419410, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #24 0x7fd8c6b8a790 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #25 0x7fd8c6fe11fc in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867 #26 0x7fd8c77d39d5 in QApplication::exec () at kernel/qapplication.cpp:2824 #27 0x55b64ec9fa47 in main (argc=, argv=0x7ffe304194c0) at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/daemon/kdeconnectd.cpp:174 [Inferior 1 (process 2508) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[knotes] [Bug 324840] sync notes with owncloud notes app
https://bugs.kde.org/show_bug.cgi?id=324840 Danny Medina changed: What|Removed |Added CC||lyrix...@gmx.com --- Comment #6 from Danny Medina --- I would love to see this as well, as a matter of fact it would be a swell idea to sync all the nextcloud services/apps to the corresponding kde apps. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 439445] New: Request to toggle Bluetooth on/off via custom shortcut
https://bugs.kde.org/show_bug.cgi?id=439445 Bug ID: 439445 Summary: Request to toggle Bluetooth on/off via custom shortcut Product: Bluedevil Version: 5.22.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: system tray Assignee: now...@gmail.com Reporter: lyrix...@gmx.com CC: plasma-b...@kde.org Target Milestone: --- I'm requesting for the Bluetooth applet or system tray icon to have a map-able shortcut to toggle Bluetooth on and off. i know most laptops have some sort of function key for this but I'm on a Desktop with a Bluetooth adapter. I thought id be convenient to map a shortcut to toggle it on and off. Scenario: You want to do some gaming and you have your Bluetooth gamepad. You then right click on the Bluetooth applet and switch it on when you can just press something like ctl+alt+b or whatever custom shortcut to toggle it on/off on the fly. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405436] Some installed apps from discover do not have desktop entry
https://bugs.kde.org/show_bug.cgi?id=405436 Danny Roberts changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 473586] New: [Wishlist] Allow workspaces only on certain screens.
https://bugs.kde.org/show_bug.cgi?id=473586 Bug ID: 473586 Summary: [Wishlist] Allow workspaces only on certain screens. Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: lyrix...@gmx.com Target Milestone: --- SUMMARY *** For users that have screens/ monitors for tasks that don't change ei: TV watching /streaming , Gaming, static tasks, but use workspaces on the other screens. *** * It would be nice to have the ability to turn off workspaces say, for screen number X or more. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 402203] Yakuake cut off, tab bar not viewable
https://bugs.kde.org/show_bug.cgi?id=402203 --- Comment #3 from Danny Zen --- This is good to close On Wed, Jan 18, 2023 at 7:19 PM Justin Zobel wrote: > https://bugs.kde.org/show_bug.cgi?id=402203 > > Justin Zobel changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > > --- Comment #2 from Justin Zobel --- > Thank you for reporting this issue 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? > > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you! > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 423650] New: Summary line of credit card reconciliation incorrectly worded
https://bugs.kde.org/show_bug.cgi?id=423650 Bug ID: 423650 Summary: Summary line of credit card reconciliation incorrectly worded Product: kmymoney Version: 5.0.8 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: d.o.sc...@unb.ca Target Milestone: --- SUMMARY Summary Line at end of credit card ledger when reconciling says: 1 charge ($284.21) 40 payments (961.03) Should say: 1 payment ($284.21) 40 charges (961.03) to correspond with real life as well as the column headings. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.71.0 KDE Frameworks Version: Qt Version: 5.15.0 ADDITIONAL INFORMATION openSUSE Tumbleweed -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 426047] Crash in KQuickAddons::ConfigModule::~ConfigModule() for multiple System Settings KCMs
https://bugs.kde.org/show_bug.cgi?id=426047 Danny Medina changed: What|Removed |Added CC||lyrix...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 426047] Crash in KQuickAddons::ConfigModule::~ConfigModule() for multiple System Settings KCMs
https://bugs.kde.org/show_bug.cgi?id=426047 --- Comment #17 from Danny Medina --- Created attachment 133692 --> https://bugs.kde.org/attachment.cgi?id=133692&action=edit New crash information added by DrKonqi systemsettings5 (5.20.2) using Qt 5.15.2 - What I was doing when the application crashed: Changing the wallpaper category of the "Wallpaper of the day" plugin, afterwards i locked the screen to see the changes, then closed the lock screen appareance settings and while the application exited, it also crashed upon exit. - Custom settings of the application: Had the "Wallpaper of the day" plugin enabled. -- Backtrace (Reduced): #4 0x7fa5321f48aa in QQmlData::wasDeleted (object=0x558dbe34af00) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/qml/qqmldata_p.h:338 #5 QV4::QObjectWrapper::getQmlProperty (engine=engine@entry=0x558dbe319f80, qmlContext=qmlContext@entry=0x558dbe322fb0, object=0x558dbe34af00, name=0x7fa4bd3185e8, revisionMode=revisionMode@entry=QV4::QObjectWrapper::CheckRevision, hasProperty=hasProperty@entry=0x7fffd81593c8, property=0x7fffd81593d0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:360 #6 0x7fa5321d42ca in QV4::QQmlContextWrapper::getPropertyAndBase (resource=, id=..., receiver=, hasProperty=0x7fffd8159447, base=0x0, lookup=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/common/qv4staticvalue_p.h:325 #7 0x7fa5321d4b93 in QV4::QQmlContextWrapper::resolveQmlContextPropertyLookupGetter (l=0x558dbe3947c0, engine=0x558dbe319f80, base=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/common/qv4staticvalue_p.h:325 #8 0x7fa532211410 in QV4::Moth::VME::interpret (frame=0x7fffd8159630, engine=0x558dbe319f80, code=0x7fa4bccf8a0b "\030\n(N\030\r\247a\001") at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/src/qml/jsruntime/qv4vme_moth.cpp:585 -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 329787] KsysGuard crash
https://bugs.kde.org/show_bug.cgi?id=329787 Danny Medina changed: What|Removed |Added CC||lyrix...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 91753] WISH: use knewstuff to maintain a central list of feeds, providing an easy way to get popular feeds
https://bugs.kde.org/show_bug.cgi?id=91753 --- Comment #5 from Danny Allen --- You can close this issue, thanks. On Tue, 9 Mar 2021, at 4:12 AM, Justin Zobel wrote: > https://bugs.kde.org/show_bug.cgi?id=91753 > > --- Comment #4 from Justin Zobel --- > Thank you for the bug report. > > As this report hasn't seen any changes in 5 years or more, we ask if you can > please confirm that the issue still persists. > > If this bug is no longer persisting or relevant please change the status to > resolved. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405436] Some installed apps from discover do not have desktop entry
https://bugs.kde.org/show_bug.cgi?id=405436 Danny Roberts changed: What|Removed |Added Resolution|DOWNSTREAM |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #4 from Danny Roberts --- Marking re-opened in the hope my previous comment gets noticed. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405436] Some installed apps from discover do not have desktop entry
https://bugs.kde.org/show_bug.cgi?id=405436 --- Comment #6 from Danny Roberts --- I don't have any expectations as to how the actual implementation. The original answer was given was that they had no entries in Kicker because they had no .desktop files (or at least heavily implied this). That simply isn't true. So I re-opened it to point this out. If KDE has some unique way that a snap must be put together to read it's .desktop file(s) that hasn't been made clear at all. Or are you expecting the snap to place the .desktop file somewhere outside of the snap contents for KDE to pick it up? Again it isn't clear. Both of these seem odd, because if I compare against a Gnome desktop whether I add a Snap via the Gnome Software Centre or via the snap CLI tool that app will show up in Gnome's software menu as expected. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 407006] New: Snaps not added to Application Launcher
https://bugs.kde.org/show_bug.cgi?id=407006 Bug ID: 407006 Summary: Snaps not added to Application Launcher Product: Discover Version: 5.15.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Snap Backend Assignee: lei...@leinir.dk Reporter: da...@thefallenphoenix.net CC: aleix...@kde.org Target Milestone: --- SUMMARY After installing snaps on KDE Neon (either via the CLI or via Discover) the app is not added to the launcher, so the only way to run it is via the CLI/KRunner. STEPS TO REPRODUCE 1. Open discover. 2. Search for app available as a snap (e.g. Spotify). 3. Install app. OBSERVED RESULT No entry is added to the app menu. EXPECTED RESULT Entry is added to the app menu. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.15 (4.15.0-48-generic) amd64 (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 405436] Some installed apps from discover do not have desktop entry
https://bugs.kde.org/show_bug.cgi?id=405436 --- Comment #3 from Danny Roberts --- This is not resolved in my opinion. All the Snap apps on my system DO contain at least 1 .desktop file: ➜ kemra102@iacon ~ find /snap/spotify/35/ -name '*.desktop' /snap/spotify/35/meta/gui/spotify.desktop /snap/spotify/35/usr/share/spotify/spotify.desktop ➜ kemra102@iacon ~ find /snap/electronplayer/6/ -name '*.desktop' /snap/electronplayer/6/meta/gui/electronplayer.desktop ➜ kemra102@iacon ~ find /snap/slack/13 -name '*.desktop' /snap/slack/13/meta/gui/slack.desktop /snap/slack/13/usr/share/applications/slack.desktop ➜ kemra102@iacon ~ find /snap/telegram-desktop/715 -name '*.desktop' /snap/telegram-desktop/715/meta/gui/telegramdesktop.desktop /snap/telegram-desktop/715/snap/gui/telegramdesktop.desktop Is this still not correct some how? -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 411634] kio-gdrive crash when saving file from text editor
https://bugs.kde.org/show_bug.cgi?id=411634 Danny Smit changed: What|Removed |Added CC||danny.smi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 398237] Discover app re-fetches updates when opened from the Plasmoid that the Plasmoid already seems to know about
https://bugs.kde.org/show_bug.cgi?id=398237 --- Comment #7 from Danny Roberts --- I've been thinking about this recently and if a purely technical solution isn't apparent (and it doesn't seem to be), perhaps a workflow solution would do the trick. So instead of: 1. Single left click on Update icon that drops down to show number of updates and an update button. 2. Discover opens with a message of "Checking for updates...". we might have something like this: 1. Single left click on Update icon which immediately loads Discover (on hover says "Updates Available" or similar). 2. Discover opens with a message of "Getting full list of updates..." I feel this would be better as it doesn't set any expectations that X amount of downloads are available & gives the impression that the Updater/Discover has only just appeared so it being in the process of getting all the updates seems normal. Though in some ways imprecise I believe this is how things are still done on Windows & people aren't unhappy about it there. -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 391186] Access token expires/invalidates after performing a few file operations
https://bugs.kde.org/show_bug.cgi?id=391186 Danny Rafferty changed: What|Removed |Added CC||danny.raffe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415865] New: Crashes when opens Window Decorations
https://bugs.kde.org/show_bug.cgi?id=415865 Bug ID: 415865 Summary: Crashes when opens Window Decorations Product: systemsettings Version: 5.17.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: edward...@gmail.com Target Milestone: --- Application: systemsettings5 (5.17.4) Qt Version: 5.13.2 Frameworks Version: 5.65.0 Operating System: Linux 5.0.0-37-generic x86_64 Distribution: Feren OS -- Information about the crash: - What I was doing when the application crashed: When selcting the Window decorations the System settings crashes everytime, please look into this and resolve - Custom settings of the application: Using the unity theme, not sure if this has anything to do with this bug or if its an issue with system settings The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6a514bde40 (LWP 8577))] Thread 7 (Thread 0x7f6a11014700 (LWP 8613)): #0 0x7f6a45ee4664 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f6a45e9e47d in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a45e9e6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a4d13cb9b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6a4d0dd06a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a4cef83aa in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6a4a878815 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f6a4cef9b52 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6a4c2b96db in start_thread (arg=0x7f6a11014700) at pthread_create.c:463 #9 0x7f6a4c7f688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f6a19910700 (LWP 8612)): #0 0x7f6a4c7e9bf9 in __GI___poll (fds=0x7f6a14081a20, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f6a45e9e5c9 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a45e9e6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a4d13cb9b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6a4d0dd06a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a4cef83aa in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6a4a878815 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f6a4cef9b52 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6a4c2b96db in start_thread (arg=0x7f6a19910700) at pthread_create.c:463 #9 0x7f6a4c7f688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f6a222c7700 (LWP 8591)): #0 0x7f6a45e9e4ee in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f6a45e9e6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a4d13cb9b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f6a4d0dd06a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f6a4cef83aa in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6a4a878815 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f6a4cef9b52 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6a4c2b96db in start_thread (arg=0x7f6a222c7700) at pthread_create.c:463 #8 0x7f6a4c7f688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f6a2b324700 (LWP 8589)): #0 0x7f6a4c7e50b4 in __GI___libc_read (fd=12, buf=0x7f6a2b323b70, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f6a45ee32d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f6a45e9e0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f6a45e9e570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f6a45e9e6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f6a4d13cb9b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f6a4d0dd06a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f6a4cef83aa in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6a4a878815 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f6a4cef9b52
[plasmashell] [Bug 421787] New: Plasma crashed after trying to move files from desktop to folder
https://bugs.kde.org/show_bug.cgi?id=421787 Bug ID: 421787 Summary: Plasma crashed after trying to move files from desktop to folder Product: plasmashell Version: 5.18.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: damc0...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.5) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.3.0-51-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: I've opened a folder from desktop, later on I tried to move three .mp3 files (that were also located on desktop) into the opened folder but Plasma crashed. The background turned black (dolphin and other apps were still open) and after a few seconds, Plasma started again; so I tried to move the same files again but Plasma crashed in the same way; this time showing the Crash Reporting Assistant. Files were not moved. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcba48001c0 (LWP 1595))] Thread 25 (Thread 0x7fcb0f1e3700 (LWP 6008)): #0 0x7fcb9aeb09f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fcb8007a970) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7fcb8007a920, cond=0x7fcb8007a948) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7fcb8007a948, mutex=0x7fcb8007a920) at pthread_cond_wait.c:655 #3 0x7fcb9e2741db in QWaitConditionPrivate::wait (deadline=..., this=0x7fcb8007a920) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x7fcb880205b0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fcb9e274359 in QWaitCondition::wait (this=this@entry=0x7fcb880205b8, mutex=mutex@entry=0x7fcb880205b0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7fcba23ac233 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x7fcb880205a8) at scenegraph/qsgthreadedrenderloop.cpp:255 #7 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x7fcb88020510) at scenegraph/qsgthreadedrenderloop.cpp:905 #8 0x7fcba23ac691 in QSGRenderThread::run (this=0x7fcb88020510) at scenegraph/qsgthreadedrenderloop.cpp:1000 #9 0x7fcb9e26dc2c in QThreadPrivate::start (arg=0x7fcb88020510) at thread/qthread_unix.cpp:342 #10 0x7fcb9aeaa6db in start_thread (arg=0x7fcb0f1e3700) at pthread_create.c:463 #11 0x7fcb9db5488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7fcb0f9e4700 (LWP 6007)): #0 0x7fcb9aeb09f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55ef217cc9d8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55ef217cc988, cond=0x55ef217cc9b0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55ef217cc9b0, mutex=0x55ef217cc988) at pthread_cond_wait.c:655 #3 0x7fcb79e3aa0b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7fcb79e3a607 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7fcb9aeaa6db in start_thread (arg=0x7fcb0f9e4700) at pthread_create.c:463 #6 0x7fcb9db5488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 23 (Thread 0x7fcb167f7700 (LWP 5278)): #0 0x7fcb9aeb09f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55ef21006d04) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55ef21006cb0, cond=0x55ef21006cd8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55ef21006cd8, mutex=0x55ef21006cb0) at pthread_cond_wait.c:655 #3 0x7fcb9e2741db in QWaitConditionPrivate::wait (deadline=..., this=0x55ef21006cb0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x7fcb88011a40, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7fcb9e274359 in QWaitCondition::wait (this=this@entry=0x7fcb88011a48, mutex=mutex@entry=0x7fcb88011a40, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7fcba23ac233 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x7fcb88011a38) at scenegraph/qsgthreadedrenderloop.cpp:255 #7 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x7fcb880119a0) at scenegraph/qsgthreadedrenderloop.cpp:905 #8 0x7fcba23ac691 in QSGRenderThread::run (this=0x7fcb880119a0) at scenegraph/qsgthreadedrenderloop.cpp:1000 #9 0x7fcb9e26dc2c in QThreadPrivate::start (arg=0x7fcb880119a0) at thread/qthread_unix.c
[plasmashell] [Bug 421847] New: Lock screen clock does not respect the system's font antialiasing setting
https://bugs.kde.org/show_bug.cgi?id=421847 Bug ID: 421847 Summary: Lock screen clock does not respect the system's font antialiasing setting Product: plasmashell Version: 5.18.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: svc@kdrag0n.dev CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY The lock screen clock fails to respect the system's font antialiasing settings and always uses RGB subpixel antialiasing, even when everything is configured to use grayscale antialiasing. STEPS TO REPRODUCE 1. Switch to grayscale font antialiasing in System Settings -> Fonts 2. Re-login to make sure the font rendering change takes effect 3. Lock the screen 4. Look closely at the clock or date OBSERVED RESULT The clock and date at the top of the lock screen are rendered using RGB subpixel antialiasing. This can be verified by carefully looking at the edges of the text in a screenshot if the difference is not clear. EXPECTED RESULT The clock and date are rendered using grayscale antialiasing. SOFTWARE VERSIONS KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391335] New: After reconcile of account only non-reconciled records shown
https://bugs.kde.org/show_bug.cgi?id=391335 Bug ID: 391335 Summary: After reconcile of account only non-reconciled records shown Product: kmymoney Version: 5.0.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: d.o.sc...@unb.ca Target Milestone: --- The option to not show reconciled transactions is not checked. Prior to reconciling all records are shown. After reconciling the reconciled transactions are not shown. Selecting a different account and then returning shows all records. Using openSUSE Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kmediaplayer] [Bug 391545] New: XF86AudioPlay no longer resumes play on spotify
https://bugs.kde.org/show_bug.cgi?id=391545 Bug ID: 391545 Summary: XF86AudioPlay no longer resumes play on spotify Product: frameworks-kmediaplayer Version: 5.12.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: alex.me...@kde.org Reporter: d...@schedmd.com CC: kdelibs-b...@kde.org Target Milestone: --- After upgrading to KDE 5.12.3 I find my play key on my keyboard no longer resumes play on spotify any more. It does pause still, just doesn't resume play. I have tested on amarok and both pause and play work as expected. It appear the problem is only with spotify from my testing. This used to work fine before the upgrade. Sorry if this is the wrong product. It wasn't clear what the Media Player widget controlling the play/pause button was under. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391545] XF86AudioPlay no longer resumes play on spotify
https://bugs.kde.org/show_bug.cgi?id=391545 --- Comment #2 from Danny Auble --- Friedrich, thanks for the help! qdbus | grep org.mpris.MediaPlayer2 org.mpris.MediaPlayer2.spotify qdbus org.mpris.MediaPlayer2.spotify /org/mpris/MediaPlayer2 org.freedesktop.DBus.Properties.Get org.mpris.MediaPlayer2.Player CanPlay true qdbus org.mpris.MediaPlayer2.spotify /org/mpris/MediaPlayer2 org.freedesktop.DBus.Properties.Get org.mpris.MediaPlayer2.Player CanPause true At this point it seems to be correct Note even stranger, I have set up another hotkey to expressly call dbus-send --print-reply --dest=org.mpris.MediaPlayer2.spotify /org/mpris/MediaPlayer2 org.mpris.MediaPlayer2.Player.PlayPause and that works just fine for both play and pause. I have tried uninstalling and reinstalling spotify as well and that didn't change the behavior. This just started with the update. I also tried on a different machine and functionality seems to be correct there, so this must be some sort of configuration issue. I have tried with a completely new user on the bad system with the same bad results so the issue seems to be system wide. I suppose I could reinstall everything from fresh, but I would rather avoid doing that. At the moment I can still use the extra hotkey to do the play/pausing, but love the MediaPlayer interface when switching players (as I use Amarok very often as well). Thanks again for your help! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391545] XF86AudioPlay no longer resumes play on spotify
https://bugs.kde.org/show_bug.cgi?id=391545 --- Comment #3 from Danny Auble --- For further reference qdbus org.mpris.MediaPlayer2.spotify /org/mpris/MediaPlayer2 org.freedesktop.DBus.Properties.GetAll org.mpris.MediaPlayer2.Player CanControl: true CanGoNext: true CanGoPrevious: true CanPause: true CanPlay: true CanSeek: true LoopStatus: Playlist MaximumRate: 1 Metadata: mpris:artUrl: http://open.spotify.com/thumb/0fd555d08a265b1c364044a4118cf6e1ea700f67 mpris:length: 32300 mpris:trackid: spotify:track:6Oy2qpuumdnPo44ZpmxSY7 xesam:album: Liberty xesam:artist: Duran Duran xesam:autoRating: 0.16 xesam:contentCreated: 1990-01-01T00:00:00 xesam:discNumber: 1 xesam:title: Downtown xesam:trackNumber: 11 xesam:url: spotify:track:6Oy2qpuumdnPo44ZpmxSY7 MinimumRate: 1 PlaybackStatus: Paused Position: 0 Rate: 1 Shuffle: false Volume: 0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391545] XF86AudioPlay no longer resumes play on spotify
https://bugs.kde.org/show_bug.cgi?id=391545
--- Comment #4 from Danny Auble ---
If I attach dbus-monitor to it I get
dbus-monitor "sender='org.mpris.MediaPlayer2.spotify'"
When I hit play/pause
method return time=1520955006.105602 sender=:1.40 -> destination=:1.19
serial=1108 reply_serial=1360
variant boolean true
method return time=1520955006.105816 sender=:1.40 -> destination=:1.19
serial=1109 reply_serial=1361
variant string "Playing"
method return time=1520955006.106052 sender=:1.40 -> destination=:1.19
serial=1110 reply_serial=1362
variant boolean true
signal time=1520955006.109423 sender=:1.40 -> destination=(null destination)
serial= path=/StatusNotifierItem; interface=org.kde.StatusNotifierItem;
member=NewStatus
string "Passive"
signal time=1520955006.109442 sender=:1.40 -> destination=(null destination)
serial=1112 path=/StatusNotifierItem; interface=org.kde.StatusNotifierItem;
member=NewStatus
string "Active"
signal time=1520955006.109452 sender=:1.40 -> destination=(null destination)
serial=1113 path=/StatusNotifierItem; interface=org.kde.StatusNotifierItem;
member=NewToolTip
method return time=1520955006.89 sender=:1.40 -> destination=:1.19
serial=1114 reply_serial=1363
signal time=1520955006.111576 sender=:1.40 -> destination=(null destination)
serial=1115 path=/org/mpris/MediaPlayer2;
interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
string "org.mpris.MediaPlayer2.Player"
array [
dict entry(
string "PlaybackStatus"
variant string "Paused"
)
]
array [
]
signal time=1520955006.111671 sender=:1.40 -> destination=(null destination)
serial=1116 path=/StatusNotifierItem/menu; interface=com.canonical.dbusmenu;
member=LayoutUpdated
uint32 14
int32 0
method return time=1520955006.111899 sender=:1.40 -> destination=:1.19
serial=1117 reply_serial=1364
variant int64 0
method return time=1520955006.114116 sender=:1.40 -> destination=:1.19
serial=1118 reply_serial=1365
uint32 14
struct {
int32 0
array [
dict entry(
string "children-display"
variantstring "submenu"
)
]
array [
variant struct {
int32 1
array [
dict entry(
string "enabled"
variant boolean false
)
dict entry(
string "label"
variant string "Duran Duran â
Ordinary World"
)
]
array [
]
}
variant struct {
int32 2
array [
dict entry(
string "type"
variant string "separator"
)
]
array [
]
}
variant struct {
int32 3
array [
dict entry(
string "label"
variant string "Open Spotify"
)
]
array [
]
}
variant struct {
int32 4
array [
dict entry(
string "type"
variant string "separator"
)
]
array [
]
}
variant struct {
int32 5
array [
dict entry(
string "label"
variant string "Play"
)
]
array [
]
}
variant struct {
int32 6
array [
dict entry(
string "type"
variant string "separator"
)
]
array [
]
}
variant struct {
int32 7
array [
dict entry(
string "label"
variant string "Next"
)
]
array [
]
}
variant struct {
int32 8
array [
dict ent
[plasmashell] [Bug 391545] XF86AudioPlay no longer resumes play on spotify
https://bugs.kde.org/show_bug.cgi?id=391545 --- Comment #6 from Danny Auble --- I am glad it makes sense at least :). How would I check this method and property? Thanks again for you help! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391545] XF86AudioPlay no longer resumes play on spotify
https://bugs.kde.org/show_bug.cgi?id=391545 --- Comment #8 from Danny Auble --- Thanks for the tutorial :). That appears to be the issue. qdbus org.mpris.MediaPlayer2.spotify /org/mpris/MediaPlayer2 org.mpris.MediaPlayer2.Player.Play results in nothing. qdbus org.mpris.MediaPlayer2.spotify /org/mpris/MediaPlayer2 org.mpris.MediaPlayer2.Player.Pause works just fine. Any idea how to fix it (or go back to the old method)? Seems strange it works on other systems. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391545] XF86AudioPlay no longer resumes play on spotify
https://bugs.kde.org/show_bug.cgi?id=391545 --- Comment #9 from Danny Auble --- qdbus org.mpris.MediaPlayer2.spotify /org/mpris/MediaPlayer2 org.mpris.MediaPlayer2.Player.PlayPause Also works just fine as well (expected). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391545] XF86AudioPlay no longer resumes play on spotify
https://bugs.kde.org/show_bug.cgi?id=391545 --- Comment #11 from Danny Auble --- I agree, thanks for your help on this. I have already verified they have this fixed in a newer release of spotify. The spotify version with the problem is 0.9.17.8. 1.0.69 is working as expected. I also verified the 'good' system I though it worked with was actually still running KDE 5.10.5 so it also makes sense why it was working. Thanks for your help and great information on how to debug. -- You are receiving this mail because: You are watching all bug changes.
