Upgrading from Beryllium to experimental Boron

dhalgren · 2023-02-26 05:50:10

I just thought - for fonts which aren't available as packages from the regular Debian repositories, if you're going to install manually is it even necessary to install a package?

For use with TeX and LaTeX you have to create the font maps using font metrics files using a script (downloadable) and a texlive package from the repositorys. Then you copy this into the appropriate texlive folder on the HDD and run the updmap and mktexlsr commands which registers them for use as T1 fonts. (It is a little more complicated than that, but there you go.)

This is all due to LaTeX using only T1fonts, not TT (true type).

If using XeTeX or LuaTex, TT fonts can be used, but they do not typeset as nicely as the T1 fonts.

So yes, you are correct, but I use LaTeX as I find it typesets much more effectively for what I do, so creating the font maps and installing them is a bit of a must. But i can live without the Adobe fonts I have decided, and will leave the installation as it now is.

Last edited by dhalgren (2023-02-26 05:51:23)

johnraff · 2023-02-26 06:46:07

^Ah I see. I hope you eventually find a way to get those fonts back on Boron.

Re: that error message "Internal Error, No file name for..." you could try exploring a web search.
This one wasn't too helpful: https://askubuntu.com/questions/1344314 … 0-04-2-lts
but here: https://askubuntu.com/questions/167784/ … get-remove
suggested:

sudo dpkg --configure -a

dhalgren · 2023-02-26 07:08:48

johnraff wrote:

suggested:

sudo dpkg --configure -a

Yes, all done and everything is peachy (or cherry blossomed, perhaps ).

hhh · 2023-02-26 09:42:02

johnraff wrote:

dhalgren wrote:
As for my issues with fonts---I had forgotten that I installed them, which is a danger with additions which are not used very often, and I don't use them often enough to bother re-installing them.
I just thought - for fonts which aren't available as packages from the regular Debian repositories, if you're going to install manually is it even necessary to install a package? Up to now, I've always just copied the font file (usually .ttf) into ~/.local/share/fonts and run 'fc-cache -f -v ~/.local/share/fonts'.

I've never even run the fc-cache command, just copy to .fonts or .local/share/fonts or /usr/share/fonts and logout or reboot.

https://wiki.debian.org/Fonts

dmontaine · 2023-03-06 19:14:47

I have tried the Beryllium to Boron upgrade process on two laptops and one desktop.

Laptop: LG UltraPC 16" Ryzen 7 internal AMD Radeon graphics
Laptop: HP 15z Ryzen 5 internal AMD Radeon graphics
Desktop: HP TP1 i5 AMD Radeon add-on graphics card.

The LG has pcloud installed and a compiled version of Gambas 18.1, Other than that, all three had stock installs of Beryllium.

All three installs and upgrades went without problems. The upgrade solved two issues on the TP1: 1) Beryllium did not have drivers for wifi, so I had to use a wired connection, and it could not use the full resolution of the LG 34" 2560x1440 monitor and defaulted to 1024x768. Both issues were solved by the upgrade.

I did run into a small issue this morning on the TP1 upgrade that I did not run into last night upgrading the two laptops. When trying to edit the running tint2 session, it tried to open "tin2rcapos" rather than "tint2rc" I was able to edit the correct file using the tint2 editor and selecting "tint2rc".

dmontaine · 2023-03-07 02:23:40

After upgrading to Boron, editing the keybinds from the menu does not cause the new keybinds to be activated. Editing .xbindkeysrc with the micro editor in a terminal window and saving does cause the new keybinds to be activated.

johnraff · 2023-03-07 09:13:13

Thanks for the feedback!

dmontaine wrote:

When trying to edit the running tint2 session, it tried to open "tin2rcapos" rather than "tint2rc" I was able to edit the correct file using the tint2 editor and selecting "tint2rc".

You found a bug. In bash 5.2, as used in Bookworm, ampersands in parameter substitution have to be escaped with a backslash. This is because of a new bash option patsub_replacement which you could look up if you're curious.

The XMLescape() and pangoEscape() functions in bl-includes have now been fixed, and uploaded in bunsen-common 12.1-1, so could you see if an apt update/upgrade fixes this issue?

editing the keybinds from the menu does not cause the new keybinds to be activated.

xbindkeys is supposed to reload its config file when edited (like conky), but in practice this never seems to happen. Even 'killall -HUP xbindkeys', suggested in the comments in ~/.xbindkeysrc, doesn't usually work for me.
What actually does the job is:

pkill -x xbindkeys
xbindkeys_autostart

Luckily, there is a menu item "Restart" right under "Edit .xbindkeysrc" which should run those commands.

Editing .xbindkeysrc with the micro editor in a terminal window and saving does cause the new keybinds to be activated.

What's this "micro editor"? I tried editing .xbindkeysrc with "bl-cli-editor" (nano or vim in a terminal) and xbindkeys still needed restarting.

dmontaine · 2023-03-07 16:07:05

The micro editor is an modernized TUI editor that is designed to be a more modern option than nano. It is in the Debian repositories. The home page is https://micro-editor.github.io/.

johnraff · 2023-03-08 03:11:39

^Thanks for the tip! Now installed micro, and it looks quite nice.

dmontaine · 2023-03-09 21:26:07

I especially like the very complete mouse support and the fact that it allows you to enter your password for sudo when you try to save a protected file after forgetting to call micro with sudo.

johnraff · 2023-03-10 04:41:35

dmontaine wrote:

...the fact that it allows you to enter your password for sudo when you try to save a protected file after forgetting to call micro with sudo.

Sounds nice - I'll check that out.

DeepDayze · 2023-03-10 17:14:30

dmontaine wrote:

