You are not logged in.

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

sleekmason
zoom
Registered: 2018-05-22
Posts: 620
Website

Re: Additions to Beryllium

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.

Offline

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

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 8,310
Website

Re: Additions to Beryllium

^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)


...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Introduction to the Bunsenlabs Lithium Desktop

Offline

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

DeepDayze
Like sands through an hourglass...
From: In Linux Land
Registered: 2017-05-28
Posts: 1,356

Re: Additions to Beryllium

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.


Real Men Use Linux

Offline

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

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 8,310
Website

Re: Additions to Beryllium

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! smile

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


...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Introduction to the Bunsenlabs Lithium Desktop

Offline

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

DeepDayze
Like sands through an hourglass...
From: In Linux Land
Registered: 2017-05-28
Posts: 1,356

Re: Additions to Beryllium

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)


Real Men Use Linux

Offline

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

sleekmason
zoom
Registered: 2018-05-22
Posts: 620
Website

Re: Additions to Beryllium

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)

Offline

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

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 8,310
Website

Re: Additions to Beryllium

^^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)


...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Introduction to the Bunsenlabs Lithium Desktop

Offline

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

DeepDayze
Like sands through an hourglass...
From: In Linux Land
Registered: 2017-05-28
Posts: 1,356

Re: Additions to Beryllium

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


Real Men Use Linux

Offline

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

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 8,310
Website

Re: Additions to Beryllium

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.


...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Introduction to the Bunsenlabs Lithium Desktop

Offline

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

jeffreyC
Member
Registered: 2019-09-07
Posts: 68

Re: Additions to Beryllium

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.

Offline

#61 2021-03-22 23:58:13

DeepDayze
Like sands through an hourglass...
From: In Linux Land
Registered: 2017-05-28
Posts: 1,356

Re: Additions to Beryllium

jeffreyC wrote:

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.

Nice addition which is trivial to implement. Basically add an option to the Applications>System menu to display that command output in a terminal window. That command would be useful here too for helping users with troubleshooting issues.

Last edited by DeepDayze (2021-03-22 23:59:46)


Real Men Use Linux

Offline

#62 2021-03-23 09:37:54

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 8,310
Website

Re: Additions to Beryllium

^^Thanks - that does sound like a good idea.


...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Introduction to the Bunsenlabs Lithium Desktop

Offline

#63 2021-03-23 10:55:38

rbh
Moderator
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 1,206

Re: Additions to Beryllium

Maybe add option for installing package hw-probe from bl-wellcome?


// Regards rbh

Please read before requesting help: Guide to getting help,
Introduction to the Bunsenlabs Lithium Desktop and other help topics under "Help Resources" on the BunsenLabs menu

Offline

#64 2021-03-23 13:25:09

jeffreyC
Member
Registered: 2019-09-07
Posts: 68

Re: Additions to Beryllium

rbh wrote:

Maybe add option for installing package hw-probe from bl-wellcome?

inxi does not upload your info to any database, some people find hw-probe doing that disturbing.

Offline

#65 2021-03-24 08:51:09

dolly
Miss Mixunderstand
From: /lab701
Registered: 2015-10-03
Posts: 434

Re: Additions to Beryllium

How about removing Dropbox from "bl-welcome"? I think it is about time.

By the way, if there are a lot of "bl-welcome" suggestions in the loop, it could be better to have them in a separate thread? It would make it easier to keep track of the discussion.

Also, thanks for the "inxi -Fxrz" idea, sounds great. smile

Edit =  ops

Last edited by dolly (2021-05-15 11:28:45)


A bit nerdy, trying to grow up.

Offline

#66 2021-03-24 10:23:56

rbh
Moderator
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 1,206

Re: Additions to Beryllium

jeffreyC wrote:
rbh wrote:

Maybe add option for installing package hw-probe from bl-wellcome?

inxi does not upload your info to any database, some people find hw-probe doing that disturbing.

If you don't want to contribute to build the hardware database, you must not do that. It is totaly voluntarily. Just do not install it.
Do you know what disturbs folks with submitting anomynized hw-data?

But Many find hw-probe very usefull. It is good to have a growing hw database. It is good to be able to browse the database for your OS: https://linux-hardware.org/?d=Debian and harware you want to know if it is Linux compatible.

A Link to https://linux-hardware.org/?d=Debian, might be helpful under Help.


// Regards rbh

Please read before requesting help: Guide to getting help,
Introduction to the Bunsenlabs Lithium Desktop and other help topics under "Help Resources" on the BunsenLabs menu

