Boron Beta 2 isos available, amd64 and i386

johnraff · 2023-10-14 06:33:13

hhh wrote:

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

Page up/page down and arrow up/arrow down on an open text file moves the cursor. That's quite different from scrolling with the mouse wheel or edge of touchpad which lets you view a different section of the file.

dmontaine · 2023-10-14 06:54:43

Someone needs to go through all the blobs to make sure they load correctly. For example, the lithium blob does not change the color scheme and does not load the background. Also the current horizontal bar has a height that is larger than in previous versions of Bunsenlabs. The height is not changed when you select a Lithium or Beryllium horizontal bar, so the wallpaper does not fit as well.

Last edited by dmontaine (2023-10-14 07:06:27)

johnraff · 2023-10-14 08:12:00

johnraff wrote:

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

OK that was easily explained - I was looking at the beta1 iso.

I now see that both 32 bit and 64 bit beta 2 isos hold generic vmlinuz and vmlinuz-<version> files, same for initrd.img.
So I can't see where the 32 bit grml and Ideapad failures to boot come from.

@rbh and @hhh any error messages that might help?

johnraff · 2023-10-14 08:14:55

dmontaine wrote:

Someone needs to go through all the blobs to make sure they load correctly.

All help is gratefully accepted!

Bonus points if you post any error messages.

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

rbh wrote:

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 ;'

johnraff wrote:

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

Try this line:

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; printf "\n%s\n" "Press Enter to get a bash shell"; read -r _ ; bash ;'

hhh · 2023-10-14 11:12:42

^ Just this from the Beryllium 32 bit ISO...

https://forums.bunsenlabs.org/viewtopic … 93#p129793

re: edge scrolling... Page up/down, arrows and space-bar do scroll a text editor or a browser page, as long as the cursor isn't in a text box or form field, and of course there are scroll bars, but I'm not suggesting disabling vertical scroll from our synclient. I am suggesting adding touchpad right and middle clicks, and possibly palm detection, but we've had no feedback yet. My hate for touchpad scrolling is that I do it accidentally all the time if it's enabled. Maybe I have fat palms? Spastic fingers? I don't know.

Actual feedback... where's the update-notifier icon coming from? It's way darker in the default setup than the other systray icons.

As far as stability and usability of the ISOs, I think we're good to go.

johnraff · 2023-10-15 00:14:57

^Did you get this error message from Beta2, or is that beta1?

hhh wrote:

