Running under F27, Ffx 57 puts some accursed Url in its address
box on every new tab. Blasted thin is a royal pain to have to delete
before I can just enter the one I want. How do I turn this excrement off??
Beartooth Staffwright, Not Quite Clueless Power User
Remember I know little (precious little!) of where up is.
in order to backing up of the data , I wrote a script that uses the rsync
This script have to be launched manually, and the data are saved on a USB
Hard Disk, which (obviously) must be mounted.
The mounting of the partitions for the back up on the USB HD is made
permantly at boot of the computer (the name of the backup-partitions is
wrote in the file / etc / fstab) :
UUID=376214F24CC07CE0 /media/BKx_data-personal ntfs defaults 0 0
UUID=479F99A324FF4D1D /media/BKx_programming ntfs defaults 0 0
UUID=EA8266EA8266BB29 /media/BKx_data-common ntfs defaults 0 0
This script works fine.
However, this solution for backing up the data is problematic, because *I
always receive messages with the request of access to the partitions ** of
the “backup-partitions”** by "nautilus"* - every time that I use the "find"
I can consider that this problem is connected with the *permanent *
*mounting* of the partitions on the HD-USB (on the file /etc/fstab).
To avoid these problems I actually removed the permanent mounting of the
partitions by registering them on the file fstab and now I'm looking for an
alternative solution for the back up the data.
I think this solution can go in the following directions:
mounting the partitions (commanded by the script) before executing the
rsync command and unmounting them immediately afterwards.
alternatively, giving appropriate orders to the “udev feature” about the
backup partitions (I think this is possible to do, but I do not know how to
I would like to have some suggestions and advice about it.
I managed by various means to get my Fedora 26 to run KDE, but it
appears that all is not well...
i) during login, I get
[drm] VGACON disable radeon kernel modesetting (2 times) &
[drm] cannot get speed from usb address (approx)
ii) the system then comes up with the drawing of a river bank & asks for
iii) system then comes up with a KDE Plasma screen, which it then
changes to a different size & then
iv) comes up with a more-or-less KDE start page.
I've had an amount of Trouble to get KDE running (the only live DVD I
have is running Gnome which I prefer not to use) & I'm no longer sure of
what real system I'm running.
I've tried taking the "nomodeset" out of /etc/grub, but that doesn't
appear to do the trick & I haven't been able to find anything else...
Updates are done OK, but it appears that a number of applications are
not listed in the launcher.
Can anyone help me????
Linux Big_Blue_26 4.14.11-200.fc26.x86_64 #1 SMP Wed Jan 3 13:58:53 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
First: this is an upgrade of a USB system and I have an image of f26 before the
upgrade to f27 and I will redo it in full. So no disaster, yet I want to understand
how the upgrade process recovers from such a failure (if at all).
I followed the usual process
# dnf update (and such)
# dnf system-upgrade download --releasever=27
# dnf system-upgrade reboot
but due to an oversight I turned off the power to the laptop (where the USB was
installed) so overnight it shut down.
This morning I tried to restart it. A reboot brought up a f26 kernel (though the
desktop background looked like f27). dnf thinks this is still a f26 system.
# dnf system-upgrade reboot
which started an upgrade, though with less packages listed. However, when the main
Upgrade/Install phase ended the post scripts were ran only for the recently listed
On a reboot I still was on f26, sort of, but some packages claimed to be installed
twice (e.g. dnf lists both f26 and f27).
# dnf system-upgrade download --releasever=27
failed saying some critical packages (e.g. 'dnf') will be removed.
What is the correct way to complete the upgrade? (I kept an image of the failure).
Eyal Lebedinsky (fedora(a)eyal.emu.id.au)
only a simple (and maybe stupid) question ...
To use autofs for the automatic mounting of partitions existing on USB HD
(that is permanently connected to the computer), it is also mandatory to
install NFS ?
If I run "iconv --list" it sticks "//" on the end of every
encoding name, but I don't need the "//" when specifying
a to or from encoding name.
Does anyone have the slightest clue why the slashes
are there in the listing output?
Funny, the things one learns after making the first clean install in ten
or more iterations of Fedora.
For instance, that Adobe long ago abandoned the Adobe ("Acrobat") Reader
for Linux, and the nspluginwrapper project.
So that now, if you still want to use Adobe for Linux, you have to save
an old rpm and install it directly. And do it every time you reinstall
Fedora--or at least reinstall it cleanly.
I need advice on whether I can abandon Adobe Reader completely, and what
to use instead.
I use it all the time for certain PDF's that come with form fields that
you fill out. Not all PDF viewers--and not the PDF viewer native to
Firefox--support form filling. Without form filling, I have to fill in
forms by hand--and my fist is a bit of a strain on anyone's eyes,
especially those of a bureaucrat or his confidential secretary. So I
need form filling.
That aside, I'd love to have something that opens seemlessly in any
For the record, I use KDE. But I'll still use any GNOME products that
still open in KDE.
Just had another boot that utterly failed because services that were
supposed to start only after the network interfaces came up, didn't. They
started too soon. Privoxy's logfile has the smoking gun:
2017-12-16 09:42:39.875 7f4acdaa6740 Fatal error: can't bind to 192.168.0.1:8000: Cannot assign requested address
This is despite that NetworkManager-wait-online was enabled and active. This
is what everyone kept telling me was the only thing that needed to be done.
Well, it was enabled:
[root@shorty system]# systemctl status NetworkManager-wait-online
● NetworkManager-wait-online.service - Network Manager Wait Online
Loaded: loaded (/usr/lib/systemd/system/NetworkManager-wait-
Active: active (exited) since Sat 2017-12-16 09:42:39 EST; 12min ago
Process: 977 ExecStart=/usr/bin/nm-online -s -q --timeout=30 (code=exited,
Main PID: 977 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
Dec 16 09:42:32 shorty.email-scan.com systemd: Starting Network Manager Wait
Dec 16 09:42:39 shorty.email-scan.com systemd: Started Network Manager Wait O
It came up at 09:42:39. And, at 09:42:39 privoxy also came up. And privoxy
still blew chunks because the primary network interface wasn't up yet.
Why is it so friggin difficult to get something this simple, this basic
concept of starting things only after the network interfaces are up, working
correctly, and reliably?
Oh yeah, I know. systemd.
Can someone tell me what this is about? A message in the journal
shortly after a boot reads:
Failed to start Create Volatile Files and Directories
which leads me to the following systemd status query.
$ systemctl status systemd-tmpfiles-setup.service
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2018-01-02 21:34:31 PST; 30min ago
Main PID: 860 (code=exited, status=1/FAILURE)
Jan 02 21:34:31 amito.localdomain systemd: Starting Create Volatile Files and Directories...
Jan 02 21:34:31 amito.localdomain systemd-tmpfiles: [/usr/lib/tmpfiles.d/gluster.conf:2] Unknown user 'gluster'.
Jan 02 21:34:31 amito.localdomain systemd: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE
Jan 02 21:34:31 amito.localdomain systemd: Failed to start Create Volatile Files and Directories.
Jan 02 21:34:31 amito.localdomain systemd: systemd-tmpfiles-setup.service: Unit entered failed state.
Jan 02 21:34:31 amito.localdomain systemd: systemd-tmpfiles-setup.service: Failed with result 'exit-code'.