Boron Beta 2 isos available, amd64 and i386

johnraff · 2023-10-11 02:57:08

NOTE: there are now Release Candidate isos available, so if you're making a fresh install they are recommended:
https://forums.bunsenlabs.org/viewtopic.php?id=8793

As the official release draws near, we have Beta 2 RC2 iso files for people to check out. This is very close to what the official release will be - the only possible differences will be small things that are fixed by package upgrades - so if you don't feel like waiting any more then by all means go ahead and install BunsenLabs Boron from these files.

Please post any issues you might find, though!

Last edited by johnraff (2023-12-23 06:22:28)

Pinhead · 2023-10-11 16:28:34

Installed. Everything OK so far.
I only had to fix the screen tearing (intel card) and I will have to set up something for keyboard switching (ibus) and numlockx...

The logout command takes 1.5 min.

Last edited by Pinhead (2023-10-11 19:13:34)

or1o9 · 2023-10-11 19:48:34

Installed ok.Will get back to you if there is something weird. Great work team, thank you.

rbh · 2023-10-11 21:29:33

johnraff wrote:

https://sourceforge.net/projects/bunsenlabs-releases

Can you upload SHA256 checksum files?

johnraff · 2023-10-12 05:07:28

Pinhead wrote:

Installed. Everything OK so far.

Thanks for testing!

I only had to fix the screen tearing (intel card)

What did you do to fix tearing? I have an intel graphics card too.

The logout command takes 1.5 min.

That's... a bit long. If it continues that way, maybe you could start a support topic in Kernel & Hardware? I'm not a hardware wiz but somebody might be able to help.

johnraff · 2023-10-12 05:30:22

rbh wrote:

johnraff wrote:
https://sourceforge.net/projects/bunsenlabs-releases
Can you upload SHA256 checksum files?

OK done for the two latest isos.

Pinhead · 2023-10-12 05:37:41

What did you do to fix tearing? I have an intel graphics card too.

/etc/X11/xorg.conf.d/20-intel.conf

Section "Device"
    Identifier "Intel Graphics"
    Driver "intel"
    Option "TearFree"    "true"
    Option "AccelMod"    "uxa"
    Option "DRI"         "3"
EndSection

or just

Section "Device"
    Identifier "Intel Graphics"
    Driver "intel"
    Option "TearFree"    "true"
EndSection

Screen Tearing Test

That's... a bit long. If it continues that way, maybe you could start a support topic in Kernel & Hardware? I'm not a hardware wiz but somebody might be able to help.

I knew I'd seen it somewhere before...

Lithium logout - delay displaying login fields again

Last edited by Pinhead (2023-10-12 06:03:51)

johnraff · 2023-10-12 06:46:34

Pinhead wrote:

What did you do to fix tearing? I have an intel graphics card too.
/etc/X11/xorg.conf.d/20-intel.conf
Section "Device"
    Identifier "Intel Graphics"
    Driver "intel"
    Option "TearFree"    "true"
    Option "AccelMod"    "uxa"
    Option "DRI"         "3"
EndSection
or just
Section "Device"
    Identifier "Intel Graphics"
    Driver "intel"
    Option "TearFree"    "true"
EndSection
Screen Tearing Test

Thanks. I did have some jagged edges on those bars, so tried that xorg config. Unfortunately both versions broke my X server: "lightdm failed to start". This is still a Bullseye system - if Bookworm is no different then I guess not all Intel graphics cards are equal.

---

That's... a bit long. If it continues that way, maybe you could start a support topic in Kernel & Hardware? I'm not a hardware wiz but somebody might be able to help.
I knew I'd seen it somewhere before...
Lithium logout - delay displaying login fields again

Now I remember occasionally getting those long black logout screens too. It seems a very long time ago that it last hit though. At the time I often found that logging into another TTY then going back to TTY 7 would break the jam. Sometimes just momentarily switching TTY was enough. If there are no hints in the thread you found, and the problem persists, please open a new thread.

rbh · 2023-10-12 17:15:22

Package xfce4-appfinder
Categories not visible. One have to choose hide categories and then unhide, to show them.
If we in ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-appfinder.xml add:

