[valgrind] [Bug 476465] AArch64 ARMv8.3 LDAPR/LDAPRH/LDAPRB instructions not supported
https://bugs.kde.org/show_bug.cgi?id=476465 William Ashley changed: What|Removed |Added CC||w...@amazon.com --- Comment #11 from William Ashley --- I was able to verify that the proposed patch does result in a successful valgrind run of Arne's production case on Graviton. That's only verifying that it applies, compiles, doesn't hit the unrecognized instruction error in valgrind, and the program behaves as it does outside of valgrind. I haven't however, dove into the IR and surrounding logic to ensure that it is semantically correct. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 492529] okular is very slow opening some PDFs
https://bugs.kde.org/show_bug.cgi?id=492529 William Bader changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #8 from William Bader --- (In reply to Justin Zobel from comment #7) > I'd suggest testing with the Flatpak Okular as it won't have any changed > settings and seeing if there is a difference in load times. Thanks!!! Testing with the flatpak version was a good idea. The flatpak version was almost instant for me. I compared the settings under Settings -> Configure Okular -> Performance The flatpak had "enable graphics antialias" checked. My local okular had it unchecked. (I had done that a long time ago because I thought that antialiasing made it slower.) I checked it, and it went from a minute to almost instant rending the sample PDF. I had thought that antialias rendered at a higher resolution and then averaged the high resolution image down to the displayed resolution, so enabling antialias is usually a few times slower. I didn't expect that enabling antialias in okular would be about 50 times faster instead of a few times slower. If antialias is off, does okular revert to a slower method (like using poppler splash)? I tried unsetting antialias for both text and graphics to see if having them set differently was the problem, but having them both unchecked was still slow. Anyway, thanks, enabling graphics antialias solved the problem! Thanks again! William -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 492529] okular is very slow opening some PDFs
https://bugs.kde.org/show_bug.cgi?id=492529 --- Comment #6 from William Bader --- (In reply to Justin Zobel from comment #3) > I've just opened this PDF in Okular on two different devices, and it loads > within 1–2 seconds. Are you able to boot a live ISO of another OS and test > the file there? It might be some tuning thing on Fedora that is causing the > issue. Thank you for the reply. Is it possible that I set something wrong in okular? I have the default settings, except since my laptop has a cpu with 20 threads and has 64 GB RAM, in Okular -> Configure -> Performance, I set Memory Usage to "Greedy". I also currently have CPU usage: [ ] Enable transparency effects (not set) Rendering options: [x] Enable text antialias (set) [ ] Enable graphic antialias (not set) [ ] Enable text hinting (not set) I use okular to read long documents. I want the text clear, but I don't care if the images aren't as clear as possible. My Linux installation runs X with Mate Desktop (Wayland isn't an option with Mate), and I think that I have X configured to use the built-in Intel GPU primarily while making the nvidia GPU available to applications. My laptop has a 4K (3840x2160) display, and I use mate-tweaks to configure for hidpi. I think that my hardware and OS configuration are ok because evince and atril open the test page in a few seconds, maybe about 30X faster than okular, but I am open to suggestions. Regards, William -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 492529] okular is very slow opening some PDFs
https://bugs.kde.org/show_bug.cgi?id=492529 --- Comment #5 from William Bader --- (In reply to Timothée Ravier from comment #4) > I've opened this PDF in fresh Fedora 40 and Fedora 41 VMs and it loaded in > 1-2 seconds. It also loads quickly on my Kinoite 40 installation with > Flathub's Okular so I recommend giving this a try to narrow down the > potential root cause: https://flathub.org/apps/org.kde.okular Thank you for the reply. I'm willing to try that. Fedora provides flatpak. It looks like it would install about a GB. After testing, can I used `flatpack uninstall ...` to remove everything that `flatpak install flathub org.kde.okular` loaded? My laptop has no CD drive, but it has USB 3 and 64 GB RAM, so I can boot ISOs copied to usb sticks (which is how I tested Fedora 40 before updating to it), but I would rather test with flatpak or a VM first. ```$ flatpak install flathub org.kde.okular Looking for matches… Required runtime for org.kde.okular/x86_64/stable (runtime/org.kde.Platform/x86_64/6.7) found in remote flathub Do you want to install it? [Y/n]: y org.kde.okular permissions: ipc network cups fallback-x11 pulseaudio wayland x11 dri file access [1] dbus access [2] [1] host, xdg-config/kdeglobals:ro [2] com.canonical.AppMenu.Registrar, org.kde.KGlobalSettings, org.kde.kconfig.notify IDBranch Op Remote Download 1. org.freedesktop.Platform.GL.default 23.08 i flathub < 170.7 MB 2. org.freedesktop.Platform.GL.default 23.08-extra i flathub < 170.7 MB 3. org.freedesktop.Platform.GL.nvidia-560-35-03 1.4 i flathub < 323.4 MB 4. org.freedesktop.Platform.VAAPI.Intel 23.08 i flathub < 13.4 MB 5. org.freedesktop.Platform.openh264 2.2.0 i flathub < 944.3 kB 6. org.kde.KStyle.Adwaita6.7 i flathub < 8.1 MB 7. org.kde.Platform.Locale 6.7 i flathub < 393.3 MB (partial) 8. org.kde.Platform 6.7 i flathub < 333.9 MB 9. org.kde.okular.Locale stable i flathub < 2.8 MB (partial) 10. org.kde.okularstable i flathub < 35.5 MB Proceed with these changes to the system installation? [Y/n]: n ``` -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 492529] okular is very slow opening some PDFs
https://bugs.kde.org/show_bug.cgi?id=492529 --- Comment #2 from William Bader --- Hopefully viewing the PDF with a profiling build of okular will identify the problem. I think that okular, atril, and evince all use libpoppler as the back-end for PDFs, and usually okular is faster, I think because atril and evince do an extra layer of copying internally. My laptop is using xorg-x11-server-Xorg-1.20.14 and xorg-x11-drv-nvidia-560.35.03 with an NVIDIA GeForce RTX 3050 Laptop GPU. Fedora 40 has poppler-24.02.0 Maybe the PDF has a large image with a color format that doesn't match any of the formats provided by X. pdftops -level1sep takes 54 seconds, while pdftops -level2 takes under 1 second, so maybe okular is interfacing with poppler in a way that poppler think that it needs to use splash. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 492529] okular is very slow opening some PDFs
https://bugs.kde.org/show_bug.cgi?id=492529 William Bader changed: What|Removed |Added CC||williamba...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 492529] okular is very slow opening some PDFs
https://bugs.kde.org/show_bug.cgi?id=492529 --- Comment #1 from William Bader --- The PDF is 26 MB. I made a temporary link on dropbox. https://www.dropbox.com/scl/fi/y48kao7495tucy4w2reig/gf202405-pg25-okular-slow-2sep24.pdf?rlkey=oen6hjglippfyfkx0k4o5prc3&st=q2rszx5h&dl=0 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 492529] New: okular is very slow opening some PDFs
https://bugs.kde.org/show_bug.cgi?id=492529 Bug ID: 492529 Summary: okular is very slow opening some PDFs Classification: Applications Product: okular Version: 24.08.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: williamba...@hotmail.com Target Milestone: --- SUMMARY I have a single page PDF that takes okular over a minute to open, while gv/gs opens it almost instantly and atril and evince open it in a few seconds. STEPS TO REPRODUCE 1. view the file with okular OBSERVED RESULT It takes over a minute to paint completely (Fedora 40 Linux on an i7-12800H laptop) EXPECTED RESULT It should take a few seconds like atril and evince, since I think that all three use the same libpoppler. SOFTWARE/OS VERSIONS Linux: Fedora 40 Desktop: mate 1.28 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 492050] Valgrind does not understand some eBPF commands passed into the bpf syscalls
https://bugs.kde.org/show_bug.cgi?id=492050 --- Comment #2 from William Cohen --- This bug is not a duplicate of 478774. The bug 478774 is tracking the size of objects initialized by the kernel. This bug is filed due to some of the eBPF commands not being handled by valgrind. Just to be sure the reproducer was run with a version of valgrind that included the patch from 478774. The warnings about unhandled eBPF commands were still present on the patched version of valgrind. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 478066] Image preview not showing
https://bugs.kde.org/show_bug.cgi?id=478066 William Wojciechowski changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|NOT A BUG |--- CC||w@yandex.com --- Comment #12 from William Wojciechowski --- (In reply to Justin Zobel from comment #5) > I can't reproduce this. Thumbnails show up for me. Are all the effected > users on Arch? Debian Sid user here, with a working Plasma 6 from Experimental. I don't have thumbnails, too. I just saw that, for each "thumbnailable" icon shown by Dolphin, journald writes: dolphin kf.kio.core: couldn't create worker: Unknown protocol 'thumbnail' I have ffmpegthumbnailer and kdegraphics-thumbnailers packages installed. "Show previews" is also checked. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 492050] New: Valgrind does not understand some eBPF commands passed into the bpf syscalls
https://bugs.kde.org/show_bug.cgi?id=492050 Bug ID: 492050 Summary: Valgrind does not understand some eBPF commands passed into the bpf syscalls Classification: Developer tools Product: valgrind Version: 3.23.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: wco...@redhat.com Target Milestone: --- SUMMARY When attempting to track down the root cause of a valgrind complaint about unitialized fields in some PCP code I noticed that valgrind would print out messages in the following in the output: --1794549-- WARNING: unhandled eBPF command 28 --1794549-- WARNING: unhandled eBPF command 35 The command 28 and 35 map to BPF_LINK_CREATE and BPF_PROG_BIND_MAP, respectively. The handling of things the bpf syscall handles is incomplete. STEPS TO REPRODUCE on Fedora 40 as root: 1. dnf install pcp-pmda-bpf valgrind 2. touch /var/lib/pcp/pmdas/bpf/.NeedInstall 3. systemctl restart pmcd 4. valgrind pminfo -L -K clear -K add,157,/var/lib/pcp/pmdas/bpf/pmda_bpf,bpf_init -dmtT bpf.disk bpf.runq OBSERVED RESULT The output has a number of messages about "unhandled eBPF command ..." EXPECTED RESULT No messages about unhandled eBPF commands in the output SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 pcp-pmda-bpf-6.2.2-3.fc39.x86_64 valgrind-3.22.0-4.fc39.x86_64 ADDITIONAL INFORMATION The last command in the list that valgrind understands is BPF_MAP_FREEZE. There looks to be a number of additional BPF commands after BPF_MAP_FREEZE listed on the 6.11 kernel: https://elixir.bootlin.com/linux/v6.11-rc4/source/include/uapi/linux/bpf.h#L922 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 491242] Intermittent Plasma Crash with Multi-Monitor Setup, Custom Keyboard Layout, and Specific Window Focus Sequence
https://bugs.kde.org/show_bug.cgi?id=491242 William changed: What|Removed |Added URL||https://www.regfield.co.za -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 491242] New: Intermittent Plasma Crash with Multi-Monitor Setup, Custom Keyboard Layout, and Specific Window Focus Sequence
https://bugs.kde.org/show_bug.cgi?id=491242 Bug ID: 491242 Summary: Intermittent Plasma Crash with Multi-Monitor Setup, Custom Keyboard Layout, and Specific Window Focus Sequence Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: williamcand...@gmail.com Target Milestone: --- Hi. When i am using a multi-monitor setup with 3 monitors with a custom keyboard layout and a specific sequence of window focus events, the plasma crashes occasionally and that results in the entire desktop environment restarting. Reaching out looking for a work around for it. Your advice or assistance will extremely be appreciated. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 490182] memcheck fails with message "Assertion `offsetB < 4096' failed" when using a large number of active registers and tracking origins on aarch64 machine
https://bugs.kde.org/show_bug.cgi?id=490182 William Ashley changed: What|Removed |Added CC||w...@amazon.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 484279] background color used in settings leads to bad contrast
https://bugs.kde.org/show_bug.cgi?id=484279 William changed: What|Removed |Added Version|6.0.0 |6.1.0 --- Comment #7 from William --- bump: still a problem in plasma 6.1: breaking all dark color-schemes -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 484279] background color used in settings leads to bad contrast
https://bugs.kde.org/show_bug.cgi?id=484279 --- Comment #6 from William --- because the current background color comes from out of nowhere and cannot be configured in kde color-scheme settings. thats bad, but if a fix in Kirigami takes more effort/ time why not do what was done in qt5 and use the normal background color that is used everywhere else and can be configured? the color looks out of place in any color scheme even breeze default and is nowhere to be found in the color-scheme file. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 484279] background color used in settings leads to bad contrast
https://bugs.kde.org/show_bug.cgi?id=484279 William changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #4 from William --- bump: discover settings page is the only thing that seems to be affected. is the SwipeListItem not used anywhere else? And why cant discover set the normal default background overwritting whatever kirigami sets as the standard? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] With fractional scale, bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 William Chambers changed: What|Removed |Added CC||william+...@bioselement.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449105] Dragging a window that was opened maximized moves the mouse cursor to the top left corner of the window
https://bugs.kde.org/show_bug.cgi?id=449105 William Chambers changed: What|Removed |Added CC||william+...@bioselement.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 475871] [Wayland] Window resized incorrectly when initialised as maximised
https://bugs.kde.org/show_bug.cgi?id=475871 William Chambers changed: What|Removed |Added CC||william+...@bioselement.com Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED Ever confirmed|0 |1 --- Comment #2 from William Chambers --- I am running KDE with kwin 6.1 on Arch and am experiencing this exact problem. I originally thought it was an issue with Godot, but Konsole and Firefox have exhibited the same behavior. Example Video: https://youtu.be/Xr5cmBRonls Honestly have no idea how I could help debug this as it is super strange, but am happy to help however I can. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 479816] Get New... buttons not working with Qt 6.7
https://bugs.kde.org/show_bug.cgi?id=479816 --- Comment #16 from William Hood --- > As the bug title clearly states, this happens with Qt 6.7. So you did not > experience the bug until your distribution updated to that Qt version. Thank you for clarifying -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 479816] Get New... buttons not working with Qt 6.7
https://bugs.kde.org/show_bug.cgi?id=479816 --- Comment #14 from William Hood --- > FIXED means fixed in KDE. If your distribution still doesn't ship the fix, > you need to wait for it. Yes, I understand that. I'd like to think that KDE Neon, developed by KDE, is about as up-to-date as KDE gets. This is not an issue that's been present since January 14'th all this time, this is something that was working fine until just a few days ago and then suddenly broke. Either this bug regressed, or it's a brand new bug that just happens to have the same symptoms. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 479816] Get New... buttons not working with Qt 6.7
https://bugs.kde.org/show_bug.cgi?id=479816 William Hood changed: What|Removed |Added Resolution|FIXED |--- CC||william.arthur.hood@gmail.c ||om Status|RESOLVED|REOPENED --- Comment #12 from William Hood --- *** Bug 485392 has been marked as a duplicate of this bug. *** 👆️ Duplicate or not this issue has regressed. As of now I have all updates applied on KDE Neon, and the following "Get New" buttons do nothing when I attempt to use them: - Icons - Colors - Plasma Style - Window Decorations - Cursors - Splash Screens - Login Screen (SDDM) - Boot Splash Screen In other words, all of them. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 484498] New: Widgets/Addons cannot be updated
https://bugs.kde.org/show_bug.cgi?id=484498 Bug ID: 484498 Summary: Widgets/Addons cannot be updated 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: warca...@live.com Target Milestone: --- Created attachment 167770 --> https://bugs.kde.org/attachment.cgi?id=167770&action=edit Error on updating widget SUMMARY Widgets/Addons cannot be updated STEPS TO REPRODUCE 1. Right-click and select `Add widgets...` 2. Click on button "Get new widgets..." and select "Download new plasma widgets" 3. in window "Plasma Widgets", click on toolbar button "Show Only Updateable Entries" 4. the window content shows "No items found" message, however if you select "Show Only Installed Entries" button, the window content shows all widgets installed, every entry showed has 2 floating buttons (Use, Uninstall) or 3 floating buttons (Use, Update, Uninstall). This means that updateable widgets are not being recognized properly, 5. for updateable widgets, if you click on "Update" button, you get an error message similar to this: > Installation of /tmp/vsXxBE-Vivid-Dark-Plasma.tar.gz > failed: /home/warcayac/.local/share/plasma/desktoptheme/Vivid-Dark-Plasma > already exists the same happens when trying to update for Themes, styles, etc in the System Settings. OBSERVED RESULT 1. Updateable widgets are not listed on clicking on "Show Only Updateable Entries" button 2. Updateable widgets raise error messages when updating EXPECTED RESULT 1. Updateable widgets should be listed on clicking on "Show Only Updateable Entries" button 2. Updateable widgets should be able to update SOFTWARE/OS VERSIONS Linux distro: EndeavourOS Linux x86_64 Kernel: 6.8.1-zen1-1-zen KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Graphics platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484279] background color used in settings leads to bad contrast
https://bugs.kde.org/show_bug.cgi?id=484279 --- Comment #2 from William --- Added color-scheme (default breeze-dark with only one color changed to black). Why does a white-greyish color (#BEBEBE) when changing a color to black. It is impossible to change this color without also changing the window-background of lets say the calculator app, Maybe there should be an option to set this color specifically in the color-scheme (where #BEBEBE wich is 190,190,190 in dez) is never even present. Anyways somehow the behind-the-options stuff that generates this color is not working properly for dark colors. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484279] background color used in settings leads to bad contrast
https://bugs.kde.org/show_bug.cgi?id=484279 --- Comment #1 from William --- Created attachment 167625 --> https://bugs.kde.org/attachment.cgi?id=167625&action=edit color-scheme -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484279] New: background color used in settings leads to bad contrast
https://bugs.kde.org/show_bug.cgi?id=484279 Bug ID: 484279 Summary: background color used in settings leads to bad contrast Classification: Applications Product: Discover Version: 6.0.2 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: wi11ia...@pm.me CC: aleix...@kde.org Target Milestone: --- Created attachment 167624 --> https://bugs.kde.org/attachment.cgi?id=167624&action=edit picture of discover settings SUMMARY The Settings page in Discover uses a new background color for the row, which is generated from the color-schemes [Colors:Window] -> BackgroundNormal value, this however does not work properly for very dark themes, e.g. pure black window color leads to white text on almost white background. STEPS TO REPRODUCE 1. Use color-scheme Breeze-Dark 2. Change Window-background color to pure-black #00 3. Open Discover Settings OBSERVED RESULT Settings almost unreadable, background color is almost white. EXPECTED RESULT The colors from my color-scheme should not be "manipulated" and the background should just be black. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 482947] Screen turns off automatically with Plasma 6 despite being configured not to
https://bugs.kde.org/show_bug.cgi?id=482947 --- Comment #8 from William AC --- (In reply to Jakob Petsovits from comment #7) > Thanks. Let me try out your settings and see if I can reproduce something > similar on my system. Thanks. At present I've changed to X11 because it's more stable than Wayland (moreover, certain apps are not compatible yet), and I'm not having this problem so far. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 482947] Screen turns off automatically with Plasma 6 despite being configured not to
https://bugs.kde.org/show_bug.cgi?id=482947 --- Comment #6 from William AC --- Sorry, Lock screen automatically: - after (5 min): uncheked - after waking from sleep: check Allow unlocking without password for: 5 sec -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 482947] Screen turns off automatically with Plasma 6 despite being configured not to
https://bugs.kde.org/show_bug.cgi?id=482947 --- Comment #4 from William AC --- I've attached an image in my original post. All options are disabled/unchecked -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482947] Screen turns off automatically with Plasma 6 despite being configured not to
https://bugs.kde.org/show_bug.cgi?id=482947 William AC changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|DUPLICATE |--- --- Comment #2 from William AC --- (In reply to Jakob Petsovits from comment #1) > I'm going to assume that this is on X11 and a duplicate of Bug 481308. > Please update to Plasma 6.0.2 and reopen this in case you're still seeing > this after the update. > > *** This bug has been marked as a duplicate of bug 481308 *** This happened with Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482947] Screen turns off automatically with Plasma 6
https://bugs.kde.org/show_bug.cgi?id=482947 William AC changed: What|Removed |Added CC||warca...@live.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482947] New: Screen turns off automatically with Plasma 6
https://bugs.kde.org/show_bug.cgi?id=482947 Bug ID: 482947 Summary: Screen turns off automatically with Plasma 6 Classification: Applications Product: systemsettings Version: 6.0.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_powerdevil Assignee: plasma-b...@kde.org Reporter: warca...@live.com CC: k...@privat.broulik.de, natalie_clar...@yahoo.de Target Milestone: --- Created attachment 166777 --> https://bugs.kde.org/attachment.cgi?id=166777&action=edit my current Energy Saving settings SUMMARY I just installed Endeavouros with KDE Plasma 6, and I’m getting this problem with my screen even when Energy Saving is unchecked all its properties (see attachment). My screen persists in turning off after 5 or 7 minutes, sometimes it fails to recover after making movements with the mouse and stays off. This did not happen with Plasma 5. STEPS TO REPRODUCE 1. Uncheck all properties on Energy Saving settings 2. Apply changes 3. Don't touch/move anything on your PC for 7 minutes at least OBSERVED RESULT Screen turns off EXPECTED RESULT Screen stays on SOFTWARE/OS VERSIONS - OS: EndeavourOS Linux x86_64 - Kernel: 6.7.9-zen1-1-zen - Shell: zsh 5.9 - Resolution: 3440x1440 - DE: Plasma 6.0.1 - WM: KWin - Icons: breeze [GTK2/3] - Terminal: WarpTerminal - CPU: AMD Ryzen 7 1700 (16) @ 3.800GHz - GPU: NVIDIA GeForce GTX 1070 - Memory: 15905MiB - KDE Frameworks version: 6.0.0 - Qt version: 6.6.2 - Monitor: Huawei ZQE-CBA ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 482202] Elisa: Improve Tray Icon
https://bugs.kde.org/show_bug.cgi?id=482202 --- Comment #1 from William --- after reporting found this bug from 2021: https://bugs.kde.org/show_bug.cgi?id=434560 with a potential fix already, wondering why that was not applied. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 482202] New: Elisa: Improve Tray Icon
https://bugs.kde.org/show_bug.cgi?id=482202 Bug ID: 482202 Summary: Elisa: Improve Tray Icon Classification: Applications Product: Elisa Version: 23.08.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: wi11ia...@pm.me Target Milestone: --- Almost all apps that include a minimize to sys-tray option show up in the sys-tray always or include an option to do so. This way the app can be minimized to tray not just by pressing close but also by pressing on the sys-tray icon. (like telegram for example) To make the best music player on KDE even better pls add an option to always show tray icon and let user toggle the state by clicking it. STEPS TO REPRODUCE 1. Open Elisa Settings 2. Activate Sys-tray icon when window is closed OBSERVED RESULT sys-tray icon only shows when closed EXPECTED RESULT add another option below the sys-tray activation that activates the sys-tray icon always. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 477337] New: Show inputs supported by an app on its product page
https://bugs.kde.org/show_bug.cgi?id=477337 Bug ID: 477337 Summary: Show inputs supported by an app on its product page Classification: Applications Product: Discover Version: unspecified Platform: unspecified OS: Unspecified Status: REPORTED Severity: wishlist Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: gamerminst...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 163345 --> https://bugs.kde.org/attachment.cgi?id=163345&action=edit Mockup of new icons When using Linux on less common form factors (tablets, touch screens, Home Theater setups), usually there is no way to know if an app is going to be usable until you install and run it. For example, you have no idea if an app will respond to touch inputs properly, or if a game will work well with a gamepad. However, it has come to my attention that the Appstream specification allows apps to list what s they support. see here: https://freedesktop.org/software/appstream/docs/chap-Metadata.html When viewing an app in Discover, would it be possible to add icons to indicate what forms of input this app supports? Screenshot attached as a rough mockup of what I'm thinking. If this is an acceptable idea, I am willing to take an honest stab at implementing this myself in a pull request. However, I am a web developer, with barely any c++ experience. I would likely need guidance. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 460616] disInstr(arm64): unhandled instruction 0x4E819402 (dotprod/ASIMDDP)
https://bugs.kde.org/show_bug.cgi?id=460616 --- Comment #6 from William Ashley --- Thanks Mark! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 475429] New: Discover Crash
https://bugs.kde.org/show_bug.cgi?id=475429 Bug ID: 475429 Summary: Discover Crash Classification: Applications Product: Discover Version: 5.27.8 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: willsa...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.27.8) Qt Version: 5.15.3 Frameworks Version: 5.104.0 Operating System: Linux 5.15.0-86-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.3 LTS DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: Crash when launching home tab while loading app icons The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7efcff3a7ba4 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #5 0x7efcff3a7c10 in PackageKitBackend::resolvePackages(QStringList const&) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #6 0x7efcff3a89f7 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #7 0x7efcff3b4fd5 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #8 0x7efd3fea141e in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7efd41770713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7efd3fe73e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7efd3fe76f27 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7efd3fecda67 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7efd3e5a4d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7efd3e5fa258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7efd3e5a23e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7efd3fecd0b8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7efd3fe7275b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7efd3fe7acf4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x55fa22df1c63 in ?? () #20 0x7efd3f78fd90 in __libc_start_call_main (main=main@entry=0x55fa22df1340, argc=argc@entry=1, argv=argv@entry=0x7ffdb6276768) at ../sysdeps/nptl/libc_start_call_main.h:58 #21 0x7efd3f78fe40 in __libc_start_main_impl (main=0x55fa22df1340, argc=1, argv=0x7ffdb6276768, init=, fini=, rtld_fini=, stack_end=0x7ffdb6276758) at ../csu/libc-start.c:392 #22 0x55fa22df26a5 in ?? () [Inferior 1 (process 3887) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473115] clientFullScreenSet signal is not being emitted on Wayland
https://bugs.kde.org/show_bug.cgi?id=473115 William Franco Abdul Hai changed: What|Removed |Added CC||haiwilli...@gmail.com --- Comment #1 from William Franco Abdul Hai --- I can confirm that I'm also facing the same problem on Wayland. Same Plasma and Frameworks versions as OP, and QT version 5.15.9. I'm running NixOS unstable. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 460616] disInstr(arm64): unhandled instruction 0x4E819402
https://bugs.kde.org/show_bug.cgi?id=460616 William Ashley changed: What|Removed |Added Attachment #160568|0 |1 is obsolete|| --- Comment #3 from William Ashley --- Created attachment 160669 --> https://bugs.kde.org/attachment.cgi?id=160669&action=edit Patch to add FEAT_DotProd support -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 460616] disInstr(arm64): unhandled instruction 0x4E819402
https://bugs.kde.org/show_bug.cgi?id=460616 --- Comment #2 from William Ashley --- On Friday I submitted the change to the valgrind-developers mailing list, https://sourceforge.net/p/valgrind/mailman/valgrind-developers/thread/ed40273d-295d-445c-8d97-9fc48f535...@amazon.com/ -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 441109] [ARM64] Invalid write of size 8 when it's really 16
https://bugs.kde.org/show_bug.cgi?id=441109
--- Comment #2 from William Ashley ---
With stp (store pair), there's a similar problem. Pairs of 32, 64 and 128-bit
values all get reported as the wrong write sizes.
asm volatile ("stp s0, s1, [%0]" :: "r" (ptr) : "s0", "s1", "memory");
asm volatile ("stp d0, d1, [%0]" :: "r" (ptr) : "d0", "d1", "memory");
asm volatile ("stp q0, q1, [%0]" :: "r" (ptr) : "q0", "q1", "memory");
==26048== Invalid write of size 4
==26048==at 0x400630: main (strtest.c:12)
==26048== Address 0x4a1a140 is 0 bytes after a block of size 256 alloc'd
==26048==at 0x48682A4: malloc (vg_replace_malloc.c:431)
==26048==by 0x4005F3: main (strtest.c:3)
==26048==
==26048== Invalid write of size 8
==26048==at 0x400638: main (strtest.c:13)
==26048== Address 0x4a1a140 is 0 bytes after a block of size 256 alloc'd
==26048==at 0x48682A4: malloc (vg_replace_malloc.c:431)
==26048==by 0x4005F3: main (strtest.c:3)
==26048==
==26048== Invalid write of size 8
==26048==at 0x400640: main (strtest.c:14)
==26048== Address 0x4a1a140 is 0 bytes after a block of size 256 alloc'd
==26048==at 0x48682A4: malloc (vg_replace_malloc.c:431)
==26048==by 0x4005F3: main (strtest.c:3)
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 441109] [ARM64] Invalid write of size 8 when it's really 16
https://bugs.kde.org/show_bug.cgi?id=441109
--- Comment #1 from William Ashley ---
To expand on this a bit, here's a sweep through all of the 'str' sizes:
#include
int main(void) {
char *ptr = malloc(256);
ptr += 256;
asm volatile ("str b0, [%0]" :: "r" (ptr) : "b0", "memory");
asm volatile ("str h0, [%0]" :: "r" (ptr) : "h0", "memory");
asm volatile ("str s0, [%0]" :: "r" (ptr) : "s0", "memory");
asm volatile ("str d0, [%0]" :: "r" (ptr) : "d0", "memory");
asm volatile ("str q0, [%0]" :: "r" (ptr) : "q0", "memory");
free(ptr - 256);
return 0;
}
which under the latest valgrind release shows the expected sizes except for q
==5990== Invalid write of size 1
==5990==at 0x400608: main (strtest.c:5)
==5990== Address 0x4a1a140 is 0 bytes after a block of size 256 alloc'd
==5990==at 0x48682A4: malloc (vg_replace_malloc.c:431)
==5990==by 0x4005F3: main (strtest.c:3)
==5990==
==5990== Invalid write of size 2
==5990==at 0x400610: main (strtest.c:6)
==5990== Address 0x4a1a140 is 0 bytes after a block of size 256 alloc'd
==5990==at 0x48682A4: malloc (vg_replace_malloc.c:431)
==5990==by 0x4005F3: main (strtest.c:3)
==5990==
==5990== Invalid write of size 4
==5990==at 0x400618: main (strtest.c:7)
==5990== Address 0x4a1a140 is 0 bytes after a block of size 256 alloc'd
==5990==at 0x48682A4: malloc (vg_replace_malloc.c:431)
==5990==by 0x4005F3: main (strtest.c:3)
==5990==
==5990== Invalid write of size 8
==5990==at 0x400620: main (strtest.c:8)
==5990== Address 0x4a1a140 is 0 bytes after a block of size 256 alloc'd
==5990==at 0x48682A4: malloc (vg_replace_malloc.c:431)
==5990==by 0x4005F3: main (strtest.c:3)
==5990==
==5990== Invalid write of size 8
==5990==at 0x400628: main (strtest.c:9)
==5990== Address 0x4a1a140 is 0 bytes after a block of size 256 alloc'd
==5990==at 0x48682A4: malloc (vg_replace_malloc.c:431)
==5990==by 0x4005F3: main (strtest.c:3)
Decode for the 'q' case does look correct (GET:V128, so it would be a 16-byte
value)
(arm64) 0x400628: str q0, [x0, #0]
-- IMark(0x400628, 4, 0) --
t21 = Add64(GET:I64(16),0x0:I64)
STle(t21) = GET:V128(320)
PUT(272) = 0x40062C:I64
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 441109] [ARM64] Invalid write of size 8 when it's really 16
https://bugs.kde.org/show_bug.cgi?id=441109 William Ashley changed: What|Removed |Added CC||w...@amazon.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 438322] disInstr(arm): unhandled instruction: 0xE320F014
https://bugs.kde.org/show_bug.cgi?id=438322 William Ashley changed: What|Removed |Added CC|w...@amazon.com | -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 438322] disInstr(arm): unhandled instruction: 0xE320F014
https://bugs.kde.org/show_bug.cgi?id=438322 William Ashley changed: What|Removed |Added CC||w...@amazon.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 472742] New: Update downloads fail to resume after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=472742 Bug ID: 472742 Summary: Update downloads fail to resume after waking from sleep Classification: Applications Product: Discover Version: 5.27.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: gamerminst...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY *** 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. Have several GB of updates in Discover. 2. Click Update All 3. Go grab a coffee, let your computer fall asleep. Wake it back up. OBSERVED RESULT All internet activity from the Discover app will have ceased and will not continue until you click Cancel and retry updates. EXPECTED RESULT Downloads should resume without me manually tricking them into resuming. 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.
[valgrind] [Bug 460616] disInstr(arm64): unhandled instruction 0x4E819402
https://bugs.kde.org/show_bug.cgi?id=460616 William Ashley changed: What|Removed |Added CC||w...@amazon.com --- Comment #1 from William Ashley --- Created attachment 160568 --> https://bugs.kde.org/attachment.cgi?id=160568&action=edit Patch to add FEAT_DotProd support I have implemented support for the dot product instructions (more specifically those under the FEAT_DotProd feature). The attached patch file applies cleanly to 'master' as of this writing. I haven't yet figured out the 'correct' process for submitting changes to the valgrind project. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 443150] losing focus changes content
https://bugs.kde.org/show_bug.cgi?id=443150 William Kendrick changed: What|Removed |Added CC||n...@sonic.net --- Comment #1 from William Kendrick --- This happens to me with Wallet Manager 21.12.3 (under Kubuntu 22.04.2), and it's super intrusive. :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 --- Comment #10 from William Coolman --- My mistake. I'll correct that. On Wed, May 31, 2023, 7:32 AM Federico Dossena wrote: > https://bugs.kde.org/show_bug.cgi?id=469445 > > --- Comment #9 from Federico Dossena --- > Why did you mark this as fixed? That's a workaround, not a solution. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 William Coolman changed: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED --- Comment #7 from William Coolman --- Removing [ScreenMapping] entry from /home/[user]/.config/plasma-org.kde.plasma.desktop-appletsrc fixed the problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 --- Comment #6 from William Coolman --- (In reply to William Coolman from comment #5) > Created attachment 159362 [details] > attachment-3610397-0.html > > I don't think this is the same bug. My memory usage looks normal. > > On Wed, May 24, 2023 at 9:35 AM Paul Worrall > wrote: > > > https://bugs.kde.org/show_bug.cgi?id=469445 > > > > Paul Worrall changed: > > > >What|Removed |Added > > > > > > CC||wcool...@gmail.com > > > > --- Comment #4 from Paul Worrall --- > > *** Bug 470195 has been marked as a duplicate of this bug. *** > > > > -- > > You are receiving this mail because: > > You are on the CC list for the bug. Ok, removing the ScreenMapping entry made things work again. I'll close this ticket. Thanks for your help! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 470195] Cannot open any apps, getting "Resource error (fork failure): Cannot allocate memory" on everything
https://bugs.kde.org/show_bug.cgi?id=470195 William Coolman changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- Ever confirmed|0 |1 --- Comment #2 from William Coolman --- I don't appear to have a memory leak, so I don't think the suggested bug that this was listed as a clone is accurate. I'm reopening this ticket. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469445] Ever-growing ScreenMapping entry in config file makes plasmashell slow down and eventually crash
https://bugs.kde.org/show_bug.cgi?id=469445 --- Comment #5 from William Coolman --- I don't think this is the same bug. My memory usage looks normal. On Wed, May 24, 2023 at 9:35 AM Paul Worrall wrote: > https://bugs.kde.org/show_bug.cgi?id=469445 > > Paul Worrall changed: > >What|Removed |Added > > > CC||wcool...@gmail.com > > --- Comment #4 from Paul Worrall --- > *** Bug 470195 has been marked as a duplicate of this bug. *** > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468899] [Spectacle 23.04] Video Recording - Add configuration options and shortcuts to Spectacle settings page.
https://bugs.kde.org/show_bug.cgi?id=468899 William Herron changed: What|Removed |Added CC||wherro...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 470195] New: Cannot open any apps, getting "Resource error (fork failure): Cannot allocate memory" on everything
https://bugs.kde.org/show_bug.cgi?id=470195 Bug ID: 470195 Summary: Cannot open any apps, getting "Resource error (fork failure): Cannot allocate memory" on everything 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: wcool...@gmail.com Target Milestone: --- Created attachment 159219 --> https://bugs.kde.org/attachment.cgi?id=159219&action=edit Can't open anything through main K menu, Task Manager, or Desktop Operating System: Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-20-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 PRO 5650U with Radeon Graphics Memory: 14.4 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 20XF004SUS System Version: ThinkPad T14s Gen 2 ADDITIONAL INFORMATION I can't open *anything* in the K menu or from the task manager. I'm getting a "Resource error (fork failure): Cannot allocate memory" error for everything, see attachment. Also, none of my desktop icons are viewable. I have 16 gigs of memory total, and have been running Kubuntu for a year without any real problems. I don't know what update brought on this behavior? Running free -h shows I have 9.1Gi left, so I don't know what is going on. The only way I was able to even open Firefox to file this bug report was krunner. So far, I've been able to open most things through it, or typing into konsole once I opened that through krunner, but this is a huge inconvenience. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457487] After fixing the shaded/shuttered window feature, restarting kwin_x11 --replace forgets the shaded window sizes
https://bugs.kde.org/show_bug.cgi?id=457487 William Kendrick changed: What|Removed |Added CC||n...@sonic.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450582] Some change between 5.24.0 and 5.24.1 broke windows shade/shutter feature
https://bugs.kde.org/show_bug.cgi?id=450582 William Kendrick changed: What|Removed |Added CC||n...@sonic.net -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468453] Installed and am trying to setup KDE connect.
https://bugs.kde.org/show_bug.cgi?id=468453 William changed: What|Removed |Added Attachment #158058|0 |1 is obsolete|| Attachment #158059|0 |1 is obsolete|| Attachment #158085|0 |1 is obsolete|| --- Comment #4 from William --- Created attachment 158088 --> https://bugs.kde.org/attachment.cgi?id=158088&action=edit scrn shot not relevant After the initial install failed to connect, I rebooted both the computer and the phone with slightly better results...but serious problems still remain. The phone and computer connected, but all the words are gibberish --words are missing letters. I also discovered that if I try to edit the computer name, then KDE only detects about half the keys on my keyboard. I want this to work so that I can send SMS messages from my Windows 10pro laptop. Is that possible. Currently, i do not see that function is available -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468453] Installed and am trying to setup KDE connect.
https://bugs.kde.org/show_bug.cgi?id=468453 --- Comment #3 from William --- Created attachment 158085 --> https://bugs.kde.org/attachment.cgi?id=158085&action=edit scrn shot of KDE connect After the initial install failed to connect, I rebooted both the computer and the phone with slightly better results...but serious problems still remain. The phone and computer connected, but all the words are gibberish --words are missing letters. I also discovered that if I try to edit the computer name, then KDE only detects about half the keys on my keyboard. I want this to work so that I can send SMS messages from my Windows 10pro laptop. Is that possible. Currently, i do not see that function is available. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468453] Installed and am trying to setup KDE connect.
https://bugs.kde.org/show_bug.cgi?id=468453 William changed: What|Removed |Added CC||bwett...@gmail.com --- Comment #2 from William --- Created attachment 158059 --> https://bugs.kde.org/attachment.cgi?id=158059&action=edit scrn shot of KDE connect I rebooted both the computer and the phone with slightly better results...but serious problems still remain. See screen shot 2. As that shows, the phone and computer connected, but all the words are gibberish --words are missing letters. I also discovered that if I try to edit the computer name, then only about half the keys on my keyboard are detected. I want this to work so that I can send SMS messages from my Windows 10pro laptop. Is that possible. Currently, i do not see that function is available. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468453] Installed and am trying to setup KDE connect.
https://bugs.kde.org/show_bug.cgi?id=468453 --- Comment #1 from William --- I opened a command prompt and tried your troubleshooting commands. Check that the process is listening on the network: sudo netstat -tunelp | grep -i kdeconnect error: sudo is not a recognized command Are the ports open/blocked? netcat -z -v 1714-1764 error: cannot find file I opened the ports to no avail. Same results -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468453] New: Installed and am trying to setup KDE connect.
https://bugs.kde.org/show_bug.cgi?id=468453 Bug ID: 468453 Summary: Installed and am trying to setup KDE connect. Classification: I don't know Product: kde Version: unspecified Platform: Microsoft Windows OS: Android 13.x Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bwett...@gmail.com Target Milestone: --- Created attachment 158058 --> https://bugs.kde.org/attachment.cgi?id=158058&action=edit scrn shot of KDE connect SUMMARY See attached screen shot. As you see, KDE does not know my computer. I tried typing in my computer name but KDE will not let me type the letter B *** 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. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 William changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #71 from William --- (In reply to Nate Graham from comment #70) > Please stop changing the status to VERIFIED despite not verifying the fix. > I'd like William to do that, since he's the one who reported this issue. Sry i didnt keep up with what was happening in this isssue and i only recently got the 5-27 update in manjaro stable. But i am happy to report now that it doesnt happen anymore for me. i removed my "read-only" workaround script and used the command "kquitapp5 plasmashell && kstart5 plasmashell" at least 50 times in a row, which previously would always result in some form of icon scramble, but this time it did not. Good job to whatever was done in the end that fixed it. 5.27 seems like a great release! PS: manjaro skipped the early point releases and went straight to plasma 5.27.3. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 456724] No transition when changing color schemes through "Use" button in "Get New Color Schemes"
https://bugs.kde.org/show_bug.cgi?id=456724 William F. changed: What|Removed |Added Version Fixed In||5.27 Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/08d37c535ea1438e124347a49 ||88bff0eb98f375d -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 456724] No transition when changing color schemes through "Use" button in "Get New Color Schemes"
https://bugs.kde.org/show_bug.cgi?id=456724 William F. changed: What|Removed |Added CC||haiwilli...@gmail.com Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #4 from William F. --- Fixed as of https://invent.kde.org/plasma/plasma-workspace/-/commit/08d37c535ea1438e124347a4988bff0eb98f375d in plasma-workspace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #39 from William --- bump: plasma 5.26.4, 2 month after the latest claum it would be fixed this is still happening alot on fresh kde installs, how can i get the devs that worked on https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1150 and https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2240 to take a look at this issue again? it is rly rly annoying and an absolute no-go. As was pointed out it has nothing to do with systemd or anything happening before plasmashell startup. it happens even when plasmashell is started manually. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #37 from William --- the point was that nothing should ever write to said file ever unless triggerd by a user-action (aka creating a new icon or moving one) parallel or not it doesnt matter. Also systemd cannot be blamed for this all the major distros use it and they all manage to not f*** with user settings during startup process. plasma is the only one where this happens. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #34 from William --- ok still happens with the old style scramble when doing the command: kquitapp5 plasmashell && kstart5 plasmashell seeing this in the log output if it helps: file:///usr/lib/qt/qml/org/kde/plasma/private/containmentlayoutmanager/BasicAppletContainer.qml:144: TypeError: Cannot read property 'width' of null org.kde.plasma.containmentlayoutmanager: Error: cannot change the containment to AppletsLayout Trying to use rootObject before initialization is completed, whilst using setInitializationDelayed. Forcing completion wish someone wouldve actually worked with me or anyone who has this issue and can reproduce it effortlessly. i wouldve been happy to test out any new development version of plasmashell. plasma is by far the best DE there is but issues like this make it impossible to recommend. can we use this ticket or do i have to open it again with the exact same description? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 William changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #32 from William --- still happening on manjaro stable 5.26.2 changes did affect the behavoir instead of: AA B -> B C C it now scrambles the icons in a different way: AA B -> B CC sry but this is not fixed.- something still wrong here. why is it so hard to remove any logik that touches that desktop-appletrc file during plasmashell startup? you should only ever need to read from it till startup is completly done and in case of items or icons not found in it just dont display them till the user moves them to a new spot... -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 460013] New: When logging in, plasmashell fails to load so the program has to be manually opened in the Konsole via the control+esc menu
https://bugs.kde.org/show_bug.cgi?id=460013 Bug ID: 460013 Summary: When logging in, plasmashell fails to load so the program has to be manually opened in the Konsole via the control+esc menu Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: wclifton...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Created attachment 152602 --> https://bugs.kde.org/attachment.cgi?id=152602&action=edit A video I recorded after encountering the bug and then immediately logging out which is when I started filming. SUMMARY *** 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 *** I logged into my computer after it loaded the SDDM login page, I selected the option "Plasma (X11)" or "Plasma (Wayland)", the loading screen went blank and Steam loaded (it is set to load on boot), if I closed or minimised Steam, then there would only be a black screen, the KWin functions work properly such as Alt+Tab or Meta+Tab but the shell has not loaded, I do not see my wallpaper background or any of the desktop features such as the floating panel or clock widget and the only way to open a program is via the Konsole which can be opened from the "systemmonitor" program which loads when control+escape is pressed on the keyboard. I first saw this bug when I had the "obsolete" KDE "Liquidshell" installed which I had load instead of the "plasmashell" even when "Plasma (X11)" was selected in the SDDM login menu instead of "Liquidshell" in the SDDM menu, I then removed the "Liquidshell" via the Konsole using the command "sudo apt remove liquidshell" and logged out whereby the "liquidshell" option was removed. The other options in the SDDM login menu were: Gnome (Wayland) Plasma (Wayland) Gnome (Ubuntu) Gnome (on X.org) Gnome (on X11) Liquidshell Plasma (X11) Ubuntu Selecting Ubuntu would load the GNOME 3.23 shell in light theme; trying to select the dark theme would crash the GNOME shell and load a menu asking to log out of the system; All KDE apps would load in the application menu including the Plasma settings application. STEPS TO REPRODUCE n/a I recorded this bug because I logged in and then immediately logged out which is when I started recording from my phone as I run KDE Neon on real hardware (is listed as an attachment) OBSERVED RESULT "Plasmashell" failed to load on boot so it had to be manually loaded via the Konsole but if the Konsole crashed or was manually closed, then the "plasmashell" would also close. EXPECTED RESULT "Plasmashell" loads on boot with no errors, not requiring the program to be manually loaded on boot via the Konsole. SOFTWARE/OS VERSIONS Windows: n/a macOS: n/a Linux/KDE Plasma: KDE Neon 5.25 with KDE Plasma 5.25 (available in About System) Info copied from Neofetch in Konsole: `..---+/---..`william@MEDIONKDENEON `---.`` `` `.---.`- .--.````-:-. OS: KDE neon User - 5.25 x86_64 `:/: `.//.` :/-Host: E32012 .:.`---` `--.`.:` Kernel: 5.15.0-48-generic .:` `--`.:-`:. Uptime: 16 mins `/`:. `.-::-.` -:` `/`Packages: 3648 (dpkg), 98 (flatpak), 28 (snap) /./. `::` .:.:Shell: bash 5.0.17 `/.: `+++/ /` `+` Resolution: 1920x1080 /+` -- .` :. .+: DE: Plasma `/.: `+++/ /` `+` Theme: [Plasma], Graphite-dark-nord [GTK2/3] /`/. `::` .:.:Icons: WhiteSur [Plasma], WhiteSur [GTK2/3] ./`:. `.:::-.` -:` `/`Terminal: konsole .:` `--`.:-`:. CPU: AMD Ryzen 3 PRO 4350G with .:.`---` `--.`.:` Radeon Graphics (8) @ 4.105GHz `:/: `.//.` :/- GPU: AMD ATI 0d:00.0 Renoir .-:.````-:-. Memory: 3012MiB / 23417MiB `---.`` `` `.---.` `..---+/---..` KDE Plasma Version: 5.25 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.15.0-48-generic (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION Liquidshell was installed the first time I came across this bug today but was latterly removed (as seen in
[plasmashell] [Bug 454345] Desktop Icons sometimes get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #29 from William --- do desktop dimensions also change during plasmashell startup? the MergeRequest https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2118 indeed sounds pormising but lets pls not close the bug until it is fixed for sure. This issue occured on all gpus all monitors (single or multi monitor) and all distributions (i tried quite a bit of KDE installs), it is 100% reproducable with the posted plasmashell restart commands (so not only during KDE startup, just plasmashell startup im still baffled how its hard to reproduce while it happens to me every KDE install ever within a week of using it, nothing special (no power user stuff or customizations). I know how to install latest KDE Neon unstable if it lands there i can check it if i have the time otherwise idk how to verify early if this MR would help -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #13 from William --- (In reply to Uwe Dippel from comment #12) > Are we now running into something else, or am I at the wrong report? Earlier > we were at 'scrambled at reboot' AFAIK. Now we are at Plasmashell Start? > I still experience the 'at reboot' st times. Like today, see attachment. > Everything in 'Desktop' plus my desktop icons are placed in a wrapped > fashion above the default desktop background (see attachment). > Then I have to 'Customize Layout', add the PlasmaConfigSaver and restore to > my last saved desktop layout (see attachment). > > Please, inform me if this is not the appropriate bug, and the 'RESOLVED > CLOSED' (LOL) original was reopened elsewhere, thanks. this is the correct bug report, i just named it "on plasmashell start" as that is precisly what is happening during reboot, relogin or via commands, the part in question is the plasmashell startup that messes things up. Mb u can run the command "kquitapp5 plasmashell && kstart5 plasmashell" and see if it happnes to u with that aswell. Anyways the old report was closed and u are right here, welcome to the a bug that is now 7 years old, twice marketed as fixed and still some process during startup does not respect icon positions and on top of all also tries overwrites a users config file that it shouldnt ever even attempt to write to. here is to another 6 years of noone bothering to fix the most important issue in KDE plasma and why windows users wont switch, quote "if it cant even remember my desktop icons i cant trust it to store anything, even if microsoft collects all my data at least it does know how to store stuff lol" try to install xfce or zorinOS if u dont want to scare them away. kde just doesnt prioritize this kind of stuff - every other company wouldve had complete featurefreeze and stopped all further coding till this is fixed but opensource u cant do that so every1 just does what he likes to do. even throwing money at this thing does nothing,... i guess i have to learn coding and fix it myself, even if that takes 3 years it probably is faster -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #6 from William --- This bug happens on all configs (row / clolumn) align fixed positions, doesnt matter. The icons change position and wanna be in a different state than the one saved in the appletrc "positions=" line. YES if u restart plasmashell and dont have the file in readOnly mode that line gets rewritten, but even if u put it in readOnly the icons shift and the config file shows different positions that those displayed on the desktop. There is only 1 screen at all times and no the scramble does not follow alphabethical order or reverse or anything like that... when in row alignment (with manual sorting) icons in a column: turn into some sort of staircase with only the upper left staying where it was AA B -> B C C Also there is no "[ScreenConnectors]" section in the ~/.config/plasmashellrc file. As i said on new user it is not reproducable immediatly, just when u start using that user after a while soemthing happens (mb plasma crashes or doesnt shutdown properly or smthing) and after that icon scrambles happen almost everytime plasmashell is restarted. I backed up the ~/.config/plasma-org.kde.plasma.desktop-appletsrc file from fresh user where it did not happen, when it started happening i replaced it with the backup, that did NOT fix it either: the icons keep scrambling every restart. Mb its note worthy but the desktop in question always uses "large" label width for the icons. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] Desktop Icons get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 --- Comment #1 from William --- Additional Observarions on my part after the dissapointment that it was still not fixed with 5.24.5: 1: you can put the file where the desktop icon positions are stored: "~/.config/plasma-org.kde.plasma.desktop-appletsrc" in readonly mode and icons still get scrambled, even though the file does not seem to be changed. 2: when executing the restart commands the desktop icons can stay in a different state then currently shown when u have focus on a window, clicking on the desktop shows icons on different positions then when a window is in focus, this stopps after a while and the "desktop-state" when no window is in focus takes over for good 3: i have not completly figured out when this starts happening as you can create a fresh user and it doesnt happen for it until some point when it happens once, then it seems to happen everytime u just restart the shell or login. Deleting the ~/.config file does not have any effect on it either having to recreate ur desktop. 4: happens with no activitys and on single desktops, plasma uses systemd-startup. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #213 from William --- i created new bug for those still expirencing the issue here: https://bugs.kde.org/show_bug.cgi?id=454345 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454345] New: Desktop Icons get scrambled on plasmashell startup
https://bugs.kde.org/show_bug.cgi?id=454345 Bug ID: 454345 Summary: Desktop Icons get scrambled on plasmashell startup Product: plasmashell Version: 5.24.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Folder Assignee: plasma-b...@kde.org Reporter: wi11ia...@pm.me CC: h...@kde.org Target Milestone: 1.0 SUMMARY *** Everything is already explained here: https://bugs.kde.org/show_bug.cgi?id=354802 except that the this has nothing to do with resolution changes, so 5.24.5 did not fix it. *** STEPS TO REPRODUCE 1. put icons on desktop 2. kquitapp5 plasmashell && kstart5 plasmashell OBSERVED RESULT icons switch position, seemingly random with some sort of order to it so the same layout of icons mostly results in teh same scamble EXPECTED RESULT icons stay where they were SOFTWARE/OS VERSIONS Betriebssystem: Manjaro Linux KDE-Plasma-Version: 5.24.5 KDE-Frameworks-Version: 5.93.0 Qt-Version: 5.15.3 Kernel-Version: 5.17.6-1-MANJARO (64-bit) Grafik-Plattform: X11 ADDITIONAL INFORMATION This has nothing to do with resolutions, multimonitors or variable refresh rates or what not. Happens on logout/login or reboot aswell. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #204 from William --- (In reply to Nate Graham from comment #203) > Please file a new bug report as the original cause of this one has been > fixed. There might be new causes, but those need new bug reports. what policy is that? the bug description and everything in it fits the issue i have exactly, THIS bug is not fixed, creating a new one with exact same description will just lead to it not being found and not gaining any credibility, so it can be ignored for 6years again? There was a commit that claimed to fix this and it didnt: THIS BUG IS NUMBER 1 REASON u cannot install KDE to new users who dont want windows11.- and the action is to just ignore it and put it on "CLOSED FIXED" ? I am here telling you and whoever claimed to fix this, i can pay you if this gets finally fixed for real! And to anyone coming here from google, and co: THIS BUG IS NOT FIXED,.. it is very much still happening and 100% reproduceable every single logout/login, you are not the only one and your install is not at fault. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 William changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #202 from William --- Ok this might be a slitghtly different issue but the desktop icons still get scrambled and if i run the command cp -v ~/.config/plasma-org.kde.plasma.desktop-appletsrc.bak ~/.config/plasma-org.kde.plasma.desktop-appletsrc followed by the usual plamsashell restart: kquitapp5 plasmashell && kstart5 plasmashell the desktop ends up in a weird state where the icons show up where they belong as long as the focus is on the terminal, but when clicking anywhere on teh desktop the icons show up scrambled and on different positions. PLS PLS someone fix this issue for good, this is the nr1 reason i have to install xfce desktops on new linux user pcs because this happening every reboot/login would just drive em away from linux again at this point i am willing to pay for this to get fixed for real. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #201 from William --- still also happens but not always on running "pkill plasmashell && kstart5 plasmashell" just tested this too, every 2nd or 3rd time that command changes deskto item positions aswell..- pls remove any codepath that touches that file during plasmashell start! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 --- Comment #200 from William --- what i just dont understand is why the "plasma-org.kde.plasma.desktop-appletsrc" file in the user home gets overwritten at all. if it already exists it shouldnt be changed by a login like ever.. i tried locking the file in readOnly mode it still gets touched and items are scrambled so only workaround is to autostart a script that changes that file agian... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 William changed: What|Removed |Added CC||wi11ia...@pm.me --- Comment #199 from William --- Betriebssystem: Manjaro Linux KDE-Plasma-Version: 5.24.5 KDE-Frameworks-Version: 5.93.0 Qt-Version: 5.15.3 Kernel-Version: 5.17.6-1-MANJARO (64-bit) Grafik-Plattform: X11 just hit the update on manjaro stable, this bug still occuring , left/right row or column alignment items locked or unlocked, after every logout/login they are scrambled, although it doesnt seem random but rather in same way everytime (for example row alignment causes them to be in a sort of staircase pattern next login that is same everytime) -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 422934] Option to render (and/or otherwise make available) details about the picture of the day (potd) wallpaper
https://bugs.kde.org/show_bug.cgi?id=422934 --- Comment #24 from William Kendrick --- Thanks so much! -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 451344] New: Elisa fails to index the system for audio files even when acceptable folders to look in is put in the app's settings and indexing is allowed in the system settings
https://bugs.kde.org/show_bug.cgi?id=451344 Bug ID: 451344 Summary: Elisa fails to index the system for audio files even when acceptable folders to look in is put in the app's settings and indexing is allowed in the system settings Product: Elisa Version: 20.12.3 Platform: Android OS: Android 11.x Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: wclifton...@gmail.com Target Milestone: --- SUMMARY: Elisa fails to index the system for audio files even when acceptable folders to look in is put in the app's settings and indexing is allowed in the system settings *** 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_cra-sh_reports *** STEPS TO REPRODUCE [ this goes from the start of installation and was achieved on a Samsung Galaxy xCover 5 smartphone running Android 11 build number RP1A.200720.012.G525FXXS5AVB3 ] 1) Install the Elisa APK from the KDE Binary Factory (I downloaded the APK using Mozilla Firefox for Android) 2) Open the Elisa application and open the hamburger menu on the left side of the screen and click on "settings" 3) Scroll down to where it says "Music Folders" and click on "Add New Location" and select the file location of where your music is stored, for me the app displays the following path: content://com.android.externalstorage.documents/tree/primary%3AMusic even if the actual file path selected in the file browser is /storage/emulated/0/Music according to the file browser "Total Commander" 4) Then close out of the settings page and in the hamburger menu, select any of the options that will try to index system files e.g. "Tracks" or "Files". The problem you'll get (or at least the problem I got) is a pink circle doing an infinite loop trying to load something but fails to actually load anything after minuets of loading, this has the same outcome whether the "Use fast native indexer" or the "Scan the filesystem directly" option is selected in the app's settings under the "Music Indexing" option. Another potential variable is that my music folder has individual tracks that were downloaded from Soundcloud and tracks that are a part of albums which are in their own folders which were downloaded from Bandcamp both on a Windows 10 Computer (specifically an Acer Aspire XC-705 SFF Desktop but this info is irrelevant). The file types in the music folder selected are JPGs, MP3s, WMAs, M4As, FLACs, (2) XSPFs (playlist files), (2) S3Ms (tracker/MOD files), plus a folder of a totally legitimate copy of Mike Oldfield's "Ommadawn" album which has the folder types .BUP, .IFO, .VOB plus there is a "hidden" /.thumbnails folder with 2 files one is a file called ".database_uuid" and another file called ".nomedia" Another factor is that I also have VLC Media Player installed which could be an issue if there are conflicting ffmpeg libraries installed on my device but probably not... OBSERVED RESULT No music is loaded and no files are visible EXPECTED RESULT Music & other files are loaded in the app namely the "Tracks", "Artists", "Albums" and "Files" section accessible via the hamburger menu SOFTWARE/OS VERSIONS Windows: n/a macOS: n/a Linux/KDE Plasma: n/a but this phone is running Android 11 with Google Play Services (available in About System) KDE Plasma Version: n/a KDE Frameworks Version: n/a Qt Version: n/a ADDITIONAL INFORMATION This is a Samsung Galaxy xCover 5 smartphone running Android 11 with One UI Version 3.1 on the Vodafone UK mobile network. The phone has at least 2GB of RAM and at least 16GB of internal storage. I'm not sure about the specific application version but it was whatever the latest release of the Arm64 apk file on the KDE Binary Factory (or whatever the site directory is called) on Tuesday 8th March 2022 at some point in the late evening. I don't know the specific app version as the file I downloaded doesn't display an app version, nor is it listed in the app itself BUT the "Settings" app on my phone says under "App info" that the version of Elisa that was installed is "Version 21.07.70" which is not an option that can be selected on the KDE bugs report website (bugs.kde.org) so I don't know if I was supposed to download this version or not and expect it to work... And yes I already knew that it wouldn't be fully featured as the Android version of Elisa is not at all publicised (for good reason it seems!) - William Clifton minds,com/wclifton968 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450201] Desktop Application Launcher opens desktop file in text editor.
https://bugs.kde.org/show_bug.cgi?id=450201 --- Comment #1 from William F. --- Just tested on x11, same behaviour as wayland. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 446497] Breeze GTK theme CSD (window decorations) incorrect under Wayland
https://bugs.kde.org/show_bug.cgi?id=446497 William F. changed: What|Removed |Added CC||haiwilli...@gmail.com --- Comment #5 from William F. --- I can reproduce this on 5.24 Tumbleweed under Wayland with both natively installed apps and flatpaks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450201] New: Desktop Application Launcher opens desktop file in text editor.
https://bugs.kde.org/show_bug.cgi?id=450201 Bug ID: 450201 Summary: Desktop Application Launcher opens desktop file in text editor. Product: plasmashell Version: 5.24.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: haiwilli...@gmail.com CC: notm...@gmail.com Target Milestone: 1.0 Created attachment 146702 --> https://bugs.kde.org/attachment.cgi?id=146702&action=edit bug depiction SUMMARY Not sure If I'm reporting this in the correct place, but when using the application launcher that opens by clicking on the desktop opens the desktop file in the default text editor instead of opening the desired application. STEPS TO REPRODUCE 1. Enable application menu on desktop 2. Open any application OBSERVED RESULT Desktop file opens in default text editor. EXPECTED RESULT Application opens. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed (available in About System) KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Have not tested on x11, bug experienced under wayland. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 449236] Scrollbar do not takes the colors from the profile color scheme anymore when using an Application Theme different from Breeze i.e.(Oxygen, Fusion).
https://bugs.kde.org/show_bug.cgi?id=449236 William Peterson changed: What|Removed |Added CC||william.peterso...@aol.com --- Comment #34 from William Peterson --- Same issue here. Not good to remove functions to fix bugs. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 449156] Media plasmoid content does not update on sidebar.
https://bugs.kde.org/show_bug.cgi?id=449156 --- Comment #2 from William F. --- (In reply to Michail Vourlakos from comment #1) > why this is Latte fault and not a bug of that specific media applet? Because the plasmoid refreshes its content just fine outside of Latte. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 449156] New: Media plasmoid content does not update on sidebar.
https://bugs.kde.org/show_bug.cgi?id=449156 Bug ID: 449156 Summary: Media plasmoid content does not update on sidebar. Product: lattedock Version: 0.10.7 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: haiwilli...@gmail.com Target Milestone: --- SUMMARY I use a very wide panel set up to auto-hide as a sort of sidebar, and on there I have the media player plasmoid. The problem is that the progress bar does not update as the currently playing track plays, though it does recognise if the track is playing or not, and if the previous and next buttons are available. If you pause and play the track, it then updates the status bar, but it remains static once again. This issue can also be replicated with the on-demand sidebar profile. STEPS TO REPRODUCE 1. Make a wide panel. 2. Place the media player plasmoid. 3. See that the progress bar doesn't refresh. OBSERVED RESULT Media player does not update track progress bar. EXPECTED RESULT Media player should update progress bar. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 448228] New: Gradients on Vector layer Issues (video included)
https://bugs.kde.org/show_bug.cgi?id=448228 Bug ID: 448228 Summary: Gradients on Vector layer Issues (video included) Product: krita Version: 5.0.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Layers/Vector Assignee: krita-bugs-n...@kde.org Reporter: williamrma...@gmail.com Target Milestone: --- SUMMARY https://youtu.be/v51IGnlRvZ4 Multi color Gradients not working as expected. The above video shows examples *** 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. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: Windows 10 Pro - OS Build - 19042.1415 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.
[frameworks-kiconthemes] [Bug 446477] Breeze icon being shown despite current icon theme not having Breeze in its fallback chain
https://bugs.kde.org/show_bug.cgi?id=446477 --- Comment #6 from William --- i dont wanna exagerate here but isnt this kinda a big issue? people who use different icon-themes to not want to have apps icons falling back to breeze, apps like Steam bring their own icon and with this bug alive those icons will never be used in any case, beacuse there exists a steam icon in the breeze-icon theme. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447099] Plasma Mobile Sleep timer does not listen for gamepads
https://bugs.kde.org/show_bug.cgi?id=447099 --- Comment #3 from William Ethridge --- Is it possible to tell KDE to not hibernate if specific applications are running? That might be an acceptable workaround for at least my use-case. After all, I think I would only be using a gamepad when I am playing a game. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 447099] New: Plasma Mobile Sleep timer does not listen for gamepads
https://bugs.kde.org/show_bug.cgi?id=447099 Bug ID: 447099 Summary: Plasma Mobile Sleep timer does not listen for gamepads Product: kde Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: gamerminst...@gmail.com Target Milestone: --- SUMMARY I am using a Pinephone, running Manjaro+Plasma Mobile. If I stop using the touch screen and instead start using a gamepad (such as the Razer Kishi), whatever function turns the device to sleep for inactivity does not listen for it. The screen will dim after a few seconds, and the screen will lock within a minute STEPS TO REPRODUCE 1. open up a game like Retroarch 2. Try using gamepad instead of the touch screen 3. Pinephone will fall asleep after 1 minute. OBSERVED RESULT Phone goes to sleep EXPECTED RESULT Device should stay awake so long as it detects gamepad inputs SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro-ARM/KDE Plasma KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 437089] On Wayland, Windows that were closed when maximized will open in the maximized position, but not the maximized state
https://bugs.kde.org/show_bug.cgi?id=437089 Brendan William changed: What|Removed |Added CC||bt.will...@outlook.com --- Comment #18 from Brendan William --- I have trouble believing this is something that needs to be resolved by individual apps. This effects various native Wayland applications, particularly Qt ones. I have experienced this with Dolphin, Konsole, MultiMC 5, Kate, Kalendar, System Settings, Discover, and several others, and also with VS Code running with relevant launch flags to use Ozone platform under Wayland. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 446831] New: header footer on printed output
https://bugs.kde.org/show_bug.cgi?id=446831 Bug ID: 446831 Summary: header footer on printed output Product: Falkon Version: 3.1.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: now...@gmail.com Reporter: wch-t...@house-grp.net Target Milestone: --- SUMMARY *** 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. N/A 2. 3. OBSERVED RESULT N/A EXPECTED RESULT N/A SOFTWARE/OS VERSIONS N/A ADDITIONAL INFORMATION Would like to have capability of including page reference information in header and footer when printing pages 1) URL 2) date/time 3) page data (Page # of ## pages) 4) page title 5) other useful info. Have these items user selectable for each of the 4 corners of the printed page in the header and footer sections. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 446477] wrong app icons
https://bugs.kde.org/show_bug.cgi?id=446477 William changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from William --- (In reply to Nate Graham from comment #3) > Can you test with Frameworks 5.89 once it's released in a week? If that > fixes it, then it's the same issue as Bug 445804. I can test it right now on KDE Neon Unstable Edition with frameworks 5.89.0 and the bahaviour is still exactly the same. breeze icons show up for apps even though the breeze icon theme is nowhere in the inherits chain and the icon exists in hicolor theme. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 446477] wrong app icons
https://bugs.kde.org/show_bug.cgi?id=446477 --- Comment #2 from William --- sry i meant it might be related to this commit: https://github.com/KDE/kiconthemes/commit/de3a1abb1839136322f32f2782f9592280b2bbd3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 446477] wrong app icons
https://bugs.kde.org/show_bug.cgi?id=446477 --- Comment #1 from William --- obviously the icon theme from step 1 is not breeze itself. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 445804] kiconthemes 5.88.0 inconsistent icon changes
https://bugs.kde.org/show_bug.cgi?id=445804 --- Comment #10 from William --- sry didnt mean to cause confusion: i created a new ticket here: https://bugs.kde.org/show_bug.cgi?id=446477 -- You are receiving this mail because: You are watching all bug changes.
