openSUSE

Amaterasu , in openSUSE Tumbleweed Monthly Update - May 2024

This is awesome work. Tons of necessary updates.

Archaeopteryx OP , in openSUSE Tumbleweed Monthly Update - May 2024
@Archaeopteryx@kbin.run avatar

There is still an issue that the update want delete the steam package because of a broken dependency.

2 Problems:
Problem: 1: the installed calibre-7.4.0-2.3.x86_64 requires 'libQt6Gui.so.6(Qt_6.7.0_PRIVATE_API)(64bit)', but this requirement cannot be provided
deleted providers: libQt6Gui6-6.7.0-2.2.x86_64

Problem: 2: the installed steam-1.0.0.79-1.4.x86_64 requires 'glibc-locale-base-32bit', but this requirement cannot be provided
deleted providers: glibc-locale-base-32bit-2.39-7.1.x86_64


Problem: 1: the installed calibre-7.4.0-2.3.x86_64 requires 'libQt6Gui.so.6(Qt_6.7.0_PRIVATE_API)(64bit)', but this requirement cannot be provided
deleted providers: libQt6Gui6-6.7.0-2.2.x86_64

 Solution 1: Following actions will be done:
  keep obsolete libQt6Gui6-6.7.0-2.2.x86_64
  keep obsolete libQt6Core6-6.7.0-2.2.x86_64
  keep obsolete libQt6DBus6-6.7.0-2.2.x86_64
  keep obsolete libQt6OpenGL6-6.7.0-2.2.x86_64
  keep obsolete libQt6Widgets6-6.7.0-2.2.x86_64
 Solution 2: deinstallation of calibre-7.4.0-2.3.x86_64
 Solution 3: break calibre-7.4.0-2.3.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c): 2

Problem: 2: the installed steam-1.0.0.79-1.4.x86_64 requires 'glibc-locale-base-32bit', but this requirement cannot be provided
deleted providers: glibc-locale-base-32bit-2.39-7.1.x86_64

 Solution 1: deinstallation of steam-1.0.0.79-1.4.x86_64
 Solution 2: keep obsolete glibc-locale-base-32bit-2.39-7.1.x86_64
 Solution 3: break steam-1.0.0.79-1.4.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c): 

But it looks like there is a fix already in testing.

Archaeopteryx OP ,
@Archaeopteryx@kbin.run avatar

The issue is resolved.

Maragato , in Aeon Desktop Brings New Features in RC2 Release
@Maragato@lemmy.world avatar

Excellent news about Aeon and the development of an own installer. The last time I installed Aeon it didn't allow automatic user login, is this possible anymore? Thanks

sugar_in_your_tea OP ,

I haven't used it, but this post implies that it should work:

edit /etc/sysconfig/displaymanager and put your username in DISPLAYMANAGER_AUTOLOGIN="username"

sugar_in_your_tea , in openSUSE Community Readies for Release Party

I'm excited for this one. It seems to be the last 15.X release until whatever openSUSE ALP does. I'm probably going to switch my servers to MicroOS, but I'm happy that I get another year or so with 15.6.

Congrats on the hard work everyone! I'm out of town for the release, but I might upgrade my VPN server remotely to join in a little.

sugar_in_your_tea , (edited ) in Leap 15.6 Unveils Choices for Users

Woo! Good work to everyone involved!

I'm excited to update, and will be playing with MicroOS in the meantime.

Edit: Just upgraded my NAS and VPS a few days ago and everything went smoothly. Good release everyone!

Archaeopteryx OP ,
@Archaeopteryx@kbin.run avatar

Yeah. Will do the update on my server playground today :)

dogsnest , (edited ) in How to block applications from accessing the Internet
@dogsnest@lemmy.world avatar

First Solution Works

Also:

Firejail

eta: Firejail is available in most distros' repos.

The last reply in THIS thread includes a simple bash script to launch restricted apps.

Archaeopteryx ,
@Archaeopteryx@kbin.run avatar

Firejail is great. I can recommend it.

RelativeArea0 , in How to block applications from accessing the Internet

Heres my lazy and probably stupid way (im a nub btw)

  1. Only install flatpak apps.
  2. Install flatseal and manage every app using that.

Cons: might be a problem to manage if you got like 1000+ flatpak apps installed

sandalbucket , in How to block applications from accessing the Internet

Use network namespaces :)

A brand new network namespace doesn’t have any network interfaces. When you start a process in a namespace, all its child processes will start there too. It’s like a little network jail, and the functionality is baked into the kernel / is kernel enforced.

I use this to keep certain processes on a vpn, with no need for interface-binding support from the process, or a vpn-killswitch.

Another fun fact, this is the functionality that enables containerization, like docker/podman

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • [email protected]
  • All magazines