Bug 929443

Summary: Unable to start GNOME session on F-18 Live CD in gnome-boxes
Product: [Fedora] Fedora Reporter: Michael Monreal <michael.monreal>
Component: gnome-boxesAssignee: Christophe Fergeau <cfergeau>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 18CC: berrange, cfergeau, marcandre.lureau, virt-maint, zeenix
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 20:23:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot
none
output none

Description Michael Monreal 2013-03-30 18:18:04 UTC
Created attachment 718318 [details]
Screenshot

Description of problem:
I am not able to boot a F-18 desktop live CD in current F-18. The desktop session seems to crash during start and it always stays in the "Oh no! Something has gone wrong." screen.

The same ISO boots fine in virt-manager on the same system btw.

Version-Release number of selected component (if applicable):
gnome-boxes-3.6.3-1.fc18.x86_64
qemu-kvm-1.2.2-6.fc18.x86_64

How reproducible:
Just boot desktop spin in gnome-boxes.

Comment 1 Christophe Fergeau 2013-04-01 11:28:15 UTC
Very likely to be bug https://bugzilla.gnome.org/show_bug.cgi?id=695283
Can you attach /proc/cpuinfo, the output of virsh capabilities, and check dmesg on the guest for something like:
traps: gnome-shell[1289] trap invalid
                opcode ip:xxxxxxxxxxx sp:xxxxxxxxxx error:0

Comment 2 Michael Monreal 2013-04-01 12:06:45 UTC
Created attachment 730251 [details]
output

Here is the output of the commands you asked for on the host side. How can I get the desired information on the VM?

Comment 3 Fedora End Of Life 2013-12-21 12:34:22 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2014-02-05 20:23:10 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.