Additions to Beryllium

linux_user · 2021-01-16 14:35:57

It is nice to see package suggestions for the next release. However, I suggest that we use a framework based on which the default packages can be selected. If I were to suggest such a framework, I would think as below.

Identity

BL stands for fast, lightweight, responsive, no-nonsense, terminal themed and keyboard driven distro. Most distros share these features, but don't share the terminal themed desktop UI. Therefore, most functional terminal based apps (ranger, tmux, cmus, tty-clock, mpv, etc...) and theming packages (conky and cmatrix) must be available out of the box.

Expectations

There are apps that linux users (not just BL users) are expecting from every distro, irrespective of _whether or not_ they are the lightest and fastest among their kind. Such packages like firefox and libreoffice, must be available out of the box.

Debian repos

When packages are no longer available in Debian, either it must be maintained in the BL repo or an alternative must be chosen. If the developers decide for an alternative, then a gtk based package must have preference over qt or other GUI framework based packages. Not that they will be inferior, but on some post in the forum I once read that GTK based package are a part of BL ecosystem, and I agree.

Exceptions

Then there are some packages that are just too good to ignore. They may not go along with BL, Linux or free software philosophies, but they outperform others that go with the said philosophies. Eg, Tixati. If are ever to include a torrent downloader out of the box, my vote will go for Tixati.

The others

These include choosing between many of the video players, text editors, music players, etc..., which the community can vote or we can go along how it has been done in BL historically.

=======

These are just mere suggestions. I hope I don't sound like someone trying to influence BL to become what I want it to be.

damo · 2021-01-16 15:40:42

linux_user wrote:

...
Identity
BL stands for fast, lightweight, responsive, no-nonsense, terminal themed and keyboard driven distro.
.....

I beg to differ.

bunsenlabs wrote:

BunsenLabs Linux Lithium is a distribution offering a light-weight and easily customizable Openbox desktop.

It has never been a "terminal themed and keyboard driven distro", although that has always been possible if the user chooses to use the capability.

linux_user · 2021-01-16 15:48:39

You're right Damo. It has never been officially offered as a 'terminal themed and keyboard driven distro'. But that's how I perceive the BL (crunchbang) interface to be. I am taking the liberty to say that most distro hoppers would perceive it the same way. To put it another way, if someone used to keybaords for tasks and likes a sleek interface, he/she would love BL.

damo · 2021-01-16 20:20:44

linux_user wrote:

.... To put it another way, if someone used to keybaords for tasks and likes a sleek interface, he/she would love BL.

BL FTW

johnraff · 2021-01-17 06:06:28

exe wrote:

Honestly, i like back to only openbox menu. Back to essence the openbox.
Jgmenu is unnecessary in my opinion.

The openbox menu is still available in BL - you aren't obliged to use jgmenu, nor to go to an absolute vanilla OpenBox session.

Press Ctrl+Alt+Q to see the BL openbox menu - it's just a placeholder out of the box, but:
Edit ~/.config/openbox/bl-menu.xml to set it up the way you want.
Edit ~/.config/openbox/bl-rc.xml to change the keybind to display the OB menu. (But try to avoid it clashing with any keybinds in ~/.xbindkeysrc)

The rest of BL will continue to work as before.

OTOH if you choose the "openbox session" option at login, you can start from scratch by copying /etc/xdg/openbox/menu.xml rc.xml and autostart into ~/.config/openbox/ and editing them to taste. The BL session will be quite unaffected and you can go back to it at any time.

Last edited by johnraff (2021-01-17 08:20:35)

johnraff · 2021-01-17 07:09:12

ohnonot wrote:

I have been telling the BL team they shouldn't fall into the distro (or DE) trap. Because crunchbang was different in that respect.
But my sympathies lean towards avoiding the unnecessary.
...wayland etc... doesn't justify turning a lean openbox setup into a ... not-so-lean "custom desktop environment and session management" sort of thing.

OK Ohnonot, understood, some people like a plain CLI environment, some like GNOME or KDE, and some like something in between. Exactly where that ideal spot lies will be different for each person. I know @hhh for example has been spending time with Cinnamon and Plasma, and I understand that you use Arch Linux. I use BunsenLabs as my daily work machine.

Your input and suggestions are always valued and read with care and respect, but in this case I wonder exactly why you seem to strongly want BL to be this way or that way if you don't actually use it? Are you saying that more users would like BL if it went back to being a plain OpenBox setup?

