unity-panel-service crashed with SIGSEGV in __memset_x86_64() from memset() from g_slice_alloc0() from g_type_create_instance()

Bug #1016759 reported by Chris Johnston
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Unity
Invalid
High
Unassigned
unity (Ubuntu)
Invalid
High
Unassigned

Bug Description

Crashed while away from computer

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: unity-services 5.12-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-1.1-generic 3.5.0-rc3
Uname: Linux 3.5.0-1-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.2.5-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Fri Jun 22 17:31:30 2012
ExecutablePath: /usr/lib/unity/unity-panel-service
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcCmdline: /usr/lib/unity/unity-panel-service
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_type_create_instance () 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_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: unity-panel-service crashed with SIGSEGV in g_slice_alloc0()
UpgradeStatus: Upgraded to quantal on 2012-06-12 (10 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Chris Johnston (cjohnston) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __memset_x86_64 () at ../sysdeps/x86_64/multiarch/../memset.S:1229
 memset (__len=152, __ch=0, __dest=0x7fac70005220) at /usr/include/x86_64-linux-gnu/bits/string3.h:85
 g_slice_alloc0 (mem_size=152) at /build/buildd/glib2.0-2.33.2/./glib/gslice.c:1031
 g_type_create_instance (type=140378724471120) at /build/buildd/glib2.0-2.33.2/./gobject/gtype.c:1872
 g_object_constructor (type=<optimized out>, n_construct_properties=3, construct_params=0x7fac70033e20) at /build/buildd/glib2.0-2.33.2/./gobject/gobject.c:1854

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity (Ubuntu):
importance: Undecided → Medium
summary: - unity-panel-service crashed with SIGSEGV in g_slice_alloc0()
+ unity-panel-service crashed with SIGSEGV in __memset_x86_64()
tags: removed: need-amd64-retrace
summary: - unity-panel-service crashed with SIGSEGV in __memset_x86_64()
+ unity-panel-service crashed with SIGSEGV in __memset_x86_64() from
+ memset() from g_slice_alloc0() from g_type_create_instance()
Revision history for this message
Bilal Akhtar (bilalakhtar) wrote :

Seems like a bad memory allocation error, possibly in Compiz.

Changed in unity (Ubuntu):
status: New → Confirmed
Changed in unity:
status: New → Confirmed
importance: Undecided → High
Changed in unity (Ubuntu):
importance: Medium → High
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Compiz does not use glib "g_" functions. That is all Unity.

no longer affects: compiz (Ubuntu)
Revision history for this message
Mikko Saarinen (mikk0) wrote :

Ok

Can't be sure if this is the same bug, but when nvidia kernel modules are in use, I get no top or side panels in desktop after I've logged in. Only the mouse cursor over the default wallpaper. Right clicking opens desktop properties window, so some functionality is still left.

With the free xorg nouveau drivers things work ok, but the left panel is grey a little while after I've logged in, but soon turns to normal colour (transparent?)

I've got GeForce GTX 660 Ti (GK104) if that helps out. Also I have pure 64 bit installation and haven't modified or installed anything yet.

How to check if my problem is caused by the same issue? dmesg or what?

Revision history for this message
Will Cooke (willcooke) wrote :

Sorry folks, but as part of the bug clean up ahead of 16.04 I'm marking this as invalid because it affects an Ubuntu release which is now unsupported. If you can still recreate this bug in a supported release please do open a new bug and we can triage it for consideration in the 16.04 development cycle.

Changed in unity:
status: Confirmed → Invalid
Changed in unity (Ubuntu):
status: Confirmed → Invalid
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.