Carbon TODO

hhh · 2025-12-18 17:13:46

Make sure it's not a picom issue...

pkill picom

Now lock the screen. Same thing?

hhh · 2025-12-19 02:57:26

Fresh install, packages upgraded, OOTB lock-screen issue confirmed...

-edit- pkill picom solves it, I think. It's a picom issue we need to troubleshoot (a transparency exception rule for light-locker, probably).

hhh · 2025-12-19 03:01:20

Please, let's use this synclient entry this time so right-click/3-finger click on touchpads is enabled ny default...

synclient VertEdgeScroll=0 VertTwoFingerScroll=1 HorizEdgeScroll=0 TapButton1=1 TapButton2=3 TapButton3=2 PalmDetect=1 PalmMinWidth=4 PalmMinZ=100

I think that's it, one minute for me to confirm...

-edit- That's right, I think.

Last edited by hhh (2025-12-19 03:04:58)

johnraff · 2025-12-19 03:08:30

hhh wrote:

Fresh install, packages upgraded, OOTB lock-screen issue confirmed...
https://thumbs2.imgbox.com/62/1e/LEKa4hqP_t.png

I can see it too.

Not a happy discovery, this. There's no such problem on Boron.

We need to look over the various lock-screen options and see where it's coming from.
Previous discussion: https://forums.bunsenlabs.org/viewtopic.php?id=9515

At worst, we might have to implement a different screen locking utility...

hhh · 2025-12-19 03:09:46

See my edit from my scrot post above re: picom/light-locker.

hhh · 2025-12-19 03:27:48

OK, I didn't realize picom had a major overhaul. The boron conf is working for me, no transparency on the lock screen.

boron: https://raw.githubusercontent.com/Bunse … picom.conf

carbon: https://raw.githubusercontent.com/Bunse … picom.conf

hhh · 2025-12-19 03:29:57

^ Quck glance, define active and inactive opacity in the new conf, at least.

hhh · 2025-12-19 03:36:08

Spamming, sorry. Active and inactive opacity both default to one, so that's no help. @dave, can you confirm that killing picom "solves" the issue?

boron picom.conf "works" because it's not starting.

carbon@ghost:~$ picom
[ 12/18/25 22:44:10.700 c2_parse_target WARN ] Type specifier is deprecated. Type "c" specified on target "_GTK_FRAME_EXTENTS" will be ignored, you can remove it.
[ 12/18/25 22:44:10.700 c2_parse_target WARN ] Type specifier is deprecated. Type "a" specified on target "_NET_WM_STATE" will be ignored, you can remove it.
[ 12/18/25 22:44:10.700 c2_parse_target WARN ] Format specifier is deprecated. Format "32" specified on target "_NET_WM_STATE" will be ignored, you can remove it.
[ 12/18/25 22:44:10.700 c2_parse_target WARN ] Type specifier is deprecated. Type "a" specified on target "_NET_WM_STATE" will be ignored, you can remove it.
[ 12/18/25 22:44:10.700 c2_parse_target WARN ] Format specifier is deprecated. Format "32" specified on target "_NET_WM_STATE" will be ignored, you can remove it.
[ 12/18/25 22:44:10.700 c2_parse_target WARN ] Type specifier is deprecated. Type "c" specified on target "_GTK_FRAME_EXTENTS" will be ignored, you can remove it.
[ 12/18/25 22:44:10.700 c2_parse_target WARN ] Type specifier is deprecated. Type "c" specified on target "_GTK_FRAME_EXTENTS" will be ignored, you can remove it.
[ 12/18/25 22:44:10.700 c2_parse_target WARN ] Type specifier is deprecated. Type "a" specified on target "_NET_WM_STATE" will be ignored, you can remove it.
[ 12/18/25 22:44:10.700 c2_parse_target WARN ] Format specifier is deprecated. Format "32" specified on target "_NET_WM_STATE" will be ignored, you can remove it.
[ 12/18/25 22:44:10.700 sanitize_options ERROR ] Backend not specified. You must choose one explicitly. Valid ones are: 
[ 12/18/25 22:44:10.700 sanitize_options ERROR ] 	dummy
[ 12/18/25 22:44:10.700 sanitize_options ERROR ] 	xrender
[ 12/18/25 22:44:10.700 sanitize_options ERROR ] 	egl
[ 12/18/25 22:44:10.700 sanitize_options ERROR ] 	glx
[ 12/18/25 22:44:10.700 session_init FATAL ERROR ] Failed to get configuration, usually mean you have specified invalid options.
[ 12/18/25 22:44:10.700 main FATAL ERROR ] Failed to create new session.

