[Touch-packages] [Bug 2045574] Re: Ubuntu 22.04 missing CMake installation files from 9.0.0
** Description changed: - As reported in the following question, Ubuntu 22.04 is currently missing the CMake installation files from tinyxml version 9.0.0. + As reported in the following question, Ubuntu 22.04 is currently missing the CMake installation files from tinyxml version 9.0.0. https://answers.launchpad.net/ubuntu/+source/tinyxml2/+question/708581 These were added in the following source PR as part of the 9.0.0 release: https://github.com/leethomason/tinyxml2/pull/861 - A developer noticed that the packaged version on Ubuntu was missing the installation of the new CMake files, and added them in this patch: + A developer noticed that the packaged version on Ubuntu was missing the installation of the new CMake files, and added them in this patch: https://git.launchpad.net/ubuntu/+source/tinyxml2/patch/debian/libtinyxml2-dev.install?id=8ec400cc2fe03ce9760c01fdde017b75b2aeed59 - This patch has not made it to Ubuntu 22. + This patch has not made it to Ubuntu 22.04 - Users of TinyXML2 on Ubuntu 22 are still facing the issue as reported here: + Users of TinyXML2 on Ubuntu 22.04 are still facing the issue as reported here: https://github.com/leethomason/tinyxml2/issues/930#issue-1527973704 The effect is an inability to use find_package(tinyxml2 CONFIG REQUIRED). As I tested out, installing 9.0.0+dfsg-3.1 in Jammy solves the issue. The next step was to create this bug report so that it could be backported. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tinyxml2 in Ubuntu. https://bugs.launchpad.net/bugs/2045574 Title: Ubuntu 22.04 missing CMake installation files from 9.0.0 Status in tinyxml2 package in Ubuntu: New Status in tinyxml2 package in Debian: Fix Released Bug description: As reported in the following question, Ubuntu 22.04 is currently missing the CMake installation files from tinyxml version 9.0.0. https://answers.launchpad.net/ubuntu/+source/tinyxml2/+question/708581 These were added in the following source PR as part of the 9.0.0 release: https://github.com/leethomason/tinyxml2/pull/861 A developer noticed that the packaged version on Ubuntu was missing the installation of the new CMake files, and added them in this patch: https://git.launchpad.net/ubuntu/+source/tinyxml2/patch/debian/libtinyxml2-dev.install?id=8ec400cc2fe03ce9760c01fdde017b75b2aeed59 This patch has not made it to Ubuntu 22.04 Users of TinyXML2 on Ubuntu 22.04 are still facing the issue as reported here: https://github.com/leethomason/tinyxml2/issues/930#issue-1527973704 The effect is an inability to use find_package(tinyxml2 CONFIG REQUIRED). As I tested out, installing 9.0.0+dfsg-3.1 in Jammy solves the issue. The next step was to create this bug report so that it could be backported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tinyxml2/+bug/2045574/+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 2045574] Re: Ubuntu 22.04 missing CMake installation files from 9.0.0
** Bug watch added: Debian Bug tracker #967045 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967045 ** Also affects: tinyxml2 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967045 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tinyxml2 in Ubuntu. https://bugs.launchpad.net/bugs/2045574 Title: Ubuntu 22.04 missing CMake installation files from 9.0.0 Status in tinyxml2 package in Ubuntu: New Status in tinyxml2 package in Debian: Unknown Bug description: As reported in the following question, Ubuntu 22.04 is currently missing the CMake installation files from tinyxml version 9.0.0. https://answers.launchpad.net/ubuntu/+source/tinyxml2/+question/708581 These were added in the following source PR as part of the 9.0.0 release: https://github.com/leethomason/tinyxml2/pull/861 A developer noticed that the packaged version on Ubuntu was missing the installation of the new CMake files, and added them in this patch: https://git.launchpad.net/ubuntu/+source/tinyxml2/patch/debian/libtinyxml2-dev.install?id=8ec400cc2fe03ce9760c01fdde017b75b2aeed59 This patch has not made it to Ubuntu 22. Users of TinyXML2 on Ubuntu 22 are still facing the issue as reported here: https://github.com/leethomason/tinyxml2/issues/930#issue-1527973704 The effect is an inability to use find_package(tinyxml2 CONFIG REQUIRED). As I tested out, installing 9.0.0+dfsg-3.1 in Jammy solves the issue. The next step was to create this bug report so that it could be backported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tinyxml2/+bug/2045574/+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 2039411] Re: Addition of ppa repository failing intermittently
The correct PPA naming is ppa:longsleep/golang-backports and ppa:criu/ppa without tilde character and without "/ubuntu" in the middle. Eventually the code of the script should be modified to cater for usage with wrong-named PPAs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2039411 Title: Addition of ppa repository failing intermittently Status in software-properties package in Ubuntu: Confirmed Bug description: I get following error intermittently when trying to add ppa repository: $ sudo add-apt-repository ppa:~longsleep/ubuntu/golang-backports Cannot add PPA: 'ppa:~longsleep/ubuntu/golang-backports'. The user named '~longsleep' has no PPA named 'ubuntu/golang-backports' Please choose from the following available PPAs: * 'bcmwl': bcmwl * 'couchdb': Apache CouchDB * 'couchdb-precise-backport': Apache CouchDB with Erlang 18 for precise * 'createrepo-backports': Createrepo Backports * 'firehol-backports': Firehol Backports * 'golang-backports': Golang Backports * 'golang-backports-dev': Golang Backports Dev * 'iridium-browser-dev': Iridium Browser Dev dependencies * 'pixel-extras': Pixel extras * 'python2.7-backports': Python 2.7 Backports * 'python3-m2crypto-backports': Python 3 M2Crypto backports * 'stuff': Stuff * 'ubuntu-pine64-flavour-makers': Ubuntu Pine64 Makers PPA After multiple attempts, it may succeed, but the same above command sometimes may return following error as well (intermittently): $ sudo add-apt-repository ppa:~longsleep/ubuntu/golang-backports Traceback (most recent call last): File "/usr/bin/add-apt-repository", line 137, in shortcut = shortcut_handler(line) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 885, in shortcut_handler ret = factory(shortcut) File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 469, in shortcut_handler return PPAShortcutHandler(shortcut) File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 426, in __init__ info = get_ppa_info(self.shortcut) File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 392, in get_ppa_info _get_suggested_ppa_message(user, ppa)) File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 349, in _get_suggested_ppa_message lp_user = get_info_from_lp(LAUNCHPAD_USER_API % user) File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 104, in get_info_from_lp return get_info_from_https(lp_url, True) File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 98, in get_info_from_https return json.loads(data) File "/usr/lib/python3.8/json/__init__.py", line 357, in loads return _default_decoder.decode(s) File "/usr/lib/python3.8/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) File "/usr/lib/python3.8/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2039411/+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 2019927] Re: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error e
zstd: error 70 : Write error : cannot write block : No space left on device bpool/BOOT/ubuntu_bpduzc 663296 655744 7552 99% /boot Your boot partition is far too small. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2019927 Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: This bug report showed up after rebooting first time to 23.04. I have not yet noticed anything actually broken in the system, but uptime is only 6 minutes. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue May 16 23:41:05 2023 Dependencies: firmware-sof-signed 2.2.4-1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-03-21 (786 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) MachineType: ASUSTeK COMPUTER INC. ZenBook UX425IA_UM425IA PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_bpduzc@/vmlinuz-6.2.0-20-generic root=ZFS=rpool/ROOT/ubuntu_bpduzc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: initramfs-tools Title: package linux-firmware 20230323.gitbcdcfbcf-0ubuntu1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-17 (0 days ago) dmi.bios.date: 09/16/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX425IA.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX425IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.307:bd09/16/2020:br5.16:efr3.7:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ZenBook dmi.product.name: ZenBook UX425IA_UM425IA 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/initramfs-tools/+bug/2019927/+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 2017852] Re: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
>From the logs: zstd: error 25 : Write error : No space left on device (cannot write compressed block) Not a bug in the software, but a local problem on your system. You have to clean up your system to create enough free space. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2017852 Title: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 27 07:47:41 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-11-10 (532 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: initramfs-tools Title: package linux-image-5.19.0-41-generic 5.19.0-41.42~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2022-08-27 (242 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017852/+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 1988548] Re: Missing fix for CVE-2022-37434 in zlib1g in focal and jammy
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-37434 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1988548 Title: Missing fix for CVE-2022-37434 in zlib1g in focal and jammy Status in zlib package in Ubuntu: New Bug description: There is a crictical security issue with zlib tracked here [1] The newest version in bionic [2] already has a security patch for it but the one in the focal [3] (and jammy) does not. As can be seen from their respective changelogs in the right hand side panel. Since zlib is loaded by lots of software, e.g. the apache weg server, this could be a problem. It seems that focal, jammy and bionic use the same base zlib version (1.2.11), so maybe the patch there could be recycled? I was asked to create a bug here after asking it as question here [4]. Thank you very much for your hard work! [1] CVE: https://nvd.nist.gov/vuln/detail/CVE-2022-37434 [2] Bionic Package: https://packages.ubuntu.com/bionic/zlib1g [3] Focal Package: https://packages.ubuntu.com/focal/zlib1g [4] Original Question: https://answers.launchpad.net/ubuntu/+source/zlib/+question/703010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1988548/+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 1934559] Re: Typo in capital of Ukraine
There seems to be a first step into that direction in version 2022b (still to be packaged for Ubuntu) https://data.iana.org/time- zones/tzdb/NEWS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1934559 Title: Typo in capital of Ukraine Status in tzdata package in Ubuntu: New Bug description: During installation on a map and in timezone settings there's "Kiev" city, but it's not correct. Should be Kyiv - https://en.wikipedia.org/wiki/Kyiv. Ubuntu 21.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1934559/+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 1969671] Re: Misspelled Ukrainian cities in tzdata
There seems to be a first step into that direction in version 2022b (still to be packaged for Ubuntu) https://data.iana.org/time- zones/tzdb/NEWS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1969671 Title: Misspelled Ukrainian cities in tzdata Status in tzdata package in Ubuntu: New Bug description: When user is prompted to choose a city in the region 'Europe' they have a choice of 4 cities in Ukraine: 23. Kiev -> should be Kyiv 46. Simferopol - > OK 54. Uzhgorod -> should be Uzhhorod 62. Zaporozhye -> should be Zaporizhzhia The 'should be' variant is the only correct transliteration from Ukrainian into English. Possible useful pieces of ubuntu-bug report (run in a headless ubuntu/latest docker image): DistroRelease: Ubuntu 20.04 Package: tzdata 2022a-0ubuntu0.20.04 Tags: focal PackageArchitecture: all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1969671/+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 1985984] Re: package linux-image-5.15.0-46-generic 5.15.0-46.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
>From your logs: Filesystem1K-blocks Used Available Use% Mounted on /dev/nvme1n1p2 719936 609372 58100 92% /boot Probably not enough free space on /boot. Suggested solution: purge old kernels. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1985984 Title: package linux-image-5.15.0-46-generic 5.15.0-46.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Bug showed up at boot-up ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-46-generic 5.15.0-46.49~20.04.1 Uname: Linux 5.18.10-76051810-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Aug 10 20:31:39 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2022-02-26 (166 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-46-generic 5.15.0-46.49~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1985984/+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 1970449] Re: GPG keys are not shown in Software and Updates
Re-running the autopkgtest has succeeded, https://autopkgtest.ubuntu.com/packages/d/crash/jammy/arm64 Confirming the SRU. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1970449 Title: GPG keys are not shown in Software and Updates Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Jammy: Fix Committed Status in software-properties source package in Kinetic: Fix Released Bug description: [Impact] software-properties-gtk does not show the registered apt gpg keys in the "Authentication" tab on my Ubuntu 21.10 and 22.04 systems. [Test Plan] 1. Launch software-properties-gtk 2. Click on the "Authentication" tab 3. At least one key should be listed [Where problems could occur] I fail to come up with possible problems. The failures was a regression and the fixed version has a test case. [Other Infos] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 20:48:04 2022 InstallationDate: Installed on 2022-04-25 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970449/+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 1970449] Re: GPG keys are not shown in Software and Updates
I tested the updated package on my system and I can confirm that the new version now correctly shows the apt keys. Other actions in software- properties-gtk like changing the repository server and disabling -proposed still work as before. For the autopkgtest regression that has been reported in comment #21: This seems to be caused by a transient network hickup, see relevant output from the log below: Ign:1 http://ddebs.ubuntu.com jammy-updates/main arm64 linux-image-unsigned-5.15.0-41-generic-dbgsym arm64 5.15.0-41.44 Err:1 http://ddebs.ubuntu.com jammy-updates/main arm64 linux-image-unsigned-5.15.0-41-generic-dbgsym arm64 5.15.0-41.44 Error reading from server. Remote end closed connection [IP: 185.125.190.18 80] Fetched 17.3 kB in 25min 53s (11 B/s) E: Failed to fetch http://ddebs.ubuntu.com/pool/main/l/linux/linux-image-unsigned-5.15.0-41-generic-dbgsym_5.15.0-41.44_arm64.ddeb Error reading from server. Remote end closed connection [IP: 185.125.190.18 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? autopkgtest [14:56:44]: test live: ---] live FAIL non-zero exit status 100 I assume that re-running the autopkgtest will show that this is no regression in the package. In my opinion verification has succeeded, but due to the autopkgtest failure report I do not dare to change the tags accordingly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1970449 Title: GPG keys are not shown in Software and Updates Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Jammy: Fix Committed Status in software-properties source package in Kinetic: Fix Released Bug description: [Impact] software-properties-gtk does not show the registered apt gpg keys in the "Authentication" tab on my Ubuntu 21.10 and 22.04 systems. [Test Plan] 1. Launch software-properties-gtk 2. Click on the "Authentication" tab 3. At least one key should be listed [Where problems could occur] I fail to come up with possible problems. The failures was a regression and the fixed version has a test case. [Other Infos] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 20:48:04 2022 InstallationDate: Installed on 2022-04-25 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970449/+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 1981645] Re: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Quote from your logs: Processing triggers for initramfs-tools (0.140ubuntu13) ... update-initramfs: Generating /boot/initrd.img-5.15.0-40-generic xz: (stdout): Write error: No space left on device Filesystem 1K-blocks Used Available Use% Mounted on bpool/BOOT/ubuntu_jitbuk394368 275840118528 70% /boot Your /boot partition is far too small. Current recommendation is allocating at least 0.75 GiB, better 1.5 GiB for /boot, not only 0.4 GB as you have on your system. see also Bug #1959971 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1981645 Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Simply running sudo apt upgrade ProblemType: Package DistroRelease: Ubuntu 22.04 Package: initramfs-tools 0.140ubuntu13 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jul 13 16:01:05 2022 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-02-27 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 SourcePackage: initramfs-tools Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1981645/+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 1981154] Re: package linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Filesystem1K-blocks Used Available Use% Mounted on /dev/sdc2721392587824 81104 88% /boot Probably not enough free space on /boot. Suggested solution: purge old kernels. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1981154 Title: package linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: possibly relating to locked boot disk. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jul 7 01:08:28 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-07-06 (368 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1981154/+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 1970449] Re: GPG keys are not shown in Software and Updates
Fact is: software-properties-gtk does not show the registered apt gpg keys in the "Authentication" tab on my Ubuntu 21.10 and 22.04 systems. My Ubuntu 20.04 shows the registered keys in the window. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1970449 Title: GPG keys are not shown in Software and Updates Status in software-properties package in Ubuntu: Confirmed Bug description: Canonical livepatch icon doesn't appear on the title bar. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 20:48:04 2022 InstallationDate: Installed on 2022-04-25 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970449/+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 1970449] Re: GPG keys are not shown in Software and Updates
Due to the fact that the system in question showed two different issues, there is a mix of information related to the two problems. I have tried to clean that up a bit. ** Package changed: ubuntu-release-upgrader (Ubuntu) => software- properties (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1970449 Title: GPG keys are not shown in Software and Updates Status in software-properties package in Ubuntu: Confirmed Bug description: Canonical livepatch icon doesn't appear on the title bar. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 20:48:04 2022 InstallationDate: Installed on 2022-04-25 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970449/+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 1932022] Re: Can you add the btvirt executable to bluez-tests?
** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1932022 Title: Can you add the btvirt executable to bluez-tests? Status in bluez package in Ubuntu: Confirmed Bug description: See the Debian package: https://packages.debian.org/buster/i386/bluez- test-tools/filelist The Ubuntu package contains the same tools, except for btvirt. Would it be possible to add this? The buildlog shows that the btvirt executable is already built, but just not put into the *.deb package. Additions to be done to debian/bluez-tests.install: emulator/b1ee usr/bin emulator/btvirt usr/bin emulator/hfp usr/bin Having the btvirt tool available will make testing on CI systems a lot easier. References: https://github.com/hadess/bluez/blob/master/Makefile.tools#L76-L82 https://answers.launchpad.net/ubuntu/+source/bluez/+question/697542 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1932022/+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 1925745] Re: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies
Re: "I could not find any information what "phased 20%" means." https://wiki.ubuntu.com/StableReleaseUpdates#Phasing https://discourse.ubuntu.com/t/phased-updates-in-apt-in-21-04/20345 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1925745 Title: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: I'm using the ubuntu-21.04-live-server-amd64 ISO to install my hirsute desktop machines so I can automate the installation. After installation, I'm trying to install the desktop via "apt install ubuntu-desktop". This fails with: "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: ubuntu-release-upgrader-gtk : Depends: ubuntu-release-upgrader-core (= 1:21.04.11) but 1:21.04.10 is to be installed Depends: python3-distupgrade (= 1:21.04.11) but 1:21.04.10 is to be installed E: Unable to correct problems, you have held broken packages." "apt policy ubuntu-release-upgrader-core" shows: "ubuntu-release-upgrader-core: Installed: 1:21.04.10 Candidate: 1:21.04.10 Version table: 1:21.04.11 1 (phased 20%) 500 http://at.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages *** 1:21.04.10 500 500 http://at.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status" I could not find any information what "phased 20%" means. It's obviously a major problem not being able to install the desktop on a fresh installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1925745/+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 1913061] Re: systemd-coredump not available for systemd 245.4-4ubuntu3.2
** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1913061 Title: systemd-coredump not available for systemd 245.4-4ubuntu3.2 Status in systemd package in Ubuntu: Invalid Bug description: Hi, I am trying to install systemd-coredump, but it fails with the following error message: 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: systemd-coredump : Depends: systemd (= 245.4-4ubuntu3) E: Unable to correct problems, you have held broken packages. Following discussion on my question i am opening a bug report (link to question: https://answers.launchpad.net/ubuntu/+source/systemd/+question/695171) As far as i understand i have a version of systemd for which no systemd-coredump exists (or is at least not specified). It seems like this wasn't necessary for many users that had an older version of systemd-coredump installed and simply held the older package, but leads to this error if systemd-coredump has not been previously installed. Thanks a lot, Georg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913061/+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 1879206] Re: cups hplip not install printer
Ubuntu 20.04 needs - either the HPLIP version 3.20.3+dfsg0-2 packages from the Ubuntu repositories - or HPLIP version 3.20.5 (or higher) from the HPLIP pages Version 3.20.3 from the HPLIP pages does not work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1879206 Title: cups hplip not install printer Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After upgrading to Ubuntu 20.04 I can't print anymore. Description: Ubuntu 20.04 LTS Release: 20.04 cups: Installato: 2.3.1-9ubuntu1.1 Candidato: 2.3.1-9ubuntu1.1 Tabella versione: *** 2.3.1-9ubuntu1.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages hplip: Installato: 3.20.3+dfsg0-2 Candidato: 3.20.3+dfsg0-2 Tabella versione: *** 3.20.3+dfsg0-2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I tried to reinstall the printer, but it is not being re-saved by cups / hplip ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 02:24:07 2020 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for DeskJet_3630: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658 MachineType: LENOVO 80G0 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DeskJet_3630.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+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 1781428] Re: please enable snap mediation support
Now with the updated snap packages published, (see Bug #1856196 ), when will the pulseaudio packages be re-published? Everyone on Xenial and Bionic who did a package update between 2019-12-11 and 2019-12-12 now has orphaned pulseaudio packages installed, blocking the installation of additional pulseaudio packages! see Bug #1858164 Bug #1858164 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1781428 Title: please enable snap mediation support Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Fix Committed Status in pulseaudio source package in Bionic: Fix Committed Bug description: [Impact] Ubuntu 16.10 added rudimentary snap support to disable audio recording if the connecting process was a snap. By Ubuntu 18.04, something changed in the build resulting in 'Enable Snappy support: no' with audio recording no longer being mediated by pulseaudio (access to the pulseaudio socket continued to be mediated by snapd's apparmor policy). This resulted in any application with the pulseaudio interface connected to be able to also record. Ubuntu 16.04 never had mediation patches and always allowed recording when the pulseaudio interface was connected. To correct this situation but not regress existing behavior, Ubuntu 19.04's pulseaudio was updated patch to allow playback to all connected clients (snaps or not), record by classic snaps (see bug 1787324) and record by strict mode snaps if either the pulseaudio or new-in-snapd-2.41 audio-record interfaces were connected. With this change, snapd is in a position to migrate snaps to the new audio- playback and audio-record interfaces and properly mediate audio recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio- interface-deprecation/13418). The patch to pulseaudio consists of adding a module, enabling it in default.pa and then when it is enabled, pulseaudio when faced with a record operation will, when the connecting process is a snap (ie, its security label (ie, apparmor label) starts with 'snap.'), query snapd via its control socket to ask if the snap is classic and if not, whether the pulseaudio or audio-record interfaces are connected. Adjusting pulseaudio in the manner does not require coordination with any release of snapd. It does need a newer version of snapd-glib, which was recently updated to 1.49 in the last SRU. [Test Case] IMPORTANT: if updating pulseaudio while the session is running, either need to reboot for the test or kill pulseaudio so it can restart with the new snap policy For unconfined applications: $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes For confined, non-snap applications: $ sudo apt-get install evince $ aa-exec -p /usr/bin/evince -- paplay /usr/share/sounds/alsa/Noise.wav && echo yes $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes" yes For classic snaps: $ sudo snap install test-snapd-classic-confinement --classic $ snap run --shell test-snapd-classic-confinement $ cat /proc/self/attr/current # verify we are classic confined snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain) $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes" yes $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes" # ctrl-c to stop recording ^Cyes $ paplay /tmp/out.wav && echo "yes" yes $ exit # out of snap run --shell For strict snaps with pulseaudio: $ sudo snap install test-snapd-pulseaudio --edge $ snap connections test-snapd-pulseaudio Interface Plug Slot Notes pulseaudio test-snapd-pulseaudio:pulseaudio :pulseaudio - $ test-snapd-pulseaudio.play --help # ensure SNAP dirs are created ... $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd- pulseaudio/common/ $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav && echo yes xcb_connection_has_error() returned true yes (note, the xcb_connection_has_error() message is due to the x11 interface not being connecting which is unrelated to mediation. x11 is left out to ensure that just audio-playback/audio-record are tested) $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass ... ^Cyes $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes ... yes For strict snaps with audio-playback/audio-record: $ sudo snap refresh core --candidate # make sure have 2.41. 'install' on 16.04 $ sudo snap install test-snapd-audio-record --edge $
[Touch-packages] [Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd
Sebastien Bacher (seb128)wrote on 2019-12-12: #5 The Xenial/Bionic SRUs have been removed until the Recommends on snapd gets lowered to a Suggest And when will they be re-published? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd Status in pulseaudio package in Ubuntu: Won't Fix Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+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 1844518] Re: Ubuntu 19:10 - Python 3 os.path.isfile not working as expected
In my opinion this bug can be set to invalid. In the linked question #684013 it became evident, that (for whatever reason) /vmlinuz was a dangling symlink pointing to a non-existing kernel version. So python's output islink:true and isfile:false is fully correct. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1844518 Title: Ubuntu 19:10 - Python 3 os.path.isfile not working as expected Status in python3-defaults package in Ubuntu: Incomplete Bug description: When one runs "os.path.isfile("/vmlinuz")" or the same for os.path.exists, False is returned. However, given the information at: https://docs.python.org/3.8/library/os.path.html#os.path.isfile and https://docs.python.org/3.7/library/os.path.html#os.path.isfile, True should be returned for links as well. "os.path.islink("/vmlinuz")" works as expected, so I'm not sure what's going on here. Any ideas? It could be my VM as it's been running 19.10 for a little while now. Hamish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1844518/+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 1607845] Re: List of versioned kernels is not right for Ubuntu
What about packages like linux-modules-extra-3.13.0-168-generic Two versions ago (starting with 3.13.0-166) the former linux-image- extra-* packages have been renamed to linux-modules-extra-* I do not see any provision for these in /etc/apt/apt.conf.d/01autoremove and 01autoremove-kernels on my trusty system (apt 1.0.1ubuntu2.23), and indeed "apt autoremove" deleted the linux-image-extra package belonging to the "running kernel minus one" kernel version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1607845 Title: List of versioned kernels is not right for Ubuntu Status in apt package in Ubuntu: In Progress Bug description: The following command outputs the list: $ apt-config dump --no-empty --format '%v%n' 'APT::VersionedKernelPackages' linux-image linux-headers linux-image-extra linux-signed-image kfreebsd-image kfreebsd-headers gnumach-image .*-modules .*-kernel linux-backports-modules-.* linux-tools but the list does not 'contain linux-.*-tools' and 'linux-goldfish- headers', which are versioned kernel packages as well, if I have understood correctly. On the other hand are these values appropriate for Ubuntu? kfreebsd-image kfreebsd-headers gnumach-image .*-modules .*-kernel Same thing for Ubuntu 14.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jul 29 18:55:50 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-21 (250 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: apt UpgradeStatus: Upgraded to xenial on 2016-06-24 (35 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1607845/+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 1818902] Re: The io.elementary.camera package installs on Ubuntu Disk 19.04 normally, but does not open the video image.
Not related to camera-app (Ubuntu) but io.elementary.camera from the elementary OS PPA. ** Changed in: camera-app (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1818902 Title: The io.elementary.camera package installs on Ubuntu Disk 19.04 normally, but does not open the video image. Status in camera-app package in Ubuntu: Invalid Bug description: Hello guys I installed the io.elementary.camera package from Elementary OS on Ubuntu Disk 19.04 normally, but message appears that it does not recognize the webcam. Note I have the Juno Elementary OS installed on the same machine and the Webcam works normally. I installed through the repository: sudo add-apt-repository ppa: elementary-os / daily sudo apt update sudo apt install io.elementary.camera In the description, there is the option pantheon-camera, but this one says to be with broken package and does not install. Could it be this that does not let the webcam work? Look! sudo apt install pantheon-camera [sudo] password for edson: Reading package lists ... Ready Building dependency tree Reading status information ... Ready Some packages could not be installed. This may mean that you asked for an impossible situation or, if you are using the unstable distribution, that some required packages have not been created yet or have been removed from Incoming. The following information may help resolve the situation: The following packages have mismatched dependencies: pantheon-camera: Depends: io.elementary.camera but will not install E: Impossible to fix problems, you kept (hold) broken packages. Note When I enter synaptcis there is no broken package. If you uninstall io.elementary.camera and try to install the pantheon- camera the same broken package information appears. The installation of io.elementary.camera is performed successfully on Ubuntu 19.04 Disk, but does not appear the image of the video and nor does it recognize the webcam, video attachments. When you try to open the camera through the terminal the following error message appears: edson @ edson-p6540br: ~ $ io.elementary.camera (io.elementary.camera:10218): Clutter-WARNING **: 16: 43: 29.698: Whoever translated default: LTR did so wrongly. (io.elementary.camera:10218): Clutter-Gst-CRITICAL **: 16: 43: 29.753: Unable to setup device without element factory, node and name set 0x55a19aa51200 0x7fc2ec00e240 (nil) edson @ edson-p6540br: ~ $ I ask you to forward the responsible team so that the correction can be carried out. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1818902/+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 1817557] Re: python3-software-properties broken
resolved by reinstalling packages. ** Changed in: software-properties (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1817557 Title: python3-software-properties broken Status in software-properties package in Ubuntu: Invalid Bug description: I'm getting the following error when I try add an ppa. NAME="Ubuntu" VERSION="18.04.2 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.2 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic mmattox@a1ubthorp01:~$ sudo add-apt-repository ppa:nilarimogard/webupd8 Traceback (most recent call last): File "/usr/bin/add-apt-repository", line 11, in from softwareproperties.SoftwareProperties import SoftwareProperties, shortcut_handler File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 64, in from . import shortcuts File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line 23, in _DEF_CODENAME = aptsources.distro.get_distro().codename File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 576, in get_distro os_release = _OSRelease() File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 525, in __init__ self.parse() File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 547, in parse self.parse_entry(*line.split('=', 1)) TypeError: parse_entry() missing 1 required positional argument: 'value' mmattox@a1ubthorp01:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1817557/+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 1808610] Re: chamelon
The contents of the message look like the search output for a certain apk file provided by virustotal: https://www.virustotal.com/#/file/76e27c4b09f9c1cbbf0b414719b741d3087fc744f6de9431a282fbd976bd445a/detection I cannot see a relationship to iputils in Ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1808610 Title: chamelon Status in iputils package in Ubuntu: Incomplete Bug description: Search or scan a URL, IP address, domain, or file hash Sign in 1 / 61 One engine detected this file SHA-25676e27c4b09f9c1cbbf0b414719b741d3087fc744f6de9431a282fbd976bd445a File namemssoJ77AHDuALWGu6G File size11.78 MB Last analysis2018-03-28 08:17:09 UTC Detection Details Relations Behavior Community VirusTotal Droidy Detailed report Network Communication HTTP Requests http://api.exc.mob.com:80/errconf http://api.share.mob.com:80/conn http://api.share.mob.com:80/snsconf https://static.yuanbaopu.com/hotcode/fidewd/ http://api.share.mob.com:80/conf4 http://api.share.mob.com:80/data2 http://api.share.mob.com:80/date http://loc.map.baidu.com/offline_loc http://loc.map.baidu.com/sdk.php http://loc.map.baidu.com/statloc DNS Resolutions loc.map.baidu.com 180.97.104.187 cdn.polyfill.io 151.101.122.109 dualstack.f3.shared.global.fastly.net 151.101.122.109 api.share.mob.com newloc.map.n.shifen.com api.exc.mob.com static.yuanbaopu.com IP Traffic 61.174.10.208:80 (TCP) 120.132.176.173:80 (TCP) 151.101.122.109:443 (TCP) 182.254.154.23:443 (TCP) 180.97.104.187:80 (TCP) File System Actions Files Opened /data/data/com.yuanbaopu.ybpmark/shared_prefs/chcp_plugin_config_pref.xml /data/misc/keychain/pins /storage/emulated/0/ShareSDK/com.yuanbaopu.ybpmark/cache/com.yuanbaopu.ybpmark/.lock /storage/emulated/0/baidu/.cuid /proc/net/if_inet6 /sys/class/net/ip6tnl0/ifindex /sys/class/net/lo/ifindex /sys/class/net/sit0/ifindex /sys/class/net/eth0/ifindex /storage/emulated/0/ShareSDK/.dk Files Written /storage/emulated/0/baidu/tempdata/ls.db /data/data/com.yuanbaopu.ybpmark/files/ofld/ofl_location.db /data/data/com.yuanbaopu.ybpmark/files/ofld/ofl_statistics.db /storage/emulated/0/test.0 /data/data/com.yuanbaopu.ybpmark/files/ofld/ofl.config /storage/emulated/0/baidu/tempdata/ller.dat /storage/emulated/0/baidu/tempdata/conlts.dat /storage/emulated/0/baidu/tempdata/grtcf.dat Files Deleted /data/data/com.yuanbaopu.ybpmark/shared_prefs/chcp_plugin_config_pref.xml.bak /data/data/com.yuanbaopu.ybpmark/shared_prefs/chcp_plugin_config_pref.xml /data/data/com.yuanbaopu.ybpmark/shared_prefs/share_sdk_1.xml.bak /data/data/com.yuanbaopu.ybpmark/shared_prefs/share_sdk_1.xml /storage/emulated/0/test.0 Files Copied /data/data/com.yuanbaopu.ybpmark/shared_prefs/chcp_plugin_config_pref.xml /data/data/com.yuanbaopu.ybpmark/shared_prefs/share_sdk_1.xml Files Dropped 36ac59e578357746f7ab39a543f47e84260ca584534b3bbf3371bc1f4b407fd9 Process And Service Actions Permissions Checked android.permission.READ_PHONE_STATE android.permission.ACCESS_WIFI_STATE android.permission.CHANGE_WIFI_STATE android.permission.GET_TASKS Shell Commands su Services Opened com.google.android.gms.games.service.GamesIntentService (com.google.android.gms) com.google.android.gms.people.service.bg.PeopleBackgroundTasks (com.google.android.gms) Activities Started com.yuanbaopu.ybpmark.MainActivity (com.yuanbaopu.ybpmark) Synchronization Mechanisms & Signals Signals Hooked android.intent.action.PROXY_CHANGE android.intent.action.CONFIGURATION_CHANGED android.intent.action.PHONE_STATE android.intent.action.PACKAGE_ADDED android.intent.action.PACKAGE_REMOVED android.net.wifi.SCAN_RESULTS Modules Loaded Runtime Modules neh locSDK6a Invoked Methods android.os.SystemProperties.addChangeCallback android.os.SystemProperties.getLong com.fasterxml.jackson.databind.MapperFeature.values com.fasterxml.jackson.databind.DeserializationFeature.values com.fasterxml.jackson.databind.SerializationFeature.values com.android.org.conscrypt.OpenSSLCipher$Padding.values com.android.org.conscrypt.OpenSSLCipher$Mode.values android.net.wifi.SupplicantState.values android.net.wifi.WifiSsid.createFromAsciiEncoded com.nordnetab.chcp.main.model.ChcpError.values Highlighted Actions Calls Highlighted android.net.wifi.WifiInfo.getBSSID android.net.wifi.WifiInfo.getMacAddress android.net.wifi.WifiInfo.getSSID android.os.Debug.isDebuggerConnected android.telephony.TelephonyManager.getCellLocation android.telephony.TelephonyManager.getDeviceId android.telephony.TelephonyManager.getNetworkCountryIso android.telephony.TelephonyManager.getSimOperator android.telephony.TelephonyManager.getSubscriberId android.util.Base64.encode Cryptogr
[Touch-packages] [Bug 1792370] Re: Broken links to libmircookie packages
What do you get when changing each occurrence of 'cookie' into 'c%6f%6fkie' in the url? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1792370 Title: Broken links to libmircookie packages Status in mir package in Ubuntu: Invalid Bug description: Can't install libmircookie via apt or dawnload from https://packages.ubuntu.com/xenial/libmircookie-dev. Every link to libmircookie package at http://security.ubuntu.com/ubuntu/pool/main/m/mir/ seems to be broken. Its wrong filename at server: libmircoieok instead libmircookie. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1792370/+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 1644643] Re: apt failed to run due to link time reference error
The root cause of this problem is Zentyal who provide an updated version of libapt-pkg5.0 in their repositories (version 1.5.1), but no updated version of the apt package (which will be taken from the Ubuntu repositories, currently version 1.2.29). These two packages do not fit together. Workaround: downgrade libapt-pkg5.0 to the Ubuntu version (and mark that package not to be updated to the Zentyal version again) Long term solution proposal: Zentyal have to reassess and correct the contents of their repositories. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1644643 Title: apt failed to run due to link time reference error Status in apt package in Ubuntu: Incomplete Bug description: After update apt and its related library to 1.2.15 from 1.2.10ubuntu1, I get following message when I try to invoke apt: apt-get: relocation error: /usr/lib/x86_64-linux-gnu/libapt- private.so.0.0: symbol _ZlsRSoRKN3APT9PrettyPkgE, version APTPKG_5.0 not defined in file libapt-pkg.so.5.0 with link time reference 1.2.10 do not have this problem. Now I manually downgrade from 1.2.15 to 1.2.10 to solve this problem. Ubuntu release: Description: Ubuntu 16.04.1 LTS Release: 16.04 what I expect to happen: apt would show the helper message what happened instead: apt shows me the line on above To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1644643/+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 1767322] Re: "Activation of network connection failed" popup shows incessantly
I had the same problem and just found out that it was caused by a USB network interface that probably has been added when I plugged in a USB network device some time ago. The device has not been connected for months, yet apparently it's active in network manager, trying to get DHCP leases, which of course will fail. Removing the USB connection profile from network manager solved the problem for me. Sylog output example before removing connection profile: Aug 31 07:59:43 p4t-nb-199 dhclient[31345]: DHCPDISCOVER on enp0s20f0u3c2 to 255.255.255.255 port 67 interval 5 (xid=0x5dc07171) Aug 31 07:59:48 p4t-nb-199 dhclient[31345]: DHCPDISCOVER on enp0s20f0u3c2 to 255.255.255.255 port 67 interval 13 (xid=0x5dc07171) Aug 31 08:00:01 p4t-nb-199 dhclient[31345]: DHCPDISCOVER on enp0s20f0u3c2 to 255.255.255.255 port 67 interval 16 (xid=0x5dc07171) Aug 31 08:00:17 p4t-nb-199 dhclient[31345]: DHCPDISCOVER on enp0s20f0u3c2 to 255.255.255.255 port 67 interval 13 (xid=0x5dc07171) Aug 31 08:00:24 p4t-nb-199 NetworkManager[1026]: [1535695224.9894] dhcp4 (enp0s20f0u3c2): request timed out Aug 31 08:00:24 p4t-nb-199 NetworkManager[1026]: [1535695224.9895] dhcp4 (enp0s20f0u3c2): state changed unknown -> timeout Aug 31 08:00:25 p4t-nb-199 NetworkManager[1026]: [1535695225.0064] dhcp4 (enp0s20f0u3c2): canceled DHCP transaction, DHCP client pid 31345 Aug 31 08:00:25 p4t-nb-199 NetworkManager[1026]: [1535695225.0066] dhcp4 (enp0s20f0u3c2): state changed timeout -> done Aug 31 08:00:25 p4t-nb-199 NetworkManager[1026]: [1535695225.0083] device (enp0s20f0u3c2): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed') Aug 31 08:00:25 p4t-nb-199 NetworkManager[1026]: [1535695225.0122] device (enp0s20f0u3c2): Activation: failed for connection 'Wired connection 1' Aug 31 08:00:25 p4t-nb-199 NetworkManager[1026]: [1535695225.0160] device (enp0s20f0u3c2): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Aug 31 08:00:25 p4t-nb-199 avahi-daemon[1009]: Withdrawing address record for fe80::dc1a:366d:4591:9ef8 on enp0s20f0u3c2. Aug 31 08:00:25 p4t-nb-199 avahi-daemon[1009]: Leaving mDNS multicast group on interface enp0s20f0u3c2.IPv6 with address fe80::dc1a:366d:4591:9ef8. Aug 31 08:00:25 p4t-nb-199 systemd-timesyncd[793]: Network configuration changed, trying to establish connection. Aug 31 08:00:25 p4t-nb-199 avahi-daemon[1009]: Interface enp0s20f0u3c2.IPv6 no longer relevant for mDNS. Aug 31 08:00:25 p4t-nb-199 NetworkManager[1026]: [1535695225.0415] policy: auto-activating connection 'Wired connection 1' Aug 31 08:00:25 p4t-nb-199 NetworkManager[1026]: [1535695225.0441] device (enp0s20f0u3c2): Activation: starting connection 'Wired connection 1' (469a98cb-89f1-384c-bae1-f72617a41bff) Aug 31 08:00:25 p4t-nb-199 NetworkManager[1026]: [1535695225.0446] device (enp0s20f0u3c2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Aug 31 08:00:25 p4t-nb-199 NetworkManager[1026]: [1535695225.0457] device (enp0s20f0u3c2): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Aug 31 08:00:25 p4t-nb-199 NetworkManager[1026]: [1535695225.0470] device (enp0s20f0u3c2): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Aug 31 08:00:25 p4t-nb-199 NetworkManager[1026]: [1535695225.0475] dhcp4 (enp0s20f0u3c2): activation: beginning transaction (timeout in 45 seconds) Aug 31 08:00:25 p4t-nb-199 systemd-timesyncd[793]: Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com). Aug 31 08:00:25 p4t-nb-199 NetworkManager[1026]: [1535695225.0532] dhcp4 (enp0s20f0u3c2): dhclient started with pid 31373 Aug 31 08:00:25 p4t-nb-199 dhclient[31373]: DHCPDISCOVER on enp0s20f0u3c2 to 255.255.255.255 port 67 interval 3 (xid=0x3463f46) Aug 31 08:00:26 p4t-nb-199 avahi-daemon[1009]: Joining mDNS multicast group on interface enp0s20f0u3c2.IPv6 with address fe80::dc1a:366d:4591:9ef8. Aug 31 08:00:26 p4t-nb-199 avahi-daemon[1009]: New relevant interface enp0s20f0u3c2.IPv6 for mDNS. Aug 31 08:00:26 p4t-nb-199 systemd-networkd[794]: enp0s20f0u3c2: Gained IPv6LL Aug 31 08:00:26 p4t-nb-199 avahi-daemon[1009]: Registering new address record for fe80::dc1a:366d:4591:9ef8 on enp0s20f0u3c2.*. Aug 31 08:00:26 p4t-nb-199 systemd-timesyncd[793]: Network configuration changed, trying to establish connection. Aug 31 08:00:26 p4t-nb-199 systemd-timesyncd[793]: Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1767322 Title: "Activation of network connection failed" popup shows incessantly Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: All network connections work normally, however the popup "Activation of n
[Touch-packages] [Bug 1773484] Re: Login screen not moved to used monitor
"Beamer" is another display device connected to VGA connector. The behavior on Ubuntu 16.04 was perfect. a) the system menu was visible on each screen b) the login dialog follows the mouse c) configurations were automatically detected (i guess depending on device ids). and former configurations restored. d) if no configuration available screens were automatically mirrored (not sure if I remember correct) That behavior is also desired for Ubuntu 18.04 The current behavior: .. Connected ... Internal LCD ... VGA...GOOD? - First time ... Monitor on VGA .. L+S E ... No -> 1) After Login .. Monitor on VGA .. S .. E ... No -> 2) After reconfiguration Monitor on VGA .. Off S ... Yes After Restart Monitor on VGA .. L+S E ... No -> 1) After Login .. Monitor on VGA .. Off S ... Yes -> 3) -> 1) Login Dialog not following mouse. Without internal LCD no login possible. -> 2) Screen on VGA monitor is empty -> 3) After Login former monitor configuration automatically detected and restored. As soon as I can connect another VGA monitor I will describe the behavior again (at the moment not available). -- 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/1773484 Title: Login screen not moved to used monitor Status in xorg package in Ubuntu: Incomplete Bug description: On Ubuntu 16.04 the login screen and system menu bar, ... is moved to the monitor where the mouse pointer is located. On Ubuntu 18.04 login dialog and system menues are restricted to the main monitor. So if you have a notebook with defect lcd display you can work with it using Ubuntu 16.04 and an external monitor, but you cannot work with Ubuntu 18.04, because you are not able to login! This problem was also asked on: https://askubuntu.com/questions/1031808/problem-with-login-screen-with-dual-monitor-on-ubuntu-18-04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 26 07:04:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2018-04-30 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20AQ007TGE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=28805c99-e27d-49f9-a2e5-17f85980a6d6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET77WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ007TGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQ007TGE:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TGE:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AQ007TGE dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773484/+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.launchp
[Touch-packages] [Bug 1773484] Re: Login screen not moved to used monitor
Formatted table again, is there any way to edit a posted entry or to format (markdown, ..)? .. Connected ... Internal LCD ... VGA -- First time ... Monitor on VGA .. L+S E After Login .. Monitor on VGA .. S .. E After reconfiguration Monitor on VGA .. Off S After Restart Monitor on VGA .. Off L+S After Login .. Monitor on VGA .. Off S Restart with Beamer .. Beamer on VGA .. L+S E Restart with Monitor . Monitor on VGA .. L+S E After Login .. Monitor on VGA .. Off S -- 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/1773484 Title: Login screen not moved to used monitor Status in xorg package in Ubuntu: Incomplete Bug description: On Ubuntu 16.04 the login screen and system menu bar, ... is moved to the monitor where the mouse pointer is located. On Ubuntu 18.04 login dialog and system menues are restricted to the main monitor. So if you have a notebook with defect lcd display you can work with it using Ubuntu 16.04 and an external monitor, but you cannot work with Ubuntu 18.04, because you are not able to login! This problem was also asked on: https://askubuntu.com/questions/1031808/problem-with-login-screen-with-dual-monitor-on-ubuntu-18-04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 26 07:04:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2018-04-30 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20AQ007TGE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=28805c99-e27d-49f9-a2e5-17f85980a6d6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET77WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ007TGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQ007TGE:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TGE:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AQ007TGE dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773484/+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 1773484] Re: Login screen not moved to used monitor
I hope this table is correct. I will verify it as soon as possible (when I have a beamer). Reconfiguration is done with GUI Display dialog (to LCD off and VGA as active display). L+S ... Login/System bar E ... Empty screen Off ... Screen off S ... Normal working screen with system bar ... ConnectedInternal LCD VGA -- First time Monitor on VGA L+SE After Login Monitor on VGA S E After reconfigurationMonitor on VGA OffS After RestartMonitor on VGA OffL+S After Login Monitor on VGA OffS Restart with Beamer Beamer on VGAL+SE Restart with Monitor Monitor on VGA L+SE After Login Monitor on VGA OffS -- 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/1773484 Title: Login screen not moved to used monitor Status in xorg package in Ubuntu: Incomplete Bug description: On Ubuntu 16.04 the login screen and system menu bar, ... is moved to the monitor where the mouse pointer is located. On Ubuntu 18.04 login dialog and system menues are restricted to the main monitor. So if you have a notebook with defect lcd display you can work with it using Ubuntu 16.04 and an external monitor, but you cannot work with Ubuntu 18.04, because you are not able to login! This problem was also asked on: https://askubuntu.com/questions/1031808/problem-with-login-screen-with-dual-monitor-on-ubuntu-18-04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 26 07:04:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2018-04-30 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20AQ007TGE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=28805c99-e27d-49f9-a2e5-17f85980a6d6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET77WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ007TGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQ007TGE:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TGE:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AQ007TGE dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773484/+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 1773484] Re: Login screen not moved to used monitor
Screenshot of internal LCD and external VGA in mirror configuration in attachment. ** Attachment added: "screenshot_lcdAndvga_mirrored.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773484/+attachment/5145283/+files/screenshot_lcdAndvga_mirrored.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/1773484 Title: Login screen not moved to used monitor Status in xorg package in Ubuntu: Incomplete Bug description: On Ubuntu 16.04 the login screen and system menu bar, ... is moved to the monitor where the mouse pointer is located. On Ubuntu 18.04 login dialog and system menues are restricted to the main monitor. So if you have a notebook with defect lcd display you can work with it using Ubuntu 16.04 and an external monitor, but you cannot work with Ubuntu 18.04, because you are not able to login! This problem was also asked on: https://askubuntu.com/questions/1031808/problem-with-login-screen-with-dual-monitor-on-ubuntu-18-04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 26 07:04:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2018-04-30 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20AQ007TGE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=28805c99-e27d-49f9-a2e5-17f85980a6d6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET77WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ007TGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQ007TGE:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TGE:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AQ007TGE dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773484/+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 1773484] Re: Login screen not moved to used monitor
The issue of the Bug description is the most important, because it will affect most of users. This issue has no link to the i-tec adapter issue, it is also visible when the adapter is not connected. I remember that the situation now (on Ubuntu 18.04) is compareable with the situation on Ubuntu 12.04 (maybe also 14.04). In 16.04 this issue was solved in a perfect way (system menues and login dialog follows the mouse pointer to the desired display). -- 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/1773484 Title: Login screen not moved to used monitor Status in xorg package in Ubuntu: Incomplete Bug description: On Ubuntu 16.04 the login screen and system menu bar, ... is moved to the monitor where the mouse pointer is located. On Ubuntu 18.04 login dialog and system menues are restricted to the main monitor. So if you have a notebook with defect lcd display you can work with it using Ubuntu 16.04 and an external monitor, but you cannot work with Ubuntu 18.04, because you are not able to login! This problem was also asked on: https://askubuntu.com/questions/1031808/problem-with-login-screen-with-dual-monitor-on-ubuntu-18-04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 26 07:04:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2018-04-30 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20AQ007TGE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=28805c99-e27d-49f9-a2e5-17f85980a6d6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET77WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ007TGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQ007TGE:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TGE:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AQ007TGE dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773484/+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 1773484] Re: Login screen not moved to used monitor
Question 1) Monitor is plugged in on standard VGA connector (15 pin D-Sub). I guess it does not matter which monitor type. I have done it with a Ilyama ProLite G2773HS and a Samsung Syncmaster S24B350 monitor. As soon as the monitors are configured, for example the external monitor as replacement for the built in LCD-display of a notebook, the system detects this configuration next time automatically and is switching to the proper monitor configuration, also for the login-screen. This behavior is fine, but does not help the first time, when no configuration was done (or it falls back to the starting situation). Question 2) I am using the P/N: U3DUALADA (barcode D16-00352296). Question 3) As HDMI monitor I am using the Samsung Syncmaster S24B35 Question 4) Using the i-tec adapter for the additional Samsung Syncmaster S24B350 monitor was working without any problems on Ubuntu 16.04. On Ubuntu 18.04 monitor configuration is not automatically detected. As work-arround I open the configuration->devices->displays dialog. If this dialog is open and I reconnect the i-tec adapter, the system offers now configuration possibilities. This must be done every time the adpater is connected to the system. A second minor problem when using this adapter is a mouse flickering effect. When mouse icon changes, it mouse icon disappears completely for a short time. When disconnecting the adapter system finds back to the default monitor situation without problems. -- 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/1773484 Title: Login screen not moved to used monitor Status in xorg package in Ubuntu: Incomplete Bug description: On Ubuntu 16.04 the login screen and system menu bar, ... is moved to the monitor where the mouse pointer is located. On Ubuntu 18.04 login dialog and system menues are restricted to the main monitor. So if you have a notebook with defect lcd display you can work with it using Ubuntu 16.04 and an external monitor, but you cannot work with Ubuntu 18.04, because you are not able to login! This problem was also asked on: https://askubuntu.com/questions/1031808/problem-with-login-screen-with-dual-monitor-on-ubuntu-18-04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 26 07:04:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2018-04-30 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20AQ007TGE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=28805c99-e27d-49f9-a2e5-17f85980a6d6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET77WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ007TGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQ007TGE:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TGE:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AQ007TGE dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages
[Touch-packages] [Bug 1773484] [NEW] Login screen not moved to used monitor
Public bug reported: On Ubuntu 16.04 the login screen and system menu bar, ... is moved to the monitor where the mouse pointer is located. On Ubuntu 18.04 login dialog and system menues are restricted to the main monitor. So if you have a notebook with defect lcd display you can work with it using Ubuntu 16.04 and an external monitor, but you cannot work with Ubuntu 18.04, because you are not able to login! This problem was also asked on: https://askubuntu.com/questions/1031808/problem-with-login-screen-with-dual-monitor-on-ubuntu-18-04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 26 07:04:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2018-04-30 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20AQ007TGE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=28805c99-e27d-49f9-a2e5-17f85980a6d6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET77WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ007TGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQ007TGE:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TGE:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AQ007TGE dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- 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/1773484 Title: Login screen not moved to used monitor Status in xorg package in Ubuntu: New Bug description: On Ubuntu 16.04 the login screen and system menu bar, ... is moved to the monitor where the mouse pointer is located. On Ubuntu 18.04 login dialog and system menues are restricted to the main monitor. So if you have a notebook with defect lcd display you can work with it using Ubuntu 16.04 and an external monitor, but you cannot work with Ubuntu 18.04, because you are not able to login! This problem was also asked on: https://askubuntu.com/questions/1031808/problem-with-login-screen-with-dual-monitor-on-ubuntu-18-04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 26 07:04:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2018-04-30 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20AQ007TGE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=28805c99-e27d-49f9-a2e5-17f8
[Touch-packages] [Bug 1721626] Re: Remove obsolete versioned dependency on initramfs-tools Edit
Are you aware that ubiquity-2.21.63.5 in xenial-updates already depends on console-setup 1.108ubuntu15.4 which is only in xenial-proposed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1721626 Title: Remove obsolete versioned dependency on initramfs-tools Edit Status in console-setup package in Ubuntu: Fix Released Status in console-setup source package in Xenial: Fix Committed Bug description: [SRU Justification] Up until artful, console-setup declares a versioned dependency on initramfs-tools. This was an Ubuntu-specific dependency only needed for upgrades, and the version referenced is ancient (ca. 2008). In artful and later, the dependency has now been removed. Since this is no longer relevant for upgrades and we would not otherwise have a dependency on initramfs-tools, we should drop this dependency to support building of images with initramfs-tools removed for systems that we know don't require an initramfs. [Test case] 1. On a xenial default cloud image install, try to run 'sudo apt purge initramfs-tools'. 2. Verify that this tries to remove console-setup, console-setup-linux, and kbd. 3. Cancel the removal. 4. Install console-setup from xenial-proposed. 5. Run 'sudo apt purge initramfs-tools' again. 6. Verify that console-setup, console-setup-linux, and kbd are not removed. 7. Run 'sudo apt install --reinstall console-setup' and confirm that the package can be installed successfully without initramfs-tools installed. [Regression Potential] If a user needs an initramfs in order to mount their root device, and console-setup is the only package on their system which depends on initramfs-tools, it is possible that the user may remove initramfs-tools and render their system unbootable. This is unlikely because initramfs-tools is still part of the 'minimal' seed and is therefore a dependency of ubuntu-minimal; and it remains a dependency of the generic kernel image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1721626/+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 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c
@Karl Schindler: What you see is probably a bug in Eclipse, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=479646 Something that eclipse has to work on. ** Bug watch added: Eclipse bugs #479646 https://bugs.eclipse.org/bugs/show_bug.cgi?id=479646 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to consolekit in Ubuntu. https://bugs.launchpad.net/bugs/1264368 Title: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c Status in AndroidSDK: New Status in Banshee: New Status in gnome-control-center: Incomplete Status in GParted: Unknown Status in notification-daemon: New Status in anjuta package in Ubuntu: Confirmed Status in consolekit package in Ubuntu: Confirmed Status in f-spot package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Status in putty package in Ubuntu: Confirmed Bug description: Steps to recreate: 1. Open gnome-control-center in terminal. 2. Go to Network. 3. Go back to All preferences. 4. Notice that in terminal there is a warning: $ gnome-control-center (gnome-control-center:13519): GLib-CRITICAL **: Source ID 166 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu49 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Dec 26 21:03:52 2013 InstallationDate: Installed on 2013-10-15 (71 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131015) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to trusty on 2013-11-05 (51 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/androidsdk/+bug/1264368/+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 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Wie kann ich als Anfänger den Schaden beheben? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1642966 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Triaged Status in cups source package in Yakkety: Fix Released Status in cups source package in Zesty: Fix Released Bug description: This is in xenial-proposed, please block release to -updates accordingly :) [Impact] * fail to upgrade [testcase] Root cause is believed to be reproducible with: #!/bin/bash systemctl stop cups.path cups.service rm /var/cache/cups/org.cups.cupsd systemctl start cups.path touch /var/cache/cups/org.cups.cupsd sleep 1 rm /var/cache/cups/org.cups.cupsd sleep 1 systemctl stop cups.service echo $? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Fri Nov 18 11:13:15 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-02 (200 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for mallards-officejet-pro-8600: dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461 MachineType: Dell Inc. XPS 15 9550 Papersize: a4 PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+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 1697153] Re: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal
I tried all, all command other tried, but this failure remains ... I am more USER then SW Engineer ... What else can I do? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1697153 Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. Status in libnl3 package in Ubuntu: Incomplete Bug description: linux-libc-dev:amd64 (4.4.0-79.100) wird eingerichtet ... Fehler traten auf beim Bearbeiten von: libnl-genl-3-200:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 AptOrdering: libnl-3-200: Install libnl-3-200: Configure libnl-genl-3-200: Configure libnl-route-3-200: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Jun 10 10:30:10 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 libnl-3-200 3.2.27-1ubuntu0.16.04.1 ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. InstallationDate: Installed on 2016-04-03 (432 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libnl3 Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. UpgradeStatus: Upgraded to xenial on 2016-11-29 (192 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1697153/+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
Re: [Touch-packages] [Bug 1697153] Re: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es noch
What Commands do I need to enter? Later the day it seems that I could install a new kernel. May try it the next two days again, before heading it vacation till end of June ;-) MANFRED Am 12.06.2017 um 18:47 schrieb Joshua Powers : >> From terminal log (translated): > > Dpkg: Error processing package libnl-genl-3-200: amd64 (--configure): > Package is in a very bad inconsistent condition - you should get it > Again before attempting the configuration. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1697153 > > Title: > package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to > install/upgrade: Paket ist in einem sehr schlechten inkonsistenten > Zustand - Sie sollten es nochmal installieren, bevor Sie die > Konfiguration versuchen. > > Status in libnl3 package in Ubuntu: > Incomplete > > Bug description: > linux-libc-dev:amd64 (4.4.0-79.100) wird eingerichtet ... > Fehler traten auf beim Bearbeiten von: > libnl-genl-3-200:amd64 > E: Sub-process /usr/bin/dpkg returned an error code (1) > > ProblemType: Package > DistroRelease: Ubuntu 16.04 > Package: libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 > ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 > Uname: Linux 4.4.0-78-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.6 > AptOrdering: > libnl-3-200: Install > libnl-3-200: Configure > libnl-genl-3-200: Configure > libnl-route-3-200: Configure > NULL: ConfigurePending > Architecture: amd64 > Date: Sat Jun 10 10:30:10 2017 > Dependencies: > gcc-6-base 6.0.1-0ubuntu1 > libc6 2.23-0ubuntu7 > libgcc1 1:6.0.1-0ubuntu1 > libnl-3-200 3.2.27-1ubuntu0.16.04.1 > ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - > Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. > InstallationDate: Installed on 2016-04-03 (432 days ago) > InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) > RelatedPackageVersions: > dpkg 1.18.4ubuntu1.2 > apt 1.2.20 > SourcePackage: libnl3 > Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to > install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - > Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. > UpgradeStatus: Upgraded to xenial on 2016-11-29 (192 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1697153/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1697153 Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. Status in libnl3 package in Ubuntu: Incomplete Bug description: linux-libc-dev:amd64 (4.4.0-79.100) wird eingerichtet ... Fehler traten auf beim Bearbeiten von: libnl-genl-3-200:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 AptOrdering: libnl-3-200: Install libnl-3-200: Configure libnl-genl-3-200: Configure libnl-route-3-200: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Jun 10 10:30:10 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 libnl-3-200 3.2.27-1ubuntu0.16.04.1 ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. InstallationDate: Installed on 2016-04-03 (432 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libnl3 Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. UpgradeStatus: Upgraded to xenial on 2016-11-29 (192 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1697153/+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 1697153] [NEW] package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochma
Public bug reported: linux-libc-dev:amd64 (4.4.0-79.100) wird eingerichtet ... Fehler traten auf beim Bearbeiten von: libnl-genl-3-200:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 AptOrdering: libnl-3-200: Install libnl-3-200: Configure libnl-genl-3-200: Configure libnl-route-3-200: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Jun 10 10:30:10 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 libnl-3-200 3.2.27-1ubuntu0.16.04.1 ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. InstallationDate: Installed on 2016-04-03 (432 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libnl3 Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. UpgradeStatus: Upgraded to xenial on 2016-11-29 (192 days ago) ** Affects: libnl3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1697153 Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. Status in libnl3 package in Ubuntu: New Bug description: linux-libc-dev:amd64 (4.4.0-79.100) wird eingerichtet ... Fehler traten auf beim Bearbeiten von: libnl-genl-3-200:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 AptOrdering: libnl-3-200: Install libnl-3-200: Configure libnl-genl-3-200: Configure libnl-route-3-200: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Jun 10 10:30:10 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 libnl-3-200 3.2.27-1ubuntu0.16.04.1 ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. InstallationDate: Installed on 2016-04-03 (432 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libnl3 Title: package libnl-genl-3-200:amd64 3.2.27-1ubuntu0.16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. UpgradeStatus: Upgraded to xenial on 2016-11-29 (192 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1697153/+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 1660633] Re: /usr/bin/ucfr: line ... : [: : integer expression expected
Meanwhile in https://answers.launchpad.net/ubuntu/+source/ucf/+question/448737 we identified two areas where the ucfr script misbehaved in the environment of the original poster. The following workarounds helped: Change all occurrences of $" into "'$' Change all occurrences of egrep into grep -E Even if we do not know why the ucfr script failed in the original poster's environment, these modifications might be worth being considered for future versions of the ucfr script. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1660633 Title: /usr/bin/ucfr: line ... : [: : integer expression expected Status in ucf package in Ubuntu: Incomplete Bug description: I've had a reoccurring issue: https://ubuntuforums.org/showthread.php?t=2350682 Running: ucf_3.0036_all.deb http://askubuntu.com/questions/875415/usr-bin-ucfr-errors-integer-expression-expected http://serverfault.com/questions/827873/grub-pc-update-fail-dev-sda-ext2-doesnt-support-embedding I don't know why ucfr is erroring out but the accumulated errors are now enough to stall priority packages which I feel hamstrung about. I've reinstalled the ucf package and danced around the issue enough. Any maintainers have a shot in the dark for why this would be happening? Discussion: https://answers.launchpad.net/ubuntu/+source/ucf/+question/448737 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1660633/+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 1660633] Re: /usr/bin/ucfr: line ... : [: : integer expression expected
/var/lib/ucf/registry is present on the system with the problem (see https://answers.launchpad.net/ubuntu/+source/ucf/+question/448737 ) As far as we already found out one of the causes of this error is that the command egrep --count "[[:space:]]/etc/default/grub$" "/var/lib/ucf/registry" returns "Illegal variable name." when executed in a csh or tcsh shell. According to http://www.grymoire.com/unix/CshTop10.txt any use of the string $" in a csh or tcsh fails that way. According to suggestions in the grymoire document, a potential workaround could be changing line 321 of ucfr from count=$(egrep --count "[[:space:]]${real_conf_file_re}$" "$statedir/registry") || true into count=$(egrep --count "[[:space:]]${real_conf_file_re}"'$' "$statedir/registry") || true (instead of 'dollar doublequote' make it 'doublequote quote dollar quote') (Note, I was not in a position that I could test myself whether this works.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1660633 Title: /usr/bin/ucfr: line ... : [: : integer expression expected Status in ucf package in Ubuntu: Incomplete Bug description: I've had a reoccurring issue: https://ubuntuforums.org/showthread.php?t=2350682 Running: ucf_3.0036_all.deb http://askubuntu.com/questions/875415/usr-bin-ucfr-errors-integer-expression-expected http://serverfault.com/questions/827873/grub-pc-update-fail-dev-sda-ext2-doesnt-support-embedding I don't know why ucfr is erroring out but the accumulated errors are now enough to stall priority packages which I feel hamstrung about. I've reinstalled the ucf package and danced around the issue enough. Any maintainers have a shot in the dark for why this would be happening? Discussion: https://answers.launchpad.net/ubuntu/+source/ucf/+question/448737 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1660633/+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 1614299] Re: install failure on python 3.5
As already written in https://answers.launchpad.net/ubuntu/+source /python-apt/+question/285522 python-apt version 0.7.8 is a very old and obsolete version (was for Ubuntu 9.04). For Ubuntu 14.04 the designated version is 0.9.3.5ubuntu2 The message "from DistUtilsExtra.command import * ImportError: No module named 'DistUtilsExtra'" might indicate that the package python-distutils-extra is missing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1614299 Title: install failure on python 3.5 Status in python-apt package in Ubuntu: Confirmed Bug description: Related to expired issue: https://answers.launchpad.net/ubuntu/+source /python-apt/+question/285522 snafu$ cd /tmp snafu$ pyvenv apt snafu$ source apt/bin/activate (apt) snafu$ lsb_release -a; uname -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 Codename: xenial Linux snafu 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux (apt) snafu$ pip install python-apt Collecting python-apt Using cached python-apt-0.7.8.tar.bz2 Complete output from command python setup.py egg_info: Traceback (most recent call last): File "", line 1, in File "/tmp/pip-build-l1pt_xe2/python-apt/setup.py", line 6, in from DistUtilsExtra.command import * ImportError: No module named 'DistUtilsExtra' Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-l1pt_xe2/python-apt/ You are using pip version 8.1.1, however version 8.1.2 is available. You should consider upgrading via the 'pip install --upgrade pip' command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1614299/+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 1625372] Re: NTP security issues on Precise and Trusty
** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-1547 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-1548 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-1550 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-2516 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-2518 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1625372 Title: NTP security issues on Precise and Trusty Status in ntp package in Ubuntu: New Bug description: Based on the changelog, precise and trusty have not received patches for the following CVE issues: CVE-2016-1547 CVE-2016-1548 CVE-2016-1550 CVE-2016-2516 CVE-2016-2518 When will these be fixed on Precise and Trusty? They have been fixed on Debian 7 and 8. Thanks, Bryan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1625372/+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 1596693] Re: OpenSSL 1.0.2 for trusty
>From https://www.openssl.org/policies/releasestrat.html Support for version 1.0.1 will cease on 2016-12-31. No further releases of 1.0.1 will be made after that date. Security fixes only will be applied to 1.0.1 until then. How is Ubuntu going to deal with that? Both Precise and Trusty currently have 1.0.1 versions, and both Ubuntu releases have a target life time beyond that date. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1596693 Title: OpenSSL 1.0.2 for trusty Status in openssl package in Ubuntu: Won't Fix Bug description: ALPN support was introduced in OpenSSL 1.0.2 which myself, and I'm guessing a lot of other people, are going to need, is there any chance OpenSSL 1.0.2 will come to trusty, or can be backported? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1596693/+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 1596831] Re: Ubuntu 12.04_5 LTS and openSSL 1.0.1 EOL
>From https://www.openssl.org/policies/releasestrat.html Support for version 1.0.1 will cease on 2016-12-31. No further releases of 1.0.1 will be made after that date. Security fixes only will be applied to 1.0.1 until then. How is Ubuntu going to deal with that? Both Precise and Trusty currently have 1.0.1 versions, and both Ubuntu releases have a target life time beyond that date. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1596831 Title: Ubuntu 12.04_5 LTS and openSSL 1.0.1 EOL Status in openssl package in Ubuntu: New Bug description: With OpenSSL 1.0.1 EOL in December this year, openSSL needs to be upgraded to version 1.0.2. This affects : Description: Ubuntu 12.04.5 LTS Release: 12.04 Lib: apt-cache policy openssl openssl: Installed: 1.0.1-4ubuntu5.36 Candidate: 1.0.1-4ubuntu5.36 Version table: *** 1.0.1-4ubuntu5.36 0 500 http://nl.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status 1.0.1-4ubuntu3 0 500 http://nl.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1596831/+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 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c
@Dmitry: Are you sure that you always have a valid id when calling g_source_remove(id), and that you call that function for each id only once? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to consolekit in Ubuntu. https://bugs.launchpad.net/bugs/1264368 Title: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c Status in AndroidSDK: New Status in Banshee: New Status in gnome-control-center: Incomplete Status in GParted: Unknown Status in anjuta package in Ubuntu: Confirmed Status in consolekit package in Ubuntu: Confirmed Status in f-spot package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Status in putty package in Ubuntu: Confirmed Bug description: Steps to recreate: 1. Open gnome-control-center in terminal. 2. Go to Network. 3. Go back to All preferences. 4. Notice that in terminal there is a warning: $ gnome-control-center (gnome-control-center:13519): GLib-CRITICAL **: Source ID 166 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu49 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Dec 26 21:03:52 2013 InstallationDate: Installed on 2013-10-15 (71 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131015) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to trusty on 2013-11-05 (51 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/androidsdk/+bug/1264368/+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 1582854] Re: mount -t nfs not working in ubuntu 16.04
After a lot of digging, I found a solution/workaround. The problem is the nfs version, in short: sudo mount -t nfs o nfsvers=2 server:/ does the trick. Anyway, here is what happens without specifying the nfsvers option: sudo mount -t nfs -v server:/ mount.nfs: timeout set for Sat May 21 11:59:43 2016 mount.nfs: trying text-based options 'vers=4,addr=192.168.1.133,clientaddr=192.168.1.25' mount.nfs: mount(2): Stale file handle Version 3 also does not work: sudo mount -t nfs -v o nfsvers=3 server:/ mount.nfs: timeout set for Sat May 21 12:00:12 2016 mount.nfs: trying text-based options 'nfsvers=3,addr=192.168.1.133' mount.nfs: prog 13, trying vers=3, prot=6 mount.nfs: trying 192.168.1.133 prog 13 vers 3 prot TCP port 2049 mount.nfs: prog 15, trying vers=3, prot=17 mount.nfs: trying 192.168.1.133 prog 15 vers 3 prot UDP port 55187 mount.nfs: mount(2): Stale file handle Finally, this does work: sudo mount -t nfs -v o nfsvers=2 server:/ mount.nfs: timeout set for Sat May 21 12:00:33 2016 mount.nfs: trying text-based options 'nfsvers=2,addr=192.168.1.133' mount.nfs: prog 13, trying vers=2, prot=6 mount.nfs: trying 192.168.1.133 prog 13 vers 2 prot TCP port 2049 mount.nfs: prog 15, trying vers=1, prot=17 mount.nfs: trying 192.168.1.133 prog 15 vers 1 prot UDP port 34856 Again, the NFS server runs Ubuntu Desktop 14.04, nfs export is done without any specific options wrt the nfs version. So maybe this is not a bug per se and it is just that the default for the version has changed, but IMHO, a meaningful error message would be *a lot* better than just timing out without any additional information. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1582854 Title: mount -t nfs not working in ubuntu 16.04 Status in util-linux package in Ubuntu: New Bug description: After upgrading from 15.10 to 16.04, the command sudo mount -t nfs Biest:/ /home/manfred/BigDisk/ times out without any further error reporting: mount.nfs: Connection timed out It worked on the same machine before the upgrade, and it still works from both a 14.04 and a 15.10 machine. The file server is running 14.04. Additional info: I just updated today (05/17/2016). Let me know what else you need. Other people seem to have the same or similar problems, but no official bug report, fix, or workaround to be found. Only viable option I have now is to downgrade to 15.10. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: mount 2.27.1-6ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 17 20:57:58 2016 InstallationDate: Installed on 2015-06-27 (325 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: util-linux UpgradeStatus: Upgraded to xenial on 2016-04-30 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1582854/+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 1582854] Re: mount -t nfs not working in ubuntu 16.04
Update: there seems to be a much deeper networking problem, perhaps introduced with kernel update 4.4.0-22. Mounting Windows shares/samba also does not work any more. Neither does network printing. The only things still working are ssh and sftp. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1582854 Title: mount -t nfs not working in ubuntu 16.04 Status in util-linux package in Ubuntu: New Bug description: After upgrading from 15.10 to 16.04, the command sudo mount -t nfs Biest:/ /home/manfred/BigDisk/ times out without any further error reporting: mount.nfs: Connection timed out It worked on the same machine before the upgrade, and it still works from both a 14.04 and a 15.10 machine. The file server is running 14.04. Additional info: I just updated today (05/17/2016). Let me know what else you need. Other people seem to have the same or similar problems, but no official bug report, fix, or workaround to be found. Only viable option I have now is to downgrade to 15.10. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: mount 2.27.1-6ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 17 20:57:58 2016 InstallationDate: Installed on 2015-06-27 (325 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: util-linux UpgradeStatus: Upgraded to xenial on 2016-04-30 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1582854/+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 1582854] [NEW] mount -t nfs not working in ubuntu 16.04
Public bug reported: After upgrading from 15.10 to 16.04, the command sudo mount -t nfs Biest:/ /home/manfred/BigDisk/ times out without any further error reporting: mount.nfs: Connection timed out It worked on the same machine before the upgrade, and it still works from both a 14.04 and a 15.10 machine. The file server is running 14.04. Additional info: I just updated today (05/17/2016). Let me know what else you need. Other people seem to have the same or similar problems, but no official bug report, fix, or workaround to be found. Only viable option I have now is to downgrade to 15.10. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: mount 2.27.1-6ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 17 20:57:58 2016 InstallationDate: Installed on 2015-06-27 (325 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: util-linux UpgradeStatus: Upgraded to xenial on 2016-04-30 (16 days ago) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1582854 Title: mount -t nfs not working in ubuntu 16.04 Status in util-linux package in Ubuntu: New Bug description: After upgrading from 15.10 to 16.04, the command sudo mount -t nfs Biest:/ /home/manfred/BigDisk/ times out without any further error reporting: mount.nfs: Connection timed out It worked on the same machine before the upgrade, and it still works from both a 14.04 and a 15.10 machine. The file server is running 14.04. Additional info: I just updated today (05/17/2016). Let me know what else you need. Other people seem to have the same or similar problems, but no official bug report, fix, or workaround to be found. Only viable option I have now is to downgrade to 15.10. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: mount 2.27.1-6ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 17 20:57:58 2016 InstallationDate: Installed on 2015-06-27 (325 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: util-linux UpgradeStatus: Upgraded to xenial on 2016-04-30 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1582854/+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 1537915] Re: libgtk-3-common: Adwaita theme dependency not recognized
Ok, now the only line shown is the missing dependency on adwaita-icon- theme. As a test for a possible workaround, what is the output of apt-get --simulate --no-install-recommends install libgtk-3-common=3.18.6-1ubuntu1 adwaita-icon-theme -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1537915 Title: libgtk-3-common: Adwaita theme dependency not recognized Status in gtk+3.0 package in Ubuntu: New Bug description: Pre-note: due to severe bugs, I had to go down from 3.19.x back to 3.18.6. I think the following content will speak for itself: user@mybuntubox:~$ sudo apt-get install --reinstall adwaita-icon-theme Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 70 not to upgrade. Need to get 0 B/897 kB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 307199 files and directories currently installed.) Preparing to unpack .../adwaita-icon-theme_3.18.0-2ubuntu1_all.deb ... Unpacking adwaita-icon-theme (3.18.0-2ubuntu1) over (3.18.0-2ubuntu1) ... Setting up adwaita-icon-theme (3.18.0-2ubuntu1) ... +++ OKAY. Adwaita Icon Theme is now installed and expected to be working. Version = __3.18.0-2__ user@mybuntubox~$ sudo apt-get install libgtk-3-common=3.18.6-1ubuntu1 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. libgtk-3-common : Depends: adwaita-icon-theme (>= 3.18) but it is not going to be installed Recommends: libgtk-3-0 but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. There is clearly something wrong. Just for "emphasis", I reinstalled Adwaita icon theme 3.18.x again above, to be sure it is really expected to be there. But it seems to be a bug that libgtk-3-common does not recognize it as there. Plus, --force-depends appears to be unavailable when using the '=' sign for a version-specific downgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1537915/+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 1537915] Re: libgtk-3-common: Adwaita theme dependency not recognized
Just to verify that the dependency problem is caused by adwaita-icon- theme and not by "Recommends: libgtk-3-0" What is the output of sudo apt-get --no-install-recommends install libgtk-3-common=3.18.6-1ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1537915 Title: libgtk-3-common: Adwaita theme dependency not recognized Status in gtk+3.0 package in Ubuntu: New Bug description: Pre-note: due to severe bugs, I had to go down from 3.19.x back to 3.18.6. I think the following content will speak for itself: user@mybuntubox:~$ sudo apt-get install --reinstall adwaita-icon-theme Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 70 not to upgrade. Need to get 0 B/897 kB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 307199 files and directories currently installed.) Preparing to unpack .../adwaita-icon-theme_3.18.0-2ubuntu1_all.deb ... Unpacking adwaita-icon-theme (3.18.0-2ubuntu1) over (3.18.0-2ubuntu1) ... Setting up adwaita-icon-theme (3.18.0-2ubuntu1) ... +++ OKAY. Adwaita Icon Theme is now installed and expected to be working. Version = __3.18.0-2__ user@mybuntubox~$ sudo apt-get install libgtk-3-common=3.18.6-1ubuntu1 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. libgtk-3-common : Depends: adwaita-icon-theme (>= 3.18) but it is not going to be installed Recommends: libgtk-3-0 but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. There is clearly something wrong. Just for "emphasis", I reinstalled Adwaita icon theme 3.18.x again above, to be sure it is really expected to be there. But it seems to be a bug that libgtk-3-common does not recognize it as there. Plus, --force-depends appears to be unavailable when using the '=' sign for a version-specific downgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1537915/+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 1460487] Re: unknown
There was a recent comment from the bug reporter in bug #948053 "i wanna have the nvidia-173 cause i can't have a good resolution whithout" If the display hardware is GraphicsCard: NVIDIA Corporation G72 [GeForce 7500 LE] [10de:01dd] (rev a1) (prog-if 00 [VGA controller]) as shown in this bug report, then the nvidia-graphics- drivers-304-updates package should contain the correct driver. As far as I know there is no working 173 driver available for Ubuntu 12.04.3 and up, but the GeForce 7500 LE hardware should be well supported by the 304 driver. see http://us.download.nvidia.com/XFree86/Linux-x86/304.125/README/supportedchips.html Try installing the package nvidia-304-updates -- 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/1460487 Title: unknown Status in xorg package in Ubuntu: Incomplete Bug description: unknown ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18 Uname: Linux 3.13.0-51-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jun 1 00:24:33 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G72 [GeForce 7500 LE] [10de:01dd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:821b] InstallationDate: Installed on 2014-01-28 (488 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1) MachineType: PACKARD BELL BV IMEDIA F9671 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-51-generic root=UUID=cceff882-7626-412e-ae65-f7af1c46bcc7 ro drm.debug=0xe plymouth:debug Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: W7301VP2.316 dmi.board.name: Cuba MS-7301 dmi.board.vendor: Packard Bell BV dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell BV dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrW7301VP2.316:bd09/28/2007:svnPACKARDBELLBV:pnIMEDIAF9671:pvrPB80103902:rvnPackardBellBV:rnCubaMS-7301:rvr1.0:cvnPackardBellBV:ct3:cvr: dmi.product.name: IMEDIA F9671 dmi.product.version: PB80103902 dmi.sys.vendor: PACKARD BELL BV version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.libdrm2: libdrm2 2.4.61+git1505281830.97be70~gd~t version.libgl1-mesa-dri: libgl1-mesa-dri 10.7~git1505310730.7f62fd~gd~t version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.7~git1505310730.7f62fd~gd~t version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Jun 1 00:18:17 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1460487/+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 1452216] Re: libgcrypt11 not present in Vivid (15.04) - Spotify and other app issue.
@Seth Arnold: Several people have tried creating a link from libgcrypt11 to libgcrypt20 sudo ln -s /lib/x86_64-linux-gnu/libgcrypt.so.20.0.2 /lib/x86_64-linux-gnu/libgcrypt.so.11 respectively sudo ln -s /lib/i386-linux-gnu/libgcrypt.so.20.0.2 /lib/i386-linux-gnu/libgcrypt.so.11 and have received errors like spotify: /lib/x86_64-linux-gnu/libgcrypt.so.11: version `GCRYPT_1.2' not found (required by /opt/spotify/spotify-client/Data/libcef.so) So that seems not to be sufficiently binary compatible. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgcrypt11 in Ubuntu. https://bugs.launchpad.net/bugs/1452216 Title: libgcrypt11 not present in Vivid (15.04) - Spotify and other app issue. Status in libgcrypt11 package in Ubuntu: Confirmed Bug description: The package libgcrypt11 is not present anymore in official ubuntu vivid repositories. This cause app crash, such as spotify: spotify: error while loading shared libraries: libgcrypt.so.11: cannot open shared object file: No such file or directory Current workaround is to manually download the .deb package from launchpad/debian package such as https://packages.debian.org/wheezy/libgcrypt11 and manually install with dpkg. Linux SAGITTER 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu 15.04 Release: 15.04 Codename: vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/1452216/+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 1414333] Re: libcairo-dev depencencies in Utopic
** Changed in: cairo (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1414333 Title: libcairo-dev depencencies in Utopic Status in cairo package in Ubuntu: Confirmed Bug description: My problem in Utopic is: The following packages have unmet dependencies: libcairo2-dev : Depends: libcairo2 (= 1.13.0~20140204-0ubuntu1) but 1.13.0~20140204-0ubuntu1.1 is to be installed Depends: libcairo-gobject2 (= 1.13.0~20140204-0ubuntu1) but 1.13.0~20140204-0ubuntu1.1 is to be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1414333/+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 1414333] Re: libcairo-dev depencencies in Utopic
This is a regression bug caused by the fact that for correction of bug #1391857 a package cairo 1.13.0~20140204-0ubuntu1.1 was created in trusty only but not in utopic. See https://launchpad.net/ubuntu/+source/cairo Steps for duplicating that bug: On a trusty implementation with -updates enabled install libcairo2 from trusty-updates (version 1.13.0~20140204-0ubuntu1.1), but not libcariro2-dev. Upgrade from trusty to utopic Try installing libcariro2-dev This fails with The following packages have unmet dependencies: libcairo2-dev : Depends: libcairo2 (= 1.13.0~20140204-0ubuntu1) but 1.13.0~20140204-0ubuntu1.1 is to be installed Depends: libcairo-gobject2 (= 1.13.0~20140204-0ubuntu1) but 1.13.0~20140204-0ubuntu1.1 is to be installed E: Unable to correct problems, you have held broken packages. Proposals for solution: copy the trusty package to utopic or backport the 1.14 version from vivid to utopic. This problem has gained importance, because the ...ubuntu1.1 version has meanwhile been moved from trusty-proposed to trusty-updates and will be part of a standard trusty implementation now. ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1414333 Title: libcairo-dev depencencies in Utopic Status in cairo package in Ubuntu: Invalid Bug description: My problem in Utopic is: The following packages have unmet dependencies: libcairo2-dev : Depends: libcairo2 (= 1.13.0~20140204-0ubuntu1) but 1.13.0~20140204-0ubuntu1.1 is to be installed Depends: libcairo-gobject2 (= 1.13.0~20140204-0ubuntu1) but 1.13.0~20140204-0ubuntu1.1 is to be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1414333/+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 1371859] Re: can't update loaders.cache: permission denied
Putting sudo in front of a command for redirecting output to a file where you do not have write permission, does not help. You might try gdk-pixbuf-query-loaders | sudo tee /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1371859 Title: can't update loaders.cache: permission denied Status in “gdk-pixbuf” package in Ubuntu: New Bug description: upgrading that fresh Utopic 64 bits installation, i'm seeing that error into the dialog box: Processing triggers for hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:3098): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. The terminal output is: oem@u64:~$ gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache bash: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache: Permission denied oem@u64:~$ sudo gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache bash: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache: Permission denied ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libgdk-pixbuf2.0-0 2.30.8-1 ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Sep 20 08:00:57 2014 SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1371859/+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 1371293] Re: console-kit-daemon[5037]: GLib-CRITICAL: Source ID 40 was not found when attempting to remove it
*** This bug is a duplicate of bug 1313042 *** https://bugs.launchpad.net/bugs/1313042 ** This bug has been marked a duplicate of bug 1313042 console-kit-daemon Glib-CRITICAL warning -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to consolekit in Ubuntu. https://bugs.launchpad.net/bugs/1371293 Title: console-kit-daemon[5037]: GLib-CRITICAL: Source ID 40 was not found when attempting to remove it Status in “consolekit” package in Ubuntu: New Bug description: Hi, In syslog there is critical error/s: Sep 18 21:15:38 hostname console-kit-daemon[5037]: GLib-CRITICAL: Source ID 40 was not found when attempting to remove it Sep 18 21:15:38 hostname console-kit-daemon[5037]: GLib-CRITICAL: Source ID 49 was not found when attempting to remove it apt-cache policy consolekit consolekit: Installed: 0.4.6-5 Candidate: 0.4.6-5 Version table: *** 0.4.6-5 0 500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status lsb_release -rd Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 Thank You, Kind Regards, Martin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/1371293/+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 1313042] Re: console-kit-daemon Glib-CRITICAL warning
I think I have given some hints on what source changes might be required in https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/1313042/comments/7 I am not sure if these changes will ever be implemented in the package, because http://freedesktop.org/wiki/Software/ConsoleKit/ tells "ConsoleKit is currently not actively maintained. The focus has shifted to the built-in seat/user/session management of Software/systemd called systemd-logind!" (I do not have any knowledge what has to be done to replace consolekit functionality by systemd-logind.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to consolekit in Ubuntu. https://bugs.launchpad.net/bugs/1313042 Title: console-kit-daemon Glib-CRITICAL warning Status in “consolekit” package in Ubuntu: Confirmed Bug description: The day I upgraded from 13.10 to 14.04 some of my ssh sessions into the new system (server side is Ubuntu 14.04) started hanging. The symptom is: I run some command with a lot of output (say a few hundreds of lines) in an ssh session, and the second the command completes, and the shell displays a new prompt, the shell stops responding to keyboard input. At the exact time of the hang (to the second) I always see these 3 warnings in syslog: Apr 21 18:15:25 xx console-kit-daemon[3357]: GLib-CRITICAL: Source ID 469 was not found when attempting to remove it Apr 21 18:15:25 xx console-kit-daemon[3357]: GLib-CRITICAL: Source ID 86 was not found when attempting to remove it Apr 21 18:15:25 xx console-kit-daemon[3357]: GLib-CRITICAL: Source ID 86 was not found when attempting to remove it The Source ID numbers vary, but the warnings always come in triplets at the time of the hang. I was able to reproduce this about 10 times today. Every time the session hangs, these warnings appear in the log and vice versa: every time they appear in the log, I have a hanged remote session. A quote from an upstream (bugzilla.gnome.org) comment: https://bugzilla.gnome.org/show_bug.cgi?id=721369 GLib recently started throwing a warning when g_source_remove() is passed garbage (as per warning). Your applications have probably been broken for a while, and there's no telling what could actually have happened in the past when g_source_remove() would happily close any random source because the programmer got the wrong argument to g_source_remove(). So based on this I'm opening a bug against consolekit for bad calls to g_source_remove() which seem to be related to the ssh hang. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/1313042/+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