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=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
https://bugs.kde.org/show_bug.cgi?id=369131
Thomas Lübking changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=369832
Thomas Lübking changed:
What|Removed |Added
Ever confirmed|0 |1
https://bugs.kde.org/show_bug.cgi?id=369130
--- Comment #1 from Thomas Lübking ---
One (or both) of the monitors will go to deep sleep or the kscreen daemon
detaches them, the workspace shrinks, kwin keeps them in sight but when the
screen gets re-added doesn't see
https://bugs.kde.org/show_bug.cgi?id=369131
--- Comment #1 from Thomas Lübking ---
Please specify "the application" for KDE applications should restore geometry
"per screen" anyway and the client may reconfigure itself to that position
after mapping (ie. there're
https://bugs.kde.org/show_bug.cgi?id=368685
--- Comment #2 from Thomas Lübking ---
xdotool, and the forum says "slide conky off screen"
in that case, you just want to bind a kwin script that does this (and skip
shell and xdotool)
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=368003
--- Comment #1 from Thomas Lübking ---
> should match the outgoing message exactly, bite-wise
+100
> detect that we cannot submit our message in this way, remove the previously
> stored copy, upload a new one with no CTE:
https://bugs.kde.org/show_bug.cgi?id=350826
Thomas Lübking changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=367685
--- Comment #1 from Thomas Lübking ---
This belongs to either plasma-desktop (kickoff) or krunner. Maybe kglobalaccel
if some default binding is provided but certainly not kwin ;-)
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=367534
--- Comment #7 from Thomas Lübking ---
This is not a kwin bug, but please attach the output of glxinfo (to provide a
hint on why compositing may fail)
There's most likely a window (the dialog?) with uninitialized content
https://bugs.kde.org/show_bug.cgi?id=367554
--- Comment #7 from Thomas Lübking ---
No. The role was originally handled lowercased in kwin. This was implicitly
changed by no more keeping the value internally but relying on the
kwindowsystem value. As a result, the rule
https://bugs.kde.org/show_bug.cgi?id=366742
--- Comment #8 from Thomas Lübking ---
Some static backtrace won't get you anywhere reg. CPU load - this would only
work if kwin would be trapped in an infinite loop.
Suspend the compositor (SHIFT+Alt+F12), run qbittorrent
https://bugs.kde.org/show_bug.cgi?id=367534
--- Comment #5 from Thomas Lübking ---
> Can you please post the output of:
> qdbus org.kde.KWin /KWin supportInformation
It doesn't actually look like the compositor is running at all (hard to say on
the particular setup,
https://bugs.kde.org/show_bug.cgi?id=367554
Thomas Lübking changed:
What|Removed |Added
Summary|Special Window Settings |Special Window
https://bugs.kde.org/show_bug.cgi?id=367554
--- Comment #3 from Thomas Lübking ---
Smells related to bug #343709 - "mainwindow" is probably really "MainWindow" or
similar.
Please attach the ouput of "xprop" on a window you want to control this way.
--
You are
https://bugs.kde.org/show_bug.cgi?id=348227
Thomas Lübking changed:
What|Removed |Added
CC|thomas.luebk...@gmail.com |
--
You are
https://bugs.kde.org/show_bug.cgi?id=365918
--- Comment #14 from Thomas Lübking ---
Is rebooting required or does switching the compositor backend or restarting
kwin clear the stage as well?
You could disable the two effects but that would only provide negative
https://bugs.kde.org/show_bug.cgi?id=366794
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=358369
--- Comment #27 from Thomas Lübking ---
*** Bug 366794 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=365918
--- Comment #12 from Thomas Lübking ---
The flicker is due to the re-used buffer, the question is why one of them is
invalid but for the newly exposed area and this seems to be related to window
decorations.
Let's start with
https://bugs.kde.org/show_bug.cgi?id=366742
--- Comment #2 from Thomas Lübking ---
> Xorg and kwin_x11
Smells like something (qbittorrent? plasmashell?) will cause massive repaints.
Suspend the compositor (SHIFT+Alt+F12) and check the remaining load on Xorg
plus
https://bugs.kde.org/show_bug.cgi?id=366651
Thomas Lübking changed:
What|Removed |Added
See Also|
https://bugs.kde.org/show_bug.cgi?id=342326
Thomas Lübking changed:
What|Removed |Added
See Also|
https://bugs.kde.org/show_bug.cgi?id=365299
Thomas Lübking changed:
What|Removed |Added
Severity|major |normal
--- Comment
https://bugs.kde.org/show_bug.cgi?id=286146
--- Comment #62 from Thomas Lübking ---
Firefox in particular is unrelated to this bug since it doesn't use kxmlgui or
any KDE class.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=366498
--- Comment #4 from Thomas Lübking ---
Can you please provide more log data, ideally all, but at least starting w/ the
matching SELECT call (ie ">>> y17" in *this* case, could be a differet tag in
another try)
The reply looks
https://bugs.kde.org/show_bug.cgi?id=364633
--- Comment #13 from Thomas Lübking ---
Thanks for your efforts and sorry for the delay.
The only apparent pattern* is that they all seem to be quick tiled (at least it
looks like) so this really does seem to be the trigger.
https://bugs.kde.org/show_bug.cgi?id=361236
Thomas Lübking changed:
What|Removed |Added
CC||rosan...@lajt.hu
https://bugs.kde.org/show_bug.cgi?id=366126
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=351763
--- Comment #14 from Thomas Lübking ---
> I don't know if I am experiencing the same problem.
Please attach a backtrace*, otherwise one will never figure ;-)
* developer information tab in the crash dialog, the console
https://bugs.kde.org/show_bug.cgi?id=366097
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://bugs.kde.org/show_bug.cgi?id=361236
Thomas Lübking changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=361236
Thomas Lübking changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=366096
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=366091
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=362531
Thomas Lübking changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=366081
--- Comment #6 from Thomas Lübking ---
https://bugs.kde.org/show_bug.cgi?id=342716#c18
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=361236
Thomas Lübking changed:
What|Removed |Added
CC||sami.lie...@iki.fi
https://bugs.kde.org/show_bug.cgi?id=366012
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=365964
Thomas Lübking changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=347495
Thomas Lübking changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=365964
--- Comment #4 from Thomas Lübking ---
No.
Please install kwin-dbg, trigger the crash (run the fullscreen game) and attach
the new developer information from the crash dialog (just what you posted
before, but now it will
https://bugs.kde.org/show_bug.cgi?id=365988
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://bugs.kde.org/show_bug.cgi?id=361236
--- Comment #20 from Thomas Lübking ---
*** Bug 365988 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=365964
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=365913
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=341497
--- Comment #66 from Thomas Lübking ---
*** Bug 365913 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=365824
--- Comment #8 from Thomas Lübking ---
Please check against the xrender compositor, but
> if I minimize all running apps (empty desktop) it works and the calendar is
> shown as expected
really makes me believe it's the
https://bugs.kde.org/show_bug.cgi?id=365896
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://bugs.kde.org/show_bug.cgi?id=361236
Thomas Lübking changed:
What|Removed |Added
CC||kr...@free.fr
---
https://bugs.kde.org/show_bug.cgi?id=365799
--- Comment #15 from Thomas Lübking ---
I wanted to see KWin's opinion on the screen config ;-)
==> Did you try OpenGL 2.0?
Ftr, GLX_EXT_buffer_age is *not* supported (the listing in client extensions is
insufficient, one
https://bugs.kde.org/show_bug.cgi?id=365824
Thomas Lübking changed:
What|Removed |Added
See Also|
https://bugs.kde.org/show_bug.cgi?id=350826
Thomas Lübking changed:
What|Removed |Added
See Also|
https://bugs.kde.org/show_bug.cgi?id=365821
Thomas Lübking changed:
What|Removed |Added
Summary|Content of some windows not |Emacs stop damage
https://bugs.kde.org/show_bug.cgi?id=364633
--- Comment #10 from Thomas Lübking ---
This is on killing kwin, I assume?!
Please dump xprop and xwininfo on dolphin, qtcreator, smplayer and konqueror as
well as
ldd `which dolphin`
ldd `which konqueror`
ldd `which
https://bugs.kde.org/show_bug.cgi?id=365821
--- Comment #8 from Thomas Lübking ---
Random crashes in "foo" are not necessarily related to "bar" - this is about
emacs (apparently under kwin, maybe only even plasma) and (likely) damage
events.
I don't think it's a driver
https://bugs.kde.org/show_bug.cgi?id=365821
--- Comment #5 from Thomas Lübking ---
if it does even happen with xrender chances are good the client simply stops
causing damage events (for whatever reason)
you probably tried all backends on the same instance? can you
https://bugs.kde.org/show_bug.cgi?id=352445
--- Comment #14 from Thomas Lübking ---
the bug is not in kwin, likely bug #364641 (race condition in libplasma theme
code)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=365821
--- Comment #3 from Thomas Lübking ---
run "kcmshell5 kwincompositing"
it wasn't removed but the settings split so users won't find them easily
(unfortunately that's not a joke)
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=364633
--- Comment #8 from Thomas Lübking ---
> Many gtk
Please confirm this for anything that's *not* gtk3 because it could be a client
reaction to WM losses. (client side decoration and/or removing-this-nonsense
plugins on top)
https://bugs.kde.org/show_bug.cgi?id=364633
--- Comment #6 from Thomas Lübking ---
This does *only* affect "quick tiled" windows, right?
What's the state after this happens (window still quick tiled, ie. dragging it
away from the corner restores some size)?
NB: this
https://bugs.kde.org/show_bug.cgi?id=365824
--- Comment #1 from Thomas Lübking ---
please attach the output of "qdbus org.kde.KWin /KWin supportInformation" and
ensure this doesn't happen w/ suspended compositor (SHIFT+Alt+F12)
This only affects plasma windows, ie.
https://bugs.kde.org/show_bug.cgi?id=365799
--- Comment #10 from Thomas Lübking ---
The corruption looks very much like a driver bug, you see the buffer tiles
which partially contain junk.
Could be a buffer_age issue - check glxinfo for general support and in case
https://bugs.kde.org/show_bug.cgi?id=365821
--- Comment #1 from Thomas Lübking ---
> enable another rendered, but docs saying that there's no way to choose it
> now.
Hummwhat?
Please provide the output of "qdbus org.kde.KWin /KWin supportInformation" and
ensure that
https://bugs.kde.org/show_bug.cgi?id=198175
Thomas Lübking changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=365780
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=358369
Thomas Lübking changed:
What|Removed |Added
CC||zholeg...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=365726
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
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
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
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?
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
https://bugs.kde.org/show_bug.cgi?id=365685
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://bugs.kde.org/show_bug.cgi?id=350826
Thomas Lübking changed:
What|Removed |Added
CC|
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
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
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
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 #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
https://bugs.kde.org/show_bug.cgi?id=350826
Thomas Lübking changed:
What|Removed |Added
See Also|
https://bugs.kde.org/show_bug.cgi?id=365685
Thomas Lübking changed:
What|Removed |Added
See Also|
https://bugs.kde.org/show_bug.cgi?id=310005
Thomas Lübking changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=365681
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
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
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.
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
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
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
https://bugs.kde.org/show_bug.cgi?id=361236
Thomas Lübking changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=365593
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |DUPLICATE
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
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=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
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=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
https://bugs.kde.org/show_bug.cgi?id=365464
Thomas Lübking changed:
What|Removed |Added
Resolution|--- |BACKTRACE
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
https://bugs.kde.org/show_bug.cgi?id=365455
Thomas Lübking changed:
What|Removed |Added
Product|kwin|KScreen
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.
1 - 100 of 1287 matches
Mail list logo