lubuntu mantic install; picom crashed too many times at login

Bug #2032909 reported by Chris Guiver
10
This bug affects 1 person
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/7350/8350)
testcase: install using existing partition

this maybe related to https://bugs.launchpad.net/ubuntu/+source/picom/+bug/2018620

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
ExecutableTimestamp: 1679233319
ProcCmdline: /usr/bin/picom
ProcCwd: /home/guiverc
Signal: 6
SourcePackage: picom
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Chris Guiver (guiverc) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __assert_fail_base (fmt=0x7f5a1b9b9f68 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x5581de61c013 "false", file=file@entry=0x5581de61c004 "../src/picom.c", line=line@entry=425, function=function@entry=0x5581de61de00 <__PRETTY_FUNCTION__.24> "destroy_backend") at ./assert/assert.c:92
 __assert_fail (assertion=assertion@entry=0x5581de61c013 "false", file=file@entry=0x5581de61c004 "../src/picom.c", line=line@entry=425, function=function@entry=0x5581de61de00 <__PRETTY_FUNCTION__.24> "destroy_backend") at ./assert/assert.c:101
 destroy_backend (ps=ps@entry=0x5581df645d00) at ../src/picom.c:425
 configure_root (ps=0x5581df645d00) at ../src/picom.c:602
 handle_root_flags (ps=0x5581df645d00) at ../src/picom.c:665

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in picom (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Chris Guiver (guiverc)
description: updated
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2032909

tags: added: iso-testing
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.