I just installed TLP on a thinkpad T450 for Fedora 25 - Mate following
the instructions given by the tlp website. The tlp systemd service is
running and tlp-stat reports that it is enabled.
Is it necessary to disable mate-power-manager in anyway? Does tlp use
the settings provided in the power manager gui to control display
brightness/computer sleep timing or do I need to reconfigure these
My googlefoo is lacking me in finding a definitive answer on these points.
On 05/28/2017 02:21 AM, Paul Allen Newell wrote:
> On 05/28/2017 01:40 AM, Tom H wrote:
>> You replied off-list
>> On Sun, May 28, 2017 at 4:16 AM, Paul Allen Newell
>> <pnewell(a)cs.cmu.edu> wrote:
>>> On 05/28/2017 01:04 AM, Tom H wrote:
>>>> "-i" is faster than "su -l" :)
>> sudo -i
>> is faster than
>> sudo su -l
> Apologies for replying off-list, it was not intentional.
> I was unaware of the "-i" option for sudo. Am reading online man pages
> on it and beginning to understand.
> Thanks for reply as I try to understand "-i"
Correcting my off-list post by cc-ing back to the list ... once again,
I've got a file.. with a bunch of lines looking like:
$bookVariable['wmich']['Summer II 2017']='1';
$bookVariable['wmich']['Summer I 2017']='1';
I''m looking to get the "text" inside the 1st group of brackets 
The following sed only gets the 1st 3 lines.. and it doesn't completely work.
sed -n "s/^.*bookVariable\['\(\S*\)'].*$/\1/p" foo.txt
Version: 17.3.0 (revision 8467)
cannot play mkv files :(
The video player I select in preferences is mplayer.
Even if I change it to mpv, it will not play mkv.
However, if I invoke either mplayer or mpv from command line, then
they do play the .mkv file.
Some years ago I had an IBM ThinkPad that one day failed to boot, and every
subsystem diagnostic that ran at power-up (keyboard, memory, disk
controller, ...) reported a problem. On a whim I put in a new clock
battery and everything was fine. Now any time a machine suddenly goes
flakey, the clock battery is the first thing that gets replaced.
On Fri, May 26, 2017 at 21:22:17 +0930,Tim wrote:
> On Thu, 2017-05-25 at 12:47 -0700, Rick Stevens wrote:
> > Otherwise, with a weak battery the BIOS will usually revert to default
> > settings which are generally considered conservative and "safe".
> I'm not so sure that's the case. In many PCs, the BIOS clock, BIOS
> memory, and perhaps other BIOS hardware, are powered solely by the
> battery (even when the computer is running off mains power). So, with
> failing power you could have all manner of random things happen.
I need OpenVPN 2.3 because the end router has an outdated OpenVPN
version and OpenVPN 2.4 broke compatibility.
2 weeks ago I accidentally updated to 2.4 but I managed to do dnf downgrade.
However, after I updated Fedora 25 today I can no longer downgrade, it
says it is at lowest version.
OpenVPN upgraded even tho I explicitely set
What is the correct way to avoid this in the future? How to properly
prevent package from updating?
Luckily I found 2.3 rpm on rpmfind so the day is saved for now.
This is an f24 system. I just (about 1pm US mountain time) completed my
weekly "dnf upgrade", and I saw no hint of failure or trouble. But when
I shut down the system, and then powered back up, the boot failed. The
grub menu looked ok. The blue-and-white bar at the bottom of the boot
screen did go most of the way normally. But it never got to the log in
screen. There was some text being displayed, but I have no way of
capturing it, and I don't remember what it said.
I'm no sys. admin. I have no idea what to do. Please help. (I'm using
a windows 7 system for this e-mail.)
Thank-you in advance.
Within the last couple of days an update is causing LibreOffice to
crash. When I click on the icon, recovery mode comes up, but there is no
file to recover, and when I click "OK" the Logo comes up briefly and
then goes away. When I try to run from the command line, I get
I have tried reinstalling but get the same "Application error" when I
attempt to run it from the command line.
W.Paul Erickson MCP Registered Clinical Counsellor
"Society needs to rethink how it treats those
who do the jobs we don't want to do." Dr. Marv Westwood
I have a computer running fc25.x86_64. It has one folder, /home/photo,
with ~100 GB of photographs (about 40K files) organized in many
subfolders named like username/year/YYYYMMDD-event
I use rsync to have a full copy of that folder on an external drive,
connected via USB. This morning, rsync copied many new files without
problems, but at a certain point it failed. It left behind on the drive
a folder which "looks" empty, but it isn't, and cannot be removed.
Commands and error messages are below.
The questions are
- may this be a software-only problem? Maybe caused by "system
overload"? I also had a text-analysis script running, using all the RAM
and CPU it could get. Also, probably irrelevant: at some point one of
the kids plugged a smartphone into another USB port, to recharge it :
- assuming the fault is not in the drive... how should I get rid of that
corrupted folder? I already tried unmounting and remounting, but no
rsync -rvt --delete --no-o --no-g /home/photo/ /run/media/marco/TOSHIBA\
/dev/sda5 on /home type ext4 (rw,relatime,seclabel,data=ordered)
/dev/sdb1 on /run/media/marco/TOSHIBA EXT type fuseblk
RSYNC ERROR: many lines like this (many files copied properly before and
after that folder...)
rsync: mkstemp "/run/media/marco/TOSHIBA
Input/output error (5)
RSYNC FINAL MESSAGE:
rsync error: some files/attrs were not transferred (see previous errors)
(code 23) at main.c(1178) [sender=3.1.2]
SIZE OF ORIGINAL FOLDER ON THE COMPUTER (57 files):
ls -l /home/z/photo/marco/2016/ | grep 20161116-family
drwxrwxr-x. 2 marco marco 4096 Jan 1 20:23 20161116-family
SIZE AND CONTENT OF SAME FOLDER on the USB drive:
#> ls -l | grep 20161116-family
drwxrwxrwx. 1 marco marco 20480 Jan 1 20:23 20161116-family
#> ls -la 20161116-family/
ls: reading directory '20161116-family/': Input/output error
FOLDER CANNOT BE REMOVED (EVEN sudo rm -rf fails the same way)
#> rm -rf 20161116_1117-family/
rm: cannot remove '20161116-family/': Directory not empty