[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

https://bugs.kde.org/show_bug.cgi?id=363749 David Edmundson changed: What|Removed |Added Resolution|--- |INVALID CC|

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

https://bugs.kde.org/show_bug.cgi?id=363749 Alexander Mentyu changed: What|Removed |Added CC||notux...@gmail.com --- Comment #15 from

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

https://bugs.kde.org/show_bug.cgi?id=363749 Dr. Chapatin changed: What|Removed |Added CC||yy...@gmx.com -- You are

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

https://bugs.kde.org/show_bug.cgi?id=363749 --- Comment #14 from Martin Gräßlin --- We don't need to discuss this The problem that users have incorrectly Gles is always gentoo. Guess why I immediately jumped to the conclusion that you use Gentoo. Gles an gl are not mutual

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

https://bugs.kde.org/show_bug.cgi?id=363749 --- Comment #13 from s...@zxc.pp.ua --- (In reply to Martin Gräßlin from comment #12) > No, is an old Linux myth. Just think about it, that wouldn't work anywhere, > no distro compiles with gles. > > This problem only exists for Gentoo users. It's

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

https://bugs.kde.org/show_bug.cgi?id=363749 --- Comment #12 from Martin Gräßlin --- Am 18. Januar 2017 22:43:31 MEZ schrieb bugzilla_nore...@kde.org: >https://bugs.kde.org/show_bug.cgi?id=363749 > >--- Comment #11 from s...@zxc.pp.ua --- >(In reply to Martin Gräßlin from

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

https://bugs.kde.org/show_bug.cgi?id=363749 --- Comment #11 from s...@zxc.pp.ua --- (In reply to Martin Gräßlin from comment #10) > > wayland and other DEs which require gles. > > Wayland does not (!) require GLES. Wayland by itself not require gles. But other DEs require gles to run (compile)

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

https://bugs.kde.org/show_bug.cgi?id=363749 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

https://bugs.kde.org/show_bug.cgi?id=363749 --- Comment #10 from Martin Gräßlin --- > wayland and other DEs which require gles. Wayland does not (!) require GLES. -- You are receiving this mail because: You are watching all bug changes.

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

https://bugs.kde.org/show_bug.cgi?id=363749 --- Comment #9 from s...@zxc.pp.ua --- By the way kscreenlocker is only program (installed on my computer) that causing such memory leak. -- You are receiving this mail because: You are watching all bug changes.

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

https://bugs.kde.org/show_bug.cgi?id=363749 --- Comment #8 from s...@zxc.pp.ua --- (In reply to Martin Gräßlin from comment #6) > > 98% sure that answer is yes. > > If it is: switch to normal OpenGL (in case you are a Gentoo user this > requires a full(!) rebuild of everything of Qt and

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

https://bugs.kde.org/show_bug.cgi?id=363749 --- Comment #7 from Martin Gräßlin --- And yes, the valgrind log shows you are using OpenGL ES and it's full of errors due to that. -- You are receiving this mail because: You are watching all bug changes.

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

https://bugs.kde.org/show_bug.cgi?id=363749 --- Comment #6 from Martin Gräßlin --- > 98% sure that answer is yes. If it is: switch to normal OpenGL (in case you are a Gentoo user this requires a full(!) rebuild of everything of Qt and everything depending on Qt). OpenGL ES

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

https://bugs.kde.org/show_bug.cgi?id=363749 --- Comment #5 from s...@zxc.pp.ua --- (In reply to Martin Gräßlin from comment #4) > Are you using an OpenGL es build of Qt? 98% sure that answer is yes. I can check check it tomorrow. I saw bug somewhere around regarding qt + gles and "error:

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

https://bugs.kde.org/show_bug.cgi?id=363749 --- Comment #4 from Martin Gräßlin --- Are you using an OpenGL es build of Qt? -- You are receiving this mail because: You are watching all bug changes.

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

https://bugs.kde.org/show_bug.cgi?id=363749 --- Comment #3 from s...@zxc.pp.ua --- Created attachment 103490 --> https://bugs.kde.org/attachment.cgi?id=103490=edit valgrind kscreen log for 1 minute Attaching valgrind log -- You are receiving this mail because: You are watching all bug

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

https://bugs.kde.org/show_bug.cgi?id=363749 s...@zxc.pp.ua changed: What|Removed |Added CC||s...@zxc.pp.ua --- Comment #2 from

[kscreenlocker] [Bug 363749] kscreenlocker_greet will not accept password and taking 4.9 GiB

https://bugs.kde.org/show_bug.cgi?id=363749 --- Comment #1 from Martin Gräßlin --- you can run the actual binary of kscreenlocker_greet with --testing through gdb or valgrind. Though there is a chance that the actual problem won't be hit when in test mode. -- You are