panel crashed with SIGSEGV in indicator_object_get_entries()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
# trying to install Ubuntu-Gnome 13.04 live cd daily build from a usb media for testing .. this is the 3 attempt, I've set nomodeset to the boot option line, " Try Ubuntu " then I've seen a single line " KVM: Disabled by bios.
=/
http://
MD5 : fe2b38dcaa70a07
=======
ubuntu-
Description: Ubuntu Raring Ringtail (development branch)
Release: 13.04
ubuntu-
=======
ubuntu-
ubiquity:
Installed: 2.13.18
Candidate: 2.13.18
Version table:
*** 2.13.18 0
500 http://
100 /var/lib/
ubuntu-
*-display
description: VGA compatible controller
product: Wrestler [Radeon HD 6320]
vendor: Advanced Micro Devices [AMD] nee ATI
physical id: 1
bus info: pci@0000:00:01.0
version: 00
width: 32 bits
clock: 33MHz
resources: irq:42 memory:
=======
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: ubiquity-
ProcVersionSign
Uname: Linux 3.8.0-15-generic i686
ApportVersion: 2.9.2-0ubuntu5
Architecture: i386
CasperVersion: 1.330
Date: Sun Mar 31 03:30:16 2013
ExecutablePath: /usr/lib/
InstallCmdLine: noprompt cdrom-detect/
LiveMediaBuild: Ubuntu-GNOME 13.04 "Raring Ringtail" - Alpha i386 (20130330)
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcEnviron:
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0xb76e28c8 <indicator_
PC (0xb76e28c8) ok
source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: ubiquity
StacktraceTop:
indicator_
?? ()
__libc_start_main () from /lib/i386-
?? ()
Title: panel crashed with SIGSEGV in indicator_
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 #1161058, 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.