[Touch-packages] [Bug 2009859] Re: systemd: networkd-test.py fails with newer kinetic kernels
I have hit this bug in the ADT testing part of the linux-aws 5.19.0-1027.28 release: https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/s/systemd/20230525_124201_d6c4e@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/arm64/s/systemd/20230525_134055_652ab@/log.gz ** Tags added: sru-20230515 -- 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/2009859 Title: systemd: networkd-test.py fails with newer kinetic kernels Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux source package in Kinetic: Confirmed Status in systemd source package in Kinetic: New Bug description: systemd autopkgtests are failing in kinetic, and they are not considered regressions. The failing test is one within networkd- test.py: == ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest) resolved: domain-restricted DNS servers -- Traceback (most recent call last): File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 680, in test_resolved_domain_restricted_dns out = subprocess.check_output(['resolvectl', 'query', 'math.lab']) File "/usr/lib/python3.10/subprocess.py", line 420, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.10/subprocess.py", line 524, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' returned non-zero exit status 1. -- Ran 35 tests in 161.770s FAILED (errors=1, skipped=2) The failures started without any changes to the systemd package, i.e. it was caused by another package upload. In particular, the failures started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine with linux 5.19.0-21.21, i.e. the version in kinetic-release. This can be demonstrated locally with autopkgtest: $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin- packages=kinetic=src:linux --setup-commands 'apt update' -- qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img Note in the above command I did not pass -U, so no packages in the test bed are upgraded. But, with: $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U -- qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic- amd64.img the kernel is upgraded, and the test fails. This can also be done manually by grabbing the systemd source on a kinetic machine (e.g. pull-lp-source systemd kinetic), and running: $ sudo python3 test/networkd-test.py DnsmasqClientTest.test_resolved_domain_restricted_dns The attached journal.txt shows systemd-resolved logs from when the test is run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 9 11:56 seq crw-rw 1 root audio 116, 33 Mar 9 11:56 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 console=ttyS0 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: kinetic Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.16.0-debian-1.16.0-4 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU
[Touch-packages] [Bug 1848587] Re: lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2
** Description changed: + [ Impact ] + + * Test suite fails due to inexistent device (/dev/network_latency). + + [ Test Plan ] + + * Run the test suite. + * The test should pass. + + [ Where problems could occur ] + + * The regression risk is very low, and the changes only affect the + tests, so the regression scope is minimal. + + [ Other Info ] + + Original bug report: + Testing failed on: - amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/l/lxc/20191016_150939_0f81d@/log.gz - arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/arm64/l/lxc/20191016_152027_0f81d@/log.gz - ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/ppc64el/l/lxc/20191016_150251_0f81d@/log.gz - s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/s390x/l/lxc/20191016_150201_0f81d@/log.gz + amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/l/lxc/20191016_150939_0f81d@/log.gz + arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/arm64/l/lxc/20191016_152027_0f81d@/log.gz + ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/ppc64el/l/lxc/20191016_150251_0f81d@/log.gz + s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/s390x/l/lxc/20191016_150201_0f81d@/log.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1848587 Title: lxc 3.0.4-0ubuntu1 ADT test failure with linux 5.4.0-1.2 Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Bionic: Fix Committed Bug description: [ Impact ] * Test suite fails due to inexistent device (/dev/network_latency). [ Test Plan ] * Run the test suite. * The test should pass. [ Where problems could occur ] * The regression risk is very low, and the changes only affect the tests, so the regression scope is minimal. [ Other Info ] Original bug report: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/amd64/l/lxc/20191016_150939_0f81d@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/arm64/l/lxc/20191016_152027_0f81d@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/ppc64el/l/lxc/20191016_150251_0f81d@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan-canonical-kernel-team-unstable/eoan/s390x/l/lxc/20191016_150201_0f81d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587/+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 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)
** Description changed: + [ Impact ] + + * The device_add_remove_test test fails on the affected series (e.g. Bionic). + * Having the test fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for this test. + + [ Test Plan ] + + * Run the affected test on an affected series (e.g. Bionic). + * The test should pass. + + [ Other Info ] + + Upstream drop of network_latency: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c3082a674f46fe49383b157882c41dfabaa37113 + Related to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587 + Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz The failing test seems to be: FAIL: lxc-tests: lxc-test-device-add-remove (0s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... --- This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note that this testcase is successful on Focal with the same kernel version. ** Description changed: [ Impact ] - * The device_add_remove_test test fails on the affected series (e.g. Bionic). - * Having the test fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for this test. + * The device_add_remove_test test fails on the affected series (e.g. Bionic). + * Having the test fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for this test. [ Test Plan ] - * Run the affected test on an affected series (e.g. Bionic). - * The test should pass. + * Run the affected test on an affected series (e.g. Bionic). + * The test should pass. [ Other Info ] Upstream drop of network_latency: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c3082a674f46fe49383b157882c41dfabaa37113 Related to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587 + + Original bug report: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz The failing test seems to be: FAIL: lxc-tests: lxc-test-device-add-remove (0s) --- Adding /dev/network_latency to the container (device_add_remove_test) failed... --- This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note that this testcase is successful on Focal with the same kernel version. ** Description changed: [ Impact ] * The device_add_remove_test test fails on the affected series (e.g. Bionic). * Having the test fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for this test. [ Test Plan ] * Run the affected test on an affected series (e.g. Bionic). * The test should pass. + + [ Where problems could occur ] + + * The regression risk is very low, and the changes only affect the + tests, so the regression scope is minimal. [ Other Info ] Upstream drop of network_latency: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c3082a674f46fe49383b157882c41dfabaa37113 Related to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587 Original bug report: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz ppc64el:
[Touch-packages] [Bug 1939537] Re: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases
** Description changed: [ Impact ] - * The following tests fail as they try to use inexistent LXC images: -* lxc-test-apparmor-mount - * lxc-test-autostart - * lxc-test-unpriv - * lxc-test-usernic + * The following tests fail as they try to use inexistent LXC images: + * lxc-test-apparmor-mount + * lxc-test-autostart + * lxc-test-unpriv + * lxc-test-usernic - * Having them fixed for the affected series (for example Bionic) will allow us to run the LXC test suite without maintaining local changes. - + * Having them fixed for the affected series (for example, Bionic) will + allow us to run the LXC test suite without maintaining local changes for + these tests. [ Test Plan ] - * Run the affected tests on an affected series (e.g. Bionic). + * Run the affected tests on an affected series (e.g. Bionic). [ Where problems could occur ] - * The regression risk is very low and the changes only affect the tests + * The regression risk is very low and the changes only affect the tests so the regression scope is minimal. [Other info] Original bug report: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. ** Description changed: [ Impact ] * The following tests fail as they try to use inexistent LXC images: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic * Having them fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for these tests. [ Test Plan ] * Run the affected tests on an affected series (e.g. Bionic). + * The tests should pass. [ Where problems could occur ] * The regression risk is very low and the changes only affect the tests so the regression scope is minimal. [Other info] Original bug report: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1939537 Title: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Confirmed Status in lxc source package in Bionic: Fix Committed Bug description: [ Impact ] * The following tests fail as they try to use inexistent LXC images: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic * Having them fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for these tests. [ Test Plan ] * Run the affected tests on an affected series (e.g. Bionic). * The tests should pass. [ Where problems could occur ] * The regression risk is very low and the changes only affect the tests so the regression scope is minimal. [Other info] Original bug report: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. To manage notifications about this bug go to:
[Touch-packages] [Bug 1939537] Re: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases
** Description changed: + [ Impact ] + + * The following tests fail as they try to use inexistent LXC images: +* lxc-test-apparmor-mount + * lxc-test-autostart + * lxc-test-unpriv + * lxc-test-usernic + + * Having them fixed for the affected series (for example Bionic) will allow us to run the LXC test suite without maintaining local changes. + + + [ Test Plan ] + + * Run the affected tests on an affected series (e.g. Bionic). + + [ Where problems could occur ] + + * The regression risk is very low and the changes only affect the tests + so the regression scope is minimal. + + [Other info] + + Original bug report: + Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: - * lxc-test-apparmor-mount - * lxc-test-autostart - * lxc-test-unpriv - * lxc-test-usernic + * lxc-test-apparmor-mount + * lxc-test-autostart + * lxc-test-unpriv + * lxc-test-usernic Are now failing with: - ERROR: Couldn't find a matching image. - + ERROR: Couldn't find a matching image. + This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: - ubuntu-distro-info --supported + ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1939537 Title: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: Confirmed Status in lxc source package in Bionic: Fix Committed Bug description: [ Impact ] * The following tests fail as they try to use inexistent LXC images: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic * Having them fixed for the affected series (for example, Bionic) will allow us to run the LXC test suite without maintaining local changes for these tests. [ Test Plan ] * Run the affected tests on an affected series (e.g. Bionic). [ Where problems could occur ] * The regression risk is very low and the changes only affect the tests so the regression scope is minimal. [Other info] Original bug report: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939537/+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 1939537] Re: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases
I am attaching a fix for Bionic. Note that this pulls in another unapproved change from @xnox to ease merging in time for the SRU cycle. This was checked with Stéphane Graber, who agreed to an exception of pushing a test-specific change given the SRU cycle is ending very soon, and most of the users would have switched anyway. ** Patch added: "lxc_3.0.3-0ubuntu1~18.04.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1939537/+attachment/5673160/+files/lxc_3.0.3-0ubuntu1~18.04.3.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1939537 Title: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: New Status in lxc source package in Bionic: New Bug description: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939537/+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 1939537] Re: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases
** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Bionic) Assignee: (unassigned) => Andrei Gherzan (agherzan) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1939537 Title: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases Status in ubuntu-kernel-tests: New Status in lxc package in Ubuntu: New Status in lxc source package in Bionic: New Bug description: Issue found on node onibi 4.15.0-142-generic #146~16.04.1 With bug 1916087 resolved, the following tests: * lxc-test-apparmor-mount * lxc-test-autostart * lxc-test-unpriv * lxc-test-usernic Are now failing with: ERROR: Couldn't find a matching image. This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target release is "trusty" or the system release if supported. It will be checked with: ubuntu-distro-info --supported However Xenial is an ESM series now, it won't use xenial as the target release but use trusty instead. The attempt to download trusty image will fail with this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939537/+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 1964401] Re: Software Sources/software-properties-qt privilege escalation not accepting password
*** This bug is a duplicate of bug 1965439 *** https://bugs.launchpad.net/bugs/1965439 ** This bug has been marked a duplicate of bug 1965439 software-properties-qt can no longer launch when called by pkexec -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1964401 Title: Software Sources/software-properties-qt privilege escalation not accepting password Status in plasma-discover package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) package version - apt-cache policy pkgname' plasma-discover: Installed: 5.24.2.1-0ubuntu1 software-properties-qt: Installed: 0.99.19 3) expected to happen * In Discover: Settings > Software Sources * opens a privilege escalation dialogue * enter user password * software-properties-qt opens 4) happened instead * In Discover: Settings > Software Sources * opens a privilege escalation dialogue * insert known-correct user password * **does not accept known-correct user password** # Additional Info Note: described behaviour is for a post 20.04->22.04 devel daily upgrade found during a QA Testcase. Behaviour exists, but has slightly different symptoms in a virgin live 22.04 daily session (see below) * launching from terminal works as expected sudo software-properties-qt ## process & errors - post 20.04->22.04 devel daily upgrade * running Discover from terminal $ plasma-discover * Settings > Software Sources gives error on terminal: > org.kde.kdesu: Daemon not safe (not sgid), not using it. * insert known-correct user password gives error on terminal: > kf.su: [ ./src/stubprocess.cpp : 225 ] Unknown request: "stop" > end * close password window gives error on terminal > Usage: /usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu [options] command > Runs a program with elevated privileges. > Options: > -h, --help Displays help on commandline options. > [...] ## process & errors - live Kubuntu 22.04 daily similar behaviour, hoever password-asking window never appears. Terminal errors differ from above: * Settings > Software Sources gives error on terminal: > org.kde.kdesu: Daemon not safe (not sgid), not using it. > > Don't need password!! > >kf.su: [./src/stubprocess.cpp : 255 ] Unknown request: "ok" --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-07 (2 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: plasma-discover 5.24.2.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy third-party-packages Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1964401/+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 1961484] [NEW] 20.04.3: libva2 fails under Wayland (wl_drm@22: error 0: authenticate failed)
Public bug reported: In current 20.04.3 libva2 fails to authenticate connection to Wayland composer. This may be related to update of Mesa to 21.2.6. Any program using libva2 fails with bor@bor-Latitude-E5450:~$ vainfo wl_drm@7: error 0: authenticate failed VA error: wayland: Wayland roundtrip error: Protocol error (errno 71) libva info: VA-API version 1.7.0 libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) vaInitialize failed with error code 3 (invalid VADisplay),exit bor@bor-Latitude-E5450:~$ This is fixed in libva upstream in pull request https://github.com/intel/libva/pull/476 I verified that upstream libva correctly works: bor@bor-Latitude-E5450:~/src/intel/libva-utils$ ./vainfo/vainfo libva info: VA-API version 1.15.0 libva info: Trying to open /home/bor/pkg/lib/dri/iHD_drv_video.so libva info: va_openDriver() returns -1 libva info: Trying to open /home/bor/pkg/lib/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_6 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.15 (libva 2.15.0.pre1) vainfo: Driver version: Intel i965 driver for Intel(R) Broadwell - 2.4.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Simple : VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileVP8Version0_3 : VAEntrypointVLD bor@bor-Latitude-E5450:~/src/intel/libva-utils$ With *only* commit 283f776a9649dcef58b47958c1269499adfa1cd4 reverted bor@bor-Latitude-E5450:~/src/intel/libva-utils$ ./vainfo/vainfo wl_drm@7: error 0: authenticate failed VA error: wayland: Wayland roundtrip error: Protocol error (errno 71) libva info: VA-API version 1.15.0 libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) vaInitialize failed with error code 3 (invalid VADisplay),exit bor@bor-Latitude-E5450:~/src/intel/libva-utils$ Please update libva in 20.04.3 to match Mesa. This bug affects any application that is trying to use VAAPI for hardware acceleration. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libva2 2.7.0-2 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-lowlatency 5.13.19 Uname: Linux 5.13.0-30-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 19 19:16:15 2022 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (2424 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: libva UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libva (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1961484 Title: 20.04.3: libva2 fails under Wayland (wl_drm@22: error 0: authenticate failed) Status in libva package in Ubuntu: New Bug description: In current 20.04.3 libva2 fails to authenticate connection to Wayland composer. This may be related to update of Mesa to 21.2.6. Any program using libva2 fails with bor@bor-Latitude-E5450:~$ vainfo wl_drm@7: error 0: authenticate failed VA error: wayland: Wayland roundtrip error: Protocol error (errno 71) libva info: VA-API version 1.7.0 libva error: vaGetDriverNameByIndex() failed with invalid VADisplay, driver_name = (null) vaInitialize failed with error code 3 (invalid VADisplay),exit bor@bor-Latitude-E5450:~$ This is fixed in libva upstream in pull request https://github.com/intel/libva/pull/476 I verified that upstream libva correctly works: bor@bor-Latitude-E5450:~/src/intel/libva-utils$ ./vainfo/vainfo libva info: VA-API version 1.15.0 libva info: Trying to open
[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
Fixed for me, I have suspended laptop and after that I still could turn on bluetooth, before that it didn't work Ubuntu 21.04 3.38.1-3ubuntu3.1 -- 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/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Fix Released Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: Fix Released Status in gnome-settings-daemon source package in Focal: Fix Committed Status in bluez source package in Hirsute: Fix Released Status in gnome-settings-daemon source package in Hirsute: Fix Committed Status in bluez source package in Impish: Fix Released Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+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 1935754] Re: laptop brightness hotkey after latest update
done ** Summary changed: - Problems with Blutooth and laptop brightness hotkey after lates update + laptop brightness hotkey after latest update ** Description changed: Hello! - After recent update I have several problems - 1. can't turn on/off my bluetooth - 2. brightness laptop button are turning my mic off instead of reduce or high it - + After recent update I have a problem brightness laptop button are + turning my mic off instead of reduce or high it Could you fix it please? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu4.2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 10 21:32:04 2021 InstallationDate: Installed on 2020-04-08 (458 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP EliteBook 850 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=78466619-ba7c-4459-92c2-58fc31c658f2 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-15 (86 days ago) dmi.bios.date: 09/12/2019 dmi.bios.release: 3.0 dmi.bios.vendor: HP dmi.bios.version: R70 Ver. 01.03.00 dmi.board.name: 8549 dmi.board.vendor: HP dmi.board.version: KBC Version 52.52.00 dmi.chassis.asset.tag: 5CG9450KGR dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 82.82 dmi.modalias: dmi:bvnHP:bvrR70Ver.01.03.00:bd09/12/2019:br3.0:efr82.82:svnHP:pnHPEliteBook850G6:pvr:rvnHP:rn8549:rvrKBCVersion52.52.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G6 dmi.product.sku: 7KP17EA#ACB dmi.sys.vendor: HP hciconfig: - hci0:Type: Primary Bus: USB - BD Address: 94:E6:F7:2D:22:F5 ACL MTU: 1021:4 SCO MTU: 96:6 - UP RUNNING PSCAN ISCAN - RX bytes:21793 acl:0 sco:0 events:3343 errors:0 - TX bytes:796729 acl:0 sco:0 commands:3321 errors:0 + hci0:Type: Primary Bus: USB + BD Address: 94:E6:F7:2D:22:F5 ACL MTU: 1021:4 SCO MTU: 96:6 + UP RUNNING PSCAN ISCAN + RX bytes:21793 acl:0 sco:0 events:3343 errors:0 + TX bytes:796729 acl:0 sco:0 commands:3321 errors:0 ** Changed in: bluez (Ubuntu) Status: Incomplete => New -- 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/1935754 Title: laptop brightness hotkey after latest update Status in bluez package in Ubuntu: New Bug description: Hello! After recent update I have a problem brightness laptop button are turning my mic off instead of reduce or high it Could you fix it please? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu4.2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 10 21:32:04 2021 InstallationDate: Installed on 2020-04-08 (458 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP EliteBook 850 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=78466619-ba7c-4459-92c2-58fc31c658f2 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-15 (86 days ago) dmi.bios.date: 09/12/2019 dmi.bios.release: 3.0 dmi.bios.vendor: HP dmi.bios.version: R70 Ver. 01.03.00 dmi.board.name: 8549 dmi.board.vendor: HP dmi.board.version: KBC Version 52.52.00 dmi.chassis.asset.tag: 5CG9450KGR dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 82.82 dmi.modalias: dmi:bvnHP:bvrR70Ver.01.03.00:bd09/12/2019:br3.0:efr82.82:svnHP:pnHPEliteBook850G6:pvr:rvnHP:rn8549:rvrKBCVersion52.52.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G6 dmi.product.sku: 7KP17EA#ACB dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: 94:E6:F7:2D:22:F5 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:21793 acl:0 sco:0 events:3343 errors:0 TX bytes:796729 acl:0 sco:0 commands:3321 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1935754/+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 1935754] [NEW] Problems with Blutooth and laptop brightness hotkey after lates update
Public bug reported: Hello! After recent update I have several problems 1. can't turn on/off my bluetooth 2. brightness laptop button are turning my mic off instead of reduce or high it Could you fix it please? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu4.2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 10 21:32:04 2021 InstallationDate: Installed on 2020-04-08 (458 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP EliteBook 850 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=78466619-ba7c-4459-92c2-58fc31c658f2 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-15 (86 days ago) dmi.bios.date: 09/12/2019 dmi.bios.release: 3.0 dmi.bios.vendor: HP dmi.bios.version: R70 Ver. 01.03.00 dmi.board.name: 8549 dmi.board.vendor: HP dmi.board.version: KBC Version 52.52.00 dmi.chassis.asset.tag: 5CG9450KGR dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 82.82 dmi.modalias: dmi:bvnHP:bvrR70Ver.01.03.00:bd09/12/2019:br3.0:efr82.82:svnHP:pnHPEliteBook850G6:pvr:rvnHP:rn8549:rvrKBCVersion52.52.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G6 dmi.product.sku: 7KP17EA#ACB dmi.sys.vendor: HP hciconfig: hci0: Type: Primary Bus: USB BD Address: 94:E6:F7:2D:22:F5 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:21793 acl:0 sco:0 events:3343 errors:0 TX bytes:796729 acl:0 sco:0 commands:3321 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- 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/1935754 Title: Problems with Blutooth and laptop brightness hotkey after lates update Status in bluez package in Ubuntu: New Bug description: Hello! After recent update I have several problems 1. can't turn on/off my bluetooth 2. brightness laptop button are turning my mic off instead of reduce or high it Could you fix it please? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu4.2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jul 10 21:32:04 2021 InstallationDate: Installed on 2020-04-08 (458 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP EliteBook 850 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=78466619-ba7c-4459-92c2-58fc31c658f2 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-15 (86 days ago) dmi.bios.date: 09/12/2019 dmi.bios.release: 3.0 dmi.bios.vendor: HP dmi.bios.version: R70 Ver. 01.03.00 dmi.board.name: 8549 dmi.board.vendor: HP dmi.board.version: KBC Version 52.52.00 dmi.chassis.asset.tag: 5CG9450KGR dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 82.82 dmi.modalias: dmi:bvnHP:bvrR70Ver.01.03.00:bd09/12/2019:br3.0:efr82.82:svnHP:pnHPEliteBook850G6:pvr:rvnHP:rn8549:rvrKBCVersion52.52.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 850 G6 dmi.product.sku: 7KP17EA#ACB dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: 94:E6:F7:2D:22:F5 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:21793 acl:0 sco:0 events:3343 errors:0 TX bytes:796729 acl:0 sco:0 commands:3321 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1935754/+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 1904695] Re: systemctl doesn't work when running from `docker run $image chroot` command (Bionic)
I found a solution that works for me: it is needed to add option `--pid host` option to `docker run` command. -- 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/1904695 Title: systemctl doesn't work when running from `docker run $image chroot` command (Bionic) Status in systemd package in Ubuntu: New Bug description: 1) Tested on fresh installed system using http://old-releases.ubuntu.com/releases/bionic/ubuntu-18.04-server-amd64.iso image. The release of Ubuntu via 'lsb_release -rd' Description: Ubuntu 18.04.4 LTS Release: 18.04 2) The version of the systemd package via 'apt-cache policy systemd' systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.42 Version table: 237-3ubuntu10.42 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages *** 237-3ubuntu10.33 100 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) Steps to reproduce the problem $ sudo su $ apt update $ apt install docker.io $ docker pull ubuntu:latest $ docker run -it -v /:/host_root:ro ubuntu:latest chroot /host_root/ systemctl -a 4) What you expected to happen: a list of all systemd units is expected to be displayed, e.g. UNITLOAD ACTIVE SUB DESCRIPTION proc-sys-fs-binfmt_misc.automount loaded active waiting Arbitrary Executable File Formats File System Auto dev-cdrom.deviceloaded active plugged VBOX_CD-ROM dev-disk-by\x2did-ata\x2dVBOX_CD\x2dROM_VB2\x2d01700376.device loaded active plugged VBOX_CD-ROM [cut out] 5) What happened instead: get the following error message Failed to connect to bus: No data available 6) The same steps tested on fresh installed Ubuntu Xenial OS using http://old-releases.ubuntu.com/releases/xenial/ubuntu-16.04.6-server-amd64.iso image. And in this environment the `systemctl -a` command works well. $ lsb_release -rd Description: Ubuntu 16.04.6 LTS Release: 16.04 $ apt-cache policy systemd systemd: Installed: 229-4ubuntu21.16 Candidate: 229-4ubuntu21.29 Version table: 229-4ubuntu21.29 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 229-4ubuntu21.27 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages *** 229-4ubuntu21.16 100 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 7) Additional notes: I tried to add `--privileged` options to `docker run` command but it didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1904695/+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 1904695] [NEW] systemctl doesn't work when running from `docker run $image chroot` command (Bionic)
Public bug reported: 1) Tested on fresh installed system using http://old-releases.ubuntu.com/releases/bionic/ubuntu-18.04-server-amd64.iso image. The release of Ubuntu via 'lsb_release -rd' Description:Ubuntu 18.04.4 LTS Release:18.04 2) The version of the systemd package via 'apt-cache policy systemd' systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.42 Version table: 237-3ubuntu10.42 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages *** 237-3ubuntu10.33 100 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) Steps to reproduce the problem $ sudo su $ apt update $ apt install docker.io $ docker pull ubuntu:latest $ docker run -it -v /:/host_root:ro ubuntu:latest chroot /host_root/ systemctl -a 4) What you expected to happen: a list of all systemd units is expected to be displayed, e.g. UNITLOAD ACTIVE SUB DESCRIPTION proc-sys-fs-binfmt_misc.automount loaded active waiting Arbitrary Executable File Formats File System Auto dev-cdrom.deviceloaded active plugged VBOX_CD-ROM dev-disk-by\x2did-ata\x2dVBOX_CD\x2dROM_VB2\x2d01700376.device loaded active plugged VBOX_CD-ROM [cut out] 5) What happened instead: get the following error message Failed to connect to bus: No data available 6) The same steps tested on fresh installed Ubuntu Xenial OS using http://old-releases.ubuntu.com/releases/xenial/ubuntu-16.04.6-server-amd64.iso image. And in this environment the `systemctl -a` command works well. $ lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 $ apt-cache policy systemd systemd: Installed: 229-4ubuntu21.16 Candidate: 229-4ubuntu21.29 Version table: 229-4ubuntu21.29 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 229-4ubuntu21.27 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages *** 229-4ubuntu21.16 100 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 7) Additional notes: I tried to add `--privileged` options to `docker run` command but it didn't help. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: systemctl -- 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/1904695 Title: systemctl doesn't work when running from `docker run $image chroot` command (Bionic) Status in systemd package in Ubuntu: New Bug description: 1) Tested on fresh installed system using http://old-releases.ubuntu.com/releases/bionic/ubuntu-18.04-server-amd64.iso image. The release of Ubuntu via 'lsb_release -rd' Description: Ubuntu 18.04.4 LTS Release: 18.04 2) The version of the systemd package via 'apt-cache policy systemd' systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.42 Version table: 237-3ubuntu10.42 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages *** 237-3ubuntu10.33 100 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) Steps to reproduce the problem $ sudo su $ apt update $ apt install docker.io $ docker pull ubuntu:latest $ docker run -it -v /:/host_root:ro ubuntu:latest chroot /host_root/ systemctl -a 4) What you expected to happen: a list of all systemd units is expected to be displayed, e.g. UNITLOAD ACTIVE SUB DESCRIPTION proc-sys-fs-binfmt_misc.automount loaded active waiting Arbitrary Executable File Formats File System Auto dev-cdrom.deviceloaded active plugged VBOX_CD-ROM dev-disk-by\x2did-ata\x2dVBOX_CD\x2dROM_VB2\x2d01700376.device loaded active plugged VBOX_CD-ROM [cut out] 5) What happened instead: get the following error message Failed to connect to bus: No data available 6) The same steps tested on fresh installed Ubuntu Xenial OS using http://old-releases.ubuntu.com/releases/xenial/ubuntu-16.04.6-server-amd64.iso image. And in this environment the `systemctl -a` command works well. $ lsb_release -rd Description: Ubuntu 16.04.6
[Touch-packages] [Bug 1890891] [NEW] dock
Public bug reported: when no one program is pinned and no one open dock stop working normally. When I open program it appear only 10 sec later as well for closing. restarting with alt + f2 is solving problem until all programs again unpinned and closed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 16:08:55 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. A320M-S2H V2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=bfd431bb-2152-4fc0-98a1-a1e23b252397 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H V2-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.:bvrF50:bd12/02/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2HV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2HV2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H V2 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1890891 Title: dock Status in xorg package in Ubuntu: New Bug description: when no one program is pinned and no one open dock stop working normally. When I open program it appear only 10 sec later as well for closing. restarting with alt + f2 is solving problem until all programs again unpinned and closed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 16:08:55 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. A320M-S2H V2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=bfd431bb-2152-4fc0-98a1-a1e23b252397 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H V2-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3
[Touch-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
This is the most heated bug on this site. Can someone please get this fixed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1807709] Re: dbus always crashes at session start (on wayland)
Same here, Ubuntu 19.04, not on wayland. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1807709 Title: dbus always crashes at session start (on wayland) Status in dbus package in Ubuntu: Confirmed Bug description: When you login in ubuntu 18.10 using gnome shell and wayland, dbus always crashes and you are welcomed with a dialog to report the crash. Looking into the file `/var/crash/_usr_bin_dbus-daemon.1000.crash` one can see that there is antoher bug, previoulsy reported as #1591548 (https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1591548) So may be the bug report is never sent, either ? /var/crash/_usr_bin_dbus-daemon.1000.crash content is: ProblemType: Crash Architecture: amd64 Date: Sun Dec 9 11:16:22 2018 DistroRelease: Ubuntu 18.10 ExecutablePath: /usr/bin/dbus-daemon ExecutableTimestamp: 1536206167 ProcCmdline: /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only ProcCwd: /home/solstice ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcMaps: 55c9bfc7a000-55c9bfc83000 r--p 08:07 787824 /usr/bin/dbus-daemon 55c9bfc83000-55c9bfca5000 r-xp 9000 08:07 787824 /usr/bin/dbus-daemon 55c9bfca5000-55c9bfcb3000 r--p 0002b000 08:07 787824 /usr/bin/dbus-daemon 55c9bfcb3000-55c9bfcb5000 r--p 00038000 08:07 787824 /usr/bin/dbus-daemon 55c9bfcb5000-55c9bfcb6000 rw-p 0003a000 08:07 787824 /usr/bin/dbus-daemon 55c9c1bd8000-55c9c1f1e000 rw-p 00:00 0 [heap] 7eff0278c000-7eff02792000 r--p 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff02792000-7eff027bd000 r-xp 6000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027bd000-7eff027cc000 r--p 00031000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027cc000-7eff027cf000 r--p 0003f000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027cf000-7eff027d rw-p 00042000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027d-7eff027d1000 rw-p 00:00 0 7eff027d1000-7eff027d4000 r--p 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027d4000-7eff027db000 r-xp 3000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027db000-7eff027de000 r--p a000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027de000-7eff027df000 r--p c000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027df000-7eff027e rw-p d000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027e-7eff027e6000 rw-p 00:00 0 7eff027e6000-7eff027ea000 r--p 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027ea000-7eff027f8000 r-xp 4000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027f8000-7eff027fd000 r--p 00012000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027fd000-7eff027fe000 r--p 00016000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027fe000-7eff027ff000 rw-p 00017000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027ff000-7eff02801000 rw-p 00:00 0 7eff02801000-7eff02803000 r--p 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff02803000-7eff0280b000 r-xp 2000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280b000-7eff0280d000 r--p a000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280d000-7eff0280e000 r--p b000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280e000-7eff0280f000 rw-p c000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280f000-7eff02811000 r--p 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02811000-7eff02817000 r-xp 2000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02817000-7eff02818000 r--p 8000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02818000-7eff02819000 r--p 8000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02819000-7eff0281a000 rw-p 9000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff0281a000-7eff0281f000 rw-p 00:00 0
[Touch-packages] [Bug 1807709] Re: dbus always crashes at session start (on wayland)
Here's crash report. Ubuntu 19.04, not on wayland. ** Attachment added: "Crash report" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1807709/+attachment/5274264/+files/_usr_bin_dbus-daemon.1000.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1807709 Title: dbus always crashes at session start (on wayland) Status in dbus package in Ubuntu: Confirmed Bug description: When you login in ubuntu 18.10 using gnome shell and wayland, dbus always crashes and you are welcomed with a dialog to report the crash. Looking into the file `/var/crash/_usr_bin_dbus-daemon.1000.crash` one can see that there is antoher bug, previoulsy reported as #1591548 (https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1591548) So may be the bug report is never sent, either ? /var/crash/_usr_bin_dbus-daemon.1000.crash content is: ProblemType: Crash Architecture: amd64 Date: Sun Dec 9 11:16:22 2018 DistroRelease: Ubuntu 18.10 ExecutablePath: /usr/bin/dbus-daemon ExecutableTimestamp: 1536206167 ProcCmdline: /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only ProcCwd: /home/solstice ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcMaps: 55c9bfc7a000-55c9bfc83000 r--p 08:07 787824 /usr/bin/dbus-daemon 55c9bfc83000-55c9bfca5000 r-xp 9000 08:07 787824 /usr/bin/dbus-daemon 55c9bfca5000-55c9bfcb3000 r--p 0002b000 08:07 787824 /usr/bin/dbus-daemon 55c9bfcb3000-55c9bfcb5000 r--p 00038000 08:07 787824 /usr/bin/dbus-daemon 55c9bfcb5000-55c9bfcb6000 rw-p 0003a000 08:07 787824 /usr/bin/dbus-daemon 55c9c1bd8000-55c9c1f1e000 rw-p 00:00 0 [heap] 7eff0278c000-7eff02792000 r--p 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff02792000-7eff027bd000 r-xp 6000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027bd000-7eff027cc000 r--p 00031000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027cc000-7eff027cf000 r--p 0003f000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027cf000-7eff027d rw-p 00042000 08:07 650406 /lib/x86_64-linux-gnu/libnss_systemd.so.2 7eff027d-7eff027d1000 rw-p 00:00 0 7eff027d1000-7eff027d4000 r--p 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027d4000-7eff027db000 r-xp 3000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027db000-7eff027de000 r--p a000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027de000-7eff027df000 r--p c000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027df000-7eff027e rw-p d000 08:07 654769 /lib/x86_64-linux-gnu/libnss_files-2.28.so 7eff027e-7eff027e6000 rw-p 00:00 0 7eff027e6000-7eff027ea000 r--p 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027ea000-7eff027f8000 r-xp 4000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027f8000-7eff027fd000 r--p 00012000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027fd000-7eff027fe000 r--p 00016000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027fe000-7eff027ff000 rw-p 00017000 08:07 654766 /lib/x86_64-linux-gnu/libnsl-2.28.so 7eff027ff000-7eff02801000 rw-p 00:00 0 7eff02801000-7eff02803000 r--p 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff02803000-7eff0280b000 r-xp 2000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280b000-7eff0280d000 r--p a000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280d000-7eff0280e000 r--p b000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280e000-7eff0280f000 rw-p c000 08:07 654771 /lib/x86_64-linux-gnu/libnss_nis-2.28.so 7eff0280f000-7eff02811000 r--p 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02811000-7eff02817000 r-xp 2000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02817000-7eff02818000 r--p 8000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so 7eff02818000-7eff02819000 r--p 8000 08:07 654767 /lib/x86_64-linux-gnu/libnss_compat-2.28.so
[Touch-packages] [Bug 1827685] [NEW] Corrupted background after automatic power suspend
Public bug reported: Another one graphical bug in a new Ubuntu 19.04, GNOME. Corrupted background appears every time after automatic power suspend. The background may show some buggy pictures, but usually shows a white screen. See attached images in .zip archive. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Fri May 3 16:31:10 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:8392] InstallationDate: Installed on 2019-04-29 (3 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 17-an0xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8392 dmi.board.vendor: HP dmi.board.version: 40.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-an0xx dmi.product.sku: 2FP35EA#ACB dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption disco ubuntu ** Attachment added: "Screenshots.zip" https://bugs.launchpad.net/bugs/1827685/+attachment/5261360/+files/Screenshots.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1827685 Title: Corrupted background after automatic power suspend Status in xorg package in Ubuntu: New Bug description: Another one graphical bug in a new Ubuntu 19.04, GNOME. Corrupted background appears every time after automatic power suspend. The background may show some buggy pictures, but usually shows a white screen. See attached images in .zip archive. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Fri May 3 16:31:10 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56,
[Touch-packages] [Bug 1827428] Re: Mouse cursor left freezed copy of itself
> What desktop environment do you use? GNOME. From the latest Ubuntu release (19.04). > Screenshot. I tried to capture it by screenshot. But freezed cursor is not shown on it. So I attach a photo. Freezed cursor is on the bottom left. ** Attachment added: "VrAmb8UYn0o.jpg" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827428/+attachment/5261036/+files/VrAmb8UYn0o.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1827428 Title: Mouse cursor left freezed copy of itself Status in xorg package in Ubuntu: Incomplete Bug description: Mouse cursor left freezed copy of itself over all the windows after login after lock screen. Functionality is not broken. It's just not aesthetic. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 2 16:10:09 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:8392] InstallationDate: Installed on 2019-04-29 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 17-an0xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8392 dmi.board.vendor: HP dmi.board.version: 40.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-an0xx dmi.product.sku: 2FP35EA#ACB dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827428/+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 1789538] [NEW] Kernel packages are not completely removed during automatic cleanup
Public bug reported: Some packages are left in "residual-config" state. This is confusing. Linux bor-Latitude-E5450 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 16:00:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux bor@bor-Latitude-E5450:~$ dpkg-query -W linux\* linux-base 4.5ubuntu1 linux-doc-4.15.0 linux-firmware 1.173.1 linux-firmware-snapdragon linux-generic 4.15.0.33.35 linux-generic-hwe-16.04 4.15.0.33.35 linux-headers linux-headers-3.0 linux-headers-4.15.0-30-generic linux-headers-4.15.0-32 4.15.0-32.35 linux-headers-4.15.0-32-generic 4.15.0-32.35 linux-headers-4.15.0-33 4.15.0-33.36 linux-headers-4.15.0-33-generic 4.15.0-33.36 linux-headers-686-pae linux-headers-amd64 linux-headers-generic 4.15.0.33.35 linux-headers-generic-hwe-16.04 4.15.0.33.35 linux-hwe-tools-4.15.0-29 4.15.0-29.31~16.04.1 linux-image linux-image-4.15.0-30-generic 4.15.0-30.32 linux-image-4.15.0-32-generic 4.15.0-32.35 linux-image-4.15.0-33-generic 4.15.0-33.36 linux-image-generic 4.15.0.33.35 linux-image-generic-hwe-16.04 4.15.0.33.35 linux-image-unsigned-4.15.0-30-generic linux-image-unsigned-4.15.0-32-generic linux-image-unsigned-4.15.0-33-generic linux-initramfs-tool linux-kernel-headers linux-kernel-headers-arm64-cross linux-kernel-headers-mips-cross linux-kernel-headers-mips64-cross linux-kernel-log-daemon linux-libc-dev:amd644.15.0-33.36 linux-libc-dev:i386 4.15.0-33.36 linux-libc-dev-arm64-cross 4.15.0-18.19cross1 linux-libc-dev-arm64-dcv1 linux-libc-dev-mips-cross 4.15.0-18.19cross1 linux-libc-dev-mips-dcv1 linux-libc-dev-mips64-cross 4.15.0-18.19cross1 linux-libc-dev-mips64-dcv1 linux-modules-4.15.0-30-generic 4.15.0-30.32 linux-modules-4.15.0-32-generic 4.15.0-32.35 linux-modules-4.15.0-33-generic 4.15.0-33.36 linux-modules-extra-4.15.0-30-generic 4.15.0-30.32 linux-modules-extra-4.15.0-32-generic 4.15.0-32.35 linux-modules-extra-4.15.0-33-generic 4.15.0-33.36 linux-restricted-common linux-signed-generic4.15.0.33.35 linux-signed-generic-hwe-16.04 4.15.0.33.35 linux-signed-image-generic 4.15.0.33.35 linux-signed-image-generic-hwe-16.044.15.0.33.35 linux-sound-base1.0.25+dfsg-0ubuntu5 linux-source-4.15.0 linux-tools linux-tools-4.15.0-32 4.15.0-32.35 linux-tools-4.15.0-32-generic 4.15.0-32.35 linux-tools-4.15.0-33 4.15.0-33.36 linux-tools-4.15.0-33-generic 4.15.0-33.36 linux-tools-common 4.15.0-33.36 linux-tools-generic 4.15.0.33.35 linux-tools-generic-hwe-16.04 4.15.0.33.35 bor@bor-Latitude-E5450:~$ or@bor-Latitude-E5450:~$ LC_ALL=C apt list linux-headers-4.15.0-30-generic linux-image-unsigned-4.15.0-30-generic linux-modules-4.15.0-30-generic linux-modules-extra-4.15.0-30-generic Listing... Done linux-headers-4.15.0-30-generic/bionic-updates,bionic-security 4.15.0-30.32 amd64 linux-image-unsigned-4.15.0-30-generic/bionic-updates,bionic-security 4.15.0-30.32 amd64 linux-modules-4.15.0-30-generic/bionic-updates,bionic-security,now 4.15.0-30.32 amd64 [residual-config] linux-modules-extra-4.15.0-30-generic/bionic-updates,bionic-security,now 4.15.0-30.32 amd64 [residual-config] bor@bor-Latitude-E5450:~$ bor@bor-Latitude-E5450:~$ LC_ALL=C sudo apt purge linux-image-4.15.0-30-generic linux-modules-4.15.0-30-generic linux-modules-extra-4.15.0-30-generic Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: extlinux g++-4.8 gcc-5-cross-base giblib1 libaec0 libatomic1-arm64-cross libbabeltrace-ctf1 libbonobo2-common libboost-chrono1.58.0 libboost-system1.58.0 libc6-dev-arm64-cross libebml4v5 libffi-dev libgcc1-arm64-cross libgomp1-arm64-cross libisc-export160 libjasper1:i386 libjson-c2:i386 libllvm5.0:i386 libmysofa libobjc-5-dev libobjc4 liborbit-2-0 libpango-perl libtorrent-rasterbar8 libva-drm1 libva-wayland1 libx264-148 linux-generic-hwe-16.04 linux-hwe-tools-4.15.0-29 linux-libc-dev-arm64-cross linux-libc-dev-mips64-cross python-ndg-httpsclient qml-module-qtgraphicaleffects qml-module-qtquick-dialogs qml-module-qtquick-privatewidgets qml-module-qtwebkit qml-module-ubuntu-performancemetrics Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: linux-image-4.15.0-30-generic* linux-modules-4.15.0-30-generic* linux-modules-extra-4.15.0-30-generic* 0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 301437 files and directories currently installed.) Purging configuration files for linux-modules-extra-4.15.0-30-generic (4.15.0-30.32) ... Purging configuration files for linux-modules-4.15.0-30-generic (4.15.0-30.32) ... dpkg: warning: while removing linux-modules-4.15.0-30-generic, directory
[Touch-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
I can also provide information needed or test possible solutions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1767065] Re: [regression] pulseaudio+bluetooth crash causing user to be logged out (since pulseaudio 1:8.0-0ubuntu3.9)
Spoke too soon, it happened again. Seems to be from pulse and bluetooth. Why is systemd still trying to start bluetooth when it is off in the bios and the service is disabled. I really don't understand what I can try more to debug. Apr 30 11:31:09 ESS-PC26 org.gtk.vfs.AfcVolumeMonitor[8928]: Volume monitor alive Apr 30 11:31:10 ESS-PC26 org.gnome.ScreenSaver[8928]: ** Message: Lost the name, shutting down. Apr 30 11:31:16 ESS-PC26 rtkit-daemon[1501]: Supervising 7 threads of 2 processes of 2 users. Apr 30 11:31:16 ESS-PC26 rtkit-daemon[1501]: Successfully made thread 9456 of process 9266 (n/a) owned by '1001' RT at priority 5. Apr 30 11:31:16 ESS-PC26 rtkit-daemon[1501]: Supervising 8 threads of 2 processes of 2 users. Apr 30 11:31:16 ESS-PC26 rtkit-daemon[1501]: Successfully made thread 9458 of process 9458 (n/a) owned by '1001' high priority at nice level -11. Apr 30 11:31:16 ESS-PC26 rtkit-daemon[1501]: Supervising 9 threads of 3 processes of 2 users. Apr 30 11:31:16 ESS-PC26 pulseaudio[9458]: [pulseaudio] pid.c: Daemon already running. Apr 30 11:31:16 ESS-PC26 rtkit-daemon[1501]: Successfully made thread 9460 of process 9460 (n/a) owned by '1001' high priority at nice level -11. Apr 30 11:31:16 ESS-PC26 rtkit-daemon[1501]: Supervising 9 threads of 3 processes of 2 users. Apr 30 11:31:16 ESS-PC26 pulseaudio[9460]: [pulseaudio] pid.c: Daemon already running. Apr 30 11:31:16 ESS-PC26 dbus[1148]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' Apr 30 11:31:16 ESS-PC26 gnome-session[9150]: (uint32 1,) Apr 30 11:31:16 ESS-PC26 systemd[1]: Starting Locale Service... Apr 30 11:31:16 ESS-PC26 gnome-session-binary[9150]: Entering running state Apr 30 11:31:16 ESS-PC26 gnome-session[9150]: (process:9493): indicator-application-service-WARNING **: Unable to get watcher name 'org.kde.StatusNotifierWatcher' Apr 30 11:31:16 ESS-PC26 gnome-session[9150]: (process:9493): indicator-application-service-WARNING **: Name Lost Apr 30 11:31:16 ESS-PC26 polkitd(authority=local)[1278]: Registered Authentication Agent for unix-session:c4 (system bus name :1.181 [/usr/lib/policykit-1-gnome/polkit-gnome-authentication-a Apr 30 11:31:16 ESS-PC26 dbus[1148]: [system] Successfully activated service 'org.freedesktop.locale1' Apr 30 11:31:16 ESS-PC26 systemd[1]: Started Locale Service. Apr 30 11:31:22 ESS-PC26 dbus[1148]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' Apr 30 11:31:22 ESS-PC26 dbus[1148]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found. -- 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/1767065 Title: [regression] pulseaudio+bluetooth crash causing user to be logged out (since pulseaudio 1:8.0-0ubuntu3.9) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I'm a sysadmin and have gotten multiple reports recently from users of them randomly getting logged out of their machines. From what I can tell from the journalctl printout this appears immediately after either bluetoothd or pulsaudio crashes. This is happening multiple time each day for each user. It doesn't happen to all users, but the reports seem to be getting more frequent by the day. From what I have noticed there recently was an update for pulseaudio and its bluetooth integration. Here is the journalctl printout: Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSource Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSink Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of process 8042 (n/a) owned by '108' high priority at nice level -11. Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 processes of 1 users. Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already running. Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus can't be made Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): session closed for user lightdm We are running Ubuntu 16.04 LTS with the latest updated. EDIT: Worth mentioning, this error happens with both Unity and Gnome as desktop environments. --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC1D7p',
[Touch-packages] [Bug 1767065] Re: [regression] pulseaudio+bluetooth crash causing user to be logged out (since pulseaudio 1:8.0-0ubuntu3.9)
Now this is something really weird. I said for the hell of it to try and see if this would fix the issue. I was thinking that to save energy maybe the system tried to power down wifi/bluetooth and such during idle times. I added intel_idle.max_cstate=1 to the kernel start options in the grub config. The main person I'm testing with hasn't reported any forced logouts since this change. Based on this solution: https://askubuntu.com/questions/761706/ubuntu-15-10-and-16-04-keep- freezing-randomly Is the CPU/ ACPI calls going into a lower state causing problems with the login/logout state of the machine? This might not have anything to do with pulse, but it opens an entire new can of worms. -- 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/1767065 Title: [regression] pulseaudio+bluetooth crash causing user to be logged out (since pulseaudio 1:8.0-0ubuntu3.9) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I'm a sysadmin and have gotten multiple reports recently from users of them randomly getting logged out of their machines. From what I can tell from the journalctl printout this appears immediately after either bluetoothd or pulsaudio crashes. This is happening multiple time each day for each user. It doesn't happen to all users, but the reports seem to be getting more frequent by the day. From what I have noticed there recently was an update for pulseaudio and its bluetooth integration. Here is the journalctl printout: Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSource Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSink Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of process 8042 (n/a) owned by '108' high priority at nice level -11. Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 processes of 1 users. Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already running. Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus can't be made Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): session closed for user lightdm We are running Ubuntu 16.04 LTS with the latest updated. EDIT: Worth mentioning, this error happens with both Unity and Gnome as desktop environments. --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', '/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: pulseaudio 1:8.0-0ubuntu3.9 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE 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.:bvr1301:bd03/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE: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 --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p',
[Touch-packages] [Bug 1767065] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1767065/+attachment/5128204/+files/ProcEnviron.txt -- 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/1767065 Title: pulseaudio+bluetooth crash causing user to be logged out Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I'm a sysadmin and have gotten multiple reports recently from users of them randomly getting logged out of their machines. From what I can tell from the journalctl printout this appears immediately after either bluetoothd or pulsaudio crashes. This is happening multiple time each day for each user. It doesn't happen to all users, but the reports seem to be getting more frequent by the day. From what I have noticed there recently was an update for pulseaudio and its bluetooth integration. Here is the journalctl printout: Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSource Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSink Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of process 8042 (n/a) owned by '108' high priority at nice level -11. Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 processes of 1 users. Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already running. Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus can't be made Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): session closed for user lightdm We are running Ubuntu 16.04 LTS with the latest updated. EDIT: Worth mentioning, this error happens with both Unity and Gnome as desktop environments. --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', '/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: pulseaudio 1:8.0-0ubuntu3.9 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE 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.:bvr1301:bd03/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE: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 --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/controlC2', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: pulseaudio 1:8.0-0ubuntu3.9 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon
[Touch-packages] [Bug 1767065] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1767065/+attachment/5128202/+files/Dependencies.txt -- 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/1767065 Title: pulseaudio+bluetooth crash causing user to be logged out Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I'm a sysadmin and have gotten multiple reports recently from users of them randomly getting logged out of their machines. From what I can tell from the journalctl printout this appears immediately after either bluetoothd or pulsaudio crashes. This is happening multiple time each day for each user. It doesn't happen to all users, but the reports seem to be getting more frequent by the day. From what I have noticed there recently was an update for pulseaudio and its bluetooth integration. Here is the journalctl printout: Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSource Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSink Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of process 8042 (n/a) owned by '108' high priority at nice level -11. Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 processes of 1 users. Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already running. Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus can't be made Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): session closed for user lightdm We are running Ubuntu 16.04 LTS with the latest updated. EDIT: Worth mentioning, this error happens with both Unity and Gnome as desktop environments. --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', '/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: pulseaudio 1:8.0-0ubuntu3.9 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE 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.:bvr1301:bd03/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE: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 --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/controlC2', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: pulseaudio 1:8.0-0ubuntu3.9 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon
[Touch-packages] [Bug 1767065] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1767065/+attachment/5128199/+files/Dependencies.txt ** Description changed: Hello, I'm a sysadmin and have gotten multiple reports recently from users of them randomly getting logged out of their machines. From what I can tell from the journalctl printout this appears immediately after either bluetoothd or pulsaudio crashes. This is happening multiple time each day for each user. It doesn't happen to all users, but the reports seem to be getting more frequent by the day. From what I have noticed there recently was an update for pulseaudio and its bluetooth integration. Here is the journalctl printout: Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSource Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSink Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of process 8042 (n/a) owned by '108' high priority at nice level -11. Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 processes of 1 users. Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already running. Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus can't be made Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): session closed for user lightdm We are running Ubuntu 16.04 LTS with the latest updated. EDIT: Worth mentioning, this error happens with both Unity and Gnome as desktop environments. --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', '/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: pulseaudio 1:8.0-0ubuntu3.9 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE 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.:bvr1301:bd03/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE: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 + --- + ApportVersion: 2.20.1-0ubuntu2.16 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/controlC2', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 16.04 + NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia + Package: pulseaudio 1:8.0-0ubuntu3.9 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + Tags: xenial + Uname: Linux 4.13.0-39-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/07/2018 +
[Touch-packages] [Bug 1767065] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1767065/+attachment/5128200/+files/AlsaInfo.txt -- 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/1767065 Title: pulseaudio+bluetooth crash causing user to be logged out Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I'm a sysadmin and have gotten multiple reports recently from users of them randomly getting logged out of their machines. From what I can tell from the journalctl printout this appears immediately after either bluetoothd or pulsaudio crashes. This is happening multiple time each day for each user. It doesn't happen to all users, but the reports seem to be getting more frequent by the day. From what I have noticed there recently was an update for pulseaudio and its bluetooth integration. Here is the journalctl printout: Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSource Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSink Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of process 8042 (n/a) owned by '108' high priority at nice level -11. Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 processes of 1 users. Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already running. Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus can't be made Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): session closed for user lightdm We are running Ubuntu 16.04 LTS with the latest updated. EDIT: Worth mentioning, this error happens with both Unity and Gnome as desktop environments. --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', '/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: pulseaudio 1:8.0-0ubuntu3.9 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE 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.:bvr1301:bd03/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE: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 --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/controlC2', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: pulseaudio 1:8.0-0ubuntu3.9 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running,
[Touch-packages] [Bug 1767065] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1767065/+attachment/5128201/+files/CurrentDmesg.txt -- 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/1767065 Title: pulseaudio+bluetooth crash causing user to be logged out Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I'm a sysadmin and have gotten multiple reports recently from users of them randomly getting logged out of their machines. From what I can tell from the journalctl printout this appears immediately after either bluetoothd or pulsaudio crashes. This is happening multiple time each day for each user. It doesn't happen to all users, but the reports seem to be getting more frequent by the day. From what I have noticed there recently was an update for pulseaudio and its bluetooth integration. Here is the journalctl printout: Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSource Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSink Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of process 8042 (n/a) owned by '108' high priority at nice level -11. Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 processes of 1 users. Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already running. Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus can't be made Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): session closed for user lightdm We are running Ubuntu 16.04 LTS with the latest updated. EDIT: Worth mentioning, this error happens with both Unity and Gnome as desktop environments. --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', '/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: pulseaudio 1:8.0-0ubuntu3.9 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE 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.:bvr1301:bd03/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE: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 --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/controlC2', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: pulseaudio 1:8.0-0ubuntu3.9 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon
[Touch-packages] [Bug 1767065] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1767065/+attachment/5128198/+files/CurrentDmesg.txt -- 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/1767065 Title: pulseaudio+bluetooth crash causing user to be logged out Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I'm a sysadmin and have gotten multiple reports recently from users of them randomly getting logged out of their machines. From what I can tell from the journalctl printout this appears immediately after either bluetoothd or pulsaudio crashes. This is happening multiple time each day for each user. It doesn't happen to all users, but the reports seem to be getting more frequent by the day. From what I have noticed there recently was an update for pulseaudio and its bluetooth integration. Here is the journalctl printout: Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSource Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSink Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of process 8042 (n/a) owned by '108' high priority at nice level -11. Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 processes of 1 users. Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already running. Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus can't be made Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): session closed for user lightdm We are running Ubuntu 16.04 LTS with the latest updated. EDIT: Worth mentioning, this error happens with both Unity and Gnome as desktop environments. --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', '/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: pulseaudio 1:8.0-0ubuntu3.9 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE 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.:bvr1301:bd03/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE: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 --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/controlC2', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: pulseaudio 1:8.0-0ubuntu3.9 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon
[Touch-packages] [Bug 1767065] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1767065/+attachment/5128203/+files/ProcCpuinfoMinimal.txt -- 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/1767065 Title: pulseaudio+bluetooth crash causing user to be logged out Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I'm a sysadmin and have gotten multiple reports recently from users of them randomly getting logged out of their machines. From what I can tell from the journalctl printout this appears immediately after either bluetoothd or pulsaudio crashes. This is happening multiple time each day for each user. It doesn't happen to all users, but the reports seem to be getting more frequent by the day. From what I have noticed there recently was an update for pulseaudio and its bluetooth integration. Here is the journalctl printout: Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSource Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSink Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of process 8042 (n/a) owned by '108' high priority at nice level -11. Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 processes of 1 users. Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already running. Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus can't be made Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): session closed for user lightdm We are running Ubuntu 16.04 LTS with the latest updated. EDIT: Worth mentioning, this error happens with both Unity and Gnome as desktop environments. --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', '/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: pulseaudio 1:8.0-0ubuntu3.9 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE 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.:bvr1301:bd03/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE: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 --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/controlC2', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: pulseaudio 1:8.0-0ubuntu3.9 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
[Touch-packages] [Bug 1767065] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1767065/+attachment/5128197/+files/AlsaInfo.txt -- 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/1767065 Title: pulseaudio+bluetooth crash causing user to be logged out Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I'm a sysadmin and have gotten multiple reports recently from users of them randomly getting logged out of their machines. From what I can tell from the journalctl printout this appears immediately after either bluetoothd or pulsaudio crashes. This is happening multiple time each day for each user. It doesn't happen to all users, but the reports seem to be getting more frequent by the day. From what I have noticed there recently was an update for pulseaudio and its bluetooth integration. Here is the journalctl printout: Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSource Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSink Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of process 8042 (n/a) owned by '108' high priority at nice level -11. Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 processes of 1 users. Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already running. Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus can't be made Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): session closed for user lightdm We are running Ubuntu 16.04 LTS with the latest updated. EDIT: Worth mentioning, this error happens with both Unity and Gnome as desktop environments. --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', '/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: pulseaudio 1:8.0-0ubuntu3.9 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: xenial Uname: Linux 4.13.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: PRIME X299-DELUXE 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.:bvr1301:bd03/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE: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 --- ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC2D8p', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC2D7p', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/controlC2', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: pulseaudio 1:8.0-0ubuntu3.9 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running,
[Touch-packages] [Bug 1767065] Re: pulseaudio+bluetooth crash causing user to be logged out
Another update. After truning off pulseaudio yesterday, the system didn't crash as fast as before, but it did eventually lock up a couple of times. The logs seems similar even without pulse, still beginning with the bluetooth service. After this I completely turned off bluetooth from the BIOS of the machine. This seemed to have solved the issue until a few moments ago when the bluetoothservice tried to start something again. I have now disabled the bluetooth service. I hope it doesn't do anything more. Here's how the system locks-up now: Apr 27 09:37:26 ESS-PC26 dbus[1187]: [system] Failed to activate service 'org.bluez': timed out Apr 27 09:37:26 ESS-PC26 pulseaudio[2214]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out Apr 27 09:37:26 ESS-PC26 pulseaudio[1521]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out The system freezes for multiple seconds then recovers. I've now run apport-collect and authorized it for one week. Hope this helps. ** Tags added: apport-collected ** Description changed: Hello, I'm a sysadmin and have gotten multiple reports recently from users of them randomly getting logged out of their machines. From what I can tell from the journalctl printout this appears immediately after either bluetoothd or pulsaudio crashes. This is happening multiple time each day for each user. It doesn't happen to all users, but the reports seem to be getting more frequent by the day. From what I have noticed there recently was an update for pulseaudio and its bluetooth integration. Here is the journalctl printout: Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSource Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSink Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of process 8042 (n/a) owned by '108' high priority at nice level -11. Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 processes of 1 users. Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already running. Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus can't be made Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): session closed for user lightdm We are running Ubuntu 16.04 LTS with the latest updated. - EDIT: Worth mentioning, this error happens with both Unity and Gnome as - desktop environments. + EDIT: Worth mentioning, this error happens with both Unity and Gnome as desktop environments. + --- + ApportVersion: 2.20.1-0ubuntu2.16 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D9p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC2D8p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', '/dev/snd/pcmC2D3p', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 16.04 + NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia + Package: pulseaudio 1:8.0-0ubuntu3.9 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + Tags: xenial + Uname: Linux 4.13.0-39-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/07/2018 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 1301 + dmi.board.asset.tag: Default string + dmi.board.name: PRIME X299-DELUXE + 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.:bvr1301:bd03/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX299-DELUXE: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 -- You received this bug notification because you are
[Touch-packages] [Bug 1767065] Re: pulseaudio+bluetooth crash causing user to be logged out
Update, I noticed the pattern so far and turning off pulseaudio seems to have stopped the behaviour. I obviously can't leave the system without sound, so I'm still looking for a permanent fix. The pattern is allways like this: Apr 26 15:06:07 ESS-PC26 bluetoothd[11243]: Endpoint registered: sender=:1.445 path=/MediaEndpoint/A2DPSource Apr 26 15:06:07 ESS-PC26 bluetoothd[11243]: Endpoint registered: sender=:1.445 path=/MediaEndpoint/A2DPSink Apr 26 15:06:07 ESS-PC26 pulseaudio[12799]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.of Apr 26 15:06:07 ESS-PC26 bluetoothd[11243]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98) Apr 26 15:06:07 ESS-PC26 rtkit-daemon[1524]: Successfully made thread 12829 of process 12829 (n/a) owned by '108' high priority at nice level -11. Apr 26 15:06:07 ESS-PC26 rtkit-daemon[1524]: Supervising 9 threads of 3 processes of 2 users. Apr 26 15:06:07 ESS-PC26 pulseaudio[12829]: [pulseaudio] pid.c: Daemon already running. Apr 26 15:06:14 ESS-PC26 org.gtk.vfs.Daemon[12708]: A connection to the bus can't be made Bluetooth tries to register a device or something, pulse fails and system loggs out. My current workaround is to completely turn off pulseaudio by creating a ~/.pulse/client.conf file with autospawn=no inside. As I've already mentioned before, pulseaudio crashing leves no crash log. How an I get this fixed/debugged? -- 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/1767065 Title: pulseaudio+bluetooth crash causing user to be logged out Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I'm a sysadmin and have gotten multiple reports recently from users of them randomly getting logged out of their machines. From what I can tell from the journalctl printout this appears immediately after either bluetoothd or pulsaudio crashes. This is happening multiple time each day for each user. It doesn't happen to all users, but the reports seem to be getting more frequent by the day. From what I have noticed there recently was an update for pulseaudio and its bluetooth integration. Here is the journalctl printout: Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSource Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSink Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of process 8042 (n/a) owned by '108' high priority at nice level -11. Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 processes of 1 users. Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already running. Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus can't be made Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): session closed for user lightdm We are running Ubuntu 16.04 LTS with the latest updated. EDIT: Worth mentioning, this error happens with both Unity and Gnome as desktop environments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767065/+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 1767065] Re: pulseaudio+bluetooth crash causing user to be logged out
Went, did step 1 and 2, looked in /var/crash and there was nothing. There are no crash logs in that location for the event that just happened. Attached another printout of journalctl. From what I can tell the system went in full shutdown mode and logged the user out. ** Attachment added: "journalclt printout" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767065/+attachment/5127533/+files/crash2.txt -- 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/1767065 Title: pulseaudio+bluetooth crash causing user to be logged out Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I'm a sysadmin and have gotten multiple reports recently from users of them randomly getting logged out of their machines. From what I can tell from the journalctl printout this appears immediately after either bluetoothd or pulsaudio crashes. This is happening multiple time each day for each user. It doesn't happen to all users, but the reports seem to be getting more frequent by the day. From what I have noticed there recently was an update for pulseaudio and its bluetooth integration. Here is the journalctl printout: Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSource Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSink Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of process 8042 (n/a) owned by '108' high priority at nice level -11. Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 processes of 1 users. Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already running. Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus can't be made Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): session closed for user lightdm We are running Ubuntu 16.04 LTS with the latest updated. EDIT: Worth mentioning, this error happens with both Unity and Gnome as desktop environments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767065/+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 1767065] Re: pulseaudio+bluetooth crash causing user to be logged out
** Description changed: Hello, I'm a sysadmin and have gotten multiple reports recently from users of them randomly getting logged out of their machines. From what I can tell from the journalctl printout this appears immediately after either bluetoothd or pulsaudio crashes. This is happening multiple time each day for each user. It doesn't happen to all users, but the reports seem to be getting more frequent by the day. From what I have noticed there recently was an update for pulseaudio and its bluetooth integration. Here is the journalctl printout: Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSource Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSink Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of process 8042 (n/a) owned by '108' high priority at nice level -11. Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 processes of 1 users. Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already running. Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus can't be made Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): session closed for user lightdm We are running Ubuntu 16.04 LTS with the latest updated. + + EDIT: Worth mentioning, this error happens with both Unity and Gnome as + desktop environments. -- 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/1767065 Title: pulseaudio+bluetooth crash causing user to be logged out Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I'm a sysadmin and have gotten multiple reports recently from users of them randomly getting logged out of their machines. From what I can tell from the journalctl printout this appears immediately after either bluetoothd or pulsaudio crashes. This is happening multiple time each day for each user. It doesn't happen to all users, but the reports seem to be getting more frequent by the day. From what I have noticed there recently was an update for pulseaudio and its bluetooth integration. Here is the journalctl printout: Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSource Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSink Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of process 8042 (n/a) owned by '108' high priority at nice level -11. Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 processes of 1 users. Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already running. Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus can't be made Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): session closed for user lightdm We are running Ubuntu 16.04 LTS with the latest updated. EDIT: Worth mentioning, this error happens with both Unity and Gnome as desktop environments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767065/+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 1767065] [NEW] pulseaudio+bluetooth crash causing user to be logged out
Public bug reported: Hello, I'm a sysadmin and have gotten multiple reports recently from users of them randomly getting logged out of their machines. From what I can tell from the journalctl printout this appears immediately after either bluetoothd or pulsaudio crashes. This is happening multiple time each day for each user. It doesn't happen to all users, but the reports seem to be getting more frequent by the day. From what I have noticed there recently was an update for pulseaudio and its bluetooth integration. Here is the journalctl printout: Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSource Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSink Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of process 8042 (n/a) owned by '108' high priority at nice level -11. Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 processes of 1 users. Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already running. Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus can't be made Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): session closed for user lightdm We are running Ubuntu 16.04 LTS with the latest updated. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** No longer affects: linphone (Ubuntu) -- 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/1767065 Title: pulseaudio+bluetooth crash causing user to be logged out Status in pulseaudio package in Ubuntu: New Bug description: Hello, I'm a sysadmin and have gotten multiple reports recently from users of them randomly getting logged out of their machines. From what I can tell from the journalctl printout this appears immediately after either bluetoothd or pulsaudio crashes. This is happening multiple time each day for each user. It doesn't happen to all users, but the reports seem to be getting more frequent by the day. From what I have noticed there recently was an update for pulseaudio and its bluetooth integration. Here is the journalctl printout: Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSource Apr 25 10:50:53 ESS-PC26 bluetoothd[1168]: Endpoint registered: sender=:1.219 path=/MediaEndpoint/A2DPSink Apr 25 10:50:53 ESS-PC26 pulseaudio[8026]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Successfully made thread 8042 of process 8042 (n/a) owned by '108' high priority at nice level -11. Apr 25 10:50:53 ESS-PC26 rtkit-daemon[1515]: Supervising 5 threads of 2 processes of 1 users. Apr 25 10:50:53 ESS-PC26 pulseaudio[8042]: [pulseaudio] pid.c: Daemon already running. Apr 25 10:51:00 ESS-PC26 org.gtk.vfs.Daemon[7931]: A connection to the bus can't be made Apr 25 10:51:00 ESS-PC26 lightdm[7915]: pam_unix(lightdm-greeter:session): session closed for user lightdm We are running Ubuntu 16.04 LTS with the latest updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1767065/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade
When will this be available in the main repositories? -- 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/1735594 Title: [regression] compiz crashes after Mesa upgrade Status in mesa package in Ubuntu: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: [Impact] When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] This is caused by a mesa upgrade, which added a patch for bug #1727401. The crasher is reproduced on: - gen4 / gen5 Intel - if using modesetting X driver, like when xserver-xorg-video-intel is not installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults to modesetting) [Test case] Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash. [Regression potential] The backported patches need to be tested, here for regressions and on 1727401 that they fix the original bug (again). Best to test on a wide array of Intel HW: gen4 (965GM/GM45/G45) gen5 (Ironlake) gen6 (Sandy Bridge) gen7 (Bay Trail, Ivy Bridge, Haswell) gen8 (Braswell, Broadwell) gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1737805] [NEW] package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: package libglib2.0-0:amd64 is already installed and configured
Public bug reported: the instalation failed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0:amd64 2.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98 Uname: Linux 4.4.0-103-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.14 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Tue Dec 12 20:28:43 2017 DuplicateSignature: package:libglib2.0-0:amd64:2.48.2-0ubuntu1 Unpacking qtdeclarative5-dialogs-plugin:amd64 (5.5.1-1ubuntu1) ... dpkg: error processing package uuid-runtime (--configure): package uuid-runtime is already installed and configured ErrorMessage: package libglib2.0-0:amd64 is already installed and configured InstallationDate: Installed on 2016-07-07 (523 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: glib2.0 Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: package libglib2.0-0:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1737805 Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: package libglib2.0-0:amd64 is already installed and configured Status in glib2.0 package in Ubuntu: New Bug description: the instalation failed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0:amd64 2.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98 Uname: Linux 4.4.0-103-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.14 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Tue Dec 12 20:28:43 2017 DuplicateSignature: package:libglib2.0-0:amd64:2.48.2-0ubuntu1 Unpacking qtdeclarative5-dialogs-plugin:amd64 (5.5.1-1ubuntu1) ... dpkg: error processing package uuid-runtime (--configure): package uuid-runtime is already installed and configured ErrorMessage: package libglib2.0-0:amd64 is already installed and configured InstallationDate: Installed on 2016-07-07 (523 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: glib2.0 Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: package libglib2.0-0:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1737805/+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 1736825] Re: CFQ is default scheduler (incorrect udev rule)
** Description changed: I've found out that all my drives uses CFQ scheduler by default, since - that udev rule (60-ssd-scheduler.rules) for use CFQ for rotating disk is - useless. I heard that Ubuntu uses Deadline scheduler by default, but for - somewhat reason it's not that on my system. + that udev rule (60-ssd-scheduler.rules) that says use CFQ for rotating + disk is useless. I belive that Ubuntu uses Deadline scheduler by + default, but for somewhat reason it's not that on my system. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu21 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: KDE CustomUdevRuleFiles: 60-vboxdrv.rules 60-ssd-scheduler.rules Date: Thu Dec 7 03:11:16 2017 InstallationDate: Installed on 2014-11-26 (1106 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic root=UUID=33a02342-70da-4f8d-9868-2f8e7330ec90 ro SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-07-28 (496 days ago) dmi.bios.date: 09/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H67-M dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3901:bd09/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- 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/1736825 Title: CFQ is default scheduler (incorrect udev rule) Status in systemd package in Ubuntu: New Bug description: I've found out that all my drives uses CFQ scheduler by default, since that udev rule (60-ssd-scheduler.rules) that says use CFQ for rotating disk is useless. I belive that Ubuntu uses Deadline scheduler by default, but for somewhat reason it's not that on my system. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu21 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: KDE CustomUdevRuleFiles: 60-vboxdrv.rules 60-ssd-scheduler.rules Date: Thu Dec 7 03:11:16 2017 InstallationDate: Installed on 2014-11-26 (1106 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic root=UUID=33a02342-70da-4f8d-9868-2f8e7330ec90 ro SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-07-28 (496 days ago) dmi.bios.date: 09/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H67-M dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3901:bd09/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-M:rvrRevX.0x: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/systemd/+bug/1736825/+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 1736825] [NEW] CFQ is default scheduler (incorrect udev rule)
Public bug reported: I've found out that all my drives uses CFQ scheduler by default, since that udev rule (60-ssd-scheduler.rules) for use CFQ for rotating disk is useless. I heard that Ubuntu uses Deadline scheduler by default, but for somewhat reason it's not that on my system. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu21 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: KDE CustomUdevRuleFiles: 60-vboxdrv.rules 60-ssd-scheduler.rules Date: Thu Dec 7 03:11:16 2017 InstallationDate: Installed on 2014-11-26 (1106 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic root=UUID=33a02342-70da-4f8d-9868-2f8e7330ec90 ro SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-07-28 (496 days ago) dmi.bios.date: 09/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H67-M dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3901:bd09/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1736825 Title: CFQ is default scheduler (incorrect udev rule) Status in systemd package in Ubuntu: New Bug description: I've found out that all my drives uses CFQ scheduler by default, since that udev rule (60-ssd-scheduler.rules) for use CFQ for rotating disk is useless. I heard that Ubuntu uses Deadline scheduler by default, but for somewhat reason it's not that on my system. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu21 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: KDE CustomUdevRuleFiles: 60-vboxdrv.rules 60-ssd-scheduler.rules Date: Thu Dec 7 03:11:16 2017 InstallationDate: Installed on 2014-11-26 (1106 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic root=UUID=33a02342-70da-4f8d-9868-2f8e7330ec90 ro SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-07-28 (496 days ago) dmi.bios.date: 09/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H67-M dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3901:bd09/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-M:rvrRevX.0x: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/systemd/+bug/1736825/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
Such a shame... This bug will probably never get fixed :( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1709852] [NEW] PCI/internal sound card not detected and no soud
Public bug reported: I have installed windows 10 and it was working ok sound and wifi. When i intalled ubuntu mate or ubuntu 16.04 it dosnt work. Both HDMI and 3.5mm ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Thu Aug 10 14:02:02 2017 InstallationDate: Installed on 2017-08-09 (0 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YB2001 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 35 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYB2001:bd04/27/2017:svnBeelink:pnBT3Pro:pvrBT3ProV01:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct35:cvrToBeFilledByO.E.M.: dmi.product.name: BT3 Pro dmi.product.version: BT3 Pro V01 dmi.sys.vendor: Beelink ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1709852 Title: PCI/internal sound card not detected and no soud Status in alsa-driver package in Ubuntu: New Bug description: I have installed windows 10 and it was working ok sound and wifi. When i intalled ubuntu mate or ubuntu 16.04 it dosnt work. Both HDMI and 3.5mm ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Thu Aug 10 14:02:02 2017 InstallationDate: Installed on 2017-08-09 (0 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YB2001 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 35 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYB2001:bd04/27/2017:svnBeelink:pnBT3Pro:pvrBT3ProV01:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct35:cvrToBeFilledByO.E.M.: dmi.product.name: BT3 Pro dmi.product.version: BT3 Pro V01 dmi.sys.vendor: Beelink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1709852/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
SD Card hasn't been fixed yet but sound works after you use the kernel I have compiled: https://github.com/Grippentech/Asus-E200HA-Linux-Post-Install-Script I'm working on making a smaller version of the kernel as the one I have right now is quite bloated (has support for almost every device that can be supported) but that's 2+ weeks away as I'm on vacation without the E200ha. Hopefully the changes that Takashi Iwai made with the rest of the guys working on the Sound side will get merged into mainstream kernel 4.13 but that's just speculation, not based on anything. I know they're trying to get it into mainstream tho, if Linus and the devs approve it is another issue entirely. I'm not aware on anybody working on the SD card side of things, I'm not sure where I'd start either. If someone has some insight feel free to chip in. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: 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/alsa-driver/+bug/1563110/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
Any updates? The fact that I can't make the subwoofer to work properly(at all) is the only reason I can't fully switch to Linux :( ** Also affects: alsa-driver (Fedora) Importance: Undecided Status: New ** No longer affects: alsa-driver (Fedora) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1525477] Re: X server crash when pasting selection using middle button in Chromium
This is still present in 16.04.2 with X 1.19.3. ** Changed in: xorg (Ubuntu) Status: Fix Released => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1525477 Title: X server crash when pasting selection using middle button in Chromium Status in xorg package in Ubuntu: New Bug description: Description: Ubuntu 14.04.3 LTS Release: 14.04 xorg 1:7.7+1ubuntu8.1 Select any text; use middle button to paste selection in Chromium (I observed it pasting in URL bar or in any form text input field, including previous attempt to report this bug :) ). Session crashes. It does not happen, when either pasting into different application (like terminal) or wen use Copy - Paste instead of middle button. I noticed it about a week ago, so it must be some recent change; I use selection paste often enough to notice something like this before. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.2.0-19.23~14.04.1-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Dec 12 11:09:22 2015 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:062b] InstallationDate: Installed on 2015-07-02 (162 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-:128M vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/19/2015:svnDellInc.:pnLatitudeE5450:pvr01:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Dec 12 11:08:11 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1133 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1525477/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
Hey Akli, please try to run it again, should work now. Sorry for the delay but I had to have another user report this for me to see it. In the future please e-mail me or send an issue request on the Github repo. Also, nice username ;) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: 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/alsa-driver/+bug/1563110/+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 1628591] Re: ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention
In Debian 9 Stretch, works as it should. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1628591 Title: ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention Status in ifupdown package in Ubuntu: Confirmed Bug description: The regular expressions used in /etc/network/if-post-down.d/vlan and /etc/network/if-pre-up.d/vlan do not match the name of my network card enp4s0f0. This can be fixed by broadening the regular expression. This is only a problem when the device is a vlan device! See below for the fix that worked on my system. if-pre-up: #!/bin/sh # Most of this stuff is to enable vlans case "$IFACE" in # Ignore any alias (#272891) which uses : *:*) exit 0 ;; vlan0*) vconfig set_name_type VLAN_PLUS_VID VLANID=`echo $IFACE|sed "s/vlan0*//"` ;; vlan*) vconfig set_name_type VLAN_PLUS_VID_NO_PAD VLANID=`echo $IFACE|sed "s/vlan0*//"` ;; eth*.0*|bond*.0*|wlan*.0*|em*.0*|p[0-9]*.0*|enp[0-9]*.0*) vconfig set_name_type DEV_PLUS_VID VLANID=`echo $IFACE|sed "s/eth[0-9][0-9]*\.0*//g;s/bond[0-9][0-9]*\.0*//g;s/wlan[0-9][0-9]*\.0*//g;s/em[0-9][0-9]*\.0*//g;s/p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\.0*//g;s/enp[0-9]s[0-9]f[0-9]\.0*//g"` IF_VLAN_RAW_DEVICE=`echo $IFACE|sed "s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/;s/\(enp[0-9]s[0-9]f[0-9]\)\..*/\1/"` ;; eth*.*|bond*.*|wlan*.*|em*.*|p[0-9]*.*|enp[0-9]*.*) vconfig set_name_type DEV_PLUS_VID_NO_PAD VLANID=`echo $IFACE|sed "s/eth[0-9][0-9]*\.0*//g;s/bond[0-9][0-9]*\.0*//g;s/wlan[0-9][0-9]*\.0*//g;s/em[0-9][0-9]*\.0*//g;s/p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\.0*//g;s/enp[0-9]s[0-9]f[0-9]\.//g"` IF_VLAN_RAW_DEVICE=`echo $IFACE|sed "s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/;s/\(enp[0-9]s[0-9]f[0-9]\)\..*/\1/"` ;; *.0*) # Silently ignore interfaces which we do not (know how to) support [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0 vconfig set_name_type DEV_PLUS_VID VLANID=`echo $IFACE|sed "s/[^.]*\.0*//g"` ;; *.*) # Silently ignore interfaces which we do not (know how to) support [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0 vconfig set_name_type DEV_PLUS_VID_NO_PAD VLANID=`echo $IFACE|sed "s/[^.]*\.0*//g"` ;; *) exit 0 ;; esac if [ -n "$IF_VLAN_RAW_DEVICE" ] && [ ! -d /sys/class/net/$IFACE ]; then if [ ! -x /sbin/vconfig ]; then exit 0 fi if ! ip link show dev "$IF_VLAN_RAW_DEVICE" > /dev/null; then echo "$IF_VLAN_RAW_DEVICE does not exist, unable to create $IFACE" exit 1 fi if [ ! -e "/sys/class/net/$IFACE" ]; then ip link set up dev $IF_VLAN_RAW_DEVICE vconfig add $IF_VLAN_RAW_DEVICE $VLANID fi fi # This is not vlan specific, and should actually go somewhere else. if [ -n "$IF_HW_MAC_ADDRESS" ]; then ip link set $IFACE address $IF_HW_MAC_ADDRESS fi if-post-down: #!/bin/sh # If IFACE is an automagic vlan interface (without the vlan-raw-device # parameter) then let's try to discover the magic here.. Another way would be # to just probe for the right device name in /proc/net/vlan case "$IFACE" in # Ignore any alias (#272891) *:*) exit 0 ;; eth*.0*|bond*.0*|wlan*.0*|em*.0*|p[0-9]*.0*|enp[0-9]*\.0*) IF_VLAN_RAW_DEVICE=`echo $IFACE|sed "s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/"` ;; eth*.*|bond*.*|wlan*.*|em*.*|p[0-9]*.*|enp[0-9]*\.*) IF_VLAN_RAW_DEVICE=`echo $IFACE|sed "s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/"` ;; # Test for vlan raw device (#196890, #292648) *) [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0 ;; esac if [ ! -x /sbin/vconfig ]; then exit 0 fi vconfig rem $IFACE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1628591/+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 1643063] Re: unable to ifup vlan based interface with systemd persistent naming
*** This bug is a duplicate of bug 1628591 *** https://bugs.launchpad.net/bugs/1628591 Check out my alternative workaround from duplicate bug #1628591. In my opinion, it's cleaner. I haven't heard of vconfig to be deprecated. Anyway... it's funny how we must do workarounds for basic functionality, such as networking. In Debian 9 Stretch, you don't have to do any of this. It works out-of- the-box with both "eth" and "enp" naming conventions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1643063 Title: unable to ifup vlan based interface with systemd persistent naming Status in ifupdown package in Ubuntu: Confirmed Bug description: root@atlantis:/etc# ifup enp2s0.121 Cannot find device "enp2s0.121" Failed to bring up enp2s0.121. Workaround: Add pre-up /sbin/ip link add link enp2s0 name enp2s0.121 type vlan id 121 to /etc/network/interfaces declaration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1643063/+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 1643063] Re: unable to ifup vlan based interface with systemd persistent naming
*** This bug is a duplicate of bug 1628591 *** https://bugs.launchpad.net/bugs/1628591 ** This bug has been marked a duplicate of bug 1628591 ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1643063 Title: unable to ifup vlan based interface with systemd persistent naming Status in ifupdown package in Ubuntu: Confirmed Bug description: root@atlantis:/etc# ifup enp2s0.121 Cannot find device "enp2s0.121" Failed to bring up enp2s0.121. Workaround: Add pre-up /sbin/ip link add link enp2s0 name enp2s0.121 type vlan id 121 to /etc/network/interfaces declaration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1643063/+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 1628591] Re: ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention
As a workaround, you could add "vlan-raw-device", like this: auto enp0s8 iface enp0s8 inet manual auto enp0s8.7 iface enp0s8.7 inet static vlan-raw-device enp0s8 address x.x.x.x/y It's a pity that such a project doesn't pay more attention to basic features... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1628591 Title: ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention Status in ifupdown package in Ubuntu: Confirmed Bug description: The regular expressions used in /etc/network/if-post-down.d/vlan and /etc/network/if-pre-up.d/vlan do not match the name of my network card enp4s0f0. This can be fixed by broadening the regular expression. This is only a problem when the device is a vlan device! See below for the fix that worked on my system. if-pre-up: #!/bin/sh # Most of this stuff is to enable vlans case "$IFACE" in # Ignore any alias (#272891) which uses : *:*) exit 0 ;; vlan0*) vconfig set_name_type VLAN_PLUS_VID VLANID=`echo $IFACE|sed "s/vlan0*//"` ;; vlan*) vconfig set_name_type VLAN_PLUS_VID_NO_PAD VLANID=`echo $IFACE|sed "s/vlan0*//"` ;; eth*.0*|bond*.0*|wlan*.0*|em*.0*|p[0-9]*.0*|enp[0-9]*.0*) vconfig set_name_type DEV_PLUS_VID VLANID=`echo $IFACE|sed "s/eth[0-9][0-9]*\.0*//g;s/bond[0-9][0-9]*\.0*//g;s/wlan[0-9][0-9]*\.0*//g;s/em[0-9][0-9]*\.0*//g;s/p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\.0*//g;s/enp[0-9]s[0-9]f[0-9]\.0*//g"` IF_VLAN_RAW_DEVICE=`echo $IFACE|sed "s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/;s/\(enp[0-9]s[0-9]f[0-9]\)\..*/\1/"` ;; eth*.*|bond*.*|wlan*.*|em*.*|p[0-9]*.*|enp[0-9]*.*) vconfig set_name_type DEV_PLUS_VID_NO_PAD VLANID=`echo $IFACE|sed "s/eth[0-9][0-9]*\.0*//g;s/bond[0-9][0-9]*\.0*//g;s/wlan[0-9][0-9]*\.0*//g;s/em[0-9][0-9]*\.0*//g;s/p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\.0*//g;s/enp[0-9]s[0-9]f[0-9]\.//g"` IF_VLAN_RAW_DEVICE=`echo $IFACE|sed "s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/;s/\(enp[0-9]s[0-9]f[0-9]\)\..*/\1/"` ;; *.0*) # Silently ignore interfaces which we do not (know how to) support [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0 vconfig set_name_type DEV_PLUS_VID VLANID=`echo $IFACE|sed "s/[^.]*\.0*//g"` ;; *.*) # Silently ignore interfaces which we do not (know how to) support [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0 vconfig set_name_type DEV_PLUS_VID_NO_PAD VLANID=`echo $IFACE|sed "s/[^.]*\.0*//g"` ;; *) exit 0 ;; esac if [ -n "$IF_VLAN_RAW_DEVICE" ] && [ ! -d /sys/class/net/$IFACE ]; then if [ ! -x /sbin/vconfig ]; then exit 0 fi if ! ip link show dev "$IF_VLAN_RAW_DEVICE" > /dev/null; then echo "$IF_VLAN_RAW_DEVICE does not exist, unable to create $IFACE" exit 1 fi if [ ! -e "/sys/class/net/$IFACE" ]; then ip link set up dev $IF_VLAN_RAW_DEVICE vconfig add $IF_VLAN_RAW_DEVICE $VLANID fi fi # This is not vlan specific, and should actually go somewhere else. if [ -n "$IF_HW_MAC_ADDRESS" ]; then ip link set $IFACE address $IF_HW_MAC_ADDRESS fi if-post-down: #!/bin/sh # If IFACE is an automagic vlan interface (without the vlan-raw-device # parameter) then let's try to discover the magic here.. Another way would be # to just probe for the right device name in /proc/net/vlan case "$IFACE" in # Ignore any alias (#272891) *:*) exit 0 ;; eth*.0*|bond*.0*|wlan*.0*|em*.0*|p[0-9]*.0*|enp[0-9]*\.0*) IF_VLAN_RAW_DEVICE=`echo $IFACE|sed "s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/"` ;; eth*.*|bond*.*|wlan*.*|em*.*|p[0-9]*.*|enp[0-9]*\.*) IF_VLAN_RAW_DEVICE=`echo $IFACE|sed "s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/"` ;; # Test for vlan raw device (#196890, #292648) *) [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0 ;; esac if [ ! -x /sbin/vconfig ]; then exit 0 fi vconfig rem $IFACE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1628591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1628591] Re: ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention
** Summary changed: - ifup and ifdown dont work for vlan devices when raw ethernet device name does not meet regular conventions + ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1628591 Title: ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention Status in ifupdown package in Ubuntu: Confirmed Bug description: The regular expressions used in /etc/network/if-post-down.d/vlan and /etc/network/if-pre-up.d/vlan do not match the name of my network card enp4s0f0. This can be fixed by broadening the regular expression. This is only a problem when the device is a vlan device! See below for the fix that worked on my system. if-pre-up: #!/bin/sh # Most of this stuff is to enable vlans case "$IFACE" in # Ignore any alias (#272891) which uses : *:*) exit 0 ;; vlan0*) vconfig set_name_type VLAN_PLUS_VID VLANID=`echo $IFACE|sed "s/vlan0*//"` ;; vlan*) vconfig set_name_type VLAN_PLUS_VID_NO_PAD VLANID=`echo $IFACE|sed "s/vlan0*//"` ;; eth*.0*|bond*.0*|wlan*.0*|em*.0*|p[0-9]*.0*|enp[0-9]*.0*) vconfig set_name_type DEV_PLUS_VID VLANID=`echo $IFACE|sed "s/eth[0-9][0-9]*\.0*//g;s/bond[0-9][0-9]*\.0*//g;s/wlan[0-9][0-9]*\.0*//g;s/em[0-9][0-9]*\.0*//g;s/p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\.0*//g;s/enp[0-9]s[0-9]f[0-9]\.0*//g"` IF_VLAN_RAW_DEVICE=`echo $IFACE|sed "s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/;s/\(enp[0-9]s[0-9]f[0-9]\)\..*/\1/"` ;; eth*.*|bond*.*|wlan*.*|em*.*|p[0-9]*.*|enp[0-9]*.*) vconfig set_name_type DEV_PLUS_VID_NO_PAD VLANID=`echo $IFACE|sed "s/eth[0-9][0-9]*\.0*//g;s/bond[0-9][0-9]*\.0*//g;s/wlan[0-9][0-9]*\.0*//g;s/em[0-9][0-9]*\.0*//g;s/p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\.0*//g;s/enp[0-9]s[0-9]f[0-9]\.//g"` IF_VLAN_RAW_DEVICE=`echo $IFACE|sed "s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/;s/\(enp[0-9]s[0-9]f[0-9]\)\..*/\1/"` ;; *.0*) # Silently ignore interfaces which we do not (know how to) support [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0 vconfig set_name_type DEV_PLUS_VID VLANID=`echo $IFACE|sed "s/[^.]*\.0*//g"` ;; *.*) # Silently ignore interfaces which we do not (know how to) support [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0 vconfig set_name_type DEV_PLUS_VID_NO_PAD VLANID=`echo $IFACE|sed "s/[^.]*\.0*//g"` ;; *) exit 0 ;; esac if [ -n "$IF_VLAN_RAW_DEVICE" ] && [ ! -d /sys/class/net/$IFACE ]; then if [ ! -x /sbin/vconfig ]; then exit 0 fi if ! ip link show dev "$IF_VLAN_RAW_DEVICE" > /dev/null; then echo "$IF_VLAN_RAW_DEVICE does not exist, unable to create $IFACE" exit 1 fi if [ ! -e "/sys/class/net/$IFACE" ]; then ip link set up dev $IF_VLAN_RAW_DEVICE vconfig add $IF_VLAN_RAW_DEVICE $VLANID fi fi # This is not vlan specific, and should actually go somewhere else. if [ -n "$IF_HW_MAC_ADDRESS" ]; then ip link set $IFACE address $IF_HW_MAC_ADDRESS fi if-post-down: #!/bin/sh # If IFACE is an automagic vlan interface (without the vlan-raw-device # parameter) then let's try to discover the magic here.. Another way would be # to just probe for the right device name in /proc/net/vlan case "$IFACE" in # Ignore any alias (#272891) *:*) exit 0 ;; eth*.0*|bond*.0*|wlan*.0*|em*.0*|p[0-9]*.0*|enp[0-9]*\.0*) IF_VLAN_RAW_DEVICE=`echo $IFACE|sed "s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/"` ;; eth*.*|bond*.*|wlan*.*|em*.*|p[0-9]*.*|enp[0-9]*\.*) IF_VLAN_RAW_DEVICE=`echo $IFACE|sed "s/\(eth[0-9][0-9]*\)\..*/\1/;s/\(bond[0-9][0-9]*\)\..*/\1/;s/\(wlan[0-9][0-9]*\)\..*/\1/;s/\(em[0-9][0-9]*\)\..*/\1/;s/\(p[0-9][0-9]*\(p[0-9][0-9]*\)\?\(_[0-9][0-9]*\)\?\)\..*/\1/"` ;; # Test for vlan raw device (#196890, #292648) *) [ -z "$IF_VLAN_RAW_DEVICE" ] && exit 0 ;; esac if [ ! -x /sbin/vconfig ]; then exit 0 fi vconfig rem $IFACE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1628591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1684298] Re: Security issues (solved in Debian) - affecting icu52 in trusty
Thank you, Janitor ! :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1684298 Title: Security issues (solved in Debian) - affecting icu52 in trusty Status in icu package in Ubuntu: Fix Released Bug description: Date Reported: 19 Apr 2017 Security database references: In the Debian bugtracking system: 860314. In Mitre's CVE dictionary: CVE-2017-7867, CVE-2017-7868. More information: It was discovered that icu, the International Components for Unicode library, did not correctly validate its input. An attacker could use this problem to trigger an out-of-bound write through a heap-based buffer overflow, thus causing a denial of service via application crash, or potential execution of arbitrary code. For the stable distribution (jessie), these problems have been fixed in version 52.1-8+deb8u5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1684298/+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 1684298] Re: Security issues (solved in Debian) - affecting icu52 in trusty
** Summary changed: - Security issues (solved in Debian) - affecting icu 52.1-3ubuntu0.5 trusty + Security issues (solved in Debian) - affecting icu52 in trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1684298 Title: Security issues (solved in Debian) - affecting icu52 in trusty Status in icu package in Ubuntu: New Bug description: Date Reported: 19 Apr 2017 Security database references: In the Debian bugtracking system: 860314. In Mitre's CVE dictionary: CVE-2017-7867, CVE-2017-7868. More information: It was discovered that icu, the International Components for Unicode library, did not correctly validate its input. An attacker could use this problem to trigger an out-of-bound write through a heap-based buffer overflow, thus causing a denial of service via application crash, or potential execution of arbitrary code. For the stable distribution (jessie), these problems have been fixed in version 52.1-8+deb8u5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1684298/+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 1684298] [NEW] Security issues (solved in Debian) - affecting icu 52.1-3ubuntu0.5 trusty
*** This bug is a security vulnerability *** Public security bug reported: Date Reported: 19 Apr 2017 Security database references: In the Debian bugtracking system: 860314. In Mitre's CVE dictionary: CVE-2017-7867, CVE-2017-7868. More information: It was discovered that icu, the International Components for Unicode library, did not correctly validate its input. An attacker could use this problem to trigger an out-of-bound write through a heap-based buffer overflow, thus causing a denial of service via application crash, or potential execution of arbitrary code. For the stable distribution (jessie), these problems have been fixed in version 52.1-8+deb8u5. ** Affects: icu (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Public Security ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-7867 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-7868 ** Description changed: Date Reported: 19 Apr 2017 Security database references: - In the Debian bugtracking system: Bug 860314. + In the Debian bugtracking system: 860314. In Mitre's CVE dictionary: CVE-2017-7867, CVE-2017-7868. More information: It was discovered that icu, the International Components for Unicode library, did not correctly validate its input. An attacker could use this problem to trigger an out-of-bound write through a heap-based buffer overflow, thus causing a denial of service via application crash, or potential execution of arbitrary code. For the stable distribution (jessie), these problems have been fixed in version 52.1-8+deb8u5. ** Summary changed: - Security issues (solved in Debian) + Security issues (solved in Debian) - affecting icu 52.1-3ubuntu0.5 trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1684298 Title: Security issues (solved in Debian) - affecting icu 52.1-3ubuntu0.5 trusty Status in icu package in Ubuntu: New Bug description: Date Reported: 19 Apr 2017 Security database references: In the Debian bugtracking system: 860314. In Mitre's CVE dictionary: CVE-2017-7867, CVE-2017-7868. More information: It was discovered that icu, the International Components for Unicode library, did not correctly validate its input. An attacker could use this problem to trigger an out-of-bound write through a heap-based buffer overflow, thus causing a denial of service via application crash, or potential execution of arbitrary code. For the stable distribution (jessie), these problems have been fixed in version 52.1-8+deb8u5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1684298/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
You're welcome guys, glad to be of help. @Venkat How exactly did you get microsd to work? Is this on the Asus E200HA? I don't believe mine works as of now. @Marco Indeed 17.04 requires you to remove the default kernel after the install. Does the line you added fix your sound issue? Cheers, Andrei ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: 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/alsa-driver/+bug/1563110/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
Can you provide the output from "uname -r"? The kernel patch should have worked fine. I fixed a bug in the script late last night if you cloned it then. Right now this is only confirmed to work flawlessly (within reason) with Ubuntu 16.10. Ubuntu 16.04 seems to have an issue with intermitent sound cutting out, might have to do with the version of Pulseaudio installed. As of 16.10 the version installed is 9. I really recommend for now to run Ubuntu 16.10 and patch that. You can get your desktop environment set up fairly easily if you prefer KDE or Lubuntu by "sudo apt-get install lubuntu-desktop" or similar commands. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: 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/alsa-driver/+bug/1563110/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
Got sound working folks. See the repository for the new updated install script (it's at the top of the description). Only things not working perfectly now are Sleep (my script makes it so the screen just shuts down to save some power) and SD card. Cheers! https://github.com/Grippentech/Asus-E200HA-Linux-Post-Install-Script -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: 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/alsa-driver/+bug/1563110/+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 1525477] Re: X server crash when pasting selection using middle button in Chromium
I cannot reproduce it with daily live after installing Chromium. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1525477 Title: X server crash when pasting selection using middle button in Chromium Status in xorg package in Ubuntu: Incomplete Bug description: Description: Ubuntu 14.04.3 LTS Release: 14.04 xorg 1:7.7+1ubuntu8.1 Select any text; use middle button to paste selection in Chromium (I observed it pasting in URL bar or in any form text input field, including previous attempt to report this bug :) ). Session crashes. It does not happen, when either pasting into different application (like terminal) or wen use Copy - Paste instead of middle button. I noticed it about a week ago, so it must be some recent change; I use selection paste often enough to notice something like this before. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.2.0-19.23~14.04.1-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Dec 12 11:09:22 2015 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:062b] InstallationDate: Installed on 2015-07-02 (162 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-:128M vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/19/2015:svnDellInc.:pnLatitudeE5450:pvr01:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Dec 12 11:08:11 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1133 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1525477/+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 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method
I just upgraded 16.04 to 16.10 and had to search and find the solution on my fucking smartphone instead of the PC because somebody decided to change the way the network manager *manages* the network interfaces. Good job, you've just wasted tens of people's hours for nothing. I hope somebody's really proud of themselves. I swear to god, as soon as Android manages to take a big chunk out of the Linux desktop market share, Ubuntu goes right out of the SSD on my machine. I've just about had enough of this crap. -- 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/1638842 Title: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method Status in network-manager package in Ubuntu: Won't Fix Bug description: Hello, I installed Ubuntu 16.10 using a chroot. I use network-manager to manage connections. My system is up-to-date (so I use network-manager 1.2.4-0ubuntu1). Wifi works perfectly but I cannot connect to wired networks and using my phone's Bluetooth connection. Corresponding devices are said to be unmanaged by network-manager. nmcli dev outputs: DEVICETYPE STATE CONNECTION enp1s0ethernet unmanaged -- wlp2s0wifi disconnected -- 6C:9B:02:2C:EE:2C btunmanaged -- hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C gsm unmanaged -- loloopback unmanaged -- The following command has no effect: sudo nmcli dev set enp1s0 managed yes I can connect to a wired connection by doing: ifconfig enp1s0 up dhclient enp1s0 There is nothing in the file /etc/network/interfaces. Everything works perfectly if I downgrade network-manager to this version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb (http://packages.ubuntu.com/xenial-updates/amd64/network- manager/download). I had to install libreadline6 and downgrade nplan to meet dependencies. I don't know what to join to this bug report so please ask in case anything is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
Konstantinos what flavor and version of Linux are you using? Ubuntu and derivatives from 16.04 and newer should detect the keyboard by default with no issue. Audio News: I have e-mailed the developer working on the connexant driver that pertains to the E200HA and he said they are making progress and he will send me some code to test by next week when he returns to the office. I will do my best to update you guys and try to provide some working code if I can. In the mean-time you can follow this github page where I try to fix as many of the issues on the E200HA as possible, I'm more likely to keep that up to date than this forum. https://github.com/Grippentech/Asus-E200HA-Linux-Post-Install-Script -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: 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/alsa-driver/+bug/1563110/+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 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
Just made an account to post here. The fact that this bug is known for ALMOST a year irritates me the most, I can't enjoy ubuntu or any linux distribution in my E200HA. On-topic: Some guy announced on other forum that they work at this bug but it's not prioritized and it will be fixed in kernel 4.12, not before, that's sad. I can't find the link to the forum anymore, I think they deleted it.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: 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/alsa-driver/+bug/1563110/+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 1525477] Re: X server crash when pasting selection using middle button in Chromium
It does not look like live image includes Chromium (at least, I do not see it in Dash search results), so unfortunately I cannot test it - the problem so far was observed only when pasting in Chromium. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1525477 Title: X server crash when pasting selection using middle button in Chromium Status in xorg package in Ubuntu: Incomplete Bug description: Description: Ubuntu 14.04.3 LTS Release: 14.04 xorg 1:7.7+1ubuntu8.1 Select any text; use middle button to paste selection in Chromium (I observed it pasting in URL bar or in any form text input field, including previous attempt to report this bug :) ). Session crashes. It does not happen, when either pasting into different application (like terminal) or wen use Copy - Paste instead of middle button. I noticed it about a week ago, so it must be some recent change; I use selection paste often enough to notice something like this before. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.2.0-19.23~14.04.1-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Dec 12 11:09:22 2015 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:062b] InstallationDate: Installed on 2015-07-02 (162 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-:128M vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/19/2015:svnDellInc.:pnLatitudeE5450:pvr01:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Dec 12 11:08:11 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1133 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1525477/+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 1525477] Re: X server crash when pasting selection using middle button in Chromium
Still valid in Ubuntu 16.04.2 with HWE kernels and Xorg. It is beyond my understanding why you would need BIOS version for this, but if you insist ... A14 12/26/2016 And no, there is of course no improvement after updating BIOS. ** Changed in: xorg (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1525477 Title: X server crash when pasting selection using middle button in Chromium Status in xorg package in Ubuntu: New Bug description: Description: Ubuntu 14.04.3 LTS Release: 14.04 xorg 1:7.7+1ubuntu8.1 Select any text; use middle button to paste selection in Chromium (I observed it pasting in URL bar or in any form text input field, including previous attempt to report this bug :) ). Session crashes. It does not happen, when either pasting into different application (like terminal) or wen use Copy - Paste instead of middle button. I noticed it about a week ago, so it must be some recent change; I use selection paste often enough to notice something like this before. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.2.0-19.23~14.04.1-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Dec 12 11:09:22 2015 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:062b] InstallationDate: Installed on 2015-07-02 (162 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-:128M vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/19/2015:svnDellInc.:pnLatitudeE5450:pvr01:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Dec 12 11:08:11 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1133 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1525477/+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 1559429] Re: Xorg crash after middle button paste in Chromium under kernel 4.4 LTS
OMG ... again finding easy reason to not do anything ... Yes, I updated BIOS to the last available today (12.02.2017). This is A14 12/26/2016 And the bug is still present on 16.04.2 with HWE kernel (4.8) and Xorg (1.18.4). Of course you can now wait couple of months until new BIOS is released and waive off with "BIOS outdated" again ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1559429 Title: Xorg crash after middle button paste in Chromium under kernel 4.4 LTS Status in xorg package in Ubuntu: New Bug description: When pasting text in Chromium using middle button Xorg crashes. So far this happens only - in Chromium (I can middle paste in other programs like terminal) - using kernel 4.4 LTS (it does not happen using stock 3.16 kernel) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-9.24~14.04.1~beta1-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Mar 19 12:21:17 2016 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:062b] InstallationDate: Installed on 2015-07-02 (261 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9-generic root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-:128M vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/19/2015:svnDellInc.:pnLatitudeE5450:pvr01:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Mar 19 12:12:47 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1133 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559429/+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 1638675] [NEW] package procps 2:3.3.12-1ubuntu2 failed to install/upgrade: end of file on stdin at conffile prompt
Public bug reported: Not really know of any. Was trying to upgrade 16.04 to 16.10 headless home media server. Pressed ctrl+c by mistake during install. All hell broke loose. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: procps 2:3.3.12-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Wed Nov 2 18:37:42 2016 ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2013-11-06 (1092 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: procps Title: package procps 2:3.3.12-1ubuntu2 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: Upgraded to yakkety on 2016-11-02 (0 days ago) mtime.conffile..etc.sysctl.conf: 2014-05-05T12:03:01.086378 ** Affects: procps (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1638675 Title: package procps 2:3.3.12-1ubuntu2 failed to install/upgrade: end of file on stdin at conffile prompt Status in procps package in Ubuntu: New Bug description: Not really know of any. Was trying to upgrade 16.04 to 16.10 headless home media server. Pressed ctrl+c by mistake during install. All hell broke loose. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: procps 2:3.3.12-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Wed Nov 2 18:37:42 2016 ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2013-11-06 (1092 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: procps Title: package procps 2:3.3.12-1ubuntu2 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: Upgraded to yakkety on 2016-11-02 (0 days ago) mtime.conffile..etc.sysctl.conf: 2014-05-05T12:03:01.086378 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1638675/+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 1637801] [NEW] Incorrect Russian translation of "apt list --upgradeabe" results
Public bug reported: bor@bor-Latitude-E5450:~$ apt list --upgradeable Вывод списка… Готово build/неизвестно 20161025 all [может быть обновлён до: 20151105] In Russian this means "version 20161025 can be upgraded TO version 20151105) While original English says exactly opposite: bor@bor-Latitude-E5450:~$ LC_ALL=C LANG=C apt list --upgradeable Listing... Done build/unknown 20161025 all [upgradable from: 20151105] Literal translation (that does not require serious phrase change) would probably be "может быть обновлен с" although it sounds also artificial, as in Russian subject is package that is being updated (currently installed), not new version. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.8.0-25.27~16.04.1-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 30 09:39:47 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (485 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 SourcePackage: apt UpgradeStatus: Upgraded to xenial on 2016-10-29 (0 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1637801 Title: Incorrect Russian translation of "apt list --upgradeabe" results Status in apt package in Ubuntu: New Bug description: bor@bor-Latitude-E5450:~$ apt list --upgradeable Вывод списка… Готово build/неизвестно 20161025 all [может быть обновлён до: 20151105] In Russian this means "version 20161025 can be upgraded TO version 20151105) While original English says exactly opposite: bor@bor-Latitude-E5450:~$ LC_ALL=C LANG=C apt list --upgradeable Listing... Done build/unknown 20161025 all [upgradable from: 20151105] Literal translation (that does not require serious phrase change) would probably be "может быть обновлен с" although it sounds also artificial, as in Russian subject is package that is being updated (currently installed), not new version. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.12~ubuntu16.04.1 ProcVersionSignature: Ubuntu 4.8.0-25.27~16.04.1-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 30 09:39:47 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (485 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 SourcePackage: apt UpgradeStatus: Upgraded to xenial on 2016-10-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1637801/+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 1543794] Re: isc-dhcp-server fails to start on second & further attempts with 'Can't open /var/lib/dhcp/dhcpd.leases for append'
I have the same issue on Ubuntu 16.04, removing apparmor confs helped. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1543794 Title: isc-dhcp-server fails to start on second & further attempts with 'Can't open /var/lib/dhcp/dhcpd.leases for append' Status in isc-dhcp package in Ubuntu: Fix Released Bug description: During the first start of isc-dhcp-server (using the systemd service unit), a blank dhcpd.leases file is created (presumably owned by root:root). dhcpd starts successfully (and then exits due to no subnet definitions, that's expected). Attempting to start the service again fails with 'Can't open /var/lib/dhcp/dhcpd.leases for append' (the dhcpd.leases file ownership is now dhcpd.dhcpd), and apparmor logs a denial of the dac_override capability. Removing the leases file repeats this process (first start works as expected, future ones do not). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: isc-dhcp-server 4.3.3-5ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Tue Feb 9 20:58:12 2016 InstallationDate: Installed on 2016-02-09 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206) ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1543794/+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 1559429] [NEW] Xorg crash after middle button paste in Chromium under kernel 4.4 LTS
Public bug reported: When pasting text in Chromium using middle button Xorg crashes. So far this happens only - in Chromium (I can middle paste in other programs like terminal) - using kernel 4.4 LTS (it does not happen using stock 3.16 kernel) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-9.24~14.04.1~beta1-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Mar 19 12:21:17 2016 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:062b] InstallationDate: Installed on 2015-07-02 (261 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9-generic root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-:128M vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/19/2015:svnDellInc.:pnLatitudeE5450:pvr01:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Mar 19 12:12:47 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1133 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 crash trusty ubuntu ** Attachment added: "Crash report" https://bugs.launchpad.net/bugs/1559429/+attachment/4604152/+files/_usr_bin_Xorg.0.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1559429 Title: Xorg crash after middle button paste in Chromium under kernel 4.4 LTS Status in xorg package in Ubuntu: New Bug description: When pasting text in Chromium using middle button Xorg crashes. So far this happens only - in Chromium (I can middle paste in other programs like terminal) - using kernel 4.4 LTS (it does not happen using stock 3.16 kernel) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-9.24~14.04.1~beta1-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Mar 19 12:21:17 2016 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard:
[Touch-packages] [Bug 1539491] Re: Update to 2016a
** Tags added: precise trusty ** Tags added: wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1539491 Title: Update to 2016a Status in tzdata package in Ubuntu: Confirmed Bug description: Changes affecting future time stamps America/Cayman will not observe daylight saving this year after all. Revert our guess that it would. (Thanks to Matt Johnson.) Asia/Chita switches from +0800 to +0900 on 2016-03-27 at 02:00. (Thanks to Alexander Krivenyshev.) Asia/Tehran now has DST predictions for the year 2038 and later, to be March 21 00:00 to September 21 00:00. This is likely better than predicting no DST, albeit off by a day every now and then. Changes affecting past and future time stamps America/Metlakatla switched from PST all year to AKST/AKDT on 2015-11-01 at 02:00. (Thanks to Steffen Thorsen.) America/Santa_Isabel has been removed, and replaced with a backward compatibility link to America/Tijuana. Its contents were apparently based on a misreading of Mexican legislation. Changes affecting past time stamps Asia/Karachi's two transition times in 2002 were off by a minute. (Thanks to Matt Johnson.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1539491/+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 1557359] [NEW] Update to 2016b
Public bug reported: The 2016b release of the tz code and data is available. It reflects the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes. A last-minute note: some 2016b data entries cause zic implementations derived from tz releases 2005j through 2015e to issue warnings like "time zone abbreviation differs from POSIX standard (+03)". These warnings should not otherwise affect zic's output and can safely be ignored on today's platforms, as the warnings refer to a restriction in POSIX.1-1988 that was removed in POSIX.1-2001. One way to suppress the warnings is to upgrade to zic derived from tz releases 2015f and later. Changes affecting future time stamps New zones Europe/Astrakhan and Europe/Ulyanovsk for Astrakhan and Ulyanovsk Oblasts, Russia, both of which will switch from +03 to +04 on 2016-03-27 at 02:00 local time. They need distinct zones since their post-1970 histories disagree. New zone Asia/Barnaul for Altai Krai and Altai Republic, Russia, which will switch from +06 to +07 on the same date and local time. Also, Asia/Sakhalin moves from +10 to +11 on 2016-03-27 at 02:00. (Thanks to Alexander Krivenyshev for the heads-up, and to Matt Johnson and Stepan Golosunov for followup.) As a trial of a new system that needs less information to be made up, the new zones use numeric time zone abbreviations like "+04" instead of invented abbreviations like "ASTT". Haiti will not observe DST in 2016. (Thanks to Jean Antoine via Steffen Thorsen.) Palestine's spring-forward transition on 2016-03-26 is at 01:00, not 00:00. (Thanks to Hannah Kreitem.) Guess future transitions will be March's last Saturday at 01:00, not March's last Friday at 24:00. Changes affecting past time stamps Europe/Chisinau observed DST during 1990, and switched from +04 to +03 at 1990-05-06 02:00, instead of switching from +03 to +02. (Thanks to Stepan Golosunov.) 1991 abbreviations in Europe/Samara should be SAMT/SAMST, not KUYT/KUYST. (Thanks to Stepan Golosunov.) Changes to code tzselect's diagnostics and checking, and checktab.awk's checking, have been improved. (Thanks to J William Piggott.) tzcode now builds under MinGW. (Thanks to Ian Abbott and Esben Haabendal.) tzselect now tests Julian-date TZ settings more accurately. (Thanks to J William Piggott.) Changes to commentary Comments in zone tables have been improved. (Thanks to J William Piggott.) tzselect again limits its menu comments so that menus fit on a 24x80 alphanumeric display. A new web page tz-how-to.html. (Thanks to Bill Seymour.) In the Theory file, the description of possible time zone abbreviations in tzdata has been cleaned up, as the old description was unclear and inconsistent. (Thanks to Alain Mouette for reporting the problem.) Here are links to the release files: ftp://ftp.iana.org/tz/releases/tzcode2016b.tar.gz ftp://ftp.iana.org/tz/releases/tzdata2016b.tar.gz ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1557359 Title: Update to 2016b Status in tzdata package in Ubuntu: New Bug description: The 2016b release of the tz code and data is available. It reflects the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes. A last-minute note: some 2016b data entries cause zic implementations derived from tz releases 2005j through 2015e to issue warnings like "time zone abbreviation differs from POSIX standard (+03)". These warnings should not otherwise affect zic's output and can safely be ignored on today's platforms, as the warnings refer to a restriction in POSIX.1-1988 that was removed in POSIX.1-2001. One way to suppress the warnings is to upgrade to zic derived from tz releases 2015f and later. Changes affecting future time stamps New zones Europe/Astrakhan and Europe/Ulyanovsk for Astrakhan and Ulyanovsk Oblasts, Russia, both of which will switch from +03 to +04 on 2016-03-27 at 02:00 local time. They need distinct zones since their post-1970 histories disagree. New zone Asia/Barnaul for Altai Krai and Altai Republic, Russia, which will switch from +06 to +07 on the same date and local time. Also, Asia/Sakhalin moves from +10 to +11 on 2016-03-27 at 02:00. (Thanks to Alexander Krivenyshev for the heads-up, and to Matt Johnson and Stepan Golosunov for followup.) As a trial of a new system that needs less information to be made up, the new zones use numeric time zone
[Touch-packages] [Bug 1539491] Re: Update to 2016a
Package already exists in Xenial, so the question is just to backport it to Trusty and Wily http://packages.ubuntu.com/search?keywords=tzdata=names=xenial=all -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1539491 Title: Update to 2016a Status in tzdata package in Ubuntu: Confirmed Bug description: Changes affecting future time stamps America/Cayman will not observe daylight saving this year after all. Revert our guess that it would. (Thanks to Matt Johnson.) Asia/Chita switches from +0800 to +0900 on 2016-03-27 at 02:00. (Thanks to Alexander Krivenyshev.) Asia/Tehran now has DST predictions for the year 2038 and later, to be March 21 00:00 to September 21 00:00. This is likely better than predicting no DST, albeit off by a day every now and then. Changes affecting past and future time stamps America/Metlakatla switched from PST all year to AKST/AKDT on 2015-11-01 at 02:00. (Thanks to Steffen Thorsen.) America/Santa_Isabel has been removed, and replaced with a backward compatibility link to America/Tijuana. Its contents were apparently based on a misreading of Mexican legislation. Changes affecting past time stamps Asia/Karachi's two transition times in 2002 were off by a minute. (Thanks to Matt Johnson.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1539491/+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 1539491] Re: Update to 2016a
Debian already built a package: https://packages.debian.org/en/sid/tzdata -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1539491 Title: Update to 2016a Status in tzdata package in Ubuntu: Confirmed Bug description: Changes affecting future time stamps America/Cayman will not observe daylight saving this year after all. Revert our guess that it would. (Thanks to Matt Johnson.) Asia/Chita switches from +0800 to +0900 on 2016-03-27 at 02:00. (Thanks to Alexander Krivenyshev.) Asia/Tehran now has DST predictions for the year 2038 and later, to be March 21 00:00 to September 21 00:00. This is likely better than predicting no DST, albeit off by a day every now and then. Changes affecting past and future time stamps America/Metlakatla switched from PST all year to AKST/AKDT on 2015-11-01 at 02:00. (Thanks to Steffen Thorsen.) America/Santa_Isabel has been removed, and replaced with a backward compatibility link to America/Tijuana. Its contents were apparently based on a misreading of Mexican legislation. Changes affecting past time stamps Asia/Karachi's two transition times in 2002 were off by a minute. (Thanks to Matt Johnson.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1539491/+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 1514165] Re: package sudo 1.8.12-1ubuntu3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
I've downloaded guitarpro from torrent and it was missing some dependencies. When I did sudo apt-get install -f after it did it's job, I saw at the end that it was trying to delete the sudoers file also, but I didn't have that privilege (luckily) for that. Be careful what you download and install from torrents. If this helps, I've also scanned guitarpro package with clamav, and the clamscan was negative for viruses. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1514165 Title: package sudo 1.8.12-1ubuntu3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in sudo package in Ubuntu: Invalid Bug description: This happened after doing apt-get check and I was recommended to run apt-get -f install ProblemType: Package DistroRelease: Ubuntu 15.10 Package: sudo 1.8.12-1ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-16.19-lowlatency 4.2.3 Uname: Linux 4.2.0-16-lowlatency x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 Date: Sun Nov 8 04:45:37 2015 DpkgHistoryLog: Start-Date: 2015-11-08 04:45:36 Commandline: apt-get -f install Install: libportaudio2:i386 (19+svn20140130-1build1, automatic) Remove: sudo:amd64 (1.8.12-1ubuntu3), ubuntu-minimal:amd64 (1.341), guitarpro6:i386 (6.1.9) DuplicateSignature: package:sudo:1.8.12-1ubuntu3:subprocess installed pre-removal script returned error exit status 1 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2015-10-23 (15 days ago) InstallationMedia: Ubuntu-Studio 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1 SourcePackage: sudo Title: package sudo 1.8.12-1ubuntu3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1514165/+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 1130252] Re: Stop music on hibernate or suspend
** Changed in: pulseaudio (Ubuntu) Status: New => Invalid -- 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/1130252 Title: Stop music on hibernate or suspend Status in pulseaudio package in Ubuntu: Invalid Status in unity package in Ubuntu: Invalid Bug description: Steps: 1. Play music via Spotify or Banshee. 2. Suspend or hibernate without stopping the music 3. Turn your system back on The expected behaviour: Music is stopped, you can open your laptop safely. The actual behaviour: Music continues to play as it was before hibernation. It might be unwanted when someone is sleeping or you're turning your laptop on before a lecture starts. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.12.0-0ubuntu0.2 Uname: Linux 3.8.0-030800rc4-generic i686 ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Feb 19 09:35:18 2013 InstallationDate: Installed on 2012-11-05 (106 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1130252/+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 1539491] [NEW] Update to 2016a
Public bug reported: Changes affecting future time stamps America/Cayman will not observe daylight saving this year after all. Revert our guess that it would. (Thanks to Matt Johnson.) Asia/Chita switches from +0800 to +0900 on 2016-03-27 at 02:00. (Thanks to Alexander Krivenyshev.) Asia/Tehran now has DST predictions for the year 2038 and later, to be March 21 00:00 to September 21 00:00. This is likely better than predicting no DST, albeit off by a day every now and then. Changes affecting past and future time stamps America/Metlakatla switched from PST all year to AKST/AKDT on 2015-11-01 at 02:00. (Thanks to Steffen Thorsen.) America/Santa_Isabel has been removed, and replaced with a backward compatibility link to America/Tijuana. Its contents were apparently based on a misreading of Mexican legislation. Changes affecting past time stamps Asia/Karachi's two transition times in 2002 were off by a minute. (Thanks to Matt Johnson.) ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1539491 Title: Update to 2016a Status in tzdata package in Ubuntu: New Bug description: Changes affecting future time stamps America/Cayman will not observe daylight saving this year after all. Revert our guess that it would. (Thanks to Matt Johnson.) Asia/Chita switches from +0800 to +0900 on 2016-03-27 at 02:00. (Thanks to Alexander Krivenyshev.) Asia/Tehran now has DST predictions for the year 2038 and later, to be March 21 00:00 to September 21 00:00. This is likely better than predicting no DST, albeit off by a day every now and then. Changes affecting past and future time stamps America/Metlakatla switched from PST all year to AKST/AKDT on 2015-11-01 at 02:00. (Thanks to Steffen Thorsen.) America/Santa_Isabel has been removed, and replaced with a backward compatibility link to America/Tijuana. Its contents were apparently based on a misreading of Mexican legislation. Changes affecting past time stamps Asia/Karachi's two transition times in 2002 were off by a minute. (Thanks to Matt Johnson.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1539491/+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 1525477] [NEW] X server crash when pasting selection using middle button in Chromium
Public bug reported: Description:Ubuntu 14.04.3 LTS Release:14.04 xorg 1:7.7+1ubuntu8.1 Select any text; use middle button to paste selection in Chromium (I observed it pasting in URL bar or in any form text input field, including previous attempt to report this bug :) ). Session crashes. It does not happen, when either pasting into different application (like terminal) or wen use Copy - Paste instead of middle button. I noticed it about a week ago, so it must be some recent change; I use selection paste often enough to notice something like this before. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.2.0-19.23~14.04.1-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Dec 12 11:09:22 2015 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:062b] InstallationDate: Installed on 2015-07-02 (162 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-:128M vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/19/2015:svnDellInc.:pnLatitudeE5450:pvr01:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Dec 12 11:08:11 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1133 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1525477 Title: X server crash when pasting selection using middle button in Chromium Status in xorg package in Ubuntu: New Bug description: Description: Ubuntu 14.04.3 LTS Release: 14.04 xorg 1:7.7+1ubuntu8.1 Select any text; use middle button to paste selection in Chromium (I observed it pasting in URL bar or in any form text input field, including previous attempt to report this bug :) ). Session crashes. It does not happen, when either pasting into different application (like terminal) or wen use Copy - Paste instead of middle button. I noticed it about a week ago, so it must be some recent change; I use selection paste often enough to notice something like this before. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.2.0-19.23~14.04.1-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist:
[Touch-packages] [Bug 1503979] Re: ubuntu-support-status throws exeption No date tag found (regression)
Why this bug suddenly became Invalid?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1503979
Title:
ubuntu-support-status throws exeption No date tag found (regression)
Status in python-apt package in Ubuntu:
Confirmed
Status in update-manager package in Ubuntu:
Invalid
Bug description:
Description: Ubuntu 14.04.3 LTS
Release: 14.04
update-manager-core: 1:0.196.14
Since the last update ubuntu-support-status throws
Traceback (most recent call last):
File "/usr/bin/ubuntu-support-status", line 133, in
pkg.name, support_tag)
File "/usr/bin/ubuntu-support-status", line 49, in get_maintenance_status
raise Exception("No date tag found")
Exception: No date tag found
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1503979/+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 1502058] Re: Update to 2015g
Hi Adam. So far - no problems using latest update. Since we do many calculations which are time-zone dependent I would say that everything seems to work fine for us. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1502058 Title: Update to 2015g Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Precise: Fix Released Status in tzdata source package in Trusty: Fix Released Status in tzdata source package in Vivid: Fix Released Bug description: The 2015g release of the tz code and data is available. It reflects the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes: Changes affecting future time stamps Turkey's 2015 fall-back transition is scheduled for Nov. 8, not Oct. 25. (Thanks to Fatih.) Norfolk moves from +1130 to +1100 on 2015-10-04 at 02:00 local time. (Thanks to Alexander Krivenyshev.) Fiji's 2016 fall-back transition is scheduled for January 17, not 24. (Thanks to Ken Rylander.) Fort Nelson, British Columbia will not fall back on 2015-11-01. It has effectively been on MST (-0700) since it advanced its clocks on 2015-03-08. New zone America/Fort_Nelson. (Thanks to Matt Johnson.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1502058/+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 1502058] Re: Update to 2015g
Hi Adam. Actually I manually installed this package from Wily repository - everything seems to be Ok. But I'll enable proposed for sure. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1502058 Title: Update to 2015g Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Precise: Fix Committed Status in tzdata source package in Trusty: Fix Committed Status in tzdata source package in Vivid: Fix Committed Bug description: The 2015g release of the tz code and data is available. It reflects the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes: Changes affecting future time stamps Turkey's 2015 fall-back transition is scheduled for Nov. 8, not Oct. 25. (Thanks to Fatih.) Norfolk moves from +1130 to +1100 on 2015-10-04 at 02:00 local time. (Thanks to Alexander Krivenyshev.) Fiji's 2016 fall-back transition is scheduled for January 17, not 24. (Thanks to Ken Rylander.) Fort Nelson, British Columbia will not fall back on 2015-11-01. It has effectively been on MST (-0700) since it advanced its clocks on 2015-03-08. New zone America/Fort_Nelson. (Thanks to Matt Johnson.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1502058/+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 1270257] Re: NetworkManager failed to function after suspend and resume
This issue has been present again with systemd on Ubuntu 15.04. I have a clean install of 15.04 on a Lenovo Y50-70 with an Intel Wi-Fi AC 7260 and I need to run sudo service network-manager restart in order to bring back internet access. This issue was not present with 14.10 and before. I first found the solution on http://ubuntuforums.org/showthread.php?t=2223566 . It would be great if this would be fixed, as it is quite annoying. But then again, this is OSS, so I have no hopes for this issue. -- 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/1270257 Title: NetworkManager failed to function after suspend and resume Status in network-manager package in Ubuntu: Invalid Bug description: NetworkManager failed to function after resuming from suspend. The indicator applet in the Mac OS style menu bar showed the empty quarter-circle, and clicking Enable Networking didn't change the menu options or the style of the applet. Running sudo service network-manager restart brought back functionality. $ dpkg -l systemd* logind* 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 logind none(no description available) un systemdnone(no description available) ii systemd-services 204-0ubuntu19.1 amd64systemd runtime services ii systemd-shim 6-0ubuntu0.13.10 amd64shim for systemd Thanks ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Fri Jan 17 10:08:48 2014 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-10-18 (456 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.14 metric 9 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-11-06 (72 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-11-05T17:49:23 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1270257/+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 1482810] [NEW] dropbear DEVICE variable is ignored when sourced from conf.d
Public bug reported:
1) this is what /usr/share/initramfs-tools/init does:
```
. /conf/initramfs.conf
for conf in conf/conf.d/*; do
[ -f ${conf} ] . ${conf}
done
. /scripts/functions
```
2) this is what /usr/share/initramfs-tools/scripts/init-premount/dropbear
does:
```
. /scripts/functions
. /conf/initramfs.conf
configure_networking
```
3) bug result: ```configure_networking ``` will not find a $DEVICE variable
if the $DEVICE variable is overriden from some
```/etc/initramfs-tools/conf.d/user-file```
4) I would hope this be somehow enforced for all scripts?
###
lsb_release -rd
Description:Ubuntu 14.04.2 LTS
Release:14.04
###
apt-cache policy initramfs-tools
initramfs-tools:
Installed: 0.103ubuntu4.2
Candidate: 0.103ubuntu4.2
Version table:
*** 0.103ubuntu4.2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
100 /var/lib/dpkg/status
0.103ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Tags: conf.d device dropbear variable
** Description changed:
-
1) this is what /usr/share/initramfs-tools/init does:
```
. /conf/initramfs.conf
for conf in conf/conf.d/*; do
- [ -f ${conf} ] . ${conf}
+ [ -f ${conf} ] . ${conf}
done
. /scripts/functions
```
- 2) this is what /usr/share/initramfs-tools/scripts/init-premount does:
+ 2) this is what /usr/share/initramfs-tools/scripts/init-premount/dropbeaar
does:
```
. /scripts/functions
. /conf/initramfs.conf
configure_networking
```
3) bug result: ```configure_networking ``` will not find a $DEVICE variable
if the $DEVICE variable is overriden from some
```/etc/initramfs-tools/conf.d/user-file```
4) I would hope this be somehow enforced for all scripts?
###
lsb_release -rd
Description:Ubuntu 14.04.2 LTS
Release:14.04
###
apt-cache policy initramfs-tools
initramfs-tools:
- Installed: 0.103ubuntu4.2
- Candidate: 0.103ubuntu4.2
- Version table:
- *** 0.103ubuntu4.2 0
- 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
- 100 /var/lib/dpkg/status
- 0.103ubuntu4 0
- 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
+ Installed: 0.103ubuntu4.2
+ Candidate: 0.103ubuntu4.2
+ Version table:
+ *** 0.103ubuntu4.2 0
+ 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
+ 100 /var/lib/dpkg/status
+ 0.103ubuntu4 0
+ 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
** Description changed:
1) this is what /usr/share/initramfs-tools/init does:
```
. /conf/initramfs.conf
for conf in conf/conf.d/*; do
[ -f ${conf} ] . ${conf}
done
. /scripts/functions
```
- 2) this is what /usr/share/initramfs-tools/scripts/init-premount/dropbeaar
does:
+ 2) this is what /usr/share/initramfs-tools/scripts/init-premount/dropbear
does:
```
. /scripts/functions
. /conf/initramfs.conf
configure_networking
```
3) bug result: ```configure_networking ``` will not find a $DEVICE variable
if the $DEVICE variable is overriden from some
```/etc/initramfs-tools/conf.d/user-file```
4) I would hope this be somehow enforced for all scripts?
###
lsb_release -rd
Description:Ubuntu 14.04.2 LTS
Release:14.04
###
apt-cache policy initramfs-tools
initramfs-tools:
Installed: 0.103ubuntu4.2
Candidate: 0.103ubuntu4.2
Version table:
*** 0.103ubuntu4.2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
Packages
100 /var/lib/dpkg/status
0.103ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
--
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/1482810
Title:
dropbear DEVICE variable is ignored when sourced from conf.d
Status in initramfs-tools package in Ubuntu:
New
Bug description:
1) this is what /usr/share/initramfs-tools/init does:
```
. /conf/initramfs.conf
for conf in conf/conf.d/*; do
[ -f ${conf} ] . ${conf}
done
. /scripts/functions
```
2) this is what /usr/share/initramfs-tools/scripts/init-premount/dropbear
does:
```
. /scripts/functions
. /conf/initramfs.conf
configure_networking
```
3) bug result: ```configure_networking ``` will not find a $DEVICE variable
if the $DEVICE variable is overriden from some
```/etc/initramfs-tools/conf.d/user-file```
4) I would hope this be somehow enforced for all scripts?
###
lsb_release -rd
Description:Ubuntu 14.04.2 LTS
Release:14.04
###
apt-cache policy initramfs-tools
initramfs-tools:
Installed: 0.103ubuntu4.2
Candidate:
[Touch-packages] [Bug 1476692] Re: [Ubuntuphone] Unable to see the app preview screen in Unity8 on Meizu MX4
The same issue with Meizu MX 4 Ubuntu Edition -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1476692 Title: [Ubuntuphone] Unable to see the app preview screen in Unity8 on Meizu MX4 Status in unity-scope-click package in Ubuntu: Incomplete Bug description: Hi I try to press long on an app to go to the app preview screen on Unity, but it takes a long moment, trying to refresh and fail to load any information Happened on Meizu MX 4 Ubuntu Edition Cheers, Winael To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1476692/+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 1476692] Re: [Ubuntuphone] Unable to see the app preview screen in Unity8 on Meizu MX4
The Apps is just hanging. The are no errors in log file, seems also there is no any new crash file in /var/crash directory after this. The same behaviour sometimes happening when trying to open and install application in software centre. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1476692 Title: [Ubuntuphone] Unable to see the app preview screen in Unity8 on Meizu MX4 Status in unity-scope-click package in Ubuntu: Incomplete Bug description: Hi I try to press long on an app to go to the app preview screen on Unity, but it takes a long moment, trying to refresh and fail to load any information Happened on Meizu MX 4 Ubuntu Edition Cheers, Winael To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1476692/+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 1476798] [NEW] Can't uninstall application
Public bug reported: Do a long press on the application on the Installed category. Actual: 'App Preview' window is blank. Expect: App Preview and Uninstall button are displayed. Ubuntu Release: Ubuntu 15.04(r3) Phone: Meizu MX4 ** Affects: unity-scope-click (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1476798 Title: Can't uninstall application Status in unity-scope-click package in Ubuntu: New Bug description: Do a long press on the application on the Installed category. Actual: 'App Preview' window is blank. Expect: App Preview and Uninstall button are displayed. Ubuntu Release: Ubuntu 15.04(r3) Phone: Meizu MX4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1476798/+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 1461850] [NEW] Unable to Log In to Gnome 3.16 Desktop
Public bug reported: I installed Gnome 3.16 from the gnome-staging PPA on my Ubuntu 15.04 (previously updated from 14.04), but I am unable to log into the Gnome desktop, both on a cold boot or after logging out from Unity. What I expect to happen: Selecting gdm as the default dekstop manager takes me to the Gnome greeter when starting my machine. If lightdm is selected, I am able to log into Gnome by choosing the appropriate session at the Unity greeter. What actually happened: With gdm selected, the system boots to a black screen with only the mouse cursor showing. It is not frozen (I can move the mouse and switch to TTY), but no other GUI element loads. With lightdm selected, I am able to log into Unity, but if I choose Gnome I get a black screen for a couple of seconds after typing my password, then I'm back at the login screen. I have tried the following suggestions I found online, but to no avail: - remove nvidia-* packages - remove the .Xauthority file - manually restart gdm/lightdm - manually stop gdm then run startx - do a dist-upgrade The only potentially useful log info I can find is in /var/log/gdm/(null)-greeter.log: (WW) xf86CloseConsole: KDSETMODE failed: Input/output error (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error (EE) Fatal server error: (EE) xf86CloseConsole: VT_ACTIVATE failed: Input/output error (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at /var/log/Xorg.0.log for additional information. (EE) (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x7f13a8d92556] (EE) 1: /usr/bin/X (0x7f13a8bdf000+0x1b7749) [0x7f13a8d96749] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f13a68a5000+0x352f0) [0x7f13a68da2f0] (EE) 3: ?? [0x7f13ab7f08c0] (EE) (EE) Segmentation fault at address 0x7f13ab7f08c0 (EE) FatalError re-entered, aborting (EE) Caught signal 11 (Segmentation fault). Server aborting There is no error message in /var/log/Xorg.0.log. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Jun 4 12:10:36 2015 DistUpgraded: 2015-06-01 01:05:16,590 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: vivid DistroVariant: kubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0616] InstallationDate: Installed on 2014-03-16 (444 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. Vostro 5470 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic root=UUID=fababcc7-f83d-4082-9cc1-89aea60c2768 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to vivid on 2015-05-31 (3 days ago) dmi.bios.date: 12/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0G5M5F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd12/06/2013:svnDellInc.:pnVostro5470:pvr:rvnDellInc.:rn0G5M5F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Vostro 5470 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Jun 2 17:59:42 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: intel(G1): [drm] failed to set drm interface version: Permission denied [13]. intel(G1): Failed to claim DRM device. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5238 vendor CMN xserver.version:
[Touch-packages] [Bug 1461695] [NEW] RTL8723BE wifi connection drops out every 20-30 min
Public bug reported: so i have to reboot very often. Besides, the internet is very slow comparing with windows Please help to solve the problem Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM Controller [8086:0a04] (rev 0b) Subsystem: Lenovo Device [17aa:3978] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: [e0] Vendor Specific Information: Len=0c ? 00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 59 Region 0: Memory at b000 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at a000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 4000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0f00c Data: 41a1 Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915 00:03.0 Audio device [0403]: Intel Corporation Haswell-ULT HD Audio Controller [8086:0a0c] (rev 0b) Subsystem: Lenovo Device [17aa:3978] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 61 Region 0: Memory at b051 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0f00c Data: 41c1 Capabilities: [70] Express (v1) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- Kernel driver in use: snd_hda_intel 00:14.0 USB controller [0c03]: Intel Corporation Lynx Point-LP USB xHCI HC [8086:9c31] (rev 04) (prog-if 30 [XHCI]) Subsystem: Lenovo Device [17aa:3978] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 57 Region 0: Memory at b050 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Address: fee0f00c Data: 4181 Kernel driver in use: xhci_hcd 00:16.0 Communication controller [0780]: Intel Corporation Lynx Point-LP HECI #0 [8086:9c3a] (rev 04) Subsystem: Lenovo Device [17aa:3978] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 60 Region 0: Memory at b0518000 (64-bit, non-prefetchable) [size=32] Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0f00c Data: 41b1 Kernel
[Touch-packages] [Bug 1441592] [NEW] Unity restart broken (Vivid)
Public bug reported: Restarting Unity no longer works properly in Ubuntu 15.04 Vivid Vervet. Steps to reproduce: press ALT + F2, type Unity and press ENTER. What should occur: Unity should be restarted without logging out the user. What actually occurs: the LightDM login screen greeter shows up (so the user is logged out) instead of just restarting Unity. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150330-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Apr 8 14:50:13 2015 InstallationDate: Installed on 2015-03-11 (28 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1441592 Title: Unity restart broken (Vivid) Status in unity package in Ubuntu: New Bug description: Restarting Unity no longer works properly in Ubuntu 15.04 Vivid Vervet. Steps to reproduce: press ALT + F2, type Unity and press ENTER. What should occur: Unity should be restarted without logging out the user. What actually occurs: the LightDM login screen greeter shows up (so the user is logged out) instead of just restarting Unity. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150330-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Apr 8 14:50:13 2015 InstallationDate: Installed on 2015-03-11 (28 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1441592/+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 1437674] [NEW] Ubuntu bq Aquaris always showing roaming is on when usin 2g/3g network
Public bug reported: While using Ubuntu on bq Aquaris E4.5 i always get Roaming as active if using 2g/3g setting for the cellular data. If a set the connection type to 2g only, then all is OK, I can call and recieve calls, use mobile internet etc. If I use the 2g/3g setting, then the notification are shows Roaming as active, even thow the Roaming setting in Ubuntu thouch is disabled, and I cannot use mobile internet. I can recieve calls, thow. My ISP is Telekom Romania, Ubuntu touch build number 20, image part 20150312 (Utopic Unicorn). ** Affects: indicator-network (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1437674 Title: Ubuntu bq Aquaris always showing roaming is on when usin 2g/3g network Status in indicator-network package in Ubuntu: New Bug description: While using Ubuntu on bq Aquaris E4.5 i always get Roaming as active if using 2g/3g setting for the cellular data. If a set the connection type to 2g only, then all is OK, I can call and recieve calls, use mobile internet etc. If I use the 2g/3g setting, then the notification are shows Roaming as active, even thow the Roaming setting in Ubuntu thouch is disabled, and I cannot use mobile internet. I can recieve calls, thow. My ISP is Telekom Romania, Ubuntu touch build number 20, image part 20150312 (Utopic Unicorn). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1437674/+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 1437674] Re: Ubuntu bq Aquaris always showing roaming is on when usin 2g/3g network
** Changed in: indicator-network (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1437674 Title: Ubuntu bq Aquaris always showing roaming is on when usin 2g/3g network Status in indicator-network package in Ubuntu: Incomplete Bug description: While using Ubuntu on bq Aquaris E4.5 i always get Roaming as active if using 2g/3g setting for the cellular data. If a set the connection type to 2g only, then all is OK, I can call and recieve calls, use mobile internet etc. If I use the 2g/3g setting, then the notification are shows Roaming as active, even thow the Roaming setting in Ubuntu thouch is disabled, and I cannot use mobile internet. I can recieve calls, thow. My ISP is Telekom Romania, Ubuntu touch build number 20, image part 20150312 (Utopic Unicorn). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1437674/+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 1387219] Re: Mouse pointer disappears and cursor stops blinking
So is anybody going to do something about this any time soon? Or do we have to wait another 4 years for this to be fixed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1387219 Title: Mouse pointer disappears and cursor stops blinking Status in GtkSourceView Widget: Expired Status in anjuta package in Ubuntu: Confirmed Status in gedit package in Ubuntu: Confirmed Status in ibus package in Ubuntu: Confirmed Bug description: Open gedit. Notice the cursor is blinking. Type a few lines of text. Highilight some of the text. Press CTRLc to cut the text. Notice that the mouse ponter is invisible while hovering over the gedit window. Notice that the gedit cursor is no longer blinking. ***Workaround*** sudo apt-get install ibus-gtk $ uname -a Linux XYZ 3.16.0-23-generic #31-Ubuntu SMP Tue Oct 21 17:56:17 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.10 Release: 14.10 Codename: utopic To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1387219/+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 1328213] Re: you can accidentally resize windows when they are not even visible while in show desktop mode
*** This bug is a duplicate of bug 1324104 *** https://bugs.launchpad.net/bugs/1324104 Hello. I can confirm this bug, although i didn't know what it was as i am used to work with maximised or semi-maximised windows and as such use super+d a lot. If i were to describe it, that would be something like resize cursor appears at random places on desktop. 14.04 x86_64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1328213 Title: you can accidentally resize windows when they are not even visible while in show desktop mode Status in unity package in Ubuntu: New Bug description: This is unbelievable. Steps to reproduce: 1. make sure you have a few windows open and not maximized 2. hit ctrl+super+D to hide all windows and show the desktop 3. move the mouse around slowly, especially around where you remember some windows' edges were when the windows were visible Expected: nothing: the mouse cursor should remain the default one and any mouse action should always interact with the desktop and its icons Observed: the mouse cursor behaves as if the hidden windows were there. You suddenly see the mouse cursor change to the window- resizing cursor, and if you then click and drag, you will actually resize the windows that you are not seing. When you then hit Ctrl+Super+D again and the windows show up back, you'll see what you've done to them. Not to mention this often prevents you from properly interacting with the icons on the desktop.ç One more screwed-upness of the poorly designed and worse implemented show/hide desktop feature in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Jun 9 20:13:36 2014 InstallationDate: Installed on 2013-10-11 (241 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1328213/+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 1354498] Re: Switcher Icons emblem (count) is too small
** Changed in: unity/7.2 Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1354498 Title: Switcher Icons emblem (count) is too small Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [ Impact] The emblem size does not change as the icon size is adjusted. [ Test Case ] (1) Use the System Settings Displays Scale for menus and title bars slider to adjust the Swicther icon size. (2) Observe the size of the badge. It should scale with the icon size. [ Regression Potential Any code change to the Unity desktop shell has the potential to introduce new crashers or lockers. [ Other Info ] The Unity SRU fix for Ubuntu 14.04 LTS was cherry-picked from Ubuntu 14.10 where it has been in production use for some time with no apparent regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1354498/+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 1417037] Re: Upgrade to 7.4.4-1ubuntu2.5 hangs
Try to kill the process: /bin/sh /var/lib/dpkg/info/rsyslog.postinst configure 7.4.4-1ubuntu2.3 So that the install process can at least finish configuring the other packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1417037 Title: Upgrade to 7.4.4-1ubuntu2.5 hangs Status in rsyslog package in Ubuntu: Confirmed Bug description: I've just ran an update+dist-upgrade which pulled 7.4.4-1ubuntu2.5. It's sat there doing nothing. CTRL+C won't kill it. Htop shows that the last process to be created is stop rsyslog which follows invoke-rc.d rsyslog restart. dpkg.log: 2015-02-02 09:39:10 configure rsyslog:amd64 7.4.4-1ubuntu2.5 none 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status unpacked rsyslog:amd64 7.4.4-1ubuntu2.5 2015-02-02 09:39:10 status half-configured rsyslog:amd64 7.4.4-1ubuntu2.5 I have KILLed stop rsyslog which then moves on to start rsyslog which I have also had to KILL. Setting up rsyslog (7.4.4-1ubuntu2.5) ... The user `syslog' is already a member of `adm'. Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Terminated Terminated invoke-rc.d: initscript rsyslog, action restart failed. dpkg: error processing package rsyslog (--configure): subprocess installed post-installation script returned error exit status 143 Setting up linux-image-virtual-lts-utopic (3.16.0.30.23) ... Setting up linux-libc-dev:amd64 (3.13.0-45.74) ... Setting up python3-software-properties (0.92.37.3) ... Setting up software-properties-common (0.92.37.3) ... Errors were encountered while processing: rsyslog E: Sub-process /usr/bin/dpkg returned an error code (1) W: Operation was interrupted before it could finish ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rsyslog 7.4.4-1ubuntu2.5 ProcVersionSignature: Ubuntu 3.16.0-29.39~14.04.1-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Mon Feb 2 09:43:26 2015 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1417037/+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 1391857]
CONFIRMING for cairo v1.13.1 $ cat /etc/system-release uname -a Fedora release 20 (Heisenbug) Linux localhost.localdomain 3.17.7-200.fc20.x86_64 #1 SMP Wed Dec 17 03:35:33 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ yum info installed cairo Loaded plugins: langpacks, priorities, refresh-packagekit Installed Packages Name: cairo Arch: x86_64 Version : 1.13.1 Release : 0.1.git337ab1f.fc20 Size: 1.7 M Repo: installed From repo : fedora Summary : A 2D graphics library URL : http://cairographics.org License : LGPLv2 or MPLv1.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1391857 Title: libcairo segfaults when rendering video streams, e.g. youtube videos in webkit based browsers Status in Cairo Graphics Library: Confirmed Status in cairo package in Ubuntu: Fix Released Status in midori package in Ubuntu: Confirmed Status in webkitgtk package in Ubuntu: Confirmed Status in cairo source package in Trusty: Fix Released Bug description: * Impact The libcairo version (1.13) that is used on Ubuntu 14.04 contains a bug the leads to a segementation fault (see https://bugs.freedesktop.org/show_bug.cgi?id=81699) when rendering certain video streams. E.g. webkit based browser that render Youtube videos will eventually crash. * Testcase try to open https://www.youtube.com/watch?v=b1XGPvbWn0A in midori browser * Regression potential check that GTK and webkit still work correctly (no segfault, no rendering issues) --- The bug has been fixed upstream, libcairo 1.14 does not segfault, so it would be very desirable that the libcairo2 package in Ubuntu gets updated to version 1.14 of libcairo. To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1391857/+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 1411620] Re: Unity requires restart after enabling always-show-menus or LIM
@Marco: what other features would you like me to test? I can't think of anything else that would require a restart (besides the scaling factor, already tested by Mateusz). Also, note that I tested this in VirtualBox. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1411620 Title: Unity requires restart after enabling always-show-menus or LIM Status in unity package in Ubuntu: Confirmed Bug description: Unity requires restart after enabling always-show-menus or LIM. When I first tested the always-show-menus (about 3-4 weeks ago, by using Marco's branch), I don't remember it requiring a restart. Also, enabling LIM in Ubuntu 14.04 and 14.10 doesn't require restarting Unity but it does with the latest Unity in Ubuntu 15.04 Vivid Vervet. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150115-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic i686 ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Jan 16 13:23:00 2015 InstallationDate: Installed on 2015-01-16 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20150116) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1411620/+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 1411620] [NEW] Unity requires restart after enabling always-show-menus or LIM
Public bug reported: Unity requires restart after enabling always-show-menus or LIM. When I first tested the always-show-menus (about 3-4 weeks ago, by using Marco's branch), I don't remember it requiring a restart. Also, enabling LIM in Ubuntu 14.04 and 14.10 doesn't require restarting Unity but it does with the latest Unity in Ubuntu 15.04 Vivid Vervet. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150115-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic i686 ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Jan 16 13:23:00 2015 InstallationDate: Installed on 2015-01-16 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20150116) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1411620 Title: Unity requires restart after enabling always-show-menus or LIM Status in unity package in Ubuntu: New Bug description: Unity requires restart after enabling always-show-menus or LIM. When I first tested the always-show-menus (about 3-4 weeks ago, by using Marco's branch), I don't remember it requiring a restart. Also, enabling LIM in Ubuntu 14.04 and 14.10 doesn't require restarting Unity but it does with the latest Unity in Ubuntu 15.04 Vivid Vervet. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150115-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic i686 ApportVersion: 2.15.1-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Jan 16 13:23:00 2015 InstallationDate: Installed on 2015-01-16 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20150116) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1411620/+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 1353013] Re: Popping/Crackling sound when playing audio in Ubuntu 14.04
I have the same thing happening on Ubuntu 14.04. Identical; popping and when that happens volume goes for a few millisecs to another level then back. In the audio settings, analogue output dissapears exactly when the sound pops and reappears immediately. As the initial poster mentioned on the forum, if I plug the speakers/headphones in the front jack of the PC it works normally - no popping. So popping only happens when only back side jack is used with speakers. Forum post: http://ubuntuforums.org/showthread.php?t=2245429 For example if I have speakers conncted to back jack and headphones to front jack sound also works normally in both. Is this a hardware (front jack malfunction) or software problem? Should I go back to the store and ask for replacements? -- 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/1353013 Title: Popping/Crackling sound when playing audio in Ubuntu 14.04 Status in nvidia-hdmi-pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When listening to audio (pandora internet radio, youtube, etc.), I get a repeated popping/crackling sound. When I look at the sound settings while this is happening, I see Headphone Output rapidly appearing and then disappearing in the Play Sound Through section. The appearance and disappearance of Headphone Output coincides with the popping and crackling of the sound. I am wondering if it has anything to do with the fact that my Nvidia card has a built-in HDMI card that might be interfering with my onboard sound: $ cat /proc/asound/cards 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xf722 irq 54 1 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xf708 irq 55 cat /proc/asound/modules 0 snd_hda_intel 1 snd_hda_intel Obviously blacklisting snd_hda_intel in /etc/modprobe.d/blacklist.conf won't work, because it then disables all sound (both onboard and nvidia are listed as snd_hda_intel). Description: Ubuntu 14.04.1 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim1856 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 5 10:17:34 2014 InstallationDate: Installed on 2014-04-17 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0132.2011.1007.1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-205 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0132.2011.1007.1505:bd10/07/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-205:cvn:ct3:cvr: modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2014-08-04T12:00:53.999120 mtime.conffile..etc.pulse.default.pa: 2014-08-04T12:18:08.532386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-hdmi-pulseaudio/+bug/1353013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 573493] Re: No sound from headphone jack
Ok. Thank you. On Thu, Nov 13, 2014 at 6:03 PM, Rolf Leggewie 573...@bugs.launchpad.net wrote: OK, that's unfortunate. Thanks for reporting and getting back to me. I'll do the housekeeping and close this ticket as unreproducible then ** Changed in: alsa-driver (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/573493 Title: No sound from headphone jack Status in “alsa-driver” package in Ubuntu: Invalid Bug description: As a follow on from bug #549289; No sound from headphone jack but following code fixes the problem: /etc/modprobe.conf/alsa-base.conf code options snd-hda-intel model=olpc-xo-1_5 /code Subsystem ID from my /proc/asound/card0/codec#0 is: Codec: Conexant CX20582 (Pebble) Address: 0 Function Id: 0x1 Vendor Id: 0x14f15066 Subsystem Id: 0x17aa21b4 Revision Id: 0x100300 And my lspci says: andrew@fuji:~$ lspci ... 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/573493/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/573493 Title: No sound from headphone jack Status in “alsa-driver” package in Ubuntu: Invalid Bug description: As a follow on from bug #549289; No sound from headphone jack but following code fixes the problem: /etc/modprobe.conf/alsa-base.conf code options snd-hda-intel model=olpc-xo-1_5 /code Subsystem ID from my /proc/asound/card0/codec#0 is: Codec: Conexant CX20582 (Pebble) Address: 0 Function Id: 0x1 Vendor Id: 0x14f15066 Subsystem Id: 0x17aa21b4 Revision Id: 0x100300 And my lspci says: andrew@fuji:~$ lspci ... 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/573493/+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 1311316] Re: After locking screen there is no input field to type password for unlock
It is happens, when screen is starting to lock and I move mouse to prevent locking. So I got funny my login name without password field. It happens periodically. unity --replace helps me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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
