pacman crashed with SIGSEGV in __libc_start_main()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xscreensaver (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Ubuntu 13.10 patched - xscreensaver on well over an hour.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xscreensaver-
ProcVersionSign
Uname: Linux 3.10.0-2-generic x86_64
NonfreeKernelMo
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Mon Jul 8 16:27:11 2013
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-07-03 (5 days ago)
InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
MarkForUpload: True
ProcCmdline: pacman -root
ProcEnviron:
PATH=(custom, user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x4084bf: cmp 0xdb8(%rdi),%esi
PC (0x004084bf) ok
source "0xdb8(%rdi)" (0x01821008) 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=
Title: pacman crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: Upgraded to saucy on 2013-07-05 (3 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev root sambashare sudo
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.