Offline

#67 2021-07-22 03:08:44

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 8,310
Website

Re: Additions to Beryllium

sleekmason wrote:

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.

Final (hopefully) revisit of this topic: dbus-user-session is already in the Beryllium metapackage dependencies, but yesterday I hit an issue with the Beryllium bunsen-meta-lite setup, which uses mousepad instead of geany as bl-text-editor.
Menu "Open as root", which invokes pkexec bl-text-editor <file>, didn't work until I installed dbus-x11.
Anyway, protonvpn on my Buster machine also depends on dbus-x11, so it's clear that some apps still need it.

Installing both dbus-user-session and dbus-x11 feels messy, but it hasn't yet been shown to do any harm.

So - given that we will install dbus-user-session anyway - add dbus-x11 only to bunsen-meta-lite or to bunsen-meta-all also?


...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Introduction to the Bunsenlabs Lithium Desktop

Offline

#68 2021-07-22 19:36:31

DeepDayze
Like sands through an hourglass...
From: In Linux Land
Registered: 2017-05-28
Posts: 1,356

Re: Additions to Beryllium

johnraff wrote:
sleekmason wrote:

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.

Final (hopefully) revisit of this topic: dbus-user-session is already in the Beryllium metapackage dependencies, but yesterday I hit an issue with the Beryllium bunsen-meta-lite setup, which uses mousepad instead of geany as bl-text-editor.
Menu "Open as root" - which invokes pkexec bl-text-editor <file> - didn't work until I installed dbus-x11.
Anyway, protonvpn on my Buster machine also depends on dbus-x11, so it's clear that some apps still need it.

Installing both dbus-user-session and dbus-x11 feels messy, but it hasn't yet been shown to do any harm.

So - given that we will install dbus-user-session anyway - add dbus-x11 only to bunsen-meta-lite or to bunsen-meta-all also?

Policykit-1 (which has pkexec and friends) does depend on dbus thus by extension dbus-x11:

~$ apt depends policykit-1
policykit-1
  Depends: dbus
  Depends: libpam-systemd
  Depends: libc6 (>= 2.7)
  Depends: libglib2.0-0 (>= 2.37.3)
  Depends: libpam0g (>= 0.99.7.1)
  Depends: libpolkit-agent-1-0 (= 0.105-25)
  Depends: libpolkit-backend-1-0 (= 0.105-25)
  Depends: libpolkit-gobject-1-0 (= 0.105-25)

Best to install both d-u-s and d-x11 in Beryllium in that case to cover all the corner cases.

Last edited by DeepDayze (2021-07-22 19:37:03)


Real Men Use Linux

Offline

#69 2021-07-23 01:50:08

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 8,310
Website

Re: Additions to Beryllium

DeepDayze wrote:

Best to install both d-u-s and d-x11 in Beryllium in that case to cover all the corner cases.

Yes, starting to think this way too.

The Debian documentation presents things in an either/or way, but it seems that as long as d-u-s is installed, then a dbus user session is correctly started up. Then if d-x11 is also installed, although it won't normally be used, corner cases that want to invoke dbus-launch (which d-x11 includes) can still do so, even though that might not be an ideal situation. Reading 'man dbus-launch' again, the  "AUTOMATIC LAUNCHING" section suggests why mousepad might have wanted dbus-launch in order to run as root:

man dbus-launch wrote:

AUTOMATIC LAUNCHING
       If DBUS_SESSION_BUS_ADDRESS is not set for a process that tries to use
       D-Bus, by default the process will attempt to invoke dbus-launch with
       the --autolaunch option to start up a new session bus or find the
       existing bus address on the X display or in a file in
       ~/.dbus/session-bus/

       Whenever an autolaunch occurs, the application that had to start a new
       bus will be in its own little world; it can effectively end up starting
       a whole new session if it tries to use a lot of bus services. This can
       be suboptimal or even totally broken, depending on the app and what it
       tries to do.

       There are two common reasons for autolaunch. One is ssh to a remote
       machine....
(snip)

       The second common reason for autolaunch is an su to another user, and
       display of X applications running as the second user on the display
       belonging to the first user. Perhaps the ideal fix in this case would be
       to allow the second user to connect to the session bus of the first
       user, just as they can connect to the first user's display. However, a
       mechanism for that has not been coded.

