https://bugs.kde.org/show_bug.cgi?id=385321
veeh...@zoho.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |CONFIRMED
--- Comment #17 from veeh...@zoho.com ---
(In reply to Nate Graham from comment #16)
> In general for these kinds of issues it's always good to file a new bug
> report, since an issue with the same symptoms can be caused by wildly
> different root causes.
I'm happy to create my own bug report and link back. Would you like me to do
that?
I've had the loginctl finally happen to me tonight.
> ...
> [Fri Nov 18 18:06:26 2022] wlp166s0: authenticate with e8:48:b8:9b:4a:45
> [Fri Nov 18 18:06:26 2022] wlp166s0: send auth to e8:48:b8:9b:4a:45 (try 1/3)
> [Fri Nov 18 18:06:26 2022] wlp166s0: authenticate with e8:48:b8:9b:4a:45
> [Fri Nov 18 18:06:26 2022] wlp166s0: send auth to e8:48:b8:9b:4a:45 (try 1/3)
> [Fri Nov 18 18:06:26 2022] wlp166s0: authenticated
> [Fri Nov 18 18:06:26 2022] wlp166s0: associate with e8:48:b8:9b:4a:45 (try
> 1/3)
> [Fri Nov 18 18:06:26 2022] wlp166s0: RX AssocResp from e8:48:b8:9b:4a:45
> (capab=0x511 status=0 aid=2)
> [Fri Nov 18 18:06:26 2022] wlp166s0: associated
> [Fri Nov 18 18:06:26 2022] wlp166s0: Limiting TX power to 27 (30 - 3) dBm as
> advertised by e8:48:b8:9b:4a:45
> [Fri Nov 18 18:06:26 2022] IPv6: ADDRCONF(NETDEV_CHANGE): wlp166s0: link
> becomes ready
> [Fri Nov 18 18:06:28 2022] wlp166s0: deauthenticating from e8:48:b8:9b:4a:45
> by local choice (Reason: 3=DEAUTH_LEAVING)
> [Fri Nov 18 18:06:29 2022] show_signal_msg: 63 callbacks suppressed
> [Fri Nov 18 18:06:29 2022] kscreenlocker_g[3741]: segfault at 18 ip
> 00007f9a0f90bda6 sp 00007ffdab661660 error 4 in
> libLayerShellQtInterface.so.5.26.3[7f9a0f90a000+3000]
> [Fri Nov 18 18:06:29 2022] Code: 8d 64 24 38 48 89 44 24 28 48 89 ee 4c 89 e7
> e8 10 e8 ff ff 48 89 ef e8 08 e9 ff ff 4c 89 e6 4c 89 ef 89 44 24 24 49 8b 46
> 38 <4c> 8b 48 18 4c 89 4c 24 18 e8 cc e9 ff ff 48 8b 44 24 40 4d 8b 7f
> [Fri Nov 18 18:06:29 2022] PM: suspend entry (s2idle)
> [Fri Nov 18 18:06:29 2022] Filesystems sync: 0.105 seconds
> [Fri Nov 18 18:06:29 2022] Freezing user space processes ... (elapsed 0.002
> seconds) done.
> [Fri Nov 18 18:06:29 2022] OOM killer disabled.
> [Fri Nov 18 18:06:29 2022] Freezing remaining freezable tasks ... (elapsed
> 0.001 seconds) done.
> [Fri Nov 18 18:06:29 2022] printk: Suspending console(s) (use
> no_console_suspend to debug)
> [Fri Nov 18 18:06:30 2022] PM: suspend devices took 0.593 seconds
> [Fri Nov 18 18:06:30 2022] ACPI: EC: interrupt blocked
> ...
OS: Fedora 37 KDE spin
KDE plasma version: 5.26.3
Frameworks version: 5.100.0
QT version: 5.15:6
kernel: 6.0.8-300.fc37
Graphics platform: Wayland
The exact process I've done tonight is disconnect laptop from charger/usb dock,
update the entire OS via KDE Discover(i noticed the general OS updates and a
handful of KDE flatpak updates) and reboot to apply the various updates. Login
and fairly quickly press powerbutton to sleep. I come back about an hour later
to wake laptop up and thats when i'm presented by the loginctl screen.
Based on the above dmesg output, kscreenlocker_g crashed as the laptop went
into sleep, and not on the way out. First time I've had an issue since owning
this laptop (about 2 weeks).
Laptop is a Framework i5-1240P model.
--
You are receiving this mail because:
You are watching all bug changes.
