[FINISHED] Boron Release Candidate isos available

johnraff · 2023-12-19 08:13:08

Barring any last-minute tweaks, these Release Candidate iso files should be pretty much identical with the Official Release.

The number is was RC2 because RC1 was caught up in the Debian kernel bug issue.

The website has not been updated, nor the release notes yet written, but now there is little reason for users not to install these.

EDIT: RC3 now out for a short time, till the official release.

boron-RC3-240114-amd64.hybrid.iso:
https://sourceforge.net/projects/bunsen … hybrid.iso

sha256: 92e111f1bb2c4a32a099604e77981cc51137e41ec4c541697a5f301602749597

boron-RC3-240115-i386.hybrid.iso:
https://sourceforge.net/projects/bunsen … hybrid.iso

sha256: 2890b28dc148bd8521ab18fa7c00cfba92da5129845fa4efee834bb76f86df96

Of course any feedback is still welcome!

Last edited by johnraff (2024-01-24 11:09:04)

jimjamz · 2023-12-19 12:48:07

Thanks John.

Are we OK to stick with our Boron installations from the prior Beta 2 ISO's? Hopefully an apt update/upgrade should be pick up any of the later package changes in the RC and official release ISOs?

or1o9 · 2023-12-19 16:03:17

Thanks for the good news, looking forward to switch to Boron from Beryllium soon then.

PackRat · 2023-12-19 16:12:09

Downloaded no problems.

Boots on an uEFI system and everything working out of the box.

rbh · 2023-12-19 22:06:12

jimjamz wrote:

Are we OK to stick with our Boron installations from the prior Beta 2 ISO's? Hopefully an apt update/upgrade should be pick up any of the later package changes in the RC and official release ISOs?

Yes! No need to reinstall with the new RC iso, if you have Boron.

dmontaine · 2023-12-20 00:56:02

Downloaded and installed on two computers. No problems. And, the Beryllium blob installs without issues, yea! Only thing I miss from other distros is having the option of a plain background instead of Wallpaper. I always have to create my own in GIMP.

johnraff · 2023-12-22 00:31:29

The apt "abort" issue with bl-welcome has started appearing again.
It was supposed to have been fixed three months ago.
https://forums.bunsenlabs.org/viewtopic … 54#p129654

I guess another package upgrade somewhere must have changed the behaviour of sudo in some subtle way...

temporary workaround
If when running bl-welcome after a new install, you get an apt "abort" error when the script asks you whether to continue or not, a workaround is to close the script (eg with Ctrl+C), open a new terminal and run 'bl-welcome' there.

NOTE: this only seems to be affecting urxvt, so if you are using a different terminal emulator you should be OK anyway.

UPDATE: bl-welcome now makes it easier for users, see below: https://forums.bunsenlabs.org/viewtopic … 24#p131224

Last edited by johnraff (2024-01-06 06:38:10)

hhh · 2023-12-23 13:11:06

dmontaine wrote:

Only thing I miss from other distros is having the option of a plain background instead of Wallpaper. I always have to create my own in GIMP.