I tried the Install entry and got this message...
error: file `/live/vmlinuz-5.10.0-2.0-686' not found
error: You need to load the kernel first

I ask because while a versioned vmlinuz was indeed missing in Beta1, /live/vmlinuz-6.1.0-13-686 is present in Beta2.

That also raises the question of why the error message was about an older kernel. If it's looking for the wrong version anyway, that's another clue.

So if you have a moment, could you check the message again with Beta2? Thanks!

...
Scrolling: yes the arrows work fine in a browser page but the main time I need real scrolling is when looking at a long page of code in a text editor. I want to look here and there in the file without losing where the cursor is. The terminal is another place - how can you look at a long command output without scrolling? Arrow keys just go back a command. Actually scrolling, even with touchpad edge enabled, is the biggest area of annoyance for me when using a laptop.

Last edited by johnraff (2023-10-15 01:03:36)

johnraff · 2023-10-15 00:46:33

hhh wrote:

Actual feedback... where's the update-notifier icon coming from? It's way darker in the default setup than the other systray icons.

It's a call to "software-update-available".

john@bookworm-tmp:~$ find /usr/share/icons/Numix* -iname '*software-update-available*'
/usr/share/icons/Numix/scalable/status/software-update-available-symbolic.svg
/usr/share/icons/Numix-Light/scalable/status/software-update-available-symbolic.svg

The Numix icon is light grey, not black like the Numix-Light variant. Even yad-icon-browser shows the light grey version when using Numix-Bunsen-Circle-aqua (not light) icons.

So I don't know why the black icon is being chosen. I thought at first it was because Numix wasn't shipping a light-coloured icon for dark themes, but I now see that's not the case. (I think that is the case with "ac-adapter".)

Even weirder, try

yad --image="software-update-available"

and it's using a Gnome icon!

yad --image="software-update-available-symbolic"

Has the correct light grey icon.

But "software-update-available" is a nice generic name that many icon themes should have available:

john@bookworm-tmp:~$ find /usr/share/icons -iname '*software-update-available*'
/usr/share/icons/gnome/16x16/status/software-update-available.png
/usr/share/icons/gnome/24x24/status/software-update-available.png
/usr/share/icons/gnome/256x256/status/software-update-available.png
/usr/share/icons/gnome/48x48/status/software-update-available.png
/usr/share/icons/gnome/32x32/status/software-update-available.png
/usr/share/icons/gnome/22x22/status/software-update-available.png
/usr/share/icons/Papirus-Light/16x16/panel/software-update-available.svg
/usr/share/icons/Papirus-Light/24x24/panel/software-update-available.svg
/usr/share/icons/Papirus-Light/22x22/panel/software-update-available.svg
/usr/share/icons/Yaru/24x24@2x/status/software-update-available.png
/usr/share/icons/Yaru/scalable/status/software-update-available-symbolic.svg
/usr/share/icons/Yaru/16x16/status/software-update-available.png
/usr/share/icons/Yaru/24x24/status/software-update-available.png
/usr/share/icons/Yaru/48x48@2x/status/software-update-available.png
/usr/share/icons/Yaru/256x256/status/software-update-available.png
/usr/share/icons/Yaru/256x256@2x/status/software-update-available.png
/usr/share/icons/Yaru/48x48/status/software-update-available.png
/usr/share/icons/Yaru/32x32@2x/status/software-update-available.png
/usr/share/icons/Yaru/16x16@2x/status/software-update-available.png
/usr/share/icons/Yaru/32x32/status/software-update-available.png
/usr/share/icons/Numix-Light/scalable/status/software-update-available-symbolic.svg
/usr/share/icons/Papirus-Dark/symbolic/status/software-update-available-symbolic.svg
/usr/share/icons/ePapirus/24x24/panel/software-update-available.svg
/usr/share/icons/Adwaita/scalable/status/software-update-available-symbolic.svg
/usr/share/icons/Adwaita/16x16/status/software-update-available-symbolic.symbolic.png
/usr/share/icons/Adwaita/24x24/legacy/software-update-available.png
/usr/share/icons/Adwaita/24x24/status/software-update-available-symbolic.symbolic.png
/usr/share/icons/Adwaita/64x64/status/software-update-available-symbolic.symbolic.png
/usr/share/icons/Adwaita/48x48/legacy/software-update-available.png
/usr/share/icons/Adwaita/48x48/status/software-update-available-symbolic.symbolic.png
/usr/share/icons/Adwaita/32x32/status/software-update-available-symbolic.symbolic.png
/usr/share/icons/Adwaita/96x96/status/software-update-available-symbolic.symbolic.png
/usr/share/icons/Numix/scalable/status/software-update-available-symbolic.svg
/usr/share/icons/Faenza/status/scalable/software-update-available-symbolic.svg
/usr/share/icons/Faenza/status/22/software-update-available.png
/usr/share/icons/Faenza/status/24/software-update-available.png
/usr/share/icons/Faenza-Dark/status/scalable/software-update-available-symbolic.svg
/usr/share/icons/Faenza-Dark/status/22/software-update-available.png
/usr/share/icons/Faenza-Dark/status/24/software-update-available.png
/usr/share/icons/Paper/24x24@2x/apps/software-update-available.png
/usr/share/icons/Paper/24x24@2x/status/software-update-available.png
/usr/share/icons/Paper/512x512/apps/software-update-available.png
/usr/share/icons/Paper/512x512/status/software-update-available.png
/usr/share/icons/Paper/scalable/status/software-update-available-symbolic.svg
/usr/share/icons/Paper/16x16/apps/software-update-available.png
/usr/share/icons/Paper/16x16/status/software-update-available.png
/usr/share/icons/Paper/24x24/apps/software-update-available.png
/usr/share/icons/Paper/24x24/status/software-update-available.png
/usr/share/icons/Paper/48x48@2x/apps/software-update-available.png
/usr/share/icons/Paper/48x48@2x/status/software-update-available.png
/usr/share/icons/Paper/48x48/apps/software-update-available.png
/usr/share/icons/Paper/48x48/status/software-update-available.png
/usr/share/icons/Paper/512x512@2x/apps/software-update-available.png
/usr/share/icons/Paper/512x512@2x/status/software-update-available.png
/usr/share/icons/Paper/32x32@2x/apps/software-update-available.png
/usr/share/icons/Paper/32x32@2x/status/software-update-available.png
/usr/share/icons/Paper/16x16@2x/apps/software-update-available.png
/usr/share/icons/Paper/16x16@2x/status/software-update-available.png
/usr/share/icons/Paper/32x32/apps/software-update-available.png
/usr/share/icons/Paper/32x32/status/software-update-available.png
/usr/share/icons/Papirus/16x16/panel/software-update-available.svg
/usr/share/icons/Papirus/symbolic/status/software-update-available-symbolic.svg
/usr/share/icons/Papirus/24x24/panel/software-update-available.svg
/usr/share/icons/Papirus/22x22/panel/software-update-available.svg

I knew we had Unfinished Business with icons that we'd have to deal with once the other stuff was done...

Last edited by johnraff (2023-10-15 01:01:36)

hhh · 2023-10-15 01:53:22

Even weirder is that if I color-pick the Numix-light icon in its folder, or open it in Inkscape and look at it's fill properties, the hex is #353535 with no transparency, same as the other systray icons, but if I color-pick the update icon in the systray it's #000000 (black). But hey, it's a feature, not a bug (makes it a more "urgent" icon)!

I can't give any more info on the 32 bit ISO failure. If you recall, my BIOS doesn't even "see" the USB drive with that ISO copied to it.

More feedback, I thought we agreed to disable inactive window transparency? It's very, very pretty but causes usability issues.

johnraff · 2023-10-15 02:37:04

hhh wrote:

I can't give any more info on the 32 bit ISO failure. If you recall, my BIOS doesn't even "see" the USB drive with that ISO copied to it.

Last time with Beta1 you posted an error message:

error: file `/live/vmlinuz-5.10.0-2.0-686' not found