<property name="hide-category-pane" type="bool" value="false"/>

will categories be visible with first start.

Package bunsen-apt-update-checker:
File /usr/bin/bl-apt-update-check
Row 99: x-terminal-emulator -T 'Available Package Upgrades' -e sh -c 'printf "%s\n" "Available upgrades:"; apt list --upgradeable; printf "\n%s\n" "Held packages:"; apt-mark showhold; bash
Add flag --norc to bash. This stops bash from sourcing .bashrc. Many have neofetch and other commands and aliases starting from .bashrc, and we don't want that to be started with bunsen-apt-update-checker.
Change line to:

x-terminal-emulator -T 'Available Package Upgrades' -e sh -c 'printf "%s\n" "Available upgrades:"; apt list --upgradeable; printf "\n%s\n" "Held packages:"; apt-mark showhold; bash --norc ;'

Lightlocker when turned on by powersawings:
After unlocking, screen-resolution has returned to default low-res.
I have to set screen resolution again after unlocking.

64 bit iso:
Meld is available in live session but is missing in installed system. I wiped the beta1 install, can not check, but am sure meld was there...

rbh · 2023-10-12 22:01:57

Iso-boot with grml-rescueboot, now works wit 64 bit iso but not with the 32 bit.

hhh · 2023-10-12 23:34:02

re: intel tearing...

https://www.dedoimedo.com/computers/lin … aring.html

Use inxi -G to ID your driver, it will appear under "loaded:". Of course, reboot. I use this video to test...

https://www.youtube.com/watch?v=SD-31Q2IgKU

The test is hard on graphics, but you should see noticeable improvement.

@Pinhead, if you're only using bl-exit to logout of BunsenLabs/Openbox, you could hack bl-exit by copying it to the bin folder in your home directory, make sure it's still executable, and change line #184 to...

        --button=" _Logout!system-log-out!Logout":'bash -c "openbox --exit"' \

hhh · 2023-10-12 23:55:32

I couldn't get the 64 bit install to work... until I realized I had an HDMI cable still plugged in but my TV turned off!

This release is still using xorg-synaptics for touchpad controls, yes? Can we enable touchpad two-finger/3 finger clicks, maybe as a commented out option in autostart? Something that would show some more touchpad options? I'm currently using this...

synclient VertEdgeScroll=0 VertTwoFingerScroll=0 HorizEdgeScroll=0 TapButton1=1 TapButton2=3 TapButton3=2 PalmDetect=1

Yes, I hate edge scrolling. The PalmDetect option has reduced typing mistakes/cursor suddenly appearing somewhere else considerably on my laptop (cheap IdeaPad 3, it has a very large touchpad).

johnraff · 2023-10-13 05:40:54

@rbh thanks for the detailed report.

rbh wrote:

Package xfce4-appfinder
Categories not visible. One have to choose hide categories and then unhide, to show them.

I found the "hide categories" option was checked by default, so I only had to uncheck it to show the categories pane. Anyway, new users would likely not notice that option at first, so let's indeed display the categories by default, with the xml line you suggest. While checking the file, I noticed a bug: an unwanted '</property>' line, which might have been causing the app to reject the config we had to inhibit the daemon.

If we in ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-appfinder.xml add:
<property name="hide-category-pane" type="bool" value="false"/>
will categories be visible with first start.

I'll do that.

Package bunsen-apt-update-checker:
File /usr/bin/bl-apt-update-check
Row 99: x-terminal-emulator -T 'Available Package Upgrades' -e sh -c 'printf "%s\n" "Available upgrades:"; apt list --upgradeable; printf "\n%s\n" "Held packages:"; apt-mark showhold; bash
Add flag --norc to bash. This stops bash from sourcing .bashrc. Many have neofetch and other commands and aliases starting from .bashrc, and we don't want that to be started with bunsen-apt-update-checker.

