how to run the wf-install script to install wayfire automatically

[Marietto2008]

@ammen99 ; @soreau :

ok. Let's continue here :

[marietto@marietto-I5 /usr/home/marietto/Scaricati/wf-install]==> git config --global --add safe.directory /usr/home/marietto/Scaricati/wf-install/wayfire

error: can't block configuration file /home/marietto/.config/git/config: Permission denied

[marietto@marietto-I5 /usr/home/marietto/Scaricati/wf-install]==> sudo git config --global --add safe.directory /usr/home/marietto/Scaricati/wf-install/wayfire
Password:

[marietto@marietto-I5 /usr/home/marietto/Scaricati/wf-install]==> ./install.sh --prefix /opt/wayfire
Building Wayfire master
Installation prefix: /opt/wayfire

fatal: detected dubious ownership in repository at '/usr/home/marietto/Scaricati/wf-install/wayfire'
To add an exception for this directory, call:

	git config --global --add safe.directory /usr/home/marietto/Scaricati/wf-install/wayfire

[marietto@marietto-I5 /usr/home/marietto/Scaricati/wf-install]==> git config --global --add safe.directory /usr/home/marietto/Scaricati/wf-install/wayfire

error: can't block configuration file /home/marietto/.config/git/config: Permission denied

[marietto@marietto-I5 /usr/home/marietto/Scaricati/wf-install]==> sudo git config --global --add safe.directory /usr/home/marietto/Scaricati/wf-install/wayfire

[marietto@marietto-I5 /usr/home/marietto/Scaricati/wf-install]==> ./install.sh --prefix /opt/wayfire
Building Wayfire master
Installation prefix: /opt/wayfire
fatal: detected dubious ownership in repository at '/usr/home/marietto/Scaricati/wf-install/wayfire'

To add an exception for this directory, call:

	git config --global --add safe.directory /usr/home/marietto/Scaricati/wf-install/wayfire

[ammen99]

I would suggest deleting the wf-install folder together with everything and re-cloning it as a normal user + run install.sh as a normal user again.

Also, your git permissions are messed up. You should fix that first - I think google should be able to help there ;)

[Marietto2008]

[marietto@marietto-I5 /usr/home/marietto/Scaricati/wf-install] ==> # git clone https://github.com/WayfireWM/wf-install && cd wf-install

[marietto@marietto-I5 /usr/home/marietto/Scaricati/wf-install] ==>./install.sh --prefix /opt/wayfire

[62/62] Linking target src/panel/wf-panel
ninja: Entering directory `build'
[0/1] Installing files.
Installing subprojects/wayland-logout/wayland-logout to /opt/wayfire/bin
Installing src/panel/wf-panel to /opt/wayfire/bin
Installing src/background/wf-background to /opt/wayfire/bin
Installing src/dock/wf-dock to /opt/wayfire/bin
Installing /usr/home/marietto/Scaricati/wf-install/wf-shell/subprojects/wayland-logout/wayland-logout.1 to /opt/wayfire/share/man/man1
Installing /usr/home/marietto/Scaricati/wf-install/wf-shell/build/metadata/background.xml to /opt/wayfire/share/wayfire/metadata/wf-shell
Installing /usr/home/marietto/Scaricati/wf-install/wf-shell/metadata/dock.xml to /opt/wayfire/share/wayfire/metadata/wf-shell
Installing /usr/home/marietto/Scaricati/wf-install/wf-shell/metadata/panel.xml to /opt/wayfire/share/wayfire/metadata/wf-shell
Installing /usr/home/marietto/Scaricati/wf-install/wf-shell/data/wayfire.png to /opt/wayfire/share/wayfire/icons
Installing /usr/home/marietto/Scaricati/wf-install/wf-shell/data/wallpaper.jpg to /opt/wayfire/share/wayfire
Installing /usr/home/marietto/Scaricati/wf-install/wf-shell/build/meson-private/wf-shell.pc to /opt/wayfire/libdata/pkgconfig
Do you want to override the existing config file /home/marietto/.config/wayfire.ini [y/n]? y
cp: --backup=t is not a directory

[Marietto2008]

I think this error is more serious than the previous one :

Do you want to override the existing config file /home/marietto/.config/wayfire.ini [y/n]? y
Do you want to override the existing config file /home/marietto/.config/wf-shell.ini [y/n]? y

sed: 1: "/usr/home/marietto/Scar ...": extra characters at the end of h command

[ammen99]

Oh, I see. cp does not have such an option at all on BSD, just checked the documentation as well. In this case @Marietto2008 please take a look at the install.sh file and modify/remove all Linux-specific stuff. I think you are the first one to try and report wf-install on *BSD which is why I did not recognize the bug at first.

About this particular instance, I think it is safe to just remove the --backup=t parameter, or even the whole command altogether, since you already have a wayfire.ini file. It is only meant for first-time installations.

The errors you were getting later were related to the sed command. I suppose we're also using something linux-specific there: if you can figure out how the commands can be changed (I have no idea about BSD, unfortunately) I would be happy to add the changes upstream as well.

[Marietto2008]

that's not an error caused by the fact that I use zsh. Infact I've changed the default shell from zsh to bash :

[marietto@marietto-I5 /usr/home/marietto/Scaricati/wf-install]$ zsh -version
GNU bash, versione 5.2.21(0)-release (amd64-portbld-freebsd14.0)
Copyright (C) 2022 Free Software Foundation, Inc.
Licenza GPLv3+: GNU GPL versione 3 o successiva http://gnu.org/licenses/gpl.html

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

but the error is still there :

sed: 1: "/usr/home/marietto/Scar ...": extra characters at the end of h command

[Marietto2008]

this is the counter proof :

[marietto@marietto-I5 /usr/home/marietto/Scaricati/wf-install]==> chsh -s bash
Password: 
chsh: user information updated

[marietto@marietto-I5 /usr/home/marietto/Scaricati/wf-install]==> bash 

[marietto@marietto-I5 /usr/home/marietto/Scaricati/wf-install]$ bash -version
GNU bash, versione 5.2.21(0)-release (amd64-portbld-freebsd14.0)
Copyright (C) 2022 Free Software Foundation, Inc.
Licenza GPLv3+: GNU GPL versione 3 o successiva <http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Installing /usr/home/marietto/Scaricati/wf-install/wf-shell/data/wayfire.png to /opt/wayfire/share/wayfire/icons
Installing /usr/home/marietto/Scaricati/wf-install/wf-shell/data/wallpaper.jpg to /opt/wayfire/share/wayfire
Installing /usr/home/marietto/Scaricati/wf-install/wf-shell/build/meson-private/wf-shell.pc to /opt/wayfire/libdata/pkgconfig
Do you want to override the existing config file /home/marietto/.config/wayfire.ini [y/n]? n
Do you want to override the existing config file /home/marietto/.config/wf-shell.ini [y/n]? n

sed: 1: "/usr/home/marietto/Scar ...": extra characters at the end of h command

[ammen99]

I mean sed is not a function of the shell, sed is a utility program installed in /usr/bin and apparently on BSD, that utility program behaves differently than it does on Linux.

[soreau]

The problem is drm-backend : NO, you will have to install the dependencies required to build wlroots with drm backend as wayfire requires it.

[ammen99]

@Marietto2008 try to change the script like this:

sed -i "s@...."

should become

sed -i '' "s@..."

in all places where we use sed. Take a look at the stackoverflow link for details.

[ammen99]

@Marietto2008 Ok :) I thought you had more knowledge in general since using *BSD is a rather niche thing, I'd expect most "beginners" to use Ubuntu/Fedora/Arch. In any case, what I wrote in the previous comment should be enough to fix that particular issue.

[Marietto2008]

I can have more knowledge,yes,I'm not stupid. But more you go deeply in the specific,less is the knowledge that I can obtain reading and trying to understand. You already know that the shell scripting is a very specific task. You should not be wondered by this. Your fixes worked,except for the last two "sed" that I have converted from :

sed -i "s@^Exec.@exec=$PREFIX/bin/startwayfire@g" "$BUILDROOT/wayfire.desktop"
sed -i "s@^Icon.@ICON=$PREFIX/share/wayfire/icons/wayfire.png@g" "$BUILDROOT/wayfire.desktop"

to :

sed '' -i "s@^Exec.@exec=$PREFIX/bin/startwayfire@g" "$BUILDROOT/wayfire.desktop"
sed '' -i "s@^Icon.@ICON=$PREFIX/share/wayfire/icons/wayfire.png@g" "$BUILDROOT/wayfire.desktop"

but it didn't work. This is the error :

sed: -i: No such file or directory
sed: s@^Exec.*@exec=/opt/wayfire/bin/startwayfire@g: No such file or directory

[Marietto2008]

oh sorry,my mistake. It should be :

sed -i '' "s@^Exec.@exec=$PREFIX/bin/startwayfire@g" "$BUILDROOT/wayfire.desktop"
sed -i '' "s@^Icon.@ICON=$PREFIX/share/wayfire/icons/wayfire.png@g" "$BUILDROOT/wayfire.desktop"

Installation done. Run /opt/wayfire/bin/startwayfire to start wayfire.

now the fun begins...

[Marietto2008]

#!/usr/local/bin/zsh
export LD_LIBRARY_PATH=/opt/wayfire/lib/$libdir
export PATH=/opt/wayfire/bin:$PATH
env WLR_NO_HARDWARE_CURSORS=1 LIBSEAT_BACKEND=consolekit2 ck-launch-session dbus-run-session /opt/wayfire/bin/./wayfire

=

failed to open /dev/dri/card0 : permission denied
failed to open /dev/dri/render0128 : permission denied

[soreau]

failed to open /dev/dri/card0 : permission denied
failed to open /dev/dri/render0128 : permission denied

You might need to add your user to the group associated with these files.

[Marietto2008]

I've found the solution ;

Modified /etc/devfs.rules as follows:

add path 'dri/*' mode 0666 group video
add path 'drm/*' mode 0666 group video

And add myself to group video.

[ammen99]

Oh, that's great :) Maybe the video group is set for these files automatically only under Linux and *BSD is again different here ... But in any case good that you found the cause.

[Marietto2008]

That's interesting to note that wayfire worked for some time without adding those paths on the devfs.rules and then,suddenly,it stopped working.

[Marietto2008]

Is there a way to place some icon / launchers in the middle of the screen,when you use wayfire,that when clicked,some kind of application is launched ? Every DM works like this. xfce,kde and so on. Wayfire has it ?

[soreau]

There are launchers you can configure for wf-panel but they are on the panel, not the middle of the screen. It's good you got the nvidia drivers working with wlroots on freebsd. Perhaps we should create a new discussion for general wayfire questions and configuration.