fwupd crashed with SIGSEGV in g_str_hash()

Bug #1698675 reported by David
52
This bug affects 10 people
Affects Status Importance Assigned to Milestone
fwupd (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I installed Ubuntu starting at version 13.10 and slowly upgraded to 17.10 on a Intel based quad-core Lenovo ThinkServer. This started happening as soon as I reached around version 16.10.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: fwupd 0.9.2-5
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic i686
ApportVersion: 2.20.5-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Sat Jun 17 14:13:47 2017
ExecutablePath: /usr/lib/fwupd/fwupd
InstallationDate: Installed on 2017-06-17 (1 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
ProcCmdline: /usr/lib/fwupd/fwupd
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0xb7542eda <g_str_hash+10>: movsbl (%ebx),%edx
 PC (0xb7542eda) ok
 source "(%ebx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: fwupd
StacktraceTop:
 g_str_hash () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/fwupd-plugins-2/libfu_plugin_unifying.so
 lu_context_coldplug () from /usr/lib/i386-linux-gnu/fwupd-plugins-2/libfu_plugin_unifying.so
 fu_plugin_startup () from /usr/lib/i386-linux-gnu/fwupd-plugins-2/libfu_plugin_unifying.so
Title: fwupd crashed with SIGSEGV in g_str_hash()
UpgradeStatus: Upgraded to artful on 2017-06-17 (0 days ago)
UserGroups:

Revision history for this message
David (david-hotle) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_str_hash (v=0x0) at ../../../../glib/ghash.c:1878
 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x0, hash_table=0x9561420) at ../../../../glib/ghash.c:375
 g_hash_table_insert_internal (hash_table=0x9561420, key=0x0, value=0x9efdb38, keep_new_key=0) at ../../../../glib/ghash.c:1229
 lu_context_add_udev_device (ctx=ctx@entry=0x9070230, udev_device=udev_device@entry=0xa71d5a0) at ../../plugins/unifying/lu-context.c:284
 lu_context_coldplug (ctx=0x9070230) at ../../plugins/unifying/lu-context.c:491

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 fwupd (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in fwupd (Ubuntu):
status: New → Confirmed
information type: Private → Public
Revision history for this message
Richard Hughes (richard-hughes) wrote :

Does running valgrind as root on the fwupd process trigger any invalid reads or other warnings?

Revision history for this message
David (david-hotle) wrote : Re: [Bug 1698675] Re: fwupd crashed with SIGSEGV in g_str_hash()

I don't remember...I reinstalled things using the MAC compliant version of
Ubuntu (even though I installed it on a Lenovo ThinkServer) starting at
around version 13 and it works. Lenovo ThinkServers have really weird
issues with newer versions of Ubuntu -- you can't install the standard 64
bit versions on them.

On Tue, Apr 10, 2018 at 7:10 AM, Richard Hughes <email address hidden> wrote:

> Does running valgrind as root on the fwupd process trigger any invalid
> reads or other warnings?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1698675
>
> Title:
> fwupd crashed with SIGSEGV in g_str_hash()
>
> Status in fwupd package in Ubuntu:
> Confirmed
>
> Bug description:
> I installed Ubuntu starting at version 13.10 and slowly upgraded to
> 17.10 on a Intel based quad-core Lenovo ThinkServer. This started
> happening as soon as I reached around version 16.10.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 17.10
> Package: fwupd 0.9.2-5
> ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
> Uname: Linux 4.10.0-22-generic i686
> ApportVersion: 2.20.5-0ubuntu4
> Architecture: i386
> CrashCounter: 1
> Date: Sat Jun 17 14:13:47 2017
> ExecutablePath: /usr/lib/fwupd/fwupd
> InstallationDate: Installed on 2017-06-17 (1 days ago)
> InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386
> (20131016.1)
> ProcCmdline: /usr/lib/fwupd/fwupd
> ProcEnviron:
> LANG=en_US.UTF-8
> PATH=(custom, no user)
> SegvAnalysis:
> Segfault happened at: 0xb7542eda <g_str_hash+10>: movsbl (%ebx),%edx
> PC (0xb7542eda) ok
> source "(%ebx)" (0x00000000) not located in a known VMA region (needed
> readable region)!
> destination "%edx" ok
> SegvReason: reading NULL VMA
> Signal: 11
> SourcePackage: fwupd
> StacktraceTop:
> g_str_hash () from /lib/i386-linux-gnu/libglib-2.0.so.0
> ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
> ?? () from /usr/lib/i386-linux-gnu/fwupd-plugins-2/libfu_plugin_
> unifying.so
> lu_context_coldplug () from /usr/lib/i386-linux-gnu/fwupd-
> plugins-2/libfu_plugin_unifying.so
> fu_plugin_startup () from /usr/lib/i386-linux-gnu/fwupd-
> plugins-2/libfu_plugin_unifying.so
> Title: fwupd crashed with SIGSEGV in g_str_hash()
> UpgradeStatus: Upgraded to artful on 2017-06-17 (0 days ago)
> UserGroups:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/
> 1698675/+subscriptions
>

Revision history for this message
Mario Limonciello (superm1) wrote :

Given it can't be reproduced anymore, I'm going to mark this one invalid.

If you do happen to reproduce this issue, please re-open or open a new bug with the following:
1) test with 1.0.x or 1.1.x versions (either packaged or from a snap are fine)
2) Test if running the daemon under valgrind triggers anything interesting (share the output).

Changed in fwupd (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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