mastodon.world is one of the many independent Mastodon servers you can use to participate in the fediverse.
Generic Mastodon server for anyone to use.

Server stats:

8.5K
active users

#justlinuxthings

0 posts0 participants0 posts today
Replied in thread

@peppe thaks man... it feels good, as I'm on the suck train for a while now 😅

Since I've switched themes, LightDM stopped working, and I can't log in until I first log in on an other TTY in text mode... Apparently opening the #LightDM greeter settings app screwed everything up? Now I'm looking for an alternative, but nothing else seem to support a "switch user" type feature?

#justLinuxThings I guess...

smh

After lots and lots of waiting and trying out multiple different things regarding single window recording in #OBS :obs: on #Wayland :wayland: running #labwc :labwc: there is now a solution in place I can work with.

I wrote a wrapper script (see here) that does the following things when added as #pipemenu in labwc and I click the menu entry to create the output.

  1. Add a virtual output
  2. Use wlr-randr to set the geometry
  3. Use swaybg to set the wallpaper
  4. Send an update signal to a custom #Waybar module

I can now start #OBS and can add a #PipeWire screen recording and select the output (I have to do it blindly by just moving the cursor outside my actual display, because there is no menu, but that’s fine).

For what I’m doing the performance of the OBS preview is fast enough so I simply move the cursor over to the virtual output and use it “inside OBS”.

When I’m done, I invoke the script again, by clicking the remove entry which is dynamically shown if the output is active.

  1. Remove the output
  2. Remove “the output’s swaybg instance”
  3. Send an update signal to a custom Waybar instance

Until individual-window recording will be possible this is a good workaround.

#JustLinuxThings #ModernLinuxProblems #SharingIsCaring #scripting #Luanti #MinetestGame

//cc @whynothugo (thanks) @LXQt (thanks, too)

I never was a fan of this, but removing packages that are not explicitly installed and that are not dependencies of other packages is quite satisfying when the list contains packages with "weird" or "random" names. Also cleaning up Pacman cache is nice.

pacman -Rns $(pacman -Qtdq)
pacman -Scc
Continued thread

Upon further investigations I unintentionally set up #Howdy to work with the regular video camera and not the IR sensor/blaster. I have since rectified the situation, with the help of the ‘linux-enable-ir-emitter’ utility.

[tldr]: TIL: sudoedit

I never ever was a fan of sudo because I like having my accounts properly and strictly separated. If I want to do root stuff, I become root using su -l. (And in general I will continue handling it like this in the future.)

Since my distribution’s package build system has it as hard dependency, I have sudo installed. It’s configured to never cache anything and always only ask for the root password, with no further “real” configuration. I am the only use on the system, so I don’t care about running tasks as different user (and if so, it’s the root account).

Defaults rootpw
Defaults timestamp_timeout=0
dirk ALL=(ALL) ALL

… this allows the package creation process to run properly. At a specific point I enter my root password and that’s fine. Under normal circumstances I just use su -l.

But since I recently had to configure a lot of files outside my home directory I always had the problem of a fully unconfigured editor. No proper syntax highlighting, my key combinations, etc. all not present (I prefer leaving root as unconfigured as possible).

Then I found sudoedit.

It runs in my normal environment, with all my configuration but allows me to edit files outside my $HOME. I can just replace nvim /etc/foo.bar with sudoedit /etc/foo.bar and enter the root password and then edit the file as if it was a file in my environment.

It sometimes worth leaving your comfort zone to explore new things.

//tagged: #JustLinuxThings #TIL #commandline #sudo #sudoedit #changes

My laptop had this weird issue where periodically start garbling all audio into like a weird metallic tone? It would just randomly crop up and off now and then, so I assumed it was like a hardware issue

today I decided to search for it just in case, and wow.

it turns out there's some software called speach-dispatcher? idk what it does, but apparently whenever it gets activated it screws up audio.

#justlinuxthings omg fml I hate linux so much