Re: nmcli won't save VPN password
On 2020-07-23 10:49, Sam Varshavchik wrote: > This means the password is stored in the user's key ring on a per-user basis. > > I haven't tried changing this via nmcli. But, will investigate. FWIW nmcli connection modify US-East-NJ vpn.secrets "password=something" Works just fine for a logged-in user. -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: nmcli won't save VPN password
On 2020-07-23 10:49, Sam Varshavchik wrote: > Ed Greshko writes: > >> On 2020-07-23 10:25, Sam Varshavchik wrote: >> > vpn.data: auth = SHA512, ca = PEMFILEPATH, >> > cipher = AES-256-CBC, comp-lzv = no-by-default, connection-type = >> > password, dev = tun, mssfix = 1450, password-flags = 1, ping = 15, >> > ping-restart = 0, remote = OP_ADDRESS, remote-cert-tls = server, >> > remote-random = yes, reneg-seconds = 0, ta = /root/.cert/PEMFILE, ta-dir = >> > 1, tunnel-mtu = 1500 >> > vpn.secrets: >> >> OK You've probably seen my other responses by now. Fragmented as they >> are. >> >> You have "password-flags = 1" >> >> This means the password is stored in the user's key ring on a per-user basis. >> >> I haven't tried changing this via nmcli. But, will investigate. > > Yup, thanks. This is doable. The magic incantation is: > > nmcli connection modify "$conn" +vpn.data password-flags=0 \ > vpn.user-name "$USERNAME" vpn.secrets password="$PASSWORD" > > This needs to be documented somewhere, I would guess in the > NetworkManager-openvpn package, which installs absolutely no documentation > whatsoever. > > nm-settings(5) doesn't really go into what vpn.data and vpn.secrets have. > This is bog standard OpenVPN, so it's reasonable to have something scribbled > in the NetworkManager-openvpn package, even something that gets tossed next > to the README that's already in there. What also needs to be documented, or I need to get better at searching, is what are the possible values for "option" when doing a modify of vpn.secrets and flags=1. "help" was of no "help". Error: failed to modify vpn.secrets: 'help' is not valid; use =. -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: nmcli won't save VPN password
Ed Greshko writes: On 2020-07-23 10:25, Sam Varshavchik wrote: > vpn.data: auth = SHA512, ca = PEMFILEPATH, cipher = AES-256- CBC, comp-lzv = no-by-default, connection- type = password, dev = tun, mssfix = 1450, password- flags = 1, ping = 15, ping-restart = 0, remote = OP_ADDRESS, remote-cert- tls = server, remote-random = yes, reneg- seconds = 0, ta = /root/.cert/PEMFILE, ta-dir = 1, tunnel-mtu = 1500 > vpn.secrets: OK You've probably seen my other responses by now. Fragmented as they are. You have "password-flags = 1" This means the password is stored in the user's key ring on a per-user basis. I haven't tried changing this via nmcli. But, will investigate. Yup, thanks. This is doable. The magic incantation is: nmcli connection modify "$conn" +vpn.data password-flags=0 \ vpn.user-name "$USERNAME" vpn.secrets password="$PASSWORD" This needs to be documented somewhere, I would guess in the NetworkManager- openvpn package, which installs absolutely no documentation whatsoever. nm-settings(5) doesn't really go into what vpn.data and vpn.secrets have. This is bog standard OpenVPN, so it's reasonable to have something scribbled in the NetworkManager-openvpn package, even something that gets tossed next to the README that's already in there. pgpLkYPBZDZIC.pgp Description: PGP signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: nmcli won't save VPN password
Ed Greshko writes: On 2020-07-23 10:15, Ed Greshko wrote: > On 2020-07-23 09:20, Sam Varshavchik wrote: >> Some searching around found some hits suggesting that my /etc/NetworkManager/system-connections/CONNECTIONNAME should have a [vpn- secrets] section, but mine does not. If I add it, run "nmcli connection reload", "nmcli connection modify", that just removes the [vpn-secrets] section. > Oooopps, sorry. > > I did not read far enough. > > If your connection is type "Password with Certificatees (TLS)" then vpn.secrets is not used as the password > is stored per-user. > > Having a bad morning. Coffee ineffective. I meant to say the "default" is password is stored per-user. You have to inspect vpn.data. If "password-flags = 0" then the password is stored unencrypted and will be in vpn.secrets. If "password-flags = 1" then the password will be stored in the user's keyring and vpn.secrets will not be used. That was the missing link. Of course, "modify vpn.data password_flags=0" just blew away all of my vpn.data. Need to use +vpn.data to reset password_flags. So, I zapped the connection and reloaded it from scratch, from the VPN provider's config file. That did the trick, but there might still be a bug in here, somewhere. The first time I configured a VPN connection I had to deal with some SELinux alerts becase /root/.cert's context was unconfined_u:object_r:admin_home_t:s0, and I fixed it by restorecon-ing it to unconfined_u:object_r:home_cert_t:s0 That problem came back, after I recreated the connection. I think I fixed the context on /root/.cert and /root/.cert/nm-openvpn/* files, but not on /root/.cert/nm-openvpn, but at the very least whatever created /root/.cert didn't give it the right context. I feel like the persistent password stuff needs to be documented somewhere. Thanks. pgpe0QkQTGa5S.pgp Description: PGP signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: nmcli won't save VPN password
On 2020-07-23 10:25, Sam Varshavchik wrote: > vpn.data: auth = SHA512, ca = PEMFILEPATH, > cipher = AES-256-CBC, comp-lzo = no-by-default, connection-type = password, > dev = tun, mssfix = 1450, password-flags = 1, ping = 15, ping-restart = 0, > remote = OP_ADDRESS, remote-cert-tls = server, remote-random = yes, > reneg-seconds = 0, ta = /root/.cert/PEMFILE, ta-dir = 1, tunnel-mtu = 1500 > vpn.secrets: OK You've probably seen my other responses by now. Fragmented as they are. You have "password-flags = 1" This means the password is stored in the user's key ring on a per-user basis. I haven't tried changing this via nmcli. But, will investigate. -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: nmcli won't save VPN password
Ed Greshko writes: On 2020-07-23 09:45, Ed Greshko wrote: > On 2020-07-23 09:20, Sam Varshavchik wrote: >> I'm trying to save an OpenVPN password via nmcli, in Fedora 32. I believe I should be executing: >> >> nmcli connection modify CONNECTIONNAME vpn.secrets "password=[PASSWORD]" >> >> So I execute this as root, and this initially produces very promising noises in /var/log/messages: >> >> Jul 22 20:41:35 jack NetworkManager[1525]: [1595464895.3350] audit: op="connection-update" uuid="UUID" name="CONNECTIONNAME" args="vpn.secrets" pid=67812 uid=0 result="success" >> >> However, the password appears to disappear into a black hole: >> >> nmcli --show-secrets connection CONNECTIONNAME | grep secrets >> vpn.secrets: -- >> >> And nmcli connection up fails because there's no password. >> >> The VPN connection's configuration was imported from the VPN provider's supplied ovpn file, via "nmcli connection import". >> >> Some searching around found some hits suggesting that my /etc/NetworkManager/system-connections/CONNECTIONNAME should have a [vpn- secrets] section, but mine does not. If I add it, run "nmcli connection reload", "nmcli connection modify", that just removes the [vpn-secrets] section. >> >> What would be the right way to do this? > When you do > > nmcli connection show CONNECTNAME > > What is the value of > > 802-11-wireless-security.psk-flags? > Also, what is the value of... 802-11-wireless-security.key-mgmt None of them are set. This is on an edge server with two Ethernet connections. A default route to the Internet, and a /24 route to the LAN. No wireless here. The password in question is the VPN provider's password. Here are all the properties. I masked a few bits in the vpn.data setting. With --show-secrets, vpn-secrets is always just a --. I can nmcli connection modify CONNECTIONNAME vpn.secrets anything=whatever And this gets parroted back to me by --show-secrets. But password=whatever is stubbornly ignored, not saved, and not used. If I manually hack it into the /etc/NetworkManager/system-connections/CONNECTIONNAME.nmconnection, and nmcli connection reload it, it gets stubbornly ignored. I cannot find any way to start the VPN other than with the --ask option, and prompt for the password, every time. connection.id: CONNECTIONNAME connection.uuid:d5a4c828-ba14-46bb-866b-9d1b66a50668 connection.stable-id: -- connection.type:vpn connection.interface-name: -- connection.autoconnect: yes connection.autoconnect-priority:0 connection.autoconnect-retries: -1 (default) connection.multi-connect: 0 (default) connection.auth-retries:-1 connection.timestamp: 1595467636 connection.read-only: no connection.permissions: -- connection.zone:-- connection.master: -- connection.slave-type: -- connection.autoconnect-slaves: -1 (default) connection.secondaries: -- connection.gateway-ping-timeout:0 connection.metered: unknown connection.lldp:default connection.mdns:-1 (default) connection.llmnr: -1 (default) connection.wait-device-timeout: -1 ipv4.method:auto ipv4.dns: -- ipv4.dns-search:-- ipv4.dns-options: -- ipv4.dns-priority: 0 ipv4.addresses: -- ipv4.gateway: -- ipv4.routes:-- ipv4.route-metric: -1 ipv4.route-table: 0 (unspec) ipv4.routing-rules: -- ipv4.ignore-auto-routes:no ipv4.ignore-auto-dns: yes ipv4.dhcp-client-id:-- ipv4.dhcp-iaid: -- ipv4.dhcp-timeout: 0 (default) ipv4.dhcp-send-hostname:yes ipv4.dhcp-hostname: -- ipv4.dhcp-fqdn: -- ipv4.dhcp-hostname-flags: 0x0 (none) ipv4.never-default: no ipv4.may-fail: yes ipv4.dad-timeout: -1 (default) ipv6.method:auto ipv6.dns: -- ipv6.dns-search:-- ipv6.dns-options: -- ipv6.dns-priority: 0 ipv6.addresses: -- ipv6.gateway: -- ipv6.routes:-- ipv6.route-metric: -1 ipv6.route-table: 0 (unspec) ipv6.routing-rules: --
Re: nmcli won't save VPN password
On 2020-07-23 10:15, Ed Greshko wrote: > On 2020-07-23 09:20, Sam Varshavchik wrote: >> Some searching around found some hits suggesting that my >> /etc/NetworkManager/system-connections/CONNECTIONNAME should have a >> [vpn-secrets] section, but mine does not. If I add it, run "nmcli connection >> reload", "nmcli connection modify", that just removes the [vpn-secrets] >> section. > Oooopps, sorry. > > I did not read far enough. > > If your connection is type "Password with Certificatees (TLS)" then > vpn.secrets is not used as the password > is stored per-user. > > Having a bad morning. Coffee ineffective. I meant to say the "default" is password is stored per-user. You have to inspect vpn.data. If "password-flags = 0" then the password is stored unencrypted and will be in vpn.secrets. If "password-flags = 1" then the password will be stored in the user's keyring and vpn.secrets will not be used. -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: nmcli won't save VPN password
On 2020-07-23 09:20, Sam Varshavchik wrote: > Some searching around found some hits suggesting that my > /etc/NetworkManager/system-connections/CONNECTIONNAME should have a > [vpn-secrets] section, but mine does not. If I add it, run "nmcli connection > reload", "nmcli connection modify", that just removes the [vpn-secrets] > section. Oooopps, sorry. I did not read far enough. If your connection is type "Password with Certificatees (TLS)" then vpn.secrets is not used as the password is stored per-user. -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: nmcli won't save VPN password
On 2020-07-23 09:45, Ed Greshko wrote: > On 2020-07-23 09:20, Sam Varshavchik wrote: >> I'm trying to save an OpenVPN password via nmcli, in Fedora 32. I believe I >> should be executing: >> >> nmcli connection modify CONNECTIONNAME vpn.secrets "password=[PASSWORD]" >> >> So I execute this as root, and this initially produces very promising noises >> in /var/log/messages: >> >> Jul 22 20:41:35 jack NetworkManager[1525]: [1595464895.3350] audit: >> op="connection-update" uuid="UUID" name="CONNECTIONNAME" args="vpn.secrets" >> pid=67812 uid=0 result="success" >> >> However, the password appears to disappear into a black hole: >> >> nmcli --show-secrets connection CONNECTIONNAME | grep secrets >> vpn.secrets: -- >> >> And nmcli connection up fails because there's no password. >> >> The VPN connection's configuration was imported from the VPN provider's >> supplied ovpn file, via "nmcli connection import". >> >> Some searching around found some hits suggesting that my >> /etc/NetworkManager/system-connections/CONNECTIONNAME should have a >> [vpn-secrets] section, but mine does not. If I add it, run "nmcli connection >> reload", "nmcli connection modify", that just removes the [vpn-secrets] >> section. >> >> What would be the right way to do this? > When you do > > nmcli connection show CONNECTNAME > > What is the value of > > 802-11-wireless-security.psk-flags? > Also, what is the value of... 802-11-wireless-security.key-mgmt -- The key to getting good answers is to ask good questions. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: fedora 32 - debug freezing new install!!
On 7/22/20 5:58 PM, Jack Craig wrote: what is the current wisdom on debugging this fedora 32 freeze failure type? You'll first need to provide some information. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: nmcli won't save VPN password
On 2020-07-23 09:20, Sam Varshavchik wrote: > I'm trying to save an OpenVPN password via nmcli, in Fedora 32. I believe I > should be executing: > > nmcli connection modify CONNECTIONNAME vpn.secrets "password=[PASSWORD]" > > So I execute this as root, and this initially produces very promising noises > in /var/log/messages: > > Jul 22 20:41:35 jack NetworkManager[1525]: [1595464895.3350] audit: > op="connection-update" uuid="UUID" name="CONNECTIONNAME" args="vpn.secrets" > pid=67812 uid=0 result="success" > > However, the password appears to disappear into a black hole: > > nmcli --show-secrets connection CONNECTIONNAME | grep secrets > vpn.secrets: -- > > And nmcli connection up fails because there's no password. > > The VPN connection's configuration was imported from the VPN provider's > supplied ovpn file, via "nmcli connection import". > > Some searching around found some hits suggesting that my > /etc/NetworkManager/system-connections/CONNECTIONNAME should have a > [vpn-secrets] section, but mine does not. If I add it, run "nmcli connection > reload", "nmcli connection modify", that just removes the [vpn-secrets] > section. > > What would be the right way to do this? When you do nmcli connection show CONNECTNAME What is the value of 802-11-wireless-security.psk-flags? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: bizzare dual-monitor behavior SOLVED
On Mon, Jul 20, 2020 at 10:10 AM Greg Woods wrote: > > > What used to happen when I switched to a different computer is that I can > use the new computer using the first monitor, the mouse and the keyboard, > just as usual. The second monitor, unaffected by the KVM switch, will > continue to show the image it is getting from the dual-monitor system. > > But, what is now happening (since yesterday) is that when I switch to a > second computer, the non-KVM-switched monitor now flashes off and on every > few seconds (and just keeps doing this seemingly forever; I did leave it > this way for more than 15 minutes last night) . This is INCREDIBLY annoying > and makes it impossible to make any use of the image displayed there. > UPDATE: one or two times when I switched away from the dual monitor system, I got a green screen on the second monitor, and when switching back to the problem system, both monitors were green screened and the keyboard and mouse were unresponsive. It required an SSH in from another system to suspend the machine; on resuming, things were working again. But this raised the level of the issue from "very annoying" to "show stopper". I realize nobody reading this now cares about this (presumably that just means nobody else has a dual monitor setup with one monitor controlled through a KVM switch, or else those who do haven't seen this happen and don't have any ideas). But I'm posting this in case anyone finds this in the archives later. I am now convinced the issue all along that the graphics driver for my card, which is one of the "Republic of Gamers" (ROG) intended for serious gamers, is the cause (ROG is just an ASUS marketing term). I have spent a lot of time Googling around and finally found a proprietary driver that ASUS produces. It is intended for EL8 and derivatives (e.g Centos 8), and will not install directly on Fedora, as the necessary packages (which have names that begin with "amdgpu") are not in the EPEL repo for Fedora. However, I downloaded the driver software for Linux from https://www.amd.com/en/support/kb/release-notes/rn-amdgpu-unified-linux-20-10 and then followed the guide I found at https://www.reddit.com/r/Fedora/comments/hftkwd/guide_install_amdgpupro_opencl_in_fedora_32/ This installs a part of the driver called "OpenCL"; the kernel device driver "amdgpu" is still being used. I am not entirely clear on what OpenCL is, but it adds some features that programs like Blender used; the guide author reported getting crashes prior to installing the proprietary OpenCL part (he probably considered that a show stopper too). For me, I was just in desperation mode to solve my issue, but this fixed it. Once I installed the ASUS OpenCL packages, I no longer get the "flashing monitor syndrome" or green screen lockups. --Greg ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: Sane Scanner Resolution Configuration
Glad it worked out for you. I don't know why your Sane is so different from mine. I cannot find the "Bind X and Y resolutions" option in Window - Show Advanced Options or Preferences - Setup. But your Sane works and mine works, so everybody is happy. Mike On 7/22/20 6:40 PM, Stephen Morris wrote: Thanks Mike, I had a look at your 'CANON:Canoscan9000FMarkII.drc' and it only has one line for Resolution which you have set at 300 as I do. My Epson drc file has two entries for Resolution, an X resolution and a Y resolution, which are reflected as such in the xsane gui where I have a 'Resolution in the X direction' dropdown and a 'Resolution in the Y direction' dropdown. After looking at your drc file I have now resolved the issue with the two resolution dropdowns being disabled. In the xsane advanced settings I had the checkbox for 'Bind X and Y resolutions' selected and when I unselected that checkbox the two resolution options became selectable and I could then select one of the 16 resolutions displayed for each of the X and Y resolutions, each of which if desired can be set to different values. I'm also not sure if my scanner supports all the resolutions being made available. I know it supports resolutions of 75, 150, 300, 600 and 1200, but I'm not sure if it supports the rest. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
nmcli won't save VPN password
I'm trying to save an OpenVPN password via nmcli, in Fedora 32. I believe I should be executing: nmcli connection modify CONNECTIONNAME vpn.secrets "password=[PASSWORD]" So I execute this as root, and this initially produces very promising noises in /var/log/messages: Jul 22 20:41:35 jack NetworkManager[1525]: [1595464895.3350] audit: op="connection-update" uuid="UUID" name="CONNECTIONNAME" args="vpn.secrets" pid=67812 uid=0 result="success" However, the password appears to disappear into a black hole: nmcli --show-secrets connection CONNECTIONNAME | grep secrets vpn.secrets:-- And nmcli connection up fails because there's no password. The VPN connection's configuration was imported from the VPN provider's supplied ovpn file, via "nmcli connection import". Some searching around found some hits suggesting that my /etc/NetworkManager/system-connections/CONNECTIONNAME should have a [vpn- secrets] section, but mine does not. If I add it, run "nmcli connection reload", "nmcli connection modify", that just removes the [vpn-secrets] section. What would be the right way to do this? pgp1K06MKjS4g.pgp Description: PGP signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
fedora 32 - debug freezing new install!!
what is the current wisdom on debugging this fedora 32 freeze failure type? thx, jackc... ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: Sane Scanner Resolution Configuration
On 22/7/20 9:09 pm, Mike Flannigan wrote: Sure thing. The 'xsane.rc' file at ~/.sane/xsane is copied here: http://www.mflan.com/temp/xsane.rc There is also a 'xsane.mdf' file in there, but I don't think you need that. There is also a 'CANON:Canoscan9000FMarkII.drc' file in there and it is copied here: http://www.mflan.com/temp/CANON:Canoscan9000FMarkII.drc Thanks Mike, I had a look at your 'CANON:Canoscan9000FMarkII.drc' and it only has one line for Resolution which you have set at 300 as I do. My Epson drc file has two entries for Resolution, an X resolution and a Y resolution, which are reflected as such in the xsane gui where I have a 'Resolution in the X direction' dropdown and a 'Resolution in the Y direction' dropdown. After looking at your drc file I have now resolved the issue with the two resolution dropdowns being disabled. In the xsane advanced settings I had the checkbox for 'Bind X and Y resolutions' selected and when I unselected that checkbox the two resolution options became selectable and I could then select one of the 16 resolutions displayed for each of the X and Y resolutions, each of which if desired can be set to different values. I'm also not sure if my scanner supports all the resolutions being made available. I know it supports resolutions of 75, 150, 300, 600 and 1200, but I'm not sure if it supports the rest. regards, Steve Mike On 7/21/20 10:09 PM, users-requ...@lists.fedoraproject.org wrote: Thanks Mike, that's interesting, my Xsane ver 0.999 doesn't provide the same functionality. Where your gui has the resolution dropdown to let you select between the supported resolutions, my gui has two entries, a horizontal resolution and a vertical resolution, and both of them are disabled, so that the only way to change it is to manually changed the corresponding two lines in the configuration file. I'm now wondering whether the Epson driver is having an impact, as in order to see and use the Epson scanner xsane seems to be using the settings I put in the config file created by the install of Epson's imagescan software. Are you able to supply the config file, or the resolution part of the config file, for your scanner, which if it is stored in the same location as it is for me, is in ~/.sane/xsane? I just wanted to see how it is set up for you and whether or not I can replicate that in my configuration. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: Printing failure -
On Wed, Jul 22, 2020, 23:50 Bob Goodwin wrote: > > > On 2020-07-21 21:19, Ed Greshko wrote: > > OK, and do verify that the changes were made to /etc/nsswitch.conf. > Just because paranoia is > > at times not a bad thing.:-) :-) > ° > I did that immediately after activating the change. > > The important thing is that I am able to print and satisfy the need for > crossword puzzles ... > > Thanks for the help > Happy to hear that one puzzle was solved. > ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: Alternatives link broken after package upgrade
Thanks Robin, I wasn't sure it was me or a bug that need reporting. On Wed, Jul 22, 2020 at 1:45 PM Robin Lee wrote: > > > Terry Polzin 于2020年7月23日 周四上午1:34写道： > >> I've been dealing with this issue on a couple of my Fedora 32 machines. >> It appears that the upgrade of icedtea-web >> from icedtea-web-1.8.2-3.fc31.x86_64 to >> icedtea-web-2.0.0-pre.0.3.alpha13.patched1.fc32.x86_64 breaks the >> alternatives link to javaws.x86_64. >> >> I have to downgrade icedtea-web to be able to run JNLPs >> > https://bugzilla.redhat.com/show_bug.cgi?id=1859090 > > ___ >> users mailing list -- users@lists.fedoraproject.org >> To unsubscribe send an email to users-le...@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-le...@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-le...@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
Re: Alternatives link broken after package upgrade
Terry Polzin 于2020年7月23日 周四上午1:34写道： > I've been dealing with this issue on a couple of my Fedora 32 machines. > It appears that the upgrade of icedtea-web > from icedtea-web-1.8.2-3.fc31.x86_64 to > icedtea-web-2.0.0-pre.0.3.alpha13.patched1.fc32.x86_64 breaks the > alternatives link to javaws.x86_64. > > I have to downgrade icedtea-web to be able to run JNLPs > https://bugzilla.redhat.com/show_bug.cgi?id=1859090 ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@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-le...@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
Alternatives link broken after package upgrade
I've been dealing with this issue on a couple of my Fedora 32 machines. It appears that the upgrade of icedtea-web from icedtea-web-1.8.2-3.fc31.x86_64 to icedtea-web-2.0.0-pre.0.3.alpha13.patched1.fc32.x86_64 breaks the alternatives link to javaws.x86_64. I have to downgrade icedtea-web to be able to run JNLPs ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: Printing failure -
On 2020-07-21 21:19, Ed Greshko wrote: OK, and do verify that the changes were made to /etc/nsswitch.conf. Just because paranoia is at times not a bad thing.:-) :-) ° I did that immediately after activating the change. The important thing is that I am able to print and satisfy the need for crossword puzzles ... Thanks for the help -- Bob Goodwin - Zuni, Virginia, USA http://www.qrz.com/db/W2BOD FEDORA-32/64bit LINUX XFCE Fastmail POP3 ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: podman and PCI passthrough
On 7/22/20 07:57, Mauricio Tavares wrote: > On Wed, Jul 22, 2020 at 6:14 AM Daniel Walsh wrote: >> On 7/21/20 20:54, Gordon Messmer wrote: >>> On 7/21/20 4:46 PM, Mauricio Tavares wrote: What is the argument I need to properly pass a PCI or PCIe device to a podman container at runtime (podman-run)? >>> >>> Assuming that it's supported by the OS running podman, I believe you >>> can mount the device node inside the container using the --volume option. >>> ___ >>> users mailing list -- users@lists.fedoraproject.org >>> To unsubscribe send an email to users-le...@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 >> If this is a standard device on /dev. then using podman run --device or >> podman create --device would put the device into the container. > How much is exposed vs abstracted using --device in podman vs in > docker? Can I also do something like > > --mount type=bind,source=/sys/bus/pci/[...] Yes this should work. > to pass the device? And does podman support --cap-add options or has > an equivalent? Podman has everything that Docker has. So yes --cap-add is supported. > >> ___ >> users mailing list -- users@lists.fedoraproject.org >> To unsubscribe send an email to users-le...@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-le...@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-le...@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
Re: podman and PCI passthrough
On Wed, Jul 22, 2020 at 6:14 AM Daniel Walsh wrote: > > On 7/21/20 20:54, Gordon Messmer wrote: > > On 7/21/20 4:46 PM, Mauricio Tavares wrote: > >>What is the argument I need to properly pass a PCI or PCIe > >> device to a podman container at runtime (podman-run)? > > > > > > Assuming that it's supported by the OS running podman, I believe you > > can mount the device node inside the container using the --volume option. > > ___ > > users mailing list -- users@lists.fedoraproject.org > > To unsubscribe send an email to users-le...@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 > > If this is a standard device on /dev. then using podman run --device or > podman create --device would put the device into the container. How much is exposed vs abstracted using --device in podman vs in docker? Can I also do something like --mount type=bind,source=/sys/bus/pci/[...] to pass the device? And does podman support --cap-add options or has an equivalent? > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@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-le...@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
Re: Sane Scanner Resolution Configuration
Sure thing. The 'xsane.rc' file at ~/.sane/xsane is copied here: http://www.mflan.com/temp/xsane.rc There is also a 'xsane.mdf' file in there, but I don't think you need that. There is also a 'CANON:Canoscan9000FMarkII.drc' file in there and it is copied here: http://www.mflan.com/temp/CANON:Canoscan9000FMarkII.drc Mike On 7/21/20 10:09 PM, users-requ...@lists.fedoraproject.org wrote: Thanks Mike, that's interesting, my Xsane ver 0.999 doesn't provide the same functionality. Where your gui has the resolution dropdown to let you select between the supported resolutions, my gui has two entries, a horizontal resolution and a vertical resolution, and both of them are disabled, so that the only way to change it is to manually changed the corresponding two lines in the configuration file. I'm now wondering whether the Epson driver is having an impact, as in order to see and use the Epson scanner xsane seems to be using the settings I put in the config file created by the install of Epson's imagescan software. Are you able to supply the config file, or the resolution part of the config file, for your scanner, which if it is stored in the same location as it is for me, is in ~/.sane/xsane? I just wanted to see how it is set up for you and whether or not I can replicate that in my configuration. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
Re: podman and PCI passthrough
On 7/21/20 20:54, Gordon Messmer wrote: > On 7/21/20 4:46 PM, Mauricio Tavares wrote: >> What is the argument I need to properly pass a PCI or PCIe >> device to a podman container at runtime (podman-run)? > > > Assuming that it's supported by the OS running podman, I believe you > can mount the device node inside the container using the --volume option. > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@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 If this is a standard device on /dev. then using podman run --device or podman create --device would put the device into the container. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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
