users October 2021

users@lists.fedoraproject.org

62 participants
105 discussions

Re: Does the program llvm break all the hardware or only some of it ?
by Jonathan Billings 31 Oct '21

31 Oct '21

On Sun, Oct 31, 2021 at 11:26:48AM +0000, Dorian ROSSE wrote: > Does my system was broken because i have removed the program zoo ? No. In fact, I don't believe that 'zoo' is a program that is part of Fedora in the first place. There's an 'unzoo' though. Remember last time you asked this question, and we said, "You need to give us more details!" well... You need to give us more details! (Repetition helps people learn.) -- Jonathan Billings <billings(a)negate.org>

1 0

Re: Does the program llvm break all the hardware or only some of it ?
by Jonathan Billings 31 Oct '21

31 Oct '21

On Sun, Oct 31, 2021 at 11:32:01AM +0000, Dorian ROSSE wrote: > [-- BEGIN PGP MESSAGE --] > ... > [-- END PGP MESSAGE --] Please stop. -- Jonathan Billings <billings(a)negate.org>

1 0

RE: Does the program llvm break all the hardware or only some of it ?
by Dorian ROSSE 31 Oct '21

31 Oct '21

1 0

Re: Does the program llvm break all the hardware or only some of it ?
by Dorian ROSSE 31 Oct '21

31 Oct '21

Hello everybody Does my system was broken because i have removed the program zoo ? Thank you in advance for yours answer, Regards. Dorian Rosse. ________________________________ From: Dorian ROSSE <dorianbrice(a)hotmail.fr> Sent: Monday, October 25, 2021 2:53:58 PM To: Community support for Fedora users <users(a)lists.fedoraproject.org> Subject: Re: Does the program llvm break all the hardware or only some of it ? I have success to report the two broken, Regards. Dorian Rosse. ________________________________ From: Matthew Miller <mattdm(a)fedoraproject.org> Sent: Friday, October 22, 2021 12:35:58 AM To: Community support for Fedora users <users(a)lists.fedoraproject.org> Subject: Re: Does the program llvm break all the hardware or only some of it ? On Mon, Oct 18, 2021 at 09:50:41PM -0400, Jonathan Billings wrote: > The LLVM Project is a collection of modular and reusable compiler and toolchain technologies. Despite its name, LLVM has little to do with traditional virtual machines. The name "LLVM" itself is not an acronym; it is the full name of the project. I think a PR at https://src.fedoraproject.org/rpms/llvm/blob/rawhide/f/llvm.spec to update the Summary would be the most helpful thing in this case (along with, of course, an explanatory comment). -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader _______________________________________________ users mailing list -- users(a)lists.fedoraproject.org To unsubscribe send an email to users-leave(a)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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

1 0

RE: Does the program llvm break all the hardware or only some of it ?
by Dorian ROSSE 31 Oct '21

31 Oct '21

1 0

Problems with USB AudioEngine Speakers
by Jonathan Ryshpan 31 Oct '21

31 Oct '21

I have just installed a pair of AudioEngine speakers and have many problems: The stock Fedora-34 with pipewire allows some audio output from the speakers but with problems. However the system with pipewire was so unstable that I was unable to investigate: * device names changed * audio configuration changed in unexpected ways, for unknown reasons * system locked up (probably KDE Plasma lockup) * audio went from one device to another and back every second or so * ... So I reverted to pulseaudio. The audio is now stable, but the speakers are not recognized. Here are suspicious sections of the starts of the journals for the two setups: With pipewire: ... Oct 07 15:50:10 amito kernel: usb 3-14: reset full-speed USB device number 6 using xhci_hcd Oct 07 15:50:11 amito kernel: usb 3-14.1: new full-speed USB device number 9 using xhci_hcd Oct 07 15:50:11 amito kernel: usb 3-14.1: New USB device found, idVendor=0a12, idProduct=4007, bcdDevice=14.86 Oct 07 15:50:11 amito kernel: usb 3-14.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 07 15:50:11 amito kernel: usb 3-14.1: Product: Audioengine 2+ Oct 07 15:50:11 amito kernel: usb 3-14.1: Manufacturer: Audioengine LLC Oct 07 15:50:11 amito kernel: usb 3-14.1: SerialNumber: AE202010001A2002 Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 48000 to ep 0x3 Oct 07 15:50:11 amito kernel: hid-generic 0003:0A12:4007.0007: hiddev97,hidraw3: USB HID v1.11 Device [Audioengine LLC Audioengine 2+] on usb-0000:00:14.0-14.1/input2 Oct 07 15:50:11 amito upowerd[2720]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-14 Oct 07 15:50:11 amito upowerd[2720]: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb3/3-14 Oct 07 15:50:11 amito mtp-probe[6841]: checking bus 3, device 9: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-14/3-14.1" Oct 07 15:50:11 amito mtp-probe[6841]: bus: 3, device: 9 was not an MTP device Oct 07 15:50:11 amito plasmashell[4490]: UdevQt: unhandled device action "bind" Oct 07 15:50:11 amito plasmashell[4490]: UdevQt: unhandled device action "bind" Oct 07 15:50:11 amito plasmashell[4490]: UdevQt: unhandled device action "bind" Oct 07 15:50:11 amito mtp-probe[6869]: checking bus 3, device 9: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-14/3-14.1" Oct 07 15:50:11 amito mtp-probe[6869]: bus: 3, device: 9 was not an MTP device Oct 07 15:50:11 amito plasmashell[4490]: UdevQt: unhandled device action "bind" Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to ep 0x3 Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to ep 0x3 Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to ep 0x3 Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to ep 0x3 Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to ep 0x3 Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to ep 0x3 Oct 07 15:50:11 amito kernel: usb 3-14.1: 1:1: cannot set freq 44100 to ep 0x3 ... Using pulseaudio: ... Oct 07 17:45:46 amito kernel: usb 3-14.1: New USB device found, idVendor=0a12, idProduct=4007, bcdDevice=14.86 Oct 07 17:45:46 amito kernel: usb 3-14.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 07 17:45:46 amito kernel: usb 3-14.1: Product: Audioengine 2+ Oct 07 17:45:46 amito kernel: hid-generic 0003:046D:400A.0005: input,hidraw2: USB HID v1.11 Mouse [Logitech Wireless Device PID:400a] on usb-0000:00:14.0-13/input2:1 Oct 07 17:45:46 amito kernel: hub 3-14:1.0: hub_ext_port_status failed (err = -71) Oct 07 17:45:46 amito kernel: input: Logitech M325 as /devices/pci0000:00/0000:00:14.0/usb3/3-13/3- 13:1.2/0003:046D:C52B.0004/0003:046D:400A.0005/input/input13 ... Oct 07 17:45:46 amito kernel: usb 3-14.1: New USB device found, idVendor=0a12, idProduct=4007, bcdDevice=14.86 Oct 07 17:45:46 amito kernel: usb 3-14.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Oct 07 17:45:46 amito kernel: usb 3-14.1: Product: Audioengine 2+ Oct 07 17:45:46 amito kernel: usb 3-14.1: Manufacturer: Audioengine LLC Oct 07 17:45:46 amito kernel: usb 3-14.1: can't set config #1, error - 71 ... It would help to know what the various errors mean. System is Fedora-34 with all updates installed, in detail: Operating System: Fedora 34 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.14.9-200.fc34.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 -- Sincerely Jonathan Ryshpan <jonrysh(a)pacbell.net> If God lived on earth, people would break all his windows.

5 34

Desktop Icons Blank
by Robert McBroom 30 Oct '21

30 Oct '21

I use KeePass for a password keeper. There is an icon for it in the KeePass directory and it is referenced by the launcher on the desktop. Nothing shows in recent 33,34. Do I need to convert the png file to another format or put it in a particular directory?

4 5

target - enable httpds
by Jack Craig 30 Oct '21

30 Oct '21

