Re: clean-up of old kernel fragments.

[home user via users]

On 11/7/24 10:22 PM, Samuel Sieb wrote:

On 11/7/24 4:15 PM, home user via users wrote:

On 11/6/24 10:15 PM, Jeffrey Walton wrote:
[snip]

[snip]

-bash.11[~]:

I still have old kernel files in /boot:

-bash.17[~]: cd /boot
-bash.18[boot]: ls *-6.10.*
config-6.10.12-100.fc39.x86_64 System.map-6.10.12-100.fc39.x86_64
initramfs-6.10.12-100.fc39.x86_64.img  vmlinuz-6.10.12-100.fc39.x86_64
symvers-6.10.12-100.fc39.x86_64.xz


There are no packages involved.  You just have to manually delete the files.  You can 
verify by running "rpm -qf /boot/*" or whatever other directory you're checking 
to see which files aren't owned.



Thank-you Samuel.  That worked.

While doing those "rpm -qf" commands, 2 questions came to mind.
1. Suppose [dir] has sub-directories.  If I do "rpm -qf [dir]/*", will it also 
check [dir]'s sub-directories?
If no, then
2. How do get the sub-directories checked without having to do them manually 
one-by-one?

Comment/suggestion
The output for some of the "rpm -qf" runs showed a lot of output.  It showed both owned 
and unowned files.  It listed sub-directories as though they were files.  It would have been too 
easy to miss that a file is owned, and then do an "rm -rf" on something that should be 
kept.  I found it helpful to add
 | grep " not owned "
or
 | grep -v " not owned "
to get a clearer picture of things, and to give me more confidence that doing "rm 
-rf [dir]" is safe.

I recently started a sys.admin. tips file for myself.  I'm definitely adding the 
"rpm -qf" with the pipe to grep to that tips file.

--
___
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: Remove disk encryption in Maintenance Mode

[Roger Heflin]

I am not sure what version mine last worked on.  I would guess the
default changed on 39 or 40.

What fixed it for me (type plain password from stdin) was adding
--hash ripemd160 (they appear to have changed the default hash, BAD
developer).

Guessing related to this:
https://gitlab.com/cryptsetup/cryptsetup/-/issues/758

And given people could have a script/command to mount like this(and
ask for a password), changing the default is not nice especially since
it will break the password working with no indication of anything
except the password/hash not decrypting the fs.

On Thu, Nov 7, 2024 at 8:35 PM Jeffrey Walton  wrote:
>
> On Thu, Nov 7, 2024 at 8:03 PM Roger Heflin  wrote:
> >
> > The encryption defaults changed sometime recently.
>
> I don't see the change documented at
>  or
> .
>
> That's unfortunate.
>
> > The defaults cryptsetup command I had in a script stopped mount my
> > encrypted filesystem until I  did a bunch of research and found out
> > what parameters needed to be specified to match the prior default.
> >
> > If you want to try what I found out reply and I can boot up the
> > encrypted machine and see what parameters I needed to add.
>
> Jeff
> --
> ___
> 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
-- 
___
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: clean-up of old kernel fragments.

[Jeffrey Walton]

On Fri, Nov 8, 2024 at 8:15 PM home user via users
 wrote:
>
> On 11/8/24 5:18 PM, Samuel Sieb wrote:
> > On 11/8/24 10:15 AM, home user via users wrote:
> >> While doing those "rpm -qf" commands, 2 questions came to mind.
> >> 1. Suppose [dir] has sub-directories.  If I do "rpm -qf [dir]/*", will it 
> >> also check [dir]'s sub-directories?
> >> If no, then
> >> 2. How do get the sub-directories checked without having to do them 
> >> manually one-by-one?
> >
> > find [dir] -type f -print0 | xargs -0 rpm -qf
> >
>
> I cooked up a simple test /lib/modules/ directory with a subdirectory and a 
> few small text files.
> Worked fine.
>
> Tried this on /lib/modules/6.11.5-200.fc40.x86_64/.
> Some files got listed (file names only) a huge number of times (multiple 
> 40-line screens per file).  These are (of course) owned by packages.  I 
> noticed kernel-modules-core-6.11.5-200.fc40.x86_64 to be listed an especially 
> large number of times.
> Why?  Can this repetition be prevented?

If a particular kernel was not properly (or maybe cleanly) removed,
then there will be an artifact in /lib/modules, and the particular
kernel's directory tree will _not_ be empty. A handful of small files
is expected. You know about that bug. But a large number of files with
megabytes of storage is not expected.

In your case -- a richly populated kernel under /lib/modules --
indicates the kernel was not properly (or maybe cleanly) removed. You
should investigate why the dnf remove or rpm erase (or whatever you
ran) did not complete successfully. Or, if the package was forcefully
removed, then just delete the remaining directory tree in
/lib/modules.

Jeff
-- 
___
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: clean-up of old kernel fragments.

[Samuel Sieb]

On 11/8/24 5:14 PM, home user via users wrote:

On 11/8/24 5:18 PM, Samuel Sieb wrote:

On 11/8/24 10:15 AM, home user via users wrote:

While doing those "rpm -qf" commands, 2 questions came to mind.
1. Suppose [dir] has sub-directories.  If I do "rpm -qf [dir]/*", 
will it also check [dir]'s sub-directories?

If no, then
2. How do get the sub-directories checked without having to do them 
manually one-by-one?


find [dir] -type f -print0 | xargs -0 rpm -qf



I cooked up a simple test /lib/modules/ directory with a subdirectory 
and a few small text files.

Worked fine.

Tried this on /lib/modules/6.11.5-200.fc40.x86_64/.
Some files got listed (file names only) a huge number of times (multiple 
40-line screens per file).  These are (of course) owned by packages.  I 
noticed kernel-modules-core-6.11.5-200.fc40.x86_64 to be listed an 
especially large number of times.

Why?  Can this repetition be prevented?


I'm not sure what you mean.  Each file should only get listed once.  If 
you see otherwise, please show what you're seeing.
Most of the files are going to be owned by "kernel-modules-core" because 
that's what's there.  There will likely be a few that are owned by 
kernel module subpackages for less common hardware.


What repetition are you wanting to prevent?

--
___
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: clean-up of old kernel fragments.

[Samuel Sieb]

On 11/8/24 8:46 PM, home user via users wrote:
I thought that in the case of a file that IS owned by a package, rpm -qf 
was displaying the name of the owned file.  So I was expecting a file 
name to appear once, not 2000+ times!


It's now occurring to me that in the case of a file that is owned by a 
package, it's listing the name of the owning package, not the name of 
the owned file.  Am I correct?


That is correct.

And now I see why you're confused.  It doesn't show the filename, only 
the package name, so you'll see an endless list of the package name, 
with possibly only a few filenames mixed in.


--
___
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: clean-up of old kernel fragments.

[home user via users]

On 11/8/24 9:06 PM, Samuel Sieb wrote:

On 11/8/24 6:19 PM, home user via users wrote:

On 11/8/24 6:40 PM, Samuel Sieb wrote:

On 11/8/24 5:14 PM, home user via users wrote:

Tried this on /lib/modules/6.11.5-200.fc40.x86_64/.
Some files got listed (file names only) a huge number of times (multiple 
40-line screens per file).  These are (of course) owned by packages.  I noticed 
kernel-modules-core-6.11.5-200.fc40.x86_64 to be listed an especially large 
number of times.
Why?  Can this repetition be prevented?


I'm not sure what you mean.  Each file should only get listed once. If you see 
otherwise, please show what you're seeing.
Most of the files are going to be owned by "kernel-modules-core" because that's 
what's there.  There will likely be a few that are owned by kernel module subpackages for 
less common hardware.

What repetition are you wanting to prevent?



Doing this:

-bash.3[~]: find /lib/modules/6.11.5-200.fc40.x86_64/ -type f -print0 | xargs -0 
rpm -qf > findout.txt
-bash.4[~]: ls -l findout.txt
-rw-r--r--. 1 root root 179205 Nov  8 19:12 findout.txt
-bash.5[~]:

and then using "view", the file findout.txt is 4437 lines long.  List rules 
forbid attaching something that big.  Shall I send that to you privately?


"wc -l findout.txt" will give you number of lines.

But that's about the expected number of files there.  You're going to get a 
line for each file.  What are you wanting instead?



hmmm...
Maybe some of that snow coming down outside is getting into my brain.
Could it be that I'm misunderstanding the output?

I thought that in the case of a file that IS owned by a package, rpm -qf was 
displaying the name of the owned file.  So I was expecting a file name to 
appear once, not 2000+ times!

It's now occurring to me that in the case of a file that is owned by a package, 
it's listing the name of the owning package, not the name of the owned file.  
Am I correct?

--
___
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: clean-up of old kernel fragments.

[home user via users]

On 11/8/24 6:40 PM, Samuel Sieb wrote:

On 11/8/24 5:14 PM, home user via users wrote:

On 11/8/24 5:18 PM, Samuel Sieb wrote:

On 11/8/24 10:15 AM, home user via users wrote:

While doing those "rpm -qf" commands, 2 questions came to mind.
1. Suppose [dir] has sub-directories.  If I do "rpm -qf [dir]/*", will it also 
check [dir]'s sub-directories?
If no, then
2. How do get the sub-directories checked without having to do them manually 
one-by-one?


find [dir] -type f -print0 | xargs -0 rpm -qf



I cooked up a simple test /lib/modules/ directory with a subdirectory and a few 
small text files.
Worked fine.

Tried this on /lib/modules/6.11.5-200.fc40.x86_64/.
Some files got listed (file names only) a huge number of times (multiple 
40-line screens per file).  These are (of course) owned by packages.  I noticed 
kernel-modules-core-6.11.5-200.fc40.x86_64 to be listed an especially large 
number of times.
Why?  Can this repetition be prevented?


I'm not sure what you mean.  Each file should only get listed once.  If you see 
otherwise, please show what you're seeing.
Most of the files are going to be owned by "kernel-modules-core" because that's 
what's there.  There will likely be a few that are owned by kernel module subpackages for 
less common hardware.

What repetition are you wanting to prevent?



Doing this:

-bash.3[~]: find /lib/modules/6.11.5-200.fc40.x86_64/ -type f -print0 | xargs -0 
rpm -qf > findout.txt
-bash.4[~]: ls -l findout.txt
-rw-r--r--. 1 root root 179205 Nov  8 19:12 findout.txt
-bash.5[~]:

and then using "view", the file findout.txt is 4437 lines long.  List rules 
forbid attaching something that big.  Shall I send that to you privately?

--
___
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: clean-up of old kernel fragments.

[Samuel Sieb]

On 11/8/24 6:19 PM, home user via users wrote:

On 11/8/24 6:40 PM, Samuel Sieb wrote:

On 11/8/24 5:14 PM, home user via users wrote:

Tried this on /lib/modules/6.11.5-200.fc40.x86_64/.
Some files got listed (file names only) a huge number of times 
(multiple 40-line screens per file).  These are (of course) owned by 
packages.  I noticed kernel-modules-core-6.11.5-200.fc40.x86_64 to be 
listed an especially large number of times.

Why?  Can this repetition be prevented?


I'm not sure what you mean.  Each file should only get listed once.  
If you see otherwise, please show what you're seeing.
Most of the files are going to be owned by "kernel-modules-core" 
because that's what's there.  There will likely be a few that are 
owned by kernel module subpackages for less common hardware.


What repetition are you wanting to prevent?



Doing this:

-bash.3[~]: find /lib/modules/6.11.5-200.fc40.x86_64/ -type f -print0 | 
xargs -0 rpm -qf > findout.txt

-bash.4[~]: ls -l findout.txt
-rw-r--r--. 1 root root 179205 Nov  8 19:12 findout.txt
-bash.5[~]:

and then using "view", the file findout.txt is 4437 lines long.  List 
rules forbid attaching something that big.  Shall I send that to you 
privately?


"wc -l findout.txt" will give you number of lines.

But that's about the expected number of files there.  You're going to 
get a line for each file.  What are you wanting instead?


--
___
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: clean-up of old kernel fragments.

[home user via users]

On 11/8/24 6:33 PM, Jeffrey Walton wrote:

On Fri, Nov 8, 2024 at 8:15 PM home user via users
 wrote:


On 11/8/24 5:18 PM, Samuel Sieb wrote:

On 11/8/24 10:15 AM, home user via users wrote:

While doing those "rpm -qf" commands, 2 questions came to mind.
1. Suppose [dir] has sub-directories.  If I do "rpm -qf [dir]/*", will it also 
check [dir]'s sub-directories?
If no, then
2. How do get the sub-directories checked without having to do them manually 
one-by-one?


find [dir] -type f -print0 | xargs -0 rpm -qf



I cooked up a simple test /lib/modules/ directory with a subdirectory and a few 
small text files.
Worked fine.

