[Solved] Booting into tty directly, $DBUS_SESSION_BUS_ADDRESS not set.

amixra · 2023-04-24 07:41:32

After last update when I rebooted, I was directly sent to tty interface. I was confused but I suddenly recalled that grub was updated in the last update but i didn't those 2 commands.

# grub-install ...
# grub-mkconfig ...

So I did that too and rebooted confidently but that didn't helped anyway. I checked arch wiki found `sytemctl set-default graphical.target` and rebooted with again full confidence.
But landed again into tty interface. I checked journalctl and found when I had shutdown last time after updating then I recalled some issue occured after shutting down I was into sddm which is not expected usually. Taken out that part exactly from logs

...
...
Apr 24 05:36:51 amit-dell systemd[1]: Reached target Unmount All Filesystems.
Apr 24 05:36:51 amit-dell sddm-greeter[209222]: Reading from "/usr/share/xsessions/awesome.desktop"
Apr 24 05:36:51 amit-dell sddm[623]: Message received from greeter: Login
Apr 24 05:36:51 amit-dell sddm[623]: Reading from "/usr/share/xsessions/awesome.desktop"
Apr 24 05:36:51 amit-dell sddm[623]: Reading from "/usr/share/xsessions/awesome.desktop"
Apr 24 05:36:51 amit-dell sddm[623]: Session "/usr/share/xsessions/awesome.desktop" selected, command: "awesome"
Apr 24 05:36:51 amit-dell sddm-helper[209530]: [PAM] Starting...
Apr 24 05:36:51 amit-dell sddm-helper[209530]: [PAM] Authenticating...
Apr 24 05:36:51 amit-dell sddm-helper[209530]: [PAM] Preparing to converse...
Apr 24 05:36:51 amit-dell sddm-helper[209530]: [PAM] Conversation with 1 messages
Apr 24 05:36:51 amit-dell sddm-helper[209530]: [PAM] authenticate: Authentication failure
Apr 24 05:36:51 amit-dell sddm-helper[209530]: [PAM] returning.
Apr 24 05:36:51 amit-dell sddm[623]: Authentication error: "System is going down. Unprivileged users are not permitted to log in anymore. For technical details, see pam_nologin(8).\n">
Apr 24 05:36:51 amit-dell sddm-greeter[209222]: Message received from daemon: LoginFailed
Apr 24 05:36:51 amit-dell sddm-helper[209530]: [PAM] Ended.
Apr 24 05:36:51 amit-dell sddm[623]: Auth: sddm-helper exited with 1
Apr 24 05:36:51 amit-dell systemd[1]: lvm2-monitor.service: Deactivated successfully.
...
...

Last edited by amixra (2023-04-25 16:23:00)

amixra · 2023-04-24 07:43:49

I can come into graphical interface from tty by doing `sudo sddm` and then login as normal user but this adds an overhead.

amixra · 2023-04-24 14:44:44

Also after last update I have few things got broken like if I start few things which probably require some variables set then it simply fails. My soundcard is failing because pipewire or pulseaudio is failing because DBUS_SESSION_BUS_ADDRESS is not set. I found I need to do `export $(dbus-launch)` but that doesn't makes soundcard comeback.
Also I launched spectacle, it failed so I launched through konsole, following are the logs and second time it launched

$ spectacle
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-amit'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-amit'
kf.dbusaddons: DBus session bus not found. To circumvent this problem try the following command (with bash):
export $(dbus-launch)
$ export $(dbus-launch) 
$ spectacle                                                                                     
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-amit'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-amit'
kf.kirigami: Failed to find a Kirigami platform plugin
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.1'
Error querying plasma version "org.freedesktop.DBus.Error.ServiceUnknown" "The name org.kde.plasmashell was not provided by any .service files"

seth · 2023-04-24 15:04:48

amit-dell sddm[623]: Authentication error: "System is going down. Unprivileged users are not permitted to log in anymore. For technical details, see pam_nologin(8).\n">

stat /var/run/nologin /etc/nologin

export $(dbus-launch)

Don't do that.

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

amixra · 2023-04-24 18:27:35

seth wrote:

amit-dell sddm[623]: Authentication error: "System is going down. Unprivileged users are not permitted to log in anymore. For technical details, see pam_nologin(8).\n">

stat /var/run/nologin /etc/nologin

I too was highlighting that thing but forgot to mention there are no files for me.

$ stat /var/run/nologin /etc/nologin                                                     
stat: cannot statx '/var/run/nologin': No such file or directory
stat: cannot statx '/etc/nologin': No such file or directory

seth wrote:

Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st

http://0x0.st/HKac.txt The session was currently running and hence quite long

seth · 2023-04-24 20:21:24

That journal doesn't cover the SDDM failure b/c of "loglevel=3"

amixra · 2023-04-25 06:18:10

Yup I was aware of the fact the error I showed on the top was taken from last working as expected system. After that Getty simply comes over after plymouth instead of graphical target.

amixra · 2023-04-25 06:22:16

Few other things also seems broken like safeeyes is not working anymore probably it also depends upon some variable and showing next break at a time which is already passed. Seems it is unaware of current time. There is some meta problem which is resulting in these symptoms. I am just trying to put more of them here.

seth · 2023-04-25 06:34:55

Please post the journal of a boot that actually covers the SDDM failure

amixra · 2023-04-25 07:43:45

journalctl --since="2023-04-23 23:26:00" --until="2023-04-24 06:00:00"

This day actually system was already running from a long time so I have filtered the majority of the process from where this all started on 23 april from "23:26:36" I ran

sudo pacman -syu

from logs:

Apr 23 23:26:36 amit-dell sudo[127921]:     amit : TTY=pts/0 ; PWD=/home/amit/codelib/web/auto-quartet ; USER=root ; COMMAND=/usr/bin/pacman -Syu

This started fetching core,community db etc. and downloading stuff happening
Around 00:25, probably(not sure) I pressed CTRL+C because it was still downloading.

Apr 24 00:25:06 amit-dell sudo[127921]: pam_unix(sudo:session): session closed for user root

I restarted the download with

sudo pacman -Syu && shutdown now

I just went to sleep thinking it will shutdown when the process would be done but I woke up to see

Packages (x) package names etc................................. 

Total Download Size:   abc MiB
Total Installed Size:  xyz MiB
Net Upgrade Size:       x MiB

:: Proceed with installation? [Y/n]

So actually installation and update started in front of me in the morning. I pressed "Y" but there were some errors in between for fetching from various mirrors. So I started it again and you would find update command again at

Apr 24 05:10:52 amit-dell sudo[176779]:     amit : TTY=pts/0 ; PWD=/home/amit/codelib/web/auto-quartet ; USER=root ; COMMAND=/usr/bin/pacman -Syu

update is happening and during that a core dump occurs and I get logged out.

Apr 24 05:25:37 amit-dell systemd-coredump[182729]: Process 637 (Xorg) of user 0 dumped core.
                                                    
                                                    Stack trace of thread 637:
                                                    #0  0x00007f8f711998ec n/a (libc.so.6 + 0x878ec)
                                                    #1  0x00007f8f7114aea8 raise (libc.so.6 + 0x38ea8)
                                                    #2  0x00007f8f7113453d abort (libc.so.6 + 0x2253d)
                                                    #3  0x0000558c88a9ac70 OsAbort (Xorg + 0x153c70)
                                                    #4  0x0000558c88a9c0d3 FatalError (Xorg + 0x1550d3)
                                                    #5  0x0000558c88aa2a39 n/a (Xorg + 0x15ba39)
                                                    #6  0x00007f8f7114af50 n/a (libc.so.6 + 0x38f50)
                                                    #7  0x00007f8f659c2039 n/a (/usr/lib/xorg/modules/input/libinput_drv.so (deleted) + 0xf039)
                                                    ELF object binary architecture: AMD x86-64
Apr 24 05:25:37 amit-dell systemd[1]: systemd-coredump@0-182718-0.service: Deactivated successfully.

Then I came from somewhere glanced the screen and then logged in (since It was on sddm interface)

Apr 24 05:35:05 amit-dell sddm-greeter[183175]: Reading from "/usr/share/xsessions/awesome.desktop"
Apr 24 05:35:05 amit-dell sddm[623]: Message received from greeter: Login
Apr 24 05:35:05 amit-dell sddm[623]: Reading from "/usr/share/xsessions/awesome.desktop"
Apr 24 05:35:05 amit-dell sddm[623]: Reading from "/usr/share/xsessions/awesome.desktop"
Apr 24 05:35:05 amit-dell sddm[623]: Session "/usr/share/xsessions/awesome.desktop" selected, command: "awesome"
Apr 24 05:35:05 amit-dell sddm-helper[208590]: [PAM] Starting...
Apr 24 05:35:05 amit-dell sddm-helper[208590]: [PAM] Authenticating...