I'm not going to speak for the other devs here, but my preference is that BL be as useful as possible, without all the big DE encumbrances. I don't think it's fair to say BL isn't lean - it's just a compromise, but systems that were appropriate for machines with 500MB of RAM and a Pentium 4 may no longer be the best compromise in 2020.

PS as to package bloat, I might mention that every item on our install lists is checked, along with its dependencies. There is a certain amount of stuff unavoidably pulled in but we do our best to keep it to a minimum. Probably basing BL on Arch, for example, would make it easier to cut down, but using Debian Stable has its own advantages.

Last edited by johnraff (2021-01-17 07:48:35)

ohnonot · 2021-01-17 08:11:03

johnraff, I think you should've quoted all of my previous post.
You wonder..., but the answer seems to be in the bits you cut out:

I made my peace with it.
But my sympathies lean towards avoiding the unnecessary.
Not saying jgmenu isn't a great app though!
But too many people are all too unaware of what openbox can do all by itself.

Have you ever thought why I'm not using Bunsenlabs anymore?

I will keep saying these things every now and then, don't try to politely silence me.
Esp. when somebody gets dissed for asking the right questions, like exe in the last few posts (not by you though).
Doesn't mean I "strongly want BL to be" anything.
Seriously, do Your Thing! It's appreciated. But don't expect everybody here to subscribe to the fanclub attitude. Criticism is important, too.

BTW, "getting more users" is not an argument for anything in my Linux world.

johnraff wrote:

The rest of BL will continue to work as before.

That's good to hear.

johnraff · 2021-01-17 08:24:31

ohnonot wrote:

I will keep saying these things every now and then, don't try to politely silence me.

johnraff wrote:

Your input and suggestions are always valued and read with care and respect

ohnonot · 2021-01-20 06:50:29

^ You know, you're right. "politely silence" was an exaggeration. Sorry about that.

johnraff · 2021-01-20 07:05:04

^No worries! As I said, your input is appreciated.

sleekmason · 2021-01-28 14:29:59

Noticed while checking some code here: https://forums.bunsenlabs.org/viewtopic … 26#p110626

Bunsenlabs is still using dbus-x11 rather than dbus-user-session, which is now the standard.

I've tried both in my own stuff and though didn't notice any differences to performance, it did remove a couple of xsession errors about dbus.

johnraff · 2021-01-29 05:12:36

^Thanks for the reminder there. Switching to dbus-user-session has been on my "stuff to think about" list for some time now - it's a somewhat complicated topic (dependency on systemd is one aspect), but there does seem to be a movement in Debian to drop dbus-launch:
https://lists.debian.org/debian-devel/2 … 00484.html
https://bugs.debian.org/cgi-bin/bugrepo … bug=833318

There was a bug report here back in 2017 related to Terminator in Helium: https://forums.bunsenlabs.org/viewtopic … 489#p55489 and we chose dbus-X11 then, but for Beryllium perhaps it's time to switch to dbus-user-session.

Last edited by johnraff (2021-01-29 05:44:37)

DeepDayze · 2021-01-29 13:38:17

On my Lithium system I happen to have both dbus-x11 and dbus-u-s installed and no issue noted with terminator with or without the enable dbus config in terminator config.

johnraff · 2021-01-30 01:08:18

Without more research I don't know what happens when both are installed, but it seems clear that a choice would have to be made between the two algorithms ( https://bugs.debian.org/cgi-bin/bugrepo … =833318#15 )

The purpose of the dbus-user-session package is that it gives sysadmins
the choice between two models for what "the session bus" means:
* without dbus-user-session: each X11 session has its own separate
session bus, and there is no per-uid session bus that can be used to
communicate with `systemd --user` (this is the traditional behaviour)
* with dbus-user-session: there is one session bus per uid, spanning
one or more possibly overlapping login sessions (this is now the
recommended behaviour)

Also, the "Why should dbus-user-session be optional?" section here: https://lists.debian.org/debian-devel/2 … 00484.html

If you had the time, and felt like it, it might be interesting if you posted the output (purged of private data if necessary) of:

systemctl --user show-environment
env
pgrep -a dbus
grep -r 'dbus-launch' /etc/X11/Xsession.d/
grep -r DBUSLAUNCH /etc/X11/Xsession.d/

I have only dbus-x11 installed at the moment, here's mine:

