Hi, I have just upgraded to F31 from F30 using dnf system-upgrade download --releasever=31. Before I did the upgrade I updated F30 to the latest maintenance level. When I booted into Gnome on F31 there was no activities menu to be able to launch any application, the only way I could launch applications (if I knew the application command) was to use alt-f2. In F30 I was using dash-to-dock but in the F31 upgrade that failed to start. I did find an entry on the net saying that V66 of dash-to-dock had an issue in F31 with kde (plasma) but no reference to issues with Gnome. I was able to run Gnome-tweaks, see that it was flagging that it couldn't start dash-to-dock, the dash-to-dock settings were saying that it was V66, so I used gnome tweaks to uninstall it. I then used dnfdragora to install V67 of dash-to-dock when confirmed the V67 was installed and V66 wasn't, but when I went back into gnome-tweeks it was still saying that it was trying to start V66 of dash-to-dock. I eventually found that I had to remove all the gnome-shell extension settings in my home path, use dnf to uninstall dash-to-dock V67 and reinstall it for Gnome-tweaks to show that it was successfully able to start dash-to-dock V67. Also after doing this when I launched firefox it immediately asked me asked me if I wanted to update all my extensions from upstream except for dash-to-dock, which I did and that then activated all the extensions even though at update they weren't active. When I launch firefox V73.0a1 it displays with two windows overlapping each other displaying the same contents, forms being displayed on the screen are not displaying correctly in terms of when input is entered into text boxes the input is actually being displayed below the text boxes. Also the address bar keeps flashing on and off because the display of the web page being accessed is intermittently overlaying the address bar, consequently I can't actually select any menus displayed on the web page. Just for interest Thunderbird V73.0a1 doesn't seem to exhibit these issues. If I run the version of firefox from the repositories it exhibits the same overlay issues as well. When I run Gnome-terminal it exhibits the dual window overlay issue when maximised. If I run Gnome-terminal unmaximised it doesn't exhibit the issue, but if I manually expand the size of the gnome-terminal window it exhibits the overlay issue as soon as I type anything into the window. I tried reinstalling Gnome by re-installing the 'Gnome Desktop Environment' group from dnf but that did not make any difference. Does anyone have any ideas what the issue might be? If I run dnf system-upgrade download --releasever=30 will that downgrade me to a fully working version of F30 as it was before I did the F31 upgrade?
regards, Steve
On Tue, 7 Jan 2020 08:24:19 +1100, Stephen Morris wrote:
Hi, I have just upgraded to F31 from F30 using dnf system-upgrade download --releasever=31. Before I did the upgrade I updated F30 to the latest maintenance level. When I booted into Gnome on F31 there was no activities menu to be able to launch any application, the only way I could launch applications (if I knew the application command) was to use alt-f2.
Did you try what happens if you create and use a new user account?
On 7/1/20 09:38, Michael Schwendt wrote:
On Tue, 7 Jan 2020 08:24:19 +1100, Stephen Morris wrote:
Hi, I have just upgraded to F31 from F30 using dnf system-upgrade download --releasever=31. Before I did the upgrade I updated F30 to the latest maintenance level. When I booted into Gnome on F31 there was no activities menu to be able to launch any application, the only way I could launch applications (if I knew the application command) was to use alt-f2.
Did you try what happens if you create and use a new user account?
I created a new account and on that account the Gnome Activities menu is there, but the dual window and web page issue are present on the new account. The issue also appears to not be present on the new account or my existing account under KDE.
regards, Steve
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On 8/1/20 08:07, Stephen Morris wrote:
On 7/1/20 09:38, Michael Schwendt wrote:
On Tue, 7 Jan 2020 08:24:19 +1100, Stephen Morris wrote:
Hi, I have just upgraded to F31 from F30 using dnf system-upgrade download --releasever=31. Before I did the upgrade I updated F30 to the latest maintenance level. When I booted into Gnome on F31 there was no activities menu to be able to launch any application, the only way I could launch applications (if I knew the application command) was to use alt-f2.
Did you try what happens if you create and use a new user account?
I created a new account and on that account the Gnome Activities menu is there, but the dual window and web page issue are present on the new account. The issue also appears to not be present on the new account or my existing account under KDE.
Just further to this, the issue appears to only be in Gnome under Wayland, it does not appear to be present in Gnome under Xorg.
regards, Steve
regards, Steve
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On 8/1/20 08:26, Stephen Morris wrote:
On 8/1/20 08:07, Stephen Morris wrote:
On 7/1/20 09:38, Michael Schwendt wrote:
On Tue, 7 Jan 2020 08:24:19 +1100, Stephen Morris wrote:
Hi, I have just upgraded to F31 from F30 using dnf system-upgrade download --releasever=31. Before I did the upgrade I updated F30 to the latest maintenance level. When I booted into Gnome on F31 there was no activities menu to be able to launch any application, the only way I could launch applications (if I knew the application command) was to use alt-f2.
Did you try what happens if you create and use a new user account?
I created a new account and on that account the Gnome Activities menu is there, but the dual window and web page issue are present on the new account. The issue also appears to not be present on the new account or my existing account under KDE.
Just further to this, the issue appears to only be in Gnome under Wayland, it does not appear to be present in Gnome under Xorg.
I tried a reinstall from scratch of F29 in another VM and upgraded it to F31 and the issue is still there in Gnome under Wayland. If I start Gnome Classic or Gnome on Xorg the issue does not occur.
regards, Steve
regards, Steve
regards, Steve
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On 1/12/20 12:49 PM, Stephen Morris wrote:
On 8/1/20 08:26, Stephen Morris wrote:
On 8/1/20 08:07, Stephen Morris wrote:
On 7/1/20 09:38, Michael Schwendt wrote:
On Tue, 7 Jan 2020 08:24:19 +1100, Stephen Morris wrote:
Hi, I have just upgraded to F31 from F30 using dnf system-upgrade download --releasever=31. Before I did the upgrade I updated F30 to the latest maintenance level. When I booted into Gnome on F31 there was no activities menu to be able to launch any application, the only way I could launch applications (if I knew the application command) was to use alt-f2.
Did you try what happens if you create and use a new user account?
I created a new account and on that account the Gnome Activities menu is there, but the dual window and web page issue are present on the new account. The issue also appears to not be present on the new account or my existing account under KDE.
Just further to this, the issue appears to only be in Gnome under Wayland, it does not appear to be present in Gnome under Xorg.
I tried a reinstall from scratch of F29 in another VM and upgraded it to F31 and the issue is still there in Gnome under Wayland. If I start Gnome Classic or Gnome on Xorg the issue does not occur.
Interesting that it happens in a VM. Does it happen if you do a clean install of F31 directly?
On 2020-01-13 04:49, Stephen Morris wrote:
I tried a reinstall from scratch of F29 in another VM and upgraded it to F31 and the issue is still there in Gnome under Wayland. If I start Gnome Classic or Gnome on Xorg the issue does not occur.
I installed F29 Workstation from the LiveDVD in a QEMU VM. I then updated, installed the dnf upgrade plugin and rebooted. I then did the upgrade from F29 to F31.
Looks fine.
Should I be doing an additional step to try and recreate the issue?
On 13/1/20 08:44, Samuel Sieb wrote:
On 1/12/20 12:49 PM, Stephen Morris wrote:
On 8/1/20 08:26, Stephen Morris wrote:
On 8/1/20 08:07, Stephen Morris wrote:
On 7/1/20 09:38, Michael Schwendt wrote:
On Tue, 7 Jan 2020 08:24:19 +1100, Stephen Morris wrote:
Hi, I have just upgraded to F31 from F30 using dnf system-upgrade download --releasever=31. Before I did the upgrade I updated F30 to the latest maintenance level. When I booted into Gnome on F31 there was no activities menu to be able to launch any application, the only way I could launch applications (if I knew the application command) was to use alt-f2.
Did you try what happens if you create and use a new user account?
I created a new account and on that account the Gnome Activities menu is there, but the dual window and web page issue are present on the new account. The issue also appears to not be present on the new account or my existing account under KDE.
Just further to this, the issue appears to only be in Gnome under Wayland, it does not appear to be present in Gnome under Xorg.
I tried a reinstall from scratch of F29 in another VM and upgraded it to F31 and the issue is still there in Gnome under Wayland. If I start Gnome Classic or Gnome on Xorg the issue does not occur.
Interesting that it happens in a VM. Does it happen if you do a clean install of F31 directly?
I'll download an F31 livedvd and try that.
regards, Steve
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On 13/1/20 11:39, Ed Greshko wrote:
On 2020-01-13 04:49, Stephen Morris wrote:
I tried a reinstall from scratch of F29 in another VM and upgraded it to F31 and the issue is still there in Gnome under Wayland. If I start Gnome Classic or Gnome on Xorg the issue does not occur.
I installed F29 Workstation from the LiveDVD in a QEMU VM. I then updated, installed the dnf upgrade plugin and rebooted. I then did the upgrade from F29 to F31.
Looks fine.
Should I be doing an additional step to try and recreate the issue?
No, that is what I did. The Gnome Terminal displays 2 overlayed windows and only the one that is the bottom of the two accepts input. Firefox displays pages alternating between the page content overlaying the address bar and the address bar overlaying pages, and as a result if the page has menus I can't select the menus. The issue didn't occur in F29 with Wayland. In the vm where I removed my account from sudoers (I've got it back again now) I got these issues under Wayland, but they did not happen with Gnome in Xorg nor with KDE, and not only does it happen with Firefox V72 it also happens with Firefox V74.0a1 which was installed from a tar file in F30. In that image F31 was an upgrade from F30 where these issues were not present. I am running the VM's in Vmware Player V15 which has been updated each time maintenance became available. Also with this issue occurring in the VM with KDE installed, reinstalling Gnome via dnf group install did not rectify the issue, and nor did installing a custom operating system via dnf group install. As a side issue Thunderbird V74.0a1 does not appear to exhibit the issue. One other thing I've just remembered with this issue, if I have the Gnome Terminal or Firefox un-maximised the issue doesn't occur, it only occurs if they are maximised. I don't know if the screen resolution has anything to do with it, the monitor runs at a resolution of 3840x2160, but because I'm in a vm I have to run it at 3840x2075(9:5).
regards, Steve
I
On 2020-01-13 13:08, Stephen Morris wrote:
On 13/1/20 11:39, Ed Greshko wrote:
On 2020-01-13 04:49, Stephen Morris wrote:
I tried a reinstall from scratch of F29 in another VM and upgraded it to F31 and the issue is still there in Gnome under Wayland. If I start Gnome Classic or Gnome on Xorg the issue does not occur.
I installed F29 Workstation from the LiveDVD in a QEMU VM. I then updated, installed the dnf upgrade plugin and rebooted. I then did the upgrade from F29 to F31.
Looks fine.
Should I be doing an additional step to try and recreate the issue?
No, that is what I did. The Gnome Terminal displays 2 overlayed windows and only the one that is the bottom of the two accepts input. Firefox displays pages alternating between the page content overlaying the address bar and the address bar overlaying pages, and as a result if the page has menus I can't select the menus. The issue didn't occur in F29 with Wayland. In the vm where I removed my account from sudoers (I've got it back again now) I got these issues under Wayland, but they did not happen with Gnome in Xorg nor with KDE, and not only does it happen with Firefox V72 it also happens with Firefox V74.0a1 which was installed from a tar file in F30. In that image F31 was an upgrade from F30 where these issues were not present. I am running the VM's in Vmware Player V15 which has been updated each time maintenance became available. Also with this issue occurring in the VM with KDE installed, reinstalling Gnome via dnf group install did not rectify the issue, and nor did installing a custom operating system via dnf group install. As a side issue Thunderbird V74.0a1 does not appear to exhibit the issue. One other thing I've just remembered with this issue, if I have the Gnome Terminal or Firefox un-maximised the issue doesn't occur, it only occurs if they are maximised. I don't know if the screen resolution has anything to do with it, the monitor runs at a resolution of 3840x2160, but because I'm in a vm I have to run it at 3840x2075(9:5).
You're using VMware Player, I'm using virt-manger. VMware Player is not free, is it? Have you asked on the VMware support groups if anyone is seeing that sort of issue? And, have you tried selecting a lower resolution?
Anyway, the max resolution in full-scree mode for my VM's are 2560X1440 (16:9).
On 2020-01-13 13:08, Stephen Morris wrote:
I am running the VM's in Vmware Player V15
Which also leads to the questions....
Your VMware host is running F31/GNOME/Wayland? If so, if you run GNOME/Xorg on the host are the guests still showing the same issues?
And the user account in the guest, it is vanilla? Meaning no changes from the time of creation. No gnome-shell extensions or configuration changes?
On 13/1/20 23:41, Ed Greshko wrote:
On 2020-01-13 13:08, Stephen Morris wrote:
I am running the VM's in Vmware Player V15
Which also leads to the questions....
Your VMware host is running F31/GNOME/Wayland? If so, if you run GNOME/Xorg on the host are the guests still showing the same issues?
And the user account in the guest, it is vanilla? Meaning no changes from the time of creation. No gnome-shell extensions or configuration changes?
Sorry for the slow response, we are getting a kitchen renovation done and the internet is only intermittently available at the moment. Vmware player is free. I haven't asked on the vmware forum yet, I just figured that if it was fine in F30 it would be fine in F31. The host I'm running Vmware player in is Windows 10. The guest in the VM is F31 upgraded from F30 which in turn was upgraded from F29. The user account in the guest I am using does have Gnome-shell extensions installed, but they were installed before the upgrade to F31. The only issue I had with the extensions was with Dash-to-dock, which I had to upgrade to V67 and V66 doesn't work in F31, but even though it was upgraded I had to remove the extension settings from my home folder before Gnome-tweaks would recognise that the version of Dash-to-dock that was actually installed was V67 and not V66 (Gnome-tweaks was continually saying it could load the extension, and when I went into the settings interface the settings were saying it was V66 even though V67 was actually installed and V66 had been manually removed first). To test whether it was an issue with my account, I created a user account for my wife and tried that. This account was a vanilla account with no extensions and no Gnome settings configuration at all. When I booted this account into Gnome with Wayland the issue occurred. With both accounts the issue does not occur if I boot into Gnome with Xorg, and it also doesn't occur if I boot both accounts into KDE. Also to test whether there was an issue with the existing vm, I created a new vm with F29 which was then upgraded to F31. The account defined in this vm was a vanilla account with no changes at all, and this account encountered the issue when booting into Gnome in Wayland. This install also provided entries in the dm for Gnome in Xorg and Gnome Classic, and boot into both of those did not show the issue. I haven't tried downloading an F31 live dvd to install into a vm as yet as I haven't had the internet access and I probably still won't have it for another week.
regards, Steve
On 21/1/20 12:52, Stephen Morris wrote:
On 13/1/20 23:41, Ed Greshko wrote:
On 2020-01-13 13:08, Stephen Morris wrote:
I am running the VM's in Vmware Player V15
Which also leads to the questions....
Your VMware host is running F31/GNOME/Wayland? If so, if you run GNOME/Xorg on the host are the guests still showing the same issues?
And the user account in the guest, it is vanilla? Meaning no changes from the time of creation. No gnome-shell extensions or configuration changes?
Sorry for the slow response, we are getting a kitchen renovation done and the internet is only intermittently available at the moment. Vmware player is free. I haven't asked on the vmware forum yet, I just figured that if it was fine in F30 it would be fine in F31. The host I'm running Vmware player in is Windows 10. The guest in the VM is F31 upgraded from F30 which in turn was upgraded from F29. The user account in the guest I am using does have Gnome-shell extensions installed, but they were installed before the upgrade to F31. The only issue I had with the extensions was with Dash-to-dock, which I had to upgrade to V67 and V66 doesn't work in F31, but even though it was upgraded I had to remove the extension settings from my home folder before Gnome-tweaks would recognise that the version of Dash-to-dock that was actually installed was V67 and not V66 (Gnome-tweaks was continually saying it could load the extension, and when I went into the settings interface the settings were saying it was V66 even though V67 was actually installed and V66 had been manually removed first). To test whether it was an issue with my account, I created a user account for my wife and tried that. This account was a vanilla account with no extensions and no Gnome settings configuration at all. When I booted this account into Gnome with Wayland the issue occurred. With both accounts the issue does not occur if I boot into Gnome with Xorg, and it also doesn't occur if I boot both accounts into KDE. Also to test whether there was an issue with the existing vm, I created a new vm with F29 which was then upgraded to F31. The account defined in this vm was a vanilla account with no changes at all, and this account encountered the issue when booting into Gnome in Wayland. This install also provided entries in the dm for Gnome in Xorg and Gnome Classic, and boot into both of those did not show the issue. I haven't tried downloading an F31 live dvd to install into a vm as yet as I haven't had the internet access and I probably still won't have it for another week.
Sorry, one thing I forgot to mention is this issue seems to only occur when applications are run full screen (maximised). The screen resolution I am running is 3840x2075 due to vm limitations. The actual screen resolution is 3840x2160.
regards, Steve
regards, Steve
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On 2020-01-21 10:04, Stephen Morris wrote:
On 21/1/20 12:52, Stephen Morris wrote:
On 13/1/20 23:41, Ed Greshko wrote:
On 2020-01-13 13:08, Stephen Morris wrote:
I am running the VM's in Vmware Player V15
Which also leads to the questions....
Your VMware host is running F31/GNOME/Wayland? If so, if you run GNOME/Xorg on the host are the guests still showing the same issues?
And the user account in the guest, it is vanilla? Meaning no changes from the time of creation. No gnome-shell extensions or configuration changes?
Sorry for the slow response, we are getting a kitchen renovation done and the internet is only intermittently available at the moment. Vmware player is free. I haven't asked on the vmware forum yet, I just figured that if it was fine in F30 it would be fine in F31. The host I'm running Vmware player in is Windows 10. The guest in the VM is F31 upgraded from F30 which in turn was upgraded from F29. The user account in the guest I am using does have Gnome-shell extensions installed, but they were installed before the upgrade to F31. The only issue I had with the extensions was with Dash-to-dock, which I had to upgrade to V67 and V66 doesn't work in F31, but even though it was upgraded I had to remove the extension settings from my home folder before Gnome-tweaks would recognise that the version of Dash-to-dock that was actually installed was V67 and not V66 (Gnome-tweaks was continually saying it could load the extension, and when I went into the settings interface the settings were saying it was V66 even though V67 was actually installed and V66 had been manually removed first). To test whether it was an issue with my account, I created a user account for my wife and tried that. This account was a vanilla account with no extensions and no Gnome settings configuration at all. When I booted this account into Gnome with Wayland the issue occurred. With both accounts the issue does not occur if I boot into Gnome with Xorg, and it also doesn't occur if I boot both accounts into KDE. Also to test whether there was an issue with the existing vm, I created a new vm with F29 which was then upgraded to F31. The account defined in this vm was a vanilla account with no changes at all, and this account encountered the issue when booting into Gnome in Wayland. This install also provided entries in the dm for Gnome in Xorg and Gnome Classic, and boot into both of those did not show the issue. I haven't tried downloading an F31 live dvd to install into a vm as yet as I haven't had the internet access and I probably still won't have it for another week.
Sorry, one thing I forgot to mention is this issue seems to only occur when applications are run full screen (maximised). The screen resolution I am running is 3840x2075 due to vm limitations. The actual screen resolution is 3840x2160.
Well, I don't think I'm going to be of much help. I don't have a bare-metal Win10 system from which to test.
But, it does sound more like a VMPlayer video driver issue more than anything else.
I've not used VMWare products for several years now. VirtualBox and qemu virtualization are sufficient for my needs.
On 22/1/20 17:44, Ed Greshko wrote:
On 2020-01-21 10:04, Stephen Morris wrote:
On 21/1/20 12:52, Stephen Morris wrote:
On 13/1/20 23:41, Ed Greshko wrote:
On 2020-01-13 13:08, Stephen Morris wrote:
I am running the VM's in Vmware Player V15
Which also leads to the questions....
Your VMware host is running F31/GNOME/Wayland? If so, if you run GNOME/Xorg on the host are the guests still showing the same issues?
And the user account in the guest, it is vanilla? Meaning no changes from the time of creation. No gnome-shell extensions or configuration changes?
Sorry for the slow response, we are getting a kitchen renovation done and the internet is only intermittently available at the moment. Vmware player is free. I haven't asked on the vmware forum yet, I just figured that if it was fine in F30 it would be fine in F31. The host I'm running Vmware player in is Windows 10. The guest in the VM is F31 upgraded from F30 which in turn was upgraded from F29. The user account in the guest I am using does have Gnome-shell extensions installed, but they were installed before the upgrade to F31. The only issue I had with the extensions was with Dash-to-dock, which I had to upgrade to V67 and V66 doesn't work in F31, but even though it was upgraded I had to remove the extension settings from my home folder before Gnome-tweaks would recognise that the version of Dash-to-dock that was actually installed was V67 and not V66 (Gnome-tweaks was continually saying it could load the extension, and when I went into the settings interface the settings were saying it was V66 even though V67 was actually installed and V66 had been manually removed first). To test whether it was an issue with my account, I created a user account for my wife and tried that. This account was a vanilla account with no extensions and no Gnome settings configuration at all. When I booted this account into Gnome with Wayland the issue occurred. With both accounts the issue does not occur if I boot into Gnome with Xorg, and it also doesn't occur if I boot both accounts into KDE. Also to test whether there was an issue with the existing vm, I created a new vm with F29 which was then upgraded to F31. The account defined in this vm was a vanilla account with no changes at all, and this account encountered the issue when booting into Gnome in Wayland. This install also provided entries in the dm for Gnome in Xorg and Gnome Classic, and boot into both of those did not show the issue. I haven't tried downloading an F31 live dvd to install into a vm as yet as I haven't had the internet access and I probably still won't have it for another week.
Sorry, one thing I forgot to mention is this issue seems to only occur when applications are run full screen (maximised). The screen resolution I am running is 3840x2075 due to vm limitations. The actual screen resolution is 3840x2160.
Well, I don't think I'm going to be of much help. I don't have a bare-metal Win10 system from which to test.
But, it does sound more like a VMPlayer video driver issue more than anything else.
I've not used VMWare products for several years now. VirtualBox and qemu virtualization are sufficient for my needs.
Thanks Ed. I think I may have found a pointer to where the issue is. Looking at xorg.0.log for Gnome with Xorg or KDE with Xorg, where the issue doesn't occur, because there is no xorg.conf file Xorg is using a default screen definition for which it is loading driver /usr/lib64/xorg/modules/drivers/vmware_drv.so and /usr/lib64/xorg/modules/drivers/modesetting_drv.so, and from the modelines displayed by the vmware driver the driver does not support the 3840x2075 resolution of the screen, so it is setting the resolution to 800x600. If I then maximise the window Xorg then scales the layout to 3840x2075. This happens both with Gnome and KDE, where everything works fine. It seems to me that Wayland does not properly handle the resolution rescaling. What I don't understand is what has changed in F31 to cause this, as there was no issue in F30.
regards, Steve
On 2020-01-24 18:54, Stephen Morris wrote:
Thanks Ed. I think I may have found a pointer to where the issue is. Looking at xorg.0.log for Gnome with Xorg or KDE with Xorg, where the issue doesn't occur, because there is no xorg.conf file Xorg is using a default screen definition for which it is loading driver /usr/lib64/xorg/modules/drivers/vmware_drv.so and /usr/lib64/xorg/modules/drivers/modesetting_drv.so, and from the modelines displayed by the vmware driver the driver does not support the 3840x2075 resolution of the screen, so it is setting the resolution to 800x600. If I then maximise the window Xorg then scales the layout to 3840x2075. This happens both with Gnome and KDE, where everything works fine. It seems to me that Wayland does not properly handle the resolution rescaling. What I don't understand is what has changed in F31 to cause this, as there was no issue in F30.
Oh, one thing I would do is to actually confirm if wayland is in use. I'm not certain that the VMware video drivers support it.
So, I'd install, if not already installed, inxi and then run "inxi -GxxSMza". The Graphics section will have a line such as...
Display: x11 server: Fedora Project X.org 1.20.6 driver: nvidia
If wayland is in use then you'd see "wayland server".
On 24/1/20 23:31, Ed Greshko wrote:
On 2020-01-24 18:54, Stephen Morris wrote:
Thanks Ed. I think I may have found a pointer to where the issue is. Looking at xorg.0.log for Gnome with Xorg or KDE with Xorg, where the issue doesn't occur, because there is no xorg.conf file Xorg is using a default screen definition for which it is loading driver /usr/lib64/xorg/modules/drivers/vmware_drv.so and /usr/lib64/xorg/modules/drivers/modesetting_drv.so, and from the modelines displayed by the vmware driver the driver does not support the 3840x2075 resolution of the screen, so it is setting the resolution to 800x600. If I then maximise the window Xorg then scales the layout to 3840x2075. This happens both with Gnome and KDE, where everything works fine. It seems to me that Wayland does not properly handle the resolution rescaling. What I don't understand is what has changed in F31 to cause this, as there was no issue in F30.
Oh, one thing I would do is to actually confirm if wayland is in use. I'm not certain that the VMware video drivers support it.
So, I'd install, if not already installed, inxi and then run "inxi -GxxSMza". The Graphics section will have a line such as...
Display: x11 server: Fedora Project X.org 1.20.6 driver: nvidia
If wayland is in use then you'd see "wayland server".
Thanks Ed. I installed and ran that command and it gave me the following output:
Display: wayland server: Fedora Project X.org 1.20.6 driver: vmwgfx
The driver shown is the same driver when running Gnome on Xorg.
The command also showed me the following:
mobo: Intel model: 440BX Desktop Reference Platform
What does this info mean as my motherboard I thought was AMD and not Intel as I'm running an AMD Ryzen cpu?
Just one further question, how do I determine the dimensions of a 'Gnome Terminal' Window? What I have just found is that if I click and hold the bottom right hand corner of the window and scale the window, the issue occurs once I scale past certain dimensions, whereas if I use 'konsole' instead of 'Gnome Terminal' it doesn't matter what dimensions I run 'Konsole' at the issue does not occur.
regards, Steve
On 2020-01-29 10:26, Stephen Morris wrote:
Thanks Ed. I installed and ran that command and it gave me the following output:
Display: wayland server: Fedora Project X.org 1.20.6 driver: vmwgfx
The driver shown is the same driver when running Gnome on Xorg.
The "driver" is not important. vmwgfx is the video driver used by your guest and is the VMWare-gfx driver.
The important thing is "wayland server".
The command also showed me the following:
mobo: Intel model: 440BX Desktop Reference Platform
What does this info mean as my motherboard I thought was AMD and not Intel as I'm running an AMD Ryzen cpu?
Sure.... Remember you're running Fedora in a VMWare Virtual Machine. VMWare is emulating HW. The mobo VMWare emulates is an Intel 440BX.
So, all the HW that inxi reports is emulated HW.
Just one further question, how do I determine the dimensions of a 'Gnome Terminal' Window? What I have just found is that if I click and hold the bottom right hand corner of the window and scale the window, the issue occurs once I scale past certain dimensions, whereas if I use 'konsole' instead of 'Gnome Terminal' it doesn't matter what dimensions I run 'Konsole' at the issue does not occur.
I think you need to be a bit clearer.
When you run konsole, are you running it in the KDE Plasma Destop or the GNOME desktop?
Also, I only keep about 2 weeks of messages from this list on my server so I may have forgotten somethings.
I seem to recall you have both GNOME and KDE desktops installed on F31. So, how about trying one more thing? Instead of using gdm, switch to sddm. sddm being the display manager supplied by KDE. Switch by doing
sudo systemctl --force enable sddm
And then reboot.
The inxi -GxxSMza command will should now show "Display: x11 server".
Then see how your GNOME desktop works.
On 29/1/20 16:23, Ed Greshko wrote:
On 2020-01-29 10:26, Stephen Morris wrote:
Thanks Ed. I installed and ran that command and it gave me the following output:
Display: wayland server: Fedora Project X.org 1.20.6 driver: vmwgfx
The driver shown is the same driver when running Gnome on Xorg.
The "driver" is not important. vmwgfx is the video driver used by your guest and is the VMWare-gfx driver.
The important thing is "wayland server".
The command also showed me the following:
mobo: Intel model: 440BX Desktop Reference Platform
What does this info mean as my motherboard I thought was AMD and not Intel as I'm running an AMD Ryzen cpu?
Sure.... Remember you're running Fedora in a VMWare Virtual Machine. VMWare is emulating HW. The mobo VMWare emulates is an Intel 440BX.
So, all the HW that inxi reports is emulated HW.
Thanks Ed, I wasn't aware it emulated the motherboard as well.
Just one further question, how do I determine the dimensions of a 'Gnome Terminal' Window? What I have just found is that if I click and hold the bottom right hand corner of the window and scale the window, the issue occurs once I scale past certain dimensions, whereas if I use 'konsole' instead of 'Gnome Terminal' it doesn't matter what dimensions I run 'Konsole' at the issue does not occur.
I think you need to be a bit clearer.
When you run konsole, are you running it in the KDE Plasma Destop or the GNOME desktop?
I'm running konsole on the Gnome desktop. It doesn't exhibit the issue when I get a full window when the window is maximised as Gnome terminal does, but if I try to select and text in the window it then exhibits the issue by removing the text I attempted to highlight.
Also, I only keep about 2 weeks of messages from this list on my server so I may have forgotten somethings.
I seem to recall you have both GNOME and KDE desktops installed on F31. So, how about trying one more thing? Instead of using gdm, switch to sddm. sddm being the display manager supplied by KDE. Switch by doing
sudo systemctl --force enable sddm
And then reboot.
The inxi -GxxSMza command will should now show "Display: x11 server".
Then see how your GNOME desktop works.
I forced the swap of display manager and rebooted the system. Inxi -GxxSMaz gave me the following output:
Display: wayland server: Fedora Project X.org 1.20.6 driver: vmware
Even though it is using a different driver the issue still occurs.
I thought the issue might be being caused by setting the font scaling factor in Tweak Tools->Fonts to 1.5, as windows does, but setting it to 1 made no difference to the issue.
regards, Steve
On 2020-01-29 14:48, Stephen Morris wrote:
I forced the swap of display manager and rebooted the system. Inxi -GxxSMaz gave me the following output:
Display: wayland server: Fedora Project X.org 1.20.6 driver: vmware
Even though it is using a different driver the issue still occurs.
That is not what I expected. If anything I was expecting...
Display: x11 server: Fedora Project X.org 1.20.6 driver: vmware
OK.....
Can you switch back to gdm?
systemctl --force enable gdm
Then before you reboot, edit the file
/etc/gdm/custom.conf
To have the line
# Uncomment the line below to force the login screen to use Xorg WaylandEnable=false
And reboot?
Then login to GNOME and see with inxi reports?
On 29/1/20 20:10, Ed Greshko wrote:
On 2020-01-29 14:48, Stephen Morris wrote:
I forced the swap of display manager and rebooted the system. Inxi -GxxSMaz gave me the following output:
Display: wayland server: Fedora Project X.org 1.20.6 driver: vmware
Even though it is using a different driver the issue still occurs.
That is not what I expected. If anything I was expecting...
Display: x11 server: Fedora Project X.org 1.20.6 driver: vmware
Hi Ed, the inxi output I showed above was from selecting the entry 'Gnome' in the dm which is 'Gnome on Wayland'.
If I select the entry 'Gnome on Xorg' then I get the following display which is what you were expecting (which I suspect would also be displayed if I booted into Gnome with Wayland disabled):
Display: x11 server: Fedora Project X.org 1.20.6 driver: vmware unloaded: fbdev,modesetting,vesa compositor: gnome-shell resolution: 3840x2075~60Hz
I haven't switched back to gdm as yet, but I might do so as with the screen size the vm starts up with, the sddm line that normally displays at the bottom of the screen that contains the drop down that provides the desktop selection overlays the row of shutdown icons below the password prompt.
In F30, in order to get KDE to run at the 4k resolution of the monitor, I had to put a modes entry for 3840x2075 into the modes list in xorg.conf. I might add multiple files into /etc/X11/xorg.conf.d for a monitor definition, and a screen definition containing a list of all the modes as well that are shown by xrandr (if I have to I can also specify a list of modelines for all the xrandr resolutions with the modeline specifications provided by gtf), if I need to (a monitor definition file containing a preferredmode of 3840x2075 should be enough to get Xorg to start in that resolution), to see if I can get xorg to start in full screen mode. Currently, if I have the vm window maximised and start up Fedora Xorg starts in 800x600 and it stays that way not filling the maximised window. To get it to fill the maximised window I have to un-maximise the window and then re-maximise it which then causes Xorg to scale to 3840x2075. This won't help Wayland as, from what I have read, there has been a deliberate intent to not provide the Wayland equivalent of xrandr, and I don't know what config files it uses as yet, but at least I'll have Xorg running the way I want it to.
OK.....
Can you switch back to gdm?
systemctl --force enable gdm
Then before you reboot, edit the file
/etc/gdm/custom.conf
To have the line
# Uncomment the line below to force the login screen to use Xorg WaylandEnable=false
Just as a side issue to this, if kdm is still provided, will adding a custom.conf with WaylandEnable=false into /usr/share/config/kdm/Xsetup and for sddm into /usr/share/sddm/scripts/Xsetup do the same thing?
And reboot?
Then login to GNOME and see with inxi reports?
regards, Steve
This might be useless but: I have updated many times successfully until F31. My desktop just wasn't working the same after the F31 upgrade and my oft used productivity shortcuts including Super key weren't working. I spent lots of time checking Tweaks tool etc.
Then I checked the settings (cog) on the login screen. F31 and switched me to use Gnome Classic be default!! I had never made that switch myself. So I switched to Gnome, logged in, and all the familiarity and productivity of Gnome 3 returned. I'm embarrassed by how long it took me to figure it out.
-William
On Mon, Jan 6, 2020 at 2:25 PM Stephen Morris samorris@netspace.net.au wrote:
Hi, I have just upgraded to F31 from F30 using dnf system-upgrade download --releasever=31. Before I did the upgrade I updated F30 to the latest maintenance level. When I booted into Gnome on F31 there was no activities menu to be able to launch any application, the only way I could launch applications (if I knew the application command) was to use alt-f2. In F30 I was using dash-to-dock but in the F31 upgrade that failed to start. I did find an entry on the net saying that V66 of dash-to-dock had an issue in F31 with kde (plasma) but no reference to issues with Gnome. I was able to run Gnome-tweaks, see that it was flagging that it couldn't start dash-to-dock, the dash-to-dock settings were saying that it was V66, so I used gnome tweaks to uninstall it. I then used dnfdragora to install V67 of dash-to-dock when confirmed the V67 was installed and V66 wasn't, but when I went back into gnome-tweeks it was still saying that it was trying to start V66 of dash-to-dock. I eventually found that I had to remove all the gnome-shell extension settings in my home path, use dnf to uninstall dash-to-dock V67 and reinstall it for Gnome-tweaks to show that it was successfully able to start dash-to-dock V67. Also after doing this when I launched firefox it immediately asked me asked me if I wanted to update all my extensions from upstream except for dash-to-dock, which I did and that then activated all the extensions even though at update they weren't active. When I launch firefox V73.0a1 it displays with two windows overlapping each other displaying the same contents, forms being displayed on the screen are not displaying correctly in terms of when input is entered into text boxes the input is actually being displayed below the text boxes. Also the address bar keeps flashing on and off because the display of the web page being accessed is intermittently overlaying the address bar, consequently I can't actually select any menus displayed on the web page. Just for interest Thunderbird V73.0a1 doesn't seem to exhibit these issues. If I run the version of firefox from the repositories it exhibits the same overlay issues as well. When I run Gnome-terminal it exhibits the dual window overlay issue when maximised. If I run Gnome-terminal unmaximised it doesn't exhibit the issue, but if I manually expand the size of the gnome-terminal window it exhibits the overlay issue as soon as I type anything into the window. I tried reinstalling Gnome by re-installing the 'Gnome Desktop Environment' group from dnf but that did not make any difference. Does anyone have any ideas what the issue might be? If I run dnf system-upgrade download --releasever=30 will that downgrade me to a fully working version of F30 as it was before I did the F31 upgrade?
regards, Steve _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On 30/1/20 11:20, Stephen Morris wrote:
On 29/1/20 20:10, Ed Greshko wrote:
On 2020-01-29 14:48, Stephen Morris wrote:
I forced the swap of display manager and rebooted the system. Inxi -GxxSMaz gave me the following output:
Display: wayland server: Fedora Project X.org 1.20.6 driver: vmware
Even though it is using a different driver the issue still occurs.
That is not what I expected. If anything I was expecting...
Display: x11 server: Fedora Project X.org 1.20.6 driver: vmware
Hi Ed, the inxi output I showed above was from selecting the entry 'Gnome' in the dm which is 'Gnome on Wayland'.
If I select the entry 'Gnome on Xorg' then I get the following display which is what you were expecting (which I suspect would also be displayed if I booted into Gnome with Wayland disabled):
Display: x11 server: Fedora Project X.org 1.20.6 driver: vmware unloaded: fbdev,modesetting,vesa compositor: gnome-shell resolution: 3840x2075~60Hz
I haven't switched back to gdm as yet, but I might do so as with the screen size the vm starts up with, the sddm line that normally displays at the bottom of the screen that contains the drop down that provides the desktop selection overlays the row of shutdown icons below the password prompt.
In F30, in order to get KDE to run at the 4k resolution of the monitor, I had to put a modes entry for 3840x2075 into the modes list in xorg.conf. I might add multiple files into /etc/X11/xorg.conf.d for a monitor definition, and a screen definition containing a list of all the modes as well that are shown by xrandr (if I have to I can also specify a list of modelines for all the xrandr resolutions with the modeline specifications provided by gtf), if I need to (a monitor definition file containing a preferredmode of 3840x2075 should be enough to get Xorg to start in that resolution), to see if I can get xorg to start in full screen mode. Currently, if I have the vm window maximised and start up Fedora Xorg starts in 800x600 and it stays that way not filling the maximised window. To get it to fill the maximised window I have to un-maximise the window and then re-maximise it which then causes Xorg to scale to 3840x2075. This won't help Wayland as, from what I have read, there has been a deliberate intent to not provide the Wayland equivalent of xrandr, and I don't know what config files it uses as yet, but at least I'll have Xorg running the way I want it to.
OK.....
Can you switch back to gdm?
systemctl --force enable gdm
Then before you reboot, edit the file
/etc/gdm/custom.conf
To have the line
# Uncomment the line below to force the login screen to use Xorg WaylandEnable=false
Just as a side issue to this, if kdm is still provided, will adding a custom.conf with WaylandEnable=false into /usr/share/config/kdm/Xsetup and for sddm into /usr/share/sddm/scripts/Xsetup do the same thing?
And reboot?
Then login to GNOME and see with inxi reports?
Hi Ed, just further to this, you might be right in saying that it could be the vmware driver not properly supporting Wayland. I have a vm with Mageia installed in it, and if I connect to Gnome on Wayland in that vm I get the same issue. With the location of where the driver is being sourced from, is it likely to be a file supplied by Vmware Tools or is it a file supplied by Fedora?
regards, Steve
regards, Steve _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On 2020-02-01 08:51, Stephen Morris wrote:
Hi Ed, just further to this, you might be right in saying that it could be the vmware driver not properly supporting Wayland. I have a vm with Mageia installed in it, and if I connect to Gnome on Wayland in that vm I get the same issue. With the location of where the driver is being sourced from, is it likely to be a file supplied by Vmware Tools or is it a file supplied by Fedora?
I don't know anything about VMware Player. But this
https://docs.vmware.com/en/VMware-Workstation-Player-for-Windows/15.0/com.vm...
suggests the drivers used are supplied by Vmware Tools.
On 1/2/20 19:50, Ed Greshko wrote:
On 2020-02-01 08:51, Stephen Morris wrote:
Hi Ed, just further to this, you might be right in saying that it could be the vmware driver not properly supporting Wayland. I have a vm with Mageia installed in it, and if I connect to Gnome on Wayland in that vm I get the same issue. With the location of where the driver is being sourced from, is it likely to be a file supplied by Vmware Tools or is it a file supplied by Fedora?
I don't know anything about VMware Player. But this
https://docs.vmware.com/en/VMware-Workstation-Player-for-Windows/15.0/com.vm...
suggests the drivers used are supplied by Vmware Tools.
Thanks Ed. I've had a look the url you provided, and that indicates that the version of Vmware Tools I had installed via the Vmware Player were not the current version, and that Vmware do not supply the current version for linux guests, they require the distribution to supply them which Fedora does via open-vm-tools and open-vm-tools-desktop. When the Vmware tools were originally installed, when the script detected the server (which was the server shown by inxi) it checked the initramfs to see if it needed to be rebuilt, and decided that because there was already a driver for the detected server in the initramfs it did not need to supply one and hence did not need to rebuild the initramfs, so the drivers being used are supplied by Fedora. To upgrade to the latest version of Vmware tools I used the uninstall script from the original install to remove the original tools, and also used dnf to remove the lasest version of the tools because they were installed as well, rebooted the vm, then reinstalled the latest version of the Vmware tools via dnf. Having done this, Wayland still scales to the physical window size when it maximised but it no longer scales to the full resolution, instead of scaling to 3840x2075 as it did previously, it now scales to 3818x2045 (I need to recheck the vertical resolution), but the original issue this thread was raised for is still there.
I have also installed Virtualbox for Windows 10 and done a bit of playing around in that. The issue this thread was raised for seems to not occur in Virtualbox, but with the Virtualbox additions installed by Fedora with the initial Fedora install, Wayland does not scale when the window is maximised. Also at the moment, shared folders in Virtualbox do not appear to work correctly. After the initial install I ran a dnf upgrade which installed a large number of packages (around 700) which included an updated version of Virtualbox additions, but I'm yet to see if anything has changed relative to Wayland and shared folders.
One thing I have noticed with this is Vmware only supports grub2 in legacy mode whereas Virtualbox seems to support grub2 in efi mode, but I am yet to test out if efi is actually supported.
regards, Steve
On 4/2/20 12:12, Stephen Morris wrote:
On 1/2/20 19:50, Ed Greshko wrote:
On 2020-02-01 08:51, Stephen Morris wrote:
Hi Ed, just further to this, you might be right in saying that it could be the vmware driver not properly supporting Wayland. I have a vm with Mageia installed in it, and if I connect to Gnome on Wayland in that vm I get the same issue. With the location of where the driver is being sourced from, is it likely to be a file supplied by Vmware Tools or is it a file supplied by Fedora?
I don't know anything about VMware Player. But this
https://docs.vmware.com/en/VMware-Workstation-Player-for-Windows/15.0/com.vm...
suggests the drivers used are supplied by Vmware Tools.
Thanks Ed. I've had a look the url you provided, and that indicates that the version of Vmware Tools I had installed via the Vmware Player were not the current version, and that Vmware do not supply the current version for linux guests, they require the distribution to supply them which Fedora does via open-vm-tools and open-vm-tools-desktop. When the Vmware tools were originally installed, when the script detected the server (which was the server shown by inxi) it checked the initramfs to see if it needed to be rebuilt, and decided that because there was already a driver for the detected server in the initramfs it did not need to supply one and hence did not need to rebuild the initramfs, so the drivers being used are supplied by Fedora. To upgrade to the latest version of Vmware tools I used the uninstall script from the original install to remove the original tools, and also used dnf to remove the lasest version of the tools because they were installed as well, rebooted the vm, then reinstalled the latest version of the Vmware tools via dnf. Having done this, Wayland still scales to the physical window size when it maximised but it no longer scales to the full resolution, instead of scaling to 3840x2075 as it did previously, it now scales to 3818x2045 (I need to recheck the vertical resolution), but the original issue this thread was raised for is still there.
I have also installed Virtualbox for Windows 10 and done a bit of playing around in that. The issue this thread was raised for seems to not occur in Virtualbox, but with the Virtualbox additions installed by Fedora with the initial Fedora install, Wayland does not scale when the window is maximised. Also at the moment, shared folders in Virtualbox do not appear to work correctly. After the initial install I ran a dnf upgrade which installed a large number of packages (around 700) which included an updated version of Virtualbox additions, but I'm yet to see if anything has changed relative to Wayland and shared folders.
I tried Virtualbox with vm's for every version of Fedora from F29 to F31 and internet access fails in every version. The network gets an IP Address from DHCP and Firefox can access http://www.google.com.au and return results for google searches, but it cannot access the default home page of https://start.fedoraproject.org, nor can dnf refresh any of its repositories. It also doesn't matter what network setting I specify in the VM settings the same thing happens on every one of them. I'm not sure at the moment what the issue is.
regards, Steve
One thing I have noticed with this is Vmware only supports grub2 in legacy mode whereas Virtualbox seems to support grub2 in efi mode, but I am yet to test out if efi is actually supported.
regards, Steve
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On 2020-02-04 17:45, Stephen Morris wrote:
I tried Virtualbox with vm's for every version of Fedora from F29 to F31 and internet access fails in every version. The network gets an IP Address from DHCP and Firefox can access http://www.google.com.au and return results for google searches, but it cannot access the default home page of https://start.fedoraproject.org, nor can dnf refresh any of its repositories. It also doesn't matter what network setting I specify in the VM settings the same thing happens on every one of them. I'm not sure at the moment what the issue is.
Well, you are running VMware Player and VirtualBox as host on Windows 10. And the guest systems are Fedora.
This is opposite of what I, and I suspect others here, are familiar with.
My bare metal systems are all Fedora. I run both VirtualBox and QEMU virtualization without difficulty. Yes, there are some quirks. But those quirks are most likely different if your bare metal system is Windows.
IMO, you probably should seek help from those running virtualization with Windows as the host system.
On 5/2/20 02:20, Ed Greshko wrote:
On 2020-02-04 17:45, Stephen Morris wrote:
I tried Virtualbox with vm's for every version of Fedora from F29 to F31 and internet access fails in every version. The network gets an IP Address from DHCP and Firefox can access http://www.google.com.au and return results for google searches, but it cannot access the default home page of https://start.fedoraproject.org, nor can dnf refresh any of its repositories. It also doesn't matter what network setting I specify in the VM settings the same thing happens on every one of them. I'm not sure at the moment what the issue is.
Well, you are running VMware Player and VirtualBox as host on Windows 10. And the guest systems are Fedora.
This is opposite of what I, and I suspect others here, are familiar with.
My bare metal systems are all Fedora. I run both VirtualBox and QEMU virtualization without difficulty. Yes, there are some quirks. But those quirks are most likely different if your bare metal system is Windows.
IMO, you probably should seek help from those running virtualization with Windows as the host system.
Thanks Ed, I'll see if I can find someone who is running the same setup as me. As a side issue, I had to reinstall vmware and virtualbox as a result of having to reinstall windows because the SSD that is windows drive c died on the weekend. After the reinstall of virtualbox the network issues I had with the original install have disappeared, but the X11 virtualbox video driver supplied by fedora does not support the 4k resolution of my monitor whereas the X11 vmware driver supplied by fedora does. Is this something that can be raised as a bugzilla?
regards, Steve
On 2020-02-12 14:37, Stephen Morris wrote:
Thanks Ed, I'll see if I can find someone who is running the same setup as me. As a side issue, I had to reinstall vmware and virtualbox as a result of having to reinstall windows because the SSD that is windows drive c died on the weekend. After the reinstall of virtualbox the network issues I had with the original install have disappeared, but the X11 virtualbox video driver supplied by fedora does not support the 4k resolution of my monitor whereas the X11 vmware driver supplied by fedora does. Is this something that can be raised as a bugzilla?
AFAIK, and I could be wrong, the driver supplied by fedora is an opensource version of the driver supplied by VMware. Much like nouveau is the opensource of the nVidia driver.
So, sure, you can raise a BZ. But not sure how long it would take, or how much effort would be put into, getting the capability added.
On 12/2/20 17:54, Ed Greshko wrote:
On 2020-02-12 14:37, Stephen Morris wrote:
Thanks Ed, I'll see if I can find someone who is running the same setup as me. As a side issue, I had to reinstall vmware and virtualbox as a result of having to reinstall windows because the SSD that is windows drive c died on the weekend. After the reinstall of virtualbox the network issues I had with the original install have disappeared, but the X11 virtualbox video driver supplied by fedora does not support the 4k resolution of my monitor whereas the X11 vmware driver supplied by fedora does. Is this something that can be raised as a bugzilla?
AFAIK, and I could be wrong, the driver supplied by fedora is an opensource version of the driver supplied by VMware. Much like nouveau is the opensource of the nVidia driver.
So, sure, you can raise a BZ. But not sure how long it would take, or how much effort would be put into, getting the capability added.
It wasn't the vmware driver I was looking at raising the issue on, it was the virtualbox driver not supporting the preferred 4k resolution of the monitor.
regards, Steve
On 12/2/20 17:54, Ed Greshko wrote:
On 2020-02-12 14:37, Stephen Morris wrote:
Thanks Ed, I'll see if I can find someone who is running the same setup as me. As a side issue, I had to reinstall vmware and virtualbox as a result of having to reinstall windows because the SSD that is windows drive c died on the weekend. After the reinstall of virtualbox the network issues I had with the original install have disappeared, but the X11 virtualbox video driver supplied by fedora does not support the 4k resolution of my monitor whereas the X11 vmware driver supplied by fedora does. Is this something that can be raised as a bugzilla?
AFAIK, and I could be wrong, the driver supplied by fedora is an opensource version of the driver supplied by VMware. Much like nouveau is the opensource of the nVidia driver.
You are correct in saying the driver supplied for vmware is open source, but with the advent of Version 11 and onwards of the vmware-tools vmware require users to source and use the vmware-tools supplied by linux distributions, as opposed to a windows guest where vmware still supply the vmware-tools.
regards, Steve
So, sure, you can raise a BZ. But not sure how long it would take, or how much effort would be put into, getting the capability added.
On 2020-02-12 15:08, Stephen Morris wrote:
On 12/2/20 17:54, Ed Greshko wrote:
On 2020-02-12 14:37, Stephen Morris wrote:
Thanks Ed, I'll see if I can find someone who is running the same setup as me. As a side issue, I had to reinstall vmware and virtualbox as a result of having to reinstall windows because the SSD that is windows drive c died on the weekend. After the reinstall of virtualbox the network issues I had with the original install have disappeared, but the X11 virtualbox video driver supplied by fedora does not support the 4k resolution of my monitor whereas the X11 vmware driver supplied by fedora does. Is this something that can be raised as a bugzilla?
AFAIK, and I could be wrong, the driver supplied by fedora is an opensource version of the driver supplied by VMware. Much like nouveau is the opensource of the nVidia driver.
So, sure, you can raise a BZ. But not sure how long it would take, or how much effort would be put into, getting the capability added.
It wasn't the vmware driver I was looking at raising the issue on, it was the virtualbox driver not supporting the preferred 4k resolution of the monitor.
Sorry, I misread your original post.
The VirtualBox tools supplied by Fedora are simply those from Oracle that have been packaged and placed in the repos.
That being said, I have no problems to erase virtualbox-guest-additions supplied by fedora and then run the installer from Oracle to install theirs. I actually find them to work better in that screen resizing works as I expect.
On 12/2/20 18:12, Stephen Morris wrote:
On 12/2/20 17:54, Ed Greshko wrote:
On 2020-02-12 14:37, Stephen Morris wrote:
Thanks Ed, I'll see if I can find someone who is running the same setup as me. As a side issue, I had to reinstall vmware and virtualbox as a result of having to reinstall windows because the SSD that is windows drive c died on the weekend. After the reinstall of virtualbox the network issues I had with the original install have disappeared, but the X11 virtualbox video driver supplied by fedora does not support the 4k resolution of my monitor whereas the X11 vmware driver supplied by fedora does. Is this something that can be raised as a bugzilla?
AFAIK, and I could be wrong, the driver supplied by fedora is an opensource version of the driver supplied by VMware. Much like nouveau is the opensource of the nVidia driver.
You are correct in saying the driver supplied for vmware is open source, but with the advent of Version 11 and onwards of the vmware-tools vmware require users to source and use the vmware-tools supplied by linux distributions, as opposed to a windows guest where vmware still supply the vmware-tools.
In Virtualbox I installed the F31 Astronomy-KDE spin, so in order to get Gnome I did a dnf install of group "Fedora Workstation", and I also did a group install of "KDE Plasma Workspaces" in addition. After the install I logged out and logged back into Gnome on Wayland and the issue is occurring in Virtualbox now as well, which is not surprising as Virtualbox and Vmware seem to be running the same video driver as according to inxi both are running with a driver named "vmware". This driver appears to potentially be the driver from the fedora repositories, as after running the install script from the virtualbox-guest-additions mount point the fedora virtualbox-guest-additions package was installed even though I did not explicitly install it at any point. Having said this, both virtualbox and vmware could be using a driver of the same name and them not be the same physical driver, which if that is the case, given that both have the issue, that would potentially mean the issue is not the driver itself but is actually Wayland itself, or am I jumping to the wrong conclusion?
regards, Steve
regards, Steve
So, sure, you can raise a BZ. But not sure how long it would take, or how much effort would be put into, getting the capability added.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
-
Ed Greshko -
Michael Schwendt -
Samuel Sieb -
Stephen Morris -
William Henry