I’ve recently run into a rather concerning issue that I’ve had trouble solving. Google has been very little in the way of help. All I’ve found as to results that sound like my issue is this singular thread, which is an immediate dead-end, as I do not have the files SingletonLock or archlinux-2085 in my ~/.config/chromium folder, so that can’t be the issue. Short of reinstalling Chromium and electron and applications that use it, I’m already out of ideas. This is kind of a huge issue since this has ruined my ability to stream.
Among the applications affected, I’ve tried running, AND reinstalling all of them to no affect. I’ve also tried reinstalling Electron, no dice:
Stream Labels (installed via Debtap with some modifications to its deps, this sounds hacky but it did used to work btw so I think it not working related to the issue as it uses electron iirc)
Here’s what happens if I run the Chromium browser via the terminal.
Chromium logs
Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
(chromium:4927): IBUS-WARNING **: 15:25:42.218: chromium has no capability of surrounding-text feature
Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
If this causes problems, reconfigure your locale. See the locale(1) manual
for more information.
Fontconfig error: Cannot load default config file: No such file: (null)
I can hardly think of where to even begin to fix this issue, this issue came out of nowhere a few days ago and I’m completely stumped. I hope someone can help, thanks in advance for any and all answers.
I’m not sure where else it could’ve come from. Besides Stream Labels, and Toontown Rewritten I’ve almost always installed things via the AUR and cannot think of any other examples. Again Stream Labels was installed via debtap, but it worked before, and I’m not really sure why it’d break, or what steps I should take in debugging it.
locale output
[roadhog360@roadhog360-laptop16 ~]$ locale
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.UTF-8
LC_CTYPE=“en_US.UTF-8”
LC_NUMERIC=en_US.UTF-8
LC_TIME=en_AU.UTF-8
LC_COLLATE=“en_US.UTF-8”
LC_MONETARY=en_US.UTF-8
LC_MESSAGES=“en_US.UTF-8”
LC_PAPER=en_US.UTF-8
LC_NAME=en_US.UTF-8
LC_ADDRESS=en_US.UTF-8
LC_TELEPHONE=en_US.UTF-8
LC_MEASUREMENT=en_US.UTF-8
LC_IDENTIFICATION=en_US.UTF-8
LC_ALL=
This is a bit odd. I’ve noticed sometimes installing things complains about locale, but as it’s never caused any issues before, I never paid any mind to it since things seem to default to en_US as intended anyways. It’s been that way since install, on both PCs I’ve used EndeavorOS on. It hasn’t gotten in the way of any installs so I’m unsure of why it would now.
What further steps can I take to provide you with the best relevant information? I’m basically completely lost as to where to even go since this issue is bizarre and unlike anything else before.
Who told you to do this? Where’d you get the info to use the AUR for everything?
In any case, please read through the following threads. Make your life in Arch Linux less complicated by following what actually experienced users recommend.
Install apps in this order once they are available:
Official Repos > AUR/Chaotic-AUR > Direct binary from app website > Flatpak > Snap
The second and third are interchangeable depending on the app, but if you decide to add and use the Chaotic-AUR, do not put it ahead of the Official Repos.
A direct binary file could be an AppImage, zipped folder, etc.
Yes, I should mention this is intentional; I prefer 24:00 clock with YYYY-MM-DD calendar. Although, in locale.conf, it shows LC_TIME=en_US.UTF-8, oddly enough. I’ve added LC_ALL=en_US.UTF-8 to locale.conf and rebooted, with no difference.
[roadhog360@roadhog360-laptop16 ~]$ locale -a
C
C.utf8
en_US.utf8
POSIX
I’ve done as instructed. Chromium still doesn’t work at all, but the locale errors aren’t there any more at least. I’ve rebooted just to be sure after executing the commands you gave me. I’ve decided to reinstall Vesktop to see if its Electron instance would give any info. It turns out it’s also unable to load anything due to timeouts… wait, while fetching all the info for the initial post, I forgot to mention the specific part that is not working is because the page always times out. Argh, sorry!
So yeah, just to clarify, it seems most Chromium things don’t work, because they time out when trying to connect to anything.
Vesktop and Chromium logs
[roadhog360@roadhog360-laptop16 ~]$ vesktop
APPIMAGE env is not defined, current application is not an AppImage
Vesktop v1.5.5
checkForUpdatesAndNotify called, downloadPromise is null
[arRPC > ipc] listening at /run/user/1000/discord-ipc-0
[arRPC > websocket] listening on 6463
[arRPC > process] started
(vesktop:8667): IBUS-WARNING **: 23:44:56.873: vesktop has no capability of surrounding-text feature
(vesktop:8667): IBUS-WARNING **: 23:44:56.874: vesktop has no capability of surrounding-text feature
(node:8667) electron: Failed to load URL: https://discord.com/app with error: ERR_TIMED_OUT
(Use `vesktop --trace-warnings ...` to show where the warning was created)
^X^Z
[1]+ Stopped vesktop
[roadhog360@roadhog360-laptop16 ~]$ chromium
(chromium:9316): IBUS-WARNING **: 23:46:57.121: chromium has no capability of surrounding-text feature
Fontconfig error: Cannot load default config file: No such file: (null)
If you feel it’d be relevant I can throw some OBS logs in too after running a barebones scene with only some browser sources.
locale -a now contains en_AU.utf8:
[roadhog360@roadhog360-laptop16 ~]$ locale -a
C
C.utf8
en_AU.utf8
en_US.utf8
POSIX
locale no longer shows an error, but LC_ALL is still somehow blank, even though I added en_US.utf8 to that value in locale.conf multiple reboots ago:
I’m wondering if this issue is even related to the system locale at this point. I had a feeling it wasn’t, but I didn’t really know what else the issue could be.
Well this is embarassing. Somehow the issue was… bad proxy settings. I thought I had set it back to no proxy and honestly this just completely slipped my mind. I had this enabled to use tethering apps with my phone when not at home. I thought I’d set it back, but apparently just forgot. Did I turn off my PC before hitting apply or something…?
When it’s enabled when I’m connected to “regular” internet, I usually don’t even get working internet, which inadvertently reminds me to change it back, so my question now is… why the hell did it break Chromium but not the rest of my PC’s internet accessibility this time?! What changed recently!?
Apologies for the trouble. Dang it
TL;DR Solution: Apparently a bad proxy can potentially break only Chromium… and nothing else… but only sometimes???
No. I was writing this on Firefox on the same PC, and the AUR/commandline was able to fetch packages, the Vencord command to curl and run the installer worked. Seemingly, everything, BUT Chromium worked. What? How is that even possible?
I changed nothing about my proxy configuration beyond changing it to a custom IP for the purpose of making it compatible with my mobile tethering app, which those apps typically need the receiving PC to use a proxy. I didn’t do anything to make it affect specifically Chromium so I have no idea how this happened.
I should have left out the question about the why it only effected Chromiub-based apps. I was more curious how you a globally configured proxy configured and why because I wasn’t quite getting the reason. So from my understanding you were tethering with your mobile phone which needs a Proxy and then you configured a global proxy somewhere for your apps to be able to access the internet through your phone?
I just changed the proxy settings in the settings menu. There’s no option to make the proxy per-network, and there are no proxy settings under the networks I’ve connected to, the only proxy settings menu I see affects all networks unconditionally. So the “how” is just in the system settings app included with KDE, and the why is because there’s no other option to make it apply to only one network.
Do other browsers time out as well?