Bug 2314607 - Anaconda crashes after clicking on Finish installation (policykit issue)
Summary: Anaconda crashes after clicking on Finish installation (policykit issue)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 42
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jiri Konecny
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-09-25 07:22 UTC by Kamil Páral (Red Hat)
Modified: 2025-12-09 08:32 UTC (History)
4 users (show)

Fixed In Version: anaconda-42.11-1
Clone Of:
Environment:
Last Closed: 2025-12-09 08:32:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
anaconda.log (20.54 KB, text/plain)
2024-09-25 07:24 UTC, Kamil Páral (Red Hat)
no flags Details
dbus.log (3.91 KB, text/plain)
2024-09-25 07:25 UTC, Kamil Páral (Red Hat)
no flags Details
journal.log (2.53 MB, text/plain)
2024-09-25 07:25 UTC, Kamil Páral (Red Hat)
no flags Details
lvm.log (385.40 KB, text/plain)
2024-09-25 07:25 UTC, Kamil Páral (Red Hat)
no flags Details
packaging.log (15.77 KB, text/plain)
2024-09-25 07:25 UTC, Kamil Páral (Red Hat)
no flags Details
program.log (5.41 KB, text/plain)
2024-09-25 07:25 UTC, Kamil Páral (Red Hat)
no flags Details
storage.log (225.07 KB, text/plain)
2024-09-25 07:25 UTC, Kamil Páral (Red Hat)
no flags Details

Description Kamil Páral (Red Hat) 2024-09-25 07:22:17 UTC
Description of problem:
After a default installation of Fedora-Workstation-Live-x86_64-41-20240924.n.0.iso (all defaults), this is printed out to the terminal after clicking on Finish Installation button:

/usr/sbin/setenforce:  security_setenforce() failed:  Permission denied
/usr/lib/python3.13/site-packages/blivet/threads.py:31: DeprecationWarning: Passing arguments to RLock is deprecated and will be removed in 3.15
  blivet_lock = threading.RLock(verbose=flags.debug_threads)

umount: /mnt/sysimage/tmp: must be superuser to unmount.
umount: /mnt/sysimage/sys/fs/selinux: must be superuser to unmount.
umount: /mnt/sysimage/sys: must be superuser to unmount.
umount: /mnt/sysimage/run: must be superuser to unmount.
umount: /mnt/sysimage/proc: must be superuser to unmount.
umount: /mnt/sysimage/home: must be superuser to unmount.
umount: /mnt/sysimage/dev/shm: must be superuser to unmount.
umount: /mnt/sysimage/dev/pts: must be superuser to unmount.
umount: /mnt/sysimage/dev: must be superuser to unmount.
umount: /mnt/sysimage/boot: must be superuser to unmount.
umount: /mnt/sysimage: must be superuser to unmount.
vda: Failed to write 'change' to '/sys/devices/pci0000:00/0000:00:02.6/0000:07:00.0/virtio6/block/vda/uevent': Permission denied
vda1: Failed to write 'change' to '/sys/devices/pci0000:00/0000:00:02.6/0000:07:00.0/virtio6/block/vda/vda1/uevent': Permission denied
vda2: Failed to write 'change' to '/sys/devices/pci0000:00/0000:00:02.6/0000:07:00.0/virtio6/block/vda/vda2/uevent': Permission denied
vda3: Failed to write 'change' to '/sys/devices/pci0000:00/0000:00:02.6/0000:07:00.0/virtio6/block/vda/vda3/uevent': Permission denied
sr0: Failed to write 'change' to '/sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sr0/uevent': Permission denied
loop0: Failed to write 'change' to '/sys/devices/virtual/block/loop0/uevent': Permission denied
zram0: Failed to write 'change' to '/sys/devices/virtual/block/zram0/uevent': Permission denied
Traceback (most recent call last):
  File "/usr/lib64/python3.13/site-packages/gi/overrides/BlockDev.py", line 1250, in wrapped
    ret = orig_obj(*args, **kwargs)
  File "/usr/lib64/python3.13/site-packages/gi/overrides/BlockDev.py", line 892, in lvm_lvs
    return _lvm_lvs(vg_name)
gi.repository.GLib.GError: g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Sender is not authorized to send message (9)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/anaconda-cleanup", line 82, in <module>
    devicetree.populate(cleanup_only=True)
    ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.13/site-packages/blivet/threads.py", line 49, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.13/site-packages/blivet/populator/populator.py", line 444, in populate
    self._populate()
    ~~~~~~~~~~~~~~^^
  File "/usr/lib/python3.13/site-packages/blivet/threads.py", line 49, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.13/site-packages/blivet/populator/populator.py", line 488, in _populate
    self.handle_device(dev)
    ~~~~~~~~~~~~~~~~~~^^^^^
  File "/usr/lib/python3.13/site-packages/blivet/threads.py", line 49, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.13/site-packages/blivet/populator/populator.py", line 282, in handle_device
    self._add_name(name)
    ~~~~~~~~~~~~~~^^^^^^
  File "/usr/lib/python3.13/site-packages/blivet/threads.py", line 49, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.13/site-packages/blivet/populator/populator.py", line 144, in _add_name
    if name not in self.names:
                   ^^^^^^^^^^
  File "/usr/lib/python3.13/site-packages/blivet/threads.py", line 49, in run_with_lock
    return m(*args, **kwargs)
  File "/usr/lib/python3.13/site-packages/blivet/devicetree.py", line 146, in names
    lv_info = list(lvs_info.cache.keys())
                   ^^^^^^^^^^^^^^
  File "/usr/lib/python3.13/site-packages/blivet/static_data/lvm_info.py", line 44, in cache
    lvs = blockdev.lvm.lvs()
  File "/usr/lib64/python3.13/site-packages/gi/overrides/BlockDev.py", line 1272, in wrapped
    raise transform[1](msg)
gi.overrides.BlockDev.LVMError: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Sender is not authorized to send message
anaconda must be run as root.
/usr/sbin/setenforce:  security_setenforce() failed:  Permission denied


Look like there are two exceptions happening sequentially, the second one blivet-related, the first one related to lvm?

The system looks fully functional. I'm not aware of any negative effect this might have on the installed system.


Version-Release number of selected component (if applicable):
anaconda-41.31-1.fc41.x86_64
anaconda-core-41.31-1.fc41.x86_64
anaconda-gui-41.31-1.fc41.x86_64
anaconda-install-env-deps-41.31-1.fc41.x86_64
anaconda-live-41.31-1.fc41.noarch
anaconda-tui-41.31-1.fc41.x86_64
anaconda-widgets-41.31-1.fc41.x86_64
blivet-data-3.11.0-1.fc41.noarch
blivet-gui-runtime-2.5.0-4.fc41.noarch
python3-blivet-3.11.0-1.fc41.noarch


How reproducible:
always

Steps to Reproduce:
1. boot F41 Workstation compose
2. open terminal
3. run "liveinst"
4. perform a default installation (all defaults)
5. click on Finish Installation button at the end
6. see the error printed into terminal

Comment 1 Kamil Páral (Red Hat) 2024-09-25 07:24:58 UTC
Created attachment 2048610 [details]
anaconda.log

Comment 2 Kamil Páral (Red Hat) 2024-09-25 07:25:01 UTC
Created attachment 2048611 [details]
dbus.log

Comment 3 Kamil Páral (Red Hat) 2024-09-25 07:25:04 UTC
Created attachment 2048612 [details]
journal.log

Comment 4 Kamil Páral (Red Hat) 2024-09-25 07:25:07 UTC
Created attachment 2048613 [details]
lvm.log

Comment 5 Kamil Páral (Red Hat) 2024-09-25 07:25:11 UTC
Created attachment 2048614 [details]
packaging.log

Comment 6 Kamil Páral (Red Hat) 2024-09-25 07:25:14 UTC
Created attachment 2048615 [details]
program.log

Comment 7 Kamil Páral (Red Hat) 2024-09-25 07:25:17 UTC
Created attachment 2048616 [details]
storage.log

Comment 8 Kamil Páral (Red Hat) 2024-09-25 08:04:16 UTC
Jiri Konecny responded on Matrix about this bug with some details:

Hi, yes, I'm already aware of that. Good think is it doesn't block stuff. The bad thing is that we need to find a way to fix our PAM configuration to cover other than the main Anaconda script which is the issue here.
On Live installation we migrated recently to PAM from what we had before, but it seems the new PAM configuration covers only main anaconda run and not other two parts we are executing there. I was briefly looking on that but I don't have any experience with it
in short it fails here: https://github.com/rhinstaller/anaconda/blob/master/data/liveinst/liveinst#L134 if anyone has experience with PAM configuration we would be glad for a help here
the same issue happens here: https://github.com/rhinstaller/anaconda/blob/master/data/liveinst/liveinst#L190
also visible in the traceback

Comment 9 Jiri Konecny 2024-10-23 14:02:40 UTC
PR: https://github.com/rhinstaller/anaconda/pull/5956

Comment 10 Aoife Moloney 2025-02-26 13:12:07 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.


Note You need to log in before you can comment on or make changes to this bug.