[neon] [Bug 487627] New: Time inaccurate after long sleep and doesnt re-sync
https://bugs.kde.org/show_bug.cgi?id=487627 Bug ID: 487627 Summary: Time inaccurate after long sleep and doesnt re-sync Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: thomaslukeduf...@hotmail.co.uk CC: carlosdema...@gmail.com, j...@jriddell.org, neon-b...@kde.org Target Milestone: --- SUMMARY Using my laptop (Lenovo 14APH8 Ideapad Pro 5), if I leave the system in sleep mode for a long period (hours, overnight) the clock becomes wildly out of sync and refuses to re-sync automatically. The date can be anywhere from a few hours out of date to over a hundred years into the future, which usually (definitely) causes SSL handshakes to fail until fixed. Usually, I have to toggle "auto-sync time/date" checkbox in the system settings, as the system doesn't seem to do this at all after boot. A useful feature could also be a "sync time now" button in the system settings beside the checkbox for automatically syncing, as that may be more intuitive for less technical users who aren't used to the common troubleshooting method of toggling a checkbox! STEPS TO REPRODUCE 1. Set system to sleep mode for a few hours/overnight 2. Wake system back up OBSERVED RESULT Date is wildly out of sync, with no real pattern to it. Sometimes it can be the correct date but a few hours off, or it can a seemingly random date in the future (year 2187 seems to be favourable if that helps). EXPECTED RESULT The date is in sync with the real date. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.0, kernel 6.5.0-35-generic KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION None yet. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 486934] New: [Feature Request] Cycle processes by initial character when key pressed in process view.
https://bugs.kde.org/show_bug.cgi?id=486934 Bug ID: 486934 Summary: [Feature Request] Cycle processes by initial character when key pressed in process view. Classification: Applications Product: plasma-systemmonitor Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: thomaslukeduf...@hotmail.co.uk CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY A useful feature when looking for a process that I've used in other system monitor apps (ie. the infamous task manager) is that when you press a key (eg. 'S' for steam, 'F' for firefox), the highlighted process cycles through the processes starting with that letter. This is useful for when you *sorta* know the name of the process you're expecting. Also, it's much faster than filtering, which takes at least one click to select the searchbox. It also matches similar functionality in Dolphin, which cycles through files of the same initial character when one is pressed with the window focused. STEPS TO REPRODUCE 1. Open System Monitor 2. Open "Processes" tab 3. Press a letter OBSERVED RESULT No action EXPECTED RESULT Cycles through processes of the given keypress, in sorted order (ie. highest-lowest memory by default) 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.
[frameworks-kiconthemes] [Bug 482648] With Breeze Dark and >100% display scaling, Symbolic icons are not shown.
https://bugs.kde.org/show_bug.cgi?id=482648
--- Comment #4 from Luke Horwell ---
Created attachment 168947
--> https://bugs.kde.org/attachment.cgi?id=168947=edit
Video demo of switching light/dark themes. Display is at 200% scale (Wayland)
It's still happening in the current release versions (on Arch Linux, rolling).
Can reproduce in a new user account too.
KDE Plasma 6.0.4
KDE Frameworks 6.2.0
Qt 6.7.0
Wayland and X11
In addition to dolphin, other apps include:
- Gwenview's Places sidebar (e.g. when icons set to 16x16)
- Open/Save file dialog chooser
I did come across something strange. At first, I thought where the theme is
changed made a difference:
(1) System Settings (Home) → "Breeze Dark"
(2) System Settings → Colors & Themes → Global Theme / Icons → "Breeze Dark"
Turns out if switching themes, the icons may look correct, but hovering over
the program reloads into the wrong (colour) icons. Sometimes it'll be right,
but broken thereafter by restarting the program (like with "Details" view in
Dolphin). Attached is a screen capture of some of the weirdness.
It seems to be the icon theme itself ("Breeze Dark") that has the issue - but
only when display scaling is set above 100% (regardless of screen resolution).
If I get time, I'll see if I can Neon running in a container (distrobox) to
check the current git versions.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kiconthemes] [Bug 482648] With Breeze Dark and >100% display scaling, Symbolic icons are not shown.
https://bugs.kde.org/show_bug.cgi?id=482648 Luke Horwell changed: What|Removed |Added Ever confirmed|0 |1 CC||c...@horwell.me Status|REPORTED|CONFIRMED --- Comment #2 from Luke Horwell --- Can confirm the bug happens on X11 too. I observe that symbolic icons do render correctly at 200% monitor scale in Dolphin's sidebar and home folder list view if the regular "Breeze" icon theme is used (requires re-opening Dolphin). Although it's not a great workaround since using "Breeze" icons under a "Breeze Dark" style would result in dark icons for GTK applications. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 484940] libkcolorpicker-qt6-0 failed to install in updates
https://bugs.kde.org/show_bug.cgi?id=484940 Thomas-Luke Duffin changed: What|Removed |Added CC||thomaslukeduf...@hotmail.co ||.uk --- Comment #11 from Thomas-Luke Duffin --- (In reply to jblake from comment #9) > Have resolved this by removing all klibcolorpicker packages via the terminal: > > cd .. to usr/share/doc > cd .. libkcolorpicker-qt6-0 > > then deleted the 2 documents in the directory: > > sudo rm changelog.Debian.gz copyright > > then > > sudo rrm libkcolorpicker-qt6-0 > > then cd.. to > > usr/lib/x86_64-linux-gnu > > then > > sudo rm libkColorPicker-Qt6.so.0.3.0 > > sudo rm libkColorPicker-Qt.so.0 > > sudo rm libkColorPicker-Qt6.so.0 > > sudo rm libkColorPicker.so.0 > > rebooted, checked for updates, and now all good. Didn't seem to fix it for me -- just returned after my next reboot :/ I had a couple more libkColorPicker entries in the /usr/lib/x86_64-linux-gnu folder compared to you but I deleted those too. I think for now I'll just have to wait for this to get resolved or for another fix to come through -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 469762] Give us a way to configure if the destination opens or not after creating an archive via "Compress to..." option from the context menus
https://bugs.kde.org/show_bug.cgi?id=469762
--- Comment #3 from Luke Horwell ---
With the latest Plasma 6 and Ark/Dolphin 24.02.1, here's what happens when
starting a long-running compression via context menu:
* Dolphin process that started the compression is closed: No dolphin window
opens on completion. [Good]
* Dolphin process that started the compression stays open: That window steals
focus back on completion. [Bad]
* Dolphin process that started the compression navigated to a different folder:
New window opens on completion, stealing focus. [Bad]
Under X11 at least, I haven't checked if this is the same behaviour under
Wayland. I have "Keep a single Dolphin window, opening new folders in tabs"
unchecked in Dolphin's settings if that's related.
For now, until a configuration option is present, I'll rebuild the ark package
locally but revert changes in:
https://invent.kde.org/utilities/ark/-/commit/2c847f76778a797964e189bb17ce774e56005f57
In particular, by removing this line in app/compressfileitemaction.cpp:
KIO::highlightInFileManager({QUrl::fromLocalFile(addToArchiveJob->fileName())});
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 483012] New: Changing line spacing for a Konsole profile causes misalignment until application restart
https://bugs.kde.org/show_bug.cgi?id=483012 Bug ID: 483012 Summary: Changing line spacing for a Konsole profile causes misalignment until application restart Classification: Applications Product: konsole Version: 24.02.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: font Assignee: konsole-de...@kde.org Reporter: c...@horwell.me Target Milestone: --- Created attachment 166812 --> https://bugs.kde.org/attachment.cgi?id=166812=edit Screenshot after changing line spacing to 16px SUMMARY In Konsole 24.02.0, changing the line spacing for a profile causes the terminal to be misaligned (in some cases unreadable) until the application is restarted. This is also problematic if the user switches to a profile using different line spacing settings, unless it is the default profile. STEPS TO REPRODUCE 1. Settings → Create/Edit a profile (use CTRL+ALT+M to show menu bars if hidden) 2. Appearance → Miscellaneous 3. Set the line spacing to 8px. 4. Run an application like "nano" to observe text. OBSERVED RESULT The line spacing is broken, causing unreadable text, depending on the line spacing. This is a regression since Konsole 23.08.5 (Qt 5). EXPECTED RESULT Changing line spacing (via settings or switching profiles) render correctly without needing to restart Konsole. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Tested under X11. Observation for other users -- opening a new Konsole window (24.02.0, Qt 6) did seem smaller to its 23.08.5 (Qt 5) version after upgrading, then I found out line spacing wasn't applying properly and also needs a 1 pixel bump. I had it set to 1px up to now, but 2px makes it familiar again to how it was prior to upgrading (after restarting Konsole, of course!) Appreciate the line spacing option, a nice feature for dyslexa users! -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 481308] screen locker black with cursor on X11
https://bugs.kde.org/show_bug.cgi?id=481308 --- Comment #33 from Luke --- (In reply to Bug Janitor Service from comment #31) > A possibly relevant merge request was started @ > https://invent.kde.org/plasma/powerdevil/-/merge_requests/332 Following the logic of this merge request, I was able to fix the problem on my PC by: - enabling automatic screen turn-off; - setting a long-enough LockGrace period. In my case, LockGrace has to be at least 15 seconds; as soon as it’s set lower, the unintentional screen turn-off happens again. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 481308] screen locker blank-with-cursor [xorg]
https://bugs.kde.org/show_bug.cgi?id=481308 Luke changed: What|Removed |Added CC||luke.la...@protonmail.com --- Comment #18 from Luke --- Exact same issue here, as shown in video attachment. It happens consistently as soon as I enter screen lock. Problem started when upgrading to Qt6. Same PC had Qt5, without any issue. Screen is connected to PC via HDMI, and when returning from a screen lock (blindly typing the password) not only it struggles to reactivate the screen (only mouse pointer is visible on a black screen), but also HDMI audio isn’t functioning properly (it goes on and off untill screen is finally available). Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-21-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Celeron® CPU J3455 @ 1.50GHz Memory: 5.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 500 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482489] New: Error when launching discover from kickoff
https://bugs.kde.org/show_bug.cgi?id=482489 Bug ID: 482489 Summary: Error when launching discover from kickoff Classification: Plasma Product: plasmashell Version: 6.0.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: thomaslukeduf...@hotmail.co.uk CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 SUMMARY Error when trying to uninstall apps, or open Discover app listing in from kickoff : `Unable to create KIO worker. Unknown protocol 'appstream'.` Desktop was upgraded from Plasma 5.27 (worked fine) to 6.0 (broken) STEPS TO REPRODUCE 1. Open kickoff 2. search for an app (eg. 'libresprite') 3. select "install X" OBSERVED RESULT Unable to create KIO worker. Unknown protocol 'appstream'. -- dialog box EXPECTED RESULT Opens app listing in discover SOFTWARE/OS VERSIONS `$ neofetch --off` OS: KDE neon 6.0 x86_64 Host: 83AM Lenovo IdeaPad Pro 5 14APH8 Kernel: 6.5.0-18-generic Uptime: 31 mins Packages: 2376 (dpkg), 23 (flatpak), 7 (snap) Shell: bash 5.1.16 Resolution: 2880x1800 DE: Plasma 6.0.0 WM: kwin WM Theme: Breeze Theme: [Plasma], Breeze-Dark [GTK2], Breeze [GTK3] Icons: breeze-dark [Plasma], breeze-dark [GTK2/3] Terminal: konsole CPU: AMD Ryzen 7 7840HS (16) @ 5.137GHz GPU: AMD ATI 63:00.0 Device 15bf Memory: 3165MiB / 27736MiB ADDITIONAL INFORMATION I trigged the error a few times and copied the result of `journalctl` since boot. https://pastebin.com/2AEwH9sG -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480342] Dropped connections with Mediatek MT7921 chipset - Fixed in upstream linux-firmware repository
https://bugs.kde.org/show_bug.cgi?id=480342 Thomas-Luke Duffin changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #5 from Thomas-Luke Duffin --- Latest firmware updates appear to fix. If not, recommend copying changes from linux-firmware repo as prev. mentioned. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482038] [6.0] shell no longer loading after plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=482038 --- Comment #5 from Thomas-Luke Duffin --- (In reply to Marco Martin from comment #3) > Can you paste here the file > ~/.config/plasma-org.kde.plasma.desktop-appletsrc ? https://pastebin.com/NfWwyBZH Just as a warning that I've basically re-added the default plasma panel by manually adding the panel and widgets. So this may look normal (?) But also as another note that since my device doesnt have Nvidia graphics, I don't think it was the driver update in the other ticket that fixed their particular case. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482038] [6.0] shell no longer loading after plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=482038 --- Comment #2 from Thomas-Luke Duffin --- Okay so I can manually add the application launcher and task panel but the one present by default is gone. Maybe it just deleted the panel? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482038] [6.0] shell no longer loading after plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=482038 --- Comment #1 from Thomas-Luke Duffin --- Apologies, it looks like I should've used journalctl -b All I'm getting is "KPackageStructure of KPluginMetaData(PluginId:"org.kde.plasma.betterinlineclock", filename: "..." doers not match request format "Plasma/applet") " and a few other normal-looking events. Nothing I can see that suggests the shell failed to load but I could be wrong. I'll upload any logs you need if you ask! But since I want to... use my system I might opt to re-install later today :'D -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482038] New: [6.0] shell no longer loading after plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=482038 Bug ID: 482038 Summary: [6.0] shell no longer loading after plasmashell crash Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: thomaslukeduf...@hotmail.co.uk CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Crashed when trying to set desktop background (will make ticket when I can reproduce) and on reboot the shell no longer loads in either x11 or Wayland. STEPS TO REPRODUCE (May not be reproducible) 1. Crash plasmashell (in my case, by double clicking already-selected desktop background) 2. reboot 3. log back in OBSERVED RESULT Logs in, but shell doesn't start. Can see my desktop, and can open GUI apps with the command line. EXPECTED RESULT Shell starts as usual SOFTWARE/OS VERSIONS Linux Kernel: 6.5.0-18-generic (64-bit) KDE Neon: 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION I scrubbed journalctl and found the error (I think): `plasmashell[1349]: Aborting shell load, the activity manager daemon (kactivitymanagerd) is not running` I also recently added an entry for krunner in /usr/share/dbus-1/services because people recommended it to resolve krunner not launching. However, the file no longer exists. Could be related? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482030] New: [6.0]missing touchpad gesture settings
https://bugs.kde.org/show_bug.cgi?id=482030 Bug ID: 482030 Summary: [6.0]missing touchpad gesture settings Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: thomaslukeduf...@hotmail.co.uk CC: natalie_clar...@yahoo.de 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. Open system settings 2. Search "gestures" 3. Check results OBSERVED RESULT Nothing for touchpad gestures can be found EXPECTED RESULT Gestures section under mouse/touchpad or within touchpad settings page I'd love for Gestures to be available within a single page with options for three and 4 finger swipes in each direction. In particular, I was hoping to change the Overview gesture from 4 fingers to 3, just because right now up/down three finger gestures aren't utilized by my system atm. SOFTWARE/OS VERSIONS Linux Kernel: 6.5.0-18-generic (64-bit) KDE Neon: 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION I'm using Wayland exclusively and gestures *do* work, just that there's no way to configure them at all :( PS: Happy 6.0 launch! It looks *beautiful* and honestly I've not had any major breaking issues which is a testament to your testing and bug-hunting <3 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480342] Dropped connections with Mediatek MT7921 chipset - Fixed in upstream linux-firmware repository
https://bugs.kde.org/show_bug.cgi?id=480342 Thomas-Luke Duffin changed: What|Removed |Added Summary|Dropped connections with|Dropped connections with |Mediatek MT7921 chipset - |Mediatek MT7921 chipset - |Fixed in upstream |Fixed in upstream |linux-firmware package |linux-firmware repository -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480342] Dropped connections with Mediatek MT7921 chipset - Fixed in upstream linux-firmware package
https://bugs.kde.org/show_bug.cgi?id=480342 Thomas-Luke Duffin changed: What|Removed |Added Summary|Intermittent dropped|Dropped connections with |network connectivity|Mediatek MT7921 chipset - ||Fixed in upstream ||linux-firmware package -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480342] Intermittent dropped network connectivity
https://bugs.kde.org/show_bug.cgi?id=480342 --- Comment #4 from Thomas-Luke Duffin --- Yup. The new drivers in linux-firmware's git fixed it for me. However, Ubuntu insists on pushing updates which seem to revert my changes to the older firmware and reproducing the issue. For now, I'm just replacing the updates as and when they occur. Either way, I'm not too experienced in how these bugs are handled (Where do I send reports? There's dozens of projects with individual bug trackers that have some influence on this) so advice on how to properly get this fixed for more than just myself would be good. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480342] Intermittent dropped network connectivity
https://bugs.kde.org/show_bug.cgi?id=480342 --- Comment #3 from Thomas-Luke Duffin --- Nope, it's crapping out again. Have followed some discussions on the framework forums as they use the same SoC and WiFi adapter on the Framework, and one suggestions was to copy changes from the linux-firmware git repo: https://community.frame.work/t/responded-slow-wi-fi-on-amd-7040-with-ubuntu-22-04/43375 Will be testing. Once again working "okay" but I can't be sure until it happens again but right now I've gone for about an hour without more than 2 consecutive dropped packets. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480342] Intermittent dropped network connectivity
https://bugs.kde.org/show_bug.cgi?id=480342 --- Comment #2 from Thomas-Luke Duffin --- Investigating further, it looks like an update to the drivers is causing issues. KDE Neon's live USB worked fine, and a fresh install of the distro (wiped everything) seemed to fix the issue... until the first system updates were applied. Searching "kernel 6.5.0 mt 7921e" it appears there's a bunch of issues with this driver. That being said, I saw some suggestions saying to boot down the laptop, unplug it, and hold the power button for ~60s to properly powerdown the components and properly configure the updated drivers. I *think* it's working better now, but might leave this bug up to see if there's a software issue that someone else can identify from my logs. Will update if it poops out again. (also, disabled ipv6 but it had no effect) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480342] Intermittent dropped network connectivity
https://bugs.kde.org/show_bug.cgi?id=480342 --- Comment #1 from Thomas-Luke Duffin --- I've tried a Pop!OS live USB and the network is pretty much perfect. I'm gonna go on a whim and say that there's something going on with the network manager config or some kind of driver mismatch. As such, here's a link from diffchecker that shows the difference between: 1. lsmod for pop!OS (left) and kde neon (right) https://www.diffchecker.com/4conkDJK/ 2. nmcli device show for pop!OS (left) and kde neon (right) https://www.diffchecker.com/lPA4U1KR/ Both links will expire 1 month from now, so you may need me to re-run and re-post if you're visiting later. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480342] New: Intermittent dropped network connectivity
https://bugs.kde.org/show_bug.cgi?id=480342 Bug ID: 480342 Summary: Intermittent dropped network connectivity Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: thomaslukeduf...@hotmail.co.uk CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Created attachment 165220 --> https://bugs.kde.org/attachment.cgi?id=165220=edit result of journalctl -u NetworkManager.service SUMMARY Using KDE Neon 5.27 on my Lenovo IdeaPad Pro 5 14APH8, I'm getting intermittent drops in WIFI connection which didn't previously occur on my previous distro (pop!OS). Usually, websites will fail to load due to DNS failure, and NetworkManager will update its state to "CONNECTED_SITE" within a few minutes (which triggers the plasmoid to show the little ! symbol) and eventually recovers. I can action a recovery faster by manually restarting the system daemon or toggling airplane mode with Fn + F8. I've scoured the available logs in journalctl and nothing seems to happen to "cause" the dropped network connectivity, just that eventually the daemon realizes it's disconnected and eventually sorts itself out. I've tried disabling ipv6, clearing the network keychain password in kwallet, setting the wifi security to "unencrypted" in wifi settings, and disabling power management in NetworkManager. Nothing seems to help unfortunately. As said before, this wasn't an issue with Pop!OS which is also Ubuntu-based, but I know it's significantly modified compared to that of Neon, so I'm hoping asking here might get me somewhere. STEPS TO REPRODUCE 1. Connect to Wifi 2. Wait/browse internet as usual OBSERVED RESULT "Limited Connectivity" notification eventually appears until I toggle airplane mode or restart NetworkManager daemon EXPECTED RESULT Network remains connected SOFTWARE/OS VERSIONS uname -a result: Linux tom-83am 6.5.0-14-generic #14~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Nov 20 18:15:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux ADDITIONAL INFORMATION from lspci: Network controller: MEDIATEK Corp. Device 0616 I believe that's an MT7925 wifi card, if duckduckgo serves me well. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 469762] Give us a way to configure if the destination opens or not after creating an archive via "Compress to..." option from the context menus
https://bugs.kde.org/show_bug.cgi?id=469762 Luke Horwell changed: What|Removed |Added CC||c...@horwell.me --- Comment #2 from Luke Horwell --- This "bug" still bites (23.08.4). Sometimes I use the compress menu to create archives, but don't expect Dolphin to steal focus(!) after the archive finished being created minutes later. The notification is good on its own since it allows to open the containing folder if desired. Having Dolphin honour Ark's "Open destination folder after extraction" will greatly help. Another way to reproduce (on X11) is to compress a large file and switch to another application. - Expected: Only the notification is shown when compression finished. - Observed: Dolphin pops up (even if it was on another virtual desktop) and steals focus of the active app. Hopefully the DELETE key isn't being pressed at the time :) -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 266883] You cannot draw with (semi)transparent color, only fill
https://bugs.kde.org/show_bug.cgi?id=266883 Luke-Jr changed: What|Removed |Added CC||luke-jr+kdeb...@utopios.org --- Comment #6 from Luke-Jr --- Confirmed also in 23.04.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477201] New: Wayland: Right click and dragging does not activate context menu item
https://bugs.kde.org/show_bug.cgi?id=477201 Bug ID: 477201 Summary: Wayland: Right click and dragging does not activate context menu item Classification: Plasma Product: plasmashell Version: 5.27.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: c...@horwell.me CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Activating items from a context menu is possible while holding the right click and releasing it while hovering over the item. Under Wayland, this doesn't happen for the Plasma shell (possibly if it uses Qt 6 Quick), but works in Qt Widgets applications like Dolphin (v24.01.75), GTK 3 applications and under the Plasma X11 session. Areas affected: - On a panel, launchers or applets. - On the desktop or its icons. STEPS TO REPRODUCE 1. Right click (but keep hold) on a panel. 2. Hover over "Enter Edit Mode" then release the right click. OBSERVED RESULT Under Wayland, the item did not hover nor activate. The user must release the right mouse button and left click the item. Under X11, this works as expected. EXPECTED RESULT The menu item highlights and activates upon release of the right click. SOFTWARE/OS VERSIONS OS: Arch Linux KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 476934] New: GNU Screen / tmux integration: scroll buffer
https://bugs.kde.org/show_bug.cgi?id=476934 Bug ID: 476934 Summary: GNU Screen / tmux integration: scroll buffer Classification: Applications Product: konsole Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: history Assignee: konsole-de...@kde.org Reporter: luke-jr+kdeb...@utopios.org Target Milestone: --- It would be nice if Konsole integrated with GNU Screen / tmux such that it loaded the (potentially remote) buffer size into the scrollbar and could function transparently as if it was a normal console. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476808] Symbolic links on desktop cannot open original location under "Desktop folder" setting
https://bugs.kde.org/show_bug.cgi?id=476808 --- Comment #1 from Luke Horwell --- Can confirm the bug happens on Plasma 5.27.80 (Plasma 6 Alpha) too. Plus, the "link" icon at the bottom-right of the icon was missing, but the icon's label was italic. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476808] New: Symbolic links on desktop cannot open original location under "Desktop folder" setting
https://bugs.kde.org/show_bug.cgi?id=476808 Bug ID: 476808 Summary: Symbolic links on desktop cannot open original location under "Desktop folder" setting Classification: Plasma Product: plasmashell Version: 5.27.9 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: c...@horwell.me CC: notm...@gmail.com Target Milestone: 1.0 SUMMARY For symbolic links stored on the desktop, the [>.] button to open the original location (via the Properties window) does not work as expected. The error message reads "The file or folder [path] does not exist" where [path] erroneously prefixes "/home/luke/Desktop" at the start. The symbolic link itself is valid, and the path inside the "Points to" text box is correct. This only happens when configured with the default setting: Configure Desktop and Wallpaper → Location → "Desktop folder" The [>.] button works when this setting is set to "Places panel item" or "Custom location", as well as within Dolphin. Workaround: Set "/home/" as the custom location. STEPS TO REPRODUCE 1. Configure your Desktop Folder Settings to "Desktop folder". 2. Create a symbolic link on desktop (i.e. CTRL+SHIFT+drag a file) 3. Right click the file and open Properties. 4. Click the [>.] button to open the original location. OBSERVED RESULT An error appears stating that the path does not exist. The path in the error message prefixes /home//Desktop. EXPECTED RESULT Dolphin opens to show the original location for the symbolic link. SOFTWARE/OS VERSIONS OS: Arch Linux KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Would love to cross-check with Plasma 6 Alpha, but the unstable Neon ISO and Arch kde-unstable packages result in a black screen under a VirtualBox VM at this time. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476800] KWrite and "minimal overlapping" window placement regressed since 22.08.3
https://bugs.kde.org/show_bug.cgi?id=476800 --- Comment #2 from Luke Horwell --- If it helps, I did a git bisect and found that 353bccf6c5fe0fa284c8cb51def259313e7c9e45 is the commit when the minimal overlapping breaks. https://invent.kde.org/utilities/kate/-/commit/353bccf6c5fe0fa284c8cb51def259313e7c9e45 https://invent.kde.org/utilities/kate/-/network/master?extended_sha1=353bccf6c5fe0fa284c8cb51def259313e7c9e45 Thanks in advance! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476800] KWrite and "minimal overlapping" window placement regressed since 22.08.3
https://bugs.kde.org/show_bug.cgi?id=476800 --- Comment #1 from Luke Horwell --- Created attachment 163019 --> https://bugs.kde.org/attachment.cgi?id=163019=edit Buggy behaviour (kwrite 23.08.2) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 476800] New: KWrite and "minimal overlapping" window placement regressed since 22.08.3
https://bugs.kde.org/show_bug.cgi?id=476800 Bug ID: 476800 Summary: KWrite and "minimal overlapping" window placement regressed since 22.08.3 Classification: Applications Product: kate Version: 23.08.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: c...@horwell.me Target Milestone: --- Created attachment 163018 --> https://bugs.kde.org/attachment.cgi?id=163018=edit Expected behaviour (kate 22.08.3) SUMMARY Around the release of Kate 22.12.0, opening KWrite windows with KDE's minimal overlapping option regressed since 22.08.3. The bug is still present at time of writing (23.08.2). However, the main Kate application open its windows as expected, so it seems specific to KWrite. KDE -> System Settings -> Window Behaviour: - Window placement: "Minimal Overlapping" - Uncheck: "Allow apps to remember the positions of their own windows, if they support it." Workaround: Downgrade kate to 22.08.3, since KWrite is part of Kate. STEPS TO REPRODUCE 1. Start with an empty desktop. 2. Set the KDE setting above (minimal overlapping, don't remember positions) 3. Open multiple KWrite instances. OBSERVED RESULT Newly opened KWrite windows overlaps in a way that is inconsistent with other applications or 22.08.3. EXPECTED RESULT New KWrite instances open without overlapping other windows, similar to 22.08.3 and versions prior. SOFTWARE/OS VERSIONS OS: Arch Linux KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Please observe the attached videos demoing the before/after. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 474920] xdg-open prefers vscode over dolphin
https://bugs.kde.org/show_bug.cgi?id=474920 --- Comment #3 from Thomas-Luke Duffin --- (In reply to Nate Graham from comment #1) > What does `xdg-mime query default inode/directory` run in a terminal window > print out? > > Can you attach your fill /usr/share/applications/mimeinfo.cache file? > > I strongly suspect they're *prepending* their app ID to the inode/directory= > key in that file, rather than *appending* to it, as they should. https://gist.github.com/TDuffinNTU/1685cfd2727b88e3c5ccc9bfdfeb65ee That is exactly what happened when I installed VSCode, as shown from the mimeinfo.cache I've linked above (line 262). The issue resolved itself once I moved the "code.desktop" entry to the end of the list. However, if I revert the change (Which causes the issue to start again) running `xdg-mime query default inode/directory` *still* returns org.Kde.Dolphin :/ There's a lot more discussion that might be helpful as part of the github issue that also might help give some extra context If you check the link I provided in "Additional Details" in the original ticket, the VSCode contributors seem to be unsure what the best practice is. It might be worth replying there to add your input as they were looking for people with domain experience with this. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 474920] New: xdg-open prefers vscode over dolphin
https://bugs.kde.org/show_bug.cgi?id=474920 Bug ID: 474920 Summary: xdg-open prefers vscode over dolphin Classification: Plasma Product: xdg-desktop-portal-kde Version: git-stable-Plasma/5.27 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: thomaslukeduf...@hotmail.co.uk CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- SUMMARY When VSCode is installed, it prepends itself to the `/usr/share/applications/mimeinfo.cache` file of the host/sandbox. On GNOME this seems to be handled fine, but on KDE and some other DE's this appears to cause apps leveraging xdg-open to prefer VSCode over Dolphin. This manifests as either "open folder" buttons failing to launch any app at all (appearing broken) or opening VSCode instead of Dolphin/preferred file picker, which usually breaks application functionality. STEPS TO REPRODUCE 1. Install VSCode on a KDE system. 2. Attempt to open a folder via an app that relies on xdg-portals. (2 examples are gdlauncher and prism launcher if you're in your bi-annual Minecraft phase like I am) OBSERVED RESULT Nothing happens, or VSCode launches. Using `journalctl -f` you can observe failed launches of vscode. Appears that these happen mainly when VSCode is installed as a Snap (And possibly Flatpak but I didn't check) EXPECTED RESULT Dolphin opens. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.2.0-33-generic (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 4600H with Radeon Graphics Memory: 22.8 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 Manufacturer: Acer Product Name: Nitro AN515-44 System Version: V1.04 ADDITIONAL INFORMATION Issue on VSCode's repo: https://github.com/microsoft/vscode/issues/114425 The maintainers seem to believe they're doing what is believed to be standard practice when it comes to setting mimetypes. It could be that KDE and other distros are parsing this file incorrectly (or GNOME is doing it wrong and everyone has just assumed the outliers are wrong). Though I'm speculating on all fronts. As a suggestion, Plasma could do more to suggest which app should be used to attempt to open an xdg-mimetype when multiple apps are available like Android does. Right now, this is something only available in Dolphin via the "Open with..." dialog, but making this a cross-system option would help with UX in these fiddly edge-cases. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 3212] Option to hide backup files as well as dotfiles?
https://bugs.kde.org/show_bug.cgi?id=3212 Luke Horwell changed: What|Removed |Added CC||c...@horwell.me --- Comment #81 from Luke Horwell --- Just wanted to note: To unhide any of the file extensions affected by this change / Dolphin 23.08, use "File Associations" in System Settings to create a new file type for them. To the contrary, removing *.old and *.bak from the "application/x-trash" association still kept them hidden (which makes sense since the file types probably fell back to the system association, which is still "application/x-trash") Might be stating the obvious, but I think this tip might help someone stumbling into this in future. I was one of the users purposefully renaming files to end in *.bak or *.old and naturally would like to keep them visible. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 471403] New: Auto-indentation can delete non-indenting characters
https://bugs.kde.org/show_bug.cgi?id=471403 Bug ID: 471403 Summary: Auto-indentation can delete non-indenting characters Classification: Applications Product: kate Version: 22.12.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: luke-jr+kdeb...@utopios.org Target Milestone: --- SUMMARY File content can be lost for no reason due to this bug. STEPS TO REPRODUCE 1. Make a file with contents "\taaa\n\tbbbccc" 2. Go to the very beginning of the second line (before the tab); backspace to delete the \n and put both lines together 3. Immediately press Enter to restore the \n OBSERVED RESULT File content is now "\taaa\n\tccc" - "bbb" has been lost EXPECTED RESULT File content should go back to being "\taaa\n\tbbbccc" -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 469606] valgrind crashed when compile with c++ stand 17 and boost::lockfree::queue
https://bugs.kde.org/show_bug.cgi?id=469606 Luke changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 469606] valgrind crashed when compile with c++ stand 17 and boost::lockfree::queue
https://bugs.kde.org/show_bug.cgi?id=469606 --- Comment #2 from Luke --- Indeed it's my own problem, after upgrade valgrind to 3.22 everything works. thanks Paul Floyd for your help. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 469606] valgrind crashed when compile with c++ stand 17 and boost::lockfree::queue
https://bugs.kde.org/show_bug.cgi?id=469606 Luke changed: What|Removed |Added Summary|valgrind crashed when |valgrind crashed when |compile with c++ stand 17 |compile with c++ stand 17 ||and boost::lockfree::queue -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 469606] New: valgrind crashed when compile with c++ stand 17
https://bugs.kde.org/show_bug.cgi?id=469606
Bug ID: 469606
Summary: valgrind crashed when compile with c++ stand 17
Classification: Developer tools
Product: valgrind
Version: 3.16.1
Platform: RedHat Enterprise Linux
OS: Unspecified
Status: REPORTED
Severity: crash
Priority: NOR
Component: massif
Assignee: n...@valgrind.org
Reporter: lvwanzhu2...@gmail.com
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. compile project with flag "-std=c++17"
2. run application with valgrind massif tool
OBSERVED RESULT
valgrind/massif crashed with below error:
==16638== Massif, a heap profiler
==16638== Copyright (C) 2003-2017, and GNU GPL'd, by Nicholas Nethercote
==16638== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info
==16638== Command:
/build/os/sys-root/x86_64-pc-linux-gnu/lib64/ld-linux-x86-64.so.2
--library-path /build/os/sys-root/x86_64-pc-linux-gnu/lib64 myapp
==16638==
Starting main...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
==16638==
==16638== Process terminating with default action of signal 6 (SIGABRT):
dumping core
==16638==at 0x5A3A610: raise (raise.c:50)
==16638==by 0x5A24525: abort (abort.c:79)
==16638==by 0x576D80B: ??? (in
/build/os/sys-root/x86_64-pc-linux-gnu/usr/lib64/libstdc++.so.6.0.28)
==16638==by 0x57788F5: ??? (in
/build/os/sys-root/x86_64-pc-linux-gnu/usr/lib64/libstdc++.so.6.0.28)
==16638==by 0x5778960: std::terminate() (in
/build/os/sys-root/x86_64-pc-linux-gnu/usr/lib64/libstdc++.so.6.0.28)
==16638==by 0x5778BF3: __cxa_throw (in
/build/os/sys-root/x86_64-pc-linux-gnu/usr/lib64/libstdc++.so.6.0.28)
==16638==by 0x576D4C7: ??? (in
/build/os/sys-root/x86_64-pc-linux-gnu/usr/lib64/libstdc++.so.6.0.28)
==16638==by 0xD63ECE: allocate (new_allocator.h:112)
==16638==by 0xD63ECE:
freelist_stack*>::node>
> (freelist.hpp:61)
==16638==by 0xD63ECE: boost::lockfree::queue*>::queue(unsigned long) (queue.hpp:217)
code example:
TaskPool::TaskPool()
: tasksQueue_(100)
{
}
mutable boost::lockfree::queue* > tasksQueue_;
EXPECTED RESULT
no crash
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma:
N.el7.x86_64 #2 SMP Mon Nov 30 18:39:13 EET 2020 x86_64 x86_64 x86_64 GNU/Linux
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
If I compile project with flag "-std=c++14", valgrind works correctly.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 442877] Submenus of KStatusNotifierItem open to the wrong side
https://bugs.kde.org/show_bug.cgi?id=442877 Luke Horwell changed: What|Removed |Added CC||c...@horwell.me --- Comment #1 from Luke Horwell --- Created attachment 158279 --> https://bugs.kde.org/attachment.cgi?id=158279=edit Test case: Simple AppIndicator3 in Python Can confirm AppIndicator3 (GTK) and Ayatana Indicator tray icons are affected too. Both in single monitor and multiple monitor setups. Attached is a simple test case to replicate this with a simple Python application. If necessary, replace "AppIndicator3" with "AyatanaAppIndicator3" depending on the Python implementation available for your distro (both APIs are compatible). I was writing this for a new bug report until I found this one, originally suspecting it was a GTK integration bug. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 468691] New: Keyboard shortcut to share clipboard contents
https://bugs.kde.org/show_bug.cgi?id=468691 Bug ID: 468691 Summary: Keyboard shortcut to share clipboard contents Classification: Applications Product: kdeconnect Version: unspecified Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: wishlist Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: lfara...@debian.org CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY Running latest nightly built for macOS (bf3a4b40ec5597ff389a8fbc24bf478282d94ce9). For security, it would be nice to offer a setting to only share clipboard contents (from computer to mobile) when a user-configured keyboard shortcut is pressed. SOFTWARE/OS VERSIONS Windows: macOS: Ventura Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468283] New: DigiKam closes after closing slideshow
https://bugs.kde.org/show_bug.cgi?id=468283 Bug ID: 468283 Summary: DigiKam closes after closing slideshow Classification: Applications Product: digikam Version: 7.10.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Plugin-Generic-SlideShow Assignee: digikam-bugs-n...@kde.org Reporter: kul...@yahoo.com 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. Open DigiKam 2. Select any photo and start the slideshow 3. Close slideshow OBSERVED RESULT After closing the slideshow Digikam stays open for a few seconds and then closes. EXPECTED RESULT I would expect Digikam to stay open. SOFTWARE/OS VERSIONS Windows: 10 Version 2009 (x86_64) macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.102.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434932] Emoji Selector should enter the selected Emojis directly
https://bugs.kde.org/show_bug.cgi?id=434932 Thomas-Luke Duffin changed: What|Removed |Added CC||thomaslukeduf...@hotmail.co ||.uk --- Comment #8 from Thomas-Luke Duffin --- Bumping for support on this. Makes more sense and is how the UX works for other desktop emoji pickers such as on Mac or Windows. Also meets expected UX on mobile interface, where emoji were popularized. The picker in KDE is great (better than windows in terms of aesthetics imo!) but this one weird quirk makes it cumbersome for more than one emoji 梁 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451794] battery percentage hard to read
https://bugs.kde.org/show_bug.cgi?id=451794 --- Comment #7 from Thomas-Luke Duffin --- Created attachment 157656 --> https://bugs.kde.org/attachment.cgi?id=157656=edit Example of low battery icon design And while I'm on a role... how about these for low battery? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451794] battery percentage hard to read
https://bugs.kde.org/show_bug.cgi?id=451794 --- Comment #6 from Thomas-Luke Duffin --- Created attachment 157655 --> https://bugs.kde.org/attachment.cgi?id=157655=edit Example of charging applet icon design Also, since a linked bug mentioned not seeing when charging is available -- how about something like this? Windows prefers to have an animation but this little lightning bolt symbol is commonplace in other designs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451794] battery percentage hard to read
https://bugs.kde.org/show_bug.cgi?id=451794 Thomas-Luke Duffin changed: What|Removed |Added CC||thomaslukeduf...@hotmail.co ||.uk --- Comment #5 from Thomas-Luke Duffin --- I've attached a picture of a comparison between the current % display and my own bodge-job of a battery display. You'll notice that I've kept the battery icon the same total size in both (so that it fits the square dimensional boundary for the icon) but removed the superfluous % (we already know this number represents %!) It's a lot more readable in this comparison, but obviously doesn't meet the same style as other KDE designs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451794] battery percentage hard to read
https://bugs.kde.org/show_bug.cgi?id=451794 Thomas-Luke Duffin changed: What|Removed |Added Platform|Manjaro |unspecified Version|5.24.3 |5.27.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451794] battery percentage hard to read
https://bugs.kde.org/show_bug.cgi?id=451794 --- Comment #4 from Thomas-Luke Duffin --- Created attachment 157654 --> https://bugs.kde.org/attachment.cgi?id=157654=edit Comparison of a draft design vs the current design Obviously a bit of a bodge job but even from a distance you can see it's much easier to read than the current :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467170] New: Ability to define window border colours
https://bugs.kde.org/show_bug.cgi?id=467170 Bug ID: 467170 Summary: Ability to define window border colours Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: luke-jr+kdeb...@utopios.org Target Milestone: --- It would be nice to have a way to define a window border colour for certain windows (ie, via "Window Rules") similar to what Xpra does. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466687] New: Add shortcuts to allow moving of windows between tiling zones within a layout
https://bugs.kde.org/show_bug.cgi?id=466687 Bug ID: 466687 Summary: Add shortcuts to allow moving of windows between tiling zones within a layout Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Custom Tiling Assignee: kwin-bugs-n...@kde.org Reporter: thomaslukeduf...@hotmail.co.uk CC: notm...@gmail.com Target Milestone: --- SUMMARY In Windows using FancyZones, a combination of the Meta+Arrow keys allows a user to cycle the active window between each of the zones within a layout without having to use Shift+Drag. It's a little bonus feature that makes the custom tiling more useful and intuitive with how it integrates with quick snapping behaviors. It also would allow for some super quick layout management using only the keyboard! Simply adding keyboard shortcuts to cycle to the previous/next zone in a layout would work, though I know other solutions guess at the direction you want to move a window to decide which zone to tile it to, but that's a bit much for the scope of this feature imo. PS: I love the new tiling btw. I think it's what has kept me from cracking and moving back to Pop!OS and GNOME :^) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 466684] New: Screen Corners/Touchscreen Gestures - Allow assignment of custom actions/shortcuts
https://bugs.kde.org/show_bug.cgi?id=466684 Bug ID: 466684 Summary: Screen Corners/Touchscreen Gestures - Allow assignment of custom actions/shortcuts Classification: Applications Product: systemsettings Version: 5.27.2 Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: thomaslukeduf...@hotmail.co.uk Target Milestone: --- SUMMARY One of the things that limits the Screen corners settings is the limited options available to the user when choosing the behavior of screen corners. For example, I thought it would be cool to be able to change virtual desktops using the L/R corners. I was disappointed that there's only a predetermined list of actions I can select here, when this is available for other settings. It would add a lot of flexibility and perhaps unexpectedly powerful customization with (what I'd imagine is) relatively little effort. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446541] KWin Inactive Inner Window Actions inappropriately apply to Plasma panels
https://bugs.kde.org/show_bug.cgi?id=446541 Luke-Jr changed: What|Removed |Added CC||luke-jr+kdeb...@utopios.org --- Comment #2 from Luke-Jr --- Seems to be Wayland-specific, as this has worked for a decade under X11. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 465091] New: Closing last Kate doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=465091 Bug ID: 465091 Summary: Closing last Kate doesn't do anything Classification: Applications Product: kate Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: thomaslukeduf...@hotmail.co.uk Target Milestone: --- Created attachment 155834 --> https://bugs.kde.org/attachment.cgi?id=155834=edit VSCode 'no tab' state SUMMARY In web browsers and tabbed text editors such as VSCode, closing the last tab usually closes the whole app. In the case of VSCode, closing the last open tab leaves a handful of helpful keyboard shortcuts in place of where the tab view is normally shown. I've left a screenshot for this particular case. Currently, Kate's tab offers a "Close" button, but trying to click it just makes the tab flicker and remain open. It introduces a minor amount of jank to the end user since a close button should usually allow for some kind of "close" behaviour. Doing nothing in this case feels confusing when using Kate as a new user. There's a few ideal solutions here. As I'm quite new to KDE I'm not sure what meets your HIG best: 1. Close the tab, showing some basic "get started" content where the tabbed content would normally be (like VSCode) 2. Close the whole app (like most modern browsers) 3. Remove the close control on the last tab entirely (feels like this may be an annoying UX choice) 4. Close the tab, and replace it with the welcome/get started tab that cannot be closed. STEPS TO REPRODUCE 1. Open Kate 2. Attempt to close all of the open tabs OBSERVED RESULT Tab flickers a little bit, but ultimately does nothing EXPECTED RESULT Does *something* ADDITIONAL INFORMATION Attached screenshot of VSCode's 'no tab' state for reference. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 464831] "Pick your installation Option" dialog doesn't support touchpad scrolling and overflows the visible window.
https://bugs.kde.org/show_bug.cgi?id=464831 --- Comment #5 from Thomas-Luke Duffin --- Thanks Nate. Still getting the hang of this site -- would've saved you both the trouble if I knew I could've marked it :^) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464884] Give users option to move default Kickoff screen position
https://bugs.kde.org/show_bug.cgi?id=464884 --- Comment #3 from Thomas-Luke Duffin --- Ah that's a shame. I can appreciate why it isn't possible to modify in the settings, but it would make things a lot easier for custom layouts if kickoff could be filtered out via the window behaviours settings from other plasmoids. I was hoping to get a KDE dev environment set up over the weekend (or sometime soon!) to play about with and would be happy to give this a go for kickoff (ie. giving kickoff a unique window name) if it wasn't super technical. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464884] Give users option to move default Kickoff screen position
https://bugs.kde.org/show_bug.cgi?id=464884 --- Comment #1 from Thomas-Luke Duffin --- This would give existing kickoff (and other launchers if given their own window name!) a unique bonus customisation option to mimic Windows 11/other operating systems with non-standard launcher positions. Also helps with theming the dock as the kickoff launcher is designed to play nicely with a floating dock that stretches to the edges of the screen, but floating starts 8px inwards by default. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464884] New: Give users option to move default Kickoff screen position
https://bugs.kde.org/show_bug.cgi?id=464884 Bug ID: 464884 Summary: Give users option to move default Kickoff screen position Classification: Plasma Product: plasmashell Version: 5.26.5 Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: thomaslukeduf...@hotmail.co.uk CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 SUMMARY At the moment, any changes to Kickoff's screen location aren't saved once the menu is closed and re-opened. You can also try using window behaviour rules, but as there is no way to differentiate the kickoff applet with other applets such as the bluetooth, network, notification applets, these plasmoids are also set to the same position on screen when opened. STEPS TO REPRODUCE 1. Move kickoff location with META + Drag click, or by modifying a setting in config menu. 2. Close kickoff 3. Reopen kickoff OBSERVED RESULT Kickoff reverts to old position, and there's no option in config menu to set position exactly. EXPECTED RESULT Closing/reopening kickoff keeps same position as before. There should also be an option to set the position exactly in the config menu. SOFTWARE/OS VERSIONS KDE 5.26.5, KDE NEON. ADDITIONAL INFORMATION A smaller comparative fix perhaps (?) would be to give kickoff a unique window name instead of 'plasma' since this conflicts with other plasmoids when using window behaviours to control the launcher position. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 464831] "Pick your installation Option" dialog doesn't support touchpad scrolling and overflows the visible window.
https://bugs.kde.org/show_bug.cgi?id=464831 --- Comment #3 from Thomas-Luke Duffin --- Good spot. Apologies :) Feel free to close -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 464831] "Pick your installation Option" dialog doesn't support touchpad scrolling and overflows the visible window.
https://bugs.kde.org/show_bug.cgi?id=464831 --- Comment #1 from Thomas-Luke Duffin --- Just noticed too late that EXPECT and OBSERVED sections are switched by mistake just FYI! :^) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 464831] New: "Pick your installation Option" dialog doesn't support touchpad scrolling and overflows the visible window.
https://bugs.kde.org/show_bug.cgi?id=464831 Bug ID: 464831 Summary: "Pick your installation Option" dialog doesn't support touchpad scrolling and overflows the visible window. Classification: Applications Product: Discover Version: 5.26.5 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: thomaslukeduf...@hotmail.co.uk CC: aleix...@kde.org Target Milestone: --- Created attachment 155644 --> https://bugs.kde.org/attachment.cgi?id=155644=edit the dialog overflowing the window. As its a dialog i cannot resize or move to rectify SUMMARY When installing a plasmoid, kwin extension, or other add-on through the settings menu (with the discover app[let?]), sometimes the user is prompted to pick their installation option from a list of provided versions of said add-on. This dialog box that is shown not only overflows the visible window and screen (especially on smaller screens) but it doesn't support scrolling gestures from screens/touchpads. I haven't used this dialog with a mouse so cannot comment on if it responds to a traditional scrollwheel. The scrollbar works fine if clicked and dragged, so scroll events are being reacted to in some respects, but more natural scrolling behaviours aren't respected. I've noticed this on three separate installs of KDE via Manjaro, Neon, and on the Steamdeck via SteamOS. All relatively fresh installs of their respective distributions without many/any 3rd party kwin scripts. This notably doesnt happen if you're using the Discover app directly, as it seems to pick the installation option for you. STEPS TO REPRODUCE NB: I use a flow here to "install additional widgets" but this is present in other examples of the "get new X..." discover applet. 1. Open the kwin scripts settings page and select the "Get New Scripts..." button. 2. Find a listing that has additional install options. I found that "Window Gaps" by Natalie (https://store.kde.org/p/1619642) was a good example with lots of install options. 3. Attempt to resize the dialog, or scroll using touchpad/screen gestures. OBSERVED RESULT Scrolling gestures should work. Dialog should be sized to fit the window/screen boundaries. EXPECTED RESULT Scrolling doesn't occur. Options dialog visibly occluded by window/screen boundaries. SOFTWARE/OS VERSIONS 5.26 KDE NEON ADDITIONAL INFORMATION N/A but contact via email if you need assistance in reproducing! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 325286] snap-to-client vs snap-to-deco should be configurable
https://bugs.kde.org/show_bug.cgi?id=325286 --- Comment #100 from Luke-Jr --- Can't verify right now, but last I checked, it was still an issue at least on X11...? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463057] New: Top panel (a "Windows go below") has a 1px gap above it
https://bugs.kde.org/show_bug.cgi?id=463057 Bug ID: 463057 Summary: Top panel (a "Windows go below") has a 1px gap above it Classification: Plasma Product: plasmashell Version: 5.26.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: luke-jr+kdeb...@utopios.org CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY I have a "Windows go below" panel on the top of my screen with a few applets (pager & clock). I'm used to moving my mouse all the way up to it and clicking the clock to get the calendar shown. But after upgrading to 5.26 (or 5.25? not sure what I was running before my last reboot) there is a 1px space above it, which causes the click to go to whatever window decoration happens to be behind it. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 458621] Option to disable tab functionality
https://bugs.kde.org/show_bug.cgi?id=458621 --- Comment #9 from Luke-Jr --- FWIW, it looks like the last real KWrite (22.04.3) still builds fine with newer KDE at the moment. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 445658] Clipboard sharing from Android to desktop doesn't work (only the other way around)
https://bugs.kde.org/show_bug.cgi?id=445658 Luke-Jr changed: What|Removed |Added CC||luke-jr+kdeb...@utopios.org --- Comment #3 from Luke-Jr --- Same issue here suddenly. No changes to OS or app in months. :/ -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 458621] Option to disable tab functionality
https://bugs.kde.org/show_bug.cgi?id=458621 --- Comment #3 from Luke-Jr --- While we wait for a fix, is there a simple hack I can patch kwrite with to fix this? Also noticed a side effect: Ctrl-W now closes the window rather than leaving it with an empty/new document. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461207] Assigning Window shortcut key cannot include "meta" key (the "Windows" key) or it will be modified to some weird key and fail
https://bugs.kde.org/show_bug.cgi?id=461207 --- Comment #1 from Luke Lee --- Another observation and workaround is that, when the key input dialog appears, the first "Meta" (Windows key) key-down event will be immediate converted into " ៀ?, ...", at this moment keep the "Meta" key pressed and use mouse to click the "clear" button (the button with a cross "X" on it), then this " ៀ?, ..." will be erased then, keep holding the meta key, continuing the remaining key, say, "Z" for "Meta+Z". Now this trick will also work without having to load the workaround xmodmap keys I mentioned in the previous comment. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461207] Assigning Window shortcut key cannot include "meta" key (the "Windows" key) or it will be modified to some weird key and fail
https://bugs.kde.org/show_bug.cgi?id=461207 Luke Lee changed: What|Removed |Added CC||luke.yx@gmail.com Summary|Assigning Window shortcut |Assigning Window shortcut |key cannot include "meta" |key cannot include "meta" |key (the "Windows" key) or |key (the "Windows" key) or |it will be modified to some |it will be modified to some |weird key |weird key and fail -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461207] New: Assigning Window shortcut key cannot include "meta" key (the "Windows" key) or it will be modified to some weird key
https://bugs.kde.org/show_bug.cgi?id=461207 Bug ID: 461207 Summary: Assigning Window shortcut key cannot include "meta" key (the "Windows" key) or it will be modified to some weird key Classification: Plasma Product: kwin Version: 5.24.6 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: luke.yx@gmail.com Target Milestone: --- SUMMARY On Kubuntu 22.04LTS, whenever I assign a window shortcut key including the "Meta" key (the left "Windows" key), for example, "Meta+D" it will be immediately converted to a weird sequence "ៀ?" which is not a valid shortcut key. This *only* happens on Kubuntu 22.04LTS, not on 20.04 or 18.04. STEPS TO REPRODUCE 1. Open any window say an xterm, on Kubuntu 22.04 LTS 2. Right click on the title bar of xterm, move down to "More Actions" -> "Set Window Shortcut" 3. In the dialog box enters whatever key combination containing the "Meta" key (more exactly the left "Windows" key), say, "Meta+D" (Win+D) OBSERVED RESULT After the key combination is typed in the above dialog box, inn the beginning it will correctly show "Meta+D" but 1 second later it will be converted to the text "ៀ?". If we try "Meta+Alt+D" it will become "Alt+ៀ?". After we closed the dialog, that key combination has no effect at all. After examine the xmodmap I found the following 3 keys initially are: keycode 64 = Alt_L Meta_L Alt_L Meta_L keycode 108 = Alt_R Meta_R Alt_R Meta_R keycode 133 = Super_L NoSymbol Super_L I need to change them to the following to fix this issue. keycode 64 = Alt_L Alt_L Alt_L Alt_L keycode 108 = Alt_R Alt_R Alt_R Alt_R keycode 133 = Meta_L Meta_L Meta_L EXPECTED RESULT It supposed to keep what we typed in instead of modifying it into "ៀ?" If I load the modified xmodkey as above, the this won't happen and the key combination works well as before (Kubuntu 20.04LTS). SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 22.04LTS (available in About System) KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427950] "Application Style" settings crash when scrolling style view/list
https://bugs.kde.org/show_bug.cgi?id=427950 Luke-Jr changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Ever confirmed|0 |1 Version|5.19.5 |5.26.1 Status|NEEDSINFO |CONFIRMED --- Comment #4 from Luke-Jr --- Yep, still hasn't been fixed... -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 461071] New: Kleopatra on Tails purged all PGP keys, won't create or import new
https://bugs.kde.org/show_bug.cgi?id=461071 Bug ID: 461071 Summary: Kleopatra on Tails purged all PGP keys, won't create or import new Classification: Applications Product: kleopatra Version: 3.1.11 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: aheine...@gnupg.org Reporter: antipod...@protonmail.com CC: kdepim-b...@kde.org, m...@kde.org Target Milestone: --- Created attachment 153238 --> https://bugs.kde.org/attachment.cgi?id=153238=edit screenshot of key creation failure error message "structure needs cleaning" Hello, I'm not the most technically savvy user but hoping I can get assistance or guidance. I've been using Tails sparingly for a couple years, encrypting messages with OpenPGP and had a small collection of users public keys imported as well as my own private key. A few months ago with an upgrade to Tails I started using Kleopatra which was working well, then a couple weeks ago I went to encrypt a message and found that both my PGP key and all public keys were gone and no longer discoverable. I had not upgraded Tails in between it working and no longer working, so it was seemingly random. I've tried creating a new key and it fails with the message "Could not create key pair: Structure needs cleaning", and attempting to import a user's public key does not succeed. Tails: 5.5 - 20221013 Kleopatra 3.1.11 (20.08.3) Steps to recreate in Kleopatra: 1. File > New Key Pair... 2. Choose Format = Create a personal OpenPGP key pair 3. Added a name, clicked Next 4. Review Parameters, clicked Create 5. Entered password twice 6. Observed Result = Key Creation Failed, "Could not create key pair. Structure needs cleaning" Steps for importing: 1. Copy user's public key, paste in Text Editor, save as .asc file in persistent drive. 2. Go into Kleopatra > Import > navigate to .asc file and select to import 3. Observed Result = Results window pops up, "Total number processed: 0, Imported: 0" I would really appreciate any help figuring out why this is happening. Please let me know if you need more information from me to identify the issue, thank you!! -- 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 --- Comment #4 from Luke-Jr --- (In reply to Hans-Peter Jansen from comment #3) > (In reply to Luke-Jr from comment #2) > > Is this going to get fixed? (Alternatively, is there a maintained fork of > > KWin somewhere out there we can switch to?) > > Be careful with such expressions: kwin is maintained! Not fixing a major regression like this after so long would lead one to think otherwise ;) > It's the X11 part, > that is problematic, and here, it's related to a feature, that doesn't even > exist under wayland, yet! If you want this feature for wayland, please show > your interest here: https://bugs.kde.org/show_bug.cgi?id=377162 My approach for now is to simply not use Wayland. It seems to introduce problems and regressions like this, for no benefit. > FTR: I tried different approaches already to backport to an earlier state of > the shaded window feature, aas well as backing out those changes, in order > to get back to the state of the good ol' times, but the kwin codebase was > shuffled around so heavily, that it would end up into something similar, > what Vlad did already. Duuh. This is what I'm successfully using as of 5.26.1: http://dpaste.com/EHULW6PHM The only thing that seems broken is if I maximise a shaded window, unshade it, then try to unmaximise. But I'm not sure if that ever worked. Shading and replacing kwin does seem to be fine, though. -- 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 Luke-Jr changed: What|Removed |Added CC||vlad.zahorod...@kde.org --- Comment #2 from Luke-Jr --- Is this going to get fixed? (Alternatively, is there a maintained fork of KWin somewhere out there we can switch to?) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441140] Switching virtual deskops causes taskbar to hang Plasma for several seconds
https://bugs.kde.org/show_bug.cgi?id=441140 Luke-Jr changed: What|Removed |Added Version|5.22.4 |5.25.5 --- Comment #2 from Luke-Jr --- A year later and still no improvement... I'm growing used to just not using the taskbar at all, and wondering if maybe I should find a new whatever-plasmashell-is to replace it. -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 452132] Qt/KDE applications not accessible with the Orca screen reader.
https://bugs.kde.org/show_bug.cgi?id=452132 Luke Yelavich changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #11 from Luke Yelavich --- Can confirm the patch works, after updating flatpaks using Qt5 here. Thanks all. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 458621] New: KWrite should not have a tabbed interface
https://bugs.kde.org/show_bug.cgi?id=458621 Bug ID: 458621 Summary: KWrite should not have a tabbed interface Product: kate Version: 22.08.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: luke-jr+kdeb...@utopios.org Target Milestone: --- When I want a tabbed interface, I use Kate. But now KWrite is opening new tabs (when I click "New") instead of new windows. I do not see any way to get the old behaviour back. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 458619] New: Left-side selector changed from vertical text to ugly large icons
https://bugs.kde.org/show_bug.cgi?id=458619 Bug ID: 458619 Summary: Left-side selector changed from vertical text to ugly large icons Product: kate Version: 22.08.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: luke-jr+kdeb...@utopios.org Target Milestone: --- The left side of Kate has always had a list of open documents, which works well. At some point, a selector was added to choose between Documents, Projects, or other plugins. That was fine. But with 22.08, it's become rather large (40x40?) icons instead, which don't indicate what they are (unless you open the tooltip) and waste a lot of screen space. There appears to be no way to turn it off or make it smaller. -- 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 Luke-Jr changed: What|Removed |Added CC||luke-jr+kdeb...@utopios.org -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 457857] New: Kate randomly crawls the filesystem, leading to hanging
https://bugs.kde.org/show_bug.cgi?id=457857
Bug ID: 457857
Summary: Kate randomly crawls the filesystem, leading to
hanging
Product: kate
Version: 22.04.3
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: general
Assignee: kwrite-bugs-n...@kde.org
Reporter: luke-jr+kdeb...@utopios.org
Target Milestone: ---
SUMMARY
For some reason, Kate will often crawl the filesystem, even paths far from the
file being edited. While it does, the GUI hangs for seconds or even a minute or
two.
STEPS TO REPRODUCE
1. Use Kate?
OBSERVED RESULT
Hanging. strace shows lots of filesystem crawling.
EXPECTED RESULT
No hanging. No crawling unrelated files.
SOFTWARE/OS VERSIONS
Linux: 4.19.248
KDE Plasma Version: 5.25.3.1
KDE Frameworks Version: 5.96.0-r1
Qt Version: 5.15.5-r1
ADDITIONAL INFORMATION
(gdb) bt full
#0 syscall () at ../sysdeps/unix/sysv/linux/powerpc/syscall.S:39
No locals.
#1 0x7fff95b1c228 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0,
val=3, op=0, addr=) at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/src/corelib/thread/qfutex_p.h:116
result =
#2 QtLinuxFutex::futexWait >
(expectedValue=0x3, futex=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/src/corelib/thread/qfutex_p.h:135
No locals.
#3 lockInternal_helper (elapsedTimer=0x0, timeout=-1, d_ptr=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/src/corelib/thread/qmutex_linux.cpp:142
nstimeout =
remainingTime =
r =
#4 QBasicMutex::lockInternal (this=0x7fff960faa10 <(anonymous
namespace)::Q_QGS_staticQMimeDatabase::innerFunction()::holder+48>) at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/src/corelib/thread/qmutex_linux.cpp:159
No locals.
#5 0x7fff95b1c354 in QMutex::lock (this=) at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/src/corelib/thread/qmutex.cpp:237
current =
#6 0x7fff95eaa078 in QMutexLocker::QMutexLocker (m=,
this=0x7fffeb427490) at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/include/QtCore/../../src/corelib/thread/qmutex.h:238
No locals.
#7 QMimeDatabasePrivate::mimeInherits (this=0x7fff960fa9e0 <(anonymous
namespace)::Q_QGS_staticQMimeDatabase::innerFunction()::holder>, mime=...,
parent=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/src/corelib/mimetypes/qmimedatabase.cpp:309
locker = {val = 140735710997008}
#8 0x7fff95ead444 in QMimeType::inherits (this=0x13f0c9ea8,
mimeTypeName=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.5-r1/work/qtbase-everywhere-src-5.15.5/src/corelib/mimetypes/qmimetype.cpp:515
No locals.
#9 0x7fff97f07ec0 in KFileItem::isDir (this=0x13f1653b0) at
/var/tmp/portage/kde-frameworks/kio-5.96.0-r2/work/kio-5.96.0/src/core/kfileitem.cpp:1293
No locals.
#10 0x7fff97ff9f20 in KCoreDirLister::matchesFilter (this=0x13f0539d0,
item=...) at
/var/tmp/portage/kde-frameworks/kio-5.96.0-r2/work/kio-5.96.0/src/core/kcoredirlister.cpp:2435
No locals.
#11 0x7fff97ffa380 in KCoreDirListerPrivate::isItemVisible
(this=0x13f053a60, item=...) at
/var/tmp/portage/kde-frameworks/kio-5.96.0-r2/work/kio-5.96.0/src/core/kcoredirlister.cpp:2587
No locals.
#12 0x7fff97ffad4c in operator() (item=..., __closure=)
at
/usr/lib/gcc/powerpc64le-unknown-linux-gnu/11.3.0/include/g++-v11/bits/unique_ptr.h:173
this =
#13 std::copy_if::const_iterator,
std::back_insert_iterator, KCoreDirLister::itemsForDir(const
QUrl&, KCoreDirLister::WhichItems) const::
>(QList::const_iterator, QList::const_iterator,
std::back_insert_iterator, struct {...}) (__first=...,
__last=..., __result=__result@entry=..., __pred=__pred@entry=...) at
/usr/lib/gcc/powerpc64le-unknown-linux-gnu/11.3.0/include/g++-v11/bits/stl_algo.h:700
No locals.
#14 0x7fff97fffeb8 in KCoreDirLister::itemsForDir (this=0x13f0539d0,
dir=..., which=) at
/usr/lib/gcc/powerpc64le-unknown-linux-gnu/11.3.0/include/g++-v11/bits/move.h:49
allItems = 0x13f078dd0
result = {> = {> = {}, {p = {static shared_null = {ref = {atomic = {_q_value =
{> = {static _S_alignment = 4, _M_i = -1}, static
is_always_lock_free = true}}}, alloc = 0, begin = 0, end = 0, array = {0x0}}, d
= 0x7fff88008970}, d = 0x7fff88008970}}, }
#15 0x7fff8f2ffda8 in KFilePreviewGeneratorPrivate::updateCutItems
(this=0x13f08a080) at
/var/tmp/portage/kde-frameworks/kio-5.96.0-r2/work/kio-5.96.0/src/filewidgets/kfilepreviewgenerator.cpp:684
url = @0x13f06ea70: {d = 0x13f079490}
__for_range = @0x7fffeb4276b8: {> = {}, {p = {static shared_null = {ref = {atomic = {_q_value =
{> = {static _S_alignment = 4, _M_i = -1}, static
is_always_lock_free = true}}},
[valgrind] [Bug 452758] Valgrind does not read properly DWARF5 as generated by Clang14
https://bugs.kde.org/show_bug.cgi?id=452758 Luke-Jr changed: What|Removed |Added CC||luke-jr+kdeb...@utopios.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 456782] New: "Save tab layout to file" makes meaningless file
https://bugs.kde.org/show_bug.cgi?id=456782
Bug ID: 456782
Summary: "Save tab layout to file" makes meaningless file
Product: konsole
Version: 22.04.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: konsole-de...@kde.org
Reporter: luke-jr+kdeb...@utopios.org
Target Milestone: ---
STEPS TO REPRODUCE
1. On the menu, View->Save tab layout to file
2. Enter a filename and click OK
OBSERVED RESULT
File contains simply
{
"Orientation": "Horizontal",
"Widgets": [
{
"SessionRestoreId": 0
}
]
}
no matter how many tabs are open.
EXPECTED RESULT
File should contain at least some data that could be useful for restoring them
(without invisible local Konsole state that might be wiped on a clean OS
reinstall)
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 456781] New: "Save tab layout to file" -> "Cancel" => "A problem occurred when saving the Layout."
https://bugs.kde.org/show_bug.cgi?id=456781 Bug ID: 456781 Summary: "Save tab layout to file" -> "Cancel" => "A problem occurred when saving the Layout." Product: konsole Version: 22.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: luke-jr+kdeb...@utopios.org Target Milestone: --- STEPS TO REPRODUCE 1. On the menu, View->Save tab layout to file 2. Cancel the save file dialog OBSERVED RESULT Got error "A problem occurred when saving the Layout." EXPECTED RESULT Silently cancel the operation. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 454412] Bookmarks should have a top-level menu item rather than being hidden in the Go menu
https://bugs.kde.org/show_bug.cgi?id=454412
Luke-Jr changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED|CONFIRMED
--- Comment #10 from Luke-Jr ---
FWIW I'm now building KTextEditor with this (for some reason the main menu ONLY
shows the icon if it's set):
--- a/src/data/katepart5ui.rc
+++ b/src/data/katepart5ui.rc
@@ -115,6 +115,7 @@
+
Tools
--- a/src/utils/katebookmarks.cpp
+++ b/src/utils/katebookmarks.cpp
@@ -74,7 +74,6 @@ void KateBookmarks::createActions(KActionCollection *ac)
KActionMenu *actionMenu = new KActionMenu(i18n(""), this);
actionMenu->setPopupMode(QToolButton::InstantPopup);
-actionMenu->setIcon(QIcon::fromTheme(QStringLiteral("bookmarks")));
ac->addAction(QStringLiteral("bookmarks"), actionMenu);
m_bookmarksMenu = actionMenu->menu();
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-plasma] [Bug 450945] Oxygen desktoptheme: Notifications are dark grey on black
https://bugs.kde.org/show_bug.cgi?id=450945 --- Comment #3 from Luke-Jr --- It's using Plasma::Theme::ViewColorGroup instead of (the correct?) Plasma::Theme::ToolTipColorGroup -- You are receiving this mail because: You are watching all bug changes.
[frameworks-krunner] [Bug 455901] New: Window search: Bring to current virtual desktop option
https://bugs.kde.org/show_bug.cgi?id=455901 Bug ID: 455901 Summary: Window search: Bring to current virtual desktop option Product: frameworks-krunner Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: luke-jr+kdeb...@utopios.org Target Milestone: --- I often use KRunner to find windows and switch to them by name. However, Xpra tends to throw them on the wrong virtual desktop, so I end up using KRunner to find/switch to it, then move the window to the virtual desktop I want it on. It would be nice to pull the window to the current desktop, rather than switching to the one it is on. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 454412] Bookmarks should have a top-level menu item rather than being hidden in the Go menu
https://bugs.kde.org/show_bug.cgi?id=454412 --- Comment #8 from Luke-Jr --- (In reply to Lothar from comment #7) > On top of this file is a version number, try to increase these e.g 98=>110 > (so you have some updates left until it will replaced by a new one) But, how > reliable that is... Good to know. But how do I get Kate to generate the file to start with? :) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 454412] Bookmarks should have a top-level menu item rather than being hidden in the Go menu
https://bugs.kde.org/show_bug.cgi?id=454412 --- Comment #6 from Luke-Jr --- (In reply to Lothar from comment #5) > try to remove ~/.local/share/kxmlgui5/katepart/katepart5ui.rc Thanks, that worked! With that taken care of, only ktexteditor needs to be downgraded it seems. (I wonder if there's a way to generate the katepart5ui.rc with the Bookmarks menu, to get it to stay in the newer version...) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 454412] Bookmarks should have a top-level menu item rather than being hidden in the Go menu
https://bugs.kde.org/show_bug.cgi?id=454412 --- Comment #4 from Luke-Jr --- Any idea what package I need to downgrade to get the menu back? Downgrading `kate` and `ktexteditor` don't seem to do the trick :( -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 454412] Bookmarks should have a top-level menu item rather than being hidden in the Go menu
https://bugs.kde.org/show_bug.cgi?id=454412 --- Comment #2 from Luke-Jr --- (In reply to Lothar from comment #1) > Hm, I have never used Bookmarks because the functionality was fuzzy to me. > Did you know, Alt+PgUp/Down to jump to book marks? You can find these in > ShortCut settings. When you have a dozen or more bookmarks, you don't necessarily remember/care whether they are up or down. Being able to quickly see the entire list and select with the keyboard is crucial. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429453] Bookmarks should have a top-level menu item rather than being hidden in the Go menu
https://bugs.kde.org/show_bug.cgi?id=429453 --- Comment #9 from Luke-Jr --- https://bugs.kde.org/show_bug.cgi?id=454412 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 454412] New: Bookmarks should have a top-level menu item rather than being hidden in the Go menu
https://bugs.kde.org/show_bug.cgi?id=454412 Bug ID: 454412 Summary: Bookmarks should have a top-level menu item rather than being hidden in the Go menu Product: kate Version: 22.04.1 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: luke-jr+kdeb...@utopios.org Target Milestone: --- Prior to 22.04, Kate had a very usable top-level Bookmarks menu, accessible quickly with Alt-B. After upgrading, it's hidden under a "Go" menu, which has terrible usability. Related (Dolphin has the same complaint): https://bugs.kde.org/show_bug.cgi?id=429453 (In the meantime, what do I need to downgrade to get this back?) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429453] Bookmarks should have a top-level menu item rather than being hidden in the Go menu
https://bugs.kde.org/show_bug.cgi?id=429453 Luke-Jr changed: What|Removed |Added CC||luke-jr+kdeb...@utopios.org --- Comment #7 from Luke-Jr --- Ugh, now Kate has copied this regression too. Should I open a separate bug? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 453112] Fixed scroll position jumps around during non-visible output
https://bugs.kde.org/show_bug.cgi?id=453112 --- Comment #6 from Luke-Jr --- (In reply to ninjalj from comment #5) > Git commit d2ca202abd4e6b415a7647927db493337092d5f3 by Luis Javier Merino > Morán. > Committed on 24/05/2022 at 10:51. Confirmed this seems to fix it (backported to 22.04.0) -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 391018] Crash after adding new column in Calligra Sheets
https://bugs.kde.org/show_bug.cgi?id=391018 --- Comment #15 from Luke-Jr --- (In reply to Tomas Mecir from comment #14) > Git commit a43a05877689f7cdb7a3f1b36e05626027869d72 by Tomas Mecir. > Committed on 21/05/2022 at 12:52. > Pushed by mecir into branch 'master'. > > Disable the style cache, it's causing more problems than it's worth. > Related: bug 368852, bug 448587, bug 449729 > > M +41 -41 sheets/core/StyleStorage.cpp > > https://invent.kde.org/office/calligra/commit/ > a43a05877689f7cdb7a3f1b36e05626027869d72 Can confirm this (backported to 3.2.1) seems to have fixed my issue. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 274102] Automatically backup new unnamed/unsaved notes/files
https://bugs.kde.org/show_bug.cgi?id=274102 --- Comment #14 from Luke-Jr --- (In reply to Kishore Gopalakrishnan from comment #13) > Isn't this fixed now as long as one uses sessions? "as long as one uses sessions" isn't this. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 453112] New: Fixed scroll position jumps around during non-visible output
https://bugs.kde.org/show_bug.cgi?id=453112 Bug ID: 453112 Summary: Fixed scroll position jumps around during non-visible output Product: konsole Version: 22.04.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: history Assignee: konsole-de...@kde.org Reporter: luke-jr+kdeb...@utopios.org Target Milestone: --- SUMMARY The scroll position is no longer fixed as it ought to be. STEPS TO REPRODUCE 1. Set a Fixed size buffer (eg, 1000 lines as default) 2. while sleep 1; do date; done 3. Scroll up so new output isn't visible (eg, Shift-Up to go up one line) OBSERVED RESULT Scroll position constantly changes as there's new output beyond the visible area EXPECTED RESULT Scroll position remains fixed and window contents unchanging ADDITIONAL INFORMATION Regression since 21.12.3 (I think) Unlimited buffer doesn't have the problem, it appears -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450520] Ushading is not working in breeze theme with borders
https://bugs.kde.org/show_bug.cgi?id=450520 Luke-Jr changed: What|Removed |Added CC||luke-jr+kdeb...@utopios.org --- Comment #5 from Luke-Jr --- (In reply to cnoss from comment #4) > As seen in duplicate bug 450582: Reverted commit 733469d4e7648 on top of > 71c93ff6a56eb6b in branch Plasma/5.24 - shading and unshading works again. Can also confirm this fixes it on top of 5.24.4 -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 452750] New: adb/scrcpy support
https://bugs.kde.org/show_bug.cgi?id=452750 Bug ID: 452750 Summary: adb/scrcpy support Product: krdc Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: uwol...@kde.org Reporter: luke-jr+kdeb...@utopios.org CC: aa...@kde.org Target Milestone: --- It would be nice if krdc supported connecting to adb servers, possibly using scrcpy for the heavy lifting. -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 452132] Qt/KDE applications not accessible with the Orca screen reader.
https://bugs.kde.org/show_bug.cgi?id=452132
--- Comment #6 from Luke Yelavich ---
The below was run on the host Linux install, which is now Fedora 36.
I set AT_SPI_DBUS_ADDRESS after getting it from a gdbus command and then ran
dolphin:
[themuso@barton ~]$ gdbus call -e -d org.a11y.Bus -o /org/a11y/bus -m
org.a11y.Bus.GetAddress
('unix:path=/run/user/1000/at-spi/bus_0',)
[themuso@barton ~]$ export
AT_SPI_BUS_ADDRESS=unix:path=/run/user/1000/at-spi/bus_0
[themuso@barton ~]$ dolphin
Qt: Session management error: networkIdsList argument is NULL
libpng warning: iCCP: known incorrect sRGB profile
Prior to setting AT_SPI_BUS_ADDRESS, I ran dolphin, and could navigate
files/folders with spoken output from Orca. After setting AT_SPI_BUS_ADDRESS as
above, Orca did not speak anything when navigating files/folders in Dolphin.
Unsetting AT_SPI_BUS_ADDRESS returned the previous behavior, with Orca
providing spoken output.
So to me here, it appears to be something in Qt. Setting AT_SPI_BUS_ADDRESS
seems to not quite be enough for Qt's at-spi backend to function.
--
You are receiving this mail because:
You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 452132] Qt/KDE applications not accessible with the Orca screen reader.
https://bugs.kde.org/show_bug.cgi?id=452132 --- Comment #5 from Luke Yelavich --- (In reply to tingping from comment #4) > Could you test setting `AT_SPI_BUS_ADDRESS` on the host (with latest Qt5 > that has this change) to the host address. > > You can get it with `gdbus call -e -d org.a11y.Bus -o /org/a11y/bus -m > org.a11y.Bus.GetAddress`. > Then export > `AT_SPI_BUS_ADDRESS=unix:path=/run/user/1000/at-spi/bus_1, > guid=37f2237a76e844fd76e4ab94622a3609` for example. > > If this works then Qt is using the env var fine and the problem is the > flatpak proxy permissions. If this fails then the patch using the env var is > likely incorrect. I don't *think* it is anything to do with flatpak, because GTK 4 apps work just fine, and a glance at GTK 4 code shows that AT_SPI_BUS_ADDRESS is used. However, I will humor you, and will check host Qt, and will do a local patched build if need be. -- You are receiving this mail because: You are watching all bug changes.
