[Touch-packages] [Bug 1025388] Re: Internal mic stops working when plugging in headphones
Same issue as #17, when I connect my headphone with combo jack (works great with other devices) to laptop with ubuntu 16.04. In PulseAudio volume control gui, in 'Input devices' tab, it shows that internal microphone is 'unplugged' and microphone (external, from combo headset) is 'plugged in'. But it does not work! So as I find out that the combo headset clearly does not work due to lack of drivers, there should be a workaround to let users use the internal mic instead. PS: This issue has been for 5 long year (see #1 above), somebody please do something. If we have commonplace headset with combo jack and and recent laptops with combo port, we evidently can't use ubuntu for video chatting. That's quite a downfall. -- 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/1025388 Title: Internal mic stops working when plugging in headphones Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO 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:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1025388/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 997331] Re: Some ALSA applications play bad sound
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/997331 Title: Some ALSA applications play bad sound Status in pulseaudio package in Ubuntu: Expired Bug description: Some applications using ALSA plays bad sound. One is WINE applications. Winecfg test sound is distorted (sounds awful). Spotify running WINE plays songs way too fast. A flash based program play distorted sound. The common thing for all of them is that under Applications in Sound settings it says alsa-plugin and it flashes very rapidly between "No application is currently playing" and alsa-plugin. It almost looks like flickering. I've testet a normal wave file using aplay and that was okey, no problems. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: oeriksen 3299 F pulseaudio /dev/snd/controlC0: oeriksen 3299 F pulseaudio /dev/snd/controlC1: oeriksen 3299 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xfa40 irq 60' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,10438410,00100302' Controls : 41 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'Socialize'/'Creative Labs VF0640 Live! Cam Socialize at usb-:00:1d.0-1.4, high speed' Mixer name : 'USB Mixer' Components : 'USB041e:4083' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 48 Mono: Capture 45 [94%] [18.00dB] [on] Card2.Amixer.info: Card hw:2 'NVidia'/'HDA NVidia at 0xfa08 irq 17' Mixer name : 'Nvidia GPU 16 HDMI/DP' Components : 'HDA:10de0016,10de0101,00100100' Controls : 24 Simple ctrls : 4 Date: Wed May 9 22:41:04 2012 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [System Product Name, Realtek ALC892, Green Line Out, Rear] Playback problem UpgradeStatus: Upgraded to precise on 2012-03-02 (68 days ago) dmi.bios.date: 02/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8P67 REV 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2302:bd02/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8P67REV3.1:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/997331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1692276] Re: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
[Expired for iproute2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: iproute2 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1692276 Title: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in iproute2 package in Ubuntu: Expired Bug description: just can't install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iproute2 4.3.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat May 20 21:53:21 2017 DuplicateSignature: package:iproute2:4.3.0-1ubuntu3 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package iproute2 (--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 2017-05-15 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: iproute2 Title: package iproute2 4.3.0-1ubuntu3 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/iproute2/+bug/1692276/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1692217] Re: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: el paquete iproute2 no está listo para configurarse no se puede configurar (estado actual `half-installed
[Expired for iproute2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: iproute2 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1692217 Title: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: el paquete iproute2 no está listo para configurarse no se puede configurar (estado actual `half-installed') Status in iproute2 package in Ubuntu: Expired Bug description: estaba actualisando ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iproute2 4.3.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat May 20 07:26:41 2017 ErrorMessage: el paquete iproute2 no está listo para configurarse no se puede configurar (estado actual `half-installed') InstallationDate: Installed on 2017-05-17 (2 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: iproute2 Title: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: el paquete iproute2 no está listo para configurarse no se puede configurar (estado actual `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1692217/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704422] Re: systemd-resolved keeps swapping DNS servers and breaking name resolution
Found out it's related to some occasional packet loss. Why this happens, I'm not sure, but appears to be more related to the wireless kernel mod than systemd in this case. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1704422 Title: systemd-resolved keeps swapping DNS servers and breaking name resolution Status in systemd package in Ubuntu: Invalid Bug description: Hi, I think the name is self explanatory, let me paste some logs of what does my syslog look like at any given time: https://paste.ubuntu.com/25089356/ Jul 14 16:49:23 Tuxedo systemd-resolved[1120]: Using system hostname 'Tuxedo'. Jul 14 16:49:52 Tuxedo systemd-resolved[1120]: Switching to fallback DNS server 8.8.8.8. Jul 14 16:50:17 Tuxedo systemd-resolved[1120]: Switching to fallback DNS server 8.8.4.4. Jul 14 16:50:17 Tuxedo systemd-resolved[1120]: Switching to fallback DNS server 2001:4860:4860::. Jul 14 16:50:17 Tuxedo systemd-resolved[1120]: Switching to fallback DNS server 2001:4860:4860::8844. Jul 14 16:50:18 Tuxedo systemd-resolved[1120]: Switching to fallback DNS server 8.8.8.8. Jul 14 16:50:18 Tuxedo systemd-resolved[1120]: Switching to fallback DNS server 8.8.4.4. Jul 14 16:50:18 Tuxedo systemd-resolved[1120]: Using degraded feature set (UDP+EDNS0+DO) for DNS server 8.8.4.4. Jul 14 16:50:18 Tuxedo systemd-resolved[1120]: Switching to fallback DNS server 2001:4860:4860::. Jul 14 16:50:19 Tuxedo systemd-resolved[1120]: Switching to fallback DNS server 2001:4860:4860::8844. (...) Jul 14 16:50:43 Tuxedo systemd-resolved[1120]: Using degraded feature set (UDP+EDNS0+DO) for DNS server 78.46.223.24. Jul 14 16:50:43 Tuxedo systemd-resolved[1120]: Switching to DNS server 162.242.211.137 for interface tun0. Jul 14 16:50:44 Tuxedo systemd-resolved[1120]: Switching to DNS server 78.46.223.24 for interface tun0. Jul 14 16:50:45 Tuxedo systemd-resolved[1120]: Switching to DNS server 162.242.211.137 for interface tun0. Jul 14 16:50:48 Tuxedo systemd-resolved[1120]: Switching to DNS server 78.46.223.24 for interface tun0. Jul 14 16:50:48 Tuxedo systemd-resolved[1120]: Switching to DNS server 162.242.211.137 for interface tun0. Jul 14 16:50:49 Tuxedo systemd-resolved[1120]: Switching to DNS server 78.46.223.24 for interface tun0. Jul 14 16:50:50 Tuxedo systemd-resolved[1120]: Switching to DNS server 162.242.211.137 for interface tun0. Jul 14 16:50:50 Tuxedo systemd-resolved[1120]: Switching to DNS server 78.46.223.24 for interface tun0. This happens both over the VPN and without (only than without the VPN I don't get the log messages, just a huge packet loss): tux@Tuxedo:~$ ping google.es ^T192PING google.es (216.58.201.131) 56(84) bytes of data. 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=1 ttl=55 time=26.9 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=5 ttl=55 time=19.5 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=9 ttl=55 time=24.4 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=10 ttl=55 time=22.3 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=14 ttl=55 time=20.5 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=20 ttl=55 time=20.7 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=22 ttl=55 time=26.4 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=24 ttl=55 time=29.2 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=25 ttl=55 time=20.1 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=26 ttl=55 time=22.7 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=27 ttl=55 time=21.0 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=28 ttl=55 time=30.4 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=29 ttl=55 time=23.2 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=30 ttl=55 time=29.1 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=37 ttl=55 time=30.1 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=40 ttl=55 time=24.8 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=43 ttl=55 time=23.3 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=45 ttl=55 time=22.9 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=46 ttl=55 time=21.9 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=53 ttl=55 time=23.7 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=61 ttl=55 time=21.1 ms 64 bytes from mad06s25-in-f3.1e100.net (216.58.201.131): icmp_seq=62 ttl=55 time=19.3 ms ^C --- google.es ping
[Touch-packages] [Bug 1692981] Re: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config
Thanks, problem solved. ** Changed in: openssl (Ubuntu) Status: Confirmed => Fix Released ** Changed in: dpkg (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1692981 Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in dpkg package in Ubuntu: Fix Released Status in openssl package in Ubuntu: Fix Released Bug description: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: libssl1.0.0:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue May 23 21:47:55 2017 DuplicateSignature: package:libssl-dev:amd64:1.0.2g-1ubuntu11.2 Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ... dpkg: error processing package libssl-dev: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 2017-05-15 (7 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: openssl Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1692981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705800] [NEW] Error message appears at startup
Public bug reported: [ 2.231153] nouveau :01:00.0: bus: MMIO read of FAULT at 3e6684 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 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: Sat Jul 22 00:58:12 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GM107 [GeForce GTX 750 Ti] [3842:3753] InstallationDate: Installed on 2017-07-21 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=73638941-2a1f-4419-940b-ee07b54dce2b ro locale=pt_BR quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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 N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Jul 22 00:55:55 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMOSART Semi. 2.4G RF Keyboard & Mouse KEYBOARD, id 8 inputMOSART Semi. 2.4G RF Keyboard & Mouse KEYBOARD, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 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/1705800 Title: Error message appears at startup Status in xorg package in Ubuntu: New Bug description: [ 2.231153] nouveau :01:00.0: bus: MMIO read of FAULT at 3e6684 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 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: Sat Jul 22 00:58:12 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GM107 [GeForce GTX 750 Ti] [3842:3753] InstallationDate: Installed on 2017-07-21 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=73638941-2a1f-4419-940b-ee07b54dce2b ro locale=pt_BR quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK
[Touch-packages] [Bug 1703866] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: debconf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1703866 Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 Status in debconf package in Ubuntu: Confirmed Status in openssl package in Ubuntu: Confirmed Bug description: Was just trying to upgrade from 14.04 to 16.04 and the installer reported that issue and asked me to fill this... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.24 Architecture: amd64 Date: Tue Jul 11 17:05:23 2017 DuplicateSignature: package:libssl1.0.0:amd64:1.0.2g-1ubuntu4.8:subprocess installed post-installation script returned error exit status 255 ErrorMessage: subprocess installed post-installation script returned error exit status 255 InstallationDate: Installed on 2013-09-06 (1404 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssl Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 UpgradeStatus: Upgraded to xenial on 2017-07-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1703866/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703866] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openssl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1703866 Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 Status in debconf package in Ubuntu: Confirmed Status in openssl package in Ubuntu: Confirmed Bug description: Was just trying to upgrade from 14.04 to 16.04 and the installer reported that issue and asked me to fill this... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.24 Architecture: amd64 Date: Tue Jul 11 17:05:23 2017 DuplicateSignature: package:libssl1.0.0:amd64:1.0.2g-1ubuntu4.8:subprocess installed post-installation script returned error exit status 255 ErrorMessage: subprocess installed post-installation script returned error exit status 255 InstallationDate: Installed on 2013-09-06 (1404 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssl Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 UpgradeStatus: Upgraded to xenial on 2017-07-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1703866/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
I opened a PR upstream with the proposed fix and also prepared a backport for Xenial in this PPA: https://launchpad.net/~rbalint/+archive/ubuntu/scratch The PPA has a build for Artful, too. PR: https://github.com/mvo5/unattended-upgrades/pull/64 -- 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/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686803] Re: sudo returns exit code 0 if child is killed with SIGTERM
Verified sudo_1.8.16-0ubuntu3.3_amd64.deb fixes the bug on yakkety. ** Tags removed: verification-needed-yakkety ** Tags added: verification-done-yakkety ** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1686803 Title: sudo returns exit code 0 if child is killed with SIGTERM Status in sudo: Unknown Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Xenial: Fix Committed Status in sudo source package in Yakkety: Fix Committed Status in sudo source package in Zesty: Fix Committed Status in sudo source package in Artful: Fix Released Bug description: [Impact] * sudo returns exit code 0 if child is killed with signals other than SIGINT * This can break scripts assuming successful execution of the command ran by sudo [Test Case] * Open two separate shells 1. In shell 1. run: ubuntu@tough-calf:~$ sudo sleep 300; echo $? 2. In shell 2. run: root@tough-calf:~# killall -TERM sleep 3. In broken versions shell 1. shows this: ubuntu@tough-calf:~$ sudo sleep 300; echo $? 0 4. Install fixed version 5. Execute steps 1. and 2. 6. In fixed version shell 1. shows this: ubuntu@tough-calf:~$ sudo sleep 300; echo $? Terminated 143 [Regression Potential] * sudo may exit with a different status than expected [Other Info] original bug description: Please backport upstream sudo changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the" to xenial, yakkety, and zesty versions of sudo. This will fix a regression documented by this upstream bug report: https://bugzilla.sudo.ws/show_bug.cgi?id=784 sudo 1.8.15 changeset 10229:153f016db8f1 "When the command sudo is running is killed by a signal, sudo will" introduced a regression where the exit status is always 0 when a command is killed by a signal other than SIGINT. https://www.sudo.ws/repos/sudo/rev/153f016db8f1 This will be fixed in sudo 1.8.20 with changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the". https://www.sudo.ws/repos/sudo/rev/50b988d0c97f trusty sudo is based off sudo 1.8.9 and is not affected. xenial sudo based off sudo 1.8.16, yaketty sudo based off sudo 1.8.16, and zesty sudo based off 1.8.19 need the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/sudo/+bug/1686803/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686803] Re: sudo returns exit code 0 if child is killed with SIGTERM
Verified sudo_1.8.19p1-1ubuntu1.2_amd64.deb fixes the bug on zesty. ** Tags removed: verification-needed-zesty ** Tags added: verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1686803 Title: sudo returns exit code 0 if child is killed with SIGTERM Status in sudo: Unknown Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Xenial: Fix Committed Status in sudo source package in Yakkety: Fix Committed Status in sudo source package in Zesty: Fix Committed Status in sudo source package in Artful: Fix Released Bug description: [Impact] * sudo returns exit code 0 if child is killed with signals other than SIGINT * This can break scripts assuming successful execution of the command ran by sudo [Test Case] * Open two separate shells 1. In shell 1. run: ubuntu@tough-calf:~$ sudo sleep 300; echo $? 2. In shell 2. run: root@tough-calf:~# killall -TERM sleep 3. In broken versions shell 1. shows this: ubuntu@tough-calf:~$ sudo sleep 300; echo $? 0 4. Install fixed version 5. Execute steps 1. and 2. 6. In fixed version shell 1. shows this: ubuntu@tough-calf:~$ sudo sleep 300; echo $? Terminated 143 [Regression Potential] * sudo may exit with a different status than expected [Other Info] original bug description: Please backport upstream sudo changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the" to xenial, yakkety, and zesty versions of sudo. This will fix a regression documented by this upstream bug report: https://bugzilla.sudo.ws/show_bug.cgi?id=784 sudo 1.8.15 changeset 10229:153f016db8f1 "When the command sudo is running is killed by a signal, sudo will" introduced a regression where the exit status is always 0 when a command is killed by a signal other than SIGINT. https://www.sudo.ws/repos/sudo/rev/153f016db8f1 This will be fixed in sudo 1.8.20 with changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the". https://www.sudo.ws/repos/sudo/rev/50b988d0c97f trusty sudo is based off sudo 1.8.9 and is not affected. xenial sudo based off sudo 1.8.16, yaketty sudo based off sudo 1.8.16, and zesty sudo based off 1.8.19 need the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/sudo/+bug/1686803/+subscriptions -- Mailing list: https://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 1705551] Re: close lid suspends correctly and wakealarm resumes from suspend to run cron jobs but opening lid reveals no display
Sorry, I forgot to make a correction to my [Additional Information] which I re-tested. After my cron backup job is finished it will check if the lid is closed. If it is closed then it will run pm-suspend. If I then open the lid, the laptop resumes without a normal working display. So pm-suspend suspended the laptop without a display and the next time I open the lid the laptop resumes without a display. Thanks, Pierre On Fri, Jul 21, 2017 at 4:04 PM, Pierre Fortierwrote: > Hi, > > With regards to "FN keys", I tried all the FN keys and Ctrl+Alt+FN keys > and Esc and many others but nothing worked. > > With regards to "never close the lid, but suspend via SW", (1) while in > xfce account I ran sudo pm-suspend which suspended the laptop and (2) I > then pressed the shift key and the laptop resumed normally with a working > display. I repeated this with a remote ssh login into the laptop and it > also worked perfectly. > > With regards to "xset dpms force off", when I do a remote ssh login into > the laptop which resumed from wakealarm and has no display, I don't see a > DISPLAY environment variable. When I execute "sudo -u bierre env DISPLAY=:0 > /usr/bin/xrandr --auto", the system reports: > > No protocol specified > Can't open display :0 > > I don't know if I am remotely executing this command correctly. > Furthermore, I don't know how to reach xorg to execute "xset dpms force > off". > > Thanks, > Pierre > > > On Fri, Jul 21, 2017 at 3:50 AM, ChristianEhrhardt < > 1705...@bugs.launchpad.net> wrote: > >> Hi, >> you said "all sorts of keyboard combinations" but maybe it is worth a >> try. I had a similar case where it actually enabled the display, but at >> brightness 0 - you might not accidentally have the same case? I could get >> it on by using the FN keys to increase brightness in those cases. >> >> Another question would be if you never close the lid, but suspend via SW. >> And next day you wakeup via the alarm (while the lid was still open when >> sleeping) - is it then waking up normally with display enabled? >> >> Finally - I beg your pardon as I'm not an expert on this - but the >> following could enable it. >> You might need tweaks to actually "reach" your xorg, but I'm sure you can >> do that. Once you did call: >> $ xset dpms force off >> That should disable the power saving blank that your screen is in. >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1705551 >> >> Title: >> close lid suspends correctly and wakealarm resumes from suspend to run >> cron jobs but opening lid reveals no display >> >> Status in pm-utils package in Ubuntu: >> Incomplete >> >> Bug description: >> [Problem] >> >> When I close the laptop lid, pm-action runs the following code which I >> have added: >> >> sh -c "echo 0 > /sys/class/rtc/rtc0/wakealarm" # clear alarm >> sh -c "echo `date '+%s' -d '7am next day + 30 minutes'` > >> /sys/class/rtc/rtc0/wakealarm" # set alarm >> >> and then suspends. At 7:30 AM the next day, the laptop resumes from >> suspend with the lid closed and executes cron jobs (e.g. some >> backups). If I open the lid then there is no display. I tried several >> options to resume the display: >> >> - [FAILS] all sorts of keyboard combinations >> - [FAILS] ssh -X into laptop and execute "sudo -u bierre env DISPLAY=:0 >> /usr/bin/xrandr --auto" (n.b. when I run "sudo -u bierre env" there is no >> DISPLAY variable) >> - [MANUAL HACK] closing the lid causes the laptop to suspend and then >> opening the lid causes it to resume with a normal working display >> >> I would like a solution or SOFTWARE HACK which I could add to /usr/lib >> /pm-utils/sleep.d/99video during resume from suspend triggered by >> wakealarm so that opening the lid would reveal a working display. >> >> [Laptop System Information] >> >> laptop = MacBookPro5,5 >> pm-utils version = 1.4.1-13ubuntu0.2 >> kernel = Linux version 3.19.0-32-generic (buildd@lgw01-43) (gcc >> version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #37~14.04.1-Ubuntu SMP Thu Oct 22 >> 09:41:40 UTC 2015 >> OS = "Linux Mint 17.3 Rosa" based on "14.04.3 LTS, Trusty Tahr" >> desktop environment = XFCE >> video card = NVIDIA Corporation C79 [GeForce 9400M] (rev b1) (prog-if >> 00 [VGA controller]) >> video driver = [633938.944] (II) NOUVEAU(0): Output LVDS-1 >> >> [Additional Information] >> >> After my cron backup job is finished it will check if the lid is >> closed. If it is closed then it will run pm-suspend. If I then open >> the lid, the laptop resumes with a normal working display. So the >> problem of no visible display occurs only when I open the lid after >> resume from wakealarm and before the backup job suspends the laptop. >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1705 >> 551/+subscriptions >> > > -- You received this bug
[Touch-packages] [Bug 1705595] Re: g_unix_signal_source_new does not support SIGWINCH
The attachment "add-sigwinch.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1705595 Title: g_unix_signal_source_new does not support SIGWINCH Status in glib2.0 package in Ubuntu: New Bug description: This is a request for upstream #769534 (https://bugzilla.gnome.org/show_bug.cgi?id=769534) to be incorporated into Xenial. It is a one-line change, and was incorporated in 2.53.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1705595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1692981] Re: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config
I had a slightly different issue but the solution was very similar. When I ran the dpkg command it didn't list any bad packages, though when I updated it still told me there was a package in a very bad state. I used: sudo apt-get install --reinstall libssl1.0.0:i386 (this was listed in my term.log file as bad) and now everything is updating/installing properly. I'm running Ubuntu 16.04 on an intel dual core i7. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1692981 Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in dpkg package in Ubuntu: Confirmed Status in openssl package in Ubuntu: Confirmed Bug description: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: libssl1.0.0:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue May 23 21:47:55 2017 DuplicateSignature: package:libssl-dev:amd64:1.0.2g-1ubuntu11.2 Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ... dpkg: error processing package libssl-dev: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 2017-05-15 (7 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: openssl Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1692981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1696814] Re: add openjdk hs log to list of acceptable_fields in whoopsie
Import notes about running the testcase in Xenial and Zesty: 1. OpenJDK 8 has not yet been released with the apport hook on Xenial and Zesty; I copied the source_openjdk-8.py hook file from the apport package-hooks directory from OpenJDK 8 in artful to the right place in order to test it in Xenial and Zesty. 2. The HotspotError key was present in all cases when viewing the report with the apport-cli tool, as expected, and whoopsie *without* the fix ignored the key and didn't upload it, also as expected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1696814 Title: add openjdk hs log to list of acceptable_fields in whoopsie Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Xenial: Fix Committed Status in whoopsie source package in Zesty: Fix Committed Bug description: [Impact] By default OpenJDK 8 generates an hs_err file when it crashes, this file contains the stacktrace generated by OpenJDK (thus it contains different data compared to a gdb stacktrace) plus information on the running threads, classes, and memory usage (OpenJDK's regions). This file is usually required by the OpenJDK and/or IcedTea upstream developers when filling a bug and, in the case of OpenJDK, is more useful than the incomplete stacktrace that GDB can generate from OpenJDK crashes. OpenJDK 8 now includes a new apport hook to collect additional data from crash reports as well as the hs_err log file (in the new HotspotError key). A new release is soon reaching Zesty and Xenial with the hook included and without SRU'ing this fix the hs_err file won't be uploaded to the error tracker. [Test Case] Make sure that you are using OpenJDK 8 and to stop whoopsie service before continuing. If any popup about submitting a crash report shows up at any time, ignore/cancel it - we are going to manually submit the report to the staging error tracker (instead of the official one). # SleepTest.java public class SleepTest { public static void main(String[] args) throws Exception { Thread.sleep(5000); } } 1. Run whoopsie: $ sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f 2. Run the SleepTest and SIGKILL it in another terminal: $ java SleepTest & sleep 1 && pkill -f -SIGILL "java SleepTest" 3. View the crash report and submit it: $ apport-cli -c report /var/crash/_usr_lib_jvm_java-8-openjdk-amd64_jre_bin_java.1000.crash 3a) View the report 3b) [Optional] Search for the "HotspotError" key 3c) Send the report 4. Verify that the report was saved, including the hs_err content: 4a) In whoopsie terminal, check the OOPS ID code 4b) Browse to errors.staging.ubuntu.com/oops/$OOPSID 4c) Confirm that the HotspotError was added to the report [Regression Potential] If the new key is added to acceptable_fields whoopsie will upload the entries in it. Currently the OpenJDK apport hook limits this to 100 KB, but changes to it could allow bigger files with in turn cause an overhead in the error tracker infrastructure. [Original bug report] OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to a Crash report under the HotspotError key. The hook is currently limited to attaching files under 100 KB. Please add HotspotError key to the whitelist in order for it to be available in error tracker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1696814] Re: add openjdk hs log to list of acceptable_fields in whoopsie
Results from the testcase in Zesty: - current whoopsie 0.2.55: no HotspotError (as expected) https://errors.staging.ubuntu.com/oops/90d56bae-6e50-11e7-8a18-fa163eaf9b83 - proposed whoopsie 0.2.55.1: HotspotError is present (as expected) https://errors.staging.ubuntu.com/oops/3e464710-6e4f-11e7-8a18-fa163eaf9b83 ** Tags removed: verification-needed-zesty ** Tags added: verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1696814 Title: add openjdk hs log to list of acceptable_fields in whoopsie Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Xenial: Fix Committed Status in whoopsie source package in Zesty: Fix Committed Bug description: [Impact] By default OpenJDK 8 generates an hs_err file when it crashes, this file contains the stacktrace generated by OpenJDK (thus it contains different data compared to a gdb stacktrace) plus information on the running threads, classes, and memory usage (OpenJDK's regions). This file is usually required by the OpenJDK and/or IcedTea upstream developers when filling a bug and, in the case of OpenJDK, is more useful than the incomplete stacktrace that GDB can generate from OpenJDK crashes. OpenJDK 8 now includes a new apport hook to collect additional data from crash reports as well as the hs_err log file (in the new HotspotError key). A new release is soon reaching Zesty and Xenial with the hook included and without SRU'ing this fix the hs_err file won't be uploaded to the error tracker. [Test Case] Make sure that you are using OpenJDK 8 and to stop whoopsie service before continuing. If any popup about submitting a crash report shows up at any time, ignore/cancel it - we are going to manually submit the report to the staging error tracker (instead of the official one). # SleepTest.java public class SleepTest { public static void main(String[] args) throws Exception { Thread.sleep(5000); } } 1. Run whoopsie: $ sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f 2. Run the SleepTest and SIGKILL it in another terminal: $ java SleepTest & sleep 1 && pkill -f -SIGILL "java SleepTest" 3. View the crash report and submit it: $ apport-cli -c report /var/crash/_usr_lib_jvm_java-8-openjdk-amd64_jre_bin_java.1000.crash 3a) View the report 3b) [Optional] Search for the "HotspotError" key 3c) Send the report 4. Verify that the report was saved, including the hs_err content: 4a) In whoopsie terminal, check the OOPS ID code 4b) Browse to errors.staging.ubuntu.com/oops/$OOPSID 4c) Confirm that the HotspotError was added to the report [Regression Potential] If the new key is added to acceptable_fields whoopsie will upload the entries in it. Currently the OpenJDK apport hook limits this to 100 KB, but changes to it could allow bigger files with in turn cause an overhead in the error tracker infrastructure. [Original bug report] OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to a Crash report under the HotspotError key. The hook is currently limited to attaching files under 100 KB. Please add HotspotError key to the whitelist in order for it to be available in error tracker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+subscriptions -- Mailing list: https://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 1705551] Re: close lid suspends correctly and wakealarm resumes from suspend to run cron jobs but opening lid reveals no display
Hi, With regards to "FN keys", I tried all the FN keys and Ctrl+Alt+FN keys and Esc and many others but nothing worked. With regards to "never close the lid, but suspend via SW", (1) while in xfce account I ran sudo pm-suspend which suspended the laptop and (2) I then pressed the shift key and the laptop resumed normally with a working display. I repeated this with a remote ssh login into the laptop and it also worked perfectly. With regards to "xset dpms force off", when I do a remote ssh login into the laptop which resumed from wakealarm and has no display, I don't see a DISPLAY environment variable. When I execute "sudo -u bierre env DISPLAY=:0 /usr/bin/xrandr --auto", the system reports: No protocol specified Can't open display :0 I don't know if I am remotely executing this command correctly. Furthermore, I don't know how to reach xorg to execute "xset dpms force off". Thanks, Pierre On Fri, Jul 21, 2017 at 3:50 AM, ChristianEhrhardt < 1705...@bugs.launchpad.net> wrote: > Hi, > you said "all sorts of keyboard combinations" but maybe it is worth a try. > I had a similar case where it actually enabled the display, but at > brightness 0 - you might not accidentally have the same case? I could get > it on by using the FN keys to increase brightness in those cases. > > Another question would be if you never close the lid, but suspend via SW. > And next day you wakeup via the alarm (while the lid was still open when > sleeping) - is it then waking up normally with display enabled? > > Finally - I beg your pardon as I'm not an expert on this - but the > following could enable it. > You might need tweaks to actually "reach" your xorg, but I'm sure you can > do that. Once you did call: > $ xset dpms force off > That should disable the power saving blank that your screen is in. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1705551 > > Title: > close lid suspends correctly and wakealarm resumes from suspend to run > cron jobs but opening lid reveals no display > > Status in pm-utils package in Ubuntu: > Incomplete > > Bug description: > [Problem] > > When I close the laptop lid, pm-action runs the following code which I > have added: > > sh -c "echo 0 > /sys/class/rtc/rtc0/wakealarm" # clear alarm > sh -c "echo `date '+%s' -d '7am next day + 30 minutes'` > > /sys/class/rtc/rtc0/wakealarm" # set alarm > > and then suspends. At 7:30 AM the next day, the laptop resumes from > suspend with the lid closed and executes cron jobs (e.g. some > backups). If I open the lid then there is no display. I tried several > options to resume the display: > > - [FAILS] all sorts of keyboard combinations > - [FAILS] ssh -X into laptop and execute "sudo -u bierre env DISPLAY=:0 > /usr/bin/xrandr --auto" (n.b. when I run "sudo -u bierre env" there is no > DISPLAY variable) > - [MANUAL HACK] closing the lid causes the laptop to suspend and then > opening the lid causes it to resume with a normal working display > > I would like a solution or SOFTWARE HACK which I could add to /usr/lib > /pm-utils/sleep.d/99video during resume from suspend triggered by > wakealarm so that opening the lid would reveal a working display. > > [Laptop System Information] > > laptop = MacBookPro5,5 > pm-utils version = 1.4.1-13ubuntu0.2 > kernel = Linux version 3.19.0-32-generic (buildd@lgw01-43) (gcc version > 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 > UTC 2015 > OS = "Linux Mint 17.3 Rosa" based on "14.04.3 LTS, Trusty Tahr" > desktop environment = XFCE > video card = NVIDIA Corporation C79 [GeForce 9400M] (rev b1) (prog-if 00 > [VGA controller]) > video driver = [633938.944] (II) NOUVEAU(0): Output LVDS-1 > > [Additional Information] > > After my cron backup job is finished it will check if the lid is > closed. If it is closed then it will run pm-suspend. If I then open > the lid, the laptop resumes with a normal working display. So the > problem of no visible display occurs only when I open the lid after > resume from wakealarm and before the backup job suspends the laptop. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/ > 1705551/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1705551 Title: close lid suspends correctly and wakealarm resumes from suspend to run cron jobs but opening lid reveals no display Status in pm-utils package in Ubuntu: Incomplete Bug description: [Problem] When I close the laptop lid, pm-action runs the following code which I have added: sh -c "echo 0 > /sys/class/rtc/rtc0/wakealarm" # clear alarm sh -c "echo `date '+%s' -d '7am next day + 30 minutes'` > /sys/class/rtc/rtc0/wakealarm" # set alarm and then suspends. At
[Touch-packages] [Bug 1704998] Re: Flashing LEDs (~2min interval) on Logitech Performance MX (USB Wireless) Mouse
Thanks for the information. I've checked the kern.log and other logs in /var/log but nothing relevant showed up (to be exact no log-entries at all when the LEDs light up). Like you suggested I've also tested it with my notebook and it shows the same behavior with a fully upgraded Ubuntu 16.04.2 LTS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1704998 Title: Flashing LEDs (~2min interval) on Logitech Performance MX (USB Wireless) Mouse Status in upower package in Ubuntu: New Bug description: Hi, Since my upgrade from Ubuntu 14.04 to 16.04.2 LTS the battery indicator LEDs on my Logitech Performance MX Mouse light up about every 120 seconds when the mouse is inactive (no movement). Depending on the charging level 1, 2 or 3 LEDs light up green. When I boot into recovery mode or disable upower after a normal boot this behaviour doesn't occur. The expected behaviour is that the LEDs do not light up every 2 minutes but instead only when the charging levels drop from "3 to 2 LEDs" and "2 to 1 LEDs" - that's how it works with Ubuntu 14.04 (and Windows 10). Using the usbmon module I captured the usb traffic and when the LEDs light up the following is logged by "cat /sys/kernel/debug/usb/usbmon/2u": 8807a16ddd80 290929349 S Co:2:009:0 s 21 09 0210 0002 0007 7 = 10018107 00 8807a16ddd80 290929492 C Co:2:009:0 0 7 > 88074c55b180 290932022 C Ii:2:009:3 0:2 7 = 10018f81 070900 88074c55b180 290932033 S Ii:2:009:3 -115:2 32 < 8807f4332540 296834836 S Co:2:009:0 s 21 09 0210 0002 0007 7 = 10028107 00 8807f4332540 296835012 C Co:2:009:0 0 7 > 88074c55b180 298689874 C Ii:2:009:3 0:2 7 = 10028107 05 88074c55b180 298689892 S Ii:2:009:3 -115:2 32 < "upower --monitor-detail" shows the following when the LEDs light up: [10:22:41.041] device changed: /org/freedesktop/UPower/devices/mouse_0003o046Do101Ax0006 native-path: /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.8/2-1.8.4/2-1.8.4:1.2/0003:046D:C52B.0004/0003:046D:101A.0006 vendor: Logitech, Inc. model:Performance MX serial: F8A45D1F power supply: no updated: Tue 18 Jul 2017 10:22:40 AM UTC (1 seconds ago) has history: yes has statistics: no mouse present: yes rechargeable:yes state: discharging warning-level: none percentage: 55% icon-name: 'battery-good-symbolic' Information from solaar: Index : 2 Wireless PID : 101A Protocol : HID++ 1.0 Polling rate : 8 ms (125Hz) Serial : F8A45D1F Firmware : 15.01.B0062 Bootloader : 02.11 Other : 00.09 Notifications: battery status Here is the output from "lsusb -v" for the Logitech Unifying Receiver in use: Bus 002 Device 009: ID 046d:c52b Logitech, Inc. Unifying Receiver Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x046d Logitech, Inc. idProduct 0xc52b Unifying Receiver bcdDevice 12.01 iManufacturer 1 Logitech iProduct2 USB Receiver iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 84 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 4 RQR12.01_B0019 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 98mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.11 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 59 Report Descriptors: **
[Touch-packages] [Bug 1696814] Re: add openjdk hs log to list of acceptable_fields in whoopsie
Results from tests on Xenial: - current whoopsie 0.2.52.3: no HotspotError (as expected) https://errors.staging.ubuntu.com/oops/5e77a89e-6e4a-11e7-8a18-fa163eaf9b83 - proposed whoopsie 0.2.52.4: HotspotError is present (as expected) https://errors.staging.ubuntu.com/oops/cfa0113c-6e4a-11e7-8a18-fa163eaf9b83 ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1696814 Title: add openjdk hs log to list of acceptable_fields in whoopsie Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Xenial: Fix Committed Status in whoopsie source package in Zesty: Fix Committed Bug description: [Impact] By default OpenJDK 8 generates an hs_err file when it crashes, this file contains the stacktrace generated by OpenJDK (thus it contains different data compared to a gdb stacktrace) plus information on the running threads, classes, and memory usage (OpenJDK's regions). This file is usually required by the OpenJDK and/or IcedTea upstream developers when filling a bug and, in the case of OpenJDK, is more useful than the incomplete stacktrace that GDB can generate from OpenJDK crashes. OpenJDK 8 now includes a new apport hook to collect additional data from crash reports as well as the hs_err log file (in the new HotspotError key). A new release is soon reaching Zesty and Xenial with the hook included and without SRU'ing this fix the hs_err file won't be uploaded to the error tracker. [Test Case] Make sure that you are using OpenJDK 8 and to stop whoopsie service before continuing. If any popup about submitting a crash report shows up at any time, ignore/cancel it - we are going to manually submit the report to the staging error tracker (instead of the official one). # SleepTest.java public class SleepTest { public static void main(String[] args) throws Exception { Thread.sleep(5000); } } 1. Run whoopsie: $ sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f 2. Run the SleepTest and SIGKILL it in another terminal: $ java SleepTest & sleep 1 && pkill -f -SIGILL "java SleepTest" 3. View the crash report and submit it: $ apport-cli -c report /var/crash/_usr_lib_jvm_java-8-openjdk-amd64_jre_bin_java.1000.crash 3a) View the report 3b) [Optional] Search for the "HotspotError" key 3c) Send the report 4. Verify that the report was saved, including the hs_err content: 4a) In whoopsie terminal, check the OOPS ID code 4b) Browse to errors.staging.ubuntu.com/oops/$OOPSID 4c) Confirm that the HotspotError was added to the report [Regression Potential] If the new key is added to acceptable_fields whoopsie will upload the entries in it. Currently the OpenJDK apport hook limits this to 100 KB, but changes to it could allow bigger files with in turn cause an overhead in the error tracker infrastructure. [Original bug report] OpenJDK 8 apport hook attaches the hs_err_pid.log (if it exists) to a Crash report under the HotspotError key. The hook is currently limited to attaching files under 100 KB. Please add HotspotError key to the whitelist in order for it to be available in error tracker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1696814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700573] Re: Code execution through path traversal in .crash files processing
This bug was fixed in the package apport - 2.20.6-0ubuntu4 --- apport (2.20.6-0ubuntu4) artful; urgency=medium * apport/REThread.py: A bare except needs to be used so that we can catch the dialog being closed. * test/test_report.py: Be a little patient and give some time for the core file to show up. -- Brian MurrayFri, 21 Jul 2017 10:42:33 -0700 ** Changed in: apport (Ubuntu Artful) Status: In Progress => Fix Released -- 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/1700573 Title: Code execution through path traversal in .crash files processing Status in Apport: Fix Released Status in apport package in Ubuntu: Fix Released Status in apport source package in Trusty: Fix Released Status in apport source package in Xenial: Fix Released Status in apport source package in Yakkety: Fix Released Status in apport source package in Zesty: Fix Released Status in apport source package in Artful: Fix Released Bug description: The function add_hooks_info in apport/report.py is vulnerable to a directory traversal when processing the ExecutablePath key of a malicious .crash file: opt_path = None if self.get('ExecutablePath', '').startswith(_opt_dir): opt_path = self.get('ExecutablePath', '') elif package: # check package contents try: for f in apport.packaging.get_files(package): if f.startswith(_opt_dir) and os.path.isfile(f): opt_path = f break except ValueError: # uninstalled package pass if opt_path: while len(opt_path) >= len(_opt_dir): hook_dirs.append(os.path.join(opt_path, 'share', 'apport', 'package-hooks')) opt_path = os.path.dirname(opt_path) This can be used to execute an arbitrary python script from an attacker controlled path when a crash file is opened: fwilhelm@box:~$ cat poc.crash ProblemType: Bug ExecutablePath: /opt/../tmp/poc/share/apport/package-hooks Package: f fwilhelm@box:~$ cat /tmp/poc/share/apport/package-hooks/f.py import os os.system("gnome-calculator") fwilhelm@bpx:~$ strace -eprocess -f /usr/share/apport/apport-gtk poc.crash 2>&1 | grep gnome-calculator [pid 62617] execve("/bin/sh", ["sh", "-c", "gnome-calculator"], [/* 65 vars */]) = 0 [pid 62617] execve("/usr/bin/gnome-calculator", ["gnome-calculator"], [/* 64 vars */]) = 0 The sub directory requirement makes this a bit tricky to exploit remotely, but depending on the environment a malicious USB drive, a shared NFS share or a crash file inside an archive could be used. Please credit Felix Wilhelm from the Google Security Team in all releases, patches and advisories related to these issues. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1700573/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1588562] Re: Please add ~/.local/bin to the default $PATH
Very much appreciated. Subscribed to the bug report you made. -- 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/1588562 Title: Please add ~/.local/bin to the default $PATH Status in bash package in Ubuntu: Fix Released Status in bash source package in Xenial: Fix Released Status in bash package in Debian: Fix Released Bug description: Starting in Xenial, 'pip install' by default places executables into ~/.local/bin. This is the de-facto standard place to put per-user executables -- for example, Fedora/Redhat puts it on the $PATH by default, and PEP 370 makes it the standard place for unprivileged installs of Python packages to put their scripts. But unfortunately, Ubuntu's does *not* add this directory to $PATH by default, which means that 'pip install' doesn't actually work -- any scripts that are installed are inaccessible, and every user has to manually add this to their PATH. Ubuntu should put ~/.local/bin onto PATH by default. Minor details (discussed with @doko at the PyCon sprints): - this should go at the beginning of PATH rather than the end, in accordance with Debian policy saying that more-local paths go before more-upstream paths. (This is inconsistent with how Fedora/RH do it, but consistent with how Python itself searches for packages.) - this will be added to /etc/skel/profile, so that it won't change any existing user accounts; it will only be applied to user accounts created *after* this change lands - unlike ~/bin (which Debian/Ubuntu have supported for ages), it will be added to PATH unconditionally, even if the directory doesn't exist. This is important to avoid a nasty trap for new users, where the first time they try to install a Python package they have to restart their shell. Since this only applies to new accounts, the directory will always start out nonexistent/empty, so having it in $PATH won't cause any unexpected changes in behavior. - possibly it would make sense to set this in /etc/environment or /etc/skel/.gnomerc or similar, so that it would also apply to non-shell processes (e.g. if the user wants to add a global key-binding to launch a Python program, then generally ~/.profile *doesn't* affect the environment where this command gets executed, and that can frustrate and confuse users if a command works fine from the terminal but not from a keybinding). But we should defer this discussion for the future, because even if this is a good idea, it isn't a good idea in a Xenial stable update. Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820856 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1588562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1697375] Re: whoopsie's network-manager state querying is broken
Hmm apparently After=network-online.target may not be enough as I'm still running into a race. bdmurray@clean-xenial-amd64:~$ systemctl status whoopsie ● whoopsie.service - crash report submission daemon Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2017-07-21 11:51:09 PDT; 8s ago Main PID: 587 (whoopsie) CGroup: /system.slice/whoopsie.service └─587 /usr/bin/whoopsie -f Jul 21 11:51:09 clean-xenial-amd64 systemd[1]: Started crash report submission daemon. Jul 21 11:51:10 clean-xenial-amd64 whoopsie[587]: [11:51:10] Using lock path: /var/lock/whoopsie/lock Jul 21 11:51:10 clean-xenial-amd64 whoopsie[587]: [11:51:10] offline Jul 21 11:51:10 clean-xenial-amd64 whoopsie[587]: [11:51:10] Cannot reach: https://daisy.ubuntu.com Jul 21 11:51:10 clean-xenial-amd64 whoopsie[587]: [11:51:10] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/0 Jul 21 11:51:10 clean-xenial-amd64 whoopsie[587]: [11:51:10] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/0 Jul 21 11:51:10 clean-xenial-amd64 whoopsie[587]: [11:51:10] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/0 Jul 21 11:51:10 clean-xenial-amd64 whoopsie[587]: [11:51:10] online bdmurray@clean-xenial-amd64:~$ sudo shutdown -r now [sudo] password for bdmurray: Connection to clean-xenial-amd64.local closed by remote host. Connection to clean-xenial-amd64.local closed. Last login: Fri Jul 21 11:51:11 2017 from 192.168.122.1 bdmurray@clean-xenial-amd64:~$ systemctl status whoopsie ● whoopsie.service - crash report submission daemon Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2017-07-21 11:52:46 PDT; 4min 6s ago Main PID: 596 (whoopsie) CGroup: /system.slice/whoopsie.service └─596 /usr/bin/whoopsie -f Jul 21 11:52:46 clean-xenial-amd64 systemd[1]: Started crash report submission daemon. Jul 21 11:52:46 clean-xenial-amd64 whoopsie[596]: [11:52:46] Using lock path: /var/lock/whoopsie/lock Jul 21 11:52:46 clean-xenial-amd64 whoopsie[596]: [11:52:46] Could not get the Network Manager state: Jul 21 11:52:46 clean-xenial-amd64 whoopsie[596]: [11:52:46] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was Jul 21 11:52:46 clean-xenial-amd64 whoopsie[596]: [11:52:46] offline Jul 21 11:52:46 clean-xenial-amd64 whoopsie[596]: [11:52:46] Cannot reach: https://daisy.ubuntu.com Jul 21 11:52:47 clean-xenial-amd64 whoopsie[596]: [11:52:47] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/0 Jul 21 11:52:47 clean-xenial-amd64 whoopsie[596]: [11:52:47] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/0 Jul 21 11:52:47 clean-xenial-amd64 whoopsie[596]: [11:52:47] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/0 Jul 21 11:52:47 clean-xenial-amd64 whoopsie[596]: [11:52:47] online Regardless, this isn't making the situation worse and fixes it some of the time so I think it is still worth letting into -updates while we further sort out the matter. ** Tags removed: verification-needed-xenial verification-needed-zesty ** Tags added: verification-done-xenial verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1697375 Title: whoopsie's network-manager state querying is broken Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Xenial: Fix Committed Status in whoopsie source package in Zesty: Fix Committed Status in whoopsie source package in Artful: Fix Released Bug description: [Impact] whoopsie's querying of network-manager's state is broken and this results in whoopsie only being able to detect if the system is on-line when network manager's state changes. Subsequently, if one manually restarts whoopsie then whoopsie will stay off-line until an n-m state change. This can result in crashes not being uploaded. Additionally, whoopsie's systemd service file does not start after networking which is incorrect since it initially needs to query network-manager's state. (However, this ended up allowing crash reports to still be submitted because whoopsie would start first then the n-m's state would change and whoopsie would detect that.) [Test Case] (state detection failure) 1) Manually restart the whoopsie service 2) Observe the following two messages: "Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09] Could not get the Network Manager state: Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09] GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such property 'state'" with the version of network-manager from -proposed you will not see these messages when restarting whoopsie.
[Touch-packages] [Bug 1705571] Re: Add ~/.local/bin to the path in /etc/skel/.profile
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bash (Ubuntu) Status: New => Confirmed -- 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/1705571 Title: Add ~/.local/bin to the path in /etc/skel/.profile Status in bash package in Ubuntu: Confirmed Bug description: This appears to be a regression of https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1588562 In 16.04, per the above bug it is set with bash 4.3 # Working in 16.04 $ dpkg -l bash | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--= ii bash 4.3-14ubuntu1.2 amd64GNU Bourne Again SHell $ tail -n 2 /etc/skel/profile # set PATH so it includes user's private bin directories PATH="$HOME/bin:$HOME/.local/bin:$PATH" # Regression in 17.04 $ dpkg -l bash | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==--= ii bash 4.4-2ubuntu1.1 amd64GNU Bourne Again SHell $ tail -n 4 /etc/skel/.profile # set PATH so it includes user's private bin if it exists if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin:$PATH" fi # Regression in 17.10 $ dpkg -l bash | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii bash 4.4-5ubuntu1 amd64GNU Bourne Again SHell $ tail -n 4 /etc/skel/.profile # set PATH so it includes user's private bin if it exists if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin:$PATH" fi foo@76ee9ed7d4f5:~$ echo $PATH /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games The issue could be fixed with a diff on /etc/skel/.profile like: # Patch Diff diff --git a/.profile b/.profile index c9db459..da82446 100644 --- a/.profile +++ b/.profile @@ -20,3 +20,8 @@ fi if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin:$PATH" fi + +# set PATH so it includes user's private python-pip bin if it exists +if [ -d "$HOME/.local/bin" ] ; then +PATH="$HOME/.local/bin:$PATH" +fi LSB info $ lsb_release -rd Description: Ubuntu 17.04 Release: 17.04 $ lsb_release -rd Description:Ubuntu Artful Aardvark (development branch) Release:17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1705571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
Complementing #8 and #11: sudo fuser -v /var/cache/debconf/config.dat returned nothing. So, I made a backup of the files contained in /var/cache/debconf/ and have deleted all the original files in the same directory. After that, I've "restored" the backup and the upgrade worked fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable Status in Aptdaemon: Confirmed Status in Debconf: New Status in aptdaemon package in Ubuntu: Triaged Status in debconf package in Ubuntu: Triaged Bug description: Upgrading packages that use debconf sometimes fail with the following error: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/aptdaemon/+bug/349469/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1697375] Re: whoopsie's network-manager state querying is broken
Part 1 verified on Ubuntu 16.04: bdmurray@clean-xenial-amd64:~$ systemctl status whoopsie ● whoopsie.service - crash report submission daemon Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2017-07-21 11:33:57 PDT; 2min 32s ago Main PID: 1696 (whoopsie) CGroup: /system.slice/whoopsie.service └─1696 /usr/bin/whoopsie -f Jul 21 11:33:57 clean-xenial-amd64 systemd[1]: Started crash report submission daemon. Jul 21 11:33:57 clean-xenial-amd64 whoopsie[1696]: [11:33:57] Using lock path: /var/lock/whoopsie/lock Jul 21 11:33:57 clean-xenial-amd64 whoopsie[1696]: [11:33:57] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/0 Jul 21 11:33:57 clean-xenial-amd64 whoopsie[1696]: [11:33:57] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/0 Jul 21 11:33:57 clean-xenial-amd64 whoopsie[1696]: [11:33:57] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/0 bdmurray@clean-xenial-amd64:~$ apt-cache policy whoopsie whoopsie: Installed: 0.2.52.4 Candidate: 0.2.52.4 Version table: *** 0.2.52.4 500 500 http://192.168.10.7/ubuntu xenial-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.2.52.3 500 500 http://192.168.10.7/ubuntu xenial-updates/main amd64 Packages 0.2.52 500 500 http://192.168.10.7/ubuntu xenial/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1697375 Title: whoopsie's network-manager state querying is broken Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Xenial: Fix Committed Status in whoopsie source package in Zesty: Fix Committed Status in whoopsie source package in Artful: Fix Released Bug description: [Impact] whoopsie's querying of network-manager's state is broken and this results in whoopsie only being able to detect if the system is on-line when network manager's state changes. Subsequently, if one manually restarts whoopsie then whoopsie will stay off-line until an n-m state change. This can result in crashes not being uploaded. Additionally, whoopsie's systemd service file does not start after networking which is incorrect since it initially needs to query network-manager's state. (However, this ended up allowing crash reports to still be submitted because whoopsie would start first then the n-m's state would change and whoopsie would detect that.) [Test Case] (state detection failure) 1) Manually restart the whoopsie service 2) Observe the following two messages: "Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09] Could not get the Network Manager state: Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09] GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such property 'state'" with the version of network-manager from -proposed you will not see these messages when restarting whoopsie. [Test Case] (starting after network-manager0 1) Boot your system 2) Observe the following in syslog: "Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] Could not get the Network Manager state: Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files " with the version of network-manager in -proposed you will not see the "NetworkManager was not provided" messages. [Regression Potential] Its possible that systems that were not submitting crash reports suddenly will and that will use some network bandwidth and Error Tracker resources. - Original Description - On artful crash reports are not uploaded automatically (several .crash files in /var/crash and no corresponding upload or .uploaded files) ProblemType: BugDistroRelease: Ubuntu 17.10 Package: whoopsie 0.2.56 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 12 09:39:29 2017 InstallationDate: Installed on 2013-09-03 (1377 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: apport-noui N/ASourcePackage: whoopsie UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1697375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1617697] Re: Drop obsolete diff from Debian
Based on the package history [1], the Ubuntu delta seems to have been either removed or upstreamed to Debian (breaks: packagekit-plugin- click), and the package in Artful is now in sync with Debian. [1] https://launchpad.net/ubuntu/+source/packagekit/+publishinghistory ** Changed in: packagekit (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1617697 Title: Drop obsolete diff from Debian Status in packagekit package in Ubuntu: Fix Released Bug description: I don't think either of these 2 changes are worth making any more: * Client tools alternatively depend on or recommend aptdaemon's compatibility layer * packagekit provides the virtual packagekit-system-interface packagekit is now a recommends for all the Ubuntu 16.10 flavors. And I believe we're eventually demoting or even removing aptdaemon. I don't think any thing uses packagekit-system-interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1617697/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1697375] Re: whoopsie's network-manager state querying is broken
Part 1 verified on Ubuntu 17.04 bdmurray@clean-zesty-amd64:~$ sudo service whoopsie status ● whoopsie.service - crash report submission daemon Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2017-07-21 11:05:00 PDT; 6s ago Main PID: 1787 (whoopsie) Tasks: 4 (limit: 4915) CGroup: /system.slice/whoopsie.service └─1787 /usr/bin/whoopsie -f Jul 21 11:05:00 clean-zesty-amd64 systemd[1]: Stopped crash report submission daemon. Jul 21 11:05:00 clean-zesty-amd64 systemd[1]: Started crash report submission daemon. Jul 21 11:05:00 clean-zesty-amd64 whoopsie[1787]: [11:05:00] Using lock path: /var/lock/whoopsie/lock Jul 21 11:05:00 clean-zesty-amd64 whoopsie[1787]: [11:05:00] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/0 Jul 21 11:05:00 clean-zesty-amd64 whoopsie[1787]: [11:05:00] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/0 Jul 21 11:05:00 clean-zesty-amd64 whoopsie[1787]: [11:05:00] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/0 bdmurray@clean-zesty-amd64:~$ apt-cache policy whoopsie whoopsie: Installed: 0.2.55.1 Candidate: 0.2.55.1 Version table: *** 0.2.55.1 500 500 http://192.168.10.7/ubuntu zesty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.2.55 500 500 http://192.168.10.7/ubuntu zesty/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1697375 Title: whoopsie's network-manager state querying is broken Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Xenial: Fix Committed Status in whoopsie source package in Zesty: Fix Committed Status in whoopsie source package in Artful: Fix Released Bug description: [Impact] whoopsie's querying of network-manager's state is broken and this results in whoopsie only being able to detect if the system is on-line when network manager's state changes. Subsequently, if one manually restarts whoopsie then whoopsie will stay off-line until an n-m state change. This can result in crashes not being uploaded. Additionally, whoopsie's systemd service file does not start after networking which is incorrect since it initially needs to query network-manager's state. (However, this ended up allowing crash reports to still be submitted because whoopsie would start first then the n-m's state would change and whoopsie would detect that.) [Test Case] (state detection failure) 1) Manually restart the whoopsie service 2) Observe the following two messages: "Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09] Could not get the Network Manager state: Jul 14 14:48:09 speedy whoopsie[14137]: [14:48:09] GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such property 'state'" with the version of network-manager from -proposed you will not see these messages when restarting whoopsie. [Test Case] (starting after network-manager0 1) Boot your system 2) Observe the following in syslog: "Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] Could not get the Network Manager state: Jul 17 06:46:47 speedy whoopsie[1156]: [06:46:47] GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files " with the version of network-manager in -proposed you will not see the "NetworkManager was not provided" messages. [Regression Potential] Its possible that systems that were not submitting crash reports suddenly will and that will use some network bandwidth and Error Tracker resources. - Original Description - On artful crash reports are not uploaded automatically (several .crash files in /var/crash and no corresponding upload or .uploaded files) ProblemType: BugDistroRelease: Ubuntu 17.10 Package: whoopsie 0.2.56 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 12 09:39:29 2017 InstallationDate: Installed on 2013-09-03 (1377 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: apport-noui N/ASourcePackage: whoopsie UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1697375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1705752] [NEW] MacbookPro2015Retina13
Public bug reported: MacbookPro2015Retina13 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.12.3-041203-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jul 22 01:44:23 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:162b] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Broadwell-U Integrated Graphics [106b:013f] InstallationDate: Installed on 2017-07-18 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05ac:0273 Apple, Inc. Bus 001 Device 003: ID 05ac:8290 Apple, Inc. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.3-041203-generic root=UUID=c9754d17-264f-4e69-b9d6-3d2d31ef2851 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/16/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B24.1702161608 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B24.1702161608:bd02/16/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Jul 22 01:43:28 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 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/1705752 Title: MacbookPro2015Retina13 Status in xorg package in Ubuntu: New Bug description: MacbookPro2015Retina13 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.12.3-041203-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jul 22 01:44:23 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:162b] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Broadwell-U Integrated Graphics [106b:013f] InstallationDate: Installed on 2017-07-18 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05ac:0273 Apple, Inc. Bus 001 Device 003: ID 05ac:8290 Apple, Inc. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.3-041203-generic root=UUID=c9754d17-264f-4e69-b9d6-3d2d31ef2851 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/16/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B24.1702161608 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version:
[Touch-packages] [Bug 1704929] Re: Repeating "can't open /dev/ttyX: No such device or address" messages during installation
** Description changed: + [Impact] + + console-setup continuously tries to open /dev/tty[1-6] on s390x, when + such consoles do not exist on s390x. + + This can be seen on boot in the output from the initramfs, and during + the installer. + + [Cuase] + + It seems to me that the postinst of the console-setup is incorrect for + s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR, + z/VM, KVM) + + [Solution] + I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it to... "guess". Usually it should be slcp, but that depends on which consoles are configured/activated in the given KVM. + + [Testcase] + On boot, scroll all the messages and makesure there are no error messages about inability to open /dev/tty* + + [Original Bug Report] + During the installation (z/VM guest and KVM virtual machine) of Ubuntu Server 16.04.1 (and 16.04.2) repeating messages of the form: " Select and install software ... 10% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 20% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 30%... 40% can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... 50% can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... 60% can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... Finishing the installation ... 13%... 22%... 31% can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty4: No such device or address ... 40%... 50%... 63%... 72%... 81% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 90% The system is going down NOW - Sent SIGTERM to all processes - Sent SIGKILL to all processes - Requesting system reboot + Sent SIGTERM to all processes + Sent SIGKILL to all processes + Requesting system reboot 01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 02: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 00 Storage cleared - system reset. 00 zIPL .. " They start to occur when the software gets installed: "Select and install software ... 10% can't open /dev/tty4: No such device or address" And only stop with the final system reboot at the end of the installation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1704929 Title: Repeating "can't open /dev/ttyX: No such device or address" messages during installation Status in Ubuntu on IBM z Systems: New Status in console-setup package in Ubuntu: New Status in console-setup source package in Xenial: New Status in console-setup source package in Zesty: New Status in console-setup source package in Artful: New Bug description: [Impact] console-setup continuously tries to open /dev/tty[1-6] on s390x, when such consoles do not exist on s390x. This can be seen on boot in the output from the initramfs, and during the installer. [Cuase] It seems to me that the postinst of the console-setup is incorrect for s390, since on s390 Linux tty[1-6] do not exist in any modes (LPAR, z/VM, KVM) [Solution] I do not know what ACTIVE_CONSOLES should be set as, my guess is to set it to... "guess". Usually it should be slcp, but that depends on which consoles are configured/activated in the given KVM. [Testcase] On boot, scroll all the messages and makesure there are no error messages about inability to open /dev/tty* [Original Bug Report] During the installation (z/VM guest and KVM virtual machine) of Ubuntu Server 16.04.1 (and 16.04.2) repeating messages of the form: " Select and install software ... 10% can't open /dev/tty4: No such
[Touch-packages] [Bug 1635907] Re: Can't connect to Wifi network after suspend and resume
It seems I have a similar issue. After resume a connection dialog appears where the (correct) password is given. Connecting is still not possible (the dialog reappears in a loop, no connection established). Cancelling and connecting from the menu works fine. This looks like a similar old issue where the reconnect logon dialog messed up the encryption. (just my impression). -- 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/1635907 Title: Can't connect to Wifi network after suspend and resume Status in network-manager package in Ubuntu: New Bug description: Beginning in Ubuntu 16.04 and getting worse after upgrading to 16.10, I can't connect to wifi networks after suspending and resuming my laptop. I have a Sony Vaio SVP112A1CL with wireless network controller Intel Corporation Wireless 7260 (rev 6b). Typically I have to restart NetworkManager to recover from the problem (sudo systemctl restart NetworkManager). This seemed to be a reliable way to recover in 16.04, but it doesn't always work in 16.10 and may require a reboot. In some related bug reports they requested we run `sudo iw dev wlan0 scan` which resulted initially in an error but after running it a few times returned successfully. I'll attach the output below. Even though it did return, the wifi network still was unable to reconnect. I'll try to grab the errors next time, but if I do it now, I'll lose connectivity. $ apt-cache policy network-manager network-manager: Installed: 1.2.4-0ubuntu1 Candidate: 1.2.4-0ubuntu1 Version table: *** 1.2.4-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status $ sudo iw dev wlan0 scan BSS d4:05:98:46:d9:40(on wlan0) -- associated TSF: 2690064842954 usec (31d, 03:14:24) freq: 2457 beacon interval: 100 TUs capability: ESS Privacy ShortPreamble ShortSlotTime APSD (0x0c31) signal: -68.00 dBm last seen: 3728 ms ago Information elements from Probe Response frame: SSID: stevens-2G Supported rates: 1.0* 2.0* 5.5* 11.0* 9.0 18.0 36.0 54.0 DS Parameter set: channel 10 ERP: Extended supported rates: 6.0 12.0 24.0 48.0 Country: US Environment: Indoor/Outdoor Channels [1 - 11] @ 36 dBm HT capabilities: Capabilities: 0x1ec HT20 SM Power Save disabled RX HT20 SGI RX HT40 SGI TX STBC RX STBC 1-stream Max AMSDU length: 3839 bytes No DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 4 usec (0x05) HT RX MCS rate indexes supported: 0-23 HT TX MCS rate indexes are undefined HT operation: * primary channel: 10 * secondary channel offset: no secondary * STA channel width: 20 MHz * RIFS: 0 * HT protection: no * non-GF present: 1 * OBSS non-GF present: 0 * dual beacon: 0 * dual CTS protection: 0 * STBC beacon: 0 * L-SIG TXOP Prot: 0 * PCO active: 0 * PCO phase: 0 WPA: * Version: 1 * Group cipher: TKIP * Pairwise ciphers: TKIP CCMP * Authentication suites: PSK RSN: * Version: 1 * Group cipher: TKIP * Pairwise ciphers: TKIP CCMP * Authentication suites: PSK * Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x) WMM: * Parameter version 1 * u-APSD * BE: CW 15-1023, AIFSN 3 * BK: CW 15-1023, AIFSN 7 * VI: CW 7-15, AIFSN 2, TXOP 3008 usec * VO: CW 3-7, AIFSN 2, TXOP 1504 usec BSS Load: * station count: 5 * channel utilisation: 28/255 * available admission capacity: 31250 [*32us] Extended capabilities: HT Information Exchange Supported Country: US Environment: Indoor/Outdoor Channels [1 - 11] @ 16 dBm WPS: * Version: 1.0 * Wi-Fi Protected Setup State: 2 (Configured) * Response Type: 3 (AP) * UUID: bc329e00-1dd8-11b2-8601-d4059846d940 * Manufacturer: Celeno Communication, Inc. * Model: Celeno Wireless AP 2.4G * Model Number: CL1800 * Serial Number: 12345678
[Touch-packages] [Bug 1696710] Re: Ubuntu 16.04.02: depmod: WARNING: needs unknown symbol .TOC.
** Changed in: ubuntu-power-systems Assignee: Canonical Server Team (canonical-server) => Canonical Foundations Team (canonical-foundations) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1696710 Title: Ubuntu 16.04.02: depmod: WARNING: needs unknown symbol .TOC. Status in The Ubuntu-power-systems project: New Status in kmod package in Ubuntu: New Bug description: == Comment: #0 - Douglas Miller- 2017-01-24 07:59:54 == ---Problem Description--- depmod does not handle .TOC symbol on powerpc platforms Contact Information = Douglas Miller ---uname output--- Linux p8le03 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:40:06 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = other ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Compile kernel, during modules_install target the messages appear. PPC64 modules have a .TOC symbol which is required. It may be the only symbol with a period in the name, and so tools that restrict symbols based on a pattern may neglect to include .TOC. Userspace tool common name: depmod The userspace tool has the following bit modes: 64 Userspace rpm: libkmod2:ppc64el Userspace tool obtained from project website: na *Additional Instructions for Douglas Miller : -Attach ltrace and strace of userspace application. == Comment: #3 - Douglas Miller - 2017-01-24 08:12:58 == kmod package: # dpkg --list |grep kmod ii kmod 22-1ubuntu4 ppc64el tools for managing Linux kernel modules ii libkmod2:ppc64el 22-1ubuntu4 ppc64el libkmod shared library == Comment: #7 - Douglas Miller - 2017-06-07 16:20:38 == I was doing a build of upstream origin/master on Ubuntu 16.04.2 fresh install and still getting these messages. In the "make modules_install" output I see: ... DEPMOD 4.12.0-rc4 depmod: WARNING: /lib/modules/4.12.0-rc4/kernel/arch/powerpc/kernel/rtas_flash.ko needs unknown symb ol .TOC. ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1692981] Re: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config
Seth, Thank you very much. Your advice worked for me. Here the results you've requested: 1) dpkg -l | awk '/^iH/ { print $2 }' > libssl1.0.0:amd64 2) sudo apt-get install --reinstall libssl1.0.0:amd64 > Ok. 3) dpkg -l | awk '/^iH/ { print $2 }' > (none) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1692981 Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in dpkg package in Ubuntu: Confirmed Status in openssl package in Ubuntu: Confirmed Bug description: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: libssl1.0.0:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue May 23 21:47:55 2017 DuplicateSignature: package:libssl-dev:amd64:1.0.2g-1ubuntu11.2 Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ... dpkg: error processing package libssl-dev: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 2017-05-15 (7 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: openssl Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1692981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623666] Re: iOS device contents not displayed in Ubuntu
** Changed in: libimobiledevice Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS device contents not displayed in Ubuntu Status in Libimobiledevice: Fix Released Status in gnutls28 package in Ubuntu: Confirmed Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice*: Vauge discussion that mentions using the latest git HEAD*: https://github.com/libimobiledevice/libimobiledevice/issues/327 *This discussion is quite vague. One comment points out "iOS 10 devices don't allow SSLv3 anymore but require at least TLSv1", but not how or if that has been fixed in libimobiledevice git HEAD. This ppa packages the git version and may resolve the issue: https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages There are several other upstream reports related to this problem. Partial success patch (idevicepair only) trying to keep GnuTLS: https://github.com/libimobiledevice/libimobiledevice/issues/413 Failure with GnuTLS, Success with OpenSSL: https://gitlab.com/gnutls/gnutls/issues/145 Ubuntu packages libimobiledevice with "--disable-openssl": https://github.com/libimobiledevice/ifuse/issues/32 Duplicate bug 1638177 suggests to repackage libimobiledevice using OpenSSL to avoid this problem, as per comment 27 below. To manage notifications about this bug go to: https://bugs.launchpad.net/libimobiledevice/+bug/1623666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456789] Re: restarting services hangs on systemd-tty-ask-password-agent
I'm still seeing this with Ubuntu 16.04.2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1456789 Title: restarting services hangs on systemd-tty-ask-password-agent Status in systemd package in Ubuntu: Incomplete Status in systemd package in Debian: Fix Released Bug description: I have a script run as root from cron that tweaks smb.conf and restarts smbd and winbind. Problem is, starting today after working perfectly up till yesterday, this script now hangs on Ubuntu 15.04. When run from cron, the process tree looks like this: service smbd restart \_ systemctl restart smbd.service \_ /bin/systemd-tty-ask-password-agent --watch \_ /usr/bin/pkttyagent --notify-fd 5 --fallback Run from a shell via sudo, same thing except the process tree (obviously) includes the sudo command. It times out after 5 minutes, causing the script to fail. If I manually kill the processes, it fails faster. The simplest possible scripts that reproduce this, run as root or through cron or via sudo, are: #!/bin/sh service smbd restart #!/bin/sh systemctl restart smbd.service Using 'service', this works perfectly on Ubuntu 14.04 and 14.10, and until this morning worked perfectly on 15.04 as well. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 15.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center systemd 219-7ubuntu5 samba 2:4.1.13+dfsg-4ubuntu3 3) What you expected to happen Services to restart 4) What happened instead Services didn't restart, 'systemctl' hung To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1456789/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700826] Re: please include numactl on the ubuntu-server iso
** Also affects: ubuntu-meta (Ubuntu Zesty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1700826 Title: please include numactl on the ubuntu-server iso Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Xenial: New Status in ubuntu-meta source package in Zesty: New Bug description: I've submitted an MIR for the numactl binary package at: LP: #1700824. Assuming that is approved, please also include this on the server seed, which I believe is necessary for it to appear on the ubuntu-server ISOs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1700826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700826] Re: please include numactl on the ubuntu-server iso
Here is my understanding of next steps: 1) A MP should be submitted against the Artful seeds to update the 17.10 image(s) (which have not been release-published yet). On the next run, that will lead to numactl showing up in main in 17.10. 2) A MP should be submitted against the Zesty seeds to update the 17.04 publishing. 3) A MP should be submitted against the Xenial seeds to update the 16.04 publishing. 4) A request needs to be made to the AAs to actually move the binary package in the released series. They will need to do a pocket copy from $series/universe to $series-updates/main of the same version, since the $series release pocket is frozen. This will lead to numactl showing up in main in 17.04 and 16.04. 5) When the 16.04.3 ISOs are built, presuming 4) is complete for 16.04, then numactl should show up on the ISO. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1700826 Title: please include numactl on the ubuntu-server iso Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Xenial: New Status in ubuntu-meta source package in Zesty: New Bug description: I've submitted an MIR for the numactl binary package at: LP: #1700824. Assuming that is approved, please also include this on the server seed, which I believe is necessary for it to appear on the ubuntu-server ISOs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1700826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623666] Re: iOS device contents not displayed in Ubuntu
This is still not natively fixed in zesty even with ubuntu backport and updates. The workaround works but no applications like digikam can access automatically to IOS 10+ iphones anymore. Can someone at ubuntu do something to fix this definitly on the official release please ? ** Changed in: libimobiledevice Remote watch: github.com/libimobiledevice/libimobiledevice/issues #413 => github.com/libimobiledevice/ifuse/issues #32 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS device contents not displayed in Ubuntu Status in Libimobiledevice: Unknown Status in gnutls28 package in Ubuntu: Confirmed Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice*: Vauge discussion that mentions using the latest git HEAD*: https://github.com/libimobiledevice/libimobiledevice/issues/327 *This discussion is quite vague. One comment points out "iOS 10 devices don't allow SSLv3 anymore but require at least TLSv1", but not how or if that has been fixed in libimobiledevice git HEAD. This ppa packages the git version and may resolve the issue: https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages There are several other upstream reports related to this problem. Partial success patch (idevicepair only) trying to keep GnuTLS: https://github.com/libimobiledevice/libimobiledevice/issues/413 Failure with GnuTLS, Success with OpenSSL: https://gitlab.com/gnutls/gnutls/issues/145 Ubuntu packages libimobiledevice with "--disable-openssl": https://github.com/libimobiledevice/ifuse/issues/32 Duplicate bug 1638177 suggests to repackage libimobiledevice using OpenSSL to avoid this problem, as per comment 27 below. To manage notifications about this bug go to: https://bugs.launchpad.net/libimobiledevice/+bug/1623666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704596] Re: Mesa 17 (Ubuntu 16.04 HWE) breaks the dash's blur (dash and launcher are black)
Just tried xorg-edgers. The bug remains. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1704596 Title: Mesa 17 (Ubuntu 16.04 HWE) breaks the dash's blur (dash and launcher are black) Status in mesa package in Ubuntu: Incomplete Bug description: System: Ubuntu 16.04 32-bit + HWE Video card: GF 7300GT Driver: nouveau I'm testing the latest HWE stack. With Mesa 17 and enabled blur activating the dash results in all transparent elements getting black. Also, the launcher and panel are dark when the windows spread/scale is active. Disabling the blur or reverting to Mesa 12 solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1704596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704596] Re: Mesa 17 (Ubuntu 16.04 HWE) breaks the dash's blur (dash and launcher are black)
Mesa 17.1 (ppa:ubuntu-x-swat/updates) and 17.2 (ppa:oibaf/graphics- drivers) make no difference. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1704596 Title: Mesa 17 (Ubuntu 16.04 HWE) breaks the dash's blur (dash and launcher are black) Status in mesa package in Ubuntu: Incomplete Bug description: System: Ubuntu 16.04 32-bit + HWE Video card: GF 7300GT Driver: nouveau I'm testing the latest HWE stack. With Mesa 17 and enabled blur activating the dash results in all transparent elements getting black. Also, the launcher and panel are dark when the windows spread/scale is active. Disabling the blur or reverting to Mesa 12 solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1704596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623666] Re: iOS device contents not displayed in Ubuntu
** Also affects: libimobiledevice via https://github.com/libimobiledevice/libimobiledevice/issues/413 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS device contents not displayed in Ubuntu Status in Libimobiledevice: Unknown Status in gnutls28 package in Ubuntu: Confirmed Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice*: Vauge discussion that mentions using the latest git HEAD*: https://github.com/libimobiledevice/libimobiledevice/issues/327 *This discussion is quite vague. One comment points out "iOS 10 devices don't allow SSLv3 anymore but require at least TLSv1", but not how or if that has been fixed in libimobiledevice git HEAD. This ppa packages the git version and may resolve the issue: https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages There are several other upstream reports related to this problem. Partial success patch (idevicepair only) trying to keep GnuTLS: https://github.com/libimobiledevice/libimobiledevice/issues/413 Failure with GnuTLS, Success with OpenSSL: https://gitlab.com/gnutls/gnutls/issues/145 Ubuntu packages libimobiledevice with "--disable-openssl": https://github.com/libimobiledevice/ifuse/issues/32 Duplicate bug 1638177 suggests to repackage libimobiledevice using OpenSSL to avoid this problem, as per comment 27 below. To manage notifications about this bug go to: https://bugs.launchpad.net/libimobiledevice/+bug/1623666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623666] Re: iOS device contents not displayed in Ubuntu
** Tags added: zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS device contents not displayed in Ubuntu Status in Libimobiledevice: Unknown Status in gnutls28 package in Ubuntu: Confirmed Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice*: Vauge discussion that mentions using the latest git HEAD*: https://github.com/libimobiledevice/libimobiledevice/issues/327 *This discussion is quite vague. One comment points out "iOS 10 devices don't allow SSLv3 anymore but require at least TLSv1", but not how or if that has been fixed in libimobiledevice git HEAD. This ppa packages the git version and may resolve the issue: https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages There are several other upstream reports related to this problem. Partial success patch (idevicepair only) trying to keep GnuTLS: https://github.com/libimobiledevice/libimobiledevice/issues/413 Failure with GnuTLS, Success with OpenSSL: https://gitlab.com/gnutls/gnutls/issues/145 Ubuntu packages libimobiledevice with "--disable-openssl": https://github.com/libimobiledevice/ifuse/issues/32 Duplicate bug 1638177 suggests to repackage libimobiledevice using OpenSSL to avoid this problem, as per comment 27 below. To manage notifications about this bug go to: https://bugs.launchpad.net/libimobiledevice/+bug/1623666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705067] Re: system-local terminfo does not search /usr/share/terminfo as README says
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1705067 Title: system-local terminfo does not search /usr/share/terminfo as README says Status in ncurses package in Ubuntu: New Bug description: $ lsb_release -rd Description:Ubuntu 16.04.2 LTS Release:16.04 The file /etc/terminfo/README says This directory is for system-local terminfo descriptions. By default, ncurses will search ${HOME}/.terminfo first, then /etc/terminfo (this directory), then /lib/terminfo, and last not least /usr/share/terminfo. but it seems that /usr/share/terminfo is not used or does not work as expected? Repro: 1) Install `stterm` 2) Start `stterm` 3) Type `clear` Result: terminals database is inaccessible Expected result: Screen is cleared Workaround: Symlink the terminfo database to a user-local ~/.terminfo mkdir -p ~/.terminfo/s && ln -sf /usr/share/terminfo/s/stterm* ~/.terminfo/s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1705067/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705145] Re: upgrade xenial-perl to get important security fixes
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2016-1238 ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1705145 Title: upgrade xenial-perl to get important security fixes Status in perl package in Ubuntu: New Bug description: xenial packages perl at version 5.22.1, as described here -- https://packages.ubuntu.com/xenial/perl Please could you upgrade the package to reflect 5.22.4, to include critical bug fixes that have been fixed in the meantime? This is a binary-compatible upgrade that does not require the recompilation of perl modules contained in other ubuntu packages. Debian has already prepared a 5.22.4 build so you should be able to simply copy that over. The main security issue of concern is this one -- https://security-tracker.debian.org/tracker/CVE-2016-1238 -- which directly affects the package managers used by debian and ubuntu. I am also in touch with the debian perl people, and the core perl team, so I can answer additional questions or facilitate communication with either group as needed. thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1705145/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704929] Re: Repeating "can't open /dev/ttyX: No such device or address" messages during installation
** Also affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Also affects: console-setup (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: console-setup (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: console-setup (Ubuntu Zesty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1704929 Title: Repeating "can't open /dev/ttyX: No such device or address" messages during installation Status in Ubuntu on IBM z Systems: New Status in console-setup package in Ubuntu: New Status in console-setup source package in Xenial: New Status in console-setup source package in Zesty: New Status in console-setup source package in Artful: New Bug description: During the installation (z/VM guest and KVM virtual machine) of Ubuntu Server 16.04.1 (and 16.04.2) repeating messages of the form: " Select and install software ... 10% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 20% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 30%... 40% can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... 50% can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... 60% can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address ... Finishing the installation ... 13%... 22%... 31% can't open /dev/tty3: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty4: No such device or address ... 40%... 50%... 63%... 72%... 81% can't open /dev/tty4: No such device or address can't open /dev/tty2: No such device or address can't open /dev/tty3: No such device or address ... 90% The system is going down NOW Sent SIGTERM to all processes Sent SIGKILL to all processes Requesting system reboot 01: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 02: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 03: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop CPU 00. 00 Storage cleared - system reset. 00 zIPL .. " They start to occur when the software gets installed: "Select and install software ... 10% can't open /dev/tty4: No such device or address" And only stop with the final system reboot at the end of the installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1704929/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703092] Re: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
Affects every system software upgrade. -- 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/1703092 Title: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 Status in systemd package in Ubuntu: Confirmed Bug description: error shows when upgrading system Could not install 'systemd-shim' ProblemType: Package DistroRelease: Ubuntu 17.04 Package: systemd-sysv 232-21ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-23.25-generic 4.10.17 Uname: Linux 4.10.0-23-generic i686 ApportVersion: 2.20.4-0ubuntu4.4 Architecture: i386 Date: Sat Jul 8 10:37:04 2017 ErrorMessage: subprocess installed post-removal script returned error exit status 2 InstallationDate: Installed on 2013-05-04 (1525 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: systemd Title: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1703092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701692] Re: package util-linux 2.29-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dpkg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1701692 Title: package util-linux 2.29-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in dpkg package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Bug description: package util-linux 2.29-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration ProblemType: Package DistroRelease: Ubuntu 17.04 Package: util-linux 2.29-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Fri Jun 30 18:02:59 2017 DpkgTerminalLog: dpkg: error processing package util-linux (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-06-27 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package util-linux 2.29-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1701692/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701692] Re: package util-linux 2.29-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: util-linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1701692 Title: package util-linux 2.29-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in dpkg package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Bug description: package util-linux 2.29-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration ProblemType: Package DistroRelease: Ubuntu 17.04 Package: util-linux 2.29-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Fri Jun 30 18:02:59 2017 DpkgTerminalLog: dpkg: error processing package util-linux (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-06-27 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package util-linux 2.29-1ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1701692/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1567697] Re: libcurl is missing http2 support
> to resolve this issue it would seem that Canonical first must be convinced to take on official support for the nghttp2 package Yes, how can we do this? I find it crazy that Canonical doesn't want to officially support HTTP/2 in curl. Debian's curl is built with it for example. People shouldn't need to rebuild curl to have HTTP/2 support, it's not so experimental anymore. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1567697 Title: libcurl is missing http2 support Status in curl package in Ubuntu: Confirmed Bug description: libcurl supports HTTP/2.0 through libnghttp2, but the package on Ubuntu is not compiled with it. Alternatively, a libcurl4-(gnutls|openssl)-nghttp2 might be a good idea. See also: https://curl.haxx.se/docs/http2.html curl CLI tool should not need an update, as it already has the commandline switches, but when you use them it comes back with unsupported protocol. drwilco@eris:~$ curl --http2 www.google.com curl: (1) Unsupported protocol drwilco@eris:~$ lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 root@eris:~# apt-cache policy libcurl3 libcurl3: Installed: 7.47.0-1ubuntu2 Candidate: 7.47.0-1ubuntu2 Version table: *** 7.47.0-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1567697/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704998] Re: Flashing LEDs (~2min interval) on Logitech Performance MX (USB Wireless) Mouse
> How did you check the firmware build? The only information related to firmware I was able to find where provided from solaar solaar is a good way to get the device build number. > Could you also provide the version ("iConfiguration" in "lsusb -v") of your Unifying Receiver? It seems my mouse is a slightly older version. You have build 62 for the mouse and build 19 for the receiver. My mouse has build 60 for the mouse and build 17 for the receiver. Did you check if there is any interesting kernel messages (/var/log/kern.log) when upower issues the "device changed" message every 120 s? By any chance did you try it on another computer? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1704998 Title: Flashing LEDs (~2min interval) on Logitech Performance MX (USB Wireless) Mouse Status in upower package in Ubuntu: New Bug description: Hi, Since my upgrade from Ubuntu 14.04 to 16.04.2 LTS the battery indicator LEDs on my Logitech Performance MX Mouse light up about every 120 seconds when the mouse is inactive (no movement). Depending on the charging level 1, 2 or 3 LEDs light up green. When I boot into recovery mode or disable upower after a normal boot this behaviour doesn't occur. The expected behaviour is that the LEDs do not light up every 2 minutes but instead only when the charging levels drop from "3 to 2 LEDs" and "2 to 1 LEDs" - that's how it works with Ubuntu 14.04 (and Windows 10). Using the usbmon module I captured the usb traffic and when the LEDs light up the following is logged by "cat /sys/kernel/debug/usb/usbmon/2u": 8807a16ddd80 290929349 S Co:2:009:0 s 21 09 0210 0002 0007 7 = 10018107 00 8807a16ddd80 290929492 C Co:2:009:0 0 7 > 88074c55b180 290932022 C Ii:2:009:3 0:2 7 = 10018f81 070900 88074c55b180 290932033 S Ii:2:009:3 -115:2 32 < 8807f4332540 296834836 S Co:2:009:0 s 21 09 0210 0002 0007 7 = 10028107 00 8807f4332540 296835012 C Co:2:009:0 0 7 > 88074c55b180 298689874 C Ii:2:009:3 0:2 7 = 10028107 05 88074c55b180 298689892 S Ii:2:009:3 -115:2 32 < "upower --monitor-detail" shows the following when the LEDs light up: [10:22:41.041] device changed: /org/freedesktop/UPower/devices/mouse_0003o046Do101Ax0006 native-path: /sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.8/2-1.8.4/2-1.8.4:1.2/0003:046D:C52B.0004/0003:046D:101A.0006 vendor: Logitech, Inc. model:Performance MX serial: F8A45D1F power supply: no updated: Tue 18 Jul 2017 10:22:40 AM UTC (1 seconds ago) has history: yes has statistics: no mouse present: yes rechargeable:yes state: discharging warning-level: none percentage: 55% icon-name: 'battery-good-symbolic' Information from solaar: Index : 2 Wireless PID : 101A Protocol : HID++ 1.0 Polling rate : 8 ms (125Hz) Serial : F8A45D1F Firmware : 15.01.B0062 Bootloader : 02.11 Other : 00.09 Notifications: battery status Here is the output from "lsusb -v" for the Logitech Unifying Receiver in use: Bus 002 Device 009: ID 046d:c52b Logitech, Inc. Unifying Receiver Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x046d Logitech, Inc. idProduct 0xc52b Unifying Receiver bcdDevice 12.01 iManufacturer 1 Logitech iProduct2 USB Receiver iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 84 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 4 RQR12.01_B0019 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 98mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 0 HID Device Descriptor: bLength
[Touch-packages] [Bug 1696499] Re: dhclient segfaults on ubuntu 17.04
If you are using network-manager, remove the following modules from the enforcing mode should allow automatic DHCP from network-manager: /usr/lib/NetworkManager/nm-dhcp-client.action /usr/lib/NetworkManager/nm-dhcp-helper -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1696499 Title: dhclient segfaults on ubuntu 17.04 Status in isc-dhcp package in Ubuntu: Confirmed Bug description: After upgrading, network-manager stopped running DHCP, after trying to run dhclient myself I found out it segfaults. Attached is its strace output. I can connect to the internet by stopping network-manager and using ifconfig + route + /etc/resolv.conf. Output: guy@golem4:~$ dhclient Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1696499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1696499] Re: dhclient segfaults on ubuntu 17.04
Inspection of the core dump and some testing proves the Segmentation fault error is caused by denied permission to read /proc/self/cmdline. Moving the executable anywhere else the problem would simply disappear. Further inspection pointed the cause to be apparmor denied the open file call, thus, the obvious workaround is remove /sbin/dhclient's apparmor from enforcing mode: sudo apt install apparmor-utils sudo aa-complain /sbin/dhclient This would allow the dhclient to run without error. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1696499 Title: dhclient segfaults on ubuntu 17.04 Status in isc-dhcp package in Ubuntu: Confirmed Bug description: After upgrading, network-manager stopped running DHCP, after trying to run dhclient myself I found out it segfaults. Attached is its strace output. I can connect to the internet by stopping network-manager and using ifconfig + route + /etc/resolv.conf. Output: guy@golem4:~$ dhclient Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1696499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576282] Re: Snaps built from deb can't be gettext translated
** Description changed: Currently it seems not possible to have working gettext translations - without included a patch glibc build in your snap + without included a patched glibc build in your snap - the core image doesn't have locales definition that can be worked around by including locales definitions in the snap, though that's tedious, ideally snapcraft would help there - - - traditional desktop applications are built with calls to 'bindtextdomain ("domain", LOCALEDIR)', where LOCALDIR is defined at buildtime and so pointing to /usr + - traditional desktop applications are built with calls to + 'bindtextdomain ("domain", LOCALEDIR)', where LOCALDIR is defined at + buildtime and so pointing to /usr there seems to be no way to redirect to another directory at runtime - - - desktop applications needs system library translations sometime which means langpacks need to be included in snaps + - desktop applications needs system library translations sometime which + means langpacks need to be included in snaps -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1576282 Title: Snaps built from deb can't be gettext translated Status in Canonical System Image: In Progress Status in Snapcraft: New Status in Ubuntu App Platform: Fix Released Status in snapcraft package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Currently it seems not possible to have working gettext translations without included a patched glibc build in your snap - the core image doesn't have locales definition that can be worked around by including locales definitions in the snap, though that's tedious, ideally snapcraft would help there - traditional desktop applications are built with calls to 'bindtextdomain ("domain", LOCALEDIR)', where LOCALDIR is defined at buildtime and so pointing to /usr there seems to be no way to redirect to another directory at runtime - desktop applications needs system library translations sometime which means langpacks need to be included in snaps To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1576282/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Changed in: openssh (Ubuntu Artful) Status: Fix Released => Triaged ** Changed in: openssh (Ubuntu Artful) Importance: High => Critical ** Changed in: openssh (Ubuntu Zesty) Status: In Progress => Confirmed ** Changed in: openssh (Ubuntu Zesty) Importance: High => Critical ** Changed in: ubuntu-z-systems Status: Fix Committed => Triaged ** Changed in: ubuntu-z-systems Importance: High => Critical -- 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: Triaged Status in openssh source package in Zesty: Confirmed Status in openssh source package in Artful: Triaged Bug description: [ Impact ] * Unable to ssh into Ubuntu, using default sshd configuration, when hw acceleration is enabled in openssl. [ Proposed solution ] * Cherrypick upstream fixes for: - sandboxing code on big endian - allowing hw accel iocls in the sandbox 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." __ [Test case] long: enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x like this: sudo apt-get install openssl-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
[Touch-packages] [Bug 1449001] Re: systemd-resolved: please do not use Google public DNS by default
** No longer affects: systemd (Ubuntu Yakkety) -- 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/1449001 Title: systemd-resolved: please do not use Google public DNS by default Status in systemd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Zesty: Confirmed Status in systemd source package in Artful: Fix Released Status in systemd package in Debian: Fix Released Bug description: systemd-resolved will fall back to Google public DNS (8.8.8.8, etc.) in the absence of other configured DNS servers. systemd-resolved is not enabled by default in Ubuntu 15.04, but it is installed by default and will behave in this way if enabled by the user. $ cat /etc/systemd/resolved.conf (...) # Entries in this file show the compile time defaults. (...) #FallbackDNS=8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844 This raises privacy concerns since in the event of accidental misconfiguration DNS queries will be sent unencrypted across the internet, and potentially also security concerns given systemd- resolved does not perform DNSSEC validation and is not particularly well hardened against malicious responses e.g. from a MITM (http://www.openwall.com/lists/oss-security/2014/11/12/5). I believe that it would be better to fail safe if no DNS server is configured -- i.e. have DNS lookups fail; it's better that the user is aware of their misconfiguration, rather than silently sending their queries to Google. The user can intentionally opt to use Google public DNS if they wish. Steps to reproduce: 1. Remove existing DNS configuration (from /etc/network/interfaces, /etc/resolv.conf, /etc/resolvconf/resolv.conf.d/*) 2. Reboot, or otherwise clear relevant state 3. sudo service systemd-resolved start 4. Note that Google's servers are listed in /run/systemd/resolve/resolv.conf 5. If systemd-resolved is enabled in /etc/nsswitch.conf (it isn't by default), observe that DNS lookups probably still work, and queries are being sent to one of Google's servers Possible workaround/bugfix: ship a resolved.conf which clears the FallbackDNS parameter. This issue has been discussed in the Debian BTS (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658). My interpretation of the Debian package maintainer's position is that a user concerned with the privacy implications shouldn't let systemd get into a state where it uses the fallback DNS servers (quoting Marco d'Itri: "Short summary: have a resolv.conf file or use DHCP"). I would argue that it's safest not to have fallback DNS servers configured at all by default. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1449001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()
** No longer affects: systemd (Ubuntu Yakkety) -- 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/1621396 Title: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for() Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Zesty: Fix Released Bug description: [Impact] * Null-pointer dereference in resolved, results in resolved crash and reports on launchpad and errors. [Test Case] * Unknown steps to reproduce * Monitor the drop off in crashes on errors.ubuntu.com: https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 [Regression Potential] * The behavior is similar, instead of crashing resolved it returns an error in the relevant function. Whilst this may not result in correct dns resolution for the affected dns packets, it should not result in resolved crashes. [Original Bug Report] This is one of background errors that happens without any active app being involved. For the records, I had open: Firefox, Slack, Franz and the Terminal The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 233-6ubuntu2, the problem page at https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-5 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 8 09:33:55 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2013-06-06 (1189 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so sd_event_run () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago) UserGroups: dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0PJHXN 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.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN: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/systemd/+bug/1621396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1665088] Re: netplan bridge config doesn't support stp boolean
** No longer affects: systemd (Ubuntu Yakkety) -- 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/1665088 Title: netplan bridge config doesn't support stp boolean Status in netplan: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Released Status in systemd source package in Xenial: New Status in nplan source package in Yakkety: Fix Released Status in nplan source package in Zesty: Fix Released Status in systemd source package in Zesty: Fix Released Bug description: [Impact] Users of netplan may wish to specify a custom MTU value for a device. [Test case] - Run nplan integration tests on the release - Validate that netplan generate && netplan apply alone, without config, behave as expected (no result) - Validate that netplan generate && netplan apply with minimal config writes /run/NetworkManager/conf.d/10-globally-managed-devices.conf - Validate that netplan generate && netplan apply works with any existing configuation. - Use the config below; ensure behavior is as expected (STP value is set on the interface; adjust device names as appropriate). There should be no errors at applying the requested configuration. - Use the config below with the 'stp' key; the device should be brought up and include the default value set for the kernel. [Regression potential] STP default value should continue to be used for the bridge configured using netplan if STP is unset in configuration. --- networkd supports setting STP value in Bridge type netdevs, but netplan does not accept the key. root@ubuntu:/etc/netplan# apt-cache policy nplan nplan: Installed: 0.18 Candidate: 0.18 Version table: *** 0.18 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:/etc/netplan# lsb_release -rd Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 root@ubuntu:/etc/netplan# cat 52-bridge.yaml network: ethernets: eth0: addresses: - 10.11.12.13/24 match: macaddress: '52:54:00:12:34:00' set-name: foobar0 eth1: match: macaddress: '52:54:00:12:34:02' set-name: eth1 eth2: match: macaddress: '52:54:00:12:34:04' set-name: eth2 bridges: br0: addresses: - 192.168.14.2/24 interfaces: - eth1 - eth2 parameters: ageing-time: 250 priority: 22 forward-delay: 1 hello-time: 1 max-age: 10 path-cost: eth1: 50 eth2: 75 stp: true version: 2 root@ubuntu:/etc/netplan# netplan generate Error in network definition //etc/netplan/52-bridge.yaml line 24 column 16: unknown key stp To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1665088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668347] Re: Unable to set bridge_portpriority with networkd
** No longer affects: systemd (Ubuntu Yakkety) -- 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/1668347 Title: Unable to set bridge_portpriority with networkd Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Zesty: Fix Released Bug description: [Impact] * Netplan uses systemd-netword provider to configure all sorts of networking settings * However, unlike ifupdown, released versions of systemd do not support setting bridgeport priority, aka `brctl setportprio ` * This prevents full migration from ifupdown to netplan/systemd-networkd for projects like MAAS that do need to configure equal cost; yet differential priority bridge ports. * This is proposal to cherrypick this functionality which essentially accepts one more key in the .network units; and send those values via netlink. [Test Case] * networkd-test.py is executed as part of autopkgtests that configures a bridge, and sets various valid bridge port priorities and verifies from sysfs that those were correctly set by systemd. * Alternativey create a bridge .link unit, and specify .network unit for a bridge port and use Priority=4 setting in the [Bridge] section in the said unit to modify bridge port priority. [Regression Potential] * This is an upstream cherrypick of functionality that will be included in 234 release. However, since MAAS and netplan target stable releases, I would like to cherrypick this functionality all the way back to xenial. This almost a feature, rather than a bugfix, but it is so small and accompanied by regression testsuite that it is almost a tiny bugfix. [Other Info] * Original request to support this feature. 1. root@ubuntu:/run/systemd/network# lsb_release -rd Description:Ubuntu Zesty Zapus (development branch) Release:17.04 2. root@ubuntu:/run/systemd/network# apt-cache policy systemd systemd: 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. Using a networkd config like this: # cat 10-netplan-eth1.network [Match] MACAddress=52:54:00:12:34:02 Name=eth1 [Network] Bridge=br0 LinkLocalAddressing=no IPv6AcceptRA=no [Bridge] Cost=50 Priority=28 % cat /sys/class/net/br0/brif/eth1/priority 28 4. % cat /sys/class/net/br0/brif/eth1/priority 32 When using ifupdown and /etc/network/interfaces to configure a bridge users are able to specify a bridge port priority: auto br0 iface br0 inet static address 192.168.1.1 bridge_ports eth1 eth2 bridge_portprio eth1 28 bridge_portprio eth2 14 Which results in the bridge hook scripts running: brctl setportprio br0 eth1 28 which is visible via: /sys/class/net/br0/brif/eth2/priority Note, networkd does not mention PortPriority under netdev Bridge section, however, PathCost is mentioned. It appears networkd is missing an implementation. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 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: Mon Feb 27 17:11:32 2017 Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic root=UUID=900c1e3f-f682-4455-949c-ebdbf60ac6f5 ro console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.1-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-zesty dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.1-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-zesty:cvnQEMU:ct1:cvrpc-i440fx-zesty: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-zesty dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686784] Re: no predictable names for platform (non-PCI) NICs
** No longer affects: systemd (Ubuntu Yakkety) -- 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/1686784 Title: no predictable names for platform (non-PCI) NICs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Zesty: Fix Released Bug description: [Impact] Systems may have NICs attached to the "platform" bus. These are NICs that are onboard, but not attached to a PCI(-like) bus. Rather, they are described by firmware directly. None of the naming policies enabled by Ubuntu by default matches these NICs, so they end up having unpredictable names. In the case where other NICs are attached (e.g. PCIe cards), the ethN enumeration race occurs, making it impossible to have an interface name that is persistent across reboots. That is, if you do a network install over "eth0", on reboot that NIC now maybe "eth3", which causes it to fail to start the network on boot. The HiSilicon D05 boards are an example of this. It has 4 onboard NICs that are described by ACPI directly, and may also have other PCIe NICs plugged in. [Test Case] Boot a system with the characteristics described above, and check to see if any "ethN" interfaces exist. [Regression Risk] Unless one fixed the names locally with .netlink / .rules files the interface names will change for the ACPI/platform bus network interfaces, from random ethX names to stable names named like enaVENDORMODELiX. Thus we should check that this update doesn't negatively break certified ARM64 platforms with: ARM, NVIDIA, HISILICON platform bus ethernet devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1686784/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** No longer affects: systemd (Ubuntu Yakkety) -- 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 Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Zesty: Fix Released Status in systemd source package in Artful: Fix Released Bug description: [Impact] * Containers cannot use maximum RLIMIT_NOFILE, because systemd sets an arbitrary cap. [Test Case] * Start container with high RLIMIT_NOFILE (e.g. 100 000) * Check that RLIMIT_NOFILE on the container is more than 65536 [Regression Potential] * This is a feature / change of behaviour. Some users may be relying on the lower RLIMIT_NOFILE cap, but it should not have a negative impact on the host (as in creating too many file descriptors/denial of service). [Original Bug Report] 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 1692136] Re: Backport "core/timer: downgrade message about random time addition (#5229)".
** No longer affects: systemd (Ubuntu Yakkety) -- 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/1692136 Title: Backport "core/timer: downgrade message about random time addition (#5229)". Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Zesty: Fix Released Bug description: [Impact] * Systemd spams logs too much with pointless messages [Test Case] * Boot system and observe no pointless messages of scheduling random timers for things at a given offset [Regression Potential] * Low, this patch simply changes the priority of the message from info to debug. [Original bug report] Please backport upstream systemd v233 commit 382852fd581efe3cc0ae11154102ab9f435adea1 "core/timer: downgrade message about random time addition (#5229)". https://github.com/systemd/systemd/commit/382852fd581efe3cc0ae11154102ab9f435adea1 This removes "random time" messages flooding dmesg. The spew was introduced with v229 commit "core: add new RandomSec= setting for time units". https://github.com/systemd/systemd/commit/744c7693751830149ae78fdaf95c6c6f99d59f07 trusty based off v204 is not affected. xenial based off v229, yakkety based off v231, and zesty based off v232 need this fix. artful based off v233 has the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1692136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1698734] Re: systemd-resolved spams syslog whenever I'm disconnected
** No longer affects: systemd (Ubuntu Yakkety) -- 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/1698734 Title: systemd-resolved spams syslog whenever I'm disconnected Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: New Status in systemd source package in Zesty: New Status in systemd source package in Artful: Fix Released Bug description: Every time I suspend my laptop and resume in a situation where I don't have connectivity I get big syslog spam from systemd-resolved. See for instance yesterday when I went out: Jun 18 18:48:16 chiron systemd[1]: Starting Suspend... Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS server 8.8.8.8. Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS server 8.8.4.4. Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS server 2001:4860:4860::. Jun 18 18:48:16 chiron systemd-resolved[1868]: Switching to fallback DNS server 2001:4860:4860::8844. ... And the last messages of the "episode": Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS server 8.8.8.8. Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS server 8.8.4.4. Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS server 2001:4860:4860::. Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS server 2001:4860:4860::8844. Jun 18 20:13:28 chiron systemd-resolved[1868]: Switching to fallback DNS server 8.8.8.8. Jun 18 20:13:28 chiron NetworkManager[30674]: [1497809608.0889] device (wlp2s0): supplicant interface state: associ ated -> 4-way handshake So this correspond to roughly 85 minutes of disconnection, during which I got... $ grep "fallback DNS" /var/log/syslog.1 | wc -l 444066 This correspond to 5224 messages/minute, 87 messages/second I had a few other episodes in the last week, including a 4h train roundtrip: $ zgrep "fallback DNS" /var/log/syslog* | wc -l 1964217 I noticed the bug during the trip, when the SSD activity was slowing my machine in a clearly noticeable way. I'm running: $ lsb_release -rd Description: Ubuntu 17.04 Release: 17.04 $ apt-cache policy $(dpkg-query -S $(which systemd-resolve ) | awk '{print $1}') systemd: Installed: 232-21ubuntu3 Candidate: 232-21ubuntu3 Version table: *** 232-21ubuntu3 500 500 http://es.archive.ubuntu.com/ubuntu zesty-updates/main amd64 Packages 100 /var/lib/dpkg/status 232-21ubuntu2 500 500 http://es.archive.ubuntu.com/ubuntu zesty/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1698734/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1702823] Re: Systemd fails to serialize tasks correctly on daemon-reload
** No longer affects: systemd (Ubuntu Yakkety) -- 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/1702823 Title: Systemd fails to serialize tasks correctly on daemon-reload Status in systemd: Fix Released 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 Status in systemd package in Debian: Fix Released Bug description: Hi, I was initially tracking down a libvirt bug [1], but happened to realize it is actually a general systemd issue. From there I got to file, discuss and test [2]. For now I file the bug to be ablte to do my tests correctly, but if it really fixes the issue I'd like to suggest to fix it in the release - so better file upfront and do even my test patches right. [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867379 [2]: https://github.com/systemd/systemd/issues/6299. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1702823/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1288258] Re: GDebi isn't localized in Ubuntu 14.04: gdebi-core package is missing /usr/share/locale directory
Seems to be fine now. Apparently it had been fixed with the updates of all language-pack-xx-base packages to version 1:14.04+20160720. I see gdebi.mo is included there now. ** Changed in: gdebi (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1288258 Title: GDebi isn't localized in Ubuntu 14.04: gdebi-core package is missing /usr/share/locale directory Status in gdebi package in Ubuntu: Fix Released Bug description: When I install GDebi 0.9.3 in a Dutch localized and fully updated Xubuntu 14.04, GDebi is 100 % in English. But it should be 100 % Dutch, as the Dutch translation for GDebi on Launchpad, was completed over a year ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1288258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack
Installed virtualbox-hwe-guest-utils, guest-x11 guest-dkms and everything worked correctly. Removed dkms package and installed vith module-assistant the virtualbox-guest-source package. So far so good, reboot works correctly -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in virtualbox-hwe package in Ubuntu: Fix Committed Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: New Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in libinput source package in Xenial: Fix Committed Status in libwacom source package in Xenial: Fix Committed Status in libxfont source package in Xenial: Fix Committed Status in libxfont2 source package in Xenial: Fix Committed Status in llvm-toolchain-4.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in vulkan source package in Xenial: Fix Committed Status in wayland source package in Xenial: Fix Committed Status in x11proto-core source package in Xenial: Fix Committed Status in xfonts-utils source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: Fix Committed Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack
** Tags removed: block-proposed verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in virtualbox-hwe package in Ubuntu: Fix Committed Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: New Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in libinput source package in Xenial: Fix Committed Status in libwacom source package in Xenial: Fix Committed Status in libxfont source package in Xenial: Fix Committed Status in libxfont2 source package in Xenial: Fix Committed Status in llvm-toolchain-4.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in vulkan source package in Xenial: Fix Committed Status in wayland source package in Xenial: Fix Committed Status in x11proto-core source package in Xenial: Fix Committed Status in xfonts-utils source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: Fix Committed Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 988144] Re: Getting error message: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]
This is happening again on: xenial $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial $ uname -a Linux vaughan 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ rsync --version rsync version 3.1.1 protocol version 31 Copyright (C) 1996-2014 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv, symtimes, prealloc rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/988144 Title: Getting error message: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] Status in rsync package in Ubuntu: Confirmed Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Precise 12.04LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Installed: 3.0.9-1ubuntu1 Candidate: 3.0.9-1ubuntu1 Version table: *** 3.0.9-1ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ precise/main i386 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I was using rsync to backup my Home DIrectorys' contents and at one point in the backup it gave me this error: Downloads/Windows.7.Ultimate.32-64Bit.(2011-02-09).iso 3809312768 83% 21.03MB/s0:00:35 rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32) rsync: connection unexpectedly closed (70735 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] This only came about when it was trying to copy my Windows ISO from my directory over to my backup drive that I have formatted in EXT4 - so I'm not sure of the issue it's having. This is the command I used to backup: rsync --progress -rEog --exclude Videos/ --exclude converted_music/ --exclude VirtualBox\ VMs/ --exclude virtual-drives/ --exclude Backup_of_boot_sectors/ --exclude examples.desktop --exclude Music/ --exclude .ecryptfs --exclude .VirtualBox/ --exclude .thumbnails/ --exclude .thunderbird/ --exclude .vidalia/ --exclude .teamviewer/ --exclude Templates/ --exclude sources.list --exclude wary-5.3.iso --exclude Public/ --exclude .cache/ /home/alex/ /media/backup/12.04 -Precise-backup_4.23.2012/ Please look into this for me. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/988144/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1207004] Re: certdata2pem.py doesn't handle CKT_NSS_MUST_VERIFY_TRUST
** Changed in: ca-certificates (Debian) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1207004 Title: certdata2pem.py doesn't handle CKT_NSS_MUST_VERIFY_TRUST Status in ca-certificates package in Ubuntu: Confirmed Status in ca-certificates package in Debian: Fix Committed Bug description: Hello, I'm a Python core developer and hobbyist security researcher. While I was working on my own parser for Mozillas certdata.txt [1] I found an issue in curls mk-ca-bundle.pl script. Today I found the same issue in Debian's and Ubuntu's script. The Python script ./mozilla/certdata2pem.py of ca-certificates-20120623 doesn't handle the flag CKT_NSS_MUST_VERIFY_TRUST. The flag was introduced in revision 1.84 of certdata.txt, see [2] The PKCS#11 glue documentation [3] of the freedesktop.org project has some background information on the flag, too. Quote: --- The certificate is not a trusted anchor (even if a later trust record in another PKCS #11 module says this cert should be trusted). If the marked certificate is self-signed, then this is semantically equivalent to CKT_NSS_NOT_TRUSTED, except NSS will return a different error code (unknown CA for CKT_NSS_MUST_VERIFY_TRUST versus untrusted CA for CKT_NSS_NOT_TRUSTED). --- May I suggest that you reverse the check and distrust any certificate unless it was explicitly flagged as a trusted delegator and root CA cert? In the context of cryptography and TLS it more secure to omit a root CA cert than to wrongly ship a bogus cert. By the way Adam Langley [4] uses the same approach [5]. My Ubuntu box has files like Verisign_Class_1_Public_Primary_Certification_Authority.pem in the /etc/ssl/certs/ directory. According to my script "Verisign Class 1 Public Primary Certification Authority" is flagged as CKT_NSS_MUST_VERIFY_TRUST for CKA_TRUST_SERVER_AUTH [6]. $ LC_ALL=C apt-cache policy ca-certificates ca-certificates: Installed: 20120623 Candidate: 20120623 Version table: *** 20120623 0 500 http://de.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status $ LC_ALL=C lsb_release -a LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch Distributor ID: Ubuntu Description:Ubuntu 12.10 Release:12.10 Codename: quantal Regards, Christian [1] https://bitbucket.org/tiran/storeroom/ [2] http://lists.debian.org/debian-release/2012/11/msg00411.html [3] http://p11-glue.freedesktop.org/doc/storing-trust-policy/storing-trust-existing.html [4] https://www.imperialviolet.org/2012/01/30/mozillaroots.html [5] https://github.com/agl/extract-nss-root-certs/blob/master/convert_mozilla_certdata.go#L251 [6] https://bitbucket.org/tiran/storeroom/src/e24eef16ff64041ab7792a907f0d69f7b19cd624/certdata/certs.py?at=default#cl-4411 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1207004/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1644189] Re: Shell doesn't know when base display config has changed
** Changed in: miral Milestone: None => 1.5 ** Changed in: qtmir (Ubuntu) Assignee: Alan Griffiths (alan-griffiths) => (unassigned) ** Changed in: qtmir (Ubuntu) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1644189 Title: Shell doesn't know when base display config has changed Status in Mir: Fix Released Status in MirAL: In Progress Status in mir package in Ubuntu: Fix Released Status in qtmir package in Ubuntu: Won't Fix Bug description: Privileged clients can change the server base display configuration. Shell wants to know when the base config is committed to a valid config (as opposed to a preview), in order to save that config to disk, to be applied again on restart. I cannot see any API for shell to learn when base config is changed. Closest is the AuthorizingDisplayChanger, but that is private. Really, all we want is a callback on - base config set to new config (applied, not previewed) Would also be nice to know: - base config has changed to preview a new config - base config preview cancelled To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1644189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705651] [NEW] blinking screen in laptop
Public bug reported: sometime in my laptop ,when I on it while long time (4-5 day) it started to blinking and after sometime(2-3 hour) problem is automatically solved, or become less frequent. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.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:Unity7 Date: Fri Jul 21 13:27:12 2017 DistUpgraded: 2017-04-19 14:23:43,826 DEBUG icon theme changed, re-reading DistroCodename: zesty DistroVariant: ubuntu 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-03-09 (133 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=91858ffc-a851-4b91-8927-312dbc0d0442 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to zesty on 2017-04-19 (92 days ago) dmi.bios.date: 08/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 08TMHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron3537:pvrA09:rvnDellInc.:rn08TMHK:rvrA00:cvnDellInc.:ct8:cvrA09: dmi.product.name: Inspiron 3537 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu zesty -- 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/1705651 Title: blinking screen in laptop Status in xorg package in Ubuntu: New Bug description: sometime in my laptop ,when I on it while long time (4-5 day) it started to blinking and after sometime(2-3 hour) problem is automatically solved, or become less frequent. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.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:Unity7 Date: Fri Jul 21 13:27:12 2017 DistUpgraded: 2017-04-19 14:23:43,826 DEBUG icon theme changed, re-reading DistroCodename: zesty DistroVariant: ubuntu 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-03-09 (133 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=91858ffc-a851-4b91-8927-312dbc0d0442 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to zesty on 2017-04-19 (92 days ago) dmi.bios.date: 08/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 08TMHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron3537:pvrA09:rvnDellInc.:rn08TMHK:rvrA00:cvnDellInc.:ct8:cvrA09: dmi.product.name: Inspiron 3537 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs:
[Touch-packages] [Bug 1705551] Re: close lid suspends correctly and wakealarm resumes from suspend to run cron jobs but opening lid reveals no display
Hi, you said "all sorts of keyboard combinations" but maybe it is worth a try. I had a similar case where it actually enabled the display, but at brightness 0 - you might not accidentally have the same case? I could get it on by using the FN keys to increase brightness in those cases. Another question would be if you never close the lid, but suspend via SW. And next day you wakeup via the alarm (while the lid was still open when sleeping) - is it then waking up normally with display enabled? Finally - I beg your pardon as I'm not an expert on this - but the following could enable it. You might need tweaks to actually "reach" your xorg, but I'm sure you can do that. Once you did call: $ xset dpms force off That should disable the power saving blank that your screen is in. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1705551 Title: close lid suspends correctly and wakealarm resumes from suspend to run cron jobs but opening lid reveals no display Status in pm-utils package in Ubuntu: Incomplete Bug description: [Problem] When I close the laptop lid, pm-action runs the following code which I have added: sh -c "echo 0 > /sys/class/rtc/rtc0/wakealarm" # clear alarm sh -c "echo `date '+%s' -d '7am next day + 30 minutes'` > /sys/class/rtc/rtc0/wakealarm" # set alarm and then suspends. At 7:30 AM the next day, the laptop resumes from suspend with the lid closed and executes cron jobs (e.g. some backups). If I open the lid then there is no display. I tried several options to resume the display: - [FAILS] all sorts of keyboard combinations - [FAILS] ssh -X into laptop and execute "sudo -u bierre env DISPLAY=:0 /usr/bin/xrandr --auto" (n.b. when I run "sudo -u bierre env" there is no DISPLAY variable) - [MANUAL HACK] closing the lid causes the laptop to suspend and then opening the lid causes it to resume with a normal working display I would like a solution or SOFTWARE HACK which I could add to /usr/lib /pm-utils/sleep.d/99video during resume from suspend triggered by wakealarm so that opening the lid would reveal a working display. [Laptop System Information] laptop = MacBookPro5,5 pm-utils version = 1.4.1-13ubuntu0.2 kernel = Linux version 3.19.0-32-generic (buildd@lgw01-43) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 UTC 2015 OS = "Linux Mint 17.3 Rosa" based on "14.04.3 LTS, Trusty Tahr" desktop environment = XFCE video card = NVIDIA Corporation C79 [GeForce 9400M] (rev b1) (prog-if 00 [VGA controller]) video driver = [633938.944] (II) NOUVEAU(0): Output LVDS-1 [Additional Information] After my cron backup job is finished it will check if the lid is closed. If it is closed then it will run pm-suspend. If I then open the lid, the laptop resumes with a normal working display. So the problem of no visible display occurs only when I open the lid after resume from wakealarm and before the backup job suspends the laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1705551/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705551] Re: close lid suspends correctly and wakealarm resumes from suspend to run cron jobs but opening lid reveals no display
incomplete - waiting for more feedback ** Changed in: pm-utils (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1705551 Title: close lid suspends correctly and wakealarm resumes from suspend to run cron jobs but opening lid reveals no display Status in pm-utils package in Ubuntu: Incomplete Bug description: [Problem] When I close the laptop lid, pm-action runs the following code which I have added: sh -c "echo 0 > /sys/class/rtc/rtc0/wakealarm" # clear alarm sh -c "echo `date '+%s' -d '7am next day + 30 minutes'` > /sys/class/rtc/rtc0/wakealarm" # set alarm and then suspends. At 7:30 AM the next day, the laptop resumes from suspend with the lid closed and executes cron jobs (e.g. some backups). If I open the lid then there is no display. I tried several options to resume the display: - [FAILS] all sorts of keyboard combinations - [FAILS] ssh -X into laptop and execute "sudo -u bierre env DISPLAY=:0 /usr/bin/xrandr --auto" (n.b. when I run "sudo -u bierre env" there is no DISPLAY variable) - [MANUAL HACK] closing the lid causes the laptop to suspend and then opening the lid causes it to resume with a normal working display I would like a solution or SOFTWARE HACK which I could add to /usr/lib /pm-utils/sleep.d/99video during resume from suspend triggered by wakealarm so that opening the lid would reveal a working display. [Laptop System Information] laptop = MacBookPro5,5 pm-utils version = 1.4.1-13ubuntu0.2 kernel = Linux version 3.19.0-32-generic (buildd@lgw01-43) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 UTC 2015 OS = "Linux Mint 17.3 Rosa" based on "14.04.3 LTS, Trusty Tahr" desktop environment = XFCE video card = NVIDIA Corporation C79 [GeForce 9400M] (rev b1) (prog-if 00 [VGA controller]) video driver = [633938.944] (II) NOUVEAU(0): Output LVDS-1 [Additional Information] After my cron backup job is finished it will check if the lid is closed. If it is closed then it will run pm-suspend. If I then open the lid, the laptop resumes with a normal working display. So the problem of no visible display occurs only when I open the lid after resume from wakealarm and before the backup job suspends the laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1705551/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705642] Re: [libgtk-3-doc] FIXME: MISSING XINCLUDE CONTENT
** Package changed: gnome-software (Ubuntu) => gtk+3.0 (Ubuntu) -- 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/1705642 Title: [libgtk-3-doc] FIXME: MISSING XINCLUDE CONTENT Status in gtk+3.0 package in Ubuntu: New Bug description: Run commands: apt-get install libgtk-3-doc firefox /usr/share/doc/libgtk-3-doc/gtk3/gtk-getting-started.html Read page. Instead of some content the message "FIXME: MISSING XINCLUDE CONTENT" showed. Please, rebuild package "libgtk-3-doc" correctly. Expected behaviour: show valid content instead of message "FIXME: MISSING XINCLUDE CONTENT". File name: pool/main/g/gtk+3.0/libgtk-3-doc_3.18.9-1ubuntu3.3_all.deb. OS: Ubuntu 16.04 (xenial). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1705642/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705642] [NEW] [libgtk-3-doc] FIXME: MISSING XINCLUDE CONTENT
You have been subscribed to a public bug: Run commands: apt-get install libgtk-3-doc firefox /usr/share/doc/libgtk-3-doc/gtk3/gtk-getting-started.html Read page. Instead of some content the message "FIXME: MISSING XINCLUDE CONTENT" showed. Please, rebuild package "libgtk-3-doc" correctly. Expected behaviour: show valid content instead of message "FIXME: MISSING XINCLUDE CONTENT". File name: pool/main/g/gtk+3.0/libgtk-3-doc_3.18.9-1ubuntu3.3_all.deb. OS: Ubuntu 16.04 (xenial). ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- [libgtk-3-doc] FIXME: MISSING XINCLUDE CONTENT https://bugs.launchpad.net/bugs/1705642 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1696499] Re: dhclient segfaults on ubuntu 17.04
Workaround provided does not seem to work for me. It seems the dhclient binary only fails with Seg fault when it is at /sbin/dhclient, when it is moved to /usr/sbin/dhclient it works fine from command line. But this made nm-dhclient-helper to fail. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1696499 Title: dhclient segfaults on ubuntu 17.04 Status in isc-dhcp package in Ubuntu: Confirmed Bug description: After upgrading, network-manager stopped running DHCP, after trying to run dhclient myself I found out it segfaults. Attached is its strace output. I can connect to the internet by stopping network-manager and using ifconfig + route + /etc/resolv.conf. Output: guy@golem4:~$ dhclient Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1696499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574351] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other in
@Reuben your solution worked for me thx. Issue arised when simplescan said you need to update your drivers, and when i did it failed. Thx Ron -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1574351 Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 Status in perl package in Ubuntu: Confirmed Bug description: Don't run aplication after upgrade from 14.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libperl5.22 5.22.1-9 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 24 21:08:20 2016 DpkgTerminalLog: Preparing to unpack .../libperl5.22_5.22.1-9_i386.deb ... Unpacking libperl5.22:i386 (5.22.1-9) ... dpkg: error processing archive /var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 DuplicateSignature: Unpacking libperl5.22:i386 (5.22.1-9) ... dpkg: error processing archive /var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 InstallationDate: Installed on 2016-04-24 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: perl Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1574351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705636] [NEW] package initramfs-tools 0.125ubuntu9 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
Public bug reported: while upgrade failed that package ProblemType: Package DistroRelease: Ubuntu 17.10 Package: initramfs-tools 0.125ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic i686 ApportVersion: 2.20.5-0ubuntu5 Architecture: i386 Date: Fri Jul 21 06:30:59 2017 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5~beta1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.125ubuntu9 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package artful i386 -- 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/1705636 Title: package initramfs-tools 0.125ubuntu9 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 Status in initramfs-tools package in Ubuntu: New Bug description: while upgrade failed that package ProblemType: Package DistroRelease: Ubuntu 17.10 Package: initramfs-tools 0.125ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic i686 ApportVersion: 2.20.5-0ubuntu5 Architecture: i386 Date: Fri Jul 21 06:30:59 2017 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5~beta1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.125ubuntu9 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1705636/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack
** Changed in: virtualbox-hwe (Ubuntu) Status: New => Fix Committed ** Changed in: virtualbox-hwe (Ubuntu) Assignee: (unassigned) => LocutusOfBorg (costamagnagianfranco) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in virtualbox-hwe package in Ubuntu: Fix Committed Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: New Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in libinput source package in Xenial: Fix Committed Status in libwacom source package in Xenial: Fix Committed Status in libxfont source package in Xenial: Fix Committed Status in libxfont2 source package in Xenial: Fix Committed Status in llvm-toolchain-4.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in vulkan source package in Xenial: Fix Committed Status in wayland source package in Xenial: Fix Committed Status in x11proto-core source package in Xenial: Fix Committed Status in xfonts-utils source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server source package in Xenial: Invalid Status in xorg-server-hwe-16.04 source package in Xenial: Fix Committed Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp