pacman crashed with SIGSEGV in __libc_start_main()

Bug #1229513 reported by Scott Moore
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xscreensaver (Ubuntu)
New
Undecided
Unassigned

Bug Description

Crash occurs when logging back in after screen saver.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xscreensaver-data-extra 5.15-3ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
Uname: Linux 3.11.0-8-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.12.4-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Mon Sep 23 21:47:15 2013
ExecutablePath: /usr/lib/xscreensaver/pacman
InstallationDate: Installed on 2013-09-08 (16 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130907)
MarkForUpload: True
ProcCmdline: pacman -root
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x804fbce: cmp 0xc60(%eax),%ecx
 PC (0x0804fbce) ok
 source "0xc60(%eax)" (0x091a3008) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: xscreensaver
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main (main=0x8049c80, argc=2, ubp_av=0xbfbddc94, init=0x8055c20, fini=0x8055c90, rtld_fini=0xb77525f0 <_dl_fini>, stack_end=0xbfbddc8c) at libc-start.c:260
Title: pacman crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Scott Moore (scottbomb) 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 #1196251, 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.

information type: Private → Public
tags: removed: need-i386-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.