January 2022 Screenshots

hhh · 2022-01-15 03:05:34

^ Pardon me... Would you have any Grey Poupon?

But of course.

Grey Poupon. One of life's finer pleasures.

https://www.youtube.com/watch?v=NmannAYiwh0

And I'd argue that this is one of the best advertisements ever made, Grey Poupon...

https://www.youtube.com/watch?v=dzwkpASLExg

hhh · 2022-01-15 03:31:30

OT...

Wallpaper by @johnraff...

https://forums.bunsenlabs.org/viewtopic … 91#p119791

Themes by hhh. GTK3 via Oomox. Icon colors via Papirus Folders.

hhh · 2022-01-15 04:15:25

hhh · 2022-01-15 19:02:45

DeepDayze · 2022-01-15 19:24:43

hhh wrote:

https://imgur.com/9WiVzoTt.png

hhh wrote:

I already posted this in Dev, but I like this simple one so here it is again...
https://imgur.com/fvNaLRTt.png

Both of these are nice and why not have these themes/wallpapers for Beryllium?

hhh · 2022-01-15 20:44:10

^ We will, I just need to get them all finished and uploaded to GitHub.

hhh · 2022-01-16 07:45:04

Having fun setting up a Plasma session over BL Beryllium...

A lot of fun...

deleted0 · 2022-01-21 21:16:27

Latest desktop:

8bit

Last edited by deleted0 (2022-01-21 21:21:57)

hhh · 2022-01-22 18:19:20

^ Nice. If you're using xfce4-panel, you can get a horizontal clock by setting the panel to "Deskbar" mode and making it wide enough to display the clock fully.

deleted0 · 2022-01-22 19:17:07

Thanks for reminding me. I haven't got to the clock yet. 12 hour display without a leading zero; sideways is fine.

8bit

deleted0 · 2022-01-22 21:12:57

Also hadn't got to the menu yet:

8bit

hhh · 2022-01-23 04:37:03

Embracing the ol' skool. Every time I install these icons the nostalgia hits me like a tsunami. picom is awesome and I finally themed it all decently...

picom.conf...

##  Picom user configuration file (~/.config/picom.conf)
##  written for BunsenLabs Beryllium
##  custom transparency and wintypes/current Firefox tweaks by hhhorb
##  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 = 12
shadow-radius = 7;

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

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

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

# 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

# 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.
# shadow-exclude = []
shadow-exclude = [
#    "! name~=''",
#    "name = 'jgmenu'",
    "name = 'tint2'",
    "name = 'Notification'",
    "name = 'wbar'",
    "name = 'Plank'",
    "name = 'Docky'",
    "name = 'Kupfer'",
#    "name = 'xfce4-notifyd'",
    "name *= 'VirtualBox'",
    "name *= 'VLC'",
    "name *= 'picom'",
    "name *= 'Chromium'",
    "name *= 'Chrome'",
    "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'",
    "_GTK_FRAME_EXTENTS@:c"
];

# 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 = 0.03;

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

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

# 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_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'" ];
#

# alpha-step seems no longer to be supported
# https://github.com/yshui/picom/pull/48 https://github.com/yshui/picom/issues/359
# alpha-step = 0.06;


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

# Parameters for background blurring, see the *BLUR* section for more information.
# blur-method =
# blur-size = 12
#
# blur-deviation = false

# 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'",
  "_GTK_FRAME_EXTENTS@:c"
];


#################################
#       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. '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

# 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.
#
#   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; }
#  dnd = { shadow = false; }
#  popup_menu = { opacity = 0.8; }
#  dropdown_menu = { opacity = 0.8; }
#};

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


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

# 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 =

johnraff · 2022-01-23 04:58:02

^Definitely in favour of some drop shadow. The active windows stand out better.

hhh · 2022-01-23 05:20:04

^ I had window shadows at 7 radius, here they are 10 (default is 12px). I think you can see them even with this dark gnome wallpaper. Keeping it at 10, thanks for the suggestion!

