[krunner] [Bug 474782] Recent files search requires knowing beginning of the filename
https://bugs.kde.org/show_bug.cgi?id=474782 --- Comment #4 from Michael D --- Sorry, the problem is not what I thought it was. The problem is that search is case sensitive. If the file is called "Carroll and the Tortoise.pdf" and I search "tortoise", it won't return a result, but I will if I type "Tortoise". I think this is a bug in any case as a search for recent files shouldn't be case sensitive. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 474782] New: Recent files search requires knowing beginning of the filename
https://bugs.kde.org/show_bug.cgi?id=474782 Bug ID: 474782 Summary: Recent files search requires knowing beginning of the filename Classification: Plasma Product: krunner Version: 5.27.8 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: nortex...@gmail.com CC: alexander.loh...@gmx.de, natalie_clar...@yahoo.de Target Milestone: --- The search algorithm for recent files is not very "smart" and requires knowing the beginning of the filename. E.g. if the file is called "Carroll and the tortoise.pdf", searching any substring that does not include the initial segment will fail to return anything, e.g. searching "tortoise" will not return anything but "carr" will. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474771] New: in Wayland a "ghost" Mouse Cursor stays at edge of externally connected display
https://bugs.kde.org/show_bug.cgi?id=474771 Bug ID: 474771 Summary: in Wayland a "ghost" Mouse Cursor stays at edge of externally connected display Classification: Plasma Product: kwin Version: 5.27.8 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: natato...@hotmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Connect external display to NVidia driven port on Intel/Nvidia hybrid laptop 2. Move mouse from external display and primary display OBSERVED RESULT with inconsistent results, the image of the mouse cursor will remain toward the edge of the exited display while an active cursor will continue on the other displays. This "ghost" image cursor will remain until the active cursor re-enters the view of the external display. EXPECTED RESULT Mouse cursor flows from one display to the next, disappearing completely from the frame of the exited display SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon (available in About System) KDE Plasma Version: 5.27.8 - Wayland Session KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION * display connected to NVidia driven port on an intel/nvidia hybrid laptop * reddit user Zamundaa is aware and wanted me to report it so they could look into possibly backporting a fix from 6 back to 5.27 * Original post: https://www.reddit.com/r/kde/comments/16npjma/wayland_bug_external_monitor_edge_cursor_wonkiness/ -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 450551] Battery charge limit is not preserved after reboot on many laptops that support charge limits; need to write it on every boot
https://bugs.kde.org/show_bug.cgi?id=450551 --- Comment #40 from Michael --- (In reply to ioo+kde from comment #39) > So #17 is a systemd service that run this command: > echo 75 > /sys/class/power_supply/CMB0/charge_control_end_threshold > > but when I run it as root I get: > bash: echo: write error: Invalid argument First do this: ls -la /sys/class/power_supply/ ... and you'll see something differing from CMB0. In my case, I see ACAD and BAT1. I substitute BAT1 for CMB0 in your case. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474273] plasmashell restarted from a non-standard directory may hold open mount points wrongly
https://bugs.kde.org/show_bug.cgi?id=474273 --- Comment #2 from Michael Reilly --- (In reply to Nate Graham from comment #1) > How exactly did you quit and relaunch plasma? What command did you use? Sorry about the long delay in response, I seem to have not received a notification. You can reproduce this behavior by doing $ cd /mount/point $ kquitapp5 plasmashell && kstart5 plasmashell $ cd / to launch the plasmashell from below the mount point, launch plasmashell within the pwd of the mounted drive, then exit the mounted drive (so the shell itself isn't holding the mount point open). -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 450551] Battery charge limit is not preserved after reboot on many laptops that support charge limits; need to write it on every boot
https://bugs.kde.org/show_bug.cgi?id=450551 --- Comment #38 from Michael --- > How does the KDE Neon GUI write to this file? I can set the value with the > GUI and it does update the file so its possible but nothing I can find will > allow me to set the value. I always get an 'Invalid argument' error. I am running KDE neon User Edition and what worked for me was linked to by comment #17 https://bugs.kde.org/show_bug.cgi?id=450551#c17 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 474634] Qwenview crashes when scanning a folder
https://bugs.kde.org/show_bug.cgi?id=474634 --- Comment #1 from Michael Hamilton --- Created attachment 161682 --> https://bugs.kde.org/attachment.cgi?id=161682=edit Image with bad exif that caused the issue -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 474634] New: Qwenview crashes when scanning a folder
https://bugs.kde.org/show_bug.cgi?id=474634 Bug ID: 474634 Summary: Qwenview crashes when scanning a folder Classification: Applications Product: gwenview Version: 23.08.0 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: mich...@actrix.gen.nz Target Milestone: --- Application: gwenview (23.08.0) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 6.5.3-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: When using gwenview to open a image from Dolphin, it appears to start to display the image but then crashes. The crash is caused by the scanning the other files in the same folder when one of those files contains exif data that it cannot cope with. I used showfioto to open the image with the bad exif, then saved it to rewrite the exif. After making the correction, gwenview worked properly - I could open the image file I wanted and it no longer fell over on scanning the folder containing the offending image, The crash can be reproduced every time. -- Backtrace: Application: Gwenview (gwenview), signal: Aborted [KCrash Handler] #4 0x7fec77e91e0c in __pthread_kill_implementation () from /lib64/libc.so.6 #5 0x7fec77e3f0e6 in raise () from /lib64/libc.so.6 #6 0x7fec77e268d7 in abort () from /lib64/libc.so.6 #7 0x7fec782acc17 in ?? () from /lib64/libstdc++.so.6 #8 0x7fec782bc1fc in ?? () from /lib64/libstdc++.so.6 #9 0x7fec782bc267 in std::terminate() () from /lib64/libstdc++.so.6 #10 0x7fec782bc4c8 in __cxa_throw () from /lib64/libstdc++.so.6 #11 0x7fec786bcd6f in QUnhandledException::raise() const () from /lib64/libQt5Core.so.5 #12 0x7fec7870ac8d in QFutureInterfaceBase::waitForResult(int) () from /lib64/libQt5Core.so.5 #13 0x7fec7abcbe1f in ?? () from /lib64/libgwenviewlib.so.5 #14 0x7fec78925812 in ?? () from /lib64/libQt5Core.so.5 #15 0x7fec7870d995 in QFutureWatcherBase::event(QEvent*) () from /lib64/libQt5Core.so.5 #16 0x7fec795a519e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #17 0x7fec788ed568 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #18 0x7fec788f0b61 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #19 0x7fec78946c93 in ?? () from /lib64/libQt5Core.so.5 #20 0x7fec765169d8 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #21 0x7fec76516de8 in ?? () from /lib64/libglib-2.0.so.0 #22 0x7fec76516e7c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #23 0x7fec789464a6 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #24 0x7fec788ebffb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #25 0x7fec788f4490 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #26 0x55ff15557423 in ?? () #27 0x7fec77e281b0 in __libc_start_call_main () from /lib64/libc.so.6 #28 0x7fec77e28279 in __libc_start_main_impl () from /lib64/libc.so.6 #29 0x55ff15557b85 in ?? () [Inferior 1 (process 16878) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474588] New: Plasma crash related to an alternative app launcher widget
https://bugs.kde.org/show_bug.cgi?id=474588 Bug ID: 474588 Summary: Plasma crash related to an alternative app launcher widget Classification: Plasma Product: plasmashell Version: 5.27.7 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: michaeldrummon...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.7) Qt Version: 5.15.10 Frameworks Version: 5.107.0 Operating System: Linux 6.4.0-4-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux trixie/sid DrKonqi: 5.27.7 [CoredumpBackend] -- Information about the crash: Plasma crashed after installing Avalon Menu and then switching back to default Application Launcher. This happens every time on KDE Plasma 5.27.7. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 1242 (plasmashell) UID: 1000 (mikde) GID: 1000 (mikde) Signal: 11 (SEGV) Timestamp: Sat 2023-09-16 03:10:30 MST (41s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (mikde) Boot ID: 294558ef2f434459b7ca10e007a4e51e Machine ID: 045c94cdf9834dde9d3a04441987ad19 Hostname: mikeDeb Storage: /var/lib/systemd/coredump/core.plasmashell.1000.294558ef2f434459b7ca10e007a4e51e.1242.169485903000.zst (present) Size on Disk: 46.1M Message: Process 1242 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-254.1-3.amd64 Module libudev.so.1 from deb systemd-254.1-3.amd64 Stack trace of thread 1242: #0 0x7f01844acfd4 pthread_sigmask (libc.so.6 + 0x8efd4) #1 0x7f018445a6e9 sigprocmask (libc.so.6 + 0x3c6e9) #2 0x7f0186edce9b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4e9b) #3 0x7f0186eddb3e _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b3e) #4 0x7f018445a500 n/a (libc.so.6 + 0x3c500) Stack trace of thread 1731: #0 0x7f01844a3146 n/a (libc.so.6 + 0x85146) #1 0x7f01844a5808 pthread_cond_wait (libc.so.6 + 0x87808) #2 0x7f0184adfbfb _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xdfbfb) #3 0x7f0186a08835 n/a (libQt5Quick.so.5 + 0x208835) #4 0x7f0186a0ac61 n/a (libQt5Quick.so.5 + 0x20ac61) #5 0x7f0184ad9ffd n/a (libQt5Core.so.5 + 0xd9ffd) #6 0x7f01844a63dc n/a (libc.so.6 + 0x883dc) #7 0x7f0184526a1c n/a (libc.so.6 + 0x108a1c) Stack trace of thread 2512: #0 0x7f01844a3146 n/a (libc.so.6 + 0x85146) #1 0x7f01844a5808 pthread_cond_wait (libc.so.6 + 0x87808) #2 0x7f0184adfbfb _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xdfbfb) #3 0x7f0186a08835 n/a (libQt5Quick.so.5 + 0x208835) #4 0x7f0186a0ac61 n/a (libQt5Quick.so.5 + 0x20ac61) #5 0x7f0184ad9ffd n/a (libQt5Core.so.5 + 0xd9ffd) #6 0x7f01844a63dc n/a (libc.so.6 + 0x883dc) #7 0x7f0184526a1c n/a (libc.so.6 + 0x108a1c) Stack trace of thread 1644: #0 0x7f01844ac890 pthread_self (libc.so.6 + 0x8e890) #1 0x7f017686c5fd n/a (libnvidia-glcore.so.525.125.06 + 0x146c5fd) #2 0x7f01768dad6d n/a (libnvidia-glcore.so.525.125.06 + 0x14dad6d) #3 0x7f01768726d8 n/a (libnvidia-glcore.so.525.125.06 + 0x14726d8) #4 0x7f0176872aaa n/a (libnvidia-glcore.so.525.125.06 + 0x1472aaa) #5 0x7f017687038a n/a (libnvidia-glcore.so.525.125.06 + 0x147038a) #6 0x7f01844a63dc n/a (libc.so.6 + 0x883dc) #7 0x7f0184526a1c n/a (libc.so.6 + 0x108a1c) Stack trace of thread 1626: #0 0x7f01844a3146 n/a (libc.so.6 + 0x85146) #1 0x7f01844a5808 pthread_cond_wait (libc.so.6 + 0x87808) #2 0x7f0184adfbfb _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xdfbfb) #3 0x7f0186a08835 n/a (libQt5Quick.so.5 + 0x208835) #4 0x7f0186a0ac61
[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 #11 from Michael Lashkevich --- Nearly half a year. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 472191] Kdiff3 crashes on exit
https://bugs.kde.org/show_bug.cgi?id=472191 michael changed: What|Removed |Added CC||k...@jaggard.org.uk --- Comment #6 from michael --- *** Bug 474215 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 474215] Segmentation Fault 11 when quitting kdiff3
https://bugs.kde.org/show_bug.cgi?id=474215 michael changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from michael --- *** This bug has been marked as a duplicate of bug 472191 *** -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 472191] Kdiff3 crashes on exit
https://bugs.kde.org/show_bug.cgi?id=472191 michael changed: What|Removed |Added Summary|Kdiff3 aborts on exit on|Kdiff3 crashes on exit |aarm64 MacOS| OS|macOS |All -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474273] New: plasmashell restarted from a non-standard directory may hold open mount points wrongly
https://bugs.kde.org/show_bug.cgi?id=474273 Bug ID: 474273 Summary: plasmashell restarted from a non-standard directory may hold open mount points wrongly Classification: Plasma Product: plasmashell Version: 5.27.7 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: omnipotentent...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Mount a USB drive with the GUI widget 2. Shut down plasmashell and relaunch from a command line with a working directory at or below the mount point of the USB drive 3. Attempt to safely remove the USB drive with the GUI widget OBSERVED RESULT The USB drive fails to unmount via the GUI widget, or indeed via umount, until the plasmashell is closed and relaunched from a different working directory. No diagnostic is given. EXPECTED RESULT plasmashell should be able to unmount this drive, (by, for instance, changing its current working directory). SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS 23.05 (available in About System) KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION Encountered this issue after a plasmashell crash and I relaunched the plasmashell from the nearest command line handy, which happened to be in a subdirectory of the mounted drive, because I was using it to transfer files. Because this process was quite time consuming, it wasn't until the next day that I attempted to remove the drive, and I spent a few mystified minutes trying to figure out what was holding the drive open. I don't think this would be a commonly encountered issue, but it's also one that seems to be easy to fix by changing the current working directory on launch, as plasmashell doesn't seem to be sensitive to this value at all. -- 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/ ||kdesrc-build/-/commit/5b155 ||c5e29dd2d377fd1f84fb42d0e62 ||9a9f368b Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Michael Pyne --- Git commit 5b155c5e29dd2d377fd1f84fb42d0e629a9f368b by Michael Pyne. Committed on 07/09/2023 at 02:34. Pushed by mpyne into branch 'master'. 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 M +11 -11 doc/index.docbook M +28 -10 doc/man-kdesrc-build.1.docbook M +37 -21 modules/ksb/Cmdline.pm https://invent.kde.org/sdk/kdesrc-build/-/commit/5b155c5e29dd2d377fd1f84fb42d0e629a9f368b -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474213] New: kwin_wayland crashes sometimes after connecting external display
https://bugs.kde.org/show_bug.cgi?id=474213 Bug ID: 474213 Summary: kwin_wayland crashes sometimes after connecting external display Classification: Plasma Product: kwin Version: 5.27.7 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: nortex...@gmail.com Target Milestone: --- Sometimes I connect an external display (via USB-C) while my laptop is asleep. When I resume, kwin crashes and I'm greeted by a fresh session on the external display. (It doesn't crash to SDDM.) Not sure where to find useful logs for this. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 472612] Crash when adding Manual Diff Alignment
https://bugs.kde.org/show_bug.cgi?id=472612 michael changed: What|Removed |Added Version Fixed In||1.10.6 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from michael --- The crash appears to be resolved in the latest source both stable and dev. However it is unclear to me exactly what changed this. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 422820] You are prompted with "The output has been modified. If you continue your changes will be lost" multiple times
https://bugs.kde.org/show_bug.cgi?id=422820 michael changed: What|Removed |Added Latest Commit|https://invent.kde.org/sdk/ |https://invent.kde.org/sdk/ |kdiff3/-/commit/9536120f039 |kdiff3/-/commit/aa9e782c58c |6c597980a2e13c8e9111de9c6e0 |ae3ada688f3f1d3eafbb2eef13b |eb |f2 --- Comment #4 from michael --- Git commit aa9e782c58cae3ada688f3f1d3eafbb2eef13bf2 by Michael Reeves. Committed on 02/09/2023 at 03:16. Pushed by mreeves into branch '1.10'. Insure MergeResultWindow::connectActions is only called once FIXED-IN:1.10.6 M +13 -9src/mergeresultwindow.cpp https://invent.kde.org/sdk/kdiff3/-/commit/aa9e782c58cae3ada688f3f1d3eafbb2eef13bf2 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 422820] You are prompted with "The output has been modified. If you continue your changes will be lost" multiple times
https://bugs.kde.org/show_bug.cgi?id=422820 michael changed: What|Removed |Added Latest Commit||https://invent.kde.org/sdk/ ||kdiff3/-/commit/9536120f039 ||6c597980a2e13c8e9111de9c6e0 ||eb Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||1.10.6 --- Comment #3 from michael --- Git commit 9536120f0396c597980a2e13c8e9111de9c6e0eb by Michael Reeves. Committed on 02/09/2023 at 03:14. Pushed by mreeves into branch 'master'. Insure MergeResultWindow::connectActions is only called once FIXED-IN:1.10.6 M +13 -9src/mergeresultwindow.cpp https://invent.kde.org/sdk/kdiff3/-/commit/9536120f0396c597980a2e13c8e9111de9c6e0eb -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454946] plasmashell crashes in ShellCorona::loadLookAndFeelDefaultLayout() when switching between Global Theme desktop layouts
https://bugs.kde.org/show_bug.cgi?id=454946 Michael Mikowski changed: What|Removed |Added CC||z_mikow...@yahoo.com --- Comment #40 from Michael Mikowski --- This looks promising Harald. Kfocus will test with 5.27.8 across multiple installations and report back. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468648] Move OSD popups away from center
https://bugs.kde.org/show_bug.cgi?id=468648 Michael D changed: What|Removed |Added CC||nortex...@gmail.com --- Comment #3 from Michael D --- The position of the OSD along the y-axis is very odd indeed, and it would be nice to see it moved further down. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473800] New: Kwin crashed after changing fonts.
https://bugs.kde.org/show_bug.cgi?id=473800 Bug ID: 473800 Summary: Kwin crashed after changing fonts. Classification: Plasma Product: kwin Version: 5.27.7 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: michael.lucky.maxi...@gmail.com Target Milestone: --- Application: kwin_x11 (5.27.7) Qt Version: 5.15.10 Frameworks Version: 5.109.0 Operating System: Linux 6.4.11-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.7 [CoredumpBackend] -- Information about the crash: Changed current font to a freshly installed system font. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault PID: 20615 (kwin_x11) UID: 1000 (michael) GID: 1000 (michael) Signal: 11 (SEGV) Timestamp: Sun 2023-08-27 19:34:53 PST (1min 14s ago) Command Line: /usr/bin/kwin_x11 --replace Executable: /usr/bin/kwin_x11 Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_x11.service Unit: user@1000.service User Unit: plasma-kwin_x11.service Slice: user-1000.slice Owner UID: 1000 (michael) Boot ID: 006c7bf6241d4708ade6dbc60baab4a1 Machine ID: 3daf6b71ed714c1998d7dbbb870bf911 Hostname: 192.168.254.105 Storage: /var/lib/systemd/coredump/core.kwin_x11.1000.006c7bf6241d4708ade6dbc60baab4a1.20615.169313609300.zst (present) Size on Disk: 5.5M Message: Process 20615 (kwin_x11) of user 1000 dumped core. Stack trace of thread 20615: #0 0x7f7c5cc97308 pthread_sigmask@GLIBC_2.2.5 (libc.so.6 + 0x97308) #1 0x7f7c5cc3f40d sigprocmask (libc.so.6 + 0x3f40d) #2 0x7f7c6005c8db _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x58db) #3 0x7f7c6005ed93 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x7d93) #4 0x7f7c5cc3f1f0 n/a (libc.so.6 + 0x3f1f0) Stack trace of thread 20627: #0 0x7f7c5cc8c54e __futex_abstimed_wait_common (libc.so.6 + 0x8c54e) #1 0x7f7c5cc8f5b5 pthread_cond_timedwait@@GLIBC_2.3.2 (libc.so.6 + 0x8f5b5) #2 0x7f7c5e10980c _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0x10980c) #3 0x7f7c5e1076dc n/a (libQt5Core.so.5 + 0x1076dc) #4 0x7f7c5e103ffd n/a (libQt5Core.so.5 + 0x103ffd) #5 0x7f7c5cc8ffa4 start_thread (libc.so.6 + 0x8ffa4) #6 0x7f7c5cd187fc __clone3 (libc.so.6 + 0x1187fc) Stack trace of thread 20636: #0 0x7f7c5cd0a0af __poll (libc.so.6 + 0x10a0af) #1 0x7f7c4e72b297 n/a (libnvidia-glcore.so.535.86.05 + 0x152b297) #2 0x7f7c4e713a24 n/a (libnvidia-glcore.so.535.86.05 + 0x1513a24) #3 0x7f7c5cc8ffa4 start_thread (libc.so.6 + 0x8ffa4) #4 0x7f7c5cd187fc __clone3 (libc.so.6 + 0x1187fc) Stack trace of thread 20622: #0 0x7f7c5cd0a0af __poll (libc.so.6 + 0x10a0af) #1 0x7f7c5b916d3e n/a (libglib-2.0.so.0 + 0x5dd3e) #2 0x7f7c5b916e5c g_main_context_iteration (libglib-2.0.so.0 + 0x5de5c) #3 0x7f7c5e3464be _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x3464be) #4 0x7f7c5e2ebffb _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2ebffb) #5 0x7f7c5e102dce _ZN7QThread4execEv (libQt5Core.so.5 + 0x102dce) #6 0x7f7c5db59517 n/a (libQt5DBus.so.5 + 0x1a517) #7 0x7f7c5e103ffd n/a (libQt5Core.so.5 + 0x103ffd) #8 0x7f7c5cc8ffa4 start_thread (libc.so.6 + 0x8ffa4) #9 0x7f7c5cd187fc __clone3 (libc.so.6 + 0x1187fc) Stack trace of thread 20630: #0 0x7f7c5cc8c54e __futex_abstimed_wait_common (libc.so.6 + 0x8c54e) #1 0x7f7c5cc8f5b5 pthread_cond_timedwait@@GLIBC_2.3.2 (libc.so.6 + 0x8f5b5) #2 0x7f7c5e10980c _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0x10980c) #3 0x7f7c5e1076dc n/a (libQt5Core.so.5 + 0x1076dc) #4 0x7f7c5e103ffd n/a (libQt5Core.so.5 + 0x103ffd) #5 0x7f7c5cc8ffa4 start_thread (libc.so.6 + 0x8ffa4) #6 0x7f7c5cd187fc __clone3 (libc.so.6 + 0x1187fc) Stack trace of thread 20628: #0 0x7f
[kdevplatform] [Bug 473749] New: Kdevelop not able to add documentation
https://bugs.kde.org/show_bug.cgi?id=473749 Bug ID: 473749 Summary: Kdevelop not able to add documentation Classification: Developer tools Product: kdevplatform Version: 5.6.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: templates Assignee: kdevelop-bugs-n...@kde.org Reporter: i...@rechtsanwaltsteyer.de Target Milestone: --- I use MX-Linux 23 (debian bookworm) and KDevelop 5.10.221202. If I want to add a documentation via Einstellungen (settings), documentation/Qt-Hilfe (path: /home/luzifer/Daten/Programmierung/Literatur/Qt/Hilfedateien/cppreference-doc-en-cpp.qch) it is not possible to open this documentation via the documentation-window in the IDE itself. BTW: The same Procedure works perfect under KDevelop 5.6.2 in MX-Linux 21.3 (debian bullseye) -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 473399] On Git master/1.10, application crashes when word wrap is enabled, selecting text, and refreshing diff
https://bugs.kde.org/show_bug.cgi?id=473399 michael changed: What|Removed |Added Latest Commit|https://invent.kde.org/sdk/ |https://invent.kde.org/sdk/ |kdiff3/-/commit/74792ce8aa7 |kdiff3/-/commit/6585c91fea3 |95deb7397ca224f63543996b5de |20d2f6d909766c836bcbc0c5b23 |15 |0d --- Comment #2 from michael --- Git commit 6585c91fea320d2f6d909766c836bcbc0c5b230d by Michael Reeves. Committed on 25/08/2023 at 03:30. Pushed by mreeves into branch '1.10'. Correct mishandling of empty m_diff3WrapLineVector DiffTextWindow::convertLineCoordsToD3LCoords can be called when m_diff3WrapLineVector is empty. This has always been then case but for some reason hasn't happened previously. Nothing in the way this function is used suggests it was ever guaranteed to be working with a non-empty m_diff3WrapLineVector In fact its called in KDiff3App::recalcWordWrap before the new word warp is computed. Therefor we can not assume m_diff3WrapLineVector is non-empty as it is cleared by default. FIXED-IN:1.10.6 M +2-2src/difftextwindow.cpp https://invent.kde.org/sdk/kdiff3/-/commit/6585c91fea320d2f6d909766c836bcbc0c5b230d -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 473399] On Git master/1.10, application crashes when word wrap is enabled, selecting text, and refreshing diff
https://bugs.kde.org/show_bug.cgi?id=473399 michael changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||1.10.6 Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/sdk/ ||kdiff3/-/commit/74792ce8aa7 ||95deb7397ca224f63543996b5de ||15 --- Comment #1 from michael --- Git commit 74792ce8aa795deb7397ca224f63543996b5de15 by Michael Reeves. Committed on 25/08/2023 at 03:30. Pushed by mreeves into branch 'master'. Correct miss-handling of empty m_diff3WrapLineVector DiffTextWindow::convertLineCoordsToD3LCoords can be called when m_diff3WrapLineVector is empty. This has always been then case but for some reason hasn't happened previously. Nothing in the way this function is used suggests it was ever guaranteed to be working with a non-empty m_diff3WrapLineVector In fact its called in KDiff3App::recalcWordWrap before the new word warp is computed. Therefor we can not assume m_diff3WrapLineVector is non-empty as it is cleared by default. FIXED-IN:1.10.6 M +2-2src/difftextwindow.cpp https://invent.kde.org/sdk/kdiff3/-/commit/74792ce8aa795deb7397ca224f63543996b5de15 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 473610] New: Kalender eintrag
https://bugs.kde.org/show_bug.cgi?id=473610 Bug ID: 473610 Summary: Kalender eintrag Classification: Applications Product: kontact Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: petry-pohlhe...@t-online.de Target Milestone: --- Application: kontact (5.23.3 (23.04.3)) Qt Version: 5.15.10 Frameworks Version: 5.108.0 Operating System: Linux 6.4.9-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.7 [KCrashBackend] -- Information about the crash: Bei einem Eintrag für den Kalender und Teilnehmer die per E-Mail eingeladen wurden, stürtze die Anwendung ab The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 0x7f15e12bc072 in QSortFilterProxyModel::parent(QModelIndex const&) const () from /lib64/libQt5Core.so.5 #5 0x7f15e12872af in QPersistentModelIndex::parent() const () from /lib64/libQt5Core.so.5 #6 0x7f15e129b073 in ?? () from /lib64/libQt5Core.so.5 #7 0x7f15e12a249c in ?? () from /lib64/libQt5Core.so.5 #8 0x7f15e13257b3 in ?? () from /lib64/libQt5Core.so.5 #9 0x7f15e12862e6 in QAbstractItemModel::layoutChanged(QList const&, QAbstractItemModel::LayoutChangeHint) () from /lib64/libQt5Core.so.5 #10 0x7f15e12be6d6 in ?? () from /lib64/libQt5Core.so.5 #11 0x7f15e13257b3 in ?? () from /lib64/libQt5Core.so.5 #12 0x7f15e12862e6 in QAbstractItemModel::layoutChanged(QList const&, QAbstractItemModel::LayoutChangeHint) () from /lib64/libQt5Core.so.5 #13 0x7f157879393a in ?? () from /lib64/libKPim5IncidenceEditor.so.5 #14 0x7f157878420a in ?? () from /lib64/libKPim5IncidenceEditor.so.5 #15 0x7f15787d3cb3 in ?? () from /lib64/libKPim5IncidenceEditor.so.5 #16 0x7f15787879b5 in ?? () from /lib64/libKPim5IncidenceEditor.so.5 #17 0x7f15e1325812 in ?? () from /lib64/libQt5Core.so.5 #18 0x7f15e2695845 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib64/libKF5CoreAddons.so.5 #19 0x7f15e2699beb in ?? () from /lib64/libKF5CoreAddons.so.5 #20 0x7f15e1319320 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #21 0x7f15e1fa519e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #22 0x7f15e12ed568 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #23 0x7f15e12f0b61 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #24 0x7f15e1346c93 in ?? () from /lib64/libQt5Core.so.5 #25 0x7f15d7b169b8 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #26 0x7f15d7b16dc8 in ?? () from /lib64/libglib-2.0.so.0 #27 0x7f15d7b16e5c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #28 0x7f15e13464a6 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #29 0x7f15e12ebffb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #30 0x7f15e12f4490 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #31 0x561e370e8fe3 in ?? () #32 0x7f15e08281f0 in __libc_start_call_main () from /lib64/libc.so.6 #33 0x7f15e08282b9 in __libc_start_main_impl () from /lib64/libc.so.6 #34 0x561e370e9625 in ?? () [Inferior 1 (process 21296) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 472191] Kdiff3 aborts on exit on aarm64 MacOS
https://bugs.kde.org/show_bug.cgi?id=472191 michael changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||1.10.6 Resolution|--- |FIXED --- Comment #5 from michael --- The last build you also included changes in KDiff3 that hopefully that will resolve the crash. Difficult to know for sure since my test machine doesn't replicate the crash. Feel free to reopen this if it happens again. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 472327] Crash while quit
https://bugs.kde.org/show_bug.cgi?id=472327 michael changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from michael --- *** This bug has been marked as a duplicate of bug 472191 *** -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 472191] Kdiff3 aborts on exit on aarm64 MacOS
https://bugs.kde.org/show_bug.cgi?id=472191 michael changed: What|Removed |Added CC||erben...@gmail.com --- Comment #4 from michael --- *** Bug 472327 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 472191] Kdiff3 aborts on exit on aarm64 MacOS
https://bugs.kde.org/show_bug.cgi?id=472191 michael changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|DUPLICATE |--- -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473449] Duplicate search restriction is sometimes ignored
https://bugs.kde.org/show_bug.cgi?id=473449 --- Comment #2 from Michael --- Then I guess I'm the next one to have problems with this. I usually move large amounts of images. For a gut feeling, I have attached my database statistics below. There are already duplicates in the database that I have to keep with different metadata. On the other hand, I already have a few thousand images to import again and I have to find the images in those imports that are already in the database. So my requirement is to find all the images in the import that are already in the database. But I only want to delete duplicates from the import. So practically the whole existing database is the reference. Sometimes I also get a request to preserve a duplicate from the import and add it to the current database with new metadata. So it would help me if I can define what the albums of the reference images are and which albums are the images to be searched. Whether an album is then just a reference, a search or both is then completely up to me. The rest regarding quality and information content of an image, I could cover so far with the advanced search. So in principle, I don't need this function to automatically select the reference, because I usually do that in advance via other functions and filter out the required qualities. So now my question regarding the duplicate search, do you have any advice for me on how to achieve my goal if this is not a bug? How shall we proceed with this ticket? Thanks and many greetings Michael digikam version 8.1.0 Images: AVIF: 1 BMP: 6695 EPS: 6 GIF: 23135 ICNS: 6 ICO: 94 JP2: 2 JPEG: 141 JPG: 1339786 KRA: 2 PCX: 956 PNG: 34809 PPM: 26 PSD: 17 RAW-ARW: 8 RAW-CR2: 30737 RAW-CRW: 903 RAW-DNG: 34 RAW-HDR: 1 RAW-RAW: 1 TGA: 157 TIFF: 340 WEBP: 2817 WMF: 6 XCF: 97 XPM: 10 total: 1440787 : Videos: 3GP: 223 AVI: 1591 MOV: 2395 MP4: 5994 MPEG: 55 VOB: 47 WMV: 240 total: 10545 : Audio: AAC: 85 M4A: 150 MP3: 17302 MP4: 3 MPC: 7 OGG: 340 WAV: 1313 WMA: 6 total: 19206 : Total Items: 1470538 Albums: 86485 Tags: 2618 : Database backend: QSQLITE Database Path: F:/digikam_db/ Database locale: UTF-8 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473449] New: Duplicate search restriction is sometimes ignored
https://bugs.kde.org/show_bug.cgi?id=473449 Bug ID: 473449 Summary: Duplicate search restriction is sometimes ignored Classification: Applications Product: digikam Version: 8.1.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Searches-Similarity Assignee: digikam-bugs-n...@kde.org Reporter: mas_masterandserv...@outlook.de Target Milestone: --- Created attachment 161004 --> https://bugs.kde.org/attachment.cgi?id=161004=edit Faulty result SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** Searching with restrictions does not always seem to work properly and returns unexpected results. I tested with 2 albums ( A and B ) and used 3 different images ( 1, 2 and 3 ). The albums are structured as follows: Root + A ( 1, 1, 3 ) + B ( 1, 1, 2, 2, 3 ) STEPS TO REPRODUCE 1. Search in both albums for duplicates with the restriction "Exclude Reference Album". 2. Now add the configuration that the reference should be in a different album than A OBSERVED RESULT Now duplicates are found in both albums. But in A only 1 of 2 and in B the reference and the other duplicate. EXPECTED RESULT I expected that both duplicates are found in A and in B only the reference is present. See also screenshot SOFTWARE/OS VERSIONS Windows: WIN 11 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Perhaps the search is also easier to handle and implement if the search is redesigned in such a way that one can directly specify where to search for the references and where to delete. This would mean that the reference set R and the set of duplicates D to be deleted or found could be defined as follows: R=D ( General search for duplicates in the whole database ). R≠D ( E.g. matching of an import with a certain other image set ) S∩D or S∪D ( Restriction to certain sets ) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473396] New: HEIC images not rotated correctly even though EXIF metadata could be read
https://bugs.kde.org/show_bug.cgi?id=473396 Bug ID: 473396 Summary: HEIC images not rotated correctly even though EXIF metadata could be read Classification: Applications Product: digikam Version: 8.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Exif Assignee: digikam-bugs-n...@kde.org Reporter: b...@kofler.info Target Milestone: --- SUMMARY Imported HEIC images are not rotated according to EXIF data. STEPS TO REPRODUCE 1. imported HEIC image in portrait mode (from iPhone 13) 2. shotwell shows image in wrong rotation EXIF-Metadata is processed correctly, says orientation = right/top SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.27 ADDITIONAL INFORMATION I was impressed HEIC import worked at all without searching for HEIF libraries :-) -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 472718] Merge conflict resolved to empty is saved as newline
https://bugs.kde.org/show_bug.cgi?id=472718 michael changed: What|Removed |Added Latest Commit|https://invent.kde.org/sdk/ |https://invent.kde.org/sdk/ |kdiff3/-/commit/546d17293bb |kdiff3/-/commit/760d38c0d50 |a213fc6b06d0e0b7f4a9688cd06 |c48d07e21f1ebf3b8e6443e8dbf |50 |d3 --- Comment #2 from michael --- Git commit 760d38c0d50c48d07e21f1ebf3b8e6443e8dbfd3 by Michael Reeves. Committed on 14/08/2023 at 05:51. Pushed by mreeves into branch '1.10'. Account for deleted lines when determining first line of output. FIXED-IN:1.10.6 M +5-3src/mergeresultwindow.cpp https://invent.kde.org/sdk/kdiff3/-/commit/760d38c0d50c48d07e21f1ebf3b8e6443e8dbfd3 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 472718] Merge conflict resolved to empty is saved as newline
https://bugs.kde.org/show_bug.cgi?id=472718 michael changed: What|Removed |Added Version Fixed In||1.10.6 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/sdk/ ||kdiff3/-/commit/546d17293bb ||a213fc6b06d0e0b7f4a9688cd06 ||50 --- Comment #1 from michael --- Git commit 546d17293bba213fc6b06d0e0b7f4a9688cd0650 by Michael Reeves. Committed on 14/08/2023 at 05:31. Pushed by mreeves into branch 'master'. Account for deleted lines when determining first line of output. FIXED-IN:1.10.6 M +5-3src/mergeresultwindow.cpp https://invent.kde.org/sdk/kdiff3/-/commit/546d17293bba213fc6b06d0e0b7f4a9688cd0650 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473355] Big trash bin freezes digikam for long time
https://bugs.kde.org/show_bug.cgi?id=473355 --- Comment #2 from Michael --- My workaround is to delete the ".dtrash" folder directly by the windows file explorer. So I assume that it takes so long, cause digikam has to read all data from the files in .dtrash again. The .dtrash does not live on a SDD like the SQLiteDB. It it lives on a simple, old mobile HDD. Maybe I should simply empty the trash more often. With <10.000 images it is working pretty good. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 473355] New: Big trash bin freezes digikam for long time
https://bugs.kde.org/show_bug.cgi?id=473355 Bug ID: 473355 Summary: Big trash bin freezes digikam for long time Classification: Applications Product: digikam Version: 8.1.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Albums-Trash Assignee: digikam-bugs-n...@kde.org Reporter: mas_masterandserv...@outlook.de Target Milestone: --- Created attachment 160942 --> https://bugs.kde.org/attachment.cgi?id=160942=edit Screenshot during freeze SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I am running digikam's sqlitedb on a SSD. Everything is fast enough and response times are great for me, even if I have to wait some minutes. But now I have to wait for a very long time. STEPS TO REPRODUCE 1. Have a huge db with >1.000.000 images 2. Remove >80.000 images with a search for duplicates. Can be done in several steps. 3. Select the album trash OBSERVED RESULT Digikam freezes until some background work is done. I do not know which. It takes more than 2 hours in my case. After that digikam works normal again and I can work with it. EXPECTED RESULT Album trash opens faster like my biggest albums with > 80.000 images SOFTWARE/OS VERSIONS Windows: WIN 11 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Thanks for this great software! Greetings Michael -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 472191] Kdiff3 aborts on exit on aarm64 MacOS
https://bugs.kde.org/show_bug.cgi?id=472191 michael changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from michael --- *** This bug has been marked as a duplicate of bug 472327 *** -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 472327] Crash while quit
https://bugs.kde.org/show_bug.cgi?id=472327 michael changed: What|Removed |Added CC||m...@fireburn.co.uk --- Comment #1 from michael --- *** Bug 472191 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 374017] Stream audio between devices
https://bugs.kde.org/show_bug.cgi?id=374017 Michael changed: What|Removed |Added CC||mailinglis...@kmhessler.de --- Comment #11 from Michael --- As mentioned from @evea https://bugs.kde.org/show_bug.cgi?id=374017#c0: > It would be great if you could enable audio output to you Android Device. Furthermore it may support local LAN- or wLAN-speakers ... Is there any schedule for this enhancement? I'd appreciate it very much ... As mentioned from @ npeters https://bugs.kde.org/show_bug.cgi?id=374017#c7 > AudioRelay Anybody experiences with AudioRelay https://audiorelay.net/? What is supported, what is missing? -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 472270] Crash when ignoring whitespace and diffing files with trailing whitespace
https://bugs.kde.org/show_bug.cgi?id=472270 michael changed: What|Removed |Added Latest Commit|https://invent.kde.org/sdk/ |https://invent.kde.org/sdk/ |kdiff3/-/commit/9c2901040c3 |kdiff3/-/commit/341bb032202 |40696d9e7b9fea81bdc0b32a0fc |6053400def3aa7f46e1ac171d0f |b3 |c5 --- Comment #3 from michael --- Git commit 341bb0322026053400def3aa7f46e1ac171d0fc5 by Michael Reeves, on behalf of Nyan Pasu. Committed on 08/08/2023 at 17:47. Pushed by mreeves into branch '1.10'. Fix segfault if ignoring whitespace FIXED-IN:1.10.5 M +48 -10 src/diff.cpp https://invent.kde.org/sdk/kdiff3/-/commit/341bb0322026053400def3aa7f46e1ac171d0fc5 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 472270] Crash when ignoring whitespace and diffing files with trailing whitespace
https://bugs.kde.org/show_bug.cgi?id=472270 michael changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/sdk/ ||kdiff3/-/commit/9c2901040c3 ||40696d9e7b9fea81bdc0b32a0fc ||b3 Status|REPORTED|RESOLVED Version Fixed In||1.10.5 --- Comment #2 from michael --- Git commit 9c2901040c340696d9e7b9fea81bdc0b32a0fcb3 by Michael Reeves, on behalf of Nyan Pasu. Committed on 08/08/2023 at 17:47. Pushed by mreeves into branch 'master'. Fix segfault if ignoring whitespace FIXED-IN:1.10.5 M +48 -10 src/diff.cpp https://invent.kde.org/sdk/kdiff3/-/commit/9c2901040c340696d9e7b9fea81bdc0b32a0fcb3 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 472236] Maximized window state/size not properly restored
https://bugs.kde.org/show_bug.cgi?id=472236 --- Comment #3 from michael --- Weirdly on my test machine this starts out restored correctly. However on clicking cancel at the the initial open dialog to maximized status is flipped. This seems to be windows specific and does not happen under linux. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 467868] kdialog --getopenfilename filter argument regresses, needs updated documentation change in usage text
https://bugs.kde.org/show_bug.cgi?id=467868 --- Comment #6 from Michael --- (In reply to Baltasar Sanchez from comment #5) > I think I found a related bug with --getexistingdirectory > > this used to work, I just updated to kdialog 23.04.3 and it no longer works > as it used to I can verify that it doesn't seem to work, but maybe it should have it's own bug report to be tracked as a separate issue? -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 472236] Maximized window state/size not properly restored
https://bugs.kde.org/show_bug.cgi?id=472236 michael changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from michael --- I can fix this easily enough from kdiff3 side. I think ultimately its a bug in Qt's save/restore feature which is supposed preserve fullscreen/maximized state and does on my test machine. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 472718] Merge conflict resolved to empty is saved as newline
https://bugs.kde.org/show_bug.cgi?id=472718 michael changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 472778] New: Relative file URL generating incorrectly
https://bugs.kde.org/show_bug.cgi?id=472778 Bug ID: 472778 Summary: Relative file URL generating incorrectly Classification: Applications Product: tellico Version: 3.5.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ro...@periapsis.org Reporter: agentrebo...@gmail.com Target Milestone: --- SUMMARY After creating a new URL field with relative set to true, any URLs which may be added end up not working when moving the directory to a different location. The link will change and be mostly correct, however it will remove the folder which the Tellico file is contained within from the path which makes it not work. STEPS TO REPRODUCE 1. Create a folder named "Test". 2. Place some kind of file inside of the "Test" folder, such as an image. Name it "Testfile". 3. Open Tellico and create a new custom collection. Save it into the "Test" folder under the name "TestCollection". 4. In this collection, create a URL field named "URL" and set property "relative" to "true". 5. Create a new entry titled "Test", and link the URL field to the "Testfile" file in the same folder. 6. Now that the URL is linking to the file correctly, save and exit Tellico. 7. Exit the "Test" folder and create a new folder within the same location. Title the new folder "MoveTestHere". 8. Move the "Test" folder into the "MoveTestHere" folder and open the Tellico file to view the URL. OBSERVED RESULT The URL which was set to relative is now altered to fit the change in location, but the "Test" folder which the files are contained within will be excluded from the path, and the URL will no longer function due to this. e.g. The URL which once pointed to "file:///home/*user*/Test/Testfile.png" now points to "file:///home/*user*/MoveTestHere/Testfile.png". (Moving just the files without the "Test" folder to "MoveTestHere" doesn't help either as it then will just exclude "MoveTestHere" from the path instead). EXPECTED RESULT The URL which is set to relative should now have been altered to fit the change in location, and should function as previously. e.g. The URL which once pointed to "file:///home/*user*/Test/Testfile.png" should now point to "file:///home/*user*/MoveTestHere/Test/Testfile.png". SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- 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 #10 from Michael Lashkevich --- (In reply to Andrey from comment #9) > No, because we incorporated new platform-agnostic Wayland-capable applet to > replace the old one since then. There is no way to return back. > The only way is a proper fix. I remind again. Maybe somebody else can do it, except you? -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 445050] Feature Request: Also distribute KMyMoney via Flatpak, Flathub
https://bugs.kde.org/show_bug.cgi?id=445050 Michael Carpino changed: What|Removed |Added CC||mfcarp...@gmail.com --- Comment #12 from Michael Carpino --- https://flathub.org/apps/org.kde.kmymoney -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 439364] Dialog "Conflicts Left" is displayed when kdiff3 just started.
https://bugs.kde.org/show_bug.cgi?id=439364 --- Comment #8 from michael --- How are you starting kdiff3? It seems to think you are asking to compare files in auto resolve mode. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 439364] Dialog "Conflicts Left" is displayed when kdiff3 just started.
https://bugs.kde.org/show_bug.cgi?id=439364 michael changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- Ever confirmed|1 |0 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 472510] New: Saved sessions sometimes lose all their info
https://bugs.kde.org/show_bug.cgi?id=472510 Bug ID: 472510 Summary: Saved sessions sometimes lose all their info Classification: Applications Product: kate Version: 23.04.3 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: sessions Assignee: kwrite-bugs-n...@kde.org Reporter: michaelalexsan...@protonmail.com Target Milestone: --- SUMMARY When opening a saved session in Kate, I sometimes come across of what looks like a newly created one. Opened directory and files, button placement, everything reverts to the "default" state. STEPS TO REPRODUCE 1. Open a saved session. 2. See that everything was lost. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 23.04 KDE Plasma Version: N/A KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 472270] Crash when ignoring whitespace and diffing files with trailing whitespace
https://bugs.kde.org/show_bug.cgi?id=472270 --- Comment #1 from michael --- You can also create a MR for this the exit crash has been reported previously and is a different root cause. Going to have a look at your fix. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 439148] GUI is not shown during comparing of folders when Kdiff3 launched from command line.
https://bugs.kde.org/show_bug.cgi?id=439148 --- Comment #8 from michael --- Yes. Playing catch up right now. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 439364] Dialog "Conflicts Left" is displayed when kdiff3 just started.
https://bugs.kde.org/show_bug.cgi?id=439364 michael changed: What|Removed |Added Status|REOPENED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #6 from michael --- Could someone experiencing this please provide the full error text. There are two dialogs with this title. -- You are receiving this mail because: You are watching all bug changes.
[kcharselect] [Bug 472376] KCharSelect Missing entire "Mathematical Alphanumeric Symbols" block
https://bugs.kde.org/show_bug.cgi?id=472376 --- Comment #2 from Michael --- Thank you, I tried searching but I didn't realize the technical reason behind it and couldn't get a match. Looks like it's an old bug, 16 years old. -- You are receiving this mail because: You are watching all bug changes.
[kcharselect] [Bug 472376] New: KCharSelect Missing entire "Mathematical Alphanumeric Symbols" block
https://bugs.kde.org/show_bug.cgi?id=472376 Bug ID: 472376 Summary: KCharSelect Missing entire "Mathematical Alphanumeric Symbols" block Classification: Applications Product: kcharselect Version: 23.04.3 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cf...@kde.org Reporter: k...@callthecomputerdoctor.com Target Milestone: --- SUMMARY KCharSelect is missing an entire grouping/block of symbols called "Mathematical Alphanumeric Symbols". The symbols can be looked up one at a time in its database if you happen to know exactly what you're looking for, but we cannot see the entire block and browse them, like we can for "Supplemental Arrows-A" group, for example. This missing block is defined here: https://www.unicode.org/charts/PDF/U1D400.pdf STEPS TO REPRODUCE 1. In KCharSelect, paste the 풀 symbol into the search bar at the top and ensure that Noto Sans is selected as the font. 2. The character is found and the code point is shown as U+1D480, as it should be. 3. From the unicode.org site, doing a search on this character tells us that it is the "Mathematical Alphanumeric Symbols" range. 4. Attempt to find the "Mathematical Alphanumeric Symbols" block in KCharSelect. 4a. Select "Mathematical Symbols" from the first drop-down list and examine the secondary drop-down list. 4b. Go through all the sub-blocks one at a time, to verify that code point U+1D480 is not there. Even look in the first drop-down's "Symbol" category, it's not there either. EXPECTED RESULT Should be able to find the entire group/block called "Mathematical Alphanumeric Symbols" as shown in https://www.unicode.org/charts/PDF/U1D400.pdf SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[kcharselect] [Bug 451552] kcharselect missing many characters entirely
https://bugs.kde.org/show_bug.cgi?id=451552 --- Comment #5 from Michael --- Not sure why this is marked as resolved, though. Pasting in a character, even if it happens to be a unicode emoji, should still be able to show a match. -- You are receiving this mail because: You are watching all bug changes.
[kcharselect] [Bug 451552] kcharselect missing many characters entirely
https://bugs.kde.org/show_bug.cgi?id=451552 Michael changed: What|Removed |Added CC||kde@callthecomputerdoctor.c ||om --- Comment #4 from Michael --- I can confirm in KCharSelect 23.04.3, typing gear does find the gear, but pasting in the emoji of the gear doesn't find the gear. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 471857] "Do not change color from original HTML mail" also makes plain text mail not adhere to color scheme
https://bugs.kde.org/show_bug.cgi?id=471857 Michael Bromilow changed: What|Removed |Added CC||d...@mail.bromilow.uk -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471642] Severe memory leak in 5.27.5 with Wayland
https://bugs.kde.org/show_bug.cgi?id=471642 --- Comment #1 from Michael Butash --- So this is still happening, and very much related to 3d activity, but otherwise without even still continues to climb steadily either way. It seems without gaming or 3d applications it sinks about 10gb of ram into plasma per day, but running various games or persistent gl/vulkan functions vastly increase this, using my 128gb in plasmashell within two days to need to reset the user session. Using wayland with plasma, I get weird artifacting in transparencies like the title bars of windows always, that show a mouse moving over it over and over - it seems to be collecting "fragments" of things somehow, caching or otherwise using them, and not releasing them. Any sort of dynamic graphics exemplifies this to the point of memory starts climbing the more active it is. Various games opengl or vulkan seem to cause memory use of different levels to grow in plasmashell, but they certainly never reduce along the way. I suspect windows snapshot caching, but not sure how to disable globally just to see if the system behaves. My system and configuration is not particularly unique other than maybe the resolution/displays, I'd like to think I'm not the only one seeing this as prevalent as it is. Combined with things like zoom still not working properly with wayland or a working screen locker, makes it really hard to want to keep with it as the "future" still. I'm trying to stick with wayland, but having to restart my desktop every few days due to a memory leak in kde/wayland is killing me. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 468523] Customizable initial location for Files View
https://bugs.kde.org/show_bug.cgi?id=468523 --- Comment #4 from Michael --- (In reply to ebray187 from comment #3) > What if the default folder follows the System settings -> Applications -> > Locations -> Music path? Should be fine! I assume that: xdg-user-dir MUSIC ...will give the proper path to the music folder on any system. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 468708] Crash if kdiff3 attempts to auto-exit after auto-applying all non-conflicting merges
https://bugs.kde.org/show_bug.cgi?id=468708 --- Comment #21 from michael --- It looks it may something else going wrong with the threads. Doesn't seem to be occur as easily on my setup. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 472082] KMail doesn't load externally referenced images when email is displayed in own window with respect to relevant setting
https://bugs.kde.org/show_bug.cgi?id=472082 Michael changed: What|Removed |Added Summary|KMail doesn't load |KMail doesn't load |externally referenced |externally referenced |images when email is|images when email is |displayed in own window |displayed in own window ||with respect to relevant ||setting -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 472082] New: KMail doesn't load externally referenced images when email is displayed in own window
https://bugs.kde.org/show_bug.cgi?id=472082 Bug ID: 472082 Summary: KMail doesn't load externally referenced images when email is displayed in own window Classification: Applications Product: kmail2 Version: 5.23.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: k...@callthecomputerdoctor.com Target Milestone: --- SUMMARY KMail doesn't respect the "Allow messages to load external references from Internet" setting for emails when displayed in their own window. It respects the setting only in the preview pane. STEPS TO REPRODUCE 1. Go to KMail -> Settings menu -> Configure KMail -> Security tab, -> ensure that "Allow messages to load external references from Internet" is checked 2. Back in KMail's main interface, find an email that has HTML content with pictures. Click on it. In the preview pane, external references appear as they should. 3. Now double-click on the email item to make it appear in its own window. OBSERVED RESULT When the email is in its own window, no external HTML pictures are loaded. Instead a red box appears with this message: "Note: This HTML message may contain external references to images etc. For security/privacy reasons external references are not loaded. If you trust the sender of this message then you can load the external references for this message by clicking here." EXPECTED RESULT Externally referenced HTML pictures should be immediately visible, as they are in the preview pane. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 5.19.0-46-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 472081] New: Elisa stops playing audio track when clicking on a star to rate the track
https://bugs.kde.org/show_bug.cgi?id=472081 Bug ID: 472081 Summary: Elisa stops playing audio track when clicking on a star to rate the track Classification: Applications Product: Elisa Version: 23.04.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: baloo Assignee: matthieu_gall...@yahoo.fr Reporter: k...@callthecomputerdoctor.com Target Milestone: --- SUMMARY Elisa stops playing audio track when rclicking on a star to rate the track, and then starts playing from beginning again. Happens only the first time in a session. STEPS TO REPRODUCE 1. Start Elisa, clear the playlist, and add 3 audio tracks to the playlist. I tested audio tracks with no star metadata added to them. 2. Start playing the first audio track. 3. After several seconds, in the playlist area, click on the empty star icon for the current audio track (the tooltip says "Set track rating"). Five stars appear to select a star rating. 4. Click on the 5th star to rate it 5 stars. OBSERVED RESULT Audio track stops playing, then starts playing from the beginning, and a pop-up message appears in the corner of the screen saying that "Imported x tracks". EXPECTED RESULT Audio track shouldn't suddenly stop playing when giving a star rating, and a pop up message shouldn't appear saying that x tracks were imported. Note that repeating this procedure for subsequent tracks doesn't have the same audio track resetting effect, but the pop up message still appears. Elisa needs to be restarted to induce the undesired effect again again. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 Kernel Version: 5.19.0-46-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 468708] Crash if kdiff3 attempts to auto-exit after auto-applying all non-conflicting merges
https://bugs.kde.org/show_bug.cgi?id=468708 michael changed: What|Removed |Added Latest Commit||e74f887f8a5d47161cedc7421e3 ||8deb1212b49c6 Version Fixed In|1.10.4 |1.10.5 --- Comment #18 from michael --- Finial fixed this in e74f887f8a5d47161cedc7421e38deb1212b49c6. KDiff3 creates short lived helper threads to assist with auto-wrap calculation. These threads previously relied on two raw pointers to long lived objects. This created a chance for a race condition on exit as c++ and qt did automatic cleanup. I don't now why this didn't happen in earlier versions but it was always possible. Theses are now shared pointers which can't be freed until all helper threads are destroyed or compete. 1.10.4 is less likely to trigger it but may still do so. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 472059] New: Pop3 account crashes on Check Mail
https://bugs.kde.org/show_bug.cgi?id=472059 Bug ID: 472059 Summary: Pop3 account crashes on Check Mail Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: POP3 Resource Assignee: kdepim-b...@kde.org Reporter: i...@michaelzeilfelder.de CC: aa...@kde.org, c...@carlschwan.eu Target Milestone: --- Application: akonadi_pop3_resource (5.15.3 (20.08.3)) Qt Version: 5.15.2 Frameworks Version: 5.78.0 Operating System: Linux 5.10.0-23-amd64 x86_64 Windowing system: X11 Distribution: Debian GNU/Linux 11 (bullseye) -- Information about the crash: - What I was doing when the application crashed: Started KMail and directly afterwards clicked "Check Mail" button. I got this crash regularly since Debian 11 (sorry, late report... didn't figure out before how to add the debug symbols). My workaround is that I usually slow down - start KMail - wait a few seconds - and only then click Check Mail. Thought not sure if the crash even does anything that matters, kmail continues to run. Same crash also often happens if I click Check Mail twice in a row. Thought not always - some days (rather seldom) it allows me to click endless without getting this crash. - Further info: Possibly mail database is messed up. It's imported over and over since KDE 2.x times and the amount of times I had to run akonadictl fsck over the years to get rid of other problems (double mails, undeleted mails, etc) is very high. The crash can be reproduced sometimes. -- Backtrace: Application: POP3 Account (akonadi_pop3_resource), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fbeed2b34c0 (LWP 1816))] [KCrash Handler] #6 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:526 #7 0x7fbef26cb28b in memmove (__len=, __src=, __dest=) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:40 #8 QListData::remove (this=this@entry=0x7fff728c6028, i=, i@entry=0) at tools/qlist.cpp:282 #9 0x7fbef26cb5d9 in QListData::erase (this=this@entry=0x7fff728c6028, xi=xi@entry=0x558547bdbca0) at tools/qlist.cpp:347 #10 0x558545bf13fb in QList::erase (it=..., this=0x7fff728c6028) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:567 #11 POP3Resource::saveSeenUIDList (this=0x7fff728c6b50) at ./resources/pop3/pop3resource.cpp:930 #12 0x558545bf3010 in POP3Resource::finish (this=0x7fff728c6b50) at ./resources/pop3/pop3resource.cpp:848 #13 0x7fbef28a65a6 in QtPrivate::QSlotObjectBase::call (a=0x7fff728c6220, r=0x7fff728c6b50, this=0x558547b9c320) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #14 doActivate (sender=0x558547b54fe0, signal_index=6, argv=argv@entry=0x7fff728c6220) at kernel/qobject.cpp:3886 #15 0x7fbef289f900 in QMetaObject::activate (sender=sender@entry=0x558547b54fe0, m=m@entry=0x7fbef3382ce0 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fff728c6220) at kernel/qobject.cpp:3946 #16 0x7fbef332de7c in KJob::result (this=this@entry=0x558547b54fe0, _t1=, _t1@entry=0x558547b54fe0, _t2=...) at ./obj-x86_64-linux-gnu/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:576 #17 0x7fbef332e9a3 in KJob::finishJob (this=0x558547b54fe0, emitResult=) at ./src/lib/jobs/kjob.cpp:93 #18 0x7fbef333037a in KJob::emitResult (this=) at ./src/lib/jobs/kjob.cpp:297 #19 0x558545bfbf3f in SlaveBaseJob::slotSlaveResult (this=0x558547b54fe0, job=0x558547baa8e0) at ./resources/pop3/jobs.cpp:227 #20 0x7fbef28a65a6 in QtPrivate::QSlotObjectBase::call (a=0x7fff728c6390, r=0x558547b54fe0, this=0x558547b9f880) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #21 doActivate (sender=0x558547baa8e0, signal_index=6, argv=argv@entry=0x7fff728c6390) at kernel/qobject.cpp:3886 #22 0x7fbef289f900 in QMetaObject::activate (sender=sender@entry=0x558547baa8e0, m=m@entry=0x7fbef3382ce0 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fff728c6390) at kernel/qobject.cpp:3946 #23 0x7fbef332de7c in KJob::result (this=this@entry=0x558547baa8e0, _t1=, _t1@entry=0x558547baa8e0, _t2=...) at ./obj-x86_64-linux-gnu/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:576 #24 0x7fbef332e9a3 in KJob::finishJob (this=0x558547baa8e0, emitResult=) at ./src/lib/jobs/kjob.cpp:93 #25 0x7fbef28a65a6 in QtPrivate::QSlotObjectBase::call (a=0x7fff728c6470, r=0x558547baa8e0, this=0x558547b5b360) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #26 doActivate (sender=0x558547babb50, signal_index=7, argv=0x7fff728c6470, argv@entry=0x0) at kernel/qobject.cpp:3886 #27 0x7fbef289f900 in QMetaObject::activate (sender=sender@entry=0x558547babb50, m=m@entry=0x7fbef361af20 ,
[Akonadi] [Bug 457233] Please provide oauth2 login for IMAP - not just Gmail
https://bugs.kde.org/show_bug.cgi?id=457233 Michael Tsang changed: What|Removed |Added CC||mikl...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 466241] kdiff3 crashes on invalid symbolic link
https://bugs.kde.org/show_bug.cgi?id=466241 michael changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #7 from michael --- The !m_modificationTime.isNull() assertion no longer exists in kdiff3 source. It proved to be invalid due to the design of QDateTime::isNull(). Current 1.10 yields a conflicting type error in the permissions case but will no longer crash. That removal may not have been part of the same commit. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467574] kwin_screencast: Dropping a screencast frame because the compositor is slow
https://bugs.kde.org/show_bug.cgi?id=467574 Michael Seifert changed: What|Removed |Added CC||m.seifert@digitalernachschu ||b.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471642] New: Severe memory leak in 5.27.5 with Wayland
https://bugs.kde.org/show_bug.cgi?id=471642 Bug ID: 471642 Summary: Severe memory leak in 5.27.5 with Wayland Classification: Plasma Product: plasmashell Version: 5.27.6 Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mich...@butash.net CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 159983 --> https://bugs.kde.org/attachment.cgi?id=159983=edit Memory Leak Graph, running x11, reboot, running wayland plasma SUMMARY After switching back to testing using wayland over x, I noticed my system suddenly using all 128gb of ram and going into swap. Plasmashell is consuming all of the memory, and I have to restart back to sddm. STEPS TO REPRODUCE 1. Log into Plasma Wayland session from x, start desktop 2. Start normal use (browsers, gaming, zoom, libreoffice) OBSERVED RESULT Within 2 days, all 128gb of my ram is consumed of what is left by plasmashell process. Restarting the session is necessary. EXPECTED RESULT I normally operate weeks/months without reboot with x11, and have with wayland on earlier 5.27.1 or so, but since last upgrade(s) and testing with 5.27.5 and .6 now, there is an extreme memory leak directly in plasmashell. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux, 6.3.9 kernel, nvidia 535.54.03, wayland 1.22.0 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: qt5-5.15.10 System uses a large 11520x2160p frame buffer with 3x 4k displays, has caused even x11 issues earlier kde5, but lately not a problem over time with x11 on the 3080rtx gpu, only with wayland. ADDITIONAL INFORMATION With plasma wayland session or x11 (both same), I use NO desktop widgets, only the default taskbar, k menu, systray, and latte-dock with various widgets loaded there. The plasmashell process itself is consuming the memory from htop observation. I had been using wayland for some weeks a few months ago without issue, went back to xorg for a bit after some odd crashes, only this last week trying wayland again to now observe these. I added my desktop to librenms for snmp polling to observe/document the memory use as well, will include this of the past week after using xorg (normal use), and then switching back to wayland observing the drastic leak. I'm willing to provide any requested info, and willing to run with valgrind if possible, not sure the best way to do this and actually use the desktop. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 471494] New: gwenview logs mime type errors on kde-neon, ubuntu, linuxmint, and crashes on arch
https://bugs.kde.org/show_bug.cgi?id=471494
Bug ID: 471494
Summary: gwenview logs mime type errors on kde-neon, ubuntu,
linuxmint, and crashes on arch
Classification: Applications
Product: gwenview
Version: 23.04.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: gwenview-bugs-n...@kde.org
Reporter: michael.hm...@gmail.com
Target Milestone: ---
the first part is logged in Kde Neon and Linuxmint, the second crash, core
dump, happens for now only on Archlinux and plasma 5.27.6, Gwenview is 23.04.2
all packages and systems are up to date, reinstalling gwenview and dependencies
or stating without rc file does not change the behavior
esay to reproduce when opening an image from dolphin preview
I can open Gwenview directly, it shows folder with the tiny image previews,
clicking on one it opens and appear the bigger image previews place holders,
but on first display the large thumb it crashes with the following log entries
Jun 27 05:55:44 hm-abang systemd[1676]: Started Gwenview - KDE Image Viewer.
jun 27 05:55:46 hm-abang gwenview[15953]: kf.i18n.kuit: "Unknown subcue
':whatsthis,' in UI marker in context {@info:whatsthis, %1 the action's text}."
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-aptus-mos"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-arq"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-bay"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-bmq"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-cap"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-cine"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-cs1"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-dc2"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-drf"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-dxo"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-epson-eip"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-epson-erf"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-fff"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-hasselblad-3fr"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-iiq"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-kodak-dcs"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-kodak-kc2"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-mamiya-mef"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-mfw"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-minolta-mdc"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-mng"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-obm"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-ori"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-ptx"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-pxn"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-qtk"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-r3d"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-raw"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-rdc"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-rwl"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-rwz"
jun 27 05:55:46 hm-abang gwenview[15953]: org.kde.kdegraphics.gwenview.lib:
Unresolved
[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 #8 from Michael Lashkevich --- (In reply to Andrey from comment #7) > I do not have capacity for this recently, sorry. That's sad. But in plasma <=5.18? it worked perfectly. Is it possible to return the code to the initial state? -- 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 #6 from Michael Lashkevich --- (In reply to Andrey from comment #3) > Thanks, haven't had a chance to progress further yet, sorry. I remind you again. For me it is very inconvenient to track every time, in which layout state I leave each window. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 471234] Moving between Deltas in the Diff Windows doesn't work if Word Wrap is on
https://bugs.kde.org/show_bug.cgi?id=471234 michael changed: What|Removed |Added Latest Commit|https://invent.kde.org/sdk/ |https://invent.kde.org/sdk/ |kdiff3/-/commit/9b79dc1a4f0 |kdiff3/-/commit/6f383a22943 |7a743e2ec3dc5a760619453ba01 |93d526b7826c611fc7db228987e |41 |ca --- Comment #4 from michael --- Git commit 6f383a2294393d526b7826c611fc7db228987eca by Michael Reeves. Committed on 26/06/2023 at 01:40. Pushed by mreeves into branch 'master'. Partial revert no need for shared_ptr in Diff3LineVector FIXED-IN:1.10.5 M +5-5src/diff.cpp M +2-2src/diff.h M +7-7src/difftextwindow.cpp https://invent.kde.org/sdk/kdiff3/-/commit/6f383a2294393d526b7826c611fc7db228987eca -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 471234] Moving between Deltas in the Diff Windows doesn't work if Word Wrap is on
https://bugs.kde.org/show_bug.cgi?id=471234 michael changed: What|Removed |Added Version Fixed In||1.10.5 Latest Commit||https://invent.kde.org/sdk/ ||kdiff3/-/commit/9b79dc1a4f0 ||7a743e2ec3dc5a760619453ba01 ||41 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from michael --- Git commit 9b79dc1a4f07a743e2ec3dc5a760619453ba0141 by Michael Reeves. Committed on 26/06/2023 at 01:36. Pushed by mreeves into branch '1.10'. Partial revert no need for shared_ptr in Diff3LineVector FIXED-IN:1.10.5 M +5-5src/diff.cpp M +2-2src/diff.h M +7-7src/difftextwindow.cpp https://invent.kde.org/sdk/kdiff3/-/commit/9b79dc1a4f07a743e2ec3dc5a760619453ba0141 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464225] copy/move symbolic link moves link destination instead
https://bugs.kde.org/show_bug.cgi?id=464225 Michael changed: What|Removed |Added CC||kde@callthecomputerdoctor.c ||om --- Comment #6 from Michael --- I can confirm this problem exists on a f2fs filesystem on this setup: Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 471152] Option to display only differences
https://bugs.kde.org/show_bug.cgi?id=471152 michael changed: What|Removed |Added Severity|normal |wishlist Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 450123] Please add ability to crop images after scan
https://bugs.kde.org/show_bug.cgi?id=450123 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471240] Search for camera model EOS 300D does not find all images
https://bugs.kde.org/show_bug.cgi?id=471240 --- Comment #3 from Michael --- Created attachment 159786 --> https://bugs.kde.org/attachment.cgi?id=159786=edit Log file In the join you will find ..."( ImageMetadata.model = ?)", where "?" is replaced by "CANON EOS 300D DIGITAL". So the case sensitivity is relevant. I tested the SQL with "( ImageMetadata.model like ? )" directly in the SQLiteBrowser. For my case this gives the correct results. All EOS 300D images are found. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471240] Search for camera model EOS 300D does not find all images
https://bugs.kde.org/show_bug.cgi?id=471240 --- Comment #2 from Michael --- Hello Maik, yes. I was wondering the same as you. So I tried it several times and I am sure I chose the right option. And not only that. I restarted digikam, I restarted my computer and I recreated the complete database. Always the same. Only "CANON" is found and "Canon" is not. And I checked the database table "ImageMetadata", hope it is the right one. Besides the DebugView, I can offer you to try to rewrite the Canon data entries to match the same notation via "update table" statement. Let me know if you want me to test it with the "update table" statement as well. The DebugView will follow in the next few days. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 471234] Moving between Deltas in the Diff Windows doesn't work if Word Wrap is on
https://bugs.kde.org/show_bug.cgi?id=471234 michael changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from michael --- I believe this should be fixed now. The auto-wrap calculation has been restored to its original behavior. Was related to 469817 in that both stem from that behavior change. The threads used for this were causing issues on exit from auto-merge. The underling cause being the use of two raw pointers that were shared with the main thread. Theses object could be destroyed on exit causing weird stack traces if a helper thread was still running. That mess has now been resolved properly. Keeping this open for now in case there's something else that was overlooked. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471240] New: Search for camera model EOS 300D does not find all images
https://bugs.kde.org/show_bug.cgi?id=471240
Bug ID: 471240
Summary: Search for camera model EOS 300D does not find all
images
Classification: Applications
Product: digikam
Version: 8.0.0
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: Searches-Advanced
Assignee: digikam-bugs-n...@kde.org
Reporter: mas_masterandserv...@outlook.de
Target Milestone: ---
There are thousands of images made by a Canon EOS 300D in my database. But if I
am searching for images taken by "EOS 300D" only 3 images are found.
I am using a German digikam, so I hope my own translations will fit the real
English words.
STEPS TO REPRODUCE
1. Go to search view
2. Click "New Advanced Search"
3. Go to Image Information ("Fotoinformationen")
4. Select the camera model ("Das Modell der Kamera") "EOS 300D"
5. Click "OK"
OBSERVED RESULT
Only 3 images are found
EXPECTED RESULT
There should be 42072 (result of query in SQLiteBrowser on table
"ImageMetadata")
SOFTWARE/OS VERSIONS
Windows: 22H2 Build 22621.1848
(available in About System)
KDE Plasma Version: ---
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
digikam:
- Build date: 12.04.2023 15:33 (target: RelWithDebInfo)
- Revision: 66b84e1ba8f8003994fa398a669e1ccc4224a901
ADDITIONAL INFORMATION
I noticed the following that makes me wonder.
1. The real database entries are
makemodel
Canon Canon EOS 300D DIGITAL
But in the Advanced Search Dialog's drop down box there is "EOS 300D" only.
2. 42069 datasets are:
makemodel
Canon Canon EOS 300D DIGITAL
But 3 datasets are:
make model
CANON CANON EOS 300D DIGITAL
These 3 are exactly the images which are found. It seems that "CANON" and
"Canon" makes the difference.
3. In the database are camera models like "dffdfg" or "erre" and makes like
"gfgfgfgf" like "rg". These appear in the drop down box of the Advanced Search
Dialog. But "Canon EOS 300D DIGITAL" or "CANON EOS 300D DIGITAL" do not appear,
instead "EOS 300D" appears as model and "CANON" and "Canon" as make only.
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 448843] Multiple Cores Not Used
https://bugs.kde.org/show_bug.cgi?id=448843 --- Comment #6 from Michael --- Since version 8.0.0 I am using SQLite. Performance is good and all available and possible cores are used. Michael -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 471172] New: wierd log entries at gwenview start
https://bugs.kde.org/show_bug.cgi?id=471172
Bug ID: 471172
Summary: wierd log entries at gwenview start
Classification: Applications
Product: gwenview
Version: 23.04.2
Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: gwenview-bugs-n...@kde.org
Reporter: michael.hm...@gmail.com
Target Milestone: ---
every single time these entries are showing up:
Jun 17 19:12:32 hm-mint systemd[1424]:
app-org.kde.gwenview-a277c9bc3b3d4c2892535cdbeeff2b57.scope: Consumed 5.988s
CPU time.
Jun 17 19:12:34 hm-mint systemd[1424]: Started Gwenview - KDE Image Viewer.
Jun 17 19:12:35 hm-mint gwenview[20264]: kf.i18n.kuit: "Unknown subcue
':whatsthis,' in UI marker in context {@info:whatsthis, %1 the action's text}."
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-aptus-mos"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-arq"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-bay"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-bmq"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-canon-cr3"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-cap"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-cine"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-cs1"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-dc2"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-drf"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-dxo"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-epson-eip"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-epson-erf"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-fff"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-hasselblad-3fr"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-iiq"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-kodak-dcs"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-kodak-kc2"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-mamiya-mef"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-mfw"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-minolta-mdc"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-mng"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-nikon-nrw"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-obm"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-ori"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-ptx"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-pxn"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-qtk"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-r3d"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-raw"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-rdc"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-rwl"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-rwz"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-samsung-srw"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved mime type "image/x-sti"
Jun 17 19:12:35 hm-mint gwenview[20264]: org.kde.kdegraphics.gwenview.lib:
Unresolved raw mime type "image/x-nikon-nrw"
Jun
[kdiff3] [Bug 442582] When merging files from`git mergetool`, output is scrolled to top instead of first conflict
https://bugs.kde.org/show_bug.cgi?id=442582 michael changed: What|Removed |Added Latest Commit|https://invent.kde.org/sdk/ |https://invent.kde.org/sdk/ |kdiff3/-/commit/d6d661f74a9 |kdiff3/-/commit/32d4d0321a9 |6c734daa74d3f4a36534ca35ce8 |5be4318312d5ebb567137fff5f4 |3a |8d --- Comment #10 from michael --- Git commit 32d4d0321a95be4318312d5ebb567137fff5f48d by Michael Reeves. Committed on 13/06/2023 at 19:11. Pushed by mreeves into branch 'master'. Turn on updates before calling MergeResultWindow::slotGoNextUnsolvedConflict FIXED-IN:1.10.5 M +3-2src/pdiff.cpp https://invent.kde.org/sdk/kdiff3/-/commit/32d4d0321a95be4318312d5ebb567137fff5f48d -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 442582] When merging files from`git mergetool`, output is scrolled to top instead of first conflict
https://bugs.kde.org/show_bug.cgi?id=442582 michael changed: What|Removed |Added Latest Commit||https://invent.kde.org/sdk/ ||kdiff3/-/commit/d6d661f74a9 ||6c734daa74d3f4a36534ca35ce8 ||3a Resolution|--- |FIXED Version Fixed In||1.10.5 Status|ASSIGNED|RESOLVED --- Comment #9 from michael --- Git commit d6d661f74a96c734daa74d3f4a36534ca35ce83a by Michael Reeves. Committed on 13/06/2023 at 19:08. Pushed by mreeves into branch '1.10'. Turn on updates before calling MergeResultWindow::slotGoNextUnsolvedConflict FIXED-IN:1.10.5 M +3-2src/pdiff.cpp https://invent.kde.org/sdk/kdiff3/-/commit/d6d661f74a96c734daa74d3f4a36534ca35ce83a -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 439364] Dialog "Conflicts Left" is displayed when kdiff3 just started.
https://bugs.kde.org/show_bug.cgi?id=439364 michael changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 470988] New: Back up numbers and location
https://bugs.kde.org/show_bug.cgi?id=470988 Bug ID: 470988 Summary: Back up numbers and location Classification: Applications Product: kmymoney Version: 5.1.2 Platform: Ubuntu OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: file Assignee: kmymoney-de...@kde.org Reporter: imgi...@gmail.com Target Milestone: --- First off, I really like kmymoney. Thanks for all the hard work developing it. Great job. Just a little wish list item(s). For the autosave/backups. It would be nice to only save one backup per session (so 10 backups would be the last 10 sessions, not just all the ones every 10 minutes) and it would also be great to specify where the backups are stored. Again, both of those are seriously no big deal. Thanks again. --Michael -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 442582] When merging files from`git mergetool`, output is scrolled to top instead of first conflict
https://bugs.kde.org/show_bug.cgi?id=442582 michael changed: What|Removed |Added Status|REOPENED|ASSIGNED --- Comment #8 from michael --- Thanks I'll have a look at this. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 470299] Silent install no longer works
https://bugs.kde.org/show_bug.cgi?id=470299 --- Comment #9 from michael --- Should be fixed now https://download.kde.org/stable/kdiff3/kdiff3-1.10.4-windows-x86_64.exe.mirrorlist. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 439364] Dialog "Conflicts Left" is displayed when kdiff3 just started.
https://bugs.kde.org/show_bug.cgi?id=439364 michael changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #4 from michael --- Looks like this should now be resolved in 1.10.4 by changes for an unrelated issue handling auto-merge. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 462693] select all and copy doesn't work
https://bugs.kde.org/show_bug.cgi?id=462693 michael changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from michael --- Observed that focus can be on the file name field while still having the selection visible in the diff window. Looks like the source of this issue. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 470299] Silent install no longer works
https://bugs.kde.org/show_bug.cgi?id=470299 --- Comment #8 from michael --- That would be an artifact of it having been built from 1.10 tip rather than a release tar ball. Going to go ahead and rebuild to 1.10.4 installer now that silent install is working. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 470299] Silent install no longer works
https://bugs.kde.org/show_bug.cgi?id=470299 michael changed: What|Removed |Added Status|REOPENED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 470299] Silent install no longer works
https://bugs.kde.org/show_bug.cgi?id=470299 --- Comment #6 from michael --- Looks like I uploaded the wrong binary. Trying again. Going to keep this open until the fix can be confirmed. sha256: 89e0c4ffdffa7ec85ce8845f5909488df0998d80a8ca6cf77b1b1417993ca98e kdiff3-1.10.4-slientfixed-windows-x86_64.exe sha1: 1cb49f9c21e934a6f5c23a9f906137fb51d28862 kdiff3-1.10.4-slientfixed-windows-x86_64.exe The checksums are for the corrected installer. This will be replacing an existing file by the same name on the server. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 465582] Kde Connect doen't reconnect
https://bugs.kde.org/show_bug.cgi?id=465582
--- Comment #4 from Michael ---
well, seems nobody has interest in solving this, I can understand that there
are not much people using it, but since kdeconnect is there it should work,
agree?
in fact, it doesn't seem to have a reconnect routine and that should be
corrected
a cmd line like "/usr/bin/kdeconnect-cli -n Moto E7 --refresh" does it, but for
some reason I can not automate it, I believe that is so because udev runs as
root and the command needs to be run as the user
inside the script to be run from udev_rule (as root) this command should, but
is not working
su hm -c '/usr/bin/kdeconnect-cli "-n Moto E7 --refresh"'
the options are interpreted as two, or as a diretcory depends on how I set the
quotes
that's in my udev_rules file
KERNEL=="rndis_host", ACTION=="add", ENV{ID_SERIAL}=="0e8d:2005",
RUN+="/usr/sbin/kdeconnect.sh"
the kernel event in my case:
rndis_host 1-2:1.0 usb0: register 'rndis_host' at usb-:00:12.2-2, RNDIS
device, 5a:c0:6b:31:9a:5c
rndis_host 1-2:1.0 enx5ac06b319a5c: renamed from usb0
the kdeconnect reconnect should run after the renaming of usb0, the device ID
"enx*' is random
if somebody here has a better idea or knows how to make it work from udev, it
would be nice
thanks
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 470441] New: After folding code, kate/kwrite no longer scrolls by real lines instead of view lines
https://bugs.kde.org/show_bug.cgi?id=470441 Bug ID: 470441 Summary: After folding code, kate/kwrite no longer scrolls by real lines instead of view lines Classification: Applications Product: kate Version: 23.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: folding Assignee: kwrite-bugs-n...@kde.org Reporter: nortex...@gmail.com Target Milestone: --- Kate now (as of around 5 years ago) scrolls per view line rather than real line. However, if you fold some code, it goes back to its old behavior of scrolling per real line. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 470299] Silent install no longer works
https://bugs.kde.org/show_bug.cgi?id=470299 michael changed: What|Removed |Added Status|ASSIGNED|RESOLVED Version Fixed In||1.10.5 Resolution|--- |FIXED --- Comment #3 from michael --- Its up at: https://download.kde.org/stable/kdiff3/kdiff3-1.10.4-slientfixed-windows-x86_64.exe.mirrorlist -- You are receiving this mail because: You are watching all bug changes.
