panel issue (labwc)

[Alphizi]

if monitor turn off, then turn on -> lxqt panel not auto starting. Need command "lxqt-panel" in terminal by hands.

[stefonarch]

How do you turn off the monitor?
In Session Settings → Modules do you see the panel running? It can be stopped and started there.

[Alphizi]

How do you turn off the monitor? In Session Settings → Modules do you see the panel running? It can be stopped and started there.

push on physical button on monitor case.

Did I pick the right place to leave bug reports for lxqt wayland + labwc session?

In Session Settings → Modules

Thanks

[stefonarch]

I can't reproduce this in both setups I have.. But somehow it reminds me of lxqt/lxqt-panel#2073

2 questions:

1.In Session Settings → Modules do you see the panel running when the monitor is turned on again? Open it before to see.

2. Do you use kanshi or it's default configuration?

Did I pick the right place to leave bug reports for lxqt wayland + labwc session?

It's fine, lxqt-panel would be good too. I don't think labwc is involved here, but you could check with other compositors too.

[JFLim1]

Had similar experience with lxqt-wayland session with labwc and kwin wayland compositor.

When you turn off the monitor after a while and the system auto lock-session. Turn on the monitor again, the lxqt-panel disappeared and the screen colour become garbled/distorted. Had to resort to logout/login or reboot return display monitor to display correctly again.

Is there any simple command or gui to prevent system from auto lock-session when on labwc or kwin wayland compositor session?

Tried "sudo systemctl mask loginctl lock-session" it didn't work.

[stefonarch]

Is there any simple command or gui to prevent system from auto lock-session when on labwc or kwin wayland compositor session?

Session Settings → unset "Lock before suspend/hibernate"
Power Management → no "lock " action
In KDE's systemsettings is a setting for lockscreen, it would be possible also modifying startlxqtwayland adding --no-lockscreen to the kwin command.

[JFLim1]

Power Management → no "lock " action

Thank you for guiding.

On Power Management GUI cannot find NO Lock actiion.

Green in programming. Where do insert the command for " --no-lockscreen " in startlxqtwayland?

labwc

elif [ "$COMPOSITOR" = "labwc" ]; then
    # Copy default configuration if not existing and set keyboard layout if different from us
    if [ ! -d "$XDG_CONFIG_HOME/labwc" ]; then
       cp -av "$share_dir"/lxqt/wayland/labwc "$XDG_CONFIG_HOME"/  # use default location here
       if echo "$valid_layouts" | grep -q "$trylayout"; then
          echo "XKB_DEFAULT_LAYOUT=$trylayout" >> $XDG_CONFIG_HOME/labwc/environment
       fi
    fi

    # enable cursor on VM (systemd only)
    if type systemd-detect-virt > /dev/null 2>&1 && systemd-detect-virt --quiet; then
        export WLR_NO_HARDWARE_CURSORS=1
        echo "Running on virtualized hardware"
    fi

    exec $COMPOSITOR -C $XDG_CONFIG_HOME/labwc -S lxqt-session

kwin_wayland

elif [ "$COMPOSITOR" = "kwin_wayland" ]; then
    # Style KDE's QML apps like systemsettings
    export QT_QUICK_CONTROLS_STYLE=org.kde.desktop
    export XDG_CURRENT_DESKTOP="LXQt:$COMPOSITOR"
    if echo "$valid_layouts" | grep -q "$trylayout"; then
        kxkbrc=$XDG_CONFIG_HOME/kxkbrc
        layout="LayoutList=$trylayout"
        if [ -f $XDG_CONFIG_HOME/kxkbrc ]; then
            if ! grep -q "LayoutList" "$kxkbrc"; then
                echo $layout >> $XDG_CONFIG_HOME/kxkbrc
            fi
        else
            echo "[Layout]" > $XDG_CONFIG_HOME/kxkbrc
            echo $layout >> $XDG_CONFIG_HOME/kxkbrc
        fi
    fi
    # WARNING: Option '--no-kactivities' can result in crashes with animations and corner actions.
    exec ${COMPOSITOR}_wrapper --exit-with-session lxqt-session --xwayland

