Re: Fedora 28 persistant printer issue
On Thu, 2019-02-21 at 10:50 -0800, Howard Howell wrote: > On Wed, 2019-02-20 at 11:52 -0800, Samuel Sieb wrote: > > On 2/20/19 9:23 AM, Howard Howell wrote: > > > That didn't go well at all I dnf installed system-config- > > > firewall > > > and invoked it as sudo system-config-firewall: > > > > system-config-firewall is the old way for configuring iptables. If > > you're running firewalld, you need "firewall-config". Also, you > > can't > > run applications as root under Wayland, that's why you got the error. > > > Thanks, Samuel, > Got firewall-config up and running. > I will never understand how things evolve so rapidly and in > such arbitrary ways One of the delights of using Fedora. If you want a quiet life, maybe try a different distro :-) > ... Guess I'm getting old. We all are ... poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Fedora 28 persistant printer issue
On Wed, 2019-02-20 at 11:52 -0800, Samuel Sieb wrote: > On 2/20/19 9:23 AM, Howard Howell wrote: > > That didn't go well at all I dnf installed system-config- > > firewall > > and invoked it as sudo system-config-firewall: > > system-config-firewall is the old way for configuring iptables. If > you're running firewalld, you need "firewall-config". Also, you > can't > run applications as root under Wayland, that's why you got the error. > Thanks, Samuel, Got firewall-config up and running. I will never understand how things evolve so rapidly and in such arbitrary ways... Guess I'm getting old. Regards, Les H ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: how now to set ibus (Intelligent Pinyin) font. [SOLVED]
ok, here's the solution in Gnome... 1. install "gnome-shell-extension-ibus-font", which I did from the command line: dnf install gnome-shell-extension-ibus-font 2. run "gnome-shell-extension-prefs", which I did from the command line: gnome-shell-extension-prefs This launches a GUI. Scroll down to the line "ibus-font-setting". Turn it on. Click the gear to see the current font setting. It launches a second GUI showing the current font setting. If you want another font, click the current font name. That brings up a third GUI with a menu of available fonts. Choose the one you want. Click the Select button; that closes the third GUI. Close the ibus font setting GUI. Close the Shell Extensions GUI. That should do it. Things do seem to be working as desired in KDE also. No new bug was needed. Thank-you Ed and Peng for your help. I'm marking this thread "SOLVED". ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: dnf install from list file
On Thu, 21 Feb 2019 15:36:08 +0100 "Patrick Dupre" wrote: > How can I make a dnf install "list of pkgs in a file"? > > I tried dnf install `file` > > but it does not work. I usually use a python script to read the file and run dnf in a subprocess for each package. That way, a single problem doesn't stop the whole update. I haven't tried these, so I don't know if they work, but you could try dnf update < $(cat file) or cat file | xargs dnf update Because I haven't tried them, there may be syntax or grammar errors in the commands. The first should treat the file as a group, and will be faster if there are no dependency errors. The second should do each package individually, so will be slower but error tolerant. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: dnf install from list file
dnf install `cat file` On Thu, Feb 21, 2019 at 9:02 AM stan via users wrote: > > On Thu, 21 Feb 2019 15:36:08 +0100 > "Patrick Dupre" wrote: > > > How can I make a dnf install "list of pkgs in a file"? > > > > I tried dnf install `file` > > > > but it does not work. > > I usually use a python script to read the file and run dnf in a > subprocess for each package. That way, a single problem doesn't stop > the whole update. > > I haven't tried these, so I don't know if they work, but you could try > dnf update < $(cat file) > or > cat file | xargs dnf update > > Because I haven't tried them, there may be syntax or grammar errors in > the commands. The first should treat the file as a group, and will be > faster if there are no dependency errors. The second should do each > package individually, so will be slower but error tolerant. > > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > 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-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: dnf install from list file
As long as you're sure you want to install all of those packages then: # cat 'file' | xargs dnf -y install should do it. You have to do the -y because dnf will just exit if you don't. You can't run an interactive prompt... Thanks, Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
dnf install from list file
Hello, How can I make a dnf install "list of pkgs in a file"? I tried dnf install `file` but it does not work. Thank === Patrick DUPRÉ | | email: pdu...@gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988 === ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: Email Question - OT
On Wed, 2019-02-20 at 13:09 -0800, Mike Wright wrote: > [snip] > You didn't have a dns delegation-of-authority which allows you to > claim > control or the mail server's reverse dns address and showing you're > not > some fly-by-night spammer or some such. > > If your were to dig for the PTR record for the mailserver's IP you > would > get back something like 75-25-207-10.lightspeed.sjcpca.sbcglobal.net > that indicates who is currently in charge of that IP. If you had > the > delegation-of-authority it would return YOUR mailserver's name. > > e.g. > 1st record shows name of mailserver for your domain > 2nd record shows address of mailserver > 3rd record ties the mailserver's address to it's IP > > forward dns: yourchurch.org IN MX mx.yourchurch.org > forward dns: mx.yourchurch.org IN A 192.168.10.20 > reverse dns: 20.10.168.192.in-addr.arpa IN PTR mx.yourchurch.org > > The delegations are usually available from your ISP if you're > persistent > and may come with a monthly fee. AT&T used to charge me $5 US but > raised it to $15 because they could. Good bye AT&T, hello Digital > Ocean: $5 for a basic server includes a delegated authority record. > > Yes! Now that you mention it, that's the buzzword I was blanking on. My mistake was that I thought that the delegation of authority was a configuration issue and I kept trying different ways of assigning it to myself in the bind configuration files and nothing worked. I got to that horrible point of just making random changes in random configuration files just to see if anything would change, and then gave up. I completely missed that I had to go to the ISP to get it. Sigh. That's part of my life I'll never get back. billo ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: New install
On Thu, Feb 21, 2019 at 6:09 AM Patrick Dupre wrote: > The issue is solved. > Because I did not boot on the SUB live in UEFI, the install was not > compatible with a UEFI > boot. > > Sorry for the disturbance. > It's not intuitive! But that was going to be my next question, glad you figured it out. Thanks, Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: KDE Desktop Environment Doesn't Boot After Installer Puts Entry in Desktop Manager in F29
On Thu, 2019-02-21 at 23:00 +1100, Stephen Morris wrote: > Putting the following section in xorg.conf caused Gnome under Xorg to > start with the resolution of the Maximized vmware player, which was > 1600x844, as desired. KDE did not start at the resolution of 1600x844, > instead starting at 640x480, but the display configuration facility > including 1600x844 as one of the resolutions it now provided, which then > switched KDE into the desired resolution. > > > Section "Monitor" > Identifier "Monitor0" > VendorName "Unknown" > ModelName "Unknown" > # HorizSync 28.0 - 33.0 > # VertRefresh 43.0 - 72.0 > Modeline "1600x844_60.00" 110.75 1600 1696 1856 2112 844 > 847 857 876 -hsync +vsync > Option "PreferredMode" "1600x844_60.00" > Option "DPMS" > EndSection Glad it worked out. Note that if you actually want to use the Nvidia card to its full capability within a VM, you need to use GPU passthrough. AFAIK this currently cannot be done in VMware or Virtual Box, only on KVM/QEMU. It's something of a hassle to set up and depends on certain features of your motherboard and BIOS, but I use it to run Windows games and it works very well. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: KDE Desktop Environment Doesn't Boot After Installer Puts Entry in Desktop Manager in F29
On Thu, 2019-02-21 at 22:32 +1100, Stephen Morris wrote: > On 21/2/19 9:48 pm, Ed Greshko wrote: > > On 2/21/19 6:43 PM, Patrick O'Callaghan wrote: > > > On Thu, 2019-02-21 at 20:29 +1100, Stephen Morris wrote: > > > > On 21/2/19 6:47 am, Samuel Sieb wrote: > > > > > On 2/20/19 1:02 AM, Stephen Morris wrote: > > > > > > lspci provides the following output for the device: > > > > > > > > > > > > 00:0f.0 VGA compatible controller: VMware SVGA II Adapter > > > > > As Patrick pointed out, this is clearly not an NVidia device. You can > > > > > find out which driver is actually handling it, by running "lspci -v". > > > > > There will be a line with "Kernel driver in use:". > > > > > > > > > "lspci -v" gives me the following output: > > > > > > > > > > > > 00:0f.0 VGA compatible controller: VMware SVGA II Adapter (prog-if 00 > > > > [VGA controller]) > > > > Subsystem: VMware SVGA II Adapter > > > > Flags: bus master, medium devsel, latency 64, IRQ 16 > > > > I/O ports at 1070 [size=16] > > > > Memory at e800 (32-bit, prefetchable) [size=128M] > > > > Memory at fe00 (32-bit, non-prefetchable) [size=8M] > > > > [virtual] Expansion ROM at 000c [disabled] [size=128K] > > > > Capabilities: > > > > Kernel driver in use: vmwgfx > > > > Kernel modules: vmwgfx > > > > > > > > This output is under Wayland. I have previously installed the nvidia > > > > proprietary driver from Negativo17 via dkms, and from what I can see > > > > from the Xorg log, Xorg is loading that driver and the corresponding glx > > > > module just before the message that Xorg can't find any display devices > > > > to use. > > > > > > > > I also checked the xorg.conf file and it specifies to use the nvidia > > > > driver, should I change it to the above driver or is the above driver > > > > unique to Wayland? > > > The driver has nothing to do with Wayland as such. Clearly an Nvidia > > > driver isn't going to work with a non-Nvidia GPU, which is what your VM > > > has. If you're loading the Nvidia driver anyway, this may be the source > > > of the problem. Remove the Nvidia stuff and try again. > > > > > Kernel driver in use: vmwgfx > > > > vmwgfx is VMWare guest GL driver > > > > If it were nVidia it would read > > > > Kernel driver in use: nvidia > > I have tried removing the nvidia entries from the device group in > xorg.conf, and, also specifying driver "vmware" instead of "nvidia", and > in both cases Gnome and KDE can be started with Xorg. I would uninstall the Nvidia support completely to be on the safe side (i.e. remove the package or at least blacklist the kernel module), but that may not be necessary. > In both cases > though they start with the wrong screen resolution relative to the > resolution that the vmware player is using. Gnome under Wayland is > capable of re-setting its resolution to match that of the vmware player > when maximizing the player, but KDE is not capable of doing so under > Wayland. I might have to play around with the resolution configuration > parameters to try to get Xorg to set its resolution to match vmware's. I use KDE under X as currently Wayland support for KDE is running behind Gnome. You may want to ask on the KDE list for more information. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: New install
The issue is solved. Because I did not boot on the SUB live in UEFI, the install was not compatible with a UEFI boot. Sorry for the disturbance.___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: KDE Desktop Environment Doesn't Boot After Installer Puts Entry in Desktop Manager in F29
On 21/2/19 10:32 pm, Stephen Morris wrote: On 21/2/19 9:48 pm, Ed Greshko wrote: On 2/21/19 6:43 PM, Patrick O'Callaghan wrote: On Thu, 2019-02-21 at 20:29 +1100, Stephen Morris wrote: On 21/2/19 6:47 am, Samuel Sieb wrote: On 2/20/19 1:02 AM, Stephen Morris wrote: lspci provides the following output for the device: 00:0f.0 VGA compatible controller: VMware SVGA II Adapter As Patrick pointed out, this is clearly not an NVidia device. You can find out which driver is actually handling it, by running "lspci -v". There will be a line with "Kernel driver in use:". "lspci -v" gives me the following output: 00:0f.0 VGA compatible controller: VMware SVGA II Adapter (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter Flags: bus master, medium devsel, latency 64, IRQ 16 I/O ports at 1070 [size=16] Memory at e800 (32-bit, prefetchable) [size=128M] Memory at fe00 (32-bit, non-prefetchable) [size=8M] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: Kernel driver in use: vmwgfx Kernel modules: vmwgfx This output is under Wayland. I have previously installed the nvidia proprietary driver from Negativo17 via dkms, and from what I can see from the Xorg log, Xorg is loading that driver and the corresponding glx module just before the message that Xorg can't find any display devices to use. I also checked the xorg.conf file and it specifies to use the nvidia driver, should I change it to the above driver or is the above driver unique to Wayland? The driver has nothing to do with Wayland as such. Clearly an Nvidia driver isn't going to work with a non-Nvidia GPU, which is what your VM has. If you're loading the Nvidia driver anyway, this may be the source of the problem. Remove the Nvidia stuff and try again. Kernel driver in use: vmwgfx vmwgfx is VMWare guest GL driver If it were nVidia it would read Kernel driver in use: nvidia I have tried removing the nvidia entries from the device group in xorg.conf, and, also specifying driver "vmware" instead of "nvidia", and in both cases Gnome and KDE can be started with Xorg. In both cases though they start with the wrong screen resolution relative to the resolution that the vmware player is using. Gnome under Wayland is capable of re-setting its resolution to match that of the vmware player when maximizing the player, but KDE is not capable of doing so under Wayland. I might have to play around with the resolution configuration parameters to try to get Xorg to set its resolution to match vmware's. Putting the following section in xorg.conf caused Gnome under Xorg to start with the resolution of the Maximized vmware player, which was 1600x844, as desired. KDE did not start at the resolution of 1600x844, instead starting at 640x480, but the display configuration facility including 1600x844 as one of the resolutions it now provided, which then switched KDE into the desired resolution. Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "Unknown" # HorizSync 28.0 - 33.0 # VertRefresh 43.0 - 72.0 Modeline "1600x844_60.00" 110.75 1600 1696 1856 2112 844 847 857 876 -hsync +vsync Option "PreferredMode" "1600x844_60.00" Option "DPMS" EndSection regards, Steve regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html 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-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: KDE Desktop Environment Doesn't Boot After Installer Puts Entry in Desktop Manager in F29
On 21/2/19 9:48 pm, Ed Greshko wrote: On 2/21/19 6:43 PM, Patrick O'Callaghan wrote: On Thu, 2019-02-21 at 20:29 +1100, Stephen Morris wrote: On 21/2/19 6:47 am, Samuel Sieb wrote: On 2/20/19 1:02 AM, Stephen Morris wrote: lspci provides the following output for the device: 00:0f.0 VGA compatible controller: VMware SVGA II Adapter As Patrick pointed out, this is clearly not an NVidia device. You can find out which driver is actually handling it, by running "lspci -v". There will be a line with "Kernel driver in use:". "lspci -v" gives me the following output: 00:0f.0 VGA compatible controller: VMware SVGA II Adapter (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter Flags: bus master, medium devsel, latency 64, IRQ 16 I/O ports at 1070 [size=16] Memory at e800 (32-bit, prefetchable) [size=128M] Memory at fe00 (32-bit, non-prefetchable) [size=8M] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: Kernel driver in use: vmwgfx Kernel modules: vmwgfx This output is under Wayland. I have previously installed the nvidia proprietary driver from Negativo17 via dkms, and from what I can see from the Xorg log, Xorg is loading that driver and the corresponding glx module just before the message that Xorg can't find any display devices to use. I also checked the xorg.conf file and it specifies to use the nvidia driver, should I change it to the above driver or is the above driver unique to Wayland? The driver has nothing to do with Wayland as such. Clearly an Nvidia driver isn't going to work with a non-Nvidia GPU, which is what your VM has. If you're loading the Nvidia driver anyway, this may be the source of the problem. Remove the Nvidia stuff and try again. Kernel driver in use: vmwgfx vmwgfx is VMWare guest GL driver If it were nVidia it would read Kernel driver in use: nvidia I have tried removing the nvidia entries from the device group in xorg.conf, and, also specifying driver "vmware" instead of "nvidia", and in both cases Gnome and KDE can be started with Xorg. In both cases though they start with the wrong screen resolution relative to the resolution that the vmware player is using. Gnome under Wayland is capable of re-setting its resolution to match that of the vmware player when maximizing the player, but KDE is not capable of doing so under Wayland. I might have to play around with the resolution configuration parameters to try to get Xorg to set its resolution to match vmware's. regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: KDE Desktop Environment Doesn't Boot After Installer Puts Entry in Desktop Manager in F29
On 2/21/19 6:43 PM, Patrick O'Callaghan wrote: > On Thu, 2019-02-21 at 20:29 +1100, Stephen Morris wrote: >> On 21/2/19 6:47 am, Samuel Sieb wrote: >>> On 2/20/19 1:02 AM, Stephen Morris wrote: lspci provides the following output for the device: 00:0f.0 VGA compatible controller: VMware SVGA II Adapter >>> As Patrick pointed out, this is clearly not an NVidia device. You can >>> find out which driver is actually handling it, by running "lspci -v". >>> There will be a line with "Kernel driver in use:". >>> >> "lspci -v" gives me the following output: >> >> >> 00:0f.0 VGA compatible controller: VMware SVGA II Adapter (prog-if 00 >> [VGA controller]) >> Subsystem: VMware SVGA II Adapter >> Flags: bus master, medium devsel, latency 64, IRQ 16 >> I/O ports at 1070 [size=16] >> Memory at e800 (32-bit, prefetchable) [size=128M] >> Memory at fe00 (32-bit, non-prefetchable) [size=8M] >> [virtual] Expansion ROM at 000c [disabled] [size=128K] >> Capabilities: >> Kernel driver in use: vmwgfx >> Kernel modules: vmwgfx >> >> This output is under Wayland. I have previously installed the nvidia >> proprietary driver from Negativo17 via dkms, and from what I can see >> from the Xorg log, Xorg is loading that driver and the corresponding glx >> module just before the message that Xorg can't find any display devices >> to use. >> >> I also checked the xorg.conf file and it specifies to use the nvidia >> driver, should I change it to the above driver or is the above driver >> unique to Wayland? > The driver has nothing to do with Wayland as such. Clearly an Nvidia > driver isn't going to work with a non-Nvidia GPU, which is what your VM > has. If you're loading the Nvidia driver anyway, this may be the source > of the problem. Remove the Nvidia stuff and try again. > Kernel driver in use: vmwgfx vmwgfx is VMWare guest GL driver If it were nVidia it would read Kernel driver in use: nvidia -- Right: I dislike the default color scheme Wrong: What idiot picked the default color scheme ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: KDE Desktop Environment Doesn't Boot After Installer Puts Entry in Desktop Manager in F29
On Thu, 2019-02-21 at 20:29 +1100, Stephen Morris wrote: > On 21/2/19 6:47 am, Samuel Sieb wrote: > > On 2/20/19 1:02 AM, Stephen Morris wrote: > > > lspci provides the following output for the device: > > > > > > 00:0f.0 VGA compatible controller: VMware SVGA II Adapter > > > > As Patrick pointed out, this is clearly not an NVidia device. You can > > find out which driver is actually handling it, by running "lspci -v". > > There will be a line with "Kernel driver in use:". > > > "lspci -v" gives me the following output: > > > 00:0f.0 VGA compatible controller: VMware SVGA II Adapter (prog-if 00 > [VGA controller]) > Subsystem: VMware SVGA II Adapter > Flags: bus master, medium devsel, latency 64, IRQ 16 > I/O ports at 1070 [size=16] > Memory at e800 (32-bit, prefetchable) [size=128M] > Memory at fe00 (32-bit, non-prefetchable) [size=8M] > [virtual] Expansion ROM at 000c [disabled] [size=128K] > Capabilities: > Kernel driver in use: vmwgfx > Kernel modules: vmwgfx > > This output is under Wayland. I have previously installed the nvidia > proprietary driver from Negativo17 via dkms, and from what I can see > from the Xorg log, Xorg is loading that driver and the corresponding glx > module just before the message that Xorg can't find any display devices > to use. > > I also checked the xorg.conf file and it specifies to use the nvidia > driver, should I change it to the above driver or is the above driver > unique to Wayland? The driver has nothing to do with Wayland as such. Clearly an Nvidia driver isn't going to work with a non-Nvidia GPU, which is what your VM has. If you're loading the Nvidia driver anyway, this may be the source of the problem. Remove the Nvidia stuff and try again. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: A fontpath question. (Samuel Sieb)
On Thu, 2019-02-21 at 07:50 +, George R Goffe via users wrote: > BTW, this release of Fedora is FC30 x86_64 There is no FC30 (or F30 which is what it would in due course be called) unless it's Rawhide, in which case this is really a question for the Fedora Test list. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: New install
One though, When I installed fedora from the USB stick, I had to boot without UEFI, because the bios did not recognize the stick as providing a UEFI mounting point. Could have been a problem? However, on the key, I have /boot/efi I also checked (from the fedora live when mounted on /mnt/linux) df -h --local | grep /boot /dev/sdb4 477M 151M 298M 34% /mnt/linux/boot but I have ls /mnt/linux/boot config-4.16.3-301.fc28.x86_64 initramfs-0-rescue-5b77b2954d4149beab535546c82f45a0.img System.map-4.16.3-301.fc28.x86_64 efi initramfs-4.16.3-301.fc28.x86_64.img vmlinuz-0-rescue-5b77b2954d4149beab535546c82f45a0 elf-memtest86+-5.01 loader vmlinuz-4.16.3-301.fc28.x86_64 extlinux lost+found grub2 memtest86+-5.01 chroot /mnt/linux Error, do this: mount -t proc proc /proc /usr/bin/basename: missing operand Try '/usr/bin/basename --help' for more information. Error, do this: mount -t proc proc /proc /bin/basename: missing operand Try '/bin/basename --help' for more information. Hello, I guess that the issue comme from: efibootmgr /dev/sdb EFI variables are not supported on this system. The fstab seems OK as well as the /boot/efi === Patrick DUPRÉ | | email: pdu...@gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988 === Sent: Wednesday, February 20, 2019 at 2:27 PM From: "Richard Shaw" To: "Community support for Fedora users" Subject: Re: New install I was temporarily not able to ssh into my home machine, but here's some examples of what you should see for a UEFI install: $ sudo parted -l ... Model: NVMe Device (nvme) Disk /dev/nvme0n1: 500GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1049kB 211MB 210MB fat16 EFI System Partition boot, esp 2 211MB 1285MB 1074MB ext4 3 1285MB 500GB 499GB lvm Ok, so parted it showing my ESP partition as fat16, not fat32 and it has the "boot" and "esp" flags turned on. # cat /etc/fstab | grep boot UUID=ed603fce-d39e-425a-8153-6c39c04162f5 /boot ext4 defaults 1 2 UUID=76C7-6578 /boot/efi vfat umask=0077 0 2 Here you can see partition with the UUID=76C7-6578 label (which is my EFI partition) mounted to /boot/efi. Hope that helps! Boot using your live USB. You can also try running efibootmgr and see if you get the correct response... $ sudo efibootmgr BootCurrent: 0001 Timeout: 1 seconds BootOrder: 0001,0002,0003 Boot0001* Fedora Boot0002* CD/DVD Drive Boot0003* Hard Drive Thanks, Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html 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-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html 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-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html 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-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: New install
I also checked (from the fedora live when mounted on /mnt/linux) df -h --local | grep /boot /dev/sdb4 477M 151M 298M 34% /mnt/linux/boot but I have ls /mnt/linux/boot config-4.16.3-301.fc28.x86_64 initramfs-0-rescue-5b77b2954d4149beab535546c82f45a0.img System.map-4.16.3-301.fc28.x86_64 efi initramfs-4.16.3-301.fc28.x86_64.img vmlinuz-0-rescue-5b77b2954d4149beab535546c82f45a0 elf-memtest86+-5.01 loader vmlinuz-4.16.3-301.fc28.x86_64 extlinux lost+found grub2 memtest86+-5.01 chroot /mnt/linux Error, do this: mount -t proc proc /proc /usr/bin/basename: missing operand Try '/usr/bin/basename --help' for more information. Error, do this: mount -t proc proc /proc /bin/basename: missing operand Try '/bin/basename --help' for more information. Hello, I guess that the issue comme from: efibootmgr /dev/sdb EFI variables are not supported on this system. The fstab seems OK as well as the /boot/efi === Patrick DUPRÉ | | email: pdu...@gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988 === Sent: Wednesday, February 20, 2019 at 2:27 PM From: "Richard Shaw" To: "Community support for Fedora users" Subject: Re: New install I was temporarily not able to ssh into my home machine, but here's some examples of what you should see for a UEFI install: $ sudo parted -l ... Model: NVMe Device (nvme) Disk /dev/nvme0n1: 500GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1049kB 211MB 210MB fat16 EFI System Partition boot, esp 2 211MB 1285MB 1074MB ext4 3 1285MB 500GB 499GB lvm Ok, so parted it showing my ESP partition as fat16, not fat32 and it has the "boot" and "esp" flags turned on. # cat /etc/fstab | grep boot UUID=ed603fce-d39e-425a-8153-6c39c04162f5 /boot ext4 defaults 1 2 UUID=76C7-6578 /boot/efi vfat umask=0077 0 2 Here you can see partition with the UUID=76C7-6578 label (which is my EFI partition) mounted to /boot/efi. Hope that helps! Boot using your live USB. You can also try running efibootmgr and see if you get the correct response... $ sudo efibootmgr BootCurrent: 0001 Timeout: 1 seconds BootOrder: 0001,0002,0003 Boot0001* Fedora Boot0002* CD/DVD Drive Boot0003* Hard Drive Thanks, Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html 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-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html 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-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: New install
Hello, I guess that the issue comme from: efibootmgr /dev/sdb EFI variables are not supported on this system. The fstab seems OK as well as the /boot/efi === Patrick DUPRÉ | | email: pdu...@gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988 === Sent: Wednesday, February 20, 2019 at 2:27 PM From: "Richard Shaw" To: "Community support for Fedora users" Subject: Re: New install I was temporarily not able to ssh into my home machine, but here's some examples of what you should see for a UEFI install: $ sudo parted -l ... Model: NVMe Device (nvme) Disk /dev/nvme0n1: 500GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 1 1049kB 211MB 210MB fat16 EFI System Partition boot, esp 2 211MB 1285MB 1074MB ext4 3 1285MB 500GB 499GB lvm Ok, so parted it showing my ESP partition as fat16, not fat32 and it has the "boot" and "esp" flags turned on. # cat /etc/fstab | grep boot UUID=ed603fce-d39e-425a-8153-6c39c04162f5 /boot ext4 defaults 1 2 UUID=76C7-6578 /boot/efi vfat umask=0077 0 2 Here you can see partition with the UUID=76C7-6578 label (which is my EFI partition) mounted to /boot/efi. Hope that helps! Boot using your live USB. You can also try running efibootmgr and see if you get the correct response... $ sudo efibootmgr BootCurrent: 0001 Timeout: 1 seconds BootOrder: 0001,0002,0003 Boot0001* Fedora Boot0002* CD/DVD Drive Boot0003* Hard Drive Thanks, Richard ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html 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-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
block size
parted -l Model: ATA SK hynix SC311 S (scsi) Disk /dev/sdb: 512GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: pmbr_boot Number Start End SizeFile system Name Flags 1 1049kB 787MB 786MB fat32 EFI system partition boot, esp 2 787MB 6156MB 5369MB fat32 Basic data partition msftres 3 6156MB 39.7GB 33.6GB linux-swap(v1)swap 4 39.7GB 40.2GB 524MB ext4Boot0 5 40.2GB 145GB 105GB VolSys0 lvm 6 145GB 250GB 105GB VolUsrlvm 7 250GB 250GB 524MB ext4Boot1 8 250GB 355GB 105GB VolSys1 lvm 9 355GB 460GB 105GB ext4Backup0 Warning: The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes. Ignore/Cancel? What should I do? === Patrick DUPRÉ | | email: pdu...@gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988 === ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: KDE Desktop Environment Doesn't Boot After Installer Puts Entry in Desktop Manager in F29
On 21/2/19 6:47 am, Samuel Sieb wrote: On 2/20/19 1:02 AM, Stephen Morris wrote: lspci provides the following output for the device: 00:0f.0 VGA compatible controller: VMware SVGA II Adapter As Patrick pointed out, this is clearly not an NVidia device. You can find out which driver is actually handling it, by running "lspci -v". There will be a line with "Kernel driver in use:". "lspci -v" gives me the following output: 00:0f.0 VGA compatible controller: VMware SVGA II Adapter (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter Flags: bus master, medium devsel, latency 64, IRQ 16 I/O ports at 1070 [size=16] Memory at e800 (32-bit, prefetchable) [size=128M] Memory at fe00 (32-bit, non-prefetchable) [size=8M] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: Kernel driver in use: vmwgfx Kernel modules: vmwgfx This output is under Wayland. I have previously installed the nvidia proprietary driver from Negativo17 via dkms, and from what I can see from the Xorg log, Xorg is loading that driver and the corresponding glx module just before the message that Xorg can't find any display devices to use. I also checked the xorg.conf file and it specifies to use the nvidia driver, should I change it to the above driver or is the above driver unique to Wayland? regards, Steve I've checked whether hardware acceleration is active by running glxgears, which runs quite happily, so I'm assuming that hardware acceleration, as set by the vm configuration, is actually active, hence the nvidia driver is functioning, so I thought Xorg would be able to work with the nvidia driver quite happily. That doesn't tell you that there is hardware acceleration. There is a software 3D renderer available. You can try running "glxinfo" to find out what is being used. I'm not sure what that will show under Wayland. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html 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-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Re: A fontpath question. (Samuel Sieb)
On 02/21/2019 12:50 AM, George R Goffe via users wrote: BTW, this release of Fedora is FC30 x86_64. I hadn't heard that Fc30 is even in alpha yet. However, that shouldn't matter because I doubt that the code for xterm has changed in many years. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
