[kwin] [Bug 369131] Closed application keeps its size when closed even if started on another screen

[Thomas Lübking via KDE Bugzilla]

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.

[kwin] [Bug 369131] Closed application keeps its size when closed even if started on another screen

[Thomas Lübking via KDE Bugzilla]

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 support this, so you don't need/want to
shrink the window.

Try instead


diff --git a/manage.cpp b/manage.cpp
index 4198e60..3cbfb9e 100644
--- a/manage.cpp
+++ b/manage.cpp
@@ -433,14 +433,14 @@ bool Client::manage(xcb_window_t w, bool isMapped)
 // i intended a second check on cs < area.size() ("the managed
client ("minus border") is smaller
 // than the workspace") but gtk / gimp seems to store it's size
including the decoration,
 // thus a former maximized window wil become non-maximized
-bool keepInFsArea = false;
+bool keepInArea = false;
 if (width() < fsa.width() && (cs.width() > ss.width()+1)) {
 pseudo_max &= ~MaximizeHorizontal;
-keepInFsArea = true;
+keepInArea = true;
 }
 if (height() < fsa.height() && (cs.height() > ss.height()+1)) {
 pseudo_max &= ~MaximizeVertical;
-keepInFsArea = true;
+keepInArea = true;
 }

 if (pseudo_max != MaximizeRestore) {
@@ -457,8 +457,8 @@ bool Client::manage(xcb_window_t w, bool isMapped)
 geom_restore.setWidth(width());
 }
 }
-if (keepInFsArea)
-keepInArea(fsa, partial_keep_in_area);
+if (keepInArea)
+keepInArea(area, true);
 }
 }

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 369131] Closed application keeps its size when closed even if started on another screen

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369131

Thomas Lübking  changed:

   What|Removed |Added

 CC||thomas.luebk...@gmail.com

--- Comment #4 from Thomas Lübking  ---
What exactly happens on your side?
Do you enter the branch including "pseudo_max &= ~MaximizeVertical;"?
If yes, keepInArea should be called anyway. If not, the window should be
vertically maximized.

Also debug out area around
"if (height() >= area.height())
pseudo_max |=  MaximizeVertical;"

Could be the placement area is > the screenarea (because of borked struts)

And please dump "xrandr -q"

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 369832] PartStatusWidget hides additional lines of text

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=369832

Thomas Lübking  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED

--- Comment #1 from Thomas Lübking  ---
The alignment (see commit 0e4e1837f0c2fae9aac66c32e10f753b09f334ce) gets
reset/overridden (ie. something post-alters the chain somewhere)

The "fixes" it for me by updating the alignment once more.

diff --git a/src/Gui/PartWidget.cpp b/src/Gui/PartWidget.cpp
index 3c6785c..f6b7d56 100644
--- a/src/Gui/PartWidget.cpp
+++ b/src/Gui/PartWidget.cpp
@@ -219,6 +219,7 @@ void PartStatusWidget::showDetails()
 m_seperator->hide();
 m_detailButton->setText(tr("Show Details"));
 } else {
+static_cast(layout())->setAlignment(m_details, 0);
 m_details->show();
 m_seperator->show();
 m_detailButton->setText(tr("Hide Details"));

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 369130] Windows move to certain monitor after returning to a locked session

[Thomas Lübking via KDE Bugzilla]

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 requirement to reposition them again. -
geometry.cpp, but your should rather see to prevent "locked because of
inactivity" from altering the screen layout. That would be powerdevil or
kscreen (ie. not in kwin)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 369131] Closed application keeps its size when closed even if started on another screen

[Thomas Lübking via KDE Bugzilla]

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 several ways to end within this position and one
needs to know which in order to tackle it)

Relevant code is in manage.cpp and geometry.cpp

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 368685] wishlist - systemsettings --> desktop behavior --> screen edges does not allow custom actions.

[Thomas Lübking via KDE Bugzilla]

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 because:
You are watching all bug changes.

[trojita] [Bug 368003] CATENATE might produce invalid MIME messages

[Thomas Lübking via KDE Bugzilla]

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: 8bit et al
Sounds not too efficient?

> disable CATENATE for now?
If either a fix is located in Farfaraway or fixing it "right" would add more
overhead than CATENATE removes, that would be a viable option.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 350826] plasma desktop containment seems to intermediately switch window type to normal when showing desktop

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=350826

Thomas Lübking  changed:

   What|Removed |Added

 CC||thomas.luebk...@gmail.com

--- Comment #67 from Thomas Lübking  ---
Sorry for the delay (but I'm officially no longer here ;-)

run "kcmshell5 kwinrules", "detect", click the desktop, ensure to select *all*
window types in the lower listview of the main dialog and finally in its
"appearance and fixes" tab, force the window to be of desktop type.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 367685] Toggle application launcher on meta key

[Thomas Lübking via KDE Bugzilla]

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:
You are watching all bug changes.

[kwin] [Bug 367534] popup windows shows only decoration and freezes

[Thomas Lübking via KDE Bugzilla]

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 which
also doesn't update for exposure events and by this accumulates everything the
server ever displayed in its area.
Whatever client provides this window is likely "frozen" (taken by something)

For a wild guess, try setting the system language to english.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 367554] Special Window Settings are written with lowercased WM_WINDOW_ROLE

[Thomas Lübking via KDE Bugzilla]

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 now matches case sensitively. All
fine, but the rule is still *written* lowercased (at least in this context)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 366742] Qbitorrent Xorg/kwin_x11 high cpu usage while adding more than 1 torrent at the same time.

[Thomas Lübking via KDE Bugzilla]

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 and watch remaining CPU
loads.
A high cpu load in qbittorrent and Xorg, but no load in kwin likely means that
the client repaints like hell - this will directly impact the compositor
(rasing kwin in that regard)

If kwin has high cpu load despite a suspended compositor (no shadows,
translucency etc!) that would suggest the client causes map/unmap notifications
(some window shows/hides) or configure requests.

In the latter case I would check on its systray icon (it certainly has one,
yesno?)
Try to disable such feature in qbittorrent and see what happens.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 367534] popup windows shows only decoration and freezes

[Thomas Lübking via KDE Bugzilla]

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, but the round corners are crisp and I see no shadows)

"Freeze" also does not seem to imply that kwin turns inresponsive - at least it
looks as if you can still move around windows, yesno?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 367554] Special Window Settings are written with lowercased WM_WINDOW_ROLE

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=367554

Thomas Lübking  changed:

   What|Removed |Added

Summary|Special Window Settings |Special Window Settings are
   |never take effect   |written with lowercased
   ||WM_WINDOW_ROLE
  Component|general |rules

--- Comment #5 from Thomas Lübking  ---
> WM_WINDOW_ROLE(STRING) = "MainWindow"
Bingo. The rule needs to be written case sesitively.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 367554] Special Window Settings never take effect

[Thomas Lübking via KDE Bugzilla]

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 receiving this mail because:
You are watching all bug changes.

[frameworks-kglobalaccel] [Bug 348227] Opening new windows causes events to be raised on incorrect windows

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=348227

Thomas Lübking  changed:

   What|Removed |Added

 CC|thomas.luebk...@gmail.com   |

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365918] Sometimes flickering when interacting with windows

[Thomas Lübking via KDE Bugzilla]

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
knowledge, of course (ie. if it still happens, it's not them)

Could it be related to running fullscreen games (steam et al.)?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 366794] kwin or plasma5 crashes often when an sftp:// or a ftp:// location

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366794

Thomas Lübking  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Thomas Lübking  ---
for kwin, run "kcmshell5 kwindecoration" and switch to "breeze"
For plasmashell, there's no solution - the bug is QtQuick.

*** This bug has been marked as a duplicate of bug 358369 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 358369] Plasma crashed after opening an HTML5 video in Chrome

[Thomas Lübking via KDE Bugzilla]

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.

[kwin] [Bug 365918] Sometimes flickering when interacting with windows

[Thomas Lübking via KDE Bugzilla]

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 the obvious: pelase deactivate blur and contrast effects
(kcmshell5 kwineffects) and see whether it's still a problem.

You can also try
  export KWIN_USE_BUFFER_AGE=0
  kwin_x11 --replace &

and see what happens (this will read the old data from the front buffer instead
of relying on the buffer_age extension)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 366742] Qbitorrent Xorg/kwin_x11 high cpu usage while adding more than 1 torrent at the same time.

