budgie-polkit-dialog crashed with SIGSEGV in g_bytes_unref()

Bug #1812653 reported by Eric Carvalho
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
budgie-desktop (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

This crash happens just after login.

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: budgie-core 10.4+git20190110.01.1f8eceaa58e-1
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu18
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Mon Jan 21 08:46:43 2019
ExecutablePath: /usr/bin/budgie-polkit-dialog
InstallationDate: Installed on 2017-12-22 (394 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221)
ProcCmdline: budgie-polkit-dialog
SegvAnalysis:
 Segfault happened at: 0x7f1d6d6bb71f: add %cl,-0x7b(%rax)
 PC (0x7f1d6d6bb71f) ok
 source "%cl" ok
 destination "-0x7b(%rax)" (0x7f1d6d6bb6a4) in non-writable VMA region: 0x7f1d6d683000-0x7f1d6d700000 r-xp /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.5800.1
 Stack memory exhausted (SP below stack segment)
SegvReason: writing VMA /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.5800.1
Signal: 11
SourcePackage: budgie-desktop
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_bytes_unref () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_variant_unref () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_hash_table_unref () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: budgie-polkit-dialog crashed with SIGSEGV in g_bytes_unref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers wireshark

Revision history for this message
Eric Carvalho (eric-carvalho) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () at ../../../../glib/gmem.c:169 from /tmp/apport_sandbox_7vu82sol/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_bytes_unref (bytes=0x559a430510f0) at ../../../../glib/gbytes.c:337
 g_variant_unref (value=0x559a431eaaf0) at ../../../../glib/gvariant-core.c:638
 g_hash_table_remove_all_nodes (hash_table=hash_table@entry=0x559a430e8980, notify=notify@entry=1, destruction=destruction@entry=1) at ../../../../glib/ghash.c:552
 g_hash_table_remove_all_nodes (destruction=1, notify=1, hash_table=0x559a430e8980) at ../../../../glib/ghash.c:1103

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

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

Changed in budgie-desktop (Ubuntu):
status: New → Confirmed
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.