users March 2024

users@lists.fedoraproject.org

61 participants
45 discussions

Re: Configuring LXC containers
by Patrick O'Callaghan 11 Mar '24

11 Mar '24

On Sun, 2024-03-10 at 19:37 -0700, Mike Wright wrote: > On 3/10/24 15:40, Patrick O'Callaghan wrote: > > On Sun, 2024-03-10 at 11:13 -0700, Mike Wright wrote: > > > The last two lines are key. Add these flags: -F -o logfile. The > > > default loglevel is ERROR. If you want more detail include -l > > > LEVEL. > > > > > > e.g. lxc-start -n containerName -F -o containerName.log -l WARN > > > > > > > This is what I get: > > > > $ lxc-start -n test -F -o test.log -l WARN > ... > > lxc-start test 20240310223702.945 ERROR start - > > start.c:print_top_failing_dir:99 - Permission denied - Could not > > access /home/poc/.local. Please grant it x access, or add an ACL > > for the container root > > This one looks interesting > $ ls -ld /home/poc/.local drwx------. 1 poc poc 56 Aug 28 2021 /home/poc/.local IOW, it already has x access (and lxc-start is not setuid so it's running as me). poc

1 0

Marble problem: libicui18n.so.69
by ToddAndMargo 11 Mar '24

11 Mar '24

# dnf install marble Last metadata expiration check: 0:58:05 ago on Sat 09 Mar 2024 09:03:09 PM PST. Dependencies resolved. ================================================================================ Package Architecture Version Repository Size ================================================================================ Installing: marble x86_64 1:23.08.5-1.fc39 updates 188 k Transaction Summary ================================================================================ Install 1 Package Total download size: 188 k Installed size: 585 k Is this ok [y/N]: y Downloading Packages: marble-23.08.5-1.fc39.x86_64.rpm 186 kB/s | 188 kB 00:01 -------------------------------------------------------------------------------- Total 114 kB/s | 188 kB 00:01 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : marble-1:23.08.5-1.fc39.x86_64 1/1 Running scriptlet: marble-1:23.08.5-1.fc39.x86_64 1/1 Verifying : marble-1:23.08.5-1.fc39.x86_64 1/1 Installed: marble-1:23.08.5-1.fc39.x86_64 Complete! root@rn6:/home$ marble marble: error while loading shared libraries: libicui18n.so.69: cannot open shared object file: No such file or directory

7 21

Virtualization: Windows 32-bit i686 guest not working on Fedora 39 x86_64 ?
by Franta Hanzlík 10 Mar '24

10 Mar '24

After 'dnf system-upgrade...' my machine from F37 x86_64 to F39, win7-32 guest did not start due to BSOD 0x0000007B boot problem, while win10 64-bit works fine on the same machine. I then tried: - a newly created virtual machine consisting only of Win7-32 or Win10-32 installation ISO image freezes after start on the first inquiry window - the keyboard and mouse do not respond. - the same way created virtual win10 64-bit installation CD ISO works correctly. - I received the same behavior on a cleqan, freshly installed F39 system - Win7 or Win10 32-bit did not work, but 64-bit without problems. - on a new installation of F38 - Win7 guest works without problems, as well as both guest installations of 32-bit windows from the CD ISO image. On F38 is libvirt-daemon-9.0.0-4.fc38.x86_64 + qemu-kvm-7.2.8-1.fc38.x86_64 On F39 is libvirt-daemon-9.7.0-2.fc39.x86_64 + qemu-kvm-8.1.3-4.fc39.x86_64 Does anyone have any idea where the problem could be? -- Thanks, Franta Hanzlik

1 0

Strange issue with name resolution systemd-resolved.service - Network Name Resolution
by Michael D. Setzer II 08 Mar '24

08 Mar '24

Currently in Nevada accessing 4 of my computers back in Guam. Has been working fine, until earlier today. VNC into the machines using same name of router, but different ports mapped to machines. Generally login to each one, and then next with no problem. But today, got error messages that couldn't resolve names. then tried dig on name and got similar timeout problem with it. Tried restarting service, and that would work for a while, but then it would give error again. IP is a dyndns.org address, so it can change, but very seldom. Added the address to /etc/hosts and then problem went away completely. Connections made with no problem. Works, unless IP changes. Don't know if something was changed with service recently, or if their is some way to have it have a backup if the 127.0.0.53 isn't working? Just says timedout? Any options to optimize things to prevent this? Have also seen a similare issue running dnf updates. Sometimes it reports that it can't resolve names of repos? Note: Cox is ISP where I'm located, so don't know. The speed is good, getting 175+M down, and about 11M up. Long ago use to use multiple name servers including 8.8.8.8, but then at somepoint it changed to the 127.0.0.53 thing. Thanks. +------------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:mikes@guam.net mailto:msetzerii@gmail.com mailto:msetzerii@gmx.com Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ +------------------------------------------------------------+

2 1

Fedora Linux 40 i18n test week 2024-03-05 through 2024-03-11
by Sumantro Mukherjee 02 Mar '24

02 Mar '24

Hey Folks, We will be having a Fedora Linux 40 i18n test week starting 2024-03-05. The wiki[0] has all the information on participating in the test week. You can grab the choice of your image [Workstation/Silverblue/Kionite] from this page[1] We look forward to the results and feedback! Thank You [0] http://fedoraproject.org/wiki/Test_Day:2024-03-05_I18N_Test_Day [1] https://www.happyassassin.net/nightlies.html -- //sumantro Fedora QE TRIED AND PERSONALLY TESTED, ERGO TRUSTED

1 0