[Touch-packages] [Bug 1821269] Re: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole combo jack mic doesn't detect)
I installed oem-audio-hda-daily-dkms_0.1_all.deb And rebooted my PC and plugged in apple earset. But earset's mic doesn't work too. compressed.zip contains 3 files. 20190523-00 : Ubuntu sound setting screenshot. "내부마이크" is laptop's internal mic. And earset's mic doesn't appear. 20190523-01 : I installed "PulseAudio Volume Control" package. When I installed oem-audio-xxx.deb, "Mic(unplugged)" is added. I changed to this from 내부마이크(internal mic). but it operated like laptop's internal mic. As a result, the earset's mic does not work. alsa-info.txt.ALf0UgderM : This is new "alsa-info.txt" file. Please check it. I'll remove oem-audio-hda-daily-dkms_0.1_all.deb package. Thank you. ** Attachment added: "compressed.zip" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821269/+attachment/5266143/+files/compressed.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821269 Title: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole combo jack mic doesn't detect) Status in alsa-driver package in Ubuntu: New Bug description: I use realtek alc255 analog audio jack. External jack is 4 pole combo(apple type. not europe type.). When I plug 4 pole mic into jack, It doesn't detect. So I can't my voice through external mic. My laptop has internal mic. It belongs to Intel sound(HDA Intel PCH. Audio device: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 21)). Internal mic works well. Please check 4pole external mic detection. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: jimnong1441 F...m pulseaudio /dev/snd/pcmC0D0p: jimnong1441 F...m pulseaudio /dev/snd/controlC0: jimnong1441 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 22 11:30:39 2019 InstallationDate: Installed on 2017-07-27 (603 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: 내장 오디오 - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_Type: No auto-switch between inputs Title: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch UpgradeStatus: Upgraded to bionic on 2018-09-23 (179 days ago) dmi.bios.date: 09/06/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Garp_BA dmi.board.vendor: Acer dmi.board.version: V1.24 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.24:bd09/06/2016:svnAcer:pnAspireES1-131:pvrV1.24:rvnAcer:rnGarp_BA:rvrV1.24:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: Aspire ES1-131 dmi.product.version: V1.24 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821269/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades
@rbalint: While it isn't clear from the bug updates alone IRC chat gave me the impression that this will be handled by you and the security Team (to push to -security) - is that correct or is any help needed that I miss? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1823872 Title: Fixing fsfreeze-hook can break unattended upgrades Status in qemu package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Confirmed Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Cosmic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: [Impact] * If an update has a new conffile at a path that in a former version was a directory like old: /a/b/c new: a/b Here b is the new file name and was a directory in the old version. Then unattended upgrades breaks on installing such a package. * a recent qemu update has such a case and due to that triggered the issue in >=Bionic * The fix is to harden unattended upgrades to be able to handle the case without aborting. [Test Case] Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12 That can be done with: $ time uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic label=daily Log in and apt update & upgrade all packages, then Install the release level qemu in there. $ uvt-kvm ssh bionic-testuu $ sudo apt update $ sudo apt dist-upgrade $ sudo apt install unattended-upgrades $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7 All before was preparation, now force the unattended upgrade to trigger the bug. $ sudo unattended-upgrade -d With the bug you'll find some error like: found pkg: qemu-guest-agent conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191 current md5: f61a64ac1e48993023018fd1cff85191 conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 15f6ff42cbc5550a07ee21c2a471d905 /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles /etc/init.d/qemu-guest-agent /etc/qemu/fsfreeze-hook found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2057, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1773, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' [Regression Potential] * The fix is trying to detect moved conffiles by looking for /etc/foo/foo when the new package ships /etc/foo and /etc/foo is not a known conffile and also checking the renames in the opposite direction. The potential regression is breaking the logic for detecting changed conffiles and either holding back a package for no reason or trying to install a package with a modified conffile on the system and aborting the upgrade in the middle due to the appearing conffile prompt. To avoid such regressions the test_conffile.py tests are extended to cover rename scenarios. [Other Info] * n/a --- As reported on https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20 We fixed an issue and we added workrounds since basic mv_conffile coudn't handle it and did all sort of upgrade tests. That all worked fine and moved the conffile. It was now reported that due to some pre-checks that unattended upgrades might do this might do some checks on its own. Next step: - check unattended upgrades through this change - check if it only affects cases were the former config was modified (minority) or the default file layout (majority) --- original report copied --- just wanted to add: This bug also crashes unattended-upgrade and thus prevents security updates on 18.04: root@mailin1:~# unattended-upgrade Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1998, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1714, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' Basically, unattended-upgrade wants to compare old/new conffiles and doesn't like it when the old conffile tu
[Touch-packages] [Bug 1830318] Re: intel graphics issues
Please run these commands on the machine: journalctl -b0 > journal.txt lspci -k > lspcik.txt dmesg > dmesg.txt and attach the resulting files: journal.txt, lspcik.txt and dmesg.txt ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Package changed: xorg (Ubuntu) => 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/1830318 Title: intel graphics issues Status in Ubuntu: Incomplete Bug description: my computer is behaving a though there arent any graphics drivers installed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 24 08:03:57 2019 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1830318/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830318] [NEW] intel graphics issues
Public bug reported: my computer is behaving a though there arent any graphics drivers installed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 24 08:03:57 2019 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1830318 Title: intel graphics issues Status in xorg package in Ubuntu: New Bug description: my computer is behaving a though there arent any graphics drivers installed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 24 08:03:57 2019 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1830318/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1818802 Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Audio dies after few seconds, returns after few minutes and dies again filip@ux433:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.20.14-042014-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: filip 8566 F pulseaudio /dev/snd/pcmC0D0p: filip 8566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 10:11:01 2019 InstallationDate: Installed on 2019-01-05 (59 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 comm="/usr/bin/pulseaudio --daemonize=no ") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago) dmi.bios.date: 11/21/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX433FN.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX433FN dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX433FN_UX433FN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821269] Re: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole combo jack mic doesn't detect)
checked the alsa-info.txt in #14, found the lifebook-extmic doesn't take effect, "model=liefbook-extmic" was added to kernel-4.19 but we are using kerel-4.15. So please test this dkms, if headset-mic still doesn't work, please generate an alsa-info.txt too. thx. To install the dkms: sudo dpkg -i oem-audio-xxx.deb reboot to remove the dkms: sudo dpkg -P oem-audio-hda-daily-dkms reboot ** Attachment added: "oem-audio-hda-daily-dkms_0.1_all.deb" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821269/+attachment/5266138/+files/oem-audio-hda-daily-dkms_0.1_all.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821269 Title: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole combo jack mic doesn't detect) Status in alsa-driver package in Ubuntu: New Bug description: I use realtek alc255 analog audio jack. External jack is 4 pole combo(apple type. not europe type.). When I plug 4 pole mic into jack, It doesn't detect. So I can't my voice through external mic. My laptop has internal mic. It belongs to Intel sound(HDA Intel PCH. Audio device: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 21)). Internal mic works well. Please check 4pole external mic detection. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: jimnong1441 F...m pulseaudio /dev/snd/pcmC0D0p: jimnong1441 F...m pulseaudio /dev/snd/controlC0: jimnong1441 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 22 11:30:39 2019 InstallationDate: Installed on 2017-07-27 (603 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: 내장 오디오 - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_Type: No auto-switch between inputs Title: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch UpgradeStatus: Upgraded to bionic on 2018-09-23 (179 days ago) dmi.bios.date: 09/06/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Garp_BA dmi.board.vendor: Acer dmi.board.version: V1.24 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.24:bd09/06/2016:svnAcer:pnAspireES1-131:pvrV1.24:rvnAcer:rnGarp_BA:rvrV1.24:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: Aspire ES1-131 dmi.product.version: V1.24 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821269/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830283] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1830283 Title: Xorg freeze Status in Ubuntu: Incomplete Bug description: 1 have worked in my projects then my ubuntu froze suddenly ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 24 02:20:15 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Today GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:2213] InstallationDate: Installed on 2019-04-01 (52 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 001 Device 004: ID 0bda:b001 Realtek Semiconductor Corp. Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=1dbcbc41-3811-4525-8a07-83de047700c3 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2213 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd09/19/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr096C11405F00050660180:rvnHewlett-Packard:rn2213:rvr57.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.version: 096C11405F00050660180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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/+bug/1830283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
** Bug watch removed: trac.nginx.org/nginx/ #1529 http://trac.nginx.org/nginx/ticket/1529 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1797386 Title: [SRU] OpenSSL 1.1.1 to 18.04 LTS Status in openssl package in Ubuntu: Fix Released Status in python-tornado package in Ubuntu: Confirmed Status in libio-socket-ssl-perl source package in Bionic: Incomplete Status in libnet-ssleay-perl source package in Bionic: Incomplete Status in openssl source package in Bionic: Fix Committed Status in python-cryptography source package in Bionic: Fix Committed Status in python2.7 source package in Bionic: Fix Committed Status in python3.6 source package in Bionic: Fix Committed Status in python3.7 source package in Bionic: Fix Committed Status in r-cran-openssl source package in Bionic: Fix Committed Status in ruby-openssl source package in Bionic: Fix Committed Status in ruby2.5 source package in Bionic: Confirmed Bug description: [Impact] * OpenSSL 1.1.1 is an LTS release upstream, which will continue to receive security support for much longer than 1.1.0 series will. * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be rapidly adopted due to increased set of supported hashes & algoes, as well as improved handshake [re-]negotiation. * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities. * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software is sensitive to the negotiation handshake and may either need patches/improvements or clamp-down to maximum v1.2. [Test Case] * Rebuild all reverse dependencies * Execute autopkg tests for all of them * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. mongodb) * Backport TLS v1.3 support patches, where applicable [Test cases for the python updates] python3.7 is a preview in bionic as a non-supported/non-default version of python3. Passing it's own autopkgtests is sufficient validation for python3.7. It includes a point release update, with OpenSSL 1.1.1 compat and features. python3.6 not only has OpenSSL 1.1.1 compat and features patches, but also includes a point release update to 3.6.8. It has been part of the full-archive rebuild and regression analysis. Autopkgtests were triggered for python3.6 and python3-defaults with regressions already fixed in the individual packages as appropriate. python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1 compat only. It has been part of the full-archive rebuild and regression analysis. Autopkgtests were triggered for python2.7 and python-defaults with regressions already fixed in the individual packages as appropriate. The archive rebuilds done, were commulative with OpenJDK 11, OpenSSL 1.1.1 and python point releases as seen in: http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-test-bionic.html And analyzed in https://docs.google.com/spreadsheets/d/1tMIwlwoHH_1h5sbvUbNac6-HIPKi3e0Xr8ebchIOU1A/edit#gid=147857652 [Regression Potential] * Connectivity interop is the biggest issues which will be unavoidable with introducing TLS v1.3. However, tests on cosmic demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3 without issues. * Mitigation of discovered connectivity issues will be possible by clamping down to TLS v1.2 in either server-side or client-side software or by backporting relevant support fixes * Notable changes are listed here https://wiki.openssl.org/index.php/TLS1.3 * Most common connectivity issues so far: - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. Solution is client change to set hostname, or to clamp down the client to TLSv1.2. - session negotiation is different in TLSv1.3, existing client code may fail to create/negotiate/resume session. Clients need to learn how to use session callback. - non-application data records. TLSv1.3 sends more of these, when compared with previous versions, and some applications may not handle this correctly. Resulting in application data not being available, when previously expected. Mitigation around these involve disabling/enabling SSL_MODE_AUTO_RETRY or setting max protocol version to TLSv1.2. For example see discussion identified in the perl stack https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914034 Similar hangs are possible with prior versions of TLS as well, it is however easier to trigger this with TLSv1.3. * Deprecated npn extenstion does not exist in TLSv1.3 implementation. * This update bundles python 3.6 and 3.7 point releases [Other Info] * Previous FFe for OpenSSL in 18.10 is at https://bugs.launchpad.net/ubu
[Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
** Bug watch removed: github.com/openssl/openssl/issues #3665 https://github.com/openssl/openssl/issues/3665 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1797386 Title: [SRU] OpenSSL 1.1.1 to 18.04 LTS Status in openssl package in Ubuntu: Fix Released Status in python-tornado package in Ubuntu: Confirmed Status in libio-socket-ssl-perl source package in Bionic: Incomplete Status in libnet-ssleay-perl source package in Bionic: Incomplete Status in openssl source package in Bionic: Fix Committed Status in python-cryptography source package in Bionic: Fix Committed Status in python2.7 source package in Bionic: Fix Committed Status in python3.6 source package in Bionic: Fix Committed Status in python3.7 source package in Bionic: Fix Committed Status in r-cran-openssl source package in Bionic: Fix Committed Status in ruby-openssl source package in Bionic: Fix Committed Status in ruby2.5 source package in Bionic: Confirmed Bug description: [Impact] * OpenSSL 1.1.1 is an LTS release upstream, which will continue to receive security support for much longer than 1.1.0 series will. * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be rapidly adopted due to increased set of supported hashes & algoes, as well as improved handshake [re-]negotiation. * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities. * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software is sensitive to the negotiation handshake and may either need patches/improvements or clamp-down to maximum v1.2. [Test Case] * Rebuild all reverse dependencies * Execute autopkg tests for all of them * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. mongodb) * Backport TLS v1.3 support patches, where applicable [Test cases for the python updates] python3.7 is a preview in bionic as a non-supported/non-default version of python3. Passing it's own autopkgtests is sufficient validation for python3.7. It includes a point release update, with OpenSSL 1.1.1 compat and features. python3.6 not only has OpenSSL 1.1.1 compat and features patches, but also includes a point release update to 3.6.8. It has been part of the full-archive rebuild and regression analysis. Autopkgtests were triggered for python3.6 and python3-defaults with regressions already fixed in the individual packages as appropriate. python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1 compat only. It has been part of the full-archive rebuild and regression analysis. Autopkgtests were triggered for python2.7 and python-defaults with regressions already fixed in the individual packages as appropriate. The archive rebuilds done, were commulative with OpenJDK 11, OpenSSL 1.1.1 and python point releases as seen in: http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-test-bionic.html And analyzed in https://docs.google.com/spreadsheets/d/1tMIwlwoHH_1h5sbvUbNac6-HIPKi3e0Xr8ebchIOU1A/edit#gid=147857652 [Regression Potential] * Connectivity interop is the biggest issues which will be unavoidable with introducing TLS v1.3. However, tests on cosmic demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3 without issues. * Mitigation of discovered connectivity issues will be possible by clamping down to TLS v1.2 in either server-side or client-side software or by backporting relevant support fixes * Notable changes are listed here https://wiki.openssl.org/index.php/TLS1.3 * Most common connectivity issues so far: - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. Solution is client change to set hostname, or to clamp down the client to TLSv1.2. - session negotiation is different in TLSv1.3, existing client code may fail to create/negotiate/resume session. Clients need to learn how to use session callback. - non-application data records. TLSv1.3 sends more of these, when compared with previous versions, and some applications may not handle this correctly. Resulting in application data not being available, when previously expected. Mitigation around these involve disabling/enabling SSL_MODE_AUTO_RETRY or setting max protocol version to TLSv1.2. For example see discussion identified in the perl stack https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914034 Similar hangs are possible with prior versions of TLS as well, it is however easier to trigger this with TLSv1.3. * Deprecated npn extenstion does not exist in TLSv1.3 implementation. * This update bundles python 3.6 and 3.7 point releases [Other Info] * Previous FFe for OpenSSL in 18.10 is at https://bug
[Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
** Bug watch removed: github.com/openssl/openssl/issues #8055 https://github.com/openssl/openssl/issues/8055 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1797386 Title: [SRU] OpenSSL 1.1.1 to 18.04 LTS Status in openssl package in Ubuntu: Fix Released Status in python-tornado package in Ubuntu: Confirmed Status in libio-socket-ssl-perl source package in Bionic: Incomplete Status in libnet-ssleay-perl source package in Bionic: Incomplete Status in openssl source package in Bionic: Fix Committed Status in python-cryptography source package in Bionic: Fix Committed Status in python2.7 source package in Bionic: Fix Committed Status in python3.6 source package in Bionic: Fix Committed Status in python3.7 source package in Bionic: Fix Committed Status in r-cran-openssl source package in Bionic: Fix Committed Status in ruby-openssl source package in Bionic: Fix Committed Status in ruby2.5 source package in Bionic: Confirmed Bug description: [Impact] * OpenSSL 1.1.1 is an LTS release upstream, which will continue to receive security support for much longer than 1.1.0 series will. * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be rapidly adopted due to increased set of supported hashes & algoes, as well as improved handshake [re-]negotiation. * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities. * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software is sensitive to the negotiation handshake and may either need patches/improvements or clamp-down to maximum v1.2. [Test Case] * Rebuild all reverse dependencies * Execute autopkg tests for all of them * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. mongodb) * Backport TLS v1.3 support patches, where applicable [Test cases for the python updates] python3.7 is a preview in bionic as a non-supported/non-default version of python3. Passing it's own autopkgtests is sufficient validation for python3.7. It includes a point release update, with OpenSSL 1.1.1 compat and features. python3.6 not only has OpenSSL 1.1.1 compat and features patches, but also includes a point release update to 3.6.8. It has been part of the full-archive rebuild and regression analysis. Autopkgtests were triggered for python3.6 and python3-defaults with regressions already fixed in the individual packages as appropriate. python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1 compat only. It has been part of the full-archive rebuild and regression analysis. Autopkgtests were triggered for python2.7 and python-defaults with regressions already fixed in the individual packages as appropriate. The archive rebuilds done, were commulative with OpenJDK 11, OpenSSL 1.1.1 and python point releases as seen in: http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-test-bionic.html And analyzed in https://docs.google.com/spreadsheets/d/1tMIwlwoHH_1h5sbvUbNac6-HIPKi3e0Xr8ebchIOU1A/edit#gid=147857652 [Regression Potential] * Connectivity interop is the biggest issues which will be unavoidable with introducing TLS v1.3. However, tests on cosmic demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3 without issues. * Mitigation of discovered connectivity issues will be possible by clamping down to TLS v1.2 in either server-side or client-side software or by backporting relevant support fixes * Notable changes are listed here https://wiki.openssl.org/index.php/TLS1.3 * Most common connectivity issues so far: - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. Solution is client change to set hostname, or to clamp down the client to TLSv1.2. - session negotiation is different in TLSv1.3, existing client code may fail to create/negotiate/resume session. Clients need to learn how to use session callback. - non-application data records. TLSv1.3 sends more of these, when compared with previous versions, and some applications may not handle this correctly. Resulting in application data not being available, when previously expected. Mitigation around these involve disabling/enabling SSL_MODE_AUTO_RETRY or setting max protocol version to TLSv1.2. For example see discussion identified in the perl stack https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914034 Similar hangs are possible with prior versions of TLS as well, it is however easier to trigger this with TLSv1.3. * Deprecated npn extenstion does not exist in TLSv1.3 implementation. * This update bundles python 3.6 and 3.7 point releases [Other Info] * Previous FFe for OpenSSL in 18.10 is at https://bug
[Touch-packages] [Bug 1828215] Re: openssl ca -spkac output regressed
** Changed in: openssl (Ubuntu Bionic) Importance: Undecided => High ** Changed in: openssl (Ubuntu Cosmic) Importance: Undecided => High ** Changed in: openssl (Ubuntu Disco) Importance: Undecided => High ** Changed in: openssl (Ubuntu Eoan) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1828215 Title: openssl ca -spkac output regressed Status in OpenSSL: Fix Released Status in openssl package in Ubuntu: Confirmed Status in openssl source package in Bionic: Confirmed Status in openssl source package in Cosmic: Confirmed Status in openssl source package in Disco: Confirmed Status in openssl source package in Eoan: Confirmed Bug description: [Impact] * openssl command line utility option parsing has regressed in 1.1.0i+ and produces binary output, where text output is expected, breaking applications that parse that. [Test Case] * OPENSSL_ENABLE_MD5_VERIFY=1 openssl ca -config test.openssl.cnf -passin stdin -batch -spkac input_file -startdate 190121130654Z Currently produces binary goop. Should produce PEM format Base64 encoded certificate data in a block surrounded with BEGIN/END certificate. [Regression Potential] * This is a regression in cosmic and up, and impeding regression in bionic with the upcoming 1.1.1 SRU. A bugfix exists upstream. [Other Info] * Originally reported https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/comments/39 To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1828215/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
I'm experiencing the same that Gaute in Ubuntu 18.04.2 LTS: Suspending on closing the lid is only working without the external monitor connected, no matter what I try to configure. -- 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/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 Status in systemd package in Ubuntu: Confirmed Bug description: My notebook does not suspend after upgrading from 15.10 to 16.04. According to system settings the notebook should suspend when lid is closed but actually this does not happen. Instead it continues to run as if nothing had happened. With the previous versions of ubuntu (14.04-15.10) everything worked fine. My System: HP Pavilion dv7. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 23:11:15 2016 InstallationDate: Installed on 2015-10-29 (176 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: acpi UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1574120/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
This affects bionic openstack cloud environments when os-*-hostname is configured for keystone, and the keystone entry is deleted temporarily from upstream dns, or the upstream dns fails providing no record for the lookup of keystone.endpoint.domain.com. We have to then flush all caches across the cloud once DNS issue is resolved, rather than auto-healing at 60 seconds as if we were running nscd with negative-ttl set to 60 seconds. Ultimately, a negative TTL that is settable would be ideal, or the ability to not cache negative hits would also be useful. Only workaround now is to not use caches or to operationally flush caches as needed. -- 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: Confirmed 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 1668771] Re: systemd-resolved negative caching for extended period of time
This is especially upsetting in an OpenStack and server environment where external DNS is being used to reach/resolve API endpoints and other systems such as database servers. A small outage to DNS becomes a potentially unbounded outage when the SERVFAIL responses are cached indefinitely, requiring manual intervention on each host in addition to fixing the cause of the SERVFAIL. ** Tags added: canonical-bootstack -- 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: Confirmed 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 1830283] [NEW] Xorg freeze
Public bug reported: 1 have worked in my projects then my ubuntu froze suddenly ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 24 02:20:15 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Today GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:2213] InstallationDate: Installed on 2019-04-01 (52 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 001 Device 004: ID 0bda:b001 Realtek Semiconductor Corp. Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=1dbcbc41-3811-4525-8a07-83de047700c3 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2213 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd09/19/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr096C11405F00050660180:rvnHewlett-Packard:rn2213:rvr57.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 Notebook PC dmi.product.version: 096C11405F00050660180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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/1830283 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: 1 have worked in my projects then my ubuntu froze suddenly ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 24 02:20:15 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Today GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:2213] InstallationDate: Installed on 2019-04-01 (52 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam Bus 001 Device 004: ID 0bda:b001 Realtek Semiconductor Corp. Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=1dbcbc41-3811-4525-8a07-83de047700c3 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display
[Touch-packages] [Bug 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1823872 Title: Fixing fsfreeze-hook can break unattended upgrades Status in qemu package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Confirmed Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Cosmic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: [Impact] * If an update has a new conffile at a path that in a former version was a directory like old: /a/b/c new: a/b Here b is the new file name and was a directory in the old version. Then unattended upgrades breaks on installing such a package. * a recent qemu update has such a case and due to that triggered the issue in >=Bionic * The fix is to harden unattended upgrades to be able to handle the case without aborting. [Test Case] Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12 That can be done with: $ time uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic label=daily Log in and apt update & upgrade all packages, then Install the release level qemu in there. $ uvt-kvm ssh bionic-testuu $ sudo apt update $ sudo apt dist-upgrade $ sudo apt install unattended-upgrades $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7 All before was preparation, now force the unattended upgrade to trigger the bug. $ sudo unattended-upgrade -d With the bug you'll find some error like: found pkg: qemu-guest-agent conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191 current md5: f61a64ac1e48993023018fd1cff85191 conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 15f6ff42cbc5550a07ee21c2a471d905 /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles /etc/init.d/qemu-guest-agent /etc/qemu/fsfreeze-hook found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2057, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1773, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' [Regression Potential] * The fix is trying to detect moved conffiles by looking for /etc/foo/foo when the new package ships /etc/foo and /etc/foo is not a known conffile and also checking the renames in the opposite direction. The potential regression is breaking the logic for detecting changed conffiles and either holding back a package for no reason or trying to install a package with a modified conffile on the system and aborting the upgrade in the middle due to the appearing conffile prompt. To avoid such regressions the test_conffile.py tests are extended to cover rename scenarios. [Other Info] * n/a --- As reported on https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20 We fixed an issue and we added workrounds since basic mv_conffile coudn't handle it and did all sort of upgrade tests. That all worked fine and moved the conffile. It was now reported that due to some pre-checks that unattended upgrades might do this might do some checks on its own. Next step: - check unattended upgrades through this change - check if it only affects cases were the former config was modified (minority) or the default file layout (majority) --- original report copied --- just wanted to add: This bug also crashes unattended-upgrade and thus prevents security updates on 18.04: root@mailin1:~# unattended-upgrade Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1998, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1714, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' Basically, unattended-upgrade wants to compare old/new conffiles and doesn't like it when the old conffile turns out to be a directory... This prevents security updates to be installed. The unattended-upgrade logs do not contain the trace, only the messages: 2019-04-05 13:24:24,851 INFO Initial blackli
[Touch-packages] [Bug 1540587] Re: No UK keyboard support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1540587 Title: No UK keyboard support Status in ibus package in Ubuntu: Confirmed Bug description: UK keyboard is NOT available as an input method in uBuntu 14.04 LTS ibus (1.5.5-1ubuntu3) input method selection. Please can someone fix this omission by adding the appropriate info to /usr/share/ibus/component/simple.xml as having the system incorrectly default to a US keyboard is a real pain - you can't put anything in quotes or pipe output from one command into another. It makes a UK keyboard system unusable. My simple solution is to add the 'gb' keyboard as follows: xkb:gb::eng eng GPL gb English (UK) English (UK) ibus-keyboard 99 A better solution would be to process files in /usr/share/X11/xkb/symbols and add ALL available xkb keyboards to simple.xml as a post installation operation. Doing this would help people see the advantages of ibus instead of fighting it to try and get a usable system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1540587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830272] Re: /usr/bin/software-properties-gtk:SyntaxError:/usr/bin/software-properties-gtk@37:/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py@35
The traceback is actually in aptdaemon: Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 37, in from softwareproperties.gtk.SoftwarePropertiesGtk import SoftwarePropertiesGtk File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 35, in from aptdaemon import client File "/usr/lib/python3/dist-packages/aptdaemon/client.py", line 1570 async = reply_handler and error_handler ^ SyntaxError: invalid syntax ** Package changed: software-properties (Ubuntu) => aptdaemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1830272 Title: /usr/bin/software-properties-gtk:SyntaxError:/usr/bin/software- properties-gtk@37:/usr/lib/python3/dist- packages/softwareproperties/gtk/SoftwarePropertiesGtk.py@35 Status in aptdaemon package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.97.11, the problem page at https://errors.ubuntu.com/problem/bcd4cb93a6d3f4bb93cc6ea7534e293f4a744849 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/aptdaemon/+bug/1830272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813268] [evolution-data-server/cosmic] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for cosmic for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1813268 Title: connection issues with Kopano IMAP servers Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Cosmic: Fix Committed Bug description: * Impact Evolution doesn't work with Kopano IMAP servers: * Test case Configure an account on a Kopano IMAP server and try to use it from evolution * Regression potential The change is in the imap handling code so it would be good to test on a few different type of server that things still work correctly - 3.30.1-1 has the following issue with Kopano IMAP servers: Disable request of BODYSTRUCTURE when its response is broken https://gitlab.gnome.org/GNOME/evolution-data-server/issues/37 In 3.30.4-1 it's fixed, so a backport to cosmic would be great. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1813268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815882] [evolution-data-server/cosmic] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for cosmic for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1815882 Title: Update evolution-data-server to 3.30.5 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Cosmic: Fix Committed Bug description: * Impact That's a new bug-fix only update from GNOME There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME https://gitlab.gnome.org/GNOME/evolution-data-server/blob/gnome-3-30/NEWS https://gitlab.gnome.org/GNOME/evolution-data-server/commits/gnome-3-30 * Test Case After installing the update, restart your computer. Run several eds-using apps like Evolution, GNOME Calendar and verify that they continue to run at least as well as before this update. * Regression Potential It's a new version with a bug of changes and fixes including in imap, calendar and gpg signing code so those features need to be well tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1815882/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830272] [NEW] /usr/bin/software-properties-gtk:SyntaxError:/usr/bin/software-properties-gtk@37:/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py@35
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.97.11, the problem page at https://errors.ubuntu.com/problem/bcd4cb93a6d3f4bb93cc6ea7534e293f4a744849 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: aptdaemon (Ubuntu) Importance: Undecided Status: New ** Tags: bionic disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1830272 Title: /usr/bin/software-properties-gtk:SyntaxError:/usr/bin/software- properties-gtk@37:/usr/lib/python3/dist- packages/softwareproperties/gtk/SoftwarePropertiesGtk.py@35 Status in aptdaemon package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.97.11, the problem page at https://errors.ubuntu.com/problem/bcd4cb93a6d3f4bb93cc6ea7534e293f4a744849 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/aptdaemon/+bug/1830272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604737] Re: headless installations are degraded due to failed setvtrgb.service
It looks to me like comment #2 may have been addressed with the following changes: https://salsa.debian.org/debian/kbd/commit/21fc74ec128fffe08ea75186c2c01b0f32eb3e1f -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1604737 Title: headless installations are degraded due to failed setvtrgb.service Status in console-setup package in Ubuntu: Fix Released Status in console-setup source package in Xenial: Won't Fix Bug description: s390x installations are degraded due to failed setvtrgb.service on z/vm, suspecting that it should be limited to just kvm on s390x, somehow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1604737/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812132] Re: Does not return results with files that have hyphens in the filename
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tracker (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1812132 Title: Does not return results with files that have hyphens in the filename Status in tracker package in Ubuntu: Confirmed Bug description: On Ubuntu 18.04 using the `vanilla-gnome-desktop` session (i.e. Gnome Shell), tracker does not return any files if there is a hyphen (-) in the search string. To recreate: - Create a file named `foo-bar`. - Press to open Overview. - Type foo. Observe that the `foo-bar` file appears. - Type foo-. Observe that the overview says "No results." This is a regression as files with hyphens in the filename were included in search results in 16.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1812132/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1823872 Title: Fixing fsfreeze-hook can break unattended upgrades Status in qemu package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Confirmed Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Cosmic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: [Impact] * If an update has a new conffile at a path that in a former version was a directory like old: /a/b/c new: a/b Here b is the new file name and was a directory in the old version. Then unattended upgrades breaks on installing such a package. * a recent qemu update has such a case and due to that triggered the issue in >=Bionic * The fix is to harden unattended upgrades to be able to handle the case without aborting. [Test Case] Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12 That can be done with: $ time uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic label=daily Log in and apt update & upgrade all packages, then Install the release level qemu in there. $ uvt-kvm ssh bionic-testuu $ sudo apt update $ sudo apt dist-upgrade $ sudo apt install unattended-upgrades $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7 All before was preparation, now force the unattended upgrade to trigger the bug. $ sudo unattended-upgrade -d With the bug you'll find some error like: found pkg: qemu-guest-agent conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191 current md5: f61a64ac1e48993023018fd1cff85191 conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 15f6ff42cbc5550a07ee21c2a471d905 /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles /etc/init.d/qemu-guest-agent /etc/qemu/fsfreeze-hook found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2057, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1773, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' [Regression Potential] * The fix is trying to detect moved conffiles by looking for /etc/foo/foo when the new package ships /etc/foo and /etc/foo is not a known conffile and also checking the renames in the opposite direction. The potential regression is breaking the logic for detecting changed conffiles and either holding back a package for no reason or trying to install a package with a modified conffile on the system and aborting the upgrade in the middle due to the appearing conffile prompt. To avoid such regressions the test_conffile.py tests are extended to cover rename scenarios. [Other Info] * n/a --- As reported on https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20 We fixed an issue and we added workrounds since basic mv_conffile coudn't handle it and did all sort of upgrade tests. That all worked fine and moved the conffile. It was now reported that due to some pre-checks that unattended upgrades might do this might do some checks on its own. Next step: - check unattended upgrades through this change - check if it only affects cases were the former config was modified (minority) or the default file layout (majority) --- original report copied --- just wanted to add: This bug also crashes unattended-upgrade and thus prevents security updates on 18.04: root@mailin1:~# unattended-upgrade Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1998, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1714, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' Basically, unattended-upgrade wants to compare old/new conffiles and doesn't like it when the old conffile turns out to be a directory... This prevents security updates to be installed. The unattended-upgrade logs do not contain the trace, only the messages: 2019-0
[Touch-packages] [Bug 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades
** Patch added: "qemu_2.11+dfsg-1ubuntu7.14.patch" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1823872/+attachment/5266072/+files/qemu_2.11+dfsg-1ubuntu7.14.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1823872 Title: Fixing fsfreeze-hook can break unattended upgrades Status in qemu package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Confirmed Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Cosmic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: [Impact] * If an update has a new conffile at a path that in a former version was a directory like old: /a/b/c new: a/b Here b is the new file name and was a directory in the old version. Then unattended upgrades breaks on installing such a package. * a recent qemu update has such a case and due to that triggered the issue in >=Bionic * The fix is to harden unattended upgrades to be able to handle the case without aborting. [Test Case] Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12 That can be done with: $ time uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic label=daily Log in and apt update & upgrade all packages, then Install the release level qemu in there. $ uvt-kvm ssh bionic-testuu $ sudo apt update $ sudo apt dist-upgrade $ sudo apt install unattended-upgrades $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7 All before was preparation, now force the unattended upgrade to trigger the bug. $ sudo unattended-upgrade -d With the bug you'll find some error like: found pkg: qemu-guest-agent conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191 current md5: f61a64ac1e48993023018fd1cff85191 conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 15f6ff42cbc5550a07ee21c2a471d905 /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles /etc/init.d/qemu-guest-agent /etc/qemu/fsfreeze-hook found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2057, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1773, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' [Regression Potential] * The fix is trying to detect moved conffiles by looking for /etc/foo/foo when the new package ships /etc/foo and /etc/foo is not a known conffile and also checking the renames in the opposite direction. The potential regression is breaking the logic for detecting changed conffiles and either holding back a package for no reason or trying to install a package with a modified conffile on the system and aborting the upgrade in the middle due to the appearing conffile prompt. To avoid such regressions the test_conffile.py tests are extended to cover rename scenarios. [Other Info] * n/a --- As reported on https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20 We fixed an issue and we added workrounds since basic mv_conffile coudn't handle it and did all sort of upgrade tests. That all worked fine and moved the conffile. It was now reported that due to some pre-checks that unattended upgrades might do this might do some checks on its own. Next step: - check unattended upgrades through this change - check if it only affects cases were the former config was modified (minority) or the default file layout (majority) --- original report copied --- just wanted to add: This bug also crashes unattended-upgrade and thus prevents security updates on 18.04: root@mailin1:~# unattended-upgrade Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1998, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1714, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' Basically, unattended-upgrade wants to compare old/new conffiles and doesn't like it when the old conffile turns out to be a directory... This prevents se
[Touch-packages] [Bug 1823872] Re: Fixing fsfreeze-hook can break unattended upgrades
Please add Breaks: unattended-upgrades (<< 1.1ubuntu1.18.04.11) to qemu- guest-agent for Bionic and similar breaks for other affected releases to prevent unfixed u-u from considering the upgrade the package. This allows installation of other security fixes. ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1823872 Title: Fixing fsfreeze-hook can break unattended upgrades Status in qemu package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Confirmed Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Cosmic: Fix Released Status in unattended-upgrades source package in Disco: Fix Released Bug description: [Impact] * If an update has a new conffile at a path that in a former version was a directory like old: /a/b/c new: a/b Here b is the new file name and was a directory in the old version. Then unattended upgrades breaks on installing such a package. * a recent qemu update has such a case and due to that triggered the issue in >=Bionic * The fix is to harden unattended upgrades to be able to handle the case without aborting. [Test Case] Get a qemu guest e.g. of Bionic before the update to 1:2.11+dfsg-1ubuntu7.12 That can be done with: $ time uvt-simplestreams-libvirt --verbose sync --source http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=bionic $ uvt-kvm create --password ubuntu bionic-testuu arch=amd64 release=bionic label=daily Log in and apt update & upgrade all packages, then Install the release level qemu in there. $ uvt-kvm ssh bionic-testuu $ sudo apt update $ sudo apt dist-upgrade $ sudo apt install unattended-upgrades $ sudo apt install qemu-guest-agent=1:2.11+dfsg-1ubuntu7 All before was preparation, now force the unattended upgrade to trigger the bug. $ sudo unattended-upgrade -d With the bug you'll find some error like: found pkg: qemu-guest-agent conffile line: /etc/init.d/qemu-guest-agent f61a64ac1e48993023018fd1cff85191 current md5: f61a64ac1e48993023018fd1cff85191 conffile line: /etc/qemu/fsfreeze-hook/fsfreeze-hook 15f6ff42cbc5550a07ee21c2a471d905 /etc/qemu/fsfreeze-hook/fsfreeze-hook not in package conffiles /etc/init.d/qemu-guest-agent /etc/qemu/fsfreeze-hook found conffile /etc/qemu/fsfreeze-hook in new pkg but on dpkg status Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 2057, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1773, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 988, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook' [Regression Potential] * The fix is trying to detect moved conffiles by looking for /etc/foo/foo when the new package ships /etc/foo and /etc/foo is not a known conffile and also checking the renames in the opposite direction. The potential regression is breaking the logic for detecting changed conffiles and either holding back a package for no reason or trying to install a package with a modified conffile on the system and aborting the upgrade in the middle due to the appearing conffile prompt. To avoid such regressions the test_conffile.py tests are extended to cover rename scenarios. [Other Info] * n/a --- As reported on https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1820291/comments/20 We fixed an issue and we added workrounds since basic mv_conffile coudn't handle it and did all sort of upgrade tests. That all worked fine and moved the conffile. It was now reported that due to some pre-checks that unattended upgrades might do this might do some checks on its own. Next step: - check unattended upgrades through this change - check if it only affects cases were the former config was modified (minority) or the default file layout (majority) --- original report copied --- just wanted to add: This bug also crashes unattended-upgrade and thus prevents security updates on 18.04: root@mailin1:~# unattended-upgrade Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1998, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1714, in main if conffile_prompt(item.destfile): File "/usr/bin/unattended-upgrade", line 929, in conffile_prompt with open(prefix + conf_file, 'rb') as fp: IsADirectoryError: [Errno 21] Is a directory: '/etc/qemu/fsfreeze-hook'
[Touch-packages] [Bug 1783283] Re: setvtrgb.service incorrectly ordered [with patchy]
If this is racy, then it should be possible to trigger it reliably by adding sleep commands to one or more units. I have looked at the topology of the base units in Ubuntu and I don't see any bugs. I don't understand your assertion that After=plymouth- quit-wait.service is insufficient or why you refer to plymouth-quit being queued "instead" of plymouth-quit-wait, which I do not see as a possible outcome of the unit dependencies. And if there is something to be fixed here, I think it's the reliability of the plymouth-quit-wait dependency, not changing the dependency of setvtrgb. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1783283 Title: setvtrgb.service incorrectly ordered [with patchy] Status in console-setup package in Ubuntu: Incomplete Bug description: setvtrgb is not correctly ordered when used with plymouth. It has an After=plymouth-quit-wait.service, but that may not be applicable when plymouth-quit.service is queued instead. This ultimately results in semi-random setvtrgb results as calling setvtrgb too soon will do nothing if the VTs aren't up/still getting fiddled with with by plymouth. So, depending on the unit tree the VT may have the correct custom color, or the default kernel color. Since this is entirely dependent on the units being started, and their effective order, this is super hard to reproduce reliably. The most reliable way I have is an ISO which has Calamares instead of Ubiquity and SDDM instead of GDM, which 100% of the time ends up having a unit order where setvtrgb is called way too soon (even before getty.target, although I am not sure that matters as far as the VT colors are concerned). The solution seems excitingly simple though. Adding an After=plymouth- quit.service rule correctly orders the unit at least in my test case. Since After is only an order hint this should be entirely regression free. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1783283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823398] Re: setvtrgb causes boot delays in clouds
I've created multiple disco Google GCE instances of type N1_Standard_2 and checked how much time setvtrgb.service took using "systemd-analyze blame | grep setvtrgb" and while there was some variance I never saw a result greater 500ms. Given that this isn't a significant amount of time I'm going to close this bug as Invalid. ** Changed in: console-setup (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1823398 Title: setvtrgb causes boot delays in clouds Status in console-setup package in Ubuntu: Invalid Bug description: systemd-analyze output of cloud images shows that setvtrgb.service can take a measureable amount of time to complete. Setting the color pallete for a graphical console on a cloud instance that we have no graphical console access to is not something that should be allowed to slow down boot. Reproduced with disco on a Google GCE instance of type N1_Standard_2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1823398/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1353013] Re: Popping/Crackling sound when playing audio in Ubuntu 14.04
I'm seeing this bug in Linux Mint 19.1 (Ubuntu 18.04 base). The audio devices do not appear and disappear in the "Sounds" GUI. The workaround I've found is to do this in a terminal: pulseaudio -k && sleep 5 ; pulseaudio -D Sometimes this works for hours, and sometimes it works for minutes, after killing/restarting the PulseAudio daemon, as above. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1353013 Title: Popping/Crackling sound when playing audio in Ubuntu 14.04 Status in nvidia-hdmi-pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When listening to audio (pandora internet radio, youtube, etc.), I get a repeated popping/crackling sound. When I look at the sound settings while this is happening, I see "Headphone Output" rapidly appearing and then disappearing in the "Play Sound Through" section. The appearance and disappearance of "Headphone Output" coincides with the popping and crackling of the sound. I am wondering if it has anything to do with the fact that my Nvidia card has a built-in HDMI card that might be interfering with my onboard sound: $ cat /proc/asound/cards 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xf722 irq 54 1 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xf708 irq 55 cat /proc/asound/modules 0 snd_hda_intel 1 snd_hda_intel Obviously blacklisting "snd_hda_intel" in /etc/modprobe.d/blacklist.conf won't work, because it then disables all sound (both onboard and nvidia are listed as snd_hda_intel). Description: Ubuntu 14.04.1 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim1856 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 5 10:17:34 2014 InstallationDate: Installed on 2014-04-17 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0132.2011.1007.1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-205 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0132.2011.1007.1505:bd10/07/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-205:cvn:ct3:cvr: modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2014-08-04T12:00:53.999120 mtime.conffile..etc.pulse.default.pa: 2014-08-04T12:18:08.532386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-hdmi-pulseaudio/+bug/1353013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829401] Re: /usr/bin/software-properties-gtk:TypeError:on_pktask_finish:on_pktask_finish:new_init:__init__:new_init:__init__:new_init
** Also affects: packagekit (Ubuntu Eoan)
Importance: Medium
Status: Triaged
** Tags removed: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1829401
Title:
gi.repository.GLib.GError: pk-client-error-quark: could not do
untrusted question as no klass support
Status in packagekit package in Ubuntu:
Triaged
Status in packagekit source package in Eoan:
Triaged
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.98.2, the problem page at
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d
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/.
[Back trace]
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted
question as no klass support (8)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 89, in on_pktask_finish
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support
** Summary changed:
-
/usr/bin/software-properties-gtk:TypeError:on_pktask_finish:on_pktask_finish:new_init:__init__:new_init:__init__:new_init
+ gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted
question as no klass support
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1829401
Title:
gi.repository.GLib.GError: pk-client-error-quark: could not do
untrusted question as no klass support
Status in packagekit package in Ubuntu:
Triaged
Status in packagekit source package in Eoan:
Triaged
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.98.2, the problem page at
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d
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/.
[Back trace]
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted
question as no klass support (8)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 89, in on_pktask_finish
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829401] Re: /usr/bin/software-properties-gtk:TypeError:on_pktask_finish:on_pktask_finish:new_init:__init__:new_init:__init__:new_init
** Changed in: packagekit (Ubuntu)
Importance: Undecided => Medium
** Changed in: packagekit (Ubuntu)
Status: New => Incomplete
** Changed in: packagekit (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1829401
Title:
/usr/bin/software-properties-
gtk:TypeError:on_pktask_finish:on_pktask_finish:new_init:__init__:new_init:__init__:new_init
Status in packagekit package in Ubuntu:
Triaged
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
software-properties. This problem was most recently seen with package version
0.98.2, the problem page at
https://errors.ubuntu.com/problem/300ff7bf9068dc50ace4c5db5c4a34ba0dfc926d
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/.
[Back trace]
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 86, in on_pktask_finish
results = self._pktask.generic_finish(result)
gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted
question as no klass support (8)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py",
line 89, in on_pktask_finish
Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in
__init__
self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in
__init__
_window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319,
in new_init
return super_init_func(self, **new_kwargs)
TypeError: could not convert value for property `transient_for' from
DialogCacheOutdated to GtkWindow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 997758] Re: gnome battery indicator missing in 12.04/12.10
Can anyone tell me that the daemon version 0.9.17 is compatible with windows 10 because I am getting windows update error 80070103 continuously for that I also checked https://errorcode0x.com/windows- update-error-80070103/ but did not get the valid solution to fix this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/997758 Title: gnome battery indicator missing in 12.04/12.10 Status in indicator-power package in Ubuntu: Confirmed Bug description: This is 12.04 Precise, with Unity turned off, using Gnome. Multiple users are reporting the panel battery indicator is missing. http://ubuntuforums.org/showthread.php?p=11924048#post11924048 indicator-power is installed Perhaps realated: System Settings -> Power Show battery status in the menu bar is blank when the window opens, but non-blank values don't take. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: indicator-power 2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic i686 ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Thu May 10 20:56:22 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: indicator-power UpgradeStatus: Upgraded to precise on 2012-05-09 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/997758/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828282] Re: busybox 1.30.1 crashes bzip2 test case with glibc 2.29, always
** Changed in: busybox (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1828282 Title: busybox 1.30.1 crashes bzip2 test case with glibc 2.29, always Status in BusyBox: Confirmed Status in Ubuntu on IBM z Systems: Invalid Status in busybox package in Ubuntu: Fix Committed Status in glibc package in Ubuntu: Invalid Bug description: Steps to reproduce: 1) Get a system with glibc 2.29 2) Get busybox 1.30.1 installed (e.g. eoan, or download busybox package from https://launchpad.net/ubuntu/+source/busybox/1:1.30.1-4ubuntu3/+build/16724246 and use $ apt install ./busybox*.deb to install) 3) Get busybox 1.30.1 source code, e.g. $ pull-lp-source busybox Or like download the orig tarball from https://launchpad.net/ubuntu/+source/busybox/1:1.30.1-4ubuntu3 4) Run the bunzip2 testsuite: cd testsuite/ ECHO=/bin/echo ./bunzip2.tests Observe that with glibc 2.29 the: PASS: bunzip2: bz2_issue_11.bz2 corrupted example is XFAIL or FAIL, on s390x, whereas it passes on all other arches. If one uses glibc 2.28 (ie. use Cosmic, and install busybox & use matching test suite from eoan using links above) one can observe that the testcase always passes. We suspect this might be a glibc 2.29 s390x-specific setjmp regression. Probably due to setjmp usage in ./archival/libarchive/decompress_bunzip2.c The tests were done on a z13 machine. To manage notifications about this bug go to: https://bugs.launchpad.net/busybox/+bug/1828282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830022] Re: DirtyCleanInterval should be 0 by default
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu Disco) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1830022 Title: DirtyCleanInterval should be 0 by default Status in cups package in Ubuntu: Confirmed Status in cups source package in Xenial: Confirmed Status in cups source package in Bionic: Confirmed Status in cups source package in Cosmic: Confirmed Status in cups source package in Disco: Confirmed Bug description: Please consider changing DirtyCleanInterval value to 0 as default. Otherwise if cupsd crashes due to (e.g. OOM killer) under a heavy workload even hundreds of jobs may be lost. This concern is backed up by a real-life scenario and leaves the client sending thousands of jobs unaware that many of them are lost during a crash. After cupsd gets restarted it rewinds it's job counter to the last cached and continues unaware about the jobs accepted and lost. Having DirtyCleanInterval set to 0 will cause some performance impact, but not significant under lighter workloads and a completely justified price for reliability under heavy workloads. Test scenario: 1. sudo apt install printer-driver-cups-pdf 2. while [ 1 ]; do lp -d PDF somepdf.pdf; done; 3. # on other terminal kill -9 $(pidof cupsd) 4. Note last job number and wait for cupsd to be restarted by systemd. 5. Once accepting jobs is resumend the job counter is rewound. Expected behavior: Accepted jobs are queued for processing. Actual behavior: Some accepted jobs are lost. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1830022/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
I have a NVIDIA Corporation GP107 [GeForce GTX 1050] card and ubuntu 19.04 installed. After installing the lastest Nvidia driver-430, the dektop GUI is lost when you reboot (18.10 gave the same issue). I tried many proposed solutions, including the one above. Nothing worked. I finally found a solution for this Nvidia driver issue (on ubuntu 18 and 19). See instructions at the top at https://ubuntuforums.org/showthread.php?t=2419319&highlight=nvidia+drivers, it worked for me! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830022] Re: DirtyCleanInterval should be 0 by default
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu Cosmic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1830022 Title: DirtyCleanInterval should be 0 by default Status in cups package in Ubuntu: Confirmed Status in cups source package in Xenial: Confirmed Status in cups source package in Bionic: Confirmed Status in cups source package in Cosmic: Confirmed Status in cups source package in Disco: Confirmed Bug description: Please consider changing DirtyCleanInterval value to 0 as default. Otherwise if cupsd crashes due to (e.g. OOM killer) under a heavy workload even hundreds of jobs may be lost. This concern is backed up by a real-life scenario and leaves the client sending thousands of jobs unaware that many of them are lost during a crash. After cupsd gets restarted it rewinds it's job counter to the last cached and continues unaware about the jobs accepted and lost. Having DirtyCleanInterval set to 0 will cause some performance impact, but not significant under lighter workloads and a completely justified price for reliability under heavy workloads. Test scenario: 1. sudo apt install printer-driver-cups-pdf 2. while [ 1 ]; do lp -d PDF somepdf.pdf; done; 3. # on other terminal kill -9 $(pidof cupsd) 4. Note last job number and wait for cupsd to be restarted by systemd. 5. Once accepting jobs is resumend the job counter is rewound. Expected behavior: Accepted jobs are queued for processing. Actual behavior: Some accepted jobs are lost. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1830022/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830022] Re: DirtyCleanInterval should be 0 by default
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1830022 Title: DirtyCleanInterval should be 0 by default Status in cups package in Ubuntu: Confirmed Status in cups source package in Xenial: Confirmed Status in cups source package in Bionic: Confirmed Status in cups source package in Cosmic: Confirmed Status in cups source package in Disco: Confirmed Bug description: Please consider changing DirtyCleanInterval value to 0 as default. Otherwise if cupsd crashes due to (e.g. OOM killer) under a heavy workload even hundreds of jobs may be lost. This concern is backed up by a real-life scenario and leaves the client sending thousands of jobs unaware that many of them are lost during a crash. After cupsd gets restarted it rewinds it's job counter to the last cached and continues unaware about the jobs accepted and lost. Having DirtyCleanInterval set to 0 will cause some performance impact, but not significant under lighter workloads and a completely justified price for reliability under heavy workloads. Test scenario: 1. sudo apt install printer-driver-cups-pdf 2. while [ 1 ]; do lp -d PDF somepdf.pdf; done; 3. # on other terminal kill -9 $(pidof cupsd) 4. Note last job number and wait for cupsd to be restarted by systemd. 5. Once accepting jobs is resumend the job counter is rewound. Expected behavior: Accepted jobs are queued for processing. Actual behavior: Some accepted jobs are lost. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1830022/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820691] Re: WSL give error in installing (required for openfoam installtion)
Please try running: apt-get clean apt-get update apt-get install openfoam This should clean the local cache and try installing openfoam again. It works for me in Ubuntu on WSL. ** Changed in: libxt (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxt in Ubuntu. https://bugs.launchpad.net/bugs/1820691 Title: WSL give error in installing (required for openfoam installtion) Status in libxt package in Ubuntu: Invalid Bug description: To use OpenFOAM in windows I have to install OpenFOAM in WSL(windows subsystem for Linux) OpenFOAM is highly depended on libXt-dev version 1.1.5_1, while direct installing it from the terminal or from synaptic package manager it gives me a hash mismatch error. so I try to install it with downloading .deb file from the Ubuntu repository but it gives me a lzma error telling that archive is corrupt. so please help to install these packages; so, I can install OpenFOAM and continue my work. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxt/+bug/1820691/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830022] Re: DirtyCleanInterval should be 0 by default
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1830022 Title: DirtyCleanInterval should be 0 by default Status in cups package in Ubuntu: Confirmed Status in cups source package in Xenial: Confirmed Status in cups source package in Bionic: Confirmed Status in cups source package in Cosmic: Confirmed Status in cups source package in Disco: Confirmed Bug description: Please consider changing DirtyCleanInterval value to 0 as default. Otherwise if cupsd crashes due to (e.g. OOM killer) under a heavy workload even hundreds of jobs may be lost. This concern is backed up by a real-life scenario and leaves the client sending thousands of jobs unaware that many of them are lost during a crash. After cupsd gets restarted it rewinds it's job counter to the last cached and continues unaware about the jobs accepted and lost. Having DirtyCleanInterval set to 0 will cause some performance impact, but not significant under lighter workloads and a completely justified price for reliability under heavy workloads. Test scenario: 1. sudo apt install printer-driver-cups-pdf 2. while [ 1 ]; do lp -d PDF somepdf.pdf; done; 3. # on other terminal kill -9 $(pidof cupsd) 4. Note last job number and wait for cupsd to be restarted by systemd. 5. Once accepting jobs is resumend the job counter is rewound. Expected behavior: Accepted jobs are queued for processing. Actual behavior: Some accepted jobs are lost. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1830022/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830022] Re: DirtyCleanInterval should be 0 by default
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1830022 Title: DirtyCleanInterval should be 0 by default Status in cups package in Ubuntu: Confirmed Status in cups source package in Xenial: Confirmed Status in cups source package in Bionic: Confirmed Status in cups source package in Cosmic: Confirmed Status in cups source package in Disco: Confirmed Bug description: Please consider changing DirtyCleanInterval value to 0 as default. Otherwise if cupsd crashes due to (e.g. OOM killer) under a heavy workload even hundreds of jobs may be lost. This concern is backed up by a real-life scenario and leaves the client sending thousands of jobs unaware that many of them are lost during a crash. After cupsd gets restarted it rewinds it's job counter to the last cached and continues unaware about the jobs accepted and lost. Having DirtyCleanInterval set to 0 will cause some performance impact, but not significant under lighter workloads and a completely justified price for reliability under heavy workloads. Test scenario: 1. sudo apt install printer-driver-cups-pdf 2. while [ 1 ]; do lp -d PDF somepdf.pdf; done; 3. # on other terminal kill -9 $(pidof cupsd) 4. Note last job number and wait for cupsd to be restarted by systemd. 5. Once accepting jobs is resumend the job counter is rewound. Expected behavior: Accepted jobs are queued for processing. Actual behavior: Some accepted jobs are lost. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1830022/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825591] Re: Ubuntu 18.04 LTS (WSL) fails to launch in Windows 10 1903
I checked the feedback in the Feedback Hub and there is not any more information there either about the issue. The issue seems to be in WSL, not in Ubuntu and it can't be fixed in Ubuntu packages. :-( ** Changed in: wslu Status: New => Invalid ** Changed in: systemd (Ubuntu) Status: New => Invalid ** No longer affects: systemd (Ubuntu) ** Project changed: systemd => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1825591 Title: Ubuntu 18.04 LTS (WSL) fails to launch in Windows 10 1903 Status in wslu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: Ubuntu 18.04 LTS for WSL, official Microsoft Store package by Canonical, fails to open at all on Windows 10 May 2019 Feature Update. Link to issue in Microsoft Feedback Hub: https://aka.ms/AA4ubdp To manage notifications about this bug go to: https://bugs.launchpad.net/wslu/+bug/1825591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825591] [NEW] Ubuntu 18.04 LTS (WSL) fails to launch in Windows 10 1903
You have been subscribed to a public bug: Ubuntu 18.04 LTS for WSL, official Microsoft Store package by Canonical, fails to open at all on Windows 10 May 2019 Feature Update. Link to issue in Microsoft Feedback Hub: https://aka.ms/AA4ubdp ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: wslu Importance: Undecided Status: Invalid ** Tags: package store windows10 wsl -- Ubuntu 18.04 LTS (WSL) fails to launch in Windows 10 1903 https://bugs.launchpad.net/bugs/1825591 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828282] Re: busybox 1.30.1 crashes bzip2 test case with glibc 2.29, always
Launchpad has imported 1 comments from the remote bug at https://bugs.busybox.net/show_bug.cgi?id=11896. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2019-05-23T10:56:10+00:00 Dimitri John Ledkov wrote: Originally reported at https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1828282 with initial suspicion at glibc, however later diagnosed to be a busybox issue. The full analysis is at https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1828282/comments/1 In short bz2_issue_11.bz2 test case always fails on s390x since bunzip2 depends on uninitialised values, which happen to always be "wrong" on s390x. This is observable with valgrind too: # valgrind busybox bunzip2 &1 >/dev/null ==40965== Memcheck, a memory error detector ==40965== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==40965== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info ==40965== Command: busybox bunzip2 ==40965== ==40965== Conditional jump or move depends on uninitialised value(s) ==40965==at 0x17C1D4: get_next_block (decompress_bunzip2.c:393) ==40965==by 0x17C37F: get_next_block (decompress_bunzip2.c:419) ==40965== bunzip2: bunzip error -5 ==40965== ==40965== HEAP SUMMARY: ==40965== in use at exit: 0 bytes in 0 blocks ==40965== total heap usage: 7 allocs, 7 frees, 4,539,696 bytes allocated ==40965== ==40965== All heap blocks were freed -- no leaks are possible ==40965== ==40965== For counts of detected and suppressed errors, rerun with: -v ==40965== Use --track-origins=yes to see where uninitialised values come from ==40965== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) For the time being we are skipping the bz2_issue_11.bz2 test case in ubuntu. Reply at: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1828282/comments/6 ** Changed in: busybox Status: Unknown => Confirmed ** Changed in: busybox Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1828282 Title: busybox 1.30.1 crashes bzip2 test case with glibc 2.29, always Status in BusyBox: Confirmed Status in Ubuntu on IBM z Systems: Invalid Status in busybox package in Ubuntu: Triaged Status in glibc package in Ubuntu: Invalid Bug description: Steps to reproduce: 1) Get a system with glibc 2.29 2) Get busybox 1.30.1 installed (e.g. eoan, or download busybox package from https://launchpad.net/ubuntu/+source/busybox/1:1.30.1-4ubuntu3/+build/16724246 and use $ apt install ./busybox*.deb to install) 3) Get busybox 1.30.1 source code, e.g. $ pull-lp-source busybox Or like download the orig tarball from https://launchpad.net/ubuntu/+source/busybox/1:1.30.1-4ubuntu3 4) Run the bunzip2 testsuite: cd testsuite/ ECHO=/bin/echo ./bunzip2.tests Observe that with glibc 2.29 the: PASS: bunzip2: bz2_issue_11.bz2 corrupted example is XFAIL or FAIL, on s390x, whereas it passes on all other arches. If one uses glibc 2.28 (ie. use Cosmic, and install busybox & use matching test suite from eoan using links above) one can observe that the testcase always passes. We suspect this might be a glibc 2.29 s390x-specific setjmp regression. Probably due to setjmp usage in ./archival/libarchive/decompress_bunzip2.c The tests were done on a z13 machine. To manage notifications about this bug go to: https://bugs.launchpad.net/busybox/+bug/1828282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823070] Re: unattended-upgrades should tell the user (via motd) when security updates are held back
https://github.com/mvo5/unattended-upgrades/pull/200 ** Changed in: unattended-upgrades (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1823070 Title: unattended-upgrades should tell the user (via motd) when security updates are held back Status in unattended-upgrades package in Ubuntu: In Progress Bug description: Currently we have the following pieces as part of the default UX on Ubuntu 18.04 and later: 1) unattended-upgrades automatically installs security updates daily by default 2) the motd reports the number of available updates, including security updates. A user who knows about 1) also knows that a non-zero number of pending security updates listed in 2) is nothing to worry about. However, unattended-upgrades will also cleverly detect when a security update cannot safely be installed non-interactively due to conffile changes on the system. In this case, unattended-upgrades should also inform the user via the motd that these updates are not being installed. Otherwise, there's nothing to tell the user that the non-zero count of available security updates in motd is a *problem*. Suggested wording: N security updates will not be automatically installed due to local changes. See /var/log/foo for details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1823070/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
** Changed in: libreoffice (Ubuntu Cosmic) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" Status in fonts-noto-cjk package in Ubuntu: New Status in gnome-characters package in Ubuntu: New Status in gucharmap package in Ubuntu: New Status in icu package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in mozc package in Ubuntu: Fix Released Status in openjdk-8 package in Ubuntu: Fix Released Status in poppler-data package in Ubuntu: New Status in unicode-data package in Ubuntu: Fix Released Status in gnome-characters source package in Xenial: New Status in gucharmap source package in Xenial: New Status in icu source package in Xenial: New Status in libreoffice source package in Xenial: New Status in libreoffice-l10n source package in Xenial: New Status in mozc source package in Xenial: Fix Released Status in openjdk-8 source package in Xenial: New Status in poppler-data source package in Xenial: New Status in unicode-data source package in Xenial: New Status in fonts-noto-cjk source package in Bionic: New Status in gnome-characters source package in Bionic: New Status in gucharmap source package in Bionic: New Status in icu source package in Bionic: New Status in libreoffice source package in Bionic: New Status in libreoffice-l10n source package in Bionic: New Status in mozc source package in Bionic: Fix Released Status in openjdk-8 source package in Bionic: New Status in poppler-data source package in Bionic: New Status in unicode-data source package in Bionic: New Status in fonts-noto-cjk source package in Cosmic: New Status in gnome-characters source package in Cosmic: New Status in gucharmap source package in Cosmic: New Status in icu source package in Cosmic: New Status in libreoffice source package in Cosmic: Fix Released Status in libreoffice-l10n source package in Cosmic: New Status in mozc source package in Cosmic: Fix Released Status in openjdk-8 source package in Cosmic: New Status in poppler-data source package in Cosmic: New Status in unicode-data source package in Cosmic: New Status in fonts-noto-cjk source package in Disco: New Status in gnome-characters source package in Disco: New Status in gucharmap source package in Disco: New Status in icu source package in Disco: New Status in libreoffice source package in Disco: Fix Released Status in libreoffice-l10n source package in Disco: Fix Released Status in mozc source package in Disco: Fix Released Status in openjdk-8 source package in Disco: New Status in poppler-data source package in Disco: New Status in unicode-data source package in Disco: New Bug description: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和） This is the meta bug to track packages that need fixes; which packages have already been SRUd to previous releases, how to prioritize the work needed, and general test cases for verifying that things are working as expected. [Impact] Users who run Ubuntu in Japanese. [Test cases] == Date conversion == On applications that support writing dates in long form, or with symbols to denote era (either in X00.00.00 format or in GG1G5G1G format (G- glyph; X- character): 1) Enable date formatting in each of the above formats that are supported (long form or symbols) 2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" or "R1.05.01" 3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" or "H31.4.30" == Date output == 1) Set date to 2019/05/01 2) Output date; verify that the year it is displayed as "令和元年" 3) Set date to 2019/04/30 4) Output date; verify that the year is diplayed as "平成31年" === Displaying formatted year for Japanese era with glibc === Run: LC_ALL=ja_JP.utf8 date +%EY -d 20190430 # previous era (should still work as before SRUs) or LC_ALL=ja_JP.utf8 date +%EY -d 20190501 # new era (should now correctly display the new era) == Character maps / font support == 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - SQUARE ERA NAME HEISEI: ㍻ - SQUARE ERA NAME REIWA: 令和 (in a single glyph) Display of the Reiwa square glyph is font-specific; it may show simply as a empty square or a square with hex characters. If that is the case, the unicode data supports the new character, but the selected font does not include the new glyph. == Typing / input methods == 1) Type in 'heisei'
[Touch-packages] [Bug 1828282] Re: busybox 1.30.1 crashes bzip2 test case with glibc 2.29, always
** Bug watch added: Busybox Bugzilla #11896 https://bugs.busybox.net/show_bug.cgi?id=11896 ** Also affects: busybox via https://bugs.busybox.net/show_bug.cgi?id=11896 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1828282 Title: busybox 1.30.1 crashes bzip2 test case with glibc 2.29, always Status in BusyBox: Unknown Status in Ubuntu on IBM z Systems: Invalid Status in busybox package in Ubuntu: Triaged Status in glibc package in Ubuntu: Invalid Bug description: Steps to reproduce: 1) Get a system with glibc 2.29 2) Get busybox 1.30.1 installed (e.g. eoan, or download busybox package from https://launchpad.net/ubuntu/+source/busybox/1:1.30.1-4ubuntu3/+build/16724246 and use $ apt install ./busybox*.deb to install) 3) Get busybox 1.30.1 source code, e.g. $ pull-lp-source busybox Or like download the orig tarball from https://launchpad.net/ubuntu/+source/busybox/1:1.30.1-4ubuntu3 4) Run the bunzip2 testsuite: cd testsuite/ ECHO=/bin/echo ./bunzip2.tests Observe that with glibc 2.29 the: PASS: bunzip2: bz2_issue_11.bz2 corrupted example is XFAIL or FAIL, on s390x, whereas it passes on all other arches. If one uses glibc 2.28 (ie. use Cosmic, and install busybox & use matching test suite from eoan using links above) one can observe that the testcase always passes. We suspect this might be a glibc 2.29 s390x-specific setjmp regression. Probably due to setjmp usage in ./archival/libarchive/decompress_bunzip2.c The tests were done on a z13 machine. To manage notifications about this bug go to: https://bugs.launchpad.net/busybox/+bug/1828282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828134] Re: Wifi not working after suspend/resume cycle
The issue would probably be best reported upstream on https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/ -- 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/1828134 Title: Wifi not working after suspend/resume cycle Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: About 75% of the time for the past few weeks (I don't have a time where this started), my wifi is not working after resume from suspend. I'm happy to provide more debugging info if needed. I have tried an rmmod/modprobe on on the iwlwifi,iwlmvm modules just to see after the resume, and didn't re-enable the card. The symptoms are, the wlp4so interface is DOWN, I can't bring it up. gnome-network-manager widget turning the interface off/on doesn't work. I don't see anything glaring in dmesg. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-generic 5.0.0.14.15 ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6 Uname: Linux 5.0.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dpb4587 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 7 18:49:01 2019 InstallationDate: Installed on 2018-06-18 (323 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20HRCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-14-generic root=UUID=fa64d67d-26bf-4c42-a12f-c45b6ea5117c ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-14-generic N/A linux-backports-modules-5.0.0-14-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-03-15 (53 days ago) dmi.bios.date: 02/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET52W(1.37) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET52W(1.37):bd02/14/2019:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HRCTO1WW dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828134/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821269] Re: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole combo jack mic doesn't detect)
@hui.wang After #12, I tried to generate new alsa-info.txt file. Please check attachment file again. I confirmed that there is "snd_hda_intel: model = lifebook-extmic" entry in the "Modprobe options" category. But apple 4 pole earset's mic is still not working. Thank you for your sincere effort. ** Attachment added: "alsa-info.txt.LhKA0UjBF3" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821269/+attachment/5265952/+files/alsa-info.txt.LhKA0UjBF3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821269 Title: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole combo jack mic doesn't detect) Status in alsa-driver package in Ubuntu: New Bug description: I use realtek alc255 analog audio jack. External jack is 4 pole combo(apple type. not europe type.). When I plug 4 pole mic into jack, It doesn't detect. So I can't my voice through external mic. My laptop has internal mic. It belongs to Intel sound(HDA Intel PCH. Audio device: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 21)). Internal mic works well. Please check 4pole external mic detection. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: jimnong1441 F...m pulseaudio /dev/snd/pcmC0D0p: jimnong1441 F...m pulseaudio /dev/snd/controlC0: jimnong1441 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 22 11:30:39 2019 InstallationDate: Installed on 2017-07-27 (603 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: 내장 오디오 - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_Type: No auto-switch between inputs Title: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch UpgradeStatus: Upgraded to bionic on 2018-09-23 (179 days ago) dmi.bios.date: 09/06/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Garp_BA dmi.board.vendor: Acer dmi.board.version: V1.24 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.24:bd09/06/2016:svnAcer:pnAspireES1-131:pvrV1.24:rvnAcer:rnGarp_BA:rvrV1.24:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: Aspire ES1-131 dmi.product.version: V1.24 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821269/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830169] Re: lvm udev rule fails to call systemd-run
On fresh disco and up installations this "just works" due to /usr-merge
by default.
On prior releases bin dir is configurable at lvm build time, which we
set to /bin (as that's where we want lvm2 utils to end up), but that's
not the location of systemd-run.
Needs a manual patch to lvm2, to support split-/usr systems (older
releases & upgraded systems)
** Package changed: systemd (Ubuntu) => lvm2 (Ubuntu)
** Also affects: lvm2 (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: lvm2 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: lvm2 (Ubuntu Eoan)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Also affects: lvm2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: lvm2 (Ubuntu Cosmic)
Importance: Undecided
Status: New
--
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/1830169
Title:
lvm udev rule fails to call systemd-run
Status in Ubuntu on IBM z Systems:
Triaged
Status in lvm2 package in Ubuntu:
New
Status in lvm2 source package in Xenial:
New
Status in lvm2 source package in Bionic:
New
Status in lvm2 source package in Cosmic:
New
Status in lvm2 source package in Disco:
New
Status in lvm2 source package in Eoan:
New
Bug description:
In /lib/udev/rules.d/69-lvm-metad.rules file, it calls /bin/systemd-run
command during removal ---
ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run /sbin/lvm
pvscan --cache $major:$minor", GOTO="lvm_end"
But /bin/systemd-run is not found, in fact systemd-run is in /usr/bin
/systemd-run.
xx:~$ cat /etc/issue
Ubuntu 18.04.2 LTS \n \l
xx:~$ ls /bin/systemd-run
ls: cannot access '/bin/systemd-run': No such file or directory
xx:~$ ls /usr/bin/systemd-run
/usr/bin/systemd-run
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1830169/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825194] Re: [SRU] resolvconf is racy, which leads to broken resolv.conf in parallel calls
This bug was fixed in the package resolvconf - 1.78ubuntu7 --- resolvconf (1.78ubuntu7) xenial; urgency=medium * bin/resolvconf: use flock so resolvconf can be called in parallel safely (LP: #1825194). -- Alfonso Sanchez-Beato (email Canonical) Mon, 06 May 2019 10:39:40 +0200 ** Changed in: resolvconf (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1825194 Title: [SRU] resolvconf is racy, which leads to broken resolv.conf in parallel calls Status in resolvconf package in Ubuntu: Fix Released Status in resolvconf source package in Xenial: Fix Released Bug description: [Impact] The bug can lead to non-working DNS. This is a critical bug that needs to be fixed in the stable release. The patch fixes the bug by using a file lock via the flock command. [Test case] This script should eventually stop with the current version, thing that should not happen after applying the patch: while true; do printf "\n" | sudo resolvconf -a NetworkManager printf "nameserver 8.8.8.8\n" | sudo resolvconf -a networkd wait printf "nameserver 8.8.8.8\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd wait ping -c 1 www.google.com || break done [Regression Potential] The patch is small and what it does is straightforward. It has also been thoroughly tested. However, the effect if something is wrong would be not being able to resolve DNS names, which is disastrous, so it needs to be very well tested for the SRU. [Other Info] It has been found that simultaneous calls to resolvconf can lead to inconsistent content in resolv.conf. For instance, no nameservers while NetworkManager has one in its record (see LP: #1824395): $ cat /run/resolvconf/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN $ cat /run/resolvconf/interface/NetworkManager nameserver 192.168.1.6 nameserver 192.168.1.2 This can happen easily when calling "netplan apply", which can re- start both networkd and NM. resolvconf is called at that point by the "systemd-networkd-resolvconf-update.service" service, and also directly by NetworkManager, which leads to the situation described above. This is not surprising as there is nothing preventing different instances of resolvconf to access the same files. This sort of situation can be reproduced by running in a loop commands like: $ printf "\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd $ printf "nameserver 80.58.61.250\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd Eventually, this leads to a resolv.conf that is not consistent with the last run command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825194] Update Released
The verification of the Stable Release Update for resolvconf has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1825194 Title: [SRU] resolvconf is racy, which leads to broken resolv.conf in parallel calls Status in resolvconf package in Ubuntu: Fix Released Status in resolvconf source package in Xenial: Fix Released Bug description: [Impact] The bug can lead to non-working DNS. This is a critical bug that needs to be fixed in the stable release. The patch fixes the bug by using a file lock via the flock command. [Test case] This script should eventually stop with the current version, thing that should not happen after applying the patch: while true; do printf "\n" | sudo resolvconf -a NetworkManager printf "nameserver 8.8.8.8\n" | sudo resolvconf -a networkd wait printf "nameserver 8.8.8.8\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd wait ping -c 1 www.google.com || break done [Regression Potential] The patch is small and what it does is straightforward. It has also been thoroughly tested. However, the effect if something is wrong would be not being able to resolve DNS names, which is disastrous, so it needs to be very well tested for the SRU. [Other Info] It has been found that simultaneous calls to resolvconf can lead to inconsistent content in resolv.conf. For instance, no nameservers while NetworkManager has one in its record (see LP: #1824395): $ cat /run/resolvconf/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN $ cat /run/resolvconf/interface/NetworkManager nameserver 192.168.1.6 nameserver 192.168.1.2 This can happen easily when calling "netplan apply", which can re- start both networkd and NM. resolvconf is called at that point by the "systemd-networkd-resolvconf-update.service" service, and also directly by NetworkManager, which leads to the situation described above. This is not surprising as there is nothing preventing different instances of resolvconf to access the same files. This sort of situation can be reproduced by running in a loop commands like: $ printf "\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd $ printf "nameserver 80.58.61.250\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd Eventually, this leads to a resolv.conf that is not consistent with the last run command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830169] Re: lvm udev rule fails to call systemd-run
** Package changed: linux (Ubuntu) => systemd (Ubuntu)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Status: New => Triaged
** Changed in: ubuntu-z-systems
Importance: Undecided => Medium
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
--
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/1830169
Title:
lvm udev rule fails to call systemd-run
Status in Ubuntu on IBM z Systems:
Triaged
Status in systemd package in Ubuntu:
New
Bug description:
In /lib/udev/rules.d/69-lvm-metad.rules file, it calls /bin/systemd-run
command during removal ---
ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run /sbin/lvm
pvscan --cache $major:$minor", GOTO="lvm_end"
But /bin/systemd-run is not found, in fact systemd-run is in /usr/bin
/systemd-run.
xx:~$ cat /etc/issue
Ubuntu 18.04.2 LTS \n \l
xx:~$ ls /bin/systemd-run
ls: cannot access '/bin/systemd-run': No such file or directory
xx:~$ ls /usr/bin/systemd-run
/usr/bin/systemd-run
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1830169/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830169] [NEW] lvm udev rule fails to call systemd-run
You have been subscribed to a public bug:
In /lib/udev/rules.d/69-lvm-metad.rules file, it calls /bin/systemd-run command
during removal ---
ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run /sbin/lvm
pvscan --cache $major:$minor", GOTO="lvm_end"
But /bin/systemd-run is not found, in fact systemd-run is in /usr/bin
/systemd-run.
xx:~$ cat /etc/issue
Ubuntu 18.04.2 LTS \n \l
xx:~$ ls /bin/systemd-run
ls: cannot access '/bin/systemd-run': No such file or directory
xx:~$ ls /usr/bin/systemd-run
/usr/bin/systemd-run
** Affects: systemd (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-177805 severity-medium
targetmilestone-inin18041
--
lvm udev rule fails to call systemd-run
https://bugs.launchpad.net/bugs/1830169
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to systemd in Ubuntu.
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815649] Re: Vim on Ubuntu Disc 19.04 does not work
Sebastien's information is correct (Thanks!) Command 'vim.tiny' works. Also 'vi'. I think the confusion is the user expects a graphical application. Vim- tiny, the default installation in Ubuntu, is a console (Terminal) application. To get the graphical version, install gVim in Ubuntu Software. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1815649 Title: Vim on Ubuntu Disc 19.04 does not work Status in vim package in Ubuntu: Confirmed Bug description: Hi guys The Vim on Ubuntu Disk 19.04 comes installed by default, but so far does not work. It is stated that it is installed by the Ubuntu software, but by the terminal says it is not installed as can be seen in the attached image. Command 'vim' not found, but can be installed with: Awaiting arrangements and correction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1815649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
Installed the systemd from the ppa and the .14 NM package: ii network-manager 1.10.14-0ubuntu2 ii systemd 237-3ubuntu10.22~ppa1 Rebooted, gave it a spin and no good, I'm afraid. The 127.0.0.54 resolver was still left out of the loop. I've since gone back to the public systemd version and once again downgraded NM to restore functionality as I need it day-to-day, sorry there isn't better news. -- 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/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns Status in network-manager package in Ubuntu: Incomplete Status in network-manager source package in Bionic: Incomplete Bug description: On 18.04.2 the `upgrade network-manager:amd64 1.10.6-2ubuntu1.1 1.10.14-0ubuntu2` lead to scoped DNS servers defined in `/etc/systemd/resolved.conf.d/*.conf` being ignored. Downgrading with `sudo apt-get install network- manager=1.10.6-2ubuntu1.1` has resolved the issue for now. Example systemd-resolved conf: [Resolve] Cache=no DNS=127.0.0.54 Domains=~.local.org.com Where 127.0.0.54:53 is bound to a dnsmasq server capable of resolving queries in that subdomain. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815649] Re: Vim on Ubuntu Disc 19.04 does not work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: vim (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1815649 Title: Vim on Ubuntu Disc 19.04 does not work Status in vim package in Ubuntu: Confirmed Bug description: Hi guys The Vim on Ubuntu Disk 19.04 comes installed by default, but so far does not work. It is stated that it is installed by the Ubuntu software, but by the terminal says it is not installed as can be seen in the attached image. Command 'vim' not found, but can be installed with: Awaiting arrangements and correction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1815649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1288182] Re: Cyrillic not displayed in the input field
** Changed in: poppler Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1288182 Title: Cyrillic not displayed in the input field Status in Evince: Unknown Status in Poppler: New Status in evince package in Ubuntu: Triaged Status in poppler package in Ubuntu: Invalid Bug description: Ubuntu 14.04 x64 Evince 3.10.3 Cyrillic not displayed in the input field. In attach screenshot: input field with text 'This сyrillic: "Кириллица"' Upd. Still actual for Ubuntu 16.04 x64 Evince 3.18.2 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1288182/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1353013] Re: Popping/Crackling sound when playing audio in Ubuntu 14.04
Dane, That sounds like a different bug. Please open a new one using this command: ubuntu-bug pulseaudio -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1353013 Title: Popping/Crackling sound when playing audio in Ubuntu 14.04 Status in nvidia-hdmi-pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When listening to audio (pandora internet radio, youtube, etc.), I get a repeated popping/crackling sound. When I look at the sound settings while this is happening, I see "Headphone Output" rapidly appearing and then disappearing in the "Play Sound Through" section. The appearance and disappearance of "Headphone Output" coincides with the popping and crackling of the sound. I am wondering if it has anything to do with the fact that my Nvidia card has a built-in HDMI card that might be interfering with my onboard sound: $ cat /proc/asound/cards 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xf722 irq 54 1 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xf708 irq 55 cat /proc/asound/modules 0 snd_hda_intel 1 snd_hda_intel Obviously blacklisting "snd_hda_intel" in /etc/modprobe.d/blacklist.conf won't work, because it then disables all sound (both onboard and nvidia are listed as snd_hda_intel). Description: Ubuntu 14.04.1 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim1856 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 5 10:17:34 2014 InstallationDate: Installed on 2014-04-17 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0132.2011.1007.1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-205 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0132.2011.1007.1505:bd10/07/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-205:cvn:ct3:cvr: modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2014-08-04T12:00:53.999120 mtime.conffile..etc.pulse.default.pa: 2014-08-04T12:18:08.532386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-hdmi-pulseaudio/+bug/1353013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821269] Re: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole combo jack mic doesn't detect)
@Ji-min, After #12, please upload an alsa-info.txt, let me check if "model =liefbook-extmic" is applied or not. If it really applied but it did not work on this machine, I will ask for help from realtek. thx. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821269 Title: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole combo jack mic doesn't detect) Status in alsa-driver package in Ubuntu: New Bug description: I use realtek alc255 analog audio jack. External jack is 4 pole combo(apple type. not europe type.). When I plug 4 pole mic into jack, It doesn't detect. So I can't my voice through external mic. My laptop has internal mic. It belongs to Intel sound(HDA Intel PCH. Audio device: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 21)). Internal mic works well. Please check 4pole external mic detection. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: jimnong1441 F...m pulseaudio /dev/snd/pcmC0D0p: jimnong1441 F...m pulseaudio /dev/snd/controlC0: jimnong1441 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 22 11:30:39 2019 InstallationDate: Installed on 2017-07-27 (603 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: 내장 오디오 - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_Type: No auto-switch between inputs Title: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch UpgradeStatus: Upgraded to bionic on 2018-09-23 (179 days ago) dmi.bios.date: 09/06/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Garp_BA dmi.board.vendor: Acer dmi.board.version: V1.24 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.24:bd09/06/2016:svnAcer:pnAspireES1-131:pvrV1.24:rvnAcer:rnGarp_BA:rvrV1.24:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: Aspire ES1-131 dmi.product.version: V1.24 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821269/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1288182] Re: Cyrillic not displayed in the input field
poppler moved to gitlab ** Bug watch added: gitlab.freedesktop.org/poppler/poppler/issues #463 https://gitlab.freedesktop.org/poppler/poppler/issues/463 ** Changed in: poppler Importance: Medium => Unknown ** Changed in: poppler Remote watch: freedesktop.org Bugzilla #17913 => gitlab.freedesktop.org/poppler/poppler/issues #463 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1288182 Title: Cyrillic not displayed in the input field Status in Evince: Unknown Status in Poppler: Unknown Status in evince package in Ubuntu: Triaged Status in poppler package in Ubuntu: Invalid Bug description: Ubuntu 14.04 x64 Evince 3.10.3 Cyrillic not displayed in the input field. In attach screenshot: input field with text 'This сyrillic: "Кириллица"' Upd. Still actual for Ubuntu 16.04 x64 Evince 3.18.2 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1288182/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821269] Re: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole combo jack mic doesn't detect)
@vanvugt Thank you for help. I modified my /etc/default/grub file like this. #GRUB_DEFAULT=0 GRUB_DEFAULT=saved #GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=10 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" GRUB_CMDLINE_LINUX_DEFAULT="snd_hda_intel.model=lifebook-extmic" GRUB_CMDLINE_LINUX="" And "sudo update-grub" and rebooted. But no change occurred. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1821269 Title: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch (4-pole combo jack mic doesn't detect) Status in alsa-driver package in Ubuntu: New Bug description: I use realtek alc255 analog audio jack. External jack is 4 pole combo(apple type. not europe type.). When I plug 4 pole mic into jack, It doesn't detect. So I can't my voice through external mic. My laptop has internal mic. It belongs to Intel sound(HDA Intel PCH. Audio device: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio Controller (rev 21)). Internal mic works well. Please check 4pole external mic detection. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: jimnong1441 F...m pulseaudio /dev/snd/pcmC0D0p: jimnong1441 F...m pulseaudio /dev/snd/controlC0: jimnong1441 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 22 11:30:39 2019 InstallationDate: Installed on 2017-07-27 (603 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: 내장 오디오 - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_Type: No auto-switch between inputs Title: [Aspire ES1-131, Realtek ALC255, Mic, Internal] No autoswitch UpgradeStatus: Upgraded to bionic on 2018-09-23 (179 days ago) dmi.bios.date: 09/06/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Garp_BA dmi.board.vendor: Acer dmi.board.version: V1.24 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.24:bd09/06/2016:svnAcer:pnAspireES1-131:pvrV1.24:rvnAcer:rnGarp_BA:rvrV1.24:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: Aspire ES1-131 dmi.product.version: V1.24 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821269/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1353013] Re: Popping/Crackling sound when playing audio in Ubuntu 14.04
I'm seeing this bug in Linux Mint 19.1 (Ubuntu 18.04 base). The audio devices do not appear and disappear in the "Sounds" GUI. The workaround I've found is to do this in a terminal: pulseaudio -k && sleep 5 ; pulseaudio -D Sometimes this works for hours, and sometimes it works for minutes, after killing/restarting the PulseAudio daemon, as above. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1353013 Title: Popping/Crackling sound when playing audio in Ubuntu 14.04 Status in nvidia-hdmi-pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When listening to audio (pandora internet radio, youtube, etc.), I get a repeated popping/crackling sound. When I look at the sound settings while this is happening, I see "Headphone Output" rapidly appearing and then disappearing in the "Play Sound Through" section. The appearance and disappearance of "Headphone Output" coincides with the popping and crackling of the sound. I am wondering if it has anything to do with the fact that my Nvidia card has a built-in HDMI card that might be interfering with my onboard sound: $ cat /proc/asound/cards 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xf722 irq 54 1 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xf708 irq 55 cat /proc/asound/modules 0 snd_hda_intel 1 snd_hda_intel Obviously blacklisting "snd_hda_intel" in /etc/modprobe.d/blacklist.conf won't work, because it then disables all sound (both onboard and nvidia are listed as snd_hda_intel). Description: Ubuntu 14.04.1 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim1856 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 5 10:17:34 2014 InstallationDate: Installed on 2014-04-17 (109 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0132.2011.1007.1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10212-205 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0132.2011.1007.1505:bd10/07/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-205:cvn:ct3:cvr: modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2014-08-04T12:00:53.999120 mtime.conffile..etc.pulse.default.pa: 2014-08-04T12:18:08.532386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-hdmi-pulseaudio/+bug/1353013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
