[krita] [Bug 487483] Krita fails to save transparency masks for specific animated fill layers
https://bugs.kde.org/show_bug.cgi?id=487483 --- Comment #2 from Michael Eric Oberlin --- Comment on attachment 169778 --> https://bugs.kde.org/attachment.cgi?id=169778 Zip of example file and video of bug happening Video is now on YouTube, only the file and its backup are in the zip. (It was too big for the system.) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 487483] Krita fails to save transparency masks for specific animated fill layers
https://bugs.kde.org/show_bug.cgi?id=487483 --- Comment #1 from Michael Eric Oberlin --- Created attachment 169778 --> https://bugs.kde.org/attachment.cgi?id=169778=edit Zip of example file and video of bug happening Couldn't upload the original file as my screen capture was too big! So I uploaded it unlisted on YouTube: https://youtu.be/33-hLlkbjVM This should provide a satisfactory example of the UX for the bug and hopefully help chase it down. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 487483] New: Krita fails to save transparency masks for specific animated fill layers
https://bugs.kde.org/show_bug.cgi?id=487483 Bug ID: 487483 Summary: Krita fails to save transparency masks for specific animated fill layers Classification: Applications Product: krita Version: 5.2.2 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: vikinghelme...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Critical data can be lost when saving an animation to the kra file format. When a new fill layer is added and cleared with the delete key, all new animation frames will begin blank instead of solid. Changes can then be made as per usual, and committed to new frames; and for that run, both animation playback and rendering through FFMPEG will work fine. This feels like a feature. However, once the file is saved as a .kra, closed, and reopened, the detail of the layer being cleared is lost, and all frames of that fill layer are solid-color again. This has, of course, cost me a lot of time! So I did some digging to figure out what it was that was causing it. I am enclosing both a final file which this has happened to, and a video of it happening, to make tracking this bug easier. STEPS TO REPRODUCE 1. Create any Krita file in the animation workspace 2. Add a fill layer 3. Press "delete" to clear the layer 4. Add a new frame at the beginning of the file 5. Move to another frame, press new frame (note that the frame is cleared to blank, not solid) 6. Do some brush strokes on this additional fill layer frame 7. Verify proper playback and export 8. Save file 9. Close file 10. Re-open file Note that your alterations of your second frame are now completely missing, and replaced with a solid frame. OBSERVED RESULT Solid color over the entire frame EXPECTED RESULT The modifications made the last time that Krita was open SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KUbuntu 22.04 (available in About System) KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I'm not sure how much help the mis-saved .kra is going to be, so I'm also adding a video of this exact event occurring. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 335027] Touchpad on LENOVO X240
https://bugs.kde.org/show_bug.cgi?id=335027 --- Comment #11 from Michael --- Please see my answer here https://bugs.kde.org/show_bug.cgi?id=335027#c5. I'm waiting for KDE6 on MANJARO stable. After that, I can work on this issue. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 487320] Version 1.11.1 still says 1.11
https://bugs.kde.org/show_bug.cgi?id=487320 --- Comment #4 from michael --- Uploaded a new windows installer with corrected version. https://phabricator.kde.org/T17341 sha256 and sha-1 checksums are provided. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 487320] Version 1.11.1 still says 1.11
https://bugs.kde.org/show_bug.cgi?id=487320 --- Comment #3 from michael --- Going regerate windows binaries manually to use 1.11.1 target. Internial kidff3 does know what version it is but the windows install date comes from the target name used in the craft build. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 487320] Version 1.11.1 still says 1.11
https://bugs.kde.org/show_bug.cgi?id=487320 --- Comment #2 from michael --- looka like craft didn't have the new archive avialiable when I did the last build. A corrected exe has bet generated add will be uploaded to the standard download location within the next couple of days. A temporary copy can be found here https://invent.kde.org/sdk/kdiff3/-/jobs/1842508/artifacts/browse/.kde-ci-packages/ -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487334] I would like the Faces "Unconfirmed" and "Unknown" views to be filterable by Album & Sub-Tree
https://bugs.kde.org/show_bug.cgi?id=487334 --- Comment #2 from Michael Moore --- Thanks Maik, Yes, I group/separate the view by albums sometimes and it does help a bit. I'd like to get to where I can Filter by Album and then Group By Face. Then I could see all shots of (eg.) my kid when they were 1. It would make it very easy to quickly say "oh yeah, that's how Kid looked in 2008". -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487334] New: I would like the Faces "Unconfirmed" and "Unknown" views to be filterable by Album & Sub-Tree
https://bugs.kde.org/show_bug.cgi?id=487334 Bug ID: 487334 Summary: I would like the Faces "Unconfirmed" and "Unknown" views to be filterable by Album & Sub-Tree Classification: Applications Product: digikam Version: 8.3.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: stuporg...@gmail.com Target Milestone: --- Created attachment 169686 --> https://bugs.kde.org/attachment.cgi?id=169686=edit A mockup of an ideal (to me) Album filter tool SUMMARY I am tagging faces in the People tab. I have over 200,000 Unknown faces. Viewing the Unknown list makes Digikam slow, and it is overwhelming from a workflow perspective. I would like to be able to select an Album (including its Sub-Tree) and only see Unknown faces from that Album (including Sub-Tree). Ideally: * Part of the filter pane * Able to check/select multiple albums or sub-album items * Able to toggle "Include Album Sub-Tree" for filter All of my photos are organized into /MM/DD folders, so I would pick a year or a month from a year and see all photos within that year or month. STEPS TO REPRODUCE 1. Click People tab on left side 2. Click "Unknown" happy face icon in People tab 3. Have more photos than you can deal with in your workflow 4. Click Filter tab on right side 5. Find no way to filter by Album OBSERVED RESULT I don't observe a way to filter the photos in this view by Album. NOTE: I tried using the Text Filter, and even had it apply to the Album Name, but it seems that it only filters against the DD part of my /MM/DD folder structure. I do think filtering by album would be more user friendly, but even the Text Filter would work for me if it considered the full album path name. EXPECTED RESULT No expectations, just grateful for the great software and hopeful to find a way to improve my current workflow. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian Trixie/Testing KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0, maybe? Qt Version: 6.4.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 487277] New: cursor vanishing in text boxes
https://bugs.kde.org/show_bug.cgi?id=487277 Bug ID: 487277 Summary: cursor vanishing in text boxes Classification: Applications Product: Falkon Version: 24.02.2 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: michael.hm...@gmail.com Target Milestone: --- since the latest upgrade the text cursor vanishes, in Facebook comments and posts for example switching to another tab and switching back, it reappears I'm not 100% sure, but it might have started after enabling hunspell dics en_US and pt_BR, whatsoever, disabling spellcheck doesn't bring the cursor back plasma 6.0.4 Qt 6.7.0 X11 Falkon 22.02.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 480657] Preferred resolution not applied
https://bugs.kde.org/show_bug.cgi?id=480657 Michael Amrhein changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Michael Amrhein --- Works as expected in version 6.0.4. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 397594] Kaffeine plays video in a separate window under Wayland
https://bugs.kde.org/show_bug.cgi?id=397594 --- Comment #17 from Michael --- I may have found a workaround. KDE Bugs lists this issue: Possible workround is running kaffeine with "-platform xcb" to force the X11 backend. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 478164] Directory merge is activated automatically on rescan
https://bugs.kde.org/show_bug.cgi?id=478164 michael changed: What|Removed |Added Status|REPORTED|CONFIRMED Platform|Microsoft Windows |Compiled Sources OS|Microsoft Windows |All Ever confirmed|0 |1 --- Comment #1 from michael --- Seems like good idea for improvement. The current design seems to be intentional updating for the whole directory rather than just the changed file. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 453575] Last modification date always show 18/19/20th January 1970 for remote files
https://bugs.kde.org/show_bug.cgi?id=453575 michael changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 486909] KDiff3 as git mergetool does not jump to first conflict position at startup
https://bugs.kde.org/show_bug.cgi?id=486909 michael changed: What|Removed |Added Latest Commit|https://invent.kde.org/sdk/ |https://invent.kde.org/sdk/ |kdiff3/-/commit/475d52c7442 |kdiff3/-/commit/17021d7e247 |4cabe881602713a1f4946a19871 |9e92b23d450b48843237c0d92e7 |32 |85 --- Comment #3 from michael --- Git commit 17021d7e2479e92b23d450b48843237c0d92e785 by Michael Reeves. Committed on 18/05/2024 at 19:27. Pushed by mreeves into branch 'master'. Fix bad value limiter Use std::max not std::min to limit line value range FIXED-IN:1.11.1 M +1-1src/Overview.cpp M +2-2src/difftextwindow.cpp https://invent.kde.org/sdk/kdiff3/-/commit/17021d7e2479e92b23d450b48843237c0d92e785 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 485999] kdiff3 segaborts when comparing two files
https://bugs.kde.org/show_bug.cgi?id=485999 --- Comment #6 from michael --- May be related to wayland somehow. I do most tests under X11 which does not readily reproduce the scroll crash. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 482790] Strange graphical issues make usage near impossible
https://bugs.kde.org/show_bug.cgi?id=482790 michael changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #10 from michael --- As there seems to be something wiered going on with your setup. I am closing this for now. Looks like frame works /qt is having issues drawing. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 484997] Kdiff3 and Kompare can't see the home folder or media folder
https://bugs.kde.org/show_bug.cgi?id=484997 michael changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #10 from michael --- >From kdiff3s perspective this is resolved in the default settings. Manual override on your machine can also be done by command line or in some distros a plugin for system settings maybe provided . -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 459484] Crash and Windows SmartScreen warning
https://bugs.kde.org/show_bug.cgi?id=459484 michael changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #7 from michael --- closing for now as its been a long time since this was reported. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 426568] Kdiff3 can't read remote files when comparing remote folders
https://bugs.kde.org/show_bug.cgi?id=426568 michael changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #16 from michael --- I would like to confirm if this still happens with the 1.11.1 tag or master. I found a pair of bugs that would have resulted in arbitrary KIO job cancellation when handling non-file paths. Meta data retrieval and file reads where impacted by a race condition that resulted from this. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 486909] KDiff3 as git mergetool does not jump to first conflict position at startup
https://bugs.kde.org/show_bug.cgi?id=486909 michael changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/sdk/ ||kdiff3/-/commit/475d52c7442 ||4cabe881602713a1f4946a19871 ||32 Version Fixed In||1.11.1 Resolution|--- |FIXED --- Comment #2 from michael --- Git commit 475d52c74424cabe881602713a1f4946a1987132 by Michael Reeves. Committed on 18/05/2024 at 22:51. Pushed by mreeves into tag '1.11.1'. Fix bad value limiter Use std::max not std::min to limit line value range FIXED-IN:1.11.1 M +1-1src/Overview.cpp M +2-2src/difftextwindow.cpp https://invent.kde.org/sdk/kdiff3/-/commit/475d52c74424cabe881602713a1f4946a1987132 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 453575] Last modification date always show 18/19/20th January 1970 for remote files
https://bugs.kde.org/show_bug.cgi?id=453575 michael changed: What|Removed |Added Version Fixed In||1.11.1 --- Comment #3 from michael --- I believe this should be fixed in 1.11.1. Found to separate issues in handling non file urls via KIO. Together they caused the initial stat to abort at an arbitrary time. Typically not long enough to actually get the response. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 480936] Looking Web page of Release notes for 1.10.7 and older ones.
https://bugs.kde.org/show_bug.cgi?id=480936 michael changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 486909] KDiff3 as git mergetool does not jump to first conflict position at startup
https://bugs.kde.org/show_bug.cgi?id=486909 michael changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from michael --- This will be fixed in the next release thanks. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 487190] ksysguard for KDE6?
https://bugs.kde.org/show_bug.cgi?id=487190 Michael changed: What|Removed |Added CC||mailinglis...@kmhessler.de -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 487190] New: ksysguard for KDE6?
https://bugs.kde.org/show_bug.cgi?id=487190 Bug ID: 487190 Summary: ksysguard for KDE6? Classification: Applications Product: ksysguard Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: mailinglis...@kmhessler.de CC: plasma-b...@kde.org Target Milestone: --- Since KDE6, [ksysguard](https://apps.kde.org/de/ksysguard/) is no longer supported. Is there any replacement for this helpful tool or can you recommend any similar one? Thank you for your work! -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 483531] View / Hide Read Feeds doesn't work, closes feed as soon as you highlight unread item
https://bugs.kde.org/show_bug.cgi?id=483531 Michael changed: What|Removed |Added CC||mailinglis...@kmhessler.de --- Comment #3 from Michael --- Same here, the issue came with the UPdate to KDE6. In addition to the OP #4: Access that item via + (shortcut for "Jump to next unread article) has the same problem. As a workaround I modified "Mark actual article as read" from 0 to 10 seconds. My system: Operating System: Manjaro Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 5.15.158-1-MANJARO (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486918] New: Cannot logout after starting another XServer
https://bugs.kde.org/show_bug.cgi?id=486918 Bug ID: 486918 Summary: Cannot logout after starting another XServer Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Session Management Assignee: plasma-b...@kde.org Reporter: michael.dluho...@gmail.com CC: natalie_clar...@yahoo.de Target Milestone: 1.0 SUMMARY When starting a seconds X11 session (with the same user that started the kde desktop) for example via startx then I cannot logout anymore from the plasma desktop. Following error pops up in the journalctl: ksmserver-logout-greeter[4361]: qt.qpa.xcb: could not connect to display :1 STEPS TO REPRODUCE 1. login to plasma and do a systemctl --user show-environment -> note down DISPLAY and XAUTHORITY 2. startx from another tty as the same user 3. switch to plasma and do a systemctl --user show-environment -> env variables have changed 4. try to logout or restart the computer -> nothing happens OBSERVED RESULT I cannot logout or restart EXPECTED RESULT I can logout or restart SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION Maybe a easy fix is doing a systemctl --user import-environment XAUTHORITY DISPLAY just after the user clicks on logout,restart etc. So that the ksmserver-logout-greeter has no chance of using the wrong env variables. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 486910] New: `--geometry` argument is completely ignored
https://bugs.kde.org/show_bug.cgi?id=486910 Bug ID: 486910 Summary: `--geometry` argument is completely ignored Classification: Applications Product: kdialog Version: 24.02.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: br...@frogmouth.net Reporter: michaelalexsan...@protonmail.com Target Milestone: --- SUMMARY I don't just mean that it throws away the argument's value, I mean that I couldn't even find it being parse in the source code itself. STEPS TO REPRODUCE 1. Attempt to use kdialog with the `--geometry` argument. 2. See that it doesn't affect anything. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Kinoite 40 (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 109501] [Feature request] Quiet mode
https://bugs.kde.org/show_bug.cgi?id=109501 Michael Pyne changed: What|Removed |Added Latest Commit||https://invent.kde.org/sdk/ ||kdesrc-build/-/commit/61688 ||25682c81d3e6984b698d8cfa822 ||bac1797d --- Comment #3 from Michael Pyne --- Git commit 6168825682c81d3e6984b698d8cfa822bac1797d by Michael Pyne. Committed on 25/07/2005 at 02:45. Pushed by ashark into branch 'docbook_historied_per_file'. Add documentation for the recently added --quiet option. Also, make --dry-run an alias for --pretend since --dry-run seems to be a common name for that type of option. svn path=/trunk/KDE/kdesdk/doc/scripts/kdesvn-build/; revision=438341 Original commit: 660d9d66 https://invent.kde.org/sdk/kdesrc-build/-/commit/660d9d660e3e8047fb1379e1d656472dcf6d4202 M +23 -1doc/cmdline/index.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/6168825682c81d3e6984b698d8cfa822bac1797d -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 194635] Add support for ionice
https://bugs.kde.org/show_bug.cgi?id=194635 Michael Pyne changed: What|Removed |Added Latest Commit||https://invent.kde.org/sdk/ ||kdesrc-build/-/commit/3324e ||f4ff7d46714bd18e91abb5508ad ||5b1b2c8c --- Comment #3 from Michael Pyne --- Git commit 3324ef4ff7d46714bd18e91abb5508ad5b1b2c8c by Michael Pyne. Committed on 31/01/2010 at 02:04. Pushed by ashark into branch 'docbook_historied_per_file'. Add support for automatically using the ionice tool supported in Linux since 2.6.13 (or so) using CFQ, in kdesvn-build. Also update the documentation at the same time for once. To enable, set use-idle-io-priority to true in your .kdesvn-buildrc (it is disabled by default for now). svn path=/trunk/KDE/kdesdk/doc/scripts/kdesvn-build/; revision=1082647 Original commit: 76bbcd80 https://invent.kde.org/sdk/kdesrc-build/-/commit/76bbcd80c6aed139da835aad9ad462f8d74cf7a4 M +2-2doc/index.docbook M +11 -0doc/kdesvn-buildrc/conf-options-table.docbook M +29 -14 doc/using-kdesvn-build/basic-features.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/3324ef4ff7d46714bd18e91abb5508ad5b1b2c8c -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 248826] Buggy feature: skip build when no source update occurs
https://bugs.kde.org/show_bug.cgi?id=248826 Michael Pyne changed: What|Removed |Added Latest Commit||https://invent.kde.org/sdk/ ||kdesrc-build/-/commit/9aee3 ||f12a3aaded1d016426bad966bfd ||41712683 --- Comment #4 from Michael Pyne --- Git commit 9aee3f12a3aaded1d016426bad966bfd41712683 by Michael Pyne. Committed on 28/08/2010 at 02:28. Pushed by ashark into branch 'docbook_historied_per_file'. Some fixes to make the "skipping build" feature hopefully more useful: * It is now controlled by an option 'build-when-unchanged' which defaults to true, so the optimization must now be explicitly enabled. * The build is only skipped if the module was successfully installed (as determined by the persistent data recorded last run). * A command-line option, --force-build is added, along with --no-build-when-unchanged to be symmetric with the rc-file option. The new command line option and rc-file option are also documented and added to the Kate/Kwrite syntax highlighting file. FIXED-IN:1.12.1 svn path=/trunk/KDE/kdesdk/doc/scripts/kdesrc-build/; revision=1168981 Original commit: 142c7911 https://invent.kde.org/sdk/kdesrc-build/-/commit/142c79caa8b2473fd93cfe2af2a905b7fbf2 M +15 -0doc/cmdline/supported-cmdline-params.docbook M +26 -0doc/kdesrc-buildrc/conf-options-table.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/9aee3f12a3aaded1d016426bad966bfd41712683 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 109044] Add "--remove-builddir" option to kdesvn-build
https://bugs.kde.org/show_bug.cgi?id=109044 Michael Pyne changed: What|Removed |Added Latest Commit||https://invent.kde.org/sdk/ ||kdesrc-build/-/commit/cbe91 ||666f39690f6f3febc5994ac7495 ||599f1e24 --- Comment #3 from Michael Pyne --- Git commit cbe91666f39690f6f3febc5994ac7495599f1e24 by Michael Pyne. Committed on 15/07/2005 at 01:12. Pushed by ashark into branch 'docbook_historied_per_file'. Add remove-after-install option to add wish 109044. This can be used to remove the builddir and/or source dir after a successful module install, for people with limited disk space. Supports the following values: none - Don't delete anything. Obviously this is the default. builddir - Delete the build directory after install. This isn't a command line option though, it needs to be set in your ~/.kdesvn-buildrc (it is possible to set it via the command line though by doing --remove-after-install=builddir). svn path=/trunk/KDE/kdesdk/doc/scripts/kdesvn-build/; revision=434684 Original commit: b89f6bea https://invent.kde.org/sdk/kdesrc-build/-/commit/b89f6bea3a3edf596b5a17bc1df48c0a576ffddb M +22 -0doc/kdesvn-buildrc/index.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/cbe91666f39690f6f3febc5994ac7495599f1e24 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 337446] malformed JSON string
https://bugs.kde.org/show_bug.cgi?id=337446 Michael Pyne changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdes |https://invent.kde.org/sdk/ |rc-build/6911da5c8713c3e33e |kdesrc-build/-/commit/fab78 |8e43c6707a2c871bf79375 |b389048faff2db425e3e942da01 ||403c74c0 --- Comment #13 from Michael Pyne --- Git commit fab78b389048faff2db425e3e942da01403c74c0 by Michael Pyne. Committed on 16/07/2014 at 05:00. Pushed by ashark into branch 'docbook_historied_per_file'. Improve first-run behavior with build metadata. This commit makes the kde-build-metadata module a requirement instead of an option, since the vast majority of runs will require this module now. Additionally the --metadata-only option is added and documented to allow for downloading the kde-build-metadata module alone (and make the --pretend option work afterwards), and kdesrc-build recommends using it if you run with --pretend and without metadata. This should hopefully make the first-run use case easier for users. FIXED-IN:1.16 Original commit: 6911da5c https://invent.kde.org/sdk/kdesrc-build/-/commit/6911da5c8713c3e33e8e43c6707a2c871bf79375 M +24 -3doc/cmdline/supported-cmdline-params.docbook M +5-1doc/features/features-overview.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/fab78b389048faff2db425e3e942da01403c74c0 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 331654] cmake-git does not compile with ninja as build command
https://bugs.kde.org/show_bug.cgi?id=331654 Michael Pyne changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdes |https://invent.kde.org/sdk/ |rc-build/9fb3fb04d170478c92 |kdesrc-build/-/commit/bca4e |2c5d85bb996f8f4b7ed82c |917547a7b1a720b18bd4598a4ac ||63d5eba4 --- Comment #4 from Michael Pyne --- Git commit bca4e917547a7b1a720b18bd4598a4ac63d5eba4 by Michael Pyne. Committed on 30/03/2014 at 03:39. Pushed by ashark into branch 'docbook_historied_per_file'. build-systems: Mask default options for non-default build systems. This is a first-step hack to have non-default build systems ignore global options which are related to the build system in use (e.g. compile or make flags, install/uninstall options, etc.). This should fix bug 331654 (now that I understand it better) and improve the situation for bug 332789 (which would be the long-term fix when implemented). Related: bug 332789 FIXED-IN:1.16 Original commit: 9fb3fb04 https://invent.kde.org/sdk/kdesrc-build/-/commit/9fb3fb04d170478c922c5d85bb996f8f4b7ed82c M +11 -8doc/kdesrc-buildrc/conf-options-table.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/bca4e917547a7b1a720b18bd4598a4ac63d5eba4 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 365813] options doesn't work for module-sets
https://bugs.kde.org/show_bug.cgi?id=365813 Michael Pyne changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdes |https://invent.kde.org/sdk/ |rc-build/c3081844077eb53adb |kdesrc-build/-/commit/dc70f |8a9d58c8a3e3dc66921cee |55c7dc6e494fbc8a16b94e48111 ||a59b5740 --- Comment #4 from Michael Pyne --- Git commit dc70f55c7dc6e494fbc8a16b94e48111a59b5740 by Michael Pyne. Committed on 24/07/2016 at 17:01. Pushed by ashark into branch 'docbook_historied_per_file'. Allow 'options' groups to apply to named module-sets. This makes it more convenient to work with baseline configurations (that are 'include'd) without changing the upstream configuration. Still to do: add a warning when modules and module-sets end up sharing the same name somehow. FIXED-IN:16.08 Original commit: c3081844 https://invent.kde.org/sdk/kdesrc-build/-/commit/c3081844077eb53adb8a9d58c8a3e3dc66921cee M +1-1doc/index.docbook M +8-0doc/kdesrc-buildrc/kdesrc-buildrc-overview.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/dc70f55c7dc6e494fbc8a16b94e48111a59b5740 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 473859] Add short options for --include-dependencies and --no-include-dependencies
https://bugs.kde.org/show_bug.cgi?id=473859 Michael Pyne changed: What|Removed |Added Latest Commit|https://invent.kde.org/sdk/ |https://invent.kde.org/sdk/ |kdesrc-build/-/commit/5b155 |kdesrc-build/-/commit/5c875 |c5e29dd2d377fd1f84fb42d0e62 |8a40dd9c47b73c22f77be71f09a |9a9f368b|2051d3bf --- Comment #3 from Michael Pyne --- Git commit 5c8758a40dd9c47b73c22f77be71f09a2051d3bf by Michael Pyne. Committed on 07/09/2023 at 00:34. Pushed by ashark into branch 'docbook_historied_per_file'. Add short options for --[no-]include-dependencies. This adds and documents -d as a short alias for --include-dependencies, and a corresponding -D as its negation. While I'm at it, and at user request, this also adds short options for: * --help * --no-src * --src-only * --refresh-build * --ignore-modules * --resume-from and --resume-after Original commit: 5b155c5e https://invent.kde.org/sdk/kdesrc-build/-/commit/5b155c5e29dd2d377fd1f84fb42d0e629a9f368b M +11 -11 doc/cmdline/supported-cmdline-params.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/5c8758a40dd9c47b73c22f77be71f09a2051d3bf -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 352478] Support Identity
https://bugs.kde.org/show_bug.cgi?id=352478 Michael Pyne changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdes |https://invent.kde.org/sdk/ |rc-build/21b5eb9371fbb0f5f4 |kdesrc-build/-/commit/7c266 |3f7cba7606c4bdb32fedd4 |5eb90aafece2786217021586042 ||c13ac24e --- Comment #3 from Michael Pyne --- Git commit 7c2665eb90aafece2786217021586042c13ac24e by Michael Pyne. Committed on 12/09/2015 at 20:57. Pushed by ashark into branch 'docbook_historied_per_file'. Add git-user option. This option can be used to setup the user.name and user.email git-config options within each new git repository cloned or installed from snapshot, including kde-projects repositories. This can be useful for KDE developers with multiple Git identities that they use for development. Module settings override global settings so you could e.g. have a global git-user option for KDE modules and then override specific modules or module-sets with a different git-user setting. This setting is only applied during the initial git-clone process though... if there's interest in having kdesrc-build re-apply settings later that's possible too. FIXED-IN:15.09 Original commit: 21b5eb93 https://invent.kde.org/sdk/kdesrc-build/-/commit/21b5eb9371fbb0f5f43f7cba7606c4bdb32fedd4 M +2-2doc/index.docbook M +31 -0doc/kdesrc-buildrc/conf-options-table.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/7c2665eb90aafece2786217021586042c13ac24e -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 406268] telepathy-accounts-signon does not seem to have a build system to use
https://bugs.kde.org/show_bug.cgi?id=406268 --- Comment #4 from Michael Pyne --- Git commit 6b226e2ce10c359f7b803a160020dcec7ec5b8ac by Michael Pyne. Committed on 04/05/2019 at 20:15. Pushed by ashark into branch 'docbook_historied_per_file'. Add support for Meson build system. New/updated config file options: * 'configure-flags', reused as the way to pass cmdline options to the meson setup command. * 'ninja-options', a new option to pass cmdline options to the `ninja` command. Note that ninja is mandated by Meson as the underlying build tool. Tested with https://github.com/plibither8/2048.cpp Fixes #27, reviewed in !8. Test suite passes and I continue to be able to build 2048.cpp. I've also validated that ninja-options is passed to ninja when building 2048.cpp, though this was a manual verification. Original commit: 6385f5e4 https://invent.kde.org/sdk/kdesrc-build/-/commit/6385f5e429dd11393b48690a33d67a66edeacfd2 M +43 -2doc/kdesrc-buildrc/conf-options-table.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/6b226e2ce10c359f7b803a160020dcec7ec5b8ac -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 398858] kdesrc-build should use HTTPS instead of SSH for anonymous git clones
https://bugs.kde.org/show_bug.cgi?id=398858 Michael Pyne changed: What|Removed |Added Latest Commit|2c09ca0d8bc469d9860fc293b3e |https://invent.kde.org/sdk/ |1eae2814dd4cb |kdesrc-build/-/commit/96093 ||c4fead6ea56dd037335786fd31e ||6459d255 --- Comment #4 from Michael Pyne --- Git commit 96093c4fead6ea56dd037335786fd31e6459d255 by Michael Pyne, on behalf of Johan Ouwerkerk. Committed on 23/09/2018 at 00:21. Pushed by ashark into branch 'docbook_historied_per_file'. Use HTTPS instead of Git protocol as default git transport. With this change, users of kdesrc-build have better protection from man in the middle attacks on source code transfers by default without having to switch to SSH-tunneled Git protocol. FIXED-IN:18.09 Original commit: 2c09ca0d https://invent.kde.org/sdk/kdesrc-build/-/commit/2c09ca0d8bc469d9860fc293b3e1eae2814dd4cb M +1-1doc/getting-started/before-building.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/96093c4fead6ea56dd037335786fd31e6459d255 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 342416] Please add qmake-options to be able to pass options to qmake
https://bugs.kde.org/show_bug.cgi?id=342416 Michael Pyne changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdes |https://invent.kde.org/sdk/ |rc-build/432efae0a9841be849 |kdesrc-build/-/commit/70e5f |c78f9ef24ea48296f3c19c |241e3c2e35507f4446f653e4c0c ||48c6c8a5 --- Comment #2 from Michael Pyne --- Git commit 70e5f241e3c2e35507f4446f653e4c0c48c6c8a5 by Michael Pyne. Committed on 07/02/2015 at 22:31. Pushed by ashark into branch 'docbook_historied_per_file'. qmake: Add qmake-options to pass options to qmake. Obviously this only applies to the few modules that utilize the qmake build system. FIXED-IN:1.16 Original commit: 432efae0 https://invent.kde.org/sdk/kdesrc-build/-/commit/432efae0a9841be849c78f9ef24ea48296f3c19c M +1-1doc/index.docbook M +14 -0doc/kdesrc-buildrc/conf-options-table.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/70e5f241e3c2e35507f4446f653e4c0c48c6c8a5 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 332789] kdesrc-build should support giving options for each build system
https://bugs.kde.org/show_bug.cgi?id=332789 --- Comment #7 from Michael Pyne --- Git commit bca4e917547a7b1a720b18bd4598a4ac63d5eba4 by Michael Pyne. Committed on 30/03/2014 at 03:39. Pushed by ashark into branch 'docbook_historied_per_file'. build-systems: Mask default options for non-default build systems. This is a first-step hack to have non-default build systems ignore global options which are related to the build system in use (e.g. compile or make flags, install/uninstall options, etc.). This should fix bug 331654 (now that I understand it better) and improve the situation for bug 332789 (which would be the long-term fix when implemented). Related: bug 331654 FIXED-IN:1.16 Original commit: 9fb3fb04 https://invent.kde.org/sdk/kdesrc-build/-/commit/9fb3fb04d170478c922c5d85bb996f8f4b7ed82c M +11 -8doc/kdesrc-buildrc/conf-options-table.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/bca4e917547a7b1a720b18bd4598a4ac63d5eba4 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 308493] "tag" option doesn't work
https://bugs.kde.org/show_bug.cgi?id=308493 Michael Pyne changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdes |https://invent.kde.org/sdk/ |rc-build/c22b7b0653ae10fdb0 |kdesrc-build/-/commit/80364 |4b9991720ac5501c0b79c9 |4c42e94aebbd2c87b075f61e8be ||10f12f4a --- Comment #5 from Michael Pyne --- Git commit 803644c42e94aebbd2c87b075f61e8be10f12f4a by Michael Pyne. Committed on 22/10/2012 at 03:44. Pushed by ashark into branch 'docbook_historied_per_file'. Implement tag and revision options for git modules. This makes the 'tag' option allow for checking out a given git tag for a module (which is enforced by using refs/tags/$foo when passing to git). Additionally, the 'revision' option has been adopted for git modules as well, to allow for checking out any other git "tree-ish" that git supports (i.e. anything supported by 'git checkout $foo'). Both options should leave the source directory in a detached HEAD state, although kdesrc-build will adapt as necessary with each source update. The auto-stashing is still attempted for both types, and a failure to apply an auto-stashed change will cause the module to fail to build. Ensure you're in a clean working directory if you want to avoid issues due to this. The test suite continues to pass (not that it's very extensive). FIXED-IN:1.16 Original commit: c22b7b06 https://invent.kde.org/sdk/kdesrc-build/-/commit/c22b7b0653ae10fdb04b9991720ac5501c0b79c9 M +9-3doc/kdesrc-buildrc/conf-options-table.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/803644c42e94aebbd2c87b075f61e8be10f12f4a -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 330387] set-module-option-value Mising from Help Message
https://bugs.kde.org/show_bug.cgi?id=330387 Michael Pyne changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdes |https://invent.kde.org/sdk/ |rc-build/2f52754d9547aeb283 |kdesrc-build/-/commit/8c4c2 |811fb0021497c972814622 |c96c734a41185716c440ff9634b ||cdf7a5eb --- Comment #2 from Michael Pyne --- Git commit 8c4c2c96c734a41185716c440ff9634bcdf7a5eb by Michael Pyne. Committed on 26/01/2014 at 05:11. Pushed by ashark into branch 'docbook_historied_per_file'. doc: Correct docs for changes to arbitrary global cmdline flags. This was changed in the recent refactor, now the docs should be up-to-date. Original commit: 2f52754d https://invent.kde.org/sdk/kdesrc-build/-/commit/2f52754d9547aeb283811fb0021497c972814622 M +13 -3doc/cmdline/supported-cmdline-params.docbook M +3-2doc/index.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/8c4c2c96c734a41185716c440ff9634bcdf7a5eb -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 303692] kdesrc-build should support custom make command
https://bugs.kde.org/show_bug.cgi?id=303692 Michael Pyne changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdes |https://invent.kde.org/sdk/ |rc-build/9d0f34cefd1f7233cc |kdesrc-build/-/commit/382af |90cf3f17b8566a280dd3f8 |a11df63fd8924ea891165540d53 ||27e6d74b --- Comment #5 from Michael Pyne --- Git commit 382afa11df63fd8924ea891165540d5327e6d74b by Michael Pyne. Committed on 28/07/2012 at 23:12. Pushed by ashark into branch 'docbook_historied_per_file'. Add custom build command option. Unfortunately I was not able to split out moving safe_make and run_make_command with the actual implementation of this option after-the-fact. Whoops. This should implement support for a custom build command (and custom install command, assuming the install can be performed by adding 'install' to the command line). Hopefully that will be sufficient for 'ninja' or other buildsystems. Note that this only changes the *build* command, the other parts of the build system still needs to be supported in kdesrc-build (for now, custom build systems probably wouldn't be too hard to implement if necessary). Assuming your proposed command is available in PATH and can be called like make, doing something like this should suffice: module (or module-set) foo custom-build-command ninja end module (or module-set) Original commit: 9d0f34ce https://invent.kde.org/sdk/kdesrc-build/-/commit/9d0f34cefd1f7233cc90cf3f17b8566a280dd3f8 M +18 -0doc/kdesrc-buildrc/conf-options-table.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/382afa11df63fd8924ea891165540d5327e6d74b -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 315251] Add --stop-before and --stop-after options
https://bugs.kde.org/show_bug.cgi?id=315251
Michael Pyne changed:
What|Removed |Added
Latest Commit|http://commits.kde.org/kdes |https://invent.kde.org/sdk/
|rc-build/f3d30fb5a056f29718 |kdesrc-build/-/commit/b109e
|1aa63d66af5f92f45b2635 |05d3eb833c384114cb07856a510
||99f29416
--- Comment #2 from Michael Pyne ---
Git commit b109e05d3eb833c384114cb07856a51099f29416 by Michael Pyne.
Committed on 20/02/2013 at 04:23.
Pushed by ashark into branch 'docbook_historied_per_file'.
Add --stop-{before,after} command line options.
Should hopefully be pretty much what it says on the tin. Stop either
right before or right after the given module. (GUI flag since this
involves documentation changes to the Handbook and man page).
FIXED-IN:1.16
GUI:
Original commit: f3d30fb5
https://invent.kde.org/sdk/kdesrc-build/-/commit/f3d30fb5a056f297181aa63d66af5f92f45b2635
M +30 -0doc/cmdline/supported-cmdline-params.docbook
M +4-3doc/index.docbook
https://invent.kde.org/sdk/kdesrc-build/-/commit/b109e05d3eb833c384114cb07856a51099f29416
--
You are receiving this mail because:
You are watching all bug changes.
[kdesrc-build] [Bug 309713] “At the lowest level comes Nokia's library,”
https://bugs.kde.org/show_bug.cgi?id=309713 Michael Pyne changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdes |https://invent.kde.org/sdk/ |rc-build/8c038f9bcb66e3e8ad |kdesrc-build/-/commit/aed03 |cc11bc587f6258bc66d2b6 |3ed56a4347b65a8c66f18742cc1 ||7abadd4e --- Comment #2 from Michael Pyne --- Git commit aed033ed56a4347b65a8c66f18742cc17abadd4e by Michael Pyne. Committed on 10/11/2012 at 03:04. Pushed by ashark into branch 'docbook_historied_per_file'. doc: Digia now maintains Qt, not Nokia. FIXED-IN:1.16 Original commit: 8c038f9b https://invent.kde.org/sdk/kdesrc-build/-/commit/8c038f9bcb66e3e8adcc11bc587f6258bc66d2b6 M +0-26 doc/cmdline/supported-cmdline-params.docbook M +1-1doc/getting-started/kde-modules-and-selection.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/aed033ed56a4347b65a8c66f18742cc17abadd4e -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 331941] Re-add --resume
https://bugs.kde.org/show_bug.cgi?id=331941 Michael Pyne changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdes |https://invent.kde.org/sdk/ |rc-build/7222909901afcf1a2f |kdesrc-build/-/commit/09b14 |1f395714e6ed0ac46020f6 |a79b4c3223731b3b7f040da6179 ||5b5ef9bf --- Comment #2 from Michael Pyne --- Git commit 09b14a79b4c3223731b3b7f040da61795b5ef9bf by Michael Pyne. Committed on 16/03/2014 at 03:15. Pushed by ashark into branch 'docbook_historied_per_file'. Add --resume (and --stop-on-failure) command line options. Now you don't have to do --stop-on-failure=1. --resume is documented in the man page and docbook, but basically lets you resume the last build list quickly without source or metadata updates, starting from the module that failed. If you want to skip the failed module, look into --resume-after and --stop-before. FIXED-IN:1.16 Original commit: 72229099 https://invent.kde.org/sdk/kdesrc-build/-/commit/7222909901afcf1a2f1f395714e6ed0ac46020f6 M +40 -0doc/cmdline/supported-cmdline-params.docbook M +8-0doc/using-kdesrc-build/advanced-features.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/09b14a79b4c3223731b3b7f040da61795b5ef9bf -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 331939] Add --no-metadata option (or similar)
https://bugs.kde.org/show_bug.cgi?id=331939 Michael Pyne changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdes |https://invent.kde.org/sdk/ |rc-build/900a08a7d8421452be |kdesrc-build/-/commit/f8204 |08d0e0967d46975541cb21 |c946cd23fd2a13afb5c09926af3 ||56f0d17f --- Comment #2 from Michael Pyne --- Git commit f8204c946cd23fd2a13afb5c09926af356f0d17f by Michael Pyne. Committed on 15/03/2014 at 22:51. Pushed by ashark into branch 'docbook_historied_per_file'. kde-projects: Add --no-metadata command line option. FIXED-IN:1.16 Original commit: 900a08a7 https://invent.kde.org/sdk/kdesrc-build/-/commit/900a08a7d8421452be08d0e0967d46975541cb21 M +12 -0doc/cmdline/supported-cmdline-params.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/f8204c946cd23fd2a13afb5c09926af356f0d17f -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 321667] Flaw in direct-repo-child filter prevents other valid repos from being recursively added
https://bugs.kde.org/show_bug.cgi?id=321667 Michael Pyne changed: What|Removed |Added Latest Commit|https://invent.kde.org/sdk/ |https://invent.kde.org/sdk/ |kdesrc-build/-/commit/26461 |kdesrc-build/-/commit/a825e |b97d3f53c09024bc602ddaca3c9 |c00f754dae8edc158f90405fa9b |04a3b043|61ad611e --- Comment #28 from Michael Pyne --- Git commit a825ec00f754dae8edc158f90405fa9b61ad611e by Michael Pyne. Committed on 11/01/2014 at 21:06. Pushed by ashark into branch 'docbook_historied_per_file'. rc-file: Add specific "option override" entry type. Add a specific config file grouping (which acts just like a module declaration), to allow for specifying options to override a previously-declared module. The use case here is for a module-set: You can specify options which apply to an entire module-set when declaring the module-set, and then override those options with any changes in a later "options" declaration. These declarations can stack too, so this can also be useful for multi-level file includes (but this is less useful since an "options" declaration requires a specific module, it doesn't work on module-sets; in that case you'd want to have the different module-sets in your most-specific included config files instead of in a base file). Tested on my personal test case for bug 321883, and on a --pretend run, and with a bug 321883 test case modified to not pre-declare the overridden module first. Example: module-set kde-mm repository kde-projects use-modules kde/kdemultimedia end module-set options kmix # Not mentioned before this line branch KDE/4.11 end options In this case kmix would use KDE/4.11 branch while juk (and the rest of kde-mm) would use whatever the global branch or branch-group was (probably 'master'). Original commit: 38ea9975 https://invent.kde.org/sdk/kdesrc-build/-/commit/38ea997502e18313e6fe0f7120dee9ed8544bd82 M +67 -1doc/kdesrc-buildrc/kdesrc-buildrc-overview.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/a825ec00f754dae8edc158f90405fa9b61ad611e -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 321667] Flaw in direct-repo-child filter prevents other valid repos from being recursively added
https://bugs.kde.org/show_bug.cgi?id=321667 Michael Pyne changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdes |https://invent.kde.org/sdk/ |rc-build/38ea997502e18313e6 |kdesrc-build/-/commit/26461 |fe0f7120dee9ed8544bd82 |b97d3f53c09024bc602ddaca3c9 ||04a3b043 --- Comment #27 from Michael Pyne --- Git commit 26461b97d3f53c09024bc602ddaca3c904a3b043 by Michael Pyne. Committed on 12/07/2013 at 03:41. Pushed by ashark into branch 'docbook_historied_per_file'. kde-projects: Don't auto-filter git-repo's direct children. Kind of a mouthful, but remove a filter that was added to avoid automatically including an actual git repository's children that were also git repositories. E.g. think of something like a SuperBuild git module that also had its component git modules as logical children within projects.kde.org. This filter is unnecessary now that kdesrc-build supports both kde.org metadata (kde-build-metadata/build-script-ignore) and user-configurable module filtering (ignore-modules option). More importantly this filter precludes many other desirable types of group syntax (e.g. including all of kdebindings just by asking for kdebindings). So we remove the filter. The trouble I've seen so far is that it is now rather difficult to build *only* kdelibs, since kde/kdelibs is a logical parent of nepomuk-core, nepomuk-widgets, and kactivities. This can be worked-around by using a normal single module declaration. E.g. module kdelibs repository kde:kdelibs end module On the other hand, the recently-added config file option "ignore-modules" should now remove any kde-projects modules that contain a path component(s) matching the ignored module. You may have to be specific with a given ignore atom for this reason (e.g. ignore playground/libs, not 'libs' otherwise you'll also ignore kdegraphics/libs at this point... though that was also true before this commit). Original commit: a0338664 https://invent.kde.org/sdk/kdesrc-build/-/commit/a033866429b62c29fd93aea843c2f21427634ec8 M +12 -0doc/getting-started/kde-modules-and-selection.docbook M +12 -0doc/kdesrc-buildrc/conf-options-table.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/26461b97d3f53c09024bc602ddaca3c904a3b043 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 308493] "tag" option doesn't work
https://bugs.kde.org/show_bug.cgi?id=308493 --- Comment #4 from Michael Pyne --- Git commit 85d31758599fef91532a3a84f50abafcbb67fe1d by Michael Pyne. Committed on 21/10/2012 at 16:40. Pushed by ashark into branch 'docbook_historied_per_file'. Use 'tag' option when cloning git modules. This partially implements bug 308493. To fully implement it will be required to handle the case of an already-checked-out module (though prepatory work is already complete). Original commit: e3c41daf https://invent.kde.org/sdk/kdesrc-build/-/commit/e3c41dafab0796cbf441c5dd52306db8e614dbf1 M +3-0doc/kdesrc-buildrc/conf-options-table.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/85d31758599fef91532a3a84f50abafcbb67fe1d -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 305409] wish: add option to default to http for kde-project repositories
https://bugs.kde.org/show_bug.cgi?id=305409 Michael Pyne changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdes |https://invent.kde.org/sdk/ |rc-build/08372a530b584e86ef |kdesrc-build/-/commit/61d2e |5757398e255a646741b37e |601a8a2d587af5ae9fa8a5a326c ||55e7ea26 --- Comment #2 from Michael Pyne --- Git commit 61d2e601a8a2d587af5ae9fa8a5a326c55e7ea26 by Michael Pyne. Committed on 19/08/2012 at 23:19. Pushed by ashark into branch 'docbook_historied_per_file'. Allow using HTTP for kde-projects modules. This adds an option git-desired-protocol to allow for using HTTP instead of git protocol when updating git modules. For non kde-projects modules, it should already be possible to use an http:// URL as a repository instead of git:// (though I haven't tested this yet). This should implement wish 305409. FIXED-IN:1.16 Original commit: 08372a53 https://invent.kde.org/sdk/kdesrc-build/-/commit/08372a530b584e86ef5757398e255a646741b37e M +28 -0doc/kdesrc-buildrc/conf-options-table.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/61d2e601a8a2d587af5ae9fa8a5a326c55e7ea26 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 305411] wish: Use http_proxy environment variable.
https://bugs.kde.org/show_bug.cgi?id=305411 Michael Pyne changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdes |https://invent.kde.org/sdk/ |rc-build/da098bebfd5da903f4 |kdesrc-build/-/commit/808c8 |9ead490a5e1178df5f6954 |36b4a3d051c42415f9c2c3d6382 ||59fc0a21 --- Comment #2 from Michael Pyne --- Git commit 808c836b4a3d051c42415f9c2c3d638259fc0a21 by Michael Pyne. Committed on 19/08/2012 at 21:56. Pushed by ashark into branch 'docbook_historied_per_file'. Allow setting http-proxy settings. Right now this will be utilized for anything needing libwww-perl (kde_projects.xml download, tarball snapshots), and will be propagated to subprocesses via http_proxy environment variable, unless that variable is already set. Tested by using a simple HTTP proxy utilizing HTTP::Proxy from CPAN. Implements wish 305411. FIXED-IN:1.16 Original commit: da098beb https://invent.kde.org/sdk/kdesrc-build/-/commit/da098bebfd5da903f49ead490a5e1178df5f6954 M +18 -0doc/kdesrc-buildrc/conf-options-table.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/808c836b4a3d051c42415f9c2c3d638259fc0a21 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 297847] kdesrc-build changes the order of modules without reason, breaking compilation
https://bugs.kde.org/show_bug.cgi?id=297847 Michael Pyne changed: What|Removed |Added Latest Commit||https://invent.kde.org/sdk/ ||kdesrc-build/-/commit/79685 ||7861a789a84876489a7ae6b1ee1 ||44f8fa9b --- Comment #3 from Michael Pyne --- Git commit 796857861a789a84876489a7ae6b1ee144f8fa9b by Michael Pyne. Committed on 14/04/2012 at 01:17. Pushed by ashark into branch 'docbook_historied_per_file'. Revert "Bracket modules into sorted tiers." This reverts commit 089edc6a73646bce540d39c784fd2991cdefd1d2. Although auto-grouping is a nice easy way to get approximately right dependency ordering, it doesn't work in all situations. The "Best" thing would be to only sort within kde-project modules (as expanded) but for now just back out this commit so I don't break customized rc-files. Original commit: e1a2c285 https://invent.kde.org/sdk/kdesrc-build/-/commit/e1a2c2850336285b90bc0e1cebaa5fe2b1ce0770 M +0-21 doc/kdesrc-buildrc/conf-options-table.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/796857861a789a84876489a7ae6b1ee144f8fa9b -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 297357] Review "use-stable-kde" option to build current stable release
https://bugs.kde.org/show_bug.cgi?id=297357 Michael Pyne changed: What|Removed |Added Latest Commit||https://invent.kde.org/sdk/ ||kdesrc-build/-/commit/01fad ||9c26c729699862701cbd7d06b58 ||05af8e19 --- Comment #2 from Michael Pyne --- Git commit 01fad9c26c729699862701cbd7d06b5805af8e19 by Michael Pyne, on behalf of Valery Yundin. Committed on 05/04/2012 at 02:19. Pushed by ashark into branch 'docbook_historied_per_file'. Support defaulting to stable branches from proj.k.o. Valery Yundin has kindly submitted a patch (including documentation!) resurrecting the old "use-stable-kde" option to allow for defaulting kde-projects modules to the stable branch (if defined for that module). This should track with changes to the stable branch as defined, so it would be a good way to track the "not quite bleeding-edge" of development. A hearty thanks to Valery for making up a patch and then adapting it to make use of the old use-stable-kde option. FIXED-IN:1.15 Original commit: 84447b1d https://invent.kde.org/sdk/kdesrc-build/-/commit/84447b1deffea6b3c4740d987b064b75e3b5d185 M +13 -0doc/getting-started/configure-data.docbook M +18 -5doc/kdesrc-buildrc/conf-options-table.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/01fad9c26c729699862701cbd7d06b5805af8e19 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 223334] Add an option to configure the path of '.kdesvn-build-data'
https://bugs.kde.org/show_bug.cgi?id=223334 Michael Pyne changed: What|Removed |Added Latest Commit||https://invent.kde.org/sdk/ ||kdesrc-build/-/commit/20359 ||d040c92549c6c143272340bc53f ||f0bf0b87 --- Comment #2 from Michael Pyne --- Git commit 20359d040c92549c6c143272340bc53ff0bf0b87 by Michael Pyne. Committed on 05/03/2012 at 03:34. Pushed by ashark into branch 'docbook_historied_per_file'. Allow persistent data location to be user-defined. For all my users with multiple rc files in the same directory. ;) FEATURE: FIXED-IN:1.15 Original commit: 814ad429 https://invent.kde.org/sdk/kdesrc-build/-/commit/814ad429e4b1a2d6c9b174fcff2586a1e5a50931 M +1-1doc/index.docbook M +14 -0doc/kdesrc-buildrc/conf-options-table.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/20359d040c92549c6c143272340bc53ff0bf0b87 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 284071] [Patch] Add option to set ssh identity file
https://bugs.kde.org/show_bug.cgi?id=284071 Michael Pyne changed: What|Removed |Added Latest Commit||https://invent.kde.org/sdk/ ||kdesrc-build/-/commit/af67d ||864606f1a8920c49a6a42daf19c ||c816cbd5 --- Comment #4 from Michael Pyne --- Git commit af67d864606f1a8920c49a6a42daf19cc816cbd5 by Michael Pyne. Committed on 20/10/2011 at 00:11. Pushed by ashark into branch 'docbook_historied_per_file'. Allow SSH identity to be specified. Now you can specify the private key to be passed to your SSH agent if you forgot to run that before running kdesrc-build. Proof-of-concept patch graciously provided by Ralf Jung. FIXED-IN:1.14.2 Original commit: 2430b0a3 https://invent.kde.org/sdk/kdesrc-build/-/commit/2430b0a308bc63c5d008ba602f0bcf345d35166f M +13 -0doc/kdesrc-buildrc/conf-options-table.docbook https://invent.kde.org/sdk/kdesrc-build/-/commit/af67d864606f1a8920c49a6a42daf19cc816cbd5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 335027] Touchpad on LENOVO X240
https://bugs.kde.org/show_bug.cgi?id=335027 --- Comment #9 from Michael --- Please see my answer here https://bugs.kde.org/show_bug.cgi?id=335027#c5. I'm waiting for KDE6 on MANJARO stable. After that, I can work on this issue. -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 486787] New: Paused downloads cannot be resumed
https://bugs.kde.org/show_bug.cgi?id=486787 Bug ID: 486787 Summary: Paused downloads cannot be resumed Classification: Applications Product: kget Version: 24.02.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Core Assignee: k...@kde.org Reporter: sexymim...@gmail.com CC: wbau...@a1.net Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Start a new download from a server that supports downloading file chunks using the Accept-Range and Range header 2. Pause the download 3. Resume the download OBSERVED RESULT The download does not resume, and its status gets updated to "stalled" after a short while. EXPECTED RESULT The download should resume properly. SOFTWARE/OS VERSIONS Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486599] Request for a use-native-DPI setting
https://bugs.kde.org/show_bug.cgi?id=486599 --- Comment #6 from Michael Hamilton --- (In reply to Zamundaaa from comment #5) > Sorry, but if you want to have content be shown at specific (physical or > otherwise) sizes, you need to request that feature from apps, otherwise you > will never have any guarantees - no matter if system wide scaling is > involved or not. Thanks for taking the time to think over the request and providing some feedback, much appreciated. A few comments... For photographic images, if I set scaling to 1.0, I cannot see any sensible photo application deciding to overrule that. I think that's a pretty safe. The less guaranteed side is having document viewers that can show documents at actual print-size or with the correct drawing scale. While there may be no guarantees, all document oriented applications have historically "just worked" as long as the desktop DPI can be set to the actual DPI of the viewing device. Up until now this has been pretty easy to achieve. > > > Providing no attempt is made to defeat the use of QT_FONT_DPI, could it at > > least be acceptable that it remains a documented solution that can be > > employed in such cases? > We can't ensure that workarounds keep working, as it comes at the cost of > the intended system working. If it turns out that many people are causing > bugs on their PC by having the environment variable set, we might override > it in Plasma at some point. In making this request, I'm raising an issue around supporting a particular user-case and describing how I really use the desktop on a daily basis. Which is not to say you "have to" support this use-case, but to at least raise some awareness that some of us work this way and you might like to take that into consideration going forward in some way or other. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 486727] New: Option to disable alerts for when IMAP server restarts, and simply re-connect when it's available again.
https://bugs.kde.org/show_bug.cgi?id=486727 Bug ID: 486727 Summary: Option to disable alerts for when IMAP server restarts, and simply re-connect when it's available again. Classification: Applications Product: trojita Version: 0.7 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: IMAP Assignee: trojita-b...@kde.org Reporter: mich...@erikgranger.name Target Milestone: --- SUMMARY My email provider regularly restarts the IMAP service occasionally. When this happens, trojita goes into offline mode, I get an error message, and the imap dialog pops up. I then have to manually set it back to online mode and it works fine... until the IMAP server restarts again. STEPS TO REPRODUCE 1. Wait for the IMAP service to restart OBSERVED RESULT 1: Error message 2: Offline mode 3: IMAP console appears EXPECTED RESULT 1: It just waits until the IMAP service is back and carries on SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 6.0 (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION Thank you for the fantastic email client that "Just works", very light and very hard to mess up. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486599] Request for a use-native-DPI setting
https://bugs.kde.org/show_bug.cgi?id=486599 --- Comment #4 from Michael Hamilton --- (In reply to Nate Graham from comment #3) > > The scaling leads to different on screen size in different applications > That's the problem, yes: the DPI setting in Qt is global, not per-screen. > The only thing that's per-screen is the current scale system we're trying to > encourage everyone to use. > > As such I'm not sure this is feasible unless we make it clear to the user > that it will not work properly if they have a multi-monitor setup where the > monitors' DPIs don't match. This would include the common setup of plugging > an external screen into a laptop. > > Ultimately I think this is just one of those awkward issues that we have to > expect until apps are properly ported to Wayland. I think I've already encountered this with X11. The old X11 Fonts->Force font DPI setting is multi-monitor. I'm not sure if my case is typical, but I'll note it here in case it helps to see an actual use case. I set the font-DPI to 162 for my primary 4K unscaled monitor. Photo editing and architectural plans are then consistently scaled (the plans are particularly important as interpreting them wrong could be quite costly). My secondary monitor is then scaled so that the apparent size of windows is the same as the unscaled 4K monitor. I find this very workable, I trust the primary, and use the secondary mainly as a place to park work, read manuals, or edit text. In this instance I would prefer that you trust the user to do something sensible for their unique situation and accept that they are responsible for the consequences of their own actions. I do see that the desktop should be shipped with some training-wheels attached along with a warning about removing them. Providing no attempt is made to defeat the use of QT_FONT_DPI, could it at least be acceptable that it remains a documented solution that can be employed in such cases? Rather than having people wait, or potentially move on to some other alternative, it would provide a "buyer beware" way forward. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486599] Request for a use-native-DPI setting
https://bugs.kde.org/show_bug.cgi?id=486599 --- Comment #2 from Michael Hamilton --- (In reply to Michael Hamilton from comment #0) > ... > When dealing with the above use cases, it could be argued that the user > could determine their physical DPI and convert back to achieve a scale based > on dividing by 96 DPI, but I would question why achieving a view at native > DPI should be so difficult. It would be easier to tick a "native-DPI box", > or to be able to specify a DPI directly. > ... I experimented with this approach. The scaling leads to different on screen size in different applications, Qwenview shows a image of a plan at one scale, and the browser at another. So this suggestion is not a feasible workaround if consistency across the board is what is required. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484427] Transparency 'saved' of multiple closed windows to form a composite desktop background
https://bugs.kde.org/show_bug.cgi?id=484427 Michael Butash changed: What|Removed |Added CC||mich...@butash.net --- Comment #1 from Michael Butash --- I was going to open a ticket on this too, just testing some of the Desktop Effects of Plasma 6.0. I used to use Translucency in 5.27 and before various time, but too buggy to use regularly, but seems about the same issues still in 6.0. Same issue that if I enable Translucency and minimize windows, they leave a "ghost" effect of the translucent window there still once minimized, effectively leaving clutter on the desktop I can't click on, but appears to still be there. This doesn't happen with native QT-based windows for KDE windows or firefox, but does for libreoffice, virtualbox, electron apps like slack or signal, anything seemingly NOT QT or otherwise avoiding the issue like Firefox somehow. This is on arch linux with plasma 6.0.4, not sure really what to provide aside from screen shots and system versions, but glad to do so if something to look for helps resolve and make this usable again. I used to love to use Translucency effects, but it's always been buggy that I can't use it for long, and I believe this ghosting might have been present from the last time I tried under plasma 5.x, but definitely present in 6.0. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486638] Running Chromium-based browsers in native wayland mode causes them to freeze and crash when drag and dropping in Plasma 6 Wayland
https://bugs.kde.org/show_bug.cgi?id=486638 --- Comment #1 from Michael --- Created attachment 169221 --> https://bugs.kde.org/attachment.cgi?id=169221=edit Screen recording reproducing the issue During the demonstration I opened a new tab with the keyboard shortcut CTRL+T to showcase how the mouse click is unresponsive. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486638] New: Running Chromium-based browsers in native wayland mode causes them to freeze and crash when drag and dropping in Plasma 6 Wayland
https://bugs.kde.org/show_bug.cgi?id=486638 Bug ID: 486638 Summary: Running Chromium-based browsers in native wayland mode causes them to freeze and crash when drag and dropping in Plasma 6 Wayland Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sbnav...@proton.me CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Currently, Chromium-based browsers require running natively on Wayland to provide pinch-to-zoom and swipe gestures. Although still not enabled by default like in Mozilla Firefox, some users report that they've been running Chromium-based browsers successfully under GNOME Wayland. See an example here https://www.reddit.com/r/linux/comments/1cklr5b/want_pinch_to_zoom_swipe_gestures_in_brave_chrome However, in my testing on latest Fedora 40 with Plasma 6.0.4, the browser freezes and eventually crashes on force-quitting whenever a click and dragging action is performed. It seems the browser window becomes unresponsive to mouse inputs, although it still responds to keyboard inputs. But when closing the window the browser eventually crashes. STEPS TO REPRODUCE 1. Set #ozone-platform-hint flag to "Auto" or "Wayland" in chromium:///flags and restart the browser 2. Drag some webpage element around or drag a URL/bookmark into the bookmarks bar OBSERVED RESULT The browser is frozen to mouse inputs when a dragging action is performed. EXPECTED RESULT The browser should not freeze or crash when clicking and dragging. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.8-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-1240P Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: LG Electronics Product Name: 15Z90Q-G.AA52P System Version: 0.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486599] Request for a use-native-DPI setting
https://bugs.kde.org/show_bug.cgi?id=486599 --- Comment #1 from Michael Hamilton --- Some relevant discussions: https://discuss.kde.org/t/return-dpi-resolution-adjustments-in-font-settings-support/11860/12 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486599] New: Request for a use-native-DPI setting
https://bugs.kde.org/show_bug.cgi?id=486599 Bug ID: 486599 Summary: Request for a use-native-DPI setting Classification: Plasma Product: kwin Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mich...@actrix.gen.nz Target Milestone: --- I suspect there is a requirement for a simple setting that sets the desktop DPI to the native DPI of the display (primary display?). The consequence would be that one desktop pixel is equal to one physical pixel for all applications no matter how or when they were written or whether they are running in Wayland or XWayland. There are several use-cases where this brings distinct advantages: 1) When using the desktop for photography there would be an easy way to ensure that photos are rendered and viewed at 100% are viewed as they were captured by the camera. Currently the myriad of browsers, photo-editors, photo-viewers, and graphical tools vary in their awareness of scaling. Many are not scaling aware, and those that are vary in what they do about it. 2) When working with printed documents, there would be an easy way to preview the document at actual print size. This applies not only to photography, but to any situation where it would be desirable to proof a document at its real size. 3) When working with architectural, engineering, clothing-design, or other documents with measurable lengths, there would be a way to take rough measurements directly from the screen. When dealing with the above use cases, it could be argued that the user could determine their physical DPI and convert back to achieve a scale based on dividing by 96 DPI, but I would question why achieving a view at native DPI should be so difficult. It would be easier to tick a "native-DPI box", or to be able to specify a DPI directly. Such a setting may affect the way the desktop looks. Given the requirements presented in the above use cases, I think the the value of seeing documents at the right size may outweigh seeing the desktop elements correctly proportioned. There is already the relatively unknown QT_FONT_DPI which appears to work well with desktops scaled to 1.0. I've found using that with KDE6 in Wayland quite effective with no noticeable detrimental effects. Perhaps this could be exposed as a setting. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 Michael Butash changed: What|Removed |Added CC||mich...@butash.net --- Comment #4 from Michael Butash --- Is it DP output to DP input, or some mode conversion to HDMI? I have this happen almost clockwork after a suspend awaken, reboot, even just a glitch of the power to the dock or something, and seems to come largely from having to use DP on dock to HDMI on TV conversion. Often I'll see the display after reset come up instead of my Samsung TV's I use to display as generic "NVidia 640x480", and is usually all xrandr sees as well, indicating like the conversion chip in the cable/adapter glitches and EDID data doesn't resolve correctly on the host. I often have to end up unplugging physically and resetting the DP end of the cable/adapter to fix it. With my laptop dock with only DP out, this got annoying and problematic enough I bought specific EDID spoofers to keep this from changing any more than needed, but still occasionally I need to reset power to those as well, even re-seat the cable to get it back to sanity. I've never had actual DP displays to see if this is any better, but HDMI-only displays are certainly a curse and four-letter word. Quite annoying using ANY sort of conversion for me between DP and HDMI. This has been going on damn near a decade for me I've dealt with in various ways across various devices, but it never seems to get better with adapters, video cards, docks, or any combination of. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 485999] kdiff3 segaborts when comparing two files
https://bugs.kde.org/show_bug.cgi?id=485999 michael changed: What|Removed |Added Status|REOPENED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 485999] kdiff3 segaborts when comparing two files
https://bugs.kde.org/show_bug.cgi?id=485999 michael changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486587] New: "Blinking" launch feedback is visually glitchy
https://bugs.kde.org/show_bug.cgi?id=486587 Bug ID: 486587 Summary: "Blinking" launch feedback is visually glitchy Classification: Plasma Product: kwin Version: 6.0.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: michaelalexsan...@protonmail.com Target Milestone: --- SUMMARY The "Blinking" launch feedback appears visually glitchy. And yes, I know this was already reported (https://bugs.kde.org/show_bug.cgi?id=405521), but it was 5 years ago, and closed because it was intended (?). STEPS TO REPRODUCE 1. Select "Blinking" in the "Configure Launch Feedback..." inside the "Cursors" settings. 2. Launch an application. 3. See effect in the cursor. OBSERVED RESULT It turns into a white square. EXPECTED RESULT To just fade away. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Kinoite 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 486516] New: Change Subtitle Location
https://bugs.kde.org/show_bug.cgi?id=486516 Bug ID: 486516 Summary: Change Subtitle Location Classification: Applications Product: kdenlive Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: kde_2...@michaelaltfield.net Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY This ticket is a request to add a way for users to change the location of subtitles in kdenlive STEPS TO REPRODUCE 1. Open kdenlive 2. Click Project -> Subtitles -> Edit Subtitle tool 3. Double-click somewhere in the "Subtitle" timeline 4. Type "this is a subtitle" 5. Press 6. Realize that the subtitle is so low on the video that it will be covered-up by the playback controls 7. Try to move the subtitle higher 8. ??? 9. Search the internet for how to move the subitlte higher 10. Find this (saying it's not possible and to file a bug report here) https://discuss.kde.org/t/subtitle-change-predefined-position/1492 11. File bug report OBSERVED RESULT There doesn't appear to be an option to change the default position for subtitles EXPECTED RESULT There should be a global setting that users can alter in the UI to make the subtitles appear in a different location (eg higher up the screen, so that the YouTube playback controls won't cover-up the subtitles) SOFTWARE/OS VERSIONS Debian Linux, but not relevant. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 486422] New: Suspend inhibits also end up keeping the display on
https://bugs.kde.org/show_bug.cgi?id=486422 Bug ID: 486422 Summary: Suspend inhibits also end up keeping the display on Classification: Plasma Product: Powerdevil Version: 5.27.80 Platform: Kubuntu OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: m...@mterry.name CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY When an app inhibits suspend via a freedesktop.org dbus call, it seems to also wake & keep the display on. This causes annoyance when this happens overnight. A user of my backup app reported this issue [1], and I'm reporting it on here with some extra investigation. Here's the backup use case for "suspend only" inhibits (while wanting to allow display to stay off / the session to go idle): - This app can resume backups. So if the user wants to log out or power off, that's fine. - If the user wants to walk away from the machine or otherwise go idle, that's also fine. - But the app wants to be able to finish its work without being suspended through power policy. I've noticed by watching dbus, that the fd.o inhibit request gets sent to Powerdevil as an InterruptSession inhibit. But past that, I am not sure how this ends up resulting in the display staying on. [1] https://gitlab.gnome.org/World/deja-dup/-/issues/462 STEPS TO REPRODUCE 1. Inhibit suspend via dbus (or if using this backup app, run "deja-dup --backup --auto" after configuring a backup) 2. See if display is allowed to turn off (I've not tested this myself, I don't have a KDE system handy and VMs don't seem to reproduce display-power-logic.) OBSERVED RESULT The display wakes up and stays on. EXPECTED RESULT The display to stay off and be allowed to go idle. SOFTWARE/OS VERSIONS Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-27-generic (64-bit) Graphics Platform: X11 Processors: 16 × 12th Gen Intel® Core™ i5-12500H Memory: 15.2 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: VivoBook_ASUSLaptop K3502ZA_K3502ZA System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 485999] kdiff3 segaborts when comparing two files
https://bugs.kde.org/show_bug.cgi?id=485999 michael changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from michael --- I believe I may found the cause of this error getBestFirstLine is returning a negative line value. This situation does not happen with most files and would have been ignored by pre 1.9 kdiff3. That would break assumptions else where in kdiff3 causing unpredictable results. I a fix locally need to test it the make sure. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 485854] kde-frameworks/kio-6.1.0: [LLVM-18] src/gui/systemd/scopedprocessrunner.cpp:60:9: error: use of undeclared identifier 'close'
https://bugs.kde.org/show_bug.cgi?id=485854 --- Comment #5 from Michael --- Here is the MR https://invent.kde.org/frameworks/kio/-/merge_requests/1619 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 484997] Kdiff3 and Kompare can't see the home folder or media folder
https://bugs.kde.org/show_bug.cgi?id=484997 --- Comment #8 from michael --- I can can check the repo. on invent.kde.org. Any config file would be there if its mantianed on kde's systems. I would also be willing to do the MR. Hopeful that will get to the right person. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 335027] Touchpad on LENOVO X240
https://bugs.kde.org/show_bug.cgi?id=335027 --- Comment #7 from Michael --- Please see my answer here https://bugs.kde.org/show_bug.cgi?id=335027#c5. I'm waiting for KDE6 on MANJARO stable. After thta, I can work on this issue. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 484997] Kdiff3 and Kompare can't see the home folder or media folder
https://bugs.kde.org/show_bug.cgi?id=484997 michael changed: What|Removed |Added Status|ASSIGNED|CONFIRMED --- Comment #6 from michael --- kdiff3 will has bee adjusted to use --filesystem=home as its default ship setting. Further opening of the permissions should be done by configuration at the install site. This is now resolved for KDiff3. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 484997] Kdiff3 and Kompare can't see the home folder or media folder
https://bugs.kde.org/show_bug.cgi?id=484997 michael changed: What|Removed |Added Status|REOPENED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 484997] Kdiff3 and Kompare can't see the home folder or media folder
https://bugs.kde.org/show_bug.cgi?id=484997 michael changed: What|Removed |Added Status|CLOSED |REOPENED Ever confirmed|0 |1 Resolution|NOT A BUG |--- --- Comment #5 from michael --- My apologies for the rather turse auto reply and closure. I am overruling the closure as kdiff3 can and should ajust its default permisions. Flatpack by default is highly restrictive on what apps are permitted to do. For kdiff3 this is excessive. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 484988] SEGABRT in Kdiff3 with Qt 6.6+ when opening files
https://bugs.kde.org/show_bug.cgi?id=484988 --- Comment #9 from michael --- Go ahead and file sperrate bug for the new crash so its easier to track. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 485854] kde-frameworks/kio-6.1.0: [LLVM-18] src/gui/systemd/scopedprocessrunner.cpp:60:9: error: use of undeclared identifier 'close'
https://bugs.kde.org/show_bug.cgi?id=485854 Michael changed: What|Removed |Added CC||egge...@protonmail.com --- Comment #2 from Michael --- Created attachment 168786 --> https://bugs.kde.org/attachment.cgi?id=168786=edit fix-undecleared-identifier-close.patch Happens for me as well on Gentoo with LLVM/Clang 17. I've attached patch as a workaround that includes unistd.h that defines "close", however I'm not sure if this has some unwanted side effects, but so far everything seems to work fine. STEPS TO REPRODUCE 1. Have llvm-17.0.6 2. Update KDE Plasma 6.0.4, Gear 24.02.2 and Frameworks 6.1.0 2. Compile kde-frameworks/kio-6.1.0 clang and USE flags "X wayland" SOFTWARE/OS VERSIONS Linux: Gentoo Linux 2.15 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 484976] Kdiff3 fails to start when built with Qt 6.7.0
https://bugs.kde.org/show_bug.cgi?id=484976 michael changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||b63bdfe17bacd0bb89255823983 ||a472ab54fcd33 --- Comment #2 from michael --- Looks like a master only regression. Fixed in b63bdfe17bacd0bb89255823983a472ab54fcd33. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 484988] SEGABRT in Kdiff3 with Qt 6.6+ when opening files
https://bugs.kde.org/show_bug.cgi?id=484988 michael changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #7 from michael --- Both the crash and the file processing error have now been corrected in master and 1.11. -- You are receiving this mail because: You are watching all bug changes.
[Marknote] [Bug 485925] New: Suggestion: make MarkNote more streamlined for adding notes
https://bugs.kde.org/show_bug.cgi?id=485925 Bug ID: 485925 Summary: Suggestion: make MarkNote more streamlined for adding notes Classification: Applications Product: Marknote Version: 1.1.1 Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: m...@kaidan.im Reporter: k...@callthecomputerdoctor.com CC: c...@carlschwan.eu, m...@kaidan.im Target Milestone: --- I found out about MarkNote on The Planet and have installed it via Flatpak, works great. I have been looking for a native KDE note taking app to replace BasKet Note Pads, which seems to have stalled development. One thing that works great from a workflow perspective that makes BasKet frictionless and a joy to use is that I don't have to slow down to name a note ahead of time. Most times, I simply want to start typing right away. In this case, the first line of the note automatically and always is the title/name of the note by the fact that it's the first line and is the most top-of-mind. This UI concept was used in the classic PalmPilot Notes app to great effect. You just added a new note, wrote it out, and then when you clicked Done, you saw an elided version of the note's first line as the note's title in the list of notes. It was very simple and intuitive to use. I really wish more note taking apps were like that--make it fast, frictionless and intuitive. My wish is to eliminate the "New note: input name, Save / Cancel" dialog after I click the + to add a new note and just take me right into the note where I can begin typing. That would be great. Along these lines, I suggest an option to automatically style the first line or not. Not everyone will want to have the first line be Large, Bolded Title Text. Nice app, though! -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 484988] SEGABRT in Kdiff3 with Qt 6.6+ when opening files
https://bugs.kde.org/show_bug.cgi?id=484988 michael changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #6 from michael --- The crash on save is fixed in: 700eb940c615d8a90632f87f9833ca1a8e3a2fc2 ff6196eba71179c528360ab5eef355989d5ae979 This is present in master and 1.11.0. Will be submitting a fix for the file open crash shortly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484606] High CPU usage on kwin_x11/Xorg when screen is off
https://bugs.kde.org/show_bug.cgi?id=484606 --- Comment #9 from Michael Hamilton --- I'm not sure if I'm seeing the same issue. I do see high CPU usage after I've locked the session, but I only for my old/existing user login, if I try a newer user login, then the problem does not occur. (X11, nvidia 550.67, plasma 6.0.3). In my case I suspect there is something in the old user's config that is the cause. If you're experiencing the issue, it might be worth creating a new user and seeing if that login also experiences the issue. I removed various CPU/Memory tracking widgets, that seemed to resolve the issue, and putting them back reverted the behaviour. But adding the same widgets to the newer account did not replicate the issue, so it's not as simple as that. Perhaps it's a combo of settings, such as floating-panel + widgets or some other setting. Also I think switching to a text console might trigger similar symptoms without needing to lock the session. If I switch to a text console, plasma-shell periodically burns CPU - but it is not constant. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467992] Wrong keyboard layout switch hotkey behavior for more than two layouts and per window layout policy
https://bugs.kde.org/show_bug.cgi?id=467992 --- Comment #23 from Michael Lashkevich --- More than a year. Is there any fix? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484606] High CPU usage on kwin_x11/Xorg when screen is off
https://bugs.kde.org/show_bug.cgi?id=484606 Michael Hamilton changed: What|Removed |Added CC||mich...@actrix.gen.nz -- You are receiving this mail because: You are watching all bug changes.
[KDE Config Driver Manager] [Bug 402901] kdesrc-build --initial-setup reports "* No installer for linux!" when executing the command on Debian 9 stable
https://bugs.kde.org/show_bug.cgi?id=402901 --- Comment #8 from Michael Pyne --- Git commit a5d286145e9b9374b5e9c6ec6045de1e58f812e9 by Michael Pyne. Committed on 06/01/2019 at 02:39. Pushed by ashark into branch 'no-ff-recreate'. first-run: Add basic installer and packages for Debian distros. This adds the installer to allow Debian-based distros to run and a basic set of packages needed to at least allow kdesrc-build to successfully run --initial-setup, as tested under a Docker image of debian 9. This will still miss the dependencies required to fully make it through any kind of reasonable KDE software build. In particular even if I included the list of Qt modules that Debian 9 stable has available, they are too old for current git-based applications. But other modules are probably needed and still missing (suggestions accepted! :). So there's still more to do here, which is why the bug remains open. See issue #15 Original commit: 845e9da4 https://invent.kde.org/sdk/kdesrc-build/-/commit/845e9da4ac262e14161bb777449d85972cfe6103 M +3-1distro-dependencies/debian.ini https://invent.kde.org/sysadmin/repo-metadata/-/commit/a5d286145e9b9374b5e9c6ec6045de1e58f812e9 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 402484] kdesrc-build's initial setup needs to install perl-io-socket-ssl on Arch et al.
https://bugs.kde.org/show_bug.cgi?id=402484 Michael Pyne changed: What|Removed |Added Latest Commit|e84022a7acd6347b34cefd58a5c |https://invent.kde.org/sysa |002e4bf03f440 |dmin/repo-metadata/-/commit ||/0ff608a2cf7b58dfa7fef9e247 ||4bbb8d873065fa --- Comment #3 from Michael Pyne --- Git commit 0ff608a2cf7b58dfa7fef9e2474bbb8d873065fa by Michael Pyne, on behalf of Nate Graham. Committed on 26/12/2018 at 01:28. Pushed by ashark into branch 'no-ff-recreate'. Add Arch package for IO::Socket::SSL as a kdesrc-build dep. Fixes #3 Differential Revision: https://phabricator.kde.org/D17768 FIXED-IN:19.01 Original commit: e84022a7 https://invent.kde.org/sdk/kdesrc-build/-/commit/e84022a7acd6347b34cefd58a5c002e4bf03f440 M +1-1distro-dependencies/arch.ini https://invent.kde.org/sysadmin/repo-metadata/-/commit/0ff608a2cf7b58dfa7fef9e2474bbb8d873065fa -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 485379] New: "Still looking" and spinning cogwheel not vertically centered unlike other messages
https://bugs.kde.org/show_bug.cgi?id=485379 Bug ID: 485379 Summary: "Still looking" and spinning cogwheel not vertically centered unlike other messages Classification: Applications Product: Discover Version: 5.27.11 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: nortex...@gmail.com CC: aleix...@kde.org Target Milestone: --- When searching for something the message "Still looking" that is accompanied by a cogwheel are not vertically centered like all other messages such as those pertaining to loading and not finding a package. All messages should occur in the same spot, namely, centered. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485328] New: Files in folder view widget not consistently highlighted/clickable, mostly in "list view"
https://bugs.kde.org/show_bug.cgi?id=485328 Bug ID: 485328 Summary: Files in folder view widget not consistently highlighted/clickable, mostly in "list view" Classification: Plasma Product: plasmashell Version: 6.0.3 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Folder Assignee: plasma-b...@kde.org Reporter: d...@mail.bromilow.uk CC: h...@kde.org Target Milestone: 1.0 *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY When mousing over items in a folder view widget, they are not consistently highlighted and clickable, as though they are losing focus. STEPS TO REPRODUCE 1. Add "folder view" widget to panel, pointing to somewhere with a few files/folders. 2. Configure "Icons/View Mode" as "List" (the default). 3. Move cursor up and down list of files/folders. OBSERVED RESULT Sometimes the cursor is on top of items and they are not highlighted; clicking has no effect. EXPECTED RESULT The item that the cursor is hovering over should be highlighted and clickable at all times. SOFTWARE/OS VERSIONS Arch Linux (confirmed in a fresh VM) KDE Plasma: 6.0.3 (available in About System) KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Using Wayland KWin session. ADDITIONAL INFORMATION Seems to have some link to changing the direction of the cursor up/down. It also happens in Icon view but is hard to notice as it seems the larger size of the icons causes the highlighting to kick in after some amount of movement. I believe this regression occurred between 5.27 and 6.0; unfortunately I am currently short on time to investigate exactly where further. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 335027] Touchpad on LENOVO X240
https://bugs.kde.org/show_bug.cgi?id=335027 --- Comment #5 from Michael --- Thank you @ Nate: To be honest. the X240 is no longer my working horse, but I will UPdate it to KDE6, as soon as KDE6 will be standard on MANJARO (stable). After that, I will report here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 436240] Lag/hang in apps and Plasma when a notification appears while compositing is active and using a non-NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=436240 --- Comment #16 from Michael Hamilton --- (In reply to Nate Graham from comment #15) > Are you 100% positive it's the exact same issue? Including triggering steps > as well as GPU hardware? Os so, updated reproduction steps would be > appreciated If not, we need a new bug report to track it since it's a > different issue. > > Thanks! It hasn't repeated recently. I've since updated the kernel, GPU, and various tumbleweed KDE packages, so I don't think I'll ever get to the bottom of it. I'll raise a new issue if anything similar reliably repeats. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484944] Wayland session disables internal monitor
https://bugs.kde.org/show_bug.cgi?id=484944 Michael Magyar changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Michael Magyar --- Hello, Poking around I have figured out this situation. I believe this may just be a quirk of the Thinkpad P14s Gen4 AMD ( 21K5001JUS ). At some point the resolution settings for the internal display changed from the display's 16:10 aspect ratio to a 16:9 aspect ratio with the same scaling factor. These settings result in the display remaining blank. I would guess I changed this when connecting to a 16:9 external display in mirroring mode. Changing the internal display back to a 16:10 aspect ratio output gets all my displays working correctly again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484944] Wayland session disables internal monitor
https://bugs.kde.org/show_bug.cgi?id=484944 Michael Magyar changed: What|Removed |Added Keywords||multiscreen, wayland -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 449091] kscreenlocker crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=449091 --- Comment #2 from Michael Josenhans --- I had to reinstall Kdeneon. I no longer have this problem. Am Sat, 6 Apr 2024 09:27:56 +, mydarkstar schrieb: > https://bugs.kde.org/show_bug.cgi?id=449091 > > mydarkstar changed: > >What|Removed |Added > > Resolution|--- |WORKSFORME > Status|REPORTED|NEEDSINFO > > --- Comment #1 from mydarkstar --- > I have just re-filed this bug report for kscreenlocker, which I > assume you were > referring to. > > However, I am unfortunately unable to reproduce your issue across different > systems. > The issue you are describing usually happens after doing a > larger Plasma update > and locking the screen during it. But it should definitely not occur after a > reboot. > > Could you please check whether this is still an issue for you on a recent > version? > If so, please provide more details on your setup, such as your GPU and other > hardware configuration. > > If only the mouse pointer is visible after logging into a new session, this > does not appear to be an issue with kscreenlocker, but would be something > separate to the first issue you described. > -- Sent with Dekko - the convergent email app -- You are receiving this mail because: You are watching all bug changes.
