View previous topic :: View next topic |
Author |
Message |
Buffoon Veteran
Joined: 17 Jun 2015 Posts: 1369 Location: EU or US
|
Posted: Tue Dec 29, 2020 4:57 pm Post subject: Xorg and compositing |
|
|
Hello forums
I cannot get compositing to work. This is not important, really, but I'm curious.
I never cared about eyecandy and my setup is very basic. Using no-multilib profile. I added USE flags as necessary when I installed Xorg, but there certainly are some flags turned off compared to desktop profile.
Since nowadays Chromium misbehaves without compositing manager I decided to install one. This is where the problem started. First I tried xcompmgr. This resulted in a chaotic desktop, all open windows disappeared and started flashing, appearing/disappearing randomly. No error message. No errors in logs. Then I tried picom, it runs and Chromium is happy with it. However, I thought since I have it then why not transparency. I am unable to get any effects working, may it be some component of Xorg is not playing along?
My Xorg log: https://dpaste.com/E9XPCLQL7
Where should I look to find out why xcompmgr goes berserk and picom does nothing? |
|
Back to top |
|
|
The Main Man Veteran
Joined: 27 Nov 2014 Posts: 1171 Location: /run/user/1000
|
Posted: Wed Dec 30, 2020 12:02 am Post subject: |
|
|
I faced the same problem with no-multilib, problem is in the X use flag which that profile unsets globally, so you can set that flag globally and update the @world
At least I think that's the problem in your case, anyway you can find my recent question about that here :
https://forums.gentoo.org/viewtopic-t-1124551-postdays-0-postorder-asc-start-0.html
Yeah reading that now... with picom it was actually opengl use flag |
|
Back to top |
|
|
Buffoon Veteran
Joined: 17 Jun 2015 Posts: 1369 Location: EU or US
|
Posted: Wed Dec 30, 2020 12:29 am Post subject: |
|
|
Thanks for looking into this. I had opengl and X already enabled in package.use for most packages which have these, enabling both globally did not change anything, no package required rebuild. Here is my glxinfo, just in case: https://dpaste.com/3BHP6YPF3
I do not see any verbosity options for picom, it has debug mode, though. Not sure if that helps with my problem. Unfortunately X has never been my cup of tea ... |
|
Back to top |
|
|
The Main Man Veteran
Joined: 27 Nov 2014 Posts: 1171 Location: /run/user/1000
|
Posted: Wed Dec 30, 2020 10:22 am Post subject: |
|
|
Well, don't know then what could be the problem.
I figured what was the problem in my case in the log file, I still have that error message when I look at the log file, it was this :
Code: | [ 12/02/2020 15:01:47.974 init_render ERROR ] GLX backend support not compiled in.
[ 12/02/2020 15:01:47.974 session_init FATAL ERROR ] Failed to initialize the backend |
Maybe you can see something useful in yours, here's my config file
Code: | log-level = "warn";
log-file = "~/picom.log"
vsync = true
refresh-rate = 60;
backend = "glx"
use-damage = true;
fading = false
shadow = false
opacity-rule = [
"95:class_g = 'st-256color' "
]; |
|
|
Back to top |
|
|
Buffoon Veteran
Joined: 17 Jun 2015 Posts: 1369 Location: EU or US
|
Posted: Wed Dec 30, 2020 10:48 am Post subject: |
|
|
Thank you! Knowing this works for you like this is really helpful. |
|
Back to top |
|
|
The Main Man Veteran
Joined: 27 Nov 2014 Posts: 1171 Location: /run/user/1000
|
Posted: Wed Dec 30, 2020 12:09 pm Post subject: |
|
|
I said that because you didn't mention picom.log and is there something useful in it, in my case that info helped.
Also, the config posted was so that you can see how to enable the log file and more importantly transparency, in case you don't know (I don't know if you do)
Are you using the same config for picom that you used in desktop profile ?
If yes and transparency was working there and it doesn't now in no-multilib, then you're missing some of the use flags.
I'm sorry I can't help you directly on the first try and solve your problem right away, I tried to help ... good luck! |
|
Back to top |
|
|
Buffoon Veteran
Joined: 17 Jun 2015 Posts: 1369 Location: EU or US
|
Posted: Wed Dec 30, 2020 12:37 pm Post subject: |
|
|
I didn't know picom can log! I tried to read the man page - which does not exist in my system and then I was looking at picom -h output, read Arch wiki, and some other places. None of them mentioned logging. Now I realize picom is not reading conf file, I put it in ~.config/picom.conf - which is supposed to be a valid location. I started picom with a bunch of command line options in attempt to enable transparency, and there was no transparency. BTW, I've never used desktop profile. This install was plain multilib once, I guess for Adobe flash perhaps which was 32-bit only back then, then I converted it to no-multilib many years ago.
Here is my mesa
Code: | [ebuild R ] media-libs/mesa-20.3.1::gentoo USE="X classic dri3 egl gallium gbm vaapi vulkan xa zstd -d3d9 -debug -gles1 -gles2 -llvm -lm-sensors -opencl -osmesa (-selinux) -test -unwind -valgrind -vdpau -vulkan-overlay -wayland -xvmc -zink" VIDEO_CARDS="i965 intel iris (-freedreno) -i915 (-lima) -nouveau (-panfrost) -r100 -r200 -r300 -r600 -radeon -radeonsi (-v3d) (-vc4) -virgl (-vivante) -vmware" 0 KiB
|
and xorg-server
Code: | [ebuild R ] x11-base/xorg-server-1.20.10:0/1.20.10::gentoo USE="ipv6 suid udev xorg xvfb -debug -dmx -doc -elogind -kdrive -libressl -minimal (-selinux) -static-libs -systemd -unwind -wayland -xcsecurity -xephyr -xnest" 0 KiB
|
|
|
Back to top |
|
|
The Main Man Veteran
Joined: 27 Nov 2014 Posts: 1171 Location: /run/user/1000
|
Posted: Wed Dec 30, 2020 1:42 pm Post subject: |
|
|
Location of the config file is good, I believe your problem is in that config file.
The rest doesn't matter (USE flags etc.), picom is working in your case, but as far as I know transparency is working only if you specify for which windows you want transparency.
Like I did for my terminal only
Code: | opacity-rule = [
"95:class_g = 'st-256color' "
]; |
you can run xprop command from the terminal and then click on the window you want to be transparent, you will get some info and what you're looking for is
Code: | WM_CLASS(STRING) = "st-256color", "st-256color" |
In this case I got st-256color but you will get something else and then you need to put that in the opacity rule within ~/.config/picom.conf
btw I start picom only with 'picom -b' , everything else is in the config file
Maybe you could do transparency from the options in the command line but I'm not sure |
|
Back to top |
|
|
Buffoon Veteran
Joined: 17 Jun 2015 Posts: 1369 Location: EU or US
|
|
Back to top |
|
|
|