[kscreenlocker] [Bug 453741] Lock screen is broken
https://bugs.kde.org/show_bug.cgi?id=453741 --- Comment #10 from giuseppe --- Created attachment 148804 --> https://bugs.kde.org/attachment.cgi?id=148804=edit coredumpctl after i run the command from bash instead of fish I thought backtrace was the output when I tried to run the lock screen from bash. Instead it should be the coredumpctl. This one seems longer of 40 lines indeed. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 453741] Lock screen is broken
https://bugs.kde.org/show_bug.cgi?id=453741 --- Comment #9 from giuseppe --- Seens exact same, just this time i used bash as you suggested -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 453741] Lock screen is broken
https://bugs.kde.org/show_bug.cgi?id=453741 --- Comment #8 from Nate Graham --- Is the backtrace the same? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 453741] Lock screen is broken
https://bugs.kde.org/show_bug.cgi?id=453741 --- Comment #7 from giuseppe --- /usr/libexec/kscreenlocker_greet --testing Locked at 1652457928 file:///usr/share/plasma/look-and-feel/org.fedoraproject.fedora.desktop/contents/components/UserList.qml:42:9: Unable to assign [undefined] to bool qt.qpa.wayland: Wayland does not support QWindow::requestActivate() file:///usr/share/plasma/look-and-feel/org.fedoraproject.fedora.desktop/contents/components/UserList.qml:42:9: Unable to assign [undefined] to bool qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Segmentation fault (core dumped) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 453741] Lock screen is broken
https://bugs.kde.org/show_bug.cgi?id=453741 --- Comment #6 from Nate Graham --- > #0 0x7f0b702ecc4f > _ZN18QMetaObjectPrivate10disconnectEPK7QObjectiPK11QMetaObjectS2_iPPvNS_14DisconnectTypeE > (libQt5Core.so.5 + 0x2d4c4f) > #1 0x7f0b702edc82 > _ZN7QObject14disconnectImplEPKS_PPvS1_S3_PK11QMetaObject (libQt5Core.so.5 + > 0x2d5c82) > #2 0x55cb07a8694f > _ZN12ScreenLocker9UnlockApp18markViewsAsVisibleEPN12KQuickAddons21QuickViewSharedEngineE > (kscreenlocker_greet + 0x1094f) Can you use bash (or whatever your login shell is) in your konsole window, and run `/usr/libexec/kscreenlocker_greet --testing` again? Does it still crash with the same backtrace? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 453741] Lock screen is broken
https://bugs.kde.org/show_bug.cgi?id=453741 --- Comment #5 from giuseppe --- Additional findings: I have a soundbar attached and powered by the monitor itself. After I tried a couple of time the screen locker I noticed the soundbar profile was set off by itself. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 453741] Lock screen is broken
https://bugs.kde.org/show_bug.cgi?id=453741 --- Comment #4 from giuseppe --- Created attachment 148801 --> https://bugs.kde.org/attachment.cgi?id=148801=edit coredumpctl gdb this is the coredumpctl. About the other question, I just have fish set in use as konsole command, I didn't do chsh to set it. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 453741] Lock screen is broken
https://bugs.kde.org/show_bug.cgi?id=453741 Nate Graham changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO --- Comment #3 from Nate Graham --- Seems like kscreenlocker_greet is crashing. That definitely shouldn't happen. :) Can you get a backtrace of it? You may be able to use `coredumpctl` to get an existing one. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl I also notice that you're using fish shell. Does the issue go away if you change your login shell to bash? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 453741] Lock screen is broken
https://bugs.kde.org/show_bug.cgi?id=453741 giuseppe changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #2 from giuseppe --- (In reply to Nate Graham from comment #1) > What happens if you run `/usr/libexec/kscreenlocker_greet --testing` ? Can > you do so and paste the output in your terminal window? It didn't crash this time. But after I turn off the monitor and on again it didn't ask for my password. Below the output: Locked at 1652454987 file:///usr/share/plasma/look-and-feel/org.fedoraproject.fedora.desktop/contents/components/UserList.qml:42:9: Unable to assign [undefined] to bool qt.qpa.wayland: Wayland does not support QWindow::requestActivate() file:///usr/share/plasma/look-and-feel/org.fedoraproject.fedora.desktop/contents/components/UserList.qml:42:9: Unable to assign [undefined] to bool qt.qpa.wayland: Creating a fake screen in order for Qt not to crash fish: Job 1, '/usr/libexec/kscreenlocker_gree…' terminated by signal SIGSEGV (Address boundary error) It seems the problem was the external monitor itself -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 453741] Lock screen is broken
https://bugs.kde.org/show_bug.cgi?id=453741 Nate Graham changed: What|Removed |Added Severity|normal |grave Status|REPORTED|NEEDSINFO CC||n...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- What happens if you run `/usr/libexec/kscreenlocker_greet --testing` ? Can you do so and paste the output in your terminal window? -- You are receiving this mail because: You are watching all bug changes.
