241·
5 days agoThey actually got a GTK3 based release out before GTK3 went EOL. Congratulations!
Can they update ti GTK4 based before that goes EOL? :D
Linux enthusiast, family man and nerd
- 0 Posts
- 132 Comments
Joined 2 years ago
Cake day: August 24th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
Just to clarify. You system is not bricked. Bricked means that it can’t boot anything. It sounds like the update is not working correctly (eg the kernel is not fully loading).
You have two options:
- Try to repair the current broken install (can be difficult depending on skill level)
- Backup your data and “nuke’n’pave”, eg re-install it all.
Both options require a live USB with your distro on it (preferably the new version).
There seems to be links to some learning materials for it at the website.
https://www.lpi.org/our-certifications/lpic-1-overview/
As it is just a test (multiple choice and written text) I don’t think there are any preperation tests for it.
understand why this post has such a negative vote count when the conditions for its existence seems like an acceptable risk since it’s disconnected from the internet;
The OP says nothing about being disconnected from the internet. The referenced guide uses a computer without internet, but not OP.
So it’s fair to assume OPs PC is still connected to the internet, as must devices are these days.
So, they are kind of like Linux Live USB sticks with persistant storage?
I had something similar happen in Plasma 6.1 and 6.2. After I turned off the dccutils support in powerdevil, I have not had the issue since. My desktop is not a laptop, so it’s always powered, same with screen, so I don’t need fancy power profiles.
If firefox is still in /usr/lib64/firefox, then it should still be there. Maybe just the .desktop file is removed?
Quote from https://www.reddit.com
KDE is officially a community dedicated to developing FOSS software. It’s legally represented by the KDE e.V. and the KDE Free Qt Foundation. The latter is to ensure that the dual-licensed Qt software used by KDE stays open source.
KDE Plasma is the desktop environment made by KDE. It’s sometimes called just KDE because, duh, it shorter. The apps included in Plasma are also made by the KDE (also see KDE Gear).
There’s the KDE Frameworks, built on top of Qt.
Plasma mobile is a distribution for mobile devices.
KDE Neon is a “distribution” showcasing the lastest KDE software.
It depends on how the network is setup, I suppose. I don’t know how AWS does things, but I would imagine that the Windows Desktop is set to be on the same network/subnet as the compute node you ssh into. Else the node would be accessible by anyone on the internet for brute forcing.
Maybe it’s a dangling dependency process that keeps crashing.
yeah, €1500 for an i7 with 32 GB RAM and 1 TB SSD is just a bit too high compared to a ThinkPad that runs linux pretty well. :D
Didn’t know about this vendor.
Looking at their page the prces look a bit steep for me.
You asked for a graphical date and time settings app to use instead of gnome-system-tools. You didn’t mention that you needed the other functionality from gnome-system-tools whatever that may be…
They started doing that in a couple of years back. Saw quite a bit of backlash in the Linux news media at the time.
I know of a small application, that’s part of a larger suite if you want it. It’s called CoreTime.
It’s Qt based, but the dependency list is quite small.
Might have to reboot for the polkit agent to be started.
It is maintained by Bitwarden, it is up to date and it is official/verified:
Why not just describe it?
Video is not searchable.
I’m not a Kubuntu expert or even user, so I will just list op the general steps.
Boot into the live USB and unlock the encrypted drive. Make sure you have an internet connection too. Then chroot (change root) into the OS drive you decrypted and look at the logs from last update or even boot logs if posisble to determine what went wrong during the update. If possible fix the issue and complete a full update again (apt update & apt upgrade). Hopefully that should fix it.
Does your PC have any known hardware that requires proprietary drivers, like Nvidia or Broadcom?