[Touch-packages] [Bug 998156] Re: GTK Print dialog sends broken custom page size attribute: "PageSize=Custom.Custom.x"
** Changed in: gimp (Ubuntu) Status: Invalid => Confirmed ** Changed in: gimp (Ubuntu) Assignee: (unassigned) => anil (aneelpace) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/998156 Title: GTK Print dialog sends broken custom page size attribute: "PageSize=Custom.Custom.x" Status in GTK+: Fix Released Status in Ubuntu: In Progress Status in firefox package in Ubuntu: Invalid Status in gimp package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Fix Released Status in inkscape package in Ubuntu: Invalid Status in The Precise Pangolin: Triaged Status in firefox source package in Precise: Invalid Status in gimp source package in Precise: Invalid Status in gtk+3.0 source package in Precise: In Progress Status in inkscape source package in Precise: Invalid Status in The Quantal Quetzal: Won't Fix Status in firefox source package in Quantal: Invalid Status in gimp source package in Quantal: Invalid Status in gtk+3.0 source package in Quantal: Fix Released Status in inkscape source package in Quantal: Invalid Status in gtk+2.0 package in Debian: Confirmed Bug description: [Impact] [Fix] [Test Case] [Regression Potential] [Original Report] When trying to print a photo, the printer stops with status "rendering completed". I have to remove all printing jobs and restart CUPS to be able to print again. This error does not occur when printing other documents, i.e. simple text. I use a HP PhotoSmart b109a connected to a Fritz!Box 7390 wireless router ("socket://fritz.box:9100"). This bug is also present in Debian: http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=664031 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/998156/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687353] Re: System freezes due to ALSA error and recovers after significant time
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-lib (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1687353 Title: System freezes due to ALSA error and recovers after significant time Status in alsa-lib package in Ubuntu: Confirmed Bug description: Hello I have a Lenovo Ideapad 310. I was having issues with power management, and was using upstream kernels. I noticed they had frequent freezes, so I decided to use the standard from Ubuntu 16.04 (today, 4.4.0-75). But now it has this freezes too, so something which was bugged on the newer kernel was inserted on 4.4.0-75, as previous version (4.4.0-72) hadn't this issue. What is happening is: the system freezes. The sound that was being played loops endlessly. Everything freezes, Ctrl+Alt+Fnumber don't work. The system completely stops. Normally, I would just power the computer off keeping the power button pressed. But this time I tried to recover it, as the syslog ended always corrupted. I needed to gets the logs at least once. So I started to disconnect hardware parts: battery charger, external USB HDD (it was not being accessed), USB mouse, USB keyboard. When I disconnected the sound jack, I noticed the mouse moved, so it was recoverable. I waited for 100 seconds until the system recovered. When it recovered, looked like nothing had happened, and now I'm writing this report from the computer, without restarting. Steps to reproduce: 1) open Audacious or VLC; 2) play a music/video on Audacious or VLC; 3) open another program with sound (Steam, a browser (I use Opera), etc); 4) use the computer until a freeze happens. Observations: -Audacious + Steam + Starbound is nearly 100% chance of triggering it (SDL?). -VLC + Opera + Firefox (on start page) was enough for trigger it once, even with the only program with media opened being VLC. The freeze I was able to recover had: Opera Developer (YouTube video playing) + Audacious (playing) + Steam with audio streams opened on pavucontrol. Additionally, Thunderbird and Evince were opened, and intel-gpu-overlay was opened inside a Xnest window. The syslog says to report to alsa, so I'm writing the report here. However, it should be noted that there is a i915 error too, maybe it was a consequence, maybe it was the cause. $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 $ uname -a Linux usuario-Lenovo-ideapad-310-14ISK 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Thank you. Edit: one thing I noticed with indicator-multiload, the internal HDD activity completely stopped while this problem was happening and soon after it started to function. It was like the computer was recovering with the internal HDD turned off. The HDD usage ramped up and the system returned to normal. May this be related with the power management issues? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libasound2 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 30 23:43:29 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libasound2-data 1.1.0-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 InstallationDate: Installed on 2016-12-31 (121 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: alsa-lib UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1687353/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686612] Re: Stacked profiles fail to reload in Trusty LXD containters
Note, if we are running the right kernel, there is no reason that we couldn't have a trusty containers load profiles. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1686612 Title: Stacked profiles fail to reload in Trusty LXD containters Status in apparmor package in Ubuntu: Invalid Status in libvirt package in Ubuntu: New Status in lxd package in Ubuntu: Invalid Bug description: Hi, in our testing I found an issue that might now surface due to stacked profiles working. Our setup is a Xenial (or newer) Host with LXD Containers for all supported releases. In that Xenial+ are good but recently the Trusty containers ran into an issue. After installing libvirt profiles are enforced and processes confined just as they should be. 3 processes are in enforce mode. [...] /usr/sbin/libvirtd (5253 All good so far, but once the Trusty container is rebooting it looses that. Libvirt is no more enforced and confined. I happen to find this being related: $ service apparmor restart "Not reloading AppArmor in container" Looking deeper I found that the newer Releases had code that uses is_container_with_internal_policy from /lib/apparmor/functions. That lets Xenial+ load the profiles in LXD correctly. But on Trusty the init script just calls /bin/running-in-container and if true will skip loading. For now I just drop this section in my setup via: sed -ei '/running-in-container/,/^\s*fi/{d}' /etc/init.d/apparmor I don't know what the support state of profiles in (Trusty) containers is, but I think more issues might arise out of this than just my libvirt profile. As I see it everything will fail to be confined after restart. This is not a regression per-se as before stacked was just not working at all. Now that it works this issue surfaces. In my case the eventual symptom was qemu guest failing to migrate between restarted and not restarted containers complaining that on the restarted one the apparmor security label is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1686612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 441247] Re: nvidia MCP79 HDA microphone does not work
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/441247 Title: nvidia MCP79 HDA microphone does not work Status in alsa-driver package in Ubuntu: Expired Bug description: My microphone does not work, recording in audacity or calling in skype. Tried raising the microphone levels in alsamixer, but that didn't help System is Ubuntu 9.10 karmic ProblemType: Bug Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1659 F pulseaudio Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xf098 irq 17' Mixer name : 'Nvidia MCP7A HDMI' Components : 'HDA:10ec0888,10250160,00100202 HDA:10de0007,10de0101,00100100' Controls : 29 Simple ctrls : 15 Date: Sat Oct 3 13:08:21 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: alsa-base 1.0.20+dfsg-1ubuntu4 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-11.38-generic SourcePackage: alsa-driver Uname: Linux 2.6.31-11-generic i686 --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stalker1238 F pulseaudio Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xf098 irq 17' Mixer name : 'Nvidia MCP7A HDMI' Components : 'HDA:10ec0888,10250160,00100202 HDA:10de0007,10de0101,00100100' Controls : 29 Simple ctrls : 15 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318) Package: alsa-base 1.0.22.1+dfsg-0ubuntu3 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Tags: lucid Uname: Linux 2.6.32-17-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/441247/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 566535] Re: Heavy stutter without system load
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/566535 Title: Heavy stutter without system load Status in alsa-driver package in Ubuntu: Expired Bug description: Binary package hint: pulseaudio Description: Ubuntu lucid (development branch) Release: 10.04 AMD64 With turn from karmic to lucid beta the sound is poping and stuttering while playing trough pulseaudio. When this happens i got tons of these lines in messages. Apr 19 12:13:29 agamemnon pulseaudio[5718]: ratelimit.c: 5 events suppressed Apr 19 12:18:05 agamemnon pulseaudio[5718]: ratelimit.c: 1 events suppressed Sometimes pulse goes to sleep_state and the sound stops completely, audio applications grey out in this case. The chip is a rt888 HDA. I tryed to set higher priority at /etc/pulse/daemon.conf but -11 and forbidden realtime scheduling seems to be the reality. I tryed different resample-method without an effect. In karmic pulse runs with -20 and everything was fine. pulseaudio: Installed: 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14 There is 2x 2.8GHz CPU power, 4gig of 1333 mem but load isn't needed to let pulse stutter und popple. Other distros enable pulse-rt to workaround this, ubuntu did not not have this group. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14 ProcVersionSignature: Ubuntu 2.6.32-21.32-genusername 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eric 5718 F pulseaudio /dev/snd/pcmC0D0p: eric 5718 F...m pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,1458e601,0011' Controls : 39 Simple ctrls : 21 CheckboxSubmission: 72ffaca291c05635776d4a13f9e644e4 CheckboxSystem: 32980ee028b29311fef8e195a759b031 Date: Mon Apr 19 12:17:10 2010 ProcEnviron: LANGUAGE=de_DE:de:en_GB:en LANG=de_DE.utf8 SHELL=/bin/bash SourcePackage: pulseaudio dmi.bios.date: 12/09/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-MA770T-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd12/09/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA770T-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA770T-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA770T-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.pulse.daemon.conf: 2010-04-18T16:17:13.703498 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/566535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 682565] Re: Thinkpad Edge 11" (Intel) [Conexant CX20582 (Pebble)] Internal Mic Not Working
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/682565 Title: Thinkpad Edge 11" (Intel) [Conexant CX20582 (Pebble)] Internal Mic Not Working Status in alsa-driver package in Ubuntu: Expired Bug description: I have a thinkpad edge 11" (intel) which uses the Conexant CX20582 (Pebble) sound chip. Currently, the internal microphone will not work. Out of the box, the headphones and external mic also have issues but these get solved following directions in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/587388 Following the solution listed in this bug report and setting my /etc/modprobe.d/alsa-base.conf to options snd-hda-intel model="olpc- xo-1_5" the headphone and external microphone seem to work, but the internal microphone seem not to work. The options in alsa-mixer seem not to match the physical hardware layout. My guess is that the configuration of the pebble chip in the laptop is not supported by the drivers yet. Let me know how else I can help. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: alsa-base 1.0.23+dfsg-1ubuntu4 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Compiled on Nov 18 2010 for kernel 2.6.35-22-generic (SMP). Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ahnise 2703 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf070 irq 48' Mixer name : 'Intel IbexPeak HDMI' Components : 'HDA:14f15066,17aa21c8,00100302 HDA:80862804,80860101,0010' Controls : 18 Simple ctrls : 9 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 86HT19WW-1.165000' Mixer name : 'ThinkPad EC 86HT19WW-1.165000' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Mon Nov 29 14:33:19 2010 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all ProcEnviron: LANG=en_PH.utf8 SHELL=/bin/bash SelectedCard: 0 Intel HDA-Intel - HDA Intel SourcePackage: alsa-driver Symptom: audio Title: [Conexant CX20582 (Pebble)] Recording problem dmi.bios.date: 08/10/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 86ET19WW (1.03 ) dmi.board.name: 03282NB dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr86ET19WW(1.03):bd08/10/2010:svnLENOVO:pn03282NB:pvrThinkPadEdge:rvnLENOVO:rn03282NB:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 03282NB dmi.product.version: ThinkPad Edge dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/682565/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 817661] Re: [0769ERG, Realtek ALC861-VD, Speaker, Internal] No sound at all
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/817661 Title: [0769ERG, Realtek ALC861-VD, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Expired Bug description: there is no sound coming from my speakers. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: alsa-base 1.0.24+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC861-VD Analog [ALC861-VD Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ahsan 1452 F pulseaudio /dev/snd/pcmC0D0p: ahsan 1452 F...m pulseaudio /dev/snd/controlC1: ahsan 1452 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfc30 irq 47' Mixer name : 'Realtek ALC861-VD' Components : 'HDA:10ec0862,17aa3867,0011 HDA:11c11040,11c10001,00100200' Controls : 19 Simple ctrls : 12 Card1.Amixer.info: Card hw:1 'CAMERA'/'ARKMICRO USB2.0 PC CAMERA at usb-:00:1d.7-3, high speed' Mixer name : 'USB Mixer' Components : 'USB18ec:3299' Controls : 2 Simple ctrls : 1 CurrentDmesg: [ 18.956485] tg3 :06:00.0: eth0: Link is up at 100 Mbps, full duplex [ 18.956490] tg3 :06:00.0: eth0: Flow control is off for TX and off for RX [ 18.956680] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 21.337900] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0 [ 29.088022] eth0: no IPv6 routers present Date: Thu Jul 28 18:22:36 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Internal Audio - HDA Intel Symptom_DevicesInUse: 1452 1452 1452 ahsan F...m pulseaudio /dev/snd/controlC1: ahsan F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [0769ERG, Realtek ALC861-VD, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to natty on 2011-07-28 (0 days ago) dmi.bios.date: 06/11/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 68ET37WW dmi.board.name: IEL10 dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr68ET37WW:bd06/11/2008:svnLENOVO:pn0769ERG:pvr3000N200:rvnLENOVO:rnIEL10:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 0769ERG dmi.product.version: 3000 N200 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/817661/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687843] Re: humanity-icon-theme is not ready for configuration cannot configure (current status 'half-installed')
** Summary changed: - package humanity-icon-theme 0.6.10 [modified: usr/share/icons/Humanity/actions/32/object-inverse.svg usr/share/icons/Humanity/animations/16/process-working.png usr/share/icons/Humanity/animations/22/process-working.png usr/share/icons/Humanity/animations/24/process-working.png usr/share/icons/Humanity/animations/32/process-working.png usr/share/icons/Humanity/categories/32/applications-development.svg usr/share/icons/Humanity/emblems/16/emblem-OK.png usr/share/icons/Humanity/emblems/16/emblem-cool.png usr/share/icons/Humanity/emblems/16/emblem-ohno.png usr/share/icons/Humanity/emblems/22/emblem-OK.png usr/share/icons/Humanity/emblems/22/emblem-cool.png usr/share/icons/Humanity/emblems/22/emblem-ohno.png usr/share/icons/Humanity/emblems/24/emblem-OK.png usr/share/icons/Humanity/emblems/24/emblem-cool.png usr/share/icons/Humanity/emblems/24/emblem-ohno.png usr/share/icons/Humanity/emblems/32/emblem-OK.png usr/share/icons/Humanity/emblems/32/emblem-cool.png usr/share/icons/Humanity/em blems/32/emblem-ohno.png usr/share/icons/Humanity/index.theme usr/share/icons/Humanity/mimes/16/libreoffice-oasis-drawing-template.png usr/share/icons/Humanity/mimes/16/libreoffice-oasis-master-document.png usr/share/icons/Humanity/mimes/16/libreoffice-oasis-presentation-template.png usr/share/icons/Humanity/mimes/16/libreoffice-oasis-spreadsheet-template.png usr/share/icons/Humanity/mimes/16/libreoffice-oasis-web-template.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis-drawing-template.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis-formula.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis-presentation-template.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis-spreadsheet-template.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis-text-template.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis-web-template.png usr/share/icons/Humanity/mimes/48/libreoffice-oasis-drawing-template.png usr/share/icons/Humanity/mimes/48/libreoffice-oasis-presentati on-template.png usr/share/icons/Humanity/mimes/48/libreoffice-oasis-spreadsheet-template.png usr/share/icons/Humanity/mimes/48/libreoffice-oasis-text-template.png usr/share/icons/Humanity/status/16/audio-volume-high.png usr/share/icons/Humanity/status/16/audio-volume-medium.png usr/share/icons/Humanity/status/22/audio-volume-high.png usr/share/icons/Humanity/status/22/audio-volume-low.png usr/share/icons/Humanity/status/22/audio-volume-medium.png usr/share/icons/Humanity/status/22/audio-volume-muted.png usr/share/icons/Humanity/status/22/gsm-3g-low-secure.svg usr/share/icons/Humanity/status/22/gsm-3g-low.svg usr/share/icons/Humanity/status/22/gsm-3g-medium-secure.svg usr/share/icons/Humanity/status/22/gsm-3g-medium.svg usr/share/icons/Humanity/status/22/gsm-3g-none-secure.svg usr/share/icons/Humanity/status/22/gsm-3g-none.svg usr/share/icons/Humanity/status/24/audio-volume-high.png usr/share/icons/Humanity/status/24/audio-volume-low.png usr/share/icons/Humanity/status/24/audio-volum e-medium.png usr/share/icons/Humanity/status/24/audio-volume-muted.png usr/share/icons/Humanity/status/24/gsm-3g-high-secure.svg usr/share/icons/Humanity/status/24/gsm-3g-high.svg usr/share/icons/Humanity/status/24/gsm-3g-low-secure.svg usr/share/icons/Humanity/status/24/gsm-3g-medium-secure.svg usr/share/icons/Humanity/status/48/weather-showers.svg] failed to install/upgrade: package humanity-icon-theme is not ready for configuration cannot configure (current status 'half-installed') + humanity-icon-theme is not ready for configuration cannot configure (current status 'half-installed') -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1687843 Title: humanity-icon-theme is not ready for configuration cannot configure (current status 'half-installed') Status in humanity-icon-theme package in Ubuntu: New Bug description: Error on trying to update "Software Updater". However, the software updater did get updated successfully. ProblemType: Package DistroRelease: Ubuntu 16.04 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue May 2 22:34:56 2017 ErrorMessage: package humanity-icon-theme is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-04-04 (28 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: humanity-icon-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1687843/+subscriptio
[Touch-packages] [Bug 1686612] Re: Stacked profiles fail to reload in Trusty LXD containters
LXD mounts /sys/kernel/security as upstart and systemd won't let the system boot if that's not mounted (and they can't mount it themselves). LXD also doesn't differentiate Ubuntu 14.04 from Ubuntu 16.04, or any other distro or release. Instead we provide the exact same environment to every container, just like a VM would. The users can define extra things on top of that, but the source image that's used has no impact on that. If something is directly loading profiles, bypassing apparmor's own check, then it's either a problem in that software in the first place or a problem with the apparmor tools which should match the init behavior and refuse to operate in unsupported environments. ** Changed in: lxd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1686612 Title: Stacked profiles fail to reload in Trusty LXD containters Status in apparmor package in Ubuntu: Invalid Status in libvirt package in Ubuntu: New Status in lxd package in Ubuntu: Invalid Bug description: Hi, in our testing I found an issue that might now surface due to stacked profiles working. Our setup is a Xenial (or newer) Host with LXD Containers for all supported releases. In that Xenial+ are good but recently the Trusty containers ran into an issue. After installing libvirt profiles are enforced and processes confined just as they should be. 3 processes are in enforce mode. [...] /usr/sbin/libvirtd (5253 All good so far, but once the Trusty container is rebooting it looses that. Libvirt is no more enforced and confined. I happen to find this being related: $ service apparmor restart "Not reloading AppArmor in container" Looking deeper I found that the newer Releases had code that uses is_container_with_internal_policy from /lib/apparmor/functions. That lets Xenial+ load the profiles in LXD correctly. But on Trusty the init script just calls /bin/running-in-container and if true will skip loading. For now I just drop this section in my setup via: sed -ei '/running-in-container/,/^\s*fi/{d}' /etc/init.d/apparmor I don't know what the support state of profiles in (Trusty) containers is, but I think more issues might arise out of this than just my libvirt profile. As I see it everything will fail to be confined after restart. This is not a regression per-se as before stacked was just not working at all. Now that it works this issue surfaces. In my case the eventual symptom was qemu guest failing to migrate between restarted and not restarted containers complaining that on the restarted one the apparmor security label is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1686612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687482] Re: -4 flag doesn't work
I've figured out that it is caused by this line in /etc/ssh/ssh_config ProxyCommand /usr/bin/sss_ssh_knownhostsproxy -p %p %h This was put there by the freeipa installer (ipa-client-install), so I guess this is a freeipa or sssd bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1687482 Title: -4 flag doesn't work Status in openssh package in Ubuntu: Incomplete Bug description: Whenever I use the -4 flag on ssh, it still uses the ipv6 address from dns instead of forcing ipv4 like it says it is supposed to do in the man page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1687482/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687482] Re: -4 flag doesn't work
Although it could still be a bug in ssh if ssh doesn't do ProxyCommand correctly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1687482 Title: -4 flag doesn't work Status in openssh package in Ubuntu: Incomplete Bug description: Whenever I use the -4 flag on ssh, it still uses the ipv6 address from dns instead of forcing ipv4 like it says it is supposed to do in the man page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1687482/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1640868] Re: network-interface-security upstart job is not container aware
** Description changed: The network-interface-security upstart job unconditionally loads the usr.sbin.dhclient AppArmor profile even if the job is running in a LXC/LXD container that cannot load AppArmor policy. I don't see any negative side effects from this behavior, so I don't think this is a high priority bug. If this were to be fixed, the upstart job would need to check to see if it is running inside of a container and, if so, if the container is capable of loading its own AppArmor security policy. See https://launchpad.net/ubuntu/+source/apparmor/2.10.95-4ubuntu5 for an example of what this would look like. This behavior can be seen with a 16.04 host, running lxd from either the archive or as a snap, and launching a 14.04 container. aa-status inside of the container will show: $ lxd.lxc exec t aa-status apparmor module is loaded. 3 profiles are loaded. 3 profiles are in enforce mode. -/sbin/dhclient -/usr/lib/NetworkManager/nm-dhcp-client.action -/usr/lib/connman/scripts/dhclient-script + /sbin/dhclient + /usr/lib/NetworkManager/nm-dhcp-client.action + /usr/lib/connman/scripts/dhclient-script 0 profiles are in complain mode. 1 processes have profiles defined. 1 processes are in enforce mode. -/sbin/dhclient (810) + /sbin/dhclient (810) 0 processes are in complain mode. 0 processes are unconfined but have a profile defined. - - IMPORTANT: It is likely that upstart in 14.04 will receive a future SRU - which will result in AppArmor policy to be loaded during the boot - process when inside of a LXD container. That will make this bug more - difficult to verify. Once that change lands, you'll likely have to - modify /lib/init/aa-profile-load, inside of the container, to not load - policy at boot in order to definitively see this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1640868 Title: network-interface-security upstart job is not container aware Status in ifupdown package in Ubuntu: Triaged Bug description: The network-interface-security upstart job unconditionally loads the usr.sbin.dhclient AppArmor profile even if the job is running in a LXC/LXD container that cannot load AppArmor policy. I don't see any negative side effects from this behavior, so I don't think this is a high priority bug. If this were to be fixed, the upstart job would need to check to see if it is running inside of a container and, if so, if the container is capable of loading its own AppArmor security policy. See https://launchpad.net/ubuntu/+source/apparmor/2.10.95-4ubuntu5 for an example of what this would look like. This behavior can be seen with a 16.04 host, running lxd from either the archive or as a snap, and launching a 14.04 container. aa-status inside of the container will show: $ lxd.lxc exec t aa-status apparmor module is loaded. 3 profiles are loaded. 3 profiles are in enforce mode. /sbin/dhclient /usr/lib/NetworkManager/nm-dhcp-client.action /usr/lib/connman/scripts/dhclient-script 0 profiles are in complain mode. 1 processes have profiles defined. 1 processes are in enforce mode. /sbin/dhclient (810) 0 processes are in complain mode. 0 processes are unconfined but have a profile defined. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1640868/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686612] Re: Stacked profiles fail to reload in Trusty LXD containters
Hi Christian - thanks for the clearly written bug report. AppArmor profiles should not be loaded inside of Trusty containers. As you mentioned, we are simply calling running-in-container from the apparmor init script and not loading profiles if true. The bug is either in libvirt-bin's postinst (it should call running-in- container and skip the profile load after installation if true) or, arguably, in LXD for mounting apparmorfs inside of the container in the first place. AppArmorfs probably shouldn't be writable (or even mounted?) inside of a 14.04 container. I am leaning towards LXD being the proper place to fix this bug as more than just libvirt's AppArmor profiles are being incorrectly loaded. Bug #1640868 is another example. ** Also affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Also affects: lxd (Ubuntu) Importance: Undecided Status: New ** Changed in: apparmor (Ubuntu) Status: New => Invalid ** Changed in: apparmor (Ubuntu) Assignee: Tyler Hicks (tyhicks) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1686612 Title: Stacked profiles fail to reload in Trusty LXD containters Status in apparmor package in Ubuntu: Invalid Status in libvirt package in Ubuntu: New Status in lxd package in Ubuntu: New Bug description: Hi, in our testing I found an issue that might now surface due to stacked profiles working. Our setup is a Xenial (or newer) Host with LXD Containers for all supported releases. In that Xenial+ are good but recently the Trusty containers ran into an issue. After installing libvirt profiles are enforced and processes confined just as they should be. 3 processes are in enforce mode. [...] /usr/sbin/libvirtd (5253 All good so far, but once the Trusty container is rebooting it looses that. Libvirt is no more enforced and confined. I happen to find this being related: $ service apparmor restart "Not reloading AppArmor in container" Looking deeper I found that the newer Releases had code that uses is_container_with_internal_policy from /lib/apparmor/functions. That lets Xenial+ load the profiles in LXD correctly. But on Trusty the init script just calls /bin/running-in-container and if true will skip loading. For now I just drop this section in my setup via: sed -ei '/running-in-container/,/^\s*fi/{d}' /etc/init.d/apparmor I don't know what the support state of profiles in (Trusty) containers is, but I think more issues might arise out of this than just my libvirt profile. As I see it everything will fail to be confined after restart. This is not a regression per-se as before stacked was just not working at all. Now that it works this issue surfaces. In my case the eventual symptom was qemu guest failing to migrate between restarted and not restarted containers complaining that on the restarted one the apparmor security label is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1686612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1682499] Re: disable dnssec
This particular issue is now closed. Please open a new bug report requesting a cherrypick. We really should not use one bug report for all the past and future defects :-) We need a new bug number for SRU tracking purposes. Regards, Dimitri. On 2 May 2017 5:01 pm, "allfox_wy" <1682...@bugs.launchpad.net> wrote: Greetings, everyone. I'm on Ubuntu GNOME 17.04 I see that DNSSEC is now off by default, however, in my log, I would see something like: 4 May 2 23:29:31 lavender systemd-resolved[1129]: Grace period over, resuming full feature set (UDP+EDNS0+DO+LARGE) for DNS server 10.2.5.7. 5 May 2 23:29:31 lavender systemd-resolved[1129]: Using degraded feature set (UDP) for DNS server 10.2.5.7. And during that, it seems the systemd-resolved would act just like DNSSEC enabled, and Web would fail some time like before. I don't quite get what is going on. I have dnsmasq run in my network to provide DNS cache, it's the 10.2.5.7 . My upstream server do not support DNSSEC, so the validation would fail certainly. What I observed is during this feature set test, dnsmasq cache would receive TCP connection from Ubuntu GNOME 17.04 . And take some time, the test fail. I know this feature test would fail, as I know the upstream server do not support DNSSEC. I don't know what is EDNS0 or LARGE. But the problem here is that even DNSSEC is now off by default, this feature set test would still do the "DO" test, which stands for DNSSEC OK. It would surely fail, and it can not be turned off via configuration, and it would cut the Web for some time. There is a patch for this: https://github.com/systemd/systemd/issues/5352 Is it possible to cherry pick it please ? ** Bug watch added: github.com/systemd/systemd/issues #5352 https://github.com/systemd/systemd/issues/5352 -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1682499 Title: disable dnssec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/ 1682499/+subscriptions -- 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/1682499 Title: disable dnssec Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Zesty: Fix Released Bug description: [Impact] * dnssec functionality in systemd-resolved prevents network access in certain intra and extra net cases, due to failure to correctly validate dnssec entries. As a work-around we should disable dnssec by default. [Test Case] * Validate systemd-resolved is compiled with --with-default-dnssec=no * Validate that systemd-resolve --status says that DNSSEC setting is no $ systemd-resolve --status good output: ... DNSSEC setting: no DNSSEC supported: no ... bad output: ... DNSSEC setting: allow-downgrade DNSSEC supported: yes ... [Regression Potential] * People who expect DNSSEC to be available by default will need to re-enable it by modifying systemd-resolve configuration file [Other Info] * See duplicate bugs and other bug reports in systemd for scenarios of DNS resolution failures when DNSSEC is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1682499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686612] Re: Stacked profiles fail to reload in Trusty LXD containters
** Description changed: Hi, in our testing I found an issue that might now surface due to stacked profiles working. Our setup is a Xenial (or newer) Host with LXD Containers for all supported releases. In that Xenial+ are good but recently the Trusty containers ran into an issue. After installing libvirt profiles are enforced and processes confined just as they should be. 3 processes are in enforce mode. [...] -/usr/sbin/libvirtd (5253 + /usr/sbin/libvirtd (5253 All good so far, but once the Trusty container is rebooting it looses that. Libvirt is no more enforced and confined. I happen to find this being related: $ service apparmor restart - "Not reloading AppArmor in container" + "Not reloading AppArmor in container" Looking deeper I found that the newer Releases had code that uses is_container_with_internal_policy from /lib/apparmor/functions. That lets Xenial+ load the profiles in LXD correctly. - But on Xenial the init script just calls /bin/running-in-container and if true will skip loading. + But on Trusty the init script just calls /bin/running-in-container and if true will skip loading. For now I just drop this section in my setup via: - sed -ei '/running-in-container/,/^\s*fi/{d}' /etc/init.d/apparmor + sed -ei '/running-in-container/,/^\s*fi/{d}' /etc/init.d/apparmor I don't know what the support state of profiles in (Trusty) containers is, but I think more issues might arise out of this than just my libvirt profile. As I see it everything will fail to be confined after restart. This is not a regression per-se as before stacked was just not working at all. Now that it works this issue surfaces. In my case the eventual symptom was qemu guest failing to migrate between restarted and not restarted containers complaining that on the restarted one the apparmor security label is missing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1686612 Title: Stacked profiles fail to reload in Trusty LXD containters Status in apparmor package in Ubuntu: New Bug description: Hi, in our testing I found an issue that might now surface due to stacked profiles working. Our setup is a Xenial (or newer) Host with LXD Containers for all supported releases. In that Xenial+ are good but recently the Trusty containers ran into an issue. After installing libvirt profiles are enforced and processes confined just as they should be. 3 processes are in enforce mode. [...] /usr/sbin/libvirtd (5253 All good so far, but once the Trusty container is rebooting it looses that. Libvirt is no more enforced and confined. I happen to find this being related: $ service apparmor restart "Not reloading AppArmor in container" Looking deeper I found that the newer Releases had code that uses is_container_with_internal_policy from /lib/apparmor/functions. That lets Xenial+ load the profiles in LXD correctly. But on Trusty the init script just calls /bin/running-in-container and if true will skip loading. For now I just drop this section in my setup via: sed -ei '/running-in-container/,/^\s*fi/{d}' /etc/init.d/apparmor I don't know what the support state of profiles in (Trusty) containers is, but I think more issues might arise out of this than just my libvirt profile. As I see it everything will fail to be confined after restart. This is not a regression per-se as before stacked was just not working at all. Now that it works this issue surfaces. In my case the eventual symptom was qemu guest failing to migrate between restarted and not restarted containers complaining that on the restarted one the apparmor security label is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1686612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687843] Re: package humanity-icon-theme 0.6.10 [modified: usr/share/icons/Humanity/actions/32/object-inverse.svg usr/share/icons/Humanity/animations/16/process-working.png usr/s
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1687843 Title: package humanity-icon-theme 0.6.10 [modified: usr/share/icons/Humanity/actions/32/object-inverse.svg usr/share/icons/Humanity/animations/16/process-working.png usr/share/icons/Humanity/animations/22/process-working.png usr/share/icons/Humanity/animations/24/process-working.png usr/share/icons/Humanity/animations/32/process-working.png usr/share/icons/Humanity/categories/32/applications-development.svg usr/share/icons/Humanity/emblems/16/emblem-OK.png usr/share/icons/Humanity/emblems/16/emblem-cool.png usr/share/icons/Humanity/emblems/16/emblem-ohno.png usr/share/icons/Humanity/emblems/22/emblem-OK.png usr/share/icons/Humanity/emblems/22/emblem-cool.png usr/share/icons/Humanity/emblems/22/emblem-ohno.png usr/share/icons/Humanity/emblems/24/emblem-OK.png usr/share/icons/Humanity/emblems/24/emblem-cool.png usr/share/icons/Humanity/emblems/24/emblem-ohno.png usr/share/icons/Humanity/emblems/32/emblem-OK.png usr/share/icons/Humanity/emblems/32/emblem-cool.png usr/share/icons/Humanity/emblems/32/emblem-ohno.png usr/share/icons/Humanity/index.theme usr/share/icons/Humanity/mimes/16 /libreoffice-oasis-drawing-template.png usr/share/icons/Humanity/mimes/16/libreoffice-oasis-master- document.png usr/share/icons/Humanity/mimes/16/libreoffice-oasis- presentation-template.png usr/share/icons/Humanity/mimes/16 /libreoffice-oasis-spreadsheet-template.png usr/share/icons/Humanity/mimes/16/libreoffice-oasis-web-template.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis-drawing- template.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis- formula.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis- presentation-template.png usr/share/icons/Humanity/mimes/32 /libreoffice-oasis-spreadsheet-template.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis-text-template.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis-web-template.png usr/share/icons/Humanity/mimes/48/libreoffice-oasis-drawing- template.png usr/share/icons/Humanity/mimes/48/libreoffice-oasis- presentation-template.png usr/share/icons/Humanity/mimes/48 /libreoffice-oasis-spreadsheet-template.png usr/share/icons/Humanity/mimes/48/libreoffice-oasis-text-template.png usr/share/icons/Humanity/status/16/audio-volume-high.png usr/share/icons/Humanity/status/16/audio-volume-medium.png usr/share/icons/Humanity/status/22/audio-volume-high.png usr/share/icons/Humanity/status/22/audio-volume-low.png usr/share/icons/Humanity/status/22/audio-volume-medium.png usr/share/icons/Humanity/status/22/audio-volume-muted.png usr/share/icons/Humanity/status/22/gsm-3g-low-secure.svg usr/share/icons/Humanity/status/22/gsm-3g-low.svg usr/share/icons/Humanity/status/22/gsm-3g-medium-secure.svg usr/share/icons/Humanity/status/22/gsm-3g-medium.svg usr/share/icons/Humanity/status/22/gsm-3g-none-secure.svg usr/share/icons/Humanity/status/22/gsm-3g-none.svg usr/share/icons/Humanity/status/24/audio-volume-high.png usr/share/icons/Humanity/status/24/audio-volume-low.png usr/share/icons/Humanity/status/24/audio-volume-medium.png usr/share/icons/Humanity/status/24/audio-volume-muted.png usr/share/icons/Humanity/status/24/gsm-3g-high-secure.svg usr/share/icons/Humanity/status/24/gsm-3g-high.svg usr/share/icons/Humanity/status/24/gsm-3g-low-secure.svg usr/share/icons/Humanity/status/24/gsm-3g-medium-secure.svg usr/share/icons/Humanity/status/48/weather-showers.svg] failed to install/upgrade: package humanity-icon-theme is not ready for configuration cannot configure (current status 'half-installed') Status in humanity-icon-theme package in Ubuntu: New Bug description: Error on trying to update "Software Updater". However, the software updater did get updated successfully. ProblemType: Package DistroRelease: Ubuntu 16.04 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue May 2 22:34:56 2017 ErrorMessage: package humanity-icon-theme is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-04-04 (28 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: humanity-icon-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1687843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : ht
[Touch-packages] [Bug 1687843] [NEW] package humanity-icon-theme 0.6.10 [modified: usr/share/icons/Humanity/actions/32/object-inverse.svg usr/share/icons/Humanity/animations/16/process-working.png usr
Public bug reported: Error on trying to update "Software Updater". However, the software updater did get updated successfully. ProblemType: Package DistroRelease: Ubuntu 16.04 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue May 2 22:34:56 2017 ErrorMessage: package humanity-icon-theme is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-04-04 (28 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: humanity-icon-theme UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: humanity-icon-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1687843 Title: package humanity-icon-theme 0.6.10 [modified: usr/share/icons/Humanity/actions/32/object-inverse.svg usr/share/icons/Humanity/animations/16/process-working.png usr/share/icons/Humanity/animations/22/process-working.png usr/share/icons/Humanity/animations/24/process-working.png usr/share/icons/Humanity/animations/32/process-working.png usr/share/icons/Humanity/categories/32/applications-development.svg usr/share/icons/Humanity/emblems/16/emblem-OK.png usr/share/icons/Humanity/emblems/16/emblem-cool.png usr/share/icons/Humanity/emblems/16/emblem-ohno.png usr/share/icons/Humanity/emblems/22/emblem-OK.png usr/share/icons/Humanity/emblems/22/emblem-cool.png usr/share/icons/Humanity/emblems/22/emblem-ohno.png usr/share/icons/Humanity/emblems/24/emblem-OK.png usr/share/icons/Humanity/emblems/24/emblem-cool.png usr/share/icons/Humanity/emblems/24/emblem-ohno.png usr/share/icons/Humanity/emblems/32/emblem-OK.png usr/share/icons/Humanity/emblems/32/emblem-cool.png usr/share/icons/Humanity/emblems/32/emblem-ohno.png usr/share/icons/Humanity/index.theme usr/share/icons/Humanity/mimes/16 /libreoffice-oasis-drawing-template.png usr/share/icons/Humanity/mimes/16/libreoffice-oasis-master- document.png usr/share/icons/Humanity/mimes/16/libreoffice-oasis- presentation-template.png usr/share/icons/Humanity/mimes/16 /libreoffice-oasis-spreadsheet-template.png usr/share/icons/Humanity/mimes/16/libreoffice-oasis-web-template.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis-drawing- template.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis- formula.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis- presentation-template.png usr/share/icons/Humanity/mimes/32 /libreoffice-oasis-spreadsheet-template.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis-text-template.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis-web-template.png usr/share/icons/Humanity/mimes/48/libreoffice-oasis-drawing- template.png usr/share/icons/Humanity/mimes/48/libreoffice-oasis- presentation-template.png usr/share/icons/Humanity/mimes/48 /libreoffice-oasis-spreadsheet-template.png usr/share/icons/Humanity/mimes/48/libreoffice-oasis-text-template.png usr/share/icons/Humanity/status/16/audio-volume-high.png usr/share/icons/Humanity/status/16/audio-volume-medium.png usr/share/icons/Humanity/status/22/audio-volume-high.png usr/share/icons/Humanity/status/22/audio-volume-low.png usr/share/icons/Humanity/status/22/audio-volume-medium.png usr/share/icons/Humanity/status/22/audio-volume-muted.png usr/share/icons/Humanity/status/22/gsm-3g-low-secure.svg usr/share/icons/Humanity/status/22/gsm-3g-low.svg usr/share/icons/Humanity/status/22/gsm-3g-medium-secure.svg usr/share/icons/Humanity/status/22/gsm-3g-medium.svg usr/share/icons/Humanity/status/22/gsm-3g-none-secure.svg usr/share/icons/Humanity/status/22/gsm-3g-none.svg usr/share/icons/Humanity/status/24/audio-volume-high.png usr/share/icons/Humanity/status/24/audio-volume-low.png usr/share/icons/Humanity/status/24/audio-volume-medium.png usr/share/icons/Humanity/status/24/audio-volume-muted.png usr/share/icons/Humanity/status/24/gsm-3g-high-secure.svg usr/share/icons/Humanity/status/24/gsm-3g-high.svg usr/share/icons/Humanity/status/24/gsm-3g-low-secure.svg usr/share/icons/Humanity/status/24/gsm-3g-medium-secure.svg usr/share/icons/Humanity/status/48/weather-showers.svg] failed to install/upgrade: package humanity-icon-theme is not ready for configuration cannot configure (current status 'half-installed') Status in humanity-icon-theme package in Ubuntu: New Bug description: Error on trying to update "Software Updater". However, the software updater did get updated successfully. ProblemType: Package DistroRelease: Ubuntu 16.0
[Touch-packages] [Bug 1162475] Re: [hostnamed] Changing hostname doesn't update /etc/hosts
** Tags added: zesty -- 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/1162475 Title: [hostnamed] Changing hostname doesn't update /etc/hosts Status in gnome-control-center package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Status in unity-control-center package in Ubuntu: Confirmed Status in gnome-control-center package in Debian: Fix Released Bug description: GUI --- 1a. Run sudo gnome-control-center, or... 1b. Save the gnome-control-center.pkla from https://bazaar.launchpad.net/~ubuntu-desktop/gnome-control-center/ubuntu/revision/556 to /var/lib/polkit-1/localauthority/10-vendor.d/ and then run gnome-control-center as an admin user 2. Enter the Details panel 3. The "Device name" (hostname) text field should be editable; change the text to something else. 4. The hostname is updated instantly which can be verified by looking in /etc/hostname. However /etc/hosts/ is not updated. Command line hostnamectl set-hostname The hostnamed documentation at http://www.freedesktop.org/wiki/Software/systemd/hostnamed says "To properly handle name lookups with changing local hostnames without having to edit /etc/hosts for them we recommend using hostnamed in combination with nss-myhostname: http://0pointer.de/lennart/projects/nss-myhostname/ " Without /etc/hosts being handled correctly, the hostnamed integration is only half-working. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu18 ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4 Uname: Linux 3.8.0-15-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Sun Mar 31 08:52:57 2013 MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup26.0-0ubuntu1 gnome-control-center-signon 0.1.5-0ubuntu1 gnome-control-center-unity 1.2daily13.02.15-0ubuntu1 indicator-datetime 12.10.3daily13.03.26-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1162475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1687482] Re: -4 flag doesn't work
I'd suggest using "ssh -v" rather than relying on the "Last login:" output. For instance: $ ssh -v -Snone riva : 2>&1 | grep 'Connecting to' debug1: Connecting to riva.pelham.vpn.ucam.org [2001:8b0:bff2:eb14:6a05:caff:fe12:71bf] port 22. $ ssh -4v -Snone riva : 2>&1 | grep 'Connecting to' debug1: Connecting to riva.pelham.vpn.ucam.org [172.20.153.17] port 22. The client in this case is on xenial, so I know that "ssh -4" is not fundamentally broken on xenial. You might also like to check that there's nothing relevant in your ~/.ssh/config that might be overriding the normal logic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1687482 Title: -4 flag doesn't work Status in openssh package in Ubuntu: Incomplete Bug description: Whenever I use the -4 flag on ssh, it still uses the ipv6 address from dns instead of forcing ipv4 like it says it is supposed to do in the man page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1687482/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1645631] Re: Sending files fails because obex not loaded
Thanks for reporting, I was just struck by this bug on 17.04. For a fix which lasts across reboots, run as normal user: systemctl --user enable obex This permanently enables OBEX service for your user sessions. -- 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/1645631 Title: Sending files fails because obex not loaded Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: If I run bluetooth-sendto from command line and try to send the file, it quits after selecting the target device with following command line output: "Acquiring proxy failed: Error calling StartServiceByName for org.bluez.obex: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.obex.service not found." After I run "systemctl --user start obex", it proceeds to send the file. Even then it for some reason gets stuck, but I do not know what causes it and it is probably a different problem. This system is upgraded from xenial. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-bluetooth 3.20.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Nov 29 11:04:11 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-12 (77 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=fi TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to yakkety on 2016-11-01 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1645631/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687666] Re: apt-cache doesn't read keys from trusted.gpg.d when rootdir is used
This was an instance of one of the files being a keybox format, rather than a public key packet. ** Changed in: apt (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1687666 Title: apt-cache doesn't read keys from trusted.gpg.d when rootdir is used Status in apt package in Ubuntu: Invalid Bug description: Or so it would seem. Will try to attach a reproducer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1687666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687742] Re: package linux-image-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1687742 Title: package linux-image-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Resolved as possible by the instruction from ubuntu-bugs.narkive.com from Steve Beattie: sudo dpkg -P casper-memdisk sudo apt-get install -f # here 4.4.0 kernel was generated multiple times sudo update-grub This is the third time I'm trying to upgrade inbox 14.04 to 16.04 on my Dell Inspiron and only one I've successfully rebooted. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-77-generic 4.4.0-77.98 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ignat 2290 F pulseaudio /dev/snd/controlC0: ignat 2290 F pulseaudio Date: Tue May 2 22:49:58 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=feaee4ca-16e7-434e-8539-8a1cdadfab79 InstallationDate: Installed on 2017-04-21 (11 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Inspiron 3558 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=fabdcb72-bbec-4f90-ade9-9821baba8e4b ro quiet splash radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to xenial on 2017-05-02 (0 days ago) dmi.bios.date: 05/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0G1TDD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/31/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0G1TDD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1687742/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687742] [NEW] package linux-image-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: Resolved as possible by the instruction from ubuntu-bugs.narkive.com from Steve Beattie: sudo dpkg -P casper-memdisk sudo apt-get install -f # here 4.4.0 kernel was generated multiple times sudo update-grub This is the third time I'm trying to upgrade inbox 14.04 to 16.04 on my Dell Inspiron and only one I've successfully rebooted. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-77-generic 4.4.0-77.98 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ignat 2290 F pulseaudio /dev/snd/controlC0: ignat 2290 F pulseaudio Date: Tue May 2 22:49:58 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=feaee4ca-16e7-434e-8539-8a1cdadfab79 InstallationDate: Installed on 2017-04-21 (11 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Inspiron 3558 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=fabdcb72-bbec-4f90-ade9-9821baba8e4b ro quiet splash radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to xenial on 2017-05-02 (0 days ago) dmi.bios.date: 05/31/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0G1TDD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/31/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0G1TDD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. ** Affects: initramfs-tools (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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1687742 Title: package linux-image-4.4.0-77-generic 4.4.0-77.98 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Resolved as possible by the instruction from ubuntu-bugs.narkive.com from Steve Beattie: sudo dpkg -P casper-memdisk sudo apt-get install -f # here 4.4.0 kernel was generated multiple times sudo update-grub This is the third time I'm trying to upgrade inbox 14.04 to 16.04 on my Dell Inspiron and only one I've successfully rebooted. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-77-generic 4.4.0-77.98 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ignat 2290 F pulseaudio /dev/snd/controlC0: ignat 2290 F pulseaudio Date: Tue May 2 22:49:58 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=feaee4ca-16e7-434e-8539-8a1cdadfab79 InstallationDate: Installed on 2017-04-21 (11 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Inspiron 3558 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=fabdcb72-bbec-4f90-ade9-9821baba8e4b ro quiet splash radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title:
[Touch-packages] [Bug 1687666] Re: apt-cache doesn't read keys from trusted.gpg.d when rootdir is used
"apt-cache" (the commandline binary packaged in apt) never reads keys because it has no business with keys… from the "reproducer" I guess you are trying to report a problem with the python bindings? You have also omitted any other useful information like which version you are using… If you want it to stay as an apt bug perhaps try to reproduce it with "apt-get update -o Rootdir=/path/". The mentioning of "trusty" in the tarball indicates a rather old version. We had a bunch of these strange characters/spaces in path issues in recent times; perhaps some/all weren't backported to trusty – I don't follow Julians effort on that front all too closely. btw: Rootdir is usually not the option you want. Dir tends to have the same effect for "less" surprises – depends a bit on what you actually do through. -- 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/1687666 Title: apt-cache doesn't read keys from trusted.gpg.d when rootdir is used Status in apt package in Ubuntu: New Bug description: Or so it would seem. Will try to attach a reproducer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1687666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627950] Re: Stopped (with error) ... messages on encrypted LVM shutdown
As a consequence File System Check runs on every boot. It could result in corrupted (encrypted) file system. -- 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/1627950 Title: Stopped (with error) ... messages on encrypted LVM shutdown Status in systemd package in Ubuntu: Confirmed Bug description: Install (Default + crypted LVM) in Ubuntu Server s390x in Yakkety Daily Everything seems to work only on shutdown there is a bunch of "fail" messages related to the disks from systemd: [ OK ] Stopped Network Time Synchronization. [ 33.971312] systemd[1]: Stopped (with error) /dev/disk/by-id/dm-name-vda2_crypt. [FAILED] Stopped (with error) /dev/disk/by-id/dm-name-vda2_crypt. [ 33.971469] systemd[1]: Stopped (with error) /dev/disk/by-id/dm-uuid-CRYPT-LUKS1-ef8aced3ceb640fe80c2c700c4504ccb-vda2_crypt. [FAILED] Stopped (with error) /dev/disk/by-i...40fe80c2c700c4504ccb-vda2_crypt. [ 33.971595] systemd[1]: Stopped (with error) /dev/disk/by-id/lvm-pv-uuid-9hfIOG-dPqq-MpWQ-DzEr-njkh-t2LD-XT3kxq. [FAILED] Stopped (with error) /dev/disk/by-i...dPqq-MpWQ-DzEr-njkh-t2LD-XT3kxq. [FAILED] Stopped (with error) /dev/mapper/vda2_crypt. [FAILED] Stopped (with error) /dev/dm-0. [FAILED] Stopped (with error) /sys/devices/virtual/block/dm-0. [ OK ] Stopped Create Volatile Files and Directories. [ OK ] Stopped Raise network interfaces. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1627950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1684298] Re: Security issues (solved in Debian) - affecting icu52 in trusty
Thank you, Janitor ! :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1684298 Title: Security issues (solved in Debian) - affecting icu52 in trusty Status in icu package in Ubuntu: Fix Released Bug description: Date Reported: 19 Apr 2017 Security database references: In the Debian bugtracking system: 860314. In Mitre's CVE dictionary: CVE-2017-7867, CVE-2017-7868. More information: It was discovered that icu, the International Components for Unicode library, did not correctly validate its input. An attacker could use this problem to trigger an out-of-bound write through a heap-based buffer overflow, thus causing a denial of service via application crash, or potential execution of arbitrary code. For the stable distribution (jessie), these problems have been fixed in version 52.1-8+deb8u5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1684298/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627950] Re: Stopped (with error) ... messages on encrypted LVM shutdown
I tried replacing device uuid with /dev/sdx in /etc/crypttab as "asgard2 (kamp000x)" suggested, but the problem persists. I'm using plain LUKS. -- 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/1627950 Title: Stopped (with error) ... messages on encrypted LVM shutdown Status in systemd package in Ubuntu: Confirmed Bug description: Install (Default + crypted LVM) in Ubuntu Server s390x in Yakkety Daily Everything seems to work only on shutdown there is a bunch of "fail" messages related to the disks from systemd: [ OK ] Stopped Network Time Synchronization. [ 33.971312] systemd[1]: Stopped (with error) /dev/disk/by-id/dm-name-vda2_crypt. [FAILED] Stopped (with error) /dev/disk/by-id/dm-name-vda2_crypt. [ 33.971469] systemd[1]: Stopped (with error) /dev/disk/by-id/dm-uuid-CRYPT-LUKS1-ef8aced3ceb640fe80c2c700c4504ccb-vda2_crypt. [FAILED] Stopped (with error) /dev/disk/by-i...40fe80c2c700c4504ccb-vda2_crypt. [ 33.971595] systemd[1]: Stopped (with error) /dev/disk/by-id/lvm-pv-uuid-9hfIOG-dPqq-MpWQ-DzEr-njkh-t2LD-XT3kxq. [FAILED] Stopped (with error) /dev/disk/by-i...dPqq-MpWQ-DzEr-njkh-t2LD-XT3kxq. [FAILED] Stopped (with error) /dev/mapper/vda2_crypt. [FAILED] Stopped (with error) /dev/dm-0. [FAILED] Stopped (with error) /sys/devices/virtual/block/dm-0. [ OK ] Stopped Create Volatile Files and Directories. [ OK ] Stopped Raise network interfaces. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1627950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627950] Re: Stopped (with error) ... messages on encrypted LVM shutdown
I have the same problem with zesty and some other users too: - https://github.com/systemd/systemd/issues/1620#issuecomment-296487263 - https://github.com/systemd/systemd/issues/1620#issuecomment-297115150 Apparently they fixed this in systemd v233 (https://github.com/systemd/systemd/issues/5527#issuecomment-284186141). ** Bug watch added: github.com/systemd/systemd/issues #5527 https://github.com/systemd/systemd/issues/5527 -- 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/1627950 Title: Stopped (with error) ... messages on encrypted LVM shutdown Status in systemd package in Ubuntu: Confirmed Bug description: Install (Default + crypted LVM) in Ubuntu Server s390x in Yakkety Daily Everything seems to work only on shutdown there is a bunch of "fail" messages related to the disks from systemd: [ OK ] Stopped Network Time Synchronization. [ 33.971312] systemd[1]: Stopped (with error) /dev/disk/by-id/dm-name-vda2_crypt. [FAILED] Stopped (with error) /dev/disk/by-id/dm-name-vda2_crypt. [ 33.971469] systemd[1]: Stopped (with error) /dev/disk/by-id/dm-uuid-CRYPT-LUKS1-ef8aced3ceb640fe80c2c700c4504ccb-vda2_crypt. [FAILED] Stopped (with error) /dev/disk/by-i...40fe80c2c700c4504ccb-vda2_crypt. [ 33.971595] systemd[1]: Stopped (with error) /dev/disk/by-id/lvm-pv-uuid-9hfIOG-dPqq-MpWQ-DzEr-njkh-t2LD-XT3kxq. [FAILED] Stopped (with error) /dev/disk/by-i...dPqq-MpWQ-DzEr-njkh-t2LD-XT3kxq. [FAILED] Stopped (with error) /dev/mapper/vda2_crypt. [FAILED] Stopped (with error) /dev/dm-0. [FAILED] Stopped (with error) /sys/devices/virtual/block/dm-0. [ OK ] Stopped Create Volatile Files and Directories. [ OK ] Stopped Raise network interfaces. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1627950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687722] [NEW] lightdm should not have a pulseaudio config
Public bug reported: If the directory /var/lib/lightdm/.config/pulse exists, then whenever the screen goes blank, the sound volume changes, mutes, or takes on some other random parameters specified by this file. It does not reset on unlocking the screen. This is an extraordinarily dumb behaviour which can be temporarily remedied by deleting that directory, or swapping out lightdm for xscreensaver. Please make sure that lightdm cannot write a pulse config file, or that consolekit or whatever for pulseaudio does not use system users as sources for parameters, and so forth. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Tue May 2 11:23:46 2017 InstallationDate: Installed on 2016-10-09 (204 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1687722 Title: lightdm should not have a pulseaudio config Status in lightdm package in Ubuntu: New Bug description: If the directory /var/lib/lightdm/.config/pulse exists, then whenever the screen goes blank, the sound volume changes, mutes, or takes on some other random parameters specified by this file. It does not reset on unlocking the screen. This is an extraordinarily dumb behaviour which can be temporarily remedied by deleting that directory, or swapping out lightdm for xscreensaver. Please make sure that lightdm cannot write a pulse config file, or that consolekit or whatever for pulseaudio does not use system users as sources for parameters, and so forth. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Tue May 2 11:23:46 2017 InstallationDate: Installed on 2016-10-09 (204 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1687722/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1684298] Re: Security issues (solved in Debian) - affecting icu52 in trusty
This bug was fixed in the package icu - 52.1-3ubuntu0.6 --- icu (52.1-3ubuntu0.6) trusty-security; urgency=medium * SECURITY UPDATE: out-of-bounds write in common/utext.cpp (LP: #1684298) - debian/patches/CVE-2017-786x.patch: properly handle chunk size in source/common/utext.cpp, added test to source/test/intltest/utxttest.cpp, source/test/intltest/utxttest.h. - CVE-2017-7867 - CVE-2017-7868 -- Marc Deslauriers Tue, 02 May 2017 09:43:38 -0400 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1684298 Title: Security issues (solved in Debian) - affecting icu52 in trusty Status in icu package in Ubuntu: Fix Released Bug description: Date Reported: 19 Apr 2017 Security database references: In the Debian bugtracking system: 860314. In Mitre's CVE dictionary: CVE-2017-7867, CVE-2017-7868. More information: It was discovered that icu, the International Components for Unicode library, did not correctly validate its input. An attacker could use this problem to trigger an out-of-bound write through a heap-based buffer overflow, thus causing a denial of service via application crash, or potential execution of arbitrary code. For the stable distribution (jessie), these problems have been fixed in version 52.1-8+deb8u5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1684298/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1684298] Re: Security issues (solved in Debian) - affecting icu52 in trusty
This bug was fixed in the package icu - 57.1-5ubuntu0.1 --- icu (57.1-5ubuntu0.1) zesty-security; urgency=medium * SECURITY UPDATE: out-of-bounds write in common/utext.cpp (LP: #1684298) - debian/patches/CVE-2017-786x.patch: properly handle chunk size in source/common/utext.cpp, added test to source/test/intltest/utxttest.cpp, source/test/intltest/utxttest.h. - CVE-2017-7867 - CVE-2017-7868 -- Marc Deslauriers Tue, 02 May 2017 08:14:14 -0400 ** Changed in: icu (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1684298 Title: Security issues (solved in Debian) - affecting icu52 in trusty Status in icu package in Ubuntu: Fix Released Bug description: Date Reported: 19 Apr 2017 Security database references: In the Debian bugtracking system: 860314. In Mitre's CVE dictionary: CVE-2017-7867, CVE-2017-7868. More information: It was discovered that icu, the International Components for Unicode library, did not correctly validate its input. An attacker could use this problem to trigger an out-of-bound write through a heap-based buffer overflow, thus causing a denial of service via application crash, or potential execution of arbitrary code. For the stable distribution (jessie), these problems have been fixed in version 52.1-8+deb8u5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1684298/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1684298] Re: Security issues (solved in Debian) - affecting icu52 in trusty
This bug was fixed in the package icu - 57.1-4ubuntu0.2 --- icu (57.1-4ubuntu0.2) yakkety-security; urgency=medium * SECURITY UPDATE: out-of-bounds write in common/utext.cpp (LP: #1684298) - debian/patches/CVE-2017-786x.patch: properly handle chunk size in source/common/utext.cpp, added test to source/test/intltest/utxttest.cpp, source/test/intltest/utxttest.h. - CVE-2017-7867 - CVE-2017-7868 -- Marc Deslauriers Tue, 02 May 2017 08:32:50 -0400 ** Changed in: icu (Ubuntu) Status: New => Fix Released ** Changed in: icu (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1684298 Title: Security issues (solved in Debian) - affecting icu52 in trusty Status in icu package in Ubuntu: Fix Released Bug description: Date Reported: 19 Apr 2017 Security database references: In the Debian bugtracking system: 860314. In Mitre's CVE dictionary: CVE-2017-7867, CVE-2017-7868. More information: It was discovered that icu, the International Components for Unicode library, did not correctly validate its input. An attacker could use this problem to trigger an out-of-bound write through a heap-based buffer overflow, thus causing a denial of service via application crash, or potential execution of arbitrary code. For the stable distribution (jessie), these problems have been fixed in version 52.1-8+deb8u5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1684298/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1651623] Re: adt tests fail on zesty for apport
** Changed in: apport (Ubuntu) Status: New => Fix Committed ** Branch linked: lp:~xnox/apport/no-to-keybox ** Changed in: apport (Ubuntu) Assignee: Dimitri John Ledkov (xnox) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1651623 Title: adt tests fail on zesty for apport Status in apport package in Ubuntu: Fix Committed Status in apport source package in Yakkety: New Status in apport source package in Zesty: New Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/amd64/a/apport/20161214_232615_2ff4a@/log.gz fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1651623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode
** Changed in: juju Milestone: 2.2-beta3 => None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1665160 Title: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode Status in juju: Incomplete Status in juju 2.1 series: Won't Fix Status in dbus package in Ubuntu: New Bug description: As seen at http://reports.vapour.ws/releases/issue/5768c750749a563f2d7daa6e A unit test is exclusively failing on our new zesty machine. the previous issues is not related to the zesty falures machine-0: has workers [agent api-address-updater api-caller api-config-watcher disk-manager log-forwarder log-sender logging-config-updater machine-action-runner machiner migration-fortress migration-inactive-flag migration-minion proxy-config-updater reboot-executor ssh-authkeys-updater state-config-watcher storage-provisioner termination-signal-handler unconverted-api-workers upgrade-check-flag upgrade-check-gate upgrade-steps-flag upgrade-steps-gate upgrader] machine-0: waiting for [unit-agent-deployer] machine-0: unexpected [] machine-0: report: {} machine_test.go:1272: WaitMatch(c, matcher.Check, coretesting.LongWait, s.BackingState.StartSync) engine_test.go:234: c.Fatalf("timed out waiting for workers") ... Error: timed out waiting for workers To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1665160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687129] Re: Needs to allow updates from the ESM archive
** Also affects: unattended-upgrades (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: unattended-upgrades (Ubuntu Precise) Status: New => Triaged ** Changed in: unattended-upgrades (Ubuntu Precise) Importance: Undecided => High -- 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/1687129 Title: Needs to allow updates from the ESM archive Status in unattended-upgrades package in Ubuntu: New Status in unattended-upgrades source package in Precise: Triaged Bug description: When the dust has settled on the ESM archive Release file format[1], unattended-upgrades needs to be tweaked to match. [1] https://github.com/CanonicalLtd/archive-auth-mirror/issues/43 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1687129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1678187] Re: dpkg fails to remove a linux-image-extra package, if /boot is about full
** Description changed: "dpkg --purge" calls /etc/kernel/postinst.d/initramfs-tools when purging/removing a linux-image-extra package. That calls "update- initramfs -c" which needs significant amount of additional disk space in /boot temporarily. But there is no space left, if /boot is full. The fix could be to create the new initrg.img file in different partition before replacing the old one by it in update-initramfs. So the - update-initramfs script should be fixed. + update-initramfs script should be fixed. But there may not be such a + partition.. - Alternatively some should remove the respective /boot/initrd.img- file before removing the linux-image-extra package. That could also be done by - sudo update-initramfs -d -k + Alternatively the init script should remove the respective /boot/initrd.img- file when removing/installing the linux-image-extra package. That could also be done by + update-initramfs -d -k Related question: http://askubuntu.com/q/898499/21005 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.7 ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49 Uname: Linux 4.4.0-71-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 31 17:42:35 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (922 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1678187 Title: dpkg fails to remove a linux-image-extra package, if /boot is about full Status in initramfs-tools: New Status in dpkg package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: New Bug description: "dpkg --purge" calls /etc/kernel/postinst.d/initramfs-tools when purging/removing a linux-image-extra package. That calls "update- initramfs -c" which needs significant amount of additional disk space in /boot temporarily. But there is no space left, if /boot is full. The fix could be to create the new initrg.img file in different partition before replacing the old one by it in update-initramfs. So the update-initramfs script should be fixed. But there may not be such a partition.. Alternatively the init script should remove the respective /boot/initrd.img- file when removing/installing the linux-image-extra package. That could also be done by update-initramfs -d -k Related question: http://askubuntu.com/q/898499/21005 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.7 ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49 Uname: Linux 4.4.0-71-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 31 17:42:35 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (922 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/1678187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687710] [NEW] [Inspiron 5559, Realtek ALC3234, Speaker, Internal] No sound at all
Public bug reported: i get no sound, neither from internal speakers nor headphone, i have tried using the command aplay -l and a list of sound cards were shown, but still i dont get any sound ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:9.0-2ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-51.54-generic 4.8.17 Uname: Linux 4.8.0-51-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D3p: nimesh 2162 F...m pulseaudio /dev/snd/controlC0: nimesh 2162 F pulseaudio CurrentDesktop: Unity Date: Tue May 2 22:48:32 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 InstallationDate: Installed on 2016-09-19 (225 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nimesh 2162 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Inspiron 5559, Realtek ALC3234, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0924RG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd06/08/2016:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn0924RG:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1687710 Title: [Inspiron 5559, Realtek ALC3234, Speaker, Internal] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: i get no sound, neither from internal speakers nor headphone, i have tried using the command aplay -l and a list of sound cards were shown, but still i dont get any sound ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:9.0-2ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-51.54-generic 4.8.17 Uname: Linux 4.8.0-51-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D3p: nimesh 2162 F...m pulseaudio /dev/snd/controlC0: nimesh 2162 F pulseaudio CurrentDesktop: Unity Date: Tue May 2 22:48:32 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 InstallationDate: Installed on 2016-09-19 (225 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nimesh 2162 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Inspiron 5559, Realtek ALC3234, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0924RG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd06/08/2016:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn0924RG:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1687710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687015] Re: 229_4ubuntu17 removes group write permissions from /var/log
** Tags added: xenial ** Changed in: systemd (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1687015 Title: 229_4ubuntu17 removes group write permissions from /var/log Status in systemd package in Ubuntu: New Bug description: Steps to reproduce (time senstive, once lxd image is updated with 4ubuntu17, I expect this won't work) lxc launch ubuntu:x test lxc exec test -- ls -ld /var/log # shows 775 perms lxc exec test -- apt update lxc exec test -- apt-cache policy systemd lxc exec test -- apt install systemd lxc exec test -- ls -ld /var/log # shows 755 permissions straceing the apt install shows no chmod calls to /var/log (only /var/log/apt.log, as you'd expect) This means syslog cannot write new files in /var/log, and had broken some production logging for us as a result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1687015/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687666] Re: apt-cache doesn't read keys from trusted.gpg.d when rootdir is used
I think spaces are irrelevant here. It would seem as if trusted.gpg.d was not read at all by apt-cache. ** Summary changed: - apt-cache doesn't read keys from an apt root that has spaces in it + apt-cache doesn't read keys from trusted.gpg.d when rootdir is used -- 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/1687666 Title: apt-cache doesn't read keys from trusted.gpg.d when rootdir is used Status in apt package in Ubuntu: New Bug description: Or so it would seem. Will try to attach a reproducer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1687666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682154] Re: loginctl ignoring user given sessions IDs at command-line
This is not yet fixed in artful yet. -- 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/1682154 Title: loginctl ignoring user given sessions IDs at command-line Status in systemd: New Status in systemd package in Ubuntu: Triaged Status in systemd source package in Zesty: Triaged Bug description: Kubuntu zesty, 232-21ubuntu2 See upstream bug https://github.com/systemd/systemd/issues/5733 with patch attached. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1682154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687666] Re: apt-cache doesn't read keys from an apt root that has spaces in it
Oh not again, aargh! -- 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/1687666 Title: apt-cache doesn't read keys from trusted.gpg.d when rootdir is used Status in apt package in Ubuntu: New Bug description: Or so it would seem. Will try to attach a reproducer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1687666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687666] Re: apt-cache doesn't read keys from an apt root that has spaces in it
Attached shell script, and a sample directory. Python bindings are used and initialize apt.Cache for the rootdir="/tmp/tmppdiktnx2/cache/Foonux 1.2/apt" which fails to update, even though all the keys are present in trusted.gpg.d for all the repositories. -- 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/1687666 Title: apt-cache doesn't read keys from trusted.gpg.d when rootdir is used Status in apt package in Ubuntu: New Bug description: Or so it would seem. Will try to attach a reproducer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1687666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682154] Re: loginctl ignoring user given sessions IDs at command-line
The patch has been accepted upstream: https://github.com/systemd/systemd/commit/b0d08b056e73007695f2f001213da73d19802e23 -- 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/1682154 Title: loginctl ignoring user given sessions IDs at command-line Status in systemd: New Status in systemd package in Ubuntu: Triaged Status in systemd source package in Zesty: Triaged Bug description: Kubuntu zesty, 232-21ubuntu2 See upstream bug https://github.com/systemd/systemd/issues/5733 with patch attached. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1682154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687666] Re: apt-cache doesn't read keys from an apt root that has spaces in it
** Attachment added: "reproduce" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1687666/+attachment/4870925/+files/reproduce -- 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/1687666 Title: apt-cache doesn't read keys from trusted.gpg.d when rootdir is used Status in apt package in Ubuntu: New Bug description: Or so it would seem. Will try to attach a reproducer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1687666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687666] Re: apt-cache doesn't read keys from an apt root that has spaces in it
** Attachment added: "bug.tar.gz" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1687666/+attachment/4870903/+files/bug.tar.gz -- 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/1687666 Title: apt-cache doesn't read keys from an apt root that has spaces in it Status in apt package in Ubuntu: New Bug description: Or so it would seem. Will try to attach a reproducer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1687666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687666] [NEW] apt-cache doesn't read keys from an apt root that has spaces in it
Public bug reported: Or so it would seem. Will try to attach a reproducer. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- 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/1687666 Title: apt-cache doesn't read keys from an apt root that has spaces in it Status in apt package in Ubuntu: New Bug description: Or so it would seem. Will try to attach a reproducer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1687666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687015] Re: 229_4ubuntu17 removes group write permissions from /var/log
The explicit /bin/systemd-tmpfiles is invoked in the postinst script for systemd. Interestingly, it's identical to systemd 229_4ubuntu16 postinst script, so it was not introduced in 4ubuntu17. I suspect this issue has been present for a while, but the daily run of systemd-tmpfiles-clean job restores it. If so, this is probably a debhelper bug? As it, it should respect the machine's tmpfiles.d config rather than exclude it? -- 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/1687015 Title: 229_4ubuntu17 removes group write permissions from /var/log Status in systemd package in Ubuntu: Incomplete Bug description: Steps to reproduce (time senstive, once lxd image is updated with 4ubuntu17, I expect this won't work) lxc launch ubuntu:x test lxc exec test -- ls -ld /var/log # shows 775 perms lxc exec test -- apt update lxc exec test -- apt-cache policy systemd lxc exec test -- apt install systemd lxc exec test -- ls -ld /var/log # shows 755 permissions straceing the apt install shows no chmod calls to /var/log (only /var/log/apt.log, as you'd expect) This means syslog cannot write new files in /var/log, and had broken some production logging for us as a result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1687015/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687647] Re: udev version 232-21ubuntu3 from ports is broken on Zesty s390x
Note that the udev package seems to be looking for /sys/class/net/eth* On my z/KVM instance, eth* do not exist, rather the dev is enc*: ubuntu@s1lp9g003:~$ ls /sys/class/net/ enc4 lo Likewise, on z/VM, the device is also enc*: ubuntu@hwe0008:~$ ls /sys/class/net enc600 lo Interestingly however, on z/VM, this did not fail. ubuntu@hwe0008:~$ sudo apt-cache policy udev udev: Installed: 232-21ubuntu2 Candidate: 232-21ubuntu3 Version table: 232-21ubuntu3 500 500 http://us.ports.ubuntu.com/ubuntu-ports zesty-updates/main s390x Packages *** 232-21ubuntu2 500 500 http://us.ports.ubuntu.com/ubuntu-ports zesty/main s390x Packages 100 /var/lib/dpkg/status ubuntu@hwe0008:~$ sudo apt-get install udev Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libudev1 The following packages will be upgraded: libudev1 udev 2 upgraded, 0 newly installed, 0 to remove and 49 not upgraded. Need to get 1058 kB of archives. After this operation, 3072 B of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://us.ports.ubuntu.com/ubuntu-ports zesty-updates/main s390x udev s390x 232-21ubuntu3 [1005 kB] Get:2 http://us.ports.ubuntu.com/ubuntu-ports zesty-updates/main s390x libudev1 s390x 232-21ubuntu3 [52.9 kB] Fetched 1058 kB in 0s (22.0 MB/s) (Reading database ... 82787 files and directories currently installed.) Preparing to unpack .../udev_232-21ubuntu3_s390x.deb ... Unpacking udev (232-21ubuntu3) over (232-21ubuntu2) ... Preparing to unpack .../libudev1_232-21ubuntu3_s390x.deb ... Unpacking libudev1:s390x (232-21ubuntu3) over (232-21ubuntu2) ... Setting up libudev1:s390x (232-21ubuntu3) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for libc-bin (2.24-9ubuntu2) ... Setting up udev (232-21ubuntu3) ... addgroup: The group `input' already exists as a system group. Exiting. update-initramfs: deferring update (trigger activated) Processing triggers for systemd (232-21ubuntu2) ... Processing triggers for man-db (2.7.6.1-2) ... Processing triggers for initramfs-tools (0.125ubuntu9) ... update-initramfs: Generating /boot/initrd.img-4.10.0-19-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasdb (0200). Done. Unfortunately, I have no way to revert my z/KVM instance to re-try on that machine -- 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/1687647 Title: udev version 232-21ubuntu3 from ports is broken on Zesty s390x Status in systemd package in Ubuntu: New Bug description: I'm attempting to install some cert tools on a z/KVM instance of Zesty. This is failing because udev exits with an error during installation. The apt logs show this: Setting up udev (232-21ubuntu3) ... addgroup: The group `input' already exists as a system group. Exiting. cat: '/sys/class/net/eth*/address': No such file or directory dpkg: error processing package udev (--configure): subprocess installed post-installation script returned error exit status 1 and because of that, all other packages up the dependency chain fail to install. Interestingly, this is resolved by installing the older version of udev and libudev1 ubuntu@s1lp9g003:~$ apt-cache policy udev udev: Installed: 232-21ubuntu3 Candidate: 232-21ubuntu3 Version table: *** 232-21ubuntu3 500 500 http://us.ports.ubuntu.com/ubuntu-ports zesty-updates/main s390x Packages 100 /var/lib/dpkg/status 232-21ubuntu2 500 500 http://us.ports.ubuntu.com/ubuntu-ports zesty/main s390x Packages ubuntu@s1lp9g003:~$ sudo apt-get install udev=232-21ubuntu2 libudev1=232-21ubuntu2 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-image-4.8.0-36-generic linux-image-4.8.0-46-generic linux-image-extra-4.8.0-36-generic linux-image-extra-4.8.0-46-generic Use 'sudo apt autoremove' to remove them. The following packages will be DOWNGRADED: libudev1 udev 0 upgraded, 0 newly installed, 2 downgraded, 0 to remove and 0 not upgraded. 6 not fully installed or removed. Need to get 0 B/1056 kB of archives. After this operation, 3072 B disk space will be freed. Do you want to continue? [Y/n] y dpkg: warning: downgrading udev from 232-21ubuntu3 to 232-21ubuntu2 (Reading database ... 99656 files and directories currently installed.) Preparing to unpack .../udev_232-21ubuntu2_s390x.deb ... Unpacking udev (232-21ubuntu2) over (232-21ubuntu3) ... dpkg: warning: downgrad
[Touch-packages] [Bug 1687015] Re: 229_4ubuntu17 removes group write permissions from /var/log
I'm an idiot. Of course strace doesn't trace forks by default. I did a full strace -f (including custom build of strace to stop truncating arguments) and found more info. The culprit seems to be /bin/systemd-tmpfiles During install of the package this is called like so: /bin/systemd-tmpfiles --create /usr/lib/tmpfiles.d/debian.conf /usr/lib/tmpfiles.d/home.conf /usr/lib/tmpfiles.d/journal-nocow.conf /usr/lib/tmpfiles.d/legacy.conf /usr/lib/tmpfiles.d/systemd-nologin.conf /usr/lib/tmpfiles.d/systemd.conf /usr/lib/tmpfiles.d/tmp.conf /usr/lib/tmpfiles.d/var.conf /usr/lib/tmpfiles.d/x11.conf On a clean default xenial lxd image, in which /var/log is 775, running the above, even without upgrading to 229_4ubuntu17, will change perms on /var/log to 755. Digging further, I see a conflict in tmpfiles.d config for /var/log in the *current* xenial image. $ cat /usr/lib/tmpfiles.d/00rsyslog.conf # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by # the syslog group, so that rsyslog can run as user. # See tmpfiles.d(5) for details. The config it's overriding is in /usr/lib/tmpfiles.d/var.conf: ... d /var/log 0755 - - - ... It seems that, by providing an explicit list of tmpfiles.d to the /bin /systemd-tmpfiles, the install process is excluding the careful placed override in /usr/lib/tmpfiles.d/00rsyslog.conf -- 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/1687015 Title: 229_4ubuntu17 removes group write permissions from /var/log Status in systemd package in Ubuntu: Incomplete Bug description: Steps to reproduce (time senstive, once lxd image is updated with 4ubuntu17, I expect this won't work) lxc launch ubuntu:x test lxc exec test -- ls -ld /var/log # shows 775 perms lxc exec test -- apt update lxc exec test -- apt-cache policy systemd lxc exec test -- apt install systemd lxc exec test -- ls -ld /var/log # shows 755 permissions straceing the apt install shows no chmod calls to /var/log (only /var/log/apt.log, as you'd expect) This means syslog cannot write new files in /var/log, and had broken some production logging for us as a result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1687015/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687652] Re: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 [origin: unknown] failed to install/upgrade: subprocess installed post-installation script returned error
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1687652 Title: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 [origin: unknown] failed to install/upgrade: subprocess installed post- installation script returned error exit status 1 Status in url-dispatcher package in Ubuntu: New Bug description: While Upgrading from 16.10 to 17.04 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 4.8.0-51.54-generic 4.8.17 Uname: Linux 4.8.0-51-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 AptOrdering: NULL: ConfigurePending Architecture: amd64 CrashDB: url_dispatcher Date: Tue May 2 19:09:46 2017 DpkgHistoryLog: Start-Date: 2017-05-02 19:09:45 Requested-By: sh (1000) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-04-29 (368 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1.1 apt 1.3.5 SourcePackage: url-dispatcher ThirdParty: True Title: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 [origin: unknown] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2017-05-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1687652/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome
Fresh installation of Ubuntu 16.04 and got the same problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1687019 Title: Cannot add a Google account using Online Accounts in Ubuntu Gnome Status in gnome-online-accounts package in Ubuntu: Confirmed Status in gnome-online-accounts package in Arch Linux: New Bug description: With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13 laptop), I cannot add a Google account using Online-Accounts. If I choose to add a new Google account in Online Accounts, a window appears where I can enter my Google email. After entering my email and pressing the Next button, a window appears where I can enter my Google password. After entering the password and pressing the Next button, an empty window appears and nothing else happens. I expected this to show something useful, and actually add the Google account to my Gnome environment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1687019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687652] [NEW] package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 [origin: unknown] failed to install/upgrade: subprocess installed post-installation script returned erro
Public bug reported: While Upgrading from 16.10 to 17.04 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 4.8.0-51.54-generic 4.8.17 Uname: Linux 4.8.0-51-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 AptOrdering: NULL: ConfigurePending Architecture: amd64 CrashDB: url_dispatcher Date: Tue May 2 19:09:46 2017 DpkgHistoryLog: Start-Date: 2017-05-02 19:09:45 Requested-By: sh (1000) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-04-29 (368 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1.1 apt 1.3.5 SourcePackage: url-dispatcher ThirdParty: True Title: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 [origin: unknown] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2017-05-02 (0 days ago) ** Affects: url-dispatcher (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check third-party-packages yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1687652 Title: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 [origin: unknown] failed to install/upgrade: subprocess installed post- installation script returned error exit status 1 Status in url-dispatcher package in Ubuntu: New Bug description: While Upgrading from 16.10 to 17.04 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 4.8.0-51.54-generic 4.8.17 Uname: Linux 4.8.0-51-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 AptOrdering: NULL: ConfigurePending Architecture: amd64 CrashDB: url_dispatcher Date: Tue May 2 19:09:46 2017 DpkgHistoryLog: Start-Date: 2017-05-02 19:09:45 Requested-By: sh (1000) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-04-29 (368 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1.1 apt 1.3.5 SourcePackage: url-dispatcher ThirdParty: True Title: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 [origin: unknown] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2017-05-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1687652/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682499] Re: disable dnssec
Greetings, everyone. I'm on Ubuntu GNOME 17.04 I see that DNSSEC is now off by default, however, in my log, I would see something like: 4 May 2 23:29:31 lavender systemd-resolved[1129]: Grace period over, resuming full feature set (UDP+EDNS0+DO+LARGE) for DNS server 10.2.5.7. 5 May 2 23:29:31 lavender systemd-resolved[1129]: Using degraded feature set (UDP) for DNS server 10.2.5.7. And during that, it seems the systemd-resolved would act just like DNSSEC enabled, and Web would fail some time like before. I don't quite get what is going on. I have dnsmasq run in my network to provide DNS cache, it's the 10.2.5.7 . My upstream server do not support DNSSEC, so the validation would fail certainly. What I observed is during this feature set test, dnsmasq cache would receive TCP connection from Ubuntu GNOME 17.04 . And take some time, the test fail. I know this feature test would fail, as I know the upstream server do not support DNSSEC. I don't know what is EDNS0 or LARGE. But the problem here is that even DNSSEC is now off by default, this feature set test would still do the "DO" test, which stands for DNSSEC OK. It would surely fail, and it can not be turned off via configuration, and it would cut the Web for some time. There is a patch for this: https://github.com/systemd/systemd/issues/5352 Is it possible to cherry pick it please ? ** Bug watch added: github.com/systemd/systemd/issues #5352 https://github.com/systemd/systemd/issues/5352 -- 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/1682499 Title: disable dnssec Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Zesty: Fix Released Bug description: [Impact] * dnssec functionality in systemd-resolved prevents network access in certain intra and extra net cases, due to failure to correctly validate dnssec entries. As a work-around we should disable dnssec by default. [Test Case] * Validate systemd-resolved is compiled with --with-default-dnssec=no * Validate that systemd-resolve --status says that DNSSEC setting is no $ systemd-resolve --status good output: ... DNSSEC setting: no DNSSEC supported: no ... bad output: ... DNSSEC setting: allow-downgrade DNSSEC supported: yes ... [Regression Potential] * People who expect DNSSEC to be available by default will need to re-enable it by modifying systemd-resolve configuration file [Other Info] * See duplicate bugs and other bug reports in systemd for scenarios of DNS resolution failures when DNSSEC is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1682499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686618] Re: ssh connection attempts fail if hw crypto support on s390x is enabled on 17.04
7.5 is now in artful. https://launchpad.net/ubuntu/+source/openssh/1:7.5p1-2 ** Changed in: openssh (Ubuntu Artful) Status: Triaged => Fix Released ** Changed in: openssh (Ubuntu Zesty) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: openssh (Ubuntu Zesty) Milestone: None => zesty-updates ** Changed in: openssh (Ubuntu Zesty) Status: New => Triaged ** Changed in: openssh (Ubuntu Zesty) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1686618 Title: ssh connection attempts fail if hw crypto support on s390x is enabled on 17.04 Status in Ubuntu on IBM z Systems: Triaged Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Zesty: Triaged Status in openssh source package in Artful: Fix Released Bug description: short: after investigations the following commits are needed by openssh-server version 7.4p1 that is part of 17.04: - 5f1596e11d55539678c41f68aed358628d33d86f - 9e96b41682aed793fadbea5ccd472f862179fb02 on master branch in https://github.com/openssh/openssh-portable that belong to openssh 7.5 release notes statement: "sshd(8): Avoid sandbox errors for Linux S390 systems using an ICA crypto coprocessor." __ long: enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x like this: sudo apt-get install openssh-ibmca libica-utils libica2 sudo tee -a /etc/ssl/openssl.cnf < /usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' /etc/ssl/openssl.cnf sudo sed -i '10i openssl_cnf = openssl_def' /etc/ssl/openssl.cnf afterwards ssh login attempts fail: $ ssh ubuntu@zlin42 ubuntu@zlin42's password: Connection to zlin42 closed by remote host. Connection to zlin42 closed. the normal logs don't provide any interesting details: mit log: Apr 24 12:37:52 zlin42 kernel: [933567.994312] audit: type=1326 audit(1493051872.112:29): auid=4294967295 uid=107 gid=65534 ses=4294967295 pid=25105 comm="sshd" exe="/usr/sbin/sshd" sig=31 arch=8016 syscall=201 compat=0 ip=0x3ffb8a3fb32 code=0x0 Verbose: OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g 1 Mar 2016 debug1: Reading configuration data /home/fheimes/.ssh/config debug1: /home/fheimes/.ssh/config line 6: Deprecated option "useroaming" debug1: /home/fheimes/.ssh/config line 7: Applying options for * debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to 10.245.208.7 [10.245.208.7] port 22. debug1: Connection established. debug1: identity file /home/fheimes/.ssh/id_rsa type 1 debug1: key_load_public: No such file or directory debug1: identity file /home/fheimes/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/fheimes/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/fheimes/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/fheimes/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/fheimes/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/fheimes/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/fheimes/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.1 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4p1 Ubuntu-10 debug1: match: OpenSSH_7.4p1 Ubuntu-10 pat OpenSSH* compat 0x0400 debug1: Authenticating to 10.245.208.7:22 as 'ubuntu' debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: curve25519-sha...@libssh.org debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ecdsa-sha2-nistp256 SHA256:ss9j12+jMMKL9u2vxNeb3XjOeH0E9lw24IG5LxUeJXk debug1: Host '10.245.208.7' is known and matches the ECDSA host key. debug1: Found key in /home/fheimes/.ssh/known_hosts:87 debug1: rekey after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: rekey after 134217728 blocks debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs= debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,
[Touch-packages] [Bug 1687647] [NEW] udev version 232-21ubuntu3 from ports is broken on Zesty s390x
Public bug reported: I'm attempting to install some cert tools on a z/KVM instance of Zesty. This is failing because udev exits with an error during installation. The apt logs show this: Setting up udev (232-21ubuntu3) ... addgroup: The group `input' already exists as a system group. Exiting. cat: '/sys/class/net/eth*/address': No such file or directory dpkg: error processing package udev (--configure): subprocess installed post-installation script returned error exit status 1 and because of that, all other packages up the dependency chain fail to install. Interestingly, this is resolved by installing the older version of udev and libudev1 ubuntu@s1lp9g003:~$ apt-cache policy udev udev: Installed: 232-21ubuntu3 Candidate: 232-21ubuntu3 Version table: *** 232-21ubuntu3 500 500 http://us.ports.ubuntu.com/ubuntu-ports zesty-updates/main s390x Packages 100 /var/lib/dpkg/status 232-21ubuntu2 500 500 http://us.ports.ubuntu.com/ubuntu-ports zesty/main s390x Packages ubuntu@s1lp9g003:~$ sudo apt-get install udev=232-21ubuntu2 libudev1=232-21ubuntu2 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-image-4.8.0-36-generic linux-image-4.8.0-46-generic linux-image-extra-4.8.0-36-generic linux-image-extra-4.8.0-46-generic Use 'sudo apt autoremove' to remove them. The following packages will be DOWNGRADED: libudev1 udev 0 upgraded, 0 newly installed, 2 downgraded, 0 to remove and 0 not upgraded. 6 not fully installed or removed. Need to get 0 B/1056 kB of archives. After this operation, 3072 B disk space will be freed. Do you want to continue? [Y/n] y dpkg: warning: downgrading udev from 232-21ubuntu3 to 232-21ubuntu2 (Reading database ... 99656 files and directories currently installed.) Preparing to unpack .../udev_232-21ubuntu2_s390x.deb ... Unpacking udev (232-21ubuntu2) over (232-21ubuntu3) ... dpkg: warning: downgrading libudev1:s390x from 232-21ubuntu3 to 232-21ubuntu2 Preparing to unpack .../libudev1_232-21ubuntu2_s390x.deb ... Unpacking libudev1:s390x (232-21ubuntu2) over (232-21ubuntu3) ... Setting up libudev1:s390x (232-21ubuntu2) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for libc-bin (2.24-9ubuntu2) ... Setting up udev (232-21ubuntu2) ... addgroup: The group `input' already exists as a system group. Exiting. update-initramfs: deferring update (trigger activated) Processing triggers for systemd (232-21ubuntu3) ... Processing triggers for man-db (2.7.6.1-2) ... Setting up python3-checkbox-support (0.34.0~rc1+git201704041517+pkg52~ubuntu17.04.1) ... Setting up plainbox-provider-resource-generic (0.31.0+git201704241134+pkg28~ubuntu17.04.1) ... Setting up plainbox-provider-checkbox (0.35.0+git201705012258+pkg34~ubuntu17.04.1) ... Setting up plainbox-provider-certification-server (0.33.0+git201705021508+pkg60~ubuntu17.04.1) ... Setting up canonical-certification-server (0.33.0+git201705021508+pkg60~ubuntu17.04.1) ... Processing triggers for initramfs-tools (0.125ubuntu9) ... update-initramfs: Generating /boot/initrd.img-4.10.0-20-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: vda (). Done. As you can see, once I installed the original zesty version of udev and libudev1, my packages succeeded in completing installation. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: udev 232-21ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic s390x NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4 Architecture: s390x CustomUdevRuleFiles: 41-generic-ccw-0.0.0003.rules 41-generic-ccw-0.0.0004.rules 41-generic-ccw-0.0..rules 41-generic-ccw-0.0.0005.rules 41-cio-ignore.rules 41-generic-ccw-0.0.0001.rules 41-generic-ccw-0.0.0002.rules Date: Tue May 2 11:41:16 2017 Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcKernelCmdLine: root=/dev/mapper/s1lp9g003_vg-s1lp9g003_lv crashkernel=196M SourcePackage: systemd UpgradeStatus: Upgraded to zesty on 2017-04-13 (18 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug s390x zesty -- 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/1687647 Title: udev version 232-21ubuntu3 from ports is broken on Zesty s390x Status in systemd package in Ubuntu: New Bug description: I'm attempting to install some cert tools on a z/KVM instance of Zesty. This is failing because udev exits with an error during
[Touch-packages] [Bug 1687482] Re: -4 flag doesn't work
I'm running xenial. After I saw your comment I tried it on zesty and have yet to run into this bug on zesty. I haven't tried in the same environment yet though, I can try that later this week as well as get an apport-collect done. As you can see below, the last login reports an ipv6 address. I verified it is using ipv6 using iftop as well. I also tried your trivial case and the same thing happened. We are running freeipa, I don't know if that would have an effect or not. If it's fixed in zesty, is there any way to get the same fix into xenial? bryceml@ratpoison:~$ ssh -4 sake Welcome to Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-75-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage 0 packages can be updated. 0 updates are security updates. Last login: Tue May 2 08:50:11 2017 from 2620:10f:3007:a068:1a66:daff:fe1f:a85 bryceml@sake:~$ logout Connection to sake closed. bryceml@ratpoison:~$ ssh -4 sake Welcome to Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-75-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage 0 packages can be updated. 0 updates are security updates. Last login: Tue May 2 08:50:27 2017 from 2620:10f:3007:a068:1a66:daff:fe1f:a85 bryceml@sake:~$ host sake sake.cs.byu.edu has address 192.168.168.107 sake.cs.byu.edu has IPv6 address 2620:10f:3007:a068:1a66:daff:fe1f:d96f bryceml@sake:~$ bryceml@ratpoison:~$ ssh -4 ip6-localhost The authenticity of host 'ip6-localhost ()' can't be established. ECDSA key fingerprint is SHA256:nhU3sXqrZoF3zNUxlWAfuLebsMSFhRuycFFWHlL2RRY. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'ip6-localhost' (ECDSA) to the list of known hosts. Welcome to Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-75-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage 0 packages can be updated. 0 updates are security updates. Last login: Tue May 2 08:43:46 2017 from 2620:10f:3007:a080:1a66:daff:fe1f:1057 bryceml@ratpoison:~$ logout Connection to ip6-localhost closed. bryceml@ratpoison:~$ ssh -4 ip6-localhost Welcome to Ubuntu 16.04.2 LTS (GNU/Linux 4.4.0-75-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage 0 packages can be updated. 0 updates are security updates. Last login: Tue May 2 08:57:16 2017 from ::1 bryceml@ratpoison:~$ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1687482 Title: -4 flag doesn't work Status in openssh package in Ubuntu: Incomplete Bug description: Whenever I use the -4 flag on ssh, it still uses the ipv6 address from dns instead of forcing ipv4 like it says it is supposed to do in the man page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1687482/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687015] Re: 229_4ubuntu17 removes group write permissions from /var/log
Xenial, sorry, ubuntu:x is lxd shortcut for xenial. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1687015 Title: 229_4ubuntu17 removes group write permissions from /var/log Status in systemd package in Ubuntu: Incomplete Bug description: Steps to reproduce (time senstive, once lxd image is updated with 4ubuntu17, I expect this won't work) lxc launch ubuntu:x test lxc exec test -- ls -ld /var/log # shows 775 perms lxc exec test -- apt update lxc exec test -- apt-cache policy systemd lxc exec test -- apt install systemd lxc exec test -- ls -ld /var/log # shows 755 permissions straceing the apt install shows no chmod calls to /var/log (only /var/log/apt.log, as you'd expect) This means syslog cannot write new files in /var/log, and had broken some production logging for us as a result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1687015/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687015] Re: 229_4ubuntu17 removes group write permissions from /var/log
Installing systemd 229_4ubuntu17 also installs the same version of libsystemd0 and libpam-systemd, so possibly could be those packages, but as noted, an strace of 'apt install systemd' didn't indictate anything. -- 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/1687015 Title: 229_4ubuntu17 removes group write permissions from /var/log Status in systemd package in Ubuntu: Incomplete Bug description: Steps to reproduce (time senstive, once lxd image is updated with 4ubuntu17, I expect this won't work) lxc launch ubuntu:x test lxc exec test -- ls -ld /var/log # shows 775 perms lxc exec test -- apt update lxc exec test -- apt-cache policy systemd lxc exec test -- apt install systemd lxc exec test -- ls -ld /var/log # shows 755 permissions straceing the apt install shows no chmod calls to /var/log (only /var/log/apt.log, as you'd expect) This means syslog cannot write new files in /var/log, and had broken some production logging for us as a result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1687015/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687015] Re: 229_4ubuntu17 removes group write permissions from /var/log
The source package: https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu17 and the diff: http://launchpadlibrarian.net/306522149/systemd_229-4ubuntu16_229-4ubuntu17.diff.gz -- 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/1687015 Title: 229_4ubuntu17 removes group write permissions from /var/log Status in systemd package in Ubuntu: Incomplete Bug description: Steps to reproduce (time senstive, once lxd image is updated with 4ubuntu17, I expect this won't work) lxc launch ubuntu:x test lxc exec test -- ls -ld /var/log # shows 775 perms lxc exec test -- apt update lxc exec test -- apt-cache policy systemd lxc exec test -- apt install systemd lxc exec test -- ls -ld /var/log # shows 755 permissions straceing the apt install shows no chmod calls to /var/log (only /var/log/apt.log, as you'd expect) This means syslog cannot write new files in /var/log, and had broken some production logging for us as a result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1687015/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687640] [NEW] gstreamer 1.12 updates drop ubuntu-touch changes
Public bug reported: I'm uploading gstreamer 1.11.91 to Artful. The following Ubuntu Touch changes have been dropped either because they don't apply or to take us closer to Debian so that the packages are easier to maintain. base: 0001-riff-Add-input-buffer-size-to-GstCaps.patch good: qtdemux-Set-maximum-sample-input-size-in-caps.patch bad: adding-mirsink-and-android-media-over-hybris-support.patch desktop-mirsink.patch videoparsers, faad package split ugly: amr split The git repositories are still there under ~ubuntu-desktop on Launchpad. I'm filing this so that if you want to revive any of the changes you can propose merges to bring them back. Please only do this if they are going to be used in Ubuntu, as the cost of maintaining them on an ongoing basis is real. ** Affects: gst-plugins-bad1.0 (Ubuntu) Importance: Undecided Status: New ** Affects: gst-plugins-base1.0 (Ubuntu) Importance: Undecided Status: New ** Affects: gst-plugins-good1.0 (Ubuntu) Importance: Undecided Status: New ** Affects: gst-plugins-ugly1.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-plugins-good1.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-plugins-bad1.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-plugins-ugly1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1687640 Title: gstreamer 1.12 updates drop ubuntu-touch changes Status in gst-plugins-bad1.0 package in Ubuntu: New Status in gst-plugins-base1.0 package in Ubuntu: New Status in gst-plugins-good1.0 package in Ubuntu: New Status in gst-plugins-ugly1.0 package in Ubuntu: New Bug description: I'm uploading gstreamer 1.11.91 to Artful. The following Ubuntu Touch changes have been dropped either because they don't apply or to take us closer to Debian so that the packages are easier to maintain. base: 0001-riff-Add-input-buffer-size-to-GstCaps.patch good: qtdemux-Set-maximum-sample-input-size-in-caps.patch bad: adding-mirsink-and-android-media-over-hybris-support.patch desktop-mirsink.patch videoparsers, faad package split ugly: amr split The git repositories are still there under ~ubuntu-desktop on Launchpad. I'm filing this so that if you want to revive any of the changes you can propose merges to bring them back. Please only do this if they are going to be used in Ubuntu, as the cost of maintaining them on an ongoing basis is real. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1687640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules
On Tue, May 2, 2017 at 8:54 AM, Dimitri John Ledkov wrote: > Ideally, the following should happen: > * boot > * Created link configuration context > > * Check if link configuration needs reloading -> appears in the debug logs > * New MTU is successfully applied > Let me put in the cloud-init sequence and see if we can figure out what may be missing. * boot * systemd-udev* sockets, trigger, settle, udevd , cloud-init-local : run * cloud-init writes a netplan.yaml * cloud-init invokes netplan-generate * system reaches sysinit.target Looking at the deps on the systemd-udev units; there's no strict ordering in cloud-init that says it would run before, or strictly after udev related units. If you note about the ignoring updated files that are less than 3 seconds old as well as systemd's variability w.r.t unit ordering due to missing explicit Before/After directives might explain the race. I'd prefer not to wait for 3 seconds just because; so it maybe use useful to see if we can run cloud-init before udev; however it's not clear if invoking udev settle in cloudinit (which is done at various places directly (or indirectly through calling programs like blkid or other system programs) would end up waiting. We could also explicitly order cloud-init-local after the udevd service which depends on all other udev units; however, if cloud-init runs immediately after it, the 3 seconds may not have passed. I like running after udevd, but I would like to see if we can force/configure udev to not wait that 3 seconds; > If the 'Check ...' is missing from the debug logs, after netplan has > run, udevd will not reload the configs. > > I also would have thought that calling udevadm control --reload would > force it to reload the contexts for the builtins. > > >From the original bug report description there is a call to: > 'systemctl', 'start', '--no-block', 'systemd-udev-trigger.service' > > But if one is doing that, to avoid races, one should call udevadm settle > -t 3 before re-triggering add. > Note that -t 3, --timeout=3 only sets the maxium wait time; this means that if it processes any event with in those 3 seconds, that we may not have waited long enough for udev when it re-reads link files and says it's not 3 seconds since the last time. The 3 second re-read is arbitrary and ideally should be replaced by content hashing or use of inotify such that changes to the file (.link) can be triggered automatically without hacky things like sleep 3. > These things are possibly red herrings too. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1669564 > > Title: > udevadm trigger subsystem-match=net doesn't always run rules > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/ > 1669564/+subscriptions > -- 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/1669564 Title: udevadm trigger subsystem-match=net doesn't always run rules Status in systemd package in Ubuntu: New Bug description: 1. root@ubuntu:~# lsb_release -rd Description:Ubuntu Zesty Zapus (development branch) Release:17.04 2. root@ubuntu:~# apt-cache policy udev udev: Installed: 232-18ubuntu1 Candidate: 232-18ubuntu1 Version table: *** 232-18ubuntu1 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status 3. udevadm trigger --verbose --subsystem-match=net --action=add will run and read .link files from /run/systemd/network/10-netplan-interface1.link and apply MTU settings 4. during system boot running (3) does not set the MTU; running (3) after boot has completed MTU is set correctly. Here'a log during boot where cloud-init generates a netplan config, invokes `netplan generate` which writes the networkd config out and then udevadm trigger (3). Upon logging in interface1 has an MTU of 1500. Re-running udevadm trigger now runs the rules/link files and updates the MTU. Note that, if you run udevadm test /sys/class/net/interface1; this also will apply the MTU (test probably shouldn't change the interface, I'll file a bug for that as well). # journalctl -o short-precise --no-pager -b | grep WARK Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['netplan', '--debug', 'generate']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['stat', '/run/systemd/network/10-netplan-interface1.link']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['cat', '/run/systemd/network/10-netplan-interface1.link']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['systemctl', 'start', '--no-block', 'systemd-udev-trigger.service']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['udevadm', 'trigger', '--verbose', '--subsystem-match=net', '--action=add']: root
[Touch-packages] [Bug 1686183] Re: Ship ubuntu-advantage in ubuntu-minimal
This bug was fixed in the package ubuntu-meta - 1.267.2 --- ubuntu-meta (1.267.2) precise; urgency=medium * Refreshed dependencies * Added ubuntu-advantage-tools to minimal LP: #1686183 -- Dimitri John Ledkov Fri, 28 Apr 2017 16:12:30 +0100 ** Changed in: ubuntu-meta (Ubuntu Precise) Status: Fix Committed => Fix Released -- 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/1686183 Title: Ship ubuntu-advantage in ubuntu-minimal Status in ubuntu-advantage-tools package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-advantage-tools source package in Precise: Fix Released Status in ubuntu-meta source package in Precise: Fix Released Bug description: [Impact] * Allow ubuntu-advantage users to access the extended security maintenance script with a simple command line tool. This script needs to hit precise machines and be easy for ubuntu-advantage customers to enable, thus basefiles was chosen as a home. [Test Case] * Run ubuntu-advantage, it should print out help * Run sudo ubuntu-advantage enable (without sudo it will warn you), but you need to be an ubuntu-advantage customer to get that token. In the end, the script simply adds and removes an /etc/apt/sources.list.d entry. * you can contact me (d...@canonical.com) if you would like a token for test purposes. [Regression Potential] * Low, this is a new script, not included in any automated startup paths. [Other Info] * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1686183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686183] Update Released
The verification of the Stable Release Update for ubuntu-advantage-tools 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 ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1686183 Title: Ship ubuntu-advantage in ubuntu-minimal Status in ubuntu-advantage-tools package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-advantage-tools source package in Precise: Fix Released Status in ubuntu-meta source package in Precise: Fix Released Bug description: [Impact] * Allow ubuntu-advantage users to access the extended security maintenance script with a simple command line tool. This script needs to hit precise machines and be easy for ubuntu-advantage customers to enable, thus basefiles was chosen as a home. [Test Case] * Run ubuntu-advantage, it should print out help * Run sudo ubuntu-advantage enable (without sudo it will warn you), but you need to be an ubuntu-advantage customer to get that token. In the end, the script simply adds and removes an /etc/apt/sources.list.d entry. * you can contact me (d...@canonical.com) if you would like a token for test purposes. [Regression Potential] * Low, this is a new script, not included in any automated startup paths. [Other Info] * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1686183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686183] Re: Ship ubuntu-advantage in ubuntu-minimal
This bug was fixed in the package ubuntu-advantage-tools - 1 --- ubuntu-advantage-tools (1) precise; urgency=medium * Initial Release. LP: #1686183 -- Dimitri John Ledkov Fri, 28 Apr 2017 15:04:47 +0100 ** Changed in: ubuntu-advantage-tools (Ubuntu Precise) Status: Fix Committed => Fix Released -- 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/1686183 Title: Ship ubuntu-advantage in ubuntu-minimal Status in ubuntu-advantage-tools package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-advantage-tools source package in Precise: Fix Released Status in ubuntu-meta source package in Precise: Fix Released Bug description: [Impact] * Allow ubuntu-advantage users to access the extended security maintenance script with a simple command line tool. This script needs to hit precise machines and be easy for ubuntu-advantage customers to enable, thus basefiles was chosen as a home. [Test Case] * Run ubuntu-advantage, it should print out help * Run sudo ubuntu-advantage enable (without sudo it will warn you), but you need to be an ubuntu-advantage customer to get that token. In the end, the script simply adds and removes an /etc/apt/sources.list.d entry. * you can contact me (d...@canonical.com) if you would like a token for test purposes. [Regression Potential] * Low, this is a new script, not included in any automated startup paths. [Other Info] * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1686183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1274613] Re: module-bluetooth-discover does not load on login
confirmed that the resolution posted by cfgnunes works on 14.04 LTS: sudo apt-add-repository ppa:cschramm/blueman -y && sudo apt-get dist- upgrade -y I'm using an MSi u-100 netbook with an upgraded intel 7260 network card; and I was going insane trying to get a2dp working. I no longer have to manually load the bluetooth module even though it was listed in /etc/pulse/default.pa. 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/1274613 Title: module-bluetooth-discover does not load on login Status in pulseaudio package in Ubuntu: Triaged Bug description: The following lines appear in /etc/pulse/default.pa, which I have not modified: .ifexists module-bluetooth-discover.so load-module module-bluetooth-discover .endif Expected: module-bluetooth-discover is loaded on login, as configured. Observed: pulseaudio's module-bluetooth-discover does not load on login. My system does not detect and set up sinks when I connect to Bluetooth devices (including an A2DP speaker and a headset). If I issue, in a terminal window: $ pactl load-module module-bluetooth-discover 24 …then the devices are detected and sinks set up correctly. $ lsb_release -rd && apt-cache policy pulseaudio-module-bluetooth Description:Ubuntu 13.10 Release:13.10 pulseaudio-module-bluetooth: Installed: 1:4.0-0ubuntu6 Candidate: 1:4.0-0ubuntu6 Version table: *** 1:4.0-0ubuntu6 0 500 http://mirrors.mit.edu/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.30-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: khaeru 2051 F pulseaudio Date: Thu Jan 30 12:18:50 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-10-29 (457 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-09-11 (140 days ago) dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 085VR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn085VR5:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1274613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules
Ideally, the following should happen: * boot * Created link configuration context * Check if link configuration needs reloading -> appears in the debug logs * New MTU is successfully applied If the 'Check ...' is missing from the debug logs, after netplan has run, udevd will not reload the configs. I also would have thought that calling udevadm control --reload would force it to reload the contexts for the builtins. >From the original bug report description there is a call to: 'systemctl', 'start', '--no-block', 'systemd-udev-trigger.service' But if one is doing that, to avoid races, one should call udevadm settle -t 3 before re-triggering add. These things are possibly red herrings too. -- 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/1669564 Title: udevadm trigger subsystem-match=net doesn't always run rules Status in systemd package in Ubuntu: New Bug description: 1. root@ubuntu:~# lsb_release -rd Description:Ubuntu Zesty Zapus (development branch) Release:17.04 2. root@ubuntu:~# apt-cache policy udev udev: Installed: 232-18ubuntu1 Candidate: 232-18ubuntu1 Version table: *** 232-18ubuntu1 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status 3. udevadm trigger --verbose --subsystem-match=net --action=add will run and read .link files from /run/systemd/network/10-netplan-interface1.link and apply MTU settings 4. during system boot running (3) does not set the MTU; running (3) after boot has completed MTU is set correctly. Here'a log during boot where cloud-init generates a netplan config, invokes `netplan generate` which writes the networkd config out and then udevadm trigger (3). Upon logging in interface1 has an MTU of 1500. Re-running udevadm trigger now runs the rules/link files and updates the MTU. Note that, if you run udevadm test /sys/class/net/interface1; this also will apply the MTU (test probably shouldn't change the interface, I'll file a bug for that as well). # journalctl -o short-precise --no-pager -b | grep WARK Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['netplan', '--debug', 'generate']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['stat', '/run/systemd/network/10-netplan-interface1.link']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['cat', '/run/systemd/network/10-netplan-interface1.link']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['systemctl', 'start', '--no-block', 'systemd-udev-trigger.service']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['udevadm', 'trigger', '--verbose', '--subsystem-match=net', '--action=add']: root@ubuntu:~# cat /run/systemd/network/10-netplan-interface1.link [Match] MACAddress=52:54:00:12:34:02 [Link] Name=interface1 WakeOnLan=off MTUBytes=1492 root@ubuntu:~# ifconfig interface1 interface1: flags=4163 mtu 1500 inet 10.0.2.100 netmask 255.255.255.0 broadcast 10.0.2.255 inet6 fe80::5054:ff:fe12:3402 prefixlen 64 scopeid 0x20 inet6 fec0::5054:ff:fe12:3402 prefixlen 64 scopeid 0x40 ether 52:54:00:12:34:02 txqueuelen 1000 (Ethernet) RX packets 16 bytes 5053 (5.0 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 35 bytes 3287 (3.2 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@ubuntu:~# udevadm trigger --verbose --subsystem-match=net --action=add /sys/devices/pci:00/:00:04.0/virtio1/net/interface1 /sys/devices/pci:00/:00:05.0/virtio2/net/interface2 ys/devices/pci:00/:00:06.0/virtio3/net/interface0 /sys/devices/virtual/net/lo root@ubuntu:~# ifconfig interface1 interface1: flags=4163 mtu 1492 inet 10.0.2.100 netmask 255.255.255.0 broadcast 10.0.2.255 inet6 fe80::5054:ff:fe12:3402 prefixlen 64 scopeid 0x20 inet6 fec0::5054:ff:fe12:3402 prefixlen 64 scopeid 0x40 ether 52:54:00:12:34:02 txqueuelen 1000 (Ethernet) RX packets 16 bytes 5053 (5.0 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 37 bytes 3504 (3.5 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: udev 232-18ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Uname: Linux 4.10.0-8-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Thu Mar 2 19:22:14 2017 Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic root=UUID=8bbb84fe-91e8-4a9a-bd91-f6af4793727e r
[Touch-packages] [Bug 1512992] Re: package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1
yakkety verification: without proposed: root@zlib-yakkety-1512992:~# apt install zlib1g-dev:i386 lib32z1-dev (...) Unpacking zlib1g-dev:i386 (1:1.2.8.dfsg-2ubuntu5) ... dpkg: error processing archive /tmp/apt-dpkg-install-ZGcn5m/59-zlib1g-dev_1%3a1.2.8.dfsg-2ubuntu5_i386.deb (--unpack): trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu5 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/apt-dpkg-install-ZGcn5m/59-zlib1g-dev_1%3a1.2.8.dfsg-2ubuntu5_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) With proposed enabled it installs just fine: http://pastebin.ubuntu.com/24498634/ root@zlib-yakkety-1512992:~# apt-cache policy zlib1g-dev:i386 lib32z1-dev zlib1g-dev:i386: Installed: 1:1.2.8.dfsg-2ubuntu5.1 Candidate: 1:1.2.8.dfsg-2ubuntu5.1 Version table: *** 1:1.2.8.dfsg-2ubuntu5.1 500 500 http://br.archive.ubuntu.com/ubuntu yakkety-proposed/main i386 Packages 100 /var/lib/dpkg/status 1:1.2.8.dfsg-2ubuntu5 500 500 http://br.archive.ubuntu.com/ubuntu yakkety/main i386 Packages lib32z1-dev: Installed: 1:1.2.8.dfsg-2ubuntu5.1 Candidate: 1:1.2.8.dfsg-2ubuntu5.1 Version table: *** 1:1.2.8.dfsg-2ubuntu5.1 500 500 http://br.archive.ubuntu.com/ubuntu yakkety-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:1.2.8.dfsg-2ubuntu5 500 500 http://br.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages ** Tags added: verification-done-yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1512992 Title: package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 Status in One Hundred Papercuts: Confirmed Status in zlib package in Ubuntu: Fix Released Status in zlib source package in Xenial: Fix Committed Status in zlib source package in Yakkety: Fix Committed Bug description: Test Case - 1) Install zlib1g-dev:i386 2) Install lib32z1-dev. 3) Observe a package installation failure After enabling -proposed you should be able to install both packages without an issue. Original Description The package did not install when I did a fresh install of 15.10. ProblemType: PackageDistroRelease: Ubuntu 15.10 Package: zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 Date: Wed Nov 4 10:36:43 2015 DuplicateSignature: package:zlib1g-dev:1:1.2.8.dfsg-2ubuntu4:trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 ErrorMessage: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 InstallationDate: Installed on 2015-11-04 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1SourcePackage: zlib Title: package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1512992/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules
Hm. udevd applies MTU property from the link file in the link_config_apply() function, which is called by builtin_net_setup_link(), from the net_setup_link builtin. Reading the conditions for builtin_net_setup_link_init() and builtin_set_setup_link_validate(), the link configuration context is never recreated; but paths_check_timestamp(link_dirs, &ctx->link_dirs_ts_usec, false) is used to determine if things need to be reloaded. It verifies the time of last modification (st_mtim) on the directories that hold the link files. However, udevd only calls validate on the builtins at most every 3 seconds (see udevd.c). Thus if one changes link files (e.g. modification time on the directory less than 3 seconds since the last udev scan), and one triggers to run 80-net-setup-link, the link files will not be re- read and nothing new will happen. >From the original logs, it seems like everything happens within the same second on boot. Hence the race. It would be interesting to boot the bad instances with udev debugging enabled, to observe the messages related to realoding net link configuration and/or applying it, e.g. the interesting messages are: Created link configuration context. Unloaded link configuration context. Check if link configuration needs reloading. Udev debugging can be set by changing /etc/udev/udev.conf and use udev_log="debug", or by booting with udev.log-priority=debug on the kernel command line. Also it would be interesting to see, if we can sleep for 3 seconds, before triggering udevadm add. I understand that hardcoding 3 second sleep is sub-optimal, this is purely to establish if the above analysis is a complete red-herring or not =) -- 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/1669564 Title: udevadm trigger subsystem-match=net doesn't always run rules Status in systemd package in Ubuntu: New Bug description: 1. root@ubuntu:~# lsb_release -rd Description:Ubuntu Zesty Zapus (development branch) Release:17.04 2. root@ubuntu:~# apt-cache policy udev udev: Installed: 232-18ubuntu1 Candidate: 232-18ubuntu1 Version table: *** 232-18ubuntu1 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status 3. udevadm trigger --verbose --subsystem-match=net --action=add will run and read .link files from /run/systemd/network/10-netplan-interface1.link and apply MTU settings 4. during system boot running (3) does not set the MTU; running (3) after boot has completed MTU is set correctly. Here'a log during boot where cloud-init generates a netplan config, invokes `netplan generate` which writes the networkd config out and then udevadm trigger (3). Upon logging in interface1 has an MTU of 1500. Re-running udevadm trigger now runs the rules/link files and updates the MTU. Note that, if you run udevadm test /sys/class/net/interface1; this also will apply the MTU (test probably shouldn't change the interface, I'll file a bug for that as well). # journalctl -o short-precise --no-pager -b | grep WARK Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['netplan', '--debug', 'generate']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['stat', '/run/systemd/network/10-netplan-interface1.link']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['cat', '/run/systemd/network/10-netplan-interface1.link']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['systemctl', 'start', '--no-block', 'systemd-udev-trigger.service']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['udevadm', 'trigger', '--verbose', '--subsystem-match=net', '--action=add']: root@ubuntu:~# cat /run/systemd/network/10-netplan-interface1.link [Match] MACAddress=52:54:00:12:34:02 [Link] Name=interface1 WakeOnLan=off MTUBytes=1492 root@ubuntu:~# ifconfig interface1 interface1: flags=4163 mtu 1500 inet 10.0.2.100 netmask 255.255.255.0 broadcast 10.0.2.255 inet6 fe80::5054:ff:fe12:3402 prefixlen 64 scopeid 0x20 inet6 fec0::5054:ff:fe12:3402 prefixlen 64 scopeid 0x40 ether 52:54:00:12:34:02 txqueuelen 1000 (Ethernet) RX packets 16 bytes 5053 (5.0 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 35 bytes 3287 (3.2 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@ubuntu:~# udevadm trigger --verbose --subsystem-match=net --action=add /sys/devices/pci:00/:00:04.0/virtio1/net/interface1 /sys/devices/pci:00/:00:05.0/virtio2/net/interface2 ys/devices/pci:00/:00:06.0/virtio3/net/interface0 /sys/devices/virtual/net/lo root@ubuntu:~# ifconfig interface1 interface1: flags=4163 mtu 1492 inet 10.0.2.100 netmask 255.255.255.0 broadcast 10.0.2.255 inet6 fe80::5054:ff:fe12:3402
[Touch-packages] [Bug 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS
** Tags removed: server-next -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1683237 Title: krb5-user: kinit fails for OTP user when using kdc discovery via DNS Status in krb5 package in Ubuntu: Fix Released Status in krb5 source package in Zesty: Triaged Status in krb5 package in Debian: Fix Released Bug description: Zesty is now affected, please see the debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307 and upstream bug http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554 Would it be possible to get 1.15.1 (already released upstream) in zesty/zesty-updates? Thanks Jochen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1683237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS
I think this bug is fixed in Artful then, but still affects Zesty? To fix Zesty, please follow the steps documented at https://wiki.ubuntu.com/StableReleaseUpdates#Procedure to get a fixed version released to zesty-updates. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1683237 Title: krb5-user: kinit fails for OTP user when using kdc discovery via DNS Status in krb5 package in Ubuntu: Fix Released Status in krb5 source package in Zesty: Triaged Status in krb5 package in Debian: Fix Released Bug description: Zesty is now affected, please see the debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307 and upstream bug http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554 Would it be possible to get 1.15.1 (already released upstream) in zesty/zesty-updates? Thanks Jochen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1683237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1512992] Re: package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1
xenial verification Reproduced the bug without proposed: root@zlib-xenial-1512992:~# apt install zlib1g-dev:i386 lib32z1-dev (...) Unpacking zlib1g-dev:i386 (1:1.2.8.dfsg-2ubuntu4) ... dpkg: error processing archive /var/cache/apt/archives/zlib1g-dev_1%3a1.2.8.dfsg-2ubuntu4_i386.deb (--unpack): trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 Processing triggers for libc-bin (2.23-0ubuntu7) ... Processing triggers for man-db (2.7.5-1) ... Errors were encountered while processing: /var/cache/apt/archives/zlib1g-dev_1%3a1.2.8.dfsg-2ubuntu4_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) With proposed enabled, installation works just fine: http://pastebin.ubuntu.com/24498586/ root@zlib-xenial-1512992:~# apt-cache policy zlib1g-dev:i386 lib32z1-dev zlib1g-dev:i386: Installed: 1:1.2.8.dfsg-2ubuntu4.1 Candidate: 1:1.2.8.dfsg-2ubuntu4.1 Version table: *** 1:1.2.8.dfsg-2ubuntu4.1 500 500 http://br.archive.ubuntu.com/ubuntu xenial-proposed/main i386 Packages 100 /var/lib/dpkg/status 1:1.2.8.dfsg-2ubuntu4 500 500 http://br.archive.ubuntu.com/ubuntu xenial/main i386 Packages lib32z1-dev: Installed: 1:1.2.8.dfsg-2ubuntu4.1 Candidate: 1:1.2.8.dfsg-2ubuntu4.1 Version table: *** 1:1.2.8.dfsg-2ubuntu4.1 500 500 http://br.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:1.2.8.dfsg-2ubuntu4 500 500 http://br.archive.ubuntu.com/ubuntu xenial/main amd64 Packages ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1512992 Title: package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 Status in One Hundred Papercuts: Confirmed Status in zlib package in Ubuntu: Fix Released Status in zlib source package in Xenial: Fix Committed Status in zlib source package in Yakkety: Fix Committed Bug description: Test Case - 1) Install zlib1g-dev:i386 2) Install lib32z1-dev. 3) Observe a package installation failure After enabling -proposed you should be able to install both packages without an issue. Original Description The package did not install when I did a fresh install of 15.10. ProblemType: PackageDistroRelease: Ubuntu 15.10 Package: zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 Date: Wed Nov 4 10:36:43 2015 DuplicateSignature: package:zlib1g-dev:1:1.2.8.dfsg-2ubuntu4:trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 ErrorMessage: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 InstallationDate: Installed on 2015-11-04 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.2ubuntu5 apt 1.0.10.2ubuntu1SourcePackage: zlib Title: package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1512992/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673717] Re: rsyslog GnuTLS error -50
** Changed in: rsyslog (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1673717 Title: rsyslog GnuTLS error -50 Status in rsyslog package in Ubuntu: New Status in rsyslog package in Debian: New Bug description: Exactly the same as this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832995 Error: > rsyslogd-2078: unexpected GnuTLS error -50 in nsd_gtls.c:530: The > request is invalid. [v8.16.0 try http://www.rsyslog.com/e/2078 ] Provided patch in https://github.com/rsyslog/rsyslog/issues/732 works. Please apply patch or upgrade rsyslog. Ubuntu 16.04 AMD64 Rsyslog 8.16.0-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1673717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687621] [NEW] software problem after every boot
Public bug reported: Appearance of a window "software problem after every boot Apparition d'une fenêtre "problème de logiciel après chaque démérrage ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49 Uname: Linux 4.4.0-67-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue May 2 15:09:19 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] RS780L [Radeon 3000] [1462:7641] InstallationDate: Installed on 2017-02-18 (72 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: MSI MS-7641 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-67-generic root=UUID=45bb9d8c-8080-40ac-8ab3-113b5e1ab1ec ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V17.6 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 760GM-P34(FX) (MS-7641) dmi.board.vendor: MSI dmi.board.version: 4.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 4.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV17.6:bd02/17/2012:svnMSI:pnMS-7641:pvr4.0:rvnMSI:rn760GM-P34(FX)(MS-7641):rvr4.0:cvnMSI:ct3:cvr4.0: dmi.product.name: MS-7641 dmi.product.version: 4.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 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: Mon May 1 12:01:53 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu xenial -- 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/1687621 Title: software problem after every boot Status in xorg package in Ubuntu: New Bug description: Appearance of a window "software problem after every boot Apparition d'une fenêtre "problème de logiciel après chaque démérrage ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49 Uname: Linux 4.4.0-67-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue May 2 15:09:19 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] RS780L [Radeon 3000] [1462:7641] InstallationDate: Installed on 2017-02-18 (72 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: MSI MS-7641 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-67-generic root=UUID=45bb9d8c-8080-40ac-8ab3-113b5e1ab1ec ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V17.6 dmi.board.asset.tag: To Be Filled By O
[Touch-packages] [Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
AFAIK everything landed for this already in zesty (and thus in artful as well). Not sure why it is still "In Progress". I'm setting this to Fix Released; if there are any other issues anyway, they should get their own bug so we can better track any possible SRUs. ** Changed in: initramfs-tools (Ubuntu) Status: In Progress => Fix Released ** Changed in: initramfs-tools (Ubuntu) Assignee: Dave Chiluk (chiluk) => (unassigned) ** Changed in: initramfs-tools (Ubuntu Zesty) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Fix Released Status in initramfs-tools source package in Yakkety: Fix Released Status in initramfs-tools source package in Zesty: Fix Released Bug description: [Impact] * initramfs-tools SRUs introduced regressions in ip= syntax, which cause unexpected behavior [Test Case] * Create a machine that boots using an nfsroot. * Use ip=:eth0:dhcp on the kernel command line. To set up networking. * Discover that the device never comes up because, networking is not configured correctly. [Regression Potential] Should be back to original behavior before ipv6 support was introduced in the past 2 or 3 SRUs. [Other Info] * There are a number of other issues in this code base that are not solved by this fix. - The ?*:?*:?*:?*: use case falls through to the default case, and likely breaks there. As such static assignment via ip= appears broken - * The networking configuration does not strictly follow the kernel documentation as described https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt . This should be fixed. This bug is a regression of changes made under bug 1628306. Original Bug Description Follows== initramfs-tools 0.122ubuntu8.3 introduced a serious regression where networking is not initialized when the boot option "ip=dhcp" is provided. We are seeing this problem in AWS, but cannot confirm if this issue is specific to AWS or will occur with different hardware or in different environments. Removing "ip=dhcp" from the boot options with 0.122ubuntu8.3 results in networking being configured. The issue does not occur with 0.122ubuntu8.2 or previous versions when "ip=dhcp" is set. AWS has no console so debugging is not a trivial task. I do have a console log with some output, and will update this bug shortly with it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules
On Tue, May 2, 2017 at 3:05 AM, Dimitri John Ledkov wrote: > Looking at the journal files from the netplan-udev that fail, I see that > links are already renamed, before cloud-init renders things: > > Mar 09 17:51:12 ubuntu kernel: virtio_net virtio0 ens3: renamed from eth0 > Mar 09 17:51:12 ubuntu kernel: virtio_net virtio1 ens4: renamed from eth1 > Mar 09 17:51:14 ubuntu kernel: virtio_net virtio0 interface0: renamed from > ens3 > Mar 09 17:51:14 ubuntu kernel: virtio_net virtio1 interface1: renamed from > ens4 > Mar 09 17:51:15 ubuntu cloud-init[382]: WARK: ['netplan', 'generate']: > stdout: > Mar 09 17:51:15 ubuntu cloud-init[382]: WARK: ['udevadm', 'trigger', > '--verbose', '--subsystem-match=net', '--action=add']: stdout: > > This seems to me as a test case that did not fail, or there are stray > files left during this test run. > The renames are not the issue; it's the .link files which set things like MTU. cloud-init may issue ip set dev link name commands to apply a new name, if it's not already set but won't issue them if the names are what it expects. > > A full sosreport might be helpful, maybe there are persistent-net rules > written out, in addition to link files? > I can collect a sosreport; I don't think it provides anything additional, the core issue is inside systemd itself w.r.t how the udev code is invoked by systemd-udevd -- 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/1669564 Title: udevadm trigger subsystem-match=net doesn't always run rules Status in systemd package in Ubuntu: New Bug description: 1. root@ubuntu:~# lsb_release -rd Description:Ubuntu Zesty Zapus (development branch) Release:17.04 2. root@ubuntu:~# apt-cache policy udev udev: Installed: 232-18ubuntu1 Candidate: 232-18ubuntu1 Version table: *** 232-18ubuntu1 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status 3. udevadm trigger --verbose --subsystem-match=net --action=add will run and read .link files from /run/systemd/network/10-netplan-interface1.link and apply MTU settings 4. during system boot running (3) does not set the MTU; running (3) after boot has completed MTU is set correctly. Here'a log during boot where cloud-init generates a netplan config, invokes `netplan generate` which writes the networkd config out and then udevadm trigger (3). Upon logging in interface1 has an MTU of 1500. Re-running udevadm trigger now runs the rules/link files and updates the MTU. Note that, if you run udevadm test /sys/class/net/interface1; this also will apply the MTU (test probably shouldn't change the interface, I'll file a bug for that as well). # journalctl -o short-precise --no-pager -b | grep WARK Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['netplan', '--debug', 'generate']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['stat', '/run/systemd/network/10-netplan-interface1.link']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['cat', '/run/systemd/network/10-netplan-interface1.link']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['systemctl', 'start', '--no-block', 'systemd-udev-trigger.service']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['udevadm', 'trigger', '--verbose', '--subsystem-match=net', '--action=add']: root@ubuntu:~# cat /run/systemd/network/10-netplan-interface1.link [Match] MACAddress=52:54:00:12:34:02 [Link] Name=interface1 WakeOnLan=off MTUBytes=1492 root@ubuntu:~# ifconfig interface1 interface1: flags=4163 mtu 1500 inet 10.0.2.100 netmask 255.255.255.0 broadcast 10.0.2.255 inet6 fe80::5054:ff:fe12:3402 prefixlen 64 scopeid 0x20 inet6 fec0::5054:ff:fe12:3402 prefixlen 64 scopeid 0x40 ether 52:54:00:12:34:02 txqueuelen 1000 (Ethernet) RX packets 16 bytes 5053 (5.0 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 35 bytes 3287 (3.2 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@ubuntu:~# udevadm trigger --verbose --subsystem-match=net --action=add /sys/devices/pci:00/:00:04.0/virtio1/net/interface1 /sys/devices/pci:00/:00:05.0/virtio2/net/interface2 ys/devices/pci:00/:00:06.0/virtio3/net/interface0 /sys/devices/virtual/net/lo root@ubuntu:~# ifconfig interface1 interface1: flags=4163 mtu 1492 inet 10.0.2.100 netmask 255.255.255.0 broadcast 10.0.2.255 inet6 fe80::5054:ff:fe12:3402 prefixlen 64 scopeid 0x20 inet6 fec0::5054:ff:fe12:3402 prefixlen 64 scopeid 0x40 ether 52:54:00:12:34:02 txqueuelen 1000 (Ethernet) RX packets 16 bytes 5053 (5.0 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 37 bytes 3504 (3.5 KB)
[Touch-packages] [Bug 1686577] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1686577 Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: Incomplete Bug description: update issue ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.2 ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-49-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed Apr 26 20:33:34 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-03-01 (56 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 65: Bad configuration option: X11UseForwarding /etc/ssh/sshd_config: terminating, 1 bad configuration options SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1686577/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686577] Re: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
>From the log: /etc/ssh/sshd_config: line 65: Bad configuration option: X11UseForwarding I only happen to know "X11Forwarding" as option, maybe the other one is an old entry or from an outdated howto? On upgrades the services need to be restarted. A broken configuration like this will prevent the update to work properly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1686577 Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: Incomplete Bug description: update issue ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.2 ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-49-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed Apr 26 20:33:34 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-03-01 (56 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 65: Bad configuration option: X11UseForwarding /etc/ssh/sshd_config: terminating, 1 bad configuration options SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1686577/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686472] Re: package libkrb5support0:amd64 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting
>From the log: install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration I can't spot what initially failed for you, but since you are now in a bad state I'd recommend to follow usual cleanup howtos as in [1] just adapted to the packages you are facing issues with. That seem to be overall: - libgssapi-krb5-2 - libkrb5-3 - libkrb5support0 Refreshing those should help, please report back if the problem persists. [1]: https://askubuntu.com/questions/148715/how-to-fix-package-is-in-a -very-bad-inconsistent-state-error ** Changed in: krb5 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1686472 Title: package libkrb5support0:amd64 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in krb5 package in Ubuntu: Incomplete Bug description: NA ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libkrb5support0:amd64 1.13.2+dfsg-5ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Wed Apr 26 08:35:07 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libkrb5support0:amd64:1.13.2+dfsg-5ubuntu2 Unpacking chromium-codecs-ffmpeg-extra (58.0.3029.81-0ubuntu0.16.04.1277) over (57.0.2987.98-0ubuntu0.16.04.1276) ... dpkg: error processing package libkrb5support0:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-05-04 (357 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: krb5 Title: package libkrb5support0:amd64 1.13.2+dfsg-5ubuntu2 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/krb5/+bug/1686472/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1657553] Re: Laptop stick and touchpad problems after linux 4.4 update
Hi, I am pretty sure that I've got the same issue (Dell Latitude E5470, Linux Mint 18.1 x64). It did not work with kernel 4.8 so I updated to kernel 4.10.0-20-generic and the problem persists. xinput lists: ⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPad id=12 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS DualPoint Stick id=13 [slave pointer (2)] Let me know if any other information is needed. Thanks and best regards, Philip -- 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/1657553 Title: Laptop stick and touchpad problems after linux 4.4 update Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Status in linux source package in Xenial: Incomplete Status in systemd source package in Xenial: Confirmed Bug description: Ever since the 4.4.0-53 kernel update the touchpad and trackpoint have behaved erratically on my Dell Precision 7510: * The trackpoint moves WAY too fast and there don't seem to be any parameters I can change in xinput to fix this. It is essentially unusable. * The touchpad starts with parameters set incorrectly. * Touchpad tap to click is now turned on again and is very sensitive. This I can change through xinput but the change is still odd. * The two finger scrolling is set incorrectly to be highly sensitive. This I can also change through xinput. * Two finger scrolling still activates often during normal use of the trackpad. To the extent that I had to turn off two finger scrolling to stop inadvertent scrolling. All of the above behavior is new going from 4.4.0-47 to -53. Previously this all worked perfectly on this machine. Seems to be symptoms noted by these other users on askubuntu here as well: http://askubuntu.com/questions/862527/laptop-stick-mouse- problems-after-linux-4-4-update-on-14-04 The touchpad symptoms I seem to be able to work around my changing xinput parameters, but the trackpoint I have not been able to fix at all (which is sad since that is my primary mouse device normally). Would appreciate any suggestions as to how to revert the old behavior. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-53-generic 4.4.0-53.74 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jpeverill 2813 F pulseaudio /dev/snd/controlC0: jpeverill 2813 F pulseaudio Date: Wed Jan 18 10:21:55 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-17 (916 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc. Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 7510 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed root=UUID=4a4cfeb0-ad39-4293-bcaf-000d6538b550 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-05-01 (262 days ago) dmi.bios.date: 01/24/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.10 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.10:bd01/24/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Precision 7510 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657553/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673717] Re: rsyslog GnuTLS error -50
** Bug watch added: Debian Bug tracker #832995 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832995 ** Also affects: rsyslog (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832995 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1673717 Title: rsyslog GnuTLS error -50 Status in rsyslog package in Ubuntu: New Status in rsyslog package in Debian: Unknown Bug description: Exactly the same as this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832995 Error: > rsyslogd-2078: unexpected GnuTLS error -50 in nsd_gtls.c:530: The > request is invalid. [v8.16.0 try http://www.rsyslog.com/e/2078 ] Provided patch in https://github.com/rsyslog/rsyslog/issues/732 works. Please apply patch or upgrade rsyslog. Ubuntu 16.04 AMD64 Rsyslog 8.16.0-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1673717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record
Can confirm, have the same problem: server loses connection after a while with no usable log entries except for the avahi-daemon message. I am however not using Ubuntu, but Arch. Also not in a VM. The NIC is for me the same: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 02). -- 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/1586528 Title: Avahi-daemon withdraws address record Status in avahi package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: For some reason, if I leave my Ubuntu VM up for a prolonged period of time the machine will lose connection to the network. ip addr shows that the nic port no longer has an address and an examination of the syslog shows this: May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record for 10.0.2.15 on enp0s3. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast group on interface enp0s3.IPv4 with address 10.0.2.15. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no longer relevant for mDNS. for no known reason. The only reliable way to get the network to come back (that I have found) is a full reboot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 27 15:11:34 2016 InstallationDate: Installed on 2015-10-22 (218 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: avahi UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687507] Re: Memory leak (/run file system filling up)
Please provide steps to reproduce the issue. ** Changed in: snapd Status: Invalid => Incomplete ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1687507 Title: Memory leak (/run file system filling up) Status in snapd: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: (see also related discussion on forum: https://forum.snapcraft.io/t/memory-run-memory-file-system-leaking-with-snap-install-remove/429 ) I have a CI system which tests my snap and does a lot install/remove of snap packages as part of the operation on some small virtual systems. My /tmp is 200MB This is on latest Ubuntu Server 16.04 (all packages updated), with the alternative 4.8 kernel from the Ubuntu Repo) At this time, all packages are updated to latest version. I have this bug for a long time (since I've started building up a CI infrastructure for the Snap - approx 6 months ago), so this is not a new bug, but only the more frequent snap testing made it obvious. In my system the /tmp filesystem fills up - within approx 2..7 days I'm out of space on it. All the space is used up under /run/udev/data/ and approx 95% of the files (around 45'000) start with +cgroup prefix I can provide access to a VM in this state if requested (IPv6 only, contact me with SSH key) Here is some current output (not yet out of space... may need another day) root@ci-comp17-dut:~# df Filesystem 1K-blocksUsed Available Use% Mounted on udev 1002892 0 1002892 0% /dev tmpfs 204796 148196 56600 73% /run /dev/vda16060608 3462628 2267076 61% / tmpfs1023976 0 1023976 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock tmpfs1023976 0 1023976 0% /sys/fs/cgroup /dev/loop0 80256 80256 0 100% /snap/core/1577 /dev/loop1 77056 77056 0 100% /snap/core/1337 /dev/loop2 80256 80256 0 100% /snap/core/1441 tmpfs 204796 0204796 0% /run/user/0 /dev/loop3 14592 14592 0 100% /snap/frr/x1 Attached is a full dir output of /run/udev/data (ls_run_udev_data.log) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1687507/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687507] Re: Memory leak (/run file system filling up)
is this leaks from snaps onto host system, generated by mounting/unmounting of snaps? Does snapd insures to close/stop all sessions that are started for each snap? If normal snapd operations result in pam_logind creating sessions which are never ended, and these sessions leak onto the host system, this certainly may result in data leaks. Is this an Ubuntu core or classic system? -- 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/1687507 Title: Memory leak (/run file system filling up) Status in snapd: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: (see also related discussion on forum: https://forum.snapcraft.io/t/memory-run-memory-file-system-leaking-with-snap-install-remove/429 ) I have a CI system which tests my snap and does a lot install/remove of snap packages as part of the operation on some small virtual systems. My /tmp is 200MB This is on latest Ubuntu Server 16.04 (all packages updated), with the alternative 4.8 kernel from the Ubuntu Repo) At this time, all packages are updated to latest version. I have this bug for a long time (since I've started building up a CI infrastructure for the Snap - approx 6 months ago), so this is not a new bug, but only the more frequent snap testing made it obvious. In my system the /tmp filesystem fills up - within approx 2..7 days I'm out of space on it. All the space is used up under /run/udev/data/ and approx 95% of the files (around 45'000) start with +cgroup prefix I can provide access to a VM in this state if requested (IPv6 only, contact me with SSH key) Here is some current output (not yet out of space... may need another day) root@ci-comp17-dut:~# df Filesystem 1K-blocksUsed Available Use% Mounted on udev 1002892 0 1002892 0% /dev tmpfs 204796 148196 56600 73% /run /dev/vda16060608 3462628 2267076 61% / tmpfs1023976 0 1023976 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock tmpfs1023976 0 1023976 0% /sys/fs/cgroup /dev/loop0 80256 80256 0 100% /snap/core/1577 /dev/loop1 77056 77056 0 100% /snap/core/1337 /dev/loop2 80256 80256 0 100% /snap/core/1441 tmpfs 204796 0204796 0% /run/user/0 /dev/loop3 14592 14592 0 100% /snap/frr/x1 Attached is a full dir output of /run/udev/data (ls_run_udev_data.log) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1687507/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687601] Re: package udev 229-4ubuntu17 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
insserv: warning: script 'S80panasoniclpd-init' missing LSB tags and overrides insserv: warning: script 'panasoniclpd-init' missing LSB tags and overrides insserv: There is a loop between service plymouth and procps if started insserv: loop involving service procps at depth 2 insserv: loop involving service udev at depth 1 insserv: Starting panasoniclpd-init depends on plymouth and therefore on system facility `$all' which can not be true! -- 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/1687601 Title: package udev 229-4ubuntu17 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 Status in systemd package in Ubuntu: New Bug description: An error occurred while updating the program. I do not know anything else. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu17 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue May 2 13:51:44 2017 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2016-12-15 (137 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: Hewlett-Packard HP ProBook 4720s ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=a784bf3c-f5a1-4b14-9c07-22b064da1362 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: systemd Title: package udev 229-4ubuntu17 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68AZZ Ver. F.08 dmi.board.name: 1411 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 57.1D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68AZZVer.F.08:bd06/29/2010:svnHewlett-Packard:pnHPProBook4720s:pvr:rvnHewlett-Packard:rn1411:rvrKBCVersion57.1D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4720s dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1687601/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687601] Re: package udev 229-4ubuntu17 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
You appear to have panasoniclpd-init sysv initd script which is malformed and cannot be included as part of the system. Please disable that initd script, and/or correct it. Which package is it installed from? Is it shipped by Ubuntu? -- 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/1687601 Title: package udev 229-4ubuntu17 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 Status in systemd package in Ubuntu: New Bug description: An error occurred while updating the program. I do not know anything else. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu17 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue May 2 13:51:44 2017 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2016-12-15 (137 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: Hewlett-Packard HP ProBook 4720s ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=a784bf3c-f5a1-4b14-9c07-22b064da1362 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: systemd Title: package udev 229-4ubuntu17 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68AZZ Ver. F.08 dmi.board.name: 1411 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 57.1D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68AZZVer.F.08:bd06/29/2010:svnHewlett-Packard:pnHPProBook4720s:pvr:rvnHewlett-Packard:rn1411:rvrKBCVersion57.1D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4720s dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1687601/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687482] Re: -4 flag doesn't work
Without a sophisticated ipv6 setup I tried the most trivial. # ssh ip6-localhost The authenticity of host 'ip6-localhost (::1)' can't be established. [...] root@zesty-test:~# ssh -4 ip6-localhost The authenticity of host 'ip6-localhost (127.0.0.1)' can't be established. As you can see the -4 successfully avoided to use the ipv6 address. What version/release are you running on, any details on your setup that might help to understand? If you could use apport-collect that would add not all (not your setup details), but most other info needed. ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1687482 Title: -4 flag doesn't work Status in openssh package in Ubuntu: Incomplete Bug description: Whenever I use the -4 flag on ssh, it still uses the ipv6 address from dns instead of forcing ipv4 like it says it is supposed to do in the man page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1687482/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687507] Re: Memory leak (/run file system filling up)
expanding on: "looking at the listing" i meant to say, there are only very few related snap bits in there, many are simply from the OS itself including apt updates and the like that are completely unrelated to snaps. -- 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/1687507 Title: Memory leak (/run file system filling up) Status in snapd: Invalid Status in systemd package in Ubuntu: New Bug description: (see also related discussion on forum: https://forum.snapcraft.io/t/memory-run-memory-file-system-leaking-with-snap-install-remove/429 ) I have a CI system which tests my snap and does a lot install/remove of snap packages as part of the operation on some small virtual systems. My /tmp is 200MB This is on latest Ubuntu Server 16.04 (all packages updated), with the alternative 4.8 kernel from the Ubuntu Repo) At this time, all packages are updated to latest version. I have this bug for a long time (since I've started building up a CI infrastructure for the Snap - approx 6 months ago), so this is not a new bug, but only the more frequent snap testing made it obvious. In my system the /tmp filesystem fills up - within approx 2..7 days I'm out of space on it. All the space is used up under /run/udev/data/ and approx 95% of the files (around 45'000) start with +cgroup prefix I can provide access to a VM in this state if requested (IPv6 only, contact me with SSH key) Here is some current output (not yet out of space... may need another day) root@ci-comp17-dut:~# df Filesystem 1K-blocksUsed Available Use% Mounted on udev 1002892 0 1002892 0% /dev tmpfs 204796 148196 56600 73% /run /dev/vda16060608 3462628 2267076 61% / tmpfs1023976 0 1023976 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock tmpfs1023976 0 1023976 0% /sys/fs/cgroup /dev/loop0 80256 80256 0 100% /snap/core/1577 /dev/loop1 77056 77056 0 100% /snap/core/1337 /dev/loop2 80256 80256 0 100% /snap/core/1441 tmpfs 204796 0204796 0% /run/user/0 /dev/loop3 14592 14592 0 100% /snap/frr/x1 Attached is a full dir output of /run/udev/data (ls_run_udev_data.log) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1687507/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome
I am also have the issue of blank screen. I tried a fresh install of Fedora out of curiosity and worked perfect. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1687019 Title: Cannot add a Google account using Online Accounts in Ubuntu Gnome Status in gnome-online-accounts package in Ubuntu: Confirmed Status in gnome-online-accounts package in Arch Linux: New Bug description: With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13 laptop), I cannot add a Google account using Online-Accounts. If I choose to add a new Google account in Online Accounts, a window appears where I can enter my Google email. After entering my email and pressing the Next button, a window appears where I can enter my Google password. After entering the password and pressing the Next button, an empty window appears and nothing else happens. I expected this to show something useful, and actually add the Google account to my Gnome environment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1687019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687601] [NEW] package udev 229-4ubuntu17 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
Public bug reported: An error occurred while updating the program. I do not know anything else. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu17 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue May 2 13:51:44 2017 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2016-12-15 (137 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: Hewlett-Packard HP ProBook 4720s ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=a784bf3c-f5a1-4b14-9c07-22b064da1362 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: systemd Title: package udev 229-4ubuntu17 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68AZZ Ver. F.08 dmi.board.name: 1411 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 57.1D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68AZZVer.F.08:bd06/29/2010:svnHewlett-Packard:pnHPProBook4720s:pvr:rvnHewlett-Packard:rn1411:rvrKBCVersion57.1D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4720s dmi.sys.vendor: Hewlett-Packard ** Affects: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1687601 Title: package udev 229-4ubuntu17 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 Status in systemd package in Ubuntu: New Bug description: An error occurred while updating the program. I do not know anything else. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu17 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue May 2 13:51:44 2017 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2016-12-15 (137 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) MachineType: Hewlett-Packard HP ProBook 4720s ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic root=UUID=a784bf3c-f5a1-4b14-9c07-22b064da1362 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: systemd Title: package udev 229-4ubuntu17 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68AZZ Ver. F.08 dmi.board.name: 1411 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 57.1D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68AZZVer.F.08:bd06/29/2010:svnHewlett-Packard:pnHPProBook4720s:pvr:rvnHewlett-Packard:rn1411:rvrKBCVersion57.1D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4720s dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1687601/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687507] Re: Memory leak (/tmp file system filling up)
looking at the listing as well as the fact that the syslog excerpt on the forum is full of: Apr 28 09:36:48 ci-comp11-dut systemd[1]: Started Session 1816 of user root. this is either a systemd bug or a bug with the way systemd is used in the CI ... moving it to systemd to have a systemd maintainer take a look. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: snapd Status: New => Invalid ** Summary changed: - Memory leak (/tmp file system filling up) + Memory leak (/run file system filling up) -- 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/1687507 Title: Memory leak (/run file system filling up) Status in snapd: Invalid Status in systemd package in Ubuntu: New Bug description: (see also related discussion on forum: https://forum.snapcraft.io/t/memory-run-memory-file-system-leaking-with-snap-install-remove/429 ) I have a CI system which tests my snap and does a lot install/remove of snap packages as part of the operation on some small virtual systems. My /tmp is 200MB This is on latest Ubuntu Server 16.04 (all packages updated), with the alternative 4.8 kernel from the Ubuntu Repo) At this time, all packages are updated to latest version. I have this bug for a long time (since I've started building up a CI infrastructure for the Snap - approx 6 months ago), so this is not a new bug, but only the more frequent snap testing made it obvious. In my system the /tmp filesystem fills up - within approx 2..7 days I'm out of space on it. All the space is used up under /run/udev/data/ and approx 95% of the files (around 45'000) start with +cgroup prefix I can provide access to a VM in this state if requested (IPv6 only, contact me with SSH key) Here is some current output (not yet out of space... may need another day) root@ci-comp17-dut:~# df Filesystem 1K-blocksUsed Available Use% Mounted on udev 1002892 0 1002892 0% /dev tmpfs 204796 148196 56600 73% /run /dev/vda16060608 3462628 2267076 61% / tmpfs1023976 0 1023976 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock tmpfs1023976 0 1023976 0% /sys/fs/cgroup /dev/loop0 80256 80256 0 100% /snap/core/1577 /dev/loop1 77056 77056 0 100% /snap/core/1337 /dev/loop2 80256 80256 0 100% /snap/core/1441 tmpfs 204796 0204796 0% /run/user/0 /dev/loop3 14592 14592 0 100% /snap/frr/x1 Attached is a full dir output of /run/udev/data (ls_run_udev_data.log) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1687507/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1672499] Re: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0.13.15 on armhf
** Also affects: systemd (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Artful) Status: New => Fix Committed -- 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/1672499 Title: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0.13.15 on armhf Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Zesty: New Status in systemd source package in Artful: Fix Committed Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/armhf/s/systemd/20170310_221057_b5cf9@/log.gz root-unittests fails: -> Unit a.service: Description: a.service Instance: n/a Unit Load State: not-found Unit Active State: inactive State Change Timestamp: n/a Inactive Exit Timestamp: n/a Active Enter Timestamp: n/a Activeerror: org.freedesktop.systemd1.NoSuchUnit: Unit c.service not found. Assertion 'r == 0' failed at ../src/test/test-engine.c:62, function main(). Aborting. Exit Timestamp: n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1422795] Re: bash crashes often if inputrc contains revert-all-at-newline
Marking as verification-done again, now that we fixed the build failure on arm64. ** Tags removed: verification-failed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1422795 Title: bash crashes often if inputrc contains revert-all-at-newline Status in bash package in Ubuntu: Fix Released Status in bash source package in Trusty: In Progress Status in bash package in Debian: Fix Released Bug description: Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747341 The Debian bug includes complete reproduction case. Basically: with .inputrc containing set revert-all-at-newline On Go back in the commandline history, edit a command, then submit a different command (may be empty) Such as: $ ls something $ Attached diff is confirmed to fix the issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bash 4.3-7ubuntu1.5 [origin: goobuntu-trusty-testing-desktop] ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Tue Feb 17 15:49:30 2015 SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.bash.bashrc: [modified] mtime.conffile..etc.bash.bashrc: 2015-01-27T03:27:18.751405 [Test Case] Adapted from the Debian bug report: 1. echo "set revert-all-at-newline on" > bug.inputrc 2. INPUTRC=bug.inputrc bash 3. echo hello 4. ^P^U^N^M [Hold down control and type "punm".] Bash should die immediately with SIGABRT. [Regression Potential] Relatively low. The change has no effect at all unless _rl_revert_all_lines() is called, which only happens if revert-all-at-newline is set, and then only when a newline is typed. So, the potential for regression is essentially zero for non-interactive shells and for anyone not using revert-all-at-newline (which is not the default). Further, this change appeared upstream and in both Debian and Ubuntu over a year ago, so it's had plenty of public testing. lib/readline/misc.c:_rl_revert_all_lines() contains a loop which iterates over history entries, reverting changes to each history entry. This patch causes entry->data, which points to the per-entry undo list, to be cleared before reverting edits rather than after. At first glance, this shouldn't make any difference. However, it prevents rl_do_undo() from replacing the history entry with one reflecting the change. Otherwise, the entry gets freed, leaving _rl_revert_all_lines() with an invalid pointer. _Not_ having an invalid pointer and double-free certainly can't be worse than the current situation. Since we're avoiding is making the pointer invalid rather than not doing the free, the chance of a new leak is pretty much nonexistent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1422795/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1644363] Re: [trusty/arm64] binutils segfaults on bash gettext configure test
As we can see in https://launchpad.net/ubuntu/+source/bash/4.3-7ubuntu1.6/+build/11220608, the bash package built successfully with this new binutils: Get:51 http://ftpmaster.internal/ubuntu/ trusty-proposed/main binutils arm64 2.24-5ubuntu14.2 [1050 kB] thus marking as verification-done. ** 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 binutils in Ubuntu. https://bugs.launchpad.net/bugs/1644363 Title: [trusty/arm64] binutils segfaults on bash gettext configure test Status in binutils package in Ubuntu: Invalid Status in eglibc package in Ubuntu: Invalid Status in binutils source package in Trusty: Fix Committed Status in eglibc source package in Trusty: Invalid Bug description: On arm64, the bash gettext configure test causes binutils to segv: configure:8453: gcc -o conftest -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror= format-security -Wall -D_FORTIFY_SOURCE=2 -Wl,-Bsymbolic-functions -Wl,-z,relro -static conftest.c >&5 conftest.c: In function 'main': conftest.c:116:8: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + *_nl_domain_bindings ^ conftest.c:116:29: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] return (int) gettext ("") + (int) ngettext ("", "", 0) + _nl_msg_cat_cntr + *_nl_domain_bindings ^ collect2: error: ld terminated with signal 11 [Segmentation fault], core dumped configure:8453: $? = 1 configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "bash" | #define PACKAGE_TARNAME "bash" | #define PACKAGE_VERSION "4.3-release" | #define PACKAGE_STRING "bash 4.3-release" | #define PACKAGE_BUGREPORT "bug-b...@gnu.org" | #define PACKAGE_URL "" | #define ALIAS 1 | #define PUSHD_AND_POPD 1 | #define RESTRICTED_SHELL 1 | #define PROCESS_SUBSTITUTION 1 | #define PROMPT_STRING_DECODE 1 | #define SELECT_COMMAND 1 | #define HELP_BUILTIN 1 | #define ARRAY_VARS 1 | #define DPAREN_ARITHMETIC 1 | #define BRACE_EXPANSION 1 | #define COMMAND_TIMING 1 | #define EXTENDED_GLOB 1 | #define EXTGLOB_DEFAULT 0 | #define COND_COMMAND 1 | #define COND_REGEXP 1 | #define COPROCESS_SUPPORT 1 | #define ARITH_FOR_COMMAND 1 | #define NETWORK_REDIRECTIONS 1 | #define PROGRAMMABLE_COMPLETION 1 | #define DEBUGGER 1 | #define CASEMOD_ATTRS 1 | #define CASEMOD_EXPANSIONS 1 | #define GLOBASCII_DEFAULT 0 | #define MEMSCRAMBLE 1 | #define STDC_HEADERS 1 | #define HAVE_SYS_TYPES_H 1 | #define HAVE_SYS_STAT_H 1 | #define HAVE_STDLIB_H 1 | #define HAVE_STRING_H 1 | #define HAVE_MEMORY_H 1 | #define HAVE_STRINGS_H 1 | #define HAVE_INTTYPES_H 1 | #define HAVE_STDINT_H 1 | #define HAVE_UNISTD_H 1 | #define __EXTENSIONS__ 1 | #define _ALL_SOURCE 1 | #define _GNU_SOURCE 1 | #define _POSIX_PTHREAD_SEMANTICS 1 | #define _TANDEM_SOURCE 1 | #define READLINE 1 | #define HISTORY 1 | #define BANG_HISTORY 1 | #define _GNU_SOURCE 1 | #define HAVE_STRINGIZE 1 | #define HAVE_LONG_DOUBLE_WIDER 1 | #define HAVE_LONG_DOUBLE 1 | #define PROTOTYPES 1 | #define __PROTOTYPES 1 | #define restrict __restrict | #define HAVE_ALLOCA_H 1 | #define HAVE_ALLOCA 1 | #define HAVE_STDLIB_H 1 | #define HAVE_UNISTD_H 1 | #define HAVE_SYS_PARAM_H 1 | #define HAVE_SYS_TIME_H 1 | #define HAVE_GETPAGESIZE 1 | #define HAVE_MMAP 1 | #define INTDIV0_RAISES_SIGFPE 0 | #define HAVE_INTTYPES_H_WITH_UINTMAX 1 | #define HAVE_STDINT_H_WITH_UINTMAX 1 | #define HAVE_UNSIGNED_LONG_LONG 1 | #define HAVE_UINTMAX_T 1 | #define HAVE_INTTYPES_H 1 | #define HAVE_ARGZ_H 1 | #define HAVE_LIMITS_H 1 | #define HAVE_LOCALE_H 1 | #define HAVE_NL_TYPES_H 1 | #define HAVE_MALLOC_H 1 | #define HAVE_STDDEF_H 1 | #define HAVE_STDLIB_H 1 | #define HAVE_STRING_H 1 | #define HAVE_UNISTD_H 1 | #define HAVE_SYS_PARAM_H 1 | #define HAVE_FEOF_UNLOCKED 1 | #define HAVE_FGETS_UNLOCKED 1 | #define HAVE_GETC_UNLOCKED 1 | #define HAVE_GETCWD 1 | #define HAVE_GETEGID 1 | #define HAVE_GETEUID 1 | #define HAVE_GETGID 1 | #define HAVE_GETUID 1 | #define HAVE_MEMPCPY 1 | #define HAVE_MUNMAP 1 | #define HAVE_PUTENV 1 | #define HAVE_SETENV 1 | #define HAVE_SETLOCALE 1 | #define HAVE_LOCALECONV 1 | #define HAVE_STPCPY 1 | #define HAVE_STRCASECMP 1 | #define HAVE_STRDUP 1 | #define HAVE_STRTOUL 1 | #define HAVE_TSEARCH 1 | #define HAVE___ARGZ_COUNT 1 | #define HAVE___ARGZ_STRINGIFY 1 | #define HAVE___ARGZ_NEXT 1 | #define HAVE___FSETLOCKING 1 | #define HAVE_ICONV 1 | #define ICONV_CONST | #define HAVE_LANGINFO_CODESET 1 | #define HAVE_LC_MESSAGES 1 | /* end confdefs.h. */ | #include | extern int _nl_m
[Touch-packages] [Bug 1240336] Re: After release upgrade, the user looses permissions for several basic actions in the system
Actually, it works for installing packages from software center (auth dialog appears), still fails silently sometimes (for example when I try to remove software source PPA). I also created a new admin user, by running sudo gnome-control-center -> Users & Groups. For that user everything works fine. This appears to be a recurring bug which has been reported on Launchpad back in 2013. Every version of ubuntu since is affected by this but not everyone sees the error. On the moment I write this (march 2015) there's no permanent solution, however there are workarounds to solve the problem. For Ubuntu 14.10 the problem appears to be related to the package ulatencyd. Removing this package causes the error to disappear in my situation. If I recall correctly I've installed this package manually on a certain moment in time so it does not belong to a standard install and therefore this might not affect everyone. -- 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/1240336 Title: After release upgrade, the user looses permissions for several basic actions in the system Status in gdm package in Ubuntu: Triaged Status in lightdm package in Ubuntu: Triaged Status in lxdm package in Ubuntu: Triaged Status in policykit-desktop-privileges package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE: - Upgrade Ubuntu to the next release. RESULT: - The user looses permissions for several basic actions in the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-desktop-privileges UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1240336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686189] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1686189 Title: External monitor connecting problem Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 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.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 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: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
This breaks domain name resolution in Ubuntu 16.04, as seen in bug #1522057. tags: added: precise xenial Changed in network-manager (Ubuntu): importance: Medium → Critical Changed in dnsmasq (Ubuntu Precise): importance: Medium → Critical Changed in dnsmasq (Ubuntu): importance: Medium → Critical Changed in network-manager (Ubuntu Precise): importance: Medium → Critical Changed in network-manager (Ubuntu): status: Confirmed → Invalid Changed in network-manager (Ubuntu Precise): status: Triaged → Invalid Changed in dnsmasq (Ubuntu): status: Confirmed → Triaged Changed in dnsmasq (Ubuntu Precise): status: Confirmed → Triaged ** Changed in: dnsmasq (Ubuntu) Assignee: sunil (chikkalli) => nikhil (nikhilnikki) -- 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/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers Status in dnsmasq package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Invalid Status in dnsmasq source package in Precise: Triaged Status in network-manager source package in Precise: Invalid Status in dnsmasq package in Debian: New Bug description: A number of reports already filed against network-manager seem to reflect this problem, but to make things very clear I am opening a new report. Where appropriate I will mark other reports as duplicates of this one. Consider a pre-Precise system with the following /etc/resolv.conf: nameserver 192.168.0.1 nameserver 8.8.8.8 The first address is the address of a nameserver on the LAN that can resolve both private and public domain names. The second address is the address of a nameserver on the Internet that can resolve only public names. This setup works fine because the GNU resolver always tries the first- listed address first. Now the administrator upgrades to Precise and instead of writing the above to resolv.conf, NetworkManager writes server=192.168.0.1 server=8.8.8.8 to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to resolv.conf. Resolution of private domain names is now broken because dnsmasq treats the two upstream nameservers as equals and uses the faster one, which could be 8.8.8.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686361] Re: systemd does not respect nofile ulimit when running in container
** Changed in: systemd (Ubuntu Artful) Status: Confirmed => Fix Committed -- 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/1686361 Title: systemd does not respect nofile ulimit when running in container Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: New Status in systemd source package in Yakkety: New Status in systemd source package in Zesty: New Status in systemd source package in Artful: Fix Committed Bug description: When systemd currently starts in a container that has RLIMIT_NOFILE set to e.g. 10 systemd will lower it to 65536 since this value is hard-coded into systemd. I've pushed a patch to systemd upstream that will try to set the nofile limit to the allowed kernel maximum. If this fails, it will compute the minimum of the current set value (the limit that is set on the container) and the maximum value as soft limit and the currently set maximum value as the maximum value. This way it retains the limit set on the container. It would be great if we could backport this patch to have system adhere to nofile limits set for the container. This is especially important since user namespaces will allow you to lower the limit but not raise it back up afterwards. The upstream patch is appended. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1686361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686189] Re: External monitor connecting problem
I have this problem since linux-image-4.4.0-75 linux-image-4.4.0-77 is also affected. linux-image-4.4.0-72 works ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1686189 Title: External monitor connecting problem Status in linux package in Ubuntu: New Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 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.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 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: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
another solution is to resolve 192.168.0.1 code it as server=/sample.com/192.168.0.1 which would send all dns lookups for sample.com to 192.168.0.1. -- 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/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers Status in dnsmasq package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Invalid Status in dnsmasq source package in Precise: Triaged Status in network-manager source package in Precise: Invalid Status in dnsmasq package in Debian: New Bug description: A number of reports already filed against network-manager seem to reflect this problem, but to make things very clear I am opening a new report. Where appropriate I will mark other reports as duplicates of this one. Consider a pre-Precise system with the following /etc/resolv.conf: nameserver 192.168.0.1 nameserver 8.8.8.8 The first address is the address of a nameserver on the LAN that can resolve both private and public domain names. The second address is the address of a nameserver on the Internet that can resolve only public names. This setup works fine because the GNU resolver always tries the first- listed address first. Now the administrator upgrades to Precise and instead of writing the above to resolv.conf, NetworkManager writes server=192.168.0.1 server=8.8.8.8 to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to resolv.conf. Resolution of private domain names is now broken because dnsmasq treats the two upstream nameservers as equals and uses the faster one, which could be 8.8.8.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 7415] Re: Segmentation fault in 'sshd'
Subject: The kernel version is the problem Rudresh, I think the problem you are facing is dependent on the kernel version. Try using different kernel version. I've heard of a problem between vmware and the kernel(the version which you are using now). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/7415 Title: Segmentation fault in 'sshd' Status in openssh package in Ubuntu: Invalid Status in openssh package in Debian: Incomplete Bug description: Automatically imported from Debian bug report #265348 http://bugs.debian.org/265348 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/7415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp