GNOME Boxes issueshttps://gitlab.gnome.org/GNOME/gnome-boxes/-/issues2020-03-30T10:41:04Zhttps://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/4RDP Support2020-03-30T10:41:04ZBugzillaRDP Support## Submitted by James Cape
**[Link to original bug (#674039)](https://bugzilla.gnome.org/show_bug.cgi?id=674039)**
## Description
What it says on the tin :-)## Submitted by James Cape
**[Link to original bug (#674039)](https://bugzilla.gnome.org/show_bug.cgi?id=674039)**
## Description
What it says on the tin :-)GNOME 3.30https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/174use libguestfs API to inspect GPT images2023-03-09T10:59:23ZBugzillause libguestfs API to inspect GPT images## Submitted by Federico Bruni `@fedelibre`
**[Link to original bug (#790505)](https://bugzilla.gnome.org/show_bug.cgi?id=790505)**
## Description
Please see this discussion:
https://github.com/systemd/mkosi/issues/197
Boxes curren...## Submitted by Federico Bruni `@fedelibre`
**[Link to original bug (#790505)](https://bugzilla.gnome.org/show_bug.cgi?id=790505)**
## Description
Please see this discussion:
https://github.com/systemd/mkosi/issues/197
Boxes currently uses libosinfo to detect the OS of ISO files.
It would be nice if it was able to detect the OS of other kind of images, such as GPT images.
In above discussion it was suggested to use libguestfs APIs to inspect the disk image.
http://libguestfs.org/guestfs.3.html#inspectionGNOME 3.34https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/138Make it possible to delete/cancel ongoing clone operations2018-02-13T15:47:42ZBugzillaMake it possible to delete/cancel ongoing clone operations## Submitted by Fabiano Fidêncio
**[Link to original bug (#781469)](https://bugzilla.gnome.org/show_bug.cgi?id=781469)**
## Description
Accidentally clicking on "Clone" instead of "Delete" may lead the user to wait for several minut...## Submitted by Fabiano Fidêncio
**[Link to original bug (#781469)](https://bugzilla.gnome.org/show_bug.cgi?id=781469)**
## Description
Accidentally clicking on "Clone" instead of "Delete" may lead the user to wait for several minutes till the process of cloning the VM is finished.
Another option would be to confirm whether the user really want to clone the VM and let they Cancel the operation before it starts.
Even another option would be to allow cancelling the "Clone" operation after it started.3.29.1https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/52Allow users to specify CPUs assigned to a box2020-03-30T10:41:06ZBugzillaAllow users to specify CPUs assigned to a box## Submitted by Stefan Lau
**[Link to original bug (#748066)](https://bugzilla.gnome.org/show_bug.cgi?id=748066)**
## Description
Created attachment 301856
New slider in action
Since one is able to select the amount of memory and d...## Submitted by Stefan Lau
**[Link to original bug (#748066)](https://bugzilla.gnome.org/show_bug.cgi?id=748066)**
## Description
Created attachment 301856
New slider in action
Since one is able to select the amount of memory and disk-space for a box, in my oppinion one should also be able to select the number of vCPUs for a box. This would be as an additional slider to the memory / disk-space slider. On my machine gnome-boxes defaults to using as many vCPUs as I have cpu-cores, so I would like to be able to reduce this.
I wanted to get into developing gnome-apps, so I have a patch ready that adds this slider (I will try to attach it soon). Since it's my first time in Gnome/Vala/Boxes I might have overlooked some things, so please review (if you think this feature is good.)
**Attachment 301856**, "New slider in action":
![Bildschirmfoto_von__2015-04-17_18-09-35_](/uploads/702fb4c421a379dc1e1c784d2544628c/Bildschirmfoto_von__2015-04-17_18-09-35_.png)GNOME 3.36https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/26Better error message when ENOSPACE2021-11-30T16:22:03ZBugzillaBetter error message when ENOSPACE## Submitted by Bastien Nocera `@hadess`
**[Link to original bug (#731527)](https://bugzilla.gnome.org/show_bug.cgi?id=731527)**
## Description
When running out of space on the disk when we're importing, the UI just says that the im...## Submitted by Bastien Nocera `@hadess`
**[Link to original bug (#731527)](https://bugzilla.gnome.org/show_bug.cgi?id=731527)**
## Description
When running out of space on the disk when we're importing, the UI just says that the import failed.
(gnome-boxes:8546): Boxes-WARNING **: vm-importer.vala:49: Failed to import box '892fc77a8ada9bbd68f87cf2c52ee7cd5ec33c72131c21e45b2a64836677351a 2' from file '/home/hadess/Downloads/892fc77a8ada9bbd68f87cf2c52ee7cd5ec33c72131c21e45b2a64836677351a.qcow2': Failed to execute: qemu-img convert -O qcow2 /home/hadess/Downloads/892fc77a8ada9bbd68f87cf2c52ee7cd5ec33c72131c21e45b2a64836677351a.qcow2 /home/hadess/.local/share/gnome-boxes/images/boxes-unknown-2
(gnome-boxes:8546): Boxes-WARNING **: util.vala:162: Failed to write file '/home/hadess/.config/gnome-boxes/sources/QEMU Session.D094GX': write() failed: No space left on device
There should be a better error message when that happens.GNOME 42https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/18the customize page should have 'undo'2020-03-30T10:41:05ZBugzillathe customize page should have 'undo'## Submitted by Matthias Clasen `@matthiasc`
**[Link to original bug (#710286)](https://bugzilla.gnome.org/show_bug.cgi?id=710286)**
## Description
(from Montreal summit session)
There should be an undo or 'back to defaults' button...## Submitted by Matthias Clasen `@matthiasc`
**[Link to original bug (#710286)](https://bugzilla.gnome.org/show_bug.cgi?id=710286)**
## Description
(from Montreal summit session)
There should be an undo or 'back to defaults' button on the customize page.3.29.1https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/177Introduce "Remote Viewer mode"2020-06-09T10:13:37ZBugzillaIntroduce "Remote Viewer mode"## Submitted by Felipe Borges
**[Link to original bug (#792117)](https://bugzilla.gnome.org/show_bug.cgi?id=792117)**
## Description
Since we aim to suit both virtualization and remote connection users, we should be able to build an...## Submitted by Felipe Borges
**[Link to original bug (#792117)](https://bugzilla.gnome.org/show_bug.cgi?id=792117)**
## Description
Since we aim to suit both virtualization and remote connection users, we should be able to build and launch Boxes with remote viewing capabilities only.
This way remote viewing users don't need to have a working virtualization stack underneath Boxes.
It would also make it easier to run Boxes within a flatpak since what's currently blocking us in this front is the presence/access to libvirt in the sandbox.https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/176Various build related improvements2018-02-13T10:37:37ZBugzillaVarious build related improvements## Submitted by Iñigo Martínez `@inigomartinez`
**[Link to original bug (#791421)](https://bugzilla.gnome.org/show_bug.cgi?id=791421)**
## Description
This bug includes various meson improvements.## Submitted by Iñigo Martínez `@inigomartinez`
**[Link to original bug (#791421)](https://bugzilla.gnome.org/show_bug.cgi?id=791421)**
## Description
This bug includes various meson improvements.https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/175USB redirection doesn't work on I440FX with Windows 10 (and badly with everyt...2020-08-04T02:32:10ZBugzillaUSB redirection doesn't work on I440FX with Windows 10 (and badly with everything else)## Submitted by Maciej (Matthew) Piechotka
**[Link to original bug (#791232)](https://bugzilla.gnome.org/show_bug.cgi?id=791232)**
## Description
It seems to be a known problem:
- https://unix.stackexchange.com/questions/250938/qem...## Submitted by Maciej (Matthew) Piechotka
**[Link to original bug (#791232)](https://bugzilla.gnome.org/show_bug.cgi?id=791232)**
## Description
It seems to be a known problem:
- https://unix.stackexchange.com/questions/250938/qemu-usb-passthrough-windows-guest
- https://wiki.qemu.org/Features/Q35
Probably in 2017 it's a good idea to use q35 as default (verified that it works by modifying libvirt config).https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/173VM fails to start (machine.vala input/output error)2018-12-19T15:21:08ZBugzillaVM fails to start (machine.vala input/output error)## Submitted by Pascal Obry
**[Link to original bug (#790455)](https://bugzilla.gnome.org/show_bug.cgi?id=790455)**
## Description
I'm on GNU/Debian/unstable.
From GNOME Boxes I cannot start a VM. That is GNOME Boxes starts but whe...## Submitted by Pascal Obry
**[Link to original bug (#790455)](https://bugzilla.gnome.org/show_bug.cgi?id=790455)**
## Description
I'm on GNU/Debian/unstable.
From GNOME Boxes I cannot start a VM. That is GNOME Boxes starts but when I try to start a VM (Windows) by clicking on it fails with the following on the console:
(gnome-boxes:29711): Boxes-WARNING **: machine.vala:611: Failed to start Windows XP: Unable to start domain: End of file while reading data: Input/output error
I still can start the VM with qemu directly, so my VM image is not corrupted:
$ qemu-system-x86_64 --enable-kvm images/boxes-unknown
I have looked at the recent updates on my machine and found an update for libvirt0. The installed version is 3.9.0, reverting to libvirt 3.0.0 from GNU/Debian/stable fixes the issue.
So the issue may be in libvirt or it is an incompatibility with GNOME Boxes.
Any idea to better understand what is going on?
Thanks.https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/172Boxes inherit old names when making a clone2023-03-06T11:00:35ZBugzillaBoxes inherit old names when making a clone## Submitted by Ekaterina Gerasimova `@kat`
**[Link to original bug (#790053)](https://bugzilla.gnome.org/show_bug.cgi?id=790053)**
## Description
When I rename a VM, then clone it, the cloned VM has the original name of the first V...## Submitted by Ekaterina Gerasimova `@kat`
**[Link to original bug (#790053)](https://bugzilla.gnome.org/show_bug.cgi?id=790053)**
## Description
When I rename a VM, then clone it, the cloned VM has the original name of the first VM followed by a number rather than the new name of the original VM followed by a number.
For example,
* Create a VM named "red box"
* Rename "red box" to "green box"
* Clone "green box"
* Cloned VM is named "red box 1" rather than "green box 1"
I would expect the cloned VM to be named "green box 1"https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/171FileChooserDialog doesn't go to the manual inserted path2018-06-27T10:47:51ZBugzillaFileChooserDialog doesn't go to the manual inserted path## Submitted by dev..@..ook.it
**[Link to original bug (#789915)](https://bugzilla.gnome.org/show_bug.cgi?id=789915)**
## Description
I can't go to the inserted path in the file chooser dialog.
Steps to reproduce the issue:
1) Open...## Submitted by dev..@..ook.it
**[Link to original bug (#789915)](https://bugzilla.gnome.org/show_bug.cgi?id=789915)**
## Description
I can't go to the inserted path in the file chooser dialog.
Steps to reproduce the issue:
1) Open gnome-boxes
2) Start the creation of a new virtual machine clicking the 'New' button
3) Click on the 'Select file' button (to load your iso)
4) When the file chooser dialog is open, press Ctrl + L to be able to manually put the path where to go
5) Issue: Pressing Enter to jump to the inserted path doesn't work
The expected behaviour is that I can jump to the manually inserted path.
At the beginning I thought that this issue could be more general regarding the gtk file chooser dialog component, but I noticed that the other applications work well, thus I think the problem is related to gnome-boxes.https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/170cannot add folder to share with guest, in the shared folders dialog2019-10-21T04:38:25ZBugzillacannot add folder to share with guest, in the shared folders dialog## Submitted by A.S. Boerema
**[Link to original bug (#789466)](https://bugzilla.gnome.org/show_bug.cgi?id=789466)**
## Description
Created attachment 362240
screenshot
I wanted to use the new shared folders feature, but I cannot g...## Submitted by A.S. Boerema
**[Link to original bug (#789466)](https://bugzilla.gnome.org/show_bug.cgi?id=789466)**
## Description
Created attachment 362240
screenshot
I wanted to use the new shared folders feature, but I cannot get it to work.
I've installed the spice-webdavd service (2.2) int the windows 7x64 guest and it started and is running.
I do get the + menu to add a host folder as a shared folder under the properties menu, but the folder list shows (None) and clicking the pulldownn menu does not give a list of folders.
Thherefore it is not possible to add a folder.
I also would like to add that there is no documentation for this (very nice) feature, other than the blog post form the developer tat implemented it.
My OS is ubuntu 17.10 with gnome 3.26.
**Attachment 362240**, "screenshot":
![Screenshot_from_2017-10-25_11-10-36](/uploads/09969a956944ad41f91e7d937f7a73e7/Screenshot_from_2017-10-25_11-10-36.png)https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/169Screenshot don't have the .png extension2018-01-11T11:36:47ZBugzillaScreenshot don't have the .png extension## Submitted by led..@..il.com
**[Link to original bug (#789221)](https://bugzilla.gnome.org/show_bug.cgi?id=789221)**
## Description
I'm using GNOME Boxes 3.26.1 on Solus 3.
When i use "≡ -> take a screenshot", a screenshot is tak...## Submitted by led..@..il.com
**[Link to original bug (#789221)](https://bugzilla.gnome.org/show_bug.cgi?id=789221)**
## Description
I'm using GNOME Boxes 3.26.1 on Solus 3.
When i use "≡ -> take a screenshot", a screenshot is taken but is named for example "Capture d’écran depuis 2017-10-20 01-30-12" (it's french, "Screenshot from yyyy-mm-dd hh-mm-ss").
The image file is a totally valid png picture, but since there is not the .png extension, i have to manually rename each screenshot if i want to use a picture.https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/168Auto-subscribe RHEL VMs using the Developer Suite subscription2019-07-03T08:46:28ZBugzillaAuto-subscribe RHEL VMs using the Developer Suite subscription## Submitted by Debarshi Ray `@debarshir`
**[Link to original bug (#788886)](https://bugzilla.gnome.org/show_bug.cgi?id=788886)**
## Description
In [bug 786679](https://bugzilla.gnome.org/show_bug.cgi?id=786679), we added the abilit...## Submitted by Debarshi Ray `@debarshir`
**[Link to original bug (#788886)](https://bugzilla.gnome.org/show_bug.cgi?id=788886)**
## Description
In [bug 786679](https://bugzilla.gnome.org/show_bug.cgi?id=786679), we added the ability to install RHEL virtual machines from Red Hat's developer portal. These VMs are eligible to use the gratis Developer Suite subscription. It will be nice if they would be automatically enrolled with Red Hat's subscription management service upon installation.
We need a way to securely wire the user's credentials that are entered in the embedded WebView to the post installation phase of the express installation.
https://bugzilla.gnome.org/show_bug.cgi?id=786679#c47 suggested:
* A Spice channel for the keyring which would allow the host to expose its keyring to the guests? (some spice dev could drop a comment clarifying the feasibility of it)
* A key exchange throughout the webdav channel (guest's agent generates a pair, passes its public key to the host which encrypts the authentication data and passes it back to the guest to feed it to the subscription-manager cli).
https://bugzilla.gnome.org/show_bug.cgi?id=786679#c55 suggested:
Wondering if https://libvirt.org/formatsecret.html could be leveraged to pass this data to the guest? The kickstart file could be put in an encrypted qcow2 volume with an 'ephemeral' secret (assuming the guest being able to access the unencrypted text file is not an issue).Debarshi Rayrishi.is@lostca.seDebarshi Rayrishi.is@lostca.sehttps://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/167gnome-boxes is crashing on startup - Error setting up default broker2018-01-24T15:30:16ZBugzillagnome-boxes is crashing on startup - Error setting up default broker## Submitted by Torben Andresen
**[Link to original bug (#788631)](https://bugzilla.gnome.org/show_bug.cgi?id=788631)**
## Description
Hi,
i installed 3.26 today on my Arch box. After that Gnome-Boxes is crashing on startup. Here i...## Submitted by Torben Andresen
**[Link to original bug (#788631)](https://bugzilla.gnome.org/show_bug.cgi?id=788631)**
## Description
Hi,
i installed 3.26 today on my Arch box. After that Gnome-Boxes is crashing on startup. Here is what i got from terminal:
Error setting up default broker: Unable to open qemu+unix:///session: Cannot recv data: Connection reset by peer
**
Boxes:ERROR:/home/fborges/checkout/gnome-boxes/src/app.vala:442:boxes_app_setup_default_source_co: assertion failed: (default_connection != null)
Aborted (core dumped)https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/166Attempts to delete snapshot every five seconds2018-01-11T18:50:12ZBugzillaAttempts to delete snapshot every five seconds## Submitted by Michael Catanzaro `@mcatanzaro`
**[Link to original bug (#788427)](https://bugzilla.gnome.org/show_bug.cgi?id=788427)**
## Description
I noticed that after deleting a snapshot, Boxes tries to delete it again and agai...## Submitted by Michael Catanzaro `@mcatanzaro`
**[Link to original bug (#788427)](https://bugzilla.gnome.org/show_bug.cgi?id=788427)**
## Description
I noticed that after deleting a snapshot, Boxes tries to delete it again and again forever, once every five seconds or so. Each time, it prints this error message:
(gnome-boxes:17794): Boxes-WARNING **: snapshot-list-row.vala:188: Error while deleting snapshot 2016-09-22-23-42-04: Unable to delete snapshot `2016-09-22-23-42-04'
I think the first attempt to delete the snapshot succeeded (since I was able to resize ;) and the subsequent attempts are all failing because it's already deleted.https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/165"Enter URL" has inconsistent "go back" UI2018-01-24T15:28:42ZBugzilla"Enter URL" has inconsistent "go back" UI## Submitted by Debarshi Ray `@debarshir`
**[Link to original bug (#786689)](https://bugzilla.gnome.org/show_bug.cgi?id=786689)**
## Description
Created attachment 358250
Screenshot of the "Enter URL" page (with the bug)
The New ->...## Submitted by Debarshi Ray `@debarshir`
**[Link to original bug (#786689)](https://bugzilla.gnome.org/show_bug.cgi?id=786689)**
## Description
Created attachment 358250
Screenshot of the "Enter URL" page (with the bug)
The New -> Enter URL page is inconsistent with all the other pages in the WizardWindow when it comes to the behaviour of the "go back" UI. Others use the "back" button in the WizardToolbar headerbar. However, this one uses a strange looking (rounded lower left and right corners) GtkButton in the content area that says "< Enter URL", and the "back" button in the header bar is disabled.
While there are bigger issues with this page (eg., [bug 776955](https://bugzilla.gnome.org/show_bug.cgi?id=776955)), this is relatively easier to fix.
**Attachment 358250**, "Screenshot of the "Enter URL" page (with the bug)":
![gnome-boxes-source-selection-enter-url](/uploads/7a02bf9bfa83a1dc31d74582987e7721/gnome-boxes-source-selection-enter-url.png)https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/164Gnome opens but closes immediately2019-12-18T14:47:19ZBugzillaGnome opens but closes immediately## Submitted by Gal
**[Link to original bug (#786559)](https://bugzilla.gnome.org/show_bug.cgi?id=786559)**
## Description
I am using Arch Linux with the 4.12.8-1 Linux kernel.
I installed Gnome-boxes using pacman (Arch Linux's bina...## Submitted by Gal
**[Link to original bug (#786559)](https://bugzilla.gnome.org/show_bug.cgi?id=786559)**
## Description
I am using Arch Linux with the 4.12.8-1 Linux kernel.
I installed Gnome-boxes using pacman (Arch Linux's binary package manager) and it worked nicely in the beginning, but after a few days it stopped working. Everytime I launch Gnome-boxes, the main window opens, shows the loading animation for a few seconds and then closes. When I ran it using a terminal it displayed the following message:
(gnome-boxes:20899): Boxes-CRITICAL **: media-manager.vala:190: Error connecting to Tracker: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Tracker1 was not provided by any .service files
(gnome-boxes:20899): Libvirt.GObject-CRITICAL **: gvir_storage_vol_get_info: assertion 'GVIR_IS_STORAGE_VOL(vol)' failed
[1] 20899 segmentation fault (core dumped) gnome-boxes
I then tried to compile it from source, and got an error message upon launching it once again:
(gnome-boxes:20541): Boxes-CRITICAL **: media-manager.vala:190: Error connecting to Tracker: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Tracker1 was not provided by any .service files
(gnome-boxes:20541): Libvirt.GObject-CRITICAL **: gvir_storage_vol_get_info: assertion 'GVIR_IS_STORAGE_VOL(vol)' failed
[1] 20541 segmentation fault (core dumped) ./gnome-boxes
Running ./gnome-boxes --check results in the following message:
(gnome-boxes:20989): Boxes-WARNING **: util-app.vala:250: Failed to execute child process ?restorecon? (No such file or directory)
• The CPU is capable of virtualization: yes
• The KVM module is loaded: yes
• Libvirt KVM guest available: yes
• Boxes storage pool available: yes
• The SELinux context is default: no
Report bugs to <https://bugzilla.gnome.org/enter_bug.cgi?product=gnome-boxes>.
Boxes home page: <https://wiki.gnome.org/Apps/Boxes>.https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/163Reverting to a snapshot while VM is running is allowed, but fails2020-02-03T15:09:17ZBugzillaReverting to a snapshot while VM is running is allowed, but fails## Submitted by GN `@gnome-nuclearsunshine`
**[Link to original bug (#786374)](https://bugzilla.gnome.org/show_bug.cgi?id=786374)**
## Description
With a running VM, the UI allows "Revert to this state" for snapshots, but this fails...## Submitted by GN `@gnome-nuclearsunshine`
**[Link to original bug (#786374)](https://bugzilla.gnome.org/show_bug.cgi?id=786374)**
## Description
With a running VM, the UI allows "Revert to this state" for snapshots, but this fails while the VM is running.
After shutting the VM down, snapshot reversion instead succeeds.
If snapshot reversion isn't supported with a running VM, the UI should either informatively disallow it, or automatically shut down the VM first (confirming shouldn't be necessary since reversion a state loss anyway) then revert the VM.
Tested with a freshly installed Fedora 26 Workstation VM and the "Just installed" snapshot.