Carbon Themes (beta version)

micko01 · 2025-02-22 04:37:29

johnraff wrote:

micko01 wrote:
Different idea.
What about a minimal labbe version (named labbe-min-icons or something), just necessary folders (with the Material-Solarized* blend for bark/sage) and a few more application icons. Then with a hard dependency on Material-Solarized-[Bark,Sage]++ ?
Micko this all looks great, but right now I don't have time to check out your icon ideas because I'm tangled up in picom, xfce4-panel and bunsen-configs (still want to revisit xwwall too).
Please don't interpret lack of comments as lack of interest!
Anyway, that idea of a minimal labbe icon set inheriting the recoloured material-solarized icons looks solid.

I'm not here for aproval.

I just do stuff, if it's worthy of including or not, so be it.

Anyways, merged the solarized-bark/sage into one repo, = 1 package.

https://github.com/01micko/material-sol … lus-carbon

Created the labbe-min-icon repository.

https://github.com/01micko/labbe-min-icons

All build fine and work together pretty well.

johnraff · 2025-02-22 05:49:31

micko01 wrote:

micko01 wrote:
What about...<stuff>?
johnraff wrote:
...<just a minute>...
I'm not here for aproval.

I think you might have misinterpreted my response.
You seemed to be asking for an opinion, and I didn't want you to think I was ignoring your suggestion, that's all.

You work at a fast pace, and I can't always keep up.

Last edited by johnraff (2025-02-22 05:52:45)

micko01 · 2025-02-22 08:45:49

^No, I mis-worded mine!

Anyway, I've uploaded packages to my repo for labbe-min-icons and the combined material-(snip)-carbon

hhh · 2025-02-22 17:29:01

Here's bunsen-Yaru-bark (light)...

Drive by posting, I'll post the configs later.

I will now be switching back to the vastly superior *-bark-dark theme.

greenjeans · 2025-02-22 17:40:21

I like that light one ^^. I especially like the subdued color of the hover color on the menu.

I wonder what it would look like if the difference were split? Just my personal taste, but I think I would change the title-bars to a dark color, pull one of the dark shades from the wallpaper, and instead of the white background, pull one of the light colors from the wallpaper.

hhh · 2025-02-22 17:49:49

greenjeans wrote:

... I would change the title-bars to a dark color, pull one of the dark shades from the wallpaper, and instead of the white background, pull one of the light colors from the wallpaper.

You can't easily do that. The GTK 3 and 4 themes are all embedded in gresources files. You'd have to extract the contents of a couple of files (easy once you're set up, PITA to set up the first time), and then edit the messy results. Seriously, the theme files are huge and unorganized.

It's Yaru libgtk, it has the same almost-pure-white background color as Adwaita. It's hideous. Use the dark theme.

greenjeans · 2025-02-22 17:56:42

Ahh gotcha, so kind of what's been done with libadwaita and them rolling icons and theme css into gtk itself? (please forgive my dumb questions, still trying to learn).

It's still pretty easy in OB and Mate, though for Pluma I had to change the background color for it in gtksourceview-4 as the theme css had no effect on the interior background or side-panel.

Last edited by greenjeans (2025-02-22 17:57:32)

hhh · 2025-02-22 17:58:15

@johnraff, I think the easiest way to post my xfce4-panel profile is to upload the tar.bz2 file produced by xfce4-panel-profiles...

https://packages.debian.org/bookworm/xf … l-profiles

I can't upload it today, but will ASAP.

marens · 2025-02-23 01:00:40

greenjeans wrote:

Ahh gotcha, so kind of what's been done with libadwaita and them rolling icons and theme css into gtk itself? (please forgive my dumb questions, still trying to learn).
It's still pretty easy in OB and Mate, though for Pluma I had to change the background color for it in gtksourceview-4 as the theme css had no effect on the interior background or side-panel.

It's actually easy to override the settings in the gresources css files.

Don't be afraid of these or similar lines of gtk.css code:

@import url("resource:///org/gnome/Mcata-theme/gtk.css");

Anything you add below will be valid.
I already posted something about it:
https://forums.bunsenlabs.org/viewtopic … 10#p137810

What could be the problem?
Developers usually change the CSS code (file manager, text editor...) with a new release of the OS.
You need to install GTK Inspector and examine the element you want to change but that's off topic.

johnraff · 2025-02-23 01:35:58

hhh wrote:

@johnraff, I think the easiest way to post my xfce4-panel profile is to upload the tar.bz2 file produced by xfce4-panel-profiles...
https://packages.debian.org/bookworm/xf … l-profiles
I can't upload it today, but will ASAP.

I'd never heard of xfce4-panel-profiles but that looks like a plan.
Thanks!

We might want to consider shipping xfce4-panel-profiles in BL for our users, looks like a substitute for all the tint2 utilities that we'll be forced to abandon. ( Sorry Damo )
BLOB will probably need it too.

johnraff · 2025-02-23 01:39:00

micko01 wrote:

I've uploaded packages to my repo for labbe-min-icons and the combined material-(snip)-carbon

Great!
What are the package names again?
OK I figured out we'll need labbe-min-icons and that will pull in material-solarized-suruplusplus-carbon.

Last edited by johnraff (2025-02-23 01:45:26)

greenjeans · 2025-02-23 02:52:46

marens wrote:

greenjeans wrote:
Ahh gotcha, so kind of what's been done with libadwaita and them rolling icons and theme css into gtk itself? (please forgive my dumb questions, still trying to learn).
It's still pretty easy in OB and Mate, though for Pluma I had to change the background color for it in gtksourceview-4 as the theme css had no effect on the interior background or side-panel.
It's actually easy to override the settings in the gresources css files.
Don't be afraid of these or similar lines of gtk.css code:
@import url("resource:///org/gnome/Mcata-theme/gtk.css");
Anything you add below will be valid.
I already posted something about it:
https://forums.bunsenlabs.org/viewtopic … 10#p137810
What could be the problem?
Developers usually change the CSS code (file manager, text editor...) with a new release of the OS.
You need to install GTK Inspector and examine the element you want to change but that's off topic.

Thank you so much for that, I already had the inspector onboard just needed to enable it, this will really help me fine-tune things. I spent a good chunk of late December-early January editing gtk.css files for my own projects and choosing colors (which is harder than it sounds), this helps quite a bit going forward.

This is the kind of thing I really like about this forum, i'm learning new things and doing so very fast.

As soon as the first freeze this next month, i'll be clearing space and installing/upgrading BL and hopefully can contribute by testing and reporting back.

micko01 · 2025-02-23 03:18:32

johnraff wrote:

micko01 wrote:
I've uploaded packages to my repo for labbe-min-icons and the combined material-(snip)-carbon
Great!
What are the package names again?
OK I figured out we'll need labbe-min-icons and that will pull in material-solarized-suruplusplus-carbon.

A few beers made me lazy, sorry about that.

material-solarized-suruplusplus-carbon, couldn't really think of a better name but I suppose that's ok. Can always change it if needed.

Oh, I packaged them too.

mick@dellhome:~$ apt search material-solarized-suruplusplus-carbon
material-solarized-suruplusplus-carbon/unknown 13.0-1 all
  Material-Solarized-Sage++ and Bark++ icons sets.

mick@dellhome:~$ apt search labbe-min-icons
labbe-min-icons/unknown 0.1.0-1 all
  Light weight gtk icon theme, minimal version.

johnraff · 2025-02-23 06:24:07

^I like apt policy for a quick check, but they're there anyway:

john@trixie-tester:~$ apt policy labbe-min-icons
labbe-min-icons:
  Installed: (none)
  Candidate: 0.1.0-1
  Version table:
     0.1.0-1 100
        100 https://01micko.github.io/debian carbon-trixie/main amd64 Packages

and installed

john@trixie-tester:~$ sudo apt install labbe-min-icons

Installing:
  labbe-min-icons

Installing dependencies:
  material-solarized-suruplusplus-carbon

Summary:
  Upgrading: 0, Installing: 2, Removing: 0, Not Upgrading: 0
  Download size: 5,847 kB
  Space needed: 120 MB / 13.6 GB available

Setting up material-solarized-suruplusplus-carbon (13.0-1) ...
Setting up labbe-min-icons (0.1.0-1) ...

johnraff · 2025-02-23 07:59:34

micko01 wrote:

johnraff wrote:
micko01 wrote:
Here's tint2 with some picom tweaks (bare metal)
Where did you get that tint2?
The one in sid. ...Only the picom config was broken and that was relatively easy to fix.

What was broken for you in that picom.conf? I compared it with what boron had and the changes are basically to remove the lines I added here: https://forums.bunsenlabs.org/viewtopic … 43#p130543
links:
https://forum.maboxlinux.org/t/test-nee … rners/1209
https://wiki.archlinux.org/title/Picom# … nsparency)

"_NET_WM_STATE@:32a *= '_NET_WM_STATE_MAXIMIZED_VERT'" still seems to work for suppressing shadows or round corners of maximized windows.

I see "_GTK_FRAME_EXTENTS@:c" has been deprecated, so those lines should come out (although they were just ignored), but what actual issues were you getting?

I'm asking this because I'm having all kinds of trouble with picom 12.5 on my qemu VM right now, and trying to get a grip on it.

'--backend glx' just doesn't work at all. The desktop freezes.
Even with '--backend xrender', I'm getting weird fragmentation, eg:

(Sometimes it gets much worse than this, or even freezes up.)

micko01 · 2025-02-23 08:21:35

johnraff wrote:

What was broken for you in that picom.conf? I compared it with what boron had and the changes are basically to remove the lines I added here: https://forums.bunsenlabs.org/viewtopic … 43#p130543
links:
https://forum.maboxlinux.org/t/test-nee … rners/1209
https://wiki.archlinux.org/title/Picom# … nsparency)
"_NET_WM_STATE@:32a *= '_NET_WM_STATE_MAXIMIZED_VERT'" still seems to work for suppressing shadows or round corners of maximized windows.
I see "_GTK_FRAME_EXTENTS@:c" has been deprecated, so those lines should come out (although they were just ignored), but what actual issues were you getting?
I'm asking this because I'm having all kinds of trouble with picom 12.5 on my qemu VM right now, and trying to get a grip on it.
'--backend glx' just doesn't work at all. The desktop freezes.
Even with '--backend xrender', I'm getting weird fragmentation, eg:
https://i.imgur.com/944CnsZm.png
(Sometimes it gets much worse than this, or even freezes up.)

Here's the diff from the stock boron version, which I guess you may have done.

--- /usr/share/bunsen/skel/.config/picom.conf	2023-12-04 19:28:22.000000000 +1000
+++ /home/mick/.config/picom.conf	2025-02-15 22:09:08.405451588 +1000
@@ -111,10 +111,7 @@
     "class_g ?= 'Cairo-dock'",
 #    "class_g ?= 'Xfce4-notifyd'",
     "class_g ?= 'Xfce4-power-manager'",
-    "window_type = 'desktop'",
-    "_NET_WM_STATE@:32a *= '_NET_WM_STATE_HIDDEN'",
-    "_NET_WM_STATE@:32a *= '_NET_WM_STATE_MAXIMIZED_VERT'",
-    "_GTK_FRAME_EXTENTS@:c"
+    "window_type = 'desktop'"
 ];
 
 # Specify a list of conditions of windows that should have no shadow painted over, such as a dock window.