I especially like the very complete mouse support and the fact that it allows you to enter your password for sudo when you try to save a protected file after forgetting to call micro with sudo.

A nice feature for doing edits of config files that reside in /etc for example.

johnraff · 2023-03-11 05:15:04

Install micro on Bookworm/Boron, then in Menu > System > Edit Debian Alternatives it should be possible to choose 'micro' as the alternative for 'editor'.
(On Beryllium/Bullseye I had to do it by hand.)

Then you can open a file with 'BL CLI Editor' and get it in micro.

deleted0 · 2023-03-23 00:49:10

Easy Breezy Upgrade

8bit

matollik · 2023-04-24 12:02:55

I've upgraded to Bookworm/Boron via apt. The recommend two-part upgrade...
sudo apt upgrade --without-new-pkgs
Reboot.
sudo apt full-upgrade
Reboot.

Upgrading with above guidelines from Beryllium to Boron succeeded fine.
Edit: For an unknown reason cpu temperature gets ca.10 deg celcius higher. I compared it with a newly installed Beryllium and the temp difference was quite obvious. The temp is indicated by Conky monitoring.

Last edited by matollik (2023-05-01 13:36:51)

dbvolvox · 2023-05-22 21:18:12

Upgraded my reserve laptop to Boron, totally uneventful. Dare one say boring!

ekzotic · 2023-06-14 10:17:20

Successfully upgraded! Is it possible to fix black battery icon in the tray?
Also may I suggest replacing 640x480 grub image with 1920x1080? Looks much nicer.
And with linux 6 you can try mglru.

Last edited by ekzotic (2023-06-14 10:50:23)

rbh · 2023-06-14 12:46:00

ekzotic wrote:

Is it possible to fix black battery icon in the tray?

It should be fixed. Do you have latest xfce4-power-manager, from pkg.bunsenlabs.org/debian installed? On this machine I have xfce4-power-manager_4.18.1+bl12.iconpatch1-1, from pkg.bunsenlabs.org/debian bookworm-backports, and it works ok.

hhh · 2023-06-14 16:57:11

rbh wrote:

ekzotic wrote:
Is it possible to fix black battery icon in the tray?
It should be fixed. Do you have latest xfce4-power-manager, from pkg.bunsenlabs.org/debian installed? On this machine I have xfce4-power-manager_4.18.1+bl12.iconpatch1-1, from pkg.bunsenlabs.org/debian bookworm-backports, and it works ok.

@ekzotic, BL bookworm-backports needs to be added to sources (/etc/apt/sources.list/d/bunsen.list is a good spot)...

#BunsenLabs Boron
deb https://pkg.bunsenlabs.org/debian boron main

#Boron Backports
deb https://pkg.bunsenlabs.org/debian bookworm-backports main

Then upgrade to the backported power manager with...

sudo apt install -t bookworm-backports xfce4-power-manager

Logout, log back in and enjoy the serenity.

ekzotic · 2023-06-14 17:09:54

hhh wrote:

rbh wrote:
ekzotic wrote:
Is it possible to fix black battery icon in the tray?
It should be fixed. Do you have latest xfce4-power-manager, from pkg.bunsenlabs.org/debian installed? On this machine I have xfce4-power-manager_4.18.1+bl12.iconpatch1-1, from pkg.bunsenlabs.org/debian bookworm-backports, and it works ok.
@ekzotic, BL bookworm-backports needs to be added to sources (/etc/apt/sources.list/d/bunsen.list is a good spot)...
#BunsenLabs Boron
deb https://pkg.bunsenlabs.org/debian boron main

#Boron Backports
deb https://pkg.bunsenlabs.org/debian bookworm-backports main
Then upgrade to the backported power manager with...
sudo apt install -t bookworm-backports xfce4-power-manager
Logout, log back in and enjoy the serenity.

That worked indeed thanks for the help guys and girls Bliss

#21 2023-02-26 05:50:10

Re: Upgrading from Beryllium to experimental Boron

#22 2023-02-26 06:46:07

Re: Upgrading from Beryllium to experimental Boron

#23 2023-02-26 07:08:48

Re: Upgrading from Beryllium to experimental Boron

#24 2023-02-26 09:42:02

Re: Upgrading from Beryllium to experimental Boron

#25 2023-03-06 19:14:47

Re: Upgrading from Beryllium to experimental Boron

#26 2023-03-07 02:23:40

Re: Upgrading from Beryllium to experimental Boron

#27 2023-03-07 09:13:13

Re: Upgrading from Beryllium to experimental Boron

#28 2023-03-07 16:07:05

Re: Upgrading from Beryllium to experimental Boron

#29 2023-03-08 03:11:39

Re: Upgrading from Beryllium to experimental Boron

#30 2023-03-09 21:26:07

Re: Upgrading from Beryllium to experimental Boron

#31 2023-03-10 04:41:35

Re: Upgrading from Beryllium to experimental Boron

#32 2023-03-10 17:14:30

Re: Upgrading from Beryllium to experimental Boron

#33 2023-03-11 05:15:04

Re: Upgrading from Beryllium to experimental Boron

#34 2023-03-23 00:49:10

Re: Upgrading from Beryllium to experimental Boron

#35 2023-04-24 12:02:55

Re: Upgrading from Beryllium to experimental Boron

#36 2023-05-22 21:18:12

Re: Upgrading from Beryllium to experimental Boron

#37 2023-06-14 10:17:20

Re: Upgrading from Beryllium to experimental Boron

#38 2023-06-14 12:46:00

Re: Upgrading from Beryllium to experimental Boron

#39 2023-06-14 16:57:11

Re: Upgrading from Beryllium to experimental Boron

#40 2023-06-14 17:09:54

Re: Upgrading from Beryllium to experimental Boron

Board footer