Could you do again whatever you did that time, and post the error message you get with Beta2?

More feedback, I thought we agreed to disable inactive window transparency? It's very, very pretty but causes usability issues.

Yes we did indeed. Could you tell me what change to make in picom.conf?

I'd like to discuss the compositor settings a bit more in general, in fact, before uploading the next iso.

hhh · 2023-10-15 03:00:28

johnraff wrote:

Last time with Beta1 you posted an error message:
error: file `/live/vmlinuz-5.10.0-2.0-686' not found

hhh wrote:

@Johnraff, I tried running the 32 bit Beryllium ISO on my Ideapad

No hay más información con Boron, señor.

For picom transparency, just comment out inactive window transparency in the OPACITY section (and uncomment the line before it for clarity), lines 164 and 165, like so...

# Opacity of inactive windows. (0.1 - 1.0, defaults to 1.0)
# inactive-opacity = 1
inactive-opacity = 0.7;

I'd suggest a new thread for Picom discussion, but if you want different drop shadows just comment out the current settings and add your own. It's shadow radius, lines 27/28, and offset-x and -y in the following lines. I won't be offended!

hhh · 2023-10-16 09:39:40

Suggestion: Enable the xfce4-notifyd Notification log by default (set to "Always") and increase the notification timeout, at least to 30 seconds.

Notifications can be dismissed with a mouse click, but xfce4-notifyd has no systray app to show that you've missed a notification if you're away from keyboard, and the logging is disabled by default. As it is, if you don't read the notification while it's on-screen for 15 seconds, you've missed it entirely.

rbh · 2023-10-16 21:38:34

johnraff wrote:

There are other ways to make the terminal stay open.

Yes, that is the linux way.

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

If it is run first or last when opening a terminal, does not matter. But, if the command is added in .bashrc, it is run. I asked Google ".bashrc AND neofetch" and got 9 140 answers. The first was from EndeavourOS forum, with the text:

For some reason, many people like to add neofetch to their .bashrc (or .zshrc, or whatever shell rc file they are using).

It is quite common to do so. I did not compare, those users with users having alias for "apt update && apt upgrade" in bashrc... I have no clue how many they are. Probably some fewer, as Google gives 6 540 hits for '.bashrc AND "apt update && apt upgrade"'...

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

No. If you want to add a prompt, the text should be: "Press [any key]|[Press Enter] to continue". As I have pointed out, ".bashrc" keeps the terminal open instead of closing it after the update listing.

But, if you want that solution, why not add the option to quit?
"Press Enter to continue, Press Q to quit.

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

Default settings. Test boot VM in live session. But, I now noticed that vm with Guest additions, behaves ok in that aspect. Sorry, I should have tested that first.
So, maybe a note for VirtualBox users, in release notes?

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

Nope, screen totally black. Can not change to console tty. And that is still after installed Guest additions.

Meld is not present in the live system of either i386 or amd64 Beta 2 - I just checked. Maybe you installed it?

You are right. I must have done that.

[Iso-boot with grml-rescueboot,]

In 64 bit VirtualBox vm, with Guest -additions installed, iso-boot with grml-rescueboot works, but with errors.
When executing grub file in the vm it stops with:

error: file "/boot/grub/i386-pc/efi_gop.mod" was not found.
error: file "/boot/grub/i386-pc/efi_uga.mod" was not found.
error: file "/isolinux/splash800x600.png" was not found.
Press a key to continue...

(My translation from swedish)
It boots to 800x600 resolution screen. Whole welcome yad can not be read and there is no scrollbar.

Choosing isos failsafe menu, it ends with kernel panic

On 64 bit hardware, it drops to BysyBox shell. Can not find live system.

On 32 bit hardware, reading hosts grub, it make same complain as above. Continue and boot ok.

johnraff · 2023-10-17 01:18:51

hhh wrote:

johnraff wrote:
Last time with Beta1 you posted an error message:
error: file `/live/vmlinuz-5.10.0-2.0-686' not found
hhh wrote:
@Johnraff, I tried running the 32 bit Beryllium ISO on my Ideapad
No hay más información con Boron, señor.

