date:20210711

[Desktop-packages] [Bug 1930359] Re: glib2.0: Uninitialised memory is written to gschema.compiled, failure to parse this file leads to gdm, gnome-shell failing to start

2021-07-11 Thread Daniel van Vugt

** Bug watch added: gitlab.gnome.org/GNOME/gvdb/-/issues #2
   https://gitlab.gnome.org/GNOME/gvdb/-/issues/2

** Also affects: glib via
   https://gitlab.gnome.org/GNOME/gvdb/-/issues/2
   Importance: Unknown
   Status: Unknown

** Tags added: fixed-in-2.65.0 fixed-upstream

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

Title:
  glib2.0: Uninitialised memory is written to gschema.compiled, failure
  to parse this file leads to gdm, gnome-shell failing to start

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  In Progress

Bug description:
  [Impact]

  A recent SRU of mutter 3.36.9-0ubuntu0.20.04.1 caused an outage for a
  user with 300 VDIs running Focal, where GNOME applications would fail
  to start, and if you reboot, gdm and gnome-shell both fail to start,
  and you are left with a black screen and a blinking cursor.

  After much investigation, mutter was not at fault. Instead, mutter-
  common calls the libglib2.0-0 hook on upgrade:

  Processing triggers for libglib2.0-0:amd64 (2.64.6-1~ubuntu20.04.3)
  ...

  This in turn calls glib-compile-schemas to recompile the gsettings
  gschema cache, from the files in /usr/share/glib-2.0/schemas/. The
  result is a binary gschemas.compiled file, which is loaded by
  libglib2.0 on every invocation of a GNOME application, or gdm or
  gnome-shell to fetch application default settings.

  Now, glib2.0 2.64.6-1~ubuntu20.04.3 in Focal has some non-
  deterministic behaviour when calling glib-compile-schemas, causing
  generated gschemas.compiled files to have differing contents on each
  run:

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 D0
  3771 A4 DB

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 C3
  3771 A4 98

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 68
  3771 A4 30
  3772 55 56

  The bytes on the left are from a corrupted gschemas.compiled provided
  by an affected user. The changing bytes on the right are non-
  deterministic.

  I ran valgrind over glib-compile-schemas, and found that we are
  writing to uninitialised memory.

  https://paste.ubuntu.com/p/hvZccwdzxz/

  What is happening is that a submodule of glib, gvdb, contains the
  logic for serialising the gschema data structures, and when it
  allocates a buffer to store the eventual gschemas.compiled file, it
  does not initialise it.

  When we populate the fields in the buffer, some bytes are never
  overwritten, and these junk bytes find themselves written to
  gschemas.compiled.

  On boot, when gdm and gnome-shell attempt to parse and load this
  corrupted gschemas.compiled file, it can't parse the junk bytes, and
  raises and error, which propagates up to a breakpoint in glib logging,
  but no debugger is present, so the kernel traps the breakpoint, and
  terminates the library, and the calling application, e.g. gdm.

  The result is that the user is left starting at a black screen with a
  blinking pointer.

  [Testcase]

  On a Focal system, simply run valgrind over glib-compile-schemas:

  # valgrind glib-compile-schemas /usr/share/glib-2.0/schemas

  You will get output like this, with the warning "Syscall param
  write(buf) points to uninitialised byte(s)":

  https://paste.ubuntu.com/p/hvZccwdzxz/

  If you happen to have a large amount of gschema overrides present on
  your system, like my affected user does, you can save a copy of a
  generated gschema.compiled to your home directory and bindiff it
  against recompiles:

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cp /usr/share/glib-2.0/schemas/gschema.compiled 
/home/ubuntu/schemas/gschemas.compiled
  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 C3
  3771 A4 98

  If you install the test package from the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf311791-test

  When you run valgrind, it will report a clean run with no writing to
  uninitialised buffers, and all invocations of glib-compile-schemas
  will be deterministic, and generate the file same with the same sha256
  hash every time. The unwritten bytes if you do a

[Desktop-packages] [Bug 1930359] Re: glib2.0: Uninitialised memory is written to gschema.compiled, failure to parse this file leads to gdm, gnome-shell failing to start

2021-07-11 Thread Matthew Ruffell

Attached is a debdiff for glib2.0 on Focal which fixes this problem.

** Patch added: "Debdiff for glib2.0 for Focal"
   
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1930359/+attachment/5510466/+files/lp1930359_focal.debdiff

** Tags removed: regression-update
** Tags added: sts-sponsor

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

Title:
  glib2.0: Uninitialised memory is written to gschema.compiled, failure
  to parse this file leads to gdm, gnome-shell failing to start

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  In Progress

Bug description:
  [Impact]

  A recent SRU of mutter 3.36.9-0ubuntu0.20.04.1 caused an outage for a
  user with 300 VDIs running Focal, where GNOME applications would fail
  to start, and if you reboot, gdm and gnome-shell both fail to start,
  and you are left with a black screen and a blinking cursor.

  After much investigation, mutter was not at fault. Instead, mutter-
  common calls the libglib2.0-0 hook on upgrade:

  Processing triggers for libglib2.0-0:amd64 (2.64.6-1~ubuntu20.04.3)
  ...

  This in turn calls glib-compile-schemas to recompile the gsettings
  gschema cache, from the files in /usr/share/glib-2.0/schemas/. The
  result is a binary gschemas.compiled file, which is loaded by
  libglib2.0 on every invocation of a GNOME application, or gdm or
  gnome-shell to fetch application default settings.

  Now, glib2.0 2.64.6-1~ubuntu20.04.3 in Focal has some non-
  deterministic behaviour when calling glib-compile-schemas, causing
  generated gschemas.compiled files to have differing contents on each
  run:

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 D0
  3771 A4 DB

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 C3
  3771 A4 98

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 68
  3771 A4 30
  3772 55 56

  The bytes on the left are from a corrupted gschemas.compiled provided
  by an affected user. The changing bytes on the right are non-
  deterministic.

  I ran valgrind over glib-compile-schemas, and found that we are
  writing to uninitialised memory.

  https://paste.ubuntu.com/p/hvZccwdzxz/

  What is happening is that a submodule of glib, gvdb, contains the
  logic for serialising the gschema data structures, and when it
  allocates a buffer to store the eventual gschemas.compiled file, it
  does not initialise it.

  When we populate the fields in the buffer, some bytes are never
  overwritten, and these junk bytes find themselves written to
  gschemas.compiled.

  On boot, when gdm and gnome-shell attempt to parse and load this
  corrupted gschemas.compiled file, it can't parse the junk bytes, and
  raises and error, which propagates up to a breakpoint in glib logging,
  but no debugger is present, so the kernel traps the breakpoint, and
  terminates the library, and the calling application, e.g. gdm.

  The result is that the user is left starting at a black screen with a
  blinking pointer.

  [Testcase]

  On a Focal system, simply run valgrind over glib-compile-schemas:

  # valgrind glib-compile-schemas /usr/share/glib-2.0/schemas

  You will get output like this, with the warning "Syscall param
  write(buf) points to uninitialised byte(s)":

  https://paste.ubuntu.com/p/hvZccwdzxz/

  If you happen to have a large amount of gschema overrides present on
  your system, like my affected user does, you can save a copy of a
  generated gschema.compiled to your home directory and bindiff it
  against recompiles:

  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cp /usr/share/glib-2.0/schemas/gschema.compiled 