john@lithium:~$ systemctl --user show-environment
HOME=/home/john
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
LOGNAME=john
PATH=/home/john/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:
SHELL=/bin/bash
USER=john
XDG_RUNTIME_DIR=/run/user/1000
QT_ACCESSIBILITY=1
QT4_IM_MODULE=fcitx
IM_CONFIG_PHASE=1
GTK_IM_MODULE=fcitx
XMODIFIERS=@im=fcitx
QT_IM_MODULE=fcitx
CLUTTER_IM_MODULE=fcitx

john@lithium:~$ env
SHELL=/bin/bash
QT_ACCESSIBILITY=1
COLORTERM=truecolor
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
GTK_IM_MODULE=fcitx
LANGUAGE=en_GB:en
QT4_IM_MODULE=fcitx
SSH_AUTH_SOCK=/tmp/ssh-jGgjDBXG980M/agent.1128
GIT_PS1_SHOWDIRTYSTATE=true
DEBFULLNAME=John Crawley
XMODIFIERS=@im=fcitx
DESKTOP_SESSION=bunsenlabs
SSH_AGENT_PID=1194
NO_AT_BRIDGE=1
GPG_TTY=/dev/pts/5
XDG_SEAT=seat0
PWD=/home/john
XDG_SESSION_DESKTOP=bunsenlabs
LOGNAME=john
QT_QPA_PLATFORMTHEME=gtk2
XDG_SESSION_TYPE=x11
GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
XAUTHORITY=/home/john/.Xauthority
XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/john
HOME=/home/john
LANG=en_GB.UTF-8
LS_COLORS=rs= # very long string #
XDG_CURRENT_DESKTOP=XFCE
VTE_VERSION=5402
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
CLUTTER_IM_MODULE=fcitx
XDG_SESSION_CLASS=user
TERM=xterm-256color
GTK_OVERLAY_SCROLLING=0
USER=john
DISPLAY=:0.0
SHLVL=2
QT_IM_MODULE=fcitx
XDG_VTNR=7
XDG_SESSION_ID=2
XDG_RUNTIME_DIR=/run/user/1000
PATH=/home/john/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
GDMSESSION=bunsenlabs
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-cz1Iw3AJE9,guid= #long number#
GIT_PS1_SHOWUNTRACKEDFILES=true

john@lithium:~$ pgrep -a dbus
561 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
1181 /usr/bin/dbus-launch --exit-with-session --sh-syntax
1182 /usr/bin/dbus-daemon --syslog --fork --print-pid 5 --print-address 7 --session
1228 /usr/bin/dbus-daemon --syslog --fork --print-pid 5 --print-address 7 --config-file /usr/share/fcitx/dbus/daemon.conf
1232 /usr/bin/fcitx-dbus-watcher unix:abstract=/tmp/dbus-3JK19669ml,guid=# long number#
1348 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3

john@lithium:~$ grep -r dbus-launch /etc/X11/Xsession.d/
/etc/X11/Xsession.d/70im-config_launch:# The hook script for dbus-launch is in 75 which changes $STARTUP string.
/etc/X11/Xsession.d/70im-config_launch:# This shuld be befor this dbus-launch hook to ensure the working dbus
/etc/X11/Xsession.d/75dbus_dbus-launch:DBUSLAUNCH=/usr/bin/dbus-launch

john@lithium:~$ grep -r DBUSLAUNCH  /etc/X11/Xsession.d/
/etc/X11/Xsession.d/75dbus_dbus-launch:DBUSLAUNCH=/usr/bin/dbus-launch
/etc/X11/Xsession.d/75dbus_dbus-launch:  if [ -z "$DBUS_SESSION_BUS_ADDRESS" ] && [ -x "$DBUSLAUNCH" ]; then
/etc/X11/Xsession.d/75dbus_dbus-launch:  eval $($DBUSLAUNCH --exit-with-session --sh-syntax)

# NOTE:
*) env contains much more than the systemd user environment in my case
*) I have a process starting with dbus-launch

Oh yes, also do you see this line in ~/.xsession-errors?

dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1

It might be even more interesting to see what changed in your output if you uninstalled dbus-x11!

Last edited by johnraff (2021-01-30 01:19:29)

DeepDayze · 2021-01-30 01:39:55

Here's mine with both dbus-x11 and dbus-u-s installed (private data has been obfuscated):

