systemctl, start a --user service from a root script
by Mike Wright
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
1 year, 11 months
Re: Can new Fedora changes help users ?
by R. G. Newbury
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.
1 year, 11 months
Not Able To Use External Monitor with Laptop
by Richard Kimberly Heck
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
1 year, 11 months
to wayland or not?
by Jack Craig
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, ...
1 year, 11 months
Pipewire update reset audio devices AGAIN
by Richard Shaw
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
1 year, 11 months
Re: Fedora trashes my NTFS drive
by Roger Heflin
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.
1 year, 11 months
bluetooth pairing problem
by ToddAndMargo
Hi All
Fedora 35
Xfce
Xfce's bluetooth manager find my Jabra 85h but
when I try to pair with it, I get "Disconnected"
https://imgur.com/VsnXOSK.png
# rpm -qa | grep -i blue | grep -v fish | grep -v bird
bluez-tools-0.2.0-0.17.git20170912.7cb788c.fc35.x86_64
gnome-bluetooth-libs-3.34.5-2.fc35.x86_64
gnome-bluetooth-3.34.5-2.fc35.x86_64
bluez-5.64-1.fc35.x86_64
bluez-libs-5.64-1.fc35.x86_64
bluez-cups-5.64-1.fc35.x86_64
bluez-obexd-5.64-1.fc35.x86_64
# dnf install pulseaudio-module-bluetooth
Error:
Problem: problem with installed package
pipewire-pulseaudio-0.3.50-1.fc35.x86_64
- package pipewire-pulseaudio-0.3.50-1.fc35.x86_64 conflicts with
pulseaudio provided by pulseaudio-15.0-2.fc35.x86_64
When I try to pair, journal give me:
bluetoothd[1182]: src/device.c:load_gatt_db() Unable to load key file
from /var/lib/bluetooth/00:19:0E:19:3F:C4/cache/7F:A5:9F:E8:AA:26: (No
such file)
And there really is no file of that name:
# ls -al /var/lib/bluetooth/00\:19\:0E\:19\:3F\:C4/cache/
total 16
drwx------. 2 root root 4096 Apr 22 19:15 .
drwx------. 4 root root 4096 Apr 22 19:15 ..
-rw-------. 1 root root 1078 Apr 22 19:15 30:50:75:48:88:97
-rw-------. 1 root root 29 Mar 21 20:31 CC:82:EB:4C:D5:D5
What is interesting is that 30:50:75:48:88:97 says it is
my Jabra 85H
[General]
Name=Jabra Elite 85h
If I erase the cache and start over, the same thing
happens. A new file is created but the error log
says it can't find a different file.
Yours in frustration,
-T
1 year, 11 months
Cinnamon: tranferring ALT to virt-manager
by Alex
Hi,
I have a kvm instance running win10 and need to use the ALT-click key
within the instance. However, it seems Cinnamon is intercepting that
keypress when accessing the instance using virt-manager.
It works fine with virt-manager and GNOME, just not with virt-manager
and Cinnamon.
virt-manager isn't my favorite, but I've also tried tigervnc some time
ago and it also has the same problem.
Is there a virt-manager config options I need to select in order to
pass the ALT + left mouse key through to the instance?
It's currently just set up as a PS2 mouse.
Here is my qemu xml config
https://pastebin.com/Pnizy4Q7
1 year, 11 months
Re: Fedora trashes my NTFS drive
by Matt Morgan
On Sat, Apr 23, 2022 at 11:16 AM Lily White <lilywhite2005(a)outlook.com>
wrote:
> Hi,
>
> I have a NTFS flashdrive. When I plug it into Fedora, it reads and
> writes normally. However, when plugged into M$ Windows, only an icon and
> a not-so-informative ``Removable media'' is shown.
>
> When I try to reformat it with Windows Disk Management, another
> not-so-informative error ``Windows cannot format the given drive'' is
> shown.
>
> I then filled it with zeroes with a Chinese partition management program
> (AoMei, if that is useful) and recreated NTFS on it. It worked on
> Windows. However, after a plug into Fedora it was ruined again: Fedora
> recognized it, but Windows did not.
>
> Results of `sudo fsck /dev/sdc1':
>
> -------------------------------------
> fsck from util-linux 2.37.4
> Unsupported: replay_log()
> Unsupported: check_volume()
> Checking 256 MFT records.
> Unsupported cases found.
> ntfsck was unable to run properly.
> -------------------------------------
>
> So I ran `ntfsfix` on it and the following output was produced:
>
> --------------------------------------------------------
> Mounting volume... OK
> Processing of $MFT and $MFTMirr completed successfully.
> Checking the alternate boot sector... OK
> NTFS volume version is 3.1.
> NTFS partition /dev/sdc1 was processed successfully.
> --------------------------------------------------------
>
> A rerun of fsck produced identical output.
>
> *Note that the drive was usable on Fedora throughout the process.*
>
> Any idea what's behind this?
> ------
> From LilyWhite with love
>
I haven't done this for a while, but I used to have a similar problem with
Win7 and FAT drives; however, Win7 would always offer to repair the drive
and it would be fine again. It happened only on one series of promotional
flash drives I had bought in bulk, i.e. they were all the same type and
probably from the same production run. So I don't have real suggestions,
but a question: does this happen on all NTFS flashdrives, or just this one?
Maybe it's the drive itself.
1 year, 11 months
ssh infested by systemd.resolved
by Sam Varshavchik
The latest systemd update broke ssh. Specifically, "ssh hostname", where
hostname was not a FQDN no longer worked, and I had to use "ssh
hostname.domain", for my LAN.
Of course, /etc/resolv.conf was pointing to systemd's resolver, and features:
search .
this was despite my DHCP server offering the LAN's domain name properly.
I don't remember if I fixed this laptop previously, or it was using
systemd's resolver for a while. I just symlinked /etc/resolv.conf to
/run/NetworkManager/no-stub-resolv.conf, which had the correct DNS search
string, as always.
This seemed to have fixed DNS lookups, per se:
$ host jack
jack.email-scan.com has address 192.168.0.6
But ssh was still broken, and failing.
An strace of ssh revealed that it still insists on talking to systemd.
connect(3, {sa_family=AF_UNIX,
sun_path="/run/systemd/resolve/io.systemd.Resolve"}, 42) = 0
sendto(3, "{\"method\":\"io.systemd.Resolve.ResolveHostname\",\"parameters\":
{\"name\":\"jack\",\"flags\":0}}\0", 87, MSG_DONTWAIT|MSG_NOSIGNAL, NULL, 0)
= 87
mmap(NULL, 135168, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f103ff5c000
I don't see where it's picking this up. The only thing I can think of is
nsswitch.conf, but the "hosts" entry there is identical to what's on
another, un-upgraded system.
I don't see where it's picking this up. The only thing I can think of is
nsswitch.conf, but the "hosts" entry there is identical to what's on
another, un-upgraded system.
Does anyone know how to fumigate systemd out of ssh?
1 year, 11 months
