Hi Everyone,
I just upgraded three machines to Fedora 41 using https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/. The machines were two desktops and one server. All the machines use the default Fedora repos; and they do not use third party repos.
The process went as expected. There were no problems.
`rpmconf -a` replaced more conf files than usual. For my configurations, it looks like older Java versions present in my environment were the reason for the extra replacements.
It looks like `clean-rpm-gpg-pubkey` is a new program added to optional post-upgrade steps.
RPMFusion users may want to wait for the third party repository to rebuild its packages for F41.
Jeff
On Wed, Oct 30, 2024 at 1:38 PM pocallaghan@gmail.com wrote:
On Wed, 2024-10-30 at 12:48 -0400, Jeffrey Walton wrote:
RPMFusion users may want to wait for the third party repository to rebuild its packages for F41.
RPMfusion repos are already on F41.
Conflicting NVIDIA Packages from RPM Fusion, https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/thread/M3JRVUET763A2FFOII7PGUXIKDKEZJTK/.
Jeff
Is it still true that stock F41 does not include the ability to run X11? I'm stuck until Wayland has a way to invoke Firefox from a cron job.
On Wed, Oct 30, 2024 at 4:18 PM Dave Close dave@compata.com wrote:
Is it still true that stock F41 does not include the ability to run X11? I'm stuck until Wayland has a way to invoke Firefox from a cron job.
I don't run X so I can't say for certain. But there's a lot of X11 gear in the standard repos:
$ dnf search x11 | wc -l 470
$ dnf search x11 | grep 'xorg-x11' xorg-x11-drivers.x86_64: X.Org X11 driver installation package xorg-x11-drv-ati.x86_64: Xorg X11 ati video driver xorg-x11-drv-dummy.x86_64: Xorg X11 dummy video driver xorg-x11-drv-evdev.x86_64: Xorg X11 evdev input driver xorg-x11-drv-evdev-devel.i686: Xorg X11 evdev input driver development package. xorg-x11-drv-evdev-devel.x86_64: Xorg X11 evdev input driver development packag e. xorg-x11-drv-intel.i686: Xorg X11 Intel video driver xorg-x11-drv-intel.x86_64: Xorg X11 Intel video driver xorg-x11-drv-libinput.x86_64: Xorg X11 libinput input driver xorg-x11-drv-libinput-devel.i686: Xorg X11 libinput input driver development pa ckage. xorg-x11-drv-libinput-devel.x86_64: Xorg X11 libinput input driver development package. xorg-x11-drv-nouveau.x86_64: Xorg X11 nouveau video driver for NVIDIA graphics chipsets xorg-x11-drv-openchrome.x86_64: Xorg X11 openchrome video driver xorg-x11-drv-qxl.x86_64: Xorg X11 qxl video driver xorg-x11-drv-synaptics-devel.i686: Xorg X11 synaptics input driver xorg-x11-drv-synaptics-devel.x86_64: Xorg X11 synaptics input driver xorg-x11-drv-synaptics-legacy.x86_64: Xorg X11 synaptics input driver xorg-x11-drv-vesa.x86_64: Xorg X11 vesa video driver xorg-x11-drv-vmware.x86_64: Xorg X11 vmware video driver xorg-x11-drv-wacom.x86_64: Xorg X11 wacom input driver xorg-x11-drv-wacom-devel.i686: Xorg X11 wacom input driver development package xorg-x11-drv-wacom-devel.x86_64: Xorg X11 wacom input driver development packag e xorg-x11-font-utils.x86_64: X.Org X11 font utilities xorg-x11-proto-devel.noarch: X.Org X11 Protocol headers xorg-x11-util-macros.noarch: X.Org X11 Autotools macros xorg-x11-xauth.x86_64: X.Org X11 X authority utilities xorg-x11-xbitmaps.noarch: X.Org X11 application bitmaps xorg-x11-xdm.x86_64: X.Org X11 xdm - X Display Manager xorg-x11-xinit.x86_64: X.Org X11 X Window System xinit startup scripts xorg-x11-xtrans-devel.noarch: X.Org X11 developmental X transport library xorg-x11-drv-amdgpu.x86_64: AMD GPU video driver xorg-x11-drv-armada.x86_64: X.org graphics driver for KMS based systems with pl uggable GPU backend xorg-x11-drv-wacom-serial-support.x86_64: Files for enabling the wacom_w8001 ke rnel driver xorg-x11-fonts-100dpi.noarch: A set of 100dpi resolution fonts for the X Window System xorg-x11-fonts-75dpi.noarch: A set of 75dpi resolution fonts for the X Window S ystem xorg-x11-fonts-ISO8859-1-100dpi.noarch: A set of 100dpi ISO-8859-1 fonts for X xorg-x11-fonts-ISO8859-1-75dpi.noarch: A set of 75dpi ISO-8859-1 fonts for X xorg-x11-fonts-ISO8859-14-100dpi.noarch: ISO8859-14-100dpi fonts xorg-x11-fonts-ISO8859-14-75dpi.noarch: ISO8859-14-75dpi fonts xorg-x11-fonts-ISO8859-15-100dpi.noarch: ISO8859-15-100dpi fonts xorg-x11-fonts-ISO8859-15-75dpi.noarch: ISO8859-15-75dpi fonts xorg-x11-fonts-ISO8859-2-100dpi.noarch: A set of 100dpi Central European langua ge fonts for X xorg-x11-fonts-ISO8859-2-75dpi.noarch: A set of 75dpi Central European language fonts for X xorg-x11-fonts-ISO8859-9-100dpi.noarch: ISO8859-9-100dpi fonts xorg-x11-fonts-ISO8859-9-75dpi.noarch: ISO8859-9-75dpi fonts xorg-x11-fonts-Type1.noarch: Type1 fonts provided by the X Window System xorg-x11-fonts-cyrillic.noarch: Cyrillic fonts for X xorg-x11-fonts-ethiopic.noarch: Ethiopic fonts xorg-x11-fonts-misc.noarch: misc bitmap fonts for the X Window System xorg-x11-server-Xephyr.x86_64: A nested server xorg-x11-server-Xnest.x86_64: A nested server xorg-x11-server-Xorg.x86_64: Xorg X server xorg-x11-server-Xspice.x86_64: XSpice is an X server that can be accessed by a Spice client xorg-x11-server-Xvfb.x86_64: A X Windows System virtual framebuffer X server xorg-x11-server-Xwayland.i686: Xwayland xorg-x11-server-Xwayland.x86_64: Xwayland xorg-x11-server-Xwayland-devel.i686: Development package xorg-x11-server-Xwayland-devel.x86_64: Development package xorg-x11-server-common.x86_64: Xorg server common files xorg-x11-server-devel.i686: SDK for X server driver module development xorg-x11-server-devel.x86_64: SDK for X server driver module development xorg-x11-server-source.noarch: Xserver source code required to build VNC server (Xvnc) xorg-x11-server-x2gokdrive.x86_64: KDrive graphical server backend for X2GoServ er xorg-x11-xinit-session.x86_64: Display manager support for ~/.xsession and ~/.X clients
Jeff
Once upon a time, Dave Close dave@compata.com said:
Is it still true that stock F41 does not include the ability to run X11?
That hasn't ever been true...
On Wed, 30 Oct 2024 13:17:56 -0700 Dave Close dave@compata.com wrote:
Is it still true that stock F41 does not include the ability to run X11? I'm stuck until Wayland has a way to invoke Firefox from a cron job.
I've made the upgrade from Fedora 39 to 41 (Xfce). Everything is OK. My X11 / C / Motif stuff keep on working fine.
Angelo
On 10/30/24 4:39 PM, t_pol@tiscali.it wrote:
On Wed, 30 Oct 2024 13:17:56 -0700 Dave Close dave@compata.com wrote:
Is it still true that stock F41 does not include the ability to run X11? I'm stuck until Wayland has a way to invoke Firefox from a cron job.
I've made the upgrade from Fedora 39 to 41 (Xfce). Everything is OK. My X11 / C / Motif stuff keep on working fine.
Angelo
X11 is on f42 rawhide virtual machine so not dead yet
On Oct 30, 2024, at 16:18, Dave Close dave@compata.com wrote:
Is it still true that stock F41 does not include the ability to run X11? I'm stuck until Wayland has a way to invoke Firefox from a cron job.
If it’s a cron job that runs as your user as part of your login session (and shouldn’t ever run if you aren’t logged in) then don’t use cron, create a systemd timer that runs in your user session, put files in $HOME/.config/systemd/user/. Since it runs as part of your session it can launch graphical programs, speak to dbus, etc.
If it’s a detached Firefox that isn’t connected to any logged in session, just run it in an Xvnc session, which is X11, and you can use cron or whatever you want. Connect to the session through a VNC client if you ever need to interact with the Firefox but it won’t need to be running at the same time you are logged in.
Cron talking to X is just super janky and I try to avoid it. That being said, I’ve built a whole automation project doing something similar with ansible, so I’m a bit of a hypocrite.
OK++
Ive upgraded 1/2 machines, using graphical interface from the "notify" prompt.
all went smoothly.
Speed of update seems faster, maybe its the ~3 progress bars updating so smoothly.
new here is the 2nd line below - perhaps the replacing line is obvious, and suppressible ?
xwaylandvideobridge x86_64 0.4.0-7.fc41 updates 209.3 KiB replacing xwaylandvideobridge x86_64 0.4.0-6.fc41 fedora 213.3 KiB
On Wed, Oct 30, 2024 at 10:49 AM Jeffrey Walton noloader@gmail.com wrote:
Hi Everyone,
I just upgraded three machines to Fedora 41 using <https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/
.
The machines were two desktops and one server. All the machines use the default Fedora repos; and they do not use third party repos.
The process went as expected. There were no problems.
`rpmconf -a` replaced more conf files than usual. For my configurations, it looks like older Java versions present in my environment were the reason for the extra replacements.
It looks like `clean-rpm-gpg-pubkey` is a new program added to optional post-upgrade steps.
RPMFusion users may want to wait for the third party repository to rebuild its packages for F41.
Jeff
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@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
On 2/11/24 15:23, jim.cromie@gmail.com wrote:
new here is the 2nd line below - perhaps the replacing line is obvious, and suppressible ?
xwaylandvideobridge x86_64 0.4.0-7.fc41 updates 209.3 KiB replacing xwaylandvideobridge x86_64 0.4.0-6.fc41 fedora 213.3 KiB
The 2nd line you are showing is what I was querying in my thread "Strange DNF5 Functionality" where that display is new with F41 and for me, for every update, that 2nd line lists the repository as "<unknown>".
regards, Steve
On 2 Nov 2024, at 22:04, Stephen Morris steve.morris.au@gmail.com wrote:
Functionality" where that display is new with F41 and for me, for every update, that 2nd line lists the repository as "<unknown>".
This is because the database with the repo cannot be migrated from f40/dnf4 to f41/dnf5. As you update the repo data will get filled in for the updated packages.
The reason seems to be an issue with database scheme problems.
Barry
On 4 Nov 2024, at 12:58, Barry barry@barrys-emacs.org wrote:
This is because the database with the repo cannot be migrated from f40/dnf4 to f41/dnf5.
Should say database with the “repo info cannot…”.
Barry