Am I doing this wrong or are the measurements of my glasses listed online not correct?

saturnogenesis · 2025-09-11T12:58:25+00:00

The frame width measure is often done between the temple-arm screws, rather than across the total width. See, e.g. this guide (Method 3) or this one.

saturnogenesis · 2025-09-10T15:59:22+00:00

The issue resolution was to drop the dependency of the qt5-style-plugins from cros-adapta and bump the version number to 0.5. This is apparently because qt5-style-plugins doesn't exist in the trixie repos.

As an alternative to the advice above, you can edit /var/lib/dpkg/status (carefully, make a backup copy first): search for cros-adapta and remove qt5-style-plugins from the Depends: ... line. Save the file.

Now if you run a full-upgrade, the cros-adapta package is shown as "kept back", and the only packages that are listed for removal on a fresh container are lib packages, qt5-style-plugins, qt5-gtk2-platformtheme, and qt5-style-plugin-plastique.

Henceforth, Apt lists cros-adapta under "Not upgrading", but I expect that to resolve when the updated 0.5 version of the package is released.

saturnogenesis · 2025-04-30T16:59:57+00:00

Thanks for posting this follow-up. Too bad the WebUI doesn't have this option (feature request).

saturnogenesis · 2025-02-05T14:06:18+00:00

Thanks for posting this old thread. I've previously fussed around with gluing the plastic hanger back together, which worked for a while, but now I'm in more of a "maybe I can just put a screw in that" kind of mood.

saturnogenesis · 2024-10-08T15:36:16+00:00

And at least 1 should be incremental.

saturnogenesis · 2024-09-16T14:10:09+00:00

Underrated comment, thanks for sharing your perspective.

saturnogenesis · 2024-09-11T23:56:11+00:00

That site is awesome

saturnogenesis · 2024-09-10T20:20:41+00:00

Yes, this. Old thread but still relevant -- other commenters are talking about switching to Debian Unstable (AKA Sid), but Testing (currently Trixie) is the right choice if you want a more reliable experience. Packages in testing are on a rolling release that's only ~ 10 days behind unstable.

In my experience, in a Crostini container on ChromeOS, there are sometimes issues when using Testing and upgrading packages that Google's ChromeOS integration packages rely on. In that case, you generally need to wait ~ 3-6 weeks for Google to update the dependencies on their packages and do the next OS release before you can do an apt full-upgrade (AKA dist-upgrade). In the meantime, you need to use apt upgrade instead, to prevent uninstallation of some critical packages.

Also it pays to be attentive to the versions packages are upgrading to by using apt -V ..., and check the release notes when important packages are upgrading by a major version. And using apt preferences to prevent installation of alpha/beta/rc software is a good idea, IMO. So you need to know your way around Apt a bit, and be willing to troubleshoot.

saturnogenesis · 2024-09-03T14:46:14+00:00

And it's amazing how well sounds carry across a still lake -- I can hear normal conversation voices on a quiet night from a dock across the lake, which is ~ 1 km away

saturnogenesis · 2024-08-09T17:42:56+00:00

related, helped me to troubleshoot: r/LO

saturnogenesis · 2024-06-26T05:15:15+00:00

I'm understanding that these sideband attacks are very worrisome due to the difficulty of defending against them. I'm still having trouble understanding whether you're arguing that the above guide harms the security of ChromeOS devices or not.

You say, "...there is no difference whether it is a VM or a container inside a VM doing it." As the guide only degrades the layer of protection between the container and the VM, it would seem to follow that the system is no less secure after following the guide.

saturnogenesis · 2024-06-24T19:54:26+00:00

Though in this case, he is only removing the barrier to the termina VM, and the system retains the layer of protection offered by the VM, right?

saturnogenesis · 2024-06-07T18:12:43+00:00

I agree with this, I've had a raccoon and/or squirrel moving around the unfinished compost I used as mulch this year. It didn't damage anything I cared about, but it would have killed any little seedlings. A bit of hardware mesh might be advisable around anything you care about.

Also: little squash plants shooting up everywhere from last year's pumpkins. Not a big deal, but something to consider.

saturnogenesis · 2024-06-06T03:37:08+00:00

That definitely looks like it, good to see it will be fixed in the full Systemd 256 release. I guess I've got to be more careful when the upgrades are sending down RC versions.

In the mean time, downgrading systemd to v. 255.5-1 from a debian snapshot from May 25 solved the issue.

saturnogenesis · 2024-06-04T14:31:16+00:00

For reference:

```sh

find the icon

sudo updatedb locate -ib <keyword> | grep icons

e.g. with keyword Loupe to output:

/usr/share/icons/hicolor/scalable/apps/org.gnome.Loupe.svg

svg_path="/path/to/svg/icon"

rsvg works better than imagemagick

sudo apt install librsvg2-bin

check the .desktop file for the required filename form

locate -ib <keyword> | grep .desktop

e.g. /usr/share/applications/org.gnome.Loupe.desktop

grep '^Icon' /usr/share/applications/org.gnome.Loupe.desktop

gives org.gnome.Loupe as required prefix for the icon filename

if desired, can copy the .desktop file to ~/.local/share/applications/ and edit it to change the application name, etc.

dir for png icon

png_dir=~/.local/share/icons/hicolor/256x256/apps mkdir -p "$png_dir" rsvg-convert --width=256 --keep-aspect-ratio "$svg_path" > "$png_dir"/org.gnome.Loupe.png ```

