[Bug 1752053] Re: nvidia-390 fails to boot graphical display
I have the same problem of power drains even when prime-select is on intel. I know for sure that the nvidia GPU is running because the external HDMI port is working and shouldn't since it's wired to the GPU. sudo sh -c 'echo auto > /sys/bus/pci/devices/\:01\:00.0/power/control' sudo sh -c "echo "1" > remove" gives no result on my system (Nvidia Quadro M2000M/Thinkpad P51). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
Same on Thinkpad P51 (Nvidia Quadro M2200), Ubuntu 18.04, Nvidia 390 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765556] [NEW] nvidia-prime needs a reboot to switch between dGPU/hGPU
Public bug reported: I previously used Ubuntu 16.04 and Nvidia 375 driver with a Nvidia Geforce 635M and Sandy Bridge i7. To switch between the 2 Optimus cards (Intel hybrid and Nvidia discrete), one had to go into nvidia-settings, switch, logoff, login back, and the change was applied. I now have a Nvidia Quadro M2000 and a Skylake Xeon which has some Sync/Mux feature (whatever does that mean) with the Nvidia 390 driver. First of all, installing nivida-prime doesn't install bbswitch-dkms. Then, once the GPU switch is made, it triggers update-initramfs, recompile the kernel modules, and one needs to reboot the system to get the GPU change. Even when we install bbswitch-dkms. So am I getting a wrong impression or is there something twisted here ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:20:01 2018 Dependencies: InstallationDate: Installed on 2018-04-08 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-prime (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/1765556 Title: nvidia-prime needs a reboot to switch between dGPU/hGPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762603] Re: bluetooth keeps turning off
Ok I troubleshot this problem. Apparently, it came from the package `connman`, an Intel utility to manage wlan and bluetooth that I installed wrongly since it's intended for embedded systems. Removing it solved all my problems. ** Package changed: bluez (Ubuntu) => connman (Ubuntu) ** Changed in: connman (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762603 Title: bluetooth keeps turning off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/connman/+bug/1762603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762602] Re: resolv.conf empty after reboot
It's related to https://bugs.launchpad.net/ubuntu/+source/connman/+bug/1762603 and package connman. sorry for the noise. ** Package changed: network-manager-applet (Ubuntu) => connman (Ubuntu) ** Changed in: connman (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762602 Title: resolv.conf empty after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/connman/+bug/1762602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"
Same bug on Ubuntu 18.04 / Thinkpad P51. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738838 Title: Bluetooth icon shows "Off" and the only option given below it is "Turn Off" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1738838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762603] Re: bluetooth keeps turning off
Yes it looks like the same bug (at least for the GUI part), and it's a Thinkpad as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762603 Title: bluetooth keeps turning off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1762603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762603] Re: bluetooth keeps turning off
I mean reboots. So, on boot, the airplane mode is turned on by default (for an unknwon reason). The rfkill output is attached above. I have to trigger several `sudo rfkill unblock all` to actually have them unlocked (in command line). But then, the GUI still shows the bluetooth switch as OFF. When I try to enable the BT in the GUI, the gnome-control-center window freezes but no device detection happens. Closing and re-opening the gnome-control- center shows that BT is still OFF. Using the BT hotkey from the laptop chenges nothing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762603 Title: bluetooth keeps turning off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1762603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762603] Re: bluetooth keeps turning off
Also I have tried with blueman instead, with and without acpi-calls- dkms, tp-smapi-dkms, tlp installed, the issue remains. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762603 Title: bluetooth keeps turning off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1762603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762603] [NEW] bluetooth keeps turning off
Public bug reported: the bluetooth worked well right after install. After a few reboots, it's impossible to keep it on and to connect devices. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 23:24:56 2018 InstallationDate: Installed on 2018-04-08 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) InterestingModules: bnep btusb bluetooth MachineType: LENOVO 20HHCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=UUID=f6fc1852-25c6-47a6-9776-4ed8b8d6b70e ro quiet splash elevator=noop vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET46W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40112 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET46W(1.20):bd02/26/2018:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0Q40112WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HHCTO1WW dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO hciconfig: ** Affects: bluez (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/1762603 Title: bluetooth keeps turning off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1762603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762602] [NEW] resolv.conf empty after reboot
Public bug reported: /etc/resolv.conf contains only : # Generated by Connection Manager nameserver ::1 nameserver 127.0.0.1 If I add "nameserver 8.8.8.8", it's lost on the next reboot. Manually entering the DNS IP in the WIFI parameters (network-manager- gnome, tab IPv4) does nothing. I have to edit the resolv.conf on each reboot to get the WIFI to work. Ethernet connections are not affected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 23:06:26 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-08 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp4s0 wifi connected /org/freedesktop/NetworkManager/Devices/3 THEMISTOCLE 51e5474c-e370-4a95-89d1-c766b4e50484 /org/freedesktop/NetworkManager/ActiveConnection/8 enp0s31f6 ethernet connected /org/freedesktop/NetworkManager/Devices/2 enp0s31f6de319564-8508-4a64-ae18-3d24d96f465b /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager-applet (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/1762602 Title: resolv.conf empty after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1762602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762597] [NEW] External HDMI screen get internal screen color profile
Public bug reported: System : Intel Skylake Xeon + Nvidia Quadro M2200M with Nvidia Optimus laptop Kernel : 4.15.16 Driver : Nvidia 390.48 Optimus sync enabled. Configuration : The internal screen is wired to the Intel GPU, the HDMI port is wired to the Nvidia GPU. The HDMi port has an external monitor plugged. Reproduce the bug : Both screens have a different color profile (.icm and .icc) loaded in gnome-color-manager. However, after booting or when the internal display profile is edited, the external monitor gets the same color profile as the internal one. Workaround : Disable then re-enable the color profile on the external monitor. This applies back the correct profile. xrandr output: Screen 0: minimum 8 x 8, current 3840 x 1200, maximum 16384 x 16384 DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 connected primary 1920x1200+1920+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 59.95*+ 1920x1080 60.0059.9450.0023.9860.0560.0050.04 1680x1050 59.95 1600x900 60.00 1280x1024 75.0260.02 1280x800 59.81 1280x720 60.0059.9450.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-4 disconnected (normal left inverted right x axis y axis) DP-5 disconnected (normal left inverted right x axis y axis) eDP-1-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 345mm x 194mm 3840x2160 60.02 + 60.0060.0159.9859.97 3200x1800 59.9659.94 2880x1620 59.9659.97 2560x1600 59.9959.97 2560x1440 59.9959.9959.9659.95 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 2048x1152 59.9959.9859.9059.91 1920x1200 59.8859.95 1920x1080 60.01* 59.9759.9659.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 1920x1200 (0x5c) 154.000MHz +HSync -VSync h: width 1920 start 1968 end 2000 total 2080 skew0 clock 74.04KHz v: height 1200 start 1203 end 1209 total 1235 clock 59.95Hz 1680x1050 (0x62) 146.250MHz -HSync +VSync h: width 1680 start 1784 end 1960 total 2240 skew0 clock 65.29KHz v: height 1050 start 1053 end 1059 total 1089 clock 59.95Hz 1280x1024 (0x6a) 108.000MHz +HSync +VSync h: width 1280 start 1328 end 1440 total 1688 skew0 clock 63.98KHz v: height 1024 start 1025 end 1028 total 1066 clock 60.02Hz 1280x800 (0x77) 83.500MHz -HSync +VSync h: width 1280 start 1352 end 1480 total 1680 skew0 clock 49.70KHz v: height 800 start 803 end 809 total 831 clock 59.81Hz 1024x768 (0x7f) 65.000MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1344 skew0 clock 48.36KHz v: height 768 start 771 end 777 total 806 clock 60.00Hz 800x600 (0x8e) 40.000MHz +HSync +VSync h: width 800 start 840 end 968 total 1056 skew0 clock 37.88KHz v: height 600 start 601 end 605 total 628 clock 60.32Hz 640x480 (0x9d) 25.175MHz -HSync -VSync h: width 640 start 656 end 752 total 800 skew0 clock 31.47KHz
[Bug 1322571] Re: Deja dup (duplicity) crashes during backup
Same error for me, Trusty too, but while restoring : Traceback (most recent call last): File /usr/bin/duplicity, line 1494, in module with_tempdir(main) File /usr/bin/duplicity, line 1488, in with_tempdir fn() File /usr/bin/duplicity, line 1337, in main do_backup(action) File /usr/bin/duplicity, line 1422, in do_backup restore(col_stats) File /usr/bin/duplicity, line 700, in restore % (globals.restore_dir,), UnicodeDecodeError: 'ascii' codec can't decode byte 0xe9 in position 34: ordinal not in range(128) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322571 Title: Deja dup (duplicity) crashes during backup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1322571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
