https://bugs.kde.org/show_bug.cgi?id=368910
--- Comment #13 from linuxfluesterer ---
@Sebastian As I said, I'm using Sabayon binary distro, based on Gentoo. The
Plasma environment is not upgraded to version 5.8 yet. But I assume due to the
intention to ship 'stable' versions of packages, it will
https://bugs.kde.org/show_bug.cgi?id=368910
--- Comment #12 from Sebastian Kügler ---
@Matthias no harm done, thanks for digging into the problem. I'm glad you found
the issue. :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=368910
--- Comment #11 from Sebastian Kügler ---
@-Linuxfluesterer Like Matthias said, your bug is an unrelated problem,
fortunately, one which we have fixed already. Your Plasma version is a bit
outdated, so it doesn't contain the fix yet. It would be great i
https://bugs.kde.org/show_bug.cgi?id=368910
--- Comment #10 from linuxfluesterer ---
(In reply to Matthias Blaicher from comment #7)
> Hi linuxfluesterer,
>
> I am sorry, but this is a totally unrelated bug, as you acknowledge:
>
> Neither is it docking related, nor does it have problems enabl
https://bugs.kde.org/show_bug.cgi?id=368910
Matthias Blaicher changed:
What|Removed |Added
Resolution|--- |INVALID
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=368910
--- Comment #8 from Matthias Blaicher ---
(In reply to Sebastian Kügler from comment #4)
> For kicks, could you check if this works in GNOME or Unity (maybe they've
> found such a workaround)?
I just checked - GNOME also does not work So I guess th
https://bugs.kde.org/show_bug.cgi?id=368910
--- Comment #7 from Matthias Blaicher ---
Hi linuxfluesterer,
I am sorry, but this is a totally unrelated bug, as you acknowledge:
Neither is it docking related, nor does it have problems enabling your monitor
(looks like a plasmashell crashes to me)
https://bugs.kde.org/show_bug.cgi?id=368910
--- Comment #6 from linuxfluesterer ---
I can confirm inability with correct recognising a direct connected monitor to
my laptop, no matter on vga or HDMI. I can connect such a monitor, but after
connecting I still can move the mouse pointer, but I can
https://bugs.kde.org/show_bug.cgi?id=368910
linuxfluesterer changed:
What|Removed |Added
CC||linuxflueste...@gmx.net
--- Comment #5 from l
https://bugs.kde.org/show_bug.cgi?id=368910
--- Comment #4 from Sebastian Kügler ---
Yeah, it seems to be down to a problem somewhere in the stack. I'm testing
docking station (with a Lenovo X1 Yoga and a OneLine+) almost daily, and that
works flawlessly now -- but there, we do actually get chang
https://bugs.kde.org/show_bug.cgi?id=368910
--- Comment #3 from Matthias Blaicher ---
Hi Sebastian,
thank you for your work and looking into it. As this used to work for KDE4, I
suppose it is not an hardware issue, but the whole software stack and kernel
changed since then...
Regarding xrandr, t
https://bugs.kde.org/show_bug.cgi?id=368910
Sebastian Kügler changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=368910
Sebastian Kügler changed:
What|Removed |Added
Keywords||multiscreen
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=368910
--- Comment #1 from Matthias Blaicher ---
Created attachment 101128
--> https://bugs.kde.org/attachment.cgi?id=101128&action=edit
Annotated kscreen log
Annotated kscreen log with relevant input from journald of the folliowing
sequence:
1. Boot into
14 matches
Mail list logo
