pacman crashed with SIGSEGV in __libc_start_main()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xscreensaver (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Dell T3400 8 Gb RAM running on new 13.04/13.10 install. Just insdtalled a couple of packages, "Ubuntu After Install" everything except Chromium. Desktop set to wake-up early morning. I found the screen saver running a curtain looking pink,greens and white verticle ribons. Pressing the space key stopped the screen saver properly and thats about all I know. Hope it helps. Love what I'm seeing so far except no application menu on initial install had to install the "classic menu indicator" for that. Thanks, you all rock.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xscreensaver-
ProcVersionSign
Uname: Linux 3.10.0-6-generic i686
ApportVersion: 2.11-0ubuntu1
Architecture: i386
Date: Thu Aug 1 02:21:26 2013
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-07-30 (2 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130729)
MarkForUpload: True
ProcCmdline: pacman -root
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x804fbce: cmp 0xc60(%eax),%ecx
PC (0x0804fbce) ok
source "0xc60(%eax)" (0x09644004) 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=0xbff96db4, init=0x8055c20, fini=0x8055c90, rtld_fini=
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
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.