Comment out the nitrogen --restore line (#94) in the ~./config/bunsen/autostart file (Main Menu>User Settings>BunsenLabs Session>Edit autostart)...

    ## Set a wallpaper
#    nitrogen --restore

Change the lightdm-gtk-greeter background from "Picture" to "Color" (Main Menu>System Settings>LightDM Interface>Appearance). Pick a color,"Save" and logout. Of course, now the login page will have a solid background as well.

If you always use the same login background image as your desktop image, you can also leave the nitrogen command commented out and just set your wallpaper from the LightDM Greeter GUI, which gets written to line #54 of /usr/share/lightdm/lightdm/lightdm.conf.d/50_bunsen.conf

hhh · 2023-12-23 13:42:30

^ Looking at this some more, and installing hsetroot is probably the best option..

sudo apt install hsetroot

Then you can leave lightdm alone and use a command instead of 'nitrogen --restore' in you autostart file...

    ## Set a wallpaper
#    nitrogen --restore
hsetroot -solid "#000000"

That sets a solid black background at login. For some reason you can't just remove the image directory from nitrogen's GUI and have it set a background color, but you can use nitrogen as a color picker to get any hex code. Open nitrogen and click on the (black by default) color swatch... a color picker and color wheel will open and the hex code will be in the "Color name:" field.

or1o9 · 2024-01-01 20:52:42

I finally got it done. Took much longer than expected, but it is impossible to plan life as usual. All well with the installation though.

walter · 2024-01-05 22:16:15

Installed RC2 as daily driver on my computer.

I made a USB drive to install it. I could boot from it and the live version worked. But installing did not worked. It was complaining the installation media could not be read. Tried it several times. Did not worked. But the live version still worked. Weird.

Created a new installation medium and that worked.

All seems well.

One of the first things I tried to do and remember was how to change the taskbar from vertical at the bottem of the screen I fairly fast found that was with the tint2 setting. The default is tint2rc

But I could not found where that setting was. Because I noticed some profiles where labeled with 'vertical' in the name I tried the one without that.
'boron-dark.tint2rc' did the trick.

Giving those profiles names not only 'vertical' but also 'horizontal' in their label would make that more obvious. I suspect that wanting to change the placing of the taskbar is common.

Last edited by walter (2024-01-05 22:16:30)

johnraff · 2024-01-06 04:37:30

walter wrote:

One of the first things I tried to do and remember was how to change the taskbar from vertical at the bottem of the screen I fairly fast found that was with the tint2 setting. The default is tint2rc
But I could not found where that setting was. Because I noticed some profiles where labeled with 'vertical' in the name I tried the one without that.
'boron-dark.tint2rc' did the trick.
Giving those profiles names not only 'vertical' but also 'horizontal' in their label would make that more obvious. I suspect that wanting to change the placing of the taskbar is common.

That sounds like a good idea - let's do it, for Boron anyway.

BTW "tint2rc" is a symlink to whatever is the default tint2 config file, for Boron that's 'boron-dark-vertical.tint2rc'.

johnraff · 2024-01-06 06:36:39

johnraff wrote:

The apt "abort" issue with bl-welcome has started appearing again.
It was supposed to have been fixed three months ago.
https://forums.bunsenlabs.org/viewtopic … 54#p129654
I guess another package upgrade somewhere must have changed the behaviour of sudo in some subtle way...
temporary workaround
If when running bl-welcome after a new install, you get an apt "abort" error when the script asks you whether to continue or not, a workaround is to close the script (eg with Ctrl+C), open a new terminal and run 'bl-welcome' there.
NOTE: this only seems to be affecting urxvt, so if you are using a different terminal emulator you should be OK anyway.

Bunsen-welcome 12.3-1 has been uploaded incorporating the above workaround. If urxvt is detected as x-terminal-emulator, then after informing the user of the issue a new terminal window is opened where they can run 'bl-welcome'.

I asked again on debian-user but nobody was able to help this time, so it doesn't look like a well-known issue. Since no other terminal emulators show that behaviour maybe it will go away in a future version of urxvt?

TO TEST:

If anyone feels like checking that the new bl-welcome is an acceptable workaround for the script+urxvt+sudo+apt issue, feedback is always welcome, plus any suggestions if the UI text could use improvement:

0) Apt update/upgrade to bring in the new bunsen-welcome 12.3-1
1) Install urxvt if it's not already: 'sudo apt install rxvt-unicode'
2) Set x-terminal-emulator to urxvt: Menu>System Settings>Edit Debian Alternatives>scroll down to x-terminal-emulator, choose /usr/bin/urxvt
3) Hit Alt+F2 for gmrun, enter 'bl-welcome'
4) After the first "Hit 'Enter' to continue" prompt, you should see a message "There is an issue with the terminal emulator urxvt..."
5) A new terminal window will pop up: enter "bl-welcome" there, and the script should start normally, and the apt prompts should work OK. (The message says "without quotes" but actually they don't matter.)
6) Instead of the Alt+F2 gmrun window, launch bl-welcome from a regular terminal and confirm that none of that "issue" stuff comes up, it just works. (The issue depends on being launched without a terminal.)
7) Set x-terminal-emulator to anything except urxvt, and confirm that there is no warning, no popup and no issue with apt prompts, whether launched from gmrun or a terminal.

Thanks!

Last edited by johnraff (2024-01-07 05:44:53)

walter · 2024-01-06 14:38:32

Some other things I noticed;

I added the repository for the Belgian eID card. The middleware to be login on websites (smartcard) and the program 'eID Viewer' to read out the ID card and change the pincode.
https://eid.belgium.be/en/linux-eid-sof … stallation

Debian 11 and 12 is officially supported. Installing the middle ware (eid-mw) is not a problem (and it works).

eid-viewer does not install. It does show up but only the version for debian 11 is listed. (used Synaptic , 'properties' -> 'versions')

I installed in a VM a fresh version of Beryllium and Debian 12. - And done the same there.

eid-viewer (version for debian 11) works on Berylium. And also on Debian 12. The version of eid-viewer for debian 12 shows up like it should be.

