QGIS will not install on Ubuntu 22.04 #48685
Comments
havenerk
added
the
Bug
|
not reproducable - there's no |
|
I don't get it. I have tried it with all combinations of libgdal in-not in /lib and also in-not in /usr/lib. I have removed it completely from my system to let qgis install its own dependency of gdal, thinking that if qgis needs gdal.so.30 it should install it. And it does--in both /lib and /usr/lib! In both cases libgdal.so.30 is a symlink to libgdal.so.30.0.1. I still get this symbol error for libgdal.so.30 which results in qgis-providers not being configured which then cascades to qgis, qgis-plugin-grass, and python3-qgis. /usr/lib/qgis/crssync: symbol lookup error: /lib/libgdal.so.30: undefined symbol |
combinations? Above gdal comes from stock ubuntu. Are your versions the versions above? |
Pedro-Murteira
added
Build/Install
|
Yes. If I remove libgdal.so.30 symlink and libgdal.so.30.0.1 from both /lib and /usr/lib, the QGIS install puts them back in both places, symlinking /usr/libgdal.so.30 --> /usr/libgdal.so.30.0.1 and /lib/libgdal.so.30 --> /lib/libgdal.so.30.0.1. If I remove qgis, then autoremove, all instances of libgdal.30.so go away, so I'm pretty sure it is qgis doing the deed, and not some other dependency installing it on my system. Looking through 'apt list', all libgdal related packages are 3.4.1+dfsg-1build4 amd64 except libgdal-grass/jammy 3.4.1-3 amd64. Thoughts? |
The symlinks in |
|
I have been successfully able to install both the LTR version and the packages from the Ubuntu repository on 22.04. Have you tried either of those? |
|
Make sure you have updated Ubuntu before you attempt an installation. It is not considered to be stable until the first point release comes out. |
|
The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". |
github-actions
bot
added
the
stale
|
Hello Mr Github-actions bot, No, it is still happening. To answer a few comments above. Ubuntu is up to date, who knows if it is 22.04.1? I update at least once a week. I can neither install the Ubuntu repository version, nor the qgis.org version (see below). 3.22.x was working on Ubuntu 21.10. They fail at exactly the same place, trying to configure qgis-providers and for the same reeason /usr/lib/qgis/crssync complaining about /lib/libgdal or /usr/lib/libgdal depending on who knows what. Apt seems to install libgdal.so.30.0.1 in both places (There is also a /lib/qgis and /usr/lib/qgis with identical content. Why?) Is Ubuntu's libgdal/libopenjp2-7 broken for Ubuntu 22.04? I don't know how to test that. Bottom line, QGIS will not install on Ubuntu 22.04 for me. ... dpkg: error processing package qgis (--configure): dpkg: error processing package qgis-plugin-grass (--configure): dpkg: error processing package python3-qgis (--configure): ... dpkg: error processing package qgis (--configure): dpkg: error processing package qgis-plugin-grass (--configure): dpkg: error processing package python3-qgis (--configure): |
github-actions
bot
removed
the
stale
|
Oh, and here is the relevant output from qgis-ltr: Setting up qgis-providers (1:3.22.7+36jammy-1) ... |
|
The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". |
github-actions
bot
added
the
stale
|
@havenerk |
github-actions
bot
removed
the
stale
|
The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". |
github-actions
bot
added
the
stale
|
The problem still persists with qgis 3.26.1: Setting up qgis-providers (1:3.26.1+36jammy) ... dpkg: error processing package qgis (--configure): dpkg: error processing package qgis-plugin-grass (--configure): dpkg: error processing package python3-qgis (--configure): I cannot install qgis-providers from 3.22 ltr, 3.24, and now 3.26 The most relevant comment I've received so far is from jef-n on May 23 above. The problem is uninstalling libopenjp2-7 and reinstalling it would also uninstall a metric crap-ton of dependencies that I could probably not recover from, including ubuntu desktop. His comment about gdalinfo is also correct. So what do I do about libopenjp2-7? Why is it different in my setup vice everyone else's who has moved to ubuntu 22.04? |
github-actions
bot
removed
the
stale
|
@havenerk in mine 22.04 I have libopenjpeg 8.0, after kernel update, then I rebuiltd gdal and I solved all dpkg configuration issues. (This because of a local build of gdal it uses the installed version of libopenjpeg) |
|
I have done multiple installs of Qgis LTR onto Ubuntu 22.04 and there was an issue every time. However, apt upgrade or apt full-upgrade fixed each problem as they happened. Using the project's packages rather than the Ubuntu ones. Last install I did was a week ago onto a computer that had just been upgraded in place from 20.04 to 22.04.0 |
|
Are you using apt full-upgrade as well as apt upgrade. Ubuntu has only just reached 22.04.1 which is the official public release of 22.04 LTS, before that it was still in beta. |
|
Still no bueno. My 22.04 is upgraded weekly so I have no idea what 22.04.x point release I may be on at any given time. I do use the project's packages rather than Ubuntu's. I have no idea what libopenjpeg8 is--it isn't available, so maybe a typo in that comment. I did check to see if there was a new libopenjp2-7 and there is but it makes use of "opj_encoder_set_extra_options" as well so would likely break gdal and qgis-providers as well. I am a meteorologist/climatologist and it is possible that some grib2 tool installed the culprit libopenjp2-7 library, but most of those tools use the jasper libraries instead. Sudo apt remove libopenjp2-7 reveals several gnome, gnome-desktop, ubuntu-desktop, and libreoffice dependencies in addition to the qgis ones, so it probably wasn't one of my specialty tools that did the deed. |
|
@havenerk sorry for mistake, I meant libopenjpeg 8.0 |
@havenerk still looks like a local issue and not a general one. |
|
Setting up qgis-providers (1:3.26.2+36jammy) ... So I removed (and autoremoved) all qgis and gdal packages, installed qgis and still get this error. I think my previous discussion of libopenjp2 was a red herring as I can find no dependencies of that library in the release files. @gioman, I would not call this a local issue because the error message is clearly impossible to reconcile--QGIS installs both of the conflicting libraries. Before I install, those libraries simply do not exist on the target machine. Afterward both are present and the error condition presents itself. But yet the conflict does not present on other machines, even another one of mine. The good machine is older, and AMD based, but both are bog standard unimpressive HP laptops and both started out as impish to jammy upgrades. Of course both upgrades uninstalled qgis, which I then re-installed or have at least attempted to. |
|
As said before it's not a QGIS problem. GDAL comes from an other source (eg. Ubuntu) and that depends on openjp2 and misses a symbol on your machine. QGIS installs fine on a fresh jammy. Probably some local leftovers from upgrades on your machine. I suppose GDAL is inoperable on your box too whether you install QGIS or not. |
|
Yes, gdal is broken when I install gdal-bin as a standalone program. |
|
@havenerk can you try to install libopenjpeg 8.0? In my case all works fine after this library installation |
|
@Antoviscomi, I can find no such package (libopenjpeg 8. I already have libjpeg8 installed (and also libjpeg9). |
|
@havenerk sorry for mistake you're right, the package is libjpeg 8.0, however only one version of this must be installed 8 or 9, double version installed, create conflict with gdal |
|
@Antoviscomi I removed libjpeg9 to no effect. Still getting the same error. Reinstalled libjpeg8, also to no effect. I've asked the same question on the gdal git page. Maybe someone there knows what could be causing the conflict. |
|
opj_encoder_set_extra_options is new to openjpeg 2.4.0. I guess you have (possibly leftovers of) an earlier version around that GDAL for some reason picks up. How it looks like here on a fresh jammy: # ldd /usr/bin/gdalinfo | grep openjp libopenjp2.so.7 => /lib/x86_64-linux-gnu/libopenjp2.so.7 (0x00007f3c8d184000) # dpkg -S libopenjp2.so.7 libopenjp2-7:amd64: /usr/lib/x86_64-linux-gnu/libopenjp2.so.7 # dpkg -s libopenjp2-7:amd64 | grep ^Version: Version: 2.4.0-6 Forcefully going back to impish's version: # gdalinfo
Usage: gdalinfo [--help-general] [-json] [-mm] [-stats | -approx_stats] [-hist] [-nogcp] [-nomd]
[-norat] [-noct] [-nofl] [-checksum] [-proj4]
[-listmdd] [-mdd domain|`all`] [-wkt_format WKT1|WKT2|...]*
[-sd subdataset] [-oo NAME=VALUE]* [-if format]* datasetname
FAILURE: No datasource specified.
# dpkg -i /var/cache/apt/archives/libopenjp2-7_2.3.1-1ubuntu4_amd64.deb
dpkg: warning: downgrading libopenjp2-7:amd64 from 2.4.0-6 to 2.3.1-1ubuntu4
(Reading database ... 13018 files and directories currently installed.)
Preparing to unpack .../libopenjp2-7_2.3.1-1ubuntu4_amd64.deb ...
Unpacking libopenjp2-7:amd64 (2.3.1-1ubuntu4) over (2.4.0-6) ...
Setting up libopenjp2-7:amd64 (2.3.1-1ubuntu4) ...
Processing triggers for libc-bin (2.35-0ubuntu3) ...
# gdalinfo
gdalinfo: symbol lookup error: /lib/libgdal.so.30: undefined symbol: opj_encoder_set_extra_options
|
|
SOLVED. Thank you @jef-n. My clumsy attempt with ldd didn't show anything, but when I invoked your command, I found a stray /usr/local/lib version of openjp2 version 2.3.0. I expect it was part of some meteorology software that I'd installed. Was not present on the one system that worked. |
|
I found uninstalling gdal-bin and reinstalling qgis sorted this issue for me. qgis has a dependency on libgdal-grass |
QGIS doesn't need grass support in GDAL. |
|
@havenerk what was your solution?
As the issue (which makes sense, since I have |
|
In my case I found an earlier version of a library in /use/local/lib which
was earlier In my library path. The library was superfluous to needs and
was replaced by a newer GDAL version in the QGIS, that was never found
because it found the old version in my executable/LD path first. You can
change the order in your path to execute /use/lib before /usr/local/lib.
Bottom line: find the old library and remove it or change the order of your
executable/library paths.
Kevin
…On Tue, Sep 13, 2022, 05:23 Idan Tene ***@***.***> wrote:
@havenerk <https://github.com/havenerk> what was your solution?
I'm running into similar issues but it cites
/usr/lib/qgis/crssync: error while loading shared libraries:
libproj.so.19: cannot open shared object file: No such file or directory
As the issue (which makes sense, since I have libproj22 installed, which
is also the requirement -- not sure why it's looking for libproj.so.19).
—
Reply to this email directly, view it on GitHub
<#48685 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACAMKC3DQJ4AC7LQRDCGZXLV6BW2NANCNFSM5WT2BW4Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Thanks for clarifying @havenerk! I cleared many of those, but no matter what I do, I do not have libproj.so.19 anywhere, and have no idea why it's needed specifically... Creating a link results in undefined symbols as well, so I'm a bit stumped now 🤔 |
|
In one of the previous answers to my problem there was a way to execute
GDAL and see what libraries it was linking, or maybe it was an apt or an
ld-related command, but that pesky library is somewhere on your path I
bet. Good hunting
…On Tue, Sep 13, 2022, 07:35 Idan Tene ***@***.***> wrote:
Thanks for clarifying @havenerk <https://github.com/havenerk>! I cleared
many of those, but no matter what I do, I do not have libproj.so.19
anywhere, and have no idea why it's needed specifically...
Creating a link results in undefined symbols as well, so I'm a bit stumped
now 🤔
—
Reply to this email directly, view it on GitHub
<#48685 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACAMKCYYQZX7EW3C45IXTFLV6CGMPANCNFSM5WT2BW4Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Thanks @havenerk! I managed to resolve the issue, and for what it's worth (for potential future troubleshooters), here's the rundown on my end:
|
|
Running into a similar problem on Ubuntu Jammy 22.04. QGIS (either 3.28 or 3.26.1 from the Software Store) will not install. And I removed a fully functioning version of 3.26.1 so now I have nothing. Here is the IO from
..... All help is appreciated Thanks. |
|
@paddleman I solve it by removing all qgis* info files then or (in your case)
|
|
Check your path/LD path. That old lib is probably in it somewhere and it
finds it first and then errors out. I think I found my problem library in
/usr/local/lib which comes before /lib and /usr/lib in my path. I had
installed something research-ish outside the normal QGIS and ubuntu
installation process, long since removed, but it left that old library.
Maybe just change the order of your path to get it installed if that turn
out to be the problem. There is a command to find the location of the
dependencies (it's in this thread somewhere) that pointed to the location
of the offending library. Good luck.
Kevin
…On Tue, Sep 13, 2022, 08:23 Idan Tene ***@***.***> wrote:
@havenerk <https://github.com/havenerk> what was your solution?
I'm running into similar issues but it cites
/usr/lib/qgis/crssync: error while loading shared libraries:
libproj.so.19: cannot open shared object file: No such file or directory
As the issue (which makes sense, since I have libproj22 installed, which
is also the requirement -- not sure why it's looking for libproj.so.19).
—
Reply to this email directly, view it on GitHub
<#48685 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACAMKC3DQJ4AC7LQRDCGZXLV6BW2NANCNFSM5WT2BW4Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
sudo apt install qgis The following packages have unmet dependencies: any one can help? |
|
I also met this error while installing qgis on Ubuntu 22.04, and my solution is to install and use qgis in the conda environment. For details, please refer to https://gisunchained.wordpress.com/2019/05/29/using-qgis-from-conda/. |
special thanks > more indifferenthttps://blog.csdn.net/qq_38979769/article/details/129723825download sqlite-autoconf-${current_version}.tar.gz version no amalgamationedit first macro definitions lines and add define SQLITE_ENABLE_COLUMN_METADATA 1 like thissave and make installenjoyif the installation is corrupted retry
|
|
Try it, it worked here Try removing ALL gdal packages and reinstalling first gdal-bin and libgdal-dev and lastly qgis |
Nice and simple solution. Thanks |
In mine I should need to rebuild gdal, because of a local build version, so this solution is useful for those have a classic installation |
What is the bug or the crash?
Setting up qgis-providers (1:3.24.3+36jammy-1) ...
/usr/lib/qgis/crssync: symbol lookup error: /lib/libgdal.so.30: undefined symbol: opj_encoder_set_extra_options
dpkg: error processing package qgis-providers (--configure):
installed qgis-providers package post-installation script subprocess returned error exit status 127
dpkg: dependency problems prevent configuration of qgis:
qgis depends on qgis-providers (= 1:3.24.3+36jammy-1); however:
Package qgis-providers is not configured yet.
dpkg: error processing package qgis (--configure):
dependency problems - leaving unconfigured
Setting up libqgis-customwidgets (1:3.24.3+36jammy-1) ...
No apport report written because the error message indicates its a followup error from a previous failure.
dpkg: dependency problems prevent configuration of qgis-plugin-grass:
qgis-plugin-grass depends on qgis (= 1:3.24.3+36jammy-1); however:
Package qgis is not configured yet.
dpkg: error processing package qgis-plugin-grass (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Setting up libqgisgrass7-3.24.3 (1:3.24.3+36jammy-1) ...
dpkg: dependency problems prevent configuration of python3-qgis:
python3-qgis depends on qgis-providers (= 1:3.24.3+36jammy-1); however:
Package qgis-providers is not configured yet.
dpkg: error processing package python3-qgis (--configure):
dependency problems - leaving unconfigured
Setting up python3-qgis-common (1:3.24.3+36jammy-1) ...
No apport report written because MaxReports is reached already
Setting up qgis-provider-grass (1:3.24.3+36jammy-1) ...
Errors were encountered while processing:
qgis-providers
qgis
qgis-plugin-grass
python3-qgis
E: Sub-process /usr/bin/dpkg returned an error code (1)
W: Operation was interrupted before it could finish
Steps to reproduce the issue
sudo apt remove qgis
sudo apt autoremove
sudo apt remove geos
sudo apt install qgis
Versions
This has been true since Jammy was released. 3.22.4+ and 3.24.x all fail for the same reason.
Supported QGIS version
New profile
Additional context
Whenever I upgrade to a new Ubuntu release, the release manager helpfully uninstalls my working version of QGIS, which I then have to reinstall. The reinstall is not working this time.
The text was updated successfully, but these errors were encountered: