Re: xdg-email config

2018-06-12 Thread Curt
On 2018-06-11, Pierre Frenkiel  wrote:
> On Mon, 11 Jun 2018, Curt wrote:
>
>> ~/.local/share/applications/mimeapps
>>
>> which contains, in my case
>>
>> [Default Applications]
>> x-scheme-handler/mailto=alpine.desktop
>>
> I have also a mimeapps.list with that line in .config and 
> .local/share/applications
> but that doesn't solve the problem. The only work around I found was using 
> the 
> script I mentionned earlier.
>
> best regards,

What does  "XDG_UTILS_DEBUG_LEVEL=2 xdg-email" say? 

curty@einstein:~$ XDG_UTILS_DEBUG_LEVEL=2 xdg-email
Checking /home/curty/.config/mimeapps.list
Checking /home/curty/.local/share/applications/mimeapps.list
Running gvfs-open "mailto:";



Re: xdg-email config

2018-06-12 Thread Pierre Frenkiel

On Tue, 12 Jun 2018, Curt wrote:


What does  "XDG_UTILS_DEBUG_LEVEL=2 xdg-email" say?


   Checking /data/home/frenkiel/.local/share/applications/mimeapps.list
   Selected DE generic
   Checking /data/home/frenkiel/.local/share/applications/mimeapps.list

best regards,
--
Pierre Frenkiel



Software and Updates Restart notification Stretch

2018-06-12 Thread Anil Duggirala
hello,
I am getting a notification in Gnome saying there are packages to be
updated and I get the option to click on a button saying Update and
Restart. However, if I do a regular apt upgrade, I dont need to restart
my system. Why am I getting this notification? since when do I need to
restart my system to upgrade any package in Debian?
thanks,



Re: Software and Updates Restart notification Stretch

2018-06-12 Thread tomas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Jun 12, 2018 at 08:30:39AM -0500, Anil Duggirala wrote:
> hello,
> I am getting a notification in Gnome saying there are packages to be
> updated and I get the option to click on a button saying Update and
> Restart. However, if I do a regular apt upgrade, I dont need to restart
> my system. Why am I getting this notification? since when do I need to
> restart my system to upgrade any package in Debian?

No need to restart for an upgrade. But sometimes, the upgrade will only
take effect after a restart: it's obvious in the case of the kernel,
but also for some core libraries.

Many "services" (database, web server) are restarted after the upgrade
without need to restart the whole system.

Cheers
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlsf0+4ACgkQBcgs9XrR2kZXpACfTsH/iv6iqmHFH5jSieSfXuiv
ujUAn0D5Gb+jb+d6TJHZyrl/bHa5j9vh
=hZi3
-END PGP SIGNATURE-



Re: Software and Updates Restart notification Stretch

2018-06-12 Thread Anil Duggirala
> No need to restart for an upgrade. But sometimes, the upgrade will only
> take effect after a restart: it's obvious in the case of the kernel,
> but also for some core libraries.
> 

Why has this become a "default" behavior, at least with Gnome, in Debian 
Stretch then ? A notification appears asking the user to upgrade and restart 
the whole system. If it is not necessary, why has this feature been implemented 
as part of the DE?



Re: Software and Updates Restart notification Stretch

2018-06-12 Thread Dan Ritter
On Tue, Jun 12, 2018 at 09:31:47AM -0500, Anil Duggirala wrote:
> > No need to restart for an upgrade. But sometimes, the upgrade will only
> > take effect after a restart: it's obvious in the case of the kernel,
> > but also for some core libraries.
> > 
> 
> Why has this become a "default" behavior, at least with Gnome, in Debian 
> Stretch then ? A notification appears asking the user to upgrade and restart 
> the whole system. If it is not necessary, why has this feature been 
> implemented as part of the DE?
> 

Because the feature comes from GNOME, who have always been
interested in supporting the least knowledgeable user whenever
possible.

For those users, it is hard to explain how an update might or
might not take effect without a reboot.

-dsr-



Latest version of X not starting in buster

2018-06-12 Thread Siard
A couple of months ago, xserver-common, xserver-xorg-core and 
xserver-xorg-legacy
were upgraded from version 1.19.2 to 1.19.6 in Buster.

But since then, when starting X from the console, the process soon comes to a
grinding halt. These are the last lines:

(==) Log file: "/home//local/share/xorg/Xorg.0.log", Time: Tue Jun 12 
16:18:18 2018
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"

When I downgrade the three packages back to 1.19.2, same as in Stretch, then
X starts without problems.
Now that 1.19.6 still does not work after a few months, what could be the 
reason?


These are the last lines in the mentioned log file:

[30.968] (EE) xf86OpenSerial: Cannot open device /dev/console
Permission denied.
[30.968] (II) console: opening input device '/dev/console' failed 
(Permission denied).
[30.968] (II) console - failed to create input device '/dev/console'.
[30.968] (EE) libinput: (unnamed): Failed to create a device for 
/dev/console
[30.968] (EE) PreInit returned 2 for "(unnamed)"
[30.968] (II) UnloadModule: "libinput"
[30.968] (II) config/udev: Adding input device (unnamed) (/dev/ptmx)
[30.968] (**) (unnamed): Applying InputClass "Logitech USB Laser Mouse"
[30.968] (II) Using input driver 'libinput' for '(unnamed)'
[30.969] (EE) systemd-logind: failed to take device /dev/ptmx: No such 
device
[30.969] (**) (unnamed): always reports core events
[30.969] (**) Option "Device" "/dev/ptmx"
[30.969] (**) Option "_source" "server/udev"



Re: Software and Updates Restart notification Stretch

2018-06-12 Thread Darac Marjal

On Tue, Jun 12, 2018 at 11:04:12AM -0400, Dan Ritter wrote:

On Tue, Jun 12, 2018 at 09:31:47AM -0500, Anil Duggirala wrote:

> No need to restart for an upgrade. But sometimes, the upgrade will only
> take effect after a restart: it's obvious in the case of the kernel,
> but also for some core libraries.
>

Why has this become a "default" behavior, at least with Gnome, in Debian 
Stretch then ? A notification appears asking the user to upgrade and restart the whole 
system. If it is not necessary, why has this feature been implemented as part of the DE?



Because the feature comes from GNOME, who have always been
interested in supporting the least knowledgeable user whenever
possible.

For those users, it is hard to explain how an update might or
might not take effect without a reboot.


Really? The 'needrestart' package seems to do quite a good job of this. 
The main issue is that, if a library is upgraded, then a long-running 
process probably won't notice (aside: on Linux, one can delete a file 
and replace it, but a process with a handle to the old file generally 
won't be affected). needrestart scans the process table after an upgrade 
and, if a process has a handle to a deleted library, it is noted. If 
that process is part of a service, needrestart gives the option to 
restart the service. If the process is part of user session, then 
needrestart can pop-up a message telling the user to either restart the 
application (e.g. in the case of their browser) or to logout-login (e.g. 
in the case of a window manager).


Now, it may be the case that there are so many applications running that 
it's just as easy to reboot as it is to close and restart them all, but 
that's up to the user.




-dsr-



--
For more information, please reread.


signature.asc
Description: PGP signature


Re: Your Epic Games Account Has Been Created

2018-06-12 Thread Hans Vogelsberger
Am Tue, 12 Jun 2018 10:02:13 +
schrieb Epic Games :

