[kwin] [Bug 357728] Dragging window leads to display freeze

https://bugs.kde.org/show_bug.cgi?id=357728 Bernd Steinhauser changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[kwin] [Bug 357728] Dragging window leads to display freeze

https://bugs.kde.org/show_bug.cgi?id=357728 --- Comment #17 from Bernd Steinhauser --- Last time it happened I forgot to enable ssh before, so I could not check. After that I started testing the setting mentioned above and it didn't happen again. I will reenable

[kwin] [Bug 357728] Dragging window leads to display freeze

https://bugs.kde.org/show_bug.cgi?id=357728 --- Comment #16 from Thomas Lübking --- No, it's indeed unlikely. gdb is likely to be unspecific as well (still worth a shot ;-), but dmesg of the life system might be very relevant. reloading the radeon kernel module also

[kwin] [Bug 357728] Dragging window leads to display freeze

https://bugs.kde.org/show_bug.cgi?id=357728 --- Comment #15 from Bernd Steinhauser --- Ok, tried to reproduce the quick-tiling thing in two ways: 1) Using shortcuts for quick tile left, right and top 2) Dagging the window quickly (works best in the top corner where

[kwin] [Bug 357728] Dragging window leads to display freeze

https://bugs.kde.org/show_bug.cgi?id=357728 --- Comment #14 from Bernd Steinhauser --- Looking at that bug it seems different to me in that for me it leads to a complete freeze (cannot even kill X with sysrq+k (security access key). For allan, things seemed to get

[kwin] [Bug 357728] Dragging window leads to display freeze

https://bugs.kde.org/show_bug.cgi?id=357728 --- Comment #13 from Thomas Lübking --- (In reply to Bernd Steinhauser from comment #12) > Are there special OpenGL extensions that translucency requires? Maybe I > could have a look at the kernel/mesa changes related to

[kwin] [Bug 357728] Dragging window leads to display freeze

https://bugs.kde.org/show_bug.cgi?id=357728 --- Comment #12 from Bernd Steinhauser --- (In reply to Bernd Steinhauser from comment #11) > (In reply to Thomas Lübking from comment #10) > > > layers.acceleration.disabled false > > layers.acceleration.disabled true >

[kwin] [Bug 357728] Dragging window leads to display freeze

https://bugs.kde.org/show_bug.cgi?id=357728 --- Comment #11 from Bernd Steinhauser --- (In reply to Thomas Lübking from comment #10) > > layers.acceleration.disabled false > layers.acceleration.disabled true This is the first thing I'm trying and so far it looks good,

[kwin] [Bug 357728] Dragging window leads to display freeze

https://bugs.kde.org/show_bug.cgi?id=357728 --- Comment #8 from Bernd Steinhauser --- (In reply to Thomas Lübking from comment #6) > Even gtk+ windows should just kick the NETWM moveresize in the WM > > > kwin4_effect_translucency > Try to disable this. Will do. > >

[kwin] [Bug 357728] Dragging window leads to display freeze

https://bugs.kde.org/show_bug.cgi?id=357728 --- Comment #7 from Thomas Lübking --- PS: and HW acceleration in FF! ("about:config" iirc, filter for "accel") -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 357728] Dragging window leads to display freeze

https://bugs.kde.org/show_bug.cgi?id=357728 --- Comment #5 from Bernd Steinhauser --- Created attachment 96538 --> https://bugs.kde.org/attachment.cgi?id=96538=edit qdbus-qt5 org.kde.KWin /KWin org.kde.KWin.supportInformation with compositing enabled -- You are

[kwin] [Bug 357728] Dragging window leads to display freeze

https://bugs.kde.org/show_bug.cgi?id=357728 --- Comment #4 from Bernd Steinhauser --- (In reply to Thomas Lübking from comment #3) > *cough* > > > Compositing > > === > > Compositing is not active Hm, that's interesting, I didn't notice that. It seems like I

[kwin] [Bug 357728] Dragging window leads to display freeze

https://bugs.kde.org/show_bug.cgi?id=357728 --- Comment #10 from Thomas Lübking --- > layers.acceleration.disabled false layers.acceleration.disabled true Isn't double negation a pleasure for everyone? ;-) -- You are receiving this mail because: You are watching all

[kwin] [Bug 357728] Dragging window leads to display freeze

https://bugs.kde.org/show_bug.cgi?id=357728 --- Comment #6 from Thomas Lübking --- Even gtk+ windows should just kick the NETWM moveresize in the WM > kwin4_effect_translucency Try to disable this. > electricBorderMaximize: true > electricBorderTiling: true and this

[kwin] [Bug 357728] Dragging window leads to display freeze

https://bugs.kde.org/show_bug.cgi?id=357728 --- Comment #9 from Bernd Steinhauser --- (In reply to Thomas Lübking from comment #7) > PS: and HW acceleration in FF! ("about:config" iirc, filter for "accel") apz.fling_accel_base_mult 1.0 apz.fling_accel_interval_ms 500

[kwin] [Bug 357728] Dragging window leads to display freeze

https://bugs.kde.org/show_bug.cgi?id=357728 --- Comment #2 from Bernd Steinhauser --- Created attachment 96537 --> https://bugs.kde.org/attachment.cgi?id=96537=edit qdbus-qt5 org.kde.KWin /KWin org.kde.KWin.supportInformation -- You are receiving this mail

[kwin] [Bug 357728] Dragging window leads to display freeze

https://bugs.kde.org/show_bug.cgi?id=357728 --- Comment #1 from Bernd Steinhauser --- Created attachment 96536 --> https://bugs.kde.org/attachment.cgi?id=96536=edit Last messages from journal when the freeze occured -- You are receiving this mail because: You are

[kwin] [Bug 357728] Dragging window leads to display freeze

https://bugs.kde.org/show_bug.cgi?id=357728 --- Comment #3 from Thomas Lübking --- *cough* > Compositing > === > Compositing is not active > I think (but I'm not sure here), I've even tried with the compositor switched > off. Wow. > I've seen this issue