[Bug 1821870] Re: gnome-shell segfault libmutter-clutter-2

2019-06-13 Thread Launchpad Bug Tracker
[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.

[Bug 1824657] Re: GNOME shell crash

2019-06-13 Thread Launchpad Bug Tracker
[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.

[Bug 1824578] Re: Screen lock doesn't lock Launcher (left-sidebar) and Status Menus (Indicators)

2019-06-13 Thread Launchpad Bug Tracker
[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.

[Bug 1832792] Re: App-switcher icons too small with hidpi (3000x2000) monitor

2019-06-13 Thread Bug Watch Updater
** 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)

[Bug 1831161] Re: App-switcher icons too small with hidpi monitor and 1.25 scaling

2019-06-13 Thread Daniel van Vugt
** 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

[Bug 1832792] Re: App-switcher icons too small with hidpi (3000x2000) monitor

2019-06-13 Thread Daniel van Vugt
** 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

[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Daniel van Vugt
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)

[Bug 1723827] Re: App indicator icon size is too small

2019-06-13 Thread Carlos Pita
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

[Bug 1832793] Re: Size is not right with hidpi (both 2x and 1x with font scaling)

2019-06-13 Thread Carlos Pita
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

[Bug 1832793] [NEW] Size is not right with hidpi (both 2x and 1x with font scaling)

2019-06-13 Thread Carlos Pita
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:    

[Bug 1831161] Re: App-switcher icons too small with hidpi monitor and 1.25 scaling

2019-06-13 Thread Carlos Pita
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

[Bug 1832792] [NEW] App-switcher icons too small with hidpi (3000x2000) monitor

2019-06-13 Thread Carlos Pita
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

[Bug 1781029] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

2019-06-13 Thread Launchpad Bug Tracker
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.

[Bug 1782535] Re: cifs - poor upload speed with nautilus compared to rsync

2019-06-13 Thread Florian Schwarz
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

[Bug 1831356] Re: Settings crashes when I click "Devices"(Enheter in norwegian) tap

2019-06-13 Thread Gunnar Hjalmarsson
** 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

[Bug 1772811] Re: [SRU] different behaviors for switch display mode between xenial and bionic

2019-06-13 Thread Yuan-Chen Cheng
** 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

[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Tim Richardson
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

[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Tim Richardson
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

[Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia (on a desktop with an unused Intel GPU)

2019-06-13 Thread Bug Watch Updater
** 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

[Bug 1798790] Re: Ubuntu login screen sometimes doesn't appear on a single GPU Nvidia system (and setting WaylandEnable=false fixes it)

2019-06-13 Thread Daniel van Vugt
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

[Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an Intel GPU)

2019-06-13 Thread Daniel van Vugt
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

[Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an Intel GPU)

2019-06-13 Thread Daniel van Vugt
-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

[Bug 1705369] Re: Ubuntu boots to blank screen when using Nvidia drivers (on a desktop with an Intel GPU)

2019-06-13 Thread Daniel van Vugt
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

[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Daniel van Vugt
** 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

[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Tim Richardson
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

[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Daniel van Vugt
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

[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Daniel van Vugt
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

[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Tim Richardson
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.

[Bug 1769857] Re: Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used (Optimus)

2019-06-13 Thread Daniel van Vugt
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

[Bug 1799994] Re: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1 even though WaylandEnable=false is set

2019-06-13 Thread Daniel van Vugt
*** 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

[Bug 1716857] Re: nvidia-drm.modeset=1 results in no monitors detected by Xorg

2019-06-13 Thread Daniel van Vugt
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.

[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

2019-06-13 Thread Daniel van Vugt
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

[Bug 1832693] [NEW] System auto suspend again during resuming

2019-06-13 Thread cktenn
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

[Bug 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

2019-06-13 Thread Daniel van Vugt
** 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

[Bug 1813173] Re: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta()

2019-06-13 Thread Daniel van Vugt
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

[Bug 1813173] Re: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta()

2019-06-13 Thread Daniel van Vugt
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,

[Bug 1813173] Re: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta()

2019-06-13 Thread Daniel van Vugt
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

[Bug 1813173] Re: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta()

2019-06-13 Thread Kostadin Stoilov
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