I am having a problem with rsyncing:
rsync -ah --stats --delete /home/ /media/HD103SI/backups/homebase/home
usage.xls") failed: Input/output error (5)
rsync: recv_generator: failed to stat
usage.xls": Input/output error (5)
IO error encountered -- skipping file deletion
So I go to the directory and I try to ls P* and it hangs.
I tried to remove the bad file:
rm Power\ usage.xls
rm: cannot remove `Power usage.xls': Input/output error
How can I get this bad file out of the way so I can back up properly?
Sharing the following for the benefit of others. Entering a passphrase for
your gpg key with a passphrase is broken again, if you're on a simple ssh
connection, from the looks of it.
It originally broke a year or so ago – maybe longer, I don't recall exactly
-- when the simple prompt for your passphrase was replaced by a separate
pinentry tool that wanted to open a pretty X window for that. Nobody uses
ssh anymore, apparently, and checking DISPLAY and falling back to a terminal
prompt wasn't very obvious, so everyone had to figure out how to do
echo pinentry-program /usr/bin/pinentry-curses >~/.gnupg/gpg-agent.conf
Well, even that no longer works:
$ git tag -s -a libcxx/0.21.0/`date +%Y%m%d%H%M%S` -m 'Tag version 0.21.0'
error: gpg failed to sign the data
error: unable to sign the tag
… aaaand, we're done.
stracing what was going on wasn't very enlightening:
[pid 2581154] read(4, "INQUIRE PINENTRY_LAUNCHED 2581156 curses 1.1.0 -
gnome localhost:10.0\n", 1002) = 70
[pid 2581154] write(2, "[GNUPG:] PINENTRY_LAUNCHED 2581156 curses 1.1.0 -
gnome localhost:10.0", 70 <unfinished …>
[ buncha noise, and finally ]
[pid 2581154] read(4, "ERR 83918950 Inappropriate ioctl for device
<Pinentry>\n", 1002) = 55
And that's it. After reading random man pages, here and there, and simply
trying things at random, I discovered that setting GPG_TTY environment
variable makes pinentry-curses work again:
GPG_TTY=`tty` git tag -s [options]
And, pinentry-curses works again. There you go.
Why can't this be an obvious default fallback, so everything works
flawlessly, by default, for everyone? Would love to hear a logical
I was commenting yesterday afternoon on how painless the upgrade had been so far for me (4 laptops, 1 workstation). Got jinxed on a workstation at work! For me, F31 got upgraded to F32 using the methods oulined in https://fedoramagazine.org/upgrading-fedora-31-to-fedora-32/. All steps went smoothly, until it was time to come up: I was thrown into emergency mode after the upgrade.
As instructed by the emergency mode, here is the output of journalctl and rdsosreport.txt
Note that I have changed the hostname to hostname.suppressed (I don't know what else has the machine's identity even though it behind VPN).
Output of journalctl:
$ fpaste journal.txt
$ fpaste rdsosreport.txt
Any suggestions as to what is wrong? The machine is sort of hard to get to simply because it is not online now, and I have to go in to get more information but I will try and provide additional requests for information in as timely a manner as possible.
Many thanks again and best wishes,
The first thing that I noticed after updating my router to F32 is that
masquerading didn't seem to work. telnet to some public port 80 appears to
be blocked, traceroute dies, etc…
When I ran firewall-config, the masquerading checkbox was off, so I enabled
it, but it made no difference.
Poking around suggested that something more fundamental is broken, somewhere.
firewall-config itself seems to be showing my two interfaces:
This is correct, my ports, both in the zone. But firewall-cmd on the command
line comes back with this:
[root@shorty ~]# firewall-cmd --list-interfaces
[root@shorty ~]# firewall-cmd --get-active-zone
Something seems to be broken in firewalld-land, but I don't know where to
After upgrading to Fedora 32 my monitors no longer turn off after timeout
or locking the display.
Interestingly, they do for a few seconds after I lock the screen but then
turn back on. The display is blank/black but the backlighting is
AMD RX580 and a LG & Acer 1080p IPS monitors.
I had a printer problem an hour ago and in the course of straightening
things out I found that I could not print a CUPS test page. Is that a
new situation for Fedora 32? I also tried the Print Settings in the
Administration section. As I remember there was a Maintenance menu in
CUPS that had two test options, I see no Maintenance in CUPS now. I may
have something wrong in my setup but can't imagine what? I set up both
printers with the Brother Linux printer tool as I have been doing for a
few years and until tonight I had no need to use CUPS, there has been no
problem printing and it did print a test page with one I found by
googling for it.
What's wrong, is it just me? I've seen no other complaints bout this. Bob
Bob Goodwin - Zuni, Virginia, USA
FEDORA-32/64bit LINUX XFCE Fastmail POP3
Until recently, Firefox had a feature I really liked and used a lot: if
you clicked anywhere in a scroll bar other than on the slider, it would
jump instantly to the top or bottom of the page. This seems to have
gone, and clicking just scrolls the way it does in most browsers. Does
anyone know if there's a setting to control this?
I recently (last night) upgraded the oldest of my machines.
Because I was doing this from memory, I decided to do trial-and-error (not a good idea, I know, but it was late and I was lazy).
So, I did:
sudo dnf upgrade --releasever 31
and everything went through fine, including installation on the commandline. There was no interruption because it came up immediately in F31 (was previously F30). This morning, I went back and looked at the notes at https://fedoramagazine.org/upgrading-fedora-31-to-fedora-32/ and realized that I should have used
sudo dnf system-upgrade download --releasever=32
sudo dnf system-upgrade reboot
so that is what I did to move the system to F32. This took a long time in coming up, during which the machine was unusable.
So, my question: which of the two approaches is "better"? The latter is swankier while coming up, but is the one with the Windows-type message (Upgrading system -- please do not turn off your computer, or something similar) but if there is no difference, I prefer the first.
Many thanks and best wishes,
I have a working firstwalld with wireguard config working on f30
but after the update to f31 some of my config is not being applied.
I have the following:
$ more /etc/firewalld/direct.xml
<?xml version="1.0" encoding="utf-8"?>
<rule ipv="ipv4" table="filter" chain="FORWARD" priority="0">-i wg0 -o internal -j ACCEPT</rule>
<rule ipv="ipv4" table="filter" chain="FORWARD" priority="0">-i wg0 -o internal -m state --state RELATED,ESTABLISHED -
This is important as it allows routing from interface wg0 to interface internal.
What is the F31 version of the above?
I tried punting the issue by switching firewalld back to iptables but that did not seen to fix it.