users May 2022

users@lists.fedoraproject.org

91 participants
81 discussions

Foliate does not work
by Paul Smith 29 May '22

29 May '22

Dear All, I cannot be sure, but I suspect that after having upgraded to F36, Foliate no longer works. Any ideas? Do others experience the same problem? Thanks in advance, Paul

3 12

Frequent Crashes with Puddletag
by Steven P. Ulrick 27 May '22

27 May '22

Hello Everyone, I am running Fedora 36, fully updated as of right now... I am running version 2.1.1-1 of puddletag. That is the most recent version of puddletag in the official Fedora repo. I have had puddletag crash on multiple occasions since I started running this version under Fedora 36. I have not been able to narrow down anything that I am doing when the crashes occur that would help narrow things down. Anybody else having issues like this? If not, any advice on how to debug/troubleshoot this issue? There is one bug on the Fedora Bugzilla for puddletag: https://bugzilla.redhat.com/show_bug.cgi?id=2084341 but since puddletag crashes silently, and without invoking ABRT, I have no idea if that report has anything to do with my issue. Thank you, Steven P. Ulrick

4 9

F36 kernel (packaging) problems?
by Adrian Sevcenco 27 May '22

27 May '22

Hi! I have a very strange situation after i updated my system to fedora 36: the new 5.17.9-300.fc36.x86_64 does not boot or at least cannot start my monitor (i get on the monitor "no signal received") while the identical fedora 35 one worrks 5.17.9-200.fc35.x86_64 having an nvidia card, i checked that i have kmods for both kernels root@hal: entries # rpm -qa | grep kmod-nvidia akmod-nvidia-515.43.04-1.fc36.x86_64 kmod-nvidia-5.17.9-200.fc35.x86_64-515.43.04-1.fc36.x86_64 kmod-nvidia-5.17.9-300.fc36.x86_64-515.43.04-1.fc36.x86_64 and my GRUB_CMD_LINE looks like this: GRUB_CMDLINE_LINUX="acpi_osi='Windows 2013' acpi_enforce_resources=lax iommu=soft iomem=relaxed quiet mitigations=off libahci.ignore_sss=1 root=/dev/md1 rootfstype=ext4 selinux=0 rd.plymouth=0 plymouth.enable=0 rd.auto rd.md=1 rd.dm=1 rd.lvm=0 rd.luks=0 rd.vconsole.font=ter-v32n KEYTABLE=us LANG=en_US.UTF-8 rd.driver.blacklist=nouveau modprobe.blacklist=nouveau" any idea why f36 kernel would not work and how can i troubleshoot this? Thanks a lot! Adrian

3 5

Dropbox and Fedora 36
by Terry Polzin 26 May '22

26 May '22

Dropbox seems to get stuck "connecting" starting on login or any manual start. How do I diagnose this?

2 4

Re: ssh infested by systemd.resolved
by Jonathan Billings 25 May '22

25 May '22

On Apr 23, 2022, at 22:36, Stephen J. Turnbull <stephen(a)xemacs.org> wrote: > As far as I know there isn't really a technical argument for systemd > or any particular systemd.* on Fedora workstations. The various > traditional inits and daemons work fine in that environment.[1] There are several features in systemd that directly benefit the desktop. 1.) systemd service dependencies can ensure that the desktop environment doesn’t launch until all dependencies are met. The side benefit of this is that with parallel startup of services, the desktop launches faster, but it also launches with all the services it needs. 2.) systemd-logind helps contain desktop processes in cgroups, meaning that if you want it to, it will terminate all user processes *for that session* when it logs out. This is a huge thing for the enterprise desktop environments. For example, I managed engineering desktops and there was a particularly finicky circuit designer that loved to leave background processes that would survive logouts, and if another user logged in it would interfere. But this process management also introduced resource management per-user session, so you could ensure a single user couldn’t abuse the system. This was also important to me, since we had multi-user systems running graphical sessions via VNC, and we wanted to make sure one user didn’t overwhelm the system. 3.) systemd now launches your GUI. You have your own private systemd --user running every time you log in. This process launches services and apps, maintains your environment, and can run other systemd units such as timers. This gives you a similar interface to system services, scoped just to your account. Since there’s only one user systemd per user, you can launch a process that can be used and managed by both the graphical login and a ssh session. (This is actually annoying to me, since it means stuff like Kerberos and AFS works differently than it used to) 4.) the desktop session output and error are captured in the journal. Previously init systems had user console lost to the user. There was some attempt to capture the X logs and the gnome session, but in systemd each user unit can be individually examined with journalctl. This is just stuff off the top of my head. While I do agree that there has been a lot of focus on server with systemd, a lot of cool things (like unit templating) were introduced because of systemd on workstations. Don’t forget that nearly all the common benefits of systemd also help desktops, because at its core, it’s the core init system to launch the OS. -- Jonathan Billings

12 21

F36, need help with screen blanks after 30 seconds of idle
by Lars E. Pettersson 25 May '22

25 May '22

Hi, I have noticed a very annoying thing after an upgrade to Fedora 36. My screen blanks after 30 seconds of idle. It is set to blank, and lock screen, after 10 minutes. I even tried to reset these settings, but still no luck. Never seen this before, and started after upgrade to F36. Anyone else seen this? Anyone who can give a pointer on what to check? Running Gnome, Xorg. Lars

5 7

I found the biggest improvement and the biggest disappointment in F36
by Sam Varshavchik 25 May '22

25 May '22

It is that a Qemu VM with a 1280x960 display is now exactly one pixel row shorter, vertically, after adding up all of the window title bars and the panel on the XFCE desktop. It fits exactly on my 1920x1080 monitor. I no longer have to do a "Resize to VM" every time I start it, to get rid of the annoying scrollbars. Big thumbs up from me, and the biggest step forwards in recent memory… The biggest frustration is openssl 3. Once again there are backwards- incompatible API changes, with little if none documentation, or direction. I wasted half of my weekend trying to figure out WTF needs to be done to make stuff work again. This time, it's not even a compilation issue. Things will compile. Just not work. Frustrating.

2 2

rpm erase or removal of rpms
by Bill Cunningham 24 May '22

24 May '22

I have been trying to use rpm or dnf to remove some rpms. Most the ones I am concerned with are docker related, and or to do with go (golang). You certainly can't use wildcards with rpm erase. I have a list generated with the date these rpms were installed, but I am not THAT good with CLI and bash operations like cut, xargs, sed and so on to alter the list; and I wouldn't be sure how to pipe the list contents or redirect to rpm the text's content from the ascii text file, to erase these particular rpms. Is there a way to mass erase many files (with rpm switches or such) using rpm? Here is an example of what I have been trying to do, ex: list.txt, gcc-devel // example, python-devel //example rpm -e // would this list content be redirectable to rpm -e ? cat list.txt lists rpms, rpm -e < cat list, or cat list | rpm -e do not work.

7 9

Re: rpm erase or removal of rpms
by Bill Cunningham 24 May '22

24 May '22

On 5/24/2022 6:26 PM, Bill Cunningham wrote: > > On 5/24/2022 6:23 PM, Bill Cunningham wrote: >> >> On 5/24/2022 5:28 PM, Barry wrote: >>> >>>> On 23 May 2022, at 23:03, Todd Zullinger <tmz(a)pobox.com> wrote: >>>> >>>> Hi, >>>> >>>> Bill Cunningham wrote: >>>>> I have been trying to use rpm or dnf to remove some rpms. >>>> I'd use dnf. It provides a much wider safety net. >>> I have always assumed that using rpm -e will mess up dnf. >>> so I never use rpm for any operation that modifies the system. >>> I think I shot off a foot a decade or so ago doing that. >> >> I usually will from time to time, erase the /var/cache/dnf >> directory, then run 'dnf makecache'. This does to my knowledge, erase >> many dnf config and status files. Running the makecache rebuilds the >> database. This is updated frequently when you run dnf. You can too >> run the dnf clear option too. >> >>

1 0

podman containers won't start after F36 upgrade
by Clemens Eisserer 24 May '22

24 May '22

HI there, I've just recently upgraded from F35->F36 and now podman containers don't start anymore. When starting a container which was created with F35 as user, I just get: Error: OCI runtime error: unable to start container "0a4d835ccc0777ccf77bc61976c32d9c3fbbf32c18902f0a2043a0 12d5fed598": runc: runc create failed: unable to start container process: can't get final child's PID from pipe: EOF It is a bit unfortunate I need the containers as they are, so I can't simply recreate them. I've tried to solve the problem by installing crun and making sure runc is installed, however nothing helped- Any idea what could be the problem? Thank you in advance, Clemens

3 4

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