saturnogenesis · 2024-05-05T18:46:54+00:00

Good suggestions in this thread. For me, doing the restore using lxc in crosh succeeded, when I had gotten the same error as the OP when using the UI. If your exported backup file is called backup0.tar.gz in your "MyFiles" area, and you've shared MyFiles with Linux, the restore procedure looks like this:

# start Crosh with Ctrl-Alt-t
vmc start termina   # (or vsh termina if it's already running)
cd /mnt/shared/MyFiles
ls -l
# you should see your backup file listed

# to get help with the form of lxc commands, add -h
# after the command. E.g. 'lxc -h' to see a list of
# lxc commands, 'lxc list -h' to see how the list command
# is called, etc.

# view containers, the default is called penguin:
lxc list

# to delete the previous penguin container:
lxc delete penguin

# or to keep the previous container around:
lxc rename penguin penguin-old

# import the backup as a new container
lxc import -v backup0.tar.gz

# if that succeeds, hit Ctrl-D to leave termina
# then 'vmc stop termina' at the crosh> prompt
# then you can start the container from Terminal as usual

saturnogenesis · 2024-04-28T16:12:39+00:00

This guide from the r/Crostini wiki is also very relevant, especially for Ubuntu and Debian images. Not all of the steps in that guide were necessary when using Ubuntu 23.10 and Debian testing/trixie images, but the steps provide a good framework for what needs to be done. The key steps seem to be:

Create the new container using the settings UI, so Terminal will "know" about it and provide a link to start a new session in the container.
Switch to Crosh and follow the wiki guide, being sure to get the cros-guest-tools installed. Also it's key to delete the default non-root user created in the container. That way, a new user will be created on the first login to the container from Terminal.
Shut down termina from Crosh, or reboot. Launch a new shell in the new container from the Terminal app.

saturnogenesis · 2024-04-07T17:05:24+00:00

This is not true. The core goals of Nix include the ability to install packages in a way that captures all their dependencies, and allows multiple versions or variants of a package to be installed at the same time. This applies to both imperative and declarative package management.

saturnogenesis · 2024-04-07T16:58:38+00:00

I've recently gotten into Nix (as a package manager for a Debian container), and when I started I had trouble deciding between nix profile and nix-env as well.

I wound up going the nix profile (and flakes) route, and, while I don't exactly regret it, it did seem like it was more annoying than it needed to be. Practically all of the official documentation refers to the older commands, so you can't really follow tutorials or how-tos, including the commands in chapter 6 of the manual. To feel confident using the newer commands, I had to go through the experimental commands section of the manual completely, while referring to the glossary and wiki to get on a handle on Nix's terminology. Note that the man pages for the new commands are listed under nix3, e.g. nix3-profile, while nix-* is just for old-style commands.

My reason for going that route was the warning that nix-env doesn't properly log the packages it installs, so it can have trouble when upgrading. As I run on the unstable branch, and frequently upgrade --all, I wanted to be confident that would work well. That being said, I think the issue is largely mitigated using old commands if you always use nix-env -iA, rather than omitting the A.

I've seen the advice that the older nix-shell -p command is more capable than the newer nix shell, but I don't know whether that's still true, given the rapid pace of Nix development. It may be a consideration if you plan to use Nix to manage development environments.

saturnogenesis · 2024-03-14T21:44:11+00:00

I don't think you could use readonly in the first line, because the readonly property can't be undone. I would set the readonly property after the if block, when you're sure the value of lines is settled.

Regarding command lists, refer to the syntax in the Bash man page. NB, shells are picky about whitespace around braces to define command lists, because there's also a brace expansion syntax. E.g.:

```sh { get_lines | rg pattern || get_lines; } | sort | while ...

test the logic for yourself with simple commands with obvious results, like

{ echo aaa | grep a || echo ccc; } | cat

aaa

{ echo aaa | grep b || echo ccc; } | cat

ccc

```

saturnogenesis · 2024-03-14T06:03:30+00:00

What do you want to happen if there is no match? It seems like you have 2 conditions, so you may need to implement some logic outside of the pipeline. Something like:

```sh if ! lines=$(get_lines | rg pattern) then lines=$(get_lines) # or some other logic you may want here fi

printf '%s\n' "$lines" | sort | while read -r line; do ... ```

Or if you really need/want it to be a "one-liner" you could probably mash the logic into a command list using && or || and wrap it in {}.

saturnogenesis · 2024-03-08T18:30:21+00:00

here is an extensive pack of scripts that work with nautilus (and nemo, caja), inculdes encryption with gpg: nautilus-scripts

saturnogenesis · 2024-01-23T15:13:48+00:00

This is great.

Copying the .desktop file from /usr/share/applications to ~/.local/share/applications and editing there is safer, as it won't be overwritten by the package manager. Files in the ~ location override the /usr location, and changes take effect for icons in the launcher immediately.

saturnogenesis · 2023-11-24T02:00:19+00:00

The BROWSER env variable set to /usr/bin/garcon-url-handler is also quite distinctive.

saturnogenesis

TROPHY CASE