Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
mastodon.world is one of the many independent Mastodon servers you can use to participate in the fediverse.
Generic Mastodon server for anyone to use.

Administered by:

Server stats:

9.1K
active users

mastodon.world: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#labwc

0 posts0 participants0 posts today
Public *
Justine Smithies
Decided that using xorg on my dell optiplex 3080 tower under #FreeBSD isn't for me although it bought back memories. I have seen how certain software has already become stale by which I mean no updates or bug fixes in a good 4-5 years. So I've switched back to #Wayland which I still use on my #ThinkPAD . But my experience of using twm and xterm have made me go explore #Labwc again with my favourite Wayland terminal Foot. It's a lovely minimal stacking window manager which can be themed using #OpenBox themes. I have gruvbox dark installed which I quite like. As to what bar I'm going to use ? I'm not sure maybe waybar or sfwbar or even something else ? #RunBSD

https://github.com/labwc/labwc
Public
yianiris

LXDE is back alive and kicking

diaspora-fr.org/posts/10930716

diaspora-fr.org, un réseau social libre et respectueuxLXDE is backLXDE is back After many years of inactivity and due to dated code becoming problematic with late gcc developments, LXDE has received updates in the past few weeks. About the only two packages left untouched is lxpolkit and lxpanel, the rest of the group has been updated. This is a good thing because it was about the only desktop not falling pray to systemd/logind and dbus-ism. Some said that LXDE was abandoned because of #LXQT, a lightweight #plasma / #kde thing that resembled very little of what lxde was and became just as infected by systemd mechanisms as xfce4 and others. The systemd mainstays, #debian, #ubuntu, #mint, #fedora, rushed to replace lxde with lxqt. What they sold was the name of LXDE of stability and lightweight applications to associate with the buggy LXQT dt. Why was it buggy? Because it is a corporate rat race, one chasing behind the other, Qt, Kde, plasma, and back again. By the time they'd patch one side the other had bugs. And lxqt had to follow this ma...
#LXDE#openbox#labwc
Replied to Justine Smithies
Public
Makaba

@justine
I recommend reading this evident provocation.
xahlee.info/linux/why_tiling_w

At the moment I am happy with #labwc.
I have configured the titlebar with double left click to iconify and middle click to close, xfce4-panel as vertical #deskbar with intelligent autohide.
I use "Run or Raise" with single key shortcuts for most used application.

Here is a link to an old implementation request of mine.
github.com/labwc/labwc/issues/

Below is the current state of my #FreeBSD desktop environment

Public *
Justine Smithies
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 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
Public
KaiXin
Agreed. I mean, most of #Wayland compositors seem to be tilling #WM based, which I am always afraid to even try out because I am so spoiled by stacking windows. But #labwc makes me at home even I am trying out something totally new.
Continued thread
Public
𝘋𝘪𝘳𝘬

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
Public
𝘋𝘪𝘳𝘬

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.

Public
Drew Naylor

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.

codeberg.org/DrewNaylor/Retile

#Retiled (it's related since I talk about running my stuff in the link) #LabWC #postmarketOS

Summary card of repository DrewNaylor/Retiled
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.
Public
𝘋𝘪𝘳𝘬

After lots and lots of waiting and trying out multiple different things regarding single window recording in #OBS :obs: on #Wayland :wayland: running #labwc :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.

  1. Add a virtual output
  2. Use wlr-randr to set the geometry
  3. Use swaybg to set the wallpaper
  4. 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.

  1. Remove the output
  2. Remove “the output’s swaybg instance”
  3. 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)

Screenshot of a dual-output setup. The right output in 2K resolution and shows Luanti in fullscreen. The left output is in 4K resolution and shows OBS with a PipeWire screen recording of the right output and a small circular webcam image in the top right corner.
ExploreLive feeds
About