Carbon Themes (beta version)

hhh · 2025-02-20 02:27:18

A new thread focusing on the default desktop items and their themes.

Here's where I'm at now (with big-clock conky, that won't be the default config). Themes in the neofetch, this uses xfce4-panel instead of tint2...

Note that the OS is boron, I don't have carbon installed yet. Waiting for the transitional freeze in mid-March.

Also note that I spelled my host name incorrectly.

micko01 · 2025-02-20 08:45:57

^looks great

You want me to add some branding to login screen and grub screen? Like https://imgbox.com/KD4nTUcZ

johnraff · 2025-02-20 08:51:40

micko01 wrote:

^looks great

Very much agreed, although I'm a bit afraid the upgrade to Trixie might throw some spanners in the works.
Both picom and xfce4-panel have gone through big changes.

micko01 · 2025-02-20 10:20:48

Here's tint2 with some picom tweaks (bare metal)

Has remnants of labbe-material there but those icons are a custom hack, could be applied to any theme, although far beyond the scope of a stock theme! And BTW fastfetch -c neofetch, but has it's issues in that capture.

[later]
and here's labwc/sfwbar with those icons fixed and same fastfetch bugs.

Last edited by micko01 (2025-02-20 11:47:52)

PackRat · 2025-02-20 13:26:49

Those look good.

johnraff · 2025-02-21 00:25:07

micko01 wrote:

Here's tint2 with some picom tweaks (bare metal)

Where did you get that tint2? It's absent from Trixie right now, and we don't know if/when it will return.

johnraff · 2025-02-21 00:30:25

micko01 wrote:

and here's labwc/sfwbar with those icons fixed and same fastfetch bugs.
https://thumbs2.imgbox.com/78/52/JKjQWMn2_t.png

Those icons look OK in fact (maybe the plain directory icons look a bit chubby by comparison with the others). Do you think we should consider Material-Solarized-Bark++ for the whole system, not just the menu icons? Hesitant to drop your labbe icons, but there's something to be said for only having to install one icon theme.

Head_on_a_Stick · 2025-02-21 07:15:38

That theme looks great. Good work.

micko01 · 2025-02-21 09:23:05

johnraff wrote:

micko01 wrote:
and here's labwc/sfwbar with those icons fixed and same fastfetch bugs.
https://thumbs2.imgbox.com/78/52/JKjQWMn2_t.png
Those icons look OK in fact (maybe the plain directory icons look a bit chubby by comparison with the others). Do you think we should consider Material-Solarized-Bark++ for the whole system, not just the menu icons? Hesitant to drop your labbe icons, but there's something to be said for only having to install one icon theme.

Sure

Material-Solarized-Bark++ and Material-Solarized-Sage++ could certainly be extended with more application icons to try and avoid the crappy shipped icons with applications (not that there all crappy but they aren't very theme friendly).

Maybe I can do something with the chubbiness of the directory icons, I'll take a look over the weekend.

For a one line sed operation they are about the easiest icon themes I've ever "made"

Edit: speaking of sed .. s/there/they're

Last edited by micko01 (2025-02-21 11:49:18)

micko01 · 2025-02-21 11:46:54

johnraff wrote:

micko01 wrote:
Here's tint2 with some picom tweaks (bare metal)
Where did you get that tint2? It's absent from Trixie right now, and we don't know if/when it will return.

The one in sid. Installed when I installed all the bunsen stuff (coz I have unstable enabled). Only the picom config was broken and that was relatively easy to fix.

hhh · 2025-02-21 18:58:22

Head_on_a_Stick wrote:

That theme looks great. Good work.

Thanks, and thanks to micko01 for working on icons, and to John and everyone for their input and encouragement.

I've been using this desktop for the last 4 days now, and it's a very relaxed experience. We really cooked with Boron, that was a big leap forward in making the OB desktop experience better.

greenjeans · 2025-02-21 20:16:31

I have to say, the work you guys put into theming and icons is impressive and inspiring, all the more so because it's such a small crew doing it. The theme work in fact when I first downloaded Boron was what made me want to join this forum and see what all goes into making BL.

Makes me want to do better myself with my own projects. Looking forward to seeing the finished product in Carbon.

micko01 · 2025-02-21 21:26:07

micko01 wrote:

johnraff wrote:
micko01 wrote:
and here's labwc/sfwbar with those icons fixed and same fastfetch bugs.
https://thumbs2.imgbox.com/78/52/JKjQWMn2_t.png
Those icons look OK in fact (maybe the plain directory icons look a bit chubby by comparison with the others). Do you think we should consider Material-Solarized-Bark++ for the whole system, not just the menu icons? Hesitant to drop your labbe icons, but there's something to be said for only having to install one icon theme.
Sure
Material-Solarized-Bark++ and Material-Solarized-Sage++ could certainly be extended with more application icons to try and avoid the crappy shipped icons with applications (not that there all crappy but they aren't very theme friendly).
Maybe I can do something with the chubbiness of the directory icons, I'll take a look over the weekend.
For a one line sed operation they are about the easiest icon themes I've ever "made"
Edit: speaking of sed .. s/there/they're

I'm putting changing the folder icons in Material-Solarized-Bark++ and Material-Solarized-Sage++ on the back burner a.k.a in the too hard basket.

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]++ ?

micko01 · 2025-02-22 00:57:07

Ok, getting somewhere

This is in labwc but openbox should behave similarly.

..later and openbox

here's the index.theme

[Icon Theme]
Name=labbe-min-bark
Inherits=Material-Solarized-Bark++
Comment=A GTK Icon Theme by zigbert, technosaurus and 01micko
Directories=16,16/places,16/apps,16@2x,22,22/places,22/apps,22@2x,24,24/places,24/apps,24@2x,32,32/places,32/apps,32@2x,48,48/places,48/apps,48@2x,64,64/places,64/apps,64@2x,scalable,scalable/places,scalable/apps,scalable@2x

[16]
Size=16
Context=16
Type=fixed

[16/places]
Size=16
Context=Places
Type=fixed

[16/apps]
Size=16
Context=Apps
Type=fixed

[16@2x]
Size=16
Scale=2
Context=16@2x
Type=fixed

[22]
Size=22
Context=22
Type=fixed

[22/places]
Size=22
Context=Places
Type=fixed

[22/apps]
Size=22
Context=Apps
Type=fixed

[22@2x]
Size=22
Scale=2
Context=22@2x
Type=fixed

[24]
Size=24
Context=24
Type=fixed

[24/places]
Size=24
Context=Places
Type=fixed

[24/apps]
Size=24
Context=Apps
Type=fixed

[24@2x]
Size=24
Scale=2
Context=24@2x
Type=fixed

[32]
Size=32
Context=32
Type=fixed

[32/places]
Size=32
Context=Places
Type=fixed

[32/apps]
Size=32
Context=Apps
Type=fixed

[32@2x]
Size=32
Scale=2
Context=32@2x
Type=fixed

[48]
Size=48
Context=48
Type=fixed

[48/places]
Size=48
Context=Places
Type=fixed

[48/apps]
Size=48
Context=Apps
Type=fixed

[48@2x]
Size=48
Scale=2
Context=48@2x
Type=fixed

[64]
Size=64
Context=64
Type=fixed

[64/places]
Size=64
Context=Places
Type=fixed

[64/apps]
Size=64
Context=Apps
Type=fixed

[64@2x]
Size=64
Scale=2
Context=64@2x
Type=fixed

[scalable]
Size=256
Context=Scalable
Type=Scalable
MinSize=8
MaxSize=512

[scalable/places]
Size=256
Context=Places
Type=Scalable
MinSize=8
MaxSize=512

[scalable/apps]
Size=256
Context=Apps
Type=Scalable
MinSize=8
MaxSize=512

[scalable@2x]
Size=256
Context=Scalable@2x
Type=Scalable
MinSize=8
MaxSize=512

There are only 3 folder variants and a few application icons. Also, the Solarized icons miss a link, org.xfce.thunar.svg. I added it in my local install but I'll add it to github. Might also be a few more.

Last edited by micko01 (2025-02-22 01:16:24)

johnraff · 2025-02-22 02:03:37

micko01 wrote:

johnraff wrote:
Where did you get that tint2?
The one in sid. Installed when I installed all the bunsen stuff (coz I have unstable enabled). Only the picom config was broken and that was relatively easy to fix.

I think we're pretty much obliged to drop tint2. Even if the maintainer steps up and provides a version that builds on Trixie, the upstream developer announced some time ago that they've frozen the project, so any security fixes will only come via Debian patches.

I've now (yesterday) dropped tint2 from the netinstall script and meta-package package lists because its unavailability on the Trixie repo was blocking installs, and provisionally replaced it with xfce4-panel. It would be good to ship a usable xfce4-panel config in bunsen-configs asap...

There's a whole bunch of stuff I'm trying to keep in mind, but right now I'm looking at picom, because on Trixie/Carbon it's been messing up my whole desktop and I also was having doubts about our current config inherited from Boron.

The picom.sample.conf they ship changed quite a bit between 9.1 and 12.5 and I'm merging the changes into our picom.conf, but if you've fixed it, it would speed up my work no end to know what changes you made. Could you post it here? Thanks!

johnraff · 2025-02-22 02:10:09

hhh wrote:

I've been using this desktop for the last 4 days now, and it's a very relaxed experience. We really cooked with Boron, that was a big leap forward in making the OB desktop experience better.

Boron is very nice indeed and got a whole lot of positive feedback.

You're currently using xfce4-panel, right? If you'd like to post your config I'll drop it directly into bunsen-configs. Even if we want to tweak it later, it will be great to have something to build on. Now tint2 is gone from Trixie, providing a replacement has become somewhat urgent.

People upgrading from Boron to Carbon won't notice, because they'll inherit the bookworm tint2, but fresh Carbon installs will be messed up till we provide a replacement.

johnraff · 2025-02-22 02:13:26

greenjeans wrote:

The theme work in fact when I first downloaded Boron was what made me want to join this forum and see what all goes into making BL.

Thanks @greenjeans, and thanks for the work you've already put in with the QT theming!

I've long thought that the graphics stack was one of BunsenLabs' main strong points. CrunchBang too for that matter.

johnraff · 2025-02-22 02:19:35

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.

micko01 · 2025-02-22 03:10:36

~/.config/picom.conf

##  Picom user configuration file (~/.config/picom.conf)
##  written for BunsenLabs Boron
##  with reference to: /usr/share/doc/picom/examples/picom.sample.conf
##  http://duncanlock.net/blog/2013/06/07/how-to-switch-to-compton-for-beautiful-tear-free-compositing-in-xfce/
##  and https://forums.bunsenlabs.org/viewtopic.php?pid=61249#p61249
##
##  Various people have contributed to this file,
##  so the meaning of "I" is not well defined.
##
##  In most cases 'man picom' has more information.
##  See also: https://wiki.archlinux.org/title/Picom


#################################
#
#  Shadows
#
#################################

# Enabled client-side shadows on windows. Note desktop windows
# (windows with '_NET_WM_WINDOW_TYPE_DESKTOP') never get shadow,
# unless explicitly requested using the wintypes option.
#
# shadow = false
shadow = true;

# The blur radius for shadows, in pixels. (defaults to 12)
#shadow-radius = 35;
shadow-radius = 12;

# The opacity of shadows. (0.0 - 1.0,  defaults to 0.75)
#shadow-opacity = 0.30;
shadow-opacity = 0.45;

# The left offset for shadows, in pixels. (defaults to -15)
#shadow-offset-x = -32;
shadow-offset-x = -8;

# The top offset for shadows, in pixels. (defaults to -15)
#shadow-offset-y = -32;
shadow-offset-y = -8;

# Avoid drawing shadows on dock/panel windows. This option is deprecated,
# you should use the *wintypes* option in your config file instead.
#
# no-dock-shadow = false

# Don't draw shadows on drag-and-drop windows. This option is deprecated,
# you should use the *wintypes* option in your config file instead.
#
# no-dnd-shadow = false

#  Set if you want different colour shadows

# Red color value of shadow (0.0 - 1.0, defaults to 0).
# shadow-red = 0

# Green color value of shadow (0.0 - 1.0, defaults to 0).
# shadow-green = 0

# Blue color value of shadow (0.0 - 1.0, defaults to 0).
# shadow-blue = 0

# Hex string color value of shadow (#000000 - #FFFFFF, defaults to #000000). This option will override options set shadow-(red/green/blue)
# shadow-color = "#000000"

# Do not paint shadows on shaped windows. Note shaped windows
# here means windows setting its shape through X Shape extension.
# Those using ARGB background is beyond our control.
# Deprecated, use
#   shadow-exclude = 'bounding_shaped'
# or
#   shadow-exclude = 'bounding_shaped && !rounded_corners'
# instead.
#
# shadow-ignore-shaped = ''

# Specify a list of conditions of windows that should have no shadow.
#
# examples:
#   shadow-exclude = "n:e:Notification";
#
#  The shadow exclude options are helpful if you have shadows enabled.
#  Due to the way picom draws its shadows, certain applications will have visual glitches
#  (most applications are fine, only apps that do weird things with xshapes or argb are affected).
#  This list includes all the affected apps I found in my testing.
#  The "! name~=''" part excludes shadows on any "Unknown" windows, this prevents a visual glitch with the XFWM alt tab switcher.
#  The "_GTK_FRAME_EXTENTS@:c" entry is to fix dual shadows with GTK3 Client Side Decorations.
#  '_NET_WM_STATE_HIDDEN' entry, see https://wiki.archlinux.org/title/Picom#Tabbed_windows_(shadows_and_transparency)
#  '_NET_WM_STATE_MAXIMIZED_VERT' entry excludes maximized windows
# shadow-exclude = []
shadow-exclude = [
    "! name~=''",
#    "name = 'jgmenu'",
    "name = 'Notification'",
    "name = 'wbar'",
    "name = 'Docky'",
    "name = 'Kupfer'",
#    "name = 'xfce4-notifyd'",
    "name *= 'VirtualBox'",
    "name *= 'VLC'",
    "name *= 'Chromium'",
    "name *= 'Chrome'",
    "class_g ?= 'plank'", # see wintypes
    "class_g ?= 'picom'",
    "class_g = 'Tint2'",
    "class_g ?= 'Conky'",
    "class_g = 'Kupfer'",
    "class_g = 'Synapse'",
    "class_g ?= 'Notify-osd'",
    "class_g ?= 'Cairo-dock'",
#    "class_g ?= 'Xfce4-notifyd'",
    "class_g ?= 'Xfce4-power-manager'",
    "window_type = 'desktop'"
];

# Specify a list of conditions of windows that should have no shadow painted over, such as a dock window.
# clip-shadow-above = []

# Specify a X geometry that describes the region in which shadow should not
# be painted in, such as a dock window region. Use
#    shadow-exclude-reg = "x10+0+0"
# for example, if the 10 pixels on the bottom of the screen should not have shadows painted on.
#
# shadow-exclude-reg = ""

# Crop shadow of a window fully on a particular Xinerama screen to the screen.
# xinerama-shadow-crop = false


#################################
#           Fading              #
#################################

# Fade windows in/out when opening/closing and when opacity changes,
#  unless no-fading-openclose is used.
# fading = false
fading = true;

# Opacity change between steps while fading in. (0.01 - 1.0, defaults to 0.028)
# fade-in-step = 0.028
fade-in-step = 0.06;

# Opacity change between steps while fading out. (0.01 - 1.0, defaults to 0.03)
# fade-out-step = 0.03
fade-out-step = 1.0;

# The time between steps in fade step, in milliseconds. (> 0, defaults to 10)
#fade-delta = 0

#  Specify a list of conditions of windows that should not be faded.
#  (Some might need setting in wintypes below.)
#fade-exclude = ["name = 'jgmenu'"];

#  Fade windows in/out when opening/closing
#no-fading-openclose = true;

#  Do not fade destroyed ARGB windows with WM frame. Workaround of bugs in Openbox, Fluxbox, etc.
no-fading-destroyed-argb = true;


#################################
#   Transparency / Opacity      #
#################################

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

# Opacity of window titlebars and borders. (0.1 - 1.0, disabled by default)
# frame-opacity = 0.7;
frame-opacity = 1.0;

# Default opacity for dropdown menus and popup menus. (0.0 - 1.0, defaults to 1.0)
# Option `menu-opacity` is deprecated, and will be removed.
# Please use the wintype option `opacity` of `popup_menu` and `dropdown_menu` instead.
# menu-opacity = 1.0;

# Let inactive opacity set by -i override the '_NET_WM_WINDOW_OPACITY' values of windows.
# inactive-opacity-override = true
inactive-opacity-override = false;

# Default opacity for active windows. (0.0 - 1.0, defaults to 1.0)
active-opacity = 1.0;

# Dim inactive windows. (0.0 - 1.0, defaults to 0.0)
# inactive-dim = 0.2

# Specify a list of conditions of windows that should always be considered focused.
# focus-exclude = []
#focus-exclude = [ "class_g = 'Cairo-clock'" ];

# Use fixed inactive dim value, instead of adjusting according to window opacity.
# inactive-dim-fixed = 1.0

# Specify a list of opacity rules, in the format `PERCENT:PATTERN`,
# like `50:name *= "Firefox"`. picom-trans is recommended over this.
# Note we don't make any guarantee about possible conflicts with other
# programs that set '_NET_WM_WINDOW_OPACITY' on frame or client windows.
# example:
#    opacity-rule = [ "80:class_g = 'URxvt'" ];
#
# opacity-rule = []


#################################
#           Corners             #
#################################

# Sets the radius of rounded window corners. When > 0, the compositor will
# round the corners of windows. Does not interact well with
# `transparent-clipping`.
corner-radius = 10;

# Exclude conditions for rounded corners.
# Also see: https://github.com/owl4ce/dotfiles/discussions/177
rounded-corners-exclude = [
    "! name~=''",    # exclude windows with no name
#    "class_g = 'tint2'",
    "class_g  = 'Conky'",
#   "window_type = 'menu'",
#   "window_type = 'dock'",
    "window_type = 'desktop'"
#   "window_type = 'dropdown_menu'",
#   "window_type = 'popup_menu'",
#   "window_type = 'tooltip'",
#   "window_type = 'utility'"
#   "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'"
];


#################################
#     Background-Blurring       #
#################################

# Parameters for background blurring,
# see the *BLUR* section of the manual for more information.

# blur-method =
# blur-size = 12
#
# blur-deviation = false
#
# blur-strength = 5

# Blur background of semi-transparent / ARGB windows.
# Bad in performance, with driver-dependent behavior.
# The name of the switch may change without prior notifications.
#
# blur-background = false

# Blur background of windows when the window frame is not opaque.
# Implies:
#    blur-background
# Bad in performance, with driver-dependent behavior. The name may change.
#
# blur-background-frame = false


# Use fixed blur strength rather than adjusting according to window opacity.
# Do not let blur radius adjust based on window opacity.
#blur-background-fixed = false;

# Specify the blur convolution kernel, with the following format:
# example:
#   blur-kern = "5,5,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1";
#
# blur-kern = ""
#blur-kern = "3x3box";


# Exclude conditions for background blur.
# blur-background-exclude = []
blur-background-exclude = [
  "window_type = 'dock'",
  "window_type = 'desktop'"
];


#################################
#       General Settings        #
#################################

# Enable remote control via D-Bus. See the *D-BUS API* section in the manual for more details.
# The D-Bus methods and signals are not yet stable, thus undocumented right now.
# dbus = false

# Try to detect WM windows (a non-override-redirect window with no
# child that has 'WM_STATE') and mark them as active.
#
# mark-wmwin-focused = false
mark-wmwin-focused = true;

# Mark override-redirect windows that doesn't have a child window with 'WM_STATE' focused.
# mark-ovredir-focused = false
mark-ovredir-focused = true;

# Try to detect windows with rounded corners and don't consider them
# shaped windows. The accuracy is not very high, unfortunately.
#
# detect-rounded-corners = false
detect-rounded-corners = true;


# Detect '_NET_WM_OPACITY' on client windows, useful for window managers
# not passing '_NET_WM_OPACITY' of client windows to frame windows.
# This prevents opacity being ignored for some apps.
# For example without this enabled my xfce4-notifyd is 100% opacity no matter what.
#
# detect-client-opacity = false
detect-client-opacity = true;

# Use EWMH '_NET_ACTIVE_WINDOW' to determine currently focused window,
# rather than listening to 'FocusIn'/'FocusOut' event. Might have more accuracy,
# provided that the WM supports it. (openbox should be OK)
#
use-ewmh-active-win = true;

# Unredirect all windows if a full-screen opaque window is detected,
# to maximize performance for full-screen windows. Known to cause flickering
# when redirecting/unredirecting windows.
# paint-on-overlay may make the flickering less obvious.
#
unredir-if-possible = true;

# Delay before unredirecting the window, in milliseconds. Defaults to 0.
# unredir-if-possible-delay = 0

# Conditions of windows that shouldn't be considered full-screen for unredirecting screen.
# unredir-if-possible-exclude = []

# Use 'WM_TRANSIENT_FOR' to group windows, and consider windows
# in the same group focused at the same time.
#
# detect-transient = false
detect-transient = true;

# Use 'WM_CLIENT_LEADER' to group windows, and consider windows in the same
# group focused at the same time. This usually means windows from the same application
# will be considered focused or unfocused at the same time.
# 'WM_TRANSIENT_FOR' has higher priority if detect-transient is enabled, too.
#
# detect-client-leader = false
detect-client-leader = true;

# Resize damaged region by a specific number of pixels.
# A positive value enlarges it while a negative one shrinks it.
# If the value is positive, those additional pixels will not be actually painted
# to screen, only used in blur calculation, and such. (Due to technical limitations,
# with use-damage, those pixels will still be incorrectly painted to screen.)
# Primarily used to fix the line corruption issues of blur,
# in which case you should use the blur radius value here
# (e.g. with a 3x3 kernel, you should use `--resize-damage 1`,
# with a 5x5 one you use `--resize-damage 2`, and so on).
# May or may not work with *--glx-no-stencil*. Shrinking doesn't function correctly.
#
# resize-damage = 1

# Specify a list of conditions of windows that should be painted with inverted color.
# Resource-hogging, and is not well tested.
#
# invert-color-include = []

# Disable the use of damage information.
# This cause the whole screen to be redrawn everytime, instead of the part of the screen
# has actually changed. Potentially degrades the performance, but might fix some artifacts.
# The opposing option is use-damage
#
# no-use-damage = false
use-damage = true;

# Use X Sync fence to sync clients' draw calls, to make sure all draw
# calls are finished before picom starts drawing. Needed on nvidia-drivers
# with GLX backend for some users.
#
# xrender-sync-fence = false

# GLX backend: Use specified GLSL fragment shader for rendering window contents.
# See `compton-default-fshader-win.glsl` and `compton-fake-transparency-fshader-win.glsl`
# in the source tree for examples.
#
# glx-fshader-win = ""

# Force all windows to be painted with blending. Useful if you
# have a glx-fshader-win that could turn opaque pixels transparent.
#
# force-win-blend = false

# Do not use EWMH to detect fullscreen windows.
# Reverts to checking if a window is fullscreen based only on its size and coordinates.
#
# no-ewmh-fullscreen = false

# Dimming bright windows so their brightness doesn't exceed this set value.
# Brightness of a window is estimated by averaging all pixels in the window,
# so this could comes with a performance hit.
# Setting this to 1.0 disables this behaviour. Requires --use-damage to be disabled. (default: 1.0)
#
# max-brightness = 1.0

# Make transparent windows clip other windows like non-transparent windows do,
# instead of blending on top of them.
#
# transparent-clipping = false

# Set the log level. Possible values are:
#  "trace", "debug", "info", "warn", "error"
# in increasing level of importance. Case doesn't matter.
# If using the "TRACE" log level, it's better to log into a file
# using *--log-file*, since it can generate a huge stream of logs.
#
# log-level = "debug"
log-level = "warn";

# Set the log file.
# If *--log-file* is never specified, logs will be written to stderr.
# Otherwise, logs will to written to the given file, though some of the early
# logs might still be written to the stderr.
# When setting this option from the config file, it is recommended to use an absolute path.
#
# log-file = '/path/to/your/log/file'

# Show all X errors (for debugging)
# show-all-xerrors = false

# Write process ID to a file.
# write-pid-path = '/path/to/your/log/file'

#################################
#
#  Window type settings
#
#################################

# 'WINDOW_TYPE' is one of the 15 window types defined in EWMH standard:
#     "unknown", "desktop", "dock", "toolbar", "menu", "utility",
#     "splash", "dialog", "normal", "dropdown_menu", "popup_menu",
#     "tooltip", "notification", "combo", and "dnd".
#
# Following per window-type options are available: ::
#
#   fade, shadow:::
#     Controls window-type-specific shadow and fade settings.
#
#   opacity:::
#     Controls default opacity of the window type.
#
#   focus:::
#     Controls whether the window of this type is to be always considered focused.
#     (By default, all window types except "normal" and "dialog" has this on.)
#
#   full-shadow:::
#     Controls whether shadow is drawn under the parts of the window that you
#     normally won't be able to see. Useful when the window has parts of it
#     transparent, and you want shadows in those areas.
#
#   clip-shadow-above:::
#     Controls wether shadows that would have been drawn above the window should
#     be clipped. Useful for dock windows that should have no shadow painted on top.
#
#   redir-ignore:::
#     Controls whether this type of windows should cause screen to become
#     redirected again after been unredirected. If you have unredir-if-possible
#     set, and doesn't want certain window to cause unnecessary screen redirection,
#     you can set this to `true`.
#
#wintypes:
#{
#  tooltip = { fade = true; shadow = true; opacity = 0.75; focus = true; full-shadow = false; };
#  dock = { shadow = false; clip-shadow-above = true; }
#  dnd = { shadow = false; }
#  popup_menu = { opacity = 0.8; }
#  dropdown_menu = { opacity = 0.8; }
#};

wintypes:
{
  dock = { shadow = false; };
  tooltip = { fade = false; shadow = false; };
  menu = { fade = false; };
  dropdown_menu = { fade = false; opacity = 1.0; };
  popup_menu =  { fade = false; opacity = 1.0; };
};


########################################################################
###  "advanced" machine specific options  ###

#  It is possible to set these in /etc/bunsen/picom-startup
#  where they will be applied for all users, but can also be set here.
#  Any settings in /etc/bunsen/picom-startup will have priority.
#
#  Some old (2017) forum threads which might be of historical interest:
#  https://forums.bunsenlabs.org/viewtopic.php?id=4176
#  https://forums.bunsenlabs.org/viewtopic.php?pid=61249#p61249
#  https://forums.bunsenlabs.org/viewtopic.php?id=3699
#
#  Two graphics test pages:
#  This one is flashing green and red fast enough that it should look
#  like a flickery orange colour:
#  https://launchpadlibrarian.net/274755154/kenjo_vidtest_60fps.mp4
#  This is a screen tearing test for vsync:
#  https://www.youtube.com/watch?v=MfL_JkcEFbE

########################################################################

# Daemonize process. Fork to background after initialization. Causes issues with certain (badly-written) drivers.
# In a BunsenLabs sesssion, picom is forked anyway, so this setting is not needed.
# daemon = false


#################################
#
#  Backend
#
#################################

#  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";

# Enable/disable VSync.
# vsync = false
# vsync = true


#################################
#
#  GLX backend
#
#################################

# GLX backend: Avoid using stencil buffer, useful if you don't have a stencil buffer.
# This may not work with --blur-background. Tests show a 15% performance boost.
# Might cause incorrect opacity when rendering transparent content (but never
# practically happened) and may not work with blur-background.
# "My tests show a 15% performance boost. Recommended."
#
# glx-no-stencil = true

# GLX backend: Avoid rebinding pixmap on window damage.
# Probably could improve performance on rapid window content changes,
# but is known to break things on some drivers (LLVMpipe, xf86-video-intel, etc.).
# "This option causes lockups in Virtualbox."
# Recommended if it works.
#
# glx-no-rebind-pixmap = true

# GLX backend: Use specified GLSL fragment shader for rendering window contents.
# See `compton-default-fshader-win.glsl` and `compton-fake-transparency-fshader-win.glsl`
# in the source tree for examples.
#
# glx-fshader-win = ''

# Force all windows to be painted with blending. Useful if you
# have a glx-fshader-win that could turn opaque pixels transparent.
#
# force-win-blend = true

#################################

# Use X Sync fence to sync clients' draw calls, to make sure all draw
# calls are finished before picom starts drawing. Needed on nvidia-drivers
# with GLX backend for some users.
#
# xrender-sync-fence = false

# Specify refresh rate of the screen. If not specified or 0, picom will
# try detecting this with X RandR extension.
#
# refresh-rate = 60
#refresh-rate = 0

# Limit picom to repaint at most once every 1 / 'refresh_rate' second to
# boost performance. This should not be used with
#   vsync drm/opengl/opengl-oml
# as they essentially does sw-opti's job already,
# unless you wish to specify a lower refresh rate than the actual value.
#
# sw-opti =

HTH

johnraff · 2025-02-22 03:34:51

^thanks!

#1 2025-02-20 02:27:18

Carbon Themes (beta version)

#2 2025-02-20 08:45:57

Re: Carbon Themes (beta version)

#3 2025-02-20 08:51:40

Re: Carbon Themes (beta version)

#4 2025-02-20 10:20:48

Re: Carbon Themes (beta version)

#5 2025-02-20 13:26:49

Re: Carbon Themes (beta version)

#6 2025-02-21 00:25:07

Re: Carbon Themes (beta version)

#7 2025-02-21 00:30:25

Re: Carbon Themes (beta version)

#8 2025-02-21 07:15:38

Re: Carbon Themes (beta version)

#9 2025-02-21 09:23:05

Re: Carbon Themes (beta version)

#10 2025-02-21 11:46:54

Re: Carbon Themes (beta version)

#11 2025-02-21 18:58:22

Re: Carbon Themes (beta version)

#12 2025-02-21 20:16:31

Re: Carbon Themes (beta version)

#13 2025-02-21 21:26:07

Re: Carbon Themes (beta version)

#14 2025-02-22 00:57:07

Re: Carbon Themes (beta version)

#15 2025-02-22 02:03:37

Re: Carbon Themes (beta version)

#16 2025-02-22 02:10:09

Re: Carbon Themes (beta version)

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

Re: Carbon Themes (beta version)

#18 2025-02-22 02:19:35

Re: Carbon Themes (beta version)

#19 2025-02-22 03:10:36

Re: Carbon Themes (beta version)

#20 2025-02-22 03:34:51

Re: Carbon Themes (beta version)

Board footer