users November 2020

users@lists.fedoraproject.org

127 participants
151 discussions

F32 --> F33 upgrade fails .
by Kostas Sfakiotakis 29 Nov '20

29 Nov '20

Greetings , Upon trying to download the files in order to be able to upgrade from F32 to F33 i get the following errors Error: Problem 1: package openssh-ldap-8.3p1-3.fc32.x86_64 requires openssh = 8.3p1-3.fc32, but none of the providers can be installed - openssh-8.3p1-3.fc32.x86_64 does not belong to a distupgrade repository - problem with installed package openssh-ldap-8.3p1-3.fc32.x86_64 Problem 2: package tomahawk-0.8.4-23.fc31.x86_64 requires libboost_filesystem.so.1.69.0()(64bit), but none of the providers can be installed - boost-filesystem-1.69.0-18.fc32.x86_64 does not belong to a distupgrade repository - problem with installed package tomahawk-0.8.4-23.fc31.x86_64 (try to add '--skip-broken' to skip uninstallable packages) The thing is that even if i try to use the --skip-broken option the download of the files will not begin either . Now apart from deleting the offending packages , trying the upgrade and then reinstalling them is there anything else that i can try ???

3 5

Why is only 11 GB used of my 12 GB swap file ?
by Sreyan Chakravarty 27 Nov '20

27 Nov '20

Hi, I have created my swap file using the command: dd if=/dev/zero of=/fedora.swap bs=1M count=12288 status=progress So this should produce a 12 GB file right ? I can confirm it does: $ ls -lh /fedora.swap -rw-------. 1 root root 12G Nov 27 20:23 /fedora.swap So why is the swap memory in my system reported as 11 GB by the free command ? $ free -h total used free shared buff/cache available Mem: 7.7Gi 1.4Gi 4.5Gi 394Mi 1.8Gi 5.6Gi Swap: 11Gi 0B 11Gi Why is it 11 GB ? Shouldn't it be 12 GB ? Am I missing something? What is the reason for this? -- Regards, Sreyan Chakravarty

4 8

Sync rpms with other computer
by Mayavimmer 27 Nov '20

27 Nov '20

How do I sync rpm packages with another computer? I have a list of the remote's rpms generated with "rpm -qa". I expect to have to modify a couple of packages in the list due to hardware dependent rpms like xorg. Otherwise it should be a simple matter of downloading the rpms from the edited list and then installing them. Or is there already a script for this?

3 5

Is TRIM or DISCARD needed for regular HDDs
by Sreyan Chakravarty 27 Nov '20

27 Nov '20

Hi, I am confused about whether I should use TRIM or DISCARD on my laptop. I use LVM on top of LUKS and I do make frequent use of snapshots. Merging them to my root volume. I have a regular HDD and not a SSD. Will enabling TRIM and DISCARD help me? If so, how do I do that ? I have already tried enabling: issue_discards=1 in /etc/lvm/lvm.conf and then dracut -f But fstrim -v / still fails with : fstrim: /: the discard operation is not supported So how do I enable it in Fedora32 ? -- Regards, Sreyan Chakravarty

4 17

Read-only flash drives
by Joe Zeff 26 Nov '20

26 Nov '20

Every now and then I buy a flash drive and find that when I mount it it's owned by root and read only except by root. I can, of course, change that by using chown and chmod, but that only lasts until I unmount the drive. Generally, I need to reformat the drive to get it working properly. And, it's not just Fedora; my sister uses Xubuntu, and has the same issue. Does anybody know a way to keep this from happening, or to fix it without reformatting?

6 19

virt-install fails with F33 with "Failed to start Switch Root"
by Michal Schorm 26 Nov '20

26 Nov '20

Hello, I am deploying VMs via kickstart files, so the process can be completely non-interactive. Right now I'm stuck with Fedora 33. The following command works completely fine on F32, F31 and so on, but not F33. Can you please help me fix it? virt-install \ --connect qemu:///system \ --network bridge:virbr0 \ --initrd-inject /var/local/minimal.ks \ --name test_name_3 \ --disk /VMs/test_name_3.qcow2,size=10,format=qcow2 \ --memory 2048 \ --location https://download.fedoraproject.org/pub/fedora/linux/releases/32/Server/x86_… \ --hvm --vcpus=2 --check-cpu --accelerate \ --graphics none \ --extra-args 'ks=file:/minimal.ks console=tty0 console=ttyS0,115200' Just change the URL to point to F33 repo. It will fail, after the whole installation is complete and the VM should start one last time, with following error: Failed to start Switch Root. Failed to switch root: Specified switch root path '/sysroot' does not seem to be an OS tree. os-release file is missing. I checked that the file "/etc/os-release" is in place and populated. I uploaded the used Kickstarter file, as well as some logs here: https://gitlab.com/Faramos/vm/-/snippets/2042979 I also tried to force installation with EXT4 partitions (instead of F33 default BTRFS), but it hasn't made any difference. Nothing else in https://fedoraproject.org/wiki/Category:ChangeAcceptedF33 seems suspicous to me. I am using an F32 host. -- Michal Schorm Software Engineer Core Services - Databases Team Red Hat --

