Bugzilla – Bug 1182673
Hangs at "started locale service" [sway]
Last modified: 2021-03-08 20:05:45 UTC
When I zypper dup my system I can't start it anymore. Started 1-2 weeks ago. It hangs during boot at "started locale service". There's an mouse cursor I can move though. Got to rollback then. Was doing internet research and most often it was issuing the display manager or proprietary graphics drivers. I use lightdm with autologin. And the notebook only has an ordinary intel onboard graphics. It's a Fujitsu Lifebook S782. What can I do? What information do you need?
Now I get a different output after latest zypper dup: lightdm[2147]: session_real_start: assertion 'priv->pid == 0' failed lightdm[2147]: g_file_test: assertion 'filename != NULL' failed No mouse cursor this time, stops at "login:" (tty).
...'journalctl -x' btw.
Hi Alexei, I'm not quite sure whether it is correct to assign it to you, please feel free to reassign whenever necessary, thanks.
First, from the description it seems unlikely that is caused by sway, but lets verify that. Did you get to graphical login manager? - If so, could you start any other session? - If not, could you access command line and run `sway` directly?
Created attachment 846859 [details] journalctl -x I just did another zypper dup update. This time I get to the display manager, but it has a different look now. Looks more like sddm/KDE Plasma instead of GTK 'lightweighty'. And I can't log in anymore, neither via display manager nor via tty1: "user not known to the underlying authentication module". Hope that I have caught the right journalctl place....
Well, this is not related to sway at all. It's not even obvious if it is bug or just configuration issue. Attached log shows how NetworkManager was disconnected - maybe during `zypper dup`. It's not helpful for neither of reported issues, I'd recommend to use some interactive support channel instead of bug reporting: https://en.opensuse.org/Portal:Support#Interactive
Sorry for posting here again but I think I nailed down the problem. I updated only xterm (1.1.12-14.1 to 1.1.12-14.2) and the unwanted behavior appeared again. .Xdefaults: 1 URxvt.saveLines: 1000 2 URxvt.scrollBar: false 3 URxvt.foreground: white 4 URxvt.background: black 5 #URxvt.secondaryScroll: true 6 URxvt.font: xft:Bitstream Vera Sans Mono:pixelsize=13 7 URxvt.perl-ext-common: default,matcher 8 URxvt.urlLauncher: firefox 9 URxvt.matcher.button: 1 10 URxvt.tabbed.saveLines: 1000 11 URxvt.tabbed.scrollBar: false 12 URxvt.tabbed.tabbar-fg: 3 13 URxvt.tabbed.tabbar-bg: 0 14 URxvt.tabbed.tab-fg: 0 15 URxvt.tabbed.tab-bg: 1 16 URxvt.tabbed.secondaryScroll: true 17 URxvt.tabbed.font: xft:Bitstream Vera Sans Mono:pixelsize=12 18 #URxvt*inheritPixmap: false 19 URxvt*transparent: false 20 #URxvt*shading: 10 Any idea, hint?
..sorry, I meant xdm
I would need to know, which changes are supposed to be the culprit of that issue. Could you please provide the output of rpm --changelog -q xdm | head -n 5 before and after the update?
Here's the 'before': * Mo Jan 04 2021 Stefan Dirsch <sndirsch@suse.com> - fixed path of pidof tool for older openSUSE Leap releases (boo#1179607) * Di Dez 01 2020 Stefan Dirsch <sndirsch@suse.com> The 'after' gonna be problematic because I can't login anymore. Maybe over ssh?.. Do you think it's related to?: https://bugzilla.opensuse.org/show_bug.cgi?id=1173049
Well, that's already the latest change in xdm. So this can't be the culprit. Sorry.
Pretty sure it's systemd. I resolved all xdm dependencies and installed one after one, even xdm itself.