i am working to make letsencrypt .pem files work on my F34 workstation. so far, i try firefox browser, and, ... ssl:info] [pid 16630:tid 16630] AH01914: Configuring server www.linuxlighthouse.com:443 for SSL protocol [ssl:trace3] [pid 16630:tid 16630] ssl_engine_init.c(649): Using OpenSSL/system default SSL/TLS protocols [ssl:trace3] [pid 16630:tid 16630] ssl_engine_init.c(670): Creating new SSL context (protocols: default) [ssl:trace1] [pid 16630:tid 16630] ssl_engine_init.c(1036): Configuring permitted SSL ciphers [PROFILE=SYSTEM] [ssl:debug] [pid 16630:tid 16630] ssl_engine_init.c(1248): AH01904: Configuring server certificate chain (2 CA certificates) [ssl:debug] [pid 16630:tid 16630] ssl_engine_init.c(528): AH01893: Configuring TLS extension handling [ssl:trace3] [pid 16630:tid 16630] ssl_util_ssl.c(436): [ www.linuxlighthouse.com:443] modssl_X509_match_name: expecting name ' www.linuxlighthouse.com', NOT matched by ID 'linuxlighthouse.com' [ssl:trace3] [pid 16630:tid 16630] ssl_util_ssl.c(436): [ www.linuxlighthouse.com:443] modssl_X509_match_name: expecting name ' www.linuxlighthouse.com', NOT matched by ID 'ws.linuxlighthouse.com' [ssl:trace3] [pid 16630:tid 16630] ssl_util_ssl.c(436): [ www.linuxlighthouse.com:443] modssl_X509_match_name: expecting name ' www.linuxlighthouse.com', matched by ID 'www.linuxlighthouse.com' [ssl:debug] [pid 16630:tid 16630] ssl_util_ssl.c(451): AH02412: [ www.linuxlighthouse.com:443] Cert matches for name 'www.linuxlighthouse.com' [subject: CN=linuxlighthouse.com / issuer: CN=R3,O=Let's Encrypt,C=US / serial: 03DBD10F4587D6C0A8DF92A4AFAB30608EFF / notbefore: Oct 22 21:12:41 2021 GMT / notafter: Jan 20 21:12:40 2022 GMT] [ssl:info] [pid 16630:tid 16630] AH02568: Certificate and private key www.linuxlighthouse.com:443:0 configured from /etc/letsencrypt/live/ linuxlighthouse.com/fullchain.pem and /etc/letsencrypt/live/ linuxlighthouse.com/privkey.pem [ssl:info] [pid 16630:tid 16630] AH01914: Configuring server www.linuxlighthouse.com:443 for SSL protocol [ssl:trace3] [pid 16630:tid 16630] ssl_engine_init.c(649): Using OpenSSL/system default SSL/TLS protocols [ssl:trace3] [pid 16630:tid 16630] ssl_engine_init.c(670): Creating new SSL context (protocols: default) [ssl:trace1] [pid 16630:tid 16630] ssl_engine_init.c(1036): Configuring permitted SSL ciphers [PROFILE=SYSTEM] [ssl:debug] [pid 16630:tid 16630] ssl_engine_init.c(1248): AH01904: Configuring server certificate chain (2 CA certificates) [ssl:debug] [pid 16630:tid 16630] ssl_engine_init.c(528): AH01893: Configuring TLS extension handling [ssl:trace3] [pid 16630:tid 16630] ssl_util_ssl.c(436): [ www.linuxlighthouse.com:443] modssl_X509_match_name: expecting name ' www.linuxlighthouse.com', NOT matched by ID 'linuxlighthouse.com' [ssl:trace3] [pid 16630:tid 16630] ssl_util_ssl.c(436): [ www.linuxlighthouse.com:443] modssl_X509_match_name: expecting name ' www.linuxlighthouse.com', NOT matched by ID 'ws.linuxlighthouse.com' [ssl:trace3] [pid 16630:tid 16630] ssl_util_ssl.c(436): [ www.linuxlighthouse.com:443] modssl_X509_match_name: expecting name ' www.linuxlighthouse.com', matched by ID 'www.linuxlighthouse.com' [ssl:debug] [pid 16630:tid 16630] ssl_util_ssl.c(451): AH02412: [ www.linuxlighthouse.com:443] Cert matches for name 'www.linuxlighthouse.com' [subject: CN=linuxlighthouse.com / issuer: CN=R3,O=Let's Encrypt,C=US / serial: 03DBD10F4587D6C0A8DF92A4AFAB30608EFF / notbefore: Oct 22 21:12:41 2021 GMT / notafter: Jan 20 21:12:40 2022 GMT] [ssl:info] [pid 16630:tid 16630] AH02568: Certificate and private key www.linuxlighthouse.com:443:0 configured from /etc/letsencrypt/live/ linuxlighthouse.com/fullchain.pem and /etc/letsencrypt/live/ linuxlighthouse.com/privkey.pem ssl:info] [pid 16630:tid 16630] AH01914: Configuring server www.linuxlighthouse.com:443 for SSL protocol [ssl:trace3] [pid 16630:tid 16630] ssl_engine_init.c(649): Using OpenSSL/system default SSL/TLS protocols [ssl:trace3] [pid 16630:tid 16630] ssl_engine_init.c(670): Creating new SSL context (protocols: default) [ssl:trace1] [pid 16630:tid 16630] ssl_engine_init.c(1036): Configuring permitted SSL ciphers [PROFILE=SYSTEM] [ssl:debug] [pid 16630:tid 16630] ssl_engine_init.c(1248): AH01904: Configuring server certificate chain (2 CA certificates) [ssl:debug] [pid 16630:tid 16630] ssl_engine_init.c(528): AH01893: Configuring TLS extension handling [ssl:trace3] [pid 16630:tid 16630] ssl_util_ssl.c(436): [ www.linuxlighthouse.com:443] modssl_X509_match_name: expecting name ' www.linuxlighthouse.com', NOT matched by ID 'linuxlighthouse.com' [ssl:trace3] [pid 16630:tid 16630] ssl_util_ssl.c(436): [ www.linuxlighthouse.com:443] modssl_X509_match_name: expecting name ' www.linuxlighthouse.com', NOT matched by ID 'ws.linuxlighthouse.com' [ssl:trace3] [pid 16630:tid 16630] ssl_util_ssl.c(436): [ www.linuxlighthouse.com:443] modssl_X509_match_name: expecting name ' www.linuxlighthouse.com', matched by ID 'www.linuxlighthouse.com' [ssl:debug] [pid 16630:tid 16630] ssl_util_ssl.c(451): AH02412: [ www.linuxlighthouse.com:443] Cert matches for name 'www.linuxlighthouse.com' [subject: CN=linuxlighthouse.com / issuer: CN=R3,O=Let's Encrypt,C=US / serial: 03DBD10F4587D6C0A8DF92A4AFAB30608EFF / notbefore: Oct 22 21:12:41 2021 GMT / notafter: Jan 20 21:12:40 2022 GMT] [ssl:info] [pid 16630:tid 16630] AH02568: Certificate and private key www.linuxlighthouse.com:443:0 configured from /etc/letsencrypt/live/ linuxlighthouse.com/fullchain.pem and /etc/letsencrypt/live/ linuxlighthouse.com/privkey.pem [ssl:info] [pid 16630:tid 16630] AH01914: Configuring server www.linuxlighthouse.com:443 for SSL protocol [ssl:trace3] [pid 16630:tid 16630] ssl_engine_init.c(649): Using OpenSSL/system default SSL/TLS protocols [ssl:trace3] [pid 16630:tid 16630] ssl_engine_init.c(670): Creating new SSL context (protocols: default) [ssl:trace1] [pid 16630:tid 16630] ssl_engine_init.c(1036): Configuring permitted SSL ciphers [PROFILE=SYSTEM] [ssl:debug] [pid 16630:tid 16630] ssl_engine_init.c(1248): AH01904: Configuring server certificate chain (2 CA certificates) [ssl:debug] [pid 16630:tid 16630] ssl_engine_init.c(528): AH01893: Configuring TLS extension handling [ssl:trace3] [pid 16630:tid 16630] ssl_util_ssl.c(436): [ www.linuxlighthouse.com:443] modssl_X509_match_name: expecting name ' www.linuxlighthouse.com', NOT matched by ID 'linuxlighthouse.com' [ssl:trace3] [pid 16630:tid 16630] ssl_util_ssl.c(436): [ www.linuxlighthouse.com:443] modssl_X509_match_name: expecting name ' www.linuxlighthouse.com', NOT matched by ID 'ws.linuxlighthouse.com' [ssl:trace3] [pid 16630:tid 16630] ssl_util_ssl.c(436): [ www.linuxlighthouse.com:443] modssl_X509_match_name: expecting name ' www.linuxlighthouse.com', matched by ID 'www.linuxlighthouse.com' [ssl:debug] [pid 16630:tid 16630] ssl_util_ssl.c(451): AH02412: [ www.linuxlighthouse.com:443] Cert matches for name 'www.linuxlighthouse.com' [subject: CN=linuxlighthouse.com / issuer: CN=R3,O=Let's Encrypt,C=US / serial: 03DBD10F4587D6C0A8DF92A4AFAB30608EFF / notbefore: Oct 22 21:12:41 2021 GMT / notafter: Jan 20 21:12:40 2022 GMT] [ssl:info] [pid 16630:tid 16630] AH02568: Certificate and private key www.linuxlighthouse.com:443:0 configured from /etc/letsencrypt/live/ linuxlighthouse.com/fullchain.pem and /etc/letsencrypt/live/ linuxlighthouse.com/privkey.pem F34 install, add letsencrypt , and i am https ready. problem, i am not getting text secure link and not seeing a lot of options> rather than screw it up by guessing, i need to learn a bit about SSL Engine. suggestions? tia, ..

