Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see:
viewtopic.php?t=158230
Graphical Environments, Managers, Multimedia & Desktop questions.
milomak
Posts: 2168 Joined: 2009-06-09 22:20
Been thanked: 2 times
#1
Post
by milomak » 2018-11-14 23:16
so getting the below on sid
$ gimp
Code: Select all
gimp: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0: undefined symbol: babl_format_with_space
i figure since it' the same version in testing it's something worth looking at
$ apt-cache policy gimp
Code: Select all
gimp:
Installed: 2.10.8-1
Candidate: 2.10.8-1
Version table:
*** 2.10.8-1 500
500 http://debian.mirror.ac.za/debian testing/main amd64 Packages
500 http://debian.mirror.ac.za/debian sid/main amd64 Packages
500 http://ftp.is.co.za/debian testing/main amd64 Packages
500 http://ftp.is.co.za/debian sid/main amd64 Packages
500 http://debian.saix.net testing/main amd64 Packages
500 http://debian.saix.net sid/main amd64 Packages
500 http://deb-mir1.naitways.net/debian testing/main amd64 Packages
500 http://deb-mir1.naitways.net/debian sid/main amd64 Packages
100 /var/lib/dpkg/status
Last edited by
milomak on 2018-11-15 18:42, edited 1 time in total.
Desktop: A320M-A PRO MAX, AMD Ryzen 5 3600, GALAX GeForce RTX™ 2060 Super EX (1-Click OC) - Sid, Win10, Arch Linux, Gentoo, Solus
Laptop: hp 250 G8 i3 11th Gen - Sid
Kodi: AMD Athlon 5150 APU w/Radeon HD 8400 - Sid
stevepusser
Posts: 12930 Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 72 times
#2
Post
by stevepusser » 2018-11-15 01:48
I've found in backporting gimp 2.10.X to a Stretch base that the Debian package often does not force an update of the babl and gegl libraries to what it actually needs. So run
Code: Select all
apt policy libbabl-0.1-0 libgegl-0.4-0
and make sure you have 0.1.58 and 0.4.12 respectively, and that you don't have any deb-multimedia versions of those pretending to be high enough with that epoch tacked onto the front of the version.
I'm stumped if that's not the case--all I can say is that the backported 2.10.8 runs fine for me on a Stretch base:
https://build.opensuse.org/project/show ... -backports
MX Linux packager and developer
Head_on_a_Stick
Posts: 14114 Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 133 times
#3
Post
by Head_on_a_Stick » 2018-11-15 06:06
The gimp is working for me in testing:
Code: Select all
empty@buster:~ $ apt policy gimp libbabl-0.1-0 libgegl-0.4-0
gimp:
Installed: 2.10.8-1
Candidate: 2.10.8-1
Version table:
*** 2.10.8-1 500
100 https://cdn-aws.deb.debian.org/debian sid/main amd64 Packages
500 https://cdn-aws.deb.debian.org/debian buster/main amd64 Packages
100 /var/lib/dpkg/status
libbabl-0.1-0:
Installed: 0.1.58-1
Candidate: 0.1.58-1
Version table:
*** 0.1.58-1 500
100 https://cdn-aws.deb.debian.org/debian sid/main amd64 Packages
500 https://cdn-aws.deb.debian.org/debian buster/main amd64 Packages
100 /var/lib/dpkg/status
libgegl-0.4-0:
Installed: 0.4.12-1
Candidate: 0.4.12-1
Version table:
*** 0.4.12-1 500
100 https://cdn-aws.deb.debian.org/debian sid/main amd64 Packages
500 https://cdn-aws.deb.debian.org/debian buster/main amd64 Packages
100 /var/lib/dpkg/status
empty@buster:~ $
deadbang
milomak
Posts: 2168 Joined: 2009-06-09 22:20
Been thanked: 2 times
#4
Post
by milomak » 2018-11-15 18:42
thanks. my problem was
Code: Select all
libbabl-0.1-0:
Installed: 1:0.1.28-dmo1
Candidate: 1:0.1.28-dmo1
Version table:
*** 1:0.1.28-dmo1 100
100 /var/lib/dpkg/status
0.1.58-1 500
500 http://debian.mirror.ac.za/debian testing/main amd64 Packages
500 http://debian.mirror.ac.za/debian sid/main amd64 Packages
500 http://ftp.is.co.za/debian testing/main amd64 Packages
500 http://ftp.is.co.za/debian sid/main amd64 Packages
500 http://debian.saix.net testing/main amd64 Packages
500 http://debian.saix.net sid/main amd64 Packages
500 http://deb-mir1.naitways.net/debian testing/main amd64 Packages
500 http://deb-mir1.naitways.net/debian sid/main amd64 Packages
0.1.18-1 500
500 http://debian.mirror.ac.za/debian stable/main amd64 Packages
500 http://ftp.is.co.za/debian stable/main amd64 Packages
500 http://debian.saix.net stable/main amd64 Packages
500 http://deb-mir1.naitways.net/debian stable/main amd64 Packages
Desktop: A320M-A PRO MAX, AMD Ryzen 5 3600, GALAX GeForce RTX™ 2060 Super EX (1-Click OC) - Sid, Win10, Arch Linux, Gentoo, Solus
Laptop: hp 250 G8 i3 11th Gen - Sid
Kodi: AMD Athlon 5150 APU w/Radeon HD 8400 - Sid
stevepusser
Posts: 12930 Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 72 times
#5
Post
by stevepusser » 2018-11-15 19:59
Yes, DMO's epoch has caused the same issue for my backported MX 17 version for several users, so I've seen the error messages before.
MX Linux packager and developer
stevepusser
Posts: 12930 Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 72 times
#6
Post
by stevepusser » 2018-11-15 22:27
By the way, we're considering having the latest GIMP backport in the next point release of MX Linux, but weren't happy that it made MyPaint uninstallable:
https://bugs.debian.org/cgi-bin/bugrepo ... bug=894757
I found a patch online this morning that renames MyPaint's .mo files so they don't conflict, and rebuilt it and libmypaint to remove the conflict if MyPaint's our new version. I don't think that renaming those .mo translation files violates Debian policy, and is preferable to disabling them as suggested in that bug thread.
MX Linux packager and developer