So root does not have DBUS_SESSION_BUS_ADDRESS set and mousepad (in the BL "lite" setup) calls dbus-launch when invoked with pkexec. (For whatever reason, geany handles things differently, and if geany is set as bl-text-editor then 'pkexec bl-text-editor' works even without dbus-x11 installed.)

DeepDayze wrote:

Policykit-1 (which has pkexec and friends) does depend on dbus thus by extension dbus-x11:

However, this isn't exactly right, see:

john@lithium:~$ apt depends dbus
dbus
  Depends: adduser
  Depends: libapparmor1 (>= 2.8.94)
  Depends: libaudit1 (>= 1:2.2.1)
  Depends: libc6 (>= 2.14)
  Depends: libcap-ng0 (>= 0.7.9)
  Depends: libdbus-1-3 (= 1.12.20-0+deb10u1)
  Depends: libexpat1 (>= 2.1~beta3)
  Depends: libselinux1 (>= 2.0.65)
  Depends: libsystemd0
 |Suggests: <default-dbus-session-bus>
    dbus-user-session
  Suggests: <dbus-session-bus>
    dbus-user-session
    dbus-x11

dbus suggests the virtual packages default-dbus-session-bus or dbus-session-bus, and the latter is provided by either of d-u-s or d-x11.

Anyway, enough, let's ship both!

Next problem...


...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Introduction to the Bunsenlabs Lithium Desktop

Offline

#70 2021-07-29 05:59:52

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 8,310
Website

Re: Additions to Beryllium

jeffreyC wrote:

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.

So, I added this to ~/.config/jgmenu/prepend.csv in the "System" section near the end:

Quick System Info,x-terminal-emulator -T 'inxi -Fxrz' -e bash -c "inxi -Fxrz; echo $'\n\nPress any key to close'; read -srn1"

Seems to do the job. Thanks @jeffreyC for the suggestion.

Give it a try!


...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Introduction to the Bunsenlabs Lithium Desktop

Offline

#71 2021-07-29 06:59:35

damo
....moderator....
Registered: 2015-08-20
Posts: 6,716

Re: Additions to Beryllium

^ That's neat smile


Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt  «» BunsenLabs on DeviantArt

Offline

#72 2021-07-30 07:32:58

dolly
Miss Mixunderstand
From: /lab701
Registered: 2015-10-03
Posts: 434

Re: Additions to Beryllium

Thanks, very nice, and also thank you for the white battery indicator. Looks much better now. smile


A bit nerdy, trying to grow up.

Offline

#73 2021-08-02 11:18:19

rbh
Moderator
From: Sweden/Vasterbotten/Rusfors
Registered: 2016-08-11
Posts: 1,206

Re: Additions to Beryllium

It might be helpful for some people to add the info below in the header of all BL user configs...

Bunsenlabs User config files
All default BunsenLabs user config files is located in /usr/share/bunsen/skel.
Skript bl-user-setup, copies them to $HOME directory.
More info with command 'bl-user-setup --help'


// Regards rbh

Please read before requesting help: Guide to getting help,
Introduction to the Bunsenlabs Lithium Desktop and other help topics under "Help Resources" on the BunsenLabs menu

Offline

#74 2021-08-03 05:50:45

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 8,310
Website

Re: Additions to Beryllium

^This will be easy to do - I'll add something to files as I edit them for whatever reason.


...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Introduction to the Bunsenlabs Lithium Desktop

Offline

#75 2021-08-11 01:51:22

portaro
Member
From: Portugal
Registered: 2020-01-03
Posts: 58

Re: Additions to Beryllium

I see in last days a form to view images on terminal - xterm, and for see videos in terminal with a tools like →
sixel
lsix
img2sixel

https://github.com/saitoha/libsixel

I test in my actual system but I cant configure that i I can't do this work,maybe is an iteresting thing to add to make more atractive the terminal of our Bunsenlabs, in my opinion is very good.

I also use bpytop here and is great, there are also a gotop like htop but with other appearance.

https://github.com/cjbassi/gotop

In other way today I see a youtube stream about on openbox distro and a user cooment that the distro dont have any graphic tool to edit mouse sensitivity then I search on my Bunsenlabs to see if I find anything and I als donte see any tool, other user comment to install lxinput. (Maybe is a interesting thing to think also for people that use games).

Take a look if posible on sixel and if is interesting maybe come in the next release if the developers have time and like the idea to implement it in Bunsenlabs.


Thanks, I hope my suggestion is interesting.

Last edited by portaro (2021-08-11 01:59:24)

Offline

Board footer

Powered by FluxBB