https://bugs.kde.org/show_bug.cgi?id=377808
Marco Martin changed:
What|Removed |Added
CC||ddash.r...@gmail.com
--- Comment #17 from Marco
https://bugs.kde.org/show_bug.cgi?id=377808
Marco Martin changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/pla
|
https://bugs.kde.org/show_bug.cgi?id=377808
--- Comment #15 from Marco Martin ---
possible fix: https://phabricator.kde.org/D5323
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=377808
--- Comment #14 from Marco Martin ---
one more thing that has been discovered: it appears this also depends from the
primary screen (that is getting removed or added) to be at 0,0 position and the
other screen being at the right of it.
this makes the n
https://bugs.kde.org/show_bug.cgi?id=377808
--- Comment #13 from Marco Martin ---
the theory i can make is that a new primary screen arrives, but has a wrong
geometry for a while, making the old screen "redundant", then it gets
moved/resized (maybe even without emitting signals) so things get ver
https://bugs.kde.org/show_bug.cgi?id=377808
--- Comment #12 from Kai Uwe Broulik ---
Qt 5.7.1 for me
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=377808
--- Comment #11 from Marco Martin ---
also: what's the Qt version? some of this problems may depend on it (and why i
can't reproduce any)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=377808
--- Comment #10 from Marco Martin ---
(In reply to Kai Uwe Broulik from comment #8)
>
> It calls reconsiderOutputs() which might remove and delete a view (at one
> point we only have one in the above scenario), so m_desktopViewforId is now
> empty, aft
https://bugs.kde.org/show_bug.cgi?id=377808
--- Comment #9 from Marco Martin ---
(In reply to Roman Gilg from comment #4)
> Details worth mentioning:
>
> This only happens when the 2nd screen was already connected in SDDM. After
> login it shows the panel on the 2nd screen (it also doesn't remem
https://bugs.kde.org/show_bug.cgi?id=377808
Kai Uwe Broulik changed:
What|Removed |Added
Assignee|plasma-b...@kde.org |aleix...@kde.org
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=377808
Kai Uwe Broulik changed:
What|Removed |Added
CC||agrar.pfu...@gmail.com
--- Comment #7 from Ka
https://bugs.kde.org/show_bug.cgi?id=377808
--- Comment #6 from Roman Gilg ---
Yes, but the external monitor only is the primary screen, if I login from sddm
with the monitor already being connected in sddm. I also can't change the
primary screen in session with the KCM (but I assume that's unrel
https://bugs.kde.org/show_bug.cgi?id=377808
Marco Martin changed:
What|Removed |Added
CC||notm...@gmail.com
--- Comment #5 from Marco Mart
https://bugs.kde.org/show_bug.cgi?id=377808
--- Comment #4 from Roman Gilg ---
Details worth mentioning:
This only happens when the 2nd screen was already connected in SDDM. After
login it shows the panel on the 2nd screen (it also doesn't remember the
position from last time) and then disconnec
https://bugs.kde.org/show_bug.cgi?id=377808
Roman Gilg changed:
What|Removed |Added
Status|NEEDSINFO |UNCONFIRMED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=377808
Kai Uwe Broulik changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=377808
--- Comment #1 from Roman Gilg ---
--
Backtrace:
--
Thread 1 (Thread 0x7f919e6388c0 (LWP 16430)):
[KCrash Handler]
#6 0x7f9198bf5428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7 0x7f9198bf702a in
17 matches
Mail list logo