I'm not so sure this is a problem. The purpose of bunsen-apt-update-checker is only to check. It informs the user of the situation, then gives them a normal terminal to run any commands they want. (Usually that would be 'sudo apt upgrade', but if there's some complication they might want to run some other apt or dpkg commands.) The 'bash' command just starts a terminal session the same as if they had opened a terminal any other way, eg Win+T. Users who display neofetch every time they open a terminal can go on doing so if they want. There's no reason we should stop them just because the terminal was triggered by bunsen-apt-update-checker. As for aliases, I think users should be able to continue relying on them - maybe they have some aliases related to apt commands.

Or have I missed some problem?

Lightlocker when turned on by powersawings:
After unlocking, screen-resolution has returned to default low-res.
I have to set screen resolution again after unlocking.

I don't see any change when locking with win+L. Can you tell me how to reproduce this problem? Is it in a VM or real hardware?

64 bit iso:
Meld is available in live session but is missing in installed system. I wiped the beta1 install, can not check, but am sure meld was there...

Meld is not in any of the package lists I could find, but it is a Suggests of bunsen-blob. That's the only link I could find.

Iso-boot with grml-rescueboot, now works wit 64 bit iso but not with the 32 bit.

It should have worked with the 64bit iso all along, but I thought I had fixed the issue which was interfering with booting on some devices in the 32bit build. I'll have another look, but this might take a little longer...

johnraff · 2023-10-13 06:32:27

Re: tearing with intel

Both lspci "Kernel driver in use: i915" and inxi "driver: i915" were misleading about the graphics driver, and
Driver "intel"
and
Driver "i915"
both broke X.

Inxi did have further down "loaded: modesetting" and another hint came from 'grep "LoadModule" /var/log/Xorg.0.log' where i915 did not appear but "modesetting" did.

So
Driver "modesetting"
did not break the X session.

Unfortunately it did not help the tearing.
Finally, I found tearfree is not yet available with modesetting, at least on my system, likely not on Bookworm either:
https://www.reddit.com/r/archlinux/comm … available/
https://www.phoronix.com/news/xf86-vide … g-TearFree

Ah well, there's likely some picom setting...

Last edited by johnraff (2023-10-13 06:36:57)

johnraff · 2023-10-13 06:45:08

hhh wrote:

This release is still using xorg-synaptics for touchpad controls, yes? Can we enable touchpad two-finger/3 finger clicks, maybe as a commented out option in autostart? Something that would show some more touchpad options? I'm currently using this...
synclient VertEdgeScroll=0 VertTwoFingerScroll=0 HorizEdgeScroll=0 TapButton1=1 TapButton2=3 TapButton3=2 PalmDetect=1
Yes, I hate edge scrolling. The PalmDetect option has reduced typing mistakes/cursor suddenly appearing somewhere else considerably on my laptop (cheap IdeaPad 3, it has a very large touchpad).

We're currently installing:
xserver-xorg-input-synaptics
xserver-xorg-input-evdev
and I think synaptics takes precedence with the touchpad settings. (We discussed this some time ago.)
This is what we currently have in ~/.config/bunsen/autostart:

### TOUCHPAD: comment out the next two entries if you don't have one

## Configure touchpad. See 'man synaptics' for more info.
## (Now might be using libinput instead of synaptics.)
synclient VertEdgeScroll=1 HorizEdgeScroll=1 TapButton1=1 2>/dev/null

## Disable touchpad while typing
syndaemon -i .5 -K -t -R -d &

Not sure I hate edge scrolling as much as you. How else do you scroll with a touchpad?
I think default settings should enable things new users might want, rather than leave them struggling to find the settings.

Anyway no harm in adding some commented-out options, maybe with brief explanations. What would you suggest?

hhh · 2023-10-13 10:32:21

I scroll with page up/page down and arrow up/arrow down.

Let's get some feedback before we add or change anything.

So, no luck with this 20-intel.conf config?

Section "Device"
  Identifier "Intel Graphics"
  Driver "modesetting"
  Option "TearFree" "true"
EndSection

https://wiki.archlinux.org/title/intel_ … leshooting

hhh · 2023-10-13 11:00:11

johnraff wrote:

... I thought I had fixed the issue which was interfering with booting on some devices in the 32bit build. I'll have another look, but this might take a little longer...

