#241 2025-11-01 03:41:07

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,331

Website

Re: Carbon Bugs

https://forums.bunsenlabs.org/viewtopic … 24#p146724

---

I don't care what you do at home. Would you care to explain?

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 551

Website

Re: Carbon Bugs

Slightly right and it's more legible.

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 551

Website

Re: Carbon Bugs

Is this what you were chasing, less LSD?

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,331

Website

Re: Carbon Bugs

^^ That works nicely. ^ Why does the logo look so thin here? Must be the acid.

---

I don't care what you do at home. Would you care to explain?

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 551

Website

Re: Carbon Bugs

^^ That works nicely. ^ Why does the logo look so thin here? Must be the acid.

I narrowed the overlay by about 12-15% to allow for FHD res. Looks ok too as I replaced my /boot/grub/images/bunsen/default.png on my main box as well as the VM for testing purposes.

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,807

Website

Re: Carbon Bugs

Thanks to both of you for working at this while I was goofing off.
@micko, the updated icon theme is labbe-icons-ng (branch carbon) right?
And material-solarized-suruplusplus-gtkicons (branch main) got their last update on 25th Oct?

If so I'm ready to build and upload.

And the new grub images - I should grab the two you posted here?
https://forums.bunsenlabs.org/viewtopic … 19#p146719

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 551

Website

Re: Carbon Bugs

^
labbe -> carbon
suru -> main (updated 25 oct yes)

IDK why but doesn't matter.

We should actually keep carbon and maiin on both updated and in sync (I did labbe). That way when forky/nitrogen dev starts we're all set.

The Sage grub image is fine but I should post a plain pic of the updated Bark image - see https://forums.bunsenlabs.org/viewtopic … 26#p146726

--

Ok here it is..

Logo is slightly offset to avoid the busy centre.

As before size is reduced with pngquant.

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,807

Website

Re: Carbon Bugs

^Many thanks! The new grub images are both beautiful. I'll see if bunsen-images can ship both, not just the default version. Don't see any reason why not.

As for branches, how you organize it is up to you, especially for packages which aren't closely bound to a specific BL release like bunsen-configs or bunsen-images. Most of our in-house packages have release-name branches and no "main", but third-party software usually has a main branch. Anyway, as long as it's clear which branch I should build from, then please do it as you see fit.

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,807

Website

Re: Carbon Bugs

+1 to moving the Ruby walls out. My preference is to strip all the previous walls into extra packages

What we have right now is the images organized between two main source packages:

bunsen-images builds:
    bunsen-images-base and bunsen-images

bunsen-images-extra builds:
    bunsen-images-archives (bunsen-images-extra still exists in the source but we don't build it atm)

bunsen-images-base ships just what is needed for the current release, with a single alternative - in Carbon that means Bark and Sage.

bunsen-images ships the previous BL release's images, plus a few more popular alternatives (like Cog's).

Older BL wallpapers get moved into bunsen-images-archives.

Right now bunsen-images and bunsen-images-base still hold wallpapers that need to be moved back. Sorting them out is another pre-release task.

(the redundancy of different wall resolutions in our old images is unnecessary, IMO).
Slap a basic resolution wall selection in there, one resolution from each previous release, plus cog's wallpapers, done.

That sounds good. Unless we cull them they'll just build up...

What should be the default old wallpaper size? 1280x1024? 1440x900? 1920x1080?

Last edited by johnraff (2025-11-05 03:48:21)

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

hhh

Gaucho

From: High in the Custerdome

Registered: 2015-09-17

Posts: 16,331

Website

Re: Carbon Bugs

1920x1080 is my vote.

---

I don't care what you do at home. Would you care to explain?

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,807

Website

Re: Carbon Bugs

^OK.
The with-logo or plain version? Or both?

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,807

Website

Re: Carbon Bugs

As for branches, how you organize it is up to you...

Although I've just noticed that material-solarized-suruplusplus-gtkicons has a carbon branch as well as main, but carbon was last updated in June. I guess you might want to remove "carbon" or merge "main" into it or something.

PS  labbe-icons-ng now built and uploaded, and arrived in my VM.
Those new folders look great!
Even with subtle touches like "hidden" folders with dot names are slightly duller in colour.
(Or is that something that Thunar is doing?)

Last edited by johnraff (2025-11-05 07:01:19)

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 551

Website

Re: Carbon Bugs

Carbon is now synced with main on suru++

Just keep both and it's easy to sync. Whatever is behind you just switch to that branch locally and merge the latest branch then push to the remote. That way when we start nitrogen dev (a year or 2?) we can just let carbon go stale and fork nitrogen off main. Not that hard to manage.

EDIT: also deleted my upstream and forked off my own copy of suru++/main. That way I can fire in a PR if there is something dubious I may want to commit.

Last edited by micko01 (2025-11-05 11:10:26)

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 551

Website

Re: Carbon Bugs

(Or is that something that Thunar is doing?)

Indeed it's Thunar. Still, nice feature!

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,807

Website

Re: Carbon Bugs

Just keep both and it's easy to sync. Whatever is behind you just switch to that branch locally and merge the latest branch then push to the remote. That way when we start nitrogen dev (a year or 2?) we can just let carbon go stale and fork nitrogen off main. Not that hard to manage.

Sure, sounds fine.

Up to now I've been forking each new branch off the current release, with no "main". Probably makes little difference...

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,807

Website

Re: Carbon Bugs

The Sage grub image is fine but I should post a plain pic of the updated Bark image...
Ok here it is..
Logo is slightly offset to avoid the busy centre.

Sage and Bark grub images are in bunsen-images now, and the package upgrade is coming when the wallpapers are ready.

Meanwhile, for the iso installer splash images, I'll just take the sage grub image and resize it to 800x600 and 640x480 for grub-pc and syslinux-common. Fingers crossed there's no overlapping text issue.

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

greenjeans

Member

Registered: 2025-01-18

Posts: 258

Website

Re: Carbon Bugs

Meanwhile, for the iso installer splash images, I'll just take the sage grub image and resize it to 800x600 and 640x480 for grub-pc and syslinux-common. Fingers crossed there's no overlapping text issue.

Forgive the intrusion as I know you're busy, but wanted to ask why so small for the grub-splash? (I'm assuming you're referring to the grub background in the installed system). I know syslinux has to have that tiny 640x480 for the live grub splash, but a full size wallpaper for the installed system boot-splash looks really nice.

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,807

Website

Re: Carbon Bugs

^I'm talking about the splash screen that the installer displays, which as you know has a size limit. ("grub-pc" is a bit bigger than syslinux at 800x600.)

We ship a grub boot image for the installed system which is 1024x765.

I'm pretty sure grub was unable to show anything bigger than that in the past, but you say it will now accept a fullsized wallpaper?

EDIT I found this: https://shallowsky.com/blog/linux/grub-splashimage.html

Use 640x480 at least initially. I think it's supposed to be possible to use other resolutions, but I haven't explored that yet. (Update: in 2025 I have successfully used a 1920 x 1200 image either as PNG or JPEG.)

Last edited by johnraff (2025-11-08 00:48:13)

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop

micko01

void main()

From: Queensland, Australia

Registered: 2024-04-07

Posts: 551

Website

Re: Carbon Bugs

I think 1024x768 is fine for grub. IDK who sits there staring at that image, but for me I either hit enter as soon as possible or down and enter if I want to use another option in the menu. 3 seconds and that's all over until next time

---

#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen

johnraff

nullglob

From: Nagoya, Japan

Registered: 2015-09-09

Posts: 12,807

Website

Re: Carbon Bugs

I think 1024x768 is fine for grub.

I just noticed - grub bark is 1024x768 while sage is 1024x765
I guess that doesn't matter at all?

---

...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )

Introduction to the Bunsenlabs Boron Desktop