[Thomas Lübking via KDE Bugzilla]

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 whatever process else boils up in top.

And use transmission ;-)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 366651] Kwin Compositor Stops Updating Windows

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366651

Thomas Lübking  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=342326

--- Comment #2 from Thomas Lübking  ---
bug #342326 and friends

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 342326] window contents freeze

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=342326

Thomas Lübking  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=366651

-- 
You are receiving this mail because:
You are watching all bug changes.

[trojita] [Bug 365299] make transition from qtwebkit to qtwebengine

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365299

Thomas Lübking  changed:

   What|Removed |Added

   Severity|major   |normal

--- Comment #4 from Thomas Lübking  ---
Before this turns into a flamewar:

Actually™, both are ridiculuously fat.
Also (but not only) given that Trojitá is a mail client and not a web browser.

One should not use html for mails itfp. and the vast majority of html-only
mails are indeed spam.
For the rest, QTextBrowser is probably capable of sufficiently rendering them.


Since Jan feels required to ultimately support both khtml forks, the result
will probably look like a plugin driven system with the (available anyway)
QTextBrowser as defaulting failsafe.
This would also cover for the various "Whoops, setEcmaEnabled() is effectively
noop. What do you mean, we interpret redirections? No, disabling forms isn't
supported." security flaws in the webengines that one could imagine...

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kxmlgui] [Bug 286146] Window size/geometry not always restored on TwinView

[Thomas Lübking via KDE Bugzilla]

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.

[trojita] [Bug 366498] InvalidResponseCode

[Thomas Lübking via KDE Bugzilla]

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 incomplete (at least FLAGS, EXISTS, and RECENT should be in
there), but that could also just be a capped log.


The main problem here though will be that UIDVALIDITY "slightly" exceeds 32
bits.
At least I read https://tools.ietf.org/html/rfc3501#section-2.3.1.1 as 32bit
"UIDVALIDITY"  + 32bit UID 

Jan will know for sure and might reply next week or by the end of the month.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 364633] windows sometimes are translated downwards (mostly on kwin crash / kill -9 + restart)

[Thomas Lübking via KDE Bugzilla]

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.

As for myself, I'm sorry to say that I won't be available anymore - I removed
myself from kwin bugs, so don't wonder why I will no more reply ;-)

Good bye, everyone.

* crosses Qt4 & Qt5, KDE and plain Qt

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361236

Thomas Lübking  changed:

   What|Removed |Added

 CC||rosan...@lajt.hu

--- Comment #24 from Thomas Lübking  ---
*** Bug 366126 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 366126] Crash after adding new panel with dual monitor system

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366126

Thomas Lübking  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Thomas Lübking  ---
kcmshell5 kwindecoration, switch to breeze.

*** This bug has been marked as a duplicate of bug 361236 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 351763] yet another segfault in QV4::ExecutionEngine::newStringObject

[Thomas Lübking via KDE Bugzilla]

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 output is
irrelevant here.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 366097] KWin crashes on start after upgrade to Fedora 23

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366097

Thomas Lübking  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Thomas Lübking  ---
run "kcmshell5 kwindecoration" and switch to breeze.

*** This bug has been marked as a duplicate of bug 361236 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361236

Thomas Lübking  changed:

   What|Removed |Added

 CC||const.nekras...@gmail.com

--- Comment #23 from Thomas Lübking  ---
*** Bug 366097 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361236

Thomas Lübking  changed:

   What|Removed |Added

 CC||kde.jr...@grifent.com

--- Comment #22 from Thomas Lübking  ---
*** Bug 366096 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 366096] KDE crashed on start.

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366096

Thomas Lübking  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Thomas Lübking  ---
kcmshell5 kwindecoration, switch to breeze

*** This bug has been marked as a duplicate of bug 361236 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 366091] Compositor is de-activated the second time you log in KDE

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366091

Thomas Lübking  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #2 from Thomas Lübking  ---
> The taskbar for example is not transparent.
What means nothing.
If the supportInformation reflects the condition, you're just hitting bug
#362531

*** This bug has been marked as a duplicate of bug 362531 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 362531] Plasma panels are not transparent after login

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=362531

Thomas Lübking  changed:

   What|Removed |Added

 CC||Panagiotis.Kavalagios@eurod
   ||yn.com

--- Comment #25 from Thomas Lübking  ---
*** Bug 366091 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 366081] kwin's windows stay translucent after moving, become invisible

[Thomas Lübking via KDE Bugzilla]

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.

[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361236

Thomas Lübking  changed:

   What|Removed |Added

 CC||sami.lie...@iki.fi

--- Comment #21 from Thomas Lübking  ---
*** Bug 366012 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 366012] kwin crash shortly after starting kde

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366012

Thomas Lübking  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Thomas Lübking  ---
run "kcmshell5 kwindecoration", switch to breeze.

*** This bug has been marked as a duplicate of bug 361236 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365964] KWin crash when I run fullscreen games

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365964

Thomas Lübking  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|BACKTRACE   |DUPLICATE

--- Comment #6 from Thomas Lübking  ---
Thanks, the bug is fixed in 5.6

*** This bug has been marked as a duplicate of bug 347495 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 347495] Kwin crashed after attempting to start a fullscreen app, and the resolution swapped a lot

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=347495

Thomas Lübking  changed:

   What|Removed |Added

 CC||guoyunhebr...@gmail.com

--- Comment #13 from Thomas Lübking  ---
*** Bug 365964 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365964] KWin crash when I run fullscreen games

[Thomas Lübking via KDE Bugzilla]

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 contain more information)

(The latest attachment shows gdb attached to kwin, there's no segfault occurred
and notably no trace contained.)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365988] Kwin crashes on firefox start

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365988

Thomas Lübking  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Thomas Lübking  ---
run "kcmshell5 kwindecoration", switch to breeze.

> When will you fix this issues with KWin finally? We deal with it sind a long 
> time now.
Never. The bug is (we're not missing an "in" here..) QtQuick/QML. Get used to
it.

*** This bug has been marked as a duplicate of bug 361236 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6

[Thomas Lübking via KDE Bugzilla]

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.

[kwin] [Bug 365964] KWin crash when I run fullscreen games

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365964

Thomas Lübking  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |BACKTRACE

--- Comment #1 from Thomas Lübking  ---
#6  0x7ff897bf1acd in  () at /usr/lib64/libkwin.so.5
#7  0x7ff897bf1b89 in  () at /usr/lib64/libkwin.so.5


please install the kwin-dbg package and recause the crash

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365913] in crash

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365913

Thomas Lübking  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Thomas Lübking  ---
welcome to the show, update to Qt 5.6 asap

*** This bug has been marked as a duplicate of bug 341497 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

[Thomas Lübking via KDE Bugzilla]

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.

[kwin] [Bug 365824] krunner, launcher and applet windows just blink and won't show up

[Thomas Lübking via KDE Bugzilla]

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 window type juggling, notably since only QML
clients seem affected.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365896] Kwin crashes when wallet pops-up

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365896

Thomas Lübking  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Thomas Lübking  ---
run "kcmshell5 kwindecoration" and switch to breeze.

*** This bug has been marked as a duplicate of bug 361236 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361236

Thomas Lübking  changed:

   What|Removed |Added

 CC||kr...@free.fr

--- Comment #19 from Thomas Lübking  ---
*** Bug 365896 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365799] Graphical corruption and display stops updating when connecting external monitor through HDMI

[Thomas Lübking via KDE Bugzilla]

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 would expect it in server and general extensions as well)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365824] krunner, launcher and applet windows just blink and won't show up

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365824

Thomas Lübking  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=350826

--- Comment #4 from Thomas Lübking  ---
Something tells me this is related to bug #350826 resp. bug #365685

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 350826] plasma desktop containment seems to intermediately switch window type to normal when showing desktop

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=350826

Thomas Lübking  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=365824

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365821] Emacs stop damage events (liekly when disobeying its geometry hints)

[Thomas Lübking via KDE Bugzilla]

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 events
   |being updated   |(liekly when disobeying its
   ||geometry hints)
  Component|scene-opengl|compositing

--- Comment #10 from Thomas Lübking  ---
The tiling probably disobeys emacs size hints and emacs has e a
"record" of being very errr "special"? "picky"? on this (it starts a war on
its geometry)