2 1

RE: Read-only flash drives
by J.Witvliet＠mindef.nl 26 Nov '20

26 Nov '20

-----Original Message----- From: Tim via users <users(a)lists.fedoraproject.org> Sent: Thursday, November 26, 2020 10:40 AM To: users(a)lists.fedoraproject.org Cc: Tim <ignored_mailbox(a)yahoo.com.au> Subject: Re: Read-only flash drives On Thu, 2020-11-26 at 07:36 +0000, J.Witvliet--- via users wrote: > Once in a while we come across thumb-drives, that after using a couple > of times, can’t even be reformatted. Some people leave them plugged in all the time, and although they think only that they're using them occasionally, they're getting warm from whatever their computer was doing in the background. I view thumb drives as some temporary media for sneakernetting, I'd never rely on them for storage. But, I wonder, those having trouble with them: Are they buying the cheap and nasty ones? -----Original Message----- Not intended to steal the thread, But do you consider "Kingston DT50, 16GB USB3" cheap & nasty? We use them as boot-device, filling them with a image with "dd" Upto now, we considered them bricked, and threw them away. Next time I'll ask to keep them for further analysis. Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.

1 0

Re: Read-only flash drives
by J.Witvliet＠mindef.nl 26 Nov '20

26 Nov '20

You’re still lucky. Once in a while we come across thumb-drives, that after using a couple of times, can’t even be reformatted. From: "Joe Zeff" <joe(a)zeff.us<mailto:joe@zeff.us>> Date: Thursday, 26 November 2020 at 00:02:35 To: "Community support for Fedora users" <users(a)lists.fedoraproject.org<mailto:users@lists.fedoraproject.org>> Subject: Read-only flash drives Every now and then I buy a flash drive and find that when I mount it it's owned by root and read only except by root. I can, of course, change that by using chown and chmod, but that only lasts until I unmount the drive. Generally, I need to reformat the drive to get it working properly. And, it's not just Fedora; my sister uses Xubuntu, and has the same issue. Does anybody know a way to keep this from happening, or to fix it without reformatting? _______________________________________________ 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 Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het elektronisch verzenden van berichten. This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.

2 1

Strange pause after running gedit from regular text terminal window.
by Michael D. Setzer II 26 Nov '20

26 Nov '20

The pause varies in time, and sometimes shows message and sometimes doesn't?? Example $:gedit gccdirectory.1126 (org.gnome.gedit:4156283): Gtk-WARNING **: 07:13:25.756: Calling org.xfce.Session.Manager.Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method “Inhibit” Get no response for about 5 or more seconds (but varies) Pressing up arrow key to pull up the previous commands. Then it will respond with all the keys pressed after the pause. Installed geany and did the same kind of process with the same files, and it never shows the pause or error messages. Running xfce desktop. +------------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:mikes@guam.net mailto:msetzerii@gmail.com Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ +------------------------------------------------------------+

1 0

Re: NFS Problems in Fedora 33
by Ed Greshko 25 Nov '20

25 Nov '20

On 26/11/2020 03:36, Robert wrote: > My fstab entry is as follows. > 192.168.2.100:/STUF/STUFF /home/me/STUFF nfs rw 0 0 OK. Using just nfs on the fstab entry would mean that it should use the default protocol on the server. I am using a Centos7 server that hasn't been modified. So, nfs-v4 is being used. You can verify this by using "df -T" on the client. Also, you should check the server's /etc/nfs.conf to make sure no modifications have been made. The default is.... #[nfsd] # debug=0 # threads=8 # host= # port=0 # grace-time=90 # lease-time=90 # udp=y # tcp=y # vers2=n # vers3=y # vers4=y # vers4.0=y # vers4.1=y # vers4.2=y # rdma=n > My 'hosts.allow files is as follows: > > portmap: 192.168.2.100 # 192.168.2.100 is the Data Server > rquotad: 192.168.2.100 > mountd: 192.168.2.100 > statd: 192.168.2.100 I do not use "hosts.allow" onn my systems. > Do you have 'selinux' running? Oh, yes. I only disable selinux if I need to troubleshoot. > I am not sure just how to find out which version I am running. > I assume you mean on the client when you ask about 'Can you switch to mounting NFS-v4?' I think I covered that above. Using "df -T" will show nfs4 if the mounted share is using V4. Also, I think you indicated that you have some things sym linked on the client side? Could you try and open files which are directly on the mount point as opposed to the sym link location? --- The key to getting good answers is to ask good questions.

1 0

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

Jump to page: