muffin crashed with SIGSEGV

Bug #1918857 reported by Joshua Peisach
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
muffin (Ubuntu)
New
Medium
Unassigned

Bug Description

I edited /usr/share/cinnamon/js/ui/runDialog.js to test something/a small feature and muffin began to crash.

ProblemType: Crash
DistroRelease: Ubuntu 21.04
Package: muffin 4.8.1-1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu60
Architecture: amd64
CasperMD5CheckResult: unknown
CrashCounter: 1
CurrentDesktop: X-Cinnamon
Date: Thu Mar 11 23:12:38 2021
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/muffin
InstallationDate: Installed on 2021-02-28 (12 days ago)
InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210227)
ProcCmdline: muffin --replace
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: muffin
StacktraceTop:
 ()
 process_event (bindings=<optimized out>, n_bindings=<optimized out>, display=display@entry=0x55974e29df80, screen=screen@entry=0x55974e299160, window=window@entry=0x0, event=event@entry=0x7ffd92fc63f0, keysym=65289, on_window=0, allow_release=0, mouse_grab_move=0) at core/keybindings.c:1582
 process_modifier_key (allow_key_up=<synthetic pointer>, have_window=<optimized out>, keysym=65289, event=0x7ffd92fc63f0, window=0x0, screen=0x55974e299160, display=0x55974e29df80) at core/keybindings.c:1627
 meta_display_process_key_event (display=display@entry=0x55974e29df80, window=window@entry=0x0, event=event@entry=0x7ffd92fc63f0) at core/keybindings.c:1736
 event_callback (event=0x7ffd92fc63f0, data=0x55974e29df80) at core/display.c:1815
Title: muffin crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo
separator:

Revision history for this message
Joshua Peisach (itzswirlz) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 process_event (bindings=<optimized out>, n_bindings=<optimized out>, display=display@entry=0x55974e29df80, screen=screen@entry=0x55974e299160, window=window@entry=0x0, event=event@entry=0x7ffd92fc63f0, keysym=65289, on_window=0, allow_release=0, mouse_grab_move=0) at core/keybindings.c:1582
 process_modifier_key (allow_key_up=<synthetic pointer>, have_window=<optimized out>, keysym=65289, event=0x7ffd92fc63f0, window=0x0, screen=0x55974e299160, display=0x55974e29df80) at core/keybindings.c:1627
 meta_display_process_key_event (display=display@entry=0x55974e29df80, window=window@entry=0x0, event=event@entry=0x7ffd92fc63f0) at core/keybindings.c:1736
 event_callback (event=0x7ffd92fc63f0, data=0x55974e29df80) at core/display.c:1815

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 muffin (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
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.