[plasmashell] [Bug 475563] Panel disappears in Wayland
https://bugs.kde.org/show_bug.cgi?id=475563 --- Comment #4 from Matthias --- Hi Nate :-) Yes, the panel disappears and all the others stay alive. I suspected it might not crash, but I did lack the term to describe it otherwise. So what could be the issue for it disappearing? I will try to test to run the third party widget in a dedicated panel, it could take a while, though. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475729] New: plasma crash when closing notification message
https://bugs.kde.org/show_bug.cgi?id=475729 Bug ID: 475729 Summary: plasma crash when closing notification message 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: panayoto...@gmail.com 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-13-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: plasma crash when closing notification message. it happen several times per week. not to severe bug The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 1255 (plasmashell) UID: 1000 (panayotovip) GID: 1000 (panayotovip) Signal: 11 (SEGV) Timestamp: Tue 2023-10-17 09:53:26 EEST (45s 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 (panayotovip) Boot ID: b927a14f2a2942918a3c2be87b388cc4 Machine ID: 93b8132d78914146b529766d901bc920 Hostname: station Storage: /var/lib/systemd/coredump/core.plasmashell.1000.b927a14f2a2942918a3c2be87b388cc4.1255.169752560600.zst (present) Size on Disk: 41.3M Message: Process 1255 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.17-1~deb12u1.amd64 Module libudev.so.1 from deb systemd-252.17-1~deb12u1.amd64 Stack trace of thread 1255: #0 0x7f2ad92aec24 pthread_sigmask (libc.so.6 + 0x8fc24) #1 0x7f2ad925b1b9 sigprocmask (libc.so.6 + 0x3c1b9) #2 0x7f2adb8dce9b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4e9b) #3 0x7f2adb8ddb3e _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b3e) #4 0x7f2ad925afd0 n/a (libc.so.6 + 0x3bfd0) #5 0x7f2ada58a56b n/a (libQt5Widgets.so.5 + 0x18a56b) #6 0x7f2ada59b49b _ZN7QWidget12removeActionEP7QAction (libQt5Widgets.so.5 + 0x19b49b) #7 0x7f2a9dd8bf94 n/a (libplasmacomponentsplugin.so + 0xff94) #8 0x7f2ada562fae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fae) #9 0x7f2ad96b16f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8) #10 0x7f2ad96e6b07 _ZN14QObjectPrivate16setParent_helperEP7QObject (libQt5Core.so.5 + 0x2e6b07) #11 0x7f2ad96e7083 _ZN7QObjectD2Ev (libQt5Core.so.5 + 0x2e7083) #12 0x7f2a9dd88ac6 n/a (libplasmacomponentsplugin.so + 0xcac6) #13 0x7f2ad96dd4bf _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2dd4bf) #14 0x7f2ada562fae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fae) #15 0x7f2ad96b16f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8) #16 0x7f2ad96b4681 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b4681) #17 0x7f2ad970a153 n/a (libQt5Core.so.5 + 0x30a153) #18 0x7f2ad81017a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9) #19 0x7f2ad8101a38 n/a (libglib-2.0.so.0 + 0x54a38) #20 0x7f2ad8101acc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #21 0x7f2ad9709836 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x309836) #22 0x7f2ad96b017b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b017b) #23 0x7f2ad96b82d6 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2b82d6) #24 0x560388dcbdc3 n/a (plasmashell + 0x26dc3) #25 0x7f2ad92461ca n/a (libc.so.6 + 0x271ca) #26 0x7f2ad9246285 __libc_start_main (libc.so.6 + 0x27285) #27 0x560388dcbee1 n/a (plasmashell + 0x26ee1) Stack trace of thread 1287: #0 0x7f2ad931b05f __poll (libc.so.6 + 0xfc05f) #1 0x7f2ad81019ae n/a (libglib-2.0.so.0 + 0x5
[frameworks-baloo] [Bug 475730] New: Software crased
https://bugs.kde.org/show_bug.cgi?id=475730 Bug ID: 475730 Summary: Software crased Classification: Frameworks and Libraries Product: frameworks-baloo Version: 5.110.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: harveyr...@gmail.com Target Milestone: --- Application: baloo_file_extractor (5.110.0) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 6.5.6-200.fc38.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 38 (KDE Plasma) DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: It automatically crashed when I logged in. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation fault [KCrash Handler] #4 0x7fcd86a81cfa in QVector::realloc(int, QFlags) () from /lib64/libQt5Gui.so.5 #5 0x7fcd86a82199 in QVector::resize(int) () from /lib64/libQt5Gui.so.5 #6 0x7fcd86a7aa8c in QTextHtmlParser::newNode(int) () from /lib64/libQt5Gui.so.5 #7 0x7fcd86a803fe in QTextHtmlParser::parseTag() () from /lib64/libQt5Gui.so.5 #8 0x7fcd86a809a8 in QTextHtmlParser::parse() () from /lib64/libQt5Gui.so.5 #9 0x7fcd86aa5b02 in QTextHtmlImporter::QTextHtmlImporter(QTextDocument*, QString const&, QTextHtmlImporter::ImportMode, QTextDocument const*) () from /lib64/libQt5Gui.so.5 #10 0x7fcd86a62de8 in QTextDocument::setHtml(QString const&) () from /lib64/libQt5Gui.so.5 #11 0x7fcd743215b9 in KFileMetaData::MobiExtractor::extract(KFileMetaData::ExtractionResult*) () from /usr/lib64/qt5/plugins/kf5/kfilemetadata/kfilemetadata_mobiextractor.so #12 0x55d3c43ad1b8 in Baloo::App::index(Baloo::Transaction*, QString const&, unsigned long long) () #13 0x55d3c43aef84 in Baloo::App::processNextFile() () #14 0x7fcd864eba9a in QSingleShotTimer::timerEvent(QTimerEvent*) () from /lib64/libQt5Core.so.5 #15 0x7fcd864decab in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #16 0x7fcd864b41a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #17 0x7fcd86505a9b in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #18 0x7fcd865063d1 in idleTimerSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #19 0x7fcd84f134fc in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #20 0x7fcd84f716b8 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #21 0x7fcd84f10b83 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #22 0x7fcd86506749 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #23 0x7fcd864b2b6b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #24 0x7fcd864badfb in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #25 0x55d3c43a505b in main () [Inferior 1 (process 2286) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475653] Primary monitor is switched when coming back from suspend/rebooting
https://bugs.kde.org/show_bug.cgi?id=475653 --- Comment #2 from James North --- I am able to reliably reproduce this display shuffling bug whenever resuming from suspend. (In reply to Michael Butash from comment #1) > Every time my displays change, KDE chooses random ID's for them (DP-1, DP-3, > DP-5), and it wreaks havoc on things. I suspect yours might be similar. > Until someone makes wayland far more deterministic around display ID's, I > suspect kde will remain a basketcase for multi-monitor. Where are you seeing these IDs? I couldn't find anything in plasmashellrc. > After a while, I find KDE builds like 50 different display configs for them > each time it changes randomly, which seems to just confuse the hell out of > things. Per Nate Graham, clearing them fixed things, but they start building > up with the shuffling again over time, and each time clearing them makes my > life better since learning this, which I've done periodically over a bit > since figuring this out. You probably should as well with hot plugging your > second display probably causes similar. Where do I find these display configs to clear out? By "hot plugging", do you mean unplugging the monitor while the system is running? Because these monitors are permanently plugged in. For some reason, my graphics tablet is usually detected as the main monitor by Linux-based systems by default (I don't know about other operating systems). The Arch Linux install media reliably detected my graphics tablet as the main monitor and formatted the console as 1920x1080, leaving a very large space on my 4K monitor completely black. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 475730] Software crased
https://bugs.kde.org/show_bug.cgi?id=475730 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org --- Comment #1 from tagwer...@innerjoin.org --- (In reply to harveyrasp from comment #0) > #11 0x7fcd743215b9 in > KFileMetaData::MobiExtractor::extract(KFileMetaData::ExtractionResult*) () > from /usr/lib64/qt5/plugins/kf5/kfilemetadata/kfilemetadata_mobiextractor.so Looks as if baloo is stumbling over an e-book, when trying to extract the text from a Mobi... You might get a hint if you run "balooctl monitor", it should list the files as baloo_file_extractor indexes them. If one file keeps reappearing, move it out the way and see what happens (I tend to gzip files to do this, it's easy to gunzip them afterwards. You don't have to remember what you moved out the way and where you have to move it back to 8-) -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 474353] bluetooth context not restored when switching betwin to users
https://bugs.kde.org/show_bug.cgi?id=474353 Philippe ROUBACH changed: What|Removed |Added Summary|bluetooth context disapears |bluetooth context not |when switching to another |restored when switching |user|betwin to users --- Comment #3 from Philippe ROUBACH --- Exact summary Two users get simultaneous opened kde session on the same PC. Bluetooth context not restored when switching between to users -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 460077] PC does not connect automatically to a device when opening kde session
https://bugs.kde.org/show_bug.cgi?id=460077 --- Comment #3 from Philippe ROUBACH --- Hello After no context restoration problem for about one or two months, again when opening a kde session then bluetooth is activated but the connection to my speaker is not restored. Last days there were an update to kde gears 23.08.2 and to qt6 6.6 . -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 460077] PC does not connect automatically to a device when opening kde session
https://bugs.kde.org/show_bug.cgi?id=460077 --- Comment #4 from Philippe ROUBACH --- sorry i forgot Operating System: openSUSE Tumbleweed 20231013 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 kde gears 23.08.2 -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 474353] bluetooth context not restored when switching betwin two users
https://bugs.kde.org/show_bug.cgi?id=474353 Philippe ROUBACH changed: What|Removed |Added Summary|bluetooth context not |bluetooth context not |restored when switching |restored when switching |betwin to users |betwin two users -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 475695] baloo_file_extractor crash on login
https://bugs.kde.org/show_bug.cgi?id=475695 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org --- Comment #5 from tagwer...@innerjoin.org --- You could try Igor Poboiko's baloo-checkdb.py "consistency check" script: https://invent.kde.org/frameworks/baloo/uploads/bdc9f5f17fc96490b7bd4a22ac664843/baloo-checkdb.py There's a quick description here: https://invent.kde.org/frameworks/baloo/-/merge_requests/87#note_535270 Heads up about the need to load the whole database into memory. It waves a flag about possible corruptions, doesn't try to fix them. Sorry, I don't a step by step install instructions for Gentoo... -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 475400] Update and download denied when it should be allowed (connectivity problem)
https://bugs.kde.org/show_bug.cgi?id=475400 --- Comment #13 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/multimedia/kasts/-/merge_requests/139 -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 475400] Update and download denied when it should be allowed (connectivity problem)
https://bugs.kde.org/show_bug.cgi?id=475400 b...@mogwai.be changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #14 from b...@mogwai.be --- (In reply to maizjoris from comment #12) > Ok, I will try. Let me know once the source is ready. The implementation is available as MR at https://invent.kde.org/multimedia/kasts/-/merge_requests/139 Or you can directly retrieve it through the git branch "work/rip-out-connectivity-check" -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 475731] New: Dolphin crashes just after paste and immediately try to open such file
https://bugs.kde.org/show_bug.cgi?id=475731 Bug ID: 475731 Summary: Dolphin crashes just after paste and immediately try to open such file Classification: Applications Product: dolphin Version: 22.12.3 Platform: Kubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: lltre...@hotmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.0-34-generic x86_64 Windowing System: X11 Distribution: Ubuntu 23.04 DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: I just copy and paste a single file on a directory, then almost immediately I tried to open such file (it was a libreoffice file), and I face the crash The crash does not seem to be reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f425469d5d4 in KFileItem::KFileItem(KFileItem const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #5 0x7f425475aefb in ?? () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #6 0x7f425475d58b in ?? () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #7 0x7f4254759271 in ?? () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #8 0x7f4252af39af in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f4253ee6a09 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #10 0x7f4253eec97b in KJob::finishJob(bool) () from /lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #11 0x7f4252af39af in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f42546e4d93 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #13 0x7f42546e33ca in KIO::SlaveInterface::dispatch() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #14 0x7f42546e81c1 in KIO::Slave::gotInput() () from /lib/x86_64-linux-gnu/libKF5KIOCore.so.5 #15 0x7f4252af39af in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f4252ae7de0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f425376bf92 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f4252abae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f4252abdea1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f4252b157b7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f425086149d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f42508bc178 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f42508601b0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f4252b14e7a in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f4252ab97cb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x7f4252ac1c1a in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x55da2c9db56a in ?? () #28 0x7f4252023a90 in __libc_start_call_main (main=main@entry=0x55da2c9d8c40, argc=argc@entry=1, argv=argv@entry=0x7ffc13272c88) at ../sysdeps/nptl/libc_start_call_main.h:58 #29 0x7f4252023b49 in __libc_start_main_impl (main=0x55da2c9d8c40, argc=1, argv=0x7ffc13272c88, init=, fini=, rtld_fini=, stack_end=0x7ffc13272c78) at ../csu/libc-start.c:360 #30 0x55da2c9dbc65 in ?? () [Inferior 1 (process 33363) detached] The reporter indicates this bug may be a duplicate of or related to bug 467985. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475318] Often unable to open application menu, access taskbar, or switch away from window coerced into full screen mode using "apply initially" Window Rule
https://bugs.kde.org/show_bug.cgi?id=475318 --- Comment #11 from Stephane Travostino --- I don't have access to KDE for a while, but as I mentioned previously, it's not strictly related to window rules: it happened in the game Darkwood which was set fullscreen from the game options. So the original title was correct: this issue happens on fullscreen window, whether they're forced with window rules, or through in-app methods. And it is sporadic as I mentioned. Very empirically, immediately after starting the app the issue doesn't present, but after a while (minutes) pressing Win or Alt-Tab switches away for a split second before returning to the application. It takes a dozen tries to be able to switch away this way, and then everything is fine until it breaks again. It feels like there's a race between the window and Plasma to get focus, and 9 times out of 10 the app wins. On Mon, 16 Oct 2023, at 19:48, Ismael Asensio wrote: > https://bugs.kde.org/show_bug.cgi?id=475318 > > --- Comment #10 from Ismael Asensio --- > Unfortunately trying to run RuneLite crashes my (admitedly flaky currently) > dev > kwin instance. > > However I could reproduce it sporadically with supertuxkart \o/, simply by > turning it fullscreen via the window menu. > > Stephane, can you try to reproduce the issue without setting the rule on > RuneLite, but via the window menu (Alt+F3 -> More Actions -> Fullscreen)? This > can help to better pinpoint the scope of the bug. > > Thanks!! > > -- > You are receiving this mail because: > You reported the bug. -- 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.
[digikam] [Bug 471269] Application crashes when album contains avif file
https://bugs.kde.org/show_bug.cgi?id=471269 --- Comment #10 from caulier.gil...@gmail.com --- Strange. The patch from Maik is now applied the the last Windows build and libaom have been also updated. Maik, perhaps it miss some optional dependencies to libaom ? https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_libaom/CMakeLists.txt?ref_type=heads List of build options from aommedia from git/master: ENABLE_ARM_CRC32:BOOL=ON ENABLE_AVX:BOOL=ON ENABLE_AVX2:BOOL=ON ENABLE_CCACHE:BOOL=OFF ENABLE_DECODE_PERF_TESTS:BOOL=OFF ENABLE_DISTCC:BOOL=OFF ENABLE_DOCS:BOOL=ON ENABLE_ENCODE_PERF_TESTS:BOOL=OFF ENABLE_EXAMPLES:BOOL=ON ENABLE_GOMA:BOOL=OFF ENABLE_IDE_TEST_HOSTING:BOOL=OFF ENABLE_MMX:BOOL=ON ENABLE_NASM:BOOL=OFF ENABLE_NEON:BOOL=ON ENABLE_NEON_DOTPROD:BOOL=ON ENABLE_NEON_I8MM:BOOL=ON ENABLE_SSE:BOOL=ON ENABLE_SSE2:BOOL=ON ENABLE_SSE3:BOOL=ON ENABLE_SSE4_1:BOOL=ON ENABLE_SSE4_2:BOOL=ON ENABLE_SSSE3:BOOL=ON ENABLE_SVE:BOOL=ON ENABLE_TESTDATA:BOOL=ON ENABLE_TESTS:BOOL=ON ENABLE_TOOLS:BOOL=ON ENABLE_VSX:BOOL=ON ENABLE_WERROR:BOOL=OFF Gilles -- 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.
[plasmashell] [Bug 465441] plasmashell leaks memory after each resume (currently around 23 GB) [with heaptrack] in plasmadesktoptheme.cpp:231
https://bugs.kde.org/show_bug.cgi?id=465441 H.H. changed: What|Removed |Added CC||cyberb...@gmx.de -- 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 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 471269] Application crashes when album contains avif file
https://bugs.kde.org/show_bug.cgi?id=471269 --- Comment #11 from Maik Qualmann --- The main problem is that I cannot reproduce the crash on 3 different Windows (AMD/Intel) computers. The library does not use GPU acceleration. So it can only be due to some SSE options. Maik -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 472328] Rendering a video gets stuck on waiting
https://bugs.kde.org/show_bug.cgi?id=472328
Andrey changed:
What|Removed |Added
CC||meges...@efenstor.net
--- Comment #1 from Andrey ---
I have this behaviour in the version 23.08.2, though may be it's a different
bug. The problem is present in BOTH the AppImage and the Flatpak release.
Additional info:
1. The problem is present only when using proxies. Codec used for proxies (H264
or MJPEG) does not matter.
2. Although rendering seems to be stuck in the preparation phase for a very
long time the project is eventually rendered fine.
3. There are no useful messages displayed in the terminal during the wait. When
using gdb there are only several "Thread [...] exited" messages and nothing
else.
3. Rendering can be immediately aborted during the wait, the message "QProcess:
Destroyed while process ("/app/bin/melt") is still running" is displayed in the
terminal (with gdb).
4. The more proxified clips are in the project the longer is the wait. On my
system (Ryzen 7 2700 Eight-Core) it is about 1min 30sec for 50 clips.
5. Number of clips used in the timeline has no matter, only the total number of
clips with proxies in the project bin matters.
For me everything points to a bug in MLT.
--
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 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 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 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.
[krita] [Bug 474679] Krita fails to render animations that don't have starting frame as 0
https://bugs.kde.org/show_bug.cgi?id=474679 Dmitry Kazakov changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED Assignee|krita-bugs-n...@kde.org |dimul...@gmail.com --- Comment #17 from Dmitry Kazakov --- Okay, I have the testing file on my email, so I will look into that. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474606] Keyboard input doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=474606 Teemu Rytilahti changed: What|Removed |Added CC||t...@iki.fi --- Comment #13 from Teemu Rytilahti --- I am experiencing the very same issue, some notes: * I am also running a setup which has carried the $HOME over for a long time. * Log has the same keycode clipping warning, but also a couple of `unrecognized keysym`s. * Some inputs are working fine, like changing virtual consoles to access other ttys and alt+tab, `libinput debug-events` receives keys. * Screen locker works as expected and receives keys, verified that it was running (according to env variables) on Wayland, too. * Most notably, everything is working as expected when using a clean user! I'm not sure where to go look for the potential cause, so let me know if I you want me to try something out. I have a couple of keyboard related settings, like this custom ~/.Xmodmap file: ``` keycode 34 = udiaeresis Udiaeresis keycode 57 = n N n N ntilde Ntilde ``` and this $HOME/.config/kxkbrc: ``` [$Version] update_info=kxkb_variants.upd:split-variants,kxkb.upd:remove-empty-lists,kxkb.upd:add-back-resetoptions [Layout] DisplayNames=,, LayoutList=fi,ru,ua LayoutLoopCount=-1 Model=pc105 Options=lv3:caps_switch ResetOldOptions=true ShowFlag=false ShowLabel=true ShowLayoutIndicator=true ShowSingle=false SwitchMode=Global Use=true VariantList=,phonetic,phonetic ``` Log: ``` systemd[1647]: Starting KDE Window Manager... systemd[1647]: Started KDE Window Manager. kwin_wayland[28065]: No backend specified, automatically choosing drm kwin_wayland[28065]: OpenGL vendor string: Intel kwin_wayland[28065]: OpenGL renderer string: Mesa Intel(R) UHD Graphics 620 (KBL GT2) kwin_wayland[28065]: OpenGL version string: 4.6 (Core Profile) Mesa 23.2.1-arch1.1 kwin_wayland[28065]: OpenGL shading language version string: 4.60 kwin_wayland[28065]: Driver: Intel kwin_wayland[28065]: GPU class: Kaby Lake kwin_wayland[28065]: OpenGL version: 4.6 kwin_wayland[28065]: GLSL version: 4.60 kwin_wayland[28065]: Mesa version: 23.2.1 kwin_wayland[28065]: Linux kernel version: 6.5.5 kwin_wayland[28065]: Requires strict binding:no kwin_wayland[28065]: GLSL shaders: yes kwin_wayland[28065]: Texture NPOT support: yes kwin_wayland[28065]: Virtual Machine:no kwin_wayland[28065]: kwin_core: Parse error in tiles configuration for monitor "28eb92d0-b82a-573c-9f71-b7d18e5fca24" : "illegal value" Creating default setup kwin_wayland[28065]: kwin_xkbcommon: XKB: inet:323:58: unrecognized keysym "XF86EmojiPicker" kwin_wayland[28065]: kwin_xkbcommon: XKB: inet:324:58: unrecognized keysym "XF86Dictate" kwin_wayland_wrapper[28122]: (WW) Option "-listen" for file descriptors is deprecated kwin_wayland_wrapper[28122]: Please use "-listenfd" instead. kwin_wayland_wrapper[28122]: (WW) Option "-listen" for file descriptors is deprecated kwin_wayland_wrapper[28122]: Please use "-listenfd" instead. kwin_wayland_wrapper[28163]: The XKEYBOARD keymap compiler (xkbcomp) reports: kwin_wayland_wrapper[28163]: > Warning: Unsupported maximum keycode 708, clipping. kwin_wayland_wrapper[28163]: > X11 cannot support keycodes above 255. kwin_wayland_wrapper[28163]: Errors from xkbcomp are not fatal to the X server kwin_wayland[28065]: OpenGL vendor string: Intel kwin_wayland[28065]: OpenGL renderer string: Mesa Intel(R) UHD Graphics 620 (KBL GT2) kwin_wayland[28065]: OpenGL version string: 4.6 (Core Profile) Mesa 23.2.1-arch1.1 kwin_wayland[28065]: OpenGL shading language version string: 4.60 kwin_wayland[28065]: Driver: Intel kwin_wayland[28065]: GPU class: Kaby Lake kwin_wayland[28065]: OpenGL version: 4.6 kwin_wayland[28065]: GLSL version: 4.60 kwin_wayland[28065]: Mesa version: 23.2.1 kwin_wayland[28065]: X server version: 1.23.2 kwin_wayland[28065]: Linux kernel version: 6.5.5 kwin_wayland[28065]: Requires strict binding:no kwin_wayland[28065]: GLSL shaders: yes kwin_wayland[28065]: Texture NPOT support: yes kwin_wayland[28065]: Virtual Machine:no kwin_wayland[28065]: BlurConfig::instance called after the first use - ignoring kwin_wayland[28065]: ZoomConfig::instance called after the first use - ignoring kwin_wayland[28065]: WindowViewConfig::instance called after the first use - ignoring kwin_way
[frameworks-kcoreaddons] [Bug 472862] plasmashell and kwin_wayland randomly crashed in KDirWatchPrivate::emitEvent() due to kate sessions
https://bugs.kde.org/show_bug.cgi?id=472862 --- Comment #17 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kcoreaddons/-/merge_requests/385 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446987] plasmashell crashes on launch in QWindow::screenChanged() with multiple screens connected
https://bugs.kde.org/show_bug.cgi?id=446987 --- Comment #14 from Yurii --- Any chance this will be fixed in Plasma 6? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475729] plasma crash when closing notification message
https://bugs.kde.org/show_bug.cgi?id=475729 Ivan Panayotov changed: What|Removed |Added CC||panayoto...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475729] plasma crash when closing notification message
https://bugs.kde.org/show_bug.cgi?id=475729 --- Comment #1 from Ivan Panayotov --- Created attachment 162368 --> https://bugs.kde.org/attachment.cgi?id=162368&action=edit New crash information added by DrKonqi plasmashell (5.27.5) using Qt 5.15.8 this crash appear when pc is turning on displays from sleep -- Backtrace (Reduced): #6 0x7f644ab9b49b in QWidget::removeAction(QAction*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #8 0x7f644ab62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f6449eb16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f6449ee6b07 in QObjectPrivate::setParent_helper(QObject*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f6449ee7083 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475721] KDE session doesn't start when attempting to login (applying kscreen config failed!)
https://bugs.kde.org/show_bug.cgi?id=475721 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Severity|critical|normal -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 475732] New: External tools does not show
https://bugs.kde.org/show_bug.cgi?id=475732 Bug ID: 475732 Summary: External tools does not show Classification: Applications Product: kate Version: 23.08.1 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: igorp.mail...@gmail.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. Remove all external tools 2. Add single one OBSERVED RESULT In menu, there is no single entry EXPECTED RESULT I should see my external tool entry in the menu SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION It worked, then stopped. Reinstalled and cleared all Local and Roaming data as well. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472901] Screen flickers when switching virtual desktop with touchpad gesture and animations are off
https://bugs.kde.org/show_bug.cgi?id=472901 Vlad Zahorodnii changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwin/-/commit/94b74cff96 |ma/kwin/-/commit/1c447b7cee |0566d42813ecf4847637c2283a6 |950e99761763c80c15e6e862b40 |fac |b4b --- Comment #4 from Vlad Zahorodnii --- Git commit 1c447b7cee950e99761763c80c15e6e862b40b4b by Vlad Zahorodnii, on behalf of Quinten Kock. Committed on 16/10/2023 at 19:07. Pushed by vladz into branch 'Plasma/5.27'. plugins/slide: add special case for instant animations In springmotion.cpp for the slide plugin, there are issues when animations are disabled, namely a black screen flicker. The flicker is caused by float under/overflow (div-by-0 -> infinity). This commit fixes that by special-casing an infinite spring constant, so that the animation immediately jumps to the anchor. (cherry picked from commit 94b74cff960566d42813ecf4847637c2283a6fac) M +10 -0src/effects/slide/springmotion.cpp https://invent.kde.org/plasma/kwin/-/commit/1c447b7cee950e99761763c80c15e6e862b40b4b -- You are receiving this mail because: You are watching all bug changes.
[isoimagewriter] [Bug 473925] Verify all images instead of only selected distro images
https://bugs.kde.org/show_bug.cgi?id=473925 --- Comment #2 from gudvinr+...@gmail.com --- Hard coding for limited set of images is a terrible solution. It's not sustainable simply because maintainers can switch to other verification methods at any time. Also has zero scalability because each and every change requires to rebuild an app. I am suggesting opposite of trying to find any kind of pattern across distro images simply because verification process has nothing to do with ISO and doesn't care about content of the file. And FILE verification (as opposed to ISO verification) more often than not follows quite strict rule since utils that produce hashes have pretty standard output format (sha256sum, md5sum, etc). So, there's no need to guess and if file with given pattern exist then use it. If it doesn't then allow user to provide some sort of signature. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461741] Panel in "Auto-hide" mode inappropriately un-hides after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=461741 --- Comment #7 from gudvinr+...@gmail.com --- Can't reproduce it since I don't daily drive wayland anymore. I guess issue can be closed and reopened if someone (myself included) will experience it in the future. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475200] File associations are inherited in the incorrect order
https://bugs.kde.org/show_bug.cgi?id=475200 David Redondo changed: What|Removed |Added CC||k...@david-redondo.de --- Comment #1 from David Redondo --- I think you are right. The spec says in the section about selecting an application "The above process is repeated for each mimetype from the most specific to the least specific. Note in particular that an application that can handle a more specific type will be used in preference to an application explicitly marked as the default for a less-specific type." In the example text/plain is more specific then octet-stream -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422682] "Show in Activities" item is missing in window menu
https://bugs.kde.org/show_bug.cgi?id=422682 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #37 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kactivitymanagerd/-/merge_requests/60 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 472862] plasmashell and kwin_wayland randomly crashed in KDirWatchPrivate::emitEvent() due to kate sessions
https://bugs.kde.org/show_bug.cgi?id=472862 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #18 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kdeplasma-addons/-/merge_requests/479 -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 190238] Provide a widget to view and change the "do not ask again" saved options
https://bugs.kde.org/show_bug.cgi?id=190238 kolAflash changed: What|Removed |Added CC||kolafl...@kolahilft.de --- Comment #7 from kolAflash --- In KDE/Plasma 5.27.5 on Debian-12 I still have a problem when opening entries in the applications: address in Dolphin. Can be workarounded via: systemsettings -> Applications -> File Associations -> application/x-desktop -> Application Preference Order -> Add /usr/bin/kioclient exec -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475733] New: Infinite loop in KWin::Placement::placeSmart() on new window
https://bugs.kde.org/show_bug.cgi?id=475733
Bug ID: 475733
Summary: Infinite loop in KWin::Placement::placeSmart() on new
window
Classification: Plasma
Product: kwin
Version: 5.27.8
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: thay...@noraisin.net
Target Milestone: ---
SUMMARY
Several times today, I've observed an infinite loop in
KWin::Placement::placeSmart() when opening a new application.
That leads to kwin_wayland becoming unresponsive until killed, in a 100% CPU
loop. I think this is the same root issue as bug #407221, but since that was
closed I thought better to file a new bug.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 38 with KDE 5.27.8
When it gets stuck, `KWin::Placement::placeSmart` is spinning in the overall
do/while loop:
`do { ... } while ((overlap != none) && (overlap != h_wrong) && (y <
area.bottom()));`
When it reaches the condition at the end of the loop, `y=1234` and area = `{xp
= 0, yp = 0, w = 2194.2857142857142, h = 1234.2857142857142}`
With the mismatch between integer y and fractional screen height, I think the
root cause is fractional scaling (I have a small 4k display and 175% scaling.
Backtrace:
(gdb) bt
#0 KWin::Placement::placeSmart(KWin::Window*, QRectF const&,
KWin::PlacementPolicy) (this=, area=..., window=)
at /usr/src/debug/kwin-5.27.8-1.fc38.x86_64/src/placement.cpp:201
#1 KWin::Placement::placeSmart(KWin::Window*, QRectF const&,
KWin::PlacementPolicy) (this=, window=, area=...)
at /usr/src/debug/kwin-5.27.8-1.fc38.x86_64/src/placement.cpp:159
#2 0x7f10dd566e0e in KWin::X11Window::manage(unsigned int, bool)
(this=0x5633e2e12eb0, w=, isMapped=false) at
/usr/src/debug/kwin-5.27.8-1.fc38.x86_64/src/x11window.cpp:757
#3 0x7f10dd546068 in KWin::Workspace::createX11Window(unsigned int, bool)
(this=0x5633e154d140, windowId=12582920, is_mapped=false) at
/usr/src/debug/kwin-5.27.8-1.fc38.x86_64/src/workspace.cpp:711
#4 0x7f10dd44c455 in KWin::Workspace::workspaceEvent(xcb_generic_event_t*)
(this=0x5633e154d140, e=0x5633e1bc0120) at
/usr/src/debug/kwin-5.27.8-1.fc38.x86_64/src/events.cpp:215
#5 0x7f10dbab123c in
QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) ()
at /lib64/libQt5Core.so.5
#6 0x5633e0a4c0d9 in
KWin::Xwl::Xwayland::dispatchEvents(KWin::Xwl::Xwayland::DispatchEventsMode) ()
#7 0x7f10dbae8481 in void doActivate(QObject*, int, void**) () at
/lib64/libQt5Core.so.5
#8 0x7f10dbaeae8d in QSocketNotifier::activated(QSocketDescriptor,
QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at
/lib64/libQt5Core.so.5
#9 0x7f10dbaeb6fb in QSocketNotifier::event(QEvent*) () at
/lib64/libQt5Core.so.5
#10 0x7f10db1aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#11 0x7f10dbab41a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#12 0x7f10dbb037ff in
QEventDispatcherUNIXPrivate::activateSocketNotifiers() () at
/lib64/libQt5Core.so.5
#13 0x7f10dbb03b80 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#14 0x5633e0b199c2 in
QUnixEventDispatcherQPA::processEvents(QFlags)
()
#15 0x7f10dbab2b6b in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#16 0x7f10dbabadfb in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#17 0x5633e0a32e44 in main ()
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 475734] New: Build system tries to install breeze-text.s to /usr when CMAKE_INSTALL_PREFIX is set to something else
https://bugs.kde.org/show_bug.cgi?id=475734 Bug ID: 475734 Summary: Build system tries to install breeze-text.s to /usr when CMAKE_INSTALL_PREFIX is set to something else Classification: Plasma Product: Breeze Version: 5.27.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plymouth Assignee: plasma-b...@kde.org Reporter: n...@kde.org CC: sit...@kde.org Target Milestone: --- Which of course does not work when building this repo using kdesrc-build: <<< PACKAGES FAILED TO BUILD >>> breeze-plymouth - file:///home/nate/kde/src/log/2023-10-17-02/breeze-plymouth/install.log * Installing "sample-kde-env-master.sh" would overwrite an existing file: * /home/nate/.config/kde-env-master.sh * If this is acceptable, please delete the existing file and re-run, * or pass --delete-my-settings and re-run. :-( Your logs are saved in file:///home/nate/kde/src/log/2023-10-17-02 # kdesrc-build running: 'gmake' 'install/fast' # from directory: /home/nate/kde/build6/breeze-plymouth Install the project... -- Install configuration: "RelWithDebInfo" -- Installing: /usr/lib64/plymouth/breeze-text.so CMake Error at breeze-text/cmake_install.cmake:60 (file): file INSTALL cannot copy file "/home/nate/kde/build6/breeze-plymouth/breeze-text/breeze-text.so" to "/usr/lib64/plymouth/breeze-text.so": Permission denied. Call Stack (most recent call first): cmake_install.cmake:47 (include) My CMake environment: > BACKGROUND_BOTTOM_COLOR black > BACKGROUND_TOP_COLOR black > CMAKE_BUILD_TYPE RelWithDebInfo > CMAKE_EXPORT_COMPILE_COMMANDSON > CMAKE_INSTALL_PREFIX /home/nate/kde/usr6 > DISTRO_LOGO plasma > DISTRO_NAME Fedora Linux 38 (KDE Plasma) > DISTRO_VERSION > ECM_DIR /home/nate/kde/usr6/share/ECM/cmake > INSTALL_BROKEN_PLYMOUTH_DATA OFF > KDE_CHECK_JSONSCHEMA_EXECUTABL KDE_CHECK_JSONSCHEMA_EXECUTABLE-NOTFOUND > KDE_CLANG_FORMAT_EXECUTABLE /usr/bin/clang-format > MATH_LIBRARY /usr/lib64/libm.so -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472901] Screen flickers when switching virtual desktop with touchpad gesture and animations are off
https://bugs.kde.org/show_bug.cgi?id=472901 Quinten Kock changed: What|Removed |Added Version Fixed In||5.27.9 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461741] Panel in "Auto-hide" mode inappropriately un-hides after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=461741 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #8 from Nate Graham --- Ok, feel free to re-open this if and when you encounter the issue on Wayland again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 461741] On Wayland, panel in "Auto-hide" mode inappropriately un-hides after unlocking screen
https://bugs.kde.org/show_bug.cgi?id=461741 Nate Graham changed: What|Removed |Added Summary|Panel in "Auto-hide" mode |On Wayland, panel in |inappropriately un-hides|"Auto-hide" mode |after unlocking screen |inappropriately un-hides ||after unlocking screen Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 426624] General log file for data sources
https://bugs.kde.org/show_bug.cgi?id=426624 Robby Stephenson changed: What|Removed |Added Version Fixed In||4.0 Latest Commit||https://invent.kde.org/offi ||ce/tellico/-/commit/18a131e ||66175f57f460ce0f5d2d186dd49 ||deced5 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Robby Stephenson --- Git commit 18a131e66175f57f460ce0f5d2d186dd49deced5 by Robby Stephenson. Committed on 17/10/2023 at 14:47. Pushed by rstephenson into branch 'master'. Add menu item to show the log file, if exists FIXED-IN: 4.0 M +7-14 src/core/filehandler.cpp M +4-0src/core/logger.cpp M +1-0src/core/logger.h M +8-5src/document.cpp M +7-6src/main.cpp M +48 -1src/mainwindow.cpp M +2-1src/mainwindow.h M +10 -7src/tellicoui.rc https://invent.kde.org/office/tellico/-/commit/18a131e66175f57f460ce0f5d2d186dd49deced5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 475659] Selection for ISO integration is missing in the Dolphin menu after the update
https://bugs.kde.org/show_bug.cgi?id=475659 --- Comment #6 from joekamprad --- https://invent.kde.org/sdk/dolphin-plugins/-/merge_requests/42/diffs pull request -- You are receiving this mail because: You are watching all bug changes.
[kasts] [Bug 475400] Update and download denied when it should be allowed (connectivity problem)
https://bugs.kde.org/show_bug.cgi?id=475400 --- Comment #15 from b...@mogwai.be --- Git commit ea5d01043d01a8d5ecdcf81ef30d3313361c8ad4 by Bart De Vries. Committed on 17/10/2023 at 09:36. Pushed by bdevries into branch 'release/23.08'. Remove network connectivity check Apparently in some cases the network manager is incorrectly signaling that the system is offline while it's actually online. The current implementation does not have a way to circumvent that incorrect reporting. Also the error reporting made it seem that the actual problem is a metered connection. Ripping out the connectivity check solves these issues at the expense of connections timing out rather than the connection not being set up in the first place when the system is offline. M +8-16 src/networkconnectionmanager.cpp https://invent.kde.org/multimedia/kasts/-/commit/ea5d01043d01a8d5ecdcf81ef30d3313361c8ad4 -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 475735] New: kdevelop : wizard does not create new classes
https://bugs.kde.org/show_bug.cgi?id=475735 Bug ID: 475735 Summary: kdevelop : wizard does not create new classes Classification: Developer tools Product: kdevplatform Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: appwizard Assignee: kdevelop-bugs-n...@kde.org Reporter: nm...@yandex.com Target Milestone: --- Hi, The new 'class wizard' in kdevelop creates empty and unsaved files. The preview in the first page of the wizard is empty also. Since: Version 5.12.230802 (23.08.2) Running on: Operating System: Arch Linux KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 Kernel Version: 6.5.7-arch1-1 (64-bit) Graphics Platform: X11 This is observed on 2 machines. Please note it's not about the 'new app wizard'. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kdevplatform] [Bug 475735] kdevelop : wizard does not create new classes
https://bugs.kde.org/show_bug.cgi?id=475735 nmset changed: What|Removed |Added CC||nm...@yandex.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 475004] Tab Context Menu (Open on device) missing
https://bugs.kde.org/show_bug.cgi?id=475004 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 475695] baloo_file_extractor crash on login
https://bugs.kde.org/show_bug.cgi?id=475695 --- Comment #6 from Zack Weinberg --- $ python3 dl/baloo-checkdb.py .local/share/baloo.bad/index Loading DB from .local/share/baloo.bad/index... Traceback (most recent call last): File "/home/zack/dl/baloo-checkdb.py", line 265, in db.check() File "/home/zack/dl/baloo-checkdb.py", line 235, in check self.load_all() File "/home/zack/dl/baloo-checkdb.py", line 52, in load_all self._load_posting() File "/home/zack/dl/baloo-checkdb.py", line 87, in _load_posting for (key, value) in txn.cursor(): lmdb.PageNotFoundError: mdb_cursor_get: MDB_PAGE_NOTFOUND: Requested page not found -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 474565] Crash upon hitting open file limit
https://bugs.kde.org/show_bug.cgi?id=474565 farid changed: What|Removed |Added CC||snd.no...@gmail.com --- Comment #4 from farid --- (In reply to jackleberry from comment #2) > I tried with git today's git master and experienced the same thing. kdenlive > crashes unless the open file limit is increased. There are 476 clips in the > project, and the default open file limit is 1000. But did you try using MLT master as well? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 474565] Crash upon hitting open file limit
https://bugs.kde.org/show_bug.cgi?id=474565 --- Comment #5 from farid --- Could you try to reproduce this with the AppImage? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 475601] Segfault after loading project
https://bugs.kde.org/show_bug.cgi?id=475601 farid changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||snd.no...@gmail.com Status|REPORTED|NEEDSINFO --- Comment #1 from farid --- This might be a bad packaging issue. Are you able to reproduce this using the latest appimage? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 475734] Build system tries to install breeze-text.s to /usr when CMAKE_INSTALL_PREFIX is set to something else
https://bugs.kde.org/show_bug.cgi?id=475734 --- Comment #1 from Harald Sitter --- It's been this way since forever? You have to build with INSTALL_BROKEN_PLYMOUTH_DATA=ON -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420280] Google authentication process gets stuck due to excessively old version of signon-ui library
https://bugs.kde.org/show_bug.cgi?id=420280 --- Comment #92 from Gilberto Ferreira --- Well well well... I wonder why it's works pretty well in Gnome, Xfce and Cinnamon. Right now I am using Ubuntu Cinnamon and signon-ui-whatever works as expected. It's seems only in KDE Plasma doesn't work. Sadly! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429963] digiKam hangs when adding people or cleaning the DB
https://bugs.kde.org/show_bug.cgi?id=429963 --- Comment #24 from caulier.gil...@gmail.com --- It's a Q of course... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475736] New: PWA chrome applications being grouped under chrome icon
https://bugs.kde.org/show_bug.cgi?id=475736 Bug ID: 475736 Summary: PWA chrome applications being grouped under chrome icon Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sombr...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY some Progressive Web Apps gets under chrome icon instead it's own icon. STEPS TO REPRODUCE 1. install google chrome 2. get some progressive web apps 3. pin them to the bar 4. open chrome fist and then you pinned pwa app 5. app gets grouped with chrome. OBSERVED RESULT applications with different icons grouped under chrome icon EXPECTED RESULT each app grouped in its own icon, no matter if it's PWA SOFTWARE/OS VERSIONS Linux: openSUSE Tumbleweed 6.5.6-1-default (64-bit) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION running a wayland session -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420280] Google authentication process gets stuck due to excessively old version of signon-ui library
https://bugs.kde.org/show_bug.cgi?id=420280 --- Comment #94 from Gilberto Ferreira --- (In reply to Dipta Biswas from comment #93) > (In reply to Gilberto Ferreira from comment #92) > > Well well well... > > I wonder why it's works pretty well in Gnome, Xfce and Cinnamon. > > Right now I am using Ubuntu Cinnamon and signon-ui-whatever works as > > expected. > > It's seems only in KDE Plasma doesn't work. > > Sadly! > > GNOME & Cinnamon use gnome-online-accounts, not signon-ui Ok! Did know that. But, anyway, the question remain! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475737] New: Exporting CMYK32 to PNG leaves vertical lines
https://bugs.kde.org/show_bug.cgi?id=475737 Bug ID: 475737 Summary: Exporting CMYK32 to PNG leaves vertical lines Classification: Applications Product: krita Version: 5.2.0 Platform: Other OS: Other Status: REPORTED Keywords: regression Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: penguinflyer2...@gmail.com Target Milestone: --- SUMMARY As reported on KA (https://krita-artists.org/t/on-export-to-png-blue-areas-now-have-thin-vertical-purple-lines/76230), exporting CMYK32 to PNG leaves discolored vertical lines at intervals. This happens on 5.2.0, but not 5.1.5. It appears to have been caused by commit e152f99c12 (https://invent.kde.org/graphics/krita/-/commit/e152f99c12). STEPS TO REPRODUCE 1. Create a CMYK32 image with a whitish background, draw some blue scribbles. 2. Export to PNG. OBSERVED RESULT Purple lines, and a blueish background. EXPECTED RESULT To look the same as in Krita- with no lines and a whitish background. SOFTWARE/OS VERSIONS Krita 5.2.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 463197] UI frequently locks up / unresponsive with large collection
https://bugs.kde.org/show_bug.cgi?id=463197 --- Comment #17 from Metal450 --- (In reply to Peter from comment #16) > A search interrupt button would be nice. A button wouldn't do anything if the UI thread is already locked up & not processing user inputs. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475738] New: Find Action shortcut doesn't work in krita
https://bugs.kde.org/show_bug.cgi?id=475738 Bug ID: 475738 Summary: Find Action shortcut doesn't work in krita Classification: Applications Product: krita Version: 5.2.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: saileshpoud...@gmail.com Target Milestone: --- SUMMARY ctrl + alt + I , should search all actions in menus but doesn't seem to work with krita. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 Kernel Version: 6.5.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-9300H CPU @ 2.40GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 Manufacturer: Dell Inc. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420280] Google authentication process gets stuck due to excessively old version of signon-ui library
https://bugs.kde.org/show_bug.cgi?id=420280 --- Comment #93 from Dipta Biswas --- (In reply to Gilberto Ferreira from comment #92) > Well well well... > I wonder why it's works pretty well in Gnome, Xfce and Cinnamon. > Right now I am using Ubuntu Cinnamon and signon-ui-whatever works as > expected. > It's seems only in KDE Plasma doesn't work. > Sadly! GNOME & Cinnamon use gnome-online-accounts, not signon-ui -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475739] New: Plasma crashes after changing audio profile in pavucontrol
https://bugs.kde.org/show_bug.cgi?id=475739 Bug ID: 475739 Summary: Plasma crashes after changing audio profile in pavucontrol 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: kr...@krose.org 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-13-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: This seems to happen once per boot/wake from hibernate or suspend: the first time I change audio profile for my motherboard audio device, Plasma crashes, (presumably) taking Firefox with it. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 271916 (plasmashell) UID: 1000 (krose) GID: 1000 (krose) Signal: 11 (SEGV) Timestamp: Tue 2023-10-17 10:03:43 EDT (24s 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 (krose) Boot ID: d668527e945240e3a440266866cc88a0 Machine ID: 664a7982d2ac41c29342ce753ce1d617 Hostname: nausicaa Storage: /var/lib/systemd/coredump/core.plasmashell.1000.d668527e945240e3a440266866cc88a0.271916.169755142300.zst (present) Size on Disk: 133.3M Message: Process 271916 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.17-1~deb12u1.amd64 Module libudev.so.1 from deb systemd-252.17-1~deb12u1.amd64 Stack trace of thread 271916: #0 0x7f1ef38a9d3c __pthread_kill_implementation (libc.so.6 + 0x8ad3c) #1 0x7f1ef385af32 __GI_raise (libc.so.6 + 0x3bf32) #2 0x7f1ef6279b46 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b46) #3 0x7f1ef385afd0 __restore_rt (libc.so.6 + 0x3bfd0) #4 0x7f1ef38a9d3c __pthread_kill_implementation (libc.so.6 + 0x8ad3c) #5 0x7f1ef385af32 __GI_raise (libc.so.6 + 0x3bf32) #6 0x7f1ef385afd0 __restore_rt (libc.so.6 + 0x3bfd0) #7 0x7f1ef38a4da4 __futex_abstimed_wait_common64 (libc.so.6 + 0x85da4) #8 0x7f1ef38a7468 __pthread_cond_wait_common (libc.so.6 + 0x88468) #9 0x7f1ef3ed1a2b _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd1a2b) #10 0x7f1ef5e0bd58 n/a (libQt5Quick.so.5 + 0x20bd58) #11 0x7f1ef5e0d013 n/a (libQt5Quick.so.5 + 0x20d013) #12 0x7f1ef45493f5 _ZN7QWindow5eventEP6QEvent (libQt5Gui.so.5 + 0x1493f5) #13 0x7f1ef4f62fae _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162fae) #14 0x7f1ef40b16f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8) #15 0x7f1ef453e5cd _ZN22QGuiApplicationPrivate18processExposeEventEPN29QWindowSystemInterfacePrivate11ExposeEventE (libQt5Gui.so.5 + 0x13e5cd) #16 0x7f1ef4511cac _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Gui.so.5 + 0x111cac) #17 0x7f1eeeafbeca n/a (libQt5XcbQpa.so.5 + 0x6deca) #18 0x7f1ef2a571b4 n/a (libglib-2.0.so.0 + 0x571b4) #19 0x7f1ef2a5a2d7 n/a (libglib-2.0.so.0 + 0x5a2d7) #20 0x7f1ef2a5a8f0 g_main_context_iteration (libglib-2.0.so.0 + 0x5a8f0) #21 0x7f1ef4109836 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x309836) #22 0x7f1ef40b017b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b017b) #23 0x7f1ef40b82d6 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2b82d6) #24 0x56107c5bedc3 n/a (plasmashell + 0x26dc3) #25 0x7f1ef38461ca __libc_start_call_main (libc.so.6 + 0x271ca) #26 0x7f1ef3846285 __libc_start_main_impl (libc.so.6 + 0x27285) #27 0x56107c5beee1 n/a (plasmashell + 0x26ee1) Stack trace of thread 271969: #0 0x7f1ef391b05f __GI___poll
[plasmashell] [Bug 475740] New: When plugging in a previously mounted-and-unmounted disk, it doesn't appear until plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=475740 Bug ID: 475740 Summary: When plugging in a previously mounted-and-unmounted disk, it doesn't appear until plasmashell is restarted Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Keywords: qt6 Severity: normal Priority: NOR Component: Disks & Devices Assignee: plasma-b...@kde.org Reporter: n...@kde.org Target Milestone: 1.0 STEPS TO REPRODUCE 1. Plug in a disk 2. In the Disks & Devices popup, mount it 3. From the Disks & Devices popup, unmount it 4. Unplug it 5. Plug it in again OBSERVED RESULT The Disks & Devices popup opens, but it's empty. EXPECTED RESULT Disks & Devices popup opens but the disk is listed in it. ADDITIONAL INFORMATION After step 5, if I restart plasmashell, the disk is shown in the popup when I open it manually. This is a regression from Plasma 5. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475740] When plugging in a previously mounted-and-unmounted disk, it doesn't appear until plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=475740 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Nate Graham --- This turns out to be a regression from https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3416, not something already in master. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475741] New: View/Fit to View option
https://bugs.kde.org/show_bug.cgi?id=475741 Bug ID: 475741 Summary: View/Fit to View option Classification: Applications Product: krita Version: 5.2.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Resize/Scale Image/Layer Assignee: krita-bugs-n...@kde.org Reporter: krizcr...@comcast.net Target Milestone: --- Created attachment 162369 --> https://bugs.kde.org/attachment.cgi?id=162369&action=edit screenshot of image after fit to view - left side of image missing from view Fit to View option not working correctly. Fit to View should resize the entire canvas-image so it fits inside the project window both horz and vert. Sometimes it works, sometimes it doesn't. This option worked perfectly in previous versions. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475742] New: Plasmashell taskbar crashes when swotching desktops or interacting with it
https://bugs.kde.org/show_bug.cgi?id=475742 Bug ID: 475742 Summary: Plasmashell taskbar crashes when swotching desktops or interacting with it Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: martin-ko...@protonmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.8) (Compiled from sources) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 6.1.53-gentoo-r1 x86_64 Windowing System: Wayland Distribution: "Gentoo Linux" DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: This particular time, it crashed when switching desktops, but it sometimes crashes also when interacting with it. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted [KCrash Handler] #4 0x7f7797cb166c in () at /lib64/libc.so.6 #5 0x7f7797c63d82 in raise () at /lib64/libc.so.6 #6 0x7f7797c4d4af in abort () at /lib64/libc.so.6 #7 0x7f7797ea0c38 in () at /usr/lib/gcc/x86_64-pc-linux-gnu/13/libstdc++.so.6 #8 0x7f7797eb30b6 in () at /usr/lib/gcc/x86_64-pc-linux-gnu/13/libstdc++.so.6 #9 0x7f7797eb3121 in () at /usr/lib/gcc/x86_64-pc-linux-gnu/13/libstdc++.so.6 #10 0x7f7797eb33b3 in __cxa_rethrow () at /usr/lib/gcc/x86_64-pc-linux-gnu/13/libstdc++.so.6 #11 0x7f77984adc96 in QVector::realloc(int, QFlags) (this=0x5562f8e5bfe0, aalloc=, options=...) at /usr/src/debug/dev-qt/qtcore-5.15.10-r2/qtbase-everywhere-src-5.15.10/include/QtCore/../../src/corelib/tools/qvector.h:734 #12 0x7f77986938da in QVector::detach() (this=) at /usr/src/debug/dev-qt/qtcore-5.15.10-r2/qtbase-everywhere-src-5.15.10/include/QtCore/../../src/corelib/global/qflags.h:121 #13 QVector::data() (this=) at /usr/src/debug/dev-qt/qtcore-5.15.10-r2/qtbase-everywhere-src-5.15.10/include/QtCore/../../src/corelib/tools/qvector.h:134 #14 QVector::operator[](int) (i=1, this=) at /usr/src/debug/dev-qt/qtcore-5.15.10-r2/qtbase-everywhere-src-5.15.10/include/QtCore/../../src/corelib/tools/qvector.h:458 #15 QSortFilterProxyModelPrivate::build_source_to_proxy_mapping(QVector const&, QVector&) const (proxy_to_source=..., source_to_proxy=..., this=0x5562f8799040) at /usr/src/debug/dev-qt/qtcore-5.15.10-r2/qtbase-everywhere-src-5.15.10/src/corelib/itemmodels/qsortfilterproxymodel.cpp:1232 #16 0x7f779869779c in QSortFilterProxyModelPrivate::remove_proxy_interval(QVector&, QVector&, int, int, QModelIndex const&, Qt::Orientation, bool) (emit_signal=true, orient=Qt::Vertical, proxy_parent=..., proxy_end=, proxy_start=, proxy_to_source=..., source_to_proxy=..., this=0x5562f8799040) at /usr/src/debug/dev-qt/qtcore-5.15.10-r2/qtbase-everywhere-src-5.15.10/src/corelib/itemmodels/qsortfilterproxymodel.cpp:819 #17 QSortFilterProxyModelPrivate::remove_source_items(QVector&, QVector&, QVector const&, QModelIndex const&, Qt::Orientation, bool) (this=this@entry=0x5562f8799040, source_to_proxy=..., proxy_to_source=..., source_items=..., source_parent=..., orient=orient@entry=Qt::Vertical, emit_signal=true) at /usr/src/debug/dev-qt/qtcore-5.15.10-r2/qtbase-everywhere-src-5.15.10/src/corelib/itemmodels/qsortfilterproxymodel.cpp:792 #18 0x7f7798697b61 in QSortFilterProxyModelPrivate::source_items_about_to_be_removed(QModelIndex const&, int, int, Qt::Orientation) (this=0x5562f8799040, source_parent=..., start=0, end=0, orient=Qt::Vertical) at /usr/src/debug/dev-qt/qtcore-5.15.10-r2/qtbase-everywhere-src-5.15.10/src/corelib/itemmodels/qsortfilterproxymodel.cpp:1094 #19 0x7f77987094d0 in doActivate(QObject*, int, void**) (sender=0x5562f8e34860, signal_index=14, argv=0x7ffdebe563e0) at /usr/src/debug/dev-qt/qtcore-5.15.10-r2/qtbase-everywhere-src-5.15.10/src/corelib/kernel/qobject.cpp:3937 #20 0x7f779870014f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x5562f8e34860, m=m@entry=0x7f77987c9ac0 , local_signal_index=local_signal_index@entry=11, argv=argv@entry=0x7ffdebe563e0) at /usr/src/debug/dev-qt/qtcore-5.15.10-r2/qtbase-everywhere-src-5.15.10/src/corelib/kernel/qobject.cpp:3985 #21 0x7f779865ebae in QAbstractItemModel::rowsAboutToBeRemoved(QModelIndex const&, int, int, QAbstractItemModel::QPrivateSignal) (this=this@entry=0x5562f8e34860, _t1=..., _t2=, _t2@entry=0, _t3=, _t3@entry=0, _t4=...) at .moc/moc_qabstractitemmodel.cpp:599 #22 0x7f77986673ce in QAbstractItemModel::beginRemoveRows(QModelIndex const&, int, int) (this=0x5562f8e34860, parent=..., first=0, last=0) at /usr/src/debug/dev-qt/qtcore-5.15.10-r2/qtbase-everywhere-src-5.15.10/src/corelib/itemmodels/qabstractitemmodel.cpp:2818 #23 0x7f779008da22 in TaskManager::Task
[systemsettings] [Bug 473125] Switching between System Settings pages with a stylus doesn't work most of the time in Plasma 6
https://bugs.kde.org/show_bug.cgi?id=473125 --- Comment #3 from Nate Graham --- Git commit 70678e79c908ce03cf996f2317fdac2ee0c3eb03 by Nate Graham, on behalf of Aki Sakurai. Committed on 17/10/2023 at 16:24. Pushed by ngraham into branch 'master'. Correct the misgenerated localMouseEvent This commit fixes the issue where some parts of Qt6 widgets couldn't be clicked with a Wacom tablet stylus. 1. QMouseEvent is constructed with incorrect arguments. https://doc.qt.io/qt-6/qmouseevent.html#QMouseEvent-3 The _button_ that caused the event is given as a value from the Qt::MouseButton enum. If the event _type_ is MouseMove, then the appropriate button for this event is Qt::NoButton. _buttons_ is the state of all buttons at the time of the event, _modifiers_ is the state of all keyboard modifiers. 2. Some parts of Qt widgets require a timestamp to function properly. https://codereview.qt-project.org/c/qt/qtdeclarative/+/493020 QQuickWidget: give each mapped mouse event the same QEventPoint. Counter-intuitively, this is done by setting the timestamp. Every time you construct a new mouse event, you always need to call setTimestamp() for the obvious reason: the timestamp is not a ctor argument, but it's important for some event receivers. But the non-obvious reason is that QMutableEventPoint::setTimestamp() has other useful side effects: the velocity calculation is done there, sensibly enough. But to make that possible, it also looks up the persistent QEventPoint with the same ID as the one in the QMouseEvent, and that's the most important to fix QTBUG-114258 specifically. QQuickFlickablePrivate::handleMoveEvent() calculates delta as QEventPoint::position() - mapFromGlobal(globalPressPosition()) and then QQuickFlickablePrivate::drag() does the drag threshold check. M +3-1kstyle/oxygenwindowmanager.cpp https://invent.kde.org/plasma/oxygen/-/commit/70678e79c908ce03cf996f2317fdac2ee0c3eb03 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 473125] Switching between System Settings pages with a stylus doesn't work most of the time in Plasma 6
https://bugs.kde.org/show_bug.cgi?id=473125 --- Comment #4 from Nate Graham --- Git commit b050ab3bca5a667fcea8137f74f8eea514d57f0f by Nate Graham, on behalf of Aki Sakurai. Committed on 17/10/2023 at 16:24. Pushed by ngraham into branch 'master'. Correct the misgenerated localMouseEvent This commit fixes the issue where some parts of Qt6 widgets couldn't be clicked with a Wacom tablet stylus. 1. QMouseEvent is constructed with incorrect arguments. https://doc.qt.io/qt-6/qmouseevent.html#QMouseEvent-3 The _button_ that caused the event is given as a value from the Qt::MouseButton enum. If the event _type_ is MouseMove, then the appropriate button for this event is Qt::NoButton. _buttons_ is the state of all buttons at the time of the event, _modifiers_ is the state of all keyboard modifiers. 2. Some parts of Qt widgets require a timestamp to function properly. https://codereview.qt-project.org/c/qt/qtdeclarative/+/493020 QQuickWidget: give each mapped mouse event the same QEventPoint. Counter-intuitively, this is done by setting the timestamp. Every time you construct a new mouse event, you always need to call setTimestamp() for the obvious reason: the timestamp is not a ctor argument, but it's important for some event receivers. But the non-obvious reason is that QMutableEventPoint::setTimestamp() has other useful side effects: the velocity calculation is done there, sensibly enough. But to make that possible, it also looks up the persistent QEventPoint with the same ID as the one in the QMouseEvent, and that's the most important to fix QTBUG-114258 specifically. QQuickFlickablePrivate::handleMoveEvent() calculates delta as QEventPoint::position() - mapFromGlobal(globalPressPosition()) and then QQuickFlickablePrivate::drag() does the drag threshold check. M +2-1kstyle/breezewindowmanager.cpp https://invent.kde.org/plasma/breeze/-/commit/b050ab3bca5a667fcea8137f74f8eea514d57f0f -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 473125] Switching between System Settings pages with a stylus doesn't work most of the time in Plasma 6
https://bugs.kde.org/show_bug.cgi?id=473125 Nate Graham changed: What|Removed |Added Resolution|UPSTREAM|FIXED Version Fixed In||6.0 Latest Commit||https://invent.kde.org/plas ||ma/breeze/-/commit/b050ab3b ||ca5a667fcea8137f74f8eea514d ||57f0f -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475375] Ghost duplicate buttons in Task Manager
https://bugs.kde.org/show_bug.cgi?id=475375 --- Comment #3 from martin-ko...@protonmail.com --- I was able to recompile with debug symbols have submitted a crash report: https://bugs.kde.org/show_bug.cgi?id=475742 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475690] Highlight flashes in new overview on X11
https://bugs.kde.org/show_bug.cgi?id=475690 ratijas changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||m...@ratijas.tk --- Comment #2 from ratijas --- Can confirm. It's is part of something way worse related to flickering or getting stuck on a wrong frame -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 474679] Krita fails to render animations that don't have starting frame as 0
https://bugs.kde.org/show_bug.cgi?id=474679 Dmitry Kazakov changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/krita/-/commit/2cf4dfb ||f0de99d81fbe32654d0fad6a2d6 ||29ad16 --- Comment #18 from Dmitry Kazakov --- Git commit 2cf4dfbf0de99d81fbe32654d0fad6a2d629ad16 by Dmitry Kazakov. Committed on 17/10/2023 at 16:42. Pushed by dkazakov into branch 'krita/5.2'. Fix rendering of the video when start frame is non-zero When start frame is non-zero or if the frames are saved with numbering offset, we should pass correct offsets to ffmpeg. Before the patch, it had the following problems: 1) If start numbering was > 4, then ffmpeg rendering failed. 2) If first frame was non-zero, then audio was saved with wrong offset M +7-6libs/ui/animation/KisVideoSaver.cpp https://invent.kde.org/graphics/krita/-/commit/2cf4dfbf0de99d81fbe32654d0fad6a2d629ad16 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 475743] New: Repeat current track 'breaks' next button
https://bugs.kde.org/show_bug.cgi?id=475743 Bug ID: 475743 Summary: Repeat current track 'breaks' next button Classification: Applications Product: Elisa Version: 23.08.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: quinten@quinten.space Target Milestone: --- SUMMARY When multiple tracks are queued, and "Repeat current track" is enabled, the "Skip forward" button repeats the current track instead. This makes sense on paper (because of the repeat mode), but in practice it is likely not what the user means as to restart they can already use the "Skip backward" button and repeat mode is generally only expected to affect 'automatic advancing' (and maybe if the backward/forward buttons loop around or are disabled). STEPS TO REPRODUCE 1. Have multiple songs queued 2. Enable "Repeat current track" 3. Click "Skip Forward" OBSERVED RESULT Current song repeats EXPECTED RESULT "Skip forward" overrides repeat mode and starts playing the next song SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Seems this was also implemented in Amarok at some point, BUG: 85087. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 474679] Krita fails to render animations that don't have starting frame as 0
https://bugs.kde.org/show_bug.cgi?id=474679 Dmitry Kazakov changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/-/commit/2cf4dfb |hics/krita/-/commit/a11cf8e |f0de99d81fbe32654d0fad6a2d6 |076e537bb457a8226cf4703cbeb |29ad16 |33cde0 --- Comment #19 from Dmitry Kazakov --- Git commit a11cf8e076e537bb457a8226cf4703cbeb33cde0 by Dmitry Kazakov. Committed on 17/10/2023 at 16:43. Pushed by dkazakov into branch 'master'. Fix rendering of the video when start frame is non-zero When start frame is non-zero or if the frames are saved with numbering offset, we should pass correct offsets to ffmpeg. Before the patch, it had the following problems: 1) If start numbering was > 4, then ffmpeg rendering failed. 2) If first frame was non-zero, then audio was saved with wrong offset M +7-6libs/ui/animation/KisVideoSaver.cpp https://invent.kde.org/graphics/krita/-/commit/a11cf8e076e537bb457a8226cf4703cbeb33cde0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 474679] Krita fails to render animations that don't have starting frame as 0
https://bugs.kde.org/show_bug.cgi?id=474679 --- Comment #20 from Dmitry Kazakov --- Hi, Nathan! Could you please test this build when it is finished? https://binary-factory.kde.org/job/Krita_Stable_Windows_Build/2015/ I think the bug is fixed now. Please also check if there is any offset between the video and audio streams. Now there should be no offset :) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407505] Animations using audio do not respect the designated playback range.
https://bugs.kde.org/show_bug.cgi?id=407505 Dmitry Kazakov changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED CC||dimul...@gmail.com --- Comment #3 from Dmitry Kazakov --- Hi, animeBenz! Could you please check the latest version of Krita 5.2? It seems like the bug is fixed now :) https://krita.org/en/item/krita-5-2-released/ -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 475744] New: No icon (for Thunderbird) if not running
https://bugs.kde.org/show_bug.cgi?id=475744 Bug ID: 475744 Summary: No icon (for Thunderbird) if not running Classification: Plasma Product: lattedock Version: 0.10.8 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: kde-b...@spaetzle.info Target Milestone: --- Created attachment 162370 --> https://bugs.kde.org/attachment.cgi?id=162370&action=edit Screenshot SUMMARY *** The launcher doesn't show the thunderbird icon (just a rectangle placeholder). I did not change anything on the icons myself (maybe via majaro-stable updates). Once launched there's a separate, correct thunderbird icon though (see screenshot). *** STEPS TO REPRODUCE 1. Have lattedock running OBSERVED RESULT No icon for thunderbird EXPECTED RESULT Show correct icon for thunderbird SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro-Stable KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475562] krita segfaults on start after displaying the splash screen
https://bugs.kde.org/show_bug.cgi?id=475562
Lynx3d changed:
What|Removed |Added
CC||lynx.mw+...@gmail.com
--- Comment #15 from Lynx3d ---
hm the crashing line is:
> cs->profile()->uniqueId() ==
> KoColorSpaceRegistry::instance()->p2020PQProfile()->uniqueId()) {
That suggests the p2020PQProfile is not available, which should be part of a
correct installation.
Nevertheless, I guess there needs to be a nullptr check, I wasn't aware this
function depends on the presence of a .icc file and thus can fail to return a
valid profile.
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 475745] New: Crash while working on many raster layers with a transform mask each
https://bugs.kde.org/show_bug.cgi?id=475745 Bug ID: 475745 Summary: Crash while working on many raster layers with a transform mask each Classification: Applications Product: krita Version: 5.2.0 Platform: Other OS: Other Status: REPORTED Severity: crash Priority: NOR Component: Resize/Scale Image/Layer Assignee: krita-bugs-n...@kde.org Reporter: saranv...@gmail.com Target Milestone: --- Created attachment 162371 --> https://bugs.kde.org/attachment.cgi?id=162371&action=edit Crash report SUMMARY *** STEPS TO REPRODUCE I repeated this steps several times quickly, I am not sure if this alone is what caused the crash. 1. have a raster layer with a trasnform mask on it, move it and scale it. 2. duplicate both 3. click on the transform mask with transform tool and change its position 4. repeat steps 2 and 3 SOFTWARE/OS VERSIONS Windows 10 ADDITIONAL INFORMATION i had a group with raster layers and clipping masks hidden. I was duplicating a merged version of the group several times and moving the duplicates with a transform mask on each of them. At the time of crash I had about 8 layers with transform masks. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 475746] New: location path setting cant support soft link
https://bugs.kde.org/show_bug.cgi?id=475746
Bug ID: 475746
Summary: location path setting cant support soft link
Classification: Applications
Product: systemsettings
Version: 5.27.8
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: kcm_desktoppath
Assignee: plasma-b...@kde.org
Reporter: ycj...@163.com
Target Milestone: ---
Created attachment 162372
--> https://bugs.kde.org/attachment.cgi?id=162372&action=edit
location set
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 location of download path(下载路径) to /home/imic/Downloads （this is a soft
link, linked to another disk）
[imic@imic-21fca000cd ~]$ pwd
/home/imic
[imic@imic-21fca000cd ~]$ ls -lsh | grep Downloads
0 lrwxrwxrwx 1 imic imic 30 9月30日 09:24 Downloads ->
/run/media/imic/work/Downloads
[imic@imic-21fca000cd ~]$
2. restart os ,the location of download path changed to /home/imic/
OBSERVED RESULT
location of download path is /home/imic/
EXPECTED RESULT
location of download path is /home/imic/Downloads or
/run/media/imic/work/Downloads
SOFTWARE/OS VERSIONS
██ OS: Manjaro 23.0.4 Uranos
██ Kernel: x86_64 Linux 6.1.55-1-MANJARO
██ Uptime: 1h 28m
Packages: 1269
Shell: zsh 5.9
Resolution: 1920x1200
DE: KDE 5.110.0 / Plasma 5.27.8
WM: KWin
GTK Theme: Breeze [GTK2/3]
Icon Theme: WhiteSur
Disk: 260G / 762G (35%)
CPU: 13th Gen Intel Core i7-13700H @ 20x
4.8GHz [33.0°C]
GPU: NVIDIA RTX A500 Laptop GPU
RAM: 5416MiB / 31771MiB
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 475746] location path setting cant support soft link
https://bugs.kde.org/show_bug.cgi?id=475746 --- Comment #1 from ycj...@163.com --- Created attachment 162373 --> https://bugs.kde.org/attachment.cgi?id=162373&action=edit disk auto mount setting -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475562] krita segfaults on start after displaying the splash screen
https://bugs.kde.org/show_bug.cgi?id=475562
--- Comment #16 from Timo Gurr ---
Created attachment 162374
--> https://bugs.kde.org/attachment.cgi?id=162374&action=edit
krita-5.2.0-installed-files.txt
(In reply to Lynx3d from comment #15)
> hm the crashing line is:
> > cs->profile()->uniqueId() ==
> > KoColorSpaceRegistry::instance()->p2020PQProfile()->uniqueId()) {
>
> That suggests the p2020PQProfile is not available, which should be part of a
> correct installation.
Can you please name the file I have to check for to verify something is
actually missing or not correctly installed? Attaching a full list of installed
files.
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 475747] New: kconnect crash whilst transferring multiple files from phone
https://bugs.kde.org/show_bug.cgi?id=475747 Bug ID: 475747 Summary: kconnect crash whilst transferring multiple files from phone Classification: Applications Product: kdeconnect Version: 22.12.3 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: t...@buttersideup.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Application: kdeconnectd (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-13-amd64 x86_64 Windowing System: Wayland Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: KDE crashes on the 10th file, when tranfering a block of 16 files from my phone. The crash can be reproduced sometimes. -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 #5 0x7f1c91aa9d9f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78 #6 0x7f1c91a5af32 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #7 0x7f1c91a45472 in __GI_abort () at ./stdlib/abort.c:79 #8 0x7f1c91c90c79 in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #9 QMessageLogger::fatal (this=this@entry=0x7f1c5e3fc6f0, msg=msg@entry=0x7f1c934b3d40 "Fatal Error: Got cmd %d, while waiting for an answer!") at global/qlogging.cpp:893 #10 0x7f1c933e93b6 in KIO::SlaveBase::waitForAnswer (this=this@entry=0x7f1c4c003090, expected1=expected1@entry=84, expected2=expected2@entry=65, data=..., pCmd=pCmd@entry=0x7f1c5e3fc764) at ./src/core/slavebase.cpp:1149 #11 0x7f1c933eb335 in KIO::SlaveBase::canResume (this=this@entry=0x7f1c4c003090, offset=65536) at ./src/core/slavebase.cpp:1116 #12 0x7f1c805581bd in FileProtocol::put (this=0x7f1c4c003080, url=..., _mode=-1, _flags=...) at ./src/ioslaves/file/file.cpp:546 #13 0x7f1c933f0a91 in KIO::SlaveBase::dispatch (this=0x7f1c4c003090, command=68, data=...) at ./src/core/slavebase.cpp:1289 #14 0x7f1c933f13f6 in KIO::SlaveBase::dispatchLoop (this=0x7f1c4c003090) at ./src/core/slavebase.cpp:342 #15 0x7f1c9348aa6e in KIO::WorkerThread::run (this=0x563834ef9660) at ./src/core/workerthread.cpp:62 #16 0x7f1c91ccbd43 in QThreadPrivate::start (arg=0x563834ef9660) at thread/qthread_unix.cpp:331 #17 0x7f1c91aa8044 in start_thread (arg=) at ./nptl/pthread_create.c:442 #18 0x7f1c91b2861c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 10 (Thread 0x7f1c5f3ff6c0 (LWP 4478) "kdeconnectd"): #1 __pselect (nfds=nfds@entry=5, readfds=readfds@entry=0x7f1c5f3f6ad0, writefds=writefds@entry=0x0, exceptfds=exceptfds@entry=0x0, timeout=, timeout@entry=0x7f1c5f3f6ac0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/pselect.c:56 #2 0x7f1c9020ba62 in usbmuxd_listen_inotify () at libusbmuxd.c:923 #3 0x7f1c9020ce60 in usbmuxd_listen () at libusbmuxd.c:979 #4 device_monitor (data=) at libusbmuxd.c:1107 #5 0x7f1c91aa8044 in start_thread (arg=) at ./nptl/pthread_create.c:442 #6 0x7f1c91b2861c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 9 (Thread 0x7f1c74dff6c0 (LWP 4358) "Qt bearer threa"): #1 0x7f1c905d49ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1c905d4acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1c91f0984e in QEventDispatcherGlib::processEvents (this=0x7f1c58000b70, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f1c91eb017b in QEventLoop::exec (this=this@entry=0x7f1c74dfebc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #5 0x7f1c91ccab87 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f1c91ccbd43 in QThreadPrivate::start (arg=0x563834dec9b0) at thread/qthread_unix.cpp:331 #7 0x7f1c91aa8044 in start_thread (arg=) at ./nptl/pthread_create.c:442 #8 0x7f1c91b2861c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 8 (Thread 0x7f1c80ffc6c0 (LWP 4357) "QDBusConnection"): #1 __GI___libc_read (fd=16, buf=0x7f1c80ffb970, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f1c90623c9f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1c905d44c5 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f1c905d4958 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f1c905d4acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f1c91f0984e in QEventDispatcherGlib::processEvents (this=0x7f1c68000b70, flags=...) at kernel/q
[kwin] [Bug 475748] New: Default keybindings (for e.g. virtual desktop switching) are not enabled by default
https://bugs.kde.org/show_bug.cgi?id=475748 Bug ID: 475748 Summary: Default keybindings (for e.g. virtual desktop switching) are not enabled by default Classification: Plasma Product: kwin Version: 5.27.8 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: ngomp...@gmail.com Target Milestone: --- SUMMARY With a fresh Fedora KDE install, a number of default keybindings are not enabled by default, leading to a puzzling situation where it looks like you have them, but they don't work. A specific example are the key bindings for switching virtual desktops using Meta+Ctrl+ArrowKeys. These are the default, but don't work without setting them in System Settings > Shortcuts > KWin. STEPS TO REPRODUCE 1. Install Fedora KDE 2. Configure virtual desktops (I use a 2x2 grid) 3. Try switching with the mentioned keybindings in the summary. OBSERVED RESULT Virtual desktops don't switch with the keybindings. EXPECTED RESULT Virtual desktops switch with the default keybindings. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 39 (KDE Plasma) (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION I've noticed this affects a number of default keybindings, and I don't understand why any default keybindings are disabled by default. -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 475686] Provide an import wizard to import settings from other desktop
https://bugs.kde.org/show_bug.cgi?id=475686 --- Comment #2 from Fushan Wen --- # Accessibility - [ ] Screen magnifier - [ ] Track mode - [ ] Screen reader - [ ] Beep - [ ] Bounce Keys - [ ] Enable - [ ] Delay - [ ] Mouse Keys - [ ] Slow Keys - [ ] Sticky Keys # Desktop - [ ] Wallpaper - [ ] Zoom Option - [ ] URI - [ ] Dark URI - [ ] Background Color - [ ] Lockscreen wallpaper - [ ] Enable animations - [ ] Themes - [ ] Color scheme (Light/Dark) - [ ] Toolbar style - [ ] Icon theme - [ ] Font name - [ ] Cursor theme - [ ] Cursor size - [ ] Sound theme name - [ ] Scaling factor - [ ] Automatically update timezone - [ ] Show the week date in the calendar - [ ] Clock shows seconds - [ ] Clock shows date - [ ] Enable hot corners - [ ] Show battery percentage - [ ] Enable selection paste - [ ] Automount - [ ] Keyboard shortcuts - [ ] Workspace - [ ] Window - [ ] Applications menu - [ ] Workspace names # Hardware - [ ] Edge scrolling - [ ] Two finger scrolling - [ ] Disable while typing - [ ] Tap to click - [ ] Acceleration profile - [ ] Pointer Speed - [ ] Natural scrolling - [ ] Emulate middle click - [ ] Key repeat interval - [ ] Initial key repeat delay - [ ] Double click interval - [ ] Left handed mode - [ ] Tablet area - [ ] Brightness when idle - [ ] Idle dim - [ ] Sleep timeout - [ ] Sleep Action - [ ] Enable ambient light sensor - [ ] Power profile # Window Management - [ ] Raise on click - [ ] Focus mode - [ ] Button layout - [ ] Middle click action - [ ] Display all workspaces - [ ] Display all monitors # Applications - [ ] Default applications - [ ] Email - [ ] Calendar - [ ] Tasks - [ ] Terminal - [ ] Recently used Emoji - [ ] Last folder path -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 431596] Improve startup time and responsiveness with network music collections when loading a very large playlist on launch
https://bugs.kde.org/show_bug.cgi?id=431596 t...@gmx.com changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from t...@gmx.com --- With version 23.08.2 this issue appears to be resolved. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 472862] plasmashell and kwin_wayland randomly crashed in KDirWatchPrivate::emitEvent() due to kate sessions
https://bugs.kde.org/show_bug.cgi?id=472862 --- Comment #19 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kcoreaddons/-/merge_requests/386 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420280] Google authentication process gets stuck due to excessively old version of signon-ui library
https://bugs.kde.org/show_bug.cgi?id=420280 --- Comment #95 from Nate Graham --- The question was already answered: connecting to online accounts in GNOME works because the GNOME code does not depend on a recent version of the signon-ui library. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 475734] Build system tries to install breeze-text.s to /usr when CMAKE_INSTALL_PREFIX is set to something else
https://bugs.kde.org/show_bug.cgi?id=475734 --- Comment #2 from Nate Graham --- Probably, I guess I only now started building it due to `kdesrc-build workspace` pulling it in, and I migrated to that to exercise what we're recommending in our documentation at https://community.kde.org/Get_Involved/development/Build_software_with_kdesrc-build#Plasma_Desktop. Seems like when built from kdesrc-build, we should automatically pass INSTALL_BROKEN_PLYMOUTH_DATA=ON. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 423884] Type-ahead in details view mode should scroll the current result to the center of the list
https://bugs.kde.org/show_bug.cgi?id=423884 Méven Car changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/syst ||em/dolphin/-/commit/a59d9f8 ||5fa770a00d10e66025e102c736e ||18fa70 --- Comment #2 from Méven Car --- Git commit a59d9f85fa770a00d10e66025e102c736e18fa70 by Méven Car, on behalf of Amol Godbole. Committed on 17/10/2023 at 17:47. Pushed by meven into branch 'master'. KItemListView: add view position in scrollToItem() An item, on being scrolled to, is always located at the nearest edge of the view. This is not always convenient. Allow specifying where the item should be positioned with respect to the view in scrollToItem(). M +1-1src/kitemviews/kitemlistcontroller.cpp M +48 -12 src/kitemviews/kitemlistview.cpp M +6-2src/kitemviews/kitemlistview.h M +1-1src/views/dolphinview.cpp https://invent.kde.org/system/dolphin/-/commit/a59d9f85fa770a00d10e66025e102c736e18fa70 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 475734] Build system tries to install breeze-text.s to /usr when CMAKE_INSTALL_PREFIX is set to something else
https://bugs.kde.org/show_bug.cgi?id=475734 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/sdk/kdesrc-build/-/merge_requests/294 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472005] Touchpad disabled after booting, but can be re-enabled in settings
https://bugs.kde.org/show_bug.cgi?id=472005 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #6 from Nate Graham --- Ok, so something is disabling the touchpad intentionally. Any chance you could try this on X11 and see if it's working as expected there? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 459624] Mouse wheel scrolling on a slider produces inverted results
https://bugs.kde.org/show_bug.cgi?id=459624 Nate Graham changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #1 from Nate Graham --- In progrss with https://invent.kde.org/frameworks/qqc2-desktop-style/-/merge_requests/288. -- You are receiving this mail because: You are watching all bug changes.
[KPipeWire] [Bug 469005] Very high memory used while screen recording (possibly cursor related)
https://bugs.kde.org/show_bug.cgi?id=469005 whyhow3@gmail.com changed: What|Removed |Added CC||whyhow3@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475653] Primary monitor is switched when coming back from suspend/rebooting
https://bugs.kde.org/show_bug.cgi?id=475653 --- Comment #3 from Michael Butash --- This was my other thread on the matter. https://bugs.kde.org/show_bug.cgi?id=465889 These tend to pile up in ~/.local/share/kscreen. Also recommended was clearing these that seemed to accumulate display config fragments with this too, letting kde rebuild these clean certainly helped, but they begin piling up again. ~/config/plasma-org.kde.plasma.desktop-appletsrc ~/config/plasmashellrc My displays attached to a tb dock rotate display id constantly with every reset. This seems to be more a systemic problem in wayland than kde that this isn't more deterministic, but something's gotta make due with the quirk. I have to keep latte-dock profiles for each of the 3 display variations I get, and when they blip, sigh, and go change latte dock for whatever they land on this time. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcoreaddons] [Bug 466562] Remove support for FAM ( long dead project)
https://bugs.kde.org/show_bug.cgi?id=466562 Méven Car changed: What|Removed |Added CC||meve...@gmail.com --- Comment #1 from Méven Car --- This is not a warning, merely information intended for developers and packagers might find useful or are free to ignore. FAM library is the only notification system supporting NFS (as the message says), this is a reason enough to me to keep it supported as long as distro do ship the dependency, (and no major issues are brought up with it), or an alternative becomes available. What GNOME deprecates is there business, although that is an interesting datapoint. It seems they never had NFS usecase in mind when they removed support, perhaps gamin did not have support for it. -- You are receiving this mail because: You are watching all bug changes.