Tried this on /lib/modules/6.11.5-200.fc40.x86_64/.
Some files got listed (file names only) a huge number of times (multiple 
40-line screens per file).  These are (of course) owned by packages.  I noticed 
kernel-modules-core-6.11.5-200.fc40.x86_64 to be listed an especially large 
number of times.
Why?  Can this repetition be prevented?


If a particular kernel was not properly (or maybe cleanly) removed,
then there will be an artifact in /lib/modules, and the particular
kernel's directory tree will _not_ be empty. A handful of small files
is expected. You know about that bug. But a large number of files with
megabytes of storage is not expected.

In your case -- a richly populated kernel under /lib/modules --
indicates the kernel was not properly (or maybe cleanly) removed. You
should investigate why the dnf remove or rpm erase (or whatever you
ran) did not complete successfully. Or, if the package was forcefully
removed, then just delete the remaining directory tree in
/lib/modules.

Jeff


Weekly patches are done via "dnf --refresh upgrade".
Semi-annual upgrades are done via "dnf system-upgrade download --releasever={number]" 
followed by "dnf system-upgrade reboot".
The clean-up of /boot and /lib/modules was done this morning before my late-this-morning 
post on this thread.  I had to use rm and "rm -rf" to do that.  Both 
directories are now nice and clean:

bash.1[~]: ls /boot
config-6.11.5-200.fc40.x86_64 memtest86+x64.bin
config-6.11.6-200.fc40.x86_64 symvers-6.11.5-200.fc40.x86_64.xz
efi   symvers-6.11.6-200.fc40.x86_64.xz
grub2 System.map-6.11.5-200.fc40.x86_64
initramfs-6.11.5-200.fc40.x86_64.img  System.map-6.11.6-200.fc40.x86_64
initramfs-6.11.6-200.fc40.x86_64.img  vmlinuz-6.11.5-200.fc40.x86_64
loadervmlinuz-6.11.6-200.fc40.x86_64
lost+found
-bash.2[~]: ls /lib/modules
6.11.5-200.fc40.x86_64  6.11.6-200.fc40.x86_64
-bash.3[~]:

--
___
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: Remove disk encryption in Maintenance Mode

[Todd Zullinger]

Roger Heflin wrote:
> I am not sure what version mine last worked on.  I would guess the
> default changed on 39 or 40.
> 
> What fixed it for me (type plain password from stdin) was adding
> --hash ripemd160 (they appear to have changed the default hash, BAD
> developer).
> 
> Guessing related to this:
> https://gitlab.com/cryptsetup/cryptsetup/-/issues/758
> 
> And given people could have a script/command to mount like this(and
> ask for a password), changing the default is not nice especially since
> it will break the password working with no indication of anything
> except the password/hash not decrypting the fs.

This would have been in cryptsetup-2.7.0, so Fedora 40.
Upstream does note this backward incompatible change in the
2.7.0 release notes¹ and it doesn't seem like they made it
just to make it.  Sure, it's annoying when it happens and
catches one of us, but it is a necessary evil sometimes.

Relevant to the initial problem in this thread, does
anything in Fedora use cryptsetup plain mode by default?
Doesn't the installer use LUKS when encrypting a drive
(which isn't affected by this change) and lack support
encrypting /boot or /boot/efi?  I thought that was something
you could do, but you had to work it out on your own?

¹ 
https://gitlab.com/cryptsetup/cryptsetup/-/blob/main/docs/v2.7.0-ReleaseNotes?ref_type=heads#L148-177

-- 
Todd


signature.asc
Description: PGP signature
-- 
___
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: HDR Support in KDE

[Stephen Morris]

On 7/11/24 08:43, Stephen Morris wrote:

On 6/11/24 20:40, Barry Scott wrote:



On 5 Nov 2024, at 22:10, Stephen Morris  
wrote:


In my case I need a BENQ EL2870U driver to get HDR enabled in Windows.


That would indicate they have a non-standard implementation in the 
monitor.
Unless someone adds a way to support that to linux I do not think HDR 
will work.
Thanks Barry, that is what I was afraid of, so the best I can hope for 
is the monitor emulating HDR as it appears to be doing now after I 
changed the terminal settings in its hardware configuration, pressing 
the HDR button on the front of the monitor was not enough to set up 
HDR in its internal settings.
Just as a matter of interest what brand monitor do you use. I've had a 
look at some LG 4K monitors with HDR10 and HDR 400, and it seems that 
with those to get all the features of the monitor available (presumably 
HDR, on screen mouse controlled configuration, etc) you need to install 
windows or mac software, so presumably that is not going to work in 
Linux either?
I tried to find doco on Fedora Hardware Compatibility List for Monitors 
but couldn't find anything.


regards,
Steve


regards,
Steve



Barry







OpenPGP_0x1EBE7C07B0F7242C.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature
-- 
___
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: DNF Needs Restarting Repository Update

[Stephen Morris]

On 8/11/24 09:08, Jeffrey Walton wrote:

The noisy glibc trigger-post-uninstall scriptlet was fixed recently;
see.

Thanks Jeffrey, my assumption was it had been updated.

regards,
Steve




OpenPGP_0x1EBE7C07B0F7242C.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature
-- 
___
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: Systemd-resolved

[Barry]

> On 8 Nov 2024, at 13:19, jarmo  wrote:
> 
> Had to install inxi first :)

