[Bug 1820859] Re: /usr/bin/nautilus:11:g_application_impl_get_dbus_object_path:g_application_get_dbus_object_path:update_dbus_opened_locations:bus_acquired_cb:connection_get_cb
How to reproduce this ? Previously crash was in `nautilus_window_slot_get_location` which is now fixed upstream. With 3.32.1-1ubuntu1, I can't reproduce with G_MESSAGES_DEBUG=all /usr/bin/nautilus. Can you copy/paste error as I don't have access? But we don't really to update windows locations when org.freedesktop.FileManager1 is acquired or being acquired. If there is still a error I will open a merge. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1820859 Title: /usr/bin/nautilus:11:g_application_impl_get_dbus_object_path:g_application_get_dbus_object_path:update_dbus_opened_locations:bus_acquired_cb:connection_get_cb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821870] Re: gnome-shell segfault libmutter-clutter-2
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1821870 Title: gnome-shell segfault libmutter-clutter-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821870/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1824657] Re: GNOME shell crash
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1824657 Title: GNOME shell crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824657/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1824578] Re: Screen lock doesn't lock Launcher (left-sidebar) and Status Menus (Indicators)
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1824578 Title: Screen lock doesn't lock Launcher (left-sidebar) and Status Menus (Indicators) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824578/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832792] Re: App-switcher icons too small with hidpi (3000x2000) monitor
** Changed in: gnome-shell Status: Unknown => New -- 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/1832792 Title: App-switcher icons too small with hidpi (3000x2000) monitor To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1832792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1831161] Re: App-switcher icons too small with hidpi monitor and 1.25 scaling
** Tags added: hidpi -- 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/1831161 Title: App-switcher icons too small with hidpi monitor and 1.25 scaling To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1831161/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832792] Re: App-switcher icons too small with hidpi (3000x2000) monitor
** Tags added: hidpi ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1370 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1370 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1370 Importance: Unknown Status: Unknown -- 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/1832792 Title: App-switcher icons too small with hidpi (3000x2000) monitor To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1832792/+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 results in no monitors detected by Xorg
Nvidia 430.26 behaves a bit differently. It just fails to start as non- root and gives reasons: [ 897.467] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) ... [ 897.470] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 897.470] (EE) NVIDIA: system's kernel log for additional error messages and [ 897.470] (EE) NVIDIA: consult the NVIDIA README for details. [ 897.470] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the [ 897.470] (EE) NVIDIA: system's kernel log for additional error messages and [ 897.470] (EE) NVIDIA: consult the NVIDIA README for details. [ 897.470] (EE) [drm] Failed to open DRM device for (null): -2 [ 897.470] (EE) [drm] Failed to open DRM device for pci::01:00.0: -2 So then the NVIDIA driver gives up and Xorg tries the modeset driver instead. Modeset seems to detect my monitor fine (got the EDID) but then fails with bug 1813897. This is now a bit off-topic, but I suspect the above problem with nvidia-430 will have the same fix as this bug. -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg 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 1723827] Re: App indicator icon size is too small
See my report https://bugs.launchpad.net/ubuntu/+source/gnome-shell- extension-appindicator/+bug/1832793 Indeed PANEL_ICON_SIZE is the wrong way to compute the icon size. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1723827 Title: App indicator icon size is too small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1723827/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832793] Re: Size is not right with hidpi (both 2x and 1x with font scaling)
I've reported this in github also: https://github.com/ubuntu/gnome- shell-extension-appindicator/issues/181. I'm not sure which is the better place since upstream = distro here. ** Bug watch added: github.com/ubuntu/gnome-shell-extension-appindicator/issues #181 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/181 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1832793 Title: Size is not right with hidpi (both 2x and 1x with font scaling) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1832793/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832793] [NEW] Size is not right with hidpi (both 2x and 1x with font scaling)
Public bug reported: I've tried this in two different hidpi monitors with different scaling configurations: 1) A 1920x1080 screen with scale factor 1x and font scale factor 1.25. 2) A 3000x2000 screen with scale factor 2x. In the first one, icons are too small, I have to change: this._iconBox = new AppIndicator.IconActor(indicator, Panel.PANEL_ICON_SIZE + 6); to this._iconBox = new AppIndicator.IconActor(indicator, Panel.PANEL_ICON_SIZE + 12); OTOH, icons are a little too big in the second setting and I have to do: this._iconBox = new AppIndicator.IconActor(indicator, Panel.PANEL_ICON_SIZE + 2); Icons directly managed by gnome shell are not sized according to PANEL_ICON_SIZE, see: https://gitlab.gnome.org/GNOME/gnome- shell/blob/master/js/ui/panelMenu.js Short of a smarter way of computing icons size, you could provide a setting to adjust it so that the user could fine tune it if necessary without hacking the code. ** Affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Size is not right with hidpi (both 2x and fractional scaling) + Size is not right with hidpi (both 2x and 1x with font scaling) ** Description changed: I've tried this in two different hidpi monitors with different scaling configurations: 1) A 1920x1080 screen with scale factor 1x and font scale factor 1.25. - + 2) A 3000x2000 screen with scale factor 2x. - In the first one, icons are too small, I have to change: -this._iconBox = new AppIndicator.IconActor(indicator, + this._iconBox = new AppIndicator.IconActor(indicator, Panel.PANEL_ICON_SIZE + 6); to -this._iconBox = new AppIndicator.IconActor(indicator, + this._iconBox = new AppIndicator.IconActor(indicator, Panel.PANEL_ICON_SIZE + 12); OTOH, icons are a little too big in the second setting and I have to do: -this._iconBox = new AppIndicator.IconActor(indicator, + this._iconBox = new AppIndicator.IconActor(indicator, Panel.PANEL_ICON_SIZE + 2); + Icons directly managed by gnome shell are not sized according to + PANEL_ICON_SIZE, see: - Icons directly managed by gnome shell are not sized according to PANEL_ICON_SIZE, see: - -https://gitlab.gnome.org/GNOME/gnome- + https://gitlab.gnome.org/GNOME/gnome- shell/blob/master/js/ui/panelMenu.js Short of a smarter way of computing icons size, you could provide a - setting to adjust it. + setting to adjust it so that the user could fine tune it if necessary + without hacking the code. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1832793 Title: Size is not right with hidpi (both 2x and 1x with font scaling) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1832793/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1831161] Re: App-switcher icons too small with hidpi monitor and 1.25 scaling
I've changed `baseIconSizes` from the looking glass and I get bigger icons. This doesn't seem to be hard to fix really. Maybe the size restriction should be checked *before* scaling up 2x. Maybe bigger icons should be allowed. -- 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/1831161 Title: App-switcher icons too small with hidpi monitor and 1.25 scaling To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1831161/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1832792] [NEW] App-switcher icons too small with hidpi (3000x2000) monitor
Public bug reported: I've reported this upstream (https://gitlab.gnome.org/GNOME/gnome- shell/issues/1370), but given that this is an important part of the Ubuntu desktop and that you're providing some patches for improving the X11 experience with hidpi monitors, I'm notifying about the issue here too. It could be related to my previous similar report for fractional scaling resolutions: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1831161. But I'm not sure. Besides, fractional scaling is an experimental feature while 2x is not. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Summary changed: - App-switcher icons too small with hidpi monitor + App-switcher icons too small (48x48) with hidpi monitor ** Summary changed: - App-switcher icons too small (48x48) with hidpi monitor + App-switcher icons too small (48x48) with hidpi (3000x2000) monitor ** Summary changed: - App-switcher icons too small (48x48) with hidpi (3000x2000) monitor + App-switcher icons too small with hidpi (3000x2000) monitor -- 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/1832792 Title: App-switcher icons too small with hidpi (3000x2000) monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1781029] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-menus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1781029 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1781029/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782535] Re: cifs - poor upload speed with nautilus compared to rsync
Issue may get closed. Solved with upgrading to Ubuntu 19.04. Nevertheless thanks for your help. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1782535 Title: cifs - poor upload speed with nautilus compared to rsync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1782535/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1831356] Re: Settings crashes when I click "Devices"(Enheter in norwegian) tap
** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Confirmed -- 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/1831356 Title: Settings crashes when I click "Devices"(Enheter in norwegian) tap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1831356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772811] Re: [SRU] different behaviors for switch display mode between xenial and bionic
** Changed in: oem-priority Status: Triaged => Fix Released -- 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/1772811 Title: [SRU] different behaviors for switch display mode between xenial and bionic To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1772811/+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 results in no monitors detected by Xorg
User generix reports that when gdm3 is compiled without wayland support, this bug is not seen. -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg 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 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
I posted here: https://devtalk.nvidia.com/default/topic/1055528/linux/nvidia-driver-in- modeset-1-requires-root-permissions-daniel-van-vugt-canonical-concludes- it-is-an-nvidia-bug/?offset=3#5351122 -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg 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 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)
** Changed in: gnome-shell Status: Unknown => New -- 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/1705369 Title: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1705369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798790] Re: Ubuntu login screen sometimes doesn't appear on a single GPU Nvidia system (and setting WaylandEnable=false fixes it)
Also, just a reminder: If anyone is using a multi-GPU desktop machine then please see bug 1705369 instead. ** Summary changed: - Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it) + Ubuntu login screen sometimes doesn't appear on a single GPU Nvidia system (and setting WaylandEnable=false fixes it) -- 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/1798790 Title: Ubuntu login screen sometimes doesn't appear on a single GPU Nvidia system (and setting WaylandEnable=false fixes it) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1798790/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an Intel GPU)
Two years later... I am reviewing this bug again today. I can confirm it's still in Ubuntu 19.10. And I can confirm that comment #19 was right. See comment #19. ** Summary changed: - Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an Intel GPU) + Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU) ** Description changed: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) - WORKAROUNDS: + WORKAROUNDS (you only need one): - * Disable integrated graphics/GPU in your BIOS; or + * Uncomment #WaylandEnable=false in /etc/gdm3/custom.conf + + * Disable integrated graphics/GPU in your BIOS * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then - run: sudo update-initramfs - and reboot. + run: sudo update-initramfs + and reboot. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux ** Description changed: - Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a - desktop with an Intel GPU) + Ubuntu boots to blank screen when using Nvidia drivers (on a desktop + with an unused Intel GPU). WORKAROUNDS (you only need one): * Uncomment #WaylandEnable=false in /etc/gdm3/custom.conf * Disable integrated graphics/GPU in your BIOS * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then run: sudo update-initramfs and reboot. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux ** Changed in: gnome-shell (Ubuntu) Importance: High => Undecided ** Changed in: nvidia-graphics-drivers-375 (Ubuntu) Importance: High => Undecided ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Triaged ** Bug watch added: gitlab.gnome.org/GNOME/gdm/issues #492 https://gitlab.gnome.org/GNOME/gdm/issues/492 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gdm/issues/492 Importance: Unknown Status: Unknown -- 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/1705369 Title: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1705369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an Intel GPU)
-black +blank Because on Ubuntu 19.10 it's purple. Still the same bug though. ** Summary changed: - Ubuntu boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) + Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an Intel GPU) ** Tags removed: aardvark gnome-17.10 ** Tags added: eoan ** Tags removed: artful -- 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/1705369 Title: Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an Intel GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an Intel GPU)
Comment #116 appears to be linking to the wrong bug. That link is for nvidia-drm.modeset=1 and this bug is specifically about when you don't have that set, like the default. -- 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/1705369 Title: Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an Intel GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+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 results in no monitors detected by Xorg
** No longer affects: gdm3 (Debian) ** Tags added: eoan -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg 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 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
I will post your findings to the nvidia developers forum. -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg 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 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
Not yet. I am just untangling more Nvidia bugs today. Also, I forgot to mention that you CAN run Xorg+Nvidia and see your monitors as non-root. But only after you have started and stopped Xorg as root beforehand. Something gets remembered, maybe in $HOME somewhere? -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg 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 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
Also, it sounds like the root cause here is the same as bug 1769857. -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg 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 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg
Hi Daniel, thanks for not forgetting about this, unlike everyone else :) Have you communicated this observation to Nvidia at all? -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg 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 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)
Sounds like the root cause here is the same as bug 1716857. ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Invalid -- 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/1769857 Title: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1799994] Re: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1 even though WaylandEnable=false is set
*** This bug is a duplicate of bug 1716857 *** https://bugs.launchpad.net/bugs/1716857 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1716857, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1716857 nvidia-drm.modeset=1 results in no monitors detected by Xorg -- 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/174 Title: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1 even though WaylandEnable=false is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/174/+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 results in no monitors detected by Xorg
For a full list of reasons to not use nvidia-drm.modeset=1 right now, please see: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nvidia-drm.modeset -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg 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 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
In a more pure development environment, I can confirm this bug without needing hybrid GPUs, or gdm3. Just the Nvidia driver and Xorg results in no outputs/monitors detected: $ xrandr Screen 0: minimum 8 x 8, current 640 x 480, maximum 16384 x 16384 To work around the problem I need to run Xorg as root. Then I get: $ xrandr Screen 0: minimum 8 x 8, current 1920 x 1200, maximum 16384 x 16384 DVI-I-0 disconnected primary (normal left inverted right x axis y axis) DVI-I-1 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x 324mm 1920x1200 59.95*+ 59.88 1920x1080 60.0059.9450.0023.98 1600x1200 60.00 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 So perhaps gdm3 is sometimes missing whatever /dev/* privileges it needs to start Xorg on Nvidia properly. And perhaps lightdm just always does it right. Although a solution here in the medium term might lay in gdm3, I would more like to see the Nvidia driver fix this bug. Because I can reproduce it without any *dm. Just the kernel + Nvidia driver + Xorg. ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Opinion ** Changed in: mutter (Ubuntu) Status: Confirmed => Invalid ** Also affects: nvidia-graphics-drivers-418 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-418 (Ubuntu) Status: New => Confirmed ** Also affects: nvidia-graphics-drivers-375 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-375 (Ubuntu) Status: New => Confirmed ** Summary changed: - gdm3, hybrid nvidia with modeset=1, no external monitors detected + nvidia-drm.modeset=1 results in no monitors detected by Xorg ** Changed in: gdm3 (Ubuntu) Status: Opinion => Invalid -- 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/1716857 Title: nvidia-drm.modeset=1 results in no monitors detected by Xorg 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 1832693] [NEW] System auto suspend again during resuming
Public bug reported: ## Issue In certain case, system wake-up from suspend will suspend again automatically. The issue comes from a target machine turning auto-suspend on and suspends after the idle time-out. Manually suspend, e.g., click suspend icon or execute "systemctl suspend" won't reproduce the issue. When waking up from this situation, the monitor keeps blank, although the monitor has exited low power mode, then suspend again immediately. Can successfully waking up the system after that, but once the system reaches the idle time again, the issue appears repeatedly. From the system log, a sleep request is following the wake request. Hardware configuration also counts. It is hard to reproduce the issue with the system installed on SSD or with a lower resolution monitor; graphics card may also affect. It's likely to be a timing issue. ## Environment Machine: Dell Precision 7920 Tower. Monitor: Philips 288P6L DistroRelease: Ubuntu 18.04.2 Graphics card: Nvidia Quadro P2200 Nvidia driver version: 418.74 CPU: Intel(R) Xeon(R) Platinum 8276 CPU @ 2.20GHz ## Steps to reproduce: Turn on automatic suspend in Settings->Power Wait for the system to suspend Wake up the system via pressing power button or keyboard. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- 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/1832693 Title: System auto suspend again during resuming To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1832693/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected
** Tags added: nvidia-drm.modeset -- 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/1716857 Title: gdm3, hybrid nvidia with modeset=1, no external monitors detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813173] Re: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta()
Yes, that does seem to be the problem, most likely. The only calls to 'get_child_meta' in gnome-shell are in environment.js, which seems to be called from the GPaste extension per the above comment. I recommend uninstalling the GPaste extension. -- 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/1813173 Title: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813173/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813173] Re: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta()
It appears this crash is not very common, suggesting it might be related to some extension(s). You seem to have installed: 'weatherinthecl...@jasonlg1979.github.io' 'gpa...@gnome-shell-extensions.gnome.org' 'sound-output-device-choo...@kgshank.net' so please try uninstalling those completely, and tell us if the crash still occurs. -- 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/1813173 Title: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813173/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1813173] Re: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta()
The attached file JournalErrors.txt suggests the GPaste extension might be the most suspicious extension: яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: == Stack trace for context 0x55db415214d0 == яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #0 0x7fff6837e650 I resource:///org/gnome/shell/ui/environment.js:41 (0x7fa438386d58 @ 20) яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #1 0x7fff6837e740 b resource:///org/gnome/shell/ui/popupMenu.js:658 (0x7fa438123d58 @ 202) яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #2 0x7fff6837e7b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fa4383b5de0 @ 71) яну 24 16:34:05 hostname gnome-shell[30607]: clutter_container_add_actor: assertion 'CLUTTER_IS_CONTAINER (container)' failed яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #3 0x55db418d30d0 i /usr/share/gnome-shell/extensions/gpa...@gnome-shell-extensions.gnome.org/indicator.js:323 (0x7fa4180bf5e8 @ 48) яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #4 0x7fff6837f3a0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fa4383b5de0 @ 71) яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #5 0x55db418d3030 i /usr/share/gnome-shell/extensions/gpa...@gnome-shell-extensions.gnome.org/indicator.js:90 (0x7fa4180b75e8 @ 274) яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: == Stack trace for context 0x55db415214d0 == яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #0 0x7fff6837f390 I resource:///org/gnome/shell/ui/environment.js:41 (0x7fa438386d58 @ 20) яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #1 0x55db418d3030 i /usr/share/gnome-shell/extensions/gpa...@gnome-shell-extensions.gnome.org/indicator.js:92 (0x7fa4180b75e8 @ 332) яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: == Stack trace for context 0x55db415214d0 == яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #0 0x7fff6837f390 I resource:///org/gnome/shell/ui/environment.js:32 (0x7fa438386cd0 @ 26) яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #1 0x7fff6837f390 I resource:///org/gnome/shell/ui/environment.js:43 (0x7fa438386d58 @ 50) яну 24 16:34:05 hostname org.gnome.Shell.desktop[30607]: #2 0x55db418d3030 i /usr/share/gnome-shell/extensions/gpa...@gnome-shell-extensions.gnome.org/indicator.js:92 (0x7fa4180b75e8 @ 332) яну 24 16:34:05 hostname gnome-shell[30607]: Object St.BoxLayout (0x55db492b5a10), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs яну 24 16:34:05 hostname gnome-shell[30607]: clutter_container_get_children: assertion 'CLUTTER_IS_CONTAINER (container)' failed яну 24 16:34:05 hostname gnome-shell[30607]: Object St.BoxLayout (0x55db492b5a10), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs яну 24 16:34:05 hostname gnome-shell[30607]: clutter_container_add_actor: assertion 'CLUTTER_IS_CONTAINER (container)' failed яну 24 16:34:05 hostname gnome-shell[30607]: Object St.BoxLayout (0x55db492b5a10), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs яну 24 16:34:05 hostname gnome-shell[30607]: clutter_container_get_children: assertion 'CLUTTER_IS_CONTAINER (container)' failed яну 24 16:34:05 hostname gnome-shell[30607]: Object St.BoxLayout (0x55db492b5a10), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs яну 24 16:34:05 hostname gnome-shell[30607]: clutter_container_add_actor: assertion 'CLUTTER_IS_CONTAINER (container)' failed яну 24 16:34:05 hostname gnome-shell[30607]: Object St.BoxLayout (0x55db440bd770), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs яну 24 16:34:05 hostname gnome-shell[30607]: clutter_container_add_actor: assertion 'CLUTTER_IS_CONTAINER (container)' failed яну 24 16:34:05 hostname gnome-shell[30607]: Object St.BoxLayout (0x55db440bd770), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs яну 24 16:34:46 hostname gnome-session-binary[30496]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ub
[Bug 1813173] Re: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta()
Hi, This crash is still present in the latest gnome-shell version 3.28.4-0ubuntu18.04.1 -- 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/1813173 Title: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813173/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
