https://bugs.kde.org/show_bug.cgi?id=361151
Bernd Steinhauser changed:
What|Removed |Added
CC||li...@bernd-steinhauser.de
--
You are
https://bugs.kde.org/show_bug.cgi?id=353825
Bernd Lentes changed:
What|Removed |Added
CC||bernd.lentes@helmholtz-muen
https://bugs.kde.org/show_bug.cgi?id=353825
--- Comment #29 from Bernd Lentes ---
Wrong question.
Monty, which nomachine version did you try ?
Bernd
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=353825
--- Comment #31 from Bernd Lentes ---
Monty, i'm a bit confused.
You wrote: I downloaded and installed nomachine. I did not experience the
same DCMInit issue and the desktop did load remotely.
Some comments later you said:
I did do some te
https://bugs.kde.org/show_bug.cgi?id=353825
--- Comment #33 from Bernd Lentes ---
OK. My first impression is that this points very clearly to a KDE bug.
But does not FreeNX and X2Go depend on libraries from nomachine ?
So that they have the same or a similiar codebase ?
Bernd
--
You are
https://bugs.kde.org/show_bug.cgi?id=353825
--- Comment #35 from Bernd Lentes ---
Hi,
sorry to ask something very fundamental, but this is my first time i'm
participating in a bug tracking system.
Status "confirmed" means that the KDE Developer say "Yes, that's a bug in
https://bugs.kde.org/show_bug.cgi?id=365339
Bernd Steinhauser changed:
What|Removed |Added
CC||li...@bernd-steinhauser.de
--
You are
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.
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 this one
actually talks about
https://bugs.kde.org/show_bug.cgi?id=346961
Bernd Steinhauser changed:
What|Removed |Added
CC||li...@bernd-steinhauser.de
--
You are
https://bugs.kde.org/show_bug.cgi?id=356884
Bernd Steinhauser changed:
What|Removed |Added
CC||li...@bernd-steinhauser.de
--
You are
Severity: normal
Priority: NOR
Component: kcm
Assignee: se...@kde.org
Reporter: li...@bernd-steinhauser.de
I'm on 5.5.95, but I've seen this since 5.4 at least.
As kscreen does not (always) respect the saved config, I have to reconfigure my
scr
: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: li...@bernd-steinhauser.de
Since 5.5.95, I've noticed that moving the mouse cursor over the window tabs in
the task ma
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&action=edit
qdbus-qt5 org.kde.KWin /KWin org.kde.KWin.supportInformation
--
You are receiving this mail because:
You are w
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&action=edit
glxinfo
--
You are receiving this mail because:
You are watching all bug changes.
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.
>
> Does any
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
> > a
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 be 400% on thi
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&action=edit
Output of coredumpctl
--
You are receiving this mail because:
You are watching all bug changes.
: crash
Priority: NOR
Component: general
Assignee: afies...@kde.org
Reporter: li...@bernd-steinhauser.de
CC: kdelibs-b...@kde.org
Since updating to Qt 5.6.0-rc, I get a reproducible crash in kded leading to
misbehaviour of the desktop. See the
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 consumption of eith
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 good idea to make
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 playing a video. For
that, i
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 receiving this mail because
Severity: normal
Priority: NOR
Component: common
Assignee: se...@kde.org
Reporter: li...@bernd-steinhauser.de
I've seen this a lot since 5.5.95. I'm not sure if I saw it before, if so then
it happened only rarely.
I have a 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&action=edit
screen configuration
--
You are receiving this mail because:
You are watching all bug changes.
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
decoration, which should lead to
https://bugs.kde.org/show_bug.cgi?id=360137
--- Comment #19 from Bernd Steinhauser ---
(In reply to Thomas Lübking from comment #18)
> Doubleclick sounds like related to bug #357450 but should be resolved in
> your KWin?
I've never had this before updating to 5.5.95. But now that you
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 to do with window management
https://bugs.kde.org/show_bug.cgi?id=360173
Bernd Steinhauser changed:
What|Removed |Added
CC||li...@bernd-steinhauser.de
--- Comment #8
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.
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 there, as
po
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 retrieve the config
Severity: normal
Priority: NOR
Component: Panel
Assignee: plasma-b...@kde.org
Reporter: li...@bernd-steinhauser.de
Have not seen this happening in Plasma 5.5, but only since 5.5.95.
I should mention, that I performed the upgrade to Qt 5.6 at the same time,
currently
https://bugs.kde.org/show_bug.cgi?id=356225
Bernd Steinhauser changed:
What|Removed |Added
CC||li...@bernd-steinhauser.de
--- Comment #34
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 because:
You are watching all bug
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 changes.
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 5.2
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 them.
Changing the s
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 panel/taskbar
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.
https://bugs.kde.org/show_bug.cgi?id=360137
--- Comment #21 from Bernd Steinhauser ---
Now on 5.6.0, this does still happen.
One thing I noticed recently: If I copy a file using dolphin, plasmashell
becomes unresponsive. Like I can't use the task manager to switch screens,
can't us
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 mail because:
You are wat
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 watching all bug changes.
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 all bug changes.
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 rank 1, right before Xorg with
https://bugs.kde.org/show_bug.cgi?id=352042
Bernd Steinhauser changed:
What|Removed |Added
CC||li...@bernd-steinhauser.de
--- Comment #5
https://bugs.kde.org/show_bug.cgi?id=352042
--- Comment #6 from Bernd Steinhauser ---
Sorry, forget what I just said.
Somehow plasma-pa sneaked through my update session and was still at 5.6.5.
With 5.6.95, it works as expected, thanks. ;)
--
You are receiving this mail because:
You are
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.
https://bugs.kde.org/show_bug.cgi?id=341143
Bernd Paysan changed:
What|Removed |Added
CC||bernd.pay...@gmx.de
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=349482
Bernd Steinhauser changed:
What|Removed |Added
CC||li...@bernd-steinhauser.de
--- Comment #5
https://bugs.kde.org/show_bug.cgi?id=355953
Bernd Steinhauser changed:
What|Removed |Added
CC||li...@bernd-steinhauser.de
--- Comment #1
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 properly.)
However, the
https://bugs.kde.org/show_bug.cgi?id=353975
Bernd Steinhauser changed:
What|Removed |Added
CC||li...@bernd-steinhauser.de
--- Comment #11
Severity: wishlist
Priority: NOR
Component: Multi-screen support
Assignee: aleix...@kde.org
Reporter: li...@bernd-steinhauser.de
CC: plasma-b...@kde.org
I'm using the application dashboard as an application launcher. (BTW, there
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
reconnecting, it wasn't moved bac
https://bugs.kde.org/show_bug.cgi?id=355953
--- Comment #5 from Bernd Steinhauser ---
Have to admit, this is getting funny now.
Today when starting the computer, the panel bounced 4 times between two screens
before resting on one of them.
What the …? :D
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=356859
Bernd Weigelt changed:
What|Removed |Added
CC||weigelt.be...@web.de
--- Comment #1 from Bernd
https://bugs.kde.org/show_bug.cgi?id=356859
Bernd Weigelt changed:
What|Removed |Added
CC|weigelt.be...@web.de|
--
You are receiving this mail because:
You
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Multi-screen support
Assignee: aleix...@kde.org
Reporter: li...@bernd-steinhauser.de
CC: plasma-b...@kde.org
Wanted to setup a new background on one
https://bugs.kde.org/show_bug.cgi?id=356954
Bernd Steinhauser changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=341143
--- Comment #145 from Bernd Paysan ---
I have my free software projects myself, and I understand that you occasionally
want to rewrite something from scratch. Usually, when the main features have
been bolted on later, and make the whole thing a
https://bugs.kde.org/show_bug.cgi?id=342326
Bernd Steinhauser changed:
What|Removed |Added
CC||li...@bernd-steinhauser.de
--- Comment #24
https://bugs.kde.org/show_bug.cgi?id=342326
--- Comment #25 from Bernd Steinhauser ---
Created attachment 96535
--> https://bugs.kde.org/attachment.cgi?id=96535&action=edit
qdbus-qt5 org.kde.KWin /KWin org.kde.KWin.supportInformation
--
You are receiving this mail because:
You are w
https://bugs.kde.org/show_bug.cgi?id=343661
Bernd Steinhauser changed:
What|Removed |Added
CC||li...@bernd-steinhauser.de
--
You are
https://bugs.kde.org/show_bug.cgi?id=342500
Bernd Steinhauser changed:
What|Removed |Added
CC||li...@bernd-steinhauser.de
--
You are
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: common
Assignee: dvra...@kde.org
Reporter: li...@bernd-steinhauser.de
Since some time, I think since version 5.5, kscreen likes to spam the logs with
the message:
kscreen:
: normal
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: li...@bernd-steinhauser.de
Now I am aware, that this is possibly a bug in the display driver that is
triggered by kwin.
If this is the case, what I'm here hoping for
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&action=edit
Last messages from journal when the freeze occured
--
You are receiving this mail because:
You are watching
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&action=edit
qdbus-qt5 org.kde.KWin /KWin org.kde.KWin.supportInformation
--
You are receiving this mail because:
You are w
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 see
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&action=edit
qdbus-qt5 org.kde.KWin /KWin org.kde.KWin.supportInformation with compositing
enabled
--
You are receiving th
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.
> > e
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.flin
https://bugs.kde.org/show_bug.cgi?id=356882
Bernd Steinhauser changed:
What|Removed |Added
CC||li...@bernd-steinhauser.de
--
You are
: normal
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: li...@bernd-steinhauser.de
This sounds very similar to bug 353975, but I'm pretty sure, that there are two
bugs, one in plasmashell and one in kwin or X11 or driver. bug 3
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, I haven&
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&action=edit
Log output when changing the screen
--
You are receiving this mail because:
You are watching all bug changes.
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&action=edit
qdbus-qt5 org.kde.KWin /KWin org.kde.KWin.supportInformation
--
You are receiving this mail because:
You are w
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 situa
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&action=edit
glxinfo -l
--
You are receiving this mail because:
You are watching all bug changes.
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: DisplayPor
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 afterwards?
I&#x
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_x1
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 screen corruption.
However
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 afterwards?
Not sur
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 w/ the plasma
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 and
>
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,
> > the right
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:
Option "Tea
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.
https://bugs.kde.org/show_bug.cgi?id=342326
--- Comment #29 from Bernd Steinhauser ---
(In reply to Bernd Steinhauser from comment #28)
> (In reply to Thomas Lübking from comment #26)
> > vdpau specific: does it
> > a) start to update when you suspend the compositor
> > b)
https://bugs.kde.org/show_bug.cgi?id=358560
Bernd Steinhauser changed:
What|Removed |Added
CC||li...@bernd-steinhauser.de
--- Comment #1
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
> This i
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 working again once he switched
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 switches
between side
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 translucency and see if
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: effects-various
Assignee: kwin-bugs-n...@kde.org
Reporter: li...@bernd-steinhauser.de
Tried with OpenGL 2.0 and 3.1, XRender, EGL, GLX, all the same.
Transparancy comes back
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...)
>
> This h
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 because:
You are watching all
801 - 900 of 924 matches
Mail list logo
