Issue when making heavy use of Linutil with Ubuntu 24.04

[Lurchicus]

Describe the bug

I wish I could be more detailed on the exact steps to reproduce this (too many steps to isolate the cause). The symptom, after making heavy use of the stable release of Liinutil, then restarting, When I get the password prompt, enter my password and press return, it flickers and goes back to the login screen (the one with my name). All attempts fron then on don't allow me to login (including a restart and dropping to root and changing my password. The machine I'm using is a Dell XPS-9320 laptop that I bought with Ubuntu installed. The end result, I have to do a full reinstall of Ubuntu 24.04.

To Reproduce

Steps to reproduce the behavior:

1. Run an update/upgrade and restart
2. Run the stable release of Linutil via the curl command in github
3. Install a LOT of stuff with Linutil
4. Restart the system
5. Login and password screen loop endlessly with my not being able to log in.

Expected behavior

After entering the password, go to the Gnome desktop (Wayland)

Screenshots

Nothing to see here (see 4 above)

Additional context

My system only has the Intel built-in GPU, 32 GB of RAM, a 2TB NVME SSD, an external 4TB hard drive (for backups), a docking port that supplies an external keyboard, mouse, two additional screens, a wired net connection, headphone/mic (Blackwire), and the backup drive. Running a 13th gen I7 (i7-1360P).

I did not try the dev branch as it take a long time to reinstall and configure the system

Checklist

• I checked for duplicate issues.
• [ X} I checked already existing discussions.
• [X ] This issue is not included in the roadmap.
• [ ?] This issue is present on both stable and development branches.

[Lurchicus]

Things that don't appear to break Ubuntu 24.04:

• Bash prompt
• Docker
• FastFetch
• Timeshift backup

[Lurchicus]

One of these broke Ubuntu 24.04 (as described above):

• Github Desktop
• Meld
• Discord
• Zoom (install failed)

Back to rebuilding my system again.

[adamperkowski]

Well, that's unexpected. The scripts you listed above are very unlikely to "break" the system in that capacity.

---

GitHub Desktop setup uses gpg but does not check if it's installed. (that should be fixed, redirecting to other contributors)

---

Meld Setup does this weird thing for some reason:

linutil/core/tabs/applications-setup/Developer-tools/meld-setup.sh

Lines 5 to 8 in a9a678f

	installMeld() {
	cd "$HOME" && git clone https://gitlab.gnome.org/GNOME/meld.git
	echo "PATH=\$PATH:$HOME/meld/bin" | "$ESCALATION_TOOL" tee -a /etc/environment
	}

I don't think that this could be the issue here though.

---

Discord script (for Ubuntu) downloads and installs the deb package so that couldn't be an issue.

---

And Zoom. The script for Zoom uses flatpak (incorrectly - #705) so it in theory should:

1. check for flatpak and install it
2. install zoom from flathub

---

Now for the flatpak script, it's just garbage in my opinion. Half of the code is pure 100% bloat.

I'm really sorry this happened to you. I don't see any direct issue that could cause that...

Most of the scripts you listed are by @guruswarupa I think.

[adamperkowski]

I will try to recreate this in a VM.

[Lurchicus]

I'm going to take one more pass through the last four with a restart between each one.

Just FYI, this doesn't seem to bother my Linux Mint Cinnamon system (latest version) or my WSL2 24.04 install... until my windows system (11 pro) ate it's boot sector.

Also by trade I'm a (retired) C#/SQL server developer, but except for games and WinForm development, I've become more and more focused on Linux.

[adamperkowski]

I'm going to take one more pass through the last four with a restart between each one.

Okay, let me know how it went.

this doesn't seem to bother my Linux Mint Cinnamon system (latest version) or my WSL2 24.04 install... until my windows system (11 pro) ate it's boot sector.

Yeah, typical for windows.
I'm not up to date with the mint stuff but I heard they're trying to go Debian-based. I assume yours is still on Ubuntu, right?

[Lurchicus]

Looks like Meld is the issue, for my system anyway. Have not checked Discord or Zoom yet. Git Desktop was fine (and all the others I mentioned).

It may not have any bearing, but I'm using Chrome, not Firefox.

Also I'm running 3 laptops with Ubuntu 24.04, Linux Mint Cinnamon (11th Gen i7) and Debian 12 (old XPS i7-3517U). Windows 11 pro is on a desktop with an i9-10900K (with Winutils run on it... I'm still rebuilding this system... reinstalling software).

[Lurchicus]

Just FYI, Meld did not affect my Debian 12 laptop. I'm not going to try my Linux Mint system for now.

[adamperkowski]

Okay. #644 got merged today. The only thing that IMO could be an issue with the meld script got refactored. We do not have a new prerelease yet so the change won't be present on precomplied versions but you can build linutil from source (from the main branch) and check if it still persists if you want to.

[guruswarupa]

Describe the bug

I wish I could be more detailed on the exact steps to reproduce this (too many steps to isolate the cause). The symptom, after making heavy use of the stable release of Liinutil, then restarting, When I get the password prompt, enter my password and press return, it flickers and goes back to the login screen (the one with my name). All attempts fron then on don't allow me to login (including a restart and dropping to root and changing my password. The machine I'm using is a Dell XPS-9320 laptop that I bought with Ubuntu installed. The end result, I have to do a full reinstall of Ubuntu 24.04.

To Reproduce

Steps to reproduce the behavior:

1. Run an update/upgrade and restart
2. Run the stable release of Linutil via the curl command in github
3. Install a LOT of stuff with Linutil
4. Restart the system
5. Login and password screen loop endlessly with my not being able to log in.

Expected behavior

After entering the password, go to the Gnome desktop (Wayland)

Screenshots

Nothing to see here (see 4 above)

Additional context

My system only has the Intel built-in GPU, 32 GB of RAM, a 2TB NVME SSD, an external 4TB hard drive (for backups), a docking port that supplies an external keyboard, mouse, two additional screens, a wired net connection, headphone/mic (Blackwire), and the backup drive. Running a 13th gen I7 (i7-1360P).

I did not try the dev branch as it take a long time to reinstall and configure the system

Checklist

• I checked for duplicate issues.
• [ X} I checked already existing discussions.
• [X ] This issue is not included in the roadmap.
• [ ?] This issue is present on both stable and development branches.

Well am sorry to hear that! But yes the scripts I made doesn't seem to break things at that level.

[Lurchicus]

Okay. #644 got merged today. The only thing that IMO could be an issue with the meld script got refactored. We do not have a new prerelease yet so the change won't be present on precomplied versions but you can build linutil from source (from the main branch) and check if it still persists if you want to.

I believe I will run the dev branch and only try installing Meld. If there are no issues, I will close this with a reference to #644

[Lurchicus]

I ran the Meld install (it didn't report any errors), from the Linutil dev branch, it's still munging Ubuntu 24.04 on my system. I'm going to reinstall Ubuntu, but I'll wait for the next release (or until someone wants me to test a fix specific for this issue). I'll keep checking in (though it will be sometime tomorrow before I get the system going again... I just don't have another reinstall/rebuild in me tonight).

Duh, I just read your comment that the fix isn't in the named dev branch. talk about a perfect shot to the foot! For my next trick, I'll clone the actual dev branch, compile and run from that version and try Meld again... tomorrow. :)