Boron alpha 1 iso available for testing and feedback

johnraff · 2023-08-09 08:18:21

^true (though not that much work), and it would also avoid having to have alternative conkys for the light and dark desktops.

But doesn't 8AB8BC look slightly better for aqua?

And users might prefer to keep the conky settings separate?

hhh · 2023-08-09 08:38:22

johnraff wrote:

BTW the menu icons do look quite pretty on the dark background, although I'd been thinking we could make the dark desktop no-icons by default...???

I like jgmenu either way, and I like the idea of offering two versions for two different themes by default, to allow the user to explore customized themes beyond the defaults.

unklar · 2023-08-09 17:22:02

johnraff wrote:

^true (though not that much work), and it would also avoid having to have alternative conkys for the light and dark desktops.
But doesn't 8AB8BC look slightly better for aqua?
And users might prefer to keep the conky settings separate?

No.
The longer I look at it, then my decision falls for ABB8B8 for both backgrounds. Do it with this.

johnraff · 2023-08-10 06:35:24

^It's a small difference, and since you are firm about it, no problem from this side.

@hhh conky text colour of #ABB8B8 for both aqua and dark backgrounds OK?
(You've already said no_comment=agreement )

Last edited by johnraff (2023-08-10 06:37:02)

johnraff · 2023-08-10 08:06:59

Another quick one to run past @hhh:
boron tint2 filenames: since the default Boron desktop is light, to have the dark tint2s named simply boron.tint2rc and boron-vertical.tint2rc might confuse users into thinking they are the default.
I suggest boron-dark.tint2rc, boron-dark-vertical.tint2rc, boron-light.tint2rc and boron-light-vertical.tint2rc.

Strictly, the same could be done for the Lithium files, but a) the dark version was the default then, and b) it's two versions ago and only likely to confuse people and break their scripts etc.

hhh · 2023-08-11 06:54:42

^ Yes, that's fine! And the no comment one!

johnraff · 2023-08-14 05:24:24

johnraff wrote:

Another quick one to run past @hhh:
boron tint2 filenames: since the default Boron desktop is light, to have the dark tint2s named simply boron.tint2rc and boron-vertical.tint2rc might confuse users into thinking they are the default.

GTK themename too?
ie rename Boron to Boron-dark for the same reason?

hhh · 2023-08-14 05:56:29

Yes. Make it so.

walter · 2023-08-23 18:13:34

I installed 'bunsen-apt-update-checker' in the alpha some time ago. I have not yet noticed it doing anything. And yes, it was running more then 10 minutes and there where updates.

Obviously I am doing something wrong.

Other thing;

I have it running in a virtual box. Every time it boots up it is back at its default resolution. I can change it with ARandR Screen Layout editor. That works. But does not survives a reboot. Not used Virtualbox a lot. Maybe that is normal.

Installed the current version of BunsenLabs in virtualbox. Has the same problem that it does not safe the screen resolution. So whatever the reason is it is not related to the alpha edition

Last edited by walter (2023-08-23 19:27:07)

rbh · 2023-08-23 21:47:39

walter wrote:

Installed the current version of BunsenLabs in virtualbox. Has the same problem that it does not safe the screen resolution. So whatever the reason is it is not related to the alpha edition

From [Introduction to the Bunsenlabs Lithium Desktop](https://forums.bunsenlabs.org/viewtopic.php?id=6461)

Screen settings
BunsenLabs has a Screen layout editor:
The command "arandr"
Menu -> Preferences -> Display -> ARandR Screen Layout Editor
ARandr is a visual front end for xrandr.
You can configure multiple monitors, set size, resolution and orientation.
If you want configured settings to load at start, you can save the settings as a script, to be loaded by autostart:
On menu "Layout", choose "Save As", save as screen.sh in the default folder: ~./screenlayout/.
Open file ~/.config/bunsen/autostart in your editor.
After text "### SETTINGS START", add:
$HOME/.screenlayout/screen.sh

johnraff · 2023-08-24 06:22:07

Hi walter, thank you for the feedback.

walter wrote:

I installed 'bunsen-apt-update-checker' in the alpha some time ago. I have not yet noticed it doing anything. And yes, it was running more then 10 minutes and there where updates.

How long was "some time ago"?
After installing bunsen-apt-update-checker apt is configured to check the upstream repository every 24 hours. The exact time is random to avoid concentrated system overuse.
"More than 10 minutes" is not enough, unless there are already some available updates recorded in the local apt data-base.

The notification that upgrades are available should appear in the form of a popup for 10 seconds or so, and an icon which is placed in your system tray.

How did you know that there were updates? If you run 'sudo apt update' and find updates are available, the notification should appear at that point. But bypassing the script like that is pointless - you want automatic reporting of available updates.

The only way to confirm whether bunsen-apt-update-checker is doing its job or not is to leave apt alone - no manual apt updates - for more than a day, in a situation where you are sure updates are available. To know that, you can check on another computer, or follow the debian-security-announce mailing list which will inform you of new security updates without interfering with apt's data base.

The update checker has been doing its job for me, but if there is a bug I'd very much like to know about it!

walter · 2023-08-24 06:38:18

Thanks John,

I installed it a couple of weeks ago. And the install was running in virtualbox for a couple of hours. I forgot that I installed it and suddenly realized I never seen a notification.

I knew there where updates because I did what I always do;
sudo apt-get update
sudo apt-get upgrade (and there where updates to install, few actually and bunsen specific)

I will experiment a bit specific with this. Will start with a fresh virtual install of the alpha.

johnraff · 2023-08-24 07:15:52

walter wrote:

I knew there where updates because I did what I always do;
sudo apt-get update
sudo apt-get upgrade (and there where updates to install, few actually and bunsen specific)

If you were doing that regularly then the package was never getting a chance to do its job because you were pre-empting it.
Even so, at the point where you run 'sudo apt-get update', and there are upgrades available, then the notification popup should appear. Could you confirm if that is happening?

If the notification popup does not appear, before running 'sudo apt-get upgrade', could you try this?

bl-apt-update-check

No popup?

matollik · 2023-08-30 15:59:33

With

bl-apt-update-check

gave 'command not found'. At terminal that is.
Then, when a new program is installed, an error follows:
"E: linux-image-6.1.0-11-amd64: installed linux-image-6.1.0-11-amd64 package post-installation script subprocess returned error exit status 1
E: linux-image-amd64: dependency problems - leaving unconfigured
E: linux-image-6.1.0-10-amd64: installed linux-image-6.1.0-10-amd64 package post-installation script subprocess returned error exit status 1
E: initramfs-tools: installed initramfs-tools package post-installation script subprocess returned error exit status 1". The whole process lasts ages, too.
Installation itself takes place with success though. At previous versions I've tested no problem of this kind.

Last edited by matollik (2023-08-30 16:06:00)

johnraff · 2023-08-31 01:39:20

@matollik thank you for this report. It looks as if you might have found a bug in the bunsen-apt-update-checker package. Possibly two bugs...

If you have a little time, could I ask a few questions?

Have you actually installed bunsen-apt-update-checker?
If so, did you install it directly with an apt or apt-get command, or via the bl-welcome script?
Do you get those "script subprocess returned error exit status 1" messages any time you try to install a package, or was it during the installation of the iso itself?
Do the messages go away if you uninstall bunsen-apt-update-checker?

matollik · 2023-08-31 05:31:20

Now I run a second installment of BL alfa, and this time I accepted all suggested applications be installed while still at bl-welcome. Anyway I'll check bunsen-apt-update-checker. It has not been added to the system yet.

Yes,I think "script subprocess returned error exit status 1" is present at most installs of a program. Not sure, I've only twice saved the error message. Every time prog installment lasts an unusually long time, very rare previously.
Do the messages go away if you uninstall bunsen-apt-update-checker? I'll try this.
Iso-file installment was error free.

ED:
matti@debian:~$ sudo apt bunsen-apt-update-checker
[sudo] password for matti:
E: Invalid operation bunsen-apt-update-checker
matti@debian:~$
This got this as result.

Last edited by matollik (2023-08-31 05:41:37)

unklar · 2023-08-31 08:00:30

Desktop

sudo apt install bunsen-apt-update-checker

$ bl-apt-update-check

No popup.

Laptop

bl-welcome

$ bl-apt-update-check

No popup.

However, there is nothing to update for both at the moment.

matollik · 2023-08-31 16:34:45

Many thanks. The update-checker was installed and a check flag messaged soon of two upgrades. The installment lasted 7 minutes.

These were the final lines of installing:
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
linux-image-6.1.0-11-amd64
linux-image-amd64
linux-image-6.1.0-10-amd64
initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

The OS was installed on an flash stick. Acer i3 laptop as computer.

johnraff · 2023-09-01 03:22:24

Hi @matollik, could you try temporarily uninstalling bunsen-apt-update-checker, and see if the error messages remain?

sudo apt remove bunsen-apt-update-checker

---
By the way, it's not really recommended to install everything that bl-welcome offers. Just choose the things you think you'll need. You can always run the script again later if you decide you want to add something else.

hhh · 2023-09-01 04:10:40

johnraff wrote:

By the way, it's not really recommended to install everything that bl-welcome offers. Just choose the things you think you'll need. You can always run the script again later if you decide you want to add something else.

You've gotten rid of bunsen-images-extra and dropbox, I hope?

#81 2023-08-09 08:18:21

Re: Boron alpha 1 iso available for testing and feedback

#82 2023-08-09 08:38:22

Re: Boron alpha 1 iso available for testing and feedback

#83 2023-08-09 17:22:02

Re: Boron alpha 1 iso available for testing and feedback

#84 2023-08-10 06:35:24

Re: Boron alpha 1 iso available for testing and feedback

#85 2023-08-10 08:06:59

Re: Boron alpha 1 iso available for testing and feedback

#86 2023-08-11 06:54:42

Re: Boron alpha 1 iso available for testing and feedback

#87 2023-08-14 05:24:24

Re: Boron alpha 1 iso available for testing and feedback

#88 2023-08-14 05:56:29

Re: Boron alpha 1 iso available for testing and feedback

#89 2023-08-23 18:13:34

Re: Boron alpha 1 iso available for testing and feedback

#90 2023-08-23 21:47:39

Re: Boron alpha 1 iso available for testing and feedback

#91 2023-08-24 06:22:07

Re: Boron alpha 1 iso available for testing and feedback

#92 2023-08-24 06:38:18

Re: Boron alpha 1 iso available for testing and feedback

#93 2023-08-24 07:15:52

Re: Boron alpha 1 iso available for testing and feedback

#94 2023-08-30 15:59:33

Re: Boron alpha 1 iso available for testing and feedback

#95 2023-08-31 01:39:20

Re: Boron alpha 1 iso available for testing and feedback

#96 2023-08-31 05:31:20

Re: Boron alpha 1 iso available for testing and feedback

#97 2023-08-31 08:00:30

Re: Boron alpha 1 iso available for testing and feedback

#98 2023-08-31 16:34:45

Re: Boron alpha 1 iso available for testing and feedback

#99 2023-09-01 03:22:24

Re: Boron alpha 1 iso available for testing and feedback

#100 2023-09-01 04:10:40

Re: Boron alpha 1 iso available for testing and feedback

Board footer