[plasmashell] [Bug 483163] On X11 with compositing turned on, blank screen on lock screen when using Breeze Plasma style

2024-06-07 Thread Nicole Schoebel
https://bugs.kde.org/show_bug.cgi?id=483163

--- Comment #33 from Nicole Schoebel  ---
I just made an interesting observation. A couple of days ago I added a second
monitor to my system. Since then the bug had disappeared. I would always see
the lock screen as intended. Today I checked what happens when I remove the
second monitor again.

I unplugged the second monitor from the computer, changed
“/etc/X11/xorg.conf.d/10-monitor.conf” back to what it was before, and
rebooted. The bug was back. I would see a black lock screen with the exception
of a visible mouse cursor. I then plugged the (second) monitor cable back into
the computer, but did NOT connect the other end to the monitor yet. Bug still
there.

I then connected the other end of the cable to the monitor, and - without
having to reboot (!) - the lock screen would then work as intended. The monitor
was connected to power, but in standby at that point. When I turned it
completely on nothing was visible, it wasn’t even getting a signal. “xrandr -q”
was showing the monitor as connected though.

I then unplugged the monitor cable from the computer again. The lock screen
would still work as intended.

So, to sum it up: As long as I connect a second monitor at any time after a
reboot, the lock screen will work as intended until the next reboot. The
monitor does NOT have to stay connected. It just had to be there at some point.

For information: My primary monitor is connected via DisplayPort. The second
one is connected via HDMI.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 483163] blank screen on lock screen activation when using breeze plasma style

2024-04-06 Thread Nicole Schoebel
https://bugs.kde.org/show_bug.cgi?id=483163

--- Comment #25 from Nicole Schoebel  ---
Earlier today I went into "System Settings / Display & Monitor" and DISabled
"Compositing / Enable on startup". I then rebooted. After I logged back into
KDE, I could then activate the lock screen and it would show properly. I tested
this multiple times, and it worked fine every time.

I then re-enabled the compositor, and then the lock screen would show up black
again except for the mouse cursor.

So the bug only seems to appear when the compositor is enabled, which makes me
wonder if the compositor is getting confused about which window should be
displayed on top? If I understand the design of the lock screen correctly (as
described in the sources in kscreenlocker/DESIGN), then a fullscreen (empty -
all black) window is put on top of all other windows, and then the actual lock
screen is put on top of that. If the compositor for some reason would think
that that fullscreen window belongs on top of the lock screen... we would see
exactly this bug. So, could this actually be a compositor bug?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 483163] blank screen on lock screen activation when using breeze plasma style

2024-03-13 Thread Nicole Schoebel
https://bugs.kde.org/show_bug.cgi?id=483163

Nicole Schoebel  changed:

   What|Removed |Added

 CC||schoebel220...@nschoebel.de

--- Comment #7 from Nicole Schoebel  ---
I still see this on 6.0.2. Just installed it on Arch Linux, rebooted and then
tested it.

I have a weird observation to add though. While most times the lock-screen is
not visible (but the mouse cursor is), sometimes I did actually see the
lock-screen. I keep my computer on overnight, but the session is locked and the
monitor is turned off. On most occasions in the morning the lock-screen was
visible. I also had that happen once during the day. It only seems to happen
when a couple of hours have passed. And what may be a factor here (though I'm
not sure) is that a lot of disk activity happened while the session was locked
or just before it was locked. My computer does automatic backup overnight. And
the one time when it worked during the day, I had copied a couple of gigabytes
to a USB disk just before locking the session.

-- 
You are receiving this mail because:
You are watching all bug changes.

[ktorrent] [Bug 455367] Vertical unreadable `% Complete` progress bars

2022-06-30 Thread Nicole Schoebel
https://bugs.kde.org/show_bug.cgi?id=455367

Nicole Schoebel  changed:

   What|Removed |Added

 CC||schoebel220...@nschoebel.de

--- Comment #7 from Nicole Schoebel  ---
I see the same problem with the vertical progress bar in LibreOffice when
saving a big document. For a split second a progress bar appears at the bottom
of the window, and with Breeze it is vertical, but it should be horizontal.

When I change the application style to Fusion the bug disappears both in
KTorrent and LibreOffice. Switch back to Breeze, and the bug appears again.
This is on Arch Linux.

So it looks to me as if the bug is actually in Breeze.

Looking at the recent commits, there is one from a few weeks ago
(https://invent.kde.org/plasma/breeze/-/commit/2bf9fc4c7be280e2b77f7c150855e0fca0b80d9a)
that made changes to the progress bar implementation in Breeze. I'm not
familiar with the KDE codebase, not even familiar with C++, so I'm not sure if
that is actually the cause.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 483163] Sometimes on X11 with compositing turned on, black lock screen when using Breeze Plasma style, but controls are all there and remain interactive

2025-01-04 Thread Nicole Schoebel
https://bugs.kde.org/show_bug.cgi?id=483163

--- Comment #99 from Nicole Schoebel  ---
Count me in as another one for whom 6.2.5 does NOT fix this bug.

I vote to reopen this bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 483163] Sometimes on X11 with compositing turned on, black lock screen when using Breeze Plasma style, but controls are all there and remain interactive

2025-02-23 Thread Nicole Schoebel
https://bugs.kde.org/show_bug.cgi?id=483163

--- Comment #127 from Nicole Schoebel  ---
For me the bug was gone in 6.3.0 and remains fixed in 6.3.1. This is on Arch
Linux.

-- 
You are receiving this mail because:
You are watching all bug changes.