pacman crashed with SIGSEGV in __libc_start_main()

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

Bug Description

Computer was running with xscreensaver on at the time.
Eric Tennant

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: xscreensaver-data-extra 5.15-3ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
Uname: Linux 3.13.0-18-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Fri Mar 21 13:22:09 2014
ExecutablePath: /usr/lib/xscreensaver/pacman
InstallationDate: Installed on 2014-03-19 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140319)
ProcCmdline: pacman -root
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4084bf: cmp 0xdb8(%rdi),%esi
 PC (0x004084bf) ok
 source "0xdb8(%rdi)" (0x00bea000) 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, argv=0x7fff912da3b8, init=<optimised out>, fini=<optimised out>, rtld_fini=<optimised out>, stack_end=0x7fff912da3a8) at libc-start.c:285
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
eric tennant (erictennant) wrote :
information type: Private → Public
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.

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.