- Status Closed
- Percent Complete
- Task Type Bug Report
- Category Any
-
Assigned To
Emulatorman - Operating System Hyperbola GNU/Linux-libre
- Severity High
- Priority High
- Reported Version Milky Way v0.2
- Due in Version Starfix
-
Due Date
Undecided
- Votes
- Private
Attached to Project: Packages
Opened by fablamar78 - 10/02/2018
Last edited by Emulatorman - 12/02/2018
Opened by fablamar78 - 10/02/2018
Last edited by Emulatorman - 12/02/2018
FS#656 - [lightdm] is running under foreground mode and causing service failure in another services
Since latest update, many of my service do not start automatically. (I can start them manually though)
This cause multiple errors at shutdown as well.
udev [ started ] localmount [ started ] dbus [ started ] elogind [ started ] NetworkManager [ started ] syslog-ng [ started ] acpid [ started ] dhcpcd [ started ] avahi-daemon [ started ] netmount [ started ] lightdm [ starting ] alsasound [ stopped ] avahi-dnsconfd [ stopped ] cronie [ stopped ] cupsd [ stopped ] fuse [ stopped ] ntpd [ stopped ] libvirtd [ stopped ] openrc-settingsd [ stopped ] sshd [ stopped ] thinkfan [ stopped ] local [ stopped ] agetty.tty5 [ stopped ] agetty.tty3 [ stopped ] agetty.tty6 [ stopped ] agetty.tty4 [ stopped ] agetty.tty2 [ stopped ] agetty.tty1 [ stopped ] Dynamic Runlevel: hotplugged Dynamic Runlevel: needed/wanted modules-load [ started ] lvmetad [ started ]
Before dbus update, everything was working fine.
Thanks for your help
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
OpenRC shutdown log :
I've just removed the systemd-sysusers file in the latest revision [0] , so i suppose you are using systemd-sysusers support since it generates a temporary dbus user in memory under systemd way.
Some distros such as Parabola and Artix are supporting systemd-sysusers through opensysusers and systemd-tmpfiles through opentmpfiles for their OpenRC version, however Hyperbola hasn't plans to support them since we are using from install files or from our filesystem package that contains dbus user added in passwd by default [1] or through OpenRC init scripts. The main reason about it is that Hyperbola Project follows the Unix way like the old times, not the systemd one.
If you come from Artix or Parabola, then you are using opensysusers/opentmpfiles package. Currently, i'm removing all systemd-sysusers and systemd-tmpfiles from all packages distributed by Hyperbola in the v0.2 version and re-adapting like the old times.
BTW, did you run pacdiff to compare changes between your passwd file and our one distributed through filesystem package? I mean it because all Arch-based distros migrated their users and groups under the systemd way. [2]
Perhaps you have remaining packages and configurations adapted from the previous distro yet. To check orphan packages, run:
Thanks for your answer. I installed Hyperbola straight from the official iso (Milky Way v0.2.2) Unfortunately, it doesn't solve the issue.
No orphans as well.
Is there additional logs I can provide ?
For now, I reverted back to previous dbus version and it works fine.
It's a strange bug, since i can't replicate that (i've upgraded all machines and it works well) please, paste here your runlevels configuration.
To do it, run:
Then, paste your pacman.conf here to confirm if signature verification is working well and a checksum about your dbus package downloaded in /var/pacman/cache, eg:
It should be the result:
x86_64:
i686:
Thanks.
As requested, with dbus-1.10.18-1.hyperbola4-x86_64 :
rc-update –all -v
NetworkManager | default acpid | default agetty | agetty.tty1 | default agetty.tty2 | default agetty.tty3 | default agetty.tty4 | default agetty.tty5 | default agetty.tty6 | default alsasound | default atd | auditd | avahi-daemon | default avahi-dnsconfd | default binfmt | boot bootmisc | boot brltty | ceph | consolefont | boot cpupower | cronie | default cups-browsed | cupsd | default dbus | default devfs | sysinit device-mapper | dhcpcd | default dmcrypt | boot dmesg | sysinit dmeventd | dnsmasq | elogind | default fancontrol | fsck | boot ftpd | fuse | default git-daemon | gpm | gssproxy | haveged | hddtemp | hdparm | hostapd | hostname | boot httpd | hwclock | boot ip6tables | iptables | irexec | keymaps | boot killprocs | shutdown krb5kadmind | krb5kdc | krb5kpropd | libvirt-guests | libvirtd | default lightdm | default lircd | lircmd | lm_sensors | sysinit local | default nonetwork localmount | boot default loopback | boot lvm | boot lvm-monitoring | lvmetad | lvmlockd | mdadm | mdraid | modules | boot modules-load | mount-ro | shutdown mpd | mtab | boot net-online | net.lo | boot netmount | default nfs | nfsclient | nscd | ntp-client | ntpd | default numlock | openrc-settingsd | default openvpn-client | openvpn-server | osclock | php-fpm | procfs | boot qemu-ga | rbdmap | root | boot rpc.gssd | rpc.idmapd | rpc.pipefs | rpc.statd | rpc.svcgssd | rpcbind | rsyncd | runsvdir | s6-svscan | saned | savecache | shutdown sensord | sntp | spice-vdagent | sshd | default stunnel | svn | swap | boot swclock | sysctl | boot sysfs | sysinit syslog-ng | default sysstat | termencoding | boot thinkfan | default tox-bootstrapd | udev | default sysinit udev-settle | udev-trigger | sysinit urandom | boot virtlockd | virtlogd | vnstatd | wpa_supplicant | xdm | xdm-setup |pacman.conf
dbus-1.10.18-1.hyperbola4-x86_64.pkg.tar.xz checksum is correct btw
rc-status -a
Affected services are in bold, they were working fine before upgrading dbus. (Automatically started with runlevel default)
Remove dbus from default runlevel since it is a needed/wanted service:
Then, reboot again:
No change unfortunately.
I've got replicate the issue adding LightDM service in default runlevel and i've paid attention that LightDM is starting under foreground mode:
... and causing the issue in the shutdown process:
The reason is related about my latest change in LightDM init script [0] because i thought LightDM could run in background mode by default, so i'm going to fixing it to push a new revision.
Confirmed 100% working on my 2 machines running Hyperbola, thank you !