[kscreenlocker] [Bug 417282] Set 24h in System Settings, got 12h in lockscreen

2023-04-27 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=417282 --- Comment #13 from Wedge009 --- Hmm, doesn't appear that I can edit recently posted comments. I checked another system (also Plasma 5.25) and the lock screen seems to follow the Formats - System Settings specifications, which (unfortunately, in my

[kscreenlocker] [Bug 417282] Set 24h in System Settings, got 12h in lockscreen

2023-04-27 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=417282 --- Comment #12 from Wedge009 --- I'm only on Plasma 5.25 but my lock screen is currently showing 24-hour time, followed by day, dd mmm . This matches my expectations/preferences. -- You are receiving this mail because: You are watching all bug

[kscreenlocker] [Bug 449857] Lockscreen window does not get focus by default on X11

2022-10-14 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=449857 --- Comment #69 from Wedge009 --- Have a look at the commits linked by Erik on 2022-05-19. I recall manually deleting the 'enabled: visible' line when I was still on Kubuntu 20.04. I'm currently on Kubuntu 22.04 - I assume a fresh installation

[systemsettings] [Bug 454415] System Settings Icon View appears to not honour single- vs double-click setting

2022-05-27 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=454415 --- Comment #7 from Wedge009 --- Toolbar buttons and hyperlinks aren't quite the same as Control Panel icons. At any rate, what's done is done, at least I know the introduction of the inconsistency was intentional and not a bug. 'It's not a bug, it's

[systemsettings] [Bug 454415] System Settings Icon View appears to not honour single- vs double-click setting

2022-05-27 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=454415 --- Comment #5 from Wedge009 --- I understand that the text was changed. It's just that the unfortunate convention in the OS that has desktop monopoly has the convention of being consistent across everything, not just files and directories. Hence why

[systemsettings] [Bug 454415] System Settings Icon View appears to not honour single- vs double-click setting

2022-05-26 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=454415 --- Comment #3 from Wedge009 --- Okay, thanks for confirming that it was intentional. A bit unfortunate, though, for someone like me coming from a Windows background where single- vs double-click is consistent throughout. Something to get used to I

[systemsettings] [Bug 454415] System Settings Icon View appears to not honour single- vs double-click setting

2022-05-25 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=454415 --- Comment #1 from Wedge009 --- I don't know if something has changed in recent Plasma versions but I notice the same has happened with adding widgets to the Panel - used to require a double-click, now it happens with a single-click (double-click adds

[systemsettings] [Bug 454415] New: System Settings Icon View appears to not honour single- vs double-click setting

2022-05-25 Thread Wedge009
OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: iconview Assignee: plasma-b...@kde.org Reporter: wedge...@wedge009.net Target Milestone: --- I apologise if this has already been reported - I've searched

[kscreenlocker] [Bug 449857] Lockscreen window does not get focus by default on X11

2022-03-18 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=449857 --- Comment #55 from Wedge009 --- I can only speak for myself, but it sounds like the same also applies to Maciej and Nathan: I am referring to the issue introduced in Plasma 5.18.7 where keyboard input ceased to show the unlock screen

[kscreenlocker] [Bug 449857] Lockscreen window does not get focus by default on X11

2022-03-17 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=449857 --- Comment #53 from Wedge009 --- (In reply to Fabian Vogt from comment #51) > However, all of this is specific to 5.18.7, while this bug report is > initially about 5.24. I understand that, but if you look at the original bug report for Plasm

[kscreenlocker] [Bug 449857] Lockscreen window sometimes does not get focus by default on X11

2022-03-16 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=449857 --- Comment #50 from Wedge009 --- I apologise if this was already discussed in these bug reports but the fix was applied to master with MR 561: https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/561 Commentary suggests some reason

[kscreenlocker] [Bug 449857] Lockscreen window sometimes does not get focus by default on X11

2022-03-16 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=449857 --- Comment #49 from Wedge009 --- It looks like only the 'enabled: visible' line is relevant here. I reinstated 'visible: opacity > 0' and I still get the desired historical behaviour of keyboard inputs feeding straight into the password input fi

[kscreenlocker] [Bug 449857] Lockscreen window sometimes does not get focus by default on X11

2022-03-16 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=449857 --- Comment #48 from Wedge009 --- Interesting. I confirm that removing those lines also resolves the issue for me, at least what is reported in bug #439604. I am also using Kubuntu 20.04, so am using Plasma 5.18 not 5.24. -- You are receiving

