users November 2020

users@lists.fedoraproject.org

127 participants
147 discussions

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

xournal++ dev
by Patrick Dupre 25 Nov '20

25 Nov '20

Hello, I am not sure that it is the right list to post it, but there is a development version of xournalpp 1.1 which is not available in fedora Is there a chance to have it soon? Actually, I have not been able to get the sources. =========================================================================== 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 ===========================================================================

1 0

Keyboard switches to US keyboard after each reboot
by Joachim Backes 25 Nov '20

25 Nov '20

Hi, I'm running F33 with Cinnamon/German nodeadkeys keyboard layout. Having the problem that after each reboot the keyboad layout switches to US layout. Workaround (not permanent; valid until next reboot): "loadkeys de" in some console windowd (Ctrl Fx ...) Anybody sees a solution for this problem? Kind regards -- Fedora release 33 (Thirty Three) Kernel-5.9.11-200.fc33.x86_64 Joachim Backes <joachim.backes(a)rhrk.uni-kl.de> https://www-user.rhrk.uni-kl.de/~backes/

1 1

Bricked system after migrating to thin LVMs
by Sreyan Chakravarty 25 Nov '20

25 Nov '20

Hi, I have cloned my original root LVM, and then migrated to the newer thin LVMs using partclone. Both backup and restore went off without causing any problems. But when I am now trying to boot into my system, it asks for the encryption LUKS passphrase but after that I am getting: dracut-initqueue[300]: Warning: dracut-initqueue timeout - starting timeout scripts I have not changed anything. Even my logical volume name is the same as before. These are the backup and restore commands that I have used from the Fedora live environment: (Creating the backup) # partclone.ext4 -c -s /dev/vgfedora/fedora | gzip -c --best > /run/media/liveuser/externalhdd/fedora.tar.gz (Restoring the backup) # gzip -c -d /run/media/externalhdd/fedora.tar.gz | partclone.ext4 -r -o /dev/vgfedora/fedora These commands were run as root from Fedora live environment and prior to taking my backup I had set my logical volume to read-only via: # lvchange -pr vgfedora/fedora This is my current volume group and logical volumes: # lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert fedora vgfedora Vwi-a-tz-- 700.00g pool00 16.61 pool00 vgfedora twi-aotz-- 929.75g 12.50 16.61 # vgs VG #PV #LV #SN Attr VSize VFree vgfedora 1 2 0 wz--n- 929.99g 8.00m This is my /etc/fstab: /dev/mapper/vgfedora-fedora / ext4 defaults,x-systemd.device-timeout=0 1 1 UUID=4d112d8e-080d-44f2-8962-9c13f20a7885 /boot ext4 defaults 1 2 UUID=041A-E511 /boot/efi vfat defaults,uid=0,gid=0,umask=077,shortname=winnt 0 2 /fedora.swap none swap defaults 0 2 I have not changed the /etc/fstab after the migration since nothing has changed. /dev/mapper/vgfedora-fedora still exists. The only difference is that it is a thin LVM volume. This is my GRUB_CMDLINE: GRUB_CMDLINE_LINUX="rd.luks.uuid=luks-2ec7f1ae-6f9b-4896-a7b2-be7809e9d2f4 rd.lvm.lv=vgfedora/fedora resume=/dev/disk/by-uuid/03aef3ba-dca1-4cba-a3f5-36c5c0fe948e resume_offset=1449984" The UUID of the LUKS encryption is still the same, as I can confirm from here : # ll /dev/disk/by-uuid/ # lrwxrwxrwx. 1 root root 10 Nov 24 03:38 2ec7f1ae-6f9b-4896-a7b2-be7809e9d2f4 -> ../../sda3 I don't know what else I have to change, or what is going wrong. Grub is asking for the password for LUKS and is setting up the encrypted partition, but after that nothing happens. I guess it is not able to load the root logical volume. Do I have to re-generate my initramfs ? I didn't think that would be necessary since the LVM thin tools were already installed. Please let me know if any other info is required from my side. Need some help as I am unable to use my laptop. -- Regards, Sreyan Chakravarty

3 6

Fedora-33 No Sound
by Bob Goodwin 24 Nov '20

24 Nov '20

In a new install of Fedora-33 desktop I have no sound. I have fiddled with the problem for several days to no avail so I guess I need to ask for help. PA Volume appears to get an input but i see no output ... The system had sound with the previous install which was removed when anaconda did the present install. Any ideas, suggestions, whatever? Bob -- Bob Goodwin - Zuni, Virginia, USA FEDORA-32/64bit LINUX XFCE Fastmail POP3

4 7

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

Jump to page: