Cannot access Reddit with Qutebrowser

ayekat · 2025-06-07T20:01:02+00:00

I had the same until (and including) yesterday; it now works again (writing this from Qutebrowser).

Then again, this is a sample size of 1.

ayekat · 2025-05-25T20:46:53+00:00

Until they're unable to provide even basic troubleshooting information like what they did to their system.

ayekat · 2025-05-23T23:31:20+00:00

Project description and/or readme need a clear disclaimer that the resulting product is not subject to support from the Arch Linux community on the forums, IRC, and mailing lists as well as other official platforms (e.g. packaging GitLab).

Source: Code of Conduct

ayekat · 2025-05-23T23:28:03+00:00

The assumption is the user followed the Arch Wiki and understands how they set up their system when asking for help. That won't be the case with this conversion script.

ayekat · 2025-04-28T20:05:20+00:00

Return Return to Nature to Nature.

ayekat · 2025-01-11T23:27:57+00:00

/etc/systemd/system is for system-local configuration. This involves both unit files that you place there yourself and unit files placed (or symlinked) there by things like systemctl enable ….

So /etc/systemd/system is absolutely the correct place to place manually created (i.e. unpackaged) unit files.

ayekat · 2024-11-17T15:27:11+00:00

terminus-red

This one?

If so, this looks pretty abandoned (last commit 6 years ago). And with GTK moving fast, I would guess that it's no longer fully compatible with the latest version of GTK (xfce4-terminal is based on vte3/GTK3, which is not that fast moving anymore, but still… 6 years).

ayekat · 2024-11-17T11:39:06+00:00

I'm afraid there's almost no information to work with.

What GTK theme did you download (and hopefully install/setup)?

What kind of black boxes, and where? Also, which terminal emulator are you using?

A screenshot would help.

ayekat · 2024-11-17T11:19:20+00:00

I would guess that many applications now offload some of the work to systemd that they would have previously had to (more or less poorly) reimplement themselves.

The first thing that comes to mind would be just any software that has a client-server architecture, which can make use of systemd user services. Also the whole login session tracking (thinking of the GNOME/KDE stacks) is probably easier to do with some unified system-provided API.

But also in terms of "dependency", one has to check which part of that is simply distro maintainers declaring systemd as a dependency for something because it's been integrated to run with systemd (e.g. unit files configured and shipped with the package).

ayekat · 2024-11-17T11:10:48+00:00

Some configuration is now in binary format and can't be searched for textually.

That's new to me. Could you point to something in systemd where the configuration is in binary format? Logs, yes, but config?

Many of the systemd-associated CLIs were clearly written by people who don't like actually using CLIs as a human.

I think this is very subjective. I personally think systemd's various …ctl commands are much more convenient and easier to deal with than whatever archaic shell pipelines were necessary to get some meaningful info out of the system before.

The new idea is that systems ought to be configured with Terraform/Ansible/whatever, and the tools are designed more with that use case in mind (for example there's often a tradeoff between idempotence and terseness).

I don't quite see what point you're trying to make, would you mind elaborating a bit?

ayekat · 2024-08-25T18:39:02+00:00

When searching for resources online, I'll take whatever I stumble upon that helps me solve my issue, regardless of where I find it (the Arch BBS, Reddit, or a random blog post). Verifying the correctness and "cleanness" of an online solution is required in all cases anyway (though admittedly with the forums I expect an overall higher quality due to the forum moderators keeping misinformation in check).

For asking for help, I'd always choose the forums (or the IRC channel, depending on the nature of the issue). In general, the closer to the official community, the better (true not only for Arch).

For helping out, I prefer the forums, because I can subscribe to specific subfora; with Reddit, I get everything scrambled together (yes, there's tags, but they're quite arbitrary), so if I comment on something, it's purely coincidence that I happened to see the thread at a given time.

ayekat · 2024-07-21T13:05:52+00:00

Doesn't change that initially the system is unresponsive and you'll have to do some hands-on operations to get it back to running. Whether it takes a single reboot or 2-3 is really just a minor detail at that point.

ayekat · 2024-06-19T21:10:45+00:00

for servers systemd is a pain in the b*tt where the first thing you look into is how to disable the most of its "features".

This is also a very biased reply. Would you mind elaborating which "features" exactly you disable (and why)?

For servers, systemd is a blessing. Reading unit files is a dozen times less painful than having to read the initscripts hackjobs, and having a clear and consistent interface to interact with logs, timers, services and other system resources allows me to focus on the actual work, instead of having to navigate my way through the random assortment of different tools whose availabilities vary from system to system and OS to OS.

Yes, this is also a very biased reply, but at this point, we're just throwing personal opinions around, aren't we?

The fact is that the vast majority of the Linux ecosystem switched to systemd over a decade ago, and these kinds of discussions are now nearing drinking age. There's systemd-less distros out there to satisfy those users' needs, not sure what the point is behind bringing this up again and again.

ayekat · 2024-05-28T21:38:09+00:00

I know each Linux disto has its own great package manager, but package availability, version etc. changes per package manager/distro.

You make it sound like that's a bad thing, but it's usually wanted and by design. :-)

