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 w
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
>>> ha
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 dr
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 driv
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
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
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,
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 c
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
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 t
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
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) o
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 drive
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.
T
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.
T
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
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 defau
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
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
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 F3
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
ar
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
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,
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
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
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 F
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
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
d
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 up
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 mainte
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 Gn
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
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 lau
33 matches
Mail list logo