[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #26 from caulier.gil...@gmail.com --- Marcel, If there is a memory leak somewhere with your Linux box (i see nothing with mine) valgrind can certainly help to identify the dirty code. Look here to see how to run digiKam in valgrind (running speed is decreased by 20). https://www.digikam.org/api/index.html#memleak I full valgrind console trace can be instructive as the memory leak can be located outside digiKam... Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #25 from Marcel --- Created attachment 131428 --> https://bugs.kde.org/attachment.cgi?id=131428=edit endless loop without crash On another try with gdb the behavior was even more strange. There is no seg fault after running out of memory but digikam is still running but does not check any pictures for faces. You can see this on the network history as all my pics are on a network drive. See MemoryConsumptionSlowDown.png -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #24 from Marcel --- Created attachment 131427 --> https://bugs.kde.org/attachment.cgi?id=131427=edit Memory consumption of the process before it crashs I checked the new commit from Maik. It looks much better. Anyway I still have a seg fault later in time. So it takes longer until it crashes. But now I think it is a memory leak. See the attached picture MemoryConsumption.png -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 426169] gtk apps don't work properly with latte-panel.
https://bugs.kde.org/show_bug.cgi?id=426169 --- Comment #3 from Atif --- yeah. So is this unfixable? -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 426200] New: Under wayland kpatience crashes on window resize/launch
https://bugs.kde.org/show_bug.cgi?id=426200 Bug ID: 426200 Summary: Under wayland kpatience crashes on window resize/launch Product: kpat Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: co...@kde.org Reporter: ja...@jasonplayne.com CC: kde-games-b...@kde.org Target Milestone: --- Application: kpat (20.08.1) Qt Version: 5.14.2 Frameworks Version: 5.73.0 Operating System: Linux 5.8.6-050806-generic x86_64 Windowing system: Wayland Distribution: KDE neon User Edition 5.19 -- Information about the crash: - What I was doing when the application crashed: I was wanting to play, so I launch the app and when to move the window I tried a few times and it is some variant of: launch app, double click title or resize window that causes the app to crash - Unusual behavior I noticed: after crash there is a 50% translucent ghost of kpatience covering my desktop. The crash can be reproduced every time. -- Backtrace: Application: KPatience (kpat), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #5 0x7f0bd10d9859 in __GI_abort () at abort.c:79 #6 0x7f0bd1665b69 in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=, msg=) at global/qlogging.cpp:893 #8 0x7f0bcc70a8b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #9 0x7f0bcc71b0de in QtWaylandClient::QWaylandDisplay::flushRequests() () from /usr/lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #10 0x7f0bd18b3550 in doActivate (sender=0x557027e0c1b0, signal_index=3, argv=0x7ffef3f49cb0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395 #11 0x7f0bd18adaf7 in QMetaObject::activate (sender=sender@entry=0x557027e0c1b0, m=m@entry=0x7f0bd1b59ba0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffef3f49cb0) at kernel/qobject.cpp:3930 #12 0x7f0bd18b6d95 in QSocketNotifier::activated (this=this@entry=0x557027e0c1b0, _t1=, _t2=...) at .moc/moc_qsocketnotifier.cpp:141 #13 0x7f0bd18b70f1 in QSocketNotifier::event (this=0x557027e0c1b0, e=0x7ffef3f49f70) at kernel/qsocketnotifier.cpp:266 #14 0x7f0bd2462cc3 in QApplicationPrivate::notify_helper (this=this@entry=0x557027d900f0, receiver=receiver@entry=0x557027e0c1b0, e=e@entry=0x7ffef3f49f70) at kernel/qapplication.cpp:3685 #15 0x7f0bd246bf40 in QApplication::notify (this=0x7ffef3f4a2f0, receiver=0x557027e0c1b0, e=0x7ffef3f49f70) at kernel/qapplication.cpp:3431 #16 0x7f0bd187d78a in QCoreApplication::notifyInternal2 (receiver=0x557027e0c1b0, event=0x7ffef3f49f70) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:153 #17 0x7f0bd18d6de5 in socketNotifierSourceDispatch (source=0x557027dc34d0) at kernel/qeventdispatcher_glib.cpp:107 #18 0x7f0bcf41bfbd in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7f0bcf41c240 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7f0bcf41c2e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7f0bd18d61e2 in QEventDispatcherGlib::processEvents (this=0x557027e0be80, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #22 0x7f0bd187c24b in QEventLoop::exec (this=this@entry=0x7ffef3f4a180, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:136 #23 0x7f0bd1884296 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:118 #24 0x557026bf1d11 in ?? () #25 0x7f0bd10db0b3 in __libc_start_main (main=0x557026bf0010, argc=3, argv=0x7ffef3f4a468, init=, fini=, rtld_fini=, stack_end=0x7ffef3f4a458) at ../csu/libc-start.c:308 #26 0x557026bf29ce in ?? () [Inferior 1 (process 508358) detached] Possible duplicates by query: bug 424911, bug 423951, bug 423222, bug 423132, bug 422433. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #23 from Marcel --- (In reply to Maik Qualmann from comment #15) > Marcel, a GDB backtrace would be good to see in which function it crashes. > > https://www.digikam.org/contribute/ > > Maik The backtrace was attached from the beginning on. See Backtrace.txt -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 418141] Font rendering instantly gets better when you go to Tool Settings > go to Stroke panel > click 'No Fill'
https://bugs.kde.org/show_bug.cgi?id=418141 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Ever confirmed|1 |0 Resolution|WAITINGFORINFO |--- --- Comment #10 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425630] Making animation Krita crashes
https://bugs.kde.org/show_bug.cgi?id=425630 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 396387] Crashed on the next after several F3 view actions in a row on JPG and TXT files
https://bugs.kde.org/show_bug.cgi?id=396387 --- Comment #10 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 423041] sftp/segmentation fault
https://bugs.kde.org/show_bug.cgi?id=423041 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426198] kwin wayland build has X11 dependency
https://bugs.kde.org/show_bug.cgi?id=426198 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 426199] frameworks-kglobalaccel build requires X11 on Linux
https://bugs.kde.org/show_bug.cgi?id=426199 Leonard Lausen changed: What|Removed |Added CC||leon...@lausen.nl -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 426199] New: frameworks-kglobalaccel build requires X11 on Linux
https://bugs.kde.org/show_bug.cgi?id=426199 Bug ID: 426199 Summary: frameworks-kglobalaccel build requires X11 on Linux Product: frameworks-kglobalaccel Version: 5.73.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: leon...@lausen.nl Target Milestone: --- Created attachment 131426 --> https://bugs.kde.org/attachment.cgi?id=131426=edit patch kglobalaccel supports building without X11 only on MacOS. OBSERVED RESULT Building kglobalaccel for Wayland requires building with X11 too. EXPECTED RESULT kglobalaccel can be built without X11 support on Linux. Attached is a simple patch to add an USE_X11 option to the CmakeLists.txt. There might be a more idiomatic way with ECM, but this sufficed to try build kglobalaccel without X11. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 426198] New: kwin wayland build has X11 dependency
https://bugs.kde.org/show_bug.cgi?id=426198 Bug ID: 426198 Summary: kwin wayland build has X11 dependency Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: leon...@lausen.nl Target Milestone: --- SUMMARY kwin CMakeLists.txt seems to always require X11. However, users may wish to build kwin only for wayland without X11 support. OBSERVED RESULT Building KWin for Wayland requires building KWin for X11 too. EXPECTED RESULT KWin can be build for Wayland without building for X11. An option USE_X11 can be used to toggle if X11 target is built. -- You are receiving this mail because: You are watching all bug changes.
[SeExpr] [Bug 426197] New: Found some mistakes in a few strings
https://bugs.kde.org/show_bug.cgi?id=426197 Bug ID: 426197 Summary: Found some mistakes in a few strings Product: SeExpr Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Translations Assignee: krita-bugs-n...@kde.org Reporter: tyson...@tysontan.com Target Milestone: --- ## #: ExprBuiltins.cpp:138 Current: x transitions linearly when x b （it has an extra space at the end too) Possible correction: x transitions linearly when a x b ## #: ExprBuiltins.cpp:401 Current: color saturate(color val, float amt) Scale saturation of color by amt. The color is scaled around the rec709 luminance value, and negative results are clamped at zero. (It has an extra empty line at the end) Possible correction: Remove empty line ## #: ExprBuiltins.cpp:698 Current: The gain< controls how much each Possible correction: The gain controls how much each ## #: ExprBuiltins.cpp:1175 Current: The result rotates v such that the Y axis points in the given up direction Possible correction: The result is computed as ``loRange + value % (hiRange-loRange+1)``. ## #: ExprBuiltins.cpp:1319 Current: Interpolates a set of values to the parameter specified where y1, ..., yn are distributed evenly from [0...1] Possible correction: Interpolates a set of values to the parameter specified where y1, ..., yn are distributed evenly from [0..1] (Is there a reason to use [0..1] instead of [0,1] as in the documentation?) ## #: UI/ExprColorCurve.cpp:369 Selected Position: (1 empty space at the end) #: UI/ExprCurve.cpp:276 Selected Position: (2 empty spaces at the end) #: UI/ExprColorCurve.cpp:380 Selected Color: (2 empty spaces at the end) #: UI/ExprCurve.cpp:287 Selected Value: (2 empty spaces at the end) Possible correction(s): Can we use 1 space in all of them, or is there a reason to use 2 spaces? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 426196] New: Dolphin can incorrectly move files/folders while holding down the Control key
https://bugs.kde.org/show_bug.cgi?id=426196 Bug ID: 426196 Summary: Dolphin can incorrectly move files/folders while holding down the Control key Product: dolphin Version: 20.08.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: umbreon.does.j...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Dolphin can incorrectly move files/folders while holding down the Control key STEPS TO REPRODUCE 1. mkdir -p ~/test/test2 2. touch ~/test/test2/file.txt 3. Open ~/test/test2/ in Dolphin 4. Open ~/test/ in a new Dolphin window (using another window is important; the issue seems to not occur if using tabs within the same Dolphin window) 5. WITHOUT holding down the Control key and WITHOUT releasing the left mouse button, drag ~/test/test2/file.txt to ~/test 6. After the mouse is finished moving, hold down the Control key WITHOUT moving the mouse any further, and then release the left mouse button OBSERVED RESULT After releasing the left mouse button, file.txt is moved from ~/test/test2 into ~/test rather than being copied. EXPECTED RESULT After releasing the left mouse button, file.txt should be copied from ~/test/test2 into ~/test. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon Unstable Edition KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION I noticed that if I use a single Dolphin window (with ~/test/test2 and ~/test as separate tabs) to perform the file copy operation, the issue seems to not occur. Issue does not occur when running Kubuntu 20.04.1 LTS from a live image. (Dolphin version 19.12.3) Issue occurs when running neon-user-20200827-0945.iso from a live image. (Dolphin version 20.08.0) Issue occurs when running neon-testing-20200901-1829.iso from a live image. (Dolphin version 20.08.0) Issue occurs when running neon-unstable-20200830-0330.iso from a live image. (Dolphin version 20.11.70) Issue still occurs after installing KDE neon Unstable Edition and updating all packages. (Dolphin version 20.11.70) The system I first encountered this issue on is running Manjaro, but this does not seem to be a Manjaro-specific issue. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425765] Konsole scrollback stutter when fingers are lifted during scrolling using touchpad
https://bugs.kde.org/show_bug.cgi?id=425765 Kevin Wilson changed: What|Removed |Added CC||l.gae...@gmail.com --- Comment #4 from Kevin Wilson --- *** Bug 425456 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425456] Trackpoint Scrolling in Konsole broken since 20.07
https://bugs.kde.org/show_bug.cgi?id=425456 Kevin Wilson changed: What|Removed |Added CC||kwil...@sc.edu Resolution|--- |DUPLICATE Status|REPORTED|NEEDSINFO --- Comment #1 from Kevin Wilson --- Hi there, I think that this bug likely is a duplicate of https://bugs.kde.org/show_bug.cgi?id=425765 . Does the patch attached to that bug fix your problem? *** This bug has been marked as a duplicate of bug 425765 *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 425765] Konsole scrollback stutter when fingers are lifted during scrolling using touchpad
https://bugs.kde.org/show_bug.cgi?id=425765 Kevin Wilson changed: What|Removed |Added Attachment #131289|0 |1 is obsolete|| CC||kwil...@sc.edu --- Comment #3 from Kevin Wilson --- Created attachment 131425 --> https://bugs.kde.org/attachment.cgi?id=131425=edit adjusts previous version of patch to make it apply cleanly to konsole-20.08.1 (In reply to Gabriele from comment #2) > Created attachment 131289 [details] > Handle diagonal scrolling > > Hi, I found the problem and fixed it. Unfortunately I forgot my password and > username, apparently the email alone is not enough to recover the password, > so I'll just attach the patch here with a temp account I've just created. > Hopefully I'll be able to recover my credentials. I confirm that (a) the problem still exists in konsole-20.08.1, and (b) your patch solves it. Great! Thanks for tracking down the bug. The patch needed a minor change because since the last konsole release, the file TerminalDisplay.cpp moved out of the subdirectory in which it used to live. I've attached a modified version that applies to konsole-20.08.1, leaving all of the original author's information unaltered. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 324393] To avoid repetitive screen configuration actions, kscreen should have a way of saving commonly used screen profiles
https://bugs.kde.org/show_bug.cgi?id=324393 jamese changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #21 from jamese --- Hello I'm now using KDE Neon 20.04 packages and the original issue is fixed and has been for a while, at least on Neon. When I plug my screens in via a dock the last known configuration for those screens is loaded. I sometimes have a weird flickering/non-sleep-wake-up thing going on but I'll put that down to a crappy DisplayPort implementation from Dell in their U2414H screens which I'll fix by buying a new screen :D Thanks for the work put into Kscreen over the years. I'll mark this as resolved and someone else can reopen it if needed. Current package: $ pkcon get-details kscreen Resolving [=] Getting details [=] Waiting in queue [=] Loading cache [=] Finished [=] Package description package: kscreen-4:5.19.5-0xneon+20.04+focal+build8.amd64 summary: KDE monitor hotplug and screen handling license: unknown group: desktop-kde description: KScreen provides multiple monitor support. This support tries to be as smart as possible adapting the behavior of it to each use case making the configuration of monitors as simple as plugging them into your computer. This package contains the modules and plugins for monitor hotplug and automatic screen handling. size:1277952 bytes url: https://projects.kde.org/projects/kde/workspace/kscreen Cheers J -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 426195] New: Plasma session crash after returning from wayland session.
https://bugs.kde.org/show_bug.cgi?id=426195 Bug ID: 426195 Summary: Plasma session crash after returning from wayland session. Product: frameworks-baloo Version: 5.68.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: stefan.bru...@rwth-aachen.de Reporter: empathd...@gmail.com Target Milestone: --- Application: baloo_file (5.68.0) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-45-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Just initiate the normal plasma session after endind the wayland session. - Unusual behavior I noticed: It crashes and most of the time I cannot generate bactracing in plasma session. - Custom settings of the application: None change on baloo_file_extractor or db mechanisms was done. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __GI___libc_read (nbytes=16, buf=0x7fff4058baa0, fd=3) at ../sysdeps/unix/sysv/linux/read.c:26 [Current thread is 1 (Thread 0x7f3c08325c80 (LWP 8464))] Thread 3 (Thread 0x7f3c0727c700 (LWP 8573)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x7f3c0bbb9859 in __GI_abort () at abort.c:79 #8 0x7f3c0b23ba83 in mdb_assert_fail (env=0x55e2ad710600, expr_txt=expr_txt@entry=0x7f3c0b23e02f "rc == 0", func=func@entry=0x7f3c0b23e978 <__func__.7221> "mdb_page_dirty", line=line@entry=2127, file=0x7f3c0b23e010 "mdb.c") at mdb.c:1542 #9 0x7f3c0b2306d5 in mdb_page_dirty (mp=, txn=0x55e2ad7109f0) at mdb.c:2114 #10 mdb_page_dirty (txn=0x55e2ad7109f0, mp=) at mdb.c:2114 #11 0x7f3c0b231966 in mdb_page_alloc (num=num@entry=1, mp=mp@entry=0x7f3c0727aee8, mc=) at mdb.c:2308 #12 0x7f3c0b231ba3 in mdb_page_touch (mc=mc@entry=0x7f3c0727b420) at mdb.c:2495 #13 0x7f3c0b2337c7 in mdb_cursor_touch (mc=mc@entry=0x7f3c0727b420) at mdb.c:6523 #14 0x7f3c0b2368f9 in mdb_cursor_put (mc=mc@entry=0x7f3c0727b420, key=key@entry=0x7f3c0727b810, data=data@entry=0x7f3c0727b820, flags=flags@entry=0) at mdb.c:6657 #15 0x7f3c0b23976b in mdb_put (txn=0x55e2ad7109f0, dbi=5, key=key@entry=0x7f3c0727b810, data=data@entry=0x7f3c0727b820, flags=flags@entry=0) at mdb.c:9022 #16 0x7f3c0c7124c5 in Baloo::DocumentDB::put (this=this@entry=0x7f3c0727b960, docId=, docId@entry=2704142263366, list=...) at ./src/engine/documentdb.cpp:79 #17 0x7f3c0c743da7 in Baloo::WriteTransaction::replaceDocument (this=0x55e2ad7ea340, doc=..., operations=operations@entry=...) at ./src/engine/writetransaction.cpp:232 #18 0x7f3c0c736b16 in Baloo::Transaction::replaceDocument (this=this@entry=0x7f3c0727bc10, doc=..., operations=operations@entry=...) at ./src/engine/transaction.cpp:295 #19 0x55e2ac5d6cbc in Baloo::UnindexedFileIndexer::run (this=0x55e2ad79ca20) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qrefcount.h:60 #20 0x7f3c0c177f82 in QThreadPoolThread::run (this=0x55e2ad717f20) at thread/qthreadpool.cpp:99 #21 0x7f3c0c1749d2 in QThreadPrivate::start (arg=0x55e2ad717f20) at thread/qthread_unix.cpp:361 #22 0x7f3c0b29d609 in start_thread (arg=) at pthread_create.c:477 #23 0x7f3c0bcb6103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f3c07d8f700 (LWP 8472)): #0 0x7f3c0bca996f in __GI___poll (fds=0x7f3c29e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f3c0ab8b1ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3c0ab8b2e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3c0c394583 in QEventDispatcherGlib::processEvents (this=0x7f3c0b60, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7f3c0c33b4db in QEventLoop::exec (this=this@entry=0x7f3c07d8ed70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #5 0x7f3c0c173785 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #6 0x7f3c0c76aefa in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f3c0c1749d2 in QThreadPrivate::start (arg=0x7f3c0c7edd80) at thread/qthread_unix.cpp:361 #8 0x7f3c0b29d609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f3c0bcb6103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f3c08325c80 (LWP 8464)): #0 __GI___libc_read (nbytes=16, buf=0x7fff4058baa0, fd=3) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=3, buf=0x7fff4058baa0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f3c0abd389f in ?? ()
[plasmashell] [Bug 424879] plasmashell aborted shortly after logging in with the error The Wayland connection experienced a fatal error: Invalid argument
https://bugs.kde.org/show_bug.cgi?id=424879 --- Comment #7 from Matt Fagnani --- Created attachment 131424 --> https://bugs.kde.org/attachment.cgi?id=131424=edit New crash information added by DrKonqi plasmashell (5.19.5) using Qt 5.14.2 - What I was doing when the application crashed: I was using Plasma 5.19.5 on Wayland in Fedora 33. I set desktop to use the Application Menu by right-clicking on the button at the bottom left of the screen, selecting Show Alternatives > Application Menu > Switch. I clicked to open the Application Menu. I right clicked on the Kate and Konsole icons at the left side of the Application menu 4 times. The Task Manager at the bottom of the screen disappeared, they background went black, and they reappeared automatically. plasmashell aborted with the message The Wayland connection experienced a fatal error: Invalid argument. The journal at the time of the crash had the following. Sep 04 20:40:10 plasmashell[7606]: kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55d9c6ecabc0) Sep 04 20:40:10 plasmashell[7606]: kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55d9c6ecabc0) Sep 04 20:40:11 plasmashell[7606]: QQmlComponent: Created graphical object was not placed in the graphics scene. Sep 04 20:40:11 plasmashell[7606]: QQmlComponent: Created graphical object was not placed in the graphics scene. Sep 04 20:40:11 plasmashell[7606]: QQmlComponent: Created graphical object was not placed in the graphics scene. Sep 04 20:40:11 plasmashell[7606]: QQmlComponent: Created graphical object was not placed in the graphics scene. Sep 04 20:40:11 plasmashell[7606]: QQmlComponent: Created graphical object was not placed in the graphics scene. Sep 04 20:40:11 plasmashell[7606]: QQmlComponent: Created graphical object was not placed in the graphics scene. Sep 04 20:40:11 plasmashell[7606]: QQmlComponent: Created graphical object was not placed in the graphics scene. Sep 04 20:40:11 plasmashell[7606]: QQmlComponent: Created graphical object was not placed in the graphics scene. Sep 04 20:40:11 plasmashell[7606]: QQmlComponent: Created graphical object was not placed in the graphics scene. Sep 04 20:40:11 plasmashell[7606]: qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x55d9c76159f0) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x55d9c67f81a0) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents Sep 04 20:40:11 plasmashell[7606]: kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55d9c6ecabc0) Sep 04 20:40:11 plasmashell[7606]: kf.plasma.quick: Couldn't create KWindowShadow for ToolTipDialog(0x55d9c6ecabc0) Sep 04 20:40:11 plasmashell[7606]: The Wayland connection experienced a fatal error: Invalid argument Sep 04 20:40:12 plasmashell[8628]: kf.plasma.quick: Applet preload policy set to 1 Sep 04 20:40:12 plasmashell[8628]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) I've seen this crash at least 4 times when right-clicking repeatedly on the Kate and Kontact icons on the left of the Application menu. -- Backtrace (Reduced): #4 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7f6ee512d8a4 in __GI_abort () at abort.c:79 #6 0x7f6ee554fa7f in qt_message_fatal (message=..., context=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=this@entry=0x7ffc433e4ba0, msg=msg@entry=0x7f6ed3d05dc8 "The Wayland connection experienced a fatal error: %s") at global/qlogging.cpp:893 #8 0x7f6ed3c95640 in QtWaylandClient::QWaylandDisplay::checkError (this=) at /usr/include/qt5/QtCore/qlogging.h:90 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375951] locally integrated menus
https://bugs.kde.org/show_bug.cgi?id=375951 Geekley changed: What|Removed |Added CC||mrgeek...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424322] Switch user does not work
https://bugs.kde.org/show_bug.cgi?id=424322 Geekley changed: What|Removed |Added CC||mrgeek...@gmail.com --- Comment #8 from Geekley --- I just reported a possible duplicate of this, with additional info. https://bugs.kde.org/show_bug.cgi?id=426194 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426194] OS Soft-lock when locking screen and switching back to the same user; running session isn't restored
https://bugs.kde.org/show_bug.cgi?id=426194 --- Comment #2 from Geekley --- Oops, just noticed possible duplicate: https://bugs.kde.org/show_bug.cgi?id=424322 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426194] OS Soft-lock when locking screen and switching back to the same user; running session isn't restored
https://bugs.kde.org/show_bug.cgi?id=426194 --- Comment #1 from Geekley --- Output of Command: apt list *sddm* | grep installed kde-config-sddm/focal,now 4:5.18.4.1-0ubuntu1 amd64 [installed,automatic] sddm-theme-breeze/focal-updates,now 4:5.18.5-0ubuntu0.1 amd64 [installed,automatic] sddm/focal,now 0.18.1-1ubuntu2 amd64 [installed,automatic] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426194] New: OS Soft-lock when locking screen and switching back to the same user; running session isn't restored
https://bugs.kde.org/show_bug.cgi?id=426194 Bug ID: 426194 Summary: OS Soft-lock when locking screen and switching back to the same user; running session isn't restored Product: plasmashell Version: 5.18.5 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: Lock/logout Assignee: plasma-b...@kde.org Reporter: mrgeek...@gmail.com Target Milestone: 1.0 SUMMARY When locking Plasma session, and clicking switch user, I can't go back to same user (unlock session) in SDDM. Plasma tries to start new session, but shows nothing. Whole system soft-locks and can't be interacted with. Keystrokes don't work. Can't recover from this state without a shutdown. STEPS TO REPRODUCE Steps I tested: 0a. (have multiple user accounts, may be relevant) 0b. (you may want to open some app; but make sure no important apps / files are open since you'll have to force a shutdown) 0c. (you may want to set some FG and BG apps to load on startup, to see the missing title bar effect) 0d. (not sure if relevant, but in System Settings > Startup and Shutdown > Desktop Session, you may want to set it to "Start with empty session") 1. Lock screen (META+L) 2. Click switch user 3. Choose same user, type password, enter 4. Wait for Plasma startup animation 5. There is a black screen / BG; system soft-locks 6. Test various keystrokes; but can only use power button here (press, no need to hold); takes a while to shutdown or reboot Combinations that I didn't test, but might cause this too: - Using Menu > Leave > Lock Screen (instead of shortcut) - PROBABLY YES - Switch user directly (without Lock Screen first) - PROBABLY NOT - Switch to different user, then back (using various methods) - PROBABLY NOT - Anything involving terminal (CTRL+ALT+F7 / CTRL+ALT+F1) - NO IDEA OBSERVED RESULT After entering password, previous session isn't restored / unlocked. Plasma/Breeze presentation screen is shown, as if trying to start a new session. It seems to fail to start a new session. BG / Plasma UI isn't loaded, so a black screen is shown. The apps configured to load on startup are loaded (and seem kind of interactable), but windows have no title bar. The apps that were open when locked session are nowhere to be seen, but I assume they're still running. The taskbar / task manager panel isn't loaded. OS Keyboard shortcuts (such as CTRL+ALT+DEL) don't seem to work as expected (should show options to logout, etc). I think CTRL+ALT+F7 / CTRL+ALT+F1 doesn't work either. Unable to recover from this state (soft-lock? hang?). The only thing that seems to work is pressing (no need to hold) the laptop power button. When I do that, screen goes black. After long wait, it shuts down or reboots the computer "gracefully" (I hope?). EXPECTED RESULT Screen should be unlocked, and all apps from running session should be restored. SOFTWARE/OS VERSIONS OS: Kubuntu 20.04 64-bit Linux Kernel: 5.4.0-45-generic KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Output of Command: apt list plasma* | grep installed plasma-browser-integration/focal-updates,now 5.18.5-0ubuntu0.1 amd64 [installed,automatic] plasma-calendar-addons/focal,now 4:5.18.4.1-0ubuntu2 amd64 [installed,automatic] plasma-dataengines-addons/focal,now 4:5.18.4.1-0ubuntu2 amd64 [installed,automatic] plasma-desktop-data/focal-updates,focal-updates,now 4:5.18.5-0ubuntu0.1 all [installed,automatic] plasma-desktop/focal-updates,now 4:5.18.5-0ubuntu0.1 amd64 [installed,automatic] plasma-discover-backend-fwupd/focal-updates,now 5.18.5-0ubuntu0.1 amd64 [installed,automatic] plasma-discover-backend-snap/focal-updates,now 5.18.5-0ubuntu0.1 amd64 [installed,automatic] plasma-discover-common/focal-updates,focal-updates,now 5.18.5-0ubuntu0.1 all [installed,automatic] plasma-discover-snap-backend/focal-updates,focal-updates,now 5.18.5-0ubuntu0.1 all [installed,automatic] plasma-discover/focal-updates,now 5.18.5-0ubuntu0.1 amd64 [installed,automatic] plasma-framework/focal,now 5.68.0-0ubuntu1 amd64 [installed,automatic] plasma-integration/focal,now 5.18.4.1-0ubuntu2 amd64 [installed,automatic] plasma-nm/focal-updates,now 4:5.18.4.1-0ubuntu1.1 amd64 [installed,automatic] plasma-pa/focal-updates,now 4:5.18.5-0ubuntu0.1 amd64 [installed,automatic] plasma-runners-addons/focal,now 4:5.18.4.1-0ubuntu2 amd64 [installed,automatic] plasma-thunderbolt/focal,now 5.18.4.1-0ubuntu1 amd64 [installed,automatic] plasma-vault/focal-updates,now 5.18.5-0ubuntu0.1 amd64 [installed,automatic] plasma-wallpapers-addons/focal,now 4:5.18.4.1-0ubuntu2 amd64 [installed,automatic] plasma-widgets-addons/focal,now 4:5.18.4.1-0ubuntu2 amd64 [installed,automatic] plasma-workspace/focal-updates,now 4:5.18.5-0ubuntu0.1 amd64 [installed,automatic] ADDITIONAL INFORMATION When I talk about "restoring session" I mean unlocking screen,
[kfontview] [Bug 426189] Kfontview is missing from Neon Unstable 5.19.80
https://bugs.kde.org/show_bug.cgi?id=426189 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- Fonts kcm is missing too. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 426192] Kinfocenter shows "Highlight Changed Settings" but there are no settings to be changed
https://bugs.kde.org/show_bug.cgi?id=426192 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 425964 *** -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 425964] Pointless "Highlight changed settings" feature
https://bugs.kde.org/show_bug.cgi?id=425964 Patrick Silva changed: What|Removed |Added CC||guimarcalsi...@gmail.com --- Comment #2 from Patrick Silva --- *** Bug 426192 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 413504] Brush outline (and also stroke) lags significantly on 4k displays
https://bugs.kde.org/show_bug.cgi?id=413504 --- Comment #15 from Dmitry Kazakov --- Hi, Andrei! Could you also check this package (DK14)? It is basically the same optimization present in the previous package(DK11), but it has a few bugs fixed. Though this bugfixes could theoretically make it slower, so it would be nice to test both: DK14: https://yadi.sk/d/0CpMkqRjTDL86w PS: This new package should have zooming, background and checkers fixed, though canvas decorations are still disabled. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 426193] New: On wayland, Right click on "Updates available" notification do not show menu and hang the panel
https://bugs.kde.org/show_bug.cgi?id=426193 Bug ID: 426193 Summary: On wayland, Right click on "Updates available" notification do not show menu and hang the panel Product: Discover Version: 5.19.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifier Assignee: aleix...@kde.org Reporter: luancarvalhomart...@gmail.com Target Milestone: --- SUMMARY Wayland only. A right click on the "Updates available" notification is not opening a menu. There seem to be a glitch of a menu for a fraction of a second. Then the panel gets stuck, it won't hide anymore. STEPS TO REPRODUCE 1. In a Wayland session, right click the "Updates available" notification on the system tray OBSERVED RESULT No menu appears. The panel is now stuck, and won't autohide. EXPECTED RESULT A menu appearing and the autohide working. SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.73.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-18-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-1035G1 CPU @ 1.00GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics ADDITIONAL INFORMATION Bug do not show up on a X session. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 425829] Prompts to run JavaScript files
https://bugs.kde.org/show_bug.cgi?id=425829 Nate Graham changed: What|Removed |Added Version|git master |5.73.0 -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 426192] New: Kinfocenter shows "Highlight Changed Settings" but there are no settings to be changed
https://bugs.kde.org/show_bug.cgi?id=426192 Bug ID: 426192 Summary: Kinfocenter shows "Highlight Changed Settings" but there are no settings to be changed Product: kinfocenter Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: guimarcalsi...@gmail.com CC: hubn...@gmail.com Target Milestone: --- Created attachment 131423 --> https://bugs.kde.org/attachment.cgi?id=131423=edit KinfoCenter window SUMMARY I'm using the latest KDE Neon Unstable Edition (fully updated) and Kinfocenter is showing the new option "Highlight Changed Settings", but it makes no sense to have that option there since as far as I know there's no options to be changed, unlike the system settings app. I'm also using the system in PT-BR but the text is not translated, the same button is translated in system settings. I won't fill another bug report about the translation because I believe the button shouldn't be there anyway. OBSERVED RESULT Kinfocenter shows "Highlight Changed Settings". EXPECTED RESULT Kinfocenter shouldn't show that option. The option has no effect since there's no options to be changed in Kinfocenter. SOFTWARE/OS VERSIONS Linux/KDE Plasma:5.19.80 (available in About System) KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.4.0-45-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-9400F CPU @ 2.90GHz Memory: 3.8 GiB of RAM Graphics Processor: SVGA3D; build: RELEASE; LLVM; -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 426192] Kinfocenter shows "Highlight Changed Settings" but there are no settings to be changed
https://bugs.kde.org/show_bug.cgi?id=426192 guimarcalsi...@gmail.com changed: What|Removed |Added CC||guimarcalsi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 426191] New: Gwinview Crash while browsing images.
https://bugs.kde.org/show_bug.cgi?id=426191 Bug ID: 426191 Summary: Gwinview Crash while browsing images. Product: gwenview Version: 19.12.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: scoob...@yahoo.com Target Milestone: --- Application: gwenview (19.12.1) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.8.4-200.fc32.x86_64 x86_64 Windowing system: X11 Distribution: "Fedora release 32 (Thirty Two)" -- Information about the crash: - What I was doing when the application crashed: Pressing Next Button ">" while browsing images. After restart keeps crashing while restarting. The crash can be reproduced every time. -- Backtrace: Application: Gwenview (gwenview), signal: Floating point exception Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f79209aae80 (LWP 11564))] Thread 8 (Thread 0x7f78fcd0d700 (LWP 11576)): [KCrash Handler] #4 0x7f7926c5764d in Gwenview::JpegContent::thumbnail() const () from /lib64/libgwenviewlib.so.5 #5 0x7f7926c6a1ee in Gwenview::ThumbnailContext::load(QString const&, int) () from /lib64/libgwenviewlib.so.5 #6 0x7f7926c6aa4c in Gwenview::ThumbnailGenerator::run() () from /lib64/libgwenviewlib.so.5 #7 0x7f7925203690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7f7923e5d432 in start_thread () from /lib64/libpthread.so.0 #9 0x7f7924e84913 in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7f79088b3700 (LWP 11570)): #0 0x7f7923e63e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f790ae3c6db in util_queue_thread_func () from /usr/lib64/dri/iris_dri.so #2 0x7f790ae3c1ab in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so #3 0x7f7923e5d432 in start_thread () from /lib64/libpthread.so.0 #4 0x7f7924e84913 in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7f79090b4700 (LWP 11569)): #0 0x7f7923e63e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f790ae3c6db in util_queue_thread_func () from /usr/lib64/dri/iris_dri.so #2 0x7f790ae3c1ab in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so #3 0x7f7923e5d432 in start_thread () from /lib64/libpthread.so.0 #4 0x7f7924e84913 in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f79098b5700 (LWP 11568)): #0 0x7f7923e63e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f790ae3c6db in util_queue_thread_func () from /usr/lib64/dri/iris_dri.so #2 0x7f790ae3c1ab in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so #3 0x7f7923e5d432 in start_thread () from /lib64/libpthread.so.0 #4 0x7f7924e84913 in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f790a0b6700 (LWP 11567)): #0 0x7f7923e63e92 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f790ae3c6db in util_queue_thread_func () from /usr/lib64/dri/iris_dri.so #2 0x7f790ae3c1ab in impl_thrd_routine () from /usr/lib64/dri/iris_dri.so #3 0x7f7923e5d432 in start_thread () from /lib64/libpthread.so.0 #4 0x7f7924e84913 in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f7912156700 (LWP 11566)): #0 0x7f7924e754cc in read () from /lib64/libc.so.6 #1 0x7f792360553f in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x7f79235bb5ee in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x7f79235bba55 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #4 0x7f79235bbbe3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7f79253e3b8b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f792539691b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7f7925202427 in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7f7924b1451b in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #9 0x7f7925203690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #10 0x7f7923e5d432 in start_thread () from /lib64/libpthread.so.0 #11 0x7f7924e84913 in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f7913738700 (LWP 11565)): #0 0x7f7924e79aaf in poll () from /lib64/libc.so.6 #1 0x7f792354a38a in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f792354c71a in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f79138aac78 in QXcbEventQueue::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7f7925203690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f7923e5d432 in start_thread () from /lib64/libpthread.so.0 #6 0x7f7924e84913 in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f79209aae80 (LWP 11564)): #0
[kdevelop] [Bug 426190] New: [KDevelop] : C++ code highlighter glitch
https://bugs.kde.org/show_bug.cgi?id=426190 Bug ID: 426190 Summary: [KDevelop] : C++ code highlighter glitch Product: kdevelop Version: 5.5.80 Platform: Compiled Sources OS: All Status: REPORTED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: rjvber...@gmail.com Target Milestone: --- SUMMARY The C++ code highlighter derails in KDMGeneralWidget::loadGuiStyles() STEPS TO REPRODUCE 1. Fetch my KDM5 project from github:RJVB/kdm5.git and import it into KDevelop 2. open kdm/kcm/kdm-gen.cpp and navigate to `KDMGeneralWidget::loadGuiStyles()` OBSERVED RESULT The highlighting and auto-indenting are off from the #else in that function if code is forced to use the #else branch. EXPECTED RESULT It should make no difference if the code has `#if 0` or `#if 1`. SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.60.0 Qt Version: 5.9.8 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #348 from Ernie --- Christoph Feck! So all you can add is don't leave comments? A status update from time to time would be appreciated. The only thing tat gets a response is a few days of bitching by dozens of people who have been kept in the dark for years. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-sonnet] [Bug 420469] Alway report init failed for sonnet and Hspell
https://bugs.kde.org/show_bug.cgi?id=420469 Aurélien Oudelet (auroud85_fr) changed: What|Removed |Added Status|REPORTED|CONFIRMED Platform|Ubuntu Packages |Mageia RPMs Version|unspecified |5.73.0 Ever confirmed|0 |1 CC||aoude...@outlook.com --- Comment #2 from Aurélien Oudelet (auroud85_fr) --- I confirm same behavior with Kwrite. $ kwrite text.txt Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. kf.sonnet.clients.hspell: HSpellDict::HSpellDict: Init failed Operating System: Mageia 8 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.8.6-desktop-1.mga8 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6600K CPU @ 3.50GHz Memory: 15.6 Gio of RAM Graphics Processor: GeForce GTX 1660 Ti/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 426189] New: Kfontview is missing from Neon Unstable 5.19.80
https://bugs.kde.org/show_bug.cgi?id=426189 Bug ID: 426189 Summary: Kfontview is missing from Neon Unstable 5.19.80 Product: kfontview Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: r.griff...@gmail.com Target Milestone: --- SUMMARY Kfontview is missing from Neon Unstable 5.19.80. It's been missing for weeks but I don't know exactly when / if something changed. It's still in 5.19.5. STEPS TO REPRODUCE 1. Open system settings 2. Search for fonts OBSERVED RESULT Fonts (kfontview) is missing. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417040] No pressure at first stamp in floating dock mode
https://bugs.kde.org/show_bug.cgi?id=417040 Dmitry Kazakov changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/4f98a20fb |hics/krita/commit/081c38c87 |f2e64858b28ad22ca809d95c40a |63c94c79b132aafc99f1b087b88 |00be|d421 --- Comment #12 from Dmitry Kazakov --- Git commit 081c38c8763c94c79b132aafc99f1b087b88d421 by Dmitry Kazakov. Committed on 04/09/2020 at 20:27. Pushed by dkazakov into branch 'master'. Fix full-pressure blobs when using floating dockers On Windows tablet events may arrive asynchronously to the mouse events (in WinTab mode). The problem is that Qt generates Enter/Leave and FocusIn/Out events via mouse events only. It means that TabletPress may come much before Enter and FocusIn event and start the stroke. In such a case we shouldn't unblock mouse events. PS: Ideally, we should fix Qt to generate Enter/Leave and FocusIn/Out events based on tablet events as well, but it is a lot of work. M +0-5libs/ui/input/kis_input_manager.cpp M +0-3libs/ui/input/kis_input_manager.h M +21 -0libs/ui/input/kis_input_manager_p.cpp https://invent.kde.org/graphics/krita/commit/081c38c8763c94c79b132aafc99f1b087b88d421 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417040] No pressure at first stamp in floating dock mode
https://bugs.kde.org/show_bug.cgi?id=417040 Dmitry Kazakov changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/4f98a20fb ||f2e64858b28ad22ca809d95c40a ||00be --- Comment #11 from Dmitry Kazakov --- Git commit 4f98a20fbf2e64858b28ad22ca809d95c40a00be by Dmitry Kazakov. Committed on 04/09/2020 at 20:16. Pushed by dkazakov into branch 'krita/4.3'. Fix full-pressure blobs when using floating dockers On Windows tablet events may arrive asynchronously to the mouse events (in WinTab mode). The problem is that Qt generates Enter/Leave and FocusIn/Out events via mouse events only. It means that TabletPress may come much before Enter and FocusIn event and start the stroke. In such a case we shouldn't unblock mouse events. PS: Ideally, we should fix Qt to generate Enter/Leave and FocusIn/Out events based on tablet events as well, but it is a lot of work. M +0-5libs/ui/input/kis_input_manager.cpp M +0-3libs/ui/input/kis_input_manager.h M +21 -0libs/ui/input/kis_input_manager_p.cpp https://invent.kde.org/graphics/krita/commit/4f98a20fbf2e64858b28ad22ca809d95c40a00be -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 426188] New: Open .docx with comments
https://bugs.kde.org/show_bug.cgi?id=426188 Bug ID: 426188 Summary: Open .docx with comments Product: calligrawords Version: 3.2.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: calligra-words-bugs-n...@kde.org Reporter: galanl...@gmail.com Target Milestone: --- Application: calligrawords (3.2.0) Qt Version: 5.14.2 Frameworks Version: 5.73.0 Operating System: Linux 5.4.0-40-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.19 -- Information about the crash: - What I was doing when the application crashed: Trying to open an existing document that includes comments. The crash can be reproduced every time. -- Backtrace: Application: Calligra Words (calligrawords), signal: Segmentation fault [KCrash Handler] #4 0x7f55cf3affbc in QTextLine::y() const () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #5 0x7f55d079fbc8 in KoTextDocumentLayout::positionAnchorTextRanges(int, int, QTextDocument const*) () from /usr/lib/x86_64-linux-gnu/libkotextlayout.so.17 #6 0x7f55d0782470 in KoTextLayoutArea::layoutBlock(FrameIterator*) () from /usr/lib/x86_64-linux-gnu/libkotextlayout.so.17 #7 0x7f55d07851e8 in KoTextLayoutArea::layout(FrameIterator*) () from /usr/lib/x86_64-linux-gnu/libkotextlayout.so.17 #8 0x7f55d079d001 in KoTextLayoutRootArea::layoutRoot(FrameIterator*) () from /usr/lib/x86_64-linux-gnu/libkotextlayout.so.17 #9 0x7f55d07a06a6 in KoTextDocumentLayout::doLayout() () from /usr/lib/x86_64-linux-gnu/libkotextlayout.so.17 #10 0x7f55d07a0d58 in KoTextDocumentLayout::layout() () from /usr/lib/x86_64-linux-gnu/libkotextlayout.so.17 #11 0x7f55d0dbe2a9 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f55d11e2cc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f55d11ebf40 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f55d188483d in KoApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libkomain.so.17 #15 0x7f55d0d9078a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f55d0d92f74 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f55d0de9b87 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f55ce816fbd in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7f55ce817240 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7f55ce8172e3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7f55d0de9251 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f55d0dc6550 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f55d0dc6550 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f55d0230e15 in KoUpdater::sigProgress(int) () from /usr/lib/x86_64-linux-gnu/libkowidgetutils.so.17 #25 0x7f55d188e056 in KoDocument::openFile() () from /usr/lib/x86_64-linux-gnu/libkomain.so.17 #26 0x7f55d1894a01 in KoDocument::openUrlInternal(QUrl const&) () from /usr/lib/x86_64-linux-gnu/libkomain.so.17 #27 0x7f55d1895255 in KoDocument::openUrl(QUrl const&) () from /usr/lib/x86_64-linux-gnu/libkomain.so.17 #28 0x7f55d189aff7 in KoMainWindow::openDocumentInternal(QUrl const&, KoPart*, KoDocument*) () from /usr/lib/x86_64-linux-gnu/libkomain.so.17 #29 0x7f55d189e5a7 in KoMainWindow::openDocument(QUrl const&) () from /usr/lib/x86_64-linux-gnu/libkomain.so.17 #30 0x7f55d18a8c0f in KoMainWindow::slotFileOpen() () from /usr/lib/x86_64-linux-gnu/libkomain.so.17 #31 0x7f55d18772f1 in ?? () from /usr/lib/x86_64-linux-gnu/libkomain.so.17 #32 0x7f55d0dc6550 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7f55d11dc846 in QAction::triggered(bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #34 0x7f55d11def18 in QAction::activate(QAction::ActionEvent) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #35 0x7f55d11df82f in QAction::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #36 0x7f55d11e2cc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #37 0x7f55d11ebf40 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #38 0x7f55d188483d in KoApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libkomain.so.17 #39 0x7f55d0d9078a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from
[frameworks-kdeclarative] [Bug 390109] Meta+é etc. hotkeys not working on French AZERTY keyboards
https://bugs.kde.org/show_bug.cgi?id=390109 Nate Graham changed: What|Removed |Added Target Milestone|1.0 |--- Product|plasmashell |frameworks-kdeclarative CC||kdelibs-b...@kde.org Assignee|h...@kde.org|notm...@gmail.com Summary|Meta-1 etc. hotkeys not |Meta+é etc. hotkeys not |working on French AZERTY|working on French AZERTY |keyboards |keyboards Version|5.12.0 |5.73.0 Component|Task Manager and Icons-Only |general |Task Manager| -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 425387] Location bar autosuggestion broken
https://bugs.kde.org/show_bug.cgi?id=425387 Noah Davis changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/kio/commit/955984a1a ||3cc8a64d98e6ddfcc09881a4dd7 ||880a Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Noah Davis --- Git commit 955984a1a3cc8a64d98e6ddfcc09881a4dd7880a by Noah Davis. Committed on 04/09/2020 at 19:47. Pushed by ndavis into branch 'master'. Revert "[KUrlCompletion] Don't append / to completed folders" This reverts commit 9f5f8540112e1178aa54a350f29b542c5de7df68. Revert "Remove / from kurlcompletiontest matches" This reverts commit b167b61de8c8b4b3f601b741dda9bd70a2fc83d9. M +14 -14 autotests/kurlcompletiontest.cpp M +1-1src/widgets/kurlcompletion.cpp https://invent.kde.org/frameworks/kio/commit/955984a1a3cc8a64d98e6ddfcc09881a4dd7880a -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426157] Translation for "Default settings for window decoration" too long to fit in German
https://bugs.kde.org/show_bug.cgi?id=426157 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- pt-br translation is also affected, see bug 417430 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426185] digiKam starts more slowly than previous versions
https://bugs.kde.org/show_bug.cgi?id=426185 --- Comment #1 from Minh Nghia Duong --- (In reply to Maik Qualmann from comment #0) > The file "/usr/share/digikam/facesengine/openface_nn4.small2.v1.t7" is > loaded 10 times per RecognitionPreprocessor. A total of about 40 times at > the start of digiKam. Can't we load the file once and use it multiple times? > > Maik Hi Maik, I am intent to load an array of 10 faces extractor which contain OpenCV DNN Net object in order to accelerate batch processing. These objects can not be copied. However I fail to understand while the DNN Face recognizer is reloaded 4 times before digikam started. Could you explain why the faces management try to reload the face recognizer 4 times, please? Nghia -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420966] After tab-completing to a path (or typing a trailing slash) and hitting enter, Dolphin instead navigates to the first suggested subdirectory of that path
https://bugs.kde.org/show_bug.cgi?id=420966 Noah Davis changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #22 from caulier.gil...@gmail.com --- Note the HD version of the session is under processing by YouTube. Please wait... Gilles -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426187] New: Notification changes its position on the screen when I open hamburger menu of Notifications applet
https://bugs.kde.org/show_bug.cgi?id=426187 Bug ID: 426187 Summary: Notification changes its position on the screen when I open hamburger menu of Notifications applet Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: k...@privat.broulik.de Reporter: bugsefor...@gmx.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 131422 --> https://bugs.kde.org/attachment.cgi?id=131422=edit screen recording SUMMARY Watch the attached screen recording please. EXPECTED RESULT notification should remain positioned above popup of Notifications applet when we open the hamburger menu. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #21 from caulier.gil...@gmail.com --- See my face detection session with 7.2.0-beta2 Appimage bundle: https://youtu.be/KnJVSsu0nX8 There is no memory leak here, no crash at all. Best Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426186] Lots of error messages from ItemAlbumModel
https://bugs.kde.org/show_bug.cgi?id=426186 Maik Qualmann changed: What|Removed |Added CC||kartikx2...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426186] New: Lots of error messages from ItemAlbumModel
https://bugs.kde.org/show_bug.cgi?id=426186 Bug ID: 426186 Summary: Lots of error messages from ItemAlbumModel Product: digikam Version: 7.2.0 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-IconView Assignee: digikam-bugs-n...@kde.org Reporter: metzping...@gmail.com Target Milestone: --- Hovering over thumbnails produces many messages like this: digikam.general: Invalid index for extraData QModelIndex(13,0,0x0,Digikam::ItemAlbumModel(0x14b3850)) digikam.general: Invalid index for extraData QModelIndex(14,0,0x0,Digikam::ItemAlbumModel(0x14b3850)) digikam.general: Invalid index for extraData QModelIndex(14,0,0x0,Digikam::ItemAlbumModel(0x14b3850)) digikam.general: Invalid index for extraData QModelIndex(14,0,0x0,Digikam::ItemAlbumModel(0x14b3850)) digikam.general: Invalid index for extraData QModelIndex(14,0,0x0,Digikam::ItemAlbumModel(0x14b3850)) digikam.general: Invalid index for extraData QModelIndex(14,0,0x0,Digikam::ItemAlbumModel(0x14b3850)) digikam.general: Invalid index for extraData QModelIndex(14,0,0x0,Digikam::ItemAlbumModel(0x14b3850)) Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426185] digiKam starts more slowly than previous versions
https://bugs.kde.org/show_bug.cgi?id=426185 Maik Qualmann changed: What|Removed |Added CC||minhnghiaduong...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426185] New: digiKam starts more slowly than previous versions
https://bugs.kde.org/show_bug.cgi?id=426185 Bug ID: 426185 Summary: digiKam starts more slowly than previous versions Product: digikam Version: 7.2.0 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Recognition Assignee: digikam-bugs-n...@kde.org Reporter: metzping...@gmail.com Target Milestone: --- The file "/usr/share/digikam/facesengine/openface_nn4.small2.v1.t7" is loaded 10 times per RecognitionPreprocessor. A total of about 40 times at the start of digiKam. Can't we load the file once and use it multiple times? Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #20 from Maik Qualmann --- Marcel, it would be good if you would test the change. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #19 from Maik Qualmann --- Git commit bd222b146bc7516378646efd3fff8ac5bf7bb737 by Maik Qualmann. Committed on 04/09/2020 at 19:07. Pushed by mqualmann into branch 'master'. disable loading notification for a test M +1-1core/libs/threadimageio/fileio/loadsavetask.cpp M +1-1core/libs/threadimageio/preview/previewtask.cpp M +1-1core/libs/threadimageio/thumb/thumbnailtask.cpp https://invent.kde.org/graphics/digikam/commit/bd222b146bc7516378646efd3fff8ac5bf7bb737 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 343655] Previous/Next blending modes don't follow one another abiding by the drop-down menu list
https://bugs.kde.org/show_bug.cgi?id=343655 Dmitry Kazakov changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/33fa2048a |hics/krita/commit/d301b76c9 |39427f58c8e1f873e95e2bc4ec9 |62534de849557ad09bb062f933f |b23f|ae89 --- Comment #5 from Dmitry Kazakov --- Git commit d301b76c962534de849557ad09bb062f933fae89 by Dmitry Kazakov. Committed on 04/09/2020 at 18:55. Pushed by dkazakov into branch 'krita/4.3'. Reenable Next/Prev Blendign Mode shortcuts They were disabled in 2015 because iteration didn't work in a simple way. And my recent fixes for Mouse Wheel and Up/Down keys has solved the issue. M +2-2krita/krita.action M +4-4libs/ui/widgets/kis_cmb_composite.cc https://invent.kde.org/graphics/krita/commit/d301b76c962534de849557ad09bb062f933fae89 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422919] brushes Blending modes's shortcutes are not work.
https://bugs.kde.org/show_bug.cgi?id=422919 Dmitry Kazakov changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/4a7ebe992 |hics/krita/commit/75e33fc1c |44cb3ce9980def209a71574fb91 |93e6ab171c4df8054f0bd49c789 |176e|d953 --- Comment #2 from Dmitry Kazakov --- Git commit 75e33fc1c93e6ab171c4df8054f0bd49c789d953 by Dmitry Kazakov. Committed on 04/09/2020 at 18:54. Pushed by dkazakov into branch 'krita/4.3'. Fix blending mode shortcuts when using non-English locale Actions should not use translated strings as action-ids. M +1-3libs/ui/kis_paintop_box.cc M +69 -176 libs/ui/widgets/kis_cmb_composite.cc M +4-2libs/ui/widgets/kis_cmb_composite.h https://invent.kde.org/graphics/krita/commit/75e33fc1c93e6ab171c4df8054f0bd49c789d953 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #18 from Maik Qualmann --- Another problematic feature of the preview loader is the loading notification. This is only used by a single function in digiKam. It's the color properties tab. The idea is good, if in the meantime another thread has already loaded the image completely, the current request is canceled and the new image requested. I debugged it. The chance of it entering was zero after 1 hour of intensive use. But thousands of notifications were sent about the addresses stored in the loading cache, if one of these taks no longer exists in the meantime, it would crash. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417040] No pressure at first stamp in floating dock mode
https://bugs.kde.org/show_bug.cgi?id=417040 --- Comment #10 from Dmitry Kazakov --- Yes, I can reproduce the problem (even with a Huion tablet). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #17 from Maik Qualmann --- I think a unit test won't help. The problem is that all processes are brought together via the static loading cache, including the thumbnail threads / tasks. Unfortunately, I and apparently you cannot reproduce the crash. All loading tasks use a non-recursive mutex because a QWaitCondition is used. But this also means that all processes start when the mutex is unlocked. I hope that the problem with calling the wrong overloaded function due to my change to explicit float type in the progress info function is a thing of the past, so far this crash has not been reported again. Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 343655] Previous/Next blending modes don't follow one another abiding by the drop-down menu list
https://bugs.kde.org/show_bug.cgi?id=343655 Dmitry Kazakov changed: What|Removed |Added CC||dimul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 343655] Previous/Next blending modes don't follow one another abiding by the drop-down menu list
https://bugs.kde.org/show_bug.cgi?id=343655 Dmitry Kazakov changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/33fa2048a ||39427f58c8e1f873e95e2bc4ec9 ||b23f Resolution|LATER |FIXED --- Comment #4 from Dmitry Kazakov --- Git commit 33fa2048a39427f58c8e1f873e95e2bc4ec9b23f by Dmitry Kazakov. Committed on 04/09/2020 at 18:42. Pushed by dkazakov into branch 'master'. Reenable Next/Prev Blendign Mode shortcuts They were disabled in 2015 because iteration didn't work in a simple way. And my recent fixes for Mouse Wheel and Up/Down keys has solved the issue. M +2-2krita/krita.action M +4-4libs/ui/widgets/kis_cmb_composite.cc https://invent.kde.org/graphics/krita/commit/33fa2048a39427f58c8e1f873e95e2bc4ec9b23f -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422919] brushes Blending modes's shortcutes are not work.
https://bugs.kde.org/show_bug.cgi?id=422919 Dmitry Kazakov changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/4a7ebe992 ||44cb3ce9980def209a71574fb91 ||176e Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Dmitry Kazakov --- Git commit 4a7ebe99244cb3ce9980def209a71574fb91176e by Dmitry Kazakov. Committed on 04/09/2020 at 18:42. Pushed by dkazakov into branch 'master'. Fix blending mode shortcuts when using non-English locale Actions should not use translated strings as action-ids. M +1-3libs/ui/kis_paintop_box.cc M +69 -176 libs/ui/widgets/kis_cmb_composite.cc M +4-2libs/ui/widgets/kis_cmb_composite.h https://invent.kde.org/graphics/krita/commit/4a7ebe99244cb3ce9980def209a71574fb91176e -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #16 from caulier.gil...@gmail.com --- Maik, Can you remember me which Preview engine call is in fault from the Face detection process ? I want mean, if the face engine call to quickly the preview engine and create race conditions, perhaps we can lock the process step ? Creating a unit test to run Preview Engine in multi-thread with plenty of images to render can help to debug this code. Gilles -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 426130] Ambiguous Shortcuts
https://bugs.kde.org/show_bug.cgi?id=426130 Christoph Feck changed: What|Removed |Added CC||valterm...@gmail.com --- Comment #2 from Christoph Feck --- *** Bug 426179 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 426179] Same shortcut for two different commands in the menu
https://bugs.kde.org/show_bug.cgi?id=426179 Christoph Feck changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 426130 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 426180] dolphin crashes often during opening very big FoldersWhen opening
https://bugs.kde.org/show_bug.cgi?id=426180 --- Comment #1 from Christoph Feck --- Are you using the Tree view mode in Dolphin? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #15 from Maik Qualmann --- Marcel, a GDB backtrace would be good to see in which function it crashes. https://www.digikam.org/contribute/ Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #14 from Maik Qualmann --- The problem is a race condition in the preview loading thread. I've spent a lot of time with it and think I have a good overview of the function. It is programmed very amboned. I have a new idea how the loading notification can be exchanged between the threads safely. I'll be programming a major change for testing. Why the problem mainly occurs under Ubuntu is a mystery to me. Maik -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 426184] Disappearing Album Art
https://bugs.kde.org/show_bug.cgi?id=426184 --- Comment #2 from Norbert Keliher --- Created attachment 131421 --> https://bugs.kde.org/attachment.cgi?id=131421=edit Normal display -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 426184] Disappearing Album Art
https://bugs.kde.org/show_bug.cgi?id=426184 --- Comment #1 from Norbert Keliher --- Created attachment 131420 --> https://bugs.kde.org/attachment.cgi?id=131420=edit Display after scrolling up and down -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 426184] New: Disappearing Album Art
https://bugs.kde.org/show_bug.cgi?id=426184 Bug ID: 426184 Summary: Disappearing Album Art Product: elisa Version: 19.12.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: norbert.keli...@opeast.org Target Milestone: --- Created attachment 131419 --> https://bugs.kde.org/attachment.cgi?id=131419=edit Missing album art after waking up SUMMARY Album art disappears in the library and "now playing" area after logging back in from sleep. STEPS TO REPRODUCE 1. Open Elisa window 2. Put computer to sleep 3. Log back in OBSERVED RESULT I just installed Kubuntu 20.04 and started using pre-installed Elisa for the first time. I noticed that after I put the computer to sleep and then wake it up again, all of the album art displayed in the Elisa window goes solid black. In the "Albums" library this art reappears when I scroll down to other albums and then scroll back up, but in the top of the window the "Now Playing" album stays black. This happens whether or not the Elisa window is minimized. EXPECTED RESULT Album art continues to display. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 426183] New: ktp-morse-telegram - Account configuration doesn't show up
https://bugs.kde.org/show_bug.cgi?id=426183 Bug ID: 426183 Summary: ktp-morse-telegram - Account configuration doesn't show up Product: telepathy Version: 20.04 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kde-telepathy-b...@kde.org Reporter: andrius...@gmail.com Target Milestone: Future SUMMARY STEPS TO REPRODUCE 1. Open "Online Accounts" in systemsettings5 2. Try adding a Telegram account. OBSERVED RESULT It goes back to the previous screen with no indication of error. When opening systemsettigns5 from the terminal it shows: "ktp-morse-telegram" Looking for plugin "ktpaccountskcm_plugin_kaccounts" Adding plugin KAccountsUiProvider(0x5586b47d61f0) "ktpaccountskcm_plugin_kaccounts.so" Unexpected topLevelWindows found: 4 please report a bug Adding service "IM" Qt WebEngine seems to be initialized from a plugin. Please set Qt::AA_ShareOpenGLContexts using QCoreApplication::setAttribute before constructing QGuiApplication. Adding plugin NextcloudWizard(0x5586b4b65bf0) "nextcloud_plugin_kaccounts.so" Unexpected topLevelWindows found: 4 please report a bug Adding plugin OwnCloudWizard(0x5586b4d9fca0) "owncloud_plugin_kaccounts.so" Unexpected topLevelWindows found: 4 please report a bug Requested UI for manager "morse" and protocol "telegram" Creating service for "ktp-morse-telegram" EXPECTED RESULT Telegram Account configuration settings and log-in being shown SOFTWARE/OS VERSIONS Plasma 5.19.80 KDE Frameworks 5.74.0 Qt 5.14.2 Linux 5.4.0-42-generic 64 bit -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426182] New: Wayland session does not start due to error in plasmawayland.desktop
https://bugs.kde.org/show_bug.cgi?id=426182 Bug ID: 426182 Summary: Wayland session does not start due to error in plasmawayland.desktop Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ke...@calvelli.us CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Starting a plasma wayland session from SDDM fails due to error in /usr/share/wayland-sessions/plasmawayland.desktop STEPS TO REPRODUCE 1. From SDDM select Desktop Session: Plasma(Wayland) 2. Enter login credentials 3. OBSERVED RESULT No Wayland session started, screen returns to SDDM EXPECTED RESULT Wayland session started SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: openSUSE Tumbleweed 20200902 (available in About System) KDE Plasma Version: 5.19.80 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION In /usr/share/wayland-sessions/plasmawayland.desktop, line 2: Exec=/usr/lib/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland Should read: Exec=/usr/lib64/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 426067] Same song plays twice back-to-back when shuffling
https://bugs.kde.org/show_bug.cgi?id=426067 --- Comment #2 from PRIZ ;] --- Where can I download the 20.08 version? It doesn't appear in APT. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 416145] Krunner doesn't immediately intercept keystrokes, leading the user to accidentally type text into whatever app is open
https://bugs.kde.org/show_bug.cgi?id=416145 stefanpro...@kolabnow.com changed: What|Removed |Added CC||stefanpro...@kolabnow.com -- You are receiving this mail because: You are watching all bug changes.
[libalkimia] [Bug 426181] German translation not shown in onlinequoteseditor although application language is set to german
https://bugs.kde.org/show_bug.cgi?id=426181 --- Comment #1 from Ralf Habacker --- (In reply to Ralf Habacker from comment #0) > OBSERVED RESULT > Text displayed in the dock windows are not translated to german The issue does not occurs when running the onlinequoteseditor on Linux os with the help of wine e.g. DBUS_SESSION_BUS_ADDRESS= wine bin/onlinequoteseditor.exe The difference is that on Linux the environment variable LANGUAGE is set to the current language, which is not the case on Windows. Setting this variable on Windows before starting onlinequoteseditor or kmymoney with set LANGUAGE=de let the application show the correct translation. Since ki18n uses the same implementation as kdelibs4 in this area, KF5 builds of alkimia (and kmymoney if patched to use alkimia 8.x) are probably also affected by this bug. -- You are receiving this mail because: You are watching all bug changes.
[libalkimia] [Bug 426181] New: German translation not shown in onlinequoteseditor although application language is set to german
https://bugs.kde.org/show_bug.cgi?id=426181 Bug ID: 426181 Summary: German translation not shown in onlinequoteseditor although application language is set to german Product: libalkimia Version: 8.0.3 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: kmymoney-de...@kde.org Reporter: ralf.habac...@freenet.de Target Milestone: --- STEPS TO REPRODUCE 1. Download portable package from KMyMoney snapshots page (Aqbanking6: https://kmymoney.org/snapshots.php#kmymoney4-aq6 or Aqbanking5: https://kmymoney.org/snapshots.php#kmymoney4-aq6) 2. unpack 7z file 3. enter 'bin' dir and start onlinequoteseditor 4. select menu entry "help"->"change application language" and change language to german 5. save and restart onlinequoteseditor OBSERVED RESULT Text displayed in the dock windows are not translated to german EXPECTED RESULT Text displayed in the dock windows should be translated to german SOFTWARE/OS VERSIONS Windows: Windows 10 KDE Version: 4.14.65 Qt Version: 4.8 ADDITIONAL INFORMATION The same issue appears with the "online quotes" settings page opened within kmymoney. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 426180] New: dolphin crashes often during opening very big FoldersWhen opening
https://bugs.kde.org/show_bug.cgi?id=426180 Bug ID: 426180 Summary: dolphin crashes often during opening very big FoldersWhen opening Product: dolphin Version: 20.08.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: boy...@mailbox.org CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (20.08.0) Qt Version: 5.15.0 Frameworks Version: 5.73.0 Operating System: Linux 5.8.4-1-default x86_64 Windowing system: X11 Distribution: openSUSE Tumbleweed -- Information about the crash: - What I was doing when the application crashed: I work with dolphin in 2 window mode. A very large folder (more than 20,000 files) was opened in each window and the files were sorted by date. Then dolphin crashed. Not every time, but often -- Backtrace: Application: Dolphin (dolphin), signal: Aborted [KCrash Handler] #4 0x7f2f0c15b4b1 in raise () from /lib64/libc.so.6 #5 0x7f2f0c144539 in abort () from /lib64/libc.so.6 #6 0x7f2f0c19e827 in __libc_message () from /lib64/libc.so.6 #7 0x7f2f0c1a5b2c in malloc_printerr () from /lib64/libc.so.6 #8 0x7f2f0c1a6e35 in _int_free () from /lib64/libc.so.6 #9 0x7f2f0c06eaae in KFileItemModel::removeItems(KItemRangeList const&, KFileItemModel::RemoveItemsBehavior) () from /usr/lib64/libdolphinprivate.so.5 #10 0x7f2f0c06a39a in KFileItemModel::setExpanded(int, bool) () from /usr/lib64/libdolphinprivate.so.5 #11 0x7f2f0c085ab0 in KItemListController::mouseReleaseEvent(QGraphicsSceneMouseEvent*, QTransform const&) () from /usr/lib64/libdolphinprivate.so.5 #12 0x7f2f0c08a669 in KItemListController::processEvent(QEvent*, QTransform const&) () from /usr/lib64/libdolphinprivate.so.5 #13 0x7f2f0c08e66d in KItemListView::event(QEvent*) () from /usr/lib64/libdolphinprivate.so.5 #14 0x7f2f0ae500cf in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #15 0x7f2f0a23bc3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #16 0x7f2f0b164f35 in ?? () from /usr/lib64/libQt5Widgets.so.5 #17 0x7f2f0b1652d1 in ?? () from /usr/lib64/libQt5Widgets.so.5 #18 0x7f2f0b16aa5c in QGraphicsScene::mouseReleaseEvent(QGraphicsSceneMouseEvent*) () from /usr/lib64/libQt5Widgets.so.5 #19 0x7f2f0b1776b1 in QGraphicsScene::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #20 0x7f2f0ae500cf in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #21 0x7f2f0a23bc3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #22 0x7f2f0b194020 in QGraphicsView::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libQt5Widgets.so.5 #23 0x7f2f0ae900de in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #24 0x7f2f0af384de in QFrame::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #25 0x7f2f0a23b9a3 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #26 0x7f2f0ae500be in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #27 0x7f2f0ae57121 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #28 0x7f2f0a23bc3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #29 0x7f2f0ae56036 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /usr/lib64/libQt5Widgets.so.5 #30 0x7f2f0aea813a in ?? () from /usr/lib64/libQt5Widgets.so.5 #31 0x7f2f0aeab62e in ?? () from /usr/lib64/libQt5Widgets.so.5 #32 0x7f2f0ae500cf in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5 #33 0x7f2f0a23bc3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5 #34 0x7f2f0a73927b in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib64/libQt5Gui.so.5 #35 0x7f2f0a70f51b in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib64/libQt5Gui.so.5 #36 0x7f2f054e6f4a in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #37 0x7f2f080ef2b7 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #38 0x7f2f080ef638 in ?? () from /usr/lib64/libglib-2.0.so.0 #39 0x7f2f080ef6ef in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #40 0x7f2f0a29307f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #41 0x7f2f0a23a5fb in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #42 0x7f2f0a242860 in QCoreApplication::exec() () from
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #13 from Marcel --- I checked my library and there are around 60'000 pics and 3'500 unknown faces and about the same number tagged. The error shows up around 10 to 20 seconds after starting the process. It works on a smaller set of pics. If I can check anything just say it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 423305] Can't bind Meta + !, @, #, etc. anymore for keybindings (i.e. those which involve the shift key)
https://bugs.kde.org/show_bug.cgi?id=423305 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/kdeclarative/-/commi ||t/acd8dd06412b8af1650bfdbf4 ||6eee82b7eaef5ca Status|CONFIRMED |RESOLVED Version Fixed In||5.74 --- Comment #5 from Nate Graham --- Fixed with https://invent.kde.org/frameworks/kdeclarative/-/commit/acd8dd06412b8af1650bfdbf46eee82b7eaef5ca -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 425048] Picture of the day wallpaper is not cached in /tmp with tmpfs after reboot
https://bugs.kde.org/show_bug.cgi?id=425048 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.20 Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/kdeplasma-addons/-/commi ||t/e7c51a046583213467d5a4d45 ||3334d6e98d61512 --- Comment #10 from Nate Graham --- Fixed with https://invent.kde.org/plasma/kdeplasma-addons/-/commit/e7c51a046583213467d5a4d453334d6e98d61512 -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 415749] When selecting multiple scan areas only first area gets scanned ("Automatic Document Feeder")
https://bugs.kde.org/show_bug.cgi?id=415749 Andrew Ammerlaan changed: What|Removed |Added CC||andrewammerl...@riseup.net --- Comment #1 from Andrew Ammerlaan --- I think I encountered the same (or at least very similar) issue with my Brother MFC-j5320dw on Gentoo Linux. When the "Preview before saving" feature in the settings is enabled, and while trying to scan multiple documents (Using the automatic document feeder), only the first document will get scanned. After the first document has been scanned and after pressing the save button, the rest of the documents will just get pulled through. Disabling the "Preview before saving" feature fixes the issue, and makes the scanner scan multiple documents as expected using the ADF. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 426179] New: Same shortcut for two different commands in the menu
https://bugs.kde.org/show_bug.cgi?id=426179 Bug ID: 426179 Summary: Same shortcut for two different commands in the menu Product: dolphin Version: 20.08.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: valterm...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 131418 --> https://bugs.kde.org/attachment.cgi?id=131418=edit Warning window for Ctrl+H SUMMARY "Show hidden files" and "Donate" have the same shortcut "Ctrl+H" STEPS TO REPRODUCE 1. Open Dolphin 2. Click the hamburger menu 3. Search the items specified above on Summary OBSERVED RESULT You will note that the shortcuts are the same. Also, if you click "Ctrl+H", a window appears warning for ambiguous shortcut, and the command is not executed (screenshot attached). EXPECTED RESULT ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #12 from Minh Nghia Duong --- I will go through this problem while reform faces management in preparation for the portage to DPlugin. I hope I will fund somethings -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #11 from caulier.gil...@gmail.com --- Around 200 000 photo, with JPEG (mostly), RAW, PNG, and TIFF. I use 32 Gb of RAM, so if there is a memory leak, i cannot see the dysfunction, but i already check the system memory while scanning, and it's very stable. Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #10 from Minh Nghia Duong --- (In reply to caulier.gilles from comment #9) How large is your collection? I found that it crashes after found about 3000 faces. Nghia -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #9 from caulier.gil...@gmail.com --- Here under Mageia and Centos, i cannot reproduce the crash. As you know i parsed my huge family collection of photo. So, the difference can be something in the kernel about memory allocation or a different ulimit settings. Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #8 from Minh Nghia Duong --- (In reply to caulier.gilles from comment #7) > Hi Nghia, > > Do you use also a Ubuntu like Linux ? > Yes, I use Ubuntu 18.4. > Gilles -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 425968] [Neon unstable] Starting some applications shows "ambiguous shortcut" window
https://bugs.kde.org/show_bug.cgi?id=425968 Oded Arbel changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #4 from Oded Arbel --- With the current Neon unstable I am now getting the same issue on both CTRL+H and ALT+. (in Dolphin - Gwenview apparently doesn't care as it uses much less shortcut keys and does not have any conflicts on the chosen keys). Please stop putting shortcut keys on "Donate" - it doesn't make any sense as "Donate" is not a frequently used action, let alone two shortcuts! If you are trying to get people to discover the donation option by accidentally triggering the "Donate" action when they hit a shortcut key by mistake, then that is a horrible way to get donations - even nag dialogs are a better option. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 407028] KDE Connect app fails to send files - Write error, SSL exception in logcat
https://bugs.kde.org/show_bug.cgi?id=407028 moshpirit changed: What|Removed |Added CC||a...@openmailbox.org --- Comment #3 from moshpirit --- (In reply to NiO from comment #1) > One extra bit of info: I am able to transmit files from PC to phone without > issue, the problem only exists transferring from phone to PC. Same here. Also, while I get the notification that the file sending failed but I got the file (it's in ~/Downloads). I also noticed that for Android - Android file transmission it fails for files bigger than 200Kb it may (or may not) send the entire file. My guess(*) is that it also depends on the Wifi connection. Maybe for larger files it may start failing with Laptop - Android too (IRL, not just the notification). I tried with a 180 MiB (and again with a 1.8 GiB) and got no problem (of course beyond the failure notification). Here are my devices: Laptop: - OS: Manjaro 20.1 Mikah - Kernel: x86_64 Linux 5.7.17-2-MANJARO - Host: 20351 Lenovo G50-70 - DE: KDE 5.73.0 / Plasma 5.19.4 Android phone: - Host: Xiaomi Redmi Note 7 - OS: Android 10 - Kernel: 4.4.192-perf+ - MIUI: 11 Android Tablet: - Host: Samsung Galaxy Tab S4 - OS: Android 10 - Kernel: 4.4.205-18876299 My laptop and Android devices are up to date. (*) I have no technical knowledge about this, I'm not a developer. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 --- Comment #7 from caulier.gil...@gmail.com --- Hi Nghia, Do you use also a Ubuntu like Linux ? Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426175] Segmentation fault while Faces detection
https://bugs.kde.org/show_bug.cgi?id=426175 caulier.gil...@gmail.com changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426178] Albumfilter on Unknown faces does not work
https://bugs.kde.org/show_bug.cgi?id=426178 Marcel changed: What|Removed |Added CC||maes...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 426178] New: Albumfilter on Unknown faces does not work
https://bugs.kde.org/show_bug.cgi?id=426178 Bug ID: 426178 Summary: Albumfilter on Unknown faces does not work Product: digikam Version: 7.2.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Albums-Filters Assignee: digikam-bugs-n...@kde.org Reporter: maes...@gmail.com Target Milestone: --- SUMMARY After running a face detection, there are lots of "Unknown" faces. Going to the album and filtering the albums on pictures with unknown faces does not show any pictures. By the way, in Digikam 7.2. all unknown faces are ungrouped in one album. Before they ware split into the albums they belong to. So that bug gets more important with this version. STEPS TO REPRODUCE 1. Run face detection on pictures with people 2. Go to album view 3. Select the face tag filter "Unknown" 4. Nothing is shown OBSERVED RESULT Nothing is shown although there are pictures with unknown faces EXPECTED RESULT All pictures with unknown faces SOFTWARE/OS VERSIONS Digikam: Commit 2fdab922ec229c29be1698e9dce59b80dd6cfda6 Linux/KDE Plasma: Kubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 426177] New: Palapeli fails to run
https://bugs.kde.org/show_bug.cgi?id=426177 Bug ID: 426177 Summary: Palapeli fails to run Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Snaps Assignee: neon-b...@kde.org Reporter: sil-...@kryogenix.org CC: neon-b...@kde.org Target Milestone: --- SUMMARY $ palapeli /snap/palapeli/29/kf5-launch: line 209: /snap/palapeli/29/kf5-locale-gen: No such file or directory STEPS TO REPRODUCE 1. Install Palapeli from Ubuntu Software. 2. Run it, and nothing happens. 3. Run it from a terminal to see the above error. SOFTWARE/OS VERSIONS Ubuntu 20.04 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426173] Krita crashes
https://bugs.kde.org/show_bug.cgi?id=426173 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #2 from Boudewijn Rempt --- Also... You don't tell us what you're actually doing. Does this happen when you're making an animation? Or on creating a new image? Does it always happen?? * Check whether manually changing the gpu renderer to Angle makes a different (settings->configure krita->display) * Please also attach the contents of %LOCALAPPDATA%\kritacrash.log. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 375785] Processing layers/filters inside groups with pass through could be disabled if group is invisible
https://bugs.kde.org/show_bug.cgi?id=375785 Dmitry Kazakov changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #2 from Dmitry Kazakov --- As far as I can see from the code and testing, the bug has been fixed :) There are no updates when I paint under a pass-though group with adjustment layers. -- You are receiving this mail because: You are watching all bug changes.
