[Bug 1834293] Re: screen

2019-06-26 Thread Daniel van Vugt
Are you saying the display gets screenshotted without you asking?

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

-- 
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/1834293

Title:
  screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1834293/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1834249] Re: Google Chrome pausing live streaming video briefly for a second or two every 5-10 seconds

2019-06-25 Thread Daniel van Vugt
Sorry, Google Chrome is not part of Ubuntu so we can't handle bug
reports for it here. However, if you install 'chromium-browser' and find
the same bug in that then we can handle it here.

Do you find the same problems with Firefox?

** Package changed: totem (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1834249

Title:
  Google Chrome pausing live streaming video briefly for a second or two
  every 5-10 seconds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1834249/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1834110] Re: Broken lock-screen wallpaper, stutter after resuming from hibernation

2019-06-25 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1809407 ***
https://bugs.launchpad.net/bugs/1809407

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 1809407, 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 1809407
   [nvidia] Corrupted wallpaper after resuming from suspend

-- 
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/1834110

Title:
  Broken lock-screen wallpaper, stutter after resuming from hibernation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1834110/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1833508] Re: the system woke up and has not proper desktop image

2019-06-25 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1809407 ***
https://bugs.launchpad.net/bugs/1809407

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 1809407, 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.


** Tags added: nvidia

** This bug has been marked a duplicate of bug 1809407
   [nvidia] Corrupted wallpaper after resuming from suspend

-- 
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/1833508

Title:
  the system woke up and has not proper desktop image

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833508/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend

2019-06-25 Thread Daniel van Vugt
The Ubuntu release process requires that we always get the fix into the
_next_ release first. That means 19.10. After that we are free to
propose it for 19.04 and earlier. I have nominated 19.10, 19.04 and
18.04 at the top of 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/1809407

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1809407/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1834058] Re: Keyboard layout indicator vanishes after Suspend or Screenlock

2019-06-24 Thread Daniel van Vugt
Just in case it is related, please try UNINSTALLING these extensions and
then reboot:

'gnom...@panacier.gmail.com'
'activities-config@nls1729'
'dash-to-d...@micxgx.gmail.com'
'appindicatorsupp...@rgcjonas.gmail.com'
'apps-m...@gnome-shell-extensions.gcampax.github.com'
'background-l...@marketing.fedoraproject.org'
'caffe...@patapon.info'
'lockk...@vaina.lt'

We find a lot of bugs are caused by extensions.

** Tags added: resume suspend-resume

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

-- 
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/1834058

Title:
  Keyboard layout indicator vanishes after Suspend or Screenlock

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1834058/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

2019-06-24 Thread Daniel van Vugt
---> bug 1834058 now

-- 
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/1812266

Title:
  Keyboard layout indicator does not indicate current layout (18.04
  Bionic beaver)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1834110] Re: Broken lock-screen wallpaper, stutter after resuming from hibernation

2019-06-24 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1834110

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Changed in: mutter (Ubuntu)
   Status: New => Incomplete

-- 
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/1834110

Title:
  Broken lock-screen wallpaper, stutter after resuming from hibernation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1834110/+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)

2019-06-24 Thread Daniel van Vugt
Upstream is against changing mutter for this, so "Won't Fix" to mutter.
But the fix for gdm3 has landed and that's enough to resolve the bug.

** Changed in: gdm3 (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: mutter (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 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 1833832] Re: NVIDIA kernel module fails with KMS on optimus hardware

2019-06-23 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1716857 ***
https://bugs.launchpad.net/bugs/1716857

The errors in the attached journal log show this is the same as what I
recently described in:

https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-418/+bug/1716857/comments/36

** 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/1833832

Title:
  NVIDIA kernel module fails with KMS on optimus hardware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1833832/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 561370] Re: gnome-terminal transparency no longer works reliably (usually opaque, but sometimes shows transparency)

2019-06-23 Thread Daniel van Vugt
** Tags added: disco

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/561370

Title:
  gnome-terminal transparency no longer works reliably (usually opaque,
  but sometimes shows transparency)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/561370/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1833508] Re: the system woke up and has not proper desktop image

2019-06-23 Thread Daniel van Vugt
If you are using Nvidia then this is bug 1809407.

Also...

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1833508

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

-- 
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/1833508

Title:
  the system woke up and has not proper desktop image

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833508/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832869] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call()

2019-06-23 Thread Daniel van Vugt
Yes that theming.js around like 479 (on bionic) looks like a candidate
for calling the offending `meta_workspace_list_windows`:

_dockIsNear: function() {
if (this._dockActor.has_style_pseudo_class('overview'))
return false;
/* Get all the windows in the active workspace that are in the primary 
monitor and visible */
let activeWorkspace = global.screen.get_active_workspace();
let dash = this._dash;
let windows = 
activeWorkspace.list_windows().filter(function(metaWindow) {
return metaWindow.get_monitor() === dash._monitorIndex &&
   metaWindow.showing_on_its_workspace() &&
   metaWindow.get_window_type() != Meta.WindowType.DESKTOP;
});

-- 
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/1832869

Title:
  gnome-shell crashed with SIGSEGV in g_hash_table_iter_next →
  meta_display_list_windows → meta_workspace_list_windows →
  ffi_call_SYSV → ffi_call()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832869/+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

2019-06-23 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1831161 ***
https://bugs.launchpad.net/bugs/1831161

** This bug has been marked a duplicate of bug 1831161
   App-switcher icons too small with hidpi monitor and 1.25 scaling

-- 
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 1832436] Re: login page first appears sideways for Lenovo miix 510 ubuntu 18.04 and 18.10

2019-06-23 Thread Daniel van Vugt
** Package changed: gdm3 (Ubuntu) => linux (Ubuntu)

** No longer affects: ubuntu

-- 
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/1832436

Title:
  login page first appears sideways  for Lenovo miix 510 ubuntu 18.04
  and 18.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832436/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1822515] Re: Touchscreen input doesn't rotate with the screen

2019-06-23 Thread Daniel van Vugt
It's true that commit f9d6627fe03f68a132501a488f73e08080018115 is
released in mutter version 3.32.2 already. Which is also fix released in
eoan already.

** Changed in: mutter (Ubuntu)
   Status: Fix Committed => Fix Released

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/issues/581
   Importance: Unknown
   Status: Unknown

-- 
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/1822515

Title:
  Touchscreen input doesn't rotate with the screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1822515/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1833558] Re: gnome-shell crashed with SIGSEGV in meta_monitor_manager_get_monitor_for_connector() from

2019-06-21 Thread Daniel van Vugt
** Tags added: cosmic disco

-- 
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/1833558

Title:
  gnome-shell crashed with SIGSEGV in
  meta_monitor_manager_get_monitor_for_connector() from 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833558/+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

2019-06-20 Thread Daniel van Vugt
In isolation I don't think it's correct to say that Wayland sessions
have "no external monitors". Wayland sessions do work with external
monitors on the Nvidia driver if you have nvidia-drm.modeset=1. I've
confirmed this on a desktop at least.

It sounds like you're describing some other laptop-specific or Optimus-
specific bug. So I think to avoid confusion that should have its own
separate bug report.

-- 
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 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 1833558] Re: gnome-shell crashed with SIGSEGV in meta_monitor_manager_get_monitor_for_connector() from

2019-06-20 Thread Daniel van Vugt
It appears there's only one caller of this function in gnome-shell:

js/ui/osdMonitorLabeler.js:let monitor =
this._monitorManager.get_monitor_for_connector(connector);


** Also affects: mutter (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: mutter (Ubuntu)
   Status: New => Confirmed

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Medium

-- 
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/1833558

Title:
  gnome-shell crashed with SIGSEGV in
  meta_monitor_manager_get_monitor_for_connector() from 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833558/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1833558] Re: gnome-shell crashed with SIGSEGV in meta_monitor_manager_get_monitor_for_connector()

2019-06-20 Thread Daniel van Vugt
Tracking in:
https://errors.ubuntu.com/problem/6651d911f833729ccc39cf01ed5e393b95cb0c3f

** Description changed:

+ https://errors.ubuntu.com/problem/6651d911f833729ccc39cf01ed5e393b95cb0c3f
+ 
  gnome shell crashes when I go to Settings -> Devices -> Displays
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 19 11:01:41 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-04-29 (1146 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f49b8116bf0 
:mov0x18(%rax),%eax
   PC (0x7f49b8116bf0) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_monitor_manager_get_monitor_for_connector () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in 
meta_monitor_manager_get_monitor_for_connector()
  UpgradeStatus: Upgraded to bionic on 2018-08-04 (319 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin plugdev 
sambashare sudo

** Information type changed from Private to Public

** Summary changed:

- gnome-shell crashed with SIGSEGV in 
meta_monitor_manager_get_monitor_for_connector()
+ gnome-shell crashed with SIGSEGV in 
meta_monitor_manager_get_monitor_for_connector() from 

-- 
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/1833558

Title:
  gnome-shell crashed with SIGSEGV in
  meta_monitor_manager_get_monitor_for_connector() from 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833558/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1833642] Re: /usr/bin/gnome-shell:11:meta_monitor_manager_get_monitor_for_connector:ffi_call_unix64:ffi_call:gjs_invoke_c_function:function_call

2019-06-20 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1833558 ***
https://bugs.launchpad.net/bugs/1833558

** This bug has been marked a duplicate of private bug 1833558

-- 
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/1833642

Title:
  /usr/bin/gnome-
  
shell:11:meta_monitor_manager_get_monitor_for_connector:ffi_call_unix64:ffi_call:gjs_invoke_c_function:function_call

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833642/+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

2019-06-20 Thread Daniel van Vugt
gnome-shell!587 only says it fixes gnome-shell#1325. If you think it
also fixes gnome-shell#1370 then you should probably add a comment here:

https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/587

-- 
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

2019-06-20 Thread Daniel van Vugt
Actually, maybe those other DMs don't run as root. My memory is failing.
So again maybe we do want a similar workaround in gdm3. But that doesn't
seem to be the root cause of the bug.

** Changed in: gdm3 (Ubuntu)
   Status: Invalid => Opinion

** No longer affects: mutter (Ubuntu)

-- 
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

2019-06-20 Thread Daniel van Vugt
> If you need modeset=1 for wayland, then why is there any effort to support
nvidia and wayland under gnome, since it won't work (or are only optimus
systems affected by this?)

I don't understand the question, sorry. The statement "it won't work" is
wrong. Wayland does work. This bug is about Xorg, not Wayland.

> So it looks like a gdm3 bug.

Yes I understand that's how it looks, but we have established the root
cause of this bug is in the Nvidia driver. Maybe we will be able to work
around it with some gdm3 change, but that's not where the root cause of
the problem is.

Other display managers are managing to work around the Nvidia driver bug
here because they run as root. gdm3 does not run as root because it is
trying to be more secure and avoid running as root. Calling this a gdm3
bug is probably wrong. I can reproduce the bug without gdm3.

-- 
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

2019-06-20 Thread Daniel van Vugt
Compiling gdm3 without wayland isn't a fix. It's a workaround, and kind
of pointless. It's pointless because the most common reason for using
nvidia-drm.modeset=1 is to get Wayland support. I know there are other
reasons for wanting nvidia-drm.modeset=1 such as avoiding tearing in
PRIME setups. But mostly if people use modeset=1 it is to get Wayland
support.

If we can't get a fix from Nvidia then some kind of workaround that runs
Xorg as root (like comment #26) is probably the next best option.

-- 
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 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-06-20 Thread Daniel van Vugt
Workaround for mutter proposed here:

https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/369083

-- 
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/1832138

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-06-20 Thread Daniel van Vugt
And the problem is indeed the kernel advertising
DRM_CAP_TIMESTAMP_MONOTONIC but instead of using CLOCK_MONOTONIC it is
really using CLOCK_REALTIME. This confirms kernel commit 37efe80ce85f is
the fix, but it may well have some prerequisite commits we haven't fully
worked out...

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f

I'll see if I can hack around it, but the simplicity of the mistake in
the vmwgfx kernel code makes me think we should be preferring a kernel
fix still.

-- 
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/1832138

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15

2019-06-20 Thread Daniel van Vugt
I am now able to reproduce and debug the problem. Indeed it is what I
said in comment #31.

The vmwgfx driver in this old kernel is telling lies. It says the next
screen refresh is in 49 years from now. It should be within 16.6
milliseconds.


** Summary changed:

- Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or 
using WaylandEnable=false) fixes it
+ Login screen never appears on vmwgfx using bionic kernel 4.15

-- 
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/1832138

Title:
  Login screen never appears on vmwgfx using bionic kernel 4.15

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-20 Thread Daniel van Vugt
It seems I stumbled on a workaround. Just install the kernel that comes
in the 18.04.2 ISO:

https://launchpad.net/ubuntu/+source/linux-hwe

** Also affects: linux-hwe (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-hwe (Ubuntu Bionic)
   Status: New => Fix Released

** Changed in: linux-hwe (Ubuntu Eoan)
   Status: New => 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/1832138

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1833500] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv("Function allocate terminated with uncatchable exception")

2019-06-20 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1736664 ***
https://bugs.launchpad.net/bugs/1736664

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 1736664, 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.


** Summary changed:

- gnome-shell crashed with signal 5
+ gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler() from g_logv("Function 
allocate terminated with uncatchable exception")

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1736664
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler() from g_logv("Function 
allocate terminated with uncatchable exception") from g_log()

-- 
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/1833500

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler() from
  g_logv("Function allocate terminated with uncatchable exception")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833500/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-20 Thread Daniel van Vugt
Using VirtualBox 6 and VMSVGA as recommended by Eric I still can't
reproduce the bug. But I think I can see why now: Ubuntu 18.04.2 comes
with kernel 4.18

Let me try 18.04.1...

-- 
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/1832138

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1736664] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler() from g_logv("Function allocate terminated with uncatchable exception") from

2019-06-20 Thread Daniel van Vugt
** Summary changed:

- gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler() from g_logv("Function 
AsyncReadyCallback terminated with uncatchable exception") from g_log()
+ gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler() from g_logv("Function 
allocate terminated with uncatchable exception") from g_log()

-- 
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/1736664

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler() from
  g_logv("Function allocate terminated with uncatchable exception") from
  g_log()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736664/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1652282] Re: Xwayland not using XAUTHORITY, prevents root applications from connecting

2019-06-19 Thread Daniel van Vugt
Sounds like a fix is on the way:

https://gitlab.gnome.org/GNOME/mutter/merge_requests/626

** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #643
   https://gitlab.gnome.org/GNOME/mutter/issues/643

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/issues/643
   Importance: Unknown
   Status: Unknown

** Tags removed: artful yakkety

-- 
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/1652282

Title:
  Xwayland not using XAUTHORITY, prevents root applications from
  connecting

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1652282/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-19 Thread Daniel van Vugt
It also sounds like VirtualBox might allow me to reproduce the bug...

** Changed in: mutter (Ubuntu Bionic)
   Status: Incomplete => In Progress

-- 
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/1832138

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-19 Thread Daniel van Vugt
** Changed in: mutter (Ubuntu Bionic)
   Status: Won't Fix => Incomplete

-- 
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/1832138

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-19 Thread Daniel van Vugt
** Changed in: mutter (Ubuntu Bionic)
   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/1832138

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-19 Thread Daniel van Vugt
> Do you know what change could have introduced this vmwgfx/wayland
interaction problem inside mutter in the first place ?

Technically it was a whole point release. The trigger could be any
change that went into mutter 3.28.4 as well as any Ubuntu patch. As
mentioned in comment #31, my suspicion is this specific change:
https://gitlab.gnome.org/GNOME/mutter/commit/e9e4b2b72

> Just to look at our option (since a kernel fix might be not end up
being trivial) does a revert of the change could be a possibility here ?

If the issue turns out to be commit e9e4b2b72 above then no. Because too
many people benefit vs the possible number of people affected by this
bug. But we also aren't completely sure that's the relevant mutter
commit.

If only I could reproduce this bug I could probably write a workaround
(or fix) for it in mutter.

-- 
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/1832138

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832988] Re: Intel 8260 Bluetooth not working

2019-06-19 Thread Daniel van Vugt
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: gnome-bluetooth (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Invalid

-- 
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/1832988

Title:
  Intel 8260 Bluetooth not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1832988/+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)

2019-06-19 Thread Daniel van Vugt
** Description changed:

  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.
+ 
+ * Add a line to /usr/lib/udev/rules.d/61-gdm.rules:
+   DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
  
  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

-- 
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 (on a desktop with an unused Intel GPU)

2019-06-19 Thread Daniel van Vugt
** Changed in: mutter (Ubuntu)
   Status: Won't Fix => 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/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 (on a desktop with an unused Intel GPU)

2019-06-19 Thread Daniel van Vugt
Oops. It appears upstream already fixed this bug. And we removed their
fix in Ubuntu (revert_nvidia_wayland_blacklist.patch in gdm3). If you
revert that revert then the bug is fixed.

** Changed in: gdm3 (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: gdm3 (Ubuntu)
   Status: Invalid => In Progress

** Changed in: gdm3 (Ubuntu)
   Importance: Undecided => High

** Changed in: mutter (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 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 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-18 Thread Daniel van Vugt
Thanks Pat.

That seems to confirm the 'regression-update' tag here. Although I
wouldn't be able to debug and fix the mutter change because I can't
reproduce the bug, using VMware. Mine just works :/

It sounds like good progress is being made in the kernel anyway. So I
think a fix there would be preferable. Otherwise I would just be hunting
for a way to cripple mutter to work around apparent VMware driver bugs.

** Changed in: mutter (Ubuntu Bionic)
   Status: Incomplete => Won't Fix

-- 
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/1832138

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-18 Thread Daniel van Vugt
Card archived: https://trello.com/c/gn0J5Qgb

-- 
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/1832138

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1833045] Re: Ubuntu on Wayland login option is missing on random boots in VMware

2019-06-18 Thread Daniel van Vugt
This bug _only_ affects bionic. But I am happy to say "Won't Fix".

** Also affects: mutter (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: mutter (Ubuntu Bionic)
   Status: New => Won't Fix

-- 
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/1833045

Title:
  Ubuntu on Wayland login option is missing on random boots in VMware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1833045/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1830422] Re: Shell boxpointer menus don't have scroll buttons when they exceed the screen height

2019-06-18 Thread Daniel van Vugt
That's a Launchpad bug. Nothing is fixed. The bug was rejected and
closed, which Launchpad misinterprets as "Fix Released":

https://gitlab.gnome.org/GNOME/gnome-shell/issues/1332

** No longer affects: gnome-shell

-- 
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/1830422

Title:
  Shell boxpointer menus don't have scroll buttons when they exceed the
  screen height

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830422/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1833098] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from g_file_get_parent() from _st_theme_resolve_url() from _st_theme_node_ensure_background() from st_theme_node_pain

2019-06-18 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1788429 ***
https://bugs.launchpad.net/bugs/1788429

Which is presently a duplicate of bug 1788429...

** This bug has been marked a duplicate of bug 1788429
   gnome-shell crashed with SIGSEGV in g_file_get_parent → 
_st_theme_resolve_url → _st_theme_node_ensure_background → 
st_theme_node_paint_equal → st_widget_recompute_style

-- 
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/1833098

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from
  g_file_get_parent() from _st_theme_resolve_url() from
  _st_theme_node_ensure_background() from st_theme_node_paint_equal()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833098/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1833098] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from g_file_get_parent() from _st_theme_resolve_url() from _st_theme_node_ensure_background() from st_theme_node_pain

2019-06-18 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1788429 ***
https://bugs.launchpad.net/bugs/1788429

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 1788428, 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.

-- 
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/1833098

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from
  g_file_get_parent() from _st_theme_resolve_url() from
  _st_theme_node_ensure_background() from st_theme_node_paint_equal()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833098/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832856] Re: Gnome-shell crashes frequently in gnome-shell/extensions/wsmat...@martin.zurowietz.de

2019-06-18 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1788429 ***
https://bugs.launchpad.net/bugs/1788429

** This bug is no longer a duplicate of bug 1833098
   gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from 
g_file_get_parent() from _st_theme_resolve_url() from 
_st_theme_node_ensure_background() from st_theme_node_paint_equal()
** This bug has been marked a duplicate of bug 1788429
   gnome-shell crashed with SIGSEGV in g_file_get_parent → 
_st_theme_resolve_url → _st_theme_node_ensure_background → 
st_theme_node_paint_equal → st_widget_recompute_style

-- 
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/1832856

Title:
  Gnome-shell crashes frequently in gnome-
  shell/extensions/wsmat...@martin.zurowietz.de

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832856/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1762235] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_init() from nm_ip_address_dup() from g_boxed_copy()

2019-06-18 Thread Daniel van Vugt
Tracking in:
https://errors.ubuntu.com/problem/f00ece10287bf9cfb758c3819e2e3f6575704d10

** Description changed:

- -
+ https://errors.ubuntu.com/problem/f00ece10287bf9cfb758c3819e2e3f6575704d10
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Apr  8 20:57:53 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-02-18 (49 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=cs_CZ.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=cs_CZ.UTF-8
+  SHELL=/bin/bash
  SegvAnalysis:
-  Segfault happened at: 0x7f8db9b994f4 :mov
0x44(%rsi),%eax
-  PC (0x7f8db9b994f4) ok
-  source "0x44(%rsi)" (0x3838342032313176) not located in a known VMA region 
(needed readable region)!
-  destination "%eax" ok
+  Segfault happened at: 0x7f8db9b994f4 :mov
0x44(%rsi),%eax
+  PC (0x7f8db9b994f4) ok
+  source "0x44(%rsi)" (0x3838342032313176) not located in a known VMA region 
(needed readable region)!
+  destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
-  g_hash_table_iter_init () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  () at /usr/lib/x86_64-linux-gnu/libnm.so.0
-  g_boxed_copy () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  gjs_boxed_from_c_struct () at /usr/lib/libgjs.so.0
-  gjs_value_from_g_argument () at /usr/lib/libgjs.so.0
+  g_hash_table_iter_init () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  () at /usr/lib/x86_64-linux-gnu/libnm.so.0
+  g_boxed_copy () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  gjs_boxed_from_c_struct () at /usr/lib/libgjs.so.0
+  gjs_value_from_g_argument () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_hash_table_iter_init()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

-- 
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/1762235

Title:
  gnome-shell crashed with SIGSEGV in g_hash_table_iter_init() from
  nm_ip_address_dup() from g_boxed_copy()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1762235/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1833324] Re: /usr/bin/gnome-shell:11:g_hash_table_iter_init:nm_ip_address_dup:g_boxed_copy:gjs_boxed_from_c_struct:gjs_value_from_g_argument

2019-06-18 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1762235 ***
https://bugs.launchpad.net/bugs/1762235

** This bug has been marked a duplicate of bug 1762235
   gnome-shell crashed with SIGSEGV in g_hash_table_iter_init() from 
nm_ip_address_dup() from g_boxed_copy()

-- 
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/1833324

Title:
  /usr/bin/gnome-
  
shell:11:g_hash_table_iter_init:nm_ip_address_dup:g_boxed_copy:gjs_boxed_from_c_struct:gjs_value_from_g_argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833324/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1833263] Re: /usr/bin/gnome-shell:11:g_str_hash:nm_ip_address_dup:g_boxed_copy:gjs_boxed_from_c_struct:gjs_value_from_g_argument

2019-06-18 Thread Daniel van Vugt
This doesn't seem to be exactly the same issue as bug 1762235 so they
should probably be separate for now.

** This bug is no longer a duplicate of bug 1762235
   gnome-shell crashed with SIGSEGV in g_hash_table_iter_init() from 
nm_ip_address_dup() from g_boxed_copy()

** Summary changed:

