| Summary: | In dual screen mode Firefox looses the kwin surrounding | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | m.wege |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | Keywords: | investigated, triaged |
| Priority: | NOR | ||
| Version First Reported In: | 4.7.1 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
m.wege
2011-10-11 09:50:55 UTC
I fail to reproduce Is there any way to produce debug info for this? I do not have an exact way of describing in order to reproduce, but it happens so often, so there should be a way. We need very precise orders on how to reproduce the issue. Like 1. Do Foo 2. Then do bar 3. Do baz 4. ... There needs to be an order on the steps you do each time to trigger the bug. Please also consider whether this is a Firefox bug. E.g. try a different version, I just tested with Iceweasel 7 @m.wege (1) attempt to set the kbd focus to the issued FF window -> works? (2) press "alt + f3", a popup should appear -> works? === if 1 or 2 fails, go on with "kwin crashed" === (3) select the advanced submenu and check the "no border" entry -> is it checked? (4) in that advanced submenu -> is there a shortcut assigned to "fullscreen" and is it F11? (in addition to the FF shortcut) (5) is it related to desktop effects? (6) Two FF windows, but one process or two? (7) Try whether it's related to the multiscreen setup, eg. try on one screen === KWIN CRASHED ========== there should be some dialog where you can click "developer info" (or similar) to gather a backtrace but since it's an intel chip and fullscreen related, it's most likely this bug #252817 - disable compositing suspension for fullscreen windows in that case we still need the introductions to reproduce Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |