[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760923 Title: watch command stack smash running nvidia-smi 384.111 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1760923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824693] [NEW] add rack controller shows only instructions
Public bug reported: If I click "add rack controller" I only see instructions to do this. MAAS should do this for me. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: maas 2.4.2-7034-g2f5deb8b8-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 13:42:58 2019 InstallationDate: Installed on 2019-04-06 (8 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824693 Title: add rack controller shows only instructions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1824693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824696] [NEW] no implicitly consistant ip configuration
Public bug reported: To add a local rack controller, I have to setup an ip address with "ip addr add" for the ethernet port. I also have to run: sudo maas-rack register --url http://192.168.2.3:5240/MAAS --secret Normally this should be done without multiple commands. MMAS should provide an user interface to setup both consistently. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: maas 2.4.2-7034-g2f5deb8b8-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 13:49:24 2019 InstallationDate: Installed on 2019-04-06 (8 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824696 Title: no implicitly consistant ip configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1824696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824698] [NEW] AMT graceful power operations not supported
Public bug reported: MAAS switches off computers graceless. Since Intel Haswell AMT supports graceful power operations. MAAS should send a graceful powerdown command to switch off the computer. It should use acpi shutdown. It should also fallback if graceful powerdown times out or an older AMT version is detected. It should also warn after detecting AMT version: "This AMT version is too old for graceful powerdown. Minimum version AMT 9.0 is required for graceful shutdown." ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: maas 2.4.2-7034-g2f5deb8b8-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 13:58:50 2019 InstallationDate: Installed on 2019-04-06 (8 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824698 Title: AMT graceful power operations not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1824698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824697] [NEW] AMT power operations no username configureable
Public bug reported: Using AMT to check power and power up computer, MAAS does not allow to specify the username. It defaults to "admin". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: maas 2.4.2-7034-g2f5deb8b8-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 13:56:39 2019 InstallationDate: Installed on 2019-04-06 (8 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824697 Title: AMT power operations no username configureable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1824697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824702] [NEW] AMT address conflict is not a conflict
Public bug reported: AMT uses same MAC- and IP-address like the host network port of the computer. MAAS seems to have a problem with that. MAAS detects all computers that may be controlled by MAAS. Now we can configure the machine e. g. by setting the power configuration to have AMT on a specific IP address. Now MAAS registers that IP-address as "BMC"-IP. That address is now reserved for the BMC and cannot be reused. Now I have to assign a new host-IP-address for the machine. And that is the point everything breaks. MAAS dhcp sets this new IP-address which also changes the AMT-IP-address to this, because AMT and host are sharing the same MAC-address. Now MAAS is not able to switch the computer on using the configured AMT power IP-address. There is only one way to trick MAAS to work: After the host IP is assigned, I can reconfigure the IP in "power configurations" to the host-IP, because on the opposite way the conflict is not detected. We need a checkbox "shared with host" here. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: maas 2.4.2-7034-g2f5deb8b8-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 14:05:41 2019 InstallationDate: Installed on 2019-04-06 (8 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824702 Title: AMT address conflict is not a conflict To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1824702/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768633 Title: desktop or window fallen over after standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840508] [NEW] eog crashes if new files are written to the directory it is reading from
Public bug reported: If eog is called to read a png file from a directory like: eog mydirectory/picture.png while new png images are frequently added to this directory, eog crashes with random errors, e. g.: (eog:4447): GLib-WARNING **: 00:00:37.123: Accessing a sequence while it is being sorted or searched is not allowed (eog:4447): GLib-WARNING **: 00:00:37.124: Accessing a sequence while it is being sorted or searched is not allowed malloc(): memory corruption Aborted (core dumped) This happens only if the files are written to the same directory. If the files are written to different directories, it opens it without error. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: eog 3.28.1-1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 16 23:52:32 2019 InstallationDate: Installed on 2019-06-08 (69 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840508 Title: eog crashes if new files are written to the directory it is reading from To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1840508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758243] Re: bumblebee needs configuration changes to work with nvidia-driver-390 and libglvnd0
These proposed way seems to work for me. What are the next steps to bring it upstream? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758243 Title: bumblebee needs configuration changes to work with nvidia-driver-390 and libglvnd0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/1758243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758243] Re: bumblebee needs configuration changes to work with nvidia-driver-390 and libglvnd0
Very important: I had to select "intel" in nvidia-settings to prevent loading the blacklisted nvidia driver by nvidia-persistenced. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758243 Title: bumblebee needs configuration changes to work with nvidia-driver-390 and libglvnd0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/1758243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787975 Title: unable to restart lightdm after 2 weeks of no interaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1787975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768633 Title: desktop or window fallen over after standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