> Account Created.
> 
> 
> Hi QWBxj1517!
> 
> You have successfully created an Epic Games account.
> 
> Thank you for signing up!
> 
> Kind Regards,
> Your Friends at Epic
> 
> 
> Need Help? h...@epicgames.com (mailto:h...@epicgames.com?subject=My
> Subject ID)
> 
> © 2004-2018, Epic Games, Inc. All rights reserved. Epic Games, Unreal
> Tournament, Fortnite, Paragon, Unreal, Unreal Engine, UE4 and their
> respective logos are Epic's trademarks or registered trademarks in
> the United States of America and elsewhere. Terms of Service
> (https://www.epicgames.com/tos) | Privacy Policy
> (https://www.epicgames.com/privacypolicy)


No, I never did anything to create an account at Epic Games. I do not
even know who or what Epic Games is. You better take me off your lists
and tell me this before I look what State Attorney is in charge of
things like that.

Hans Vogelsberger



Hibernation does not work after upgrade to Stretch

2018-06-12 Thread Piotr
Dear all,

Recently I upgraded my Jessie to Stretch and since then I do not have working 
hibernation.

When I do hibernate-disk, then it seems to be making a memory snapshot,
but when I restart I gets a hang up with a black screen or reboot
(depends on which kernel version I use). Already tried with
4.16.0-0.bpo.2-686-pae, 4.16.0-0.bpo.1-686-pae and with
linux-image-3.16.0-5-686-pae. 

How should I debug this issue and fix it?

Regards,
Piotr



Re: Software and Updates Restart notification Stretch

2018-06-12 Thread Dan Ritter
On Tue, Jun 12, 2018 at 04:14:23PM +0100, Darac Marjal wrote:
> On Tue, Jun 12, 2018 at 11:04:12AM -0400, Dan Ritter wrote:
> > On Tue, Jun 12, 2018 at 09:31:47AM -0500, Anil Duggirala wrote:
> > > > No need to restart for an upgrade. But sometimes, the upgrade will only
> > > > take effect after a restart: it's obvious in the case of the kernel,
> > > > but also for some core libraries.
> > > >
> > > 
> > > Why has this become a "default" behavior, at least with Gnome, in Debian 
> > > Stretch then ? A notification appears asking the user to upgrade and 
> > > restart the whole system. If it is not necessary, why has this feature 
> > > been implemented as part of the DE?
> > > 
> > 
> > Because the feature comes from GNOME, who have always been
> > interested in supporting the least knowledgeable user whenever
> > possible.
> > 
> > For those users, it is hard to explain how an update might or
> > might not take effect without a reboot.
> 
> Really? The 'needrestart' package seems to do quite a good job of this. The
> main issue is that, if a library is upgraded, then a long-running process
> probably won't notice (aside: on Linux, one can delete a file and replace
> it, but a process with a handle to the old file generally won't be
> affected). needrestart scans the process table after an upgrade and, if a
> process has a handle to a deleted library, it is noted. If that process is
> part of a service, needrestart gives the option to restart the service. If
> the process is part of user session, then needrestart can pop-up a message
> telling the user to either restart the application (e.g. in the case of
> their browser) or to logout-login (e.g. in the case of a window manager).

Sure, needrestart works for Debian. It's not always installed,
though. You could make it a dependency -- and now GNOME depends
on a non-GNOME package. The integration will be different for
each distribution. 

The GNOME people don't care. If you want this to happen in Debian,
you need the Debian people packaging GNOME to care about it.

-dsr-



Re: Hibernation does not work after upgrade to Stretch

2018-06-12 Thread Hans
Am Dienstag, 12. Juni 2018, 17:31:44 CEST schrieb Piotr:
Same here, just almost since a year. I doubt, this will be fixed. As far as I 
read, this is too difficult for the developers, due to the very different 
hardware. The problem is, the playing together with kernel, hardware and 
hibernation software is too complex, so there is only little chance, this bug 
can be dfixed at all.

Sorry, to disappoint you at the moment.

Best 

Hans

> Dear all,
> 
> Recently I upgraded my Jessie to Stretch and since then I do not have
> working hibernation.
> 
> When I do hibernate-disk, then it seems to be making a memory snapshot,
> but when I restart I gets a hang up with a black screen or reboot
> (depends on which kernel version I use). Already tried with
> 4.16.0-0.bpo.2-686-pae, 4.16.0-0.bpo.1-686-pae and with
> linux-image-3.16.0-5-686-pae.
> 
> How should I debug this issue and fix it?
> 
> Regards,
> Piotr






/etc/localtime and How it Works

2018-06-12 Thread Martin McCormick
After getting curious about what all is in /etc/localtime, I
found out that one can read the binary with zdump.  zdump -v
filename produces a number of lines that correspond to continuity
breaks such as the shift from standard time in Winter to Daylight
Saving Time or Summer Time.

I happen to live in the Central United States so
/etc/localtime is a copy of /usr/share/zoneinfo/America/Chicago
and zdump -v of this file shows about 450 lines showing the start
and end of DST from 1901 through 2038 when we run out of bits in
the current 32-bit counter.

One striking change is the switch to War Time that
started in February of 1942 and ended on August 14 of 1945 with
no modification of any kind between those two dates.

Some parts of the country actually added two hours of
time shifting in Summer and then dropped back to 
War Time in the Winter.  The Chicago file shows a single hour of
time shift during War time.

I looked at /usr/share/zoneinfo/America/New_York to see
what the Eastern Time Zone did and got a surprise.  Instead of
450 odd lines, there are only 4 which basically describe the
1901-2038 life span of the file.

I was expecting America/New_York to look just like
America/Chicago except for the UTC offset and maybe some slightly
different dates back when DST was mostly used on the coasts and
not at all in much of the middle of the country.

Oklahoma and Texas, for example, didn't use any time
shifting except for War Time until 1967 after passage of the
Uniform Time Standards Act and a decision by all the major
television networks of the day to no longer send delayed
broadcasts down their wires to affiliates in states that didn't
observe DST.

So, my question is why is there such a difference between
the two files and how do people in the Eastern Time Zone
automatically learn of the two time shifts each year?

Martin McCormick



Re: /etc/localtime and How it Works

2018-06-12 Thread Greg Wooledge
On Tue, Jun 12, 2018 at 12:38:05PM -0500, Martin McCormick wrote:
>   I looked at /usr/share/zoneinfo/America/New_York to see
> what the Eastern Time Zone did and got a surprise.  Instead of
> 450 odd lines, there are only 4 which basically describe the
> 1901-2038 life span of the file.

wooledg:~$ zdump -v America/New_York | wc
   2324   37136  229862



Re: /etc/localtime and How it Works

2018-06-12 Thread Dan Ritter
On Tue, Jun 12, 2018 at 12:38:05PM -0500, Martin McCormick wrote:
>   I was expecting America/New_York to look just like
> America/Chicago except for the UTC offset and maybe some slightly
> different dates back when DST was mostly used on the coasts and
> not at all in much of the middle of the country.
> 
>   Oklahoma and Texas, for example, didn't use any time
> shifting except for War Time until 1967 after passage of the
> Uniform Time Standards Act and a decision by all the major
> television networks of the day to no longer send delayed
> broadcasts down their wires to affiliates in states that didn't
> observe DST.
> 
>   So, my question is why is there such a difference between
> the two files and how do people in the Eastern Time Zone
> automatically learn of the two time shifts each year?

You have just stepped into a minefield. It's a really
interesting one, though.

First: the compilation of timezone data is the Olson Database,
after the original editor. The current editor is Paul Eggert,
and the America/New_York style nomenclature is his fault.

https://www.iana.org/time-zones
https://en.wikipedia.org/wiki/Tz_database

Second: every decision recorded in the Olson Database is a
political decision. Science and engineering don't really 
enter into it much.

In many countries, the national government sets the standard,
and that's that. In the USA, the federal government sets the
dates for changing from standard to daylight saving time and
back, but does not mandate adoption of DST or any specific 
timezone.

You'd think that at least each state would be consistent
internally, but that's not necessarily the case either. 

https://en.wikipedia.org/wiki/Eastern_Time_Zone

So, to answer your question: laws are passed and the information
published in the same way that other laws are published, plus
newspapers and TV news and so forth tend to be vocal about the
issue. And Eggert learns about it and puts it in the database,
and then everybody makes changes to their copies of tz.

-dsr-



Re: /etc/localtime and How it Works

2018-06-12 Thread Martin McCormick
Greg Wooledge  writes:
> wooledg:~$ zdump -v America/New_York | wc
>2324   37136  229862

My mistake was that I used cd to get to
/usr/share/zoneinfo/America and then I did zdump -v New_York and
it didn't complain at all but printed out just the 4 lines that
made me think it was processing the file.  It's not but this is
probably a lead-in and lead-out that brackets the interpretation
of the binary data in the file.

giving zdump the America/New_York path produced output
that does, in fact, look just like America/Chicago except for the
things one would expect to be different such as the UTC offsets.

also, another poster mentioned about the information being based
on political decisions.  A perfect example just occurred in the
last few weeks in which the DPRK and ROK agreed to use the same
time zone again.  The difference had been 1800 seconds or 30
minutes.

Thanks.

Martin McCormick



combining stable and testing in sources.list

2018-06-12 Thread murtaugh
I mistakenly added two lines with 'testing' to my 'sources.list' file, 
which now looks like this:


   deb http://debian.osuosl.org/debian/ stretch main non-free contrib
   deb-src http://debian.osuosl.org/debian/ stretch main non-free contrib

   deb http://security.debian.org/debian-security stretch/updates main
   contrib non-free
   deb-src http://security.debian.org/debian-security stretch/updates
   main contrib non-free

   deb http://debian.osuosl.org/debian/ stretch-updates main contrib
   non-free
   deb-src http://debian.osuosl.org/debian/ stretch-updates main
   contrib non-free

   # my bad:
   deb http://ftp.us.debian.org/debian/ testing main non-free contrib
   deb-src http://ftp.us.debian.org/debian/ testing main non-free contrib

I have read that it's difficult or impossible to revert to 'stable' once 
'testing' packages have been installed. I have also read that it's not a 
good idea to have both 'stable' and 'testing' repositories in 
'sources.list', so I'm wondering how to proceed. I experimented with 
replacing 'stretch' by 'buster' in the first six lines above (and 
removing the last two lines), but then the system couldn't find the 
stable google-chrome repository in '/etc/apt/sources.list.d'.  I now 
have the uncomfortable feeling that I'm playing with fire.


Thanks in advance for any suggestions about if/how I should edit my 
'sources.list' file!


-Paul




Re: combining stable and testing in sources.list

2018-06-12 Thread George Shuklin
There is a bit of misunderstanding here. Lines in /etc/apt/sources.list 
(as well as in sources.list.d) are just a description of used 
repositories. By itself they couldn't change anything in the OS. When 
you 'apt-get update' it downloads package lists. This is fine, as no 
damage was done yet. But when you use apt-get upgrade, or apt-get 
install (something), then those new package lists may mess up system. 
The reason is that some packages may have other packages as 
dependencies, and those dependencies from the newer debian version may 
conflict with existing ones, or cause some packages removal (f.e. some 
package may say that it 'replaces' some other package).


Rolling back this testing/stable mix is a huge pain. If you done some 
minor installation of something without dependencies, than you may just 
revert it back to older version. It there was a major update, then... 
Well, upgrade to testing and live with it. Or reinstall OS.


If you want to understand the state of your system, look here:

/var/log/apt/history.log - log of installations/upgrades
/var/log/apt/term.log - output of installation process

You can see currently installed packages: dpkg -l
For each package you can see 'policy' by using apt-cache policy command. 
It shows which version of a given package is coming from which release. 
F.e.: apt-cache policy xpad


The main pain point here is dependencies of dependencies... I was able 
few times roll back back upgrade, but it took me few hours of heavy 
work, and I couldn't recommend doing this to anyone.


TL;DR;

1. If you just added those lines in sources.list - just remove them
2. If you added them and used apt-get update - remove them and call 
apt-get update again

3. If you installed or upgraded your system after that - you have a problem

On 12/06/18 22:15, murta...@stat.orst.edu wrote:


I mistakenly added two lines with 'testing' to my 'sources.list' file, 
which now looks like this:


deb http://debian.osuosl.org/debian/ stretch main non-free contrib
deb-src http://debian.osuosl.org/debian/ stretch main non-free contrib

deb http://security.debian.org/debian-security stretch/updates
main contrib non-free
deb-src http://security.debian.org/debian-security stretch/updates
main contrib non-free

deb http://debian.osuosl.org/debian/ stretch-updates main contrib
non-free
deb-src http://debian.osuosl.org/debian/ stretch-updates main
contrib non-free

# my bad:
deb http://ftp.us.debian.org/debian/ testing main non-free contrib
deb-src http://ftp.us.debian.org/debian/ testing main non-free contrib

I have read that it's difficult or impossible to revert to 'stable' 
once 'testing' packages have been installed. I have also read that 
it's not a good idea to have both 'stable' and 'testing' repositories 
in 'sources.list', so I'm wondering how to proceed.  I experimented 
with replacing 'stretch' by 'buster' in the first six lines above (and 
removing the last two lines), but then the system couldn't find the 
stable google-chrome repository in '/etc/apt/sources.list.d'.  I now 
have the uncomfortable feeling that I'm playing with fire.


Thanks in advance for any suggestions about if/how I should edit my 
'sources.list' file!


-Paul






Re: Hibernation does not work after upgrade to Stretch

2018-06-12 Thread Piotr
On Tue, 12 Jun 2018 18:12:42 +0200
Hans  wrote:

> Am Dienstag, 12. Juni 2018, 17:31:44 CEST schrieb Piotr:
> Same here, just almost since a year. I doubt, this will be fixed. As far as I 
> read, this is too difficult for the developers, due to the very different 
> hardware. The problem is, the playing together with kernel, hardware and 
> hibernation software is too complex, so there is only little chance, this bug 
> can be dfixed at all.
> 
> Sorry, to disappoint you at the moment.

It is pity that it worked well with Jessie with no hardware change. Somebody 
told me that I should try different kernel versions, but even the latest does 
not work. It was nice to have a hibernate to disk, but now I have to live 
without it. Luckily debian starts fast on my old laptop,

Thanks for the info.

Regards,
Piotr



SSL to TLS

2018-06-12 Thread culser

In Debian i will need to change over to the TLS secure protocol.

is this done by certificate update or must i also update the software.

in particular i am using Perl to send and receive i believe SSL protocol 
now.


my current Debian is 4.1.2-25, Kernel 2.6.26-2 Amd, Apache 2, Postfix

other system info: curl 7.18.2 (x86_64-pc-linux-gnu) libcurl/7.18.2 
OpenSSL/0.9.8g zlib/1.2.3.3 libidn/1.8 libssh2/0.18


and if i must change the software is there a seemless way to upgrade 
without altering other settings.




Re: SSL to TLS

2018-06-12 Thread Dan Purgert
culser wrote:
> [...]`
> my current Debian is 4.1.2-25, Kernel 2.6.26-2 Amd, Apache 2, Postfix

Debian 4, as in Etch, which has been obsolete for 8 years now?

Yes, yes you absolutely need to upgrade.


-- 
|_|O|_| Registered Linux user #585947
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281



Re: Hibernation does not work after upgrade to Stretch

2018-06-12 Thread davidson

On Tue, 12 Jun 2018, Piotr wrote:


Dear all,

Recently I upgraded my Jessie to Stretch and since then I do not
have working hibernation.

When I do hibernate-disk, then it seems to be making a memory
snapshot, but when I restart I gets a hang up with a black screen or
reboot (depends on which kernel version I use). Already tried with
4.16.0-0.bpo.2-686-pae, 4.16.0-0.bpo.1-686-pae and with
linux-image-3.16.0-5-686-pae.

How should I debug this issue and fix it?


No idea.

Killing some idle time with

  backport kernel stretch hibernation site:debian.org

at a search engine eventually led me to this 2007 document, which
looks interesting:

  https://www.kernel.org/doc/Documentation/power/basic-pm-debugging.txt

I have not yet read it in full, (and so, obviously) have never used it
myself.

--

It's gotten to the point where I get immediately suspicious whenever
anybody starts talking about "civility," "tone," or as Iowa Public
Radio touts itself, "with no shouting." Oh thank heavens, waving my
fan to cool myself from those torrid opinions.

twitter.com/bluntedpurpose/status/1001567312057651201



Hardware decoding of video not working in VLC

2018-06-12 Thread Celejar
My machine is a ThinkPad W550s, with an i7-5500U CPU and Intel HD
Graphics 5500. Hardware decoding of video works fine with mpv (using
vaapi), but not with vlc:

mpv without hardware decoding:

$ time mpv Rogue\ One\ -\ A\ Star\ Wars\ Story\ -\ Trailer.mp4 
Playing: Rogue One - A Star Wars Story - Trailer.mp4
[ffmpeg/demuxer] mov,mp4,m4a,3gp,3g2,mj2: stream 0, timescale not set
 (+) Video --vid=1 (*) (h264)
 Video --vid=2 [P] (mjpeg)
 (+) Audio --aid=1 --alang=eng (*) (aac)

...

AO: [alsa] 48000Hz stereo 2ch float
VO: [opengl] 1920x816 yuv420p
AV: 00:02:06 / 00:02:06 (99%) A-V:  0.000

...

real2m6.828s
user0m36.432s
sys 0m1.356s

mpv with hardware decoding:

$ time mpv --hwdec=vaapi Rogue\ One\ -\ A\ Star\ Wars\ Story\ -\ Trailer.mp4 
Playing: Rogue One - A Star Wars Story - Trailer.mp4
[ffmpeg/demuxer] mov,mp4,m4a,3gp,3g2,mj2: stream 0, timescale not set
 (+) Video --vid=1 (*) (h264)
 Video --vid=2 [P] (mjpeg)
 (+) Audio --aid=1 --alang=eng (*) (aac)

...

libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
AO: [alsa] 48000Hz stereo 2ch float
Using hardware decoding (vaapi).
VO: [opengl] 1920x816 vaapi
AV: 00:02:06 / 00:02:06 (99%) A-V:  0.000

...

real2m7.019s
user0m3.224s
sys 0m1.608s

[Note the decrease in CPU usage ("user").]

With vlc, the CPU usage remains roughly the same (high), regardless
of whether hardware decoding is enabled or not.

vlc without hardware decoding:

$ time vlc Rogue\ One\ -\ A\ Star\ Wars\ Story\ -\ Trailer.mp4 
VLC media player 3.0.2 Vetinari (revision 3.0.2-0-gd7b653cf14)
[55aad94521a0] main libvlc: Running vlc with the default interface. Use 
'cvlc' to use vlc without interface.
QObject::~QObject: Timers cannot be stopped from another thread

real2m20.461s
user0m43.796s
sys 0m1.292s

vlc with hardware decoding:

$ time vlc --avcodec-hw vaapi Rogue\ One\ -\ A\ Star\ Wars\ Story\ -\ 
Trailer.mp4 
VLC media player 3.0.2 Vetinari (revision 3.0.2-0-gd7b653cf14)
[5586746a81a0] main libvlc: Running vlc with the default interface. Use 
'cvlc' to use vlc without interface.
QObject::~QObject: Timers cannot be stopped from another thread

real2m10.894s
user0m43.276s
sys 0m1.808s

I've tried other values for --avcodec, as well as enabling hardware
acceleration from the GUI, to no avail - I get no reduction in CPU
usage.

The Arch Wiki indeed claims that hardware decoding only works with mpv,
and not with vlc:

https://wiki.archlinux.org/index.php/Mpv#Hardware_decoding

But vlc's own documentation claims that hardware decoding should work:

https://wiki.videolan.org/VLC_GPU_Decoding

Trying to figure out hardware decoding is pretty frustrating - the web
seems full of inconsistent, outdated, and just plain wrong information.
Any ideas?

Celejar