search

pop-os / iso

Pop!_OS ISO production
Other
498 stars 65 forks source link

Pop!_OS 24.04 ISO tracking issue (amd64) #326

Closed XV-02 closed 3 months ago

XV-02 commented 6 months ago

This Issue is for tracking issues with the initial release ISOs for the 24.04 derived release of Pop!_OS.

Edit this checklist as bugs are found and resolved. Create individual posts in this issue for each bug as it occurs. (Checkmarks are no longer problems)

Outstanding Issues:

Resolved

XV-02 commented 6 months ago

Resolved

ISO requires network:

While attempting to do an install on actual hardware without a network connection, the install errors out and fails.

I've attached a copy of the install logs:

The first installer.log looks truncated by the installer dying during the install attempt.

The second Install_attempt_02.log was pulled directly from the terminal output while running sudo -E io.elementary.installer

When I connect to wi-fi the install progressed smoothly, however.

Additionally, network connection of not, the install progresses smoothly on a virtual machine.

XV-02 commented 6 months ago

ISO doesn't land in live-user session reliably

When launching the live session, I have only seen the live disk drop into the live-user session once.

In general, the process gets caught up on the login screen for cosmic-greeter. There is no obvious way to launch a session from the login screen.

I'm not sure if that is due to the pop-os user not having a password, or if it is similar to an on-going issue where cosmic-greeter will hang after entering the user password and trying to launch a session. diagnostically, it looks the same at first blush.

My current workaround is to open a separate TTY (usually tty4 via ctrl + alt + F4 ), login using the pop-os user, and launch cosmic-session directly before proceeding.

This needs further investigation.

XV-02 commented 6 months ago

Resolved

Installer doesn't auto-launch

This issue was highlighted by @jackpot51

Currently, the workaround is to launch the installer from the terminal using sudo -E io.elementary.installer

This will be needed for the 24.04 release ISO.

XV-02 commented 6 months ago

Resolved

Cannot boot encrypted install

While the encrypted install itself seems slightly unstable, when successfully completed, the system does not boot to a decrypt prompt of any kind afterwards.

This requires additional investigation.

WatchMkr commented 6 months ago

Flathub remotes aren't installed

jackpot51 commented 6 months ago

Flathub remotes aren't installed

This would require running xdg autostarts.

XV-02 commented 5 months ago

Testing against debug 137 on laptops (serw13, darp10):

Negatives:

  1. The ISO still fails to launch the live user session consistently. I had to restart cosmic-greeter from a TTY to get the session to start correctly. I think this is a more correctly a cosmic-greeter issue.
  2. UI is uncomfortably small on high resolution displays. I wonder if we should dynamically set scaling in the ISO? Cosmic-randr will return display dimensions and selected resolution, so we can ballpark PPI, especially on laptops.
  3. Attempting to boot results in a Kernel Panic from a missing file during init. This is blocking the ability to test the installed OS. IMG20240618102804

Positive:

XV-02 commented 5 months ago

Resolved

Testing debug 137 on a Thelio Major R4 with a 3060ti, I am seeing different behaviour.

For the Nvidia ISO, cosmic-greeter attempts but fails to start. Output for systemctl status cosmic-greeter.service (log file) Output from sudo dmesg (log file) Output from journalctl -b 0 (log file)

On a separate attempt, I noticed that the nvidia-powerd.service unit had also failed, so I pulled logs for that too: ISO137N_cosmicgreeterservice2.log ISO137N_dmesg2.log ISO137N_journal2.log ISO137N_nvidiapowerdservice2.log

For the Intel ISO, cosmic-comp starts, but the system is completely unresponsive. This behaviour was also seen on a Thelio R3 with GeForce 1050.

XV-02 commented 4 months ago

Testing debug 145, the desktop issues persist, but appear to be Nvidia specific. The behaviour is unchanged.

On a Mira B4 with an RX 6600 XT, the ISO successfully reaches a GUI session, auto-launches the installer, and installs.

Flathub remotes are present on a clean install.

