Lx 4.3 build 230 live iso: Plasma environment not starting

Development Development Testing
1

Hello,

I’m testing the latest iso on an asus netbook P1504 U.

Unfortunately, while it boots without any problem before starting the desktop environment, Plasma launch is stuck during splash screen.

I can have acces to a shell, so I could launch the debug script.

omv-bug-report.txt (292.8 KB)

1 Like
2

Better you try with this ISO.

1 Like
3

In journal:

Sep 19 14:05:04 kernel: SQUASHFS error: zstd decompression error: 14
Sep 19 14:05:04 kernel: SQUASHFS error: zstd decompression failed, data probably corrupt
Sep 19 14:05:04 kernel: SQUASHFS error: Failed to read block 0x7368b67f: -5
Sep 19 14:05:04 kernel: SQUASHFS error: Unable to read data cache entry [7368b67f]
Sep 19 14:05:04 kernel: SQUASHFS error: Unable to read page, block 7368b67f, size 1dc0
Sep 19 14:05:04 kernel: SQUASHFS error: Unable to read data cache entry [7368b67f]
Sep 19 14:05:04 kernel: SQUASHFS error: Unable to read page, block 7368b67f, size 1dc0
Sep 19 14:05:04 kernel: SQUASHFS error: Unable to read data cache entry [7368b67f]
Sep 19 14:05:04 kernel: SQUASHFS error: Unable to read page, block 7368b67f, size 1dc0
Sep 19 14:05:04 kernel: SQUASHFS error: zstd decompression error: 14
Sep 19 14:05:04 kernel: SQUASHFS error: zstd decompression failed, data probably corrupt
Sep 19 14:05:04 kernel: SQUASHFS error: Failed to read block 0x7368b67f: -5
Sep 19 14:05:04 kernel: SQUASHFS error: zstd decompression error: 14
Sep 19 14:05:04 kernel: SQUASHFS error: zstd decompression failed, data probably corrupt
Sep 19 14:05:04 kernel: SQUASHFS error: Failed to read block 0x7368b67f: -5
Sep 19 14:05:04 kernel: SQUASHFS error: zstd decompression error: 14
Sep 19 14:05:04 kernel: SQUASHFS error: zstd decompression failed, data probably corrupt
Sep 19 14:05:04 kernel: SQUASHFS error: Failed to read block 0x7368b67f: -5

That looks like either corrupted media or a corrupted download. I get this sometimes if I download using a browser downloader instead of downloading in terminal. Or sometimes this just happens for reasons I can not explain. To download ISO’s I always check checksum files and I use this:

$ aria2c -c -m 0 http://example.com/file.iso

2 Likes
4

Since build 230 is what we have up on SourceForge I just tested it:

  1. Fresh download using aria2c
  2. Check checksums - OK
  3. Used ISO Image Writer to copy .iso file to a flash drive
  4. Boot Legacy and UEFI on Ryzen5 desktop and boot UEFI on ASUS X550C notebook - OK in all instances (noting whether login sound works, it did)
  5. Connect to wifi - OK in all instances
  6. Open Calamares installer and navigate to the page where my partitions are listed - OK in all instances
  7. Check that a few things in Application Menu and OM-Welcome open.

In recent history we have not been seeing any problems with installing in “normal” circumstances. So it is believed to be most likely that installing would not be a problem.

The build 275 ISO @rugyada posted and the most recent Rolling/Lx 4.3RC ISO build 347 have undergone the same testing and were also OK.

1 Like
5

It seems also that Sourceforge is not providing Md5 or SHA1 sums, so I could not check if the iso was OK…

edit: well now I can see the icon which provides additional information, yesterday it was not the case, I can swear…