@Thomas: I have a new idea. When we destroy the Deleted we send a client
message to the window. In KSnapshot we add an x11 event filter and delay
the snapshot till we got the client message.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to ksn
> Fix the issue through setting blocking compositing
no! that's a very bad idea! I'm using ksnapshot quite a lot to capture desktop
effects.
for general information: I'm going to work on ksnapshot starting tomorrow. It
wants an XCB and Qt 5 port. Let's see whether I can also add a proper solutio
are you really using multiple X screens like :0.0 and :0.1?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1264821
Title:
kscreenlock_greet insecure with multiple X screens
To manage notifications a
ok, so it is multi-head.
This is a very uncommon setup and I doubt any developer is able to test
and verify the patch. From a quick look at the patch looks wrong to me,
because you use "i" as an index in QDesktopWindow::screen(). This looks
crashy to me and potentially wrong. In fact in your case
this sounds like your XServer "loses" the output - which should not
happen on power management. Could you please check whether that's the
case in e.g. /var/log/Xorg.0.log?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
> This is certainly fixable with X11
No, it's not. The problem is that a popup window normally grabs the
keyboard and while the keyboard is grabbed no other process is able to
get key events. The result is global shortcuts cannot work. As long as
the X11 protocol allows to grab the keyboard and as
Do whatever you want to do with this bug report, I'm out of here!
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/45843
Title:
Right-click context menu disactivates the very hotkeys (keyboard
I'm sorry but this bug is not fixable with X11. It's a design problem in
the X11 protocol and thus cannot be fixed on X11. It's pointless to keep
the bug open for X11 as it cannot be fixed. Also there is no other place
to report the bug and get it fixed. As it's a design problem in the X11
protocol
Good news: Plasma 5.4 will come with a new experimental Wayland backend.
With Wayland we are able to better handle this situation and this issue
should already be fixed in 5.4 on top of Wayland.
Given that it is an issue with X11 and unfixable with X11 I dare to mark
the bug as resolved.
--
You
(In reply to Sergio from comment #60)
> > I don't care about session management: because I do not restart the
> > session, I restart the session whenever the system freezes
>
> Under these premises, it would be a matter of clarity to state from the main
> KDE web page that KDE development mainly
I have now adjusted Aurorae in the linked review request for quick help
and on all desktops.
> 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
(In reply to Wolfram from comment #37)
> Who on earth has driven the Kubuntu-maintainers to switch to Plasma 5 so
> early, if it's "not nearly ready for productive use" as Thomas said ?
> In their currently released Upgrade to 15.04 there is no way to stick to kde
> 4, so people should be warned t
Thanks Robert for your comment! Just to make it more clear: if I get
whining here, I'm not motivated working on it. Now I also go to answer
why I don't care about session management: because I do not restart the
session, I restart the session whenever the system freezes, so session
management is no
The xcb errors are false positives (we cannot check whether a window is
gone and perform our cleanup on them nevertheless - doesn't matter
except for the reported errors).
Overall it sounds like the root problem is a hanging/freezing dbus
server taking down everything. Can you have a look at top w
This will make it difficult. Ksmserver has to render the screen black
and it looks like it doesn't have access to all X servers.
I'm afraid that this might be a problem which we won't fix any time
soon. It will require quite some reworking on assumptions in the lock
screen interaction.
--
You re
I started working on drag'n'drop support for Wayland and also looked at
a solution for this problem.
This morning I discussed ideas with our usability team and we will also
do some iterative in person tests next week during our development
sprint.
So far we concluded that the best approach is to
Git commit 8a1f19b1450fc244977ad6e7dff48d4fb6c28a13 by Martin Gräßlin.
Committed on 02/03/2016 at 07:34.
Pushed by graesslin into branch 'master'.
Add support for Drag'n'Drop on Wayland
Drag'n'Drop on Wayland allows us to improve the drag'n'drop experience.
When entering a window during the drag'
(In reply to Syam from comment #46)
> The problem is that this raise happens not on 'click' but on mouse-down
> itself.
This is correct, the raise happens on press if that's the action you
configured for what happens on click on inactive window. This is
configurable. If you don't like the default
> I'm not sure if that'd suffice. Consider the situation:
We considered this situation during our discussions and came to the
conclusion that it's out of scope. The drag is performed from the active
window, for the compositor it's impossible to know that the user clicked
the window to perform a dr
In a multi-head setup do you have two ksmserver instances?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1264821
Title:
kscreenlock_greet insecure with multiple X screens
To manage notifications ab
given that the window is marked as demands attention I consider this as
the expected behavior.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kde-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/1369424
Title:
LibreOffice windows and
given comment #20 I assume this issue to be fixed. If it still happens,
please reopen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/184682
Title:
kscreensaver immediately reengages when attempting
*** This bug has been marked as a duplicate of bug 314073 ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1264821
Title:
kscreenlock_greet insecure with multiple X screens
To manage notifications
adding some more information: breeze hides the button.
--
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 ab
still applies for Aurorae as of 5.2. I'm not sure yet whether I want to
fix it.
--
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
T
all right, given that I am going to try to fix Aurorae.
> Where should we document this?
in the API documentation of KDecoration?
--
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
(In reply to Thomas Lübking from comment #10)
> 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.)
I'd say two groups of behavior:
* might change during life tim
> xfwm4 is so far the only window manager I've come across that supports
mwm hints, but not this combination.
Just for the record: KWin doesn't support this combination, either (see
https://bugzilla.gnome.org/show_bug.cgi?id=729769) and our investigation
showed that there are lots more window mana
I started to work on tackling this problem. KWin part is prepared:
https://git.reviewboard.kde.org/r/115288/
At the moment I'm targeting the KWin 5 only. Depending on when we get
the support into KSnapshot I will be tempted to backport to 4.11. It's
not largely invasive and only conflicts in atoms
Git commit 41c77675e6bb0bbb4b50c121f8c81799fa2e411b by Martin Gräßlin.
Committed on 24/01/2014 at 11:34.
Pushed by graesslin into branch 'KDE/4.11'.
Allow windows to specify that they should not get animated on window
close
By setting the X property _KDE_NET_WM_SKIP_CLOSE_ANIMATION to 1 a window
Git commit 2d7d4545b4c7961970a28aabfc0d61cdb6af6c5f by Martin Gräßlin.
Committed on 28/01/2014 at 08:04.
Pushed by graesslin into branch 'KDE/4.12'.
Set window property to not animate KSnapshot's window on close
Starting with KWin 4.11.6 [1] there is a hint to exclude a window from
the closing an
Change for KSnapshot prepared: https://git.reviewboard.kde.org/r/115350/
If timing works fine we will have this fixed in the combined release of
4.11.6 and 4.12.2 on February 4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
*** Bug 338714 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 notif
(In reply to S from comment #44)
> Created attachment 89230 [details]
> ksnapshot (0.8.2, KDE 4.14.1) captures itself, including the save dialog
but that's a different instance, isn't it?
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to ksnap
*** Bug 306254 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
*** Bug 304464 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
*** Bug 305002 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
*** Bug 317594 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
I think following Weston's approach is probably the best one as I assume that
Kristian knows what is best with Mesa's drivers.
We should know the actual damage area after the effects have modified it, once
it goes back into the scene. So it should be possible to keep a queue of the
last frames
(In reply to comment #67)
> > Btw. we have quite some time to get it right as I think that's already too
> > late for 4.10 (we are past soft feature freeze).
> So you think this is a feature?
It's not really a feature, neither really a bug fix. It changes the way how we
render and it could introd
> Ubuntu changelog does not mention any patches related to KWin, though.
that's not surprising as the KDE SC 4.9.3 changelog doesn't mention this
change either. The Kubuntu developers are probably not aware of it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
> Don't see any kwin changes
> http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/kde-workspa
> ce/changes
Rev 699: New upstream release (LP: #1074747)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
as a matter of fact KWallet is not very secure in the first place. With a
password it is secure as long as you have not opened the wallet. Once the
wallet is open it is unsecure in the following (obvious) ways:
* all information on how to read the passwords has to be in memory. Reading
the memor
This problem cannot be fixed until we have done the transition to
Wayland.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/435347
Title:
KDE panel blocking mouse
To manage notifications about this bu
> > No, false positives is what you'll get on your approach - proof: the cause
> > for this discussion.
>
> Yes, I'll get some false positives. Theoretically. But in practice:
> - What's the problem with unredirected fullscreen unmanaged window? It could
> cause flicker once, nothing more.
KWin us
45 matches
Mail list logo
