https://bugs.kde.org/show_bug.cgi?id=357007
Götz changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #45 from Martin Gräßlin ---
I would like to see a backtrace of a hung kscreenlocker. Best would be through
ssh as it might be that switching to the tty already does the unfreeze.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=357007
Stefan Werner changed:
What|Removed |Added
CC||dust...@gmx.de
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #44 from Götz ---
Today I found something interesting. First the screenlocker was frozen, then I
changed the brightness with the corresponding hotkey and the screenlocker
unfroze, the cursor was blinking and I could write the password and un
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #43 from Thomas Lübking ---
(In reply to PhillB from comment #42)
> That is to say the bold notice, indicating the shift key is
> active, appears when you press the shift key and goes away when you release
Means this bug is (likely) not you
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #42 from PhillB ---
Just a quick note: I noticed a couple of weeks ago (and meant to add it here)
that when the screenlocker becomes unresponsive to KB/Mouse the shift key still
works. That is to say the bold notice, indicating the shift key
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #41 from Diego ---
(In reply to Thomas Lübking from comment #40)
> Moreover fullscreen unredirection is no way the same as suspending the
> compositor (the former still bears an active GL context), so the interesting
> question is whether th
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #40 from Thomas Lübking ---
Moreover fullscreen unredirection is no way the same as suspending the
compositor (the former still bears an active GL context), so the interesting
question is whether that setting makes any difference for you?
-
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #39 from Martin Gräßlin ---
(In reply to Diego from comment #38)
> Is checking "Suspend compositor for full screen windows" supposed to disable
> compositing for kscreenlock? I expect the answer to be "yes". Thanks.
maybe. The feature only
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #38 from Diego ---
Is checking "Suspend compositor for full screen windows" supposed to disable
compositing for kscreenlock? I expect the answer to be "yes". Thanks.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=357007
Diego changed:
What|Removed |Added
CC||diego...@zoho.com
--
You are receiving this mail becau
https://bugs.kde.org/show_bug.cgi?id=357007
Simon Andric changed:
What|Removed |Added
CC||simonandr...@gmail.com
--
You are receiving thi
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #37 from Götz ---
This is strange, since a week or two, using KWin with OpenGL 2.0 and XGL
composition, when the locker becomes unresponsive, just switching to a TTY and
back (without killing any process) makes the locker become responsive a
https://bugs.kde.org/show_bug.cgi?id=357007
Nakato changed:
What|Removed |Added
CC||chronicli...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=357007
Nicolás Adamo changed:
What|Removed |Added
CC||nicoad...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=357007
PhillB changed:
What|Removed |Added
CC||phi...@webwombat.com.au
--- Comment #36 from PhillB -
https://bugs.kde.org/show_bug.cgi?id=357007
Maciej Sitarz changed:
What|Removed |Added
CC||macieksit...@wp.pl
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #35 from Jan-Marek Glogowski ---
Created attachment 97888
--> https://bugs.kde.org/attachment.cgi?id=97888&action=edit
jmux full es2_info output
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #34 from Jan-Marek Glogowski ---
(In reply to Götz from comment #32)
> Using EGL, there same issue(s) continue.
>
> > Can you try to kill just kscreenlocker_greet instead? (see jmux's input)
>
> Yes, the newly restarted kscreenlocker_greet
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #33 from Götz ---
I forgot to add, that before restarting the greeter, I used a shortcut to
change the Keyboard Layout, and after the greeter restarted, the layout was
changed.
--
You are receiving this mail because:
You are watching all b
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #32 from Götz ---
Using EGL, there same issue(s) continue.
> Can you try to kill just kscreenlocker_greet instead? (see jmux's input)
Yes, the newly restarted kscreenlocker_greet works fine, and after unlocking
it, plasmashell is unrespons
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #31 from Thomas Lübking ---
(In reply to Götz from comment #26)
> This is also strange. The combobox was empty while OpenGL 2.0 or 3 where
> selected. Now I see the options (now sure what changed) and I have selected
> EGL.
It queries KWin
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #30 from Thomas Lübking ---
(In reply to Jan-Marek Glogowski from comment #28)
> kill the greeter (SIGKILL) and the restarted
> instance is responsible for input and I can unlock my session. Still an
You may safely assume that this is a bug
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #29 from Jan-Marek Glogowski ---
Created attachment 97761
--> https://bugs.kde.org/attachment.cgi?id=97761&action=edit
jmux KWin support info
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=357007
Jan-Marek Glogowski changed:
What|Removed |Added
CC||glo...@fbihome.de
--- Comment #28 from Ja
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #27 from Götz ---
It seems that there are no "OpenGL interface" options (the combobox is empty),
when kwin is not running. Bug or feature?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #26 from Götz ---
> Comment #2 said "Just tried using KWin with compton as compositor and the
> same problem."
I don't remember that :)
There are to many variables I forgot that one.
> Yes, but while hidden when you select XRender, it's n
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #25 from Thomas Lübking ---
Comment #2 said "Just tried using KWin with compton as compositor and the same
problem."
> Is that the 'OpenGL interface' in System Settings?
Yes, but while hidden when you select XRender, it's never supposed to
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #24 from Götz ---
> - Have you tried EGL compositing?
I haven't tried EGL. And I don't known how to do it. Is that the 'OpenGL
interface' in System Settings? That combobox is disabled in my system.
And I haven't tried KWin + compton (will d
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #23 from Thomas Lübking ---
- Have you tried EGL compositing?
- Was/is the konsole window in the second shot interactable?
The entire thing looks pretty much like the driver fails to keep the compositor
and the QtQuick GL contexts apart, bu
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #22 from Götz ---
Created attachment 97730
--> https://bugs.kde.org/attachment.cgi?id=97730&action=edit
then, screenshot after killing kscreenlocker
the left Plasma panel is not shown, only an empty transparent section, showing
the kscree
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #21 from Götz ---
Created attachment 97729
--> https://bugs.kde.org/attachment.cgi?id=97729&action=edit
After killing kwin_x11
kscreenlocker is active/shown, but without reacting to keyboard input, password
is entered, without screen bein
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #20 from Götz ---
I can not reproduce that, but other odd things happen. It was, Alt+Tab not
working, Alt+F4 neither, mouse clicks don't works.
Sometimes kscreenlocker works but after unlocking, screen parts which update,
flicker.
I'll al
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #19 from Götz ---
Created attachment 97728
--> https://bugs.kde.org/attachment.cgi?id=97728&action=edit
"qdbus org.kde.KWin /KWin supportInformation"
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #18 from Thomas Lübking ---
PS, please attach the output of "qdbus org.kde.KWin /KWin supportInformation"
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #17 from Thomas Lübking ---
What is
> react strange to keyboard or mouse input
?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=357007
Martin Gräßlin changed:
What|Removed |Added
Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org
--
You are receiving t
https://bugs.kde.org/show_bug.cgi?id=357007
Götz changed:
What|Removed |Added
Component|general |general
Version|5.5.1 |
38 matches
Mail list logo
