users June 2021

users@lists.fedoraproject.org

93 participants
90 discussions

by Robert McBroom

Getting strange messages during an update. /usr/lib/tmpfiles.d/kdm.conf:1: Line references path below legacy directory /var/run/, updating /var/run/kdm/ → /run/kdm/; please update the tmpfiles.d/ drop-in file accordingly. /usr/lib/tmpfiles.d/kdm.conf:2: Line references path below legacy directory /var/run/, updating /var/run/xdmctl → /run/xdmctl; please update the tmpfiles.d/ drop-in file accordingly. What do these mean and how can they be fixed?

2 years, 10 months

4
3
0 / 0

mpi-default-bin

by Patrick Dupre

Hello, I am looking for mpi-default-bin and mpi-default-dev for fedora These packages are available for ubuntu and debian. What do you suggest? =========================================================================== Patrick DUPRÉ | | email: pdupre(a)gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988 | | Room# D114A ===========================================================================

2 years, 10 months

2
1
0 / 0

Millions of temp files in .gnome2/keyrings

by Meikel

Hi folks, I have a problem with Gnome-Keyrings, my filesystem seems to be flooded by millions of *.keyring.temp-* files in directory .gnome2/keyrings. I have a home server (CentOS 8) where the files are located. On my workstation (Fedora 33 XFCE Spin) I mount it via autofs and sshfs into the /home-Directory. I do not have a good understanding of what Gnome Keyrings does, but in my eyes I have a "standard" installation, I can' t remember that I did something that brought it onto my workstation, I expect that Gnome Keyring was already there after the initial installation of the workstation. Because the file system on the workstation is mounted from a server my problem might be caused by any restrictions on the server (i.e. SELinux or whatever), but because it is mounted via sshfs I expect that the server is "innocent" as far as an ssh from the workstation to the server works. For that reason I post to the Fedora mailing list. I did some investigation that shows, that at probably random points in time each time 64999 temp files are create in .gnome2/keyrings, so after some minutes I have millions of files there. Following my analysis. Workstation: The OS version is cat /etc/redhat-release Fedora release 33 (Thirty Three) and just for completeness, but probably not important, the XFCE version is xfce4-about -V xfce4-about 4.14.1 (Xfce 4.14) ... SSH from workstation to server works fine ssh sysadmin@server3 "ls -d ~/disk1/home_meikel" /home/sysadmin/disk1/home_meikel and the file system is mounted LANG="" df -h /home/meikel Filesystem Size Used Avail Use% Mounted on sysadmin@server3:/home/sysadmin/disk1/home_meikel/ 1007G 747G 210G 79% /home/meikel After some minutes/hours of working on the workstation the directory .gnome2/keyrings/ seems to be flooded by hundred of thousands of temp files, the directory listing takes about one and a half minute (!!!): cd /home/meikel time ls -l .gnome2/keyrings/ | wc -l 247263 real 1m28,358s user 0m4,642s sys 0m3,831s Home-Server (via ssh): The OS version is cat /etc/redhat-release CentOS Linux release 8.4.2105 After some time (this example was taken during the same day, some hours later) the situation is the same, meanwhile there are some millions of temp files: cd /home/sysadmin/disk1/home_meikel/.gnome2/keyrings/ time ls -l | wc -l 2804719 real 0m49,023s user 0m27,330s sys 0m22,120s Further investigation: To understand what are those millions of files I did a ls -l .gnome2/keyrings/ > /tmp/gnome-keyrings-3.txt and some further manually investigation. Following I give the beginning of /tmp/gnome-keyrings-3.txt where I manually replaced multiple occurrences of the same line by "--> xxx times". There seems to be a pattern where in each point of time it tries for 64999 times to create a temp file: total 10438868 -rw-------. 64999 sysadmin sysadmin 1162 Jun 5 20:39 Trousseau_de_clés_par_défaut_9.keyring.temp-1000041255 -rw-------. 64999 sysadmin sysadmin 1162 Jun 5 20:39 --> 64997 times -rw-------. 64999 sysadmin sysadmin 1162 Jun 5 20:39 Trousseau_de_clés_par_défaut_9.keyring.temp-1000072888 -rw-------. 64999 sysadmin sysadmin 1162 Jun 5 19:35 Trousseau_de_clés_par_défaut_9.keyring.temp-100000967 -rw-------. 64999 sysadmin sysadmin 1162 Jun 5 19:35 --> 64997 times -rw-------. 64999 sysadmin sysadmin 1162 Jun 5 19:35 Trousseau_de_clés_par_défaut_9.keyring.temp-1000037381 -rw-------. 64999 sysadmin sysadmin 1162 Jun 5 19:32 Trousseau_de_clés_par_défaut_9.keyring.temp-1000014039 -rw-------. 64999 sysadmin sysadmin 1162 Jun 5 19:32 --> 64997 times -rw-------. 64999 sysadmin sysadmin 1162 Jun 5 19:32 Trousseau_de_clés_par_défaut_9.keyring.temp-1000058050 -rw-------. 64999 sysadmin sysadmin 1162 Jun 5 18:42 Trousseau_de_clés_par_défaut_9.keyring.temp-1000006582 -rw-------. 64999 sysadmin sysadmin 1162 Jun 5 18:42 --> 64997 times -rw-------. 64999 sysadmin sysadmin 1162 Jun 5 18:42 Trousseau_de_clés_par_défaut_9.keyring.temp-1000149586 ... many more ... The word "Trousseau_de_clés_par_défaut" (it is french) means something like "default keyring". To find a pattern in the timestamps to understand when those temp files are created I ran cut -c 42-53 gnome-keyrings-3.txt | sort | uniq Jun 2 07:28 ... Jun 5 10:52 ... May 22 08:12 ... May 28 08:35 but due to the "sort" the result is now unsorted (!!!), there is a break in the sorting between June and May. I' m not sure if I really need to sort before uniq-ify the output. As it' s a result of "ls -l" it might already be sorted by timestamp. However I need a further step to sort output by timestamp, so I ran cut -c 42-53 gnome-keyrings-3.txt | sort | uniq | while read d ; do date +%s -d "${d}" ; done | sort | while read d ; do date -d @${d} ; done sam. 22 mai 2021 08:12:00 CEST sam. 22 mai 2021 08:21:00 CEST sam. 22 mai 2021 13:45:00 CEST dim. 23 mai 2021 09:18:00 CEST mar. 25 mai 2021 07:44:00 CEST mar. 25 mai 2021 07:59:00 CEST mar. 25 mai 2021 08:06:00 CEST mer. 26 mai 2021 07:43:00 CEST jeu. 27 mai 2021 07:45:00 CEST jeu. 27 mai 2021 08:22:00 CEST ven. 28 mai 2021 08:34:00 CEST ven. 28 mai 2021 08:35:00 CEST mer. 02 juin 2021 07:28:00 CEST mer. 02 juin 2021 07:31:00 CEST mer. 02 juin 2021 07:42:00 CEST mer. 02 juin 2021 07:47:00 CEST mer. 02 juin 2021 07:49:00 CEST sam. 05 juin 2021 10:52:00 CEST sam. 05 juin 2021 10:56:00 CEST sam. 05 juin 2021 10:57:00 CEST sam. 05 juin 2021 11:00:00 CEST sam. 05 juin 2021 11:04:00 CEST sam. 05 juin 2021 11:07:00 CEST sam. 05 juin 2021 11:11:00 CEST sam. 05 juin 2021 11:14:00 CEST sam. 05 juin 2021 11:19:00 CEST sam. 05 juin 2021 11:22:00 CEST sam. 05 juin 2021 11:28:00 CEST sam. 05 juin 2021 11:32:00 CEST sam. 05 juin 2021 11:40:00 CEST sam. 05 juin 2021 11:43:00 CEST sam. 05 juin 2021 11:53:00 CEST sam. 05 juin 2021 11:56:00 CEST sam. 05 juin 2021 12:09:00 CEST sam. 05 juin 2021 12:12:00 CEST sam. 05 juin 2021 12:27:00 CEST sam. 05 juin 2021 12:30:00 CEST sam. 05 juin 2021 12:47:00 CEST sam. 05 juin 2021 12:50:00 CEST sam. 05 juin 2021 13:11:00 CEST sam. 05 juin 2021 13:14:00 CEST sam. 05 juin 2021 13:38:00 CEST sam. 05 juin 2021 13:41:00 CEST sam. 05 juin 2021 14:09:00 CEST sam. 05 juin 2021 14:12:00 CEST sam. 05 juin 2021 14:40:00 CEST sam. 05 juin 2021 14:43:00 CEST sam. 05 juin 2021 15:22:00 CEST sam. 05 juin 2021 15:25:00 CEST sam. 05 juin 2021 16:01:00 CEST sam. 05 juin 2021 16:04:00 CEST sam. 05 juin 2021 16:49:00 CEST sam. 05 juin 2021 16:51:00 CEST sam. 05 juin 2021 17:41:00 CEST sam. 05 juin 2021 17:44:00 CEST sam. 05 juin 2021 18:38:00 CEST sam. 05 juin 2021 18:42:00 CEST sam. 05 juin 2021 19:32:00 CEST sam. 05 juin 2021 19:35:00 CEST sam. 05 juin 2021 20:39:00 CEST So at each of these timestamps the number of 64999 temp files is created in .gnome2/keyrings. I can't see any pattern in those points of time, I don't understand for what reason there need to be created the temp files at theses times and why always 64999 times at the same moment. From time to time I manually delete the files by running (as root) find . -name "*.temp-*" -delete which is not really satisfying. Any ideas what is the reason that these millions of temp files are created? Why do I need Gnome Keyrings? Can I get rid of that software to solve the problem? Regards, Meikel

