[Touch-packages] [Bug 1781169] Re: apt frontend locking
Frontend locking causes a regression: dpkg::post-invoke and other related scripts can no longer install/remove packages, as they are now called with 'lock' released, but 'lock-frontend' not. This needs a further change to set DPKG_FRONTEND_LOCKED for those scripts when the frontend lock is acquired. ** Tags removed: verification-needed verification-needed-bionic verification-needed-xenial ** Tags added: verification-failed verification-failed-bionic verification-failed-xenial -- 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/1781169 Title: apt frontend locking Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Bug description: [Impact] apt acquires /var/lib/dpkg/lock but has to release it while running dpkg, offering a short window for other clients to acquire the lock. This implements /var/lib/dpkg/lock-frontend which will be acquired earlier and not released by apt for dpkg to run. dpkg will try to acquire the frontend lock as well, unless told not to do so via an environment variable, which apt does; hence concurrent runs of dpkg without other locking can't happen. [Test case] Run strace apt install $something and check that lock-frontend is acquired at the beginning and not released until the end. [Regression potential] Frontend locking failures are in English, as there are no translations yet. More locks also mean more potential for locking to go wrong across programs, but since we don't have any waiting locks we at least won't deadlock. [Other info] This is part of a wider series of SRUs for frontend locking - dpkg (bug 1796081) - apt (bug 1781169) - python-apt (bug 1795407) - packagekit (bug 1795614) - unattended-upgrades (bug 1789637) - aptdaemon (no bug filed yet) Further details about frontend locking can be found in https://lists.debian.org/debian-dpkg/2017/01/msg00044.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1781169/+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 1796246] [NEW] Assembler crashes when building ndiswrapper
You have been subscribed to a public bug: > lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 -- > apt-cache policy binutils binutils: Installato: 2.30-21ubuntu1~18.04 Candidato: 2.30-21ubuntu1~18.04 Tabella versione: *** 2.30-21ubuntu1~18.04 500 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.30-20ubuntu2~18.04 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2.30-15ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages -- when installing ndiswrapper-1.50 via apt-get: Loading new ndiswrapper-1.60 DKMS files... Building for 4.15.0-34-generic 4.15.0-36-generic Building initial module for 4.15.0-34-generic Done. ndiswrapper: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.15.0-34-generic/updates/dkms/ depmod... DKMS: install completed. Building initial module for 4.15.0-36-generic Error! Bad return status for module build on kernel: 4.15.0-36-generic (x86_64) Consult /var/lib/dkms/ndiswrapper/1.60/build/make.log for more information. --- contents of the log file: DKMS make.log for ndiswrapper-1.60 for kernel 4.15.0-36-generic (x86_64) mer 3 ott 2018, 12.29.37, CEST make: ingresso nella directory "/usr/src/linux-headers-4.15.0-36-generic" MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/crt_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/hal_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ndis_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/rtl_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/usb_exports.h MKSTUBS /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.h CC [M] /var/lib/dkms/ndiswrapper/1.60/build/crt.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/hal.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/loader.o symbolmap: sezione: invalid section CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/pe_linker.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/pnp.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/proc.o symbolmap: sezione: invalid section CC [M] /var/lib/dkms/ndiswrapper/1.60/build/rtl.o symbolmap: sezione: invalid section CC [M] /var/lib/dkms/ndiswrapper/1.60/build/wrapmem.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/wrapndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/wrapper.o Assembler messages: Internal error (Errore di segmentazione). Please report this bug. CC [M] /var/lib/dkms/ndiswrapper/1.60/build/usb.o AS [M] /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.o scripts/Makefile.build:332: recipe for target '/var/lib/dkms/ndiswrapper/1.60/build/wrapper.o' failed make[1]: *** [/var/lib/dkms/ndiswrapper/1.60/build/wrapper.o] Error 2 make[1]: *** Attesa per i processi non terminati symbolmap: sezione: invalid section symbolmap: sezione: invalid section Makefile:1551: recipe for target '_module_/var/lib/dkms/ndiswrapper/1.60/build' failed make: *** [_module_/var/lib/dkms/ndiswrapper/1.60/build] Error 2 make: uscita dalla directory "/usr/src/linux-headers-4.15.0-36-generic" ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ndiswrapper-dkms 1.60-6 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DKMSKernelVersion: 4.15.0-36-generic Date: Wed Oct 3 12:29:45 2018 InstallationDate: Installed on 2016-01-25 (981 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all PackageVersion: 1.60-6 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: ndiswrapper Title: ndiswrapper-dkms 1.60-6: ndiswrapper kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ndiswrapper-dkms 1.60-6 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DKMSKernelVersion: 4.15.0-36-generic Date: Wed Oct 3 12:29:45 2018 InstallationDate: Installed on 2016-01-25 (981 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture:
[Touch-packages] [Bug 1796246] [NEW] Assembler crashes when building ndiswrapper
Public bug reported: > lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 -- > apt-cache policy binutils binutils: Installato: 2.30-21ubuntu1~18.04 Candidato: 2.30-21ubuntu1~18.04 Tabella versione: *** 2.30-21ubuntu1~18.04 500 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.30-20ubuntu2~18.04 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2.30-15ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages -- when installing ndiswrapper-1.50 via apt-get: Loading new ndiswrapper-1.60 DKMS files... Building for 4.15.0-34-generic 4.15.0-36-generic Building initial module for 4.15.0-34-generic Done. ndiswrapper: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.15.0-34-generic/updates/dkms/ depmod... DKMS: install completed. Building initial module for 4.15.0-36-generic Error! Bad return status for module build on kernel: 4.15.0-36-generic (x86_64) Consult /var/lib/dkms/ndiswrapper/1.60/build/make.log for more information. --- contents of the log file: DKMS make.log for ndiswrapper-1.60 for kernel 4.15.0-36-generic (x86_64) mer 3 ott 2018, 12.29.37, CEST make: ingresso nella directory "/usr/src/linux-headers-4.15.0-36-generic" MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/crt_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/hal_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ndis_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/rtl_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/usb_exports.h MKSTUBS /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.h CC [M] /var/lib/dkms/ndiswrapper/1.60/build/crt.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/hal.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/loader.o symbolmap: sezione: invalid section CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/pe_linker.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/pnp.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/proc.o symbolmap: sezione: invalid section CC [M] /var/lib/dkms/ndiswrapper/1.60/build/rtl.o symbolmap: sezione: invalid section CC [M] /var/lib/dkms/ndiswrapper/1.60/build/wrapmem.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/wrapndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/wrapper.o Assembler messages: Internal error (Errore di segmentazione). Please report this bug. CC [M] /var/lib/dkms/ndiswrapper/1.60/build/usb.o AS [M] /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.o scripts/Makefile.build:332: recipe for target '/var/lib/dkms/ndiswrapper/1.60/build/wrapper.o' failed make[1]: *** [/var/lib/dkms/ndiswrapper/1.60/build/wrapper.o] Error 2 make[1]: *** Attesa per i processi non terminati symbolmap: sezione: invalid section symbolmap: sezione: invalid section Makefile:1551: recipe for target '_module_/var/lib/dkms/ndiswrapper/1.60/build' failed make: *** [_module_/var/lib/dkms/ndiswrapper/1.60/build] Error 2 make: uscita dalla directory "/usr/src/linux-headers-4.15.0-36-generic" ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ndiswrapper-dkms 1.60-6 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DKMSKernelVersion: 4.15.0-36-generic Date: Wed Oct 3 12:29:45 2018 InstallationDate: Installed on 2016-01-25 (981 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all PackageVersion: 1.60-6 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: ndiswrapper Title: ndiswrapper-dkms 1.60-6: ndiswrapper kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ndiswrapper-dkms 1.60-6 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DKMSKernelVersion: 4.15.0-36-generic Date: Wed Oct 3 12:29:45 2018 InstallationDate: Installed on 2016-01-25 (981 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all PackageVersion: 1
[Touch-packages] [Bug 1795853] Re: Assembler crashes when building ndiswrapper
As requested, this is the link to the newly created bug https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1796246 (why did I have to do this?) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1795853 Title: Assembler crashes when building ndiswrapper Status in binutils package in Ubuntu: Incomplete Bug description: > lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 -- > apt-cache policy ndiswrapper-dkms ndiswrapper-dkms: Installato: 1.60-6 Candidato: 1.60-6 Tabella versione: *** 1.60-6 500 500 http://it.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://it.archive.ubuntu.com/ubuntu bionic/universe i386 Packages 100 /var/lib/dpkg/status -- when installing via apt-get: Loading new ndiswrapper-1.60 DKMS files... Building for 4.15.0-34-generic 4.15.0-36-generic Building initial module for 4.15.0-34-generic Done. ndiswrapper: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.15.0-34-generic/updates/dkms/ depmod... DKMS: install completed. Building initial module for 4.15.0-36-generic Error! Bad return status for module build on kernel: 4.15.0-36-generic (x86_64) Consult /var/lib/dkms/ndiswrapper/1.60/build/make.log for more information. --- contents of the log file: DKMS make.log for ndiswrapper-1.60 for kernel 4.15.0-36-generic (x86_64) mer 3 ott 2018, 12.29.37, CEST make: ingresso nella directory "/usr/src/linux-headers-4.15.0-36-generic" MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/crt_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/hal_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ndis_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/rtl_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/usb_exports.h MKSTUBS /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.h CC [M] /var/lib/dkms/ndiswrapper/1.60/build/crt.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/hal.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/loader.o symbolmap: sezione: invalid section CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/pe_linker.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/pnp.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/proc.o symbolmap: sezione: invalid section CC [M] /var/lib/dkms/ndiswrapper/1.60/build/rtl.o symbolmap: sezione: invalid section CC [M] /var/lib/dkms/ndiswrapper/1.60/build/wrapmem.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/wrapndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/wrapper.o Assembler messages: Internal error (Errore di segmentazione). Please report this bug. CC [M] /var/lib/dkms/ndiswrapper/1.60/build/usb.o AS [M] /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.o scripts/Makefile.build:332: recipe for target '/var/lib/dkms/ndiswrapper/1.60/build/wrapper.o' failed make[1]: *** [/var/lib/dkms/ndiswrapper/1.60/build/wrapper.o] Error 2 make[1]: *** Attesa per i processi non terminati symbolmap: sezione: invalid section symbolmap: sezione: invalid section Makefile:1551: recipe for target '_module_/var/lib/dkms/ndiswrapper/1.60/build' failed make: *** [_module_/var/lib/dkms/ndiswrapper/1.60/build] Error 2 make: uscita dalla directory "/usr/src/linux-headers-4.15.0-36-generic" ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ndiswrapper-dkms 1.60-6 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DKMSKernelVersion: 4.15.0-36-generic Date: Wed Oct 3 12:29:45 2018 InstallationDate: Installed on 2016-01-25 (981 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all PackageVersion: 1.60-6 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: ndiswrapper Title: ndiswrapper-dkms 1.60-6: ndiswrapper kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage
[Touch-packages] [Bug 1796246] Re: Assembler crashes when building ndiswrapper
*** This bug is a duplicate of bug 1795853 *** https://bugs.launchpad.net/bugs/1795853 ** This bug has been marked a duplicate of bug 1795853 Assembler crashes when building ndiswrapper -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1796246 Title: Assembler crashes when building ndiswrapper Status in binutils package in Ubuntu: New Bug description: > lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 -- > apt-cache policy binutils binutils: Installato: 2.30-21ubuntu1~18.04 Candidato: 2.30-21ubuntu1~18.04 Tabella versione: *** 2.30-21ubuntu1~18.04 500 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.30-20ubuntu2~18.04 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2.30-15ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages -- when installing ndiswrapper-1.50 via apt-get: Loading new ndiswrapper-1.60 DKMS files... Building for 4.15.0-34-generic 4.15.0-36-generic Building initial module for 4.15.0-34-generic Done. ndiswrapper: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.15.0-34-generic/updates/dkms/ depmod... DKMS: install completed. Building initial module for 4.15.0-36-generic Error! Bad return status for module build on kernel: 4.15.0-36-generic (x86_64) Consult /var/lib/dkms/ndiswrapper/1.60/build/make.log for more information. --- contents of the log file: DKMS make.log for ndiswrapper-1.60 for kernel 4.15.0-36-generic (x86_64) mer 3 ott 2018, 12.29.37, CEST make: ingresso nella directory "/usr/src/linux-headers-4.15.0-36-generic" MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/crt_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/hal_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ndis_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/rtl_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/usb_exports.h MKSTUBS /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.h CC [M] /var/lib/dkms/ndiswrapper/1.60/build/crt.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/hal.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/loader.o symbolmap: sezione: invalid section CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/pe_linker.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/pnp.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/proc.o symbolmap: sezione: invalid section CC [M] /var/lib/dkms/ndiswrapper/1.60/build/rtl.o symbolmap: sezione: invalid section CC [M] /var/lib/dkms/ndiswrapper/1.60/build/wrapmem.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/wrapndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/wrapper.o Assembler messages: Internal error (Errore di segmentazione). Please report this bug. CC [M] /var/lib/dkms/ndiswrapper/1.60/build/usb.o AS [M] /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.o scripts/Makefile.build:332: recipe for target '/var/lib/dkms/ndiswrapper/1.60/build/wrapper.o' failed make[1]: *** [/var/lib/dkms/ndiswrapper/1.60/build/wrapper.o] Error 2 make[1]: *** Attesa per i processi non terminati symbolmap: sezione: invalid section symbolmap: sezione: invalid section Makefile:1551: recipe for target '_module_/var/lib/dkms/ndiswrapper/1.60/build' failed make: *** [_module_/var/lib/dkms/ndiswrapper/1.60/build] Error 2 make: uscita dalla directory "/usr/src/linux-headers-4.15.0-36-generic" ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ndiswrapper-dkms 1.60-6 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DKMSKernelVersion: 4.15.0-36-generic Date: Wed Oct 3 12:29:45 2018 InstallationDate: Installed on 2016-01-25 (981 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all PackageVersion: 1.60-6 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2
[Touch-packages] [Bug 1795853] Re: Assembler crashes when building ndiswrapper
That's not what I meant. The 'ubuntu-bug yourfile.crash' command will create a new bug. If it doesn't then try 'apport-cli yourfile.crash' instead. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1795853 Title: Assembler crashes when building ndiswrapper Status in binutils package in Ubuntu: Incomplete Bug description: > lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 -- > apt-cache policy ndiswrapper-dkms ndiswrapper-dkms: Installato: 1.60-6 Candidato: 1.60-6 Tabella versione: *** 1.60-6 500 500 http://it.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://it.archive.ubuntu.com/ubuntu bionic/universe i386 Packages 100 /var/lib/dpkg/status -- when installing via apt-get: Loading new ndiswrapper-1.60 DKMS files... Building for 4.15.0-34-generic 4.15.0-36-generic Building initial module for 4.15.0-34-generic Done. ndiswrapper: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.15.0-34-generic/updates/dkms/ depmod... DKMS: install completed. Building initial module for 4.15.0-36-generic Error! Bad return status for module build on kernel: 4.15.0-36-generic (x86_64) Consult /var/lib/dkms/ndiswrapper/1.60/build/make.log for more information. --- contents of the log file: DKMS make.log for ndiswrapper-1.60 for kernel 4.15.0-36-generic (x86_64) mer 3 ott 2018, 12.29.37, CEST make: ingresso nella directory "/usr/src/linux-headers-4.15.0-36-generic" MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/crt_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/hal_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ndis_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/rtl_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/usb_exports.h MKSTUBS /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.h CC [M] /var/lib/dkms/ndiswrapper/1.60/build/crt.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/hal.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/loader.o symbolmap: sezione: invalid section CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/pe_linker.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/pnp.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/proc.o symbolmap: sezione: invalid section CC [M] /var/lib/dkms/ndiswrapper/1.60/build/rtl.o symbolmap: sezione: invalid section CC [M] /var/lib/dkms/ndiswrapper/1.60/build/wrapmem.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/wrapndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/wrapper.o Assembler messages: Internal error (Errore di segmentazione). Please report this bug. CC [M] /var/lib/dkms/ndiswrapper/1.60/build/usb.o AS [M] /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.o scripts/Makefile.build:332: recipe for target '/var/lib/dkms/ndiswrapper/1.60/build/wrapper.o' failed make[1]: *** [/var/lib/dkms/ndiswrapper/1.60/build/wrapper.o] Error 2 make[1]: *** Attesa per i processi non terminati symbolmap: sezione: invalid section symbolmap: sezione: invalid section Makefile:1551: recipe for target '_module_/var/lib/dkms/ndiswrapper/1.60/build' failed make: *** [_module_/var/lib/dkms/ndiswrapper/1.60/build] Error 2 make: uscita dalla directory "/usr/src/linux-headers-4.15.0-36-generic" ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ndiswrapper-dkms 1.60-6 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DKMSKernelVersion: 4.15.0-36-generic Date: Wed Oct 3 12:29:45 2018 InstallationDate: Installed on 2016-01-25 (981 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all PackageVersion: 1.60-6 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: ndiswrapper Title: ndiswrapper-dkms 1.60-6: ndiswrapper kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage n
[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot
Sorry, still not working here. Same behavior as my previous post.
Maybe it's due to VirtualBox? Haven't tried on my production KDE (Proxmox)
yet...
---
# dpkg -s netplan.io | grep Version
Version: 0.40~18.04.1
---
** Tags removed: verification-needed-bionic
** Tags added: verification-failed-bionic
--
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/1770082
Title:
systemd-networkd not renaming devices on boot
Status in netplan:
Fix Released
Status in cloud-init package in Ubuntu:
Confirmed
Status in netplan.io package in Ubuntu:
Fix Released
Status in nplan package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Confirmed
Status in nplan source package in Xenial:
Fix Released
Status in netplan.io source package in Bionic:
Fix Committed
Bug description:
[Impact]
Systems relying on renaming network interfaces at boot and when 'netplan
apply' is run.
[Test case]
- Write a new netplan YAML (adjusting for current system as necessary):
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: myif0
- Run 'netplan apply'
- Verify that the device is correctly renamed to 'myif0'.
- Reboot.
- Make sure the device is correctly renamed to 'myif0'.
[Regression potential]
Changes in rename logic to add udev rules may otherwise impact applying
different settings to the network interfaces. Changes in settings on network
interfaces, missing parameters (especially on bonds, bridges) should be
investigated as potential regressions. Other failures to apply network settings
might also happen if there's a race between applying renames via the udev
rules, and using the new names to apply configuration changes to the interfaces.
=== systemd issue ===
Renaming devices doesn't seem to work.
If I disable all other network configuration and create
/etc/systemd/network/10-network.link with:
[Match]
MACAddress=52:54:00:c1:c9:bb
[Link]
Name=myiface3
I expect this to cause the device with that MAC address to be renamed
to myiface3. However, when I reboot, I instead see:
$ ip l
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
The device is not renamed.
This link file is pretty much identical to Example 2 in
https://www.freedesktop.org/software/systemd/man/systemd.link.html.
The renaming does work if I boot with net.ifnames=0, and oddly, it
also works if I unbind the device and rebind it as netplan apply does.
No setting of NamePolicy seems to help.
=== Original Bug ==
'set-name:' doesn't change the name of a network interface on boot, it
only works when you do netplan apply.
Say I take this 50-cloud-init.yaml file:
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: ens3
Say I change set-name to 'myiface3' and reboot. I expect that the
device will be called myiface3 and brought up fine with dhcp. However,
instead I see:
$ ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: mtu 1500 qdisc noop state DOWN group default
qlen 1000
link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
The name has not been changed, and the device has not been brought up.
If I run netplan apply however, I see the following:
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
3: myiface3: mtu 1500 qdisc fq_codel state
UP group default qlen 1000
link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
valid_lft 3575sec preferred_lft 3575sec
inet6 fe80::5054:ff:fede:bdf6/64 scope link
valid_l
[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot
Wrong cut&paste:
---
# dpkg -s netplan.io | grep Version
Version: 0.40.1~18.04.1
---
--
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/1770082
Title:
systemd-networkd not renaming devices on boot
Status in netplan:
Fix Released
Status in cloud-init package in Ubuntu:
Confirmed
Status in netplan.io package in Ubuntu:
Fix Released
Status in nplan package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Confirmed
Status in nplan source package in Xenial:
Fix Released
Status in netplan.io source package in Bionic:
Fix Committed
Bug description:
[Impact]
Systems relying on renaming network interfaces at boot and when 'netplan
apply' is run.
[Test case]
- Write a new netplan YAML (adjusting for current system as necessary):
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: myif0
- Run 'netplan apply'
- Verify that the device is correctly renamed to 'myif0'.
- Reboot.
- Make sure the device is correctly renamed to 'myif0'.
[Regression potential]
Changes in rename logic to add udev rules may otherwise impact applying
different settings to the network interfaces. Changes in settings on network
interfaces, missing parameters (especially on bonds, bridges) should be
investigated as potential regressions. Other failures to apply network settings
might also happen if there's a race between applying renames via the udev
rules, and using the new names to apply configuration changes to the interfaces.
=== systemd issue ===
Renaming devices doesn't seem to work.
If I disable all other network configuration and create
/etc/systemd/network/10-network.link with:
[Match]
MACAddress=52:54:00:c1:c9:bb
[Link]
Name=myiface3
I expect this to cause the device with that MAC address to be renamed
to myiface3. However, when I reboot, I instead see:
$ ip l
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
The device is not renamed.
This link file is pretty much identical to Example 2 in
https://www.freedesktop.org/software/systemd/man/systemd.link.html.
The renaming does work if I boot with net.ifnames=0, and oddly, it
also works if I unbind the device and rebind it as netplan apply does.
No setting of NamePolicy seems to help.
=== Original Bug ==
'set-name:' doesn't change the name of a network interface on boot, it
only works when you do netplan apply.
Say I take this 50-cloud-init.yaml file:
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: ens3
Say I change set-name to 'myiface3' and reboot. I expect that the
device will be called myiface3 and brought up fine with dhcp. However,
instead I see:
$ ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: mtu 1500 qdisc noop state DOWN group default
qlen 1000
link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
The name has not been changed, and the device has not been brought up.
If I run netplan apply however, I see the following:
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
3: myiface3: mtu 1500 qdisc fq_codel state
UP group default qlen 1000
link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
valid_lft 3575sec preferred_lft 3575sec
inet6 fe80::5054:ff:fede:bdf6/64 scope link
valid_lft forever preferred_lft forever
So names are successfully changed with netplan apply.
This seems to be some udev-related timing or priority issue that I'm
still trying to hunt down.
This breaks some forms o
[Touch-packages] [Bug 1795853] Re: Assembler crashes when building ndiswrapper
As apport-cli led to the same situation as before, I tried step 2, but I couldn't find any recent error reported on that page. Therefore, after performing an automatic system update, I tried step 3, as you suggested, and the problem did not presented again (ndiswrapper-dkms installed regularly and the module compiled without errors). I cannot send you more details or create a new bug. Thanks for your help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1795853 Title: Assembler crashes when building ndiswrapper Status in binutils package in Ubuntu: Incomplete Bug description: > lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 -- > apt-cache policy ndiswrapper-dkms ndiswrapper-dkms: Installato: 1.60-6 Candidato: 1.60-6 Tabella versione: *** 1.60-6 500 500 http://it.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://it.archive.ubuntu.com/ubuntu bionic/universe i386 Packages 100 /var/lib/dpkg/status -- when installing via apt-get: Loading new ndiswrapper-1.60 DKMS files... Building for 4.15.0-34-generic 4.15.0-36-generic Building initial module for 4.15.0-34-generic Done. ndiswrapper: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.15.0-34-generic/updates/dkms/ depmod... DKMS: install completed. Building initial module for 4.15.0-36-generic Error! Bad return status for module build on kernel: 4.15.0-36-generic (x86_64) Consult /var/lib/dkms/ndiswrapper/1.60/build/make.log for more information. --- contents of the log file: DKMS make.log for ndiswrapper-1.60 for kernel 4.15.0-36-generic (x86_64) mer 3 ott 2018, 12.29.37, CEST make: ingresso nella directory "/usr/src/linux-headers-4.15.0-36-generic" MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/crt_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/hal_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ndis_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/rtl_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.60/build/usb_exports.h MKSTUBS /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.h CC [M] /var/lib/dkms/ndiswrapper/1.60/build/crt.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/hal.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/iw_ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/loader.o symbolmap: sezione: invalid section CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/ntoskernel_io.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/pe_linker.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/pnp.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/proc.o symbolmap: sezione: invalid section CC [M] /var/lib/dkms/ndiswrapper/1.60/build/rtl.o symbolmap: sezione: invalid section CC [M] /var/lib/dkms/ndiswrapper/1.60/build/wrapmem.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/wrapndis.o CC [M] /var/lib/dkms/ndiswrapper/1.60/build/wrapper.o Assembler messages: Internal error (Errore di segmentazione). Please report this bug. CC [M] /var/lib/dkms/ndiswrapper/1.60/build/usb.o AS [M] /var/lib/dkms/ndiswrapper/1.60/build/win2lin_stubs.o scripts/Makefile.build:332: recipe for target '/var/lib/dkms/ndiswrapper/1.60/build/wrapper.o' failed make[1]: *** [/var/lib/dkms/ndiswrapper/1.60/build/wrapper.o] Error 2 make[1]: *** Attesa per i processi non terminati symbolmap: sezione: invalid section symbolmap: sezione: invalid section Makefile:1551: recipe for target '_module_/var/lib/dkms/ndiswrapper/1.60/build' failed make: *** [_module_/var/lib/dkms/ndiswrapper/1.60/build] Error 2 make: uscita dalla directory "/usr/src/linux-headers-4.15.0-36-generic" ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ndiswrapper-dkms 1.60-6 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DKMSKernelVersion: 4.15.0-36-generic Date: Wed Oct 3 12:29:45 2018 InstallationDate: Installed on 2016-01-25 (981 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all PackageVersion: 1.60-6 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7
[Touch-packages] [Bug 216847] Re: sshd will not start at boot if ListenAddress is set, because network interface is not yet up
10 years ago ... Same bug ! Incredible :( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/216847 Title: sshd will not start at boot if ListenAddress is set, because network interface is not yet up Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Confirmed Bug description: Binary package hint: openssh-server The sshd will not start at boot if the ListenAddress option in /etc/ssh/sshd_config is set to an IPv4 address other then 0.0.0.0 . I am using Ubuntu 7.10 and the version 1:4.6p1-5ubuntu0.2 of the openssh-server package. I would expect that sshd is started after boot but it will not and I found this in /var/log/auth.log: sshd[4527]: error: Bind to port 22 on 10.1.1.22 failed: Cannot assign requested address. sshd[4527]: fatal: Cannot bind any address. Once the System is started you can start/stop the sshd with the /etc/init.d/ssh script without any problems. To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/216847/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
After the update to the latest available version of the package .. initramfs-tools/bionic-updates,bionic-updates,now 0.130ubuntu3.5 all [installed] the problem still exists! Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic -- 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/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Confirmed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1796274] [NEW] /usr/lib/packagekit/packagekitd:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:std::__throw_length_error
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.1.10-1ubuntu6, the problem page at https://errors.ubuntu.com/problem/97c33f533af7c2ce7fe52bd67a84c2a230b59ba9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: packagekit (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic kylin-18.10 raring saucy trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1796274 Title: /usr/lib/packagekit/packagekitd:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:std::__throw_length_error Status in packagekit package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.1.10-1ubuntu6, the problem page at https://errors.ubuntu.com/problem/97c33f533af7c2ce7fe52bd67a84c2a230b59ba9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1796274/+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 1796274] Re: /usr/lib/packagekit/packagekitd:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:std::__throw_length_error
Odd, it crashes in std::stringstream::str() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1796274 Title: /usr/lib/packagekit/packagekitd:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:std::__throw_length_error Status in packagekit package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.1.10-1ubuntu6, the problem page at https://errors.ubuntu.com/problem/97c33f533af7c2ce7fe52bd67a84c2a230b59ba9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1796274/+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 1778936] Re: please re-add Support-system-image-read-only-etc.patch
** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress -- 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/1778936 Title: please re-add Support-system-image-read-only-etc.patch Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Fix Released Bug description: The 16.04 version of systemd had a patch to support the read-only etc. For core18 we will also need this change because core18 is still not on a fully writable etc. I will attach a debdiff against the current bionic version of systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+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 1773148] Re: /lib/systemd/systemd-journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate
** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress -- 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/1773148 Title: /lib/systemd/systemd- journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: New Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 237-3ubuntu10, the problem page at https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1773148/+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 1773859] Re: upgrades to 18.04 fail
** Changed in: systemd (Ubuntu Bionic) Status: Confirmed => In Progress -- 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/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Committed Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: In Progress Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Committed Status in systemd-shim source package in Cosmic: Won't Fix Bug description: $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+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 1776626] Re: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part
** Also affects: cryptsetup (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress -- 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/1776626 Title: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part Status in Ubuntu on IBM z Systems: Fix Released Status in cryptsetup package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in cryptsetup source package in Bionic: New Status in systemd source package in Bionic: In Progress Bug description: Support fast clear key dm-crypt with 4k support Extend /etc/crypttab to enable 4k sector support in plain mode The proposed enhancements are posted on github, see https://github.com/systemd/systemd/issues/8881 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1776626/+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 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
** Changed in: systemd (Ubuntu Bionic) Status: Confirmed => In Progress -- 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/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: In Progress Status in snapd source package in Cosmic: Confirmed Status in systemd source package in Cosmic: Fix Released Bug description: This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. Specifically, this is evident by e.g. $ systemd-run env. Or any other daemons that spawn shell scripts (e.g. cloud-init metadata acquired shell hooks, etc.). Since v232 systemd provides support for environment generators, snapd should package/ship a snippet that injects the correct snapd path into systemd environment. E.g.: $ sudo mkdir -p /usr/lib/systemd/system-environment-generators $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \ sudo tee /usr/lib/systemd/system-environment-generators/90-snapd Something similar can be done for user-environment-generators too. Note that user-environment-generators can generate unique variables per user. Note please use /usr/lib path, as it appears that /lib/systemd path is not working atm. Will check if that needs to be fixed up. systemd in xenial does not support system-environment-generators, thus we probably need to upload a patch to change the DEFAULT_PATH compiled in default there. [Testcase] $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
** Changed in: systemd (Ubuntu Bionic) Status: Confirmed => In Progress -- 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/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in landscape-client source package in Bionic: New Status in systemd source package in Bionic: In Progress Status in landscape-client source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+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 1796308] [NEW] package libapparmor1:amd64 2.12-4ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu
Public bug reported: I don't know. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libapparmor1:amd64 2.12-4ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Fri Oct 5 10:47:23 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 DuplicateSignature: package:libapparmor1:amd64:2.12-4ubuntu5 Setting up librubberband2:amd64 (1.8.1-7ubuntu2) ... dpkg: error processing package libapparmor1:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-08-09 (56 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=46667fc6-e4b4-40a9-969f-70f354598d84 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: apparmor Syslog: Title: package libapparmor1:amd64 2.12-4ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1796308 Title: package libapparmor1:amd64 2.12-4ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in apparmor package in Ubuntu: New Bug description: I don't know. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libapparmor1:amd64 2.12-4ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Fri Oct 5 10:47:23 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 DuplicateSignature: package:libapparmor1:amd64:2.12-4ubuntu5 Setting up librubberband2:amd64 (1.8.1-7ubuntu2) ... dpkg: error processing package libapparmor1:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-08-09 (56 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=46667fc6-e4b4-40a9-969f-70f354598d84 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: apparmor Syslog: Title: package libapparmor1:amd64 2.12-4ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1796308/+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 1796308] Re: package libapparmor1:amd64 2.12-4ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1796308 Title: package libapparmor1:amd64 2.12-4ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in apparmor package in Ubuntu: New Bug description: I don't know. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libapparmor1:amd64 2.12-4ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Fri Oct 5 10:47:23 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 DuplicateSignature: package:libapparmor1:amd64:2.12-4ubuntu5 Setting up librubberband2:amd64 (1.8.1-7ubuntu2) ... dpkg: error processing package libapparmor1:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-08-09 (56 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=46667fc6-e4b4-40a9-969f-70f354598d84 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: apparmor Syslog: Title: package libapparmor1:amd64 2.12-4ubuntu5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1796308/+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 1671951] Re: networkd should allow configuring IPV6 MTU
** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress -- 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/1671951 Title: networkd should allow configuring IPV6 MTU Status in cloud-init package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: Fix Released Status in cloud-init source package in Bionic: Confirmed Status in netplan.io source package in Bionic: New Status in systemd source package in Bionic: In Progress Bug description: 1) Zesty 2) systemd-232-19 3) I need to configure the IPV6 MTU for tunneling by adding an IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 static address in the [Network] section 4) networkd does not parse or read the value and does not apply this configuration to the interface. Upstream has discussed this issue here: https://github.com/systemd/systemd/pull/1533 But it's been closed in favor of only setting via RA. However, we know of multiple use-case which are currently supported in ifdupdown where we want to retain control over IPV6 MTU values outside of PMTU Discovery configurations. Some context from those discussions >> Client systems that route their ipv6 packets to a 6in4 router also >> have to have their ipv6 mtu lowered. They could lower their link mtu, >> so their ipv6 packets are small enough, but that reduces performance >> of their ipv4 network. Yes. Anything that creates a PMTUD black hole can result in situations where the higher header overhead of IPv6 will cause IPv4 to pass but IPv6 traffic to be dropped. One example here is egress from an ipsec tunnel wherein the next hop MTU is too low for IPv6 datagrams to pass. Another is VM -> whatever -> host bridge -> tunnel ingress. If the datagram cannot enter the tunnel due to size, it is dropped, and an ICMP response uses the tunnel address as a source, which may not be routable back to the origin. This one is an issue with IPv4 as well, and is one case where manually setting the IPv6 MTU lower than the (also manually set) device MTU is of benefit. In essence, any of these sort of cases that require an explicit setting of the device MTU will likely require a setting of the IPv6 mtu as well to account for its larger header overhead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1671951/+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 1796324] [NEW] symbol export missing: pa_encoding_from_string
Public bug reported: This specific release of libpulsecommon-11.1 is missing the symbol `pa_encoding_from_string`. This was fixed upstream: https://bugs.freedesktop.org/show_bug.cgi?id=103806 This has a Debian bug open, but I suspect it's been fixed by bumping major version: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882029 This results in unexpected: = note: /usr/bin/ld: /home/faux/code/rust-tone/target/debug/deps/liblibpulse_binding-f64ba2ce37bb3bc6.rlib(libpulse_binding-f64ba2ce37bb3bc6.libpulse_binding.3msoaviz-cgu.13.rcgu.o): undefined reference to symbol 'pa_encoding_from_string' //usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libpulse-dev 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: faux 2964 F pulseaudio /dev/snd/controlC2: faux 2964 F pulseaudio /dev/snd/pcmC0D0p: faux 2964 F...m pulseaudio /dev/snd/controlC0: faux 2964 F pulseaudio Date: Fri Oct 5 15:37:38 2018 InstallationDate: Installed on 2018-04-25 (162 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180425) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: Default string dmi.board.name: TUF Z370-PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd05/22/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFZ370-PROGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1796324 Title: symbol export missing: pa_encoding_from_string Status in pulseaudio package in Ubuntu: New Bug description: This specific release of libpulsecommon-11.1 is missing the symbol `pa_encoding_from_string`. This was fixed upstream: https://bugs.freedesktop.org/show_bug.cgi?id=103806 This has a Debian bug open, but I suspect it's been fixed by bumping major version: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882029 This results in unexpected: = note: /usr/bin/ld: /home/faux/code/rust-tone/target/debug/deps/liblibpulse_binding-f64ba2ce37bb3bc6.rlib(libpulse_binding-f64ba2ce37bb3bc6.libpulse_binding.3msoaviz-cgu.13.rcgu.o): undefined reference to symbol 'pa_encoding_from_string' //usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libpulse-dev 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: faux 2964 F pulseaudio /dev/snd/controlC2: faux 2964 F pulseaudio /dev/snd/pcmC0D0p: faux 2964 F...m pulseaudio /dev/snd/controlC0: faux 2964 F pulseaudio Date: Fri Oct 5 15:37:38 2018 InstallationDate: Installed on 2018-04-25 (162 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180425) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: Default string dmi.board.name: TUF Z370-PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd05/22/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFZ370-PROGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product
[Touch-packages] [Bug 1796355] [NEW] USB-C ValueLine network adapter fails to connect
Public bug reported: The adapter I'm trying to use using is a 'Valueline' USB-C adapter, with no external identifying information. lsusb lists it as Bus 004 Device 022: ID 0bda:8153 Realtek Semiconductor Corp. It works fine on a Windows 10 system (same hardware platform), where it's identified as a 10/100/1000 Realtek adapter. When I connect it to my system (Asus Zenbook UX490UA) internal lights go on, but no connection is produced. The network icon (upper right) is shown briefly, then disappears, the is show, then disappears. After some time it seems to give up. Kernel logs show repeated occurrences of: Oct 5 17:02:22 athasus kernel: [ 317.843590] usb 4-2: new SuperSpeed USB device number 121 using xhci_hcd Oct 5 17:02:22 athasus kernel: [ 317.863719] usb 4-2: New USB device found, idVendor=0bda, idProduct=8153 Oct 5 17:02:22 athasus kernel: [ 317.863728] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=6 Oct 5 17:02:22 athasus kernel: [ 317.863735] usb 4-2: Product: USB 10/100/1000 LAN Oct 5 17:02:22 athasus kernel: [ 317.863741] usb 4-2: Manufacturer: Realtek Oct 5 17:02:22 athasus kernel: [ 317.863745] usb 4-2: SerialNumber: 0100 Oct 5 17:02:22 athasus kernel: [ 318.000268] usb 4-2: reset SuperSpeed USB device number 121 using xhci_hcd Oct 5 17:02:22 athasus kernel: [ 318.057875] r8152 4-2:1.0 eth0: v1.09.9 Oct 5 17:02:22 athasus kernel: [ 318.138042] r8152 4-2:1.0 enxa0cec809bf58: renamed from eth0 Oct 5 17:02:22 athasus kernel: [ 318.170397] IPv6: ADDRCONF(NETDEV_UP): enxa0cec809bf58: link is not ready Oct 5 17:02:22 athasus kernel: [ 318.176359] IPv6: ADDRCONF(NETDEV_UP): enxa0cec809bf58: link is not ready Oct 5 17:02:22 athasus kernel: [ 318.354745] r8152 4-2:1.0 enxa0cec809bf58: Stop submitting intr, status -71 Oct 5 17:02:22 athasus kernel: [ 318.543737] usb 4-2: USB disconnect, device number 121 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 17:35:17 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-03 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 172.16.4.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 172.16.4.0/24 dev wlp2s0 proto kernel scope link src 172.16.4.102 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE ATH 79577e92-4b01-46c4-bbff-2088aaf0750a wifi 1538753528 fre 5 okt 2018 17:32:08 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 ATH 79577e92-4b01-46c4-bbff-2088aaf0750a /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1796355 Title: USB-C ValueLine network adapter fails to connect Status in network-manager package in Ubuntu: New Bug description: The adapter I'm trying to use using is a 'Valueline' USB-C adapter, with no external identifying information. lsusb lists it as Bus 004 Device 022: ID 0bda:8153 Realtek Semiconductor Corp. It works fine on a Windows 10 system (same hardware platform), where it's identified as a 10/100/1000 Realtek adapter. When I connect it to my system (Asus Zenbook UX490UA) internal lights go on, but no connection is produced. The network icon (upper right) is shown briefly, then di
[Touch-packages] [Bug 1796367] [NEW] New release of 'mesa3d' (18.2.2)
Public bug reported: Hello, https://www.mesa3d.org/relnotes/18.2.2.html Bug fixes - [apitrace] Graphical artifacts in Civilization VI on RX Vega - swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported - radv: OpBitfieldUExtract returns incorrect result when count is zero - [DXVK] MSAA reflections are broken in GTA V - [Debian Stretch]Fail to build because "xcb_randr_lease_t" Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglapi-mesa 18.2.1-1ubuntu1 Uname: Linux 4.18.12-gnu x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 13:45:21 2018 Dependencies: gcc-8-base 8.2.0-7ubuntu1 libc6 2.28-0ubuntu1 libgcc1 1:8.2.0-7ubuntu1 libidn2-0 2.0.5-1 libunistring2 0.9.10-1ubuntu1 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.18.0-8-generic, x86_64: installed virtualbox, 5.2.18, 4.18.12-gnu, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0d7] InstallationDate: Installed on 2017-10-13 (357 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.12-gnu root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 xserver.bootTime: Fri Jul 20 17:46:48 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ubuntu upgrade-software-version wayland-session ** Description changed: Hello, https://www.mesa3d.org/relnotes/18.2.2.html Bug fixes - Bug 104602 - [apitrace] Graphical artifacts in Civilization VI on RX Vega - Bug 104926 - swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported - Bug 107276 - radv: OpBitfieldUExtract returns incorrect result when count is zero - Bug 107786 - [DXVK] MSAA reflections are broken in GTA V - Bug 108024 - [Debian Stretch]Fail to build because "xcb_randr_lease_t" + - [apitrace] Graphical artifacts in Civilization VI on RX Vega + - swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported + - radv: OpBitfieldUExtract returns incorrect result when count is zero + - [DXVK] MSAA reflections are broken in GTA V + - [Debian Stretch]Fail to build because "xcb_randr_lease_t" Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglapi-mesa 18.2.1-1ubuntu1 Uname: Linux 4.18.12-gnu x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 13:45:21 2018 Dependencies: - gcc-8-base 8.2.0-7ubuntu1 - libc6 2.28-0ubuntu1 - libgcc1 1:8.2.0-7ubuntu1 - libidn2-0 2.0.5-1 - libunistring2 0.9.10-1ubuntu1 + gcc-8-base 8.2.0-7ubuntu1 + libc6 2.28-0ubuntu1 + libgcc1 1:8.2.0-7ubuntu1 + libidn2-0 2.0.5-1 + libunistring2 0.9.10-1u
[Touch-packages] [Bug 1796367] Re: New release of 'mesa' (18.2.2)
** Summary changed: - New release of 'mesa3d' (18.2.2) + New release of 'mesa' (18.2.2) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1796367 Title: New release of 'mesa' (18.2.2) Status in mesa package in Ubuntu: New Bug description: Hello, https://www.mesa3d.org/relnotes/18.2.2.html Bug fixes - [apitrace] Graphical artifacts in Civilization VI on RX Vega - swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported - radv: OpBitfieldUExtract returns incorrect result when count is zero - [DXVK] MSAA reflections are broken in GTA V - [Debian Stretch]Fail to build because "xcb_randr_lease_t" Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglapi-mesa 18.2.1-1ubuntu1 Uname: Linux 4.18.12-gnu x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 13:45:21 2018 Dependencies: gcc-8-base 8.2.0-7ubuntu1 libc6 2.28-0ubuntu1 libgcc1 1:8.2.0-7ubuntu1 libidn2-0 2.0.5-1 libunistring2 0.9.10-1ubuntu1 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.18.0-8-generic, x86_64: installed virtualbox, 5.2.18, 4.18.12-gnu, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0d7] InstallationDate: Installed on 2017-10-13 (357 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.12-gnu root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 xserver.bootTime: Fri Jul 20 17:46:48 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1796367/+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 1796375] [NEW] package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2
Public bug reported: slows computer ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Sun Sep 30 11:40:26 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2013-12-13 (1757 days ago) InstallationMedia: This Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-10-01 (4 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic third-party-packages -- 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/1796375 Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 Status in systemd package in Ubuntu: New Bug description: slows computer ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Sun Sep 30 11:40:26 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2013-12-13 (1757 days ago) InstallationMedia: This Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-10-01 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796375/+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 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
@VascoT: Delete the configuration and reconnect to the wifi doing the configuration from fresh. -- 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/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+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 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
Indeed, sorry about that, I overlooked that this was on a bond and tested with a bridge instead. Here are the results with a bond: $ cat /etc/netplan/50-cloud-init.yaml network: version: 2 ethernets: eth0: dhcp4: false bonds: bond0: interfaces: [eth0] dhcp4: yes addresses: ["fe81::32a5:bc5f:287f:8db8/64"] $ ip addr show dev bond0 2: bond0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether a2:83:94:5d:cc:de brd ff:ff:ff:ff:ff:ff inet 10.141.225.183/24 brd 10.141.225.255 scope global dynamic bond0 valid_lft 3540sec preferred_lft 3540sec inet6 fe81::32a5:bc5f:287f:8db8/64 scope link valid_lft forever preferred_lft forever inet6 fe80::a083:94ff:fe5d:ccde/64 scope link valid_lft forever preferred_lft forever $ Again, the dhcp4 address and the static ipv6 address are both present. -- 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/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Incomplete Status in network-manager package in Ubuntu: Incomplete Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package need to be assigned...! To manage notifications about th
[Touch-packages] [Bug 1796379] Re: dumpe2fs crashed with SIGSEGV in e2p_is_null_uuid()
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1796379 Title: dumpe2fs crashed with SIGSEGV in e2p_is_null_uuid() Status in e2fsprogs package in Ubuntu: New Bug description: when using gnome control center (no idea, if related) ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: e2fsprogs 1.44.4-2 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 Date: Fri Oct 5 19:27:27 2018 ExecutablePath: /sbin/dumpe2fs InstallationDate: Installed on 2018-10-05 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181004) ProcCmdline: dumpe2fs -h /dev/sdc1 SegvAnalysis: Segfault happened at: 0x7fa1b9836ffc : cmpb $0x0,-0x1(%rdi) PC (0x7fa1b9836ffc) ok source "$0x0" ok destination "-0x1(%rdi)" (0x7ffcdb8f3000) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: e2fsprogs StacktraceTop: e2p_is_null_uuid () from /lib/x86_64-linux-gnu/libe2p.so.2 e2p_uuid2str () from /lib/x86_64-linux-gnu/libe2p.so.2 e2p_list_journal_super () from /lib/x86_64-linux-gnu/libe2p.so.2 ?? () ?? () Title: dumpe2fs crashed with SIGSEGV in e2p_is_null_uuid() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1796379/+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 1576353] Re: Install openssh-server with disabled password auth by default on servers
See the comment on the linked debian-cd MP from Marc Deslauriers. Note that the goal of removing the cloud-image seed is still entirely reasonable and doable, openssh-server should just move to livecd-rootfs as something always added to cloud images. Done and done. There's no reason that one package needs to be represented in a seed/task any more than custom kernels or cloud agents are. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1576353 Title: Install openssh-server with disabled password auth by default on servers Status in Ubuntu CD Images: In Progress Status in livecd-rootfs package in Ubuntu: New Status in openssh package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: New Bug description: we want to remove 'cloud-image' seed and join it with 'server' seed. openssh-server is one of the few (3) packages that are in cloud image and not in 'ubuntu-server'. We'd like to have the server iso install openssh-server by default and prompt the user if they want to enable it or not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1576353/+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 1576353] Re: Install openssh-server with disabled password auth by default on servers
This is won't fix at the moment, please see comments at https://code.launchpad.net/~vorlon/debian-cd/lp.1576353/+merge/348112 ** Changed in: livecd-rootfs (Ubuntu) Status: New => Won't Fix ** Changed in: ubuntu-meta (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1576353 Title: Install openssh-server with disabled password auth by default on servers Status in Ubuntu CD Images: Won't Fix Status in livecd-rootfs package in Ubuntu: Won't Fix Status in openssh package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Won't Fix Bug description: we want to remove 'cloud-image' seed and join it with 'server' seed. openssh-server is one of the few (3) packages that are in cloud image and not in 'ubuntu-server'. We'd like to have the server iso install openssh-server by default and prompt the user if they want to enable it or not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1576353/+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 1576353] Re: Install openssh-server with disabled password auth by default on servers
** Changed in: ubuntu-cdimage Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1576353 Title: Install openssh-server with disabled password auth by default on servers Status in Ubuntu CD Images: Won't Fix Status in livecd-rootfs package in Ubuntu: Won't Fix Status in openssh package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Won't Fix Bug description: we want to remove 'cloud-image' seed and join it with 'server' seed. openssh-server is one of the few (3) packages that are in cloud image and not in 'ubuntu-server'. We'd like to have the server iso install openssh-server by default and prompt the user if they want to enable it or not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1576353/+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 1796379] Re: dumpe2fs crashed with SIGSEGV in e2p_is_null_uuid()
This is almost certainly fixed via this patch: https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?h=maint&id=b0ec76d623f737a32abc5ab8bb7198bf1d9939a4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1796379 Title: dumpe2fs crashed with SIGSEGV in e2p_is_null_uuid() Status in e2fsprogs package in Ubuntu: New Bug description: when using gnome control center (no idea, if related) ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: e2fsprogs 1.44.4-2 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 Date: Fri Oct 5 19:27:27 2018 ExecutablePath: /sbin/dumpe2fs InstallationDate: Installed on 2018-10-05 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181004) ProcCmdline: dumpe2fs -h /dev/sdc1 SegvAnalysis: Segfault happened at: 0x7fa1b9836ffc : cmpb $0x0,-0x1(%rdi) PC (0x7fa1b9836ffc) ok source "$0x0" ok destination "-0x1(%rdi)" (0x7ffcdb8f3000) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: e2fsprogs StacktraceTop: e2p_is_null_uuid () from /lib/x86_64-linux-gnu/libe2p.so.2 e2p_uuid2str () from /lib/x86_64-linux-gnu/libe2p.so.2 e2p_list_journal_super () from /lib/x86_64-linux-gnu/libe2p.so.2 ?? () ?? () Title: dumpe2fs crashed with SIGSEGV in e2p_is_null_uuid() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1796379/+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 1749728] Re: Installing packages fails when launched via Firefox ("open with")
any news on this bug ? very annoying
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/1749728
Title:
Installing packages fails when launched via Firefox ("open with")
Status in gdebi package in Ubuntu:
Confirmed
Bug description:
When launched from Firefox with the "open with" function, GDebi is
unable to complete installing the package. The GDebi window does open,
but after selecting to "install" the package the window closes and the
package is left uninstalled.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdebi 0.9.5.7+nmu2
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Feb 15 17:08:31 2018
InstallationDate: Installed on 2018-02-15 (0 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64
(20180215)
PackageArchitecture: all
SourcePackage: gdebi
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1749728/+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 1795913] Re: Systemd Resolver works unreliable to local DNS Names
After some more digging I found this behavior roots from the DNS Resolver running on the Router (a Turris Omnia) Local hosts get a name xxx.home.example.com from fixed DHCP leases and the knot resolver (kresd) on the Turris responds with the local IPv4 Address for this hosts. Queries for IPv6 Addresses of xxx.home.example.com get a NXDOMAIN response from kresd. systemd-resolved queries for A and records, the A request gets used and the subsequent NXDOMAIN responce leads to a cache flush and a negative caching for the name. After tracking down the behavior a workaround in the turris kresd configuration was proposed (https://github.com/CZ-NIC/turris-os- packages/commit/42da887f8165dccc374c73c3ed9e024fba7b0c3e). This fixed my problem. Thanks, this bug can be closed, the source is not in systemd -- 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/1795913 Title: Systemd Resolver works unreliable to local DNS Names Status in systemd package in Ubuntu: New Bug description: systemd-resolved fails to resolve reliably local DNS names under home.example.com. The first call succeeds but all following calls fails to resolve the address correctly: steve@steve-ThinkPad-T560:~$ systemd-resolve --flush-caches steve@steve-ThinkPad-T560:~$ systemd-resolve akolus.home.example.com akolus.home.example.com: 192.168.1.5 -- Information acquired via protocol DNS in 2.7ms. -- Data is authenticated: no steve@steve-ThinkPad-T560:~$ systemd-resolve akolus.home.example.com akolus.home.example.com: resolve call failed: 'akolus.home.example.com' not found A call to systemd-resolve --flush-caches get the next resolvement working again. The syslog show following entries Oct 3 16:44:41 steve-ThinkPad-T560 systemd-resolved[1092]: Flushed all caches. Oct 3 16:44:41 steve-ThinkPad-T560 systemd-resolved[1092]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. A dig for the adresses to all DHCP provided DNS Server works: steve@steve-ThinkPad-T560:~$ dig akolus.home.example.com @192.168.1.1 ; <<>> DiG 9.11.3-1ubuntu1.2-Ubuntu <<>> akolus.home.example.com @192.168.1.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61886 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;akolus.home.example.com. IN A ;; ANSWER SECTION: akolus.home.example.com. 0IN A 192.168.1.5 ;; Query time: 0 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Wed Oct 03 16:46:30 CEST 2018 ;; MSG SIZE rcvd: 70 steve@steve-ThinkPad-T560:~$ dig akolus.home.example.com @2a04:4540:4707:a800::1 ; <<>> DiG 9.11.3-1ubuntu1.2-Ubuntu <<>> akolus.home.example.com @2a04:4540:4707:a800::1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24202 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;akolus.home.example.com. IN A ;; ANSWER SECTION: akolus.home.example.com. 0IN A 192.168.1.5 ;; Query time: 0 msec ;; SERVER: 2a04:4540:4707:a800::1#53(2a04:4540:4707:a800::1) ;; WHEN: Wed Oct 03 16:46:33 CEST 2018 ;; MSG SIZE rcvd: 70 steve@steve-ThinkPad-T560:~$ dig akolus.home.example.com @fd9c:9819:4c58::1 ; <<>> DiG 9.11.3-1ubuntu1.2-Ubuntu <<>> akolus.home.example.com @fd9c:9819:4c58::1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9783 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;akolus.home.example.com. IN A ;; ANSWER SECTION: akolus.home.example.com. 0IN A 192.168.1.5 ;; Query time: 0 msec ;; SERVER: fd9c:9819:4c58::1#53(fd9c:9819:4c58::1) ;; WHEN: Wed Oct 03 16:46:38 CEST 2018 ;; MSG SIZE rcvd: 70 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Wed Oct 3 15:56:44 2018 InstallationDate: Installed on 2018-03-05 (212 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305) MachineType: LENOVO 20FH002RGE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Sourc
[Touch-packages] [Bug 1796438] [NEW] cryptsetup-initramfs: error message is displayed at initramfs stage when cryptsetup is not included to the initrd
You have been subscribed to a public bug: In ubuntu 18.10, error message is displayed at initramfs stage when cryptsetup is not included to the initrd. vmware@ubuntu-18.10:~$ sudo update-initramfs -u [sudo] password for vmware: update-initramfs: Generating /boot/initrd.img-4.18.0-8-generic cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries nor crypto modules. If that's on purpose, you may want to uninstall the 'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs integration and avoid this warning. rmdir: failed to remove '/var/tmp/mkinitramfs_mxUIaj/var/cache/ldconfig': No such file or directory vmware@ubuntu-1810:~$ There is a bug in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901830 ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- cryptsetup-initramfs: error message is displayed at initramfs stage when cryptsetup is not included to the initrd https://bugs.launchpad.net/bugs/1796438 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. -- 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 1796438] [NEW] cryptsetup-initramfs: error message is displayed at initramfs stage when cryptsetup is not included to the initrd
Public bug reported: In ubuntu 18.10, error message is displayed at initramfs stage when cryptsetup is not included to the initrd. vmware@ubuntu-18.10:~$ sudo update-initramfs -u [sudo] password for vmware: update-initramfs: Generating /boot/initrd.img-4.18.0-8-generic cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries nor crypto modules. If that's on purpose, you may want to uninstall the 'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs integration and avoid this warning. rmdir: failed to remove '/var/tmp/mkinitramfs_mxUIaj/var/cache/ldconfig': No such file or directory vmware@ubuntu-1810:~$ There is a bug in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901830 ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Package changed: cloud-init (Ubuntu) => initramfs-tools (Ubuntu) -- 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/1796438 Title: cryptsetup-initramfs: error message is displayed at initramfs stage when cryptsetup is not included to the initrd Status in initramfs-tools package in Ubuntu: New Bug description: In ubuntu 18.10, error message is displayed at initramfs stage when cryptsetup is not included to the initrd. vmware@ubuntu-18.10:~$ sudo update-initramfs -u [sudo] password for vmware: update-initramfs: Generating /boot/initrd.img-4.18.0-8-generic cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries nor crypto modules. If that's on purpose, you may want to uninstall the 'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs integration and avoid this warning. rmdir: failed to remove '/var/tmp/mkinitramfs_mxUIaj/var/cache/ldconfig': No such file or directory vmware@ubuntu-1810:~$ There is a bug in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1796438/+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 1796441] Re: upstart /etc/init/lightdm.conf exists but unsed since since 16.04
Bug exists in 16.04...18.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1796441 Title: upstart /etc/init/lightdm.conf exists but unsed since since 16.04 Status in lightdm package in Ubuntu: New Bug description: Since xenial (16.04), systemd is init and services are launched via systemd .service files. I found that lightdm.service files available, installed and used to launch it. However, I found legacy upstart /etc/init/lightdm.conf since 16.04. Since, upstart is not used to launch lightdm, this config is redundant and should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1796441/+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 1796441] [NEW] upstart /etc/init/lightdm.conf exists but unsed since since 16.04
Public bug reported: Since xenial (16.04), systemd is init and services are launched via systemd .service files. I found that lightdm.service files available, installed and used to launch it. However, I found legacy upstart /etc/init/lightdm.conf since 16.04. Since, upstart is not used to launch lightdm, this config is redundant and should be removed. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1796441 Title: upstart /etc/init/lightdm.conf exists but unsed since since 16.04 Status in lightdm package in Ubuntu: New Bug description: Since xenial (16.04), systemd is init and services are launched via systemd .service files. I found that lightdm.service files available, installed and used to launch it. However, I found legacy upstart /etc/init/lightdm.conf since 16.04. Since, upstart is not used to launch lightdm, this config is redundant and should be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1796441/+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 1764827] Re: sometimes, maybe after pluging in headphones, there is no sound. Sound goes thrue , , dummy output''
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1764827 Title: sometimes, maybe after pluging in headphones, there is no sound. Sound goes thrue ,,dummy output'' Status in pulseaudio package in Ubuntu: Expired Bug description: No sound. Sound goes to dummy output ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lukasbirstonas 1259 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Apr 17 21:25:57 2018 InstallationDate: Installed on 2017-12-02 (136 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Title: [20CD0034UK, Conexant CX20751/2, Green Headphone Out, Front] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GQET35WW (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CD0034UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50518 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGQET35WW(1.15):bd04/21/2014:svnLENOVO:pn20CD0034UK:pvrThinkPadS1Yoga:rvnLENOVO:rn20CD0034UK:rvrSDK0E50518Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad S1 Yoga dmi.product.name: 20CD0034UK dmi.product.version: ThinkPad S1 Yoga dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1764827/+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 1755326] Re: Periodic glitch in sound with Firewire and snd-dice
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1755326 Title: Periodic glitch in sound with Firewire and snd-dice Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: I have a fresh installation of Ubuntu 17.10 with almost nothing extra installed yet besides Bitwig Studio, Cadence and a few other things from the KX Studio repositories. But I also tried the bug after a fresh install with nothing else than Bitwig Studio installed, it's the same. Not sure if this information can be added afterwards: but I installed the 3.19.8 low latency kernel, and the problem disappeared. On 17.1 I can't use the current low latency kernel because the system becomes very unresponsive to the point of being hard to even log in. So I'm not sure if this is just a matter of difference between the low latency and regular kernels. I have a TC Electronics Impact Twin Firewire audio interface. It is connected to a Iocrest SY-PEX30016 PCI-E card, which has a Texas Instruments XIO2213BZAY chipset. The ALSA snd-dice drivers work, but with glitches. There is a periodic, glitch in the sound that sounds like a part of the stream is missing, or something. It is steady in timing, nothing seems to have an effect on it. Recording seems to work. All outputs and inputs, also the ADAT outputs seem to work, altough I could not test if the ADAT outputs feature the glitch too. Seemingly randomly there might be a short maybe around 0.3 second total break in the sound. I'm not getting xruns at all. I tried also Ubuntu Studio live USB, it has the exact same glitch. I also tried a Native Instruments Audio2DJ USB interface, with that there is no problem with the sound on my computer. I tried also with Carla and ZynAddSubFx, and also with the live USB of Linux Mint (current version), and the same glitch is present. I tried also another Firewire controller card with a XIO2200A Texas Instruments chip, it features the same glitch, but running a different speed. I had a KX Studio 14.x installation a few years ago, where the interface was working without a hitch. But then I was running with FFADO. So to me it seems that the kernel integration of snd-dice has some problem with timing with a TC Electronics interface? I could not get FFADO to run with Jack now so I can't say if the FFADO implementation would work. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC4D0c: kim3563 F...m jackdbus /dev/snd/pcmC4D0p: kim3563 F...m jackdbus /dev/snd/controlC4: kim3563 F jackdbus CurrentDesktop: ubuntu:GNOME Date: Tue Mar 13 02:11:51 2018 InstallationDate: Installed on 2018-03-12 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd02/12/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/hwC3D0', '/dev/snd/midiC3D0', '/dev/snd/pcmC3D0c', '/dev/snd/pcmC3D0p', '/dev/snd/controlC3', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/midiC2D0', '/dev/snd/controlC2', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 Hibe
[Touch-packages] [Bug 1758569] Re: can't switch to bluetooth speakers
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1758569 Title: can't switch to bluetooth speakers Status in firefox package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: I'm not really sure this problem is with bluez, pulseaudio or firefox. The main symptom is that Firefox refuses to send audio to my AD2P compliant bluetooth speakers. I can select the speakers with the gnome-control-center for bluetooth and play the test sounds (even while FF is playing sound through the computer (DELL N7010 laptop) speakers. Even VLC has the same problem so I suspect this is a system problem and not an application problem. Note - I installed pavucontrol and was able to switch the audio of a playing youtube to the bluetooth speakers. now for your recommended info lsb_release says Ubuntu 17.10 Firefox is Version 59.0.1 dpkg -l | grep -i blue says ii bluez 5.46-0ubuntu3 amd64 Bluetooth tools and daemons ii bluez-cups 5.46-0ubuntu3 amd64 Bluetooth printer driver for CUPS ii bluez-obexd 5.46-0ubuntu3 amd64 bluez obex daemon ii bluez-tools 0.2.0~20140808-5build1 amd64 Set of tools to manage Bluetooth devices for linux ii gir1.2-gnomebluetooth-1.0:amd64 3.26.1-1 amd64 Introspection data for GnomeBluetooth ii gnome-bluetooth 3.26.1-1 amd64 GNOME Bluetooth tools ii libbluetooth3:amd64 5.46-0ubuntu3 amd64 Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth13:amd64 3.26.1-1 amd64 GNOME Bluetooth tools - support library ii pulseaudio-module-bluetooth 1:10.0-2ubuntu3.1 amd64 Bluetooth module for PulseAudio sound server ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluez 5.46-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 14:10:02 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-19 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron N7010 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=94a7c54a-20a6-4bd0-905c-918de9b5ff61 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08VFX1 dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd03/31/2011:svnDellInc.:pnInspironN7010:pvrA11:rvnDellInc.:rn08VFX1:rvrA11:cvnDellInc.:ct8:cvrA11: dmi.product.name: Inspiron N7010 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: C0:CB:38:C2:18:51 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING INQUIRY RX bytes:234685 acl:43 sco:0 events:33407 errors:0 TX bytes:56372584 acl:66043 sco:0 commands:212 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1758569/+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 1758569] Re: can't switch to bluetooth speakers
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1758569 Title: can't switch to bluetooth speakers Status in firefox package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: I'm not really sure this problem is with bluez, pulseaudio or firefox. The main symptom is that Firefox refuses to send audio to my AD2P compliant bluetooth speakers. I can select the speakers with the gnome-control-center for bluetooth and play the test sounds (even while FF is playing sound through the computer (DELL N7010 laptop) speakers. Even VLC has the same problem so I suspect this is a system problem and not an application problem. Note - I installed pavucontrol and was able to switch the audio of a playing youtube to the bluetooth speakers. now for your recommended info lsb_release says Ubuntu 17.10 Firefox is Version 59.0.1 dpkg -l | grep -i blue says ii bluez 5.46-0ubuntu3 amd64 Bluetooth tools and daemons ii bluez-cups 5.46-0ubuntu3 amd64 Bluetooth printer driver for CUPS ii bluez-obexd 5.46-0ubuntu3 amd64 bluez obex daemon ii bluez-tools 0.2.0~20140808-5build1 amd64 Set of tools to manage Bluetooth devices for linux ii gir1.2-gnomebluetooth-1.0:amd64 3.26.1-1 amd64 Introspection data for GnomeBluetooth ii gnome-bluetooth 3.26.1-1 amd64 GNOME Bluetooth tools ii libbluetooth3:amd64 5.46-0ubuntu3 amd64 Library to use the BlueZ Linux Bluetooth stack ii libgnome-bluetooth13:amd64 3.26.1-1 amd64 GNOME Bluetooth tools - support library ii pulseaudio-module-bluetooth 1:10.0-2ubuntu3.1 amd64 Bluetooth module for PulseAudio sound server ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluez 5.46-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 14:10:02 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-03-19 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron N7010 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=94a7c54a-20a6-4bd0-905c-918de9b5ff61 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 08VFX1 dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd03/31/2011:svnDellInc.:pnInspironN7010:pvrA11:rvnDellInc.:rn08VFX1:rvrA11:cvnDellInc.:ct8:cvrA11: dmi.product.name: Inspiron N7010 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: C0:CB:38:C2:18:51 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING INQUIRY RX bytes:234685 acl:43 sco:0 events:33407 errors:0 TX bytes:56372584 acl:66043 sco:0 commands:212 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1758569/+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 1755326] Re: Periodic glitch in sound with Firewire and snd-dice
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1755326 Title: Periodic glitch in sound with Firewire and snd-dice Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: I have a fresh installation of Ubuntu 17.10 with almost nothing extra installed yet besides Bitwig Studio, Cadence and a few other things from the KX Studio repositories. But I also tried the bug after a fresh install with nothing else than Bitwig Studio installed, it's the same. Not sure if this information can be added afterwards: but I installed the 3.19.8 low latency kernel, and the problem disappeared. On 17.1 I can't use the current low latency kernel because the system becomes very unresponsive to the point of being hard to even log in. So I'm not sure if this is just a matter of difference between the low latency and regular kernels. I have a TC Electronics Impact Twin Firewire audio interface. It is connected to a Iocrest SY-PEX30016 PCI-E card, which has a Texas Instruments XIO2213BZAY chipset. The ALSA snd-dice drivers work, but with glitches. There is a periodic, glitch in the sound that sounds like a part of the stream is missing, or something. It is steady in timing, nothing seems to have an effect on it. Recording seems to work. All outputs and inputs, also the ADAT outputs seem to work, altough I could not test if the ADAT outputs feature the glitch too. Seemingly randomly there might be a short maybe around 0.3 second total break in the sound. I'm not getting xruns at all. I tried also Ubuntu Studio live USB, it has the exact same glitch. I also tried a Native Instruments Audio2DJ USB interface, with that there is no problem with the sound on my computer. I tried also with Carla and ZynAddSubFx, and also with the live USB of Linux Mint (current version), and the same glitch is present. I tried also another Firewire controller card with a XIO2200A Texas Instruments chip, it features the same glitch, but running a different speed. I had a KX Studio 14.x installation a few years ago, where the interface was working without a hitch. But then I was running with FFADO. So to me it seems that the kernel integration of snd-dice has some problem with timing with a TC Electronics interface? I could not get FFADO to run with Jack now so I can't say if the FFADO implementation would work. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC4D0c: kim3563 F...m jackdbus /dev/snd/pcmC4D0p: kim3563 F...m jackdbus /dev/snd/controlC4: kim3563 F jackdbus CurrentDesktop: ubuntu:GNOME Date: Tue Mar 13 02:11:51 2018 InstallationDate: Installed on 2018-03-12 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd02/12/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVOR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/hwC3D0', '/dev/snd/midiC3D0', '/dev/snd/pcmC3D0c', '/dev/snd/pcmC3D0p', '/dev/snd/controlC3', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/midiC2D0', '/dev/snd/controlC2', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17
[Touch-packages] [Bug 1726122] Re: HDA VT2020 missing in pulseaudio sound settings
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1726122 Title: HDA VT2020 missing in pulseaudio sound settings Status in pulseaudio package in Ubuntu: Expired Bug description: Description: Ubuntu 17.10 Release: 17.10 pulseaudio 1:10.0-2ubun amd64 Have an analog VT2020 HDA device as primary card and the HDMI digital pitcairn sound card in the system. Bug: The pulseaudio settings in the panel do only list the pitcairn device. @athena:~$ sudo aplay -l [sudo] Passwort für : Liste der Hardware-Geräte (PLAYBACK) Karte 0: SB [HDA ATI SB], Gerät 0: VT2020 Analog [VT2020 Analog] Sub-Geräte: 0/1 Sub-Gerät #0: subdevice #0 Karte 0: SB [HDA ATI SB], Gerät 1: VT2020 Digital [VT2020 Digital] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 0: SB [HDA ATI SB], Gerät 2: VT2020 Alt Analog [VT2020 Alt Analog] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: HDMI [HDA ATI HDMI], Gerät 3: HDMI 0 [HDMI 0] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: HDMI [HDA ATI HDMI], Gerät 7: HDMI 1 [HDMI 1] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: HDMI [HDA ATI HDMI], Gerät 8: HDMI 2 [HDMI 2] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: HDMI [HDA ATI HDMI], Gerät 9: HDMI 3 [HDMI 3] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: HDMI [HDA ATI HDMI], Gerät 10: HDMI 4 [HDMI 4] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: HDMI [HDA ATI HDMI], Gerät 11: HDMI 5 [HDMI 5] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Both devices are recognized by alsa, kernel modules are loaded. Temporary bugfix: Installed pavucontrol, it shows the analog VT2020. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: eric 1598 F...m pulseaudio /dev/snd/controlC0: eric 1598 F pulseaudio /dev/snd/controlC1: eric 1598 F pulseaudio CurrentDesktop: X-Cinnamon Date: Sun Oct 22 21:05:19 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-22 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2g dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2g:bd10/07/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1726122/+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 1728385] Re: Reduce/hide excessive logging when Bluetooth is intentionally disabled: "Failed to set mode: Blocked through rfkill (0x12)"
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- 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/1728385 Title: Reduce/hide excessive logging when Bluetooth is intentionally disabled: "Failed to set mode: Blocked through rfkill (0x12)" Status in bluez package in Ubuntu: Expired Bug description: Ubuntu 17.10, bluetooth disabled, get error in Logs: bluetoothd: Failed to set mode: Blocked through rfkill (0x12) --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-24 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20GJ001HMH Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R0CET26W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20GJ001HMH dmi.board.vendor: LENOVO dmi.board.version: S dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0CET26W(1.14):bd06/13/2016:svnLENOVO:pn20GJ001HMH:pvrThinkPadS2:rvnLENOVO:rn20GJ001HMH:rvrS:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad S2 dmi.product.name: 20GJ001HMH dmi.product.version: ThinkPad S2 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:B3:18:52:20:69 ACL MTU: 1021:4 SCO MTU: 96:6 DOWN RX bytes:14933 acl:0 sco:0 events:2414 errors:0 TX bytes:596764 acl:0 sco:0 commands:2412 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1728385/+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 1726929] Re: pulseaudio crashed with SIGABRT in __GI_____strtof128_l_internal()
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1726929 Title: pulseaudio crashed with SIGABRT in __GI_strtof128_l_internal() Status in pulseaudio package in Ubuntu: Expired Bug description: In sound panel, the analog output keeps appearing/disappearing for a minute or so. Then this crash occurs. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: henklaak F...m firefox /dev/snd/controlC0: henklaak F firefox henklaak 6370 F alsamixer /dev/snd/timer: henklaak f firefox CrashCounter: 1 CurrentDesktop: Unity:Unity7 Date: Tue Oct 24 18:07:04 2017 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-04-25 (547 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_sink_input_finish_move () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so pa_sink_move_all_finish () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so pa_card_set_profile () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so ?? () from /usr/lib/pulse-10.0/modules/module-switch-on-port-available.so Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move() UpgradeStatus: Upgraded to artful on 2017-10-19 (4 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sudo dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1708 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH Z77 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1708:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ77:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1726929/+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 1733667] Re: Bluetooth doesn't (usually) work on booting [MacBookPro12, 1]
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- 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/1733667 Title: Bluetooth doesn't (usually) work on booting [MacBookPro12,1] Status in bluez package in Ubuntu: Expired Bug description: $ uname -a Linux mbpr13b 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Just updated to latest repo kernel. After reboot, the bluetoothd gets started but not activated. Restarting does not work (error msg in bluetooth panel: adapter not found - it was there before the reboot). Required several reboots to fix the issue (i.e. after a reboot I have to reboot several times, click the mouse frantically during boot to get it recognized somewhere during the bootup). I remember this to have happened two kernels before so I think it is a regression. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluez 5.46-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 21 18:58:04 2017 InstallationDate: Installed on 2017-10-20 (32 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-17-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:32:75:9F:91:1E ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:28328 acl:854 sco:0 events:231 errors:0 TX bytes:6881 acl:65 sco:0 commands:121 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1733667/+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 1737326] Re: Cannot use internal sound devices on Asus e200HA
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1737326 Title: Cannot use internal sound devices on Asus e200HA Status in pulseaudio package in Ubuntu: Expired Bug description: Processor recognized but plays no sound when selected. External sound devices are the only way to play sound on my computer. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jamie 1733 F pulseaudio /dev/snd/controlC0: jamie 1733 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 9 14:58:06 2017 InstallationDate: Installed on 2017-12-01 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA 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.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.300:bd06/01/2016:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: E dmi.product.name: E200HA 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/pulseaudio/+bug/1737326/+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 1730419] Re: Audio does not auto-switch to Bluetooth speaker "JBL! GO" when it is turned on
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1730419 Title: Audio does not auto-switch to Bluetooth speaker "JBL! GO" when it is turned on Status in pulseaudio package in Ubuntu: Expired Bug description: No automatically switch to Bluetooth speaker device. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-20 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Package: gnome-bluetooth 3.26.1-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1730419/+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 1716127] Re: Audio streaming over bluetooth to Bose QC35 is highly unreliable on a MacBookPro12, 1
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- 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/1716127 Title: Audio streaming over bluetooth to Bose QC35 is highly unreliable on a MacBookPro12,1 Status in bluez package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Streaming of audio files over bluetooth is not possible in Ubuntu 17.10. Connecting a headphone requires several attempts. Then the sound settings have to be selected manually Even then, the sound offered is mono I tested with a Bose QC35. There is a sound profile that requires manual selection and offers stereo speakers. However, while testing left speaker gives reasonable results, testing the right speaker only produces cracking noise. Playback of music is virtually impossible (the stream is repeatedly interupted by voice anouncements of incoming calls ??? and reconnection attemts) To eliminate hardware issues I tested under macOS and the sound quality is excellent (even during working in a spread sheet and a word processor in parallel). => issues caused by the software stack ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluez 5.46-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 9 15:12:02 2017 InstallationDate: Installed on 2017-09-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05ac:0273 Apple, Inc. Bus 001 Device 003: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:32:75:9F:91:1E ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1558111 acl:54896 sco:0 events:1375 errors:0 TX bytes:1129512 acl:1895 sco:5 commands:247 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1716127/+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 1716127] Re: Audio streaming over bluetooth to Bose QC35 is highly unreliable on a MacBookPro12, 1
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1716127 Title: Audio streaming over bluetooth to Bose QC35 is highly unreliable on a MacBookPro12,1 Status in bluez package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Streaming of audio files over bluetooth is not possible in Ubuntu 17.10. Connecting a headphone requires several attempts. Then the sound settings have to be selected manually Even then, the sound offered is mono I tested with a Bose QC35. There is a sound profile that requires manual selection and offers stereo speakers. However, while testing left speaker gives reasonable results, testing the right speaker only produces cracking noise. Playback of music is virtually impossible (the stream is repeatedly interupted by voice anouncements of incoming calls ??? and reconnection attemts) To eliminate hardware issues I tested under macOS and the sound quality is excellent (even during working in a spread sheet and a word processor in parallel). => issues caused by the software stack ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluez 5.46-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 9 15:12:02 2017 InstallationDate: Installed on 2017-09-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05ac:0273 Apple, Inc. Bus 001 Device 003: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B33.1706181928 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:32:75:9F:91:1E ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1558111 acl:54896 sco:0 events:1375 errors:0 TX bytes:1129512 acl:1895 sco:5 commands:247 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1716127/+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 1712529] Re: pulseaudio crashed with SIGABRT in pa_source_output_attach()
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1712529 Title: pulseaudio crashed with SIGABRT in pa_source_output_attach() Status in pulseaudio package in Ubuntu: Expired Bug description: Just upgraded packages in 17.10 dev and rebooted and this crash popped out. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shemgp15659 F pulseaudio CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Aug 23 17:02:31 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2015-09-28 (694 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_source_output_attach () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so pa_source_attach_within_thread () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so ?? () from /usr/lib/pulse-10.0/modules/module-echo-cancel.so pa_source_process_msg () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so ?? () from /usr/lib/pulse-10.0/modules/libalsa-util.so Title: pulseaudio crashed with SIGABRT in pa_source_output_attach() UpgradeStatus: Upgraded to artful on 2017-08-12 (10 days ago) UserGroups: adm cdrom dip docker fuse kismet libvirt libvirtd lp lpadmin lxd mail mythtv netdev plugdev sambashare sbuild scanner sudo video dmi.bios.date: 09/24/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GCETA3WW (2.63 ) dmi.board.asset.tag: Not Available dmi.board.name: 34361A0 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCETA3WW(2.63):bd09/24/2015:svnLENOVO:pn34361A0:pvrThinkPadX220:rvnLENOVO:rn34361A0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X220 dmi.product.name: 34361A0 dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1712529/+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 1726074] Re: pulseaudio crashed with SIGSEGV in pa_mcalign_csize() from pa_memblockq_push_align()
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1726074 Title: pulseaudio crashed with SIGSEGV in pa_mcalign_csize() from pa_memblockq_push_align() Status in pulseaudio package in Ubuntu: Expired Bug description: No action by user - listening to Pandora in Chromium while working in LibreOffice. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 10674 F pulseaudio /dev/snd/pcmC1D0p: mike 10674 F...m pulseaudio /dev/snd/controlC1: mike 10674 F pulseaudio CurrentDesktop: KDE Date: Sun Oct 22 12:56:26 2017 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: pulseaudio StacktraceTop: pa_mcalign_csize () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so pa_memblockq_push_align () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so pa_sink_input_peek () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so pa_sink_render_into () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so Title: pulseaudio crashed with SIGSEGV in pa_mcalign_csize() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare sudo dmi.bios.date: 04/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: AB350M-Gaming 3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd04/07/2017:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350M-Gaming 3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1726074/+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 1708774] Re: bluetoothd crashed with SIGSEGV in _dbus_header_get_message_type() from _dbus_message_has_type_interface_member() from browse_request_complete() from device_svc_reso
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- 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/1708774 Title: bluetoothd crashed with SIGSEGV in _dbus_header_get_message_type() from _dbus_message_has_type_interface_member() from browse_request_complete() from device_svc_resolved() Status in bluez package in Ubuntu: Expired Bug description: This is happening over and over while running behind the scenes. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: bluez 5.45-0ubuntu2 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Mon Jul 31 22:44:35 2017 ExecutablePath: /usr/lib/bluetooth/bluetoothd InstallationDate: Installed on 2017-07-29 (6 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 (20170725.1) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 003: ID 05ac:0274 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,5 ProcCmdline: /usr/lib/bluetooth/bluetoothd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: initrd=\ubuntu\initrd.img-generic root=/dev/mapper/volgrp-root rw SegvAnalysis: Segfault happened at: 0x7f2b54231cf0:mov(%rdi),%rax PC (0x7f2b54231cf0) ok source "(%rdi)" (0x3130383130303038) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: bluez StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () ?? () ?? () Title: bluetoothd crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 06/18/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B25.1706181512 dmi.board.name: Mac-06F11F11946D27C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,5 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11F11946D27C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B25.1706181512:bd06/18/2017:svnAppleInc.:pnMacBookPro11,5:pvr1.0:rvnAppleInc.:rnMac-06F11F11946D27C5:rvrMacBookPro11,5:cvnAppleInc.:ct9:cvrMac-06F11F11946D27C5: dmi.product.name: MacBookPro11,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: F4:5C:89:C2:92:3C ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:1054 acl:0 sco:0 events:59 errors:0 TX bytes:2965 acl:0 sco:0 commands:59 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1708774/+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 1709163] Re: default output changes from intel builtin to hdmi when display is turned off. yes off not on
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1709163 Title: default output changes from intel builtin to hdmi when display is turned off. yes off not on Status in pulseaudio package in Ubuntu: Expired Bug description: So if I have sound output selected to be the intel sound on the mainboard and turn off one of my two displays the audio out is changed to HDMI. YES OFF it's not a typo. The Display I turn off is connected to displayport and do not even have HDMI. The audio is switched over to the still active display. If I then turn the display back it's still hdmi. If I then turn off the display that has HDMI out connected. the audio is still connected to that display. since its actually off I hear no sound but pulseaudio still connect to it. I have to manually open the GUI tool and change back to the correct output when the display is turned off or when the display is blanked. or suspend/resume. I attache the output of "pacmd list-cards && pacmd list-sinks" ok -> ps_w1.txt fail -> ps_f1.txt --- ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kenjo 3721 F pulseaudio /dev/snd/controlC1: kenjo 3721 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2015-10-18 (659 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) Package: pulseaudio 1:10.0-2ubuntu1 PackageArchitecture: amd64 Tags: artful Uname: Linux 4.12.1-041201-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-06-10 (59 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 04/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.I0 dmi.board.asset.tag: Default string dmi.board.name: Z170A GAMING M7 (MS-7976) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7976 dmi.product.version: 1.0 dmi.sys.vendor: MSI modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2016-04-23T00:00:29.066742 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1709163/+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 1705024] Re: Output to BT speaker stops when laptop is unplugged from AC
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1705024 Title: Output to BT speaker stops when laptop is unplugged from AC Status in pulseaudio package in Ubuntu: Expired Bug description: artful desktop Test Case 1. Connect a laptop to a power supply 2. Pair a BT speaker 3. Play some music with VLC 4. Disconnect the laptop from AC to switch to battery Expected result The music continues playing Actual result It stops. pavucontrol shows that the output device is still the BT speaker and the vumeter is still alive but there is not sound on the speaker. Only powering off/on the speaker makes it work again. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: j-lallement 1293 F...m pulseaudio /dev/snd/controlC1: j-lallement 1293 F pulseaudio /dev/snd/controlC0: j-lallement 1293 F pulseaudio CurrentDesktop: GNOME Date: Tue Jul 18 14:40:02 2017 InstallationDate: Installed on 2013-09-03 (1413 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD 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.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD 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/pulseaudio/+bug/1705024/+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 1705573] Re: [QY7, recording] The sound works but the microphone does not
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1705573 Title: [QY7, recording] The sound works but the microphone does not Status in pulseaudio package in Ubuntu: Expired Bug description: Using 17.10 and as requested, using the Bluetooth QY7, the microphone is not working at all. The sound works but the microphone does not, so for meeting calls, it would not work at all. Similar to this case https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1705572 where I reported another device I have. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: cyrex 1728 F pulseaudio /dev/snd/controlC3: cyrex 1728 F pulseaudio /dev/snd/controlC0: cyrex 1728 F pulseaudio /dev/snd/controlC1: cyrex 1728 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Thu Jul 20 14:47:16 2017 InstallationDate: Installed on 2017-05-18 (63 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio Symptom: audio Symptom_Card: QY7 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: cyrex 1728 F pulseaudio /dev/snd/controlC3: cyrex 1728 F pulseaudio /dev/snd/controlC0: cyrex 1728 F pulseaudio /dev/snd/controlC1: cyrex 1728 F pulseaudio Symptom_Type: No sound at all Title: [QY7, recording] No sound at all UpgradeStatus: Upgraded to artful on 2017-07-18 (1 days ago) dmi.bios.date: 01/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3401 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3401:bd01/25/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1705573/+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 1704807] Re: Audio doesn't switch automatically to Bluetooth speaker when hotplugged after application playback started
[Expired for gst-plugins-good1.0 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gst-plugins-good1.0 (Ubuntu) Status: Incomplete => Expired -- 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/1704807 Title: Audio doesn't switch automatically to Bluetooth speaker when hotplugged after application playback started Status in gst-plugins-good1.0 package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Status in totem package in Ubuntu: Expired Bug description: artful desktop Test Case. 1. Pair a BT Speaker and set the output channel to the speaker 2. Play something with vlc or totem (and make sure it uses the speaker with pavucontrol for instance) 3. Switch the output to another channel eg internal speaker and turn the BT speaker off (do not close the music player) 4. Turn the speaker back on and wait until it connects 5. If the speaker is not selected automatically as the output, select it in the sound settings 6. Resume playing in VLC Expected result The track plays on the speaker Actual result It plays on the internal audio. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 17 17:09:17 2017 InstallationDate: Installed on 2013-09-03 (1412 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD 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.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD 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/gst-plugins-good1.0/+bug/1704807/+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 1704297] Re: Bluetooth audio stuck in A2DP profile ([pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected)
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1704297 Title: Bluetooth audio stuck in A2DP profile ([pulseaudio] module- bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected) Status in pulseaudio package in Ubuntu: Expired Bug description: I've got a pair of Parot Zik bluetooth headphones, with inbuilt microphones and such. The Sound control panel offers a “Profile” dropdown, with choice of A2DP and HSP profiles, but selecting the HSP profile (a) doesn't add an input source to the “Inputs” tab, and (b) doesn't stop the headphones playing stereo sound, indicating that it hasn't actually been switched to HSP profile (which is, AFAIK, mono). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: chris 7755 F pulseaudio /dev/snd/controlC1: chris 7755 F pulseaudio /dev/snd/pcmC0D0c: chris 7755 F...m pulseaudio /dev/snd/controlC0: chris 7755 F pulseaudio CurrentDesktop: GNOME Date: Fri Jul 14 16:27:09 2017 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1704297/+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 1704807] Re: Audio doesn't switch automatically to Bluetooth speaker when hotplugged after application playback started
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1704807 Title: Audio doesn't switch automatically to Bluetooth speaker when hotplugged after application playback started Status in gst-plugins-good1.0 package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Status in totem package in Ubuntu: Expired Bug description: artful desktop Test Case. 1. Pair a BT Speaker and set the output channel to the speaker 2. Play something with vlc or totem (and make sure it uses the speaker with pavucontrol for instance) 3. Switch the output to another channel eg internal speaker and turn the BT speaker off (do not close the music player) 4. Turn the speaker back on and wait until it connects 5. If the speaker is not selected automatically as the output, select it in the sound settings 6. Resume playing in VLC Expected result The track plays on the speaker Actual result It plays on the internal audio. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 17 17:09:17 2017 InstallationDate: Installed on 2013-09-03 (1412 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD 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.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD 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/gst-plugins-good1.0/+bug/1704807/+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 1704807] Re: Audio doesn't switch automatically to Bluetooth speaker when hotplugged after application playback started
[Expired for totem (Ubuntu) because there has been no activity for 60 days.] ** Changed in: totem (Ubuntu) Status: Incomplete => Expired -- 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/1704807 Title: Audio doesn't switch automatically to Bluetooth speaker when hotplugged after application playback started Status in gst-plugins-good1.0 package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Status in totem package in Ubuntu: Expired Bug description: artful desktop Test Case. 1. Pair a BT Speaker and set the output channel to the speaker 2. Play something with vlc or totem (and make sure it uses the speaker with pavucontrol for instance) 3. Switch the output to another channel eg internal speaker and turn the BT speaker off (do not close the music player) 4. Turn the speaker back on and wait until it connects 5. If the speaker is not selected automatically as the output, select it in the sound settings 6. Resume playing in VLC Expected result The track plays on the speaker Actual result It plays on the internal audio. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 17 17:09:17 2017 InstallationDate: Installed on 2013-09-03 (1412 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD 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.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD 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/gst-plugins-good1.0/+bug/1704807/+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 1640139] Re: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1640139 Title: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 Status in One Hundred Papercuts: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 Codename: xenial # uname -a Linux rotem-laptop 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux tried removing pulseaudio ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpulse0 (not installed) ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rotemfo2383 F pulseaudio /dev/snd/controlC0: rotemfo2383 F pulseaudio Date: Tue Nov 8 12:46:09 2016 DuplicateSignature: package:libpulse0:(not installed) Unpacking libpulse0:i386 (1:8.0-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/libpulse0_1%3a8.0-0ubuntu3_i386.deb (--unpack): trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 ErrorMessage: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 InstallationDate: Installed on 2016-10-25 (14 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: error while loading shared libraries: libpulse.so.0: cannot open shared object file: No such file or directory RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: pulseaudio Title: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/17/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1640139/+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 1640139] Re: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package
[Expired for One Hundred Papercuts because there has been no activity for 60 days.] ** Changed in: hundredpapercuts Status: Incomplete => Expired -- 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/1640139 Title: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 Status in One Hundred Papercuts: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 Codename: xenial # uname -a Linux rotem-laptop 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux tried removing pulseaudio ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpulse0 (not installed) ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rotemfo2383 F pulseaudio /dev/snd/controlC0: rotemfo2383 F pulseaudio Date: Tue Nov 8 12:46:09 2016 DuplicateSignature: package:libpulse0:(not installed) Unpacking libpulse0:i386 (1:8.0-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/libpulse0_1%3a8.0-0ubuntu3_i386.deb (--unpack): trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 ErrorMessage: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 InstallationDate: Installed on 2016-10-25 (14 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: error while loading shared libraries: libpulse.so.0: cannot open shared object file: No such file or directory RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: pulseaudio Title: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/17/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1640139/+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 1217495] Re: I am getting the same error - tried the suggested solutions
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1217495 Title: I am getting the same error - tried the suggested solutions Status in vim package in Ubuntu: Expired Bug description: hello, it was after I upgrade my ubuntu 12.04. And now when I start gvim in the terminal .It will return the following message: gvim:9055): Gnome-WARNING **: Accessibility: failed to find module 'libgail-gnome' which is needed to make this application accessible (gvim:9055): GLib-GObject-WARNING **: cannot retrieve class for invalid (unclassed) type `' ... I hage used sudo gconftool-2 --type bool --set /desktop/gnome/interface/accessibility false as suggested, and reinstalled gvim. Still continue to have errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1217495/+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 1319881] Re: package vim-runtime 2:7.3.547-4ubuntu1.1 [modified: usr/share/doc/vim-runtime/changelog.Debian.gz usr/share/man/fr/man1/vimtutor.1.gz usr/share/man/it/man1/vimtutor.
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1319881 Title: package vim-runtime 2:7.3.547-4ubuntu1.1 [modified: usr/share/doc/vim- runtime/changelog.Debian.gz usr/share/man/fr/man1/vimtutor.1.gz usr/share/man/it/man1/vimtutor.1.gz usr/share/man/man1/vimtutor.1.gz usr/share/man/pl/man1/vimtutor.1.gz usr/share/man/ru/man1/vimtutor.1.gz] failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 2 Status in vim package in Ubuntu: Expired Bug description: This was part of a do-upgrade from saucy to trusty ProblemType: Package DistroRelease: Ubuntu 14.04 Package: vim-runtime 2:7.3.547-4ubuntu1.1 [modified: usr/share/doc/vim-runtime/changelog.Debian.gz usr/share/man/fr/man1/vimtutor.1.gz usr/share/man/it/man1/vimtutor.1.gz usr/share/man/man1/vimtutor.1.gz usr/share/man/pl/man1/vimtutor.1.gz usr/share/man/ru/man1/vimtutor.1.gz] ProcVersionSignature: Ubuntu 3.11.0-20.35-generic 3.11.10.6 Uname: Linux 3.11.0-20-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 Date: Thu May 15 15:53:10 2014 DuplicateSignature: package:vim-runtime:2:7.3.547-4ubuntu1.1 [modified: usr/share/doc/vim-runtime/changelog.Debian.gz usr/share/man/fr/man1/vimtutor.1.gz usr/share/man/it/man1/vimtutor.1.gz usr/share/man/man1/vimtutor.1.gz usr/share/man/pl/man1/vimtutor.1.gz usr/share/man/ru/man1/vimtutor.1.gz]:ErrorMessage: subprocess new pre-installation script returned error exit status 2 ErrorMessage: ErrorMessage: subprocess new pre-installation script returned error exit status 2 InstallationDate: Installed on 2013-01-05 (494 days ago) InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2) PackageArchitecture: all SourcePackage: vim Title: package vim-runtime 2:7.3.547-4ubuntu1.1 [modified: usr/share/doc/vim-runtime/changelog.Debian.gz usr/share/man/fr/man1/vimtutor.1.gz usr/share/man/it/man1/vimtutor.1.gz usr/share/man/man1/vimtutor.1.gz usr/share/man/pl/man1/vimtutor.1.gz usr/share/man/ru/man1/vimtutor.1.gz] failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 2 UpgradeStatus: Upgraded to trusty on 2014-05-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1319881/+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 1174556] Re: package vim-tiny 2:7.3.547-6ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1174556 Title: package vim-tiny 2:7.3.547-6ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in vim package in Ubuntu: Expired Bug description: this happens every time I try to install a new package or when I try to upgrade ubuntu, please help ProblemType: Package DistroRelease: Ubuntu 13.04 Package: vim-tiny 2:7.3.547-6ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Mon Apr 29 23:46:03 2013 DuplicateSignature: Setting up vim-tiny (2:7.3.547-6ubuntu5) ... update-alternatives: error: /var/lib/dpkg/alternatives/rview corrupt: invalid status dpkg: error processing vim-tiny (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2012-04-16 (378 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MarkForUpload: True SourcePackage: vim Title: package vim-tiny 2:7.3.547-6ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to raring on 2013-04-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1174556/+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 694299] Re: The Gvim's menu is not normal, except for "Help"
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/694299 Title: The Gvim's menu is not normal,except for "Help" Status in vim package in Ubuntu: Expired Bug description: Binary package hint: vim Today I want to try the Gvim, when I open it ,its menu is not display, but if I click it, it will display ,and also can't full display. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: vim-gnome 2:7.2.330-1ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-27.49-generic 2.6.32.26+drm33.12 Uname: Linux 2.6.32-27-generic i686 NonfreeKernelModules: nvidia wl Architecture: i386 Date: Sat Dec 25 23:43:24 2010 ExecutablePath: /usr/bin/vim.gnome InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=zh_CN.utf8 SHELL=/bin/bash SourcePackage: vim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/694299/+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 1077788] Re: package vim-gnome 2:7.3.547-4ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1077788 Title: package vim-gnome 2:7.3.547-4ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in vim package in Ubuntu: Expired Bug description: Every time I log on after a few minutes. I get the error message. Most of the time I ignore it but I want to fix this. ProblemType: Package DistroRelease: Ubuntu 12.10 Package: vim-gnome 2:7.3.547-4ubuntu1.1 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Fri Nov 9 14:18:53 2012 ErrorMessage: subprocess installed post-installation script returned error exit status 2 MarkForUpload: True SourcePackage: vim Title: package vim-gnome 2:7.3.547-4ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1077788/+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 407259] Re: Cannot uninstall vim-gnome
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/407259 Title: Cannot uninstall vim-gnome Status in vim package in Ubuntu: Expired Bug description: Binary package hint: vim-gnome Tried to uninstall the package but something went wrong it seems. ProblemType: Package Architecture: amd64 DistroRelease: Ubuntu 9.04 ErrorMessage: underproces pre-removal script returnerede afslutningsstatus 2 NonfreeKernelModules: fglrx Package: vim-gnome 2:7.2.079-1ubuntu5 SourcePackage: vim Title: package vim-gnome 2:7.2.079-1ubuntu5 failed to install/upgrade: underproces pre-removal script returnerede afslutningsstatus 2 Uname: Linux 2.6.28-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/407259/+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 1504827] Re: vimtutor opens up empty
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1504827 Title: vimtutor opens up empty Status in vim package in Ubuntu: Expired Bug description: bubba@mine:~$ vimtutor The program 'vimtutor' is currently not installed. You can install it by typing: sudo apt-get install vim-runtime bubba@mine:~$ which vim bubba@mine:~$ which vi /usr/bin/vi bubba@mine:~$ dpkg-query -S $(which vi) dpkg-query: no path found matching pattern /usr/bin/vi bubba@mine:~$ vi ~ ~ ~ VIM - Vi IMproved ~ ~ version 7.4.488 ~ by Bram Moolenaar et al. ~ Modified by pkg-vim-maintain...@lists.alioth.debian.org ~ Vim is open source and freely distributable ~ ~Become a registered Vim user! ~type :help register for information ~ ~type :q to exit ~type :help orfor on-line help ~type :help version7 for version info ~ ~Running in Vi compatible mode ~type :set nocpfor Vim defaults ~type :help cp-default for info on this ~ ~ ~ :q bubba@mine:~$ dpkg-query -l 'vi*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= un vile (no description available) ii vile-common9.8p-1 all VI Like Emacs - support files for ii vile-filters 9.8p-1 amd64VI Like Emacs - highlighting filt un vim (no description available) un vim-athena (no description available) ii vim-common 2:7.4.488-3u amd64Vi IMproved - Common files un vim-gnome(no description available) un vim-gtk (no description available) un vim-nox (no description available) ii vim-tiny 2:7.4.488-3u amd64Vi IMproved - enhanced vi editor un virtualbox-gue (no description available) bubba@mine:~$ sudo apt-get install vim-runtime Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: vim-runtime 0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded. Need to get 4,980 kB of archives. After this operation, 26.2 MB of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu/ vivid/main vim-runtime all 2:7.4.488-3ubuntu2 [4,980 kB] Fetched 4,980 kB in 5s (845 kB/s) Selecting previously unselected package vim-runtime. (Reading database ... 174233 files and directories currently installed.) Preparing to unpack .../vim-runtime_2%3a7.4.488-3ubuntu2_all.deb ... Adding 'diversion of /usr/share/vim/vim74/doc/help.txt to /usr/share/vim/vim74/doc/help.txt.vim-tiny by vim-runtime' Adding 'diversion of /usr/share/vim/vim74/doc/tags to /usr/share/vim/vim74/doc/tags.vim-tiny by vim-runtime' Unpacking vim-runtime (2:7.4.488-3ubuntu2) ... Processing triggers for man-db (2.7.0.2-5) ... Setting up vim-runtime (2:7.4.488-3ubuntu2) ... Processing /usr/share/vim/addons/doc bubba@mine:~$ vimtutor ~ ~
[Touch-packages] [Bug 885535] Re: package vim 2:7.3.035 hg~8fdc12103333-1ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/885535 Title: package vim 2:7.3.035 hg~8fdc1210-1ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in vim package in Ubuntu: Expired Bug description: i ran this command, sudo apt-get install vim-runtime. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: vim 2:7.3.035+hg~8fdc1210-1ubuntu7 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic x86_64 AptOrdering: vim-runtime: Install vim: Install vim-runtime: Configure vim: Configure Architecture: amd64 Date: Wed Nov 2 22:44:00 2011 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: vim Title: package vim 2:7.3.035+hg~8fdc1210-1ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/885535/+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 401790] Re: package vim-gnome 2:7.2.079-1ubuntu5 failed to install/upgrade: 子程序·post-installation script·返回了錯誤號·2
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/401790 Title: package vim-gnome 2:7.2.079-1ubuntu5 failed to install/upgrade: 子程序 ·post-installation script·返回了錯誤號·2 Status in vim package in Ubuntu: Expired Bug description: Binary package hint: vim package vim-gnome 2:7.2.079-1ubuntu5 failed to install/upgrade: 子程序 ·post-installation script·返回了錯誤號·2 ProblemType: Package Architecture: i386 DistroRelease: Ubuntu 9.04 ErrorMessage: 子程序·post-installation script·返回了錯誤號·2 Package: vim-gnome 2:7.2.079-1ubuntu5 SourcePackage: vim Title: package vim-gnome 2:7.2.079-1ubuntu5 failed to install/upgrade: 子程序·post-installation script·返回了錯誤號·2 Uname: Linux 2.6.28-13-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/401790/+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 778919] Re: package vim-common 2:7.2.330-1ubuntu4 failed to install/upgrade: tentative de remplacement de « /usr/share/vim/vimcurrent », qui appartient aussi au paquet llvm-dev 2
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/778919 Title: package vim-common 2:7.2.330-1ubuntu4 failed to install/upgrade: tentative de remplacement de « /usr/share/vim/vimcurrent », qui appartient aussi au paquet llvm-dev 2.8-0ubuntu3 Status in vim package in Ubuntu: Expired Bug description: Binary package hint: vim Hello, There seems to be a conflict between vim-common and llvm-dev on file /usr/share/vim/vimcurrent. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: vim-common 2:7.2.330-1ubuntu4 ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11 Uname: Linux 2.6.35-28-generic i686 Architecture: i386 Date: Fri May 6 23:54:21 2011 ErrorMessage: tentative de remplacement de « /usr/share/vim/vimcurrent », qui appartient aussi au paquet llvm-dev 2.8-0ubuntu3 SourcePackage: vim Title: package vim-common 2:7.2.330-1ubuntu4 failed to install/upgrade: tentative de remplacement de « /usr/share/vim/vimcurrent », qui appartient aussi au paquet llvm-dev 2.8-0ubuntu3 UpgradeStatus: Upgraded to natty on 2011-05-04 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/778919/+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 896725] Re: package vim-tiny 2:7.3.154+hg~74503f6ee649-2ubuntu3 [modified: usr/share/vim/vim73/doc/help.txt usr/share/vim/vim73/doc/tags] failed to install/upgrade: ErrorMessage:
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/896725 Title: package vim-tiny 2:7.3.154+hg~74503f6ee649-2ubuntu3 [modified: usr/share/vim/vim73/doc/help.txt usr/share/vim/vim73/doc/tags] failed to install/upgrade: ErrorMessage: subprocess installed post- installation script returned error exit status 2 Status in vim package in Ubuntu: Expired Bug description: Happened during upgrade to Ubuntu 11.10. ProblemType: Package DistroRelease: Ubuntu 11.10 Package: vim-tiny 2:7.3.154+hg~74503f6ee649-2ubuntu3 [modified: usr/share/vim/vim73/doc/help.txt usr/share/vim/vim73/doc/tags] ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sat Nov 26 17:58:25 2011 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: vim Title: package vim-tiny 2:7.3.154+hg~74503f6ee649-2ubuntu3 [modified: usr/share/vim/vim73/doc/help.txt usr/share/vim/vim73/doc/tags] failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to oneiric on 2011-11-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/896725/+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 298530] Re: gvim occasionally crashes when file changed outside it
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/298530 Title: gvim occasionally crashes when file changed outside it Status in vim package in Ubuntu: Expired Bug description: Binary package hint: vim I am using gvim to read a file created by a program. gvim will irregularly crash when the file is changed underneath it and you click 'Load' in the dialogue box. It come up with a invalid nline. Seems to be when the file is shortened from the original, have not determined a pattern yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/298530/+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 1796355] Re: USB-C ValueLine network adapter fails to connect
I may have misidentified the affected package. Further testing indicates that while the USB adapter works fine in all three USB-C ports under Windows, the connection problem I've reported above appears only when I use either of the two USB-C ports (described as USB Type-C/Thunderbolt 3/Power (DC) input combo port by Asus), but not when I use the remaining port (described as USB Type-C/Power (DC) input combo port). Thus, in the Thunderbolt 3-capable ports, under Ubuntu, it doesn't work. In the non-Thunderbolt-port it does work: -- 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/1796355 Title: USB-C ValueLine network adapter fails to connect Status in network-manager package in Ubuntu: New Bug description: The adapter I'm trying to use using is a 'Valueline' USB-C adapter, with no external identifying information. lsusb lists it as Bus 004 Device 022: ID 0bda:8153 Realtek Semiconductor Corp. It works fine on a Windows 10 system (same hardware platform), where it's identified as a 10/100/1000 Realtek adapter. When I connect it to my system (Asus Zenbook UX490UA) internal lights go on, but no connection is produced. The network icon (upper right) is shown briefly, then disappears, the is show, then disappears. After some time it seems to give up. Kernel logs show repeated occurrences of: Oct 5 17:02:22 athasus kernel: [ 317.843590] usb 4-2: new SuperSpeed USB device number 121 using xhci_hcd Oct 5 17:02:22 athasus kernel: [ 317.863719] usb 4-2: New USB device found, idVendor=0bda, idProduct=8153 Oct 5 17:02:22 athasus kernel: [ 317.863728] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=6 Oct 5 17:02:22 athasus kernel: [ 317.863735] usb 4-2: Product: USB 10/100/1000 LAN Oct 5 17:02:22 athasus kernel: [ 317.863741] usb 4-2: Manufacturer: Realtek Oct 5 17:02:22 athasus kernel: [ 317.863745] usb 4-2: SerialNumber: 0100 Oct 5 17:02:22 athasus kernel: [ 318.000268] usb 4-2: reset SuperSpeed USB device number 121 using xhci_hcd Oct 5 17:02:22 athasus kernel: [ 318.057875] r8152 4-2:1.0 eth0: v1.09.9 Oct 5 17:02:22 athasus kernel: [ 318.138042] r8152 4-2:1.0 enxa0cec809bf58: renamed from eth0 Oct 5 17:02:22 athasus kernel: [ 318.170397] IPv6: ADDRCONF(NETDEV_UP): enxa0cec809bf58: link is not ready Oct 5 17:02:22 athasus kernel: [ 318.176359] IPv6: ADDRCONF(NETDEV_UP): enxa0cec809bf58: link is not ready Oct 5 17:02:22 athasus kernel: [ 318.354745] r8152 4-2:1.0 enxa0cec809bf58: Stop submitting intr, status -71 Oct 5 17:02:22 athasus kernel: [ 318.543737] usb 4-2: USB disconnect, device number 121 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 17:35:17 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-03 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 172.16.4.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 172.16.4.0/24 dev wlp2s0 proto kernel scope link src 172.16.4.102 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE ATH 79577e92-4b01-46c4-bbff-2088aaf0750a wifi 1538753528 fre 5 okt 2018 17:32:08 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 ATH 79577e92-4b01-46c4-bbff-2088aaf0750a /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled
[Touch-packages] [Bug 1796367] Re: New release of 'mesa' (18.2.2)
we're not on the SRU phase yet, so these are fairly pointless -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1796367 Title: New release of 'mesa' (18.2.2) Status in mesa package in Ubuntu: New Bug description: Hello, https://www.mesa3d.org/relnotes/18.2.2.html Bug fixes - [apitrace] Graphical artifacts in Civilization VI on RX Vega - swrast: Mesa 17.3.3 produces: HW cursor for format 875713089 not supported - radv: OpBitfieldUExtract returns incorrect result when count is zero - [DXVK] MSAA reflections are broken in GTA V - [Debian Stretch]Fail to build because "xcb_randr_lease_t" Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglapi-mesa 18.2.1-1ubuntu1 Uname: Linux 4.18.12-gnu x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 13:45:21 2018 Dependencies: gcc-8-base 8.2.0-7ubuntu1 libc6 2.28-0ubuntu1 libgcc1 1:8.2.0-7ubuntu1 libidn2-0 2.0.5-1 libunistring2 0.9.10-1ubuntu1 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.18.0-8-generic, x86_64: installed virtualbox, 5.2.18, 4.18.12-gnu, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0d7] InstallationDate: Installed on 2017-10-13 (357 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.12-gnu root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 xserver.bootTime: Fri Jul 20 17:46:48 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1796367/+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
