orw icon indicating copy to clipboard operation
orw copied to clipboard

Install on vanilla Arch

Open sdrwtf opened this issue 1 year ago • 3 comments

Hi,

I wanted to give this project a shot because I really like what is shown in your videos. I've tried to install it on a vanilla Arch system (a virtual machine if that makes a difference) with XORG profile used (via archinstall) but without any window manager. Unfortunately I'm not able to get it up running as expected.

Here's what I've tried:

After the initial Arch installation I cloned your repository and executed ´./setup.sh´. The script runs through until the following error showed up:

[sd@arch-orw orw]$ ./setup.sh
copying files..
installing dependencies..
[sudo] password for sd:
cleaning..
installing picom..
installing cava..
installing bar..
installing colorpicker..
installing i3lock-color..
installing sfeed..
backing up files in
setting up orw..
linking config files..
backing up files in ~/
backing up files in ~/.config
Cannot open display.
Error: DISPLAY environment variable is empty. Is there an Xorg or other X server running? You can try setting 'export DISPLAY=:0' and trying again.
Failed creating new xdo instance.
Cannot open display.
Cannot open display.
^C

This makes sense somehow, since X server is not running at the moment.

Can this project be used in a vanilla Arch installation or are there any dependencies that need to be installed up front? In issue https://github.com/s0la/orw/issues/9 you wrote that you use orw on vanilla arch, but the issue is also a bit older...

Thanks for your help!

Edit:

just figured out that if i ignore the error (by pressing ´ctrl + c´) and re-logon Openbox and the Theme etc. is loading:

image

but if i open any application (for example the terminal) I only get a small windows and have no chance to resize or maximize it:

image

sdrwtf avatar Oct 16 '23 13:10 sdrwtf

Hi there, and thanks for giving ORW a shot! :)

To clarify the first question first; based on error appearance, I'm quite confident it comes from the script responsible for generating orw config file (which holds information about the wm settings/properties and display(s)), so it's not mandatory for installation to finish, though I think issues you later described are totally expected given the lack of information to operate on..

I always ran the script (installation script - setup.sh) directly from Openbox gui session, so I never ran into this kind of issues myself.. Luckily, it's not a big deal, and the fix is super simple :)

First open the terminal (and resize it to some usable size - you can use Alt key and right mouse button to resize in any direction). Once you have a proper sized terminal, you need to remove orw config file (given it was created in the first place) at ~/.config/orw/config.. I'm pretty sure you know how to do it, but I'll provide an explicit commands anyway, just in case some other user stumbles upon this issue in the future:

[[ -f ~/.config/orw/config ]] && rm ~/.config/orw/config

after that, simply run a script generate_orw_config.sh, so

~/.orw/scripts/generate_orw_config.sh

which should generate a properly set config file.. I'd also suggest restarting the session, which can be done with:

openbox --exit

or using rofi power menu (Alt + q) and selecting a second option..

After you log in, everything should work as expected :) If you encounter any other issue, please let me know, and thanks for reporting this one as well!

s0la avatar Oct 16 '23 13:10 s0la

Hi,

thanks for the fast reply!

I tried the fix on the VM but it seems that the virtual environment causes some trouble. I will test it on a bare metal installation this week and inform about the outcome.

sdrwtf avatar Oct 16 '23 14:10 sdrwtf

Oh, sorry to hear it didn't work..

Would you mind pasting the content of your ~/.config/orw/config file, just to see if it was generated correctly?

s0la avatar Oct 16 '23 14:10 s0la