lubuntu mantic install; picom crashed too many times at login
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| picom (Ubuntu) |
New
|
Medium
|
Unassigned | ||
Bug Description
lubuntu mantic re-install on
- dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/
testcase: install using existing partition
this maybe related to https:/
I'm seeing this still on my my primary box, plus on some INSTALL USING EXISTING PARTITION installs... where the HOME DIRECTORY is RE-USED... could a setting remain on re-install that causes this issue?
** Expected result
on fresh install; no first pop-up telling me something has crashed too many times
** Actual result
on login, wallpaper is drawn then a pop-up reporting PICOM HAS CRASHED TOO MANY TIMES
ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: picom 10.2-1
Uname: Linux 6.3.0-7-generic x86_64
Architecture: amd64
CurrentDesktop: LXQt
Date: Thu Aug 24 18:50:52 2023
ExecutablePath: /usr/bin/picom
ExecutableTimes
ProcCmdline: /usr/bin/picom
ProcCwd: /home/guiverc
Signal: 6
SourcePackage: picom
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
| Chris Guiver (guiverc) wrote | #1 |
| information type: | Private → Public |
| Apport retracing service (apport) wrote | #2 |
| Apport retracing service (apport) wrote Stacktrace.txt | #3 |
| Apport retracing service (apport) wrote StacktraceSource.txt | #4 |
| Apport retracing service (apport) wrote ThreadStacktrace.txt | #5 |
| Changed in picom (Ubuntu): | |
| importance: | Undecided → Medium |
| tags: | removed: need-amd64-retrace |
| description: | updated |
StacktraceTop:
__assert_fail_base (fmt=0x7f5a1b9b9f68 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=
__assert_fail (assertion=
destroy_backend (ps=ps@
configure_root (ps=0x5581df645d00) at ../src/picom.c:602
handle_root_flags (ps=0x5581df645d00) at ../src/picom.c:665