Carbon RC2 bugs

johnraff · 2026-01-13 09:00:00

Please post any issues you find with the Carbon RC2 iso here.
Thanks!

This thread is now closed because having multiple bug reports mixed up together was too confusing. Please post any new bugs related to the Carbon RC2 iso in individual threads, adding a tag [Carbon RC2]. I have split off the two remaining unresolved discussions in this way:
https://forums.bunsenlabs.org/viewtopic.php?id=9662
https://forums.bunsenlabs.org/viewtopic.php?id=9664

Last edited by johnraff (2026-01-18 05:34:40)

titan · 2026-01-13 12:01:21

Just installed it, long time since I used BL so may be operator error but
can't remove conky, can kill it from menu but like zombie it come back ( it worked on Boron)
Cant see how to rename, or remove name(number) for workspaces. On xfce workspace switcher the slider to show workspace number is off but they are on. Get error failed to open workspace settings "xfwm4-workspace-settings" no such file

PackRat · 2026-01-13 19:44:22

Trying the live session.

Failed to boot on uEFI system, booted fine on legacy BIOS system.

Two battery monitor icons showing. One for xfce4-power-manager and the battery monitor plugin:

Same workspace issues as titan. Change the workspace settings with obconf? I didn't get that far into testing.

Everything else working out of the box.

s-rod · 2026-01-13 20:25:43

UPDATE: I was able to correct these issues by copying ~/.config/picom.conf from my Boron qemu host to the CarbonRC2 guest.

Attempting to get RC2 to work in qemu (Boron host).

1) Live booting presents me with correct desktop and conky (but no panel). Choosing xfce4-panel Preferences from the menu will start the panel. The bigger issue is when using the terminal, keyboard input does not display until I resize the terminal window.

2) When installed - Keyboard input (asterisks) shows up when logging in. However the Bunsenlabs-Welcome window does not show any text until the terminal is resized. Anytime something is typed, the terminal window must be resized to show the results. Additionally selecting run from the menu shows no keyboard input.

Thinking this was a qemu issue, I logged out and started an openbox session. Within the openbox session the terminal works correctly. When switching between sessions, the xfce-panel doesn't always start in the Bunsenlabs session - going to the menu an selecting xfce-panel-preferences will start the panel

Last edited by s-rod (2026-01-13 21:39:31)

dmontaine · 2026-01-13 23:30:05

Installed into virtualbox. 12g of memory 12 cpu cores
-----------------------------------------------------------------------

Installation very very slow - paused for 10 minutes

bl-welcome did not start on first login- terminal was frozen

terminal finally freed up on 5th reboot, but no bl-welcome

tried to run bl-welcome manually, froze at "checking internet connection"

tried to apply Bark blob - system aborted with no error message

in general seemed slow and lagging

Installed to backup laptop(bare metal) that has been used in the past for Boron
--------------------------------------------------------------------------------------------------------
Installed on bare metal MSI laptop

Install worked OK - bl-welcome ran correctly

However - problems with Blobs

1) Changing to Beryllium Blob
- message that desktop wallpaper was not available
- error message about line 3097

2) After installation of Beryllium Blob, tried to manually change background wallpaper using XW Wallpaper
- result was everything missing from desktop
- only jgmenu was available
- even network connection disappeared

Last edited by dmontaine (2026-01-16 01:20:27)

johnraff · 2026-01-14 01:30:01

Thanks for these reports. I'm out of time today but I'll go over them all soon.

First off, the upgrade of picom - requiring openGL to work properly - brings issues, especially on a VM. If you can't set your VM to use 3D acceleration and openGL, then for now I suggest turning composition off.
Menu > User Settings > Compositor
That should fix a lot of weirdness.

hhh · 2026-01-14 03:46:43

Something seriously wrong with @dmontaine's and @s-rod's installs. I'm not seeing any of that when installed on my laptop. No delays, no picom issues, no conky issues.

@PackRat, I see it, a battery icon and a battery power level applet (progressbar).

s-rod · 2026-01-14 16:02:10

My picom issue was a result of the default qemu settings not providing 3D acceleration. I enabled 3d acceleration in qemu settings:
Display Spice > Listen type" > None > Check the OpenGL box.
Then under "Video Virtio" the 3d Acceleration could be enabled without any errors.

I have a tendency to evaluate distros in a VM first. Not a big deal for me as I have used Bunsenlabs since day one. My concern would be that a new user might get frustrated and just give up on evaluating Bunsenlabs because it doesn't function correctly in a default qemu setup.

dbvolvox · 2026-01-14 22:28:18

Fresh install on an HP255 laptop. Looks very nice, great job guys. I have added numlockx and put the 'numlockx on' command in .config/bunsen/autostart but it doesn't work. Is that the right place to put that command? NB the command works in a terminal.

I also had to install nfs-common to get connection to my network share. Is the need for this so rare that it's not worth having in the ISO?

johnraff · 2026-01-15 00:30:33

Thanks again for all the bug reports! As promised, I will come back and check over each one, but I'm really tied up for a few days...

unklar · 2026-01-15 11:25:16

titan wrote:

Just installed it, long time since I used BL so may be operator error but
can't remove conky, can kill it from menu but like zombie it come back ( it worked on Boron)
...

I can confirm this error here on a metal installation.
The message in the ~/.xsession-errors is:

/usr/bin/bl-conky-session: There is no default session file: /home/unklar/.config/conky/conky-sessionfile, generating now...

It will probably be through the script bl-conky-session in /usr/bin/ caused because the command

bl-conky-session --list
conky-sessionfile *

returns.
---------------------------------
bl-welcome Script also offers to set up the debian-backport and bunsen-backport, which I did. Later I converted to the deb822 format using the command

sudo apt modernize-sources

executed.
It was noticeable that the backports were missing.
Therefore bl-welcome again to determine that the backports are not created.

The conversion from debian and bunsen sources is done correctly and the update is error-free.

Last edited by unklar (2026-01-15 11:29:18)

johnraff · 2026-01-16 08:45:17

titan wrote:

can't remove conky, can kill it from menu but like zombie it come back

How exactly did you kill it? Try User Settings > Conky > Conky Manager

Cant see how to rename, or remove name(number) for workspaces. On xfce workspace switcher the slider to show workspace number is off but they are on. Get error failed to open workspace settings "xfwm4-workspace-settings" no such file

The xfce4-panel is not the place to edit workspaces. "xfwm4-workspace-settings" is for Xfce's window manager xfwm4, which we don't use. You want User Settings > Openbox > obconf - GUI config tool

johnraff · 2026-01-16 08:47:45

PackRat wrote:

Failed to boot on uEFI system...

It's supposed to work in an efi system. There have been no changes in that department since Boron which installed OK on my efi boot system.
Any hints?

Edit by PackRat: It's a hardware glitch on my end. Don't worry about it.

Last edited by johnraff (2026-01-18 05:14:27)

johnraff · 2026-01-16 08:53:22

s-rod wrote:

UPDATE: I was able to correct these issues by copying ~/.config/picom.conf from my Boron qemu host to the CarbonRC2 guest.

That's probably because the Boron picom.conf is incompatible with the current picom and made it crash. You were getting a desktop with compositing turned off, which is one way out of the issues you described.

As you found, it's the VM settings need to be changed to suit the new picom.

johnraff · 2026-01-16 09:44:47

dmontaine wrote:

Installation very very slow - paused for 10 minutes

I don't know what's happening here. There is a section where the installer doesn't show a progress bar ("configuring apt" maybe?) and seems to hang, but for me that was about 1 min, not 10! Anyway, BL customizing of the installer is minimal and shouldn't be responsible for that. How does a regular Debian Trixie installer compare on your machine?

bl-welcome did not start on first login- terminal was frozen
terminal finally freed up on 5th reboot, but no bl-welcome
tried to run bl-welcome manually, froze at "checking internet connection"
tried to apply Bark blob - system aborted with no error message
in general seemed slow and lagging

All this sounds like the same VM vs compositor issue s-rod got. Either enable 3D acceleration + openGL or disable compositing from the menu User Settings > Compositor > Disable Compositing

1) Changing to Beryllium Blob
- message that desktop wallpaper was not available
- error message about line 3097

Thank you - you've found a bug. The function that parses feh files needs a fix.
Blob should offer to install bunsen-archives at that point, to provide the needed wallpaper.
I'll upload a new bunsen-blob package as soon as the fehbg parser code has been finalized.

2) After installation of Beryllium Blob, tried to manually change background wallpaper using XW Wallpaper
- result was everything missing from desktop
- only jgmenu was available
- even network connection disappeared

I suspect this might be the continuing effects of picom needing 3D acceleration to work. If your VM can't provide that, then turn off compositing.

