Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#66675 - [picom] Segmentation fault on startup

Attached to Project: Community Packages
Opened by Harish Rajagopal (rharish) - Saturday, 16 May 2020, 11:19 GMT
Last edited by Alexander F. Rødseth (xyproto) - Monday, 07 September 2020, 18:35 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Alexander F. Rødseth (xyproto)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Picom crashes with a segmentation fault on startup.

Additional info:
* picom version: 8-2
* logs: attached

Steps to reproduce:
* Launch picom with default configuration
* It should crash with a segfault
   logs.txt (49.6 KiB)
This task depends upon

Closed by  Alexander F. Rødseth (xyproto)
Monday, 07 September 2020, 18:35 GMT
Reason for closing:  Upstream
Comment by Harish Rajagopal (rharish) - Saturday, 16 May 2020, 11:20 GMT
BTW, I am using i3-gaps (version 4.18.1-1) as my WM.
Comment by freswa (frederik) - Saturday, 16 May 2020, 14:30 GMT
I can't find a segmentation fault in the logs. Could you please provide the error message?
Comment by Harish Rajagopal (rharish) - Saturday, 16 May 2020, 14:56 GMT
The segfault is printed to the terminal. I can't redirect it to a log file. It's just one line, so here's the message printed to my shell (zsh):
```
[1] 10140 segmentation fault (core dumped) picom --log-level TRACE &> ~/logs.txt
```
Comment by freswa (frederik) - Saturday, 16 May 2020, 15:14 GMT
I don't think this is a packaging issue. Please report this issue upstream. Thank you :)

Loading...