https://bugs.kde.org/show_bug.cgi?id=360058
Bug Janitor Service changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #39 from Bug Janitor Service ---
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
https://bugs.kde.org/show_bug.cgi?id=360058
Nate Graham changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=360058
bjoe...@arcor.de changed:
What|Removed |Added
CC||bjoe...@arcor.de
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=360058
Postix changed:
What|Removed |Added
CC||pos...@posteo.eu
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=360058
bugreporte...@gmail.com changed:
What|Removed |Added
CC||bugreporte...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #36 from Simone Gaiarin ---
In KScreen 5.11.5 (maybe also in previous versions) the situation is slightly
improved for me. If I wakeup the notebook before docking it, once I dock it the
correct configuration is applied.
https://bugs.kde.org/show_bug.cgi?id=360058
LJoco changed:
What|Removed |Added
CC||j.lori...@chello.hu
--- Comment
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #34 from Sergio ---
I work uniquely in X because single window network operation with xpra is
essential in our setup.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #33 from Simone Gaiarin ---
Do you see the improvements on X or wayland?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #32 from Sergio ---
No, unfortunately it was just a couple of lucky cases. Still I have situations
in which I attach an external monitor and kscreen thinks it is the same monitor
that was attached in some
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #31 from Sergio ---
Seems OK or at least very much improved now!!! I'll do some more checking and
report. In the meanwhile, thanks for having worked on this.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #30 from Sergio ---
As I have no experience at all with Wayland (either on the reference composer
or on kwin), I'd like to take the occasion to ask a few questions on it.
I have read that some forms of network
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #29 from Simone Gaiarin ---
I have tried to switch to wayland multiple times for this exact reason but I
always found it unusable.
The last time I've tried it with plasma 5.11 was fairly decent but there is
still bug
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #28 from Martin Flöser ---
I just want to add that with Plasma 5.12 in a Wayland session this will all
work 100 % correct. So if this is an issue to you, I highly suggest to switch
to Wayland starting with 5.12. Even in
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #27 from Simone Gaiarin ---
Dear Sebastian,
I think no one here wants to blame you of anything. I know that the resources
in terms of people and time are limited and some bugs may be particularly nasty
to solve or have
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #26 from Sergio ---
Hi,
thanks for your suggestion.
As a matter of fact, what I would like to do is being able to configure the
screen graphically, having the system making only the safe choice of
re-enabling
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #25 from Sebastian Kügler ---
You can disable the kscreen background service and it won't do any automatic
configuration or reconfiguration, then you can use xrandr by hand.
I may also note that, while in your situation,
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #24 from Sergio ---
At this point, almost two years after the original report and many proud
articles such as https://lwn.net/Articles/694157/ all the issues are still
there.
If you have a laptop, and you attach
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #23 from Sergio ---
Bug still present as of
framework 5.37
QT 5.7.1
plasma 5.10.5
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #22 from Sergio ---
Issue is still present on kubuntu 17.04 with the KDE PPA, that is
Framework 5.35.0
QT 5.7.1
Plasma 5.10.2
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #21 from Simone Gaiarin ---
Is it there any progress on this bug?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #20 from Simone Gaiarin ---
Ok. So I tried again today and I can find the process
/usr/lib/kf5/kscreen_backend_launcher, so yesterday probably it crashed.
Case 1:
In any case now I've tried this:
- Undock from work
-
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #19 from Sebastian Kügler ---
If you're running on X11 and you don't have that process, that will cause the
issue.
Can you check if it crashes, or is perhaps not or wrongly installed? It could
be an integration issue.
--
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #18 from Simone Gaiarin ---
This bug got worse since a month or two, because now it happens even with the
following sequence of operations (that was working fine before):
At home -> detach monitor -> suspend -> go to
https://bugs.kde.org/show_bug.cgi?id=360058
Erik Quaeghebeur changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #17 from Simone Gaiarin ---
I confirm the behaviour described in comment 15. I'm experiencing exactly the
same.
Sergio explained it in a much more clear way than me.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=360058
Sebastian Kügler changed:
What|Removed |Added
Ever confirmed|0 |1
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #15 from Sergio ---
What I see does in fact seem consistent with your last comment.
As soon as I am in a place where I have external screens to swap, I'll collect
the logs and send them to you.
My feeling is
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #14 from Sebastian Kügler ---
Bit confused now, but could you get me the kscreen.log after a startup when
things went wrong? (And tell me what it should have been.)
The config files in ~/.local/share/kscreen/* would also be
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #13 from Sergio ---
@Simone
> can you please verify if you have a similar situation, where two screens in
> different location are named the same way?
This is obscure to me. They have obviously the same "name"
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #12 from Simone Gaiarin ---
I've noticed that the two problematic monitors have the same identifiers also
in .config/monitors.xml. So this bug seems generated by X bad naming. Also it
seems that X remembers all the
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #11 from Simone Gaiarin ---
I need to make a correction (still the considerations in comment #6 are still
valid):
Attachment 101767 is my correct HOME configuration:
DP1: Notebook screen
DP1-2: Dell U2414H
Attachment
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #10 from Simone Gaiarin ---
Created attachment 101769
--> https://bugs.kde.org/attachment.cgi?id=101769=edit
Kscreen configuration WORK (Correct version)
This is the correct version of my WORK configuration:
eDP1:
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #9 from Simone Gaiarin ---
The kscreen.log in comment #4 is probably irrelevant, refer to the info in
comment #6 which refer to a more accurate test.
@Sergio Can you please verify if you have a similar situation, where
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #8 from Simone Gaiarin ---
Created attachment 101768
--> https://bugs.kde.org/attachment.cgi?id=101768=edit
Kscreen configuration WORK
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #7 from Simone Gaiarin ---
Created attachment 101767
--> https://bugs.kde.org/attachment.cgi?id=101767=edit
Kscreen configuration HOME
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #6 from Simone Gaiarin ---
Here is a clue on what may be the cause of the problem: it seems that one
monitor at home is named as one monitor at work, so when I wake from suspend,
kscreen doesn't notice the difference.
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #5 from Sergio ---
So the bug has got to 5.8.1. Sad to hear that, being on in ubuntuland that
shall probably get to 5.8.1 in another 6 months. Looks like no one with kde
uses laptops that dock to external
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #4 from Simone Gaiarin ---
Created attachment 101732
--> https://bugs.kde.org/attachment.cgi?id=101732=edit
kscreen.log after resuming notebook in a different location
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=360058
Simone Gaiarin changed:
What|Removed |Added
CC||simg...@gmail.com
---
https://bugs.kde.org/show_bug.cgi?id=360058
Martin Gräßlin changed:
What|Removed |Added
Severity|crash |normal
https://bugs.kde.org/show_bug.cgi?id=360058
--- Comment #1 from Sergio ---
Note that whenever the system remains "usable enough" at 6) to perform some
action, a workaround for the issue is to switch to a text console and to issue
a
killall kscreen_backend_launcher
43 matches
Mail list logo