[Bug 1446865]
(In reply to Storm Engineer from comment #58) > The following do NOT get restored: > - Firefox https://forum.kde.org/viewtopic.php?f=111=131515 > Isn't Chrome using Qt tho? No. And as mentioned, Qt (vlc) still *is* broken itr. It by this patch just got the *option* to not act brokenly. Every client needs to opt into that. (But that's not been different with Qt4, just no additional Qt API was required then and kdelibs fixed it for most KDE applications implicitly) > I have another issue which may be related, but the two are spanning across > different time frames so it doesn't seem likely. This issue is shutdown > being halt with "A stop job is running for session c2 of user" with a 1:30 Seems a systemd bug, see https://bugs.freedesktop.org/show_bug.cgi?id=70593 or https://bugs.freedesktop.org/show_bug.cgi?id=70593 It might be related to firefox session management, you could try whether you also get this problems when quitting all applications (ensure there're no stale processes left!) before exitting the session and then (if it's now gone) see whether adding some process back at the session end (ie. leave dolphin running, try shutdown; then leave firefox for the next shutdown) causes this. The process may not quit on sigterm. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: KDE5/Qt5 does not support session restoration To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 38753]
FYI, on windows, window management is completely done by the clients (so a client knows that this is gonna be a drag and can avoid the self-raise) The WM_TAKE_FOCUS protocol (despite the focus has really nothing to do with the stack order) pointed that direction (and sucks terribly because of broken client implementations... letting alone the focus stealing problems) Raising on MB release would be possible (on caveats, see comment #37), but just cause other behavioral problems (if the user didn't want to drag something, but draw a selection frame etc.) About present windows to the rescue: *cough* https://git.reviewboard.kde.org/r/105341/ **COUGH** :-P Last thought: detect the drag (maybe even on X11 by listening to dnd messages rather than "something grabbed the pointer") and restore the stack if it happened within "the dnd timeout™" (which doesn't exist either - there's no guarantee Qt and Gtk wait the same amount of time), ie. lower the window we just raised (while even that could be nasty: assume the user wanted to dnd within the just raised client and suddenly it lowers again) tl;dr - clean up your f desktop ;-P -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in Ubuntu. https://bugs.launchpad.net/bugs/38753 Title: Inactive window "raise on click" should occur after click is released To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/38753/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1446865]
Please file a review request (attaching the frameworks group), the bug is assigned to Seli and I'm not sure anybody but us reads it. I can already say that it lacks a QT_VERSION test. About the Qt side, one might want to consider using a Qt::ApplicationAttribute instead? "Qt::AA_DoNotKludgeSessionSaving"? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: KDE5/Qt5 does not support session restoration To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1446865]
Well, "shrug, I don't care then" - Qt seems to be dropping desktop support anyway, so it probably doesn't really matter. For principal reasins I'd however object " proven to be not broken by being around for over 10 years": It wasn't "broken" because one major client class (KDE) simply replaced that "unbroken" code. Nor did I mean to support directly "changing behavior" - I simply suggested to raise awareness of the problem by intercepting "this looks unimplemented" conditions to allow getting rid of the "unbroken" code in Qt6 w/o pain. Closing windows certainly is wrong (and apparently wasn't done before Qt4, seems more like a closeEvent was faked previously) because it alters the session even on a canceled session exit, regardless on whether it breaks restoring them (which one would kludge away in the session manager) Ok, bottom line is SM is FUBAR on Qt5 and there's no intention to ever fix that, merely re-allow client code to bypass the broken Qt behavior. I'll tag future bugs respectively. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: KDE5/Qt5 does not support session restoration To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1446865]
Fun fact (though you likely already know) - KApplication::commitData(.) *did* send a fake close event to everything but KMainWindow ... -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: KDE5/Qt5 does not support session restoration To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1446865]
For a KMainWindow solution, one should not require a nasty global eventfilter on the application - handling KMainWindow::closeEvent() should be sufficient, but there might be an additional pitfall on modal windows (ie. if there's already a save dialog, we might have to forcefully activate that to cause user interaction) However, as long as QGuiApplication cancels the session lougout as long as any close event is ignored, this cannot be applied either (ie. still requires your new patch to Qt) and, of course, this doesn't provide a solution for Qt5 either - session management on Qt5 will remain broken forever and just some KDE applications work around that. That's a pretty crappy situation :-( -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: KDE5/Qt5 does not support session restoration To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1446865]
(In reply to Andreas Hartmetz from comment #27) > We can, however, implement a workaround in KDE (and then fix our stuff when > something breaks): > [...] > Now which repository should that go in? It would be ugly to copy and paste > the necessary code around - it should be roughly ten lines. That's some sort of problem. KXmlGui/KMainWindow would cover most™ cases, but certainly not all. The idea of KF5 is to merely optionally extend Qt and the QPA plugin would affect every Qt application. Since this will however also require to fix the application wrt listening to the datacommit request itfp, this could only apply to the fixed cases - which would for a general fix then be KMainWindow, calling queryClose() on this occasion. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: KDE5/Qt5 does not support session restoration To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1446865]
How exactly did you try the kwrite crashing workaround? Just by sending a zombie closeEvent? Do you still have a backtrace? (Let's say it's legit for a leaf widget to assume that the close event it doesn't ignore() will cause a close with all implications on future user interaction, data deletion and stuff, but it's not necessarily good style. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: KDE5/Qt5 does not support session restoration To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1437260]
(In reply to hamelg from comment #52) > Testing again the new patch. It's still ok but i am in 24bits. How can i do > to test 30/32bits depth ? You can't - that's a server thing. Seems the image just has a degenerated alpha channel on SNA but not on UXA (and most other drivers) - what could indicate the ARGB_premultiplied is generally wrong. *shrug* - we shall just jump into the pool and wait until somebody with an exotic color table reports a bug. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1437260 Title: Plasma5 Font Preview is not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1437260/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1437260]
Thanks everyone, but the test I mostly wait for is that on intel/sna (I assume the format was hardcoded because it worked on that driver and I don't want to break it - it's too common) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1437260 Title: Plasma5 Font Preview is not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1437260/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1437260]
https://git.reviewboard.kde.org/r/126713/ -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1437260 Title: Plasma5 Font Preview is not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1437260/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1437260]
Resp. this one (the ARGB32 translucency handling is uncritical, it's
applied to the preconverted image. This should be the single point of
failure)
diff --git a/kcms/kfontinst/lib/FcEngine.cpp b/kcms/kfontinst/lib/FcEngine.cpp
index 19b7206..012a9d5 100644
--- a/kcms/kfontinst/lib/FcEngine.cpp
+++ b/kcms/kfontinst/lib/FcEngine.cpp
@@ -537,7 +537,14 @@ QImage CFcEngine::Xft::toImage(int w, int h) const
if (!xImage) {
return QImage();
}
-return QImage(xImage->data, xImage->width, xImage->height, xImage->stride,
QImage::Format_ARGB32_Premultiplied, , xImage);
+QImage::Format format = QImage::Format_RGB32;
+switch (DefaultDepth(QX11Info::display(), 0)) {
+case 32: format = QImage::Format_ARGB32_Premultiplied; break;
+case 16: format = QImage::Format_RGB16; break;
+case 8: format = QImage::Format_Grayscale8; break;
+default: break;
+}
+return QImage(xImage->data, xImage->width, xImage->height, xImage->stride,
format, , xImage);
}
inline int point2Pixel(int point)
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to plasma-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/1437260
Title:
Plasma5 Font Preview is not visible
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1437260/+subscriptions
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1437260]
Yes, is. Stunning.
The xft image is RGB32 here, may depend on whether it's set to
translucent (though there ARGB32 instead of pre-multiplied is used)
We need this patch tested on all possible GPUs (notably intel/sna!)
diff --git a/kcms/kfontinst/lib/FcEngine.cpp b/kcms/kfontinst/lib/FcEngine.cpp
index 19b7206..6c731dc 100644
--- a/kcms/kfontinst/lib/FcEngine.cpp
+++ b/kcms/kfontinst/lib/FcEngine.cpp
@@ -537,7 +537,7 @@ QImage CFcEngine::Xft::toImage(int w, int h) const
if (!xImage) {
return QImage();
}
-return QImage(xImage->data, xImage->width, xImage->height, xImage->stride,
QImage::Format_ARGB32_Premultiplied, , xImage);
+return QImage(xImage->data, xImage->width, xImage->height, xImage->stride,
QImage::Format_RGB32, , xImage);
}
inline int point2Pixel(int point)
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to plasma-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/1437260
Title:
Plasma5 Font Preview is not visible
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1437260/+subscriptions
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1437260]
Thanks a lot. Risking to be a complete PITA, mind testing this patch and
notably watching on whether you're on 32bit depth and whether a format
is found (and it's the correct one ;-)
diff --git a/kcms/kfontinst/lib/FcEngine.cpp b/kcms/kfontinst/lib/FcEngine.cpp
index 19b7206..6026753 100644
--- a/kcms/kfontinst/lib/FcEngine.cpp
+++ b/kcms/kfontinst/lib/FcEngine.cpp
@@ -219,6 +219,7 @@ class CFcEngine::Xft
XftColor itsTxtColor,
itsBgndColor;
Pix itsPix;
+QImage::Format imageFormat;
};
CFcEngine::Xft::Xft()
@@ -267,6 +268,47 @@ bool CFcEngine::Xft::init(const QColor , const QColor
, int w, int h)
XftColorAllocValue(QX11Info::display(), visual, colorMap, ,
);
}
+XVisualInfo defaultVinfo;
+defaultVinfo.depth = DefaultDepth(QX11Info::display(), 0);
+// normal/failsafe
+imageFormat = QImage::Format_RGB32; // 24bit
+switch (defaultVinfo.depth) {
+case 32: imageFormat = QImage::Format_ARGB32_Premultiplied; break;
+case 30: imageFormat = QImage::Format_RGB30; break;
+case 16: imageFormat = QImage::Format_RGB16; break;
+case 8: imageFormat = QImage::Format_Grayscale8; break;
+default: break;
+}
+qDebug() << "Depth" << defaultVinfo.depth;
+if (defaultVinfo.depth == 30 || defaultVinfo.depth == 32) {
+// detect correct format
+int num_vinfo = 0;
+defaultVinfo.visual = DefaultVisual(QX11Info::display(), 0);
+defaultVinfo.screen = 0;
+defaultVinfo.visualid = XVisualIDFromVisual(defaultVinfo.visual);
+XVisualInfo *vinfo = XGetVisualInfo(QX11Info::display(),
VisualIDMask|VisualScreenMask|VisualDepthMask, , _vinfo);
+for (int i = 0; i < num_vinfo; ++i) {
+if (vinfo[i].visual == defaultVinfo.visual) {
+if (defaultVinfo.depth == 30) {
+if (vinfo[i].red_mask == 0x3ff)
+imageFormat = QImage::Format_BGR30;
+else if (vinfo[i].blue_mask == 0x3ff)
+imageFormat = QImage::Format_RGB30;
+} else if (defaultVinfo.depth == 32) {
+if (vinfo[i].blue_mask == 0xff)
+imageFormat = QImage::Format_ARGB32_Premultiplied;
+else if (vinfo[i].red_mask == 0x3ff)
+imageFormat = QImage::Format_A2BGR30_Premultiplied;
+else if (vinfo[i].blue_mask == 0x3ff)
+imageFormat = QImage::Format_A2RGB30_Premultiplied;
+}
+qDebug() << "Found one" << imageFormat;
+break;
+}
+}
+XFree(vinfo);
+}
+
if(itsPix.allocate(w, h) && itsDraw)
XftDrawChange(itsDraw, itsPix.x11);
@@ -537,7 +579,7 @@ QImage CFcEngine::Xft::toImage(int w, int h) const
if (!xImage) {
return QImage();
}
-return QImage(xImage->data, xImage->width, xImage->height, xImage->stride,
QImage::Format_ARGB32_Premultiplied, , xImage);
+return QImage(xImage->data, xImage->width, xImage->height, xImage->stride,
imageFormat, , xImage);
}
inline int point2Pixel(int point)
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to plasma-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/1437260
Title:
Plasma5 Font Preview is not visible
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1437260/+subscriptions
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1437260]
You need to get the sources of plasma-desktop, apply the patch (patch -p1 < path/to/patch.diff) and rebuild at least kcms/kfontinst. If you've no experience with compilation, you can ask your distro to pre-pick the patch (ask implies the answer may be "no") There's no schedule on when this patch hits downstream, sorry. It's not even applied upstream yet. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1437260 Title: Plasma5 Font Preview is not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1437260/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1440210]
not kde4, qt4. it's - very likely - due to combined xcb and xlib usage and on top of that happens in xinout2. none of that used in qt4. closing seems required. sorry. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwin in Ubuntu. https://bugs.launchpad.net/bugs/1440210 Title: KWin crashes multiple times a day and often has to be restarted manually. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1440210/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1440210]
bug #353587 won't fix with any KDE release, it's a bug in XLib. And please stop commenting on *this* bug, see comment #154 -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwin in Ubuntu. https://bugs.launchpad.net/bugs/1440210 Title: KWin crashes multiple times a day and often has to be restarted manually. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1440210/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1446865]
The typical fail will be the "there are 5 tabs open, close/cancel" dialogs. Afaiu this was added because of some MS Windows behavior and even if not, one has to assume that clients simply rely on window "save your work first!" protection to be in place and not somewhen been killed by the SM (what will happen when the SM got an "ok" and then tries to close windows or sigterm the process, would it not?) Large behavioral changes could be denied itr, sending out close events should bail you out ;-) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: KDE5/Qt5 does not support session restoration To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1446865]
Andreas, the Qt patch kills the ability to cancel the logout process (when the process or user prevents closing a window), I'm not sure it will be accepted and if, you probably will have caused a feature breakage. See comment #8. Instead of actually closing, the system likely wants to ask whether anyone is ok with closing this window (ie. cause close events w/o actually closing the window) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: KDE5/Qt5 does not support session restoration To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1440210]
IPORTANT NOTICE: *this* bug entry has long tiem turned a completely poinless mess of various "something does not work" reports on contradicting problem descriptions - often not even KWin related (plasmashell hangs for corrupted cache and whatnot issues) => I'll now close it as WONTFIX. Please abort it completely. Do not post on it. Not even to confirm this stance (to keep this message on top) If you've continuing problems and believe they're related to KWin (whether as window manager or compositor), please open a NEW bug with an exact description of your problem and have us triage them. Ruchir, I'm very sorry that this happened. If your original problem persists, please just re-file it. Sorry again. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwin in Ubuntu. https://bugs.launchpad.net/bugs/1440210 Title: KWin crashes multiple times a day and often has to be restarted manually. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1440210/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 252002]
*** Bug 353916 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde4libs in Ubuntu. https://bugs.launchpad.net/bugs/252002 Title: YaKuake 2.9.3 does not allow the menu key to be used as a shortcut To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/252002/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1369424]
The script API didn't change (for KWin 5, no promises for 6 =) and the stock scripts of course access the workspace object. How did you install the script, does it show up in kcmshell5 kwinscripts and is it present in ~/.local/share/kwin/scripts/ ? Did you verify the warning is from the kwin_x11 process and you didn't perhaps install the script to plasmashell (the desktop) - what will of course not work? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1369424 Title: LibreOffice windows and dialogs do not receive focus on startup (KDE, Razorqt) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1369424/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 637629]
*** Bug 345605 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-runtime in Ubuntu. https://bugs.launchpad.net/bugs/637629 Title: drkonqi crashed with signal 7 in pthread_mutex_timedlock() To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/637629/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1369424]
(In reply to Murz from comment #10) Maybe we can extend it via auto move focus to any new LibreOffice window created? To get an idea what you're talking about: do you rather encounter bug #340915 ? (being -likely- https://bugs.documentfoundation.org/show_bug.cgi?id=75471) The issue overthere is not about dialogs for minimized windows, but for libreoffice _actively_ denying to take the focus. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1369424 Title: LibreOffice windows and dialogs do not receive focus on startup (KDE, Razorqt) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1369424/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1175299]
Linking in HIG: @Thomas P (or anyone you'd like to consult ;-) The core question is what to do with disabled titlebar buttons (eg. if a window cannot be maximized) - show the disabled button - hide the disabled button - replace the disabled button with a gap One may simply argue that Plastik (as windows) traditionally just hid the button, but imo. it's rather important to sport a common behavior among at least all stock decos, so this should follow a general pattern (breeze, oxygen, plastik) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1175299 Title: kwin Plastik decoration displays the help-button wrong To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1175299/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1175299]
(In reply to Thomas Pfeiffer from comment #13) (In reply to Martin Gräßlin from comment #11) I'd say two groups of behavior: * might change during life time of window (e.g. maximize) * might not change during life time of window (e.g. quick help) If, however, the windeco _can_ know whether the button is temporarily or permanently unavailable, then of course temporarily unavailable buttons should be disabled and permanently unavailable ones should be hidden. *cough* might *cough* Actually every button *might* be temporarily unavailable - it's more a matter of likelihood. But *usually* a feature will be available or not for a window as long as it exists - and it's not predictable whether the eg. the client will later on release the size constraints. @Martin I'm actually not sure about esp. the context help here - a client could pot. provide it depending on which kcm is currently loaded or which tab is the current in a QTabWidget - I didn't find a comment on whether WM_PROTOCOLS must not be updated after mapping. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1175299 Title: kwin Plastik decoration displays the help-button wrong To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1175299/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1252235]
Can you please explain how you take a snapshot of the ksnapshot save dialog if the ksnapshot that shoots the save dialog of ksnapshot is not another ksnapshot than the ksnapshot with the save dialog that you shot? IOW, your illustrative shots contain a ksnapshot window w/ a modal dialog. The ksnapshot window seen there (that w/ the modal dialog) is CERTAINLY not what made the snapshot (it cannot be used to take the snapshot since that's currently prevented by the modal dialog) The first screenshot also contains a ksnapshot window w/ snapshot5.png being the titlebar, while the one with the modal dialog is entitled snapshot2.png what makes me assume that there're actually three ksnapshot windows invoked (snapshot2 shooting snapshot5 and a third variant shooting snapshot2) - Can you please describe *precisely* what you're trying to do and what you expect? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to ksnapshot in Ubuntu. https://bugs.launchpad.net/bugs/1252235 Title: Ksnapshot captures its window if Snapshot delay is No delay and window hide effect is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/kdegraphics/+bug/1252235/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1252235]
KWin's off the hook then and that very particular copy of ksnapshot (0.8.2 on 4.14.2 here) seems to take screenshots continuously. That's not related to this very bug but a fresh and new one. (This bug played on the animations when showing/hiding ksnapshot what cause ghosts of it to remain on the screenshot) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to ksnapshot in Ubuntu. https://bugs.launchpad.net/bugs/1252235 Title: Ksnapshot captures its window if Snapshot delay is No delay and window hide effect is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/kdegraphics/+bug/1252235/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1252235]
Yes. Please notice that I only _assume_ that ksnapshot shoots continuously (4 times would be sufficient for the behavior as well) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to ksnapshot in Ubuntu. https://bugs.launchpad.net/bugs/1252235 Title: Ksnapshot captures its window if Snapshot delay is No delay and window hide effect is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/kdegraphics/+bug/1252235/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1252235]
(In reply to S from comment #53) Yes it is. Should it be? Yes, but please try turning it off - we need to figure whether ksnapshot keeps requesting shots or the kwin effect keeps saving them. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to ksnapshot in Ubuntu. https://bugs.launchpad.net/bugs/1252235 Title: Ksnapshot captures its window if Snapshot delay is No delay and window hide effect is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/kdegraphics/+bug/1252235/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 637629]
*** Bug 338717 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-runtime in Ubuntu. https://bugs.launchpad.net/bugs/637629 Title: drkonqi crashed with signal 7 in pthread_mutex_timedlock() To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/637629/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1283820]
iow it was NOT fixed by 10.1 rc3? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1283820 Title: content of windows (and desktop) appear black when using kwin, but not with kwin_gles - intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1283820/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 850628]
(In reply to comment #201) (In reply to comment #200) I can't find an option to automatically suspend compositing in KCM. Because a general setting would be silly. Already was for unredirection. Probably it won't. http://standards.freedesktop.org/wm-spec/wm-spec-latest.html#idp6357888 This is not about a general setting at all, but about a protocol. The silly part about the *general* setting was that we treated konqueror and quake equally. The _NET_WM_BYPASS_COMPOSITOR was actually somehow inspired by the (largely ignored) _KDE_NET_WM_BLOCK_COMPOSITING, so merging the atoms and deprecate _KDE_NET_WM_BLOCK_COMPOSITING certainly makes sense. It will require to move the blocking code from Client to Toplevel - does anything but (upcoming) SDL2 support it so far? https://git.reviewboard.kde.org/r/110088/ I think this could be a good default option The problem of this is that we don't get out of the default since there's no system in place to rule override_redirects (since they do not belong to WM or user) The _NET_WM_BYPASS_COMPOSITOR tristate is a red herring: if special clients are not interested in saying: 1, why should regular clients be interested in saying 2? And why esp. those which are override_redirect and thus often don't set any properties at all? The next problem is that unmanged windows are only matched fullscreen by their geometry, so if your imagebrowser opens a popup to preview the image and uses the maximum screen area, you'll toggle compositing by it. - The only (present) downstream (user accessible) way to control those (and FS state changes of managed clients) is via the script interface. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/850628 Title: When the Euphoria (GL) Screensaver starts, KWIN crashes To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/850628/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 850628]
(In reply to comment #195) Please revert this. Add a warning, don't enable it by default It *is* disabled by default - what does not prevent people from happily activating it, because some guy in a random forum told them it's the best trick ever - and then report crashes in driver that resolve by after disabling unredirection, bug is gone We basically (and actually for far too long) expose users to a feature, while knowing it will crash their WM more or less for sure. It worked for me very well (Intel HD 3000). Since you mentioned DRI_PRIME, it will rather be some IGP-GPU briged system? Also, without it I can't currently use DRI_PRIME. As far as i was told, DRI_PRIME does only work *with* redirection, ie. whenever you disable the compositor, the DRI_PRIME context paints nothing. If it does NOT work redirected for you, the better solution to suspend compositing altogether is not affected. Either (depending on redirection states) would probably a major bug in the prime handling, though. Also, I prepared a patch that makes it less agressive The level of aggression is not relevant, esp. since you try to constrain it to the most problematic cases (override_redirect windows, assuming those are games, ie. likely will have a second GL context) - which overmore would largely benefit from simply turning the compositor off instead (frees memory, quits redirection/damage processing/conversion overhead) What currently missing to do this from scripts is to have scripts informed when unmanaged windows are added, eventually resized to/from fullscreen. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/850628 Title: When the Euphoria (GL) Screensaver starts, KWIN crashes To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/850628/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 850628]
(In reply to comment #198) Then add big red label in KCM: kde-workspace is frozen. - not before summer 2014 (iff at all) For me it NEVER crashed KWin or anything. Lucky for you. Yet bugzilla suggests there's a problem. Look at only the plain dupes of this one and feel free to search through bugzilla... Yes, but KWin is always running on Intel, and doesn't even know about Radeon. Yes, but dri does. The crash is in the driver. No, for me it paints black screen when compositing is enabled (without unredirection). So it works with suspended compositing as well? I can't find an option to automatically suspend compositing in KCM. Because a general setting would be silly. Already was for unredirection. (In reply to comment #199) Put a rule in Window Rules (component Window Behavior) selecting the window, then in Appearance Fixes (last tab), set Block compositing This will unfortunately not work with unmanaged windows (and for some strage reason most SDL games are; though i expect they will have to change if they still want to be fullscreened on wayland as well) @Alex You should have received a RR that enables controlling this via kwin scripts. Instead there's now non-working (silently!) Yes, that's a bit unfortunate. We had to remove gl system detection from the settings because it occasionally caused (guess what) driver crashes (though iirc mostly amd) - killing the dialog or even systemsettings. And... Mutter and Compiz now do unredirection by default. They're probably just better than kwin then. Or will figure such things happen. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/850628 Title: When the Euphoria (GL) Screensaver starts, KWIN crashes To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/850628/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1069498]
None of the discussed more buffer swapping patches has been applied to kde 4.10 -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1069498 Title: KWin shows tearing despite of VSync To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1069498/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1061073]
(In reply to comment #37) I also noticed that low resolution videos (480p) play smoothly, as well as the HD videos but only when not viewed fullscreen. kcmshell4 kwincompositing, last tab. is suspend compositing for fullscreen windows checked? Do they play faster if you suspend compositing altogether? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1061073 Title: Desktop effects are slow and desktop corruption using mesa 9 To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1061073/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1061073]
Iff at all, rather http://quickgit.kde.org/?p=kde-workspace.gita=commith=9364f5a7579567f5ebcf537eccf6147416e0e7e0 or maybe http://quickgit.kde.org/?p=kde-workspace.gita=commith=55a2f19c8a41d9b3d13d69d776daf5730414 - Can you check reverting the commits? - Sure the intel driver (xf86-video-intel) / flash / vlc/libav didn't change between works and works not? This: Flash remained unaffected either way (it doesn't simply slow down, it fails to expand the video fullscreen and freezes the video). Smells suspicious, since with suspended compositing, kwin is actually out of game here. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1061073 Title: Desktop effects are slow and desktop corruption using mesa 9 To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1061073/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 850628]
*** Bug 310027 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/850628 Title: When the Euphoria (GL) Screensaver starts, KWIN crashes To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/850628/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 850628]
= IT IS COMPLETELY POINTLESS TO ADD FURTHER CRASH REPORTS TO THIS BUG. = This is a *Driver Bug*. We cannot do anything in KWin to fix this bug. Recent versions have fullscreen unredirection disabled by default. If you enabled it and encountered this bug, just disable it again - there is no other fix. Open konsole and enter: kwriteconfig --file kwinrc --group Compositing --key UnredirectFullscreen false qdbus org.kde.kwin /KWin reconfigure qdbus org.kde.kwin /KWin toggleCompositing qdbus org.kde.kwin /KWin toggleCompositing Or use systemsettings or kcmshell4 kwincompositing to configure it with a GUI -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/850628 Title: When the Euphoria (GL) Screensaver starts, KWIN crashes To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/850628/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 410432]
workaround for the particular window effects related crash https://git.reviewboard.kde.org/r/105339/ -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/410432 Title: QDragManger crashes in various applications To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/410432/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 410432]
Different from Qt gtk+ does NOT seem to grab the pointer for DnD operations (i was still able to QCursor::setPos()) and therefore neither causes the issues on screen borders nor this nasty crash. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/410432 Title: QDragManger crashes in various applications To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/410432/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
