Jun 10, 2023, 10:00 AM
Post #4 of 10
(260 views)
Permalink
On 2023.06.10 04:44, Michael wrote:
> On Saturday, 10 June 2023 01:19:06 BST Jack wrote:
>> I've been running xorg (KDE Plasma) for years, and have been
>> perfectly happy, but every now and then I have tried wayland, with
>> less or even less success. My recent attempts give me a plasma
>> session in the upper 1024 x 768 of a monitor that does 1920x1080. It
>> also doesn't recognize the second monitor at all. However, the
>> mouse cursor moves freely across all of both monitors.
>
> Stating the obvious, but have you tried systemsettings to change the
> Display resolution? Logout, then login.
Display Settings said that 1024x768 was the only available resolution.
(see below)
>
> Also, have you tried dropping into a console and back again into the
> wayland desktop?
Same behavior.
>
> I know some of the above sounds like cargo-culting, but I have found
> them to work with mixed results.
I've seen stranger things work.
>
I'm not sure what in your response that gave me a clue, but although I
modified .xinitrc into .winitrc to use startplasma-wayland, I was still
calling it with startx. DOH! So now, just running .winitrc gets me
full resolution.
However, running as a new user, it sees both monitors, but running as
my existing user, it only sees one monitor. At least now I can start
digging through changes in .login/.config between the two users.
>
>> I've modified /etc/default/grub per the Wayland wiki page with no
>> change. My main question right now is where to find any log of the
>> wayland session. There is a KDE page which says where to look if
>> you launch wayland from sddm, but I'm launching from a command line,
>> using startx, with the last line in .winitrc (so I can also keep my
>> original .xinitrc) of either "exec dbus-run-session
>> startplasma-wayland" or "exec dbus-launch --sh-syntax
>> --exit-with-session startplasma-wayland".
>
> Without sddm, you can run the startplasma-wayland stanza from a
> console, do your thing, logout and the console would have captured
> various logs - just as startx does.
still didn't notice anything useful in the output, other than finally
noticing that X was still starting when I least expected it.
> Alternatively, to check wayland or xwayland applications from within
> wayland, run in a terminal:
I might still try that, but it's that basic system, not any particular
application that was the issue.
Thanks for the clue, or at least triggering me to find it.
>
> qdbus org.kde.KWin /KWin org.kde.KWin.showDebugConsole
>
> I moved to wayland 2-3 years ago for the opposite reasons to you.
> After the
> odd update(s) Xorg had started playing up with two monitors, causing
> the
> Plasma Task Manager to disappear, messing up the resolution,
> switching the
> primary monitor from left to right, and other problems I can't recall.
> Reconfiguring Plasma settings would not survive a reboot. I never
> bottomed
> out the causes of these problems (Plasma, Xorg video driver, mesa)
> and was
> about to give up on Plasma when I thought of trying out Wayland.
> Surprisingly
> Wayland provided a more stable desktop than Xorg had become! I have
> three
> systems running Wayland, all with radeon graphics. I don't know if
> Nvidia
> needs particular tweaking for NVENC, I've no experience with Nvidia in
> general. An intel laptop with Enlightenment works in Wayland,
> although the
> odd xwayland application fails to launch (e.g. Gkrellms).
I have also had odd behavior with X and two monitors, but I always
managed to get it working without excessive effort. My most persistent
problem was if the right monitor was plugged into the primary output,
reordering the monitors in the Display Settings would eventually get
lost and require me to do it again. At this point I can't remember why
I was so against just switching the cables.
>
Final point - I still haven't found where the wayland log is when not
using sddm.
Jack