gnome-session crashed with SIGSEGV in g_object_unref()

Bug #1202116 reported by Dimitri John Ledkov
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-session (Ubuntu)
New
Undecided
Unassigned

Bug Description

Crash! =)

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-session-bin 3.8.2.1-1ubuntu4
ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
Date: Wed Jul 17 09:10:03 2013
ExecutablePath: /usr/bin/gnome-session
InstallationDate: Installed on 2012-01-12 (551 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318)
MarkForUpload: True
ProcCmdline: gnome-session --session=ubuntu
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f1732cdfb04 <g_object_unref+20>: cmpq $0x50,(%rax)
 PC (0x7f1732cdfb04) ok
 source "$0x50" ok
 destination "(%rax)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-session
StacktraceTop:
 g_object_unref (_object=0x22c79e0) at /build/buildd/glib2.0-2.37.3/./gobject/gobject.c:3086
 ?? ()
 ?? ()
 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 message_queue_dispatch (source=source@entry=0x213e4d0, callback=<optimised out>, user_data=<optimised out>) at dbus-gmain.c:90
Title: gnome-session crashed with SIGSEGV in g_object_unref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo

Revision history for this message
Dimitri John Ledkov (xnox) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1196163, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

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.