[kscreenlocker] [Bug 433054] Code errors in the lock screen theme (1st party or 3rd-party) can block screen unlocking

2022-03-06 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=433054 --- Comment #76 from Wedge009 --- What you describe seems to be tracked in bug #449857. They are not supporting Plasma 5.18.x any more, with the release of 5.24.x. -- You are receiving this mail because: You are watching all bug changes.

[kscreenlocker] [Bug 450753] Keyboard does not activate password field on locking

2022-02-23 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=450753 Wedge009 changed: What|Removed |Added CC||wedge...@wedge009.net --- Comment #2 from Wedge009

[plasmashell] [Bug 449857] Lock screen password field not focused by default

2022-02-15 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=449857 --- Comment #36 from Wedge009 --- (In reply to Duns from comment #28) > the second alternative: click the password field as well. In that case, Plasma 5.24 is a further regression from Plasma 5.18.8. Nate has declared we should conti

[plasmashell] [Bug 439604] Plasma-5.18.7.1, screen lock: textbox/loginbox not activated by keyboard

2022-02-15 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=439604 --- Comment #16 from Wedge009 --- (In reply to Nate Graham from comment #12) > ...However > since the same issue is still present in Plasma 5.24, let's continue the > conversation in Bug 449857. I also understand the need to focus lim

[kscreenlocker] [Bug 450081] When screen is locked, I must move the mouse before typing the password

2022-02-15 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=450081 --- Comment #4 from Wedge009 --- No worries, and I made a mistake above: I meant Plasma 5.18.7 and 5.18.8, not 5.17 and 5.18. -- You are receiving this mail because: You are watching all bug changes.

[plasmashell] [Bug 449857] Lock screen password field not focused by default

2022-02-15 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=449857 --- Comment #25 from Wedge009 --- What do you mean by regaining 'focus'? Is it just a matter of moving the mouse or are you needing to click the password field as well? -- You are receiving this mail because: You are watching all bug changes.

[plasmashell] [Bug 449857] Lock screen password field not focused by default

2022-02-14 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=449857 Wedge009 changed: What|Removed |Added CC||wedge...@wedge009.net --- Comment #23 from Wedge009

[plasmashell] [Bug 439604] Plasma-5.18.7.1, screen lock: textbox/loginbox not activated by keyboard

2022-02-14 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=439604 --- Comment #11 from Wedge009 --- Yes, it's still an issue (albeit minor) as of Plasma 5.18. I think bug 450081 is a duplicate of this. -- You are receiving this mail because: You are watching all bug changes.

[kscreenlocker] [Bug 450081] When screen is locked, I must move the mouse before typing the password

2022-02-14 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=450081 Wedge009 changed: What|Removed |Added CC||wedge...@wedge009.net --- Comment #2 from Wedge009

[kscreenlocker] [Bug 370676] Greeter shows wallpaper, but no input widgets; cannot unlock screen

2021-09-02 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=370676 --- Comment #23 from Wedge009 --- Perhaps it's worth checking what you have installed for the plasma-workspace and/or libkworkspace5-5 packages. The issue for me was introduced with 5.18.7 and went away with 5.18.7.1. -- You are receiving this mail

[kscreenlocker] [Bug 370676] Greeter shows wallpaper, but no input widgets; cannot unlock screen

2021-09-02 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=370676 --- Comment #22 from Wedge009 --- I meant how to replicate from a clean installation, since neither Nate nor I - and presumably no-one else right now - can replicate the issue still. -- You are receiving this mail because: You are watching all bug

[kscreenlocker] [Bug 370676] Greeter shows wallpaper, but no input widgets; cannot unlock screen

2021-09-02 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=370676 --- Comment #19 from Wedge009 --- I think they need more information than that. Nate indicates it's no longer a problem for him. I confirm it's not an issue with Plasma 5.18.7.1 nor 5.22.4 on (K)Ubuntu. You mentioned KDE Neon before - is it possible

[plasmashell] [Bug 439604] Plasma-5.18.7.1, screen lock: textbox/loginbox not activated by keyboard

2021-08-05 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=439604 --- Comment #8 from Wedge009 --- (In reply to imaginator from comment #5) > You probably have to update to 5.18.7.1. See: > https://bugs.kde.org/show_bug.cgi?id=438498 Thanks: I only just had those packages become available just before no

[plasmashell] [Bug 439604] Plasma-5.18.7.1, screen lock: textbox/loginbox not activated by keyboard

2021-08-05 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=439604 --- Comment #7 from Wedge009 --- I only just had Plasma 5.18.7.1 become available for me. While I have the lock screen restored in the sense that I can input password again, I can confirm the original report that only mouse movement brings up the input

[kscreenlocker] [Bug 370676] Greeter shows wallpaper, but no input widgets; cannot log in

2021-08-05 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=370676 --- Comment #14 from Wedge009 --- Packages for Plasma 5.18.7.1 were just released for me and seems to resolve the issue. I have input widgets on the lock screen again. -- You are receiving this mail because: You are watching all bug changes.

[ktorrent] [Bug 378906] Ktorrent disables automatic screen lock

2021-08-05 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=378906 --- Comment #16 from Wedge009 --- As discussed in the merge request, I'm unable to make any changes in my fork of KTorrent, I think I broke something in GitLab. Someone else will have to make the change. (sigh) -- You are receiving this mail because

[kscreenlocker] [Bug 433054] Code errors in the lock screen theme (1st party or 3rd-party) can block screen unlocking

2021-08-05 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=433054 --- Comment #58 from Wedge009 --- I'm not so sure (I also left a comment there) as that report seems to indicate that mouse activity can still activate the input widgets. In my case, neither keyboard nor mouse activity brings up anything. -- You

[ktorrent] [Bug 378906] Ktorrent disables automatic screen lock

2021-08-05 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=378906 --- Comment #15 from Wedge009 --- Apologies if I've done anything wrong or missed something I'm supposed to do, I haven't really worked with GitLab before... https://invent.kde.org/network/ktorrent/-/merge_requests/45 -- You are receiving this mail

[ktorrent] [Bug 378906] Ktorrent disables automatic screen lock

2021-08-05 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=378906 --- Comment #13 from Wedge009 --- For the sake of clarity, perhaps the description of the option in KTorrent could be updated to refer to screen locking and/or power saving as well as 'sleep'? Clearly I'm not the only one who would assume

[plasmashell] [Bug 417282] Set 24h in System Settings, got 12h in lockscreen

2021-08-05 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=417282 Wedge009 changed: What|Removed |Added CC||wedge...@wedge009.net --- Comment #10 from Wedge009

[ktorrent] [Bug 378906] Ktorrent disables automatic screen lock

2021-08-05 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=378906 Wedge009 changed: What|Removed |Added CC||wedge...@wedge009.net --- Comment #10 from Wedge009

[plasmashell] [Bug 439604] Plasma-5.18.7.1, screen lock: textbox/loginbox not activated by keyboard

2021-08-05 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=439604 Wedge009 changed: What|Removed |Added CC||wedge...@wedge009.net --- Comment #4 from Wedge009

[kscreenlocker] [Bug 433054] Code errors in the lock screen theme (1st party or 3rd-party) can block screen unlocking

2021-08-05 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=433054 --- Comment #56 from Wedge009 --- VLO/VHI appears to refer to priority: Very Low and Very High, I assume. -- You are receiving this mail because: You are watching all bug changes.

[kscreenlocker] [Bug 433054] Code errors in the lock screen theme (1st party or 3rd-party) can block screen unlocking

2021-08-05 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=433054 Wedge009 changed: What|Removed |Added CC||wedge...@wedge009.net --- Comment #55 from Wedge009

[kscreenlocker] [Bug 370676] Greeter shows wallpaper, but no input widgets; cannot log in

2021-08-05 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=370676 Wedge009 changed: What|Removed |Added CC||wedge...@wedge009.net --- Comment #13 from Wedge009

[plasma-systemmonitor] [Bug 440261] System Monitoring (CPU/Memory) is broken on AMD Kabini

2021-08-02 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=440261 --- Comment #14 from Wedge009 --- Great! -- You are receiving this mail because: You are watching all bug changes.

[plasma-systemmonitor] [Bug 440261] System Monitoring (CPU/Memory) is broken on AMD Kabini

2021-07-28 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=440261 --- Comment #10 from Wedge009 --- I did a comparison between tags for 5.22.3 and 5.22.4 and there were only a handful of commits, with the one I quoted being the only meaningful change. I rolled back *only* the ksystemstats package back to 5.22.3

[plasma-systemmonitor] [Bug 440261] System Monitoring (CPU/Memory) is broken on AMD Kabini

2021-07-28 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=440261 --- Comment #8 from Wedge009 --- I found this commit: https://github.com/KDE/ksystemstats/commit/70550a94e1752a8adad577574ab3b051088f5a61 https://invent.kde.org/plasma/ksystemstats/-/merge_requests/8 For bug: https://bugs.kde.org/show_bug.cgi?id

[plasma-systemmonitor] [Bug 440261] System Monitoring (CPU/Memory) is broken on AMD Kabini

2021-07-28 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=440261 --- Comment #7 from Wedge009 --- Plasma 5.22.4 packages just became available for my systems. I honestly wasn't expecting any difference from Plasma 5.22.3, but it seems to be working now...? * kstatsviewer --list reporting info again * ksystemstats

[plasma-systemmonitor] [Bug 440261] System Monitoring (CPU/Memory) is broken on AMD Kabini

2021-07-27 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=440261 --- Comment #5 from Wedge009 --- Do you still have KSysguard installed? Because I didn't and so kstatsviewer -list reported nothing. (Seemed to 'hang' for several seconds before eventually returning to the command prompt.) At least we seem to have

[plasma-systemmonitor] [Bug 440261] System Monitoring (CPU/Memory) is broken on AMD Kabini

2021-07-27 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=440261 --- Comment #3 from Wedge009 --- Interesting. Of course where the widgets work, kstatsviewer --list provides plenty of info. Going back to Plasma 5.22.3 on Kabini I do indeed find ksystemstats is not running. Running it manually simply returns

[plasmashell] [Bug 437114] System Monitor widgets cannot be used to replicate appearance and functionality of the old System Load Viewer widget

2021-07-25 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=437114 --- Comment #10 from Wedge009 --- Reported the aforementioned monitor breakage in https://bugs.kde.org/show_bug.cgi?id=440261. Seems to be hardware-specific, so not relevant to this particular bug report. -- You are receiving this mail because: You

[plasma-systemmonitor] [Bug 440261] New: System Monitoring (CPU/Memory) is broken on AMD Kabini

2021-07-25 Thread Wedge009
: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: wedge...@wedge009.net CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY Since Plasma 5.22.0 onwards

[frameworks-solid] [Bug 338469] Display brightness -indicator doesn't work

2021-07-25 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=338469 Wedge009 changed: What|Removed |Added CC||wedge...@wedge009.net --- Comment #5 from Wedge009

[plasmashell] [Bug 437114] System Monitor widgets cannot be used to replicate appearance and functionality of the old System Load Viewer widget

2021-06-14 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=437114 --- Comment #9 from Wedge009 --- Agreed on swap space request. It could just be my distribution's packaging, but it looks like the system monitors (for both CPU and memory) are non-functional with an upgrade to Plasma 5.22. -- You are receiving

[plasma-systemmonitor] [Bug 437114] Consider Restoring Old System Load Viewer Look and Function

2021-05-15 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=437114 --- Comment #6 from Wedge009 --- So it doesn't get lost, I'll add from my 'duplicate' report that there is no apparent ability to configure the update interval in the new System Monitor, in addition to what Garry specified above, including the Memory

[plasma-systemmonitor] [Bug 437114] Consider Restoring Old System Load Viewer Look and Function

2021-05-14 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=437114 Wedge009 changed: What|Removed |Added CC||wedge...@wedge009.net --- Comment #4 from Wedge009

[plasma-systemmonitor] [Bug 437124] Update System Monitor to Match System Load Viewer Features

2021-05-14 Thread Wedge009
https://bugs.kde.org/show_bug.cgi?id=437124 --- Comment #1 from Wedge009 --- Created attachment 138437 --> https://bugs.kde.org/attachment.cgi?id=138437=edit System Monitor in Plasma 5.21 -- You are receiving this mail because: You are watching all bug changes.

[plasma-systemmonitor] [Bug 437124] New: Update System Monitor to Match System Load Viewer Features

2021-05-14 Thread Wedge009
: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: wedge...@wedge009.net CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment

[kde] [Bug 357911] vlc problem with kde 5.5.3

2016-04-22 Thread Wedge009 via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357911 --- Comment #3 from Wedge009 <wedge...@wedge009.net> --- Not sure what's changed in the Kubuntu release yesterday but the issue seems to have gone away for me. KDE 5.5.4 (haven't yet got 5.5.5 from the backports), Qt 5.5.1. How intrusive

[kde] [Bug 357911] vlc problem with kde 5.5.3

2016-01-21 Thread Wedge009 via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357911 Wedge009 <wedge...@wedge009.net> changed: What|Removed |Added CC||wedge...@wedge0