[Powerdevil] [Bug 456966] Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 --- Comment #16 from David Url --- Created attachment 153747 --> https://bugs.kde.org/attachment.cgi?id=153747=edit systemctl --user status plasma-powerdevil.service on failed boot The status always looks the same, as the service tries to restart after it receives the timeout. Is there some kind of debug logging I can enable to show whats going on before the service times out? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456966] Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #15 from Nate Graham --- > Nov 08 21:06:18 dT14 systemd[794]: plasma-powerdevil.service: start operation > timed out. Terminating. > Nov 08 21:06:18 dT14 systemd[794]: plasma-powerdevil.service: Failed with > result 'timeout'. David, can you please paste the output of `systemctl status --user plasma-powerdevil.service` after a boot where it's failed? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456966] Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 --- Comment #14 from David Url --- Created attachment 153651 --> https://bugs.kde.org/attachment.cgi?id=153651=edit journalctl -p4 of successful login after boot -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456966] Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 --- Comment #13 from David Url --- Created attachment 153650 --> https://bugs.kde.org/attachment.cgi?id=153650=edit journalctl -p4 of failed login after boot -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456966] Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 --- Comment #12 from David Mak --- Created attachment 153423 --> https://bugs.kde.org/attachment.cgi?id=153423=edit journalctl --user logs from a boot where Powerdevil fails to launch -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456966] Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 David Url changed: What|Removed |Added CC||da...@urld.io --- Comment #11 from David Url --- I experience the same issue on my Lenovo T14 gen3: Kernel: x86_64 Linux 6.0.5-arch1-1 DE: KDE 5.99.0 / Plasma 5.26.2 CPU: AMD Ryzen 7 PRO 6850U While the behaviour seems to be the same, i dont get any hasdualgpu or wayland errors in the logs: ``` Okt 30 23:18:59 dT14 systemd[803]: Starting Powerdevil... Okt 30 23:19:04 dT14 systemd[803]: plasma-powerdevil.service: start operation timed out. Terminating. Okt 30 23:19:04 dT14 systemd[803]: plasma-powerdevil.service: Failed with result 'timeout'. Okt 30 23:19:04 dT14 systemd[803]: Failed to start Powerdevil. Okt 30 23:19:04 dT14 systemd[803]: plasma-powerdevil.service: Scheduled restart job, restart counter is at 1. Okt 30 23:19:04 dT14 systemd[803]: Stopped Powerdevil. Okt 30 23:19:04 dT14 systemd[803]: Starting Powerdevil... Okt 30 23:19:09 dT14 systemd[803]: plasma-powerdevil.service: start operation timed out. Terminating. Okt 30 23:19:09 dT14 systemd[803]: plasma-powerdevil.service: Failed with result 'timeout'. Okt 30 23:19:09 dT14 systemd[803]: Failed to start Powerdevil. ``` It looks a bit like a race condition between some services to me. While i can open a shell and run some commands, everything is incredibly slow, and most systemctl commands never return. Also shutdown or reboot just hang endlessly. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456966] Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 David Mak changed: What|Removed |Added Resolution|WORKSFORME |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456966] Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 --- Comment #10 from David Mak --- I can attach a few more logs tomorrow when I get back to my laptop, since this issue has persisted for me. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456966] Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 --- Comment #8 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456966] Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 djagoo changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME --- Comment #9 from djagoo --- It didn't happen again since I reported that I am affected too. Seems like an update which was done around this time fixed it for me. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456966] Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #7 from Nate Graham --- I see a lot of "The Wayland connection broke. Did the Wayland compositor die?" Are you seeing other crashes on boot? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456966] Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 djagoo changed: What|Removed |Added CC||d...@djagoo.io --- Comment #6 from djagoo --- Same problem here with AMD Ryzen 6850 (Thinkpad Z13). Every second boot/login the screen turn black and login hangs because of plasma-powerdevil hanging. Log shows the same message: org.kde.powerdevil: org.kde.powerdevil.discretegpuhelper.hasdualgpu failed -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456966] Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 --- Comment #5 from David Mak --- Created attachment 150801 --> https://bugs.kde.org/attachment.cgi?id=150801=edit Powerdevil Logs from Journalctl, last 10 boots. (In reply to Nicolas Fella from comment #3) > Can you run "systemctl --user status plasma-powerdevil.service" when it > failed and show the output? Since I am not able to reproduce it every time, here is the `journactl --user -u plasma-powerdevil` for the last 10 boots. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456966] Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 --- Comment #4 from David Mak --- (In reply to Nate Graham from comment #1) > Seems quite relevant: > > > Jul 21 10:14:08 david-laptop org_kde_powerdevil[1135]: org.kde.powerdevil: > > org.kde.powerdevil.discretegpuhelper.hasdualgpu failed > > Is this a dual-GPU system? It's not. It's an APU (Ryzen 7 PRO 6850U with Radeon 680M) with no discrete GPU. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456966] Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 --- Comment #3 from Nicolas Fella --- Can you run "systemctl --user status plasma-powerdevil.service" when it failed and show the output? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456966] Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #2 from Nicolas Fella --- (In reply to Nate Graham from comment #1) > Seems quite relevant: > > > Jul 21 10:14:08 david-laptop org_kde_powerdevil[1135]: org.kde.powerdevil: > > org.kde.powerdevil.discretegpuhelper.hasdualgpu failed > > Is this a dual-GPU system? It might not be relevant. All the discretegpuhelper does is test whether a specific file exists -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 456966] Failed to start Powerdevil on AMD Rembrandt
https://bugs.kde.org/show_bug.cgi?id=456966 Nate Graham changed: What|Removed |Added CC||n...@kde.org, ||xaver.h...@gmail.com --- Comment #1 from Nate Graham --- Seems quite relevant: > Jul 21 10:14:08 david-laptop org_kde_powerdevil[1135]: org.kde.powerdevil: > org.kde.powerdevil.discretegpuhelper.hasdualgpu failed Is this a dual-GPU system? -- You are receiving this mail because: You are watching all bug changes.
