budgie-wm crashed with SIGSEGV in meta_close_dialog_default_show()

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

Bug Description

Crashed while moving files.

ProblemType: Crash
DistroRelease: Ubuntu 20.10
Package: budgie-core 10.5.1+git20200824-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
Uname: Linux 5.8.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CrashCounter: 1
CurrentDesktop: Budgie:GNOME
Date: Wed Sep 23 13:17:10 2020
ExecutablePath: /usr/bin/budgie-wm
ProcCmdline: budgie-wm
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f61bf8240e4: mov 0x78(%rbp),%rdi
 PC (0x7f61bf8240e4) ok
 source "0x78(%rbp)" (0x00000078) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: budgie-desktop
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libmutter-7.so.0
 meta_close_dialog_show () from /lib/x86_64-linux-gnu/libmutter-7.so.0
 ?? () from /lib/x86_64-linux-gnu/libmutter-7.so.0
 ?? () from /lib/x86_64-linux-gnu/libmutter-7.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: budgie-wm crashed with SIGSEGV in meta_close_dialog_show()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

Revision history for this message
Frogs Hair (detaill) wrote :
tags: removed: need-amd64-retrace
tags: added: need-amd64-retrace
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 meta_close_dialog_default_show (dialog=0x563a69978f20) at ../src/core/meta-close-dialog-default.c:126
 meta_close_dialog_show (dialog=0x563a69978f20) at ../src/core/meta-close-dialog.c:75
 meta_window_set_alive (window=0x563a69cc4420, is_alive=<optimized out>) at ../src/core/delete.c:70
 meta_display_ping_timeout (data=0x563a69ceb490) at ../src/core/display.c:2123
 g_timeout_dispatch () from /tmp/apport_sandbox_l1vvpug9/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6600.0

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
summary: - budgie-wm crashed with SIGSEGV in meta_close_dialog_show()
+ budgie-wm crashed with SIGSEGV in meta_close_dialog_default_show()
tags: removed: need-amd64-retrace
Revision history for this message
fossfreedom (fossfreedom) wrote :

Please can you detail how to reproduce this crash?

information type: Private → Public
Changed in budgie-desktop (Ubuntu):
status: New → Incomplete
Revision history for this message
Frogs Hair (detaill) wrote :

I was moving file folders from the main window of the file manager to a destination folder on the side pane.This was the only activity other than having a docked open web browser.

Revision history for this message
fossfreedom (fossfreedom) wrote : Re: [Bug 1896807] Re: budgie-wm crashed with SIGSEGV in meta_close_dialog_default_show()

> destination folder on the side pane

I cannot reproduce this with Nemo unfortunately.

On Sat, 10 Oct 2020 at 17:10, Frogs Hair <email address hidden> wrote:
>
> I was moving file folders from the main window of the file manager to a
> destination folder on the side pane.This was the only activity other
> than having a docked open web browser.
>
> --
> You received this bug notification because you are subscribed to budgie-
> desktop in Ubuntu.
> https://bugs.launchpad.net/bugs/1896807
>
> Title:
> budgie-wm crashed with SIGSEGV in meta_close_dialog_default_show()
>
> Status in budgie-desktop package in Ubuntu:
> Incomplete
>
> Bug description:
> Crashed while moving files.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 20.10
> Package: budgie-core 10.5.1+git20200824-0ubuntu1
> ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
> Uname: Linux 5.8.0-19-generic x86_64
> NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia
> ApportVersion: 2.20.11-0ubuntu45
> Architecture: amd64
> CasperMD5CheckResult: skip
> CrashCounter: 1
> CurrentDesktop: Budgie:GNOME
> Date: Wed Sep 23 13:17:10 2020
> ExecutablePath: /usr/bin/budgie-wm
> ProcCmdline: budgie-wm
> ProcEnviron:
> LANGUAGE=en_US
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SegvAnalysis:
> Segfault happened at: 0x7f61bf8240e4: mov 0x78(%rbp),%rdi
> PC (0x7f61bf8240e4) ok
> source "0x78(%rbp)" (0x00000078) not located in a known VMA region (needed readable region)!
> destination "%rdi" ok
> SegvReason: reading NULL VMA
> Signal: 11
> SourcePackage: budgie-desktop
> StacktraceTop:
> ?? () from /lib/x86_64-linux-gnu/libmutter-7.so.0
> meta_close_dialog_show () from /lib/x86_64-linux-gnu/libmutter-7.so.0
> ?? () from /lib/x86_64-linux-gnu/libmutter-7.so.0
> ?? () from /lib/x86_64-linux-gnu/libmutter-7.so.0
> ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> Title: budgie-wm crashed with SIGSEGV in meta_close_dialog_show()
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
> separator:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1896807/+subscriptions

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

I was also using the places applet to open different windows in the file manager. I had two crashes and no new crashes since numerous updates.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for budgie-desktop (Ubuntu) because there has been no activity for 60 days.]

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