You are not logged in.
DeepDayze wrote:Any chance of bug report to lightdm (and light-locker) devs about adding better support for launching Wayland sessions?
We'd need to do some debugging ourselves first, if the report is going to be helpful. Also some websearching to see if anyone else is getting problems launching Wayland sessions from LightDM. First, find where the lightdm logs are, and if it has a "verbose" option we can set somewhere. It's strange, because by the time the session has been started (by executing the command in a .desktop file) lightdm should have left the scene altogether...
And why does nwg-hello have no problems?
Makes sense and fair enough :-)
Real Men Use Linux
Offline
^making some progress > https://forums.bunsenlabs.org/viewtopic … 66#p137566
It looks like a lightdm bug - with a workaround - which has already been reported on GitHUb.
...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 )
Offline
apt lets me install both xfce4-notifyd (x11/carbon w/ openbox) and mako-notifier (wlroots/carbon w/ labwc), but the two notifiers cancel each other out when you boot. They both try to access dbus, and they both fail since only one is allowed.
https://kevinlocke.name/bits/2020/04/12 … conflicts/
I'm going to mess with it now.
I don't care what you do at home. Would you care to explain?
Offline
Xfce seem to be working hard on Wayland right now, there might be some hints we can pick up.
Here's one developer thread:
https://gitlab.xfce.org/xfce/xfce4-session/-/issues/209
...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 )
Offline
Xfce seem to be working hard on Wayland right now, there might be some hints we can pick up.
Here's one developer thread:
https://gitlab.xfce.org/xfce/xfce4-session/-/issues/209
Looks like that's a great sign Xfce devs are moving in the right direction. Xfce on Wayland would be awesome!
Real Men Use Linux
Offline
Right now xfce _is_ working with labwc.
As you know @johnraff labwc-0.8.2 supports window app icons, a big leap forward (and also as you know I packaged labwc and it's icon dependency libsfdo).
Birger Schatt the labwc (and much other stuff wayland) maintainer has just pushed libsfdo to unstable and my very recent apt update (few minutes ago) pulled it in but broke labwc! No big deal, just removed the versions I built and @b1rgers versions successfully installed. The beauty of this is that I think (hope) Birger is preparing for labwc-0.8.3 which the pre-release recently had pushes for menu icons support (using same libsfdo libs). This makes labwc much easier on the eye and definitively showing signs that it is reaching some sort of maturity.
Kudos to @malm for such an excellent project 
Here is Birger's bug report and fix : https://bugs.debian.org/cgi-bin/bugrepo … ug=1092211
Also, @malm recently posted a screenshot (https://forums.bunsenlabs.org/viewtopic … 53#p141053) depicting labwc-0.8.3(pre) with xfce4-panel showing icons and workspaces in the panel.
So xfce4-panel will be great for carbon-wayland no matter how far behind (in terms of release date) the X11 carbon version it will be.
#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen
Offline
So xfce4-panel will be great for carbon-wayland no matter how far behind (in terms of release date) the X11 carbon version it will be.
The issue that bothers me is the system tray on Wayland. Until xfce4-panel has that sorted, it is somewhat of a blocker.
(There's no systray visible on the panel in @malm's recent screenshot.)
Last edited by johnraff (2025-02-13 02:57:13)
...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 )
Offline
micko01 wrote:So xfce4-panel will be great for carbon-wayland no matter how far behind (in terms of release date) the X11 carbon version it will be.
The issue that bothers me is the system tray on Wayland. Until xfce4-panel has that sorted, it is somewhat of a blocker.
(There's no systray visible on the panel in @malm's recent screenshot.)
![]()
#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen
Offline
.. and this (systray popups work) https://forums.bunsenlabs.org/viewtopic … 21#p141221
#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen
Offline
.. and this (systray popups work) https://forums.bunsenlabs.org/viewtopic … 21#p141221
Thanks, that's encouraging. ![]()
Is that xfce4-panel 4.20.0-1 from Trixie?
...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 )
Offline
.. and this (systray popups work) https://forums.bunsenlabs.org/viewtopic … 21#p141221
I'm really looking forward to trying it out. ![]()
Thank you for your work!
Offline
micko01 wrote:.. and this (systray popups work) https://forums.bunsenlabs.org/viewtopic … 21#p141221
Thanks, that's encouraging.
Is that xfce4-panel 4.20.0-1 from Trixie?
Yup, all trixie, only sid is my reprepro install, which is kind of irrelevant
. Just hoping xfce4-panel-4.20.3 and labwc-0.8.3 make freeze and carbon-wayland will be a viable X11 alternative.
#!/bin/sh
echo '#include <stdio.h>\nvoid main() { printf("Hi, bunsenlabs\\n"); return; }' > bunsen.c
gcc bunsen.c -o bunsen
./bunsen
Offline
Just hoping
xfce4-panel-4.20.3andlabwc-0.8.3make freeze and carbon-wayland will be a viable X11 alternative.
Fingers crossed.
But I think we'll be able to offer something, and maybe post-release upgrades will improve the situation...
...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 )
Offline
Just a quick report on using Wayland over the last couple of months, as I needed to install Devuan on a Surface tablet, and opted for KDE Plasma this time around (previously GNOME) in the hope that the haptic feedback for dragging and swiping gestures would be better overall.
Some of the issues I'm about to list are not tablet-specific, and so would affect any devices using KDE Plasma with a Wayland compositor.
Of the issues listed, I have found the same issues to be absent in both GNOME and KDE Plasma (X11).
The issues have been identified across both KDE Plasma and the Plasma Mobile package, each when the Wayland compositor is used:
- In-built on-screen keyboard does not re-scale when switching from displays with a larger resolution to a smaller resolution. The keyboard size ratio is too large when switching back to a smaller display. What would be tablet-specific is, if there is no physical keyboard attached and the screen times out, the user cannot log in with the virtual keyboard due to it scaling off the screen, not all keys are available. The current workaround is to re-attach to a larger display, or attach a physical keyboard to restart the device. Logging out/in does not fix it. Resetting the virtual keyboard in the settings page does resolve the issue, but getting there without a physical keyboard will be tricky.
- When the screen times out, after logging in again, only the last focused window is available. There is no desktop (a black void). The system tray is no longer accessible and no other windows can (or the desktop) are accessible. The user has to log out and log back in as a workaround. This is intermittent.
- Auto-rotate screen orientation does not work on devices that support it, even when attempting to use surface- or tablet-kernels implemented for such features should they be missing.
- Screen flickering around the system tray.
- Automatically full-screening some applications without access to drop-down menus (e.g. browser). F11 to temporarily workaround, but after some seconds, it reverts to full screen where menus are not accessible.
Of the issues listed above, these do not appear to be an issue on the same device when choosing KDE Plasma (X11).
I'm not sure if it's relevant, but thought it might be useful to know should anyone experience similar issues when testing Wayland.
Offline