It’s a user systemd service for you start as your user, start then if ok enable.
1 Like
I followed the documentation and created ~>/.config/systemd/user/walker.service
[Unit]
Description=Walker Launcher Service
PartOf=graphical-session.target
[Service]
ExecStart=/usr/bin/walker --gapplication-service
Restart=on-failure
[Install]
WantedBy=default.target
According to the docs once walker first run it will create a ~>/.config/walker/config.toml
but it did not.
Configuration
Walker is configured through ~/.config/walker/config.toml. This guide covers all available configuration options.
Configuration File Location
Default: ~/.config/walker/config.toml
Created automatically on first run
Reference: resources/config.toml in the Walker repository
So walker is still waiting for elephant. Elephant is sleeping man 
I did also this:
systemctl --user daemon-reload
systemctl --user enable walker.service
systemctl --user start walker.service
Thanks
@conram The elephant systemd service is included in the rpm install of elephant, all you need to do is run systemctl --user start elephant.service
Edit, you likely also want to add in the walker.service [Unit] After=elephant.service
1 Like
Yep I did that. Waiting for the elephant is gone but still walker is empty.
It is not responding to search. According to the docs, the first time you run walker it will have a config.toml in the ~>/.config/walker. In my case it did not. There is no walker folder in the ~>/.config directory . I would like to create one but there will be too much reading in the doc before I can build my config.toml.
Thanks
2 Likes
@enziosavio Really like that GNOME setup! I’ve themed mine out a bit more since my last posting.
Just curious as I haven’t run GNOME on openSUSE Tumbleweed for that long, does openSUSE usually roll out a new GNOME version as soon as it’s released or does it delay it for a bit? Just wondering as I use a few extensions and want to prepare in case they break if GNOME is updated too quickly.
Release is usually within a day or two… depends on the extensions, so may just require the metadata.json being updated with the version. But check the extension upstream to see where they are at as well.
Likewise, I saw none… It could be since openSUSE is not supported?
1 Like
It has rarely happened to me that the extensions did not work, in that case they disabled themselves without creating problems…I forgot to put the system data. The thing I gave up on were the proprietary drivers, since I did that I stopped having problems.
1 Like
Sounds good, thank you for the information.
I do not need propriety drivers in my setup, so I am good in this case.
Yes, indeed!
