[kwin] [Bug 417455] Black screen after SDDM login and start screen in 10bit/30bpp mode with compositor enabled in OpenGL mode (amdgpu)
https://bugs.kde.org/show_bug.cgi?id=417455 --- Comment #10 from ber...@codewiz.org --- Xorg.0.log confirms that the server is running in 10bpp: [ 8387.363] (II) AMDGPU(0): Creating default Display subsection in Screen section "default" for depth/fbbpp 30/32 [ 8387.363] (**) AMDGPU(0): Depth 30, (--) framebuffer bpp 32 [ 8387.363] (II) AMDGPU(0): Pixel depth = 30 bits stored in 4 bytes (32 bpp pixmaps) [ 8387.363] (==) AMDGPU(0): Default visual is TrueColor [ 8387.363] (**) AMDGPU(0): Option "VariableRefresh" "true" [ 8387.363] (==) AMDGPU(0): RGB weight 101010 [ 8387.363] (II) AMDGPU(0): Using 10 bits per RGB (8 bit DAC) [ 8387.363] (--) AMDGPU(0): Chipset: "Radeon RX Vega" (ChipID = 0x687f) ... [ 8387.411] (II) AMDGPU(0): glamor X acceleration enabled on Radeon RX Vega (VEGA10, DRM 3.36.0, 5.6.14-arch1-1, LLVM 10.0.0) [ 8387.411] (II) AMDGPU(0): glamor detected, initialising EGL layer. [ 8387.411] (==) AMDGPU(0): TearFree property default: auto [ 8387.411] (**) AMDGPU(0): VariableRefresh: enabled [ 8387.411] (II) AMDGPU(0): KMS Pageflipping: enabled ... [ 8387.425] (II) AMDGPU(0): 10 bits per channel -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 417455] Black screen after SDDM login and start screen in 10bit/30bpp mode with compositor enabled in OpenGL mode (amdgpu)
https://bugs.kde.org/show_bug.cgi?id=417455 ber...@codewiz.org changed: What|Removed |Added CC||ber...@codewiz.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #9 from ber...@codewiz.org --- Just tested this on ArchLinux with: kwin 5.18.5-1 libdrm 2.4.101-1 mesa 20.0.7-3 xf86-video-amdgpu 19.1.0-2 After logging in from sddm, I just get blank screen (mouse cursor moves normally). Killing kwin_x11 causes konsole to re-appear. I don't have other X11 window managers installed to test with. Setting KWIN_OPENGL_INTERFACE=egl as suggested in comment #5 did not help. Happy to run further tests if necessary. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398288] digikam no write access to folder
https://bugs.kde.org/show_bug.cgi?id=398288 --- Comment #22 from Maik Qualmann --- Access is not sensitive. We don't even trust QFileInfo here. We try to create a temporary file. Again, if it works in the user folder and not just below C: everything is ok at the moment. The extended file protection cannot be deactivated by switching off the UAC. Believe me, we have examined the problem intensively. You have to wait until digiKam is available in the App Store at some point. Maik -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392239] CR linebreaks in message view are not shown
https://bugs.kde.org/show_bug.cgi?id=392239 --- Comment #11 from Laurent Montel --- Git commit 65372b5304a504446259ec1504aa5e2856105e46 by Laurent Montel. Committed on 25/05/2020 at 05:06. Pushed by mlaurent into branch 'release/20.04'. Add autotest for bug 392239 So we extract correctly \r Now we need to know why it doesn't display them A +19 -0autotests/data/mails/bug392239.mbox M +9-0autotests/messagetest.cpp M +1-0autotests/messagetest.h https://invent.kde.org/pim/kmime/commit/65372b5304a504446259ec1504aa5e2856105e46 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 411664] clicking on a certain brush preset crashes software
https://bugs.kde.org/show_bug.cgi?id=411664 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #12 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kid3] [Bug 421201] kid3 flags ISRC tags with the new QM (USA) country code as invalid
https://bugs.kde.org/show_bug.cgi?id=421201 --- 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.
[krita] [Bug 421283] Texture should not always scale with brush size
https://bugs.kde.org/show_bug.cgi?id=421283 --- 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.
[krita] [Bug 410750] Annoying straight lines when I draw slow
https://bugs.kde.org/show_bug.cgi?id=410750 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #11 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410024] Autosave prevents saving (without any message for the user)
https://bugs.kde.org/show_bug.cgi?id=410024 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 347874] Drawing area flashes random section of the alpha layer
https://bugs.kde.org/show_bug.cgi?id=347874 --- Comment #5 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.
[digikam] [Bug 421945] Existing face tags not rotated with image
https://bugs.kde.org/show_bug.cgi?id=421945 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.0.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/digikam/commit/9900860 ||0b7b2ba5b28ae15bec638c1eb8f ||ad7b6d --- Comment #5 from Maik Qualmann --- Git commit 99008600b7b2ba5b28ae15bec638c1eb8fad7b6d by Maik Qualmann. Committed on 25/05/2020 at 04:26. Pushed by mqualmann into branch 'master'. fix face rotation when only change the orientation flag FIXED-IN: 7.0.0 M +2-2NEWS M +5-0core/libs/fileactionmanager/databaseworkeriface.cpp M +15 -99 core/libs/fileactionmanager/fileworkeriface.cpp M +0-3core/libs/fileactionmanager/fileworkeriface.h M +85 -0core/libs/fileactionmanager/metadatahub.cpp M +7-0core/libs/fileactionmanager/metadatahub.h https://invent.kde.org/graphics/digikam/commit/99008600b7b2ba5b28ae15bec638c1eb8fad7b6d -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 422036] Kdenlive latest version freezes for any task, opens multiple windows
https://bugs.kde.org/show_bug.cgi?id=422036 Christoph Feck changed: What|Removed |Added Component|general |User Interface Assignee|unassigned-b...@kde.org |j...@kdenlive.org Product|kde |kdenlive -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 422036] New: Kdenlive latest version freezes for any task, opens multiple windows
https://bugs.kde.org/show_bug.cgi?id=422036 Bug ID: 422036 Summary: Kdenlive latest version freezes for any task, opens multiple windows Product: kde Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: cheryl.me...@att.net Target Milestone: --- SUMMARY version 20.04.01 - I upgraded and your program freezes when I simply insert a clip in the timeline. I wait and it says it's not responding. STEPS TO REPRODUCE 1. Insert clip in timeline 2. 3. OBSERVED RESULT Program freezes EXPECTED RESULT Not to freeze SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION You guys need to beta test things better, not use us like Bill Gates did. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422034] Krita won't let me render image sequence with frames "starting" past 500?
https://bugs.kde.org/show_bug.cgi?id=422034 --- Comment #2 from Michelle --- (In reply to Eoin O'Neill from comment #1) > Hi Michelle! I have a few questions about this bug: > > First, could you tell me what version you are currently using? > > Secondly, have you tried changing your animation docker's playback range? > The maximum value is generally set based on the setting of the animation > docker's playback range. I don't seem to have this issue when setting the > playback range within the docker (it always has the right values.) > > Thank you for taking the time to file a bug report. Oh! Turns out that was the issue! I hadn't realized my docker's playback range was set to 500 frames, and I didn't realize those were correlated. Thank you so much! (And if you still want to know my version was 4.2.9) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422034] Krita won't let me render image sequence with frames "starting" past 500?
https://bugs.kde.org/show_bug.cgi?id=422034 Michelle changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 422001] KF5 5.70.0 regression: Dolphin shows same SMB share twice
https://bugs.kde.org/show_bug.cgi?id=422001 --- Comment #5 from S --- Thanks for looking into this. It appears I was wrong about this being a problem limited to Dolphin / KIO. This is what I discovered: - Tumbleweed KDE, KF5 5.70.0 --> *duplicates* - openSUSE Leap 15.2 beta, KF5 5.69.0 --> no duplicates - Fedora 32 KDE, KF5 5.68.0 --> no duplicates - Fedora 32 Gnome 3.34 w/ Nautilus --> no duplicates - Ubuntu 20.04 Gnome 3.34 w/ Nautilus --> *duplicates* So I can't seem to find any rhyme or reason as to why some distros manifest this bug and others don't. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422034] Krita won't let me render image sequence with frames "starting" past 500?
https://bugs.kde.org/show_bug.cgi?id=422034 Eoin O'Neill changed: What|Removed |Added CC||eoinoneill1...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Eoin O'Neill --- Hi Michelle! I have a few questions about this bug: First, could you tell me what version you are currently using? Secondly, have you tried changing your animation docker's playback range? The maximum value is generally set based on the setting of the animation docker's playback range. I don't seem to have this issue when setting the playback range within the docker (it always has the right values.) Thank you for taking the time to file a bug report. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 345358] digiKam crash when vkontakte plugin failed to upload images
https://bugs.kde.org/show_bug.cgi?id=345358 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Plugin-WebService-Vkontakte Summary|KIPI host application crash |digiKam crash when |when vkontakte plugin |vkontakte plugin failed to |failed to upload images |upload images Assignee|imaging-bugs-n...@kde.org |digikam-bugs-n...@kde.org Product|libkvkontakte |digikam -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 56052] Printing the What's next view
https://bugs.kde.org/show_bug.cgi?id=56052 gjditchfi...@acm.org changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED CC||gjditchfi...@acm.org --- Comment #5 from gjditchfi...@acm.org --- It looks like this wish was granted in 2004. Current KOrganizer lets you select one or more days in the month widget in the left sidebar and print them. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421210] digiKam 5.9.0-1+b1 refuses to start since LMDE4 Debbie upgrade
https://bugs.kde.org/show_bug.cgi?id=421210 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||7.0.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422035] New: Icons align right on move align left
https://bugs.kde.org/show_bug.cgi?id=422035 Bug ID: 422035 Summary: Icons align right on move align left Product: plasmashell Version: 5.18.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: h...@kde.org Reporter: leszek.les...@web.de CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. Align Icons as columns to the right and set sorting manually 2. Move an icon to a new column or row (with now other icon) OBSERVED RESULT Icons suddenly align left but mirrored. EXPECTED RESULT Icon should just move according to set alignment SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian 10 stable KDE Plasma Version: 5.18.90 KDE Frameworks Version: 5.70 Qt Version: 5.14.2 ADDITIONAL INFORMATION When trying to mark desktop icons for selection they suddenly jump to the right alignment again. See video here that shows the issue: https://youtu.be/5LrviqEU1rM -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 421896] can't open video settings
https://bugs.kde.org/show_bug.cgi?id=421896 --- Comment #1 from Sérgio Basto --- Version-Release number of selected component (if applicable): kamoso from Fedora kamoso-18.03.80-4.fc31 repo and kamoso updated to kamoso-20.04.1-2.fc31.x86_64 built on corp I'm testing it here: https://copr.fedorainfracloud.org/coprs/sergiomb/builds_for_Stable_Releases/package/kamoso/ with https://src.fedoraproject.org/rpms/kamoso/pull-request/1 -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 421896] can't open video settings
https://bugs.kde.org/show_bug.cgi?id=421896 Sérgio Basto changed: What|Removed |Added Summary|Why I can't see video |can't open video settings |settings ? | -- You are receiving this mail because: You are watching all bug changes.
[Craft] [Bug 421921] MacOS X builds failing on CI due to signing tool not liking plugin names
https://bugs.kde.org/show_bug.cgi?id=421921 michael changed: What|Removed |Added Summary|MacOS X builds failing on |MacOS X builds failing on |CI due to duplicate RPATH |CI due to signing tool not ||liking plugin names --- Comment #4 from michael --- That got it working. Would be nice to have this documented. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 421946] Baloo indexing anomalies
https://bugs.kde.org/show_bug.cgi?id=421946 --- Comment #3 from Scott --- (In reply to tagwerk19 from comment #2) > If I was to make a guess... > > The result from "balooctl status" includes the number of directories looked > at whereas the stream from "balooctl monitor" gives you the files opened and > indexed. > > Try creating a new empty folder, purge and reindex and see if the "balooctl > status" goes up one. That's the difference, thank you. Case closed. -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 363852] Ktorrent no longer starts hidden in tray
https://bugs.kde.org/show_bug.cgi?id=363852 --- Comment #16 from Matt Scheirer --- I did go and make a pull request on Invent for the fix @ https://invent.kde.org/network/ktorrent/-/merge_requests/1. Don't think anyone with access is paying attention to Gitlab yet. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 421816] Setting transparency of a selection in KolourPaint
https://bugs.kde.org/show_bug.cgi?id=421816 --- Comment #3 from secretagent0...@gmail.com --- Let me correct my previous comment. It shouldn't be difficult even for setting selection more opaque. Let's see first how to make selection more transparent. For instance, if we want to reduce alpha by x%. Then: An = Ao*(100-x)/100 Where Ao is old alpha value, and An is new alpha value. Now, if we want to make selection more opaque, we can do the same thing with 255-An and 255-Ao, namely: 255-An = (255-Ao)*(100-x)/100, which gives us An = 255-(255-Ao)*(100-x)/100 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 350365] Battery monitor in tray randomly shows there is no battery
https://bugs.kde.org/show_bug.cgi?id=350365 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 419844] Dolphin crashes when trying to create a file from the right-click menu
https://bugs.kde.org/show_bug.cgi?id=419844 --- Comment #21 from Matthias Fehring --- Created attachment 128759 --> https://bugs.kde.org/attachment.cgi?id=128759=edit Dolphin Valgrind Crash With valgrind, dolphin crashes for me directly after startup. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 421816] Setting transparency of a selection in KolourPaint
https://bugs.kde.org/show_bug.cgi?id=421816 --- Comment #2 from secretagent0...@gmail.com --- If you are talking about the option to set whether the background is transparent or opaque, it doesn't solve my problem, because then only the background color will be transparent, and it will be fully transparent. I was thinking something like changing alpha of all that is selected for all colors (you can see what the alpha channel does by double clicking on the color palette and changing alpha for some color). For instance, it would be nice to have some slider that when moved fully to the left would make the entire selection completely transparent, and when moved fully to the right would make it completely opaque (if possible, see below). Now, here is the tricky part. It shouldn't just set alpha the same for everything selected. If I have in my selection some part that has alpha set to 255 (completely opaque), and some other part with alpha set to 128 (half transparent), then it should change alpha proportionally to that value. Now, that might complicate things to make everything opaque when pushing slider to the right, but at least it shouldn't be too difficult to implement pushing slider to the left (the part that makes selection more transparent). This option could be added to Selection -> More Effects... -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 415854] kscreenlocker_greet crashes when setting video(qml) wallpaper
https://bugs.kde.org/show_bug.cgi?id=415854 winicius.c...@gmail.com changed: What|Removed |Added CC||winicius.c...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 417384] File transfer notification cannot be closed
https://bugs.kde.org/show_bug.cgi?id=417384 --- Comment #1 from Christians --- Created attachment 128758 --> https://bugs.kde.org/attachment.cgi?id=128758=edit persistent notification -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 417384] File transfer notification cannot be closed
https://bugs.kde.org/show_bug.cgi?id=417384 Christians changed: What|Removed |Added CC||scr...@vollbio.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398288] digikam no write access to folder
https://bugs.kde.org/show_bug.cgi?id=398288 --- Comment #21 from David Griffiths --- Drive C: in the laptop is the ONLY drive! I tried disabling UAC and it did not solve the problem. It seems the write access test is too sensitive ?? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421933] Reopening unnamed autosave produces an error dialog
https://bugs.kde.org/show_bug.cgi?id=421933 --- Comment #5 from Ahab Greybeard --- On debian 10 MATE, I've noticed that if you change XDG_PICTURES_DIR then you need to Kill Caja (it will restart) to update the folders to the user-dirs.dirs entries. The autosave file in this situation is initially written to the $HOME folder. The question would be why is it moved to the Pictures folder after you say OK to opening it? Also, why is it not deleted from there if you Save As after working on it? This seems to be a more particular and Linux specific variant of https://bugs.kde.org/show_bug.cgi?id=363971 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 404073] In "Save as" dialog file name is not completing when is present extension
https://bugs.kde.org/show_bug.cgi?id=404073 --- Comment #2 from Piotr Mierzwinski --- (In reply to Méven Car from comment #1) > This assumes you want to overwrite your file or at least base your file > naming on existing files, which FileWidgets can't guess for the users. > So I believe the behavior is fine. No. Otherwise also completing name without extension would meant that I want to overwrite existing name, because I can select name from a list of names already existing files, whereas I want only use part of this name. I'm not sure, maybe I wasn't clear earlier. I meant that pup up list doesn't appear if I start typing in case if extension of file is present in field. > Clicking on the desired file in the view would give the result you expect. Yes. So why we have completing at all? We can click on file name on the list, ritght? I would like to get suggestions of names just without take your hands off the keyboard. The same what I get if I start typing name when field is empty. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416140] Sub-pixel font rendering shows "RGB" in the KCM, but is not actually applied
https://bugs.kde.org/show_bug.cgi?id=416140 --- Comment #25 from Tony --- I forgot to mention that on first access to KCM fonts, if you do not Accept the settings, next times you are being asked to accept over and over, probably because file fonts.conf is not created. Once you accept, file is created, requests finish and accesses to KCM fonts are normal. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421819] Dolphin crashes when creating a folder with right click
https://bugs.kde.org/show_bug.cgi?id=421819 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Elvis Angelaccio --- *** This bug has been marked as a duplicate of bug 419844 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 419844] Dolphin crashes when trying to create a file from the right-click menu
https://bugs.kde.org/show_bug.cgi?id=419844 Elvis Angelaccio changed: What|Removed |Added CC||more...@morenji.com --- Comment #20 from Elvis Angelaccio --- *** Bug 421819 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422034] New: Krita won't let me render image sequence with frames "starting" past 500?
https://bugs.kde.org/show_bug.cgi?id=422034 Bug ID: 422034 Summary: Krita won't let me render image sequence with frames "starting" past 500? Product: krita Version: 4.2.9 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: michellehar...@outlook.com Target Milestone: --- Created attachment 128757 --> https://bugs.kde.org/attachment.cgi?id=128757=edit "First frame" option locks in at 500 max, yet my "Last frame" option can extremely high SUMMARY I'm trying to render an image sequence from Krita that's about 12 frames. It's at 804 frames in, yet it won't let me make the rendering start anywhere past 500 frames (but lets the "last" frame be as high as I want). Also also, not sure this is important, but there isn't any heavy images/actual rendered animations in this file, it's essentially just sloppy sketches in short intervals I have broken up over the timeline. I was told it sounded like a limitation issue I have that might need to be removed, and I needed to report it here. STEPS TO REPRODUCE 1. Attempt to render image sequence (or any sequence for that matter) 2. Set which frame number you want the sequence to start rendering at 3. OBSERVED RESULT Will go no higher than 500 frames in. EXPECTED RESULT Should allow me to go higher. 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.
[okular] [Bug 421984] Add adress bar, w current page ie [path/to/doc/doc.pdf#page=43], use as a link
https://bugs.kde.org/show_bug.cgi?id=421984 --- Comment #6 from David Hurka --- (In reply to 9juhnke from comment #5) > Of course I can assemble such "links" by hand. I really wonder about your interesting workflow. Can you compile Okular yourself? If so, I can give you a patch for copying such links and “pasting” them. > In the same way, one could also discuss using a browser whether it actually > needs an address line. Yeah. After scaling down the link-click frequency of a web browser to Okular, it probably doesn’t need an address bar. (And if Firefox actually had no address bar, it would even be less broken...) There are people who actually just type “google” in the Bing search bar, just to visit google.com, where they enter “example.com” ;) > > There is already a dedicated [...] > > The question is, what speaks for dedicated. It has several buttons which are useful for a search bar. Usually I don’t set case sensitivity for an address bar, but people have weird workflows sometimes. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 419844] Dolphin crashes when trying to create a file from the right-click menu
https://bugs.kde.org/show_bug.cgi?id=419844 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org --- Comment #19 from Elvis Angelaccio --- Those who can reproduce the crash: please provide a valgrind log as described here: https://community.kde.org/Dolphin/FAQ/Crashes -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 419844] Dolphin crashes when trying to create a file from the right-click menu
https://bugs.kde.org/show_bug.cgi?id=419844 Elvis Angelaccio changed: What|Removed |Added CC||cont...@symbioxy.com --- Comment #18 from Elvis Angelaccio --- *** Bug 421807 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421807] Dolphin crashes when creating new folder
https://bugs.kde.org/show_bug.cgi?id=421807 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Elvis Angelaccio --- *** This bug has been marked as a duplicate of bug 419844 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 417749] Creating a file on a Samba share crashes Dolphin
https://bugs.kde.org/show_bug.cgi?id=417749 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org --- Comment #4 from Elvis Angelaccio --- @Nate: the valgrind log seems to point to the dropbox plugin. Can you try to disable it? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416140] Sub-pixel font rendering shows "RGB" in the KCM, but is not actually applied
https://bugs.kde.org/show_bug.cgi?id=416140 --- Comment #24 from Tony --- Created attachment 128756 --> https://bugs.kde.org/attachment.cgi?id=128756=edit Screenshots after link on neon-user -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416140] Sub-pixel font rendering shows "RGB" in the KCM, but is not actually applied
https://bugs.kde.org/show_bug.cgi?id=416140 --- Comment #23 from Tony --- Created attachment 128755 --> https://bugs.kde.org/attachment.cgi?id=128755=edit Screenshots before link on neon-user -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416140] Sub-pixel font rendering shows "RGB" in the KCM, but is not actually applied
https://bugs.kde.org/show_bug.cgi?id=416140 --- Comment #22 from Tony --- I can add a comment: fresh neon user-edition installation (20200514), first access in KCM fonts, we have the button Apply enabled and are being asked to Accept, Discard, Delete with no action done. This happens only the first time. Next accesses in KCM fonts are good: you do nothing, you are not being asked anything. News is, on the first access, if you Accept the settings, the file ~/.config/fontconfig/fonts.conf is created and it contains the setting: rgb that applies rgb-subpixel rendering without creating the global link. Screenshots have been added. So, now the settings actually reflect the machine status. Last problem left is creating the fonts.conf without forcing the user to Accept a request he has never done. -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 422033] New: Break never counts down to zero in Wayland
https://bugs.kde.org/show_bug.cgi?id=422033 Bug ID: 422033 Summary: Break never counts down to zero in Wayland Product: rsibreak Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aa...@kde.org Reporter: i...@bordenrhodes.com Target Milestone: --- RSIBreak works fairly well in KDE running on X on Debian Bullseye. It has short breaks and long breaks and when the break comes up the pop-up appears and counts down however many seconds I specify (unless I touch the mouse or keyboard) then goes away until the next break. In Wayland KDE, behaviour is similar EXCEPT when it's time to take a break. The pop-up appears in the top left corner of my screen for some reason, which is irritating but not fatal. The timer will start at the predetermined break duration. After one second, however, having not touched the computer at all, it will reset the countdown. It does this forever until I click "Skip break" I am trying to switch to Wayland, so I have been able to reproduce this bug every time for the past two days - which is as long as I have been trying to use Wayland. STEPS TO REPRODUCE 1. Run RSIBreak normally from within KDE running on top of Wayland. 2. Wait for the break pop-up to appear. OBSERVED RESULT Break timer keeps resetting after one second, meaning that it never gets to zero unless the break is skipped. EXPECTED RESULT As in X, RSIBreak on Wayland should count down to zero if there is no contact with the computer. If there is contact with the computer, the timer should reset and start the countdown again. SOFTWARE/OS VERSIONS Linux: 5.6.0-1-amd64 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398811] Settings window should never let the categories list get a vertical scrollbar
https://bugs.kde.org/show_bug.cgi?id=398811 --- Comment #13 from Patrick Silva --- I have never changed any icons size setting on my system. I have already found the culprit: my font settings. This bug occurs on Arch and neon unstable when I use lebaration sans font with papirus or newaita icon themes. No scroll bar when any of the mentioned icon themes is used with default font settings. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421933] Reopening unnamed autosave produces an error dialog
https://bugs.kde.org/show_bug.cgi?id=421933 --- Comment #4 from Anna Medonosova --- I observed the issue while running the AppImage with isolated config and home directories for testing (https://invent.kde.org/snippets/741). In that case, XDG_PICTURES_DIR is set to system-wide default, which is $HOME/Pictures. However, the Pictures directory does not exist within the home dir. Another option to trigger the error is to temporarily change XDG_PICTURES_DIR (on my Ubuntu it is in ~/.config/user-dirs.dirs). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422010] regression: GTK theme doesn't apply to flatpak apps since Plasma 5.18.5
https://bugs.kde.org/show_bug.cgi?id=422010 --- Comment #5 from Mikhail Zolotukhin --- In the next version of Plasma (5.19) there is no option of Breeze-Dark scheme in the list any longer, since the Breeze grabs its colors from the color scheme. Can you reproduce the issues with other themes? -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 318034] Trailing spaces are not removed from file or directory name
https://bugs.kde.org/show_bug.cgi?id=318034 Toni Asensi Esteve changed: What|Removed |Added CC||toni.ase...@kdemail.net --- Comment #1 from Toni Asensi Esteve --- As it was shown in [news from yesterday](https://pointieststick.com/2020/05/23/this-week-in-kde-we-have-migrated-to-gitlab/): KDE developers also found this "remove trailing whitespaces" dilemma: - Bug 421075 - Trailing Whitespace when creating directories or files https://bugs.kde.org/show_bug.cgi?id=421075 where it was argued: Consistency with other file managers. - Nautilus, Thunar, Nemo, etc all prevent you from entering a name with a trailing or leading white space. [...] - Show inline warning when creating items with leading or trailing spaces https://phabricator.kde.org/D29483 "This is a somewhat unusual thing for a user to do intentionally, so let's show a warning to make sure they're aware that they're doing it." - Also related: - Show feedback inline when creating new files or folders https://phabricator.kde.org/D21907 https://phabricator.kde.org/file/data/sl4mjdloflybh5gu3z26/PHID-FILE-jufyl66qrkil2lfwfrgn/Peek_2019-06-19_17-59.gif -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371455] Slide show wallpaper massively slows down login when many images are configured
https://bugs.kde.org/show_bug.cgi?id=371455 --- Comment #41 from Sébastien P. --- It looks fine on 5.18.5. I switched yesterday and the login was quick, like before. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392239] CR linebreaks in message view are not shown
https://bugs.kde.org/show_bug.cgi?id=392239 --- Comment #10 from kzi --- Salut Laurent, > But which mailer generates it ? While I think KMail should be capable do deal with any kind of line break, no matter the source, the answer (taken from the header) is: esmtps (Exim 4.92.3) I received the mail from the accounting of a web shop as an invoice carrier (hence the nondisclosure in the first place), so it's likely to originate from some kind of ERP system. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 421561] Icon of Weather Report applet changes in system tray settings depending on visibility setting
https://bugs.kde.org/show_bug.cgi?id=421561 --- Comment #6 from Patrick Silva --- yes, but this report is about the icon changing depending on its visibility setting. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 422032] New: ImageColors: paletteChanged not emitted if source property is changed after object creation
https://bugs.kde.org/show_bug.cgi?id=422032 Bug ID: 422032 Summary: ImageColors: paletteChanged not emitted if source property is changed after object creation Product: frameworks-kirigami Version: Master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: jbb.m...@gmx.de Target Milestone: Not decided SUMMARY First of all: I'm not 100% sure this is a bug, possibly my user code is wrong. If I set the source property of the ImageColors type on object creation, everything works as expected, after some time paletteChanged() is emitted. But if I set the source to something else later using java script, runUpdate() is not called anymore, and no new palette is generated. STEPS TO REPRODUCE https://invent.kde.org/plasma/plasma-phone-components/-/merge_requests/66 can be used to reproduce this. The relevant code is in containments/homescreen/package/contents/ui/launcher/LauncherGrid.qml. The source property is set on app startup. OBSERVED RESULT paletteChanged() is not emitted again. EXPECTED RESULT paletteChanged() is emitted again. SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 422001] KF5 5.70.0 regression: Dolphin shows same SMB share twice
https://bugs.kde.org/show_bug.cgi?id=422001 --- Comment #4 from Harald Sitter --- one is discovered over netbios/smb1. the other is discovered over dnssd. server-side comments impact the entry name for netbios/smb1 and that's why there's two entries. the 'SMB/CIFS' comment makes the name different and because of that we simply don't know that they are the same remote. (that said, I'm not sure they would be the de-duplicated either way in 20.04 because of how NB and DNSSD interact with each other - bug #421624) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422010] regression: GTK theme doesn't apply to flatpak apps since Plasma 5.18.5
https://bugs.kde.org/show_bug.cgi?id=422010 --- Comment #4 from Peter Eszlari --- I'm switching between Breeze and Breeze-Dark. How quick I login again, seems to play a role. When I fix the flatpak theme (by switching back and forth between Breeze and Breeze-Dark), then logout and I wait some seconds before the next login, I can get it to save the settings for flatpak apps for the next three logins (it always stops remembering after that). After a quick re-login, it never works correctly (the theme doesn't get applied to flatpak apps). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394890] Compositing disabled on external monitor connection if background contrast effect is disabled
https://bugs.kde.org/show_bug.cgi?id=394890 beojan changed: What|Removed |Added Version|5.12.5 |5.18.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 394890] Compositing disabled on external monitor connection if background contrast effect is disabled
https://bugs.kde.org/show_bug.cgi?id=394890 beojan changed: What|Removed |Added CC||beo...@gmail.com --- Comment #11 from beojan --- I'm experiencing the same issue with kwin_x11 5.18.5. It persists even with "Allow applications to block compositing" switched off. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 421561] Icon of Weather Report applet changes in system tray settings depending on visibility setting
https://bugs.kde.org/show_bug.cgi?id=421561 --- Comment #5 from Konrad Materka --- It has different icons for: default state, paying and paused. There is even a bug, icon is not available if media has cover (fixed: Bug 420197) -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 422031] New: KPatience Really Likes Dealing 3 of a kind and 3 of another kind.
https://bugs.kde.org/show_bug.cgi?id=422031 Bug ID: 422031 Summary: KPatience Really Likes Dealing 3 of a kind and 3 of another kind. Product: kpat Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: co...@kde.org Reporter: junkm...@stanking.org CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY Initial deal has 3 of a kind (say, 3 queens) and often adds 3 of another kind (say, 3 8's) then the 4th queen will show up within 3 deals (dealing 3 cards). It's just annoying and almost unwinnable. STEPS TO REPRODUCE 1. start klondike 2. start kpatience 3. play OBSERVED RESULT as stated above EXPECTED RESULT a bit more randomness? SOFTWARE/OS VERSIONS Xubuntu ADDITIONAL INFORMATION I'm old. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422030] Pkexec does not work with Dolphin service menus on 20.04
https://bugs.kde.org/show_bug.cgi?id=422030 --- Comment #1 from Don B. Cilly --- 100% of people who have tried it (3 of 3 :·) confirm it. I tried it on TWO 20.04 machines. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 421914] Notification from Dolphin shows wrong amount of deleted files when I delete a folder located in a Samba share
https://bugs.kde.org/show_bug.cgi?id=421914 Ahmad Samir changed: What|Removed |Added Product|frameworks-kio |kio-extras Component|general |Samba CC||a.samir...@gmail.com Assignee|fa...@kde.org |plasma-b...@kde.org Version|5.70.0 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 422030] New: Pkexec does not work with Dolphin service menus on 20.04
https://bugs.kde.org/show_bug.cgi?id=422030 Bug ID: 422030 Summary: Pkexec does not work with Dolphin service menus on 20.04 Product: dolphin Version: 20.04.1 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: donbci...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY On Kubuntu 20.04, service menus requiring elevated privileges. No pkexec pop-up. If I try pkexec from konsole, it works. In a Dolphin service menu, it does not. The same exact service menus work on neon 5.18 and and Kubuntu 18.04 and not on K20 STEPS TO REPRODUCE 1. Run a service menu that requires pkexec on Kubuntu 20.04 2. Run it on neon 5.18 or Kubuntu 18.04 3. OBSERVED RESULT They don't work on K20. No password pop-up. EXPECTED RESULT They should :·) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04/5.18.5 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I'm on neon ATM, I guess Qt and FW version not relevant, Plasma is the same on both, one works, the other doesn't. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 417310] Incorrect resolution with HiDPI scaling on
https://bugs.kde.org/show_bug.cgi?id=417310 k...@ca.sh13.net changed: What|Removed |Added CC||andrew.crouthamel@kdemail.n ||et --- Comment #3 from k...@ca.sh13.net --- *** Bug 389754 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 389754] RDP does not scale with HiDPI screen
https://bugs.kde.org/show_bug.cgi?id=389754 k...@ca.sh13.net changed: What|Removed |Added CC||k...@ca.sh13.net Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from k...@ca.sh13.net --- *** This bug has been marked as a duplicate of bug 417310 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421210] digiKam 5.9.0-1+b1 refuses to start since LMDE4 Debbie upgrade
https://bugs.kde.org/show_bug.cgi?id=421210 rob.f...@sbcglobal.net changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #4 from rob.f...@sbcglobal.net --- Was able to install via AppImage, although why it's not up to date on the download page makes no sense to me, as it would've been a non-issue for me. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392239] CR linebreaks in message view are not shown
https://bugs.kde.org/show_bug.cgi?id=392239 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #9 from Laurent Montel --- indeed I confirm it. But which mailer generates it ? It seems that we can't load it from thunderbird. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 421561] Icon of Weather Report applet changes in system tray settings depending on visibility setting
https://bugs.kde.org/show_bug.cgi?id=421561 --- Comment #4 from Patrick Silva --- humm, icon of Media Player applet in systray settings is always the same on my system. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.71.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 421561] Icon of Weather Report applet changes in system tray settings depending on visibility setting
https://bugs.kde.org/show_bug.cgi?id=421561 --- Comment #3 from Konrad Materka --- Then we have the same issue (inconsistent behavior) for Media Player and probably other applets. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422029] New: System Settings crash when trying to start Yast
https://bugs.kde.org/show_bug.cgi?id=422029 Bug ID: 422029 Summary: System Settings crash when trying to start Yast Product: systemsettings Version: 5.18.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sammae...@gmail.com Target Milestone: --- Application: systemsettings5 (5.18.5) Qt Version: 5.14.1 Frameworks Version: 5.70.0 Operating System: Linux 5.6.12-1-default x86_64 Windowing system: X11 Distribution: openSUSE Tumbleweed -- Information about the crash: - What I was doing when the application crashed: clicked on Yast in System Settings The duplicates suggested to me when submitting all linked to original reports stating it's fixed, however it happens here with 100% rate. Launching Yast manually works perfectly fine. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f440d9f3f00 (LWP 5556))] Thread 11 (Thread 0x7f43f71af700 (LWP 5567)): #0 0x7f440eeeb795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f440329ff13 in ?? () from /usr/lib64/dri/swrast_dri.so #2 0x7f4403296a67 in ?? () from /usr/lib64/dri/swrast_dri.so #3 0x7f440eee4efa in start_thread () from /lib64/libpthread.so.0 #4 0x7f44103403bf in clone () from /lib64/libc.so.6 Thread 10 (Thread 0x7f4400a2a700 (LWP 5566)): #0 0x7f440eeeb795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f440329ff13 in ?? () from /usr/lib64/dri/swrast_dri.so #2 0x7f4403296a67 in ?? () from /usr/lib64/dri/swrast_dri.so #3 0x7f440eee4efa in start_thread () from /lib64/libpthread.so.0 #4 0x7f44103403bf in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7f440122b700 (LWP 5565)): #0 0x7f440eeeb795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f440329ff13 in ?? () from /usr/lib64/dri/swrast_dri.so #2 0x7f4403296a67 in ?? () from /usr/lib64/dri/swrast_dri.so #3 0x7f440eee4efa in start_thread () from /lib64/libpthread.so.0 #4 0x7f44103403bf in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7f4401a2c700 (LWP 5564)): #0 0x7f440eeeb795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f440329ff13 in ?? () from /usr/lib64/dri/swrast_dri.so #2 0x7f4403296a67 in ?? () from /usr/lib64/dri/swrast_dri.so #3 0x7f440eee4efa in start_thread () from /lib64/libpthread.so.0 #4 0x7f44103403bf in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f440222d700 (LWP 5563)): #0 0x7f440eeeb795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f44032a7d25 in ?? () from /usr/lib64/dri/swrast_dri.so #2 0x7f4403296a47 in ?? () from /usr/lib64/dri/swrast_dri.so #3 0x7f440eee4efa in start_thread () from /lib64/libpthread.so.0 #4 0x7f44103403bf in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f4402a2e700 (LWP 5562)): #0 0x7f440eeeb795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f44032a7d25 in ?? () from /usr/lib64/dri/swrast_dri.so #2 0x7f4403296a47 in ?? () from /usr/lib64/dri/swrast_dri.so #3 0x7f440eee4efa in start_thread () from /lib64/libpthread.so.0 #4 0x7f44103403bf in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f4408a13700 (LWP 5561)): #0 0x7f440eeeb795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f44032a7d25 in ?? () from /usr/lib64/dri/swrast_dri.so #2 0x7f4403296a47 in ?? () from /usr/lib64/dri/swrast_dri.so #3 0x7f440eee4efa in start_thread () from /lib64/libpthread.so.0 #4 0x7f44103403bf in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f4409214700 (LWP 5560)): #0 0x7f440eeeb795 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f44032a7d25 in ?? () from /usr/lib64/dri/swrast_dri.so #2 0x7f4403296a47 in ?? () from /usr/lib64/dri/swrast_dri.so #3 0x7f440eee4efa in start_thread () from /lib64/libpthread.so.0 #4 0x7f44103403bf in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f440aa28700 (LWP 5559)): #0 0x7f4410335acf in poll () from /lib64/libc.so.6 #1 0x7f440e4e49de in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f440e4e4aff in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f44108debeb in QEventDispatcherGlib::processEvents (this=0x7f43fc000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f4410886b7b in QEventLoop::exec (this=this@entry=0x7f440aa27d70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #5 0x7f44106b15ce in QThread::exec (this=) at
[frameworks-kio] [Bug 421961] File transfer from intern SSD (ext4) to external HDD (ntfs) freezes OS for about 10 seconds
https://bugs.kde.org/show_bug.cgi?id=421961 Nate Graham changed: What|Removed |Added Version|20.04.0 |5.70.0 Assignee|dolphin-bugs-n...@kde.org |fa...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||kdelibs-b...@kde.org, ||n...@kde.org Component|general |general Product|dolphin |frameworks-kio --- Comment #1 from Nate Graham --- What processes were consuming all that CPU? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421962] Tooltip gets huge left margin when metadata fields contain much information
https://bugs.kde.org/show_bug.cgi?id=421962 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||n...@kde.org Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 226900] week numbers in month view
https://bugs.kde.org/show_bug.cgi?id=226900 gjditchfi...@acm.org changed: What|Removed |Added Version Fixed In||5.14.1 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED CC||gjditchfi...@acm.org --- Comment #1 from gjditchfi...@acm.org --- The calendar that appears in the left sidebar of the Month view (and most other views) now displays week numbers. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 422007] Latte dock does not allow window title applet to take up full dock space on newer versions
https://bugs.kde.org/show_bug.cgi?id=422007 --- Comment #4 from Mitch --- Can confirm Latte git works perfectly with window-appmenu git. Thanks for the fix! -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 392239] CR linebreaks in message view are not shown
https://bugs.kde.org/show_bug.cgi?id=392239 xchain changed: What|Removed |Added Ever confirmed|0 |1 Summary|Messages or parts with |CR linebreaks in message |Content-Transfer-Encoding: |view are not shown |base64 have no line breaks | |displayed | Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #8 from xchain --- Thanks, test cases are always helpful, as they often allow to better pinpoint the core issue. Glad you found the cause! Can confirm that CR linebreaks in base64-encoded messages are not displayed using current git master. In fact, this is not really specific to base64 encoding: Converting any mbox file (e.g. with "Content-Transfer-Encoding: 7Bit") with "unix2mac" to use CR linebreaks yields an empty message view already, and converting only the mail body shows the header at least, but misses linebreaks in the message text. Note that only the message view is affected. When opening the "Message as Plain Text" window through "View Source", the linebreaks are displayed just fine. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 420766] Envelope From is empty on outgoing mails
https://bugs.kde.org/show_bug.cgi?id=420766 --- Comment #9 from xchain --- Tim: After upgrading to 5.14.1, is the issue gone for you too? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422010] regression: GTK theme doesn't apply to flatpak apps since Plasma 5.18.5
https://bugs.kde.org/show_bug.cgi?id=422010 --- Comment #3 from Mikhail Zolotukhin --- Still cannot reproduce. There were no changes in GTK intergation codebase in 5.18.5. What GTK theme are you applying? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 422007] Latte dock does not allow window title applet to take up full dock space on newer versions
https://bugs.kde.org/show_bug.cgi?id=422007 Michail Vourlakos changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #3 from Michail Vourlakos --- (In reply to Mitch from comment #2) > You have it backwards, the 9.11 behavior is desired. The applet will not > fill available space even when specifically told to on the git version, when > I want it to fill all available space because it looks awful to me stopping > partway. Sorry I was right... Latte works just fine, appmenu applet had the issue and now it solved with https://github.com/psifidotos/applet-window-appmenu/commit/2b4dc60f9e9370029f5865c33e3007535bde54c4 either you will wait for a new release or build/install appmenu by yourself from master branch -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422010] regression: GTK theme doesn't apply to flatpak apps since Plasma 5.18.5
https://bugs.kde.org/show_bug.cgi?id=422010 Peter Eszlari changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- Ever confirmed|0 |1 --- Comment #2 from Peter Eszlari --- Restarting xsettingsd or changing the theme does indeed make it apply the theme to flatpak apps, but after a logout the effect is gone and you have to redo it everytime. I wouldn't consider this " WORKSFORME", and it wasn't like this in 5.18.4. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416640] Shadowless task switcher on Wayland
https://bugs.kde.org/show_bug.cgi?id=416640 --- Comment #5 from Patrick Silva --- (In reply to Vlad Zahorodnii from comment #1) > Fortunately, shadows will be back in KDE Plasma 5.19. Plasma 5.19 beta was released and task switcher is still shadowless. :( -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 417310] Incorrect resolution with HiDPI scaling on
https://bugs.kde.org/show_bug.cgi?id=417310 --- Comment #2 from Yichao Yu --- Note that there is a fix from a year ago waiting for review @ https://phabricator.kde.org/D20790. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422028] New: Plasma or kWin crashes every time after suspend
https://bugs.kde.org/show_bug.cgi?id=422028 Bug ID: 422028 Summary: Plasma or kWin crashes every time after suspend Product: kwin Version: 5.14.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: marius.alks...@gmail.com Target Milestone: --- Application: kwin_x11 (5.14.5) Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 4.19.0-6-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: My usual session - one monitor, two virtual desktops, some activities (but rarely used). Clock is showing time in 24:00 and date in ISO format. SDDM asks me for a password after suspend and then my main and only panel on the bottom of the screen refuses to repaint. This happens every time my laptop resumes from standby. I am using custom shortcut to run "killall plasmashell; kstart plasmashell" as a workaround. I also use some custom windows rules. The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7eff26b38940 (LWP 3443))] Thread 7 (Thread 0x7eff1d6fc700 (LWP 19207)): #0 0x7eff2d4b600c in futex_wait_cancelable (private=0, expected=0, futex_word=0x55e3dea11fb0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7eff2d4b600c in __pthread_cond_wait_common (abstime=0x0, mutex=0x55e3dea11f60, cond=0x55e3dea11f88) at pthread_cond_wait.c:502 #2 0x7eff2d4b600c in __pthread_cond_wait (cond=0x55e3dea11f88, mutex=0x55e3dea11f60) at pthread_cond_wait.c:655 #3 0x7eff2e2c721b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7eff2d010009 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7eff2d01026a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7eff2e2c6a67 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7eff2d4affa3 in start_thread (arg=) at pthread_create.c:486 #8 0x7eff2f8c04cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7eff0a38b700 (LWP 8372)): #0 0x7eff2f8b591e in __GI_ppoll (fds=, nfds=, timeout=, sigmask=) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7eff2e4bb721 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7eff2e4bcb99 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7eff2e46d15b in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7eff2e2bce76 in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7eff2e2c6a67 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7eff2d4affa3 in start_thread (arg=) at pthread_create.c:486 #7 0x7eff2f8c04cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7eff1700 (LWP 16639)): #0 0x7eff2d4b600c in futex_wait_cancelable (private=0, expected=0, futex_word=0x55e3de8a5210) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7eff2d4b600c in __pthread_cond_wait_common (abstime=0x0, mutex=0x55e3de8a51c0, cond=0x55e3de8a51e8) at pthread_cond_wait.c:502 #2 0x7eff2d4b600c in __pthread_cond_wait (cond=0x55e3de8a51e8, mutex=0x55e3de8a51c0) at pthread_cond_wait.c:655 #3 0x7eff2e2c721b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7eff2d010009 in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7eff2d01026a in () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7eff2e2c6a67 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7eff2d4affa3 in start_thread (arg=) at pthread_create.c:486 #8 0x7eff2f8c04cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7eff09b8a700 (LWP 3822)): #0 0x7eff2d4b600c in futex_wait_cancelable (private=0, expected=0, futex_word=0x7eff2deb1fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7eff2d4b600c in __pthread_cond_wait_common (abstime=0x0, mutex=0x7eff2deb1f68, cond=0x7eff2deb1f90) at pthread_cond_wait.c:502 #2 0x7eff2d4b600c in __pthread_cond_wait (cond=0x7eff2deb1f90, mutex=0x7eff2deb1f68) at pthread_cond_wait.c:655 #3 0x7eff2ddbbe6a in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7eff2ddbbe89 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7eff2d4affa3 in start_thread (arg=) at pthread_create.c:486 #6 0x7eff2f8c04cf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7eff1f37a700 (LWP 3690)): #0 0x7eff2f8b5916 in __GI_ppoll (fds=0x7eff0c000d28, nfds=1, timeout=,
[okular] [Bug 422027] New: Option to suppress power management
https://bugs.kde.org/show_bug.cgi?id=422027 Bug ID: 422027 Summary: Option to suppress power management Product: okular Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: kroot.pa...@gmail.com Target Milestone: --- Currently, when reading a book, it is annoying when the "dim screen"/"screen off" feature of Plasma power management happens after no activity for some time. It would be nice if Okular could act similar to media players, and keep screen on forever. Having this as a toggle (selected per document, with a global default) would be an extra bonus. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 422007] Latte dock does not allow window title applet to take up full dock space on newer versions
https://bugs.kde.org/show_bug.cgi?id=422007 --- Comment #2 from Mitch --- You have it backwards, the 9.11 behavior is desired. The applet will not fill available space even when specifically told to on the git version, when I want it to fill all available space because it looks awful to me stopping partway. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422026] New: Night color resets inverted color scheme
https://bugs.kde.org/show_bug.cgi?id=422026 Bug ID: 422026 Summary: Night color resets inverted color scheme Product: systemsettings Version: 5.18.5 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_nightcolor Assignee: plasma-b...@kde.org Reporter: a.skemb...@gmail.com CC: kwin-bugs-n...@kde.org Target Milestone: --- SUMMARY When the system colors have been inverted and night color is activated, each time the color is shifted the inversion is reset to normal colors. Since the shift to night color is applied progressively every few minutes, the color inversion reset happens many times until the night color temp has been finally reached. This is a bit frustrating when trying to work with inverted colors during these hours. STEPS TO REPRODUCE 1. Activate night color 2. Have system colors inverted when night color is activated 3. OBSERVED RESULT System colors revert to normal colors every time the temperature is shifted towards the expected target value. EXPECTED RESULT Color inversion should remain unaffected as temperature is shifted. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenSUSE Tumbleweed, (available in About System) KDE Plasma Version: Plasma 18.5 KDE Frameworks Version: 5.70 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 421186] Android and Plasma is not communicating on phone's portable WiFi HOTSPOT
https://bugs.kde.org/show_bug.cgi?id=421186 Anjani Kumar changed: What|Removed |Added CC||anjanik...@gmail.com --- Comment #1 from Anjani Kumar --- (In reply to Durrani from comment #0) > Created attachment 128254 [details] > Check the "You're not connected to a WiFi" message > > SUMMARY > Android and Plasma is not communicating on phone's portable WiFi HOTSPOT > > STEPS TO REPRODUCE > 1. Turn on portable WiFi hotspot feature on your android device. > 2. Connect your KDE Plasma device to the android's WiFi hotspot. > 3. Open up kde Connect on android device and you will see the message. > "You're not connected to a WiFi network, so you may not be able to see any > devices. Click here to enable Wi-Fi" > > > OBSERVED RESULT > Linux host and android client do not communicate on portable WiFi hotspot > but instead work on WiFi. > > EXPECTED RESULT > Both should communicate on external WiFi device as well as using portable > WiFi hotspot just like in previous version of KDE Connect Android. > > Android Versions: > KDE Connect: 1.14.2 > Android: 8.1.0 (Oreo) > Kernel: 3.10.73-g309d642 > Device: Nexus 6P > > SOFTWARE/OS VERSIONS > Kernel: 5.3.0-51-generic > Linux/KDE neon: 5.18 > KDE Plasma Version: 5.18.5 > KDE Frameworks Version: 5.69.0 > Qt Version: 5.14.2 > > > ADDITIONAL INFORMATION What happens on the desktop side? Can you see your device from the kdeconnect desktop app? This seems weird. KDEConnect works from phone hotspot as well. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 417310] Incorrect resolution with HiDPI scaling on
https://bugs.kde.org/show_bug.cgi?id=417310 k...@ca.sh13.net changed: What|Removed |Added CC||k...@ca.sh13.net --- Comment #1 from k...@ca.sh13.net --- Created attachment 128754 --> https://bugs.kde.org/attachment.cgi?id=128754=edit Screenshot showing the issue. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422010] regression: GTK theme doesn't apply to flatpak apps since Plasma 5.18.5
https://bugs.kde.org/show_bug.cgi?id=422010 Mikhail Zolotukhin changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Mikhail Zolotukhin --- Cannot reproduce on Kubuntu 20.04, but xsettingsd (which is responsible for flatpak apps on X11) can be buggy sometimes. I suggest you to restart it a couple of times or to set the theme back and forth a couple of times. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421159] Scrolling by clicking the scroll bar is reset by scrolling with scroll wheel
https://bugs.kde.org/show_bug.cgi?id=421159 Albert Astals Cid changed: What|Removed |Added CC||keziolio...@gmail.com, ||oliver.san...@tu-dresden.de --- Comment #7 from Albert Astals Cid --- Another regression caused by the QScroller patches. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421159] Scrolling by clicking the scroll bar is reset by scrolling with scroll wheel
https://bugs.kde.org/show_bug.cgi?id=421159 Albert Astals Cid changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #6 from Albert Astals Cid --- Ok, now i understood: * Start in page 1 * Left click on the scrollbar below the slider it self until some pages change and say you're now in page 10 * use the wheel in the viewport (not the scrollbar), you're back to page 1 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 422012] Incorrect account hierarchy if an account is marked as preferred
https://bugs.kde.org/show_bug.cgi?id=422012 Thomas Baumgart changed: What|Removed |Added Latest Commit|https://invent.kde.org/offi |https://invent.kde.org/offi |ce/kmymoney/commit/5412d8e3 |ce/kmymoney/commit/d65ae5a6 |2c85485f047127fb2b0e2edfff5 |dd8d7e4050a04e2dcea1fe63ffb |3ddb4 |66782 Version Fixed In||5.0.9 --- Comment #5 from Thomas Baumgart --- Git commit d65ae5a6dd8d7e4050a04e2dcea1fe63ffb66782 by Thomas Baumgart. Committed on 24/05/2020 at 17:37. Pushed by tbaumgart into branch '5.0'. Fix incorrect account hierarchy if the account is marked as preferred When an account was marked as preferred and the user edited it, the account was moved in the hierarchy tree even though the user did not enter the Hierarchy tab to change anything. When the user opened the Hierarchy tab, there was Favorites category displayed but it should not. This commit solves the issue so that a preferred account is not moved when the user does not want it to. The Favorites catergory is now not displayed in the Hierarchy tab. FIXED-IN: 5.0.9 Signed-off-by: Robert Szczesiak (cherry picked from commit 5412d8e32c85485f047127fb2b0e2edfff53ddb4) M +6-5kmymoney/dialogs/hierarchyfilterproxymodel.cpp M +1-1kmymoney/dialogs/knewaccountdlg.ui https://invent.kde.org/office/kmymoney/commit/d65ae5a6dd8d7e4050a04e2dcea1fe63ffb66782 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420683] Inaccurate decimal precision of South Korean Won (KRW)
https://bugs.kde.org/show_bug.cgi?id=420683 Thomas Baumgart changed: What|Removed |Added Version Fixed In||5.0.9 Latest Commit|https://invent.kde.org/offi |https://invent.kde.org/offi |ce/kmymoney/commit/8025e549 |ce/kmymoney/commit/5c3505f0 |001ebbdbe3f2aa09074dd5a23ed |0cecb57ae89316ec7930990dc85 |06836 |ad400 --- Comment #2 from Thomas Baumgart --- Git commit 5c3505f00cecb57ae89316ec7930990dc85ad400 by Thomas Baumgart. Committed on 24/05/2020 at 17:38. Pushed by tbaumgart into branch '5.0'. Set the minimum unit of KRW into 1 Although the subdivision of South Korean Won exists de jure, it is de facto not used in bank statements and stock price tickers. Only in foreign exchange markets the subdivision is used but they are rounded down when it becomes to accounting. Thus adjust the precision of South Korean Won to 1. FIXED-IN: 5.0.9 (cherry picked from commit 8025e549001ebbdbe3f2aa09074dd5a23ed06836) M +1-1kmymoney/mymoney/mymoneyfile.cpp https://invent.kde.org/office/kmymoney/commit/5c3505f00cecb57ae89316ec7930990dc85ad400 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 420683] Inaccurate decimal precision of South Korean Won (KRW)
https://bugs.kde.org/show_bug.cgi?id=420683 Thomas Baumgart changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/offi ||ce/kmymoney/commit/8025e549 ||001ebbdbe3f2aa09074dd5a23ed ||06836 Status|REPORTED|RESOLVED --- Comment #1 from Thomas Baumgart --- Git commit 8025e549001ebbdbe3f2aa09074dd5a23ed06836 by Thomas Baumgart, on behalf of Shinjo Park. Committed on 24/05/2020 at 17:36. Pushed by tbaumgart into branch 'master'. Set the minimum unit of KRW into 1 Although the subdivision of South Korean Won exists de jure, it is de facto not used in bank statements and stock price tickers. Only in foreign exchange markets the subdivision is used but they are rounded down when it becomes to accounting. Thus adjust the precision of South Korean Won to 1. M +1-1kmymoney/mymoney/mymoneyfile.cpp https://invent.kde.org/office/kmymoney/commit/8025e549001ebbdbe3f2aa09074dd5a23ed06836 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 422012] Incorrect account hierarchy if an account is marked as preferred
https://bugs.kde.org/show_bug.cgi?id=422012 Thomas Baumgart changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/offi ||ce/kmymoney/commit/5412d8e3 ||2c85485f047127fb2b0e2edfff5 ||3ddb4 Resolution|--- |FIXED --- Comment #4 from Thomas Baumgart --- Git commit 5412d8e32c85485f047127fb2b0e2edfff53ddb4 by Thomas Baumgart, on behalf of Robert Szczesiak. Committed on 24/05/2020 at 17:36. Pushed by tbaumgart into branch 'master'. Fix incorrect account hierarchy if the account is marked as preferred When an account was marked as preferred and the user edited it, the account was moved in the hierarchy tree even though the user did not enter the Hierarchy tab to change anything. When the user opened the Hierarchy tab, there was Favorites category displayed but it should not. This commit solves the issue so that a preferred account is not moved when the user does not want it to. The Favorites catergory is now not displayed in the Hierarchy tab. Signed-off-by: Robert Szczesiak M +6-5kmymoney/dialogs/hierarchyfilterproxymodel.cpp M +1-1kmymoney/dialogs/knewaccountdlg.ui https://invent.kde.org/office/kmymoney/commit/5412d8e32c85485f047127fb2b0e2edfff53ddb4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421971] Arrow to show hidden systray icons is missing until an app with systray icon is launched
https://bugs.kde.org/show_bug.cgi?id=421971 --- Comment #6 from Patrick Silva --- Created attachment 128753 --> https://bugs.kde.org/attachment.cgi?id=128753=edit screenshot showing hidden systray icons -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421971] Arrow to show hidden systray icons is missing until an app with systray icon is launched
https://bugs.kde.org/show_bug.cgi?id=421971 --- Comment #5 from Konrad Materka --- When icon appears, can you click on it and attach screenshot? This arrow should be hidden if there are no icons in "hidden" area. Maybe it happens on your system? -- You are receiving this mail because: You are watching all bug changes.
[kxkb] [Bug 264886] System Tray Settings Extra Items Keyboard Layout checkbox creates redundant tray icon
https://bugs.kde.org/show_bug.cgi?id=264886 Konrad Materka changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #20 from Konrad Materka --- Probably the Keyboard Layout applet was removed, I cannot find it anymore. Marking as fixed, feel free to reopen if you find this applet - there is no point in having this indicator in two places. -- You are receiving this mail because: You are watching all bug changes.
