users April 2022

users@lists.fedoraproject.org

84 participants
81 discussions

Changing date with procmail
by Michael A. Peters 08 Jun '22

08 Jun '22

Anyone know of a procmail recipe to change the date on incoming messages? If the date is in the future by more than 24 hours - I'd like to just change it to the current date. If the date is in the past by more than two weeks - I'd like to just change it to the current date. I'd like to do it in procmail - if someone knows how. I've done some searching, still have some to do. Found some stuff on extracting the date, but not on modifying it if necessary.

5 5

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

Connecting to printer on Windows 10 System
by Robert McBroom 23 May '22

23 May '22

I have a HP Envy 5530 printer on usb connection to a Windows 10 system. KDE printer settings seems to find it with a smb URI. smb:///%2F192.168.1.100%2FHPENVY5530 Keeps asking for a user and password but doesn't accept local users or users on the remote machine. An attempt to print a test page fails with a CIFS unable to connect error NT_STATUS_NOT_FOUND. The setting window is not responsive to any mouse clicks. Other windows systems print with no problems What am I missing on getting access?

5 11

Can new Fedora changes help users ?
by Cătălin George Feștilă 03 May '22

03 May '22

I read this article https://www.theregister.com/2022/04/27/fedora_starts_to_simplify_linux/. The question is whether we can still use old laptops. I have an HP 6710b and it works very well at the moment with Fedora 36. In this case, my opinion is that the development team will release a special Fedora Spin for laptops with old hardware. What do you think?

8 12

Re: Fedora trashes my NTFS drive
by Roger Heflin 29 Apr '22

29 Apr '22

Well, merged into kernel some weeks before likely means that it will be a few weeks before the kernel.org with it is released, and it will take weeks to month or more after that before fedora updates has that kernel. And merged into the kernel also means that there are almost certainly still going to be some sorts of bugs for a while. And the management of access times and such means that you would have likely written to the metadata (if you read any files) if the implementation handles updating access times. And there are now articles saying that code that was merged into the kernel has a bunch of patches waiting to be accepted, and the maintainer has not responded to any of those requests and that new NTFS code is suspected to have immediately been orphaned by the company that asked for it to be merged and agreed to help support it. The articles indicate the linux kernel is working though what is going on with the maintainer. On Tue, Apr 26, 2022 at 10:28 AM Lily White <lilywhite2005(a)outlook.com> wrote: > I didn't mount as readonly, but I didn't write to it also. I'm > speculating that the implementation on Fedora and macOS are broken in > the same way so that they can actually read each other's broken output. > > I thought that NTFS supported just got merged into the kernel some weeks > before? Anyone know about the progress? > > > On 4/26/22 05:16, Patrick O'Callaghan wrote: > > On Mon, 2022-04-25 at 10:41 -0500, Roger Heflin wrote: > >> On Mon, Apr 25, 2022 at 10:11 AM Lily White > >> <lilywhite2005(a)outlook.com> > >> wrote: > >> > >>> I got a spare drive and it does work (at least for now, this drive > >>> worked for a while before everything broke). So I sent my old drive > >>> back > >>> to Sandisk and I'll see if it was with that specific model. > >>> > >>> I'll also wait for some time and see if wear and tear may cause > >>> problems. > >>> > >>> What's interesting is that the broken drive works on both Fedora > >>> and > >>> macOS, but not Windows. That's why I didn't speculate the drive > >>> itself > >>> was broken before. > >>> > >>> > >> I am going to bet that the NTFS code is very similar on Fedora and > >> MacOS. > >> So likely it is a code bug or a usage bug (see comments below). > >> > >> you did make sure to umount it on Linux/BSD before removing it right? > >> > >> And if you hibernate the machine(any os) and remove the usb device > >> while > >> hibernated the filesystem may not be consistent, it has to be > >> explicitly > >> unmounted on both windows and fedora before removal so that all data > >> is > >> fully written. > >> > >> In the past it was suggested to not use NTFS as a transfer drive and > >> to use > >> something simpler like FAT32 as that fs's format is better documented > >> and > >> simpler than NTFS. That may or may not still be the case. > > > > Most NTFS installation on Linux use a user-space implementation via > > Fuse, which is known to have some limitations (IIRC it's fine for > > reading but might be problematic when writing). A new kernel-based > > implementation is apparently on the way and is said to have a higher > > degree of compatibility. > > > > poc > > _______________________________________________ > > 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 > > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > > -- > From LilyWhite with love > _______________________________________________ > 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 > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure >

1 0

systemctl, start a --user service from a root script
by Mike Wright 29 Apr '22

29 Apr '22

Hey all, I'm trying to execute a user systemd function from /etc/rc.local: 755, root.root. My thought is to use su. Is there a better way? This is where I'm at now. su --login mike --command=systemctl --user start <some service> Anybody know how to accomplish this? I personally know about 100 ways to do it wrong ;D TIA Mike Wright

2 1