- 
/usr/bin/gnome-shell:11:g_str_hash:nm_ip_address_dup:g_boxed_copy:gjs_boxed_from_c_struct:gjs_value_from_g_argument
+ gnome-shell crashed with SIGSEGV in g_str_hash() from nm_ip_address_dup() 
from g_boxed_copy() from gjs_boxed_from_c_struct() from 
gjs_value_from_g_argument()

-- 
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/1833263

Title:
  gnome-shell crashed with SIGSEGV in g_str_hash() from
  nm_ip_address_dup() from g_boxed_copy() from gjs_boxed_from_c_struct()
  from gjs_value_from_g_argument()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833263/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1717453]

2019-06-18 Thread Daniel van Vugt
In progress: https://gitlab.gnome.org/GNOME/gnome-
shell/merge_requests/486

-- 
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/1717453

Title:
  Shell menus (panel, dock, window) font size does not match configured
  interface font size

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1717453/+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)

2019-06-18 Thread Daniel van Vugt
Fix proposed: https://gitlab.gnome.org/GNOME/mutter/merge_requests/625

** Changed in: mutter (Ubuntu)
   Status: Triaged => In Progress

** Changed in: gdm3 (Ubuntu)
   Status: Triaged => Invalid

** Changed in: gdm3 (Ubuntu)
   Importance: High => Undecided

** Changed in: gdm3 (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

-- 
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 1832943] Re: Ghost of an app window (like Firefox) is visible in the AO search background

2019-06-17 Thread Daniel van Vugt
** Summary changed:

- When Firefox is appeared and I open gno-menu, I will see shade of Firefox at 
background
+ Ghost of an app window (like Firefox) is visible in the AO search background

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

** Tags added: visual-quality

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-shell (Ubuntu)
   Status: New => Triaged

-- 
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/1832943

Title:
  Ghost of an app window (like Firefox) is visible in the AO search
  background

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832943/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1833098] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from g_file_get_parent() from _st_theme_resolve_url() from _st_theme_node_ensure_background() from st_theme_node_pain

2019-06-17 Thread Daniel van Vugt
** Summary changed:

- gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a()
+ gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from 
g_file_get_parent() from _st_theme_resolve_url() from 
_st_theme_node_ensure_background() from st_theme_node_paint_equal()

** Information type changed from Private to Public

-- 
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/1833098

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from
  g_file_get_parent() from _st_theme_resolve_url() from
  _st_theme_node_ensure_background() from st_theme_node_paint_equal()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833098/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1350410] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from atk_object_notify_state_change()

2019-06-17 Thread Daniel van Vugt
** Summary changed:

- gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a()
+ gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from 
atk_object_notify_state_change()

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Won't Fix

-- 
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/1350410

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from
  atk_object_notify_state_change()

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1350410/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832856] Re: Gnome-shell crashes frequently in gnome-shell/extensions/wsmat...@martin.zurowietz.de

2019-06-17 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1833098 ***
https://bugs.launchpad.net/bugs/1833098

Thanks. We can track this in bug 1833098 now.

** This bug has been marked a duplicate of private bug 1833098

-- 
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/1832856

Title:
  Gnome-shell crashes frequently in gnome-
  shell/extensions/wsmat...@martin.zurowietz.de

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832856/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1722886] Re: Include logs, monitors.xml and org.gnome.desktop.* settings in the apport-retrace data

2019-06-17 Thread Daniel van Vugt
Yes it makes sense if the shell crashes then very likely you have no
Xorg server to run xrandr against :)

-- 
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/1722886

Title:
  Include logs, monitors.xml and org.gnome.desktop.* settings in the
  apport-retrace data

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722886/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1825727] Re: gnome-shell-extension-prefs crashed with SIGSEGV in gtk_css_gadget_set_state() from gtk_switch_state_flags_changed()

2019-06-17 Thread Daniel van Vugt
** Description changed:

+ https://errors.ubuntu.com/problem/b9099237efc0ed3a713ac34e260c33a215c4599d
+ 
  Crashes when updating extensions using gnome-tweaks on Gnome 3.32+
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Apr 21 19:32:17 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell-extension-prefs
  InstallationDate: Installed on 2019-01-01 (110 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcCmdline: gnome-shell-extension-prefs dash-to-pa...@jderose9.github.com
  ProcEnviron:
-  LANGUAGE=en_IN:en
-  PATH=(custom, user)
-  XDG_RUNTIME_DIR=
-  LANG=en_IN
-  SHELL=/bin/bash
+  LANGUAGE=en_IN:en
+  PATH=(custom, user)
+  XDG_RUNTIME_DIR=
+  LANG=en_IN
+  SHELL=/bin/bash
  SegvAnalysis:
-  Segfault happened at: 0x7f32337f2a77:mov(%rdi,%rax,1),%rdi
-  PC (0x7f32337f2a77) ok
-  source "(%rdi,%rax,1)" (0xffd0) not located in a known VMA 
region (needed readable region)!
-  destination "%rdi" ok
+  Segfault happened at: 0x7f32337f2a77:mov(%rdi,%rax,1),%rdi
+  PC (0x7f32337f2a77) ok
+  source "(%rdi,%rax,1)" (0xffd0) not located in a known VMA 
region (needed readable region)!
+  destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
-  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
-  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
-  g_cclosure_marshal_VOID__UINTv () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
+  () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
+  g_cclosure_marshal_VOID__UINTv () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell-extension-prefs crashed with SIGSEGV
  UpgradeStatus: Upgraded to disco on 2019-04-19 (2 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-01-15T04:51:59.517661
  separator:

** Information type changed from Private to Public

-- 
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/1825727

Title:
  gnome-shell-extension-prefs crashed with SIGSEGV in
  gtk_css_gadget_set_state() from gtk_switch_state_flags_changed()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825727/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1833058] Re: /usr/bin/gnome-shell-extension-prefs:11:gtk_css_gadget_set_state:gtk_switch_state_flags_changed:g_cclosure_marshal_VOID__UINTv:_g_closure_invoke_va:g_signal_emit_valist

2019-06-17 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1825727 ***
https://bugs.launchpad.net/bugs/1825727

** This bug has been marked a duplicate of private bug 1825727

-- 
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/1833058

Title:
  /usr/bin/gnome-shell-extension-
  
prefs:11:gtk_css_gadget_set_state:gtk_switch_state_flags_changed:g_cclosure_marshal_VOID__UINTv:_g_closure_invoke_va:g_signal_emit_valist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833058/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832856] Re: Gnome-shell crashes frequently in gnome-shell/extensions/wsmat...@martin.zurowietz.de

2019-06-17 Thread Daniel van Vugt
Thanks. Unfortunately that page is showing an unreadable stack trace. It
also says that the gnome-shell binary file has changed (update
installed) since the crash occurred so it can't be retraced/reported.

Please reproduce the crash again and repeat the steps from comment #2.

-- 
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/1832856

Title:
  Gnome-shell crashes frequently in gnome-
  shell/extensions/wsmat...@martin.zurowietz.de

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832856/+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)

2019-06-17 Thread Daniel van Vugt
** Changed in: gdm3 (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Also affects: mutter (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: mutter (Ubuntu)
   Status: New => Triaged

** Changed in: mutter (Ubuntu)
   Importance: Undecided => High

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

-- 
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 1832856] Re: Gnome-shell crashes frequently in gnome-shell/extensions/wsmat...@martin.zurowietz.de

2019-06-17 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu)
   Status: Invalid => Incomplete

-- 
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/1832856

Title:
  Gnome-shell crashes frequently in gnome-
  shell/extensions/wsmat...@martin.zurowietz.de

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832856/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-17 Thread Daniel van Vugt
The status for mutter will remain incomplete till someone tries the
suggestion from comment #31.

Sorry, I still can't reproduce this bug myself.

-- 
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/1832138

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-17 Thread Daniel van Vugt
The problem I mentioned in comment #15 is now logged as bug 1833045.
It's clearly different to this one.

-- 
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/1832138

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1833045] [NEW] Ubuntu on Wayland login option is missing on random boots in VMware

2019-06-17 Thread Daniel van Vugt
Public bug reported:

Ubuntu on Wayland login option is missing on random boots in VMware.

This seems to be a persistent problem with Ubuntu 18.04, but seems to
have been fixed at least in 19.04.

In 18.04 where the bug does exist, upgrading the kernel to 5.1 doesn't
seem to help. This looks and feels like a mutter bug that has since been
fixed.

** Affects: mutter (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: mutter (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: mutter (Ubuntu Disco)
 Importance: Undecided
 Status: Invalid

** Affects: mutter (Ubuntu Eoan)
 Importance: Undecided
 Status: Invalid


** Tags: bionic

** Also affects: mutter (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: mutter (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: mutter (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: mutter (Ubuntu Disco)
   Status: New => Fix Released

** Changed in: mutter (Ubuntu Eoan)
   Status: New => Fix Released

** Changed in: mutter (Ubuntu Disco)
   Status: Fix Released => Invalid

** Changed in: mutter (Ubuntu Eoan)
   Status: Fix Released => Invalid

** Description changed:

  Ubuntu on Wayland login option is missing on random boots in VMware.
  
  This seems to be a persistent problem with Ubuntu 18.04, but seems to
  have been fixed at least in 19.04.
  
  In 18.04 where the bug does exist, upgrading the kernel to 5.1 doesn't
- seem to help so this looks and feels like a mutter bug that has since
- been fixed.
+ seem to help. This looks and feels like a mutter bug that has since been
+ fixed.

-- 
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/1833045

Title:
  Ubuntu on Wayland login option is missing on random boots in VMware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1833045/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1717453] Re: Shell menus (panel, dock, window) font size does not match configured interface font size

2019-06-17 Thread Daniel van Vugt
Fix in progress: https://gitlab.gnome.org/GNOME/gnome-
shell/merge_requests/486

-- 
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/1717453

Title:
  Shell menus (panel, dock, window) font size does not match configured
  interface font size

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1717453/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832946] Re: Gnome Shell performance decreases as the number of running apps increases

2019-06-17 Thread Daniel van Vugt
Note that not all performance improvements will ever make it into Ubuntu
18.04.

If you want higher performance right now then please use Ubuntu 19.04
instead. And Ubuntu 19.10 will be even faster (_after_ it gets mutter
3.33.3 or later).

Do you find that Ubuntu 19.04 has this same bug?

** Summary changed:

- Gnome Shell works the worst after I will  launch some apps
+ Gnome Shell performance decreases as the number of running apps increases

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Medium

-- 
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/1832946

Title:
  Gnome Shell performance decreases as the number of running apps
  increases

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832946/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832988] Re: Bluetooth not working

2019-06-16 Thread Daniel van Vugt
The attached RfKill.txt seems to suggest that Bluetooth is only turned
off in software. So maybe this is just a gnome-shell GUI bug, or gnome-
bluetooth.

To confirm this, please try turning it on by running this command in a
terminal:

  rfkill unblock 0


** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

** Also affects: gnome-bluetooth (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-bluetooth (Ubuntu)
   Status: New => Incomplete

-- 
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/1832988

Title:
  Intel 8260 Bluetooth not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1832988/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832988] Re: Bluetooth not working

2019-06-16 Thread Daniel van Vugt
If the above command doesn't work then I would next focus on a possible
kernel problem in:

[ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38)

** Summary changed:

- Bluetooth not working
+ Intel 8260 Bluetooth not working

-- 
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/1832988

Title:
  Intel 8260 Bluetooth not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1832988/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-16 Thread Daniel van Vugt
Pat,

Re comment #19, your crash (hang) reports there seem to show the gnome-
shell process behaving normally (in poll) and not stuck at all. That
doesn't tell us much but it would support the theory in comment #31.

** Summary changed:

- Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 fixes 
it
+ Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or 
using WaylandEnable=false) fixes it

-- 
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/1832138

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 fixes it

2019-06-16 Thread Daniel van Vugt
Interesting one of the commits mentioned above:

  37efe80ce85f drm/vmwgfx: use monotonic event timestamps
  
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f)

is related to what I changed in the latest update to mutter:

  https://gitlab.gnome.org/GNOME/mutter/commit/e9e4b2b72