rbh wrote:

[Iso-boot with grml-rescueboot,]
In 64 bit VirtualBox vm, with Guest -additions installed, iso-boot with grml-rescueboot works, but with errors.
When executing grub file in the vm it stops with:
error: file "/boot/grub/i386-pc/efi_gop.mod" was not found.
error: file "/boot/grub/i386-pc/efi_uga.mod" was not found.
error: file "/isolinux/splash800x600.png" was not found.
Press a key to continue...
(My translation from swedish)
It boots to 800x600 resolution screen. Whole welcome yad can not be read and there is no scrollbar.
Choosing isos failsafe menu, it ends with kernel panic
On 64 bit hardware, it drops to BysyBox shell. Can not find live system.
On 32 bit hardware, reading hosts grub, it make same complain as above. Continue and boot ok.

@hhh and @rbh I have no further ideas why the isoa are not booting in your situations. But could I ask two obvious questions:
1) Do the BL 32bit and 64bit beta2 isos you downloaded, successfully boot on any other machines?
2) Do the Debian, Ubuntu or other isos you might have available successfully boot on the hardware or VM where the BL iso failed?
2a) How about older BL isos like Beryllium or Lithium?

It would be nice if our isos were usable on older ideapads (@hhh yours is a 32bit?) or of course with grml.

Not a Yoga Ideapad?
https://en.wikipedia.org/wiki/IdeaPad

wikipedia wrote:

On September 21, 2016, Lenovo confirmed that their Yoga series is not meant to be compatible with Linux operating systems, that they know it is impossible to install Linux on some models, and that it is not supported.

hhh · 2023-10-17 01:42:07

@John, mine is a newish one, 64bit (I think the model was released in 2021, I bought mine in January). Yes, the 32bit ISO boots on other laptops, and the 64 bit installs and runs beautifully on this laptop, which is why I said not to spend too much time on this.

johnraff · 2023-10-17 01:47:04

hhh wrote:

Suggestion: Enable the xfce4-notifyd Notification log by default (set to "Always") and increase the notification timeout, at least to 30 seconds.
Notifications can be dismissed with a mouse click, but xfce4-notifyd has no systray app to show that you've missed a notification if you're away from keyboard, and the logging is disabled by default. As it is, if you don't read the notification while it's on-screen for 15 seconds, you've missed it entirely.

