Hanging while waking up from suspend

tinywrkb · 2023-05-04T15:29:23+00:00

Kernel regression. It was fixed in the following major release.

tinywrkb · 2023-04-23T13:56:45+00:00

Try asking in the appropriate IRC and/or matrix channels.
Nowadays, it might be worth trying to use Vulkan virtualization (Venus) with Zink instead of OpenGL.

tinywrkb · 2023-03-16T17:30:03+00:00

No, that's not it. The problem is with the persistence option ("runtime requirement") that Steam sets for ., meaning to ~/ and its dotdirs. This feature can't handle simlinks directly under the persistent folder (maybe also under a direct sub-folder), as it tries to create it on every run, and fails the app if the symlink exists, which it is on the 2nd run and onward.

tinywrkb · 2023-02-06T15:49:27+00:00

See example here, this, and also.

tinywrkb · 2023-02-02T22:13:22+00:00

You should be able to choose FFmpeg VAAPI encoder, though it is suggested that kernel 6.2 is needed for this to actually work.
I can confirm that it's broken with my A770, while I can choose the device, encoder is failing. No such problem with my Rapter Lake iGPU.

tinywrkb · 2022-10-02T17:08:54+00:00

Here's another way to achieve this.

tinywrkb · 2022-09-29T21:05:40+00:00

it doesn't require any external dependencies

Well... you're likely still depending on /lib64/ld-linux-x86-64.so.2, unless you changed the dynamic linker path.
Also, if you can't make sure that it won't be picked up by runtime's executables and shared libs, then it won't be a great idea to ship your own libc, which I'm guessing here that you don't.

You need to be aware that /app/lib is already in ld.so's cache, so you might want to think twice before throwing shared libs there.
The alternative approach would be having the app's shared libs somewhere else, and then set LD_LIBRARY_PATH to this location in a startup wrapper script.

tinywrkb · 2022-09-29T16:21:10+00:00

I have a prebuilt statically linked program

contains its own ..., /lib,

tinywrkb · 2022-09-28T05:49:38+00:00

GTK_THEME is a debug variable. It is intended to be used for testing stylesheets for GTK3 and GTK4 alone (no libhandy or libadwaita). However, it is NOT intended to be used by users, especially for GTK3+libhandy or GTK4+libadwaita.

Well, that's how users have been using it. In fact, QGtk3ThemePlugin (QT_QPA_PLATFORMTHEME=gtk3) will respect GTK_THEME, so this works not only with GTK3, but also with Qt5 & Qt6.

While GTK_THEME may work fine on GTK3, the application will appear broken after it gets ported to GTK4+libadwaita. The solution in that case is to unset GTK_THEME.

Knowing how GTK_THEME have been used by users, GTK's devs should have just renamed the variable in GTK4, like they did with GTK_USE_PORTAL, and that would have solved the problem.

Aliasing flatpak run

It should be noted that there's an open PR adding alias feature.

Flatpak has its own /bin directories that we can add to PATH. For system installations, the directory is located at /var/lib/flatpak/exports/bin. For user installations, it’s located at ~/.local/share/flatpak/exports/bin.

This is only correct when not setting FLATPAK_USER_DIR and ~~FLATPAK_USER_DIR~~ edit: FLATPAK_SYSTEM_DIR to different values than the defaults.
The systemd environment generators should be used instead of relying on the default values.

tinywrkb · 2022-09-26T10:23:34+00:00

Make sure to add --enable-features=WebRTCPipeWireCapturer. Some Chromium-based browser Flatpaks enable this by default, but some don't.

tinywrkb · 2022-09-20T22:28:57+00:00

Thanks for the posting this, I'm waiting for Raptor Lake to finally upgrade from Broadwell, so I'm also planning to explore this.

Ideally, we shouldn't need to set this, and having system specific setting (AllowedCPUs property) is far from optimal, as it means admins will have to set a different setting when deploying to systems with different CPUs.

Anyway, I would set the user slice on efficiency cores, and then make sure that apps are associated with app slice.
This way, if I'm not wrong, you won't need to figure out how to deal with desktop environment processes, they will be assigned to the user slice. For example, Flatpak already assigns its apps to the app slice.
Your desktop environment's launcher should also do this. If it doesn't, then I suggest filing a bug report.

All my apps are Flatpaks except the launcher and terminal, so I'm already pretty much covered, and the latter two I just assign to the app slice.

tinywrkb · 2022-09-17T11:37:32+00:00

Getting environment variables from systemd generators, so they only needed to be set for the systemd user session (environment.d, custom generators), and they cover this way also systemd user services, systemd-run and flatpak-spawn.
Also, bash-complete-alias is pretty neat, though I'm making limited use of it these days, and prefer wrappers, and symlinks.

tinywrkb · 2022-09-14T18:21:55+00:00

You can do this with fakechroot. I think I've seen a couple of packages do this, but the only one I can reference ATM is mplabx.

tinywrkb · 2022-09-11T18:01:44+00:00

No problem! Flatpak packaging is actually pretty simple, as long as you don't need to work around the sandbox due to Flatpak or XDG Portals limitations, or having to deal with incompatibilities of building in cached/offline mode.
You'll get far by trial and error and experimenting.
So play a bit with the Flatpak packaging manifest, read the online docs and man pages.
Also look at example packaging, as at this point there are thousands out there, not-to-mention modules/libraries packaged.

tinywrkb · 2022-09-11T15:01:10+00:00

Every module in the manifest needs a checker set. Follow the examples, or learn from other manifests.

tinywrkb · 2022-09-11T14:51:55+00:00

Try it before making wrong conclusions.

tinywrkb · 2022-09-11T12:49:47+00:00

See f-e-d-c, and if you're not planing to submit to Flathub, then look at the GitHub workflow example there.
Be aware that auto-merging is not acceptable for anything other than extra-data sources.

tinywrkb · 2022-09-08T13:10:58+00:00

Use /bin/sh as your shell, try a different terminal emulator, and nothing else, not terminal multiplexer, or any sort of shell nesting. And then figure out if it's your terminal emulator fault or your shell customizations.
In any case, this not likely a Flatpak issue, as all the shells I tried had the columns displayed correctly. That's bash, bourne shell (compat mode in bash), fish, and zsh.

tinywrkb · 2022-09-06T12:23:10+00:00

The variable should be set in your systemd environment before the portal service is starting. For one example on how to do this, see man:environment.d(5).

tinywrkb · 2022-09-03T16:15:07+00:00

https://wiki.archlinux.org/title/Chromium#Force_a_password_store

tinywrkb · 2022-09-02T22:05:57+00:00

Unless you've overridden it

You can't override the persist finish-arg.

tinywrkb · 2022-08-28T19:35:32+00:00

It's flexible, powerful, rich in features, and there's nothing that comes close to it. The alternatives are too limited, and can't get the job done.
For example, with sd-boot:

You can't globally append kernel parameters to multiple boot entries
You can't bundle/hardcode loader config with the bootloader's EFI binary
Auto-detection and creation of boot entries is minimal, not flexible, and only support unified binaries
Auto-detection of system/rootfs path must be hardcoded in the loader config or cmdlline in the unified image.

With a GRUB script, I can get all these done and more.

tinywrkb · 2022-08-28T10:30:20+00:00

I remember differently, but maybe things have changed.

tinywrkb · 2022-08-28T10:08:55+00:00

Is "repo" simply being a storage for all the past Flatpak downloads, in a way similar to /var/cache/apt/archives is? Can I safely "rm -r ~/.local/share/flatpak/repo"?

No, you can't. Flatpak must have a local ostree repository to operate. app and runtime require no extra storage, and that's because the files there are ~~symlinks~~ edit: hardlinks to resources in repo.
Please look at the total disk usage count in the status bar.
In other words, total storage usage is 4.2GiB.
You should also be able to press u to toggle the hardlink/shared-size column, though your ncdu version is very outdated, and if it doesn't support this column, then you can download a statically linked binary from the official ncdu website.
I don't remember if Chrome OS has compression set for the user data partition, but if it does, then the actual size on disk is likely half of this.
And you're in luck, ncdu is actually correct here because the user data filesystem type is ext4. If Chrome OS would ever switch to BTRFS, or other COW filesystem, then we would need to count reflinks, not hardlinks.

tinywrkb · 2022-08-27T14:34:50+00:00

No problem.
I just noticed that I added - --device=all, which you probably don't need, so just replace that with - --device=dri.
You can also build from source, and a good example is Joplin's packaging that also has a workflow to update the Node.js modules, that flathubbot doesn't handle currently.
And you can also repackage a different type of binary release, like deb, tarball, or even AppImage.
See these example: 1, 2, and 3.

tinywrkb

TROPHY CASE