2 years, 10 months

5
9
0 / 0

Persistent mdev configuration

by Danishka Navin

Is it possible to add persistent mdev config? Regards, Danishka

2 years, 10 months

1
0
0 / 0

Firefox 89?

by Neal Becker

I've been reading about firefox 89 and wanted to check it out. I'm on F34. Doesn't seem to be in updates-testing. Let's try rawhide: sudo dnf --enablerepo=rawhide update firefox I Dependencies resolved. ================================================================================================= Package Architecture Version Repository Size ================================================================================================= Upgrading: firefox x86_64 89.0-1.fc35 rawhide 103 M Transaction Summary ================================================================================================= Upgrade 1 Package Total download size: 103 M Is this ok [y/N]: y Downloading Packages: firefox-89.0-1.fc35.x86_64.rpm 6.0 MB/s | 103 MB 00:17 ------------------------------------------------------------------------------------------------- Total 5.9 MB/s | 103 MB 00:17 warning: /var/cache/dnf/rawhide-2d95c80a1fa0a67d/packages/firefox-89.0-1.fc35.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID 9867c58f: NOKEY Fedora - Rawhide - Developmental packages for the next Fedora re 796 kB/s | 1.6 kB 00:00 GPG key at file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-34-x86_64 (0x45719A39) is already installed Fedora - Rawhide - Developmental packages for the next Fedora re 1.6 MB/s | 1.6 kB 00:00 Importing GPG key 0x38AB71F4: Userid : "Fedora (36) <fedora-36-primary(a)fedoraproject.org>" Fingerprint: 53DE D2CB 922D 8B8D 9E63 FD18 999F 7CBF 38AB 71F4 From : /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-36-x86_64 Is this ok [y/N]: y Key imported successfully Import of key(s) didn't help, wrong key(s)? Public key for firefox-89.0-1.fc35.x86_64.rpm is not installed. Failing package is: firefox-89.0-1.fc35.x86_64 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-34-x86_64, file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-36-x86_64 The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Error: GPG check FAILED I don't think I want to install if gpg check failed.