So there must be something be that makes that Boron is not the same as Debian 12 in this context. So that the version for Debian 12 is not used on RC2 Boron for this software.

That I can not install eid-viewer is not important itself. - And obviously this is not supported by BunsenLabs. - But maybe the reason of this points to something larger. More relevant for more people.

I thought I found an other case. I wanted to install 'Openshot'. I used the easy install function 'install favorite packages' it did not worked. Got an error that it could not be installed.

But when I just run ' sudo apt install openshot-qt' that worked fine.

Last edited by walter (2024-01-06 14:48:38)

johnraff · 2024-01-07 06:16:34

Thanks for the feedback!

walter wrote:

eid-viewer does not install. It does show up but only the version for debian 11 is listed. (used Synaptic , 'properties' -> 'versions')

According to https://eid.belgium.be/en/future-versio … eid-viewer

There are currently no future versions available for Linux.

Which is not encouraging.
But there are packages in their repository intended to be used by Debian Bookworm, including eid-viewer 5.1.13v5.1.13-0deb12-1. Please bear in mind, though, that with third-party repositories like this, nothing is guaranteed to work.

eid-viewer does not install. It does show up but only the version for debian 11 is listed. (used Synaptic , 'properties' -> 'versions')
I installed in a VM a fresh version of Beryllium and Debian 12. - And done the same there.
eid-viewer (version for debian 11) works on Berylium. And also on Debian 12. The version of eid-viewer for debian 12 shows up like it should be.
So there must be something be that makes that Boron is not the same as Debian 12 in this context. So that the version for Debian 12 is not used on RC2 Boron for this software.

BL Boron is Debian 12, so there should be no differences in the basic system at all.
If you have the time, could you please run 'apt policy eid-viewer' in a terminal in each of the three systems you are comparing, and post the results here.
Also 'cat /etc/apt/sources.list.d/eid.list' might help.

That I can not install eid-viewer is not important itself. - And obviously this is not supported by BunsenLabs. - But maybe the reason of this points to something larger. More relevant for more people.

Indeed. And thanks for bringing it up. Anything that works on Debian 12 should also work on Boron.

I thought I found an other case. I wanted to install 'Openshot'. I used the easy install function 'install favorite packages' it did not worked. Got an error that it could not be installed.
https://i.imgur.com/XtmqBXo.png
But when I just run ' sudo apt install openshot-qt' that worked fine.

OK this is a bug, and thanks for finding it. The package 'openshot' has been a transitional package to openshot-qt for several releases now, and in Bookworm it was finally removed, but nobody noticed. We need to edit the script to install openshot-qt instead of openshot. By the way, can you confirm that the command to call it is still 'openshot', not 'openshot-qt'?

We'll get the fix in an updated bunsen-pipemenus before the final Boron release.

walter · 2024-01-07 12:48:21

johnraff wrote:

There are currently no future versions available for Linux.
Which is not encouraging.

There are also no new upcoming for Mac or Windows. Linux has been very well supported for this. The eID exist 20 years and so this software. This is mature.

johnraff wrote:

BL Boron is Debian 12, so there should be no differences in the basic system at all.
If you have the time, could you please run 'apt policy eid-viewer' in a terminal in each of the three systems you are comparing, and post the results here.
Also 'cat /etc/apt/sources.list.d/eid.list' might help.

Certainly!

On hardware, my computer running RC2:

walter@hpbunsen:~$ apt policy eid-viewer
eid-viewer:
Geïnstalleerd: (geen)
Kandidaat:     5.1.13v5.1.13-0deb11-1
Versietabel:
 5.1.13v5.1.13-0deb11-1 500
  500 https://files.eid.belgium.be/debian bullseye/main amd64 Packages

walter@hpbunsen:~$ cat /etc/apt/sources.list.d/eid.list
# To enable the candidate repository, uncomment the below line, put "deb" in
# front of it, and run "dpkg-reconfigure eid-archive" to enable the archive
# key.

# The candidate repository contains unsupported prerelease packages. Use at
# your own risk.

# Note, however, that the candidate repository is usually empty; it is
# used when we're preparing (and testing) a new release. Therefore, it
# should be relatively safe.

# There is also another "continuous" repository, for which packages get
# recompiled for each and every change to the source. This isn't listed
# (so that it can't be accidentally enabled), but the configuration is
# the same as the below, with "candidate" replaced by "continuous".

# http://files.eid.belgium.be/debian candidate/bullseye main

# The regular repository with released packages. This is what you should
# use.
deb https://files.eid.belgium.be/debian/ bullseye main 

walter@hpbunsen:~$

The fresh VM running Berrilium. Here it all works as it did before on my real computer with this install.

walter@debian11bunsenlabs:~$ apt policy eid-viewer
eid-viewer:
  Geïnstalleerd: 5.1.13v5.1.13-0deb11-1
  Kandidaat:     5.1.13v5.1.13-0deb11-1
  Versietabel:
*** 5.1.13v5.1.13-0deb11-1 500
        500 https://files.eid.belgium.be/debian bullseye/main amd64 Packages
        100 /var/lib/dpkg/status
walter@debian11bunsenlabs:~$

walter@debian11bunsenlabs:~$ cat /etc/apt/sources.list.d/eid.list
# To enable the candidate repository, uncomment the below line, put "deb" in
# front of it, and run "dpkg-reconfigure eid-archive" to enable the archive
# key.
#
# The candidate repository contains unsupported prerelease packages. Use at
# your own risk.
#
# Note, however, that the candidate repository is usually empty; it is
# used when we're preparing (and testing) a new release. Therefore, it
# should be relatively safe.
#
# There is also another "continuous" repository, for which packages get
# recompiled for each and every change to the source. This isn't listed
# (so that it can't be accidentally enabled), but the configuration is
# the same as the below, with "candidate" replaced by "continuous".
#
# http://files.eid.belgium.be/debian candidate/bullseye main

# The regular repository with released packages. This is what you should
# use.
deb https://files.eid.belgium.be/debian bullseye main
walter@debian11bunsenlabs:~$

And then just the latest stock Debian 12, fresh install, in VM

walter@Debian12native:~$ apt policy eid-viewer
eid-viewer:
  Geïnstalleerd: 5.1.13v5.1.13-0deb12-1
  Kandidaat:     5.1.13v5.1.13-0deb12-1
  Versietabel:
*** 5.1.13v5.1.13-0deb12-1 500
        500 https://files.eid.belgium.be/debian bookworm/main amd64 Packages
        100 /var/lib/dpkg/status
walter@Debian12native:~$

walter@Debian12native:~$ cat /etc/apt/sources.list.d/eid.list
# To enable the candidate repository, uncomment the below line, put "deb" in
# front of it, and run "dpkg-reconfigure eid-archive" to enable the archive
# key.
#
# The candidate repository contains unsupported prerelease packages. Use at
# your own risk.
#
# Note, however, that the candidate repository is usually empty; it is
# used when we're preparing (and testing) a new release. Therefore, it
# should be relatively safe.
#
# There is also another "continuous" repository, for which packages get
# recompiled for each and every change to the source. This isn't listed
# (so that it can't be accidentally enabled), but the configuration is
# the same as the below, with "candidate" replaced by "continuous".
#
# http://files.eid.belgium.be/debian candidate/bookworm main

# The regular repository with released packages. This is what you should
# use.
deb https://files.eid.belgium.be/debian bookworm main
walter@Debian12native:~$

... and yes, I see it also now. The 100 /var/lib/dpkg/status line is the difference.

johnraff wrote:

OK this is a bug, and thanks for finding it. The package 'openshot' has been a transitional package to openshot-qt for several releases now, and in Bookworm it was finally removed, but nobody noticed. We need to edit the script to install openshot-qt instead of openshot. By the way, can you confirm that the command to call it is still 'openshot', not 'openshot-qt'?
We'll get the fix in an updated bunsen-pipemenus before the final Boron release.

When the build in function by the menu option to install openshot did not worked I looked it up in Synaptic .

There was (and is) no 'openshot'. There was 'openshot-qt'.

So I installed it in the terminal with as 'openshot-qt'

I just also looked in the Debian 12 install. There is there also no 'openshot' package. What is available looks identical as in RC2 Boron (what it should be). And obviously installing 'openshot' does not work there.

walter@Debian12native:~$ sudo apt install openshot
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd... Klaar
De statusinformatie wordt gelezen... Klaar
Pakket openshot is niet beschikbaar, hoewel er naar verwezen wordt door
een ander pakket. Mogelijk betekent dit dat het pakket ontbreekt,
verouderd is, of enkel beschikbaar is van een andere bron

E: Pakket 'openshot' heeft geen kandidaat voor installatie
walter@Debian12native:~$

EDIT:

I misunderstood your question.

'openshot' does not work to start openshot. - 'openshot-qt' does work (RC2 Boron)

Also tested it on Debian 12: it is the same

EDIT 2:

I have installed in fresh install of RC2 every option available from the 'install favorite packages' .
Besides 'openshot' they all work. And the menu entry is removed.

Last edited by walter (2024-01-07 19:32:22)

johnraff · 2024-01-08 00:30:47