Last edited by johnraff (2026-01-18 05:21:48)

johnraff · 2026-01-16 09:46:13

s-rod wrote:

My concern would be that a new user might get frustrated and just give up on evaluating Bunsenlabs because it doesn't function correctly in a default qemu setup.

Valid point. We'll at least have to give this a prominent place in the Release Notes.

johnraff · 2026-01-16 09:48:14

dbvolvox wrote:

Fresh install on an HP255 laptop. Looks very nice, great job guys. I have added numlockx and put the 'numlockx on' command in .config/bunsen/autostart but it doesn't work. Is that the right place to put that command?

Yes that's the place. You remembered the ampersand at the end?

I also had to install nfs-common to get connection to my network share. Is the need for this so rare that it's not worth having in the ISO?

Any opinions?

johnraff · 2026-01-16 09:59:24

unklar wrote:

titan wrote:
Just installed it, long time since I used BL so may be operator error but
can't remove conky, can kill it from menu but like zombie it come back ( it worked on Boron)
...
I can confirm this error here on a metal installation.
The message in the ~/.xsession-errors is:
/usr/bin/bl-conky-session: There is no default session file: /home/unklar/.config/conky/conky-sessionfile, generating now...

That message is OK. The first time bl-conky-session runs it generates that file.

bl-welcome Script also offers to set up the debian-backport and bunsen-backport, which I did. Later I converted to the deb822 format using the command
sudo apt modernize-sources
executed.
It was noticeable that the backports were missing.

Both debian and BL backports? I can't confirm this problem.
I modernized via the offer in bl-welcome rather than running the command separately. Anything in ~/.cache/bunsen-welcome/bl-welcome.log ?

unklar · 2026-01-16 13:01:15

johnraff wrote:

That message is OK. The first time bl-conky-session runs it generates that file.

^That's right.
However, after removing the check mark in the CM and clicking 'apply', the file is generated again and the default conky appears again and again.

johnraff wrote:

Both debian and BL backports? I can't confirm this problem.
I modernized via the offer in bl-welcome rather than running the command separately. Anything in ~/.cache/bunsen-welcome/bl-welcome.log ?

I ran the bl-welcome-script for the 3rd time and both the .list and the .sources
have been created correctly.
Sorry for the fuss.

dbvolvox · 2026-01-16 13:20:10

johnraff wrote:

dbvolvox wrote:
Fresh install on an HP255 laptop. Looks very nice, great job guys. I have added numlockx and put the 'numlockx on' command in .config/bunsen/autostart but it doesn't work. Is that the right place to put that command?
Yes that's the place. You remembered the ampersand at the end?
I also had to install nfs-common to get connection to my network share. Is the need for this so rare that it's not worth having in the ISO?
Any opinions?

It was a PICNIC issue I finally noticed that I had a typo mum not num !!! now works without ampersand

Humble apologies all round.

#1 2026-01-13 09:00:00

Carbon RC2 bugs

#2 2026-01-13 12:01:21

Re: Carbon RC2 bugs

#3 2026-01-13 19:44:22

Re: Carbon RC2 bugs

#4 2026-01-13 20:25:43

Re: Carbon RC2 bugs

#5 2026-01-13 23:30:05

Re: Carbon RC2 bugs

#6 2026-01-14 01:30:01

Re: Carbon RC2 bugs

#7 2026-01-14 03:46:43

Re: Carbon RC2 bugs

#8 2026-01-14 16:02:10

Re: Carbon RC2 bugs

#9 2026-01-14 22:28:18

Re: Carbon RC2 bugs

#10 2026-01-15 00:30:33

Re: Carbon RC2 bugs

#11 2026-01-15 11:25:16

Re: Carbon RC2 bugs

#12 2026-01-16 08:45:17

Re: Carbon RC2 bugs

#13 2026-01-16 08:47:45

Re: Carbon RC2 bugs

#14 2026-01-16 08:53:22

Re: Carbon RC2 bugs

#15 2026-01-16 09:44:47

Re: Carbon RC2 bugs

#16 2026-01-16 09:46:13

Re: Carbon RC2 bugs

#17 2026-01-16 09:48:14

Re: Carbon RC2 bugs

#18 2026-01-16 09:59:24

Re: Carbon RC2 bugs

#19 2026-01-16 13:01:15

Re: Carbon RC2 bugs

#20 2026-01-16 13:20:10

Re: Carbon RC2 bugs

Board footer