XV-02 commented 4 months ago

No initial setup equivalent

From a feature-parity perspective, we don't have anything like gnome-initial-setup right now.

Some configuration with GIS might not be needed right now: dock preferences, workspace/app-library buttons, clock position, dark/light mode, location services, online accounts.

But, two configurations jump out right away as missing: time-zone selection, and wi-fi setup.

This is a UX question ultimately, and should probably have an application design drafted.

XV-02 commented 4 months ago

Resolved

The previously observed issues for Nvidia ISO are still present in Nvidia debug ISO 168.

Intel debug ISO 168, however, can successfully complete an encrypted install.

I did note that the mouse cursor did not have a consistent size when interacting with different elements in the installer. Most notably, the text-input cursor was super-sized when I was clicking into the password fields. This is a cosmetic issue only, as functionality seem fine.

thomas-zimmerman commented 3 months ago

Eddy is not installed to handle 'deb' file installs. Currently "file roller" tries to open them.

sund3RRR commented 1 month ago

Segfault when trying to select disk for installation

Intel/amd image. Tech specs: CPU: AMD Ryzen 7 5700x GPU: AMD Radeon RX 6700XT

Sep 26 18:23:15 pop-os sudo[14587]: pam_unix(sudo:session): session closed for user root
Sep 26 18:23:15 pop-os kernel: sd 7:0:0:0: [sdb] Unaligned partial completion (resid=4060, sector_sz=512)
Sep 26 18:23:15 pop-os kernel: sd 7:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
Sep 26 18:23:15 pop-os kernel: sd 7:0:0:0: [sdb] Unaligned partial completion (resid=4060, sector_sz=512)
Sep 26 18:23:15 pop-os kernel: sd 7:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
Sep 26 18:23:15 pop-os kernel: sd 7:0:0:0: [sdb] Unaligned partial completion (resid=4060, sector_sz=512)
Sep 26 18:23:15 pop-os kernel: sd 7:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
Sep 26 18:23:15 pop-os kernel: sd 7:0:0:0: [sdb] Unaligned partial completion (resid=4060, sector_sz=512)
Sep 26 18:23:15 pop-os kernel: sd 7:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
Sep 26 18:23:15 pop-os kernel: sd 7:0:0:0: [sdb] Unaligned partial completion (resid=4060, sector_sz=512)
Sep 26 18:23:15 pop-os kernel: sd 7:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
Sep 26 18:23:15 pop-os kernel: sd 7:0:0:0: [sdb] Unaligned partial completion (resid=4060, sector_sz=512)
Sep 26 18:23:15 pop-os kernel: sd 7:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
Sep 26 18:23:15 pop-os kernel: sd 7:0:0:0: [sdb] Unaligned partial completion (resid=4060, sector_sz=512)
Sep 26 18:23:15 pop-os kernel: sd 7:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
Sep 26 18:23:15 pop-os kernel: io.elementary.i[14528]: segfault at 10 ip 0000725936606178 sp 00007ffd10b9b460 error 4 in libdistinst.so[7259365e7000+29b000] likely on CPU 14 (core 6, socket 0)
Sep 26 18:23:15 pop-os kernel: Code: 48 bf 02 00 00 00 05 00 00 00 e8 33 cd ff ff 48 c7 44 24 08 00 00 00 00 48 c7 44 24 10 08 00 00 00 48 c7 44 24 18 00 00 00 00 <49> 8b 46 10 48 85 c0 0f 84 96 00 00 00 4d 8b 66 08 4c 69 e8s 88 02
Sep 26 18:23:15 pop-os systemd[2895]: app-cosmic-io.elementary.installer-14506.scope: Consumed 3.183s CPU time.
Sep 26 18:23:16 pop-os sudo[14601]:   pop-os : TTY=pts/1 ; PWD=/home/pop-os ; USER=root ; COMMAND=/usr/bin/journalctl -e
Sep 26 18:23:16 pop-os sudo[14601]: pam_unix(sudo:session): session opened for user root(uid=0) by pop-os(uid=1000)