Public bug reported:

This problem occured when launching a user session on GNOME Shell.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: software-center 13.08-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
Date: Wed Aug 28 21:14:51 2013
ExecutablePath: /usr/share/software-center/software-center
ExecutableTimestamp: 1375903486
InstallationDate: Installed on 2013-05-20 (100 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center apt://docky
ProcCwd: /home/alexandre
SegvAnalysis:
 Segfault happened at: 0x7f893de037e0:  mov    (%rbx),%rax
 PC (0x7f893de037e0) ok
 source "(%rbx)" (0x43000000c8) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: software-center
StacktraceTop:
 ?? () from /usr/lib/libgnome-menu-3.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: software-center crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to saucy on 2013-08-28 (0 days ago)
UserGroups: adm cdrom dip fuse kvm libvirtd lpadmin plugdev sambashare sudo 
vboxusers

** Affects: software-center (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-crash need-amd64-retrace saucy

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-center in Ubuntu.
https://bugs.launchpad.net/bugs/1219069

Title:
  software-center crashed with SIGSEGV in g_main_context_dispatch()

Status in “software-center” package in Ubuntu:
  New

Bug description:
  This problem occured when launching a user session on GNOME Shell.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: software-center 13.08-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Wed Aug 28 21:14:51 2013
  ExecutablePath: /usr/share/software-center/software-center
  ExecutableTimestamp: 1375903486
  InstallationDate: Installed on 2013-05-20 (100 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterpreterPath: /usr/bin/python2.7
  MarkForUpload: True
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/software-center apt://docky
  ProcCwd: /home/alexandre
  SegvAnalysis:
   Segfault happened at: 0x7f893de037e0:        mov    (%rbx),%rax
   PC (0x7f893de037e0) ok
   source "(%rbx)" (0x43000000c8) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: software-center
  StacktraceTop:
   ?? () from /usr/lib/libgnome-menu-3.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: software-center crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: Upgraded to saucy on 2013-08-28 (0 days ago)
  UserGroups: adm cdrom dip fuse kvm libvirtd lpadmin plugdev sambashare sudo 
vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1219069/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to