[KScreen] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 --- Comment #27 from Sebastian Kügler --- I'm trying to reproduce by running a neon session in a virt-manager, using qemu. I've the driver QXL, and I've installed qemu-ga inside the vm, but it can't find a channel, so it doesn't work. The error is: critical: error opening channel: Device or resource busy critical: error opening channel critical: failed to create guest agent channel critical: failed to initialize guest agent channel (The resize "vm with window" checkbox is greyed out, complains about missing guest agent) I'm a bit lost here, anyone who can help? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off
https://bugs.kde.org/show_bug.cgi?id=359542 Sebastian Kügler changed: What|Removed |Added Resolution|WAITINGFORINFO |INVALID Status|NEEDSINFO |RESOLVED --- Comment #29 from Sebastian Kügler --- @Olaf > At this point I decided you will probably not even read all the things I wrote > down until now and stopped playing around. I hope this is somehow useful for > debugging. I will attach the kscreen.log file and screen photos soon. That's unfortunately correct. You have by now put so much information into this bugreport that it's a pain and very inefficient to sift through. I have to filter out the relevant bits from your huge swathes of text, and often, I need to read a bugreport multiple times. You can imagine what a huge waste of time it becomes then. I wonder, if you know it's not useful, why you put so much (unrelated) info in it. So, for your understanding: - I'm interested in problems with resolution, position and enablement of outputs, these problems fall under kscreen - if you have problems with applications, file a bug against the app, leave the info out here - if you've problems with the plasmashell (panels location, containment location, etc.), file a bug against plasmashell (there's a Multiscreen component) In order to keep my bug triaging life manageable, I'm closing this bugreport, asking you to file a new one, with *only* the relevant information. Thanks for your cooperation, it's really appreciated. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 Sebastian Kügler changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #26 from Sebastian Kügler --- This patch is not sufficient, I should have used CCBUG, not BUG in the commit. Sorry for the noise. (I'm working on it, though.) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 Sebastian Kügler changed: What|Removed |Added Latest Commit||http://commits.kde.org/libk ||screen/6cc05cae8143bf2a1f50 ||389f39cc7976ac7030b7 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #25 from Sebastian Kügler --- Git commit 6cc05cae8143bf2a1f50389f39cc7976ac7030b7 by Sebastian Kügler. Committed on 20/10/2016 at 22:07. Pushed by sebas into branch 'master'. allow changing an output's modelist at runtime This should fix running Plasma in a windowed virtual machine, when the window is resized, the mode list changes, and libksreen can't currently handle that. Summary: * make Output::modes() non CONSTANT, add modesChanged() signal * compare the mode lists and set the new one * queue an outputChanged signal when applied * autotest for modelist changes * update the mode list on RRNotify events Test Plan: * for library part, autotests are added * for xrandr backends, we can't sensibly autotest this :( Reviewers: #plasma, mart Reviewed By: mart Subscribers: graesslin, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D3117 M +1-0autotests/CMakeLists.txt A +179 -0autotests/testmodelistchange.cpp [License: LGPL (v2.1+)] M +9-1backends/xrandr/xrandroutput.cpp M +36 -1src/output.cpp M +9-1src/output.h http://commits.kde.org/libkscreen/6cc05cae8143bf2a1f50389f39cc7976ac7030b7 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 354663] "Display configuration" does not remember settings
https://bugs.kde.org/show_bug.cgi?id=354663 --- Comment #4 from Sebastian Kügler --- I don't understand, do you expect that a disabled output has a position? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 --- Comment #24 from Sebastian Kügler --- Great. I'm making some progress on the code side. It's a little involved, since the list of modes per output is static, so it's not actually supposed to change. That's expressed in libkscreen's API, and on top of that, modelist changes aren't handled throughout. Now I've done some work on falling back to the preferred mode if the current one is invalid, that's actually landed in 5.8.0, but the mode list is still static. We'll have to see if this can actually be merged into 5.8, or if the API change we need for this is too intrusive (I don't see a way around that). On my machine, I've made the necessary changes to make the mode list dynamic and notifyable. The problem is that I can't test this easily myself, as I'd need to have a build inside the VM to debug it properly. Bottom line, with the changes that I'll post for review shortly, this *could* actually work, but we may need other fixes here and there. Perhaps we can get these things in through Neon. *goes to finish and clean up that branch* -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 371207] Every login mangles by dual monitor config! Primary monitor unusable on login (black screen unable to right click on it until I disable/renable)
https://bugs.kde.org/show_bug.cgi?id=371207 --- Comment #5 from Sebastian Kügler --- It won't unless that kubuntu upgrades to Plasma 5.8. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371196] Panel consistently appears on wrong monitor after reboot since 5.8
https://bugs.kde.org/show_bug.cgi?id=371196 Sebastian Kügler changed: What|Removed |Added Keywords||multiscreen -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 371196] Panel consistently appears on wrong monitor after reboot since 5.8
https://bugs.kde.org/show_bug.cgi?id=371196 Sebastian Kügler changed: What|Removed |Added Target Milestone|1.0 |--- Keywords|multiscreen | Product|plasmashell |KScreen Assignee|aleix...@kde.org|notm...@gmail.com Component|Multi-screen support|kded -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371196] Panel consistently appears on wrong monitor after reboot since 5.8
https://bugs.kde.org/show_bug.cgi?id=371196 Sebastian Kügler changed: What|Removed |Added Target Milestone|--- |1.0 Product|KScreen |plasmashell Component|kded|Multi-screen support -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371196] Panel consistently appears on wrong monitor after reboot since 5.8
https://bugs.kde.org/show_bug.cgi?id=371196 Sebastian Kügler changed: What|Removed |Added CC||se...@kde.org Keywords||multiscreen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371196] Panel consistently appears on wrong monitor after reboot since 5.8
https://bugs.kde.org/show_bug.cgi?id=371196 Sebastian Kügler changed: What|Removed |Added Target Milestone|--- |1.0 CC||plasma-b...@kde.org Component|kded|Multi-screen support Product|KScreen |plasmashell Assignee|se...@kde.org |aleix...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 371207] Every login mangles by dual monitor config! Primary monitor unusable on login (black screen unable to right click on it until I disable/renable)
https://bugs.kde.org/show_bug.cgi?id=371207 Sebastian Kügler changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Sebastian Kügler --- This bug has been fixed in Plasma 5.8, please upgrade. :) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 356864] Plasma cannot adapt to VM host window
https://bugs.kde.org/show_bug.cgi?id=356864 Sebastian Kügler changed: What|Removed |Added Component|kded|libkscreen Version|5.7.1 |git -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 370494] Automatic VM display resolution broken under KDE hosts
https://bugs.kde.org/show_bug.cgi?id=370494 --- Comment #16 from Sebastian Kügler --- Interesting. So it seems we do get an update event, but since we don't reparse the mode list, it stays static, and nothing actually changes. Thanks a lot for the info, I'll look into coming up with a fix. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 359542] Waking up notebook from sleep after undocking leaves display turned off
https://bugs.kde.org/show_bug.cgi?id=359542 Sebastian Kügler changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #21 from Sebastian Kügler --- Does this still happen with Plasma 5.8? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 370494] Automatic VM display resolution broken under KDE hosts
https://bugs.kde.org/show_bug.cgi?id=370494 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #8 from Sebastian Kügler --- Thanks! Could you also post the output of: * kscreen-console (should show the same mode info as xrandr -q, but does it really?) * and the remaining files in ~/.local/share/kscreen/ Also, if you look "tail -f ~/.local/share/kscreen/", are there any new events in kscreen.log when you resize the window? If you kill kscreen_backend_launcher (it will be automatically restarted when needed), does kscreen-console show the information matching with xrandr -q? I've looked into the hotplug flag that was added in GNOME to make this case work, but this is not available through XCB (I couldn't find it), but should work automatically -- that is we do monitor the relevant events for the output, this is done in libkscreen/backends/xcblistener.cpp xcb_randr_select_input(c, m_window, XCB_RANDR_NOTIFY_MASK_SCREEN_CHANGE | XCB_RANDR_NOTIFY_MASK_OUTPUT_CHANGE | XCB_RANDR_NOTIFY_MASK_CRTC_CHANGE | XCB_RANDR_NOTIFY_MASK_OUTPUT_PROPERTY ); -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 370494] Automatic VM display resolution broken under KDE hosts
https://bugs.kde.org/show_bug.cgi?id=370494 --- Comment #4 from Sebastian Kügler --- The thing is, I need to know if it works with 5.8, I won't spend time on it without knowing that it's still broken as I can't fix it twice. So if you ask me to prioritize this problem, that's useless unless I get the information I need to actually work on this. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #116 from Sebastian Kügler --- @Robin Please don't muddy up this bugreport with unrelated requests. It's already too long, and adding a discussion here will make it longer to read, which reduces the time available to work on a fix. If you have a separate problem, please report a separate bugs as to avoid this report to become useless and harder to handle. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 355006] Can't adjust the resolution via "kcmshell5 kscreen" without issuing "sudo" first
https://bugs.kde.org/show_bug.cgi?id=355006 --- Comment #6 from Sebastian Kügler --- You shouldn't be running it as root, though... -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 354842] Multi-monitor configuration not applied (sometimes)
https://bugs.kde.org/show_bug.cgi?id=354842 Sebastian Kügler changed: What|Removed |Added CC||se...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Sebastian Kügler --- We've fixed a whole bunch of issues that could lead to this behaviour. Could you re-test with Plasma 5.8, and if this problem persists, reopen this bugreport and attach ~/.local/share/kscreen/kscreen.log after reproducing the problem? Do make sure that nvidia's tool and kscreen don't get in each other's way (you can disable the kscreen service in the background services kcm, don't know about nvidia). -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 367744] systemsettings5
https://bugs.kde.org/show_bug.cgi?id=367744 Sebastian Kügler changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 354437] [regression/4] KScreen does not remember multiple monitor configuration
https://bugs.kde.org/show_bug.cgi?id=354437 Sebastian Kügler changed: What|Removed |Added CC||se...@kde.org Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #14 from Sebastian Kügler --- @Thiago: This may well be fixed with Plasma 5.8, could you check that? You're saying you only get a single configuration file, this may happen if the EDID information of both monitors is the same (which shouldn't happen, but, you know ... hardware vendors, especially Samsung...). The output of kscreen-console would be interesting (for all monitors). -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 354226] kcm_kscreen from plasma 5 is useless
https://bugs.kde.org/show_bug.cgi?id=354226 Sebastian Kügler changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED CC||se...@kde.org --- Comment #2 from Sebastian Kügler --- We've fixed a whole bunch of issues that could lead to this behaviour. Could you re-test with Plasma 5.8, and if this problem persists, reopen this bugreport and attach ~/.local/share/kscreen/kscreen.log after reproducing the problem? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 354514] KDE Display Settings Crash > Post AMD CCC Install -14.502.1040-x86.x86_64 - enabling cross-screen dragging
https://bugs.kde.org/show_bug.cgi?id=354514 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED CC||se...@kde.org --- Comment #1 from Sebastian Kügler --- This crash has most likely been fixed in Plasma 5. If you can still reproduce a crash like this, could you open a new bug-report with the new backtrace, and I'll have a look. Sorry this bug-report went silent for so long. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 353590] After changing screen orientation to 90 degrees it can't be changed to normal
https://bugs.kde.org/show_bug.cgi?id=353590 Sebastian Kügler changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO CC||se...@kde.org --- Comment #2 from Sebastian Kügler --- Sorry for the long turnaround time. Could you check if this works with Plasma 5.8? We've had a problem updating the screen size in this scenario, which leads to your bug. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 354662] "Display configuration" allows overlapping screens
https://bugs.kde.org/show_bug.cgi?id=354662 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID CC||se...@kde.org --- Comment #1 from Sebastian Kügler --- Yes, it's intended. There's a snapping algorithm in place which helps preventing that, but the UI should really allow it. Thanks for checking! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 355176] A button to reload display information from xrandr
https://bugs.kde.org/show_bug.cgi?id=355176 Sebastian Kügler changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED CC||se...@kde.org --- Comment #1 from Sebastian Kügler --- This was fixed in Plasma 5.8, libkscreen couldn't handle dynamically changing CRTCs well, now it can. Thanks for taking the time to report this bug! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 360700] Disable "Unify outputs" when there is only one display
https://bugs.kde.org/show_bug.cgi?id=360700 Sebastian Kügler changed: What|Removed |Added Latest Commit|http://commits.kde.org/kscr |http://commits.kde.org/kscr |een/e886c69e9a9bbd033f5a4d5 |een/6dcc9b19be52fdf5b4c8148 |dd12df0e4d7521b1f |124758f7392646719 --- Comment #5 from Sebastian Kügler --- Git commit 6dcc9b19be52fdf5b4c8148124758f7392646719 by Sebastian Kügler. Committed on 16/10/2016 at 22:16. Pushed by sebas into branch 'Plasma/5.8'. Disable unify button when only one output is connected FIXED-IN:5.8.2 M +1-0kcm/src/widget.cpp http://commits.kde.org/kscreen/6dcc9b19be52fdf5b4c8148124758f7392646719 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 360700] Disable "Unify outputs" when there is only one display
https://bugs.kde.org/show_bug.cgi?id=360700 Sebastian Kügler changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kscr ||een/e886c69e9a9bbd033f5a4d5 ||dd12df0e4d7521b1f Version Fixed In||5.8.2 Status|CONFIRMED |RESOLVED --- Comment #4 from Sebastian Kügler --- Git commit e886c69e9a9bbd033f5a4d5dd12df0e4d7521b1f by Sebastian Kügler. Committed on 16/10/2016 at 22:15. Pushed by sebas into branch 'master'. Disable unify button when only one output is connected FIXED-IN:5.8.2 M +1-0kcm/src/widget.cpp http://commits.kde.org/kscreen/e886c69e9a9bbd033f5a4d5dd12df0e4d7521b1f -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365864] Display layout preview renders off-window in Display Configuration using Wayland
https://bugs.kde.org/show_bug.cgi?id=365864 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #13 from Sebastian Kügler --- Closing this one as upstream, then. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 366227] System Settings under Display and Monitor does not scale viewport
https://bugs.kde.org/show_bug.cgi?id=366227 Sebastian Kügler changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #2 from Sebastian Kügler --- This doesn't have anything to do with the dpi. The viewport is supposed to resize the individual outputs so that it always fits. It seems to still run out of bounds here, though. I'll try to recreate your configuration, so it can be tested against. We're currently reworking the UI here, so I'll keep your configuration in mind when testing the changes. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 355006] Can't adjust the resolution via "kcmshell5 kscreen" without issuing "sudo" first
https://bugs.kde.org/show_bug.cgi?id=355006 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID CC||se...@kde.org --- Comment #4 from Sebastian Kügler --- Could you run kscreen-doctor --info and kscreen-doctor --outputs and paste the output in this bugreport? The kscreen backend can fail to load if you have the wrong plugin path set (QT_PLUGIN_PATH env var), if it's wrong, adjust it so that it finds your kscreen backend plugin. This is a local configuration problem, or may need to be fixed in the packaging. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 354663] "Display configuration" does not remember settings
https://bugs.kde.org/show_bug.cgi?id=354663 Sebastian Kügler changed: What|Removed |Added CC||se...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Sebastian Kügler --- We've fixed this with Plasma 5.8. Could you test this release and confirm it? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 370494] Automatic VM display resolution broken under KDE hosts
https://bugs.kde.org/show_bug.cgi?id=370494 --- Comment #2 from Sebastian Kügler --- This could be two things: (1) libkscreen failing to mode-set for some reason, we had a number of bugs that could lead to that and fixed them for 5.8. (2) https://bugs.kde.org/show_bug.cgi?id=356864 which means that xrandr changes the list of modes on the fly, which libkscreen doesn't handle gracefully enough (yet). In that case, killing kscreen_backend_launcher and kded5, then restarting kded5 should allow to set the correct mode (not an acceptable workaround, of course, just a quick test to confirm this hunch). To judge, we'd need * confirmation if this is fixed in Plasma 5.8, or not * xrandr -q, ~/.local/share/kscreen/kscreen.log, etc., as explained on https://community.kde.org/Solid/Projects/ScreenManagement#Debugging_Information -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 370410] Bug tracker says all that is needed to create an account is to enter and confirm an email address, which is false
https://bugs.kde.org/show_bug.cgi?id=370410 Sebastian Kügler changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED CC||se...@kde.org --- Comment #1 from Sebastian Kügler --- That is a normal thing for account handling and logging in, it could be improved, but I think we can expect some common sense here. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 354227] kcm_kscreen is too high
https://bugs.kde.org/show_bug.cgi?id=354227 Sebastian Kügler changed: What|Removed |Added CC||se...@kde.org Assignee|plasma-b...@kde.org |se...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] I cannot set my short date to YYYY-MM-DD, nor my time to HH:MM
https://bugs.kde.org/show_bug.cgi?id=340982 Sebastian Kügler changed: What|Removed |Added CC||se...@kde.org --- Comment #108 from Sebastian Kügler --- @Juha: Your behavior makes me stop reading here, and that's counter-productive to everyone involved. Also, your disrespectfulness has no business here, you're just destroying the base people work together on. Ask yourself this question: Do you really want to drive developers away from issues you and other people care about? Please strongly consider the Code of Conduct ( https://www.kde.org/code-of-conduct/ ) before posting again. If you don't, you simply do not have the right of speaking. "I just behave that way" is not an excuse. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 357936] Laptop-screen shows as enabled after login though lid is closed and external monitor connected.
https://bugs.kde.org/show_bug.cgi?id=357936 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Sebastian Kügler --- Thanks for the bug-report! We've fixed a number of issues in the most recent development cycle that would lead to the problem you're observing. Could you test Plasma 5.8 please and confirm that it's fixed (and, if not definitely report back)? I'll close this bug for now, as I'm pretty sure the problem is gone in 5.8. (I've tested this use-case myself, and confirm it's working now.) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 369384] Dual Monitor: only unified output
https://bugs.kde.org/show_bug.cgi?id=369384 --- Comment #7 from Sebastian Kügler --- I'm not overly happy with that portion of the ui either. We're currently in the process of polishing the design of that settings module, and I'll take your feedback into account. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 369422] Number in refresh rate dropdown is being rounded to one decimal digit, producing duplicate-looking entries
https://bugs.kde.org/show_bug.cgi?id=369422 Sebastian Kügler changed: What|Removed |Added Latest Commit|http://commits.kde.org/kscr |http://commits.kde.org/kscr |een/7c3839083d4d2d77b63d0c2 |een/7d8ec60c60477d68e91e9bc |cde4ad87994380e9a |68f334ff286cffc73 --- Comment #2 from Sebastian Kügler --- Git commit 7d8ec60c60477d68e91e9bc68f334ff286cffc73 by Sebastian Kügler. Committed on 27/09/2016 at 22:31. Pushed by sebas into branch 'Plasma/5.8'. Increase precision of refresh rate It's pretty common to have slightly different refresh rates, and since this is currently hidden in the advanced section, more precision is OK. FIXED-IN:5.8.0 M +1-1kcm/src/outputconfig.cpp http://commits.kde.org/kscreen/7d8ec60c60477d68e91e9bc68f334ff286cffc73 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 369422] Number in refresh rate dropdown is being rounded to one decimal digit, producing duplicate-looking entries
https://bugs.kde.org/show_bug.cgi?id=369422 Sebastian Kügler changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.8.0 Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kscr ||een/7c3839083d4d2d77b63d0c2 ||cde4ad87994380e9a --- Comment #1 from Sebastian Kügler --- Git commit 7c3839083d4d2d77b63d0c2cde4ad87994380e9a by Sebastian Kügler. Committed on 27/09/2016 at 22:28. Pushed by sebas into branch 'master'. Increase precision of refresh rate It's pretty common to have slightly different refresh rates, and since this is currently hidden in the advanced section, more precision is OK. FIXED-IN:5.8.0 M +1-1kcm/src/outputconfig.cpp http://commits.kde.org/kscreen/7c3839083d4d2d77b63d0c2cde4ad87994380e9a -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 369384] Dual Monitor: only unified output
https://bugs.kde.org/show_bug.cgi?id=369384 --- Comment #5 from Sebastian Kügler --- So, what happens if you drag the HDMI2 SyncMaster output aside in the top section? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 --- Comment #94 from Sebastian Kügler --- @Shrinidhi Rao Could you please file a new bug-report, and add the information as outlined on: https://community.kde.org/Solid/Projects/ScreenManagement#Debugging_Information -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 356551] Control Panel not showing when selecting 'external monitor only' in settings
https://bugs.kde.org/show_bug.cgi?id=356551 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Sebastian Kügler --- Thanks for the bug-report. I've fixed this issue for the 5.8 release. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 369384] Dual Monitor: only unified output
https://bugs.kde.org/show_bug.cgi?id=369384 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Sebastian Kügler --- Thanks for the bug-report! Just to be sure: when applying the config to span the desktop across both screens, you should drag the outputs in the preview accordingly. The unify button behaves a bit weird like that, I'm not perfectly happy with how the interaction works there, and we're currently revisiting this. That said, I am aware of positioning bugs that can lead to the problem you're facing. The good news is that they are fixed already, although only in the upcoming Plasma 5.8 release. Could you please test this release and report back? (I'll close this bug-report in the meantime, if the bug persists with 5.8, we can re-open it and look into it again.) -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 369404] New: drag and drop to chromium doesn't work
https://bugs.kde.org/show_bug.cgi?id=369404 Bug ID: 369404 Summary: drag and drop to chromium doesn't work Product: Spectacle Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: se...@kde.org Dragging the screenshot from spectacle into chromium doesn't work, chromium doesn't recognize the mimedata correctly. It's broken for me in at least wordpress's media editor and imgur's uploader. It works fine with firefox. Apparently, chromium struggles with the image attached to the mimedata in SpectacleCore.cpp When I comment the setImageData(...) call in SpectacleCore::doStartDragAndDrop() it works. I don't know which apps read the pixmap from the mimedata directly, so I dunno what this is going to break. I'm posting this bugreport for further discussion how to proceed. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 369244] Slow repainting when switched to portrait mode
https://bugs.kde.org/show_bug.cgi?id=369244 Sebastian Kügler changed: What|Removed |Added Assignee|se...@kde.org |kwin-bugs-n...@kde.org Product|KScreen |kwin Component|common |multihead Summary|External Monitor goes black |Slow repainting when |when switched to portrait |switched to portrait mode |mode| --- Comment #4 from Sebastian Kügler --- Thanks. I'm reassigning this to kwin, so Martin can have a look. It's not a kscreen problem since the output is set up correctly. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 369241] [Display key] kscreen should remember current config when cycling through others
https://bugs.kde.org/show_bug.cgi?id=369241 --- Comment #1 from Sebastian Kügler --- The current code doesn't do that at all, it's not a bug but intended behaviour. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 369241] [Display key] kscreen should remember current config when cycling through others
https://bugs.kde.org/show_bug.cgi?id=369241 Sebastian Kügler changed: What|Removed |Added Ever confirmed|0 |1 Severity|normal |wishlist Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 369244] External Monitor goes black when switched to portrait mode
https://bugs.kde.org/show_bug.cgi?id=369244 --- Comment #2 from Sebastian Kügler --- Thanks for the bug report, Tom. Can you drag open windows onto the "non-working" monitor? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369160] Kickoff's tab reordering feature hides tabs invariably
https://bugs.kde.org/show_bug.cgi?id=369160 --- Comment #1 from Sebastian Kügler --- Created attachment 101211 --> https://bugs.kde.org/attachment.cgi?id=101211&action=edit tabs missing in my kickoff -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369160] Kickoff's tab reordering feature hides tabs invariably
https://bugs.kde.org/show_bug.cgi?id=369160 Sebastian Kügler changed: What|Removed |Added Assignee|k...@davidedmundson.co.uk|jsala...@gmail.com Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369160] New: Kickoff's tab reordering feature hides tabs invariably
https://bugs.kde.org/show_bug.cgi?id=369160 Bug ID: 369160 Summary: Kickoff's tab reordering feature hides tabs invariably Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: se...@kde.org CC: plasma-b...@kde.org After opening, reordering tabs and *NOT* applying, I've lost all but the favorites tab in my Kickoff with no way to restore it (even after restarting plasmashell, they're still gone). Here's what I did: 1. opened kickoff's config dialog 2. dragged around tab buttons 3. dismissed dialog All tabs but the favorites one were gone at that point. When opening the config dialog, they're all shown as shown. There doesn't seem to be a way to restore it. This is a grave problem as the tab reordering feature allows the user to inadvertently break an essential component of the workspace. Reproducible: Didn't try -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369159] kickoff config dialog clips content
https://bugs.kde.org/show_bug.cgi?id=369159 --- Comment #1 from Sebastian Kügler --- Created attachment 101210 --> https://bugs.kde.org/attachment.cgi?id=101210&action=edit screenshot showing the wrong clipping in kickoff's config dialog -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 369159] New: kickoff config dialog clips content
https://bugs.kde.org/show_bug.cgi?id=369159 Bug ID: 369159 Summary: kickoff config dialog clips content Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: se...@kde.org CC: plasma-b...@kde.org The configuration dialog of Kickoff clips the buttons that allow dragging tabs. I can also make the dialog smaller and have items fall outside of the dialog window (they are clipped then). The dialog should have a minimum size that makes sure all items are visible (perhaps in this case allow for dragging additional items if necessary). Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 363851] "A stop job is running for Session 1 of user neon" during shutdown
https://bugs.kde.org/show_bug.cgi?id=363851 Sebastian Kügler changed: What|Removed |Added CC||se...@kde.org --- Comment #33 from Sebastian Kügler --- Tested and confirmed working, thanks for the fix! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 368910] Monitor change not detected on docking
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.
[KScreen] [Bug 368910] Monitor change not detected on docking
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 if you could try Plasma 5.8 Beta to verify your problem is fixed. Thanks for the feedback, though. :) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 368910] Monitor change not detected on docking
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 change events which we can react to. In your setup (hardware / software combo) that doesn't seem to be the case, so we can't really do anything (even if we know what we'd like to do). As I said, I'm mulling over a workaround, but it doesn't look too good right now. For kicks, could you check if this works in GNOME or Unity (maybe they've found such a workaround)? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 368910] Monitor change not detected on docking
https://bugs.kde.org/show_bug.cgi?id=368910 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Sebastian Kügler --- Thanks for the report, Matthias. The and information you provide (especially the annotation) is very useful. Unfortunately, I don't see how we can fix this issue, as we don't get any useful event which allows us to update the config. (The QXcbConnection BadWindow error you mention is not that useful, unfortunately.) I'll look further into this issue and will get back to you. Which version of xrandr are you using, by the way? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 368982] Impossible to change screen resolution under Wayland
https://bugs.kde.org/show_bug.cgi?id=368982 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Sebastian Kügler --- Thanks for the bug report! This is a known problem, as we have not yet fully implemented these things for Kwin/Wayland. I'll leave this bug report open as a reference for others. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 368910] Monitor change not detected on docking
https://bugs.kde.org/show_bug.cgi?id=368910 Sebastian Kügler changed: What|Removed |Added Keywords||multiscreen -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 368494] Crash in XRanDRConfig when connecting HDMI output
https://bugs.kde.org/show_bug.cgi?id=368494 Sebastian Kügler changed: What|Removed |Added Resolution|--- |UPSTREAM Status|CONFIRMED |RESOLVED --- Comment #3 from Sebastian Kügler --- To be honest, I'd rather spend my time on something else. The main reason is that we don't ship updates for older versions, so if we fixed something with respect to XRandR 1.4, this patch would still only go into Plasma 5.8. I think we can expect users who use an October release of Plasma to use the latest version of XRandR that has been released 6 months earlier. That said, thanks a lot for digging into the problem and the useful bug report! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 368494] Crash in XRanDRConfig when connecting HDMI output
https://bugs.kde.org/show_bug.cgi?id=368494 Sebastian Kügler changed: What|Removed |Added Keywords||multiscreen Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 368494] Crash in XRanDRConfig when connecting HDMI output
https://bugs.kde.org/show_bug.cgi?id=368494 Sebastian Kügler changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Sebastian Kügler --- Thanks for the bug report! I haven't seen this particular bit crashing, and of course it shouldn't. Would it be possible for you to try the KDE Neon git/unstable images and see if this improves the situation? We've fixed a number of problems in this part of the stack that may be at the root of the problem (especially, we're re-reading the crtcs at runtime now, which may fix this problem). If the problem persists, I'd like to have a look at the files in ~/.local/share/kscreen/* (that's configurations for different screens and the log of what exactly happened). Of course, an updated backtrace would be nice as well. https://community.kde.org/Solid/Projects/ScreenManagement#Debugging_Information has more information about obtaining useful debugging information, -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 368746] System does not allow to enable external monitor after plugging into dock and crashes after unplug
https://bugs.kde.org/show_bug.cgi?id=368746 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Sebastian Kügler --- Thanks for the report! Can you try Plasma 5.8, for example through Neon git/unstable? We have fixed a number of bugs that could lead to this problem, so it's most likely already fixed upstream. (I have similar hardware here, which didn't work well before and now is just fine.) If you can verify it against 5.8, please reopen this bugreport and attach the information as outlined on https://community.kde.org/Solid/Projects/ScreenManagement#Debugging_Information -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 362614] KScreen does not switch primary output reliably, flickers a lot
https://bugs.kde.org/show_bug.cgi?id=362614 Sebastian Kügler changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Sebastian Kügler --- Also, we fixed this issue with Plasma 5.8, please test that. (You can use Neon git/unstable for example.) If the issue persists, please reopen this bugreport. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 368481] Implement a Way to recover a wrong screen configuration
https://bugs.kde.org/show_bug.cgi?id=368481 --- Comment #3 from Sebastian Kügler --- @Tilman: This should be fixed with Plasma 5.8, you could try testing the Neon git / unstable version to verify if it's indeed fixed for your system as well. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 368481] Implement a Way to recover a wrong screen configuration
https://bugs.kde.org/show_bug.cgi?id=368481 Sebastian Kügler changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 368471] Setting scaling does not change anything
https://bugs.kde.org/show_bug.cgi?id=368471 Sebastian Kügler changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #6 from Sebastian Kügler --- Yes, but that will need support throughout the stack. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 --- Comment #91 from Sebastian Kügler --- As I said, please file a new report, this becomes too hard to track efficiently otherwise. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 --- Comment #89 from Sebastian Kügler --- @doctor78: Could you provide your ~/.local/share/kscreen/kscreen.log please, so I can have a look at what's failing? What graphics hardware do you use? Please file a new bugreport with this information, otherwise it gets too hard to track. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 --- Comment #88 from Sebastian Kügler --- @doctor78: Could you provide your ~/.local/share/kscreen/kscreen.log please, so I can have a look at what's failing? What graphics hardware do you use? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 368471] Setting scaling does not change anything
https://bugs.kde.org/show_bug.cgi?id=368471 --- Comment #1 from Sebastian Kügler --- Thanks for the report! Could you try our latest version, preferably even the unstable tree? You can download the dev/unstable flavor of KDE Neon (neon.kde.org) and test with that. I haven't seen this problem in a while, so before I start debugging, I need to know if it's even present in the latest release. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 368481] Implement a Way to recover a wrong screen configuration
https://bugs.kde.org/show_bug.cgi?id=368481 --- Comment #1 from Sebastian Kügler --- Thanks for the report! Could you describe the exact configuration that you can't get back from? We had a couple of problems that could lead to "impossible" configurations, but these have been fixed, so this situation should not happen anymore. You can also always press the Display button which will lead to a working config. Reverting is not really a good solution since the screen configuration change might be in reaction to a hardware event, which means that if that hardware isn't present anymore, we can't revert anyway. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 351025] When external monitor is disconnected, the laptop monitor doesn't become active again
https://bugs.kde.org/show_bug.cgi?id=351025 --- Comment #38 from Sebastian Kügler --- Very good to know, thanks for testing! As to your questions ... * the shortcut issue is of course unrelated, as you note, so it would be good if you could check if there's a bug reported for that * You can just pull in updates through apt, it doesn't matter which iso you installed from (as long as it's an iso which set up the right repos (basically means, if you don't change it, you'll continue to get updates from master. Don't be surprised if lots of package updates come in daily. * The dev/stable version will have it as soon as 5.8 is out (I've looked into backporting these fixes, but can't sensibly do that since it's a number of patches across different repositories and we have no way of testing that enough to go into a stable update, and we also have no further updates planned, so a regression introduced can't get fixed. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 356884] kscreen messes with original xrandr config, does not respect saved config, and apply defined config only on the second try.
https://bugs.kde.org/show_bug.cgi?id=356884 --- Comment #24 from Sebastian Kügler --- Very good to know, thanks for testing! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 351025] When external monitor is disconnected, the laptop monitor doesn't become active again
https://bugs.kde.org/show_bug.cgi?id=351025 --- Comment #36 from Sebastian Kügler --- @zanetti: KDE Neon has up to date packages: http://files.kde.org/neon/images/neon-devedition-gitunstable/current/ Keep in mind that these images are not production quality, but a snapshot from our development tree. Use at your own risk, but do let us know if thing work for you. :) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 368019] Resolution selection box not wide enough with scrollbars
https://bugs.kde.org/show_bug.cgi?id=368019 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Component|kcm |QStyle Product|KScreen |Breeze Assignee|se...@kde.org |hugo.pereira.da.costa@gmail ||.com Ever confirmed|0 |1 Version|git |5.7.3 --- Comment #1 from Sebastian Kügler --- Thanks for the report. The kscreen kcm doesn't do anything special with the ComboBox, so this is either a bug in Breeze or a bug in Qt. Hugo, can you have a look? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 351256] Way to distinguish more monitors with the same vendor/model label
https://bugs.kde.org/show_bug.cgi?id=351256 Sebastian Kügler changed: What|Removed |Added CC||se...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Sebastian Kügler --- Fixed in Plasma 5.8. Thanks for the report! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 Sebastian Kügler changed: What|Removed |Added Keywords||multiscreen -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 366346] Lenovo T460s + Docking station = external displays are broken with Plasma 5
https://bugs.kde.org/show_bug.cgi?id=366346 --- Comment #35 from Sebastian Kügler --- Unfortunately not, there have been too many changes to test different patchset combinations, so I'm not taking the risk to backport. It's all 5.8 material. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 367744] systemsettings5
https://bugs.kde.org/show_bug.cgi?id=367744 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Sebastian Kügler --- Please test with Plasma 5.8 once it's out, or Neon Git unstable if you're impatient. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365455] Second external monitor of MST setup does not turn on most of the times
https://bugs.kde.org/show_bug.cgi?id=365455 Sebastian Kügler changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REOPENED|RESOLVED --- Comment #38 from Sebastian Kügler --- @darkbasic: could you try upgrading your Intel drivers? We most likely can't do anything in KDE about this problem, as it's a driver / hardware problem. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365455] Second external monitor of MST setup does not turn on most of the times
https://bugs.kde.org/show_bug.cgi?id=365455 --- Comment #33 from Sebastian Kügler --- Just an observation: The kscreen.log looks completely fine as well. Would be interesting indeed if you can trigger switching the display on by going through a dpms cycle, as Martin asked. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365455] Second external monitor of MST setup does not turn on most of the times
https://bugs.kde.org/show_bug.cgi?id=365455 Sebastian Kügler changed: What|Removed |Added Summary|Second external monitor |Second external monitor of |does not turn on most of|MST setup does not turn on |the times |most of the times Version|5.7.0 |git -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365455] Second external monitor does not turn on most of the times
https://bugs.kde.org/show_bug.cgi?id=365455 --- Comment #26 from Sebastian Kügler --- It seems that kscreen thinks it has enabled the displays as you told it to, that would be consistent with what the kcm shows, and how kwin understands it (kwin would not place that window offscreen). The black screen seems actually switched off on the monitor side, at least that's what would kwin and kscreen do with a monitor just switched off. (If it just failed to enable it, it would not allow windows in that space.) Could you get me the ~/.local/share/kscreen/kscreen.log after a failed attempt? This will show us what's going on at a lower level as well. If your laptop has an HDMI port, could you hook up one of the Dell displays to that and see if it shows the problem as well? Does this always happen with the same monitor? Could you try switching the cables around and see if it's random, or if you could pin it down to one of the connectors or displays? Love your videos and screen setup, by the way. :) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 --- Comment #84 from Sebastian Kügler --- @andreas.sturmlechner Seems tricky. There is a whole range of fixes that I've done in libkscreen, the kscreen kcm and the kded module. While they all fix individual issues, backporting them isn't quite trivial. Also, there's a more intrusive change in plasmashell (plasma-workspace/shell) that fixes plasma's dealing with esp. screen changes (this is the series of bugs that make plasma not render the right containments on a given screen, including panels). To get a really useful combination, these need to go hand in hand, so you'd have to backport patch series for at least 3 repositories to make it actually useful. At that point, you're running a Frankenstein Plasma out of 5.7 and 5.8, which nobody has tested and we certainly can't guarantee to have working. If you're doing this work for a distro, I'd actually recommend spending that time and work on making sure Plasma 5.8 becomes available as soon as possible (we've already reduced the length of this release cycle by two weeks), and perhaps get our upcoming beta packaged as well to give us a bit more testing so we can iron out problems or regressions that may have been introduced and need catching before 5.8.0. If you really really really want, you could try picking libkscreen and kscreen from git master. That will still leave you with problems in plasmashell, which from a quick look at the git changes, seem quite untrivial to backport. I'm sorry I can't be of much use here... -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 --- Comment #81 from Sebastian Kügler --- Yes, neon dev unstable has all these fixes. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 363238] Docked laptop lid close does not enable external monitor
https://bugs.kde.org/show_bug.cgi?id=363238 --- Comment #10 from Sebastian Kügler --- So you want to switch layouts when the lid closes from only laptop screen enabled to only external enabled? That sounds kind of weird to me. You can achieve the same by just having the external screen connected or not, doing it when the lid closes seems counter-intuitive to me. Aside from that, I wouldn't know how to present it in the UI. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 366346] Lenovo T460s + Docking station = external displays are broken with Plasma 5
https://bugs.kde.org/show_bug.cgi?id=366346 Sebastian Kügler changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #33 from Sebastian Kügler --- Hai, thanks for testing and confirming it's fixed. I've seen your email and started replying, but got interrupted and haven't picked it up again. I'll do so this week. As to the visual bug in systemsettings, I've fixed some glitches there, but the code is kind of convoluted and I don't want to poke too much in there in its current state. We're planning a redesign of that particular UI, so likely, any time spent on it now may well be wasted. I suggest we'll look into this level of problems once we got the new design implemented. Again thanks for your help in nailing down the problems. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346795] touchscreen offset when using multiple displays
https://bugs.kde.org/show_bug.cgi?id=346795 Sebastian Kügler changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #5 from Sebastian Kügler --- This is a thing that X should take care of. We can't do anything about it in libkscreen. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 363238] Docked laptop lid close does not enable external monitor
https://bugs.kde.org/show_bug.cgi?id=363238 --- Comment #8 from Sebastian Kügler --- You can tell it not to suspend in Systemsettings | Power Management | Button Events handling. There's a checkbox that allows to not suspend when the lid is closed and an external monitor is connected. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 --- Comment #79 from Sebastian Kügler --- This bug is fixed in Plasma 5.8. If you could test against that, it would be nice. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357580] Seg Fault in plasma shell
https://bugs.kde.org/show_bug.cgi?id=357580 Sebastian Kügler changed: What|Removed |Added CC||se...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Sebastian Kügler --- The code triggering this crash is gone in Plasma 5.8. Closing this bug. If you run into a similar problem, please file a new one. Thanks for reporting the issue! -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 344612] libksysguard from Plasma 5.2 conflicts with libksysguard from kde-workspace
https://bugs.kde.org/show_bug.cgi?id=344612 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||se...@kde.org Resolution|--- |INVALID --- Comment #18 from Sebastian Kügler --- Sorry to close this bug, but we do not support installing Plasma 4 and 5 alongside. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365455] Second external monitor does not turn on most of the times
https://bugs.kde.org/show_bug.cgi?id=365455 --- Comment #23 from Sebastian Kügler --- I thought about it, but I don't think that's an option. There's a series of patches which affect this problem, some are pretty risk-free, others change low-level functions that we can't autotest. This means that backporting some of them means that we need proper user-testing, and I don't think we can get that without a beta. I'm just not comfortable putting them all in a stable branch. Related is also a series of fixes to plasmashell, without which this fix is quite useless (as Plasma will mess up containments), this also went into master, and it's really too invasive to backport. So, sorry, it's not an option. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 356884] kscreen messes with original xrandr config, does not respect saved config, and apply defined config only on the second try.
https://bugs.kde.org/show_bug.cgi?id=356884 Sebastian Kügler changed: What|Removed |Added CC||se...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #22 from Sebastian Kügler --- Could you please test this against Plasma/5.8? We have fixed a number of issues that almost certainly affect the behaviour you're seeing. If problems persist, could you please file a new bugreport with updated info? (Please also attach ~/.local/share/kscreen/kscreen.log then.) Thanks! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 351025] When external monitor is disconnected, the laptop monitor doesn't become active again
https://bugs.kde.org/show_bug.cgi?id=351025 Sebastian Kügler changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #34 from Sebastian Kügler --- A couple of causes for this bug have been fixed in the Plasma/5.8 branch. If problems persists with the latest code, please file a separate report to keep the debugging history clean (this bug-report mixes different causes and effects). -- You are receiving this mail because: You are watching all bug changes.