2 4

verifying Fedora 34 mate spin
by Tim 30 Oct '21

30 Oct '21

Hi, Just trying to figure out how to verify the Fedora 34 mate spin. Looking through the pages you get after going to the mate spin, it suggests <https://spins.fedoraproject.org/en/verify>, the instructions aren't coherent, and don't work as written. There's what looks like it's simply a heading saying Verify 64-bit iso, but that's actually a clickable link to download the checksum file. Not well written. Then it says to import the GPG keys. That works. $ curl https://getfedora.org/static/fedora.gpg | gpg --import Then it sends you to another page to verify the GPG keys. https://getfedora.org/en/security/ It gives the same curl command as above. Asks you to verify the checksum file is valid, but since you haven't downloaded the checksum file you can't. It imported it directly into GPG. There's no instructions that you need to *separately* download the keys and verify them (if you want to verify them). And, really, you should do that step before importing them. And, you're importing unknown untrusted keys, anyway. Trying to follow that page is a hotchpotch of reading through the page, scrolling up and down, referring to something written below the instructions, going back to reread the instructions, and flick between pages. Fair enough to put the quick list of steps you'll go through at the top, but put the full sequence, *in* the sequence that you'll do it, further down the page. Then going back to the verify page to try and figure out how to verify the mate spin. The wildcard "sha256sum -c *-CHECKSUM" command gives you way too much output, there's lots of failed notices about the other spins you don't have, with yours buried somewhere in the middle. Surely there's a better way to filter that down to just show the output of files its actually checking, rather than all the files it looked for. I've gone through three different webpages just to verify one download. -- uname -rsvp Linux 3.10.0-1160.45.1.el7.x86_64 #1 SMP Wed Oct 13 17:20:51 UTC 2021 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list.

2 1

NFS mount lockups since about a month ago
by Terry Barnaby 30 Oct '21

30 Oct '21

Hi, I use NFS mount (defaults so V4) /home directories with a simple server over Gigabit Ethernet all running Fedora33. This has been working fine for 25+ years through various Fedora versions. However in the last month or so all of the client computers are getting KDE GUI lockups every few hours that last for around 40 secs. /home is not accessible during this time and it feels/looks to be an NFS lockup issue. There are no "NFS server no responding" or such like messages in either the servers or clients /var/log/messages and the network communications seems fine. 1. Have there been some changes to NFS recently in the kernel ? 2. Any idea where to begin to try and debug this ? Terry

9 39

← Newer
1
2
3
4
5
6
7
...
11
Older →