[Plasma-Mobile] not booting after installing some apps

Describe your issue

What's the expected behaviour?

Plasma Mobile should boot.

What's the current behaviour?

Plasma Mobile stopped booting after I installed some apps.

How to reproduce your issue?

Unknown

What device are you using?

xiaomi-wt88047

On what postmarketOS version did you encounter the issue?

• edge (master branch)
• v21.12

On what environment did you encounter the issue?

Phone environments

• Phosh
• Plasma Mobile
• Sxmo (Wayland/Sway)

Other

• No environment
• GNOME
• KDE Plasma
• Kodi
• MATE
• Shelli
• Sway
• Weston
• Xfce4
• fbkeyboard
• i3wm
• Sxmo (Xorg/Dwm)

How did you get postmarketOS image?

• from https://images.postmarketos.org
• I built it using pmbootstrap
• It was preinstalled on my device

What's the build date of the image? (in yyyy-mm-dd format)

ca. 2022-01-31

Additional information

All I did was install some end user mobile apps via apk and flatpak and reboot the device.

logread: https://paste.ubuntu.com/p/dXmCFMX6Fp/ dmesg: https://paste.ubuntu.com/p/CSxPGt7wVz/ ~/.local/state/tinydm.log and ~/.local/state/tinydm.log.old exist but are empty.

changed the description

By Julian Groß on 2022-02-01T22:42:20

Some debugging with @PureTryOut came across a clue:

xiaomi-wt86047-stable:~$ /usr/bin/autologin 10000 tindym-run-session
pam_acct_mgmt failed: User not known to the underlying authentication module
xiaomi-wt86047-stable:~$ 

logread has similar output:

Jan 29 23:10:45 xiaomi-wt86047-stable authpriv.info : pam_unix(autologin:session): session closed for user motofckr9k
Jan 29 23:10:45 xiaomi-wt86047-stable daemon.warn supervise-daemon[7098]: /usr/bin/autologin, pid 8242, exited with return code 0
Jan 29 23:10:45 xiaomi-wt86047-stable auth.info elogind[2258]: Removed session c15.

xiaomi-wt86047-stable:~$ id
uid=10000(motofckr9k) gid=10000(motofckr9k) groups=10(wheel),18(audio),23(input),27(video),28(netdev),101(plugdev),10000(motofckr9k)
xiaomi-wt86047-stable:~$ 

By Julian Groß on 2022-02-03T14:50:18

Apparently autologin just needs the username and not the user id. The command finished without the authentification error now.

By Julian Groß on 2022-02-03T14:50:18

So I went through and installed the same apk apps on a different phone and I cannot reproduce the issue there. I haven't tried the flatpak apps yet, but I guess I will need to get to that as well now.

By Julian Groß on 2022-02-02T01:14:19

Yeah to probably no ones surprise, the flatpak apps weren't the problem either.

By Julian Groß on 2022-02-02T01:43:12

mentioned in issue #1290 (closed)

By Julian Groß on 2022-02-18T11:47:00

So I found out that uninstalling Geary (yes the email client) fixes the issue. I cannot reproduce the issue though. Since Geary doesn't fully launch, I can only guess that one of my attempts at restarting it somehow corrupted a config of something.

Whatever the case, what prompted me to try uninstalling Geary was etc/xdg/autostart/org.gnome.Evolution-alarm-notify.desktop and my knowledge that Geary doesn't complete launch. I guess it must have tried autostarting this notifier and failed. According to etckeeper, uninstalling and reinstalling Geary didn't change anything in /etc

By Julian Groß on 2022-03-31T07:21:30

Really strange, installing any random app really shouldn't break launching of the DE. Do you get the problem again if you reinstall Geary?

By Bart Ribbers on 2022-03-31T07:21:30

No, I haven't been able to reproduce it. I know that uninstalling Geary was what fixed the issue (since it was the only action I took on that try), but reinstalling it didn't break it again.

By Julian Groß on 2022-03-31T14:42:56

assigned to @PureTryOut

By Bart Ribbers on 2022-03-31T07:21:33

mentioned in issue #1544 (closed)

By Julian Groß on 2022-06-02T17:18:03

Installing Geary doesn't break anything, I am closing this since there is too little info and this might already be fixed.

By Julian Groß on 2023-12-05T11:16:22

closed