https://bugs.kde.org/show_bug.cgi?id=491052
--- Comment #13 from cwo ---
(In reply to Martin Senftleben from comment #12)
> Hovering over the blue square in the top left corner, it says: "overview" in
> the drop down list.
I think that's the default setting.
If it doesn't happen anymore when yo
https://bugs.kde.org/show_bug.cgi?id=491052
--- Comment #12 from Martin Senftleben ---
(In reply to cwo from comment #11)
>
> Go System Aettings > Mouse & Touchpad > Screen Edges, and see if something
> is configured to happen in the top left corner (in the monitor image, there
> would be a bloc
https://bugs.kde.org/show_bug.cgi?id=491052
--- Comment #11 from cwo ---
(In reply to Martin Senftleben from comment #10)
> Now I had more time to test it under wayland. I have the impression that the
> hickup happens when the mouse cursor moves to the top left corner of the
> screen.
This makes
https://bugs.kde.org/show_bug.cgi?id=491052
--- Comment #10 from Martin Senftleben ---
Now I had more time to test it under wayland. I have the impression that the
hickup happens when the mouse cursor moves to the top left corner of the
screen. At least I remember that, when I was using XServer,
https://bugs.kde.org/show_bug.cgi?id=491052
--- Comment #9 from Martin Senftleben ---
Now I had more time to test it under wayland. I have the impression that the
hickup happens when the mouse cursor moves to the top left corner of the
screen. At least I remember that, when I was using XServer, t
https://bugs.kde.org/show_bug.cgi?id=491052
--- Comment #8 from Martin Senftleben ---
I have worked since yesterday using Wayland. I was surprised to see that
nothing was messed up, contrary to previous experiences. Everything started as
expected and also behaves that way. So far, the reported in
https://bugs.kde.org/show_bug.cgi?id=491052
--- Comment #7 from cwo ---
(In reply to Martin Senftleben from comment #5)
> Maybe I'm doing something that triggers it, but I
> haven't found that out yet. I'll keep an eye on it.
Yes, having more information would certainly be helpful.
> Yes, small
https://bugs.kde.org/show_bug.cgi?id=491052
--- Comment #6 from Martin Senftleben ---
(In reply to Nate Graham from comment #4)
> Because you're using X11, a total system freeze can't be caused by KWin, but
> rather the X server. Only on Wayland can KWin be the culprit.
Ok, but it's not a total
https://bugs.kde.org/show_bug.cgi?id=491052
--- Comment #5 from Martin Senftleben ---
(In reply to cwo from comment #3)
> I'm not suggesting you switch to Wayland permanently, just to test if it
> also happens there, so we can narrow down the circumstances when this
> happens. I know that there a
https://bugs.kde.org/show_bug.cgi?id=491052
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--- Comment #4 from Nate Graham ---
https://bugs.kde.org/show_bug.cgi?id=491052
--- Comment #3 from cwo ---
I'm not suggesting you switch to Wayland permanently, just to test if it also
happens there, so we can narrow down the circumstances when this happens. I
know that there are still features missing from Wayland that some peopl
https://bugs.kde.org/show_bug.cgi?id=491052
--- Comment #2 from Martin Senftleben ---
Thanks for your reply.
Well, I have no idea where to put this, as I don't know what most of the things
mentioned in the long list are doing.
I use a single monitor setup. I've tried Wayland many times some tim
https://bugs.kde.org/show_bug.cgi?id=491052
cwo changed:
What|Removed |Added
Product|Active Window Control |kwin
CC||chri
13 matches
Mail list logo
