OK, then unfortunately nothing we can do. Please if this crops up again
1: If you attach gdb, then dump a core file
or
2: install debug symbols, attach gdb, and attach a backtrace.
** Changed in: fwupd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are
No crash file in /var/crash, unfortunately.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900107
Title:
fwupd is eating 100% CPU for 30 minutes
To manage notifications about this bug go to:
https:
I don't think it does. If you manage to repro again please either core
dump or install the symbols before back tracing. But I'm afraid it's a
shot in the dark until we know more or can repro.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Definitely no custom stuff in /usr/local. This was a fresh install of
20.04 in a loaner laptop while mine was getting its keyboard repaired.
I'll have to boot it up and check /var/crash on Monday. I killed the
misbehaving process with `kill` at the gdb prompt, IIRC. I don't know
what signal it
Do you have a crash dump by chance? There are debug symbols available
and they would as you say be immensely helpful. If you can send the
crash with apport it will fetch nad process them automatically. If you
can't send it via apport, here they are and you can install locally:
https://launchpad
And just to confirm - you don't happen to have a bunch of libraries or
other stuff in /usr/local that might be getting used? Those assertions
seem quite unusual.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
So, apport didn't attach the journal, therefore
spal. 16 09:09:34 bigas systemd[1]: Finished Refresh fwupd metadata and update
motd.
...
spal. 16 10:55:37 bigas fwupd[86826]: 07:55:37:0051 GLib-GObject
invalid uninstantiatable type 'GParamInt64' in cast to 'FwupdDevice'
spal. 16 10:55:37
gdb is useless without debug symbols:
__pthread_rwlock_wrlock_full (abstime=0x0, clockid=0, rwlock=0x55af956f1a60) at
pthread_rwlock_common.c:720
720 pthread_rwlock_common.c: No such file or directory.
(gdb) bt
#0 __pthread_rwlock_wrlock_full (abstime=0x0, clockid=0,
rwlock=0x55af956f1a60)
