Bug 1482845 - gnome-boxes has 100% cpu after closing it
Summary: gnome-boxes has 100% cpu after closing it
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-boxes
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Christophe Fergeau
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-18 08:28 UTC by Antonin
Modified: 2018-02-20 17:41 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-02-20 17:41:18 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Antonin 2017-08-18 08:28:14 UTC
Description of problem:

I have created some virtual machine. I select it and click on "delete" button. Immediately after that I close the gnome-boxes window. (don't touch notification about undelete option)

And there are 3 issues:
- I can't start (or open) gnome-boxes application again
- in "top" there is running gnome-boxes process with 100% cpu
- after killing it I can open gnome-boxes but deleted virtual machine is NOT deleted

Comment 1 Antonin 2017-08-25 09:08:19 UTC
100% cpu and not possible to open gnome-boxes you can achieve this way:
- start Tails in gnome-boxes - https://tails.boum.org/
- stop Tails
- immediately close window with gnome-boxes application (don't touch notification message)

Comment 2 Milan Zink 2018-02-20 15:34:12 UTC
I have exactly the same problem.

Comment 3 Milan Zink 2018-02-20 16:46:18 UTC
I've deleted all the local config files from my home directory

./.local/share/gnome-boxes
./.cache/gnome-boxes
./.config/libvirt/storage/autostart/gnome-boxes.xml
./.config/libvirt/storage/gnome-boxes.xml
./.config/gnome-boxes

and the problem seems to be gone. Looks like some bad configuration options left over from previous versions.. or corrupted files.

Comment 4 Felipe Borges 2018-02-20 17:41:18 UTC
This has been fixed upstream in commit https://gitlab.gnome.org/GNOME/gnome-boxes/commit/2da41ddc99f24b50f025bb7e269effc231406da4

The fix will be available in Fedora 28.

If you can't wait for that, I've prepared a scratch-build containing the fix: https://koji.fedoraproject.org/koji/taskinfo?taskID=25193057


Note You need to log in before you can comment on or make changes to this bug.