Thanks for the info.

Do you see systemd-resolved failing immediately after you first login?
Or does if fail after you have been using the system for a little while?
After it fails do you see any journal logs about the oom killer running?

Barry
-- 
___
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

Weird KDE vs. Chrome App Problem

[Thomas Cameron]

I nuked my Fedora 40 machine, installed Fedora 41. At the same time, I 
switched from Xfce (after using it for over a decade) to KDE. I am 
absolutely adoring the KDE experience, but there is one weird thing that 
I can't figure out. I hope someone can point me in the right direction.


I use a fair number of Chrome applications (PWAs - see 
https://support.google.com/chrome/answer/9658361) for things like Google 
Calendar, Google Chat, Google Messages for Web, and Slack (I know about 
the Slack app for Linux, but I've had wonky results with it, so I prefer 
a PWA).


Now, under Xfce in Fedora 40 and previous versions, I could middle click 
on a PWA and it would lower just fine, just like any other application. 
But under KDE, when I middle click any *non*-PWA app, it lowers as 
expected. If I middle click a PWA, it does nothing. I believe that it's 
because PWAs don't have title bars, and the "middle click to lower" 
action works on title bars.


 So my question is, how do I get a middle click to lower a PWA app in 
KDE? I have not been able to find any articles on how to enable title 
bars in Chrome apps, although I may be searching using the wrong terms. 
Any pointers?

--
personal-signature Thanks!
Thomas-- 
___
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: Systemd-resolved

[jarmo]

Fri, 8 Nov 2024 09:06:46 +
Barry  kirjoitti:

> > On 8 Nov 2024, at 06:02, jarmo  wrote:
> > 
> > Process: 19413 ExecStart=/usr/lib/systemd/systemd-resolved
> > (code=exited, status=1/FAILURE) Main PID: 19413 (code=exited,
> > status=1/FAILURE) Error: 12 (Muistin varaaminen ei onnistu)  
> 
> This is ENOMEM and that implies your do not have enough RAM to run
> Fedora. What is the output of ’inxi -Fzxx`?
> 
> Barry

Should be enough ram

free
   totalusedfree  shared  buff/cache   available
Mem: 7993668 3603712 1372532  755204 4080012 4389956
Swap:7993340   0 7993340

Jarmo
-- 
___
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: Systemd-resolved

[Tim via users]

On Fri, 2024-11-08 at 01:19 -0500, Jeffrey Walton wrote:
> Disabling a service only lasts until the next (re)boot. And it does
> not stop currently executing services, and the service can still be
> started in the current session.

Not quite the full picture, not in general, even if that was a specific
example of some service that will not quite do what you expect. 
Disabling means setting it so it's not started up (by your
preferences).  

Something else could start a disabled service, such as some other
service that wants/needs it.  Rebooting *may* but doesn't necessarily
mean it will.

> If you want to permanently disable the service, you must mask it.

That's certainly true.

Enabled - I want this to be started (usually after booting)
Disabled - I don't want this to be started by default
Masked - I really don't want this to be started, and obey me, dammit!

Stop - stop it now, but do not change the above preferences
Start - start it now, but do not change the above preferences

-- 
 
uname -rsvp
Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 

-- 
___
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: Systemd-resolved

[Barry Scott]

> On 8 Nov 2024, at 09:44, jarmo  wrote:
> 
> Fri, 8 Nov 2024 09:06:46 +
> Barry  kirjoitti:
> 
>>> On 8 Nov 2024, at 06:02, jarmo  wrote:
>>> 
>>> Process: 19413 ExecStart=/usr/lib/systemd/systemd-resolved
>>> (code=exited, status=1/FAILURE) Main PID: 19413 (code=exited,
>>> status=1/FAILURE) Error: 12 (Muistin varaaminen ei onnistu)  
>> 
>> This is ENOMEM and that implies your do not have enough RAM to run
>> Fedora. What is the output of ’inxi -Fzxx`?
>> 
>> Barry
> 
> Should be enough ram
> 
> free
>   totalusedfree  shared  buff/cache   
> available
> Mem: 7993668 3603712 1372532  755204 4080012 
> 4389956
> Swap:7993340   0 7993340


I asked for `inxi -Fzxx` that will provide a lot of info beyond RAM
can you provide that?

FYI I use `free -h` so that the numbers are easier to read.

Barry

> 
> Jarmo
> -- 
> ___
> 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

-- 
___
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: Systemd-resolved

[jarmo]

Fri, 8 Nov 2024 12:58:16 +
Barry Scott  kirjoitti:

>
> I asked for `inxi -Fzxx` that will provide a lot of info beyond RAM
> can you provide that?
> 
> FYI I use `free -h` so that the numbers are easier to read.
> 
> Barry

Had to install inxi first :)
Below is with systemd-resolved