[stefonarch]

Here:
exec ${COMPOSITOR}_wrapper --exit-with-session --no-lockscreen lxqt-session --xwayland

In the powermanagement lock screen could be triggered as idleness action, in your screenshot it is not enabled.

[JFLim1]

exec ${COMPOSITOR}_wrapper --exit-with-session --no-lockscreen lxqt-session --xwayland

Thanks. Done will test it out.

In the powermanagement lock screen could be triggered as idleness action, in your screenshot it is not enabled

Does that means in "labwc" wayland session, should not be having system auto lock-session? But from my experience yesterday on "labwc" wayland compositor still encountered the system auto lock-session which resulted in garbled/distorted screen. Will give "labwc" wayland a go later.

Currently on lxqt-desktop session (X11) which run fine with low resource usage but it loose chromium-mpp_v129 vpu hardware acceleration (only available with Wayland enabled).

[tsujan]

This is strange to me because I also use LXQt+kwin_wayland and have no issue — it's almost the same as the LXQt+kwin_x11 session I used before we made LXQt work with Wayland, but it feels lighter and more responsive.

Nowhere in LXQt or KDE's systemsettings I have a screenlocker. I don't use --no-lockscreen either.

I have monitorOffCommand=kscreen-doctor --dpms off in ~/.config/lxqt/power.conf (see https://github.com/lxqt/lxqt/wiki/ConfigWaylandSettings#turning-off-monitor-when-idle-with-kwin) and have enabled idle watcher like this:

It works exactly like it did in X11, without any problem.

Also, the graphic settings may play a role here. I've always had Intel+modesettings.

[JFLim1]

Here:
exec ${COMPOSITOR}_wrapper --exit-with-session --no-lockscreen lxqt-session --xwayland

@stefonarch,
Kwin_Wayland -- Apparently where "--no-lockscreen" is inserted it made a difference. With "--on-lockscreen" insert as above, still have the system auto "lock-screen" issue.

With "--no-lockscreen" inserted after lxqt-session like below, no more auto lock-session anymore with more 20 minutes idle or no activities.

exec ${COMPOSITOR}_wrapper --exit-with-session lxqt-session --no-lockscreen --xwayland

This is strange to me because I also use LXQt+kwin_wayland and have no issue — it's almost the same as the LXQt+kwin_x11 session I used before we made LXQt work with Wayland, but it feels lighter and more responsive.

@tsujan, I am on Arm64 device (Orange Pi 5 Plus - RK3588 SOC) not sure whether it made a difference.

Next is to test labwc wayland session whether it still have the auto lock-session issue and garble display after the auto lock-session kicks it and at time looses the "lxqt-panel" too.

[tsujan]

I am on Arm64 device ... not sure whether it made a difference.

I've received reports (in my own repositories) that showed it could make strange differences. I have no idea why.

[JFLim1]

Hi @tsujan and @stefonarch,

On lxqt-kwin-wayland, I can trigger the loss of "lxqt-panel" by turn-off the Monitor and turn-on the Monitor again. The lxqt-panel will disappear and also the background wallpaper. image disappear.

On terminal: lxqt-panel will restart the lxqt-panel.

[tsujan]

When you say it disappears, do you mean just visually or programmatically? If its process stops, then it should have crashed, and we need a backtrace. The same for pcmanfm-qt (which draws the desktop).

I think your issue happens at a more basic level than that of LXQt. My guess is that it's about Wayland.

[tsujan]

if monitor turn off, then turn on -> lxqt panel not auto starting. Need command "lxqt-panel" in terminal by hands.

@Alphizi
lxqt-panel doesn't need to auto-start after switching the monitor on and off; it should just be there. If it has crashed, please attach a backtrace.

[tsujan]

@JFLim1, @Alphizi

It might also be helpful if you tell which versions of Qt, labwc and KWin you have. But backtraces are needed.

@Alphizi, do you have arm64, like @JFLim1?