| Summary: | login to X11 session hangs (Arm64 on Raspberry Pi 4B) | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | HankB <hbarta> |
| Component: | Startup process | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | grave | CC: | hbarta, kde, nate |
| Priority: | NOR | ||
| Version: | 5.27.2 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
attachment-3075987-0.html
attachment-1993125-0.html |
||
|
Description
HankB
2023-03-26 14:23:46 UTC
I installed XFCE4 on this host to test another DE on X11 (and test another DM) with the following results. * XFCE (on X11) starts w/out issue using `lightdm` or `sddm`. * Plasma/X11 hangs when started using `lightdm`. * Plasma/Wayland starts normally from `lightdm`. I have collected further information starting with additions to ~/.xsession-errors when logging in using Plasma/X11 Xsession: X session started for hbarta at Sun Mar 26 10:51:33 CDT 2023 dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus dbus-update-activation-environment: setting DISPLAY=:0 dbus-update-activation-environment: setting XAUTHORITY=/home/hbarta/.Xauthority localuser:hbarta being added to access control list dbus-update-activation-environment: setting QT_ACCESSIBILITY=1 https://pastebin.com/JSD6qBrq dmesg output from boot through successful Wayland login and hanging X11 login https://pastebin.com/R6qcBXyn /var/log/Xorg.0.log contents following Wayland login https://pastebin.com/e6FwyABX /var/log/Xorg.0.log contents following X11 login and hang I performed a normal (Debian) update which included the following packages. adduser/testing 3.132 all [upgradable from: 3.131] libldb2/testing 2:2.6.2+samba4.17.7+dfsg-1 arm64 [upgradable from: 2:2.6.1+samba4.17.6+dfsg-1] libnm0/testing 1.42.4-1 arm64 [upgradable from: 1.42.0-1] libsmbclient/testing 2:4.17.7+dfsg-1 arm64 [upgradable from: 2:4.17.6+dfsg-1] libwbclient0/testing 2:4.17.7+dfsg-1 arm64 [upgradable from: 2:4.17.6+dfsg-1] network-manager/testing 1.42.4-1 arm64 [upgradable from: 1.42.0-1] samba-libs/testing 2:4.17.7+dfsg-1 arm64 [upgradable from: 2:4.17.6+dfsg-1] tzdata/testing 2023c-2 all [upgradable from: 2022g-7] The problem behavior is still there. As Debian Testing is in a state of flux, I will continue to periodically test to see if any package updates fix this problem. Please do let me know if there is further testing or information collection I can help with. Thank you for your attention. Can you describe in more detail what "system hangs" means? Is the cursor frozen? Or can you move it but you can'c click on anything? Or, you can move it and click on things, but nothing happens? etc. Apologies for not providing a better description. When logging in to Plasma/X11 1. I get the black interim screen With the KDE logi. 1. For a moment I see what looks like a desktop, but less than a second. 1. Screen returns to black with the KDE logo. It is stuck there and never proceeds to the desktop. 1. Mouse is working, I don't recall if the keyboard worked (e.g. <ctrl><alt><Fn> to get to a text console. There is no keyboard response otherwise. 1. I can `ssh` in and `systemctl restart sddm` and get back to the DM. At that point I can successfully log in to KDE/Wayland but not KDE/X11. I installed XFCE and can login to an X11 session using that which behaves normally. Thank you. Do you have automatic login enabled? Created attachment 157996 [details] attachment-3075987-0.html No. Is that something I should try? On Mon, Apr 10, 2023 at 10:16 AM Nate Graham <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=467812 > > --- Comment #6 from Nate Graham <nate@kde.org> --- > Do you have automatic login enabled? > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug. Nah, I just wanted to know. Does anything in https://userbase.kde.org/Troubleshooting/Black_Screen help? I checked the information at the link you provided and there wasn't anything particularly helpful. I did perform an upgrade and got a few packages including xwayland but the problem persists. The desktop session service was new to me so I checked it and it seems to be OK.
● plasma-plasmashell.service - KDE Plasma Workspace
Loaded: loaded (/usr/lib/systemd/user/plasma-plasmashell.service; enabled; preset: enabled)
Active: active (running) since Mon 2023-04-10 15:23:19 CDT; 1min 49s ago
Main PID: 891 (plasmashell)
Tasks: 15 (limit: 9214)
Memory: 204.9M
CPU: 12.360s
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service
├─ 891 /usr/bin/plasmashell --no-respawn
├─1084 /lib/aarch64-linux-gnu/libexec/kf5/kioslave5 /usr/lib/aarch64-linux-gnu/qt5/plugins/kf5/kio/desktop.so desktop "" local:/run/user/1000/plasmashellgCfUNv.1.kioworker.socket
└─1249 /lib/aarch64-linux-gnu/libexec/kf5/kioslave5 /usr/lib/aarch64-linux-gnu/qt5/plugins/kf5/kio/tags.so tags "" local:/run/user/1000/plasmashellNMQZHV.2.kioworker.socket
Apr 10 15:23:33 charm plasmashell[891]: org.kde.plasma.notifications: Failed to register Notification service on DBus
Apr 10 15:23:33 charm plasmashell[891]: file:///usr/lib/aarch64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Apr 10 15:23:33 charm plasmashell[891]: file:///usr/lib/aarch64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Apr 10 15:23:33 charm plasmashell[891]: file:///usr/lib/aarch64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Apr 10 15:23:33 charm plasmashell[891]: file:///usr/lib/aarch64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Apr 10 15:23:33 charm plasmashell[891]: file:///usr/lib/aarch64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Apr 10 15:23:33 charm plasmashell[891]: file:///usr/lib/aarch64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Apr 10 15:23:34 charm plasmashell[891]: file:///usr/lib/aarch64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Apr 10 15:23:35 charm plasmashell[891]: file:///usr/lib/aarch64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Apr 10 15:23:35 charm plasmashell[891]: file:///usr/lib/aarch64-linux-gnu/qt5/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
hbarta@charm:~$
I plan to followup with further details on logs etc. but cannot do that right now.
I tested the "hang" again and observed: 1. After login, switch to black screen with three dots and ">" logo centered and "Plasma made by KDE" + logo in lower right. There is a small gear below the centered logo that is rotating. 2. Brief flash that looks like desktop, less than a second. 3. Return to black screen as before, with logos but the gear is no longer rotating. 4. Mouse is responsive. Clicking on lower left corner shows no hint that anything is happening. 5. <ctrl><alt><fN> for N= 1..6 opens a text console. <alt><F7> returns to black screen as described in 3. 6. If left alone (no mouse, keyboard) the screen will go to low power mode according to power settings. Mouse or keyboard input brings it back up to the screen as described in 3. I have collected information from various sources and pasted into https://pastebin.com/ZfqB1tJe I checked for possible related failed systemd services and found systemd-networkd-wait-online.service which failed shortly after boot, about 5 hours ago. Allow me to wander a bit. Raspberry Pi ecosystem is a bit different from the typical X86_64. You don't mention if you have experience with that so I'm presuming perhaps not. One benefit is that the H/W is pretty invariant, though I understand that the Pi 4B uses a different GPU than previous models. But all Pi 4Bs will use the same GPU and that should make things a little easier. OTOH, I don't think that the people with the most experience with the Pi push their changes back upstream. I'm running straight Debian so I do not benefit from their efforts. Also, I'm not using the default DE for Debian which I'm sure you know is Gnome. I'm probably in a very small group of users wishing to use KDE on Debian on a Pi 4B on the Testing variant which should graduate to Stable some time in 2023. When It's ready. I don't believe that this kind of bug will hold up that graduation. I'm also aware that resources for open source projects are never quite enough. If you need to triage this and at some point relegate it to "won't fix" because there are more impactful areas demanding your time, I fully understand and will respect that decision. And will hope that progress on Wayland is swift. (I'm using it on my X86_64 desktop and laptop for KDE/Plasma.) In the mean time I will continue to perform any tests and collect any information you request, as quickly as possible to hopefully keep the context fresh. Again, Thanks! I appreciate your perspective here, thanks. Resources are indeed quite limited, and I don't have any direct experience with this hardware. It almost sounds like after login, the session is crashing. In a virtual terminal, can you use `coredumpctl` to see if there are any crash logs from right after login? I looked at output from `coredumpctl` and found the following. root@charm:~# coredumpctl TIME PID UID GID SIG COREFILE EXE SIZE Mon 2023-04-03 11:36:14 CDT 3085 1000 1000 SIGSEGV missing /usr/lib/chromium/chromium - Mon 2023-04-03 11:36:18 CDT 3177 1000 1000 SIGSEGV missing /usr/lib/chromium/chromium - Mon 2023-04-03 11:36:21 CDT 3195 1000 1000 SIGSEGV missing /usr/lib/chromium/chromium - Mon 2023-04-03 11:42:17 CDT 3751 1000 1000 SIGABRT missing /usr/lib/aarch64-linux-gnu/libexec/org_kde_powerdevil - Mon 2023-04-03 11:42:18 CDT 3759 1000 1000 SIGABRT missing /usr/bin/plasmashell - Mon 2023-04-03 11:42:18 CDT 3774 1000 1000 SIGABRT missing /usr/lib/aarch64-linux-gnu/libexec/org_kde_powerdevil - Mon 2023-04-03 11:42:18 CDT 3783 1000 1000 SIGABRT missing /usr/bin/plasmashell - Mon 2023-04-03 11:42:19 CDT 3796 1000 1000 SIGABRT missing /usr/lib/aarch64-linux-gnu/libexec/org_kde_powerdevil - Mon 2023-04-03 11:42:20 CDT 3806 1000 1000 SIGABRT missing /usr/bin/plasmashell - Mon 2023-04-03 11:42:20 CDT 3818 1000 1000 SIGABRT missing /usr/lib/aarch64-linux-gnu/libexec/org_kde_powerdevil - Mon 2023-04-03 11:42:21 CDT 3859 1000 1000 SIGABRT missing /usr/lib/aarch64-linux-gnu/libexec/org_kde_powerdevil - Mon 2023-04-03 11:42:21 CDT 3860 1000 1000 SIGABRT missing /usr/lib/aarch64-linux-gnu/libexec/xdg-desktop-portal-kde - Thu 2023-04-06 14:27:11 CDT 1193 1000 1000 SIGTRAP missing /usr/bin/light-locker - Thu 2023-04-06 14:28:27 CDT 1842 1000 1000 SIGTRAP missing /usr/bin/light-locker - Thu 2023-04-06 14:28:34 CDT 1618 1000 1000 SIGSEGV missing /usr/bin/plasmashell - Thu 2023-04-06 14:32:03 CDT 1121 1000 1000 SIGTRAP missing /usr/bin/light-locker - Mon 2023-04-10 15:23:26 CDT 1145 1000 1000 SIGTRAP present /usr/bin/light-locker 440.0K Mon 2023-04-10 20:43:53 CDT 2627 1000 1000 SIGTRAP present /usr/bin/light-locker 440.6K Mon 2023-04-10 22:32:30 CDT 4247 1000 1000 SIGTRAP present /usr/bin/light-locker 440.3K Mon 2023-04-10 22:33:46 CDT 4710 1000 1000 SIGTRAP present /usr/bin/light-locker 448.5K Tue 2023-04-11 13:54:54 CDT 1257 1000 1000 SIGTRAP present /usr/bin/light-locker 439.3K Tue 2023-04-11 13:56:43 CDT 1804 1000 1000 SIGTRAP present /usr/bin/light-locker 1.9M The one at "Tue 2023-04-11 13:54:54" was logging in using lightdm. After that I stopped lightdm and started sddm and logged in again. That resulted in the entry at Tue 2023-04-11 13:56:43. I purged lightdm, which also removed light-locker. Login still hangs and there are no additional reports from coredumpct. 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! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! Created attachment 158874 [details] attachment-1993125-0.html I tried to change the status to something other than "worksforme" because it does not. I understand it won't get attention due to time constraints but don;t think it should be marked as such. A status of "won't fix" would be appropriate. I do appreciate the attention that this received and hope that at some point some other change will resolve the situation (or Wayland will be sufficiently usable that X11 won't matter.) On Thu, May 11, 2023 at 10:46 PM Bug Janitor Service < bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=467812 > > Bug Janitor Service <bug-janitor@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|NEEDSINFO |RESOLVED > Resolution|WAITINGFORINFO |WORKSFORME > > --- Comment #15 from Bug Janitor Service <bug-janitor@kde.org> --- > This bug has been in NEEDSINFO status with no change for at least > 30 days. The bug is now 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 > > Thank you for helping us make KDE software even better for everyone! > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug. |