Quick tiling emacs might cause this as well juas as disobeying the geometry
hints via "kcmshell5 kwinrules" - this very behavior is new to me, though
(*sigh*)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 364633] windows sometimes are translated downwards (mostly on kwin crash / kill -9 + restart)

[Thomas Lübking via KDE Bugzilla]

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 smplayer`
ldd `which qtcreator` # no idea whether that's the actual binary name ;-)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365821] Content of some windows not being updated

[Thomas Lübking via KDE Bugzilla]

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 issue for *all* backends are affected.


- Does anything change when you resize the window (does it at least update
then)?
- Does it work when running compton on KDE?
(it's not a WM, so suspending the KWin compositor and starting compton should
just work "fine" - minus some integration between WM and compositor, of course)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365821] Content of some windows not being updated

[Thomas Lübking via KDE Bugzilla]

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 cause it on
xrender after a logout and fresh emacs process?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 352445] Loss of panel translucency at initial login

[Thomas Lübking via KDE Bugzilla]

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.

[kwin] [Bug 365821] Content of some windows not being updated

[Thomas Lübking via KDE Bugzilla]

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 are watching all bug changes.

[kwin] [Bug 364633] windows sometimes are translated downwards (mostly on kwin crash / kill -9 + restart)

[Thomas Lübking via KDE Bugzilla]

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)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 364633] windows sometimes are translated downwards (mostly on kwin crash / kill -9 + restart)

[Thomas Lübking via KDE Bugzilla]

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 *only* matters if the problem did NOT occur for a kwin restart (after
kill/segfault/etc.) for the quick tiled state is then lost for sure.

Also, which decoration do you use?



On a general remark, please stop killing -9 unless you really know that you
want it.
-15 is the default (SIGTERM) and should be sufficient, you can provoke
"segfaults" w/ -11 (SIGSEGV)
You can also use symbols ("kill -l" for a list)

SIGKILL means that the kernel removes the process and is really about the worst
of all choices for nothing in the process (incl. libGL) has even a remote
chance to do some cleanup to leave behind a sane context.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365824] krunner, launcher and applet windows just blink and won't show up

[Thomas Lübking via KDE Bugzilla]

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. kwrite still shows up fine?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365799] Graphical corruption and display stops updating when connecting external monitor through HDMI

[Thomas Lübking via KDE Bugzilla]

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
KWIN_USE_BUFFER_AGE=0 kwin_x11 --replace &

https://community.kde.org/KWin/Environment_Variables#KWIN_USE_BUFFER_AGE

On
> laptop screen stops updating while the second monitor works fine

Can you please dump the supportInformation again, but this time after attaching
the screen and when one screen is dead (given that kwin actually responds in
this state)
Also, does restarting the compositor (SHIFT+Alt+F12, twice) resolve the state
as well?

---
nb: this is on Qt 5.7.0 ...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365821] Content of some windows not being updated

[Thomas Lübking via KDE Bugzilla]

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 emacs doesn't expose this behavior with suspended compositor
(SHIFT+Alt+F12 toggles)

Afaik you cannot attach files on reporting but only afterwards. No idea why.

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 198175] Konsole should set blur region for the new kwin effect

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=198175

Thomas Lübking  changed:

   What|Removed |Added

 CC||goetzchr...@gmail.com

--- Comment #79 from Thomas Lübking  ---
*** Bug 365780 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365780] Blur effect doesn't work with semi-transparent windows

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365780

Thomas Lübking  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Thomas Lübking  ---
The effect requires a hint on the region to blur.
Dupe'd to konsole bug, you'll have to file a bug against FF since it's not
maintained here.

https://bugs.kde.org/show_bug.cgi?id=198175#c46 shows how to set a hint (from
outside) for the entire window.

*** This bug has been marked as a duplicate of bug 198175 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 358369] Plasma crashed after opening an HTML5 video in Chrome

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358369

Thomas Lübking  changed:

   What|Removed |Added

 CC||zholeg...@gmail.com

--- Comment #26 from Thomas Lübking  ---
*** Bug 365726 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365726] Kwin crashes after starting Firefox

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365726

Thomas Lübking  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Thomas Lübking  ---
run "kcmshell5 kwindecoration" and switch to breeze.

*** This bug has been marked as a duplicate of bug 358369 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 350826] plasma desktop containment seems to intermediately switch window type to normal when showing desktop

[Thomas Lübking via KDE Bugzilla]

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 receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365685] "keep below" windows dive below plasmashell (sometimes)

[Thomas Lübking via KDE Bugzilla]

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 are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365601] Please invert only the content, not the window decoration

[Thomas Lübking via KDE Bugzilla]

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 only app-a-like wrap the web
service anyway)

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 350826] plasma desktop containment seems to intermediately switch window type to normal when showing desktop

[Thomas Lübking via KDE Bugzilla]

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 applied.

Plasma can then fight with QtQuick on juggling the type as much as it wants,
KWin simply won't look there anymore.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365685] "keep below" windows dive below plasmashell (sometimes)

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365685

Thomas Lübking  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #13 from Thomas Lübking  ---
Thanks for the update.
>From the report, it doesn't seem that you're trying to show the desktop, but
this happens when simply clicking (activating) the desktop?

*** This bug has been marked as a duplicate of bug 350826 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 350826] plasma desktop containment seems to intermediately switch window type to normal when showing desktop

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=350826

Thomas Lübking  changed:

   What|Removed |Added

 CC||ensla...@protonmail.com

--- Comment #62 from Thomas Lübking  ---
*** Bug 365685 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365685] "keep below" windows dive below plasmashell (sometimes)

[Thomas Lübking via KDE Bugzilla]

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 on the very first tab ensure to select all window type
**except docks and dialogs** - that should do.

See this screenshot of the relevant page.
https://userbase.kde.org/images.userbase/thumb/2/20/Window-matching-init.png/560px-Window-matching-init.png

The thing should not be called "unmanaged window" ... (it's not) but again: you
do NOT want to match dialogs and docks.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365685] "keep below" windows dive below plasmashell (sometimes)

[Thomas Lübking via KDE Bugzilla]

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 actually only forces
desktop type windows to be of desktop type (ie. does nothing)

You need to ensure that normal and override type windows are caught as well.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365685] "keep below" windows dive below plasmashell (sometimes)

[Thomas Lübking via KDE Bugzilla]

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 bug changes.

[kwin] [Bug 365685] "keep below" windows dive below plasmashell (sometimes)

[Thomas Lübking via KDE Bugzilla]

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.

[kwin] [Bug 365685] "keep below" windows dive below plasmashell (sometimes)

[Thomas Lübking via KDE Bugzilla]

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.

If not, the problem will be caused by kwin updating the layer for the window
(typically when showing the desktop, but there may be other occasions) and the
window having the wrong type at that moment.

You can also try to run "xprop -spy _NET_WM_WINDOW_TYPE" on the desktop and see
whether there's noise right when the window gets lost.

Last (just in case the above fails), did you already ensure it's really because
the keep below window drops in the stack, ie. withdrawing the state with wmctrl
re-raises it?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 350826] plasma desktop containment seems to intermediately switch window type to normal when showing desktop

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=350826

Thomas Lübking  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=365685

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365685] "keep below" windows dive below plasmashell (sometimes)

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365685

Thomas Lübking  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=350826

--- Comment #1 from Thomas Lübking  ---
smells related to bug #350826

open a konsole, set it to keep above ( ;-) and try to cause this. when it
happens, run "xprop _NET_WM_WINDOW_TYPE" and click the desktop, see whether it
says "_NET_WM_WINDOW_TYPE_DESKTOP"

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 310005] Cannot tile windows horizontally (to the top or bottom)

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=310005

Thomas Lübking  changed:

   What|Removed |Added

 CC||lucas.hartm...@gmail.com

--- Comment #26 from Thomas Lübking  ---
*** Bug 365681 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365681] Edge Snapping/Tiling Actions on Vertical Displays

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365681

Thomas Lübking  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Thomas Lübking  ---
s/"full screen"/"maximized"/  - they're not the same concept.

*** This bug has been marked as a duplicate of bug 310005 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365601] Please invert only the content, not the window decoration

[Thomas Lübking via KDE Bugzilla]

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/styles/23516/midnight-surfing-global-dark-style
or
https://userstyles.org/styles/31267/global-dark-style-changes-everything-to-dark

> 2. proprietary chat applications (which I have to use for work).
Skype or lync? Not sure but in theory you can configure wine colors (if this is
the toolkit)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 360443] Kwin freezes -- mouse moves but nothing else works

[Thomas Lübking via KDE Bugzilla]

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 symbols for mesa (and intel-dri) to see which GL
call is lingering around there.
I doubt this came with an update of KWin but rather the kernel or mesa or the
intel driver.
Maybe a reconfiguration (uxa/sni/glamor or using)

Please open a new bug in any case, you're wrong here ;-)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365650] After unplug external screens, windows do not come back to current screen

[Thomas Lübking via KDE Bugzilla]

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.

[kwin] [Bug 365465] Kwin hangs

[Thomas Lübking via KDE Bugzilla]

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 watching all bug changes.

[kwin] [Bug 365601] Please invert only the content, not the window decoration

[Thomas Lübking via KDE Bugzilla]

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 you desire to invert internally (and why) - the
by far better approach was to have the client invert itself.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 361236] Aurorae crashes in QQmlBinding::write on creation - Qt 5.6

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=361236

Thomas Lübking  changed:

   What|Removed |Added

 CC||guenter.oh...@gmx.de

--- Comment #16 from Thomas Lübking  ---
*** Bug 365593 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365593] Message Segmentation Fault after Login

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365593

Thomas Lübking  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Thomas Lübking  ---
Run "kcmshell5 kwindecoration" and switch to breeze

*** This bug has been marked as a duplicate of bug 361236 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 351399] Newly started application windows randomly positioned on primary or extended screen

[Thomas Lübking via KDE Bugzilla]

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.

[kwin] [Bug 365465] Kwin hangs

[Thomas Lübking via KDE Bugzilla]

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.

[konsole] [Bug 198175] Konsole should set blur region for the new kwin effect

[Thomas Lübking via KDE Bugzilla]

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  to the GUI style (for it may also
have wanted to impact this but since Qt5 doesn't support depth changes of
existing windows, that point is now more or less void)

I'd suggest to go for a relaxed protocol (gentleman's agreement) on some
dynamic Qt property on the widgets and a static KStyle helper to traverse all
widgets in a window for the blur props, merge them into a region and set the
X11 property via KWindowSystem

You'd then
myWidget->setProperty("kwin_fx_blur", QRegion);
KStyle::updateBlur(myWidget->window()); // schedules a run for the end of the
event cycle

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365461] windows shadows crash if it not use the default theme.

[Thomas Lübking via KDE Bugzilla]

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.

[kwin] [Bug 365461] windows shadows crash if it not use the default theme.

[Thomas Lübking via KDE Bugzilla]

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 this mail because:
You are watching all bug changes.

[kwin] [Bug 365464] kwin crash when open cs:go

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365464

Thomas Lübking  changed:

   What|Removed |Added

 Resolution|--- |BACKTRACE
 Status|UNCONFIRMED |NEEDSINFO

--- Comment #1 from Thomas Lübking  ---
> #6 0x7f94fe2d7acd in () at /usr/lib64/libkwin.so.5
> #7 0x7f94fe2d7b89 in () at /usr/lib64/libkwin.so.5

lacks any relevant debug symbols. please install the kwin-dbg package, recause
the segfault and provide an updated backtrace.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 351399] Newly started application windows randomly positioned on primary or extended screen

[Thomas Lübking via KDE Bugzilla]

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 nowhere.
Since netwm is completely multiscreen unaware, it would afaics require some
call like KStartupInfoData::setXinerama(.) to define a specific screen -
there's no real protocol.

One could btw. specify a blind rule to have all windows always show on screen
1.

-- 
You are receiving this mail because:
You are watching all bug changes.

[KScreen] [Bug 365455] Second external monitor does not turn on most of the times

[Thomas Lübking via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=365455

Thomas Lübking  changed:

   What|Removed |Added

Product|kwin|KScreen
   Assignee|kwin-bugs-n...@kde.org  |se...@kde.org
  Component|general |kded

--- Comment #1 from Thomas Lübking  ---
kwin doesn't manage screens

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 365367] Kwin always crashes when I try adjust the scale of a bitmap image in mtPaint

[Thomas Lübking via KDE Bugzilla]

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.