Created attachment 1949960 [details] The anaconda launched with the error and default language(Vietnamese) I tried Fedora 38 beta with Budgie spin, it was good, but when I launch the anaconda installer it showed up as this error "Anaconda is unable to create /var/run/anaconda.pid because the file already exists. Anaconda is already running, or previous instance of anaconda has crashed.", but I didn't launch the installer before and the default language is Vietnamese, not English. Although I'm a Vietnamese guy, but I want the English instead. Hope you fix it soon. Thanks you
Please don't mark bug reports as private unless they are security-sensitive. Thank you.
I've also hit the same problem with Fedora Workstation, all default settings (literally just booted it, connected to WiFi and started anaconda). Same error message as submitted above, I tried deleting the pid file and pkill-ing the anaconda process, then re-running it, but still it did not start. Hopefully this bug is reproducible since I need the machine I tried installing on, so I already installed F37 on it.
trinhanhhathanh1701, Erazem, can you try the latest Workstation image? [1] What is your location? Can you reproduce the problem regularly, i.e. if you reboot the system, boot the Live again, and start the installer again, does it happen again? Can you do that 3 times in a row? When you see this bug, please save the system journal ("journalctl -b > journal.txt") and attach it here together with /tmp/anaconda.log. Thanks! PS: Erazem, you can still boot the Live image and start the installer even when you already installed the system. Just don't continue in the installer and quit it after starting, and nothing will get overwritten. [1] https://kojipkgs.fedoraproject.org/compose/branched/Fedora-38-20230326.n.1/compose/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-38-20230326.n.1.iso
Hi @kparal, sorry for the (very) late reply. I tried it again today and got the same result, but this time I also have the files you requested. > What is your location? Can you reproduce the problem regularly, i.e. if you > reboot the system, boot the Live again, and start the installer again, does > it happen again? Can you do that 3 times in a row? Finland, and yes, I can consistently reproduce it. > When you see this bug, please save the system journal ("journalctl -b > > journal.txt") and attach it here together with /tmp/anaconda.log. Thanks! I basically never use Bugzilla, so I can't find the file upload button atm, hopefully a 1 year expiry on a pastebin service is fine: anaconda.log: https://privatebin.at/?baeacec38aea6e5e#EPiw69nWjQ9sHyP9FZFJ34iVpwvZS5cZPmf5ipNfEkzf journalctl: https://privatebin.at/?a2bc12696f152045#6JBu2bRBE2KyZnHceijhYHjr55f8QdwG1sqdjhd6Rof8 > PS: Erazem, you can still boot the Live image and start the installer even > when you already installed the system. Just don't continue in the installer > and quit it after starting, and nothing will get overwritten. Thanks for the tip, forgot it doesn't touch the disk until I start the installation.
Oh, as a side note, I can only reproduce this problem when installing to a Lenovo Thinkpad P15, it works fine on a T540p and in GNOME Boxes, idk if this helps debug the problem further.
So there's this in the journal: Apr 14 13:21:08 localhost-live anaconda[2807]: anaconda: anaconda: Display mode is set to 'interactive graphical mode'. Apr 14 13:21:08 localhost-live anaconda[2807]: program: Running... losetup --list Apr 14 13:21:08 localhost-live anaconda[2807]: anaconda: startup_utils: check_memory(): total:31941, needed:320 Apr 14 13:21:08 localhost-live anaconda[2807]: anaconda: startup_utils: check_memory(): total:31941, graphical:410 Apr 14 13:21:09 localhost-live kernel: nouveau 0000:01:00.0: sec2: halted Apr 14 13:21:09 localhost-live kernel: nouveau 0000:01:00.0: sec2: TRACEPC SCTL 00007021 TIDX 1b1f0000 Apr 14 13:21:09 localhost-live kernel: nouveau 0000:01:00.0: sec2: TRACEPC: 000023ac Apr 14 13:21:09 localhost-live kernel: nouveau 0000:01:00.0: sec2: TRACEPC: 00002055 ... Apr 14 13:21:09 localhost-live kernel: nouveau 0000:01:00.0: sec2: TRACEPC: 00002318 Apr 14 13:21:10 localhost-live gnome-shell[2925]: nvc0_screen_create:1169 - Error allocating PGRAPH context for M2MF: -110 Apr 14 13:21:10 localhost-live kernel: nouveau 0000:01:00.0: sec2:cmdq: timeout waiting for queue ready Apr 14 13:21:10 localhost-live kernel: nouveau 0000:01:00.0: gr: init failed, -110 Apr 14 13:21:10 localhost-live gnome-shell[2925]: libEGL warning: egl: failed to create dri2 screen I wonder if anaconda fails to create a window because of nouveau driver issues. If you boot the Live image using "Troubleshooting -> Basic graphics mode" (in the install media boot menu), does it allow you to start anaconda just fine?
@kamil That seems to work (on the original USB that had the beta version). I'll try sometime soon if I have the time with the latest Fedora 38 iso.
Ok, so it's caused by nouveau.
@Kamil, I'm not sure if this has been fixed upstream yet, but today I had to reinstall Fedora 38 and I couldn't do it, because with normal mode Anaconda doesn't work and with the fallback mode, the installed system uses software rendering instead of nouveau or whatever is the default on Optimus laptops. If the issue has been fixed in nouveau, is it possible to release a new iso (I used 1.6), because at the moment I can't install Fedora properly. If you have any other ideas, they're welcome.
No, Fedora 38 install media will not get updated, officially. But there are unofficial respins of Live media which you can try [1]. They are not tested, though. If you install F38 in a basic graphics mode, it's not just for installation, it persists. In grub, you can remove "nomodeset", boot, and see if the issue is fixed with an updated system. Then you can edit the grub config file and regenerate the boot config to make the change persist. Or you can install the nvidia closed drivers. [1] https://dl.fedoraproject.org/pub/alt/live-respins/
This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '38'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 38 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.