wrapper-1.0 crashed with SIGSEGV

Bug #1424561 reported by David Pires on 2015-02-23
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
xfce4-panel (Ubuntu)
Undecided
Unassigned

Bug Description

The panel wrapper crashed upon login, after performing sudo apt-get update && sudo apt-get dist-upgrade in TTY1

~$ apt-cache policy xfce4-panel
xfce4-panel:
  Installed: 4.11.2-0ubuntu1
  Candidate: 4.11.2-0ubuntu1
  Version table:
 *** 4.11.2-0ubuntu1 0
        500 http://pt.archive.ubuntu.com/ubuntu/ vivid/universe i386 Packages
        100 /var/lib/dpkg/status

~$ lsb_release -a && uname -r
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Vivid Vervet (development branch)
Release: 15.04
Codename: vivid
3.18.0-14-generic

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: xfce4-panel 4.11.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.18.0-14.15-generic 3.18.7
Uname: Linux 3.18.0-14-generic i686
ApportVersion: 2.16.1-0ubuntu2
Architecture: i386
CurrentDesktop: XFCE
Date: Mon Feb 23 09:25:23 2015
Disassembly: => 0x24bc8b6c: Cannot access memory at address 0x24bc8b6c
ExecutablePath: /usr/lib/i386-linux-gnu/xfce4/panel/wrapper-1.0
InstallationDate: Installed on 2014-07-15 (222 days ago)
InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Alpha i386 (20140506)
ProcCmdline: /usr/lib/i386-linux-gnu/xfce4/panel/wrapper-1.0 /usr/lib/i386-linux-gnu/xfce4/panel/plugins/libsystray.so 4 29360163 systray Notification\ Area Area\ where\ notification\ icons\ appear
SegvAnalysis:
 Segfault happened at: 0x24bc8b6c: Cannot access memory at address 0x24bc8b6c
 PC (0x24bc8b6c) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: xfce4-panel
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
Title: wrapper-1.0 crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

David Pires (slickymaster) wrote :
information type: Private → Public

StacktraceSource:
 #0 0x24bc8b6c in ?? ()
 #1 0xb7137078 in gdk_threads_dispatch_free (data=0xb6582779 <_dbus_message_loader_queue_messages+9>) at /build/buildd/gtk+2.0-2.24.26/gdk/gdk.c:547
   [Error: /build/buildd/gtk+2.0-2.24.26/gdk/gdk.c was not found in source tree]
 #2 0xb6bd0000 in ?? () from /tmp/apport_sandbox_TbcmLi/usr/lib/i386-linux-gnu/libX11.so.6
StacktraceTop:
 ?? ()
 gdk_threads_dispatch_free (data=0xb6582779 <_dbus_message_loader_queue_messages+9>) at /build/buildd/gtk+2.0-2.24.26/gdk/gdk.c:547
 ?? () from /tmp/apport_sandbox_TbcmLi/usr/lib/i386-linux-gnu/libX11.so.6

tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1424561

tags: added: iso-testing
Launchpad Janitor (janitor) wrote :

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

Changed in xfce4-panel (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers