users May 2022

users@lists.stg.fedoraproject.org

91 participants
77 discussions

Fedora 36 update vs broadcom-wl
by D. Hugh Redelmeier 01 Jun '22

01 Jun '22

I have an 11-year-old netbook. The WiFi hardware needs the broadcom-wl driver from RPM Fusion. The Fedora upgrade from 35 to 36 worked fine, including keeping/updating broadcom-wl. But WiFi didn't work. The desktop didn't even see the device. I needed to issue the command sudo depmod I've had to do this in previous upgrades too. This is pretty easy to do but not at all obvious (I leave notes to myself so that I don't have to rediscover the solution). My guess is that this is a simple oversight in packaging. If so, it is an RPMFusion problem, not a Fedora problem.

3 2

subtitles conversion question
by François Patte 31 May '22

31 May '22

Bonjour, I have some films in mkv format with many subtitles tracks : hdmv_pgs_subtitles I can extract these tracks and I want to convert them in srt text format. I use a java script (found on the web) BDSup2Sub512.jar which can convert the hdmv_pgs files in two files: one has extension .idx the other one the .sub extension. I found this web site: https://subconverter.com/convert-sub-idx-to-srt-online Which I can use to convert these two files in a .srt file. So far, so good! Is there a tool on linux which could do the same job? Thank you. -- François Patte UFR de mathématiques et informatique Laboratoire CNRS MAP5, UMR 8145 Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)6 7892 5822

2 1

upgrade to F36 forgot WiFi passwords
by D. Hugh Redelmeier 31 May '22

31 May '22

I have several WiFi networks and several notebooks. Whenever I updated a notebook to Fedora 36, some WiFi passwords needed to be re-entered. I don't remember the exact details. I think that if I were updating over WiFi, that password was retained. I don't have any remaining updates that I wish to do so I'm not willing to put the effort into creating a good bug report.

1 0

Disable rpcbind on NFS server
by Ian Pilcher 31 May '22

31 May '22

I don't need rpcbind, as I only use NFSv4. Is there any way to set up or configure the NFS server-related units (nfs-server.service, etc.) to not start rpcbind? -- ======================================================================== Google Where SkyNet meets Idiocracy ========================================================================

2 2

python support for kdevelop removed?
by Adrian Sevcenco 30 May '22

30 May '22

Hi! I no longer find the python support for kdevelop... was it removed? Thanks a lot! Adrian

2 1

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