[Spectacle] [Bug 473114] New: crashed
https://bugs.kde.org/show_bug.cgi?id=473114 Bug ID: 473114 Summary: crashed Classification: Applications Product: Spectacle Version: 23.04.3 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: mip...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Application: spectacle (23.04.3) Qt Version: 5.15.10 Frameworks Version: 5.108.0 Operating System: Linux 6.2.0-26-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.7 [KCrashBackend] -- Information about the crash: Crashed after restarting, required after unsuccessfully secondary monitor connection. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Spectacle (spectacle), signal: Segmentation fault [KCrash Handler] #4 0x55627a4902b6 in ?? () #5 0x7fc2682f48f4 in QtPrivate::QSlotObjectBase::call (a=0x7fff89abc530, r=0x7fff89abcb10, this=0x55627a7699d0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #6 doActivate (sender=0x7fff89abcab0, signal_index=10, argv=0x7fff89abc530) at kernel/qobject.cpp:3925 #7 0x7fc2682ed9c7 in QMetaObject::activate (sender=, m=m@entry=0x7fc268cc8820 , local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7fff89abc530) at kernel/qobject.cpp:3985 #8 0x7fc268734fe6 in QGuiApplication::screenRemoved (this=, _t1=, _t1@entry=0x55627a6b6a20) at .moc/moc_qguiapplication.cpp:396 #9 0x7fc26876da1c in QScreen::~QScreen (this=0x55627a6b6a20, __in_chrg=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:116 #10 0x7fc26876db9d in QScreen::~QScreen (this=0x55627a6b6a20, __in_chrg=) at kernel/qscreen.cpp:178 #11 0x7fc2687161bb in QWindowSystemInterface::handleScreenRemoved (platformScreen=0x55627a600ab0) at kernel/qwindowsysteminterface.cpp:844 #12 0x7fc25caf8775 in QXcbConnection::destroyScreen (this=this@entry=0x55627a5a3ae0, screen=, screen@entry=0x55627a600ab0) at ./src/plugins/platforms/xcb/qxcbconnection_screens.cpp:269 #13 0x7fc25caf9038 in QXcbConnection::updateScreens (this=0x55627a5a3ae0, event=) at ./src/plugins/platforms/xcb/qxcbconnection_screens.cpp:170 #14 0x7fc25cacbfc0 in QXcbConnection::handleXcbEvent (this=this@entry=0x55627a5a3ae0, event=event@entry=0x7fc250007e70) at ./src/plugins/platforms/xcb/qxcbconnection.cpp:735 #15 0x7fc25caccd96 in QXcbConnection::processXcbEvents (this=0x55627a5a3ae0, flags=...) at ./src/plugins/platforms/xcb/qxcbconnection.cpp:1063 #16 0x7fc25caf4f57 in xcbSourceDispatch (source=) at ./src/plugins/platforms/xcb/qxcbeventdispatcher.cpp:103 #17 0x7fc265d1bd3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7fc265d71258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7fc265d193e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7fc268316338 in QEventDispatcherGlib::processEvents (this=0x55627a6eaab0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #21 0x7fc2682bb76b in QEventLoop::exec (this=this@entry=0x7fff89abc9d0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #22 0x7fc2682c3d14 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #23 0x55627a46a8d7 in ?? () #24 0x7fc267829d90 in __libc_start_call_main (main=main@entry=0x55627a469ef0, argc=argc@entry=1, argv=argv@entry=0x7fff89abcd28) at ../sysdeps/nptl/libc_start_call_main.h:58 #25 0x7fc267829e40 in __libc_start_main_impl (main=0x55627a469ef0, argc=1, argv=0x7fff89abcd28, init=, fini=, rtld_fini=, stack_end=0x7fff89abcd18) at ../csu/libc-start.c:392 #26 0x55627a46b745 in ?? () [Inferior 1 (process 2325) detached] The reporter indicates this bug may be a duplicate of or related to bug 473072, bug 469311, bug 468694, bug 470009. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452997] New: main monitor black
https://bugs.kde.org/show_bug.cgi?id=452997 Bug ID: 452997 Summary: main monitor black Product: kwin Version: 5.24.4 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mip...@gmail.com Target Milestone: --- Application: kwin_x11 (5.24.4) Qt Version: 5.15.3 Frameworks Version: 5.93.0 Operating System: Linux 5.13.0-40-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.24 DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I have a second monitor, the portable one crashed, going black, after closing and re-opening it. Actually it seem it works, even if background is black. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [New LWP 15513] [New LWP 15517] [New LWP 15518] [New LWP 15527] [New LWP 15528] [New LWP 15529] [New LWP 15530] [New LWP 15531] [New LWP 15532] [New LWP 15533] [New LWP 15534] [New LWP 15535] [New LWP 15543] [New LWP 15544] [New LWP 15545] [New LWP 15551] [New LWP 15552] [New LWP 15553] [New LWP 15554] [New LWP 15681] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fc30d0ff9cf in __GI___poll (fds=0x7ffe68c9a278, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7fc30876e9c0 (LWP 15506))] Thread 21 (Thread 0x7fc2b67fc700 (LWP 15681)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x56168078a6e0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56168078a690, cond=0x56168078a6b8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x56168078a6b8, mutex=0x56168078a690) at pthread_cond_wait.c:638 #3 0x7fc3053f45eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7fc3053f41eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7fc30dd91609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fc30d10c163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7fc291ffb700 (LWP 15554)): #0 0x7fc30d0ffac6 in __ppoll (fds=fds@entry=0x7fc27c000d98, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:44 #1 0x7fc30e1ea559 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7fc27c000d98) at kernel/qcore_unix.cpp:132 #3 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7fc27c000d98) at kernel/qcore_unix.cpp:129 #4 qt_safe_poll (fds=0x7fc27c000d98, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:155 #5 0x7fc30e1ebc03 in QEventDispatcherUNIX::processEvents (this=, flags=...) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:211 #6 0x7fc30e19287b in QEventLoop::exec (this=this@entry=0x7fc291ffabe0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #7 0x7fc30dfac442 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #8 0x7fc30dfad623 in QThreadPrivate::start (arg=0x56167fa26e00) at thread/qthread_unix.cpp:331 #9 0x7fc30dd91609 in start_thread (arg=) at pthread_create.c:477 #10 0x7fc30d10c163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7fc2927fc700 (LWP 15553)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x56167fa5dbe0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56167fa5db90, cond=0x56167fa5dbb8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x56167fa5dbb8, mutex=0x56167fa5db90) at pthread_cond_wait.c:638 #3 0x7fc3053f45eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7fc3053f41eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7fc30dd91609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fc30d10c163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7fc292ffd700 (LWP 15552)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x56167fab4868) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x56167fab4818, cond=0x56167fab4840) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x56167fab4840, mutex=0x56167fab4818) at pthread_cond_wait.c:638 #3 0x7fc3053f45eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7fc3053f41eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7fc30dd91609 in start_thread (arg=) at pthread_create.c:477 #6
[digikam] [Bug 451347] Missing Rating info in xmp sidecar, for RAW files (solved)
https://bugs.kde.org/show_bug.cgi?id=451347 mippo changed: What|Removed |Added Summary|Missing Rating info in xmp |Missing Rating info in xmp |sidecar, for RAW files |sidecar, for RAW files ||(solved) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451347] Missing Rating info in xmp sidecar, for RAW files
https://bugs.kde.org/show_bug.cgi?id=451347 --- Comment #5 from mippo --- Thanks Maik for your help, disabling the option "Sidecar Compatible for Commercial Programs", now allows a correct synchronization with both xmp sidecar files and no longer creation of the third xmp file. This option IMHO could create confusion, I selected it in order to have a better compatibility with other program (Darktable) and then forgot it (... or maybe DT is not considered a "Commercial" program ... ;). It could be a good idea to have a visible notice of which setting has been changed from default, or a button able to restore default settings, like in KDE Plasma settings. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451347] Missing Rating info in xmp sidecar, for RAW files
https://bugs.kde.org/show_bug.cgi?id=451347 --- Comment #3 from mippo --- (In reply to mippo from comment #2) > Created attachment 147420 [details] > sample of JPG, ARW picture and related XMP files (26.7MB) > > The 2 xmp files are created by DigiKam which assigned 1 star rating. > This rating is misaligned in xmp files, that is the issue. find here the 26.7 zip file --> https://drive.google.com/file/d/1sJFOWZ3ufdHkkQ1iqObL0rN_iMIv3ckj/view?usp=sharing Also please note that if I add a metadata model, specifically for adding copyright, this will create a new, third, xmp file. As result I have 2 picture files, JPG and ARW files plus 3 xmp files: .ARW.xmp,.JPG.xmp,.xmp -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451347] Missing Rating info in xmp sidecar, for RAW files
https://bugs.kde.org/show_bug.cgi?id=451347 --- Comment #2 from mippo --- Created attachment 147420 --> https://bugs.kde.org/attachment.cgi?id=147420=edit sample of JPG, ARW picture and related XMP files (26.7MB) The 2 xmp files are created by DigiKam which assigned 1 star rating. This rating is misaligned in xmp files, that is the issue. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451347] Missing Rating info in xmp sidecar, for RAW files
https://bugs.kde.org/show_bug.cgi?id=451347 mippo changed: What|Removed |Added CC||mip...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451347] Missing Rating info in xmp sidecar, for RAW files
https://bugs.kde.org/show_bug.cgi?id=451347 mippo changed: What|Removed |Added Summary|Missing Rating info in xmp, |Missing Rating info in xmp |for RAW files |sidecar, for RAW files -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451347] Missing Rating info in xmp, for RAW files
https://bugs.kde.org/show_bug.cgi?id=451347 mippo changed: What|Removed |Added Summary|Missing Rating info in xmp |Missing Rating info in xmp, |for RAW files |for RAW files -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 451347] New: Missing Rating info in xmp for RAW files
https://bugs.kde.org/show_bug.cgi?id=451347 Bug ID: 451347 Summary: Missing Rating info in xmp for RAW files Product: digikam Version: 7.6.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Metadata-Sidecar Assignee: digikam-bugs-n...@kde.org Reporter: mip...@gmail.com Target Milestone: --- SUMMARY The picture rating info, of a RAW picture, are not written in the related xmp sidecar file. Specifically regarding the Star, Flag and Color (not sure about other). Actually they work for the JPG files, but not for RAW files, even if that info are correctly shown in the preview of the GUI interface. Probably, my opinion, is that they are written in the Database, but not in the xmp sidecar file. STEPS TO REPRODUCE 1. select the two files JPG and RAW, related to a same picture, regardless they are "Grouped" or not; 2. apply a Star or a Flag or a Color rating, or even a combination of them; 3. open the TWO xmp files just created, using any text editor ; 4. find the Star, Flag or color setting you applied, in both jpg and RAW sidecar files 5. you will find the correct setting in the jpg xmp file, but not in the RAW xmp file; OBSERVED RESULT see point 5. above EXPECTED RESULT I need the same result settings reflected in both jpg and RAW xmp files, in order to allow some further software manipulation using other tools. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Tried various combination settings in Settings/Configuration/Metadata/Sidecar menu, without success. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 446666] Discover doesn't shows updates and crashes when pressing "information"
https://bugs.kde.org/show_bug.cgi?id=44 --- Comment #1 from mippo --- Created attachment 144340 --> https://bugs.kde.org/attachment.cgi?id=144340=edit Backtrace -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 446666] New: Discover doesn't shows updates and crashes when pressing "information"
https://bugs.kde.org/show_bug.cgi?id=44 Bug ID: 44 Summary: Discover doesn't shows updates and crashes when pressing "information" Product: Discover Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: mip...@gmail.com CC: aleix...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. start Discover 2. (Discover notices me to have 15 items to update, but without any detail about them) 3. if I press the button "Information", then Discover crashes. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 444543] New: KOrganizer crashes when adding new event
https://bugs.kde.org/show_bug.cgi?id=444543 Bug ID: 444543 Summary: KOrganizer crashes when adding new event Product: korganizer Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: mip...@gmail.com Target Milestone: --- Application: korganizer (5.18.2 (21.08.2)) Qt Version: 5.15.3 Frameworks Version: 5.87.0 Operating System: Linux 5.11.0-38-generic x86_64 Windowing System: X11 Distribution: KDE neon User - Plasma 25th Anniversary Edition DrKonqi: 5.23.2 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I was just adding a new event, usingthe default calendar, the first one of the list The crash can be reproduced sometimes. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault [New LWP 1823] [New LWP 1828] [New LWP 1834] [New LWP 1838] [New LWP 1886] [New LWP 1887] [New LWP 1888] [New LWP 1889] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f3c78406aff in __GI___poll (fds=0x7ffe95d60ef8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f3c71386bc0 (LWP 1821))] Thread 9 (Thread 0x7f3c5d6e9700 (LWP 1889)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x556c737a0838) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x556c737a07e8, cond=0x556c737a0810) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x556c737a0810, mutex=0x556c737a07e8) at pthread_cond_wait.c:647 #3 0x7f3c5e833e7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f3c5e833a7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f3c7690f609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f3c78413293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f3c5deea700 (LWP 1888)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x556c737a0838) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x556c737a07e8, cond=0x556c737a0810) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x556c737a0810, mutex=0x556c737a07e8) at pthread_cond_wait.c:647 #3 0x7f3c5e833e7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f3c5e833a7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f3c7690f609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f3c78413293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f3c5e6eb700 (LWP 1887)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x556c737a0838) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x556c737a07e8, cond=0x556c737a0810) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x556c737a0810, mutex=0x556c737a07e8) at pthread_cond_wait.c:647 #3 0x7f3c5e833e7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f3c5e833a7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f3c7690f609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f3c78413293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f3c6ce4c700 (LWP 1886)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x556c737a0838) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x556c737a07e8, cond=0x556c737a0810) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x556c737a0810, mutex=0x556c737a07e8) at pthread_cond_wait.c:647 #3 0x7f3c5e833e7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f3c5e833a7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f3c7690f609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f3c78413293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f3c6dda5700 (LWP 1838)): #0 0x7f3c75e05508 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f3c75db78e1 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3c75db829b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3c75db84a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f3c789ef61b in QEventDispatcherGlib::processEvents (this=0x7f3c58000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f3c789938ab in QEventLoop::exec (this=this@entry=0x7f3c6dda49e0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #6 0x7f3c787ad2c2 in
[dolphin] [Bug 438850] Search does not output any results
https://bugs.kde.org/show_bug.cgi?id=438850 mippo changed: What|Removed |Added CC||mip...@gmail.com --- Comment #9 from mippo --- hello, I have the same problem: in Dolphin the search doesn't work. some more tests: balooshow -x "11" returns something, related to searched item, baloosearch "11" return only a lot of blank lines, maybe proportional to the number of matching items, balooctl status says it's not running, even after enable and resume in /home/.../.config/baloofilerc I tried to set first run=true, and then restart, but nothing happens -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 432388] New: Color tag - I wish more colors
https://bugs.kde.org/show_bug.cgi?id=432388 Bug ID: 432388 Summary: Color tag - I wish more colors Product: digikam Version: 7.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tags-Colors Assignee: digikam-bugs-n...@kde.org Reporter: mip...@gmail.com Target Milestone: --- SUMMARY Could it be possible to increase color tag capability? My wish is to have all colors combination, not one only And possibly make this compatible with Darktable through the Sidecar XMP -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430817] - - -
https://bugs.kde.org/show_bug.cgi?id=430817 mippo changed: What|Removed |Added Summary|In Batch Queue Manager:if I |- - - |have several| -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430818] New: In Batch Queue Manager, the "Run" command, execute always the first queue.
https://bugs.kde.org/show_bug.cgi?id=430818 Bug ID: 430818 Summary: In Batch Queue Manager, the "Run" command, execute always the first queue. Product: digikam Version: 7.1.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: BatchQueueManager Assignee: digikam-bugs-n...@kde.org Reporter: mip...@gmail.com Target Milestone: --- SUMMARY In Batch Queue Manager: if I have several queue, set and ready to be executed, and I press the "RUN" command, then the DK execute always the #1, only the first. regardless of which one I selected before. The "Run all" command execute all of them, correctly. STEPS TO REPRODUCE 1. set some Batch Queue operation, more than one, e.g. 3 ; 2. Try to run only one of them, e.g. the 2nd, that marked as #2; 3. OBSERVED RESULT it seems DK execute ALWAYS the first queue, that marked as #1, only that, regardless of which one I have selected; EXPECTED RESULT I expected DK to execute the 2nd queue, the one I selected, before SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 430817] New: In Batch Queue Manager:if I have several
https://bugs.kde.org/show_bug.cgi?id=430817 Bug ID: 430817 Summary: In Batch Queue Manager:if I have several Product: digikam Version: 7.1.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: BatchQueueManager Assignee: digikam-bugs-n...@kde.org Reporter: mip...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414927] New: Digikam is no longer working
https://bugs.kde.org/show_bug.cgi?id=414927 Bug ID: 414927 Summary: Digikam is no longer working Product: digikam Version: 6.4.0 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: mip...@gmail.com Target Milestone: --- Application: digikam (6.4.0) Qt Version: 5.13.2 Frameworks Version: 5.64.0 Operating System: Linux 4.15.0-72-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: I left PC with some long operation, like search for a new picture or reorder into database. Probably PC stopped or restarted suddenly, maybe damaging database. Now I can't use DK and don't know where ae located databasa files. But anyway, IMHO DK should start anyway, in order to allow user to recover from error. - Custom settings of the application: pictures on NAS, database on PC using mariaDB -- Backtrace: Application: digiKam (digikam), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0d5623b340 (LWP 1673))] Thread 4 (Thread 0x7f0d0357c700 (LWP 1849)): #0 0x7f0d518f89d0 in __GI___nanosleep (requested_time=requested_time@entry=0x7f0d0357b940, remaining=remaining@entry=0x7f0d0357b940) at ../sysdeps/unix/sysv/linux/nanosleep.c:28 #1 0x7f0d524934fd in qt_nanosleep (amount=...) at kernel/qelapsedtimer_unix.cpp:195 #2 0x7f0d555a90d9 in Digikam::DatabaseServer::run() () from /usr/lib/x86_64-linux-gnu/libdigikamcore.so.6.4.0 #3 0x7f0d52250b52 in QThreadPrivate::start (arg=0x5581d8c53840) at thread/qthread_unix.cpp:360 #4 0x7f0d515fc6db in start_thread (arg=0x7f0d0357c700) at pthread_create.c:463 #5 0x7f0d5193588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f0d10ed3700 (LWP 1726)): #0 0x7f0d516029f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x5581d8c41e20) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5581d8c41dd0, cond=0x5581d8c41df8) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5581d8c41df8, mutex=0x5581d8c41dd0) at pthread_cond_wait.c:655 #3 0x7f0d52257aeb in QWaitConditionPrivate::wait (deadline=..., this=0x5581d8c41dd0) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x5581d8c20918, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f0d52257df9 in QWaitCondition::wait (this=0x5581d8c20920, mutex=0x5581d8c20918, time=) at thread/qwaitcondition_unix.cpp:208 #6 0x7f0d5459f2e6 in Digikam::ScanController::run() () from /usr/lib/x86_64-linux-gnu/libdigikamgui.so.6.4.0 #7 0x7f0d52250b52 in QThreadPrivate::start (arg=0x7f0d54eef400) at thread/qthread_unix.cpp:360 #8 0x7f0d515fc6db in start_thread (arg=0x7f0d10ed3700) at pthread_create.c:463 #9 0x7f0d5193588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f0d121c9700 (LWP 1681)): #0 0x7f0d519240b4 in __GI___libc_read (fd=8, buf=0x7f0d121c8760, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f0d461702d0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0d4612b0b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0d4612b570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0d4612b6dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f0d52493b9b in QEventDispatcherGlib::processEvents (this=0x7f0d04000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f0d5243406a in QEventLoop::exec (this=this@entry=0x7f0d121c8970, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f0d5224f3aa in QThread::exec (this=) at thread/qthread.cpp:531 #8 0x7f0d48b9a0e5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f0d52250b52 in QThreadPrivate::start (arg=0x7f0d48e11d80) at thread/qthread_unix.cpp:360 #10 0x7f0d515fc6db in start_thread (arg=0x7f0d121c9700) at pthread_create.c:463 #11 0x7f0d5193588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f0d5623b340 (LWP 1673)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #7 0x7f0d51854801 in __GI_abort () at abort.c:79 #8 0x7f0d5222ccbb in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1907 #9 QMessageLogger::fatal (this=this@entry=0x7fffb035ae50, msg=msg@entry=0x7f0d525213e8 "QThread: Destroyed while thread is still running") at global/qlogging.cpp:888 #10 0x7f0d5224e2fd in QThread::~QThread (this=0x5581d8c53840, __in_chrg=) at thread/qthread.cpp:445 #11 0x7f0d555a9069 in
