Created attachment 1470418 [details] Installation Error Message Description of problem: I have a dual boot in my notebook sony waio. The installation attempt is made by the pendrive. Then open the welcome window. So far so good. But when I click the install button, this message appears: "anaconda is unable to create /var/run/anaconda.pid because the file already exists. Anaconda is already running, or a previous instance of anaconda has crashed" I already looked for solutions on this site but I did not find any solution that could solve my problem. When I do the same procedure on the virtualbox, the same message appears, however, it opens the installation window and I can install Fedora normally. Someone who has been through this, could help me? Version-Release number of selected component (if applicable): 28 workstation How reproducible: Steps to Reproduce: 1. 2. 3. I followed the steps from this tutorial: https://www.youtube.com/watch?v=J20Gf6Bpwwk Actual results: Expected results: Additional info:
Hi, try to remove the file /var/run/anaconda.pid before you click the install button.
(In reply to Vendula Poncova from comment #1) > Hi, try to remove the file /var/run/anaconda.pid before you click the > install button. Hi. The file does not exist. It is generated when I click the install button. And then, the file is deleted when the error occurs.
It looks like anaconda is started multiple times at a time. Please, wait for the error message and attach all files /tmp/*log with anaconda logs.
(In reply to Vendula Poncova from comment #3) > It looks like anaconda is started multiple times at a time. Please, wait for > the error message and attach all files /tmp/*log with anaconda logs. With Linux Mint works. However, with Fedora, don't. I liked Fedora, more than Mint. I am almost giving up on the Fedora.
Hello Bianca, I'm sorry to hear that, however, we need more information to be able to fix your issue. Could you please try to get and attach logs mentioned in comment 3.
(In reply to Jiri Konecny from comment #5) > Hello Bianca, > > I'm sorry to hear that, however, we need more information to be able to fix > your issue. Could you please try to get and attach logs mentioned in comment > 3. I could not find the logs.
Thanks for the reply. In that case could you please provide us journal log. That could give us lead on what is happening there. To get the journal log please follow these steps: 1. reproduce the bug 2. open terminal 3. type 'journalctl > journal.log' 4. attach this log to this bug
(In reply to Jiri Konecny from comment #7) > Thanks for the reply. In that case could you please provide us journal log. > That could give us lead on what is happening there. > > To get the journal log please follow these steps: > > 1. reproduce the bug > 2. open terminal > 3. type 'journalctl > journal.log' > 4. attach this log to this bug Hello Jiri. Thanks. I will try reproduce the bug.
Hi! I I got it! Thank you Jiri.
Created attachment 1472754 [details] Bug`s log
Thanks a lot for this log. If I'm not mistaken this is the root cause of the crash. Aug 02 12:05:17 localhost-live system-python[2387]: detected unhandled Python exception in '/sbin/anaconda' Traceback (most recent call last): File "/sbin/anaconda", line 655, in <module> matched = device_matches("LABEL=OEMDRV", disks_only=True) File "/usr/lib64/python3.6/site-packages/pyanaconda/storage_utils.py", line 893, in device_matches single_spec_matches = udev.resolve_glob(full_spec) File "/usr/lib/python3.6/site-packages/blivet/udev.py", line 155, in resolve_glob for dev in get_devices(): File "/usr/lib/python3.6/site-packages/blivet/udev.py", line 73, in get_devices dev = device_to_dict(device) File "/usr/lib/python3.6/site-packages/blivet/udev.py", line 48, in device_to_dict result = dict(device.properties) File "/usr/lib/python3.6/site-packages/pyudev/device/_device.py", line 1085, in __getitem__ return ensure_unicode_string(value) File "/usr/lib/python3.6/site-packages/pyudev/_util.py", line 67, in ensure_unicode_string value = value.decode(sys.getfilesystemencoding()) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe8 in position 0: invalid continuation byte It looks like the problem comes from our storage library. Changing components if they can find out more about the crash.
Hi Jiri. Thanks for answering. I did not understand what should be done...
Hello Bianca, you don't need to do anything right now. I just asked developers from area of your issue to take a look on this.
(In reply to Jiri Konecny from comment #13) > Hello Bianca, you don't need to do anything right now. I just asked > developers from area of your issue to take a look on this. Thanks Jiri. You are very kind.
An addendum: This problem also occurs with versions 26 and 27.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.