Re: Can new Fedora changes help users ?
by R. G. Newbury 29 Apr '22

29 Apr '22

On 2022-04-28 00:04, users-request(a)lists.fedoraproject.org wrote: > I think the answer's going to depend on the age. > > I have a 2007 era laptop that still works, though its battery doesn't, > and is painfully burdened by modern Gnome. But managed Gnome from way > back then quite acceptably. It has a no-longer supported NVidia > graphics chipset (NVidia removed drivers for that model some time ago). Very old nvidia drivers may not be available through rmpfusion but drivers back to the 304 series for Geforce 6 chips are still available on nvidia.com. You just download and install the rpm. I have an IBM T60 which was first introduced in 2006. Like your laptop, the battery is very short-lived, but the computer works fine. Presently running Fedora 35 with, iirc without looking, the 340 series nvidia driver (Geforce 9600 gpu, I think). Removing the legacy BIOS boot is a step backwards and will hurt a large number of Fedora users who are, in the end count, a large testing group for a cutting edge distro. G.

3 2

Not Able To Use External Monitor with Laptop
by Richard Kimberly Heck 28 Apr '22

28 Apr '22

Hi, all, I'm having an odd problem. On two of my laptops, on which I've just done fresh installs, I cannot get the external monitor to work. Using either the XFCE display configuration tool, it shows up, but it's marked as 'disabled'. I do not seem to have the usual such tool under KDE, which is one of my puzzles. The install was done the same way in both cases, and somewhat non-standardly, so I'm guessing I might be missing some package(s). I've had trouble using KDE with Wayland, so I installed the XFCE spin, then installed KDE via dnf, so Wayland does not get loaded, and is not even installed. Graphics processor on this machine is AMD Renoir. It's a System 76 Pangolin. Riki

3 2

to wayland or not?
by Jack Craig 26 Apr '22

26 Apr '22

hi list, i was convinced that i was running wayland on my F34. i see ... in my env,.. *WAYLAND_DISPLAY=wayland-0* which_declare=declare -f XAUTHORITY=/run/user/1000/.mutter-Xwaylandauth.P2V0K1 XDG_CURRENT_DESKTOP=GNOME XDG_DATA_DIRS=/home/jackc/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share/:/usr/share/ XDG_MENU_PREFIX=gnome- XDG_RUNTIME_DIR=/run/user/1000 XDG_SESSION_CLASS=user XDG_SESSION_DESKTOP=gnome XDG_SESSION_TYPE=wayland but inxi -G sez,... *inxi -G* Graphics: Device-1: Intel HD Graphics 530 driver: i915 v: kernel Device-2: NVIDIA GK208B [GeForce GT 730] driver: nouveau v: kernel * Display: server: X.Org v: 1.21.1.4 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: nouveau resolution: 3840x2160~30Hz* OpenGL: renderer: NV106 v: 4.3 Mesa 21.1.8 so, which is it? wayland or no wayland?? thx, ...

3 4

Pipewire update reset audio devices AGAIN
by Richard Shaw 26 Apr '22

26 Apr '22

So after updating my system and rebooting, I found all of my audio settings lost AGAIN. I know it's "new" and all, but when are things going to settle down? $ dnf history info 287 | grep pipe Upgrade pipewire-0.3.50-1.fc35.i686 @updates Upgraded pipewire-0.3.49-1.fc35.i686 @@System Upgrade pipewire-0.3.50-1.fc35.x86_64 @updates Upgraded pipewire-0.3.49-1.fc35.x86_64 @@System Upgrade pipewire-alsa-0.3.50-1.fc35.i686 @updates Upgraded pipewire-alsa-0.3.49-1.fc35.i686 @@System Upgrade pipewire-alsa-0.3.50-1.fc35.x86_64 @updates Upgraded pipewire-alsa-0.3.49-1.fc35.x86_64 @@System Upgrade pipewire-gstreamer-0.3.50-1.fc35.x86_64 @updates Upgraded pipewire-gstreamer-0.3.49-1.fc35.x86_64 @@System Upgrade pipewire-jack-audio-connection-kit-0.3.50-1.fc35.x86_64 @updates Upgraded pipewire-jack-audio-connection-kit-0.3.49-1.fc35.x86_64 @@System Upgrade pipewire-libs-0.3.50-1.fc35.i686 @updates Upgraded pipewire-libs-0.3.49-1.fc35.i686 @@System Upgrade pipewire-libs-0.3.50-1.fc35.x86_64 @updates Upgraded pipewire-libs-0.3.49-1.fc35.x86_64 @@System Upgrade pipewire-pulseaudio-0.3.50-1.fc35.x86_64 @updates Upgraded pipewire-pulseaudio-0.3.49-1.fc35.x86_64 @@System Upgrade pipewire-utils-0.3.50-1.fc35.x86_64 @updates Upgraded pipewire-utils-0.3.49-1.fc35.x86_64 @@System

4 9

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