Hello all,
I'm about to build a custom Debian with Budgie and some other stuff pre-installed.
Now I'm facing one issue:
After setting custom dconf defaults like described here booting the live system gets stuck at the systemd service live-config.service.
I've used this commit as a reference.
The problem is inside /lib/live/config/1040-gnome-screensaver (part of the package live-config) where it gets stuck at line 44 (dbus-run-session command):This issue only happens with those custom dconf defaults/profile. Without includes.chroot/etc/dconf the issue is gone.
As you can see I've commented out that line and placed it in includes.chroot/lib/live/config/1040-gnome-screensaver to overwrite the file provided by that package to see if it boots fine then.
Since it does I know that something's wrong with that command not exiting at all.
I also have the same hook like here.
So, now I know where the issue is coming from but I don't know the reason and also not how to solve it properly.
Best regards,
Danny.
I'm about to build a custom Debian with Budgie and some other stuff pre-installed.
Now I'm facing one issue:
After setting custom dconf defaults like described here booting the live system gets stuck at the systemd service live-config.service.
I've used this commit as a reference.
The problem is inside /lib/live/config/1040-gnome-screensaver (part of the package live-config) where it gets stuck at line 44 (dbus-run-session command):
Code:
#!/bin/sh. /lib/live/config.sh## live-config(7) - System Configuration Components## Copyright (C) 2016-2020 The Debian Live team## Copyright (C) 2006-2015 Daniel Baumann <mail@daniel-baumann.ch>#### This program comes with ABSOLUTELY NO WARRANTY; for details see COPYING.## This is free software, and you are welcome to redistribute it## under certain conditions; see COPYING for details.#set -eCmdline (){# Reading kernel command linefor _PARAMETER in ${LIVE_CONFIG_CMDLINE}docase "${_PARAMETER}" inlive-config.username=*|username=*)LIVE_USERNAME="${_PARAMETER#*username=}";;esacdone}Init (){# Checking if package is installed or already configuredif ! pkg_is_installed "gnome-screensaver" || \ component_was_executed "gnome-screensaver"thenexit 0fiecho -n " gnome-screensaver"}Config (){# Disabling to lock the screen when the screensaver goes active.#sudo -u "${LIVE_USERNAME}" dbus-run-session -- gsettings set org.gnome.desktop.screensaver lock-enabled false# Creating state filetouch /var/lib/live/config/gnome-screensaver}CmdlineInitConfigAs you can see I've commented out that line and placed it in includes.chroot/lib/live/config/1040-gnome-screensaver to overwrite the file provided by that package to see if it boots fine then.
Since it does I know that something's wrong with that command not exiting at all.
I also have the same hook like here.
So, now I know where the issue is coming from but I don't know the reason and also not how to solve it properly.
Best regards,
Danny.
Statistics: Posted by dtrunk90 — 2024-03-27 17:42 — Replies 0 — Views 20