On 6/26/24 12:37 PM, Tim via users wrote:
Michael Hennebry:
Any ideas?
Samuel Sieb:
I don't. I usually use vlc, but I just tried totem (Videos) and it
played anything I tried, include h265.
I found totem rather bad for playing some files, likewise with parole
media player (what an awful na
Michael Hennebry:
>> Any ideas?
Samuel Sieb:
> I don't. I usually use vlc, but I just tried totem (Videos) and it
> played anything I tried, include h265.
I found totem rather bad for playing some files, likewise with parole
media player (what an awful name for a media player - and it nearly
al
On 6/25/24 4:15 PM, Michael Hennebry wrote:
On Mon, 24 Jun 2024, Samuel Sieb wrote:
On 6/24/24 5:58 PM, Michael Hennebry wrote:
On Mon, 24 Jun 2024, Patrick O'Callaghan wrote:
Note that gstreamer1-plugins-ugly is from RPMfusion because of
licensing issues.
# dnf search -v plugins-ugly
H
On 6/25/24 18:13, Doug Herr wrote:
On Mon, Jun 24, 2024, at 11:23 PM, Tim via users wrote:
Just adding my saved note on how it can be done:
Pull files out of an rpm without installing it:
mkdir foo ; cp file.rpm foo ; cd foo
rpm2cpio - < file.rpm | cpio --extract --no-absolute-filenames
--ma
On Mon, 24 Jun 2024, Samuel Sieb wrote:
On 6/24/24 5:58 PM, Michael Hennebry wrote:
On Mon, 24 Jun 2024, Patrick O'Callaghan wrote:
Note that gstreamer1-plugins-ugly is from RPMfusion because of
licensing issues.
# dnf search -v plugins-ugly
Have it now, but it did not help.
Any ideas?
Doug Herr wrote:
> Just adding my saved note on how it can be done:
>
> Pull files out of an rpm without installing it:
> mkdir foo ; cp file.rpm foo ; cd foo
> rpm2cpio - < file.rpm | cpio --extract --no-absolute-filenames
> --make-directories
Or simpler, IMO:
Install 'rpmdevtools' and use:
On Mon, Jun 24, 2024, at 11:23 PM, Tim via users wrote:
> On Mon, 2024-06-24 at 19:48 -0700, Mike Wright wrote:
>> I can't dissect a .rpm but I know how to dissect a .deb so I installed
>> totem onto Ubuntu 24.04 (latest release) so I could take it apart.
>
> You can open them in an archive manag
On Mon, 2024-06-24 at 19:48 -0700, Mike Wright wrote:
> I can't dissect a .rpm but I know how to dissect a .deb so I installed
> totem onto Ubuntu 24.04 (latest release) so I could take it apart.
You can open them in an archive manager (treating them the same as zip
files, and various other arch
On 6/24/24 5:58 PM, Michael Hennebry wrote:
On Mon, 24 Jun 2024, Patrick O'Callaghan wrote:
Note that gstreamer1-plugins-ugly is from RPMfusion because of
licensing issues.
Could not find it in rpnfusion-nonfree-* .
Found it in
rpmfusion-free-source
rpmfusion-free-updates-source
rpmfusion-fre
On 6/21/24 07:44, Michael Hennebry wrote:
On Fri, 21 Jun 2024, Michael Hennebry wrote:
Possibly related:
totem does not play movies.
totem complains that it cannot initialize openGL support.
I can't dissect a .rpm but I know how to dissect a .deb so I installed
totem onto Ubuntu 24.04 (lates
On Mon, 24 Jun 2024, Patrick O'Callaghan wrote:
On Sun, 2024-06-23 at 17:54 -0500, Michael Hennebry wrote:
Strange that firefox can play it, but totem cannot.
AFAIK Firefox has its own built-in codecs, while totem uses the
gstreamer library and plugins. Here's what I have:
$ rpm -qa gstrea
On Sun, 2024-06-23 at 17:54 -0500, Michael Hennebry wrote:
> On Fri, 21 Jun 2024, Patrick O'Callaghan wrote:
>
> > On Fri, 2024-06-21 at 09:44 -0500, Michael Hennebry wrote:
> > > On Fri, 21 Jun 2024, Michael Hennebry wrote:
> > >
> > > > Possibly related:
> > > > totem does not play movies.
> >
On Thu, 20 Jun 2024, Michael Hennebry wrote:
On Thu, 20 Jun 2024, Roger Heflin wrote:
You would need to find the log file that starts up Xorg after you login it.
There are a number of things that can be set wrong and/or missing that
will cause Xorg to attempt to start and fail and exit like t
On Fri, 21 Jun 2024, Patrick O'Callaghan wrote:
On Fri, 2024-06-21 at 09:44 -0500, Michael Hennebry wrote:
On Fri, 21 Jun 2024, Michael Hennebry wrote:
Possibly related:
totem does not play movies.
totem complains that it cannot initialize openGL support.
Correction: could not initialise op
On Fri, 2024-06-21 at 09:44 -0500, Michael Hennebry wrote:
> On Fri, 21 Jun 2024, Michael Hennebry wrote:
>
> > Possibly related:
> > totem does not play movies.
> > totem complains that it cannot initialize openGL support.
>
> Correction: could not initialise openGL support
>
> > I've installed
On Fri, 21 Jun 2024, Michael Hennebry wrote:
Possibly related:
totem does not play movies.
totem complains that it cannot initialize openGL support.
Correction: could not initialise openGL support
I've installed pretty much everything I can think of,
including *opengl* , *openGL* and *mesa*
A bit more info:
hennebry@fedora:~$ glxinfo -B
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Mesa Project (0x8086)
Device: i915 (chipset: Q33) (0x29d2)
Version: 24.1.1
Accelerated: yes
Video memory: 38
From /home/hennebry/.local/share/xorg/Xorg.0.log
[ 81949.159] (WW) glamor requires at least 128 instructions (64 reported)
[ 81949.159] (EE) modeset(0): Failed to initialize glamor at ScreenInit() time.
[ 81949.159] (EE)
Fatal server error:
[ 81949.159] (EE) AddScreen/ScreenInit failed for drive
On Fri, 21 Jun 2024, Tim via users wrote:
Tim:
Michael Hennebry wrote:
I could not login.
The screen would blink.
Sometimes I would briefly see a cursor.
I'd be back at the login screen.
[ 40469.778] (EE) Please also check the log file at
"/home/hennebry/.local/share/xorg/Xorg.0.log" for
Tim:
>> In what sense, *exactly*, "does not work"?
Michael Hennebry wrote:
> I could not login.
> The screen would blink.
> Sometimes I would briefly see a cursor.
> I'd be back at the login screen.
Very similar to what happened to me, though could be coincidental.
I'd occasionally get the same
The mail server I use for fedora is not mine and it was down for a bit.
On Fri, 21 Jun 2024, Tim via users wrote:
On Thu, 2024-06-20 at 00:30 -0500, Michael Hennebry wrote:
I just discovered something interesting:
None of the accounts on my machine will login with Xorg.
The option is offered,
On Thu, 2024-06-20 at 00:30 -0500, Michael Hennebry wrote:
> I just discovered something interesting:
> None of the accounts on my machine will login with Xorg.
> The option is offered, but is does not work.
In what sense, *exactly*, "does not work"?
I remember an old X problem where you'd try to
> On 20 Jun 2024, at 16:33, Michael Hennebry
> wrote:
>
> No go on F40.
> I expect I need some incantation involving journalctl .
Are you using wayland perhaps?
So we know the details of your setup what is the output of inxi -Fzxx ?
Barry
--
___
On Thu, 20 Jun 2024, Roger Heflin wrote:
You would need to find the log file that starts up Xorg after you login it.
There are a number of things that can be set wrong and/or missing that
will cause Xorg to attempt to start and fail and exit like this.
F39 puts the log file here on my machine
On Thu, 20 Jun 2024 00:30:31 -0500 (CDT)
Michael Hennebry wrote:
> Not being able to use Xorg is not good news.
Just a data point: I use Xorg exclusively and have no problems
with fedora 40 login. I use sddm as my greeter and changed the sddm.conf
file to say use Xorg, not wayland - don't know if
You would need to find the log file that starts up Xorg after you login it.
There are a number of things that can be set wrong and/or missing that
will cause Xorg to attempt to start and fail and exit like this.
F39 puts the log file here on my machine.
/var/log/Xorg.0.log
On most of my machines
I just discovered something interesting:
None of the accounts on my machine will login with Xorg.
The option is offered, but is does not work.
For F40, I had selected gnome-classic with Xorg.
New accounts defaulted to gnome with Wayland.
When I made a new hennebry account, even with an old home di
On Wed, 19 Jun 2024, Barry wrote:
You could login at a console and eliminate the gui as a problem.
Type alt-ctrl-f3 to get a console.
Thank you for that suggestion.
I could login from a console.
Clearly the problem was not my password.
Auto-relabel did not get me back to the gui,
but just getti
On Jun 19, 2024, at 16:41, Joe Zeff wrote:
>
> On 06/19/2024 02:31 PM, Jonathan Billings wrote:
>> So, if you’ve used a rescue disk to boot into Linux, chroot into your OS’s
>> disk, and run “passwd” to change a password, or otherwise edit /etc/shadow
>> or /etc/passwd (or other files in /etc)
On 19 Jun 2024, at 18:25, Michael Hennebry wrote:I try to login: click on the user and type in my password.F40 just goes back to the select a user screen.You could login at a console and eliminate the gui as a problem.Type alt-ctrl-f3 to get a console.You could use the process to reset a forgotten
On 06/19/2024 02:31 PM, Jonathan Billings wrote:
So, if you’ve used a rescue disk to boot into Linux, chroot into your OS’s
disk, and run “passwd” to change a password, or otherwise edit /etc/shadow or
/etc/passwd (or other files in /etc), you most likely need to fix the selinux
labels of thos
On Jun 19, 2024, at 13:25, Michael Hennebry
wrote:
>
> I recently installed F40 from DVD.
> F40 and I are having a difference of opinion
> regarding what password I gave the initial user.
> F40 is winning.
> I find it hard to believe I typed in the same wrong password twice,
> but it's F40's op
On Wed, 19 Jun 2024 13:15:21 -0500 (CDT)
Michael Hennebry wrote:
> I'll try that.
> Since it has worked for you,
> I infer that you did an su first,
> otherwise I'd expect passwd to ask for a password.
You have to be root to do a chroot, so yep, I'm root
once I get there.
--
_
On Wed, 19 Jun 2024, Tom Horsley wrote:
On Wed, 19 Jun 2024 12:24:48 -0500 (CDT)
Michael Hennebry wrote:
My usual strategy is to boot a live disk
and to edit the passwd and shadow files directly.
My strategy is to boot a live cd, then chroot into the
copy on disk and use the passwd command.
On Wed, 19 Jun 2024 12:24:48 -0500 (CDT)
Michael Hennebry wrote:
> My usual strategy is to boot a live disk
> and to edit the passwd and shadow files directly.
My strategy is to boot a live cd, then chroot into the
copy on disk and use the passwd command. Maybe that
would work better?
--
35 matches
Mail list logo
