gnome-session crashed with SIGSEGV

Bug #1193291 reported by Iain Lane
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-session (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Patched g-s-d to force use of the background plugin & enabled it.

Nautilus 3.8.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-session-bin 3.8.2.1-1ubuntu2
ProcVersionSignature: Ubuntu 3.9.0-6.13-generic 3.9.6
Uname: Linux 3.9.0-6-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.10.2-0ubuntu1
Architecture: amd64
Date: Fri Jun 21 11:11:16 2013
ExecutablePath: /usr/bin/gnome-session
InstallationDate: Installed on 2012-10-07 (256 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
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/zsh
SegvAnalysis:
 Segfault happened at: 0x41d76e: mov 0x8(%rax),%rcx
 PC (0x0041d76e) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-session
Stacktrace:
 #0 0x000000000041d76e in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x7fff02857ab8
StacktraceTop: ?? ()
Title: gnome-session crashed with SIGSEGV
UpgradeStatus: Upgraded to saucy on 2013-05-07 (45 days ago)
UserGroups: adm autopilot cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo vboxusers

Revision history for this message
Iain Lane (laney) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0x000000000041d76e in app_condition_changed (app=0x1d31bc0, app@entry=<error reading variable: Cannot access memory at address 0x7fff02857ab8>, condition=0, condition@entry=<error reading variable: Cannot access memory at address 0x7fff02857ab8>, manager=0x1d10100, manager@entry=<error reading variable: Cannot access memory at address 0x7fff02857ab8>) at gsm-manager.c:432
         error = <error reading variable error (Cannot access memory at address 0x7fff02857a88)>
         res = <optimized out>
         client = 0x0
 Cannot access memory at address 0x7fff02857ab8
StacktraceTop: app_condition_changed (app=0x1d31bc0, app@entry=<error reading variable: Cannot access memory at address 0x7fff02857ab8>, condition=0, condition@entry=<error reading variable: Cannot access memory at address 0x7fff02857ab8>, manager=0x1d10100, manager@entry=<error reading variable: Cannot access memory at address 0x7fff02857ab8>) at gsm-manager.c:432

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-session (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Jeremy Bícha (jbicha)
information type: Private → Public
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

Changed in gnome-session (Ubuntu):
status: New → 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.