@@ -223,7 +220,7 @@
     "class_g  = 'Conky'",
 #   "window_type = 'menu'",
 #   "window_type = 'dock'",
-    "window_type = 'desktop'",
+    "window_type = 'desktop'"
 #   "window_type = 'dropdown_menu'",
 #   "window_type = 'popup_menu'",
 #   "window_type = 'tooltip'",
@@ -231,9 +228,8 @@
 #   "class_g = 'Polybar'",
 #   "class_g = 'Rofi'",
 #   "class_g = 'Dunst'",
-    "_NET_WM_STATE@:32a *= '_NET_WM_STATE_HIDDEN'",
-#   "_NET_WM_STATE@:32a *= '_NET_WM_STATE_MAXIMIZED_VERT'",
-    "_GTK_FRAME_EXTENTS@:c"
+#    "_NET_WM_STATE@:32a *= '_NET_WM_STATE_HIDDEN'",
+#   "_NET_WM_STATE@:32a *= '_NET_WM_STATE_MAXIMIZED_VERT'"
 ];
 
 
@@ -281,8 +277,7 @@
 # blur-background-exclude = []
 blur-background-exclude = [
   "window_type = 'dock'",
-  "window_type = 'desktop'",
-  "_GTK_FRAME_EXTENTS@:c"
+  "window_type = 'desktop'"
 ];
 
 
@@ -527,7 +522,7 @@
 #  Backend to use: "xrender", "glx" or "xr_glx_hybrid". xrender is the default one.
 #  GLX backend is typically much faster but depends on a sane driver.
 
-#backend = "glx";
+backend = "glx";
 
 # Enable/disable VSync.
 # vsync = false

I just ran picom from cli and deleted the bad lines as it suggested. I've no experience with picom. Occasionally I used to run compton or one of the older compositors (mostly ones from Brian Bidulock) in icewm or jwm, just for some transparency.

I did see those artefacts in your previous scrot and thought a graphics driver issue for sure.

I'm not sure qemu can do good enough graphics to be able to properly diagnose problems. I do have an old Dell Optiplex 760 desktop, one of those core2 duo ones that I can fire up and see what I can do, but I have limited time over the next 2 to 3 weeks as I'm covering someone at work, so long hours.

EDIT: Oh what was broken? Just didn't start at all untill I fixed all the config issues.

Last edited by micko01 (2025-02-23 08:25:39)

johnraff · 2025-02-23 09:01:49

^It starts OK for me, using the boron picom.conf.

I didn't see the warnings till I started it in a terminal:

john@trixie-tester:~$ picom  --backend xrender
[ 23/02/25 17:38:38.219 c2_parse_target WARN ] Type specifier is deprecated. Type "c" specified on target "_GTK_FRAME_EXTENTS" will be ignored, you can remove it.
[ 23/02/25 17:38:38.219 c2_parse_target WARN ] Type specifier is deprecated. Type "a" specified on target "_NET_WM_STATE" will be ignored, you can remove it.
[ 23/02/25 17:38:38.219 c2_parse_target WARN ] Format specifier is deprecated. Format "32" specified on target "_NET_WM_STATE" will be ignored, you can remove it.
[ 23/02/25 17:38:38.219 c2_parse_target WARN ] Type specifier is deprecated. Type "a" specified on target "_NET_WM_STATE" will be ignored, you can remove it.
[ 23/02/25 17:38:38.219 c2_parse_target WARN ] Format specifier is deprecated. Format "32" specified on target "_NET_WM_STATE" will be ignored, you can remove it.
[ 23/02/25 17:38:38.219 c2_parse_target WARN ] Type specifier is deprecated. Type "c" specified on target "_GTK_FRAME_EXTENTS" will be ignored, you can remove it.
[ 23/02/25 17:38:38.219 c2_parse_target WARN ] Type specifier is deprecated. Type "c" specified on target "_GTK_FRAME_EXTENTS" will be ignored, you can remove it.
[ 23/02/25 17:38:38.219 c2_parse_target WARN ] Type specifier is deprecated. Type "a" specified on target "_NET_WM_STATE" will be ignored, you can remove it.
[ 23/02/25 17:38:38.219 c2_parse_target WARN ] Format specifier is deprecated. Format "32" specified on target "_NET_WM_STATE" will be ignored, you can remove it.

Which boils down to:
Type "c" specified on target "_GTK_FRAME_EXTENTS" will be ignored, you can remove it.
Type "a" specified on target "_NET_WM_STATE" will be ignored, you can remove it.
Format "32" specified on target "_NET_WM_STATE" will be ignored, you can remove it.

I don't know how to test what the FRAME_EXTENTS are doing, but if this line is uncommented in the rounded-corners-exclude section, maximized windows don't have round corners:

"_NET_WM_STATE@:32a *= '_NET_WM_STATE_MAXIMIZED_VERT'"

I then tried removing all the type/format endings after the colon:

_NET_WM_STATE@
_GTK_FRAME_EXTENTS@

and all the warnings disappeared, and the corner suppression of maximized windows (the only one I could easily test) still worked.

So I wonder what the difference might have been in your setup to cause picom not to run?

But all this is pretty much voodoo to me...

I do have one 64bit laptop I could test some stuff on, but we'd like our picom settings to work on a qemu VM too I guess.

But I should definitely look if picom 12.5 is throwing graphic weirdness on that laptop too. Maybe if --backend glx can run, they'll go away.

I suspect if we could get to the bottom of why glx doesn't work on qemu it might sort things. It's no longer cool to have to enforce the xrender backend when the picom people seem to have almost abandoned it for glx.

Oh yes - your picom.conf set the backend to glx - no problems?
Although if you use the bl-compositor script it will set --backend xrender and 'backend = "glx"' in picom.conf is ignored.
'pgrep -a picom' will show the command line being used.

Last edited by johnraff (2025-02-23 09:04:32)

Head_on_a_Stick · 2025-02-23 12:55:05

johnraff wrote:

I'm having all kinds of trouble with picom 12.5 on my qemu VM right now, and trying to get a grip on it.
'--backend glx' just doesn't work at all

Seems fine here:

empty@Carbon:~$ systemd-detect-virt 
kvm
empty@Carbon:~$ pgrep -a picom
1461 picom --backend glx
empty@Carbon:~$

How are you starting QEMU? I think you need virtio-gpu for OpenGL to work properly.

I use this shell function (add the path to the disk image as the first argument):

function kvm-efi {
   qemu-system-x86_64 \
      -enable-kvm \
      -device intel-iommu \
      -m 2G \
      -cpu host \
      -machine q35 \
      -drive format=raw,cache=none,if=virtio,file="$1" \
      -drive if=pflash,format=raw,readonly=on,file=/home/empty/qemu/OVMF_CODE.4m.fd \
      -drive if=pflash,format=raw,file=/home/empty/qemu/OVMF_VARS_4M.secboot.fd \
      -device virtio-vga-gl \
      -display gtk,gl=on \
      -device virtio-sound-pci,audiodev=my_audiodev \
      -audiodev pa,id=my_audiodev
}

Debian provides the kvm wrapper so omit the -enable-kvm line if you use that instead of qemu-system-x86-64.

The -drive if=pflash lines are for UEFI to test Secure Boot under QEMU, they need the OVMF firmware files to work properly; just omit those lines to boot and install in non-UEFI mode.

EDIT: add this to the last line to boot an ISO image for installation to a bare disk image:

 -cdrom "$2" -boot d

Note that the ISO won't boot in UEFI mode if OVMF firmware containing NVRAM boot entries is added as an ipflash device.

Last edited by Head_on_a_Stick (2025-02-23 13:17:51)

hhh · 2025-02-23 16:48:33

johnraff wrote:

hhh wrote:
@johnraff, I think the easiest way to post my xfce4-panel profile is to upload the tar.bz2 file produced by xfce4-panel-profiles...
https://packages.debian.org/bookworm/xf … l-profiles
I can't upload it today, but will ASAP.
I'd never heard of xfce4-panel-profiles but that looks like a plan.
Thanks!
We might want to consider shipping xfce4-panel-profiles in BL for our users, looks like a substitute for all the tint2 utilities that we'll be forced to abandon. ( Sorry Damo )
BLOB will probably need it too.

+1 to adding xfce4-panel-profiles and xfce4-panel to our default installed-packages list.

johnraff · 2025-02-24 01:23:11

^xfce4-panel is already there!
The loss of tint2 from Trixie pretty much forced the situation.
https://github.com/BunsenLabs/bunsen-me … 7047cccc07
I haven't yet checked over the Recommends of various BL packages though...

I guess there's no objection to this?

#21 2025-02-22 04:37:29

Re: Carbon Themes (beta version)

#22 2025-02-22 05:49:31

Re: Carbon Themes (beta version)

#23 2025-02-22 08:45:49

Re: Carbon Themes (beta version)

#24 2025-02-22 17:29:01

Re: Carbon Themes (beta version)

#25 2025-02-22 17:40:21

Re: Carbon Themes (beta version)

#26 2025-02-22 17:49:49

Re: Carbon Themes (beta version)

#27 2025-02-22 17:56:42

Re: Carbon Themes (beta version)

#28 2025-02-22 17:58:15

Re: Carbon Themes (beta version)

#29 2025-02-23 01:00:40

Re: Carbon Themes (beta version)

#30 2025-02-23 01:35:58

Re: Carbon Themes (beta version)

#31 2025-02-23 01:39:00

Re: Carbon Themes (beta version)

#32 2025-02-23 02:52:46

Re: Carbon Themes (beta version)

#33 2025-02-23 03:18:32

Re: Carbon Themes (beta version)

#34 2025-02-23 06:24:07

Re: Carbon Themes (beta version)

#35 2025-02-23 07:59:34

Re: Carbon Themes (beta version)

#36 2025-02-23 08:21:35

Re: Carbon Themes (beta version)

#37 2025-02-23 09:01:49

Re: Carbon Themes (beta version)

#38 2025-02-23 12:55:05

Re: Carbon Themes (beta version)

#39 2025-02-23 16:48:33

Re: Carbon Themes (beta version)

#40 2025-02-24 01:23:11

Re: Carbon Themes (beta version)

Board footer