Ha ! Just built #Labwc from their git repo on #FreeBSD and it worked like a charm. I expected to hit problems but no. I now have the very latest commit version.
#RunBSD #Wayland #WindowManager
#RunBSD #Wayland #WindowManager
Recent searches
Search options
#labwc
0 posts0 participants0 posts today
Replied to Justine Smithies
@justine
I recommend reading this evident provocation.
http://xahlee.info/linux/why_tiling_window_manager_sucks.html
I am happy with #labwc.
I have configured the titlebar with double left click to iconify and middle click to lower, xfce4-panel as vertical #deskbar with intelligent autohide.
I use "Run or Raise" with single key shortcuts for most used applications.
Here is a link to an old implementation request of mine.
https://github.com/labwc/labwc/issues/673
Below is the current state of my #FreeBSD desktop environment
Continued thread
despite having added "export QT_QPA_PLATFORM="wayland;xcb"" in #labwc environment file, #keepassxc still doesn't open.. needs to be run like :
annoyance.
QT_QPA_PLATFORM=wayland keepassxcannoyance.
Still playing around with #Labwc and although it's a #Wayland stacking window manager that can tile aka snap to edge it can also be totally configured to work with just the keyboard. I'm pretty impressed so far with what can be achieved. If you liked #OpenBox then definitely give this a shot as you'll love it.
Replied in thread
@mp362 Try #voidlinux it's surprisingly stable despite being a rolling release :)
Also if you want to keep xfce but at the same time have some fresh experience one option is to combine it with #labwc and go full #wayland (not for stability ofc :D )
https://wiki.xfce.org/releng/wayland_roadmap#testing
wiki.xfce.orgreleng:wayland_roadmap [Xfce Wiki]
Replied in thread
Still playing with #Labwc and trying to hate it but failing miserably. I'm a tiling WM girl at heart but I'm actually liking the way Labwc works. There's no IPC for external control, You just use keybinds, rules and maybe some scripting magic with the likes of
#Wayland #OpenBox
wlrctl or wob. I'm still running #RiverWM as my daily though and just testing Labwc to see what's on the otherside but hey. ;)#Wayland #OpenBox
Replied in thread
Continued thread
Oh, of course. #GIMP not behaving as expected on #Wayland is a 4 years old issue that now has an actual effect but isn’t really GIMP’s fault.
https://gitlab.gnome.org/GNOME/gimp/-/issues/5323
Also this one which is not really related but used as reference when closing a bug reports with the recent version and window positions:
https://gitlab.gnome.org/GNOME/gimp/-/issues/12230
… I still wonder if I can somehow get the individual windows with a #labwc window rule.
GitLabWayland: broken window positioning restoration (#5323) · Issues · GNOME / GIMP · GitLabGIMP version: master Operating System: Wayland/Linux Description of the bug Our code for restoring dialogs to their...
Continued thread
Seems like I cannot get the individual windows by title. (Title is set after the window was created?)
Unfortunately the windows all have the same ID, so I cannot get the windows by their ID, either. Just using the ID lets me modify the windows just fine – but all windows the same, because they all have the same ID.
The funny thing is: #GIMP3 can store the window sizes just fine, but when restarting it, all windows positions are removed and #labwc opens them in the center (because centering otherwise unspecified windows is my default rule and thus expected).
I tried setting window hints as normal window or utility window, but without luck.
So either #GIMP doesn’t play nice with #Wayland, or something is wrong with labwc.
Got LabWC to run starting from a clean install of the postmarketOS console UI and I wrote down how to do it along with notes for me (and anyone who's curious) for later to know how to get my stuff to run on it with the least number of packages required. This implies that the binaries were pre-built (in another VM) when I copied them to the VM using sftp.
#Retiled (it's related since I talk about running my stuff in the link) #LabWC #postmarketOS
Codeberg.orgRetiled/docs/installing-labwc-from-postmarketos-ui-console.md at mainRetiled - An attempt at creating a "desktop" environment mainly for Linux phones and tablets that's similar in function to some parts of Microsoft's Windows Phone 8.x, primarily the Start screen, Search app, navigation bar, Action Center, and the status bar. Testing is mainly being done using the PinePhone, so that'll be the main supported device. This repo was migrated from GitHub and is the canonical repo as of September 12, 2023. New stuff will be here.
Playing around with #Labwc just to get that retro #Openbox feel. Do you use Labwc ? Have you tried it ?
Maybe share your thoughts, tips, dot files or screenshots ? #Wayland
I'm not moving from #RiverWm I'm just exploring
https://github.com/labwc/labwc
Maybe share your thoughts, tips, dot files or screenshots ? #Wayland
I'm not moving from #RiverWm I'm just exploring
https://github.com/labwc/labwc
GitHubGitHub - labwc/labwc: A Wayland window-stacking compositorA Wayland window-stacking compositor. Contribute to labwc/labwc development by creating an account on GitHub.
Replied in thread
@LXQt @whynothugo Mmmh, so this is why wl-mirror doesn’t work, right? It only shows as super small square and does not update.
So the problem really is #labwc here? Too bad, since it’s the only really good and customizable floating WM with not too many dependencies.
After lots and lots of waiting and trying out multiple different things regarding single window recording in #OBS 
on #Wayland 
running #labwc 
there is now a solution in place I can work with.
I wrote a wrapper script (see here) that does the following things when added as #pipemenu in labwc and I click the menu entry to create the output.
- Add a virtual output
- Use
wlr-randrto set the geometry - Use
swaybgto set the wallpaper - Send an update signal to a custom #Waybar module
I can now start #OBS and can add a #PipeWire screen recording and select the output (I have to do it blindly by just moving the cursor outside my actual display, because there is no menu, but that’s fine).
For what I’m doing the performance of the OBS preview is fast enough so I simply move the cursor over to the virtual output and use it “inside OBS”.
When I’m done, I invoke the script again, by clicking the remove entry which is dynamically shown if the output is active.
- Remove the output
- Remove “the output’s
swaybginstance” - Send an update signal to a custom Waybar instance
Until individual-window recording will be possible this is a good workaround.
#JustLinuxThings #ModernLinuxProblems #SharingIsCaring #scripting #Luanti #MinetestGame
//cc @whynothugo (thanks) @LXQt (thanks, too)
Continued thread
Replied in thread
@whynothugo I searched for various solutions to create a “fake output” on #labwc. It seems to be impossible here. So I guess I have to wait … Maybe some trickery with a nested instance … oh well 
Continued thread
Users of #sway and #labwc should note that we have moved the session files and application dependencies to new packages: sway-session and labwc-session. This enables the use of these compositors with other desktops, or under different contexts, without needlessly installing applications that may not be needed or wanted.
If you use these compositors as your desktop, make sure you install the session packages before logging out or restarting!