[Bug 1969566] Re: Default to Xorg on NVIDIA-only systems
I agree, Xorg still provides the best experience with NVIDIA. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1969566 Title: Default to Xorg on NVIDIA-only systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
** Also affects: gdm3 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Impish) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Impish) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1958488 Title: [nvidia][xorg] display hangs on boot LOGO To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876052] Re: Nvidia driver, default configuration, "Use dedicated card option" for app triggers software acceleration
** Changed in: nvidia-settings (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1876052 Title: Nvidia driver, default configuration, "Use dedicated card option" for app triggers software acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876052/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
I still can't reproduce the problem here. I am attaching the output of lspci -vvv. ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801/+attachment/5358377/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
@Daniel: I tested this on an NVIDIA only system. I am going to test again on a fresh focal installation, to see if it makes any difference. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
I have just updated an Eoan installation to Focal, enabled auto-login, and I can't reproduce the problem. I am using the 440.64 driver, and nvidia-drm.modeset is disabled. I can also see the bootsplash. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg, Pop!OS fix works.
I think forcing all users (even on systems that don't use the NVIDIA driver) to run X with root privileges would be a little heavy-handed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg, Pop!OS fix works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
@Martin: comment #13 says that autologin works without problems with nouveau. @all: are you able to use auto-login if add the following line to your /etc/X11/Xwrapper.config and reboot? needs_root_rights = yes -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Unfortunately, I can't reproduce the problem on my system, running the 435 driver in 19.10. What I don't see on my system is the following error from logind: Oct 02 21:53:45 magni /usr/lib/gdm3/gdm-x-session[1220]: (EE) Error systemd-logind returned paused fd for drm node Compare this from Martin's journald log: Oct 02 21:53:45 magni /usr/lib/gdm3/gdm-x-session[1220]: (II) xfree86: Adding drm device (/dev/dri/card0) ... Oct 02 21:53:45 magni /usr/lib/gdm3/gdm-x-session[1220]: (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 paused 1 Oct 02 21:53:45 magni /usr/lib/gdm3/gdm-x-session[1220]: (EE) Error systemd-logind returned paused fd for drm node Oct 02 21:53:45 magni /usr/lib/gdm3/gdm-x-session[1220]: (II) systemd-logind: releasing fd for 226:0 Oct 02 21:53:45 magni /usr/lib/gdm3/gdm-x-session[1220]: (--) PCI:*(1@0:0:0) 10de:1b06:1043:85e4 rev 161, Mem @ 0xde00/16777216, 0xc000/268435456, 0xd000/33554432, I/O @ 0xe000/128, BIOS @ 0x/131072 Oct 02 21:53:45 magni /usr/lib/gdm3/gdm-x-session[1220]: (II) LoadModule: "glx" With what happens on my system: ott 30 11:38:49 intel-latest /usr/lib/gdm3/gdm-x-session[2043]: (II) xfree86: Adding drm device (/dev/dri/card0) ott 30 11:38:49 intel-latest /usr/lib/gdm3/gdm-x-session[2043]: (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 paused 0 ott 30 11:38:49 intel-latest /usr/lib/gdm3/gdm-x-session[2043]: (--) PCI:*(1@0:0:0) 10de:1b80:10de:119e rev 161, Mem @ 0xf600/16777216, 0xe000/268435456, 0xf000/33554432, I/O @ 0xe000/128, ott 30 11:38:49 intel-latest /usr/lib/gdm3/gdm-x-session[2043]: (II) LoadModule: "glx" I could be an bug in logind. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822478] Re: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.
I can't reproduce the problem here on my nvidia system with the 418 driver. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1822478 Title: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822478/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Fink: I would like to see powertop when you don't use bbswitch (and the Nvidia GPU is on). More specifically, I would like to know if you can disable the Nvidia GPU using the "Tunables" tab from powertop. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Pe4enko: Here is your problem: NVRM: API mismatch: the client has the version 410.66, but NVRM: this kernel module has the version 390.87. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: components have the same version. It looks like you installed the 410.66 driver (maybe using the installer from Nvidia's website), and then tried to install the 390 driver from the Ubuntu archive. This is not going to work. Please uninstall the nvidia packages (sudo apt-get remove --purge '*nvidia*') and then use the Nvidia installer to uninstall the other driver. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Dan: I would like to see your /var/log/gpu-manager.log when in power saving mode. @Fink: please install powertop, launch it by typing "sudo powertop", and get to the "device stats" tab, to see what's drawing power. You can attach a screenshot of that. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
also, we do not rely on bbswitch any more. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Krzysztof: The NVIDIA GPU is more powerful, but also more power hungry than the Intel GPU. This is why you are seeing such a high power consumption. If you select the Intel GPU, through prime-select, then you will lose the HDMI, but power consumption should also go down. If it doesn't, it is a bug, and I am going to provide a solution in the future. As for losing the HDMI output even when both Intel and NVIDIA are enabled, that is certainly unexpected. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Gregor: that shouldn't be an issue any more, assuming that you are using the latest updates, and that you are using the nvidia driver from the ubuntu archive. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Fernando: we don't support hybrid graphics without using a display manager, as that would prevent gpu-manager from running at the right time. @Michael: I can only assume there was some failure somewhere when setting the power state of the NVIDIA GPU (the dmesg output might help). There are indeed cases in which bbswitch works best on some GPUs. This sounds like one of them. @Stefan: good. Thanks for reporting :) @Krzysztof: in your case, the NVIDIA GPU seems to be first, and the Intel GPU is seen as last. Can you set Intel as first in the BIOS, please? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Krzysztof: I don't think your GPU is the same as Andrew's. Please attach your /var/log/gpu-manager.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Leandro: please attach your /var/log/gpu-manager.log , as that might give me a clue about your system. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Andrew: sorry, but your GPU is supported only by the 340 legacy driver, and we do not support hybrid graphics with that driver. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Stefan: it seems to me that you didn't install nvidia-prime from the Ubuntu archive. @Renato: does it solve your problem if you install lightdm, and you use it instead of gdm? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Anton: you are using gdm3, right? (you can check it with "ps aux | grep gdm") @Josh: this bug report: LP: #1797147 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
You are using 4.18.12-041812-generic, which is not a supported kernel. You can uninstall the nvidia driver doing the following: sudo apt-get --purge remove libnvidia* nvidia-* On Sun, 7 Oct 2018 at 14:55, Unkraut <1778...@bugs.launchpad.net> wrote: > Please add rollback instructions. I'm now stuck with a broken intel > driver. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1778011 > > Title: > SRU: PRIME Power Saving mode draws too much power > > To manage notifications about this bug go to: > https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: product=hwe-next; status=New; importance=Undecided; > assignee=None; > Launchpad-Bug: distribution=ubuntu; sourcepackage=gdm3; component=main; > status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; > sourcepackage=nvidia-graphics-drivers-390; component=restricted; status=Fix > Released; importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; sourcepackage=nvidia-prime; > component=main; status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; sourcepackage=nvidia-settings; > component=main; status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; sourcepackage=ubuntu-drivers-common; > component=main; status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=gdm3; component=main; status=Fix Released; importance=High; > assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=nvidia-graphics-drivers-390; component=restricted; status=Fix > Committed; importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=nvidia-prime; component=main; status=Fix Committed; > importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=nvidia-settings; component=main; status=Fix Committed; > importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=ubuntu-drivers-common; component=main; status=Fix Committed; > importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug-Tags: originate-from-1788575 somerville > verification-done-bionic verification-needed > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: adblair albertomilone andrebrait brian-murray > cantfind dodger-forum fvkigg happy-snizzo ilvipero janitor lmfranco > luiscastro193 mapengyu matlit mhr3 mikhailnov new-mohammads nikperrakis > odysei renatoapdo sil2100 tjaalton ubname unkraut2 vlad-svitlichniy vorlon > ximex xintx-ua zdv80 > Launchpad-Bug-Reporter: Alberto Milone (albertomilone) > Launchpad-Bug-Modifier: Unkraut (unkraut2) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: albertomilone > -- Alberto Milone -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Renato: I might have a fix for external display in 18.10. If it works correctly, I'll backport it to 18.04. @Luiz: Gdm 3 creates one main X (or XWayland) session, and then starts an additional X for the user session. It's the default behaviour. I suspect PRIME synchronisation is only meant to happen with the internal display by default. This is beyond the scope of this SRU though. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Arthur: you probably need to install the 32 bit libraries manually from -proposed. Try with the following command: sudo apt install libnvidia-gl-390:i386/bionic-proposed as for 2), I would need some logs such as /var/log/gpu-manager.log after reproducing the problem. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Aurelijus: not yet. I am going to add support for lightdm and for sddm in the next update. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
I don't know if they updated the 396 packages to reflect my changes in nvidia-390. On Thu, 20 Sep 2018 at 22:00, Vlad Svitlichniy wrote: > Is this fix related to nvidia-390 only or will nvidia-396 from graphics- > drivers/ppa benefit from it as well? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1778011 > > Title: > SRU: PRIME Power Saving mode draws too much power > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=gdm3; component=main; > status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; > sourcepackage=nvidia-graphics-drivers-390; component=restricted; status=Fix > Released; importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; sourcepackage=nvidia-prime; > component=main; status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; sourcepackage=nvidia-settings; > component=main; status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; sourcepackage=ubuntu-drivers-common; > component=main; status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=gdm3; component=main; status=Fix Committed; importance=High; > assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=nvidia-graphics-drivers-390; component=restricted; status=Fix > Committed; importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=nvidia-prime; component=main; status=Fix Committed; > importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=nvidia-settings; component=main; status=Fix Committed; > importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=ubuntu-drivers-common; component=main; status=Fix Committed; > importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug-Tags: verification-done-bionic verification-needed > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: albertomilone andrebrait brian-murray cantfind > dodger-forum happy-snizzo ilvipero janitor luiscastro193 mapengyu > mikhailnov odysei sil2100 tjaalton ubname vlad-svitlichniy vorlon ximex > xintx-ua > Launchpad-Bug-Reporter: Alberto Milone (albertomilone) > Launchpad-Bug-Modifier: Vlad Svitlichniy (vlad-svitlichniy) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: albertomilone > -- Alberto Milone -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@ubname: installing the meta-package worked here, but you can install the single packages manually: sudo apt install libnvidia-gl-390/bionic-proposed libnvidia-compute-390 /bionic-proposed libnvidia-decode-390/bionic-proposed libnvidia- encode-390/bionic-proposed libnvidia-ifr1-390/bionic-proposed libnvidia- fbc1-390/bionic-proposed You might have to do the same for the i386 dependencies. ** Tags removed: verification-failed-bionic ** Tags added: verification-needed-bionic ** Description changed: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. - _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-proposed - nvidia-settings/bionic-proposed + nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-proposed + libnvidia-compute-390/bionic-proposed libnvidia-decode-390/bionic- + proposed libnvidia-encode-390/bionic-proposed libnvidia-ifr1-390/bionic- + proposed libnvidia-fbc1-390/bionic-proposed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Thomas: sorry but support for Lightdm and SDDM will be available in the next update. On Thu, 20 Sep 2018 at 10:06, Thomas Rupprecht < rupprecht.thomas+launch...@gmail.com> wrote: > Should this also work with Kubuntu 18.04 with SDDM instead of GDM3? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1778011 > > Title: > SRU: PRIME Power Saving mode draws too much power > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=gdm3; component=main; > status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; > sourcepackage=nvidia-graphics-drivers-390; component=restricted; status=Fix > Released; importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; sourcepackage=nvidia-prime; > component=main; status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; sourcepackage=nvidia-settings; > component=main; status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; sourcepackage=ubuntu-drivers-common; > component=main; status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=gdm3; component=main; status=Fix Committed; importance=High; > assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=nvidia-graphics-drivers-390; component=restricted; status=Fix > Committed; importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=nvidia-prime; component=main; status=Fix Committed; > importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=nvidia-settings; component=main; status=Fix Committed; > importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=ubuntu-drivers-common; component=main; status=Fix Committed; > importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug-Tags: verification-done-bionic verification-needed > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: albertomilone andrebrait brian-murray cantfind > dodger-forum happy-snizzo ilvipero janitor luiscastro193 mikhailnov odysei > sil2100 tjaalton ubname vorlon ximex xintx-ua > Launchpad-Bug-Reporter: Alberto Milone (albertomilone) > Launchpad-Bug-Modifier: Thomas Rupprecht (ximex) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: albertomilone > -- Alberto Milone -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Aurelijus: please follow these steps for testing: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-proposed nvidia-settings/bionic-proposed ** Description changed: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. - [Test Case] - 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 + 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia - [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. + + + _ + * Steps to test the updates: + + 1) Enable the bionic-proposed repositories + + 2) Create /etc/apt/preferences.d/proposed-updates with the following + content: + + Package: * + Pin: release a=bionic-proposed + Pin-Priority: 400 + + 3) Update the list of packages: + + sudo apt-get update + + 4) Install the packages from -proposed using the following command: + + sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-proposed + ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-proposed + nvidia-settings/bionic-proposed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Steve, Brian: I have re-uploaded ubuntu-drivers-common 1:0.5.2.1, now with code to prevent shipping the __pycache__ cruft. While running debdiff against 1:0.5.2 will still mention the cruft, if you run "lintian -v ubuntu-drivers-common_0.5.2.1.dsc --pedantic", lintian won't complain about "source-contains-prebuilt-python-object" any more. I hope we can finally get ubuntu-drivers-common into bionic-proposed now, or verification for this bug report will keep failing. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
** Tags removed: verification-failed-bionic ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Serhiy Zahoriya: sorry but ubuntu-drivers-common (1:0.5.2.1) doesn't seem to be in bionic-proposed yet. No wonder things failed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
On Mon, 27 Aug 2018 at 23:01, Mikhail Novosyolov <1778...@bugs.launchpad.net> wrote: > Can you please explain why is nvidia-fallback needed? It worked without > it before. > I am trying to remove it with this SRU. -- Alberto Milone -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
On Wed, 15 Aug 2018 at 23:20, Steve Langasek
wrote:
> Reviewing ubuntu-drivers-common in the queue, I notice:
>
> +if (!match) {
> +free(match);
>
> Surely no good can come of this call to free() and it should be omitted?
>
Nice catch. I think it was just debris, but it wouldn't have caused any
problem, since match could be either a valid string or NULL, and freeing a
NULL pointer results in a no-op. I have addressed this though.
>
> The change to start before oem-config.service seems correct but has no
> associated bug linked. This looks to me like it should still go through
> the SRU verification process because it's unrelated to the other
> changes. (Also, it's not 100% obvious that the change is correct: for
> example, why does oem-config not provide display-manager.service? Why
> are there no interdependencies between oem-config's systemd units and
> display-manager.service?)
>
>
I am not sure why oem-config does not provide display-manager.service, but
this change suits our needs, which I have now filed in a separate bug
report (LP: #1789201), and referenced in the changelog.
> The source package as uploaded appears to have a lot of cruft in various
> __pycache__ directories. This ought to be cleaned up.
>
>
This should not be a problem in my last upload.
--
Alberto Milone
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1778011
Title:
SRU: PRIME Power Saving mode draws too much power
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@monogato: please give us time to get all the components into the -proposed repository first. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
I am going to have a look at this soon.
On Wed, 15 Aug 2018 at 23:20, Steve Langasek
wrote:
> Reviewing ubuntu-drivers-common in the queue, I notice:
>
> +if (!match) {
> +free(match);
>
> Surely no good can come of this call to free() and it should be omitted?
>
> The change to start before oem-config.service seems correct but has no
> associated bug linked. This looks to me like it should still go through
> the SRU verification process because it's unrelated to the other
> changes. (Also, it's not 100% obvious that the change is correct: for
> example, why does oem-config not provide display-manager.service? Why
> are there no interdependencies between oem-config's systemd units and
> display-manager.service?)
>
> The source package as uploaded appears to have a lot of cruft in various
> __pycache__ directories. This ought to be cleaned up.
>
> I'm going to go ahead and reject based on the missing bug reference for
> the oem-config.service change. If you think this is wrong, feel free to
> ping me on IRC to discuss.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1778011
>
> Title:
> SRU: PRIME Power Saving mode draws too much power
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: distribution=ubuntu; sourcepackage=gdm3; component=main;
> status=Fix Released; importance=High; assignee=
> alberto.mil...@canonical.com;
> Launchpad-Bug: distribution=ubuntu;
> sourcepackage=nvidia-graphics-drivers-390; component=restricted; status=Fix
> Released; importance=High; assignee=alberto.mil...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; sourcepackage=nvidia-prime;
> component=main; status=Fix Released; importance=High; assignee=
> alberto.mil...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; sourcepackage=nvidia-settings;
> component=main; status=Fix Released; importance=High; assignee=
> alberto.mil...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; sourcepackage=ubuntu-drivers-common;
> component=main; status=Fix Released; importance=High; assignee=
> alberto.mil...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; distroseries=bionic;
> sourcepackage=gdm3; component=main; status=In Progress; importance=High;
> assignee=alberto.mil...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; distroseries=bionic;
> sourcepackage=nvidia-graphics-drivers-390; component=restricted; status=In
> Progress; importance=High; assignee=alberto.mil...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; distroseries=bionic;
> sourcepackage=nvidia-prime; component=main; status=In Progress;
> importance=High; assignee=alberto.mil...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; distroseries=bionic;
> sourcepackage=nvidia-settings; component=main; status=In Progress;
> importance=High; assignee=alberto.mil...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; distroseries=bionic;
> sourcepackage=ubuntu-drivers-common; component=main; status=In Progress;
> importance=High; assignee=alberto.mil...@canonical.com;
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: albertomilone andrebrait cantfind ilvipero
> janitor vorlon
> Launchpad-Bug-Reporter: Alberto Milone (albertomilone)
> Launchpad-Bug-Modifier: Steve Langasek (vorlon)
> Launchpad-Message-Rationale: Subscriber
> Launchpad-Message-For: albertomilone
>
--
Alberto Milone
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1778011
Title:
SRU: PRIME Power Saving mode draws too much power
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Software rendering is a better bet if DKMS fails, as nouveau can cause problems when dealing with (partially?) supported GPUs. I introduced that change in bionic, but then I reverted that behaviour, also because it would cause problems to hybrid graphics. I don't think users relying on something that is broken should hold us back. If anything, the fallback would cause users to file bug reports (about graphics corruption, increased power consumption, etc.) against nvidia, where these would be really nouveau's. On Thu, 16 Aug 2018 at 00:36, Steve Langasek wrote: > Bug description says: > > > [Regression Potential] > > Low, as hybrid graphics support does not work correctly, and the changes > only affect > > this use case. > > Dropping the nvidia-fallback service means that any time the nvidia > module has failed to be loaded, including if the nvidia module has > failed to build for any reason, the nouveau module will not be loaded in > its place. This is a behavior change that potentially affects users > other than those with hybrid graphics. Is that a concern? How long has > the existing behavior been there, and what are the chances that users > may be inadvertently relying on the current fallback behavior without > knowing it? > > ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) >Status: In Progress => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1778011 > > Title: > SRU: PRIME Power Saving mode draws too much power > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=gdm3; component=main; > status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; > sourcepackage=nvidia-graphics-drivers-390; component=restricted; status=Fix > Released; importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; sourcepackage=nvidia-prime; > component=main; status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; sourcepackage=nvidia-settings; > component=main; status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; sourcepackage=ubuntu-drivers-common; > component=main; status=Fix Released; importance=High; assignee= > alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=gdm3; component=main; status=In Progress; importance=High; > assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=nvidia-graphics-drivers-390; component=restricted; > status=Incomplete; importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=nvidia-prime; component=main; status=In Progress; > importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=nvidia-settings; component=main; status=In Progress; > importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=bionic; > sourcepackage=ubuntu-drivers-common; component=main; status=In Progress; > importance=High; assignee=alberto.mil...@canonical.com; > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: albertomilone andrebrait cantfind ilvipero > janitor vorlon > Launchpad-Bug-Reporter: Alberto Milone (albertomilone) > Launchpad-Bug-Modifier: Steve Langasek (vorlon) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: albertomilone > -- Alberto Milone -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()
The drm_mode_get_hv_timing() function (used in the required kernel commit) depends on a non trivial amount of other changes, and I don't think a backport would be easy, or safe. That commit will be available in Linux 4.17, though, so we are going to get the fix in Ubuntu 18.10. ** Changed in: linux (Ubuntu) Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1754949 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754949/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
** Also affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-settings (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-settings (Ubuntu) Status: New => In Progress ** Changed in: nvidia-settings (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-settings (Ubuntu) Status: In Progress => Fix Released ** Changed in: nvidia-settings (Ubuntu Bionic) Importance: Undecided => High ** Changed in: nvidia-settings (Ubuntu Bionic) Status: New => In Progress ** Changed in: nvidia-settings (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778011] Re: PRIME Power Saving mode draws too much power
** Description changed: Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. - Solving the problem in systemd (LP: #1777099), and adding code in gpu- - manager and in nvidia-prime to unload the nvidia modules, and to allow - the PCI device to sleep, dramatically decreases power consumption. + Furthermore, if the main X/Xwayland session was started by Gdm when the + nvidia driver was loaded, the session will keep the nvidia module + loaded, and prevent the system from switching off the dGPU. Also, the + nouveau driver will be loaded, if nvidia is not, and this can cause + problems to unsupported NVIDIA GPUs. + + The solution involves the following changes: + + 1) Solving the problem in systemd (LP: #1777099) + + 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia + modules, and to allow the PCI device to sleep. + + 3) Making a slight change to the current patch in Gdm, used to call the + PRIME scripts before and after a Gdm session (so that gpu-manager gets + actually called on log out) + + 4) Adding code in gpu-manager to kill the main X/Xwayland session on log + out, if the session is preventing us from unloading the nvidia driver. A + new X/Xwayland session will be created after unload the module. + + 5) Removing the systemd service that loads nouveau from the nvidia + packages. ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Description changed: - Relying on the nouveau driver and on the vga switcheroo (to get around a - change in systemd LP: #1777099) caused increased power consumption, and - slowed down the switching process. + SRU Request: + + [Impact] + Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. + + + [Test Case] + 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 + + 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): + sudo prime-select nvidia + + 3) Restart your computer and attach your /var/log/gpu-manager.log. see + if the system boots correctly. If unsure, please attach your /var/log + /gpu-manager.log and /var/log/Xorg.0.log + + 4) Select power saving mode: + sudo prime-select intel + + 5) Log out and log back in + + 6) Check if the nvidia driver is still loaded: + lsmod | grep nvidia + + + [Regression Potential] + Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. ** Summary changed: - PRIME Power Saving mode draws too much power + SRU: PRIME Power Saving mode draws too much power -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubunt
[Bug 1778011] Re: PRIME Power Saving mode draws too much power
** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu) Status: New => In Progress ** Changed in: gdm3 (Ubuntu) Importance: Undecided => High ** Changed in: gdm3 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: gdm3 (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: gdm3 (Ubuntu Bionic) Importance: Undecided => High ** Changed in: gdm3 (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1754949 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754949/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1777099] Re: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1
** Changed in: systemd (Ubuntu) Status: Triaged => In Progress ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => High ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1777099 Title: [backport] DRM devices opened by logind stay referenced indefinitely by PID 1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1777099/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1752123] Re: Force 8bit RGB config
** Changed in: mutter (Ubuntu) Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1752123 Title: Force 8bit RGB config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cogl/+bug/1752123/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1752123] Re: Force 8bit RGB config
** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: mutter (Ubuntu) Status: New => In Progress ** Changed in: mutter (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1752123 Title: Force 8bit RGB config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cogl/+bug/1752123/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1697882] Re: GDM should not allow X11 sessions when NVIDIA's KMS is enabled
@Doug: we are going to leave PRIME systems alone in any case. This bug report is about non hybrid systems. You are using the intel GPU to drive the screen, and that is why X11 + KMS works for you. As far as I know, Wayland doesn't support that yet. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1697882 Title: GDM should not allow X11 sessions when NVIDIA's KMS is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1697882/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1697882] Re: GDM should not allow X11 sessions when NVIDIA's KMS is enabled
** Bug watch added: GNOME Bug Tracker #784470 https://bugzilla.gnome.org/show_bug.cgi?id=784470 ** Also affects: gdm via https://bugzilla.gnome.org/show_bug.cgi?id=784470 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1697882 Title: GDM should not allow X11 sessions when NVIDIA's KMS is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1697882/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1697882] Re: GDM should not allow X11 sessions when NVIDIA's KMS is enabled
** Changed in: gdm3 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: gdm3 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1697882 Title: GDM should not allow X11 sessions when NVIDIA's KMS is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1697882/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1697882] [NEW] GDM should not allow X11 sessions when NVIDIA's KMS is enabled
Public bug reported: Due to a current limitation in the nvidia binary driver, when enabling KMS (to use Wayland), any X11 sessions will crash. Ideally, GDM would check if modesetting is enabled in the nvidia driver, and blacklist the X11 sessions. The following command can tell you whether the parameter is enabled or not: :$ sudo cat /sys/module/nvidia_drm/parameters/modeset Y NOTE: KMS is disabled by default in the nvidia driver, and it is possible to enable it by editing the following file /etc/modprobe.d/nvidia-graphics-drivers.conf and by changing the following line: options nvidia_375_drm modeset=0 to this: options nvidia_375_drm modeset=1 Then you will probably have to update the initramfs too. ** Affects: gdm3 (Ubuntu) Importance: Medium Status: New ** Changed in: gdm3 (Ubuntu) Importance: Undecided => Medium ** Description changed: Due to a current limitation in the nvidia binary driver, when enabling KMS (to use Wayland), any X11 sessions will crash. Ideally, GDM would check if modesetting is enabled in the nvidia driver, and blacklist the X11 sessions. The following command can tell you whether the parameter is enabled or not: :$ sudo cat /sys/module/nvidia_drm/parameters/modeset Y NOTE: KMS is disabled by default in the nvidia driver, and it is possible to enable it by editing the following file - /etc/modprobe.d/nvidia-graphics-drivers.com + /etc/modprobe.d/nvidia-graphics-drivers.conf and by changing the following line: options nvidia_375_drm modeset=0 to this: options nvidia_375_drm modeset=1 Then you will probably have to update the initramfs too. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1697882 Title: GDM should not allow X11 sessions when NVIDIA's KMS is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1697882/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1608033] Re: nvidia-prime failed to switch to the Intel card
I suspect gdm is not calling gpu-manager, which would make it a bug in gdm. ** Also affects: gdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1608033 Title: nvidia-prime failed to switch to the Intel card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1608033/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1262068] Re: nvidia-prime should support gdm also
@Jean: please attach your /var/log/gpu-manager.log ** Changed in: ubuntu-drivers-common (Ubuntu Trusty) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1262068 Title: nvidia-prime should support gdm also To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1262068/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
** Changed in: unity-settings-daemon (Ubuntu Trusty) Assignee: (unassigned) = Alberto Milone (albertomilone) ** Changed in: unity-settings-daemon (Ubuntu Trusty) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1287341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
Just an update: I've backported a system that should work better than single quirks. This is also what AceLan tested for me. I've made a merge request into the bazaar branch of unity-settings- daemon, so that my code can be reviewed and accepted into 14.10. As soon as the merge is complete, we'll backport the feature to 14.04 (it's the same codebase). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1287341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
** Description changed: + Expected results: + The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor + + Actual results: + The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). + + + SRU Request: + + Laptops and all-in-one systems with touchscreens don't currently map the + touch input device onto the internal display. As a result, when the + screen changes (e.g. the main output is rotated or an external output is + connected), the touch input device maps onto the entire screen, + regardless of the only relevant area, thus making the touchscreen + completely useless. + + [Impact] + * The touchscreen becomes unusable if an external output is connected or if the main output is rotated. + + [Test Case] + * Either plug in an external monitor or rotate the internal monitor + - Expected: the touchscreen should respond to touch as usual. + - Bad behavior: the touchscreen is unusable and responds by selecting areas other than the one the user actually selects. + + [Regression Potential] + * Low, it only affects the main touchscreen (tablets or multiple touchscreens are not supported) and it only adds a feature that is currently missing. + + [Other Info] + * N/A + + --- + My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. - To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). - This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 .tmp.unity.support.test.0: - + ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 3 14:41:14 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: - # This is a distribution channel descriptor - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-precise-amd64-20130203-1 + Â # This is a distribution channel descriptor + Â # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + Â canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: - oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, x86_64: installed - virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed - virtualbox, 4.3.6, 3.13.0-14-generic, x86_64: installed - virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed + Â oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, x86_64: installed + Â virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed + Â virtualbox,
[Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
Yes, the Dell Inspiron 20 Model 3048 works without quirks because it uses an eDP connector. I've just implemented a quirks system which should fix the Dell OptiPlex 9030 AIO and possibly other Dells with similar specs. Please try the updated packages available here: http://people.canonical.com/~amilone/lp1287341/ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1287341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
Ok, I've corrected the quirk for the OptiPlex and I've added one for the Inspiron 2350. Please try the updated packages available here: http://people.canonical.com/~amilone/lp1287341/ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1287341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
@Acelan: please download the following binary, run it on that system, and attach the output: http://people.canonical.com/~amilone/simple-xinput Also please attach your /var/log/Xorg.0.log and the output of the xinput list --long command. Note: in this case there's no need to reproduce the problem before collecting the data, this is just to see what type of touchscreen we're dealing with. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1287341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
ok, what happens if you type: killall unity-settings-daemon unity-settings-daemon --debug mylog.log then reproduce the problem and attach the log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1287341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
The problem with all-in-one systems that don't use connectors such as eDP is that we don't have a generic way to match the display with the input device. This means that we have to quirk such systems using the display EDID and the input controller. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1287341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
AceLan: please attach the output of the following commands for all the all-in-one systems you have available (with no external screens connected): 1) xrandr --verbose 2) xinput list --long 3) /var/log/Xorg.0.log You can collect the data using a livecd of Ubuntu 14.04 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1287341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
I've built packages for both i386 and amd64 with my fix. You will find them here: http://people.canonical.com/~amilone/lp1287341/ Please install the package for your architecture, then log out, log back in, and try to reproduce the problem. It would be interesting to test my fix on laptops with a touchscreen and on all-in-one desktop systems that have a touchscreen. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1287341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
I've gone through all the relevant upstream commits, and here are my conclusions: 1) The upstream code covers the use case of Wacom tablets with built-in displays (which, although useful, is not the use case discussed in this bug report). It would be way too much code to backport, especially for an SRU. 2) The upstream code covers the use case mentioned in the original description of this bug report, but I think backporting the new GsdDeviceMapper (a tool to couple input devices with displays) to unity- settings-daemon would be an overkill, just for this single use case. This said, introducing the GsdDeviceMapper is something definitely worth exploring, as a long term plan. 3) I can provide a fix for the use case in the original description with a much smaller amount of code. For this reason I'm going to complete and integrate my current prototype with the unity-settings-daemon. The result will be effective and good for an SRU. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1287341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
I already have a prototype that solves the use case mentioned in this bug report. Apparently upstream also has code that fixes the same issue and covers more use cases. It doesn't seem like a small amount of code though. For this reason I'll take some time to see if a backport is possible or recommended over using my current implementation. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1287341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
Just as an update, I'm working on some code that will detect the touch screen, couple it with the laptop's screen, and map the touch input device onto the output whenever the screen configuration changes (e.g. on rotations, when new outputs become available, etc.). This won't require any user interaction. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1287341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
** Changed in: unity-settings-daemon (Ubuntu) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1287341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
@Steve: please attach the output of the following commands: xinput list Then look at the output and see what id matches your touchscreen (e.g. id=12), and finally type: xinput list-props $the_id_you_found -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1287341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
** Changed in: unity-settings-daemon (Ubuntu) Assignee: (unassigned) = Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1287341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1262068] Re: nvidia-prime should support gdm also
@Tim: as for permission, maybe the gdm user doesn't have the same permissions as a standard user? As for the stop script, wouldn't that require GDM to be stopped (rather than just X)? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1262068 Title: nvidia-prime should support gdm also To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1262068/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1224254] Re: xrandr Xerrors with the nvidia binary drivers (optimus)
** Changed in: gnome-desktop3 (Ubuntu) Status: In Progress = Fix Released ** Changed in: gnome-desktop3 (Ubuntu Precise) Status: In Progress = Fix Committed ** Changed in: gnome-desktop3 (Ubuntu Saucy) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1224254 Title: xrandr Xerrors with the nvidia binary drivers (optimus) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1224254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1224254] Re: xrandr Xerrors with the nvidia binary drivers (optimus)
** Changed in: gnome-settings-daemon (Ubuntu) Status: Invalid = Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1224254 Title: xrandr Xerrors with the nvidia binary drivers (optimus) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1224254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1224254] Re: xrandr Xerrors with the nvidia binary drivers (optimus)
Apparently the modesetting driver doesn't play well when trying to set the primary output (which does not seem to be supported by the driver). In any case, we should really make sure to trap the XError and to ignore it when setting the primary output, instead of only ignoring the error when we look for the primary output. This solves the problem in libgnome-desktop. ** Also affects: gnome-desktop-3 (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-desktop-3 (Ubuntu) Assignee: (unassigned) = Alberto Milone (albertomilone) ** Changed in: gnome-settings-daemon (Ubuntu) Status: Triaged = Invalid ** Changed in: gnome-desktop-3 (Ubuntu) Status: New = In Progress ** Changed in: nvidia-graphics-drivers-319 (Ubuntu) Status: Triaged = Invalid ** Changed in: gnome-desktop-3 (Ubuntu) Importance: Undecided = High ** Changed in: gnome-settings-daemon (Ubuntu) Assignee: Alberto Milone (albertomilone) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1224254 Title: xrandr Xerrors with the nvidia binary drivers (optimus) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop-3/+bug/1224254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1224254] Re: xrandr Xerrors with the nvidia binary drivers (optimus)
** Package changed: gnome-desktop-3 (Ubuntu) = gnome-desktop3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1224254 Title: xrandr Xerrors with the nvidia binary drivers (optimus) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1224254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1224254] Re: xrandr Xerrors with the nvidia binary drivers (optimus)
** Also affects: gnome-settings-daemon (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: gnome-desktop3 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-modesetting (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-319 (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: gnome-desktop3 (Ubuntu Precise) Status: New = In Progress ** Changed in: gnome-desktop3 (Ubuntu Precise) Importance: Undecided = High ** Changed in: gnome-desktop3 (Ubuntu Precise) Assignee: (unassigned) = Alberto Milone (albertomilone) ** No longer affects: gnome-settings-daemon (Ubuntu Precise) ** No longer affects: nvidia-graphics-drivers-319 (Ubuntu Precise) ** Changed in: xserver-xorg-video-modesetting (Ubuntu Precise) Status: New = Triaged ** Changed in: xserver-xorg-video-modesetting (Ubuntu) Importance: High = Medium ** Changed in: xserver-xorg-video-modesetting (Ubuntu Precise) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1224254 Title: xrandr Xerrors with the nvidia binary drivers (optimus) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1224254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1224254] Re: xrandr Xerrors with the nvidia binary drivers (optimus)
** Patch added: debdiff for trusty https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1224254/+attachment/3922068/+files/gnome-desktop3_3.8.4-0ubuntu2.debdiff -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1224254 Title: xrandr Xerrors with the nvidia binary drivers (optimus) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1224254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1224254] Re: xrandr Xerrors with the nvidia binary drivers (optimus)
** Bug watch added: GNOME Bug Tracker #719784 https://bugzilla.gnome.org/show_bug.cgi?id=719784 ** Also affects: gnome-desktop via https://bugzilla.gnome.org/show_bug.cgi?id=719784 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1224254 Title: xrandr Xerrors with the nvidia binary drivers (optimus) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1224254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1224254] Re: xrandr Xerrors with the nvidia binary drivers (optimus)
** Also affects: gnome-settings-daemon (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: gnome-desktop3 (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-modesetting (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-319 (Ubuntu Saucy) Importance: Undecided Status: New ** No longer affects: gnome-settings-daemon (Ubuntu) ** No longer affects: gnome-settings-daemon (Ubuntu Saucy) ** Changed in: gnome-desktop3 (Ubuntu Saucy) Status: New = In Progress ** Changed in: gnome-desktop3 (Ubuntu Saucy) Importance: Undecided = High ** Changed in: gnome-desktop3 (Ubuntu Saucy) Assignee: (unassigned) = Alberto Milone (albertomilone) ** Changed in: xserver-xorg-video-modesetting (Ubuntu Saucy) Status: New = Triaged ** Changed in: xserver-xorg-video-modesetting (Ubuntu Saucy) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1224254 Title: xrandr Xerrors with the nvidia binary drivers (optimus) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1224254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1224254] Re: xrandr Xerrors with the nvidia binary drivers
I can reproduce this when using the nvidia driver and offloading rendering to it using RandR on an NVIDIA Optimus system. This is what nvidia-prime does and what NVIDIA suggests on their website. I've assigned the bug report to both the nvidia driver and the modesettings driver since they are both used. The modesettings driver is the one which ultimately deals with RandR (and therefore the gnome- settings-daemon). ** Also affects: xserver-xorg-video-modesetting (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-319 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-319 (Ubuntu) Status: New = Triaged ** Changed in: xserver-xorg-video-modesetting (Ubuntu) Status: New = Triaged ** Changed in: gnome-settings-daemon (Ubuntu) Status: Confirmed = Invalid ** Changed in: nvidia-graphics-drivers-319 (Ubuntu) Importance: Undecided = Medium ** Changed in: xserver-xorg-video-modesetting (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1224254 Title: xrandr Xerrors with the nvidia binary drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1224254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1224254] Re: xrandr Xerrors with the nvidia binary drivers
Apparently, if I use the intel driver instead of the modesettings driver, I can't reproduce the problem. This is not a bug in the nvidia driver, it's definitely an issue in the modesetting driver. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1224254 Title: xrandr Xerrors with the nvidia binary drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1224254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1224254] Re: xrandr Xerrors with the nvidia binary drivers
I take back what I said, I had a false positive. I probably know what's going on but I need to investigate this a little further. ** Changed in: gnome-settings-daemon (Ubuntu) Status: Invalid = Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1224254 Title: xrandr Xerrors with the nvidia binary drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1224254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1224254] Re: xrandr Xerrors with the nvidia binary drivers
** Changed in: gnome-settings-daemon (Ubuntu) Assignee: (unassigned) = Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1224254 Title: xrandr Xerrors with the nvidia binary drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1224254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1248152] Re: Gtk.FileChooserWidget won't show the create folder button
Yes, same problem without passing the self (I've just noticed that the parent widget is not needed) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1248152 Title: GObject constructor silently accepts and ignores positional arguments To manage notifications about this bug go to: https://bugs.launchpad.net/pygobject/+bug/1248152/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 856312] Re: Can't use non-mirrored resolution with two monitors
This is really a limitation in the RandR implementation of the fglrx driver which doesn't support dynamic front buffer reallocation. There is nothing we can do about this. ** Changed in: fglrx-installer (Ubuntu) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/856312 Title: Can't use non-mirrored resolution with two monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/856312/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 118605] Re: [fglrx] freezes upon Logout or Switch user [patch]
** Changed in: linux-restricted-modules-envy-2.6.24 (Ubuntu) Status: In Progress = Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/118605 Title: [fglrx] freezes upon Logout or Switch user [patch] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/118605/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 432814] Re: Touchpad: Action for middle and right click is reversed since jaunty
** Changed in: gnome-settings-daemon (Ubuntu Lucid) Assignee: Alberto Milone (albertomilone) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/432814 Title: Touchpad: Action for middle and right click is reversed since jaunty To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/432814/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 410636] Re: Right-click should not pre-light first option, too easy to accidentally select the first Context-menu option.
** Changed in: hundredpapercuts Assignee: Alberto Milone (albertomilone) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/410636 Title: Right-click should not pre-light first option, too easy to accidentally select the first Context-menu option. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/410636/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 563276] Re: No way to tweak multi-finger tap reaction
** Changed in: gnome-settings-daemon (Ubuntu) Assignee: Alberto Milone (albertomilone) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/563276 Title: No way to tweak multi-finger tap reaction To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/563276/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1029089] Re: monitor resolution does not go back to 1440x900 after change
if you're using the nvidia driver you might want to set the resolution using the nvidia-settings tool -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1029089 Title: monitor resolution does not go back to 1440x900 after change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1029089/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1043759] Re: Display settings confirmation dialog appears out of the screen when disabling one monitor in a multi monitor setup
** Also affects: compiz (Ubuntu) Importance: Undecided Status: New ** Changed in: compiz (Ubuntu) Assignee: (unassigned) = Sam Spilsbury (smspillaz) ** Project changed: compiz = compiz-core ** Changed in: compiz (Ubuntu) Status: New = Triaged ** Changed in: compiz (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1043759 Title: Display settings confirmation dialog appears out of the screen when disabling one monitor in a multi monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-core/+bug/1043759/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1043759] Re: Display settings confirmation dialog appears out of the screen when disabling one monitor in a multi monitor setup
** Also affects: compiz Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1043759 Title: Display settings confirmation dialog appears out of the screen when disabling one monitor in a multi monitor setup To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1043759/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 647063] Re: Jerky h.264 video playback
Ignore my comment, it was an issue with the mode that I was using on my HDTV. -- Jerky h.264 video playback https://bugs.launchpad.net/bugs/647063 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gst-plugins-good0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 647063] Re: Jerky h.264 video playback
I don't why but this update makes my XVID MPEG-4 (624 x 352) videoclips stutter when I play them. If I install 0.10.25-4ubuntu1 I'm unable to reproduce the issue. This is weird as I don't think flvdemux is used for XVID MPEG-4. -- Jerky h.264 video playback https://bugs.launchpad.net/bugs/647063 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gst-plugins-good0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 410636] Re: Right-click should not pre-light first option, too easy to accidentally select the first Context-menu option.
** Changed in: hundredpapercuts Status: In Progress = Confirmed -- Right-click should not pre-light first option, too easy to accidentally select the first Context-menu option. https://bugs.launchpad.net/bugs/410636 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 410636] Re: Right-click should not pre-light first option, too easy to accidentally select the first Context-menu option.
** Changed in: hundredpapercuts Status: Confirmed = In Progress -- Right-click should not pre-light first option, too easy to accidentally select the first Context-menu option. https://bugs.launchpad.net/bugs/410636 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 508890] Re: Nautilus crashes when there are multiple XScreens
@GiBSON: I think you're experiencing a different bug. Please file a new bug report about it. @Roman: it looks like Robert Ancell re-enabled that patch (91_correct_rgba_use.patch) in nautilus 1:2.30.1-1ubuntu1 -- Nautilus crashes when there are multiple XScreens https://bugs.launchpad.net/bugs/508890 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 410636] Re: Right-click should not pre-light first option, too easy to accidentally select the first Context-menu option.
** Changed in: hundredpapercuts Assignee: (unassigned) = Alberto Milone (albertomilone) ** Changed in: hundredpapercuts Status: Triaged = In Progress -- Right-click should not pre-light first option, too easy to accidentally select the first Context-menu option. https://bugs.launchpad.net/bugs/410636 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 410636] Re: Right-click should not pre-light first option, too easy to accidentally select the first Context-menu option.
I've provided a patch in the upstream bug report. Here's a PPA with my patched gtk+ for both Lucid and Maverick, if you want to test it: https://launchpad.net/~albertomilone/+archive/papercuts -- Right-click should not pre-light first option, too easy to accidentally select the first Context-menu option. https://bugs.launchpad.net/bugs/410636 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 553200] Re: Mouse and keyboard stop working after selecting user
@Shannon Please remove the repository that you added (as it's an html page), then follow the instructions available on this page: https://launchpad.net/+help/soyuz/ppa-sources-list.html and use the following PPA: ppa:albertomilone/proprietary-video-improvements -- Mouse and keyboard stop working after selecting user https://bugs.launchpad.net/bugs/553200 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 553200] Re: Mouse and keyboard stop working after selecting user
I have uploaded the fix in Ubuntu Lucid, however my upload will be approved only after Lucid's RC is released. In the meantime, if you want to test the driver, you can install it from my PPA (as soon as the packages are built): https://launchpad.net/~albertomilone/+archive/proprietary-video-improvements -- Mouse and keyboard stop working after selecting user https://bugs.launchpad.net/bugs/553200 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 432814] Re: Touchpad: Action for middle and right click is reversed since jaunty
I've reverted my changes to the gnome-settings-daemon and I did the same with synaptics driver default settings. Now we're more compliant with upstream's default settings (both Gnome and synaptics use 1 3 2 instead of 1 2 3). I definitely agree that a we need an easy way to make this configurable but it's too late to make such changes in Lucid. Hopefully I'll have enough time to deal with this in Maverick. -- Touchpad: Action for middle and right click is reversed since jaunty https://bugs.launchpad.net/bugs/432814 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
