On 5/11/21 9:52 AM, Patrick Boutilier wrote:
On 5/10/21 1:15 PM, Temlakos wrote:
> On 5/10/21 12:12 PM, Patrick Boutilier wrote:
>>
>>
>> On 5/10/21 1:04 PM, Temlakos wrote:
>>> On 5/10/21 10:58 AM, Patrick Boutilier wrote:
>>>>
>>>>
>>>> On 5/10/21 11:32 AM, Temlakos wrote:
>>>>> On 5/10/21 10:13 AM, Patrick Boutilier wrote:
>>>>>>
>>>>>>
>>>>>> On 5/10/21 10:56 AM, Temlakos wrote:
>>>>>>> Everyone:
>>>>>>>
>>>>>>> Ever since the latest massive kde5 update (Saturday 8 May
>>>>>>> 2021), I have not been able to use the task bar to switch
>>>>>>> between open windows - and sometimes not even to start
certain
>>>>>>> applications that have taskbar icons. Anything in the System
>>>>>>> Tray is all right - like the dnfdragora update icon, the
>>>>>>> clipboard, the new-device icon, or the volume icon. But
>>>>>>> anything for an open window? Forget it. Every time I click on
>>>>>>> such an object, the computer pauses for about ten or fifteen
>>>>>>> seconds, during which it accepts no input from mouse or
>>>>>>> keyboard - and then blanks the screen, abruptly closes all
open
>>>>>>> windows, and restarts the session. Most of the time the
session
>>>>>>> is all right, but not always - in which case I restart the
>>>>>>> machine.
>>>>>>>
>>>>>>> It's not the kernel. I've tried this with all three
versions of
>>>>>>> the kernel I now have on board. (They're all three F34
builds
>>>>>>> by now.)
>>>>>>>
>>>>>>> It's one or more of the applications that are part of KDE
>>>>>>> Plasma. But I despair of telling which one. That update had
185
>>>>>>> programs in it, and only four of them are referable to the
kernel.
>>>>>>>
>>>>>>> I can always use the Alt-Tab trick to browse open windows to
>>>>>>> get to any open window I want. I can always start most
programs
>>>>>>> through the Applications Menu; that icon works. I /think/ I
can
>>>>>>> start one instance of Dolphin - but starting a new instance
>>>>>>> requires the task bar, so that's out. The only way to
open two
>>>>>>> instances of Dolphin is to connect an external device, thus
>>>>>>> giving me an excuse to open that device in Dolphin and then
>>>>>>> switch views. (And another thing: movement and copying from
one
>>>>>>> Dolphin instance to another is also broken. I have to use the
>>>>>>> clipboard as an intermediate step. Otherwise Dolphin
complains
>>>>>>> that it /can't read/ what I'm trying to move or
copy.)
>>>>>>>
>>>>>>> In other news, my bug reporting system is broken and
won't
>>>>>>> report anything, and the KDE Daemon keeps crashing at the
>>>>>>> beginning of every session - though I can't tell whether
I'm
>>>>>>> losing anything by that.
>>>>>>>
>>>>>>> Has anyone else noticed this issue?
>>>>>>>
>>>>>>> Can someone having an intact reporting system, or an upstream
>>>>>>> channel, try to report this?
>>>>>>>
>>>>>>
>>>>>> I wonder if the update didn't fully complete? Does this show
any
>>>>>> plasma/kf5 related updates?
>>>>>>
>>>>>> yum list updates
>>>>>
>>>>>
>>>>> No. No updates available at this time, from any repository.
>>>>> Whatever packages I got, the update went through. Ergo, I didn't
>>>>> get every package that needed to change, or the latest Plasma/KF5
>>>>> update contains a bug or bugs related to the Task Bar.
>>>>>
>>>>
>>>> Are yum running plasma under Wayland or X11 ?
>>>
>>> As far as I know, I'm using X11. I don't remember explicitly
>>> transferring to Wayland. I have been upgrading by the command line
>>> for every iteration since F21 at least, and so I should always have
>>> kept the same interface, which should be X11. I wouldn't know how
>>> to transfer to Wayland; I'm not even sure whether that is a valid
>>> interface for desktop hardware.
>>
>>
>> Default in Fedora 34 is wayland. Do this in Konsole and see if there
>> is any kwin/plasma stuff that comes back:
>>
>> ps ax|grep wayland
>>
>
> Done, and here is the output:
>
> ps ax|grep wayland
> 2044 ? S 0:00 /usr/libexec/sddm-helper --socket
> /tmp/sddm-auth6a45d97b-56fa-4345-8221-8fe52b898a6a --id 1 --start
> /usr/libexec/plasma-dbus-run-session-if-needed
> /usr/bin/startplasma-wayland --user Temlakos
> 2069 tty1 Ssl+ 0:00 /usr/bin/startplasma-wayland
> 2117 tty1 S+ 0:00 /usr/bin/kwin_wayland_wrapper
> --xwayland /usr/libexec/startplasma-waylandsession
> 22033 tty1 Sl+ 4:06 kwin_wayland --wayland_fd 4 --xwayland
> /usr/libexec/startplasma-waylandsession
> 22107 tty1 Sl+ 3:04 /usr/bin/Xwayland -displayfd 33
> -rootless -wm 36 -auth /run/user/1000/xauth_ITtMLk
> 22151 ? Sl 0:00 /usr/libexec/startplasma-waylandsession
> 40868 pts/1 S+ 0:00 grep --color=auto wayland
>
> The word "wayland" appears in red; the rest of the above text appears
> in white.
>
> Does that confirm your suspicion?
Yes. Try selecting an X11 plasma session from the SDDM login screen.
And how do I get to that point? My login screen asks me only one thing:
who am I, among three registered users of this computer? It does not ask
me for a preference of X11 v. Weyland.
Temlakos