lscpu crashed with SIGFPE in __libc_start_main()

Bug #1055341 reported by sasa becircic
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
util-linux (Ubuntu)
New
Undecided
Unassigned

Bug Description

Description: Ubuntu quantal (development branch)
Release: 12.10

util-linux:
  Installed: 2.20.1-5.1ubuntu2
  Candidate: 2.20.1-5.1ubuntu2
  Version table:
 *** 2.20.1-5.1ubuntu2 0
        500 http://ubuntu.inode.at/ubuntu/ quantal/main i386 Packages
        100 /var/lib/dpkg/status

Immediately after boot-up!

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: util-linux 2.20.1-5.1ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic i686
ApportVersion: 2.5.2-0ubuntu4
Architecture: i386
Date: Sun Sep 23 13:35:48 2012
ExecutablePath: /usr/bin/lscpu
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120809.1)
ProcCmdline: lscpu
ProcEnviron:
 LANGUAGE=C
 SHELL=/bin/bash
 TERM=unknown
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Signal: 8
SourcePackage: util-linux
StacktraceTop:
 ?? ()
 __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
 ?? ()
Title: lscpu crashed with SIGFPE in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
sasa becircic (sasaenator) 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 #1053539, 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.

visibility: 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