~$ systemctl --user show-environment
HOME=/home/myuser
LANG=en_US.UTF-8
LOGNAME=myuser
PATH=/home/myuser/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
SHELL=/bin/bash
USER=myuser
XDG_RUNTIME_DIR=/run/user/1000
QT_ACCESSIBILITY=1
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
DESKTOP_SESSION=bunsenlabs
DISPLAY=:0
GDMSESSION=bunsenlabs
GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
PWD=/home/myuser
QT_QPA_PLATFORMTHEME=gtk2
XAUTHORITY=/home/myuser/.Xauthority
XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/myuser
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
XDG_SESSION_CLASS=user
XDG_SESSION_DESKTOP=bunsenlabs
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
XDG_SESSION_TYPE=x11
ZEITGEIST_DATA_PATH=/home/myuser/.local/share/zeitgeist

~$ env
SHELL=/bin/bash
WINDOWID=69206019
QT_ACCESSIBILITY=1
COLORTERM=truecolor
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
TINT2_BUTTON_PANEL_X2=1920
TINT2_BUTTON_PANEL_X1=0
SSH_AUTH_SOCK=/tmp/ssh-d1Dx8NEVFRhr/agent.1449
DESKTOP_SESSION=bunsenlabs
TINT2_BUTTON_ALIGNED_Y2=1049
SSH_AGENT_PID=1494
TINT2_BUTTON_ALIGNED_Y1=1049
XDG_SEAT=seat0
PWD=/home/myuser
LOGNAME=myuser
XDG_SESSION_DESKTOP=bunsenlabs
QT_QPA_PLATFORMTHEME=gtk2
XDG_SESSION_TYPE=x11
TINT2_BUTTON_W=22
GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
TINT2_BUTTON_X=18
TINT2_BUTTON_Y=13
TINT2_BUTTON_H=22
XAUTHORITY=/home/myuser/.Xauthority
TINT2_CONFIG=/home/myuser/.config/tint2/tint2rc-lithium-custom
XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/myuser
HOME=/home/myuser
LANG=en_US.UTF-8
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.webp=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
XDG_CURRENT_DESKTOP=XFCE
VTE_VERSION=6202
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
XDG_SESSION_CLASS=user
TERM=xterm-256color
USER=myuser
TINT2_BUTTON_ALIGNED_X1=148
DISPLAY=:0
TINT2_BUTTON_ALIGNED_X2=170
SHLVL=1
XDG_VTNR=7
XDG_SESSION_ID=2
TINT2_BUTTON_PANEL_Y1=1049
TINT2_BUTTON_PANEL_Y2=1049
XDG_RUNTIME_DIR=/run/user/1000
TINT2_BUTTON_ALIGNED_Y=1049
TINT2_BUTTON_ALIGNED_X=148
PATH=/home/myuser/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
GDMSESSION=bunsenlabs
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
_=/usr/bin/env

~$ grep -r 'dbus-launch' /etc/X11/Xsession.d/
/etc/X11/Xsession.d/75dbus_dbus-launch:DBUSLAUNCH=/usr/bin/dbus-launch

~$ grep -r DBUSLAUNCH  /etc/X11/Xsession.d/
/etc/X11/Xsession.d/75dbus_dbus-launch:DBUSLAUNCH=/usr/bin/dbus-launch
/etc/X11/Xsession.d/75dbus_dbus-launch:  if [ -z "$DBUS_SESSION_BUS_ADDRESS" ] && [ -x "$DBUSLAUNCH" ]; then
/etc/X11/Xsession.d/75dbus_dbus-launch:  eval $($DBUSLAUNCH --exit-with-session --sh-syntax)

~$ pgrep -a dbus
756 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
1459 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
1500 /usr/lib/cups/notifier/dbus dbus:// 
1525 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3

EDIT:

In my ~/.xsession-errors did not see the "warning: error sending to systemd" message.

Last edited by DeepDayze (2021-01-30 01:43:40)

sleekmason · 2021-01-30 03:40:58

From my own observations, dbus-user-session will be the default if both are installed, and that they are interchangeable, meaning you can install one, and then remove the other. (but one must be installed if the dependencies are).

Dbus-x11 sets a daemon for each instance? whereas dbus-user-session throws everything into one instance.

