Bug 2240162 - liveinst doesn't work on LXDE Live spin
Summary: liveinst doesn't work on LXDE Live spin
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 40
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: anaconda-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: https://discussion.fedoraproject.org/...
: 2248914 2256507 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-09-22 06:59 UTC by Akira TAGOH
Modified: 2024-09-17 08:49 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-09-17 08:49:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
anaconda log from /tmp (3.18 KB, text/plain)
2023-12-03 16:29 UTC, a.trubitsyn
no flags Details

Description Akira TAGOH 2023-09-22 06:59:21 UTC
Starting "Install to Hard Drive" icon at the desktop doesn't show any GUI window on LXDE Live spin.


Reproducible: Always

Steps to Reproduce:
1.Boot from Fedora-LXDE-Live-x86_64-39-20230920.n.0.iso
2.update anaconda packages to 39.32.3-1.fc39 (which is the latest at this moment)
3.Double-click "Install to Hard Drive" icon at the desktop
Actual Results:  
No GUI window

Expected Results:  
anaconda should works


What I got from lxterminal:
liveuser@localhost-live:~$ liveinst 
localuser:root being added to access control list
Starting installer, one moment...
anaconda 39.32.3-1.fc39 for Fedora 39 (pre-release) started.
 * installation log files are stored in /tmp during the installation
 * shell is available on TTY2 and in second TMUX pane (ctrl+b, then press 2)
 * when reporting a bug add logs from /tmp as separate text/plain attachments

X or window manager startup failed, falling back to text mode.
================================================================================
================================================================================
X was unable to start on your machine. Would you like to start VNC to connect to
this computer from another computer and perform a graphical installation or
continue with a text mode installation?

1) Start VNC
2) Use text mode

Please make a selection from the above ['c' to continue, 'h' to help, 'q' to
quit, 'r' to refresh]: 1
================================================================================
================================================================================
VNC Password

Please provide VNC password (must be six to eight characters long).
You will have to type it twice. Leave blank for no password

Password: 
Password (confirm): 
02:49:32 Starting VNC...
Traceback (most recent call last):
  File "/sbin/anaconda", line 440, in <module>
    display.setup_display(anaconda, opts)
  File "/usr/lib64/python3.12/site-packages/pyanaconda/display.py", line 385, in setup_display
    vnc_server.startServer()
  File "/usr/lib64/python3.12/site-packages/pyanaconda/vnc.py", line 250, in startServer
    util.startX(xvnccommand, output_redirect=self.openlogfile(), timeout=self.timeout)
  File "/usr/lib64/python3.12/site-packages/pyanaconda/core/util.py", line 239, in startX
    signal.pause()
  File "/usr/lib64/python3.12/site-packages/pyanaconda/core/process_watchers.py", line 117, in _sigchld_handler
    cls._raise_exit_error(exit_statuses)
  File "/usr/lib64/python3.12/site-packages/pyanaconda/core/process_watchers.py", line 81, in _raise_exit_error
    raise ExitError(", ".join(exn_message))
pyanaconda.errors.ExitError: Xvnc exited with status 1
/usr/sbin/setenforce:  security_setenforce() failed:  Permission denied
vda: Failed to write 'change' to '/sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/uevent': Permission denied
vda1: Failed to write 'change' to '/sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/vda1/uevent': Permission denied
vda2: Failed to write 'change' to '/sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/block/vda/vda2/uevent': Permission denied
vda3: Failed to write 'change' to '/sys/devices/pci0000:00/0000:00:02.3/0000:04:00.0/virtio3/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
loop1: Failed to write 'change' to '/sys/devices/virtual/block/loop1/uevent': Permission denied
loop2: Failed to write 'change' to '/sys/devices/virtual/block/loop2/uevent': Permission denied
zram0: Failed to write 'change' to '/sys/devices/virtual/block/zram0/uevent': Permission denied
dm-0: Failed to write 'change' to '/sys/devices/virtual/block/dm-0/uevent': Permission denied
dm-1: Failed to write 'change' to '/sys/devices/virtual/block/dm-1/uevent': Permission denied
Traceback (most recent call last):
  File "/usr/lib64/python3.12/site-packages/gi/overrides/BlockDev.py", line 1226, in wrapped
    ret = orig_obj(*args, **kwargs)
          ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3.12/site-packages/gi/overrides/BlockDev.py", line 866, 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 "/bin/anaconda-cleanup", line 82, in <module>
    devicetree.populate(cleanup_only=True)
  File "/usr/lib/python3.12/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/blivet/populator/populator.py", line 446, in populate
    self._populate()
  File "/usr/lib/python3.12/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/blivet/populator/populator.py", line 490, in _populate
    self.handle_device(dev)
  File "/usr/lib/python3.12/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/blivet/populator/populator.py", line 284, in handle_device
    self._add_name(name)
  File "/usr/lib/python3.12/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/blivet/populator/populator.py", line 146, in _add_name
    if name not in self.names:
                   ^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/blivet/threads.py", line 53, in run_with_lock
    return m(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/blivet/devicetree.py", line 148, in names
    lv_info = list(lvs_info.cache.keys())
                   ^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/blivet/static_data/lvm_info.py", line 44, in cache
    lvs = blockdev.lvm.lvs()
          ^^^^^^^^^^^^^^^^^^
  File "/usr/lib64/python3.12/site-packages/gi/overrides/BlockDev.py", line 1248, 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

Also, still fails with sudo liveinst or so

Comment 1 a.trubitsyn 2023-12-03 16:27:13 UTC
I have same problem with Fedora-LXDE-Live-x86_64-39-1.5.iso 
It is latest iso. 
There is not LXDE flavor in https://dl.fedoraproject.org/pub/alt/live-respins/ at the moment.

1. boot from liveusb
2. start Desktop shortcut - see spinning wheel, then it disappear
For clear test
1. reboot from liveusb
2. type in lxterminal
   sudo /usb/bin/liveinst

** (process:2497): WARNING **: 11:05:37.505: expected enumeration type void, but got PyBlockDevPlugin instead

** (process:2497): WARNING **: 11:05:37.505: expected enumeration type void, but got PyBlockDevPlugin instead

** (process:2497): WARNING **: 11:05:37.505: expected enumeration type void, but got PyBlockDevPlugin instead

** (process:2497): WARNING **: 11:05:37.505: expected enumeration type void, but got PyBlockDevPlugin instead

** (process:2497): WARNING **: 11:05:37.505: expected enumeration type void, but got PyBlockDevPlugin instead

** (process:2497): WARNING **: 11:05:37.505: expected enumeration type void, but got PyBlockDevPlugin instead

** (process:2497): WARNING **: 11:05:37.506: expected enumeration type void, but got PyBlockDevPlugin instead

** (process:2497): WARNING **: 11:05:37.506: expected enumeration type void, but got PyBlockDevPlugin instead

** (process:2497): WARNING **: 11:05:37.506: expected enumeration type void, but got PyBlockDevPlugin instead

** (process:2497): WARNING **: 11:05:37.506: expected enumeration type void, but got PyBlockDevPlugin instead
Starting installer, one moment...

** (process:2594): WARNING **: 11:05:41.636: expected enumeration type void, but got PyBlockDevPlugin instead

** (process:2594): WARNING **: 11:05:41.636: expected enumeration type void, but got PyBlockDevPlugin instead

** (process:2594): WARNING **: 11:05:41.636: expected enumeration type void, but got PyBlockDevPlugin instead

** (process:2594): WARNING **: 11:05:41.636: expected enumeration type void, but got PyBlockDevPlugin instead

** (process:2594): WARNING **: 11:05:41.636: expected enumeration type void, but got PyBlockDevPlugin instead

** (process:2594): WARNING **: 11:05:41.636: expected enumeration type void, but got PyBlockDevPlugin instead

** (process:2594): WARNING **: 11:05:41.636: expected enumeration type void, but got PyBlockDevPlugin instead

** (process:2594): WARNING **: 11:05:41.636: expected enumeration type void, but got PyBlockDevPlugin instead

** (process:2594): WARNING **: 11:05:41.636: expected enumeration type void, but got PyBlockDevPlugin instead

** (process:2594): WARNING **: 11:05:41.636: expected enumeration type void, but got PyBlockDevPlugin instead
anaconda 39.32.6-2.fc39 for Fedora 39 started.
 * installation log files are stored in /tmp during the installation
 * shell is available on TTY2 and in second TMUX pane (ctrl+b, then press 2)
 * when reporting a bug add logs from /tmp as separate text/plain attachments
Traceback (most recent call last):
  File "/sbin/anaconda", line 333, in <module>
    startup_utils.live_startup()
  File "/usr/lib64/python3.12/site-packages/pyanaconda/startup_utils.py", line 358, in live_startup
    inhibit_screensaver()
  File "/usr/lib64/python3.12/site-packages/pyanaconda/screensaver.py", line 96, in inhibit_screensaver
    inhibit_id = session_proxy.Inhibit("anaconda", "Installing")
                 ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/dasbus/client/proxy.py", line 161, in __getattr__
    member = self._get_member(self._get_interface(name), name)
                              ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/dasbus/client/proxy.py", line 211, in _get_interface
    self._handler.specification.members
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/dasbus/client/handler.py", line 212, in specification
    self._specification = self._get_specification()
                          ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/dasbus/client/handler.py", line 332, in _get_specification
    xml = self._call_method(
          ^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/dasbus/client/handler.py", line 435, in _call_method
    self._message_bus.connection,
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/dasbus/connection.py", line 169, in connection
    self._connection = self._get_connection()
                       ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/dasbus/connection.py", line 336, in _get_connection
    return self._provider.get_session_bus_connection()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/dasbus/connection.py", line 67, in get_session_bus_connection
    return Gio.bus_get_sync(
           ^^^^^^^^^^^^^^^^^
gi.repository.GLib.GError: g-io-error-quark: Could not connect: No such file or directory (1)

Comment 2 a.trubitsyn 2023-12-03 16:29:46 UTC
Created attachment 2002720 [details]
anaconda log from /tmp

Comment 3 a.trubitsyn 2023-12-03 20:21:10 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=2248914 with LXDE.iso
https://bugzilla.redhat.com/show_bug.cgi?id=2248929 with similar error on Fedora-Workstation-39-1.5-x86_64.iso
https://bugzilla.redhat.com/show_bug.cgi?id=2249011 with Fedora-Workstation-39-1.5-x86_64.iso

Comment 4 Katerina Koukiou 2023-12-14 13:54:25 UTC
*** Bug 2248914 has been marked as a duplicate of this bug. ***

Comment 5 Neal Gompa 2023-12-15 01:25:55 UTC
anaconda-liveinst is an EPEL only package that just ships a launcher file. Reassigning back to anaconda.

Comment 6 Alessio 2024-01-02 20:13:11 UTC
*** Bug 2256507 has been marked as a duplicate of this bug. ***

Comment 7 Alessio 2024-01-02 20:14:29 UTC
Open the terminal and issue this command:
sudo dbus-launch liveinst

Could it be a workaround?

Comment 8 Kamil Páral 2024-01-03 12:19:33 UTC
(In reply to Alessio from comment #7)
> Open the terminal and issue this command:
> sudo dbus-launch liveinst

I can confirm that makes the installer start on F39 (Final) LXDE Live iso.

Comment 9 Katerina Koukiou 2024-01-15 19:01:10 UTC
Probably this is a fix, did not test it: https://pagure.io/fedora-kickstarts/pull-request/1013

Comment 10 Geraldo Simião 2024-03-11 19:28:25 UTC
Well, PR closed and no fix. 
Fedora-LXDE-Live-x86_64-40-20240306.n.0.iso still have this bug.

Comment 11 Kamil Páral 2024-03-22 09:18:34 UTC
Confirmed, still present in F40 Beta.

Comment 12 a.trubitsyn 2024-03-23 16:11:34 UTC
Yes. Fedora-LXDE-Live-x86_64-40-20240322.n.0.iso still have this bug.

Comment 13 Glenn Johnson 2024-05-02 07:14:43 UTC
Can confirm that the bug still exists and that the proposed workaround, sudo dbus-launch liveinst, works well.

Comment 14 Geraldo Simião 2024-09-12 20:08:25 UTC
Just tested the new Fedora-LXDE-Live-x86_64-41_Beta-1.2.iso and it seems the bug is fixed now because if we click on the install icon anaconda starts correctly and the system gets installed.

Comment 15 Kamil Páral 2024-09-17 08:49:43 UTC
(In reply to Geraldo Simião from comment #14)
> Just tested the new Fedora-LXDE-Live-x86_64-41_Beta-1.2.iso and it seems the
> bug is fixed now because if we click on the install icon anaconda starts
> correctly and the system gets installed.

I can confirm that. Great, let's close this.


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