[Touch-packages] [Bug 1779601] Re: Update manager
Indeed, this doesn't sound like a bug. If you need to resize a partition you can do so with: 1. sudo apt install gparted 2. sudo gparted ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- 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/1779601 Title: Update manager Status in Ubuntu: Invalid Bug description: I don't know if it is a bug, probably not. Software doesn't get updated automatically because of low disk space. I´ve tried to resize the partitioning but I have not managed to do it, and I don't know where to find out how it is done. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.13 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jul 2 07:27:17 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated Graphics Controller [144d:c06d] Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated Graphics Controller [144d:c06d] InstallationDate: Installed on 2016-10-28 (611 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 05JD.M017.20100325.KSJ dmi.board.name: R530/R730 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr05JD.M017.20100325.KSJ:bd03/25/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R530/R730 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 3 20:25:43 2018 xserver.configfile: default xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19 SynPS/2 Synaptics TouchPad: Read error 19 SynPS/2 Synaptics TouchPad: Read error 19 SynPS/2 Synaptics TouchPad: Read error 19 SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5760 vendor CMO xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779601/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779601] [NEW] Update manager
Public bug reported: I don't know if it is a bug, probably not. Software doesn't get updated automatically because of low disk space. I´ve tried to resize the partitioning but I have not managed to do it, and I don't know where to find out how it is done. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.13 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jul 2 07:27:17 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated Graphics Controller [144d:c06d] Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated Graphics Controller [144d:c06d] InstallationDate: Installed on 2016-10-28 (611 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: SAMSUNG ELECTRONICS CO., LTD. R530/R730 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2010 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 05JD.M017.20100325.KSJ dmi.board.name: R530/R730 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr05JD.M017.20100325.KSJ:bd03/25/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnR530/R730:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR530/R730:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.name: R530/R730 dmi.product.version: Not Applicable dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 3 20:25:43 2018 xserver.configfile: default xserver.errors: SynPS/2 Synaptics TouchPad: Read error 19 SynPS/2 Synaptics TouchPad: Read error 19 SynPS/2 Synaptics TouchPad: Read error 19 SynPS/2 Synaptics TouchPad: Read error 19 SynPS/2 Synaptics TouchPad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5760 vendor CMO xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1779601 Title: Update manager Status in xorg package in Ubuntu: New Bug description: I don't know if it is a bug, probably not. Software doesn't get updated automatically because of low disk space. I´ve tried to resize the partitioning but I have not managed to do it, and I don't know where to find out how it is done. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.13 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jul 2 07:27:17 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Mobile 4 Series Chipset Integrated Graphics Controller [144d:c06d] Subsystem: Samsung
[Touch-packages] [Bug 1779597] [NEW] [Satellite P55W-C, Realtek ALC233, Speaker, Internal] Pulseaudio fails to detect card
Public bug reported: It's related to a JBL Flip 2 bluetooth speaker. It worked perfectly in 16.04, in 18.04 the bluetooth speaker doesn't reconnect after a laptop suspend/resume cycle, I need to delete it from the bluetooth paired devices and repair it. Often the output sound device is missing, it only shows dummy. If I suspend while the bluetooth speaker is connected it's garanteed to disappear, but it sometimes disappears after I turn off the bluetooth speaker without suspending. Rebooting restores the output sound device and the internal speaker starts working again. I'm happy to provide further info and do some testing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 Uname: Linux 4.17.3-041703-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 2 13:53:42 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-21 (740 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [Satellite P55W-C, Realtek ALC233, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to bionic on 2018-03-17 (106 days ago) dmi.bios.date: 07/26/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.00 dmi.board.name: 0693 dmi.board.vendor: FF40 dmi.board.version: 2.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.00:bd07/26/2015:svnTOSHIBA:pnSatelliteP55W-C:pvrPSPVTU-004001B:rvnFF40:rn0693:rvr2.0:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: PEGA Family dmi.product.name: Satellite P55W-C dmi.product.version: PSPVTU-004001B dmi.sys.vendor: TOSHIBA ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1779597 Title: [Satellite P55W-C, Realtek ALC233, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: It's related to a JBL Flip 2 bluetooth speaker. It worked perfectly in 16.04, in 18.04 the bluetooth speaker doesn't reconnect after a laptop suspend/resume cycle, I need to delete it from the bluetooth paired devices and repair it. Often the output sound device is missing, it only shows dummy. If I suspend while the bluetooth speaker is connected it's garanteed to disappear, but it sometimes disappears after I turn off the bluetooth speaker without suspending. Rebooting restores the output sound device and the internal speaker starts working again. I'm happy to provide further info and do some testing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 Uname: Linux 4.17.3-041703-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 2 13:53:42 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-21 (740 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [Satellite P55W-C, Realtek ALC233, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to bionic on 2018-03-17 (106 days ago) dmi.bios.date: 07/26/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.00 dmi.board.name: 0693 dmi.board.vendor: FF40 dmi.board.version: 2.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.00:bd07/26/2015:svnTOSHIBA:pnSatelliteP55W-C:pvrPSPVTU-004001B:rvnFF40:rn0693:rvr2.0:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: PEGA Family dmi.product.name: Satellite P55W-C dmi.product.version: PSPVTU-004001B dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1779597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779597] Re: [Satellite P55W-C, Realtek ALC233, Speaker, Internal] Pulseaudio fails to detect card
Oh, and I upgraded the kernel with ukuu, it also happens with the kernel in 18.04 -- 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/1779597 Title: [Satellite P55W-C, Realtek ALC233, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: It's related to a JBL Flip 2 bluetooth speaker. It worked perfectly in 16.04, in 18.04 the bluetooth speaker doesn't reconnect after a laptop suspend/resume cycle, I need to delete it from the bluetooth paired devices and repair it. Often the output sound device is missing, it only shows dummy. If I suspend while the bluetooth speaker is connected it's garanteed to disappear, but it sometimes disappears after I turn off the bluetooth speaker without suspending. Rebooting restores the output sound device and the internal speaker starts working again. I'm happy to provide further info and do some testing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 Uname: Linux 4.17.3-041703-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 2 13:53:42 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-21 (740 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [Satellite P55W-C, Realtek ALC233, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to bionic on 2018-03-17 (106 days ago) dmi.bios.date: 07/26/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.00 dmi.board.name: 0693 dmi.board.vendor: FF40 dmi.board.version: 2.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.00:bd07/26/2015:svnTOSHIBA:pnSatelliteP55W-C:pvrPSPVTU-004001B:rvnFF40:rn0693:rvr2.0:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: PEGA Family dmi.product.name: Satellite P55W-C dmi.product.version: PSPVTU-004001B dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1779597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768314] Re: Impossible to sign into launchpad
[Expired for software-properties (Ubuntu) because there has been no activity for 60 days.] ** Changed in: software-properties (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1768314 Title: Impossible to sign into launchpad Status in software-properties package in Ubuntu: Expired Bug description: I am using xubuntu and i wanted to use the live kernel update feature because I rarely reboot my system Well sadly it is not possible to sign into launchpad on xubuntu in software-properties-gtk I tried installing gnome-control-center and that did make the button work, but the application is empty, the window has no content ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Tue May 1 13:50:05 2018 InstallationDate: Installed on 2018-04-29 (2 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1768314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 778007] Re: apport-gtk crashed when I wanted to trace a dead process
Hello Denes, Thank you for submitting this bug and reporting a problem with the apport package. You made this bug report in 2011 and there have been several versions of Ubuntu since then. Could you confirm that this is no longer a problem and that we can close the ticket? Thank you again for helping make Ubuntu better. G ** Changed in: apport (Ubuntu) Status: New => Incomplete -- 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/778007 Title: apport-gtk crashed when I wanted to trace a dead process Status in apport package in Ubuntu: Incomplete Bug description: Binary package hint: apport root@ds-desktop:~# ps aux | grep thunderbird root 2811 0.0 0.0 5588 856 pts/1R+ 19:07 0:00 grep --color=auto thunderbird ds2866 0.0 0.0 1912 512 ?S08:55 0:00 /bin/sh /usr/lib/thunderbird-3.1.9/thunderbird ds2871 0.0 0.0 1912 516 ?S08:55 0:00 /bin/sh /usr/lib/thunderbird-3.1.9/run-mozilla.sh /usr/lib/thunderbird-3.1.9/thunderbird-bin ds2875 9.8 2.1 457932 88340 ?Rl 08:55 60:09 /usr/lib/thunderbird-3.1.9/thunderbird-bin root@ds-desktop:~# apport-bug 2875 Traceback (most recent call last): File "/usr/share/apport/apport-gtk", line 369, in app.run_argv() File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 568, in run_argv return self.run_report_bug() File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 347, in run_report_bug self.report.add_proc_info(self.options.pid) File "/usr/lib/python2.7/dist-packages/apport/report.py", line 359, in add_proc_info assert os.path.exists(self['ExecutablePath']) AssertionError To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/778007/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779592] Re: I have video lagging errors
It appears your screen is 1366x768 and the CPU/GPU is an i5-4200U. I would not expect any performance problems with those. Can you please elaborate as to what you mean by "lagging"? Do you mean everything is smooth but delayed? Or do you mean it is stuttering (skipping frames)? ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Tags added: performance -- 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/1779592 Title: I have video lagging errors Status in gnome-shell package in Ubuntu: Incomplete Bug description: In browser (Chrome) and VLC. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 1 20:03:55 2018 DistUpgraded: 2018-04-29 10:40:39,012 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DpkgLog: 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:05f3] InstallationDate: Installed on 2018-04-21 (71 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Dell Inc. Inspiron 5437 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=86eb9f96-102c-4576-a37c-b2a420b78479 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-04-29 (63 days ago) dmi.bios.date: 09/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0DM6M9 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA04:bd09/06/2013:svnDellInc.:pnInspiron5437:pvrNotSpecified:rvnDellInc.:rn0DM6M9:rvrA04:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 5437 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1779592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779289] Re: [regression] bluetooth mouse not reconnected on reboot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-bluetooth (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1779289 Title: [regression] bluetooth mouse not reconnected on reboot Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: This affects at least 2 different bluetooth mice(both logitech) The behavior is that initial config when using the gui works but that the resulting "/var/lib/bluetooth///info" file does not contain a [LinkKey] section as the mouse does not require a pin. This mouse was connection on reboot under 16.04 so it's a new bug for 18.04 When setting up the mouse using bluetoothctl the info file is correctly written with a [LinkKey] section and everything works, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-bluetooth 3.28.0-2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 29 11:27:27 2018 InstallationDate: Installed on 2018-06-27 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779485] Re: bluetooth not saving mouse connection. Having to reconnect each ubuntu start.
*** This bug is a duplicate of bug 1779289 *** https://bugs.launchpad.net/bugs/1779289 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1779289, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1779289 [regression] bluetooth mouse not reconnected on reboot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1779485 Title: bluetooth not saving mouse connection. Having to reconnect each ubuntu start. Status in bluez package in Ubuntu: New Bug description: Each time I start Ubuntu, I have to turn the mouse on. Version 18.04 is not saving the setting. I don't remember having this problem with previous versions of Ubuntu. Last version I used was 16.04.4. Please fix, it's really annoying. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 30 12:39:30 2018 InstallationDate: Installed on 2018-06-26 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Sony Corporation VPCSC41FM ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=3bf4784c-157a-4e30-a49b-8f1a34d4f64c ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2012 dmi.bios.vendor: INSYDE dmi.bios.version: R2087H4 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDE:bvrR2087H4:bd06/15/2012:svnSonyCorporation:pnVPCSC41FM:pvrC60A8X35:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCSC41FM dmi.product.version: C60A8X35 dmi.sys.vendor: Sony Corporation hciconfig: hci0:Type: Primary Bus: USB BD Address: 64:27:37:CA:4D:B1 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:16064 acl:815 sco:0 events:143 errors:0 TX bytes:6645 acl:47 sco:0 commands:81 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779289] Re: [regression] bluetooth mouse not reconnected on reboot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1779289 Title: [regression] bluetooth mouse not reconnected on reboot Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: This affects at least 2 different bluetooth mice(both logitech) The behavior is that initial config when using the gui works but that the resulting "/var/lib/bluetooth///info" file does not contain a [LinkKey] section as the mouse does not require a pin. This mouse was connection on reboot under 16.04 so it's a new bug for 18.04 When setting up the mouse using bluetoothctl the info file is correctly written with a [LinkKey] section and everything works, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-bluetooth 3.28.0-2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 29 11:27:27 2018 InstallationDate: Installed on 2018-06-27 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779411] Re: info about bug appeared on screen earlier today
It sounds like some part of the system has crashed. Please: 1. Apply the workaround from bug 994921. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash and tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the contents of the /var/lib/whoopsie/whoopsie-id file on the machine. Do you find any links to recent problems on the machine? If so then please send them to us. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1779411 Title: info about bug appeared on screen earlier today Status in xorg package in Ubuntu: Incomplete Bug description: i was watching hawaiian volcano videos this morning and the screen locked up. i restarted the computer and the error message appeared(error with 18.04 was the message). however, prior to that, grub appeared to show a problem beginning to form about a week ago. grub used to be a short startup leading to give me a choice of which hard drive i wanted to begin with(1 tb wd black and a 250gb samsung ssd. both drives have linux 18.04, one ubuntu and one kubuntu. only the ubuntu is acting up. for the past two days, grub is showing me every line of the startup process, although the ubuntu is otherwise starting normally. i know enough to enter code correctly in the terminal(e.g. sudo apt-get upgrade etc) and like the simplicity and independence of linux but regret that i must have the code spelled out for me if mistakes are to be avoided. i'm old and don't mind admitting it. hope this helps. cheers. paul. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Fri Jun 29 13:48:50 2018 DistUpgraded: 2018-06-05 12:53:32,893 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4250] [1002:9715] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS880 [Radeon HD 4250] [1458:d000] InstallationDate: Installed on 2015-05-30 (1125 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Gigabyte Technology Co., Ltd. GA-880GM-UD2H ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=1b13c61c-0cc4-4160-9da5-fddeca76ae93 ro SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-06-05 (24 days ago) dmi.bios.date: 03/24/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: GA-880GM-UD2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd03/24/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GM-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GM-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GM-UD2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Jun 5 08:12:34 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1779411/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779332] Re: Screen Resolution changed with update. I cant use Native Resolution. Drivers Problem? Xorg Problem?
The attached files seem to show your screen is 1280x800. Is that not the native resolution you were expecting? Also, please attach a photo of the problem. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1779332 Title: Screen Resolution changed with update. I cant use Native Resolution. Drivers Problem? Xorg Problem? Status in xorg-server package in Ubuntu: Incomplete Bug description: I cant use my native resolution on laptop screen. New update appeared, then screen resolution changed automatically to a smaller size. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Fri Jun 29 10:56:57 2018 DistUpgraded: 2018-05-08 03:09:35,233 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox-modules-ashmem, 10.1~20180523.2.bionic.c36965f, 4.15.0-22-generic, x86_64: installed anbox-modules-ashmem, 10.1~20180523.2.bionic.c36965f, 4.15.0-23-generic, x86_64: installed anbox-modules-binder, 10.1~20180523.2.bionic.c36965f, 4.15.0-22-generic, x86_64: installed anbox-modules-binder, 10.1~20180523.2.bionic.c36965f, 4.15.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c606] InstallationDate: Installed on 2018-01-14 (165 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20180106) MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E4A/300E5A/300E7A/3430EA/3530EA ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=dd5ac09e-8460-4af0-af7f-5829c8b303cd ro quiet splash drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-05-08 (52 days ago) dmi.bios.date: 04/20/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 07QA dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 300E4A/300E5A/300E7A/3430EA/3530EA dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr07QA:bd04/20/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E4A/300E5A/300E7A/3430EA/3530EA:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn300E4A/300E5A/300E7A/3430EA/3530EA:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: 300E4A/300E5A/300E7A/3430EA/3530EA dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Jun 29 10:55:12 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputDP-1 HDMI-1 LVDS-1 VGA-1 xserver.version: 2:1.19.6-1ubuntu4 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1779332/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779289] Re: bluetooth mouse not reconeected on reboot
** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Summary changed: - bluetooth mouse not reconeected on reboot + [regression] bluetooth mouse not reconeected on reboot ** Summary changed: - [regression] bluetooth mouse not reconeected on reboot + [regression] bluetooth mouse not reconnected on reboot ** Tags added: regression-release -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1779289 Title: [regression] bluetooth mouse not reconnected on reboot Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Bug description: This affects at least 2 different bluetooth mice(both logitech) The behavior is that initial config when using the gui works but that the resulting "/var/lib/bluetooth///info" file does not contain a [LinkKey] section as the mouse does not require a pin. This mouse was connection on reboot under 16.04 so it's a new bug for 18.04 When setting up the mouse using bluetoothctl the info file is correctly written with a [LinkKey] section and everything works, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-bluetooth 3.28.0-2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 29 11:27:27 2018 InstallationDate: Installed on 2018-06-27 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779434] Re: Color is no longer correct. Reds are tinted orange.
"Reds are tinted orange" could be a couple of different issues I can think of. Here are some possibilities: 1. Reds that look bright orange may be unexpected, but in some cases are actually correct. This is a common finding for users first moving to high quality monitors with a wide colour gamut. So in this case isn't a bug at all. But regardless, if you want to change it then please see: System Settings > Device Color Profiles Now select your display and add/remove colour profiles to suit your preference. 2. Something has accidentally triggered a change in the colour profile in software. Again see: System Settings > Device Color Profiles and remove all profiles you find attached to your display. 3. Maybe some regression happened. Did the problem appear recently in an update or only after you upgraded the whole OS? Please also take a photo of the issue, preferably of the default Ubuntu desktop. ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Package changed: xorg (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1779434 Title: Color is no longer correct. Reds are tinted orange. Status in Ubuntu: Incomplete Bug description: Color is no longer correct. Reds are tinted orange. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jun 29 20:29:07 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: openafs, 1.6.15: added ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:2217] InstallationDate: Installed on 2018-03-01 (120 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 20CDS02B00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic root=UUID=15a31849-cfa8-4cce-809b-fdbfa98173f2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: LENOVO dmi.bios.version: GQET51WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CDS02B00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGQET51WW(1.31):bd03/08/2017:svnLENOVO:pn20CDS02B00:pvrThinkPadS1Yoga:rvnLENOVO:rn20CDS02B00:rvrSDK0E50512Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad S1 Yoga dmi.product.name: 20CDS02B00 dmi.product.version: ThinkPad S1 Yoga dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-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: Fri Jun 29 20:04:28 2018 xserver.configfile: default xserver.errors: Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device. Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device. Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779434/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779434] Re: Color is no longer correct. Reds are tinted orange.
** Summary changed: - Graphics Issue + Color is no longer correct. Reds are tinted orange. -- 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/1779434 Title: Color is no longer correct. Reds are tinted orange. Status in xorg package in Ubuntu: New Bug description: Color is no longer correct. Reds are tinted orange. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jun 29 20:29:07 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: openafs, 1.6.15: added ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:2217] InstallationDate: Installed on 2018-03-01 (120 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 20CDS02B00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic root=UUID=15a31849-cfa8-4cce-809b-fdbfa98173f2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: LENOVO dmi.bios.version: GQET51WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CDS02B00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 Std dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGQET51WW(1.31):bd03/08/2017:svnLENOVO:pn20CDS02B00:pvrThinkPadS1Yoga:rvnLENOVO:rn20CDS02B00:rvrSDK0E50512Std:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad S1 Yoga dmi.product.name: 20CDS02B00 dmi.product.version: ThinkPad S1 Yoga dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-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: Fri Jun 29 20:04:28 2018 xserver.configfile: default xserver.errors: Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device. Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device. Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1779434/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779583] Re: cron do_command.c attempts a fork() without testing for errors
The attachment "Compiling fix to second fork() in child_process()" 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.]
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1779583
Title:
cron do_command.c attempts a fork() without testing for errors
Status in cron package in Ubuntu:
New
Bug description:
The do_command.c file calls fork() twice.
For the first fork(), the possibility for an error is checked properly
and an error emitted (see
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785 for an
example when that happens: message is "can't fork".) This first fork()
makes use of a switch() statement as expected.
The second fork(), however, is used inside an if() statement like
this:
if (*input_data && fork() == 0) { ... }
Here we can see a couple of problems. After the if block, we have this
statement:
children++;
which means that we will have to wait on TWO children. However, (1)
the *input_data could return false and thus the second child may not
be created at all. (2) the fork() could return -1 meaning that no
other child is created.
I suppose that the child_process() probably always or nearly always
has some input_data. Otherwise it would block waiting for a child that
was never started. And of course, it is relatively rare that fork()
fails, unless you are running our of RAM (heap or stack can't be
allocated) or process space (too many processes running concurrently.)
I have a proposed patch to fix the problem. It uses a switch() which
emits an error in case the fork() fails, but let the program go on as
before (instead of an immediate exit as in the first fork()).
The children variable gets incremented only when the fork() happens
and succeeds (default: block in the new switch().)
The do_command.c file did not change between 16.04 (trusty) and 18.04
(bionic beaver), so the patch will work for either version.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779583/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779592] [NEW] I have video lagging errors
Public bug reported: In browser (Chrome) and VLC. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 1 20:03:55 2018 DistUpgraded: 2018-04-29 10:40:39,012 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DpkgLog: 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:05f3] InstallationDate: Installed on 2018-04-21 (71 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Dell Inc. Inspiron 5437 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=86eb9f96-102c-4576-a37c-b2a420b78479 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-04-29 (63 days ago) dmi.bios.date: 09/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0DM6M9 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA04:bd09/06/2013:svnDellInc.:pnInspiron5437:pvrNotSpecified:rvnDellInc.:rn0DM6M9:rvrA04:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 5437 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1779592 Title: I have video lagging errors Status in xorg package in Ubuntu: New Bug description: In browser (Chrome) and VLC. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 1 20:03:55 2018 DistUpgraded: 2018-04-29 10:40:39,012 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DpkgLog: 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:05f3] InstallationDate: Installed on 2018-04-21 (71 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Dell Inc. Inspiron 5437 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=86eb9f96-102c-4576-a37c-b2a420b78479 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-04-29 (63 days ago) dmi.bios.date: 09/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0DM6M9 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA04:bd09/06/2013:svnDellInc.:pnInspiron5437:pvrNotSpecified:rvnDellInc.:rn0DM6M9:rvrA04:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 5437 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
[Touch-packages] [Bug 1779129] Re: package libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux-gnu/libfdisk.so.1.1.0] failed to install/upgrade: package libfdisk1:amd64 is not ready for conf
** Package changed: util-linux (Ubuntu) => apt (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1779129 Title: package libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux- gnu/libfdisk.so.1.1.0] failed to install/upgrade: package libfdisk1:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in apt package in Ubuntu: New Bug description: i was installing latex-maker and as it ended i got that error. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux-gnu/libfdisk.so.1.1.0] ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu Jun 28 07:03:23 2018 DpkgTerminalLog: dpkg: error processing package libfdisk1:amd64 (--configure): package libfdisk1:amd64 is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package libfdisk1:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-06-18 (10 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: util-linux Title: package libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux-gnu/libfdisk.so.1.1.0] failed to install/upgrade: package libfdisk1:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1779129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771236] Re: forced use of systemd-networkd interferes with ifupdown in 18.04
Sigh. After I push my /etc/network/interfaces from ansible (not the stub one I previously posted) - "something" is re-reading it and applying settings. This never happened in 16.04 until an ifup/ifdown, service restart or reboot (which is what I expect and need). Not quite sure how to find the culprit. But this is breaking my ansible flow in the middle of the playbook as I lose the network config that Vmware put in. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1771236 Title: forced use of systemd-networkd interferes with ifupdown in 18.04 Status in ifupdown package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: For several reasons, we are not able to use netplan nor systemd- networkd due to legacy applications that expect ifupdown's pre-up and post-up script mechanism. The documentation around 18.04's (premature, I feel) wholesale adoption of netplan claims that one can revert to old behaviour by merely installing ifupdown (amongst assertions that netplan will never offer a mechanism for configuring pre-up and post-up actions even for network managers that support them). However when ifupdown is installed, systemd-networkd still tries to manage interfaces. If you 'systemctl disable systemd-networkd', upon next reboot it is automatically re-enabled. We tried disabling any systemd units even remotely related to networking and yet systemd- networkd still runs. If it hasn't been configured, it tries to DHCP. On networks that don't provide DHCP this results in a stupendously long stall during boot. Currently it appears to be impossible to tell systemd-networkd not to run in a clean manner that won't get reverted on package upgrades. I sincerely hope this is is a bug/oversight and not intentional. We need to be able to disable systemd-networkd properly. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1771236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779583] Re: cron do_command.c attempts a fork() without testing for errors
I guess I should attempt to compile before submitting a patch. Some
brackets were required in one of the cases.
** Patch added: "Compiling fix to second fork() in child_process()"
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779583/+attachment/5158458/+files/do_command-2.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1779583
Title:
cron do_command.c attempts a fork() without testing for errors
Status in cron package in Ubuntu:
New
Bug description:
The do_command.c file calls fork() twice.
For the first fork(), the possibility for an error is checked properly
and an error emitted (see
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785 for an
example when that happens: message is "can't fork".) This first fork()
makes use of a switch() statement as expected.
The second fork(), however, is used inside an if() statement like
this:
if (*input_data && fork() == 0) { ... }
Here we can see a couple of problems. After the if block, we have this
statement:
children++;
which means that we will have to wait on TWO children. However, (1)
the *input_data could return false and thus the second child may not
be created at all. (2) the fork() could return -1 meaning that no
other child is created.
I suppose that the child_process() probably always or nearly always
has some input_data. Otherwise it would block waiting for a child that
was never started. And of course, it is relatively rare that fork()
fails, unless you are running our of RAM (heap or stack can't be
allocated) or process space (too many processes running concurrently.)
I have a proposed patch to fix the problem. It uses a switch() which
emits an error in case the fork() fails, but let the program go on as
before (instead of an immediate exit as in the first fork()).
The children variable gets incremented only when the fork() happens
and succeeds (default: block in the new switch().)
The do_command.c file did not change between 16.04 (trusty) and 18.04
(bionic beaver), so the patch will work for either version.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779583/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779583] Re: cron do_command.c attempts a fork() without testing for errors
** Description changed:
The do_command.c file calls fork() twice.
- For the first for(), the possibility for an error is checked properly
+ For the first fork(), the possibility for an error is checked properly
and an error emitted (see
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785 for an
example when that happens: message is "can't fork".) This first fork()
makes use of a switch() statement as expected.
The second fork(), however, is used inside an if() statement like this:
if (*input_data && fork() == 0) { ... }
Here we can see a couple of problems. After the if block, we have this
statement:
children++;
which means that we will have to wait on TWO children. However, (1) the
*input_data could return false and thus the second child may not be
created at all. (2) the fork() could return -1 meaning that no other
child is created.
I suppose that the child_process() probably always or nearly always has
some input_data. Otherwise it would block waiting for a child that was
never started. And of course, it is relatively rare that fork() fails,
unless you are running our of RAM (heap or stack can't be allocated) or
process space (too many processes running concurrently.)
I have a proposed patch to fix the problem. It uses a switch() which
emits an error in case the fork() fails, but let the program go on as
before (instead of an immediate exit as in the first fork()).
The children variable gets incremented only when the fork() happens and
succeeds (default: block in the new switch().)
The do_command.c file did not change between 16.04 (trusty) and 18.04
(bionic beaver), so the patch will work for either version.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1779583
Title:
cron do_command.c attempts a fork() without testing for errors
Status in cron package in Ubuntu:
New
Bug description:
The do_command.c file calls fork() twice.
For the first fork(), the possibility for an error is checked properly
and an error emitted (see
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785 for an
example when that happens: message is "can't fork".) This first fork()
makes use of a switch() statement as expected.
The second fork(), however, is used inside an if() statement like
this:
if (*input_data && fork() == 0) { ... }
Here we can see a couple of problems. After the if block, we have this
statement:
children++;
which means that we will have to wait on TWO children. However, (1)
the *input_data could return false and thus the second child may not
be created at all. (2) the fork() could return -1 meaning that no
other child is created.
I suppose that the child_process() probably always or nearly always
has some input_data. Otherwise it would block waiting for a child that
was never started. And of course, it is relatively rare that fork()
fails, unless you are running our of RAM (heap or stack can't be
allocated) or process space (too many processes running concurrently.)
I have a proposed patch to fix the problem. It uses a switch() which
emits an error in case the fork() fails, but let the program go on as
before (instead of an immediate exit as in the first fork()).
The children variable gets incremented only when the fork() happens
and succeeds (default: block in the new switch().)
The do_command.c file did not change between 16.04 (trusty) and 18.04
(bionic beaver), so the patch will work for either version.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779583/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771236] Re: forced use of systemd-networkd interferes with ifupdown in 18.04
So from the troubleshooting and testing I just did, it seems like (at
least) I had to do the following:
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
and
mv /etc/netplan/50-cloud-init.yaml /etc/netplan/50-cloud-
init.yaml.disabled
Before taking these two steps, I kept getting a DHCP address on my
interface. After doing this and rebooting, I finally have an interface
that is simply "UP" - as configured in my /etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
auto ens160
iface ens160 inet manual
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1771236
Title:
forced use of systemd-networkd interferes with ifupdown in 18.04
Status in ifupdown package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
Incomplete
Bug description:
For several reasons, we are not able to use netplan nor systemd-
networkd due to legacy applications that expect ifupdown's pre-up and
post-up script mechanism. The documentation around 18.04's
(premature, I feel) wholesale adoption of netplan claims that one can
revert to old behaviour by merely installing ifupdown (amongst
assertions that netplan will never offer a mechanism for configuring
pre-up and post-up actions even for network managers that support
them).
However when ifupdown is installed, systemd-networkd still tries to
manage interfaces. If you 'systemctl disable systemd-networkd', upon
next reboot it is automatically re-enabled. We tried disabling any
systemd units even remotely related to networking and yet systemd-
networkd still runs. If it hasn't been configured, it tries to DHCP.
On networks that don't provide DHCP this results in a stupendously
long stall during boot. Currently it appears to be impossible to tell
systemd-networkd not to run in a clean manner that won't get reverted
on package upgrades.
I sincerely hope this is is a bug/oversight and not intentional. We
need to be able to disable systemd-networkd properly.
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1771236/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771236] Re: forced use of systemd-networkd interferes with ifupdown in 18.04
Looking for an update on this - specifically the seemingly unanswered question of "does removing all netplan related config render systemd- netword 'toothless'". I too am very concerned that simply installing ifupdown doesn't by itself achieve the result that seems to be put forth by the various pieces of documentation and advice around these issues. I'm currently fighting vmware guest customizations on 18.04 (a whole other rabbit hole...) - but my current solution is in jeopardy if systemd-networkd is "touching" interfaces before I can get ansible to do it's thing. I'm currently testing and troubleshooting this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1771236 Title: forced use of systemd-networkd interferes with ifupdown in 18.04 Status in ifupdown package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: For several reasons, we are not able to use netplan nor systemd- networkd due to legacy applications that expect ifupdown's pre-up and post-up script mechanism. The documentation around 18.04's (premature, I feel) wholesale adoption of netplan claims that one can revert to old behaviour by merely installing ifupdown (amongst assertions that netplan will never offer a mechanism for configuring pre-up and post-up actions even for network managers that support them). However when ifupdown is installed, systemd-networkd still tries to manage interfaces. If you 'systemctl disable systemd-networkd', upon next reboot it is automatically re-enabled. We tried disabling any systemd units even remotely related to networking and yet systemd- networkd still runs. If it hasn't been configured, it tries to DHCP. On networks that don't provide DHCP this results in a stupendously long stall during boot. Currently it appears to be impossible to tell systemd-networkd not to run in a clean manner that won't get reverted on package upgrades. I sincerely hope this is is a bug/oversight and not intentional. We need to be able to disable systemd-networkd properly. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1771236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1702785] Re: High memory and "can't fork" on heavy long-lived cron daemon
Actually, an immediate fix for you guys may be to make sure that there
is some *input_data. I have no clue what that means in terms of
administrative setup, though. But maybe someone else can help in that
area. The really bad statement looks like this:
if (*input_data && fork() == 0) {
... // handle input_data
exit(0);
}
children++;
The children variable counts the number of successful fork()'s. Only in
this case (1) the fork() is never checked for failure and (2) if
*input_data is false, then the fork() does not even happen. Yet, either
way, children is always increment! Ouch! As an administrator, it may not
be possible to always make sure there is something in input_data. But it
is not unlikely that this is what makes many cron fork() wait forever
and thus increase memory. I have not had that problem on my end, I was
just reading the code for fun...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1702785
Title:
High memory and "can't fork" on heavy long-lived cron daemon
Status in cron package in Ubuntu:
Confirmed
Bug description:
Ubuntu 14.04.5 LTS, cron 3.0pl1-124ubuntu2
On a server with heavy cron use (a few thousand entries across cron.d
/ users, several runs per second, a few dozen forks running at any
given time), cron will creep up in memory usage. Last I saw was 6GB
RSS, at which point it will start doing:
Jul 6 07:01:27 host cron[21699]: (CRON) error (can't fork)
Not all runs will fail, but this trend will continue until cron is
restarted.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1702785] Re: High memory and "can't fork" on heavy long-lived cron daemon
I found a bug in the code as described in this issue: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779583 The bug would not prevent the error you're seeing, however, there is a second fork() which, if it fails, will block that part of cron, which would therefore leak. So if it happens "on the wrong fork()", (1) you won't see any logs and (2) you get a cron "process" which gets stuck waiting for a second child that was never created. I included a patch too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1702785 Title: High memory and "can't fork" on heavy long-lived cron daemon Status in cron package in Ubuntu: Confirmed Bug description: Ubuntu 14.04.5 LTS, cron 3.0pl1-124ubuntu2 On a server with heavy cron use (a few thousand entries across cron.d / users, several runs per second, a few dozen forks running at any given time), cron will creep up in memory usage. Last I saw was 6GB RSS, at which point it will start doing: Jul 6 07:01:27 host cron[21699]: (CRON) error (can't fork) Not all runs will fail, but this trend will continue until cron is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779582] Re: Unable to create unpriviledged container
I forgot to mention : $ getfacl /home/alex getfacl : suppression du premier « / » des noms de chemins absolus # file: home/alex # owner: alex # group: alex user::rwx user:165536:--x group::r-x mask::r-x other::--- and so all the way down to /home/alex/.local/share/lxc/ Also lxc-copy is working ! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1779582 Title: Unable to create unpriviledged container Status in lxc package in Ubuntu: New Bug description: I already have a lot of unpriviledged container initialized while on versions prior to 18.04. I normally got all necessary pieces: $ cat /etc/subuid alex:165536:65536 $ cat /etc/subgid alex:165536:65536 $ cat .config/lxc/default.conf lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx lxc.idmap = u 0 165536 65536 lxc.idmap = g 0 165536 65536 I tried to create a new container and it failed. $ lxc-create -n gym -l DEBUG -t download -- -d ubuntu -r xenial -a amd64 Error creating container gym $ cat .local/share/lxc/gym/gym.log lxc-create gym 20180701213443.653 INFO lxc_confile - confile.c:set_config_idmaps:1666 - Read uid map: type u nsid 0 hostid 165536 range 65536 lxc-create gym 20180701213443.653 INFO lxc_confile - confile.c:set_config_idmaps:1666 - Read uid map: type g nsid 0 hostid 165536 range 65536 lxc-create gym 20180701213443.653 DEBUGlxc_conf - conf.c:chown_mapped_root:3086 - trying to chown "/home/alex/.local/share/lxc/gym" to 1001 I got this: $ ls -ld .local/share/lxc/gym drwxr-xr-x 2 165536 alex 4096 juil. 1 22:34 .local/share/lxc/gym So I don't know where it's failing and why ! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lxc 3.0.1-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jul 1 22:36:11 2018 InstallationDate: Installed on 2015-11-10 (964 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) KernLog: PackageArchitecture: all SourcePackage: lxc UpgradeStatus: Upgraded to bionic on 2018-05-04 (58 days ago) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1779582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779583] Re: cron do_command.c attempts a fork() without testing for errors
This may be one solution to the problem reported here:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785
Because when the second fork() fails, the cron process waits for 2
children, one of which doesn't even exist and thus cron is stuck with "a
ton" of memory allocated. This would also happen if *input_data is
false. So not just because the fork() fails... but it could be because
it does not even happen.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1779583
Title:
cron do_command.c attempts a fork() without testing for errors
Status in cron package in Ubuntu:
New
Bug description:
The do_command.c file calls fork() twice.
For the first for(), the possibility for an error is checked properly
and an error emitted (see
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785 for an
example when that happens: message is "can't fork".) This first fork()
makes use of a switch() statement as expected.
The second fork(), however, is used inside an if() statement like
this:
if (*input_data && fork() == 0) { ... }
Here we can see a couple of problems. After the if block, we have this
statement:
children++;
which means that we will have to wait on TWO children. However, (1)
the *input_data could return false and thus the second child may not
be created at all. (2) the fork() could return -1 meaning that no
other child is created.
I suppose that the child_process() probably always or nearly always
has some input_data. Otherwise it would block waiting for a child that
was never started. And of course, it is relatively rare that fork()
fails, unless you are running our of RAM (heap or stack can't be
allocated) or process space (too many processes running concurrently.)
I have a proposed patch to fix the problem. It uses a switch() which
emits an error in case the fork() fails, but let the program go on as
before (instead of an immediate exit as in the first fork()).
The children variable gets incremented only when the fork() happens
and succeeds (default: block in the new switch().)
The do_command.c file did not change between 16.04 (trusty) and 18.04
(bionic beaver), so the patch will work for either version.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779583/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779583] [NEW] cron do_command.c attempts a fork() without testing for errors
Public bug reported:
The do_command.c file calls fork() twice.
For the first for(), the possibility for an error is checked properly
and an error emitted (see
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785 for an
example when that happens: message is "can't fork".) This first fork()
makes use of a switch() statement as expected.
The second fork(), however, is used inside an if() statement like this:
if (*input_data && fork() == 0) { ... }
Here we can see a couple of problems. After the if block, we have this
statement:
children++;
which means that we will have to wait on TWO children. However, (1) the
*input_data could return false and thus the second child may not be
created at all. (2) the fork() could return -1 meaning that no other
child is created.
I suppose that the child_process() probably always or nearly always has
some input_data. Otherwise it would block waiting for a child that was
never started. And of course, it is relatively rare that fork() fails,
unless you are running our of RAM (heap or stack can't be allocated) or
process space (too many processes running concurrently.)
I have a proposed patch to fix the problem. It uses a switch() which
emits an error in case the fork() fails, but let the program go on as
before (instead of an immediate exit as in the first fork()).
The children variable gets incremented only when the fork() happens and
succeeds (default: block in the new switch().)
The do_command.c file did not change between 16.04 (trusty) and 18.04
(bionic beaver), so the patch will work for either version.
** Affects: cron (Ubuntu)
Importance: Undecided
Status: New
** Tags: bionic patch trusty
** Patch added: "Fix to second fork() in child_process()"
https://bugs.launchpad.net/bugs/1779583/+attachment/5158449/+files/do_command.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1779583
Title:
cron do_command.c attempts a fork() without testing for errors
Status in cron package in Ubuntu:
New
Bug description:
The do_command.c file calls fork() twice.
For the first for(), the possibility for an error is checked properly
and an error emitted (see
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785 for an
example when that happens: message is "can't fork".) This first fork()
makes use of a switch() statement as expected.
The second fork(), however, is used inside an if() statement like
this:
if (*input_data && fork() == 0) { ... }
Here we can see a couple of problems. After the if block, we have this
statement:
children++;
which means that we will have to wait on TWO children. However, (1)
the *input_data could return false and thus the second child may not
be created at all. (2) the fork() could return -1 meaning that no
other child is created.
I suppose that the child_process() probably always or nearly always
has some input_data. Otherwise it would block waiting for a child that
was never started. And of course, it is relatively rare that fork()
fails, unless you are running our of RAM (heap or stack can't be
allocated) or process space (too many processes running concurrently.)
I have a proposed patch to fix the problem. It uses a switch() which
emits an error in case the fork() fails, but let the program go on as
before (instead of an immediate exit as in the first fork()).
The children variable gets incremented only when the fork() happens
and succeeds (default: block in the new switch().)
The do_command.c file did not change between 16.04 (trusty) and 18.04
(bionic beaver), so the patch will work for either version.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779583/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779582] [NEW] Unable to create unpriviledged container
Public bug reported: I already have a lot of unpriviledged container initialized while on versions prior to 18.04. I normally got all necessary pieces: $ cat /etc/subuid alex:165536:65536 $ cat /etc/subgid alex:165536:65536 $ cat .config/lxc/default.conf lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx lxc.idmap = u 0 165536 65536 lxc.idmap = g 0 165536 65536 I tried to create a new container and it failed. $ lxc-create -n gym -l DEBUG -t download -- -d ubuntu -r xenial -a amd64 Error creating container gym $ cat .local/share/lxc/gym/gym.log lxc-create gym 20180701213443.653 INFO lxc_confile - confile.c:set_config_idmaps:1666 - Read uid map: type u nsid 0 hostid 165536 range 65536 lxc-create gym 20180701213443.653 INFO lxc_confile - confile.c:set_config_idmaps:1666 - Read uid map: type g nsid 0 hostid 165536 range 65536 lxc-create gym 20180701213443.653 DEBUGlxc_conf - conf.c:chown_mapped_root:3086 - trying to chown "/home/alex/.local/share/lxc/gym" to 1001 I got this: $ ls -ld .local/share/lxc/gym drwxr-xr-x 2 165536 alex 4096 juil. 1 22:34 .local/share/lxc/gym So I don't know where it's failing and why ! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lxc 3.0.1-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jul 1 22:36:11 2018 InstallationDate: Installed on 2015-11-10 (964 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) KernLog: PackageArchitecture: all SourcePackage: lxc UpgradeStatus: Upgraded to bionic on 2018-05-04 (58 days ago) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1779582 Title: Unable to create unpriviledged container Status in lxc package in Ubuntu: New Bug description: I already have a lot of unpriviledged container initialized while on versions prior to 18.04. I normally got all necessary pieces: $ cat /etc/subuid alex:165536:65536 $ cat /etc/subgid alex:165536:65536 $ cat .config/lxc/default.conf lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx lxc.idmap = u 0 165536 65536 lxc.idmap = g 0 165536 65536 I tried to create a new container and it failed. $ lxc-create -n gym -l DEBUG -t download -- -d ubuntu -r xenial -a amd64 Error creating container gym $ cat .local/share/lxc/gym/gym.log lxc-create gym 20180701213443.653 INFO lxc_confile - confile.c:set_config_idmaps:1666 - Read uid map: type u nsid 0 hostid 165536 range 65536 lxc-create gym 20180701213443.653 INFO lxc_confile - confile.c:set_config_idmaps:1666 - Read uid map: type g nsid 0 hostid 165536 range 65536 lxc-create gym 20180701213443.653 DEBUGlxc_conf - conf.c:chown_mapped_root:3086 - trying to chown "/home/alex/.local/share/lxc/gym" to 1001 I got this: $ ls -ld .local/share/lxc/gym drwxr-xr-x 2 165536 alex 4096 juil. 1 22:34 .local/share/lxc/gym So I don't know where it's failing and why ! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lxc 3.0.1-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jul 1 22:36:11 2018 InstallationDate: Installed on 2015-11-10 (964 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) KernLog: PackageArchitecture: all SourcePackage: lxc UpgradeStatus: Upgraded to bionic on 2018-05-04 (58 days ago) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1779582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)
Same problem here with Acer Aspire VN7-792G and ALC255. Internal mic not detected and hdajackretask not working. This model also has a separate mic-jack and a headphone-jack and an internal mic. The internal mic isn't detected and not working. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1523100 Title: Alsa not detecting internal microphone [ALC255] (Realtek) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer Aspire VN7-792G and noticed, that the internal microphone doesn't work. The computer has been released a couple of months ago and it's Intel Skylake -based with a Sunrise Point -based motherboard. INFO: The problem exists in Ubuntu 15.10 too, only microphone jack detected. Currently using Ubuntu 16.04 for proper hardware support. Alsa reports the audio device to be: Card: HDA Intel PCH Chip: Intel Skylake HDMI The speakers are working fine, but both alsamixer and pavucontrol (Pulseaudio Volume Control) raport the unplugged external microphone connector as the only sound input. I have tried many of the alsa model configurations (options snd-hda- intel model=something) without success, alsa finds only the microphone jack, which works fine when I plug an external microphone in it. Here's some info: lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H HD Audio (rev 31) cat /proc/asound/cards: 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x8432 irq 128 And a clip from dmesg | grep snd: [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs: [3.047514] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a One problem is that I can't find any model options (options snd-hda- intel model=something) or other parameters for the card's model (ALC255), I suppose this issue is relatively new. /Dennis --- ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dennis 1180 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-11-11 (23 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: xenial Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-792G dmi.board.vendor: Acer dmi.board.version: V1.02 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02: dmi.product.name: Aspire VN7-792G dmi.product.version: V1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
hello Łukasz Zemczak i am new in Ubuntu. but i have the same problem. could you help me resolve it? I have Ubuntu 18.04 and python3.6. And few apps which cant work without solving this bug. При обработке следующих пакетов произошли ошибки: python3 update-notifier-common gnome-shell update-notifier gnome-menus E: Sub-process /usr/bin/dpkg returned an error code (1) i have added -proposed repository. When i try upgrade i have this mistake: installed python3 package post-installation script subprocess returned error exit status 4 and so on. Could you help me please? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1768379 Title: python3-minimal should predepend on versioned version of python3-minimal Status in python3-defaults package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in python3-defaults source package in Artful: Fix Committed Status in ubuntu-release-upgrader source package in Artful: Invalid Status in python3-defaults source package in Bionic: Fix Committed Status in ubuntu-release-upgrader source package in Bionic: Invalid Status in python3-defaults package in Debian: Fix Released Bug description: [Impact] Release upgrades from Ubuntu 16.04 LTS to either Ubuntu 17.10 or Ubuntu 18.04 LTS can fail if python3-minimial is unpacked before python3.x-minimal so a system won't have a usable python3 symlink. Then upgrades will fail because py3clean, used in prerm scripts of python3 packages, will fail with "not found". [Test Case] 1) on a Ubuntu 16.04 LTS system with python3-apt installed download debs for Ubuntu 17.10 or 18.04 LTS of python3-minimal and python3-apt 2) dpkg --unpack python3-minimal... 3) dpkg --unpack python3-apt... Observe the following Traceback: Preparing to unpack .../python3-apt_1.4.0_beta3build2_amd64.deb ... /var/lib/dpkg/info/python3-apt.prerm: 6: /var/lib/dpkg/info/python3-apt.prerm: py3clean: not found dpkg: warning: subprocess old pre-removal script returned error exit status 127 dpkg: trying script from the new package instead ... /var/lib/dpkg/tmp.ci/prerm: 6: /var/lib/dpkg/tmp.ci/prerm: py3clean: not found dpkg: error processing archive /home/jak/Downloads/python3-apt_1.4.0_beta3build2_amd64.deb (--unpack): subprocess new pre-removal script returned error exit status 127 /var/lib/dpkg/info/python3-apt.postinst: 6: /var/lib/dpkg/info/python3-apt.postinst: py3compile: not found dpkg: error while cleaning up: subprocess installed post-installation script returned error exit status 127 With the deb python3-minimal from -proposed you won't be able to unpack python3-minimal without first installing python3.6-minimal. While that may qualify as verification it'd still be good to test unpacking python3-apt. To do that you'll need to install python3.6-minimal from the target release by editing you /etc/apt/sources.list to the new release, running 'apt-get update', and then 'apt-get install python3.6-minimal'. After that's all done you can try steps 2 and 3 from the test case again and you should not receive a Traceback. [Regression Potential] Its possible this could cause or reveal different upgrade failures so some extensive (desktop, cloud, server) upgrade testing should be done. [A Portion of the Original Description (it was a huge blob of failure)] do-release-upgrade -d on my 16.04 LTS unity laptop lead to an install failure: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1768379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779551] [NEW] package coreutils 8.25-2ubuntu2 failed to install/upgrade: package coreutils is not ready for configuration cannot configure (current status 'half-installed')
Public bug reported: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: coreutils 8.25-2ubuntu2 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 Jul 1 19:09:51 2018 ErrorMessage: package coreutils is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-06-30 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: coreutils Title: package coreutils 8.25-2ubuntu2 failed to install/upgrade: package coreutils is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1779551 Title: package coreutils 8.25-2ubuntu2 failed to install/upgrade: package coreutils is not ready for configuration cannot configure (current status 'half-installed') Status in coreutils package in Ubuntu: New Bug description: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: coreutils 8.25-2ubuntu2 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 Jul 1 19:09:51 2018 ErrorMessage: package coreutils is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-06-30 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: coreutils Title: package coreutils 8.25-2ubuntu2 failed to install/upgrade: package coreutils is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1779551/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1578011] Re: Laptop sometimes doesn't detect external monitor when docked
vik: 1) As per the sticker of the monitor itself (not from the Bug Description, or the result of a terminal command), could you please provide the full monitor manufacturer and model? 2) Regarding how you have the monitor connected, is it plugged into the dock's DVI-I, or DisplayPort port? If you switch the port is this still reproducible? 3) Regarding the connection of the monitor to the dock, is this via straight DVI-I cord, using dongle/adapter, etc.? 4) If you instead undock the computer, and plug the monitor directly into the computer, is this still reproducible? 5) Regarding the Lenovo ThinkPad OneLink Pro Dock, have you applied the latest firmware to it? ** Tags removed: latest-bios-1.29 ** Tags added: bios-outdated-1.38 regression-potential ** Attachment removed: "syslog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1578011/+attachment/4780928/+files/syslog.txt ** Changed in: xorg (Ubuntu) Importance: Medium => Low ** Changed in: xorg (Ubuntu) Status: Confirmed => Incomplete ** Summary changed: - Laptop sometimes doesn't detect external monitor when docked + [Lenovo ThinkPad Yoga Type 20C0] Laptop sometimes doesn't detect external monitor when docked into ThinkPad OneLink Pro Dock -- 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/1578011 Title: [Lenovo ThinkPad Yoga Type 20C0] Laptop sometimes doesn't detect external monitor when docked into ThinkPad OneLink Pro Dock Status in xorg package in Ubuntu: Incomplete Bug description: Lenovo Thinkpad Yoga S1 sometimes doesn't detect external monitor when docked with a Onelink Pro dock. Problem has also occurred on a non-Pro OneLink dock. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: /dev/sda1: clean, 860723/30769152 files, 38024704/123073521 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed May 4 11:47:20 2016 DistUpgraded: 2016-04-23 16:11:36,997 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.2.0-35-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:2217] InstallationDate: Installed on 2015-12-02 (153 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20C0S1CWAU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=bbf6846f-7622-4638-8e7e-286b6badb71d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-23 (10 days ago) dmi.bios.date: 01/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GQET48WW (1.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C0S1CWAU dmi.board.vendor: LENOVO dmi.board.version: 0B98417 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGQET48WW(1.28):bd01/14/2016:svnLENOVO:pn20C0S1CWAU:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S1CWAU:rvr0B98417PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20C0S1CWAU dmi.product.version: ThinkPad S1 Yoga dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed May 4 08:27:55 2016 xserver.configfile: default xserver.errors: Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device. Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device. Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device. xserver.logfile: /var/log/Xorg.0.log
[Touch-packages] [Bug 1779538] [NEW] package initramfs-tools 0.130ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati
Public bug reported: I'm try to install mysqld-server and ubuntu crash. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Sun Jul 1 07:47:51 2018 DpkgHistoryLog: Start-Date: 2018-07-01 07:47:51 Commandline: apt install mysql-server mysql-utilities Requested-By: paulo (1000) DpkgTerminalLog: [1mdpkg:[0m error processing package initramfs-tools (--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 2018-06-06 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3 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) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1779538 Title: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in initramfs-tools package in Ubuntu: New Bug description: I'm try to install mysqld-server and ubuntu crash. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Sun Jul 1 07:47:51 2018 DpkgHistoryLog: Start-Date: 2018-07-01 07:47:51 Commandline: apt install mysql-server mysql-utilities Requested-By: paulo (1000) DpkgTerminalLog: [1mdpkg:[0m error processing package initramfs-tools (--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 2018-06-06 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3 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/initramfs-tools/+bug/1779538/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772844] Re: snapd didn't initialize all the seeded snaps
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1772844 ** Tags added: iso-testing -- 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/1772844 Title: snapd didn't initialize all the seeded snaps Status in OEM Priority Project: Confirmed Status in snapd: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: snapd didn't initialize all the seeded snaps bionic-desktop-amd64.iso (20180522) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: snapd 2.32.9+18.04 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 22 22:59:18 2018 InstallationDate: Installed on 2018-05-23 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180522) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot
Thanks for the update.
Referring to this duplicate bug
(https://bugs.launchpad.net/netplan/+bug/1768827), is it going to be backported
to 18.04?
Or is there a way to install 0.38 on Ubuntu Server 18.04?
--
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/1770082
Title:
systemd-networkd not renaming devices on boot
Status in netplan:
Confirmed
Status in cloud-init package in Ubuntu:
Confirmed
Status in netplan.io package in Ubuntu:
Fix Released
Status in nplan package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Confirmed
Bug description:
=== systemd issue ===
Renaming devices doesn't seem to work.
If I disable all other network configuration and create
/etc/systemd/network/10-network.link with:
[Match]
MACAddress=52:54:00:c1:c9:bb
[Link]
Name=myiface3
I expect this to cause the device with that MAC address to be renamed
to myiface3. However, when I reboot, I instead see:
$ ip l
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
The device is not renamed.
This link file is pretty much identical to Example 2 in
https://www.freedesktop.org/software/systemd/man/systemd.link.html.
The renaming does work if I boot with net.ifnames=0, and oddly, it
also works if I unbind the device and rebind it as netplan apply does.
No setting of NamePolicy seems to help.
=== Original Bug ==
'set-name:' doesn't change the name of a network interface on boot, it
only works when you do netplan apply.
Say I take this 50-cloud-init.yaml file:
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: ens3
Say I change set-name to 'myiface3' and reboot. I expect that the
device will be called myiface3 and brought up fine with dhcp. However,
instead I see:
$ ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: mtu 1500 qdisc noop state DOWN group default
qlen 1000
link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
The name has not been changed, and the device has not been brought up.
If I run netplan apply however, I see the following:
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
3: myiface3: mtu 1500 qdisc fq_codel state
UP group default qlen 1000
link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
valid_lft 3575sec preferred_lft 3575sec
inet6 fe80::5054:ff:fede:bdf6/64 scope link
valid_lft forever preferred_lft forever
So names are successfully changed with netplan apply.
This seems to be some udev-related timing or priority issue that I'm
still trying to hunt down.
This breaks some forms of migration in certain cloud environments.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1770082/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779237] Re: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python3-defaults (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1779237 Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 Status in python3-defaults package in Ubuntu: Confirmed Bug description: Only Ubuntu Update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3 3.6.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jun 28 22:51:28 2018 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2018-04-13 (76 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: python3-defaults Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to bionic on 2018-05-03 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1779237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1664818] Re: Not possible to render pre-up, pre-down, post-up, or post-down snippets
I need to add routing information to one interface to allow ssh that enters via the non-default gateway. Before metalanguage this was easy. Now it's so difficult! The closest advice was networkd-dispatcher but the advised directory doesn't exist. I can't see why "legacy" functionality is jettisoned in such a cavalier fashion -- 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/1664818 Title: Not possible to render pre-up, pre-down, post-up, or post-down snippets Status in netplan: New Status in systemd package in Ubuntu: Triaged Bug description: Many configurations require scripts to run before or after an interface comes up or down. Example: I had a situation where I needed to render a post-up script to monitor an interface with ifupdown (and with the interface set to manual mode, because if the link was down I didn't want to require DHCP to run before the system continued booting). This is similar to what NetworkManager does in order to launch (or kill) a DHCP client. Other use cases involve setting up custom routes (such as when complex logic involving metrics or source routing is required) or anything else the designers of the netplan rendering engine didn't think of, such as invoking workarounds or special settings required for a particular NIC or environment, iptables rules that should be added or removed, etc. A follow-on issue is, it should be possible to ask that custom scripts run if the *link* is detected to come up or down. But I'll be happy if netplan first can simply replicate the custom-script-invoking behavior of ifupdown. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1664818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770839] Re: Syncevolution does not run in Ubuntu 18.04
Please ask in ubuntu-devel mailing list to update syncevolution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to syncevolution in Ubuntu. https://bugs.launchpad.net/bugs/1770839 Title: Syncevolution does not run in Ubuntu 18.04 Status in syncevolution package in Ubuntu: Confirmed Bug description: There is a problem with the package syncevolution (1.5.3-1ubuntu2) in Ubuntu 18.04 : Step to reproduce: >$ sudo apt install syncevolution Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Les paquets supplémentaires suivants seront installés : libopenobex2 libpcrecpp0v5 libsmltk0 libsyncevolution0 libsynthesis0v5 syncevolution-common syncevolution-libs syncevolution-libs-gnome Les NOUVEAUX paquets suivants seront installés : libopenobex2 libpcrecpp0v5 libsmltk0 libsyncevolution0 libsynthesis0v5 syncevolution syncevolution-common syncevolution-libs syncevolution-libs-gnome 0 mis à jour, 9 nouvellement installés, 0 à enlever et 0 non mis à jour. Il est nécessaire de prendre 2'230 ko dans les archives. Après cette opération, 10.2 Mo d'espace disque supplémentaires seront utilisés. Souhaitez-vous continuer ? [O/n] O [...] Paramétrage de syncevolution (1.5.3-1ubuntu2) ... [...] > $ syncevolution --version syncevolution: error while loading shared libraries: libgdbussyncevo.so.0: cannot open shared object file: No such file or directory > $ syncevolution --print-peers syncevolution: error while loading shared libraries: libgdbussyncevo.so.0: cannot open shared object file: No such file or directory > $ syncevolution --print-config syncevolution: error while loading shared libraries: libgdbussyncevo.so.0: cannot open shared object file: No such file or directory Please note that this bug semms corrected in a new release of syncevolution : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887043 Would it be possible to have the corrected verion in Ubuntu 18.04 ? Thanks in advance for your help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/syncevolution/+bug/1770839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779526] [NEW] Please merge 2.24.32-2 from Debian Sid
Public bug reported: 2.24.32-2 has been uploaded to Debian Sid fixing a few bugs. Let's merge it. ** Affects: gtk+2.0 (Ubuntu) Importance: Wishlist Assignee: Simon Quigley (tsimonq2) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1779526 Title: Please merge 2.24.32-2 from Debian Sid Status in gtk+2.0 package in Ubuntu: In Progress Bug description: 2.24.32-2 has been uploaded to Debian Sid fixing a few bugs. Let's merge it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1779526/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
