[Bug 1252235]
the fade effect runs 600ms at normal speed (non-linear, we're cheating because of another issue) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1252235]
hotfix: https://git.reviewboard.kde.org/r/114146/ Random note, "KWindowSystem::compositingActive()" only tests whether *some* compositor (xcompmgr, mutter, e17 ...) is running - not that kwin is running. With the hotfix there's no need to wait a lot for kwin (test for the screenshot effect dbus interface), but for other compositors you want to wait for a second anyway (eg. explosion or burn effects take quite some time) @Mehran You'll completely loose the ability to shoot occluded/translucent/shadowed windows by that approach and it's equal to simply pressing "Shift+Alt+F12" to take the screenshot. Also one could add a window rule for that purpose. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1252235]
(In reply to comment #28) > When we destroy the Deleted we send a client > message to the window. Which is not generally supposed to be there or still the drawable that it was when it was unmaped (re-used. i think mozilla apps do that) > In KSnapshot we add an x11 event filter and delay the > snapshot till we got the client message. Some close effects can take a fairly long time (explode and stuff like that), ie. we'd considerably slow down screenshot taking, basically forcing a delay while it seems (see comment #24) that the appreciated feature was to have the unwanted ksnapshot dialog vanish as fast as possible. IMO this either needs async or a 2 step processing. for the latter ksnapshot would send a sync dbus command to the effect to prepare it for taking control over the window and when that's done, close the window - which the effect now forces down immediately - and call the effect for the snapshot, what will also cause the effect to release control over the dialog. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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&t=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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446865]
Firefox or cairo-dock were certainly not targetted or affected by the related patches. This only affects Qt applications directly, so if that indeed triggered something, either the session crashes on logout or the mentioned applications used some timer based self-quitting (and are thus no more alive when the session ends) -- 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-b...@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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446865]
*** Bug 348566 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: kwin does not remember on which desktop to open windows on session start To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
~/.cache/ is a red herring to this bug (at least estimating from the initial report, and notably the two backtraces we have, yours w/ an error in xinput and Martins apparently hanging in the xcb event reader) - it's just that there was a popular bug in that direction that caused random freezes and many ppl. randomly attached here. I mostly wanted to know whether this is a virtual machine as that might have had impact on xinput as well. In case you worry about your GL/dri setup, I suggest to check the output of glxinfo and inspect /var/log/Xorg.0.log and on remaining issues head over to forum.kde.org for optional assistance on the system setup to not further clutter this bug w/ unrelated things ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
That's interesting, stalls on an error in libxinput: Thread 1 (Thread 0x7f4f6011a7c0 (LWP 21858)): #0 0x7f4f582f254f in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f4f5b27a2e5 in _XReply () from /usr/lib64/libX11.so.6 #2 0x7f4f5b27cc11 in _XSeqSyncFunction () from /usr/lib64/libX11.so.6 #3 0x7f4f5b27c3ef in _XError () from /usr/lib64/libX11.so.6 #4 0x7f4f5b279477 in handle_error () from /usr/lib64/libX11.so.6 #5 0x7f4f5b279525 in handle_response () from /usr/lib64/libX11.so.6 #6 0x7f4f5b27a3b9 in _XReply () from /usr/lib64/libX11.so.6 #7 0x7f4f4bfd7ed2 in XIQueryDevice () from /usr/lib64/libXi.so.6 #8 0x7f4f4c22df5f in QXcbConnection::xi2SetupDevices() () from /usr/lib64/qt5/plugins/platforms/libqxcb.so #9 0x7f4f4c22f6c0 in QXcbConnection::xi2HandleHierachyEvent(void*) () from /usr/lib64/qt5/plugins/platforms/libqxcb.so #10 0x7f4f4c22ff2b in QXcbConnection::xi2HandleEvent(xcb_ge_event_t*) () from /usr/lib64/qt5/plugins/platforms/libqxcb.so #11 0x7f4f4c20c96d in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () from /usr/lib64/qt5/plugins/platforms/libqxcb.so #12 0x7f4f4c20d2fb in QXcbConnection::processXcbEvents() () from /usr/lib64/qt5/plugins/platforms/libqxcb.so #13 0x7f4f5e50037e in QObject::event(QEvent*) () from /usr/lib64/libQt5Core.so.5 #14 0x7f4f5ed524fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #15 0x7f4f5ed575d8 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #16 0x7f4f5e4d234d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #17 0x7f4f5e4d5012 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQt5Core.so.5 #18 0x7f4f5e5235a4 in QEventDispatcherUNIX::processEvents(QFlags) () Another this to mention is MESA is on the SW rasterizer: Thread 2 (Thread 0x7f4f43fff700 (LWP 21882)): #0 0x7f4f582f254f in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f4eb1b156d3 in thread_function () from /usr/lib64/dri/swrast_dri.so #2 0x7f4eb1b14fd7 in impl_thrd_routine () from /usr/lib64/dri/swrast_dri.so #3 0x7f4f582ee204 in start_thread () from /lib64/libpthread.so.0 #4 0x7f4f5fc213dd in clone () from /lib64/libc.so.6 => Is this in a virtual machine? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
(In reply to Alexander Potashev from comment #100) > I don't get why discussing it on the forum is better than on this bug tracker? Because, assuming there's an issue w/ your OpenGL setup (which causes invocation of the software rasterizer) this has by 99.9% chance nothing to do with this bug (which in its core might or might not be about some libxinput error, we lack details from Ruchir in this regard, but it's the best track we have), which already is a mess of unrelated posts anyway (it's de facto unfixable, because it has turned into some unspecific "something hangs" report) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446865]
(In reply to Daniele Orlandi from comment #44) Despite nobody here really cares about those flags you're of course absolutely right: If, as you pointed out, the "whole session management" is broken, it really doesn't matter whether KWin restores the window attributes in this disfunctional environment. So I simply fixed that state for you. PS: if you just wanted to make a point- and informationless "I have an uninformed opinion" post, we invented Facebook to spare the rest of the internet this kind of spam. PPS: next time maybe spend 5 seconds on reading across the bugreport before posting *anything* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: kwin does not remember on which desktop to open windows on session start To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
This is rather unrelated - although this bug has become a general "I perceive a problem" dumpster anyway. The original report actually sounds a lot like related to bug #340294 The we have some reports which are likely related to the stale lock file bugs in KConfig & Qt: https://codereview.qt-project.org/#/c/110346/ and https://git.reviewboard.kde.org/r/122549/ Then we've complete freezes of the X11 server Finally there're some "kwin artifacts after" issues - this matches yours and I bet your right arm that you've an nvidia GPU - the invalidated vertext buffers will more likely relate to te switch to VT1 than anything else (run "dmesg | grep NVRM" and check whether it says something about unspported framebuffer consoles, but this lately was reported regardless) VLC will likely require 100% cpu because it (or rather the driver) is performing a busy wait for the next vblank signal (which is not gonna occur) The most simple resolution of invalidated vertex buffers is to restart the compositor (press SHIFT+Alt+F12 twice) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
Please notice that while this bug is now a random collection of unrelated problems, issues with the plasmashell process are misreported here for sure, so please file a bug against plasmashell. I doubt that any of the konsole output is relevant, but if it systematically happens after resuming from STR: do you have an nvidia GPU (and use the nvidia driver)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437260]
nvidia 352.09 - other font rendering is ok. Craig, the preview seems to use its own rasterizer implementation (and there's xft in the code ;-) I wonder whether that's either necessary and feasible (given that Qt5 exclusively rasterizes internally now) - or one should just QPainter::drawText() down the lines (also reflecting what it will *really* look like in KDE5 applications) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446865]
(In reply to Robert Kaiser from comment #68) > Hrm, if Qt5-based apps (like the KDE apps) don't start up by default and > only old KDE4 ones do, that's an argument for not updating yet at all, > sadly. Are there bugs filed for that? None that I could find, but I found https://bugreports.qt.io/browse/QTBUG-28228 which suggests that all session management was entirely uniplemented before Qt 5.2 ... :-\ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: kwin does not remember on which desktop to open windows on session start To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446865]
(In reply to Sergio from comment #65) > > Session restorage has nothing to do with single/multiuser questions. It's > > about session restarts, not about multiple sessions. > > True. But if you have a single monitor and a single keyboard to share > between multiple users, you have people stopping and starting sessions all > the time. No? You can start several sessions simultaniously - I frankly don't know whether KDE would even allow to start a session for a new user without locking the current one. The only problem would be if you're short on resources and/or have no swap device and/or a process of one user starts running wild. (Might be interesting to stop all processes of the non-current user when switching sessions?) But under normal conditions, it's no problem. > 1) One definitely needs commit 3442664609284ea201d50f6da27222c706a75c8e on > kwin. yupp. > Can it be expected to apply over stable kwin 5.3.1? The patch can be used functionally - whether you'll run into an unresolvable patch conflict (patch not knowing how to apply this, you'll have to help), I can't say for sure (but don't expect so) > 2) Furthermore, one needs to patch QT5 with: > 0001-Forward-QWidget-windowRole-to-QPlatformWindow.patch Not necessarily - the *really* important thing in this context is SM_CLIENT_ID (but it certainly won't hurt) > from https://bugreports.qt.io/browse/QTBUG-46310. Which I do not know if is > expected to apply cleanly on 5.4.1 (does anyone know btw?). Trying > guessing ;-) (But I think Stefan actually wrote it on top of 5.4.1) > Is this all? This will still NOT prevent Qt5 clients from not restarting at all (they somehow randomly fail to be recorded by the sessionmanager, likely killing themselves on the "session about to end" signal or whatever) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: kwin does not remember on which desktop to open windows on session start To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446865]
(In reply to David Lang from comment #67)
> Thomas, if you start lots of sessions without anyone logging out, you
> quickly run out of system resources for all the running apps.
Risking a little OT, "which"?
RAM? => https://wiki.archlinux.org/index.php/Swap
The only actual problem can, as mentioned, be at some point a slowdown
due to CPU overload by misbehaving processes (and while I don't think
kdm or sddm or even logind support this, this could in theory be covered
by stopping processes for all users that do not hold the current
session)
> But even with a single user on a laptop, I have to deal with the pain or
> restarting sessions regularly because the laptop doesn't stay plugged in all
> the time and doesn't have an infinite battery.
Hibernate?
In case it's not clear, this is from my position *not* a discussion on whether
session management should better work again at some point (it certainly should,
for there *are* reasons to log out, eg. to reboot the kernel or shutdown to
have the system fully encrypted/stashed)
It's just that multiuser environments (or battery limitations - unless you wait
too long ;-) don't somhow enforce session restarts at all, so please don't try
to make that your argument for working session support. It's factually wrong.
> The fact that KDE4 would detect when firefox was running at shutdown (even
> when I start it manually from a shell window) is a bug as far as I'm
> concerned.
It's actually a setting ("kcmshell5 smserver", also on SC4 for "kcmshell4", but
I'm not 100% sure whether the module was named smserver than as well) and
really completely unrelated.
> Go ahead and restart apps that I started through the KDE menu,
> but don't try to detect apps that I start from the command line
That's unfortunately indistiguishable.
> start them automatically (especially when you do so without the command-line
> parameters I provided)
That's actually a client bug, for it tells the smserver about the command it
wants for a restart.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1446865
Title:
kwin does not remember on which desktop to open windows on session
start
To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446865]
(In reply to David Lang from comment #70) > only if you only do this by looking at what's running at the time you > shutdown. Nothing is tracked or something. There's a session protocol and clients can support it and call for a restart or not. They can notably define *how* they want to be restarted (commandline). Even if it was not: restarting only clients that were launched through a specific interface is a pretty much instant fail. Should we care about kickoff? krunner? plasma panels? what about 3rd party dockers? Should we estrablish a protocol that each and every runner/docker/whatever needs to support? Let alone the mess that this would cause for less integrated environments as well as the most obvious question, *why* to discriminate processes that were started from eg. konsole. (Eg. I *very* often launch kwrite instances from konsole) > But if you are actually trying to restart all apps As pointed out: it's configurable and you're free to start with a blank session or an explicitly stored one. > then you are failing miserably. Thank you - But maybe better read into the topic next time. > I routinely have many apps running in terminal windows that don't > get restarted, as well as a few GUI apps (almost none KDE/Gnome apps) that > don't get restarted. As mentioned, clients either support this (dead old) protocol or not. Qt5 is apparently buggy itr. and atm. > Other apps that get restarted are missing the context > (what files they had open, etc) The apps get a signal "the session is gonna end, save your stuff" and a signal "session restarted, your last id was 123456" - what they do with that is their thing and not job of the session manager. == OFF TOPIC > swap is horrible to use swap is slow, yes, but unless some process runs wild, the logged out user will quickly get swapped out in favor of the active users processes (notably when stopping processes) Since the user isn't logged in, he doesn't care. > I've actually had a machine with 128G of RAM that only had 120G of disk. My > VMs for work > typically have 40G of disk or so, even if they have 32+G of RAM Sorry, but personal design decisions do not form a concept. Naturally a multiuser (for multiseat you obviously need tons of physical RAM) system would be designed different (hard quotas and sufficient swap space to protect user processes agains other users processes causing OOM) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: kwin does not remember on which desktop to open windows on session start To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446865]
(In reply to Sergio from comment #60) > KDE web page that KDE development mainly focuses on single user workflows Session restorage has nothing to do with single/multiuser questions. It's about session restarts, not about multiple sessions. > - if wily's qt 5.4.2 contains the same fixes that are in the Fedora package > mentioned above and if it can be safely backported to vivid in a ppa See comment #49 and comment #52 on the Qt patches. They're not in Qt upstream - not even reviewed. > what additional patches are needed on top of the kwin package contained in > the kubuntu kde > backports ppa, to see if a fixed package can be shipped in a further PPA I don't know what's in "backports ppa", but you'll need either KWin >= 5.4.0 (not yet released) or https://git.reviewboard.kde.org/r/123580/ + the forementioned Qt patches (for Qt5/KF5 clients - otherwise only Qt4/gtk/etc clients are properly restored by kwin) For client internal issues (what especially also includes "restarting Qt5 applications" when "restoring the last session" itfp) I'm not aware of any present patches. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: kwin does not remember on which desktop to open windows on session start To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
sounds af if first kwin and later on, random clients get stalled (or the x event queue turns garbage) can you please try: export KWIN_USE_INTEL_SWAP_EVENT=0 # only affects intel IGPs export KWIN_EXPLICIT_SYNC=0 # most likely candidate on nvidia GPUs export KWIN_USE_BUFFER_AGE=0 # well, you tried, but hey ... ;-) kwin_x11 --replace & -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
And after those few seconds? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
(In reply to Turbo from comment #83) > Simple things like using Dolphin can generate random -and very heavy- CPU > spikes on every core. The crucial question is "in which process", if it causes spikes in dolphin, that's a dolphin issue. There's however also bug #312919 about high cpu load caused by the qml spinner plasma-desktop shows for kio actions (and other stuff) In general, the description is too unspecific to be assigned anywhere. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
Ensure to show all processes, it may be a system process. (As alternative, just run "top" in konsole...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
Please notice that comments #44-#51 focus on something (upstream) that looks like a stalled nouveau driver, impacting even input. This bug is originally about insufficient repaint events. See comment #24, comment #34 (it's now "kwin_x11 --replace" ;-) which does however not resolve for comment #41 (comment #43) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
Did you figure which "shit" in particular, for there're now actually several completely unrelated issues (affecting different parts of the software stack; kernel, kio, kwin) mentioned here, so your comment, though not very informative, might be misadressed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
(In reply to truf from comment #78) > No any hotkeys helped. If that include SHIFT+Alt+F12, it's not the compositor freeze (this bug originally) > Eventually I damaged the system (by doing hard reset every freeze) Due to journaling filesystems, that is rather unlikely, but you may have left stale lock files around. > changed composer to OpenGL 3.x + installed all proprietary drivers except > Nvidea. "nvidia" ;-) > The problem still not appeared. So the bottom line is that after wiping the cache, the issue is gone? -> see comment #73 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446865]
It's not the same bug, but related - session management somewhat "largely" changed and was not or not sufficiently ported (I ran pretty much through the code yesterday and then figured that for some reason the sessionKey() changes _very_ early during the application start, so right now kwin reloads the "wrong" session config. Got to figure where it changes tonight ;-) So please notice that even if (optimitically: when) this bug closes, that does NOT mean session management in KF5 apps would completely work as it does in KDE SC4. I assume the vast majority of clients needs to be ported by hand (ie. eg. konsole is oc. responsible for managign its tab layout, this is nothing the WM could even possibly do) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: kwin does not remember on which desktop to open windows on session start To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446865]
That said, I started to look into it last night. Ivan, how far have your efforts gone so far? Otherwise I think I can have a patch by the end of the week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: kwin does not remember on which desktop to open windows on session start To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 850628]
Git commit f215bfb502461f2c2b281d023b0a92b2464422d7 by Thomas Lübking. Committed on 28/07/2013 at 19:44. Pushed by luebking into branch 'KDE/4.11'. write back unsupported (kwin-intel) unredirection to have a minimal hint on "this does not work" REVIEW: 111772 M +3-0kwin/options.cpp http://commits.kde.org/kde- workspace/f215bfb502461f2c2b281d023b0a92b2464422d7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
that's still unspecific, because it's not clear wheter a (all) clients
do not repaint or are entirely stalled or the compositor doesn't update
or is stalled.
if shift+alt+f12 works only the compositor doesn't update, if not, it
either doesn't respond or the issue is in the clients ("applications",
including the desktop shell) or X11.
For any progress, it's crucial to localize the problem - it's not
possible to fix symptoms.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
(In reply to EMR_Kde from comment #128) > > Be reminded that this bug will *never* fix since it turned into a random > > "something doesn't work" report mess. > Which is why I stopped using KDE, opting for LxQT. Because KDE users sometimes flood a bug with so many unrelated "I have a problem as well" comments that at some point nobody can say what the problem in the bugreport actually is? The first 24 comments are a valid bug, the rest started to mess up things with every post. Sorry. Comment #56 seems to indicate it was a problem with the intel driver, maybe then still used by default intel swap events. And if you're not using KDE, what the heck are you doing here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
If you can move to another VT it's unlikely required to reboot the system. First try to suspend the compositor (SHIFT+Alt+F12), notably if *everything* hangs (visually, you can actually inspect the condition of random processes from the other VT) If that "helps", resume it (same shortcut), obtain the output of qdbus org.kde.KWin /KWin supportInformation and file a new bug. Be reminded that this bug will *never* fix since it turned into a random "something doesn't work" report mess. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
(In reply to SinClaus from comment #129)
> At the morning screen is blank (screensaver), mouse move open desktop as a
> picture. SHIFT+Alt+F12 doesn't work, qdbus answers
> "Error: org.freedesktop.DBus.Error.NoReply
> Did not receive a reply. Possible causes include: the remote application did
> not send a reply, the message bus security policy blocked the reply, the
> reply timeout expired, or the network c
> onnection was broken."
That sounds as if the kwin_x11 process stalled, but if the screen is
locked, it's expectable that SHIFT+Alt+F12 doesn't work (all input is
grabbed by the screen locker which might be the troublemaker here)
==> does this also happen if you do *not* lock the screen with
suspending to ram??
If yes, check if kwin_x11 running and not just sigstopped ("ps ax | grep
kwin_x11" lists it with "TN" instead of "SN")
If it is, gdb into it to obtain a backtrace on the location where it's stalled.
Howto do that (using ssh is preferable, to not alter the inspected system by
changing to another VT)
https://community.kde.org/KWin/Debugging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
The original bug was *not* about the plasmashell process, but the entire session (unless suspending the compositor what in return made everything but the plasmashell desktop responsive at least, I suspect an intel driver issue, but we never figured it. Notably Ruchir stated that "Alt+Tab" would "fix" it) @SinClaus The screenlocker is unrelated to the kernel or the distro, but part of the ksmserver process (KDE feature) - I don't know the default behavior for STR, but it /can/ activate with it. To check whether your session is locked, try export DISPLAY=:0 qdbus org.freedesktop.ScreenSaver /ScreenSaver GetActive -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
That sounds like a stalled kwin process. Please file a new bug and there attach the output of qdbus org.kde.KWin /KWin supportInformation (obtain it while the compositor is running "ok" - you can toggle the compositor anytime with SHIFT+Alt+F12) Also, if possible obtain and attach a backtrace for the stalled kwin process, according to https://community.kde.org/KWin/Debugging (but first just file the bug with teh information instantly available) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 252002]
https://git.reviewboard.kde.org/r/125658/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 252002]
Git commit 3b690ae01b31faaddaa38ca6ef5425ef68f7546c by Thomas Lübking. Committed on 19/10/2015 at 19:20. Pushed by luebking into branch 'master'. Do not treat the context menu button as modifier It's not and not treated as such by Qt either. In addition suck context events while recording (so it doesn't activate, rather cosmetic) FIXED-IN: 5.16 REVIEW: 125658 CHANGELOG: Allow to bind the contextmenu key (lower right) to shortcuts M +6-1src/kkeysequencewidget.cpp http://commits.kde.org/kxmlgui/3b690ae01b31faaddaa38ca6ef5425ef68f7546c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 975056]
This is *not* a bug in KWin, but nevertheless see bug #256242 for a vast discussion on the matter (also briefly covering kglobalaccel) The basic problem here is that kglobalaccel operates on head-unaware dbus and only runs on one head. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/975056 Title: KWin shortcuts don't work on second monitor To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/975056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
If you've a specific error, please file a new bug and log the errors there. *This* bug is meanwhile a mess of random "somthing doesn't work" reports (full /var, corrupted plasma theme caches, whatnot else) and can thus never be treated nor fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
See eg. http://forums.fedoraforum.org/archive/index.php/t-247253.html Please notice that nouveau has nowhere production quality reg. OpenGL - Plasma 5 with its pleathora of GL contexts is likely just "too much". Unless you've a very strong reason (unsupported HW) resort to the nvidia blob. Otherwise I suggest to avoid OpenGL as much as possible (ie. disable HW acceleration in firefox etc, use xrender compositing) in case of troubles. And ensure to run recent kernel and mesa versions (not stable/reliable at all, but likely less static bugs) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
*** Bug 339562 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
Stupid question, does this > starting plasma with compositing disabled works as expected, ie plasma > starts, but freezes start to happen shortly after this. imply the "freezes" also occur *without* any compositing? About > though alt+f2 (to bring up krunner) is not working can you (w/ suspended compositor, that's hopefully unrelated) qdbus org.kde.krunner or does it time out as well? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
For pot. culprits, check netstat -nxp | grep dbus (do NOT post that list anywhere unrevisited!!) overall, I doubt that you encounter /this/ bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
Matteo & Sebasitan encounter sth. around https://codereview.qt- project.org/#/c/110346/ or https://git.reviewboard.kde.org/r/122549/ Totally unrelated to this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
export KWIN_USE_INTEL_SWAP_EVENT=0
export KWIN_EXPLICIT_SYNC=0
export KWIN_USE_BUFFER_AGE=0
export LIBGL_DRI3_DISABLE=1
kwin_x11 --replace &
In case that works, please figure ("unset FOO_BAR") which variable does it.
Can you obtain supportInformation while the compositor is up? (try "sleep 30;
qdbus org.kde.kwin /KWin org.kde.KWin.supportInformation", then press
SHIFT+Alt+F12 to toggle the compositor and just wait a minute or so before
toggling it off again)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446865]
Git commit 3442664609284ea201d50f6da27222c706a75c8e by Thomas Lübking. Committed on 17/06/2015 at 22:18. Pushed by luebking into branch 'master'. port session management to KF5 REVIEW: 123580 M +1-2main.cpp M +3-0main.h M +5-4main_x11.cpp M +55 -31 sm.cpp M +0-13 sm.h M +8-14 workspace.cpp M +7-2workspace.h http://commits.kde.org/kwin/3442664609284ea201d50f6da27222c706a75c8e -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446865 Title: kwin does not remember on which desktop to open windows on session start To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440210]
(In reply to Ian Newton from comment #102) > With ... KDE 4.14.9 Whatever you spotted is likely unrelated. This bug is reported on KDE 5, the stale lockfile issue is a Qt5 problem and Haswell (your chip) isn't nearly similar to ironlake (while they may of course have similar driver bugs) In case *only* the desktop froze, it's a problem with plasma-desktop. --- PS: i think we need to dissolve and close this bug - it's become a pointless mess of random "something doesn't work" reports what notoriously attracts just more unrelated reports (because noone can reasonably say what this bug is about) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446865]
So, looking into the Qt sources a bit more it seems that
a) Session management is FUBAR in Qt5 and actually was likewise FU in Qt4 -
adding the proposed flag will only restore the completely FU condition of Qt4,
ie. allow clients (KDE) to workaround the brokeness ...
b) this actually *only* seems to affect the xcb platform
("GuiApplicationPrivate::commitData()" is only called by
"QPlatformSessionManager::appCommitData()" which is only called by
"sm_performSaveYourself(QXcbSessionManager *sm)" in QXcbSessionManager)
Restoring the Qt4 state however won't cut it: KApplication is deprecated
and there's no Guarantee for a KMainWindow around. Also every "plain"
Qt5 client that can be found on KDE users desktops (qupzilla, trojita,
... whatever) won't be covered.
If you "seem to be the expert on session management" we need to define a
roadmap out of this mess, or it's never gonna happen.
What do you think about this process:
1. emit commitDataRequest()
2. at this point either the logout should be canceled (requires API addition on
QSessionManager to wire up sm_cancel; internal requirement only though. Maybe
kept in d_ptr contexts) or there thould be no windows with
QWidget::isWindowModified() or modal transients around since that indicates
some user interaction should have taken place but didn't
3. If we detect missing interaction, spam a QMessageBox and inform/ask the user:
"It looks like the application should have intercepted the logout request,
but didn't. Do you wish to cancel the logout and explicitly save data? Since
this is an application bug and this failsafe check will be removed with Qt6,
please file a bug against the application."
4. If this still didn't cancel the logout, start closing windows depending on
an application attribute (see below) and a trumping environment variable
QT_CLOSE_WINDOWS_ON_LOGOUT_REQUEST (to pass the user ultimate control over the
behavior)
5. Remove attribute, failsafe check and (actually even documented, we can NO
WAY just remove this in Qt5) window closing in Qt6
I'd go for the application attribute since indeed there's little point in
adding functions to implement a short-term workaround.
Actually, I might even be in favor of a dynamic property
(QObject::setProperty()) since it will spare the clients compile time checks -
we an add this to KFooBar now, even though Qt 5.6 (or whatever) is not on the
horizon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446865]
Yes, my concern is that status quo for several/many applications is that they do no connect to saveStateRequest() or commitDataRequest() and *only* perform interaction on window close events (since this is the regular case *during* the session) Stripping this mechanism will cause a behavioral change that is prone to cause data loss on session exit - thus such change may be denied upstream. If so, the status quo can be restored by sending close events w/o causing a) the actual loss of windows in the running session b) the application to "accidentally" quit early I don't discuss "what should be", but "what mess have we caused and how do we get around that" ;-) -- 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-b...@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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446865]
(In reply to Andreas Hartmetz from comment #18) > How should that be done, sending close events and expecting applications to > save their state in response, but not close windows or the application? QCloseEvent ce; QApplication::sendEvent(window, &ce); You only want to emit the event, the widget doesn't close in response - the event is (usually) emitted when it wants to close. > It would mean that applications are session management aware No, it means they give a shit about "session management", but they do care about what happens when the user (or anything) tries to close a window. The present code in Qt's SM tells me that this is considered the predominant way to handle data-safety - also because it's the regular incident. Notice again that this data protection mechanism has *nothing* to do with session management in particular, eg. whenever you try to close a kwrite window w/ modified text, it will ask you "err, really? maybe safe the file before?" - and at this point the user can also say "whooops, no - I didn't want to close at all" The present code triggers this mechanism and it might be required to preserve that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437260]
Sure it's this bug? Can you provide screenshots of UXA and SNA rendered fonts? -- 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-b...@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, &cleanupXImage, 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, &cleanupXImage, xImage);
}
inline int point2Pixel(int point)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437260]
https://git.reviewboard.kde.org/r/126713/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 &txt, const QColor
&bnd, int w, int h)
XftColorAllocValue(QX11Info::display(), visual, colorMap, &xrenderCol,
&itsTxtColor);
}
+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, &defaultVinfo, &num_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, &cleanupXImage, xImage);
+return QImage(xImage->data, xImage->width, xImage->height, xImage->stride,
imageFormat, &cleanupXImage, xImage);
}
inline int point2Pixel(int point)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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, &cleanupXImage, xImage);
+return QImage(xImage->data, xImage->width, xImage->height, xImage->stride,
QImage::Format_RGB32, &cleanupXImage, xImage);
}
inline int point2Pixel(int point)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Ubuntu Bugs, which is subscribed to the bug report. 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437260]
a) @Martin K., wtf happened to Craig, is he fine? (pm me in doubt) b) in any case this is apparently unmaintained bitrot - and that's neither an "excuse" nor a "reason" for the bug - it's an "explanation" c) it /is/ a hell lot of rather opaque code, but as mentioned most of it seems to go into a custom font renderer. My personal assumption would be that this could just be omitted, but I have no knowledge on why it's therer itfp. (I first and only glimpsed at the code on that one occasion) With the author/maintainer absent, one may simply resort to that and see what other bugs cook up (then simply revert the commit on trouble) d) nothing of all that excuses the attitude of some people here around. It annoys you? Hell, just fix it. You can't? Well, find somebody. In doubt set a bounty. You can neither? The you got to live with it. Reporting bugs is important and a valuable contribution, but the first answer to "why is it not yet fixed? why is it not yet fixed?" is always "because you didn't fix it?" And you better start begging that Craig is ok and just moved on. For any solution: -- Iff Craig won't return, we'll need somebody to pick the component as maintainer (and fix it). That is important because the "fix" may break other things and somebody has to care about it. If you want to give it a try (assuming the scary fontconfig code gone, it should actually not be very hard - it's a choice the maintainer has to take; i'm not too convinced that the custom rendering can be rescued with the changesto Qt5), feel free to ask for advise and help anytime (ideally on the kde-devel mailing list) > > > It makes Plasma look amateurish. > No, It MAKES Plasma/KDE amateurish! And how do we call people who use amateurish software? :-P -- 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-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1437260]
(In reply to Martin Klapetek from comment #33) > But I'm thinking we could just add brand new font rendering > widget to the kcm that replaces the old one and leave everything > else in place (including the bitrotted code). Hummm... that kicked something in my brains. The view isn't only required for the kcm, but also for kfontview. In addition it must be able to handle *specific* fonts from files, which are not (yet) installed in the system - so I guess the cause for the custom code was either the absence of QFontDataBase before Qt 4.2 or it's dependency on fontconfig? @Thomas S.: you'll have to make use of the class when/if porting the view. Reg. the multiselection: the view replaces the preview by a list of the selected font names in a QLabel here then (what oc. works like any regular font rendering), but the broken rendering does look like an issue with the color/alpha channels - what you indicate the "wrong" visual id or picture format is selected (yet even if, the code is too complex if the task can be done by QFontDatabase + QPainter) -- 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-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1446865]
KWin is not responsible for restarting applications. This bug was *only* about not restoring window manager attributes (position, virtual desktop, etc.) on session restorage. There're fundamental bugs in Qt5 that prevent (both, correct and entire) restoring of Qt5 applications, see * https://codereview.qt-project.org/#/c/113806/ * https://codereview.qt-project.org/#/c/113901/ * http://marc.info/?l=kde-core-devel&m=144832700109449&w=1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1437260]
Git commit 9977edac12d6bec56f8d9cf7f97529177ca842eb by Thomas Lübking. Committed on 15/01/2016 at 21:02. Pushed by luebking into branch 'Plasma/5.5'. fix font preview colors the image format was hardcoded to ARGB32_Premultiplied, but that's not generally correct, notably not on 24bit servers FIXED-IN: 5.5.4 REVIEW: 126713 M +41 -1kcms/kfontinst/lib/FcEngine.cpp http://commits.kde.org/plasma- desktop/9977edac12d6bec56f8d9cf7f97529177ca842eb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446865]
> 5. I completely don't like the proposed way to preserve the compatibility > with (4) and make > the use case of broken session management client implementation legal and > default, but > also try to allow proper-written apps to still survive somehow, adding some > strange > workarounds to Qt as closing all the windows, but not too much, or API > properties to enable > proper processing of SM messages. No ofense, but what you "like" is completely irrelevant. You propose to intentionally break clients by library changes in some minor update, to teach developers to do right, but while you might aim their face, you're gonna hit the users (and probably yours) We had that (I kindly remind of the qDeleteAll fix ...) and it cooked up hell. commitDataRequest hardly shows up in lxr.kde.org, what means it's probably not used at all and aboutToQuit (which isn't used but could come to rescue) isn't used too much either. The BY FAR! omnipresent pattern is to listen to queryClose() which is called/emitted on -guess what- close events from KMainWindow. And that's for pretty much sure why the (wrong) behavior in QSessionManager exists. Is this behavior correct? No. Does this matter? NO! It's ok to spam a #warning that this behavior is shit and deprecate and kill it for Qt6 and we might even bail out (aka "fix") KMainWindow applications NOW by invoking queryClose() on QGuiApplicationPrivate::commitData() but regardless, we MUST assume this to be a global default pattern that applications (also beyond KDE) rely on (also because it's absolutely natural to intercept closing to save data and not think of closing on session end could be something entirely different - actually the illegal behavior happens to be the most sane one...) Now, *actually* closing windows to test interaction on session end is of course just as wrong - if the user cancels the logout by such incident, we should not have closed random other windows before (letting alone that it causes this but) - therefore I frankly do not understand what's so complicated about just faking a close event to serve the present "save your stuff" pattern in a majority in clients without causing the destructive close itself which may not only be a bit premature, but also triggers this bug. It's the least invasive solution that does not require everyone to signal "yes, i can sessionmanagement" (what's not gonna happen) and we don't risk loosing the users data (or breaking the ability to cancel the logout) -- 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-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1446865]
(In reply to Alexey Chernov from comment #25) > According to what? According to "This is not fixed in years and each and every session management code was ported as "#if 0"" If there was some relevant interest, it would be fixed long time, since it's really not that hard. > > Loosing your data is however relevant for everyone. And the latter is the by > > far more severe issue. Restarting applications is merely an annoyance, > > loosing your work is truely expensive. > Hey, how could session management be "apparently relevant for only a > minority of users", but fixes in its behaviour be crucial for a lot of them? [...] > Fully agree here, but we should confirm that nobody said in the beggining > that upstream changes were about to break session management for KF5 > applications. It was just broken. Errr... what? Session management (in terms of "please restore the desktop as I left it") doesn't seem very important, but if you click "logout" and *booom*, gone is your work of the last two hours because the application had no chance (or, well, listened to the wrong events) to ask you to save it, that's pretty important... We're apparently talking past each other. There're two steps: a) logout, clients ask to save your stuff. That works (because of the close event) b) login, clients should restart. That's broken (because the close event is not just an event, but the window "illegally" being withdrawn during logout) You propse to fix (b) by breaking (a) and I'm trying to convince you that this is a really bad idea. > bugs which should be fixed either in library and its clients. It's better to > fix them when no one really relies on the stability too much. It looks like > this time is now for KF5-based application and environment. Yes, we should fix KMainWindow now (if faking close events is finally not considered a permanent behavior despite the majority of clients will probably do that in return to the data commit request - with a fair share actually just calling close() ...) but that has absolutely no implications on whether it's ok to easily break away from established (even though maybe wrong) behavior. > No, that's just postponing and messing up the whole problem. If, as you > stated, almost no one implemented easy and pretty simple interaction > appeared in Qt5, even less would care of possible bugs and corner cases of > the workaround, more complex protocol with close event you propose. There > would be just another argument that it's just too messy, not to mention > already existing argument that no one uses session management. Sorry, but I really cannot read any sense into this paragraph. Please try to rephrase it. The above isn't English grammar at all. > It won't be fixed until it's broken So you demand to jeopardize userdata because otherwise code won't be fixed. Sorry, but there's no way you're ever gonna convince me in this. Any solution that builds upon "jeopardize userdata" is not a solution at all. It's malicious. > I'm pretty sure there would be packages that would require just > most recent Qt version, and it would be acceptable. And jeopardize userdata. What exactly should this help in this case? > What's wrong in relying on changes in recent Qt release That you are not. "Recent Qt releases" start to jeopardize userdata because (no way) all Qt client code has been fixed, ie. distros must not use Qt 5.7 until all client code releases picked up the change. > In this way all the bugfixes should be postponed till Qt6 If a bugfix is *very* likely gonna break more things more badly than it fixes and there is absolutely no need to take this risk? Yes, avoid that fix and come up with a more robust interim solution. > By the way, are you completely sure your changes won't break any clients? > What if someone relies exactly on the current code? Err, on the close event? Well, that's exactly what I suggest to preserve. You're not gonna see more from a ::close() call in client code (it's no virtual and not invoked as slot) > In the opposite, close event or aboutToClose do mean closing > and quitting, but don't imply any data interactions (as it's too late) Errr, no. Please read the Qt API docs. You simply ::ignore() the close event and nothing is gonna be closed or changed. That's why it's massively intercepted to ask users to save stuff - what's also explicitly suggested in the API docs. And that's why somebody considered it a good idea to explicitly close windows on session end, what it's just not. That "somebody" actually wanted to trigger and check the result of the event, but not really close windows. And that's what I'm proposing to deal with the situation. The justification for QGuiApplication::commitDataRequest() though is, that a QGuiApplication doesn't necessarily have any windows at all and still wants to save stuff on logout (and of course before the SIGTERM) = Completely untested patch (not even a build attempt) for Qt 5.6: =
[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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446865]
(In reply to Alexey Chernov from comment #30) > The same way commercial customers or applications would be affected with API > changes. How an ABI styable API extension could affect anyone is frankly beyond me - I doubt it will help to resolve the problem but there's really no problem with it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446865]
(In reply to Alexey Chernov from comment #23) > Comments like this clearly don't help Seriously, you asked for breaking clients because that's what you'd "like" to do - what did you expect to hear? That's simply not an acceptable stance. > Never mentioned minor update or particular version. Please don't distort. So you meant to schedule this for Qt6? > Users were already hit when the significant part of functionality important > for someone's every day use case is broken. Let's be honest: session restorage is apparently relevant for only a minority of users. Loosing your data is however relevant for everyone. And the latter is the by far more severe issue. Restarting applications is merely an annoyance, loosing your work is truely expensive. Also there's absolutely NO reason why we should not care about both - except that you'd "like" to break client code and risk data loss for some reason that completely escapes me. > Still better than a couple of API methods like "enableSpecifiedBehaviour()" I fully agree on that proposal to be of little help - it will be mostly ignored or used w/o accounting the implications. > Once again: we all could already apply the fix of Andreas and be busy fixing > the necessary applications rather than keep discussing here. It does NOT only affect KDE applications, there're hundreds of Qt applications which might have adopted this pattern - or simply don't care about session management itfp. Also the proper order is to fix and roll out clients, *then* remove the deprecated upstream code. That's why "=> Qt6" for this approach. > On the Qt6 release you would say that everyone already rely on the > workaround there was in Qt5 etc. etc. No. Because you would tell people during Qt5 don't do this and don't rely on it because it's not gonna work with Qt6, so that when things are ported to Qt6, client code has to be fixed. Breaking it now and depending client behavior on whether it's linked against Qt 5.6 or Qt 5.7 is plain wrong and begging for trouble. > I just kindly remind your description of current Plasma 5 and it's > application state: https://bugs.kde.org/show_bug.cgi?id=341930#c30. Off topic? This was a global statement. Session management in particular is a different thing: few people seem to really care about restoring sessions. > In a couple of years We'll have seen Qt6 and this removed, but even if not - it doesn't matter. The QGuiApplication code will have a "// TODO Qt6" comment and the client code does not care about why there's a close event (which might be rejected, thus not causing eg. deletion anyway) > The only arguable point is whether it's safe to have it fixed now or should > another (possible API-changing) workaround should be added instead. No. Actually I propose to fix the "workaround" already present in QGuiApplication by turning "close()" into just sendind a close event (for that's actually the desired action) and by this fix session storage and maintain data protection with the present approaches. Breaking that behavior may happen for Qt6, anything else will be perceived as regression. On a sidenote: QGuiApplication::commitDataRequest() may be the "preferred" hook, but there's actually nothing that explicitly forbids "fake a close in addition", notably since it will trigger similar, if not equal client code. Given the status quo, I'd probably even just remove the commitDataRequest signal in Qt6 and rely only on faking close events - why should client code have to care about two different "aboutToClose" signals? Sounds stupid to me. -- 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-b...@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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1369424]
For general discussion on the topic of modal dialogs aligning to the mapping state of their leader, please see bug #339635 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1369424]
The behavior is deliberate (manage.cpp:~465 "// If a dialog is shown for minimized window, minimize it too") and likely intended to prevent the user from interruptions of minimized windows (the WM cannot decide whether this is spontanous or required) until the user moves focus to this window again. You will also notice that LOo does not unminimize nor (attempt) to gain focus if you open a *.ods (which does not require a conversion dialog) More interestingly, though the dialog is initially modal for the present window, it opens a new window with the csv (here at least), ie. the transiency and modality seems questionable in the first place. - My suggestion would thus be to rather "fix" the "libreoffice" script to either map/raise/activate the mainwindow when opening a new document? Something like if [ -e "$2" ]; then wmctrl -x -a libreoffice fi on the head of /usr/lib/libreoffice/program/soffice ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175299]
(In reply to Thomas Pfeiffer from comment #8) > Users who - for whatever reason - place > "exotic" buttons like the ?-button between more common ones (like close or > minimize) may find it irritating that the more common buttons "jump around" > between windows which have the exotic buttons and those who don't. Please notice that this is not limited to exotic buttons, "close" and "minimize" may be and "maximize" will regularily be disabled (for fixed maximum/size windows, some dialogs etc.) -- 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-b...@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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267977]
see bug #330794 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267977 Title: Extreme jerkiness with kwin compositing on Nvidia binary driver after upgrading to 4.11.5. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1267977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283820]
iow it was NOT fixed by 10.1 rc3? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1252235]
You're very much likely not using a compositor (if you do, you can skip reading here), thus claws has to repaint the area that is exposed by the ksnapshot withdrawal and it apparently needs "some time" for this (more that the few ms that ksnapshot afair delays anyway) -> try with another GTK+ style (they do largely differ in their repaint speed), but it could also just be claws itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1369424]
http://kde-look.org/content/show.php?content=167372 The script only applies to transient dialogs and unminimizes the main window as well to ensure context. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1252235]
[I cannot reproduce this, however] Actually, ksnapshot should take the screenshot before mapping any window. Together with the "shoots on save", this however sonds a bit like ksnapshot would trigger continuous shots. "kcmshell4 kwincompositing" - is the "screenshot" effect enabled? -- 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-b...@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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1252235]
That would imply that ksnapshot issues the shot before having (successfully) closed the window. That would hoever be very weird, since you'd need to click to trigger the shot unless there's a minimum of 1s delay. KSnapshot still disappears immediately and w/o delay or animation when triggering a screenshot here. -- 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-b...@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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 850628]
*** Bug 307442 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-b...@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 Ubuntu Bugs, which is subscribed to 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
