[Touch-packages] [Bug 2074302] Re: Asus Laptop (R558U) does not suspend after upgrade to 24.04
@leonard+peris the `rls-nn-incoming` tag is used by the Ubuntu Foundations team to highlight bugs for the next weekly meeting (thursdays 15-16 UTC on IRC in the #ubuntu-meeting channel). "rls" stands for release and "nn" for Noble Numbat (code name of Ubuntu 24.04 LTS). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2074302 Title: Asus Laptop (R558U) does not suspend after upgrade to 24.04 Status in linux package in Ubuntu: New Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: I was previously running Ubuntu 23.10 on my laptop. I performed a `dist-upgrade` about a week back. Since the upgrade to 24.04 my laptop does not suspend - either by pressing the power-key (previously working on 23.10) or by using the GNOME system power menu. My laptop has integrated Intel graphics as well as NVIDIA GeForce 930MX (GM108M), but i haven't installed proprietary video drivers. It is currently using xserver-x-org-video-nouveau as the video driver. My system reports as running a wayland session, but I find the above X.Org detail confusing. There is currently one inhibitor running `gsd-media-keys`. I filed a bug under systemd as ubuntu-bug would not let me file a bug without a package name. If this is incorrect, please change the package-name as appropriate. I would like to restore previous functionality - system suspend on command. I'd be happy to provide additional logs and to troubleshoot any possible fixes. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd 255.4-1ubuntu8.2 ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8 Uname: Linux 6.8.0-38-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 19:11:12 2024 InstallationDate: Installed on 2019-04-20 (1926 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. X556UR ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-38-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-07-20 (8 days ago) dmi.bios.date: 10/24/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UR.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UR.309:bd10/24/2016:br5.11:svnASUSTeKCOMPUTERINC.:pnX556UR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: X dmi.product.name: X556UR dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474519] Re: realpath fails with inexplicable error message "Not a directory"
Should we set this to "Won't fix" for Trusty? ** Tags added: rls-tt-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1474519 Title: realpath fails with inexplicable error message "Not a directory" Status in coreutils: Fix Released Status in coreutils package in Ubuntu: Fix Released Status in coreutils source package in Trusty: Fix Committed Bug description: After reading `man realpath` it should be clear why $ cd /tmp $ touch a $ realpath ./a/.. realpath: ‘./a/..’: Not a directory occurs. The manpage doesn't contain the word "directory" and thus the error message can't make sense. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: coreutils 8.23-3ubuntu1 Uname: Linux 4.1.1-040101-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 14 21:09:07 2015 InstallationDate: Installed on 2015-06-08 (36 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: coreutils UpgradeStatus: Upgraded to vivid on 2015-06-09 (35 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/coreutils/+bug/1474519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2075338] Re: merge coreutils 9.4-3.1 from Debian unstable
** Merge proposal linked: https://code.launchpad.net/~dviererbe/ubuntu/+source/coreutils/+git/coreutils/+merge/470473 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/2075338 Title: merge coreutils 9.4-3.1 from Debian unstable Status in coreutils package in Ubuntu: In Progress Status in coreutils source package in Oracular: In Progress Bug description: This is the tracking bug for merging coreutils 9.4-3.1 from Debian unstable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2075338/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474519] Re: realpath fails with inexplicable error message "Not a directory"
** Changed in: coreutils (Ubuntu Trusty) Status: Fix Committed => Won't Fix ** Tags removed: rls-tt-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1474519 Title: realpath fails with inexplicable error message "Not a directory" Status in coreutils: Fix Released Status in coreutils package in Ubuntu: Fix Released Status in coreutils source package in Trusty: Won't Fix Bug description: After reading `man realpath` it should be clear why $ cd /tmp $ touch a $ realpath ./a/.. realpath: ‘./a/..’: Not a directory occurs. The manpage doesn't contain the word "directory" and thus the error message can't make sense. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: coreutils 8.23-3ubuntu1 Uname: Linux 4.1.1-040101-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 14 21:09:07 2015 InstallationDate: Installed on 2015-06-08 (36 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: coreutils UpgradeStatus: Upgraded to vivid on 2015-06-09 (35 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/coreutils/+bug/1474519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474519] Re: realpath fails with inexplicable error message "Not a directory"
The fix is released in all supported Ubuntu versions, except for Ubuntu 14.04 LTS (Trusty Tahr). ** Also affects: coreutils (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: coreutils (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: coreutils (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1474519 Title: realpath fails with inexplicable error message "Not a directory" Status in coreutils: Fix Released Status in coreutils package in Ubuntu: Fix Released Status in coreutils source package in Trusty: Fix Committed Bug description: After reading `man realpath` it should be clear why $ cd /tmp $ touch a $ realpath ./a/.. realpath: ‘./a/..’: Not a directory occurs. The manpage doesn't contain the word "directory" and thus the error message can't make sense. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: coreutils 8.23-3ubuntu1 Uname: Linux 4.1.1-040101-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 14 21:09:07 2015 InstallationDate: Installed on 2015-06-08 (36 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: coreutils UpgradeStatus: Upgraded to vivid on 2015-06-09 (35 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/coreutils/+bug/1474519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450179] Re: manpage of cut should explain how to read from stdin
This is explained in the man pages of supported Ubuntu releases. See: - Ubuntu 20.04 LTS (focal): https://manpages.ubuntu.com/manpages/focal/en/man1/cut.1.html - Ubuntu 22.04 LTS (jammy): https://manpages.ubuntu.com/manpages/jammy/en/man1/cut.1.html - Ubuntu 24.04 LTS (noble): https://manpages.ubuntu.com/manpages/noble/en/man1/cut.1.html - Ubuntu 24.10 (oracular): https://manpages.ubuntu.com/manpages/oracular/en/man1/cut.1.html ** Changed in: coreutils (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1450179 Title: manpage of cut should explain how to read from stdin Status in coreutils: Fix Released Status in coreutils package in Ubuntu: Fix Released Bug description: It's a crucial usecase. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: coreutils 8.23-3ubuntu1 Uname: Linux 4.0.0-04-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 29 22:00:24 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-04-02 (26 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: coreutils SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/coreutils/+bug/1450179/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 416981] Re: coreutils: du(1) doesn't summarize correctly
The two Ubuntu versions 9.10 (karmic) and 10.04 (lucid), that are mentioned in this bug reached its end-of-life. Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013. Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases This bug seems also to be fixed in Ubuntu 24.04 (Noble Numbat), therefore I will put it to Fix Released. We appreciate that this bug may be old and you might not be interested in discussing it anymore. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: coreutils (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/416981 Title: coreutils: du(1) doesn't summarize correctly Status in coreutils package in Ubuntu: Fix Released Bug description: Binary package hint: coreutils Running 'du -hs ' returns a radically different size summary as displayed in the folder properties of Nautilus in Gnome. The folder I am trying with is displayed as follows in Nautilus: 2,966 items, totalling 54.0 MB du(1) 'du -hs directory' shows: 4.1Mdirectory/ I am running Ubuntu 9.04 64bit on a Dell Latitude D630, all updates installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/416981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2074213] [NEW] Testcase curl-ldapi-test fails for curl 8.9.0-1ubuntu1
://autopkgtest.ubuntu.com/results/autopkgtest-oracular-dviererbe-ppa/oracular/amd64/c/curl/20240726_110458_297e3@/log.gz - arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-oracular-dviererbe-ppa/oracular/arm64/c/curl/20240726_112320_fb8be@/log.gz - armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-oracular-dviererbe-ppa/oracular/armhf/c/curl/20240726_103536_5739a@/log.gz - ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-oracular-dviererbe-ppa/oracular/ppc64el/c/curl/20240726_103812_26a93@/log.gz - s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-oracular-dviererbe-ppa/oracular/s390x/c/curl/20240726_102839_4f7fd@/log.gz ** Affects: curl (Ubuntu) Importance: Wishlist Assignee: Dominik Viererbe (dviererbe) Status: In Progress ** Tags: foundations-todo ** Changed in: curl (Ubuntu) Status: New => In Progress ** Changed in: curl (Ubuntu) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Changed in: curl (Ubuntu) Importance: Undecided => Wishlist ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2074213 Title: Testcase curl-ldapi-test fails for curl 8.9.0-1ubuntu1 Status in curl package in Ubuntu: In Progress Bug description: I am in the process of merging 8.9.0-1 from Debian unstable. Unfortunately the testcase curl-ldapi-test fails. It fails in Debian too, so it need fixing for merging. Example log snippet from a failed run: 847s ## Building ldap-test app 847s Package libidn2 was not found in the pkg-config search path. 847s Perhaps you should add the directory containing `libidn2.pc' 847s to the PKG_CONFIG_PATH environment variable 847s Package 'libidn2', required by 'libcurl', not found 847s Package 'zlib', required by 'libcurl', not found 847s Package 'libbrotlidec', required by 'libcurl', not found 847s Package 'libzstd', required by 'libcurl', not found 847s Package 'openssl', required by 'libcurl', not found 847s Package 'libpsl', required by 'libcurl', not found 847s Package 'libssh', required by 'libcurl', not found 847s Package 'librtmp', required by 'libcurl', not found 847s Package 'libnghttp2', required by 'libcurl', not found 847s /usr/bin/ld: /tmp/ccwH6J68.o: in function `ldap_perror': 847s LDAP-bindata.c:(.text+0x15b): undefined reference to `ldap_err2string' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0x17a): undefined reference to `ldap_x_utf8s_to_mbs' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0x287): undefined reference to `ldap_x_utf8s_to_mbs' 847s /usr/bin/ld: /tmp/ccwH6J68.o: in function `main': 847s LDAP-bindata.c:(.text+0x60e): undefined reference to `ldap_set_option' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0x640): undefined reference to `ldap_set_option' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0x689): undefined reference to `ldap_initialize' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0x72c): undefined reference to `ldap_unbind_ext' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0x775): undefined reference to `ldap_connect' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0x7d8): undefined reference to `ldap_sasl_bind_s' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0x81b): undefined reference to `ldap_unbind_ext' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0xaa2): undefined reference to `ldap_add_ext_s' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0xae1): undefined reference to `ldap_unbind_ext' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0xb2a): undefined reference to `ldap_unbind_ext' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0xc67): undefined reference to `curl_global_init' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0xc83): undefined reference to `curl_easy_strerror' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0xcb5): undefined reference to `curl_global_cleanup' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0xce9): undefined reference to `curl_global_cleanup' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0xe25): undefined reference to `ldap_url_desc2str' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0xe68): undefined reference to `curl_easy_init' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0xeab): undefined reference to `ldap_memfree' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0xf21): undefined reference to `curl_easy_cleanup' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0xf30): undefined reference to `ldap_memfree' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0xf65): undefined reference to `curl_easy_setopt' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0xfa5): undefined reference to `curl_easy_setopt' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0xfe5): undefined reference to `curl_easy_setopt' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0x1021): undefined reference to `curl_easy_setopt' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0x105d): undefined reference to `curl_easy_setopt' 847s /usr/bin/ld: LDAP-bindata.c:(.text+0x1079):
[Touch-packages] [Bug 2073950] Re: Merge curl 8.9.0-1 from Debian unstable
** Description changed: - This is the tracking bug report for merging curl 8.8.0-4 from Debian + This is the tracking bug report for merging curl 8.9.0-1 from Debian unstable into Ubuntu Oracular Oriole. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2073950 Title: Merge curl 8.9.0-1 from Debian unstable Status in curl package in Ubuntu: In Progress Status in curl source package in Oracular: In Progress Bug description: This is the tracking bug report for merging curl 8.9.0-1 from Debian unstable into Ubuntu Oracular Oriole. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2073950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2074166] Re: Merge gzip 1.12-1.1 from Debian unstable
** Merge proposal linked: https://code.launchpad.net/~dviererbe/ubuntu/+source/gzip/+git/gzip/+merge/470170 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/2074166 Title: Merge gzip 1.12-1.1 from Debian unstable Status in gzip package in Ubuntu: In Progress Bug description: This is the tracking bug to merge gzip 1.12-1.1 from Debian unstable into Ubuntu Oracular Oriole. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/2074166/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2074166] [NEW] Merge gzip 1.12-1.1 from Debian unstable
Public bug reported: This is the tracking bug to merge gzip 1.12-1.1 from Debian unstable into Ubuntu Oracular Oriole. ** Affects: gzip (Ubuntu) Importance: Wishlist Assignee: Dominik Viererbe (dviererbe) Status: In Progress ** Changed in: gzip (Ubuntu) Importance: Undecided => Wishlist ** Changed in: gzip (Ubuntu) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Changed in: gzip (Ubuntu) Status: New => In Progress ** Description changed: - This is the tracking bug to merge unzip 1.12-1.1 from Debian unstable + This is the tracking bug to merge gzip 1.12-1.1 from Debian unstable into Ubuntu Oracular Oriole. ** Summary changed: - Merge unzip 1.12-1.1 from Debian unstable + Merge gzip 1.12-1.1 from Debian unstable -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/2074166 Title: Merge gzip 1.12-1.1 from Debian unstable Status in gzip package in Ubuntu: In Progress Bug description: This is the tracking bug to merge gzip 1.12-1.1 from Debian unstable into Ubuntu Oracular Oriole. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/2074166/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2071468] Re: ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not defined
** Merge proposal unlinked:
https://code.launchpad.net/~dviererbe/ubuntu/+source/curl/+git/curl/+merge/470121
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to graphite2 in Ubuntu.
https://bugs.launchpad.net/bugs/2071468
Title:
ELF package metadata failure: environment variable ‘DEB_HOST_ARCH’ not
defined
Status in asymptote package in Ubuntu:
Fix Released
Status in curl package in Ubuntu:
Fix Released
Status in doxygen package in Ubuntu:
Fix Released
Status in dpkg package in Ubuntu:
Triaged
Status in graphite2 package in Ubuntu:
Fix Released
Status in gsequencer package in Ubuntu:
Fix Released
Status in haskell-devscripts package in Ubuntu:
Fix Released
Status in jose package in Ubuntu:
New
Status in ksmtuned package in Ubuntu:
Fix Released
Status in libreoffice package in Ubuntu:
Fix Released
Status in libtpms package in Ubuntu:
New
Status in mosh package in Ubuntu:
Fix Released
Status in mwrap package in Ubuntu:
Fix Released
Status in proftpd package in Ubuntu:
New
Status in proftpd-dfsg package in Ubuntu:
Fix Released
Status in serf package in Ubuntu:
Fix Released
Status in speech-dispatcher package in Ubuntu:
New
Status in squid package in Ubuntu:
Fix Released
Status in swtpm package in Ubuntu:
Fix Released
Status in texinfo package in Ubuntu:
Triaged
Bug description:
The ELF package note metadata introduced in dpkg 1.22.6ubuntu11
(refined in 1.22.6ubuntu14) can cause this failure:
```
gcc fatal error: environment variable ‘DEB_HOST_ARCH’ not defined
```
This happens when the `-specs=/usr/share/dpkg/elf-package-
metadata.specs` parameter is set but the needed environment variables
are not set. Cases:
1. Only the LDFLAGS is queried from dpkg-buildflags. Affected source
packages builds: python3.12, openjdk-21, cdbs (causing dvbstreamer and
rp-pppoe fail to build)
2. autopkgtests
3. debugging a crash of an application build with the -spec parameter
4. People like to iteratively continue building the software in the
build dir while hacking on the package and then have no environment
variable set.
This approach is too fragile. An alternative approach would be to specify the
`--package-metadata` linker flag directly. The problem with that approach is
that the curly brackets and quotation marks need to be escaped. Example
failure: Building dpkg would add this parameter to the LDFLAGS:
```
-Wl,--package-metadata,{"type":"deb","os":"ubuntu","name":"dpkg","version":"1.22.6ubuntu15","architecture":"amd64"}
```
The following configure script call (non-relevant parameters deleted):
```
$ gcc
-Wl,--package-metadata,{type:deb,os:ubuntu,name:dpkg,version:1.22.6ubuntu15,architecture:amd64}
/usr/bin/ld: cannot find {type:deb: No such file or directory
/usr/bin/ld: cannot find os:ubuntu: No such file or directory
/usr/bin/ld: cannot find name:dpkg: No such file or directory
/usr/bin/ld: cannot find version:1.22.6ubuntu15: No such file or directory
/usr/bin/ld: cannot find architecture:amd64}: No such file or directory
```
Proposed solution: Add support for an `--escaped-package-metadata` parameter
to the linkers that takes an URL encoded (RFC 3986) parameter. Example:
```
-Wl,--encoded-package-metadata,%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22dpkg%22%2C%22version%22:%221.22.6ubuntu15%22%2C%22architecture%22:%22amd64%22%7D
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/asymptote/+bug/2071468/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2073950] Re: Merge curl 8.8.0-4 from Debian unstable
** Merge proposal linked: https://code.launchpad.net/~dviererbe/ubuntu/+source/curl/+git/curl/+merge/470121 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2073950 Title: Merge curl 8.8.0-4 from Debian unstable Status in curl package in Ubuntu: In Progress Status in curl source package in Oracular: In Progress Bug description: This is the tracking bug report for merging curl 8.8.0-4 from Debian unstable into Ubuntu Oracular Oriole. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2073950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2073950] Re: Merge curl 8.8.0-4 from Debian unstable
Autopkgtests succeeded. I am preparing the merge proposal now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2073950 Title: Merge curl 8.8.0-4 from Debian unstable Status in curl package in Ubuntu: In Progress Status in curl source package in Oracular: In Progress Bug description: This is the tracking bug report for merging curl 8.8.0-4 from Debian unstable into Ubuntu Oracular Oriole. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2073950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2073950] Re: Merge curl 8.8.0-4 from Debian unstable
The merge candidate built successfully in my PPA: https://launchpad.net/~dviererbe/+archive/ubuntu/ppa/+packages It took a while for Launchpad to publish the binaries. I triggered autopkgtests for amd64, arm64, armhf, ppc64el, s390x -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2073950 Title: Merge curl 8.8.0-4 from Debian unstable Status in curl package in Ubuntu: In Progress Status in curl source package in Oracular: In Progress Bug description: This is the tracking bug report for merging curl 8.8.0-4 from Debian unstable into Ubuntu Oracular Oriole. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2073950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2028868] [NEW] make mmdebstrap autopkgtest test-case work for ubuntu archive
Public bug reported: The mmdebstrap autopkgtest test-case is currently disabled, because it just tests the debian archive and not the ubuntu archive. This is a tracking bug to make the testcase work for the ubuntu archive. ** Affects: dash (Ubuntu) Importance: Undecided Assignee: Dominik Viererbe (dviererbe) Status: New ** Tags: foundations-todo ** Changed in: dash (Ubuntu) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/2028868 Title: make mmdebstrap autopkgtest test-case work for ubuntu archive Status in dash package in Ubuntu: New Bug description: The mmdebstrap autopkgtest test-case is currently disabled, because it just tests the debian archive and not the ubuntu archive. This is a tracking bug to make the testcase work for the ubuntu archive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/2028868/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2026730] Re: Merge dash 0.5.12-6 from debian
** Changed in: dash (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/2026730 Title: Merge dash 0.5.12-6 from debian Status in dash package in Ubuntu: Fix Committed Bug description: This is a tracking bug to merge dash 0.5.12-6 from debian. Below now follows the report of the automated merge of the Ubuntu changes to the dash source package against the new Debian version. This file is designed to be both human readable and machine-parseable. Any line beginning with four spaces is a file that should be downloaded for the complete merge set. Here are the particulars of the three versions of dash that were chosen for the merge. The base is the newest version that is a common ancestor of both the Ubuntu and Debian packages. It may be of a different upstream version, but that's not usually a problem. The files are the source package itself, and the patch from the common base to that version. base: 0.5.12-2 dash_0.5.12-2.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-2.debian.tar.xz ubuntu: 0.5.12-2ubuntu1 dash_0.5.12-2ubuntu1.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-2ubuntu1.debian.tar.xz base -> ubuntu dash_0.5.12-2ubuntu1.patch debian: 0.5.12-6 dash_0.5.12-6.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-6.debian.tar.xz base -> debian dash_0.5.12-6.patch Generated Result Due to conflict or error, it was not possible to automatically create a source package. Instead the result of the merge has been placed into the following tar file which you will need to turn into a source package once the problems have been resolved. dash_0.5.12-6ubuntu1.src.tar.gz Conflicts = In one or more cases, there were different changes made in both Ubuntu and Debian to the same file; these are known as conflicts. It is not possible for these to be automatically resolved, so this source needs human attention. Those files marked with 'C ' contain diff3 conflict markers, which can be resolved using the text editor of your choice. Those marked with 'C*' could not be merged that way, so you will find .UBUNTU and .DEBIAN files instead and should choose one of them or a combination of both, moving it to the real filename and deleting the other. C debian/tests/control Once you have a source package you are happy to upload, you should make sure you include the orig.tar.* if appropriate and information about all the versions included in the merge. Use the following command to generate a correct .changes file: $ dpkg-genchanges -S -v0.5.12-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/2026730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2026730] Re: Merge dash 0.5.12-6 from debian
** Merge proposal linked: https://code.launchpad.net/~dviererbe/ubuntu/+source/dash/+git/dash/+merge/446503 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/2026730 Title: Merge dash 0.5.12-6 from debian Status in dash package in Ubuntu: New Bug description: This is a tracking bug to merge dash 0.5.12-6 from debian. Below now follows the report of the automated merge of the Ubuntu changes to the dash source package against the new Debian version. This file is designed to be both human readable and machine-parseable. Any line beginning with four spaces is a file that should be downloaded for the complete merge set. Here are the particulars of the three versions of dash that were chosen for the merge. The base is the newest version that is a common ancestor of both the Ubuntu and Debian packages. It may be of a different upstream version, but that's not usually a problem. The files are the source package itself, and the patch from the common base to that version. base: 0.5.12-2 dash_0.5.12-2.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-2.debian.tar.xz ubuntu: 0.5.12-2ubuntu1 dash_0.5.12-2ubuntu1.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-2ubuntu1.debian.tar.xz base -> ubuntu dash_0.5.12-2ubuntu1.patch debian: 0.5.12-6 dash_0.5.12-6.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-6.debian.tar.xz base -> debian dash_0.5.12-6.patch Generated Result Due to conflict or error, it was not possible to automatically create a source package. Instead the result of the merge has been placed into the following tar file which you will need to turn into a source package once the problems have been resolved. dash_0.5.12-6ubuntu1.src.tar.gz Conflicts = In one or more cases, there were different changes made in both Ubuntu and Debian to the same file; these are known as conflicts. It is not possible for these to be automatically resolved, so this source needs human attention. Those files marked with 'C ' contain diff3 conflict markers, which can be resolved using the text editor of your choice. Those marked with 'C*' could not be merged that way, so you will find .UBUNTU and .DEBIAN files instead and should choose one of them or a combination of both, moving it to the real filename and deleting the other. C debian/tests/control Once you have a source package you are happy to upload, you should make sure you include the orig.tar.* if appropriate and information about all the versions included in the merge. Use the following command to generate a correct .changes file: $ dpkg-genchanges -S -v0.5.12-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/2026730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2026730] Re: Merge dash 0.5.12-6 from debian
I am currently building the merged package here: https://launchpad.net/~dviererbe/+archive/ubuntu/dash-merge- lp2026730-mantic/+packages ** Changed in: dash (Ubuntu) Assignee: (unassigned) => Dominik Viererbe (dviererbe) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/2026730 Title: Merge dash 0.5.12-6 from debian Status in dash package in Ubuntu: New Bug description: This is a tracking bug to merge dash 0.5.12-6 from debian. Below now follows the report of the automated merge of the Ubuntu changes to the dash source package against the new Debian version. This file is designed to be both human readable and machine-parseable. Any line beginning with four spaces is a file that should be downloaded for the complete merge set. Here are the particulars of the three versions of dash that were chosen for the merge. The base is the newest version that is a common ancestor of both the Ubuntu and Debian packages. It may be of a different upstream version, but that's not usually a problem. The files are the source package itself, and the patch from the common base to that version. base: 0.5.12-2 dash_0.5.12-2.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-2.debian.tar.xz ubuntu: 0.5.12-2ubuntu1 dash_0.5.12-2ubuntu1.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-2ubuntu1.debian.tar.xz base -> ubuntu dash_0.5.12-2ubuntu1.patch debian: 0.5.12-6 dash_0.5.12-6.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-6.debian.tar.xz base -> debian dash_0.5.12-6.patch Generated Result Due to conflict or error, it was not possible to automatically create a source package. Instead the result of the merge has been placed into the following tar file which you will need to turn into a source package once the problems have been resolved. dash_0.5.12-6ubuntu1.src.tar.gz Conflicts = In one or more cases, there were different changes made in both Ubuntu and Debian to the same file; these are known as conflicts. It is not possible for these to be automatically resolved, so this source needs human attention. Those files marked with 'C ' contain diff3 conflict markers, which can be resolved using the text editor of your choice. Those marked with 'C*' could not be merged that way, so you will find .UBUNTU and .DEBIAN files instead and should choose one of them or a combination of both, moving it to the real filename and deleting the other. C debian/tests/control Once you have a source package you are happy to upload, you should make sure you include the orig.tar.* if appropriate and information about all the versions included in the merge. Use the following command to generate a correct .changes file: $ dpkg-genchanges -S -v0.5.12-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/2026730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2026730] [NEW] Merge dash 0.5.12-6 from debian
Public bug reported: This is a tracking bug to merge dash 0.5.12-6 from debian. Below now follows the report of the automated merge of the Ubuntu changes to the dash source package against the new Debian version. This file is designed to be both human readable and machine-parseable. Any line beginning with four spaces is a file that should be downloaded for the complete merge set. Here are the particulars of the three versions of dash that were chosen for the merge. The base is the newest version that is a common ancestor of both the Ubuntu and Debian packages. It may be of a different upstream version, but that's not usually a problem. The files are the source package itself, and the patch from the common base to that version. base: 0.5.12-2 dash_0.5.12-2.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-2.debian.tar.xz ubuntu: 0.5.12-2ubuntu1 dash_0.5.12-2ubuntu1.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-2ubuntu1.debian.tar.xz base -> ubuntu dash_0.5.12-2ubuntu1.patch debian: 0.5.12-6 dash_0.5.12-6.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-6.debian.tar.xz base -> debian dash_0.5.12-6.patch Generated Result Due to conflict or error, it was not possible to automatically create a source package. Instead the result of the merge has been placed into the following tar file which you will need to turn into a source package once the problems have been resolved. dash_0.5.12-6ubuntu1.src.tar.gz Conflicts = In one or more cases, there were different changes made in both Ubuntu and Debian to the same file; these are known as conflicts. It is not possible for these to be automatically resolved, so this source needs human attention. Those files marked with 'C ' contain diff3 conflict markers, which can be resolved using the text editor of your choice. Those marked with 'C*' could not be merged that way, so you will find .UBUNTU and .DEBIAN files instead and should choose one of them or a combination of both, moving it to the real filename and deleting the other. C debian/tests/control Once you have a source package you are happy to upload, you should make sure you include the orig.tar.* if appropriate and information about all the versions included in the merge. Use the following command to generate a correct .changes file: $ dpkg-genchanges -S -v0.5.12-2ubuntu1 ** Affects: dash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/2026730 Title: Merge dash 0.5.12-6 from debian Status in dash package in Ubuntu: New Bug description: This is a tracking bug to merge dash 0.5.12-6 from debian. Below now follows the report of the automated merge of the Ubuntu changes to the dash source package against the new Debian version. This file is designed to be both human readable and machine-parseable. Any line beginning with four spaces is a file that should be downloaded for the complete merge set. Here are the particulars of the three versions of dash that were chosen for the merge. The base is the newest version that is a common ancestor of both the Ubuntu and Debian packages. It may be of a different upstream version, but that's not usually a problem. The files are the source package itself, and the patch from the common base to that version. base: 0.5.12-2 dash_0.5.12-2.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-2.debian.tar.xz ubuntu: 0.5.12-2ubuntu1 dash_0.5.12-2ubuntu1.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-2ubuntu1.debian.tar.xz base -> ubuntu dash_0.5.12-2ubuntu1.patch debian: 0.5.12-6 dash_0.5.12-6.dsc dash_0.5.12.orig.tar.gz dash_0.5.12-6.debian.tar.xz base -> debian dash_0.5.12-6.patch Generated Result Due to conflict or error, it was not possible to automatically create a source package. Instead the result of the merge has been placed into the following tar file which you will need to turn into a source package once the problems have been resolved. dash_0.5.12-6ubuntu1.src.tar.gz Conflicts = In one or more cases, there were different changes made in both Ubuntu and Debian to the same file; these are known as conflicts. It is not possible for these to be automatically resolved, so this source needs human attention. Those files marked with 'C ' contain diff3 conflict markers, which can be resolved using the text editor of your choice. Those marked with 'C*' could not be merged that way, so you will find .UBUNTU and .DEBIAN files instead and should choose one of them or a combination of both, moving it to the real filename and deleting the other. C debian/tests/control Once you have a source package you are happy to upload, you should make sure you
[Touch-packages] [Bug 2023016] Re: Merge 13.2-1 into mantic
The Merge was more complicated that anticipated, but I finally managed to merge it. I locally built it and did some trivial testing. Everything seems fine. The Merge can be downloaded here: https://launchpad.net/~dviererbe/+archive/ubuntu/lp2023016-gdb-merge-mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2023016 Title: Merge 13.2-1 into mantic Status in gdb package in Ubuntu: In Progress Bug description: The upstream version 13.2-1 should be merged into mantic. The current version is 13.1-2ubuntu2. See the merge conflict report: https://merges.ubuntu.com/g/gdb/REPORT Note: this is a tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2023016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2023016] Re: Merge 13.1-3 into mantic
** Description changed: - The upstream version 13.1-3 should be merged into mantic. The current + The upstream version 13.2-1 should be merged into mantic. The current version is 13.1-2ubuntu2. See the merge conflict report: https://merges.ubuntu.com/g/gdb/REPORT Note: this is a tracking bug ** Summary changed: - Merge 13.1-3 into mantic + Merge 13.2-1 into mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2023016 Title: Merge 13.2-1 into mantic Status in gdb package in Ubuntu: In Progress Bug description: The upstream version 13.2-1 should be merged into mantic. The current version is 13.1-2ubuntu2. See the merge conflict report: https://merges.ubuntu.com/g/gdb/REPORT Note: this is a tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2023016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390905] Re: gdb list not from the first line
Thanks for reporting this bug to help improve Ubuntu!
I looked into the source code for the gdb list command (see at the end
of this comment). It looks to me that gdb will center the listing if it
is called for the first time with no other parameters.
If you want that the listing starts at the beginning of the file, use
"list 1" or "list FILE:1". (See more help by typing "help list").
We appreciate that this bug may be old and you might not be interested
in discussing it anymore. But if you are then please re-test. If you
then still think that this is a bug, please add a comment here telling
us, why you think this is a bug, how to re-produce it and which version
it is in (or at least which version you used).
Partial Source Code of gdb list command
===
/* Pull in the current default source line if necessary. */
if (arg == NULL || ((arg[0] == '+' || arg[0] == '-') && arg[1] == '\0'))
{
set_default_source_symtab_and_line ();
symtab_and_line cursal = get_current_source_symtab_and_line ();
/* If this is the first "list" since we've set the current
source line, center the listing around that line. */
if (get_first_line_listed () == 0)
{
int first;
first = std::max (cursal.line - get_lines_to_list () / 2, 1);
/* A small special case --- if listing backwards, and we
should list only one line, list the preceding line,
instead of the exact line we've just shown after e.g.,
stopping for a breakpoint. */
if (arg != NULL && arg[0] == '-'
&& get_lines_to_list () == 1 && first > 1)
first -= 1;
print_source_lines (cursal.symtab, source_lines_range (first), 0);
}
** Changed in: gdb (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1390905
Title:
gdb list not from the first line
Status in gdb package in Ubuntu:
Invalid
Bug description:
when I use gdb list command, it does not list source code from the
first line.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1390905/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902225] Re: SRU: update gdb 8.1.1 for 18.04 LTS
** Changed in: gdb (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1902225 Title: SRU: update gdb 8.1.1 for 18.04 LTS Status in gdb package in Ubuntu: Invalid Status in gdb source package in Bionic: Fix Released Bug description: gdb 8.1.1 is a minor bug fix release for 8.1. Some of the issues fixed in 8.1.1 are already fixed in the branch update in 8.1-0ubuntu3: * gdb 8.1.1 release. This is a minor corrective release over GDB 8.1, fixing following issues: - PR gdb/23028 (inconsistent disassemble of vcvtpd2dq) - PR gdb/23053 (Fix -D_GLIBCXX_DEBUG gdb-add-index regression) - PR gdb/23127 ([AArch64] GDB cannot be used for debugging software that uses high Virtual Addresses) - PR server/23158 (gdbserver no longer functional on Windows) - PR breakpoints/23210 ([8.1/8.2 Regression] Bogus Breakpoint address adjusted from 0xf7fe7dd3 to 0xf7fe7dd3) Already fixed in 8.1-0ubuntu3: - PR gdb/22824 (misleading description of new rbreak Python function in GDB 8.1 NEWS file) - PR gdb/22849 (ctrl-c doesn't work in extended-remote) - PR gdb/22907 ([Regression] gdbserver doesn't work with filename-only binaries). * Allow remote debugging over a Unix local domain socket. LP: #1901026. This minor version update fixes four upstream issues (not counting the Windows specific issue), plus allows remote debugging over a Unix local domain socket., a patch taken from the 8.2 development. Validation: The tests run during build time are passing, and the remote debugging is checked to be working (no automated test case). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1902225/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1131841] Re: gdb run as root: untrusted .gdbinit causes malloc arena corruption crash
Thank you for reporting this bug to Ubuntu. Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases I could not replicate the crash in currently supported versions (focal, jammy, kinetic, lunar, mantic). We appreciate that this bug may be old and you might not be interested in discussing it anymore. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gdb (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1131841 Title: gdb run as root: untrusted .gdbinit causes malloc arena corruption crash Status in gdb: Invalid Status in gdb package in Ubuntu: Incomplete Bug description: When running gdb as root, the existence of ~/.gdbinit (untrusted) causes gdb to crash with a duplicate free or other heap corruption. This bug is due to some debian/ubuntu specific patches ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gdb 7.5-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Fri Feb 22 17:36:12 2013 InstallationDate: Installed on 2011-10-31 (480 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64+mac (20111012) MarkForUpload: True SourcePackage: gdb UpgradeStatus: Upgraded to quantal on 2012-10-14 (131 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1131841/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1332484] Re: GDB Demangler crashes in 14.10 and 14.04
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
Ubuntu 14.04 (trusty) reached end-of-standard-support on Apri
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
I could not replicate that bug in currently supported versions (focal,
jammy, kinetic, lunar, mantic):
$ lxc launch images:ubuntu/CODENAME tester # replace CODENAME with focal,
jammy, kinetic, lunar, mantic
$ lxc exec tester bash
$ apt update
$ apt install -y gcc gdb
$ echo 'void
_ZN5Utils9transformIPN15ProjectExplorer13BuildStepListEZNKS1_18BuildConfiguration14knownStepListsEvEUlS3_E_EEN4Myns5QListIDTclfp0_cvT__ERKNS7_IS8_EET0_()
{ } int main() {}' | gcc -xc -
$ gdb ./a.out # type "quit" to exit gdb
$ exit
$ lxc stop tester
$ lxc delete tester
We appreciate that this bug may be old and you might not be interested
in discussing it anymore. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.
** Changed in: gdb (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1332484
Title:
GDB Demangler crashes in 14.10 and 14.04
Status in gdb:
Unknown
Status in gdb package in Ubuntu:
Incomplete
Bug description:
(gdb crashed with SIGSEGV in _IO_vfprintf_internal())
This is to duplicate an upstream bug report that affects users on both
14.10 and 14.04 LTS.
Test case:
echo 'void
_ZN5Utils9transformIPN15ProjectExplorer13BuildStepListEZNKS1_18BuildConfiguration14knownStepListsEvEUlS3_E_EEN4Myns5QListIDTclfp0_cvT__ERKNS7_IS8_EET0_()
{ } int main() {}' | gcc -xc - && gdb ./a.out
Upstream has a patch, and it'd be nice to also SRU the fix to 14.04
LTS because users are seeing it (as reported on IRC).
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1332484/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2023016] Re: Merge 13.1-3 into mantic
Conflict Report: gdb Sat May 13 15:44:04 2023 Below now follows the report of the automated merge of the Ubuntu changes to the gdb source package against the new Debian version. This file is designed to be both human readable and machine-parseable. Any line beginning with four spaces is a file that should be downloaded for the complete merge set. Here are the particulars of the three versions of gdb that were chosen for the merge. The base is the newest version that is a common ancestor of both the Ubuntu and Debian packages. It may be of a different upstream version, but that's not usually a problem. The files are the source package itself, and the patch from the common base to that version. base: 13.1-2 gdb_13.1-2.dsc gdb_13.1.orig.tar.xz gdb_13.1.orig.tar.xz.asc gdb_13.1-2.debian.tar.xz ubuntu: 13.1-2ubuntu2 gdb_13.1-2ubuntu2.dsc gdb_13.1.orig.tar.xz gdb_13.1-2ubuntu2.debian.tar.xz base -> ubuntu gdb_13.1-2ubuntu2.patch debian: 13.1-3 gdb_13.1-3.dsc gdb_13.1.orig.tar.xz gdb_13.1.orig.tar.xz.asc gdb_13.1-3.debian.tar.xz base -> debian gdb_13.1-3.patch Generated Result Due to conflict or error, it was not possible to automatically create a source package. Instead the result of the merge has been placed into the following tar file which you will need to turn into a source package once the problems have been resolved. gdb_13.1-3ubuntu1.src.tar.gz Conflicts = In one or more cases, there were different changes made in both Ubuntu and Debian to the same file; these are known as conflicts. It is not possible for these to be automatically resolved, so this source needs human attention. Those files marked with 'C ' contain diff3 conflict markers, which can be resolved using the text editor of your choice. Those marked with 'C*' could not be merged that way, so you will find .UBUNTU and .DEBIAN files instead and should choose one of them or a combination of both, moving it to the real filename and deleting the other. C debian/patches/series Once you have a source package you are happy to upload, you should make sure you include the orig.tar.* if appropriate and information about all the versions included in the merge. Use the following command to generate a correct .changes file: $ dpkg-genchanges -S -v13.1-2ubuntu2 ** Changed in: gdb (Ubuntu) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Changed in: gdb (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2023016 Title: Merge 13.1-3 into mantic Status in gdb package in Ubuntu: In Progress Bug description: The upstream version 13.1-3 should be merged into mantic. The current version is 13.1-2ubuntu2. See the merge conflict report: https://merges.ubuntu.com/g/gdb/REPORT Note: this is a tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2023016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2023016] [NEW] Merge 13.1-3 into mantic
Public bug reported: The upstream version 13.1-3 should be merged into mantic. The current version is 13.1-2ubuntu2. See the merge conflict report: https://merges.ubuntu.com/g/gdb/REPORT Note: this is a tracking bug ** Affects: gdb (Ubuntu) Importance: Undecided Assignee: Dominik Viererbe (dviererbe) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2023016 Title: Merge 13.1-3 into mantic Status in gdb package in Ubuntu: In Progress Bug description: The upstream version 13.1-3 should be merged into mantic. The current version is 13.1-2ubuntu2. See the merge conflict report: https://merges.ubuntu.com/g/gdb/REPORT Note: this is a tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2023016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1992947] Re: gdb fails in Ubuntu-22.04
** Changed in: gdb (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1992947 Title: gdb fails in Ubuntu-22.04 Status in gdb package in Ubuntu: Incomplete Bug description: In Jammy 5.15.0-1014 when i try to debug an application with gdb got below error, Log: root@kria:/home/ubuntu/swetha_bins/v2xpfm# gdb threshold Could not find platform independent libraries Could not find platform dependent libraries Consider setting $PYTHONHOME to [:] Python path configuration: PYTHONHOME = (not set) PYTHONPATH = (not set) program name = '/usr/bin/python' isolated = 0 environment = 1 user site = 1 import site = 1 sys._base_executable = '/usr/bin/python' sys.base_prefix = '/usr' sys.base_exec_prefix = '/usr' sys.platlibdir = 'lib' sys.executable = '/usr/bin/python' sys.prefix = '/usr' sys.exec_prefix = '/usr' sys.path = [ '/usr/lib/python39.zip', '/usr/lib/python3.9', '/usr/lib/lib-dynload', ] Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding Python runtime state: core initialized ModuleNotFoundError: No module named 'encodings' Current thread 0xa057f020 (most recent call first): root@kria:/home/ubuntu/swetha_bins/v2xpfm# root@kria:/home/ubuntu/swetha_bins/v2xpfm# root@kria:/home/ubuntu/swetha_bins/v2xpfm# uname -a Linux kria 5.15.0-1014-xilinx-zynqmp #15-Ubuntu SMP Tue Aug 30 07:56:28 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux root@kria:/home/ubuntu/swetha_bins/v2xpfm# root@kria:/home/ubuntu/swetha_bins/v2xpfm# root@kria:/home/ubuntu/swetha_bins/v2xpfm# file threshold threshold: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (GNU/Linux), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, BuildID[sha1]=ae073c5ee47a3663ef3a06861c5df9bf62147ecd, for GNU/Linux 3.14.0, with debug_info, not stripped root@kria:/home/ubuntu/swetha_bins/v2xpfm# root@kria:/home/ubuntu/swetha_bins/v2xpfm# root@kria:/home/ubuntu/swetha_bins/v2xpfm# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1992947/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2013333] [NEW] Quick Settings in the wrong place after Rotation
Public bug reported: I am currently testing the Ubuntu Desktop amd64 in Lunar Beta. - I opened the quick settings in the top right corner (Good) - I rotated the Laptop by ca. 90 deg => This triggered the Desktop Environment to rotate too (Good) - Note: quick settings are still open - I rotated the Laptop back => This triggered the Desktop Environment to rotate back too (Good) - The quick settings are now Horizontally centered (Unexpected) Note: I tested this during the Installation. I attached a screenshot that shows this. - ISO used: https://cdimage.ubuntu.com/daily-live/20230329/lunar-desktop-amd64.iso - ISO hash and signature verified Device: Lenovo ThinkPad Yoga 460 CPU: 64-Bit Intel Core i7-6500U @2.50GHz x 4 RAM: 8GB Graphics: Mesa Intel HD Graphics 520 (SKL GT2) Storage: 256GB SSD ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2023-03-30 11-13-37.png" https://bugs.launchpad.net/bugs/201/+attachment/5659110/+files/Screenshot%20from%202023-03-30%2011-13-37.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/201 Title: Quick Settings in the wrong place after Rotation Status in xorg package in Ubuntu: New Bug description: I am currently testing the Ubuntu Desktop amd64 in Lunar Beta. - I opened the quick settings in the top right corner (Good) - I rotated the Laptop by ca. 90 deg => This triggered the Desktop Environment to rotate too (Good) - Note: quick settings are still open - I rotated the Laptop back => This triggered the Desktop Environment to rotate back too (Good) - The quick settings are now Horizontally centered (Unexpected) Note: I tested this during the Installation. I attached a screenshot that shows this. - ISO used: https://cdimage.ubuntu.com/daily-live/20230329/lunar-desktop-amd64.iso - ISO hash and signature verified Device: Lenovo ThinkPad Yoga 460 CPU: 64-Bit Intel Core i7-6500U @2.50GHz x 4 RAM: 8GB Graphics: Mesa Intel HD Graphics 520 (SKL GT2) Storage: 256GB SSD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