Hi Walter, thanks for the help!

I think I've found the problem with eid-viewer on Boron:

johnraff wrote:

BL Boron is Debian 12, so there should be no differences in the basic system at all.

Well, that is almost true, except that the package bunsen-os-release reports the system Codename as "Boron", not "Bullseye". That causes the eid-archive postinstall script to fall back on Debian bullseye as the apt repository to use, instead of Bookworm.

Two ways to fix this in your Boron system:
1) Edit /etc/apt/sources.list.d/eid.list as root, changing 'bullseye' to 'bookworm:

deb https://files.eid.belgium.be/debian bookworm main

then 'sudo apt update'.
or
2)

sudo apt purge bunsen-os-release
sudo apt purge eid-mw
sudo apt purge eid-archive
sudo apt update

Now install eid-archive again. Without bunsen-os-release on the system it should set the correct eid repository.
Install the other eid packages you want.
Finally, you can install bunsen-os-release again so that the grub menu will show "BunsenLabs".

I will adjust the install pipemenu, thanks to your feedback.

And thanks also for checking the other install entries!

Last edited by johnraff (2024-01-08 07:58:53)

walter · 2024-01-08 17:43:59

Thank you johnraff. - It works now. - Have reported this to maintainers of eID. Maybe the can add 'boron' as an alias for 'bookworm'.

That also explains why it worked on Berillium. As the fallback is the correct one. This was actually very basic and I should have found that myself. A learning moment.

johnraff · 2024-01-09 04:25:17

Glad we got that sorted.

It leaves the tricky question of whether it would be better for bunsen-os-release to set the Codename to bookworm or buster. Needs some thought...

---
The script that sets up the eid repository should be in /var/lib/info/eid-archive.postinst
and it's getting its information about the system from three calls to lsb_release:

CODE=$(lsb_release -c -s)
DIST=$(lsb_release -i -s)
REL=$(lsb_release -r -s)

lsb_release uses the data in /usr/lib/os-release, installed by bunsen-os-release.

johnraff · 2024-01-09 05:35:14

johnraff wrote:

It leaves the tricky question of whether it would be better for bunsen-os-release to set the Codename to bookworm or buster. Needs some thought...

I was almost deciding to set VERSION_CODENAME=bookworm to make life easier for third-party install scripts, but after all, it's not really true, and would be inconsistent with VERSION="12 (Boron)" and VERSION_ID="12" which are the BL versions (even though 12 also matches Debian).

ID_LIKE=debian is set already and would be a useful fallback if there was an equivalent VERSION_ID_LIKE to set to bookworm, but there isn't at the moment:

https://www.freedesktop.org/software/sy … lease.html

#1 2023-12-19 08:13:08

[FINISHED] Boron Release Candidate isos available

#2 2023-12-19 12:48:07

Re: [FINISHED] Boron Release Candidate isos available

#3 2023-12-19 16:03:17

Re: [FINISHED] Boron Release Candidate isos available

#4 2023-12-19 16:12:09

Re: [FINISHED] Boron Release Candidate isos available

#5 2023-12-19 22:06:12

Re: [FINISHED] Boron Release Candidate isos available

#6 2023-12-20 00:56:02

Re: [FINISHED] Boron Release Candidate isos available

#7 2023-12-22 00:31:29

Re: [FINISHED] Boron Release Candidate isos available

#8 2023-12-23 13:11:06

Re: [FINISHED] Boron Release Candidate isos available

#9 2023-12-23 13:42:30

Re: [FINISHED] Boron Release Candidate isos available

#10 2024-01-01 20:52:42

Re: [FINISHED] Boron Release Candidate isos available

#11 2024-01-05 22:16:15

Re: [FINISHED] Boron Release Candidate isos available

#12 2024-01-06 04:37:30

Re: [FINISHED] Boron Release Candidate isos available

#13 2024-01-06 06:36:39

Re: [FINISHED] Boron Release Candidate isos available

#14 2024-01-06 14:38:32

Re: [FINISHED] Boron Release Candidate isos available

#15 2024-01-07 06:16:34

Re: [FINISHED] Boron Release Candidate isos available

#16 2024-01-07 12:48:21

Re: [FINISHED] Boron Release Candidate isos available

#17 2024-01-08 00:30:47

Re: [FINISHED] Boron Release Candidate isos available

#18 2024-01-08 17:43:59

Re: [FINISHED] Boron Release Candidate isos available

#19 2024-01-09 04:25:17

Re: [FINISHED] Boron Release Candidate isos available

#20 2024-01-09 05:35:14

Re: [FINISHED] Boron Release Candidate isos available

Board footer