Osama,

I have a complicated environment which includes a VirtualBox VM.

I selected 'KDE Plasma Workspace' and a bunch of other packages... which 
resulted in the failure. I then tried just the "KDE Plasma Workspace" which 
succeeded. The failure comes from a complicated product mix. Both the failure 
and success had NO other differences. I went to the now running system and 
added the groups that I had initially selected... and found that the Plasma 
Workspace had multiple problems/failures. The biggest problem I had with this 
is the installation environment. Failures leave a NON functional system. It 
would be nice to be able to load a saved copy of everything up to the failure 
and then do a "rescue" to debug. 

I selected a customized partition setup and ext4 file system.

Below is a sample of what I install after a successful installation:

Regards,

George...

#!/bin/bash -xv

# Available Environment Groups:

# Installed Environment Groups:

dnf -y group install --with-optional --noautoremove --best --skip-broken 'KDE 
Plasma Workspaces'

# Installed Groups:

dnf -y group install --with-optional --noautoremove --best --skip-broken 
'Administration Tools'
dnf -y group install --with-optional --noautoremove --best --skip-broken 
'LibreOffice'

# Available Groups:

dnf -y group install --with-optional --noautoremove --best --skip-broken 'C 
Development Tools and Libraries'
dnf -y group install --with-optional --noautoremove --best --skip-broken 
'Compiz'
dnf -y group install --with-optional --noautoremove --best --skip-broken 'D 
Development Tools and Libraries'
dnf -y group install --with-optional --noautoremove --best --skip-broken 
'Development Tools'
dnf -y group install --with-optional --noautoremove --best --skip-broken 
'Editors'
dnf -y group install --with-optional --noautoremove --best --skip-broken 
'Office/Productivity'
dnf -y group install --with-optional --noautoremove --best --skip-broken 
'Python Classroom'
dnf -y group install --with-optional --noautoremove --best --skip-broken 
'Python Science'
dnf -y group install --with-optional --noautoremove --best --skip-broken 
'Robotics'
dnf -y group install --with-optional --noautoremove --best --skip-broken 'RPM 
Development Tools'
dnf -y group install --with-optional --noautoremove --best --skip-broken 
'System Tools'
dnf -y group install --with-optional --noautoremove --best --skip-broken 
'Text-based Internet'
dnf -y group install --with-optional --noautoremove --best --skip-broken 
'Window Managers'

exit 0










On Tuesday, December 12, 2023 at 10:11:56 PM PST, Osama Albahrani 
<osalb...@ncsu.edu> wrote: 





Hi George,

I can try on my end, what steps should I take? Could you provide more details 
on how to reproduce the bug?

Best,
Osama

On Tue, 12 Dec 2023 at 11:58 PM George R Goffe via test 
<test@lists.fedoraproject.org> wrote:
> Hi,
> 
> I keep seeing this "bug" across multiple fedora 40 Fedora netinst iso images. 
> Am I doing something wrong?
> 
> "current" image is  
> Fedora-Workstation-Live-osb-Rawhide-20231212.n.0.x86_64.iso
> 
> Best regards,
> 
> George
> 
> --
> _______________________________________________
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-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/test@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
> 
> 
--
_______________________________________________
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-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/test@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to