pacman crashed with SIGSEGV in __libc_start_main()

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

Bug Description

Ubuntu 13.10 KDE

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xscreensaver-data-extra 5.15-2ubuntu2
ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
Date: Sat Jul 13 17:03:40 2013
ExecutablePath: /usr/lib/xscreensaver/pacman
ExecutableTimestamp: 1367929476
InstallationDate: Installed on 2013-07-13 (0 days ago)
InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Alpha amd64 (20130712)
MarkForUpload: True
ProcCmdline: pacman -root
ProcCwd: /home/marty
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4084bf: cmp 0xdb8(%rdi),%esi
 PC (0x004084bf) ok
 source "0xdb8(%rdi)" (0x01d56004) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: xscreensaver
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main (main=0x4027f0, argc=2, ubp_av=0x7fffb5dc4568, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffb5dc4558) 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 root sambashare sudo

Revision history for this message
martyfelker (martyfelker-gmail) 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-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.