[plasmashell] [Bug 444026] LO Presentation mode broken after update to Plasma 5.23.0
https://bugs.kde.org/show_bug.cgi?id=444026 Jan-Marek Glogowski changed: What|Removed |Added CC||glo...@fbihome.de --- Comment #5 from Jan-Marek Glogowski --- FYI: the xrandr output suggests the layout is - from left to right: external HDMI (width: 1920) + 236 pixel nothing (the 2156) + laptop screen (width: 1920). In the LO bug report, Axel provided additional input from a little QScreen debug program for 5.22.5 and 5.23.0. The working setup with 5.22.5 doesn't have this gap, but since it's on a different machine, it's not yet clear it's related to the update. Still one idea is, that the LO window / screen positioning code might somehow mix up width and offset; Axel's monitor setup is uncommon. FWIW gtk and direct xlib show the same behavior for him. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436956] Multiple images copy paste issues
https://bugs.kde.org/show_bug.cgi?id=436956 --- Comment #17 from Jan-Marek Glogowski --- (In reply to Nate Graham from comment #16) > Jan-Marek, that specific issue appears to be caused by a Qt bug, which KDE > developer Jan Pontaoski has helpfully fixed already in > https://codereview.qt-project.org/c/qt/qtwayland/+/366769. The fix will be > backported into the KDE patch collection for Qt 5.15. Thanks for the quick reply. Very much looks like my LO bug. Now I just need to tell Debian to fix a non-security bug in QtWayland; it is really nasty... (I could use a QImage to catch the "application/x-qt-image" type and use convertToFormat to get the right stuff, but this feels like a horrible workaround :-( ... still tempting, but then other non-qt apps will still fail. So guess I'll just wait for a fixed Qt5) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436956] Multiple images copy paste issues
https://bugs.kde.org/show_bug.cgi?id=436956 Jan-Marek Glogowski changed: What|Removed |Added CC||glo...@fbihome.de --- Comment #15 from Jan-Marek Glogowski --- I might be hijacking this report and it might be a different problem, but it looks the same. I just analyzed a LibreOffice image pasting bug on Wayland in https://bugs.documentfoundation.org/show_bug.cgi?id=142889 Repo: 1. spectacle -> copy to clipboard 2. "wl-paste -l" lists "image/png" 3. "wl-paste -t image/png >/tmp/unknown.data" 4. "hexdump -C /tmp/unknown.data | head -n 1" 42 4d 36 ec 5e 00 00 00 00 00 36 00 00 00 28 00 |BM6.^.6...(.| So instead of ~375k PNG, which I get from spectacle on save, I got a 6.2m BMP from the clipboard, which LO's PNG reader doesn't like :-( That's for my freshly updated Debian Bullseye, which has some KDE 5.20.5 variant. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 407642] KFileWidget selects the the wrong filter on filter change with enabled automatic extensions
https://bugs.kde.org/show_bug.cgi?id=407642 --- Comment #2 from Jan-Marek Glogowski --- Patch: https://phabricator.kde.org/D21249 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 407642] KFileWidget selects the the wrong filter on filter change with enabled automatic extensions
https://bugs.kde.org/show_bug.cgi?id=407642 --- Comment #1 from Jan-Marek Glogowski --- Created attachment 120136 --> https://bugs.kde.org/attachment.cgi?id=120136=edit qmake file -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 407642] New: KFileWidget selects the the wrong filter on filter change with enabled automatic extensions
https://bugs.kde.org/show_bug.cgi?id=407642 Bug ID: 407642 Summary: KFileWidget selects the the wrong filter on filter change with enabled automatic extensions Product: frameworks-kio Version: 5.54.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Open/save dialogs Assignee: fa...@kde.org Reporter: glo...@fbihome.de CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 120135 --> https://bugs.kde.org/attachment.cgi?id=120135=edit Simple test file picker program If your filter list has two matching filters for an extension, KFileWidget will always select the first filter, even if the current filter already matches the file name. The result is that a user selects a filter and it's not honored by the UI. This resulted in two bugs in LibreOffice with the KDE backend: * https://bugs.documentfoundation.org/show_bug.cgi?id=125267 * https://bugs.documentfoundation.org/show_bug.cgi?id=120950 Our workaround is now to ignore the returned filter string. This bug doesn't happen with the non-native QFileDialog. STEPS TO REPRODUCE 1. Compile and run the attached program 2. Make sure that "auto extension" checkbox is enable 2. Select the last file filter (DocBook (.xml)) via dropdown list OBSERVED RESULT Filter is "Word 2003 XML (.xml)" EXPECTED RESULT Filter is "DocBook (.xml)" SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian Buster with KIO 5.54 I already have a patch for this. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 389349] vex amd64->IR: unhandled instruction bytes: 0xF3 0xF 0x1E 0xFA 0x48 0x8B 0x5 0xBD 0xAF 0x51
https://bugs.kde.org/show_bug.cgi?id=389349
Jan-Marek Glogowski changed:
What|Removed |Added
CC||glo...@fbihome.de
--- Comment #1 from Jan-Marek Glogowski ---
So a colleague was bitten by the same instructions on Arch with ld:
https://lists.freedesktop.org/archives/libreoffice-qa/2018-August/010517.html
Some research found: https://github.com/aquynh/capstone/issues/1129
I'm just quoting the information:
Intel introduced new instructions for the protection of indirect branches,
which make the processor fault if the target of an indirect jump is not an
endbr{32,64} instruction. If the processor does not support Indirect Branch
Tracking (IBT), the instruction is a nop (see [0], pages 15ff. and 130f.)
The instruction bytes for endbr64 are f3 0f 1e fa, for endbr32 they are f3 0f
1e fb.
So I guess there will be more of these in the future.
[0]
https://software.intel.com/sites/default/files/managed/4d/2a/control-flow-enforcement-technology-preview.pdf
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 260677] Konqueror obeys unicode RLO / RTL override char in filenames
https://bugs.kde.org/show_bug.cgi?id=260677 Jan-Marek Glogowski <glo...@fbihome.de> changed: What|Removed |Added CC||glo...@fbihome.de --- Comment #4 from Jan-Marek Glogowski <glo...@fbihome.de> --- $ touch $'Hello_\u202egnp.js' $ ls -l Hello_gnp.js $ dolphin . => Hello_sj.png -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 375010] libxkbcommon0 fails to update for users with wine-staging installed
https://bugs.kde.org/show_bug.cgi?id=375010 --- Comment #5 from Jan-Marek Glogowski <glo...@fbihome.de> --- And as sitter pointed out: Debian symbol files quite probably would have caught this problem, but they're quite a lot of work to maintain especially when you use CI build system, so Neon don't provide them. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 375010] libxkbcommon0 fails to update for users with wine-staging installed
https://bugs.kde.org/show_bug.cgi?id=375010 --- Comment #4 from Jan-Marek Glogowski <glo...@fbihome.de> --- But independently from the i386 problem, the update of kwin(-x11?) should have failed, as it needs symbols from the newer libxkbcommon0, so I guess kwin misses a versioned dependency on libxkbcommon0. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 375010] libxkbcommon0 fails to update for users with wine-staging installed
https://bugs.kde.org/show_bug.cgi?id=375010 Jan-Marek Glogowski <glo...@fbihome.de> changed: What|Removed |Added CC||glo...@fbihome.de --- Comment #3 from Jan-Marek Glogowski <glo...@fbihome.de> --- Created attachment 103946 --> https://bugs.kde.org/attachment.cgi?id=103946=edit i386 build of libxkbcommon0 Just updated my user KDE Neon yesterday. I still got skipped updates for libxkbcommon-dev, libxkbcommon-x11-0:amd64, libxkbcommon0:amd64 and libxkbcommon0:i386, which didn't bother me until I logged into the updated system. Window decorations were missing. First I suspected those Wayland Qt 5.8 bug, but dpkg still confirmed Qt 5.7. Then I wanted to dump the kwin information using qdbus, which failed due to a missing org.kde.KWin interface. Turned out kwin_x11 was not running! Manually starting kwin_x11 showed a missing library / symbols in libxkbcommon related libs. So I manually build an i386 version of libxkbcommon, which is attached for the bug. Easiest installation is "dpkg -i libxkbcommon0_0.7.0-1+16.04+build2_i386.deb" + "apt-get -f install". -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365678] Massive flicker and repaint problems with Neon 5.7 on remote X
https://bugs.kde.org/show_bug.cgi?id=365678 --- Comment #17 from Jan-Marek Glogowski <glo...@fbihome.de> --- Not sure if this helps. Searching for CS just shows the old lines, but now the previous lines list (almost) the same amount of warnings: [warning] plasmashell (unknown:0) - QXcbConnection: XCB error: 2 (BadValue), sequence: 50142, resource id: 119537670, major code: 142 (Unknown), minor code: 3 [warning] kwin (unknown:0) - QXcbConnection: XCB error: 9 (BadDrawable), sequence: 14337, resource id: 0, major code: 14 (GetGeometry), minor code: 0 [warning] kwin (unknown:0) - QXcbConnection: XCB error: 9 (BadDrawable), sequence: 14338, resource id: 0, major code: 14 (GetGeometry), minor code: 0 [warning] kwin (unknown:0) - QXcbConnection: XCB error: 9 (BadDrawable), sequence: 14340, resource id: 0, major code: 14 (GetGeometry), minor code: 0 [warning] kwin (unknown:0) - QXcbConnection: XCB error: 9 (BadDrawable), sequence: 14378, resource id: 0, major code: 14 (GetGeometry), minor code: 0 [warning] kwin (unknown:0) - QXcbConnection: XCB error: 3 (BadWindow), sequence: 17791, resource id: 132120671, major code: 15 (QueryTree), minor code: 0 [warning] kwin (unknown:0) - QXcbConnection: XCB error: 3 (BadWindow), sequence: 17840, resource id: 132120901, major code: 15 (QueryTree), minor code: 0 [warning] kwin (unknown:0) - QXcbConnection: XCB error: 3 (BadWindow), sequence: 17888, resource id: 132263908, major code: 15 (QueryTree), minor code: 0 [warning] kwin (unknown:0) - QXcbConnection: XCB error: 3 (BadWindow), sequence: 18528, resource id: 121634817, major code: 15 (QueryTree), minor code: 0 [warning] kwin (unknown:0) - QXcbConnection: XCB error: 3 (BadWindow), sequence: 20598, resource id: 121637445, major code: 15 (QueryTree), minor code: 0 radeon: The kernel rejected CS, see dmesg for more information. radeon: The kernel rejected CS, see dmesg for more information. radeon: The kernel rejected CS, see dmesg for more information. radeon: The kernel rejected CS, see dmesg for more information. radeon: The kernel rejected CS, see dmesg for more information. radeon: The kernel rejected CS, see dmesg for more information. radeon: The kernel rejected CS, see dmesg for more information. radeon: The kernel rejected CS, see dmesg for more information. radeon: The kernel rejected CS, see dmesg for more information. radeon: The kernel rejected CS, see dmesg for more information. [warning] plasmashell (file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:100) - file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Button.qml:100: TypeError: Cannot read property of null [warning] plasmashell (file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:83) - file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ToolTipDelegate.qml:83: TypeError: Cannot read property 'DesktopEntry' of undefined [warning] plasmashell (unknown:0) - QXcbConnection: XCB error: 2 (BadValue), sequence: 53586, resource id: 115343366, major code: 142 (Unknown), minor code: 3 radeon: The kernel rejected CS, see dmesg for more information. radeon: The kernel rejected CS, see dmesg for more information. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365678] Massive flicker and repaint problems with Neon 5.7 on remote X
https://bugs.kde.org/show_bug.cgi?id=365678 --- Comment #16 from Jan-Marek Glogowski <glo...@fbihome.de> --- Created attachment 100430 --> https://bugs.kde.org/attachment.cgi?id=100430=edit xsession-errors with extended error messages via QT_MESSAGE_PATTERN -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365678] Massive flicker and repaint problems with Neon 5.7 on remote X
https://bugs.kde.org/show_bug.cgi?id=365678
--- Comment #14 from Jan-Marek Glogowski <glo...@fbihome.de> ---
So this time I can confirm, that "Alt + Shift + F12" stops the compositing and
the flickering.
Guess I hit the wrong key combo last time, or I had a different problem, but
xsession-errors and dmesg show almost the same messages:
Today:
[18199.442243] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch
(888, 0x40, 1) invalid
[18199.442334] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream !
Previous:
[26610.825302] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch
(792, 0x40, 1) invalid
[26610.825349] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream !
What's the preferred way to set a different QT_MESSAGE_PATTERN? Edit startkde?
Guess the example from the Qt docs is ok for you: QT_MESSAGE_PATTERN="[%{type}]
%{appname} (%{file}:%{line}) - %{message}"
This proves my theory about the "late at day" is wrong, as I neither installed
new software, nor intensively used the system. Actually this time it happened
almost instantly after the first start of LO, when opening a dialog.
--
You are receiving this mail because:
You are watching all bug changes.
[neon] [Bug 365678] Massive flicker and repaint problems with Neon 5.7 on remote X
https://bugs.kde.org/show_bug.cgi?id=365678 --- Comment #12 from Jan-Marek Glogowski <glo...@fbihome.de> --- I had some more of these problems, but it's still not reproducible. My feeling is it's always at the end of the day, which might suggest leaking resources in the radeon driver. I don't really know, how to debug this. As you can see in the xsession-errors log, it contains a lot of > radeon: The kernel rejected CS, see dmesg for more information. so the kernel driver rejected the command stream from the Xorg driver, which matches the entries in the dmesg, literally thousand of lines of [40490.073706] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch (1752, 0x40, 1) invalid [40490.073763] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! in a few seconds / a minute. Now an application shouldn't be able to create a broken command stream. This looks more like a problem deeper in the stack. I'm not sure I remembered the right key combo, but any keys I hit didn't change the settings (I finally created a physical note, so I can active lookup the no-compositor-combo). I have access to other HW, but that's not my working system. Other people here running KDE5 with Intel HW (on Arch AFAIK) don't have this problem. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365678] Massive flicker and repaint problems with Neon 5.7 on remote X
https://bugs.kde.org/show_bug.cgi?id=365678 --- Comment #11 from Jan-Marek Glogowski <glo...@fbihome.de> --- Created attachment 100401 --> https://bugs.kde.org/attachment.cgi?id=100401=edit xsession errors from a flickering desktop -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365678] Massive flicker and repaint problems with Neon 5.7 on remote X
https://bugs.kde.org/show_bug.cgi?id=365678 --- Comment #10 from Jan-Marek Glogowski <glo...@fbihome.de> --- Created attachment 100400 --> https://bugs.kde.org/attachment.cgi?id=100400=edit Even more broken snapshot -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365678] Massive flicker and repaint problems with Neon 5.7 on remote X
https://bugs.kde.org/show_bug.cgi?id=365678 --- Comment #8 from Jan-Marek Glogowski <glo...@fbihome.de> --- Sorry that I didn't reply earlier. I tried to reproduce the problem, but failed until today (well I didn't try to actively reproduce it, but continued my LibreOffice (LO) development with Plasma 2 WM). The freezeing of LO seem to happen, when I use our LO extension, which is build with Java 7, but LO uses the Java 6 VM. This is independent of the flickering. Now today it happened again. I was able to take a screenshot and got the dmesg, which showed a lot of errors from the radeon driver, as the Linux console worked fine: line 1300: [26610.825302] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch (792, 0x40, 1) invalid [26610.825349] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! ... line 2484 [26898.242109] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch (792, 0x40, 1) invalid [26898.242152] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! It might be a coincidence, but this probably started after I installed todays Neon + Ubuntu updates. Don't know if this happened last time too. Lot of packages changed from: 4:5.7.1-0neon+16.04+* => 4:5.7.2-0neon+16.04+* Still for me the flickering never happened with Neon 5.6, which I used before. I forgot to copy the old .xsesion-errors and Xorg.0.log, so these are gone now :-( This also happened because of an other problem: I often have to login twice, otherwise primary and secondary screen are inverted. Workaround is just to logout and then login again. It's annoying, that it also moves the desktop icons between the screens, but I'll open a 2nd bug, as it doesn't seem related. I'll update the bug with .xsession-errors and Xorg.0.log, if it happens again. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365678] Massive flicker and repaint problems with Neon 5.7 on remote X
https://bugs.kde.org/show_bug.cgi?id=365678 --- Comment #7 from Jan-Marek Glogowski <glo...@fbihome.de> --- Created attachment 100208 --> https://bugs.kde.org/attachment.cgi?id=100208=edit xsession-errors from my working session It's not from the broken session, but still has a lot of troublesome looking messages, like: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 64271, resource id: 0, major code: 14 (GetGeometry), minor code: 0 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365678] Massive flicker and repaint problems with Neon 5.7 on remote X
https://bugs.kde.org/show_bug.cgi?id=365678 --- Comment #6 from Jan-Marek Glogowski <glo...@fbihome.de> --- Created attachment 100206 --> https://bugs.kde.org/attachment.cgi?id=100206=edit Flickering / broken desktop from ksnapshot This time the effect was even more extreme. Last time I had to do some interaction, like moving the mouse, to get the flickering (the desktop is nevertheless always broken in a way). This time I didn't even had to move the mouse and it was constantly flickering, albeit slower compared to the mouse movement. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365678] Massive flicker and repaint problems with Neon 5.7 on remote X
https://bugs.kde.org/show_bug.cgi?id=365678 --- Comment #5 from Jan-Marek Glogowski <glo...@fbihome.de> --- Created attachment 100205 --> https://bugs.kde.org/attachment.cgi?id=100205=edit Linux kernel log (dmesg) -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365678] Massive flicker and repaint problems with Neon 5.7 on remote X
https://bugs.kde.org/show_bug.cgi?id=365678 --- Comment #4 from Jan-Marek Glogowski <glo...@fbihome.de> --- Created attachment 100204 --> https://bugs.kde.org/attachment.cgi?id=100204=edit KWin support information -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365678] New: Massive flicker and repaint problems with Neon 5.7 on remote X
https://bugs.kde.org/show_bug.cgi?id=365678 Bug ID: 365678 Summary: Massive flicker and repaint problems with Neon 5.7 on remote X Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: glo...@fbihome.de CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org When starting LibreOffice AKA LO with KDE4 backend on a remote server, there is a high chance LO starts and gets stuck with refresh problems (no refresh at all) on startup. I can always deadlock refresh of LO by opening any dialog of LO. It's a little better with the Gtk+2 backend, where the application starts, but can still be deadlocked with opening a dialog, easiest done with the complex extension manager. To make it worse the whole screen basically breaks. On any mouse movement parts of the screen flickers and is repainted wrong. At this point you can just hope to switch to the konsole and Ctrl+C LO, which restores the screen. Luckly the window switcher (Alt + Tab) let you identify the konsole, even if the image of the window is completely broken, but it still resembles the konsole. As I need this connection for my LO development, I just switched to WindowMaker - no more problems. I found #363500, but this looks much less severe. Reproducible: Always Steps to Reproduce: 1. ssh -X 2. start LibreOffice preferably with KDE4 backend Actual Results: Whole screen is a mess, any interaction flickers. Expected Results: Remote X "just works". -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365169] New: No cryptsetup entry box or information in Neon 5.7 breeze theme
https://bugs.kde.org/show_bug.cgi?id=365169 Bug ID: 365169 Summary: No cryptsetup entry box or information in Neon 5.7 breeze theme Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: glo...@fbihome.de CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org I'm on "deb http://archive.neon.kde.org/user xenial main" - not sure which component to select, as no entry mentions the repositories - just tar and git. After upgrading from Neon 5.6 to 5.7, I see the plymouth boot splash for Neon 5.7, but cryptsetup unlocking doesn't display any information / input box - just the spinning "arrows" (?) stop. After pressing ESC I can see a console prompt to unlock the drive, which still works fine. Package: plymouth-theme-breeze Version: 5.7.0-0neon+16.04+build13 Downgrading to 5.6.5-0neon+16.04+build12 fixes the problem for me. Reproducible: Always Steps to Reproduce: Boot a computer with Neon 5.7 and cryptsetup partition. Actual Results: Frozen boot progress. Expected Results: Get the cryptsetup input prompt for the root device. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #35 from Jan-Marek Glogowski <glo...@fbihome.de> --- Created attachment 97888 --> https://bugs.kde.org/attachment.cgi?id=97888=edit jmux full es2_info output -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #34 from Jan-Marek Glogowski <glo...@fbihome.de> --- (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 works fine, and after unlocking > it, plasmashell is unresponsive. Is it also unresponsive for you Jan-Marek? > After killing plasmashell, the panel is still shown (there is no longer a > plasma process). Restarting kwin_x11 solves this. For me everything is responsive again, after killing the greeter and unlocking it. Otherwise I would run an other kind of session. I'm still don't know the origin of the deadlock. I thought it was related to DPMS, but locking the screen and running "sleep 10 && xset dpms force off" in the background doesn't trigger the greeter lockup. I just know it doesn't always lockup the greeter, but ever after longer inactivity. (In reply to Thomas Lübking from comment #30) > You may safely assume that this is a bug in the greeter or its foundation > (greeter dysfunctional -> killing. restarted greeter works) > Common pattern is Gallium/AMD, can you try EGL compositing? If I switch to EGL, compositing is disabled (according to to the qdbus output). Doesn't matter if I select OpenGL 2.0 or 3.1. The stripped output from es2_info (minus stripped extensions) says: 1.5 - not sure if this EGL version is related to the selected OpenGL version: EGL_VERSION: 1.5 (DRI2) EGL_VENDOR: Mesa Project EGL_CLIENT_APIS: OpenGL OpenGL_ES OpenGL_ES2 OpenGL_ES3 GL_VERSION: OpenGL ES 3.0 Mesa 11.1.2 GL_RENDERER: Gallium 0.4 on AMD RV710 (DRM 2.43.0, LLVM 3.8.0) BTW: my HW is old - a [AMD/ATI] RV710/M92 [Mobility Radeon HD 4530/4570/545v] -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #29 from Jan-Marek Glogowski <glo...@fbihome.de> --- Created attachment 97761 --> https://bugs.kde.org/attachment.cgi?id=97761=edit jmux KWin support info -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 Jan-Marek Glogowski <glo...@fbihome.de> changed: What|Removed |Added CC||glo...@fbihome.de --- Comment #28 from Jan-Marek Glogowski <glo...@fbihome.de> --- I've just updated from Kubuntu 14.04 to 16.04. Just wanted to add a "me too". There is a slight difference for my case: I can still switch to the tty, kill the greeter (SIGKILL) and the restarted instance is responsible for input and I can unlock my session. Still an annoyance. -- You are receiving this mail because: You are watching all bug changes.
