Bug#904544: gimp failed to launch from menu entry or terminal command

[Simon McVittie]

On Thu, 09 Aug 2018 at 14:01:46 +0200, Andreas Tille wrote:
> 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

OK, then I think we can consider your contribution to #904544 to be
another report of #903514, which doesn't need a new bug number.

Thanks,
smcv

Bug#904544: gimp failed to launch from menu entry or terminal command

[Andreas Tille]

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-data2.10.2-1
ii  libaa1   1.4p5-44+b2
ii  libbabl-0.1-00.1.54-1
ii  libbz2-1.0   1.0.6-8.1
ii  libc62.27-5
ii  libcairo21.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-00.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  libharfbuzz0b1.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-01.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  libwebpdemux20.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-utils1.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  
pn  gimp-help-en | gimp-help  
pn  gimp-python   
ii  gvfs-backends 1.36.2-1
ii  libasound21.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
> , 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

Bug#904544: gimp failed to launch from menu entry or terminal command

[Jun Jiang]

On Thu, 9 Aug 2018 11:28:23 +0100 Simon McVittie  wrote:
> On Wed, 25 Jul 2018 at 11:12:52 +0800, Jiang Jun wrote:
> > When I click GIMP launcher from menu entry, nothing happens.
> ...
> > Versions of packages gimp depends on:
> ...
> > ii  libbabl-0.1-01:0.1.54-dmo1
> ...
> > ii  libgegl-0.4-01:0.4.6-dmo1
> ...
> > ii  libmypaint-1.3-0 1:1.3.0-dmo6
>
> You seem to have installed unofficial packages from deb-multimedia.org,
> with artificially higher versions than the versions from Debian. We
> cannot support systems with unoffical packages installed. Please install
> gimp's dependencies from Debian and try again.
>
> If this bug still exists without using deb-multimedia.org packages,
> please reply describing steps to reproduce the bug and the new symptoms,
> and include the package information from "reportbug --template gimp" so
> that we know which package versions you have installed.
>
> Thanks,
> smcv
>
>

I didn't thought it was the same thing, but as I went through the GIMP bug
list I saw  James Van Zandt mentioned in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903514:

"Specifically:
   sudo apt-get install libopenblas-base- libopenblas-dev- \
 libblas3 liblapack3 libblas-dev liblapack-dev

Unfortunately julia and libjulia0.6 were also removed here, since they
depend on libopenblas-base.  I intend to report this as a bug, and request
that they depend instead on the virtual packages libblas.so.3 and
liblapack.so.3 (which can also be provided by liblapack3 and libblas3,
resp.)."


And that solved my problem too. In my case, libopenblas-dev:amd64
(0.3.2+ds-1) and libopenblas-base:amd64 (0.3.2+ds-1) got removed and after
that, GIMP launched successsfully just like it used to do. Hope it helps.

Bug#904544: gimp failed to launch from menu entry or terminal command

[Simon McVittie]

On Thu, 09 Aug 2018 at 11:34:07 +0100, Simon McVittie wrote:
> It would probably be a good idea to open a separate bug: if several bugs
> turn out to have the same root cause, we can easily merge them, but if
> several people use the same bug number to refer to different bugs that
> have the same symptom (gimp not starting), it becomes really difficult to
> determine whether they have all been fixed.

Also, do you have libopenblas-base installed? That package was implicated
in , and removing it seems to be a
workaround for that bug (at least in unstable).

If in doubt, open a separate bug and send details there, so that your
situation won't be mixed up with other people's. Bug numbers are an
unlimited resource :-)

Thanks,
smcv

Bug#904544: gimp failed to launch from menu entry or terminal command

[Simon McVittie]

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?

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. 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
, and removing it seems to be a
workaround for that bug (at least in unstable).

Thanks,
smcv

Bug#904544: gimp failed to launch from menu entry or terminal command

[Simon McVittie]

On Mon, 06 Aug 2018 at 10:08:41 +0200, CHristoph wrote:
> Package: gimp
> Version: 2.8.22-1
>
> same issue here. Gimp does not start.

You seem to be using an older version of gimp than the original reporter
of #904544, and unlike the original reporter, you do not seem to be
using unofficial packages from deb-multimedia.org.

It would probably be a good idea to open a separate bug: if several bugs
turn out to have the same root cause, we can easily merge them, but if
several people use the same bug number to refer to different bugs that
have the same symptom (gimp not starting), it becomes really difficult to
determine whether they have all been fixed.

