Carbon Bugs

hhh · 2024-08-09 15:19:10

A thread for bugs and issues with the next BL release... bunsenlabs carbon, based on Debian trixie. This thread is way early, trixie won't be release until August-ish 2025, but we're hoping to release carbon very soon after trixie (fingers crossed). Since trixie is still a year away and things are very much in flux, I'm hoping those who are interested can contribute to following trixie's development so we can change our strategy as the curve-balls come.

@johnraff and our other moderators, please merge any posts from other threads that are relevant.

I've installed BL and dist-upgraded to trixie. Two things right off the bat...

bl-exit is broken, it depends on polkitd-pkla which is no longer in trixie or sid.

xfce4-power-manager doesn't autostart because the /etc/xdg/autostart/xfce4-power-manager.desktop file has "OnlyShowIn=XFCE;" in it. In boron it had "NotShownIn=" so it didn't effect bl-session. Anyway, that fix is easy, just add 'xfce4-power-manager &' to bl-autostart like we used to.

Sector11 · 2024-08-09 17:38:23

bl-exit is broken, it depends on polkitd-pkla which is no longer in trixie or sid.

It might get fixed between now and trixie's release.
- put it under: Keep an eye on.

I don't have polkitd-pkla on my Debian 12:

 2024·08·09 @ 14:30:41 ~
   $ ser polkitd-pkla
alias ser = aptitude search
p   polkitd-pkla                    - Legacy "local authority" (.pkla) backend 
 
 2024·08·09 @ 14:35:46 ~
   $

I'm using an old modified bl-exit from 2019. Try it: ~/bin/s11-exit

#!/usr/bin/env bash
#
#    bl-exit: Bunsenlabs exit dialog, offering various exit options
#     via both GUI and CLI
#    Copyright: 2019 MXStuff.org <init.choice@mxstuff.org>
#               2019 hhh <hsumen@bunsenlabs.org>
#               2019 John Crawley <john@bunsenlabs.org>
#
#    This program is free software: you can redistribute it and/or modify
#    it under the terms of the GNU General Public License as published by
#    the Free Software Foundation, either version 3 of the License, or
#    (at your option) any later version.
#
#    This program is distributed in the hope that it will be useful,
#    but WITHOUT ANY WARRANTY; without even the implied warranty of
#    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
#    GNU General Public License for more details.
#
#    You should have received a copy of the GNU General Public License
#    along with this program.  If not, see <http://www.gnu.org/licenses/>.

########################################################################
##                                                                    ##
## Init and desktop agnostic "yad" based Logout/Exit dialogue.        ##
##                                                                    ##
## Written in response to the seeimingly widely held belief that      ##
## 'systemctl' is what you _have_ to use for power operations if you  ##
## have systemd, regardless that dbus calls are arguably superior.    ##
##                                                                    ##
## Since systemd users like systemd specific commands so much, here's ##
## a system exit dialogue that uses systemd's calls for every power   ##
## or session control action, while remaining compatible with         ##
## non-systemd systems.                                               ##
##                                                                    ##
## Originally written for Bunsenlabs "Lithium" by Bearded_Blunder     ##
## <init.choice@mxstuff.org> February 2019                            ##
##                                                                    ##
## Copyright © 2019 MXStuff.org <init.choice@mxstuff.org>             ##
##                                                                    ##
## This program is free software. It comes without any warranty, to   ##
## the extent permitted by applicable law. You can redistribute it    ##
## and/or modify it under the terms of the Do What The Fuck You Want  ##
## To Public License, Version 2, as published by Sam Hocevar. See     ##
## http://www.wtfpl.net/ for more details.                            ##
##                                                                    ##
########################################################################

### Usage ###
USAGE="\nbl-exit [OPTION]\n\n\
With no arguments default yad (GUI) or text menu at a TTY\n\n\
Only one argument is read, they cannot be combined\n\
    -h --help\tShow this help\n\
    -k --lock\tLock screen\tDoes not work for a tty session\n\
    -l --logout\tLogout\t\tAlso works for tty.\n\
    -s --suspend\tSuspend\tState determined by ACPI S0 S1 or S3\n\
    -i --hibernate\tSuspend to Disk\tRequires enough swap to store RAM\n\
    -y --hybrid\tHybrid Sleep\tACPI must support sleep state S3\n\
    -b --reboot\tReboot\n\
    -p --poweroff\tShut down\n\n\

