#dont

1 messages Β· Page 1 of 1 (latest)

trim mortar
#

dont

wintry rock
#

yeah nvm it's 20 GB big.

trim mortar
#

can you run
env and send the result

wintry rock
#
[vm@vmtest-virtualbox ~]$ env
SHELL=/bin/bash
WINDOWID=25165827
COLORTERM=truecolor
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
I3SOCK=/run/user/1000/i3/ipc-socket.809
LC_ADDRESS=en_US.UTF-8
LC_NAME=en_US.UTF-8
DESKTOP_SESSION=i3
LC_MONETARY=en_US.UTF-8
EDITOR=nano
GTK_MODULES=canberra-gtk-module
XDG_SEAT=seat0
PWD=/home/vm
LOGNAME=vm
XDG_SESSION_DESKTOP=i3
XDG_SESSION_TYPE=x11
XAUTHORITY=/home/vm/.Xauthority
XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/vm
MOTD_SHOWN=pam
HOME=/home/vm
LC_PAPER=en_US.UTF-8
LANG=en_US.UTF-8
XDG_CURRENT_DESKTOP=i3
VTE_VERSION=7603
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
XDG_SESSION_CLASS=user
LC_IDENTIFICATION=en_US.UTF-8
TERM=xterm-256color
USER=vm
DISPLAY=:0
SHLVL=1
LC_TELEPHONE=en_US.UTF-8
LC_MEASUREMENT=en_US.UTF-8
XDG_VTNR=7
XDG_SESSION_ID=2
XDG_RUNTIME_DIR=/run/user/1000
DEBUGINFOD_URLS=https://debuginfod.archlinux.org 
LC_TIME=en_US.UTF-8
GTK3_MODULES=xapp-gtk3-module
BROWSER=firefox
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
GDMSESSION=i3
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
MAIL=/var/spool/mail/vm
LC_NUMERIC=en_US.UTF-8
_=/usr/bin/env
trim mortar
#

try this

wget https://raw.githubusercontent.com/Vendicated/VencordInstaller/main/install.sh
chmod +x ./install.sh
./install.sh
#

does it still error

wintry rock
#

let me install discord, I reverted to the clean image again

twilit tapirBOT
wintry rock
#

oh shut up

trim mortar
#

Tessie L

#

can you edit install.sh and where it calls $outfile add --debug

#

then send the result

wintry rock
#

after --location I assume?

trim mortar
#

no

wintry rock
#

oh I completely misread this shell script holy crap

trim mortar
#

here

wintry rock
#

yeah lol

#

brainfart moment

#
[vm@vmtest-virtualbox ~]$ ./install.sh
Downloading Installer...
Running with sudo
DEBUG Using UserConfig
DEBUG Checking if /home/vm/.config/Vencord/dist exists: Yes
DEBUG Is Dev Install:  false
DEBUG Checking for Installer Updates...
DEBUG Fetching https://api.github.com/repos/Vencord/Installer/releases/latest
DEBUG Fetching https://api.github.com/repos/Vendicated/Vencord/releases/latest
DEBUG Checking if /opt/discord/resources exists: Yes
DEBUG Checking if /opt/discord/resources/_app.asar exists: Yes
DEBUG Found Discord install at  /opt/discord
βœ” Install Vencord
βœ” Stable - /opt/discord [PATCHED]
INFO  Patching /opt/discord...
DEBUG Installing latest builds...
DEBUG Done!
DEBUG Fixing Ownership of /home/vm/.config/Vencord/dist
DEBUG Looking up User vm
DEBUG Lookup successful, Uid 1000 Gid 1000
DEBUG chown 1000:1000 /home/vm/.config/Vencord/dist: Success!
DEBUG chown 1000:1000 /home/vm/.config/Vencord/dist/package.json: Success!
INFO  /opt/discord is already patched. Unpatching first...
INFO  Unpatching /opt/discord...
DEBUG Deleting /opt/discord/resources/app.asar
DEBUG Renaming /opt/discord/resources/_app.asar to /opt/discord/resources/app.asar
INFO  Successfully unpatched /opt/discord
DEBUG Renaming /opt/discord/resources/app.asar to /opt/discord/resources/_app.asar
DEBUG Writing custom app.asar to /opt/discord/resources/app.asar
INFO  Successfully patched /opt/discord
βœ” Success!
[vm@vmtest-virtualbox ~]$ ls -a .config/Vencord/dist/
.  ..  package.json

#

and yeah discord has the same error

#

hmmm, im gonna unpatch, delete the dist directory, and try again

#

it might've skipped stuff because the dist directory already exists

trim mortar
#

idk

wintry rock
#
[vm@vmtest-virtualbox ~]$ ./install.sh
Downloading Installer...
Running with sudo
DEBUG Using UserConfig
DEBUG Checking if /home/vm/.config/Vencord/dist exists: No
DEBUG Fixing Ownership of /home/vm/.config/Vencord
DEBUG Looking up User vm
DEBUG Lookup successful, Uid 1000 Gid 1000
DEBUG chown 1000:1000 /home/vm/.config/Vencord: Success!
DEBUG chown 1000:1000 /home/vm/.config/Vencord/dist: Success!
DEBUG Is Dev Install:  false
DEBUG Checking for Installer Updates...
DEBUG Fetching https://api.github.com/repos/Vencord/Installer/releases/latest
DEBUG Fetching https://api.github.com/repos/Vendicated/Vencord/releases/latest
DEBUG Checking if /opt/discord/resources exists: Yes
DEBUG Checking if /opt/discord/resources/_app.asar exists: No
DEBUG Found Discord install at  /opt/discord
βœ” Install Vencord
Use the arrow keys to navigate: ↓ ↑ β†’ ← 
? Select Discord install to patch (Press Enter to confirm): 
  β–Έ Stable - /opt/discord
    Custom Location
DEBUG Is self outdated? false
DEBUG Finished fetching GitHub Data
DEBUG Latest hash is 3d46f19 Local Install is outdated!

#

and it hung, no more logs for a few minutes

#

oh wait my enter key isn't being registered lol

#
vm@vmtest-virtualbox ~]$ ./install.sh
Downloading Installer...
Running with sudo
DEBUG Using UserConfig
DEBUG Checking if /home/vm/.config/Vencord/dist exists: Yes
DEBUG Is Dev Install:  false
DEBUG Checking for Installer Updates...
DEBUG Fetching https://api.github.com/repos/Vencord/Installer/releases/latest
DEBUG Fetching https://api.github.com/repos/Vendicated/Vencord/releases/latest
DEBUG Checking if /opt/discord/resources exists: Yes
DEBUG Checking if /opt/discord/resources/_app.asar exists: No
DEBUG Found Discord install at  /opt/discord
βœ” Install Vencord
βœ” Stable - /opt/discord
INFO  Patching /opt/discord...
DEBUG Installing latest builds...
DEBUG Done!
DEBUG Fixing Ownership of /home/vm/.config/Vencord/dist
DEBUG Looking up User vm
DEBUG Lookup successful, Uid 1000 Gid 1000
DEBUG chown 1000:1000 /home/vm/.config/Vencord/dist: Success!
DEBUG chown 1000:1000 /home/vm/.config/Vencord/dist/package.json: Success!
DEBUG Renaming /opt/discord/resources/app.asar to /opt/discord/resources/_app.asar
DEBUG Writing custom app.asar to /opt/discord/resources/app.asar
INFO  Successfully patched /opt/discord
βœ” Success!
[vm@vmtest-virtualbox ~]$ ls -a .config/Vencord/dist
.  ..  package.json
#

idk, I give up...

#

that last run was with all of .config/Vencord deleted

lavish shale
#

if you look at the debug log you'll see that it's literally chmodding the files and succeeding, which means they do get created successfully

yet once you check with ls or run discord they're somehow gone

#

it doesn't make any sense

#

they somehow mysteriously disappear

#

has to be something cursed with your system

lavish shale
wintry rock
#

