[konsole] [Bug 365339] Several seconds delay switching to certain tabs

https://bugs.kde.org/show_bug.cgi?id=365339 Bernd Steinhauser changed: What|Removed |Added CC|

[kwin] [Bug 361241] Double click to maximize does not work in some situations

https://bugs.kde.org/show_bug.cgi?id=361241 --- Comment #7 from Bernd Steinhauser --- At least on my system (5.7.x) I can't reproduce the bug anymore. -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 361151] (Enhancement) Implement changing the mouse acceleration profile of libinput in Wayland.

https://bugs.kde.org/show_bug.cgi?id=361151 Bernd Steinhauser changed: What|Removed |Added CC|

[systemsettings] [Bug 350688] Mouse acceleration setting has no effect with libinput

https://bugs.kde.org/show_bug.cgi?id=350688 Bernd Steinhauser changed: What|Removed |Added CC|

[plasma-pa] [Bug 352042] Plasma Audio Applet Should Include Per App Volume Levels

https://bugs.kde.org/show_bug.cgi?id=352042 Bernd Steinhauser changed: What|Removed |Added CC|

[plasmashell] [Bug 360137] Low performance when moving mouse cursor over task manager tabs in panel

https://bugs.kde.org/show_bug.cgi?id=360137 --- Comment #28 from Bernd Steinhauser --- Just to give you some numbers, I let this system run for approximately one day. During this time, plasmashell (in two threads) on average consumed 20% of one CPU. It was then on

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #118 from Bernd Steinhauser --- Should add: I started with a new plasma config and a single panel, then connected/disconnected a display multiple times. -- You are receiving this mail because: You are watching

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #117 from Bernd Steinhauser --- Tested Qt 5.7.0 + Plasma 5.6.95 and still get this. So maybe part of the fix is in place, but some part is still missing. -- You are receiving this mail because: You are

[plasmashell] [Bug 360137] Low performance when moving mouse cursor over task manager tabs in panel

https://bugs.kde.org/show_bug.cgi?id=360137 --- Comment #27 from Bernd Steinhauser --- Just wanted to note that I still see this with 5.6.95 and it feels like it actually got worse. A lot of stuttering due to plasmashell's high CPU load. -- You are receiving this

[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup

https://bugs.kde.org/show_bug.cgi?id=346961 --- Comment #53 from Bernd Steinhauser --- You're going much too far. It's sufficient to remove the writable attribute. -- You are receiving this mail because: You are watching all bug changes.

[plasmashell] [Bug 360137] Low performance when moving mouse cursor over task manager tabs in panel

https://bugs.kde.org/show_bug.cgi?id=360137 --- Comment #26 from Bernd Steinhauser --- Should note: I don't have any rotated screens. -- You are receiving this mail because: You are watching all bug changes.

[plasmashell] [Bug 360137] Low performance when moving mouse cursor over task manager tabs in panel

https://bugs.kde.org/show_bug.cgi?id=360137 --- Comment #25 from Bernd Steinhauser --- Hm, bug 362247 gave me an idea. Normally, I'm using the following driver options for either amdgpu or radeon. The driver that is used does not matter the behavior is the same:

[plasmashell] [Bug 353975] Black screen on second display.

https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #22 from Bernd Steinhauser --- I have only "external" screens (not everybody's using a laptop :P). And they have a resolution of 1920x1200. I'd say: Wait for Plasma 5.7 and see if it's still there, because it

[plasmashell] [Bug 360137] Low performance when moving mouse cursor over task manager tabs in panel

https://bugs.kde.org/show_bug.cgi?id=360137 --- Comment #24 from Bernd Steinhauser --- For testing purposes, I downgraded Plasma to 5.5.5. I do still see the same behavior. I'm pretty sure that I didn't see it previously when I ran 5.5.x, because a laggy behavior like

[plasmashell] [Bug 353975] Black screen on second display.

https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #19 from Bernd Steinhauser --- You can have the bug with other resolutions as well and also if the screens have the same resolution. The resolution doesn't matter as far as I can tell. -- You are receiving this

[konsole] [Bug 358560] Konsole crashes when I unplug a second monitor

https://bugs.kde.org/show_bug.cgi?id=358560 --- Comment #6 from Bernd Steinhauser --- I have not seen any issues with konsole crashing or disappearing when disconnecting a screen during the last two months or so. I think that this was (somehow?) fixed. Maybe you can

[plasmashell] [Bug 360137] Low performance when moving mouse cursor over task manager tabs in panel

https://bugs.kde.org/show_bug.cgi?id=360137 --- Comment #23 from Bernd Steinhauser --- (In reply to Thomas Lübking from comment #22) > Smells related to the new feature to show progress in taskitems? Is there a way to test that? Can I build plasma without it? Would

[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

[kmahjongg] [Bug 361132] kmahjongg 16.04 fails to start after migrating KDE4 configuration

https://bugs.kde.org/show_bug.cgi?id=361132 Bernd Steinhauser changed: What|Removed |Added CC|

[kwin] [Bug 361241] Double click to maximize does not work in some situations

https://bugs.kde.org/show_bug.cgi?id=361241 --- Comment #3 from Bernd Steinhauser --- That fixes the problem, thanks. -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 361241] Double click to maximize does not work in some situations

https://bugs.kde.org/show_bug.cgi?id=361241 --- Comment #1 from Bernd Steinhauser --- Forgot to mention: I ran kwin at commit id ed1d32288b50647469fb0e000f21b849e286ca36 to test this. When using kwin at 95cbd7c1b3cdbe81fdee1682049bd08ab7fe99fb (parent), I cannot

[kwin] [Bug 361241] New: Double click to maximize does not work in some situations

https://bugs.kde.org/show_bug.cgi?id=361241 Bug ID: 361241 Summary: Double click to maximize does not work in some situations Product: kwin Version: 5.6.1 Platform: Exherbo Packages OS: Linux

[kwin] [Bug 360719] Secondary user actions popup remains visible

https://bugs.kde.org/show_bug.cgi?id=360719 Bernd Steinhauser changed: What|Removed |Added CC|

[kwin] [Bug 361091] Translucency lost when starting video using mpv bypassing the compositor

https://bugs.kde.org/show_bug.cgi?id=361091 --- Comment #10 from Bernd Steinhauser --- Maybe that will be a bit out of reach of this bug, but would the situation be better on wayland, especially when talking about video (i.e. mpv)? -- You are receiving this mail

[kwin] [Bug 361091] Translucency lost when starting video using mpv bypassing the compositor

https://bugs.kde.org/show_bug.cgi?id=361091 --- Comment #7 from Bernd Steinhauser --- (In reply to Thomas Lübking from comment #1) > _NET_WM_BYPASS_COMPOSITOR isn't specified for unredirection (leaving aside > that the specification is horrible in every aspect...) >

[kwin] [Bug 361091] New: Translucency lost when starting video using mpv bypassing the compositor

https://bugs.kde.org/show_bug.cgi?id=361091 Bug ID: 361091 Summary: Translucency lost when starting video using mpv bypassing the compositor Product: kwin Version: 5.6.0 Platform: Exherbo Packages OS: Linux

[plasmashell] [Bug 360621] plasmashell hangs when moving panel

https://bugs.kde.org/show_bug.cgi?id=360621 --- Comment #5 from Bernd Steinhauser --- Yes, looks good. Haven't seen it yet, at least. If so I'll let you know. Thanks. -- You are receiving this mail because: You are watching all bug changes.

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #54 from Bernd Steinhauser --- (In reply to Theresa from comment #53) > I have my laptop connected to a HDMI monitor as well, as soon as I press the > "power off" button when I take a break/lunch break... the

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #51 from Bernd Steinhauser --- Something that never happened before to me: Yesterday, plasmashell moved both panels to one screen, so far normal. Today, both panels are gone. Possibly moved somewhere I can't see

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #48 from Bernd Steinhauser --- (In reply to cherenz from comment #45) > (In reply to Bernd Steinhauser from comment #44) > > This is getting repetitive. The bug is not fixed by Qt 5.6, it's not fixed > > by KF5

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #37 from Bernd Steinhauser --- Nope, been using Qt 5.6 for 2-3 weeks now and it did not improve things. Neither the -rc, nor the release version. -- You are receiving this mail because: You are watching all bug

[plasmashell] [Bug 360621] plasmashell hangs when moving panel

https://bugs.kde.org/show_bug.cgi?id=360621 --- Comment #2 from Bernd Steinhauser --- Yes, all three patches were applied before building Qt 5.6.0. Does not matter for this one, though. This happens with and without the patches. -- You are receiving this mail

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

https://bugs.kde.org/show_bug.cgi?id=356225 Bernd Steinhauser changed: What|Removed |Added CC|

[plasmashell] [Bug 360621] New: plasmashell hangs when moving panel

https://bugs.kde.org/show_bug.cgi?id=360621 Bug ID: 360621 Summary: plasmashell hangs when moving panel Product: plasmashell Version: 5.5.95 Platform: Exherbo Packages OS: Linux Status: UNCONFIRMED

[KScreen] [Bug 360430] kscreen randomly rewrites screen configuration

https://bugs.kde.org/show_bug.cgi?id=360430 --- Comment #5 from Bernd Steinhauser --- As I don't see this every time, I guess there is a race going on. To me, it looks like kscreen tries to look for a config, when some daemon or backend is sometimes not available to

[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected

https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #44 from Bernd Steinhauser --- This is getting repetitive. The bug is not fixed by Qt 5.6, it's not fixed by KF5 5.20 and neither Plasma 5.5.95. If you don't see, you're lucky (congrats), but the bug is still

[KScreen] [Bug 360430] kscreen randomly rewrites screen configuration

https://bugs.kde.org/show_bug.cgi?id=360430 --- Comment #3 from Bernd Steinhauser --- It's easier to remove write access to the file, but that still does not solve the problem at all. -- You are receiving this mail because: You are watching all bug changes.

[plasmashell] [Bug 360173] Plasma freeze sometime with notification & high load CPU and RAM

https://bugs.kde.org/show_bug.cgi?id=360173 Bernd Steinhauser changed: What|Removed |Added CC|

[plasmashell] [Bug 360137] Low performance when moving mouse cursor over task manager tabs in panel

https://bugs.kde.org/show_bug.cgi?id=360137 --- Comment #20 from Bernd Steinhauser --- hw accel for firefox does not make a significant difference. Tab changing in konsole, kate can also be used to trigger the stuttering. To me it seemed like it might have something

[plasmashell] [Bug 360137] Low performance when moving mouse cursor over task manager tabs in panel

https://bugs.kde.org/show_bug.cgi?id=360137 --- Comment #17 from Bernd Steinhauser --- Well, there is definitely something wrong with kwin as well, but I have yet to find out the details. For example, sometimes it does not respond to a double-click on the window

[KScreen] [Bug 360430] kscreen randomly rewrites screen configuration

https://bugs.kde.org/show_bug.cgi?id=360430 --- Comment #1 from Bernd Steinhauser --- Created attachment 97851 --> https://bugs.kde.org/attachment.cgi?id=97851=edit screen configuration -- You are receiving this mail because: You are watching all bug changes.

[KScreen] [Bug 360430] New: kscreen randomly rewrites screen configuration

https://bugs.kde.org/show_bug.cgi?id=360430 Bug ID: 360430 Summary: kscreen randomly rewrites screen configuration Product: KScreen Version: 5.5.95 Platform: Exherbo Packages OS: Linux Status: UNCONFIRMED

[plasmashell] [Bug 360137] Low performance when moving mouse cursor over task manager tabs in panel

https://bugs.kde.org/show_bug.cgi?id=360137 --- Comment #15 from Bernd Steinhauser --- Yes, I'm sure about that. I will see if I can reproduce it somehow. Is there a way to find out *what* kwin or plasmashell are doing when those issues occur? gdb? -- You are

[plasmashell] [Bug 360137] Low performance when moving mouse cursor over task manager tabs in panel

https://bugs.kde.org/show_bug.cgi?id=360137 --- Comment #13 from Bernd Steinhauser --- I'm not sure, but it could be related: Yesterday, after letting the system run for 1 day without restarting anything desktop-related, I observed a stuttering performance when

[frameworks-kded] [Bug 360245] kded crashing with Qt 5.6.0-rc

https://bugs.kde.org/show_bug.cgi?id=360245 --- Comment #3 from Bernd Steinhauser --- Thanks for that hint. building polkit-qt scm did actually fix kded and other things improved as well (i.e. kmix and akregator weren't showing up in the systray). Maybe it would be a

[plasmashell] [Bug 360137] Low performance when moving mouse cursor over task manager tabs in panel

https://bugs.kde.org/show_bug.cgi?id=360137 --- Comment #10 from Bernd Steinhauser --- kded crashes and therefore is not running. See bug 360245. I've had it running a couple of times and then it complained about blocking dbus calls. btw, I haven't seen memory

[frameworks-kded] [Bug 360245] New: kded crashing with Qt 5.6.0-rc

https://bugs.kde.org/show_bug.cgi?id=360245 Bug ID: 360245 Summary: kded crashing with Qt 5.6.0-rc Product: frameworks-kded Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity:

[frameworks-kded] [Bug 360245] kded crashing with Qt 5.6.0-rc

https://bugs.kde.org/show_bug.cgi?id=360245 --- Comment #1 from Bernd Steinhauser --- Created attachment 97757 --> https://bugs.kde.org/attachment.cgi?id=97757=edit Output of coredumpctl -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 360137] Low performance when moving mouse cursor over task manager tabs in panel

https://bugs.kde.org/show_bug.cgi?id=360137 --- Comment #8 from Bernd Steinhauser --- I meant plasmashell. It's interesting to see how, the plasmashell cpu usage instantly peaks to 70-100% when moving the mouse. Given that's only the usage of one cpu (so total would

[kwin] [Bug 360137] Low performance when moving mouse cursor over task manager tabs in panel

https://bugs.kde.org/show_bug.cgi?id=360137 --- Comment #6 from Bernd Steinhauser --- (In reply to Thomas Lübking from comment #5) > (In reply to Bernd Steinhauser from comment #4) > > > So it looks more like it's a plasma bug. Theory: plasma temporarily consumes > >

[kwin] [Bug 360137] Low performance when moving mouse cursor over task manager tabs in panel

https://bugs.kde.org/show_bug.cgi?id=360137 --- Comment #4 from Bernd Steinhauser --- (In reply to Thomas Lübking from comment #3) > > the cursor jumps for 1 to 1.5 seconds > The cursor should be done in hardware and painted directly into the scanout > buffer. > >

[kwin] [Bug 360137] Low performance when moving mouse cursor over task manager tabs in panel

https://bugs.kde.org/show_bug.cgi?id=360137 --- Comment #2 from Bernd Steinhauser --- Created attachment 97698 --> https://bugs.kde.org/attachment.cgi?id=97698=edit glxinfo -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 360137] Low performance when moving mouse cursor over task manager tabs in panel

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

[KScreen] [Bug 360113] New: Configured and Applied Screen Config do not match

https://bugs.kde.org/show_bug.cgi?id=360113 Bug ID: 360113 Summary: Configured and Applied Screen Config do not match Product: KScreen Version: 5.5.95 Platform: Exherbo Packages OS: Linux Status: UNCONFIRMED

[KScreen] [Bug 356884] kscreen messes with original xrandr config, does not respect saved config, and apply defined config only on the second try.

https://bugs.kde.org/show_bug.cgi?id=356884 Bernd Steinhauser changed: What|Removed |Added CC|

[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup

https://bugs.kde.org/show_bug.cgi?id=346961 Bernd Steinhauser changed: What|Removed |Added CC|

[konsole] [Bug 358560] Konsole crashes when I unplug a second monitor

https://bugs.kde.org/show_bug.cgi?id=358560 --- Comment #5 from Bernd Steinhauser --- Right, but killing it will also kill processes running in the konsole session, which I really would like to avoid. Anyway, maybe this should be moved into a separate bug, because

[plasmashell] [Bug 336570] Task list not updated in multiscreen setup

https://bugs.kde.org/show_bug.cgi?id=336570 --- Comment #19 from Bernd Steinhauser --- Ok, was a bit fast there. I missed, that you have to come from the side of showing only tasks from the current screen on all screens featuring a task list. It does work if you let

[kdelibs] [Bug 154839] Allow alternate shortcuts in list of global shortcuts

https://bugs.kde.org/show_bug.cgi?id=154839 --- Comment #18 from Bernd Steinhauser --- In Plasma 5 at least this feature is present, so I guess this can be closed. -- You are receiving this mail because: You are watching all bug changes.

[plasmashell] [Bug 341674] High CPU load when using second panel in multiscreen setup

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

[kwin] [Bug 357988] Black screen when reconnecting display

https://bugs.kde.org/show_bug.cgi?id=357988 --- Comment #17 from Bernd Steinhauser --- FYI, a bug was reported upstream, the issue was found and got fixed: https://bugs.freedesktop.org/show_bug.cgi?id=93746 -- You are receiving this mail because: You are watching

[plasmashell] [Bug 336570] Task list not updated in multiscreen setup

https://bugs.kde.org/show_bug.cgi?id=336570 --- Comment #18 from Bernd Steinhauser --- I didn't really try this, because multiple panels for me caused massive performance issues (opened a bug for that), so I couldn't use them. Now that you mentioned it, I tried again

[konsole] [Bug 358560] Konsole crashes when I unplug a second monitor

https://bugs.kde.org/show_bug.cgi?id=358560 --- Comment #2 from Bernd Steinhauser --- I did notice, that for me, it's not actually crashing, but konsole just disappears (as in not visible anymore). The process is reparanted to init and childs run until I kill

[kwin] [Bug 343661] stops drawing window content after some time, likely SyncObject related

https://bugs.kde.org/show_bug.cgi?id=343661 --- Comment #57 from Bernd Steinhauser --- Can confirm, that KWIN_EXPLICIT_SYNC doesn't change the behavior. However, I noticed that it might be a bit driver-dependent. For my GPU (AMD Kaveri), I can use two different KMS

[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 #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 #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 >

[konsole] [Bug 358560] Konsole crashes when I unplug a second monitor

https://bugs.kde.org/show_bug.cgi?id=358560 Bernd Steinhauser changed: What|Removed |Added CC|

[kwin] [Bug 357988] Black screen when reconnecting display

https://bugs.kde.org/show_bug.cgi?id=357988 --- Comment #12 from Bernd Steinhauser --- (In reply to Thomas Lübking from comment #11) > That would suggest that switching the VT would alter the stack position of > the plasma window, would it? Unlikely. Also interaction

[kwin] [Bug 357988] Black screen when reconnecting display

https://bugs.kde.org/show_bug.cgi?id=357988 --- Comment #14 from Bernd Steinhauser --- (In reply to Thomas Lübking from comment #13) > If you > - suspend the compositor > - run glxgears > - move it to be partially on the left and partially on the (middle) DP > output

[kwin] [Bug 357988] Black screen when reconnecting display

https://bugs.kde.org/show_bug.cgi?id=357988 --- Comment #16 from Bernd Steinhauser --- (In reply to Thomas Lübking from comment #15) > (In reply to Bernd Steinhauser from comment #14) > > Around 60 fps, no change there. The left part of glxgears is still updated, > >

[kwin] [Bug 357988] Black screen when reconnecting display

https://bugs.kde.org/show_bug.cgi?id=357988 --- Comment #10 from Bernd Steinhauser --- Two more things that might be worth mentioning: 1. I switched to Console with the screen disconnected and back to see if it occurs at well. After Reconnecting the screen, I saw

[kwin] [Bug 342326] window contents freeze

https://bugs.kde.org/show_bug.cgi?id=342326 --- Comment #28 from Bernd Steinhauser --- (In reply to Thomas Lübking from comment #26) > vdpau specific: does it > a) start to update when you suspend the compositor > b) still update when you resume the compositor

[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 357988] Black screen when reconnecting display

https://bugs.kde.org/show_bug.cgi?id=357988 --- Comment #9 from Bernd Steinhauser --- (In reply to Thomas Lübking from comment #8) > - What's the state when just suspending the compositor - is the screen black > as well? No, that works fine. > - What if you even

[kwin] [Bug 357988] New: Black screen when reconnecting display

https://bugs.kde.org/show_bug.cgi?id=357988 Bug ID: 357988 Summary: Black screen when reconnecting display Product: kwin Version: 5.5.3 Platform: Exherbo Packages OS: Linux Status: UNCONFIRMED Severity:

[kwin] [Bug 357988] Black screen when reconnecting display

https://bugs.kde.org/show_bug.cgi?id=357988 --- Comment #5 from Bernd Steinhauser --- (In reply to Thomas Lübking from comment #1) > please dump "qdbus org.kde.KWin /KWin supportInformation" before and when > this happens and ideally also when "resolving" the

[kwin] [Bug 357988] Black screen when reconnecting display

https://bugs.kde.org/show_bug.cgi?id=357988 --- Comment #6 from Bernd Steinhauser --- Created attachment 96639 --> https://bugs.kde.org/attachment.cgi?id=96639=edit glxinfo -l -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 356882] No compositing with Mesa 11.1.0 (EGL 1.5) and Plasma/KWin 5.5.1 when using EGL OpenGL interface

https://bugs.kde.org/show_bug.cgi?id=356882 Bernd Steinhauser changed: What|Removed |Added CC|

[kwin] [Bug 357988] Black screen when reconnecting display

https://bugs.kde.org/show_bug.cgi?id=357988 --- Comment #7 from Bernd Steinhauser --- (In reply to Bernd Steinhauser from comment #5) > During the disconnect, the only difference is the removed screen: > -Number of Screens: 2 > +Number of Screens: 3 > > +Name:

[kwin] [Bug 357988] Black screen when reconnecting display

https://bugs.kde.org/show_bug.cgi?id=357988 --- Comment #2 from Bernd Steinhauser --- Created attachment 96637 --> https://bugs.kde.org/attachment.cgi?id=96637=edit Log output when changing the screen -- You are receiving this mail because: You are watching all

[kwin] [Bug 357988] Black screen when reconnecting display

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

[kwin] [Bug 342326] window contents freeze

https://bugs.kde.org/show_bug.cgi?id=342326 --- Comment #27 from Bernd Steinhauser --- (In reply to Thomas Lübking from comment #26) > vdpau specific: does it > a) start to update when you suspend the compositor > b) still update when you resume the compositor

[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 #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 #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 342326] window contents freeze

https://bugs.kde.org/show_bug.cgi?id=342326 Bernd Steinhauser changed: What|Removed |Added CC|

[kwin] [Bug 343661] stops drawing window content after some time, likely SyncObject related

https://bugs.kde.org/show_bug.cgi?id=343661 Bernd Steinhauser changed: What|Removed |Added CC|

[KScreen] [Bug 357727] New: Failed to retrieve current config: "Backend invalidated"

https://bugs.kde.org/show_bug.cgi?id=357727 Bug ID: 357727 Summary: Failed to retrieve current config: "Backend invalidated" Product: KScreen Version: 5.5.2 Platform: Exherbo Packages OS: Linux

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

https://bugs.kde.org/show_bug.cgi?id=357728 Bug ID: 357728 Summary: Dragging window leads to display freeze Product: kwin Version: 5.5.2 Platform: Exherbo Packages OS: Linux Status: UNCONFIRMED Severity:

[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

[plasmashell] [Bug 356954] plasmashell hangs when desktop settings dialog is moved to another screen

https://bugs.kde.org/show_bug.cgi?id=356954 Bernd Steinhauser changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME

[plasmashell] [Bug 356954] New: plasmashell hangs when desktop settings dialog is moved to another screen

https://bugs.kde.org/show_bug.cgi?id=356954 Bug ID: 356954 Summary: plasmashell hangs when desktop settings dialog is moved to another screen Product: plasmashell Version: 5.5.0 Platform: Exherbo Packages

[plasmashell] [Bug 355953] Desktop on screens are switched on restart

https://bugs.kde.org/show_bug.cgi?id=355953 --- Comment #3 from Bernd Steinhauser --- Another interesting observation. Yesterday Plasma moved the panel, after disconnecting one screen. And it moved it onto the screen I just disconnected. Interestingly, when

[plasmashell] [Bug 355953] Desktop on screens are switched on restart

https://bugs.kde.org/show_bug.cgi?id=355953 --- Comment #2 from Bernd Steinhauser --- Just wanted to add: The black screen is usable as in Windows can be moved there, maximized etc. The application switcher can appear on that screen as well. (So kwin seems to work

[plasmashell] [Bug 349482] After resume from suspend, non-primary display in multi-screen setup is black

https://bugs.kde.org/show_bug.cgi?id=349482 Bernd Steinhauser changed: What|Removed |Added CC|

[plasmashell] [Bug 353975] Black screen on second display.

https://bugs.kde.org/show_bug.cgi?id=353975 Bernd Steinhauser changed: What|Removed |Added CC|

  1   2   >