NOTE: Screen locking is done via loginctl, and only available if
called directly as 'bl-exit --lock'.
In BunsenLabs the bl-lock utility is available which uses light-locker.
"

lock_tty_msg="Error: Graphical environment needed for screen locking.
It can be done with the vlock package installed, using the
command 'vlock'. This script does not handle that case.
If you have a graphical environment running the probable cause
of seeing this message is that no display manager is installed.
"

# Some screen locking software does not listen for logind calls,
# screen locking then fails, for such screen lockers set
# LOCK_SCREEN_COMMAND="what-locks-screen  --now"
LOCK_SCREEN_COMMAND=""
# Known tested examples: "i3lock", "slock", "xsceeensaver-command -lock"

########################################################################
#                  Compatibility function details                      #
#                                                                      #
# logoutctl() takes the following `systemctl` arguments:               #
#                                                                      #
# poweroff reboot suspend hibernate hybrid-sleep                       #
#                                                                      #
# ? suspend-then-hibernate                                             #
#                                                                      #
# elogind supports it (documented), undocumented for systemd. It does  #
# _something_ on my systemd systems YMMV. Not implimented in the main  #
# script owing to not being documented by systemctl --help.            #
#                                                                      #
# Other systemctl arguments are not transferred to the elogind project #
# and will break if a similar systemctl || loginctl approach is used.  #
#                                                                      #
# Also takes $LOCK_SCREEN_COMMAND if defined in config to handle       #
# screen lockers which don't respond to `loginctl lock-session`        #
#                                                                      #
# loginctl lock-/terminate-session is handled here both to provide     #
# central yad closing and for non-standard screen-lock compatibiliy.   #
#                                                                      #
########################################################################
logoutctl(){
    if [[ ! -z $YAD_PID ]]; then
        kill -SIGUSR1 $YAD_PID
    fi
    case $1 in
        cancel )
            echo -e "\ncancelled"
            exit 0 ;;
        lock-session )
            echo -e "\n$1"
            [[ ! -z "$LOCK_SCREEN_COMMAND" ]] && $LOCK_SCREEN_COMMAND || loginctl $1 $XDG_SESSION_ID
            exit $? ;;
        terminate-session )
            echo  -e "\n$1"
            loginctl $1 $XDG_SESSION_ID
            exit $? ;;
        suspend | hibernate | hybrid-sleep | suspend-then-hibernate | reboot | poweroff )
            echo -e "\n$1"
            # The systemd or elogind compatibility magic.   #
            [[ $(command -v systemctl) ]] && systemctl "$1" || loginctl "$1"
            exit $? ;;
    esac
}
export -f logoutctl

# tests
on_terminal(){
    if [[ -t 0 ]]
    then
        if [[ -t 1 && -t 2 ]]
        then
            return 0
        else
            echo "$0: STDIN is on terminal, but not STDOUT or STDERR" >&2
            exit 1
        fi
    else
        return 1
    fi
}
#on_graphical_session(){
#    case "$( loginctl show-session -p Type $XDG_SESSION_ID )"
#    in
#        'Type=x11'|'Type=wayland')
#            return 0
#            ;;
#        'Type=tty')
#            return 1
#            ;;
#        *)
#            echo "$0: unable to determine session type." >&2
#            exit 1
#            ;;
#    esac
#}
on_graphical_session(){
    [[ -n $DISPLAY || -n $WAYLAND_DISPLAY ]] && return 0
    return 1
}

# only display this on a TTY
tty_menu(){
    clear
    PS3="Please choose an option "
    select option in Logout Suspend Hibernate Hybrid-Sleep Reboot Power-Off Quit-Dialogue
    do
        case $option in
            Logout)        logoutctl terminate-session;;
            Suspend)       logoutctl suspend;;
            Hibernate)     logoutctl hibernate;;
            Hybrid-Sleep)  logoutctl hybrid-sleep;;
            Reboot)        logoutctl reboot;;
            Power-Off)     logoutctl poweroff;;
            Quit-Dialogue) echo 'exit cancelled';;
        esac
        break
    done
}

# can only use this in a graphical session
yad_gui() {
    yad --class=WmanExit --title "Exit" --close-on-unfocus --undecorated --center --on-top --borders=10 --window-icon=system-log-out \
        --button=" _Logout!system-log-out!Logout":'bash -c "logoutctl terminate-session"' \
        --button=" Re_boot!system-reboot!":'bash -c "logoutctl reboot"' \
        --button=" _Power Off!system-shutdown!":'bash -c "logoutctl poweroff"'
}

case "$1" in
    -h|--help)
        echo -e "$USAGE"
        ;;
    -k|--lock)
        if on_graphical_session
        then
            logoutctl lock-session
        else
            echo "$0: $lock_tty_msg" >&2
            exit 1
        fi
        ;;
    -l|--logout)
        logoutctl terminate-session
        ;;
    -b|--reboot)
        logoutctl reboot
        ;;
    -p|--poweroff)
        logoutctl poweroff
        ;;
    '')
        if on_terminal
        then
            tty_menu
        elif on_graphical_session
        then
            yad_gui
        else
            echo "$0: No exit option passed,
and unable to display exit menu." >&2
            exit 1
        fi
        ;;
    *)
        echo "$0: Unknown operation $1"
        echo -e "$USAGE"
        exit 1
        ;;
esac

Only shows:

[Logout] [Reboot] [Poweroff]

as that's all I need

hhh · 2024-08-09 17:59:39

Sector11 wrote:

I don't have polkitd-pkla on my Debian 12

Thanks for posting that! It made me double check the bookworm package and it's only for ARM architecture...

https://packages.debian.org/bookworm/ar … lkitd-pkla

So I tried installing the boron package (12.2) from here...

http://pkg.bunsenlabs.org/debian/pool/m … nsen-exit/

... and that shows a dependency on policykit-1, which in trixie is deprecated in favor of polkitd and pkexec. I'm sure @johnraff will shed more light in a few hours when he's online.

hhh · 2024-08-09 19:13:21

I wiped my install and used the trixie installer snapshot image...

https://cdimage.debian.org/cdimage/dail … 64/iso-cd/

... and installed Xfce as the desktop. I then added the bunsenkeyring and carbon sources as described here...

https://forums.bunsenlabs.org/viewtopic.php?id=9007

bunsen-meta-base fails to install due to the polkitd-pkla dependency.

Bearded_Blunder · 2024-08-09 20:45:10

hhh wrote:

I wiped my install and used the trixie installer snapshot image...
https://cdimage.debian.org/cdimage/dail … 64/iso-cd/
... and installed Xfce as the desktop. I then added the bunsenkeyring and carbon sources as described here...
https://forums.bunsenlabs.org/viewtopic.php?id=9007
bunsen-meta-base fails to install due to the polkitd-pkla dependency.

It's a case of re-writing the policykit rules in the new format, which needs doing for basically everywhere there were custom Bunsen policykit rules, I don't envy whoever does it, it's a tedious task. I'm snowed under with other stuff or I might have taken a swing at it.

Anyhow, that's where that depend is coming from.

Anything else in BL that used policykit & has custom BL rules will also be broken.

Last edited by Bearded_Blunder (2024-08-09 20:57:23)

hhh · 2024-08-09 20:55:08

https://bugs.debian.org/cgi-bin/bugrepo … ug=1033511

johnraff · 2024-08-10 00:50:20

hhh wrote:

A thread for bugs and issues with the next BL release... bunsenlabs carbon, based on Debian trixie. This thread is way early, trixie won't be release until August-ish 2025, but we're hoping to release carbon very soon after trixie (fingers crossed). Since trixie is still a year away and things are very much in flux, I'm hoping those who are interested can contribute to following trixie's development so we can change our strategy as the curve-balls come.

Great idea! Keep Carbon development separate from fixing bugs in the current BL.

Fingers xx++ about getting Carbon out right after Trixie. Looks quite possible viewed from August 2024.

johnraff · 2024-08-10 00:59:40

hhh wrote:

bl-exit is broken, it depends on polkitd-pkla which is no longer in trixie or sid.

