Your message dated Sat, 30 Apr 2022 13:30:52 -0500
with message-id <4395186.LvFx2qVVIh@riemann>
and subject line Re: Bug#1010057: digikam: Failed when generated data-base
has caused the Debian Bug report #1010057,
regarding digikam: Failed when generated data-base
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1010057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: digikam
Version: 4:7.6.0-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I installed Debian "Bookworm" in order to test this version. When launching
"Digikam" I get a database loading/generation error. Below is the digikam
report file.
In advance I thank you.
Jean Pierre
Application: digiKam (digikam), signal: Segmentation fault
[KCrash Handler]
#4 0x00007fcc44ec91b1 in QReadWriteLock::tryLockForWrite(int) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007fcc4625106b in ?? () from /lib/x86_64-linux-gnu/libQt5Sql.so.5
#6 0x00007fcc46c30a33 in ?? () from /usr/lib/digikam/libdigikamcore.so.7.6.0
#7 0x00007fcc46c30b5d in ?? () from /usr/lib/digikam/libdigikamcore.so.7.6.0
#8 0x00007fcc46c38fce in ?? () from /usr/lib/digikam/libdigikamcore.so.7.6.0
#9 0x00007fcc44eccf1f in QThreadStorageData::finish(void**) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007fcc44ec70ed in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007fcc44ec79c9 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007fcc43034d80 in start_thread () from /lib/x86_64-linux-
gnu/libpthread.so.0
#13 0x00007fcc44ade76f in clone () from /lib/x86_64-linux-gnu/libc.so.6
Thread 11 (Thread 0x7fcc0d04c640 (LWP 16462) "digikam:gdrv0"):
#1 0x00007fcc4303ac30 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#2 0x00007fcc20649beb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#3 0x00007fcc20649847 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4 0x00007fcc43034d80 in start_thread () from /lib/x86_64-linux-
gnu/libpthread.so.0
#5 0x00007fcc44ade76f in clone () from /lib/x86_64-linux-gnu/libc.so.6
Thread 10 (Thread 0x7fcc0d84d640 (LWP 16461) "digikam:sh5"):
#1 0x00007fcc4303ac30 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#2 0x00007fcc20649beb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#3 0x00007fcc20649847 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4 0x00007fcc43034d80 in start_thread () from /lib/x86_64-linux-
gnu/libpthread.so.0
#5 0x00007fcc44ade76f in clone () from /lib/x86_64-linux-gnu/libc.so.6
Thread 9 (Thread 0x7fcc0e04e640 (LWP 16460) "digikam:sh4"):
#1 0x00007fcc4303ac30 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#2 0x00007fcc20649beb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#3 0x00007fcc20649847 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4 0x00007fcc43034d80 in start_thread () from /lib/x86_64-linux-
gnu/libpthread.so.0
#5 0x00007fcc44ade76f in clone () from /lib/x86_64-linux-gnu/libc.so.6
Thread 8 (Thread 0x7fcc189fa640 (LWP 16459) "digikam:sh3"):
#1 0x00007fcc4303ac30 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#2 0x00007fcc20649beb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#3 0x00007fcc20649847 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4 0x00007fcc43034d80 in start_thread () from /lib/x86_64-linux-
gnu/libpthread.so.0
#5 0x00007fcc44ade76f in clone () from /lib/x86_64-linux-gnu/libc.so.6
Thread 7 (Thread 0x7fcc191fb640 (LWP 16458) "digikam:sh2"):
#1 0x00007fcc4303ac30 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#2 0x00007fcc20649beb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#3 0x00007fcc20649847 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4 0x00007fcc43034d80 in start_thread () from /lib/x86_64-linux-
gnu/libpthread.so.0
#5 0x00007fcc44ade76f in clone () from /lib/x86_64-linux-gnu/libc.so.6
Thread 6 (Thread 0x7fcc199fc640 (LWP 16457) "digikam:sh1"):
#1 0x00007fcc4303ac30 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#2 0x00007fcc20649beb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#3 0x00007fcc20649847 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4 0x00007fcc43034d80 in start_thread () from /lib/x86_64-linux-
gnu/libpthread.so.0
#5 0x00007fcc44ade76f in clone () from /lib/x86_64-linux-gnu/libc.so.6
Thread 5 (Thread 0x7fcc1a1fd640 (LWP 16456) "digikam:sh0"):
#1 0x00007fcc4303ac30 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#2 0x00007fcc20649beb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#3 0x00007fcc20649847 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4 0x00007fcc43034d80 in start_thread () from /lib/x86_64-linux-
gnu/libpthread.so.0
#5 0x00007fcc44ade76f in clone () from /lib/x86_64-linux-gnu/libc.so.6
Thread 4 (Thread 0x7fcc1a9fe640 (LWP 16455) "digikam:disk$0"):
#1 0x00007fcc4303ac30 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#2 0x00007fcc20649beb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#3 0x00007fcc20649847 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4 0x00007fcc43034d80 in start_thread () from /lib/x86_64-linux-
gnu/libpthread.so.0
#5 0x00007fcc44ade76f in clone () from /lib/x86_64-linux-gnu/libc.so.6
Thread 3 (Thread 0x7fcc22ba7640 (LWP 16454) "QDBusConnection"):
#1 0x00007fcc47b1a2dc in ?? () from /lib64/ld-linux-x86-64.so.2
#2 0x00007fcc47b202b8 in __tls_get_addr () from /lib64/ld-linux-x86-64.so.2
#3 0x00007fcc44ec6ed6 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x00007fcc45102fda in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007fcc364906e7 in g_main_context_prepare () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#6 0x00007fcc364910fb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7 0x00007fcc364912ef in g_main_context_iteration () from /lib/x86_64-linux-
gnu/libglib-2.0.so.0
#8 0x00007fcc45103166 in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9 0x00007fcc450aa4cb in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007fcc44ec688e in QThread::exec() () from /lib/x86_64-linux-
gnu/libQt5Core.so.5
#11 0x00007fcc435a64d7 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#12 0x00007fcc44ec79c1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007fcc43034d80 in start_thread () from /lib/x86_64-linux-
gnu/libpthread.so.0
#14 0x00007fcc44ade76f in clone () from /lib/x86_64-linux-gnu/libc.so.6
Thread 2 (Thread 0x7fcc23821640 (LWP 16453) "QXcbEventQueue"):
#1 0x00007fcc35b34d02 in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1
#2 0x00007fcc35b3705a in xcb_wait_for_event () from /lib/x86_64-linux-
gnu/libxcb.so.1
#3 0x00007fcc23b31520 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4 0x00007fcc44ec79c1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007fcc43034d80 in start_thread () from /lib/x86_64-linux-
gnu/libpthread.so.0
#6 0x00007fcc44ade76f in clone () from /lib/x86_64-linux-gnu/libc.so.6
Thread 1 (Thread 0x7fcc23fefa40 (LWP 16452) "digikam"):
#1 0x00007fcc4303ac30 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/x86_64-linux-gnu/libpthread.so.0
#2 0x00007fcc44ecd81b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#3 0x00007fcc44ec7699 in QThread::wait(QDeadlineTimer) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x00007fcc475d3c46 in Digikam::ScanController::~ScanController() () from
/usr/lib/digikam/libdigikamgui.so.7.6.0
#5 0x00007fcc475d3d29 in ?? () from /usr/lib/digikam/libdigikamgui.so.7.6.0
#6 0x00007fcc44a1ef77 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#7 0x00007fcc44a1f11a in exit () from /lib/x86_64-linux-gnu/libc.so.6
#8 0x00007fcc3bfaf788 in ?? () from /lib/x86_64-linux-
gnu/libQt5WebEngineCore.so.5
#9 0x7fffffffffffffff in ?? ()
#10 0x0000000000000000 in ?? ()
[Inferior 1 (process 16452) detached]
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages digikam depends on:
ii digikam-data 4:7.6.0-1
ii digikam-private-libs 4:7.6.0-1
ii libc6 2.33-7
ii libgcc-s1 12-20220319-1
ii libkf5configcore5 5.90.0-1
ii libkf5coreaddons5 5.90.0-1
ii libkf5i18n5 5.90.0-1
ii libmagick++-6.q16-8 8:6.9.11.60+dfsg-1.3+b2
ii libqt5core5a 5.15.2+dfsg-16
ii libqt5gui5 5.15.2+dfsg-16
ii libqt5sql5 5.15.2+dfsg-16
ii libqt5sql5-mysql 5.15.2+dfsg-16
ii libqt5sql5-sqlite 5.15.2+dfsg-16
ii libqt5widgets5 5.15.2+dfsg-16
ii libstdc++6 12-20220319-1
ii perl 5.34.0-4
Versions of packages digikam recommends:
ii ffmpegthumbs 4:21.12.3-1.1
ii firefox-esr [www-browser] 91.8.0esr-1
ii konqueror [www-browser] 4:21.12.3-1
ii lynx [www-browser] 2.9.0dev.10-1
Versions of packages digikam suggests:
ii breeze-icon-theme 4:5.90.0-1
pn digikam-doc <none>
ii systemsettings 4:5.24.4-1
-- debconf-show failed
--- End Message ---
--- Begin Message ---
Hello Jean Pierre,
On Wednesday, April 27, 2022 7:15:48 A.M. CDT Hoareau wrote:
> Hello Steve, Thanks for your help and advice. Indeed it is a problem of
> access to my second disk whose owner is 'root'. When I put the pictures
> in the "user" directory, digikam works perfectly. To make it work in
> "root" here is an effective solution that I found on the net: edit a .sh
> file containing: #! /bin/sh export QTWEBENGINE_DISABLE_SANDBOX=1 digikam
> -qwindowtitle %c
>
> and save it in the "root" directory.
>
> You can close this probleme.
Thank you for the update, really appreciate knowing that you have solved the
problem.
Regards,
-Steve
>
> Many Thanks, Cheers.
>
> Jean Pierre
>
> Le 23/04/2022 à 19:31, Steven Robbins a écrit :
> > On Saturday, April 23, 2022 7:23:48 A.M. CDT Hoareau Jean Pierre wrote:
> >> Package: digikam
> >> Version: 4:7.6.0-1
> >> Severity: grave
> >> Justification: renders package unusable
> >>
> >> Dear Maintainer,
> >> I installed Debian "Bookworm" in order to test this version. When
> >> launching
> >> "Digikam" I get a database loading/generation error.
> >
> > Are you using an external DB like mysql/mariadb?
> > Does the workaround in this report help?
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007220
> >
> > If not, can you provide reproduction steps? Digikam 7.6.0 works for me so
> > the reproduction will need explicit configuration steps. Maybe you can
> > configure from scratch for a new folder and share those steps?
> >
> > Regards,
> > -Steve
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
_______________________________________________
pkg-kde-extras mailing list
pkg-kde-extras@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-extras