2 years, 10 months

4
6
0 / 0

off-topic mouse question

by Tim

Does anybody know of a mouse with a scroll wheel that's not rubber coated? I have a latex allergy, getting really sick of the skin irritation, and I'm not having a great deal of luck researching this. Most mice don't state what they're made of. Yes, I do want a scroll wheel mouse and not a trackball. They have their purposes, but don't suit what I generally want to do. -- uname -rsvp Linux 3.10.0-1160.25.1.el7.x86_64 #1 SMP Wed Apr 28 21:49:45 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 years, 10 months

4
3
0 / 0

first axfr challenges

by Jack Craig

*i am getting a notauth on my axfr attempt. what i am not seeing is an A ip# for the secondary dns server.* *is this missing A record a problem i need to fix for following host cli???* *dig @ws.linuxlighthouse.com <http://ws.linuxlighthouse.com> axfr linuxlighthouse.com <http://linuxlighthouse.com>* ; <<>> DiG 9.11.28-RedHat-9.11.28-1.fc32 <<>> @ws.linuxlighthouse.com axfr linuxlighthouse.com ; (1 server found) ;; global options: +cmd linuxlighthouse.com. 259200 IN SOA ws.linuxlighthouse.com. root.linuxlighthouse.com. 2021051603 86400 7200 3600000 172800 linuxlighthouse.com. 259200 IN A 108.220.213.121 linuxlighthouse.com. 259200 IN CAA 0 issue "letsencrypt.org" linuxlighthouse.com. 259200 IN NS ws.linuxlighthouse.com. *linuxlighthouse.com <http://linuxlighthouse.com>. 259200 IN NS ns2.swbell.net <http://ns2.swbell.net>.* ws.linuxlighthouse.com. 259200 IN A 108.220.213.121 www.linuxlighthouse.com. 259200 IN A 108.220.213.121 linuxlighthouse.com. 259200 IN SOA ws.linuxlighthouse.com. root.linuxlighthouse.com. 2021051603 86400 7200 3600000 172800 ;; Query time: 1 msec ;; SERVER: 108.220.213.121#53(108.220.213.121) ;; WHEN: Mon May 17 12:43:43 PDT 2021 ;; XFR size: 8 records (messages 1, bytes 284) *[jackc@ws ~ $ host -t axfr ns2.swbell.net <http://ns2.swbell.net> ws.linuxlighthouse.com <http://ws.linuxlighthouse.com>* Trying "ns2.swbell.net" Using domain server: Name: ws.linuxlighthouse.com Address: 108.220.213.121#53 Aliases: Host ns2.swbell.net not found: 9(NOTAUTH) ; Transfer failed. [jackc@ws ~ $

2 years, 10 months

5
13
0 / 0

Speaking of log spamming, I see nmb spam

by Tom Horsley

Checking for spam from NM, I instead found this nonsense: Jun 6 00:01:19 zooty nmbd[2999]: [2021/06/06 00:01:19.675514, 0] ../../source3/libsmb/nmblib.c:923(send_udp) Jun 6 00:01:19 zooty nmbd[2999]: Packet send failed to 192.168.2.255(137) ERRNO=Operation not permitted That 192.168.2 network isn't really there, it is a bridge setup that has nothing connected except for some special virtual machines that sometimes use it but are almost never running. So I found the interfaces config options for smb.conf and made those messages stop, but the web is full of info telling me I no longer need netbios on Windows 10, yet when I stop the nmb service, my Windows 10 virtual machine cannot mount the shares it normally mounts from my fedora box. Anyone know if it is really possible to get rid of nmb? (The only systems mounting shares are windows 10.)

2 years, 10 months

1
2
0 / 0

remove unallocated partition

by Patrick Dupre

Hello, On one disk, I have an extended partition (sdc4) starting at 41338880 Inside, I have a ext4 partition (sdc5) starting at 53919744 (see attached file) In between the space is unallocated How can I make that the partition sdc4 starts just at the beginning of sdc5 Thanks =========================================================================== Patrick DUPRÉ | | email: pdupre(a)gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988 | | Room# D114A ===========================================================================

2 years, 10 months

3
4
0 / 0

network manager spamming logs with repetitive messages

by Frank

I noticed this morning that network manager is spamming my log with messages repeated every 3 or 4 seconds. Jun 06 11:58:22 localhost.localdomain NetworkManager[787]: <info> [1622995102.8297] policy: set-hostname: current hostname was changed outside NetworkManager: fedora Jun 06 11:58:22 localhost.localdomain NetworkManager[787]: <info> [1622995102.8299] policy: set-hostname: set hostname to localhost.localdomain (from address lookup) It repeats these messages every 3 or 4 seconds. This apparently has been going on for a few days at least. There is a bug 1894137 - But it was filed last November. Anyone have any suggestions ?

2 years, 10 months

4
10
0 / 0

← Newer
1
2
3
4
5
6
7
8
9
Older →