The latest update to mutter requires monotonic event timestamps in the
kernel driver in order to work properly. It should kind of work without
them, but that fallback is untested...

So if that is the problem then you might find reverting to the previous
mutter version also works around the issue(?). You can download the
debs:

https://launchpad.net/ubuntu/+source/mutter/3.28.3+git20190124-0ubuntu18.04.2/+build/16644915

and then try installing them together:

  dpkg -i *.deb



** Also affects: mutter (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: mutter (Ubuntu Eoan)
   Status: New => Invalid

** Changed in: mutter (Ubuntu Bionic)
   Status: New => Incomplete

** Changed in: mutter (Ubuntu Bionic)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

-- 
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/1832138

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 fixes it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

2019-06-16 Thread Daniel van Vugt
Indeed there was a kernel update to 18.04 around the same time as the
mutter update which I thought was causing this bug.

** No longer affects: mutter (Ubuntu)

** No longer affects: mutter (Ubuntu Bionic)

** No longer affects: mutter (Ubuntu Eoan)

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: Confirmed

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Bionic)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Eoan)
   Status: Confirmed => Invalid

** Summary changed:

- Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it
+ Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 fixes 
it

-- 
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/1832138

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 fixes it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832959] Re: Wrong cursor size after screensaver

2019-06-16 Thread Daniel van Vugt
** Tags added: cursor hidpi

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Summary changed:

- Wrong cursor size after screensaver
+ [hidpi] Cursor is too small after screensaver

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: 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/1832959

Title:
  [hidpi] Cursor is too small after screensaver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832959/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832946] Re: Gnome Shell works the worst after I will launch some apps

2019-06-16 Thread Daniel van Vugt
It sounds like you're trying to describe general frame skipping and
performance degradation as more apps are opened. Can you please put the
problem into words so we can be sure what the problem is you are
reporting?


** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

** Tags added: performance

-- 
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/1832946

Title:
  Gnome Shell works the worst after I will  launch some apps

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832946/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832943] Re: When Firefox is appeared and I open gno-menu, I will see shade of Firefox at background

2019-06-16 Thread Daniel van Vugt
Can you please reword that? I don't understand (and can't see in the
video) what the problem is here.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

-- 
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/1832943

Title:
  When Firefox is appeared and I open gno-menu, I will see shade of
  Firefox at background

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832943/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832913] Re: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-06-16 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1800196 ***
https://bugs.launchpad.net/bugs/1800196

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 1800196, 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 1800196
   spice-vdagent[1345]: Cannot access vdagent virtio channel 
/dev/virtio-ports/com.redhat.spice.0

-- 
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/1832913

Title:
  Cannot access vdagent virtio channel /dev/virtio-
  ports/com.redhat.spice.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1832913/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832869] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call()

2019-06-16 Thread Daniel van Vugt
** Tags added: regression-update

-- 
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/1832869

Title:
  gnome-shell crashed with SIGSEGV in g_hash_table_iter_next →
  meta_display_list_windows → meta_workspace_list_windows →
  ffi_call_SYSV → ffi_call()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832869/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832856] Re: Gnome-shell crashes frequently

2019-06-16 Thread Daniel van Vugt
It appears this crash is in:

  /home/gjm/.local/share/gnome-
shell/extensions/wsmat...@martin.zurowietz.de

which is not part of Ubuntu, so we can't handle it here. Sorry.

I suggest you uninstall that extension to avoid the crash.

** Summary changed:

- Gnome-shell crashes frequently
+ Gnome-shell crashes frequently in 
gnome-shell/extensions/wsmat...@martin.zurowietz.de

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Invalid

-- 
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/1832856

Title:
  Gnome-shell crashes frequently in gnome-
  shell/extensions/wsmat...@martin.zurowietz.de

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832856/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832856] Re: Gnome-shell crashes frequently

2019-06-16 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

-- 
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/1832856

Title:
  Gnome-shell crashes frequently in gnome-
  shell/extensions/wsmat...@martin.zurowietz.de

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832856/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery

2019-06-16 Thread Daniel van Vugt
Thanks. Since gnome-shell provides all the graphics (even the lock
screen), this bug is now assigned to gnome-shell only.

** Changed in: gdm3 (Ubuntu)
   Status: Incomplete => New

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

** No longer affects: gdm3 (Ubuntu)

-- 
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/1832812

Title:
  Locking and unlocking the screen is slow and stuttery

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832812/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832869] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call()

2019-06-16 Thread Daniel van Vugt
** Summary changed:

- gnome-shell crashed in g_hash_table_iter_next meta_display_list_windows 
meta_workspace_list_windows
+ gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → 
meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → 
ffi_call()

-- 
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/1832869

Title:
  gnome-shell crashed with SIGSEGV in g_hash_table_iter_next →
  meta_display_list_windows → meta_workspace_list_windows →
  ffi_call_SYSV → ffi_call()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832869/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1753884] Re: session logout after suspend

2019-06-16 Thread Daniel van Vugt
Unfortunately we can't backport a fix which we don't know the location
of. And I don't see any links to a patch here. Also, we generally don't
support/patch gnome-shell on Ubuntu releases older than 18.04.

Anyway, this bug is closed and we can't be sure you are experiencing the
exact same issue. So please open a new bug.

-- 
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/1753884

Title:
   session logout after suspend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753884/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1722886] Re: Include logs, monitors.xml and org.gnome.desktop.* settings in the apport-retrace data

2019-06-16 Thread Daniel van Vugt
I'm not sure monitors.xml is any more useful than the xrandr output we
already get... unless xrandr output is missing from crash bugs?

-- 
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/1722886

Title:
  Include logs, monitors.xml and org.gnome.desktop.* settings in the
  apport-retrace data

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722886/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

2019-06-14 Thread Daniel van Vugt
Looking at hungboot.txt I am starting to think maybe the login screen
('gnome-shell' process) is actually running in Wayland mode but failing
to display. That would explain a lot...

Pat, can you please reproduce the bug again and while it is happening:

 1. SSH into the VM.

 2. Run 'pidof gnome-shell' to find out the process ID of that process.
