jadams@jadams-Vivobook-Go-E1504FA-E1504FA:~$ apt list *indicator-*
ayatana-indicator-a11y/oracular,now 24.4.1-1 amd64 [residual-config]
ayatana-indicator-application/oracular,now 22.2.0-2 amd64 [installed,automatic]
ayatana-indicator-bluetooth/oracular 24.5.0-1 amd64
ayatana-indicator-common/oracular,now 0.9.10-3 all [installed,automatic]
ayatana-indicator-datetime/oracular,now 24.5.0-1 amd64 [installed]
ayatana-indicator-display/oracular,now 24.5.0-1 amd64 [installed]
ayatana-indicator-keyboard/oracular,now 24.7.0-2 amd64 [residual-config]
ayatana-indicator-messages/oracular,now 24.5.0-1 amd64 [installed,automatic]
ayatana-indicator-notifications/oracular,now 23.10.1-1 amd64 [installed,automatic]
ayatana-indicator-power/oracular,now 24.5.1-2 amd64 [installed]
ayatana-indicator-printers/oracular,now 23.10.1-2 amd64 [installed,automatic]
ayatana-indicator-session/oracular,now 24.5.0-1 amd64 [installed,automatic]
ayatana-indicator-sound/oracular,now 24.5.0-1 amd64 [installed]
budgie-indicator-applet/oracular 0.7.2-4 amd64
cairo-dock-drop-indicator-plug-in/oracular 3.4.1+git20201022.a0d3415c-1.1ubuntu2 amd64
cairo-dock-keyboard-indicator-plug-in/oracular 3.4.1+git20201022.a0d3415c-1.1ubuntu2 amd64
indicator-applet/oracular 12.10.2+20.10.20241006-0ubuntu1 amd64
indicator-application/oracular,now 12.10.1+19.04.20190308.1-0ubuntu5 amd64 [installed,automatic]
indicator-appmenu-tools/oracular 15.02.0+20.10.20200617.2-0ubuntu4 amd64
indicator-appmenu/oracular 15.02.0+20.10.20200617.2-0ubuntu4 amd64
indicator-bluetooth/oracular 0.0.6+17.10.20170605-0ubuntu5 amd64
indicator-china-weather/oracular 3.0.4.1-0ubuntu3 amd64
indicator-common/oracular,now 16.10.0+18.04.20180321.1-0ubuntu8 all [installed,automatic]
indicator-cpufreq/oracular 0.2.2-0ubuntu4 all
indicator-datetime/oracular,now 15.10+21.04.20210304-0ubuntu6 amd64 [residual-config]
indicator-keyboard/oracular,now 0.0.0+19.10.20240924-0ubuntu1 amd64 [residual-config]
indicator-messages/oracular 13.10.1+18.10.20180918-0ubuntu7 amd64
indicator-multiload/oracular 0.4-0ubuntu7 amd64
indicator-notifications/oracular 0.4.2-0ubuntu3 amd64
indicator-power/oracular,now 12.10.6+17.10.20170829.1-0ubuntu9 amd64 [residual-config]
indicator-printers/oracular 0.1.7+17.10.20171101-0ubuntu7 amd64
indicator-sensors/oracular 1.4-1build2 amd64
indicator-session/oracular 17.3.20+21.10.20210613.1-0ubuntu3 amd64
indicator-sound/oracular,now 12.10.2+18.10.20180612-0ubuntu7 amd64 [residual-config]
libappindicator-doc/oracular 12.10.1+20.10.20200706.1-0ubuntu6 all
libayatana-appindicator-doc/oracular 0.5.93+really-1 all
libindicator-dev/oracular 16.10.0+18.04.20180321.1-0ubuntu8 amd64
libindicator-transfer-dev/oracular 1.1.0-3 amd64
libindicator-transfer1t64/oracular 1.1.0-3 amd64
lomiri-indicator-network/oracular 1.0.2-7 amd64
lomiri-indicator-transfer-common/oracular 1.1.0-3 all
lomiri-indicator-transfer-download-manager/oracular 1.1.0-3 amd64
lomiri-indicator-transfer/oracular 1.1.0-3 amd64
mate-indicator-applet-common/oracular,now 1.26.0-1build3 all [installed,automatic]
mate-indicator-applet/oracular,now 1.26.0-1build3 amd64 [installed,automatic]
unity-indicator-appearance/oracular 1.2 all
xfce4-indicator-plugin/oracular 2.4.2-1build2 amd64
You have conflicting indicators left: new ayatana ones vs old canonical.
Remove them just in case:
apt --simulate remove indicator-application indicator-common
jadams@jadams-Vivobook-Go-E1504FA-E1504FA:~$ apt --simulate remove indicator-application indicator-common
NOTE: This is only a simulation!
apt needs root privileges for real execution.
Keep also in mind that locking is deactivated,
so don't depend on the relevance to the real current situation!
The following package was automatically installed and is no longer required:
libindicator3-7
Use 'apt autoremove' to remove it.
REMOVING:
indicator-application indicator-common
Summary:
Upgrading: 0, Installing: 0, Removing: 2, Not Upgrading: 1
Remv indicator-application [12.10.1+19.04.20190308.1-0ubuntu5]
Remv indicator-common [16.10.0+18.04.20180321.1-0ubuntu8]
is libayatana-indicator3-7 installed?
Yes, it is.
jadams@jadams-Vivobook-Go-E1504FA-E1504FA:~$ apt list -i | grep libayatana-indicator3-7
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
libayatana-indicator3-7/oracular,now 0.9.4-1build1 amd64 [installed,automatic]
jadams@jadams-Vivobook-Go-E1504FA-E1504FA:~$
sudo apt remove indicator-application indicator-common
Done.
jadams@jadams-Vivobook-Go-E1504FA-E1504FA:~$ sudo apt remove indicator-application indicator-common
The following package was automatically installed and is no longer required:
libindicator3-7
Use 'sudo apt autoremove' to remove it.
REMOVING:
indicator-application indicator-common
Summary:
Upgrading: 0, Installing: 0, Removing: 2, Not Upgrading: 1
Freed space: 126 kB
Continue? [Y/n]
(Reading database ... 291701 files and directories currently installed.)
Removing indicator-application (12.10.1+19.04.20190308.1-0ubuntu5) ...
Removing indicator-common (16.10.0+18.04.20180321.1-0ubuntu8) ...
Your config looks fine, so try to reboot.
Sounds good. I'll reboot and report back with the results.
Many thanks for your help.
Okay, I hope it helps.
That problem is fixed. However, today it is like playing Whack-a-mole with LightDM problems unfortunately.
I rebooted and got greeted by a TTY prompt. I tried to enable LightDM (as I had disabled it earlier so I could boot into my system) and I got the following error from systemd:
jadams@jadams-Vivobook-Go-E1504FA-E1504FA:~$ sudo systemctl enable lightdm
[sudo] password for jadams:
Synchronizing state of lightdm.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install enable lightdm
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.
Possible reasons for having these kinds of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/, .requires/, or .upholds/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
Then this when I typed sudo systemctl status lightdm:
jadams@jadams-Vivobook-Go-E1504FA-E1504FA:~$ sudo systemctl status lightdm
● lightdm.service - Light Display Manager
Loaded: loaded (/usr/lib/systemd/system/lightdm.service; static)
Active: active (running) since Sat 2025-01-18 18:06:25 EST; 2min 8s ago
Invocation: 3de846de1550470284aa53d5a3886c77
Docs: man:lightdm(1)
Main PID: 2181 (lightdm)
Tasks: 17 (limit: 8420)
Memory: 161.5M (peak: 162.2M)
CPU: 4.310s
CGroup: /system.slice/lightdm.service
├─2181 /usr/sbin/lightdm
└─2188 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
Jan 18 18:06:25 jadams-Vivobook-Go-E1504FA-E1504FA systemd[1]: Started lightdm.service - Light Display Manager.
Jan 18 18:06:26 jadams-Vivobook-Go-E1504FA-E1504FA lightdm[2214]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=110) by (uid=0)
Jan 18 18:06:26 jadams-Vivobook-Go-E1504FA-E1504FA lightdm[2214]: pam_systemd(lightdm-greeter:session): New sd-bus connection (system-bus-pam-systemd-2214) opened.
Jan 18 18:06:26 jadams-Vivobook-Go-E1504FA-E1504FA lightdm[2214]: gkr-pam: couldn't unlock the login keyring.
Jan 18 18:06:26 jadams-Vivobook-Go-E1504FA-E1504FA lightdm[2372]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "jadams"
Jan 18 18:06:31 jadams-Vivobook-Go-E1504FA-E1504FA lightdm[2372]: gkr-pam: unable to locate daemon control file
Jan 18 18:06:31 jadams-Vivobook-Go-E1504FA-E1504FA lightdm[2372]: gkr-pam: stashed password to try later in open session
Jan 18 18:06:31 jadams-Vivobook-Go-E1504FA-E1504FA lightdm[2372]: pam_unix(lightdm:session): session opened for user jadams(uid=1000) by (uid=0)
Jan 18 18:06:31 jadams-Vivobook-Go-E1504FA-E1504FA lightdm[2372]: pam_systemd(lightdm:session): New sd-bus connection (system-bus-pam-systemd-2372) opened.
Jan 18 18:06:31 jadams-Vivobook-Go-E1504FA-E1504FA lightdm[2372]: gkr-pam: unlocked login keyring
I know the greeter is fixed through because, from TTY, I typed sudo systemctl enable lightdm --now and it presented me with the correct LightDM screen.
Hopefully I didn't screw myself by initially disabling LightDM to boot into my laptop.
Update: When I rebooted the laptop, even though it says LightDM is activated in systemd, I still got booted to a TTY prompt with the following:
jadams@jadams-Vivobook-Go-E1504FA-E1504FA:~$ sudo systemctl status lightdm
[sudo] password for jadams:
○ lightdm.service - Light Display Manager
Loaded: loaded (/usr/lib/systemd/system/lightdm.service; static)
Active: inactive (dead)
Docs: man:lightdm(1)
I haven't faced systemd + lightdm issues before, unfortunately.
1 Like
Thank you. I'll take a look at the article you sent.
I appreciate your time and help today.
Jaymo
1 Like
You are welcome, @jaymo_chicago !
1 Like
It could be conflicting with a TTY service?
1 Like
3 Likes
Thanks for the article Ironfoot. I followed the last line of the bug report and restarted but it still didn't work for me.
It's 2020 now and I can confirm this bug for Ubuntu 18.04.3 LTS, too.
Calling "/lib/systemd/systemd-sysv-install enable lightdm" directly worked for me.
Oddly, logged into my account on TTY, ran startx, and now found the dark theme is somewhat broken (not consistent on Firefox) on this laptop. I'm not sure if there is a link between this and the LightDM problems I've had today, but I'd figure I'd mention it just in case there is. On my production machine running Ubuntu MATE 24.04 LTS, the dark theme is consistent across all apps (GTK3 and GTK4).
I don't want to sound too down on Ubuntu MATE since I absolutely love it and it's the only Linux distribution I've used for a long period (i.e., longer than 1-2 months since I switched to Linux). It's just unfortunate I've ran into these problems on 24.10, and I'm grateful I keep my production machine on LTS.
Many thanks,
Jaymo
1 Like
Hi Stephen,
Is there a way I can check?
Jaymo