Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1017461 > unrolled thread
| Started by | Nikolai Lusan <nikolai@lusan.id.au> |
|---|---|
| First post | 2020-07-10 20:10 +0200 |
| Last post | 2020-07-29 15:40 +0200 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.debian.bugs.dist
Bug#964810: gimp: Failure to start - GTK problem Nikolai Lusan <nikolai@lusan.id.au> - 2020-07-10 20:10 +0200
Bug#964810: gimp: Unable to start gimp in debian unstable felipe <zeden@riseup.net> - 2020-07-29 06:00 +0200
Bug#964810: gimp: Unable to start gimp in debian unstable felipe <zeden@riseup.net> - 2020-07-29 15:40 +0200
| From | Nikolai Lusan <nikolai@lusan.id.au> |
|---|---|
| Date | 2020-07-10 20:10 +0200 |
| Subject | Bug#964810: gimp: Failure to start - GTK problem |
| Message-ID | <Ar5Db-3gS-11@gated-at.bofh.it> |
Package: gimp Version: 2.10.18-1 Severity: grave Justification: renders package unusable A problem has arisen (probaly within the GTK teams) that means any attempt to start GIMP results in: nikolai@poltava:~$ gimp Gtk-Message: 03:50:02.309: Failed to load module "topmenu-gtk-module" Gtk-Message: 03:50:02.310: Failed to load module "topmenu-gtk-module" : CommandLine Error: Option 'polly' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options A search on packages.debian.org shows that the gtk topmenu module has fallen out of the reposistory. The topmenu-gtk packages are no longer available, and the files don't seem to have been rolled into any of the other GTK packages. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.6.8-poltava (SMP w/2 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gimp depends on: ii gimp-data 2.10.18-1 ii libaa1 1.4p5-46+b1 ii libbabl-0.1-0 1:0.1.78-dmo1 ii libbz2-1.0 1.0.8-3 ii libc6 2.30-8 ii libcairo2 1.16.0-4 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.2+dfsg-2 ii libgcc-s1 10.1.0-4 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5 ii libgegl-0.4-0 1:0.4.24-dmo1 ii libgexiv2-2 0.12.1-1 ii libgimp2.0 2.10.18-1 ii libglib2.0-0 2.64.4-1 ii libgs9 9.52~dfsg-1 ii libgtk2.0-0 2.24.32-4 ii libgudev-1.0-0 233-1 ii libharfbuzz0b 2.6.7-1 ii libheif1 1.6.1-1 ii libilmbase24 2.3.0-6 ii libjpeg62-turbo 1:2.0.5-1 ii libjson-glib-1.0-0 1.4.4-2 ii liblcms2-2 2.9-4+b1 ii liblzma5 5.2.4-1+b1 ii libmng1 1.0.10+dfsg-3.1+b5 ii libmypaint-1.5-1 1:1.5.1-dmo2 ii libopenexr24 2.3.0-6 ii libopenjp2-7 2.3.1-1 ii libpango-1.0-0 1.44.7-4 ii libpangocairo-1.0-0 1.44.7-4 ii libpangoft2-1.0-0 1.44.7-4 ii libpng16-16 1.6.37-2 ii libpoppler-glib8 0.71.0-6 ii librsvg2-2 2.48.7-1 ii libstdc++6 10.1.0-4 ii libtiff5 4.1.0+git191117-2 ii libwebp6 0.6.1-2+b1 ii libwebpdemux2 0.6.1-2+b1 ii libwebpmux3 0.6.1-2+b1 ii libwmf0.2-7 0.2.8.4-17 ii libx11-6 2:1.6.9-2+b1 ii libxcursor1 1:1.2.0-2 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-2 ii libxmu6 2:1.1.2-2+b3 ii libxpm4 1:3.5.12-1 ii xdg-utils 1.1.3-2 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages gimp recommends: ii ghostscript 9.52~dfsg-1 Versions of packages gimp suggests: ii gimp-data-extras 1:2.0.2-1 ii gimp-help-en [gimp-help] 2.8.2-2 ii gvfs-backends 1.44.1-1 ii libasound2 1.2.2-2.3 -- no debconf information
[toc] | [next] | [standalone]
| From | felipe <zeden@riseup.net> |
|---|---|
| Date | 2020-07-29 06:00 +0200 |
| Subject | Bug#964810: gimp: Unable to start gimp in debian unstable |
| Message-ID | <AxLq1-39s-1@gated-at.bofh.it> |
| In reply to | #1017461 |
After investigating further, I found the problematic package to be mesa-opencl-icd. After removing the package above, gimp works again.
[toc] | [prev] | [next] | [standalone]
| From | felipe <zeden@riseup.net> |
|---|---|
| Date | 2020-07-29 15:40 +0200 |
| Subject | Bug#964810: gimp: Unable to start gimp in debian unstable |
| Message-ID | <AxUtk-jw-9@gated-at.bofh.it> |
| In reply to | #1017461 |
On 7/29/20 5:07 AM, Simon McVittie wrote: > Control: reassign -1 libllvm10,libllvm9,libllvm7 > Control: forcemerge 852746 -1 > Control: affects 852746 + gimp > > On Thu, 16 Jul 2020 at 12:26:26 -0300, zeden wrote: >> $ gimp >> : CommandLine Error: Option 'polly' registered more than once! >> LLVM ERROR: inconsistency in registered CommandLine options > > On Wed, 29 Jul 2020 at 00:55:02 -0300, felipe wrote: >> After investigating further, I found the problematic package to be mesa-opencl-icd. >> >> After removing the package above, gimp works again. > > This looks like the same issue as #852746. The workaround appears to be > to avoid installing more than one OpenCL implementation at the same time: > > - If you have an AMD GPU, install mesa-opencl-icd > - If you have an NVIDIA GPU and are using the proprietary driver, > install nvidia-opencl-icd or one of the nvidia-*-opencl-icd packages > - If you have an Intel integrated GPU, install beignet-opencl-icd or > intel-opencl-icd I use and AMD polaris card with amdgpu and mesa drivers. Previously I only had mesa-opencl-icd and ocl-icd-libopencl1 which is pulled by mesa-opencl-icd. Trying to remove ocl-icd-libopencl1 prompts me to install nvidia-opencl packages. It seems bug #954849 has a pretty similar bug, but found the problem while using libreoffice's opencl implementation.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.bugs.dist
csiph-web