gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()

Bug #1871961 reported by KLEBER
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

send me news thanks

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.0-2ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 9 18:09:06 2020
DisplayManager: gdm3
ExecutablePath: /usr/libexec/gnome-shell-hotplug-sniffer
InstallationDate: Installed on 2020-04-09 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324)
ProcCmdline: /usr/libexec/gnome-shell-hotplug-sniffer
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.UTF-8
RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
SegvAnalysis:
 Segfault happened at: 0x7f2b2e6e4494 <g_str_hash+4>: movsbl (%rdi),%eax
 PC (0x7f2b2e6e4494) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

Revision history for this message
KLEBER (1980lukas) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_str_hash () from /tmp/apport_sandbox_7m52je49/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.1
 g_hash_table_lookup () from /tmp/apport_sandbox_7m52je49/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.1
 deep_count_more_files_callback ()
 next_async_callback_wrapper (source_object=0x560e7629cd00, res=0x7f2b24003d50, user_data=0x560e762b25f0) at ../../../gio/gfileenumerator.c:305
 g_task_return_now (task=0x7f2b24003d50) at ../../../gio/gtask.c:1214

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 gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Seth Arnold (seth-arnold) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1865300, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

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.