[kdenlive] [Bug 486310] Add Clip or Folder dialog window too small
https://bugs.kde.org/show_bug.cgi?id=486310 --- Comment #4 from Chris K. --- Sorry, I wanted to write "...think about it..." (not "...thing about it..."). Best regards Chris -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 486310] Add Clip or Folder dialog window too small
https://bugs.kde.org/show_bug.cgi?id=486310 Chris K. changed: What|Removed |Added CC||cplove2...@vivaldi.net --- Comment #3 from Chris K. --- Similar problem for circa one week » after Linux Manjaro big-update to Plasma 6. Kdenlive seems to work fine (as far as I can tell), but the saving of FX-stacks opens up a window which now (in Plasma 6) is a) way to small » i have to resize it everytime (for years the size was perfect, I didn't even thing about it) b) the text-focus does not change automatically "into" the then opened "save as new FX-stack" window (I have to click the field where the name of the new fx-stack goes) Thank you, best regards (from Germany) Chris -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 480928] Always print in A4
https://bugs.kde.org/show_bug.cgi?id=480928 Chris changed: What|Removed |Added CC||cjd...@brokensolstice.com --- Comment #1 from Chris --- Same problem. Set to en_us everywhere. Set in KDE, set letter in cups, on the printer and every possible location. KDE apps always default to A4. GTK apps print in Letter just fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481736] On X11, Notifications pop up in the middle of the screen after being away from pc for a while
https://bugs.kde.org/show_bug.cgi?id=481736 Chris Vanden Berghe changed: What|Removed |Added CC||ch...@vandenberghe.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483137] Screencast plugin fails if PipeWire is started after KWin
https://bugs.kde.org/show_bug.cgi?id=483137 --- Comment #7 from Chris Pfuhl --- i'm running the same patch according to diff (just with slightly different "index ..." lines which hopefully aren't that relevant to applying) For what it's worth what also worked for me without a patch at least for gentoo was to login as your user account in a shell and run "dbus-run-session gentoo-pipewire-launcher" and then start your display manager and login with the same user. not very pretty but i guess this should also work for other distributions with the correct pipewire launch command. i also wanted to try putting a pipewire launch script in ~/.config/plasma-workspace/env but i'm not very hopeful that this runs early enough. In the meantime i also found a somewhat experimental and pretty complex looking guide in the gentoo wiki to run user services with openrc: https://wiki.gentoo.org/wiki/OpenRC/User_services maybe at some point i'll get around to trying this. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 480235] Persistence in the remote desktop portal does not work across reboots
https://bugs.kde.org/show_bug.cgi?id=480235 chris changed: What|Removed |Added CC||kdebug_vo...@vllmr.eu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484417] Floating panel issue with icons at panel
https://bugs.kde.org/show_bug.cgi?id=484417 Chris Philip Fotiadis <8norc...@cpfotiadis.addy.io> changed: What|Removed |Added CC||8norc...@cpfotiadis.addy.io --- Comment #2 from Chris Philip Fotiadis <8norc...@cpfotiadis.addy.io> --- I have the same problem. If I minimize and maximize from the app icons that are pinned to the panel, no extra line appears. However, if I click on peek at desktop, additional lines appear as mentioned by the previous ones. Distro: Fedora Linux 40 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 GPU : Radeon RX 6600 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 484213] New: Crashes when loading
https://bugs.kde.org/show_bug.cgi?id=484213 Bug ID: 484213 Summary: Crashes when loading Classification: Applications Product: Discover Version: 6.0.2 Platform: Neon OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: chest...@gmail.com CC: aleix...@kde.org 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. Start Discover 2. Wait for it to load 3. OBSERVED RESULT Crashes everytime while loading EXPECTED RESULT for it to load and allow me to install programs SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.02 (available in About System) KDE Plasma Version: 6.02 KDE Frameworks Version: 6.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 484053] New: Baloo crashing randomly and frequently
https://bugs.kde.org/show_bug.cgi?id=484053 Bug ID: 484053 Summary: Baloo crashing randomly and frequently Classification: Frameworks and Libraries Product: frameworks-baloo Version: 5.114.0 Platform: Other OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: cjd...@brokensolstice.com Target Milestone: --- Application: baloo_file_extractor (5.114.0) Qt Version: 5.15.12 Frameworks Version: 5.114.0 Operating System: Linux 6.5.0-10027-tuxedo x86_64 Windowing System: X11 Distribution: TUXEDO OS 2 DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: This was happening all the time with my KDE neon install, numerous times a day. I switched from Neon to Tuxedo the other day, a brand-new install... same thing is still happening. It doesn't appear to correspond to anything I was doing. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=137867053623616) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=137867053623616) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=137867053623616, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7d63ade42476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7d63ade287f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7d63aeb7d418 in ?? () from /lib/x86_64-linux-gnu/liblmdb.so.0 #10 0x7d63aeb71c7a in ?? () from /lib/x86_64-linux-gnu/liblmdb.so.0 #11 0x7d63aeb721b0 in ?? () from /lib/x86_64-linux-gnu/liblmdb.so.0 #12 0x7d63aeb738c1 in ?? () from /lib/x86_64-linux-gnu/liblmdb.so.0 #13 0x7d63aeb7786d in mdb_cursor_del () from /lib/x86_64-linux-gnu/liblmdb.so.0 #14 0x7d63aeb790cb in ?? () from /lib/x86_64-linux-gnu/liblmdb.so.0 #15 0x7d63af6158d7 in Baloo::DocumentIdDB::del(unsigned long long) () from /lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #16 0x7d63af622e9e in Baloo::Transaction::removePhaseOne(unsigned long long) () from /lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #17 0x5bb09f5cfa03 in ?? () #18 0x5bb09f5d1196 in ?? () #19 0x7d63ae8f8ed6 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7d63ae8ea77f in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7d63ae8bd30a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7d63ae915b2b in QTimerInfoList::activateTimers() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7d63ae91642c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7d63ad5c7d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7d63ad61d258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7d63ad5c53e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7d63ae9167f8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7d63ae8bbc2b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7d63ae8c41d4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x5bb09f5c6f83 in ?? () #31 0x7d63ade29d90 in __libc_start_call_main (main=main@entry=0x5bb09f5c62f0, argc=argc@entry=1, argv=argv@entry=0x7ffcb67e14e8) at ../sysdeps/nptl/libc_start_call_main.h:58 #32 0x7d63ade29e40 in __libc_start_main_impl (main=0x5bb09f5c62f0, argc=1, argv=0x7ffcb67e14e8, init=, fini=, rtld_fini=, stack_end=0x7ffcb67e14d8) at ../csu/libc-start.c:392 #33 0x5bb09f5c70c5 in ?? () [Inferior 1 (process 7914) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483011] Floating Panels don't dodge with multiple windows
https://bugs.kde.org/show_bug.cgi?id=483011 --- Comment #2 from Chris --- (In reply to PapierFliegr from comment #1) My panels are set to translucent, and I'm not using tiling. If I understand you right, you say padding incorrectly makes panels think they're being touched when they're not? With my panel set to dodge windows, if it thought it was being touched, I'd expect it to be stuck 'hidden', but instead it's stuck "visible", and is visible on top of whatever window is there, whether the windows is maximized, floating, snapped to one side or corner of my screen, etc. Regardless, how does one set a padding amount? I don't see that in my panel settings, and searching online for it I'm not finding anything? I could at least play around with that setting and find if it helps. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466607] Bug re-introduced as of today's updates
https://bugs.kde.org/show_bug.cgi?id=466607 --- Comment #8 from Chris --- re-introduced again, as of today's updates. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 483428] New: 6.00 to 6.02 upgrade seemed to kill touchscreen on surface pro 7
https://bugs.kde.org/show_bug.cgi?id=483428 Bug ID: 483428 Summary: 6.00 to 6.02 upgrade seemed to kill touchscreen on surface pro 7 Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: chrismarine...@live.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY installed KDE Plasma 6 on Neon, installed surface kernel, https://github.com/linux-surface/linux-surface ... was working extremely well, after some restarts it did kill the surface kernel a couple of times and so had to re-install using steps in link above however, after updates the system to 6.02... the surface pro 7 touch screen does not work anymore.. *** 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. install surface pro 7 kernel via https://github.com/linux-surface/linux-surface on KDE Plasma 6.0 Neon 2. upgrade to 6.02 and re-install surface kernel... 3. touch screen no work! OBSERVED RESULT touch screen has no response for any touch, 2 finger, swipe, 4 fingers.. etc. EXPECTED RESULT expected it to work.. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.0 -> 6.02 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: Qt 6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 457233] Please provide oauth2 login for IMAP - not just Gmail
https://bugs.kde.org/show_bug.cgi?id=457233 --- Comment #12 from Chris --- This bug has 3 duplicates, all of which have importance "NOR normal": 444301 455113 462042. I think it should be fair that the present issue has the same importance. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 476527] Can't add EWS account with OAuth2 authentication, "OK" button stays greyed out until I enter random data for username and password
https://bugs.kde.org/show_bug.cgi?id=476527 Chris changed: What|Removed |Added CC||inkbottle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 409183] Using Password based authentication when Oauth2 is selected
https://bugs.kde.org/show_bug.cgi?id=409183 Chris changed: What|Removed |Added CC||inkbottle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483137] Screencast plugin fails if PipeWire is started after KWin
https://bugs.kde.org/show_bug.cgi?id=483137 Chris Pfuhl changed: What|Removed |Added CC||bugs+...@pfuhl.sh --- Comment #2 from Chris Pfuhl --- Created attachment 166969 --> https://bugs.kde.org/attachment.cgi?id=166969=edit revert kwin commit 37d2a7914329c65361eedfd995f25bd6867b68bc to fix screensharing on Gentoo Linux thank you very much for finding that patch. i can confirm reverting the patch makes screensharing work for me on Gentoo Linux. Since updating to Plasma 6.0.0 i had the same behavior, the display selection menu came up but when pressed any combination received "Failed to connect PipeWire context". With the attached patch built into the package "kde-plasma/kwin-6.0.1-r2" from the main gentoo tree screensharing seems to work flawlessly so far after a restart of the display server. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483011] Floating Panels don't dodge with multiple windows
https://bugs.kde.org/show_bug.cgi?id=483011 Chris changed: What|Removed |Added CC||junasai...@aol.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483011] New: Floating Panels don't dodge with multiple windows
https://bugs.kde.org/show_bug.cgi?id=483011 Bug ID: 483011 Summary: Floating Panels don't dodge with multiple windows Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: junasai...@aol.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 166811 --> https://bugs.kde.org/attachment.cgi?id=166811=edit Display arrangement SUMMARY *** I run EndeavourOS, and just updated to KDE6, and am trying to use the floating panels, set to "dodge windows". I have three monitors, two horizontal stacked on top of each other, and one vertical one to their left. This issue occurs on all displays. If i place a panel on the side of a screen that's a shared edge with another monitor, (such as between the top and bottom horizontal screens), dodging doesn't work. If i move the panel to an "outside" edge of any of the three displays, dodging works just fine) Per screenshot of my displays for reference: Left and bottom of Sceptre display work fine. Bottom and right of Acer display work fine. Top and right of Gigabyte display work fine. Any of the 'inside' or 'shared' edges between the multiple monitors, the panels won't dodge at all. I can try to test anything else or provide other information that's applicable. *** STEPS TO REPRODUCE 1. Use EndeavourOS (or just Arch?) and KDE 6.0.1 2. Have multiple monitors 3. Make a "floating", "dodge windows" panel on any edge of a monitor that's not an "edge", but where my desktop extends to the next monitor. 4. The Panel will not dodge windows and hide itself, the window goes below it instead. OBSERVED RESULT The Panel will not dodge windows and hide itself, the window goes below it instead. EXPECTED RESULT The panel dodges the window, and hides itself. SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Graphics Platform: Wayland GPU: AMD Radeon RX 6800XT -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482503] New: Plasma crashed when I clicked the X on a notification
https://bugs.kde.org/show_bug.cgi?id=482503 Bug ID: 482503 Summary: Plasma crashed when I clicked the X on a notification Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ch...@lewis.ca CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-18-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: I came back to my laptop to find an odd instance of a sticky note displayed on my desktop. There were no controls on the small window and I tried several ways to make it go awaym right-click on it, esc. Eventually I clicked a button at the bottom, but I do not remember what it said. I could have been save or ok, but I am not certain. The window went away and a notification popped up - this is how I know it was a sticky note. I clicked the X on the notification and the desktop crased, but retarted. I was then prompted to submit the bug report. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 1082 (plasmashell) UID: 1000 (chris) GID: 1000 (chris) Signal: 11 (SEGV) Timestamp: Tue 2024-03-05 18:45:02 EST (1min 26s 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 (chris) Boot ID: b082e128c0624c85b6738a91f5d838ad Machine ID: 14b269dd1e0746ffab19f2947e49b6a3 Hostname: trantor Storage: /var/lib/systemd/coredump/core.plasmashell.1000.b082e128c0624c85b6738a91f5d838ad.1082.170968230200.zst (present) Size on Disk: 33.0M Message: Process 1082 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.22-1~deb12u1.amd64 Module libudev.so.1 from deb systemd-252.22-1~deb12u1.amd64 Stack trace of thread 1082: #0 0x7f6297eaed14 pthread_sigmask (libc.so.6 + 0x8fd14) #1 0x7f6297e5b239 sigprocmask (libc.so.6 + 0x3c239) #2 0x7f629a5a4e9b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4e9b) #3 0x7f629a5a5b3e _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b3e) #4 0x7f6297e5b050 n/a (libc.so.6 + 0x3c050) #5 0x7f6299a77c86 _ZN5QtQml18qmlExecuteDeferredEP7QObject (libQt5Qml.so.5 + 0x277c86) #6 0x7f6299f49059 _ZN16QQuickTransition7prepareER5QListI17QQuickStateActionERS0_I12QQmlPropertyEP23QQuickTransitionManagerP7QObject (libQt5Quick.so.5 + 0x149059) #7 0x7f6299f3e997 _ZN23QQuickTransitionManager10transitionERK5QListI17QQuickStateActionEP16QQuickTransitionP7QObject (libQt5Quick.so.5 + 0x13e997) #8 0x7f62982dd50d _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2dd50d) #9 0x7f6299162fae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fae) #10 0x7f62982b16f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8) #11 0x7f6298308c31 _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x308c31) #12 0x7f62983094c4 n/a (libQt5Core.so.5 + 0x3094c4) #13 0x7f6296db87a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9) #14 0x7f6296db8a38 n/a (libglib-2.0.so.0 + 0x54a38) #15 0x7f6296db8acc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #16 0x7f6298309836 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x309836) #17 0x7f62982b017b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b017b) #18 0x7f62982b82d6 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2b82d6) #19 0x5589b0b44dc3 n/a (plasmashell + 0x26dc3) #20 0x7f6297e4624a n/a (libc.so.6 + 0x2724a) #21 0x7f6297e46305 __libc_start_main (libc.so.6 + 0x27305) #22 0x5589b0b44ee1 n/a (plasmashell + 0x26ee1) Stack trace of thread 1091: #0 0x7f6297ea4e96 n/a (libc.so.6 + 0x85e96
[neon] [Bug 480856] Fresh Neon install can't boot if encryption is used (20240201-0717 iso)
https://bugs.kde.org/show_bug.cgi?id=480856 Chris Moore changed: What|Removed |Added CC||ch...@mooreonline.org -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 481938] Unable to leave session via Desktop menu on Plasma 6.0.0
https://bugs.kde.org/show_bug.cgi?id=481938 Chris changed: What|Removed |Added CC||cjd...@brokensolstice.com --- Comment #27 from Chris --- (In reply to Sean from comment #26) > (In reply to Rich Johnson from comment #5) > > I've created 2 files in /usr/share/dbus-1/services to make my Restart, > > Shutdown & Logout work again: > > > > $ cat org.kde.Shutdown.service > > [D-BUS Service] > > Name=org.kde.Shutdown > > Exec=/usr/bin/plasma-shutdown > > > > $ cat org.kde.LogoutPrompt.service > > [D-BUS Service] > > Name=org.kde.LogoutPrompt > > Exec=/usr/lib/x86_64-linux-gnu/libexec/ksmserver-logout-greeter > > > Thanks Rich Johnson, this works perfectly (for the other noobs out there I > created the file in Kate and just saved to the correct directly specified by > Rich) Thank you for that. Exactly what I needed. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 481831] New: When Memory Usage is Set Above Low, The Page Image Might Not Refresh Correctly
https://bugs.kde.org/show_bug.cgi?id=481831 Bug ID: 481831 Summary: When Memory Usage is Set Above Low, The Page Image Might Not Refresh Correctly Classification: Applications Product: okular Version: 23.08.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: cbmiller2...@live.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. Set Memory Usage to Anything Above "Low" 2. Turn off continuous scroll 3. Change pages (sometimes it is ok for a while if just changing 1-2 pages, scrolling rapidly through pages back and forth will immediately cause the issue) 4. Page will eventually get stuck displaying a single page, although the page numbers will change indicating that the image should be changing. 5. Fullscreening or un-fullscreening the application unsticks the image. 6. Set memory usage to "Low", the problem goes away and pages can be scrolled through at any speed and still update the page image correctly. OBSERVED RESULT Page image does not update, see video: https://youtu.be/lBQRTCoiEaE EXPECTED RESULT Page image updates to reflect the current page no matter the speed of scrolling, view settings, etc SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 39 (Gnome+Wayland) (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Linux 6.7.5-200.fc39.x86_64 x86_64 PDF file that is being browsed is on a fuse filesystem using google-drive-ocamlfuse -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468830] Metadata is lost after write operation when the size of XMP JPEG segment is larger than 65535 bytes when using Exiftool backend
https://bugs.kde.org/show_bug.cgi?id=468830 --- Comment #19 from Chris --- Bug 481268 seems to be related or maybe the exact same: https://bugs.kde.org/show_bug.cgi?id=481268 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480819] Window Glitching When Snapping to Left or Right in Wayland
https://bugs.kde.org/show_bug.cgi?id=480819 --- Comment #7 from Chris Lewis --- (In reply to Nate Graham from comment #6) > And since then, has it continued to work as expected? Or did it break again? It will work temporarily and then eventually the issue will occur again either with the same or different window. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466607] Bug re-introduced as of today's updates
https://bugs.kde.org/show_bug.cgi?id=466607 --- Comment #7 from Chris --- Updated on 2/12/24... bug seems to have been corrected. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 480958] Configure/Environment does not work - cache/proxy etc stay on C:/users/{user}/AppData/Local/kdenlive/cache
https://bugs.kde.org/show_bug.cgi?id=480958 --- Comment #4 from Chris C --- That workaround seems to work for me too. Thanks. I just have to remember to go through those steps before starting a project... Regards Chris // /Dr Chris P Chaloner/ //On 08/02/2024 17:17, emohr wrote: https://bugs.kde.org/show_bug.cgi?id=480958 emohr [1] changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #3 from emohr [1] --- I can confirm the issue following your steps. I tested it with the latest master and either pointing a new project to a different drive/folder or create first a project and choose “parent folder” lead to the same error message. I don’t get any hint from DebugView what happen. The only way to get it working is: Settings -> Configure Kdenlive -> Project Defaults -> Custom Project folder -> point to another drive and folder. Then start a new project and all is working and the data flow to this new defined drive and folder. 1. mailto:fritzib...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480819] Window Glitching When Snapping to Left or Right in Wayland
https://bugs.kde.org/show_bug.cgi?id=480819 --- Comment #5 from Chris Lewis --- Yes, it started working again after I did Win + Up -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 480958] Configure/Environment does not work - cache/proxy etc stay on C:/users/{user}/AppData/Local/kdenlive/cache
https://bugs.kde.org/show_bug.cgi?id=480958 --- Comment #2 from Chris C --- Thanks for the quick reply. I've upgraded to 23.08.4, but the error is still there. I have full rights to W: and everything in it - in fact, as working space all users have full access to it. In any case, I have Admin rights too. When i switch the Project Folder to Parent Folder it creates a folder cachefiles in the target folder, which also has a folder proxy within it. Both are marked Read-Only and the proxy folder is empty. I tried changing the properties to full-control and unticking the read-only; when I repeat the attempt to change the project folder it fails again and resets them both to read-only. On one occasion I got an "Error renaming file" message - could it be that the original code is Linux-based and the "rename" command isn't becoming a "copy" in Windows? I've tried Custom as well - same result - if I select the parent folder of the project file explicitly it creates a proxy folder in that folder at the same level as cachefiles- still empty and read-only. Thanks for your efforts Chris p.s. while Googling the issue, I did come across someone else having this problem https://www.reddit.com/r/kdenlive/comments/11j6vtk/error_moving_project_folder_cache_folder_on/ /====/ /Dr Chris P Chaloner/ / / On 07/02/2024 16:02, emohr wrote: https://bugs.kde.org/show_bug.cgi?id=480958 emohr [1] changed: What|Removed |Added CC|| fritzib...@gmx.net [1] --- Comment #1 from emohr [1] --- Please try with version 23.08.4. I tested with this version and it works. Make sure you have access rights to the folder you want to save to. 1. mailto:fritzib...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480819] Window Glitching When Snapping to Left or Right in Wayland
https://bugs.kde.org/show_bug.cgi?id=480819 --- Comment #3 from Chris Lewis --- I turned wayland back on to test... when it happened again, I tried Win + Left Arrow or Right Arrow it was non-responsive. But when I Did Win + Up it started working again. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 480958] New: Configure/Environment does not work - cache/proxy etc stay on C:/users/{user}/AppData/Local/kdenlive/cache
https://bugs.kde.org/show_bug.cgi?id=480958
Bug ID: 480958
Summary: Configure/Environment does not work - cache/proxy etc
stay on C:/users/{user}/AppData/Local/kdenlive/cache
Classification: Applications
Product: kdenlive
Version: 23.04.3
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: major
Priority: NOR
Component: User Interface
Assignee: j...@kdenlive.org
Reporter: chrischalo...@gmail.com
Target Milestone: ---
Created attachment 165617
--> https://bugs.kde.org/attachment.cgi?id=165617=edit
screenshot of error popup box
SUMMARY
Cannot change Project Folder to "Parent Folder of the project file", or
"Custom" . When it attempts to move the folder contents, it fails with an
"error moving..." It seems I cannot have the project folder anywhere but
C:/Users/Chris Chaloner/AppData/Loca/kdenlive/cache - and I need it on a
different disk. I have tried Settings-Configure Kdenlive and also
Project-Project Settings- Environment
***
STEPS TO REPRODUCE
1. Create a project on W: (or any disk other than C:, where kdenlive is
installed"
2. Project tab - Project Settings and click "parent folder of the project file"
- click "OK"
3. Warning box pops up - click "Continue"
4. (same thing happens with "Custom:"
OBSERVED RESULT
Error moving project folder
EXPECTED RESULT
temporary files moved from C: to the project folder.
SOFTWARE/OS VERSIONS
Windows: 10
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 480819] Window Glitching When Snapping to Left or Right in Wayland
https://bugs.kde.org/show_bug.cgi?id=480819 --- Comment #1 from Chris Lewis --- There's another user in my post here that's experiencing the same thing in Fedora: https://discuss.kde.org/t/window-glitching-when-snapping-to-left-or-right-in-wayland/10107 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480819] Window Glitching When Snapping to Left or Right in Wayland
https://bugs.kde.org/show_bug.cgi?id=480819 Chris Lewis changed: What|Removed |Added Version|unspecified |5.27.10 CC||k...@lew1s.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480819] New: Window Glitching When Snapping to Left or Right in Wayland
https://bugs.kde.org/show_bug.cgi?id=480819 Bug ID: 480819 Summary: Window Glitching When Snapping to Left or Right in Wayland Classification: Plasma Product: kwin Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: k...@lew1s.com Target Milestone: --- SUMMARY I've included a video of the issue because it's easier to show than describe: https://mega.nz/file/DDZVwR7Q#YTJqguszTzMMvxyGg6d75ynU9TEgnnB5S3f36a9QdAY The issue is that occasionally when snapping windows to the left or right of the screen, there will be a visual glitch and cause all sorts of unexpected results. It tends to only happen with web browsers, and more frequently with Progressive Web Apps, as you can see with Gmail in my example video. The PWA I was demonstrating uses Chromium, but I’ve also had this occur with Chrome and Brave. The Appearance settings in the browsers are set to “classic”, but it happens with GTK and QT as well. I’ve set all themes back to default Breeze default to ensure it wasn’t a theme issue. I’ve only been able to reproduce this issue in Wayland. When running X11, it works just fine. STEPS TO REPRODUCE 1. Open PWA 2. Snap to either left or right 3. (I can't always reproduce the issue on demand, but it does happen very frequently) OBSERVED RESULT Visual distortion after window snap EXPECTED RESULT Clean snap to either left or right side of screen SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 kwin 5.27.10-2 wayland 1.22.0-1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466607] Bug re-introduced as of today's updates
https://bugs.kde.org/show_bug.cgi?id=466607 --- Comment #6 from Chris --- Updated system on 1/28/24... this bug was re-introduced. Had to restore from previous backup and hold off on applying update. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479583] in intel gpu system, default software cursor disappears on screen after kwin commit b214251f81cbacacf3ef483081a7cef15343fa7f
https://bugs.kde.org/show_bug.cgi?id=479583 Chris Sutcliff changed: What|Removed |Added CC|ch...@sutcliff.me | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468830] Metadata is lost after write operation when the size of XMP JPEG segment is larger than 65535 bytes when using Exiftool backend
https://bugs.kde.org/show_bug.cgi?id=468830 Chris changed: What|Removed |Added CC||chrisc.gigam...@gmail.com --- Comment #18 from Chris --- I tried today with digiKam-8.3.0-20240120T105916-Win64.exe Metadata is no longer deleted, but keywords added (tags from the tags tree) are not longer written to the file. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479764] Cursor is invisible on portrait monitors
https://bugs.kde.org/show_bug.cgi?id=479764 --- Comment #7 from Chris Sutcliff --- Thank you for the fix, I can confirm it is working for me too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479764] Cursor is invisible on portrait monitors
https://bugs.kde.org/show_bug.cgi?id=479764 Chris Sutcliff changed: What|Removed |Added CC||ch...@sutcliff.me -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479764] New: Cursor is invisible on portrait monitors
https://bugs.kde.org/show_bug.cgi?id=479764 Bug ID: 479764 Summary: Cursor is invisible on portrait monitors Classification: Plasma Product: kwin Version: 5.92.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: ch...@sutcliff.me Target Milestone: --- SUMMARY I did originally post this in https://bugs.kde.org/show_bug.cgi?id=479583 but I think it's different enough to be it's own bug, especially as someone pointed out that bug had been marked resolved so perhaps wouldn't get much attention. Using a patched kwin with the fix for 479583 added, this worked for landscape however the cursor is still invisible for portrait monitors. STEPS TO REPRODUCE 1. Be affected by 479586? 2. Use a version of kwin with the fix from 479586 applied 3. Set a screen to portrait orientation (either one) OBSERVED RESULT Cursor is invisible on portrait screen (if you have multiple monitors the landscape ones will be fine). EXPECTED RESULT Cursor is visible in all orientations SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.7.0-4-cachyos (64-bit) (available in About System) KDE Plasma Version: 5.92.0 KDE Frameworks Version: 5.248.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479583] cursor disappear on laptop screen in prime system with external display connected after kwin commit b214251f81cbacacf3ef483081a7cef15343fa7f,
https://bugs.kde.org/show_bug.cgi?id=479583 --- Comment #20 from Chris Sutcliff --- (In reply to fanzhuyifan from comment #19) > (In reply to Chris Sutcliff from comment #17) > > I'm using kde-unstable on Arch. > > > > I was having completely invisible cursor on any monitor (triple monitor > > setup). I found this bug and the fix on the arch forums where someone has > > also prepared the following patch to apply this fix and it's dependencies to > > kwin: https://pastebin.com/ykhzZZdB > > > > With that patch applied to kwin I now have a cursor on two of my monitors > > (both standard orientation, 4k) but still no cursor on my 3rd 1440p portrait > > rotated monitor. All 3 are connected via DisplayPort to an AMD 6900XT. > > > > I'm posting this here as the fix for this bug report at least partially > > solved my problem and something about my setup may give a clue as to why it > > doesn't work completely, or maybe this is a completely different bug. Happy > > to help debug it further if you can tell me what would help? > > You can find the commit fixing this bug in the "latest commit" field at the > top. > If you click on it you will be led to gitlab and see the commit, which also > contains a link to the corresponding MR and the related discussions. > > Alternately, on this page, if you look at the previous messages, you can > also find the MRs and commits fixing this. > > Cheers I'm already using the fix from this bug, it still doesn't work for portrait rotation. I'll open another for that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479583] cursor disappear on laptop screen in prime system with external display connected after kwin commit b214251f81cbacacf3ef483081a7cef15343fa7f,
https://bugs.kde.org/show_bug.cgi?id=479583 --- Comment #18 from Chris Sutcliff --- It seems the portrait rotation is the key, cursor is fine on landscape and inverted landscape but either portrait orientation makes it invisible. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479583] cursor disappear on laptop screen in prime system with external display connected after kwin commit b214251f81cbacacf3ef483081a7cef15343fa7f,
https://bugs.kde.org/show_bug.cgi?id=479583 Chris Sutcliff changed: What|Removed |Added CC||ch...@sutcliff.me --- Comment #17 from Chris Sutcliff --- I'm using kde-unstable on Arch. I was having completely invisible cursor on any monitor (triple monitor setup). I found this bug and the fix on the arch forums where someone has also prepared the following patch to apply this fix and it's dependencies to kwin: https://pastebin.com/ykhzZZdB With that patch applied to kwin I now have a cursor on two of my monitors (both standard orientation, 4k) but still no cursor on my 3rd 1440p portrait rotated monitor. All 3 are connected via DisplayPort to an AMD 6900XT. I'm posting this here as the fix for this bug report at least partially solved my problem and something about my setup may give a clue as to why it doesn't work completely, or maybe this is a completely different bug. Happy to help debug it further if you can tell me what would help? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478902] New: Pan Not Working
https://bugs.kde.org/show_bug.cgi?id=478902 Bug ID: 478902 Summary: Pan Not Working Classification: Applications Product: krita Version: 5.2.2 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Move Assignee: krita-bugs-n...@kde.org Reporter: luvkitti...@gmail.com Target Milestone: --- SUMMARY *** Middle mouse 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. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 472591] The file or folder Message recipient disconnected from message bus without replying does not exist.
https://bugs.kde.org/show_bug.cgi?id=472591
--- Comment #3 from Chris ---
Unfortunately... my above workaround has ceased to work.
I"m now getting:
kf.coreaddons: Some files could not be exported.
QDBusError("org.freedesktop.DBus.Error.NoReply", "Message recipient
disconnected from message bus without replying")
--
You are receiving this mail because:
You are watching all bug changes.
[kmymoney] [Bug 439776] Aqbanking/Kbanking broken in mingw builds on Windows 7
https://bugs.kde.org/show_bug.cgi?id=439776 --- Comment #14 from Chris Larson --- (In reply to Chris Larson from comment #13) > Unsure if this merits a new bug report or is merely additional information > for this one, so I'm initially piggybacking here. > Experiencing the OP's issue, using a newly install KMyMoney using latest > stable build for MacOS, on an Apple Silicon M1 MacBook Pro running Sonoma > 14.1. Configure aqbanking is not presented as an option under Settings. > > Happy to file this separately, if that's preferred. Happy to provide > additional information on request. Latest Stable as of this post: Build 1840 from https://binary-factory.kde.org/view/MacOS/job/KMyMoney_Release_macos/ Aqbanking also seems absent on my machine on Nightly, but as it is Nightly, I'm not sure that merits mention here. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 439776] Aqbanking/Kbanking broken in mingw builds on Windows 7
https://bugs.kde.org/show_bug.cgi?id=439776 Chris Larson changed: What|Removed |Added CC||cklar...@gmail.com --- Comment #13 from Chris Larson --- Unsure if this merits a new bug report or is merely additional information for this one, so I'm initially piggybacking here. Experiencing the OP's issue, using a newly install KMyMoney using latest stable build for MacOS, on an Apple Silicon M1 MacBook Pro running Sonoma 14.1. Configure aqbanking is not presented as an option under Settings. Happy to file this separately, if that's preferred. Happy to provide additional information on request. -- You are receiving this mail because: You are watching all bug changes.
[palapeli] [Bug 477851] New: Puzzle provided incorrect fitting and color pieces to complete it, but then removed them, leaving the puzzle deeming itself completed but not so
https://bugs.kde.org/show_bug.cgi?id=477851 Bug ID: 477851 Summary: Puzzle provided incorrect fitting and color pieces to complete it, but then removed them, leaving the puzzle deeming itself completed but not so Classification: Applications Product: palapeli Version: 2.1.23083 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: majew...@gmx.net Reporter: dbxrec...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- Created attachment 163709 --> https://bugs.kde.org/attachment.cgi?id=163709=edit Three pieces were removed by the program, and unable to insert them to complete the puzzle , which deemed the puzzle complete, when it was not. 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. Played castle of Maintenon in palapeli 2. I had as I recall two pieces left to insert each of which appeared not to be possible to fit 3. I proceeded to try, and the puzzle finished without ability to complete it OBSERVED RESULT Inability to complete the puzzle EXPECTED RESULT I expected to be able to insert the remaining pieces but neither appeared correct in color or shape to do so. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux Spiral (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 472591] The file or folder Message recipient disconnected from message bus without replying does not exist.
https://bugs.kde.org/show_bug.cgi?id=472591 --- Comment #2 from Chris --- I found some more information on this. Everything on the Internet seems to be pointing me in the wrong direction when trying to get to the bottom of this. It has nothing to do with Fuse (though that is the most popularly suggested reason). The reason why this occurring is because the system (for whatever reason) doesn't have permissions to /run/user to write a directory for the UID of the user that is launching dolphin. In my case: /run/user/1000. As a test, I changed the permissions of /run/user to 777, and suddenly dolphin works. Perhaps you could restrict it to 775, and put yourself in the root group, as an alternative. Obviously, this is not a good solution -- but it does put a much finer point on what is going on. For me, I just temporarily change the permissions if it is causing me too much of a headache as a work-around, then flip it back. Its something for now... which is better than nothing... I hope the KDE team can come up with a real fix relatively soon. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398689] Image disappears when zooming in after scale transform
https://bugs.kde.org/show_bug.cgi?id=398689 Chris Peñalver changed: What|Removed |Added CC||chris@penalvch.online --- Comment #32 from Chris Peñalver --- *** Bug 477484 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 477484] After cropping, image disappears
https://bugs.kde.org/show_bug.cgi?id=477484 Chris Peñalver changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #4 from Chris Peñalver --- (In reply to Freya Lupen from comment #3) > If it's fixed by unchecking Preferences->Display->Use texture buffer, it's a > duplicate of bug 398689 (a macOS-only bug). Hi Freya, Thanks for the suggestion! I unchecked the box and it wasn't reproducible. Hence, I'll mark this a duplicate for now. *** This bug has been marked as a duplicate of bug 398689 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 477484] After cropping, image disappears
https://bugs.kde.org/show_bug.cgi?id=477484 Chris Peñalver changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Chris Peñalver --- (In reply to wolthera from comment #1) > Hi, > > I can't reproduce this on my Linux build. This wasn't reproduced in Linux. > Can you share the export options? This has nothing to do with exporting. This occurs before any exporting. > Also, is the problem here that the thumbnail shows a checker board or is it > other applications that are having the same problem (like for example: image > viewer, web browser). This is only about how the image visually disappears after hitting Enter when done cropping. This has nothing to do with other applications, and no other applications have the same problem. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 477484] New: After cropping, image disappears
https://bugs.kde.org/show_bug.cgi?id=477484 Bug ID: 477484 Summary: After cropping, image disappears Classification: Applications Product: krita Version: 5.2.1 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: minor Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: chris@penalvch.online Target Milestone: --- Created attachment 163444 --> https://bugs.kde.org/attachment.cgi?id=163444=edit File problem consistently reproducible with. 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. Create a png file using flameshot. 2. Open this png file in Kirta 3. Crop the file and save it. OBSERVED RESULT The image is replaced with a checker board background (although the file itself still shows the image if the file is closed and reopened with Krita). EXPECTED RESULT The cropped image remains. SOFTWARE/OS VERSIONS Windows: N/A macOS: 14.1.1 Linux/KDE Plasma: N/A (available in About System) KDE Plasma Version: N/A KDE Frameworks Version: N/A Qt Version: N/A ADDITIONAL INFORMATION This has occurred with all prior versions of Krita released over last couple years, so not confirmed a regression. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477296] New: Dolphin moves user to grandparent of deleted directory instead of parent
https://bugs.kde.org/show_bug.cgi?id=477296 Bug ID: 477296 Summary: Dolphin moves user to grandparent of deleted directory instead of parent Classification: Applications Product: dolphin Version: 24.01.75 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: chris...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY If a Dolphin window is in a directory that is deleted, Dolphin moves the user to the grandparent directory of that deleted directory rather than the parent. STEPS TO REPRODUCE 1. In Dolphin, go to directory X 2. In another process (such as konsole), delete directory X 3. Observe how Dolphin moves the user when Dolphin notices the directory is deleted OBSERVED RESULT When a Dolphin window is in a directory that is deleted, Dolphin automatically moves the user to the grandparent of the deleted directory instead of the parent For example, I created a directory called testdir in $HOME Under testdir, I created directory test1 Under test1, I created directory test2 If I navigate to test2 in Dolphin then delete test2 in another process, Dolphin reports: Current location changed, '$HOME/testdir/dir1' is no longer accessible. Then I am moved to $HOME/testdir. Yet I see dir1 in $HOME/testdir and I can access $HOME/testdir/test1. Similarly, if I deleted $HOME/testdir/test1 ($HOME/testdir still exists), Dolphin would redirect me to $HOME instead of $HOME/testdir. EXPECTED RESULT Dolphin should drop me in the location nearest to the directory that was deleted. In the above example where $HOME/testdir/test1/test2 was deleted, it should drop me in $HOME/testdir/test1 instead of testdir since $HOME/testdir/test1 still exists. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Observed in both KDE Neon Unstable and ArchLinux (both from repos and built from kdesrc-build) (available in About System) KDE Plasma Version: 5.81.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 257602] K3B cannot burn Blurays (or AVCHDs)
https://bugs.kde.org/show_bug.cgi?id=257602 Chris changed: What|Removed |Added CC|k...@ontoemail.com | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 475488] In face detection, an option to suppress low quality faces as detected might improve recognition training and results
https://bugs.kde.org/show_bug.cgi?id=475488 Chris changed: What|Removed |Added CC||chrisc.gigam...@gmail.com --- Comment #3 from Chris --- Thumbs up. Good write-up and suggestion. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471335] Tag a detected face but not use it for training
https://bugs.kde.org/show_bug.cgi?id=471335 Chris changed: What|Removed |Added CC||chrisc.gigam...@gmail.com --- Comment #3 from Chris --- Thumbs up for this suggestion -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 471183] Face recognition, see and edit references
https://bugs.kde.org/show_bug.cgi?id=471183 Chris changed: What|Removed |Added CC||chrisc.gigam...@gmail.com --- Comment #20 from Chris --- (In reply to Craig from comment #19) > I think the better option would be to be able to select which faces are to > be used as a reference for the learning. Totally agree, this would be awesome. Manually hand-pick the best unblurred reference faces. Or at least remove blurred, grimacing, sunglassed faces from the reference list. :) - I read that currently digikam uses the 100 latest tagged face regions per face tag for reference. So maybe one can do some magic with some database manipulation of time stamps, to make the best tags the most recent? Coupled with a negative (rejection list per person), I think the recognition would improve a lot. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 470018] Search for similar faces by previous example selection
https://bugs.kde.org/show_bug.cgi?id=470018 Chris changed: What|Removed |Added CC||chrisc.gigam...@gmail.com --- Comment #1 from Chris --- (In reply to Andy from comment #0) > Hello, > my facial recognition has a very high error rate. I've already written a lot > about this. > At the moment I have over 2 unconfirmed and 3 unknown to work > through one by one. > My idea would be that I mark five to ten matching faces under "unconfirmed" > or "unknown" and then digikam groups new suggestions for me from all other > unknown or unconfirmed faces that show an actual similarity. Maybe that > would also work with a selection of the already confirmed faces. > When you're happy with the result, mark the first and last faces and confirm > them all at once. > > Best Regards > Andy I think the grouping under "Unconfirmed" is actually the automatic version of half of what you suggest. The problem is that the suggestion is probably wrong, since you need to manually select some (5-10 matching faces) and tell the algorhithm that "this is the same person, please find more like it." In another bug-report / suggestion I saw a mention that the last 100 face tags of a particular person are used by the algorithm to recognize people. Another way to phrase your idea, could be "allow the user to manually select 5-100 face regions of a particular person and make the algorithm use only those". It's not exactly the same, but it's all about helping the recognition algorithm use the best data. Maybe? :) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459499] The possibility to disable persons
https://bugs.kde.org/show_bug.cgi?id=459499 Chris changed: What|Removed |Added CC||chrisc.gigam...@gmail.com --- Comment #3 from Chris --- Thumbs up for the suggestion -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444394] Rejected face suggestions reappear for the same person the next time recognition is run
https://bugs.kde.org/show_bug.cgi?id=444394 Chris changed: What|Removed |Added CC||chrisc.gigam...@gmail.com --- Comment #6 from Chris --- (In reply to S. Burmeister from comment #4) > Does rejecting educate the detection engine or does it only learn from > confirmations? > > I have people with 400 confirmed faces and still digikam suggests the same > wrong faces each time I re-run the detection. So it seems to me that the > engine does not get any negative feedback and hence does not learn from > rejections. I agree. I would also like this feature. Possibly it could be done with a model similar to the one that connects confirmed and unconfirmed face tags to face regions. There could be a rejected category as well. Rejections should of course be cancellable again (if you reject by mistake). To make it even more useful, maybe a large rejection value could be applied to the face recognition, for every face tag, in order to make the recognition value make the a second best suggestion. It won't really "educate" the face recognition, but it will be helpful to the end user when running recognition again. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432537] Improve face-recognition accuracy by visually de-selecting "bad faces" to be used within the faces-engine
https://bugs.kde.org/show_bug.cgi?id=432537 Chris changed: What|Removed |Added CC||chrisc.gigam...@gmail.com --- Comment #6 from Chris --- (In reply to Maik Qualmann from comment #1) > The fact that only the last 100 assigned faces are used is no longer > available in the current version. We already have the wish to filter for > blurred faces. > > Maik This is interesting. I'm tagging a large library from scratch and, like cellipo.at.hotmail.com, I also like to tag people with blurred face and people with their backs turned. Instead of using the last 100 tags, would it be possible to pick the 100 best tags manually? Should I make this a new feature request? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432207] After rejection, assign face to next best match
https://bugs.kde.org/show_bug.cgi?id=432207 Chris changed: What|Removed |Added CC||chrisc.gigam...@gmail.com --- Comment #3 from Chris --- If possible to inject a "value" into the deep learning mechanism, a rejection could apply a large "negative" recogition value to a rejected face tag, so it would not become to top choice after a re-scan. How to keep track of rejections and cancel errornous rejections? - Similar to how face regions are related to face tags in the database, but with the meaning "rejected" instead of "matched". - A UI feature could allow you to view rejections and cancel them, in case of mistakes -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 475716] New: Feature Request: Spacer Tool in Combination With Existing Move Commands
https://bugs.kde.org/show_bug.cgi?id=475716 Bug ID: 475716 Summary: Feature Request: Spacer Tool in Combination With Existing Move Commands Classification: Applications Product: kdenlive Version: 23.08.1 Platform: Debian stable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: chrisver...@gmail.com Target Milestone: --- SUMMARY I would first like to say that I am really impressed with KdenLive. Coming from Magix (Sony) Vegas which is an absolute unstable mess which is what I used for 10 years. This program appears to be rock solid on Debian Stable and very intuitive to use. I am focusing primarily on audio cross-fading and precise edits on the timeline. This is the bulk of my work before I send off to other editors for adding VFX. I have two inquiries as I am building my workflow in Kdenlive. Question 1: Is there a way to make it so when pressing play and stop on the timeline, the timeline cursor returns to the original point where we pressed play from? This is a feature I am used to in other audio editors of the past. It's useful for when I am listening closely to the accuracy of an audio cross-fade. The current way to do this is by moving the timeline cursor back in order to replay from a point before the edit, which is one extra step. Question 2/Feature Request: I am using the Grab Current Item (Shift + G) function to grab the currently selected clip and then I use the arrow keys to move the clip 1 frame at a time to the left or to the right, or to move it to a different track. Sometimes when doing 2nd pass timeline edits, I often need to use the Spacer Tool in order to make sure the existing edits after the timeline cursor also shift. This is important for keeping those existing edits in their exact relative positions. I noticed when using the spacer tool it is necessary to use the mouse to click and drag the clips. I did try to use Grab Current Item function in combination with the spacer tool and does not seem to be supported. Basically what I am looking for is a way to use the spacer tool in combination with the arrow keys to make precise shifts of 1 frame at a time. This is because I might be doing a cross-fade in the middle of the project and all of the other cross-fades to the right should keep their existing relative positions. Using the mouse is ok but it is a little less precise and I need to keep zooming in and out of the project when using that method. Kdenlive rocks, thank you for supporting it! -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 475712] New: System Monitor Persistent Crashing X11 (might be a duplicate but not sure)
https://bugs.kde.org/show_bug.cgi?id=475712 Bug ID: 475712 Summary: System Monitor Persistent Crashing X11 (might be a duplicate but not sure) Classification: Applications Product: plasma-systemmonitor Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: chrisver...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Application: plasma-systemmonitor (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-12-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: 1. Open System Monitor on X11 desktop 2. Select one of the default tabs on the left like "Applications", and it crashes. 3. When I re open the system monitor again I see duplicate applications running of the system monitor. Sometimes I noticed other duplicate applications running depending on what I had running. Once the system monitor crashes, it seems very easy to make it crash over and over using the same method. Though I have noticed inconsistencies with which buttons need to be clicked to make it crash. I have not dug very deep into it except that I am reporting these persistent crashes. 4. When I log out using this command after crashing the System Monitor: qdbus org.kde.ksmserver /KSMServer logout 0 0 0 It takes a few seconds to process. First the background goes black behind the terminal, as if the desktop environment is shutting down but the user session is not logged out yet. After a few seconds it proceeds to log out. Normally that command will log me out of the session immediately without a hiccup. One thing I can say is that it started happening when I switched to the X11 desktop. I need to be on X11 for something I am building right now and my Nvidia card has more options under X11 than Wayland. The crash can be reproduced sometimes. -- Backtrace: Application: System Monitor (plasma-systemmonitor), signal: Segmentation fault [KCrash Handler] #4 0x in ?? () #5 0x7f203fc3fae7 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f203fc3fb59 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f203fdc1dc2 in QAccessibleQuickItem::role() const () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f2045177081 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #9 0x7f2045179e04 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #10 0x7f204517b5a1 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #11 0x7f203fc4d6d3 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7f203fc55ffd in QQuickItem::setParentItem(QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x7f203fc5650d in QQuickItem::~QQuickItem() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x7f200c7d68c5 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #15 0x7f203f3a7357 in QQmlTableInstanceModel::destroyModelItem(QQmlDelegateModelItem*, QQmlTableInstanceModel::DestructionMode) () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #16 0x7f203f3cdaf1 in ?? () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #17 0x7f203f3a6d85 in QQmlTableInstanceModel::drainReusableItemsPool(int) () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #18 0x7f203fd3de8c in QQuickTableView::geometryChanged(QRectF const&, QRectF const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #19 0x7f203fc4c2e8 in QQuickItem::setSize(QSizeF const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #20 0x7f203f4ae3a9 in QQuickControlPrivate::resizeContent() () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #21 0x7f203f4aaef3 in QQuickControlPrivate::setRightPadding(double, bool) () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #22 0x7f204aceaa43 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #23 0x7f204aceb93e in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #24 0x7f204ace9354 in QQmlBinding::update(QFlags) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #25 0x7f204acc677f in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #26 0x7f20494e8a8d in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f204ac6ea35 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #28 0x7f204aceaa19 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #29 0x7f204aceb93e in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #30 0x7f204ace9354 in QQmlBinding::update(QFlags) () from
[Akonadi] [Bug 457233] Please provide oauth2 login for IMAP - not just Gmail
https://bugs.kde.org/show_bug.cgi?id=457233 --- Comment #11 from Chris --- (In reply to Björn Bidar (Thaodan) from comment #8) > *** Bug 455113 has been marked as a duplicate of this bug. *** Bug 455113 is an actual bug because it does something it shouldn't: connecting to Gmail when it's a Yahoo address. In light of this, shouldn't this bug be considered an actual one too, instead of being classified as a mere wishlist item? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 457233] Please provide oauth2 login for IMAP - not just Gmail
https://bugs.kde.org/show_bug.cgi?id=457233 Chris changed: What|Removed |Added CC||inkbottle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 474883] New: Videos exported from Kdenlive cannot be pulled into iPhone Photos App due to the Codec ID. (hev1 vs hvc1)
https://bugs.kde.org/show_bug.cgi?id=474883 Bug ID: 474883 Summary: Videos exported from Kdenlive cannot be pulled into iPhone Photos App due to the Codec ID. (hev1 vs hvc1) Classification: Applications Product: kdenlive Version: 23.08.1 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: chrisver...@gmail.com Target Milestone: --- SUMMARY I was having a hard time figuring out why I was not able to pull any video rendered from KdenLive from Telegram right into my iPhone camera roll. This is a workflow thing I use to upload shorts to YouTube because they only let you choose the thumbnail for the video if it is uploaded from your mobile device. I made sure first the problem was coming from Kdenlive, and I did detailed comparisons and analysis using mediainfo. I determined that KdenLive exports H265 videos with the hev1 Codec ID and I noticed that my other video editor exported H265 with the hvc1 Codec ID. Any and all videos I exported so far with Kdenlive are not able to be downloaded from Telegram into iPhone Photos App. They do however play in Telegram and the videos themselves are fine, this is just a compatibility problem that might be specific to iOS (QuickTime). After running this FFMPEG command on a H265 video exported in KdenLive: ffmpeg -i .mov -c:v copy -tag:v hvc1 -c:a copy .mov Then uploaded the new file to Telegram, I can now pull it into the iPhone camera roll like usual. STEPS TO REPRODUCE 1. Export a H265 video from Kdenlive (the issue is not specific to H265 I also experienced the same with H264 but my preferred render codec is hevc_nvenc). 2. Upload it to Telegram Saved Messages in order to pull the video into iPhone camera roll 3. Save the video into your iPhone camera roll. OBSERVED RESULT If the video does not appear in camera roll, this is the problem I was experiencing. EXPECTED RESULT After changing the Codec ID using the ffmpeg command, it now works to grab the file from Telegram into the iPhone Photos app. SOFTWARE/OS VERSIONS Not specific to the OS but I am on Windows 11. ADDITIONAL INFORMATION Stack overflow article that helped me solve it: https://stackoverflow.com/questions/32152090/encode-h265-to-hvc1-codec -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 455113] Oauth2 is missing yahoo redirect to Google instead
https://bugs.kde.org/show_bug.cgi?id=455113 Chris changed: What|Removed |Added Status|CONFIRMED |ASSIGNED CC||inkbottle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 462042] Add Yahoo as an authentication method so yahoo accounts can be added to kmail
https://bugs.kde.org/show_bug.cgi?id=462042 Chris changed: What|Removed |Added CC||inkbottle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 444301] Akonadi opens gmail login webpage when adding a yahoo account
https://bugs.kde.org/show_bug.cgi?id=444301 --- Comment #4 from Chris --- Following on @Manny, this bug is duplicate of bug 455113 and bug 462042 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 472216] On a Laptop KScreen picks resolution to match internal screen aspect ratio for connected external monitors
https://bugs.kde.org/show_bug.cgi?id=472216 --- Comment #2 from Chris Rizzitello --- I've have not seen this in a bit. I think we can close it for now. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439664] Dolphin crashes with Insync 3.4.2.40293
https://bugs.kde.org/show_bug.cgi?id=439664 Chris Tree changed: What|Removed |Added CC|christree4...@outlook.com | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 473910] New: 'Artistic Color Selector' Docker Settings Break 'Gamut Mask' Docker.
https://bugs.kde.org/show_bug.cgi?id=473910 Bug ID: 473910 Summary: 'Artistic Color Selector' Docker Settings Break 'Gamut Mask' Docker. Classification: Applications Product: krita Version: 5.1.5 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: chris.m.b...@gmail.com Target Milestone: --- Created attachment 161267 --> https://bugs.kde.org/attachment.cgi?id=161267=edit Example of the dockers being in conflict with one another. SUMMARY As the title suggests, if you configure the 'Artistic Color Selector' docker with specific settings, it is unresponsive to changes made in the sibling 'Gamut Masks' docker. STEPS TO REPRODUCE 1. With both dockers visible, in the 'Artistic Color Selector' docker, configure the Hue Steps to be in 'Continuous Mode' (infinity symbol on). 2. Then configure 'Enforce Gamut Mask' to be enabled. OBSERVED RESULT Switching between the built-in Gamut Masks visibly does not update the Artistic Color Selector as they should (although the valid selectable zones have in fact been updated). EXPECTED RESULT The presentation layer of the Artistic Color Selector should be repainted to reflect the currently selected Gamut Mask. SOFTWARE/OS VERSIONS Windows: macOS: Ventura 13.5 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION See screenshot. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 472697] Open with Open on Connected Device via KDE Connect appears for all files in Dolphin
https://bugs.kde.org/show_bug.cgi?id=472697 --- Comment #3 from Chris Holland --- Uhg, can't find it. It's possible that the change is related to "mime inheritance" instead of "application/octet-stream". * KIO Search: https://invent.kde.org/search?search=application%2Foctet-stream_source=navbar_id=2729_id=1552_code=true_ref=master * (3 years ago) `KCoreDirLister::setMimeFilter` https://invent.kde.org/frameworks/kio/-/blame/master/src/core/kcoredirlister.cpp?page=3#L2319 * (2 years ago) `KFileItemPrivate::determineMimeTypeHelper` https://invent.kde.org/frameworks/kio/-/blame/master/src/core/kfileitem.cpp#L550 * (4 years ago) `KFileItem::currentMimeType` https://invent.kde.org/frameworks/kio/-/blame/master/src/core/kfileitem.cpp?page=2#L1667 * (7 months ago) `KFileFilterCombo::setMimeFilter` https://invent.kde.org/frameworks/kio/-/blame/master/src/filewidgets/kfilefiltercombo.cpp#L248 * (2 years ago) `KFileWidgetPrivate::updateAutoSelectExtension` https://invent.kde.org/frameworks/kio/-/blame/master/src/filewidgets/kfilewidget.cpp?page=3#L2300 * (3 years ago) `HTTPProtocol::davParsePropstats` https://invent.kde.org/frameworks/kio/-/blame/master/src/kioworkers/http/http.cpp#L932 * (7 years ago) `HTTPProtocol::fixupResponseMimetype` https://invent.kde.org/frameworks/kio/-/blame/master/src/kioworkers/http/http.cpp?page=3#L2605 * (7 years ago) `http.json "defaultMimetype"` https://invent.kde.org/frameworks/kio/-/blame/master/src/kioworkers/http/http.json#L7 * (1 year ago) `kfileitemactions.cpp mimeTypeListContains` https://invent.kde.org/frameworks/kio/-/blame/master/src/widgets/kfileitemactions.cpp#L61 * (7 months ago) `KFileItemActionsPrivate::addPluginActionsTo` https://invent.kde.org/frameworks/kio/-/blame/master/src/widgets/kfileitemactions.cpp#L533 * (1 year ago) `KFilePropsPlugin::slotEditFileType` https://invent.kde.org/frameworks/kio/-/blame/master/src/widgets/kpropertiesdialog.cpp?page=2#L1234 * (1 year ago) `KFilePropsPlugin::updateDefaultHandler` https://invent.kde.org/frameworks/kio/-/blame/master/src/widgets/kpropertiesdialog.cpp?page=2#L1595 * Dolphin Search (No Results): https://invent.kde.org/search?repository_ref=master=application%2Foctet-stream_code=true=projects_id=1561_id=2775 * KService (kbuildsycoca5) (A few autotests): https://invent.kde.org/search?repository_ref=master=application%2Foctet-stream_code=true=projects_id=1552_id=2379 * (3 years ago) Fix application preference ordering for mimetypes with multiple inheritance. https://invent.kde.org/frameworks/kservice/-/commit/d4c9cb9d0652c1ed7ba504335a50ea6bca7851e5 - Operating System: openSUSE Tumbleweed 20230823 KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 Kernel Version: 6.4.11-1-default (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 472697] Open with Open on Connected Device via KDE Connect appears for all files in Dolphin
https://bugs.kde.org/show_bug.cgi?id=472697 Chris Holland changed: What|Removed |Added CC||zrenf...@gmail.com --- Comment #2 from Chris Holland --- * https://discuss.kde.org/t/everything-downloaded-in-firefox-opens-in-kde-connect/4337 * https://old.reddit.com/r/kde/comments/163jnhj/how_to_remove_kde_connects_url_handler_from/ * https://invent.kde.org/network/kdeconnect-kde/-/blame/master/data/org.kde.kdeconnect_open.desktop#L132 * https://invent.kde.org/network/kdeconnect-kde/-/commit/f1ce22124ce7dd630b8e909b4c50f90f035166d5 > https://discuss.kde.org/u/guss77 (2023-08-26): > > Weird that it only started happening recently - the relevant commit that > added KDE Connect open on application/octet-stream 1 was done 2 years ago. So it's either a change in Dolphin, or KIO, or some other KDE Framework related to MimeTypes? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 444301] Akonadi opens gmail login webpage when adding a yahoo account
https://bugs.kde.org/show_bug.cgi?id=444301
--- Comment #3 from Chris ---
Just adding a bit of context:
Yahoo-mail used to be accessible to Kmail and other third party apps though an
app password. It has been described several times lately that this method might
not work any more.
https://answers.microsoft.com/en-us/outlook_com/forum/all/when-i-try-to-generate-an-app-password-in-yahoo-i/99f61c31-8c33-4995-bab6-245e95f96230
("this service is temporarily unavailable")
However yahoo-mail can also be accessed with OAuth method, and Microsoft has
tagged the above issue as "fixed" by making the shift to OAuth:
https://support.microsoft.com/en-us/office/how-to-add-a-yahoo-imap-account-to-outlook-desktop-without-an-app-password-d13fb02d-eb93-4775-bae9-0e54bf2f5bca
("status: fixed")
So I guess Kmail linking to Gmail OAuth page when trying to setup a yahoo-mail
account is totally the smart move.
Maybe if it were linking to Yahoo OAuth page it would work even better.
--
You are receiving this mail because:
You are watching all bug changes.
[Akonadi] [Bug 444301] Akonadi opens gmail login webpage when adding a yahoo account
https://bugs.kde.org/show_bug.cgi?id=444301 --- Comment #2 from Chris --- Also, discussed here: https://www.reddit.com/r/kde/comments/yy4snw/akonadikmail_opens_a_gmail_login_page_when_adding/?rdt=39337 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 444301] Akonadi opens gmail login webpage when adding a yahoo account
https://bugs.kde.org/show_bug.cgi?id=444301 Chris changed: What|Removed |Added CC||inkbottle...@gmail.com --- Comment #1 from Chris --- Same here, Operating System: NixOS 23.11 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.9 Kernel Version: 6.4.3 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 472915] Drag drop moving email in Thunderbird and desktop environment crashed
https://bugs.kde.org/show_bug.cgi?id=472915 --- Comment #5 from Chris Handy --- Created attachment 160762 --> https://bugs.kde.org/attachment.cgi?id=160762=edit New crash information added by DrKonqi akonadiserver (5.22.3 (22.12.3)) using Qt 5.15.9 I was switching between Firefox and LibreOffice Calc when both crashed -- Backtrace (Reduced): #4 0x55e13a6e129b in Akonadi::Server::AkonadiServer::connectionDisconnected() () #5 0x7f95588c8264 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #6 0x7f955889d5fb in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #7 0x7f95588a0984 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #8 0x7f95588eec27 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 472915] Drag drop moving email in Thunderbird and desktop environment crashed
https://bugs.kde.org/show_bug.cgi?id=472915 Chris Handy changed: What|Removed |Added CC||ch...@thehandys.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471136] kwin_x11 freezes xorg under certain conditions
https://bugs.kde.org/show_bug.cgi?id=471136 Chris Holland changed: What|Removed |Added CC||zrenf...@gmail.com --- Comment #9 from Chris Holland --- I was experiencing this or a similar bug on an AMD iGPU. The screen would freeze but the mouse could be moved around. Music continued to play. After a few seconds it un-freezes. I was toying around with Disabling Desktop Effects: * Morphing Popups * Sliding Popups * Squash (minimize effect) And after clicking apply, the bug went away. I re-enabled those effects but I could no longer reproduce. -- I could previously easily reproduce the bug by: * Spamming Meta key to open the app launcher (froze opening and closing). * Gliding over the panel tasks in the taskmanager widget. * Alt+Tabing. * Opening/Closing Yakuake Previously I killed kwin_x11 and the bug went away when opening/closing the app menu with the mouse. I tried disabling the compositor with the toggle key Alt+Shift+F12. I did not disabled it from startup in System Settings > Compositor > Enable on Startup. I still experienced the bug after disabling the compositor with the toggle key, but maybe I did not actually disable it? I need to confirm this in a fresh KDE install. I previously installed Ubuntu (Gnome3 based) in another partition and did not experience this bug so it's not the Kernel. - Operating System: openSUSE Tumbleweed 20230801 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.4.6-1-default (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics ( https://www.amd.com/en/product/11176 ) Memory: 13.5 GiB of RAM (Corsair Vengence LPX 3600Ghz 2x8 GB sticks, with 2GB? dedicated to VRAM) Graphics Processor: AMD Radeon Graphics Manufacturer: Micro-Star International Co., Ltd. (MSI Pro B550M-VC WIFI) Product Name: MS-7C95 System Version: 3.0 - - [YES] Entire desktop image is frozen - [YES] Pointer still works - [YES] Pointer still operates on desktop under frozen image (more on that below) - [TODO] killall -9 kwin_x11 and relaunching kwin_x11 recovers - If during the freeze, I tried to operate on any windows with pointer, they now show up in updated positions/sizes, etc. - [TODO] Does not happen if compositing is disabled - [DID NOT CHECK] Does not happen on kernels older than 6.1.9 - [?] Does not happen with any other program - [YES? TODO Was it Xorg or Wayland?] Does not happen on Gnome+Xorg - [TODO] Does not happen on Plasma+Wayland (But too many other things don't work for me) - [TODO] Does not happen if compositing is toggled off then on after logging in - [NO, kwin_x11 --replace still has the bug] Does not happen a 2nd time if kwin is killed and restarted - [TODO] Happens with a new user and user profile with default settings -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 472617] New: Latte Crashes when I attempt to change themes
https://bugs.kde.org/show_bug.cgi?id=472617 Bug ID: 472617 Summary: Latte Crashes when I attempt to change themes Classification: Plasma Product: lattedock Version: 0.10.8 Platform: Ubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: chris.warren.2...@gmail.com Target Milestone: --- Application: latte-dock (0.10.8) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.0-26-generic x86_64 Windowing System: X11 Distribution: Ubuntu 23.04 DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: When I attempt to change themes latte crashes & I'm not able use the things that I downloaded from https://store.kde.org/ The crash can be reproduced every time. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [KCrash Handler] #4 0x in ?? () #5 0x7f17516f39af in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f16fbc797cd in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/private/kicker/libkickerplugin.so #7 0x7f17516f39dc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f17516ecb03 in QObject::destroyed(QObject*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f17516f1bf4 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f16fbc72354 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/private/kicker/libkickerplugin.so #11 0x7f16fbc6bcf5 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/private/kicker/libkickerplugin.so #12 0x7f17516e58ae in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f17516f19f4 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f16fbc829f9 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/private/kicker/libkickerplugin.so #15 0x7f17516e58ae in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f17516f19f4 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f17537e3989 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #18 0x7f1753add4aa in KDeclarative::QmlObject::~QmlObject() () from /lib/x86_64-linux-gnu/libKF5Declarative.so.5 #19 0x7f1753ade28d in KDeclarative::QmlObjectSharedEngine::~QmlObjectSharedEngine() () from /lib/x86_64-linux-gnu/libKF5Declarative.so.5 #20 0x7f17516e58ae in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f17516f19f4 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f173594134d in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #23 0x7f17516e58ae in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f17516f19f4 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f173593bdbd in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #26 0x7f1753b34098 in ?? () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #27 0x7f1753b3429d in ?? () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #28 0x7f1753b1dc46 in Plasma::Applet::~Applet() () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #29 0x7f1753b1dc6d in Plasma::Applet::~Applet() () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #30 0x7f17516e58ae in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x7f17516f19f4 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7f1753b237ad in Plasma::Containment::~Containment() () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5 #33 0x5569a1621620 in ?? () #34 0x5569a16357f6 in ?? () #35 0x5569a16380d3 in ?? () #36 0x7f17516f7a26 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #37 0x7f17516e7bf5 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #38 0x7f175256bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #39 0x7f17516bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #40 0x7f1751714201 in QTimerInfoList::activateTimers() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #41 0x7f1751714b34 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #42 0x7f174fb1549d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #43 0x7f174fb70178 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #44 0x7f174fb141b0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #45 0x7f1751714e7a in QEventDispatcherGlib::processEvents(QFlags) () from
[neon] [Bug 472591] New: The file or folder Message recipient disconnected from message bus without replying does not exist.
https://bugs.kde.org/show_bug.cgi?id=472591 Bug ID: 472591 Summary: The file or folder Message recipient disconnected from message bus without replying does not exist. Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: cjd...@brokensolstice.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Hi. I've been getting this error a lot the last few months... I thought it would go away with some updates, so I gave it some time. But it still occurs. When I try to copy a file from one folder to another I get this error: The file or folder Message recipient disconnected from message bus without replying does not exist. The error does not occur on the command line. Only when trying to use dolphin, either from a drag-and-drop or from a copy and paste. STEPS TO REPRODUCE 1. Pull up dolphin on a folder (like /home/myname/Documents/" 2. Open another dolphin instance and navigate to another folder 3. Drag the file from the first dolphin instance to the 2nd. OBSERVED RESULT The file or folder Message recipient disconnected from message bus without replying does not exist. EXPECTED RESULT I expect it to copy the file SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: 5.27.6 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION After a reboot, this behavior stops for a while, but inevitably starts again within half an hour of use or so and persists until reboot, when the cycle begins again. It seems to be worse when I'm using it through a vnc session... but that might be just because I use it that way more often... not sure. But I do use tigervnc over ssl a lot for this system. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472438] Failed to update the database schema from version 15 to version 16.
https://bugs.kde.org/show_bug.cgi?id=472438 Chris changed: What|Removed |Added Component|Database-Sqlite |Database-Schema --- Comment #1 from Chris --- Not sure if I am posting this in the right category -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472438] New: Failed to update the database schema from version 15 to version 16.
https://bugs.kde.org/show_bug.cgi?id=472438 Bug ID: 472438 Summary: Failed to update the database schema from version 15 to version 16. Classification: Applications Product: digikam Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Database-Sqlite Assignee: digikam-bugs-n...@kde.org Reporter: crgla...@gmail.com Target Milestone: --- I am trying to use Digikam. Each time I start I receive the following: Failed to update the database schema from version 15 to version 16. Please read the error messages printed on the console and report this error as a bug at bugs.kde.org. EXPECTED RESULT Digikam would open. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.0 Kernel Version: 6.4.3-1 default (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 472144] Brightness not saved or loaded at startup.
https://bugs.kde.org/show_bug.cgi?id=472144 --- Comment #4 from Chris --- My reply seems to have vanish but anyway, It's MX linux 21 with KDE desktop. I was unable to select that because it was missing from the menu. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 472144] Brightness not saved or loaded at startup.
https://bugs.kde.org/show_bug.cgi?id=472144 --- Comment #3 from Chris --- Created attachment 160391 --> https://bugs.kde.org/attachment.cgi?id=160391=edit brightness save -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 472144] Brightness not saved or loaded at startup.
https://bugs.kde.org/show_bug.cgi?id=472144 --- Comment #2 from Chris --- Created attachment 160390 --> https://bugs.kde.org/attachment.cgi?id=160390=edit brightness app -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 472216] New: On a Laptop KScreen picks resolution to match internal screen aspect ratio for connected external monitors
https://bugs.kde.org/show_bug.cgi?id=472216 Bug ID: 472216 Summary: On a Laptop KScreen picks resolution to match internal screen aspect ratio for connected external monitors Classification: Plasma Product: KScreen Version: 5.27.4 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: rizzite...@kde.org Target Milestone: --- SUMMARY I have a laptop with a 16:10 aspect screen internal screen, This machine is used with an external 16:9 screen as its primary screen. Every time I boot up it connects to the monitor with a 16:10 resolution despite the settings being set for 1920x1080 (a 16:9 aspect). In addition to this the list of supported resolutions only shows up to the highest 16:10 resolution the monitor supports (1650x1080 in my case). Making it impossible to select the correct resolution as not show in the list! In order to see the real list of resolutions I need to unplug the monitor with KDE running and plug it back in. This could be related to https://bugs.kde.org/show_bug.cgi?id=469113. STEPS TO REPRODUCE 1. Use a laptop with 16:10 internal screen. 2. Plugin the monitor, turn on the laptop 3. Set the correct settings for your external monitor. The external should be in a different aspect ratio then the internal aspect ratio. Disable the internal screen. Be sure you have save the config for "this specific arrangement". 4. Reboot 5. Upon reboot check the resolution of the external screen OBSERVED RESULT The Saved resolution for the external screen (1920x1080) is not used and instead a resolution matching the internal aspect is picked. This list of available resolutions in the display KCM now stops at the highest resolution that the monitor supports in the aspect ratio of the internal screen. EXPECTED RESULT The previously selected resolution is selected for the external monitor and the full list is shown in the Display KCM for the external devices supported resolutions. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Additional Information Laptop Screen Default Resolution: 1920x1200@60hz External Screen Default Resolution: 1920x1080@75hz HDMI is used for the connection. Tested on Wayland and X11 Tested with the laptop open and closed while booting. During boot the external says its mode is 1920x1080. If you correct the resolution then log out . The correction will persist until reboot -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 472144] New: Brightness not saved or loaded at startup.
https://bugs.kde.org/show_bug.cgi?id=472144 Bug ID: 472144 Summary: Brightness not saved or loaded at startup. Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: at...@exxoshost.co.uk Target Milestone: --- SUMMARY *** Brightness app doesn't save settings. *** STEPS TO REPRODUCE 1. Change brightness. Click save. Reboot, brightness defaults back to 100% 2. 3. OBSERVED RESULT Brightness not saved or loaded at startup. EXPECTED RESULT Save brightness. SOFTWARE/OS VERSIONS MX Linux/KDE Plasma: -- You are receiving this mail because: You are watching all bug changes.
[analitza] [Bug 323370] Problem with horizontal and vertical marks while changing scale to other than 1 in 2D space
https://bugs.kde.org/show_bug.cgi?id=323370 Chris changed: What|Removed |Added Version|unspecified |8.0.0 Platform|Ubuntu |Archlinux Alias||nano CC||three6nine...@proton.me Component|analitzaplot|core -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 470681] breeze-icon-theme package not installed by default on Neon Unstable (June 4th, 2023)
https://bugs.kde.org/show_bug.cgi?id=470681 Chris Rizzitello changed: What|Removed |Added CC||rizzite...@kde.org Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Chris Rizzitello --- I also had to install breeze-icon-theme for the icons on neon -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451702] Various KDE apps lock up with 100% CPU usage when monitor powers off
https://bugs.kde.org/show_bug.cgi?id=451702 --- Comment #2 from Chris --- This doesn't seem to be happening anymore for me. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 470479] New: Gwenview crashed when trying to rotate an image
https://bugs.kde.org/show_bug.cgi?id=470479 Bug ID: 470479 Summary: Gwenview crashed when trying to rotate an image Classification: Applications Product: gwenview Version: 22.12.3 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: christree4...@outlook.com Target Milestone: --- Application: gwenview (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.0-20-generic x86_64 Windowing System: Wayland Distribution: Ubuntu 23.04 DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: I had opened Gwenview to look at 2 images, one was upside down, so I went to rotate the image and Gwenview crashed. The crash can be reproduced sometimes. -- Backtrace: Application: Gwenview (gwenview), signal: Segmentation fault [KCrash Handler] #4 __memcpy_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:461 #5 0x7f04225904a7 in QImage::copy(QRect const&) const () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #6 0x7f042434538a in ?? () from /lib/x86_64-linux-gnu/libgwenviewlib.so.5 #7 0x7f04230b6921 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f04230b717a in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f04230b6673 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f04230b717a in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f04230b6673 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f042307a5d4 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f04231223f8 in QGraphicsEffectSource::draw(QPainter*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f04230b7573 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f04230b7ba2 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f04230dc277 in QGraphicsView::paintEvent(QPaintEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f0422daec28 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f0422e5b792 in QFrame::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f04220baba3 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f0422d6bf82 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f04220bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f0422da6e59 in QWidgetPrivate::sendPaintEvent(QRegion const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f0422da7751 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags, QPainter*, QWidgetRepaintManager*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f0422d7d421 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f0422daeee8 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7f0423ab0e4d in KXmlGuiWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #27 0x7f0422d6bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7f04220bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7f04220bdea1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x7f04230a9193 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7f04220e7de0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7f0422d6bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #33 0x7f04220bae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7f04220bdea1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x7f04221157b7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #36 0x7f04201b049d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #37 0x7f042020b178 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #38 0x7f04201af1b0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #39 0x7f0422114e7a in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #40 0x7f04220b97cb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #41 0x7f04220c1c1a in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #42
[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3
https://bugs.kde.org/show_bug.cgi?id=401088 --- Comment #42 from Chris --- Created attachment 158988 --> https://bugs.kde.org/attachment.cgi?id=158988=edit Three file systems not responding. Three file systems not responding, '/', '/home/', '/home/backup/' -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3
https://bugs.kde.org/show_bug.cgi?id=401088 --- Comment #41 from Chris --- Created attachment 158987 --> https://bugs.kde.org/attachment.cgi?id=158987=edit Two mount points. Today's file system not responding '/' and '/home/backup/' -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401088] "Filesystem mounted at '/' is not responding" notification on log in to Plasma 5.14.3
https://bugs.kde.org/show_bug.cgi?id=401088 Chris changed: What|Removed |Added CC||chrisret...@gmx.com --- Comment #40 from Chris --- Operating System: Slackware64-current KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.1.28 (64-bit) Drives: Local Storage: total: 1.82 TiB used: 1.13 TiB (62.3%) ID-1: /dev/sda vendor: Western Digital model: WD10EZEX-22MFCA0 size: 931.51 GiB ID-2: /dev/sdb vendor: Western Digital model: WD10EZRX-00D8PB0 size: 931.51 GiB I have this problem. Not just with '/' but also with '/home/' and 'home/backup/' Filesystem Type Size Used Avail Use% Mounted on /dev/sda1 ext4 92G 40G 47G 46% / /dev/sda3 ext4 818G 499G 278G 65% /home /dev/sdb1 ext4 917G 623G 248G 72% /home/backup Today for example, it was just '/' and '/home/backup/'. I start my computer to runlevel 3 (CLI) and start KDE Plasma with startx. I do not use a GUI login. In one instance all the of the mounted locations came up. The system runs just fine, no issues. The 'df' command is fast real0m0.012s user0m0.007s sys 0m0.006s I will attach two screen shots, one showing today's, one showing all three mounts -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 466797] Problem connecting to calendar and contact with CalDAV protocol (in addition to problems with WebDAV and CardDAV)
https://bugs.kde.org/show_bug.cgi?id=466797 Chris changed: What|Removed |Added CC||junkspamwastema...@gmail.co ||m --- Comment #1 from Chris --- Comment on attachment 156979 --> https://bugs.kde.org/attachment.cgi?id=156979 Server access configuration & Result of an attempt to connect to a CalDAV server Hello, Following the exact steps described by Troupal, I encounter a similar error : "There was a problem with the request. HTTP error (405)." This error occurs in Akonadi, KOrganizer, KMail, Kontact, etc. (for both CalDAV and CardDAV). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 469084] New: System Settings crashes on import of OpenVPN configuration file .ovpn
https://bugs.kde.org/show_bug.cgi?id=469084 Bug ID: 469084 Summary: System Settings crashes on import of OpenVPN configuration file .ovpn Classification: Applications Product: systemsettings Version: 5.27.2 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ch...@theduncans.us Target Milestone: --- Application: systemsettings (5.27.2) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-7-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: OpenVPN configuration file is from ExpressVPN. Successive attempts to import the file crash every time. Separately installed packages openvpn and network-manager-openvpn with no change. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7ffa6d03b6ae in OpenVpnUiPlugin::importConnectionSettings(QString const&) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/network/vpn/plasmanetworkmanagement_openvpnui.so #5 0x7ffa82083972 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/kcms/systemsettings_qwidgets/kcm_networkmanagement.so #6 0x7ffac3ee8f7c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7ffac1a6eb78 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7ffac1ac6c93 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7ffac19a3521 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7ffac19a53e0 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #11 0x7ffac19c1cb6 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x7ffac19c53df in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x7ffac1957c2e in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #14 0x7ffac1ae144d in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #15 0x7ffac1a92baf in QQmlBoundSignalExpression::evaluate(void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #16 0x7ffac1a942f8 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #17 0x7ffac1ac677f in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #18 0x7ffac3ee8a8d in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7ffac1a6eb78 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #20 0x7ffac1ac6c93 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #21 0x7ffac19a3521 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #22 0x7ffac19a53e0 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #23 0x7ffac19c1cb6 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #24 0x7ffac19c53df in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #25 0x7ffac1957c2e in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #26 0x7ffac1ae144d in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #27 0x7ffac1a92baf in QQmlBoundSignalExpression::evaluate(void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #28 0x7ffac1a942f8 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #29 0x7ffac1ac677f in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #30 0x7ffac3ee8a8d in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x7ffabf271221 in QQuickAbstractButtonPrivate::handleRelease(QPointF const&) () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #32 0x7ffabf290251 in QQuickControl::mouseReleaseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #33 0x7ffac20550e8 in QQuickItem::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #34 0x7ffac4b62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #35 0x7ffac3eb16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #36 0x7ffac20729da in QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #37 0x7ffac20740dd in QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () from
[kmymoney] [Bug 469019] New: Payees match on a blank field
https://bugs.kde.org/show_bug.cgi?id=469019 Bug ID: 469019 Summary: Payees match on a blank field Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: importer Assignee: kmymoney-de...@kde.org Reporter: developerch...@rebel.com.au Target Milestone: --- Created attachment 158453 --> https://bugs.kde.org/attachment.cgi?id=158453=edit shows badly matched payee "test" SUMMARY It is possible to have a blank string as the matching text on payees, when this happens any transaction matches the payee and therefore the transaction is incorrectly assigned to that payee. STEPS TO REPRODUCE 1. Create a payee 2. Set matching criteria to "Match on name below" 3. Leave the matching text field blank 4. Save the payee. 5. Import a number of transactions OBSERVED RESULT many of the imported transactions are assigned to the bad payee The attached image shows the payee "test" matching on multiple transactions each with a different actual payee EXPECTED RESULT An Error should occur when creating the payee preventing a blank matching field, also on import the payee match should be checked to ensure that the match is not occurring on a blank field SOFTWARE/OS VERSIONS Windows 10 Version 2009 (x86_64) KDE Frameworks Version: 5.99.0 -- You are receiving this mail because: You are watching all bug changes.
