[Desktop-packages] [Bug 2084841] Re: gsd-power segfault

2024-10-20 Thread Daniel van Vugt
*** This bug is a duplicate of bug 2085060 *** https://bugs.launchpad.net/bugs/2085060 For system components like that you might have to use 'sudo apport-cli' or 'sudo ubuntu-bug'. If the upload succeeds then there should be an '.uploaded' file created with the upload ID we can use. One of yo

[Desktop-packages] [Bug 2084841] Re: gsd-power segfault

2024-10-18 Thread Luis Alvarado
I did the apport-cli and it said it worked but went to the errors https://errors.ubuntu.com/user/ID page and it did not show them. I have attatched both here in a zip. Also when doing them I got this: luis@xtreme:/var/crash$ apport-cli _usr_libexec_gsd-power.1000.crash *** Send problem report

[Desktop-packages] [Bug 2084841] Re: gsd-power segfault

2024-10-17 Thread Daniel van Vugt
1. The command you want already exists: apport-collect 2084841 2. Yes we can and do automate collection of some information. But it's a different script per package. If a person reports a bug against the wrong package then they've automatically got irrelevant or insufficient automatic attachments

[Desktop-packages] [Bug 2084841] Re: gsd-power segfault

2024-10-17 Thread Luis Alvarado
May I ask, one thing I have tried previously to do without luck is the following: 1. If a user comes directly to launchpad or creates a bug using ubuntu- bug, how can they, later in the future, add via ubuntu-bug, attachments or other information to that previous bug. So for example, this bug ID

[Desktop-packages] [Bug 2084841] Re: gsd-power segfault

2024-10-17 Thread Luis Alvarado
Hi Daniel, first let me say I just learned A LOT from your steps here. Like A LOT, I was unaware of the errors.ubuntu.com page which frankly left me speechless because of how awesome it is. Anyway, after recovering from the awesomeness, here is the Journal file. The crash files are this ones in the

[Desktop-packages] [Bug 2084841] Re: gsd-power segfault

2024-10-17 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt an