Re: VLC could not decode the format "h264" (H264 - MPEG-4 AVC (part 10))

2022-08-03 Thread Javier Perez
[pepebuho@pepewin ~]$ vlc -l | grep 264
VLC media player 3.0.17.2 Vetinari (revision )
  h264   H.264 video packetizer
  h26x   H264 video demuxer
  x264   H.264/MPEG-4 Part 10/AVC encoder (x264)
  x26410bH.264/MPEG-4 Part 10/AVC encoder (x264 10-bit)
  qsvIntel QuickSync Video encoder for
MPEG4-Part10/MPEG2 (aka H.264/H.262)

On Mon, Aug 1, 2022 at 9:08 PM Samuel Sieb  wrote:

> On 8/1/22 18:42, Javier Perez wrote:
> > Input #0, matroska,webm, from 'test_file.mkv':
> >Metadata:
> >  title   : test_file
> >  COMMENT :
> >  ENCODER : Lavf58.20.100
> >Duration: 01:04:22.25, start: 0.00, bitrate: 622 kb/s
> >Stream #0:0(eng): Video: h264 (High), yuv420p(progressive), 720x360
>
> That looks like a normal file.
> What does "vlc -l | grep 264" show?
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
>


-- 
--
 /\_/\
 |O O|  pepeb...@gmail.com
  Javier Perez
   While the night runs
   toward the day...
  m m   Pepebuho watches
from his high perch.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Switchdesk functionality has disappeared

2022-08-03 Thread stan via users
On Tue, 2 Aug 2022 23:56:39 -0400
Robert McBroom via users  wrote:

> Fedora 36 booting mode 3 to a command line boot, the switchdesk entry 
> Plasma doesn't do anything. I can switch from the default Gnome to
> xfce and back. The LXDE desktop is not there at all. Getting a xterm
> with xinit and all the desktop sessions can be started. Booting with
> a display manager has an entry for Plasma(X11) that works, but none
> for LXDE. The gui for switchdesk does not show Plasma or LXDE. What
> needs to be done to get these functions back?

It seems that latest switchdesk
Name: switchdesk
Version : 5.0.1
Release : 13.fc37
Architecture: noarch
doesn't have either of those available.

switchdesk/usr/share/switchdesk/Xclients.enlightenment
switchdesk/usr/share/switchdesk/Xclients.fluxbox
switchdesk/usr/share/switchdesk/Xclients.fvwm
switchdesk/usr/share/switchdesk/Xclients.gnome
switchdesk/usr/share/switchdesk/Xclients.icewm
switchdesk/usr/share/switchdesk/Xclients.kde
switchdesk/usr/share/switchdesk/Xclients.toplevel
switchdesk/usr/share/switchdesk/Xclients.twm
switchdesk/usr/share/switchdesk/Xclients.wmaker
switchdesk/usr/share/switchdesk/Xclients.xfce

But, when I start it in a console, or in X, it indicates that plasma is
available.  That must be in the kde entry above, though maybe it says
plasma when it means the wayland version instead of the x11 version.

A manual workaround, is:

For LXDE, put 

#! /usr/bin/bash

exec startlxde

in a file ~/.Xclients and then run startx to run LXDE.

And for plasma, replace startlxde with startplasma-x11.

I haven't looked at the source for switchdesk, but it shouldn't be too
difficult to patch it to add startlxde, or even startplasma-x11.  Just
duplicate what is done for xfce.  I notice that both mate and cinnamon
are also missing from the list above.  Seems switchdesk needs some love.

I don't use a greeter / desktop manager so I'm not sure, but I think if
the desktop is installed, they should all have the ability to switch to
that desktop available.  Have you tried a different desktop manager? As
I say, I'm not familiar, but others have mentioned sddm or lightdm.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Apache and umask for document root

2022-08-03 Thread Emmett Culley via users

On 8/2/22 8:47 PM, Tim via users wrote:

On Tue, 2022-08-02 at 15:22 +, Emmett Culley via users wrote:

So wordpress automaticaly has the ability to write all files in the
root directory.  I suppose we have to trust that wordpress will not
write hacked files to the server's root.


You are aware that it has a bad reputation for security?  You'll need
to keep on top of it being updated all the time.  It's a prime target.


So it behoovs our site webmasters to not unstall untrusted plugins.


This is where you need one or two competent and trustworthy webmasters.
General page authors aren't webmasters.
  

Thanks for your comments.

All true.  And there is nothing to do but grin and bear it, as many of our clients want 
to use wordpress.  We keep a watch for "bad" files, and we also survey what 
plugins are installed and when a new one shows up one of us researches it.  We have found 
a couple of bad actors, but if a webmaster sticks to wordpress approved plugins, we see 
no issues our current methods cannot mitigate.

Right now we are dealing with DIVI booster issues.  It wants write access to 
wp-content anytime you edit the site.  I've contected them, but so for no 
response.  In the mean time I have to temporarily enable apache write access to 
wp-content, then reinstect the site' files after disableing that access.  If is 
isn't fixed by DIVI booster soon I will require that the client uninstall that 
theme plugin.  They won't be happy, but they will like that better than getting 
a bill every tiem they need to edit their site.

I am considering changing the name of the wp-content directory, but obfuscation 
only gives false confidence as hack mitigation.  Besides, that would require 
hands of from our engineers for each wordpress site.

Emmett
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: VLC could not decode the format "h264" (H264 - MPEG-4 AVC (part 10))

2022-08-03 Thread Samuel Sieb

On 8/3/22 04:12, Javier Perez wrote:

[pepebuho@pepewin ~]$ vlc -l | grep 264
VLC media player 3.0.17.2 Vetinari (revision )
   h264                   H.264 video packetizer
   h26x                   H264 video demuxer
   x264                   H.264/MPEG-4 Part 10/AVC encoder (x264)
   x26410b                H.264/MPEG-4 Part 10/AVC encoder (x264 10-bit)
   qsv                    Intel QuickSync Video encoder for 
MPEG4-Part10/MPEG2 (aka H.264/H.262)


I have no idea why yours isn't working.  Everything looks normal.
Try creating a new user and see if it works there.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: 32-->36?

2022-08-03 Thread ToddAndMargo via users

On 7/30/22 16:50, ToddAndMargo via users wrote:

Hi All,

I have a customer who FINALLY agreed to have me upgrade
his Fedora 32 server to 36.

Can I jump directly, or do I have to go one or
two revisions at a time?

Many thanks,
-T





Follow up:

I went from 32 to 34 to 36.

from 32 to 34 I had to remove a stary iptables
(I am using netfilter).

Other than that, it went complete smooth!

And I did it all remotely over ssh!

ftp and samba and all perfectly behaving too.

Thank you all again for all the tips and help!


-T

now to calm the SELINUX errors!
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue