Fully updated F27, Dell XPS 15 9550.
So last year on F26 I could safely and reliably suspend to ram from the
menu, then after the upgrade to F27 all that stopped. I just dealt with it
until last night.
So Google let em down again with the VAST majority.. if not damned near all
of the results centered around Hibernation. It seems as if Suspending to
ram just magically works for most people.
So I know that using the menu (KDE Plasma) Suspend to Ram in all fairness
just shuts down.
Now testing last night I could 'sudo systemctl suspend' and it worked.
First tkme for a minute, second time for 10 and the third overnight.
Fast-forward to this evening, I ran 'sudo systemctl suspend' upon leaving
the office. Get home and about an hour later I open the lid and it's shut
down and rebooted yet again.
So my question is, where are the most effective places (logs, config files)
to look to troubleshoot WTF is happening?
On 2018-01-31 03:23, users-request(a)lists.fedoraproject.org wrote:
> Date: Tue, 30 Jan 2018 08:44:50 -0600
> From: Richard Shaw <hobbes1069(a)gmail.com>
> Subject: Re: Organising photos visually
> To: Community support for Fedora users <users(a)lists.fedoraproject.org>
> Content-Type: multipart/alternative;
> Content-Type: text/plain; charset="UTF-8"
>> From what I could tell searching google, you best bet is to plug in
> info you need into the EXIF data and then rename the files based on the
> EXIF data.
> I've never used this before but it only took me about 10 minutes to
> If someone finds it useful (for this or in general) I may be willing to
> submit a review request to include it in Fedora.
On Fedora 27 x86_64:
Traceback (most recent call last):
File "/bin/photini", line 6, in <module>
from pkg_resources import load_entry_point
line 3037, in <module>
line 3021, in _call_aside
line 3050, in _initialize_master_working_set
working_set = WorkingSet._build_master()
line 655, in _build_master
line 969, in require
needed = self.resolve(parse_requirements(requirements))
line 855, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'appdirs>=1.3' distribution was
not found and is required by Photini
PO Box 896
Cowra NSW 2794
fedora-using colleague just asked me how easy it would be to install
everything necessary to start playing with linux foundation's
hyperledger (blockchain), apparently including hyperledger fabric and
composer, and whatever else can be crammed onto a fully-updated fedora
i poked around, found this:
so i just tried to follow along but i am by no means a node.js expert,
and when i tried to install composer-cli with "npm" globally:
$ sudo npm install -g composer-cli
i get various warnings about deprecated modules, about a bazillion
warnings that i have no permission ...
"to access the dev dir
and warnings like:
"ajv-keywords(a)2.1.1 requires a peer of ajv(a)^5.0.0 but none is
installed. You must install peer dependencies yourself"
which makes me nervous that i have no freaking clue what i'm doing
here, and have no idea which warnings are significant and which
i'm sure i can tease all this out eventually, but has anyone already
gone through this exercise and written it up somewhere?
Robert P. J. Day Ottawa, Ontario, CANADA
followup to last query, since i have never *knowingly* done anything
with nodejs, i'm wondering how safe i am to try to wipe every trace of
it from my own fedora 27 system, then re-install.
first, it *appears* that from a package perspective, no other
*packages* appear to depend on nodejs other than the npm management
$ rpm -q --whatrequires nodejs
$ rpm -q --whatrequires npm
no package requires npm
which suggests i can remove those two.
as for what i just installed with "npm", i tried both a local and a
global ("-g") install with npm, and the end result appeared to be
simply dumping content into a "node_modules/" directory, either in my
current directory or under /usr/lib. and there are also new
directories in my home directory, .npm/ and .node-gyp. am i safe to
just remove all of the above to pretend none of this ever happened?
Robert P. J. Day Ottawa, Ontario, CANADA
On rebooting today my system took an age to shutdown, for no apparent
reason but possibly related to NFS mounts. Anyway, I looked at the
journal and spotted this snippet:
Jan 24 11:47:59 bree systemd: Shutting down.
Jan 24 11:47:59 bree systemd: Hardware watchdog 'iTCO_wdt', version
Jan 24 11:47:59 bree systemd: Set hardware watchdog to 10min.
Jan 24 11:47:59 bree kernel: watchdog: watchdog0: watchdog did not
Jan 24 11:47:59 bree systemd-shutdown: Sending SIGTERM to remaining processes...
So apparently systemd is setting a watchdog timer for 10 minutes, for
some reason best known to itself. How can I change this to (say) 5
seconds, which would be more than enough for my setup?
Also, I don't know what 'watchdog did not stop!' is supposed to mean.
When doing a tar -xzf ... of a big source tar on an NFSv4 file system
the time taken is huge. I am seeing an overall data rate of about 1
MByte per second across the network interface.
If I copy a single large file I see a network data rate of about 110
MBytes/sec which is about the limit of the Gigabit Ethernet interface I
Now, in the past I have used the NFS "async" mount option to help with
write speed (lots of small files in the case of an untar of a set of
However, this does not seem to speed this up in Fedora27 and also I
don't see the "async" option listed when I run the "mount" command. When
I use the "sync" option it does show up in the "mount" list.
The question is, is the "async" option actually working with the NFS v4
in Fedora27 ?
I run Plasma specifically, and in chasing down some journalctl errors today
I found a few that were errors generated by gnome dependencies. Since I
dont use Gnome I want to remove it. However running dnf remove
@gnome-desktop also want's to remove things like qemu, and seabios. Two
VERY IMPORTANT things that I use on a daily basis with my WIn10 kvm guest.
Is it possible to remove gnome but leave the unused and dependant packages?
I have Fedora 27 installed in a Lenovo ThinkPad P51, working pretty
good since november, but today, after the last update, Gnome crashes
when I connect any device in any usb port, usb stick, external drive or
The last messages in dmesg when I disconnect the usb are like the
[ 281.527389] cdc_acm 1-1:1.2: urb 4 failed submission with -19
[ 281.528593] xhci_hcd 0000:00:14.0: WARN Cannot submit Set TR Deq Ptr
[ 281.528607] xhci_hcd 0000:00:14.0: A Set TR Deq Ptr command is
[ 281.528610] cdc_acm 1-1:1.2: urb 13 failed submission with -19
[ 281.529927] xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed
due to incorrect slot or ep state.
In don't know where can I search to solve the problem.
Any help would be appreciated.
1. The installation enabled LUKS encryption at install time.
2. At every clean shutdown and reboot, the user enters the LUKS
password, and then fsck takes place - EVERY TIME!!!
Is this due to LUKS? If so, how can the user remove the LUKS feature?
4. After setting the firefox preferences, single clicking on the firefox
icon on the panel, pops up 2 firefox instances. I checked the
and firefox is invoked only once in the command field.
This does not happen with other icons, such as thunderbird.
Thanx for any clues to these issues.