it only explicitly mentions package.json in the log
but yeah only my system and my VM can replicate it for some reason

lavish shale
#

but earlier logs had all files

wintry rock
#

beans and me have the exact same ISO for the VM too

lavish shale
#

well anyway if you run the installer often enough, you will get rate limited by github :p so that might play part of it

wintry rock
#

possibly, yeah I'll stop running it before they block my address

lavish shale
#

nah they won't lol

#

but there's a limit of 60 api requests an hour

#

the installer sends 2 i think

#

so if you run it 30 times you get rate limited

wintry rock
#

oh I definitely exceeded it at some point earlier

lavish shale
#

the error handling is a bit lacklustre in some cases

wintry rock
#

I was running the wget method that beans proposed till it worked

lavish shale
#

installer honestly needs a rewrite at this point

#

i rewrote parts of it multiple time when changing method of installing and fetching but it's kinda messy

wintry rock
#

hmmm
I tried to download the dist directory directly from the repo, but couldn't find it, probably the wrong repo

trim mortar
#

the weirdest thing to me, is that it works fine when ran outside of the script

lavish shale
wintry rock
lavish shale
#

don't ask me why it's called devbuild

wintry rock
#

ah, excellent, maybe I can fetch the files from there if I ever re-install my EOS again and this happens

#

thx

lavish shale
trim mortar
lavish shale
#

read the code

#

it just downloads the installer binary and runs it

lavish shale
#

there's no difference to just downloading it manually

trim mortar
#

the only difference is see is the
env "$@"

wintry rock
#

yeah... I noticed it just ran the commands I ran when wget'ing the binary manually

lavish shale
#

well actually the script does pass this variable
XDG_CONFIG_HOME=$XDG_CONFIG_HOME

#

maybe you have it set to something ridiculous but it should reflect itself in the path then

#

echo $XDG_CONFIG_HOME

wintry rock
trim mortar
#

but if it was an issue with that, how come package.json gets written

lavish shale
wintry rock
#

tried it the second you mentioned that env variable, it's blank lol

lavish shale
wintry rock
#

yeah looking at the output of env rn, it's $HOME

lavish shale
trim mortar
wintry rock
lavish shale
#

env with no arguments prints your environment variables :p

#

env FOO=bar command runs command with the additional environment variable FOO

#

the script does that to forward your XDG_CONFIG_HOME (which is a standard to customise your config directory) to the installer since when run as root it won't be correct anymore usually

trim mortar
#

if either of you ever find the issue, please let me know
this is really interesting to me

wintry rock
#
env XDG_CONFIG_HOME=$XDG_CONFIG_HOME echo $XDG_CONFIG_HOME

idk if I did it right, but that printed nothing but an empty newline

trim mortar
#

anyway gn

wintry rock
#

because yeah $XDG_CONFIG_HOME doesn't exist as far as I can tell?

lavish shale
wintry rock
lavish shale
#

try ```
env XDG_CONFIG_HOME=hi bash -c 'echo $XDG_CONFIG_HOME'

wintry rock
#

it seems to not be set in EOS

lavish shale
#

try this and you'll see

wintry rock
#
env XDG_CONFIG_HOME=hi bash -c 'echo $XDG_CONFIG_HOME'
hi
lavish shale
wintry rock
#

ah

lavish shale
#

it's a standard to customise your config directory location

#

if you don't want shit in ~/.config you can change it to some different location and any good program will respect it

#

but a lot of programs ignore the variable SKULL_SKELETON

wintry rock
#

I see, interesting, I've never touched it

#

Still doesn't explain the files vanishing bruhhhhhhhh

#

I don't even know anymore, nobody else can reproduce this.

#

Imagine it's a bug in my CPU that only affects things called Vencord

#

Nah jk, I'm banking on some weird network issue that the installer doesn't handle. I can't imagine any other explanation for both my physical machine and my VM having the exact same issue, but beans not having it despite having an idential ISO.

#

Anw thanks for your understanding, I will sleep now too.

wintry rock
#

Idk there's just something about EndeavourOS and my computer that makes it not work