[Bug 1793496] Re: scaling changes when closing/re-opening the lid

2019-04-17 Thread Treviño
This has been fixed by

mutter (3.32.0-1ubuntu2) disco; urgency=medium

  * debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Don't invert the screen size when rotation is enabled (LP: #1822513)
- Remove unneeded cleanup changes
- Use xcb checked function to set scaling to catch errors
- Update screen size only after monitors modes have been derived
  (LP: #1822616)
- Trigger a monitors rebuild only if scale has changed (LP: #1823485)
- Only update UI scaling when output scaling is enabled (LP: #1822478)

 -- Marco Trevisan (Treviño)  Wed, 03 Apr 2019 19:19:59 -0400


I expect this is fixed by 
https://gitlab.gnome.org/GNOME/mutter/merge_requests/336 (issue 
https://gitlab.gnome.org/GNOME/mutter/issues/407)

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

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

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

Title:
  scaling changes when closing/re-opening the lid

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

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

[Bug 1811900] Re: SRU 3.28 latest git to bionic

2019-04-17 Thread Treviño
Both budgie and gnome-shell are in proposed now and this is verified for
mutter and both shell.

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-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/1811900

Title:
  SRU 3.28 latest git to bionic

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

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

[Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

2019-04-17 Thread El jinete sin cabeza
** Project changed: totem => gstreamer

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

Title:
  totem crashed with SIGTRAP in __glXSendError() from
  MakeContextCurrent()

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

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

[Bug 1825227] [NEW] gnome-calendar overcompensates time zone difference in web ics calendar

2019-04-17 Thread Erich Eickmeyer
Public bug reported:

Upon adding a web ics calendar (via Evolution due to Bug #1825224), the
events from this calendar were not properly time-compensated for my time
zone. While Evolution and Gnome Shell displayed the time of my events
properly, gnome-calendar displayed the events 7 hours in the past,
likely attempting to compensate for my time zone (GMT -7).

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-calendar 3.32.0-1
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: ubuntu:GNOME
Date: Wed Apr 17 11:47:17 2019
InstallationDate: Installed on 2019-04-15 (2 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-calendar
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco

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

Title:
  gnome-calendar overcompensates time zone difference in web ics
  calendar

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

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

[Bug 1825224] Re: gnome-calendar cannot add credentialed web ics calendars

2019-04-17 Thread Erich Eickmeyer
** Description changed:

  Upon attempting to add a calendar from outlook.com, I was greeted with a
  username/password dialog box. So, I entered my username (an email
  address in this case) and an app password I generated since I have two-
  factor authentication. The dialog box would go away, but the calendar
  would not be added.
  
  The only workaround was to add the calendar using Evolution, which
  properly accepted the username/app-password and added the calendar.
- Unfortunately, at that point, I discovered another bug which I will link
- here as soon as I get it filed.
+ Unfortunately, at that point, I discovered another bug (#185227).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-calendar 3.32.0-1
  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: ubuntu:GNOME
  Date: Wed Apr 17 11:39:29 2019
  InstallationDate: Installed on 2019-04-15 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  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-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  Upon attempting to add a calendar from outlook.com, I was greeted with a
  username/password dialog box. So, I entered my username (an email
  address in this case) and an app password I generated since I have two-
  factor authentication. The dialog box would go away, but the calendar
  would not be added.
  
  The only workaround was to add the calendar using Evolution, which
  properly accepted the username/app-password and added the calendar.
- Unfortunately, at that point, I discovered another bug (#185227).
+ Unfortunately, at that point, I discovered bug #185227.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-calendar 3.32.0-1
  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: ubuntu:GNOME
  Date: Wed Apr 17 11:39:29 2019
  InstallationDate: Installed on 2019-04-15 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  gnome-calendar cannot add credentialed web ics calendars

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

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

[Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

2019-04-17 Thread El jinete sin cabeza
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143

** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues #143
   https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143

** Description changed:

- https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
+ https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 
(DUPLICATE OF 
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143 )
  https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
  https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
  
  ---
  
  Backtrace goes through:
  
  totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer
  (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd
  (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
  (MakeContextCurrent) -> Xlib (XError)
  
  Ubuntu bug doesn't say anything about what's the use-case / when this
  happens and whether it's reproducible (is it e.g. timing related), it
  seems just some random crash that Apport collects.
  
  In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell 
that it was given invalid/bad context.  Corresponding Mesa code:
  ---
     if (gc) {
    /* Attempt to bind the context.  We do this before mucking with
     * gc and __glXSetCurrentContext to properly handle our state in
     * case of an error.
     *
     * If an error occurs, set the Null context since we've already
     * blown away our old context.  The caller is responsible for
     * figuring out how to handle setting a valid context.
     */
    if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
   __glXSetCurrentContextNull();
   __glXUnlock();
   __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
  False);
   return GL_FALSE;
    }
  ---
  
  I.e. bug is in what is given to Mesa, not what Mesa does.
  
  -> NOTOURBUG
  
  To me it looks something that could happen when Totem is exiting, gst-
  vaapi is trying to use resources that have already been freed, and X
  catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects()
  ask libglvnd to do CommonMakeCurrent().
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 11:26:51 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-05-04 (323 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 5
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
  Title: totem crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** No longer affects: gstreamer

** Also affects: totem via
   https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
   Importance: Unknown
   Status: Unknown

** Description changed:

- https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 
(DUPLICATE OF 
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143 )
+ https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 DUPLICATE 
OF:
+ https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
+ 
  https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
  https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
  
  ---
  
  Backtrace goes through:
  
  totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer
  (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd
  (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
  (MakeContextCurrent) -> Xlib (XError)
  
  Ubuntu bug doesn't say anything about what's the use-case / when this
  happens and whether it's reproducible (is it e.g. timing related), it
  seems just some random crash that Apport collects.
  
  In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell 
that it was given invalid/bad context.  Corresponding Mesa code:
  ---
     if (gc) {
    /* Attempt to bind the context.  We do this before mucking with
     * gc and __glXSetCurrentContext to properly handle our state in
     * case of an error.
     *
     * If an error occurs, set the Null context since we've already
    

[Bug 1825224] [NEW] gnome-calendar cannot add credentialed web ics calendars

2019-04-17 Thread Erich Eickmeyer
Public bug reported:

Upon attempting to add a calendar from outlook.com, I was greeted with a
username/password dialog box. So, I entered my username (an email
address in this case) and an app password I generated since I have two-
factor authentication. The dialog box would go away, but the calendar
would not be added.

The only workaround was to add the calendar using Evolution, which
properly accepted the username/app-password and added the calendar.
Unfortunately, at that point, I discovered bug #185227.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-calendar 3.32.0-1
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: ubuntu:GNOME
Date: Wed Apr 17 11:39:29 2019
InstallationDate: Installed on 2019-04-15 (2 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-calendar
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco

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

Title:
  gnome-calendar cannot add credentialed web ics calendars

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

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

[Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

2019-04-17 Thread Steve Langasek
In the time it took to try to port from aptdaemon to packagekit,
packagekit has gone dead upstream, and we have been recommended not to
port further work to it.

Julian is now looking at providing an aptd as part of apt upstream that
is fit for purpose.

I am unsubscribing ubuntu-archive from this bug.

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

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

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

[Bug 486154] Re: System beep broken in Karmic despite heroic efforts to fix it

2019-04-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux-lts-xenial (Ubuntu)
   Status: New => Confirmed

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

Title:
  System beep broken in Karmic despite heroic efforts to fix it

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

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

[Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

2019-04-17 Thread Bug Watch Updater
** Changed in: gstreamer
   Status: Unknown => Fix Released

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

Title:
  totem crashed with SIGTRAP in __glXSendError() from
  MakeContextCurrent()

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

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

[Bug 1822254] Re: Can't drag and drop files to Desktop on Disco 19.04 beta

2019-04-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Can't drag and drop files to Desktop on Disco 19.04 beta

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

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

[Bug 1825209] Re: Automatic suspend delay is at least 15 mins

2019-04-17 Thread Mate Varga
*** This bug is a duplicate of bug 1825208 ***
https://bugs.launchpad.net/bugs/1825208

** This bug has been marked a duplicate of bug 1825208
   Automatic suspend delay is at least 15 mins

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

Title:
  Automatic suspend delay is at least 15 mins

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

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

[Bug 1805444] Re: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend

2019-04-17 Thread blszyn
Does it mean that gdm will show an option to start Gnome on Wayland when
using Nvidia binary drivers?

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

Title:
  [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice
  backend

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

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

[Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

2019-04-17 Thread Pavarin Bhandtivej
Verified on bionic that the proposed update (mutter version
3.28.3+git20190124-0ubuntu18.04.2) fixes the issue.

Thank you everyone who has worked on the issue. Your hard work is much
appreciated.

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

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

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

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

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

[Bug 1811900] Re: SRU 3.28 latest git to bionic

2019-04-17 Thread fossfreedom
confirmed that the new mutter also tries to uplift the budgie-desktop
version.

Tested the new mutter with the 4 budgie SRU's and all is ok.

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

Title:
  SRU 3.28 latest git to bionic

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

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

[Bug 1824886] Re: Battery level stuck at 100% and Estimating...

2019-04-17 Thread Mike Kapushin
I booted from the LiveCD 19.04. Although charging status is indicated
the other way round, percentages are correct and decrease with battery
discharge.

How tired I am of this...
Ubuntu does not work normally on any of the last ten computers...

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

Title:
  Battery level stuck at 100% and Estimating...

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

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

[Bug 1821427] Re: gnome-shell crashed with signal 5 when closing evolution, logging "The program 'gnome-shell' received an X Window System error.\nThis probably reflects a bug in the program.\nThe err

2019-04-17 Thread Daniel van Vugt
Unless you can think of anything that's special or unusual about your
system that triggers this bug?

It took a while, but we now are getting other reports of this same crash via:
https://errors.ubuntu.com/problem/e622155ae760525198ab9d778ae25686a5e55978

** Description changed:

+ https://errors.ubuntu.com/problem/e622155ae760525198ab9d778ae25686a5e55978
+ 
  Had this happen a few times now, where closing the main evolution window
  (last visible window on desktop) results in a gnome-shell crash (see bug
  1821262)
  
  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 22 18:49:10 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-09-26 (177 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/usr/bin/zsh
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/usr/bin/zsh
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
-  () at /usr/lib/x86_64-linux-gnu/libX11.so.6
-  () at /usr/lib/x86_64-linux-gnu/libX11.so.6
-  _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
-  XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
-  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
+  () at /usr/lib/x86_64-linux-gnu/libX11.so.6
+  () at /usr/lib/x86_64-linux-gnu/libX11.so.6
+  _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
+  XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
+  () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to disco on 2019-03-11 (11 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  separator:

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

Title:
  gnome-shell crashed with signal 5 when closing evolution, logging "The
  program 'gnome-shell' received an X Window System error.\nThis
  probably reflects a bug in the program.\nThe error was 'BadWindow
  (invalid Window parameter)'.\n  (Details: serial 333851 error_code 3
  r"

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

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

[Bug 1768137] Re: Ubuntu doesn't remember my monitor layout after logout or reboot

2019-04-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Ubuntu doesn't remember my monitor layout after logout or reboot

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

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

[Bug 1768137] Re: Ubuntu doesn't remember my monitor layout after logout or reboot

2019-04-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Ubuntu doesn't remember my monitor layout after logout or reboot

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

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

[Bug 1768137] Re: Ubuntu doesn't remember my monitor layout after logout or reboot

2019-04-17 Thread Daniel van Vugt
** Also affects: mutter (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Ubuntu doesn't remember my monitor layout after logout or reboot

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

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

[Bug 1820423] Re: monitors.xml is not parsed or applied correctly during login after reboot or shutdown

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

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 1768137, 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 1768137
   Ubuntu doesn't remember my monitor layout after logout or reboot

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

Title:
  monitors.xml is not parsed or applied correctly during login after
  reboot or shutdown

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

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

[Bug 1825004] Re: Ubuntu loses display settings on reboot, corrupts displays

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

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 1768137, 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 1768137
   Ubuntu doesn't remember my monitor layout after logout or reboot

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

Title:
  Ubuntu loses display settings on reboot, corrupts displays

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

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

[Bug 1821427] Re: gnome-shell crashed with signal 5 when closing evolution, logging "The program 'gnome-shell' received an X Window System error.\nThis probably reflects a bug in the program.\nThe err

2019-04-17 Thread Daniel van Vugt
When you see X11 code in the gnome-shell process of a Wayland session
that's nothing unusual. It just means some X11 app is running, talking
to Xwayland and gnome-shell (which is both the Wayland display server
AND the X11 window manager in this case).

Since this bug is about a particular "BadWindow (invalid Window
parameter)", maybe it is specific to Evolution?...

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

Title:
  gnome-shell crashed with signal 5 when closing evolution, logging "The
  program 'gnome-shell' received an X Window System error.\nThis
  probably reflects a bug in the program.\nThe error was 'BadWindow
  (invalid Window parameter)'.\n  (Details: serial 333851 error_code 3
  r"

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

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

[Bug 1811900] Re: SRU 3.28 latest git to bionic

2019-04-17 Thread Mathew Hodson
** Changed in: mutter (Ubuntu)
   Status: Invalid => Fix Released

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

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

Title:
  SRU 3.28 latest git to bionic

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

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

[Bug 1805444] Re: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend

2019-04-17 Thread Daniel van Vugt
No, not directly, but kind of :)

The option to start a Wayland session is enabled by adding:

  nvidia-drm.modeset=1

to your kernel command line.

Secondly, mutter's Wayland backend needs to be found to WORK with it. If
it doesn't work (this bug), then mutter will hide the Wayland option
before you ever see the login screen.

So you should:

  1. Add nvidia-drm.modeset=1 to your kernel command line; and
  2. Either wait for this bug to be fixed in 18.04 or just use a later Ubuntu 
release which doesn't have 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/1805444

Title:
  [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice
  backend

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

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

[Bug 1817223] Re: [disco-proposed] The list of applications in Ubuntu Software is empty

2019-04-17 Thread Robert Ancell
Closing the gnome-software tasks as we downgraded.

** No longer affects: gnome-software (Ubuntu)

** No longer affects: gnome-software (Ubuntu Disco)

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

Title:
  [disco-proposed] The list of applications in Ubuntu Software is empty

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

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

[Bug 1820423] Re: monitors.xml is not parsed or applied correctly during login after reboot or shutdown

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

** This bug is no longer a duplicate of bug 1768137
   Ubuntu doesn't remember my monitor layout after logout or reboot
** This bug has been marked a duplicate of bug 1292398
   Second screen position isn't saved from one session to another

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

Title:
  monitors.xml is not parsed or applied correctly during login after
  reboot or shutdown

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

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

[Bug 1825004] Re: Ubuntu loses display settings on reboot, corrupts displays

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

** This bug is no longer a duplicate of bug 1768137
   Ubuntu doesn't remember my monitor layout after logout or reboot
** This bug has been marked a duplicate of bug 1292398
   Second screen position isn't saved from one session to another

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

Title:
  Ubuntu loses display settings on reboot, corrupts displays

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

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

[Bug 1768137] Re: Ubuntu doesn't remember my monitor layout after logout or reboot

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

Actually, let's use bug 1292398 since that's the one most users are
finding.

** This bug has been marked a duplicate of bug 1292398
   Second screen position isn't saved from one session to another

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

Title:
  Ubuntu doesn't remember my monitor layout after logout or reboot

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

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

[Bug 1811900] Re: SRU 3.28 latest git to bionic

2019-04-17 Thread Daniel van Vugt
Now clarified statuses properly :)

** Also affects: mutter (Ubuntu Disco)
   Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
   Status: Fix Released

** Also affects: gnome-shell (Ubuntu Disco)
   Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
   Status: Fix Released

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

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

** Changed in: gnome-shell (Ubuntu Disco)
   Status: Fix Released => Invalid

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

** Changed in: gnome-shell (Ubuntu Disco)
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

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

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

** Changed in: mutter (Ubuntu Disco)
 Assignee: Marco Trevisan (Treviño) (3v1n0) => (unassigned)

** No longer affects: gnome-shell (Ubuntu Cosmic)

** No longer affects: mutter (Ubuntu Cosmic)

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

Title:
  SRU 3.28 latest git to bionic

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

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

[Bug 1822753] Re: /usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref

2019-04-17 Thread Bug Watch Updater
** Changed in: gedit
   Status: New => Fix Released

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

Title:
  
/usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref

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

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

[Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

2019-04-17 Thread Martin Wimpress
** Changed in: ubuntu-mate-welcome (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: ubuntu-mate-welcome (Ubuntu)
   Status: New => Opinion

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

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

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

[Bug 1825270] Re: /usr/bin/gnome-shell:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_array:g_log_structured_standard

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

** This bug has been marked a duplicate of bug 1821427
   gnome-shell crashed with signal 5 when closing evolution, logging "The 
program 'gnome-shell' received an X Window System error.\nThis probably 
reflects a bug in the program.\nThe error was 'BadWindow (invalid Window 
parameter)'.\n  (Details: serial 333851 error_code 3 r"

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

Title:
  /usr/bin/gnome-
  
shell:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_array:g_log_structured_standard

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

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

[Bug 1825270] [NEW] /usr/bin/gnome-shell:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_array:g_log_structured_standard

2019-04-17 Thread errors.ubuntu.com bug bridge
*** This bug is a duplicate of bug 1821427 ***
https://bugs.launchpad.net/bugs/1821427

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.32.0+git20190410-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/e622155ae760525198ab9d778ae25686a5e55978 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: disco

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

Title:
  /usr/bin/gnome-
  
shell:5:_g_log_abort:g_log_writer_default:g_log_structured_array:g_log_structured_array:g_log_structured_standard

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

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

[Bug 1821427] Re: gnome-shell crashed with signal 5 when closing evolution, logging "The program 'gnome-shell' received an X Window System error.\nThis probably reflects a bug in the program.\nThe err

2019-04-17 Thread 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/1821427

Title:
  gnome-shell crashed with signal 5 when closing evolution, logging "The
  program 'gnome-shell' received an X Window System error.\nThis
  probably reflects a bug in the program.\nThe error was 'BadWindow
  (invalid Window parameter)'.\n  (Details: serial 333851 error_code 3
  r"

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

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

[Bug 1821427] Re: gnome-shell crashed with signal 5 when closing evolution, logging "The program 'gnome-shell' received an X Window System error.\nThis probably reflects a bug in the program.\nThe err

2019-04-17 Thread Daniel van Vugt
** 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/1821427

Title:
  gnome-shell crashed with signal 5 when closing evolution, logging "The
  program 'gnome-shell' received an X Window System error.\nThis
  probably reflects a bug in the program.\nThe error was 'BadWindow
  (invalid Window parameter)'.\n  (Details: serial 333851 error_code 3
  r"

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

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

[Bug 1768137] Re: Ubuntu doesn't remember my monitor layout after logout or reboot

2019-04-17 Thread Daniel van Vugt
Everyone please ensure you are actually logging in again too :)

If you're only concerned about the login screen then that is bug
1760849.

** Tags added: multimonitor

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

Title:
  Ubuntu doesn't remember my monitor layout after logout or reboot

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

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

[Bug 509661] Re: Screen layout not remembered

2019-04-17 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Screen layout not remembered

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

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

[Bug 1580451] Re: mutter does not remember position of extra displays

2019-04-17 Thread Daniel van Vugt
Tim,

Do you see the same bug in 18.04 or later?

** Description changed:

+ https://bugzilla.gnome.org/show_bug.cgi?id=747529
+ 
  If you have a laptop where you irregularly use the external monitor,
  mutter will forget the position when you turn off/on the monitor.

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

Title:
  mutter does not remember position of extra displays

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

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

[Bug 1825197] Re: system unresponse for several seconds a couple of times per hour

2019-04-17 Thread Daniel van Vugt
Thanks for the bug report. I have encountered the same problems myself
this week when stress testing parts of gnome-shell. But those parts and
the cause might be different to yours. So please run:

  apport-collect 1825197

to send us more information about the system.


** Tags added: cosmic

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

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

Title:
  system unresponse for several seconds a couple of times per hour
  [Attempting to call back into JSAPI during the sweeping phase of
  GC...]

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

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

[Bug 1825197] Re: system unresponse for several seconds a couple of times per hour

2019-04-17 Thread Daniel van Vugt
As far as I can tell, the common error (from gjs):

Attempting to call back into JSAPI during the sweeping phase of GC. This
is most likely caused by not destroying a Clutter actor or Gtk+ widget
with ::destroy signals connected, but can also be caused by using the
destroy(), dispose(), or remove() vfuncs. Because it would crash the
application, it has been blocked and the JS callback not invoked.

is caused by a type of mistake that has been made in JavaScript
locations. And that mistake is common, in multiple locations in gnome-
shell and its extensions. Although I don't yet understand what that
mistake looks like in code :(

** Summary changed:

- system unresponse for several seconds a couple of times per hour 
+ system unresponse for several seconds a couple of times per hour [Attempting 
to call back into JSAPI during the sweeping phase of GC...]

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

Title:
  system unresponse for several seconds a couple of times per hour
  [Attempting to call back into JSAPI during the sweeping phase of
  GC...]

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

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

[Bug 1824588] Re: With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input

2019-04-17 Thread Erick Brunzell
I will follow up ASAP. The plot continues to thicken. I tried a
different set of hardware today with a B43 chipset and it didn't seem to
be effected. But that board has only DVI and VGA outputs whereas the
effected board with a G43 chipset has DVI and HDMI. I'd been using HDMI
so now I ran another range of tests using DVI on the effected board and
was unable to reproduce.

So this appears to effect a very selective subset of 10 to 12 year old
hardware. Must be Intel X4500 graphics with HDMI connection and possibly
only the G43 chipset. So it's the absolute corneriest of corner issues
I've ever encountered. And the workaround couldn't be any simpler - just
remove the "quiet splash" boot parameter and all seems well (both boot
to and logout to gdm3 screen).

BTW ASAP may be rather slow in coming because I have a few medical
procedures scheduled in the next few weeks.

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

Title:
  With AutomaticLogin enabled, logging out lands me on a black screen
  that's unresponsive to any keyboard input

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

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

[Bug 1824588] Re: With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input [gnome-shell: Failed to initialize accelerated iGPU/dGPU framebuffer sha

2019-04-17 Thread Daniel van Vugt
This problem is probably related to:

"Following Mutter's 3.32.1 release, meanwhile, the developers have now
hard-enforced a requirement that graphics drivers on the system either
support OpenGL 2.1 or OpenGL ES 2.0 as a minimum."

[https://www.phoronix.com/scan.php?page=news_item=GNOME-Shell-
Mutter-3.32.1]

Although Mesa offers software rendering which supports newer OpenGL.
Therefore gdm3 and mutter *should* be detecting that the GPU is too old
and falling back. It's a semi-regular problem though, that gdm3 and
mutter fail to fall back reliably and the login screen never appears.



** Summary changed:

- With AutomaticLogin enabled, logging out lands me on a black screen that's 
unresponsive to any keyboard input
+ With AutomaticLogin enabled, logging out lands me on a black screen that's 
unresponsive to any keyboard input [gnome-shell: Failed to initialize 
accelerated iGPU/dGPU framebuffer sharing: No matching EGL configs]

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

** Changed in: gdm3 (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/1824588

Title:
  With AutomaticLogin enabled, logging out lands me on a black screen
  that's unresponsive to any keyboard input [gnome-shell: Failed to
  initialize accelerated iGPU/dGPU framebuffer sharing: No matching EGL
  configs]

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

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

[Bug 1292398] Re: Second screen position isn't saved from one session to another

2019-04-17 Thread Daniel van Vugt
OK, I give in... Since this bug is so popular and I can't find any
explicit code fix we can reopen this one. Unfortunately I still cannot
reproduce this bug myself.

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

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

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

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

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

** Tags removed: artful
** Tags added: bionic

** Tags added: cosmic

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

Title:
  Second screen position isn't saved from one session to another

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

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

[Bug 1821427] Re: gnome-shell crashed with signal 5 when closing evolution, logging "The program 'gnome-shell' received an X Window System error.\nThis probably reflects a bug in the program.\nThe err

2019-04-17 Thread Joe Barnett
Not sure if related, but I do run under wayland (weird that it looks
like an X11 error then, especially as evolution runs wayland native?),
with fractional zooming on my laptop panel @ 175% and usually have an
external, lower resolution screen at 100% scaling.  Evolution is usually
the first app i open and stays open throughout my session, so has
usually been running for days before being closed (and killing the
session) -- but sometimes closing it is fine.  Haven't seen any other
app trigger it.

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

Title:
  gnome-shell crashed with signal 5 when closing evolution, logging "The
  program 'gnome-shell' received an X Window System error.\nThis
  probably reflects a bug in the program.\nThe error was 'BadWindow
  (invalid Window parameter)'.\n  (Details: serial 333851 error_code 3
  r"

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

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

[Bug 1811540] Re: gvfsd-trash crashed with SIGSEGV in trash_item_invoke_closure()

2019-04-17 Thread Walter Lapchynski
Changed to incomplete since not replicable. If the original poster could
retest and if it's still a problem, provide clear steps and conditions
to reproduce, that would be great. Thanks!

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

** Changed in: gvfs (Ubuntu)
   Status: Invalid => Incomplete

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

Title:
  gvfsd-trash crashed with SIGSEGV in trash_item_invoke_closure()

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

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

[Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

2019-04-17 Thread eric
*** This bug is a duplicate of bug 520546 ***
https://bugs.launchpad.net/bugs/520546

The same thing just happened to me after an update.

Running `sudo kbd_mode -s` fixed it.

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1508146/+subscriptions

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

[Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

2019-04-17 Thread Patrizio Bekerle
*** This bug is a duplicate of bug 520546 ***
https://bugs.launchpad.net/bugs/520546

I also just had the same issue on KDE Neon after an update.
Running `sudo kbd_mode -s` also fixed it for me.
Thank you very much, Eric!

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1508146/+subscriptions

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

Re: [Bug 1811900] Re: SRU 3.28 latest git to bionic

2019-04-17 Thread Iain Lane
On Tue, Apr 16, 2019 at 09:30:52PM -, Steve Langasek wrote:
> If the mutter package is incompatible with the budgie package currently
> in bionic, then this is verification-failed.  A new mutter upload will
> be required to add Breaks: against the version of budgie that it's
> incompatible with.

That sounds like the right thing to do. I'll upload with that.

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  SRU 3.28 latest git to bionic

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

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

[Bug 1824886] Re: Battery charge is 100% stuck and Estimating...

2019-04-17 Thread Mike Kapushin
** Summary changed:

- Battery applet does not display battery charge.
+ Battery charge is 100% stuck and Estimating...

** Summary changed:

- Battery charge is 100% stuck and Estimating...
+ Battery level stuck at 100% and Estimating...

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

Title:
  Battery level stuck at 100% and Estimating...

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

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

[Bug 1800043] Re: nautilus cannot write on nfs file share base dir

2019-04-17 Thread Sebastien Bacher
Upstream asked for extra details
'Can you please provide gio info /media/feydreva/download and gio info -f 
/media/feydreva/download outputs?'

Could you provide those info?

Is the destination folder a symlink (like in
https://gitlab.gnome.org/GNOME/nautilus/issues/976)?

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #976
   https://gitlab.gnome.org/GNOME/nautilus/issues/976

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

Title:
  nautilus cannot write on nfs file share base dir

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

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

[Bug 1734095] Re: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]

2019-04-17 Thread Colin Law
Log attached, this is from the Disco system

** Attachment added: "journalctl.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1734095/+attachment/5256487/+files/journalctl.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/1734095

Title:
  Software & Updates not showing authorization popup [gnome-shell[N]:
  pushModal: invocation of begin_modal failed]

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

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

[Bug 1825126] [NEW] Shell dialog shadows are clipped on the top and left edges

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

Shell dialog shadows are clipped on the top and left edges.

Although the shadow only seems to exist in the Yaru theme, not upstream,
I can also fix the bug by removing:

this._dialog.set_offscreen_redirect(Clutter.OffscreenRedirect.ALWAYS);

from gnome-shell/js/ui/dialog.js

ProblemType: Bug
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
Date: Wed Apr 17 16:21:25 2019
DisplayManager: gdm3
InstallationDate: Installed on 2018-12-04 (134 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Medium
 Assignee: Daniel van Vugt (vanvugt)
 Status: New

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


** Tags: amd64 apport-bug disco third-party-packages visual-quality

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

Title:
  Shell dialog shadows are clipped on the top and left edges

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

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

[Bug 1825126] Re: Shell dialog shadows are clipped on the top and left edges

2019-04-17 Thread Daniel van Vugt
Screenshot

** Attachment added: "missing_shadows.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825126/+attachment/5256486/+files/missing_shadows.png

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

** Attachment removed: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825126/+attachment/5256483/+files/GsettingsChanges.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825126/+attachment/5256485/+files/ProcEnviron.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825126/+attachment/5256484/+files/ProcCpuinfoMinimal.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/1825126

Title:
  Shell dialog shadows are clipped on the top and left edges

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

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

[Bug 1825066] Re: gsd-xsettings have tons of error in syslog

2019-04-17 Thread Sebastien Bacher
Thank you for your bug report. Can you add your journalctl log from the
session? Do you use the default Ubuntu session? What monitors?

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

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

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

Title:
  gsd-xsettings have tons of error in syslog

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

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

[Bug 1824699] Re: gnome-calendar pango critical

2019-04-17 Thread Sebastien Bacher
can you maybe figure out/try to remember what setting you had which
created the issue?

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

Title:
  gnome-calendar pango critical

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

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

[Bug 1825004] Re: Ubuntu loses display settings on reboot, corrupts displays

2019-04-17 Thread Sebastien Bacher
Thank you for your bug report, that looks a bit similar to bug #1820423

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

Title:
  Ubuntu loses display settings on reboot, corrupts displays

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

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

[Bug 1825085] Re: [Ubuntu 18.10] Ctrl+F search does not work

2019-04-17 Thread Sebastien Bacher
Thank you for your bug report, that's an upstream issue and should
ideally be reported on https://gitlab.gnome.org/GNOME/file-
roller/issues/

** Changed in: file-roller (Ubuntu)
   Importance: Undecided => Low

** Changed in: file-roller (Ubuntu)
   Status: New => Confirmed

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

Title:
  [Ubuntu 18.10] Ctrl+F search does not work

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

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

[Bug 1825006] Re: snapp apps not showing in software center

2019-04-17 Thread Sebastien Bacher
Thank you for your bug report. Where are they not listed? Could you make a 
screenshot showing the issue?
What version of Ubuntu & gnome-software do you use?

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

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

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

Title:
  snapp apps not showing in software center

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

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

[Bug 1803319] Re: GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled

2019-04-17 Thread Michael Thayer
Seemed to work when I tested it yesterday (I do not always have access
to the test set-up).  So assuming fixed.  Thank you.

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

Title:
  GNOME Shell task bar menus not updated with external monitor primary
  and laptop screen fractionally scaled

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

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

[Bug 1824886] Re: Battery level stuck at 100% and Estimating...

2019-04-17 Thread Sebastien Bacher
upstream https://bugzilla.kernel.org/show_bug.cgi?id=201351 also

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

Title:
  Battery level stuck at 100% and Estimating...

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

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

[Bug 1824886] Re: Battery level stuck at 100% and Estimating...

2019-04-17 Thread Sebastien Bacher
Looking to comment #20 it looks like a kernel issue, the /sys entry tell
the charge level is 100%

Is /sys/class/power_supply/BAT0/status also telling you 'charging' when
it's on battery?

Googling a bit I found https://bbs.archlinux.org/viewtopic.php?id=238944 which 
states it started being buggy on the 4.17 kernel, which would explain why it 
works on the 'old 4.15' kernel you have with mint.
The comment also state that it's fixed in kernel 4.20.13, could you try on a 
19.04 liveCD to see if the new kernel there makes it work for you?

** Bug watch added: Linux Kernel Bug Tracker #201351
   https://bugzilla.kernel.org/show_bug.cgi?id=201351

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

Title:
  Battery level stuck at 100% and Estimating...

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

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

[Bug 1825006] Re: snapp apps not showing in software center

2019-04-17 Thread Sebastien Bacher
Where did you click to get the list from the first screenshot?

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

Title:
  snapp apps not showing in software center

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

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

[Bug 1825006] Re: snapp apps not showing in software center

2019-04-17 Thread Larika
I use ubuntu 18.04.2 LTS, with default gnome-desktop.

gnome-software 3.28.1

https://snag.gy/COt4sS.jpg

https://snag.gy/SOIjVx.jpg

As you can see, the postman snap is not visible in the list(first
picture) but is visible if I search it manually(second picture).

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

Title:
  snapp apps not showing in software center

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

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

[Bug 1824886] Re: Battery level stuck at 100% and Estimating...

2019-04-17 Thread Mike Kapushin
** Attachment added: "Снимок экрана от 2019-04-17 13-56-17.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1824886/+attachment/5256524/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202019-04-17%2013-56-17.png

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

Title:
  Battery level stuck at 100% and Estimating...

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

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

[Bug 1824886] Re: Battery level stuck at 100% and Estimating...

2019-04-17 Thread Mike Kapushin
** Attachment added: "Снимок экрана от 2019-04-17 13-55-42.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1824886/+attachment/5256523/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202019-04-17%2013-55-42.png

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

Title:
  Battery level stuck at 100% and Estimating...

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

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

[Bug 1824886] Re: Battery level stuck at 100% and Estimating...

2019-04-17 Thread Mike Kapushin
** Attachment added: "Снимок экрана от 2019-04-17 13-58-31.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1824886/+attachment/5256527/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202019-04-17%2013-58-31.png

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

Title:
  Battery level stuck at 100% and Estimating...

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

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

[Bug 1824886] Re: Battery level stuck at 100% and Estimating...

2019-04-17 Thread Mike Kapushin
** Attachment added: "Снимок экрана от 2019-04-17 13-57-22.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1824886/+attachment/5256525/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202019-04-17%2013-57-22.png

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

Title:
  Battery level stuck at 100% and Estimating...

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

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

[Bug 1824886] Re: Battery level stuck at 100% and Estimating...

2019-04-17 Thread Mike Kapushin
** Attachment added: "Снимок экрана от 2019-04-17 13-58-05.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1824886/+attachment/5256526/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202019-04-17%2013-58-05.png

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

Title:
  Battery level stuck at 100% and Estimating...

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

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

[Bug 1824886] Re: Battery level stuck at 100% and Estimating...

2019-04-17 Thread Mike Kapushin
** Attachment added: "Снимок экрана от 2019-04-17 13-59-02.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1824886/+attachment/5256528/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202019-04-17%2013-59-02.png

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

Title:
  Battery level stuck at 100% and Estimating...

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

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

[Bug 1691908] Re: fstab binds appear as mounts (x-gvfs-hide is being ignored)

2019-04-17 Thread Mikko Rantalainen
This bug is still relevant for Bionic. Any info about possible backport?

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

Title:
  fstab binds appear as mounts (x-gvfs-hide is being ignored)

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

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

[Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

2019-04-17 Thread El jinete sin cabeza
** Changed in: mesa (Ubuntu)
   Status: New => Invalid

** Description changed:

- https://bugs.freedesktop.org/show_bug.cgi?id=110452
+ https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
  https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
  
  ---
  
  totem crashed with signal 5
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 11:26:51 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-05-04 (323 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 5
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
  Title: totem crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Description changed:

  https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
  https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
  
  ---
  
- totem crashed with signal 5
+ Backtrace goes through:
+ 
+ totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer
+ (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd
+ (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
+ (MakeContextCurrent) -> Xlib (XError)
+ 
+ Ubuntu bug doesn't say anything about what's the use-case / when this
+ happens and whether it's reproducible (is it e.g. timing related), it
+ seems just some random crash that Apport collects.
+ 
+ In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell 
that it was given invalid/bad context.  Corresponding Mesa code:
+ ---
+if (gc) {
+   /* Attempt to bind the context.  We do this before mucking with
+* gc and __glXSetCurrentContext to properly handle our state in
+* case of an error.
+*
+* If an error occurs, set the Null context since we've already
+* blown away our old context.  The caller is responsible for
+* figuring out how to handle setting a valid context.
+*/
+   if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
+  __glXSetCurrentContextNull();
+  __glXUnlock();
+  __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
+ False);
+  return GL_FALSE;
+   }
+ ---
+ 
+ I.e. bug is in what is given to Mesa, not what Mesa does.
+ 
+ -> NOTOURBUG
+ 
+ 
+ To me it looks something that could happen when Totem is exiting, gst-vaapi 
is trying to use resources that have already been freed, and X catching that 
when Gstreamer gstvaapitexture_glx.c::destroy_objects() ask libglvnd to do 
CommonMakeCurrent().
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 11:26:51 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-05-04 (323 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 5
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
  Title: totem crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

** No longer affects: gstreamer (Ubuntu)

** Also affects: gstreamer-vaapi (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  totem crashed with SIGTRAP in __glXSendError() from
  MakeContextCurrent()

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com

[Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

2019-04-17 Thread El jinete sin cabeza
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153

** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues #153
   https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153

** Also affects: gstreamer via
   https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
   Importance: Unknown
   Status: Unknown

** Description changed:

+ https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
  https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
  https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
  
  ---
  
  Backtrace goes through:
  
  totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer
  (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd
  (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
  (MakeContextCurrent) -> Xlib (XError)
  
  Ubuntu bug doesn't say anything about what's the use-case / when this
  happens and whether it's reproducible (is it e.g. timing related), it
  seems just some random crash that Apport collects.
  
  In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell 
that it was given invalid/bad context.  Corresponding Mesa code:
  ---
-if (gc) {
-   /* Attempt to bind the context.  We do this before mucking with
-* gc and __glXSetCurrentContext to properly handle our state in
-* case of an error.
-*
-* If an error occurs, set the Null context since we've already
-* blown away our old context.  The caller is responsible for
-* figuring out how to handle setting a valid context.
-*/
-   if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
-  __glXSetCurrentContextNull();
-  __glXUnlock();
-  __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
- False);
-  return GL_FALSE;
-   }
+    if (gc) {
+   /* Attempt to bind the context.  We do this before mucking with
+    * gc and __glXSetCurrentContext to properly handle our state in
+    * case of an error.
+    *
+    * If an error occurs, set the Null context since we've already
+    * blown away our old context.  The caller is responsible for
+    * figuring out how to handle setting a valid context.
+    */
+   if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
+  __glXSetCurrentContextNull();
+  __glXUnlock();
+  __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
+ False);
+  return GL_FALSE;
+   }
  ---
  
  I.e. bug is in what is given to Mesa, not what Mesa does.
  
  -> NOTOURBUG
  
- 
- To me it looks something that could happen when Totem is exiting, gst-vaapi 
is trying to use resources that have already been freed, and X catching that 
when Gstreamer gstvaapitexture_glx.c::destroy_objects() ask libglvnd to do 
CommonMakeCurrent().
+ To me it looks something that could happen when Totem is exiting, gst-
+ vaapi is trying to use resources that have already been freed, and X
+ catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects()
+ ask libglvnd to do CommonMakeCurrent().
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 11:26:51 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-05-04 (323 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 5
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
  Title: totem crashed with signal 5
  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 totem in Ubuntu.
https://bugs.launchpad.net/bugs/1758287

Title:
  totem crashed with SIGTRAP in __glXSendError() from
  MakeContextCurrent()

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

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

[Bug 1824886] Re: Battery level stuck at 100% and Estimating...

2019-04-17 Thread Mike Kapushin
** Package changed: gnome-control-center (Ubuntu) => gnome-power-manager
(Ubuntu)

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

Title:
  Battery level stuck at 100% and Estimating...

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

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

[Bug 1824886] Re: Battery level stuck at 100% and Estimating...

2019-04-17 Thread Sebastien Bacher
Thanks for the detail, the journal log you attached is fine it just got
lost in the middle of the info.

It's a bit difficult to know what's going on exactly, but could you boot on 
Ubuntu with the charger unplugged, use the computer for a while (so we are sure 
the battery is not at 100%) and 
- take the upower -d output again
- attach a screenshot of gnome-control-center/power panel and 
gnome-power-statistics
- give the output of '$ cat /sys/class/power_supply/BAT0/charge*'

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

Title:
  Battery level stuck at 100% and Estimating...

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

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

[Bug 1824886] Re: Battery level stuck at 100% and Estimating...

2019-04-17 Thread Mike Kapushin
I disconnected the power adapter and worked ~30 minutes.

upower -d
Device: /org/freedesktop/UPower/devices/line_power_AC0
  native-path:  AC0
  power supply: yes
  updated:  Ср 17 апр 2019 13:31:34 (959 seconds ago)
  has history:  no
  has statistics:   no
  line-power
warning-level:   none
online:  yes
icon-name:  'ac-adapter-symbolic'

Device: /org/freedesktop/UPower/devices/battery_BAT0
  native-path:  BAT0
  vendor:   ASUS
  model:1215T
  power supply: yes
  updated:  Ср 17 апр 2019 13:45:35 (118 seconds ago)
  has history:  yes
  has statistics:   yes
  battery
present: yes
rechargeable:yes
state:   charging
warning-level:   none
energy:  58,9344 Wh
energy-empty:0 Wh
energy-full: 58,9344 Wh
energy-full-design:  60,3376 Wh
energy-rate: 0,014032 W
voltage: 65,535 V
percentage:  100%
capacity:97,6744%
technology:  lithium-ion
icon-name:  'battery-full-charging-symbolic'

Device: /org/freedesktop/UPower/devices/DisplayDevice
  power supply: yes
  updated:  Ср 17 апр 2019 12:40:41 (4012 seconds ago)
  has history:  no
  has statistics:   no
  battery
present: yes
state:   charging
warning-level:   none
energy:  58,9344 Wh
energy-full: 58,9344 Wh
energy-rate: 0,014032 W
percentage:  100%
icon-name:  'battery-full-charging-symbolic'

Daemon:
  daemon-version:  0.99.7
  on-battery:  no
  lid-is-closed:   no
  lid-is-present:  yes
  critical-action: PowerOff

** Attachment added: "Снимок экрана от 2019-04-17 13-51-28.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1824886/+attachment/5256505/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202019-04-17%2013-51-28.png

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

Title:
  Battery level stuck at 100% and Estimating...

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

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

[Bug 1824886] Re: Battery level stuck at 100% and Estimating...

2019-04-17 Thread Mike Kapushin
$ cat /sys/class/power_supply/BAT0/charge*
420
430
420

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

Title:
  Battery level stuck at 100% and Estimating...

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

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

[Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

2019-04-17 Thread El jinete sin cabeza
** Changed in: totem (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  totem crashed with SIGTRAP in __glXSendError() from
  MakeContextCurrent()

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

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

[Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

2019-04-17 Thread El jinete sin cabeza
** No longer affects: mesa

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

Title:
  totem crashed with SIGTRAP in __glXSendError() from
  MakeContextCurrent()

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

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

[Bug 1825167] Re: It does not correctly display the hard drive icon

2019-04-17 Thread El jinete sin cabeza
I changed the name of the gmail account to USER.

** Attachment added: "$ gio mount -li"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1825167/+attachment/5256545/+files/gio_mount_-liV2.txt

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

Title:
  It does not correctly display the hard drive icon

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

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

[Bug 1825167] Re: It does not correctly display the hard drive icon

2019-04-17 Thread El jinete sin cabeza
https://gitlab.gnome.org/GNOME/nautilus/issues/991

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

Title:
  It does not correctly display the hard drive icon

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

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

[Bug 1825167] [NEW] It does not correctly display the hard drive icon

2019-04-17 Thread El jinete sin cabeza
Public bug reported:

https://gitlab.gnome.org/GNOME/nautilus/issues/991

---

The icon of my hard drive is SSD (Attach image).

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: nautilus 1:3.32.0-0ubuntu2
Uname: Linux 5.0.8-050008-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
Date: Wed Apr 17 08:52:05 2019
InstallationDate: Installed on 2018-12-02 (135 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 LANGUAGE=es_CL:es
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=es_CL.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: Upgraded to disco on 2018-12-02 (135 days ago)
usr_lib_nautilus:

** Affects: nautilus
 Importance: Unknown
 Status: Unknown

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


** Tags: amd64 apport-bug disco

** Attachment added: "Captura de pantalla de 2019-04-17 08-48-24.png"
   
https://bugs.launchpad.net/bugs/1825167/+attachment/5256541/+files/Captura%20de%20pantalla%20de%202019-04-17%2008-48-24.png

** Description changed:

+ https://gitlab.gnome.org/GNOME/nautilus/issues/991
+ 
+ ---
+ 
  The icon of my hard drive is SSD (Attach image).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.0-0ubuntu2
  Uname: Linux 5.0.8-050008-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed Apr 17 08:52:05 2019
  InstallationDate: Installed on 2018-12-02 (135 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
-  LANGUAGE=es_CL:es
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=es_CL.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=es_CL:es
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=es_CL.UTF-8
+  SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2018-12-02 (135 days ago)
  usr_lib_nautilus:

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #991
   https://gitlab.gnome.org/GNOME/nautilus/issues/991

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

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

Title:
  It does not correctly display the hard drive icon

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

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

[Bug 1825006] Re: snapp apps not showing in software center

2019-04-17 Thread Larika
I think that "Strumenti di sviluppo" is "Development tools" in english.

https://snag.gy/6PA0yX.jpg

But, snap apps are not showing in any of the gnome-software lists,
neither in the main one.

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

Title:
  snapp apps not showing in software center

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

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

[Bug 1825167] Re: It does not correctly display the hard drive icon

2019-04-17 Thread Sebastien Bacher
Thank you for your bug report, could you provide the output of "$ gio
mount -li" ?

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  It does not correctly display the hard drive icon

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

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

[Bug 1825167] Re: It does not correctly display the hard drive icon

2019-04-17 Thread Bug Watch Updater
** Changed in: nautilus
   Status: Unknown => New

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

Title:
  It does not correctly display the hard drive icon

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

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

[Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

2019-04-17 Thread Bug Watch Updater
** Changed in: gstreamer
   Status: Unknown => New

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

Title:
  totem crashed with SIGTRAP in __glXSendError() from
  MakeContextCurrent()

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

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

[Bug 1825197] [NEW] system unresponse for several seconds a couple of times per hour

2019-04-17 Thread Steyn Westbeek
Public bug reported:

My system is up-to-date on:

$ lsb_release -rd
Description:Ubuntu 18.10
Release:18.10

$ apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.30.2-0ubuntu1.18.10.1
  Candidate: 3.30.2-0ubuntu1.18.10.1

To provide you with an idea of the motivation for the origin in gnome-
shell; I've included the lines in syslog that are displayed for many
more occasions than presented below.

At the times that these messages are displayed in my logs I can still
move my mouse, but mouse clicks are unresponsive and typing is frozen
(but text does appear after freeze).


Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was g-signal 
on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was g-signal 
on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was g-signal 
on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was g-signal 
on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was g-signal 
on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was g-signal 
on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the sweeping phase of GC. This is most likely caused by not 
destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but 
can also be caused by using the destroy(), dispose(), or remove() vfuncs. 
Because it would crash the application, it has been blocked and the JS callback 
not invoked.
Apr 17 09:30:25 TUE001295 org.gnome.Shell.desktop[11238]: == Stack trace for 
context 0x55f9f7a3f220 ==
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: The offending signal was g-signal 
on GDBusProxy 0x55f9f7e68eb0.
Apr 17 09:30:25 TUE001295 gnome-shell[11238]: Attempting to call back into 
JSAPI during the 

[Bug 1803993] Re: Password appears on the VT1 screen

2019-04-17 Thread Brian Murray
@Robert Anderson - could you please report a new bug using ubuntu-bug
plymouth? This will gather information from the system in question that
will help us investigate the matter. Thanks in advance!

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

Title:
  Password appears on the VT1 screen

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

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

[Bug 1825209] [NEW] Automatic suspend delay is at least 15 mins

2019-04-17 Thread Mate Varga
Public bug reported:

Settings -> Power -> Automatic suspend -> On battery power -> Delay has
a minimum value of 15 mins. This might made sense to the developer who
thought that you never want a lower value because you have a laptop with
multiple hours of battery life, but the same setting is used for desktop
computers than run on UPSs. In case of a power outage, desktop users
might reasonably want a lower delay before suspending the computer (1 or
5 minutes, etc.) so I believe that this is a UX design issue.

If you agree with this I might be able to patch it.

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

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

Title:
  Automatic suspend delay is at least 15 mins

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

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

[Bug 1779615] Re: Shell text and some icons have sharp edges during zoom

2019-04-17 Thread Łukasz Zemczak
Hello Daniel, or anyone else affected,

Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3+git20190124-0ubuntu18.04.2
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 for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done verification-done-bionic
** 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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1779615

Title:
  Shell text and some icons have sharp edges during zoom

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

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

[Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

2019-04-17 Thread Łukasz Zemczak
Hello Pavarin, or anyone else affected,

Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3+git20190124-0ubuntu18.04.2
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 for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done verification-done-bionic
** 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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1767648

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

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

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

[Bug 1811900] Re: SRU 3.28 latest git to bionic

2019-04-17 Thread Łukasz Zemczak
Hello Marco, or anyone else affected,

Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3+git20190124-0ubuntu18.04.2
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 for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags removed: verification-failed-bionic
** 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-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1811900

Title:
  SRU 3.28 latest git to bionic

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

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

[Bug 1805444] Re: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend

2019-04-17 Thread Łukasz Zemczak
Hello Yogish, or anyone else affected,

Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3+git20190124-0ubuntu18.04.2
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 for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done verification-done-bionic
** 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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1805444

Title:
  [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice
  backend

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

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

[Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect

2019-04-17 Thread Łukasz Zemczak
Hello Gert, or anyone else affected,

Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3+git20190124-0ubuntu18.04.2
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 for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done verification-done-bionic
** 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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1790525

Title:
  gnome-shell assert failure: double free or corruption (fasttop) in
  g_free() from g_error_free() from cogl_error_free() from
  cogl_texture_new_with_size() from
  clutter_offscreen_effect_real_create_texture()

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

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

[Bug 1795774] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_

2019-04-17 Thread Łukasz Zemczak
Hello errors.ubuntu.com, or anyone else affected,

Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3+git20190124-0ubuntu18.04.2
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 for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done verification-done-bionic
** 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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1795774

Title:
  gnome-shell crashed with SIGSEGV in
  cogl_texture_get_height(texture=0x0) from
  clutter_offscreen_effect_real_paint_target() from
  clutter_offscreen_effect_paint_texture() from
  clutter_offscreen_effect_paint() from clutter_actor_continue_paint()

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

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

[Bug 1825208] [NEW] Automatic suspend delay is at least 15 mins

2019-04-17 Thread Mate Varga
Public bug reported:

Settings -> Power -> Automatic suspend -> On battery power -> Delay has
a minimum value of 15 mins. This might made sense to the developer who
thought that you never want a lower value because you have a laptop with
multiple hours of battery life, but the same setting is used for desktop
computers than run on UPSs. In case of a power outage, desktop users
might reasonably want a lower delay before suspending the computer (1 or
5 minutes, etc.) so I believe that this is a UX design issue.

If you agree with this I might be able to patch it.

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

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

Title:
  Automatic suspend delay is at least 15 mins

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

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

[Bug 1825004] Re: Ubuntu loses display settings on reboot, corrupts displays

2019-04-17 Thread Christopher Nelson
Yes, they are very similar.

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

Title:
  Ubuntu loses display settings on reboot, corrupts displays

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

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