Keyboard dead with anydesk logon
by ToddAndMargo
Hi All,
Fedora 39
anydesk-6.3.2-1.el7.x86_64
lightdm-1.32.0-7.fc39.x86_64
Any idea why the keyboard and the onscreen keyboard
wont let me type my password into lightdm's password
prompt.
https://imgur.com/3AUrKOS.png
Anydesk told me to reboot. Did not work.
-T
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 month, 1 week
Just to note: RPMfusion just put out an updated nvidia package that now works with newer kernels.
by Michael D. Setzer II
Had to have machine with older card keep running the 6.7.11
kernel in order to have a working nvidia driver for BOINC.
The newer ones now work with the 6.8 kernels.
Just to let others know.
+------------------------------------------------------------+
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/
+------------------------------------------------------------+
1 month, 1 week
Fedora 40 virtual machine
by Paolo Galtieri
I tried to create a Fedora 40 virtual machine under VMware version
17.0.2. The ISO image boots up fine, but when I double click on the
"Install to drive" It will often fail withe the following error:
Anaconda is unable to create /var/run/anaconda.pid because the file
already exists. Anaconda is already running, or a previous instance of
anaconda has crashed.
I may have to try several times before I can install it to the drive.
When it finishes installation and I click on "Finish Installation"
nothing happens. I expect it to say reboot system, but it does
nothing. I reboot manually and when it comes back up it initially says
"Initial setup" but then the screen flashes and the login prompt appears.
Paolo
1 month, 1 week
new boot error message
by Jon LaBadie
I'm on a Fedora 38 workstation.
On reboots, say after a dnf update, I've started
getting an error message I'd not seen before.
I don't recall the exact syntax but it basically
says "/efi/Fedora" doesn't exist.
System still boots normally.
I have an "efi" partition, 1st partition on the
system disk. After boot it is mounted under /boot.
The efi partition contains a subdirectory "EFI"
and EFI contains a subdirectory "fedora". So after
boot I can see "/boot/efi/EFI/fedora".
Any explanation for the error message?
tnx
--
Jon H. LaBadie jonfu(a)jgcomp.com
1 month, 1 week
Stuck at grub prompt after reordering partitions
by Klaus-Peter Schrage
After many years of maintaing dual boot setups (Fedora/Windows) my
harddisk layout got a bit confusing: Linux and Windows partition were
scattered on mainly two harddisks (all gpt). I was able to free a third
harddisk (ssd) and copied the linux partitions boot, root and home over
to the new disk, where they now reside as /dev/sda1, /dev/sda2
and /dev/sda3.
I left the efi-partition on the disk /dev/sdc together with Windows 11.
As in /etc/fstab all partitions are identified by their UUID, I didn't
feel a need to adjust that file.
Trying to boot brought me to the grub command line prompt. After some
trial and error, the appropriate sequence of grub commands (set
root=..., linux ..., initrd ...) made the system boot into a fully
working Fedora 39 installation.
From there I tried to repair GRUB2, following the guidelines at
https://fedoraproject.org/wiki/GRUB_2?rd=Grub2#Updating_GRUB_2_configurat...
namely those three steps:
# rm /boot/efi/EFI/fedora/grub.cfg
# rm /boot/grub2/grub.cfg
# dnf reinstall shim-* grub2-efi-* grub2-common
But rebooting still gets me to the dreaded grub>.
So what am I missing?
BTW, I did NOT use the grub2-install command which shoud not be used on
UEFI systems.
1 month, 1 week
pulseaudio misbehaviour on remote
by Neal Becker
I'm running a connection to a remote server via x2go. The remote desktop
is xfce.
When I leave this unattended for some time, I come back to find that
pulseaudio is sucking 64GB of VM. Needless to say, I don't really need PA
running on it, but I haven't seen how to disable it. Also this seems like
a bug, PA has no business using 64GB of VM.
I've just been killing it when I notice, but I'd rather fix the problem.
Any thoughts?
1 month, 1 week
What's up with debuginfod?
by Sam Varshavchik
Can anyone vouch for having a reliable, established, experience with
debuginfod?
My 'make check' runs valgrind a bunch of times. Right now, each invocation
is sitting and doing nothing for about ten minutes, before it apparently
times out downloading something from debuginfod.fedoraproject.org:
poll([{fd=9, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAND}], 1, 0) = 0 (Timeout)
poll([{fd=9, events=POLLIN}], 1, 1000) = 0 (Timeout)
poll([{fd=9, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAND}], 1, 0) = 0 (Timeout)
poll([{fd=9, events=POLLIN}], 1, 1000) = 0 (Timeout)
poll([{fd=9, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAN
Whether using valgrind or gdb, I find that debuginfod gets stuck more often
than not, and this is getting old. I don't know what it's beef is. I can
reach debuginfod.fedoraproject.org on port 443 without any issues.
After perusing the man page I set DEBUGINFOD_MAXTIME=10, and things are
slowly, slowly moving forward. But I'm wondering if anyone found debuginfod
to be reliable.
1 month, 2 weeks
a tool like xte(1) but for Wayland?
by Don Marti
I have some old shell functions that use xte to fake some keyboard
input. For example, this is a function to run its argument(s) in a new
gnome-terminal tab.
run_in_tab ()
{
xte 'keydown Control_L' 'keydown Shift_L' 'key t' 'keyup Control_L'
'keyup Shift_L' 'sleep 1' "str exec $*" 'key Return'
}
Is there a tool packaged in new Fedora versions that's like xte, but for
Wayland?
1 month, 2 weeks
Which keys did I hit?
by Sam Varshavchik
My fingers had a mind of their own and apparently hit some combination of
keys that had a very weird result.
I'm using an XFCE desktop. And, apparently, it became, maybe, fourty or so
virtual pixels wider. Of course, the monitor still has the same number of
pixels, so what was happening is that moving the mouse pointer to one of the
edges scrolled the entire desktop slightly to reveal the extra virtual space
on that side. Moving the mouse pointer to the other edge scrolled the
virtual window on the desktop in the other direction, to the other side of
the now-larger virtual desktop.
It was a pretty cool effect, so after I had my fun I logged out and back in,
and things were back to normal. But I'm wondering what keys did I hit, I
looked through settings and didn't find anything relevant…
1 month, 2 weeks
