Re: urgent major problem after f39 to f40 upgrade.

2024-10-14 Thread Jonathan Billings
On Oct 14, 2024, at 18:01, Samuel Sieb  wrote:
> 
> There are some serious issues in that list.  Removing "passwd"??  But also, 
> look how many packages get removed by some of those.

The “passwd” package is retired as part of the libuser deprecation. 

https://fedoraproject.org/wiki/Changes/LibuserDeprecation

Don’t worry, the “passwd” command is still around. It’s part of the 
still-maintained “shadow-utils” package. 

-- 
Jonathan Billings-- 
___
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: urgent major problem after f39 to f40 upgrade.

2024-10-14 Thread Samuel Sieb

On 10/14/24 2:14 PM, home user via users wrote:

On 10/12/24 10:06 PM, home user via users wrote:
[snip]


I hope to try some of the post-upgrade tasks Monday.  But I'll skip 
some altogether.


The RPM database rebuild failed to delete 3 files; I don't know why.  
They are, all in /usr/lib/sysimage/rpmold.145598/, rpm.sqlite, 
rpmdb.sqlite-shm, and rpmdb.sqlite-wal.  Is this a problem or something 
I can ignore?


I expect you can ignore those.  Looks like a backup of old files or part 
of a data file conversion.


I do wonder what (if anything) I did wrong last Thursday that caused all 
this trouble, so I can avoid it in the future.


The symptoms suggest a crash before the update was finished.

--
___
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: urgent major problem after f39 to f40 upgrade.

2024-10-14 Thread home user via users

On 10/10/24 2:02 PM, home user via users wrote:

(I'm doing this from a windows-7 box)

This morning, I did my weekly patches for my f-39 stand-alone workstation.  No 
problems.

Then I did the upgrade to f-40.  I did not sit there and watch it. During the automatic 
reboot, it booted using the nouveau driver rather than the kmod one from rpm fusion 
non-free.  During the post-upgrade task "remove-retired-packages", the 
workstation apparently crashed. Upon rebooting, it came up in console(?) mode; I could 
not get into graphics mode.

I shutdown again, and tried to boot into f-39.  But it came up f-40, console 
mode.

I  have neither "live" media nor installation media; last time I tried them, 
they didn't work.  F-40 console mode and window-7 are all I have to work with.

How do I get this workstation working properly in Fedora?


I went to the github site for remove-retires-packages, and opened an issue 
suggesting that the tool log to a log file, and that the tool's man page report 
where the logs are.  The tool owner replied that the tool logs to dnf logs, and 
suggested two commands to get some relevant information.  He agreed that the 
man page needed the update.

The first command that the tool owner suggested is "dnf history list".  I did that and redirected 
output to the text file "dnfhist.txt".  It's attached.  From that, I concluded that the tool most 
likely hung/crashed while trying to remove "libgweather4".  (Notice how long that took.)  Question: 
Does anything in that list of deleted packages look suspicious or wrong?

The second command that the tool owner suggested is "dnf history info [ID]", where ID is from the output of 
"dnf history list".  I did that for "libgweather4" and redirected output to the text file 
"info1665.txt".  It's attached.  Does anything in there look suspicious or wrong?

I can't rule out the possibility that the removal that crashed/hung came between 
"libgweather" and "libkworkspace5", and the hang/crash occurred before the 
removal could be logged.
ID | Command line  | 
Date and time| Action(s)  | Altered

  1684 | remove zlib-devel | 
2024-10-10 13:14 | Removed|   41 EE
  1683 | remove wget   | 
2024-10-10 13:12 | Removed|   10 EE
  1682 | remove tint2  | 
2024-10-10 13:11 | Removed|1   
  1681 | remove rsyslog-logrotate  | 
2024-10-10 13:11 | Removed|1   
  1680 | remove rpmautospec-rpm-macros | 
2024-10-10 13:10 | Removed|   56 EE
  1679 | remove qtsoap | 
2024-10-10 13:10 | Removed|1   
  1678 | remove qaccessibilityclient   | 
2024-10-10 13:10 | Removed|5 EE
  1677 | remove python3-typed_ast  | 
2024-10-10 13:10 | Removed|1   
  1676 | remove python3-sphinxcontrib-jsmath   | 
2024-10-10 13:09 | Removed|1   
  1675 | remove python3-sphinxcontrib-applehelp| 
2024-10-10 13:09 | Removed|  115 EE
  1674 | remove python3-gobject-base-noarch| 
2024-10-10 13:06 | Removed|  156 EE
  1673 | remove plexus-containers-container-default| 
2024-10-10 13:05 | Removed|2 EE
  1672 | remove pinentry-gtk   | 
2024-10-10 13:05 | Removed|1 EE
  1671 | remove perl-Math-BigRat   | 
2024-10-10 13:04 | Removed|  334 EE
  1670 | remove pcmciautils| 
2024-10-10 13:04 | Removed|1   
  1669 | remove passwd | 
2024-10-10 13:03 | Removed|   78 EE
  1668 | remove network-scripts-ppp| 
2024-10-10 13:02 | Removed|1 EE
  1667 | remove mailx  | 
2024-10-10 13:02 | Removed|1 EE
  1666 | remove libkworkspace5 | 
2024-10-10 13:01 | Removed|   12 E<
  1665 | remove libgweather4   | 
2024-10-10 12:52 | Removed|   38 >#
  1664 | remove libdmapsharing | 
2024-10-10 12:51 | Removed|1   
  1663 | remove ksysguardd | 
2024-10-10 12:51 | Removed|1   
  1662 | remove ksysguard 

Re: HDR Support in KDE

2024-10-14 Thread Barry


> On 14 Oct 2024, at 22:21, Stephen Morris  wrote:
> 
> Thanks Barry. I issued the kscreen-doctor -o command and the HDR line in the 
> output specifies "Incapable". Why is this the case when a boot into Windows 
> activates HDR as specified in the Windows settings, and with "Auto HDR" set 
> when I go into games that support HDR I get a message that because of "Auto 
> HDR" the game is activating HDR.

Now we know why you see no hdr enable button.

I would suspect an issue with the monitor firmware as one possible cause.

One thing worth doing is to power off, not stand by, the computer and monitor.
Then power up and boot into fedora. Do not boot windows.
Does hdr work?

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: urgent major problem after f39 to f40 upgrade.

2024-10-14 Thread home user via users

On 10/14/24 4:00 PM, Samuel Sieb wrote:

On 10/14/24 2:43 PM, home user via users wrote:

On 10/10/24 2:02 PM, home user via users wrote:



The first command that the tool owner suggested is "dnf history list". I did that and redirected 
output to the text file "dnfhist.txt".  It's attached.  From that, I concluded that the tool most 
likely hung/crashed while trying to remove "libgweather4".  (Notice how long that took.) Question: 
Does anything in that list of deleted packages look suspicious or wrong?


There are some serious issues in that list.  Removing "passwd"??  But also, 
look how many packages get removed by some of those.


I did notice those things!  But I don't know if they actually were retired or 
something went wrong.  So I posted the data and question.


The second command that the tool owner suggested is "dnf history info [ID]", where ID is from the output of 
"dnf history list".  I did that for "libgweather4" and redirected output to the text file 
"info1665.txt".  It's attached.  Does anything in there look suspicious or wrong?


Very much.  It's removing most of Gnome, including gdm.  And they are F39 
packages.

What you need to look at is the info for the system-upgrade at 1651 to maybe 
see what went wrong or at least see where it stopped.



The resulting file is almost 1 megabytes in size, almost 10,000 lines long.  I 
don't think I can attach that to a post to this list.  I can send the output 
file to any list member that requests it.

Using vim and setting ignorecase, and searching for "error" and "warning", and 
manually visually scanning through, I did not see any errors or warnings in the update phase of the 
process, but it's certainly easy to miss something.  I saw a vast number of warnings and errors in 
the clean-up phase.  It did look like the process completed.
--
___
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: urgent major problem after f39 to f40 upgrade.

2024-10-14 Thread home user via users

On 10/14/24 5:26 PM, Jonathan Billings wrote:

On Oct 14, 2024, at 18:01, Samuel Sieb  wrote:


There are some serious issues in that list.  Removing "passwd"??  But also, 
look how many packages get removed by some of those.


The “passwd” package is retired as part of the libuser deprecation.

https://fedoraproject.org/wiki/Changes/LibuserDeprecation

Don’t worry, the “passwd” command is still around. It’s part of the 
still-maintained “shadow-utils” package.




Which is why I'm checking with this 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: HDR Support in KDE

2024-10-14 Thread Stephen Morris via users

On 14/10/24 19:53, Barry Scott wrote:



On 14 Oct 2024, at 09:27, Stephen Morris via users 
 wrote:


I did a search for HDR/hdr in "System Settings" under Ubuntu which 
pointed my at the Display Configuration but there isn't any settings 
for HDR on that page.


What I see is a search for "hdr" takes me to Display & Monitor/Display 
Configuration.
On that page I see "High Dynamic Range: [x] Enable HDR". It is line 
under "Colour Profile".


You can use the "kscreen-doctor -o" terminal command that will report 
an HDR line.
It will be "incapable" is HDR is not possible and "Disabled" is you 
can turn it on.
Thanks Barry. I issued the kscreen-doctor -o command and the HDR line in 
the output specifies "Incapable". Why is this the case when a boot into 
Windows activates HDR as specified in the Windows settings, and with 
"Auto HDR" set when I go into games that support HDR I get a message 
that because of "Auto HDR" the game is activating HDR.
What is happening under linux that is not activating HDR, having said 
this though I have seen those settings in the Display Configuration in 
the past (possibly in F39) so I'm not sure why they aren't there now?
I tried pressing the HDR button on my monitor which turned off HDR and 
B.I, and when I pressed it to turn the two of them back on I got a 
display message that HDR was being emulated and the HDR settings still 
did not appear in the Display Configuration. Kscreen-doctor is still 
saying HDR is incapable after doing this.
My monitor is a BENQ2870U which is being shown in Display Configuration. 
There is also an Overscan percentage line under the Refresh Rate line 
which I've never seen before.

Just for reference, below is the output from kscreen-doctor -o.
screen-doctor -o
Output: 1 HDMI-A-1
enabled
connected
priority 1
HDMI
Modes:  1:3840x2160@60*!  2:3840x2160@60  3:3840x2160@60  4:3840x2160@50 
 5:3840x2160@30  6:3840x2160@30  7:3840x2160@25  8:3840x2160@24 
 9:3840x2160@24  10:3840x2160@24  11:2560x1440@60  12:1920x1080@60 
 13:1920x1080@60  14:1920x1080@60  15
:1920x1080@50  16:1920x1080@30  17:1920x1080@30  18:1920x1080@25 
 19:1920x1080@24  20:1920x1080@24  21:1600x1200@60  22:1680x1050@60 
 23:1600x900@60  24:1280x1024@75  25:1280x1024@60  26:1280x800@60 
 27:1152x864@75  28:1280x720@60  29:1280x720@60  3
0:1280x720@50  31:1024x768@75  32:1024x768@60  33:1440x480@60 
 34:1440x480@60  35:832x624@75  36:800x600@75  37:800x600@60 
 38:720x576@50  39:720x480@60  40:720x480@60  41:640x480@75 
 42:640x480@60  43:640x480@60  44:720x400@70  45:1600x1200@60  46:
1280x1024@60  47:1024x768@60  48:2560x1600@60  49:1920x1200@60 
 50:1280x800@60  51:3840x2160@60  52:3200x1800@60  53:2880x1620@60 
 54:2560x1440@60  55:1920x1080@60  56:1600x900@60  57:1368x768@60 
 58:1280x720@60

Geometry: 0,0 2560x1440
Scale: 1.5
Rotation: 1
Overscan: 0
Vrr: incapable
RgbRange: unknown
HDR: incapable
Wide Color Gamut: incapable
ICC profile: /usr/share/color/icc/colord/AdobeRGB1998.icc
Color profile source: ICC
Brightness control: supported, set to 100%



regards,
Steve



Barry





OpenPGP_0x594338B1DE179AB2.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


Prompt for Sudo Credentials for Volume Mount at KDE Startup

2024-10-14 Thread Stephen Morris via users

Hi,
    For some reason when I start KDE I am being prompted for 
credentials to mount /dev/sdc7, but there is no entry in /etc/fstab for 
the UUID of that volume. Where is the prompt coming from? I think 
/dev/sdc7 is my Ubuntu boot partition.

    Below is my /etc/fstab:

UUID=b1b1448c-3e41-47a6-a347-266bf2aa54a7 /   btrfs 
  defaults    1 1
UUID=0926d3a0-7d16-4e89-8cda-9fc5db01b895 /boot   ext4 
   defaults    1 2
UUID=8D36-9D75    /boot/efi   vfat 
   umask=0077,shortname=winnt  1 2
UUID=041814D24615828F /mnt/winc 
  ntfs-3g users,rw    1 0
192.168.1.12:/mnt/HD/HD_a2    /mnt/nfs    nfs 
users,rw,_netdev    1 0
//192.168.1.12/Volume_1   /mnt/cifs   cifs 
   username=,password=,vers=1.0,rw  1 0
UUID=885A21AF5A219AC8 /mnt/wind 
  ntfs-3g users,rw    1 0
UUID=52F237FCF237E2C1 /mnt/wine 
  ntfs-3g users,rw    1 0
#UUID=885A21AF5A219AC8 /mnt/recover 
   ntfs-3g rw    0 0


    Below is my /dev/disk/by-uuid configuration showing the UUID's of 
all devices.


$ ll /dev/disk/by-uuid
total 0
lrwxrwxrwx. 1 root root 10 Oct 15 07:46 041814D24615828F-> ../../sdc4
lrwxrwxrwx. 1 root root 10 Oct 15 07:46 
0926d3a0-7d16-4e89-8cda-9fc5db01b895-> ../../sdc6

lrwxrwxrwx. 1 root root 10 Oct 15 07:46 0CDE882F4ED4969F-> ../../sdc1
lrwxrwxrwx. 1 root root 10 Oct 15 07:46 52F237FCF237E2C1-> ../../sdb1
lrwxrwxrwx. 1 root root 10 Oct 15 07:46 885A21AF5A219AC8-> ../../sda1
lrwxrwxrwx. 1 root root 10 Oct 15 07:46 8D36-9D75-> ../../sdc2
lrwxrwxrwx. 1 root root 10 Oct 15 07:46 
b1b1448c-3e41-47a6-a347-266bf2aa54a7-> ../../sdd1
lrwxrwxrwx. 1 root root 10 Oct 15 07:46 
be8eb9ac-31b9-4493-b6e0-4a69f119fcd6-> ../../sde1
lrwxrwxrwx. 1 root root 10 Oct 15 07:46 
c88248f9-3684-4701-b684-d6e99139c13c-> ../../sdc7

lrwxrwxrwx. 1 root root 10 Oct 15 07:46 E4508D58508D327A-> ../../sdc5

regards,
Steve


OpenPGP_0x594338B1DE179AB2.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: urgent major problem after f39 to f40 upgrade.

2024-10-14 Thread Samuel Sieb

On 10/14/24 8:36 PM, Samuel Sieb wrote:

On 10/14/24 4:36 PM, home user via users wrote:

On 10/14/24 4:00 PM, Samuel Sieb wrote:

On 10/14/24 2:43 PM, home user via users wrote:

On 10/10/24 2:02 PM, home user via users wrote:


The first command that the tool owner suggested is "dnf history 
list". I did that and redirected output to the text file 
"dnfhist.txt".  It's attached.  From that, I concluded that the tool 
most likely hung/crashed while trying to remove "libgweather4". 
(Notice how long that took.) Question: Does anything in that list of 
deleted packages look suspicious or wrong?


There are some serious issues in that list.  Removing "passwd"??  But 
also, look how many packages get removed by some of those.


I did notice those things!  But I don't know if they actually were 
retired or something went wrong.  So I posted the data and question.


The second command that the tool owner suggested is "dnf history 
info [ID]", where ID is from the output of "dnf history list".  I 
did that for "libgweather4" and redirected output to the text file 
"info1665.txt".  It's attached.  Does anything in there look 
suspicious or wrong?


Very much.  It's removing most of Gnome, including gdm.  And they are 
F39 packages.


What you need to look at is the info for the system-upgrade at 1651 
to maybe see what went wrong or at least see where it stopped.




The resulting file is almost 1 megabytes in size, almost 10,000 lines 
long.  I don't think I can attach that to a post to this list.  I can 
send the output file to any list member that requests it.


Using vim and setting ignorecase, and searching for "error" and 
"warning", and manually visually scanning through, I did not see any 
errors or warnings in the update phase of the process, but it's 
certainly easy to miss something.  I saw a vast number of warnings and 
errors in the clean-up phase.  It did look like the process completed.


It clearly didn't complete because you had at least gdm and the various 
-release packages from F39.  You can email me the file if you want.


There's no indication in that info that it failed, so I have no idea 
what could have happened.  The gweather removal did fail, but that was 
also removing packages that should not have been there.


See if "dnf system-upgrade log" will list any logs.  If it does, then 
"dnf system-upgrade log " will show you the journal from that 
run.  See if there is anything interesting in 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: urgent major problem after f39 to f40 upgrade.

2024-10-14 Thread home user via users

On 10/12/24 10:06 PM, home user via users wrote:
[snip]


I hope to try some of the post-upgrade tasks Monday.  But I'll skip some 
altogether.



This morning, I did many of the parts of this.

Of course, I skipped the remove-retired-packages.  I remain very suspicious of 
it and uncomfortable with it.  I did open an issue on it in its github site.  
We'll see what comes of that.

The old symlink clean-up sure found a lot of dangling symlinks.  But I saw no 
indication of errors.

The RPM database rebuild failed to delete 3 files; I don't know why.  They are, 
all in /usr/lib/sysimage/rpmold.145598/, rpm.sqlite, rpmdb.sqlite-shm, and 
rpmdb.sqlite-wal.  Is this a problem or something I can ignore?

The relabelling of files with the latest SELinux policy seemed to take an 
unusually short amount of time.  But I've seen no problems since, so I'm 
assuming it functioned correctly.

I do wonder what (if anything) I did wrong last Thursday that caused all this 
trouble, so I can avoid it in the future.

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

2024-10-14 Thread Barry


> On 14 Oct 2024, at 23:01, Stephen Morris  wrote:
> 
> I'll need to see if I can get KDE with Xorg working again too, to see if that 
> makes a difference.

That is unlikely. I expect the issue is between the monitor and the kernel.
Does Xorg even have hdr support?

I am running out of knowledge. This needs to be raised with kde or kernel 
people next.

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: HDR Support in KDE

2024-10-14 Thread Barry


> On 14 Oct 2024, at 23:01, Stephen Morris via users 
>  wrote:
> 
> power off my computer and monitor every night and every morning,

Just to check you unplug from the mains?
If you leave the computer and monitor plugged it will not fully reset.

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: urgent major problem after f39 to f40 upgrade.

2024-10-14 Thread Samuel Sieb

On 10/14/24 2:43 PM, home user via users wrote:

On 10/10/24 2:02 PM, home user via users wrote:

(I'm doing this from a windows-7 box)

This morning, I did my weekly patches for my f-39 stand-alone 
workstation.  No problems.


Then I did the upgrade to f-40.  I did not sit there and watch it. 
During the automatic reboot, it booted using the nouveau driver rather 
than the kmod one from rpm fusion non-free.  During the post-upgrade 
task "remove-retired-packages", the workstation apparently crashed. 
Upon rebooting, it came up in console(?) mode; I could not get into 
graphics mode.


I shutdown again, and tried to boot into f-39.  But it came up f-40, 
console mode.


I  have neither "live" media nor installation media; last time I tried 
them, they didn't work.  F-40 console mode and window-7 are all I have 
to work with.


How do I get this workstation working properly in Fedora?


I went to the github site for remove-retires-packages, and opened an 
issue suggesting that the tool log to a log file, and that the tool's 
man page report where the logs are.  The tool owner replied that the 
tool logs to dnf logs, and suggested two commands to get some relevant 
information.  He agreed that the man page needed the update.


The first command that the tool owner suggested is "dnf history list".  
I did that and redirected output to the text file "dnfhist.txt".  It's 
attached.  From that, I concluded that the tool most likely hung/crashed 
while trying to remove "libgweather4".  (Notice how long that took.)  
Question: Does anything in that list of deleted packages look suspicious 
or wrong?


There are some serious issues in that list.  Removing "passwd"??  But 
also, look how many packages get removed by some of those.


The second command that the tool owner suggested is "dnf history info 
[ID]", where ID is from the output of "dnf history list".  I did that 
for "libgweather4" and redirected output to the text file 
"info1665.txt".  It's attached.  Does anything in there look suspicious 
or wrong?


Very much.  It's removing most of Gnome, including gdm.  And they are 
F39 packages.


What you need to look at is the info for the system-upgrade at 1651 to 
maybe see what went wrong or at least see where it stopped.


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

2024-10-14 Thread Stephen Morris via users

On 15/10/24 08:42, Barry wrote:



On 14 Oct 2024, at 22:21, Stephen Morris  wrote:

Thanks Barry. I issued the kscreen-doctor -o command and the HDR line in the output specifies 
"Incapable". Why is this the case when a boot into Windows activates HDR as specified in the 
Windows settings, and with "Auto HDR" set when I go into games that support HDR I get a message 
that because of "Auto HDR" the game is activating HDR.

Now we know why you see no hdr enable button.

I would suspect an issue with the monitor firmware as one possible cause.

One thing worth doing is to power off, not stand by, the computer and monitor.
Then power up and boot into fedora. Do not boot windows.
Does hdr work?
I power off my computer and monitor every night and every morning, but 
that has no effect on HDR being available. I'll need to check again but 
I don't remember seeing those options in Ubuntu with KDE either.
I'll need to see if I can get KDE with Xorg working again too, to see if 
that makes a difference.


regards,
Steve


Barry






OpenPGP_0x594338B1DE179AB2.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


Strange DNF Repository

2024-10-14 Thread Stephen Morris via users

Hi,
    Can someone tell me what DNF repository _dnf_local is, and why an 
install of kmod-nvidia-6.10.12-200.fc40.x86_64 after it was removed by 
DNF would want to come from there and fail because it wasn't signed?
    Also after a "sudo dnf clean all" was issued a dnf install of the 
above kmod-nvidia package which also wanted to install it from 
_dnf_local rather than the rpmfusion repository successfully installed 
the package?


regards,
Steve



OpenPGP_0x594338B1DE179AB2.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: Strange DNF Repository

2024-10-14 Thread Samuel Sieb

On 10/14/24 3:09 PM, Stephen Morris via users wrote:
     Can someone tell me what DNF repository _dnf_local is, and why an 
install of kmod-nvidia-6.10.12-200.fc40.x86_64 after it was removed by 
DNF would want to come from there and fail because it wasn't signed?
     Also after a "sudo dnf clean all" was issued a dnf install of the 
above kmod-nvidia package which also wanted to install it from 
_dnf_local rather than the rpmfusion repository successfully installed 
the package?


Usually you would use the akmod package to compile and build the kmod 
package locally.  Maybe you did that before and there are still some 
remnants of that?


--
___
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: urgent major problem after f39 to f40 upgrade.

2024-10-14 Thread Samuel Sieb

On 10/14/24 4:26 PM, Jonathan Billings wrote:

On Oct 14, 2024, at 18:01, Samuel Sieb  wrote:


There are some serious issues in that list.  Removing "passwd"??  But 
also, look how many packages get removed by some of those.


The “passwd” package is retired as part of the libuser deprecation.

https://fedoraproject.org/wiki/Changes/LibuserDeprecation fedoraproject.org/wiki/Changes/LibuserDeprecation>


Don’t worry, the “passwd” command is still around. It’s part of the 
still-maintained “shadow-utils” package.


Ok, that's good to know.  But if you look at the history, removing that 
took out another 77 packages as well, so something wasn't right.


--
___
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: urgent major problem after f39 to f40 upgrade.

2024-10-14 Thread Samuel Sieb

On 10/14/24 4:36 PM, home user via users wrote:

On 10/14/24 4:00 PM, Samuel Sieb wrote:

On 10/14/24 2:43 PM, home user via users wrote:

On 10/10/24 2:02 PM, home user via users wrote:


The first command that the tool owner suggested is "dnf history 
list". I did that and redirected output to the text file 
"dnfhist.txt".  It's attached.  From that, I concluded that the tool 
most likely hung/crashed while trying to remove "libgweather4".  
(Notice how long that took.) Question: Does anything in that list of 
deleted packages look suspicious or wrong?


There are some serious issues in that list.  Removing "passwd"??  But 
also, look how many packages get removed by some of those.


I did notice those things!  But I don't know if they actually were 
retired or something went wrong.  So I posted the data and question.


The second command that the tool owner suggested is "dnf history info 
[ID]", where ID is from the output of "dnf history list".  I did that 
for "libgweather4" and redirected output to the text file 
"info1665.txt".  It's attached.  Does anything in there look 
suspicious or wrong?


Very much.  It's removing most of Gnome, including gdm.  And they are 
F39 packages.


What you need to look at is the info for the system-upgrade at 1651 to 
maybe see what went wrong or at least see where it stopped.




The resulting file is almost 1 megabytes in size, almost 10,000 lines 
long.  I don't think I can attach that to a post to this list.  I can 
send the output file to any list member that requests it.


Using vim and setting ignorecase, and searching for "error" and 
"warning", and manually visually scanning through, I did not see any 
errors or warnings in the update phase of the process, but it's 
certainly easy to miss something.  I saw a vast number of warnings and 
errors in the clean-up phase.  It did look like the process completed.


It clearly didn't complete because you had at least gdm and the various 
-release packages from F39.  You can email me the file if you want.


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

2024-10-14 Thread Stephen Morris via users

On 14/10/24 09:29, Barry wrote:



On 13 Oct 2024, at 01:37, Stephen Morris via users 
 wrote:

HI,
 With the last system update I put on (yesterday) I have been upgraded to 
Plasma 6.2. One of the enhancements in this version was more support for HDR, 
but even though my monitor is HDR there are no HDR settings in KDE System 
Settings. Under Gnome with Wayland there are HDR settings. Is anyone else 
seeing the same issue?

I have dell monitor with hdr and plasma 6.2 allowed me to turn on hdr support.
I think i searched for “hdr” is system settings to find the right place.
If you do not find it reply here and I will give exact location I found.
Also you should check that your monitor’s settings have hdr mode enabled.
Thanks Barry, HDR is turned on in my monitor as it is active under 
Windows. I'm replying to this mail under Ubuntu as the last couple of 
system updates have destroyed the ability for KDE and Gnome to start.


regards,
Steve



Barry


regards,
Steve


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




OpenPGP_0x594338B1DE179AB2.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: Strange behavior with F40 server iso and VM

2024-10-14 Thread Barry
S

> On 14 Oct 2024, at 04:30, Tim via users  wrote:
> 
> I'm wondering what *less* user data separation means?

I assume it means using btrfs to put / and /home into the same file system.
For a server the data that the server handles is in a separate file system.

The trade offs for a server and a desktop and different.

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: Log your reports for F41 Upgrade Test Days

2024-10-14 Thread Luna Jernberg
Decided to jump in and test today

Den mån 14 okt. 2024 kl 04:30 skrev Sumantro Mukherjee :

> Hey All,
>
> A gentle reminder, today will be the last day to record your upgrade
> experiences in [0]
> This will help us not only know the problems you faced (if at all any) and
> then resolve
> them (if they end up blocking).
>
> [0] http://fedoraproject.org/wiki/Test_Day:2024-10-11_F41_Upgrade_Test_Day
>
>
> --
> //sumantro
> Fedora QE
> TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
> --
> ___
> 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: HDR Support in KDE

2024-10-14 Thread Barry Scott


> On 14 Oct 2024, at 09:27, Stephen Morris via users 
>  wrote:
> 
> I did a search for HDR/hdr in "System Settings" under Ubuntu which pointed my 
> at the Display Configuration but there isn't any settings for HDR on that 
> page.

What I see is a search for "hdr" takes me to Display & Monitor/Display 
Configuration. 
On that page I see "High Dynamic Range: [x] Enable HDR". It is line under 
"Colour Profile".

You can use the "kscreen-doctor -o" terminal command that will report an HDR 
line.
It will be "incapable" is HDR is not possible and "Disabled" is you can turn it 
on.

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: KDE and Gnome Can't Start From SDDM After the Last Couple of System Updates

2024-10-14 Thread Barry Scott


> On 14 Oct 2024, at 09:21, Stephen Morris via users 
>  wrote:
> 
> Hi,
> A couple of updates ago a system update installed Plasma 6.2, which 
> booted fine after the update. I went into "System Settings" and went through 
> all the options, I did change the display profile to one of the ICC profiles 
> shown under the Colour options (sRGB).
> On the next reboot SDDM could not start KDE Xorg or Wayland, they both 
> went to a black screen and the monitor went into sleep mode notifying of a 
> loss of signal.
> So I tried starting Gnome which booted fine. Dnf said there were a lot of 
> updates ready to go on so I put them on. On the next reboot Gnome would no 
> longer start with Xorg or Wayland, exhibiting the same situations as KDE.
> To try and investigate the issue, I booted into SDDM and used ctrl-alt-F2 
> to switch to a terminal login, but that did the same thing, it displayed a 
> black screen and the monitor went into sleep mode with a loss of signal 
> notification.
> I'm currently sending this mail from Thunderbird under UBUNTU using the 
> thunderbird configuration from the Fedora implementation.
> Can anyone give me any hints on what I can do to try to get around these 
> situations?

We need information on what is happening.

What is the output of these commands?
inxi -Fzxx
sudo journalctl -u sddm

Barry

> 
> regards,
> Steve
> 
> -- 
> ___
> 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: HDR Support in KDE

2024-10-14 Thread Stephen Morris via users

On 14/10/24 19:11, Stephen Morris via users wrote:

On 14/10/24 09:29, Barry wrote:


On 13 Oct 2024, at 01:37, Stephen Morris via users 
 wrote:


HI,
 With the last system update I put on (yesterday) I have been 
upgraded to Plasma 6.2. One of the enhancements in this version was 
more support for HDR, but even though my monitor is HDR there are no 
HDR settings in KDE System Settings. Under Gnome with Wayland there 
are HDR settings. Is anyone else seeing the same issue?
I have dell monitor with hdr and plasma 6.2 allowed me to turn on hdr 
support.

I think i searched for “hdr” is system settings to find the right place.
If you do not find it reply here and I will give exact location I found.
Also you should check that your monitor’s settings have hdr mode 
enabled.
Thanks Barry, HDR is turned on in my monitor as it is active under 
Windows. I'm replying to this mail under Ubuntu as the last couple of 
system updates have destroyed the ability for KDE and Gnome to start.
I did a search for HDR/hdr in "System Settings" under Ubuntu which 
pointed my at the Display Configuration but there isn't any settings for 
HDR on that page.


regards,
Steve



regards,
Steve



Barry


regards,
Steve


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







OpenPGP_0x594338B1DE179AB2.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


KDE and Gnome Can't Start From SDDM After the Last Couple of System Updates

2024-10-14 Thread Stephen Morris via users

Hi,
    A couple of updates ago a system update installed Plasma 6.2, which 
booted fine after the update. I went into "System Settings" and went 
through all the options, I did change the display profile to one of the 
ICC profiles shown under the Colour options (sRGB).
    On the next reboot SDDM could not start KDE Xorg or Wayland, they 
both went to a black screen and the monitor went into sleep mode 
notifying of a loss of signal.
    So I tried starting Gnome which booted fine. Dnf said there were a 
lot of updates ready to go on so I put them on. On the next reboot Gnome 
would no longer start with Xorg or Wayland, exhibiting the same 
situations as KDE.
    To try and investigate the issue, I booted into SDDM and used 
ctrl-alt-F2 to switch to a terminal login, but that did the same thing, 
it displayed a black screen and the monitor went into sleep mode with a 
loss of signal notification.
    I'm currently sending this mail from Thunderbird under UBUNTU using 
the thunderbird configuration from the Fedora implementation.
    Can anyone give me any hints on what I can do to try to get around 
these situations?


regards,
Steve



OpenPGP_0x594338B1DE179AB2.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: Strange behavior with F40 server iso and VM

2024-10-14 Thread Tim via users
Tim:
>> I'm wondering what *less* user data separation means?

Barry:
> I assume it means using btrfs to put / and /home into the same file system.
> For a server the data that the server handles is in a separate file system.
> 
> The trade offs for a server and a desktop and different.
> 

The bit, in the post I replied to had a couple of aspects that piqued
my interest.

* One comment was quite understandable, with separating user data from
system data.  Where /home could be an independent partition, or a
directory, or one of those malleable pretend partitions.  Giving
differing controls over separation.

* The other comment was about separating different user data from each
other.  Which sounded like it meant user joebloggs versus user janedoe,
etc.

I have some NASs that are a complete minefield in that regards.  They
like to store data as owned by nobody, or everybody.  Then control
access by how you log on (very Windows 98-like).  Which doesn't help
when you access the data via some other method (e.g. NFS versus SMB)
and in the meantime it's made some directory be owned by someone else
and you lose access to it.  Then they have pseudo partitions of PUBLIC
versus your private files.  All in all, it's incoherent and
inconsistent.

I have mixed feelings about (allegedly) making things easier for the
technically illiterate.  Often it's not very well thought out, and it's
just another confusing way to do something, or dumbed down the point
where it's worse than useless.

And making computing easier for the less knowledgeable is the reason
why we had masses of computer viruses (people with little clue about
safe computing being exploited by asshats with no moral conscience). 
The blackhats who falsely claim to be improving things by discovering
flaws (and then exploiting them maliciously) should be treated like
arsonists (with derision and deprivation of liberty).

-- 
 
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: Strange behavior with F40 server iso and VM

2024-10-14 Thread Peter Boy Uni


> Am 14.10.2024 um 05:28 schrieb Tim via users :
> 
> On Mon, 2024-10-14 at 00:04 +0200, Peter Boy Uni wrote:
>> Server follows the good old Unix principle to strictly separate user
>> data from system data, and furthermore separates different user data
>> from each other. The goal is to minimize the effects of possible file
>> system problems. Workstation gave up this principle some times ago in
>> favor of less effort for system configuration and to make it easier
>> for less experienced users.
> 
> I'm wondering what *less* user data separation means?

Server puts user data and system data into separate filesystems. In case of 
filesystem issues they don’t affect each other, you can format each 
independently from the other. You can umount the user data while doing critical 
system maintenance to protect user data from any unintended change. 

„Less“ would be putting everything in one *filesystem* separating them not at 
all or use a pseudo-separating filesystem like BTRFS. Its „subvolumes“ are by 
no means independent from each other. These are just kind of „enhanced 
subdirectories“.   

Of course, in some cases this strict separating strategy might be an overkill. 
Obviously, workstation WG considered it an overkill for desktop computers where 
in most cases there is only one person working on it and owning all data and in 
(seldom) case of data loss there is only one person affected and not a bunch of 
different users. And on Servers it could be an overkill in some cases. During 
installation, therefore there is the option to switch to another filesystem 
type. You can even easily introduce a BTRFS filesystem later, when there arises 
a need for it. 

I’m writing a Server documentation article describing those options. 

> 
> World read and execute permissions on /home/username?  All users in a
> common group by default, with group read and execute permissions? 
> Something else?

No, that’s not a separation but a restriction. :-)




--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
p...@fedoraproject.org

Timezone: CET (UTC+1) / CEST (UTC+2)

Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast

-- 
___
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: Log your reports for F41 Upgrade Test Days

2024-10-14 Thread Luna Jernberg
Me and lemonzest logged our testing with the GNOME version earlier today

Den mån 14 okt. 2024 kl 10:36 skrev Luna Jernberg :

> Decided to jump in and test today
>
> Den mån 14 okt. 2024 kl 04:30 skrev Sumantro Mukherjee <
> sumuk...@redhat.com>:
>
>> Hey All,
>>
>> A gentle reminder, today will be the last day to record your upgrade
>> experiences in [0]
>> This will help us not only know the problems you faced (if at all any)
>> and then resolve
>> them (if they end up blocking).
>>
>> [0] http://fedoraproject.org/wiki/Test_Day:2024-10-11_F41_Upgrade_Test_Day
>>
>>
>> --
>> //sumantro
>> Fedora QE
>> TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
>> --
>> ___
>> 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