budgie-panel crashed with SIGSEGV

Bug #1861557 reported by Frogs Hair
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
budgie-desktop (Ubuntu)
New
Medium
Unassigned

Bug Description

Ubuntu Budgie Panel Crash 20.04 Development release. May be different than previous reports.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: budgie-core 10.5.1-3
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Sat Feb 1 08:13:15 2020
ExecutablePath: /usr/bin/budgie-panel
InstallationDate: Installed on 2019-11-28 (65 days ago)
InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20191127)
ProcCmdline: budgie-panel
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f9008445f38: cmp %rdi,0x18(%rax)
 PC (0x7f9008445f38) ok
 source "%rdi" ok
 destination "0x18(%rax)" (0x01193514) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: budgie-desktop
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/budgie-desktop/plugins/budgie-genmon-plugin/libappmenu-budgie.so
 ?? () from /usr/lib/budgie-desktop/plugins/budgie-genmon-plugin/libappmenu-budgie.so
 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: budgie-panel crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd pico plugdev sambashare sudo
separator:

Revision history for this message
Frogs Hair (detaill) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 node_get_pos () from /tmp/apport_sandbox_wlo1ugub/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6303.0
 layout_parse (layout=<optimized out>, menu=0x7f8ff005c5e0) at ../lib/dbusmenu-importer/model.c:264
 layout_parse (menu=0x7f8ff005c5e0, layout=<optimized out>) at ../lib/dbusmenu-importer/model.c:178
 get_layout_cb (source_object=0x5565c73f6080, res=0x5565c74960c0, user_data=user_data@entry=0x7f8ff005c5e0) at ../lib/dbusmenu-importer/model.c:415
 g_task_return_now (task=0x5565c74960c0) 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 budgie-desktop (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
fossfreedom (fossfreedom) wrote :

If you can remember ... Was this issue due to using the global menu - specifically using QT based apps like VSCode?

Revision history for this message
Frogs Hair (detaill) wrote :

I can't remember an seeing that no other users were affected I wouldn't waste time on this report. I don't use VSCode.I may have been experimenting with Kconnect or a QT based movie player, but I can't be sure.

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.