You are not logged in.
I did it wrong....I should prest ctrl+alt+F2 when LOGGED out. I will repeat it again.
Offline
The extra login was not needed but you found the problem at least, you see geoclue on session-1.scope?
It’s hanging the logout.
Only solution for that right now its to prevent it from launching.
You need to mask it’s desktop file:
As root:
If ‘stat /etc/xdg/autostart/geoclue-demo-agent.desktop’ does not fail.
Run ‘ln -sf /dev/null /etc/xdg/autostart/geoclue-demo-agent.desktop’
And do a fresh boot to see if the issue does not replicate anymore...
See the PID close to geoclue, the number?
Run as root ‘kill -9 (THE PID)‘
So your session properly closes and you can actually shutdown.
Last edited by GaKu999 (2020-07-24 19:00:22)
Offline
This should be it. Rebooted system. Then logged out. Then waited for a while and entered TTY2
And here is the output of "systemctl status" :
● arch-hp
State: running
Jobs: 0 queued
Failed: 0 units
Since: Fri 2020-07-24 20:49:03 CEST; 1min 37s ago
CGroup: /
├─user.slice
│ ├─user-966.slice
│ │ ├─user@966.service
│ │ │ ├─gvfs-daemon.service
│ │ │ │ ├─1184 /usr/lib/gvfsd
│ │ │ │ └─1189 /usr/lib/gvfsd-fuse /run/user/966/gvfs -f
│ │ │ ├─init.scope
│ │ │ │ ├─1159 /usr/lib/systemd/systemd --user
│ │ │ │ └─1160 (sd-pam)
│ │ │ ├─at-spi-dbus-bus.service
│ │ │ │ ├─1176 /usr/lib/at-spi-bus-launcher
│ │ │ │ ├─1182 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
│ │ │ │ └─1205 /usr/lib/at-spi2-registryd --use-gnome-session
│ │ │ └─dbus.service
│ │ │ └─1175 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
│ │ └─session-c1.scope
│ │ ├─1155 lightdm --session-child 18 21
│ │ └─1169 /usr/bin/lightdm-gtk-greeter
│ └─user-1000.slice
│ ├─user@1000.service
│ │ ├─init.scope
│ │ │ ├─549 /usr/lib/systemd/systemd --user
│ │ │ └─550 (sd-pam)
│ │ ├─pipewire.service
│ │ │ ├─787 /usr/bin/pipewire
│ │ │ └─793 exec pipewire-media-session
│ │ └─dbus.service
│ │ └─1139 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
│ ├─session-4.scope
│ │ ├─1211 login -- arch
│ │ ├─1212 -bash
│ │ └─1226 systemctl status
│ └─session-1.scope
│ └─689 /usr/lib/geoclue-2.0/demos/agent
├─init.scope
│ └─1 /sbin/init
└─system.slice
├─systemd-udevd.service
│ └─340 /usr/lib/systemd/systemd-udevd
├─polkit.service
│ └─660 /usr/lib/polkit-1/polkitd --no-debug
├─rtkit-daemon.service
│ └─730 /usr/lib/rtkit-daemon
├─bluetooth.service
│ └─472 /usr/lib/bluetooth/bluetoothd
├─wpa_supplicant.service
│ └─515 /usr/bin/wpa_supplicant -u -s -O /run/wpa_supplicant
├─lightdm.service
│ ├─ 444 /usr/bin/lightdm
│ ├─1144 /usr/lib/Xorg :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
│ └─1203 lightdm --session-child 14 21
├─systemd-journald.service
│ └─326 /usr/lib/systemd/systemd-journald
├─NetworkManager.service
│ └─428 /usr/bin/NetworkManager --no-daemon
├─lvm2-lvmetad.service
│ └─346 /usr/bin/lvmetad -f
├─upower.service
│ └─753 /usr/lib/upowerd
├─udisks2.service
│ └─652 /usr/lib/udisks2/udisksd
├─dbus.service
│ └─427 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
└─systemd-logind.service
└─430 /usr/lib/systemd/systemd-logind Offline
Well, I did "stat /etc/xdg/autostart/geoclue-demo-agent.desktop" and I had an output.
then I ran this 'Run ‘ln -sf /dev/null /etc/xdg/autostart/geoclue-demo-agent.desktop’
And then tried to find geolclue in htop to find the PID number....but couldn't, So i have tried to reboot normally. And it hangs there, can't reboot ...hard restart
Offline
Well, I did "stat /etc/xdg/autostart/geoclue-demo-agent.desktop" and I had an output.
then I ran this 'Run ‘ln -sf /dev/null /etc/xdg/autostart/geoclue-demo-agent.desktop’
And then tried to find geolclue in htop to find the PID number....but couldn't, So i have tried to reboot normally. And it hangs there, can't reboot ...hard restart
You had the PIDs from the previous output. 689...
Anyways if this fails to replicate remember to mark this as [SOLVED] by editing your first post and adding that to the tittle.
Offline
sudo kill -9 689
kill: sending signal to 689 failed: No such process
Offline
sudo kill -9 689
kill: sending signal to 689 failed: No such process
You already did a hard reset, why did you run a kill? Anyways, does it still hangs on shutdown? Is the geoclue-2.0/demo/agent being launched?
Offline
I didn't see this process there. But it is still hangs. I thing there is somthing wrong with my USB - I have 1 USB 3 and if I dont takeout the usb connector for my mouse then the rgub menu will not move. So every time I should reboot and take out that connector and them boot in. A
Offline
With geoclue out of the picture...
Do a fresh boot, login, wait a while and then shutdown, wait for the hang now, don’t do a hard reset, so the journal keeps something useful...
When it manages to poweroff, boot again and run “journalctl -b -1 |& curl -F 'f:1=<-' ix.io“.
Then post the link, so we may see what is happening now...
Offline
I don't think it will ever shutdown. It can hang there till battery dies.
Offline
I have changed the environment to KDE. The same stuff. No more mate. Reinstalled Arch. the same thing is happening
Offline