No lucking booting the 32 bit on my Ideapad 3, the USB still isn't recognized by the BIOS.

Don't spend too much time on this, it boots fine on 32 bit laptops.

rbh · 2023-10-13 15:47:52

johnraff wrote:

@rbh thanks for the detailed report.
rbh wrote:
Package bunsen-apt-update-checker:
I'm not so sure this is a problem.

The user wants to show a list of updates. If neofetch is started from .bashrc, it is run after the listing and the listing is srcolled out of sight. To see the list, user has to scroll back. That is a slight problem.

The 'bash' command just starts a terminal session the same as if they had opened a terminal any other way, eg Win+T.

No. If you omit the "bash" command from the script, the terminal will pop up, list available upgrades if any and close before you had any chance to se the output. The command "bash", makes the terminal to stay open.

Users who display neofetch every time they open a terminal can go on doing so if they want. There's no reason we should stop them just because the terminal was triggered by bunsen-apt-update-checker.

I dont think so many users would like to show neofetch output after the listing of available upgrades. That is not a sane default. The best is to append "--norc" to "bash". The prompt will change to "bash-5.2", but all sudo commands can be executed as usual.
If user in an very rare situation would need some setting from .bashrc, it is only to give command "bash", without any flag.

Or have I missed some problem?

In real life and BunsenLabs/Debian, there are often both pros and cons to a solution. My proposal offers more advantages than disadvantages

Lightlocker when turned on by powersawings:
After unlocking, screen-resolution has returned to default low-res.

I don't see any change when locking with win+L.

Me neither.
As I wrote, it happens when powersawings set the computer to sleep and lock it. But, I should remember to tell it's only in VirtualBox VM.
I tested now, to sett powersavings to only suspend, not lock, when inactive for 15 min. Then, I could not wake guest.

Meld is not in any of the package lists I could find, but it is a Suggests of bunsen-blob. That's the only link I could find.

I thought meld was installed on purpose. It is much easier to fix dotfiles the way you wqnt to, with meld, when BL upgrades dotfiles...
Weird, it is in live iso but not in installed system. Maybe good idea to add it?

[Iso-boot with grml-rescueboot,]

It should have worked with the 64bit iso all along, but I thought I had fixed the issue which was interfering with booting on some devices in the 32bit build.

Ah, rememberd wrong. The corona flu severely inhibited my memory.

Last edited by rbh (2023-10-13 15:48:49)

johnraff · 2023-10-14 02:01:16

hhh wrote:

So, no luck with this 20-intel.conf config?
Section "Device"
  Identifier "Intel Graphics"
  Driver "modesetting"
  Option "TearFree" "true"
EndSection
https://wiki.archlinux.org/title/intel_ … leshooting

No. 'Driver "modesetting"' does not break X, but the "TearFree" option is not available. I'll have another look after I upgrade to Bookworm.

johnraff · 2023-10-14 03:38:02

rbh wrote:

johnraff wrote:
@rbh thanks for the detailed report.
rbh wrote:
Package bunsen-apt-update-checker:
I'm not so sure this is a problem.
The user wants to show a list of updates. If neofetch is started from .bashrc, it is run after the listing and the listing is srcolled out of sight. To see the list, user has to scroll back. That is a slight problem.

Yes, agreed.

The 'bash' command just starts a terminal session the same as if they had opened a terminal any other way, eg Win+T.
No. If you omit the "bash" command from the script, the terminal will pop up, list available upgrades if any and close before you had any chance to se the output. The command "bash", makes the terminal to stay open.

There are other ways to make the terminal stay open. The purpose of the bash call is to give the user immediate access to a terminal so they can upgrade (if they want to).

Users who display neofetch every time they open a terminal can go on doing so if they want. There's no reason we should stop them just because the terminal was triggered by bunsen-apt-update-checker.
I dont think so many users would like to show neofetch output after the listing of available upgrades. That is not a sane default.

Personally, I don't think it's a sane default to put in .bashrc, but anyway...