Sounds OK to me. (I didn't know about the logging facility.)

Display timeout could get annoying if trivial notifications lingered too long, but 15s is probably too short. I seem to have already set mine to 30s. Developers shouldn't really be using notification popups for important information that the user ought not to miss. But maybe sometimes they do...

johnraff · 2023-10-17 01:51:04

hhh wrote:

@John, mine is a newish one, 64bit (I think the model was released in 2021, I bought mine in January). Yes, the 32bit ISO boots on other laptops, and the 64 bit installs and runs beautifully on this laptop, which is why I said not to spend too much time on this.

Ah it's a 64bit machine. In that case, agreed let's not worry why the 32bit iso doesn't boot on it.

It might be EFI. There's no EFI support in the 32bit iso - hands up all those who have 32bit laptops which use EFI...

johnraff · 2023-10-17 02:33:41

rbh wrote:

I did not compare, those users with users having alias for "apt update && apt upgrade" in bashrc... I have no clue how many they are.

I know for certain at least two regular members of this forum have bash aliases related to apt package handling. I don't think we should break their familiar terminal just to accomodate the problems caused by decoration. Do people with neofetch in their .bashrc get it every time they open a new terminal? While happy to let them keep that freedom, I would find it very irritating if neofetch appeared more than once a day. I can see no problem with it if working on a text-only tty where neofetch might be similar to Debian's Message Of The Day. One appearance, then get on with your work...

But happily we can accomodate both camps.

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".
No. If you want to add a prompt, the text should be: "Press [any key]|[Press Enter] to continue".

I have since reconsidered, and chosen "Press Enter for a bash shell". That's the most accurate IMO.

But, if you want that solution, why not add the option to quit?
"Press Enter to continue, Press Q to quit.

Yes, I suppose that would be an improvement.
I had to use bash not sh for the launching shell because dash's 'read' does not offer the option of returning after a single keypress. That would require users who want to quit to press Q and Enter. With bash just Q (or q) is enough. Try running this line in a terminal, does it look reasonable?

x-terminal-emulator -T 'Available Package Upgrades' -e bash -c 'printf "%s\n" "Available upgrades:"; apt list --upgradeable; printf "\n%s\n"  "Held packages:"; apt-mark showhold; printf "\n%s\n" "Press Enter for a bash shell, Q to quit"; read -srn1 REPLY; case "$REPLY" in q|Q) exit;; esac ; bash ;'

rbh · 2023-10-17 08:04:47

johnraff wrote:

I know for certain at least two regular members of this forum have bash aliases related to apt package handling.

And I have both neofetch starting from .bashrc and bash aliases related to apt...

I don't think we should break their familiar terminal just to accomodate the problems caused by decoration.

Neofetch is not just decoration, just like conky is not only decoration. But, when I want to list available upgrades, I'm not intrested in running neofetch. I don't think so many would be keen on that.

Do people with neofetch in their .bashrc get it every time they open a new terminal?

Yes, just like commands in ~/.config/bunsen/autostart runs every time you log in to an bunsenlabs session.

While happy to let them keep that freedom,

I have very hard to believe that those who want to list available upgrades is interested in running neofetch..

But, if you want that solution, why not add the option to quit?
"Press Enter to continue, Press Q to quit.

Yes, I suppose that would be an improvement.

Try running this line in a terminal, does it look reasonable?
x-terminal-emulator -T 'Available Package Upgrades' -e bash -c 'printf "%s\n" "Available upgrades:"; apt list --upgradeable; printf "\n%s\n" "Held packages:"; apt-mark showhold; printf "\n%s\n" "Press Enter for a bash shell, Q to quit"; read -srn1 REPLY; case "$REPLY" in q|Q) exit;; esac ; bash ;'

Technically, the code works of course. But, still the text should be "...to continue..."
I asked google for the phrase "Press Enter for a bash shell". and got zero hits. Phrase "Press enter to continue", returned 5.2 million hits.
I am not alone prefering "Press enter to continue"...

johnraff · 2023-10-17 08:12:37

^Sorry, but I prefer "Press Enter for a bash shell". It's correct, and it makes clear what the user will get.

#21 2023-10-14 06:33:13

Re: Boron Beta 2 isos available, amd64 and i386

#22 2023-10-14 06:54:43

Re: Boron Beta 2 isos available, amd64 and i386

#23 2023-10-14 08:12:00

Re: Boron Beta 2 isos available, amd64 and i386

#24 2023-10-14 08:14:55

Re: Boron Beta 2 isos available, amd64 and i386

#25 2023-10-14 08:45:13

Re: Boron Beta 2 isos available, amd64 and i386

#26 2023-10-14 11:12:42

Re: Boron Beta 2 isos available, amd64 and i386

#27 2023-10-15 00:14:57

Re: Boron Beta 2 isos available, amd64 and i386

#28 2023-10-15 00:46:33

Re: Boron Beta 2 isos available, amd64 and i386

#29 2023-10-15 01:53:22

Re: Boron Beta 2 isos available, amd64 and i386

#30 2023-10-15 02:37:04

Re: Boron Beta 2 isos available, amd64 and i386

#31 2023-10-15 03:00:28

Re: Boron Beta 2 isos available, amd64 and i386

#32 2023-10-16 09:39:40

Re: Boron Beta 2 isos available, amd64 and i386

#33 2023-10-16 21:38:34

Re: Boron Beta 2 isos available, amd64 and i386

#34 2023-10-17 01:18:51

Re: Boron Beta 2 isos available, amd64 and i386

#35 2023-10-17 01:42:07

Re: Boron Beta 2 isos available, amd64 and i386

#36 2023-10-17 01:47:04

Re: Boron Beta 2 isos available, amd64 and i386

#37 2023-10-17 01:51:04

Re: Boron Beta 2 isos available, amd64 and i386

#38 2023-10-17 02:33:41

Re: Boron Beta 2 isos available, amd64 and i386

#39 2023-10-17 08:04:47

Re: Boron Beta 2 isos available, amd64 and i386

#40 2023-10-17 08:12:37

Re: Boron Beta 2 isos available, amd64 and i386

Board footer