[plasmashell] [Bug 481197] When the panel is hidden, a thin blue line is always visible
https://bugs.kde.org/show_bug.cgi?id=481197 --- Comment #5 from Tobias G. --- (In reply to Marco Martin from comment #4) > > *** This bug has been marked as a duplicate of bug 480434 *** Is this really a duplicate? The other bug has a different description -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481197] When the panel is hidden, a thin blue line is always visible
https://bugs.kde.org/show_bug.cgi?id=481197 --- Comment #3 from Tobias G. --- (In reply to fanzhuyifan from comment #1) > There is an effect that only activates when your cursor is near the edge. It > is called screen edge in window management - desktop effects. > > However based on the screenshot the issue you are encountering might be > different. Could you verify if you still see this after turning off this > effect? > > Thanks! I can also confirm that the issue still exist after turning off aforementioned feature. Good that I'm not the only one, my screen is scaled by 150% -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481197] New: When the panel is hidden, a thin blue line is always visible
https://bugs.kde.org/show_bug.cgi?id=481197 Bug ID: 481197 Summary: When the panel is hidden, a thin blue line is always visible Classification: Plasma Product: plasmashell Version: master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 165737 --> https://bugs.kde.org/attachment.cgi?id=165737=edit Screenshot showing blue line SUMMARY I have a floating panel and set it to dodge windows, which works fine. However, when the panel is hidden, a thin blue line is visible at the bottom of the screen where the panel is located (see screenshot) If this behavior is wanted, is there an option to turn this off? STEPS TO REPRODUCE 1. Set panel to floating 2. Set panel to dodge windows 3. Open fullscreen content OBSERVED RESULT There's a blue line at the screen edge where the panel is EXPECTED RESULT There is no indicator at to where the panel is SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240206 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.7.2-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7 ADDITIONAL INFORMATION See Image -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481095] New: After logout, I sometimes have visual glitches
https://bugs.kde.org/show_bug.cgi?id=481095 Bug ID: 481095 Summary: After logout, I sometimes have visual glitches Classification: Plasma Product: kwin Version: git master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY See video. After logout, I sometimes get weird lines and artifacts when elements get redrawn STEPS TO REPRODUCE 1. logout 2. observe 3. OBSERVED RESULT visual artifacts and glitches EXPECTED RESULT no visual artifacts and glitches SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240206 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.7.2-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7 ADDITIONAL INFORMATION I made a video: https://www.youtube.com/watch?v=XMRkRcZUhKw -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481094] New: No kwin scripts are shown to install
https://bugs.kde.org/show_bug.cgi?id=481094 Bug ID: 481094 Summary: No kwin scripts are shown to install Classification: Applications Product: systemsettings Version: master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kwinscripts Assignee: kwin-bugs-n...@kde.org Reporter: tobi.goerg...@gmail.com CC: alexander.loh...@gmx.de, plasma-b...@kde.org Target Milestone: --- SUMMARY I can't install any kwin scripts as the dialog doesn't find any STEPS TO REPRODUCE 1. go to kwin script's settings page 2. search for new scripts online using the inbuilt dialog 3. observe OBSERVED RESULT No scripts can be found EXPECTED RESULT The dalog shows the available scripts SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240206 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.7.2-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7 ADDITIONAL INFORMATION I made a video: https://www.youtube.com/watch?v=pR98oMgRbGw -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 481093] New: When switching the theme, it happens piece by piece and not smoothly
https://bugs.kde.org/show_bug.cgi?id=481093 Bug ID: 481093 Summary: When switching the theme, it happens piece by piece and not smoothly Classification: Plasma Product: kwin Version: git master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY When switching the theme of Plasma, it's done in a choppy way and there's no smooth transition STEPS TO REPRODUCE 1. start settings 2. switch to other theme 3. observe OBSERVED RESULT The theme is switched in "multiple steps" EXPECTED RESULT The theme should be switched in one go and be smoothly animated SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240206 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.7.2-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7 ADDITIONAL INFORMATION I made a video: https://www.youtube.com/watch?v=vHSgbiYwEqE -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 481092] New: Discover doesn't list/show packagekit applications
https://bugs.kde.org/show_bug.cgi?id=481092 Bug ID: 481092 Summary: Discover doesn't list/show packagekit applications Classification: Applications Product: Discover Version: master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PackageKit Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY When searching for an application, only flatpaks are shown, even though the packagekit backend is also installed and updates work fine STEPS TO REPRODUCE 1. open discover 2. search for application 3. only find flatpak OBSERVED RESULT only the flatpak version of applications is found EXPECTED RESULT packagekit applications are shown as well SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240206 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.7.2-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7 ADDITIONAL INFORMATION I made a video: https://www.youtube.com/watch?v=H6Ma2bD-jOE -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 481091] New: Discover doesn't show application on the start page even though packagekit is installed and updates/remove software works
https://bugs.kde.org/show_bug.cgi?id=481091 Bug ID: 481091 Summary: Discover doesn't show application on the start page even though packagekit is installed and updates/remove software works Classification: Applications Product: Discover Version: master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY The start page of discover doesn't show any applications. STEPS TO REPRODUCE 1. start discover 2. wait 3. see error message OBSERVED RESULT I get an hint to check the internet connection EXPECTED RESULT Discover shows applications SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240206 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.7.2-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7 ADDITIONAL INFORMATION I made a video: https://www.youtube.com/watch?v=dLGUt6wYkJs -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 481087] Partiton manager asks two times for password
https://bugs.kde.org/show_bug.cgi?id=481087 Tobias G. changed: What|Removed |Added Platform|Other |openSUSE -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 481087] New: Partiton manager asks two times for password
https://bugs.kde.org/show_bug.cgi?id=481087 Bug ID: 481087 Summary: Partiton manager asks two times for password Classification: Applications Product: partitionmanager Version: Git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY When opened, the partition manager asks two times for the password, which is also acting weird with the fingerprint sensor. When dismissing the second one, one gets asked again STEPS TO REPRODUCE 1. open partiton manager 2. enter first password 3. enter second password OBSERVED RESULT the user is asked two times for a password EXPECTED RESULT the user is only asked once (OR even better: only asked when a privileged action is to be done) SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240206 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.7.2-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7 ADDITIONAL INFORMATION I made a video: https://www.youtube.com/watch?v=uYOuUi1NAyQ -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 481086] New: Fingerprint unlock of screen locker only works after initial failure
https://bugs.kde.org/show_bug.cgi?id=481086 Bug ID: 481086 Summary: Fingerprint unlock of screen locker only works after initial failure Classification: Plasma Product: kscreenlocker Version: git-master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY See video. Often, the fingerprint wouldn't be registered until I enter the wrong password once, only then it accepts the fingerprint STEPS TO REPRODUCE 1. set up fingerprint 2. lock screen 3. try to unlock using fingerprint reader OBSERVED RESULT Screen doesn't unlock EXPECTED RESULT Screen should unlock SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240206 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.7.2-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7 ADDITIONAL INFORMATION I made a video: https://www.youtube.com/watch?v=KmxRadbhnzI -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 481085] New: Battery widget in panel doessn't save "show percent" setting
https://bugs.kde.org/show_bug.cgi?id=481085 Bug ID: 481085 Summary: Battery widget in panel doessn't save "show percent" setting Classification: Plasma Product: kdeplasma-addons Version: git-master Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY The battery widget in the panel has a setting to show the percent in the panel on the symbol. However, after a reboot the percentage is not shown anymore. STEPS TO REPRODUCE 1. activate "show battery percent" in battery/power widget 2. reboot 3. observe OBSERVED RESULT battery percent is not shown anymore EXPECTED RESULT battery percent should still be shown SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240206 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.7.2-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467176] New: Systemd-homed users can't share folders
https://bugs.kde.org/show_bug.cgi?id=467176 Bug ID: 467176 Summary: Systemd-homed users can't share folders Classification: Applications Product: dolphin Version: 22.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: tobi.goerg...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When being logged in as systemd-homed user, one is not able to share folders. While the tab appears in the properties window of a folder, the window remains empty and doesn't show any information. The terminal logs the following error: PermissionsHelper::reload() failed: current user is null qrc:/org.kde.filesharing.samba/qml/main.qml:39: TypeError: Cannot read property 'inSamba' of null When using a non-systemd-homed user, it works as expected. STEPS TO REPRODUCE 1. create systemd-homed user 2. log in with it 3. try to share a folder with dolphin OBSERVED RESULT The share tab is empty EXPECTED RESULT the share tab offers options to share the folder SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Should additional information be required, I'd be happy to provide them :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467145] New: Offline updates are not directly installed when selecting shutdown, but on next boot
https://bugs.kde.org/show_bug.cgi?id=467145 Bug ID: 467145 Summary: Offline updates are not directly installed when selecting shutdown, but on next boot Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Currently, when selecting shutdown with offline updates pending, the system shuts down without installing the updates and the updates are just installed during next boot. Instead, when selecting shutdown and offline updates pending, the system should reboot to install the updates and then shutdown. This way, the system is actually usable when booting it the next time instead of sitting in front of an update screen and not being able to do anything productive and getting as angry on Linux for updating in the worst possible moment as on Windows. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 435845] Option to shut down/restart without applying pending offline updates
https://bugs.kde.org/show_bug.cgi?id=435845 Tobias G. changed: What|Removed |Added CC||tobi.goerg...@gmail.com --- Comment #8 from Tobias G. --- Is there any progress on this? I really hate offline updates in KDE currently, because every simple reboot instantly prevents me from using my computer for updates to install that were not that important to me in this moment. Having an option to let the user choose is, at least for me, vital. This is the very reason I don't use offline updates currently with KDE and can't recommend enabling them. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467142] New: Show open application when trying to close a session
https://bugs.kde.org/show_bug.cgi?id=467142 Bug ID: 467142 Summary: Show open application when trying to close a session Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Currently, when hitting shutdown/reboot/logout in Plasma, the session is simply quitted, no matter what applications are currently running/what their state is. This might lead to users losing unsaved work or long shutdown times (to the maximum defined by systems), due to applications not wanting to quit. This problem could be solved by showing a list of still open applications after pressing shutdown etc. and, in the best case, the user should be prominently warned if an application reports an unsaved state. Plasma should remain active for as long as this list is visible or a timer is running out (e.g. 60 seconds), shutting down/rebooting anyway. The user should have the option to cancel the shutdown or shutdown anyway. In this phase, Plasma could already try to close open applications so the list gets smaller and only really blocking/important applications remain. All applications with an unsaved state should be shown and the issue should be obvious (e.g. with a subtitle stating that there's unsaved work) Other Desktop Environments already support this and this feature could have prevented me from unintentionally losing edited files. The system monitor already supports showing a list of applications, so detecting them and distinguishing them from other processes seems to be possible. In a KDE manner, this feature could be made optional and not enforced to users. Is this a useful feature? What do others think about this? If wanted, I could add a wireframe to visualize what I mean. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 462617] New: Laptop doesn't go into hibernation if in standby for a long time
https://bugs.kde.org/show_bug.cgi?id=462617 Bug ID: 462617 Summary: Laptop doesn't go into hibernation if in standby for a long time Classification: Plasma Product: kscreenlocker Version: 5.26.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Hey there, I use Plasma on a Laptop and selected that it should go into hibernation mode after being in standby mode for a while. While going into hibernation directly, this option doesn't work. The laptop never goes to actual hibernation, but always stays in standby consuming battery constantly. There is also no error message, indicating why it doesn't work (if it was ever triggered) (error messages for failing hibernation would in general be great, rarely I manually want to go into hibernation and it doesn't work (probably full swap file)) And what exactly is "a while"? :D STEPS TO REPRODUCE 1. Activate go into deepleep after a while setting 2. Put your device into standby 3. Observe after "a while" that it hasn't gone into hibernation OBSERVED RESULT Device stays in standby mode EXPECTED RESULT Device goes to hibernation mode SOFTWARE/OS VERSIONS Manjaro Linux stable ADDITIONAL INFORMATION Should any additional information be required, I'd be happy to provide them. :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461615] Workspace only in top left corner with rotated display
https://bugs.kde.org/show_bug.cgi?id=461615 --- Comment #2 from Tobias G. --- Created attachment 153604 --> https://bugs.kde.org/attachment.cgi?id=153604=edit broken setup -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461615] Workspace only in top left corner with rotated display
https://bugs.kde.org/show_bug.cgi?id=461615 --- Comment #1 from Tobias G. --- Created attachment 153603 --> https://bugs.kde.org/attachment.cgi?id=153603=edit correct setup -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461615] Workspace only in top left corner with rotated display
https://bugs.kde.org/show_bug.cgi?id=461615 Tobias G. changed: What|Removed |Added Version|5.24.5 |5.26.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461615] New: Workspace only in top left corner with rotated display
https://bugs.kde.org/show_bug.cgi?id=461615 Bug ID: 461615 Summary: Workspace only in top left corner with rotated display Classification: Plasma Product: kwin Version: 5.24.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Hey there, since the update to Plasma 5.26.2, I sometimes can't interact (after reboot/waking from sleep) with my system as the workspace is only shown in the top left corner of my main screen that I can't interact with (neither in the top left nor where the elements should actually be on the screen) (I attached pictures of what it looks like and what my setup should be). When it happens, it completely disables the rotated screen. Sometimes I can "fix" it by hitting ctrl+alt+F2 and ctrl+alt+F1 again, then it's at least shown correctly on one screen. Enabling and rotating the disabled screen breaks it again, until the timer runs up asking for confirmation of the setup (btw. thanks for adding it). I can, however, mostly make it work again by first activating the screen and confirming it and then rotating it. Should any additional information be required, I'd be happy to help :) STEPS TO REPRODUCE 1. have rotated screen 2. reboot 3. observe OBSERVED RESULT the rotated display is turned off and the workspace shown in one corner EXPECTED RESULT The rotated screen is turned on and confirgured correctly SOFTWARE/OS VERSIONS Betriebssystem: Manjaro Linux KDE-Plasma-Version: 5.26.2 KDE-Frameworks-Version: 5.99.0 Qt-Version: 5.15.6 Kernel-Version: 5.15.75-xanmod1-1.1-lts (64-bit) Grafik-Plattform: X11 Prozessoren: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Speicher: 23,4 GiB Arbeitsspeicher Grafikprozessor: NVIDIA GeForce GTX 1080/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 433495] Lock screen greeter fails to visually update when system is woken up while connected to TV via receiver
https://bugs.kde.org/show_bug.cgi?id=433495 --- Comment #6 from Tobias G. --- Sorry for the late reply, this issue seems to be fixed now :) Should it ever happen again, I'll reopen this bug report -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 451232] Broken font rendering in wayland
https://bugs.kde.org/show_bug.cgi?id=451232 --- Comment #7 from Tobias G. --- Hey there, I tested a few things and I noticed that all my text looks broken, when I disable font smoothing (disabling anti-aliasing). Might it be that it's not applied everywhere for some reason on my system? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454871] New: (SDDM) Login screen doesn't save rotation of screen
https://bugs.kde.org/show_bug.cgi?id=454871 Bug ID: 454871 Summary: (SDDM) Login screen doesn't save rotation of screen Product: kwin Version: 5.24.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Hey there, I've tried in the past few hours to make SDDM save the rotation of my screens, as one is rotated by 90°. But unfortunately, SDDM just doesn't want to do that. I've tried to synchronize the settings in wayland and X11, but the log in screen always has the wrong orientation. Am I missing something? PS: I couldn't find SDDM as module to open this bug, so I opened it here, I hope that's OK. STEPS TO REPRODUCE 1. rotate display by 90° 2. sync settings with login screen 3. log out OBSERVED RESULT SDDM is not rotated by 90° EXPECTED RESULT SDDM should be rotated by 90° SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 23.4 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454630] Add support for System76 scheduler
https://bugs.kde.org/show_bug.cgi?id=454630 --- Comment #2 from Tobias G. --- (In reply to David Edmundson from comment #1) > This is out of scope Are you sure? I don't really know what would have to be done, but there is a kwin script that does exactly that. AFAIK, KWin "just" has to tell the scheduler which window is curently focussed to increase it's niceness. The script can be found here: https://store.kde.org/p/1789957 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 454627] Add support for face unlock
https://bugs.kde.org/show_bug.cgi?id=454627 --- Comment #2 from Tobias G. --- (In reply to Phos from comment #1) > Hey Tobias, you might want to check out Howdy > https://github.com/Boltgolt/howdy Hi, thank you, I already heard of Howdy. :) Unfortunately, it doesn't have a graphical interface for setup, requires manual configuration and users have to search for it manually. It would be way more convenient if KDE included this natively. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454642] New: automatically hidden panel inaccessible using touch screen
https://bugs.kde.org/show_bug.cgi?id=454642 Bug ID: 454642 Summary: automatically hidden panel inaccessible using touch screen Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Hey guys, whenever I set a plasma/latte panel or dock to auto hide, the dock is not accessible anymore using the touchscreen. Moving with the finger to the edge doesn't make the panel appear. This happens with the default plasma panels or panels/docks added using Latte. STEPS TO REPRODUCE 1. add panel to workspace 2. set panel to auto-hide 3. try to make it visible using touch screen OBSERVED RESULT panel stays hidden EXPECTED RESULT panel should appear SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics Memory: 7.2 GiB of RAM Graphics Processor: AMD RENOIR ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 454641] New: "Edit dock/panel" button unreliable in wayland session
https://bugs.kde.org/show_bug.cgi?id=454641 Bug ID: 454641 Summary: "Edit dock/panel" button unreliable in wayland session Product: lattedock Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Hey guys, in a wayland session, the "Edit dock/panel" button works very unreliable. Either, the blue background is shown for a short time, but then disappears and I have to open it again or the menu opens for half a second and latte crashes or it just opens normally. This doesn't happen in X11 STEPS TO REPRODUCE 1. start latte 2. right click on dock 3. hit "Edit dock/panel" button OBSERVED RESULT the menu is not always shown, but latte crashes or the menu is closed after half a second EXPECTED RESULT the menu opens and waits for input SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics Memory: 7.2 GiB of RAM Graphics Processor: AMD RENOIR ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 454640] New: Unable to use context menu when app preview is enabled on wayland
https://bugs.kde.org/show_bug.cgi?id=454640 Bug ID: 454640 Summary: Unable to use context menu when app preview is enabled on wayland Product: lattedock Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Hey guys, on wayland, I'm unable to use the context menu if prior to that the preview window is shown (by hovering over an opened application). The context menu is opened with a right click, as soon as one moves out of the preview window, not only the preview is closed, but also the context menu, making it tricky/impossible to use it in that case. STEPS TO REPRODUCE 1. start wayland session and latte 2. enable window preview on hover 3. right click on opened app 4. try to access context menu OBSERVED RESULT the context menu is closed with the preview EXPECTED RESULT the preview is closed, but the context menu stays open SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics Memory: 7.2 GiB of RAM Graphics Processor: AMD RENOIR ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454632] New: Add energy modes to energy applet
https://bugs.kde.org/show_bug.cgi?id=454632 Bug ID: 454632 Summary: Add energy modes to energy applet Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Hey guys, it would be nice if the energy applet showed the option to change the system's behavior, e.g. a battery saving mode, underclocking CPU/GPU and reducing the display brightness, a balanced mode (normal) and a performance mode with more aggressive clocking. This would give the users the opportunity to decide on their own, whether they prefer battery life or performance, based on the current situation. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454631] New: Add context menu to run application using dGPU
https://bugs.kde.org/show_bug.cgi?id=454631 Bug ID: 454631 Summary: Add context menu to run application using dGPU Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Hey there, it would be nice if KDE Plasma showed a menu entry in the context menu for applications to run them using a dGPU on systems, where it is supported. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454630] New: Add support for System76 scheduler
https://bugs.kde.org/show_bug.cgi?id=454630 Bug ID: 454630 Summary: Add support for System76 scheduler Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Hey guys, System76 developed a scheduler with better responsiveness for their system. It would be great if KDE Plasma also supported the scheduler out of the box, to deliver the best experience. The repo can be found here: https://github.com/pop-os/system76-scheduler -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454629] New: System hangs in Plymouth splash screen
https://bugs.kde.org/show_bug.cgi?id=454629 Bug ID: 454629 Summary: System hangs in Plymouth splash screen Product: kwin Version: 5.24.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Hey guys, sometimes (1/3 times), when starting my system, I never see Plasma, but instead, the plymouth splash screen is shown endlessly spinning. Nothing happens then, I can prevent that by hitting an F key early, then Plasma is starting reliably. I haven't tested it with Plasma 5.24.5 yet, but it happened on 5.24.4. It also just happened with wayland sessions so far. STEPS TO REPRODUCE 1. boot system into wayland session 2. observe plymouth OBSERVED RESULT plymouth is shown endlessly EXPECTED RESULT plymouth is terminated and Plasma is shown SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics Memory: 7.2 GiB of RAM Graphics Processor: AMD RENOIR ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 454628] New: Add option to hide session options
https://bugs.kde.org/show_bug.cgi?id=454628 Bug ID: 454628 Summary: Add option to hide session options Product: kdeplasma-addons Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Application Dashboard Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Hey there, It would be nice if the application dashboard had an option to hide the session menu (with poweroff, reboot, etc.). Currently, this is not possible. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 454627] New: Add support for face unlock
https://bugs.kde.org/show_bug.cgi?id=454627 Bug ID: 454627 Summary: Add support for face unlock Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcheckpass Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY Hey there, it would be nice if Plasma supported unlocking the screen/logging in using face unlock, similar to how fingerprint unlock works. This could either only work with infrared-cams or with "Normal" cams as well, though they might not be as secure. Executing root commands should also be possible using it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454626] New: screen turns on again when switching to hibernation
https://bugs.kde.org/show_bug.cgi?id=454626 Bug ID: 454626 Summary: screen turns on again when switching to hibernation Product: kwin Version: 5.24.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Hey guys, whenever I put my PC in hibernation, the screen turns off for a few seconds, then turns on again with just the lock screen clock and mouse cursor visible to then turn off again and actually go into hibernation. The screen shouldn't turn on again though, but should stay turned off. This might not be a wayland-specific bug. STEPS TO REPRODUCE 1. start wayland session 2. start hibernation mode 3. observe screen OBSERVED RESULT screen turns on again for a short time EXPECTED RESULT screen stays turned off SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics Memory: 7.2 GiB of RAM Graphics Processor: AMD RENOIR ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454455] KDE applications should have more descriptive names
https://bugs.kde.org/show_bug.cgi?id=454455 --- Comment #6 from Tobias G. --- (In reply to Ömer Fadıl USTA from comment #4) > Hello Tobias G. , whenever you log in you can use alt f2 or alt space > shortcut to reach > applications fast and in there whenever you write file it will directly > show you dolphin > whenever you type terminal it will show you konsole whenever you type scan > it will show you skanlight > ( this behavior is same in search box in start menu ) > > As Nate mentioned it will be big problem if these applications named like > Files or Terminal also you are missing > non-english language users than Files might be meaningless for them when > they see it doesnt it ? > Also it is same in market when you get in shop you ask for coca-cola even > you ask salesman direcly as coke s/he > will bring you coca-cola/pepsi but the label still will be not coke Yes, that's true, though, for example my father is a mouse-centric desktop user - he doesn't search for files to find the file manager, but he looks in the menu and scrolls through it looking for an application with that name. That's also a reason why more visible descriptions won't completely solve the issue - my father still wouldn't find the application, he doesn't want to read all app descriptions to find what he needs. Names in desktop entries can be translated, so that wouldn't be a problem. :) The analogy also works for me - the application menu shows "Files" as name of the application (you ask for the coke) and Dolphin is opened (he brings you a pepsi). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454455] KDE applications should have more descriptive names
https://bugs.kde.org/show_bug.cgi?id=454455 --- Comment #5 from Tobias G. --- (In reply to Nate Graham from comment #3) > I can understand the issue that the subtitle/description is easy to > overlook. Let's focus on that, since I don't think we're going to move in > the direction of giving our apps boring generic names. > > I have an open merge request to move the subtitle/description to below the > main text, rather than off to the side: > https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/699 > > You can see the before-and-after images to visualize the proposed change. Do > you think that would make made things more obvious to your mom? Or better > yet, could you show it to her and ask? And the other people too? > > If the answer is yes, I would very much appreciate it if you could leave a > supportive comment on > https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/699. :) > > > They also told me that some apps need better defaults to be usable > Can you open separate bug reports for specific issues with the default > settings for our apps? Thanks! Yes, my family members think that showing the description under the title would be better, though a more descriptive name would be optimal. :) The apps could this be called the way they are called now, "just change the desktop files" to show "Files" instead of Dolphin and maybe in the title bar. This way, the apps can keep their creative names internally, while still having descriptive names. :) I'll leave a positive comment later! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454625] New: System hangs when using stylus after some time/when sharing the screen in firefox
https://bugs.kde.org/show_bug.cgi?id=454625 Bug ID: 454625 Summary: System hangs when using stylus after some time/when sharing the screen in firefox Product: kwin Version: 5.24.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Hey there, I notice regularly when writing with my stylus pen (which is exceptionally good supported btw) that my system freezes after some time. I use RNote to take notes and at some point, just nothing happens anymore, the clock in my dock doesn't update and I can't interact with my system in any way anymore. I unfortunately don't know which logs are required, but maybe I'm not the only one with this issue. I haven't tested it on X11 (writing there is garbage) Alternatively, sharing the screen with firefox might also be the issue. I enabled native wayland rendering and when I write, I usually share my screen with my partner. This might also cause the crash, it didn't crash when using chromium to share the screen when I remember correctly and this is way easier to test :) STEPS TO REPRODUCE 1. start wayland session 2. write with stylus/share screen in firefox 3. wait for hang OBSERVED RESULT the whole system hangs, nothing responds to anything anymore, I need to restart EXPECTED RESULT The system keeps on responding SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 6 × AMD Ryzen 5 4500U with Radeon Graphics Memory: 7.2 GiB of RAM Graphics Processor: AMD RENOIR ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454455] KDE applications should have more descriptive names
https://bugs.kde.org/show_bug.cgi?id=454455 Tobias G. changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Tobias G. --- (In reply to Nate Graham from comment #1) > If we did this, then anytime you have both Dolphin and Nautilus installed, > your application menu would have two apps named "Files". That wouldn't be > great. > > KDE apps already list their descriptions. For example Gwenview has text > beside it that says "KDE image viewer". Did yo not notice this? Or you did > notice it, but it wasn't enough? That's a point, it wouldn't be great. But, is having two having the same name, but with different icon in a hypothetical scenario worth the tradeoff of users not knowing what the app does (I've let a few non digital-natives try plasma to get their point of view and this was one thing they noticed). Yes, the app description says that it's a file manager, but the description is way smaller than the title and way easier to overlook and my mom for example didn't notice them. So yes, they are (in what I found out) not enough. They also told me that some apps need better defaults to be usable (e.g. Kontakt and KDE's mail app is really not user friendly using the default settings and overwhelming, as well as all customizablility options directly visible in the settings app with confusing categories not always holding what they expected) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454455] New: KDE applications should have more descriptive names
https://bugs.kde.org/show_bug.cgi?id=454455 Bug ID: 454455 Summary: KDE applications should have more descriptive names Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Hey there, I know this is not the right category, but I don't know where to put it, so I placed it here. If you know a better component, feel free to move it there. :) I'm regularly testing other desktop environments to see how they develop and one thing I noticed and really liked about GNOME is that applications seem to have very descriptive names in general. For example, the file explorer is called "Files", the terminal "Terminal" and the scan application "Document scanner". In plasma, this is not the case. The file explorer is called "Dolphin", the terminal is called "Konsole" and the document scanner is called "Skanlight". How should an inexperienced user know that Dolphin is a file manager, other than looking on the icon and trying? I think, I wouldn't. GNOME's file manager also has an internal name, Nautilus. But it's not exposed to the user directly. I think Plasma should do this as well. Use descriptive, direct names throughout the DE, to make it easier accessible for new users. What are your thoughts? Are there any explicit reasons why not to do that? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 451490] [startup] latte docks dodge void at boot
https://bugs.kde.org/show_bug.cgi?id=451490 --- Comment #4 from Tobias G. --- (In reply to Michail Vourlakos from comment #1) > (In reply to Tobias G. from comment #0) > > SUMMARY > > Hey there, > > > > I'm using Latte and have set it to dodge active windows. However, whenever I > > start the system and no window is active > > why on startup no window is possible? you mean that there is no window shown? Oh, I'm so sorry for just answering now. The issue doesn't seem to appear anymore, so I guess it's resolved. :) Should it appear again, I'll reopen this bug with more detailed information. :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445449] Shutting down from Plasma Wayland causes shutdown to be delayed while stopping SDDM
https://bugs.kde.org/show_bug.cgi?id=445449 Tobias G. changed: What|Removed |Added CC||tobi.goerg...@gmail.com --- Comment #27 from Tobias G. --- I also have this issue with Plasma 5.24.3 on Manjaro, using the wayland session and kernel 5.16 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451235] right click menu entries not readable in wayland
https://bugs.kde.org/show_bug.cgi?id=451235 --- Comment #3 from Tobias G. --- (In reply to Nate Graham from comment #2) > Are you using menu transparency? If so, does the issue go away if you make > menus opaque again? Yes, I'm using transparency, no, it doesn't go away when making it opaque again :( -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451232] Broken font rendering in wayland
https://bugs.kde.org/show_bug.cgi?id=451232 --- Comment #4 from Tobias G. --- (In reply to Nate Graham from comment #3) > And it doesn't happen with anything in Plasma itself, right? Like text in > Kickoff of the Task Manager or icons on the desktop? No, neither in kickoff, icons on the desktop nor in the task manager in the panel. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451293] [wayland] graphical issues after standby mode
https://bugs.kde.org/show_bug.cgi?id=451293 --- Comment #5 from Tobias G. --- Created attachment 147678 --> https://bugs.kde.org/attachment.cgi?id=147678=edit Example 3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451293] [wayland] graphical issues after standby mode
https://bugs.kde.org/show_bug.cgi?id=451293 --- Comment #4 from Tobias G. --- Created attachment 147677 --> https://bugs.kde.org/attachment.cgi?id=147677=edit Example 2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451293] [wayland] graphical issues after standby mode
https://bugs.kde.org/show_bug.cgi?id=451293 --- Comment #3 from Tobias G. --- Created attachment 147676 --> https://bugs.kde.org/attachment.cgi?id=147676=edit Example 1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451293] [wayland] graphical issues after standby mode
https://bugs.kde.org/show_bug.cgi?id=451293 --- Comment #2 from Tobias G. --- (In reply to Nate Graham from comment #1) > Can you attach a screenshot that shows some of these graphical issues? > > Does it happen in the X11 session, or only with Wayland? It never happened in the X11 session (I use standby regularly and have also switched back to X11 already), just in wayland. While trying to "provoke" the issue (setting PC to standby) I also managed to get no screen at all after waking the PC, not even the mouse was visible. In the second attempt I managed to get the issue I'm talking about, but it seems like not all letters are missing, just most of them, for example "8" and "f" work fine, but most others don't. I guess my PC just forgot how to write lol -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451232] Broken font rendering in wayland
https://bugs.kde.org/show_bug.cgi?id=451232 --- Comment #2 from Tobias G. --- (In reply to Nate Graham from comment #1) > Does it go away if you restart the affected app? > > Does it affect QtWidgets apps like Dolphin? Unfortunately, it doesn't go away after restarting the app and it doesn't happen with Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 451218] [wayland] instant crash at startup (nvidia)
https://bugs.kde.org/show_bug.cgi?id=451218 Tobias G. changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 451490] New: Latte docks dodge void at boot
https://bugs.kde.org/show_bug.cgi?id=451490 Bug ID: 451490 Summary: Latte docks dodge void at boot Product: lattedock Version: 0.10.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Hey there, I'm using Latte and have set it to dodge active windows. However, whenever I start the system and no window is active, Latte hides all docks, until I click on the workspace, which makes the Latte docks appear again and behave normally. Can this be confirmed? STEPS TO REPRODUCE 1. set Latte to dodge active windows 2. restart system 3. observe OBSERVED RESULT All latte docks dodge the void EXPECTED RESULT Latte docks stay visible until an actual window appears SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.11-2-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 23.4 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 451236] can't select a pipewire display or window to record in wayland (obs)
https://bugs.kde.org/show_bug.cgi?id=451236 Tobias G. changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from Tobias G. --- (In reply to Nicolas Fella from comment #1) > For me this works okay (except that it reacts poorly to double clicks, see > https://bugs.kde.org/show_bug.cgi?id=451240). I can click on an item and > then click the "Share" button. > > The actual recording doesn't work on my Nvidia system but works on my Intel > system, but that's a different issue OK, I restarted the system, now it works - I don't know what caused it, still weird. But at least now "fixed" I guess :D -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451293] New: [wayland] graphical issues after standby mode
https://bugs.kde.org/show_bug.cgi?id=451293 Bug ID: 451293 Summary: [wayland] graphical issues after standby mode Product: plasmashell Version: 5.24.2 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Hey guys, I noticed that after putting my pc to sleep and waking it again leads to severe graphical issues, with e.g text not being visible in the application menu anymore. STEPS TO REPRODUCE 1. Start wayland session 2. Put pc to standby 3. Wake pc OBSERVED RESULT Graphical issues EXPECTED RESULT No graphical issues SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.11-2-MANJARO (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 23.4 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 ADDITIONAL INFORMATION I didn't know which component's fault it is, so I just put it in the general category, sorry. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451236] New: can't select a pipewire display or window to record in wayland (obs)
https://bugs.kde.org/show_bug.cgi?id=451236 Bug ID: 451236 Summary: can't select a pipewire display or window to record in wayland (obs) Product: plasmashell Version: 5.24.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Hey there, I recently switched from X11 to Wayland and tried to record my screen using obs, it showed the option to record a window or display using pipewire, it also asks me to select a screen, but unfortunately, I can't interact with it. I can't select an entry, not with the mouse nor the keyboard. Since the dialog looks very plasma-ish and also shows a kde logo in the top left, I suspected it was a KDE dialog. I have an nvidia graphics card using proprietary drivers STEPS TO REPRODUCE 1. start a wayland session 2. open obs 3. try to select a display or window to record OBSERVED RESULT can't interact with the screen/window selection window EXPECTED RESULT can select window / screen SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.11-2-MANJARO (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 23.4 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 ADDITIONAL INFORMATION I didn't know which component's fault it is, so I just put it in the general category, sorry. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 451218] [wayland] instant crash at startup (nvidia)
https://bugs.kde.org/show_bug.cgi?id=451218 --- Comment #6 from Tobias G. --- (In reply to Michail Vourlakos from comment #4) > This is KScreen applet crash under wayland that is hosted probably in the > systray. > If you close Latte, add a default plasma panel and relogin dont you have the > same crash? I just noticed that executing "latte-dock -d --default-layout " brings up a dock that works, I can't add a panel or dock though -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451235] New: right click menu entries not readable in wayland
https://bugs.kde.org/show_bug.cgi?id=451235 Bug ID: 451235 Summary: right click menu entries not readable in wayland Product: plasmashell Version: 5.24.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 147348 --> https://bugs.kde.org/attachment.cgi?id=147348=edit invisible right-click-menu SUMMARY Hey there, I recently switched from X11 to wayland and noticed that right-click-menus' renderings are broken, as soon as I hover over an entry every other entry becomes invisible. I have to hover over every entry to make them visible again. I have an nvidia graphics card and use the proprietary drivers. I attached a screenshot where I hovered over the first two elements. STEPS TO REPRODUCE 1. right click somewhere 2. hover over an element 3. observe OBSERVED RESULT other entries disappear EXPECTED RESULT all entries stay visible SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.11-2-MANJARO (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 23.4 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 ADDITIONAL INFORMATION I didn't know which component's fault it is, so I just put it in the general category, sorry -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451234] multi monitor with different scale factor breaks workspace and wallpaper alignment in wayland
https://bugs.kde.org/show_bug.cgi?id=451234 --- Comment #1 from Tobias G. --- Created attachment 147347 --> https://bugs.kde.org/attachment.cgi?id=147347=edit broken workspace had to make it a jpeg, so transparency is gone -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451234] New: multi monitor with different scale factor breaks workspace and wallpaper alignment in wayland
https://bugs.kde.org/show_bug.cgi?id=451234 Bug ID: 451234 Summary: multi monitor with different scale factor breaks workspace and wallpaper alignment in wayland Product: plasmashell Version: 5.24.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Hey there, I recently switched from X11 to wayland and noticed that sometimes on startup of my system the "workspace" and wallpaper of my secondary monitor is broken. I noticed that when selecting a field on the display (so the bluish field appears you can drag), I can't actually enter the black area. My left display is rotated by 90° and set to 125% scale, my right display is 0° rotated and has a scale factor of 100%. I can "fix" it by setting the left display to 100% as well and back to 125%. I have an nvidia graphics card and use proprietary drivers STEPS TO REPRODUCE 1. switch to wayland 2. set two displays to different scale factors 3. restart machine OBSERVED RESULT workspace is broken on scaled display EXPECTED RESULT workspace should be fine SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.11-2-MANJARO (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 23.4 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 ADDITIONAL INFORMATION I didn't know which component's fault it is, so I just put it in the general category, sorry -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 451232] New: Broken font rendering in wayland
https://bugs.kde.org/show_bug.cgi?id=451232 Bug ID: 451232 Summary: Broken font rendering in wayland Product: plasmashell Version: 5.24.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 147344 --> https://bugs.kde.org/attachment.cgi?id=147344=edit bad font rendering example SUMMARY Hey there, I recently switched from x11 to wayland. I have two displays, one turned by 90° (Display 1), one oriented normally (Display 0). Display 0 is set to 100% scale, Display 1 to 125% scale. In some places, like the system settings window, fonts are broken (see attachment), which really makes it hard to read it. Ironically, it's especially bad in the font settings of plasma :D I own an nvidia graphics card with proprietary drivers. STEPS TO REPRODUCE 1. switch to wayland 2. set two displays to different scale factors 3. try to read text OBSERVED RESULT Font is partly unreadable EXPECTED RESULT font looks clear as water SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.11-2-MANJARO (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 23.4 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 ADDITIONAL INFORMATION I wasn't sure which component's fault it is, so I just put it in the general category, sorry -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 451218] [wayland] instant crash at startup (nvidia)
https://bugs.kde.org/show_bug.cgi?id=451218 --- Comment #5 from Tobias G. --- (In reply to Michail Vourlakos from comment #4) > This is KScreen applet crash under wayland that is hosted probably in the > systray. > If you close Latte, add a default plasma panel and relogin dont you have the > same crash? oh, that's interesting. I already added a default plasma panel, before running these latte commands (as I wouldn't have any panel at all otherwise) So, with default Plasma panel -> crash -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 451218] [wayland] instant crash at startup (nvidia)
https://bugs.kde.org/show_bug.cgi?id=451218 --- Comment #3 from Tobias G. --- Created attachment 147343 --> https://bugs.kde.org/attachment.cgi?id=147343=edit backtace -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 451218] [wayland] instant crash at startup (nvidia)
https://bugs.kde.org/show_bug.cgi?id=451218 Tobias G. changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Tobias G. --- (In reply to Michail Vourlakos from comment #1) > https://userbase.kde.org/LatteDock/HowToReportCrashes Oh sorry, I've attached a picture of the backtrace window. It doesn't really seem to be a crash, but latte just "hangs" endlessly and never shows up. I also ran the other command listed on the website. Here's the output of env QV4_FORCE_INTERPRETER=1 latte-dock -d: https://pastebin.com/dtrbhTtn -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 451218] New: [wayland] instant crash at startup (nvidia)
https://bugs.kde.org/show_bug.cgi?id=451218 Bug ID: 451218 Summary: [wayland] instant crash at startup (nvidia) Product: lattedock Version: 0.10.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Hey there, I recently switched from x11 to wayland, but latte always either crashes when trying to start it or when trying to creaste a new panel. Here's the log: https://pastebin.com/7bBQhS6t I have an nvidia GTX 1080 with proprietary graphics drivers installed and I'm on Plasma 5.24.2 on Manjaro. I already tried to delete the config folder of latte. Should any additional information be required, I'd be happy to help! STEPS TO REPRODUCE 1. start Plasma in wayland session 2. try to start latte-dock 3. observe OBSERVED RESULT latte crashes EXPECTED RESULT latte doesn't crash SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.11-2-MANJARO (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 23.4 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445416] Dolphin keeps asking for credentials of Windows share
https://bugs.kde.org/show_bug.cgi?id=445416 Tobias G. changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REOPENED|RESOLVED --- Comment #13 from Tobias G. --- (In reply to Alex Levkovich from comment #10) > No one is going to fix a thing, right? I'd like to hear an answer from a > responsible person. Hey there, good news! I managed to open a bug report here: https://bugzilla.samba.org/show_bug.cgi?id=14935 And there's a commit merged into master already that fixes the issue, the shares are accessible again! :) We have to wait until samba 4.16 though or build from master. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445416] Dolphin keeps asking for credentials of Windows share
https://bugs.kde.org/show_bug.cgi?id=445416 --- Comment #12 from Tobias G. --- (In reply to Alex Levkovich from comment #10) > No one is going to fix a thing, right? I'd like to hear an answer from a > responsible person. I'm in contact with a samba dev via email, hoping that a bug report on their side will be created as it seems to be an issue in libsmb -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445416] Dolphin keeps asking for credentials of Windows share
https://bugs.kde.org/show_bug.cgi?id=445416 Tobias G. changed: What|Removed |Added Resolution|WORKSFORME |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #11 from Tobias G. --- I have to re-open this bug, as it stopped working for me; icu has been updated to a version not supported by samba 4.13, so I had to update samba as well. This is still an issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446594] New: Wallpaper sets to black with two screens connected via Displayport
https://bugs.kde.org/show_bug.cgi?id=446594 Bug ID: 446594 Summary: Wallpaper sets to black with two screens connected via Displayport Product: plasmashell Version: 5.23.3 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Image Wallpaper Assignee: notm...@gmail.com Reporter: tobi.goerg...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Hey there, I have two 4k displays connected via Displayport, one is rotated by 90 degrees, the other one is my main display. Sometimes, after I turned off both screens, the lockscreen activated, I turned the displays on again and unlocked the workspace, the wallpaper of the left, rotated display just sets to the color black (or is reset to the default one, then this is is shown in the wallpaper settings). The wallpaper settings menu shows that my actual wallpaper is still selected and I can't set it, I have to set another wallpaper and then the desired one again. I use X11. STEPS TO REPRODUCE 1. Turn off both screen connected via DP with lockscreen 2. Turn them on again and unlock the workspace 3. Have a look at the left display OBSERVED RESULT Wallpaper is reset or black EXPECTED RESULT Wallpaper remains unchanged SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 21.10 (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Should any further information or logs be required, I'd be happy to help! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 446592] New: Lockscreen offset with two displays
https://bugs.kde.org/show_bug.cgi?id=446592 Bug ID: 446592 Summary: Lockscreen offset with two displays Product: kscreenlocker Version: 5.23.3 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com CC: bhus...@gmail.com Target Milestone: --- SUMMARY Hey there, I have two 4k displays connected via Displayport, one is rotated by 90 degrees, the other one is my main display. It happens more often than not that when both screen were off, the lockscreen activates and the displays are being turned on again, the lockscreen shows correctly on the left one, but is offset on the right one, with only about one quarter showing the lockscreen (its offset to the top left, so that in the top left corner the bottom right part of the lockscreen is visible). I can unlock it normally and the actual workspace is shown normally. I'm using X11. STEPS TO REPRODUCE 1. Turn off via DP connected displays 2. Wait for lockscreen to turn on 3. Observe OBSERVED RESULT The lockscreen is offset EXPECTED RESULT The lockscreen is shown normally SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 21.10 (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Should any additional information or logs be required, I'd be happy to help! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446591] New: Workspace icons rearrange at display reconnect
https://bugs.kde.org/show_bug.cgi?id=446591 Bug ID: 446591 Summary: Workspace icons rearrange at display reconnect Product: plasmashell Version: 5.23.3 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: tobi.goerg...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Hey there, I have two 4k displays connected via Displayport, one is rotated by 90 degrees, the other one is my main display. It happened multiple times already that after turning off both displays and on again, the icons I ordered manually on my workspace rearrange themselves, appending icons in a second / third etc. road after the first one. I have similar issues when changing the display resolution to something smaller than the icons need to be displayed (e.g. when starting games for the first time at low resolution, which should be another issue, but might get solved here as well). My guess is that the PC forgets about the displays and when reconnected, arranged the icons again, changing the order. (just a guess though, but I see my display flickering beforehand). This issue might get solved by saving the icon layout and, if the resolution changes / displays get disconnected and reconnected, the icon layout is restored, if no changes have been made to them in the meantime. STEPS TO REPRODUCE 0. Arrange icons on workspace manually in multiple rows 1. Turn off display connected via DP 2. Turn it on again 3. Observe OBSERVED RESULT Icons are rearranged EXPECTED RESULT Previous layout should be kept SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 21.10 (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Should any logs or additional information be required, I'd be happy to help! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445559] Add "minimal" mode showing only essential options
https://bugs.kde.org/show_bug.cgi?id=445559 --- Comment #2 from Tobias G. --- (In reply to Nate Graham from comment #1) > I'm afraid we explicitly don't want to do this. See > https://community.kde.org/Get_Involved/Design/Lessons_Learned#Basic. > 2Fadvanced_modes for the reasons why. > > We will have to come up with another way to make things seem simpler. Thank you very much for the answer and the link! It's great to know that you also think that things have to seem simpler (as you've also written on your blog). Unfortunately, I can't think of a way to preserve all features visible, without it seeming bloated or complex, even if it just was a list of simple checkboxes. One question to the lessons to be learned though: There's stated that users with a big ego might use an "advanced" mode, even though the basic mode would fit them better. I think to use this as an argument is difficult for 2 reasons, including the exact opposite reason: The plasma environment seems pretty complex now for new users, as it lacks such a basic/advanced options, so all users are forced currently to see all options (which would then be the advanced mode), but have no option to switch to a simpler mode. So the exact opposite of what feared there happens right now, inexperienced users without a big ego are forced to look through everything and might be afraid to change something as it seems complex. In my opinion, this is even worse, as users don't even have a chance to make the system seem simpler. Also, this only is an issue if a naming scheme of basic/advanced was used. Naming it e.g. normal/extra might not trigger the big ego issue. This would also help unexperienced users help use the advanced set, as they are only labeled "extra" and not advanced, so it might take their fear to activate/use them. Also, with the work being done on the welcome screen that's currently being developed, it could be explained there what these two modes do and that one does not need to be afraid of activating these options, but also stating that new users of Plasma might be more comfortable with the normal set and how to change to them. It could also be shown in an example, which options are typical to be found in the normal set and which in the extra one. The only other argument is that some users might think an option should be in the normal category and others would think it's an extra option. This issue would be applicable to every approach solving this, as some options HAVE to be more prominent and others will HAVE to be more hidden in some way or another, to take away the complexity just resulting from seeming to be bloated. So yeah, that's every argument made in the lessons to be learned on why this should not be used. I think / hope that this approach has been discussed before and should there have been any other arguments, I'd be happy to address them. As I see the situation currently, solving this issue creates other issues that, because of the nature of a theoretical fix, would always apply to every possible solution and the current situation has its own issue that's costing plasma, as you stated, the majority of the potential user base out there. Also, because of this, I think that this is a severe problem that has to be solved ASAP, to make sure that KDE actually gets to dominate the world. ;) Otherwise, other projects might evolve, that address this issue, might it be GNOME or anything else, just because those can be used by inexperienced users, sacrificing customizebility. This approach would not. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445555] Add alternative layouts as easily selectable options
https://bugs.kde.org/show_bug.cgi?id=44 --- Comment #2 from Tobias G. --- (In reply to Nate Graham from comment #1) > We explicitly decided not to do this; see https://phabricator.kde.org/T11743. Hey there, thank you very much for linking the discussion! Is it still open or has it been decided once and for all? Also, are the "lessons to be learned" fixed and will never change again or is there any ongoing discussion about them? Not, because I can't see why these choices have been made, but I think that not all options have been evaluated eventually. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 445557] KIO doesn't work with smbclient > 4.13
https://bugs.kde.org/show_bug.cgi?id=445557 --- Comment #4 from Tobias G. --- (In reply to Harald Sitter from comment #3) > smbclient uses a different code base from libsmbclient which makes it not > nearly surprising that one works when the other does not. I'm sorry, but why is this an upstream issue now? -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 445557] KIO doesn't work with smbclient > 4.13
https://bugs.kde.org/show_bug.cgi?id=445557 Tobias G. changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|UPSTREAM|--- Ever confirmed|0 |1 --- Comment #2 from Tobias G. --- (In reply to Harald Sitter from comment #1) > Sounds like https://bugzilla.samba.org/show_bug.cgi?id=14326 > > I do rather feel like the problem is on the windows side though cause I also > didn't manage to make it work from windows 10 to another windows 10 Yes and no. As described in the linked bug report, smbclient asks me for a password, but lets me access it nonetheless with anything entered as username and password. KIO accepts until version 4.13 the windows PC name and anything as password, with smbclient > 4.13 nothing works. I can verify this since 4.15 was pre-installed on my machine and manually compiled 4.13, which made it work. It's also not an issue on Windows machines, they just don't ask me for a password at all. So yes, the bug applies here too, as it asks me for credentials, but it's not the only bug here, as KIO doesn't seem to allow access to unprotected Windows shares at all anymore. The Windows machines have a specific setup, as a local account without user password is in use instead of a Microsoft account, SMB1 is activated and password-less shares are activated. Accessing a Windows share with a Microsoft account and it's credentials works fine. Most of what I've written above is already stated in the linked bug report, with another user having an issue with KIO and smbclient > 4.13, so it might be worth a look. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445559] New: Add "minimal" mode showing only essential options
https://bugs.kde.org/show_bug.cgi?id=445559 Bug ID: 445559 Summary: Add "minimal" mode showing only essential options Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Hey there, as I noticed, what's loved about desktop environments like GNOME is it's simplicity and that it's not fearing users by the shear number of available settings. To make KDE more appealing to new users, KDE should feature a "minimal mode", where only essential options are shown. While this takes flexibility from the user, it adds simplicity that's desired by not few users. This option should e.g. only show one "theme" setting, that only changes the global theme, as this is the only essential option in this category, every other theme option is set when changing the global theme. Everything else should be hidden in this mode from the user (though the "extended" mode showing all options can always be activated ofc) This should be applied to every settings category, really questioning if the shown setting is essential to a new user or if actions can be simplified and more obvious what they actually change. The general scheme of the settings should not be changed, as this might confuse users, if they activate the "extended mode" and all settings are at a different place. For example, there should still be settings to configure which applications show notifications, but maybe not exactly, which notifications of an application will come through. Or hiding the setting for the position of the notification completely and showing it always next to the notification icon. Another example might be the compositor setting: would your grandma know what this setting is for and wouldn't be feared to change it? Mine would be, she wouldn't know what it is and also not care, so why show it to hear and frighten her. This mode should in a next step also be included in KDE applications respecting this setting, only making the really necessary configurable and everything else rely on defaults, This could e.g. mean that the position of the dock might be changeable, but not how tall it is or how transparent it is. This could also have the effect that applications make sure that their defaults are user-friendly and the application is easily usable at first start without the user having to fiddle around, making the desktop more polished and removing papercuts, making our all lives easier. The drawback of course is that the dev has to care about the defaults, though that should be the case anyway. I don't think that an argument like "it's hiding functionality from the user" is applicable here, as a) that's the intention of this option and b) it's only optional. For example, every application could feature a prominent option to switch to "minimal mode" / "extended mode" instantaneously. Also, a "welcome app" is currently in the works, that could ask at first start "Hey, are you a new user? Use this simple mode making your life easier. Are you an experienced user? Use the extended mode with more functionality" This mode could also mean that the system monitor hides the "processes" page in minimal mode, making sure the user doesn't accidentally closes system processes but shows the applications page listing the open applications. Or Dolphin not showing hidden folders starting with a dot, as these folders mostly contain folders and inexperienced users probably don't need to access them. If they still do, they can easily enable the "extended mode" and bam, there's an option to show hidden folders. Or they google, find the hint to press ctrl+h to show them. What should dolphin do? Show a prompt saying "Hey, you're trying to show hidden folders. To do this, you have to enter the extended mode. Are you sure?" Inexperienced users will then know that what they do doesn't seem to be trivial and will think about this again. But whey still have the choice to still show it. All in all, with this setting we protect the system from the user, as it's not that easily possible to do something harmful anymore and the user is protected from the system, as he's not overwhelmed by the amount of available settings. The applications will get saner defaults with a better focus on usability out-of-the-box, while also making Plasma more accessible to new users who can get to know plasma's features, power and flexibility step-by-step. Any thoughts, critics or recommendations are always welcome! -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 445557] New: KIO doesn't work with smbclient > 4.13
https://bugs.kde.org/show_bug.cgi?id=445557 Bug ID: 445557 Summary: KIO doesn't work with smbclient > 4.13 Product: kio-extras Version: 21.08.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Samba Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com CC: sit...@kde.org Target Milestone: --- SUMMARY As discussed here https://bugs.kde.org/show_bug.cgi?id=445416 KIO doesn't work properly on systems with smbclient > 4.13 installed. This leads to network shares not being accessible anymore. STEPS TO REPRODUCE 1. install smbclient > 4.13 and KDE Plasma Desktop 2. try to access a samba shares with specific config OBSERVED RESULT access to share not possible EXPECTED RESULT share should be accessed as on smbclient < 4.14 SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445416] Dolphin keeps asking for credentials of Windows share
https://bugs.kde.org/show_bug.cgi?id=445416 Tobias G. changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #9 from Tobias G. --- (In reply to Alex Levkovich from comment #7) > Created attachment 143564 [details] > modified pkgbuild re-building the package actually fixed the issue for me, so this really is at least a workaround, until the issue is fixed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445556] New: add way to export current settings
https://bugs.kde.org/show_bug.cgi?id=445556 Bug ID: 445556 Summary: add way to export current settings Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Migrating from one system to another would be way easier, if KDE featured an option to export the configuration of the current system settings. Obviously, this should not include hardware-specific configurations like network or sound configuration and security-relevant configurations like the firewall (though these might be optional via opt-in). This export feature should include all settings but the following: - Users (obviously) - KDE-password-storage (optional) - online-access (optional) - backups (optional?) - all settings of the network category (though e.g. firewall might be optional) - everything of the hardware-category (though energy-settings might be optional) - software updates (might be a security / stability issue?) Every option remaining should be de-selectable or selectable, if only partial exports are wanted. Selected themes should either be included as a link to the theme that's then downloaded or optionally directly in the export-file, without the need to download it (might be useful if themes are not available anymore) It might also be worth a thought if every KDE program should include such an option, saving all exports in one specific location, making it possible to export the configuration of the system and the used programs, that's ones imported on another system (recognizing, which settings config belongs to which program) and applying the configuration once making a new installation of a highly customized system way easier. This approach also spreads the responsibility for this feature, so that plasma's system settings doesn't have to include the export logic for all KDE programs, but every application is responsible on it's own. Importing settings should also be handled on a per-application level, so that system settings would only forward the to-be-imported settings to the application, which itself applies the settings (so that system settings only works like a "hub" connecting the config export-and-import functionality of the applications, only calling them to export their config or import it, though it might be smarter if the export is handled actually on a per-application-level and only the import is triggered on one place of the system. This could also include the feature on supported systems to install applications, which have a config file to be restored that's not installed on the system, making the configuration of a new system even faster, maybe including an option to export a list of installed applications that should be exported as well. Settings that potentially include personal information should be disabled by default. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445555] New: Add alternative layouts as easily selectable options
https://bugs.kde.org/show_bug.cgi?id=44 Bug ID: 44 Summary: Add alternative layouts as easily selectable options Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_desktoptheme Assignee: plasma-b...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Hey there, I noticed that KDE Plasma ships with one default layout (the dock at the bottom) and nothing else, other layouts have to be configured manually. As I think that most of the users would use one of the following layouts, I think it would be useful to add them as easily selectable options: - Windows-like (current default) - MacOS-like - GNOME-like - Unity-like This could also include an option to add custom layouts and make them visible there as well. Customizing one of the default layouts automatically creates a custom layout. This menu could look like on Zorin-OS (https://bit.ly/3FiPa0e) or feren OS (https://bit.ly/3HzVfay) AFAIk this already kind of exists, as global themes can ship with a custom layout; but this has some disadvantages: - custom layouts are not available in a default installation - unexperienced users might overlook the checkbox at the bottom and might wonder why the layout changed / didn't change as intended - layouts can't be distributed independent of global themes - easier accessibility and better understanding of how applying new layouts work Global themes could still also include a custom layout, but just as window decoration or the cursor, the layout should also be selectable independently. As said, this would also allow users to upload layouts without also having to include a complete global theme. This feature would also have to have a way to register panels, also by third-party-software like latte-dock, so that these docks are saved as well (though I think there already is an interface for other applications to tell kwin that they added a panel?) I think this whole idea would remove another small papercut from the KDE shell, as I, a user of KDE for about 5 years now, only learned today that global themes come with a layout (or I might just be exceptionally blind and dumb to not understand how this works :D) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445416] Dolphin keeps asking for credentials of Windows share
https://bugs.kde.org/show_bug.cgi?id=445416 --- Comment #8 from Tobias G. --- (In reply to Alex Levkovich from comment #5) > ok, I get out my accusations about quality of PKGBUILD. It seems both waf > and xsltproc do not like russian symbols in the path. So when I put PKGBUILD > in completely english subdir it worked. So if someone needs the temporary > fix: just recomple the older version. Uh thank you very much for your detailed explanation and the work you put into this! Do you know if KDE devs are working on getting KIO ready for this version / where one can track the development? I'll test your workaround and see if it solves my issue. BTW. Where do you know anyway that kio has issues with smbclient versions > 4.13? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445416] Dolphin keeps asking for credentials of Windows share
https://bugs.kde.org/show_bug.cgi?id=445416 --- Comment #3 from Tobias G. --- (In reply to Alex Levkovich from comment #1) > KDE's kio does not work with smbclient > 4.13. > That's the reason. > Could you please fix this? And thank you for your answer! :) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445416] Dolphin keeps asking for credentials of Windows share
https://bugs.kde.org/show_bug.cgi?id=445416 --- Comment #2 from Tobias G. --- (In reply to Alex Levkovich from comment #1) > KDE's kio does not work with smbclient > 4.13. > That's the reason. > Could you please fix this? Yeah, as I see, Manjaro currently provides 4.15. How can I fix it though? 樂 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445416] New: Dolphin keeps asking for credentials of Windows share
https://bugs.kde.org/show_bug.cgi?id=445416 Bug ID: 445416 Summary: Dolphin keeps asking for credentials of Windows share Product: dolphin Version: 21.08.3 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: tobi.goerg...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Hey guys, When I'm trying to access a share created on Windows 10 that doesn't require a login, I'm not able to access it. Dolphin keeps asking me for credentials, but doesn't accept anything. I've tried entering the username of the Linux system, the username of windows, the PC name of the windows machine and guest. Nothing worked. Interestingly though, I'm able to login to a PC that is password protected, entering the credentials there works just fine. It's very unlikely an issue of my samba configuration, as I can use smbclient - L //IP/share to list the share (though it also asks me for a password, but it accepts anything) and mount - t cifs //IP/share /mnt/share also works fine and is then accessible via Dolphin, but this is unfortunately not a suitable solution for me. I'm using Manjaro and followed this guide here that created a samba config file: https://wiki.manjaro.org/index.php/Using_Samba_in_your_File_Manager I think it's interesting to mention that this issue happens on Manjaro Linux, but not on Kubuntu. On Kubuntu, it also asks me for credentials (which is pretty weird), but accepts the windows pc name with any password. I've made sure that the systems are in the same domain. I've tried everything I could to rule out that it's a manjaro issue, by e.g. copying the samba config file from Kubuntu to Manjaro, with no change in behavior. The fact that I can mount the shares via cifs also makes me confident that it's an issue on the KDE side. STEPS TO REPRODUCE 1. Boot manjaro live media or install manjaro 2. Try to access a windows share 3. See dolphin asking you for credentials over and over OBSERVED RESULT No credentials are accepted EXPECTED RESULT It shouldn't ask me for credentials at all or accept anything SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Should any logs or config files be required, I'd be happy to provide them! I can also create a video showing my issue -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444269] include keyfile of root partition in initramfs if offline updates are pending
https://bugs.kde.org/show_bug.cgi?id=444269 --- Comment #1 from Tobias G. --- with this should come that new options to the power actions of kickoff are added, respectively "update and shutdown" and "update and reboot". The keyfile should only be included if the user chooses one of those options. "update and shutdown" should then reboot the pc, install the updates and then poweroff, before the poweroff though the keyfile is removed again, so that the password has to be entered again at next boot. This should be equivalent to "update and reboot". If only shutdown or reboot are hit, the system should actually only be rebooted or shutdown without installing updates and without adding the keyfile to initramfs -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444269] include keyfile of root partition in initramfs if offline updates are pending
https://bugs.kde.org/show_bug.cgi?id=444269 Tobias G. changed: What|Removed |Added Version|5.22.2 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 444269] New: include keyfile of root partition in initramfs if offline updates are pending
https://bugs.kde.org/show_bug.cgi?id=444269 Bug ID: 444269 Summary: include keyfile of root partition in initramfs if offline updates are pending Product: Discover Version: 5.22.2 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Updates (offline) Assignee: lei...@leinir.dk Reporter: tobi.goerg...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY I'm using KDE Plasma on an encrypted root partition. When I activate offline updates, I have to enter the passphrase to install them and then to start my system normally. Instead, a systemd service could store the keyfile of the root partition temporarily in the initramfs, install the update and remove the keyfile again after installing the updates. This way, I don't have to enter my password just to install the required updates. This should be an optional feature though as it might be a security concern for some users. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 436924] become aware of offline updates and offer opt out
https://bugs.kde.org/show_bug.cgi?id=436924 --- Comment #8 from Tobias G. --- What I've done so far can be found here: https://github.com/TobiPeterG/kubuntu_automatic_updates -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 436924] become aware of offline updates and offer opt out
https://bugs.kde.org/show_bug.cgi?id=436924 --- Comment #7 from Tobias G. --- (In reply to David Edmundson from comment #5) > Can we be a lot more sparing with the "VHI" flag. It has already become > completely meaningless. > > In terms of logout order of events is: > > - user clicks button in kickoff this makes a DBus call > - This DBus call auto-activates logout-greeter, this shows a prompt > > - On clicking confirm it makes a new DBus call > - This DBus call auto-activates a helper binary called plasma-shutdown > > - This binary calls into ksmserver to ask apps to quit (which they can > cancel) > > > logout-greeter is the only visual one, though it's worth pointing out it can > be skipped and the call in kickoff can go straight to plasma-shutdown based > on user preferences. Hi there, I'm working on a custom script to update my system at shutdown. The script itself is working, but it needs to be called before shutdown. I already tried to create a systemd script, but systemd shuts down services the script needs before it finishes, but I don't know which exactly are required. So, I had the idea to get the shutdown call by Plasma to redirect it to my script. Replacing the plasma-shutdown executable with my script worked, but it's also called when the system is rebooted. Is there any way to make the script just being called at shutdown? Which command is sent by plasma that actually shuts down the system? Do you know that? I'd be glad if you could help me here! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 443041] New: Use systemd's new A/B update scheme
https://bugs.kde.org/show_bug.cgi?id=443041 Bug ID: 443041 Summary: Use systemd's new A/B update scheme Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Updates (offline) Assignee: lei...@leinir.dk Reporter: tobi.goerg...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Systemd released version 249, which introduces a new update method using A/B partition schemes. KDE should work on using it (though it sounds like an OS-level feature, so KDE probably can't support it allone, but needs an OS supporting it. See https://github.com/systemd/systemd/releases/tag/v249 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 442696] New: Kscreen / kwin doesn't use xrandr settings
https://bugs.kde.org/show_bug.cgi?id=442696 Bug ID: 442696 Summary: Kscreen / kwin doesn't use xrandr settings Product: KScreen Version: 5.22.90 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- SUMMARY Hey there, I'm trying to split a display I use in two virtual ones. xrandr has a command for that (tutorial can be found here: https://chipsenkbeil.com/notes/linux-virtual-monitors-with-xrandr/ or https://askubuntu.com/questions/150066/split-monitor-in-two/998435#998435 But using these changes doesn't affect my workspace at all. I hope I selected the correct package STEPS TO REPRODUCE 1. Use xrandr to split your display in two 2. observe 3. OBSERVED RESULT the one display is still one EXPECTED RESULT the display should be seperated in two SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 441367] New: Add greeter to Plasma
https://bugs.kde.org/show_bug.cgi?id=441367 Bug ID: 441367 Summary: Add greeter to Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Desktop Containment Assignee: notm...@gmail.com Reporter: tobi.goerg...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY It would be nice if Plasma had a greeter that showed up at first boot after installation, introducing new users to the most important features / workflow AND is shown after Plasma updates, showing what's new in Plasma, making it way more easy to find out what changed and what is newly possible. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375951] locally integrated menus
https://bugs.kde.org/show_bug.cgi?id=375951 Tobias G. changed: What|Removed |Added CC||tobi.goerg...@gmail.com --- Comment #54 from Tobias G. --- Is there any progress on this feature as I would like to see this implemented as well -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441364] New: Show users programs that prevent system from shutting down
https://bugs.kde.org/show_bug.cgi?id=441364 Bug ID: 441364 Summary: Show users programs that prevent system from shutting down Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: tobi.goerg...@gmail.com Target Milestone: --- Created attachment 140947 --> https://bugs.kde.org/attachment.cgi?id=140947=edit shut down confirmation deepin SUMMARY It would be nice if Plasma would warn users when they're trying to shut down the system, even though one or more programs are still running and preventing the system from shutting down. The warning should then also have a force quit button, that kills the process and shuts the system down, hopefully eliminating "endlessly long" (1:30min) taking shut downs, because a process is still running. This also prevents the user from losing unsaved documents without their knowledge. This should be shown at shut down and reboot. A screenshot of how this is handled by Deepin is attached -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438932] Offline updates still used, even though explicitly deactivated
https://bugs.kde.org/show_bug.cgi?id=438932 --- Comment #8 from Tobias G. --- (In reply to Nate Graham from comment #7) > The entry disappears when you turn it off because that's the default value; > this is standard behavior for config files across all KDE software. I wonder > if Kubuntu uses true as its own default such that having no value in the > config file falls back to true and gives you offline updates again. > > Can you try adding > > [Software] > UseOfflineUpdates=false > > to your config file and see if that works? I tried that, but it still used offline updates when it updated my system. :( I really can't understand why now... -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438932] Offline updates still used, even though explicitly deactivated
https://bugs.kde.org/show_bug.cgi?id=438932 --- Comment #6 from Tobias G. --- (In reply to Aleix Pol from comment #5) > Can you check that your system isn't setting the PK_OFFLINE_UPDATE > environment variable? Checked it, using $ env | grep PK_OFFLINE_UPDATE but no output, so that doesn't seem to be the case either. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438932] Offline updates still used, even though explicitly deactivated
https://bugs.kde.org/show_bug.cgi?id=438932 --- Comment #4 from Tobias G. --- (In reply to Aleix Pol from comment #3) > Weeeird. > > Can you see what's on the config file? "$ cat .config/discoverrc" > > You should have something like: > > [Software] > UseOfflineUpdates=false It shows me this when deactivated: $ cat .config/discoverrc [FlatpakSources] Sources=flathub-beta,flathub [Window] geometry=2501,1006,933,597 visibility=2 when activated this: $ cat .config/discoverrc [FlatpakSources] Sources=flathub-beta,flathub [Software] UseOfflineUpdates=true [Window] geometry=2501,1006,933,597 visibility=2 It is really strange that the entry just completely disappears, when deactivated, instead of being set to false. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438932] Offline updates still used, even though explicitly deactivated
https://bugs.kde.org/show_bug.cgi?id=438932 --- Comment #2 from Tobias G. --- (In reply to Aleix Pol from comment #1) > Can you confirm that "kreadconfig5 --file discoverrc --group Software --key > UseOfflineUpdates" returns false on your system? I cannot confirm that, when I activate the offline option, it returns true. But when I deactivate it, it just returns nothing. So that might be the issue I guess. :D -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439318] Automatically discovered, but removed printers reappear instantly again
https://bugs.kde.org/show_bug.cgi?id=439318 Tobias G. changed: What|Removed |Added Summary|Automatically, but removed |Automatically discovered, |discovered printers |but removed printers |reappear instantly again|reappear instantly again -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439318] New: Automatically, but removed discovered printers reappear instantly again
https://bugs.kde.org/show_bug.cgi?id=439318 Bug ID: 439318 Summary: Automatically, but removed discovered printers reappear instantly again Product: systemsettings Version: 5.22.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_printer_manager Assignee: dantt...@gmail.com Reporter: tobi.goerg...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY Hey guys, the printer manager automatically discovered printers in my network (which is great), but doesn't use the correct driver by default (which is not so great), but the worst thing is that every time I remove the printer (by pressing on "remove printer"), the printer just reappears again, bloating my printer menu with printers I can't use, since they don't work correctly / of printers I don't use. Even automatically recognized printers should stay removed, as they could easily be re-added when needed and it's just confusing that they reappear and might lead to confusion on what printer to use for an inexperienced user (the badly configured driver is a different story here) STEPS TO REPRODUCE 1. have a printer in the network that can be discovered 2. remove it from the printer list 3. wait for half a second OBSERVED RESULT the removed printer reappears EXPECTED RESULT the removed printer stays removed Operating System: Kubuntu 21.04 KDE Plasma Version: 5.22.2 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-23-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 23.4 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 439317] New: Add support for the DUR
https://bugs.kde.org/show_bug.cgi?id=439317 Bug ID: 439317 Summary: Add support for the DUR Product: Discover Version: 5.22.2 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: tobi.goerg...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY Hey there, the DUR (Debian User Repository) was announced a few days ago as Debian's alternative to the AUR. It would be really cool, if Discover added support for installing packages using the DUR in the future on Debian based systems. -- You are receiving this mail because: You are watching all bug changes.
