Created attachment 1872592 [details] automated core dump Trying to investigate the problems presented in https://ask.fedoraproject.org/t/how-do-i-tell-fedora-to-use-the-i915g-driver-instead-of-i915/20618/ I was trying to install Fedora 36 Beta from the LiveUSB onto a spare hard drive on the test machine, which sports an Intel Core 2 Quad CPU and the corresponding chipsets, which I think is GMA 3100 but is considered i945 or i965 or something that actually uses the i915 line of graphics drivers. So, I wanted to try installing, the problem is... I can't, because Anaconda just gives me a black screen on app startup, even though it's GTK3 and not GTK4. Running it with `sudo anaconda` yields the same result, it hangs on a black screen. No errors in the terminal, only these warnings: ``` [liveuser@localhost-live ~]$ sudo anaconda Starting installer, one moment... anaconda 36.16.2-4.fc36 for anaconda bluesky (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 ** (anaconda:5029): WARNING **: 11:09:43.882: AT-SPI: Could not obtain desktop path or name ** (anaconda:5029): WARNING **: 11:09:44.554: atk-bridge: GetRegisteredEvents returned message with unknown signature ** (anaconda:5029): WARNING **: 11:09:44.554: atk-bridge: get_device_events_reply: unknown signature ** (anaconda:5029): WARNING **: 11:09:44.554: atk-bridge: get_device_events_reply: unknown signature ``` Then the app hangs, can't be stopped from the UI, this is what happens when ctrl+C'ing the terminal: ``` ^C Exception ignored in atexit callback: <function exitHandler at 0x7fb0c47f3d90> Traceback (most recent call last): File "/usr/sbin/anaconda", line 56, in exitHandler anaconda.payload.unsetup() File "/usr/lib64/python3.10/site-packages/pyanaconda/payload/dnf/payload.py", line 247, in unsetup self._configure() File "/usr/lib64/python3.10/site-packages/pyanaconda/payload/dnf/payload.py", line 306, in _configure self._dnf_manager.configure_base(self.get_packages_configuration()) File "/usr/lib64/python3.10/site-packages/pyanaconda/payload/dnf/payload.py", line 186, in get_packages_configuration self.proxy.PackagesConfiguration File "/usr/lib/python3.10/site-packages/dasbus/client/proxy.py", line 164, in __getattr__ return member.get() File "/usr/lib/python3.10/site-packages/dasbus/client/property.py", line 43, in get return self.__get__(None, None) File "/usr/lib/python3.10/site-packages/dasbus/client/property.py", line 54, in __get__ return self._getter() File "/usr/lib/python3.10/site-packages/dasbus/client/handler.py", line 376, in _get_property_value variant = self._call_method( File "/usr/lib/python3.10/site-packages/dasbus/client/handler.py", line 444, in _call_method return self._get_method_reply( File "/usr/lib/python3.10/site-packages/dasbus/client/handler.py", line 477, in _get_method_reply return self._handle_method_error(error) File "/usr/lib/python3.10/site-packages/dasbus/client/handler.py", line 486, in _handle_method_error raise error File "/usr/lib/python3.10/site-packages/dasbus/client/handler.py", line 474, in _get_method_reply result = call(*args, **kwargs) File "/usr/lib/python3.10/site-packages/dasbus/client/handler.py", line 57, in sync_call return connection.call_sync( gi.repository.GLib.GError: g-io-error-quark: The connection is closed (18) ``` If I try to run it as root (with su and then anaconda), I get an instant crash on startup, without having to do anything: ``` [liveuser@localhost-live ~]$ su [root@localhost-live liveuser]# anaconda Starting installer, one moment... anaconda 36.16.2-4.fc36 for anaconda bluesky (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 ** (anaconda:4791): WARNING **: 11:08:44.520: Binding '<Shift>Print' failed! Anaconda received signal 11!. /usr/lib64/python3.10/site-packages/pyanaconda/_isys.so(+0x1578)[0x7fd9c426a578] /lib64/libc.so.6(+0x42ae0)[0x7fd9d332fae0] /lib64/libxklavier.so.16(+0x114c5)[0x7fd9adc6c4c5] /lib64/libgobject-2.0.so.0(+0x23dff)[0x7fd9c4f90dff] /lib64/libgobject-2.0.so.0(g_object_new_valist+0x165)[0x7fd9c4f926a5] /lib64/libgobject-2.0.so.0(g_object_new+0x9d)[0x7fd9c4f92bbd] /lib64/libxklavier.so.16(xkl_engine_get_instance+0x41)[0x7fd9adc67101] /lib64/libAnacondaWidgets.so.4(+0xb8a5)[0x7fd9adc838a5] /lib64/libgobject-2.0.so.0(g_type_create_instance+0x239)[0x7fd9c4fa90f9] /lib64/libgobject-2.0.so.0(+0x23ef8)[0x7fd9c4f90ef8] /lib64/libgobject-2.0.so.0(g_object_new_with_properties+0x261)[0x7fd9c4f92141] /lib64/libgobject-2.0.so.0(g_object_new+0xc1)[0x7fd9c4f92be1] /lib64/libAnacondaWidgets.so.4(+0xc012)[0x7fd9adc84012] /lib64/libgobject-2.0.so.0(g_type_create_instance+0x1fb)[0x7fd9c4fa90bb] /lib64/libgobject-2.0.so.0(+0x23ef8)[0x7fd9c4f90ef8] /lib64/libgobject-2.0.so.0(g_object_newv+0x261)[0x7fd9c4f924a1] /lib64/libgtk-3.so.0(+0xd942b)[0x7fd9af8c242b] /lib64/libgtk-3.so.0(+0xd9a0f)[0x7fd9af8c2a0f] /lib64/libgtk-3.so.0(+0xda7a1)[0x7fd9af8c37a1] /lib64/libglib-2.0.so.0(+0x58c0c)[0x7fd9c5048c0c] [New LWP 4792] [New LWP 4793] [New LWP 4913] [New LWP 4915] [New LWP 4919] [New LWP 4920] [New LWP 4924] This GDB supports auto-downloading debuginfo from the following URLs: https://debuginfod.fedoraproject.org/ Enable debuginfod for this session? (y or [n]) [answered N; input not from terminal] Debuginfod has been disabled. To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x00007fd9d33ce71f in wait4 () from /lib64/libc.so.6 Saved corefile /tmp/anaconda.core.4791 [Inferior 1 (process 4791) detached] ``` The coredump file found in /tmp is attached.
Created attachment 1872593 [details] Anaconda log found in /tmp
Created attachment 1872594 [details] screenshot of an Anaconda in total darkness
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. 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 '36'. 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 36 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 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 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.