The best is to append "--norc" to "bash". The prompt will change to "bash-5.2", but all sudo commands can be executed as usual.
If user in an very rare situation would need some setting from .bashrc, it is only to give command "bash", without any flag.

So we are comparing the rarity of users who run neofetch first with every terminal, with that of users who have some bash aliases related to apt package handling...

In real life and BunsenLabs/Debian, there are often both pros and cons to a solution. My proposal offers more advantages than disadvantages

Without running a full user survey it's impossible to say that for sure.
But anyway, I can see a better solution:
After displaying the package information, a prompt "press any key for a terminal" or "press Enter for a terminal". So the 'bash' call waits till user has finished reading the info. In that case neofetch would be no problem, and user is already aware of the package info above. This would be easy to implement with a one-line use of 'read'.

Lightlocker when turned on by powersawings:
After unlocking, screen-resolution has returned to default low-res.
I don't see any change when locking with win+L.
Me neither.
As I wrote, it happens when powersawings set the computer to sleep and lock it. But, I should remember to tell it's only in VirtualBox VM.
I tested now, to sett powersavings to only suspend, not lock, when inactive for 15 min. Then, I could not wake guest.

Please give me exact instructions - power manager settings - on how to reproduce the low-res issue.

"Unable to wake guest" is another issue, possibly related to this?

Meld is not in any of the package lists I could find, but it is a Suggests of bunsen-blob. That's the only link I could find.
I thought meld was installed on purpose. It is much easier to fix dotfiles the way you wqnt to, with meld, when BL upgrades dotfiles...
Weird, it is in live iso but not in installed system. Maybe good idea to add it?

Meld is not present in the live system of either i386 or amd64 Beta 2 - I just checked. Maybe you installed it? It's a useful piece of software which I use all the time, but bl-user-setup will use diff directly in the terminal if meld (or kompare or diffuse) is not available so meld is not absolutely necessary.

[Iso-boot with grml-rescueboot,]

I'm working on this now. I don't understand why, even with my hook disabled, the 32bit iso does not have version-numbered vmlinuz and intrd.gz files, while the 64bit iso does...

#1 2023-10-11 02:57:08

Boron Beta 2 isos available, amd64 and i386

#2 2023-10-11 16:28:34

Re: Boron Beta 2 isos available, amd64 and i386

#3 2023-10-11 19:48:34

Re: Boron Beta 2 isos available, amd64 and i386

#4 2023-10-11 21:29:33

Re: Boron Beta 2 isos available, amd64 and i386

#5 2023-10-12 05:07:28

Re: Boron Beta 2 isos available, amd64 and i386

#6 2023-10-12 05:30:22

Re: Boron Beta 2 isos available, amd64 and i386

#7 2023-10-12 05:37:41

Re: Boron Beta 2 isos available, amd64 and i386

#8 2023-10-12 06:46:34

Re: Boron Beta 2 isos available, amd64 and i386

#9 2023-10-12 17:15:22

Re: Boron Beta 2 isos available, amd64 and i386

#10 2023-10-12 22:01:57

Re: Boron Beta 2 isos available, amd64 and i386

#11 2023-10-12 23:34:02

Re: Boron Beta 2 isos available, amd64 and i386

#12 2023-10-12 23:55:32

Re: Boron Beta 2 isos available, amd64 and i386

#13 2023-10-13 05:40:54

Re: Boron Beta 2 isos available, amd64 and i386

#14 2023-10-13 06:32:27

Re: Boron Beta 2 isos available, amd64 and i386

#15 2023-10-13 06:45:08

Re: Boron Beta 2 isos available, amd64 and i386

#16 2023-10-13 10:32:21

Re: Boron Beta 2 isos available, amd64 and i386

#17 2023-10-13 11:00:11

Re: Boron Beta 2 isos available, amd64 and i386

#18 2023-10-13 15:47:52

Re: Boron Beta 2 isos available, amd64 and i386

#19 2023-10-14 02:01:16

Re: Boron Beta 2 isos available, amd64 and i386

#20 2023-10-14 03:38:02

Re: Boron Beta 2 isos available, amd64 and i386

Board footer