Page 1 of 1
Budgie works in Sysvinit in Devuan, but not in Sysvinit in MX-Linux.
Posted: Mon Feb 24, 2025 5:27 am
by Senpai
Hi:
I find it strange that the “logout” of Budgie works perfectly with SysVinit in Devuan 5.0 and does not work with Sysvinit in MX-Linux 23...
Where can I look to find out what could be the cause or the difference?
Best regards
Code: Select all
Snapshot created on: 20240126_1812
System:
Kernel: 6.1.0-31-amd64 [6.1.128-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-31-amd64 root=UUID=<filter> ro quiet splash
Desktop: Budgie v: 10.7.1 info: budgie-panel wm: budgie-wm dm: LightDM v: 1.32.0 Distro: Senpai
Respin MX-CLI-23.5_x64 Libretto febrero 22 2025 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Kvm System: QEMU product: Standard PC (Q35 + ICH9, 2009) v: pc-q35-7.2
serial: <superuser required> Chassis: type: 1 v: pc-q35-7.2 serial: <superuser required>
Mobo: N/A model: N/A serial: N/A BIOS: SeaBIOS v: 1.16.2-debian-1.16.2-1 date: 04/01/2014
CPU:
Info: model: AMD Ryzen 5 5500 bits: 64 type: SMP arch: Zen 3 gen: 4 level: v3 note: check
built: 2021-22 process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0
microcode: 0xA50000D
Topology: cpus: 6x cores: 1 smt: <unsupported> cache: L1: 6x 128 KiB (768 KiB)
desc: d-1x64 KiB; i-1x64 KiB L2: 6x 512 KiB (3 MiB) desc: 1x512 KiB L3: 6x 16 MiB (96 MiB)
desc: 1x16 MiB
Speed (MHz): avg: 3600 min/max: N/A cores: 1: 3600 2: 3600 3: 3600 4: 3600 5: 3600 6: 3600
bogomips: 43199
Flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow mitigation: safe RET, no microcode
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: disabled; RSB
filling; PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Red Hat Virtio 1.0 GPU driver: virtio-pci v: 1 alternate: virtio_pci ports:
active: Virtual-1 empty: none bus-ID: 00:01.0 chip-ID: 1af4:1050 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: budgie-wm driver:
X: loaded: modesetting unloaded: fbdev,vesa dri: swrast gpu: virtio-pci display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.00x11.26") s-diag: 583mm (22.95")
Monitor-1: Virtual-1 model: QEMU Monitor built: 2014 res: 1920x1080 hz: 60 dpi: 150 gamma: 1.2
size: 325x203mm (12.8x7.99") diag: 383mm (15.1") ratio: 16:10 modes: max: 1280x800 min: 640x480
API: OpenGL v: 4.5 Mesa 22.3.6 renderer: llvmpipe (LLVM 15.0.6 256 bits) direct-render: Yes
Audio:
Device-1: Intel 82801I HD Audio vendor: Red Hat QEMU Virtual Machine driver: snd_hda_intel
v: kernel bus-ID: 00:1b.0 chip-ID: 8086:293e class-ID: 0403
API: ALSA v: k6.1.0-31-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Red Hat Virtio 1.0 network driver: virtio-pci v: 1 modules: virtio_pci pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: N/A bus-ID: 01:00.0 chip-ID: 1af4:1041 class-ID: 0200
IF-ID-1: eth0 state: up speed: -1 duplex: unknown mac: <filter>
Drives:
Local Storage: total: 20 GiB used: 7.75 GiB (38.8%)
ID-1: /dev/vda maj-min: 254:0 model: N/A size: 20 GiB block-size: physical: 512 B
logical: 512 B speed: <unknown> type: N/A serial: N/A scheme: MBR
SMART Message: Unknown smartctl error. Unable to generate data.
Partition:
ID-1: / raw-size: 20 GiB size: 19.52 GiB (97.59%) used: 7.75 GiB (39.7%) fs: ext4 dev: /dev/vda1
maj-min: 254:1
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon or lm-sensors.
Repos:
Packages: pm: dpkg pkgs: 1944 libs: 933 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm pkgs: 0
pm: flatpak pkgs: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://debian.redimadrid.es/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://debian.redimadrid.es/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://ftp.cica.es/mirrors/Linux/MX-Packages/mx/repo/ bookworm main non-free
Info:
Processes: 245 Uptime: 0m wakeups: 12 Memory: 5.79 GiB used: 1004.5 MiB (17.0%) Init: SysVinit
v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: BIOS (legacy, CSM, MBR)
Re: Budgie works in Sysvinit in Devuan, but not in Sysvinit in MX-Linux.
Posted: Mon Feb 24, 2025 5:29 am
by Eadwine Rose
Can you start it in the terminal, see if anything interesting pops up in there.
Re: Budgie works in Sysvinit in Devuan, but not in Sysvinit in MX-Linux.
Posted: Mon Feb 24, 2025 6:54 am
by Senpai
Eadwine Rose wrote: ↑Mon Feb 24, 2025 5:29 am
Can you start it in the terminal, see if anything interesting pops up in there.
Hi:
logout does not run from terminal to see something, when logging out of MX sysvinit and start again only comes out the error of the image and does not let you look at anything else, with systemd does not happen...
I can only pull up the errors from the previous session in ".xsession-errors.old", It seems that there are errors in the call of “gnome-session” because it looks for systemd, but no idea what to look for
Code: Select all
Xsession: X session started for manuel at lun 24 feb 2025 12:32:51 CET
dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/manuel/.Xauthority
dbus-update-activation-environment: setting XDG_CURRENT_DESKTOP=Budgie:GNOME
localuser:manuel being added to access control list
dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: systemd --user not found, ignoring --systemd argument
dbus-update-activation-environment: setting USER=manuel
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting HOME=/home/manuel
dbus-update-activation-environment: setting DESKTOP_SESSION=budgie-desktop
dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/dbus-LYItAp6FVQ,guid=6618e70373805c6a72b5ee4767bc58e3
dbus-update-activation-environment: setting LOGNAME=manuel
dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
dbus-update-activation-environment: setting PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
dbus-update-activation-environment: setting GDM_LANG=es_ES.utf8
dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session6
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting LANG=es_ES.UTF-8
dbus-update-activation-environment: setting XDG_CURRENT_DESKTOP=Budgie:GNOME
dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=budgie-desktop
dbus-update-activation-environment: setting XAUTHORITY=/home/manuel/.Xauthority
dbus-update-activation-environment: setting XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/manuel
dbus-update-activation-environment: setting SHELL=/usr/bin/bash
dbus-update-activation-environment: setting GDMSESSION=budgie-desktop
dbus-update-activation-environment: setting NO_AT_BRIDGE=1
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting QT_LOGGING_RULES=qt.qpa.xcb.warning=false
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting PWD=/home/manuel
dbus-update-activation-environment: setting XDG_DATA_DIRS=/home/manuel/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
VirtualBox Additions disabled, not in a Virtual Machine
gnome-session-check-accelerated: GL Helper exited with code 512
libEGL warning: DRI2: failed to authenticate
gnome-session-check-accelerated: GLES Helper exited with code 512
gnome-session-binary[11647]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
gnome-session-binary[11647]: WARNING: Could not parse desktop file magnus-autostart.desktop or it references a not found TryExec binary
discover_other_daemon: 1discover_other_daemon: 1discover_other_daemon: 1SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
(gsd-xsettings:11787): xsettings-plugin-WARNING **: 12:32:51.768: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist
(gsd-media-keys:11797): media-keys-plugin-WARNING **: 12:32:51.774: Unable to inhibit keypresses: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Permission denied
(gsd-usb-protection:11841): usb-protection-plugin-WARNING **: 12:32:51.782: Failed to get screen saver status: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.ScreenSaver was not provided by any .service files
(gsd-sharing:11794): sharing-plugin-WARNING **: 12:32:51.783: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
(gsd-sharing:11794): sharing-plugin-WARNING **: 12:32:51.783: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
(gsd-usb-protection:11841): usb-protection-plugin-WARNING **: 12:32:51.791: Failed to fetch USBGuard parameters: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.usbguard1 was not provided by any .service files
libmutter-Message: 12:32:52.247: Running Mutter(Budgie) (using mutter 43.8) as a X11 window and compositing manager
(budgie-wm:11939): libmutter-WARNING **: 12:32:52.391: Called enable_unredirect_for_display while unredirection is enabled.
** Message: 12:32:52.392: ibus.vala:47: ibus-daemon unsupported on this system
Window manager warning: Failed to parse saved session file: Falló al abrir el archivo «/home/manuel/.config/mutter/sessions/10b3623339a0318a40174039677168146600000116470000.ms»: No existe el fichero o el directorio
(gsd-power:11810): power-plugin-WARNING **: 12:32:52.424: No logind found: GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: Unknown object '/org/freedesktop/login1/session/auto'.
(gsd-media-keys:11797): media-keys-plugin-WARNING **: 12:32:52.438: Failed to grab accelerator for keybinding settings:hibernate
(gsd-media-keys:11797): media-keys-plugin-WARNING **: 12:32:52.438: Failed to grab accelerator for keybinding settings:playback-random
(gsd-media-keys:11797): media-keys-plugin-WARNING **: 12:32:52.438: Failed to grab accelerator for keybinding settings:rotate-video-lock
(gsd-media-keys:11797): media-keys-plugin-WARNING **: 12:32:52.438: Failed to grab accelerator for keybinding settings:playback-repeat
(budgie-wm:11939): libmutter-WARNING **: 12:32:52.447: Failed to create colord device for 'xrandr-Red Hat, Inc.-QEMU Monitor-0x00000000': failed to obtain org.freedesktop.color-manager.create-device auth
** (budgie-panel:11969): CRITICAL **: 12:32:52.754: notifications_view.vala:184: Unable to connect to notifications dispatcher: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.budgie_desktop.Notifications was not provided by any .service files
** (budgie-panel:11969): WARNING **: 12:32:52.755: OverlayMenus.vala:128: Unable to connect to Budgie XDGDirTracker: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.buddiesofbudgie.XDGDirTracker was not provided by any .service files
** (budgie-panel:11969): CRITICAL **: 12:32:52.760: budgie_app_sound_control_construct: assertion 'c_primary != NULL' failed
(budgie-panel:11969): GLib-GObject-CRITICAL **: 12:32:52.760: g_object_ref_sink: assertion 'G_IS_OBJECT (object)' failed
(budgie-panel:11969): GLib-GObject-WARNING **: 12:32:52.761: invalid (NULL) pointer instance
(budgie-panel:11969): GLib-GObject-CRITICAL **: 12:32:52.761: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(budgie-panel:11969): Gvc-CRITICAL **: 12:32:52.761: gvc_mixer_stream_get_volume: assertion 'GVC_IS_MIXER_STREAM (stream)' failed
(budgie-panel:11969): Gvc-CRITICAL **: 12:32:52.761: gvc_mixer_stream_get_is_muted: assertion 'GVC_IS_MIXER_STREAM (stream)' failed
Unable to initiate PolKit: No session for pid 11997gnome-session-binary[11647]: WARNING: App 'org.buddiesofbudgie.BudgiePolkit.desktop' exited with code 1
Unable to initiate PolKit: No session for pid 12007gnome-session-binary[11647]: WARNING: App 'org.buddiesofbudgie.BudgiePolkit.desktop' exited with code 1
gnome-session-binary[11647]: WARNING: App 'org.buddiesofbudgie.BudgiePolkit.desktop' respawning too quickly
init [5]
start pipewire
** (budgie-extras-daemon:12030): WARNING **: 12:32:53.046: Binding '<Alt>grave' failed!
** (budgie-extras-daemon:12030): WARNING **: 12:32:53.053: Binding '<Shift><Alt>grave' failed!
delay wireplumber server start 2 seconds
configurable in /home/manuel/.config/MX-Linux/pipewire-start.conf
blueman-applet 12.32.53 WARNING PluginManager:151 __load_plugin: Not loading PPPSupport because its conflict has higher priority
blueman-applet 12.32.53 WARNING PluginManager:151 __load_plugin: Not loading DhcpClient because its conflict has higher priority
blueman-applet 12.32.53 WARNING DiscvManager:119 update_menuitems: warning: Adapter is None
(budgie-wm:11939): libmutter-WARNING **: 12:32:54.971: Invalid temperature from gsd-color: 0 K
(process:12045): ayatana-indicator-application-service-WARNING **: 12:32:55.058: Name Lost
Could not acquire name
** (budgie-extras-daemon:12030): CRITICAL **: 12:32:55.070: budgie_extras_DaemonNameLost: assertion 'conn != NULL' failed
Authorization required, but no authorization protocol specified
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
Cleanup-notifier: available space at '/boot' 10997 MiB
Re: Budgie works in Sysvinit in Devuan, but not in Sysvinit in MX-Linux.
Posted: Mon Feb 24, 2025 8:42 am
by dolphin_oracle
more exactly, it does not work with the systemd-shim mashup in on MX when run under sysVinit.
since devuan seems to use debian's budgie packages, I would guess the difference is that.
Re: Budgie works in Sysvinit in Devuan, but not in Sysvinit in MX-Linux.
Posted: Mon Feb 24, 2025 2:32 pm
by Senpai
dolphin_oracle wrote: ↑Mon Feb 24, 2025 8:42 am
more exactly, it does not work with the systemd-shim mashup in on MX when run under sysVinit.
since devuan seems to use debian's budgie packages, I would guess the difference is that.
Hi:
Well the only thing that doesn't work is the logout,
, everything else seems to work, suspend, hibernate, reboot and shutdown.
Re: Budgie works in Sysvinit in Devuan, but not in Sysvinit in MX-Linux.
Posted: Mon Feb 24, 2025 2:40 pm
by AVLinux
@Senpai
Is it a problem to just use systemd with certain Desktops? Most common DE's are developed on and focus on systemd, obviously some (especially Window Managers) are more open to a choice and others are not... As an example I use Enlightenment which Debian sets up with power and system control options for systemd by default, I could go in and force it to work with sysvinit but if the developer is working with a focus on systemd and the upstream Distributor is gearing it to systemd why make trouble for yourself..? MX build-iso tools can now accommodate creating systemd-only ISO's, I would assume that Snapshot can do this as well with it's custom templates?
I agree choices are nice to have when either way will work equally well, but I also think certain DE's are going not to make that easy and it will only get worse especially as they evolve toward Wayland.. I understand Wayland alone is not dependent on systemd but I still think there will be a correlation.
Re: Budgie works in Sysvinit in Devuan, but not in Sysvinit in MX-Linux.
Posted: Tue Feb 25, 2025 5:21 am
by dreamer
AVLinux wrote: ↑Mon Feb 24, 2025 2:40 pm
I understand Wayland alone is not dependent on systemd but I still think there will be a correlation.
This is also how I see it. Most X.org window managers and compositors were developed in a time when systemd didn't exist so if there is a systemd dependency it has been added. Wayland compositors were developed in a time when systemd had maybe 80 % "market share". Anyway, I try to stay away from Wayland for the time being.
@AVLinux You described it better, lol...
Re: Budgie works in Sysvinit in Devuan, but not in Sysvinit in MX-Linux.
Posted: Tue Feb 25, 2025 6:04 am
by Senpai
AVLinux wrote: ↑Mon Feb 24, 2025 2:40 pm
@Senpai
Is it a problem to just use systemd with certain Desktops? Most common DE's are developed on and focus on systemd, obviously some (especially Window Managers) are more open to a choice and others are not... As an example I use Enlightenment which Debian sets up with power and system control options for systemd by default, I could go in and force it to work with sysvinit but if the developer is working with a focus on systemd and the upstream Distributor is gearing it to systemd why make trouble for yourself..? MX build-iso tools can now accommodate creating systemd-only ISO's, I would assume that Snapshot can do this as well with it's custom templates?
I agree choices are nice to have when either way will work equally well, but I also think certain DE's are going not to make that easy and it will only get worse especially as they evolve toward Wayland.. I understand Wayland alone is not dependent on systemd but I still think there will be a correlation.
Hi:
Of course you are right, it is no problem to remove sysvinit to make Budgie work well in MX, the MX developers make it easy with “systemd-sysv”, once again hats off to their work, their ideas and their tools...
In fact I did it in my respin mix of MX-Linux and Parrot-OS, but I think most of us who use MX do it because it gives the possibility to choose something different to Systemd and still keep Debian as a base...
That said, and as in principle only seems to fail the logout, I was curious to know if it was “simple” to fix it to continue keeping that possibility in this DE as it seems to me a nice, modern and not too consuming GTK option, as Mate seems to be a little behind with Wayland “for the moment”.
Best regards
Re: Budgie works in Sysvinit in Devuan, but not in Sysvinit in MX-Linux.
Posted: Wed Feb 26, 2025 8:17 am
by dolphin_oracle
I didn't have a problem with "logout" on budgie under sysVinit.
installing budgie did remove Xfce, which I didn't realize was going to happen. will probably remove from "Popular Apps" for that reason.
Re: Budgie works in Sysvinit in Devuan, but not in Sysvinit in MX-Linux.
Posted: Wed Feb 26, 2025 8:42 am
by asqwerth
dolphin_oracle wrote: ↑Wed Feb 26, 2025 8:17 am
.....
installing budgie did remove Xfce, which I didn't realize was going to happen. will probably remove from "Popular Apps" for that reason.
Could it be how budgie is packaged in Debian, with some conflicting dependencies?
I've had XFCE and Budgie co-existing on one of my Manjaro installs since 2016 - I installed budgie onto a Manjaro xfce system. So at least in Arch-based systems they can live together. Display manager used is lightdm.
I have noticed that I can't logout from Budgie in that Manjaro install if I run Compiz in Budgie. But I take that as indicating that Budgie doesn't work perfectly with compiz as window manager.
Re: Budgie works in Sysvinit in Devuan, but not in Sysvinit in MX-Linux.
Posted: Wed Feb 26, 2025 10:13 am
by Senpai
dolphin_oracle wrote: ↑Wed Feb 26, 2025 8:17 am
I didn't have a problem with "logout" on budgie under sysVinit.
installing budgie did remove Xfce, which I didn't realize was going to happen. will probably remove from "Popular Apps" for that reason.
Curious..., It didn't uninstall anything for me because I installed it in an installation derived from the ISO I have without Fluxbox or DE, and directly installed from the main repository, not from Popular Applications, but I guess it will install the same packages.
Re: Budgie works in Sysvinit in Devuan, but not in Sysvinit in MX-Linux.
Posted: Wed Feb 26, 2025 10:45 am
by dolphin_oracle
Senpai wrote: ↑Wed Feb 26, 2025 10:13 am
dolphin_oracle wrote: ↑Wed Feb 26, 2025 8:17 am
I didn't have a problem with "logout" on budgie under sysVinit.
installing budgie did remove Xfce, which I didn't realize was going to happen. will probably remove from "Popular Apps" for that reason.
Curious..., It didn't uninstall anything for me because I installed it in an installation derived from the ISO I have without Fluxbox or DE, and directly installed from the main repository, not from Popular Applications, but I guess it will install the same packages.
the conflict is with the new libxfcewindowing libraries. so only affects us since moving to xfce 4.20.
@asqwerth manjaro being rolling it probably has libraries lined up better.
Re: Budgie works in Sysvinit in Devuan, but not in Sysvinit in MX-Linux.
Posted: Sun Mar 02, 2025 11:35 am
by macronus
I don't know enough about Sysvinit vs Systemd to issue any definitive statement about any underlying problem responsible for this budgie logout problem. If anything, the explanations offered here strike me as being more plausible than to blame this on budgie-screensaver not being installed which appears to be the explanation offered in the following github exchange:
https://github.com/solus-project/budgie ... ssues/2145
(Let me point out that this is from four years ago. Also that budgie-screensaver is not available anywhere within the MX Package Installer.)
I only bring this up because the OP might be able to test uninstalling budgie-screensaver from his working Devuan installation to see if this triggers the budgie logout problem confirming that this is indeed the cause.
Re: Budgie works in Sysvinit in Devuan, but not in Sysvinit in MX-Linux.
Posted: Sun Mar 02, 2025 1:42 pm
by Senpai
macronus wrote: ↑Sun Mar 02, 2025 11:35 am
I don't know enough about Sysvinit vs Systemd to issue any definitive statement about any underlying problem responsible for this budgie logout problem. If anything, the explanations offered here strike me as being more plausible than to blame this on budgie-screensaver not being installed which appears to be the explanation offered in the following github exchange:
https://github.com/solus-project/budgie ... ssues/2145
(Let me point out that this is from four years ago. Also that budgie-screensaver is not available anywhere within the MX Package Installer.)
I only bring this up because the OP might be able to test uninstalling budgie-screensaver from his working Devuan installation to see if this triggers the budgie logout problem confirming that this is indeed the cause.
Hi:
It does not seem to be the problem, budgie-screensaver, does not exist in Devuan either, instead there is gnome-screensaver, that gave me the idea to look at the differences between the two installations and looking for gnome-xxxx, I installed in MX-Budgie what was missing compared to Devuan-Budgie, but the result is the same, it still fails to logout in MX, so as dolphin_oracle says it seems that the problem is with “systemd-shim”.
Best regards