[plasma-systemmonitor] [Bug 447497] New: KDE Plasma Widgets Blank on RPi4
https://bugs.kde.org/show_bug.cgi?id=447497 Bug ID: 447497 Summary: KDE Plasma Widgets Blank on RPi4 Product: plasma-systemmonitor Version: git-stable-Plasma/5.22 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: itsmah...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 144851 --> https://bugs.kde.org/attachment.cgi?id=144851=edit System Monitor app without sensor data! SUMMARY On a fresh installation Manjaro KDE Plasma on Raspberry Pi 4 Model B is not working system monitor. Its blank. Not showing any available sensors! STEPS TO REPRODUCE 1. Open Plasma System Monitor. Or 2. Add a system sensor widget to desktop. SOFTWARE/OS VERSIONS Manjaro ARM KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 384039] KConfig::groupList() returns deleted group
https://bugs.kde.org/show_bug.cgi?id=384039 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kconfig/-/merge_requests/95 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447496] New: Plasmoids are drawn 1px above panel, makes weird gap
https://bugs.kde.org/show_bug.cgi?id=447496 Bug ID: 447496 Summary: Plasmoids are drawn 1px above panel, makes weird gap Product: plasmashell Version: 5.23.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: doncb...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 144850 --> https://bugs.kde.org/attachment.cgi?id=144850=edit The wallpaper is visible between the panel and the open calendar SUMMARY The 1px separator line that separates plasmoids from the panel does not look good with other themes. Other themes show an awkward gap between the panel and the plasmoid. STEPS TO REPRODUCE 1. Choose a theme other than Breeze (e.g. Oxygen) 2. Open a plasmoid (e.g. Kickoff) 3. OBSERVED RESULT There is a 1px gap between the plasmoid and the panel EXPECTED RESULT It seems to be better hidden on Breeze. I expect a line to be drawn (ideally if the theme designer wanted it) with the panel and plasmoid connected continuously. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I think dialog.svg with line.svg on top would better support themes. Moving the separator line to the header and footer may be a better choice, though much more complicated. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447251] When qt5-qdbusviewer isn't installed, pressing in "Launch D-Bus Browser" button needs to show a prompt to install qt5-qdbusviewer
https://bugs.kde.org/show_bug.cgi?id=447251 Photon changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 447495] New: Add a shortcut in Discover settings to open System Settings > Software Update
https://bugs.kde.org/show_bug.cgi?id=447495 Bug ID: 447495 Summary: Add a shortcut in Discover settings to open System Settings > Software Update Product: Discover Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: ncqm3...@anonaddy.me CC: aleix...@kde.org Target Milestone: --- It might help in terms of feature discoverability. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446713] Settings app error or crash when getting more theming components.
https://bugs.kde.org/show_bug.cgi?id=446713 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 447248] KDE Partition Manager delays for several minutes on Intel RAID/NTFS volume scan
https://bugs.kde.org/show_bug.cgi?id=447248 --- Comment #10 from Ihor --- (In reply to Andrius Štikonas from comment #9) > This should at least fix lag of several minutes. > > But I'm not sure what it does to RAID size. Could you test this commit? Tested Git commit a5bdd5a4eb44607fed3b0318ee64cc4f15abb122: Startup now takes about 3-4 seconds! But total size check is still broken. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444328] "Shows textual list" pop-out does not disappear after selecting task on wayland
https://bugs.kde.org/show_bug.cgi?id=444328 Fushan Wen changed: What|Removed |Added Status|ASSIGNED|CONFIRMED --- Comment #9 from Fushan Wen --- I am not using Wayland now because it's hard to debug on Wayland. Anyone who wants to fix the bug can freely take over it. There is a detailed description in https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/391 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445561] Krita 5 16bit integer colorspace canvas rendering is broken on M1
https://bugs.kde.org/show_bug.cgi?id=445561 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #21 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1259 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447494] Swatch highlights and their denoting swatch name often aren't updated accordingly on color selection
https://bugs.kde.org/show_bug.cgi?id=447494 --- Comment #1 from tomtomtomreportin...@gmail.com --- Couple more cases: * There is no swatch highlight nor an appropriate swatch name when selecting a new workspace. * There is no swatch highlight when selecting another document. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447494] New: Swatch highlights and their denoting swatch name often aren't updated accordingly on color selection
https://bugs.kde.org/show_bug.cgi?id=447494 Bug ID: 447494 Summary: Swatch highlights and their denoting swatch name often aren't updated accordingly on color selection Product: krita Version: 5.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: tomtomtomreportin...@gmail.com Target Milestone: --- SUMMARY It is often a bit annoying to use the palette docker, especially with palettes using many similar colors, due to the fact that swatch highlights and the name of the currently highlighted swatch aren't updated accordingly in at least a few cases. This is not a regression of Krita 5. Some cases I've noticed: * There is no swatch highlight nor an appropriate swatch name denoted in the palette docker when starting Krita. * There is no swatch highlight in the palette docker when creating a new image. * The current swatch name isn't updated when selecting a new color through a method outside of the palette docker (e.g. color picking or using the color selector). * (Perhaps intentional) There is no swatch highlight nor a corresponding swatch name denoted when selecting a new palette. Some of these cases also affect the color selector dialog. STEPS TO REPRODUCE: 1. Select Default palette. 2. Select Black 0%. 3. Restart Krita. 4. Observe the palette docker. OBSERVED RESULT There is no swatch highlight and the Amazon swatch is denoted despite not being selected nor highlight. EXPECTED RESULT Black 0% should be highlighted and denoted as it's the selected color. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian sid KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.12.12 (appimage) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445719] Stack Smashing Crash
https://bugs.kde.org/show_bug.cgi?id=445719 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #202 from Maxim Egorushkin --- (In reply to Kevin Kofler from comment #201) > Well, the thing is, Qt does not actually use the system-wide locales, i.e., > glibc/POSIX locales. What it does is map the glibc locale to a Unicode > locale and then use that with ICU and/or with bundled copies of Unicode > tables within Qt. So just inventing a glibc locale would not fix it, because > it would not map to anything in Qt. And the tables in Qt are hardcoded and > cannot be extended at runtime. > > IMHO, the whole QLocale system should be thrown away / ignored / blacklisted > (just like, e.g., QHttp) and KDE code ported to a resurrected KLocale (based > on the old kdelibs 3 code, not on QLocale) instead. I am not sure if begging open-source developers ever worked, because someone has to pay the work, unless the developer wants to make a name with changes for themselves, which could be a quite tall order here. Would you like to spec the changes, as well as time and money required to materialize those changes? Or anyone else still listening to this conversation? With that we can try crowdfunding the change and see what happens? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447446] Fade transition with ken burns panning generates jumping images
https://bugs.kde.org/show_bug.cgi?id=447446 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Platform|Other |Ubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414121] taskbar freezes if window title updates frequently
https://bugs.kde.org/show_bug.cgi?id=414121 Fushan Wen changed: What|Removed |Added Version Fixed In||5.24 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425284] Generate Video Slideshow - Failed to open Muxer
https://bugs.kde.org/show_bug.cgi?id=425284 caulier.gil...@gmail.com changed: What|Removed |Added Version|7.0.0 |7.3.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414121] taskbar freezes if window title updates frequently
https://bugs.kde.org/show_bug.cgi?id=414121 Fushan Wen changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/commit/1d ||612571c43b23cf829edfdae8eb7 ||970812b5a32 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #7 from Fushan Wen --- Git commit 1d612571c43b23cf829edfdae8eb7970812b5a32 by Fushan Wen. Committed on 25/12/2021 at 01:11. Pushed by fusionfuture into branch 'master'. taskmanager: Only update the task label when visible When the task label is not visible, we should not bind text to model.display. This is expected to slightly reduce the power consumption in daily usage. M +11 -1applets/taskmanager/package/contents/ui/Task.qml https://invent.kde.org/plasma/plasma-desktop/commit/1d612571c43b23cf829edfdae8eb7970812b5a32 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 447360] KMail crashes on startup when it can't authenticate account
https://bugs.kde.org/show_bug.cgi?id=447360 ewag...@disroot.org changed: What|Removed |Added CC||ewag...@disroot.org -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 447360] KMail crashes on startup when it can't authenticate account
https://bugs.kde.org/show_bug.cgi?id=447360 --- Comment #1 from ewag...@disroot.org --- Created attachment 144849 --> https://bugs.kde.org/attachment.cgi?id=144849=edit New crash information added by DrKonqi kmail (5.19.0 (21.12.0)) using Qt 5.15.2 - What I was doing when the application crashed: Emails would not load, but titles were listed. Attempted to view different emails, none would load. Kmail crashed. Reproduced issue multiple times. - Custom settings of the application: Default settings except for unchecking 'Download all messages for offline use' on my email accounts. -- Backtrace (Reduced): #4 0x7ffbae89cb39 in QAction::setText(QString const&) () at /usr/lib/libQt5Widgets.so.5 #5 0x7ffbb6e0caae in KMMainWidget::updateFolderMenu() () at /usr/lib/libkmailprivate.so.5 #6 0x7ffbb6e17ca6 in KMMainWidget::setupActions() () at /usr/lib/libkmailprivate.so.5 #7 0x7ffbb6e1d731 in KMMainWidget::KMMainWidget(QWidget*, KXMLGUIClient*, KActionCollection*, QExplicitlySharedDataPointer const&) () at /usr/lib/libkmailprivate.so.5 #8 0x7ffbb6dc6bd4 in KMMainWin::KMMainWin(QWidget*) () at /usr/lib/libkmailprivate.so.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #201 from Kevin Kofler --- Well, the thing is, Qt does not actually use the system-wide locales, i.e., glibc/POSIX locales. What it does is map the glibc locale to a Unicode locale and then use that with ICU and/or with bundled copies of Unicode tables within Qt. So just inventing a glibc locale would not fix it, because it would not map to anything in Qt. And the tables in Qt are hardcoded and cannot be extended at runtime. IMHO, the whole QLocale system should be thrown away / ignored / blacklisted (just like, e.g., QHttp) and KDE code ported to a resurrected KLocale (based on the old kdelibs 3 code, not on QLocale) instead. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #200 from Maxim Egorushkin --- I did my +1 to this bug in 2016, and this issue appeared to be trivial at the time for me, a fellow (naive) C++ developer, and a big fan of KDE Plasma. It is a bit hard for me to fathom that such a seemingly trivial issue, not even a bug but oversight in my eyes, couldn't be fixed easily. The comments here suggest that the issue stems from a design oversight, in that KDE Plasma is incapable of using user defined time/date formats independently of a system-wide locale. Could there be an option to create another system-wide locale which forks an existing locale, but overrides date-time format (and other formats, if desired), and could be used by KDE Plasma? May be a locale that overrides date-time formats with ISO ones? I wanted to take a look into this issue but couldn't find easy guides how to check out KDE Plasma source, build it, and run it without destroying my existing KDE Neon desktop environment. That was in 2016, may be things changed for better since then. This is a rather annoying and unexpectedly difficult bug for the most configurable DE, IMO, which is KDE Plasma. It didn't prevent me from doing my tasks though, I can still sort by date asc/desc in Dolphin and that works as expected. The dates and times don't look ISO-well-formed, but Dolphin does sort by the timestamp correctly, and that's usable enough. Elsewhere, I use: * In `bash`: `alias ll="ls -al --time-style=long-iso --block-size=\'1"` * In `emacs`: `(custom-set-variables ... (dired-listing-switches "-al --time-style=long-iso --block-size='1") ... )` -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland
https://bugs.kde.org/show_bug.cgi?id=447337 --- Comment #19 from Andrey --- (In reply to Conrad from comment #18) > turn on sets it to 0, turn off sets it to 1. Exactly like this, not the otherwise? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447204] Task manager offers to launch new instance of kcmshell and systemsettings
https://bugs.kde.org/show_bug.cgi?id=447204 Nicolas Fella changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||c58e5433436393e2b437ccb34f3 ||75b5aacb6419c Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Nicolas Fella --- Git commit c58e5433436393e2b437ccb34f375b5aacb6419c by Nicolas Fella. Committed on 25/12/2021 at 00:11. Pushed by nicolasfella into branch 'master'. [libtaskmanager] Prevent launching a new instance of services with NoDisplay=true It is not possible for the user to launch such an app from the UI, so we should not allow to launch a new instance from the task manager context menu. M +15 -0libtaskmanager/tasktools.cpp https://invent.kde.org/plasma/plasma-workspace/commit/c58e5433436393e2b437ccb34f375b5aacb6419c -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447493] New: Crash on load of jpg
https://bugs.kde.org/show_bug.cgi?id=447493 Bug ID: 447493 Summary: Crash on load of jpg Product: krita Version: 4.4.8 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: ajv-393-919-5...@vsta.org Target Milestone: --- Created attachment 144848 --> https://bugs.kde.org/attachment.cgi?id=144848=edit Backtrace SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Load this specific jpg OBSERVED RESULT kde aborts EXPECTED RESULT show jpg? SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Debian Buster (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Actual jpg available to dev if needed, but contains personal information so not attached here -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447492] New: Thumbnails for a given recent project are only generated once per session
https://bugs.kde.org/show_bug.cgi?id=447492 Bug ID: 447492 Summary: Thumbnails for a given recent project are only generated once per session Product: krita Version: 5.0.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: tomtomtomreportin...@gmail.com Target Milestone: --- SUMMARY Thumbnails for recent projects are only generated once per session, as in, they do not properly update when the user saves changes for an already saved recent project. They will only update when the user initially saves the image or starts a new Krita session. This does not apply to the file picker thumbnails. It seems to only apply to the Welcome Screen thumbnails and File -> Open Recent thumbnails. STEPS TO REPRODUCE 1. Create a new image. 2. Make one stroke and save the image. 3. Observe thumbnail in File -> Open Recent. 4. Make another stroke and save. 5. Observe thumbnail in File -> Open Recent. OBSERVED RESULT The thumbnail in step 3 is still being used. EXPECTED RESULT There should be a new thumbnail from the modifications made in step 4, without having to restart Krita. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian sid KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.12.12 (appimage) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447491] No plugins were loaded ...
https://bugs.kde.org/show_bug.cgi?id=447491 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Version|7.5.0 |7.4.0 Version Fixed In||7.5.0 Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447491] No plugins were loaded ...
https://bugs.kde.org/show_bug.cgi?id=447491 --- Comment #3 from Christoph --- Thank you for the quick information. I had version 7.4. Now with version 7.5 everything is ok. Merry Christmas and best wishes for 2022 -Ursprüngliche Nachricht- Von: bugzilla_nore...@kde.org Gesendet: Freitag, 24. Dezember 2021 23:00 An: merz.ch...@freenet.de Betreff: [digikam] [Bug 447491] No plugins were loaded ... https://bugs.kde.org/show_bug.cgi?id=447491 --- Comment #1 from caulier.gil...@gmail.com --- Did you use really digiKam 7.5.0 release ? Because we have already fixed this problem in pre-release bundle available here : https://files.kde.org/digikam/ See bug already fixed #447013 Gilles Caulier -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447491] No plugins were loaded ...
https://bugs.kde.org/show_bug.cgi?id=447491 --- Comment #2 from caulier.gil...@gmail.com --- https://bugs.kde.org/show_bug.cgi?id=447013 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447491] No plugins were loaded ...
https://bugs.kde.org/show_bug.cgi?id=447491 --- Comment #1 from caulier.gil...@gmail.com --- Did you use really digiKam 7.5.0 release ? Because we have already fixed this problem in pre-release bundle available here : https://files.kde.org/digikam/ See bug already fixed #447013 Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447491] No plugins were loaded ...
https://bugs.kde.org/show_bug.cgi?id=447491 caulier.gil...@gmail.com changed: What|Removed |Added Component|Plugins-Interface |Geolocation-Marble Platform|Other |Microsoft Windows CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439297] "Apply" button of Application Style KCM is unnecessarily activated after change in application style settings
https://bugs.kde.org/show_bug.cgi?id=439297 Nate Graham changed: What|Removed |Added Version Fixed In||5.23.5 Severity|normal |minor -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439297] "Apply" button of Application Style KCM is unnecessarily activated after change in application style settings
https://bugs.kde.org/show_bug.cgi?id=439297 Nate Graham changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/ |bdebc4d246698b43e4182b0ebe9 |46fde8e84cbeb0a4cf7c1ee65f9 |a94b7d6780d60 |81e8ef8a4e046 --- Comment #4 from Nate Graham --- Git commit 46fde8e84cbeb0a4cf7c1ee65f981e8ef8a4e046 by Nate Graham, on behalf of Nicolas Fella. Committed on 24/12/2021 at 21:55. Pushed by ngraham into branch 'Plasma/5.23'. [kcms/style] Don't call setNeedsSave when style config changes The style config is saved already when the dialog closes so enabling the KCM apply button doesn't make sense The comment suggests that this is done for a reason, but the style preview seems to refresh correctly even with this patch (cherry picked from commit bdebc4d246698b43e4182b0ebe9a94b7d6780d60) M +0-3kcms/style/kcmstyle.cpp https://invent.kde.org/plasma/plasma-workspace/commit/46fde8e84cbeb0a4cf7c1ee65f981e8ef8a4e046 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439297] "Apply" button of Application Style KCM is unnecessarily activated after change in application style settings
https://bugs.kde.org/show_bug.cgi?id=439297 Nate Graham changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||bdebc4d246698b43e4182b0ebe9 ||a94b7d6780d60 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #3 from Nate Graham --- Git commit bdebc4d246698b43e4182b0ebe9a94b7d6780d60 by Nate Graham, on behalf of Nicolas Fella. Committed on 24/12/2021 at 21:43. Pushed by ngraham into branch 'master'. [kcms/style] Don't call setNeedsSave when style config changes The style config is saved already when the dialog closes so enabling the KCM apply button doesn't make sense The comment suggests that this is done for a reason, but the style preview seems to refresh correctly even with this patch M +0-3kcms/style/kcmstyle.cpp https://invent.kde.org/plasma/plasma-workspace/commit/bdebc4d246698b43e4182b0ebe9a94b7d6780d60 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447491] New: No plugins were loaded ...
https://bugs.kde.org/show_bug.cgi?id=447491 Bug ID: 447491 Summary: No plugins were loaded ... Product: digikam Version: 7.5.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: critical Priority: NOR Component: Plugins-Interface Assignee: digikam-bugs-n...@kde.org Reporter: merz.ch...@freenet.de Target Milestone: --- Hi, my favorite language is german :-) Your Team is great. DIGIKAM ist the best for my Pictures. Merry Christmas best wishes from Christoph Merz And here my little problem: (Windows 11, Intel Core 7, Version 7.5) During start from DIGIKAM follow: "No plugins were loaded, please check if the plugins were installed in one of the following paths: System Path: C:/Program Files/digiKam Local Path: C:/Users/MerzC/AppData/Local/.marble/plugins Also check if the plugin is compiled against the right version of Marble. Analyzing the debug messages inside a debugger might give more insight." -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 445801] Doesn't honor the system umask for newly-created files
https://bugs.kde.org/show_bug.cgi?id=445801 Vincent Minder changed: What|Removed |Added CC||vincent.min...@freebel.net --- Comment #11 from Vincent Minder --- Confirmed under Fedora 35 with KDE Frameworks 5.89, though not sure KIO is the best place for this. The issue is that KDE just doesn't seem to know about the user-defined umask at all. Not only KDE apps, any app launched through the Kickoff menu, like LibreOffice, will fail to honor the umask when creating a file. These same apps will behave as expected when launched from a shell, because the shell knows... The umask is usually set in the user profile or in the global profile. I hear that it should preferably be set in /etc/pam.d/login nowadays. I tried but it did not work any better. We've been there before, long ago, and probably several times since then: https://bugs.kde.org/show_bug.cgi?id=43172 An easy workaround then was to boot into non-graphical mode and type "startkde" by hand. Everything would work as expected, but if you went through the display manager, user-defined umask would be ignored. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 447336] Discover doesn't automatically pick a backend
https://bugs.kde.org/show_bug.cgi?id=447336 --- Comment #3 from doggoofsp...@gmail.com --- Created attachment 144847 --> https://bugs.kde.org/attachment.cgi?id=144847=edit gdb output -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland
https://bugs.kde.org/show_bug.cgi?id=447337 --- Comment #18 from Conrad --- turn on sets it to 0, turn off sets it to 1. The problem indeed only appears when numlock is enabled. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447204] Task manager offers to launch new instance of kcmshell and systemsettings
https://bugs.kde.org/show_bug.cgi?id=447204 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=429428 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429428] Task context menu has "Start new instance" for single-instance apps
https://bugs.kde.org/show_bug.cgi?id=429428 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 See Also||https://bugs.kde.org/show_b ||ug.cgi?id=447204 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429428] Task context menu has "Start new instance" for single-instance apps
https://bugs.kde.org/show_bug.cgi?id=429428 Nate Graham changed: What|Removed |Added Status|RESOLVED|REPORTED Keywords||usability Resolution|DUPLICATE |--- CC||n...@kde.org, ||plasma-b...@kde.org Component|general |Task Manager and Icons-Only ||Task Manager Target Milestone|--- |1.0 Product|konversation|plasmashell Summary|Start New Instance |Task context menu has ||"Start new instance" for ||single-instance apps Version|1.7.7 |5.23.4 Severity|wishlist|minor Assignee|konversation-de...@kde.org |h...@kde.org --- Comment #4 from Nate Graham --- Not a duplicate since that bug report is about apps whose desktop files have NoDisplay=true in them, which I have to assume is not the case for Konversation. Making this a new master bug for the issue of Task Manager context menus showing "Start new instance" item for single-instance apps. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447477] Panel disappears after interacting with applet in tablet mode
https://bugs.kde.org/show_bug.cgi?id=447477 Eric Edlund changed: What|Removed |Added Flags||Usability+ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447432] Cursor size inconsistent between windows on hi DPI display wayland
https://bugs.kde.org/show_bug.cgi?id=447432 Eric Edlund changed: What|Removed |Added Flags||Wayland+ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447432] Cursor size inconsistent between windows on hi DPI display wayland
https://bugs.kde.org/show_bug.cgi?id=447432 --- Comment #1 from Eric Edlund --- Cursor size is set to 36 to reproduce. I had to reboot to update the size. When size is 48, the cursor is the same size on all windows. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447490] Access Violation in module libkritalibpaintop.dll
https://bugs.kde.org/show_bug.cgi?id=447490 --- Comment #1 from Franck Rabeson --- Created attachment 144846 --> https://bugs.kde.org/attachment.cgi?id=144846=edit Krita log -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447490] New: Access Violation in module libkritalibpaintop.dll
https://bugs.kde.org/show_bug.cgi?id=447490 Bug ID: 447490 Summary: Access Violation in module libkritalibpaintop.dll Product: krita Version: 5.0.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: rabeson.fra...@gmail.com Target Milestone: --- Created attachment 144845 --> https://bugs.kde.org/attachment.cgi?id=144845=edit Krita crash log SUMMARY *** Affects Krita 5.0 final as well as Krita nightlies starting with build 21df2c5ffe (2021-12-21). STEPS TO REPRODUCE 1. Launch Krita OBSERVED RESULT The splash screen displays for a long time, then the krita.exe process closes without an error message. SOFTWARE/OS VERSIONS Windows: 10 x64 build 19044 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447482] In search view mouse page shows scrollbar at bottom
https://bugs.kde.org/show_bug.cgi?id=447482 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- Possibly related to bug 424474 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423161] Search results blink when updating
https://bugs.kde.org/show_bug.cgi?id=423161 --- Comment #7 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/krunner/-/merge_requests/82 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 447433] Some Icons are hard to see (Geany and Application menu)
https://bugs.kde.org/show_bug.cgi?id=447433 --- Comment #4 from pqwoerituytruei...@gmail.com --- no problem, we are all blind sometimes audacity is also a issue (Save buttons/Open buttons/exit dialog) using the breeze (not dark) icon set makes the application menu correct (though that makes the owncloud tray icon is hard to see) and does not help geany or audacity -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #199 from Enrico Tagliavini --- (In reply to cat22 from comment #198) > To me, i would think it shouldn't take more than writing a function that > does the work > and a few lines of code to decide whether to call it or not. It just can't > be so difficult that > someone couldn't fix it in an afternoon. > Be honest and change the status to "WILL NOT FIX" and we can be done with > this bickering Your expectations on how hard this would be is unrelated to how hard and how much work it actually is. Yes it sucks to have a bug for 7 years, but there might be more urgent and higher priority problems to solve first, take a look at the bug list. I would suggest you stick to the technical discussion. You and many other people have made clear about your frustration on this issue, there is no need to keep pushing. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 443573] Problems with update of battery values
https://bugs.kde.org/show_bug.cgi?id=443573 Eric Donkersloot changed: What|Removed |Added CC||eric.donkersl...@gmail.com --- Comment #4 from Eric Donkersloot --- The bug described at comment #2 is still present on my system, confirmed on 5.23.4 Operating System: openSUSE Tumbleweed 20211222 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.8-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 447489] pageStack: third page has incorrect width
https://bugs.kde.org/show_bug.cgi?id=447489 --- Comment #1 from Plata --- Created attachment 144844 --> https://bugs.kde.org/attachment.cgi?id=144844=edit increased window width -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 447489] New: pageStack: third page has incorrect width
https://bugs.kde.org/show_bug.cgi?id=447489 Bug ID: 447489 Summary: pageStack: third page has incorrect width Product: frameworks-kirigami Version: 5.88.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: pl...@mailbox.org Target Milestone: Not decided Created attachment 144843 --> https://bugs.kde.org/attachment.cgi?id=144843=edit original issue SUMMARY The third page in a pageStack does not wrap the text correctly. It seems to "believe" that the page is wider than it is actually. Even enlarging the window doesn't fix this. STEPS TO REPRODUCE 1. Build example app https://invent.kde.org/plata/kirigami-playground/-/tree/three-pages-long-text 2. Select action in global drawer OBSERVED RESULT Third page in pageStack does not wrap the text. EXPECTED RESULT Text is wrapped/page has correct width (i.e. 1/3 of window size). SOFTWARE/OS VERSIONS Linux: Manjaro KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Seems to be the reason for a bug in Alligator: https://invent.kde.org/plasma-mobile/alligator/-/issues/25 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #198 from cat22 ---
(In reply to Nate Graham from comment #197)
> The bug is acknowledged. It's marked as CONFIRMED with a VHI ("very high")
> priority and various technical people have shown up to offer thoughts on how
> to proceed with resolving it. At this point the best way to make that happen
> is to let them have that conversation without adding a bunch of comments
> saying things like, "+1, this is so bad!" and "OMG how did you let this
> happen?!" "and I've given up hope, KDE sux". Yes, we know it's bad, but
> clearly there is some desire to fix it among the developers. So let's let
> that happen.
>
> If you want to express your feelings about how bad this is and urge a
> quicker resolution, feel free to send them directly to me at n...@kde.org
> instead of posting a comment.
>
> Thanks.
and yet, nothing has been done in 7 years so apparently
CONFIRMED with a VHI ("very high") priority
don't mean what it says?
My guess is no one is even looking at this or just dismissing it as "to
involved or to hard"
To me, i would think it shouldn't take more than writing a function that does
the work
and a few lines of code to decide whether to call it or not. It just can't be
so difficult that
someone couldn't fix it in an afternoon.
Be honest and change the status to "WILL NOT FIX" and we can be done with this
bickering
--
You are receiving this mail because:
You are watching all bug changes.
[Powerdevil] [Bug 447475] lowering brightness to 0 on oled irreversibly turns off screen
https://bugs.kde.org/show_bug.cgi?id=447475 --- Comment #2 from Mark --- I could reproduce the issue in GNOME as well using brightnessctl s 0, nevertheless, perhaps a fix could be implemented to avoid going to 0 for specific type of screen. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447488] New: Window rule for an application to be on a specific monitor is not applied when opening this monitor
https://bugs.kde.org/show_bug.cgi?id=447488
Bug ID: 447488
Summary: Window rule for an application to be on a specific
monitor is not applied when opening this monitor
Product: systemsettings
Version: 5.22.5
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: kcm_kwinrules
Assignee: kwin-bugs-n...@kde.org
Reporter: tata...@gmail.com
CC: isma...@gmail.com, plasma-b...@kde.org
Target Milestone: ---
SUMMARY
I want an application to stay on my main monitor. I created a Window Rule with
the property "Screen", a value of "0" and the "Force" option.
When I apply this rule manually (during creation), if the application is on my
second monitor, it is properly moved to my main monitor ("0").
The problem:
When I close my main monitor, the application is moved to my second monitor,
this is ok. But when I open back my main monitor, the rule is not triggered
and the application is not moved to my main monitor as I want it to be.
STEPS TO REPRODUCE
1. Have two monitors. My main monitor ("0") is a Dell external monitor and my
second is the monitor of my laptop.
2. Create a Window Rule with the property "Screen", a value of "0" and the
"Force" option for a specific application.
3. Close the main monitor. The application is move to the second monitor. This
is ok.
4. Reopen the main monitor. The application is not moved back to the main
monitor.
OBSERVED RESULT
The application specified in the rule is not moved to the main monitor.
EXPECTED RESULT
The application specified in the rule is moved to the main monitor.
SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 447487] New: In search view, sub-categories column has inconsistent behavior
https://bugs.kde.org/show_bug.cgi?id=447487 Bug ID: 447487 Summary: In search view, sub-categories column has inconsistent behavior Product: systemsettings Version: 5.22.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: med.medin.2...@gmail.com Target Milestone: --- Created attachment 144842 --> https://bugs.kde.org/attachment.cgi?id=144842=edit In search view, sub-categories column has inconsistent behavior When user searches for something in Plasma settings, the sub-categories column sometimes appears and sometimes disappears and sometimes is shown but empty. If it's shown the list it contains shows wrong selected item, and if it disappears it modifies the width of right or left side. I think the middle sub-categories column should never appear when a search is triggered because those shown items have no meaning to appear as duplicated. See attached video for more info. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 441885] Latte dock crashing when changing Plasma appearance
https://bugs.kde.org/show_bug.cgi?id=441885 --- Comment #11 from Michail Vourlakos --- (In reply to Peifeng Yu from comment #10) > I compiled latte-dock and qt with debug info and I've been running > latte-dock under gdb for about a week now without any crash, while > previously the crash can happen multiple times a day. I think it's safe to > assume the latest git version somehow fixed this. it could be a packaging issue -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447486] New: In search result Appearance root node should be grayed to be consistent with other root nodes
https://bugs.kde.org/show_bug.cgi?id=447486 Bug ID: 447486 Summary: In search result Appearance root node should be grayed to be consistent with other root nodes Product: systemsettings Version: 5.22.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: med.medin.2...@gmail.com Target Milestone: --- Created attachment 144841 --> https://bugs.kde.org/attachment.cgi?id=144841=edit In search result Appearance root node should be grayed to be consistent with other root nodes See attached image for more info. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 441885] Latte dock crashing when changing Plasma appearance
https://bugs.kde.org/show_bug.cgi?id=441885 Peifeng Yu <7437...@gmail.com> changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #10 from Peifeng Yu <7437...@gmail.com> --- I compiled latte-dock and qt with debug info and I've been running latte-dock under gdb for about a week now without any crash, while previously the crash can happen multiple times a day. I think it's safe to assume the latest git version somehow fixed this. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447485] New: Application style appears directly under Appearance instead of Global Theme
https://bugs.kde.org/show_bug.cgi?id=447485 Bug ID: 447485 Summary: Application style appears directly under Appearance instead of Global Theme Product: systemsettings Version: 5.22.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: med.medin.2...@gmail.com Target Milestone: --- Created attachment 144840 --> https://bugs.kde.org/attachment.cgi?id=144840=edit Application style appears directly under Appearance instead of Global Theme See attached image. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446991] Calander popup in clock widget unusable on breeze light
https://bugs.kde.org/show_bug.cgi?id=446991 Nate Graham changed: What|Removed |Added Version|5.88.0 |5.23.3 Component|components |Digital Clock Target Milestone|--- |1.0 Product|frameworks-plasma |plasmashell Assignee|notm...@gmail.com |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447484] New: Smudge engine does not work with grayscale images
https://bugs.kde.org/show_bug.cgi?id=447484 Bug ID: 447484 Summary: Smudge engine does not work with grayscale images Product: krita Version: 5.0.0 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: crazyjer...@gmail.com Target Milestone: --- Created attachment 144839 --> https://bugs.kde.org/attachment.cgi?id=144839=edit Video demonstrating bug Smudge engine paints hard black squares on a grayscale image surrounding the layer's alpha. STEPS TO REPRODUCE 1. create/convert image to grayscale using default color profile OR convert a layer's color profile to grayscale 2. paint with any brush that smudges on the grayscale image or layer. OBSERVED RESULT Big black squares surrounding the brush EXPECTED RESULT Smudging as seen in an RGB image 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.
[frameworks-plasma] [Bug 446991] Calander popup in clock widget unusable on breeze light
https://bugs.kde.org/show_bug.cgi?id=446991 Nate Graham changed: What|Removed |Added Version Fixed In||5.23.5 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 446991] Calander popup in clock widget unusable on breeze light
https://bugs.kde.org/show_bug.cgi?id=446991 Nate Graham changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/ |df55858321906091252d87c02a5 |aaf9d475fd39fddb7671b33dca6 |e35d379a10056 |b1a8ed74e2c06 --- Comment #18 from Nate Graham --- Git commit aaf9d475fd39fddb7671b33dca6b1a8ed74e2c06 by Nate Graham, on behalf of Noah Davis. Committed on 24/12/2021 at 18:03. Pushed by ngraham into branch 'Plasma/5.23'. digital-clock: fix calendar popup contrast when opened from desktop (cherry picked from commit df55858321906091252d87c02a5e35d379a10056) M +3-0applets/digital-clock/package/contents/ui/CalendarView.qml https://invent.kde.org/plasma/plasma-workspace/commit/aaf9d475fd39fddb7671b33dca6b1a8ed74e2c06 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 446991] Calander popup in clock widget unusable on breeze light
https://bugs.kde.org/show_bug.cgi?id=446991 Noah Davis changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||df55858321906091252d87c02a5 ||e35d379a10056 --- Comment #17 from Noah Davis --- Git commit df55858321906091252d87c02a5e35d379a10056 by Noah Davis. Committed on 24/12/2021 at 13:30. Pushed by ngraham into branch 'master'. digital-clock: fix calendar popup contrast when opened from desktop M +3-0applets/digital-clock/package/contents/ui/CalendarView.qml https://invent.kde.org/plasma/plasma-workspace/commit/df55858321906091252d87c02a5e35d379a10056 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447483] New: Clearing search leave sub-categories column empty
https://bugs.kde.org/show_bug.cgi?id=447483 Bug ID: 447483 Summary: Clearing search leave sub-categories column empty Product: systemsettings Version: 5.22.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: med.medin.2...@gmail.com Target Milestone: --- Created attachment 144838 --> https://bugs.kde.org/attachment.cgi?id=144838=edit Clearing search leave sub-categories column empty See attached video for more info. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 446639] Breeze GTK: Regression in various GTK assets since commit c18f2a472a654b648fb9e056f4c7c66d5e1bf786
https://bugs.kde.org/show_bug.cgi?id=446639 Nate Graham changed: What|Removed |Added Version Fixed In||5.23.5 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/breeze-gtk/-/commit/3785 ||faebac7dc1541222a755e3070a8 ||bddcc72d4 --- Comment #4 from Nate Graham --- Fixed by Guillaume Castagnino with https://invent.kde.org/plasma/breeze-gtk/-/commit/3785faebac7dc1541222a755e3070a8bddcc72d4 in Plasma 5.23.5! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447482] New: In search view mouse page shows scrollbar at bottom
https://bugs.kde.org/show_bug.cgi?id=447482 Bug ID: 447482 Summary: In search view mouse page shows scrollbar at bottom Product: systemsettings Version: 5.22.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_mouse Assignee: plasma-b...@kde.org Reporter: med.medin.2...@gmail.com Target Milestone: --- Created attachment 144837 --> https://bugs.kde.org/attachment.cgi?id=144837=edit In search view mouse page shows scrollbar at bottom See attached video for more info. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #197 from Nate Graham ---
The bug is acknowledged. It's marked as CONFIRMED with a VHI ("very high")
priority and various technical people have shown up to offer thoughts on how to
proceed with resolving it. At this point the best way to make that happen is to
let them have that conversation without adding a bunch of comments saying
things like, "+1, this is so bad!" and "OMG how did you let this happen?!" "and
I've given up hope, KDE sux". Yes, we know it's bad, but clearly there is some
desire to fix it among the developers. So let's let that happen.
If you want to express your feelings about how bad this is and urge a quicker
resolution, feel free to send them directly to me at n...@kde.org instead of
posting a comment.
Thanks.
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 447481] New: Can't mount USB drive
https://bugs.kde.org/show_bug.cgi?id=447481 Bug ID: 447481 Summary: Can't mount USB drive Product: dolphin Version: 21.12.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: akontsev...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Can't mount USB drive in Tumbleweed KDE while it is successfully mounts on my Kubuntu 20.04 Laptop. Dolphin prints error: > Error mounting /dev/sdd1 at /run/media/user/TRANSCEND: > The function 'bd_fs_mount' called, but not implemented! Problem is fully described here: https://forums.opensuse.org/showthread.php/563878-Can-t-mount-USB-drive -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 447478] Q_ASSERT crash in screen.cpp when trying to select, searching
https://bugs.kde.org/show_bug.cgi?id=447478 --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/utilities/konsole/-/merge_requests/562 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #196 from Aaron Wolf --- If this were fixed, it would also likely make it easier to resolve https://bugs.kde.org/show_bug.cgi?id=393956 Hesitant to just add another +1, but this issue is *so* awkward. The simple capacity to override default formats with simple standard format codes ought to be trivial for anyone. I just want the logical ISO date format -MM-DD while keeping other U.S. norms, including 12-hour time (and no, 12-hour is not just some weird American thing, it's how all analog clocks work). I figured out that en_CA for Time works enough, but the extra dots in A.M. and P.M. are silly and take too much extra space. At least that workaround is possible, but this is not how it should be functioning. People lamenting a *regression* where things were fine and then a new design broke things is not the same as people demanding that free/libre/open software just magically have all the features they wish. And what bug-reporters want is mostly to have the bugs acknowledged completely. There's nothing about Open Source development that makes it any harder to simply say "yes, this is indeed a bad bug". Admitting that it's bad is not the same as a commitment to fix it promptly. There's no room for any comment that tries to be dismissive about the facts of the bug or downplay that it's bad. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447466] pixel art brush outline showing as a regular circle instead of pixelated circle but "outline shape" setting is set to "preview outline" not "circle"
https://bugs.kde.org/show_bug.cgi?id=447466 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com Status|REPORTED|ASSIGNED Ever confirmed|0 |1 Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439797] System Settings crashes in KCMLookandFeel::knsEntryChanged() when I try to update a global theme via GHNS window of Global Theme KCM
https://bugs.kde.org/show_bug.cgi?id=439797 Kalzi changed: What|Removed |Added CC|kalzwa...@yahoo.com | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439797] System Settings crashes in KCMLookandFeel::knsEntryChanged() when I try to update a global theme via GHNS window of Global Theme KCM
https://bugs.kde.org/show_bug.cgi?id=439797 --- Comment #56 from Carlos Castro --- Created attachment 144836 --> https://bugs.kde.org/attachment.cgi?id=144836=edit New crash information added by DrKonqi systemsettings5 (5.23.4) using Qt 5.15.3 - What I was doing when the application crashed: As usual every time I try to add a new topic SETTINGS crashes - Unusual behavior I noticed: As usual every time I try to add a new topic SETTINGS crashes - Custom settings of the application: None -- Backtrace (Reduced): #4 0x7f6e835b49fd in QDir::fromNativeSeparators(QString const&) () at /usr/include/c++/9/bits/atomic_base.h:318 #5 0x7f6e835c8b97 in QFileInfoPrivate::QFileInfoPrivate(QString const&) (file=..., this=0x56310e6cc300) at /usr/include/c++/9/bits/atomic_base.h:279 #6 QFileInfo::QFileInfo(QString const&) (this=0x7ffe5ce92808, file=...) at io/qfileinfo.cpp:347 #7 0x7f6e67170134 in KCMLookandFeeloperator() (__closure=, __closure=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:117 #8 KCMLookandFeel::knsEntryChanged(KNSCore::EntryWrapper*) (this=0x56310e63c450, wrapper=) at ./kcms/lookandfeel/kcm.cpp:126 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439797] System Settings crashes in KCMLookandFeel::knsEntryChanged() when I try to update a global theme via GHNS window of Global Theme KCM
https://bugs.kde.org/show_bug.cgi?id=439797 Carlos Castro changed: What|Removed |Added CC||carlos.r.castr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 447480] New: Allow currencies to be divisible by more than ten decimal places
https://bugs.kde.org/show_bug.cgi?id=447480 Bug ID: 447480 Summary: Allow currencies to be divisible by more than ten decimal places Product: kmymoney Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: chris.cru...@gmail.com Target Milestone: --- Currently the application seems to only allow a maximum of ten decimal places when adding a new currency type. Monero, a popular cryptocurrency with the third largest development community of all cryptocoins, is divisible to twelve decimal places. Please consider adding a few extra decimal places to the currency options. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 447409] okular crash when try to insert annotation stamp
https://bugs.kde.org/show_bug.cgi?id=447409 --- Comment #2 from Carlos Castro --- Created attachment 144835 --> https://bugs.kde.org/attachment.cgi?id=144835=edit New crash information added by DrKonqi okular (21.12.0) using Qt 5.15.3 - What I was doing when the application crashed: Okular crashes every time I try to create a new stamp. - Unusual behavior I noticed: I go to PREFERENCES and then to NOTES and when placing add I choose the option STAMPS and Okular crashes every time. - Custom settings of the application: None -- Backtrace (Reduced): #4 0x7f91312f6c69 in StampAnnotationWidget::createStyleWidget (this=0x557ff8e1a520, formlayout=0x557ff8e2e9e0) at ./part/annotationwidgets.cpp:442 #5 0x7f91312f19c4 in AnnotationWidget::createAppearanceWidget (this=this@entry=0x557ff8e1a520) at ./part/annotationwidgets.cpp:247 #6 0x7f91312f19e9 in AnnotationWidget::appearanceWidget (this=0x557ff8e1a520) at ./part/annotationwidgets.cpp:219 #7 0x7f91312aa207 in EditAnnotToolDialog::rebuildAppearanceBox (this=this@entry=0x7ffe675a0770) at ./part/editannottooldialog.cpp:337 #8 0x7f91312ac045 in EditAnnotToolDialog::slotTypeChanged (this=0x7ffe675a0770) at ./part/editannottooldialog.cpp:460 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 447409] okular crash when try to insert annotation stamp
https://bugs.kde.org/show_bug.cgi?id=447409 Carlos Castro changed: What|Removed |Added CC||carlos.r.castr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447408] Crash when loading metadata for specially-crafted JPEG images
https://bugs.kde.org/show_bug.cgi?id=447408 --- Comment #4 from Maik Qualmann --- I don't think the "component" parameter is a problem, most of the checks are <= 0. Maik -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 447478] Q_ASSERT crash in screen.cpp when trying to select, searching
https://bugs.kde.org/show_bug.cgi?id=447478 --- Comment #3 from Martin Sandsmark --- Can consistently reproduce by double clicking to start word selection, and then moving the cursor over an URL. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 447478] Q_ASSERT crash in screen.cpp when trying to select, searching
https://bugs.kde.org/show_bug.cgi?id=447478 --- Comment #2 from Martin Sandsmark --- >From trying to reproduce, it seems to be happening sometimes when resizing the window (so things get reflowed), and then double clicking on a highlighted URL. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447473] Cannot disable completely under/over-exposure was enable when launching "Adjust Curve"
https://bugs.kde.org/show_bug.cgi?id=447473 --- Comment #5 from Alexandre Belz --- Whoo, that's an express bug resolution ! Many thanks Maik ! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
https://bugs.kde.org/show_bug.cgi?id=340982 --- Comment #195 from sombrag...@sombragris.org --- (In reply to richlv from comment #193) > A reminder to all the demanding commenters: this is an opensource community > project. > It is OK to be disappointed or sad - but the energy that is put in demands > would be much better put elsewhere. > One might be able to help with documentation, bug triaging or testing to > give more time to developers - or put a bounty on a particular feature (like > adding this functionality in QLocale). > > [Please feel free to hide this comment and others, not contributing > technically.] It was a matter of time for a comment like this to appear. "Shut up and work instead of whining!" I try to do my best. Today it's reporting bugs in the best possible way; I simply do not have the time or money to do something else. But if you're interested, I was part of the Spanish KDE Localization team for 10 years, 2002 to 2012. My name is here: https://es.l10n.kde.org/colaboradores.php - Are you satisfied now? Do I have permission to report bugs now?? All in all, this does not invalidate the bug nor the unacceptability of its presence. It should be fixed, that's all. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447473] Cannot disable completely under/over-exposure was enable when launching "Adjust Curve"
https://bugs.kde.org/show_bug.cgi?id=447473 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.5.0 Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/2797d12 ||78be01250bd38e1c3c385d660c7 ||6290ee Resolution|--- |FIXED --- Comment #4 from Maik Qualmann --- Git commit 2797d1278be01250bd38e1c3c385d660c76290ee by Maik Qualmann. Committed on 24/12/2021 at 16:10. Pushed by mqualmann into branch 'master'. fix apply exposure settings in the ImageRegionWidget FIXED-IN: 7.5.0 M +1-0core/utilities/imageeditor/widgets/imageregionwidget.cpp https://invent.kde.org/graphics/digikam/commit/2797d1278be01250bd38e1c3c385d660c76290ee -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 447478] Q_ASSERT crash in screen.cpp when trying to select, searching
https://bugs.kde.org/show_bug.cgi?id=447478 --- Comment #1 from Martin Sandsmark --- There is something very wrong here, it ends up in the "fetch from history" branch when I'm selecting something on screen. And the code is a bit wonky, the comment says that _screenLinesSize is the same as _screenLines.size(), but it doesn't seem to be always updated (in this case _screenLines.size() is 62, _screenLinesSize is 61). -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 447479] New: Cannot install craft on windows
https://bugs.kde.org/show_bug.cgi?id=447479
Bug ID: 447479
Summary: Cannot install craft on windows
Product: Craft
Version: unspecified
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: crash
Priority: NOR
Component: Core
Assignee: vonr...@kde.org
Reporter: richard1.kellnber...@web.de
CC: kde-wind...@kde.org
Target Milestone: ---
Created attachment 144834
--> https://bugs.kde.org/attachment.cgi?id=144834=edit
PS output
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
STEPS TO REPRODUCE
Follow guide in
https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source/Windows:
1. open powershell (as admin)
2. run "Set-ExecutionPolicy -Scope CurrentUser RemoteSigned"
3. run "iex ((new-object
net.webclient).DownloadString('https://raw.githubusercontent.com/KDE/craft/master/setup/install_craft.ps1'))"
OBSERVED RESULT
Crash because a python scripted encountered an encoding error
see attachement
EXPECTED RESULT
Working install
SOFTWARE/OS VERSIONS
Windows: 10.0.19042
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
python is installed and on PATH (3.9.6)
MinGW is installed and on PATH
System language is German
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 447478] New: Q_ASSERT crash in screen.cpp when trying to select, searching
https://bugs.kde.org/show_bug.cgi?id=447478 Bug ID: 447478 Summary: Q_ASSERT crash in screen.cpp when trying to select, searching Product: konsole Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: martin.sandsm...@kde.org Target Milestone: --- Crashing on Q_ASSERT(screenLine <= _screenLinesSize); screenLine is 437, _screenLinesSize is 61, _columns is 113, the rest of the useful are optimized out. #0 0x7f72f8d3cd22 in raise () at /usr/lib/libc.so.6 #1 0x7f72f8d26862 in abort () at /usr/lib/libc.so.6 #2 0x7f72f9172f26 in qt_assert(char const*, char const*, int) () at /usr/lib/libQt5Core.so.5 #3 0x7f72f9172f86 in qt_assert_x(char const*, char const*, char const*, int) () at /usr/lib/libQt5Core.so.5 #4 0x7f72fa5ab9b4 in Konsole::Screen::copyLineToStream(int, int, int, Konsole::TerminalCharacterDecoder*, bool, bool, QFlags) const (this=, line=, start=90, count=1, decoder=, appendNewLine=, isBlockSelectionMode=false, options=...) at /usr/src/debug/konsole/src/Screen.cpp:1543 #5 0x7f72fa5d4884 in Konsole::Screen::writeToStream(Konsole::TerminalCharacterDecoder*, int, int, QFlags) const (this=0x561ca8a084d0, decoder=0x7ffd7906a840, startIndex=, endIndex=, options=...) at /usr/src/debug/konsole/src/Screen.cpp:1454 #6 0x7f72fa5d7ca2 in Konsole::Screen::text(int, int, QFlags) const (this=this@entry=0x561ca8a084d0, startIndex=50262, endIndex=50262, options=options@entry=...) at /usr/src/debug/konsole/src/Screen.cpp:1421 #7 0x7f72fa5d7e0b in Konsole::Screen::selectedText(QFlags) const (this=0x561ca8a084d0, options=options@entry=...) at /usr/src/debug/konsole/src/Screen.cpp:1402 #8 0x7f72fa5c0c13 in Konsole::Emulation::checkSelectedText() (this=0x561ca8a1af90) at /usr/include/qt/QtCore/qflags.h:121 #9 0x7f72f938ead3 in () at /usr/lib/libQt5Core.so.5 #10 0x7f72fa63037a in Konsole::TerminalDisplay::extendSelection(QPoint const&) (this=this@entry=0x561ca89f07c0, position=...) at /usr/src/debug/konsole/src/terminalDisplay/TerminalDisplay.cpp:1450 #11 0x7f72fa63091e in Konsole::TerminalDisplay::mouseMoveEvent(QMouseEvent*) (this=0x561ca89f07c0, ev=0x7ffd7906b1a0) at /usr/src/debug/konsole/src/terminalDisplay/TerminalDisplay.cpp:1299 #12 0x7f72f9e7ea96 in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #13 0x7f72f9e481a6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #14 0x7f72f9e4cfd7 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #15 0x7f72f935df8a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #16 0x7f72f9e4b99f in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /usr/lib/libQt5Widgets.so.5 #17 0x7f72f9e9c837 in () at /usr/lib/libQt5Widgets.so.5 #18 0x7f72f9e9e3dc in () at /usr/lib/libQt5Widgets.so.5 #19 0x7f72f9e481a6 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #20 0x7f72f935df8a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #21 0x7f72f97c7fa0 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib/libQt5Gui.so.5 #22 0x7f72f97b35e5 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/libQt5Gui.so.5 #23 0x7f72f2d89daa in () at /usr/lib/libQt5XcbQpa.so.5 #24 0x7f72f935626b in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #25 0x7f72f93619b7 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #26 0x561ca776080b in main(int, char**) (argc=, argv=) at /usr/src/debug/konsole/src/main.cpp:242 Seemingly same issue as https://bugs.kde.org/show_bug.cgi?id=440619#c2, which seems to be happening when searching. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447364] Unable to set current time manually
https://bugs.kde.org/show_bug.cgi?id=447364 David Edmundson changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- please include output from running systemsettings5 in a terminal -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 440619] paste in Konsole tab failed, then crash
https://bugs.kde.org/show_bug.cgi?id=440619 Martin Sandsmark changed: What|Removed |Added CC||martin.sandsm...@kde.org --- Comment #3 from Martin Sandsmark --- (In reply to Ömer Fadıl USTA from comment #2) > In screen.cpp it was hitting this assert line : > Q_ASSERT(screenLine <= _screenLinesSize); Different bug, happened here as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447465] Xwayland windows blurry on hi DPI display wayland
https://bugs.kde.org/show_bug.cgi?id=447465 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk Resolution|--- |DUPLICATE --- Comment #2 from David Edmundson --- *** This bug has been marked as a duplicate of bug 433810 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433810] Scaling with Wayland makes the windows blurry
https://bugs.kde.org/show_bug.cgi?id=433810 David Edmundson changed: What|Removed |Added CC||ericedlund2...@gmail.com --- Comment #4 from David Edmundson --- *** Bug 447465 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 438784] Panning and zooming bug in Krita
https://bugs.kde.org/show_bug.cgi?id=438784 --- Comment #12 from Alejandro --- A message to the developers: This bug occurs since the 4.3 version. Maybe you can check the 4.2.9 version (which I'm currently using as it doesn't have the bug) and compare it with the 4.3 to see the code differences and spot what causes the bug. I'm on Windows 10 with a Huion INSPIROY H1161. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447465] Xwayland windows blurry on hi DPI display wayland
https://bugs.kde.org/show_bug.cgi?id=447465 --- Comment #1 from David Edmundson --- *** Bug 447467 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447467] Xwayland windows blurry on hi DPI display wayland
https://bugs.kde.org/show_bug.cgi?id=447467 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 447465 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447477] New: Panel disappears after interacting with applet in tablet mode
https://bugs.kde.org/show_bug.cgi?id=447477 Bug ID: 447477 Summary: Panel disappears after interacting with applet in tablet mode Product: plasmashell Version: 5.23.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: ericedlund2...@gmail.com Target Milestone: 1.0 SUMMARY I'm on a 2 in 1 laptop and when I have it in tablet mode the bottom task panel is shown. Then after I interact with an applet, like pressing the battery applet to change brightness, the bar hides and I have to unfold my computer to get it back. STEPS TO REPRODUCE 1. Enter tablet mode 2. Interact with applet on dock OBSERVED RESULT Panel hides after interaction EXPECTED RESULT Panel remains visible. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon 5.23 User Edition (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447473] Cannot disable completely under/over-exposure was enable when launching "Adjust Curve"
https://bugs.kde.org/show_bug.cgi?id=447473 --- Comment #3 from Maik Qualmann --- Ok, if I change the tool settings and a new preview has to be rendered, the new button settings are applied. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447473] Cannot disable completely under/over-exposure was enable when launching "Adjust Curve"
https://bugs.kde.org/show_bug.cgi?id=447473 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- When a tool is open, the buttons for displaying the over / under exposure no longer have any effect on the tool preview. Maik -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 447475] lowering brightness to 0 on oled irreversibly turns off screen
https://bugs.kde.org/show_bug.cgi?id=447475 --- Comment #1 from Mark --- I forgot to add, I'm on linux-5.16.0.1 so all oled patches are included already. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447476] New: Polish - Panel not done composing when shown for the first time
https://bugs.kde.org/show_bug.cgi?id=447476 Bug ID: 447476 Summary: Polish - Panel not done composing when shown for the first time Product: plasmashell Version: 5.23.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: ericedlund2...@gmail.com Target Milestone: 1.0 SUMMARY When I boot to the desktop, the panel automatically shows up before its done composing. STEPS TO REPRODUCE 1. Login to plasma session 2. Watch panel appear OBSERVED RESULT The applets item on the panel is initially displayed in the middle of the panel then slid to the right where it belongs. EXPECTED RESULT All panel items are in the correct position before the panel shows for the first time. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon 5.23 User Edition (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
