You are not logged in.
That link's not working
Offline
That link's not working
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
Nope. I just get a bunch of links and a pop up saying the requested page could not be found
Offline
Offline
...the current version of xfce4 creates a ~/.config/xfce4/labwc folder for the labwc configuration and autostart files. It's nice, the files are separated from ~/.config/labwc so users can still log into labwc only.
Maybe we should do the same. Right now our openbox files are prefixed bl- but they're still in the same ~/.config/openbox directory along with the vanilla openbox files. We could put ours in ~/.config/bunsen/openbox and ~.config/bunsen/labwc
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Online
unklar wrote:Unfortunately, this does not work because the essential files (autostart; menu.xml) cannot be created. There are only environment (brooding) and rc.xml.
The user must create them by hand. At least that's the case with siduction. :x
What do you mean it does nott work?
I don't have the setup right now, but as I recall, xfce4 includes the default rc.xml file for labwc, and xfce4 wayland calls labwc as "labwc -c" so that it reads the ~/.config/xfce4/labwc configuration.
Put your autostart and menu.xml files there (although the xfce4 menu works fine with labwc OOTB). Swaybg can be called from the autostart file to set the wallpaper.
The user can also have a ~/.config/labwc with separate configuration files to launch labwc only with waybar etc ... from a separate autostart.
@PackRat, I meant exactly what @hhh formulated:
The directory for labwc inside of xfce4 (~/.config/xfce4/labwc) was definitely maybe not populated when I installed it on trixie less than a month ago.
I have always assumed that Void is much further than debian in this regard.
The image you provide characterizes the exact: https://imgbox.com/JZpUEppx
In the shine-on of siduction exactly only these two files are created in the /home and restarting the installation with labwc does not work.
Therefore, the ISO was withdrawn with labwc under xfce4 already in December 2024.
...
Known bugs: Unfortunately, the Wayland implementation is currently so experimental that the session doesn’t start. We have blocked Wayland for now. If this bug is fixed, we will re-enable it in a point release.
Offline
PackRat wrote:...the current version of xfce4 creates a ~/.config/xfce4/labwc folder for the labwc configuration and autostart files. It's nice, the files are separated from ~/.config/labwc so users can still log into labwc only.
Maybe we should do the same. Right now our openbox files are prefixed bl- but they're still in the same ~/.config/openbox directory along with the vanilla openbox files. We could put ours in ~/.config/bunsen/openbox and ~.config/bunsen/labwc
That would be good, I think.
You must unlearn what you have learned.
-- yoda
Offline
Nice. Gnome or Cinnamon?
You must unlearn what you have learned.
-- yoda
Offline
^ GNOME, overview with a bunch of apps opened on their own desktop.
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
johnraff wrote:PackRat wrote:...the current version of xfce4 creates a ~/.config/xfce4/labwc folder for the labwc configuration and autostart files. It's nice, the files are separated from ~/.config/labwc so users can still log into labwc only.
Maybe we should do the same. Right now our openbox files are prefixed bl- but they're still in the same ~/.config/openbox directory along with the vanilla openbox files. We could put ours in ~/.config/bunsen/openbox and ~.config/bunsen/labwc
That would be good, I think.
OK I've put it on the TODO list.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Online
PackRat wrote:johnraff wrote:Maybe we should do the same. Right now our openbox files are prefixed bl- but they're still in the same ~/.config/openbox directory along with the vanilla openbox files. We could put ours in ~/.config/bunsen/openbox and ~.config/bunsen/labwc
That would be good, I think.
OK I've put it on the TODO list.
I would suggest to prepend to the TODO list rather than append
#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen
Offline
Offline
^ Interesting paper. Is that your research?
You must unlearn what you have learned.
-- yoda
Offline
^nice!
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Online
Maybe we should do the same. Right now our openbox files are prefixed bl- but they're still in the same ~/.config/openbox directory along with the vanilla openbox files. We could put ours in ~/.config/bunsen/openbox and ~.config/bunsen/labwc
johnraff wrote:PackRat wrote:That would be good, I think.
OK I've put it on the TODO list.
I would suggest to prepend to the TODO list rather than append
Done.
In fact I always put new additions at the top. Every now and then dig down and drag up any that look in danger of being forgotten. The idea is that it all gets implemented by Carbon release, but sometimes less urgent things get left over.
This particular change is simple enough. Just need a little think if any backward compatibility tweaks are needed for upgraders, like symlinks from the old locations...
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Online
^ Interesting paper. Is that your research?
Nope, just some stuff copy/pasted from manual.
Offline
^nice!
Thanks. i just added a subtle shade of yellow in Inkscape. Might try and add some gradients later
Offline