[plasmashell] [Bug 442869] In SDDM, the eye icon to view the password only appears after starting the when the session is already started
https://bugs.kde.org/show_bug.cgi?id=442869 --- Comment #2 from 61kyl...@anonaddy.me --- I didn't get about the lock screen part, sorry. Why the icon appears when locking? I'm curious, hehe -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408144] while the screen is locked user profile picture is displayed incorrectly when falling back to the software plasma renderer
https://bugs.kde.org/show_bug.cgi?id=408144 --- Comment #5 from 61kyl...@anonaddy.me --- Sometimes this happens here (5.22.4) randomly and I didn't even know about Plasma Renderer. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442917] Power profiles slider doesn't show up in Battery and Brightness applet
https://bugs.kde.org/show_bug.cgi?id=442917 --- Comment #10 from David Redondo --- FYI https://gitlab.freedesktop.org/hadess/power-profiles-daemon/-/issues/50 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443088] kwin_wayland crashed in KWin::AbstractWaylandOutput::modeSize() when I logged into another user, logged out, and unlocked my original session
https://bugs.kde.org/show_bug.cgi?id=443088 --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/1474 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443105] New: ffmpeg continues beyond the range specified in Krita.
https://bugs.kde.org/show_bug.cgi?id=443105 Bug ID: 443105 Summary: ffmpeg continues beyond the range specified in Krita. Product: krita Version: nightly build (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: minor Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: healer.ha...@gmail.com Target Milestone: --- Created attachment 142001 --> https://bugs.kde.org/attachment.cgi?id=142001&action=edit Progress bar. SUMMARY If an existing png frames existed in the directory with range 0-970, and you specified Krita to render a new animation from frame 0-100, Krita would overwrite the existing png frames from 0-100; The frames from 101-970 still exist. This would result into a concatenation of the new frame 0-100 and old frame 101-970, and a progress bar like in the attachment. This old frame of 0-970 should have been automatically deleted by Krita after the video is exported, but it's possible to postpone it by cancelling the saving of png frames, or by manually saving it as png frames. STEPS TO REPRODUCE 1. At frame 0, draw a "0". at frame 24, draw a "24". at frame 60, draw a "60". 2. Render animation as png frames with range 0-100. 3. Render animation as video with range 0-30. OBSERVED RESULT Two different frames are concatenated. EXPECTED RESULT Krita renders video from range 0-30. SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Krita Version: 5.0.0-beta1 (git 0986afa) Languages: en_US, en Hidpi: false Qt Version (compiled): 5.12.11 Version (loaded): 5.12.11 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.15063 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 OpenGL Info Vendor: "Google Inc." Renderer: "ANGLE (Intel(R) HD Graphics Direct3D11 vs_5_0 ps_5_0)" Version: "OpenGL ES 3.0 (ANGLE 2.1.0.57ea533f79a7)" Shading language: "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0.57ea533f79a7)" Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format:QSurfaceFormat(version 3.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Version: 3.0 Supports deprecated functions false is OpenGL ES: true QPA OpenGL Detection Info supportsDesktopGL: true supportsAngleD3D11: true isQtPreferAngle: true Hardware Information GPU Acceleration: auto Memory: 1946 Mb Number of Cores: 4 Swap Location: C:/Users/User6/AppData/Local/Temp Current Settings Current Swap Location: C:/Users/User6/AppData/Local/Temp Current Swap Location writable: true Undo Enabled: true Undo Stack Limit: 30 Use OpenGL: true Use OpenGL Texture Buffer: true Disable Vector Optimizations: false Disable AVX Optimizations: false Canvas State: OPENGL_SUCCESS Autosave Interval: 900 Use Backup Files: true Number of Backups Kept: 1 Backup File Suffix: ~ Backup Location: Same Folder as the File Backup Location writable: false Use Win8 Pointer Input: false Use RightMiddleTabletButton Workaround: false Levels of Detail Enabled: false Use Zip64: false Display Information Number of screens: 1 Screen: 0 Name: \\.\DISPLAY1 Depth: 32 Scale: 1 Resolution in pixels: 1280x800 Manufacturer: Model: Refresh Rate: 60 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443084] Digikam 7.2.0 on windows 10 cannot download the last update 7.3.0
https://bugs.kde.org/show_bug.cgi?id=443084 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|general |Bundle-Windows -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443084] Digikam 7.2.0 on windows 10 cannot download the last update 7.3.0
https://bugs.kde.org/show_bug.cgi?id=443084 --- Comment #2 from caulier.gil...@gmail.com --- This error is fixed with 7.3.0 release. and will work with next 7/4/0 when it will be release. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443084] Digikam 7.2.0 on windows 10 cannot download the last update 7.3.0
https://bugs.kde.org/show_bug.cgi?id=443084 Maik Qualmann changed: What|Removed |Added Assignee|digikam-bugs-n...@kde.org |jgrul...@redhat.com --- Comment #1 from Maik Qualmann --- This can be a country-specific problem as it is redirected to a mirror server. Try again later or download the installer directly from the download link at www.digikam.org. Maik -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443088] kwin_wayland crashed in KWin::AbstractWaylandOutput::modeSize() when I logged into another user, logged out, and unlocked my original session
https://bugs.kde.org/show_bug.cgi?id=443088 --- Comment #2 from Vlad Zahorodnii --- Also, did you turn off any outputs while another session was active? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443084] Digikam 7.2.0 on windows 10 cannot download the last update 7.3.0
https://bugs.kde.org/show_bug.cgi?id=443084 Maik Qualmann changed: What|Removed |Added Assignee|jgrul...@redhat.com |digikam-bugs-n...@kde.org Component|general |general Version|unspecified |7.2.0 Product|plasma-pk-updates |digikam CC||metzping...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443088] kwin_wayland crashed in KWin::AbstractWaylandOutput::modeSize() when I logged into another user, logged out, and unlocked my original session
https://bugs.kde.org/show_bug.cgi?id=443088 --- Comment #1 from Vlad Zahorodnii --- Did you use the touch screen? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 251357] SCHEMA : add time zone support as properties of items
https://bugs.kde.org/show_bug.cgi?id=251357 Maik Qualmann changed: What|Removed |Added CC||adam.siemb...@gmail.com --- Comment #4 from Maik Qualmann --- *** Bug 443098 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443098] Use time zone for EXIF supplied dates
https://bugs.kde.org/show_bug.cgi?id=443098 Maik Qualmann changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 251357 *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 443104] New: Libreoffice Navigator remains in light mode even when using breeze dark mode
https://bugs.kde.org/show_bug.cgi?id=443104 Bug ID: 443104 Summary: Libreoffice Navigator remains in light mode even when using breeze dark mode Product: Breeze Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: gtk theme Assignee: uhh...@gmail.com Reporter: martin.tlus...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY I use breeze dark mode for my laptop. Everything is fine so far, but libreoffice sub-windows like navigator remain in light mode (which makes the side icons invisible). When installing another dark theme for gtk (like nord-gtk, which is a breeze derivate), the problem is gone. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT 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 443055] Pdf File's Size Changed to 0 Bytes After Sudden Power Outage
https://bugs.kde.org/show_bug.cgi?id=443055 --- Comment #4 from Jason Liam --- (In reply to David Hurka from comment #3) > If you say you created at least X bytes worth of annotations, but you can’t > find a docdata file which is bigger than X bytes, I am afraid, you can not > recover the annotations. :( > These are the things i noticed: 1) I have 976 number of files correspoinding to the pdf i lost. By looking at the date/time of their modification i see that they range from 26 August 2021 to 28 September 2021. During this one month i added a lot of annotations every day. The pdf file that i started with originally(without annotation) is of 3.2 MB. Now when i was adding annotations everyday i noticed that the size of the pdf gets bigger and bigger everyday. And at the last day(28 August 2021) it was taking around 4.3 MB of space. So the size increased by around 1 MB during a span of one month. 2) Whenever i added some text annotation into my pdf lets say i added a text annotation saying "this is some example text annotation inside the pdf", i was able to press Ctrl+F and search for this particular string "this is some example text annotation inside the pdf" or "this is some" etc etc. This makes me wonder if the annotations that i was adding day by day were actually embedded inside the pdf instead of being in the xml files. I am not sure if the version of okular that i am using (1.3.3) have this embedded annotations feature. 3) Now to confirm that the xml files that i have have nothing to do with the annotations that i add and the annotations are actually embedded inside the pdf itself, i took this pdf lets say named MyBook.pdf. Now i checked the docdata folder to see(make sure) that there are no xml files corresponding to this pdf. So at this point i had no xml files corresponding to MyBook.pdf. Now i opened the MyBook.pdf using Okular and added some annotation like created a rectagle and added a text annotation saying "some xyz text for testing" and pressed Ctrl+S. Now i went back to the docdata folder and found that there are now 4 xml files corresponding to MyBook.pdf. When i right click on any of these xml files and see how much space each takes it is around 943 bytes(each). Now when i open all of them simultaneously in sublime text i see that they all have almost the same content and there is no tag for rectangle or the text annotations that i made. Below is the content inside one of the xml files: Now i am confused that if there is no need for xml files since they do not have anything to do with the annotations i add in the pdf then why are they created in the first place? What is the need of these xml files they do not correspond to the actual annotations that i make? Is this a bug in this version of okular 1.3.3. Just FYI the 4 files are named like follows: 3187327.MyBook.pdf.xml ... ... Moreover these files takes around 900 bytes each so they waste memory unnecessarily it seems. > Except there is another location where Okular stored annotations in these > days. It was definitifely an XML file. But as far as I remember, it was > these docdata files. > > > > I am surprised that the PDF file has been lost. Your Okular version should > > > theoretically not modify it... > > > > Yes if instead a temporary file were used to write and checked if the write > > was successful this problem could have been avoided. > > Okular should theoretically open a PDF file only for reading, not for > writing. So it should stay in its state on disk. > > But actually I remember a bug report where a PDF file has shrunken to 0 > bytes after a power outage. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434904] Implement a triangle menu filter for Kickoff's categories sidebar
https://bugs.kde.org/show_bug.cgi?id=434904 --- Comment #14 from Tobias Leupold --- Video #2 demonstrates EXACTLY what happens to me when using the new launcher! And it makes it frustrating to use! Thanks for visualizing this! Gladly, you can still install "Legacy Kickoff" to keep the old (way more usable) menu ... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442966] Task switcher not shown correctly
https://bugs.kde.org/show_bug.cgi?id=442966 pa...@web.de changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|UNMAINTAINED|--- --- Comment #2 from pa...@web.de --- I tested with 5.22.90 and this version is a lot worse: It does not even show a desktop at all and only shows the login screen (programs are loaded, but neither restarting kwin_x11 nor plasmashell from a virtual terminal does help). What shall I try next? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 353874] Baloo does not remove deleted files from index
https://bugs.kde.org/show_bug.cgi?id=353874 --- Comment #19 from Dashon --- Still happening on Arch with kde plasma 5.22.5. Only solutiom is to purge the index, reindex, then logout and back in. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 441596] No hardware acceleration
https://bugs.kde.org/show_bug.cgi?id=441596 emohr changed: What|Removed |Added OS|Linux |All Platform|Appimage|unspecified --- Comment #4 from emohr --- You are right. The Mac version doesn't have HW acceleration too. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 443083] indi_webcam_ccd crashes due to wrong libx265.192.dylib file
https://bugs.kde.org/show_bug.cgi?id=443083 Jasem Mutlaq changed: What|Removed |Added Assignee|mutla...@ikarustech.com |rlanca...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442917] Power profiles slider doesn't show up in Battery and Brightness applet
https://bugs.kde.org/show_bug.cgi?id=442917 Bharadwaj Raju changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #9 from Bharadwaj Raju --- (In reply to Samuel Reddy from comment #7) > I'm pretty sure it is placeholder because it has only power-saver and > balanced, but it is weird that other desktop environments like GNOME still > show it even if it is placeholder. You should probably file a report with GNOME so they too don't show the slider for placeholder drivers. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442391] Kwin crashes after changing animation speed
https://bugs.kde.org/show_bug.cgi?id=442391 --- Comment #2 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.
[kiofuse] [Bug 442394] kio-fuse not mounting smb share if password is remembered
https://bugs.kde.org/show_bug.cgi?id=442394 --- Comment #2 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.
[krdc] [Bug 441630] I can't open the KRDC app
https://bugs.kde.org/show_bug.cgi?id=441630 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 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.
[kstars] [Bug 405283] The Stars platform seems to pic the wrong Indi driver of the atik EFW2
https://bugs.kde.org/show_bug.cgi?id=405283 --- 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 443103] New: Issues with Tablet pen and popup Pallet.
https://bugs.kde.org/show_bug.cgi?id=443103 Bug ID: 443103 Summary: Issues with Tablet pen and popup Pallet. Product: krita Version: 4.4.8 Platform: Microsoft Windows OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: taliaele...@aol.com Target Milestone: --- SUMMARY If I right click normally on my mouse, I can use my popup pallet without any issue. If I use my tablet pen, I cannot use the Canvas Rotation slider, but I can use everything else despite my cursor jumping from where my pen is pointing, to several inches away with a secondary cursor actually being used to select the tools/options I want. STEPS TO REPRODUCE 1. Open Krita Canvas 2. Right click using Pen to bring up Popup Pallet 3. Attempt to select Canvas Rotation Slider OBSERVED RESULT A second cursor appears when the PopupPallet opens. This second cursor, (an empty circle), appears an inch+ to the left and up from where my cursor is actually pointing. I am unable to select the Canvas Rotation Slider, as it simply clicks out. Unless I press hard, I am unable to select my Favorite Brush of the Eraser which is located at the very top underneath the Canvas Rotation Slider EXPECTED RESULT I expect to be able to use the Canvas Rotation Slider or erase button. SOFTWARE/OS VERSIONS Windows: Windows 10 Version 20H2 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I use a Wacom Intuos4 tablet with it's matching pen and have never had issues before with it and Krita. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 443102] New: Add the icons for Syncthing and Joplin in Breeze icon set
https://bugs.kde.org/show_bug.cgi?id=443102 Bug ID: 443102 Summary: Add the icons for Syncthing and Joplin in Breeze icon set Product: Breeze Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: sbmich...@tuta.io CC: kain...@gmail.com Target Milestone: --- Currently Breeze icon set lacks the icons for Syncthing and Joplin. For this reason I must install Papirus icon theme. These are two well known programs in their respective categories. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed KDE Plasma Version: Plasma 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.
[plasmashell] [Bug 423556] Battery icon sometimes indicates that battery is charging when laptop is unplugged
https://bugs.kde.org/show_bug.cgi?id=423556 Benoit Grégoire changed: What|Removed |Added CC||beno...@coeus.ca -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443101] No option to enter letters from KDE Connect android app
https://bugs.kde.org/show_bug.cgi?id=443101 --- Comment #1 from Bulko Hughes --- (In reply to Bulko Hughes from comment #0) > SUMMARY > No option to enter input from the KDE Connect android app > > STEPS TO REPRODUCE > 1. Open app > 2. Click on remote input > > OBSERVED RESULT > See that there is no keyboard to option for entering letters. > > EXPECTED RESULT > Expected an option to be able to enter letters > > SOFTWARE/OS VERSIONS > Windows: > macOS: > Linux/KDE Plasma: Arch Linux 5.14 > (available in About System) > KDE Plasma Version: 5.22.5-1 > KDE Frameworks Version: - > Qt Version: 5.15.2+kde+r227-1 > > ADDITIONAL INFORMATION > The KDE Connect android app version is actually 1.17.0 but I found no option > for that Edit: KDE Frameworks version is 5.86.0-1 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 443101] New: No option to enter letters from KDE Connect android app
https://bugs.kde.org/show_bug.cgi?id=443101 Bug ID: 443101 Summary: No option to enter letters from KDE Connect android app Product: kdeconnect Version: 1.10 Platform: Android OS: Android 11.x Status: REPORTED Severity: wishlist Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: greatsc...@hotmail.com Target Milestone: --- SUMMARY No option to enter input from the KDE Connect android app STEPS TO REPRODUCE 1. Open app 2. Click on remote input OBSERVED RESULT See that there is no keyboard to option for entering letters. EXPECTED RESULT Expected an option to be able to enter letters SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux 5.14 (available in About System) KDE Plasma Version: 5.22.5-1 KDE Frameworks Version: - Qt Version: 5.15.2+kde+r227-1 ADDITIONAL INFORMATION The KDE Connect android app version is actually 1.17.0 but I found no option for that -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 372408] Option to omit shadow and transparent border from windows in Active Window and Window Under Cursor modes
https://bugs.kde.org/show_bug.cgi?id=372408 Alexander Wilms changed: What|Removed |Added CC||f.alexander.wi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443100] Allow sorting by arbitrary tag, or date tag.
https://bugs.kde.org/show_bug.cgi?id=443100 --- Comment #1 from adam.siemb...@gmail.com --- A relatively easy way to improve the situation, without having to make major changes and edge cases, would be some setting in options that allows re-ordering the priority of metadata group. For example, to allow a user to move XMP dates as a higher priority than EXIF. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443100] New: Allow sorting by arbitrary tag, or date tag.
https://bugs.kde.org/show_bug.cgi?id=443100 Bug ID: 443100 Summary: Allow sorting by arbitrary tag, or date tag. Product: digikam Version: 7.3.0 Platform: unspecified OS: Unspecified Status: REPORTED Severity: wishlist Priority: NOR Component: Albums-Sort Assignee: digikam-bugs-n...@kde.org Reporter: adam.siemb...@gmail.com Target Milestone: --- I wish there was a feature that allowed to to choose which metadata tag to sort by. For example, if rather than sorting by EXIF (which doesn't take into account time zone), I wanted to sort by XMP DateCreated, which DOES account for time zone, I have no way of doing that. Because EXIF dates take priority over XMP dates, the only ways I can think of getting sorting accounting for time zone is to: 1. Delete all my EXIF dates so that my XMP dates can be used. Bad because I need to modify my files just to get sorting in the app. 2. Change all my times to UTC. Undesired because it is harder to account for daylight savings time if you really want to know the local time where the picture was taken. I wish I could just change the sorting to XMP DateCreated. See Issue 443098 for a related issue that originally motivated this request. https://bugs.kde.org/show_bug.cgi?id=443098 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442917] Power profiles slider doesn't show up in Battery and Brightness applet
https://bugs.kde.org/show_bug.cgi?id=442917 --- Comment #8 from Samuel Reddy --- balanced: Driver: placeholder * power-saver: Driver: placeholder Yep, it is placeholder, probably because power-profiles-daemon only supports intel cpus and not amd. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 443099] New: Neon restarts twice to apply updates
https://bugs.kde.org/show_bug.cgi?id=443099 Bug ID: 443099 Summary: Neon restarts twice to apply updates Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: guimarcalsi...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY This is not technically a bug but a design decision that makes it annoying for users to update their systems. Neon applies offline updates by default now, but the way it applies them is one of the reasons people get so upset about that feature. On Windows, when the user is prompted to restart their system to update, part of the updates are applied on shutdown and the final steps are applied when booting up the next time. When the system finishes installing updates it goes straight into the desktop. On Neon, when the user is prompted to restart, updates are applied on the next start-up, and after it finishes it restarts again and then boots up normally, thus adding additional time until the computer is ready to use. That's an additional reboot for something that already bothers so many users on Windows, a platform where the update process already requires fewer restarts and where updates are way less frequent. Since Neon is a distro that gets updated frequently, this can become quite frustrating. It would be prudent to reconsider the use of offline updates by default until that behavior is changed upstream (I don't know exactly what part of the system is responsible for offline updates. Maybe systemd? If so let me know so I can open a bug report upstream). A temporary solution would be to: 1. Temporarily disable offline updates by default until the issue is fixed (in systemd?). Maybe Neon developers could share their opinions in the bug report upstream so it's more likely to be fixed quickly. 2. Apply updates while the system is still running and maybe warn the user about the consequences of not restarting (like the increased possibility of bugs). That warning could maybe be put here on KDE's bug tracker, with something like: "Please restart your system and check if you can still reproduce the issue before reporting a bug". 3. After the online updates are applied, show a notification telling the user to restart (but don't enforce it). The point of showing a notification is to make users more likely to restart before bugs caused by the online update process have a chance to appear. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443098] New: Use time zone for EXIF supplied dates
https://bugs.kde.org/show_bug.cgi?id=443098 Bug ID: 443098 Summary: Use time zone for EXIF supplied dates Product: digikam Version: 7.3.0 Platform: unspecified OS: Unspecified Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Date Assignee: digikam-bugs-n...@kde.org Reporter: adam.siemb...@gmail.com Target Milestone: --- SUMMARY I've been evaluating digiKam and I've been having a lot of trouble with massaging the metadata to make the Thumbnail view display the files in an order I believe to be reasonable. It took a lot of experimentation and even digging through code to figure out what is going on. I'm still not sure, but I believe that EXIF dates take priority over XMP dates, and the `core/dplugins/generic/metadata/metadataedit/xmp/xmporigin.cpp` file shows the accepted XMP dates and the order of precedence. I also noticed that even when EXIF OffsetTimeOriginal is included (the time zone for the TimeDateOriginal), that it isn't used in determining the order of photos. For example, I could take a photo (A), fly to a different time zone, take another photo (B), and B could show up BEFORE A. HOWEVER. 1. If I create an XMP date, for example using ExifTool `exiftool -Composite:SubSecDateTimeOriginal>XMP:DateCreated`, which will write a date (that includes timezone) in XMP::photoshop\DateCreated\DateCreated\0 2. Clear all the EXIF dates so that the XMP date is the only one. `exiftool -a -all:all= filename`. Now digiKam will actually use the timezone to sort the order of images, so in the scenario before, A would now, in fact, show up before B. I believe that if the EXIF date takes priority over the more advanced and specific XMP date, it MUST also use the timezone (OffsetTimeXXX) for sorting and ordering. At this point the only way to get correct sorting of photographs is to create an XMP date and the you have to actually remove the EXIF dates, which I believe should not be necessary. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443027] Screen elements are reset after screen is turned off and on
https://bugs.kde.org/show_bug.cgi?id=443027 Yosuke Matsumura changed: What|Removed |Added Version|5.22.4 |5.22.5 Product|KScreen |plasmashell Assignee|kscreen-bugs-n...@kde.org |plasma-b...@kde.org Component|common |generic-crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443097] New: Export GUI: Ugly gaps between GUI elements with certain board layouts.
https://bugs.kde.org/show_bug.cgi?id=443097 Bug ID: 443097 Summary: Export GUI: Ugly gaps between GUI elements with certain board layouts. Product: krita Version: git master (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Keywords: junior-jobs Severity: minor Priority: NOR Component: Storyboard Assignee: krita-bugs-n...@kde.org Reporter: emmetoneill@gmail.com Target Milestone: --- There's a small graphical bug in the Storyboard Export GUI. Depending on the "Board Layout" combobox selection we're hiding the widgets for "Rows", "Columns", and "SVG Template Path" parameters. There's some padding or something between the elements that's being added even when elements are hidden, and it changes the gap between the UI elements in an annoying way. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 374774] Allow completed tasks to be displayed on their completion dates instead of their due dates.
https://bugs.kde.org/show_bug.cgi?id=374774 --- Comment #18 from gjditchfi...@acm.org --- Git commit 25b7024b401f5a2fcc0b19e9e3aec831ed5f984b by Glen Ditchfield, on behalf of Glen Ditchfield. Committed on 28/09/2021 at 16:34. Pushed by gditchfield into branch 'master'. Add a Completed Date column to the To-Do List view M +6-0src/todo/todomodel.cpp M +1-0src/todo/todomodel.h M +2-0src/todo/todoview.cpp M +34 -0src/todo/todoviewsortfilterproxymodel.cpp M +1-0src/todo/todoviewsortfilterproxymodel.h https://invent.kde.org/pim/eventviews/commit/25b7024b401f5a2fcc0b19e9e3aec831ed5f984b -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442878] Krita crashes after removing first scene
https://bugs.kde.org/show_bug.cgi?id=442878 Emmet O'Neill changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED CC||emmetoneill@gmail.com --- Comment #2 from Emmet O'Neill --- Hi again harie, I believe we fixed this one a couple days ago in this commit: d5d9f9f23e71955adaf836101c676b9b2432b401. The change should be available in the next 5.0 beta or "Krita Next" nightly build that you can download through the website. If this hasn't been resolved by that fix and still causes a crash for you, then please comment and we can reopen the issue. (I can't reproduce it anymore, though.) Thanks for the report! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Content area should be above mouse cursor; NOT the categories
https://bugs.kde.org/show_bug.cgi?id=443082 --- Comment #6 from flan_suse --- (In reply to Nate Graham from comment #4) > - You don't actually have Plasma 5.22 I definitely do, unless "Info Center" and Pamac are lying about the version. (Latest stable updates from Manjaro) --- > - You have a local copy of an older version of the applet in > ~/.local/share/plasma/plasmoids/ that is masking the system-provided applet There's only one item in that directory, nothing else: org.kde.plasma.kickofflegacy --- > - Manjaro has a packaging error that left you with the old applet or applied > a faulty downstream patch That's not something I am familiar with. I assume that Manjaro's packages are mostly vanilla Arch Linux, and only patched if necessary. I don't see why they would patch the launcher specifically. (But who knows!) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Content area should be above mouse cursor; NOT the categories
https://bugs.kde.org/show_bug.cgi?id=443082 --- Comment #5 from flan_suse --- (In reply to Nate Graham from comment #4) > Again, I'm sorry that you don't like the new menu. You're welcome to stick > with the old one. Nate, I don't want to get too psychological or philosophical, but a lot of the time users go quiet is because of fatigue. It's not neccessarily a mandate of the users once they diffuse their complaints. Sometimes it's not worth it to be persistent in reporting bugs (or deliberate designs) and to just get used to the "new normal". Many will just take whatever little improvements they can get and be done with it. It's just not worth to keep making their arguments behind why something breaks the momentum in their PC usage. I was reluctant to even report this, and I almost did not, since I had a hunch what the response would be. Will I keep using KDE? Yes! Will I use the legacy launcher as long as possible? Yes! Will I switch to the new launcher once the old one breaks due to non-compatibility with a future iteration of Plasma? Yes! Will I voice another complaint about the new launcher, and implore the devs to incorporate optional settings. Not likely. I'll just have to accept it. Does that imply I am happier with the new launcher? No, but it can be mistaken as such. --- Do you see my friends and my cousin complaining about it? They use Linux as a desktop, as a means to an end. They don't even know what a bug report is! ;) (Hence, they don't "exist".) Yet even recently when I re-installed Manjaro for my cousin on his new laptop, one of the first things he said was "Dude what the heck" when he tried using the new launcher. He asked if I could put back "That Windows 7 menu like we had it before" (referring to the previous laptop we installed Manjaro on.) --- The "pool of users" gets smaller and smaller with every layer: * Those who use Linux... * ...of these who use KDE... * ...of these who have active accounts on bug trackers... * ...of these who are willing to make bug reports... * ...of these who are willing to follow through... --- For example, there were no reports of Smb4K freezing when using it normally. Not even for earlier versions, even up to version 3.1.0; yet this glaring usability bug existed. Finally I said "Oh heck! I'll report it, and I'll record a VIDEO of it happening." Lo' and behold, not long after posting the video, the lead developer of Smb4K pin-pointed the bug and fixed it in the next version. According to the concept of "I don't really hear many complaints about XYZ" then the bug never was an issue? How can we know that there weren't "silent users" of Smb4K who kept having to restart the app every time it froze and didn't think it was worth it to try to report the bug or capture it on video? What if I never reported the bug, does that mean everyone who uses Smb4K isn't really bothered by the random freezes? After all, they're not complaining about it, let alone not even vocal about it. --- I don't mean any of this facetiously, and as you might have guessed I *LOVE* KDE. I understand that written text can come off as offensive, so I apologize if you think I'm being aggressive or rude. I just try to word things in a way that highlights the salient points. Just something to consider when you think about user consensus and satisfaction. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443081] Inapropriate UI/UX when reopening tabs/docs
https://bugs.kde.org/show_bug.cgi?id=443081 --- Comment #2 from Max Power --- Of course it's a wish, every expectation is a wish somehow. Every user has an expectation towards a tool made to be used by the user. And what I am experiencing is not what I expect. If the majority of users do not experience what they are expecting then that tool/module is just crap. Anyway thank you for your response. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 442950] Wrong microphone icon size used in Audio Volume when it exists in plasma style
https://bugs.kde.org/show_bug.cgi?id=442950 --- Comment #6 from Nate Graham --- OK great! -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 442950] Wrong microphone icon size used in Audio Volume when it exists in plasma style
https://bugs.kde.org/show_bug.cgi?id=442950 doncb...@gmail.com changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REOPENED|RESOLVED --- Comment #5 from doncb...@gmail.com --- Yes, but upon further inspection, I believe a faulty svg may have been the source of the problem. I literally copied and pasted the icons into the svg of a theme that was working and now it seems to work. I am not sure why it suddenly stopped working. Perhaps this is more an issue for how svgs are read. In any case, this can be closed, as the applet appears to work fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434904] Implement a triangle menu filter for Kickoff's categories sidebar
https://bugs.kde.org/show_bug.cgi?id=434904 --- Comment #13 from flan_suse --- (In reply to MK from comment #6) > As a professional UX designer I see two ways to solve the hover problem: > > 1. Give users the choice as to whether they want to open categories on hover > or on click ^ I agreed with this, and/or just place the most-frequently clicked targets (e.g, favorite apps) in a single pane above the cursor. If they insist on a split view, then have the most-frequently clicked targets positioned in the pane *directly above* the cursor; prioritize *THAT* pane over the less-often-used categories and sub-menus. I demonstrated this in two videos, while using Plasma 5.22.5, which uses the well-intended "TriangleMouseFilter" attempted "fix". VIDEO #1: Legacy method, cleaner, fewer mistakes, easy targets https://imgur.com/a/LN7uXUz --- VIDEO #2: New method, more cluttered, less intuitive, more mistakes, requires conscious effort https://imgur.com/a/iNH9yAF --- This new launcher requires more conscious effort, whereas the legacy launcher was more straight-forward with larger, breathable commonly accessed targets. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Content area should be above mouse cursor; NOT the categories
https://bugs.kde.org/show_bug.cgi?id=443082 --- Comment #4 from Nate Graham --- Your video #2 very clearly shows the exact bug that was fixed in Plasma 5.22, and we have no other reports of it being broken for people on 5.22. So the options are: - You don't actually have Plasma 5.22 - You have a local copy of an older version of the applet in ~/.local/share/plasma/plasmoids/ that is masking the system-provided applet - Manjaro has a packaging error that left you with the old applet or applied a faulty downstream patch Again, I'm sorry that you don't like the new menu. You're welcome to stick with the old one. It was hoped that the triangle filter would alleviate complaints about unintended category switching, and so far it has done so. I would recommend that you try it out (once you've gotten the fix) and see if you feel better about it. Our experience was that people requested all sorts of changes (Move the category list over to the right! Delete the category list! Let me disable hover and only change categories on click!) and as soon as the triangle filter was implemented, all the complaints disappeared as if by magic. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Content area should be above mouse cursor; NOT the categories
https://bugs.kde.org/show_bug.cgi?id=443082 --- Comment #3 from flan_suse --- Reading the "fix" at... https://invent.kde.org/plasma/plasma-workspace/-/commit/36ca390f56115ae9cbb1423cd00976e8dffec4d9 ...only further proves my point. The new layout *is* the reason that such a "fix" is needed. The "TriangleMouseFilter" introduces more complexities to try and predict the user's intention based on the movement of their cursor. A launcher with an intuitive and CLEAN layout requires no such intelligent filters to try and mask a design flaw, as good as the intention is. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442978] Button to configure Breeze window decoration is greyed out
https://bugs.kde.org/show_bug.cgi?id=442978 Nate Graham changed: What|Removed |Added Version Fixed In|master |5.24 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442978] Button to configure Breeze window decoration is greyed out
https://bugs.kde.org/show_bug.cgi?id=442978 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||master Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/1022ce0036a5 ||e3b77bc274204720d1583b47916 ||e Status|ASSIGNED|RESOLVED --- Comment #8 from Nate Graham --- Git commit 1022ce0036a5e3b77bc274204720d1583b47916e by Nate Graham, on behalf of Alexander Lohnau. Committed on 28/09/2021 at 23:08. Pushed by ngraham into branch 'master'. Fix condition for making themes configurable KPluginMetaData::findPlugins only returns valid json metdata, the previous check was accidentally kept for the condition that the plugin provides a theme engine. FIXED-IN: master M +3-3src/kcmkwin/kwindecoration/decorationmodel.cpp https://invent.kde.org/plasma/kwin/commit/1022ce0036a5e3b77bc274204720d1583b47916e -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443082] Content area should be above mouse cursor; NOT the categories
https://bugs.kde.org/show_bug.cgi?id=443082 --- Comment #2 from flan_suse --- (In reply to Nate Graham from comment #1) > The particular issue with inappropriate category switching was already fixed > in Plasma 5.22. I would recommend that you have your users upgrade. :) The videos I linked are from, Operating System: Manjaro Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.7-2-MANJARO (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics So I take it there's not going to be a way to have the content (e.g, favorite apps) be positioned above the cursor, and it's still going to require a diagonal movement and/or zig-zag to click on your favorite apps and places? The "angle" of trajectory seems to determine whether or not the categories will intercept the cursor. Again, this is an awkward balancing act for something that is used to quickly click a frequent/favorite app. If I move the cursor a bit *too* vertical, it will activate the categories. If I use an angle that's *too* horizontal, I always undershoot the target. What has been streamlined beyond the legacy method? I see nothing under the options to change the display or panels. I see no option to disable category triggering on hover. I see no option to enable hovering for the bottom panels. I see no difference in behaviour from previous versions of Plasma. I'm on Plasma 5.22.5 (same as the videos.) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442978] Button to configure Breeze window decoration is greyed out
https://bugs.kde.org/show_bug.cgi?id=442978 Nate Graham changed: What|Removed |Added Version|5.22.90 |git-master -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438020] Only one K3b theme is available in Discover
https://bugs.kde.org/show_bug.cgi?id=438020 --- Comment #13 from Patrick Silva --- I wait until "Still looking" disappears. In the case of intermittently affected categories, their addons are listed as expected after selecting another category and then switching back. Other categories are consistently affected if any of their addons is installed. By "asset" do you mean "addon"? I need instructions to run Discover with "knewstuff (Core Lib)" Full Debug enabled. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442882] Removing channel from animation curves is confusing.
https://bugs.kde.org/show_bug.cgi?id=442882 Emmet O'Neill changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |eoinoneill1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442882] Removing channel from animation curves is confusing.
https://bugs.kde.org/show_bug.cgi?id=442882 Emmet O'Neill changed: What|Removed |Added CC||emmetoneill@gmail.com Status|CONFIRMED |ASSIGNED --- Comment #4 from Emmet O'Neill --- This is correct, there's no way to completely remove the channel right now. Resetting only clears it. This shouldn't be too hard to add, and I'll add to the list, but I don't know if it'll make it before 5.0. As for the using shift to select multiple points, that's also a good idea and something we can add to our list of things to do. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442578] Krita crashes after the mp4 file is created.
https://bugs.kde.org/show_bug.cgi?id=442578 Emmet O'Neill changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED CC||emmetoneill@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 425012] Color shifting / image degradation when importing clip or extracting frame
https://bugs.kde.org/show_bug.cgi?id=425012 Julius Künzel changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||jk.kde...@smartlab.uber.spa ||ce --- Comment #16 from Julius Künzel --- Thanks for your report! We recently fixed a very similar problem (https://invent.kde.org/multimedia/kdenlive/-/issues/411) and I guess this is fixed. Please test with the nightly build and let us know if I it persists otherwise please close this report. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 379611] I can't capture video from my webcam
https://bugs.kde.org/show_bug.cgi?id=379611 Julius Künzel changed: What|Removed |Added CC||jk.kde...@smartlab.uber.spa ||ce Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443036] Metabug: let keyboard shortcuts live somewhere persistent, rather than in applets
https://bugs.kde.org/show_bug.cgi?id=443036 --- Comment #2 from Nate Graham --- I want to use global media control *shortcuts*, but I don't ever use the Media Player *applet*. I'd like to disable/remove the former without disabling/removing the latter. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 440975] Kdenlive crash when gpu_accel=true
https://bugs.kde.org/show_bug.cgi?id=440975 Julius Künzel changed: What|Removed |Added CC||jk.kde...@smartlab.uber.spa ||ce --- Comment #2 from Julius Künzel --- Thanks for your report! Unfortunately the movit(gpu) is not very stable at all and it is not really well maintained atm. I am not sure if this will get fixed soon (probably not), but it is definitely some where down the road on our road map! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 440975] Kdenlive crash when gpu_accel=true
https://bugs.kde.org/show_bug.cgi?id=440975 Julius Künzel changed: What|Removed |Added CC||guido.iod...@gmail.com --- Comment #1 from Julius Künzel --- *** Bug 442609 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442609] Kdenlive crashes when gpu/movit is activated
https://bugs.kde.org/show_bug.cgi?id=442609 Julius Künzel changed: What|Removed |Added Status|REPORTED|RESOLVED CC||jk.kde...@smartlab.uber.spa ||ce Resolution|--- |DUPLICATE --- Comment #1 from Julius Künzel --- *** This bug has been marked as a duplicate of bug 440975 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438020] Only one K3b theme is available in Discover
https://bugs.kde.org/show_bug.cgi?id=438020 --- Comment #12 from Aleix Pol --- I have an idea of what could be wrong. Do you have installed assets for all of the categories that don't work? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443079] Altering cloned resources without first changing filenames impacts on the original
https://bugs.kde.org/show_bug.cgi?id=443079 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com Status|REPORTED|ASSIGNED Assignee|krita-bugs-n...@kde.org |tamtamy.tym...@gmail.com Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438020] Only one K3b theme is available in Discover
https://bugs.kde.org/show_bug.cgi?id=438020 --- Comment #11 from Aleix Pol --- Created attachment 142000 --> https://bugs.kde.org/attachment.cgi?id=142000&action=edit Video when it works This is what I see, for reference -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443076] item under mouse pointer is launched instead of the first search result
https://bugs.kde.org/show_bug.cgi?id=443076 David Edmundson changed: What|Removed |Added Priority|NOR |VHI -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442197] A particular set of ladspa plugins do not work at all
https://bugs.kde.org/show_bug.cgi?id=442197 Julius Künzel changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||jk.kde...@smartlab.uber.spa ||ce Assignee|vpi...@kde.org |maxs...@tin.it --- Comment #1 from Julius Künzel --- Thanks for your report! We are going to check this… -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438020] Only one K3b theme is available in Discover
https://bugs.kde.org/show_bug.cgi?id=438020 --- Comment #10 from Aleix Pol --- I'm going to guess the issue is on Categories that have >20 items (which is the page size we have right now, if there's more we get to request them after). Would you be able to give us the output of Discover running with "knewstuff (Core Lib)" Full Debug enabled? Also could you make sure you're patient enough when it's fetching? I've seen it take quite a bit of time sometimes... (not more than 1 minute, although it might depend) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443036] Metabug: let keyboard shortcuts live somewhere persistent, rather than in applets
https://bugs.kde.org/show_bug.cgi?id=443036 --- Comment #1 from David Edmundson --- I somewhat agree all applets should be super thin front ends, rather than any place where there's any "business logic". But this isn't always trivial. For klipper the applet is where the data is stored - I can't think of a viable way to solve that without /massive/ new infra. Volume has some options, especially if we gain a plasma specific pipewire controller that we'll need anyway. Note that it does introduce a UX problem as well as solving one. If you remove the media applet it's because you don't want to use said thing, but you haven't really disabled it. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 440029] Selecting clip by keyboard does not activate the effect stack
https://bugs.kde.org/show_bug.cgi?id=440029 Julius Künzel changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||jk.kde...@smartlab.uber.spa ||ce Status|REPORTED|NEEDSINFO --- Comment #1 from Julius Künzel --- Thanks for your report! I can't reproduce using the latest master. Can you please check if this still happens with 21.08.1 and the nightly version? If this still happens please send a screenshot of your Kdenlive window so we can see how your UI is arranged. This might help to find the problem… -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 443096] New: Music is not detected when music folder is symlinked
https://bugs.kde.org/show_bug.cgi?id=443096 Bug ID: 443096 Summary: Music is not detected when music folder is symlinked Product: Elisa Version: 21.08.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: baloo Assignee: matthieu_gall...@yahoo.fr Reporter: k...@aynoa.net Target Milestone: --- SUMMARY Using fast native indexer when your music folder is symlinked no music at all is detected by Elisa. STEPS TO REPRODUCE 1. Symlink your music folder. 2. Start Elisa. OBSERVED RESULT No music at all. EXPECTED RESULT Music must be detected exactly like "scan the filesystem directly" do. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Maybe related to https://bugs.kde.org/show_bug.cgi?id=435383 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 439294] Kdenlive will crash at startup on MacOS
https://bugs.kde.org/show_bug.cgi?id=439294 Julius Künzel changed: What|Removed |Added CC||jk.kde...@smartlab.uber.spa ||ce Resolution|--- |MOVED Status|REPORTED|RESOLVED --- Comment #9 from Julius Künzel --- We finally have a dmg for macOS ready that doesn't crash anymore. All basic features seem to work, but it isn't well tested yet and there for not offically called stable. You can find more details on known issues here https://invent.kde.org/multimedia/kdenlive/-/issues/993 To download the dmg use the link you already know: https://binary-factory.kde.org/view/MacOS/job/Kdenlive_Nightly_macos/lastSuccessfulBuild/ If you like to test the macOS version and report problems this would be very helpful to have a stable macOS release soon. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443055] Pdf File's Size Changed to 0 Bytes After Sudden Power Outage
https://bugs.kde.org/show_bug.cgi?id=443055 --- Comment #3 from David Hurka --- If you say you created at least X bytes worth of annotations, but you can’t find a docdata file which is bigger than X bytes, I am afraid, you can not recover the annotations. :( Except there is another location where Okular stored annotations in these days. It was definitifely an XML file. But as far as I remember, it was these docdata files. > > I am surprised that the PDF file has been lost. Your Okular version should > > theoretically not modify it... > > Yes if instead a temporary file were used to write and checked if the write > was successful this problem could have been avoided. Okular should theoretically open a PDF file only for reading, not for writing. So it should stay in its state on disk. But actually I remember a bug report where a PDF file has shrunken to 0 bytes after a power outage. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 443090] UX issues with the "Repair system" notification after an incomplete offline update
https://bugs.kde.org/show_bug.cgi?id=443090 --- Comment #5 from Aleix Pol --- Thanks for pulling the thread there. Yes, it would make sense to ignore this error. Since it's unclear that the error is being set properly, let's see that PackageKit does the right thing then we fix it in Discover? -- You are receiving this mail because: You are watching all bug changes.
[ktimetracker] [Bug 442996] Update app icons in SVG in ktimetracker.git when https://bugs.kde.org/show_bug.cgi?id=442993 is fixed
https://bugs.kde.org/show_bug.cgi?id=442996 Bug 442996 depends on bug 442993, which changed state. Bug 442993 Summary: ktimetracker icon is much smaller than viewport for 22x22 size https://bugs.kde.org/show_bug.cgi?id=442993 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 442993] ktimetracker icon is much smaller than viewport for 22x22 size
https://bugs.kde.org/show_bug.cgi?id=442993 manuelj...@pm.me changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/breeze-icons/commit/ ||f0c1e0cac0e9f8b2a4126ace73e ||94ac4fa00949b --- Comment #4 from manuelj...@pm.me --- Git commit f0c1e0cac0e9f8b2a4126ace73e94ac4fa00949b by Manuel Jesús de la Fuente. Committed on 28/09/2021 at 22:16. Pushed by mdelafuente into branch 'master'. Fix KTimeTracker icon sizes M +1-39 icons-dark/apps/22/ktimetracker.svg M +1-39 icons-dark/apps/32/ktimetracker.svg M +1-39 icons-dark/apps/48/ktimetracker.svg M +1-39 icons/apps/22/ktimetracker.svg M +1-39 icons/apps/32/ktimetracker.svg M +1-39 icons/apps/48/ktimetracker.svg https://invent.kde.org/frameworks/breeze-icons/commit/f0c1e0cac0e9f8b2a4126ace73e94ac4fa00949b -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442917] Power profiles slider doesn't show up in Battery and Brightness applet
https://bugs.kde.org/show_bug.cgi?id=442917 --- Comment #7 from Samuel Reddy --- (In reply to Nate Graham from comment #6) > OK, so it's fully supported for me and I see this: > > > $ powerprofilesctl > performance: > Driver: platform_profile > Inhibited: no > > * balanced: > Driver: platform_profile > > power-saver: > Driver: platform_profile > > > What about you, Samuel? I'm pretty sure it is placeholder because it has only power-saver and balanced, but it is weird that other desktop environments like GNOME still show it even if it is placeholder. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 443039] Red X "Could not find the program '/home/dan/seamonkey/seamonkey'
https://bugs.kde.org/show_bug.cgi?id=443039 --- Comment #2 from Dan Wint --- After opening Konqueror, any link you open whether in Bookmarks or lets say Google has been opened. The attached popup comes up and the other browsers open fine, this happened after the last update. Thanks On 9/28/21 12:26, Stefano Crocco wrote: > https://bugs.kde.org/show_bug.cgi?id=443039 > > Stefano Crocco changed: > > What|Removed |Added > > CC||stefano.cro...@alice.it > > --- Comment #1 from Stefano Crocco --- > Could you please be a bit clearer about when you see the error popup message? > Do you have seamonkey configured to open web pages? > > Thanks > -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 443095] New: Moving mails to a different folder is very slow
https://bugs.kde.org/show_bug.cgi?id=443095 Bug ID: 443095 Summary: Moving mails to a different folder is very slow Product: Akonadi Version: 5.18.1 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Maildir Resource Assignee: kdepim-b...@kde.org Reporter: mar...@lichtvoll.de Target Milestone: --- SUMMARY I moved 13647 from one folder to another. It took a lot of time. I'd say at least 5 minutes, but I'd say it was longer than that. During that time KMail stalled on Akonadi and thus did not display any mail. It was basically unusable during that time. STEPS TO REPRODUCE 1. Move 1 mails from one folder to another 2. Wait 3. Wait 4. Wait 5. … OBSERVED RESULT Moving those mails took a lot of time. In the end I monitored how many mails it adds to the destination maildir folder each 10 seconds and got this: % while true; do find -type f | wc -l ; sleep 10 ; done 12426 12645 12936 13216 13445 13609 13647 13647 13647 13647 So it did about 200-300 mails every 10 seconds. Or 20-30 mails a second. This makes about 454 seconds or 7 minutes for and 34 seconds for moving all of the mails, in case it started moving mails immediately and it would reach 300 mails a second consistently. I did not measure the exact total time, but I believe it was more like 10 minutes or more. EXPECTED RESULT Those mails are basically moved within a few seconds. This is a ThinkPad T14 AMD Gen 1 with AMD Ryzen 7 PRO 4750U 8 core processor with hyperthreading, 32 GB RAM and 2 TB Samsung 980 Pro SSD. This hardware really gives no reason to be slow with such a kind of operation. During the move operation consequently neither the CPU, not even a single core, nor the SSD was fully utilized. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.21.5 on Devuan Ceres (aka Debian Sid without Systemd, I use runit instead) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.86 Qt Version: 5.15.2 Linux Kernel 5.14.7, self compiled. I am using PostgreSQL backend. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 435439] Yakuake crashed while manually resizing drop-down window.
https://bugs.kde.org/show_bug.cgi?id=435439 --- Comment #2 from Lemuel Simon --- Well...I can't trigger it again. Maybe this bug report is indeed a duplicate and has been resolved already... -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443057] Okular crashes on markdown files with an image without alt text
https://bugs.kde.org/show_bug.cgi?id=443057 --- Comment #6 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/okular/-/merge_requests/491 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443057] Okular crashes on markdown files with an image without alt text
https://bugs.kde.org/show_bug.cgi?id=443057 Nate Graham changed: What|Removed |Added Severity|normal |crash CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 440447] Menu highlight is a bit laggy
https://bugs.kde.org/show_bug.cgi?id=440447 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||5.86 Resolution|--- |FIXED --- Comment #5 from Nate Graham --- Yup, seems to have been fixed by the new menu style changes. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 442883] Parent app hangs or crashes when selecting "all" in icon chooser dialog's combobox
https://bugs.kde.org/show_bug.cgi?id=442883 Pawel changed: What|Removed |Added CC||bednarczyk.pa...@outlook.co ||m --- Comment #7 from Pawel --- Created attachment 141998 --> https://bugs.kde.org/attachment.cgi?id=141998&action=edit crash_no_dump hi Nate, yes I can when *NOT* using gdb. With GDB there i just a lag spike for a few seconds and the list of icons actually loads up. I have just had this same think happen when navigating the desktop, in different circumstances. No core dump, just a black screen. I can actually alt-tab between applications and ksyslog had the attached. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442818] Kickoff doesn't focus the search bar on open
https://bugs.kde.org/show_bug.cgi?id=442818 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #7 from Nate Graham --- Cool. :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443047] Implement option for customizable Ctrl+Click actions, just like middle-click actions
https://bugs.kde.org/show_bug.cgi?id=443047 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443047] Implement option for customizable Ctrl+Click actions, just like middle-click actions
https://bugs.kde.org/show_bug.cgi?id=443047 Nate Graham changed: What|Removed |Added Target Milestone|--- |1.0 Assignee|unassigned-b...@kde.org |h...@kde.org Summary|Cannot set Ctrl+Click |Implement option for |action in task manager |customizable Ctrl+Click ||actions, just like ||middle-click actions Component|general |Task Manager and Icons-Only ||Task Manager Severity|normal |wishlist Version|unspecified |5.22.5 Product|kde |plasmashell CC||n...@kde.org, ||plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 443042] Information in the info center is not aligned.
https://bugs.kde.org/show_bug.cgi?id=443042 Nate Graham changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 443042] Information in the info center is not aligned.
https://bugs.kde.org/show_bug.cgi?id=443042 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Nate Graham --- Can you define what you mean by "uncentralized"? Are you referring to the headers specifically, or something else? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 443040] Discover crashes on launch in Attica::ProviderManager::parseProviderFile()
https://bugs.kde.org/show_bug.cgi?id=443040 Nate Graham changed: What|Removed |Added Summary|Discovery will not load or |Discover crashes on launch |open|in ||Attica::ProviderManager::pa ||rseProviderFile() Component|discover|KNewStuff Backend CC||n...@kde.org --- Comment #3 from Nate Graham --- Do you have networkmanager installed but disabled, by any chance? Pasting the relevant part of the crash log inline: Thread 1 (Thread 0x7f6c8fc8be80 (LWP 4173)): [KCrash Handler] #4 0x7f6c7811ed8c in std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x51) at /usr/include/c++/9/bits/atomic_base.h:413 #5 QAtomicOps::loadRelaxed (_q_value=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed (this=0x51) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qbasicatomic.h:107 #7 QtPrivate::RefCount::isShared (this=0x51) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:101 #8 QHash::detach (this=0x559e4b90d488) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:291 #9 QHash::insert (avalue=..., akey=..., this=0x559e4b90d488) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:770 #10 Attica::ProviderManager::parseProviderFile (this=this@entry=0x559e4bc1bd60, xmlString=..., url=...) at ./src/providermanager.cpp:239 #11 0x7f6c7811fddb in Attica::ProviderManager::fileFinished (this=this@entry=0x559e4bc1bd60, url=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:1067 #12 0x7f6c7811fef9 in Attica::ProviderManageroperator() (__closure=0x559e4b94bd00) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qurl.h:70 #13 QtPrivate::FunctorCall, QtPrivate::List<>, void, Attica::ProviderManager::addProviderFile(const QUrl&):: >::call (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:146 #14 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:256 #15 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x559e4b94bcf0, r=, a=, ret=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:443 #16 0x7f6c94875d9e in QtPrivate::QSlotObjectBase::call (a=0x7ffd26c49560, r=0x559e4bc1bd60, this=0x559e4b94bcf0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #17 doActivate (sender=0x559e4b959d80, signal_index=10, argv=0x7ffd26c49560) at kernel/qobject.cpp:3886 #18 0x7f6c9486f167 in QMetaObject::activate (sender=sender@entry=0x559e4b959d80, m=m@entry=0x7f6c9418b960 , local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #19 0x7f6c9412b597 in QNetworkReply::finished (this=this@entry=0x559e4b959d80) at .moc/moc_qnetworkreply.cpp:404 #20 0x7f6c9407bd56 in QNetworkReplyHttpImplPrivate::finished (this=0x559e4b980c60) at access/qnetworkreplyhttpimpl.cpp:2280 #21 0x7f6c9407c369 in QNetworkReplyHttpImplPrivate::_q_finished (this=) at access/qnetworkreplyhttpimpl.cpp:2221 #22 0x7f6c94130643 in QNetworkReplyHttpImpl::qt_static_metacall (_o=, _c=, _id=, _a=) at .moc/../access/qnetworkreplyhttpimpl_p.h:98 #23 0x7f6c9486c919 in QObject::event (this=0x559e4b959d80, e=0x559e4b916410) at kernel/qobject.cpp:1314 #24 0x7f6c9589cdc3 in QApplicationPrivate::notify_helper (this=this@entry=0x559e4a567c70, receiver=receiver@entry=0x559e4b959d80, e=e@entry=0x559e4b916410) at kernel/qapplication.cpp:3632 #25 0x7f6c958a5bb8 in QApplication::notify (this=0x7ffd26c4af00, receiver=0x559e4b959d80, e=0x559e4b916410) at kernel/qapplication.cpp:3156 #26 0x7f6c9483ed7a in QCoreApplication::notifyInternal2 (receiver=0x559e4b959d80, event=0x559e4b916410) at ../../include/QtCore/5.15.3/QtCore/private/../../../../../src/corelib/thread/qthread_p.h:325 #27 0x7f6c94841681 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x559e4a560880) at kernel/qcoreapplication.cpp:1821 #28 0x7f6c94899f77 in postEventSourceDispatch (s=0x559e4a61f410) at kernel/qeventdispatcher_glib.cpp:277 #29 0x7f6c92b8e17d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #30 0x7f6c92b8e400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7f6c92b8e4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #32 0x7f6c94899641 in QEventDispatcherGlib::processEvents (this=0x559e4a627450, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #33 0x7f6c78e6abe7 in Attica::KdePlatformDependent::getAccessToken (this=this@entry=0x559e4b497b70) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qflags.h:121 #34 0x7
[kwin] [Bug 392376] Wayland socket buffer gets filled up and application terminates when GUI thread was blocked
https://bugs.kde.org/show_bug.cgi?id=392376 Marco Rebhan changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=433218 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433218] Dolphin lags and then crashes when browsing locked device over KDE Connect
https://bugs.kde.org/show_bug.cgi?id=433218 Marco Rebhan changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=392376 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 443038] widget fails to load
https://bugs.kde.org/show_bug.cgi?id=443038 Nate Graham changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED CC||n...@kde.org --- Comment #1 from Nate Graham --- > qrc:/plasma/plasmoids/org.kde.plasma.networkmanagement/contents/ui/TrafficMonitor.qml:101:13: > Cannot assign to non-existent property "fillColorSource" Sounds like you don't have the kquickcharts framework installed, or the version of it that you have is too old. This is a packaging or installation issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443076] item under mouse pointer is launched instead of the first search result
https://bugs.kde.org/show_bug.cgi?id=443076 Nate Graham changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443076] item under mouse pointer is launched instead of the first search result
https://bugs.kde.org/show_bug.cgi?id=443076 Nate Graham changed: What|Removed |Added Keywords||usability Status|REPORTED|CONFIRMED CC||n...@kde.org, ||noaha...@gmail.com Ever confirmed|0 |1 --- Comment #2 from Nate Graham --- I can reproduce the issue. This was working in the past, but I guess it got broken in one of many many code refactors. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442852] Fast user switching is broken since 5.23 beta
https://bugs.kde.org/show_bug.cgi?id=442852 --- Comment #8 from Nate Graham --- *** Bug 443085 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 443085] Switching user works only once after upgrade to Plasma 5.23 beta
https://bugs.kde.org/show_bug.cgi?id=443085 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from Nate Graham --- *** This bug has been marked as a duplicate of bug 442852 *** -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 442852] Fast user switching is broken since 5.23 beta
https://bugs.kde.org/show_bug.cgi?id=442852 Nate Graham changed: What|Removed |Added Version Fixed In||5.23 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443087] System Settings window can be dragged from empty areas, except shell footer
https://bugs.kde.org/show_bug.cgi?id=443087 Nate Graham changed: What|Removed |Added Component|kcmshell|general Severity|normal |minor Status|REPORTED|CONFIRMED Version|git-master |5.22.4 CC||n...@kde.org Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 443071] Show package changelog
https://bugs.kde.org/show_bug.cgi?id=443071 Nate Graham changed: What|Removed |Added CC||n...@kde.org Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