System:
  Kernel: 6.11.6-300.fc41.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.43.1-2.fc41
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.43 wm: xfwm4 dm: LightDM
Distro: Fedora Linux 41 (Xfce)
Machine:
  Type: Desktop System: Hewlett-Packard product: HP Compaq Pro 6300 SFF v: N/A
serial:  Chassis: type: 4 serial: 
  Mobo: Hewlett-Packard model: 339A serial:  part-nu: QV985AV
BIOS: Hewlett-Packard v: K01 v02.90 date: 07/16/2013
Battery:
  Device-1: hidpp_battery_0 model: Logitech M510 serial: 
charge: 55% (should be ignored) status: discharging
CPU:
  Info: quad core model: Intel Core i7-3770K bits: 64 type: MT MCP
arch: Ivy Bridge rev: 9 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 1597 min/max: 1600/3900 cores: 1: 1597 2: 1597 3: 1597
4: 1597 5: 1597 6: 1597 7: 1597 8: 1597 bogomips: 55872
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
  Device-1: Intel IvyBridge GT2 [HD Graphics 4000] vendor: Hewlett-Packard
driver: i915 v: kernel arch: Gen-7 ports: active: VGA-1 empty: DP-1,HDMI-A-1
bus-ID: 00:02.0 chip-ID: 8086:0162
  Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4
compositor: xfwm4 v: 4.18.0 driver: X: loaded: modesetting
alternate: fbdev,vesa dri: crocus gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96
  Monitor-1: VGA-1 model: Philips PHL 273V5 res: 1920x1080 dpi: 82