BTW, RAM usage... not bad, eh? Under 700 with FF and audacious running.

hhh · 2022-01-25 21:35:18

johnraff · 2022-01-26 04:37:31

hhh wrote:

^ I had window shadows at 7 radius, here they are 10 (default is 12px). I think you can see them even with this dark gnome wallpaper. Keeping it at 10, thanks for the suggestion!

I guess a lot depends on the screen resolution. The default shadows looked very big and blurry to me, but hdpi will require bigger shadows, so we have to compromise.

My VM is very small at 1024x768 and I'm using these picom settings:

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

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

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

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

So the same radius as yours, and while I slightly prefer the 0.6 opacity it doesn't seem to make a huge difference. I'm OK with the default 0.75 for that matter.

The -2 offset does look more like a shadow to me though, than -7. Minus relative to what is very unclear, as offset = 0 throws a shadow definitely offset right-bottom from the window, while the "default" of -15 is quite a big offset to the left-top! In fact, on my VM, offset x/y = -7 looks like no offset at all. Are these settings some kind of leftover from compton that mean something quite different with picom?

I enabled this in the shadow-exclude list though:

    "! name~=''",

I think it was to suppress drop shadows of the tint2 popups - taskbar and systray, which I found quite annoying. Spent some time with that issue but now barely remember which settings finally did the job.
I think this was also needed in the wintypes: at the bottom:

tooltip = { fade = false; shadow = false; };

If you felt like having a look?

brontosaurusrex · 2022-01-26 13:18:53

Pubg

Last edited by brontosaurusrex (2022-01-26 13:20:13)

sleekmason · 2022-01-30 14:51:50

Thought I would post a shot of the fine work PPC over at antiX has done with their calendar app. You can store dated info and search for it again by keyword. Really neat. The script itself is easy to adjust to your needs.

Link to the topic there:
antiX-transformation-pack

Please note that the version shown is using gnome icons and a different initial entry. The original uses the Papirus icons!

phuturism · 2022-01-31 00:33:30

Beryllium using bspwm as window manager, fairly stock :-)

cmatrix and btm (sys monitor) in terminals

another view, using pywal to change background and terminal colours... still working on term consistency with this. moc as music player

Last edited by phuturism (2022-01-31 00:41:12)

hhh · 2022-01-31 04:34:26

End of the month. BunsenLabs, Openbox/tint2/conky/picom/jgmenu, etc...

#41 2022-01-15 03:05:34

Re: January 2022 Screenshots

#42 2022-01-15 03:31:30

Re: January 2022 Screenshots

#43 2022-01-15 04:15:25

Re: January 2022 Screenshots

#44 2022-01-15 19:02:45

Re: January 2022 Screenshots

#45 2022-01-15 19:24:43

Re: January 2022 Screenshots

#46 2022-01-15 20:44:10

Re: January 2022 Screenshots

#47 2022-01-16 07:45:04

Re: January 2022 Screenshots

#48 2022-01-21 21:16:27

Re: January 2022 Screenshots

#49 2022-01-22 18:19:20

Re: January 2022 Screenshots

#50 2022-01-22 19:17:07

Re: January 2022 Screenshots

#51 2022-01-22 21:12:57

Re: January 2022 Screenshots

#52 2022-01-23 04:37:03

Re: January 2022 Screenshots

#53 2022-01-23 04:58:02

Re: January 2022 Screenshots

#54 2022-01-23 05:20:04

Re: January 2022 Screenshots

#55 2022-01-25 21:35:18

Re: January 2022 Screenshots

#56 2022-01-26 04:37:31

Re: January 2022 Screenshots

#57 2022-01-26 13:18:53

Re: January 2022 Screenshots

#58 2022-01-30 14:51:50

Re: January 2022 Screenshots

#59 2022-01-31 00:33:30

Re: January 2022 Screenshots

#60 2022-01-31 04:34:26

Re: January 2022 Screenshots

Board footer