[Touch-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Xenial: Fix Committed Status in libqmi source package in Xenial: Fix Committed Status in modemmanager source package in Xenial: Fix Committed Bug description: [Impact] * the new modemmanager packages bring in DW5816 supporting. * These modemmanager packages is needed to support new devices. [Test Case] * install modemmanager and it's dependencies from -proposed libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1 libmbim-proxy 1.14.0-1ubuntu0.16.04.1 libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1 libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1 libqmi-proxy 1.16.2-1ubuntu0.16.04.1 modemmanager 1.6.4-1ubuntu0.16.04.1 * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network-manager, gnome-control-center etc.) [Regression Potential] * The package comes from Zesty and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] We would like to upgrade xenial to 1.6 series so it supports the same modems as the modem-manager snap, specifically some new Sierra modems (HL8548 and others from HL series, popular in IoT devices). These are the packages that would need to be updated: libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap libqmi: 1.12.6-1 in xenial, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1725190/+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 1742941] Re: zlib: improve crc32 performance on P8
this is not yet committed upstream (2018-01-30). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1742941 Title: zlib: improve crc32 performance on P8 Status in The Ubuntu-power-systems project: Triaged Status in zlib package in Ubuntu: New Bug description: Calculate the checksum of data that is 16 byte aligned and a multiple of 16 bytes. The first step is to reduce it to 1024 bits. We do this in 8 parallel chunks in order to mask the latency of the vpmsum instructions. If we have more than 32 kB of data to checksum we repeat this step multiple times, passing in the previous 1024 bits. The next step is to reduce the 1024 bits to 64 bits. This step adds 32 bits of 0s to the end - this matches what a CRC does. We just calculate constants that land the data in this 32 bits. We then use fixed point Barrett reduction to compute a mod n over GF(2) for n = CRC using POWER8 instructions. We use x = 32. http://en.wikipedia.org/wiki/Barrett_reduction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1742941/+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 1746164] Re: Enable Bluetooth-Wifi coexistence by default [bluetooth audio and network skip on Wifi activity]
Please keep this bug about fixing the issue for ath9k wifi only. So this bug is not a duplicate of bug 405294. This bug is open and should be fixed in the kernel (package "linux"). ** This bug is no longer a duplicate of bug 405294 A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] -- 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/1746164 Title: Enable Bluetooth-Wifi coexistence by default [bluetooth audio and network skip on Wifi activity] Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: By default BT audio works fine on Ubuntu - if there is no WiFi active: Both work on the same frequency range, 2 WiFi channel is about 20 Bluetooth Channels wide and every time a WiFi package is sent bluetooth risks a packet loss. Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the following content: options ath9k btcoex_enable=1 bt_ant_diversity=1 resolves the problem and drastically increases bluetooth throughput for all other use cases (bluetooth networking that doesn't drop every time the WiFi probes something, lower latency Bluetooth HIDs. We should ship things in a way that they work out-of-the-box => I am all for providing this file with Ubuntu, possibly with Bluez. In the case of my laptop btcoex_enable=1 would already do the trick. Technical background: - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.46-0ubuntu4 Uname: Linux 4.15.0-041500rc9-lowlatency x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jan 30 06:40:12 2018 EcryptfsInUse: Yes InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire S7-391 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.09 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm dmi.board.vendor: Acer dmi.board.version: V2.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S7-391 dmi.product.version: V2.09 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:94:23:49:1B:BC ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:688 acl:0 sco:0 events:49 errors:0 TX bytes:3167 acl:0 sco:0 commands:49 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1746164/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
Since the history of Bug 1746164 isn't visible here I'm adding the short form here, too: By default BT audio works fine on Ubuntu - if there is no WiFi active: Both work on the same frequency range, 2 WiFi channel is about 20 Bluetooth Channels wide and every time a WiFi package is sent bluetooth risks a packet loss. We should ship things in a way that they work out-of-the-box => I am all for providing this file with Ubuntu, possibly with Bluez. In the case of my laptop btcoex_enable=1 would already do the trick. Technical background: - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity Until the kernel default is updated Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the following content: options ath9k btcoex_enable=1 bt_ant_diversity=1 should do the trick. -- 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/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
Added "Linux" as affected package since the problem is caused by a kernel default, not by a bug in bluez, see Bug 1746164. -- 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/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
A workaround that works on my system can be found at: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1746164 ** Attachment added: "The output of lspci on my system." https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294/+attachment/5045388/+files/lspci.txt ** Also affects: linux (Ubuntu) Importance: Undecided Status: 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/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 1746164] Re: Enable Bluetooth-Wifi coexistence by default [bluetooth audio and network skip on Wifi activity]
*** This bug is a duplicate of bug 405294 *** https://bugs.launchpad.net/bugs/405294 ...or do we want to mark this bug as duplicate of bug 405294? ** This bug has been marked a duplicate of bug 405294 A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] -- 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/1746164 Title: Enable Bluetooth-Wifi coexistence by default [bluetooth audio and network skip on Wifi activity] Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: By default BT audio works fine on Ubuntu - if there is no WiFi active: Both work on the same frequency range, 2 WiFi channel is about 20 Bluetooth Channels wide and every time a WiFi package is sent bluetooth risks a packet loss. Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the following content: options ath9k btcoex_enable=1 bt_ant_diversity=1 resolves the problem and drastically increases bluetooth throughput for all other use cases (bluetooth networking that doesn't drop every time the WiFi probes something, lower latency Bluetooth HIDs. We should ship things in a way that they work out-of-the-box => I am all for providing this file with Ubuntu, possibly with Bluez. In the case of my laptop btcoex_enable=1 would already do the trick. Technical background: - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.46-0ubuntu4 Uname: Linux 4.15.0-041500rc9-lowlatency x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jan 30 06:40:12 2018 EcryptfsInUse: Yes InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire S7-391 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.09 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm dmi.board.vendor: Acer dmi.board.version: V2.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S7-391 dmi.product.version: V2.09 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:94:23:49:1B:BC ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:688 acl:0 sco:0 events:49 errors:0 TX bytes:3167 acl:0 sco:0 commands:49 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1746164/+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 1746164] Re: Enable Bluetooth-Wifi coexistence by default [bluetooth audio and network skip on Wifi activity]
*** This bug is a duplicate of bug 405294 *** https://bugs.launchpad.net/bugs/405294 The corrected version of my patch (finally containing all files). ** Patch added: "bluez.patch" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1746164/+attachment/5045387/+files/bluez.patch -- 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/1746164 Title: Enable Bluetooth-Wifi coexistence by default [bluetooth audio and network skip on Wifi activity] Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: By default BT audio works fine on Ubuntu - if there is no WiFi active: Both work on the same frequency range, 2 WiFi channel is about 20 Bluetooth Channels wide and every time a WiFi package is sent bluetooth risks a packet loss. Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the following content: options ath9k btcoex_enable=1 bt_ant_diversity=1 resolves the problem and drastically increases bluetooth throughput for all other use cases (bluetooth networking that doesn't drop every time the WiFi probes something, lower latency Bluetooth HIDs. We should ship things in a way that they work out-of-the-box => I am all for providing this file with Ubuntu, possibly with Bluez. In the case of my laptop btcoex_enable=1 would already do the trick. Technical background: - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.46-0ubuntu4 Uname: Linux 4.15.0-041500rc9-lowlatency x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jan 30 06:40:12 2018 EcryptfsInUse: Yes InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire S7-391 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.09 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm dmi.board.vendor: Acer dmi.board.version: V2.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S7-391 dmi.product.version: V2.09 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:94:23:49:1B:BC ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:688 acl:0 sco:0 events:49 errors:0 TX bytes:3167 acl:0 sco:0 commands:49 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1746164/+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 1746164] Re: Enable Bluetooth-Wifi coexistence by default [bluetooth audio and network skip on Wifi activity]
*** This bug is a duplicate of bug 405294 *** https://bugs.launchpad.net/bugs/405294 I currently run the newest vanilla kernel using an Acer Aspire S7 with an Intel chipset. Still my patch is needed on my system. --- I have no experience in getting things changed in the kernel => attaching the corrected patch. But if you reassign the bug to "linux- kernel" and mark this bug as duplicate of bug 405294 I'll try to do my very best. -- 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/1746164 Title: Enable Bluetooth-Wifi coexistence by default [bluetooth audio and network skip on Wifi activity] Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: By default BT audio works fine on Ubuntu - if there is no WiFi active: Both work on the same frequency range, 2 WiFi channel is about 20 Bluetooth Channels wide and every time a WiFi package is sent bluetooth risks a packet loss. Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the following content: options ath9k btcoex_enable=1 bt_ant_diversity=1 resolves the problem and drastically increases bluetooth throughput for all other use cases (bluetooth networking that doesn't drop every time the WiFi probes something, lower latency Bluetooth HIDs. We should ship things in a way that they work out-of-the-box => I am all for providing this file with Ubuntu, possibly with Bluez. In the case of my laptop btcoex_enable=1 would already do the trick. Technical background: - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.46-0ubuntu4 Uname: Linux 4.15.0-041500rc9-lowlatency x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jan 30 06:40:12 2018 EcryptfsInUse: Yes InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire S7-391 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.09 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm dmi.board.vendor: Acer dmi.board.version: V2.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S7-391 dmi.product.version: V2.09 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:94:23:49:1B:BC ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:688 acl:0 sco:0 events:49 errors:0 TX bytes:3167 acl:0 sco:0 commands:49 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1746164/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
On second thoughts... it's been suggested today that this problem can be caused by some wifi drivers disabling Bluetooth/Wifi coexistence by default. When this happens and you're connected to a 2.4GHz wifi network you wifi signal may drown out the Bluetooth. So I wonder; can people who experience this problem please let us know what model wifi/bluetooth chips you have? You can probably get that information by running "lspci -k" and maybe from "lsusb". -- 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/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 1746164] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1746164 Title: Enable Bluetooth-Wifi coexistence by default [bluetooth audio and network skip on Wifi activity] Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: By default BT audio works fine on Ubuntu - if there is no WiFi active: Both work on the same frequency range, 2 WiFi channel is about 20 Bluetooth Channels wide and every time a WiFi package is sent bluetooth risks a packet loss. Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the following content: options ath9k btcoex_enable=1 bt_ant_diversity=1 resolves the problem and drastically increases bluetooth throughput for all other use cases (bluetooth networking that doesn't drop every time the WiFi probes something, lower latency Bluetooth HIDs. We should ship things in a way that they work out-of-the-box => I am all for providing this file with Ubuntu, possibly with Bluez. In the case of my laptop btcoex_enable=1 would already do the trick. Technical background: - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.46-0ubuntu4 Uname: Linux 4.15.0-041500rc9-lowlatency x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jan 30 06:40:12 2018 EcryptfsInUse: Yes InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire S7-391 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.09 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm dmi.board.vendor: Acer dmi.board.version: V2.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S7-391 dmi.product.version: V2.09 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:94:23:49:1B:BC ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:688 acl:0 sco:0 events:49 errors:0 TX bytes:3167 acl:0 sco:0 commands:49 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1746164/+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 1746164] Re: Enable Bluetooth-Wifi coexistence by default [bluetooth audio and network skip on Wifi activity]
Also, if all you would like to change is kernel parameters: options ath9k btcoex_enable=1 bt_ant_diversity=1 then that's a kernel bug/enhancement. Not something that bluez should be involved in... It appears those two parameters are uninitialized by default (so default to zero/off??): https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/ath/ath9k/init.c#n58 Sounds like a simple kernel fix/enhancement to turn them on by default. ** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (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/1746164 Title: Enable Bluetooth-Wifi coexistence by default [bluetooth audio and network skip on Wifi activity] Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: By default BT audio works fine on Ubuntu - if there is no WiFi active: Both work on the same frequency range, 2 WiFi channel is about 20 Bluetooth Channels wide and every time a WiFi package is sent bluetooth risks a packet loss. Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the following content: options ath9k btcoex_enable=1 bt_ant_diversity=1 resolves the problem and drastically increases bluetooth throughput for all other use cases (bluetooth networking that doesn't drop every time the WiFi probes something, lower latency Bluetooth HIDs. We should ship things in a way that they work out-of-the-box => I am all for providing this file with Ubuntu, possibly with Bluez. In the case of my laptop btcoex_enable=1 would already do the trick. Technical background: - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.46-0ubuntu4 Uname: Linux 4.15.0-041500rc9-lowlatency x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jan 30 06:40:12 2018 EcryptfsInUse: Yes InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire S7-391 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.09 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm dmi.board.vendor: Acer dmi.board.version: V2.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S7-391 dmi.product.version: V2.09 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:94:23:49:1B:BC ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:688 acl:0 sco:0 events:49 errors:0 TX bytes:3167 acl:0 sco:0 commands:49 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1746164/+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 1746164] Re: Enable Bluetooth-Wifi coexistence by default [bluetooth audio and network skip on Wifi activity]
Interestingly, it appears Intel enables bt_coex for their chips by default: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/intel/iwlwifi /iwl-modparams.h -- 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/1746164 Title: Enable Bluetooth-Wifi coexistence by default [bluetooth audio and network skip on Wifi activity] Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: By default BT audio works fine on Ubuntu - if there is no WiFi active: Both work on the same frequency range, 2 WiFi channel is about 20 Bluetooth Channels wide and every time a WiFi package is sent bluetooth risks a packet loss. Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the following content: options ath9k btcoex_enable=1 bt_ant_diversity=1 resolves the problem and drastically increases bluetooth throughput for all other use cases (bluetooth networking that doesn't drop every time the WiFi probes something, lower latency Bluetooth HIDs. We should ship things in a way that they work out-of-the-box => I am all for providing this file with Ubuntu, possibly with Bluez. In the case of my laptop btcoex_enable=1 would already do the trick. Technical background: - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.46-0ubuntu4 Uname: Linux 4.15.0-041500rc9-lowlatency x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jan 30 06:40:12 2018 EcryptfsInUse: Yes InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire S7-391 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.09 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm dmi.board.vendor: Acer dmi.board.version: V2.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S7-391 dmi.product.version: V2.09 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:94:23:49:1B:BC ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:688 acl:0 sco:0 events:49 errors:0 TX bytes:3167 acl:0 sco:0 commands:49 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1746164/+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 1746164] Re: Enable Bluetooth-Wifi coexistence by default [bluetooth audio and network skip on Wifi activity]
Thanks for the suggestion. It sounds like this may fix bug 405294 for some users. Unfortunately you forgot to attach "bluetooth-audio.conf" mentioned in your patch. ** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1746164 Title: Enable Bluetooth-Wifi coexistence by default [bluetooth audio and network skip on Wifi activity] Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: By default BT audio works fine on Ubuntu - if there is no WiFi active: Both work on the same frequency range, 2 WiFi channel is about 20 Bluetooth Channels wide and every time a WiFi package is sent bluetooth risks a packet loss. Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the following content: options ath9k btcoex_enable=1 bt_ant_diversity=1 resolves the problem and drastically increases bluetooth throughput for all other use cases (bluetooth networking that doesn't drop every time the WiFi probes something, lower latency Bluetooth HIDs. We should ship things in a way that they work out-of-the-box => I am all for providing this file with Ubuntu, possibly with Bluez. In the case of my laptop btcoex_enable=1 would already do the trick. Technical background: - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.46-0ubuntu4 Uname: Linux 4.15.0-041500rc9-lowlatency x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jan 30 06:40:12 2018 EcryptfsInUse: Yes InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire S7-391 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.09 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm dmi.board.vendor: Acer dmi.board.version: V2.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S7-391 dmi.product.version: V2.09 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:94:23:49:1B:BC ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:688 acl:0 sco:0 events:49 errors:0 TX bytes:3167 acl:0 sco:0 commands:49 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1746164/+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 1746164] Re: Enable Bluetooth-Wifi coexistence by default [bluetooth audio and network skip on Wifi activity]
The patch that resolves the problem. ** Patch added: "bluez.patch" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1746164/+attachment/5045345/+files/bluez.patch -- 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/1746164 Title: Enable Bluetooth-Wifi coexistence by default [bluetooth audio and network skip on Wifi activity] Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: By default BT audio works fine on Ubuntu - if there is no WiFi active: Both work on the same frequency range, 2 WiFi channel is about 20 Bluetooth Channels wide and every time a WiFi package is sent bluetooth risks a packet loss. Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the following content: options ath9k btcoex_enable=1 bt_ant_diversity=1 resolves the problem and drastically increases bluetooth throughput for all other use cases (bluetooth networking that doesn't drop every time the WiFi probes something, lower latency Bluetooth HIDs. We should ship things in a way that they work out-of-the-box => I am all for providing this file with Ubuntu, possibly with Bluez. In the case of my laptop btcoex_enable=1 would already do the trick. Technical background: - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.46-0ubuntu4 Uname: Linux 4.15.0-041500rc9-lowlatency x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jan 30 06:40:12 2018 EcryptfsInUse: Yes InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire S7-391 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.09 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm dmi.board.vendor: Acer dmi.board.version: V2.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S7-391 dmi.product.version: V2.09 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:94:23:49:1B:BC ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:688 acl:0 sco:0 events:49 errors:0 TX bytes:3167 acl:0 sco:0 commands:49 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1746164/+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 1746164] [NEW] Enable Bluetooth-Wifi coexistence by default [bluetooth audio and network skip on Wifi activity]
Public bug reported: By default BT audio works fine on Ubuntu - if there is no WiFi active: Both work on the same frequency range, 2 WiFi channel is about 20 Bluetooth Channels wide and every time a WiFi package is sent bluetooth risks a packet loss. Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the following content: options ath9k btcoex_enable=1 bt_ant_diversity=1 resolves the problem and drastically increases bluetooth throughput for all other use cases (bluetooth networking that doesn't drop every time the WiFi probes something, lower latency Bluetooth HIDs. We should ship things in a way that they work out-of-the-box => I am all for providing this file with Ubuntu, possibly with Bluez. In the case of my laptop btcoex_enable=1 would already do the trick. Technical background: - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.46-0ubuntu4 Uname: Linux 4.15.0-041500rc9-lowlatency x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jan 30 06:40:12 2018 EcryptfsInUse: Yes InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire S7-391 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.09 dmi.board.asset.tag: No Asset Tag dmi.board.name: Storm dmi.board.vendor: Acer dmi.board.version: V2.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.09:bd11/16/2012:svnAcer:pnAspireS7-391:pvrV2.09:rvnAcer:rnStorm:rvrV2.09:cvnAcer:ct10:cvrV2.09: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S7-391 dmi.product.version: V2.09 dmi.sys.vendor: Acer hciconfig: hci0: Type: Primary Bus: USB BD Address: 68:94:23:49:1B:BC ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN RX bytes:688 acl:0 sco:0 events:49 errors:0 TX bytes:3167 acl:0 sco:0 commands:49 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- 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/1746164 Title: Enable Bluetooth-Wifi coexistence by default [bluetooth audio and network skip on Wifi activity] Status in bluez package in Ubuntu: New Bug description: By default BT audio works fine on Ubuntu - if there is no WiFi active: Both work on the same frequency range, 2 WiFi channel is about 20 Bluetooth Channels wide and every time a WiFi package is sent bluetooth risks a packet loss. Creating a file named /etc/modprobe.d/bluetooth-audio.conf with the following content: options ath9k btcoex_enable=1 bt_ant_diversity=1 resolves the problem and drastically increases bluetooth throughput for all other use cases (bluetooth networking that doesn't drop every time the WiFi probes something, lower latency Bluetooth HIDs. We should ship things in a way that they work out-of-the-box => I am all for providing this file with Ubuntu, possibly with Bluez. In the case of my laptop btcoex_enable=1 would already do the trick. Technical background: - https://wireless.wiki.kernel.org/en/users/drivers/ath9k/btcoex - https://wiki.freebsd.org/dev/ath_hal(4)/AntennaDiversity ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.46-0ubuntu4 Uname: Linux 4.15.0-041500rc9-lowlatency x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jan 30 06:40:12 2018 EcryptfsInUse: Yes InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire S7-391 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-lowlatency root=UUID=6d0fd0ad-9048-4fdb-881a-eba6d6d13c3b ro rootflags=subvol=@ acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable nmi_watchdog=0 quiet splash acpi_backlight=vendor init=/lib/systemd/systemd intel_pstate=enable video=vesafb:ywrap,mtrr=3 nmi_watchdog=0 vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/1
[Touch-packages] [Bug 1220782] Re: ip xfrm state add crashes when supplied an algo
[Expired for iproute2 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: iproute2 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1220782
Title:
ip xfrm state add crashes when supplied an algo
Status in iproute2 package in Ubuntu:
Expired
Bug description:
This is valid for iproute2-ss17 which is default on Ubuntu 12.04
(LTS).
The crash appends when supplying enc, auth, comp, auth-trunc or aead and the
following key argumentis given as a string (as opposed to hexadecimal). When
trying to copy the key, it generates a segfault:
*** buffer overflow detected ***: /sbin/ip terminated
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x77921807]
/lib/x86_64-linux-gnu/libc.so.6(+0x109700)[0x77920700]
/lib/x86_64-linux-gnu/libc.so.6(+0x1089e6)[0x7791f9e6]
/sbin/ip[0x420d84]
/sbin/ip(do_xfrm_state+0x7a1)[0x421951]
/sbin/ip[0x405ad5]
/sbin/ip(main+0x2b4)[0x4056d4]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7783876d]
/sbin/ip[0x405959]
This buffer overflow is actually preposterous since __strncpy_chk is called
with 0 as its last argument:
0x00420d72: mov0x68(%rsp),%rsi
0x00420d77: movslq %r12d,%rdx
0x00420d7a: xor%ecx,%ecx
0x00420d7c: mov%r9,%rdi
=> 0x00420d7f: callq 0x404a10 <__strncpy_chk@plt>
("xor%ecx,%ecx" set the fourth argument to 0)
Which is equivalent to:
__strncpy_chk(buf, key, len, 0);
When obtaining the source package, the corresponding code looks like
that (from ip/xfrm_state.c, line 113):
static int xfrm_algo_parse(struct xfrm_algo *alg, enum xfrm_attr_type_t type,
char *name, char *key, char *buf, int max)
{
int len;
int slen = strlen(key);
#if 0
/* XXX: verifying both name and key is required! */
fprintf(stderr, "warning: ALGO-NAME/ALGO-KEY will send to kernel
promiscuously! (verifying them isn't implemented yet)\n");
#endif
strncpy(alg->alg_name, name, sizeof(alg->alg_name));
if (slen > 2 && strncmp(key, "0x", 2) == 0) {
} else {
len = slen;
if (len > 0) {
if (len > max)
invarg("\"ALGO-KEY\" makes buffer
overflow\n", key);
strncpy(buf, key, len); <- correct line which is
faulty in the assembly
}
}
alg->alg_key_len = len * 8;
return 0;
}
This code is actually valid but doesn't match the assembly from the
binary package.
This is quite annoying since it prevents from setting keys in a string
form, thus forcing the user to derivates itself the hexadecimal value
for the key when trying to setup an IPsec tunnel for example.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1220782/+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 1719004] Re: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed.
How about fixing this in 18.04? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1719004 Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. Status in CUPS: Fix Released Status in cups package in Ubuntu: Invalid Status in glibc package in Ubuntu: Confirmed Bug description: 1. Error: Package/cups-daemon2.2.4-7 (mutilated) 2. compiz-core/tmp/apport_core_q_vnqis (corrupted) ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: cups-daemon 2.2.4-7 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AssertionMessage: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. Date: Fri Sep 22 22:16:18 2017 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2017-05-27 (118 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Papersize: a4 ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcEnviron: LANG=el_GR.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: H110M-K D3 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0503:bd10/23/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-KD3:rvrRevX.0x: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 To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1719004/+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 1746149] [NEW] lightdm crashes when unlocking system- User attempting to unlock is logged out
Public bug reported: Sometimes when I go to unlock my system, lightdm will crash and log me out. This is infuriatingly annoying. This usually happens when my system is either locked and then left alone for over 20 minutes, or when my system locks due to inactivity. Ubuntu version: 16.04.3 LTS lightdm version: 1.18.3-0ubuntu1.1 500 What I expect to happen: 1) I lock the computer or it locks on it's own 2) It's left alone for over 20 minutes 3) I go to unlock 4) It unlocks and everything's open What actually happens: 1) I lock the computer or it locks on it's own 2) It's left alone for over 20 minutes 3) I go to unlock 4) The screen goes black for 2 to 5 seconds, then comes back up a login prompt 5) I login 6) I get a desktop, and everything's been closed This is the output of /var/log/lightdm/lightdm.log after the incident: [+93016.79s] DEBUG: Continue authentication [+93016.80s] DEBUG: Session pid=13591: Authentication complete with return value 0: Success [+93016.80s] DEBUG: Authenticate result for user the-computer-geek: Success [+93016.80s] DEBUG: User the-computer-geek authorized [+93016.81s] DEBUG: Greeter sets language en_US [+93016.86s] DEBUG: Greeter requests session xubuntu [+93016.86s] DEBUG: Seat seat0: Returning to existing user session the-computer-geek [+93016.86s] DEBUG: Unlocking login1 session c12 [+93016.86s] DEBUG: Activating VT 7 [+93016.96s] DEBUG: Seat seat0: Stopping greeter [+93016.96s] DEBUG: Session pid=13506: Sending SIGTERM [+93016.96s] DEBUG: Activating login1 session c12 [+93016.97s] DEBUG: Session pid=13591: Exited with return value 0 [+93016.97s] DEBUG: Seat seat0: Session stopped [+93016.97s] DEBUG: Seat seat0 changes active session to c12 [+93016.97s] DEBUG: Session c12 is already active [+93016.97s] DEBUG: Session pid=13506: Exited with return value 0 [+93016.97s] DEBUG: Seat seat0: Session stopped [+93016.97s] DEBUG: Seat seat0: Stopping display server, no sessions require it [+93016.97s] DEBUG: Sending signal 15 to process 13492 [+93017.03s] DEBUG: Process 13492 exited with return value 0 [+93017.03s] DEBUG: DisplayServer x-1: X server stopped [+93017.03s] DEBUG: Releasing VT 8 [+93017.03s] DEBUG: DisplayServer x-1: Removing X server authority /var/run/lightdm/root/:1 [+93017.03s] DEBUG: Seat seat0: Display server stopped [+93021.37s] DEBUG: Process 7864 terminated with signal 6 [+93021.37s] DEBUG: DisplayServer x-0: X server stopped [+93021.37s] DEBUG: Releasing VT 7 [+93021.37s] DEBUG: DisplayServer x-0: Removing X server authority /var/run/lightdm/root/:0 [+93021.37s] DEBUG: Seat seat0: Display server stopped [+93021.37s] DEBUG: Seat seat0: Stopping session [+93021.37s] DEBUG: Session pid=8073: Sending SIGTERM [+93021.37s] DEBUG: Seat seat0: Active display server stopped, starting greeter [+93021.37s] DEBUG: Seat seat0: Creating greeter session [+93021.37s] DEBUG: Seat seat0: Creating display server of type x [+93021.37s] DEBUG: Using VT 7 [+93021.37s] DEBUG: Seat seat0: Starting local X display on VT 7 [+93021.37s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log [+93021.37s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0 [+93021.37s] DEBUG: DisplayServer x-0: Launching X Server [+93021.37s] DEBUG: Launching process 17470: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch [+93021.37s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0 [+93021.96s] DEBUG: Session pid=8073: Exited with return value 0 [+93021.96s] DEBUG: Seat seat0: Session stopped [+93021.96s] DEBUG: Seat seat0: Stopping display server, no sessions require it [+93021.97s] DEBUG: Got signal 10 from process 17470 [+93021.97s] DEBUG: DisplayServer x-0: Got signal from X server :0 [+93021.97s] DEBUG: DisplayServer x-0: Connecting to XServer :0 [+93021.97s] DEBUG: Seat seat0: Display server ready, starting session authentication [+93021.98s] DEBUG: Session pid=17605: Started with service 'lightdm-greeter', username 'lightdm' [+93021.98s] DEBUG: Session pid=17605: Authentication complete with return value 0: Success [+93021.98s] DEBUG: Seat seat0: Session authenticated, running command [+93021.98s] DEBUG: Session pid=17605: Running command /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/lightdm-gtk-greeter [+93021.98s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm [+93021.98s] DEBUG: Session pid=17605: Logging to /var/log/lightdm/seat0-greeter.log [+93022.00s] DEBUG: Activating VT 7 [+93022.00s] DEBUG: Activating login1 session c16 [+93022.00s] DEBUG: Seat seat0 changes active session to c16 [+93022.00s] DEBUG: Session c16 is already active [+93022.07s] DEBUG: Greeter connected version=1.18.3 resettable=false [+93022.22s] DEBUG: Greeter start authentication for the-computer-geek [+93022.22s] DEBUG: Session pid=17678: Started with service 'lightdm', username 'the-computer-geek' [+93022.22s] DEBUG: Session pid=17678: Got 1 message(s) from PAM [+93022.22s] DEBUG:
[Touch-packages] [Bug 1745828] Re: Ubuntu 16.04 can't find any Bluetooth devices
Oh, actually this sounds like bug 1542743. Please also try the workaround mentioned there. -- 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/1745828 Title: Ubuntu 16.04 can't find any Bluetooth devices Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: It is ON and VISIBLE in the control panel. My iPhone can see two other devices but it can't see the computer, and the computer can't see anything, even if left searching for tens of minutes. The previous answers listed below suggest the following diagnostics Bluetooth not working after update How can I make my bluetooth works on Ubuntu 16.04? Ubuntu 16.04 bluetooth not working (Dell XPS13) Bluetooth (Atheros AR3012) not working on Ubuntu 16.04 Bluetooth not working on Ubuntu 16.04 LTS Bluetooth cannot find any devices Stuck on a bluetooth problem The service seems to be running /home >sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago Docs: man:bluetoothd(8) Main PID: 790 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─790 /usr/lib/bluetooth/bluetoothd Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. and not blocked /home >rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no I have edited /etc/bluetooth/main.conf to include AutoEnable=true but I noted that the entire file was commented out. The kernel seems reasonably up to date >uname -a Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I wonder if I need a device driver, but I have no idea how to find out. The following diagnostics may help some of you knowledgeable people find out. >hcitool dev Devices: hci024:0A:64:F5:EE:86 and the output of dmsg is >dmesg | grep Blue [2.030855] usb 1-1.4: Product: Bluetooth Radio [ 13.806355] Bluetooth: Core ver 2.22 [ 13.806369] Bluetooth: HCI device and connection manager initialized [ 13.806372] Bluetooth: HCI socket layer initialized [ 13.806373] Bluetooth: L2CAP socket layer initialized [ 13.806377] Bluetooth: SCO socket layer initialized [ 13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a lmp_ver=06 lmp_subver=8821 [ 13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin [ 13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin [ 13.877382] Bluetooth: hci0: rom_version status=0 version=1 [ 13.877387] Bluetooth: cfg_sz 0, total size 17428 [ 16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 16.550281] Bluetooth: BNEP filters: protocol multicast [ 16.550284] Bluetooth: BNEP socket layer initialized [ 27.868345] Bluetooth: RFCOMM TTY layer initialized [ 27.868350] Bluetooth: RFCOMM socket layer initialized [ 27.868354] Bluetooth: RFCOMM ver 1.11 and of lsusb is >lsusb Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 13d3:3414 IMC Networks Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Thanking you in anticipation To manage notifications about this bug go to: https://bugs.launchpad.net/ub
[Touch-packages] [Bug 1745866] Re: Audio does not auto-switch to HDMI after switching the connected HDMI TV on
Yes the command should eventually print an https:// URL which you can copy into a web browser on a different machine. -- 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/1745866 Title: Audio does not auto-switch to HDMI after switching the connected HDMI TV on Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I start the computer is the connected TV (HDMI) is off and the pulseaudio device stays on unplugged when I switch the TV on. If I switch the TV on before I start the computer, everything works fine. alsa_output.pci-_01_00.1.hdmi-stereo linux-image-14.0-15-generic nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic Regards, Norbert To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1745866/+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 1529356] Re: Bluetooth does not discover any device
*** This bug is a duplicate of bug 1542743 *** https://bugs.launchpad.net/bugs/1542743 ** This bug has been marked a duplicate of bug 1542743 Bluetooth (Atheros AR3012): Patch file not found ar3k/AthrBT_0x0200.dfu -- 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/1529356 Title: Bluetooth does not discover any device Status in bluez package in Ubuntu: New Bug description: It looks like https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1427680 but for an Asus ROG G551JW I'm on ubuntu 14.04 uname -a 3.19.0-25-generic #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux lsusb Bus 004 Device 002: ID 8087:8000 Intel Corp. Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 8087:8008 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b3fd Chicony Electronics Co., Ltd Bus 001 Device 004: ID 13d3:3474 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Seeing 13d3:3474 IMC Networks and searching in a search engine it seems to be an issue about AR3012 driver : I tried to update it using following ppa which should be providing the driver : sudo add-apt-repository ppa:hanipouspilot/rtlwifi sudo apt-get update sudo apt-get install linux-firmware ls /lib/firmware/ar3k/ 1020201coex ramps_0x01020200_40_0x03.dfu AthrBT_0x01020001.dfu ramps_0x01020200_40_0x04.dfu AthrBT_0x01020200.dfu ramps_0x01020200_40.dfu AthrBT_0x01020201.dfu ramps_0x01020201_26_0x01.dfu AthrBT_0x1102_ac01.dfuramps_0x01020201_26.dfu AthrBT_0x1102.dfu ramps_0x01020201_40_0x01.dfu AthrBT_0x11020100.dfu ramps_0x01020201_40_0x02.dfu AthrBT_0x3101.dfu ramps_0x01020201_40_0x03.dfu AthrBT_0x31010100.dfu ramps_0x01020201_40_0x04.dfu AthrBT_0x4102.dfu ramps_0x01020201_40.dfu ramps_0x01020001_26.dfu ramps_0x1102_40.dfu ramps_0x01020200_26_0x01.dfu ramps_0x11020100_40.dfu ramps_0x01020200_26.dfu ramps_0x3101_40.dfu ramps_0x01020200_40_0x01.dfu ramps_0x31010100_40.dfu ramps_0x01020200_40_0x02.dfu ramps_0x4102_40.dfu But it still doesn't work :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth 4.101-0ubuntu13.1 ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: LXDE Date: Sat Dec 26 09:05:33 2015 InstallationDate: Installed on 2015-11-14 (41 days ago) InstallationMedia: Lubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. G551JW PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=5dd37748-b279-4351-861a-c7a3dfcc947e ro noprompt quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G551JW.202 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G551JW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG551JW.202:bd01/16/2015:svnASUSTeKCOMPUTERINC.:pnG551JW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG551JW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G551JW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: DC:85:DE:F7:D2:8A ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:666 acl:0 sco:0 events:46 errors:0 TX bytes:1028 acl:0 sco:0 commands:46 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1529356/+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 1745828] Re: Ubuntu 16.04 can't find any Bluetooth devices
This sounds like it could be a firmware (missing) issue. Please attach full output from 'dmesg', and also run this command to attach more information automatically: apport-collect 1745828 ** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1745828 Title: Ubuntu 16.04 can't find any Bluetooth devices Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: It is ON and VISIBLE in the control panel. My iPhone can see two other devices but it can't see the computer, and the computer can't see anything, even if left searching for tens of minutes. The previous answers listed below suggest the following diagnostics Bluetooth not working after update How can I make my bluetooth works on Ubuntu 16.04? Ubuntu 16.04 bluetooth not working (Dell XPS13) Bluetooth (Atheros AR3012) not working on Ubuntu 16.04 Bluetooth not working on Ubuntu 16.04 LTS Bluetooth cannot find any devices Stuck on a bluetooth problem The service seems to be running /home >sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago Docs: man:bluetoothd(8) Main PID: 790 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─790 /usr/lib/bluetooth/bluetoothd Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. and not blocked /home >rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no I have edited /etc/bluetooth/main.conf to include AutoEnable=true but I noted that the entire file was commented out. The kernel seems reasonably up to date >uname -a Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I wonder if I need a device driver, but I have no idea how to find out. The following diagnostics may help some of you knowledgeable people find out. >hcitool dev Devices: hci024:0A:64:F5:EE:86 and the output of dmsg is >dmesg | grep Blue [2.030855] usb 1-1.4: Product: Bluetooth Radio [ 13.806355] Bluetooth: Core ver 2.22 [ 13.806369] Bluetooth: HCI device and connection manager initialized [ 13.806372] Bluetooth: HCI socket layer initialized [ 13.806373] Bluetooth: L2CAP socket layer initialized [ 13.806377] Bluetooth: SCO socket layer initialized [ 13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a lmp_ver=06 lmp_subver=8821 [ 13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin [ 13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin [ 13.877382] Bluetooth: hci0: rom_version status=0 version=1 [ 13.877387] Bluetooth: cfg_sz 0, total size 17428 [ 16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 16.550281] Bluetooth: BNEP filters: protocol multicast [ 16.550284] Bluetooth: BNEP socket layer initialized [ 27.868345] Bluetooth: RFCOMM TTY layer initialized [ 27.868350] Bluetooth: RFCOMM socket layer initialized [ 27.868354] Bluetooth: RFCOMM ver 1.11 and of lsusb is >lsusb Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 13d3:3414 IMC Networks Bus 001 Device
[Touch-packages] [Bug 1743803] Re: Nautilus text overlapping with translucent background
** Summary changed: - Nautilus text overlapping + Nautilus text overlapping with translucent background -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1743803 Title: Nautilus text overlapping with translucent background Status in Ubuntu theme: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: On the screenshot attached, calculator has focus, we see text overlapping in Nautilus 3.26.0. Using default theme on Ubuntu 17.10 This bug was originally reported in https://gitlab.gnome.org/GNOME/nautilus/issues/211, but we assume it's Ubuntu theme fault. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1743803/+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 1740441] Re: Tag borders in search bar looks halfway
** Changed in: ubuntu-themes Status: Incomplete => New ** Changed in: ubuntu-themes (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1740441 Title: Tag borders in search bar looks halfway Status in Ubuntu theme: New Status in ubuntu-themes package in Ubuntu: New Bug description: ubuntu 17.10 Nautilus search bar SS: https://i.hizliresim.com/rJWBP7.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1740441/+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 1746141] [NEW] Input level keeps changing even when there's no Mic attached
Public bug reported: Summary: On a device without build-in microphone, plug-unplug headset, on gnome-control-center sound setting input tab, input level keeps going up and down even without mic/headset attached. Steps to reproduce: 1. Fresh install Ubuntu 17.10.1 image 2. Boot up the device 3. Plug a headset(with mic) in the GHS jack 4. Open Sound settings(gnome-control-center) 5. Switch to "Input" tab, adjust the input volume amplifier to 100%, and then notice that input level will start to float 6. Leave sound setting UI as open, unplug the headset => Problem: input volume amplifier is still editable and input level keeps floating. Expected behavior: Ideally, when headset is unplugged, the input volume amplifier should become in-editable and input level shouldn't keep floating. Actual behavior: Input level keeps moving. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed ** Description changed: Summary: - On a device without build-in microphone, plugin-unplug headset, on gnome-control-center sound setting input tab, input level keeps going up and down even without mic/headset attached. + On a device without build-in microphone, plug-unplug headset, on gnome-control-center sound setting input tab, input level keeps going up and down even without mic/headset attached. Steps to reproduce: 1. Fresh install Ubuntu 17.10.1 image 2. Boot up the device 3. Plug a headset(with mic) in the GHS jack 4. Open Sound settings(gnome-control-center) 5. Switch to "Input" tab, adjust the input volume amplifier to 100%, and then notice that input level will start to float 6. Leave sound setting UI as open, unplug the headset => Problem: input volume amplifier is still editable and input level keeps floating. Expected behavior: Ideally, when headset is unplugged, the input volume amplifier should become in-editable and input level shouldn't keep floating. Actual behavior: Input level keeps moving. -- 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/1746141 Title: Input level keeps changing even when there's no Mic attached Status in alsa-driver package in Ubuntu: Confirmed Bug description: Summary: On a device without build-in microphone, plug-unplug headset, on gnome-control-center sound setting input tab, input level keeps going up and down even without mic/headset attached. Steps to reproduce: 1. Fresh install Ubuntu 17.10.1 image 2. Boot up the device 3. Plug a headset(with mic) in the GHS jack 4. Open Sound settings(gnome-control-center) 5. Switch to "Input" tab, adjust the input volume amplifier to 100%, and then notice that input level will start to float 6. Leave sound setting UI as open, unplug the headset => Problem: input volume amplifier is still editable and input level keeps floating. Expected behavior: Ideally, when headset is unplugged, the input volume amplifier should become in-editable and input level shouldn't keep floating. Actual behavior: Input level keeps moving. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1746141/+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 1719302] Re: Please include mlx4 and mlx5 InfiniBand modules
This bug was fixed in the package initramfs-tools - 0.130ubuntu2 --- initramfs-tools (0.130ubuntu2) bionic; urgency=medium * Include mlx4 and mlx5 InfiniBand modules (Closes: #871595, LP: #1719302) -- Benjamin Drung Sat, 27 Jan 2018 12:51:45 +0100 ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Fix Released -- 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/1719302 Title: Please include mlx4 and mlx5 InfiniBand modules Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools package in Debian: New Bug description: Mellanox ConnectX architecture is: mlx4_core is the lower level PCI driver which register on the PCI id, and protocol specific drivers are depended on it: mlx4_en - for Ethernet and mlx4_ib for Infiniband. NIC could have multiple ports which can change their type dynamically. We use the request_module() call to load the relevant protocol driver when needed: on loading time or at port type change event. The mlx4_core and mlx5_core modules are included in the initrd, but not mlx4_ib and mlx5_ib. Thus the request_module() call will not find these modules and fail load them. The mlx*_ib module loading will not be retried. Therefore also include mlx4_ib and mlx5_ib in the initrd to make autoloading them work. A patch is attached to the related Debian bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1719302/+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 1569653] Re: NetworkManager plugin for 'team' unavailable
Hi Sebastien, can you clarify your last response? Is there a solution
for this in 16.04?
--
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/1569653
Title:
NetworkManager plugin for 'team' unavailable
Status in network-manager package in Ubuntu:
Triaged
Bug description:
Versions:
OS: 16.04 amd64 daily build
nmcli 1.0.4
network-manager: 1.0.4-0ubuntu
Symptom:
while creating a team connection with nmcli/nmtui, actions can be done but
failed while activating team connection because no 'team' plugin avaulable.
Reproduce the issue:
$ nmcli c a type team ifname team0 con-name team0 config
'{"runner":{"name":"lacp"}}'
$ for dev in eno1 eno2 eno3 eno4; do
nmcli c a type team-slave ifname $dev con-name teamport-$dev master
team0
done
$ nmcli c up team0
Error: Connection activation failed: NetworkManager plugin for 'team'
unavailable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1569653/+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 1746128] [NEW] package libdbusmenu-qt5-2 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', which is also in pac
Public bug reported: i don't know to be specific ProblemType: Package DistroRelease: Kali 2018.1 Package: libdbusmenu-qt5-2 (not installed) ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Mon Jan 29 21:00:43 2018 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', which is also in package libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1 InstallationDate: Installed on 2018-01-26 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.19.0.5kali1 apt 1.6~alpha7 SourcePackage: libdbusmenu-qt Title: package libdbusmenu-qt5-2 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', which is also in package libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libdbusmenu-qt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package kali-rolling -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdbusmenu-qt in Ubuntu. https://bugs.launchpad.net/bugs/1746128 Title: package libdbusmenu-qt5-2 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libdbusmenu- qt5.so.2.6.0', which is also in package libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1 Status in libdbusmenu-qt package in Ubuntu: New Bug description: i don't know to be specific ProblemType: Package DistroRelease: Kali 2018.1 Package: libdbusmenu-qt5-2 (not installed) ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Mon Jan 29 21:00:43 2018 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', which is also in package libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1 InstallationDate: Installed on 2018-01-26 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.19.0.5kali1 apt 1.6~alpha7 SourcePackage: libdbusmenu-qt Title: package libdbusmenu-qt5-2 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2.6.0', which is also in package libdbusmenu-qt5:amd64 0.9.3+16.04.20160218-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdbusmenu-qt/+bug/1746128/+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 1729194] Re: /etc/resolv.conf pointing to dnsmasq instead of resolved
Here's the configuration :
```
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=false
[device]
wifi.scan-rand-mac-address=no
```
There's not anything about dnsmasq there is an empty directory
/etc/NetworkManager/dnsmasq.d with nothing configured in it though.
--
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/1729194
Title:
/etc/resolv.conf pointing to dnsmasq instead of resolved
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
Systemd sometimes just doesn't resolve DNS queries and for the life of
me I don't know why.
So often when I'm switching between wifi networks I find that systemd-
resolved in 17.10 complete fails to do it's job. Here's the example.
I'm connected to the internet :
```
chalbersma@nebraska [~] {Tue Oct 31 20:58:18}
> ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=53 time=196 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=53 time=67.5 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=53 time=78.9 ms
^C
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 67.534/114.169/196.025/58.068 ms
```
But I can't seem to resolve domains:
```
chalbersma@nebraska [~] {Tue Oct 31 20:59:17}
> nslookup google.com
;; connection timed out; no servers could be reached
```
So I did a `systemd-resolver --status` to see if it's getting the
right dns server. It is :
```
Link 3 (wlp2s0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 192.168.43.1
2001:4888:51:ff00:506:d::
2001:4888:50:ff00:500:d::
```
And it's actually up and working properly :
```
chalbersma@nebraska [~] {Tue Oct 31 21:02:06}
> nslookup google.com 192.168.43.1
Server: 192.168.43.1
Address:192.168.43.1#53
Non-authoritative answer:
Name: google.com
Address: 172.217.11.78
chalbersma@nebraska [~] {Tue Oct 31 21:03:16}
> nslookup google.com 2001:4888:51:ff00:506:d::
Server: 2001:4888:51:ff00:506:d::
Address:2001:4888:51:ff00:506:d::#53
Non-authoritative answer:
Name: google.com
Address: 172.217.11.78
```
Systemd just can't figure out to make the request. I did try the
common step of flushing the cache (with `--flush-cache`) restarting
network-manager and systemd-resolverd service but nothing seems to be
able to make systemd-resolverd function. Even a reboot doesn't always
fix the issue; sometimes it persists.
For debugging this is what's in my /etc/resolv.conf :
```
chalbersma@nebraska [~] {Tue Oct 31 21:09:15}
> cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 127.0.1.1
```
As soon as I manually set the nameserver from my loopback to the
actual dns server (bypassing systemd-resolvd) things start working
again. Let me know what kind of tshooting data I'd need to grab to
help display this issue.
In order to restore networking I had to manually edit that file and
change my dns to the external source.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1729194/+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 1746124] [NEW] /usr/bin/vim.basic:11:visit_decref:dict_traverse:subtract_refs:collect:collect_with_callback
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding vim. This problem was most recently seen with package version 2:7.4.1829-1ubuntu2.1, the problem page at https://errors.ubuntu.com/problem/c77fea5e091c93d6805e8e67c962a9a6edb320e5 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: vim (Ubuntu) Importance: Undecided Status: New ** Tags: xenial yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1746124 Title: /usr/bin/vim.basic:11:visit_decref:dict_traverse:subtract_refs:collect:collect_with_callback Status in vim package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding vim. This problem was most recently seen with package version 2:7.4.1829-1ubuntu2.1, the problem page at https://errors.ubuntu.com/problem/c77fea5e091c93d6805e8e67c962a9a6edb320e5 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1746124/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work
Hr ... curious. You can revert my code by reversing the action and reinstalling the -synaptics driver. Might be time for a clean-install? -- 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/1686081 Title: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work Status in Release Notes for Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Status in xubuntu-meta package in Ubuntu: Fix Released Status in xorg source package in Artful: Confirmed Status in xubuntu-meta source package in Artful: Fix Released Bug description: I'm splitting this issue off from LP: #1685542 (which made xserver- xorg-input-all no longer recommend xserver-xorg-input-synaptics) for tracking the remaining issues. gnome-control-center only supports libinput. If xserver-xorg-input- synaptics is installed (because it's used by some desktops which haven't been ported to libinput yet), synaptics overrides libinput. That makes gnome-control-center's Mouse & Touchpad settings panel only show basic settings and important configurations don't work. Questions - 1. Which desktops/apps still need -synaptics? - Unity - Xfce? - LXDE? LXQt? All the other major desktops have already been ported (LP: #1417980) 2. Can these apps be ported or removed before 18.04 LTS is released? 3. Can the desktops be ported and how bad is it if they are not ported and -synaptics is no longer available? 4. If -synaptics can't be removed completely from 18.04 LTS, does it make sense to have gnome-control-center Conflicts: xserver-xorg-input- synaptics? 5. Is there any other way we can fix this conflict? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1729879] Re: apport-collect is still requesting python-apport installation
** Branch linked: lp:~ubuntu-core-dev/ubuntu/bionic/apport/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1729879 Title: apport-collect is still requesting python-apport installation Status in apport package in Ubuntu: In Progress Status in apport source package in Bionic: In Progress Bug description: apport-collect should now run via python3-apport package, as python2.7 is now gone on bionic. But that fail and show: apport-collect 1729877 You need to run 'sudo apt-get install python-apport' for apport-collect to work. this is not expected now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: python3-apport 2.20.7-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportLog: ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 3 16:12:40 2017 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1729879/+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 1729879] Re: apport-collect is still requesting python-apport installation
** Changed in: apport (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: apport (Ubuntu Bionic) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1729879 Title: apport-collect is still requesting python-apport installation Status in apport package in Ubuntu: In Progress Status in apport source package in Bionic: In Progress Bug description: apport-collect should now run via python3-apport package, as python2.7 is now gone on bionic. But that fail and show: apport-collect 1729877 You need to run 'sudo apt-get install python-apport' for apport-collect to work. this is not expected now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: python3-apport 2.20.7-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportLog: ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 3 16:12:40 2017 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1729879/+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 1744260] Re: /etc/xdg/QtProject/qtlogging.ini disables qDebug() logging of all Qt 5 libraries installed on the system
We will remove the file rather than moving it to another location. See https://bugs.debian.org/886437. ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Fix Committed ** Bug watch added: Debian Bug tracker #886437 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886437 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1744260 Title: /etc/xdg/QtProject/qtlogging.ini disables qDebug() logging of all Qt 5 libraries installed on the system Status in qtbase-opensource-src package in Ubuntu: Fix Committed Bug description: The file globally disables all qDebug() for any Qt 5 installation on the system. Instead, as in other distros (Fedora), it should go to: QT_INSTALL_DATA , instead of /etc/xdg/QtProject: qmake -qt=qt5 -query QT_INSTALL_DATA /usr/share/qt5 Reference: https://bugreports.qt.io/browse/QTBUG-65841 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libqt5core5a 5.9.1+dfsg-10ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jan 19 10:36:59 2018 InstallationDate: Installed on 2018-01-10 (9 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) SourcePackage: qtbase-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.QtProject.qtlogging.ini: # [Rules] # *.debug=false mtime.conffile..etc.xdg.QtProject.qtlogging.ini: 2018-01-19T09:02:20.779862 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1744260/+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 1729879] Re: apport-collect is still requesting python-apport installation
** Also affects: apport (Ubuntu Bionic) Importance: Medium Status: Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1729879 Title: apport-collect is still requesting python-apport installation Status in apport package in Ubuntu: Triaged Status in apport source package in Bionic: Triaged Bug description: apport-collect should now run via python3-apport package, as python2.7 is now gone on bionic. But that fail and show: apport-collect 1729877 You need to run 'sudo apt-get install python-apport' for apport-collect to work. this is not expected now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: python3-apport 2.20.7-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportLog: ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 3 16:12:40 2017 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1729879/+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 1731646] Re: missing qDebug output when creating QT applications
The qt.conf file will be removed in Ubuntu 18.04, see https://bugs.debian.org/886437. Already fixed in bionic-proposed. ** Bug watch added: Debian Bug tracker #886437 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886437 ** Changed in: qtbase-opensource-src (Ubuntu) Status: Invalid => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1731646 Title: missing qDebug output when creating QT applications Status in qtbase-opensource-src package in Ubuntu: Fix Committed Bug description: This bug seems to be connected to: https://bugzilla.redhat.com/show_bug.cgi?id=1227295 in the above link I have found a workaround for the problem. I have created an empty file in: ~/.config/QtProject called qtlogging.ini and the problem is resolved. the problem was not present in ubuntu 17.04 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libqt5core5a 5.9.1+dfsg-10ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: KDE Date: Sat Nov 11 16:59:49 2017 InstallationDate: Installed on 2016-11-09 (366 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) SourcePackage: qtbase-opensource-src UpgradeStatus: Upgraded to artful on 2017-10-30 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1731646/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work
Hi Chris, thanks for taking time to look into this. I tried your code, but no, the system touchpad hotkey (FN+F3) is still not working. There are still no touchpad settings available. And my workaround-script doesn't work anymore either. ;-) -- 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/1686081 Title: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work Status in Release Notes for Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Status in xubuntu-meta package in Ubuntu: Fix Released Status in xorg source package in Artful: Confirmed Status in xubuntu-meta source package in Artful: Fix Released Bug description: I'm splitting this issue off from LP: #1685542 (which made xserver- xorg-input-all no longer recommend xserver-xorg-input-synaptics) for tracking the remaining issues. gnome-control-center only supports libinput. If xserver-xorg-input- synaptics is installed (because it's used by some desktops which haven't been ported to libinput yet), synaptics overrides libinput. That makes gnome-control-center's Mouse & Touchpad settings panel only show basic settings and important configurations don't work. Questions - 1. Which desktops/apps still need -synaptics? - Unity - Xfce? - LXDE? LXQt? All the other major desktops have already been ported (LP: #1417980) 2. Can these apps be ported or removed before 18.04 LTS is released? 3. Can the desktops be ported and how bad is it if they are not ported and -synaptics is no longer available? 4. If -synaptics can't be removed completely from 18.04 LTS, does it make sense to have gnome-control-center Conflicts: xserver-xorg-input- synaptics? 5. Is there any other way we can fix this conflict? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1729879] Re: apport-collect is still requesting python-apport installation
string-fix in apport-bug. ** Changed in: apport (Ubuntu) Importance: Undecided => Medium ** Changed in: apport (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1729879 Title: apport-collect is still requesting python-apport installation Status in apport package in Ubuntu: Triaged Bug description: apport-collect should now run via python3-apport package, as python2.7 is now gone on bionic. But that fail and show: apport-collect 1729877 You need to run 'sudo apt-get install python-apport' for apport-collect to work. this is not expected now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: python3-apport 2.20.7-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportLog: ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 3 16:12:40 2017 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1729879/+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 1745984] Re: package update-notifier 3.168.7 failed to install/upgrade: problemas de dependencias - se deja sin configurar
The error in your log is: Configurando update-notifier-common (3.168.7) ... Fichero de configuración `/etc/apt/apt.conf.d/10periodic' ==> Fichero en el sistema creado por usted o por algún script. ==> Fichero también en el paquete. ¿Qué quisiera hacer al respecto? Sus opciones son: Y o I : instalar la versión del desarrollador del paquete N o O : conservar la versión que tiene instalada actualmente D: mostrar las diferencias entre versiones Z: ejecutar un intérprete de órdenes para examinar la situación La acción por omisión es conservar la versión actual. *** 10periodic (Y/I/N/O/D/Z) [por omisión=N] ? dpkg: error al procesar el paquete update-notifier-common (--configure): end of file on stdin at conffile prompt This shows that you have modified a conffile on your system belonging to this package, which means the package manager would have prompted you to know what action to take with the conffile. However, because this was part of an unattended upgrade, there was no possibility for you to provide input, and the installation failed instead. I'm not sure that this is the wrong behavior in such a case; doing anything other than aborting the upgrade would mean taking action without the user's input. In any case, if we are to do anything different, it must be handled in the unattended-upgrades package, so reassigning. ** Package changed: update-notifier (Ubuntu) => unattended-upgrades (Ubuntu) ** Changed in: unattended-upgrades (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1745984 Title: package update-notifier 3.168.7 failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in unattended-upgrades package in Ubuntu: Triaged Bug description: ProblemType: Package DistroRelease: Ubuntu 16.04 Package: update-notifier 3.168.7 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Jan 29 09:32:30 2018 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2016-11-13 (442 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: update-notifier Title: package update-notifier 3.168.7 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.update-notifier.desktop: 2016-06-29T18:23:45 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1745984/+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 1745984] [NEW] package update-notifier 3.168.7 failed to install/upgrade: problemas de dependencias - se deja sin configurar
You have been subscribed to a public bug: ProblemType: Package DistroRelease: Ubuntu 16.04 Package: update-notifier 3.168.7 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Jan 29 09:32:30 2018 ErrorMessage: problemas de dependencias - se deja sin configurar InstallationDate: Installed on 2016-11-13 (442 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: update-notifier Title: package update-notifier 3.168.7 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.update-notifier.desktop: 2016-06-29T18:23:45 ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: Triaged ** Tags: amd64 apport-package third-party-packages xenial -- package update-notifier 3.168.7 failed to install/upgrade: problemas de dependencias - se deja sin configurar https://bugs.launchpad.net/bugs/1745984 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1745692] Re: Removable storage device not detected as block device on MacBookPro
** Summary changed: - Removable storage device not detected as block device + Removable storage device not detected as block device on MacBookPro -- 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/1745692 Title: Removable storage device not detected as block device on MacBookPro Status in systemd package in Ubuntu: New Bug description: Since updating to the 4.13.0 kernel line I have had bad behaviour from USB storage devices. After a reboot the first time I plug a flash drive in, Ubuntu mounts the drive normally. If I eject the drive and try to insert the drive again them Ubuntu does not automatically mount it, and I cannot mount it manually from the terminal. If I boot onto a kernel from the 4.10.0 line then the system behaves as expected. I have installed the latest mainline kernel which is 4.14.15 and have observed the same issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu21 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity CustomUdevRuleFiles: 61_smfpautoconf_samsung.rules 99-libsane-samsungmfp.rules 70-snap.keepassxc.rules 99-SaleaeLogic.rules 71-ti-permissions.rules 70-snap.core.rules 60_smfpautoconf_samsung.rules 70-mm-no-ti-emulators.rules 61-msp430uif.rules Date: Fri Jan 26 22:30:05 2018 EcryptfsInUse: Yes GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HotplugNewDevices: /dev/sdb /dev/sdb1 HotplugNewMounts: InstallationDate: Installed on 2017-09-04 (144 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 008: ID 058f:9380 Alcor Micro Corp. Flash Drive Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: \\boot\vmlinuz-4.13.0-32-generic.efi.signed ro root=UUID=dee8db21-42fc-46f8-8b7f-b3b1d1984cfe initrd=boot\initrd.img-4.13.0-32-generic SourcePackage: systemd Symptom: storage Title: Removable storage device not detected as block device UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 22:30:09.917: The udisks-daemon is running (name-owner :1.99). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1745692/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work
@k-one, do the following: $ sudo apt-get update && sudo apt-get --auto-remove purge xserver-xorg- input-synaptics && sudo apt-get install xserver-xorg-input-libinput $ reboot Fixed? -- 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/1686081 Title: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work Status in Release Notes for Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Status in xubuntu-meta package in Ubuntu: Fix Released Status in xorg source package in Artful: Confirmed Status in xubuntu-meta source package in Artful: Fix Released Bug description: I'm splitting this issue off from LP: #1685542 (which made xserver- xorg-input-all no longer recommend xserver-xorg-input-synaptics) for tracking the remaining issues. gnome-control-center only supports libinput. If xserver-xorg-input- synaptics is installed (because it's used by some desktops which haven't been ported to libinput yet), synaptics overrides libinput. That makes gnome-control-center's Mouse & Touchpad settings panel only show basic settings and important configurations don't work. Questions - 1. Which desktops/apps still need -synaptics? - Unity - Xfce? - LXDE? LXQt? All the other major desktops have already been ported (LP: #1417980) 2. Can these apps be ported or removed before 18.04 LTS is released? 3. Can the desktops be ported and how bad is it if they are not ported and -synaptics is no longer available? 4. If -synaptics can't be removed completely from 18.04 LTS, does it make sense to have gnome-control-center Conflicts: xserver-xorg-input- synaptics? 5. Is there any other way we can fix this conflict? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work
Hi, I just upgraded from 17.04 to 17.10. I m running my ubuntu in Xorg mode. After the upgrade (Dell Laptop with an Alps touchpad) there are no touchpad settings available at all (see attached screenshot). The touchpad would work though, but I could not disable it at all. Pressing the Function-key+F3 would show the on-screen symbol of the disabled touchpad, but it wouldn't disable the touchpad. At the moment I am using a bash script that is utilizing "xinput --disable $device" to enable/disable the touchpad. ** Attachment added: "Screenshot of mouse/touchpad settings page" https://bugs.launchpad.net/ubuntu/artful/+source/xorg/+bug/1686081/+attachment/5045199/+files/Screenshot_no_touchpad_settings.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1686081 Title: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work Status in Release Notes for Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Status in xubuntu-meta package in Ubuntu: Fix Released Status in xorg source package in Artful: Confirmed Status in xubuntu-meta source package in Artful: Fix Released Bug description: I'm splitting this issue off from LP: #1685542 (which made xserver- xorg-input-all no longer recommend xserver-xorg-input-synaptics) for tracking the remaining issues. gnome-control-center only supports libinput. If xserver-xorg-input- synaptics is installed (because it's used by some desktops which haven't been ported to libinput yet), synaptics overrides libinput. That makes gnome-control-center's Mouse & Touchpad settings panel only show basic settings and important configurations don't work. Questions - 1. Which desktops/apps still need -synaptics? - Unity - Xfce? - LXDE? LXQt? All the other major desktops have already been ported (LP: #1417980) 2. Can these apps be ported or removed before 18.04 LTS is released? 3. Can the desktops be ported and how bad is it if they are not ported and -synaptics is no longer available? 4. If -synaptics can't be removed completely from 18.04 LTS, does it make sense to have gnome-control-center Conflicts: xserver-xorg-input- synaptics? 5. Is there any other way we can fix this conflict? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1746015] Re: Apt and apt-get do not ship a en_US language catalog
** Summary changed: - Apt and apt-get do not ship a us_EN language catalog + Apt and apt-get do not ship a en_US language catalog -- 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/1746015 Title: Apt and apt-get do not ship a en_US language catalog Status in apt package in Ubuntu: Invalid Bug description: Description:Ubuntu 17.10 Release:17.10 If you install anthy with additional languages, with "US English" as your primary language, you end up with a "locale" output similar to the following: $ locale LANG=en_US.UTF-8 LANGUAGE=en_US:de:ja LC_CTYPE="en_US.UTF-8" LC_NUMERIC=en_GB.UTF-8 LC_TIME=en_GB.UTF-8 LC_COLLATE=C LC_MONETARY=en_US.UTF-8 LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= The LANGUAGE variable in this case is using the rules from https://www.gnu.org/software/gettext/manual/html_node/The-LANGUAGE- variable.html When running "aptitude" or "apt-get" or "apt install", the messages that come back are in German. If you strace those commands, you'll see apt trying to search for an en_US or en catalog, finding none, and falling down to the 2nd language in the list: "de" or German. If you run: $ LANGUAGE="" apt-get update Then the messages come back in English, because the system's fallen back to the "C" locale. apt should also properly ship an en_US language catalog. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apt 1.5.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Jan 29 08:31:38 2018 InstallationDate: Installed on 2017-04-27 (276 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: apt UpgradeStatus: Upgraded to artful on 2018-01-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1746015/+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 1745350] [NEW] whoopsie id is not unique
On Thu, Jan 25, 2018 at 10:52:53AM -, Jean-Baptiste Lallement wrote: > Public bug reported: > > The list of reports for a system actually includes reports for several > different systems: > > For example in this report: > https://errors.ubuntu.com/oops/374ff29e-fb53-11e7-83ad-fa163e192766 > the system has been installed on 2018-01-12 (user is mickymouse) > > when you open the list of reports for this system > https://errors.ubuntu.com/user/ca33fcf9202a7f0e2941820648d407f607ae410d3ef3ca17769a2ab321dc8315b82f3e155845ce915e5efca4b9da29b9ef506adc11149c0f7d11e577508c4590 > > there are several reports which pre-dates the installation. Selecting other > reports in the list show different systems. For example this report is from > another system: > https://errors.ubuntu.com/oops/a614887e-acad-11e7-b1f8-fa163e839e11 I'm not convinced that these are not in fact the same system. Unfortunately, the crashes are not complete apport reports and are missing information that would help distinguish them as different systems. However, as you mention whoopsie first tries to use /sys/class/dmi/id/product and if the system were reinstalled this would be the same. So its possible the owner of the system just reinstalled. Additionally, looking at the crash reports we can see the installation date is the same for one set of them and another set (the two oldest crash reports), so I'm pretty certain this is a reinstall. > whoopsie uses first tries to use /sys/class/dmi/id/product_uuid then > falls back to other things. > > It seems that /sys/class/dmi/id/product_uuid is sometimes a bogus value > e.g. > > 00020003-0004-0005-0006-000700080009 > > As seen in http://launchpad.net/bugs/1323081. I agree that this is a problem and I think its better tracked in bug 1636954. Although it is curious that the hashed system id for the bogus product_uuid doesn't have many recent crashes. So, I wonder how wide spread of a problem it is. -- Brian Murray -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1745350 Title: whoopsie id is not unique Status in whoopsie package in Ubuntu: Triaged Bug description: The list of reports for a system actually includes reports for several different systems: For example in this report: https://errors.ubuntu.com/oops/374ff29e-fb53-11e7-83ad-fa163e192766 the system has been installed on 2018-01-12 (user is mickymouse) when you open the list of reports for this system https://errors.ubuntu.com/user/ca33fcf9202a7f0e2941820648d407f607ae410d3ef3ca17769a2ab321dc8315b82f3e155845ce915e5efca4b9da29b9ef506adc11149c0f7d11e577508c4590 there are several reports which pre-dates the installation. Selecting other reports in the list show different systems. For example this report is from another system: https://errors.ubuntu.com/oops/a614887e-acad-11e7-b1f8-fa163e839e11 whoopsie uses first tries to use /sys/class/dmi/id/product_uuid then falls back to other things. It seems that /sys/class/dmi/id/product_uuid is sometimes a bogus value e.g. 00020003-0004-0005-0006-000700080009 As seen in http://launchpad.net/bugs/1323081. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: whoopsie 0.2.58 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CrashReports: 640:1000:114:1986326:2018-01-25 09:03:26.946560382 +0100:2018-01-25 09:03:27.946560382 +0100:/var/crash/_usr_bin_gnome-calculator.1000.crash CurrentDesktop: ubuntu:GNOME Date: Thu Jan 25 11:44:49 2018 InstallationDate: Installed on 2013-09-03 (1604 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1745350/+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 1746015] Re: Apt and apt-get do not ship a us_EN language catalog
C is not a language ** Attachment added: "c-not-a-language.png" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1746015/+attachment/5045192/+files/c-not-a-language.png -- 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/1746015 Title: Apt and apt-get do not ship a us_EN language catalog Status in apt package in Ubuntu: Invalid Bug description: Description:Ubuntu 17.10 Release:17.10 If you install anthy with additional languages, with "US English" as your primary language, you end up with a "locale" output similar to the following: $ locale LANG=en_US.UTF-8 LANGUAGE=en_US:de:ja LC_CTYPE="en_US.UTF-8" LC_NUMERIC=en_GB.UTF-8 LC_TIME=en_GB.UTF-8 LC_COLLATE=C LC_MONETARY=en_US.UTF-8 LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= The LANGUAGE variable in this case is using the rules from https://www.gnu.org/software/gettext/manual/html_node/The-LANGUAGE- variable.html When running "aptitude" or "apt-get" or "apt install", the messages that come back are in German. If you strace those commands, you'll see apt trying to search for an en_US or en catalog, finding none, and falling down to the 2nd language in the list: "de" or German. If you run: $ LANGUAGE="" apt-get update Then the messages come back in English, because the system's fallen back to the "C" locale. apt should also properly ship an en_US language catalog. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apt 1.5.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Jan 29 08:31:38 2018 InstallationDate: Installed on 2017-04-27 (276 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: apt UpgradeStatus: Upgraded to artful on 2018-01-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1746015/+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 1746015] Re: Apt and apt-get do not ship a us_EN language catalog
While that may be a precise and accurate statement, I believe it is the wrong answer. $ LANGUAGE=en_US:de:ja apt install vim E: Sperrdatei /var/lib/dpkg/lock konnte nicht geöffnet werden. - open (13: Permission denied) E: Sperren des Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, sind Sie root? $ LANGUAGE=invalid:de:ja apt install vim E: Sperrdatei /var/lib/dpkg/lock konnte nicht geöffnet werden. - open (13: Permission denied) E: Sperren des Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, sind Sie root? $ LANGUAGE="" apt install vim E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied) E: Unable to lock the administration directory (/var/lib/dpkg/), are you root? C is the *fallback* language, not the primary. Therefore, even though the user has requested English, and English is available in "C", the user is not receiving English. Besides: "C" isn't even a valid language (see screenshot). -- 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/1746015 Title: Apt and apt-get do not ship a us_EN language catalog Status in apt package in Ubuntu: Invalid Bug description: Description:Ubuntu 17.10 Release:17.10 If you install anthy with additional languages, with "US English" as your primary language, you end up with a "locale" output similar to the following: $ locale LANG=en_US.UTF-8 LANGUAGE=en_US:de:ja LC_CTYPE="en_US.UTF-8" LC_NUMERIC=en_GB.UTF-8 LC_TIME=en_GB.UTF-8 LC_COLLATE=C LC_MONETARY=en_US.UTF-8 LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= The LANGUAGE variable in this case is using the rules from https://www.gnu.org/software/gettext/manual/html_node/The-LANGUAGE- variable.html When running "aptitude" or "apt-get" or "apt install", the messages that come back are in German. If you strace those commands, you'll see apt trying to search for an en_US or en catalog, finding none, and falling down to the 2nd language in the list: "de" or German. If you run: $ LANGUAGE="" apt-get update Then the messages come back in English, because the system's fallen back to the "C" locale. apt should also properly ship an en_US language catalog. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apt 1.5.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Jan 29 08:31:38 2018 InstallationDate: Installed on 2017-04-27 (276 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: apt UpgradeStatus: Upgraded to artful on 2018-01-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1746015/+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 1738582] Re: [MIR] ibus-libpinyin and dependencies
@Ping-Wu: Right, the ibus-libpinyin package provides both an
"intelligent Pinyin" and a "Bopomofo" input method.
Yeah, suggested improvements is certainly another "thread". ;) This is
actually a bug report with a very specific adminstrative purpose. If you
want to discuss improvements, I think the proper way is to file an
upstream issue here:
https://github.com/libpinyin/ibus-libpinyin/issues
Anyway, Ubuntu 18.04 LTS will be shipped with ibus-libpinyin 1.9.2. I'm
not sure that would have happened without your input here, so thank you
very much for calling our attention to the usability differences
compared to the current version in Ubuntu 17.10. Much appreciated!
** Description changed:
Please include these packages in Ubuntu's component main:
* ibus-libpinyin
- * libpinyin (the ibus-libpinyin binary depends on libpinyin7)
+ * libpinyin (the ibus-libpinyin binary depends on libpinyin13)
As has been discussed at bug #1735362 we would like to replace ibus-
sunpinyin with ibus-libpinyin ("Intelligent Pinyin") in the live seed
and as the default input method for typing Simplified Chinese. Reasons
for the switch are:
- ibus-libpinyin is better maintained
- ibus-libpinyin is built with and depends on Python3
- (not yet in Debian: https://bugs.debian.org/883631)
- ibus-libpinyin is default input method in GNOME
Bugs ibus-libpinyin
---
https://github.com/libpinyin/ibus-libpinyin/issues
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=ibus-libpinyin
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin
Bugs libpinyin
--
https://github.com/libpinyin/libpinyin/issues
(no open Debian or Ubuntu bugs)
-
- I have read https://wiki.ubuntu.com/UbuntuMainInclusionRequirements, and
haven't found any issues that would prevent the proposed main inclusion.
+ I have read https://wiki.ubuntu.com/UbuntuMainInclusionRequirements, and
+ haven't found any issues that would prevent the proposed main inclusion.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libpinyin in Ubuntu.
https://bugs.launchpad.net/bugs/1738582
Title:
[MIR] ibus-libpinyin and dependencies
Status in ibus-libpinyin package in Ubuntu:
New
Status in libpinyin package in Ubuntu:
New
Bug description:
Please include these packages in Ubuntu's component main:
* ibus-libpinyin
* libpinyin (the ibus-libpinyin binary depends on libpinyin13)
As has been discussed at bug #1735362 we would like to replace ibus-
sunpinyin with ibus-libpinyin ("Intelligent Pinyin") in the live seed
and as the default input method for typing Simplified Chinese. Reasons
for the switch are:
- ibus-libpinyin is better maintained
- ibus-libpinyin is built with and depends on Python3
- ibus-libpinyin is default input method in GNOME
Bugs ibus-libpinyin
---
https://github.com/libpinyin/ibus-libpinyin/issues
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=ibus-libpinyin
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin
Bugs libpinyin
--
https://github.com/libpinyin/libpinyin/issues
(no open Debian or Ubuntu bugs)
I have read https://wiki.ubuntu.com/UbuntuMainInclusionRequirements,
and haven't found any issues that would prevent the proposed main
inclusion.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1738582/+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 1741189] Re: New bugfix release 17.2.8
Hello Timo, or anyone else affected,
Accepted mesa into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.8-0ubuntu0~17.10.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: mesa (Ubuntu Artful)
Status: New => Fix Committed
** Tags added: verification-needed verification-needed-artful
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
** Changed in: mesa (Ubuntu Xenial)
Status: New => Fix Committed
** Tags added: verification-needed-xenial
--
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/1741189
Title:
New bugfix release 17.2.8
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Xenial:
Fix Committed
Status in mesa source package in Artful:
Fix Committed
Bug description:
[Impact]
A new upstream bugfix release is available. Release note diff compared
to 17.2.4:
Mesa 17.2.5 is now available.
In this release we have:
In Mesa Core a GL error related to the ARB_ES3_1_compatibility spec
noticed with the GFXBench 5 Aztec Ruins has been corrected.
The GLSL compiler is not giving a linker error for mismatching uniform
precision with GLSL ES 1.00 any more. This enables, specially, several
Android applications which violate this rule, like Forge of Empires,
for example.
The SPIR-V compiler has corrected an assert triggered when support for
the simple memory model was claimed.
NIR has also received a correction related with
gl_SubGroupG{e,t}MaskARB.
The Intel drivers, specially i965, have received several fixes,
including a plug for a memory leak and another one in the compiler to
avoid GPU hangs on Broxton.
The gallium i915g driver for Intel has also seen an important
correction.
AMD drivers, mostly radv, have also received several fixes, including a
correction for a DCC corruption that was visible with Rust, breaking an
endless loop in r600, avoiding a GPU hang with vulkan dota2 in VR mode
and a plug for a memory leak.
Broadcom's vc4 has gotten a fix to compile out some non-debug code that
shouldn't be there for the release build.
Mesa 17.2.6 is now available.
In this release we have:
In Mesa Core we have included a correction to keep a program alive when
re-linking and prevent an use-after-free.
The GLSL compiler has received several fixes, including one to prevent
a SIGSEV when calling an undeclared subroutine in certain conditions
and another to mark the xfb buffers as active only if a variable uses
them.
The SPIR-V compiler has corrected a couple of issues involving the
usage of separate images and texture/samplers.
The Intel drivers include many new fixes, specially for i965. Several
are focused on improving SIMD32 and little-core. It also includes a fix
for a GPU hang which was detected while playing HW accelerated video
with mpv.
The AMD drivers have also received some care. radv has seen plugged 2
memory leaks while r600 has gotten a fix through reversing the tess
factor components for isolines.
The swr driver has corrected two performance regressions, one for the
avx512 platforms and the other for the avx/avx2 platforms.
In the ddebug gallium driver we have a fix for an use-after-free.
On the EGL side, the Wayland platform of the the DRI2 drivers has
received a fix to prevent crashing in ancient systems.
GLX has also received corrections to prevent a couple of errors when
creating and binding a context in DRI3 and DRISW, respectively.
From build and integration point of view, we have added some few more
fixes, including one to allow building libglvnd when EGL is present but
not GLX, another to enable building targets which don't need X11, such
as omx and va, when XCB is not present, and another one to be able to
specify the prefix installation for the OpenCL icd file.
Mesa 17.2.7 is now available.
In this release we have:
The current queue consists of a variety of fixes, with a sizeable hunk in the
shared GLSL code
[Touch-packages] [Bug 1741189] Please test proposed package
Hello Timo, or anyone else affected,
Accepted mesa into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.8-0ubuntu0~16.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
--
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/1741189
Title:
New bugfix release 17.2.8
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Xenial:
Fix Committed
Status in mesa source package in Artful:
Fix Committed
Bug description:
[Impact]
A new upstream bugfix release is available. Release note diff compared
to 17.2.4:
Mesa 17.2.5 is now available.
In this release we have:
In Mesa Core a GL error related to the ARB_ES3_1_compatibility spec
noticed with the GFXBench 5 Aztec Ruins has been corrected.
The GLSL compiler is not giving a linker error for mismatching uniform
precision with GLSL ES 1.00 any more. This enables, specially, several
Android applications which violate this rule, like Forge of Empires,
for example.
The SPIR-V compiler has corrected an assert triggered when support for
the simple memory model was claimed.
NIR has also received a correction related with
gl_SubGroupG{e,t}MaskARB.
The Intel drivers, specially i965, have received several fixes,
including a plug for a memory leak and another one in the compiler to
avoid GPU hangs on Broxton.
The gallium i915g driver for Intel has also seen an important
correction.
AMD drivers, mostly radv, have also received several fixes, including a
correction for a DCC corruption that was visible with Rust, breaking an
endless loop in r600, avoiding a GPU hang with vulkan dota2 in VR mode
and a plug for a memory leak.
Broadcom's vc4 has gotten a fix to compile out some non-debug code that
shouldn't be there for the release build.
Mesa 17.2.6 is now available.
In this release we have:
In Mesa Core we have included a correction to keep a program alive when
re-linking and prevent an use-after-free.
The GLSL compiler has received several fixes, including one to prevent
a SIGSEV when calling an undeclared subroutine in certain conditions
and another to mark the xfb buffers as active only if a variable uses
them.
The SPIR-V compiler has corrected a couple of issues involving the
usage of separate images and texture/samplers.
The Intel drivers include many new fixes, specially for i965. Several
are focused on improving SIMD32 and little-core. It also includes a fix
for a GPU hang which was detected while playing HW accelerated video
with mpv.
The AMD drivers have also received some care. radv has seen plugged 2
memory leaks while r600 has gotten a fix through reversing the tess
factor components for isolines.
The swr driver has corrected two performance regressions, one for the
avx512 platforms and the other for the avx/avx2 platforms.
In the ddebug gallium driver we have a fix for an use-after-free.
On the EGL side, the Wayland platform of the the DRI2 drivers has
received a fix to prevent crashing in ancient systems.
GLX has also received corrections to prevent a couple of errors when
creating and binding a context in DRI3 and DRISW, respectively.
From build and integration point of view, we have added some few more
fixes, including one to allow building libglvnd when EGL is present but
not GLX, another to enable building targets which don't need X11, such
as omx and va, when XCB is not present, and another one to be able to
specify the prefix installation for the OpenCL icd file.
Mesa 17.2.7 is now available.
In this release we have:
The current queue consists of a variety of fixes, with a sizeable hunk in the
shared GLSL codebase.
Whereas for individual drivers - i965 has a crash fix for when playing various
Valve games, r600 and nouveau have tweaks in their compiler backends. Fast
clears on radeonsi and RADV are better now, while the VAAPI encoding is
playing
nicely with GStreamer.
The WGL state tracker and SWR driver have
[Touch-packages] [Bug 1716203] Please test proposed package
Hello Timo, or anyone else affected, Accepted xserver-xorg-video-nouveau-hwe-16.04 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau- hwe-16.04/1:1.0.15-2~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** No longer affects: xserver-xorg-video-ati (Ubuntu) ** No longer affects: xserver-xorg-video-ati (Ubuntu Xenial) ** No longer affects: xserver-xorg-video-amdgpu (Ubuntu) ** No longer affects: xserver-xorg-video-amdgpu (Ubuntu Xenial) ** Changed in: xserver-xorg-video-ati-hwe-16.04 (Ubuntu) Status: New => Invalid ** Changed in: xserver-xorg-video-nouveau-hwe-16.04 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1716203 Title: Backport packages for 16.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-5.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in vulkan package in Ubuntu: Invalid Status in wayland-protocols package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Released Status in libdrm source package in Xenial: Fix Released Status in llvm-toolchain-5.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Released Status in vulkan source package in Xenial: Fix Committed Status in wayland-protocols source package in Xenial: Fix Released Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: Fix Released Status in xserver-xorg-video-amdgpu-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-ati-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-nouveau-hwe-16.04 source package in Xenial: Fix Committed Bug description: [Impact] *** hwe-16.04 refresh for 16.04.4 *** A minor update, only some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.76 to 2.4.83 - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests - intel: new pci-ids - drm: leak fixes, manpage updates - exynos, etnaviv, freedreno, android: fixes, new stuff wayland-protocols: None, just adds a few protocol definitions (xml files) llvm-toolchain-5.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-5 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for the bugfix release (xenial & artful) is bug 1727390 [Other information] build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 1716203] Re: Backport packages for 16.04.4 HWE stack
Hello Timo, or anyone else affected, Accepted xserver-xorg-video-ati-hwe-16.04 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-ati- hwe-16.04/1:7.10.0-1~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: xserver-xorg-video-ati-hwe-16.04 (Ubuntu) Importance: Undecided Status: New ** Changed in: xserver-xorg-video-ati-hwe-16.04 (Ubuntu Xenial) Status: New => Fix Committed ** Also affects: xserver-xorg-video-nouveau-hwe-16.04 (Ubuntu) Importance: Undecided Status: New ** Changed in: xserver-xorg-video-nouveau-hwe-16.04 (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1716203 Title: Backport packages for 16.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-5.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in vulkan package in Ubuntu: Invalid Status in wayland-protocols package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Released Status in libdrm source package in Xenial: Fix Released Status in llvm-toolchain-5.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Released Status in vulkan source package in Xenial: Fix Committed Status in wayland-protocols source package in Xenial: Fix Released Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: Fix Released Status in xserver-xorg-video-amdgpu-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-ati-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-nouveau-hwe-16.04 source package in Xenial: Fix Committed Bug description: [Impact] *** hwe-16.04 refresh for 16.04.4 *** A minor update, only some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.76 to 2.4.83 - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests - intel: new pci-ids - drm: leak fixes, manpage updates - exynos, etnaviv, freedreno, android: fixes, new stuff wayland-protocols: None, just adds a few protocol definitions (xml files) llvm-toolchain-5.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-5 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for the bugfix release (xenial & artful) is bug 1727390 [Other information] build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 1716203] Re: Backport packages for 16.04.4 HWE stack
Hello Timo, or anyone else affected, Accepted xserver-xorg-video-amdgpu-hwe-16.04 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu- hwe-16.04/1.4.0-1~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: xserver-xorg-video-amdgpu-hwe-16.04 (Ubuntu) Importance: Undecided Status: New ** Changed in: xserver-xorg-video-amdgpu-hwe-16.04 (Ubuntu) Status: New => Invalid ** Changed in: xserver-xorg-video-amdgpu-hwe-16.04 (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1716203 Title: Backport packages for 16.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-5.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in vulkan package in Ubuntu: Invalid Status in wayland-protocols package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-16.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-16.04 package in Ubuntu: New Status in xserver-xorg-video-nouveau-hwe-16.04 package in Ubuntu: New Status in libclc source package in Xenial: Fix Released Status in libdrm source package in Xenial: Fix Released Status in llvm-toolchain-5.0 source package in Xenial: Fix Released Status in mesa source package in Xenial: Fix Released Status in vulkan source package in Xenial: Fix Committed Status in wayland-protocols source package in Xenial: Fix Released Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: Fix Released Status in xserver-xorg-video-amdgpu source package in Xenial: New Status in xserver-xorg-video-amdgpu-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-ati source package in Xenial: New Status in xserver-xorg-video-ati-hwe-16.04 source package in Xenial: Fix Committed Status in xserver-xorg-video-nouveau-hwe-16.04 source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.4 *** A minor update, only some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.76 to 2.4.83 - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests - intel: new pci-ids - drm: leak fixes, manpage updates - exynos, etnaviv, freedreno, android: fixes, new stuff wayland-protocols: None, just adds a few protocol definitions (xml files) llvm-toolchain-5.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-5 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for the bugfix release (xenial & artful) is bug 1727390 [Other information] build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 1745866] Re: Audio does not auto-switch to HDMI after switching the connected HDMI TV on
I found a workaround: default.pa load-module module-alsa-sink device=hw:1,7 -- 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/1745866 Title: Audio does not auto-switch to HDMI after switching the connected HDMI TV on Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I start the computer is the connected TV (HDMI) is off and the pulseaudio device stays on unplugged when I switch the TV on. If I switch the TV on before I start the computer, everything works fine. alsa_output.pci-_01_00.1.hdmi-stereo linux-image-14.0-15-generic nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic Regards, Norbert To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1745866/+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 1738582] Re: [MIR] ibus-libpinyin and dependencies
Thank you so much Gunnar!
just a minor comment. ibus-libpinyin can also be toggled to input
traditional Chinese characters (繁體中文）from the default simplified Chinese
（简体中文）。People who live in Taiwan may prefer to use "bopomofo", which, as I
understand it, uses the same engine as ibus-libpinyin but a different
keyboard layout.
With ibus-libpinyin development now seemingly in the pipeline, I am
switching back from Fedora to Ubuntu!
There are ways to improve ibus-libpinyin, will discuss them later. Perhaps
a new thread?
On Mon, Jan 29, 2018 at 2:28 AM, Gunnar Hjalmarsson <
1738...@bugs.launchpad.net> wrote:
> The new versions of both ibus-libpinyin and libpinyin have now migrated
> to bionic-release.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1738582
>
> Title:
> [MIR] ibus-libpinyin and dependencies
>
> Status in ibus-libpinyin package in Ubuntu:
> New
> Status in libpinyin package in Ubuntu:
> New
>
> Bug description:
> Please include these packages in Ubuntu's component main:
>
> * ibus-libpinyin
> * libpinyin (the ibus-libpinyin binary depends on libpinyin7)
>
> As has been discussed at bug #1735362 we would like to replace ibus-
> sunpinyin with ibus-libpinyin ("Intelligent Pinyin") in the live seed
> and as the default input method for typing Simplified Chinese. Reasons
> for the switch are:
>
> - ibus-libpinyin is better maintained
> - ibus-libpinyin is built with and depends on Python3
> (not yet in Debian: https://bugs.debian.org/883631)
> - ibus-libpinyin is default input method in GNOME
>
> Bugs ibus-libpinyin
> ---
> https://github.com/libpinyin/ibus-libpinyin/issues
>
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=ibus-libpinyin
>
> https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin
>
> Bugs libpinyin
> --
> https://github.com/libpinyin/libpinyin/issues
>
> (no open Debian or Ubuntu bugs)
>
>
> I have read https://wiki.ubuntu.com/UbuntuMainInclusionRequirements,
> and haven't found any issues that would prevent the proposed main inclusion.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/
> +bug/1738582/+subscriptions
>
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libpinyin in Ubuntu.
https://bugs.launchpad.net/bugs/1738582
Title:
[MIR] ibus-libpinyin and dependencies
Status in ibus-libpinyin package in Ubuntu:
New
Status in libpinyin package in Ubuntu:
New
Bug description:
Please include these packages in Ubuntu's component main:
* ibus-libpinyin
* libpinyin (the ibus-libpinyin binary depends on libpinyin7)
As has been discussed at bug #1735362 we would like to replace ibus-
sunpinyin with ibus-libpinyin ("Intelligent Pinyin") in the live seed
and as the default input method for typing Simplified Chinese. Reasons
for the switch are:
- ibus-libpinyin is better maintained
- ibus-libpinyin is built with and depends on Python3
(not yet in Debian: https://bugs.debian.org/883631)
- ibus-libpinyin is default input method in GNOME
Bugs ibus-libpinyin
---
https://github.com/libpinyin/ibus-libpinyin/issues
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=ibus-libpinyin
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin
Bugs libpinyin
--
https://github.com/libpinyin/libpinyin/issues
(no open Debian or Ubuntu bugs)
I have read https://wiki.ubuntu.com/UbuntuMainInclusionRequirements, and
haven't found any issues that would prevent the proposed main inclusion.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1738582/+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 1670959] Re: systemd-resolved using 100% CPU
same issue with 17.10, takes a complete core,
DNSMASQ_EXCEPT=lo is not working, also after reboot, it still takes a core
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved using 100% CPU
Status in dnsmasq package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
Confirmed
Bug description:
Sometimes systemd-resolved process is using 100% CPU.
After a while it changes back to normal.
It happens usually after connecting to the (wifi) network, like
starting the OS.
strace output:
sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589),
sin_addr=inet_addr("127.0.0.1")},
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP,
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}],
msg_flags=0}, 0) = 81
sendmsg(3, {msg_name(0)=NULL,
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}],
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589),
sin_addr=inet_addr("127.0.0.1")},
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP,
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}},
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0)
= 53
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
getrandom("\365I", 2, GRND_NONBLOCK)= 2
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
getrandom("\203;", 2, GRND_NONBLOCK)= 2
clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
file or directory)
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
connect(18, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576,
u64=94565471566608}}) = 0
write(18,
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
53) = 53
clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL) = 0
close(18) = 0
journalctl output:
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS
queries reached (max: 150)
As you can see, I would use it together with dnsmasq.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: systemd 232-18ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
Uname: Linux 4.10.0-9-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
Date: Wed Mar 8 08:20:18 2017
MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
SourcePackage: systemd
UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
dmi.bios.date: 03/09/2015
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M77 Ver. 01.05
dmi.board.name: 2271
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 91.4C
dmi.chassis.asset.tag: CNU51199KV
dmi.chassis.typ
[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
Uploaded for T/X/A.
It is now waiting for the SRU verification team to approve the uploads
for the packages to start building in -proposed.
- Eric
** Tags removed: sts-sponsor-slashd
** Tags added: sts-sponsor-slashd-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
Status in AppArmor:
Fix Committed
Status in AppArmor 2.11 series:
Fix Committed
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor source package in Trusty:
In Progress
Status in apparmor source package in Xenial:
In Progress
Status in apparmor source package in Artful:
In Progress
Status in apparmor source package in Bionic:
Fix Released
Status in apparmor package in Debian:
Fix Released
Bug description:
[Impact]
If PID is larger than 6 digits apparmor denies process which only
affect 64-bit systems[1] where the PID_MAX_LIMIT can be generated up
to 7 digits at the maximum.
This fix is committed, but not released. so all supporting version are
affected.
[1] - man 5 proc
--
/proc/sys/kernel/pid_max (since Linux 2.5.34)
This file specifies the value at which PIDs wrap around (i.e., the value in
this file is one greater than the maximum PID). PIDs greater than this value
are not allocated; thus, the value in this file also acts as a system-wide
limit on the total number of processes and threads. The default value for this
file, 32768, results in the same range of PIDs as on ear‐lier kernels. On
32-bit platforms, 32768 is the maximum value for pid_max. On 64-bit systems,
pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4
million).
--
[Test Case]
1. making pid over 6 digits
#!/bin/bash
for i in {1..100}
do
touch t
done
2. snap install --dangerous core_16-2.29.4.2_amd64.snap ( snap core
16-2.30 avoids using /proc/PID/cmdline, so need to use older version
3. you can see DENIED msgs in syslog
4. change /etc/apparmor.d/tunables/kernelvars
5. service apparmor restart
6. service snapd restart
7. DENIED is gone
This is one way, can't reproduce this issue again even if you change
back to original kernelvars, and restart snapd
OR
instead of Seyeong's touch approach, things can be manually change to
7 digits range via sysctl as long as the values are below
approximately 4 millions :
Example:
$ sysctl -w kernel.pid_max=300
$ sysctl -w kernel.ns_last_pid=100
[Regression]
* This is a minor/trivial fix which changes the pid regex only, allowing 7
digits PID instead of only 6 digits PID, we don't think there is any potential
regression.
* If a regression arise, which we highly doubt, one can quickly revert
the change manually and restart the service by modifying
"/etc/apparmor.d/tunables/kernelvars" file to its original state
(before this SRU).
[Others]
* Upstream commit:
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886732
* commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
Author: Vincas Dargis
Date: Sat Sep 30 15:28:15 2017 +0300
Allow seven digit pid
* Affecting releases : TXZAB
--
$ git describe --contains 630cb2a9
v2.11.95~5^2
$ rmadison apparmor
apparmor | 2.8.95~2430-0ubuntu5 | trusty
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
apparmor | 2.10.95-0ubuntu2 | xenial
apparmor | 2.10.95-0ubuntu2.6 | xenial-security
apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
apparmor | 2.11.0-2ubuntu4| zesty
apparmor | 2.11.0-2ubuntu17 | artful
apparmor | 2.11.0-2ubuntu18 | bionic
$ rmadison -u debian apparmor
apparmor | 2.11.1-4 | unstable
--
[Original Description]
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.
@{pid} is defined in /etc/apparmor.d/tunables:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}
It only covers up to 6 digits.
This Ubuntu 17.04 system has:
kernel.pid_max = 4194303
And is showing
type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open"
p
[Touch-packages] [Bug 1745866] Re: Audio does not auto-switch to HDMI after switching the connected HDMI TV on
It is a server installation. I have only ssh connection to the system. I tried to run "apport-collect 1745866" but I can't log in with the terminal browser. Is there a way to make this via ssh? I tried: apport-cli -f -p pulseaudio --save bug.apport But it say no official ubuntu package. -- 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/1745866 Title: Audio does not auto-switch to HDMI after switching the connected HDMI TV on Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I start the computer is the connected TV (HDMI) is off and the pulseaudio device stays on unplugged when I switch the TV on. If I switch the TV on before I start the computer, everything works fine. alsa_output.pci-_01_00.1.hdmi-stereo linux-image-14.0-15-generic nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic Regards, Norbert To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1745866/+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 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
** Changed in: apparmor (Ubuntu Artful)
Status: New => In Progress
** Changed in: apparmor (Ubuntu Xenial)
Status: New => In Progress
** Changed in: apparmor (Ubuntu Trusty)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
Status in AppArmor:
Fix Committed
Status in AppArmor 2.11 series:
Fix Committed
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor source package in Trusty:
In Progress
Status in apparmor source package in Xenial:
In Progress
Status in apparmor source package in Artful:
In Progress
Status in apparmor source package in Bionic:
Fix Released
Status in apparmor package in Debian:
Fix Released
Bug description:
[Impact]
If PID is larger than 6 digits apparmor denies process which only
affect 64-bit systems[1] where the PID_MAX_LIMIT can be generated up
to 7 digits at the maximum.
This fix is committed, but not released. so all supporting version are
affected.
[1] - man 5 proc
--
/proc/sys/kernel/pid_max (since Linux 2.5.34)
This file specifies the value at which PIDs wrap around (i.e., the value in
this file is one greater than the maximum PID). PIDs greater than this value
are not allocated; thus, the value in this file also acts as a system-wide
limit on the total number of processes and threads. The default value for this
file, 32768, results in the same range of PIDs as on ear‐lier kernels. On
32-bit platforms, 32768 is the maximum value for pid_max. On 64-bit systems,
pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4
million).
--
[Test Case]
1. making pid over 6 digits
#!/bin/bash
for i in {1..100}
do
touch t
done
2. snap install --dangerous core_16-2.29.4.2_amd64.snap ( snap core
16-2.30 avoids using /proc/PID/cmdline, so need to use older version
3. you can see DENIED msgs in syslog
4. change /etc/apparmor.d/tunables/kernelvars
5. service apparmor restart
6. service snapd restart
7. DENIED is gone
This is one way, can't reproduce this issue again even if you change
back to original kernelvars, and restart snapd
OR
instead of Seyeong's touch approach, things can be manually change to
7 digits range via sysctl as long as the values are below
approximately 4 millions :
Example:
$ sysctl -w kernel.pid_max=300
$ sysctl -w kernel.ns_last_pid=100
[Regression]
* This is a minor/trivial fix which changes the pid regex only, allowing 7
digits PID instead of only 6 digits PID, we don't think there is any potential
regression.
* If a regression arise, which we highly doubt, one can quickly revert
the change manually and restart the service by modifying
"/etc/apparmor.d/tunables/kernelvars" file to its original state
(before this SRU).
[Others]
* Upstream commit:
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886732
* commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
Author: Vincas Dargis
Date: Sat Sep 30 15:28:15 2017 +0300
Allow seven digit pid
* Affecting releases : TXZAB
--
$ git describe --contains 630cb2a9
v2.11.95~5^2
$ rmadison apparmor
apparmor | 2.8.95~2430-0ubuntu5 | trusty
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
apparmor | 2.10.95-0ubuntu2 | xenial
apparmor | 2.10.95-0ubuntu2.6 | xenial-security
apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
apparmor | 2.11.0-2ubuntu4| zesty
apparmor | 2.11.0-2ubuntu17 | artful
apparmor | 2.11.0-2ubuntu18 | bionic
$ rmadison -u debian apparmor
apparmor | 2.11.1-4 | unstable
--
[Original Description]
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.
@{pid} is defined in /etc/apparmor.d/tunables:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}
It only covers up to 6 digits.
This Ubuntu 17.04 system has:
kernel.pid_max = 4194303
And is showing
type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open"
pr
[Touch-packages] [Bug 1746012] Re: please disable xconsole configuration in 50-default.conf to fix "rsyslogd-2007: action 'action 10' suspended, next retry is ..."
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: rsyslog (Ubuntu) Status: New => Confirmed -- 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/1746012 Title: please disable xconsole configuration in 50-default.conf to fix "rsyslogd-2007: action 'action 10' suspended, next retry is ..." Status in rsyslog package in Ubuntu: Confirmed Bug description: I've noticed this for a long time but never looked into it. My logs have a bunch of entries of the form: rsyslogd-2007: action 'action 10' suspended, next retry is Mon Jan 29 04:08:13 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ] This is caused by these lines in /etc/rsyslog.d/50-default.conf: # The named pipe /dev/xconsole is for the `xconsole' utility. To use it, # you must invoke `xconsole' with the `-file' option: # #$ xconsole -file /dev/xconsole [...] # # NOTE: adjust the list below, or you'll go crazy if you have a reasonably # busy site.. # daemon.*;mail.*;\ news.err;\ *.=debug;*.=info;\ *.=notice;*.=warn |/dev/xconsole /dev/xconsole is not setup by default in Ubuntu. Commenting out the above and restarting rsyslog resolves the issue. This issue was reported to Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745492 and they disabled xconsole configuration by default in 8.14.0-2, however subsequent Ubuntu merges left the configuration in debian/50-default.conf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1746012/+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 1720364] Re: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS
Bionic Beaver with all updates, bug exists. Ctrl+Shift as layout switcher, English+Russian layouts. -- 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/1720364 Title: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS Status in MATE Desktop: New Status in ubuntu-mate: New Status in X.Org X server: Confirmed Status in marco package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Status in xorg-hwe-16.04 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install ubuntu-mate-desktop on Ubuntu 17.10. 2. Set-up two keyboard layouts - English and Russian 3. Set as keyboard layout switcher 4. Try to use shortcuts starting from : 4.1. Open Firefox, open new tab, go to some site in it, close tab, try to click to restore closed tab. 4.2. Open mate-terminal, try to open new tab with , or copy (), or paste (). 4.3. Open pluma, write some text, try to navigate in it with . Expected results: switches keyboard layout, shortcuts starting from work normally. Actual results: switches keyboard layout, shortcuts starting from do not work. Notes: 1. Ubuntu 16.04 LTS with Marco and Compton work normally with keyboard layout switcher. 2. This problem was discovered before on 13.10, 14.04 and other modern versions with GNOME desktop (Metacity and Compiz) - see bug 1245473. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: marco 1.18.1-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu1 Architecture: i386 CurrentDesktop: MATE Date: Fri Sep 29 16:18:02 2017 InstallationDate: Installed on 2017-08-26 (33 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) SourcePackage: marco UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1720364/+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 1745828] Re: Ubuntu 16.04 can't find any Bluetooth devices
** Package changed: ubuntu => bluez (Ubuntu) -- 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/1745828 Title: Ubuntu 16.04 can't find any Bluetooth devices Status in bluez package in Ubuntu: New Bug description: It is ON and VISIBLE in the control panel. My iPhone can see two other devices but it can't see the computer, and the computer can't see anything, even if left searching for tens of minutes. The previous answers listed below suggest the following diagnostics Bluetooth not working after update How can I make my bluetooth works on Ubuntu 16.04? Ubuntu 16.04 bluetooth not working (Dell XPS13) Bluetooth (Atheros AR3012) not working on Ubuntu 16.04 Bluetooth not working on Ubuntu 16.04 LTS Bluetooth cannot find any devices Stuck on a bluetooth problem The service seems to be running /home >sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago Docs: man:bluetoothd(8) Main PID: 790 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─790 /usr/lib/bluetooth/bluetoothd Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. and not blocked /home >rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no I have edited /etc/bluetooth/main.conf to include AutoEnable=true but I noted that the entire file was commented out. The kernel seems reasonably up to date >uname -a Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I wonder if I need a device driver, but I have no idea how to find out. The following diagnostics may help some of you knowledgeable people find out. >hcitool dev Devices: hci024:0A:64:F5:EE:86 and the output of dmsg is >dmesg | grep Blue [2.030855] usb 1-1.4: Product: Bluetooth Radio [ 13.806355] Bluetooth: Core ver 2.22 [ 13.806369] Bluetooth: HCI device and connection manager initialized [ 13.806372] Bluetooth: HCI socket layer initialized [ 13.806373] Bluetooth: L2CAP socket layer initialized [ 13.806377] Bluetooth: SCO socket layer initialized [ 13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a lmp_ver=06 lmp_subver=8821 [ 13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin [ 13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin [ 13.877382] Bluetooth: hci0: rom_version status=0 version=1 [ 13.877387] Bluetooth: cfg_sz 0, total size 17428 [ 16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 16.550281] Bluetooth: BNEP filters: protocol multicast [ 16.550284] Bluetooth: BNEP socket layer initialized [ 27.868345] Bluetooth: RFCOMM TTY layer initialized [ 27.868350] Bluetooth: RFCOMM socket layer initialized [ 27.868354] Bluetooth: RFCOMM ver 1.11 and of lsusb is >lsusb Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 13d3:3414 IMC Networks Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Thanking you in anticipation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745828/+subscriptions -- Mailing list: https://launchpad.net/~touch-packag
[Touch-packages] [Bug 1635933] Re: package avahi-dnsconfd (not installed) failed to install/upgrade: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: avahi (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1635933 Title: package avahi-dnsconfd (not installed) failed to install/upgrade: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück Status in avahi package in Ubuntu: Confirmed Bug description: happened while uninstalling ProblemType: Package DistroRelease: Ubuntu 16.10 Package: avahi-dnsconfd (not installed) ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sat Oct 22 22:31:09 2016 ErrorMessage: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2016-10-14 (8 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: avahi Title: package avahi-dnsconfd (not installed) failed to install/upgrade: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to yakkety on 2016-10-14 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1635933/+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 1745828] [NEW] Ubuntu 16.04 can't find any Bluetooth devices
You have been subscribed to a public bug: It is ON and VISIBLE in the control panel. My iPhone can see two other devices but it can't see the computer, and the computer can't see anything, even if left searching for tens of minutes. The previous answers listed below suggest the following diagnostics Bluetooth not working after update How can I make my bluetooth works on Ubuntu 16.04? Ubuntu 16.04 bluetooth not working (Dell XPS13) Bluetooth (Atheros AR3012) not working on Ubuntu 16.04 Bluetooth not working on Ubuntu 16.04 LTS Bluetooth cannot find any devices Stuck on a bluetooth problem The service seems to be running /home >sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago Docs: man:bluetoothd(8) Main PID: 790 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─790 /usr/lib/bluetooth/bluetoothd Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. and not blocked /home >rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no I have edited /etc/bluetooth/main.conf to include AutoEnable=true but I noted that the entire file was commented out. The kernel seems reasonably up to date >uname -a Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I wonder if I need a device driver, but I have no idea how to find out. The following diagnostics may help some of you knowledgeable people find out. >hcitool dev Devices: hci024:0A:64:F5:EE:86 and the output of dmsg is >dmesg | grep Blue [2.030855] usb 1-1.4: Product: Bluetooth Radio [ 13.806355] Bluetooth: Core ver 2.22 [ 13.806369] Bluetooth: HCI device and connection manager initialized [ 13.806372] Bluetooth: HCI socket layer initialized [ 13.806373] Bluetooth: L2CAP socket layer initialized [ 13.806377] Bluetooth: SCO socket layer initialized [ 13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a lmp_ver=06 lmp_subver=8821 [ 13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin [ 13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin [ 13.877382] Bluetooth: hci0: rom_version status=0 version=1 [ 13.877387] Bluetooth: cfg_sz 0, total size 17428 [ 16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 16.550281] Bluetooth: BNEP filters: protocol multicast [ 16.550284] Bluetooth: BNEP socket layer initialized [ 27.868345] Bluetooth: RFCOMM TTY layer initialized [ 27.868350] Bluetooth: RFCOMM socket layer initialized [ 27.868354] Bluetooth: RFCOMM ver 1.11 and of lsusb is >lsusb Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 13d3:3414 IMC Networks Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Thanking you in anticipation ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Ubuntu 16.04 can't find any Bluetooth devices https://bugs.launchpad.net/bugs/1745828 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
** Tags added: rls-bb-incoming -- 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/1682637 Title: during recovery mode, enable network failed due to /etc/resolv.conf not being present Status in friendly-recovery package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Invalid Status in thermald package in Ubuntu: Invalid Bug description: Something went wrong that required me to boot to recovery mode via grub. The important part here, is that while I got as far as the recovery screen asking to "Enable Networking" and other options fsck filesystems, drop to root shell, etc. and selected "Enable Networking": the result was: grep: /etc/resolv.conf: No such File or directory. Unknown group "power" in message bus configuration file. (Networking did not enable, leaving me stranded at root shell without network which would have made adding/removing packages to troubleshoot easier) Ubuntu: zesty 17.04 Linux: Linux Hedy 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux network-manager: 1.4.4-1ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 13 16:40:19 2017 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-07-09 (1009 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708) IpRoute: default via 192.168.250.1 dev wlan1 proto static metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 192.168.250.0/24 dev wlan1 proto kernel scope link src 192.168.250.3 metric 600 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH lxcbr0 bridgeconnected/org/freedesktop/NetworkManager/Devices/3 lxcbr0 46595dd8-757b-4d93-ade3-c066f72d9e2e /org/freedesktop/NetworkManager/ActiveConnection/0 wlan1 wifi connected/org/freedesktop/NetworkManager/Devices/2 Brisbane House 2b25e748-f9c5-4c84-9fe6-0f64071fcf0b /org/freedesktop/NetworkManager/ActiveConnection/1 eth1ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1682637/+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 1743018] Re: Unable to install mesa-opencl-icd because of unmet dependencies on Xenial
64-bit Bionic Beaver with all current updates - `mesa-opencl-icd` installed without problems: $ apt-cache policy mesa-opencl-icd mesa-opencl-icd: Installed: 17.2.4-0ubuntu2 Candidate: 17.2.4-0ubuntu2 Version table: *** 17.2.4-0ubuntu2 500 500 http://ru.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status -- 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/1743018 Title: Unable to install mesa-opencl-icd because of unmet dependencies on Xenial Status in mesa package in Ubuntu: Invalid Status in mesa source package in Xenial: Fix Released Bug description: Steps to reproduce: 1. Install Ubuntu 16.04 LTS 2. Try to install `mesa-opencl-icd` with $ sudo apt-get install mesa-opencl-icd [sudo] password for user: Reading package lists... Done Building dependency tree Reading state information... Done Expected results: * mesa-opencl-icd is installed successfully Actual results: * got errors as follow Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mesa-opencl-icd : Depends: libclc-r600 (>= 0.2.0+git20170330-3) but it is not going to be installed Depends: libclc-amdgcn (>= 0.2.0+git20170330-3) but it is not going to be installed E: Unable to correct problems, you have held broken packages. Note: inspired by this AskUbuntu question - https://askubuntu.com/q/995274/66509 . ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: mesa-opencl-icd (not installed) ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,mousepoll,move,gnomecompat,wall,regex,place,resize,snap,session,imgpng,vpswitch,grid,unitymtgrabhandles,animation,expo,workarounds,ezoom,staticswitcher,fade,scale,unityshell] CompositorRunning: None CurrentDesktop: MATE Date: Fri Jan 12 21:22:22 2018 DistUpgraded: 2017-04-16 02:19:02,541 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:2135] InstallationDate: Installed on 2014-02-07 (1434 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204) MachineType: ASUSTeK COMPUTER INC. UX32A ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic root=UUID=1e3c78e2-1a6e-4afe-8249-40fe7fa81a86 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to xenial on 2017-04-15 (271 days ago) dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32A.216 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Jan 12 20:32:41 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1743018/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packa
[Touch-packages] [Bug 1744328] Re: libfreebl3.so should be public, not in the nss subdir
Suggested a fix to Debian, but also to hear if there is any known background
why it was split up that way.
See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888764
** Bug watch added: Debian Bug tracker #888764
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888764
** Also affects: nss (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888764
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1744328
Title:
libfreebl3.so should be public, not in the nss subdir
Status in nss package in Ubuntu:
New
Status in nss package in Debian:
Unknown
Bug description:
Hi,
I tried to move the chrony dependency from tomcrypt to libnss to avoid
universe dependencies.
While doing so I found that libfreebl3 is not "normally" linkable being
outside the normal ld paths.
E.g. sample program
#include
#include
#include
int main(int argc, char **argv) {
NSSLOWHASH_Begin(NSSLOWHASH_NewContext(NSSLOW_Init(), HASH_AlgSHA512));
return 0;
}
Build:
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-Wmissing-prototypes -Wall -pthread -Wdate-time -D_FORTIFY_SOURCE=2
-I/usr/include/nss -I/usr/include/nspr -o docheck docheck.c -lfreebl3
-Wl,-Bsymbolic-functions -Wl,-z,relro -v -Wl,-v -L/usr/lib/x86_64-linux-gnu/nss
Then:
ldd docheck
will give you
libfreebl3.so => not found
Obviously a link into /usr/lib/x86_64-linux-gnu/ fixes the issue but
needs some more consideration if that is the thing we want (there
might be a reason it is where it is).
Note: Required to go on with the chrony MIR which is rather urgent to
be sorted out as it has a lot of other dependencies that need to be
adapted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1744328/+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 1201528] Re: [INTEL DP55WG, Realtek ALC889] - Audio Playback Unavailable
Hello all, First of all, sorry I did not try the kernel that Joseph provided over a year ago, I've been traveling and not having my desktop computer close. I'm now settled in a location with my desktop computer as my daily and main computer, and I'm still seeing this bug occur. I'm running ubuntu xenial 16.04 with the stock kernel: nessita@dali:~$ uname -a Linux dali 4.4.0-109-generic #132-Ubuntu SMP Tue Jan 9 19:52:39 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux And audio breaks just like I've posted earlier: ( 71.143| 0.000) I: [alsa-sink-ALC889 Analog] alsa-sink.c: Underrun! I've recorded a new log file from running pulseaudio with verbose output and I've attached it to this bug. ** Attachment added: "pulseverbose.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201528/+attachment/5045074/+files/pulseverbose.log -- 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/1201528 Title: [INTEL DP55WG,Realtek ALC889] - Audio Playback Unavailable Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in alsa-driver source package in Vivid: Confirmed Status in linux source package in Vivid: Won't Fix Bug description: This is a fresh upgrade to raring. During the weekend, I updated from precise to quantal, and from there to raring. I did not use sound while the system was in quantal, so no idea if the bug was present there as well. The symptom is: * after some period of sound usage, playback stops working What I mean with sound usage is: I tried having a meeting with: mumble, skype, and google hangout, and in all three cases, audio input/outout will work just fine for ~5 minutes, and the playback just dies (people tell me they keep listening to me, so mic works fine). The only way to solve this is by rebooting. After one of the reboots, I was able to play a 20 minute video with mplayer with no further issue. Then opened skype and after ~3-5 minute talk, audio playback died again. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nessita2627 F pulseaudio Date: Mon Jul 15 14:40:20 2013 InstallationDate: Installed on 2011-12-20 (572 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (2029.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_AlsaPlaybackTestStderr: W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o r T r a n s f e r f a i l e d : O p e r a t i o n n o t p e r m i t t e d Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Headphone Out, Front Symptom_Type: None of the above Title: [, Realtek ALC889, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to raring on 2013-07-13 (2 days ago) dmi.bios.date: 08/05/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WG dmi.board.vendor: Intel Corporation dmi.board.version: AAE57269-404 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.3206.2009.0805.1855:bd08/05/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-404:cvn:ct2:cvr: --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nessita 13188 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=bd987ac2-eb4b-43e7-881b-4cf2b5078e4b InstallationDate: Installed on 2014-05-11 (366 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=e91bd3a4-787b-404b-9f19-aa6dcbe707b0 ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 RfKill: Tags: vivid vivid vivid vivid Uname: Linux 3.19.0-16-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-03-11 (61 days ago) UserGroups: adm cdrom dip l
[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
This bug was fixed in the package apparmor - 2.11.0-2ubuntu19
---
apparmor (2.11.0-2ubuntu19) bionic; urgency=medium
* d/p/0001-Allow-seven-digit-pid.patch:
On 64bit systems, /proc/sys/kernel/pid_max can be set to PID_MAX_LIMIT,
(2^22), which results in seven digit pids. Adjust the @{PID} variable in
tunables/global to accept this. (LP: #1717714)
-- Seyeong Kim Mon, 08 Jan 2018 07:52:32
-0800
** Changed in: apparmor (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
Status in AppArmor:
Fix Committed
Status in AppArmor 2.11 series:
Fix Committed
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor source package in Trusty:
New
Status in apparmor source package in Xenial:
New
Status in apparmor source package in Artful:
New
Status in apparmor source package in Bionic:
Fix Released
Status in apparmor package in Debian:
Fix Released
Bug description:
[Impact]
If PID is larger than 6 digits apparmor denies process which only
affect 64-bit systems[1] where the PID_MAX_LIMIT can be generated up
to 7 digits at the maximum.
This fix is committed, but not released. so all supporting version are
affected.
[1] - man 5 proc
--
/proc/sys/kernel/pid_max (since Linux 2.5.34)
This file specifies the value at which PIDs wrap around (i.e., the value in
this file is one greater than the maximum PID). PIDs greater than this value
are not allocated; thus, the value in this file also acts as a system-wide
limit on the total number of processes and threads. The default value for this
file, 32768, results in the same range of PIDs as on ear‐lier kernels. On
32-bit platforms, 32768 is the maximum value for pid_max. On 64-bit systems,
pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4
million).
--
[Test Case]
1. making pid over 6 digits
#!/bin/bash
for i in {1..100}
do
touch t
done
2. snap install --dangerous core_16-2.29.4.2_amd64.snap ( snap core
16-2.30 avoids using /proc/PID/cmdline, so need to use older version
3. you can see DENIED msgs in syslog
4. change /etc/apparmor.d/tunables/kernelvars
5. service apparmor restart
6. service snapd restart
7. DENIED is gone
This is one way, can't reproduce this issue again even if you change
back to original kernelvars, and restart snapd
OR
instead of Seyeong's touch approach, things can be manually change to
7 digits range via sysctl as long as the values are below
approximately 4 millions :
Example:
$ sysctl -w kernel.pid_max=300
$ sysctl -w kernel.ns_last_pid=100
[Regression]
* This is a minor/trivial fix which changes the pid regex only, allowing 7
digits PID instead of only 6 digits PID, we don't think there is any potential
regression.
* If a regression arise, which we highly doubt, one can quickly revert
the change manually and restart the service by modifying
"/etc/apparmor.d/tunables/kernelvars" file to its original state
(before this SRU).
[Others]
* Upstream commit:
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886732
* commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
Author: Vincas Dargis
Date: Sat Sep 30 15:28:15 2017 +0300
Allow seven digit pid
* Affecting releases : TXZAB
--
$ git describe --contains 630cb2a9
v2.11.95~5^2
$ rmadison apparmor
apparmor | 2.8.95~2430-0ubuntu5 | trusty
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
apparmor | 2.10.95-0ubuntu2 | xenial
apparmor | 2.10.95-0ubuntu2.6 | xenial-security
apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
apparmor | 2.11.0-2ubuntu4| zesty
apparmor | 2.11.0-2ubuntu17 | artful
apparmor | 2.11.0-2ubuntu18 | bionic
$ rmadison -u debian apparmor
apparmor | 2.11.1-4 | unstable
--
[Original Description]
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.
@{pid} is defined in /etc/apparmor.d/tunables:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1
[Touch-packages] [Bug 1742403] Re: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: installed network-manager-config-connectivity-ubuntu package post-instal
This bug was fixed in the package network-manager - 1.8.4-1ubuntu4 --- network-manager (1.8.4-1ubuntu4) bionic; urgency=medium * Do not fail installation of network-manager-config-connectivity-* if network-manager fails to reload (LP: #1742403) -- Jean-Baptiste Lallement Wed, 10 Jan 2018 10:23:38 +0100 ** Changed in: network-manager (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1742403 Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: installed network-manager-config- connectivity-ubuntu package post-installation script subprocess returned error exit status 1 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Artful: Fix Committed Bug description: [Description] Installation of network-manager-config-connectivity fails if network-manager is not running. The patch appends " || true " to force-reload in the postinst script to not fail in this case. [QA] Test Case: 1. On a machine without network-manager already install (eg server install) install network-manager-config-connectivity-ubuntu Expected Result: It installs successfully with all its dependencies buckets on errors.u.c https://errors.ubuntu.com/problem/ff73bf3ac18fbeb732d1d4f6676a15e24e7f7399 https://errors.ubuntu.com/problem/6da94ccacd3e341967667bc1e7b2e83e4ac82026 [Regression potential] Low to none. If the fix works the package will install, and if it does not work it will still fail to install. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Wed Jan 10 08:50:17 2018 ErrorMessage: installed network-manager-config-connectivity-ubuntu package post-installation script subprocess returned error exit status 1 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-09-03 (1589 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha5 SourcePackage: network-manager Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: installed network-manager-config-connectivity-ubuntu package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1742403/+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 1746015] Re: Apt and apt-get do not ship a us_EN language catalog
software generally does not ship en locales as the C locale covers that. ** Changed in: apt (Ubuntu) Status: New => Invalid -- 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/1746015 Title: Apt and apt-get do not ship a us_EN language catalog Status in apt package in Ubuntu: Invalid Bug description: Description:Ubuntu 17.10 Release:17.10 If you install anthy with additional languages, with "US English" as your primary language, you end up with a "locale" output similar to the following: $ locale LANG=en_US.UTF-8 LANGUAGE=en_US:de:ja LC_CTYPE="en_US.UTF-8" LC_NUMERIC=en_GB.UTF-8 LC_TIME=en_GB.UTF-8 LC_COLLATE=C LC_MONETARY=en_US.UTF-8 LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= The LANGUAGE variable in this case is using the rules from https://www.gnu.org/software/gettext/manual/html_node/The-LANGUAGE- variable.html When running "aptitude" or "apt-get" or "apt install", the messages that come back are in German. If you strace those commands, you'll see apt trying to search for an en_US or en catalog, finding none, and falling down to the 2nd language in the list: "de" or German. If you run: $ LANGUAGE="" apt-get update Then the messages come back in English, because the system's fallen back to the "C" locale. apt should also properly ship an en_US language catalog. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apt 1.5.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Jan 29 08:31:38 2018 InstallationDate: Installed on 2017-04-27 (276 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: apt UpgradeStatus: Upgraded to artful on 2018-01-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1746015/+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 1744328] Re: libfreebl3.so should be public, not in the nss subdir
I followed the suggestion to take a look at Fedora, and it really is
public there.
$ dnf repoquery --installed -l nss-softokn-freebl nss-softokn | grep '.so$'
/usr/lib64/libfreebl3.so
/usr/lib64/libfreeblpriv3.so
/usr/lib64/libnssdbm3.so
/usr/lib64/libsoftokn3.so
The only special one is /usr/lib64/libnssckbi.so which goes via in
indirection through /etc/alternatives as it can be provided by p11-kit-
trust
There might have been history in Debian we don't know of.
Create a suggested fix - for now only for freebl3, not the others - to move
them to an accessible path and suggest to Debian.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1744328
Title:
libfreebl3.so should be public, not in the nss subdir
Status in nss package in Ubuntu:
New
Bug description:
Hi,
I tried to move the chrony dependency from tomcrypt to libnss to avoid
universe dependencies.
While doing so I found that libfreebl3 is not "normally" linkable being
outside the normal ld paths.
E.g. sample program
#include
#include
#include
int main(int argc, char **argv) {
NSSLOWHASH_Begin(NSSLOWHASH_NewContext(NSSLOW_Init(), HASH_AlgSHA512));
return 0;
}
Build:
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-Wmissing-prototypes -Wall -pthread -Wdate-time -D_FORTIFY_SOURCE=2
-I/usr/include/nss -I/usr/include/nspr -o docheck docheck.c -lfreebl3
-Wl,-Bsymbolic-functions -Wl,-z,relro -v -Wl,-v -L/usr/lib/x86_64-linux-gnu/nss
Then:
ldd docheck
will give you
libfreebl3.so => not found
Obviously a link into /usr/lib/x86_64-linux-gnu/ fixes the issue but
needs some more consideration if that is the thing we want (there
might be a reason it is where it is).
Note: Required to go on with the chrony MIR which is rather urgent to
be sorted out as it has a lot of other dependencies that need to be
adapted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1744328/+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 1733870] Re: [Ubuntu 18.04] Add GDB support to access/display POWER8 registers
** Tags added: triage-g -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1733870 Title: [Ubuntu 18.10] Add GDB support to access/display POWER8 registers Status in The Ubuntu-power-systems project: Incomplete Status in gdb package in Ubuntu: Incomplete Bug description: This feature request is for GDB support for access to Power registers that are currently not accessible: PPR, DSCR, TAR, EBB, PMU and HTM registers. The feature is currently being worked on, so no upstream code is available yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1733870/+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 1742941] Re: zlib: improve crc32 performance on P8
** Changed in: zlib (Ubuntu) Assignee: David Britton (davidpbritton) => Patricia Gaughen (gaughen) ** Changed in: ubuntu-power-systems Assignee: David Britton (davidpbritton) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1742941 Title: zlib: improve crc32 performance on P8 Status in The Ubuntu-power-systems project: Triaged Status in zlib package in Ubuntu: New Bug description: Calculate the checksum of data that is 16 byte aligned and a multiple of 16 bytes. The first step is to reduce it to 1024 bits. We do this in 8 parallel chunks in order to mask the latency of the vpmsum instructions. If we have more than 32 kB of data to checksum we repeat this step multiple times, passing in the previous 1024 bits. The next step is to reduce the 1024 bits to 64 bits. This step adds 32 bits of 0s to the end - this matches what a CRC does. We just calculate constants that land the data in this 32 bits. We then use fixed point Barrett reduction to compute a mod n over GF(2) for n = CRC using POWER8 instructions. We use x = 32. http://en.wikipedia.org/wiki/Barrett_reduction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1742941/+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 1733870] Re: [Ubuntu 18.10] Add GDB support to access/display POWER8 registers
** Summary changed: - [Ubuntu 18.04] Add GDB support to access/display POWER8 registers + [Ubuntu 18.10] Add GDB support to access/display POWER8 registers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1733870 Title: [Ubuntu 18.10] Add GDB support to access/display POWER8 registers Status in The Ubuntu-power-systems project: Incomplete Status in gdb package in Ubuntu: Incomplete Bug description: This feature request is for GDB support for access to Power registers that are currently not accessible: PPR, DSCR, TAR, EBB, PMU and HTM registers. The feature is currently being worked on, so no upstream code is available yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1733870/+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 1742941] Re: zlib: improve crc32 performance on P8
** Changed in: zlib (Ubuntu) Assignee: Patricia Gaughen (gaughen) => Canonical Foundations Team (canonical-foundations) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1742941 Title: zlib: improve crc32 performance on P8 Status in The Ubuntu-power-systems project: Triaged Status in zlib package in Ubuntu: New Bug description: Calculate the checksum of data that is 16 byte aligned and a multiple of 16 bytes. The first step is to reduce it to 1024 bits. We do this in 8 parallel chunks in order to mask the latency of the vpmsum instructions. If we have more than 32 kB of data to checksum we repeat this step multiple times, passing in the previous 1024 bits. The next step is to reduce the 1024 bits to 64 bits. This step adds 32 bits of 0s to the end - this matches what a CRC does. We just calculate constants that land the data in this 32 bits. We then use fixed point Barrett reduction to compute a mod n over GF(2) for n = CRC using POWER8 instructions. We use x = 32. http://en.wikipedia.org/wiki/Barrett_reduction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1742941/+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 1744328] Re: libfreebl3.so should be public, not in the nss subdir
For the block in proposed I proposed
https://code.launchpad.net/~paelzer/britney/hints-ubuntu-mask-389-ds-base/+merge/336779
** Branch linked: lp:~paelzer/britney/hints-ubuntu-mask-389-ds-base
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1744328
Title:
libfreebl3.so should be public, not in the nss subdir
Status in nss package in Ubuntu:
New
Bug description:
Hi,
I tried to move the chrony dependency from tomcrypt to libnss to avoid
universe dependencies.
While doing so I found that libfreebl3 is not "normally" linkable being
outside the normal ld paths.
E.g. sample program
#include
#include
#include
int main(int argc, char **argv) {
NSSLOWHASH_Begin(NSSLOWHASH_NewContext(NSSLOW_Init(), HASH_AlgSHA512));
return 0;
}
Build:
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-Wmissing-prototypes -Wall -pthread -Wdate-time -D_FORTIFY_SOURCE=2
-I/usr/include/nss -I/usr/include/nspr -o docheck docheck.c -lfreebl3
-Wl,-Bsymbolic-functions -Wl,-z,relro -v -Wl,-v -L/usr/lib/x86_64-linux-gnu/nss
Then:
ldd docheck
will give you
libfreebl3.so => not found
Obviously a link into /usr/lib/x86_64-linux-gnu/ fixes the issue but
needs some more consideration if that is the thing we want (there
might be a reason it is where it is).
Note: Required to go on with the chrony MIR which is rather urgent to
be sorted out as it has a lot of other dependencies that need to be
adapted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1744328/+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 1746012] [NEW] please disable xconsole configuration in 50-default.conf to fix "rsyslogd-2007: action 'action 10' suspended, next retry is ..."
Public bug reported: I've noticed this for a long time but never looked into it. My logs have a bunch of entries of the form: rsyslogd-2007: action 'action 10' suspended, next retry is Mon Jan 29 04:08:13 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ] This is caused by these lines in /etc/rsyslog.d/50-default.conf: # The named pipe /dev/xconsole is for the `xconsole' utility. To use it, # you must invoke `xconsole' with the `-file' option: # #$ xconsole -file /dev/xconsole [...] # # NOTE: adjust the list below, or you'll go crazy if you have a reasonably # busy site.. # daemon.*;mail.*;\ news.err;\ *.=debug;*.=info;\ *.=notice;*.=warn |/dev/xconsole /dev/xconsole is not setup by default in Ubuntu. Commenting out the above and restarting rsyslog resolves the issue. This issue was reported to Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745492 and they disabled xconsole configuration by default in 8.14.0-2, however subsequent Ubuntu merges left the configuration in debian/50-default.conf. ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Summary changed: - rsyslogd-2007: action 'action 10' suspended, next retry is Mon Jan 29 04:08:13 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ] + rsyslogd-2007: action 'action 10' suspended, next retry is ... ** Summary changed: - rsyslogd-2007: action 'action 10' suspended, next retry is ... + please disable xconsole configuration in 50-default.conf to fix "rsyslogd-2007: action 'action 10' suspended, next retry is ..." -- 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/1746012 Title: please disable xconsole configuration in 50-default.conf to fix "rsyslogd-2007: action 'action 10' suspended, next retry is ..." Status in rsyslog package in Ubuntu: New Bug description: I've noticed this for a long time but never looked into it. My logs have a bunch of entries of the form: rsyslogd-2007: action 'action 10' suspended, next retry is Mon Jan 29 04:08:13 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ] This is caused by these lines in /etc/rsyslog.d/50-default.conf: # The named pipe /dev/xconsole is for the `xconsole' utility. To use it, # you must invoke `xconsole' with the `-file' option: # #$ xconsole -file /dev/xconsole [...] # # NOTE: adjust the list below, or you'll go crazy if you have a reasonably # busy site.. # daemon.*;mail.*;\ news.err;\ *.=debug;*.=info;\ *.=notice;*.=warn |/dev/xconsole /dev/xconsole is not setup by default in Ubuntu. Commenting out the above and restarting rsyslog resolves the issue. This issue was reported to Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745492 and they disabled xconsole configuration by default in 8.14.0-2, however subsequent Ubuntu merges left the configuration in debian/50-default.conf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1746012/+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 1719579] Re: [Ubuntu 18.04] [libvirt] virsh restore fails from state file saved in /var/tmp folder using virsh save
** Summary changed:
- [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved in
/var/tmp folder using virsh save
+ [Ubuntu 18.04] [libvirt] virsh restore fails from state file saved in
/var/tmp folder using virsh save
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1719579
Title:
[Ubuntu 18.04] [libvirt] virsh restore fails from state file saved in
/var/tmp folder using virsh save
Status in The Ubuntu-power-systems project:
Triaged
Status in apparmor package in Ubuntu:
Invalid
Status in libvirt package in Ubuntu:
Triaged
Bug description:
== Comment: #1 - SEETEENA THOUFEEK - 2017-01-17
00:09:16 ==
Bala, Please mail me the machine information.
== Comment: #3 - SEETEENA THOUFEEK - 2017-01-17
02:14:06 ==
2017-01-16 12:09:37.707+: 7024: info :
virSecurityDACRestoreFileLabelInternal:388 : Restoring DAC user and group on
'/var/tmp/bala'
2017-01-16 12:09:37.707+: 7024: info :
virSecurityDACSetOwnershipInternal:290 : Setting DAC user and group on
'/var/tmp/bala' to '0:0'
2017-01-16 12:09:37.707+: 7024: warning : qemuDomainSaveImageStartVM:6750
: failed to restore save state label on /var/tmp/bala
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF:
obj=0x3fff4ca62b00
2017-01-16 12:09:37.707+: 7024: debug : qemuDomainObjEndAsyncJob:1848 :
Stopping async job: start (vm=0x3fff4ca535c0 name=virt-tests-vm1-bala)
2017-01-16 12:09:37.707+: 7024: info : virObjectRef:296 : OBJECT_REF:
obj=0x3fff4ca62b00
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF:
obj=0x3fff4ca62b00
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF:
obj=0x3fff4ca535c0
2017-01-16 12:09:37.707+: 7024: debug : virThreadJobClear:121 : Thread
7024 (virNetServerHandleJob) finished job remoteDispatchDomainRestore with
ret=-1
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF:
obj=0x3fff7c002c10
2017-01-16 12:09:37.707+: 7024: debug : virNetServerProgramSendError:153
: prog=536903814 ver=1 proc=54 type=1 serial=4 msg=0x100133d2590
rerr=0x3fffa59be3c0
2017-01-16 12:09:37.707+: 7024: debug : virNetMessageEncodePayload:376 :
Encode length as 172
2017-01-16 12:09:37.707+: 7024: debug :
virNetServerClientSendMessageLocked:1399 : msg=0x100133d2590 proc=54 len=172
offset=0
2017-01-16 12:09:37.707+: 7024: info :
virNetServerClientSendMessageLocked:1407 : RPC_SERVER_CLIENT_MSG_TX_QUEUE:
client=0x100133d23c0 len=172 prog=536903814 vers=1 proc=54 type=1 status=1
serial=4
2017-01-16 12:09:37.707+: 7024: debug :
virNetServerClientCalculateHandleMode:157 : tls=(nil) hs=-1, rx=0x100133d0670
tx=0x100133d2590
2017-01-16 12:09:37.707+: 7024: debug :
virNetServerClientCalculateHandleMode:192 : mode=3
2017-01-16 12:09:37.707+: 7024: info : virEventPollUpdateHandle:152 :
EVENT_POLL_UPDATE_HANDLE: watch=417 events=3
2017-01-16 12:09:37.707+: 7024: debug : virEventPollInterruptLocked:727 :
Interrupting
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF:
obj=0x3fff7c002c10
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF:
obj=0x100133caea0
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF:
obj=0x100133d23c0
.
2017-01-16 12:14:28.445+: 7019: info : qemuMonitorJSONIOProcessLine:201 :
QEMU_MONITOR_RECV_EVENT: mon=0x3fff94004d90 event={"timestamp": {"seconds":
1484568868, "microseconds": 444620}, "event": "MIGRATION", "data": {"status":
"failed"}}
2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorJSONIOProcessEvent:147
: mon=0x3fff94004d90 obj=0x100133b5670
2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1762 :
object=0x100133a8000
2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 :
object=0x100133a8000 type=0 gen=0x100133d1160
2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 :
object=0x100133d2a80 type=2 gen=0x100133d1160
2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1795 :
result={"status":"failed"}
2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorEmitEvent:1218 :
mon=0x3fff94004d90 event=MIGRATION
2017-01-16 12:14:28.445+: 7019: info : virObjectRef:296 : OBJECT_REF:
obj=0x3fff94004d90
2017-01-16 12:14:28.445+: 7019: debug : qemuProcessHandleEvent:629 :
vm=0x3fff4ca535c0
2017-01-16 12:14:28.445+: 7019: info : virObjectNew:202 : OBJECT_NEW:
obj=0x100133d2870 classname=virDomainQemuMonitorEvent
2017-01-16 12:14:28.445+: 7019: debug : virObjectEventNew:645 :
obj=0x100133d2870
2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:259 : OBJECT_UNREF:
obj=0x100133d2870
2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:261 :
OBJECT_DISPOSE: obj=0x100133d28
[Touch-packages] [Bug 1746015] [NEW] Apt and apt-get do not ship a us_EN language catalog
Public bug reported: Description:Ubuntu 17.10 Release:17.10 If you install anthy with additional languages, with "US English" as your primary language, you end up with a "locale" output similar to the following: $ locale LANG=en_US.UTF-8 LANGUAGE=en_US:de:ja LC_CTYPE="en_US.UTF-8" LC_NUMERIC=en_GB.UTF-8 LC_TIME=en_GB.UTF-8 LC_COLLATE=C LC_MONETARY=en_US.UTF-8 LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= The LANGUAGE variable in this case is using the rules from https://www.gnu.org/software/gettext/manual/html_node/The-LANGUAGE- variable.html When running "aptitude" or "apt-get" or "apt install", the messages that come back are in German. If you strace those commands, you'll see apt trying to search for an en_US or en catalog, finding none, and falling down to the 2nd language in the list: "de" or German. If you run: $ LANGUAGE="" apt-get update Then the messages come back in English, because the system's fallen back to the "C" locale. apt should also properly ship an en_US language catalog. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apt 1.5.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Jan 29 08:31:38 2018 InstallationDate: Installed on 2017-04-27 (276 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: apt UpgradeStatus: Upgraded to artful on 2018-01-29 (0 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1746015 Title: Apt and apt-get do not ship a us_EN language catalog Status in apt package in Ubuntu: New Bug description: Description:Ubuntu 17.10 Release:17.10 If you install anthy with additional languages, with "US English" as your primary language, you end up with a "locale" output similar to the following: $ locale LANG=en_US.UTF-8 LANGUAGE=en_US:de:ja LC_CTYPE="en_US.UTF-8" LC_NUMERIC=en_GB.UTF-8 LC_TIME=en_GB.UTF-8 LC_COLLATE=C LC_MONETARY=en_US.UTF-8 LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= The LANGUAGE variable in this case is using the rules from https://www.gnu.org/software/gettext/manual/html_node/The-LANGUAGE- variable.html When running "aptitude" or "apt-get" or "apt install", the messages that come back are in German. If you strace those commands, you'll see apt trying to search for an en_US or en catalog, finding none, and falling down to the 2nd language in the list: "de" or German. If you run: $ LANGUAGE="" apt-get update Then the messages come back in English, because the system's fallen back to the "C" locale. apt should also properly ship an en_US language catalog. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apt 1.5.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Mon Jan 29 08:31:38 2018 InstallationDate: Installed on 2017-04-27 (276 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: apt UpgradeStatus: Upgraded to artful on 2018-01-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1746015/+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 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
About "click-apparmor" bionic/armhf regression.
# Excuses... page
autopkgtest for click-apparmor/0.3.18: amd64: Pass, arm64: Pass, armhf:
Regression ♻ , i386: Pass, ppc64el: Ignored failure, s390x: Always failed
After a discussion with security team and xnox. They are actively trying
to remove this package from the archive, but it depends on things still
at the moment. It was only used on touch which is RIP.
This regression can safely be ignore.
Regards,
Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
Status in AppArmor:
Fix Committed
Status in AppArmor 2.11 series:
Fix Committed
Status in apparmor package in Ubuntu:
Fix Committed
Status in apparmor source package in Trusty:
New
Status in apparmor source package in Xenial:
New
Status in apparmor source package in Artful:
New
Status in apparmor source package in Bionic:
Fix Committed
Status in apparmor package in Debian:
Fix Released
Bug description:
[Impact]
If PID is larger than 6 digits apparmor denies process which only
affect 64-bit systems[1] where the PID_MAX_LIMIT can be generated up
to 7 digits at the maximum.
This fix is committed, but not released. so all supporting version are
affected.
[1] - man 5 proc
--
/proc/sys/kernel/pid_max (since Linux 2.5.34)
This file specifies the value at which PIDs wrap around (i.e., the value in
this file is one greater than the maximum PID). PIDs greater than this value
are not allocated; thus, the value in this file also acts as a system-wide
limit on the total number of processes and threads. The default value for this
file, 32768, results in the same range of PIDs as on ear‐lier kernels. On
32-bit platforms, 32768 is the maximum value for pid_max. On 64-bit systems,
pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4
million).
--
[Test Case]
1. making pid over 6 digits
#!/bin/bash
for i in {1..100}
do
touch t
done
2. snap install --dangerous core_16-2.29.4.2_amd64.snap ( snap core
16-2.30 avoids using /proc/PID/cmdline, so need to use older version
3. you can see DENIED msgs in syslog
4. change /etc/apparmor.d/tunables/kernelvars
5. service apparmor restart
6. service snapd restart
7. DENIED is gone
This is one way, can't reproduce this issue again even if you change
back to original kernelvars, and restart snapd
OR
instead of Seyeong's touch approach, things can be manually change to
7 digits range via sysctl as long as the values are below
approximately 4 millions :
Example:
$ sysctl -w kernel.pid_max=300
$ sysctl -w kernel.ns_last_pid=100
[Regression]
* This is a minor/trivial fix which changes the pid regex only, allowing 7
digits PID instead of only 6 digits PID, we don't think there is any potential
regression.
* If a regression arise, which we highly doubt, one can quickly revert
the change manually and restart the service by modifying
"/etc/apparmor.d/tunables/kernelvars" file to its original state
(before this SRU).
[Others]
* Upstream commit:
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886732
* commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
Author: Vincas Dargis
Date: Sat Sep 30 15:28:15 2017 +0300
Allow seven digit pid
* Affecting releases : TXZAB
--
$ git describe --contains 630cb2a9
v2.11.95~5^2
$ rmadison apparmor
apparmor | 2.8.95~2430-0ubuntu5 | trusty
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
apparmor | 2.10.95-0ubuntu2 | xenial
apparmor | 2.10.95-0ubuntu2.6 | xenial-security
apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
apparmor | 2.11.0-2ubuntu4| zesty
apparmor | 2.11.0-2ubuntu17 | artful
apparmor | 2.11.0-2ubuntu18 | bionic
$ rmadison -u debian apparmor
apparmor | 2.11.1-4 | unstable
--
[Original Description]
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.
@{pid} is defined in /etc/apparmor.d/tunables:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9
[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
About the "snapd/2.29.4.2+18.04" bionic/ppc64el regression.
# Excuses... page
autopkgtest for snapd/2.29.4.2+18.04: amd64: Ignored failure, arm64: Always
failed, armhf: Pass, i386: Pass, ppc64el: Regression ♻ , s390x: Ignored failure
# Justification of the regression provided by mvo :
the first error 2018-01-29 00:22:55 Error executing
autopkgtest:ubuntu-18.04-ppc64el:tests/main/searching : is a store change
our integration test fails because the snap store changed
so just ignore
I suspect the other ones are similar
so please ask the sru team to ignore this error. with 2.31 (schedule in
~2weeks) the tests will be good again
until the store comes along and breaks us again :/
*if* its important to the sru team I can do an upload with just this one
test fixed
but I think its a bit overkill
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
Status in AppArmor:
Fix Committed
Status in AppArmor 2.11 series:
Fix Committed
Status in apparmor package in Ubuntu:
Fix Committed
Status in apparmor source package in Trusty:
New
Status in apparmor source package in Xenial:
New
Status in apparmor source package in Artful:
New
Status in apparmor source package in Bionic:
Fix Committed
Status in apparmor package in Debian:
Fix Released
Bug description:
[Impact]
If PID is larger than 6 digits apparmor denies process which only
affect 64-bit systems[1] where the PID_MAX_LIMIT can be generated up
to 7 digits at the maximum.
This fix is committed, but not released. so all supporting version are
affected.
[1] - man 5 proc
--
/proc/sys/kernel/pid_max (since Linux 2.5.34)
This file specifies the value at which PIDs wrap around (i.e., the value in
this file is one greater than the maximum PID). PIDs greater than this value
are not allocated; thus, the value in this file also acts as a system-wide
limit on the total number of processes and threads. The default value for this
file, 32768, results in the same range of PIDs as on ear‐lier kernels. On
32-bit platforms, 32768 is the maximum value for pid_max. On 64-bit systems,
pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4
million).
--
[Test Case]
1. making pid over 6 digits
#!/bin/bash
for i in {1..100}
do
touch t
done
2. snap install --dangerous core_16-2.29.4.2_amd64.snap ( snap core
16-2.30 avoids using /proc/PID/cmdline, so need to use older version
3. you can see DENIED msgs in syslog
4. change /etc/apparmor.d/tunables/kernelvars
5. service apparmor restart
6. service snapd restart
7. DENIED is gone
This is one way, can't reproduce this issue again even if you change
back to original kernelvars, and restart snapd
OR
instead of Seyeong's touch approach, things can be manually change to
7 digits range via sysctl as long as the values are below
approximately 4 millions :
Example:
$ sysctl -w kernel.pid_max=300
$ sysctl -w kernel.ns_last_pid=100
[Regression]
* This is a minor/trivial fix which changes the pid regex only, allowing 7
digits PID instead of only 6 digits PID, we don't think there is any potential
regression.
* If a regression arise, which we highly doubt, one can quickly revert
the change manually and restart the service by modifying
"/etc/apparmor.d/tunables/kernelvars" file to its original state
(before this SRU).
[Others]
* Upstream commit:
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886732
* commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
Author: Vincas Dargis
Date: Sat Sep 30 15:28:15 2017 +0300
Allow seven digit pid
* Affecting releases : TXZAB
--
$ git describe --contains 630cb2a9
v2.11.95~5^2
$ rmadison apparmor
apparmor | 2.8.95~2430-0ubuntu5 | trusty
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
apparmor | 2.10.95-0ubuntu2 | xenial
apparmor | 2.10.95-0ubuntu2.6 | xenial-security
apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
apparmor | 2.11.0-2ubuntu4| zesty
apparmor | 2.11.0-2ubuntu17 | artful
apparmor | 2.11.0-2ubuntu18 | bionic
$ rmadison -u debian apparmor
apparmor | 2.11.1-4 | unstable
--
[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
About the "snapd/2.29.4.2+18.04" bionic/ppc64el regression.
# Excuses... page
autopkgtest for snapd/2.29.4.2+18.04: amd64: Ignored failure, arm64: Always
failed, armhf: Pass, i386: Pass, ppc64el: Regression ♻ , s390x: Ignored failure
# Justification of the regression provided by mvo :
the first error 2018-01-29 00:22:55 Error executing
autopkgtest:ubuntu-18.04-ppc64el:tests/main/searching : is a store change
our integration test fails because the snap store changed
so just ignore
I suspect the other ones are similar
so please ask the sru team to ignore this error. with 2.31 (schedule in
~2weeks) the tests will be good again
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
Status in AppArmor:
Fix Committed
Status in AppArmor 2.11 series:
Fix Committed
Status in apparmor package in Ubuntu:
Fix Committed
Status in apparmor source package in Trusty:
New
Status in apparmor source package in Xenial:
New
Status in apparmor source package in Artful:
New
Status in apparmor source package in Bionic:
Fix Committed
Status in apparmor package in Debian:
Fix Released
Bug description:
[Impact]
If PID is larger than 6 digits apparmor denies process which only
affect 64-bit systems[1] where the PID_MAX_LIMIT can be generated up
to 7 digits at the maximum.
This fix is committed, but not released. so all supporting version are
affected.
[1] - man 5 proc
--
/proc/sys/kernel/pid_max (since Linux 2.5.34)
This file specifies the value at which PIDs wrap around (i.e., the value in
this file is one greater than the maximum PID). PIDs greater than this value
are not allocated; thus, the value in this file also acts as a system-wide
limit on the total number of processes and threads. The default value for this
file, 32768, results in the same range of PIDs as on ear‐lier kernels. On
32-bit platforms, 32768 is the maximum value for pid_max. On 64-bit systems,
pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4
million).
--
[Test Case]
1. making pid over 6 digits
#!/bin/bash
for i in {1..100}
do
touch t
done
2. snap install --dangerous core_16-2.29.4.2_amd64.snap ( snap core
16-2.30 avoids using /proc/PID/cmdline, so need to use older version
3. you can see DENIED msgs in syslog
4. change /etc/apparmor.d/tunables/kernelvars
5. service apparmor restart
6. service snapd restart
7. DENIED is gone
This is one way, can't reproduce this issue again even if you change
back to original kernelvars, and restart snapd
OR
instead of Seyeong's touch approach, things can be manually change to
7 digits range via sysctl as long as the values are below
approximately 4 millions :
Example:
$ sysctl -w kernel.pid_max=300
$ sysctl -w kernel.ns_last_pid=100
[Regression]
* This is a minor/trivial fix which changes the pid regex only, allowing 7
digits PID instead of only 6 digits PID, we don't think there is any potential
regression.
* If a regression arise, which we highly doubt, one can quickly revert
the change manually and restart the service by modifying
"/etc/apparmor.d/tunables/kernelvars" file to its original state
(before this SRU).
[Others]
* Upstream commit:
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722
* Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886732
* commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
Author: Vincas Dargis
Date: Sat Sep 30 15:28:15 2017 +0300
Allow seven digit pid
* Affecting releases : TXZAB
--
$ git describe --contains 630cb2a9
v2.11.95~5^2
$ rmadison apparmor
apparmor | 2.8.95~2430-0ubuntu5 | trusty
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
apparmor | 2.10.95-0ubuntu2 | xenial
apparmor | 2.10.95-0ubuntu2.6 | xenial-security
apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
apparmor | 2.11.0-2ubuntu4| zesty
apparmor | 2.11.0-2ubuntu17 | artful
apparmor | 2.11.0-2ubuntu18 | bionic
$ rmadison -u debian apparmor
apparmor | 2.11.1-4 | unstable
--
[Original Description]
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing
[Touch-packages] [Bug 1744328] Re: libfreebl3.so should be public, not in the nss subdir
Whatever we do, there is one in proposed for a while already which
blocks on autopkgtest of 389-ds-base.
That needs to be resolved anyway.
It makes way too much assumptions of the network:
3 # hack for lxc
4 IP=`ip route get 1.1.1.1 | sed -n -e's/.*src //; s/ .*//; p; q'`
5 HOSTNAME=`cat /etc/hosts| grep '127.0.1.1' | awk '{print $NF; exit}'`
6
7 echo "$IP $HOSTNAME.debci $HOSTNAME" >> /etc/hosts
For now we need to mark this as a bad-test to be able to fix nss and get
something migrating.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1744328
Title:
libfreebl3.so should be public, not in the nss subdir
Status in nss package in Ubuntu:
New
Bug description:
Hi,
I tried to move the chrony dependency from tomcrypt to libnss to avoid
universe dependencies.
While doing so I found that libfreebl3 is not "normally" linkable being
outside the normal ld paths.
E.g. sample program
#include
#include
#include
int main(int argc, char **argv) {
NSSLOWHASH_Begin(NSSLOWHASH_NewContext(NSSLOW_Init(), HASH_AlgSHA512));
return 0;
}
Build:
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-Wmissing-prototypes -Wall -pthread -Wdate-time -D_FORTIFY_SOURCE=2
-I/usr/include/nss -I/usr/include/nspr -o docheck docheck.c -lfreebl3
-Wl,-Bsymbolic-functions -Wl,-z,relro -v -Wl,-v -L/usr/lib/x86_64-linux-gnu/nss
Then:
ldd docheck
will give you
libfreebl3.so => not found
Obviously a link into /usr/lib/x86_64-linux-gnu/ fixes the issue but
needs some more consideration if that is the thing we want (there
might be a reason it is where it is).
Note: Required to go on with the chrony MIR which is rather urgent to
be sorted out as it has a lot of other dependencies that need to be
adapted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1744328/+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 1744328] Re: libfreebl3.so should be public, not in the nss subdir
All archs fail like
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-bionic/bionic/amd64/3/389-ds-
base/20171221_085018_38cf2@/log.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1744328
Title:
libfreebl3.so should be public, not in the nss subdir
Status in nss package in Ubuntu:
New
Bug description:
Hi,
I tried to move the chrony dependency from tomcrypt to libnss to avoid
universe dependencies.
While doing so I found that libfreebl3 is not "normally" linkable being
outside the normal ld paths.
E.g. sample program
#include
#include
#include
int main(int argc, char **argv) {
NSSLOWHASH_Begin(NSSLOWHASH_NewContext(NSSLOW_Init(), HASH_AlgSHA512));
return 0;
}
Build:
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-Wmissing-prototypes -Wall -pthread -Wdate-time -D_FORTIFY_SOURCE=2
-I/usr/include/nss -I/usr/include/nspr -o docheck docheck.c -lfreebl3
-Wl,-Bsymbolic-functions -Wl,-z,relro -v -Wl,-v -L/usr/lib/x86_64-linux-gnu/nss
Then:
ldd docheck
will give you
libfreebl3.so => not found
Obviously a link into /usr/lib/x86_64-linux-gnu/ fixes the issue but
needs some more consideration if that is the thing we want (there
might be a reason it is where it is).
Note: Required to go on with the chrony MIR which is rather urgent to
be sorted out as it has a lot of other dependencies that need to be
adapted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1744328/+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 1728077] Re: Evince uses wrong encoding when filling out a PDF form
** Tags added: artful xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1728077
Title:
Evince uses wrong encoding when filling out a PDF form
Status in Poppler:
Confirmed
Status in poppler package in Ubuntu:
New
Bug description:
Evince uses the wrong encoding when filling out a PDF form.
How to reproduce:
- Get the official Chinese Visa Application Form from
http://www.china-embassy.org/eng/visas/fd/W020130830801798289342.pdf
- Open it in Evince
- Fill in a name (e.g. "Smith"). The entered text is displayed correctly.
- Click into another filed
- The previously entered name is displayed in wrong characters (wrong
encoding used?). E.g. "Smith" becomes "4NJUI".
- Saving and loading the PDF (with the entered text) also results in
displaying wrong characters
- Clicking into the name filed results in displaying the correct name
("Smith")
=> It seems that somewhere in Evince (or libpoppler?) the wrong
encoding is used for displaying non-active input fields.
Tested Ubuntu versions:
- Ubuntu 16.04
- Ubuntu 17.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1728077/+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 1727237] Re: systemd-resolved is not finding a domain
@ #19: Mathieu, I included the '234-2ubuntu12.3~mtrudel1' from the ppa you mention to my computer. Unfortunately no change in behavior. I am still not forwarded to the captive portal after connecting to this particular wifi. Do you have a suggestion what I could try? @ #20: Does this: 'but it doesn't look like it helps.' mean that the new systemd does not fix the bug and therefore it does not work on my side? Axel -- 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/1727237 Title: systemd-resolved is not finding a domain Status in systemd package in Ubuntu: Triaged Status in systemd source package in Xenial: Triaged Status in systemd source package in Zesty: Won't Fix Status in systemd source package in Artful: Triaged Status in systemd source package in Bionic: Triaged Bug description: I have an odd network situation that I have so far managed to narrow down to the inability to resolve a domain via systemd-resolved which is resolvable with nslookup. If I use nslookup against the two nameservers on this network I get answers for the domain, but ping says it is unable to resolve the same domain (as do browsers and crucially the captive portal mechanism). Here are details: NSLOOKUP: ~$ nslookup securelogin.arubanetworks.com 208.67.220.220 Server: 208.67.220.220 Address: 208.67.220.220#53 Non-authoritative answer: Name: securelogin.arubanetworks.com Address: 172.22.240.242 ~$ nslookup securelogin.arubanetworks.com 208.67.222.222 Server: 208.67.222.222 Address: 208.67.222.222#53 Non-authoritative answer: Name: securelogin.arubanetworks.com Address: 172.22.240.242 PING: ~$ ping securelogin.arubanetworks.com ping: securelogin.arubanetworks.com: Name or service not known mark@mark-X1Y2:~$ DIG: ~$ dig @208.67.222.222 securelogin.arubanetworks.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;securelogin.arubanetworks.com. IN A ;; AUTHORITY SECTION: arubanetworks.com.1991IN SOA dns5.arubanetworks.com. hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400 ;; Query time: 34 msec ;; SERVER: 208.67.222.222#53(208.67.222.222) ;; WHEN: Wed Oct 25 10:31:10 CEST 2017 ;; MSG SIZE rcvd: 144 MORE DIG: ~$ dig securelogin.arubanetworks.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;securelogin.arubanetworks.com. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Oct 25 10:34:01 CEST 2017 ;; MSG SIZE rcvd: 58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237/+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 1726395] Re: gnome-screensaver should be removed from ubuntu-desktop Recommends because it isn't needed for Gnome Shell DE
** Branch linked: lp:~ubuntu-core-dev/ubuntu-seeds/ubuntu.bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1726395 Title: gnome-screensaver should be removed from ubuntu-desktop Recommends because it isn't needed for Gnome Shell DE Status in ubuntu-meta package in Ubuntu: In Progress Bug description: gnome-screensaver should be removed from ubuntu-desktop Recommends because it isn't needed for Gnome Shell Desktop Environment. It's 5 years old software (latest release 2012-10-16) and is needed only for old GNOME flashback (fallback) session. Gnome-screensaver shouldn't be running on GNOME Shell - users can't unlock the screen because of important bugs in gnome-screensaver, see bug #1716278 and bug #1699670 (Gnome screensaver lock always responses "incorrect password" when last active window's language is not the language of the password) for example. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1726395/+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 1726395] Re: gnome-screensaver should be removed from ubuntu-desktop Recommends because it isn't needed for Gnome Shell DE
** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1726395 Title: gnome-screensaver should be removed from ubuntu-desktop Recommends because it isn't needed for Gnome Shell DE Status in ubuntu-meta package in Ubuntu: In Progress Bug description: gnome-screensaver should be removed from ubuntu-desktop Recommends because it isn't needed for Gnome Shell Desktop Environment. It's 5 years old software (latest release 2012-10-16) and is needed only for old GNOME flashback (fallback) session. Gnome-screensaver shouldn't be running on GNOME Shell - users can't unlock the screen because of important bugs in gnome-screensaver, see bug #1716278 and bug #1699670 (Gnome screensaver lock always responses "incorrect password" when last active window's language is not the language of the password) for example. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1726395/+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 1738582] Re: [MIR] ibus-libpinyin and dependencies
The new versions of both ibus-libpinyin and libpinyin have now migrated
to bionic-release.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libpinyin in Ubuntu.
https://bugs.launchpad.net/bugs/1738582
Title:
[MIR] ibus-libpinyin and dependencies
Status in ibus-libpinyin package in Ubuntu:
New
Status in libpinyin package in Ubuntu:
New
Bug description:
Please include these packages in Ubuntu's component main:
* ibus-libpinyin
* libpinyin (the ibus-libpinyin binary depends on libpinyin7)
As has been discussed at bug #1735362 we would like to replace ibus-
sunpinyin with ibus-libpinyin ("Intelligent Pinyin") in the live seed
and as the default input method for typing Simplified Chinese. Reasons
for the switch are:
- ibus-libpinyin is better maintained
- ibus-libpinyin is built with and depends on Python3
(not yet in Debian: https://bugs.debian.org/883631)
- ibus-libpinyin is default input method in GNOME
Bugs ibus-libpinyin
---
https://github.com/libpinyin/ibus-libpinyin/issues
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=ibus-libpinyin
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin
Bugs libpinyin
--
https://github.com/libpinyin/libpinyin/issues
(no open Debian or Ubuntu bugs)
I have read https://wiki.ubuntu.com/UbuntuMainInclusionRequirements, and
haven't found any issues that would prevent the proposed main inclusion.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1738582/+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 1732030] Re: 'apt update' dies with seccomp error
@Turi with the same number 78? That's important :)
--
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/1732030
Title:
'apt update' dies with seccomp error
Status in apt package in Ubuntu:
Confirmed
Status in libvirt package in Ubuntu:
Triaged
Bug description:
$ apt-get update
0% [Working]
Seccomp prevented execution of syscall 78 on architecture amd64
Reading package lists... Done
E: Method mirror has died unexpectedly!
E: Sub-process mirror returned an error code (31)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apt 1.6~alpha5
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu4
Architecture: amd64
Date: Mon Nov 13 23:10:57 2017
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/zsh
SourcePackage: apt
UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1732030/+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 1735362] Re: Replace ibus-sunpinyin with ibus-libpinyin
** Changed in: libpinyin (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1735362 Title: Replace ibus-sunpinyin with ibus-libpinyin Status in Ubuntu Seeds: New Status in fcitx-libpinyin package in Ubuntu: Fix Released Status in ibus-libpinyin package in Ubuntu: Fix Released Status in ibus-libzhuyin package in Ubuntu: Fix Released Status in ibus-sunpinyin package in Ubuntu: New Status in language-selector package in Ubuntu: New Status in libpinyin package in Ubuntu: Fix Released Status in ibus-libpinyin package in Debian: New Status in ibus-sunpinyin package in Debian: New Bug description: ibus-sunpinyin: port to Python3 needed. Currently in the live seed, package owned by desktop-packages. Considering the lack of upstream maintenance, demotion might be an option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1735362/+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 1161239] Re: [7505, Conexant CX20590, Mic, Internal] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-driver (Ubuntu)
Status: New => Confirmed
--
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/1161239
Title:
[7505, Conexant CX20590, Mic, Internal] No sound at all
Status in alsa-driver package in Ubuntu:
Confirmed
Bug description:
mic dosn't work lenovo n581. neither pulse-audio, nor alsa . im have
been using n581 3 month, appling several ubuntu upgrades, no result
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.2.0-39.62-generic 3.2.39
Uname: Linux 3.2.0-39-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: lm 2089 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xe061 irq 44'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:14f1506e,17aac033,0013
HDA:80862806,80860101,0010'
Controls : 15
Simple ctrls : 7
Date: Thu Mar 28 08:06:23 2013
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64
(20120823.1)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
2089 lmF pulseaudio
PID ACCESS COMMAND
Symptom_Jack: Mic, Internal
Symptom_Type: No sound at all
Title: [7505, Conexant CX20590, Mic, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/22/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 5ECN40WW(V3.06)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Product Name
dmi.board.vendor: LENOVO
dmi.board.version: Mainboard version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad N581
dmi.modalias:
dmi:bvnLENOVO:bvr5ECN40WW(V3.06):bd10/22/2012:svnLENOVO:pn7505:pvrLenovoIdeaPadN581:rvnLENOVO:rnProductName:rvrMainboardversion:cvnLENOVO:ct10:cvrLenovoIdeaPadN581:
dmi.product.name: 7505
dmi.product.version: Lenovo IdeaPad N581
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1161239/+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 1735362] Re: Replace ibus-sunpinyin with ibus-libpinyin
This bug was fixed in the package ibus-libpinyin - 1.9.2-1~exp1ubuntu1 --- ibus-libpinyin (1.9.2-1~exp1ubuntu1) bionic; urgency=medium * Build with Python3 instead of Python2 (Closes: #883631) * Add python3-gi to depends (Closes: #785070) * Build with liblua5.3-dev instead of liblua5.1-dev (LP: #1735362) (Closes: #884734) ibus-libpinyin (1.9.2-1~exp1) experimental; urgency=medium * New upstream release. * Bump Standards-Version to 4.1.0. * Bump compat to 10. * Update Vcs-* fields. -- Gunnar Hjalmarsson Mon, 22 Jan 2018 16:06:00 +0100 ** Changed in: ibus-libpinyin (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1735362 Title: Replace ibus-sunpinyin with ibus-libpinyin Status in Ubuntu Seeds: New Status in fcitx-libpinyin package in Ubuntu: Fix Released Status in ibus-libpinyin package in Ubuntu: Fix Released Status in ibus-libzhuyin package in Ubuntu: Fix Released Status in ibus-sunpinyin package in Ubuntu: New Status in language-selector package in Ubuntu: New Status in libpinyin package in Ubuntu: In Progress Status in ibus-libpinyin package in Debian: New Status in ibus-sunpinyin package in Debian: New Bug description: ibus-sunpinyin: port to Python3 needed. Currently in the live seed, package owned by desktop-packages. Considering the lack of upstream maintenance, demotion might be an option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1735362/+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 400573] Re: [include in live-cd] wvdial (1.60.1+nmu2)
Have things improved since? These days, I find that Mifi dongles are popular and that most mobile phones are able to tether internet via Bluetooth, USB, or direct Wi-Fi connection. I also found that network-manager applet was sufficient enough to connect to the internet for me. Currently, I do not believe that we have enough developers who rely on such an internet connection, and thus we cannot adequately support this package and I would like to propose to move this package back into the universe. Regards, Dimitri. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/400573 Title: [include in live-cd] wvdial (1.60.1+nmu2) Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: Mobile broadband is a happening thing these days...i find the Gnome NetworkManager Applet incompetent at properly configuring my connections ..maybe it needs a bit of tweaking..i m in INdia and Many mobile broadband connection on many networks like AIrcel,AirTel,Idea wont work even though it shows connection established...There is no data transfer across the established network..so i installed wvdial and everything was a breeze..it was there preinstalled ON hardy disc but not on Jaunty so i request you to kindly include it this time.I dont know how to configure pppd config files i would rather use the intelligent weave dialer..I believe many novices users like me will feel the same.Thanking you in anticipation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/400573/+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 1721092] Re: systemd-resolved and dns-masq make CPU 100% when using lxc name resolution
Hello, I tried to get DNS packets using : $ sudo tcpdump -i lxcbr0 -l -vvv dst host 10.0.3.1 and dst port 53 |tee /tmp/tcpdump-dns I then wait until systemd-resolved ate 100% of CPU. But at this time (unfortunately when I noticed it, it may have been eaten CPU for quite a while). However I can't see any strange exchange between systemd- resolved and dnsmasq. I attach all the packets captured by tcpdump. I'm not an expert in networks topics but I'm at ease with linux and cli commands, so feel free to tell me which experiment you would like me to run. ** Attachment added: "tcpdump session between dnsmasq and systemd-resolved" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721092/+attachment/5044944/+files/tcpdump-dns -- 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/1721092 Title: systemd-resolved and dns-masq make CPU 100% when using lxc name resolution Status in systemd package in Ubuntu: Triaged Bug description: This bug may be a duplicate of https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1688364 but I'm not sure, hence this new entry. It hits while I wanted systemd to resolve the lxc domain to my internal lxc hosts. Step to (maybe) reproduce: - having lxc installed - make some user space lxc container - uncomment the line LXC_DOMAIN="lxc" in /etc/default/lxc-net - restart lxc-net service Now the dnsmasq on 10.0.3.1 should be a dns resolving lxc names. - add a file /etc/systemd/resolved.conf.d/lxc.conf [Resolve] DNS=10.0.3.1 Domains=~.lxc DNSSEC=false - restart systemd-resolved service Now systemd knows it should ask .lxc names to dnsmasq - start an lxc container, let assume it's called my-container - ping it using my-container.lxc it should work After some times, systemd-resolved should use 100% CPU. Commenting the /etc/systemd/resolved.conf.d/lxc.conf file and restarting it makes systemd-resolved never eating resources again. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-21ubuntu5 Uname: Linux 4.10.16-041016-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Oct 3 18:18:56 2017 InstallationDate: Installed on 2015-11-10 (692 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Intel Corporation Skylake Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.16-041016-generic root=UUID=6814e3c1-8cea-4ecc-964d-535fd18782e9 ro quiet splash crashkernel=384M-:128M vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to zesty on 2017-02-25 (219 days ago) dmi.bios.date: 11/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: WhiteTip Mountain1 Fab2 dmi.board.vendor: Topstar dmi.board.version: RVP7 dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd11/06/2015:svnIntelCorporation:pnSkylakePlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.name: Skylake Platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721092/+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 1740441] Re: Tag borders in search bar looks halfway
updated, I'll open a new title for other bugs. ** Summary changed: - Nautilus infobar, searchbar & notification dialog issue with Ambiance + Tag borders in search bar looks halfway ** Description changed: + ubuntu 17.10 - 1.There is no background in the Nautilus file Information Bar. ( In - inactive windows ) + Nautilus search bar - preview : https://i.hizliresim.com/0GY5nY.png - - 2.Notification window looks strange in apps. - - previews - - nautilus : https://i.hizliresim.com/OyGXMn.png - - Appstore : https://i.hizliresim.com/4GEJr7.png - - 3. EOG Zoom Element white background ( I'm not sure it's bug, but I just - wanted to mention it. ) - - preview : https://i.hizliresim.com/JO0gA5.png - - 4. more in search bar - - preview :https://i.hizliresim.com/rJWBP7.png + SS: https://i.hizliresim.com/rJWBP7.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1740441 Title: Tag borders in search bar looks halfway Status in Ubuntu theme: Incomplete Status in ubuntu-themes package in Ubuntu: Incomplete Bug description: ubuntu 17.10 Nautilus search bar SS: https://i.hizliresim.com/rJWBP7.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1740441/+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 1743710] Re: Since 2018 text in combo boxes is dark and unreadable
"Daniel van Vugt (vanvugt) wrote 5 hours ago: #16 I can reproduce the bug in 16.04 using LibreOffice, same as your screenshots show. But I can't seem to reproduce the bug in Firefox, Thunderbird or GIMP that you mention. Can you provide screenshots of those with the bug?" Firefox and Thunderbird were fine with me, too (black menu background but clearly visible white menu items), as I said in my first entry. All other programs seem to be affected, however, LibreOffice, Gimp, Pinta, Tupi, you name it. Sorry, I am running presently without the folder /gtk-2.0/, see my https://bugs.launchpad.net/ubuntu/+source/ubuntu- themes/+bug/1743710/comments/15, so I cannot show you the Gimp issue. But it looked exactly like LibreOffice. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1743710 Title: Since 2018 text in combo boxes is dark and unreadable Status in Ubuntu theme: Triaged Status in ubuntu-themes package in Ubuntu: Triaged Bug description: Since 2018 all dropdown menus in my Ubuntu 16.04 LTS have a black background and the text, i.e., file-save-as options are unreadable. After a fresh install the menus are ok, but after the first necessary updates, same problem! The menus if firefox and thunderbird are readable, but e.g., Libreoffice writer, Gimp you name it, are not. I have described this in detail in https://ubuntuforums.org/showthread.php?t=2382505&p=13730458#post13730458 and also my workaround to solve it, changing the file /usr/share/themes/Ambiance/gtk-2.0/gtkrc But I am afraid, with the next bigger Ubuntu update the error will be back again? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1743710/+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
