GNOME Boxes issueshttps://gitlab.gnome.org/GNOME/gnome-boxes/-/issues2018-12-19T15:30:57Zhttps://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/103Can't move the mouse cursor2018-12-19T15:30:57ZBugzillaCan't move the mouse cursor## Submitted by dev..@..ook.it
**[Link to original bug (#767797)](https://bugzilla.gnome.org/show_bug.cgi?id=767797)**
## Description
I tried to install Windows 7 enterprise x86, but I can't move the cursor. I have a laptop and I'm ...## Submitted by dev..@..ook.it
**[Link to original bug (#767797)](https://bugzilla.gnome.org/show_bug.cgi?id=767797)**
## Description
I tried to install Windows 7 enterprise x86, but I can't move the cursor. I have a laptop and I'm using the touchpad (no usb mouse), gnome-boxes grab the mouse but the cursor doesn't move.
I tried also Windows 10 and it works fine.
I don't know if could be useful but my libvirt version is 1.3.4.
I found a discussion about this problem here, but I still must try the proposed workarounds:
http://superuser.com/questions/1055873/windows-vm-in-gnome-boxes-wont-grab-mouse-or-respect-mouse-movementhttps://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/102Crash in boxes2019-12-18T15:46:32ZBugzillaCrash in boxes## Submitted by Ignacio Casal Quinteiro `@icq1`
**[Link to original bug (#767794)](https://bugzilla.gnome.org/show_bug.cgi?id=767794)**
## Description
From time to time I am getting a crash, if I relaunch boxes I can continue to wor...## Submitted by Ignacio Casal Quinteiro `@icq1`
**[Link to original bug (#767794)](https://bugzilla.gnome.org/show_bug.cgi?id=767794)**
## Description
From time to time I am getting a crash, if I relaunch boxes I can continue to work with the guest, so it is something specific to boxes. Let me know if you need more info.
```
Thread 7 (Thread 0x7f0dc3ffe700 (LWP 25302)):
#0 0x00007f0e1319bc4d in poll () at /lib64/libc.so.6
#1 0x00007f0e178e13fd in handle_events.part () at /lib64/libusb-1.0.so.0
#2 0x00007f0e178e2420 in libusb_handle_events_timeout_completed ()
at /lib64/libusb-1.0.so.0
#3 0x00007f0e178e251f in libusb_handle_events () at /lib64/libusb-1.0.so.0
#4 0x00007f0e173afe30 in spice_usb_device_manager_usb_ev_thread ()
at /lib64/libspice-client-glib-2.0.so.8
#5 0x00007f0e13a5cd38 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#6 0x00007f0e1346e5ba in start_thread () at /lib64/libpthread.so.0
#7 0x00007f0e131a77cd in clone () at /lib64/libc.so.6
Thread 6 (Thread 0x7f0ddbfff700 (LWP 25301)):
#0 0x00007f0e1319bc4d in poll () at /lib64/libc.so.6
#1 0x00007f0e178e79f1 in linux_udev_event_thread_main ()
at /lib64/libusb-1.0.so.0
#2 0x00007f0e1346e5ba in start_thread () at /lib64/libpthread.so.0
#3 0x00007f0e131a77cd in clone () at /lib64/libc.so.6
---Type <return> to continue, or q <return> to quit---
Thread 5 (Thread 0x7f0dee3b0700 (LWP 25216)):
#0 0x00007f0e1319bc4d in poll () at /lib64/libc.so.6
#1 0x00007f0e13a36a46 in g_main_context_iterate.isra ()
at /lib64/libglib-2.0.so.0
#2 0x00007f0e13a36b5c in g_main_context_iteration ()
at /lib64/libglib-2.0.so.0
#3 0x00007f0dee3b7fad in dconf_gdbus_worker_thread ()
at /usr/lib64/gio/modules/libdconfsettings.so
#4 0x00007f0e13a5cd38 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#5 0x00007f0e1346e5ba in start_thread () at /lib64/libpthread.so.0
#6 0x00007f0e131a77cd in clone () at /lib64/libc.so.6
Thread 4 (Thread 0x7f0def5bf700 (LWP 25214)):
#0 0x00007f0e131a1919 in syscall () at /lib64/libc.so.6
#1 0x00007f0e13a7adca in g_cond_wait_until () at /lib64/libglib-2.0.so.0
#2 0x00007f0e13a0b489 in g_async_queue_pop_intern_unlocked ()
at /lib64/libglib-2.0.so.0
#3 0x00007f0e13a5d70a in g_thread_pool_thread_proxy ()
at /lib64/libglib-2.0.so.0
#4 0x00007f0e13a5cd38 in g_thread_proxy () at /lib64/libglib-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#5 0x00007f0e1346e5ba in start_thread () at /lib64/libpthread.so.0
#6 0x00007f0e131a77cd in clone () at /lib64/libc.so.6
Thread 3 (Thread 0x7f0df5150700 (LWP 25208)):
#0 0x00007f0e1319bc4d in poll () at /lib64/libc.so.6
#1 0x00007f0e13a36a46 in g_main_context_iterate.isra ()
at /lib64/libglib-2.0.so.0
#2 0x00007f0e13a36dd2 in g_main_loop_run () at /lib64/libglib-2.0.so.0
#3 0x00007f0e1402ff76 in gdbus_shared_thread_func () at /lib64/libgio-2.0.so.0
#4 0x00007f0e13a5cd38 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#5 0x00007f0e1346e5ba in start_thread () at /lib64/libpthread.so.0
#6 0x00007f0e131a77cd in clone () at /lib64/libc.so.6
Thread 2 (Thread 0x7f0df5951700 (LWP 25207)):
#0 0x00007f0e1319bc4d in poll () at /lib64/libc.so.6
#1 0x00007f0e13a36a46 in g_main_context_iterate.isra ()
at /lib64/libglib-2.0.so.0
#2 0x00007f0e13a36b5c in g_main_context_iteration ()
at /lib64/libglib-2.0.so.0
#3 0x00007f0e13a36ba1 in glib_worker_main () at /lib64/libglib-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#4 0x00007f0e13a5cd38 in g_thread_proxy () at /lib64/libglib-2.0.so.0
#5 0x00007f0e1346e5ba in start_thread () at /lib64/libpthread.so.0
#6 0x00007f0e131a77cd in clone () at /lib64/libc.so.6
Thread 1 (Thread 0x7f0e18c8bb00 (LWP 25205)):
#0 0x00007f0e13a3d19b in g_logv () at /lib64/libglib-2.0.so.0
#1 0x00007f0e13a3d30f in g_log () at /lib64/libglib-2.0.so.0
#2 0x00007f0e13a5d14b in g_thread_new () at /lib64/libglib-2.0.so.0
#3 0x0000556bc2fed645 in boxes_async_launcher_launch_co ()
#4 0x0000556bc2f89627 in boxes_libvirt_machine_update_io_stat_co ()
#5 0x0000556bc2f89da5 in boxes_libvirt_machine_update_stats_co ()
#6 0x00007f0e13fd3343 in g_task_return_now () at /lib64/libgio-2.0.so.0
#7 0x00007f0e13fd3379 in complete_in_idle_cb () at /lib64/libgio-2.0.so.0
#8 0x00007f0e13a36703 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#9 0x00007f0e13a36ab0 in g_main_context_iterate.isra ()
at /lib64/libglib-2.0.so.0
#10 0x00007f0e13a36b5c in g_main_context_iteration ()
at /lib64/libglib-2.0.so.0
#11 0x00007f0e13ff958d in g_application_run () at /lib64/libgio-2.0.so.0
#12 0x0000556bc2f9e199 in _vala_main ()
---Type <return> to continue, or q <return> to quit---
#13 0x00007f0e130c4731 in __libc_start_main () at /lib64/libc.so.6
#14 0x0000556bc2f62549 in _start ()
```https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/101Popup Menus Behind VNC Display2020-10-08T14:04:14ZBugzillaPopup Menus Behind VNC Display## Submitted by Max Ehrlich
**[Link to original bug (#767023)](https://bugzilla.gnome.org/show_bug.cgi?id=767023)**
## Description
Overview:
When using the gnome-boxes, and connect via VNC (I haven't tried a VM), the menus (triggere...## Submitted by Max Ehrlich
**[Link to original bug (#767023)](https://bugzilla.gnome.org/show_bug.cgi?id=767023)**
## Description
Overview:
When using the gnome-boxes, and connect via VNC (I haven't tried a VM), the menus (triggered by buttons in the top right of the window) appear to pop up behind the VNC display, making them unusable. I have had this problem on previous versions of Boxes as well. Furthermore in fullscreen mode, I assume something similar happens with the popup menu that would allow you to end the connection, which should be accessed by mousing over the top middle of the screen. The result of this is that you need to tell your server to kick views in order to get out of boxes.
Steps to Reproduce:
1. Open Boxes
2. VNC someplace
3. Click any of the menu buttons on the top right
Actual Result:
Menu pops up behind VNC display
Expected Result:
Menu's are actually usable
Please let me know if I can provide any additional information I have attached a short video demonstrating the issue, if you look very closely you can see that the menus have popped up and are behind the VNC display.https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/100Please improve the description when asking privileges to change the mode on a...2020-10-08T13:57:03ZBugzillaPlease improve the description when asking privileges to change the mode on a VM image## Submitted by Laurent Bigonville `@bigon`
**[Link to original bug (#766873)](https://bugzilla.gnome.org/show_bug.cgi?id=766873)**
## Description
Related to bug #766727
The description when calling polkit to change the permission ...## Submitted by Laurent Bigonville `@bigon`
**[Link to original bug (#766873)](https://bugzilla.gnome.org/show_bug.cgi?id=766873)**
## Description
Related to bug #766727
The description when calling polkit to change the permission on the system VM images should be improved.
IMHO, it should state clearly why and what it gonna do (change the permissions of the file on the filesystem)https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/99unattended-installation: Don't accept passwordless VMs unless password is set...2019-02-24T12:10:33ZBugzillaunattended-installation: Don't accept passwordless VMs unless password is set as optional by libosinfo## Submitted by Fabiano Fidêncio
**[Link to original bug (#766731)](https://bugzilla.gnome.org/show_bug.cgi?id=766731)**
## Description
Some install scripts don't have to have the password set, as the OpenSUSE case. But some of them...## Submitted by Fabiano Fidêncio
**[Link to original bug (#766731)](https://bugzilla.gnome.org/show_bug.cgi?id=766731)**
## Description
Some install scripts don't have to have the password set, as the OpenSUSE case. But some of them do, as the Debian case. As this info, about the password being required or optional, is provided by libosinfo, we must make use of it for deciding whether the user can start the installation without setting a password for the VM or not.https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/95overlay notifications stack up in weird way2022-01-21T10:03:32ZBugzillaoverlay notifications stack up in weird way## Submitted by Christian Hergert `@chergert`
**[Link to original bug (#764520)](https://bugzilla.gnome.org/show_bug.cgi?id=764520)**
## Description
Created attachment 325250
stacked notifications
Screenshot attached. Not sure I ha...## Submitted by Christian Hergert `@chergert`
**[Link to original bug (#764520)](https://bugzilla.gnome.org/show_bug.cgi?id=764520)**
## Description
Created attachment 325250
stacked notifications
Screenshot attached. Not sure I have a suggestion on a better way to show this, just found it a bit weird when pruning old VMs.
**Attachment 325250**, "stacked notifications":
![Screenshot_from_2016-04-02_23-22-53](/uploads/51f529e75fef5998b4210676e0ed295c/Screenshot_from_2016-04-02_23-22-53.png)https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/94Allow creating new box using drag and drop of image files2018-02-09T17:07:35ZBugzillaAllow creating new box using drag and drop of image files## Submitted by Mohammed Sadiq `@pksadiq`
**[Link to original bug (#764054)](https://bugzilla.gnome.org/show_bug.cgi?id=764054)**
## Description
It would be nice if a user be able to create/boot new boxes by drag and drop of compati...## Submitted by Mohammed Sadiq `@pksadiq`
**[Link to original bug (#764054)](https://bugzilla.gnome.org/show_bug.cgi?id=764054)**
## Description
It would be nice if a user be able to create/boot new boxes by drag and drop of compatible files (iso/raw/img etc.) from programs like nautilus.https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/93GRUB2 doesn't respond to ctrl-x or f102021-05-04T11:49:04ZBugzillaGRUB2 doesn't respond to ctrl-x or f10## Submitted by Chris Murphy
**[Link to original bug (#764002)](https://bugzilla.gnome.org/show_bug.cgi?id=764002)**
## Description
Created attachment 324498
screenshot of grub menu where ctrl-x and F10 don't work but should
gnome-...## Submitted by Chris Murphy
**[Link to original bug (#764002)](https://bugzilla.gnome.org/show_bug.cgi?id=764002)**
## Description
Created attachment 324498
screenshot of grub menu where ctrl-x and F10 don't work but should
gnome-boxes-3.18.1-1.fc23.x86_64
1. Start any VM that uses GRUB2 bootloader such as Fedora 23 or 24.
2. At the GRUB boot menu type e to edit an entry.
3. Modify boot entry (or not, problem happens either way).
4. Use control-x or F10 to boot the modified entry.
Result:
Nothing. GRUB seems to not get the keyboard command ctrl-x or F10, but does see other individual key entries because I can edit the boot entry.
Expected:
I should be able to control-x or F10 somehow. Maybe a way to use arbitrary keyboard combinations from the Boxes keyboard icon that contains a handful of these like ctrl-alt-f1.
**Attachment 324498**, "screenshot of grub menu where ctrl-x and F10 don't work but should":
![Screenshot_from_2016-03-21_12-51-55](/uploads/debd02b3ffa481f33527f64863b19741/Screenshot_from_2016-03-21_12-51-55.png)https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/92screen flicker at GDM, mouse click erratic response, black login screen2023-10-04T12:35:35ZBugzillascreen flicker at GDM, mouse click erratic response, black login screen## Submitted by Chris Murphy
**[Link to original bug (#763960)](https://bugzilla.gnome.org/show_bug.cgi?id=763960)**
## Description
Created attachment 324391
journal of F24 alpha6 in Boxes (guest)
Host:
virt-manager-1.3.2-1.fc23.no...## Submitted by Chris Murphy
**[Link to original bug (#763960)](https://bugzilla.gnome.org/show_bug.cgi?id=763960)**
## Description
Created attachment 324391
journal of F24 alpha6 in Boxes (guest)
Host:
virt-manager-1.3.2-1.fc23.noarch
libvirt-daemon-1.2.18.2-2.fc23.x86_64
gnome-boxes-3.18.1-1.fc23.x86_64
Problem happens in Boxes with Fedora-Workstation-Live-x86_64-24_Alpha-6.iso but does not happen with Alpha 5. Nor does it happen with either Alpha 5 or Alpha 6 in virt-manager.
At flickering gdm screen, I keep getting a lot of these entries:
Mar 20 16:03:57 localhost.localdomain gnome-settings-daemon.desktop[1560]: (gnome-settings-daemon:1560): color-plugin-WARNING **: unable to get EDID for xrandr-Virtual23: unable to get EDID for output
Mar 20 16:03:58 localhost.localdomain gnome-settings-daemon.desktop[1560]: (gnome-settings-daemon:1560): color-plugin-WARNING **: unable to get EDID for xrandr-Virtual23: unable to get EDID for output
Mar 20 16:03:59 localhost.localdomain gnome-settings-daemon.desktop[1560]: (gnome-settings-daemon:1560): color-plugin-WARNING **: unable to get EDID for xrandr-Virtual23: unable to get EDID for output
Mar 20 16:04:00 localhost.localdomain kernel: qxl 0000:00:02.0: ffff88007a3d0800 unpin not necessary
Mar 20 16:04:00 localhost.localdomain gnome-settings-daemon.desktop[1560]: (gnome-settings-daemon:1560): color-plugin-WARNING **: unable to get EDID for xrandr-Virtual23: unable to get EDID for output
Mar 20 16:04:01 localhost.localdomain gnome-settings-daemon.desktop[1560]: (gnome-settings-daemon:1560): color-plugin-WARNING **: unable to get EDID for xrandr-Virtual23: unable to get EDID for output
Mar 20 16:04:02 localhost.localdomain gnome-settings-daemon.desktop[1560]: (gnome-settings-daemon:1560): color-plugin-WARNING **: unable to get EDID for xrandr-Virtual23: unable to get EDID for output
Mar 20 16:04:03 localhost.localdomain gnome-settings-daemon.desktop[1560]: (gnome-settings-daemon:1560): color-plugin-WARNING **: unable to get EDID for xrandr-Virtual23: unable to get EDID for output
Mar 20 16:04:04 localhost.localdomain gnome-settings-daemon.desktop[1560]: (gnome-settings-daemon:1560): color-plugin-WARNING **: unable to get EDID for xrandr-Virtual23: unable to get EDID for output
Once logging in, there are a lot of messages so I'll just include the entire journal for this boot as an attachment.
Loging attempt starts at monotonic time 129.
**Attachment 324391**, "journal of F24 alpha6 in Boxes (guest)":
[journal.log](/uploads/1c574cb855c654c16bc0edec6301a70f/journal.log)https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/91UI thread freezes when deleting snapshots2018-02-20T13:31:59ZBugzillaUI thread freezes when deleting snapshots## Submitted by Michael Catanzaro `@mcatanzaro`
**[Link to original bug (#763892)](https://bugzilla.gnome.org/show_bug.cgi?id=763892)**
## Description
Today I deleted a bunch of old snapshots I didn't need anymore. After clicking De...## Submitted by Michael Catanzaro `@mcatanzaro`
**[Link to original bug (#763892)](https://bugzilla.gnome.org/show_bug.cgi?id=763892)**
## Description
Today I deleted a bunch of old snapshots I didn't need anymore. After clicking Delete, the UI thread often froze for several seconds; twice I saw it freeze for upwards of 20 seconds before recovering.
Normally it does not freeze, or only freezes for a half second or so.https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/90VNC: features parity with vinagre2018-01-29T17:26:23ZBugzillaVNC: features parity with vinagre## Submitted by Matthias Clasen `@matthiasc`
**[Link to original bug (#763256)](https://bugzilla.gnome.org/show_bug.cgi?id=763256)**
## Description
See the feature comparison in https://wiki.gnome.org/action/edit/Apps/Boxes/Remote
...## Submitted by Matthias Clasen `@matthiasc`
**[Link to original bug (#763256)](https://bugzilla.gnome.org/show_bug.cgi?id=763256)**
## Description
See the feature comparison in https://wiki.gnome.org/action/edit/Apps/Boxes/Remote
Here are vnc connection features I found in remmina:
- readonly mode
- scaling
- compression
- clipboard handling
- quality levels
- color depth
- authentication
- reverse connectionshttps://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/89Allow setting a box name in creation assistant2020-02-03T15:02:59ZBugzillaAllow setting a box name in creation assistant## Submitted by Allan Day `@aday`
**[Link to original bug (#763219)](https://bugzilla.gnome.org/show_bug.cgi?id=763219)**
## Description
I mainly use Boxes to test GNOME continuous images, which means that most of my VMs have very s...## Submitted by Allan Day `@aday`
**[Link to original bug (#763219)](https://bugzilla.gnome.org/show_bug.cgi?id=763219)**
## Description
I mainly use Boxes to test GNOME continuous images, which means that most of my VMs have very similar names after creation. The only way for me to tell them apart is to give them different names, and I often have a name in mind for a VM when I create it. Unfortunately, I am unable to set this name when I create the Box, though, and have to go into the properties after it has been created in order to set the name.
It would be more convenient to be able to set the name as a part of the creation workflow.https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/88RFE: create qcow2 with 'nocow' option when on Btrfs /home2020-10-15T07:52:36ZBugzillaRFE: create qcow2 with 'nocow' option when on Btrfs /home## Submitted by Chris Murphy
**[Link to original bug (#763189)](https://bugzilla.gnome.org/show_bug.cgi?id=763189)**
## Description
Problem: VM images on Btrfs become heavily fragmented, thousands of fragments. In particular, Window...## Submitted by Chris Murphy
**[Link to original bug (#763189)](https://bugzilla.gnome.org/show_bug.cgi?id=763189)**
## Description
Problem: VM images on Btrfs become heavily fragmented, thousands of fragments. In particular, Windows NTFS as a guest on Btrfs is significantly fragmented, tens of thousands of fragments in short order, hundreds of thousands have been reported. This slows things down just as significantly.
Solution: qemu-img supports -o nocow=on which causes xattr 'C' to be set on the file at create time, which makes the file both nodatacow and nodatasum (no Btrfs checksumming). The other option is chattr +C on ~/.local/share/gnome-boxes/ which will cause any images created or copied into that directory to inherit this attribute.
Reference:
https://www.redhat.com/archives/libvir-list/2014-July/msg00361.html
https://btrfs.wiki.kernel.org/index.php/Gotchas#Fragmentation
Examples:
Install Fedora 24 using default installer options (ext4 on LVM), Boxes host /home is on Btrfs. Note this test are all new writes, almost no overwrites; random overwrites make this much worse.
Without +C
-rwxr--r--. 1 chris chris 4679598080 Mar 6 14:59 boxes-unknown
[chris@f23m images]$ filefrag boxes-unknown
boxes-unknown: 4453 extents found
With +C
-rwxr--r--. 1 chris chris 4638703616 Mar 6 15:45 boxes-unknown
[chris@f23m images]$ filefrag boxes-unknown
boxes-unknown: 109 extents found
Argument against the enhancement:
- xattr C means no Btrfs checksumming for the file either
- Kernel code could change and improve this for both VMs and databases; kernel developers are working on this, but for now the recommendation is xattr C.
- Even on openSUSE using Btrfs by default, /home is on XFS by default which isn't affected since it's not a COW fs. So the problem is narrow in scope and the recommendation could just be "set +C on images/ if you want to use Btrfs".
So if there is a very lightweight change to make this better on Btrfs that's also easy to reverse if Btrfs improves, great.https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/86"Troubleshoot" button on "start failed" notification2018-02-01T16:19:34ZBugzilla"Troubleshoot" button on "start failed" notification## Submitted by Zeeshan Ali (Khattak)
**[Link to original bug (#762984)](https://bugzilla.gnome.org/show_bug.cgi?id=762984)**
## Description
The troubleshooting log is pretty hidden currently. It's usually needed when something goes...## Submitted by Zeeshan Ali (Khattak)
**[Link to original bug (#762984)](https://bugzilla.gnome.org/show_bug.cgi?id=762984)**
## Description
The troubleshooting log is pretty hidden currently. It's usually needed when something goes wrong and that typically doesn't happen in properties view but rather in the main view (e.g starting the VM). It would be helpful to provide a button to go to troubleshooting log in failure notifications.https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/85import 3.19.x tested changes2019-12-18T15:46:56ZBugzillaimport 3.19.x tested changes## Submitted by vladimir benes
**[Link to original bug (#762912)](https://bugzilla.gnome.org/show_bug.cgi?id=762912)**
## Description
All these changes are now used in CI and were heavily tested. Tests are slower but more stable. Mo...## Submitted by vladimir benes
**[Link to original bug (#762912)](https://bugzilla.gnome.org/show_bug.cgi?id=762912)**
## Description
All these changes are now used in CI and were heavily tested. Tests are slower but more stable. More reporting is used here and there and some new UI changes are reflected as well.
New Core-7 (aka Core-current) iso is used instead of older 5.x.https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/84graphical issue - HDD size slider glitch - slider gets bold and stops working...2023-03-09T09:30:38ZBugzillagraphical issue - HDD size slider glitch - slider gets bold and stops working when manipulated## Submitted by Paweł
**[Link to original bug (#762883)](https://bugzilla.gnome.org/show_bug.cgi?id=762883)**
## Description
Created attachment 322685
demo of the bug, left mouse clicked on the slider
When I try to change hdd size ...## Submitted by Paweł
**[Link to original bug (#762883)](https://bugzilla.gnome.org/show_bug.cgi?id=762883)**
## Description
Created attachment 322685
demo of the bug, left mouse clicked on the slider
When I try to change hdd size with the slider, it works, but suddenly the blue line gets bold, and the slider stops. Demo on attached recording.
**Attachment 322685**, "demo of the bug, left mouse clicked on the slider":
![boxes-slider-bug](/uploads/239c09220dd676b6449bb29b08b1e42f/boxes-slider-bug.webm)https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/83Add virtio-gpu & virgl, if supported by guest OS2018-12-22T14:22:19ZBugzillaAdd virtio-gpu & virgl, if supported by guest OS## Submitted by Marc-Andre Lureau
**[Link to original bug (#762727)](https://bugzilla.gnome.org/show_bug.cgi?id=762727)**
## Description
This patch is untested.
Assuming your host has all the latest qemu/libvirt/libvirt-glib/osinfo...## Submitted by Marc-Andre Lureau
**[Link to original bug (#762727)](https://bugzilla.gnome.org/show_bug.cgi?id=762727)**
## Description
This patch is untested.
Assuming your host has all the latest qemu/libvirt/libvirt-glib/osinfo/spice-gtk
etc, then this patch should be enough to setup a VM with virgl support.
Most of the required bits are already merged upstream and pending release, the
libvirt/libvirt-glib/osinfo are not yet upstream.https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/82Firefox glitches.2018-12-19T15:55:05ZBugzillaFirefox glitches.## Submitted by Paweł
**[Link to original bug (#762447)](https://bugzilla.gnome.org/show_bug.cgi?id=762447)**
## Description
Created attachment 321830
Screenshot of the issue
I have:
1. Fedora 23, up to date - host
2. Fedora 23 in...## Submitted by Paweł
**[Link to original bug (#762447)](https://bugzilla.gnome.org/show_bug.cgi?id=762447)**
## Description
Created attachment 321830
Screenshot of the issue
I have:
1. Fedora 23, up to date - host
2. Fedora 23 inside Gnome Boxes, up to date - guest
When I visit any webpage with Firefox, on the guest system, page shows many graphical glitches, like:
- showing 4 (or more) smaller pages, instead of normal page - like a splitscreen. Just the page, Firefox ui remains ok.
- showing smaller page in top left corner - probably related to first issue.
- not refreshing new content. I have to "scrach" the old content out, with a mouse pointer, then it shows up, but sometimes not entirely.
The issues change rapidly, especially as I scroll page or just use page menu.
**Attachment 321830**, "Screenshot of the issue":
![glitch](/uploads/20dc5a741e3156e1388099fe1e9cd5a7/glitch.png)https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/81Allow sending file from host to boxes2018-02-05T14:57:53ZBugzillaAllow sending file from host to boxes## Submitted by Victor Toso
**[Link to original bug (#762321)](https://bugzilla.gnome.org/show_bug.cgi?id=762321)**
## Description
Spice has support for shared folders using WebDAV protocol and a simple and stable API for its usage ...## Submitted by Victor Toso
**[Link to original bug (#762321)](https://bugzilla.gnome.org/show_bug.cgi?id=762321)**
## Description
Spice has support for shared folders using WebDAV protocol and a simple and stable API for its usage [0]. The documentation to enable folder sharing with Spice is documented in its manual [1].
[0] http://www.spice-space.org/docs/spice-gtk/SpiceWebdavChannel.html
[1] http://www.spice-space.org/docs/manual/#_folder_sharing
A daemon in the guest is necessary in order to make a good integration with the desktop. In both Linux and Windows, spice-webdavd can be used which is part of Phodav project [2]
[2] https://wiki.gnome.org/phodav
Some UI mockups for Boxes can be found here [3]
[3] https://raw.githubusercontent.com/gnome-design-team/gnome-mockups/master/boxes/wires/file-sharing.png
Remote-viewer can be used as example of client implementing shared folder with Spice like [4] and later patches!
[4] https://github.com/SPICE/virt-viewer/commit/73f70899e4a8fae889d0911096ac0c260baf6702https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/80Can interact with parent window when properties dialog is open2018-02-16T12:28:08ZBugzillaCan interact with parent window when properties dialog is open## Submitted by Allan Day `@aday`
**[Link to original bug (#762182)](https://bugzilla.gnome.org/show_bug.cgi?id=762182)**
## Description
The properties dialog window is modal - it is attached to the parent window, and the parent win...## Submitted by Allan Day `@aday`
**[Link to original bug (#762182)](https://bugzilla.gnome.org/show_bug.cgi?id=762182)**
## Description
The properties dialog window is modal - it is attached to the parent window, and the parent window is shaded. However, you can still interact with the parent window below: you can press the new button in the header bar, and the thumbnails react on hover.
This is odd and creates some surprising interactions. When a dialog window is modal to its parent, you shouldn't be able to interact with that parent until the dialog has been dismissed.