http://0x0.st/HKuU.txt

Last edited by amixra (2023-04-25 07:46:17)

amixra · 2023-04-25 07:51:32

One thing to note here is that coredump is not new because it happens most of times I update from when I had started using ALHP.GO repository. Currently I am not using that but there are many packages from that repository still there because there isn't any update released from official repositories so those are still from that repository.

V1del · 2023-04-25 08:02:34

Run a

pacman -Syuu

to downgrade/upgrade everything to a consistent state.

amixra · 2023-04-25 08:15:50

Ran again got logged out probably a core dump again but now I feel some of the things got fixed as after getting logged out first tty interface came up but it automatically sent me to sddm which was not happening.
I logged in back. I wasn't able to see that downgrade happening. Used following command

$ ps aux | grep pacman
root       31489  0.0  0.0  17832  6616 ?        S    13:24   0:00 sudo pacman -Suuy
root       31490  7.5  2.4 281936 197364 ?       S    13:24   1:27 pacman -Suuy
root       62348  0.0  0.0   5780  2004 ?        S    13:41   0:00 xargs -r pacman -Qql
amit       63429  0.0  0.0   6568  2412 pts/0    S+   13:43   0:00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn pacman

So it's running. Out of context here but may i ask is there anyway to start getting logs of a process into stdout from there pid?

amixra · 2023-04-25 08:29:28

rebooted nothing happened it's all same way. TTY then sudo sddm then login. soundcard can't be detected.

Edit: however, alsamixer can list the soundcards. I doubt in last update there were major upgrades in kde packages probably those are itself the reasons for errors.

Last edited by amixra (2023-04-25 08:41:43)

V1del · 2023-04-25 08:37:24

For sound cards to be detected you need a proper login and dbus session which you get if the thing is started via systemd. you also need to not export dbus-launch anywhere. Start the system normally, make the login fail, repost the full output of journalctl -b (without loglevel=3 set on your cmdline)

amixra · 2023-04-25 08:59:46

Here it is, I entered wrong password first to make the login fail then entered correct password next time.
http://0x0.st/HKSq.txt

seth · 2023-04-25 13:47:49

There's no effort nor failure to start sddm before you

Apr 25 14:17:49 amit-dell sudo[1353]:     amit : TTY=tty1 ; PWD=/home/amit ; USER=root ; COMMAND=/usr/bin/sddm

systemctl status sddm
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

amixra · 2023-04-25 15:10:21

ohh yess...
sddm was disabled but how? why?
I enabled it and rebooted everything seems to work. All above symptoms gone. Thanks.

BUT WHY THAT HAPPENED ON THE FIRST PLACE?

So I also had plymouth from around more than 3-4 months and I have made no change not even changed theme or anything. So I recalled that there was some more configuration required to allow the transition from plymouth to sddm. During the process I found that /etc/systemd/system/display-manager.service was a broken symlink to /usr/lib/systemd/system/sddm-plymouth.service.

amixra · 2023-04-25 15:15:14

And probably that was as a result of downgrade? But the problem was before that too.

seth wrote:

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

However, system is now fixed and my streak of not using timeshift ever is still maintained. Still I am just putting the output to make sure everything looks good to you

bluetooth.service                        | bluetooth.target.wants
cronie.service                           | multi-user.target.wants
cups.path                                | multi-user.target.wants
cups.service                             | multi-user.target.wants
cups.service                             | printers.target.wants
cups.socket                              | sockets.target.wants
dbus-fi.w1.wpa_supplicant1.service       | system
dbus-org.bluez.service                   | system
dbus-org.freedesktop.home1.service       | system
dbus-org.freedesktop.ModemManager1.service | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.thermald.service    | system
dbus-org.freedesktop.timesync1.service   | system
default.target                           | system
disable-transparent-huge-pages.service   | basic.target.wants
display-manager.service                  | system
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
gnome-keyring-daemon.socket              | sockets.target.wants
ModemManager.service                     | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-media-session.service           | pipewire.service.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
set-cfs-tweaks.service                   | hibernate.target.wants
set-cfs-tweaks.service                   | hybrid-sleep.target.wants
set-cfs-tweaks.service                   | multi-user.target.wants
set-cfs-tweaks.service                   | suspend.target.wants
set-cfs-tweaks.service                   | suspend-then-hibernate.target.wants
systemd-homed-activate.service           | systemd-homed.service.wants
systemd-homed.service                    | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants
systemd-userdbd.socket                   | sockets.target.wants
thermald.service                         | multi-user.target.wants
tlp.service                              | multi-user.target.wants
wpa_supplicant.service                   | multi-user.target.wants
xdg-user-dirs-update.service             | default.target.wants