/home/ubuntu/schemas/gschemas.compiled
  # glib-compile-schemas /usr/share/glib-2.0/schemas
  # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
  376F E3 C3
  3771 A4 98

  If you install the test package from the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf311791-test

  When you run valgrind, it will report a clean run with no writing to
  uninitialised buffers, and all invocations of glib-compile-schemas
  will be deterministic, and generate the file same with the same sha256
  hash every time. The unwritten bytes if you do a bindiff from

[Desktop-packages] [Bug 1930359] Re: gdm fails to start in a VMware Horizon VDI environment with latest mutter 3.36.9-0ubuntu0.20.04.1 in focal-updates

2021-07-11 Thread Matthew Ruffell

** No longer affects: mutter (Ubuntu)

** No longer affects: mutter (Ubuntu Focal)

** Changed in: glib2.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: glib2.0 (Ubuntu Focal)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu Focal)
   Importance: Undecided => High

** Summary changed:

- gdm fails to start in a VMware Horizon VDI environment with latest mutter 
3.36.9-0ubuntu0.20.04.1 in focal-updates
+ glib2.0: Uninitialised memory is written to gschema.compiled, failure to 
parse this file leads to gdm, gnome-shell failing to start

** Description changed:

  [Impact]
  
- gdm fails to start in a VMware Horizon VDI environment, with Nvidia GRID
- gpus passed into the VDIs.
+ A recent SRU of mutter 3.36.9-0ubuntu0.20.04.1 caused an outage for a
+ user with 300 VDIs running Focal, where GNOME applications would fail to
+ start, and if you reboot, gdm and gnome-shell both fail to start, and
+ you are left with a black screen and a blinking cursor.
  
- Downgrading mutter from 3.36.9-0ubuntu0.20.04.1 to 3.36.1-3ubuntu3 in
- -release fixes the issue, and the issue does not occur with
- 3.36.7+git20201123-0.20.04.1.
+ After much investigation, mutter was not at fault. Instead, mutter-
+ common calls the libglib2.0-0 hook on upgrade:
  
- Currently looking into what landed in bug 1919143 and bug 1905825.
+ Processing triggers for libglib2.0-0:amd64 (2.64.6-1~ubuntu20.04.3) ...
+ 
+ This in turn calls glib-compile-schemas to recompile the gsettings
+ gschema cache, from the files in /usr/share/glib-2.0/schemas/. The
+ result is a binary gschemas.compiled file, which is loaded by libglib2.0
+ on every invocation of a GNOME application, or gdm or gnome-shell to
+ fetch application default settings.
+ 
+ Now, glib2.0 2.64.6-1~ubuntu20.04.3 in Focal has some non-deterministic
+ behaviour when calling glib-compile-schemas, causing generated
+ gschemas.compiled files to have differing contents on each run:
+ 
+ # glib-compile-schemas /usr/share/glib-2.0/schemas
+ # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
+ 376F E3 D0
+ 3771 A4 DB
+ 
+ # glib-compile-schemas /usr/share/glib-2.0/schemas
+ # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
+ 376F E3 C3
+ 3771 A4 98
+ 
+ # glib-compile-schemas /usr/share/glib-2.0/schemas
+ # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
+ 376F E3 68
+ 3771 A4 30
+ 3772 55 56
+ 
+ The bytes on the left are from a corrupted gschemas.compiled provided by
+ an affected user. The changing bytes on the right are non-deterministic.
+ 
+ I ran valgrind over glib-compile-schemas, and found that we are writing
+ to uninitialised memory.
+ 
+ https://paste.ubuntu.com/p/hvZccwdzxz/
+ 
+ What is happening is that a submodule of glib, gvdb, contains the logic
+ for serialising the gschema data structures, and when it allocates a
+ buffer to store the eventual gschemas.compiled file, it does not
+ initialise it.
+ 
+ When we populate the fields in the buffer, some bytes are never
+ overwritten, and these junk bytes find themselves written to
+ gschemas.compiled.
+ 
+ On boot, when gdm and gnome-shell attempt to parse and load this
+ corrupted gschemas.compiled file, it can't parse the junk bytes, and
+ raises and error, which propagates up to a breakpoint in glib logging,
+ but no debugger is present, so the kernel traps the breakpoint, and
+ terminates the library, and the calling application, e.g. gdm.
+ 
+ The result is that the user is left starting at a black screen with a
+ blinking pointer.
  
  [Testcase]
  
+ On a Focal system, simply run valgrind over glib-compile-schemas:
+ 
+ # valgrind glib-compile-schemas /usr/share/glib-2.0/schemas
+ 
+ You will get output like this, with the warning "Syscall param
+ write(buf) points to uninitialised byte(s)":
+ 
+ https://paste.ubuntu.com/p/hvZccwdzxz/
+ 
+ If you happen to have a large amount of gschema overrides present on
+ your system, like my affected user does, you can save a copy of a
+ generated gschema.compiled to your home directory and bindiff it against
+ recompiles:
+ 
+ # glib-compile-schemas /usr/share/glib-2.0/schemas
+ # cp /usr/share/glib-2.0/schemas/gschema.compiled 
/home/ubuntu/schemas/gschemas.compiled
+ # glib-compile-schemas /usr/share/glib-2.0/schemas
+ # cmp -l /home/ubuntu/schemas/gschemas.compiled 
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X 
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
+ 376F E3 C3
+ 3771 A4 98
+ 
+ If you install the test package from the following ppa:
+ 
+ https://launchpad.net/~mruffell/+archive/ubuntu/sf311791-test
+ 
+ When you run valgrind, it will

[Desktop-packages] [Bug 1935794] [NEW] BlueZ release 5.60

2021-07-11 Thread Daniel van Vugt

Public bug reported:

http://www.bluez.org/release-of-bluez-5-60/

** Affects: bluez (Ubuntu)
 Importance: Medium
 Assignee: Daniel van Vugt (vanvugt)
 Status: Triaged


** Tags: impish

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

Title:
  BlueZ release 5.60

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  http://www.bluez.org/release-of-bluez-5-60/

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

2021-07-11 Thread Jerry Lee

Hi Brian,

This is a debdiff for libmbim applicable to Focal(1.22.0-2).

The maintainer scripts (libmbim-proxy.postinst, libmbim-proxy.postrm)
are added to keep mbim-proxy in both places.

I built this in pbuilder and it builds successfully, and I installed it,
the patch works as intended.


** Patch added: "libmbim_1.24.8-1~20.04.02-focal.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1934286/+attachment/5510464/+files/libmbim_1.24.8-1~20.04.02-focal.debdiff

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

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  New
Status in modemmanager source package in Focal:
  Fix Committed
Status in libmbim source package in Hirsute:
  Fix Committed
Status in libqmi source package in Hirsute:
  Fix Committed
Status in modemmanager source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.

  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn Set FCC authentication' command
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits

  The minimum versions of the ModemManager suite required to enable the support 
for the above 2 mentioned modems have been verified: (LP: #1928665)
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6

  The ModemManager suite in the Impish release meets the requirements.

  [Test Plan]

  = How to Reproduce the Bug =

  Execute the following commands to list the modems detected by
  ModemManager in Hirsute and Focal releases:

  $ mmcli --list-modems
  No modems were found

  = Test Procedure =

  1. Install the Ubuntu system on the tested hardware

    The following images will be used to verify the version of the ModemManager 
suite:
    * Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
    * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
    * Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso

  2. Upgrade the kernel and driver  ( for Foxconn and Quectel modem )

    The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
    We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/

  3. Install the ModemManager suite ( for Hirsute and Focal releases )

    The ModemManager suite will be installed from the -proposed
  component:

  $ sudo apt update
  $ sudo apt install modemmanager
  $ sudo apt install libqmi-utils

  4. Execute the following commands

  4.1 Get the run-time environment

  $ uname -ar
  $ lsb_release -a
  $ mmcli -V
  $ qmicli -V

  4.2 Check the status of the ModemManager service

  $ sudo systemctl status ModemManager.service

  4.3 List the detected modems

  $ mmcli --list-modems

  4.4 Check the modem’s status

  $ mmcli --modem 0

  4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem
  only )

  $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan-
  test_amd64.snap

  4.6 Enable the detected modem

  $ sudo mmcli --modem 0 --enable

  4.7 Check the modem’s status

  $ mmcli --modem 0

  = Analyze the Tested Result =

  1. Check if installed packages are working

    The result of test procedure 4.1 and 4.2 can be used to make sure the 
installed packages are working.
    If the Modemmanager.service is active(running), the packages are working.

  2. Check if the supported modem can be detected

    The result of test procedure 4.3 can be used to see if the modem can be 
detected by ModemManager or not.
    The supported modems should be listed.

  3. Check if the modem can be enabled

    If the modem can be enabled, the state of the modem in the test
  procedure 4.7 will be set to be registered.

  = Certification Validation =

  Additionally to the aforementioned test cases, the Certification Team
  will perform some coverage testing across supported devices to make
  sure the other modems still work as expected.

  [Where problems could occur]

  There is a risk that modems supported in the old versions of
  ModemManager suite may not be supported in the newer versions.

  [Other Info]

  We need to upgrade to these

[Desktop-packages] [Bug 1927954] Re: Installing gnome-themes-extra breaks UI color

2021-07-11 Thread Launchpad Bug Tracker

[Expired for gnome-themes-extra (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: gnome-themes-extra (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Installing gnome-themes-extra breaks UI color

Status in gnome-themes-extra package in Ubuntu:
  Expired

Bug description:
  I'm using ubuntu 16 I have a need to upgrade Ubuntu 18.04. However after 
upgrading, the color of UI was changed to white (It should be grey as it is). 
It tooks me a day to find out the root cause is from gnome-themes-extra. 
  Ubuntu 16 does not have this package, but it is automatically installed when 
upgrading to 18.04.

  This white happens not only folder window, but also another app.
  Please see the image https://ibb.co/swh4g8B

  Thanks.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1928073] Re: Display settings don't persist across reboot / sleep

2021-07-11 Thread Launchpad Bug Tracker

[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Display settings don't persist across reboot / sleep

Status in gnome-control-center package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  My setup:

  Dell XPS 13 7390 2-in-1, internal display (3840x2400)

  First external monitor: Dell 24" running at 2560x1440 connected via 
USB-C/Thunderbolt
  Second external monitor: same, connected to the first monitor via DP

  Scale of the internal display set to 200%, fractional scaling on
  Scale of the external displays set to 100%, fractional scaling on

  
  What I expect:

  Settings persist across reboot / sleep / resume.

  What I observe:

  Settings for external monitors are back to 200% scale, fractional
  scaling off.

  Looks like there's a problem detecting the external
  monitors/resolutions in time.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 11 12:12:28 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-12-02 (525 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-05 (5 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1928073] Re: Display settings don't persist across reboot / sleep

2021-07-11 Thread Launchpad Bug Tracker

[Expired for gnome-control-center (Ubuntu) because there has been no
activity for 60 days.]

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

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

Title:
  Display settings don't persist across reboot / sleep

Status in gnome-control-center package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  My setup:

  Dell XPS 13 7390 2-in-1, internal display (3840x2400)

  First external monitor: Dell 24" running at 2560x1440 connected via 
USB-C/Thunderbolt
  Second external monitor: same, connected to the first monitor via DP

  Scale of the internal display set to 200%, fractional scaling on
  Scale of the external displays set to 100%, fractional scaling on

  
  What I expect:

  Settings persist across reboot / sleep / resume.

  What I observe:

  Settings for external monitors are back to 200% scale, fractional
  scaling off.

  Looks like there's a problem detecting the external
  monitors/resolutions in time.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 11 12:12:28 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-12-02 (525 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-05-05 (5 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1935777] Re: Power Saving settings have incomprehensible meanings/labels for Wi-Fi and Bluetooth

2021-07-11 Thread Daniel van Vugt

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

Sounds like bug 1751954

** This bug has been marked a duplicate of bug 1751954
   Bluetooth and Wi-Fi items in Power are worded ambiguously

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

Title:
  Power Saving settings have incomprehensible meanings/labels for Wi-Fi
  and Bluetooth

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  In the Power Saving section of the Power tab of the Settings app,
  there are two switches, one labelled "Wi-Fi" with subheading "Wi-Fi
  can be turned off to save power" and the other labelled "Bluetooth"
  with subheading "Bluetooth can be turned off to save power". On my
  machine, the "Wi-Fi" switch is off and the "Bluetooth" switch is on.
  (Screenshot attached.)

  I do not know what these switches mean, and I do not know what will
  change if I change their settings.

  Does this mean

  * yes Ubuntu is permitted to switch off your wifi to save power but it's not 
permitted to switch off your Bluetooth, or
  * it is permitted to switch off your Bluetooth but not permitted to switch 
off your wifi, or 
  * your bluetooth is already switched off to save power but wifi is always on, 
or 
  * wifi is already switched off to save power but bluetooth is always on, or
  * something else entirely?

  I am utterly confused.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.5-0ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-59-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 11 17:49:14 2021
  InstallationDate: Installed on 2020-06-20 (386 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1935745] Re: distor video

2021-07-11 Thread Daniel van Vugt

Thanks for the bug report. Please attach a photo or video of the
problem.

Please also note Ubuntu 20.10 reaches end of life this month
(https://wiki.ubuntu.com/Releases) so you should install 21.04 or 20.04
instead

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

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

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

Title:
  distor video

Status in Ubuntu:
  Incomplete

Bug description:
  all my video like in youtube and other things all are distor

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-59.66-generic 5.8.18
  Uname: Linux 5.8.0-59-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 10 19:44:54 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
  InstallationDate: Installed on 2021-04-21 (80 days ago)
  InstallationMedia: Lubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Hewlett-Packard HP ProBook 4410s
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic 
root=UUID=00e199ec-d489-4ff4-8eae-6ccad2672093 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2011
  dmi.bios.release: 15.32
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZI Ver. F.20
  dmi.board.name: 3072
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 24.0F
  dmi.chassis.asset.tag: CNU0163P9Q
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 24.15
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZIVer.F.20:bd12/09/2011:br15.32:efr24.15:svnHewlett-Packard:pnHPProBook4410s:pvrF.20:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 4410s
  dmi.product.sku: WL677PA#UUF
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1935744] Re: After a startup and login by lightdm it gave me this message: Sorry, Ubuntu 20.04 Has Expirienced An Internel Error

2021-07-11 Thread Daniel van Vugt

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

Thanks for the bug report. Judging by ShellJournal.txt this appears to
be bug 1886059.

** This bug has been marked a duplicate of bug 1886059
   gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" 
[xcb_io.c:260]

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

Title:
  After a startup and login by lightdm it gave me this message: Sorry,
  Ubuntu 20.04 Has Expirienced An Internel Error

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  It seems like gnome-shell did it but that's all i know
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  Gnome-shell version
  3.36.9-0ubuntu0.20.04.2
  i expected it to work fine. like before
  but it gave me this error

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-59-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 10 19:06:58 2021
  DisplayManager: lightdm
  InstallationDate: Installed on 2021-07-08 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1935686] Re: gnome gui crash

2021-07-11 Thread Daniel van Vugt

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

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

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

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

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


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

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

Title:
  gnome gui crash

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  hello,
  My ubuntu crashing periodically.
  I have tried 18.04, 18.10 and 21.04. 

  Gnome is crashing and must be restarted using reset button on my case.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Jul  9 17:50:35 2021
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2021-06-07 (31 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to hirsute on 2021-07-06 (2 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1935728] Re: Mouse pointer randomly disappears - other mouse operations still work

2021-07-11 Thread Daniel van Vugt

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

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

** Tags added: radeon

** Summary changed:

- Mouse pointer randomly disappears - other mouse operations still work
+ [radeon] Mouse pointer randomly disappears - other mouse operations still work

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1935728

Title:
  [radeon] Mouse pointer randomly disappears - other mouse operations
  still work

Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  The mouse pointer randomly dissappears (same behavior in ubuntu 20.04 LTS and 
ubuntu 20.10).
  When this occurs all other mouse operations still function
  - left/right click
  - scroll wheel
  - mouse position still moves

  Just the actual mouse pointer not visible.
  Only way to resolve is to restart the machine.
  Tried numerous ways to restart the mouse driver but nothing else successful

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-59-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 10 14:45:22 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96-XT [Mobility Radeon HD 
4670] [1002:9488] (prog-if 00 [VGA controller])
     Subsystem: Apple Inc. RV730/M96-XT [Mobility Radeon HD 4670] [106b:00b6]
  InstallationDate: Installed on 2021-07-05 (4 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Apple Inc. iMac10,1
  ProcKernelCmdLine: ro root=UUID=30ee9195-f382-4721-8655-6933b38f1842 
initrd=boot\initrd.img-5.8.0-59-generic
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2019
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 215.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F2268DC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F2268DC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvr215.0.0.0.0:bd06/14/2019:br0.1:svnAppleInc.:pniMac10,1:pvr1.0:rvnAppleInc.:rnMac-F2268DC8:rvr:cvnAppleInc.:ct13:cvrMac-F2268DC8:
  dmi.product.family: Mac
  dmi.product.name: iMac10,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1934836] Re: Gnome control center crashing when setting display positions

2021-07-11 Thread Daniel van Vugt

That's https://errors.ubuntu.com/oops/b861a93a-de9a-11eb-
9d02-fa163e6cac46

Unfortunately retracing failed, but what we do have is:

() at /lib/x86_64-linux-gnu/libglib-2.0.so.0
() at /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_variant_new_va () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_variant_builder_add () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
()

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

Title:
  Gnome control center crashing when setting display positions

Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  From wake the order of the displays has changed and overlapping. The
  control center crashes when trying to move them back into the correct
  positions.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-control-center 1:3.38.5-1ubuntu1
  Uname: Linux 5.12.9-051209-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  6 18:38:43 2021
  InstallationDate: Installed on 2021-06-09 (27 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RebootRequiredPkgs: evolution-data-server
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side

2021-07-11 Thread Daniel van Vugt

I don't think that bug is related to this.

This bug is about rasterization and displaying pixels from a previous
frame, which no mistake in the font itself can be responsible for. Also
the colon bug is not visible in the screenshots of comment #1 or
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2912

They are separate bugs unfortunately.

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

Title:
  Gnome Shell clock is truncated/corrupt on the right side

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When clock changes value, it doesn't displaying time properly

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1934579] Re: Nautilus crashes when opening places from the dock contextmenu

2021-07-11 Thread koyakun

Please let me know if any additional information is required.

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

Title:
  Nautilus crashes when opening places from the dock contextmenu

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  After updating to Ubuntu 21.04, Nautilus crashes every time I try to
  open a second folder by right-clicking on the Nautilus icon in the
  "Favorites" left sidebar (i.e., launch panel) and selecting a
  bookmarked "Places" folder. Normally, this would open a second
  Nautilus window for the selected folder, but instead, any open
  Nautilus windows disappear and no window opens for the selected
  folder. In other words, Nautilus crashes. This did not occur on Ubuntu
  20.10.

  This AskUbuntu post describes the same issue:
  https://askubuntu.com/questions/1344175/nautilus-crashes-when-trying-
  to-open-another-window-by-right-clicking-the-nautil

  If, instead, I right-click the Nautilus icon, select "New Window" and
  then select the desired "Places" folder from the left sidebar of the
  newly opened window, Nautilus does not crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: nautilus 1:3.38.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  4 13:36:13 2021
  InstallationDate: Installed on 2020-02-05 (514 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to hirsute on 2021-06-30 (4 days ago)
  usr_lib_nautilus:
   evince40.1-1
   file-roller   3.38.1-1
   nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
   nautilus-share0.7.3-2ubuntu3

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1934579] Re: Nautilus crashes when opening places from the dock contextmenu

2021-07-11 Thread koyakun

Changed to confirmed since another user confirmed it affects them.

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

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

Title:
  Nautilus crashes when opening places from the dock contextmenu

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  After updating to Ubuntu 21.04, Nautilus crashes every time I try to
  open a second folder by right-clicking on the Nautilus icon in the
  "Favorites" left sidebar (i.e., launch panel) and selecting a
  bookmarked "Places" folder. Normally, this would open a second
  Nautilus window for the selected folder, but instead, any open
  Nautilus windows disappear and no window opens for the selected
  folder. In other words, Nautilus crashes. This did not occur on Ubuntu
  20.10.

  This AskUbuntu post describes the same issue:
  https://askubuntu.com/questions/1344175/nautilus-crashes-when-trying-
  to-open-another-window-by-right-clicking-the-nautil

  If, instead, I right-click the Nautilus icon, select "New Window" and
  then select the desired "Places" folder from the left sidebar of the
  newly opened window, Nautilus does not crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: nautilus 1:3.38.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  4 13:36:13 2021
  InstallationDate: Installed on 2020-02-05 (514 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to hirsute on 2021-06-30 (4 days ago)
  usr_lib_nautilus:
   evince40.1-1
   file-roller   3.38.1-1
   nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
   nautilus-share0.7.3-2ubuntu3

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side

2021-07-11 Thread Travisgevans

Discovered this upstream bug report:
https://gitlab.gnome.org/GNOME/gdm/-/issues/714

Allegedly the problem affects fonts that don't provide the oddball ratio
character GNOME insists on using for the clock colon, including the
default Ubuntu font. This can also cause the colon to render incorrectly
depending on which fonts are installed on the system and what the GNOME
interface font is set to.

I'm going to try the Cantarell font (the upstream GNOME default font, I
think) and see if it resolves the issue.

** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #714
   https://gitlab.gnome.org/GNOME/gdm/-/issues/714

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

Title:
  Gnome Shell clock is truncated/corrupt on the right side

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When clock changes value, it doesn't displaying time properly

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1697373] Re: [screensaver] Screen blanks during video playback in Chrome and Firefox under Xwayland

2021-07-11 Thread Hicks

Ubuntu hirsute hippo too

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1697373

Title:
  [screensaver] Screen blanks during video playback in Chrome and
  Firefox under Xwayland

Status in X.Org X server:
  New
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  gnome-shell / gdm / wayland

  Test Case:
  1. Launch netflix in chrome
  2. Play a video
  3. Wait until the display times out.

  Expected result
  The screen does not dim

  Actual result
  The display goes black.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Jun 12 09:21:46 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2013-09-03 (1377 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1697373/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1904793] Re: upower abruptly thinks battery has gone to 1% and hibernates

2021-07-11 Thread DSHR

Journal from upowerd from Lenove P1 2nd Gen (almost identical to X1
Extreme).

** Attachment added: "upower.journal"
   
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1904793/+attachment/5510380/+files/upower.journal

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

Title:
  upower abruptly thinks battery has gone to 1% and hibernates

Status in Upower:
  Unknown
Status in upower package in Ubuntu:
  Triaged

Bug description:
  Whenever I go on battery after 20-30 minutes upower will very abruptly
  think my battery is at 1% and force my laptop to hibernate. This seems
  to happen at random times, I've seen it when my battery was reported
  to be 90%, 76%, 45%, 25%, etc. If I try to resume Ubuntu locks up
  forcing me to hard reset the machine. I suspect this is because upower
  thinks my battery is still at 1% when its not. My laptops firmware
  correctly reports the battery level and shows that I have plenty of
  power remaining. The last few times this happened I kept powertop up
  which shows that I do have plenty of power even when upower thinks I
  have none. Essentially this makes my laptop unusable on battery.

  Laptop: Lenovo X1 Carbon Extreme Gen 2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: upower 0.99.11-2
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Nov 18 13:59:24 2020
  InstallationDate: Installed on 2019-12-29 (325 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191220)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upower
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (25 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1690719] Re: Mouse pointer randomly pauses/stutters in gnome shell Wayland sessions

2021-07-11 Thread Vincent Chernin

New upstream MR that might help:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1915

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

Title:
  Mouse pointer randomly pauses/stutters in gnome shell Wayland sessions

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  The mouse pointer randomly pauses/stutters in Gnome Shell (Wayland).
  It's not reliably smooth like you would see in Xorg or Mir demo
  servers.

  Feels like there is a blocking call being made in a GUI thread that
  shouldn't have any blocking calls. Although it's not clear if this is
  just a problem with pointer input or the shell compositing in general.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu7
  Architecture: amd64
  Date: Mon May 15 13:23:22 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  InstallationDate: Installed on 2017-05-03 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1935777] Re: Power Saving settings have incomprehensible meanings/labels for Wi-Fi and Bluetooth

2021-07-11 Thread Launchpad Bug Tracker

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

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

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

Title:
  Power Saving settings have incomprehensible meanings/labels for Wi-Fi
  and Bluetooth

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  In the Power Saving section of the Power tab of the Settings app,
  there are two switches, one labelled "Wi-Fi" with subheading "Wi-Fi
  can be turned off to save power" and the other labelled "Bluetooth"
  with subheading "Bluetooth can be turned off to save power". On my
  machine, the "Wi-Fi" switch is off and the "Bluetooth" switch is on.
  (Screenshot attached.)

  I do not know what these switches mean, and I do not know what will
  change if I change their settings.

  Does this mean

  * yes Ubuntu is permitted to switch off your wifi to save power but it's not 
permitted to switch off your Bluetooth, or
  * it is permitted to switch off your Bluetooth but not permitted to switch 
off your wifi, or 
  * your bluetooth is already switched off to save power but wifi is always on, 
or 
  * wifi is already switched off to save power but bluetooth is always on, or
  * something else entirely?

  I am utterly confused.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.5-0ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-59-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 11 17:49:14 2021
  InstallationDate: Installed on 2020-06-20 (386 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1935777] [NEW] Power Saving settings have incomprehensible meanings/labels for Wi-Fi and Bluetooth

2021-07-11 Thread Stuart Langridge

Public bug reported:

In the Power Saving section of the Power tab of the Settings app, there
are two switches, one labelled "Wi-Fi" with subheading "Wi-Fi can be
turned off to save power" and the other labelled "Bluetooth" with
subheading "Bluetooth can be turned off to save power". On my machine,
the "Wi-Fi" switch is off and the "Bluetooth" switch is on. (Screenshot
attached.)

I do not know what these switches mean, and I do not know what will
change if I change their settings.

Does this mean

* yes Ubuntu is permitted to switch off your wifi to save power but it's not 
permitted to switch off your Bluetooth, or
* it is permitted to switch off your Bluetooth but not permitted to switch off 
your wifi, or 
* your bluetooth is already switched off to save power but wifi is always on, 
or 
* wifi is already switched off to save power but bluetooth is always on, or
* something else entirely?

I am utterly confused.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.5-0ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-59-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 11 17:49:14 2021
InstallationDate: Installed on 2020-06-20 (386 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug focal

** Attachment added: "photo_2021-07-11_17-49-25.jpg"
   
https://bugs.launchpad.net/bugs/1935777/+attachment/5510369/+files/photo_2021-07-11_17-49-25.jpg

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

Title:
  Power Saving settings have incomprehensible meanings/labels for Wi-Fi
  and Bluetooth

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  In the Power Saving section of the Power tab of the Settings app,
  there are two switches, one labelled "Wi-Fi" with subheading "Wi-Fi
  can be turned off to save power" and the other labelled "Bluetooth"
  with subheading "Bluetooth can be turned off to save power". On my
  machine, the "Wi-Fi" switch is off and the "Bluetooth" switch is on.
  (Screenshot attached.)

  I do not know what these switches mean, and I do not know what will
  change if I change their settings.

  Does this mean

  * yes Ubuntu is permitted to switch off your wifi to save power but it's not 
permitted to switch off your Bluetooth, or
  * it is permitted to switch off your Bluetooth but not permitted to switch 
off your wifi, or 
  * your bluetooth is already switched off to save power but wifi is always on, 
or 
  * wifi is already switched off to save power but bluetooth is always on, or
  * something else entirely?

  I am utterly confused.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.5-0ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-59-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 11 17:49:14 2021
  InstallationDate: Installed on 2020-06-20 (386 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1935776] Re: package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: installed nvidia-340 package post-installation script subprocess returned error exit status

2021-07-11 Thread Apport retracing service

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1935776

Title:
  package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade:
  installed nvidia-340 package post-installation script subprocess
  returned error exit status 10

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  This problem also prevented upgrading to version 20.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 340.108-0ubuntu5.20.04.2
  ProcVersionSignature: Ubuntu 4.15.0-150.155-generic 4.15.18
  Uname: Linux 4.15.0-150-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Jul 11 12:18:20 2021
  ErrorMessage: installed nvidia-340 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2018-04-08 (1189 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: 
installed nvidia-340 package post-installation script subprocess returned error 
exit status 10
  UpgradeStatus: Upgraded to focal on 2021-07-11 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1935776/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1935776] [NEW] package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: installed nvidia-340 package post-installation script subprocess returned error exit statu

2021-07-11 Thread Ian Ashworth

Public bug reported:

This problem also prevented upgrading to version 20.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-340 340.108-0ubuntu5.20.04.2
ProcVersionSignature: Ubuntu 4.15.0-150.155-generic 4.15.18
Uname: Linux 4.15.0-150-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Jul 11 12:18:20 2021
ErrorMessage: installed nvidia-340 package post-installation script subprocess 
returned error exit status 10
InstallationDate: Installed on 2018-04-08 (1189 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: nvidia-graphics-drivers-340
Title: package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: 
installed nvidia-340 package post-installation script subprocess returned error 
exit status 10
UpgradeStatus: Upgraded to focal on 2021-07-11 (0 days ago)

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1935776

Title:
  package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade:
  installed nvidia-340 package post-installation script subprocess
  returned error exit status 10

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  This problem also prevented upgrading to version 20.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 340.108-0ubuntu5.20.04.2
  ProcVersionSignature: Ubuntu 4.15.0-150.155-generic 4.15.18
  Uname: Linux 4.15.0-150-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Jul 11 12:18:20 2021
  ErrorMessage: installed nvidia-340 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2018-04-08 (1189 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: 
installed nvidia-340 package post-installation script subprocess returned error 
exit status 10
  UpgradeStatus: Upgraded to focal on 2021-07-11 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1935776/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1935775] [NEW] URL links functional about 5% of the time

2021-07-11 Thread Rafael Skodlar

Public bug reported:

a segment from the Error Console:
[Exception... "Component returned failure code: 0x80520001 
(NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsIXPCComponents_Utils.readUTF8URI]"  
nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)"  location: "JS frame 
:: resource://gre/modules/L10nRegistry.jsm :: L10nRegistry.loadSync :: line 
658"  data: no] L10nRegistry.jsm:658:19
loadSync resource://gre/modules/L10nRegistry.jsm:658
fetchFile resource://gre/modules/L10nRegistry.jsm:573
generateResourceSetSync resource://gre/modules/L10nRegistry.jsm:478
map self-hosted:240
generateResourceSetSync resource://gre/modules/L10nRegistry.jsm:473
generateResourceSetsForLocaleSync 
resource://gre/modules/L10nRegistry.jsm:415
next self-hosted:1099
generateBundlesSync resource://gre/modules/L10nRegistry.jsm:177
next self-hosted:1099
touchNext resource://gre/modules/Localization.jsm:167
regenerateBundles resource://gre/modules/Localization.jsm:552
activate resource://gre/modules/Localization.jsm:243
 resource:///modules/OTRUI.jsm:10
connectedCallback 
chrome://messenger/content/chat/chat-conversation-info.js:117
 chrome://global/content/customElements.js:217
08:26:55.328
Error while loading 
'jar:file:///snap/thunderbird/127/omni.ja!/chrome/messenger/search-extensions/twitter/manifest.json'
 (NS_ERROR_FILE_NOT_FOUND) Extension.jsm:570
08:26:55.329 1626017215328  addons.xpi  WARNException running 
bootstrap method startup on twit...@search.mozilla.org: Error: Error while 
loading 
'jar:file:///snap/thunderbird/127/omni.ja!/chrome/messenger/search-extensions/twitter/manifest.json'
 (NS_ERROR_FILE_NOT_FOUND)(resource://gre/modules/Extension.jsm:570:20) JS 
Stack trace: readJSON/https://bugs.launchpad.net/bugs/1935775

Title:
  URL links functional about 5% of the time

Status in thunderbird package in Ubuntu:
  New

Bug description:
  a segment from the Error Console:
  [Exception... "Component returned failure code: 0x80520001 
(NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsIXPCComponents_Utils.readUTF8URI]"  
nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)"  location: "JS frame 
:: resource://gre/modules/L10nRegistry.jsm :: L10nRegistry.loadSync :: line 
658"  data: no] L10nRegistry.jsm:658:19
  loadSync resource://gre/modules/L10nRegistry.jsm:658
  fetchFile resource://gre/modules/L10nRegistry.jsm:573
  generateResourceSetSync resource://gre/modules/L10nRegistry.jsm:478
  map self-hosted:240
  generateResourceSetSync resource://gre/modules/L10nRegistry.jsm:473
  generateResourceSetsForLocaleSync 
resource://gre/modules/L10nRegistry.jsm:415
  next self-hosted:1099
  generateBundlesSync resource://gre/modules/L10nRegistry.jsm:177
  next self-hosted:1099
  touchNext resource://gre/modules/Localization.jsm:167
  regenerateBundles resource://gre/modules/Localization.jsm:552
  activate resource://gre/modules/Localization.jsm:243
   resource:///modules/OTRUI.jsm:10
  connectedCallback 
chrome://messenger/content/chat/chat-conversation-info.js:117
   chrome://global/content/customElements.js:217
  08:26:55.328
  Error while loading 
'jar:file:///snap/thunderbird/127/omni.ja!/chrome/messenger/search-extensions/twitter/manifest.json'
 (NS_ERROR_FILE_NOT_FOUND) Extension.jsm:570
  08:26:55.329 1626017215328addons.xpi  WARNException running 
bootstrap method startup on twit...@search.mozilla.org: Error: Error while 
loading 
'jar:file:///snap/thunderbird/127/omni.ja!/chrome/messenger/search-extensions/twitter/manifest.json'
 (NS_ERROR_FILE_NOT_FOUND)(resource://gre/modules/Extension.jsm:570:20) JS 
Stack trace: readJSON/https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1935775/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1929650] Re: Screen doesn't turn off when using Wayland on a Thinkpad E480

2021-07-11 Thread Zac Schramm

Also having this issue with Intel Nuc NUC5i5RYK with Fedora 34.  Worked
before on KDE.

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

Title:
  Screen doesn't turn off when using Wayland on a Thinkpad E480

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When the screen of my laptop (Thinkpad E480) is supposed to turn off
  (because of inactivity or when actively locking screen), the screen
  dims, turns off for a second and then turns back on while remaining
  dimmed. I can see the backlight of the screen and the cursor.

  This bug is only present when using a wayland-session regardless of my
  settings. It also happens with a fresh user account. Additionally, I
  tested with the 5.8 and 5.12 kernels with the same result.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-power-manager 3.32.0-2
  ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
  Uname: Linux 5.11.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 26 08:13:27 2021
  InstallationDate: Installed on 2021-05-24 (1 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1935770] [NEW] [Sound Output Built in Speaker to HDMI] No auto switch from Speaker to HDMI and back

2021-07-11 Thread Fabricio Luiz Bronzatti

Public bug reported:

When connecting a HDMI output the Audio Output won't switch
automatically to the HDMI output from the Built in Speakers, it is
required to enter the Settings and switch manually. When disconnecting
the HDMI output the audio output won't come back to the built in
Speakers as it was previously before connecting the HDMI output.

I understand that may be intentional, however I do believe the audio
auto switch output to HDMI when a cable is connected and then back to
previously default output when HDMI is disconnected should be the
default, if a different audio output would be required than a manually
setting may be ok.

Thanks,

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-59-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  fabriciolb   1497 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul 11 10:32:46 2021
InstallationDate: Installed on 2021-06-02 (38 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Digital Out, HDMI
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: None of the above
Title: [80YH, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/30/2020
dmi.bios.release: 1.47
dmi.bios.vendor: LENOVO
dmi.bios.version: 4WCN47WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Cairo 5A
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 320-15IKB
dmi.ec.firmware.release: 1.47
dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN47WW:bd06/30/2020:br1.47:efr1.47:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnCairo5A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
dmi.product.family: IDEAPAD
dmi.product.name: 80YH
dmi.product.sku: LENOVO_MT_80YH_BU_idea_FM_
dmi.product.version: Lenovo ideapad 320-15IKB
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug audio focal hdmi output

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1935770

Title:
  [Sound Output Built in Speaker to HDMI] No auto switch from Speaker to
  HDMI and back

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When connecting a HDMI output the Audio Output won't switch
  automatically to the HDMI output from the Built in Speakers, it is
  required to enter the Settings and switch manually. When disconnecting
  the HDMI output the audio output won't come back to the built in
  Speakers as it was previously before connecting the HDMI output.

  I understand that may be intentional, however I do believe the audio
  auto switch output to HDMI when a cable is connected and then back to
  previously default output when HDMI is disconnected should be the
  default, if a different audio output would be required than a manually
  setting may be ok.

  Thanks,

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-59-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fabriciolb   1497 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 11 10:32:46 2021
  InstallationDate: Installed on 2021-06-02 (38 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [80YH, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/30/2020
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN47WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Cairo 5A
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB

[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows

2021-07-11 Thread Tim Passingham

I tried adding --display=:0 to the desktop commmand, as below:

Exec=thunderbird -addressbook --display=:0

I still get the same problem under wayland.

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

Title:
  Thunderbird under Wayland does not correctly close (or manage) windows

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default.
  Thunderbird version: 78.11.0 with "gnome-support" package.
  Same problem in safe mode.
  Description:
  By default in this context, TB is a Wayland task.
  When opening a compose windows (or reply or transfer), sending mail 
apparently close the windows, but gnome shell continue to show multiple 
"points", as if multiple windows are still active.
  And after closing TB, it seems maintained in the same state, so it becomes 
impossible to relaunch it from the desk. But task manager of "looking glass" 
does not show it and it is possible to launch from terminal.
  Provisional solution:
  Modify .desktop file to launch with --display=:0 option, that force to use 
XWayland interface, as shown by xlsclients (for example).
  But it is actually a bug under Wayland context, that also badly interfer with 
many add-ons or extensions.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1930359] Re: glib2.0: Uninitialised memory is written to gschema.compiled, failure to parse this file leads to gdm, gnome-shell failing to start

[Desktop-packages] [Bug 1930359] Re: glib2.0: Uninitialised memory is written to gschema.compiled, failure to parse this file leads to gdm, gnome-shell failing to start

[Desktop-packages] [Bug 1930359] Re: gdm fails to start in a VMware Horizon VDI environment with latest mutter 3.36.9-0ubuntu0.20.04.1 in focal-updates

[Desktop-packages] [Bug 1935794] [NEW] BlueZ release 5.60

[Desktop-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

[Desktop-packages] [Bug 1927954] Re: Installing gnome-themes-extra breaks UI color

[Desktop-packages] [Bug 1928073] Re: Display settings don't persist across reboot / sleep

[Desktop-packages] [Bug 1928073] Re: Display settings don't persist across reboot / sleep

[Desktop-packages] [Bug 1935777] Re: Power Saving settings have incomprehensible meanings/labels for Wi-Fi and Bluetooth

[Desktop-packages] [Bug 1935745] Re: distor video

[Desktop-packages] [Bug 1935744] Re: After a startup and login by lightdm it gave me this message: Sorry, Ubuntu 20.04 Has Expirienced An Internel Error

[Desktop-packages] [Bug 1935686] Re: gnome gui crash

[Desktop-packages] [Bug 1935728] Re: Mouse pointer randomly disappears - other mouse operations still work

[Desktop-packages] [Bug 1934836] Re: Gnome control center crashing when setting display positions

[Desktop-packages] [Bug 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side

[Desktop-packages] [Bug 1934579] Re: Nautilus crashes when opening places from the dock contextmenu

[Desktop-packages] [Bug 1934579] Re: Nautilus crashes when opening places from the dock contextmenu

[Desktop-packages] [Bug 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side

[Desktop-packages] [Bug 1697373] Re: [screensaver] Screen blanks during video playback in Chrome and Firefox under Xwayland

[Desktop-packages] [Bug 1904793] Re: upower abruptly thinks battery has gone to 1% and hibernates

[Desktop-packages] [Bug 1690719] Re: Mouse pointer randomly pauses/stutters in gnome shell Wayland sessions

[Desktop-packages] [Bug 1935777] Re: Power Saving settings have incomprehensible meanings/labels for Wi-Fi and Bluetooth

[Desktop-packages] [Bug 1935777] [NEW] Power Saving settings have incomprehensible meanings/labels for Wi-Fi and Bluetooth

[Desktop-packages] [Bug 1935776] Re: package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: installed nvidia-340 package post-installation script subprocess returned error exit status

[Desktop-packages] [Bug 1935776] [NEW] package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: installed nvidia-340 package post-installation script subprocess returned error exit statu

[Desktop-packages] [Bug 1935775] [NEW] URL links functional about 5% of the time

[Desktop-packages] [Bug 1929650] Re: Screen doesn't turn off when using Wayland on a Thinkpad E480

[Desktop-packages] [Bug 1935770] [NEW] [Sound Output Built in Speaker to HDMI] No auto switch from Speaker to HDMI and back

[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows

29 matches

Site Navigation

Mail list logo

Footer information