[kscreenlocker] [Bug 455712] Unlock button even with password user
https://bugs.kde.org/show_bug.cgi?id=455712 Mika Norén changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||mika.no...@gmail.com --- Comment #27 from Mika Norén --- (arch) Updated to 5.25.3.1-1 and this is still a problem. It seems random when it happens though. Sometimes it works. Sometimes it gets stuck with the unlock buttons that do nothing when clicked. I suspect it's based on how long it has been locked. This seems to happen more often if I leave the computer locked overnight. I'm downgrading to 5.24 as suggested earlier. I rather have an "unsupported system" than one I cannot unlock at all. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 353722] background lost multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=353722 --- Comment #13 from Mika Norén --- Wanted to add that this is still a problem. There have been no changes whatsoever with the last updates. I tried using wayland, but that is even worse. Operating System: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.5-arch1-1 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445332] New: Crashes when trying to eject media that is occupied.
https://bugs.kde.org/show_bug.cgi?id=445332 Bug ID: 445332 Summary: Crashes when trying to eject media that is occupied. Product: dolphin Version: 21.08.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: mika.no...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin crashes and closes when trying to eject media such as CD's DVD's and other ejectable media that is occupied elsewhere. i.e. when the media is being used in another application, or just happen to be the current working directory in a terminal. STEPS TO REPRODUCE 1. Open dolphin and use the left panel in dolphin to access (mount) some removable media such as a CD ROM. 2. Open a terminal and cd to the directory where the media is mounted. Then cd into any of the subfolder on the media. Let it sit there. 3. Back in dolphin, right-click the media in question in the left panel, and then choose "Eject". OBSERVED RESULT Dolphin crashes and quits. EXPECTED RESULT Expected dolphin to show some form of message that the media is currently occupied by some other process and cannot be ejected. SOFTWARE/OS VERSIONS Distribution: Arch Linux Linux kernel version: 5.14.15-zen1-1-zen, Plasma KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION When the removable media isn't occupied elsewhere, the eject works as intended. It is only when another process keeps the media occupied in some way the crash happens. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 437615] changing URL in addressbar does no longer change view content
https://bugs.kde.org/show_bug.cgi?id=437615 --- Comment #4 from Mika Norén --- (In reply to Mika Norén from comment #3) > Trying to enter pretty much anything into the URL bar has the same issue. > Local or remote. Search terms or addresses. Nothing takes. > Although I *can* open konqueror from a command line with an address/url > appended, like this: > > /urs/bin/konqueror http://www.kde.org Additional information: Version 21.04.1 Libraries: KDE Frameworks 5.82.0 Qt 5.15.2 (built against 5.15.2) The xcb windowing system Distribution: Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 437615] changing URL in addressbar does no longer change view content
https://bugs.kde.org/show_bug.cgi?id=437615 Mika Norén changed: What|Removed |Added CC||mika.no...@gmail.com --- Comment #3 from Mika Norén --- Trying to enter pretty much anything into the URL bar has the same issue. Local or remote. Search terms or addresses. Nothing takes. Although I *can* open konqueror from a command line with an address/url appended, like this: /urs/bin/konqueror http://www.kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416739] Panel disappears from time to time and after a while re-appears
https://bugs.kde.org/show_bug.cgi?id=416739 --- Comment #49 from Mika Norén --- (In reply to Nate Graham from comment #48) > Cool, was that ever submitted as a merge request? I believe it has, but no one has looked at it yet. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427278] Panel & desktop config of secondary monitor lost after ScreenConnectors renumbering
https://bugs.kde.org/show_bug.cgi?id=427278 Mika Norén changed: What|Removed |Added CC||mika.no...@gmail.com --- Comment #4 from Mika Norén --- Seems related: https://bugs.kde.org/show_bug.cgi?id=416739 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416739] Panel disappears from time to time and after a while re-appears
https://bugs.kde.org/show_bug.cgi?id=416739 --- Comment #47 from Mika Norén --- Potential patch perhaps? https://invent.kde.org/genpfault/plasma-workspace/commit/181fc5746e9b4aaf491a90e76e770df866d880ad -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377588] plasma panels not shown after reboot
https://bugs.kde.org/show_bug.cgi?id=377588 Mika Norén changed: What|Removed |Added CC||mika.no...@gmail.com --- Comment #9 from Mika Norén --- This might be related: https://bugs.kde.org/show_bug.cgi?id=416739 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 353722] background lost multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=353722 --- Comment #11 from Mika Norén --- There seem to be a patch available that fixes this. I suspect it's now just a matter of time before we'll see it. Thread about it: https://www.mail-archive.com/kde-bugs-dist@kde.org/msg484655.html The patch in question: https://invent.kde.org/genpfault/plasma-workspace/commit/181fc5746e9b4aaf491a90e76e770df866d880ad -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416739] Panel disappears from time to time and after a while re-appears
https://bugs.kde.org/show_bug.cgi?id=416739 --- Comment #41 from Mika Norén --- (In reply to Alain Knaff from comment #40) > I am experiencing the same problem. > > Debian Version: 10 > Kernel: 4.19.0-10-amd64 > Plasma Version: 5.14.5-1 > > Desktop: Terra > Monitors: 2 Terra 2463W monitors, connected via Display Port > > These are monitors that have 2 inputs each, Display Port and HDMI. On > Mondays and Fridays, I work from home, and connect my work laptop to the > HDMI inputs. The home computer is still connected to the display port > inputs, but the monitors are switched to HDMI input. > > I've got the impression that the problem mostly occurs when the work > computer is connected, and has the screens. > > When that happens, the ~/.config/plasmashellrc gets an extra :0.0 entry for > the screen connector: > > Before: > [ScreenConnectors] > 0=DP-1 > 1=DP-2 > > After: > [ScreenConnectors] > 0=DP-1 > 1=:0.0 > 2=DP-2 > > => i.e. the bogus sneaked right into the middle of the real entries, causing > DP-2 to get renumbered from 1 to 2. > > However, the lastScreen settings in > .config/plasma-org.kde.plasma.desktop-appletsrc would not get updated, i.e. > all panels on DP-2 would still keep lastScreen=1, causing them to disappear > (as plasma tried to display them on the non-existant :0.0 screen) > > > N.B. monitors just going to sleep don't cause the problem by itself (unless > ~/.config/plasmashellrc is already corrupted), it actually needs monitor's > input to be switched to another computer to make .plasmashellrc to become > corrupted. But once plasmashellrc *is* corrupted, then shenanigans happen > whenever monitors go to sleep. > > I've now write-protected the plasmashellrc file, let's see whether this > stops the problem from happening next Friday :-) Write-protecting the file only helps to some degree. The incorrect detection of non-existent displays will still occur and cause displays to jumble around. But as the config remains intact one simply have to perform a "plasmashell --replace" a few times until it's back where it's supposed to be again. Be patient though. Plasmashell will complain about the config file being write-protected, and might even appear as if it has hanged for a few seconds. But it'll come around eventually. Just give it a little time to recover out of the "shock". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416739] Panel disappears from time to time and after a while re-appears
https://bugs.kde.org/show_bug.cgi?id=416739 --- Comment #26 from Mika Norén --- (In reply to Erik Quaeghebeur from comment #22) > (In reply to Mika Norén from comment #21) > > I guess you could reove everything but the ones you know you use. May I > > suggest trying this? > I did. It doesn't help a bit… The same problem is still present, even with > the right entries in this file. I suspected so. Your setup is so messed up with different connections no wonder it doesn't work. Then may I suggest delete/move the plasmashellrc file and start over. Then, once your configuration is done and supposed to be where it is, you take a backup of plasmashellrc file immediately. Once your problem reappears you compare the backup file with the current one with the invalid file. You should then spot what has gone wrong. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421894] since 20.04 update, widgets and background disappear sometimes; reconfiguration required
https://bugs.kde.org/show_bug.cgi?id=421894 Mika Norén changed: What|Removed |Added CC||mika.no...@gmail.com --- Comment #8 from Mika Norén --- Looks like the same problem as everyone else with multimonitor setups have. See: https://bugs.kde.org/show_bug.cgi?id=353722 for details, and see if the suggested workarounds help you. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416739] Panel disappears from time to time and after a while re-appears
https://bugs.kde.org/show_bug.cgi?id=416739 --- Comment #21 from Mika Norén --- (In reply to Erik Quaeghebeur from comment #20) > (In reply to Mika Norén from comment #19) > > In my dual screen setup, a mysterious third output appears in > > .config/plasmashellrc under section [ScreenConnectors] > I looked at my .config/plasmashellrc while my laptop is disconnected from > any external screen and there have > > [ScreenConnectors] > 0=LVDS1 > 2=LVDS-1-unknown > 3=XWAYLAND1 > 4=:0.0 > 5=Screen30 > 6=HDMI1 > > This is on a laptop with 1 LVDS (internal), one VGA, and one DP connection. > I have no idea what all entries except the first mean. Could I remove all > those connections? That's quite a bunch indeed. Lemme make a guess: 0=LVDS1<-- Your LCD panel on the laptop itself 2=LVDS-1-unknown <-- Your LCD panel on the laptop itself seem to have been duble-detected an one point. Maybe remove. 3=XWAYLAND1<-- No idea. Some virtual display from Wayland? 4=:0.0 <-- Usually this one is the mysterious entry that spooks around. I just delete it. It randomises itself from time to time. No idea why though. 5=Screen30 <-- No idea. Another virtual display? 6=HDMI1<-- At some point you had an external display connected to your laptop. It has been registered and saved at position 6. I guess you could reove everything but the ones you know you use. May I suggest trying this? (Save the old setup in case you need to refer to it again) [ScreenConnectors] 0=LVDS1 1=HDMI1 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 421534] New: Plasma Styles "Breeze" and "Breeze Dark" conflicts.
https://bugs.kde.org/show_bug.cgi?id=421534 Bug ID: 421534 Summary: Plasma Styles "Breeze" and "Breeze Dark" conflicts. Product: Breeze Version: 5.18.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mika.no...@gmail.com Target Milestone: --- SUMMARY In "Systems settings" -> "Plasma Style" I try to switch to a theme called "Breeze" (the one that says "Follows colour scheme"). Not "Breeze Dark" or "Breeze Light" which also are listed there. In total 3 Breeze themes. It works so far, and the plasma style follows the current colour scheme. But it only works for the currently running session. If I relog, restart, or relaunch plasmashell the "Plasma Style" changes from "Breeze" to "Breeze Dark" all by itself. STEPS TO REPRODUCE 1. Open "System Settings". Select "Plasma Style" on the lefthand list. Select "Breeze" in the theme list. (Not the light or dark versions. Just "Breeze") 2. Relog, restart, reboot or relaunch plasmashell. 3. Open "System Settings" again. Select "Plasma Style". See as the "Plasma Style" switched itself from "Breeze" to "Breeze Dark" all by itself. OBSERVED RESULT The DE switches the Plasma Style from "Breeze" to "Breeze Dark" all by itself. The colour scheme of widgets, panels and menus goes from the current colour scheme to the Breeze Dark grey colours which clashes visually with the rest. EXPECTED RESULT That the selected "Breeze" theme with "Follows colour scheme" would stay active after relogging/restarting/relaunching plasmashell SOFTWARE/OS VERSIONS Arch Linux. Kernel: 5.6.13-arch1-1 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Uses a Dual screen setup. Two identical displayport monitors attached to a Radeon RX580 GPU card. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416739] Panel disappears from time to time and after a while re-appears
https://bugs.kde.org/show_bug.cgi?id=416739 --- Comment #19 from Mika Norén --- In my dual screen setup, a mysterious third output appears in .config/plasmashellrc under section [ScreenConnectors] What it's supposed to look like in my case: [ScreenConnectors] 0=DisplayPort-0 1=DisplayPort-1 What it looks like when this bug triggers: [ScreenConnectors] 0=DisplayPort-0 1=:0.0 2=DisplayPort-1 Sometimes it also looks like this: [ScreenConnectors] 0=DisplayPort-0 1=DisplayPort-1 2=:0.0 To restore the previous screen configuration, I remove the :0.0 -line from the section mentioned, and restore the order of the remaining valid outputs. I save changes and restarts plasmashell. (killall plasmashell && plasmashell --replace) Once plasmashell restarts, it's back to the intended screen configuration with all panels and widgets back in place again. This might or might not happen at any time when screens are turned on after being off, computer restarts or resuming from sleep. It's random and there seem to be no rime or reason to it. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 353722] background lost multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=353722 --- Comment #10 from Mika Norén --- Distribution: Arch Linux. KDE Frameworks 5.70.0 Qt 5.14.2 (built against 5.14.2) plasmashell 5.18.5 As previously mentioned, I also have to manually edit ~/.config/plasmashellrc, section [ScreenConnectors]. I there simply delete the mysterious :0.0 that pops up from seemingly nowhere. The number it's assigned to may is random. sometimes it's right in between the other displayport screens: 0=DisplayPort-0 1=:0.0 2=DisplayPort-1 Sometimes it appears at the end: 0=DisplayPort-0 1=DisplayPort-1 2=:0.0 Sometimes it doesn't appear at all (As it should be): 0=DisplayPort-0 1=DisplayPort-1 I manually edit the mentioned file and remove the :0.0 and rearrange the numbering order of the other displayports. Then I restart plasmashell and I get back to where it's supposed to be. After the next sleep/hibernation/reboot it might or might not get randomized again. Then I have to rinse and repeat the procedure. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 353722] background lost multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=353722 Mika Norén changed: What|Removed |Added CC||mika.no...@gmail.com --- Comment #8 from Mika Norén --- This is still a problem today. I have the same problems as described. It's not just the background. All containers that resides on any monitor that isn't the primary screen get randomized each boot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Desktop settings for the second monitor lost when monitor is connected
https://bugs.kde.org/show_bug.cgi?id=371717 Mika Norén changed: What|Removed |Added CC||mika.no...@gmail.com --- Comment #6 from Mika Norén --- I've had this problem for a few months now. Can't find out what triggers this. Seemingly random every time the computer boots or wakes up from sleep. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416739] Panel disappears from time to time and after a while re-appears
https://bugs.kde.org/show_bug.cgi?id=416739 Mika Norén changed: What|Removed |Added CC||mika.no...@gmail.com --- Comment #15 from Mika Norén --- I confirm this is still an issue with the latest Arch update as of this date. All my computers that somehow involve more than one screen (laptops, desktop etc.) has this problem. It even happens when only one screen is enabled and the rest remains disabled either through the control center application, or via xrandr/xorg.conf. Seems the plasma environment detects monitors as "new screens" every now and then for no apparent reason. This may or may not happen at cold boot, sleep, powersave or just simply triggered by a dpms event. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 --- Comment #51 from Mika Norén <mika.no...@gmail.com> --- Here's an ugly workaround to use meanwhile: 1: Set up your monitors as you see fit with KDE's monitor settings. Apply the changes. It has to be done with KDE's own tools/settings in order for the configuration to be written. xrandrand other third party tools won't do. 2: Confirm that your setup is in order by the contents of ~/.local/kde/kscreen/* 2: Open a terminal and make the configuration immutable: "sudo chattr +i ~/.local/kde/kscreen/*" (Yes, Attributes must be set/unset by root despite ownership) 3: Relog or reboot to see that it works as intended. Only drawback is that one have to remove the immutable flag in order to rearrange/reconfigure the monitors. To reverse the immutable flag, simply unset it: "sudo chattr -i ~/.local/kde/kscreen/*" -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 --- Comment #52 from Mika Norén <mika.no...@gmail.com> --- Here's an ugly workaround to use meanwhile: 1: Set up your monitors as you see fit with KDE's monitor settings. Apply the changes. It has to be done with KDE's own tools/settings in order for the configuration to be written. xrandrand other third party tools won't do. 2: Confirm that your setup is in order by the contents of ~/.local/share/kscreen/* 2: Open a terminal and make the configuration immutable: "sudo chattr +i ~/.local/share/kscreen/*" (Yes, Attributes must be set/unset by root despite ownership) 3: Relog or reboot to see that it works as intended. Only drawback is that one have to remove the immutable flag in order to rearrange/reconfigure the monitors. To reverse the immutable flag, simply unset it: "sudo chattr -i ~/.local/share/kscreen/*" -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 Mika Norén <mika.no...@gmail.com> changed: What|Removed |Added CC||mika.no...@gmail.com --- Comment #50 from Mika Norén <mika.no...@gmail.com> --- This bug is still lingering around in Plasma 5.6.2 (Frameworks 5.21.0, Qt 5.6.0) Quite annoying that one have to rearrange the monitors each time one log in. KDE won't even honour /etc/X11/xorg.conf.d/10-Monitors.conf, where other environments do. -- You are receiving this mail because: You are watching all bug changes.
