Created attachment 176284 [details]
xorg.log

Hi - a couple questions:

Are you able to login from the black/blank screen by blindly typing your password and pressing Enter? (If so, this sounds like https://bugs.kde.org/show_bug.cgi?id=483163)

Do you have multiple monitors? (This might be https://bugs.kde.org/show_bug.cgi?id=496923)

Thanks!

Only one monitor and I can't log in blindly either. It is only possible to switch to another TTY with shortcut.

Thanks! Updating the title to distinguish from similar bugs with different nuances

If you restart plasmashell by entering `plasmashell --replace` in KRunner, does everything return to normal?

(In reply to Nate Graham from comment #5)
> If you restart plasmashell by entering `plasmashell --replace` in KRunner,
> does everything return to normal?

I cannot run the KRunner, alt + f2 does not work.

*** Bug 497095 has been marked as a duplicate of this bug. ***

*** Bug 497593 has been marked as a duplicate of this bug. ***

I get this problem also during viewing YouTube videos with chrome or videos with VLC

*** Bug 496923 has been marked as a duplicate of this bug. ***

(In reply to Philippe ROUBACH from comment #9)
> I get this problem also during viewing YouTube videos with chrome or videos
> with VLC
I very much doubt that's related to this issue; is sounds like something else.

(In reply to Nate Graham from comment #11)
> (In reply to Philippe ROUBACH from comment #9)
> > I get this problem also during viewing YouTube videos with chrome or videos
> > with VLC
> I very much doubt that's related to this issue; is sounds like something
> else.

Same diagnosis and same cure, I type "plasmashell --replace" in kde menu [1] in "search" field.

[1] I display KDE menu by typing "windows" key.

I get this problem also by just reading websites during 2 hours.

(In reply to Philippe ROUBACH from comment #12)
> Same diagnosis and same cure, I type "plasmashell --replace" in kde menu [1]
> in "search" field.
> 
> [1] I display KDE menu by typing "windows" key.

Your issue is different. You can see in https://bugs.kde.org/show_bug.cgi?id=496926#c6 that the original reporter is not able to get to KRunner. 

Please create a new bug report for the problem you're having. Thanks.

Seeing the same issue as 497095/496923  (marked as dupes of this one). When waking from sleep, my second display is works, but acts as though plasma is not running (no wallpaper, right click and other plasma functions do not work). The primary screen is fine though. 

If I disable the secondary display in desktop settings and then allow it to revert, the secondary display comes back fine until the next time my displays sleep. In my case, the system itself never hibernates, only the displays. 

OS: Fedora 41
KDE : Plasma 6.2.4 (X11)
GPU: AMD RX 6650 XT
Kernel: 6.12.5-200.fc41.x86_64

*** Bug 498176 has been marked as a duplicate of this bug. ***

*** Bug 496923 has been marked as a duplicate of this bug. ***

Due to a mix-up with another bug, I tried switching to another Plasma theme, but that does not solve the problem. 
Perhaps this information can help to rule out some cause.

In my case the problem is not solved by switching to another tty and switching back again.

(In reply to Guido from comment #19)
> In my case the problem is not solved by switching to another tty and
> switching back again.

Also, the bug seems related to the external monitor (I use it as primary monitor)

(In reply to Nate Graham from comment #7)
> *** Bug 497095 has been marked as a duplicate of this bug. ***

In my case switching to text tty and come back to graphical tty doesn't solve the problem.
The only way to solve is disable the fault display using "Display configuration" ant the re-enable it.

If i switch from user1 to user2 then i switch from user2 to user1
there is no problem, desktop of user1 is displayed.

I have had this issue on Wayland for months. I've disabled suspend and it happens regularly just by having the the pc idle and it cuts signal to the monitor.  Most often when I come back to the PC I have to switch TTY for it to receive signal.
I have nvidia and use a LG OLED TV as a monitor.

(In reply to Knut Eirik from comment #23)
> I have had this issue on Wayland for months. I've disabled suspend and it
> happens regularly just by having the the pc idle and it cuts signal to the
> monitor.  Most often when I come back to the PC I have to switch TTY for it
> to receive signal.
> I have nvidia and use a LG OLED TV as a monitor.

Your issue sounds like bug 494262

I have noticed the same problem when the PC starts with the laptop monitor (where everything works fine) but then after connecting the external monitor the monitor screen appears black and I have to restart plasmashell.

I have noticed a change or improvement. Now there is a hidden interface, and I can revive the screen with "killall -9 "kwin_x11" && sleep 3 && /usr/bin/kwin_x11 --replace".

My suspicion, but it is only such a suspicion, is that the problem is due to the slowness of the external monitor wakeup. It may be that plasmashell does not see it. I cannot explain it better.

Don't know which GPU driver everyone is using but when I swapped to an nvidia card the issue went away. Then, this morning, when I put back in my AMD card, it returned.

I'm using amdgpu for my AMD card, an old RX 570, and nvidia-open for my GTX 1650. Used X11 with both.

(In reply to Kalinda from comment #28)
> Don't know which GPU driver everyone is using but when I swapped to an
> nvidia card the issue went away. Then, this morning, when I put back in my
> AMD card, it returned.
> 
> I'm using amdgpu for my AMD card, an old RX 570, and nvidia-open for my GTX
> 1650. Used X11 with both.

Interesting, so it could be a bug of Mesa.

(In reply to Guido from comment #29)
> (In reply to Kalinda from comment #28)

Also, what driver you use with AMD?

The bug persists in Plasma 6.3

I confirm. Problem still there, with X11. wayland, not tested

Confirming, since this affects multiple people over multiple Plasma versions

I can confirm this bug, using two monitors with primary being the external one. The "main" one (it's a laptop) is mostly turned off unless I need it for something. Intel i7 with integrated graphics.

(In reply to whoopsdecade from comment #34)
> I can confirm this bug, using two monitors with primary being the external
> one. The "main" one (it's a laptop) is mostly turned off unless I need it
> for something. Intel i7 with integrated graphics.

Same situation as mine.

Adding the x11-only keyword

Btw, I posted a workaround here: https://discuss.kde.org/t/custom-shortcut-to-restart-plasmashell/30482/13?u=whoopsdecade it's ugly and I assume it won't work for some but it's allowed me to avoid downgrading and having to manually restart plasma on each unlock.

Add /path/to/script/monitor_screen_lock.sh with content:

#!/bin/bash
dbus-monitor --session "type='signal',interface='org.freedesktop.ScreenSaver'" |
while read -r line; do
    case "$line" in
        *"boolean true"*)
            # Screen is locked
            ;;
        *"boolean false"*)
            ## Screen is unlocked
            plasmashell --replace &
            ;;
    esac
done

chmod +x /path/to/script/monitor_screen_lock.sh

Create a systemd user service at ~/.config/systemd/user/screen_lock_monitor.service:

[Unit]
Description=Restart plasmashell on session unlock
After=graphical-session.target

[Service]
ExecStart=/path/to/script/monitor_screen_lock.sh
Restart=always
Environment=DISPLAY=:0
Environment=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus

[Install]
WantedBy=default.target

/run/user/1000/bus needs to match your user ID (id -u).

Reload the systemd user services:

systemctl --user daemon-reload

Enable the service so it starts on login:

systemctl --user enable screen_lock_monitor.service

Start the service immediately:

systemctl --user start screen_lock_monitor.service

I would ask you to raise the priority of this bug. 
Although not technically, in fact it has the same effect as a recurring, reproducible crash. 
Thank you!

With 82% of telemetry-using Plasma users on Wayland, and KWin now split between Wayland and X11, X11 is going into formal maintenance-only mode now, so I'm downgrading the priority of this X11-only bug.

(In reply to Nate Graham from comment #40)
> With 82% of telemetry-using Plasma users on Wayland, and KWin now split
> between Wayland and X11, X11 is going into formal maintenance-only mode now,
> so I'm downgrading the priority of this X11-only bug.

I left X11 because of this bug, not because I prefer Wayland.

(In reply to Philippe ROUBACH from comment #42)
> (In reply to Nate Graham from comment #40)
> > With 82% of telemetry-using Plasma users on Wayland, and KWin now split
> > between Wayland and X11, X11 is going into formal maintenance-only mode now,
> > so I'm downgrading the priority of this X11-only bug.
> 
> I left X11 because of this bug, not because I prefer Wayland.

I agree. There are two things I really need my desktop environment to do. Wake up from sleep and remember my windows positions. Plasma/X11 can't do the first and Wayland can't do the second. Until X11 started getting buggy with sleep/restore, it worked better for me in every regard, but I'm forced to use Wayland because not waking up from sleep is worse than not remembering my window positions.

But forgetting window positions is not good. I have 3 monitors and 9 virtual desktops with 15-20 windows open at a time. It is a real hassle to rearrange them when my computer reboots.

(In reply to Reid Swanson from comment #44)
> (In reply to Philippe ROUBACH from comment #42)
> > (In reply to Nate Graham from comment #40)
> > > With 82% of telemetry-using Plasma users on Wayland, and KWin now split
> > > between Wayland and X11, X11 is going into formal maintenance-only mode now,
> > > so I'm downgrading the priority of this X11-only bug.
> > 
> > I left X11 because of this bug, not because I prefer Wayland.
> 
> I agree. There are two things I really need my desktop environment to do.
> Wake up from sleep and remember my windows positions. Plasma/X11 can't do
> the first and Wayland can't do the second. Until X11 started getting buggy
> with sleep/restore, it worked better for me in every regard, but I'm forced
> to use Wayland because not waking up from sleep is worse than not
> remembering my window positions.
> 
> But forgetting window positions is not good. I have 3 monitors and 9 virtual
> desktops with 15-20 windows open at a time. It is a real hassle to rearrange
> them when my computer reboots.

I associated a shortcut (ctrl+alt+P) with the command systemctl --user restart plasma-plasmashell.service. It is a simple solution and only requires a minimum of hassle when the bug occurs.

(In reply to Guido from comment #45)
> (In reply to Reid Swanson from comment #44)
> > (In reply to Philippe ROUBACH from comment #42)
> > > (In reply to Nate Graham from comment #40)
> > > > With 82% of telemetry-using Plasma users on Wayland, and KWin now split
> > > > between Wayland and X11, X11 is going into formal maintenance-only mode now,
> > > > so I'm downgrading the priority of this X11-only bug.
> > > 
> > > I left X11 because of this bug, not because I prefer Wayland.
> > 
> > I agree. There are two things I really need my desktop environment to do.
> > Wake up from sleep and remember my windows positions. Plasma/X11 can't do
> > the first and Wayland can't do the second. Until X11 started getting buggy
> > with sleep/restore, it worked better for me in every regard, but I'm forced
> > to use Wayland because not waking up from sleep is worse than not
> > remembering my window positions.
> > 
> > But forgetting window positions is not good. I have 3 monitors and 9 virtual
> > desktops with 15-20 windows open at a time. It is a real hassle to rearrange
> > them when my computer reboots.
> 
> I associated a shortcut (ctrl+alt+P) with the command systemctl --user
> restart plasma-plasmashell.service. It is a simple solution and only
> requires a minimum of hassle when the bug occurs.

It also doesn't work for me.

(In reply to Reid Swanson from comment #46)
> It also doesn't work for me.

I had to go back to the old way of restarting plasmashell because the old one started to fail after a plasmashell update.

Command: kquitapp5 plasmashell || killall plasmashell && kstart5 plasmashell &

The frustration people are feeling is valid and real. Thanks for keeping things civil.
We do value peoples' experience with Plasma, and we want that experience to be good. 
With that said, we also need to respect the original reporter, and the developers who will have to read this.

Bug reports are meant to gather information about a bug to help make it actionable. Please keep the discussion in this report focused on this X11 bug. Cluttering it up with unrelated comments will make it harder to fix this, if the developers have to sift through pages of text to find what's relevant.

We are aware that people have use cases which make X11 a better fit for them right now and we respect that. We also know that Wayland is lacking some features X11 has supported, like remembering window positions (this is tracked in Bug 15329). Work is happening on Wayland from their end and ours to make it more robust.

For people wanting to continue troubleshooting workarounds on their machines, I recommend starting a thread on the forums
https://discuss.kde.org

Thank you all for your consideration.

(In reply to whoopsdecade from comment #50)

> They already said they’re not going to fix it (which is why I made the
> comment), so bringing that up is kind of a moot point—but I’ll oblige.

I'd like to clarify this for everyone.
I see no such comment. I see the priority was lowered. If there was no intention to fix this bug, it would be in resolved status, not confirmed.

*** Bug 503684 has been marked as a duplicate of this bug. ***

*** Bug 497436 has been marked as a duplicate of this bug. ***

I understand the focus is on Wayland. It is clearly the way forward and I try to make the switch every few weeks. 

It is disappointing however to see this given low priority as Wayland for me is not usable. I need things that are missing protocol wise that aren't optional - mostly to do with remote screen functionality. I can't log in unattended using Rustdesk because Wayland is missing requisite permissions for screen sharing. 

If it was just minor annoyances with Wayland I'd put up with it. Unfortunately Wayland is notorious for taking literal years to add basic functionality. So it puts me in a position where I need to put up with this bug (an annoyance) or switch to Wayland and break my workflow completely.

If you want users to switch to Wayland, the issues there need to get fixed before you abandon X11 users. I want to switch. But I literally can't.

I tried disabling the compositor to see if that would help work around the issue, but while it allows for at more functionality after resume it is still mostly unusable. For example, the panel displays over the black desktop, though doesn't appear to respond to any actions. I was able to bring up a konsole window with a keystroke and use it, however.

I am encountering this with a NVIDIA card using the nvidia-open driver, so the speculation that this was Mesa-only I think is false. I am hooked up to a TV through HDMI as my only display.

I would like to reiterate the frustration for the priority. While Wayland is at least somewhat usable, it is still missing major features compared to X11:
1. It would allow adjusting of refresh rates with applications. For example, Kodi is able to handle playback of *most* videos with static 60 Hz, but playback of DVDs is choppy due to the framerate at 24 Hz, where on X11 it can switch the display mode to ensure smooth playback.
2. Some of the NVIDIA settings, most notably the power settings, currently require X11.

(In reply to akb825 from comment #55)
> I tried disabling the compositor to see if that would help work around the
> issue, but while it allows for at more functionality after resume it is
> still mostly unusable. For example, the panel displays over the black
> desktop, though doesn't appear to respond to any actions. I was able to
> bring up a konsole window with a keystroke and use it, however.
> 
> I am encountering this with a NVIDIA card using the nvidia-open driver, so
> the speculation that this was Mesa-only I think is false. I am hooked up to
> a TV through HDMI as my only display.
> 
> I would like to reiterate the frustration for the priority. While Wayland is
> at least somewhat usable, it is still missing major features compared to X11:
> 1. It would allow adjusting of refresh rates with applications. For example,
> Kodi is able to handle playback of *most* videos with static 60 Hz, but
> playback of DVDs is choppy due to the framerate at 24 Hz, where on X11 it
> can switch the display mode to ensure smooth playback.
> 2. Some of the NVIDIA settings, most notably the power settings, currently
> require X11.

I suggest you use the user service I posted above (along with the update in another one of my comments for the command in the script) because it doesn't look like they want to fix this as a way to push people to use Wayland. For context, expand my comments they marked as "spam." You may or may not need to update the command in the service to account for your main display number.