Bug#904544: gimp failed to launch from menu entry or terminal command
Andreas Tille
tille at debian.org
Thu Aug 9 13:01:46 BST 2018
On Thu, Aug 09, 2018 at 11:41:42AM +0100, Simon McVittie wrote:
> On Thu, 09 Aug 2018 at 09:10:13 +0200, Andreas Tille wrote:
> > similar here. I usually start from xterm. I'm running an up to date
> > testing system.
>
> Do you have the same versions of all packages that CHristoph did in the
> previous message?
Here is the full system information reportbug created on my system:
Package: gimp
Version: 2.10.2-1
Severity: normal
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF
-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gimp depends on:
ii gimp-data 2.10.2-1
ii libaa1 1.4p5-44+b2
ii libbabl-0.1-0 0.1.54-1
ii libbz2-1.0 1.0.6-8.1
ii libc6 2.27-5
ii libcairo2 1.15.10-3
ii libfontconfig1 2.13.0-5
ii libfreetype6 2.8.1-2
ii libgcc1 1:8.2.0-3
ii libgdk-pixbuf2.0-0 2.36.12-1
ii libgegl-0.4-0 0.4.6-1
ii libgexiv2-2 0.10.8-1
ii libgimp2.0 2.10.2-1
ii libglib2.0-0 2.56.1-2
ii libgs9 9.22~dfsg-2.1
ii libgtk2.0-0 2.24.32-2
ii libgudev-1.0-0 232-2
ii libharfbuzz0b 1.8.4-1
ii libheif1 1.3.2-1
ii libilmbase23 2.2.1-2
ii libjpeg62-turbo 1:1.5.2-2+b1
ii liblcms2-2 2.9-2
ii liblzma5 5.2.2-1.3
ii libmng1 1.0.10+dfsg-3.1+b5
ii libmypaint-1.3-0 1.3.0-2
ii libopenexr23 2.2.1-4
ii libopenjp2-7 2.3.0-1
ii libpango-1.0-0 1.42.1-2
ii libpangocairo-1.0-0 1.42.1-2
ii libpangoft2-1.0-0 1.42.1-2
ii libpng16-16 1.6.34-2
ii libpoppler-glib8 0.63.0-2
ii librsvg2-2 2.40.20-2
ii libstdc++6 8.2.0-3
ii libtiff5 4.0.9-6
ii libwebp6 0.6.1-2
ii libwebpdemux2 0.6.1-2
ii libwebpmux3 0.6.1-2
ii libwmf0.2-7 0.2.8.4-12
ii libx11-6 2:1.6.5-1
ii libxcursor1 1:1.1.15-1
ii libxext6 2:1.3.3-1+b2
ii libxfixes3 1:5.0.3-1
ii libxmu6 2:1.1.2-2
ii libxpm4 1:3.5.12-1
ii xdg-utils 1.1.3-1
ii zlib1g 1:1.2.11.dfsg-1
Versions of packages gimp recommends:
ii ghostscript 9.22~dfsg-2.1
Versions of packages gimp suggests:
pn gimp-data-extras <none>
pn gimp-help-en | gimp-help <none>
pn gimp-python <none>
ii gvfs-backends 1.36.2-1
ii libasound2 1.1.6-1
-- no debconf information
> The original reporter of #904544, Jiang Jun, is using a newer version
> of gimp and several packages from deb-multimedia.org, so I don't want
> to assume that the bug you are encountering is the same as the bug the
> original reporter is encountering.
I stick to Debian packaged versions. deb-multimedia.org was never in
my apt sources.list.
> Merging duplicate bugs is a lot easier
> than disentangling multiple root causes for the same symptom under one
> bug number, so it might be better to report a separate bug with the full
> reportbug info (or reply to the separate bug that I asked CHristoph
> to file if you are confident that all applicable package versions are
> the same).
>
> Do you have libopenblas-base installed? That package was implicated in
> <https://bugs.debian.org/903514>, and removing it seems to be a
> workaround for that bug (at least in unstable).
$ apt-cache policy libopenblas-base
libopenblas-base:
Installed: 0.3.2+ds-1
Candidate: 0.3.2+ds-1
Version table:
*** 0.3.2+ds-1 501
501 http://httpredir.debian.org/debian testing/main amd64 Packages
50 http://httpredir.debian.org/debian unstable/main amd64 Packages
I can confirm that after removing libopenblas-base gimp works as usual
again.
Please let me know if I should file a separate bug report anyway
Andreas.
--
http://fam-tille.de
More information about the pkg-gnome-maintainers
mailing list