This one's easy: bl-exit hasn't needed pkexec for some time. That came from an edit-config-file menu item that we no longer ship. I noticed the disappearance of polkitd-pkla a week or two ago when I tried to upgrade an existing Carbon test system.

The fix is trivial: drop the dependency on polkitd and polkitd-pkla.
I've already edited debian/control locally but didn't get round to uploading it.
I guess now more people are likely to be doing test installs of Carbon I should do a bunsen-exit package upgrade, today.

hhh wrote:

bunsen-meta-base fails to install due to the polkitd-pkla dependency

Thanks, all the meta- packages will also need upgrading. I guess that's urgent because people are using them for test installs, like @hhh. There will likely be a succession of upgrades of those meta packages as things come in...
---

B_B wrote:

It's a case of re-writing the policykit rules in the new format
Anything else in BL that used policykit & has custom BL rules will also be broken.

Yes, this task still remains for various other packages that do invoke pkexec. I notice, for example, that Thunar's right-click "open as root" no longer works.

Last edited by johnraff (2024-08-10 01:15:33)

johnraff · 2024-08-10 01:02:52

hhh wrote:

xfce4-power-manager doesn't autostart because the /etc/xdg/autostart/xfce4-power-manager.desktop file has "OnlyShowIn=XFCE;" in it. In boron it had "NotShownIn=" so it didn't effect bl-session. Anyway, that fix is easy, just add 'xfce4-power-manager &' to bl-autostart like we used to.

Thanks for catching that. In my VM, power management doesn't really stand out, and I totally missed it.

hhh · 2024-08-10 02:27:41

johnraff wrote:

I notice, for example, that Thunar's right-click "open as root" no longer works.

It works from me on this new trixie install, and open file as root works for me as well. More testing needed here.

One really weird thing with this fresh install is that when I installed bunsen-common, which brought in most of BL carbon, it wiped out my XFCE desktop settings. Panel reset to a blank panel, all icons shown on the desktop, touchpad settings gone, appearance settings gone. No idea what happened. But let's put that on the back-burner for now.

You up for rebuilding bunsen-exit to drop the dependency on polkitd-pkla?

This is fun, running BL again. It's a great desktop!

It's been awhile, so I was surprised to see you dropped dev tools from the bl-welcome script. I think that's a good choice though, it's much more streamlined than it used to be.

hhh · 2024-08-10 02:40:04

Menu popups and dropdowns now show black spaces around the corner (right click the main pane of Thunar, or view the menu for an example). I see the note in picom about it, but I can't make the black corners go away yet.

hhh · 2024-08-10 02:45:43

^ I fixed this on my laptop by un-commenting line #530 of picom.conf, "backend=glx;".

johnraff · 2024-08-10 05:00:55

bunsen-exit: drop dependencies on polkitd and polkitd-pkla.
bunsen-meta-*: drop dependencies on polkitd-pkla.

Both uploaded.

johnraff · 2024-08-10 05:11:50

hhh wrote:

johnraff wrote:
I notice, for example, that Thunar's right-click "open as root" no longer works.
It works from me on this new trixie install, and open file as root works for me as well. More testing needed here.

Hmm... maybe that was on Wayland. I'll have another look on Carbon X11.

One really weird thing with this fresh install is that when I installed bunsen-common, which brought in most of BL carbon, it wiped out my XFCE desktop settings. Panel reset to a blank panel, all icons shown on the desktop, touchpad settings gone, appearance settings gone. No idea what happened. But let's put that on the back-burner for now.

Weird indeed... That shouldn't happen.

You up for rebuilding bunsen-exit to drop the dependency on polkitd-pkla?

Done. It was one line in debian/control and the dependency was unneccessary anyway.

This is fun, running BL again. It's a great desktop!

I think so. It's my daily driver.

I was surprised to see you dropped dev tools from the bl-welcome script.

Wait, what?!! I haven't dropped anything. Didn't you get the invite to go on to the "development" section at the end, where you can install the "version control tools", "LAMP stack" or "Debian packaging tools"?

hhh · 2024-08-10 16:41:27

^ My bad, I bet it was there but the verbiage was different from what I remembered, and I rushed past it.

Great job fixing the dependency issue. I decided to reinstall trixie with no desktop for a pure carbon, pun intended, experience.

geany is not in trixie yet, so that breaks bunsen-meta-all for now. My workaround is to switch sources to sid and apt update, install bunsen-meta-all, then switch sources back and apt update again if you don't want to stay on sid.

bl-welcome doesn't run for me on trixie or sid...

Error: This script should run on a BunsenLabs system based on Debian Bookworm.

I looked at the script and I see you have references to DebTesting in there, but something needs tweaking, I guess.

The installation instructions we've linked were originally for installing bunsen-meta-base, of course change that to bunsen-meta-all to install the full carbon desktop.

johnraff · 2024-08-11 02:05:29

hhh wrote:

geany is not in trixie yet, so that breaks bunsen-meta-all for now.

Geany's still stuck with two serious bugs in Trixie.
https://bugs.debian.org/cgi-bin/bugrepo … ug=1061346
https://bugs.debian.org/cgi-bin/bugrepo … ug=1061406

I guess the "Geany Packaging Team" will fix them before release time, but I suppose the best thing is to temporarily remove geany from the Carbon meta lists?

Development packages mean frequent upgrades, can't be helped.

hhh · 2024-08-11 02:21:23

johnraff wrote:

I guess the "Geany Packaging Team" will fix them before release time, but I suppose the best thing is to temporarily remove geany from the Carbon meta lists?

You could replace it with, say, gedit, or you could just do what I did and use a sid source to install bunsen-meta-all and then switch back to trixie.

I haven't noticed any problems with the sid package of geany on my install yet.

hhh · 2024-08-11 02:45:28

hhh wrote:

I haven't noticed any problems with the sid package of geany on my install yet.

Installing bunsen-meta-all --no-install-recommends (or with-recommends) with sid as the source doesn't bring in geany-plugins.

My laptop fan is running faster on carbon that it does on Ubuntu noble, I'll have to check if I've installed any fan control packages that are lowering the fan speed/giving the fan more speed options.

johnraff · 2024-08-11 03:05:30

hhh wrote:

bl-welcome doesn't run for me on trixie or sid...
Error: This script should run on a BunsenLabs system based on Debian Bookworm.
I looked at the script and I see you have references to DebTesting in there, but something needs tweaking, I guess.

Yes.
I forgot to edit the Debian and BL release names to Trixie and Carbon.

DebTesting() should throw up a warning to people (like you) who are using the script while still in Testing.

Uploaded bunsen-welcome 13.1-1
If you upgrade and run bl-welcome again, does it now work OK?
And do you see that warning about security repos while using Testing?

hhh · 2024-08-11 03:24:47

^ Fast work! I'm back on trixie. Most of the script works. I get this error when trying to install the dev packages and firmware check...

No rush, but we're getting there!

BTW, my src repos are commented out, that might be part of the problem?

Last edited by hhh (2024-08-11 03:36:42)

#1 2024-08-09 15:19:10

Carbon Bugs

#2 2024-08-09 17:38:23

Re: Carbon Bugs

#3 2024-08-09 17:59:39

Re: Carbon Bugs

#4 2024-08-09 19:13:21

Re: Carbon Bugs

#5 2024-08-09 20:45:10

Re: Carbon Bugs

#6 2024-08-09 20:55:08

Re: Carbon Bugs

#7 2024-08-10 00:50:20

Re: Carbon Bugs

#8 2024-08-10 00:59:40

Re: Carbon Bugs

#9 2024-08-10 01:02:52

Re: Carbon Bugs

#10 2024-08-10 02:27:41

Re: Carbon Bugs

#11 2024-08-10 02:40:04

Re: Carbon Bugs

#12 2024-08-10 02:45:43

Re: Carbon Bugs

#13 2024-08-10 05:00:55

Re: Carbon Bugs

#14 2024-08-10 05:11:50

Re: Carbon Bugs

#15 2024-08-10 16:41:27

Re: Carbon Bugs

#16 2024-08-11 02:05:29

Re: Carbon Bugs

#17 2024-08-11 02:21:23

Re: Carbon Bugs

#18 2024-08-11 02:45:28

Re: Carbon Bugs

#19 2024-08-11 03:05:30

Re: Carbon Bugs

#20 2024-08-11 03:24:47

Re: Carbon Bugs

Board footer