You are not logged in.

#1 2022-11-23 07:10:44

bgdawes
Member
Registered: 2017-02-01
Posts: 7

[SOLVED] Picom crashes after upgrading to linux version 6.0.9.arch1-1

Hello - I've been using picom without any issues for a long time now and it's recently been crashing right after I updated linux to version 6.0.9.arch1-1. My picom config file has 'glx' set as the backend. I have integrated graphics handled by my Intel CPU (Intel Corporation HD Graphics 530 (rev 06)).

I noticed that the mesa package in the Extra repository (version 22.2.3-1) is flagged as out of date. I'm hoping that there is an outside chance that once the mesa package is updated picom won't crash anymore but I also think I could have been coasting along so far by pure luck and there might be some config setup I haven't established properly (which is highly likely).

I checked picom's core dump and the signal is 11 (SEGV). I'd definitely appreciate any thoughts about what I expect is my own user error.

Last edited by bgdawes (2022-11-23 17:01:52)


"The problem with the world is that the intelligent people are full of doubts, while the stupid ones are full of confidence."
- Charles Bukowski

Offline

#2 2022-11-23 08:15:01

seth
Member
Registered: 2012-09-03
Posts: 33,685

Re: [SOLVED] Picom crashes after upgrading to linux version 6.0.9.arch1-1

the signal is 11 (SEGV)

The backtrace would be more insightful.

Offline

#3 2022-11-23 13:47:59

CarbonChauvinist
Member
Registered: 2012-06-16
Posts: 409
Website

Re: [SOLVED] Picom crashes after upgrading to linux version 6.0.9.arch1-1


"the wind-blown way, wanna win? don't play"

Offline

#4 2022-11-23 14:21:46

seth
Member
Registered: 2012-09-03
Posts: 33,685

Re: [SOLVED] Picom crashes after upgrading to linux version 6.0.9.arch1-1

That's why a backtrace would be super-insightful wink

Offline

#5 2022-11-23 16:35:30

bgdawes
Member
Registered: 2017-02-01
Posts: 7

Re: [SOLVED] Picom crashes after upgrading to linux version 6.0.9.arch1-1

Thanks for replying seth! Apologies, I should have included a backtrace in my original post. Sadly, I'm no where near smart enough to understand what any of this means, however, I'll do some googleling. Please let me know if there is anything that might be jumping out at you based on the bt pasted below or if there is any other debugging investigation I should try.

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `picom -b'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000558a2e19599c in ?? ()
[Current thread is 1 (Thread 0x7fe2cbc61ec0 (LWP 718))]
(gdb) bt
#0  0x0000558a2e19599c in ?? ()
#1  0x0000558a2e18bff7 in ?? ()
#2  0x0000558a2e169198 in ?? ()
#3  0x0000558a2e19c52f in ?? ()
#4  0x0000558a2e164b6c in ?? ()
#5  0x00007fe2cc6d40cb in ev_invoke_pending () from /usr/lib/libev.so.4
#6  0x00007fe2cc6d7d10 in ev_run () from /usr/lib/libev.so.4
#7  0x0000558a2e16246e in ?? ()
#8  0x00007fe2cc0db290 in ?? () from /usr/lib/libc.so.6
#9  0x00007fe2cc0db34a in __libc_start_main () from /usr/lib/libc.so.6
#10 0x0000558a2e163845 in ?? ()

"The problem with the world is that the intelligent people are full of doubts, while the stupid ones are full of confidence."
- Charles Bukowski

Offline

#6 2022-11-23 17:00:02

bgdawes
Member
Registered: 2017-02-01
Posts: 7

Re: [SOLVED] Picom crashes after upgrading to linux version 6.0.9.arch1-1

Update - I just noticed that the picom package was updated yesterday (11/22). I just installed the update and picom is running along smoothly now just like always. Thanks again for the help!


"The problem with the world is that the intelligent people are full of doubts, while the stupid ones are full of confidence."
- Charles Bukowski

Offline

#7 2022-11-23 17:02:29

seth
Member
Registered: 2012-09-03
Posts: 33,685

Re: [SOLVED] Picom crashes after upgrading to linux version 6.0.9.arch1-1

It segfaults out of some private function, /usr/lib/libev.so.4 is from https://archlinux.org/packages/community/x86_64/libev/ (generic event loop framework)
The backtrace is therefore indeed not all that helpful (other than we know what is not the problem)

Make sure the system is fully updated (pacman -Syu) and move your ~/.config/picom.conf away to see whether some custom setting triggers this.
Then, on a wild guess, post the output "glxinfo -B" and also your xorg log (resp. "pacman -Qs xf86-video")

Offline

Board footer

Powered by FluxBB