Thanks,
smcv

Bug#904544: gimp failed to launch from menu entry or terminal command

[Simon McVittie]

On Wed, 25 Jul 2018 at 11:12:52 +0800, Jiang Jun wrote:
> When I click GIMP launcher from menu entry, nothing happens.
...
> Versions of packages gimp depends on:
...
> ii  libbabl-0.1-01:0.1.54-dmo1
...
> ii  libgegl-0.4-01:0.4.6-dmo1
...
> ii  libmypaint-1.3-0 1:1.3.0-dmo6

You seem to have installed unofficial packages from deb-multimedia.org,
with artificially higher versions than the versions from Debian. We
cannot support systems with unoffical packages installed. Please install
gimp's dependencies from Debian and try again.

If this bug still exists without using deb-multimedia.org packages,
please reply describing steps to reproduce the bug and the new symptoms,
and include the package information from "reportbug --template gimp" so
that we know which package versions you have installed.

Thanks,
smcv

Bug#904544: gimp failed to launch from menu entry or terminal command

[Andreas Tille]

Hi,

similar here.  I usually start from xterm.  I'm running an up to date
testing system.  Last week Gimp worked but failed today.  I removed
.config/GIMP but no change.  However, when I started

 strace gimp

it started - but loading images was not possible.  After the call with
strace a simple `gimp` worked as well, but not reliably.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#904544: gimp failed to launch from menu entry or terminal command

[CHristoph]

Package: gimp
Version: 2.8.22-1
Followup-For: Bug #904544

Dear Maintainer,
same issue here. Gimp does not start. I do not get a segfault when i
cancel with ctrl+c. Nothing happens. 
When i run gimp from gdb debugger it starts just fine and works without
any errors.

CHristoph

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_AT:de (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-data2.8.22-1
ii  libaa1   1.4p5-44+b2
ii  libbabl-0.1-00.1.54-1
ii  libbz2-1.0   1.0.6-8.1
ii  libc62.27-5
ii  libcairo21.15.10-3
ii  libdbus-1-3  1.12.10-1
ii  libdbus-glib-1-2 0.110-2
ii  libexif120.6.21-5
ii  libfontconfig1   2.13.0-5
ii  libfreetype6 2.8.1-2
ii  libgdk-pixbuf2.0-0   2.36.12-1
ii  libgegl-0.3-00.3.28-4
ii  libgimp2.0   2.8.22-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  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-2
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libpango-1.0-0   1.42.1-2
ii  libpangocairo-1.0-0  1.42.1-2
ii  libpangoft2-1.0-01.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  libtiff5 4.0.9-6
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  python   2.7.15-3
ii  python-gtk2  2.24.0-5.1+b1
ii  python2.72.7.15-3
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  
pn  gimp-help-en | gimp-help  
ii  gvfs-backends 1.36.2-1
ii  libasound21.1.6-1

-- no debconf information

Bug#904544: gimp failed to launch from menu entry or terminal command

[Jiang Jun]

Package: gimp
Version: 2.10.2-1
Severity: important

Dear Maintainer,

I don't know how long it has been like this, maybe a monthor so. GIMP just
won't launch for me.

When I click GIMP launcher from menu entry, nothing happens.
When I type gimp in a terminal, the cmd just hangs there and nothing happens,
there isn't anything echoing back even when I use --verbose option. When I
Ctrl-C to stop it, I get something like:

11669 segmentation fault (core dumped)  gimp

Here is the output of coredumpctl info -1 after the segment fault:
https://cfp.vim-cn.com/cbfkp

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.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-data2.10.2-1
ii  libaa1   1.4p5-44+b2
ii  libbabl-0.1-01:0.1.54-dmo1
ii  libbz2-1.0   1.0.6-8.1
ii  libc62.27-5
ii  libcairo21.15.10-3
ii  libfontconfig1   2.13.0-5
ii  libfreetype6 2.8.1-2
ii  libgcc1  1:8.1.0-12
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libgegl-0.4-01:0.4.6-dmo1
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  libharfbuzz0b1.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
pn  libmng1  
ii  libmypaint-1.3-0 1:1.3.0-dmo6
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-01.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.1.0-12
ii  libtiff5 4.0.9-6
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.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-utils1.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  
pn  gimp-help-en | gimp-help  
pn  gimp-python   
ii  gvfs-backends 1.36.1-1+b1
ii  libasound21.1.6-1

-- no debconf information