Last edited by hhh (2025-12-19 03:43:57)

johnraff · 2025-12-19 04:23:21

hhh wrote:

Make sure it's not a picom issue...
pkill picom
Now lock the screen. Same thing?

Yup, seems to be picom. Disable it from the menu before locking and no transparent desktop visible.

EDIT missed all @hhh's recent stuff before posting this.

hhh wrote:

-edit- pkill picom solves it, I think. It's a picom issue we need to troubleshoot (a transparency exception rule for light-locker, probably).

Last edited by johnraff (2025-12-19 04:26:58)

johnraff · 2025-12-19 05:31:44

hhh wrote:

OK, I didn't realize picom had a major overhaul.

Big changes between Bookworm and Trixie. Old picom.conf now breaks compositing. I did a complete makeover a while ago:
https://forums.bunsenlabs.org/viewtopic.php?id=9340
https://forums.bunsenlabs.org/viewtopic … 18#p142118

Last edited by johnraff (2025-12-19 06:19:08)

johnraff · 2025-12-19 05:33:56

hhh wrote:

boron picom.conf "works" because it's not starting.

Boron picom.conf works fine on Boron but breaks on Trixie because picom has changed.

johnraff · 2025-12-19 05:44:59

This is where the lockscreen transparency is coming from: lines 344 345 in Boron's picom.conf:

  match = "!focused || !group_focused";
  opacity = 0.96;

Change that opacity to 1:00 and it's gone.
So we have to find the right selector to set opacity on LightDM's lockscreen, or if that fails, just give up on the faintly transparent unfocused windows.

johnraff · 2025-12-19 06:28:10