diag: 686mm (27")
  API: OpenGL v: 4.2 vendor: intel mesa v: 24.2.6 glx-v: 1.4 es-v: 3.0
direct-render: yes renderer: Mesa Intel HD Graphics 4000 (IVB GT2)
device-ID: 8086:0162
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio
vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
chip-ID: 8086:1e20
  Device-2: Texas Instruments PCM2903C Audio CODEC
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
lanes: 1 bus-ID: 1-1.2.4:9 chip-ID: 08bb:29c3
  API: ALSA v: k6.11.6-300.fc41.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.2.6 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin
Network:
  Device-1: Intel 82579LM Gigabit Network vendor: Hewlett-Packard
driver: e1000e v: kernel port: f080 bus-ID: 00:19.0 chip-ID: 8086:1502
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 
Drives:
  Local Storage: total: 920.37 GiB used: 124.66 GiB (13.5%)
  ID-1: /dev/sda vendor: Kingston model: SA400S37240G size: 223.57 GiB
speed: 6.0 Gb/s serial:  temp: 27 C
  ID-2: /dev/sdb vendor: A-Data model: SX900 size: 119.24 GiB
speed: 3.0 Gb/s serial:  temp: 28 C
  ID-3: /dev/sdc vendor: Kingston model: SV300S37A120G size: 111.79 GiB
speed: 3.0 Gb/s serial:  temp: 29 C
  ID-4: /dev/sdd vendor: Seagate model: ST500DM002-1BD142 size: 465.76 GiB
type: USB rev: 3.0 spd: 5 Gb/s lanes: 1 serial: 
Partition:
  ID-1: / size: 198.82 GiB used: 54.37 GiB (27.3%) fs: ext4 dev: /dev/sda2
Swap:
  ID-1: swap-1 type: zram size: 7.62 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 35.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 8 GiB available: 7.62 GiB used: 3.89 GiB (51.0%) igpu: 64 MiB
  Processes: 577 Power: uptime: 22h 49m wakeups: 0 Init: systemd v: 256
target: graphical (5) default: graphical
  Packages: pm: rpm pkgs: N/A note: see --rpm Compilers: gcc: 14.2.1
Shell: Bash v: 5.2.32 running-in: xfce4-terminal inxi: 3.3.36

And next with self configured resolv.conf system-resolved disabled

System:
  Kernel: 6.11.6-300.fc41.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.43.1-2.fc41
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.43 wm: xfwm4 dm: LightDM
Distro: Fedora Linux 41 (Xfce)
Machine:
  Type: Desktop System: Hewlett-Packard product: HP Compaq Pro 6300 SFF v: N/A
serial:  Chassis: type: 4 serial: 
  Mobo: Hewlett-Packard model: 339A serial:  part-nu: QV985AV
BIOS: Hewlett-Packard v: K01 v02.90 date: 07/16/2013
Battery:
  Device-1: hidpp_battery_0 model: Logitech M510 serial: 
charge: 55% (should be ignored) status: discharging
CPU:
  Info: quad core model: Intel Core i7-3770K bits: 64 type: MT MCP
arch: Ivy Bridge rev: 9 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 3852 min/max: 1600/3900 cores: 1: 3852 2: 3852 3: 3852
4: 3852 5: 3852 6: 3852 7: 3852 8: 3852 bogomips: 55872
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
  Device-1: Intel IvyBridge GT2 [HD Graphics 4000] vendor: Hewlett-Packard
driver: i915 v: kernel arch: Gen-7 ports: active: VGA-1 

Re: Systemd-resolved

[Barry]

> On 8 Nov 2024, at 06:02, jarmo  wrote:
> 
> Process: 19413 ExecStart=/usr/lib/systemd/systemd-resolved (code=exited, 
> status=1/FAILURE)
>   Main PID: 19413 (code=exited, status=1/FAILURE)
>  Error: 12 (Muistin varaaminen ei onnistu)

This is ENOMEM and that implies your do not have enough RAM to run Fedora.
What is the output of ’inxi -Fzxx`?

Barry


-- 
___
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: Weird KDE vs. Chrome App Problem

[Patrick O'Callaghan]

On Fri, 2024-11-08 at 17:19 -0600, Thomas Cameron wrote:
>   So my question is, how do I get a middle click to lower a PWA app in 
> KDE? I have not been able to find any articles on how to enable title 
> bars in Chrome apps, although I may be searching using the wrong terms. 
> Any pointers?

Here's a pointer: try asking on the Fedora KDE list:

k...@lists.fedoraproject.org

poc
-- 
___
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: clean-up of old kernel fragments.

[Samuel Sieb]

On 11/8/24 10:15 AM, home user via users wrote:

While doing those "rpm -qf" commands, 2 questions came to mind.
1. Suppose [dir] has sub-directories.  If I do "rpm -qf [dir]/*", will 
it also check [dir]'s sub-directories?

If no, then
2. How do get the sub-directories checked without having to do them 
manually one-by-one?


find [dir] -type f -print0 | xargs -0 rpm -qf

--
___
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: clean-up of old kernel fragments.

[home user via users]

On 11/8/24 5:18 PM, Samuel Sieb wrote:

On 11/8/24 10:15 AM, home user via users wrote:

While doing those "rpm -qf" commands, 2 questions came to mind.
1. Suppose [dir] has sub-directories.  If I do "rpm -qf [dir]/*", will it also 
check [dir]'s sub-directories?
If no, then
2. How do get the sub-directories checked without having to do them manually 
one-by-one?


find [dir] -type f -print0 | xargs -0 rpm -qf



I cooked up a simple test /lib/modules/ directory with a subdirectory and a few 
small text files.
Worked fine.

Tried this on /lib/modules/6.11.5-200.fc40.x86_64/.
Some files got listed (file names only) a huge number of times (multiple 
40-line screens per file).  These are (of course) owned by packages.  I noticed 
kernel-modules-core-6.11.5-200.fc40.x86_64 to be listed an especially large 
number of times.
Why?  Can this repetition be prevented?

--
___
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