this is one of those questions better asked in debian forums if they still haven't released it
Debian will have the new KDE when they do their massive update, otherwise there is the testing and unstable branch to look and see if they have it there.
Unlike snaps and flatpaks, Appimages aren’t containerized or sandboxed at all. They are only used to bundle (some) dependencies, so you don’t need to rely on packages provided by your distro’s package manager.
You might want to look up what Appimages are as well as what containerization is. To help I have found the following.
AppImage aims to be an application deployment system for Linux with the following objectives: simplicity, binary compatibility, portability, distro agnosticism, no installation, no root permission, and keeping the underlying operating system untouched.
As stated Appimages are containerized/sandboxed as it prevents needing to install any files on the OS.
Containerized applications are applications run in isolated packages of code called containers. Containers include all the dependencies that an application might need to run on any host operating system, such as libraries, binaries, configuration files, and frameworks, into a single lightweight executable.
Source: https://cloud.google.com/discover/what-are-containerized-applications
As you can see, once again, your info is incorrect as this is another example of what Appimages are.
The thing about snaps and app image is they are containerized. The idea behind that is to help keep the apps separate from the main file subsystem by sandboxing them from each other as well as not cluttering your hdd with different versions of the same libraries to make them work.
Because of the sandboxing, once you close the app it stops running in the background therefore there is nothing to get notifications from.
IMHO, this is why snap and app image programs are not advisable for programs you may need notifications from on a, generally, required/needed basis.
As for superconductivity, the only way around that problem is to download from source, compile it and let it run natively on your system in the background, or add it to you auto startup list so it is running at boot time.
My father is one of them. Because of his idiotic glorification and idol worship of trump, my family has told him to fuck off. Haven’t talked to him for almost 3 years now. He even believed the big lie
Ponzi schemes, especially the insurance companies. They really are a Ponzi scheme.
Think about it, they promise you things asking for money, then when you need their services they decide where you go, how much they will pay (leaving the rest for you to pay as a deductible), then they turn around and increase your costs for their services, that they fight tooth and nail not to pay anything.
This is a database script i made to trigger when database events trigger a database lockup.
# Make sure to change your database info and what instance of DB you are using (i.e. sqlite3, mysql, postgres etc...)
# This script will rotate for a total of 5 logs so you can compare previous errors with current one without taking unnecessary space
# There's no strict requirement to place it in the root directory of the server, but you have some options for where to put it:
# Root Directory: Placing the script in the root directory could work, but it's generally not recommended to clutter the root directory
# with scripts. It's better to create a specific directory for your application and put the script there.
# Custom Directory: Create a specific directory for your application, and place the script there.
# For example, you could create a directory called "my_app" or "database_error_logger" and place the script in that directory.
# Scripts Directory: Some servers have a designated directory for executable scripts.
# You might check if your server has a "scripts" directory where you can place your script.
# Regardless of the location, it's essential to consider file permissions.
# Ensure that the script has the necessary permissions to execute. You may need to use the chmod command to set the appropriate
# permissions, depending on your server's configuration.
# Lastly, consider setting up a virtual environment for your Python script to isolate dependencies and avoid conflicts with other
# applications on the server. This can help ensure that the required Python libraries are installed locally for your script
# without interfering with system-wide packages.
# This script was created by Edward Freeman and is covered under GPL V3. You can modify this script as you need
# However, you must retain this GPL V3 standard, and leave credit where credit is due to the original author.
import logging
from logging.handlers import RotatingFileHandler
import sqlite3 #Make sure you change this to the correct Database provider (sqlite3, mysql, postgres etc..)
import sys
# Configure logging with rotating file handler
log_file = 'database_errors.log'
log_handler = RotatingFileHandler(log_file, maxBytes=1024 * 1024, backupCount=5)
log_formatter = logging.Formatter('%(asctime)s - %(levelname)s: %(message)s')
log_handler.setFormatter(log_formatter)
logger = logging.getLogger('DatabaseErrorLogger')
logger.setLevel(logging.ERROR)
logger.addHandler(log_handler)
def perform_database_operation():
try:
# Replace the following line with your actual database connection and query
connection = sqlite3.connect('your_database.db')
cursor = connection.cursor()
# Replace the following line with your actual database operation
cursor.execute('SELECT * FROM your_table;')
# Don't forget to commit the changes if you are performing write operations
connection.commit()
connection.close()
except Exception as e:
# Log the error with the traceback using the logger
logger.exception("Error occurred while performing the database operation.")
raise # Raising the error again allows the script to terminate or handle it at a higher level if needed
def custom_exception_handler(exctype, value, traceback):
# Log uncaught exceptions using the logger
logger.exception("Uncaught exception occurred.", exc_info=(exctype, value, traceback))
# Set the custom exception handler for uncaught exceptions
sys.excepthook = custom_exception_handler
# Call the function to perform the database operation
try:
perform_database_operation()
except Exception as e:
print("Error occurred during the database operation:", str(e))
Thanks for this system, already like the looks a little better than I expected. Also thank you for this post for us newbies to the fediverse.
view more: next ›
This is nice thanks for sharing