Bug 827932
| Summary: | [abrt] gnome-boxes-3.4.2-1.fc17: gvir_config_object_to_xml: Process /usr/bin/gnome-boxes was killed by signal 11 (SIGSEGV) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dandim <dan.dim> | ||||||||||
| Component: | gnome-boxes | Assignee: | Christophe Fergeau <cfergeau> | ||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 17 | CC: | berrange, cfergeau, marcandre.lureau, zeenix | ||||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | abrt_hash:531dca78ba231873adcac95c076c7c87a6ab77ae | ||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2013-07-31 22:07:20 UTC | Type: | --- | ||||||||||
| 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
Dandim
2012-06-03 21:05:23 UTC
Created attachment 588933 [details]
File: backtrace
Created attachment 588934 [details]
File: xsession_errors
Created attachment 588935 [details]
File: maps
Created attachment 588936 [details]
File: dso_list
I know some would say that we should still fix the crash in boxes itself but IMO selinux shouldn't block us in the first place so we wont have any crashes to fix. *** This bug has been marked as a duplicate of bug 802551 *** (In reply to comment #5) > I know some would say that we should still fix the crash in boxes itself but > IMO selinux shouldn't block us in the first place so we wont have any > crashes to fix. > > *** This bug has been marked as a duplicate of bug 802551 *** SELinux denials used to only cause "Box creation failed" errors, and this bug is about a crash. Not even looking at what causes the NULL deref is definitely not how we'll get robust software. (In reply to comment #5) > IMO selinux shouldn't block us in the first place so we wont have any > crashes to fix. > Isn't it something a sysadmin could do if he wants to prevent some users to launch/create VMs? The log has
(gnome-boxes:20036): Boxes-CRITICAL **: libvirt-machine.vala:95: Failed to fetch configuration for domain 'Mageia-2-LiveCD-GNOME-Europe1-Americas-x86_64-CD.iso 2': Unable to get domain XML config: Cannot write data: Roura přerušena (SIGPIPE)
so the connection to libvirt got destroyed somehow (or access to it was blocked). This warning comes from LibvirtMachine::update_domain_config which initializes domain_config when all goes well.
LibvirtMachine::update_display does
update_domain_config ();
try {
var xmldoc = domain_config.to_xml ();
which will crash if update_domain_config failed to set domain_config
I ran into several SELinux alerts with running Boxes due to trying to access ISO images on an NFS share, apparently. I suspect the box entry in the menu wasn't fully created, so clicking-on it caused this error. backtrace_rating: 4 Package: gnome-boxes-3.4.3-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) 1. started boxes for first time, tried to create box from ISO 2. failed with some SELinux problem with the log file 3. clicked "cancel" on the "preparing" screen 4. Boxes displayed overview 5. clicked on the newly-created Box that wasn't finished 6. crash backtrace_rating: 4 Package: gnome-boxes-3.4.3-2.fc17 OS Release: Fedora release 17 (Beefy Miracle) And you got this backtrace? Can you file another bug about the selinux issue you got? I downloaded openSUSE 12.1 x86_64 DVD iso image. Then I run GNOME Boxes. I showed me the screen of creating a new virtual machine and I chose openSUSE. Then I clicked "forward" button then "create" button and it crashed. backtrace_rating: 4 Package: gnome-boxes-3.4.3-2.fc17 OS Release: Fedora release 17 (Beefy Miracle) This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 17'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. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed. |