gsd-power segfault

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
and attach the resulting text files here.

2. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

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 crash folder:

_usr_bin_gnome-shell.1000.crash

_usr_bin_nautilus.1000.crash

_usr_libexec_gsd-power.1000.crash

_usr_libexec_gsd-power.120.crash

But if I run ubuntu-bug against any of them I get this:

https://imgur.com/a/X3HZiC8

For the errors.ubuntu.com user ID, the last recorded error was on 24.04 on June because after that 24.04 ran perfectly. 0% errors.

For the Journal file, I did 4 files so you can see all crashes if they logged in there for the past 4 boot ups since it happens on all of them.

I can send the huge CRASH files if you like in a ZIP file somewhere else.

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 is 2084841, how can I later, assuming I missed critical information, add those files to it via ubuntu-bug or a gui based tool for ubuntu that addresses an easy to collaborate with an existing bug report. Something like ubuntu-bug gnome-shell 2084841 (Just brainstorming an idea) to which the ubuntu-bug would know the issue is about gnome-shell and would gather the needed stuff for it, and then proceed to add those to the 2084841 bug report.

2. Every time someone tries to create a bug report on launchpad, your steps provided, plus the ones mentioned in other bugs like https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2084569 I feel are super critical, since it is rare to be able to create bug reports every day, so very little will users remember what step by step to follow when creating a bug report apart from the initial simple questions.

But since specific attachments are required, I feel this would save the user time and the developer time in order to be there as a step by step to easily follow.

There are other intuitive questions that I normally ask my clients that could be included in the bug reporting flow for new users, but those 2 I feel are the big ones for now.

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. I guess ubuntu-bug/apport-collect also has a minimum set of attachments for all packages, I've just never been bold enough to consider what we should be changing for ALL bug reports.

Back on the main crash here, the files of most interest are:

  _usr_libexec_gsd-power.1000.crash
  _usr_libexec_gsd-power.120.crash

but we usually can't process them ourselves. If uploading with ubuntu-bug fails then try 'apport-cli' instead. If apport-cli also fails and https://errors.ubuntu.com/user/$ID is also not showing anything recent, then the last resort would be to attach or link to the crash file here.

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 to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (2.1 MB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): s

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.REDACTED config part /etc/cloud/cloud.cfg.d/99-installer.cfg, insufficient permissions
REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg, insufficient permissions
...../usr/share/apport/package-hooks/source_gnome-settings-daemon.py:15: SyntaxWarning: invalid escape sequence '\w'
  component = re.compile("lib(\w*).so").search(words).groups(1)[0]
.......
luis@xtreme:/var/crash$ apport-cli _usr_libexec_gsd-power.120.crash

*** Error: Invalid problem report

Permission denied

Press any key to continue...

luis@xtreme:/var/crash$ apport-cli _usr_libexec_gsd-power.120.crash

*** Error: Invalid problem report

Permission denied

Press any key to continue...

Like permission issues with it. If that helps.

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 your crash files seems to have almost enough information:

Thread 1 (Thread 0x70d7ef41aac0 (LWP 4055)):
#0 0x000070d7f04b3395 in __GI___libc_free (mem=0x11ec47d490) at ./malloc/malloc.c:3375
        ar_ptr = <optimized out>
        p = <optimized out>
        err = <optimized out>
#1 0x000070d7f06c204c in g_hash_table_unref () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x000070d7f095003f in ??? () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
#3 0x000070d7f06c0ca9 in g_hash_table_remove () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x000070d7f09510cf in g_dbus_interface_info_cache_release () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
#5 0x000070d7f0949eac in ??? () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
#6 0x000070d7f07e9922 in g_object_unref () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0

which also seems to match the most common gnome-settings-daemon crash being reported. Bug 2085060 has been opened to track that.