[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2021-02-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=341497

Nate Graham  changed:

   What|Removed |Added

 CC||awil...@adelielinux.org

--- Comment #82 from Nate Graham  ---
*** Bug 362964 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2021-02-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=341497

Nate Graham  changed:

   What|Removed |Added

 CC||hzwhu...@gmail.com

--- Comment #85 from Nate Graham  ---
*** Bug 347524 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2021-02-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=341497

Nate Graham  changed:

   What|Removed |Added

 CC||iskender...@gmail.com
 CC||sc...@alfter.us

--- Comment #83 from Nate Graham  ---
*** Bug 369221 has been marked as a duplicate of this bug. ***

--- Comment #84 from Nate Graham  ---
*** Bug 366070 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2021-02-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=341497

Nate Graham  changed:

   What|Removed |Added

 CC||awil...@adelielinux.org
 CC||iskender...@gmail.com

--- Comment #82 from Nate Graham  ---
*** Bug 362964 has been marked as a duplicate of this bug. ***

--- Comment #83 from Nate Graham  ---
*** Bug 369221 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2021-02-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=341497

--- Comment #81 from Nate Graham  ---
*** Bug 345129 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2021-02-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=341497

Nate Graham  changed:

   What|Removed |Added

 CC||l.jirkov...@gmail.com

--- Comment #79 from Nate Graham  ---
*** Bug 344773 has been marked as a duplicate of this bug. ***

--- Comment #80 from Nate Graham  ---
*** Bug 343982 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2021-02-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=341497

--- Comment #78 from Nate Graham  ---
*** Bug 345205 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2021-02-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=341497

--- Comment #78 from Nate Graham  ---
*** Bug 345205 has been marked as a duplicate of this bug. ***

--- Comment #79 from Nate Graham  ---
*** Bug 344773 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2021-02-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=341497

Nate Graham  changed:

   What|Removed |Added

 CC||harishnav...@gmail.com

--- Comment #77 from Nate Graham  ---
*** Bug 343772 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2021-02-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=341497

Nate Graham  changed:

   What|Removed |Added

 CC||kdeb...@papradno.eu

--- Comment #76 from Nate Graham  ---
*** Bug 360254 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2021-02-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=341497

Nate Graham  changed:

   What|Removed |Added

 CC||simhpl+kde121...@gmail.com

--- Comment #75 from Nate Graham  ---
*** Bug 355232 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2021-02-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=341497

Nate Graham  changed:

   What|Removed |Added

 CC||arpi...@gmail.com
 CC||ferr...@live.cn

--- Comment #73 from Nate Graham  ---
*** Bug 380941 has been marked as a duplicate of this bug. ***

--- Comment #74 from Nate Graham  ---
*** Bug 359228 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2021-02-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=341497

Nate Graham  changed:

   What|Removed |Added

 CC||arpi...@gmail.com

--- Comment #73 from Nate Graham  ---
*** Bug 380941 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2021-02-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=341497

--- Comment #72 from Nate Graham  ---
*** Bug 339922 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2021-02-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=341497

Nate Graham  changed:

   What|Removed |Added

 CC||bastian.salm...@gmail.com

--- Comment #71 from Nate Graham  ---
*** Bug 346700 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2021-02-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=341497

Nate Graham  changed:

   What|Removed |Added

 CC||hallerharr...@gmail.com

--- Comment #70 from Nate Graham  ---
*** Bug 351180 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2021-02-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=341497

Nate Graham  changed:

   What|Removed |Added

 CC||con.henne...@gmail.com

--- Comment #69 from Nate Graham  ---
*** Bug 358560 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2021-02-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=341497

Nate Graham  changed:

   What|Removed |Added

 CC||k...@nidu.eu

--- Comment #68 from Nate Graham  ---
*** Bug 348262 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2021-02-08 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=341497

--- Comment #67 from Nate Graham  ---
*** Bug 360134 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2016-07-20 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341497

--- Comment #66 from Thomas Lübking  ---
*** Bug 365913 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2016-06-28 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341497

Thomas Lübking  changed:

   What|Removed |Added

 CC||ra...@pisem.net

--- Comment #65 from Thomas Lübking  ---
*** Bug 364867 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2016-06-16 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341497

Thomas Lübking  changed:

   What|Removed |Added

 CC||martin+...@serafean.cz

--- Comment #64 from Thomas Lübking  ---
*** Bug 364388 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2016-06-15 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341497

Thomas Lübking  changed:

   What|Removed |Added

 CC||pml...@gmail.com

--- Comment #63 from Thomas Lübking  ---
*** Bug 364362 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2016-06-12 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341497

Thomas Lübking  changed:

   What|Removed |Added

 CC||vivo75+...@gmail.com

--- Comment #62 from Thomas Lübking  ---
*** Bug 364242 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2016-05-05 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341497

--- Comment #60 from Thomas Lübking  ---
This is not a bug in KDE (let alone KWin)

The bug exists in every Qt 5.5 version. Older Qt versions have randr related
sefaults in QtQuick (will affect plasmashell, kwin and everything else that has
QML bits) and so does at least Qt 5.6.0 (unstashed by the restorage of the pre
5.5 behavior to prevent these crashes)

Ubuntu could likely "backport" this in Qt - while the resolving commit is a bit
bigger, the breaking one is just (afaics pretty much unmotivated other than the
broken anyway QtQuick part) 
http://code.qt.io/cgit/qt/qtbase.git/commit/src/plugins/platforms/xcb/qxcbconnection.cpp?id=51ada7734ad780178ecced11e0dff454dfc2e5f2

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2016-05-05 Thread Michael Butash via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341497

Michael Butash  changed:

   What|Removed |Added

 CC||mich...@butash.net

--- Comment #59 from Michael Butash  ---
Is a backport possible for 16.04 ubuntu users not likely to see this in lts
until 18.04?

Sadly, kde4 was terrible with unfixed bugs for setting up xrandr geometry as
well that made it unusable when relying on radeon modules, upgraded to 5 (and
16.04 to do so), was massively better, but affected by this now as well it
seems.  Going back to 4 really isn't an option being left unresolved too.

I'm using 3x displays, 48" 4k samsung tv's as my desk monitors, which don't do
dpms keepalive over hdmi cables it seems.  Rather they shut off/down, and "go
away" on the wire to the video card and xrandr, leaving it without a native
display, or your "dummy display" concept it seem to keep it sane when it has
none.  Waking up the displays, and thus xrand + kde figuring out where to put
things back to, is an entire crapshoot now whether it 1) lives perfect, 2)
lives broken needing xrandr fixing, 3) needs sddm restart from different tty,
or 4) needs rebooted as nothing wakes it up.  Feels windoze-y now.

