[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full
Is this bug confirmed resolved for any version of Ubuntu? What release do I need to get my friends migrated to, in order for this to not be a problem? -- 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/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full Status in unattended-upgrades: New Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: Currently if one chooses to use LVM or encrypted install, a /boot partition is created of 236Mb Once kernel updates start being released this partition soon fills until people are left unable to upgrade. While you and I might know that we need to watch partition space, many of the people we have installing think that a windows disk is a disk and not a partition, education is probably the key - but in the meantime support venues keep needing to deal with the fact the partition is too small and/or old kernels are not purged as new ones install. For workaround and sytem repair, see https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1357093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
Confirm on this bug with hardware: HP Z230, Intel Raid bios, Ubuntu 16.04.2. -- 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/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." Status in systemd package in Ubuntu: Confirmed Bug description: I'm booting a fully patched 16.04 from an Intel Rapid Storage Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode). If the RAID volume is recovering or resyncing for whatever reason, then `sudo systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to consistently get that). However, once the recovery/resync is complete and clean, the reboot and poweroff commands above hang forever after "Reached target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in the bug #1464917) does not help. [EDIT]Actually, the shutdown also hangs from time to time during a resync. But I've never seen it succeed once the resync is complete.[/EDIT] Then, if the server has been forcibly restarted with the power button, the Intel Matrix Storage Manager indicates a "Normal" status for the RAID1 volume, but Ubuntu then resyncs the volume anyway: [1.223649] md: bind [1.228426] md: bind [1.230030] md: bind [1.230738] md: bind [1.232985] usbcore: registered new interface driver usbhid [1.233494] usbhid: USB HID core driver [1.234022] md: raid1 personality registered for level 1 [1.234876] md/raid1:md126: not clean -- starting background reconstruction [1.234956] input: CHESEN USB Keyboard as /devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5 [1.236273] md/raid1:md126: active with 2 out of 2 mirrors [1.236797] md126: detected capacity change from 0 to 1000202043392 [1.246271] md: md126 switched to read-write mode. [1.246834] md: resync of RAID array md126 [1.247325] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. [1.247503] md126: p1 p2 p3 p4 [1.248269] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. [1.248774] md: using 128k window, over a total of 976759940k. Note that the pain of "resync upon every (re)boot" cannot even be a bit relieved thanks to bitmaps because mdadm does not support them for IMSM containers: $ sudo mdadm --grow --bitmap=internal /dev/md126 mdadm: Cannot add bitmaps to sub-arrays yet I also get this in syslog during boot when the individual drives are detected, but this seems to be harmless: May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental /dev/sdb --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental /dev/sda --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed with exit code 1. During a resync, `sudo sh -c 'echo idle > /sys/block/md126/md/sync_action'` actually stops it as expected, but it restarts immediately though nothing seems to have triggered it: May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted. May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of md126. May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126 May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a total of 976759940k. May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 from checkpoint. May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device /dev/md/Volume0 I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 > /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without any keyboard. [EDIT]But I can still switch back to tty1.[/EDIT] I have also tried with much lower values for vm.dirty_background_ratio and vm.dirty_ratio, but to no avail. Linux 4.6.0-040600-generic_4.6.0-040600.201605151930_amd64 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ did not help either. More information below: $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 1
[Touch-packages] [Bug 1585886] Re: WiFi indicator icon disappears in Ubuntu 16.04
Wifi icon on top panel disappears for me as well (16.04 + Unity). I have to use settings > network to deal with the WiFi connections. Happens mostly when I " suspend " and resume my PC. I do not use an ethernet cable. So, unable to comment on that. sudo service network-manager restart nm-applet These commands, when active on terminal brings back the icon. But, the WiFi network listing are missing at times. -- 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/1585886 Title: WiFi indicator icon disappears in Ubuntu 16.04 Status in indicator-applet package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Dear all, Can someone confirm an occasionally missing WiFi indicator tray icon? Sometimes it happens that the icon is not displayed although the WiFi connection is working. Please see also the attached screenshot. Warmly, ~Robert To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1585886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707487] Re: Bluetooth speaker only plays as mono
Who do I run "apport-collect 1707487"? Please tell me how to do this. Many thanks. -- 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/1707487 Title: Bluetooth speaker only plays as mono Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only plays back as "mono" and refuses to use "hi fidelity". I have Windows 10 installed on the same laptop and when I've used the Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its Bluetooth list. I have to hold in the "reset" button on the speaker itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I try using this speaker in Ubuntu, which suggests that Ubuntu is forcing the speaker into "mono" mode and Windows then sees it as a different device? Please help. I will post all needed outputs as instructed. Cheers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
** Attachment removed: "926BF9B9908245F6.jpg" https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/349469/+attachment/4924027/+files/926BF9B9908245F6.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable Status in Aptdaemon: Confirmed Status in Debconf: New Status in aptdaemon package in Ubuntu: Incomplete Status in debconf package in Ubuntu: Triaged Bug description: Upgrading packages that use debconf sometimes fail with the following error: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/aptdaemon/+bug/349469/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707487] Re: Bluetooth speaker only plays as mono
Open a terminal window (Ctrl+Alt+T) and then run: sudo apt install -y apport apport-collect 1707487 -- 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/1707487 Title: Bluetooth speaker only plays as mono Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only plays back as "mono" and refuses to use "hi fidelity". I have Windows 10 installed on the same laptop and when I've used the Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its Bluetooth list. I have to hold in the "reset" button on the speaker itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I try using this speaker in Ubuntu, which suggests that Ubuntu is forcing the speaker into "mono" mode and Windows then sees it as a different device? Please help. I will post all needed outputs as instructed. Cheers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703271] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from profile_new_connection() from profile_handler() f
Although it's hard to tell if "pulseaudio (1:10.0-2ubuntu1) artful" fixed this because there are zero instances of this crash in artful. We won't really know until that version gets backported to zesty. And it's possibly still a bit too early for that. ** Changed in: pulseaudio (Ubuntu) Status: In Progress => Confirmed -- 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/1703271 Title: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from profile_new_connection() from profile_handler() from _dbus_object_tree_dispatch_and_unlock() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/f2718ea2383be2a9cda88115eeb71652d9444a7d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1703271/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703272] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from pa_bluetooth_transport_put() from endpoint_set_co
Although it's hard to tell if "pulseaudio (1:10.0-2ubuntu1) artful" fixed this because there are zero instances of this crash in artful. We won't really know until the same fixes get backported to xenial. And it's possibly still a bit too early for that. ** Changed in: pulseaudio (Ubuntu) Status: In Progress => Confirmed -- 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/1703272 Title: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from pa_bluetooth_transport_put() from endpoint_set_configuration() from endpoint_handler() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:8.0-0ubuntu3.3, the problem page at https://errors.ubuntu.com/problem/80ef14dcf1628eef17ef830d6c65f4c9ee035457 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1703272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703272] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from pa_bluetooth_transport_put() from endpoint_set_co
See also bug 1703271 -- 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/1703272 Title: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from pa_bluetooth_transport_put() from endpoint_set_configuration() from endpoint_handler() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:8.0-0ubuntu3.3, the problem page at https://errors.ubuntu.com/problem/80ef14dcf1628eef17ef830d6c65f4c9ee035457 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1703272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703271] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from profile_new_connection() from profile_handler() f
See also bug 1703272 -- 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/1703271 Title: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from profile_new_connection() from profile_handler() from _dbus_object_tree_dispatch_and_unlock() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/f2718ea2383be2a9cda88115eeb71652d9444a7d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1703271/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690054] Re: pulseaudio crashed with SIGABRT in pa_sink_input_attach() from pa_sink_attach_within_thread() from pa_sink_process_msg() from sink_process_msg() from asyncmsgq_read_
** Tags added: artful -- 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/1690054 Title: pulseaudio crashed with SIGABRT in pa_sink_input_attach() from pa_sink_attach_within_thread() from pa_sink_process_msg() from sink_process_msg() from asyncmsgq_read_work() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/cba7a3bcc7f260f8aab11c71680f8742fbbb03b1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707487] Re: Bluetooth speaker only plays as mono
Thanks. I tried it, got this: Quote "You need to run 'sudo apt-get install python-apport' for apport- collect to work." I guess I need to run "sudo apt-get install python-apport" first? -- 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/1707487 Title: Bluetooth speaker only plays as mono Status in pulseaudio package in Ubuntu: Incomplete Bug description: When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only plays back as "mono" and refuses to use "hi fidelity". I have Windows 10 installed on the same laptop and when I've used the Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its Bluetooth list. I have to hold in the "reset" button on the speaker itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I try using this speaker in Ubuntu, which suggests that Ubuntu is forcing the speaker into "mono" mode and Windows then sees it as a different device? Please help. I will post all needed outputs as instructed. Cheers! --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 3626 F...m pulseaudio /dev/snd/controlC0: david 3626 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-28 (367 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: pulseaudio 1:8.0-0ubuntu3.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Tags: xenial Uname: Linux 4.4.0-87-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.21 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21: dmi.product.name: Aspire V3-571 dmi.product.version: V2.21 dmi.sys.vendor: Acer modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2016-07-29T10:08:04.428983 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
** Tags added: artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1663528 Title: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250 --- Sidenote: Imediatly got that crash after the apt-xapian-index one ( lp:1663524 ); does not know if it can exist a possible relationship between them. Got an other crash, and that time 'sound' is fully lost (pulseaudio not reloaded). Wonder if lp:1662860 can be concerned. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6 Uname: Linux 4.9.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AssertionMessage: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem4084 F pulseaudio /dev/snd/controlC0: oem4084 F pulseaudio CurrentDesktop: GNOME Date: Fri Feb 10 09:55:45 2017 ExecutablePath: /usr/bin/pulseaudio ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: __assert_fail_base (fmt=, assertion=assertion@entry=0x7f92818e7188 "mixer", file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:92 __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 "mixer.c", line=929, function=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") at assert.c:101 snd_mixer_elem_get_callback_private () from /usr/lib/x86_64-linux-gnu/libasound.so.2 ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so Title: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev sambashare sudo users dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1663528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707487] Re: Bluetooth speaker only plays as mono
apport information ** Tags added: apport-collected xenial ** Description changed: When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only plays back as "mono" and refuses to use "hi fidelity". I have Windows 10 installed on the same laptop and when I've used the Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its Bluetooth list. I have to hold in the "reset" button on the speaker itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I try using this speaker in Ubuntu, which suggests that Ubuntu is forcing the speaker into "mono" mode and Windows then sees it as a different device? Please help. I will post all needed outputs as instructed. Cheers! + --- + ApportVersion: 2.20.1-0ubuntu2.10 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/pcmC0D0c: david 3626 F...m pulseaudio + /dev/snd/controlC0: david 3626 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + EcryptfsInUse: Yes + InstallationDate: Installed on 2016-07-28 (367 days ago) + InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) + Package: pulseaudio 1:8.0-0ubuntu3.3 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 + Tags: xenial + Uname: Linux 4.4.0-87-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 12/16/2013 + dmi.bios.vendor: Insyde Corp. + dmi.bios.version: V2.21 + dmi.board.asset.tag: Type2 - Board Asset Tag + dmi.board.name: VA50_HC_CR + dmi.board.vendor: Acer + dmi.board.version: Type2 - Board Version + dmi.chassis.type: 10 + dmi.chassis.vendor: Insyde Corp. + dmi.chassis.version: V2.21 + dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21: + dmi.product.name: Aspire V3-571 + dmi.product.version: V2.21 + dmi.sys.vendor: Acer + modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] + mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2016-07-29T10:08:04.428983 ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1707487/+attachment/4924478/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1707487 Title: Bluetooth speaker only plays as mono Status in pulseaudio package in Ubuntu: New Bug description: When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only plays back as "mono" and refuses to use "hi fidelity". I have Windows 10 installed on the same laptop and when I've used the Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its Bluetooth list. I have to hold in the "reset" button on the speaker itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I try using this speaker in Ubuntu, which suggests that Ubuntu is forcing the speaker into "mono" mode and Windows then sees it as a different device? Please help. I will post all needed outputs as instructed. Cheers! --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 3626 F...m pulseaudio /dev/snd/controlC0: david 3626 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-28 (367 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: pulseaudio 1:8.0-0ubuntu3.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Tags: xenial Uname: Linux 4.4.0-87-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.21 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21: dmi.product.name: Aspire V3-571 dmi.product.version: V2.21 dmi.sys.vendor: Acer modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2016-07-29T10:08:04.428983 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : t
[Touch-packages] [Bug 1707487] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1707487/+attachment/4924479/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1707487 Title: Bluetooth speaker only plays as mono Status in pulseaudio package in Ubuntu: New Bug description: When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only plays back as "mono" and refuses to use "hi fidelity". I have Windows 10 installed on the same laptop and when I've used the Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its Bluetooth list. I have to hold in the "reset" button on the speaker itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I try using this speaker in Ubuntu, which suggests that Ubuntu is forcing the speaker into "mono" mode and Windows then sees it as a different device? Please help. I will post all needed outputs as instructed. Cheers! --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 3626 F...m pulseaudio /dev/snd/controlC0: david 3626 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-28 (367 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: pulseaudio 1:8.0-0ubuntu3.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Tags: xenial Uname: Linux 4.4.0-87-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.21 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21: dmi.product.name: Aspire V3-571 dmi.product.version: V2.21 dmi.sys.vendor: Acer modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2016-07-29T10:08:04.428983 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707487] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1707487/+attachment/4924483/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1707487 Title: Bluetooth speaker only plays as mono Status in pulseaudio package in Ubuntu: New Bug description: When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only plays back as "mono" and refuses to use "hi fidelity". I have Windows 10 installed on the same laptop and when I've used the Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its Bluetooth list. I have to hold in the "reset" button on the speaker itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I try using this speaker in Ubuntu, which suggests that Ubuntu is forcing the speaker into "mono" mode and Windows then sees it as a different device? Please help. I will post all needed outputs as instructed. Cheers! --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 3626 F...m pulseaudio /dev/snd/controlC0: david 3626 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-28 (367 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: pulseaudio 1:8.0-0ubuntu3.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Tags: xenial Uname: Linux 4.4.0-87-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.21 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21: dmi.product.name: Aspire V3-571 dmi.product.version: V2.21 dmi.sys.vendor: Acer modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2016-07-29T10:08:04.428983 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707487] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1707487/+attachment/4924482/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1707487 Title: Bluetooth speaker only plays as mono Status in pulseaudio package in Ubuntu: New Bug description: When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only plays back as "mono" and refuses to use "hi fidelity". I have Windows 10 installed on the same laptop and when I've used the Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its Bluetooth list. I have to hold in the "reset" button on the speaker itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I try using this speaker in Ubuntu, which suggests that Ubuntu is forcing the speaker into "mono" mode and Windows then sees it as a different device? Please help. I will post all needed outputs as instructed. Cheers! --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 3626 F...m pulseaudio /dev/snd/controlC0: david 3626 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-28 (367 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: pulseaudio 1:8.0-0ubuntu3.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Tags: xenial Uname: Linux 4.4.0-87-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.21 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21: dmi.product.name: Aspire V3-571 dmi.product.version: V2.21 dmi.sys.vendor: Acer modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2016-07-29T10:08:04.428983 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707487] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1707487/+attachment/4924481/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1707487 Title: Bluetooth speaker only plays as mono Status in pulseaudio package in Ubuntu: New Bug description: When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only plays back as "mono" and refuses to use "hi fidelity". I have Windows 10 installed on the same laptop and when I've used the Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its Bluetooth list. I have to hold in the "reset" button on the speaker itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I try using this speaker in Ubuntu, which suggests that Ubuntu is forcing the speaker into "mono" mode and Windows then sees it as a different device? Please help. I will post all needed outputs as instructed. Cheers! --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 3626 F...m pulseaudio /dev/snd/controlC0: david 3626 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-28 (367 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: pulseaudio 1:8.0-0ubuntu3.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Tags: xenial Uname: Linux 4.4.0-87-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.21 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21: dmi.product.name: Aspire V3-571 dmi.product.version: V2.21 dmi.sys.vendor: Acer modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2016-07-29T10:08:04.428983 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707487] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1707487/+attachment/4924484/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1707487 Title: Bluetooth speaker only plays as mono Status in pulseaudio package in Ubuntu: New Bug description: When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only plays back as "mono" and refuses to use "hi fidelity". I have Windows 10 installed on the same laptop and when I've used the Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its Bluetooth list. I have to hold in the "reset" button on the speaker itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I try using this speaker in Ubuntu, which suggests that Ubuntu is forcing the speaker into "mono" mode and Windows then sees it as a different device? Please help. I will post all needed outputs as instructed. Cheers! --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 3626 F...m pulseaudio /dev/snd/controlC0: david 3626 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-28 (367 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: pulseaudio 1:8.0-0ubuntu3.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Tags: xenial Uname: Linux 4.4.0-87-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.21 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21: dmi.product.name: Aspire V3-571 dmi.product.version: V2.21 dmi.sys.vendor: Acer modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2016-07-29T10:08:04.428983 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707487] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1707487/+attachment/4924480/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1707487 Title: Bluetooth speaker only plays as mono Status in pulseaudio package in Ubuntu: New Bug description: When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only plays back as "mono" and refuses to use "hi fidelity". I have Windows 10 installed on the same laptop and when I've used the Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its Bluetooth list. I have to hold in the "reset" button on the speaker itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I try using this speaker in Ubuntu, which suggests that Ubuntu is forcing the speaker into "mono" mode and Windows then sees it as a different device? Please help. I will post all needed outputs as instructed. Cheers! --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 3626 F...m pulseaudio /dev/snd/controlC0: david 3626 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-28 (367 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: pulseaudio 1:8.0-0ubuntu3.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Tags: xenial Uname: Linux 4.4.0-87-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.21 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21: dmi.product.name: Aspire V3-571 dmi.product.version: V2.21 dmi.sys.vendor: Acer modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2016-07-29T10:08:04.428983 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707487] Re: Bluetooth speaker only plays as mono
Now the Ubuntu updater is doing a "partial upgrade". I hope I don't break anything?!! -- 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/1707487 Title: Bluetooth speaker only plays as mono Status in pulseaudio package in Ubuntu: New Bug description: When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only plays back as "mono" and refuses to use "hi fidelity". I have Windows 10 installed on the same laptop and when I've used the Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its Bluetooth list. I have to hold in the "reset" button on the speaker itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I try using this speaker in Ubuntu, which suggests that Ubuntu is forcing the speaker into "mono" mode and Windows then sees it as a different device? Please help. I will post all needed outputs as instructed. Cheers! --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 3626 F...m pulseaudio /dev/snd/controlC0: david 3626 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-28 (367 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: pulseaudio 1:8.0-0ubuntu3.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Tags: xenial Uname: Linux 4.4.0-87-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.21 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21: dmi.product.name: Aspire V3-571 dmi.product.version: V2.21 dmi.sys.vendor: Acer modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2016-07-29T10:08:04.428983 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2
still a problem here: Ubuntu 17.04.1 32 bit sudo service colord status [sudo] password for paz: ● colord.service - Manage, Install and Generate Color Profiles Loaded: loaded (/lib/systemd/system/colord.service; static; vendor preset: enabled) Active: active (running) since Mon 2017-07-31 07:48:17 IDT; 3h 0min ago Main PID: 939 (colord) Tasks: 3 (limit: 4915) CGroup: /system.slice/colord.service └─939 /usr/lib/colord/colord Jul 31 07:48:16 paz-it systemd[1]: Starting Manage, Install and Generate Color Profiles... Jul 31 07:48:17 paz-it systemd[1]: Started Manage, Install and Generate Color Profiles. Jul 31 07:48:17 paz-it colord[939]: failed to get session [pid 825]: No such device or address Jul 31 07:49:06 paz-it colord[939]: failed to get session [pid 1721]: No such device or address -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1442050 Title: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 Status in colord package in Ubuntu: Confirmed Bug description: Get that error logged into journalctl (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 9 11:57:02 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707487] Re: Bluetooth speaker only plays as mono
** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- 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/1707487 Title: Bluetooth speaker only plays as mono Status in pulseaudio package in Ubuntu: New Bug description: When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only plays back as "mono" and refuses to use "hi fidelity". I have Windows 10 installed on the same laptop and when I've used the Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its Bluetooth list. I have to hold in the "reset" button on the speaker itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I try using this speaker in Ubuntu, which suggests that Ubuntu is forcing the speaker into "mono" mode and Windows then sees it as a different device? Please help. I will post all needed outputs as instructed. Cheers! --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 3626 F...m pulseaudio /dev/snd/controlC0: david 3626 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-28 (367 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: pulseaudio 1:8.0-0ubuntu3.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Tags: xenial Uname: Linux 4.4.0-87-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.21 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21: dmi.product.name: Aspire V3-571 dmi.product.version: V2.21 dmi.sys.vendor: Acer modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2016-07-29T10:08:04.428983 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707606] [NEW] [nautilus] no sidebar mouseover selection displayed
Public bug reported: Using nautilus 3.24 in artful, if you dnd a file over one of the folders in the sidebar with Adwaita you get a green selection displayed around the target entry. When using Ambiance there is no such indication ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: gnome-17.10 ** Tags added: gnome-17.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1707606 Title: [nautilus] no sidebar mouseover selection displayed Status in ubuntu-themes package in Ubuntu: New Bug description: Using nautilus 3.24 in artful, if you dnd a file over one of the folders in the sidebar with Adwaita you get a green selection displayed around the target entry. When using Ambiance there is no such indication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1707606/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707611] [NEW] Sound does not automatically play on new audio device
Public bug reported: When connecting a HDMI cable or other audio device, the user must manually click on the "sound volume" in the top-right and switch to the newly connected device. Example: you connect a HDMI cable to the television, but then you must manually choose the HDMI sound option; it does not get selected automatically. Often times e.g. when the HDMI cable is disconnected, the user must then manually click on the "speakers" or "line out" setting - EVEN IF IT'S ALREADY SELECTED, it must be clicked on again for the sound to work through the computer's speakers. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1707611 Title: Sound does not automatically play on new audio device Status in pulseaudio package in Ubuntu: New Bug description: When connecting a HDMI cable or other audio device, the user must manually click on the "sound volume" in the top-right and switch to the newly connected device. Example: you connect a HDMI cable to the television, but then you must manually choose the HDMI sound option; it does not get selected automatically. Often times e.g. when the HDMI cable is disconnected, the user must then manually click on the "speakers" or "line out" setting - EVEN IF IT'S ALREADY SELECTED, it must be clicked on again for the sound to work through the computer's speakers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707487] Re: Bluetooth speaker only plays as mono
I need to report a SIMILAR bug, which affects the same GUI for the audio. Bear with me. -- 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/1707487 Title: Bluetooth speaker only plays as mono Status in pulseaudio package in Ubuntu: New Bug description: When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only plays back as "mono" and refuses to use "hi fidelity". I have Windows 10 installed on the same laptop and when I've used the Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its Bluetooth list. I have to hold in the "reset" button on the speaker itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I try using this speaker in Ubuntu, which suggests that Ubuntu is forcing the speaker into "mono" mode and Windows then sees it as a different device? Please help. I will post all needed outputs as instructed. Cheers! --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 3626 F...m pulseaudio /dev/snd/controlC0: david 3626 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-28 (367 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: pulseaudio 1:8.0-0ubuntu3.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Tags: xenial Uname: Linux 4.4.0-87-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.21 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21: dmi.product.name: Aspire V3-571 dmi.product.version: V2.21 dmi.sys.vendor: Acer modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2016-07-29T10:08:04.428983 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707487] Re: Bluetooth speaker only plays as mono
I have reported a similar bug that affects the same audio GUI: bug number 1707611 Hoping that will help get to the root of the problem. Anything I can do to help, please let me know. I have all the time you need. -- 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/1707487 Title: Bluetooth speaker only plays as mono Status in pulseaudio package in Ubuntu: New Bug description: When I connect my Sony SRS-X1 Bluetooth speaker to Ubuntu, it only plays back as "mono" and refuses to use "hi fidelity". I have Windows 10 installed on the same laptop and when I've used the Bluetooth speaker in Ubuntu, Windows will "forget" the speaker on its Bluetooth list. I have to hold in the "reset" button on the speaker itself and re-add the speaker to Windows 10. This ONLY HAPPENS if I try using this speaker in Ubuntu, which suggests that Ubuntu is forcing the speaker into "mono" mode and Windows then sees it as a different device? Please help. I will post all needed outputs as instructed. Cheers! --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 3626 F...m pulseaudio /dev/snd/controlC0: david 3626 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-28 (367 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: pulseaudio 1:8.0-0ubuntu3.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Tags: xenial Uname: Linux 4.4.0-87-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/16/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.21 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.21:bd12/16/2013:svnAcer:pnAspireV3-571:pvrV2.21:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.21: dmi.product.name: Aspire V3-571 dmi.product.version: V2.21 dmi.sys.vendor: Acer modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2016-07-29T10:08:04.428983 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1707487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707606] Re: [nautilus] no sidebar mouseover selection displayed
same behavior in Nautilus 3.20.4 on Ubuntu 17.04 with light-themes version 16.10+17.10.20170518-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1707606 Title: [nautilus] no sidebar mouseover selection displayed Status in ubuntu-themes package in Ubuntu: New Bug description: Using nautilus 3.24 in artful, if you dnd a file over one of the folders in the sidebar with Adwaita you get a green selection displayed around the target entry. When using Ambiance there is no such indication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1707606/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707236] Re: man page for add-apt-repository doesn't document --update
*** This bug is a duplicate of bug 1559482 *** https://bugs.launchpad.net/bugs/1559482 ** This bug has been marked a duplicate of bug 1559482 add-apt-repository manpage does not mention new -u option -- 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/1707236 Title: man page for add-apt-repository doesn't document --update Status in software-properties package in Ubuntu: Confirmed Bug description: add-apt-repository accepts a --update flag which negates the need to run "apt[-get] update" after adding a repository, but this is undocumented in the man page. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: software-properties-common 0.96.24.13 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Fri Jul 28 16:34:06 2017 InstallationDate: Installed on 2015-07-04 (755 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to zesty on 2017-04-24 (95 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1707236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705951] Re: Ubuntu 17.10 freezes soon after login.
don't install the nvidia driver then, if the stock nouveau driver works? ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers (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/1705951 Title: Ubuntu 17.10 freezes soon after login. Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: Edited 1: After some updates received, it freezes just after login, making any action impossible. I have a PC with a nVidia GeForce 6800XT graphics card. I installed ubuntu 17.10 and have had many problems with crashes and freezes. After login, the normal screen appears, the screen flashes and the top bar disappears, flashes again and appears normal, but frozen. Clicking again blinks back to the login screen. In order to access the system I was forced to install GNOME Classic. I noticed that in ubuntu 17.04 and ubuntu GNOME 16.04 it works normal. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.agp.gpu: Fast Writes: Supported SBA: Supported AGP Rates:8x 4x Registers:0xff000e1b:0x1f000302 .proc.driver.nvidia.agp.host-bridge: Host Bridge: PCI device 1106:0308 Fast Writes: Supported SBA: Supported AGP Rates:8x 4x Registers:0x1f000a1b:0x0b02 .proc.driver.nvidia.agp.status: Status: Enabled Driver: AGPGART AGP Rate: 8x Fast Writes: Disabled SBA: Enabled .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.135 Tue Jan 17 15:26:26 PST 2017 GCC version: gcc version 6.3.0 20170618 (Ubuntu 6.3.0-19ubuntu1) ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jul 23 18:13:59 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.135, 4.11.0-10-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation NV40 [GeForce 6800 XT] [10de:0048] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2017-07-17 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170716) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic root=UUID=7a3a72ab-cccf-4c14-97c3-1dcd85b1aca8 ro recovery nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 11/08/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5VDC-X dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd11/08/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5VDC-X:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.81-2 version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jul 23 18:12:42 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSleep Button KEYBOARD, id 8 inputMicrosoft Basic Optical Mouse MOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.versi
[Touch-packages] [Bug 1559482] Re: add-apt-repository manpage does not mention new -u option
** Branch linked: lp:~adam-collard/software-properties/document-update- flag -- 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/1559482 Title: add-apt-repository manpage does not mention new -u option Status in software-properties package in Ubuntu: Triaged Bug description: The add-apt-repository tool has apparently gained a new option to update the package cache. However, the manpage does not reflect this (as seen on http://manpages.ubuntu.com/manpages/wily/en/man1/add-apt- repository.1.html or http://manpages.ubuntu.com/manpages/xenial/en/man1/add-apt- repository.1.html). While the tool's own help text does mention it, this should be documented in the manpage as well. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: software-properties-common 0.96.13 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 19 21:07:41 2016 InstallationDate: Installed on 2016-02-01 (47 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1559482/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441296] Re: Nautilus invisible focused item when selecting files with Ctrl and arrow keys
The behaviour on 17.04 is still unchanged. Any clues for how to fix, or at least what to look for? ** Changed in: ubuntu-themes Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1441296 Title: Nautilus invisible focused item when selecting files with Ctrl and arrow keys Status in Ubuntu theme: Confirmed Status in ubuntu-themes package in Ubuntu: Expired Bug description: After upgrading to 15.04 beta2 I noticed that selecting files with Ctrl and the arrow keys in Nautilus became more difficult since the active item had no decorations. I'm sure before there was some sort of dashed line around the active item's name, so this may be a regression. I have searched for any other bug report on this, or any other person complaining about it, without success. I tried using the guest account to confirm it wasn't a previous configuration on my regular account, and the issue is also present. Maybe it is uncommon for people to select items in nautilus with the keyboard arrows? I fixed it on my system for Ambiance by adding a dashed line decoration to /usr/share/themes/Ambiance/gtk-3.0/apps/nautilus.css NautilusWindow * { -GtkPaned-handle-size: 1; outline-color: @selected_bg_color; outline-style: dashed; outline-width: 1px; outline-radius: 4px; outline-offset: -1px; } This may need to go in other selector properties, but it worked like this and I couldn't make it to work on any other selector. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1441296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot
** Bug watch added: Debian Bug tracker #806556 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806556 ** Also affects: ntp (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806556 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1706818 Title: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Xenial: Triaged Status in ntp package in Debian: Unknown Bug description: ntpdate and ntp conflict on the NTP well-known-socket. If ntp and ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there are 2 static interfaces configured, most often we find that ntpd is not running after a reboot. When the ntp service is started by systemd, ntp fails to bind the NTP socket because ntpdate is running in the background. It's intended that ntp and ntpdate try to avoid this conflict with a lock file, but the locking mechanism was changed in ntpdate.if-up (from lockfile to flock), but it was not changed in ntp.init. Previously the file locking prevented ntp from trying to start when ntpdate was running. Not any more. Having multiple interfaces causes a much longer period of the socket being unavailable, because the 2 ntpdate processes will get serialized by the lock, while the ntp service is looking for a different lock, so it just plows right in. Attempts by netdate.if-up to stop and start ntp seem to overlap and when the final start is invoked, systemd seems to thing ntp is already running, though it has failed. In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made: debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock now. Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream. This change diverged locking between ntpdate.if-up and ntp.init. This was rectified in rev 451 of ntp.init, to use compatible locking, but that doesn't appear in the Ubuntu version. System Information: lsb_release -rd: Description:Ubuntu 16.04.2 LTS Release:16.04 apt-cache policy ntpdate: ntpdate: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status apt-cache policy ntp: ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot
Note for the server team: what I'd like to determine is if the user impact here justifies an SRU, and if it does, how we should prioritise it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1706818 Title: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Xenial: Triaged Status in ntp package in Debian: Unknown Bug description: ntpdate and ntp conflict on the NTP well-known-socket. If ntp and ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there are 2 static interfaces configured, most often we find that ntpd is not running after a reboot. When the ntp service is started by systemd, ntp fails to bind the NTP socket because ntpdate is running in the background. It's intended that ntp and ntpdate try to avoid this conflict with a lock file, but the locking mechanism was changed in ntpdate.if-up (from lockfile to flock), but it was not changed in ntp.init. Previously the file locking prevented ntp from trying to start when ntpdate was running. Not any more. Having multiple interfaces causes a much longer period of the socket being unavailable, because the 2 ntpdate processes will get serialized by the lock, while the ntp service is looking for a different lock, so it just plows right in. Attempts by netdate.if-up to stop and start ntp seem to overlap and when the final start is invoked, systemd seems to thing ntp is already running, though it has failed. In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made: debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock now. Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream. This change diverged locking between ntpdate.if-up and ntp.init. This was rectified in rev 451 of ntp.init, to use compatible locking, but that doesn't appear in the Ubuntu version. System Information: lsb_release -rd: Description:Ubuntu 16.04.2 LTS Release:16.04 apt-cache policy ntpdate: ntpdate: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status apt-cache policy ntp: ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot
Thank you for taking the time to report this bug and helping to make Ubuntu better. I've confirmed that the issue is as you describe in Xenial. Trusty pre- dates the change to locking in ntp.if-up, so is consistent. Zesty is also consistent in using flock in both places, as is Artful. So this bug affects only Xenial. In order to understand the importance of this bug, please could you explain why you're using both ntp and ntpdate? ntpdate isn't installed by default on Xenial, and shouldn't be required in the normal case because ntp defaults to "-g". So you could work around this bug by just removing the ntpdate package. Is there a particular reason that this won't work in your case? ** Also affects: ntp (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: ntp (Ubuntu) Status: New => Fix Released ** Changed in: ntp (Ubuntu Xenial) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1706818 Title: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Xenial: Triaged Status in ntp package in Debian: Unknown Bug description: ntpdate and ntp conflict on the NTP well-known-socket. If ntp and ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there are 2 static interfaces configured, most often we find that ntpd is not running after a reboot. When the ntp service is started by systemd, ntp fails to bind the NTP socket because ntpdate is running in the background. It's intended that ntp and ntpdate try to avoid this conflict with a lock file, but the locking mechanism was changed in ntpdate.if-up (from lockfile to flock), but it was not changed in ntp.init. Previously the file locking prevented ntp from trying to start when ntpdate was running. Not any more. Having multiple interfaces causes a much longer period of the socket being unavailable, because the 2 ntpdate processes will get serialized by the lock, while the ntp service is looking for a different lock, so it just plows right in. Attempts by netdate.if-up to stop and start ntp seem to overlap and when the final start is invoked, systemd seems to thing ntp is already running, though it has failed. In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made: debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock now. Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream. This change diverged locking between ntpdate.if-up and ntp.init. This was rectified in rev 451 of ntp.init, to use compatible locking, but that doesn't appear in the Ubuntu version. System Information: lsb_release -rd: Description:Ubuntu 16.04.2 LTS Release:16.04 apt-cache policy ntpdate: ntpdate: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status apt-cache policy ntp: ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704399] Re: new binutils snapshot and ocaml cannot build together on arm64
** Changed in: binutils (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1704399 Title: new binutils snapshot and ocaml cannot build together on arm64 Status in binutils package in Ubuntu: Invalid Status in ocaml package in Ubuntu: New Status in ocaml package in Debian: Fix Released Bug description: https://caml.inria.fr/mantis/view.php?id=7585 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1704399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706818] Re: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot
** Changed in: ntp (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1706818 Title: mismatched file locking since 1:4.2.8p4+dfsg-3ubuntu1 causes race leaving ntp dead on reboot Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Xenial: Triaged Status in ntp package in Debian: Fix Released Bug description: ntpdate and ntp conflict on the NTP well-known-socket. If ntp and ntpdate 1:4.2.8p4+dfsg-3ubuntu5.5 are installed on Xenial, and there are 2 static interfaces configured, most often we find that ntpd is not running after a reboot. When the ntp service is started by systemd, ntp fails to bind the NTP socket because ntpdate is running in the background. It's intended that ntp and ntpdate try to avoid this conflict with a lock file, but the locking mechanism was changed in ntpdate.if-up (from lockfile to flock), but it was not changed in ntp.init. Previously the file locking prevented ntp from trying to start when ntpdate was running. Not any more. Having multiple interfaces causes a much longer period of the socket being unavailable, because the 2 ntpdate processes will get serialized by the lock, while the ntp service is looking for a different lock, so it just plows right in. Attempts by netdate.if-up to stop and start ntp seem to overlap and when the final start is invoked, systemd seems to thing ntp is already running, though it has failed. In 1:4.2.8p4+dfsg-3ubuntu1 the following change was made: debian/ntpdate.if-up: Drop lockfile mechanism as upstream is using flock now. Looks like corresponds to rev 371 of debian/ntpdate.if-up from upstream. This change diverged locking between ntpdate.if-up and ntp.init. This was rectified in rev 451 of ntp.init, to use compatible locking, but that doesn't appear in the Ubuntu version. System Information: lsb_release -rd: Description:Ubuntu 16.04.2 LTS Release:16.04 apt-cache policy ntpdate: ntpdate: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status apt-cache policy ntp: ntp: Installed: 1:4.2.8p4+dfsg-3ubuntu5.5 Candidate: 1:4.2.8p4+dfsg-3ubuntu5.5 Version table: *** 1:4.2.8p4+dfsg-3ubuntu5.5 100 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1706818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2
still a problem here: Ubuntu 17.04.1 32 bit sudo service colord status [sudo] password for paz: ● colord.service - Manage, Install and Generate Color Profiles Loaded: loaded (/lib/systemd/system/colord.service; static; vendor preset: enabled) Active: active (running) since Mon 2017-07-31 07:48:17 IDT; 3h 0min ago Main PID: 939 (colord) Tasks: 3 (limit: 4915) CGroup: /system.slice/colord.service └─939 /usr/lib/colord/colord Jul 31 07:48:16 paz-it systemd[1]: Starting Manage, Install and Generate Color Profiles... Jul 31 07:48:17 paz-it systemd[1]: Started Manage, Install and Generate Color Profiles. Jul 31 07:48:17 paz-it colord[939]: failed to get session [pid 825]: No such device or address Jul 31 07:49:06 paz-it colord[939]: failed to get session [pid 1721]: No such device or address -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1442050 Title: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 Status in colord package in Ubuntu: Confirmed Bug description: Get that error logged into journalctl (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 9 11:57:02 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686344] Re: Mesa 17.0.x stable release
I ran this update on my Intel Haswell i7-4700MQ laptop. Tested it with a normal desktop session and didn't encounter any graphics related issues. -- 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/1686344 Title: Mesa 17.0.x stable release Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Zesty: Fix Committed Bug description: [Impact] Mesa stable release for zesty & backport to xenial. Xenial needs newer libdrm from zesty. These are part of the hwe-16.04 stack refresh. [Test case] Install, run desktop session, test xonotic. the important hw drivers to test: - i965 (Intel) - radeonsi (AMD) [Regression potential] Spec compliance test suites are already run by Intel and others, so feature regressions should not be possible. GLESv1 support has been dropped from the packaging though, but packages that depend on libgles1-mesa have been pushed to proposed to drop the dependency, see bug 1676845 (applies to xenial). 17.0.x has been available for xenial and yakkety users for a while, and so far no-one has complained about driver regressions. [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1686344/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1674304] Re: PRIME synchronization not working with xserver-1.19.x in Ubuntu
I even tried to manually load the module with modeset=1, yes. Will have to try again, maybe there has been a change since I last tried that fixes it. But I'm sceptical. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1674304 Title: PRIME synchronization not working with xserver-1.19.x in Ubuntu Status in lightdm package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Bug description: xserver-1.19.x is being proposed for 17.04, currently available in test ppa https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging FFe - https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671799 On 2 separate Optimus laptops there is no sign of it actually working, tearing while using nvidia drivers (375.x) is rampart. Testing with both current 4.10.0-13 & previous 4.9.0-11 kernels. Shows this in kern.log so support is enabled Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746443] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746444] [drm] Driver supports precise vblank timestamp But in Xorg.0.log - randr: falling back to unsynchronized pixmap sharing ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: nvidia-prime 0.8.4 ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Mon Mar 20 07:53:12 2017 InstallationDate: Installed on 2017-03-15 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170311) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1674304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707645] [NEW] system with high numbered uids has huge sparse /var/log/lastlog
Public bug reported: I was investigating the use of a single high UID user (ie, 20) and discovered that /var/log/lastlog grew to an enormously large sparse file: $ ls -lh /var/log/lastlog -rw-rw-r-- 1 root utmp 544G Jul 27 12:35 /var/log/lastlog The file is actually quite small though: $ ls -lh --size /var/log/lastlog 56K -rw-rw-r-- 1 root utmp 544G Jul 27 12:35 /var/log/lastlog On a standalone system, this is possibly not a problem since it is highly unlikely that a system will have 2 billion users, but this is confirmed to wreak havoc on rsync backups. ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1707645 Title: system with high numbered uids has huge sparse /var/log/lastlog Status in util-linux package in Ubuntu: New Bug description: I was investigating the use of a single high UID user (ie, 20) and discovered that /var/log/lastlog grew to an enormously large sparse file: $ ls -lh /var/log/lastlog -rw-rw-r-- 1 root utmp 544G Jul 27 12:35 /var/log/lastlog The file is actually quite small though: $ ls -lh --size /var/log/lastlog 56K -rw-rw-r-- 1 root utmp 544G Jul 27 12:35 /var/log/lastlog On a standalone system, this is possibly not a problem since it is highly unlikely that a system will have 2 billion users, but this is confirmed to wreak havoc on rsync backups. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1707645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704596] Re: Mesa 17 (Ubuntu 16.04 HWE) breaks the dash's blur (dash and launcher are black)
On 16.04 LTS release, the recent update of mesa (17.0.7) packages, broke VA-API. $ LIBVA_DRIVER_NAME='i965' vainfo libva info: VA-API version 0.39.0 libva info: va_getDriverName() returns -1 libva info: User requested driver 'i965' libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_39 vainfo: intel_driver.c:100: intel_driver_init: Assertion `(((struct drm_state *)(ctx)->drm_state)->auth_type == (VA_DRM_AUTH_DRI1)) || (((struct drm_state *)(ctx)->drm_state)->auth_type == (VA_DRM_AUTH_DRI2)) || (((struct drm_state *)(ctx)->drm_state)->auth_type == (VA_DRM_AUTH_CUSTOM))' failed. Aborted (core dumped) -- 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/1704596 Title: Mesa 17 (Ubuntu 16.04 HWE) breaks the dash's blur (dash and launcher are black) Status in mesa package in Ubuntu: Incomplete Bug description: System: Ubuntu 16.04 32-bit + HWE Video card: GF 7300GT Driver: nouveau I'm testing the latest HWE stack. With Mesa 17 and enabled blur activating the dash results in all transparent elements getting black. Also, the launcher and panel are dark when the windows spread/scale is active. Disabling the blur or reverting to Mesa 12 solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1704596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704399] Re: new binutils snapshot and ocaml cannot build together on arm64
This bug was fixed in the package ocaml - 4.04.0-2ubuntu3 --- ocaml (4.04.0-2ubuntu3) artful; urgency=medium * Mark certain symbols as .hidden in arm64 codegen, fixing FTBFS with binutils 2.29. (Closes: #868860). LP: #1704399. -- Matthias Klose Mon, 31 Jul 2017 12:41:45 +0200 ** Changed in: ocaml (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1704399 Title: new binutils snapshot and ocaml cannot build together on arm64 Status in binutils package in Ubuntu: Invalid Status in ocaml package in Ubuntu: Fix Released Status in ocaml package in Debian: Fix Released Bug description: https://caml.inria.fr/mantis/view.php?id=7585 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1704399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704596] Re: Mesa 17 (Ubuntu 16.04 HWE) breaks the dash's blur (dash and launcher are black)
I see little to no point in reportinng this problem upstream, as - unfortunately - there are more bugs in Mesa/Nouveau which freeze the entire system. Currently I'm back to the proprietary driver. -- 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/1704596 Title: Mesa 17 (Ubuntu 16.04 HWE) breaks the dash's blur (dash and launcher are black) Status in mesa package in Ubuntu: Incomplete Bug description: System: Ubuntu 16.04 32-bit + HWE Video card: GF 7300GT Driver: nouveau I'm testing the latest HWE stack. With Mesa 17 and enabled blur activating the dash results in all transparent elements getting black. Also, the launcher and panel are dark when the windows spread/scale is active. Disabling the blur or reverting to Mesa 12 solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1704596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706948] Re: [Ubuntu 1710] [Feature] Inconsistent report of pm CanSuspend state by systemd and pm-utils
** Tags added: triage-g -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1706948 Title: [Ubuntu 1710] [Feature] Inconsistent report of pm CanSuspend state by systemd and pm-utils Status in The Ubuntu-power-systems project: New Status in pm-utils package in Ubuntu: New Bug description: == Comment: #0 - Balamuruhan S <> - 2017-06-28 03:39:15 == systemd and pm-utils interprets CanSuspend states differently and reports it as supported or not in a conflicting way. # gdbus call --system --dest org.freedesktop.login1 --object-path /org/freedesktop/login1 --method org.freedesktop.login1.Manager.CanSuspend ('yes',) # pm-is-supported --suspend # echo $? 1 Both systemd and pm-is-supported looks into /sys/power/state file to check if suspend is supported. pm-is-supported --suspend returns true if either "standby" or "mem" is present in the file. ( /usr/lib/pm-utils/pm-functions ) systemd(Manager.CanSuspend) returns true if "standby", "freeze" or "mem" is present in the file. ( https://github.com/systemd/systemd/blob/dd8352659c9428b196706d04399eec106a8917ed/src/shared/sleep-config.c ) # cat /sys/power/state freeze So here, pm-is-supported --suspend returns false and gdbus returns true. Both these utilities interpret /sys/power/state differently. Secondly, systemd should split CanSuspend to Cansuspend+CanFreeze Or don't report freeze as CanSuspend. Impact of this inconsistency can be felt from Libvirt supported pm states: To reduce ABI dependency, libvirt queries the available states via dbus, if not falls to pm-utils. Libvirt won't check for strings in sys/power/state and interpret directly. so due to this, libvirt will list that suspend_to_mem is supported from virsh capabilities but ideally it might not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1706948/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704596] Re: Mesa 17 (Ubuntu 16.04 HWE) breaks the dash's blur (dash and launcher are black)
ok, closing the bug then aditya: don't hijack bugs. I don't have that issue on my system btw ** Changed in: mesa (Ubuntu) Status: Incomplete => Invalid ** Changed in: mesa (Ubuntu) Assignee: Timo Aaltonen (tjaalton) => (unassigned) -- 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/1704596 Title: Mesa 17 (Ubuntu 16.04 HWE) breaks the dash's blur (dash and launcher are black) Status in mesa package in Ubuntu: Invalid Bug description: System: Ubuntu 16.04 32-bit + HWE Video card: GF 7300GT Driver: nouveau I'm testing the latest HWE stack. With Mesa 17 and enabled blur activating the dash results in all transparent elements getting black. Also, the launcher and panel are dark when the windows spread/scale is active. Disabling the blur or reverting to Mesa 12 solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1704596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686344] Re: Mesa 17.0.x stable release
marked as verified also worth noting is that this version is already in xenial as part of the HWE stack update ** Tags removed: verification-needed ** Tags added: verification-done-zesty -- 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/1686344 Title: Mesa 17.0.x stable release Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Zesty: Fix Committed Bug description: [Impact] Mesa stable release for zesty & backport to xenial. Xenial needs newer libdrm from zesty. These are part of the hwe-16.04 stack refresh. [Test case] Install, run desktop session, test xonotic. the important hw drivers to test: - i965 (Intel) - radeonsi (AMD) [Regression potential] Spec compliance test suites are already run by Intel and others, so feature regressions should not be possible. GLESv1 support has been dropped from the packaging though, but packages that depend on libgles1-mesa have been pushed to proposed to drop the dependency, see bug 1676845 (applies to xenial). 17.0.x has been available for xenial and yakkety users for a while, and so far no-one has complained about driver regressions. [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1686344/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707222] Re: usage of /tmp during boot is not safe due to systemd-tmpfiles-clean
So Something is definitely cleaning on boot. Maybe I just misunderstood your statement, but above it seems like you were saying that only old files named like those would be removed. Try this: $ lxc launch ubuntu-daily:artful a1 $ lxc exec a1 -- touch /tmp/foo $ lxc restart a1 $ lxc exec a1 -- ls -l /tmp/foo ls: cannot access '/tmp/foo': No such file or directory ** Changed in: systemd (Ubuntu) Status: Incomplete => Confirmed -- 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/1707222 Title: usage of /tmp during boot is not safe due to systemd-tmpfiles-clean Status in cloud-init: New Status in cloud-init package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Bug description: Earlier this week on Zesty on Azure I saw a cloud-init failure in its 'mount_cb' function. That function esentially does: a.) make a tmp directory for a mount point b.) mount some filesystem to that mount point c.) call a function d.) unmount the directory What I recall was that access to a file inside the mount point failed during 'c'. This seems possible as systemd-tmpfiles-clean may be running at the same time as cloud-init (cloud-init.service in this example). It seems that this service basically inhibits *any* other service from using tmp files. It's ordering statements are only: After=local-fs.target time-sync.target Before=shutdown.target So while in most cases only services that run early in the boot process like cloud-init will be affected, any service could have its tmp files removed. this service could take quite a long time to run if /tmp/ had been filled with lots of files in the previous boot. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1707222/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641272] Re: Debug symbols package doesnt exist
** Description changed: - On Yakkery with ddebs repos enabled there is no debug packages for + On Yakkety with ddebs repos enabled there is no debug packages for dnsmasq -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1641272 Title: Debug symbols package doesnt exist Status in dnsmasq package in Ubuntu: New Bug description: On Yakkety with ddebs repos enabled there is no debug packages for dnsmasq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1641272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706195] Re: whoopsie can start before network-manager during boot
This bug was fixed in the package whoopsie - 0.2.52.5 --- whoopsie (0.2.52.5) xenial-proposed; urgency=medium * Modify the whoopsie service file to wants=networking-online.target too. (LP: #1706195) -- Brian Murray Tue, 25 Jul 2017 13:08:46 -0700 ** Changed in: whoopsie (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 whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1706195 Title: whoopsie can start before network-manager during boot Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Xenial: Fix Released Status in whoopsie source package in Zesty: Fix Released Bug description: [Impact] whoopsie can start before network-manager and then will only work when a networking device state changes, however since it started before n-m it should notice the connection come on-line. This is upload is just in case there are some corner cases out there where whoopsie isn't working and uploading the crashes to the Error Tracker. [Test Case] 1) Boot a system with the old version of whoopsie 2) Run 'systemctl status whoopsie' 3) Observe: Jul 25 11:07:01 clean-zesty-amd64 systemd[1]: Started crash report submission daemon. Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] Using lock path: /var/lock/whoopsie/lock Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] Could not get the Network Manager state: Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files Jul 25 11:07:02 clean-zesty-amd64 whoopsie[446]: [11:07:02] offline With the version of whoopsie in -proposed you'll see the following: Jul 25 11:10:33 clean-zesty-amd64 systemd[1]: Started crash report submission daemon. Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Using lock path: /var/lock/whoopsie/lock Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/0 Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/0 Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/0 [Regression Potential] If whoopsie is working properly when it wasn't, this shouldn't be the case because whoopsie would start working when the network connection changed, then people might be surprised by additional network activity (uploading of crashes) and the Error Tracker may receive more crash reports. Original Description whoopsie's systemd service file does not start after networking which is incorrect since it initially needs to query network-manager's state. A fix was attempted by changing the service file to include "After=network-online.target" but this was insufficient. The following messages demonstrate the failure, if whoopsie were to start after network-manager we would not see them: Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] Could not get the Network Manager state: Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1706195/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706195] Update Released
The verification of the Stable Release Update for whoopsie 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 whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1706195 Title: whoopsie can start before network-manager during boot Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Xenial: Fix Released Status in whoopsie source package in Zesty: Fix Released Bug description: [Impact] whoopsie can start before network-manager and then will only work when a networking device state changes, however since it started before n-m it should notice the connection come on-line. This is upload is just in case there are some corner cases out there where whoopsie isn't working and uploading the crashes to the Error Tracker. [Test Case] 1) Boot a system with the old version of whoopsie 2) Run 'systemctl status whoopsie' 3) Observe: Jul 25 11:07:01 clean-zesty-amd64 systemd[1]: Started crash report submission daemon. Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] Using lock path: /var/lock/whoopsie/lock Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] Could not get the Network Manager state: Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files Jul 25 11:07:02 clean-zesty-amd64 whoopsie[446]: [11:07:02] offline With the version of whoopsie in -proposed you'll see the following: Jul 25 11:10:33 clean-zesty-amd64 systemd[1]: Started crash report submission daemon. Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Using lock path: /var/lock/whoopsie/lock Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/0 Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/0 Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/0 [Regression Potential] If whoopsie is working properly when it wasn't, this shouldn't be the case because whoopsie would start working when the network connection changed, then people might be surprised by additional network activity (uploading of crashes) and the Error Tracker may receive more crash reports. Original Description whoopsie's systemd service file does not start after networking which is incorrect since it initially needs to query network-manager's state. A fix was attempted by changing the service file to include "After=network-online.target" but this was insufficient. The following messages demonstrate the failure, if whoopsie were to start after network-manager we would not see them: Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] Could not get the Network Manager state: Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1706195/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706195] Re: whoopsie can start before network-manager during boot
This bug was fixed in the package whoopsie - 0.2.55.2 --- whoopsie (0.2.55.2) zesty-proposed; urgency=medium * Modify the whoopsie service file to wants=networking-online.target too. (LP: #1706195) -- Brian Murray Tue, 25 Jul 2017 13:01:28 -0700 ** Changed in: whoopsie (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1706195 Title: whoopsie can start before network-manager during boot Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Xenial: Fix Released Status in whoopsie source package in Zesty: Fix Released Bug description: [Impact] whoopsie can start before network-manager and then will only work when a networking device state changes, however since it started before n-m it should notice the connection come on-line. This is upload is just in case there are some corner cases out there where whoopsie isn't working and uploading the crashes to the Error Tracker. [Test Case] 1) Boot a system with the old version of whoopsie 2) Run 'systemctl status whoopsie' 3) Observe: Jul 25 11:07:01 clean-zesty-amd64 systemd[1]: Started crash report submission daemon. Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] Using lock path: /var/lock/whoopsie/lock Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] Could not get the Network Manager state: Jul 25 11:07:01 clean-zesty-amd64 whoopsie[446]: [11:07:01] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files Jul 25 11:07:02 clean-zesty-amd64 whoopsie[446]: [11:07:02] offline With the version of whoopsie in -proposed you'll see the following: Jul 25 11:10:33 clean-zesty-amd64 systemd[1]: Started crash report submission daemon. Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Using lock path: /var/lock/whoopsie/lock Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/0 Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/0 Jul 25 11:10:33 clean-zesty-amd64 whoopsie[1192]: [11:10:33] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/0 [Regression Potential] If whoopsie is working properly when it wasn't, this shouldn't be the case because whoopsie would start working when the network connection changed, then people might be surprised by additional network activity (uploading of crashes) and the Error Tracker may receive more crash reports. Original Description whoopsie's systemd service file does not start after networking which is incorrect since it initially needs to query network-manager's state. A fix was attempted by changing the service file to include "After=network-online.target" but this was insufficient. The following messages demonstrate the failure, if whoopsie were to start after network-manager we would not see them: Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] Could not get the Network Manager state: Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1706195/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows
Leaving instances running shows that both xenial and zesty got unattended upgrade logs / attempts around 6:30am every day. Marking xenial as good. And will redo zesty upgrade test again to make sure units are started for the upgrade timer. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1686470 Title: Apt updates that are uniformly spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: Fix Committed Status in unattended-upgrades source package in Xenial: Triaged Status in apt source package in Yakkety: Won't Fix Status in unattended-upgrades source package in Yakkety: Won't Fix Status in apt source package in Zesty: Fix Committed Status in unattended-upgrades source package in Zesty: Triaged Status in apt source package in Artful: Fix Released Status in unattended-upgrades source package in Artful: Triaged Status in apt package in Debian: Fix Released Status in unattended-upgrades package in Debian: Fix Committed Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they preffer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707645] Re: system with high numbered uids has huge sparse /var/log/lastlog
FYI, people using rsync for backups might be interested in the --sparse (-S) option. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1707645 Title: system with high numbered uids has huge sparse /var/log/lastlog Status in util-linux package in Ubuntu: New Bug description: I was investigating the use of a single high UID user (ie, 20) and discovered that /var/log/lastlog grew to an enormously large sparse file: $ ls -lh /var/log/lastlog -rw-rw-r-- 1 root utmp 544G Jul 27 12:35 /var/log/lastlog The file is actually quite small though: $ ls -lh --size /var/log/lastlog 56K -rw-rw-r-- 1 root utmp 544G Jul 27 12:35 /var/log/lastlog On a standalone system, this is possibly not a problem since it is highly unlikely that a system will have 2 billion users, but this is confirmed to wreak havoc on rsync backups. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1707645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686470] Update Released
The verification of the Stable Release Update for apt 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1686470 Title: Apt updates that are uniformly spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: Fix Released Status in unattended-upgrades source package in Xenial: Triaged Status in apt source package in Yakkety: Won't Fix Status in unattended-upgrades source package in Yakkety: Won't Fix Status in apt source package in Zesty: Fix Committed Status in unattended-upgrades source package in Zesty: Triaged Status in apt source package in Artful: Fix Released Status in unattended-upgrades source package in Artful: Triaged Status in apt package in Debian: Fix Released Status in unattended-upgrades package in Debian: Fix Committed Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they preffer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1694697] Re: build-depends keeps OR flag if end of or group is ignored
This bug was fixed in the package apt - 1.2.24 --- apt (1.2.24) xenial; urgency=medium * Microrelease covering fixes of 1.4.6 * Fix parsing of or groups in build-deps with ignored packages (LP: #1694697) * apt.systemd.daily: Use unattended-ugrade --download-only if available. Instead of passing -d, which enables a debugging mode; check if unattended-upgrade supports an option --download-only (which is yet to be implemented) and use that (Closes: #863859) apt (1.2.23) xenial; urgency=medium * Microrelease covering fixes of 1.4.4 [ Alan Jenkins ] * apt.systemd.daily: fix error from locking code (Closes: #862567) apt (1.2.22) xenial; urgency=medium [ Julian Andres Klode ] * Run unattended-upgrade -d in download part * apt.systemd.daily: Add locking * Split apt-daily timer into two (LP: #1686470) [ Matt Kraai ] * bash-completion: Fix spelling of autoclean (Closes: #861846) apt (1.2.21) xenial; urgency=medium * Microrelease covering fixes of 1.4 and 1.4.1 [ Julian Andres Klode ] * Ignore \.ucf-[a-z]+$ like we do for \.dpkg-[a-z]+$ * systemd: Rework timing and add After=network-online (was LP #1615482) [ David Kalnischkies ] * Fix and avoid quoting in CommandLine::AsString (LP: #1672710) [ Unit 193 ] * apt-ftparchive: Support '.ddeb' dbgsym packages -- Julian Andres Klode Mon, 19 Jun 2017 13:58:04 +0200 ** Changed in: apt (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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1694697 Title: build-depends keeps OR flag if end of or group is ignored Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: New Status in apt source package in Xenial: Fix Released Status in apt source package in Yakkety: Won't Fix Status in apt source package in Zesty: Fix Committed Bug description: [Impact] If the last alternative(s) of an Or group is ignored, because it does not match an architecture list, we would end up keeping the or flag, effectively making the next AND an OR. For example, when parsing (on amd64): debhelper (>= 9), libnacl-dev [amd64] | libnacl-dev [i386] => debhelper (>= 9), libnacl-dev | Which can cause python-apt and apt-get build-dep to crash. Even worse: debhelper (>= 9), libnacl-dev [amd64] | libnacl-dev [i386], foobar => debhelper (>= 9), libnacl-dev [amd64] | foobar [Test case] On amd64: cat > segv.dsc << EOF Format: 3.0 (native) Source: foobar Binary: foobar Architecture: all Version: 1 Maintainer: Joe Sixpack Build-Depends: build-essential [amd64] | build-essential [fancy] Standards-Version: 3.9.8 EOF cat > failure.dsc << EOF Format: 3.0 (native) Source: foobar Binary: foobar Architecture: all Version: 1 Maintainer: Joe Sixpack Build-Depends: build-essential [amd64] | build-essential [fancy], a-non-existing-package Standards-Version: 3.9.8 EOF (1) apt-get build-dep -s ./segv.dsc should succeed instead of crash (2) apt-get build-dep -s ./failure.dsc should complain about "Depends: a-non-existing-package but it is not installable" instead of succeeding. This is the same test as run by CI and autopkgtests, so if they pass the tests passed. You can also run apt-get build-dep -s dq for a real life example that should not segfault. [Regression Potential] apt-get build-dep and friends can now fail where they succeeded previously for packages that employ architecture-limited alternatives in their build depends, as in the second example given above, because now additional packages need to be installed (which is correct, though). [Other info] By setting the previous alternatives Or flag to the current Or flag if the current alternative is ignored, we solve the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1694697/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1672710] Re: apt fails to verify keys when Dir has space, and set via cmdline
This bug was fixed in the package apt - 1.2.24 --- apt (1.2.24) xenial; urgency=medium * Microrelease covering fixes of 1.4.6 * Fix parsing of or groups in build-deps with ignored packages (LP: #1694697) * apt.systemd.daily: Use unattended-ugrade --download-only if available. Instead of passing -d, which enables a debugging mode; check if unattended-upgrade supports an option --download-only (which is yet to be implemented) and use that (Closes: #863859) apt (1.2.23) xenial; urgency=medium * Microrelease covering fixes of 1.4.4 [ Alan Jenkins ] * apt.systemd.daily: fix error from locking code (Closes: #862567) apt (1.2.22) xenial; urgency=medium [ Julian Andres Klode ] * Run unattended-upgrade -d in download part * apt.systemd.daily: Add locking * Split apt-daily timer into two (LP: #1686470) [ Matt Kraai ] * bash-completion: Fix spelling of autoclean (Closes: #861846) apt (1.2.21) xenial; urgency=medium * Microrelease covering fixes of 1.4 and 1.4.1 [ Julian Andres Klode ] * Ignore \.ucf-[a-z]+$ like we do for \.dpkg-[a-z]+$ * systemd: Rework timing and add After=network-online (was LP #1615482) [ David Kalnischkies ] * Fix and avoid quoting in CommandLine::AsString (LP: #1672710) [ Unit 193 ] * apt-ftparchive: Support '.ddeb' dbgsym packages -- Julian Andres Klode Mon, 19 Jun 2017 13:58:04 +0200 ** Changed in: apt (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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1672710 Title: apt fails to verify keys when Dir has space, and set via cmdline Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Released Status in apt source package in Yakkety: Won't Fix Bug description: When Dir has a space, and it is set via APT_CONFIG file, keys are found and validated correctly. When Dir is set without a space via cmdline, keys are found and validated correctly. When Dir is set with a space via cmdline, keys are not found and repositories are not verified. [Test case] Please see attached reproducer, which works on xenial system (gpg1) but not on zesty system (gpg2) $ bash reproducer.sh ++ mktemp -d + tmpdir=/tmp/tmp.sFipy6h5yL + pushd /tmp/tmp.sFipy6h5yL /tmp/tmp.sFipy6h5yL ~ + mkdir 'Sub Dir' + pushd 'Sub Dir' /tmp/tmp.sFipy6h5yL/Sub Dir /tmp/tmp.sFipy6h5yL ~ + mkdir -p etc/apt/apt.conf.d + mkdir -p etc/apt/trusted.gpg.d + mkdir -p etc/apt/preferences.d + mkdir -p var/lib/apt/lists/partial + mkdir -p var/lib/dpkg + touch var/lib/dpkg/status + cp /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg etc/apt/trusted.gpg.d/ + echo 'deb http://archive.ubuntu.com/ubuntu/ trusty main' + echo 'Dir "/tmp/tmp.sFipy6h5yL/Sub Dir";' + export APT_CONFIG=/tmp/tmp.sFipy6h5yL/apt.conf + APT_CONFIG=/tmp/tmp.sFipy6h5yL/apt.conf + cat /tmp/tmp.sFipy6h5yL/apt.conf Dir "/tmp/tmp.sFipy6h5yL/Sub Dir"; + : + : == list available keys == + apt-key list /tmp/tmp.sFipy6h5yL/Sub Dir/etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg - pub rsa4096 2012-05-11 [SC] 790B C727 7767 219C 42C8 6F93 3B4F E6AC C0B2 1F32 uid [ unknown] Ubuntu Archive Automatic Signing Key (2012) + : + : == update with environ APT_CONFIG setting the Dir variable == + apt update Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease Get:2 http://archive.ubuntu.com/ubuntu trusty Release [58.5 kB] Get:3 http://archive.ubuntu.com/ubuntu trusty Release.gpg [933 B] Get:4 http://archive.ubuntu.com/ubuntu trusty/main amd64 Packages [1,350 kB] Fetched 1,410 kB in 0s (1,959 kB/s) Reading package lists... Done Building dependency tree... Done All packages are up to date. + unset APT_CONFIG + : + : == update with cmdline Dir option setting Dir to relative pwd == + apt -o Dir=./ update Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease Hit:2 http://archive.ubuntu.com/ubuntu trusty Release Reading package lists... Done Building dependency tree... Done All packages are up to date. + : + : == update with cmdline Dir option setting Dir to absolute pwd with space == + apt -o 'Dir=/tmp/tmp.sFipy6h5yL/Sub Dir' update Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease Hit:2 http://archive.ubuntu.com/ubuntu trusty Release Err:3 http://archive.ubuntu.com/ubuntu trusty Release.gpg The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 Reading package lists... Done Building dependency tree... Done All packages are up to date. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. G
[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows
This bug was fixed in the package apt - 1.2.24 --- apt (1.2.24) xenial; urgency=medium * Microrelease covering fixes of 1.4.6 * Fix parsing of or groups in build-deps with ignored packages (LP: #1694697) * apt.systemd.daily: Use unattended-ugrade --download-only if available. Instead of passing -d, which enables a debugging mode; check if unattended-upgrade supports an option --download-only (which is yet to be implemented) and use that (Closes: #863859) apt (1.2.23) xenial; urgency=medium * Microrelease covering fixes of 1.4.4 [ Alan Jenkins ] * apt.systemd.daily: fix error from locking code (Closes: #862567) apt (1.2.22) xenial; urgency=medium [ Julian Andres Klode ] * Run unattended-upgrade -d in download part * apt.systemd.daily: Add locking * Split apt-daily timer into two (LP: #1686470) [ Matt Kraai ] * bash-completion: Fix spelling of autoclean (Closes: #861846) apt (1.2.21) xenial; urgency=medium * Microrelease covering fixes of 1.4 and 1.4.1 [ Julian Andres Klode ] * Ignore \.ucf-[a-z]+$ like we do for \.dpkg-[a-z]+$ * systemd: Rework timing and add After=network-online (was LP #1615482) [ David Kalnischkies ] * Fix and avoid quoting in CommandLine::AsString (LP: #1672710) [ Unit 193 ] * apt-ftparchive: Support '.ddeb' dbgsym packages -- Julian Andres Klode Mon, 19 Jun 2017 13:58:04 +0200 ** Changed in: apt (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 unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1686470 Title: Apt updates that are uniformly spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: Fix Released Status in unattended-upgrades source package in Xenial: Triaged Status in apt source package in Yakkety: Won't Fix Status in unattended-upgrades source package in Yakkety: Won't Fix Status in apt source package in Zesty: Fix Committed Status in unattended-upgrades source package in Zesty: Triaged Status in apt source package in Artful: Fix Released Status in unattended-upgrades source package in Artful: Triaged Status in apt package in Debian: Fix Released Status in unattended-upgrades package in Debian: Fix Committed Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with th
[Touch-packages] [Bug 1672710] Update Released
The verification of the Stable Release Update for apt 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1672710 Title: apt fails to verify keys when Dir has space, and set via cmdline Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Released Status in apt source package in Yakkety: Won't Fix Bug description: When Dir has a space, and it is set via APT_CONFIG file, keys are found and validated correctly. When Dir is set without a space via cmdline, keys are found and validated correctly. When Dir is set with a space via cmdline, keys are not found and repositories are not verified. [Test case] Please see attached reproducer, which works on xenial system (gpg1) but not on zesty system (gpg2) $ bash reproducer.sh ++ mktemp -d + tmpdir=/tmp/tmp.sFipy6h5yL + pushd /tmp/tmp.sFipy6h5yL /tmp/tmp.sFipy6h5yL ~ + mkdir 'Sub Dir' + pushd 'Sub Dir' /tmp/tmp.sFipy6h5yL/Sub Dir /tmp/tmp.sFipy6h5yL ~ + mkdir -p etc/apt/apt.conf.d + mkdir -p etc/apt/trusted.gpg.d + mkdir -p etc/apt/preferences.d + mkdir -p var/lib/apt/lists/partial + mkdir -p var/lib/dpkg + touch var/lib/dpkg/status + cp /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg etc/apt/trusted.gpg.d/ + echo 'deb http://archive.ubuntu.com/ubuntu/ trusty main' + echo 'Dir "/tmp/tmp.sFipy6h5yL/Sub Dir";' + export APT_CONFIG=/tmp/tmp.sFipy6h5yL/apt.conf + APT_CONFIG=/tmp/tmp.sFipy6h5yL/apt.conf + cat /tmp/tmp.sFipy6h5yL/apt.conf Dir "/tmp/tmp.sFipy6h5yL/Sub Dir"; + : + : == list available keys == + apt-key list /tmp/tmp.sFipy6h5yL/Sub Dir/etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg - pub rsa4096 2012-05-11 [SC] 790B C727 7767 219C 42C8 6F93 3B4F E6AC C0B2 1F32 uid [ unknown] Ubuntu Archive Automatic Signing Key (2012) + : + : == update with environ APT_CONFIG setting the Dir variable == + apt update Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease Get:2 http://archive.ubuntu.com/ubuntu trusty Release [58.5 kB] Get:3 http://archive.ubuntu.com/ubuntu trusty Release.gpg [933 B] Get:4 http://archive.ubuntu.com/ubuntu trusty/main amd64 Packages [1,350 kB] Fetched 1,410 kB in 0s (1,959 kB/s) Reading package lists... Done Building dependency tree... Done All packages are up to date. + unset APT_CONFIG + : + : == update with cmdline Dir option setting Dir to relative pwd == + apt -o Dir=./ update Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease Hit:2 http://archive.ubuntu.com/ubuntu trusty Release Reading package lists... Done Building dependency tree... Done All packages are up to date. + : + : == update with cmdline Dir option setting Dir to absolute pwd with space == + apt -o 'Dir=/tmp/tmp.sFipy6h5yL/Sub Dir' update Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease Hit:2 http://archive.ubuntu.com/ubuntu trusty Release Err:3 http://archive.ubuntu.com/ubuntu trusty Release.gpg The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 Reading package lists... Done Building dependency tree... Done All packages are up to date. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.ubuntu.com/ubuntu trusty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/Release.gpg The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: Some index files failed to download. They have been ignored, or old ones used instead. [Regression Potential] The fix changes the code to generate quotes in the Commmandline:AsString option, which dumps the command line for logging purposes. This was not parseable before, causing the file to be rejected, so what can happen is that something now works that did not before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1672710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-package
[Touch-packages] [Bug 1700826] Re: please include numactl on the ubuntu-server iso
** Branch linked: lp:~dannf/ubuntu-seeds/numactl.artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1700826 Title: please include numactl on the ubuntu-server iso Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Xenial: New Status in ubuntu-meta source package in Zesty: New Bug description: I've submitted an MIR for the numactl binary package at: LP: #1700824. Assuming that is approved, please also include this on the server seed, which I believe is necessary for it to appear on the ubuntu-server ISOs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1700826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1694697] Update Released
The verification of the Stable Release Update for apt 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1694697 Title: build-depends keeps OR flag if end of or group is ignored Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: New Status in apt source package in Xenial: Fix Released Status in apt source package in Yakkety: Won't Fix Status in apt source package in Zesty: Fix Committed Bug description: [Impact] If the last alternative(s) of an Or group is ignored, because it does not match an architecture list, we would end up keeping the or flag, effectively making the next AND an OR. For example, when parsing (on amd64): debhelper (>= 9), libnacl-dev [amd64] | libnacl-dev [i386] => debhelper (>= 9), libnacl-dev | Which can cause python-apt and apt-get build-dep to crash. Even worse: debhelper (>= 9), libnacl-dev [amd64] | libnacl-dev [i386], foobar => debhelper (>= 9), libnacl-dev [amd64] | foobar [Test case] On amd64: cat > segv.dsc << EOF Format: 3.0 (native) Source: foobar Binary: foobar Architecture: all Version: 1 Maintainer: Joe Sixpack Build-Depends: build-essential [amd64] | build-essential [fancy] Standards-Version: 3.9.8 EOF cat > failure.dsc << EOF Format: 3.0 (native) Source: foobar Binary: foobar Architecture: all Version: 1 Maintainer: Joe Sixpack Build-Depends: build-essential [amd64] | build-essential [fancy], a-non-existing-package Standards-Version: 3.9.8 EOF (1) apt-get build-dep -s ./segv.dsc should succeed instead of crash (2) apt-get build-dep -s ./failure.dsc should complain about "Depends: a-non-existing-package but it is not installable" instead of succeeding. This is the same test as run by CI and autopkgtests, so if they pass the tests passed. You can also run apt-get build-dep -s dq for a real life example that should not segfault. [Regression Potential] apt-get build-dep and friends can now fail where they succeeded previously for packages that employ architecture-limited alternatives in their build depends, as in the second example given above, because now additional packages need to be installed (which is correct, though). [Other info] By setting the previous alternatives Or flag to the current Or flag if the current alternative is ignored, we solve the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1694697/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707680] [NEW] RM: obsolete product
Public bug reported: pay-service was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:pay-service No reverse dependencies found $ reverse-depends -b src:pay-service No reverse dependencies found -- ubuntu-push was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:ubuntu-push Reverse-Depends === * pay-service (for ubuntu-push-client) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x $ reverse-depends -b src:ubuntu-push No reverse dependencies found -- Unity8 was a component of Ubuntu which is no longer developed. $ reverse-depends src:unity8 Reverse-Depends === * ubuntu-push-autopilot (for unity8-autopilot) Packages without architectures listed are reverse-dependencies in: amd64, armhf, i386 $ reverse-depends -b src:unity8 No reverse dependencies found ** Affects: pay-service (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: ubuntu-push (Ubuntu) Importance: High Status: New ** Affects: unity8 (Ubuntu) Importance: Medium Status: New ** Tags: u8rm ** Changed in: pay-service (Ubuntu) Status: New => Triaged ** Also affects: ubuntu-push (Ubuntu) Importance: Undecided Status: New ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Description changed: pay-service was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:pay-service No reverse dependencies found $ reverse-depends -b src:pay-service No reverse dependencies found + + + -- + + ubuntu-push was a component of Ubuntu Phone which is no longer + developed. + + Please remove this package from the Ubuntu Archive. + + $ reverse-depends src:ubuntu-push + Reverse-Depends + === + * pay-service (for ubuntu-push-client) + + Packages without architectures listed are reverse-dependencies in: + amd64, arm64, armhf, i386, ppc64el, s390x + + $ reverse-depends -b src:ubuntu-push + No reverse dependencies found + + -- + Unity8 was a component of Ubuntu which is no longer developed. + + $ reverse-depends src:unity8 + Reverse-Depends + === + * ubuntu-push-autopilot (for unity8-autopilot) + + Packages without architectures listed are reverse-dependencies in: + amd64, armhf, i386 + + $ reverse-depends -b src:unity8 + No reverse dependencies found ** Changed in: pay-service (Ubuntu) Importance: Undecided => Critical ** Changed in: ubuntu-push (Ubuntu) Importance: Undecided => High ** Changed in: unity8 (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1707680 Title: RM: obsolete product Status in pay-service package in Ubuntu: Fix Released Status in ubuntu-push package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: pay-service was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:pay-service No reverse dependencies found $ reverse-depends -b src:pay-service No reverse dependencies found -- ubuntu-push was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:ubuntu-push Reverse-Depends === * pay-service (for ubuntu-push-client) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x $ reverse-depends -b src:ubuntu-push No reverse dependencies found -- Unity8 was a component of Ubuntu which is no longer developed. $ reverse-depends src:unity8 Reverse-Depends === * ubuntu-push-autopilot (for unity8-autopilot) Packages without architectures listed are reverse-dependencies in: amd64, armhf, i386 $ reverse-depends -b src:unity8 No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pay-service/+bug/1707680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707680] Re: RM: obsolete product
Removing packages from artful: pay-service 15.10+17.04.20170211-0ubuntu2 in artful libpay2 15.10+17.04.20170211-0ubuntu2 in artful amd64 libpay2 15.10+17.04.20170211-0ubuntu2 in artful arm64 libpay2 15.10+17.04.20170211-0ubuntu2 in artful armhf libpay2 15.10+17.04.20170211-0ubuntu2 in artful i386 libpay2 15.10+17.04.20170211-0ubuntu2 in artful ppc64el libpay2 15.10+17.04.20170211-0ubuntu2 in artful s390x libpay2-dev 15.10+17.04.20170211-0ubuntu2 in artful amd64 libpay2-dev 15.10+17.04.20170211-0ubuntu2 in artful arm64 libpay2-dev 15.10+17.04.20170211-0ubuntu2 in artful armhf libpay2-dev 15.10+17.04.20170211-0ubuntu2 in artful i386 libpay2-dev 15.10+17.04.20170211-0ubuntu2 in artful ppc64el libpay2-dev 15.10+17.04.20170211-0ubuntu2 in artful s390x pay-service 15.10+17.04.20170211-0ubuntu2 in artful amd64 pay-service 15.10+17.04.20170211-0ubuntu2 in artful arm64 pay-service 15.10+17.04.20170211-0ubuntu2 in artful armhf pay-service 15.10+17.04.20170211-0ubuntu2 in artful i386 pay-service 15.10+17.04.20170211-0ubuntu2 in artful ppc64el pay-service 15.10+17.04.20170211-0ubuntu2 in artful s390x pay-test-app 15.10+17.04.20170211-0ubuntu2 in artful amd64 pay-test-app 15.10+17.04.20170211-0ubuntu2 in artful arm64 pay-test-app 15.10+17.04.20170211-0ubuntu2 in artful armhf pay-test-app 15.10+17.04.20170211-0ubuntu2 in artful i386 pay-test-app 15.10+17.04.20170211-0ubuntu2 in artful ppc64el pay-test-app 15.10+17.04.20170211-0ubuntu2 in artful s390x pay-ui 15.10+17.04.20170211-0ubuntu2 in artful amd64 pay-ui 15.10+17.04.20170211-0ubuntu2 in artful arm64 pay-ui 15.10+17.04.20170211-0ubuntu2 in artful armhf pay-ui 15.10+17.04.20170211-0ubuntu2 in artful i386 pay-ui 15.10+17.04.20170211-0ubuntu2 in artful ppc64el pay-ui 15.10+17.04.20170211-0ubuntu2 in artful s390x Comment: part of Ubuntu phone stack, no longer shipping; LP: #1707680 1 package successfully removed. ** Changed in: pay-service (Ubuntu) Importance: Critical => Undecided ** Changed in: pay-service (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1707680 Title: RM: obsolete product Status in pay-service package in Ubuntu: Fix Released Status in ubuntu-push package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: pay-service was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:pay-service No reverse dependencies found $ reverse-depends -b src:pay-service No reverse dependencies found -- ubuntu-push was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:ubuntu-push Reverse-Depends === * pay-service (for ubuntu-push-client) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x $ reverse-depends -b src:ubuntu-push No reverse dependencies found -- Unity8 was a component of Ubuntu which is no longer developed. $ reverse-depends src:unity8 Reverse-Depends === * ubuntu-push-autopilot (for unity8-autopilot) Packages without architectures listed are reverse-dependencies in: amd64, armhf, i386 $ reverse-depends -b src:unity8 No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pay-service/+bug/1707680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707222] Re: usage of /tmp during boot is not safe due to systemd-tmpfiles-clean
/tmp is only guaranteed to be in a usable state after sysinit.target currently. Or more generally, after system is fully up only. During boot (initramfs, post-initramfs, early boot, post-boot) system services should use /run, private runtime dir, private tmp dir. This is not a bug in Ubuntu boot sequence. Please fix cloud-init to use /run. ** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix -- 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/1707222 Title: usage of /tmp during boot is not safe due to systemd-tmpfiles-clean Status in cloud-init: New Status in cloud-init package in Ubuntu: New Status in systemd package in Ubuntu: Won't Fix Bug description: Earlier this week on Zesty on Azure I saw a cloud-init failure in its 'mount_cb' function. That function esentially does: a.) make a tmp directory for a mount point b.) mount some filesystem to that mount point c.) call a function d.) unmount the directory What I recall was that access to a file inside the mount point failed during 'c'. This seems possible as systemd-tmpfiles-clean may be running at the same time as cloud-init (cloud-init.service in this example). It seems that this service basically inhibits *any* other service from using tmp files. It's ordering statements are only: After=local-fs.target time-sync.target Before=shutdown.target So while in most cases only services that run early in the boot process like cloud-init will be affected, any service could have its tmp files removed. this service could take quite a long time to run if /tmp/ had been filled with lots of files in the previous boot. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1707222/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
Re inhibitor: One can run u-u --download-only from cron first without the inhibitor then the full u-u with the inhibitor. While this method does not allow per-transaction granularity, it is a fairly good solution without added complexity. I someone comes up with a proper patch it may be integrated but I think this is out of the scope of this bug. The committed solution already provides the per-transaction stopping granularity when u-u is started by apt's service. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Fix Committed Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700826] Re: please include numactl on the ubuntu-server iso
** Branch linked: lp:~dannf/ubuntu-seeds/numactl.xenial ** Branch linked: lp:~dannf/ubuntu-seeds/numactl.xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1700826 Title: please include numactl on the ubuntu-server iso Status in ubuntu-meta package in Ubuntu: In Progress Status in ubuntu-meta source package in Xenial: In Progress Status in ubuntu-meta source package in Zesty: In Progress Bug description: I've submitted an MIR for the numactl binary package at: LP: #1700824. Assuming that is approved, please also include this on the server seed, which I believe is necessary for it to appear on the ubuntu-server ISOs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1700826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700826] Re: please include numactl on the ubuntu-server iso
** Changed in: ubuntu-meta (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-meta (Ubuntu Xenial) Status: New => In Progress ** Changed in: ubuntu-meta (Ubuntu Zesty) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1700826 Title: please include numactl on the ubuntu-server iso Status in ubuntu-meta package in Ubuntu: In Progress Status in ubuntu-meta source package in Xenial: In Progress Status in ubuntu-meta source package in Zesty: In Progress Bug description: I've submitted an MIR for the numactl binary package at: LP: #1700824. Assuming that is approved, please also include this on the server seed, which I believe is necessary for it to appear on the ubuntu-server ISOs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1700826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700826] Re: please include numactl on the ubuntu-server iso
** Branch linked: lp:~dannf/ubuntu-seeds/numactl.zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1700826 Title: please include numactl on the ubuntu-server iso Status in ubuntu-meta package in Ubuntu: In Progress Status in ubuntu-meta source package in Xenial: In Progress Status in ubuntu-meta source package in Zesty: In Progress Bug description: I've submitted an MIR for the numactl binary package at: LP: #1700824. Assuming that is approved, please also include this on the server seed, which I believe is necessary for it to appear on the ubuntu-server ISOs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1700826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
The problem causing apport's slow installation mentioned in https://bugs.launchpad.net/ubuntu/+source/unattended- upgrades/+bug/1690980/comments/37 seems to be LP: #1320403. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Fix Committed Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701850] Re: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
I wait the answer because i need also Wine don't manage the accent caracters solved with the updates? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1701850 Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in dpkg package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Bug description: unable to install some product after ProblemType: Package DistroRelease: Ubuntu 17.04 Package: bsdutils 1:2.29-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-24.28-lowlatency 4.10.15 Uname: Linux 4.10.0-24-lowlatency x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: bsdutils:amd64: Configure python-xmltodict:amd64: Install python-pyquery:amd64: Install wxbanker:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Jun 30 22:47:13 2017 DpkgTerminalLog: dpkg: error processing package bsdutils (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-06-11 (20 days ago) InstallationMedia: Ubuntu-Studio 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1701850/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows
Landing the apt piece of this without the unattended-upgrades piece has regressed the around-the-clock distribution of unattended-upgrades downloads (which is enabled by default for security updates in 16.04). The plan is to follow up with unattended-upgrades SRU today to get this all landed before 16.04.3 so that the point release images are in a coherent state. apt must also declare a versioned Breaks: against versions of unattended-upgrades that don't implement --download-only. Otherwise, the infrastructure consequences of a future apt update published to the security pocket without a matching unattended-upgrades update would be severe. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1686470 Title: Apt updates that are uniformly spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: Fix Released Status in unattended-upgrades source package in Xenial: Triaged Status in apt source package in Yakkety: Won't Fix Status in unattended-upgrades source package in Yakkety: Won't Fix Status in apt source package in Zesty: Fix Committed Status in unattended-upgrades source package in Zesty: Triaged Status in apt source package in Artful: Fix Released Status in unattended-upgrades source package in Artful: Triaged Status in apt package in Debian: Fix Released Status in unattended-upgrades package in Debian: Fix Committed Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they preffer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted
This may not be a bug. Even I faced this error which seems to be related to another error, blueman.bluez.errors.DBusFailedError for which I found the solution here: https://askubuntu.com/questions/801404/bluetooth- connection-failed-blueman-bluez-errors-dbusfailederror-protocol-no. Hope this may help someone. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1490349 Title: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted Status in bluez package in Ubuntu: Invalid Bug description: On 15:10 after the bluetooth service has been stopped and restarted it is not possible to scan or connect to devices: $ sudo systemctl restart bluetooth $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows
** Description changed: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was - scheduled, poweron and observe that apt-get update / download / -unattended upgrade are all performed on boot. + scheduled, poweron and observe that apt-get update / download / + unattended upgrade are all performed on boot. + + * Downgrade systemd to the release version of the package (from +-security). Then run 'sudo systemctl start apt-daily.service'. +Confirm that the systemd package is re-upgraded. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do - everything at 6am..6:30am window" and the xenial+ behavior of "do -everything at random times throughout the day". If there are specific -deployments that rely on the previous types of behaviour they will be -able to adjust manually the systemd timers with the overrides to be -executed exactly as they wish; or match the .0 release behaviour that -they preffer. + everything at 6am..6:30am window" and the xenial+ behavior of "do + everything at random times throughout the day". If there are specific + deployments that rely on the previous types of behaviour they will be + able to adjust manually the systemd timers with the overrides to be + executed exactly as they wish; or match the .0 release behaviour that + they prefer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: Triaged => In Progress ** Changed in: unattended-upgrades (Ubuntu Xenial) Assignee: Dimitri John Ledkov (xnox) => Steve Langasek (vorlon) ** Changed in: unattended-upgrades (Ubuntu Zesty) Status: Triaged => In Progress ** Changed in: unattended-upgrades (Ubuntu Zesty) Assignee: Dimitri John Ledkov (xnox) => Steve Langasek (vorlon) -- 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/1686470 Title: Apt updates that are uniformly spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: Fix Released Status in unattended-upgrades source package in Xenial: In Progress Status in apt source package in Yakkety: Won't Fix Status in unattended-upgrades source package in Yakkety: Won't Fix Status in apt source package in Zesty: Fix Committed Status in unattended-upgrades source package in Zesty: In Progress Status in apt source package in Artful: Fix Released Status in unattended-upgrades source package in Artful: Triaged Status in apt package in
[Touch-packages] [Bug 1707680] Re: RM: obsolete product
Removing packages from artful: ubuntu-push 0.68+17.04.20170211-0ubuntu3 in artful golang-ubuntu-push-dev 0.68+17.04.20170211-0ubuntu3 in artful amd64 golang-ubuntu-push-dev 0.68+17.04.20170211-0ubuntu3 in artful arm64 golang-ubuntu-push-dev 0.68+17.04.20170211-0ubuntu3 in artful armhf golang-ubuntu-push-dev 0.68+17.04.20170211-0ubuntu3 in artful i386 golang-ubuntu-push-dev 0.68+17.04.20170211-0ubuntu3 in artful ppc64el golang-ubuntu-push-dev 0.68+17.04.20170211-0ubuntu3 in artful s390x ubuntu-push-autopilot 0.68+17.04.20170211-0ubuntu3 in artful amd64 ubuntu-push-autopilot 0.68+17.04.20170211-0ubuntu3 in artful armhf ubuntu-push-autopilot 0.68+17.04.20170211-0ubuntu3 in artful i386 ubuntu-push-client 0.68+17.04.20170211-0ubuntu3 in artful amd64 ubuntu-push-client 0.68+17.04.20170211-0ubuntu3 in artful arm64 ubuntu-push-client 0.68+17.04.20170211-0ubuntu3 in artful armhf ubuntu-push-client 0.68+17.04.20170211-0ubuntu3 in artful i386 ubuntu-push-client 0.68+17.04.20170211-0ubuntu3 in artful ppc64el ubuntu-push-client 0.68+17.04.20170211-0ubuntu3 in artful s390x ubuntu-push-dev-server 0.68+17.04.20170211-0ubuntu3 in artful amd64 ubuntu-push-dev-server 0.68+17.04.20170211-0ubuntu3 in artful arm64 ubuntu-push-dev-server 0.68+17.04.20170211-0ubuntu3 in artful armhf ubuntu-push-dev-server 0.68+17.04.20170211-0ubuntu3 in artful i386 ubuntu-push-dev-server 0.68+17.04.20170211-0ubuntu3 in artful ppc64el ubuntu-push-dev-server 0.68+17.04.20170211-0ubuntu3 in artful s390x Comment: part of Ubuntu phone stack, no longer shipping; LP: #1707680 1 package successfully removed. ** Changed in: ubuntu-push (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1707680 Title: RM: obsolete product Status in pay-service package in Ubuntu: Fix Released Status in ubuntu-push package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: pay-service was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:pay-service No reverse dependencies found $ reverse-depends -b src:pay-service No reverse dependencies found -- ubuntu-push was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:ubuntu-push Reverse-Depends === * pay-service (for ubuntu-push-client) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x $ reverse-depends -b src:ubuntu-push No reverse dependencies found -- Unity8 was a component of Ubuntu which is no longer developed. $ reverse-depends src:unity8 Reverse-Depends === * ubuntu-push-autopilot (for unity8-autopilot) Packages without architectures listed are reverse-dependencies in: amd64, armhf, i386 $ reverse-depends -b src:unity8 No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pay-service/+bug/1707680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707680] Re: RM: obsolete product
Removing packages from artful: unity8 8.15+17.04.20170404.7-0ubuntu3 in artful indicators-client 8.15+17.04.20170404.7-0ubuntu3 in artful amd64 indicators-client 8.15+17.04.20170404.7-0ubuntu3 in artful arm64 indicators-client 8.15+17.04.20170404.7-0ubuntu3 in artful armhf indicators-client 8.15+17.04.20170404.7-0ubuntu3 in artful i386 unity-scope-tool 8.15+17.04.20170404.7-0ubuntu3 in artful amd64 unity-scope-tool 8.15+17.04.20170404.7-0ubuntu3 in artful arm64 unity-scope-tool 8.15+17.04.20170404.7-0ubuntu3 in artful armhf unity-scope-tool 8.15+17.04.20170404.7-0ubuntu3 in artful i386 unity8 8.15+17.04.20170404.7-0ubuntu3 in artful amd64 unity8 8.15+17.04.20170404.7-0ubuntu3 in artful arm64 unity8 8.15+17.04.20170404.7-0ubuntu3 in artful armhf unity8 8.15+17.04.20170404.7-0ubuntu3 in artful i386 unity8-autopilot 8.15+17.04.20170404.7-0ubuntu3 in artful amd64 unity8-autopilot 8.15+17.04.20170404.7-0ubuntu3 in artful arm64 unity8-autopilot 8.15+17.04.20170404.7-0ubuntu3 in artful armhf unity8-autopilot 8.15+17.04.20170404.7-0ubuntu3 in artful i386 unity8-autopilot 8.15+17.04.20170404.7-0ubuntu3 in artful ppc64el unity8-autopilot 8.15+17.04.20170404.7-0ubuntu3 in artful s390x unity8-common 8.15+17.04.20170404.7-0ubuntu3 in artful amd64 unity8-common 8.15+17.04.20170404.7-0ubuntu3 in artful arm64 unity8-common 8.15+17.04.20170404.7-0ubuntu3 in artful armhf unity8-common 8.15+17.04.20170404.7-0ubuntu3 in artful i386 unity8-common 8.15+17.04.20170404.7-0ubuntu3 in artful ppc64el unity8-common 8.15+17.04.20170404.7-0ubuntu3 in artful s390x unity8-doc 8.15+17.04.20170404.7-0ubuntu3 in artful amd64 unity8-doc 8.15+17.04.20170404.7-0ubuntu3 in artful arm64 unity8-doc 8.15+17.04.20170404.7-0ubuntu3 in artful armhf unity8-doc 8.15+17.04.20170404.7-0ubuntu3 in artful i386 unity8-doc 8.15+17.04.20170404.7-0ubuntu3 in artful ppc64el unity8-doc 8.15+17.04.20170404.7-0ubuntu3 in artful s390x unity8-greeter 8.15+17.04.20170404.7-0ubuntu3 in artful amd64 unity8-greeter 8.15+17.04.20170404.7-0ubuntu3 in artful arm64 unity8-greeter 8.15+17.04.20170404.7-0ubuntu3 in artful armhf unity8-greeter 8.15+17.04.20170404.7-0ubuntu3 in artful i386 unity8-private 8.15+17.04.20170404.7-0ubuntu3 in artful amd64 unity8-private 8.15+17.04.20170404.7-0ubuntu3 in artful arm64 unity8-private 8.15+17.04.20170404.7-0ubuntu3 in artful armhf unity8-private 8.15+17.04.20170404.7-0ubuntu3 in artful i386 unity8-tests 8.15+17.04.20170404.7-0ubuntu3 in artful amd64 unity8-tests 8.15+17.04.20170404.7-0ubuntu3 in artful arm64 unity8-tests 8.15+17.04.20170404.7-0ubuntu3 in artful armhf unity8-tests 8.15+17.04.20170404.7-0ubuntu3 in artful i386 Comment: unity8 stack no longer shipping; LP: #1707680 1 package successfully removed. ** Changed in: unity8 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1707680 Title: RM: obsolete product Status in pay-service package in Ubuntu: Fix Released Status in ubuntu-push package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: pay-service was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:pay-service No reverse dependencies found $ reverse-depends -b src:pay-service No reverse dependencies found -- ubuntu-push was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:ubuntu-push Reverse-Depends === * pay-service (for ubuntu-push-client) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x $ reverse-depends -b src:ubuntu-push No reverse dependencies found -- Unity8 was a component of Ubuntu which is no longer developed. $ reverse-depends src:unity8 Reverse-Depends === * ubuntu-push-autopilot (for unity8-autopilot) Packages without architectures listed are reverse-dependencies in: amd64, armhf, i386 $ reverse-depends -b src:unity8 No reverse dependencies found To manage notifications about this bug
[Touch-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather
I believe these strings are in libgweather and not gnome-weather. libgweather actually provides two potfiles, these strings should be in the libgweather potfile instead of the locations one. https://git.gnome.org/browse/libgweather/tree/libgweather/gweather-weather.c https://git.gnome.org/browse/libgweather/tree/po/POTFILES.in https://translations.launchpad.net/ubuntu/artful/+source/libgweather/+pots/libgweather >From the publishing history, libgweather has been in main continuously for years. ** Also affects: libgweather (Ubuntu) Importance: Undecided Status: New ** Changed in: libgweather (Ubuntu) Importance: Undecided => High ** Changed in: libgweather (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1704533 Title: French language locale missing : Gnome-Weather Status in Ubuntu Translations: New Status in gnome-weather package in Ubuntu: In Progress Status in libgweather package in Ubuntu: Confirmed Bug description: In Gnome Weather, part of it is not translated in french : cloudy, rain showers, etc. Should be : nuageux, pluie fine, etc. I guess it's a missing french localization. Fedora does not have that problem. In Gnome-Software, they have a section for languages, under the extensions section. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1704533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707742] [NEW] package binutils 2.26.1-1ubuntu1~16.04.3 failed to install/upgrade: le paquet binutils n'est pas prêt pour la configuration configuration impossible (état actuel
Public bug reported: I only know that Ubuntu said that there is a problem durint the installation I'm sorry about that ProblemType: Package DistroRelease: Ubuntu 16.04 Package: binutils 2.26.1-1ubuntu1~16.04.3 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 Date: Mon Jul 31 22:18:26 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 zlib1g 1:1.2.8.dfsg-2ubuntu4.1 ErrorMessage: le paquet binutils n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: binutils Title: package binutils 2.26.1-1ubuntu1~16.04.3 failed to install/upgrade: le paquet binutils n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: binutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1707742 Title: package binutils 2.26.1-1ubuntu1~16.04.3 failed to install/upgrade: le paquet binutils n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») Status in binutils package in Ubuntu: New Bug description: I only know that Ubuntu said that there is a problem durint the installation I'm sorry about that ProblemType: Package DistroRelease: Ubuntu 16.04 Package: binutils 2.26.1-1ubuntu1~16.04.3 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 Date: Mon Jul 31 22:18:26 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 zlib1g 1:1.2.8.dfsg-2ubuntu4.1 ErrorMessage: le paquet binutils n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: binutils Title: package binutils 2.26.1-1ubuntu1~16.04.3 failed to install/upgrade: le paquet binutils n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed ») UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1707742/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
I test this again in the following manner, installed apt and unattended- upgrades from Balint's PPA, then modified /etc/apt/apt.conf.d/20auto- upgrades so that APT:Periodic::Unattended-Upgrade was "1". I then ran "sudo service apt-daily-upgrade start" and ran the u-u-reboot.sh script I've mentioned before. After the reboot I ran 'sudo apt-get update' and 'sudo apt-get upgrade' which returned: E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. This is the problem we are trying to avoid. I'll attach /var/log /unattended-upgrades/unattended-upgrades.log and u-u-dpkg.log. ** Attachment added: "unattended-upgrades.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1690980/+attachment/4924778/+files/unattended-upgrades.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Fix Committed Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
The dpkg log file too. ** Attachment added: "unattended-upgrades-dpkg.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1690980/+attachment/4924779/+files/unattended-upgrades-dpkg.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Fix Committed Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668722] Re: 60x11-common_xdg_path uses $DESKTOP_SESSION which needs a sanity check
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1668722 Title: 60x11-common_xdg_path uses $DESKTOP_SESSION which needs a sanity check Status in xorg package in Ubuntu: Confirmed Bug description: This file: /etc/X11/Xsession.d/60x11-common_xdg_path contains references to $DESKTOP_SESSION variable. On one of my Ubuntu installs this variable contains: "plasma", on the other it contains: "/usr/share/xsessions/plasma". I don't know where either example comes from, but the upshot is that paths are added to XDG_DATA_DIRS and XDG_CONFIG_DIRS that don't exist. MANDATORY_PATH is also affected I believe, maybe others. Surely a sanity check of the generated paths is in order. Seems pointless to add non-existent ones. $XDG_SESSION_DESKTOP looks like a replacement for $DESKTOP_SESSION, but is that true? Cheers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1668722/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Brian: It looks like blocking shutdown did work properly but the upgrade itself took longer than 15 minutes which is the current timeout. (see u-u.log) I already filed a PR against u-u to bump the timeout to 30 mins: https://github.com/mvo5/unattended-upgrades/pull/69 , but in this case apt's timer kicks in (@Julian). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Fix Committed Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707222] Re: usage of /tmp during boot is not safe due to systemd-tmpfiles-clean
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed -- 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/1707222 Title: usage of /tmp during boot is not safe due to systemd-tmpfiles-clean Status in cloud-init: New Status in cloud-init package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Bug description: Earlier this week on Zesty on Azure I saw a cloud-init failure in its 'mount_cb' function. That function esentially does: a.) make a tmp directory for a mount point b.) mount some filesystem to that mount point c.) call a function d.) unmount the directory What I recall was that access to a file inside the mount point failed during 'c'. This seems possible as systemd-tmpfiles-clean may be running at the same time as cloud-init (cloud-init.service in this example). It seems that this service basically inhibits *any* other service from using tmp files. It's ordering statements are only: After=local-fs.target time-sync.target Before=shutdown.target So while in most cases only services that run early in the boot process like cloud-init will be affected, any service could have its tmp files removed. this service could take quite a long time to run if /tmp/ had been filled with lots of files in the previous boot. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1707222/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
For being on the safe side on slow machines I would bump the timeout even higher. I'll also file a PR setting --minimal-upgrade-steps the default which will allow upgrading in transactions by default. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Fix Committed Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full
No. Automatic removing is supposed to work in 16.04 and later by default. But even in 16.04 it works only, if you let unattended-upgrades install all kernel updates. I have not tested later releases, but I guess it is the same thing. I think removing should work in 16.04 and later, if you use the configuration recommended in https://help.ubuntu.com/community/RemoveOldKernels. (i.e. setting Unattended-Upgrade::Remove-Unused-Dependencies "true";) This configuration works by 14.04, too, if you let unattended-upgrades install all kernel updates. -- 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/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full Status in unattended-upgrades: New Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: Currently if one chooses to use LVM or encrypted install, a /boot partition is created of 236Mb Once kernel updates start being released this partition soon fills until people are left unable to upgrade. While you and I might know that we need to watch partition space, many of the people we have installing think that a windows disk is a disk and not a partition, education is probably the key - but in the meantime support venues keep needing to deal with the fact the partition is too small and/or old kernels are not purged as new ones install. For workaround and sytem repair, see https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1357093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows
** Description changed: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. - * Downgrade systemd to the release version of the package (from --security). Then run 'sudo systemctl start apt-daily.service'. -Confirm that the systemd package is re-upgraded. + * Downgrade systemd to the release version of the package (from + -security). Remove apt periodic stamp files rm /var/lib/apt/periodic/*. +Then run 'sudo systemctl start apt-daily.service'. + Confirm that the systemd package is downloaded, but not upgraded. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they prefer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 -- 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/1686470 Title: Apt updates that are uniformly spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: Fix Released Status in unattended-upgrades source package in Xenial: In Progress Status in apt source package in Yakkety: Won't Fix Status in unattended-upgrades source package in Yakkety: Won't Fix Status in apt source package in Zesty: Fix Committed Status in unattended-upgrades source package in Zesty: In Progress Status in apt source package in Artful: Fix Released Status in unattended-upgrades source package in Artful: Triaged Status in apt package in Debian: Fix Released Status in unattended-upgrades package in Debian: Fix Committed Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when
[Touch-packages] [Bug 1140716] Re: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge
** Changed in: dri Status: In Progress => Fix Released -- 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/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge Status in DRI: Fix Released Status in Mesa: Unknown Status in linux package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in linux source package in Precise: Fix Committed Status in linux-lts-quantal source package in Precise: Fix Committed Status in linux-lts-raring source package in Precise: Invalid Status in mesa source package in Precise: Triaged Status in linux source package in Quantal: Invalid Status in linux-lts-quantal source package in Quantal: Invalid Status in linux source package in Raring: Invalid Status in linux-lts-quantal source package in Raring: Invalid Status in linux package in Debian: New Status in linux package in Fedora: Unknown Bug description: I'm getting errors about GPU hangs every minute or so (usually only when using FF and scrolling a webpage or something). I also get an annoying ubuntu dialog saying there is a "system error". This didn't happen with 3.5.0-24-generic. Here is the dmesg: [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.658405] [ cut here ] [26285.658472] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26285.658474] Hardware name: SATELLITE Z830 [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc lp parport e1000e ahci libahci [last unloaded: sdhci] [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic #40-Ubuntu [26285.658539] Call Trace: [26285.658549] [] warn_slowpath_common+0x7f/0xc0 [26285.658553] [] warn_slowpath_null+0x1a/0x20 [26285.658569] [] gen6_enable_rps+0x706/0x710 [i915] [26285.658584] [] intel_modeset_init_hw+0x66/0xa0 [i915] [26285.658595] [] i915_reset+0x1a4/0x6e0 [i915] [26285.658601] [] ? __switch_to+0x12b/0x420 [26285.658612] [] i915_error_work_func+0xc3/0x110 [i915] [26285.658618] [] process_one_work+0x12a/0x420 [26285.658629] [] ? gen6_pm_rps_work+0xe0/0xe0 [i915] [26285.658632] [] worker_thread+0x12e/0x2f0 [26285.658636] [] ? manage_workers.isra.26+0x200/0x200 [26285.658640] [] kthread+0x93/0xa0 [26285.658644] [] kernel_thread_helper+0x4/0x10 [26285.658649] [] ? kthread_freezable_should_stop+0x70/0x70 [26285.658652] [] ? gs_change+0x13/0x13 [26285.658654] ---[ end trace 59c6162fdfcbffee ]--- [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26756.021426] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26766.014093] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26766.014397] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26932.376233] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26932.376544] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26932.384285] [ cut here ] [26932.384354] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26932.384356] Hardware name: SATELLITE Z830 [26932.384358] Modules linked in: sdhci_pci
[Touch-packages] [Bug 1668722] Re: 60x11-common_xdg_path uses $DESKTOP_SESSION which needs a sanity check
DESKTOP_SESSION is created by the display manager. In particular, SDDM puts an absolute path in DESKTOP_SESSION, which seem to be quite distinct from what other managers are doing. I have opened https://github.com/sddm/sddm/issues/852 about that matter. However, the 60x11-common_xdg_path could be made to produce better XDG paths. This scripts was created by Ubuntu (see https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/804734 for the context), so Ubuntu should fix it if need be. Note that nothing says the paths in such variables have to be valid. The users of these variables should be ready for invalid path (simply switch to the next one in the list). ** Bug watch added: github.com/sddm/sddm/issues #852 https://github.com/sddm/sddm/issues/852 -- 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/1668722 Title: 60x11-common_xdg_path uses $DESKTOP_SESSION which needs a sanity check Status in xorg package in Ubuntu: Confirmed Bug description: This file: /etc/X11/Xsession.d/60x11-common_xdg_path contains references to $DESKTOP_SESSION variable. On one of my Ubuntu installs this variable contains: "plasma", on the other it contains: "/usr/share/xsessions/plasma". I don't know where either example comes from, but the upshot is that paths are added to XDG_DATA_DIRS and XDG_CONFIG_DIRS that don't exist. MANDATORY_PATH is also affected I believe, maybe others. Surely a sanity check of the generated paths is in order. Seems pointless to add non-existent ones. $XDG_SESSION_DESKTOP looks like a replacement for $DESKTOP_SESSION, but is that true? Cheers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1668722/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707792] [NEW] systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
*** This bug is a duplicate of bug 1705870 *** https://bugs.launchpad.net/bugs/1705870 Public bug reported: I don't know if this should be considered a bug in systemd or apport. systemd-udevd appears to crash with this bug on each boot. This is a fully updated Xubuntu Artful amd64 system (installed yesterday from the daily-live) with systemd 234-2ubuntu1, udev 234-2ubuntu1, apport 2.20.6-0ubuntu4, and kernel version 4.11.0-12-generic. The system has no swap and runs inside a VMware Workstation 12.5.7 virtual machine (with open-vm-tools) on a Windows host. The host system has not approached memory exhaustion. I suspect these details may be relevant, because the host system sometimes experiences unexplained slowdowns when I/O is high. Note that I only suspect, and do not actually know for sure, that this bug may have been triggered by the host system's I/O problems. I only know about this crash because Apport notified me. Starting the system seems to take longer than it should; specifically, once the non- graphical login prompt is shown, it sometimes takes up to a minute for LightDM to appear. But I don't know if that is related, and beyond that, I have not observed anything going wrong on the system. When I originally installed this Ubuntu (guest) system, Apport did not inform me of a crash. Since then, the host system engaged in more intensive I/O, and also I enabled artful-proposed, and now the crash occurs. I don't know if either of these changes are relevant. This most resembles bug 1705870, which occurred in Artful with some slightly earlier package versions. Depending on the results of the symbolic retrace, I might mark this as a duplicate of that bug. It also resembles bug 1663995, bug 1506798, bug 1433320, and some of its (many) duplicates. That bug (i.e., bug 1433320) was considered to affect apport rather than systemd (see https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1433320/comments/10) and is considered fixed. (To a lesser extent, this bug resembles bug 1437896, which that bug mentions, and which is considered a bug in systemd.) I have made /bin/sh a symlink to bash on this system instead of dash (because I am using this system to test http://www.linuxfromscratch.org/lfs/view/development/chapter02/mounting.html, which expects it). Aside from making startup scripts run a bit slower and increasing memory footprint slightly, I suspect this is irrelevant to this bug, but it's a significant (and *unusual*) change so I figured it is worth mentioning. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-12.17-generic 4.11.12 Uname: Linux 4.11.0-12-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Mon Jul 31 17:41:49 2017 ExecutablePath: /lib/systemd/systemd-udevd InstallationDate: Installed on 2017-07-31 (0 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170731) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcCmdline: /lib/systemd/systemd-udevd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-12-generic root=UUID=3ebdfb0d-efad-4049-955f-56e299d1acea ro quiet splash Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84 ?? () ?? () ?? () __libc_start_main (main=0x1f82c781c0, argc=1, argv=0x7ffddfff7de8, init=, fini=, rtld_fini=, stack_end=0x7ffddfff7dd8) at ../csu/libc-start.c:291 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash artful package-from-proposed ** Attachment added: "the output of dmesg" https://bugs.launchpad.net/bugs/1707792/+attachment/4924803/+files/dmesg.txt ** Information type changed from Private to Public ** Description changed: I don't know if this should be conside
[Touch-packages] [Bug 1705870] Re: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1705870 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() Status in systemd package in Ubuntu: Confirmed Bug description: . ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: udev 233-8ubuntu3 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CrashCounter: 1 CustomUdevRuleFiles: 80-net-setup-link.rules Date: Sat Jul 22 00:19:41 2017 ExecutablePath: /lib/systemd/systemd-udevd InstallationDate: Installed on 2015-03-25 (849 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-udevd ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84 ?? () ?? () ?? () __libc_start_main (main=0x558cc4bc3f20, argc=1, argv=0x7ffe6962b198, init=, fini=, rtld_fini=, stack_end=0x7ffe6962b188) at ../csu/libc-start.c:291 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-yakkety dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-yakkety:cvnQEMU:ct1:cvrpc-i440fx-yakkety: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-yakkety dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1705870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707792] Re: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
*** This bug is a duplicate of bug 1705870 *** https://bugs.launchpad.net/bugs/1705870 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1705870, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1707792/+attachment/4924804/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1707792/+attachment/4924807/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1707792/+attachment/4924813/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1707792/+attachment/4924815/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1707792/+attachment/4924816/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1707792/+attachment/4924817/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1707792/+attachment/4924818/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1705870 systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() ** Tags removed: need-amd64-retrace -- 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/1707792 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() Status in systemd package in Ubuntu: New Bug description: I don't know if this should be considered a bug in systemd or apport. systemd-udevd appears to crash with this bug on each boot. This is a fully updated Xubuntu Artful amd64 system (installed yesterday from the daily-live) with systemd 234-2ubuntu1, udev 234-2ubuntu1, apport 2.20.6-0ubuntu4, and kernel version 4.11.0-12-generic. The system has no swap and runs inside a VMware Workstation 12.5.7 virtual machine (with open-vm-tools) on a Windows host. The host system has not approached memory exhaustion. I suspect these details may be relevant, because the host system sometimes experiences unexplained slowdowns when I/O is high. Note that I only suspect, and do not actually know for sure, that this bug may have been triggered by the host system's I/O problems. I only know about this crash because Apport notified me. Starting the system seems to take longer than it should; specifically, once the non-graphical login prompt is shown, it sometimes takes up to a minute for LightDM to appear. But I don't know if that is related, and beyond that, I have not observed anything going wrong on the system. When I originally installed this Ubuntu (guest) system, Apport did not inform me of a crash. Since then, the host system engaged in more intensive I/O, and also I enabled artful-proposed, and now the crash occurs. I don't know if either of these changes are relevant. This most resembles bug 1705870, which occurred in Artful with some slightly earlier package versions. Depending on the results of the symbolic retrace, I might mark this as a duplicate of that bug. It also resembles bug 1663995, bug 1506798, bug 1433320, and some of its (many) duplicates. That bug (i.e., bug 1433320) was considered to affect apport rather than systemd (see https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1433320/comments/10) and is considered fixed. (To a lesser extent, this bug resembles bug 1437896, which that bug mentions, and which is considered a bug in systemd.) I have made /bin/sh a symlink to bash on this system instead of dash (because I am using this system to test http://www.linuxfromscratch.org/lfs/view/development/chapter02/mounting.html, which expects it). Aside from making startup scripts run a bit slower and increasing memory footprint slightly, I suspect this is irrelevant to this bug, but it's a significant (and *unusual*) change so I figured it is worth mentioning. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-12.17-generic 4.11.12 Uname: Linux 4.11.0-12-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Mon Jul 31 17:41:49 2017 ExecutablePath: /lib/systemd/systemd-udevd InstallationDate: Installed on 2017-07-31 (0 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170731) Lsu
[Touch-packages] [Bug 1707792] Re: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
*** This bug is a duplicate of bug 1705870 *** https://bugs.launchpad.net/bugs/1705870 ** Attachment removed: "the output of dmesg" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1707792/+attachment/4924803/+files/dmesg.txt -- 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/1707792 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() Status in systemd package in Ubuntu: New Bug description: I don't know if this should be considered a bug in systemd or apport. systemd-udevd appears to crash with this bug on each boot. This is a fully updated Xubuntu Artful amd64 system (installed yesterday from the daily-live) with systemd 234-2ubuntu1, udev 234-2ubuntu1, apport 2.20.6-0ubuntu4, and kernel version 4.11.0-12-generic. The system has no swap and runs inside a VMware Workstation 12.5.7 virtual machine (with open-vm-tools) on a Windows host. The host system has not approached memory exhaustion. I suspect these details may be relevant, because the host system sometimes experiences unexplained slowdowns when I/O is high. Note that I only suspect, and do not actually know for sure, that this bug may have been triggered by the host system's I/O problems. I only know about this crash because Apport notified me. Starting the system seems to take longer than it should; specifically, once the non-graphical login prompt is shown, it sometimes takes up to a minute for LightDM to appear. But I don't know if that is related, and beyond that, I have not observed anything going wrong on the system. When I originally installed this Ubuntu (guest) system, Apport did not inform me of a crash. Since then, the host system engaged in more intensive I/O, and also I enabled artful-proposed, and now the crash occurs. I don't know if either of these changes are relevant. This most resembles bug 1705870, which occurred in Artful with some slightly earlier package versions. Depending on the results of the symbolic retrace, I might mark this as a duplicate of that bug. It also resembles bug 1663995, bug 1506798, bug 1433320, and some of its (many) duplicates. That bug (i.e., bug 1433320) was considered to affect apport rather than systemd (see https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1433320/comments/10) and is considered fixed. (To a lesser extent, this bug resembles bug 1437896, which that bug mentions, and which is considered a bug in systemd.) I have made /bin/sh a symlink to bash on this system instead of dash (because I am using this system to test http://www.linuxfromscratch.org/lfs/view/development/chapter02/mounting.html, which expects it). Aside from making startup scripts run a bit slower and increasing memory footprint slightly, I suspect this is irrelevant to this bug, but it's a significant (and *unusual*) change so I figured it is worth mentioning. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-12.17-generic 4.11.12 Uname: Linux 4.11.0-12-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Mon Jul 31 17:41:49 2017 ExecutablePath: /lib/systemd/systemd-udevd InstallationDate: Installed on 2017-07-31 (0 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170731) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcCmdline: /lib/systemd/systemd-udevd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-12-generic root=UUID=3ebdfb0d-efad-4049-955f-56e299d1acea ro quiet splash Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84 ?? () ?? () ?? () __libc_start_main (main=0x1f82c781c0, argc=1, argv=0x7ffddfff7de8, init=, fini=, rtld_fini=, stack_end=0x7ffddfff7dd8) at ../csu/libc-start.c:291 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechn
[Touch-packages] [Bug 1707247] Re: package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1707247 Title: package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in unattended-upgrades package in Ubuntu: New Bug description: just check the error things on my laptop. help asap! ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.6 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Uname: Linux 4.4.0-87-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Fri Jul 28 09:58:42 2017 DuplicateSignature: package:unattended-upgrades:0.90ubuntu0.6 Installing new version of config file /etc/logrotate.d/unattended-upgrades ... frontend: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. dpkg: error processing package unattended-upgrades (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-07-03 (25 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-07-27 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1707247/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707108] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1707108 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned Status in fontconfig package in Ubuntu: New Bug description: bugfix ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Uname: Linux 4.4.0-87-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Fri Jul 28 01:36:00 2017 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-07-25 (2 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2017-07-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1707108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705870] Re: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
I've experienced this bug, also in a virtual machine (though with VMware rather than QEMU). See bug 1707792 for details. These bugs have a lot in common with bug 1433320, though that is considered fixed. -- 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/1705870 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() Status in systemd package in Ubuntu: Confirmed Bug description: . ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: udev 233-8ubuntu3 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CrashCounter: 1 CustomUdevRuleFiles: 80-net-setup-link.rules Date: Sat Jul 22 00:19:41 2017 ExecutablePath: /lib/systemd/systemd-udevd InstallationDate: Installed on 2015-03-25 (849 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150324) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcCmdline: /lib/systemd/systemd-udevd ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic root=UUID=fc32a548-00cf-4d7f-8204-2080bfaf0ebc ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84 ?? () ?? () ?? () __libc_start_main (main=0x558cc4bc3f20, argc=1, argv=0x7ffe6962b198, init=, fini=, rtld_fini=, stack_end=0x7ffe6962b188) at ../csu/libc-start.c:291 Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-yakkety dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-yakkety:cvnQEMU:ct1:cvrpc-i440fx-yakkety: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-yakkety dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1705870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 23976] Re: perl_5.8.7-6(m68k/unstable):
** Changed in: perl (Debian) Status: Won't Fix => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/23976 Title: perl_5.8.7-6(m68k/unstable): Status in perl package in Ubuntu: Invalid Status in perl package in Debian: Fix Released Bug description: Automatically imported from Debian bug report #334030 http://bugs.debian.org/334030 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/23976/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707798] [NEW] RM: obsolete product
Public bug reported: ubuntuone-credentials was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:ubuntuone-credentials No reverse dependencies found $ reverse-depends -b src:ubuntuone-credentials No reverse dependencies found ** Affects: ubuntuone-credentials (Ubuntu) Importance: Undecided Status: Triaged ** Tags: u8rm ** Changed in: ubuntuone-credentials (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntuone-credentials in Ubuntu. https://bugs.launchpad.net/bugs/1707798 Title: RM: obsolete product Status in ubuntuone-credentials package in Ubuntu: Triaged Bug description: ubuntuone-credentials was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:ubuntuone-credentials No reverse dependencies found $ reverse-depends -b src:ubuntuone-credentials No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntuone-credentials/+bug/1707798/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1638695] Re: Python 2.7.12 performance regression
Any updates on this? Are there plans to release a faster python build for Xenial? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1638695 Title: Python 2.7.12 performance regression Status in python2.7 package in Ubuntu: Confirmed Bug description: I work on the OpenStack-Ansible project and we've noticed that testing jobs on 16.04 take quite a bit longer to complete than on 14.04. They complete within an hour on 14.04 but they normally take 90 minutes or more on 16.04. We use the same version of Ansible with both versions of Ubuntu. After more digging, I tested python performance (using the 'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12). There is a significant performance difference between each version of python. That is detailed in a spreadsheet[0]. I began using perf to dig into the differences when running the python performance module and when using Ansible playbooks. CPU migrations (as measured by perf) are doubled in Ubuntu 16.04 when running the same python workloads. I tried changing some of the kerne.sched sysctl configurables but they had very little effect on the results. I compiled python 2.7.12 from source on 14.04 and found the performance to be unchanged there. I'm not entirely sure where the problem might be now. We also have a bug open in OpenStack-Ansible[1] that provides additional detail. Thanks in advance for any help you can provide! [0] https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing [1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707334] Re: Falied to start LBS - AppArmor ("inicialização")
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1707334 Title: Falied to start LBS - AppArmor ("inicialização") Status in xorg package in Ubuntu: New Bug description: Bug no Boot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-88.111-generic 4.4.76 Uname: Linux 4.4.0-88-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Jul 28 22:24:14 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651] InstallationDate: Installed on 2017-07-06 (22 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3542 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-88-generic root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0P8H6J dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/13/2016:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0P8H6J:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3542 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Jul 28 21:00:35 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1110 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1707334/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1695928] Re: Please remove obsolete UOA packages
** Description changed: Ubuntu Online Accounts is no longer maintained. There is an alternative, GNOME Online Accounts for the GNOME desktop. Also, Unity's Online Accounts settings panel does not currently work without oxide-qt but oxide-qt will be removed from Ubuntu 17.10. Please remove these source packages and their binaries: = Phase 1 --- gnome-control-center-signon account-plugins account-plugin-fitbit account-polld - pay-service - qtpurchasing-opensource-src + (pay-service removed) + (qtpurchasing-opensource-src removed) storage-provider-webdav sync-monitor ubuntuone-credentials - ubuntu-push + (ubuntu-push removed) unity-china-photo-scope unity-scope-gdrive By the way, gnome-control-center-signon fails to build with vala 0.36: https://launchpadlibrarian.net/324396241/buildlog_ubuntu-artful-amd64.gnome-control-center-signon_0.1.9+16.10.20160825-0ubuntu1~ubuntu17.10.1_BUILDING.txt.gz Phase 2 --- ubuntu-system-settings-online-accounts online-accounts-api storage-framework keeper mcloud address-book-app address-book-service dialer-app messaging-app telephony-service tone-generator ubuntu-system-settings buteo-sync-plugins-contacts-google camera-app indicator-transfer indicator-transfer-buteo libertine - ubuntu-experience-tests + (ubuntu-experience-tests removed) unity-scopes-shell - unity8 + (unity8 removed) Other Notes --- The Shotwell suggests have been dropped in artful-proposed. Shotwell is temporarily stuck in -proposed because of an autopkgtest issue https://bugzilla.gnome.org/781802 Kubuntu still uses signon-ui. See also https://code.launchpad.net/~xnox/ubuntu- seeds/unity8-removals/+merge/323615 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-control-center- signon in Ubuntu. https://bugs.launchpad.net/bugs/1695928 Title: Please remove obsolete UOA packages Status in gnome-control-center-signon package in Ubuntu: New Bug description: Ubuntu Online Accounts is no longer maintained. There is an alternative, GNOME Online Accounts for the GNOME desktop. Also, Unity's Online Accounts settings panel does not currently work without oxide-qt but oxide-qt will be removed from Ubuntu 17.10. Please remove these source packages and their binaries: = Phase 1 --- gnome-control-center-signon account-plugins account-plugin-fitbit account-polld (pay-service removed) (qtpurchasing-opensource-src removed) storage-provider-webdav sync-monitor ubuntuone-credentials (ubuntu-push removed) unity-china-photo-scope unity-scope-gdrive By the way, gnome-control-center-signon fails to build with vala 0.36: https://launchpadlibrarian.net/324396241/buildlog_ubuntu-artful-amd64.gnome-control-center-signon_0.1.9+16.10.20160825-0ubuntu1~ubuntu17.10.1_BUILDING.txt.gz Phase 2 --- ubuntu-system-settings-online-accounts online-accounts-api storage-framework keeper mcloud address-book-app address-book-service dialer-app messaging-app telephony-service tone-generator ubuntu-system-settings buteo-sync-plugins-contacts-google camera-app indicator-transfer indicator-transfer-buteo libertine (ubuntu-experience-tests removed) unity-scopes-shell (unity8 removed) Other Notes --- The Shotwell suggests have been dropped in artful-proposed. Shotwell is temporarily stuck in -proposed because of an autopkgtest issue https://bugzilla.gnome.org/781802 Kubuntu still uses signon-ui. See also https://code.launchpad.net/~xnox/ubuntu- seeds/unity8-removals/+merge/323615 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1695928/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1707108] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1707108 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned Status in fontconfig package in Ubuntu: New Bug description: bugfix ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73 Uname: Linux 4.4.0-87-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Fri Jul 28 01:36:00 2017 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-07-25 (2 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2017-07-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1707108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp