starting wayland (wayfire) fails using nvidia card [Found 0 GPUS]

This is the portion of the tutorial involved in the error :


Code: 
# nano /home/marietto/.zshenv

# Path
typeset -U PATH path
path=("$HOME/bin" "/usr/local/bin" "$path[@]")
export PATH

# xdg directories
export XDG_CONFIG_HOME="$HOME/.config"
export XDG_CACHE_HOME="$HOME/.cache"
export XDG_DATA_HOME="$HOME/.local/share"
export XDG_RUNTIME_DIR="/var/run/user/`id -u`"

as user this is what reports the id command (when I run xfce and xorg) :

Code: 
# id
uid=1001(marietto) gid=1001(marietto) groups=1001(marietto),0(wheel),44(video)

# id -u
1001

I suspect that there isn't a permission problem,but something else. When I log out from xfce4 and from xorg,this is what I see (as user) :


Code: 
# cd /var/run/user
# ls
0


I don't see the dir 1001,so I can't check the permissions !. Is that normal ? I'm using zsh.

Code: 
echo $SHELL
/usr/local/bin/zsh
 
from the pastebin

Code: 
[wayland] unable to open lockfile /var/run/user/1001/wayland-1.lock check permissions

Code: 
sudo mkdir -p /var/run/user/"$(id -u)"
sudo chown -R "${USER}":"$(id -u)" /var/run/user/"$(id -u)"
sudo chmod 700 /var/run/user/"$(id -u)"
 
This is how the wayfire-start script should be :

Code: 
env LIBSEAT_BACKEND=consolekit2 ck-launch-session dbus-run-session wayfire

With that command Wayland / Wayfire has been finally able to start. BUT it didn't work as expected. Please check the screenshots attached below.
 

Attachments

  • 5.jpeg
    5.jpeg
    367.4 KB · Views: 87
  • 6.jpeg
    6.jpeg
    353.4 KB · Views: 88
  • 7.jpeg
    7.jpeg
    257.5 KB · Views: 88
If you have the file $HOME/.config/wayfire.ini, move it elsewhere to be sure to use the default settings.
Also do you have enabled seatd ?
sysrc seatd_enable="YES"

Finally, does wayfire and wayfire-plugins-extra are from the same repository ?
 
monwarez said:
Also do you have enabled seatd ?
Click to expand...
Messages after installing sysutils/seatd says
o use ConsoleKit2 run

# pkg install consolekit2 basu
# sysrc -x seatd_enable
# service seatd stop
# sysrc dbus_enable=YES
# service dbus start
$ ck-launch-session sway

where "ck-launch-session" can be dropped after

# echo "session optional pam_ck_connector.so" >>/etc/pam.d/system
$ exit # log out to re-trigger PAM
Click to expand...
So you shouldn't do
sysrc seatd_enable="YES"
wheh using ck-launch-session or setting env IBSEAT_BACKEND=consolekit2 to start wayfire.
 
monwarez said:
If you have the file $HOME/.config/wayfire.ini, move it elsewhere to be sure to use the default settings.
Also do you have enabled seatd ?
sysrc seatd_enable="YES"

Finally, does wayfire and wayfire-plugins-extra are from the same repository ?
Click to expand...
Code: 
cp /usr/local/share/examples/wayfire/wayfire.ini ~/.config

note you want to use wcm the gui to configure wayfire
the reason is its difficult to figure out the key codes for keyboard shortcuts without the gui

and it expects the config to be in

Code: 
~/.config/wayfire.ini

and not

Code: 
~/.config/wayfire/wayfire.ini
 
I've removed wayfire 0.9 and reinstalled wayfire 0.8 and the conflict with the plugin libfollow-focus is gone. I've also changed the values connected to my monitor from DP-3 to HDMI-A-1 ,as follows :

Code: 
# nano /usr/home/marietto/.config/mpv/mpv.conf

# mpv.conf

# list profiles with: mpv --profile=help

# load hwdec profile automatically
profile=hwdec

# hardware acceleration profile
[hwdec]
profile-desc="hardware acceleration, no cache, yt-dlp 1080 or less"
vo=gpu
hwdec=vaapi

# hide: GNOME's wayland compositor lacks support for the idle inhibit protocol.
#msg-level=ffmpeg=fatal,vo/gpu/wayland=no
msg-level=ffmpeg=fatal

# cache no for internet streams
cache=no

# yt-dlp best format 1080 or less
ytdl-format="bestvideo[height<=?1080]+bestaudio/best"

# show milliseconds in the on screen display
osd-fractions

# audio device
audio-device=oss//dev/dsp1

# youtube subs - J to switch to subs
sub-auto=fuzzy
ytdl-raw-options=sub-lang="en",write-sub=,write-auto-sub=
sub-font='NotoColorEmoji'

# screenshot timecode
screenshot-template="%F-[%P]v%#01n"


# cache profile: mpv --profile=cache
[cache]
profile-desc="hardware acceleration, cache, yt-dlp 1080 or less"
# include hwdec profile
profile=hwdec
# override hwdec profile cache setting
cache=auto


# youtube conditional auto profile match any youtube url
[youtube]
profile-desc="youtube hardware acceleration, cache"
profile-cond=path:find('youtu%.?be') ~= nil
# include hwdec profile
profile=hwdec
# override hwdec profile cache setting
cache=no
# fullscreen 2nd display
fs
fs-screen-name=HDMI-A-1


# invidious conditional auto profile match any youtube url
[invidious]
profile-desc="invidious hardware acceleration, cache"
profile-cond=path:find('http://127.0.0.1:3000') ~= nil
# include hwdec profile
profile=hwdec
# override hwdec profile cache setting
cache=no
# fullscreen 2nd display
fs
fs-screen-name=HDMI-A-1


# archive.org conditional auto profile match any archive.org url
[archive]
profile-desc="archive hardware acceleration, cache"
profile-cond=path:find('archive.org') ~= nil
# include hwdec profile
profile=hwdec
# override hwdec profile cache setting
cache=auto
# fullscreen 2nd display
fs
fs-screen-name=HDMI-A-1


# bbc iplayer conditional auto profile match any bbc iplayer url
[iplayer]
profile-desc="iplayer hardware acceleration, cache"
profile-cond=path:find('bbc.co.uk/iplayer') ~= nil
# include hwdec profile
profile=hwdec
# override hwdec profile cache setting
cache=no
# fullscreen 2nd display
fs
fs-screen-name=HDMI-A-1


# bbc iplayer conditional auto profile match any bbc iplayer url
[bbc]
profile-desc="bbc hardware acceleration, cache"
profile-cond=path:find('bbc:pips:service') ~= nil
# include hwdec profile
profile=hwdec
# override hwdec profile cache setting
cache=no
# fullscreen 2nd display
fs
fs-screen-name=HDMI-A-1

I've also changed DP-3 with HDMI-A-1 in the config file below :

Code: 
# nano /usr/home/marietto/.config/wlr-which-key/config.yaml

# Theming
font: Fira Code 18
background: "#282828d0"
color: "#fbf1c7"
border: "#005577"
separator: " ➜ "
border_width: 2
corner_r: 10
padding: 15 # Defaults to corner_r

# Anchor and margin
anchor: center # One of center, left, right, top, bottom, bottom-left, top-left, etc.
# Only relevant when anchor is not center
margin_right: 0
margin_bottom: 0
margin_left: 0
margin_top: 0

menu:
  "w":
    desc: general
    submenu:
      "m": { desc: mpv, cmd: ts mpv "$(wl-paste)" 1>/dev/null }
      "p": { desc: pinch, cmd: pinch -i "$(wl-paste)" }
      "y": { desc: yt-dlp, cmd: ts yt-dlp "$(wl-paste)" -o "$HOME/downloads/%(title)s.%(ext)s" }
  "s":
    desc: screenshot
    submenu:
      "l": { desc: laptop, cmd: grim -o HDMI-A-1 }
      "m": { desc: monitor, cmd: grim -o HDMI-A-1 }
      "b": { desc: both, cmd: grim }
  "e":
    desc: emacs
    submenu:
      "m": { desc: mpv, cmd: emacsclient -cF "((visibility . nil))" -e "(mpv-play-clipboard)" }
  "o":
    desc: obs
    submenu:
      "h": { desc: laptop, cmd: obs-cmd scene switch laptop }
      "j": { desc: monitor, cmd: obs-cmd scene switch monitor }
      "k": { desc: both, cmd: obs-cmd scene switch both }
      "l": { desc: ffmpeg, cmd: obs-cmd scene switch ffmpeg }
      "r": { desc: record, cmd: obs-cmd recording toggle }

I've used HDMI-A-1 because the log says that my screen is connected to the port HDMI-A-1 :

Ubuntu Pastebin

pastebin.ubuntu.com pastebin.ubuntu.com

What's the problem now ? that as soon as wayfire starts,I see only the freebsd-lynchmob.jpg image but I don't see any menu,I can't move any windows and I can't press any key : nothing work as expected.
 
my wayfire config doesnt have a panel just the wallpaper

probably best if you start with the default config

move the exiting ~/.config/wayfire.ini to the desktop

Code: 
mv ~/.config/wayfire.ini ~/Desktop

copy the default wafire.config to the config directory

Code: 
cp /usr/local/share/examples/wayfire/wayfire.ini ~/.config

use wcm which a gui to configure wayfire
 
Ok I did that. Now I see the taskbar on top of the screen,but I can't click in any place and nothing happens when I press a lot of keyboard keys. How can I launch "wcm" ?
 
NapoleonWils0n said:
with your application launcher, its called the wayfire-config-manager

or with your terminal

i cover it in the video
Click to expand...

Now I see the taskbar on top of the screen,but I can't click in any place and nothing happens when I press a lot of keyboard keys. I don't see / have any clickable menu.
 
Code: 
# git clone https://github.com/WayfireWM/wf-shell && cd wf-shell
# meson build --prefix=/usr --buildtype=release
# ninja -C build && sudo ninja -C build install
# mv /usr/home/marietto/Scaricati/wf-shell/wf-shell.ini /usr/home/marietto/Scaricati/wf-shell/wf-shell_.ini
# cp /usr/home/marietto/Scaricati/wf-shell/wf-shell.ini.example /usr/home/marietto/Scaricati/wf-shell/wf-shell.ini

=

Ubuntu Pastebin

pastebin.ubuntu.com pastebin.ubuntu.com

(wf-shell appeared,but mouse does not work,I can't use wcm to configure the panel) ; internet connection also does not work.
 
ok. I've changed the prefix from :

Code: 
# meson build --prefix=/usr --buildtype=release

to

Code: 
# meson build --prefix=/usr/local --buildtype=release

but my mouse still does not move. Changing the prefix didn't change anything. I have the same log messages as before.
 
ziomario said:
ok. I've changed the prefix from :

Code: 
# meson build --prefix=/usr --buildtype=release

to

Code: 
# meson build --prefix=/usr/local --buildtype=release

but my mouse still does not move. Changing the prefix didn't change anything. I have the same log messages as before.
Click to expand...
Setting WLR_NO_HARDWARE_CURSORS=1 before starting Wayfire should help.
 
ziomario said:
ok. I've changed the prefix from :

Code: 
# meson build --prefix=/usr --buildtype=release

to

Code: 
# meson build --prefix=/usr/local --buildtype=release

but my mouse still does not move. Changing the prefix didn't change anything. I have the same log messages as before.
Click to expand...
it shouldn't have to change anything regarding mouse. all 3-rd party software on FreeBSD goes to /usr/local
 
You must log in or register to reply here.
Back
Top