mate-panel crashed with SIGSEGV in setup_button()

Bug #1678634 reported by SM3FT
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mate-panel (Ubuntu)
Expired
Medium
Unassigned

Bug Description

When doing update of the program starter icon, it did not change.

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: mate-panel 1.18.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
Uname: Linux 4.10.0-14-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: MATE
Date: Sun Apr 2 17:30:24 2017
ExecutablePath: /usr/bin/mate-panel
InstallationDate: Installed on 2017-03-29 (4 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
ProcCmdline: mate-panel
ProcEnviron:
 LANGUAGE=sv_SE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x55685325c54c: mov (%rax),%rbx
 PC (0x55685325c54c) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mate-panel
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: mate-panel crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm backup bin cdrom dip disk libvirt lpadmin mail plugdev root sambashare sudo sys www-data

Revision history for this message
SM3FT (sm3ft) wrote :
information type: Private → Private Security
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 setup_button (launcher=0x556857eba3c0) at launcher.c:539
 g_closure_invoke () from /tmp/apport_sandbox_oefGqK/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /tmp/apport_sandbox_oefGqK/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /tmp/apport_sandbox_oefGqK/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /tmp/apport_sandbox_oefGqK/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.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 mate-panel (Ubuntu):
importance: Undecided → Medium
summary: - mate-panel crashed with SIGSEGV in g_closure_invoke()
+ mate-panel crashed with SIGSEGV in setup_button()
tags: removed: need-amd64-retrace
Revision history for this message
Steve Beattie (sbeattie) 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 mate-panel (Ubuntu):
status: New → Confirmed
no longer affects: glib2.0 (Ubuntu)
Norbert (nrbrtx)
Changed in mate-panel (Ubuntu):
status: Confirmed → Incomplete
tags: removed: zesty
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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