Try adding this to picom.conf, maybe just under the section that sets 0.96 opacity for unfocused windows:

}, {
  match = "class_g *?= 'screensaver'";
  opacity = 1.0;
}, {

It seems to fix the issue for me.
(The screenlocker window is xfce4-screensaver, not LightdM.)

johnraff · 2025-12-19 06:39:25

hhh wrote:

Please, let's use this synclient entry this time so right-click/3-finger click on touchpads is enabled ny default...
synclient VertEdgeScroll=0 VertTwoFingerScroll=1 HorizEdgeScroll=0 TapButton1=1 TapButton2=3 TapButton3=2 PalmDetect=1 PalmMinWidth=4 PalmMinZ=100

What we have right now is:

synclient VertEdgeScroll=1 HorizEdgeScroll=1 VertTwoFingerScroll=1 TapButton1=1

and this alternative, commented-out:

#synclient VertEdgeScroll=0 VertTwoFingerScroll=0 HorizEdgeScroll=0 TapButton1=1 TapButton2=3 TapButton3=2 PalmDetect=1 PalmMinWidth=4 PalmMinZ=100

which is what you're suggesting for default, except for enabling VertTwoFingerScroll right?

I'm OK with any of those because I seldom use a touchpad, with the only principle of setting by default what's least likely to confuse and upset new users.

@hhh your decision, unless anyone jumps in to disagree.

Dave75 · 2025-12-19 16:30:02

hhh wrote:

@dave, can you confirm that killing picom "solves" the issue?

Yes, it solves.

I apologize for not being responsive and proactive on this issue, but in the last two days I had not time to connect.

Dave75 · 2025-12-19 16:38:03

johnraff wrote:

Try adding this to picom.conf, maybe just under the section that sets 0.96 opacity for unfocused windows:
}, {
  match = "class_g *?= 'screensaver'";
  opacity = 1.0;
}, {
It seems to fix the issue for me.
(The screenlocker window is xfce4-screensaver, not LightdM.)

It works for me as well. I'm not sure which screenlocker I have, I don't know how to check it. Anyway I haven't changed anything about screenlocker with respect to the installed system.

Thanks!

johnraff · 2025-12-20 00:43:14

@Dave75 thanks for confirming the fix worked.
I'll add those lines to picom.conf in the next upgrade of bunsen-configs.

hhh · 2025-12-20 01:03:54

johnraff wrote:

hhh wrote:
Please, let's use this synclient entry this time so right-click/3-finger click on touchpads is enabled ny default...
synclient VertEdgeScroll=0 VertTwoFingerScroll=1 HorizEdgeScroll=0 TapButton1=1 TapButton2=3 TapButton3=2 PalmDetect=1 PalmMinWidth=4 PalmMinZ=100
What we have right now is:
synclient VertEdgeScroll=1 HorizEdgeScroll=1 VertTwoFingerScroll=1 TapButton1=1
and this alternative, commented-out:
#synclient VertEdgeScroll=0 VertTwoFingerScroll=0 HorizEdgeScroll=0 TapButton1=1 TapButton2=3 TapButton3=2 PalmDetect=1 PalmMinWidth=4 PalmMinZ=100
which is what you're suggesting for default, except for enabling VertTwoFingerScroll right?
I'm OK with any of those because I seldom use a touchpad, with the only principle of setting by default what's least likely to confuse and upset new users.
@hhh your decision, unless anyone jumps in to disagree.

I'm trying to enable two finger-click (context-menu window) and three finger-click tapping (open a browser link in a new tab) on touchpads (touchpad scrolling is a bonus). I'm on Wayland these days, where it seems to work OOTB on my hardware, so do what you think is right.

johnraff · 2025-12-20 03:16:23

^I don't consider myself qualified to call this one.

If you're reasonably confident your suggested config won't trouble anyone (or many people anyway) then let's apply it.

Can you also suggest a totally vanilla alternative to put in, commented out?

hhh · 2025-12-20 03:58:21

Vanilla - The original line would be fine. Nobody but me has complained so far, as far as I know.

#41 2025-12-18 17:13:46

Re: Carbon TODO

#42 2025-12-19 02:57:26

Re: Carbon TODO

#43 2025-12-19 03:01:20

Re: Carbon TODO

#44 2025-12-19 03:08:30

Re: Carbon TODO

#45 2025-12-19 03:09:46

Re: Carbon TODO

#46 2025-12-19 03:27:48

Re: Carbon TODO

#47 2025-12-19 03:29:57

Re: Carbon TODO

#48 2025-12-19 03:36:08

Re: Carbon TODO

#49 2025-12-19 04:23:21

Re: Carbon TODO

#50 2025-12-19 05:31:44

Re: Carbon TODO

#51 2025-12-19 05:33:56

Re: Carbon TODO

#52 2025-12-19 05:44:59

Re: Carbon TODO

#53 2025-12-19 06:28:10

Re: Carbon TODO

#54 2025-12-19 06:39:25

Re: Carbon TODO

#55 2025-12-19 16:30:02

Re: Carbon TODO

#56 2025-12-19 16:38:03

Re: Carbon TODO

#57 2025-12-20 00:43:14

Re: Carbon TODO

#58 2025-12-20 01:03:54

Re: Carbon TODO

#59 2025-12-20 03:16:23

Re: Carbon TODO

#60 2025-12-20 03:58:21

Re: Carbon TODO

Board footer