https://bugs.kde.org/show_bug.cgi?id=456723
postix changed:
What|Removed |Added
Resolution|--- |DUPLICATE
CC|
https://bugs.kde.org/show_bug.cgi?id=456723
Nate Graham changed:
What|Removed |Added
Resolution|DUPLICATE |---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #26 from Kalzi ---
That bug*
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #25 from Kalzi ---
(In reply to Nate Graham from comment #24)
>
> *** This bug has been marked as a duplicate of bug 457284 ***
Not sure if this could be considered a duplicate of that big. That one is about
the wallpaper being black.
https://bugs.kde.org/show_bug.cgi?id=456723
Nate Graham changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #23 from Kalzi ---
(In reply to Zamundaaa from comment #22)
> Yes, these PCIe errors definitely seem suspicious. They seem to happen other
> stuff with NVidia as well:
>
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #22 from Zamundaaa ---
Yes, these PCIe errors definitely seem suspicious. They seem to happen other
stuff with NVidia as well:
https://forums.developer.nvidia.com/t/pcie-bus-error-severity-corrected-on-jetson-nano/155780
--
You are
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #21 from Kalzi ---
Created attachment 151113
--> https://bugs.kde.org/attachment.cgi?id=151113=edit
dmesg.log from wayland
This is driving me crazy. Now it stopped happening on wayland and started on
xorg. Here is the log. It didn't
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #20 from Zamundaaa ---
SDDM and the lock screen are two different things. Did you enable auto login,
or change SDDM to use kwin instead of Xorg?
One more thing we can try is that you open konsole, let the command
> sudo dmesg -w >
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #19 from Kalzi ---
(In reply to Kalzi from comment #18)
> (In reply to Zamundaaa from comment #17)
> > No, you'd still get a movable cursor and you'd also get a message about the
> > lockscreen being broken.
> >
> > Instead of using the
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #18 from Kalzi ---
(In reply to Zamundaaa from comment #17)
> No, you'd still get a movable cursor and you'd also get a message about the
> lockscreen being broken.
>
> Instead of using the terminal in weston, you could also just start it
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #17 from Zamundaaa ---
No, you'd still get a movable cursor and you'd also get a message about the
lockscreen being broken.
Instead of using the terminal in weston, you could also just start it from a
tty and initiate suspend like this:
>
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #16 from Kalzi ---
(In reply to Zamundaaa from comment #15)
> The terminal icon on the top left should be clickable. Note that libinput
> defaults to disabling tap to click for some reason; if your touchpad has
> buttons or can be
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #15 from Zamundaaa ---
The terminal icon on the top left should be clickable. Note that libinput
defaults to disabling tap to click for some reason; if your touchpad has
buttons or can be physically pressed down, you need to do that for
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #14 from Kalzi ---
(In reply to Zamundaaa from comment #13)
> You can test quite easily if powertop is at fault by not executing it. Any
> problems caused by it should also happen on Xorg though...
> In the log you attached there is still
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #13 from Zamundaaa ---
You can test quite easily if powertop is at fault by not executing it. Any
problems caused by it should also happen on Xorg though...
In the log you attached there is still no warnings or anything useful.
The next
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #12 from Kalzi ---
Created attachment 150727
--> https://bugs.kde.org/attachment.cgi?id=150727=edit
kwin2.log
There is the log after adding that command to /etc/environment
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #11 from Kalzi ---
(In reply to Zamundaaa from comment #10)
> hmm, that log contains nothing of relevance, probably because debug logging
> is disabled. Can you put
> > QT_LOGGING_RULES="kwin_wayland_*.debug=true"
> into /etc/environment,
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #10 from Zamundaaa ---
hmm, that log contains nothing of relevance, probably because debug logging is
disabled. Can you put
> QT_LOGGING_RULES="kwin_wayland_*.debug=true"
into /etc/environment, reboot and try again?
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #9 from Kalzi ---
Created attachment 150654
--> https://bugs.kde.org/attachment.cgi?id=150654=edit
kwin.log
Alright.
I have reproduced, but this time the screen wasn't black, it was just frozen.
Keyboard and cursor don't do anything.
Got
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #8 from Kalzi ---
BTW, I tried to ssh after I rebooted then closed the lid without logging into
the desktop. So, maybe because there is no internet connection?
I logged in then closed the lid, and I'll see if it happens again then I'll try
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #7 from Kalzi ---
(In reply to Kalzi from comment #6)
> (In reply to Zamundaaa from comment #5)
> > that's quite odd. If you enable ssh, you could also ssh in with a second
> > computer or your phone while the laptop isn't working and save
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #6 from Kalzi ---
(In reply to Zamundaaa from comment #5)
> that's quite odd. If you enable ssh, you could also ssh in with a second
> computer or your phone while the laptop isn't working and save the current
> log with
> > journalctl
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #5 from Zamundaaa ---
that's quite odd. If you enable ssh, you could also ssh in with a second
computer or your phone while the laptop isn't working and save the current log
with
> journalctl --user-unit plasma-kwin_wayland > ~/kwin.log
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #4 from Kalzi ---
(In reply to Zamundaaa from comment #3)
> yes. The "--boot -1" means that it'll fetch the log from the last boot
Ok, so ran the second command
> kwriteconfig5 --file startkderc --group General --key systemdBoot true
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #3 from Zamundaaa ---
yes. The "--boot -1" means that it'll fetch the log from the last boot
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #2 from Kalzi ---
(In reply to Zamundaaa from comment #1)
> After you reproduce the bug, can you run
> > journalctl --boot -1 --user-unit plasma-kwin_wayland
> and upload the output here?
>
> Note that systemd startup is still off by
https://bugs.kde.org/show_bug.cgi?id=456723
--- Comment #1 from Zamundaaa ---
After you reproduce the bug, can you run
> journalctl --boot -1 --user-unit plasma-kwin_wayland
and upload the output here?
Note that systemd startup is still off by default in 5.24; in order to get
logging to work
https://bugs.kde.org/show_bug.cgi?id=456723
Nate Graham changed:
What|Removed |Added
Assignee|unassigned-b...@kde.org |kwin-bugs-n...@kde.org
29 matches
Mail list logo
