[kscreenlocker] [Bug 338796] Blank the screen using Esc key while on the lock screen
https://bugs.kde.org/show_bug.cgi?id=338796 Sebastian Kügler changed: What|Removed |Added Assignee|se...@kde.org |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 436191] Kmail sometimes forgets the correct mapping of Sent and Draft folders
https://bugs.kde.org/show_bug.cgi?id=436191 Sebastian Kügler changed: What|Removed |Added CC||se...@kde.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Sebastian Kügler --- Observing the same problem, kmail regularly forgets Sent email folder settings for an account, meaning I have to set the sent folder before I can send emails again, this is quite annoying as it happens on a weekly basis. I usually leave KMail running, but it seems like every time I log out and back in, sent email folder setting is gone, and I can't send emails before setting it again. KMail Version 5.23.2 (23.04.2) on KDE Neon User Edition (up to date) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 401581] Win+P still assumes the monitors position wrongly, ignoring the Display Configuration.
https://bugs.kde.org/show_bug.cgi?id=401581 Sebastian Kügler changed: What|Removed |Added Assignee|se...@kde.org |kscreen-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 402607] Dynamic scren layout changes don't work properly in Plasma
https://bugs.kde.org/show_bug.cgi?id=402607 Sebastian Kügler changed: What|Removed |Added Assignee|se...@kde.org |kscreen-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 394161] kdeinit5 segmentation fault(11) detected after plasma desktop loaded (100%)
https://bugs.kde.org/show_bug.cgi?id=394161 Sebastian Kügler changed: What|Removed |Added Assignee|se...@kde.org |kscreen-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 402370] Multi monitor config lost while returning from standby
https://bugs.kde.org/show_bug.cgi?id=402370 Sebastian Kügler changed: What|Removed |Added Assignee|se...@kde.org |kscreen-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 377865] (De)Activating monitors on wayland does not work
https://bugs.kde.org/show_bug.cgi?id=377865 Sebastian Kügler changed: What|Removed |Added Assignee|se...@kde.org |kscreen-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 411337] Scale factor per display not applied
https://bugs.kde.org/show_bug.cgi?id=411337 Sebastian Kügler changed: What|Removed |Added Assignee|se...@kde.org |kscreen-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 376341] dual screen setup broken after suspend
https://bugs.kde.org/show_bug.cgi?id=376341 Sebastian Kügler changed: What|Removed |Added Assignee|se...@kde.org |kscreen-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 406377] [Feature Request] Add extend to top option
https://bugs.kde.org/show_bug.cgi?id=406377 Sebastian Kügler changed: What|Removed |Added Assignee|se...@kde.org |kscreen-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 407058] KDE Plasma5 can't change resolution in VM after last update
https://bugs.kde.org/show_bug.cgi?id=407058 Sebastian Kügler changed: What|Removed |Added Assignee|se...@kde.org |kscreen-bugs-n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425636] New: Rotation makes widget controls unusable and positioning / sizing hard
https://bugs.kde.org/show_bug.cgi?id=425636 Bug ID: 425636 Summary: Rotation makes widget controls unusable and positioning / sizing hard Product: plasmashell Version: 5.19.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: se...@kde.org CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Rotated widgets don't behave well on the desktops, some controls don't work, rotated geometry doesn't seem to be taken into account for placement. STEPS TO REPRODUCE 1. add some widget to desktop 2. rotate it 45 degrees CCW 3. try to use the resize controls or toolbars OBSERVED RESULT * The buttons (rotate, configure, show bg, remove) are covered by tooltips on hover, they're not reachable under the tooltip anymore, so you can't even rotate it back * the resize handles don't seem to take rotation into account, for example the right-middle handle can't be used to horizontally resize * the position/size indicator rubberband is not rotated, to the space reservation is off and I can't move the widget closer to the border https://youtu.be/vSOF3W2oMnU EXPECTED RESULT behavior as if it weren't rotated. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon User KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73 Qt Version: 5.14 Using dual screen. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425539] New: Rows display displays one row too many
https://bugs.kde.org/show_bug.cgi?id=425539 Bug ID: 425539 Summary: Rows display displays one row too many Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kwin_virtualdesktops Assignee: kwin-bugs-n...@kde.org Reporter: se...@kde.org CC: plasma-b...@kde.org Target Milestone: --- SUMMARY The rows display on the LHS of this KCM displays one row too many. When adding or removing a row, it shows one more with i18n error. Additionally, when using the keyboard to input a number in the row count spinner, the Apply button doesn't get enabled right away. Linux/KDE Plasma: Neon User KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425538] New: on-screen display period broken
https://bugs.kde.org/show_bug.cgi?id=425538 Bug ID: 425538 Summary: on-screen display period broken Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kwin_virtualdesktops Assignee: kwin-bugs-n...@kde.org Reporter: se...@kde.org CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Setting the interval to show the desktop switching OSD is broken in multiple ways: 1. inputting a number doesn't enable the Apply button (scrolling to change number seems to work) 2. inputting 1000 (as opposed to 1.000) resets it to zero I'm using en_US locale. There are some more pretty basic bugs in there which makes it barely work. Could it be that merging the QtQuick port for this KCM has been rushed a little? I'm referring to https://bugs.kde.org/show_bug.cgi?id=417751 which I also noticed when re-adding rows after trying if resetting to defaults helped me out here. Then, while I set rows to two, the display shows three rows (plus above i18n error), filing another bug for this just now. Linux/KDE Plasma: Neon User 20.04 KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 397825] [Wayland] Message viewer displays only a black rectangle
https://bugs.kde.org/show_bug.cgi?id=397825 Sebastian Kügler changed: What|Removed |Added CC||se...@kde.org --- Comment #10 from Sebastian Kügler --- Can confirm. When starting kmail under Wayland, the messageviewer stays black (also after switching messages), not just after restoring the window. When I start kmail under XWayland as follows, it works: export DISPLAY=:1 export QT_QPA_PLATFORM=xcb kmail This is on KDE Neon User Edition KMail 20.04 Plasma 5.19.3 Frameworks 5.72 Qt 5.14.2 Intel system with Linux 5.6 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418524] New: Cannot unselect right click behaviour in touchpad kcm
https://bugs.kde.org/show_bug.cgi?id=418524 Bug ID: 418524 Summary: Cannot unselect right click behaviour in touchpad kcm Product: systemsettings Version: 5.18.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: se...@kde.org Target Milestone: --- SUMMARY After selecting one of the options for right click behaviour in the touchpad KCM, one can't go back to none selected (they're radiobuttons, I can only select the other one, but not none). STEPS TO REPRODUCE 1. Pick on option of right-click behavior 2. try to go back to no selected option (default) 3. ... can't :( SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon User Edition 5.18.1 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418523] New: touchpad scrolls even when it fully fits into the viewport
https://bugs.kde.org/show_bug.cgi?id=418523 Bug ID: 418523 Summary: touchpad scrolls even when it fully fits into the viewport Product: systemsettings Version: 5.18.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: se...@kde.org Target Milestone: --- SUMMARY touchpad scrolls even when it fully fits into the viewport STEPS TO REPRODUCE 1. open touchpad kcm 2. make window big enough to fit all of the contents in 3. scroll or try dragging the window from within the touchpad kcm OBSERVED RESULT content scrolls EXPECTED RESULT it should not scroll, but drag when dragged (and do nothing when scrolled) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon User Edition KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413021] systemtray doesn't show battery widget
https://bugs.kde.org/show_bug.cgi?id=413021 --- Comment #4 from Sebastian Kügler --- I just noticed that also the notification widget is not loaded by the system tray. (Same as with battery, I can add it manually to the panel.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413021] systemtray doesn't show battery widget
https://bugs.kde.org/show_bug.cgi?id=413021 --- Comment #3 from Sebastian Kügler --- Yes to both: * org.kde.Solid.PowerManagement is registered on the session bus * X-Plasma-NotificationArea=true is in both, metadata.json and metadata.desktop files, and the *Category is "Hardware" It's completely vanished, i.e. not loaded at all. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 413021] New: systemtray doesn't show battery widget
https://bugs.kde.org/show_bug.cgi?id=413021 Bug ID: 413021 Summary: systemtray doesn't show battery widget Product: plasmashell Version: 5.17.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: se...@kde.org Target Milestone: 1.0 SUMMARY For about two releases, the battery widget has vanished from the systemtray. I can add it to the panel separately, and then it does work, but the automatic showing / hiding obviously doesn't. It's like my systemtray doesn't find the battery. I can also not enable it in systemtray settings, it's not shown there. The Power Management systemsettings module works just fine. Also the power management plasma engine shows hasbattery and other values correct. STEPS TO REPRODUCE 1. clean plasmashell config 2. restart plasmashell 3. observe no battery widget OBSERVED RESULT EXPECTED RESULT battery monitor in systemtray I'm on Neon dev/unstable, just upgraded to Plasma 5.17 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 408416] Breeze partly ignores color changes at runtime
https://bugs.kde.org/show_bug.cgi?id=408416 Sebastian Kügler changed: What|Removed |Added Version Fixed In|5.16.0 |5.16.1 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 408416] Breeze partly ignores color changes at runtime
https://bugs.kde.org/show_bug.cgi?id=408416 Sebastian Kügler changed: What|Removed |Added Version Fixed In||5.16.0 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 408416] Breeze partly ignores color changes at runtime
https://bugs.kde.org/show_bug.cgi?id=408416 Sebastian Kügler changed: What|Removed |Added Assignee|unassigned-b...@kde.org |se...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 408416] Breeze partly ignores color changes at runtime
https://bugs.kde.org/show_bug.cgi?id=408416 Sebastian Kügler changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Sebastian Kügler --- Patch submitted, bug can be closed, fixed in 5.16.0. (Don't know why the commit didn't close it automatically, it seems the commit didn't make it into this bugreport.) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 408416] Breeze partly ignores color changes at runtime
https://bugs.kde.org/show_bug.cgi?id=408416 --- Comment #1 from Sebastian Kügler --- Possibly patch: https://phabricator.kde.org/D21646 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 408416] New: Breeze partly ignores color changes at runtime
https://bugs.kde.org/show_bug.cgi?id=408416 Bug ID: 408416 Summary: Breeze partly ignores color changes at runtime Product: Breeze Version: 5.15.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: QStyle Assignee: unassigned-b...@kde.org Reporter: se...@kde.org Target Milestone: --- SUMMARY Color changes only partly reflected in Breeze QStyle-styled applications. STEPS TO REPRODUCE 1. open kcmshell5 colors 2. change to a theme with a different highlight color 3. apply OBSERVED RESULT Checkbox in the Colors KCM doesn't change color. EXPECTED RESULT Checkbox in the Colors KCM shows the new color. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Neon Git Stable User (available in About System) KDE Plasma Version: 5.15 KDE Frameworks Version: 5.58 Qt Version: 5.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354802] Desktop Icon position gets scrambled sometimes on reboot.
https://bugs.kde.org/show_bug.cgi?id=354802 Sebastian Kügler changed: What|Removed |Added Assignee|se...@kde.org |h...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 395804] Regression: "Switch Display" invoked via global shortcut no longer allows keyboard-only operation
https://bugs.kde.org/show_bug.cgi?id=395804 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! This seems like an oversight, indeed. -- You are receiving this mail because: You are watching all bug changes.
[kgamma] [Bug 395901] Setting gamma for individual screens does not work
https://bugs.kde.org/show_bug.cgi?id=395901 Sebastian Kügler changed: What|Removed |Added Assignee|se...@kde.org |plasma-b...@kde.org Component|kcm |general Product|KScreen |kgamma --- Comment #1 from Sebastian Kügler --- Thanks for the bugreport! I've corrected the component of this bugreport, the gamma settings are not actually a part of KScreen, but have their own component. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393924] Immediate logoff if settings are applied
https://bugs.kde.org/show_bug.cgi?id=393924 Sebastian Kügler changed: What|Removed |Added CC||se...@kde.org --- Comment #2 from Sebastian Kügler --- Sounds like kwin is crashing when changing the config. Reassignung. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 393924] Immediate logoff if settings are applied
https://bugs.kde.org/show_bug.cgi?id=393924 Sebastian Kügler changed: What|Removed |Added Product|KScreen |kwin Assignee|se...@kde.org |kwin-bugs-n...@kde.org Component|common |wayland-generic -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 393873] Monitors can't be set up with their bottoms aligned
https://bugs.kde.org/show_bug.cgi?id=393873 --- Comment #1 from Sebastian Kügler --- IIRC you should be able to forego the snapping by holding CTRL presses. Could you try this and report back (I can't look into the code right now)? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 390283] Plasma sees external monitor after disconnecting
https://bugs.kde.org/show_bug.cgi?id=390283 --- Comment #3 from Sebastian Kügler --- Thanks for the report! The information requested in https://community.kde.org/Solid/Projects/ScreenManagement#Debugging_Information especially the kscreen.log would be helpful. Even cooler: if you could mark the log with or something like this, so I can actually see what you're physically doing would be great. Cheers! -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 391196] Pressing powerbutton make notification.
https://bugs.kde.org/show_bug.cgi?id=391196 Sebastian Kügler changed: What|Removed |Added CC||se...@kde.org --- Comment #7 from Sebastian Kügler --- I'm not sure. The system should go into suspend as quickly as possible, and what use would be a notification when you close the lid? The screen isn't visible then, and in case of suspend, the notification would still be there post-resume, and then we definitely don't want to show it. I for one don't want my system to play sound on normal events, especially laptops are often used in environments with people around me and I don't want to make noise. Why exactly would you want to play a sound here? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391558] External monitor does not wake up
https://bugs.kde.org/show_bug.cgi?id=391558 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #7 from Sebastian Kügler --- It's highly unlikely that this is a Plasma issue, so I'll close this bugreport (it's not useful to track this here, just muddies up our bug list and makes it harder to manage). Thanks for the report however! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365865] Display resolution setting in Display Configuration not obeyed in Wayland Plasma session
https://bugs.kde.org/show_bug.cgi?id=365865 --- Comment #9 from Sebastian Kügler --- @RussianNeuroMancer Which Plasma version did you test? (You can find it in kinfocenter.) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 390096] Display "new screen connected" OSD when laptop Display key is pressed
https://bugs.kde.org/show_bug.cgi?id=390096 --- Comment #11 from Sebastian Kügler --- This should work. My own laptop has teh XF86Display keysym mapped, yours seems to have Super_L + p mapped (in both cases). Not long ago, to make work, we added a shortcut also for super+p to increase compatibility with Windowsy hardware (which seems to prefer super+p nowadays. In any case, if it doesn't work, you can always add a keymapping for XF86Display, but as I said, that shouldn't be necessary. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 390096] Display "new screen connected" OSD when laptop Display key is pressed
https://bugs.kde.org/show_bug.cgi?id=390096 Sebastian Kügler changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/ksc ||reen/eacbddd22d990d4f434b8b ||9aaab865d5ac62a630 --- Comment #10 from Sebastian Kügler --- Git commit eacbddd22d990d4f434b8b9aaab865d5ac62a630 by Sebastian Kügler. Committed on 01/03/2018 at 09:47. Pushed by sebas into branch 'master'. Show config selection OSD when display button is pressed Summary: This makes the working of the display button much more intuitive. Test Plan: Tested with external display plugged in, system behaves as expected Reviewers: #plasma, dvratil Reviewed By: dvratil Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D10896 M +3-54 kded/daemon.cpp M +0-4kded/daemon.h https://commits.kde.org/kscreen/eacbddd22d990d4f434b8b9aaab865d5ac62a630 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 390096] Display "new screen connected" OSD when laptop Display key is pressed
https://bugs.kde.org/show_bug.cgi?id=390096 --- Comment #8 from Sebastian Kügler --- Run xev, press the display button, paste the output from xev here and I'll tell you if it'll work. (XF86Display is the key code you're looking for, CTRL+P should also work.) Alternatively, wait for the patch to land plus ~1 day and update from dev unstable packages or run the latest iso with those packages. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 390096] Display "new screen connected" OSD when laptop Display key is pressed
https://bugs.kde.org/show_bug.cgi?id=390096 --- Comment #6 from Sebastian Kügler --- @Andrew Email me for my physical address :) (A donation to KDE e.V. is always appreciated.) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 390096] Display "new screen connected" OSD when laptop Display key is pressed
https://bugs.kde.org/show_bug.cgi?id=390096 --- Comment #3 from Sebastian Kügler --- https://phabricator.kde.org/D10896 implements this. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 390096] Display "new screen connected" OSD when laptop Display key is pressed
https://bugs.kde.org/show_bug.cgi?id=390096 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Sebastian Kügler --- Good idea, I'll look into that. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 390921] Full-screen applications launched outside of applications menu change system resolution
https://bugs.kde.org/show_bug.cgi?id=390921 --- Comment #3 from Sebastian Kügler --- I'd be at a loss why this would happen... -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 390921] Full-screen applications launched outside of applications menu change system resolution
https://bugs.kde.org/show_bug.cgi?id=390921 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Sebastian Kügler --- You may not be running the same command, check your .desktop file what parameters it uses, make sure you run that command from the same environment. This is not a source code, but a setup problem, so it doesn't make sense to track it as a software issue. I'm sorry if that sounds disappointing for you, but I'm looking at it from a developer point of view, and in that light, it's not a defect we can fix for you. Thanks for the report, however! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 390638] Wayland - cannot change primary screen
https://bugs.kde.org/show_bug.cgi?id=390638 Sebastian Kügler changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED Latest Commit||https://commits.kde.org/ksc ||reen/cd3b350e0225a3a1616804 ||924420f86e39db50a1 --- Comment #4 from Sebastian Kügler --- Git commit cd3b350e0225a3a1616804924420f86e39db50a1 by Sebastian Kügler. Committed on 23/02/2018 at 08:57. Pushed by sebas into branch 'master'. hide primary display combo when not supported Summary: Some backends, for example the kwayland backend, do not support setting the primary display. The backends already make their feature set known so we can just hide it from the UI. It's enough to hide it from the UI since setting it doesn't make any difference, the libkscreen backend will simply ignore it internally, so it's just honest to not show it. Test Plan: ran kscreen kcm on both, X11 and wayland platforms, combo and label are shown and hidden as expected Reviewers: #plasma, dvratil, davidedmundson Reviewed By: #plasma, davidedmundson Subscribers: kpiwowarski, plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D10723 M +4-2kcm/src/widget.cpp M +2-0kcm/src/widget.h https://commits.kde.org/kscreen/cd3b350e0225a3a1616804924420f86e39db50a1 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 390638] Wayland - cannot change primary screen
https://bugs.kde.org/show_bug.cgi?id=390638 Sebastian Kügler changed: What|Removed |Added Ever confirmed|0 |1 Resolution|INVALID |--- Status|RESOLVED|REOPENED --- Comment #3 from Sebastian Kügler --- I agree, we should hide the respective UI in this case: https://phabricator.kde.org/D10723 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 381515] KScreen has problem with multiple monitors with different resolutions
https://bugs.kde.org/show_bug.cgi?id=381515 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #24 from Sebastian Kügler --- I'll close this bugreport since it's apparently fixed by an upgrade, not worth spending valuable development time on it as underlying issues area already reported most likely. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 378598] Scaling display affects all monitors
https://bugs.kde.org/show_bug.cgi?id=378598 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Sebastian Kügler --- Thanks for the report! This isn't supported on X11, and we're not planning to. The Wayland session already has this feature, I'd suggest to consider moving to Wayland. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 390637] Further (temporary) options for screen management
https://bugs.kde.org/show_bug.cgi?id=390637 Sebastian Kügler changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #1 from Sebastian Kügler --- We're not tracking potential features in our bugs database. I can't say how big the group of users would be for this feature, but currently, I can't be anything but honest: it doesn't have high enough priority to implement it in the Plasma screen management stack. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 390638] Wayland - cannot change primary screen
https://bugs.kde.org/show_bug.cgi?id=390638 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Sebastian Kügler --- The panel and primary screen have nothing to do with each other. You can move the panel using the panel controller. Note: Primary screen is not a concept in Wayland, it's not even well defined in X11-based Plasma, so we're moving away from it. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 390724] kscreen 90 counterclockwise second monitor shows mouse pointer, but no windows
https://bugs.kde.org/show_bug.cgi?id=390724 Sebastian Kügler changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #3 from Sebastian Kügler --- These symptoms are not controlled by kscreen, they're probably a driver problem or something lower in the graphics stack. I'm afraid I'll have to close this bugreport, since it won't be very useful for us in improving Plasma. You may have more luck reporting this to nvidia or Xorg. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 389673] disconnected wifi icon barely visible
https://bugs.kde.org/show_bug.cgi?id=389673 --- Comment #1 from Sebastian Kügler --- Created attachment 110254 --> https://bugs.kde.org/attachment.cgi?id=110254&action=edit screenshot showing the faint icon -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 389673] New: disconnected wifi icon barely visible
https://bugs.kde.org/show_bug.cgi?id=389673 Bug ID: 389673 Summary: disconnected wifi icon barely visible Product: Breeze Version: 5.11.95 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: se...@kde.org CC: kain...@gmail.com Target Milestone: --- Wifi icon when inactive is too faint. On TN panels, the icon is barely visible in its default state after installation. It would be good if it had a little more contrast, or perhaps fully opaque and an indicator that the wifi is disconnected. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 389514] internal screen frequently turns black
https://bugs.kde.org/show_bug.cgi?id=389514 --- Comment #1 from Sebastian Kügler --- Can you attach the following information to this bug-report, please? It'll help me to figure out what the problem may be. https://community.kde.org/Solid/Projects/ScreenManagement#Debugging_Information It would be very helpful if you could mark in kscreen.log where the blacking out occured, so I can clearly see what events triggered it. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 389490] [Wayland] Display scale setting is lost when computer is restarted
https://bugs.kde.org/show_bug.cgi?id=389490 --- Comment #1 from Sebastian Kügler --- Thanks for the bug-report! Could you please collect the debugging informatio as outlined on https://community.kde.org/Solid/Projects/ScreenManagement#Debugging_Information and attach to this bug? It'll help me to figure out where the problem is. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 389097] Resolution for laptop screen is reset at each log in when there are multiple screens
https://bugs.kde.org/show_bug.cgi?id=389097 Sebastian Kügler changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |INVALID --- Comment #3 from Sebastian Kügler --- In that case, this bug-report isn't very useful. We had a ton of fixes which could affect this, and with only one system showing the problem and no debugging information, this bug isn't very useful to track and cover up other, more useful information. Thanks for the report, however. Please let me know when / if you can try a newer version of supply the needed information, closed bugreports are easily reopened. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 388469] systemsettings5 crashes on display settings component
https://bugs.kde.org/show_bug.cgi?id=388469 --- Comment #5 from Sebastian Kügler --- Can you please run systemsettings5 through gdb and attach the backtrace? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 389254] Display going to a wrong resolution
https://bugs.kde.org/show_bug.cgi?id=389254 --- Comment #1 from Sebastian Kügler --- Did you try a different cable? This sounds much like a problem with the hardware and hardly anything we can solve in software. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 389193] KDE crashes and ksceen_backend segfault when monitor is turned off or turned on
https://bugs.kde.org/show_bug.cgi?id=389193 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from Sebastian Kügler --- Hi Valdas, Thanks for your report! If you get thrown back to the login screen, it's your X server that crashes. KDE can't do anything about this, so you'd need to file a bug at Xorg. I'll mark the bug as upstream in KDE's bugtracker, meaning we won't track it any further here. Sorry if this doesn't help you a lot, but the code problem needs fixing elsewhere. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 388468] Settings showing second screen although I only have one laptop screen
https://bugs.kde.org/show_bug.cgi?id=388468 --- Comment #1 from Sebastian Kügler --- Thanks for the report, Tom! Could you please collect the information as outlined on https://community.kde.org/Solid/Projects/ScreenManagement#Debugging_Information so I can have a look at the issue? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 384733] Wayland configs are not saved
https://bugs.kde.org/show_bug.cgi?id=384733 Sebastian Kügler changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #26 from Sebastian Kügler --- Most likely fixed with https://phabricator.kde.org/D9902 Please reopen if this still persists with Plasma 5.12. Also: Thanks for the feedback! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 389097] Resolution for laptop screen is reset at each log in when there are multiple screens
https://bugs.kde.org/show_bug.cgi?id=389097 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Sebastian Kügler --- Hi David, Thanks for the bug-report! Could you please give the latest Plasma version a try? We have fixed a number of bugs in this area and your problem might already be addressed with these changes. An easy way to test the latest version is KDE's neon git/unstable, which allows you to run today's code and test. If your problem persists, could you please collect and attach the information outlined in this wiki page to this bug report? https://community.kde.org/Solid/Projects/ScreenManagement Thanks for helping us to improve Plasma! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 389016] [Wayland] Setting Primary Display thru the KScreen KCM does not save
https://bugs.kde.org/show_bug.cgi?id=389016 --- Comment #4 from Sebastian Kügler --- Right, good to know. Also very good that I asked that question, because I've been working on something very similar. If you hit me up on IRC or by email I can show you what I already have, might save you some work. I'll close this bugreport for now, since it doesn't add much tracking this in a bugreport as long as we haven't decided what to do with it at all. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 389016] [Wayland] Setting Primary Display thru the KScreen KCM does not save
https://bugs.kde.org/show_bug.cgi?id=389016 Sebastian Kügler changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 389016] [Wayland] Setting Primary Display thru the KScreen KCM does not save
https://bugs.kde.org/show_bug.cgi?id=389016 --- Comment #2 from Sebastian Kügler --- The problem is that Primary Display is not a thing in Wayland. We haven't entirely made up our mind what we want it for, so that is a bit in limbo. As KScreen reads the actual screen setup, and not just a config file, it's expected (but not intuitive) that the primary display setting won't be saved. What do you want to achieve by setting the primary display? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 388278] Cursor changes to resizing mode shape after minimize/restore kscreen kcm
https://bugs.kde.org/show_bug.cgi?id=388278 --- Comment #6 from Sebastian Kügler --- Okay, same here on at least two systems tested. It doesn't seem to be related to that. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 355396] dual monitor become single after reboot
https://bugs.kde.org/show_bug.cgi?id=355396 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #8 from Sebastian Kügler --- Could you guys also check whether this problem exists if you use the nouveau driver? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 388278] Cursor changes to resizing mode shape after minimize/restore kscreen kcm
https://bugs.kde.org/show_bug.cgi?id=388278 Sebastian Kügler changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #4 from Sebastian Kügler --- I've had a closer look, here are my findings: The problem happens when the mouse moves over the splitter between the QML widget with the previews and the lower part with the combobox and settings per output. The cursor isn't reset to the arrow shape onMouseOut. - My desktop (Qt 5.9.3 shows this problem) - My laptop (Qt 5.9.4) doesn't show it - My other laptop (5.9.2) doesn't show it - Yet another system (Qt 5.9.3) doesn't show it Kscreen's code base doesn't do anything with the mouse cursor. This means whatever the problem is, it's probably not in KScreen, but KScreen does something to trigger it. So let's start the crapshooting: What graphics driver do you use? Anything else that makes your system "special"? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 388812] Display settings window partially visible after unplugging a second screen with different resolution
https://bugs.kde.org/show_bug.cgi?id=388812 Sebastian Kügler changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Sebastian Kügler --- Supposedly, this is fixed in a newer frameworks version: The kcmshell dialog has gained scrollbars now which makes the Apply button reachable. As such, I'm closing this bugreport with the request to re-open it if the problem persists in Plasma 5.12. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 388278] Cursor changes to resizing mode shape after minimize/restore kscreen kcm
https://bugs.kde.org/show_bug.cgi?id=388278 Sebastian Kügler changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #3 from Sebastian Kügler --- Thanks, that helps. I can reproduce this problem now. Will have a look. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 388278] Cursor changes to resizing mode shape after minimize/restore kscreen kcm
https://bugs.kde.org/show_bug.cgi?id=388278 --- Comment #1 from Sebastian Kügler --- I can't confirm this, it doesn't happen on my system. How did you start systemsettings? Did you move the cursor over the window before minimizing it? Do you see it ever with other apps? (I'm shooting a bit in the dark, since I don't really have a clue how this could happen.) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 388218] Desktop scaling is applied twice in Scale Display preview
https://bugs.kde.org/show_bug.cgi?id=388218 Sebastian Kügler changed: What|Removed |Added CC||se...@kde.org --- Comment #4 from Sebastian Kügler --- I can't reproduce this on my system. Could you post the info as outlined in https://community.kde.org/Solid/Projects/ScreenManagement#Debugging_Information here, so I can have a look at what's specific to your setup? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 355396] dual monitor become single after reboot
https://bugs.kde.org/show_bug.cgi?id=355396 Sebastian Kügler changed: What|Removed |Added CC||se...@kde.org --- Comment #7 from Sebastian Kügler --- @morbid: Could you attach the information outlined in https://community.kde.org/Solid/Projects/ScreenManagement#Debugging_Information please? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 388670] No 1080p or 720p resolutions on 4k display
https://bugs.kde.org/show_bug.cgi?id=388670 Sebastian Kügler changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #3 from Sebastian Kügler --- Thanks for the quick reply! I suppose the old snapshot also contains a different Xorg version or different (version) of the graphics driver? In any case, your Xorg doesn't provide these modes anymore. The reasons for this can be manifold, but you can probably get them back by adding a modeline. Plasma just reads whatever information xrandr provides, so as soon as you get back the missing modes into xrandr, it'll also work with Plasma. I'll mark this as an upstream problem, since we can't fix this in Plasma or KScreen, not because it's not an actual issue, but because it needs to be handled outside of Plasma's codebase. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 388670] No 1080p or 720p resolutions on 4k display
https://bugs.kde.org/show_bug.cgi?id=388670 --- Comment #1 from Sebastian Kügler --- Thanks for the report! Could you please run xrandr -q (assuming you're running X11, not Wayland) on this system and post the output here? This helps us to identify where the problem may lie. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 387865] [feature request] Save various screens' profiles
https://bugs.kde.org/show_bug.cgi?id=387865 Sebastian Kügler changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Sebastian Kügler --- Thanks for the report! This is done automatically. The configuration is saved as a hash of your screens connected, so it should be remembered for every individual setup you have configured at least once. The fact that it doesn't work for you can have multiple reasons, if you're complaining that the screens are not always automatically refreshed or enabled, I'd first and foremost check that, it we don't get a "screen connected" or "setup changed" event, we can't load and apply the correct configuration. So much for the background, and how it *should* work. Could you look at the following page and collect the debug information asked for there: https://community.kde.org/Solid/Projects/ScreenManagement#Debugging_Information Ideally, tail -f kscreen.log while you're plugging and unplugging a screen and see what happens, there should be quite some output just by plugging in a screen, and if nothing happens then, we have the culprit. Otherwise, we know at least that we should react to something, and then maybe the reason is in the logs. I'll close this bugreport since it's really not very useful, instead, I would like to you file a new bugreport once you collected above information. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 360058] Kscreen should check screen at wakeup from suspend
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, nothing may have changed, we have *numerous* reports that for many users, the situation has improved and kscreen just works. That's not really helping you, but your view on the situation is limited it seems, and as a result of that, you're treating developers unfairly. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 386900] KScreen picks wrong resolution in QEMU on wayland
https://bugs.kde.org/show_bug.cgi?id=386900 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Sebastian Kügler --- Thanks! Let's close this bug then, if the problem persists, we can always re-open it and investigate further. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 386637] Regional > Formats Language Change
https://bugs.kde.org/show_bug.cgi?id=386637 Sebastian Kügler changed: What|Removed |Added Latest Commit||https://commits.kde.org/pla ||sma-desktop/8fea7fdaab1e7e8 ||5b46b9b423d8d394156f1d579 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Sebastian Kügler --- Git commit 8fea7fdaab1e7e85b46b9b423d8d394156f1d579 by Sebastian Kügler. Committed on 10/11/2017 at 08:24. Pushed by sebas into branch 'master'. ui polish of formats kcm Change Examples to description and 24 to 24.00 M +1-1kcms/formats/kcmformats.cpp M +1-1kcms/formats/kcmformatswidget.ui https://commits.kde.org/plasma-desktop/8fea7fdaab1e7e85b46b9b423d8d394156f1d579 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 386638] Accessibility > Bell Language Change
https://bugs.kde.org/show_bug.cgi?id=386638 Sebastian Kügler changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/pla ||sma-desktop/e1b3898c7e88c4e ||eed3bb646d3cb124a65784b03 Status|UNCONFIRMED |RESOLVED --- Comment #1 from Sebastian Kügler --- Git commit e1b3898c7e88c4eeed3bb646d3cb124a65784b03 by Sebastian Kügler. Committed on 09/11/2017 at 11:25. Pushed by sebas into branch 'master'. Change visible bell to visual bell M +3-3doc/kcontrol/kcmaccess/index.docbook M +3-3kcms/access/accessibility.ui M +1-1kcms/access/kcmaccess.desktop https://commits.kde.org/plasma-desktop/e1b3898c7e88c4eeed3bb646d3cb124a65784b03 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 371276] Only black screen with breeze plymouth theme in plasma 5.8.2
https://bugs.kde.org/show_bug.cgi?id=371276 Sebastian Kügler changed: What|Removed |Added CC|se...@kde.org | -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 371276] Only black screen with breeze plymouth theme in plasma 5.8.2
https://bugs.kde.org/show_bug.cgi?id=371276 Sebastian Kügler changed: What|Removed |Added Assignee|plasma-de...@kde.org|plasma-b...@kde.org CC||se...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 386321] configuration not remembered for secondary outputs
https://bugs.kde.org/show_bug.cgi?id=386321 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #4 from Sebastian Kügler --- Alright, thanks for the report! I'll mark the bug as invalid, since it's a cable / connector problem. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 386467] Expose auto-lip-sync value through kscreen-doctor
https://bugs.kde.org/show_bug.cgi?id=386467 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Sebastian Kügler --- KScreen is not a framework or applications to receive screen information, it's a tool for screen setup. We've actually moved several applications away from using kscreen because we don't want to concentrate kscreen on these use-cases, but make the case of setting up screens better. While libsync may be useful to applications, kscreen would be the wrong tool for the job, apps that need it (and there's I think zero overal with kscreen's current users) would be better of querying the HDMI interface directly. I value the suggestions, and I don't want to dismiss is, but it wouldn't make kscreen better to add this here. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 384733] Wayland configs are not saved
https://bugs.kde.org/show_bug.cgi?id=384733 --- Comment #23 from Sebastian Kügler --- Looking into this, my findings so far: We don't get a change event in kded after the scale has changed, this means that the config isn't saved, so it can't be restored. I'm looking into why we don't get said change event right now. Problem is also that I'm reproducing the same symptom but with different assumptions (my config isn't there, Rainer's is). -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 385553] Cannot unify outputs
https://bugs.kde.org/show_bug.cgi?id=385553 --- Comment #3 from Sebastian Kügler --- https://phabricator.kde.org/D8391 and https://phabricator.kde.org/D8390 should fix this. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 386321] configuration not remembered for secondary outputs
https://bugs.kde.org/show_bug.cgi?id=386321 Sebastian Kügler changed: What|Removed |Added Summary|KDE 5 seems to forget the |configuration not |settings for second |remembered for secondary |displays. |outputs --- Comment #1 from Sebastian Kügler --- Thanks for the bugreport! Could you collect the config files and log file as outlined in https://community.kde.org/Solid/Projects/ScreenManagement so I can see what's happening on your system? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 376128] SMB://server/dir Timeout on Server server in Dolphin
https://bugs.kde.org/show_bug.cgi?id=376128 Sebastian Kügler changed: What|Removed |Added CC||se...@kde.org Assignee|plasma-de...@kde.org|plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 383614] KCM opened from tray icon has wrong icon under Wayland
https://bugs.kde.org/show_bug.cgi?id=383614 Sebastian Kügler changed: What|Removed |Added Assignee|plasma-de...@kde.org|plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 385672] Identify display broken on wayland
https://bugs.kde.org/show_bug.cgi?id=385672 --- Comment #1 from Sebastian Kügler --- Thanks for the report! I'm actually working on a fix for this problem, see https://phabricator.kde.org/D3598 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 385553] Cannot unify outputs
https://bugs.kde.org/show_bug.cgi?id=385553 Sebastian Kügler changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Sebastian Kügler --- Could you please test this with 5.11? We have fixed a large number of bugs that could cause this behavior since Plasma 5.5. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 369850] Can't browse samba workgroups
https://bugs.kde.org/show_bug.cgi?id=369850 Sebastian Kügler changed: What|Removed |Added CC||se...@kde.org Assignee|plasma-de...@kde.org|plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 384066] Auto-rotate screen not working for Accelerometer sensors
https://bugs.kde.org/show_bug.cgi?id=384066 --- Comment #4 from Sebastian Kügler --- Hey Lorn, cool that you want to help us out! Here's some information that hopefully gets you started: We have discussed a solution on the plasma list here: https://www.mail-archive.com/plasma-devel@kde.org/msg73143.html Code can be found in the sebas/touchscreen branch of the libkscreen repository, it's currently only some test code, but overall it's not too much work I think, nevertheless, help is greatly appreciated. Feel free to email plasma-devel or catch us on IRC #plasma on Freenode if you have something you'd like discussed, asked, proposed. Cheers! -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 384999] Default setting of no borders drawn around dock widgets causes usability issues with multiple adjacent dock widgets
https://bugs.kde.org/show_bug.cgi?id=384999 Sebastian Kügler changed: What|Removed |Added Assignee|plasma-de...@kde.org|plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 384733] Wayland configs are not saved
https://bugs.kde.org/show_bug.cgi?id=384733 Sebastian Kügler changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #16 from Sebastian Kügler --- Note: This needs David's kwayland's 2b3f9509ac1 to not crash. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 384733] Wayland configs are not saved
https://bugs.kde.org/show_bug.cgi?id=384733 --- Comment #15 from Sebastian Kügler --- Git commit d16f63b6e64b49f8dbd4742045b0766a8c550b4b by Sebastian Kügler. Committed on 21/09/2017 at 14:15. Pushed by sebas into branch 'master'. inform outputconfiguration clients that a change has been applied Summary: After changing the output configuration, the client expects that it is informed whether or not a new configuration has been applied (or failed). This was ommitted so far, meaning that clients wouldn't know what happened in kwin. Since we don't track if a setting failed yet, send the applied() signal regardless. Test Plan: Verified that the signal arrived in libkscreen after changing scale of an output Reviewers: graesslin, davidedmundson Reviewed By: davidedmundson Subscribers: kwin, #kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D7910 M +7-0platform.cpp M +5-0plugins/platforms/drm/drm_backend.cpp https://commits.kde.org/kwin/d16f63b6e64b49f8dbd4742045b0766a8c550b4b -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 384733] Wayland configs are not saved
https://bugs.kde.org/show_bug.cgi?id=384733 --- Comment #14 from Sebastian Kügler --- Git commit 19e96249d78601d77e022a5ae081be8606ed402e by Sebastian Kügler. Committed on 21/09/2017 at 13:10. Pushed by sebas into branch 'Plasma/5.11'. track the config to monitor, save scale Summary: When doApplyConfig is called, we forgot to change the monitored config, which means we weren't tracking changes anymore. This patch makes sure that the new config becomes the monitored one in that case. Also, save the scale property to the json config, we forgot to do that. Test Plan: Scale changes through kwin are now saved, they weren't before Reviewers: davidedmundson Reviewed By: davidedmundson Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D7912 M +3-0kded/daemon.cpp M +1-0kded/serializer.cpp https://commits.kde.org/kscreen/19e96249d78601d77e022a5ae081be8606ed402e -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 384733] Wayland configs are not saved
https://bugs.kde.org/show_bug.cgi?id=384733 --- Comment #13 from Sebastian Kügler --- Git commit 8719c33eea8f115986990ddfa90de614b8e945ee by Sebastian Kügler. Committed on 21/09/2017 at 13:10. Pushed by sebas into branch 'master'. track the config to monitor, save scale Summary: When doApplyConfig is called, we forgot to change the monitored config, which means we weren't tracking changes anymore. This patch makes sure that the new config becomes the monitored one in that case. Also, save the scale property to the json config, we forgot to do that. Test Plan: Scale changes through kwin are now saved, they weren't before Reviewers: davidedmundson Reviewed By: davidedmundson Subscribers: plasma-devel Tags: #plasma Differential Revision: https://phabricator.kde.org/D7912 M +3-0kded/daemon.cpp M +1-0kded/serializer.cpp https://commits.kde.org/kscreen/8719c33eea8f115986990ddfa90de614b8e945ee -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 384733] Wayland configs are not saved
https://bugs.kde.org/show_bug.cgi?id=384733 --- Comment #11 from Sebastian Kügler --- Git commit 78e8133e934e837ff927673ca6d07218e054c60d by Sebastian Kügler. Committed on 19/09/2017 at 18:27. Pushed by sebas into branch 'sebas/scalechange'. refresh the config after it changed When we get a config change signaled, the internal config may not have updated (when the wayland connection is in process). This means that we may miss changed data. Reloading the config when it changed and only then saving it makes it more robust. I'm not 100% happy about this patch, but tried a lot of things to get the output updated when the backend changes, but it just doesn't happen. With this patch, at least the correct scale value gets written to the config file. M +20 -12 kded/daemon.cpp M +1-0kded/serializer.cpp https://commits.kde.org/kscreen/78e8133e934e837ff927673ca6d07218e054c60d -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 384733] Wayland configs are not saved
https://bugs.kde.org/show_bug.cgi?id=384733 Sebastian Kügler changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #10 from Sebastian Kügler --- Okay, I looked into scalingconfig.cpp, and wondered where the per output scaling went. I did so on a train without much time, which would explain my oversight. I'll have another look. :) -- You are receiving this mail because: You are watching all bug changes.