Here's mine with just user-dbus-session (not Bunsen though), compares with DeepDayze's
(or not so much . . Looks like both are running in DeepDayze's?) <-- no, just listed.

pgrep -a dbus
414 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
630 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
708 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3

DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus

Last edited by sleekmason (2021-01-30 03:48:34)

johnraff · 2021-01-30 04:39:08

^^Many thanks!

I think we can see there that you have dbus set up in the new single-session mode - there are some significant differences from my data:

*) You have a more complete systemd user environment; these items I don't have:

DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
DESKTOP_SESSION=bunsenlabs
DISPLAY=:0
GDMSESSION=bunsenlabs
GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
PWD=/home/myuser
QT_QPA_PLATFORMTHEME=gtk2
XAUTHORITY=/home/myuser/.Xauthority
XDG_GREETER_DATA_DIR=/var/lib/lightdm/data/myuser
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
XDG_SESSION_CLASS=user
XDG_SESSION_DESKTOP=bunsenlabs
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
XDG_SESSION_TYPE=x11

In particular, DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus looks like the new setup, and there are other envvars there that might assist people trying to do something in a user systemd environment (systemd timers etc).

*) Unlike me, you haven't got any dbus-launch process running.

*) You don't get that warning in .xsession-errors

My guess would be that if dbus-user-session is installed then dbus-x11 does nothing and could be safely removed.

EDIT: @sleekmason, I missed your post (thanks!), but that your data looks much like DeepDayze's seems to confirm that dbus-x11 does nothing if dbus-user-session is installed.

Anyway, unless something comes up maybe we should install dbus-user-session in Beryllium.

Last edited by johnraff (2021-01-30 04:44:06)

DeepDayze · 2021-01-30 15:55:12

Should I try removing dbus-x11 to see what happens?

johnraff · 2021-01-31 01:54:41

DeepDayze wrote:

Should I try removing dbus-x11 to see what happens?

I think the risk of damage would be small, but it's your system! My guess is that nothing would change, but it would be nice to confirm it.

Meanwhile, I'll try doing the same from the other end - install dbus-user-session, use that for a few days, then remove dbus-x11.

One thing to check ( https://lists.debian.org/debian-devel/2 … 00484.html )

* Some desktop environments (including many configurations of "build
your own desktop environment from pieces") do support multiple
parallel X11 sessions per uid per machine. In these setups, the
user bus breaks the expectations of software that assumes it can run
once per X11 session, in parallel, and take the same bus name on the
session bus corresponding to each X11 session (for example
gnome-settings-daemon has this behaviour).

This might, just possibly, affect our use of xsettingsd to sync GTK3 settings. Probably not, but will need checking.

jeffreyC · 2021-03-22 23:24:39

A suggestion:
To help with diagnosing problems add Quick System Info like MX Linux uses.
It is a menu shortcut for inxi -Fxrz and all the user needs to do then is paste the results between code tags.

Saves time asking about info for their system in the forum.

#41 2021-01-16 14:35:57

Re: Additions to Beryllium

Identity

Expectations

Debian repos

Exceptions

The others

#42 2021-01-16 15:40:42

Re: Additions to Beryllium

Identity

#43 2021-01-16 15:48:39

Re: Additions to Beryllium

#44 2021-01-16 20:20:44

Re: Additions to Beryllium

#45 2021-01-17 06:06:28

Re: Additions to Beryllium

#46 2021-01-17 07:09:12

Re: Additions to Beryllium

#47 2021-01-17 08:11:03

Re: Additions to Beryllium

#48 2021-01-17 08:24:31

Re: Additions to Beryllium

#49 2021-01-20 06:50:29

Re: Additions to Beryllium

#50 2021-01-20 07:05:04

Re: Additions to Beryllium

#51 2021-01-28 14:29:59

Re: Additions to Beryllium

#52 2021-01-29 05:12:36

Re: Additions to Beryllium

#53 2021-01-29 13:38:17

Re: Additions to Beryllium

#54 2021-01-30 01:08:18

Re: Additions to Beryllium

#55 2021-01-30 01:39:55

Re: Additions to Beryllium

#56 2021-01-30 03:40:58

Re: Additions to Beryllium

#57 2021-01-30 04:39:08

Re: Additions to Beryllium

#58 2021-01-30 15:55:12

Re: Additions to Beryllium

#59 2021-01-31 01:54:41

Re: Additions to Beryllium

#60 2021-03-22 23:24:39

Re: Additions to Beryllium

Board footer