[Touch-packages] [Bug 1892348] [NEW] cups samba authetication dialog closes too early
Public bug reported: Using network printers with samba authentication on Ubuntu 20.04 the authentication dialog is shown only a very short time and closes unexpectedly. But authentication works with noninteractive authentication using specifying username and password as part of the samba address. The interactive authentication dialog worked in Ubuntu 18.04 correctly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 12:57:13 2020 InstallationDate: Installed on 2020-07-07 (43 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QF00AYGE Papersize: a4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET50W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QF00AYGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET50W(1.33):bd05/13/2020:svnLENOVO:pn20QF00AYGE:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QF00AYGE:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20QF00AYGE dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1892348 Title: cups samba authetication dialog closes too early Status in cups package in Ubuntu: New Bug description: Using network printers with samba authentication on Ubuntu 20.04 the authentication dialog is shown only a very short time and closes unexpectedly. But authentication works with noninteractive authentication using specifying username and password as part of the samba address. The interactive authentication dialog worked in Ubuntu 18.04 correctly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 12:57:13 2020 InstallationDate: Installed on 2020-07-07 (43 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QF00AYGE Papersize: a4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET50W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QF00AYGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET50W(1.33):bd05/13/2020:svnLENOVO:pn20QF00AYGE:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QF00AYGE:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20QF00AYGE dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1892348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787975] [NEW] unable to restart lightdm after 2 weeks of no interaction
Public bug reported: System was running without problems for a long time. After two weeks of no interaction with mouse or keyboard, System did not respond on keyboard or mouse interaction anymore. Gui works (tried with DISPLAY=:1 xmessage "test" from ssh), mouse and keyboard are also working (Fn-LED or mouse cursor) but clicking and typing does not do anything. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: lightdm 1.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-45.50-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.9 Architecture: amd64 Date: Mon Aug 20 17:13:40 2018 InstallationDate: Installed on 2017-09-19 (335 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to artful on 2018-05-15 (96 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1787975 Title: unable to restart lightdm after 2 weeks of no interaction Status in lightdm package in Ubuntu: New Bug description: System was running without problems for a long time. After two weeks of no interaction with mouse or keyboard, System did not respond on keyboard or mouse interaction anymore. Gui works (tried with DISPLAY=:1 xmessage "test" from ssh), mouse and keyboard are also working (Fn-LED or mouse cursor) but clicking and typing does not do anything. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: lightdm 1.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-45.50-generic 4.13.16 Uname: Linux 4.13.0-45-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.9 Architecture: amd64 Date: Mon Aug 20 17:13:40 2018 InstallationDate: Installed on 2017-09-19 (335 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to artful on 2018-05-15 (96 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1787975/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768633] Re: desktop or window fallen over after standby
tried now nvidia 396.24, got simmilar problems I think it does not depend on nvidia drivers. The internal display ist connected to intel graphics. Switching nvidia gpu off does not change anything. ** Attachment added: "screenshot graphic problems" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768633/+attachment/5145128/+files/Bildschirmfoto%20vom%202018-05-27%2012-06-37.png -- 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/1768633 Title: desktop or window fallen over after standby Status in xorg package in Ubuntu: Incomplete Bug description: after wake up from standby the screen was flickering and a window was fallen over ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 NonfreeKernelModules: openafs nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 387.34 Tue Nov 21 03:09:00 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.16 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: Wed May 2 21:04:50 2018 DistUpgraded: 2017-08-25 15:00:28,865 DEBUG /openCache(), new cache size 89089 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f5] NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f5] MachineType: LENOVO 2441CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-121-generic root=UUID=d69762cf-74da-49ec-97d9-c040c9e21557 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2017-08-25 (250 days ago) dmi.bios.date: 09/26/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETA9WW (2.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 2441CTO dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ETA9WW(2.69):bd09/26/2017:svnLENOVO:pn2441CTO:pvrThinkPadW530:rvnLENOVO:rn2441CTO:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2441CTO dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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: Wed May 2 20:59:06 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) [drm] Failed to open DRM device for (null): -2 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4589 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768633/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768633] [NEW] desktop or window fallen over after standby
Public bug reported: after wake up from standby the screen was flickering and a window was fallen over ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 NonfreeKernelModules: openafs nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 387.34 Tue Nov 21 03:09:00 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.16 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: Wed May 2 21:04:50 2018 DistUpgraded: 2017-08-25 15:00:28,865 DEBUG /openCache(), new cache size 89089 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f5] NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f5] MachineType: LENOVO 2441CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-121-generic root=UUID=d69762cf-74da-49ec-97d9-c040c9e21557 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2017-08-25 (250 days ago) dmi.bios.date: 09/26/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETA9WW (2.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 2441CTO dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ETA9WW(2.69):bd09/26/2017:svnLENOVO:pn2441CTO:pvrThinkPadW530:rvnLENOVO:rn2441CTO:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2441CTO dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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: Wed May 2 20:59:06 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) [drm] Failed to open DRM device for (null): -2 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4589 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu xenial ** Attachment added: "window fallen over" https://bugs.launchpad.net/bugs/1768633/+attachment/5132367/+files/Bildschirmfoto%20vom%202018-05-02%2012-36-57.png -- 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/1768633 Title: desktop or window fallen over after standby Status in xorg package in Ubuntu: New Bug description: after wake up from standby the screen was flickering and a window was fallen over ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 NonfreeKernelModules: openafs nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 387.34 Tue Nov 21 03:09:00 PST 2017 GCC version: gcc ver
[Touch-packages] [Bug 1760923] [NEW] watch command stack smash running nvidia-smi 384.111
Public bug reported: On Ubuntu 16.04 LTS, AMD Ryzen 7 1700, 16 GB RAM, Nvidia GTX 1050 Ti with driver 384.111 running watch nvidia-smi crashes after 4 days nonstop operation with message "stack smashed" This does NOT happen on Intel Xeon E5-2660v4, GTX 1080 Ti with Ubuntu 17.04, Nvidia driver 384.111. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: procps 2:3.3.10-4ubuntu2.3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 3 18:07:17 2018 InstallationDate: Installed on 2018-03-23 (11 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: procps UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: procps (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1760923 Title: watch command stack smash running nvidia-smi 384.111 Status in procps package in Ubuntu: New Bug description: On Ubuntu 16.04 LTS, AMD Ryzen 7 1700, 16 GB RAM, Nvidia GTX 1050 Ti with driver 384.111 running watch nvidia-smi crashes after 4 days nonstop operation with message "stack smashed" This does NOT happen on Intel Xeon E5-2660v4, GTX 1080 Ti with Ubuntu 17.04, Nvidia driver 384.111. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: procps 2:3.3.10-4ubuntu2.3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 3 18:07:17 2018 InstallationDate: Installed on 2018-03-23 (11 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: procps UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1760923/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725675] [NEW] SIM-Card PIN-Code unlock windows spawns in front of login screen
Public bug reported: Sometimes the PIN-Code request window opens over the session unlock screen. The window cannot be moved. Entering PIN-Code is possible but fails. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 21 14:22:26 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto enp0s25 iface enp0s25 inet manual NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2017-08-25 (56 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-04-14T17:29:21.619202 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1725675 Title: SIM-Card PIN-Code unlock windows spawns in front of login screen Status in network-manager package in Ubuntu: New Bug description: Sometimes the PIN-Code request window opens over the session unlock screen. The window cannot be moved. Entering PIN-Code is possible but fails. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 21 14:22:26 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto enp0s25 iface enp0s25 inet manual NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2017-08-25 (56 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-04-14T17:29:21.619202 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1725675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704602] [NEW] nm-applet gui may segfault if bug #1704600 is triggered
Public bug reported: If network-manager stucks caused by bug #1704600, further attempts to interact with the nm-applet gui lead to timeouts and often a segmentation fault of nm-applet, causing the nm-applet to terminate non- gracefully. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 16 02:18:48 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto enp0s25 iface enp0s25 inet manual IpRoute: default via 10.149.15.253 dev wlp3s0 proto static metric 600 10.149.0.0/20 dev wlp3s0 proto kernel scope link src 10.149.5.84 metric 600 169.254.0.0/16 dev br-d5edc0a60a9c scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-d5edc0a60a9c proto kernel scope link src 172.18.0.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-04-14T17:29:21.619202 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "one variant of the error" https://bugs.launchpad.net/bugs/1704602/+attachment/4915345/+files/nmappletSegFault.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1704602 Title: nm-applet gui may segfault if bug #1704600 is triggered Status in network-manager package in Ubuntu: New Bug description: If network-manager stucks caused by bug #1704600, further attempts to interact with the nm-applet gui lead to timeouts and often a segmentation fault of nm-applet, causing the nm-applet to terminate non-gracefully. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 16 02:18:48 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto enp0s25 iface enp0s25 inet manual IpRoute: default via 10.149.15.253 dev wlp3s0 proto static metric 600 10.149.0.0/20 dev wlp3s0 proto kernel scope link src 10.149.5.84 metric 600 169.254.0.0/16 dev br-d5edc0a60a9c scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-d5edc0a60a9c proto kernel scope link src 172.18.0.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-04-14T17:29:21.619202 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1704602/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704600] [NEW] network-manager stucks if 127.0.1.1:53 is in use
Public bug reported: If a process binds 127.0.1.1:53 and the network-manager ist started, it tries to use this port (dnsmasq). It waits until the port is available. That means no interaction with the network-manager is possible. So unity-control-center stucks if "Network" is clicked or the nm-applet does not respond if the user tries to change connection settings. I think there should be a message that explains the problem: "network- manager tries to set up dnsmasq on 127.0.1.1:53, but this port is already in use. Retrying ..." and the associated GUI components should stay responsive, but only the blocked options should be shown as blocked by the problem. You can verify the bug with the provieded script. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 16 02:01:03 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto enp0s25 iface enp0s25 inet manual IpRoute: default via 10.149.15.253 dev wlp3s0 proto static metric 600 10.149.0.0/20 dev wlp3s0 proto kernel scope link src 10.149.5.84 metric 600 169.254.0.0/16 dev br-d5edc0a60a9c scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-d5edc0a60a9c proto kernel scope link src 172.18.0.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-04-14T17:29:21.619202 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "script triggers the problem" https://bugs.launchpad.net/bugs/1704600/+attachment/4915321/+files/crash_networkmanager.bash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1704600 Title: network-manager stucks if 127.0.1.1:53 is in use Status in network-manager package in Ubuntu: New Bug description: If a process binds 127.0.1.1:53 and the network-manager ist started, it tries to use this port (dnsmasq). It waits until the port is available. That means no interaction with the network-manager is possible. So unity-control-center stucks if "Network" is clicked or the nm-applet does not respond if the user tries to change connection settings. I think there should be a message that explains the problem: "network- manager tries to set up dnsmasq on 127.0.1.1:53, but this port is already in use. Retrying ..." and the associated GUI components should stay responsive, but only the blocked options should be shown as blocked by the problem. You can verify the bug with the provieded script. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 16 02:01:03 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto enp0s25 iface enp0s25 inet manual IpRoute: default via 10.149.15.253 dev wlp3s0 proto static metric 600 10.149.0.0/20 dev wlp3s0 proto kernel scope link src 10.149.5.84 metric 600 169.254.0.0/16 dev br-d5edc0a60a9c scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-d5edc0a60a9c proto kernel scope link src 172.18.0.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-04-14T17:29:21.619202 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1704600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packa
[Touch-packages] [Bug 1704559] Re: often no wifi connections shown
This may be a security problem, because also the currently running connection is also not shown/named. It looks like wifi is inactive, but the computer may be connected to an insecure, unencrypted or fishy network without user knowledge. ** Summary changed: - often now wifi connections shown + often no wifi connections shown ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1704559 Title: often no wifi connections shown Status in network-manager package in Ubuntu: New Bug description: On Ubuntu 16.04.2: The network-manager often does not show wifi networks. The connection may be runningen without problems at the same time. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jul 15 15:53:53 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto enp0s25 iface enp0s25 inet manual IpRoute: default via 172.22.99.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-d5edc0a60a9c proto kernel scope link src 172.18.0.1 172.22.99.0/24 dev wlp3s0 proto kernel scope link src 172.22.99.149 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-04-14T17:29:21.619202 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1704559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 32016] Re: nm-applet shows no connections (cannot control Network Manager)
Happens often also in Ubuntu 16.04.2, maybe in combination with standy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/32016 Title: nm-applet shows no connections (cannot control Network Manager) Status in network-manager package in Ubuntu: Fix Released Bug description: From the 2/19/06 upgrade of the network-manager and nm-applet packages, nm-applet no longer shows any network connections. It only shows the "wired network disconnected" icon and left-clicking it shows the grayed out "Wired Network" option and nothing else. The wireless network still seems to be initialized by Network Manager, I just have no control over it via nm-applet. I have tried removing nm-applet and network-manager and reinstalling them, but the same thing happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/32016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704559] [NEW] often now wifi connections shown
Public bug reported: On Ubuntu 16.04.2: The network-manager often does not show wifi networks. The connection may be runningen without problems at the same time. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jul 15 15:53:53 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto enp0s25 iface enp0s25 inet manual IpRoute: default via 172.22.99.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-d5edc0a60a9c proto kernel scope link src 172.18.0.1 172.22.99.0/24 dev wlp3s0 proto kernel scope link src 172.22.99.149 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-04-14T17:29:21.619202 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "empty wifi list, but wifi working" https://bugs.launchpad.net/bugs/1704559/+attachment/4915126/+files/NetworkmanagerEmptyWifi.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1704559 Title: often now wifi connections shown Status in network-manager package in Ubuntu: New Bug description: On Ubuntu 16.04.2: The network-manager often does not show wifi networks. The connection may be runningen without problems at the same time. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jul 15 15:53:53 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback auto enp0s25 iface enp0s25 inet manual IpRoute: default via 172.22.99.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-d5edc0a60a9c proto kernel scope link src 172.18.0.1 172.22.99.0/24 dev wlp3s0 proto kernel scope link src 172.22.99.149 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-04-14T17:29:21.619202 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1704559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701242] [NEW] misleading error message if cifs-utils not installed
Public bug reported: On Ubuntu 16.04.2: If cifs-utils is not installed the following command gives error messages making no sense: sudo mount -t cifs -o credentials=~/.credentials //192.168.1.2/austausch /media/austausch The message is: mount: wrong fs type, bad option, bad superblock on //192.168.1.2/austausch, missing codepage or helper program, or other error (for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount. helper program) In some cases useful info is found in syslog - try dmesg | tail or so. The dmesg output is: [2408337.346794] CIFS VFS: No username specified But the username is specified in .credentials. It should better say: "cifs-utils needed, but not installed - Install it now? [Y/n]" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: mount 2.27.1-6ubuntu3.2 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 29 13:25:41 2017 SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1701242 Title: misleading error message if cifs-utils not installed Status in util-linux package in Ubuntu: New Bug description: On Ubuntu 16.04.2: If cifs-utils is not installed the following command gives error messages making no sense: sudo mount -t cifs -o credentials=~/.credentials //192.168.1.2/austausch /media/austausch The message is: mount: wrong fs type, bad option, bad superblock on //192.168.1.2/austausch, missing codepage or helper program, or other error (for several filesystems (e.g. nfs, cifs) you might need a /sbin/mount. helper program) In some cases useful info is found in syslog - try dmesg | tail or so. The dmesg output is: [2408337.346794] CIFS VFS: No username specified But the username is specified in .credentials. It should better say: "cifs-utils needed, but not installed - Install it now? [Y/n]" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: mount 2.27.1-6ubuntu3.2 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 29 13:25:41 2017 SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1701242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700413] Re: ping deviation report negative number if rtt reaches 8 min.
** Summary changed: - ping deviation report negative number if rtt over 10 min. + ping deviation report negative number if rtt reaches 8 min. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1700413 Title: ping deviation report negative number if rtt reaches 8 min. Status in iputils package in Ubuntu: New Bug description: On Ubuntu 16.04.2: If ping time reaches 8 min. with over 600 echo requests on a lossy internet access, an overflow can happen resulting in a negative mdev value. The second bug triggered by this bug shows a minus sign after the decimal separator. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: iputils-ping 3:20121221-5ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 25 22:08:25 2017 SourcePackage: iputils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1700413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700413] [NEW] ping deviation report negative number if rtt over 10 min.
Public bug reported: On Ubuntu 16.04.2: If ping time reaches 8 min. with over 600 echo requests on a lossy internet access, an overflow can happen resulting in a negative mdev value. The second bug triggered by this bug shows a minus sign after the decimal separator. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: iputils-ping 3:20121221-5ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 25 22:08:25 2017 SourcePackage: iputils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: iputils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "screenshot of ping in terminal" https://bugs.launchpad.net/bugs/1700413/+attachment/4903205/+files/pingMdev.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1700413 Title: ping deviation report negative number if rtt over 10 min. Status in iputils package in Ubuntu: New Bug description: On Ubuntu 16.04.2: If ping time reaches 8 min. with over 600 echo requests on a lossy internet access, an overflow can happen resulting in a negative mdev value. The second bug triggered by this bug shows a minus sign after the decimal separator. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: iputils-ping 3:20121221-5ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 25 22:08:25 2017 SourcePackage: iputils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1700413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685796] Re: systemctl -H user@host hangs after execution
This bug is solved in Ubuntu 17.04 with systemd 232. Please solve it in Ubuntu 16.04 LTS. -- 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/1685796 Title: systemctl -H user@host hangs after execution Status in systemd package in Ubuntu: New Bug description: Ubuntu 16.04.2 (x86_64) systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g 1 Mar 2016 If I execute: systemctl -H root@127.0.0.1 restart networking The command is executed correctly but it hangs forever. If I run it localy: systemctl restart networking It is also executed correctly, but it does not hang at the end if the command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1685796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685796] [NEW] systemctl -H user@host hangs after execution
Public bug reported: Ubuntu 16.04.2 (x86_64) systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g 1 Mar 2016 If I execute: systemctl -H root@127.0.0.1 restart networking The command is executed correctly but it hangs forever. If I run it localy: systemctl restart networking It is also executed correctly, but it does not hang at the end if the command. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: remote ssh systemctl -- 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/1685796 Title: systemctl -H user@host hangs after execution Status in systemd package in Ubuntu: New Bug description: Ubuntu 16.04.2 (x86_64) systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g 1 Mar 2016 If I execute: systemctl -H root@127.0.0.1 restart networking The command is executed correctly but it hangs forever. If I run it localy: systemctl restart networking It is also executed correctly, but it does not hang at the end if the command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1685796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1622709] [NEW] wrong app name "docker"
Public bug reported: This is a minor name bug. If I want to start the command "docker" in bash and docker.io is not installed, It recommends to install docker: "sudo apt-get install docker" - This is not the right package name. The docker command is associated with the "docker.io" package. So It has to recommend "sudo apt-get install docker.io". ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.14 ProcVersionSignature: Ubuntu 3.16.0-76.98~14.04.1-generic 3.16.7-ckt27 Uname: Linux 3.16.0-76-generic x86_64 NonfreeKernelModules: openafs nvidia ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 12 20:22:18 2016 InstallationDate: Installed on 2016-01-21 (235 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1622709 Title: wrong app name "docker" Status in apt package in Ubuntu: New Bug description: This is a minor name bug. If I want to start the command "docker" in bash and docker.io is not installed, It recommends to install docker: "sudo apt-get install docker" - This is not the right package name. The docker command is associated with the "docker.io" package. So It has to recommend "sudo apt-get install docker.io". ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.14 ProcVersionSignature: Ubuntu 3.16.0-76.98~14.04.1-generic 3.16.7-ckt27 Uname: Linux 3.16.0-76-generic x86_64 NonfreeKernelModules: openafs nvidia ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 12 20:22:18 2016 InstallationDate: Installed on 2016-01-21 (235 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1622709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