Tell us if you don't get a result.

 3. If you do get a result from step 2 then using that PID run:

sudo kill -ABRT PID

where PID is the process ID number.

 4. Wait 30 seconds.

 5. Hopefully a crash report will have been generated so now follow:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment


** Changed in: mutter (Ubuntu Bionic)
   Status: In Progress => Incomplete

-- 
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/1832138

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1832138/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

2019-06-14 Thread Daniel van Vugt
I have been trying to reproduce this bug in VMware but have not been
able to. Ubuntu 18.04 always starts up with a login screen successfully
for me.

What it does not do successfully is offer the "Ubuntu on Wayland" option
most of the time. So I expect that's the same root cause as this bug.

Ordinarily if Wayland support is attempted and fails gracefully then
your journalctl log should show something like:

  Jun 14 02:28:16 ubuntu gnome-shell[790]: Failed to create backend:
Could not find a primary drm kms device

If you don't see that message and still don't get Wayland support then
it suggests mutter/gnome-shell is crashing during that attempt to try
Wayland. In that case we would ask you to follow these instructions from
within the virtual machine:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

I'll dig a bit deeper to try and find out why Wayland support seems to
work so rarely, because that's the part of this bug I can reproduce.

-- 
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/1832138

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1832138/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

2019-06-14 Thread Daniel van Vugt
Jussi,

That sounds like maybe a different bug. Although "commenting out the
Wayland" is also not what you need to do. You need to change:

  #WaylandEnable=false

to:

  WaylandEnable=false

If that doesn't fix the problem for you then you have a different bug.
In that case please open a new bug by running:

  ubuntu-bug mutter

from within the VM.

-- 
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/1832138

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1832138/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery

2019-06-14 Thread Daniel van Vugt
Are you able to make another video without Firefox running?


** Changed in: gdm3 (Ubuntu)
   Status: Incomplete => New

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => 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/1832812

Title:
  Locking and unlocking the screen is slow and stuttery

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832812/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery

2019-06-14 Thread Daniel van Vugt
Also, before locking the screen please open a Terminal window and run
'top' then take a screenshot of the window and attach it to this bug.

** Changed in: gdm3 (Ubuntu)
   Status: New => Incomplete

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

-- 
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/1832812

Title:
  Locking and unlocking the screen is slow and stuttery

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832812/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832816] Re: Gnome Shell is slow and stuttery while Firefox is loading/playing YouTube

2019-06-14 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1424201 ***
https://bugs.launchpad.net/bugs/1424201

> Shell works slowly with efforts also without Firefox launching.

Yes, we know. But that's not an exact bug as much as an observation that
performance is poor. For the type of issues you describe I have made a
list of fixes we need, which is half done:

https://trello.com/c/Q6JYXPPs

-- 
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/1832816

Title:
  Gnome Shell is slow and stuttery while Firefox is loading/playing
  YouTube

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832816/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery

2019-06-14 Thread Daniel van Vugt
Also, does the bug still occur if you close Firefox before locking the
screen?

If not then this may be related to bug 1832816.

** Summary changed:

- Ubuntu 19.10 (alpha) lockscreen freezes
+ Locking and unlocking the screen is slow and stuttery

** Tags added: performance

-- 
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/1832812

Title:
  Locking and unlocking the screen is slow and stuttery

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832812/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

2019-06-14 Thread Daniel van Vugt
** Changed in: mutter (Ubuntu Bionic)
   Status: Confirmed => In Progress

-- 
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/1832138

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1832138/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832816] Re: Gnome Shell is slow and stuttery while Firefox is loading/playing YouTube

2019-06-14 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1424201 ***
https://bugs.launchpad.net/bugs/1424201

** Summary changed:

- Ubuntu 19.10 Gnome Desktop works with freezes and efforts
+ Gnome Shell is slow and stuttery while Firefox is loading/playing YouTube

-- 
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/1832816

Title:
  Gnome Shell is slow and stuttery while Firefox is loading/playing
  YouTube

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832816/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832816] Re: Ubuntu 19.10 Gnome Desktop works with freezes and efforts

2019-06-14 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1424201 ***
https://bugs.launchpad.net/bugs/1424201

It appears the problem is probably that your web browser is using all
the CPU power to display YouTube's auto-playing front page. Because our
web browsers don't support hardware video decoding (LP: #1424201).

Your CPU is certainly new enough to do it. Your CPU is Apollo Lake
generation as shown in this picture:

  https://wiki.ubuntu.com/IntelQuickSyncVideo#YouTube

So the only problem here is that Firefox would be stealing all your CPU
time, which then prevents gnome-shell from responding quickly. That
makes this a duplicate of bug 1424201.


** This bug has been marked a duplicate of bug 1424201
   Web browsers lacking hardware-accelerated video decoding

-- 
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/1832816

Title:
  Gnome Shell is slow and stuttery while Firefox is loading/playing
  YouTube

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832816/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832812] Re: Ubuntu 19.10 (alpha) lockscreen freezes

2019-06-14 Thread Daniel van Vugt
Also, does the bug still occur if you disable this?

AutomaticLoginEnable=true

-- 
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/1832812

Title:
  Ubuntu 19.10 (alpha) lockscreen freezes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832812/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1832812] Re: Ubuntu 19.10 (alpha) lockscreen freezes

2019-06-14 Thread Daniel van Vugt
Can you confirm you are not using any gnome-shell extensions?

** Changed in: gdm3 (Ubuntu)
   Status: New => Incomplete

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

-- 
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/1832812

Title:
  Ubuntu 19.10 (alpha) lockscreen freezes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1832812/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)

2019-06-14 Thread Daniel van Vugt
The bug is marked as "fix released" so as far as we know the issue is
closed.

If you still experience problems then please open a new bug by running:

  ubuntu-bug gnome-shell

and mention that it seems to be related to bug 1812266.

-- 
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/1812266

Title:
  Keyboard layout indicator does not indicate current layout (18.04
  Bionic beaver)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+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

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 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

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 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

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) 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

  1   2   3   4   5   6   7   8   9   10   >