Summary: | Focus changes unexpectedly | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | FiNeX <finex> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 4.10.2 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
FiNeX
2013-04-27 12:42:19 UTC
pot. related to FF or TB? see bug #318350 Well... I'm not using TB, but I use FF a lot. Apparently it doesn't looks that FF is opening notifications but I will be careful about this on the next days. Meanwhile would you like to leave this report open? Thanks :) It stresses a pattern. Likely a dupe, but first data, then decision :-) I confirm that when FF opens the notification popup on each download the notification popup panel gets the focus. P.S: I'm using a dual monitor setup with nvidia-twinview. That should really not happen. Can you obtain xwininfo and xprop of the notification (that gets the focus)? *** This bug has been marked as a duplicate of bug 318350 *** @Thomas: how? Should I keep a terminal opened with xwinfo running and click the notification when it will be focused? Meanwhile I've found another case: 1) start kate 2) open a remote file (via sftp for example) 3) save the file and switch to another window before the saving process has ended When the file will be saved the notification window will be focused :-( Should I add the two cases I've identified (firefox notification and save to a remote location) to bug #318350 ? Thanks again :-) (In reply to comment #6) > @Thomas: how? Should I keep a terminal opened with xwinfo running and click > the notification when it will be focused? Basically, yes - i tend to sleep 30; xwininfo as that gets me 30 seconds to trigger the issue > Meanwhile I've found another case: So it does /not/ happen for you on a "wall" notification either? > Should I add the two cases I've identified (firefox notification and save to > a remote location) to bug #318350 ? We should stop talking on the dupe and channel all communication through 318350 ;-) |