[Bug 2063325] Re: postgis no longer works after dist-upgrade
This error went away on restart, so it's probably safe to close. ** Description changed: After dist-upgrading from focal to jammy, postgis no longer works due to - an undeclared dependency on glibc 3.4.29: + an undeclared dependency on glibc++ 3.4.29: ``` Apr 24 10:55:14 tiles2 renderd[1761]:reason: Postgis Plugin: ERROR: could not load library "/usr/lib/postgresql/12/lib/postgis-3.so": /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /lib/x86_64-linux-gnu/libSFCGAL.so.1)#012LINE 16: ) ``` This makes it both impossible to use postgis, and impossible to migrate to postgresql 14, since for a postgres upgrade both versions must be operational simultaneously. See also https://bugs.launchpad.net/ubuntu/+source/update- manager/+bug/1907652?comments=all and https://bugs.launchpad.net/ubuntu/+source/postgis/+bug/1950772 . ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: postgis 3.2.0+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-177.197-generic 5.4.268 Uname: Linux 5.4.0-177-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 24 10:59:04 2024 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: postgis UpgradeStatus: Upgraded to jammy on 2024-04-23 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063325 Title: postgis no longer works after dist-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgis/+bug/2063325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063325] [NEW] postgis no longer works after dist-upgrade
Public bug reported: After dist-upgrading from focal to jammy, postgis no longer works due to an undeclared dependency on glibc 3.4.29: ``` Apr 24 10:55:14 tiles2 renderd[1761]:reason: Postgis Plugin: ERROR: could not load library "/usr/lib/postgresql/12/lib/postgis-3.so": /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /lib/x86_64-linux-gnu/libSFCGAL.so.1)#012LINE 16: ) ``` This makes it both impossible to use postgis, and impossible to migrate to postgresql 14, since for a postgres upgrade both versions must be operational simultaneously. See also https://bugs.launchpad.net/ubuntu/+source/update- manager/+bug/1907652?comments=all and https://bugs.launchpad.net/ubuntu/+source/postgis/+bug/1950772 . ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: postgis 3.2.0+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-177.197-generic 5.4.268 Uname: Linux 5.4.0-177-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 24 10:59:04 2024 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: postgis UpgradeStatus: Upgraded to jammy on 2024-04-23 (0 days ago) ** Affects: postgis (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063325 Title: postgis no longer works after dist-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgis/+bug/2063325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950772] Re: Release-upgrade from bionic -> focal breaks postgres if postgis is in use
May be related to https://bugs.launchpad.net/ubuntu/+source/update- manager/+bug/1907652?comments=all ** Summary changed: - Release-upgrade from bionic -> focal bricks postgres if postgis is in use + Release-upgrade from bionic -> focal breaks postgres if postgis is in use -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950772 Title: Release-upgrade from bionic -> focal breaks postgres if postgis is in use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgis/+bug/1950772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950772] [NEW] Release-upgrade from bionic -> focal bricks postgres if postgis is in use
Public bug reported: When performing a release upgrade from bionic to focal, the package postgresql-10-postgis-2.4 is removed due to dependency issues with libgdal20. But to perform a cluster upgrade from postgresql-10 to postgresql-12, both v10 and v12 clusters must be running, and so both versions of postgis must be installed. Running pg_upgradecluster to upgrade from pgsql10->12 throws an error that postgis-2.4 is missing: ``` Starting new cluster... Notice: extra pg_ctl/postgres options given, bypassing systemctl for start operation Roles, databases, schemas, ACLs... pg_dump: error: query failed: ERROR: could not access file "$libdir/postgis-2.4": No such file or directory pg_dump: error: query was: SELECT a.attnum, a.attname, a.atttypmod, a.attstattarget, a.attstorage, t.typstorage, a.attnotnull, a.atthasdef, a.attisdropped, a.attlen, a.attalign, a.attislocal, pg_catalog.format_type(t.oid, a.atttypmod) AS atttypname, '' AS attgenerated, NULL AS attmissingval, a.attidentity, pg_catalog.array_to_string(ARRAY(SELECT pg_catalog.quote_ident(option_name) || ' ' || pg_catalog.quote_literal(option_value) FROM pg_catalog.pg_options_to_table(attfdwoptions) ORDER BY option_name), E', ') AS attfdwoptions, CASE WHEN a.attcollation <> t.typcollation THEN a.attcollation ELSE 0 END AS attcollation, array_to_string(a.attoptions, ', ') AS attoptions FROM pg_catalog.pg_attribute a LEFT JOIN pg_catalog.pg_type t ON a.atttypid = t.oid WHERE a.attrelid = '18012'::pg_catalog.oid AND a.attnum > 0::pg_catalog.int2 ORDER BY a.attnum pg_dumpall: error: pg_dump failed on database "gis", exiting Error during cluster dumping, removing new cluster sudo systemctl stop postgresql@12-main Warning: systemd was not informed about the removed cluster yet. Operations like "service postgresql start" might fail. To fix, run: sudo systemctl daemon-reload sudo systemctl stop postgresql@10-main Warning: the cluster will not be running as a systemd service. Consider using systemctl: sudo systemctl start postgresql@10-main ``` pg_dumpall fails similarly. Reactivating the bionic repositories and installing postgresql-10-postgis-2.4 throws dependency issues: ``` # apt install postgresql-10-postgis-2.4 postgresql-10-postgis-2.4-scripts Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: postgresql-10-postgis-2.4 : Depends: libgdal20 (>= 2.0.1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` So the v10 gis database is now apparently both unusable and upgradable. ** Affects: postgis (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950772 Title: Release-upgrade from bionic -> focal bricks postgres if postgis is in use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgis/+bug/1950772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838636] [NEW] SecTmpDir operation has undocumented restrictions
Public bug reported: By default, SecTmpDir is set to "/tmp", but it is recommended to change this to reference a location without general read permissions. It is not documented anywhere that I can find (but appears from experimentation to be the case) that one cannot use a subdirectory of /tmp (or of /var/tmp) as SecTmpDir. Attempting to do so results in errors such as the following when uploading files larger than the in-memory limit: ``` [Thu Aug 01 12:11:20.206816 2019] [:error] [pid 20747] [client XXX:34636] [client XXX] ModSecurity: Failed to open temporary file for reading: /var/tmp/modsecurity/20190801-121119-XULW4nH8B6zTbIg@QC9oyQQ-request_body-hki209 [hostname "XXX"] [uri "/wp-admin/async-upload.php"] [unique_id "XULW4nH8B6zTbIg@QC9oyQQ"], referer: https://XXX/wp-admin/upload.php [Thu Aug 01 12:11:20.472808 2019] [:error] [pid 20747] [client XXX:34636] [client XXX] ModSecurity: Input filter: Error reading from temporary file: Bad file descriptor [hostname "XXX"] [uri "/wp-admin/async-upload.php"] [unique_id "XULW4nH8B6zTbIg@QC9oyQQ"], referer: https://XXX/wp-admin/upload.php [Thu Aug 01 12:11:20.474908 2019] [:error] [pid 20747] [client XXX:34636] [client XXX] ModSecurity: Input filter: Error reading from temporary file: Bad file descriptor [hostname "XXX"] [uri "/wp-admin/async-upload.php"] [unique_id "XULW4nH8B6zTbIg@QC9oyQQ"], referer: https://XXX/wp-admin/upload.php [Thu Aug 01 12:11:20.475367 2019] [:error] [pid 20747] [client XXX:34636] [client XXX] ModSecurity: Input filter: Failed to delete temporary file: /var/tmp/modsecurity/20190801-121119-XULW4nH8B6zTbIg@QC9oyQQ-request_body-hki209 [hostname "XXX"] [uri "/wp-admin/async-upload.php"] [unique_id "XULW4nH8B6zTbIg@QC9oyQQ"], referer: https://XXX/wp-admin/upload.php ``` It appears that the temporary file has silently failed to be written to /var/tmp/modsecurity, causing secondary errors on attempted read and delete. The same secondary errors are thrown if any SecTmpDir is unwritable by www-data, indicating that there is a generally-silent primary error on write. It is not clear why subdirectories of /tmp and /var/tmp should be unusable as SecTmpDir, since /tmp and /var/tmp, while not recommended, are themselves usable, and the same security concerns would apply. Expected behaviour -- At the very least, one or more of the following should apply: 1) the error when attempting to write to an invalid SecTmpDir should be noisy 2) modsecurity should test for an invalid SecTmpDir on startup and throw a meaningful warning 3) for consistency, it should be either allowed to use subdirectories of /tmp and /var/tmp, or forbidden entirely from using /tmp or /var/tmp, as SecTmpDir. System info --- ii libapache2-mod-security2 2.9.2-1 amd64 Tighten web applications security for Apache Description:Ubuntu 18.04.1 LTS Release:18.04 ** Affects: modsecurity-apache (Ubuntu) Importance: Undecided Status: New ** Description changed: By default, SecTmpDir is set to "/tmp", but it is recommended to change this to reference a location without general read permissions. It is not documented anywhere that I can find (but appears from experimentation to be the case) that one cannot use a subdirectory of /tmp (or of /var/tmp) as SecTmpDir. Attempting to do so results in errors such as the following when uploading files larger than the in-memory limit: ``` - 2019] [:error] [pid 20747] [client XXX:34636] [client XXX] ModSecurity: Failed to open temporary file for reading: /var/tmp/modsecurity/20190801-121119-XULW4nH8B6zTbIg@QC9oyQQ-request_body-hki209 [hostname "XXX"] [uri "/wp-admin/async-upload.php"] [unique_id "XULW4nH8B6zTbIg@QC9oyQQ"], referer: https://XXX/wp-admin/upload.php + [Thu Aug 01 12:11:20.206816 2019] [:error] [pid 20747] [client XXX:34636] [client XXX] ModSecurity: Failed to open temporary file for reading: /var/tmp/modsecurity/20190801-121119-XULW4nH8B6zTbIg@QC9oyQQ-request_body-hki209 [hostname "XXX"] [uri "/wp-admin/async-upload.php"] [unique_id "XULW4nH8B6zTbIg@QC9oyQQ"], referer: https://XXX/wp-admin/upload.php [Thu Aug 01 12:11:20.472808 2019] [:error] [pid 20747] [client XXX:34636] [client XXX] ModSecurity: Input filter: Error reading from temporary file: Bad file descriptor [hostname "XXX"] [uri "/wp-admin/async-upload.php"] [unique_id "XULW4nH8B6zTbIg@QC9oyQQ"], referer: https://XXX/wp-admin/upload.php [Thu Aug 01 12:11:20.474908 2019] [:error] [pid 20747] [client XXX:34636] [client XXX] ModSecurity: Input filter: Error reading from temporary file: Bad file descriptor [hostname "XXX"] [uri "/wp-admin/async-upload.php"] [unique_id "XULW4nH8B6zTbIg@QC9oyQQ"], referer: https://XXX/wp-admin/upload.php [Thu Aug 01 12:11:20.475367 2019] [:error] [pid 20747] [client XXX:34636] [client XXX] ModSecurity: Input filter: Failed to delete temporary file:
[Bug 1059726] Re: Mounting drives that have '\040' in the name in fstab throws up an error during boot.
I can confirm this bug. I have two external drives in my fstab: proc/proc procnodev,noexec,nosuid 0 0 # / was on /dev/sda1 during installation UUID=a750d27d-ca00-4aa8-b154-a86c95c5054e / ext4 errors=remount-ro 0 1 # /vault was on /dev/sda6 during installation UUID=214e350f-1b00-4f1d-b105-bf9a4696b367 /vault ext4defaults 0 2 # swap was on /dev/sda5 during installation UUID=c26824e9-386f-4e7d-abaf-0040d8f7410e noneswapsw 0 0 LABEL=LACIE\0401/media/LACIE\0401 vfatdefaults0 2 LABEL=LACIE\0404/media/LACIE\0404 ext4defaults0 2 On boot, I get the error message: The disk drive for /media/LACIE 1 is not ready yet or not present. Continue to wait, or Press S to skip mounting or M for manual recovery If I choose manual recovery, I can immediately invoke mount -a on the command line and both disks are mounted without complaint. If I choose skip (for both external drives) the boot process continues, but I find once I log in that the drives have been auto-mounted on e.g. /media/LACIE 1_ (or 1__ or 1___, such caprice being why I put entries in fstab in the first place). I am now going to relabel both these drives without spaces in their names as a workaround to see if this helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059726 Title: Mounting drives that have '\040' in the name in fstab throws up an error during boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1059726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 375396] Re: ubuntu patch 01_paging.dpatch breaks rdesktop's seamlessrdp
This bug is still present in Natty. Installing version 1.6.0-3 from debian squeeze fixes the problem (although now I suffer from #309315). Installing version 1.7.0-1 from debian sid does not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/375396 Title: ubuntu patch 01_paging.dpatch breaks rdesktop's seamlessrdp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rdesktop/+bug/375396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
