[Touch-packages] [Bug 1836809] Re: segfault when CCD are present in two different HOG services
Noted! Anyway we already had installed the latest bluez version - 5.50. -- 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/1836809 Title: segfault when CCD are present in two different HOG services Status in Bluez Utilities: Unknown Status in bluez package in Ubuntu: New Bug description: Hello everyone, We are currently developing a device that contains two HID services. That device, as it is right now, is properly functioning on Windows & Android. However, when pairing the device on Linux running bluez 5.50 we do get segfaults (see attached files). Our bluetooth device has 4 services : 1 battery service, 2 HID Over Gatt services and 1 device information service. With trial and error, we managed to find that we wouldn't get any crash as long as only 1 HOG service was present. Here's the interesting part. The two HOG services are made as follows: - standard keyboard over gatt: protocole mode / report map / 1 INPUT report / boot INPUT + OUTPUT / HID information / HID Control point - raw HID over gatt : report map / 1 INPUT report / 1 OUTPUT report / HID information / HID control point Looking at the write_ccc in the call stacks we wondered if the callbacks subscribing to notifications for the INPUT reports were causing this issue. We therefore changed the raw HID over gatt (and its report map) to remove the INPUT report and change it into 1 OUTPUT report (leading to 2 OUTPUT reports): no crash. We therefore hypothesize that the segfault occurs when subscribing to notification on a second HOG service... To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1836809/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824986] Re: twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)
Yes, this does help. Thank you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1824986 Title: twinkle doesn't start (stack smashing detected) (Lubuntu 18.04) Status in qtdeclarative-opensource-src package in Ubuntu: New Status in twinkle package in Ubuntu: New Bug description: The console output: $ twinkle QApplication: invalid style override passed, ignoring it. Language name: "en" mprotect failed in ExecutableAllocator::makeExecutable: Permission denied *** stack smashing detected ***: terminated Aborted (core dumped) $ I've attached a strace output file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: twinkle 1:1.10.1+dfsg-3 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: LXDE Date: Tue Apr 16 15:29:30 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-11 (309 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: twinkle UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1824986/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836881] Re: Xorg freeze
If your "mouse works fine" then Xorg is still working and it's only gnome-shell that's frozen, so reassigning... ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Summary changed: - Xorg freeze + gnome-shell freeze -- 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/1836881 Title: gnome-shell freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: My gnome session freezes, mouse works fine but cannot start applications. I am able to enter one of the tty terminals and kill the session. This happens a few times a day and started a week ago probably. Douglas ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 17 12:29:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 4.15.0-52-generic, x86_64: installed nvidia, 418.56, 4.15.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1208] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Ti Mobile] [1025:1207] InstallationDate: Installed on 2018-01-13 (550 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. Bus 001 Device 003: ID 04ca:3016 Lite-On Technology Corp. Bus 001 Device 002: ID 0461:4e81 Primax Electronics, Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Predator PH317-51 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=455417ef-94fe-4ab8-97b7-0b992c951267 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Sienna_KLS dmi.board.vendor: KBL dmi.board.version: V1.05 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd05/18/2017:svnAcer:pnPredatorPH317-51:pvrV1.05:rvnKBL:rnSienna_KLS:rvrV1.05:cvnAcer:ct10:cvrV1.05: dmi.product.family: Predator Helios 300 dmi.product.name: Predator PH317-51 dmi.product.version: V1.05 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1836881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- 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/1836960 Title: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes Status in gnome-shell package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Description: I recently noticed a strange behavior on my (pretty vanilla) Ubuntu 18.04.2 LTS. Every time I copy some text from GNOME Terminal, using keyboard or mouse, it triggers a little hard drive activity. Intrigued, I decided to see what was going on (persistent clipboard data?). After some investigation, I found out that the activity is due to a file being written to whenever I do a copy in GNOME Terminal (or in other apps): ~/.config/nautilus/desktop-metadata The small file seems to record the nautilus view settings and the trash icon state, has no apparent relation to functions of the clipboard, and does not mutate following each write (the content stays unchanged). I also tested to see if the same happens on a different computer running 18.04.2 desktop live usb, and the answer is yes. So this shouldn't be something particular to my system. Steps to reproduce: * Boot your computer using live CD or usb created with: ubuntu-18.04.2-desktop-amd64.iso You can obtain it from: http://releases.ubuntu.com/18.04/ last modified: 2019-02-10 00:27 sha256: 22580b9f3b186cc66818e60f44c46f795d708a1ad86b9225c458413b638459c4) * Start Gnome Terminal, copy some text from there, and note the current time when you perform the copying * Check the timestamp of ~/.config/nautilus/desktop-metadata and observe it's been modified at the same time you did the copying * Repeat as many times as you like Expected behavior: Copying text in Gnome should not trigger writes to some arbitrary file (and should not trigger any disk IO at all). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1836960/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836809] Re: segfault when CCD are present in two different HOG services
Thanks. Please note Ubuntu 18.10 reaches end-of-life this month, so please upgrade to 19.04. ** Tags added: cosmic ** Bug watch added: Linux Kernel Bug Tracker #204201 https://bugzilla.kernel.org/show_bug.cgi?id=204201 ** Also affects: bluez via https://bugzilla.kernel.org/show_bug.cgi?id=204201 Importance: Unknown Status: Unknown ** Changed in: bluez (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1836809 Title: segfault when CCD are present in two different HOG services Status in Bluez Utilities: Unknown Status in bluez package in Ubuntu: New Bug description: Hello everyone, We are currently developing a device that contains two HID services. That device, as it is right now, is properly functioning on Windows & Android. However, when pairing the device on Linux running bluez 5.50 we do get segfaults (see attached files). Our bluetooth device has 4 services : 1 battery service, 2 HID Over Gatt services and 1 device information service. With trial and error, we managed to find that we wouldn't get any crash as long as only 1 HOG service was present. Here's the interesting part. The two HOG services are made as follows: - standard keyboard over gatt: protocole mode / report map / 1 INPUT report / boot INPUT + OUTPUT / HID information / HID Control point - raw HID over gatt : report map / 1 INPUT report / 1 OUTPUT report / HID information / HID control point Looking at the write_ccc in the call stacks we wondered if the callbacks subscribing to notifications for the INPUT reports were causing this issue. We therefore changed the raw HID over gatt (and its report map) to remove the INPUT report and change it into 1 OUTPUT report (leading to 2 OUTPUT reports): no crash. We therefore hypothesize that the segfault occurs when subscribing to notification on a second HOG service... To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1836809/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/1836960 Title: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes Status in gnome-shell package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Description: I recently noticed a strange behavior on my (pretty vanilla) Ubuntu 18.04.2 LTS. Every time I copy some text from GNOME Terminal, using keyboard or mouse, it triggers a little hard drive activity. Intrigued, I decided to see what was going on (persistent clipboard data?). After some investigation, I found out that the activity is due to a file being written to whenever I do a copy in GNOME Terminal (or in other apps): ~/.config/nautilus/desktop-metadata The small file seems to record the nautilus view settings and the trash icon state, has no apparent relation to functions of the clipboard, and does not mutate following each write (the content stays unchanged). I also tested to see if the same happens on a different computer running 18.04.2 desktop live usb, and the answer is yes. So this shouldn't be something particular to my system. Steps to reproduce: * Boot your computer using live CD or usb created with: ubuntu-18.04.2-desktop-amd64.iso You can obtain it from: http://releases.ubuntu.com/18.04/ last modified: 2019-02-10 00:27 sha256: 22580b9f3b186cc66818e60f44c46f795d708a1ad86b9225c458413b638459c4) * Start Gnome Terminal, copy some text from there, and note the current time when you perform the copying * Check the timestamp of ~/.config/nautilus/desktop-metadata and observe it's been modified at the same time you did the copying * Repeat as many times as you like Expected behavior: Copying text in Gnome should not trigger writes to some arbitrary file (and should not trigger any disk IO at all). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1836960/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1836960 Title: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes Status in gnome-shell package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Description: I recently noticed a strange behavior on my (pretty vanilla) Ubuntu 18.04.2 LTS. Every time I copy some text from GNOME Terminal, using keyboard or mouse, it triggers a little hard drive activity. Intrigued, I decided to see what was going on (persistent clipboard data?). After some investigation, I found out that the activity is due to a file being written to whenever I do a copy in GNOME Terminal (or in other apps): ~/.config/nautilus/desktop-metadata The small file seems to record the nautilus view settings and the trash icon state, has no apparent relation to functions of the clipboard, and does not mutate following each write (the content stays unchanged). I also tested to see if the same happens on a different computer running 18.04.2 desktop live usb, and the answer is yes. So this shouldn't be something particular to my system. Steps to reproduce: * Boot your computer using live CD or usb created with: ubuntu-18.04.2-desktop-amd64.iso You can obtain it from: http://releases.ubuntu.com/18.04/ last modified: 2019-02-10 00:27 sha256: 22580b9f3b186cc66818e60f44c46f795d708a1ad86b9225c458413b638459c4) * Start Gnome Terminal, copy some text from there, and note the current time when you perform the copying * Check the timestamp of ~/.config/nautilus/desktop-metadata and observe it's been modified at the same time you did the copying * Repeat as many times as you like Expected behavior: Copying text in Gnome should not trigger writes to some arbitrary file (and should not trigger any disk IO at all). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1836960/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes
** No longer affects: ubuntu ** Tags added: performance -- 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/1836960 Title: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes Status in gnome-shell package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Description: I recently noticed a strange behavior on my (pretty vanilla) Ubuntu 18.04.2 LTS. Every time I copy some text from GNOME Terminal, using keyboard or mouse, it triggers a little hard drive activity. Intrigued, I decided to see what was going on (persistent clipboard data?). After some investigation, I found out that the activity is due to a file being written to whenever I do a copy in GNOME Terminal (or in other apps): ~/.config/nautilus/desktop-metadata The small file seems to record the nautilus view settings and the trash icon state, has no apparent relation to functions of the clipboard, and does not mutate following each write (the content stays unchanged). I also tested to see if the same happens on a different computer running 18.04.2 desktop live usb, and the answer is yes. So this shouldn't be something particular to my system. Steps to reproduce: * Boot your computer using live CD or usb created with: ubuntu-18.04.2-desktop-amd64.iso You can obtain it from: http://releases.ubuntu.com/18.04/ last modified: 2019-02-10 00:27 sha256: 22580b9f3b186cc66818e60f44c46f795d708a1ad86b9225c458413b638459c4) * Start Gnome Terminal, copy some text from there, and note the current time when you perform the copying * Check the timestamp of ~/.config/nautilus/desktop-metadata and observe it's been modified at the same time you did the copying * Repeat as many times as you like Expected behavior: Copying text in Gnome should not trigger writes to some arbitrary file (and should not trigger any disk IO at all). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1836960/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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/1836960 Title: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes Status in Ubuntu: New Status in gnome-shell package in Ubuntu: New Status in nautilus package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Description: I recently noticed a strange behavior on my (pretty vanilla) Ubuntu 18.04.2 LTS. Every time I copy some text from GNOME Terminal, using keyboard or mouse, it triggers a little hard drive activity. Intrigued, I decided to see what was going on (persistent clipboard data?). After some investigation, I found out that the activity is due to a file being written to whenever I do a copy in GNOME Terminal (or in other apps): ~/.config/nautilus/desktop-metadata The small file seems to record the nautilus view settings and the trash icon state, has no apparent relation to functions of the clipboard, and does not mutate following each write (the content stays unchanged). I also tested to see if the same happens on a different computer running 18.04.2 desktop live usb, and the answer is yes. So this shouldn't be something particular to my system. Steps to reproduce: * Boot your computer using live CD or usb created with: ubuntu-18.04.2-desktop-amd64.iso You can obtain it from: http://releases.ubuntu.com/18.04/ last modified: 2019-02-10 00:27 sha256: 22580b9f3b186cc66818e60f44c46f795d708a1ad86b9225c458413b638459c4) * Start Gnome Terminal, copy some text from there, and note the current time when you perform the copying * Check the timestamp of ~/.config/nautilus/desktop-metadata and observe it's been modified at the same time you did the copying * Repeat as many times as you like Expected behavior: Copying text in Gnome should not trigger writes to some arbitrary file (and should not trigger any disk IO at all). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1836960/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes
** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- 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/1836960 Title: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes Status in Ubuntu: New Status in gnome-shell package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Description: I recently noticed a strange behavior on my (pretty vanilla) Ubuntu 18.04.2 LTS. Every time I copy some text from GNOME Terminal, using keyboard or mouse, it triggers a little hard drive activity. Intrigued, I decided to see what was going on (persistent clipboard data?). After some investigation, I found out that the activity is due to a file being written to whenever I do a copy in GNOME Terminal (or in other apps): ~/.config/nautilus/desktop-metadata The small file seems to record the nautilus view settings and the trash icon state, has no apparent relation to functions of the clipboard, and does not mutate following each write (the content stays unchanged). I also tested to see if the same happens on a different computer running 18.04.2 desktop live usb, and the answer is yes. So this shouldn't be something particular to my system. Steps to reproduce: * Boot your computer using live CD or usb created with: ubuntu-18.04.2-desktop-amd64.iso You can obtain it from: http://releases.ubuntu.com/18.04/ last modified: 2019-02-10 00:27 sha256: 22580b9f3b186cc66818e60f44c46f795d708a1ad86b9225c458413b638459c4) * Start Gnome Terminal, copy some text from there, and note the current time when you perform the copying * Check the timestamp of ~/.config/nautilus/desktop-metadata and observe it's been modified at the same time you did the copying * Repeat as many times as you like Expected behavior: Copying text in Gnome should not trigger writes to some arbitrary file (and should not trigger any disk IO at all). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1836960/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668771] Re: systemd-resolved negative caching for extended period of time
The proposal to extend the 'cache' option with 'no-negative' has been merged upstream. I will proceed with the backports to Ubuntu on the affected LTS releases. [0] https://github.com/systemd/systemd/pull/13047 -- 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/1668771 Title: systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Bug description: 231-9ubuntu3 If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd-resolved to have the negative caching purged. After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836209] Re: network-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9
I am currently doing improvements on the test script, making them available here: https://code.launchpad.net/~till-kamppeter/network-manager/+git/network- manager/+merge/369586 I already added timrout s to the GLIb main loops so that in case of a failure here nm.py continues with the other tests and the log of the failure in the main loop does not get lost. If the main loops hang indefinitely, autopkgtest kills the script and no results are available. Next step is improving the script for events taking too long to happen. Especially things like waiting for a hard-coded time interval and then checking a state ones (and fail if the desired state did not get reached, in check_connected_device_config()) I will replace by repeated checking over a given time interval, like assertEventually() does). Probably I will also make certain timeouts longer. ** Changed in: network-manager (Ubuntu) Status: New => In Progress -- 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/1836209 Title: network-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9 Status in network-manager package in Ubuntu: In Progress Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/n/network-manager/20190710_160945_9116e@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/i386/n/network-manager/20190710_110735_e5ce3@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1836209/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787225] Re: systemctl disable apache2 does nothing
You can also check "sudo systemctl cat apache2.service", that will show if any overrides are in place. -- 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/1787225 Title: systemctl disable apache2 does nothing Status in apache2 package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: I installed apache2 on Ubuntu 16.04, and out of the box it was enabled as a service, meaning it would automatically start at every boot. That is not what I want as this is my personal computer, not a server. $ systemctl is-enabled apache2.service enabled So I ran: $ sudo systemctl disable apache2 and this was the output: apache2.service is not a native service, redirecting to systemd-sysv-install Executing /lib/systemd/systemd-sysv-install disable apache2 insserv: warning: current start runlevel(s) (empty) of script `apache2' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `apache2' overrides LSB defaults (0 1 6). insserv: warning: current start runlevel(s) (empty) of script `apache2' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `apache2' overrides LSB defaults (0 1 6). Then I rebooted. I expected to find apache2 not running. Instead, it was running. Surprisingly: $ systemctl is-enabled apache2.service apache2.service is not a native service, redirecting to systemd-sysv-install Executing /lib/systemd/systemd-sysv-install is-enabled apache2 disabled so, it shows up as disabled, yet it is started at startup. I wonder if this is what those warnings were about. Those messages are unclear as fuck, I have no f***ing clue what they are supposed to mean. I read that the CURRENT runlevel overrides a DEFAULT. I guess that should be fine, unless what systemctl actually changes are the defaults, and those are overwritten by something else, which means that "sysctl disable" will have no effect. If that is the case, then the warning should be more explicit: - be specific about the fact that "LSB defaults" are what the command is changing - tell me that as a result, the services will not be disabled - tell me WHAT is overriding the defaults that I'm attempting to change - and/or tell me what I am supposed to do to fix the issue ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu21.4 ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134 Uname: Linux 4.4.0-133-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 15 16:26:28 2018 InstallationDate: Installed on 2013-10-11 (1768 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-133-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1787225/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787225] Re: systemctl disable apache2 does nothing
Thanks for filing this bug in Ubuntu. I just repeated your steps on a xenial lxd, using apache2 2.4.18-2ubuntu3.10, and after rebooting the container, apache2 was not started. I got the same warnings that you did, however. Furthermore, status also shows it's inactive after the reboot: $ systemctl status apache2 ● apache2.service - LSB: Apache2 web server Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled) Drop-In: /lib/systemd/system/apache2.service.d └─apache2-systemd.conf Active: inactive (dead) Docs: man:systemd-sysv-generator(8) Could you please try the above status command after you reboot, see what it says? Maybe you have something else starting apache, or requiring it perhaps? ** Changed in: apache2 (Ubuntu) Status: New => Incomplete -- 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/1787225 Title: systemctl disable apache2 does nothing Status in apache2 package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: I installed apache2 on Ubuntu 16.04, and out of the box it was enabled as a service, meaning it would automatically start at every boot. That is not what I want as this is my personal computer, not a server. $ systemctl is-enabled apache2.service enabled So I ran: $ sudo systemctl disable apache2 and this was the output: apache2.service is not a native service, redirecting to systemd-sysv-install Executing /lib/systemd/systemd-sysv-install disable apache2 insserv: warning: current start runlevel(s) (empty) of script `apache2' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `apache2' overrides LSB defaults (0 1 6). insserv: warning: current start runlevel(s) (empty) of script `apache2' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `apache2' overrides LSB defaults (0 1 6). Then I rebooted. I expected to find apache2 not running. Instead, it was running. Surprisingly: $ systemctl is-enabled apache2.service apache2.service is not a native service, redirecting to systemd-sysv-install Executing /lib/systemd/systemd-sysv-install is-enabled apache2 disabled so, it shows up as disabled, yet it is started at startup. I wonder if this is what those warnings were about. Those messages are unclear as fuck, I have no f***ing clue what they are supposed to mean. I read that the CURRENT runlevel overrides a DEFAULT. I guess that should be fine, unless what systemctl actually changes are the defaults, and those are overwritten by something else, which means that "sysctl disable" will have no effect. If that is the case, then the warning should be more explicit: - be specific about the fact that "LSB defaults" are what the command is changing - tell me that as a result, the services will not be disabled - tell me WHAT is overriding the defaults that I'm attempting to change - and/or tell me what I am supposed to do to fix the issue ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu21.4 ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134 Uname: Linux 4.4.0-133-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 15 16:26:28 2018 InstallationDate: Installed on 2013-10-11 (1768 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-133-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1787225/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704682] Re: isc-dhcp-client gladly accepts and sets server options that were not requested
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: isc-dhcp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1704682
Title:
isc-dhcp-client gladly accepts and sets server options that were not
requested
Status in isc-dhcp package in Ubuntu:
Confirmed
Bug description:
Operating System: Ubuntu 16.04 amd64, fully updated. isc-dhcp-client
package 4.3.3-5ubuntu12.7
I noticed this behaviour when trying a special setting (I didn't want
to accept the default gateway from my dhcp server). Even if I modify
the request setting by removing the routers, thus causing dhclient NOT
to send the 'Routers' option (option 3), my home router (Asus DSL-
n66u) sends everything it knows, including the default gateway.
But, from reading the documentation and various mailing lists, it
seems that the client should DISCARD options that were not requested.
That could even be a security vulnerability; a rogue DHCP server could
break much more havoc than expected, e.g. redirecting an host's
default gateway while the owner thought that was impossible.
dhclient.conf:
option rfc3442-classless-static-routes code 121 = array of unsigned integer 8;
send host-name = gethostname();
request subnet-mask, broadcast-address, time-offset,
domain-name, domain-name-servers, domain-search, host-name,
dhcp6.name-servers, dhcp6.domain-search, dhcp6.fqdn, dhcp6.sntp-servers,
netbios-name-servers, netbios-scope, interface-mtu,
ntp-servers;
interface "enp0s3" {
request subnet-mask, broadcast-address;
}
tcpdump log:
00:45:48.691568 Out 08:00:27:4b:a4:c9 ethertype IPv4 (0x0800), length 344:
(tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from
08:00:27:4b:a4:c9, length 300, xid 0xc9572a43, secs 3, Flags [none] (0x)
Client-Ethernet-Address 08:00:27:4b:a4:c9
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Discover
Requested-IP Option 50, length 4: 172.20.20.92
Hostname Option 12, length 8: "bitbuntu"
Parameter-Request Option 55, length 2:
Subnet-Mask, BR
0x: 4510 0148 8011 3996 E..H..9.
0x0010: 0044 0043 0134 f56e 0101 0600 .D.C.4.n
0x0020: c957 2a43 0003 .W*C
0x0030: 0800 274b a4c9 ..'K
0x0040:
0x0050:
0x0060:
0x0070:
0x0080:
0x0090:
0x00a0:
0x00b0:
0x00c0:
0x00d0:
0x00e0:
0x00f0:
0x0100: 6382 5363 3501 0132 c.Sc5..2
0x0110: 04ac 1414 5c0c 0862 6974 6275 6e74 7537 \..bitbuntu7
0x0120: 0201 1cff
0x0130:
0x0140:
00:45:48.691583 B 08:00:27:4b:a4:c9 ethertype IPv4 (0x0800), length 344:
(tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)
0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from
08:00:27:4b:a4:c9, length 300, xid 0xc9572a43, secs 3, Flags [none] (0x)
Client-Ethernet-Address 08:00:27:4b:a4:c9
Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Discover
Requested-IP Option 50, length 4: 172.20.20.92
Hostname Option 12, length 8: "bitbuntu"
Parameter-Request Option 55, length 2:
Subnet-Mask, BR
0x: 4510 0148 8011 3996 E..H..9.
0x0010: 0044 0043 0134 f56e 0101 0600 .D.C.4.n
0x0020: c957 2a43 0003 .W*C
0x0030: 0800 274b a4c9
[Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay
This still seems to be an issue. Running latest Bionic. # dpkg -s dbus | grep Version Version: 1.12.2-1ubuntu1.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1591411 Title: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay Status in D-Bus: Fix Released Status in systemd: Fix Released Status in dbus package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in dbus source package in Xenial: Fix Released Status in systemd source package in Xenial: Invalid Status in dbus source package in Yakkety: Won't Fix Status in systemd source package in Yakkety: Invalid Bug description: [Impact] The bug affects multiple users and introduces an user visible delay (~25 seconds) on SSH connections after a large number of sessions have been processed. This has a serious impact on big systems and servers running our software. The currently proposed fix is actually a safe workaround for the bug as proposed by the dbus upstream. The workaround makes uid 0 immune to the pending_fd_timeout limit that kicks in and causes the original issue. [Test Case] lxc launch ubuntu:x test lxc exec test -- login -f ubuntu ssh-import-id Then ran a script as follows (passing in ubuntu@): while [ 1 ]; do (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log done Then checking the log file if there are any ssh sessions that are taking 25+ seconds to complete. Multiple instances of the same script can be used at the same time. [Regression Potential] The fix has a rather low regression potential as the workaround is a very small change only affecting one particular case - handling of uid 0. The fix has been tested by multiple users and has been around in zesty for a while, with multiple people involved in reviewing the change. It's also a change that has been proposed by upstream. [Original Description] I noticed on a system that accepts large numbers of SSH connections that after awhile, SSH sessions were taking ~25 seconds to complete. Looking in /var/log/auth.log, systemd-logind starts failing with the following: Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for user ubuntu by (uid=0) Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu. Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: Transport endpoint is not connected Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create session: Message recipient disconnected from message bus without replying I reproduced this in an LXD container by doing something like: lxc launch ubuntu:x test lxc exec test -- login -f ubuntu ssh-import-id Then ran a script as follows (passing in ubuntu@): while [ 1 ]; do (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log done In my case, after 1052 logins, the 1053rd and thereafter were taking 25+ seconds to complete. Here are some snippets from the log file: $ cat log | grep 0m0 | wc -l 1052 $ cat log | grep 0m25 | wc -l 4 $ tail -5 log real 0m0.222s real 0m25.232s real 0m25.235s real 0m25.236s real 0m25.239s ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Jun 11 00:09:34 2016 MachineType: Notebook W230SS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1591411/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1832123] Re: [SRU] Bugfix release 1.14.5
I'm testing now, and will report later. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Committed Status in gst-plugins-bad1.0 source package in Bionic: Fix Committed Status in gst-plugins-base1.0 source package in Bionic: Fix Committed Status in gst-plugins-good1.0 source package in Bionic: Fix Committed Status in gst-plugins-ugly1.0 source package in Bionic: Fix Committed Status in gst-python1.0 source package in Bionic: Fix Committed Status in gst-rtsp-server1.0 source package in Bionic: Fix Committed Status in gstreamer-editing-services1.0 source package in Bionic: Fix Committed Status in gstreamer-vaapi source package in Bionic: Fix Committed Status in gstreamer1.0 source package in Bionic: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the top of a previous GError - rtspconnection: do not duplicate authentication headers - subparse: don’t assert when failing to parse subrip timestamp - video: various convert sample frame fixes - video-converter: fix conversion from I420_10LE/BE, I420_12LE/BE, A420_10LE/BE to BGRA/RGBA which created corrupted output - video-format: Fix GBRA_10/12 alpha channel pixel strides gst-plugins-good - flv: Use 8kHz sample rate for alaw/mulaw audio - flvdemux: Do not error out if the first added and chained pad is not linked - flvmux: try harder to make sure timestamps are always increasing - gdkpixbufdec: output a TIME segment which is what’s expected for raw video - matroskademux: fix handling of MS ACM audio - matroska: fix handling of FlagInterlaced - pulsesink: Deal with not being able to convert a format to caps - rtph265depay, rtph264depay; aggregation packet marker handling fixes - rtpmp4gdepay: detect broken senders who send AAC with ADTS frames - rtprawdepay: keep buffer pool around when flushing/seeking - rtpssrcdemux: Forward serialized events to all pads - qmlglsink: Handle OPENGL header guard changes - qtdemux: fix track language code parsing; ignore corrupted CTTS box - qtmux: Correctly set tkhd width/height to
[Touch-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
According to LP: #1836929 I've done the following merge request: https://code.launchpad.net/~rafaeldtinoco/britney/hints- ubuntu/+merge/370268 requesting tests before eoan to be classified as "bad tests". Thus, those failures are "false positives" and SRU is good. I have also verified the SRU is it is good. ** Tags removed: verification-needed verification-needed-disco ** Tags added: verification-done verification-done-disco -- 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/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: Fix Committed Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] # Ubuntu 19.10 (Eoan Ermine) (c)inaddy@eoan:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] I have generated a pkg using upstream iproute2 source code and it does not suffer the issue. I have generated a package using Ubuntu cosmic source package, without debian/patches/*, and verified the issue still persists (not being introduced by any of our packages, and being present if vanilla upstream version used in Cosmic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1831775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
This happens because output of clknetsim was modified and the following
regex:
# Check if only NTP port (123) was used
check_packet_port() {
local i ret=0 port=123
test_message 2 1 "checking port numbers in packet log:"
+ set -x
+
+ cp tmp/log.packets /tmp/mine.log.packets
+
for i in $(seq 1 $(get_chronyd_nodes)); do
test_message 3 0 "node $i:"
grep -E -q "$port [0-9]+\$" tmp/log.packets && \
! grep -E "^[0-9e.+-]+ $i " tmp/log.packets | \
grep -E -q -v " $port [0-9]+\$" && \
test_ok || test_bad
[ $? -eq 0 ] || ret=1
done
+ set +x
+
return $ret
}
Broke. Example of the output change:
# good (old) output (vi :set list)
2.020970e-01>---1>--2>--1.854754e-04>---123>123>1$
2.022825e-01>---2>--1>--2.935628e-04>---123>123>1$
2.027594e-01>---2>--1>--1.794174e-04>---123>123>1$
2.029388e-01>---1>--2>--2.045724e-04>---123>123>1$
# bad (new) output (vi :set list)
2.066646e+03>---2>--1>--1.297676e-04>---123>123>1>--48>-1$
2.066646e+03>---1>--2>--1.520290e-04>---123>123>1>--48>-1$
2.191654e+03>---1>--2>--1.690480e-04>---123>123>1>--48>-1$
2.191654e+03>---2>--1>--4.082407e-04>---123>123>1>--48>-1$
TODO:
- make a change to eoan so clknetsim code is compatible (so this wont happen
again)
- mark this test as faulty for previous chronie versions (since they will
always fail)
- (could do) fix autopkgtest next time chronie needs a SRU (disco/bionic)
--
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/1831775
Title:
ss seems broken when using multiple filters in the same cmdline
Status in iproute2 package in Ubuntu:
Fix Released
Status in iproute2 source package in Cosmic:
Won't Fix
Status in iproute2 source package in Disco:
Fix Committed
Status in iproute2 source package in Eoan:
Fix Released
Bug description:
[Impact]
* ss won't be able to run commands with single filters inside
parentheses, like: "( sport == :X )", for example.
* A workaround is to remove "( )" from single filters, since it looks
the issue does not affect 2 filters being put together in the same
parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and (
Y )".
* CTDB is unable to use ss filter to obtain nodes public IP addresses
in order to fail over services (LP: #722201).
[Test Case]
* Having an Ubuntu Cosmic, Disco or Eoan, try to execute the
following command:
$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3]
)" "( sport == :2049 )"
Independent of the IPs or ports being used. Copying and pasting the
command should be enough for you to know if you are affected.
Bad Result:
ss: bison bellows (while parsing filter): "syntax error!" Sorry.
Usage: ss [ OPTIONS ]
ss [ OPTIONS ] [ FILTER ]
-h, --help this message
...
Expected Result:
Recv-QSend-Q Local Address:Port
Peer Address:Port
...
* test case was discovered during CTDB scripts execution
[Regression Potential]
* biggest risk would be to affect ss interpreter (worst case scenario).
* the proposed patch is based in upstream fix and was tested against the
same issue reported as the reproducer (above) and some other generic ss
commands.
* any problem here is unlikely to change iproute2 most important command
interpreter, "ip", since the patch is applied against ss code.
[Other Info]
ORIGINAL DESCRIPTION:
Investigating an issue for CTDB (LP: #722201), after suggesting a fix
on ss syntax to CTDB upstream project, we discovered that "ss" seems
to be broken in Ubuntu since Ubuntu Cosmic:
# Debian Sid
inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src
[172.16.17.3] )" "( sport == :2049 )"
Recv-QSend-Q Local Address:Port
Peer Address:Port
# Ubuntu Ubuntu 16.04 LTS (Xenial Xerus)
(c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src
[172.16.17.3] )" "( sport == :2049 )"
Recv-Q Send-QLocal Address:Port
Peer Address:Port
# Ubuntu 18.04 LTS (Bionic Beaver)
(c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src
[172.16.17.3] )" "( sport == :2049 )"
Recv-Q Send-Q Local Address:Port
Peer Address:Port
# Ubuntu 18.10 (Cosmic Cuttlefish)
(c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src
[172.16.17.3] )" "( sport == :2049 )"
ss: bison bellows (while parsing filter): "syntax error!" Sorry.
Usage: ss [ OPTIONS ]
ss [ OPTIONS ] [ FILTER ]
-h, --help this message
# Ubuntu 19.04 (Disco Dingo)
(c)inaddy@disco:~$ ss -tn state
[Touch-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
Issue happens because of the "upstream" "git cloned" clknetsim test dependencies. The tests clone upstream clknetsim repo. Using an old version of clknetsim I was able to make the test 111 to pass: (c)inaddy@iproute2verification:~/work/sources/ubuntu/chrony/test/simulation$ ./111-knownclient Testing reply to client configured as server: network with 1*1 servers and 1 clients: non-default settings: client_conf=acquisitionport 123 server_conf=server 192.168.123.2 noselect acquisitionport 123 starting node 1:OK starting node 2:OK running simulation: OK checking chronyd exit: node 1: OK node 2: OK checking source selection: node 2: OK checking port numbers in packet log: node 1: OK node 2: OK checking clock sync time, max/rms time/freq error: node 2: 130 1.47e-04 6.19e-07 7.41e-05 8.68e-08 OK PASS Will bisect cause its faster and easier. -- 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/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: Fix Committed Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ]
[Touch-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
(c)inaddy@iproute2verification:~/work/sources/ubuntu/chrony/test/simulation/clknetsim$ git bisect bad 537cb7161de9ad372437ab0fcbff76e54a3cd97a is the first bad commit commit 537cb7161de9ad372437ab0fcbff76e54a3cd97a Author: Miroslav Lichvar Date: Tue Jun 11 17:05:22 2019 +0200 add message type :100644 100644 2898b26a7b1311647b4419da79000e69b6d89b39 5b6d8917e1dd4667fe124b22a907e42286cb86f4 M client.c :100644 100644 20f052d7583d6051e779fd7318f47a3867595993 5cab1f4e86f95719814657da69a93089d029025e M client_fuzz.c :100644 100644 7b2fcbe0c5d39193946afebbd778a506c3452cb9 eeff3aba6b4bc46dc0ef516257a8ff130549a827 M network.cc :100644 100644 427036573b6da7227c5d7fa169a3d81627330d9c b5fe35b408f2a635455548d2b7dfd0ec7ec6da90 M network.h :100644 100644 be9d6fa5177c49acd3906643fc010576a5d5369d cf94b9e42bdb6a1b33b84afe8b5e19a9a5d00806 M node.cc :100644 100644 36e4e328ce10b062166c101a1d4c74244af558ab da78179483f88c84314c85af8dbfd9843332a33d M protocol.h -- 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/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: Fix Committed Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] # Ubuntu 19.10 (Eoan Ermine) (c)inaddy@eoan:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] I have
[Touch-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
Chrony issue being investigated here: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1836929 -- 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/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: Fix Committed Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] # Ubuntu 19.10 (Eoan Ermine) (c)inaddy@eoan:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] I have generated a pkg using upstream iproute2 source code and it does not suffer the issue. I have generated a package using Ubuntu cosmic source package, without debian/patches/*, and verified the issue still persists (not being introduced by any of our packages, and being present if vanilla upstream version used in Cosmic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1831775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831150] Re: its undocumented that only user.* extended attributes are restored upon extraction
Given that the only documentation which refers to the default behavior of extended attributes is only included upstream and is not shipped in the Debian or Ubuntu package I'm closing this bug as Invalid. ** Changed in: tar (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1831150 Title: its undocumented that only user.* extended attributes are restored upon extraction Status in GNU tar: Unknown Status in tar package in Ubuntu: Invalid Status in tar package in Debian: New Bug description: The tar info page and upstream documentation indicate that when --xattr is used "all names are stored in the archive (or extracted, if using '--extract')", however when using --xattr with extract the security.capability extended attributes are not restored. If one also uses "--xattrs-include=*" then the security.capability extended attributes will be restored. [Test Case] mkdir orig restore touch orig/file_with_capability_and_user_xattr setcap cap_net_raw=p orig/file_with_capability_and_user_xattr (eoan-amd64)root@impulse:/tmp# getfattr -m . -d orig/file_with_capability_and_user_xattr # file: orig/file_with_capability_and_user_xattr security.capability=0sAgAgAAA= user.testkey="testvalue" (eoan-amd64)root@impulse:/tmp# tar c --xattrs --acls --directory orig/ . | tar x --xattrs --acls --directory restore/ (eoan-amd64)root@impulse:/tmp# getfattr -m . -d restore/file_with_capability_and_user_xattr # file: restore/file_with_capability_and_user_xattr user.testkey="testvalue" (eoan-amd64)root@impulse:/tmp# tar c --xattrs --directory orig/ . | tar x --xattrs --xattrs-include=* --directory restore/ (eoan-amd64)root@impulse:/tmp# getfattr -m . -d restore/file_with_capability_and_user_xattr # file: restore/file_with_capability_and_user_xattr security.capability=0sAgAgAAA= user.testkey="testvalue" I think tar's extract behavior should be changed to match that of create so that all names are actually extracted. To manage notifications about this bug go to: https://bugs.launchpad.net/tar/+bug/1831150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836934] [NEW] eoan boot hides grub menu
Public bug reported: I dual boot several Ubuntu versions and have edited /etc/default/grub to show them on boot (and default to the last used). When eoan installs grub I no longer see the grub menu listing them during boot. Holding the shift key doesn't help. Although not displayed the menu seems to be active as I can select another install by using the cursor keys and enter. Reinstalling and updating grub from 18.04 restores normality - once I've found 18.04 by guessing where it is on the (hidden) boot menu. ** Affects: grub (Ubuntu) Importance: Undecided Status: New ** Package changed: initramfs-tools (Ubuntu) => grub (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1836934 Title: eoan boot hides grub menu Status in grub package in Ubuntu: New Bug description: I dual boot several Ubuntu versions and have edited /etc/default/grub to show them on boot (and default to the last used). When eoan installs grub I no longer see the grub menu listing them during boot. Holding the shift key doesn't help. Although not displayed the menu seems to be active as I can select another install by using the cursor keys and enter. Reinstalling and updating grub from 18.04 restores normality - once I've found 18.04 by guessing where it is on the (hidden) boot menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/1836934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832123] Re: [SRU] Bugfix release 1.14.5
Comments #17, #18, #19 are false positives - there aren't any regressions. Amr Ibrahim, if you wanted to test this that'd be appreciated. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Committed Status in gst-plugins-bad1.0 source package in Bionic: Fix Committed Status in gst-plugins-base1.0 source package in Bionic: Fix Committed Status in gst-plugins-good1.0 source package in Bionic: Fix Committed Status in gst-plugins-ugly1.0 source package in Bionic: Fix Committed Status in gst-python1.0 source package in Bionic: Fix Committed Status in gst-rtsp-server1.0 source package in Bionic: Fix Committed Status in gstreamer-editing-services1.0 source package in Bionic: Fix Committed Status in gstreamer-vaapi source package in Bionic: Fix Committed Status in gstreamer1.0 source package in Bionic: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the top of a previous GError - rtspconnection: do not duplicate authentication headers - subparse: don’t assert when failing to parse subrip timestamp - video: various convert sample frame fixes - video-converter: fix conversion from I420_10LE/BE, I420_12LE/BE, A420_10LE/BE to BGRA/RGBA which created corrupted output - video-format: Fix GBRA_10/12 alpha channel pixel strides gst-plugins-good - flv: Use 8kHz sample rate for alaw/mulaw audio - flvdemux: Do not error out if the first added and chained pad is not linked - flvmux: try harder to make sure timestamps are always increasing - gdkpixbufdec: output a TIME segment which is what’s expected for raw video - matroskademux: fix handling of MS ACM audio - matroska: fix handling of FlagInterlaced - pulsesink: Deal with not being able to convert a format to caps - rtph265depay, rtph264depay; aggregation packet marker handling fixes - rtpmp4gdepay: detect broken senders who send AAC with ADTS frames - rtprawdepay: keep buffer pool around when flushing/seeking - rtpssrcdemux: Forward serialized events to all pads - qmlglsink: Handle OPENGL header guard changes - qtdemux: fix
[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
seb128 retried apport/i386 and libreoffice/ppc64el, blaming "infrastructure issue[s]" (I don't see evidence of that; it seems like slightly flaky tests to me). They passed on the retry, and so I think you are OK for testing now. Till, you or somebody else needs to verify this bug now. (Seb, it's probably good to comment on the bug when doing things like retrying tests, btw, so that the uploader doesn't get confused. Ideally you'll monitor your retries and comment with the results, but at least saying that you've done it would be better than nothing.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1763520 Title: after upgrade to bionic, printing fails without explanation / logs / debuggability Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Bionic: Fix Committed Status in gtk+3.0 source package in Cosmic: Won't Fix Bug description: [Impact] The problem occurs when the printer's driver package is updated and with this the PPD is replaced and one of the default settings of the queue is not available any more in the new PPD file. Then the setting is prefixed with "Custom." and with this the jobs fail. See comment #15 for more info. [Test Case] - Create a print queue with a PPD. - evince an arbitrary PDF file - Click the print icon - In the print dialog choose the newly created queue and choose some uncommon paper size (not custom). Click "Print". - Check /var/log/cups/error_log, the page size gets correctly received. - Close evince. - Stop CUPS, edit the PPD file removing the paper size you have selected for your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines. - Start CUPS. - Open the same PDF file again with evince, click Print and then select "Print" in the print dialog without changing anything. - The job fails, in /var/log/cups/error_log you see that the page size is prefixed with "Custom.". With the fixed package installed the job will print. [Regression Potential] The change applies only to saved settings of the print dialog not matching with any of the settings available in the PPD file. In rare cases the fix could fail by mis-understanding the setting and this way not being effective. For options which do not support setting custom values (the vast majority) the patch should always prevent a job failure though. [Other Info] Complete info about the bug and the fix in comment #15, Original bug description: I am unable to print to my network-attached printer after upgrade to bionic. ps shows: lp 26047 0.0 0.0 91668 5756 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 lp 26050 0.1 0.0 0 0 ?Z15:06 0:00 | \_ [gs] lp 26048 0.0 0.0 79908 3836 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 root 26049 0.0 0.0 84388 6192 ?S15:06 0:00 \_ ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 Note the un-reaped gs process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 12 15:07:49 2018 InstallationDate: Installed on 2010-09-24 (2757 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO
[Touch-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
I have downgraded iproute2 package (using -updates pocket) and it also gave the same errors: (c)inaddy@iproute2verification:~/work/sources/ubuntu/chrony/test/simulation$ ./111-knownclient Testing reply to client configured as server: network with 1*1 servers and 1 clients: ... checking port numbers in packet log: node 1: BAD node 2: BAD FAIL (c)inaddy@iproute2verification:~/work/sources/ubuntu/chrony/test/simulation$ ./112-port Testing port and acquisitionport directives: network with 1*1 servers and 1 clients: ... checking port numbers in packet log: node 1: BAD node 2: BAD FAIL So its not because of this SRU. -- 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/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: Fix Committed Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] # Ubuntu 19.10 (Eoan Ermine) (c)inaddy@eoan:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] I have generated a pkg using upstream iproute2 source code and it does not suffer the issue. I have generated a package using Ubuntu cosmic
[Touch-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
(c)inaddy@iproute2verification:~/work/sources/ubuntu/chrony/test/simulation$ ./111-knownclient Testing reply to client configured as server: network with 1*1 servers and 1 clients: non-default settings: client_conf=acquisitionport 123 server_conf=server 192.168.123.2 noselect acquisitionport 123 starting node 1:OK starting node 2:OK running simulation: OK checking chronyd exit: node 1: OK node 2: OK checking source selection: node 2: OK checking port numbers in packet log: node 1: BAD node 2: BAD FAIL AND (c)inaddy@iproute2verification:~/work/sources/ubuntu/chrony/test/simulation$ ./112-port Testing port and acquisitionport directives: network with 1*1 servers and 1 clients: non-default settings: starting node 1:OK starting node 2:OK running simulation: OK checking chronyd exit: node 1: OK node 2: OK checking source selection: node 2: OK checking mean/min incoming/outgoing packet interval: node 1: 2.74e+02 2.74e+02 6.40e+01 6.40e+01 OK node 2: 2.74e+02 2.74e+02 6.40e+01 6.40e+01 OK checking clock sync time, max/rms time/freq error: node 2: 132 9.29e-05 1.21e-06 5.77e-05 1.01e-07 OK checking port numbers in packet log: node 1: BAD node 2: BAD network with 1*1 servers and 1 clients: non-default settings: client_conf=acquisitionport 123 starting node 1:OK starting node 2:OK running simulation: OK checking chronyd exit: node 1: OK node 2: OK checking port numbers in packet log: node 1: BAD node 2: BAD FAIL -- 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/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: Fix Committed Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax
[Touch-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
Actually they are not intermittent, they started happening after ... The upstream merge request into eoan I commented about: https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/370185 and my comment: https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/369588/comments/967625 This occurs since iproute2/4.18.0-1ubuntu3 triggered the tests. I'm investigating... -- 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/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: Fix Committed Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] # Ubuntu 19.10 (Eoan Ermine) (c)inaddy@eoan:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] I have generated a pkg using upstream iproute2 source code and it does not suffer the issue. I have generated a package using Ubuntu cosmic source package, without debian/patches/*, and verified the issue still persists (not being introduced by any of our packages, and being present if vanilla upstream version used in Cosmic). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1831775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1831775] Re: ss seems broken when using multiple filters in the same cmdline
# disco verification: (c)inaddy@iproute2verification:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # migration issue (chrony rev dependency autopkgtests): 109-makestep PASS 110-chronyc PASS 111-knownclient FAIL 112-port FAIL 113-leapsecond PASS 114-presend PASS 115-cmdmontime PASS 116-minsources PASS 117-fallbackdrift PASS These are known as intermittent tests (as I reviewed last chrony upstream merge and they were also failing intermittently). -- 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/1831775 Title: ss seems broken when using multiple filters in the same cmdline Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Cosmic: Won't Fix Status in iproute2 source package in Disco: Fix Committed Status in iproute2 source package in Eoan: Fix Released Bug description: [Impact] * ss won't be able to run commands with single filters inside parentheses, like: "( sport == :X )", for example. * A workaround is to remove "( )" from single filters, since it looks the issue does not affect 2 filters being put together in the same parentheses, like: " ( X and Y ) and Y " instead of ( X and Y ) and ( Y )". * CTDB is unable to use ss filter to obtain nodes public IP addresses in order to fail over services (LP: #722201). [Test Case] * Having an Ubuntu Cosmic, Disco or Eoan, try to execute the following command: $ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Independent of the IPs or ports being used. Copying and pasting the command should be enough for you to know if you are affected. Bad Result: ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message ... Expected Result: Recv-QSend-Q Local Address:Port Peer Address:Port ... * test case was discovered during CTDB scripts execution [Regression Potential] * biggest risk would be to affect ss interpreter (worst case scenario). * the proposed patch is based in upstream fix and was tested against the same issue reported as the reproducer (above) and some other generic ss commands. * any problem here is unlikely to change iproute2 most important command interpreter, "ip", since the patch is applied against ss code. [Other Info] ORIGINAL DESCRIPTION: Investigating an issue for CTDB (LP: #722201), after suggesting a fix on ss syntax to CTDB upstream project, we discovered that "ss" seems to be broken in Ubuntu since Ubuntu Cosmic: # Debian Sid inaddy@workstation:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-QSend-Q Local Address:Port Peer Address:Port # Ubuntu Ubuntu 16.04 LTS (Xenial Xerus) (c)inaddy@xenial:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-QLocal Address:Port Peer Address:Port # Ubuntu 18.04 LTS (Bionic Beaver) (c)inaddy@bionic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" Recv-Q Send-Q Local Address:Port Peer Address:Port # Ubuntu 18.10 (Cosmic Cuttlefish) (c)inaddy@cosmic:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] -h, --help this message # Ubuntu 19.04 (Disco Dingo) (c)inaddy@disco:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] # Ubuntu 19.10 (Eoan Ermine) (c)inaddy@eoan:~$ ss -tn state established "( src [172.16.17.2] || src [172.16.17.3] )" "( sport == :2049 )" ss: bison bellows (while parsing filter): "syntax error!" Sorry. Usage: ss [ OPTIONS ] ss [ OPTIONS ] [ FILTER ] I have generated a pkg using upstream iproute2 source code
[Touch-packages] [Bug 298268] Re: shortcuts for view resize are not displayed in menu
No reply to comment #2 from reporter Report did not expire due to bug watch Issue refers to the old interface Aspect ratios changed in new interface Upstream report closed 2018-02-10 "RESOLVED OBSOLETE" Closing as report is no longer valid ** Changed in: gtk+2.0 (Ubuntu) Status: Incomplete => Invalid ** Changed in: totem (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/298268 Title: shortcuts for view resize are not displayed in menu Status in GTK+: Expired Status in gtk+2.0 package in Ubuntu: Invalid Status in totem package in Ubuntu: Invalid Bug description: Binary package hint: totem Shortcuts exist in Totem to resize the movie window to different zoom ratios: 1:1, 2:1, 1:2. There are keyboard shortcuts for these (namely '1', '2', and '0') but they are not displayed in the menu. Displaying keyboard shortcuts in the menus is the most usable way for a user to discover what those shortcuts are, and so they should most definitely be displayed there. Please add the keyboard shortcuts for these commands to the Totem menus. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/298268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892/1220 on AMD chipsets
May as well join the fun. Believed I tried every suggested work around
above, still got crackling.
In my case the crackling is present on the line-in 3.5mm jack plug and
not a microphone.
I run:
X470 GAMING PRO (MS-7B79) motherboard with a ALC892, Ryzen 2700, Radeon
RX Vega 54. Running Ubuntu 19.04, Kernel 5.0.0-20-generic (was hoping
kernel 5 would improve things).
I did notice that the crackling reduced a bit when using this setting in
/etc/default.pa
### Automatically load driver modules depending on the hardware available
.ifexists module-udev-detect.so
load-module module-udev-detect use_ucm=0 tsched=0
.else
### Use the static hardware detection module (for systems that lack udev suppor$
load-module module-detect tsched=0
.endif
I use a Loopback (# pactl load-module module-loopback latency_msec=1) to pipe
some line in audio (chiptune device('s)) into PulseAudio if that's something
useful to know.
Really annoying problem, makes me feel ashamed using Linux, really nice
up to date computer (hardware) and some trivial piece of sillycon
working with every other OS refuses to work on Linux. Don't know who to
blame, but blaming I do!
USB soundcapture isn't really the thing I'm looking for. Unnecessary
latency is often a thing I try to avoid.
Who wants to trade a X470 GAMING PRO for a X470 board that has working
sound on Linux??
--
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/1801540
Title:
Microphone distorted sound on ALC892/1220 on AMD chipsets
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Incomplete
Status in pulseaudio package in Ubuntu:
Confirmed
Bug description:
Not sure if I'll report this upstream but there is definitely an issue
with microphone recording on my desktop, this is not happening on my
laptop which has a different codec.
Already tried all workarounds possible, no luck. Only with my desktop
with this particular motherboard. No issues in Windows, the sound
recorded in there is distorted and has some static and robotic tone on
high-pitch.
alsa-info on the attachments
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829968] Re: motd [on at least some instances] does not auto-update daily
I've also verified this for Ubuntu 18.04 (bionic) and it too passed. bdmurray@clean-bionic-amd64:~$ systemctl list-timers motd* --all NEXT LEFT LAST PASSED UNIT ACTIVATES Wed 2019-07-17 11:04:56 PDT 19h left Tue 2019-07-16 15:46:33 PDT 44s ago motd-news.timer motd-news.service 1 timers listed. bdmurray@clean-bionic-amd64:~$ systemctl list-timers motd* --all NEXT LEFT LAST PASSED UNITACTIVATES Wed 2019-07-17 23:10:07 PDT 15h left Wed 2019-07-17 06:50:12 PDT 55min ago motd-news.timer motd-news.service 1 timers listed. bdmurray@clean-bionic-amd64:~$ ls -lh /var/cache/motd-news -rw-r--r-- 1 root root 169 Jul 17 06:50 /var/cache/motd-news bdmurray@clean-bionic-amd64:~$ apt-cache policy base-files base-files: Installed: 10.1ubuntu2.5 ** Tags removed: verification-needed-bionic verification-needed-disco ** Tags added: verification-done-bionic verification-done-disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1829968 Title: motd [on at least some instances] does not auto-update daily Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Bionic: Fix Committed Status in base-files source package in Cosmic: Fix Committed Status in base-files source package in Disco: Fix Committed Status in base-files source package in Eoan: Fix Released Bug description: [Impact] motd-news timer is not properly configured and may not run regularly so long running systems will not get an updated motd [Test Case] The motd-news.timer is known to be incorrectly configured because motd-news.services is a one shot service which will not become active. Subsequently, have a timer with OnUnitActiveSec is wrong and the timer will not work reliably. However, because it can work some of the time it is difficult to find a case where the timer always fails so test case will involve only confirming that the new timer is correct. 1) On a system with curl installed, install the new version of base-files 2) Run 'systemctl list-timers motd* --all 3) Confirm that "LEFT" is less than 12 hours (Its less than 24 hours because we don't want people to miss important messages) 4) Wait until "NEXT" is reached 5) Confirm that there is another "NEXT" and that the time stamp of /var/cache/motd-news was updated [Regression Potential] I can't think of any on the client side as the job wasn't working as it was intended but it may cause extra load on the motd server. Original Description I have a VM running on AWS. It was launched on May 9th: $ uptime 05:26:21 up 12 days, 6:34, 1 user, load average: 0.00, 0.00, 0.00 $ date Wed May 22 05:26:24 UTC 2019 I touched none of the system defaults, and yet the motd has not updated automatically. $ ls -l /var/cache/motd-news -rw-r--r-- 1 root root 0 May 9 22:53 /var/cache/motd-news The systemd timer unit looks like this: $ systemctl status motd-news.timer ● motd-news.timer - Message of the Day Loaded: loaded (/lib/systemd/system/motd-news.timer; enabled; vendor preset: enabled) Active: active (elapsed) since Thu 2019-05-09 22:51:58 UTC; 1 weeks 5 days ago Trigger: n/a May 09 22:51:58 ip-172-31-23-224 systemd[1]: Started Message of the Day. If I run /etc/update-motd.d/50-motd-news --force manually, the file does update correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1829968/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829968] Re: motd [on at least some instances] does not auto-update daily
I've verified this for Ubuntu 19.04 (disco) and it is good. bdmurray@clean-disco-amd64:~$ systemctl list-timers motd* --all NEXT LEFT LAST PASSED UNITACTIVATES Wed 2019-07-17 03:06:29 PDT 11h left Tue 2019-07-16 15:43:04 PDT 2min 44s ago motd-news.timer motd-news.service 1 timers listed. bdmurray@clean-disco-amd64:~$ systemctl list-timers motd* --all NEXT LEFTLAST PASSED UNITACTIVATES Wed 2019-07-17 16:23:31 PDT 8h left Wed 2019-07-17 03:07:01 PDT 4h 36min ago motd-news.timer motd-news.service 1 timers listed. bdmurray@clean-disco-amd64:~$ ls -lh /var/cache/motd-news -rw-r--r-- 1 root root 169 Jul 17 03:07 /var/cache/motd-news bdmurray@clean-disco-amd64:~$ apt-cache policy base-files base-files: Installed: 10.1ubuntu9.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1829968 Title: motd [on at least some instances] does not auto-update daily Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Bionic: Fix Committed Status in base-files source package in Cosmic: Fix Committed Status in base-files source package in Disco: Fix Committed Status in base-files source package in Eoan: Fix Released Bug description: [Impact] motd-news timer is not properly configured and may not run regularly so long running systems will not get an updated motd [Test Case] The motd-news.timer is known to be incorrectly configured because motd-news.services is a one shot service which will not become active. Subsequently, have a timer with OnUnitActiveSec is wrong and the timer will not work reliably. However, because it can work some of the time it is difficult to find a case where the timer always fails so test case will involve only confirming that the new timer is correct. 1) On a system with curl installed, install the new version of base-files 2) Run 'systemctl list-timers motd* --all 3) Confirm that "LEFT" is less than 12 hours (Its less than 24 hours because we don't want people to miss important messages) 4) Wait until "NEXT" is reached 5) Confirm that there is another "NEXT" and that the time stamp of /var/cache/motd-news was updated [Regression Potential] I can't think of any on the client side as the job wasn't working as it was intended but it may cause extra load on the motd server. Original Description I have a VM running on AWS. It was launched on May 9th: $ uptime 05:26:21 up 12 days, 6:34, 1 user, load average: 0.00, 0.00, 0.00 $ date Wed May 22 05:26:24 UTC 2019 I touched none of the system defaults, and yet the motd has not updated automatically. $ ls -l /var/cache/motd-news -rw-r--r-- 1 root root 0 May 9 22:53 /var/cache/motd-news The systemd timer unit looks like this: $ systemctl status motd-news.timer ● motd-news.timer - Message of the Day Loaded: loaded (/lib/systemd/system/motd-news.timer; enabled; vendor preset: enabled) Active: active (elapsed) since Thu 2019-05-09 22:51:58 UTC; 1 weeks 5 days ago Trigger: n/a May 09 22:51:58 ip-172-31-23-224 systemd[1]: Started Message of the Day. If I run /etc/update-motd.d/50-motd-news --force manually, the file does update correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1829968/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795959] Re: [FFe] Seed xdg-desktop-portal-gtk
Hello Ken, or anyone else affected, Accepted ubuntu-meta into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- meta/1.417.2 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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 for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-meta (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-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/1795959 Title: [FFe] Seed xdg-desktop-portal-gtk Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Xenial: New Status in ubuntu-meta source package in Bionic: Fix Committed Bug description: [Impact] * These packages can improve desktop integration of snap packages. The risk is low as nothing in the default desktop install actually exercises the portals at this time. We need to seed the portals so they are available when snaps are installed that can utilize them. Flatpak packages will also benefit. [Test Case] * This can be tested by using the portal-test snap [Regression potential] * Nothing in the default install utilizes it, so there should be no risk. [Other Info] * Security and MIR reviews have been completed for xdg-desktop-portal-gtk[1] and xdg-desktop-portal[2]. 1. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1750069 2. https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1749672 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1795959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830796] Re: [Bionic][ARM64]Failure debugging linux kernel
Hello Manoj, or anyone else affected, Accepted gdb into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gdb/8.1-0ubuntu3.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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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 for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gdb (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1830796 Title: [Bionic][ARM64]Failure debugging linux kernel Status in gdb package in Ubuntu: Fix Released Status in gdb source package in Bionic: Fix Committed Bug description: [Impact] GDB fails to debug ARM64 vmlinux debug image with proc/kcore information. For example it is unable to print values of variables like 'jiffies_64'. [Test] # gdb /usr/lib/debug/boot/vmlinux-4.18.0-20-generic /proc/kcore [New process 1] Core was generated by `BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=edb5e5a7-8272-4e13-aa25-37'. #0 0x in ?? () (gdb) p jiffies_64 Cannot access memory at address 0x09616980 (gdb) [Fix] This issue was fixed upstream (git://sourceware.org/git/binutils-gdb.git) by the following patch: 8727de56b0 Fix tagged pointer support [Regression Potential] The risk of regression after applying this patch could be to architectures other than ARM64 due to changes to gdb/util.c. Please see comment #2 where I have tested the PPA package on a ppc64el system and found it does not introduce any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1830796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1164016] Re: restore type-ahead find
So mate used to be great but doesn't seem to be a solution anymore either, type-ahead-find seemingly has been replaced for search-as-you- type in mate sometimes this summer as well, too. +1 for replacement, it could at least be a configuration option -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836881] [NEW] Xorg freeze
Public bug reported: My gnome session freezes, mouse works fine but cannot start applications. I am able to enter one of the tty terminals and kill the session. This happens a few times a day and started a week ago probably. Douglas ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 17 12:29:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 4.15.0-52-generic, x86_64: installed nvidia, 418.56, 4.15.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1208] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Ti Mobile] [1025:1207] InstallationDate: Installed on 2018-01-13 (550 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. Bus 001 Device 003: ID 04ca:3016 Lite-On Technology Corp. Bus 001 Device 002: ID 0461:4e81 Primax Electronics, Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Predator PH317-51 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=455417ef-94fe-4ab8-97b7-0b992c951267 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Sienna_KLS dmi.board.vendor: KBL dmi.board.version: V1.05 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd05/18/2017:svnAcer:pnPredatorPH317-51:pvrV1.05:rvnKBL:rnSienna_KLS:rvrV1.05:cvnAcer:ct10:cvrV1.05: dmi.product.family: Predator Helios 300 dmi.product.name: Predator PH317-51 dmi.product.version: V1.05 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1836881 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: My gnome session freezes, mouse works fine but cannot start applications. I am able to enter one of the tty terminals and kill the session. This happens a few times a day and started a week ago probably. Douglas ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 17 12:29:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 4.15.0-52-generic, x86_64: installed nvidia, 418.56, 4.15.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1208] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Ti Mobile] [1025:1207] InstallationDate: Installed on 2018-01-13 (550 days ago)
[Touch-packages] [Bug 1836809] Re: segfault when CCD are present in two different HOG services
Ubuntu 18.10 bug id 204201 thanks! -- 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/1836809 Title: segfault when CCD are present in two different HOG services Status in bluez package in Ubuntu: Incomplete Bug description: Hello everyone, We are currently developing a device that contains two HID services. That device, as it is right now, is properly functioning on Windows & Android. However, when pairing the device on Linux running bluez 5.50 we do get segfaults (see attached files). Our bluetooth device has 4 services : 1 battery service, 2 HID Over Gatt services and 1 device information service. With trial and error, we managed to find that we wouldn't get any crash as long as only 1 HOG service was present. Here's the interesting part. The two HOG services are made as follows: - standard keyboard over gatt: protocole mode / report map / 1 INPUT report / boot INPUT + OUTPUT / HID information / HID Control point - raw HID over gatt : report map / 1 INPUT report / 1 OUTPUT report / HID information / HID control point Looking at the write_ccc in the call stacks we wondered if the callbacks subscribing to notifications for the INPUT reports were causing this issue. We therefore changed the raw HID over gatt (and its report map) to remove the INPUT report and change it into 1 OUTPUT report (leading to 2 OUTPUT reports): no crash. We therefore hypothesize that the segfault occurs when subscribing to notification on a second HOG service... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1836809/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768841] Re: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
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/1768841 Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in avahi package in Ubuntu: Confirmed Bug description: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Sun Apr 29 10:24:57 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-04-28 (4 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: avahi Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1768841/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
I don't understand how we're getting two instances of this crash in
version 1:11.1-1ubuntu7.3.
It sounds like either someone built their own package by the same name,
or errors.ubuntu.com is not grouping the crashes correctly.
I say this because the fix does:
+++ pulseaudio/src/modules/alsa/module-alsa-card.c
@@ -625,7 +625,8 @@ static pa_hook_result_t card_suspend_changed
if (card->suspend_cause == 0) {
/* We were unsuspended, update jack state in case it changed while we
were suspended */
PA_HASHMAP_FOREACH(jack, u->jacks, state) {
-report_jack_state(jack->melem, 0);
+if (jack->melem)
+report_jack_state(jack->melem, 0);
}
}
Yet errors.ubuntu.com is saying it is still crashing due to a NULL
melem:
report_jack_state (melem=0x0, mask=mask@entry=0)
card_suspend_changed
That NULL should be impossible with the patch.
I think most likely errors.ubuntu.com is grouping similar assertions in
mixer.c:929 incorrectly. And it only shows the full symbolic stack trace
from some older instance of the crash -- not the ones from version
1:11.1-1ubuntu7.3.
--
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/1663528
Title:
pulseaudio assert failure: pulseaudio: mixer.c:929:
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
Status in PulseAudio:
Fix Released
Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Bionic:
Fix Committed
Status in pulseaudio source package in Cosmic:
Fix Released
Status in pulseaudio source package in Disco:
Fix Released
Status in pulseaudio source package in Eoan:
Fix Released
Bug description:
[Impact]
https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250
https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad
https://errors.ubuntu.com/problem/0f07e226e7db1d0fb140736a956760871e695669
This is one of the top pulseaudio crashes in Ubuntu 18.04 according to:
https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year
[Test Case]
No manual test case known. Just watch errors.ubuntu.com to check for
recurrences.
[Regression Potential]
Low. The fix is already in PulseAudio 12 so has been used in Ubuntu
18.10 and later for a year so far.
[Other Info]
SRU sponsorship tracked in bug 1556439.
[Original Report]
Sidenote: Imediatly got that crash after the apt-xapian-index one (
lp:1663524 ); does not know if it can exist a possible relationship
between them.
Got an other crash, and that time 'sound' is fully lost (pulseaudio
not reloaded). Wonder if lp:1662860 can be concerned.
ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: pulseaudio 1:10.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
Uname: Linux 4.9.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
AssertionMessage: pulseaudio: mixer.c:929:
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem4084 F pulseaudio
/dev/snd/controlC0: oem4084 F pulseaudio
CurrentDesktop: GNOME
Date: Fri Feb 10 09:55:45 2017
ExecutablePath: /usr/bin/pulseaudio
ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_GB.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: pulseaudio
StacktraceTop:
__assert_fail_base (fmt=,
assertion=assertion@entry=0x7f92818e7188 "mixer",
file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929,
function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private")
at assert.c:92
__GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419
"mixer.c", line=929, function=0x7f92818e76a0
"snd_mixer_elem_get_callback_private") at assert.c:101
snd_mixer_elem_get_callback_private () from
/usr/lib/x86_64-linux-gnu/libasound.so.2
?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
Title: pulseaudio assert failure: pulseaudio: mixer.c:929:
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev
sambashare sudo users
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3002
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
[Touch-packages] [Bug 1836209] Re: network-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9
** Changed in: network-manager (Ubuntu) Importance: Low => High ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) -- 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/1836209 Title: network-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9 Status in network-manager package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/n/network-manager/20190710_160945_9116e@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/i386/n/network-manager/20190710_110735_e5ce3@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1836209/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690052] Re: pulseaudio crashed with SIGABRT in transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_set_state()
** Summary changed: - pulseaudio crashed with SIGABRT in transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_set_state() from endpoint_set_configuration() from endpoint_handler() + pulseaudio crashed with SIGABRT in transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_set_state() ** Tags added: cosmic -- 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/1690052 Title: pulseaudio crashed with SIGABRT in transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_set_state() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/49a8e58cea0b15b22d3a3cdbb1d736e619467e34 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 you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690052/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836851] Re: /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:pa_bluetooth_transport_put:profile_new_connection
*** This bug is a duplicate of bug 1690052 *** https://bugs.launchpad.net/bugs/1690052 ** This bug has been marked a duplicate of bug 1690052 pulseaudio crashed with SIGABRT in transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_set_state() -- 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/1836851 Title: /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:pa_bluetooth_transport_put:profile_new_connection Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:11.1-1ubuntu7.2, the problem page at https://errors.ubuntu.com/problem/215a0c1d7c39152b104eca0369f9ea0b76a04e7a 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/pulseaudio/+bug/1836851/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836851] [NEW] /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:pa_bluetooth_transport_put:profile_new_connection
*** This bug is a duplicate of bug 1690052 *** https://bugs.launchpad.net/bugs/1690052 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:11.1-1ubuntu7.2, the problem page at https://errors.ubuntu.com/problem/215a0c1d7c39152b104eca0369f9ea0b76a04e7a 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: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic wily -- 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/1836851 Title: /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:pa_bluetooth_transport_put:profile_new_connection Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:11.1-1ubuntu7.2, the problem page at https://errors.ubuntu.com/problem/215a0c1d7c39152b104eca0369f9ea0b76a04e7a 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/pulseaudio/+bug/1836851/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836849] Re: /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:pa_bluetooth_transport_unlink:rfcomm_io_callback
*** This bug is a duplicate of bug 1690052 *** https://bugs.launchpad.net/bugs/1690052 ** This bug has been marked a duplicate of bug 1690052 pulseaudio crashed with SIGABRT in transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_set_state() -- 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/1836849 Title: /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:pa_bluetooth_transport_unlink:rfcomm_io_callback Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/23c16d54f398bab7ef2d00f464fb9617535fab5d 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/pulseaudio/+bug/1836849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836849] [NEW] /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:pa_bluetooth_transport_unlink:rfcomm_io_callback
*** This bug is a duplicate of bug 1690052 *** https://bugs.launchpad.net/bugs/1690052 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/23c16d54f398bab7ef2d00f464fb9617535fab5d 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: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic -- 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/1836849 Title: /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:pa_bluetooth_transport_unlink:rfcomm_io_callback Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/23c16d54f398bab7ef2d00f464fb9617535fab5d 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/pulseaudio/+bug/1836849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836850] Re: /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:profile_new_connection:profile_handler
*** This bug is a duplicate of bug 1690052 *** https://bugs.launchpad.net/bugs/1690052 ** This bug has been marked a duplicate of bug 1690052 pulseaudio crashed with SIGABRT in transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_set_state() -- 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/1836850 Title: /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:profile_new_connection:profile_handler Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/fae9d4e8e68acd1bce20c4c187d94c1e66cb5202 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/pulseaudio/+bug/1836850/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836850] [NEW] /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:profile_new_connection:profile_handler
*** This bug is a duplicate of bug 1690052 *** https://bugs.launchpad.net/bugs/1690052 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/fae9d4e8e68acd1bce20c4c187d94c1e66cb5202 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: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic wily xenial yakkety zesty -- 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/1836850 Title: /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:profile_new_connection:profile_handler Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/fae9d4e8e68acd1bce20c4c187d94c1e66cb5202 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/pulseaudio/+bug/1836850/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
