Your message dated Wed, 21 Nov 2018 22:45:57 -0600
with message-id <3561945.xh2jkAQdEC@riemann>
and subject line Re: digikam: Updated digikam crashes on encountering *.7z files
has caused the Debian Bug report #763590,
regarding digikam: Updated digikam crashes on encountering *.7z files
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 [email protected]
immediately.)
--
763590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763590
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: digikam
Version: 4:4.3.0-1
Severity: normal
Dear Maintainer,
After upgrading digikam and starting it from console, digikam crashes with the
following:
PROMPT> digikam
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QString)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QString)
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.
digikam(9849)/KEXIV2: Cannot load metadata from file (Error # 11 :
<MYDIRCTORY>/<SOMEFILE>.7z: The file contains data of an unknown image type
digikam(9849)/KEXIV2: Cannot load metadata using Exiv2 (Error # 11 :
<NYDIRECTORY>/<SOMEFILE>.7z: The file contains data of an unknown image type
digikam: Fatal IO error: client killed
KCrash: Application 'digikam' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/home/balin/.kde/socket-pc1478/kdeinit4__0
pa_write() failed while trying to wake up the mainloop: Bad file descriptor
pa_write() failed while trying to wake up the mainloop: Bad file descriptor
Assertion 'pa_close(fds[0]) == 0' failed at pulsecore/core-util.c:2516,
function pa_close_pipe(). Aborting.
Unable to start Dr. Konqi
After moving the offending <MYFILE>.7z out of the local library, digikam comes
around to being normal:
PROMPT> digikam
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QString)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QString)
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.
As compared to the former version, this represents a reduction in functionality.
Sincerely, Joh
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages digikam depends on:
ii digikam-data 4:4.3.0-1
ii digikam-private-libs 4:4.3.0-1
ii kde-runtime 4:4.14.1-1
ii libc6 2.19-11
ii libgcc1 1:4.9.1-15
ii libgphoto2-6 2.5.4-1.1+b1
ii libgphoto2-port10 2.5.4-1.1+b1
ii libkdcraw23 4:4.14.0-1
ii libkdecore5 4:4.14.1-1
ii libkdeui5 4:4.14.1-1
ii libkexiv2-11 4:4.14.0-1+b1
ii libkhtml5 4:4.14.1-1
ii libkio5 4:4.14.1-1
ii libkipi11 4:4.13.3-1
ii libknotifyconfig4 4:4.14.1-1
ii libkparts4 4:4.14.1-1
ii libopencv-core2.4 2.4.9.1+dfsg-1
ii libopencv-imgproc2.4 2.4.9.1+dfsg-1
ii libphonon4 4:4.8.0-1
ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2
ii libqt4-sql 4:4.8.6+git64-g5dc8b2b+dfsg-2
ii libqt4-sql-sqlite 4:4.8.6+git64-g5dc8b2b+dfsg-2
ii libqt4-xml 4:4.8.6+git64-g5dc8b2b+dfsg-2
ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-2
ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2
ii libsolid4 4:4.14.1-1
ii libstdc++6 4.9.1-15
ii libthreadweaver4 4:4.14.1-1
ii perl 5.20.1-1
ii phonon 4:4.8.0-1
Versions of packages digikam recommends:
ii chromium [www-browser] 37.0.2062.120-2
ii ffmpegthumbs 4:4.14.1-1
ii iceweasel [www-browser] 31.1.0esr-1
ii kipi-plugins 4:4.3.0-1
ii konqueror [www-browser] 4:4.14.1-1
ii w3m [www-browser] 0.5.3-17
Versions of packages digikam suggests:
pn digikam-doc <none>
ii systemsettings 4:4.11.12-1
-- no debconf information
--- End Message ---
--- Begin Message ---
On Wednesday, October 1, 2014 2:02:54 AM CST you wrote:
> Package: digikam
> Version: 4:4.3.0-1
> Severity: normal
>
> Dear Maintainer,
>
> After upgrading digikam and starting it from console, digikam crashes with
> the following: PROMPT> digikam
> Object::connect: No such signal
> org::freedesktop::UPower::DeviceAdded(QString) Object::connect: No such
> signal org::freedesktop::UPower::DeviceRemoved(QString)
> QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still
> in use, all queries will cease to work. digikam(9849)/KEXIV2: Cannot load
> metadata from file (Error # 11 : <MYDIRCTORY>/<SOMEFILE>.7z: The file
> contains data of an unknown image type digikam(9849)/KEXIV2: Cannot load
> metadata using Exiv2 (Error # 11 : <NYDIRECTORY>/<SOMEFILE>.7z: The file
> contains data of an unknown image type digikam: Fatal IO error: client
> killed
> KCrash: Application 'digikam' crashing...
I can not reproduce the issue, using the following steps:
1. Compress an image with 7z and place in the album folder
2. Start digikam
The .7z file is completely ignored and digikam starts normally.
Closing this bug.
-Steve
--- End Message ---
_______________________________________________
pkg-kde-extras mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-extras
