Your message dated Mon, 17 Feb 2020 12:45:39 +0100
with message-id <[email protected]>
and subject line Re: Bug#918478: Digikam imageeditor blank screen patch,
backported from Digikam 6.0
has caused the Debian Bug report #918478,
regarding digikam: ImageEditor window is blank when opened a second time
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.)
--
918478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918478
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: digikam
Version: 4:5.9.0-1+b1
Severity: normal
Tags: upstream
Dear Maintainer,
Starting from a clean install of digikam(*), go through the config questions,
find an image and click to open the image editor.
Carefully observe the toolbar buttons at the bottom.
Now close the editor, NOT with the "close editor" button but with the X at the
top right (that is, the close window command), and exit digikam.
Start digikam again and re-enter the editor: you'll now see that the toolbar is
missing.
If the image editor is always closed with the menu button, the issue does not
show up.
Tested on two different "testing" installations.
This is already known upstream: https://bugs.kde.org/show_bug.cgi?id=395875
(*) delete ~/.config/digikamrc and ~/.local/share/kxmlgui5/digikam
-- System Information:
Debian Release: buster/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.20.0-rc6-18.12.13.amdgpu (SMP w/4 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8),
LANGUAGE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages digikam depends on:
ii digikam-data 4:5.9.0-1
ii digikam-private-libs 4:5.9.0-1+b1
ii kipi-plugins 4:5.9.0-1+b1
ii libc6 2.28-2
ii libgcc1 1:8.2.0-13
ii libkf5configcore5 5.51.0-1
ii libkf5coreaddons5 5.51.0-1
ii libkf5filemetadata3 5.51.0-1
ii libkf5i18n5 5.51.0-1
ii libqt5core5a 5.11.3+dfsg-2
ii libqt5gui5 5.11.3+dfsg-2
ii libqt5sql5 5.11.3+dfsg-2
ii libqt5sql5-mysql 5.11.3+dfsg-2
ii libqt5sql5-sqlite 5.11.3+dfsg-2
ii libqt5widgets5 5.11.3+dfsg-2
ii libstdc++6 8.2.0-13
ii perl 5.28.1-3
Versions of packages digikam recommends:
ii ffmpegthumbs 4:18.12.0-1
ii firefox-esr [www-browser] 60.4.0esr-1
ii w3m [www-browser] 0.5.3-36+b1
Versions of packages digikam suggests:
pn digikam-doc <none>
pn systemsettings <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4:6.4.0+dfsg-1
On Thu, Feb 06, 2020 at 12:35:26PM +0100, Agustin Martin wrote:
> On Sat, Nov 09, 2019 at 05:36:07PM -0500, Timothy E. Harris wrote:
> > Because this bug affected me, I backported the patch from Digikam 6.0 to the
> > buster digikam version
>
> Hi,
>
> Thanks for the patch. Steve has just uploaded digikam 6.4.0, which should
> include the fix, to sid. I have minimally tested it and this problem seems
> gone here.
>
> ¿Is it also fixed for you?
Closing bug report. Testing a bit more with 6.4.0 and problem did not
reappear.
Thanks for your contribution to Debian.
Regards,
--
Agustin
--- End Message ---
_______________________________________________
pkg-kde-extras mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-extras
