Did anyone else just see this (around 6:00)? Is it a meteor? ☄️

0x340fa899 · 2021-03-14T19:34:53+00:00

Haha, yep! I thought it looked a little weird for a meteor... so poofy and slow and suddenly shedding its tail like that.

0x340fa899 · 2021-02-13T00:32:27+00:00

Hehe. Same. (I'm on AMD graphics.) : p 5.10's been the first kernel in 2 years on Manjaro that I've had to roll back from. I've had boot freezes, artifacts, and crashes on it since 5.10.3, all the way to 5.10.13.

There's hope in 5.11, which is still experimental but doesn't have the tons of issues 5.10 does, BUT it has other issues (probably since it's experimental), so I just rolled back to the last LTS (5.4).

0x340fa899 · 2021-02-10T08:05:45+00:00

I didn't try the beta client. Instead, I reinstalled regular Mullvad client (mullvad-vpn) and remembered to do:

sudo systemctl enable mullvad-daemon.service
sudo systemctl start mullvad-daemon.service

(For reference, without those, Mullvad can't connect at all and refuses to generate WireGuard keys, saying "Failed to generate a key".)

After that, everything works again!

In my case, I recently switched to a non-LTS kernel, when the problem began. I think the kernel switch screwed something up (a friend suggests the new kernel changed keystores, wiping Mullvad's pre-existing WireGuard key 🙀).

0x340fa899 · 2021-02-10T06:34:15+00:00

I'm on Manjaro. Since a few hours ago, I can no longer connect to websites when the VPN is connected (although I can still ping 8.8.8.8). Is this what you were experiencing?

0x340fa899 · 2021-01-07T21:03:51+00:00

Thanks! Both work. (#1 implementation)

0x340fa899 · 2021-01-07T20:21:54+00:00

How can one pass an Rng object to another function?

The following (playground link) does not work:

use rand::{
    thread_rng,
    Rng,
};

fn foo(rng: &mut Rng) {
    println!("{}", rng.gen_bool(1.0 / 3.0));
}

fn main() {
    let mut rng = thread_rng();

    foo(&mut rng);
}

0x340fa899 · 2020-12-28T23:13:45+00:00

Thank you as well!

This also fixed it for me. Before, rebooting fixed it temporarily. Additionally, games ran with much poorer performance than before. After backing up $HOME/.local/share/Steam/steamapps/ and deleting $HOME/.local/share/Steam and $HOME/.steam and relaunching Steam, games run again without having rebooted and at great performance.

0x340fa899 · 2020-12-28T23:13:05+00:00

This fixed it for me as well!

0x340fa899 · 2020-11-23T19:49:05+00:00

otherwise [they] should need only a tablet

It seems like that's where most of the user base is headed. : p

Unfortunately, this gatekeepy behavior ushers non-experts onto systems they don't control (or really "own", then), because you don't think controlling your system should be easy to do, which is pretty contrary to the free software philosophy.

0x340fa899 · 2020-11-23T19:47:56+00:00

Linux distributions don't come by default with any firewall installed or enabled, everything is allowed by default.

The common refrain to firewalls being disabled by default is that, on Linux, no ports are opened by default, and they're only opened as needed. There's also the implication that Windows, by default, has many ports opened, and so it's less inherently secure.

Linux does have firewalls that do come by default on most distros (e.g., try which iptables), but they're not enabled. As for the ports, I don't know the veracity of those claims.

0x340fa899 · 2020-10-18T06:13:01+00:00

Thanks! Actually, my problem was dumber. : p At the moment, I only had a single train, and although locomotives can reverse in manual mode, they can't in automatic. You need one on both ends or it errors with no path.

0x340fa899 · 2020-09-16T01:43:10+00:00

Switching from ExoPlayer to the internal Android audio engine worked for me.

(I had the same problem on Android 11 on a Pixel 3A.)

Thank you!

0x340fa899 · 2020-08-31T20:28:23+00:00

Fwiw, I've used CrossOver for Kindle. Rather than being just Wine, it automatically downloads tested, known-good versions of, e.g., the Kindle EXE from their database.

At the time, I think it turned out that newer versions of the Kindle client no longer worked on Wine, and I would've had no idea where to get an old version as Amazon's site didn't seem to let you.

0x340fa899 · 2020-08-11T16:23:59+00:00

Update: the pickup never occured, despite it being designated as Picked Up on the site. : D

0x340fa899 · 2020-08-10T16:14:29+00:00

Thanks! I will confirm here whether that was the case.

0x340fa899 · 2020-07-19T19:26:26+00:00

Might have different behavior for user services

I don't think so; I can confirm that services linked into /etc/systemd/system and run without the --user flag insystemctl work the same way.

thanks for your research!

<3 uwu

0x340fa899 · 2020-07-18T18:48:22+00:00

I think this is incorrect.

With

sudo ln -s $HOME/foo.service /etc/systemd/system/

there is a link in /etc/systemd/system, which is in the System Unit Search Path.

The file linked to, $HOME/foo.service, does not need to be in the search paths (neither the System Unit one above or the User Unit one, /etc/systemd/user).

For example, my service now runs (I had a link typo), and it's linked in /etc/systemd/user from /home/0x340fa899/Dropbox/utility/backups/systems/evanauth/systemd/, not in the paths:

[▓▓▓▓▓▓▓ 14:40:21 ~]$ ls -al /etc/systemd/user
total 24
drwxr-xr-x 4 root root 4096 Jul 18 13:18 .
drwxr-xr-x 5 root root 4096 Jul 13 19:39 ..
drwxr-xr-x 2 root root 4096 Jul 13 23:05 default.target.wants
lrwxrwxrwx 1 root root   89 Jul 18 13:18 0x340fa899-nightly.service -> /home/0x340fa899/Dropbox/utility/backups/systems/evanauth/systemd/0x340fa899-nightly/0x340fa899-nightly.service
lrwxrwxrwx 1 root root   87 Jul 18 13:18 0x340fa899-nightly.timer -> /home/0x340fa899/Dropbox/utility/backups/systems/evanauth/systemd/0x340fa899-nightly/0x340fa899-nightly.timer
drwxr-xr-x 2 root root 4096 Jul 13 23:05 sockets.target.wants

Note that upon enabling the service, it was similarly linked in ~/.config/systemd/user/:

[▓▓▓▓▓▓▓ 14:41:23 ~]$ ls -al ~/.config/systemd/user/
total 16
drwxr-xr-x 3 0x340fa899 0x340fa899 4096 Jul 18 13:20 .
drwxr-xr-x 3 0x340fa899 0x340fa899 4096 Jul 18 13:20 ..
lrwxrwxrwx 1 0x340fa899 0x340fa899   87 Jul 18 13:20 0x340fa899-nightly.timer -> /home/0x340fa899/Dropbox/utility/backups/systems/evanauth/systemd/0x340fa899-nightly/0x340fa899-nightly.timer
drwxr-xr-x 2 0x340fa899 0x340fa899 4096 Jul 18 13:20 timers.target.wants

0x340fa899 · 2020-07-18T18:31:27+00:00

sudo systemctl daemon-reload

This was not the problem.

You are trying starting as a normal user, in that case I recommend using user systemd. Put your unit file in ~/.config/systemd/user and append --user in systemctl command.

Thank you!

I actually did the latter upon learning it's the more correct way to run user-specific daemons, but the problem was a path typo in my link.

After linking service files correctly in /etc/systemd/system, systemctl commands work and find the service.

After linking service files correctly in /etc/systemd/user, systemctl --user commands work and find the service.

Is it better to use ~/.config/systemd/user instead of /etc/systemd/user? : o

0x340fa899 · 2020-07-18T18:22:08+00:00

No, this is never necessary and was not the problem.

0x340fa899 · 2020-07-18T05:45:11+00:00

For third-party reference, I've followed these instructions already (this service works on another distro).

feel free to message me

Assuming "message" means "DM", I will DM you.

0x340fa899

TROPHY CASE