amixra · 2023-04-25 15:17:48

One more thing in a hope to try fixing it I felt I need to enable systemd-homed which wasn't before ig. So should I disable it back? Thanks.

seth · 2023-04-25 15:31:34

Unless you've figured what anyone could reasonably need homed for and you didn't convert your logins, you can safely disable it again.
Also disable wpa-supplicant, NM activates that itself.
You somehow have cups.service twice.

BUT WHY THAT HAPPENED ON THE FIRST PLACE?

During the process I found that /etc/systemd/system/display-manager.service was a broken symlink to /usr/lib/systemd/system/sddm-plymouth.service.

So you kinda replaced sddm w/ sddm-pymouth, that was broken and you probably just removed the symlink altogether, leaving no instance of SDDM enabled?

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Arch Linux

#1 2023-04-24 07:41:32

[Solved] Booting into tty directly, $DBUS_SESSION_BUS_ADDRESS not set.

#2 2023-04-24 07:43:49

Re: [Solved] Booting into tty directly, $DBUS_SESSION_BUS_ADDRESS not set.

#3 2023-04-24 14:44:44

Re: [Solved] Booting into tty directly, $DBUS_SESSION_BUS_ADDRESS not set.

#4 2023-04-24 15:04:48

Re: [Solved] Booting into tty directly, $DBUS_SESSION_BUS_ADDRESS not set.

#5 2023-04-24 18:27:35

Re: [Solved] Booting into tty directly, $DBUS_SESSION_BUS_ADDRESS not set.

#6 2023-04-24 20:21:24

Re: [Solved] Booting into tty directly, $DBUS_SESSION_BUS_ADDRESS not set.

#7 2023-04-25 06:18:10

Re: [Solved] Booting into tty directly, $DBUS_SESSION_BUS_ADDRESS not set.

#8 2023-04-25 06:22:16

Re: [Solved] Booting into tty directly, $DBUS_SESSION_BUS_ADDRESS not set.

#9 2023-04-25 06:34:55

Re: [Solved] Booting into tty directly, $DBUS_SESSION_BUS_ADDRESS not set.

#10 2023-04-25 07:43:45

Re: [Solved] Booting into tty directly, $DBUS_SESSION_BUS_ADDRESS not set.

#11 2023-04-25 07:51:32

Re: [Solved] Booting into tty directly, $DBUS_SESSION_BUS_ADDRESS not set.

#12 2023-04-25 08:02:34

Re: [Solved] Booting into tty directly, $DBUS_SESSION_BUS_ADDRESS not set.

#13 2023-04-25 08:15:50

Re: [Solved] Booting into tty directly, $DBUS_SESSION_BUS_ADDRESS not set.

#14 2023-04-25 08:29:28

Re: [Solved] Booting into tty directly, $DBUS_SESSION_BUS_ADDRESS not set.

#15 2023-04-25 08:37:24

Re: [Solved] Booting into tty directly, $DBUS_SESSION_BUS_ADDRESS not set.

#16 2023-04-25 08:59:46

Re: [Solved] Booting into tty directly, $DBUS_SESSION_BUS_ADDRESS not set.

#17 2023-04-25 13:47:49

Re: [Solved] Booting into tty directly, $DBUS_SESSION_BUS_ADDRESS not set.

#18 2023-04-25 15:10:21

Re: [Solved] Booting into tty directly, $DBUS_SESSION_BUS_ADDRESS not set.

#19 2023-04-25 15:15:14

Re: [Solved] Booting into tty directly, $DBUS_SESSION_BUS_ADDRESS not set.

#20 2023-04-25 15:17:48

Re: [Solved] Booting into tty directly, $DBUS_SESSION_BUS_ADDRESS not set.

#21 2023-04-25 15:31:34

Re: [Solved] Booting into tty directly, $DBUS_SESSION_BUS_ADDRESS not set.

Board footer