Oddly, it doesn't always crash kwin, and sometimes recovers perfectly.  Other
times not so much, but its very random sadly.  

I've created xrandr scripts myself and with arandr to deal with it when kde5 as
a whole decides to go weird, but it's also seeming to have identity issues with
what is the "primary" display as well, as it seems to change upon these events
which is really primary, or which primary is really linked to which monitor
index.  Sometimes I just have to try setting the primary monitor randomly to
figure out which it thinks is currently actually display 2 for example.

SDDM also has recovery issues with are likely to be related but their own
beast, yet systemic of the fact no one seems to actually test kde with multiple
monitors extensively.  I was using kde4 happily with amd blob drivers and 6x
1080p montiors that did the setup itself for years, but using radeon now (with
4.x kernels that amd doesn't support yet for blob), which now works 2000x
better, breaks this with xrandr quirks like this.

-- 
You are receiving this mail because:
You are watching all bug changes.


[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2016-04-27 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341497

Thomas Lübking  changed:

   What|Removed |Added

 CC||lu...@dolezel.info

--- Comment #58 from Thomas Lübking  ---
*** Bug 362350 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2016-04-13 Thread Martin Steigerwald via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341497

--- Comment #57 from Martin Steigerwald  ---
Just to make it clear here, the QT-BUG –
https://bugreports.qt.io/browse/QTBUG-42985 – also refers to disappearing
windows, not just crashes. From reading from the QTBUG I bet the issue is fixed
in Qt 5.5.1 with patches and hopefully in 5.6.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2016-04-13 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341497

Thomas Lübking  changed:

   What|Removed |Added

 CC||mar...@lichtvoll.de

--- Comment #56 from Thomas Lübking  ---
*** Bug 361704 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2016-03-19 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341497

le.t...@gmail.com changed:

   What|Removed |Added

 CC||le.t...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.


[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2016-03-18 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341497

Thomas Lübking  changed:

   What|Removed |Added

 CC||grgo...@yahoo.com

--- Comment #55 from Thomas Lübking  ---
*** Bug 360684 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2016-03-15 Thread Pavel Hering via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341497

Pavel Hering  changed:

   What|Removed |Added

 CC|pavher...@gmail.com |

-- 
You are receiving this mail because:
You are watching all bug changes.


[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2016-03-15 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341497

Thomas Lübking  changed:

   What|Removed |Added

 CC||l.bonn...@laposte.net

--- Comment #54 from Thomas Lübking  ---
*** Bug 360548 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2016-03-09 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341497

Thomas Lübking  changed:

   What|Removed |Added

 CC||d.d.huis...@gmail.com

--- Comment #53 from Thomas Lübking  ---
*** Bug 360337 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2016-03-04 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341497

Thomas Lübking  changed:

   What|Removed |Added

 CC||mi...@voinescu.ro

--- Comment #52 from Thomas Lübking  ---
*** Bug 360079 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2016-02-25 Thread Roman Prots' via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341497

Roman Prots'  changed:

   What|Removed |Added

 CC||rpr...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.


[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2016-01-27 Thread Pasi via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341497

Pasi  changed:

   What|Removed |Added

 CC||kde.track.pasi...@xoxy.net

-- 
You are receiving this mail because:
You are watching all bug changes.


[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2016-01-26 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341497

Thomas Lübking  changed:

   What|Removed |Added

 CC||gwpub...@wp.pl

--- Comment #51 from Thomas Lübking  ---
*** Bug 358605 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2015-12-14 Thread David Edmundson via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341497

David Edmundson  changed:

   What|Removed |Added

 CC||gtwilli...@gmail.com

--- Comment #49 from David Edmundson  ---
*** Bug 353578 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.


[kwin] [Bug 341497] Segfault in Qt since the (at least) the xcb screen backend cannot deal with "no screen" conditions

2015-11-30 Thread Thomas Lübking via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=341497

Thomas Lübking  changed:

   What|Removed |Added

 CC||jbar...@gmail.com

--- Comment #47 from Thomas Lübking  ---
*** Bug 356107 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.