https://bugs.kde.org/show_bug.cgi?id=369131
Thomas Lübking changed:
What|Removed |Added
CC||thomas.luebk...@gmail.com
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=369131
--- Comment #8 from Thomas Lübking ---
> 1366x768+1920+432
^
I suppose this to be the troublemaker.
The window asks to be bigger than your screen (no hackish attempt to be
maximized) and your screen geometry can supp
https://bugs.kde.org/show_bug.cgi?id=369131
--- Comment #10 from Thomas Lübking ---
If it's not partial, the window would be shrunk (for no reason)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=355506
--- Comment #2 from Thomas Lübking ---
Notice that no, we cannot rely on the drag distance setting (caused bugreports
and looks "slow", changed in some KDE 2 release to move instantly) nor involve
the doubleclick interval (since that can be rather long
https://bugs.kde.org/show_bug.cgi?id=356076
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=355787
Thomas Lübking changed:
What|Removed |Added
Resolution|LATER |INVALID
--- Comment #11 from Thomas Lübking -
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #80 from Thomas Lübking ---
(In reply to Rafael from comment #79)
> way to recover a visible screen. Only the cursor was visible. I needed to do
> "" to recover my desktop :(
Do you lock the screen over STR?
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=356107
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=341497
Thomas Lübking changed:
What|Removed |Added
CC||jbar...@gmail.com
--- Comment #47 from Thomas
https://bugs.kde.org/show_bug.cgi?id=340240
Thomas Lübking changed:
What|Removed |Added
CC||thomas.luebk...@gmail.com
--
You are receivin
https://bugs.kde.org/show_bug.cgi?id=340240
--- Comment #3 from Thomas Lübking ---
Is spectacle already shipped w/ 5.5?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=352427
--- Comment #14 from Thomas Lübking ---
DRI3 is enabled (unless you disabled it at runtime, check "env | grep
LIBGL_DRI3_DISABLE")
Please attach the output of "qdbus org.kde.KWin /KWin supportInformation"
--
You are receiving this mail because:
You a
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #83 from Thomas Lübking ---
It's related to a shader based, hyperfast multisamplig (FXAA) which, ie enabled
*while the GL context is created!*, turns the entire desktop blurry (but is
indeed especially notable on text - or other thin lines w
https://bugs.kde.org/show_bug.cgi?id=352427
--- Comment #16 from Thomas Lübking ---
(In reply to Martin Kostolný from comment #15)
> But there is a big chance I'm wrong...
Maybe, but you're right here. Sorry.
(shall teach me to no look too brief "dri2 and dri3 mentioned, option found, no
error ->
https://bugs.kde.org/show_bug.cgi?id=340240
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Version Fixed In|
https://bugs.kde.org/show_bug.cgi?id=352427
--- Comment #19 from Thomas Lübking ---
Debug out says that you're on KWin 4.11, you'd have to explicitly "export
KWIN_OPENGL_INTERFACE="egl"" to use EGL itfp.
=> You don't run into this bug at all but rather bug #336589
run
kwriteconfig --file kwi
https://bugs.kde.org/show_bug.cgi?id=356128
Thomas Lübking changed:
What|Removed |Added
Severity|normal |wishlist
--- Comment #1 from Thomas Lübking -
https://bugs.kde.org/show_bug.cgi?id=356128
--- Comment #2 from Thomas Lübking ---
Claimed deviation #1:
---
The script prefers restoring windows whereas SDIMA would take a new window a
broken state and continue to minimize windows on next invocation.
Claimed deviation #2 (on
https://bugs.kde.org/show_bug.cgi?id=350826
--- Comment #42 from Thomas Lübking ---
I don't forget you, I just have 100 unread mails in my inbox (no shit - and
it's 23:20 now ...)
The relevant ouput will be
> 'ID: 31457299 ;WMCLASS: "plasmashell" : "plasmashell" ;Caption: "Desktop —
> Plasma" '
https://bugs.kde.org/show_bug.cgi?id=350826
Thomas Lübking changed:
What|Removed |Added
Summary|[virtual box related?] Show |plasma desktop containment
|
https://bugs.kde.org/show_bug.cgi?id=356121
--- Comment #3 from Thomas Lübking ---
In the last tab of the settings dialog
a) Do you actually intend to use the IMAP SENDMAIL extension rather than an
smtp server? (afaics, gmail does NOT support that)
b) The Sent folder is apparently not "Sent", ran
https://bugs.kde.org/show_bug.cgi?id=356144
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=341497
Thomas Lübking changed:
What|Removed |Added
CC||l...@fairtragen.de
--- Comment #48 from Thomas
https://bugs.kde.org/show_bug.cgi?id=356141
--- Comment #1 from Thomas Lübking ---
KWin crashed, the backtrace suggests an imbalance in the shader un/loading
(apparently in the contrast effect, but the imbalance could have been caused
before)
This however might be a red herring: if plasmashell c
https://bugs.kde.org/show_bug.cgi?id=352427
--- Comment #21 from Thomas Lübking ---
(In reply to kamesh from comment #20)
> I guess the "export KWIN_OPENGL_INTERFACE="egl"" is not persistent across
> reboots but the issue seems to be resolved without it.
No, but you probably don't want to use E
https://bugs.kde.org/show_bug.cgi?id=364944
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=363224
Thomas Lübking changed:
What|Removed |Added
CC||marc_sm...@gmx.com
--- Comment #7 from Thomas
https://bugs.kde.org/show_bug.cgi?id=363224
--- Comment #9 from Thomas Lübking ---
Hum?
If you can reptoduce this at will, disable translucency and dialogparent
effects in "kcmshell5 kwineffects", if this "fixes" it, please re-enable either
independently to figure the culprit.
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=364954
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=363224
Thomas Lübking changed:
What|Removed |Added
CC||joaqv1n@gmail.com
--- Comment #10 from Tho
https://bugs.kde.org/show_bug.cgi?id=362531
--- Comment #12 from Thomas Lübking ---
KWindowSystem is ok, see https://bugs.kde.org/show_bug.cgi?id=364641#c6
It's a simple race condition - you check the state before starting to monitor
it, thus run into a gap and perpetuate the wrong idea until the
https://bugs.kde.org/show_bug.cgi?id=363224
--- Comment #13 from Thomas Lübking ---
*** Bug 365003 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365003
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=365004
Thomas Lübking changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=361154
Thomas Lübking changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=365004
Thomas Lübking changed:
What|Removed |Added
Attachment #99801|application/msword |text/plain
mime type|
https://bugs.kde.org/show_bug.cgi?id=365004
--- Comment #4 from Thomas Lübking ---
Can you please re-attach that as plaintext?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365004
--- Comment #6 from Thomas Lübking ---
Nvidia fits the pattern, please check against beforehand suspended compositor
and/or a rule to omit the request to block the compositor (see other bug)
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=365004
--- Comment #8 from Thomas Lübking ---
Der Treiber (vermutlich)
Der Compositor (das Ding, das Schatten etc. macht), Steam und 1000 andere
Sachen laufen unter OpenGL und Steam schaltet den Compositor ab - da scheint
der Treiber aus dem Tritt zu kommen.
https://bugs.kde.org/show_bug.cgi?id=365042
--- Comment #3 from Thomas Lübking ---
It'll likely demand that position (or configure itself there afterwards)
"Ignore requested geometry" (At least "apply initially", perhaps "force" is
required)
--
You are receiving this mail because:
You are watch
https://bugs.kde.org/show_bug.cgi?id=365042
--- Comment #4 from Thomas Lübking ---
PS: "kcmshell5 kwinoptions", you can configure the global placement strategy
there. No need for a rule here.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365042
--- Comment #6 from Thomas Lübking ---
can you please dump "xprop" and "xwininfo" on the window and attach the output?
xwininfo > ~/winecfg.info
xprop > ~/winecfg.props
The cursor turns into a "+" each time, then just click the window.
--
You
https://bugs.kde.org/show_bug.cgi?id=365042
--- Comment #9 from Thomas Lübking ---
The window certainly positions itself, but (required) setting "ignore requested
geometry" to "force" and "yes"(!) should prevent that. Otherwise there's a bug.
In that case please attach ~/.config/kwinrulesrc
--
https://bugs.kde.org/show_bug.cgi?id=361236
Thomas Lübking changed:
What|Removed |Added
CC||tho@gmx.net
--- Comment #15 from Thomas Lü
https://bugs.kde.org/show_bug.cgi?id=365170
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=365209
Thomas Lübking changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=358142
Thomas Lübking changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=365253
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=365255
Thomas Lübking changed:
What|Removed |Added
Assignee|kwin-bugs-n...@kde.org |mgraess...@kde.org
CC|
https://bugs.kde.org/show_bug.cgi?id=365267
Thomas Lübking changed:
What|Removed |Added
Component|general |Desktop Containment
Product|kwin
https://bugs.kde.org/show_bug.cgi?id=343891
--- Comment #15 from Thomas Lübking ---
Those wouldn't be avoided (local $d simply trumps cascading and moves to the
application default) and using simple config would kill kiosk.
--
You are receiving this mail because:
You are watching all bug change
https://bugs.kde.org/show_bug.cgi?id=365274
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=346024
Thomas Lübking changed:
What|Removed |Added
CC||denis.smirnov...@gmail.com
--- Comment #26 fro
https://bugs.kde.org/show_bug.cgi?id=365285
--- Comment #1 from Thomas Lübking ---
please provide the output of "xprop" on a window that doesn't work (run the
command in konsole and click the window when the cursor turns into a "+")
--
You are receiving this mail because:
You are watching all b
https://bugs.kde.org/show_bug.cgi?id=365209
--- Comment #3 from Thomas Lübking ---
> /usr/lib64/qt5/plugins/org.kde.kdecoration2/kwin5_aurorae.so
no, you're not (not when the crash occured, at least)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365209
--- Comment #5 from Thomas Lübking ---
run
kcmshell5 kwindecoration
the widget style is irrelevant
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365333
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=365254
--- Comment #3 from Thomas Lübking ---
lower the opacity over the drop zone?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365333
--- Comment #7 from Thomas Lübking ---
one didn't know about the new issue in the past.
a strategy out could be to query the renderer from kwin and still annoy users
(because of the severe impact, "deliberately" implies developer)
alternatively, the FB
https://bugs.kde.org/show_bug.cgi?id=365367
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=363224
Thomas Lübking changed:
What|Removed |Added
CC||rb03...@gmail.com
--- Comment #14 from Thomas
https://bugs.kde.org/show_bug.cgi?id=363224
--- Comment #15 from Thomas Lübking ---
latest dupe has a good trace:
Thread 1 (Thread 0x7f61d8bc8940 (LWP 28181)):
[KCrash Handler]
#6 0x0570 in ?? ()
#7 0x7f61d62bff50 in QObject::connect (sender=0x3664060,
signal=signal@entry=0x7f6
https://bugs.kde.org/show_bug.cgi?id=365367
--- Comment #6 from Thomas Lübking ---
thread #1 - the relevant one. watch for desktopPresenceChanged and failed
object creation in qtscript.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365455
Thomas Lübking changed:
What|Removed |Added
Product|kwin|KScreen
Assignee|kwin-bugs-n...@kde.
https://bugs.kde.org/show_bug.cgi?id=351399
--- Comment #9 from Thomas Lübking ---
(In reply to Martin Gräßlin from comment #7)
> that doesn't specify a position. Uh oh, what's going on there?
Either the window doesn't specify a position (what's good) or yet another
QWidget/Window call ending n
https://bugs.kde.org/show_bug.cgi?id=365464
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |BACKTRACE
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=365461
--- Comment #1 from Thomas Lübking ---
That frankly looks like a bug in the specific theme. The top elements seem
invalid and the lower right section is junk as well.
I'd contact the author of the theme to have him seek to fix it.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=365461
--- Comment #3 from Thomas Lübking ---
The (not so great) screenshot is linked as url
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=198175
--- Comment #77 from Thomas Lübking ---
It's an X11 property - you can query it using XLib/xcb API.
Adding a KWindowSystem getter sounds a bit off for technically only the
WM/compositor should ever read it.
The discussion back then was to shovel this
https://bugs.kde.org/show_bug.cgi?id=365465
--- Comment #4 from Thomas Lübking ---
ftr, change the settings in "kcmshell5 kwindecoration" - settings in "kcmshell5
style" are irrelevant here.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=351399
--- Comment #11 from Thomas Lübking ---
Yes, even if I had not known, I would have heard - but that is not the same as
enforcing the primary screen :-)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365593
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=361236
Thomas Lübking changed:
What|Removed |Added
CC||guenter.oh...@gmx.de
--- Comment #16 from Thom
https://bugs.kde.org/show_bug.cgi?id=365601
--- Comment #3 from Thomas Lübking ---
On could probably filter the decoration quads, but this sounds like a *very*
particular usecase - and therefore probably stupid (read: "extremely low
efficient solution") approach.
Mind elaborating which window yo
https://bugs.kde.org/show_bug.cgi?id=365465
--- Comment #7 from Thomas Lübking ---
Plastik is more or less an aurorae theme, so that's in pattern :-P
Breeze is presently really the *only* reliable decoration :-(
All others suffer from QML.
--
You are receiving this mail because:
You are watchi
https://bugs.kde.org/show_bug.cgi?id=365607
--- Comment #1 from Thomas Lübking ---
Please try to suspend the compositor (SHIFT+Alt+F12) when this happens and also
(just right now, no error condition required) attach the output of "qdbus
org.kde.KWin /KWin supportInformation"
--
You are receivin
https://bugs.kde.org/show_bug.cgi?id=365367
--- Comment #21 from Thomas Lübking ---
Could one simply pass a QPointer(c->effectWIndow()) in the
queuedconnection invokeMethod call?
In doubt using a lambda wrapper?
(Something that virtually has to happen on all queued invocation parameters
since th
https://bugs.kde.org/show_bug.cgi?id=365591
--- Comment #6 from Thomas Lübking ---
given the upload time and order:
I think Martin wants to see the information when compositing is not "enabled"
(need to restart plasmashell points something entirely different) on login, so
please confirm you did *
https://bugs.kde.org/show_bug.cgi?id=365591
--- Comment #7 from Thomas Lübking ---
ftr, I bet on bug #364641
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365591
--- Comment #10 from Thomas Lübking ---
No problem ;-)
And no: I'm pretty sure your both just facing bug #364641 (explanation of the
failure over there, it's in libplasma, though. KWin isn't the problem at all.
It's a simple race on the availability che
https://bugs.kde.org/show_bug.cgi?id=365367
--- Comment #24 from Thomas Lübking ---
It's likely troublesome as script API (thus "lambda wrapper")
The queued connection problem is systematic (and easy to understand) but
requiriung an exposure check everwhere frankly looks wonky and seems to beg fo
https://bugs.kde.org/show_bug.cgi?id=365650
--- Comment #1 from Thomas Lübking ---
please dump and attach the output of "xrandr -q" in the troublesome
single-screen situation (ie. after unplug/resume/windows lost)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360443
--- Comment #14 from Thomas Lübking ---
looks like a bug in the intewl driver (where the original report was EGL on
radeon, it's only the same symptom)
could be a dead lock, run "thread apply all bt" to dump all threads.
Also you best install debug sym
https://bugs.kde.org/show_bug.cgi?id=365601
--- Comment #5 from Thomas Lübking ---
> 1. browsers, well they respect it, but they respect the CSS more
use stylish, see userstyles.org - you likely would not want to invert images or
videos, would you??
You might notably like
https://userstyles.org/
https://bugs.kde.org/show_bug.cgi?id=365681
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=310005
Thomas Lübking changed:
What|Removed |Added
CC||lucas.hartm...@gmail.com
--- Comment #26 from
https://bugs.kde.org/show_bug.cgi?id=350826
Thomas Lübking changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=365685
Thomas Lübking changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=365685
--- Comment #3 from Thomas Lübking ---
I assume it's when keep below windows are lost (otherwise the value is
expectable)
Can you create a kwin rule (kcmshell5 kwinrules) that enforces plasmashell to
be of desktop type; then try to re-cause the problem.
https://bugs.kde.org/show_bug.cgi?id=365685
--- Comment #5 from Thomas Lübking ---
Hummm... it all points that direction, still.
Could you please export and attach the rule you created?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365685
--- Comment #7 from Thomas Lübking ---
> types=2
Revisit the match page - it matches the type ;-)
Just ensure to match desktop, override and normal windows so the rule will
actually apply.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=365685
--- Comment #9 from Thomas Lübking ---
On the first tab, the window matching (ie. which windows to apply this rule to)
can be configured and that's probably too sharp because of the selected type,
ie. the rule isn't applied to the window because it actu
https://bugs.kde.org/show_bug.cgi?id=365685
--- Comment #11 from Thomas Lübking ---
No, sorry
I've abandoned KDE few months ago and only help out on bugs (since my
experience didn't drop off me - and actually I wanted to and should have quit
bugs.kde.org on July 1st...)
Just edit the rule and o
https://bugs.kde.org/show_bug.cgi?id=350826
Thomas Lübking changed:
What|Removed |Added
CC||ensla...@protonmail.com
--- Comment #62 from T
https://bugs.kde.org/show_bug.cgi?id=365685
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=350826
--- Comment #63 from Thomas Lübking ---
@Jeremy, as a workaround create a kwin rule (this oc. requires you to use kwin
as WM ;-) to enforce the desktop to be of desktop type.
Ensure to match normal and "unmanged" windows as well to have the rule applie
https://bugs.kde.org/show_bug.cgi?id=365601
--- Comment #7 from Thomas Lübking ---
(In reply to Salvo "LtWorf" Tomaselli from comment #6)
> I use slack
And now have one more reason to hate it ...
> it is white and doesn't seem to be modifiable
Isn't that a webchat? (Ie. afaiu the local clients o
https://bugs.kde.org/show_bug.cgi?id=365685
--- Comment #16 from Thomas Lübking ---
This re-reads and re-applies the rules. Did you alter the match patterns (for
otherwise you were "lucky" to have the rules applied when the desktop was set
"desktop" and now ran into the override setting)
--
You
https://bugs.kde.org/show_bug.cgi?id=350826
--- Comment #65 from Thomas Lübking ---
According to the latest dupe, this isn't limited to desktop showing but the
type juggling also occurs when simply clicking the desktop when as a result the
desktop eg. moves above keep below windows.
--
You are
https://bugs.kde.org/show_bug.cgi?id=365726
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
1 - 100 of 1450 matches
Mail list logo