After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 676308 - Segfault after accessing box which failed during install
Segfault after accessing box which failed during install
Status: RESOLVED INCOMPLETE
Product: gnome-boxes
Classification: Applications
Component: general
3.4.x (unsupported)
Other Linux
: Normal major
: --
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-05-18 11:28 UTC by Jiří Koten
Modified: 2016-03-31 14:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
ABRT log (168.62 KB, text/plain)
2012-05-18 11:28 UTC, Jiří Koten
Details

Description Jiří Koten 2012-05-18 11:28:36 UTC
Created attachment 214303 [details]
ABRT log

Sometimes happen that boxes fail during installation, but the box then appears in the overview. Boxes crash when I click on this box.

Example is cancelled install - see bug 676526 or as in this case where SELinux denies qemu-kvm access on the file /home/test/.libvirt/qemu/log/Fedora 17 2.log 

Installation doesn't finish correctly but the box is present in the boxes overview.       

Boxes should handle such failed installations and won't try to run them.
Comment 1 Christophe Fergeau 2012-05-18 11:33:00 UTC
backtrace is the same as bug #676526
Comment 2 Zeeshan Ali 2012-05-23 14:07:15 UTC
(In reply to comment #0)
> Created an attachment (id=214303) [details]
> ABRT log
> 
> Sometimes happen that boxes fail during installation, but the box then appears
> in the overview. Boxes crash when I click on this box.
> 
> Example is cancelled install - see bug 676526

Thats a gedit bug.
Comment 3 Jiří Koten 2012-05-23 15:14:25 UTC
Sorry for the typo, It's actually the bug 676256.
Comment 4 Zeeshan Ali 2012-06-06 03:02:33 UTC
While I was able to reproduce bug#676256, I failed to reproduce this one. Anyways, that IMO is the real bug and this is side-affect of leaving a non-functional domain around.
Comment 5 Marc-Andre Lureau 2012-09-06 08:47:26 UTC
Can this bug still be reproduced?
Comment 6 Tobias Mueller 2013-01-14 22:00:08 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!