Additions to Beryllium

DeepDayze · 2021-03-22 23:58:13

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)

johnraff · 2021-03-23 09:37:54

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

rbh · 2021-03-23 10:55:38

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

jeffreyC · 2021-03-23 13:25:09

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.

dolly · 2021-03-24 08:51:09

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.

Edit = :8

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

rbh · 2021-03-24 10:23:56

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.

johnraff · 2021-07-22 03:08:44

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?

DeepDayze · 2021-07-22 19:36:31

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)

johnraff · 2021-07-23 01:50:08

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...

johnraff · 2021-07-29 05:59:52

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!

damo · 2021-07-29 06:59:35

^ That's neat

dolly · 2021-07-30 07:32:58

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

rbh · 2021-08-02 11:18:19

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'

johnraff · 2021-08-03 05:50:45

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

portaro · 2021-08-11 01:51:22

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)

johnraff · 2021-08-11 02:19:30

^Thanks for the suggestions.
libsixel-bin and lxinput are both available from Debian, but maybe as Beryllium should now be released with as little delay as possible, we ought to consider them for the next release, Boron.

I've opened a new thread for Boron suggestions:
https://forums.bunsenlabs.org/viewtopic … 01#p116501

Last edited by johnraff (2021-08-11 02:23:24)

portaro · 2021-08-11 14:28:06

Thanks John.

rbh · 2021-08-26 19:50:38

I noted that "Compton is no longer being developed by the original author; the development continues as picom"

So that is a swap needed to be done.

hhh · 2021-08-26 20:46:05

I think we're on that, @johnraff would need to confirm. We've got the xfce4-panel battery icon sorted as well via a custom package build, or maybe the fix is already in bullseye.

sleekmason · 2021-08-28 12:48:06

Still no fix for the battery icon in Bullseye or Sid at the moment though it looks like @Johnraff has it figured for BL.

I tried picom to replace Compton and had a few issues with screen tearing that I couldn't resolve. Looking forward to seeing what settings you come up with. Was easier for me at the time to just stay with Compton. Sounds like that option may disappear in the future.

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

Re: Additions to Beryllium

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

Re: Additions to Beryllium

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

Re: Additions to Beryllium

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

Re: Additions to Beryllium

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

Re: Additions to Beryllium

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

Re: Additions to Beryllium

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

Re: Additions to Beryllium

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

Re: Additions to Beryllium

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

Re: Additions to Beryllium

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

Re: Additions to Beryllium

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

Re: Additions to Beryllium

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

Re: Additions to Beryllium

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

Re: Additions to Beryllium

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

Re: Additions to Beryllium

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

Re: Additions to Beryllium

#76 2021-08-11 02:19:30

Re: Additions to Beryllium

#77 2021-08-11 14:28:06

Re: Additions to Beryllium

#78 2021-08-26 19:50:38

Re: Additions to Beryllium

#79 2021-08-26 20:46:05

Re: Additions to Beryllium

#80 2021-08-28 12:48:06

Re: Additions to Beryllium

Board footer