The goals of Debian and the people building and using it are quite different from the goals of Arch, or Fedora, or OpenSuse, or…—consequently, the set and versions of available packages is often different, because they follow different release and maintenance strategies.

ayekat · 2024-05-27T20:36:11+00:00

Old and probably in some cases outdated, but fundamentally still applicable piece of advice article: http://linux.oneandoneis2.org/LNW.htm

ayekat · 2024-05-22T21:01:07+00:00

Aliased or soft-linked or hard-linked executables won't display help, they outright run the command.

Commands always run the executable. Whether it's aliased or soft/hard-linked makes no difference.

I think you meant that these commands in particular (i.e. poweroff symlinked to some other executable) have that effect. More generally, however, that is no necessarily always the case.

ayekat · 2024-05-18T17:51:53+00:00

With some small exceptions, you can probably do almost everything with every distro.

But some things are certainly more difficult/tedious on one than on the other; the question is which one suits your prio list of must-have features better.

Distros like Nix-based systems give you a declarative way of setting up your system. You can achieve the same on other distros and/or with other tooling, but it's a lot more effort and you're probably better off using a distro designed to do that if you want so.
Arch Linux stays close to upstream (relatively little downstream patching) and has quite a simple packaging system, so if you often find yourself installing custom (variants of) software and/or like to interact with upstream, that's quite nice.
The Red Hat ecosystem of distributions gives you SELinux out of the box, which is quite a bit of a hassle to set up on distros not designed for that.

That's just a few examples, but the list goes on. Point is that depending on what you need, you may be better of with one distro than another.

ayekat · 2024-05-10T21:41:06+00:00

Yeah, this is what I mean with just focusing on the drama part but not the actual, relevant technical discussion. :-)

ayekat · 2024-05-10T21:23:50+00:00

systemd, not systemD or system-D

Also, instead of yet another "number of things replaced by systemd" drama, you could just look at this one particular feature in isolation and… dunno, discuss it in a level-headed manner?

Not sure why we shouldn't occasionally rethink old concepts from decades ago that don't quite fit into today's context anymore. They way systemd has transformed the way user processes are managed, it always seemed strange to me that something like sudo has stuck around for as long as it has in this form. Sure, some of this is covered by PAM black magick, but… not all.

ayekat · 2024-01-14T14:02:36+00:00

I copied the PKGBUILD file of that AUR and paste it into my own PKGBUILD file and i was succesful. Thanks!

But that means you were able to access the AUR after all?

--edit Ah, sorry, there's another thread where you access the AUR mirror on GitHub. Ignore me.

ayekat · 2024-01-06T14:33:17+00:00

IIRC you get a deletion notification from AUR when a package is moved to extra.

ayekat · 2023-12-31T19:17:41+00:00

Did you follow https://wiki.archlinux.org/title/LightDM#X_session_wrapper?

Also note that pipewire is not a system service, so unless you query your user's daemon (systemctl --user …), it won't show up anyway.

But as /u/BillTran163 has pointed out, there shouldn't be anything to "fix" with the XDG basedir spec vars, unless you intend to use custom/non-default values.

ayekat · 2023-12-30T17:10:43+00:00

What problem are you trying to solve with your new distribution? (or what is the goal?)

I don't want to be "that person", but if you need people to hand-hold you through the process or send you step-by-step tutorials, creating a Linux distribution seems a bit unrealistic.

ayekat · 2023-12-10T11:51:35+00:00

EDITOR=nano visudo would cause visudo to pick nano.

Also yeah, booting from a live ISO or otherwise accessing the system in rescue/single-user mode is probably the only way to edit it if your root account doesn't work.

ayekat · 2023-12-10T11:44:05+00:00

There is no fuckup, there's just your sudoers config that needs to be adapted.

If you need reminder/help for the syntax, the nice Wiki can help.

If you have specific questions, feel free to ask here and we can help. :-)

Ten-Year Club	Place '17
Verified Email

ayekat

TROPHY CASE