Your message dated Fri, 04 Jan 2019 12:33:05 +0100
with message-id <87ftu864jy.fsf@localhost>
and subject line Re: Bug#918050: iv doesn't do anything
has caused the Debian Bug report #918050,
regarding iv doesn't do anything
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.)
--
918050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openimageio-tools
Version: 2.0.3~dfsg0-3
Severity: normal
I used "iv" a couple of times in the past, mostly out of curiosity.
I tried again today since I saw upstream' bug #318 should be fixed (bad
gamma handling).
However, in the last several releases (afaik, since at least 6 months)
it doesn't display any UI when started.
% iv -F IMG_20181228_194324.jpg
(iv:10030): GLib-GObject-WARNING **: 20:41:45.722: cannot register existing
type 'GtkWidget'
(iv:10030): GLib-GObject-CRITICAL **: 20:41:45.722:
g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE
(instance_type)' failed
(iv:10030): GLib-GObject-WARNING **: 20:41:45.722: cannot register existing
type 'GtkBuildable'
(iv:10030): GLib-GObject-CRITICAL **: 20:41:45.722:
g_type_interface_add_prerequisite: assertion 'G_TYPE_IS_INTERFACE
(interface_type)' failed
(iv:10030): GLib-CRITICAL **: 20:41:45.722: g_once_init_leave: assertion
'result != 0' failed
(iv:10030): GLib-GObject-CRITICAL **: 20:41:45.722:
g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE
(instance_type)' failed
(iv:10030): GLib-GObject-CRITICAL **: 20:41:45.722: g_type_register_static:
assertion 'parent_type > 0' failed
Nothing else is displayed/shown.
Admittedly, I never cared enough to report.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages openimageio-tools depends on:
ii libatomic1 8.2.0-13
ii libavcodec58 10:4.1-dmo3
ii libavformat58 10:4.1-dmo3
ii libavutil56 10:4.1-dmo3
ii libboost-atomic1.67.0 1.67.0-11
ii libboost-chrono1.67.0 1.67.0-11
ii libboost-date-time1.67.0 1.67.0-11
ii libboost-filesystem1.67.0 1.67.0-11
ii libboost-system1.67.0 1.67.0-11
ii libboost-thread1.67.0 1.67.0-11
ii libc6 2.28-4
ii libdcmtk12 3.6.2-3+b2
ii libfreetype6 2.9.1-3
ii libgcc1 1:8.2.0-13
ii libgif7 5.1.4-3
ii libgl1 1.1.0-1
ii libglu1-mesa [libglu1] 9.0.0-2.1
ii libilmbase23 2.2.1-2
ii libjpeg62-turbo 1:1.5.2-2+b1
ii libopencolorio1v5 1.1.0~dfsg0-3
ii libopencv-core3.2 3.2.0+dfsg-5
ii libopencv-imgproc3.2 3.2.0+dfsg-5
ii libopencv-videoio3.2 3.2.0+dfsg-5
ii libopenexr23 2.2.1-4
ii libopenimageio2.0 2.0.3~dfsg0-3
ii libopenjp2-7 2.3.0-1.1
ii libopenvdb5.2 5.2.0-5
ii libpng16-16 1.6.36-2
ii libqt5core5a 5.11.3+dfsg-2
ii libqt5gui5 5.11.3+dfsg-2
ii libqt5opengl5 5.11.3+dfsg-2
ii libqt5widgets5 5.11.3+dfsg-2
ii libraw19 0.19.2-1
ii libstdc++6 8.2.0-13
ii libswscale5 10:4.1-dmo3
ii libtbb2 2018~U6-4
ii libtiff5 4.0.10-3
ii libwebp6 0.6.1-2
ii zlib1g 1:1.2.11.dfsg-1
openimageio-tools recommends no packages.
openimageio-tools suggests no packages.
--- End Message ---
--- Begin Message ---
Hi!
On 2019-01-03 at 20:25 (+01), Yuri D'Elia wrote:
> I really have no idea here of any possible cause.
> Is iv qt or gtk? qt with a glib main loop?
>
> If you have a couple of ideas I can try to narrow down the issue,
> otherwise I really don't care enough to debug it. I'm just reporting the
> finding here. It used to work, but not anymore.
>
> I tried on a new user (to ensure there is _no_ customization), but it
> does the same. This is debian unstable, without any DE (just openbox).
I asked some fellow DDs to test that same package on their environments.
In the end, GNOME, Plasma, i3 and fluxbox were reported to have no
issues at all with it.
But then, checking for other possible culprits, I noticed this:
====== snip =====
> Versions of packages openimageio-tools depends on:
> ii libavcodec58 10:4.1-dmo3
> ii libavformat58 10:4.1-dmo3
> ii libavutil56 10:4.1-dmo3
>
> [...]
>
> ii libswscale5 10:4.1-dmo3
====== snip =====
Deb-multimedia.org packages are known to be problematic when used within
official Debian since they introduce entropy to the system and it's
difficult to determine if the issue is related to them or not.
So, given I don't trust dmo packages at all (we at Debian Multimedia
Maintainers Team close bug reports by default where dmo is involved),
I'm closing this bug report as 'possibly-compromised by the presence of
dmo packages'.
Besides, I'd advice you to "purify" your system from those packages and
test the openimageio-tools package again. If the issue persists, then
re-open the bug report.
Cheers.
--
Matteo F. Vescovi || Debian Developer
GnuPG KeyID: 4096R/0x8062398983B2CF7A
signature.asc
Description: PGP signature
--- End Message ---
