[Bug 1770315] Re: slow typing password

[Daniel van Vugt]

Please attach:

1. Output from 'lspci -k'

2. Output from 'journalctl -b' (immediately after the problem has
happened)

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

Title:
  slow typing password

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

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

[Bug 1770315] [NEW] slow typing password

[Diogo Filho de Morais]

Public bug reported:

The password does not appear quickly when typing to login or install
programs in the software center. Sometimes the blocking screen takes so
long that we think Ubuntu has crashed.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu May 10 01:40:22 2018
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2018-05-09 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  slow typing password

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

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

[Bug 1730211] Re: Unable to type capital letters using onscreen keyboard

[PJSingh5000]

I think this bug has been moved to https://gitlab.gnome.org/GNOME/gnome-
shell/issues/135

How can we add a remote bug watch for that?

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

Title:
  Unable to type capital letters using onscreen keyboard

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

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

[Bug 815389] Re: 3 problems with renaming / deleting .desktop files in nautilus

[Bug Watch Updater]

** Changed in: nautilus
   Status: Confirmed => Invalid

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

Title:
  3 problems with renaming / deleting .desktop files in nautilus

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

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

[Bug 1770299] Re: Gjs-WARNING Some code accessed the property 'discreteGpuAvailable'

[Daniel van Vugt]

*** This bug is a duplicate of bug 1723678 ***
https://bugs.launchpad.net/bugs/1723678

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 1723678, 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 1723678
   Some code accessed the property 'discreteGpuAvailable' on the module 
'appDisplay'. | This was previously supported, but is not correct according to 
the ES6 standard.

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

Title:
  Gjs-WARNING Some code accessed the property 'discreteGpuAvailable'

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

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

[Bug 1769116] Re: Gnome shell error in logs discreteGpuAvailable

[Daniel van Vugt]

*** This bug is a duplicate of bug 1723678 ***
https://bugs.launchpad.net/bugs/1723678

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 1723678, 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 1723678
   Some code accessed the property 'discreteGpuAvailable' on the module 
'appDisplay'. | This was previously supported, but is not correct according to 
the ES6 standard.

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

Title:
  Gnome shell error in logs discreteGpuAvailable

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

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

[Bug 1723678] Re: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. | This was previously supported, but is not correct according to the ES6 standard.

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Some code accessed the property 'discreteGpuAvailable' on the module
  'appDisplay'. | This was previously supported, but is not correct
  according to the ES6 standard.

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

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

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

[Daniel van Vugt]

OK. Sounds like there is a device (/dev/* file) that you're not getting
correct access to. And you can only get around that limitation by
running as root (which is not recommended, for security).

In this case we may find it's an nvidia driver (or installation) bug.
Although your original observation that it's a gdm problem might
actually explain this too. I don't know if it's gdm, systemd or
something else that handles the required privilege escalation to access
/dev/GRAPHICS_THINGS so am reopening the gdm task in the hope that
somebody else knows...


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

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

Title:
  Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used
  (Optimus)

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

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

[Bug 1770299] [NEW] Gjs-WARNING Some code accessed the property 'discreteGpuAvailable'

[PJSingh5000]

Public bug reported:

I executed gnome-shell --replace from the terminal.

After navigating through gnome-shell using my touch screen, I observed
the following warnings in the terminal window...

(gnome-shell:1940): Gjs-WARNING **: 22:17:58.795: Some code accessed the
property 'discreteGpuAvailable' on the module 'appDisplay'. That
property was defined with 'let' or 'const' inside the module. This was
previously supported, but is not correct according to the ES6 standard.
Any symbols to be exported from a module must be defined with 'var'. The
property access will work as previously for the time being, but please
fix your code anyway.

(gnome-shell:1940): Gjs-WARNING **: 22:17:58.811: Some code accessed the
property 'WindowPreviewMenuItem' on the module 'windowPreview'. That
property was defined with 'let' or 'const' inside the module. This was
previously supported, but is not correct according to the ES6 standard.
Any symbols to be exported from a module must be defined with 'var'. The
property access will work as previously for the time being, but please
fix your code anyway.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed May  9 22:29:33 2018
DisplayManager: gdm3
InstallationDate: Installed on 2018-05-05 (5 days ago)
InstallationMedia: Ubuntu 18.04.0 2018.05.03 LTS "Custom Bionic Beaver"
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Description changed:

- I executed gnome-shell --restart from the termnal.
+ I executed gnome-shell --replace from the termnal.
  
- 
- After navigating through gnome-shell using my touch screen, I observed the 
following warnings in the terminal window... 
+ After navigating through gnome-shell using my touch screen, I observed
+ the following warnings in the terminal window...
  
  (gnome-shell:1940): Gjs-WARNING **: 22:17:58.795: Some code accessed the
  property 'discreteGpuAvailable' on the module 'appDisplay'. That
  property was defined with 'let' or 'const' inside the module. This was
  previously supported, but is not correct according to the ES6 standard.
  Any symbols to be exported from a module must be defined with 'var'. The
  property access will work as previously for the time being, but please
  fix your code anyway.
  
  (gnome-shell:1940): Gjs-WARNING **: 22:17:58.811: Some code accessed the
  property 'WindowPreviewMenuItem' on the module 'windowPreview'. That
  property was defined with 'let' or 'const' inside the module. This was
  previously supported, but is not correct according to the ES6 standard.
  Any symbols to be exported from a module must be defined with 'var'. The
  property access will work as previously for the time being, but please
  fix your code anyway.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed May  9 22:29:33 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-05-05 (5 days ago)
  InstallationMedia: Ubuntu 18.04.0 2018.05.03 LTS "Custom Bionic Beaver"
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

- I executed gnome-shell --replace from the termnal.
+ I executed gnome-shell --replace from the terminal.
  
  After navigating through gnome-shell using my touch screen, I observed
  the following warnings in the terminal window...
  
  (gnome-shell:1940): Gjs-WARNING **: 22:17:58.795: Some code accessed the
  property 'discreteGpuAvailable' on the module 'appDisplay'. That
  property was defined with 'let' or 'const' inside the module. This was
  previously supported, but is not correct according to the ES6 standard.
  Any symbols to be exported from a module must be defined with 'var'. The
  property access will work as previously for the time being, but please
  fix your code anyway.
  
  (gnome-shell:1940): Gjs-WARNING **: 22:17:58.811: Some code accessed the
  property 'WindowPreviewMenuItem' on the module 'windowPreview'. That
  property was defined with 'let' or 'const' inside the module. This was
  previously supported, but is not correct according to 

[Bug 1770238] Re: Black screen of Death after logging in Ubuntu Bionic

[Daniel van Vugt]

1. You don't have an integrated GPU, do you? I am reminded of bug
1705369.

2. In case something is crashing, check /var/crash for files and run
'ubuntu-bug YOURFILE.crash' on each. And tell us here the IDs of new
bugs created.

3. As soon as the problem happens again, please take a copy of
~/.local/share/xorg/* and attach them here.

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

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

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

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

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

** Tags added: nvidia

** Summary changed:

- Black screen of Death after logging in Ubuntu Bionic
+ [nvidia] Logging in results in a black screen for many minutes after which 
the login screen reappears and I am able to login fine.

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

Title:
  [nvidia] Logging in results in a black screen for many minutes after
  which the login screen reappears and I am able to login fine.

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

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

[Bug 1769969] Re: GDM3 does not start if SDDM is installed (18.04)

[Daniel van Vugt]

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

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

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

Title:
  GDM3 does not start if SDDM is installed (18.04)

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

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

[Bug 1769695] Re: Freeze of Surface for 2 Minutes

[Daniel van Vugt]

Sounds like Java is causing a lot of log messages, but that might not be
related to the freeze.

Please start by keeping Eclipse and any other Java apps closed for a
while. You should be able to keep native apps like Firefox and Terminal
open.

** Package changed: gdm3 (Ubuntu) => gnome-shell (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/1769695

Title:
  Freeze of Surface for 2 Minutes

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

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

[Bug 1769695] Re: Freeze of Surface for 2 Minutes

[Daniel van Vugt]

Please also run this command to send us more info:

  apport-collect 1769695

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

Title:
  Freeze of Surface for 2 Minutes

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

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

[Bug 1769695] Re: Freeze of Surface for 2 Minutes

[Daniel van Vugt]

Also these two messages suggest pauses at a low level that could block
other things:

May 7 17:27:40 reichelt-desktop nautilus[3278]: Called "net usershare
info" but it failed: Kindprozess »net« konnte nicht ausgeführt werden
(No such file or directory)

May 9 17:41:25 reichelt-desktop kernel: [ 1033.469201] perf: interrupt
took too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate
to 79750

The second one in particular suggests the kernel is getting stuck. Maybe
keep an eye on the kernel log (dmesg -w) for more information.

Also try avoiding network filesystems/mounts for a while (in case you're
using those). Any problem in the network while doing so could cause such
pauses. Although admittedly a properly designed UI should ignore such
issues, I don't think gnome-shell is there yet.

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

Title:
  Freeze of Surface for 2 Minutes

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

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

[Bug 1765141] Re: [regression] Full screen white flash from time to time (Wayland and X11)

[Daniel van Vugt]

** Tags added: amggpu radeon

** Tags removed: amggpu
** Tags added: amdgpu

** Summary changed:

- [regression] Full screen white flash from time to time (Wayland and X11)
+ [amdgpu][radeon][regression] Full screen white flash from time to time 
(Wayland and X11)

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

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

** Changed in: mutter (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/1765141

Title:
  [amdgpu][radeon][regression] Full screen white flash from time to time
  (Wayland and X11)

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

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

[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

[Daniel van Vugt]

Do people find this is any worse/better in Wayland vs Xorg sessions?

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

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

[Bug 1189115] Re: Sound control lacks surround upmix tick and default card choice

[Daniel van Vugt]

As you've reported two separate issues here, please move one of them
into a new bug.

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

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

Title:
  Sound control lacks surround upmix tick and default card choice

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

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

[Bug 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnom

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-keyring - 3.28.0.2-1ubuntu2

---
gnome-keyring (3.28.0.2-1ubuntu2) cosmic; urgency=medium

  * debian/control{,.in}: Drop old transitional package
libp11-kit-gnome-keyring; it's not needed past an LTS. (LP: #1768541)

 -- Iain Lane   Wed, 09 May 2018 20:05:34 +0100

** Changed in: gnome-keyring (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

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

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

[Bug 1537606] Re: Changing icon sizes causes desktop icon sizes to change too

[Bug Watch Updater]

** Changed in: nautilus
   Status: Confirmed => Expired

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

Title:
  Changing icon sizes causes desktop icon sizes to change too

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

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

[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

[Simon Eisenmann]

Oh wow this was driving me nuts - and indeed the "workspaces-to-dock"
extension caused it like in comment #48 - thanks!

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

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

[Bug 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnom

[Adam Conrad]

Hello Fondfire, or anyone else affected,

Accepted gnome-keyring into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
keyring/3.28.0.2-1ubuntu1.18.04.1 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: gnome-keyring (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

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

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

[Bug 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnom

[Iain Lane]

Uploaded to bionic queue, sru description to follow once I've worked out
a reproer

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

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

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

[Bug 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnom

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/gnome-keyring/ubuntu

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

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

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

[Bug 1769954] Re: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Brian Murray]

** Changed in: desktop-file-utils (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1769954/+subscriptions

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

[Bug 1770135] Re: Rhythmbox initially crashes when trying to play a song

[Simon P.]

The bug seems to be related to the alternative toolbar once again. When
disabling the alternative toolbar, Rhythmbox works stable without those
crashes.

** Also affects: alternative-toolbar
   Importance: Undecided
   Status: New

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

Title:
  Rhythmbox initially crashes when trying to play a song

To manage notifications about this bug go to:
https://bugs.launchpad.net/alternative-toolbar/+bug/1770135/+subscriptions

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

[Bug 1770238] Re: Black screen of Death after logging in Ubuntu Bionic

[Jonathan]

Tried to run the calculator app again and system crashed...

After system startup and login ended up in black screen again.

I was able to ssh into the machine and manually restart systemd-logind.
The login screen reappeared after a couple seconds and I was able to
login without being stuck in the black screen.

sudo systemctl restart systemd-logind.service

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

Title:
  Black screen of Death after logging in Ubuntu Bionic

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

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

[Bug 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnom

[Iain Lane]

** Changed in: gnome-keyring (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gnome-keyring (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: gnome-keyring (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

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

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

[Bug 1770238] [NEW] Black screen of Death after logging in Ubuntu Bionic

[Jonathan]

Public bug reported:

** Ubuntu Bionic; Nvidia GTX 1050 w/`nvidia-390` drivers

** Problem: Logging in results in a black screen for many minutes after which 
the login screen reappears and I am able to login fine. The below log seems to 
be the earliest error when this occurs.
Note: This happened twice today so far, presumably each time I reboot.


May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) 
NVIDIA(GPU-0): Failed to acquire modesetting permission.
May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) 
NVIDIA(0): Failing initialization of X screen 0
May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (II) 
UnloadModule: "nvidia"
May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (II) 
UnloadSubModule: "wfb"
May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (II) 
UnloadSubModule: "fb"
May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) 
Screen(s) found, but none have a usable configuration.
May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE)
May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: Fatal 
server error:
May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) no 
screens found(EE)
May  9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE)

** A systemd-logind watchdog seems to be responsible for the login
screen reappearing

May  9 11:20:02 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Watchdog 
timeout (limit 3min)!
May  9 11:20:02 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Killing 
process 1697 (systemd-logind) with signal SIGABRT.
May  9 11:20:03 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Main 
process exited, code=dumped, status=6/ABRT
May  9 11:20:03 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Failed 
with result 'watchdog'.

** The Xorg.0.log doesn't seem to have any problem finding the screens
just before the above error.

29406:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: (II) 
NVIDIA(0): NVIDIA GPU GeForce GTX 1050 (GP107-A) at PCI:23:0:0 (GPU-0)
29407:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: (--) 
NVIDIA(0): Memory: 2097152 kBytes
29408:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: (--) 
NVIDIA(0): VideoBIOS: 86.07.2f.00.68
29409:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: (II) 
NVIDIA(0): Detected PCI Express Link width: 16X
29412:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: (--) 
NVIDIA(GPU-0): Acer AL1917 (DFP-0): connected
29413:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: (--) 
NVIDIA(GPU-0): Acer AL1917 (DFP-0): Internal TMDS
29414:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: (--) 
NVIDIA(GPU-0): Acer AL1917 (DFP-0): 330.0 MHz maximum pixel clock
29415:May  9 11:03:47 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[1742]: (--) 
NVIDIA(GPU-0):


** Note that I also saw the watchdog kick in while I was logged in and working 
when I was suddenly sent back to the login screen.  I believe that lines up 
with the syslog timestamp below:


May  9 10:31:24 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Watchdog 
timeout (limit 3min)!
May  9 10:31:24 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Killing 
process 1691 (systemd-logind) with signal SIGABRT.
May  9 10:31:25 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Main 
process exited, code=dumped, status=6/ABRT
May  9 10:31:25 jcormier-MS-7A93 systemd[1]: systemd-logind.service: Failed 
with result 'watchdog'.
May  9 10:31:25 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2607]: (EE)
May  9 10:31:25 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2607]: Fatal 
server error:
May  9 10:31:25 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2607]: (EE) 
systemd-logind disappeared (stopped/restarted?)
May  9 10:31:25 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2607]: (EE)
May  9 10:31:25 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2607]: (EE)

** I also experienced the computer reboot when I tried to open the
calculator app sometime between these two timestamps.

May  9 13:18:27 jcormier-MS-7A93 org.gnome.Shell.desktop[3311]: Window manager 
warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 
for 0x2605a63 (Find/Repla)
May  9 13:20:06 jcormier-MS-7A93 systemd-modules-load[437]: Inserted module 'lp'


 $ sudo ubuntu-drivers devices
== /sys/devices/pci:16/:16:00.0/:17:00.0 ==
modalias : pci:v10DEd1C81sv1458sd372Cbc03sc00i00
vendor   : NVIDIA Corporation
model: GP107 [GeForce GTX 1050]
driver   : nvidia-driver-390 - distro non-free recommended
driver   : xserver-xorg-video-nouveau - distro free builtin

It seems similar to this bug:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1748656

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 

[Bug 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnom

[Iain Lane]

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

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

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

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

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

[nastys]

I have found out just now that if I run anything Vulkan as root (e.g.
sudo vulkan-smoketest), IT WORKS! And if I then run it without sudo, IT
STILL WORKS!

At this point I have no idea what is going on, nor why this doesn't affect 
lightdm nor sddm.
It seems the affected package is indeed nvidia-graphics-drivers-390. Since it 
is proprietary, I'll ask in the NVIDIA Devtalk forums.

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

Title:
  Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used
  (Optimus)

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

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

[Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

[Bug Watch Updater]

** Changed in: gdm
   Status: Confirmed => Incomplete

** Changed in: gdm
   Importance: Medium => Critical

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

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

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

[Bug 1769954] Re: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Brian Murray]

The sources.list file in the provided apt-clone information indicates
that you were running Ubuntu 17.10 not Ubuntu 16.04 as mentioned in the
description. Is this the correct apt-clone file?

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

Title:
  package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1769954/+subscriptions

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

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

[nastys]

After some investigating, I have found that if I log out, switch to TTY then 
run startx, I get the same issue. However I noticed that if I run sudo startx, 
Vulkan works, and it still works after logging out and running startx as a 
normal user, until the computer is rebooted. Then I tried logging in as root 
from GDM and I got the same result.
Something is probably not being initialized properly when logging in as a 
non-root user.
I think the affected package is actually xinit, but I'm not sure.

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

Title:
  Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used
  (Optimus)

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

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

[Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

[Tom F]

Not on first login but on switch user after entering correct password I
get purple screen and mouse.

Sometimes after a long delay I can get back to the login screen.  I can
usually force it back to the login screen by hitting a few random cycles
of ctl+alt + F1, ctl+alt F2 and ctl+alt + F3.

At this point, if I click on the the user that failed it shows a message
about authorization problem (but the password was correct).  At login of
this user it then allows access.

I know on subsequent logins it is going to fail as soon as I see the
purple screen.  If I see initial black, I know it is going to work OK.

I noticed this issue on an initial clean build on erased disks.
Concerned about my hardware, I rebuilt again from clean and the problem
is the same.  I do not have a graphics card.  I have: Intel® Core™
i7-4790 CPU @ 3.60GHz × 8.  Ram = 24g.

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

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

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

[Bug 1750146] Re: Xbox (One) Wireless Controller won't connect

[Andre Lima]

I'm using this workaround as a permanent solution. (while waiting for
kernel patches for this problem)

- Install sysfsutils. (with synaptic or on terminal)
- edit this file with sudo - sudo nano /etc/sysfs.conf
- add this line at the end - /module/bluetooth/parameters/disable_ertm = 1
- reboot. 

Now the controller is working without problems on Ubuntu 18.04.

On ubuntu 16.04.4 the controller start moving the mouse after the first 
workaround. If it happens use this: 
- On terminal type - xinput list - and copy how your system recognize the 
gamepad. Generally is something 
  like "Xbox Wireless Controller"
- Open a terminal and type - xinput --set-prop "Xbox Wireless Controller" 
"Device Enabled" 0
- Repeat that second trick every time you got the problem.

Regards! Hope it helps.

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

Title:
  Xbox (One) Wireless Controller won't connect

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1750146/+subscriptions

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

[Bug 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnom

[Adam Conrad]

See e2fsprogs for the fix there, which almost certainly is needed here
too:

http://launchpadlibrarian.net/357614118/e2fsprogs_1.43.9-1_1.43.9-1ubuntu1.diff.gz

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

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

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

[Bug 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnom

[Adam Conrad]

>From IRC:

11:15 < infinity> Laney: You can't move from MA:same to arch:all.
11:15 < infinity> Laney: You need to use an MA:same transitional as well.
11:17 < infinity> Laney: arch:all by definition can only have one version/copy 
installed, so your 
  transitional upgrades on the primary arch, and ends up 
conflicting out any other 
  arch versions of the old package.
11:18 < infinity> Laney: Ran into this same issue with e2fslibs when Ted tried 
to do what you did.  
  Went very poorly until I fixed it. :P

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

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

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

[Bug 1770210] Re: package shared-mime-info 1.2-0ubuntu3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package shared-mime-info 1.2-0ubuntu3 failed to install/upgrade: le
  sous-processus script post-installation installé a retourné une erreur
  de sortie d'état 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1770210/+subscriptions

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

[Bug 1770210] [NEW] package shared-mime-info 1.2-0ubuntu3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

[Daniel U. Thibault]

Public bug reported:

Upgrading from 14.04.5 to 16.04.4.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shared-mime-info 1.2-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-124.148~14.04.1-generic 4.4.117
Uname: Linux 4.4.0-124-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
Date: Wed May  9 12:18:48 2018
DuplicateSignature: package:shared-mime-info:1.2-0ubuntu3:le sous-processus 
script post-installation installé a retourné une erreur de sortie d'état 1
ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
InstallationDate: Installed on 2017-01-17 (477 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.8
 apt  1.0.1ubuntu2.18
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.2-0ubuntu3 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
UpgradeStatus: Upgraded to xenial on 2018-05-09 (0 days ago)

** Affects: shared-mime-info (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package shared-mime-info 1.2-0ubuntu3 failed to install/upgrade: le
  sous-processus script post-installation installé a retourné une erreur
  de sortie d'état 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1770210/+subscriptions

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

[Bug 1765141] Re: [regression] Full screen white flash from time to time (Wayland and X11)

[Hadrien]

Mesa version is the one that comes with Ubuntu 18.04: Mesa 18.0.0-rc5

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765141/+attachment/5136754/+files/lspci.txt

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

Title:
  [regression] Full screen white flash from time to time (Wayland and
  X11)

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

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

[Bug 1770163] Re: my system crashed when i try to open android emulator

[Olivier Tilloy]

Per attached screenshot, what crashed is systemd-logind.

** Package changed: chromium-browser (Ubuntu) => systemd (Ubuntu)

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

Title:
  my system crashed when i try to open android emulator

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

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

[Bug 1769695] Re: Freeze of Surface for 2 Minutes

[David Georg Reichelt]

It seems like this happened again, but now syslog just contains:

May  9 17:41:17 reichelt-desktop thunderbird.desktop[3186]: [calBackendLoader] 
Using Thunderbird's builtin libical backend
May  9 17:41:24 reichelt-desktop gnome-shell[1833]: Some code accessed the 
property 'WindowPreviewMenu' on the module 'windowPreview'. That property was 
defined with 'let' or 'const' inside the module. This was previously supported, 
but is not correct according to the ES6 standard. Any symbols to be exported 
from a module must be defined with 'var'. The property access will work as 
previously for the time being, but please fix your code anyway.
May  9 17:41:24 reichelt-desktop gnome-shell[1833]: pushModal: invocation of 
begin_modal failed
May  9 17:41:25 reichelt-desktop kernel: [ 1033.469201] perf: interrupt took 
too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 79750
May  9 17:43:05 reichelt-desktop sudo: pam_ecryptfs: pam_sm_authenticate: 
/home/reichelt is already mounted

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

Title:
  Freeze of Surface for 2 Minutes

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

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

[Bug 1770163] [NEW] my system crashed when i try to open android emulator

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I was just trying to install android studio from software center
unfortunately i could not do that. So then I download it from official
web site then installed it. After installation is completed i was just
try to open android emulator then my system began work slower and slower
and i got this error "Your computer does not have enough free memory to
automatically analyze the problem and send a report to the developers"
then i try to send report via terminal.

System information: 
  RAM: 12 GB
  processor: intel core i5-4200H CPU @ 2.80GHz x 4
  graphics: llvmpipe (LLVM 5.0, 256 bits)
  OS type: 64-bit
  disk: 725,6 GB 

package version: android studio 3.1.2 for Linux 64-bit (853 MB) (from
official web site of android studio)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: chromium-browser (not installed)
ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-41-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CurrentDesktop: Unity
Date: Wed May  9 15:32:25 2018
InstallationDate: Installed on 2018-05-04 (5 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial
-- 
my system crashed when i try to open android emulator
https://bugs.launchpad.net/bugs/1770163
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to systemd in Ubuntu.

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

[Bug 1769969] ProcCpuinfoMinimal.txt

[Raul Dias]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1769969/+attachment/5136723/+files/ProcCpuinfoMinimal.txt

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

Title:
  GDM3 does not start if SDDM is installed (18.04)

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

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

[Bug 1769969] Re: GDM3 does not start if SDDM is installed (18.04)

[Raul Dias]

apport information

** Tags added: apport-collected bionic

** Description changed:

  After upgrading my office machines to 18.04, some machines did not start
  the GDM3.
  
  After some testing the problem was that the ones that it did not work,
  had SDDM installed too (KDE environment in those machines).
  
  The upgrade were from 17.10 and 16.04.
  
  Note that reistalling sddm, gdm3, lightdm, dpkg-reconfigure gdm3, none
  worked.
  
  On gdm3 side: systemctl is-active gdm3 reports static (which might be
  the problem).
  
  After removing sddm and rebooting, everything worked as expected.
+ --- 
+ ApportVersion: 2.20.9-0ubuntu7
+ Architecture: amd64
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2014-05-12 (1458 days ago)
+ InstallationMedia: Error: [Errno 13] Permission denied: 
'/var/log/installer/media-info'
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: sddm
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
+ Tags:  bionic
+ Uname: Linux 4.15.0-20-generic x86_64
+ UpgradeStatus: Upgraded to bionic on 2018-04-27 (12 days ago)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1769969/+attachment/5136722/+files/Dependencies.txt

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

Title:
  GDM3 does not start if SDDM is installed (18.04)

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

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

[Bug 1769969] ProcEnviron.txt

[Raul Dias]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1769969/+attachment/5136724/+files/ProcEnviron.txt

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

Title:
  GDM3 does not start if SDDM is installed (18.04)

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

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

[Bug 1756369] Re: Google Calendar is not syncing in Ubuntu 18.04

[CrazySky]

Another confirmation. But if I try to sync calendars manually, I have a
form for auth in Google. But if I enter right login/password I have
error "HTTP error code 401 (Unauthorized)".

I tried to disable 2-auth Google but still no effect.

** Summary changed:

- Google Calendar is not syncing in Ubuntu 18.04 Beta.
+ Google Calendar is not syncing in Ubuntu 18.04

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

Title:
  Google Calendar is not syncing in Ubuntu 18.04

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

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

[Bug 1769372] Re: Prompt the user when the power button is pressed on a VM

[Norbert]

OK, Jeremy!

Thank you! I hope to get this bug will be fixed.

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

Title:
  Prompt the user when the power button is pressed on a VM

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

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

[Bug 1769372] Re: Prompt the user when the power button is pressed on a VM

[Jeremy Bicha]

Norbert, the upstream bug is https://gitlab.gnome.org/GNOME/gnome-
settings-daemon/issues/46

Once that issue is fixed in GNOME, it can be fixed in the current
development release of Ubuntu and then in Ubuntu 18.04 LTS.

Comment #18 here was about something different so you can probably
ignore that.

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

Title:
  Prompt the user when the power button is pressed on a VM

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

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

[Bug 1751182] Re: package gdm3 3.26.1-3ubuntu3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 10

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package gdm3 3.26.1-3ubuntu3 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 10

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

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

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

[nastys]

I know that VSync and PRIME Sync are not the same thing. With modeset
disabled, VSync IS enabled but there is tearing regardless, and I can
see that even just by dragging a window around the screen.

glxgears reports:
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
37879 frames in 5.0 seconds = 7575.718 FPS
38056 frames in 5.0 seconds = 7611.121 FPS
[...]

There is absolutely no option in nvidia-settings to fix this. I have taken a 
few screenshots:
https://imgur.com/a/EqRi1NT

Note that there are a lot more options on a desktop computer with a
PCI-E NVIDIA graphics card.

This post by an NVIDIA explains why PRIME Synchronization is critical to get 
rid of tearing on Optimus laptops and why nvidia-drm modeset=1 is necessary:
https://devtalk.nvidia.com/default/topic/957814/linux/prime-and-prime-synchronization/

I quote:
"The NVIDIA driver’s PRIME Synchronization support relies on DRM-KMS, which is 
disabled by default due to its current incompatibility with SLI. To enable it, 
run ‘sudo rmmod nvidia-drm; sudo modprobe nvidia-drm modeset=1’. In other 
words, load the nvidia-drm module with the parameter modeset=1."

Instead of reloading the module every time I need to use my laptop, I
just added that parameter to GRUB, which works but breaks Vulkan if gdm3
is used.

If I run:
$ xrandr --output eDP-1-1 --set "PRIME Synchronization" 1
without modeset enabled, the screen goes blank for a couple of seconds and 
GNOME is reloaded, but I still get tearing and according to xrandr it's still 
disabled:
$ xrandr --verbose
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
eDP-1-1 connected primary 1920x1080+0+0 (0x47) normal (normal left inverted 
right x axis y axis) 344mm x 194mm
[...]
PRIME Synchronization: 0 
supported: 0, 1
[...]

Of course, I get no tearing if modeset is enabled. I don't need to edit
my xorg.conf or anything.

Anyway the summary of this bug is "Vulkan not working if nvidia-
drm.modeset=1 is set and gdm3 is used (Optimus)", regardless of the
tearing issues.

If gdm3 is not affected then why does this ONLY happen with GDM?

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

Title:
  Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used
  (Optimus)

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

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

[Bug 1769372] Re: Prompt the user when the power button is pressed on a VM

[Norbert]

I do not understand about "confusion" and "intersection".
Will this fixed or not in Ubuntu 18.04 LTS?
Or GNOME will continue to reinvent of new unique interaction mechanisms between 
user and desktop?

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

Title:
  Prompt the user when the power button is pressed on a VM

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

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

[Bug 1715365] Re: gnome-session-check-accelerated crashed with SIGSEGV

[psychok7]

Happened to me as well in Ubuntu 18.04

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

Title:
  gnome-session-check-accelerated crashed with SIGSEGV

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

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

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

[Daniel van Vugt]

"VSync" and "PRIME Sync" are unrelated things. You need to ignore the
fact that they sound similar. You should be able to achieve perfect
VSync regardless of the "modeset" option. But it may be disabled by
default (by Nvidia) as alluded to earlier.

The "NV-GLX" error sounds expected... In a Wayland session you're using
Xwayland which doesn't yet connect to the Nvidia driver properly. So
avoid Wayland sessions in your case - they're not expected to work for
this.

So I think you need to:
  1. Don't use nvidia-drm.modeset=1
  2. Only use Xorg sessions.
  3. Now if tearing is your only problem then look in nvidia-settings for 
options to fix that. You might also find some xorg.conf options that help here: 
http://us.download.nvidia.com/XFree86/Linux-x86_64/390.25/README/xconfigoptions.html

gdm3 has nothing to do with any of this. It just launches X and the
Nvidia driver dictates what features are supported or not. If you want
the maximum features and performance from Nvidia then you usually need
to be using a Xorg session and not "modeset".

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

Title:
  Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used
  (Optimus)

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

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

[Bug 1629600] Re: Installed application from .deb does not appear unless Ubuntu is restarted

[dino99]

** Tags removed: yakkety

** Changed in: gnome-software (Ubuntu Zesty)
   Status: New => Invalid

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

Title:
  Installed application from .deb does not appear unless Ubuntu is
  restarted

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

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

[Bug 1770135] [NEW] Rhythmbox initially crashes when trying to play a song

[Simon P.]

Public bug reported:

With Ubuntu 18.04 and Rhythmbox 3.4.2 I have the following problem:
Rhythmbox initially crashes when I try to play a song. When I open it
again it plays the song as expected without crashing.

How to reproduce the bug: 
1) Open rhythmbox. 
2) Search for a song. Doublecklick it to play it. 
--> Rhythmbox will crash. Open rhythmbox again, it works without crashing now.
3) Close rhythmbox with the Ctrl + Q command. Start over at 1), bug appears 
again.

** Affects: rhythmbox (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Rhythmbox initially crashes when trying to play a song

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

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

[Bug 1768258] Re: Intermittend black screen - after login on bootup

[Simon P.]

I am experiencing the same problem with 18.04. After a failed login
attempt and the subsequent login, the green stays black and only the
mouse cursor is shown.

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

Title:
  Intermittend black screen - after login on bootup

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

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

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

[nastys]

I have also added WaylandEnabled=false to /etc/gdm3/custom.conf and
Vulkan still doesn't work. I also lost the option to log into Wayland
from the login screen.

@vanvugt Are you sure this isn't a bug in gdm3?

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

Title:
  Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used
  (Optimus)

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

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

[Bug 1165742] Re: Synctex plugin was not built in raring

[Simon McVittie]

** Changed in: dbus-python (Ubuntu)
   Status: New => Fix Released

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

Title:
  Synctex plugin was not built in raring

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-python/+bug/1165742/+subscriptions

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

[Bug 1765141] Re: [regression] Full screen white flash from time to time (Wayland and X11)

[Daniel van Vugt]

>From what I've seen of the gnome-shell/mutter/clutter/cogl source code,
they use white as a default colour. So if you see something that's all
white it means there's meant to be a texture or image there, but for
some reason it failed to render.

That might sound obvious and meaningless but it's not :)

Can you please attach output from this command?

  lspci -k

because I think this issue will be driver-specific.

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

** 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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1765141

Title:
  [regression] Full screen white flash from time to time (Wayland and
  X11)

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

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

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

[nastys]

nvidia-drm.modeset=1 is used for PRIME Sync. In a gist, it copies the
framebuffer from the dGPU to the iGPU without tearing. Without this,
VSync is not effective no matter what.

I have switched back to gdm3. In Xorg, OpenGL works as expected, with
the NVIDIA GPU (according to glxinfo), but Vulkan still doesn't work. In
Wayland, OpenGL is rendered by the Intel GPU and when I try to run
vulkan-smokeinfo I get:

Xlib:  extension "NV-GLX" missing on display ":0".
terminate called after throwing an instance of 'std::runtime_error'
  what():  VkResult -3 returned


I remember Ubuntu 17.10 wouldn't let me log in at all if nvidia-drm.modeset=1 
was enabled, but lightdm worked without issues (and it still does). Also SSDM 
is not affected either. Somehow gdm3 doesn't like this option...

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

Title:
  Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used
  (Optimus)

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

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

[Bug 1692394] Re: Speaker volume overlay sometimes jitters left/right slightly when pressing volume keys

[Daniel van Vugt]

There is a fix for the left/right jittering in
https://bugzilla.gnome.org/show_bug.cgi?id=782011

But yes those bugs should be deduplicated.

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

Title:
  Speaker volume overlay sometimes jitters left/right slightly when
  pressing volume keys

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

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

[Bug 1692394] Re: Speaker volume overlay sometimes jitters left/right slightly when pressing volume keys

[Michal Predotka]

I think the bug you're referencing is about blurriness from y position 
calculation.
I believe the upstream bug about left/right jittering is 
https://bugzilla.gnome.org/show_bug.cgi?id=772287

** Bug watch added: GNOME Bug Tracker #772287
   https://bugzilla.gnome.org/show_bug.cgi?id=772287

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

Title:
  Speaker volume overlay sometimes jitters left/right slightly when
  pressing volume keys

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

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

[Bug 1770082] Re: set-name doesn't work on boot, only with netplan apply

[Daniel Axtens]

** Description changed:

+ === systemd issue ===
+ 
+ Renaming devices doesn't seem to work.
+ 
+ If I create /etc/systemd/network/10-network.link with:
+ 
+ [Match]
+ MACAddress=52:54:00:c1:c9:bb
+ 
+ [Link]
+ Name=myiface3
+ 
+ I expect this to cause the device with that MAC address to be named to
+ myiface3. However, when I reboot, I instead see:
+ 
+ $ ip l
+ 1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ 2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
+ link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
+ 
+ The device is not renamed.
+ 
+ This link is pretty much identical to Example 2 in
+ https://www.freedesktop.org/software/systemd/man/systemd.link.html.
+ 
+ Oddly, while it doesn't work on reboot, it does work if you unbind the
+ device and rebind it as netplan apply does.
+ 
+ === Original Bug ==
+ 
  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.
  
  Say I take this 50-cloud-init.yaml file:
  
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3
  
  Say I change set-name to 'myiface3' and reboot. I expect that the device
  will be called myiface3 and brought up fine with dhcp. However, instead
  I see:
  
  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  
  The name has not been changed, and the device has not been brought up.
  
  If I run netplan apply however, I see the following:
  
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever
  
  So names are successfully changed with netplan apply.
  
  This seems to be some udev-related timing or priority issue that I'm
  still trying to hunt down.
  
  This breaks some forms of migration in certain cloud environments.

** Description changed:

  === systemd issue ===
  
  Renaming devices doesn't seem to work.
  
  If I create /etc/systemd/network/10-network.link with:
  
  [Match]
  MACAddress=52:54:00:c1:c9:bb
  
  [Link]
  Name=myiface3
  
- I expect this to cause the device with that MAC address to be named to
+ I expect this to cause the device with that MAC address to be renamed to
  myiface3. However, when I reboot, I instead see:
  
  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
- link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
- link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
+ link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
  
  The device is not renamed.
  
  This link is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.
  
  Oddly, while it doesn't work on reboot, it does work if you unbind the
  device and rebind it as netplan apply does.
  
  === Original Bug ==
  
  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.
  
  Say I take this 50-cloud-init.yaml file:
  
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # 

[Bug 1629600] Re: Installed application from .deb does not appear unless Ubuntu is restarted

[Hadrien]

Ubuntu 18.04, gnome-software 3.28.1

The application now appears in the "Installed" list, but with the wrong name 
and the wrong icon.
If I kill gnome-software and restart it, the application is not present anymore 
in the "Installed" list.
If I do a search in gnome-software, I can find the application again, with the 
right icon and with the "Installed" check tick (as it was the case for 17.10).

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

Title:
  Installed application from .deb does not appear unless Ubuntu is
  restarted

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

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

[Bug 1769845] Re: The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it

[i30817]

** Description changed:

  First, the obvious: the mouse experience out of the box (at least on
  ubuntu 17.04) is bad. I thought this was because Wayland is slightly
  slower on animations + mouse movement but although this is happening for
  some reason (memory leak, whatever) it's mostly because the setting to
  set the mouse 'Acceleration Profile' to 'adaptive' is hidden in the
  gnome-tweak tool and set to default 'linear'. I highly suspect that this
  setting was on by default on X11 synaptics, because my mouse experience
  became equal after i turned it to adaptive when it was inferior before.
  
  This is probably the cause of many of the mouse complaints on the ubuntu
  upgrade.
- 
- Another problem. Previously, on Xorg and synaptics i could use the right
- border area of my touchpad to simulate a middle mouse button click (that
- button doesn't exist on my keypad that has a structure like this:
- 
- (imagine # is non-breaking spaces here because i sure can't make them work 
here)
- ---
- |###|#|
- |###|#|
- |###|#|
- |###|#|
- |###|#|
- |###|#|
- |###|#|
- ---
- |##|##|
- ---
- 
- (i have a acer aspire 5738 if you want to see images on google)
- 
- The bottom are the left and right mouse buttons, the right column was
- for scrolling (another bug: doesn't actually work on nautilus at the
- moment but works on Firefox).
- 
- Previously taps on that scroll area could open firefox links, open tabs
- in nautilus etc, as per 3rd mouse button. Now that whole area only does
- scrolling  and i have to try the lottery of trying the 'three finger
- tap' on the central are to simulate mouse click (this doesn't work 80%
- of the time, and the other 15% is right clicking, that's two fingers.
- Even if it works, 3 fingers probably meanwhile moved the cursor when i
- lifted or tapped). I'd *really really* like it if i could configure
- those areas somehow, either graphically or on a config file.
- 
- Meanwhile i'm using ctrl+tap or ctrl+click but that requires two hands.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May  8 09:26:49 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-09-25 (590 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-05-06 (1 days ago)

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

Title:
  The Settings->Devices menu in gnome-shell Wayland doesn't provide
  enough configurations options, and there is no cfg file to work around
  it

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

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

[Bug 1769981] Re: Temporary screen freeze when coming back from screen standby

[Alberto Donato]

FTR this also happens on another PC, also with Intel card (different
model), also a fresh Bionic install

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

Title:
  Temporary screen freeze when coming back from screen standby

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

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

[Bug 1692394] Re: Speaker volume overlay sometimes jitters left/right slightly when pressing volume keys

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Confirmed

** Changed in: gnome-shell
   Importance: Unknown => 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/1692394

Title:
  Speaker volume overlay sometimes jitters left/right slightly when
  pressing volume keys

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

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