[Desktop-packages] [Bug 1869835] [NEW] Login screen randomly reverts my default keyboard layout to en-US

[Olivier Tilloy]

Public bug reported:

I have seen that happening randomly during the 20.04 development cycle,
and I think more often in the last week or so, but never consistently:
when I turn on my laptop, on the GDM greeter screen the keyboard layout
that's selected is en-US, instead of my default preference (fr-bépo).

To give an example of the randomness, this is what I did this morning:
 1) Cold booted my laptop, selected my user, typed my password, login got 
denied, looked at the keyboard layout indicator and realized it was en-US 
instead of fr-bépo
 2) Selected fr-bépo in the indicator, typed my password again and successfully 
logged in (and indicator in the session remained fr-bépo as expected)
 3) From the menu, rebooted laptop
 4) On the GDM login screen, keyboard layout indicator was reverted to en-US, 
again
 5) Changed indicator to fr-bépo, logged in, used gnome-terminal and apt to 
dist-upgrade, then rebooted laptop from menu
 6) This time on the GDM login screen, my default preference (fr-bépo) was 
selected

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 31 07:16:14 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-07-02 (1367 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gdm3
UpgradeStatus: Upgraded to focal on 2020-01-12 (78 days ago)

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


** Tags: amd64 apport-bug focal rls-ff-incoming

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

Title:
  Login screen randomly reverts my default keyboard layout to en-US

Status in gdm3 package in Ubuntu:
  New

Bug description:
  I have seen that happening randomly during the 20.04 development
  cycle, and I think more often in the last week or so, but never
  consistently: when I turn on my laptop, on the GDM greeter screen the
  keyboard layout that's selected is en-US, instead of my default
  preference (fr-bépo).

  To give an example of the randomness, this is what I did this morning:
   1) Cold booted my laptop, selected my user, typed my password, login got 
denied, looked at the keyboard layout indicator and realized it was en-US 
instead of fr-bépo
   2) Selected fr-bépo in the indicator, typed my password again and 
successfully logged in (and indicator in the session remained fr-bépo as 
expected)
   3) From the menu, rebooted laptop
   4) On the GDM login screen, keyboard layout indicator was reverted to en-US, 
again
   5) Changed indicator to fr-bépo, logged in, used gnome-terminal and apt to 
dist-upgrade, then rebooted laptop from menu
   6) This time on the GDM login screen, my default preference (fr-bépo) was 
selected

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 31 07:16:14 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (1367 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to focal on 2020-01-12 (78 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1869835/+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 1866851] Re: Lock screen scaled down background image in top left corner when fractional scaling is enabled

[Daniel van Vugt]

** Summary changed:

- lock screen scaled down backgound image in top left corner
+ Lock screen scaled down background image in top left corner when fractional 
scaling is enabled

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

Title:
  Lock screen scaled down background image in top left corner when
  fractional scaling is enabled

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  The new lock screen in gnome 3.36 looks strange, as if the blurred
  background image is being scaled down to the top left corner of the
  screen.  background image being used is 1920x1440 pixel jpeg, display
  size is 3840x2160, with fractional scaling enabled and set to 175% on
  wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.35.91-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu19
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 10 07:38:52 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-17 (206 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-03-06 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1866851/+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 1868659] Re: gnome-shell crashed with SIGSEGV in cogl_matrix_stack_pop() from cogl_framebuffer_pop_matrix() from clutter_actor_paint() from clutter_actor_real_paint() from clut

[Daniel van Vugt]

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

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

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2418
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2418

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2418
   Importance: Unknown
   Status: Unknown

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

Title:
  gnome-shell crashed with SIGSEGV in cogl_matrix_stack_pop() from
  cogl_framebuffer_pop_matrix() from clutter_actor_paint() from
  clutter_actor_real_paint() from clutter_actor_continue_paint()

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.35.91-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/5d803bbb03daf885d3d98254f5731711add2d255 
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/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1868659/+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 1869836] [NEW] Login screen randomly reverts my default keyboard layout to en-US

[Olivier Tilloy]

Public bug reported:

I have seen that happening randomly during the 20.04 development cycle,
and I think more often in the last week or so, but never consistently:
when I turn on my laptop, on the GDM greeter screen the keyboard layout
that's selected is en-US, instead of my default preference (fr-bépo).

To give an example of the randomness, this is what I did this morning:
 1) Cold booted my laptop, selected my user, typed my password, login got 
denied, looked at the keyboard layout indicator and realized it was en-US 
instead of fr-bépo
 2) Selected fr-bépo in the indicator, typed my password again and successfully 
logged in (and indicator in the session remained fr-bépo as expected)
 3) From the menu, rebooted laptop
 4) On the GDM login screen, keyboard layout indicator was reverted to en-US, 
again
 5) Changed indicator to fr-bépo, logged in, used gnome-terminal and apt to 
dist-upgrade, then rebooted laptop from menu
 6) This time on the GDM login screen, my default preference (fr-bépo) was 
selected

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 31 07:16:14 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-07-02 (1367 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gdm3
UpgradeStatus: Upgraded to focal on 2020-01-12 (78 days ago)

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


** Tags: amd64 apport-bug focal rls-ff-incoming

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

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

Title:
  Login screen randomly reverts my default keyboard layout to en-US

Status in gdm3 package in Ubuntu:
  New

Bug description:
  I have seen that happening randomly during the 20.04 development
  cycle, and I think more often in the last week or so, but never
  consistently: when I turn on my laptop, on the GDM greeter screen the
  keyboard layout that's selected is en-US, instead of my default
  preference (fr-bépo).

  To give an example of the randomness, this is what I did this morning:
   1) Cold booted my laptop, selected my user, typed my password, login got 
denied, looked at the keyboard layout indicator and realized it was en-US 
instead of fr-bépo
   2) Selected fr-bépo in the indicator, typed my password again and 
successfully logged in (and indicator in the session remained fr-bépo as 
expected)
   3) From the menu, rebooted laptop
   4) On the GDM login screen, keyboard layout indicator was reverted to en-US, 
again
   5) Changed indicator to fr-bépo, logged in, used gnome-terminal and apt to 
dist-upgrade, then rebooted laptop from menu
   6) This time on the GDM login screen, my default preference (fr-bépo) was 
selected

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 31 07:16:14 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (1367 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to focal on 2020-01-12 (78 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1869836/+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 1866923] Re: Wifi connection says it's connected but this is not true after the computer goes into a sleep status

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  Wifi connection says it's connected but this is not true after the
  computer goes into a sleep status

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The wifi is connected and working correctly when powered on, however
  when I close the laptop lid, which I think puts it to sleep, and then
  reopen it, it says it's connected according to the icon but this is
  not true.

  A workaround is turning on Airplane mode and then switching it back on
  again. It then reconnects and is then fine again. Unless I close the
  lid and then the process repeats again.

  I guess this is to do with the wifi driver but I don't know what
  package it is so I just picked network-manager, sorry - I'm trying :)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.4-2ubuntu2.2
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 10 19:29:03 2020
  InstallationDate: Installed on 2020-03-09 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.68.1 dev wlp1s0 proto dhcp metric 600 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.68.0/24 dev wlp1s0 proto kernel scope link src 192.168.68.18 metric 
600
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1866923/+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 1869829] [NEW] File collision between libreoffice-writer-nogui-dbgsym and libreoffice-core-nogui-dbgsym

[Oleg Schelicalnov]

Public bug reported:

I'm trying to catch error and installed libreoffice-core-nogui-dbgsym.
After  it I installed libreoffice-writer-nogui-dbgsym and got error:

Unpacking libreoffice-writer-nogui-dbgsym (1:6.4.2-0ubuntu0.18.04.3) ...
dpkg: error processing archive /var/cache/apt/archives/libreoffice-
writer-nogui-dbgsym_1%3a6.4.2-0ubuntu0.18.04.3_amd64.ddeb (--unpack):
 trying to overwrite '/usr/share/libreoffice/gdb/libreoffice/sw.py',
which is also in package libreoffice-core-nogui-dbgsym
1:6.4.2-0ubuntu0.18.04.3
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

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

Title:
  File collision between libreoffice-writer-nogui-dbgsym and
  libreoffice-core-nogui-dbgsym

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I'm trying to catch error and installed libreoffice-core-nogui-dbgsym.
  After  it I installed libreoffice-writer-nogui-dbgsym and got error:

  Unpacking libreoffice-writer-nogui-dbgsym (1:6.4.2-0ubuntu0.18.04.3) ...
  dpkg: error processing archive /var/cache/apt/archives/libreoffice-
  writer-nogui-dbgsym_1%3a6.4.2-0ubuntu0.18.04.3_amd64.ddeb (--unpack):
   trying to overwrite '/usr/share/libreoffice/gdb/libreoffice/sw.py',
  which is also in package libreoffice-core-nogui-dbgsym
  1:6.4.2-0ubuntu0.18.04.3
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1869829/+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 1866923] Re: Wifi connection says it's connected but this is not true after the computer goes into a sleep status

[Danilo Alculete]

I'm having the same error no ubuntu 20.04

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

Title:
  Wifi connection says it's connected but this is not true after the
  computer goes into a sleep status

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The wifi is connected and working correctly when powered on, however
  when I close the laptop lid, which I think puts it to sleep, and then
  reopen it, it says it's connected according to the icon but this is
  not true.

  A workaround is turning on Airplane mode and then switching it back on
  again. It then reconnects and is then fine again. Unless I close the
  lid and then the process repeats again.

  I guess this is to do with the wifi driver but I don't know what
  package it is so I just picked network-manager, sorry - I'm trying :)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.4-2ubuntu2.2
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 10 19:29:03 2020
  InstallationDate: Installed on 2020-03-09 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.68.1 dev wlp1s0 proto dhcp metric 600 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.68.0/24 dev wlp1s0 proto kernel scope link src 192.168.68.18 metric 
600
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1866923/+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 1860137] Re: Chromium-browser Snap is amnesiac

[Launchpad Bug Tracker]

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

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Chromium-browser Snap is amnesiac

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  I'm using Ubuntu 19.10, latest Chromium(-browser) installed.

  The issue is that after the switch to snap-based Chromium it started
  forgetting my logged in sessions very very often. This is not isolated
  to one online service, I have to log back in to everything I use,
  including Chromium itself. It also forgets any "Remember this device"
  checkmarks.

  History, downloads or extensions however do not suffer from any data
  loss.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1860137/+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 1860761] Re: Dell XPS 13 - Bios upgrade not working - Always ask for power supply

[Launchpad Bug Tracker]

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

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

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

Title:
  Dell XPS 13 - Bios upgrade not working - Always ask for power supply

Status in gnome-software package in Ubuntu:
  Expired

Bug description:
  Each time the notebook starts I'm advised that a new bios upgrade is
  out: XPS 13 7390 System Update 0.1.3.1 => 0.1.4.0

  Problem is that when I ask for update, I always get this message
  (traduction from french):

  Not possible to upgrade "XPS 13 7390 System Update": connect power
  supply.

  Battery can be full, notebook connected on power supply, doesn't
  matter, will not upgrade.

  Daniel

  Ubuntu 18.04.3 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-software 3.28.1-0ubuntu4.18.04.14
  ProcVersionSignature: Ubuntu 4.15.0-1066.76-oem 4.15.18
  Uname: Linux 4.15.0-1066-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 09:15:31 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92
  InstallationDate: Installed on 2019-12-07 (47 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.14
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1860761/+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 1869827] [NEW] Gnome Settings not able to change sound device

[Rob Frohne]

Public bug reported:

This is a recent bug (last week or so).  Fortunately a work around is to use 
https://extensions.gnome.org/extension/906/sound-output-device-chooser/
which works.  I'm not sure this is the right package to put this bug report in. 
 I mean the settings with the gear icon in Ubuntu 20.04.  See the photo 
attached.  When you select other options other than the default laptop 
speakers, you still get sound through the laptop speakers.

Thanks for all your hard work!

Rob

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-settings-daemon 3.35.91-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 30 21:03:22 2020
InstallationDate: Installed on 2019-04-19 (347 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "2020-03-30_21-08.png"
   
https://bugs.launchpad.net/bugs/1869827/+attachment/5343592/+files/2020-03-30_21-08.png

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

Title:
  Gnome Settings not able to change sound device

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  This is a recent bug (last week or so).  Fortunately a work around is to use 
https://extensions.gnome.org/extension/906/sound-output-device-chooser/
  which works.  I'm not sure this is the right package to put this bug report 
in.  I mean the settings with the gear icon in Ubuntu 20.04.  See the photo 
attached.  When you select other options other than the default laptop 
speakers, you still get sound through the laptop speakers.

  Thanks for all your hard work!

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-settings-daemon 3.35.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 30 21:03:22 2020
  InstallationDate: Installed on 2019-04-19 (347 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  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/1869827/+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 1868705] Re: Update deja-dup to 40.6

[Bug Watch Updater]

** Changed in: deja-dup (Debian)
   Status: Unknown => New

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

Title:
  Update deja-dup to 40.6

Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Focal:
  Fix Released
Status in deja-dup package in Debian:
  New

Bug description:
  Please update deja-dup to 40.6. It is a bug-fix release.

  https://gitlab.gnome.org/World/deja-dup/-/blob/master/NEWS.md

  40.6
  Fixes a bug that prevented backing up to Google Drive accounts with unlimited 
quotas
  Updated translations

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1868705/+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 1869814] Re: ubuntu-docs build failure - possible solution

[Gunnar Hjalmarsson]

@Shaun: Have you possibly stumbled into anything similar when building
e.g. gnome-user-docs?

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

Title:
  ubuntu-docs build failure - possible solution

Status in itstool package in Ubuntu:
  New
Status in libxml2 package in Ubuntu:
  New
Status in ubuntu-docs package in Ubuntu:
  New

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1833116] Re: chtmax98090 not working out of the box

[Dylan Taylor]

Having the same issue on a Lenovo N20 "Clapper" Chromebook. Applying the
Git patch crashes PulseAudio for me as well. Can't get any sound to play
at all from the built-in speakers.

dylan@dylan-Clapper:~$ aplay -l
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 3: Generic Digital [Generic Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: chtmax98090 [chtmax98090], device 0: 3 []
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 1: chtmax98090 [chtmax98090], device 1: Deep-Buffer Audio (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

dylan@dylan-Clapper:~$ lspci | grep Audio
00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
High Definition Audio Controller (rev 0e)

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

Title:
  chtmax98090 not working out of the box

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  chtmax98090 intel HD audio device doesn't work out of the box after
  installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on
  audio devices.

  Audio options shows device and it works if I do this:

   git clone https://github.com/plbossart/UCM.git
   cd UCM
   cp -r chtmax98090/ /usr/share/alsa/ucm/
   alsactl store

  It would be great if there were a solution to make it works out of the
  box. The device (Chromebook Acer CB3-111 has it's end of life for
  chromeOS in July-August, so I suppose more people with this device
  will change OS perhaps to Ubuntu).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jaime  1293 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 17 20:32:35 2019
  InstallationDate: Installed on 2019-06-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833116/+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 1869578] Re: PCI/internal sound card not detected

[Daniel van Vugt]

Ubuntu 14.04 reached end of standard support in April 2019:

  https://wiki.ubuntu.com/Releases

If you would like to continue with free support then please update to a
newer Ubuntu version and tell us if the problem still occurs.

If you would like to continue with Ubuntu 14.04 then there is a paid
support option detailed at https://www.ubuntu.com/esm

** Tags added: regression-update

** Changed in: alsa-driver (Ubuntu)
   Status: New => Won't Fix

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  i updated ubuntu 14.04 and now no sound
  i used aplay -l and i've got this message : internal sound card not detected

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-170-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Sun Mar 29 13:56:20 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  InstallationDate: Installed on 2017-10-01 (910 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.product.name: Inspiron 15-3552

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1869578/+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 1833116] Re: chtmax98090 not working out of the box

[Dylan Taylor]

** Attachment added: "clapper-lspci-vvnn.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833116/+attachment/5343583/+files/clapper-lspci-vvnn.txt

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

Title:
  chtmax98090 not working out of the box

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  chtmax98090 intel HD audio device doesn't work out of the box after
  installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on
  audio devices.

  Audio options shows device and it works if I do this:

   git clone https://github.com/plbossart/UCM.git
   cd UCM
   cp -r chtmax98090/ /usr/share/alsa/ucm/
   alsactl store

  It would be great if there were a solution to make it works out of the
  box. The device (Chromebook Acer CB3-111 has it's end of life for
  chromeOS in July-August, so I suppose more people with this device
  will change OS perhaps to Ubuntu).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jaime  1293 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 17 20:32:35 2019
  InstallationDate: Installed on 2019-06-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833116/+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 1869759] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  [amdgpu] Opengl or vulkan or mesa bug that causes textures to glitch
  when mipmapping or trilinear/bilinear filtering is enabled

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Textures are glitched (almost like they are cut up and repeated) when
  mipmapping or trilinear/bilinear filtering is enabled. Workaround is
  to disable both.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 30 12:03:39 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c4) (prog-if 
00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Picasso [1025:134f]
  InstallationDate: Installed on 2019-11-04 (147 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Acer Aspire A515-43
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=a44eb2b0-d036-44b7-9c90-d0a427ecd008 ro quiet splash 
resume=/dev/nvme0n1p5 resume_offset=15261696 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Grumpy_PK
  dmi.board.vendor: PK
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd09/26/2019:svnAcer:pnAspireA515-43:pvrV1.06:rvnPK:rnGrumpy_PK:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-43
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  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+git20190815-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/linux/+bug/1869759/+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 1869610] Re: Desktop resolution will not go above 1024 * 768 (4:3)

[Daniel van Vugt]

Sounds like it's possible:

https://en.wikipedia.org/wiki/Display_Data_Channel


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

** Summary changed:

- Desktop resolution will not go above 1024 * 768 (4:3)
+ [i915] Desktop resolution will not go above 1024 * 768 (4:3)

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

Title:
  [i915] Desktop resolution will not go above 1024 * 768 (4:3)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Fresh install of Ubuntu 19.10 on an Acer AX3995-EF308 hooked to HP
  2159m, cannot select any higher resolution than 1024*768

  Description:  Ubuntu 19.10
  Release:  19.10

  xorg:
Installed: 1:7.7+19ubuntu12
Candidate: 1:7.7+19ubuntu12
Version table:
   *** 1:7.7+19ubuntu12 500
  500 http://ca.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 29 15:11:25 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:074f]
  InstallationDate: Installed on 2020-03-22 (6 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Acer Aspire X3995
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic 
root=UUID=e838af89-e069-4a74-b6c8-2247d6f3f026 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P11-A3
  dmi.board.name: Aspire X3995
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-A3:bd10/29/2012:svnAcer:pnAspireX3995:pvr:rvnAcer:rnAspireX3995:rvr:cvnAcer:ct3:cvr:
  dmi.product.family: Acer Desktop
  dmi.product.name: Aspire X3995
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/linux/+bug/1869610/+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 1869706] Re: Plymouth with Nvidia Drivers causes login loop at GDM

[Daniel van Vugt]

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

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


** Package changed: plymouth (Ubuntu) => gdm3 (Ubuntu)

** This bug has been marked a duplicate of bug 1845801
   [nvidia] Automatic login fails and then all subsequent logins fail. Killing 
gnome-session-binary fixes it, or just not using automatic login.

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

Title:
  Plymouth with Nvidia Drivers causes login loop at GDM

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Summary :-

  Login loop on GDM after installing nvidia drivers using ubuntu-drivers 
autoinstall sript.

  Hardware :- Nvidia GTX 1070 with a Intel Core i7 7700 HQ. HP OMEN 2017
  Laptop.

  Steps to reproduce :-

  Simply install nvidia drivers using ubuntu-drivers autoinstall script.

  
  Expected behaviour :- seamless autologin to desktop, 

  Observed behaviour:- GDM refuses to login automatically and then any
  attempts of logging in by entering password just simply fail. Hence
  login loop.

  Only known mitigation is :- remove the splash from the
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" in /etc/default grub and
  update-grub before installing nvidia drivers, Or chroot into the
  system after reproducing the error and remove "splash"

  This bug has been in existence since Ubuntu 19.10, Wanted to ensure
  this was reported here for resolution.

  Happy to provide further information if required.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: plymouth 0.9.4git20200323-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 30 16:24:42 2020
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  InstallationDate: Installed on 2020-03-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  MachineType: HP OMEN by HP Laptop
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=fed3e7a0-e171-4fe1-a43e-4c6e9292aacd ro quiet mitigations=off
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=fed3e7a0-e171-4fe1-a43e-4c6e9292aacd ro quiet mitigations=off
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/22/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.48
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8261
  dmi.board.vendor: HP
  dmi.board.version: 83.72
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.48:bd06/22/2018:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8261:rvr83.72:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Omen
  dmi.product.name: OMEN by HP Laptop
  dmi.product.sku: 1HQ37PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1869706/+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 1869820] Re: Missing dependency: gnome-shell-extension-prefs

[Daniel van Vugt]

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

This sounds like a consequence of bug 1869635 so let's track it there
for now.

** This bug has been marked a duplicate of bug 1869635
   the menu "Dash to Dock Settings" is visible

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

Title:
  Missing dependency: gnome-shell-extension-prefs

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  Dash to Dock settings does not work on a stock Ubuntu 20.04 (Focal)
  installation. If you right click the "Show Applications",  click
  settings, it'll trigger an error indicating gnome-shell-extension-
  prefs is missing. Installing this package resolves the issue. This
  package should be a dependency of gnome-shell-extension-ubuntu-dock.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1869820/+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 1869611] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style()

[Daniel van Vugt]

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

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Left PC and went to lock screen/monitor sleep and came back to this
  error when I moved my mouse/keyboard to log back in. Never saw the
  actual lock screen with password.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 29 14:16:50 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-03-26 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fc4e4f36aaf : 
repz cmpsb %es:(%rdi),%ds:(%rsi)
   PC (0x7fc4e4f36aaf) ok
   source "%es:(%rdi)" (0x7fc4e4f678f9) ok
   destination "%ds:(%rsi)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   st_theme_node_get_icon_style () from /usr/lib/gnome-shell/libst-1.0.so
   st_texture_cache_load_gicon () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869611/+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 1869737] Re: Folders in applications menu are broken in smaller screens

[Daniel van Vugt]

Thanks for the bug report. Please open a new issue for the upstream
developers at:

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

and then tell us the new issue ID.

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

Title:
  Folders in applications menu are broken in smaller screens

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When using a smaller screen resolution like 1366x768, opening and closing a 
folder inside the applications menu breaks the scaling of the icons and number 
of pages.
  Icons either become very small or disappear and the number of pages shows 
more pages than it should.

  The bug did not occur when using a 1920x1080 display.

  I've also recorded a little video: https://youtu.be/v98TfvBaxqk

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 30 11:22:30 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-28 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-03-28 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869737/+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 1869798] Re: Opening a combo box will draw windows from other workspaces on current workspace

[Daniel van Vugt]

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

Sounds like one of the issues fixed in:

https://launchpad.net/ubuntu/+source/gnome-shell/3.36.0-2ubuntu2

** This bug has been marked a duplicate of bug 1868911
   Exiting overview causes windows from other workspaces to be visible

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

Title:
  Opening  a combo box will draw windows from other workspaces on
  current workspace

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When a combo box is selected all the currently open windows will be
  drawn on the screen, even if those windows are on other workspaces.

  How to reproduce:

  - Open different windows: Files and Terminal
  - Send one window to a different Workspace: right-click on the title bar, 
Move to Workspace Down/Up
  - Open Settings | Appearance
  - Open 'Position On Screen' combo box

  - Windows that were sent to other the worspaces will appear on the
  screen. Windows aren't active and you're not able to interact with
  them, they are just displayed.

  Some windows will have a title bar that can be interacted with. In my
  example, it was Brave browser, I was able to click on
  minimize/maxime/close buttons and move the window around, but window
  content wasn't responsive. However, Terminal, Files, Settings were
  completely unresponsive.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 30 23:03:34 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  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/1869798/+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 1869747] Re: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related.

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

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

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

** Also affects: nvidia-graphics-drivers-440 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
   Status: New => Incomplete

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

Title:
  Recent changes have caused Xorg to fail to start. Possibly nvidia
  driver related.

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I am unsure where the problem stems, but changes since the 25th have
  caused my system to fail to initialise the Xorg display. The console
  remains operational for debugging. I am currently using ZFS snapshots
  to use the system as it was on the 25th of March 2020 because that is
  the last snapshot before this issue.

  This bug was captured using ubuntu-bug when booted into the broken
  (i.e. not working) latest snapshot of my filesystem.

  The versions of packages from the not broken (i.e. correctly working)
  earlier snapshot of my filesystem are:

  libnvidia-cfg1-440:amd64 440.64-0ubuntu2
  libnvidia-common-440 440.64-0ubuntu2
  libnvidia-compute-440:amd64  440.64-0ubuntu2
  libnvidia-compute-440:i386   440.64-0ubuntu2
  libnvidia-decode-440:amd64   440.64-0ubuntu2
  libnvidia-decode-440:i386440.64-0ubuntu2
  libnvidia-encode-440:amd64   440.64-0ubuntu2
  libnvidia-encode-440:i386440.64-0ubuntu2
  libnvidia-fbc1-440:amd64 440.64-0ubuntu2
  libnvidia-fbc1-440:i386  440.64-0ubuntu2
  libnvidia-gl-440:amd64   440.64-0ubuntu2
  libnvidia-gl-440:i386440.64-0ubuntu2
  libnvidia-ifr1-440:amd64 440.64-0ubuntu2
  libnvidia-ifr1-440:i386  440.64-0ubuntu2
  nvidia-compute-utils-440 440.64-0ubuntu2
  nvidia-dkms-440  440.64-0ubuntu2
  nvidia-driver-440440.64-0ubuntu2
  nvidia-kernel-common-440 440.64-0ubuntu2
  nvidia-kernel-source-440 440.64-0ubuntu2
  nvidia-prime 0.8.14
  nvidia-settings  440.64-0ubuntu1
  nvidia-utils-440 440.64-0ubuntu2
  xserver-xorg-video-nvidia-440440.64-0ubuntu2

  $ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-3ubuntu1)
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  Date: Mon Mar 30 15:49:12 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  InstallationDate: Installed on 2020-03-03 (26 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_7176ku@/vmlinuz-5.4.0-18-generic 
root=ZFS=rpool/ROOT/ubuntu_7176ku ro quiet splash intel_iommu=on vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: American 

[Desktop-packages] [Bug 1869767] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style()

[Daniel van Vugt]

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

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 1868660, 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 1868660
   gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from 
st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() 
from g_signal_emit_valist()

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This is a clean install.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 30 18:02:01 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-03-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   st_theme_node_get_icon_style () from /usr/lib/gnome-shell/libst-1.0.so
   st_texture_cache_load_gicon () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /usr/lib/gnome-shell/libst-1.0.so
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869767/+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 1869747] Re: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related.

[Daniel van Vugt]

Yes it's a crash but the stack trace in the log is confused:

[   411.772] (EE) Backtrace:
[   411.772] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55cd86b5fd2c]
[   411.772] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) 
[0x7f3b483c341f]
[   411.773] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) 
[0x7f3b4820018b]
[   411.773] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) 
[0x7f3b481df859]
[   411.773] (EE) unw_get_proc_name failed: no unwind info found [-10]
[   411.773] (EE) 4: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so (?+0x0) 
[0x7f3b42d54375]
[   411.774] (EE) 5: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so 
(nouveau_drm_screen_create+0x203457) [0x7f3b439462f7]
[   411.774] (EE) 6: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so 
(__driDriverGetExtensions_zink+0x24ee8) [0x7f3b42da45c8]

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

Title:
  Recent changes have caused Xorg to fail to start. Possibly nvidia
  driver related.

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I am unsure where the problem stems, but changes since the 25th have
  caused my system to fail to initialise the Xorg display. The console
  remains operational for debugging. I am currently using ZFS snapshots
  to use the system as it was on the 25th of March 2020 because that is
  the last snapshot before this issue.

  This bug was captured using ubuntu-bug when booted into the broken
  (i.e. not working) latest snapshot of my filesystem.

  The versions of packages from the not broken (i.e. correctly working)
  earlier snapshot of my filesystem are:

  libnvidia-cfg1-440:amd64 440.64-0ubuntu2
  libnvidia-common-440 440.64-0ubuntu2
  libnvidia-compute-440:amd64  440.64-0ubuntu2
  libnvidia-compute-440:i386   440.64-0ubuntu2
  libnvidia-decode-440:amd64   440.64-0ubuntu2
  libnvidia-decode-440:i386440.64-0ubuntu2
  libnvidia-encode-440:amd64   440.64-0ubuntu2
  libnvidia-encode-440:i386440.64-0ubuntu2
  libnvidia-fbc1-440:amd64 440.64-0ubuntu2
  libnvidia-fbc1-440:i386  440.64-0ubuntu2
  libnvidia-gl-440:amd64   440.64-0ubuntu2
  libnvidia-gl-440:i386440.64-0ubuntu2
  libnvidia-ifr1-440:amd64 440.64-0ubuntu2
  libnvidia-ifr1-440:i386  440.64-0ubuntu2
  nvidia-compute-utils-440 440.64-0ubuntu2
  nvidia-dkms-440  440.64-0ubuntu2
  nvidia-driver-440440.64-0ubuntu2
  nvidia-kernel-common-440 440.64-0ubuntu2
  nvidia-kernel-source-440 440.64-0ubuntu2
  nvidia-prime 0.8.14
  nvidia-settings  440.64-0ubuntu1
  nvidia-utils-440 440.64-0ubuntu2
  xserver-xorg-video-nvidia-440440.64-0ubuntu2

  $ lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-3ubuntu1)
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  Date: Mon Mar 30 15:49:12 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  InstallationDate: Installed on 2020-03-03 (26 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_7176ku@/vmlinuz-5.4.0-18-generic 
root=ZFS=rpool/ROOT/ubuntu_7176ku ro quiet splash intel_iommu=on vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22g
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170X-UD5 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default 

[Desktop-packages] [Bug 1869759] Re: Opengl or vulkan or mesa bug that causes textures to glitch when mipmapping or trilinear/bilinear filtering is enabled

[Daniel van Vugt]

** Tags added: amdgpu

** Summary changed:

- Opengl or vulkan or mesa bug that causes textures to glitch when mipmapping 
or trilinear/bilinear filtering is enabled
+ [amdgpu] Opengl or vulkan or mesa bug that causes textures to glitch when 
mipmapping or trilinear/bilinear filtering is enabled

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

** Also affects: xserver-xorg-video-amdgpu (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  [amdgpu] Opengl or vulkan or mesa bug that causes textures to glitch
  when mipmapping or trilinear/bilinear filtering is enabled

Status in linux package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Textures are glitched (almost like they are cut up and repeated) when
  mipmapping or trilinear/bilinear filtering is enabled. Workaround is
  to disable both.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 30 12:03:39 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c4) (prog-if 
00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Picasso [1025:134f]
  InstallationDate: Installed on 2019-11-04 (147 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Acer Aspire A515-43
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=a44eb2b0-d036-44b7-9c90-d0a427ecd008 ro quiet splash 
resume=/dev/nvme0n1p5 resume_offset=15261696 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Grumpy_PK
  dmi.board.vendor: PK
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd09/26/2019:svnAcer:pnAspireA515-43:pvrV1.06:rvnPK:rnGrumpy_PK:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-43
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  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+git20190815-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/linux/+bug/1869759/+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 1869758] Re: Repetative problem, Random connectivity

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

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

Title:
  Repetative problem, Random connectivity

Status in Ubuntu:
  Incomplete

Bug description:
  This is a reoccurring problem. I run debug and then go to report with 
attached files and afterwards the problem temporarily clears out. It reoccurs 
upon subsequent log in and restart of computer. It also clears sometimes upon 
restart of system. It is a bug true to it's nature and nagging reoccurrence. 
Please provide a solution or debug program to cure this ill bug. Thank You J. 
Chosta
  Current OS Linux 4.4.0 141 generic, build date 10 august 2018, x protocol 
version 11

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Mar 30 11:41:14 2020
  DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] 
[1002:94c3] (prog-if 00 [VGA controller])
 Subsystem: Dell Radeon HD 2400 Pro [1028:0302]
  InstallationDate: Installed on 2016-08-03 (1335 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Dell XPS420
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic 
root=UUID=e737e1ac-8869-44b7-a03f-477223f8 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-12-25 (460 days ago)
  dmi.bios.date: 03/27/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0TP406
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd03/27/2008:svnDellInc.:pnDellXPS420:pvr:rvnDellInc.:rn0TP406:rvr:cvnDellInc.:ct7:cvr:
  dmi.product.name: Dell XPS420
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Dec 25 08:33:58 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech Logitech USB Speaker KEYBOARD, id 8
   inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9
   inputDell Dell USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1869758/+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 1869750] Re: Screens turn off when setting display scaling to 200%

[Daniel van Vugt]

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

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

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

** Summary changed:

- Screens turn off when setting display scaling to 200%
+ [nvidia] Screens turn off when setting display scaling to 200%

** Tags added: nvidia

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

Title:
  [nvidia] Screens turn off when setting display scaling to 200%

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  Issue: When setting display scaling to 200% in GNOME settings with
  proprietary nvidia drivers installed displays go to sleep until
  settings automatically revert to previous settings.

  Steps to reproduce:

  - Install proprietary nvidia drivers

  - Open GNOME settings

  - Navigate to Display settings

  - Set display scaling to 200%

  
  NOTE: This issue has been solved in upstream mutter git master branch. 
Confirmed on both Arch and Fedora packages that have been created from mutter 
master branch.

  GPU: GeForce GTX 1080 Ti
  Driver: 440.64

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mutter 3.36.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 30 11:01:56 2020
  InstallationDate: Installed on 2020-03-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1869750/+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 1869819] [NEW] System can't detect external headset in the codec of Conexant

[hugh chao]

Public bug reported:

[Impact]
In some hp's devices, there are two audio jacks(one headset and one headphone) 
in the audio interface which is using the codec of Conexant, and apparently 
it's not working, the system can't detect the headset in current codec.

[Test Case]
1. Insert 3-ring headset into front audio port (headset icon)
2. Check System Setting->Sound->Output

[Expected result]
Can detect external headset

[Actual result]
Only shows internal speaker.
External headset microphone was detected.
Another front audio port (earphone icon) works fine.

[Regression Potential]

[Failure rate]
100%

[Additional information]
system-product-name: HP EliteDesk 800 G5 SFF
CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
OS-version: 18.04
kernel-version: 4.15.0-1065-oem
pulseaudio-version: 1:11.1-1ubuntu7.2

Upstream Bug:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

** Affects: oem-priority
 Importance: Critical
 Assignee: hugh chao (hugh712)
 Status: Confirmed

** Affects: oem-priority/bionic
 Importance: Undecided
 Status: New

** Package changed: pulseaudio (Ubuntu) => oem-priority

** Changed in: oem-priority
 Assignee: (unassigned) => hugh chao (hugh712)

** Also affects: oem-priority/bionic
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Status: New => Confirmed

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 3-ring headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream Bug:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1869814] Re: ubuntu-docs build failure - possible solution

[Gunnar Hjalmarsson]

Hmm.. I saw in the buildlog from the successful build that it skipped
the Chinese translation of a particular string. The reason proved to be
a missing '<' character, i.e. the translated string contains an instance
of '/em>' instead of ''. And that's the correct behavior; it should
check the Mallard syntax and skip translations with invalid syntax.

Anyway, I added the missing '<', and then ubuntu-docs built with the
itstool version in focal.

So the direct reason for the build failure is a syntactically incorrect
translation. OTOH, translators make mistakes, and a bad translation
*should not* make the whole package build to fail.

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

Title:
  ubuntu-docs build failure - possible solution

Status in itstool package in Ubuntu:
  New
Status in libxml2 package in Ubuntu:
  New
Status in ubuntu-docs package in Ubuntu:
  New

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1869706] [NEW] Plymouth with Nvidia Drivers causes login loop at GDM

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Summary :-
  
Login loop on GDM after installing nvidia drivers using ubuntu-drivers 
autoinstall sript.

Hardware :- Nvidia GTX 1070 with a Intel Core i7 7700 HQ. HP OMEN 2017
Laptop.

Steps to reproduce :-

Simply install nvidia drivers using ubuntu-drivers autoinstall script.


Expected behaviour :- seamless autologin to desktop, 

Observed behaviour:- GDM refuses to login automatically and then any
attempts of logging in by entering password just simply fail. Hence
login loop.

Only known mitigation is :- remove the splash from the
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" in /etc/default grub and
update-grub before installing nvidia drivers, Or chroot into the system
after reproducing the error and remove "splash"

This bug has been in existence since Ubuntu 19.10, Wanted to ensure this
was reported here for resolution.

Happy to provide further information if required.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: plymouth 0.9.4git20200323-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 30 16:24:42 2020
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
InstallationDate: Installed on 2020-03-30 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
MachineType: HP OMEN by HP Laptop
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=fed3e7a0-e171-4fe1-a43e-4c6e9292aacd ro quiet mitigations=off
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=fed3e7a0-e171-4fe1-a43e-4c6e9292aacd ro quiet mitigations=off
SourcePackage: plymouth
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/22/2018
dmi.bios.vendor: Insyde
dmi.bios.version: F.48
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8261
dmi.board.vendor: HP
dmi.board.version: 83.72
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.48:bd06/22/2018:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8261:rvr83.72:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Omen
dmi.product.name: OMEN by HP Laptop
dmi.product.sku: 1HQ37PA#ACJ
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug focal
-- 
Plymouth with Nvidia Drivers causes login loop at GDM
https://bugs.launchpad.net/bugs/1869706
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gdm3 in Ubuntu.

-- 
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 1869820] [NEW] Missing dependency: gnome-shell-extension-prefs

[Dylan Taylor]

Public bug reported:

Dash to Dock settings does not work on a stock Ubuntu 20.04 (Focal)
installation. If you right click the "Show Applications",  click
settings, it'll trigger an error indicating gnome-shell-extension-prefs
is missing. Installing this package resolves the issue. This package
should be a dependency of gnome-shell-extension-ubuntu-dock.

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

** Attachment added: "Screenshot from 2020-03-30 22-33-43.png"
   
https://bugs.launchpad.net/bugs/1869820/+attachment/5343582/+files/Screenshot%20from%202020-03-30%2022-33-43.png

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

Title:
  Missing dependency: gnome-shell-extension-prefs

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  Dash to Dock settings does not work on a stock Ubuntu 20.04 (Focal)
  installation. If you right click the "Show Applications",  click
  settings, it'll trigger an error indicating gnome-shell-extension-
  prefs is missing. Installing this package resolves the issue. This
  package should be a dependency of gnome-shell-extension-ubuntu-dock.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1869820/+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 1867757] Re: Please pull Mutter cursor fixes for DisplayLink devices

[Daniel van Vugt]

The repo you are talking about is:

  https://salsa.debian.org/gnome-team/mutter/-/tree/ubuntu/master

but that's not what I was referring to. I was referring to upstream:

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

Since we are extremely confident that Ubuntu will receive mutter version
3.36.1 it qualifies as Fix Committed, where that commit is presently
upstream only.

The policy is not written down but was requested by seb128 (engineering
manager).

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

Title:
  Please pull Mutter cursor fixes for DisplayLink devices

Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  For GNOME/Wayland to use hardware cursors on DisplayLink devices
  (proprietary userspace driver for USB 3 devices), the following Mutter
  fixes should be included:

  Mutter 3.34 branch (tentatively 3.34.5):
  - https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1116 Initialize 
cursor support on GPU hotplug (backport to 3.34)

  Mutter 3.36 (currently master) branch (tentatively 3.36.1):
  - https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1079 Handle lack of 
explicit cursor planes better
  - https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1097 Initialize 
cursor support on GPU hotplug

  Without "Initialize cursor support on GPU hotplug" performance on
  hotplugged DisplayLink devices that create a new DRM device node
  suffers, because Mutter uses a software cursor which implies that
  DisplayLink needs to update the whole screen on every cursor motion.

  Without "Handle lack of explicit cursor planes better" there will not
  be a cursor at all on DisplayLink devices in Mutter 3.36.

  I would assume that the 3.34 branch is relevant to Ubuntu 19.10 and
  the 3.36 branch is relevant to Ubuntu 20.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1867757/+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 1868332] Re: Scrolling jumps after switching windows

[Daniel van Vugt]

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

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

Title:
  Scrolling jumps after switching windows

Status in mutter package in Ubuntu:
  New

Bug description:
  The bug has to do with mouse scrolling and switching windows; I do not
  know which package it is part of.

  The problem arises when I have two windows of two different
  applications open, such as Google Chrome and a text editor. To
  reproduce the error, I have Google Chrome open initially, then I
  switch tabs (using the shortcut Alt-Tab) to the text editor, then
  scroll around on the text editor. When I Alt-Tab back to Google
  Chrome, my first scroll leads to the page jumping by a large amount
  either up or down before resuming regular mouse scrolling. It is only
  this initial scroll after switching tabs that jumps like this. It also
  happens regardless of whether I use a mouse or the touch pad.

  I also notice, given the same scenario, if I scroll up on the text
  editor, the Google Chrome initial scroll jump will be upward. If I
  scroll down on the text editor, the Chrome jump will be downward. If I
  scroll a lot in the text editor, the Chrome jump will be large. If I
  scroll a small amount in the text editor, the Chrome jump will be
  small.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 20 17:17:39 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b9]
  InstallationDate: Installed on 2020-01-26 (54 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=7cfa547e-7b38-4467-9a1c-5f581ce738c1 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.24
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.43
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.24:bd01/07/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.product.sku: 1WU65AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1868332/+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 1869814] Re: ubuntu-docs build failure - possible solution

[Gunnar Hjalmarsson]

@Boyuan: Do you have any thoughts on the above?

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

Title:
  ubuntu-docs build failure - possible solution

Status in itstool package in Ubuntu:
  New
Status in libxml2 package in Ubuntu:
  New
Status in ubuntu-docs package in Ubuntu:
  New

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

[Daniel van Vugt]

** Tags added: eoan focal

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

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

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

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.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/gnome-shell/+bug/1181666/+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 1869814] [NEW] ubuntu-docs build failure - possible solution

[Gunnar Hjalmarsson]

Public bug reported:

ubuntu-docs failed to build during the second Focal Fossa test rebuild:

https://launchpad.net/ubuntu/+archive/test-
rebuild-20200327-focal/+build/18982738

It was itstool which failed to generate the localized zh_CN pages. If
dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
excluding the Chinese pages is apparently not an acceptable solution.

The itstool package in focal {build-,}depends on python3. I built
itstool in a PPA with python2 instead, and in that PPA ubuntu-docs built
fine without modifications:

https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages

So the root cause seems to lie neither in ubuntu-docs nor itstool. I
would suspect that python3-libxml2 is buggy, but since itstool was built
against python2 in eoan, it's hard to tell if it's a regression.

Would building itstool against python2 be an acceptable workaround in
focal?

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

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

** Affects: ubuntu-docs (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

Title:
  ubuntu-docs build failure - possible solution

Status in itstool package in Ubuntu:
  New
Status in libxml2 package in Ubuntu:
  New
Status in ubuntu-docs package in Ubuntu:
  New

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1864253] Re: Pulseaudio sink/source selection, weird behaviour.

[Daniel van Vugt]

** No longer affects: pulseaudio

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

Title:
  Pulseaudio sink/source selection, weird behaviour.

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I have a Laptop connected to an USB-C dock. By default the docks analog
  audio output is chosen as the default pulse audio sink. I want that the
  analog output of the Laptop is the default, hence I configured this in
  /etc/pulse/default.py

  This does not work and journalctl informs me that the device chosen by me
  (alsa_output.pci-_00_1f.3.analog-stereo) does not exist, see attached 
output
  from journalctl.

  I have followed Workaround 1 here https://wiki.debian.org/BluetoothUser/a2dp
  to prevent pulseaudio getting started in gdm to prevent device capture.

  This does not work, the device does still not exist.
  Restarting pulseaudio sometimes, but not always sets the configured
  default sink. Furthermore plugging in the headphones in the Laptops analog 
input
  switches audio to the dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.4
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-28-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  findus 3055 F pulseaudio
   /dev/snd/controlC1:  findus 3055 F pulseaudio
   /dev/snd/controlC0:  findus 3055 F pulseaudio
   /dev/snd/pcmC0D0p:   findus 3055 F...m pulseaudio
  CurrentDesktop: i3
  Date: Fri Feb 21 22:19:04 2020
  InstallationDate: Installed on 2019-06-13 (253 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2IET80W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20N3S0UB00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2IET80W(1.58):bd11/26/2019:svnLENOVO:pn20N3S0UB00:pvrThinkPadT490:rvnLENOVO:rn20N3S0UB00:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T490
  dmi.product.name: 20N3S0UB00
  dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490
  dmi.product.version: ThinkPad T490
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  modified.conffile..etc.pulse.system.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2020-02-21T20:38:20.081439
  mtime.conffile..etc.pulse.default.pa: 2020-02-21T19:27:57.386938
  mtime.conffile..etc.pulse.system.pa: 2020-02-21T15:23:09.470494

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1864253/+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 1869520] Re: the windows hang after Alt+Tab or/and minimizing

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1868911
   Exiting overview causes windows from other workspaces to be visible

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

Title:
  the windows hang after Alt+Tab or/and minimizing

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When I want to shift open windows, like files, browsers, etc. they
  freeze and hang and I can neither minimize nor close that window.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 28 21:05:02 2020
  DistUpgraded: 2020-03-26 22:02:16,208 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.4, 5.3.0-42-generic, x86_64: installed
   virtualbox, 6.1.4, 5.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 
560/560X] [1002:67ff] (rev cf) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon RX 560 [1043:04bc]
  InstallationDate: Installed on 2020-02-02 (55 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. AB350M-Gaming 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=5909a9b7-eb21-439d-a04c-2c42bf662b3c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-03-26 (1 days ago)
  dmi.bios.date: 05/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F31
  dmi.board.asset.tag: Default string
  dmi.board.name: AB350M-Gaming 3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF31:bd05/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AB350M-Gaming 3
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  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+git20190815-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/gnome-shell/+bug/1869520/+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 1868116] Re: QEMU monitor no longer works

[Bug Watch Updater]

** Changed in: qemu (Debian)
   Status: Unknown => New

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

Title:
  QEMU monitor no longer works

Status in QEMU:
  New
Status in qemu package in Ubuntu:
  Triaged
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in qemu package in Debian:
  New

Bug description:
  Repro:
  VTE
  $ meson _build && ninja -C _build && ninja -C _build install

  qemu:
  $ ../configure --python=/usr/bin/python3 --disable-werror --disable-user 
--disable-linux-user --disable-docs --disable-guest-agent --disable-sdl 
--enable-gtk --disable-vnc --disable-xen --disable-brlapi --disable-fdt 
--disable-hax --disable-vde --disable-netmap --disable-rbd --disable-libiscsi 
--disable-libnfs --disable-smartcard --disable-libusb --disable-usb-redir 
--disable-seccomp --disable-glusterfs --disable-tpm --disable-numa 
--disable-opengl --disable-virglrenderer --disable-xfsctl --disable-vxhs 
--disable-slirp --disable-blobs --target-list=x86_64-softmmu --disable-rdma 
--disable-pvrdma --disable-attr --disable-vhost-net --disable-vhost-vsock 
--disable-vhost-scsi --disable-vhost-crypto --disable-vhost-user 
--disable-spice --disable-qom-cast-debug --disable-vxhs --disable-bochs 
--disable-cloop --disable-dmg --disable-qcow1 --disable-vdi --disable-vvfat 
--disable-qed --disable-parallels --disable-sheepdog --disable-avx2 
--disable-nettle --disable-gnutls --disable-capstone --disable-tools 
--disable-libpmem --disable-iconv --disable-cap-ng
  $ make

  Test:
  $ LD_LIBRARY_PATH=/usr/local/lib/x86_64-linux-gnu/:$LD_LIBRARY_PATH 
./build/x86_64-softmmu/qemu-system-x86_64 -enable-kvm --drive 
media=cdrom,file=http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/mini.iso
  - switch to monitor with CTRL+ALT+2
  - try to enter something

  Affects head of both usptream git repos.

  
  --- original bug ---

  It was observed that the QEMU console (normally accessible using
  Ctrl+Alt+2) accepts no input, so it can't be used. This is being
  problematic because there are cases where it's required to send
  commands to the guest, or key combinations that the host would grab
  (as Ctrl-Alt-F1 or Alt-F4).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: qemu 1:4.2-3ubuntu2
  Uname: Linux 5.6.0-rc6+ x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 12:16:31 2020
  Dependencies:

  InstallationDate: Installed on 2017-06-13 (1009 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  KvmCmdLine:
   COMMAND STAT  EUID  RUID PIDPPID %CPU COMMAND
   qemu-system-x86 Sl+   1000  1000   34275   25235 29.2 qemu-system-x86_64 -m 
4G -cpu Skylake-Client -device virtio-vga,virgl=true,xres=1280,yres=720 -accel 
kvm -device nec-usb-xhci -serial vc -serial stdio -hda 
/home/usuario/Sistemas/androidx86.img -display gtk,gl=on -device usb-audio
   kvm-nx-lpage-re S0 0   34284   2  0.0 [kvm-nx-lpage-re]
   kvm-pit/34275   S0 0   34286   2  0.0 [kvm-pit/34275]
  MachineType: LENOVO 80UG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-rc6+ 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 
i915.enable_gvt=1 i915.fastboot=1 cgroup_enable=memory swapaccount=1 
zswap.enabled=1 zswap.zpool=z3fold 
resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=16M 
usbhid.quirks=0x0079:0x0006:0x10 config_scsi_mq_default=y 
scsi_mod.use_blk_mq=1 mtrr_gran_size=64M mtrr_chunk_size=64M nbd.nbds_max=2 
nbd.max_part=63
  SourcePackage: qemu
  UpgradeStatus: Upgraded to focal on 2019-12-22 (87 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  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 310-14ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80UG
  dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK
  dmi.product.version: Lenovo ideapad 310-14ISK
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1868116/+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 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher

[psymin]

Tested with libpango-1.0-0_1.44.7-2ubuntu2_amd64.deb and
libpango-1.0-0_1.44.7-2ubuntu2_i386.deb from #8 above.

Worked for Minecraft.deb on Xubuntu

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

Title:
  Removing  libpango1.0-0  broke Minecraft Launcher

Status in pango1.0 package in Ubuntu:
  Fix Committed

Bug description:
  I just updated my machine, and when I did libpango1.0-0 was removed.
  This removed minecraft-launcher - the (very) popular launcher for
  Minecraft Java edition.

  I have reported this upstream, in case they can update their package
  https://bugs.mojang.com/browse/MCL-13512

  I am filing this bug so we can track it internally. I personally think
  this shouldn't have been done this late in the cycle, but there may
  well have been good reasons for it.

  As a result of the change though, it's now not possible to install
  Minecraft on Ubuntu 20.04.

  $ sudo apt install ./Minecraft\(1\).deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher

[Bill (franksmcb)]

Tested with latest packages in proposed Ubuntu MATE and able to install
and use balena-etcher-electron.

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

Title:
  Removing  libpango1.0-0  broke Minecraft Launcher

Status in pango1.0 package in Ubuntu:
  Fix Committed

Bug description:
  I just updated my machine, and when I did libpango1.0-0 was removed.
  This removed minecraft-launcher - the (very) popular launcher for
  Minecraft Java edition.

  I have reported this upstream, in case they can update their package
  https://bugs.mojang.com/browse/MCL-13512

  I am filing this bug so we can track it internally. I personally think
  this shouldn't have been done this late in the cycle, but there may
  well have been good reasons for it.

  As a result of the change though, it's now not possible to install
  Minecraft on Ubuntu 20.04.

  $ sudo apt install ./Minecraft\(1\).deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group

[Bug Watch Updater]

** Changed in: libmtp (Debian)
   Status: Unknown => Fix Released

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

Title:
  /dev/bus/usb/*/* device file of HP multi-function printer assigned to
  "audio" group

Status in libmtp package in Ubuntu:
  Fix Released
Status in libmtp package in Debian:
  Fix Released

Bug description:
  When testing HPLIP I found out that CUPS backends can access my
  printer only when they are running as root, when they are running as
  the special user lp, as it is usually the case, they cannot access the
  printer.

  So I tried to find out why and saw that the /dev/bus/usb/*/* device
  file for the printer has group ownership "audio" and not "lp":

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll 
/dev/bus/usb/*/*
  crw-rw-r--  1 root root189,   0 Feb 11 14:17 /dev/bus/usb/001/001
  crw-rw-r--  1 root root189,   2 Feb 11 14:17 /dev/bus/usb/001/003
  crw-rw-r--  1 root root189,   3 Feb 11 14:17 /dev/bus/usb/001/004
  crw-rw-r--  1 root plugdev 189,   4 Feb 14 12:23 /dev/bus/usb/001/005
  crw-rw-r--  1 root root189,   5 Feb 11 14:17 /dev/bus/usb/001/006
  crw-rw+ 1 root audio   189,  62 Feb 14 12:37 /dev/bus/usb/001/063
  crw-rw-r--  1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001
  crw-rw-r--  1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$

  The printer is the device /dev/bus/usb/001/063:

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb
  Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit 
Ethernet
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. 
  Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated 
Camera
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
  Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor
  Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ 

  There must be a bug somewhere in the UDEV rules.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1863239/+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 1865278] Re: Update to tracker 2.3.2 in Focal

[Bug Watch Updater]

** Changed in: tracker (Debian)
   Status: Unknown => Fix Released

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

Title:
  Update to tracker 2.3.2 in Focal

Status in tracker package in Ubuntu:
  Fix Released
Status in tracker package in Debian:
  Fix Released

Bug description:
  2.3.2 is a small bug-fix release.

  https://gitlab.gnome.org/GNOME/tracker/-/blob/tracker-2.3/NEWS

  NEW in 2.3.2 - 2020-02-18
  =

* Location info for photos is now inserted into the DB. It didn't
  work before as we failed to process SPARQL "blank nodes" correctly.
* Fix for oversensitive FTS5 index corruption detection

  Translations: ms

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

Re: [Desktop-packages] [Bug 1852183]

[ethanay]

This bug occurs in Pop!_OS 19.10 for me with or without a clipboard manager
installed.

In addition, when I do have a clipboard manager installed, it occurs BEFORE
any clipboard manager i tried receives any information about what I tried
to copy or paste, so seems inaccurate to me that blaming a clipboard
manager will get to the root issue.

Ethan


On Mon, Mar 30, 2020, 07:10 Eike Rathke <1852...@bugs.launchpad.net> wrote:

> Does it even occur on Windows? If so, that would be a different cause
> (though highly likely some clipboard destroyer (AKA "manager") involved
> then as well).
> I'm marking this as not-All., i.e. Linux.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1852183
>
> Title:
>   [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04
>
> Status in LibreOffice:
>   Confirmed
> Status in Mutter:
>   Fix Released
> Status in codelite package in Ubuntu:
>   Confirmed
> Status in libreoffice package in Ubuntu:
>   Triaged
> Status in mutter package in Ubuntu:
>   Fix Released
> Status in codelite source package in Eoan:
>   Confirmed
> Status in libreoffice source package in Eoan:
>   Triaged
> Status in mutter source package in Eoan:
>   Triaged
> Status in codelite source package in Focal:
>   Confirmed
> Status in libreoffice source package in Focal:
>   Triaged
> Status in mutter source package in Focal:
>   Fix Released
>
> Bug description:
>   I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.
>
>   In this environment, copy/cut/paste often fails.  Specifically, the
>   paste command sometimes does not paste the text that was cut/copied
>   most recently.  Instead, it pastes text that was cut/copied at some
>   prior time.
>
>   I use LibreOffice Writer a lot, and I now see this problem very often,
>   i.e. many times every day.
>
>   There is some discussion of the problem here:
>
>  https://ask.libreoffice.org/en/question/213510/copypaste-issues-
>   libreoffice-calc/
>
>   Several posters there say that they are also using Ubuntu 19.10.
>
>   Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:
>
>  https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
>   -Clipboard-Manager
>
>   It seems like that could be related.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions
>

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

Title:
  [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04

Status in LibreOffice:
  Confirmed
Status in Mutter:
  Fix Released
Status in codelite package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Fix Released
Status in codelite source package in Eoan:
  Confirmed
Status in libreoffice source package in Eoan:
  Triaged
Status in mutter source package in Eoan:
  Triaged
Status in codelite source package in Focal:
  Confirmed
Status in libreoffice source package in Focal:
  Triaged
Status in mutter source package in Focal:
  Fix Released

Bug description:
  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  I use LibreOffice Writer a lot, and I now see this problem very often,
  i.e. many times every day.

  There is some discussion of the problem here:

 https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

 https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+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 1868896] Re: Minimized windows reappear when closing the overview

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 3.36.0-2ubuntu2

---
gnome-shell (3.36.0-2ubuntu2) focal; urgency=medium

  * d/p/overview-Fade-in-out-over-the-desktop-instead-of-replacin.patch:
- Drop patch to fade in/out the desktop instead of replacing it, it causes
  some bugs. (LP: #1868896, #1868911)
  * d/p/keyboard-Don-t-include-keyboard-devices-when-updating-las.patch,
d/p/keyboard-Hide-keyboardBox-after-destroying-the-keyboard.patch,
d/p/layout-Use-translation_y-of-0-to-hide-keyboard.patch:
- Fix OSK leaves dask mask after being hidden (LP: #1845623)

 -- Marco Trevisan (Treviño)   Mon, 30 Mar 2020
17:49:05 +0100

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

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

Title:
  Minimized windows reappear when closing the overview

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  I just ran all of the updates for 20.04 on two machines, and both
  machines experience the same issue.

  Items do not appear to stay "minimized". For instance, you can
  minimize Thunderbird, and it appears to re-maximize itself. However,
  you cannot click on anything in the maximized window, but you can re-
  minimize it (that button does work), then click the dock to bring it
  back out and it functions properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 24 18:11:35 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
     Subsystem: Dell Iris Plus Graphics G7 [1028:096d]
  InstallationDate: Installed on 2020-03-11 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200311)
  MachineType: Dell Inc. XPS 13 9300
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vp1gr9@/vmlinuz-5.4.0-18-generic 
root=ZFS=rpool/ROOT/ubuntu_vp1gr9 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.6
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.6:bd01/17/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  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+git20190815-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/gnome-shell/+bug/1868896/+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 1845623] Re: on screen keyboard leaves dark marks on screen after being hidden

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 3.36.0-2ubuntu2

---
gnome-shell (3.36.0-2ubuntu2) focal; urgency=medium

  * d/p/overview-Fade-in-out-over-the-desktop-instead-of-replacin.patch:
- Drop patch to fade in/out the desktop instead of replacing it, it causes
  some bugs. (LP: #1868896, #1868911)
  * d/p/keyboard-Don-t-include-keyboard-devices-when-updating-las.patch,
d/p/keyboard-Hide-keyboardBox-after-destroying-the-keyboard.patch,
d/p/layout-Use-translation_y-of-0-to-hide-keyboard.patch:
- Fix OSK leaves dask mask after being hidden (LP: #1845623)

 -- Marco Trevisan (Treviño)   Mon, 30 Mar 2020
17:49:05 +0100

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

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

Title:
  on screen keyboard leaves dark marks on screen after being hidden

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Image: 19.10 beta – 
http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso
  Device: Dell XPS 13 7390 (201908-27305)

  Steps to reproduce:
  1. Make the on-screen keyboard appear by tapping on a text field on doing a 
swipe up on the screen with your finger (see video).
  2. Tap the arrow down key to hide the OSK

  Expected result: the OSK disappears

  Actual result: The OSK leaves dark traces on the sides of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 17:51:29 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-27 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  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/1845623/+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 1868911] Re: Exiting overview causes windows from other workspaces to be visible

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 3.36.0-2ubuntu2

---
gnome-shell (3.36.0-2ubuntu2) focal; urgency=medium

  * d/p/overview-Fade-in-out-over-the-desktop-instead-of-replacin.patch:
- Drop patch to fade in/out the desktop instead of replacing it, it causes
  some bugs. (LP: #1868896, #1868911)
  * d/p/keyboard-Don-t-include-keyboard-devices-when-updating-las.patch,
d/p/keyboard-Hide-keyboardBox-after-destroying-the-keyboard.patch,
d/p/layout-Use-translation_y-of-0-to-hide-keyboard.patch:
- Fix OSK leaves dask mask after being hidden (LP: #1845623)

 -- Marco Trevisan (Treviño)   Mon, 30 Mar 2020
17:49:05 +0100

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

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

Title:
  Exiting overview causes windows from other workspaces to be visible

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  $ dpkg-query -W gnome-shell
  gnome-shell 3.36.0-2ubuntu1
  $ lsb_release -rc
  Release:20.04
  Codename:   focal
  $ _ 

  
  When I toggle in and out of the overview on an empty workspace, windows from 
other workspaces appear.  They are not interactable, so this seems more like a 
rendering bug than the windows really being teleported to another workspace.  
Switching back to another workspace that has windows causes the ghost windows 
to disappear.  Opening a window in the empty workspace makes it appear on top 
of the ghost windows, and I have to switch to another workspace and back again 
to make only the new window be visible.

  I am using the vanilla "GNOME" session type.  I did not observe this
  behaviour with gnome-shell 3.35.91-1ubuntu2.

  As well as the annoyance factor, of course there's a privacy angle to showing 
random windows at surprising times.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2011-11-06 (3062 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: gnome-shell 3.36.0-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Tags: wayland-session focal third-party-packages
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-25 (29 days ago)
  UserGroups: adm admin cdrom dialout docker libvirt lpadmin lxd plugdev 
sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868911/+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 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher

[Alan Pope  濾]

Tested with the latest packages in proposed and it's fixed, I can now
install and play Minecraft. Thank you! <3

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

Title:
  Removing  libpango1.0-0  broke Minecraft Launcher

Status in pango1.0 package in Ubuntu:
  Fix Committed

Bug description:
  I just updated my machine, and when I did libpango1.0-0 was removed.
  This removed minecraft-launcher - the (very) popular launcher for
  Minecraft Java edition.

  I have reported this upstream, in case they can update their package
  https://bugs.mojang.com/browse/MCL-13512

  I am filing this bug so we can track it internally. I personally think
  this shouldn't have been done this late in the cycle, but there may
  well have been good reasons for it.

  As a result of the change though, it's now not possible to install
  Minecraft on Ubuntu 20.04.

  $ sudo apt install ./Minecraft\(1\).deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1835220] Re: Please support /usr/lib64/sane

[Bug Watch Updater]

** Changed in: sane-backends (Debian)
   Status: Fix Committed => Fix Released

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

Title:
  Please support /usr/lib64/sane

Status in sane-backends package in Ubuntu:
  Confirmed
Status in sane-backends package in Debian:
  Fix Released

Bug description:
  The patch 0125-multiarch_dll_search_path.patch makes /usr/lib/sane be
  recognized as a directory for SANE backends. However, some .deb files
  with scanner drivers, typically provided by Brother, install files in
  /usr/lib64/sane. It would be great if that directory could be
  supported too.

  This issue has been discussed in bug #1728012, but was broken out from
  there to not block another more important change in bionic.

  If Debian accepts the proposal in ,
  the change is a SRU candidate to bionic at first hand.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1835220/+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 1865314] Re: Suggest removal of xkeystone

[Bug Watch Updater]

** Changed in: x11-xserver-utils (Debian)
   Status: Unknown => New

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

Title:
  Suggest removal of xkeystone

Status in x11-xserver-utils package in Ubuntu:
  New
Status in x11-xserver-utils package in Debian:
  New

Bug description:
  Originally posted this as a question
  https://answers.launchpad.net/ubuntu/+question/689060 and was directed
  here.

  x11-xserver-utils includes the script /usr/bin/xkeystone

  xkeystone is a nickle script, and x11-xserver-utils does not depend on
  nickle, and even if you install nickle the script fails with a massive
  amount of syntax errors. (as tested with both bionic and focal
  packages).

  It's not clear to me what xkeystone is supposed to do - there's no man
  page or any documentation I could find. The only thing I was able to
  find are various threads where other distros remove this binary, so I
  suggest we remove it from ubuntu as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/1865314/+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 1869524] Re: Simple Scan doesn't load

[Charles]

That did it!  "Bug" fixed. :)  Thanks Bartosz!

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

Title:
  Simple Scan doesn't load

Status in simple-scan package in Ubuntu:
  Incomplete

Bug description:
  Simple Scan version 3.28.0-0ubuntu1 fails to load in Ubuntu 18.04 LTS

  simple-scan: error while loading shared libraries: libcolord.so.1:
  cannot open shared object file: No such file or directory

  Related to bug# 1869522
  https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1869522

  Not sure if I should be reporting the bug against Simple Scan, Gnome,
  or Ubuntu 18.04 LTS.

  Gnome project said it's not a bug with Simple Scan.  Something about not 
having the latest version of Gnome bundled with Ubuntu 18.04 LTS.
  https://gitlab.gnome.org/GNOME/simple-scan/-/issues/159

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: simple-scan 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 28 15:53:47 2020
  InstallationDate: Installed on 2014-08-08 (2059 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: MSI MS-7922
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic 
root=UUID=12cc7d65-8589-4aab-a77b-566ea7af9984 ro pci=assign-busses quiet 
splash vt.handoff=1
  SimpleScanLog:
   
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to bionic on 2020-01-05 (83 days ago)
  dmi.bios.date: 02/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 U3 PLUS (MS-7922)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.10:bd02/16/2016:svnMSI:pnMS-7922:pvr1.0:rvnMSI:rnZ97U3PLUS(MS-7922):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7922
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1869524/+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 1868332] Re: Scrolling jumps after switching windows

[Marco Gellecanao]

Thank you for the response. Also, this bug actually applies regardless
of what apps I am using, and I was just using Chrome as an example.

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

Title:
  Scrolling jumps after switching windows

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  The bug has to do with mouse scrolling and switching windows; I do not
  know which package it is part of.

  The problem arises when I have two windows of two different
  applications open, such as Google Chrome and a text editor. To
  reproduce the error, I have Google Chrome open initially, then I
  switch tabs (using the shortcut Alt-Tab) to the text editor, then
  scroll around on the text editor. When I Alt-Tab back to Google
  Chrome, my first scroll leads to the page jumping by a large amount
  either up or down before resuming regular mouse scrolling. It is only
  this initial scroll after switching tabs that jumps like this. It also
  happens regardless of whether I use a mouse or the touch pad.

  I also notice, given the same scenario, if I scroll up on the text
  editor, the Google Chrome initial scroll jump will be upward. If I
  scroll down on the text editor, the Chrome jump will be downward. If I
  scroll a lot in the text editor, the Chrome jump will be large. If I
  scroll a small amount in the text editor, the Chrome jump will be
  small.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 20 17:17:39 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b9]
  InstallationDate: Installed on 2020-01-26 (54 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=7cfa547e-7b38-4467-9a1c-5f581ce738c1 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.24
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.43
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.24:bd01/07/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.product.sku: 1WU65AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1868332/+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 1869803] Re: [HDA-Intel - HDA Intel PCH, recording] Recording problem, internal mic and headset mic not listed

[Arnaud Tardif]

Do not care about USB device, I bought a USB mic for lockdown and it
works via USB.

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

Title:
  [HDA-Intel - HDA Intel PCH, recording] Recording problem, internal mic
  and headset mic not listed

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi, my dell laptop inspiron 15 5590 not working properly, internal mic
  is not listed in inputs and headset mic neither. I tested headset mic
  on other devices and it works fine. Also when I plug headset in in/out
  jack, ubuntu doesn't ask for connection type (headset, headset mic,
  mic) it use it only as simple headset.

  I tried some configuration in alsa and HDAJackRetask but none works.
  Same for kernels, 4.15.x, 5.0.x (oem), 5.3.x none works.

  I didn't test mics under windows because I can't for the moment.

  If you need details, I'll be glad to copy/paste your commands in
  terminal.

  Infos:
  Ubuntu 19.10
  kernel: 5.3.0-29-generic
  alsa-base: 1.0.25+dfsg-0ubuntu5

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nonot  2648 F pulseaudio
   /dev/snd/pcmC1D0c:   nonot  2648 F...m pulseaudio
   /dev/snd/controlC0:  nonot  2648 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 30 23:34:18 2020
  InstallationDate: Installed on 2020-01-07 (83 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 1 4 9 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: USB PnP Audio Device(EEPROM) - USB PnP Audio Device(EEPROM)
  Symptom_Type: Only some of inputs are working
  Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/14/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 03P485
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd01/14/2020:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn03P485:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-03-25T16:08:59.064986

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1869803/+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 1869288] Re: "Privacy" tab in gnome-control-center is not findable

[Sebastien Bacher]

@Gunnar, it's probably worth reporting upstream for discussion.

The code adding the keywords seems to be there
https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/master/shell/cc-shell-model.c#L241

you could imagine doing a

if panel = 'name' or 'othername'; then

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

Title:
  "Privacy" tab in gnome-control-center is not findable

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  Searching for "Privacy" using gnome-control-center search bar returns
  the  "Search" tab instead of the "Privacy" tab. The same thing happens
  with Gnome Shell Search.

  For all the other tab names of gnome-control-center it works as
  expected, including Privacy's sub tabs. I've tested using EN and PT-BR
  languages, and it happens in both.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.0-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27
  Uname: Linux 5.4.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 26 23:42:26 2020
  InstallationDate: Installed on 2020-03-08 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304)
  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/1869288/+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 1869288] Re: "Privacy" tab in gnome-control-center is not findable

[Sebastien Bacher]

if panel = 'name' or 'othername' or 'thirpanel'; then
keywords += _('Privacy')

(pseudo code to give the idea)

That seems hackish though, probably best to just propose your patch
adding the keywords upstream for next cycle

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

Title:
  "Privacy" tab in gnome-control-center is not findable

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  Searching for "Privacy" using gnome-control-center search bar returns
  the  "Search" tab instead of the "Privacy" tab. The same thing happens
  with Gnome Shell Search.

  For all the other tab names of gnome-control-center it works as
  expected, including Privacy's sub tabs. I've tested using EN and PT-BR
  languages, and it happens in both.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.0-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27
  Uname: Linux 5.4.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 26 23:42:26 2020
  InstallationDate: Installed on 2020-03-08 (18 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304)
  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/1869288/+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 1869803] [NEW] [HDA-Intel - HDA Intel PCH, recording] Recording problem, internal mic and headset mic not listed

[Arnaud Tardif]

Public bug reported:

Hi, my dell laptop inspiron 15 5590 not working properly, internal mic
is not listed in inputs and headset mic neither. I tested headset mic on
other devices and it works fine. Also when I plug headset in in/out
jack, ubuntu doesn't ask for connection type (headset, headset mic, mic)
it use it only as simple headset.

I tried some configuration in alsa and HDAJackRetask but none works.
Same for kernels, 4.15.x, 5.0.x (oem), 5.3.x none works.

I didn't test mics under windows because I can't for the moment.

If you need details, I'll be glad to copy/paste your commands in
terminal.

Infos:
Ubuntu 19.10
kernel: 5.3.0-29-generic
alsa-base: 1.0.25+dfsg-0ubuntu5

Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  nonot  2648 F pulseaudio
 /dev/snd/pcmC1D0c:   nonot  2648 F...m pulseaudio
 /dev/snd/controlC0:  nonot  2648 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 30 23:34:18 2020
InstallationDate: Installed on 2020-01-07 (83 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 1 4 9 :  
 r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
Symptom_Card: USB PnP Audio Device(EEPROM) - USB PnP Audio Device(EEPROM)
Symptom_Type: Only some of inputs are working
Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/14/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.1
dmi.board.name: 03P485
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd01/14/2020:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn03P485:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5590
dmi.product.sku: 0957
dmi.sys.vendor: Dell Inc.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-03-25T16:08:59.064986

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


** Tags: amd64 apport-bug audio eoan mic

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

Title:
  [HDA-Intel - HDA Intel PCH, recording] Recording problem, internal mic
  and headset mic not listed

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi, my dell laptop inspiron 15 5590 not working properly, internal mic
  is not listed in inputs and headset mic neither. I tested headset mic
  on other devices and it works fine. Also when I plug headset in in/out
  jack, ubuntu doesn't ask for connection type (headset, headset mic,
  mic) it use it only as simple headset.

  I tried some configuration in alsa and HDAJackRetask but none works.
  Same for kernels, 4.15.x, 5.0.x (oem), 5.3.x none works.

  I didn't test mics under windows because I can't for the moment.

  If you need details, I'll be glad to copy/paste your commands in
  terminal.

  Infos:
  Ubuntu 19.10
  kernel: 5.3.0-29-generic
  alsa-base: 1.0.25+dfsg-0ubuntu5

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nonot  2648 F pulseaudio
   /dev/snd/pcmC1D0c:   nonot  2648 F...m pulseaudio
   /dev/snd/controlC0:  nonot  2648 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 30 23:34:18 2020
  InstallationDate: Installed on 2020-01-07 (83 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 1 4 9 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: USB PnP Audio Device(EEPROM) - USB PnP Audio Device(EEPROM)
  Symptom_Type: Only some of inputs are working
  Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably 

[Desktop-packages] [Bug 1863733] Re: Bubblewrap upstream-as-root test fails on libcap2 1:2.31-1 and later

[Bug Watch Updater]

** Changed in: bubblewrap (Debian)
   Status: Unknown => Fix Released

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

Title:
  Bubblewrap upstream-as-root test fails on libcap2 1:2.31-1 and later

Status in bubblewrap package in Ubuntu:
  New
Status in libcap2 package in Ubuntu:
  New
Status in bubblewrap package in Debian:
  Fix Released

Bug description:
  The bubblewrap upstream-as-root test started failing after libcap2
  1:2.31-1 got synced from Debian. The same failure can be seen with
  1:2.32-1. I have reproduced the issue locally on focal - when using
  the focal-proposed version, the aforementioned test fails, where with
  the release version (1:2.27-1) it passes.

  It seems to fail here already:
  bwrap --bind / / --tmpfs /tmp --as-pid-1 --cap-drop CAP_KILL --cap-drop 
CAP_FOWNER --unshare-pid capsh --print
  assert_not_file_has_content caps.test '^Current: =.*cap_kill'

  It looks like the requested caps did not get dropped, as the logs show
  that both cap_kill and cap_fowner are still there. This is only for
  the upstream-as-root test, i.e. executing tests/test-run.sh as root.

  This might be an issue with bubblewrap, but seeing that it all works
  fine with the release version, it all feels weird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bubblewrap/+bug/1863733/+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 1868433] Re: display isn't woken up correctly after sleep

[elios]

I'm having the same problem. After reopening the lid screen stays black.

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

Title:
  display isn't woken up correctly after sleep

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  after sleep via "closing laptop lid" and waking up via "opening laptop
  lid" my screen remains black. However when i wake it up at dark room i
  see that actually something is rendering in screen. However it is too
  dark. I don't have such an issue with nvidia-440 driver, only with
  nouveau.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.3.0-43.36-generic 5.3.18
  Uname: Linux 5.3.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Mar 22 11:18:19 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.3.0-42-generic, x86_64: installed
   acpi-call, 1.1.0, 5.3.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GM204M [GeForce GTX 965M] [10de:1619] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GM204M [GeForce GTX 965M] [1043:1ced]
  MachineType: ASUSTeK COMPUTER INC. G752VL
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-43-generic 
root=UUID=8425b649-34d2-4084-b81d-f18d33ae7c0f ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VL.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VL
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VL.307:bd04/26/2019:svnASUSTeKCOMPUTERINC.:pnG752VL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VL
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/xserver-xorg-video-nouveau/+bug/1868433/+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 1868433] Re: display isn't woken up correctly after sleep

[Launchpad Bug Tracker]

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

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: New => Confirmed

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

Title:
  display isn't woken up correctly after sleep

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  after sleep via "closing laptop lid" and waking up via "opening laptop
  lid" my screen remains black. However when i wake it up at dark room i
  see that actually something is rendering in screen. However it is too
  dark. I don't have such an issue with nvidia-440 driver, only with
  nouveau.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.3.0-43.36-generic 5.3.18
  Uname: Linux 5.3.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Mar 22 11:18:19 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.3.0-42-generic, x86_64: installed
   acpi-call, 1.1.0, 5.3.0-43-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GM204M [GeForce GTX 965M] [10de:1619] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GM204M [GeForce GTX 965M] [1043:1ced]
  MachineType: ASUSTeK COMPUTER INC. G752VL
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-43-generic 
root=UUID=8425b649-34d2-4084-b81d-f18d33ae7c0f ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VL.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VL
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VL.307:bd04/26/2019:svnASUSTeKCOMPUTERINC.:pnG752VL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VL
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-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/xserver-xorg-video-nouveau/+bug/1868433/+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 1862028] Re: Focal uses the exfat fuse filesystem even though there is support in the kernel

[Brad Figg]

If I take the exfat flashdrive to a 20.04 system that does not have
exfat-utils/exfat-fuse on it, it works exactly as I expect and mounts as
an exfat filesystem.

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

Title:
  Focal uses the exfat fuse filesystem even though there is support in
  the kernel

Status in linux package in Ubuntu:
  Incomplete
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntukylin-meta package in Ubuntu:
  In Progress
Status in udisks2 package in Ubuntu:
  Invalid

Bug description:
  When a storage device formatted with exfat is automatically mounted on
  a system it is mounted with a fuse filesystem instead of a native,
  kernel filesystem. The kernel now has support for exfat.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862028/+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 1862028] Re: Focal uses the exfat fuse filesystem even though there is support in the kernel

[Brad Figg]

I believe if got the exfat-fuse filesystem when I installed exfat-tools
in order to mkexfatfs.

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

Title:
  Focal uses the exfat fuse filesystem even though there is support in
  the kernel

Status in linux package in Ubuntu:
  Incomplete
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntukylin-meta package in Ubuntu:
  In Progress
Status in udisks2 package in Ubuntu:
  Invalid

Bug description:
  When a storage device formatted with exfat is automatically mounted on
  a system it is mounted with a fuse filesystem instead of a native,
  kernel filesystem. The kernel now has support for exfat.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862028/+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 1862028] Re: Focal uses the exfat fuse filesystem even though there is support in the kernel

[Brad Figg]

exfat-utils that is

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

Title:
  Focal uses the exfat fuse filesystem even though there is support in
  the kernel

Status in linux package in Ubuntu:
  Incomplete
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntukylin-meta package in Ubuntu:
  In Progress
Status in udisks2 package in Ubuntu:
  Invalid

Bug description:
  When a storage device formatted with exfat is automatically mounted on
  a system it is mounted with a fuse filesystem instead of a native,
  kernel filesystem. The kernel now has support for exfat.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862028/+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 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher

[Sebastien Bacher]

https://bugs.launchpad.net/ubuntu/+source/pango1.0/1.44.7-2ubuntu2

** Changed in: pango1.0 (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Removing  libpango1.0-0  broke Minecraft Launcher

Status in pango1.0 package in Ubuntu:
  Fix Committed

Bug description:
  I just updated my machine, and when I did libpango1.0-0 was removed.
  This removed minecraft-launcher - the (very) popular launcher for
  Minecraft Java edition.

  I have reported this upstream, in case they can update their package
  https://bugs.mojang.com/browse/MCL-13512

  I am filing this bug so we can track it internally. I personally think
  this shouldn't have been done this late in the cycle, but there may
  well have been good reasons for it.

  As a result of the change though, it's now not possible to install
  Minecraft on Ubuntu 20.04.

  $ sudo apt install ./Minecraft\(1\).deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1869798] [NEW] Opening a combo box will draw windows from other workspaces on current workspace

[David Klasinc]

Public bug reported:

When a combo box is selected all the currently open windows will be
drawn on the screen, even if those windows are on other workspaces.

How to reproduce:

- Open different windows: Files and Terminal
- Send one window to a different Workspace: right-click on the title bar, Move 
to Workspace Down/Up
- Open Settings | Appearance
- Open 'Position On Screen' combo box

- Windows that were sent to other the worspaces will appear on the
screen. Windows aren't active and you're not able to interact with them,
they are just displayed.

Some windows will have a title bar that can be interacted with. In my
example, it was Brave browser, I was able to click on
minimize/maxime/close buttons and move the window around, but window
content wasn't responsive. However, Terminal, Files, Settings were
completely unresponsive.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.0-2ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 30 23:03:34 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-03-30 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Opening  a combo box will draw windows from other workspaces on
  current workspace

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When a combo box is selected all the currently open windows will be
  drawn on the screen, even if those windows are on other workspaces.

  How to reproduce:

  - Open different windows: Files and Terminal
  - Send one window to a different Workspace: right-click on the title bar, 
Move to Workspace Down/Up
  - Open Settings | Appearance
  - Open 'Position On Screen' combo box

  - Windows that were sent to other the worspaces will appear on the
  screen. Windows aren't active and you're not able to interact with
  them, they are just displayed.

  Some windows will have a title bar that can be interacted with. In my
  example, it was Brave browser, I was able to click on
  minimize/maxime/close buttons and move the window around, but window
  content wasn't responsive. However, Terminal, Files, Settings were
  completely unresponsive.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 30 23:03:34 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-03-30 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  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/1869798/+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 1855938] Re: [nvidia] Screen freezes and only mouse moves

[Bjorn Hassler]

I'm experiencing the same issue. Similarly, around 3 times a week on
Ubuntu 19.10.

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

Title:
  [nvidia] Screen freezes and only mouse moves

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The screen freezes but the mouse can be moved. SSH access works.

  This is on Legion Y545, Ubuntu 19.10
  Nvidia Geforce 1660Ti
  Intel 9750h

  Symptoms:
  This only happens when: Nvidia-Prime is selected as "on-demand"
  And maybe most likely after the laptop comes out of sleep.
  xserver-xorg-video-intel is the latest :: 2:2.99.917+git20190815-1

  If I choose prime-select "nvidia", this never happens. Makes me
  believe this has to do with intel video drivers.

  Error trace:
   GpuWatchdog[22171]: segfault at 0 ip 56163556379d sp 7fdeb6dd8480 
error 6 in chrome[561631628000+717]
  Dec 10 14:43:57 Legion-Y545 kernel: [27680.533760] Code: 48 c1 c9 03 48 81 f9 
af 00 00 00 0f 87 c9 00 00 00 48 8d 15 29 61 9c fb f6 04 11 20 0f 84 b8 00 00 
00 be 01 00 00 00 ff 50 30  04 25 00 00 00 00 37 13 00 00 c6 05 11 6a a4 03 
01 80 7d 8f 00

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Dec 10 15:01:38 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:3ffc]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TU116M [GeForce GTX 1660 Mobile] [17aa:3ffc]
  InstallationDate: Installed on 2019-10-23 (48 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 13d3:56a6 IMC Networks Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81Q6
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=8155cfb7-305e-41c0-9d80-fdf15d29e196 ro acpi=force
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/10/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN33WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN33WW:bd10/10/2019:svnLENOVO:pn81Q6:pvrLegionY545:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545:
  dmi.product.family: Legion Y545
  dmi.product.name: 81Q6
  dmi.product.sku: LENOVO_MT_81Q6_BU_idea_FM_Legion Y545
  dmi.product.version: Legion Y545
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to 

[Desktop-packages] [Bug 1868019] Re: [FFe] Add method to enable fractional scaling

[Gunnar Hjalmarsson]

The applicable docs page looks like this:

https://help.gnome.org/users/gnome-help/stable/look-resolution.html

So it would lag with respect to this change, but the UI difference is
small and self-explanatory, so I think this is ok from a docs POV.

It looks like this will add one or two new translatable strings. If so,
please notify the translators as soon as they are available at LP for
translation.

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

Title:
  [FFe] Add method to enable fractional scaling

Status in gnome-control-center package in Ubuntu:
  New
Status in gnome-control-center source package in Focal:
  New

Bug description:
  [Impact]
  Fractional scaling is currently requires enabling an experimental feature in 
Mutter to use it. We would like this feature to be easily enabled by users. A 
lot of modern hardware supports high DPI displays and these are often not 
usable without some form of fractional scaling.

  [Test Case]
  1. Open Settings
  2. Select Displays panels

  Expected result:
  Scale can be set to fractional values (e.g. 125%). There is a UI control to 
enable fractional scaling (disabled by default).

  Observed result:
  Scale can only be set to multiples of 100% unless the feature was enabled. No 
UI control is shown for Fractional scaling.

  [Regressional Potential]
  New UI code risks introducing new bugs. Users enabling fractional scaling may 
trigger new bugs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1868019/+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 1869524] Re: Simple Scan doesn't load

[Bartosz Kosiorek]

Hi Charles.
I suspect that you have old schema in directory:
/usr/local/share

Please try to rename `/usr/local/share` directory to `/usr/local/share-
back` and check if it helps

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

Title:
  Simple Scan doesn't load

Status in simple-scan package in Ubuntu:
  Incomplete

Bug description:
  Simple Scan version 3.28.0-0ubuntu1 fails to load in Ubuntu 18.04 LTS

  simple-scan: error while loading shared libraries: libcolord.so.1:
  cannot open shared object file: No such file or directory

  Related to bug# 1869522
  https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1869522

  Not sure if I should be reporting the bug against Simple Scan, Gnome,
  or Ubuntu 18.04 LTS.

  Gnome project said it's not a bug with Simple Scan.  Something about not 
having the latest version of Gnome bundled with Ubuntu 18.04 LTS.
  https://gitlab.gnome.org/GNOME/simple-scan/-/issues/159

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: simple-scan 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 28 15:53:47 2020
  InstallationDate: Installed on 2014-08-08 (2059 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: MSI MS-7922
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic 
root=UUID=12cc7d65-8589-4aab-a77b-566ea7af9984 ro pci=assign-busses quiet 
splash vt.handoff=1
  SimpleScanLog:
   
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to bionic on 2020-01-05 (83 days ago)
  dmi.bios.date: 02/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 U3 PLUS (MS-7922)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.10:bd02/16/2016:svnMSI:pnMS-7922:pvr1.0:rvnMSI:rnZ97U3PLUS(MS-7922):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7922
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1869524/+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 1869059] Re: Button 2 of my ThinkPad X1 Yoga's stylus is not detected

[Jonas Gamao]

Dunno if this helps, but the pen is called ThinkPad Pen Pro

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

Title:
  Button 2 of my ThinkPad X1 Yoga's stylus is not detected

Status in libwacom package in Ubuntu:
  New

Bug description:
  This also happened on Eoan, but I never had the chance to report the
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libwacom2 1.1-2build3
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Mar 25 13:12:20 2020
  DistUpgraded: 2020-03-21 19:59:50,804 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   backport-iwlwifi, 8324, 5.3.0-42-generic, x86_64: installed
   backport-iwlwifi, 8324, 5.4.0-18-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics [17aa:2292]
  InstallationDate: Installed on 2020-01-19 (66 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20SA0002US
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=8644acd5-759a-4daa-a34c-75ad3f4c5c12 ro quiet splash vt.handoff=7
  SourcePackage: libwacom
  UpgradeStatus: Upgraded to focal on 2020-03-21 (3 days ago)
  dmi.bios.date: 01/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2QET19W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20SA0002US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 4th
  dmi.product.name: 20SA0002US
  dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th
  dmi.product.version: ThinkPad X1 Yoga 4th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  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+git20190815-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/libwacom/+bug/1869059/+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 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher

[Rik Mills]

** Changed in: pango1.0 (Ubuntu)
   Status: Fix Committed => In Progress

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

Title:
  Removing  libpango1.0-0  broke Minecraft Launcher

Status in pango1.0 package in Ubuntu:
  In Progress

Bug description:
  I just updated my machine, and when I did libpango1.0-0 was removed.
  This removed minecraft-launcher - the (very) popular launcher for
  Minecraft Java edition.

  I have reported this upstream, in case they can update their package
  https://bugs.mojang.com/browse/MCL-13512

  I am filing this bug so we can track it internally. I personally think
  this shouldn't have been done this late in the cycle, but there may
  well have been good reasons for it.

  As a result of the change though, it's now not possible to install
  Minecraft on Ubuntu 20.04.

  $ sudo apt install ./Minecraft\(1\).deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1869755] Re: No web browser launches in Ubuntu 20.04

[tstrike]

Thanks Brian,

Here are the cores from my crashes in the last two days:


** Attachment added: "crasheststrike.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1869755/+attachment/5343522/+files/crasheststrike.tar.gz

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

Title:
  No web browser launches in Ubuntu 20.04

Status in firefox package in Ubuntu:
  New

Bug description:
  I am getting a segmentation fault when I attempt to launch any web
  browser:

  
  $uname -ar
  Linux  5.4.0-18-generic #22-Ubuntu SMP Sat Mar 7 18:13:06 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux
  $lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  
  Segmentation errors
  Web Content[8352]: segfault at 0 ip 7f2157d07742 sp 7ffda17b9bb0 
error 6 in libxul.so[7f2156f62000+489e000]
  Mar 29 20:53:56 localhost kernel: [23017.036763] Code: 48 3b 44 24 10 75 0d 
b0 01 48 83 c4 18 5b 41 5e 41 5f 5d c3 e8 7f af 25 ff 48 8d 05 51 87 7a 04 48 
8b 0d 81 be d5 05 48 89 01  04
   25 00 00 00 00 cb 01 00 00 e8 c6 3e 26 ff 66 2e 0f 1f 84 00
  Mar 29 20:53:56 localhost kernel: [23017.464295] traps: firefox[8297] trap 
int3 ip:7f8f2feaf0d5 sp:7ffe63b051f0 error:0 in 
libglib-2.0.so.0.6400.1[7f8f2fe73000+84000]
  Mar 29 20:56:30 localhost kernel: [23171.349753] rfkill: input handler enabled
  Mar 29 20:56:34 localhost kernel: [23175.671063] ibus-ui-gtk3[6013]: segfault 
at 7ffe4caeafd0 ip 7f6661e1bfa2 sp 7ffe4caeaed0 error 6 in 
libc-2.31.so[7f6661dc4000+178000]
  Mar 29 20:56:34 localhost kernel: [23175.671074] Code: 31 c0 8b 87 c0 00 00 
00 48 89 fb 85 c0 0f 85 05 02 00 00 c7 87 c0 00 00 00 ff ff ff ff 48 8d 84 24 
20 01 00 00 48 8d 7c 24 20 <48> 89
   9c 24 00 01 00 00 66 48 0f 6e c0 48 8d 84 24 20 21 00 00 c7


  
  Mar 30 06:09:53 localhost kernel: [30608.774632] traps: bijiben-shell-s[6791] 
trap int3 ip:7f78bc38f0d5 sp:7ffc61c652c0 error:0 in 
libglib-2.0.so.0.6400.1[7f78bc353000+84000]
  Mar 30 06:09:54 localhost kernel: [30608.874646] traps: nautilus[6777] trap 
int3 ip:7feefe0c90d5 sp:7ffc5978d400 error:0 in 
libglib-2.0.so.0.6400.1[7feefe08d000+84000]
  Mar 30 06:10:15 localhost kernel: [30629.848436] brave[6882]: segfault at 18 
ip 55a0be321f27 sp 7fff3aa5ca20 error 4 in brave[55a0b99d8000+7824000]
  Mar 30 06:10:15 localhost kernel: [30629.848447] Code: 48 83 ec 78 4c 89 c3 
49 89 cf 49 89 f4 49 89 fd 89 55 d4 f6 05 d9 c3 5e 03 19 4c 89 4d b0 0f 85 2b 
02 00 00 31 c0 48 89 45 c8 <49> 8b
   45 18 48 89 45 b8 48 8d 35 af 8e 9b fa 48 8d 15 cd b5 ac fa
  Mar 30 06:10:16 localhost kernel: [30631.629120] traps: brave[6910] trap int3 
ip:55c49796accf sp:7ffedc8b31e0 error:0 in brave[55c4949f5000+7824000]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1869755/+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 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher

[Sebastien Bacher]

THanks, I guess the provide needs to be version, new revision on his
way...

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

Title:
  Removing  libpango1.0-0  broke Minecraft Launcher

Status in pango1.0 package in Ubuntu:
  Fix Committed

Bug description:
  I just updated my machine, and when I did libpango1.0-0 was removed.
  This removed minecraft-launcher - the (very) popular launcher for
  Minecraft Java edition.

  I have reported this upstream, in case they can update their package
  https://bugs.mojang.com/browse/MCL-13512

  I am filing this bug so we can track it internally. I personally think
  this shouldn't have been done this late in the cycle, but there may
  well have been good reasons for it.

  As a result of the change though, it's now not possible to install
  Minecraft on Ubuntu 20.04.

  $ sudo apt install ./Minecraft\(1\).deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1869759] Re: Opengl or vulkan or mesa bug that causes textures to glitch when mipmapping or trilinear/bilinear filtering is enabled

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Opengl or vulkan or mesa bug that causes textures to glitch when
  mipmapping or trilinear/bilinear filtering is enabled

Status in xorg package in Ubuntu:
  New

Bug description:
  Textures are glitched (almost like they are cut up and repeated) when
  mipmapping or trilinear/bilinear filtering is enabled. Workaround is
  to disable both.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 30 12:03:39 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c4) (prog-if 
00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Picasso [1025:134f]
  InstallationDate: Installed on 2019-11-04 (147 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Acer Aspire A515-43
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=a44eb2b0-d036-44b7-9c90-d0a427ecd008 ro quiet splash 
resume=/dev/nvme0n1p5 resume_offset=15261696 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Grumpy_PK
  dmi.board.vendor: PK
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd09/26/2019:svnAcer:pnAspireA515-43:pvrV1.06:rvnPK:rnGrumpy_PK:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-43
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  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+git20190815-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/xorg/+bug/1869759/+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 1869759] [NEW] Opengl or vulkan or mesa bug that causes textures to glitch when mipmapping or trilinear/bilinear filtering is enabled

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Textures are glitched (almost like they are cut up and repeated) when
mipmapping or trilinear/bilinear filtering is enabled. Workaround is to
disable both.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 30 12:03:39 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c4) (prog-if 
00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Picasso [1025:134f]
InstallationDate: Installed on 2019-11-04 (147 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Acer Aspire A515-43
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=a44eb2b0-d036-44b7-9c90-d0a427ecd008 ro quiet splash 
resume=/dev/nvme0n1p5 resume_offset=15261696 vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2019
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.06
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Grumpy_PK
dmi.board.vendor: PK
dmi.board.version: V1.06
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.06
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd09/26/2019:svnAcer:pnAspireA515-43:pvrV1.06:rvnPK:rnGrumpy_PK:rvrV1.06:cvnAcer:ct10:cvrV1.06:
dmi.product.family: Aspire 5
dmi.product.name: Aspire A515-43
dmi.product.sku: 
dmi.product.version: V1.06
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
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+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption focal reproducible single-occurrence 
ubuntu wayland-session
-- 
Opengl or vulkan or mesa bug that causes textures to glitch when mipmapping or 
trilinear/bilinear filtering is enabled
https://bugs.launchpad.net/bugs/1869759
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg in Ubuntu.

-- 
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 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher

[Alan Pope  濾]

I have proposed enabled.

$ apt-cache policy libpango-1.0-0
libpango-1.0-0:
  Installed: 1.44.7-2ubuntu1
  Candidate: 1.44.7-2ubuntu1
  Version table:
 *** 1.44.7-2ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 1.44.7-2 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

Title:
  Removing  libpango1.0-0  broke Minecraft Launcher

Status in pango1.0 package in Ubuntu:
  Fix Committed

Bug description:
  I just updated my machine, and when I did libpango1.0-0 was removed.
  This removed minecraft-launcher - the (very) popular launcher for
  Minecraft Java edition.

  I have reported this upstream, in case they can update their package
  https://bugs.mojang.com/browse/MCL-13512

  I am filing this bug so we can track it internally. I personally think
  this shouldn't have been done this late in the cycle, but there may
  well have been good reasons for it.

  As a result of the change though, it's now not possible to install
  Minecraft on Ubuntu 20.04.

  $ sudo apt install ./Minecraft\(1\).deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher

[Sebastien Bacher]

The fixed version is still in proposed, it didn't migrate yet...

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

Title:
  Removing  libpango1.0-0  broke Minecraft Launcher

Status in pango1.0 package in Ubuntu:
  Fix Committed

Bug description:
  I just updated my machine, and when I did libpango1.0-0 was removed.
  This removed minecraft-launcher - the (very) popular launcher for
  Minecraft Java edition.

  I have reported this upstream, in case they can update their package
  https://bugs.mojang.com/browse/MCL-13512

  I am filing this bug so we can track it internally. I personally think
  this shouldn't have been done this late in the cycle, but there may
  well have been good reasons for it.

  As a result of the change though, it's now not possible to install
  Minecraft on Ubuntu 20.04.

  $ sudo apt install ./Minecraft\(1\).deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1856160] Re: Bar between bread crumbs and search icon.

[Sebastien Bacher]

Looks like https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/475
means it's improved/fixed in the new version

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

Title:
  Bar between bread crumbs and search icon.

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  1) Ubuntu 19.10
  2) 1:3.34.1-1ubuntu1
  3) There should be no bar between bread crumbs and the search icon. If I 
remember correctly.
  4) There is a bar between bread crumbs and search icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 12 03:00:41 2019
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'244'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1216, 604)'
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
  InstallationDate: Installed on 2019-10-28 (45 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1856160/+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 1868896] Re: Minimized windows reappear when closing the overview

[Sebastien Bacher]

The patch has been reverted in https://launchpad.net/ubuntu/+source
/gnome-shell/3.36.0-2ubuntu2

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

Title:
  Minimized windows reappear when closing the overview

Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  I just ran all of the updates for 20.04 on two machines, and both
  machines experience the same issue.

  Items do not appear to stay "minimized". For instance, you can
  minimize Thunderbird, and it appears to re-maximize itself. However,
  you cannot click on anything in the maximized window, but you can re-
  minimize it (that button does work), then click the dock to bring it
  back out and it functions properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 24 18:11:35 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
     Subsystem: Dell Iris Plus Graphics G7 [1028:096d]
  InstallationDate: Installed on 2020-03-11 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200311)
  MachineType: Dell Inc. XPS 13 9300
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vp1gr9@/vmlinuz-5.4.0-18-generic 
root=ZFS=rpool/ROOT/ubuntu_vp1gr9 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.6
  dmi.board.name: 077Y9N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.6:bd01/17/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  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+git20190815-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/gnome-shell/+bug/1868896/+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 1869734] Re: openjade segfaults on arm (due to gcc optimization)

[Christian Ehrhardt ]

BTW src:opensp a Cxx file in includes really?
This is on version 1.5.2 for ages no upstream changes.


It is possible that depeding on the optimization of openjade on build it 
changes the code flow into ::erase and then triggers the bad behavior.

replaced the broken line with:
  for (const T *p = p1; p <= p2; p++)

Rebuilt openjade against that fixed version but that thought was too
easy. It will still try to access p1=0x1 and fault. I'll need to
understand where exactly those p1/p2 args come from and fix it there.

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

Title:
  openjade segfaults on arm (due to gcc optimization)

Status in openjade package in Ubuntu:
  Triaged

Bug description:
  cpaelzer: fun, openjade segfaulting on focal/arm64
  I beg your pardon for my ignorance of the ecosystem, but how is 
this related to postgresql-apt
  for doc generation?
  cpaelzer: the postgresql-9.5 and -9.6 builds fail during doc 
generation on focal/arm64
  everything else (other archs, other dists) is fine
  
https://pgdgbuild.dus.dg-i.net/job/postgresql-9.5-binaries/architecture=arm64,distribution=focal/55/console

  Myon: only on arm64?
  only there, yes

  ./configure && make -C doc/src/sgml all  should reproduce it
  clone and build this branch ? 
https://github.com/postgres/postgres/tree/REL9_5_STABLE
  the crash is in /usr/lib/libostyle.so.1 from libostyle1c2
  here it is
  segfault

  I have this now http://paste.debian.net/1136839/
  https://paste.ubuntu.com/p/CfzrfWkqzs/

  well I wanted to get -O0 to see more int he debugger
  my build worked as well now
  the -O0 openjade installed doesn't segfault
  oh so like my -O0 then
  so maybe we should just always -O0 openjade then?
  TBH who cares about optimization in that
  But its usage is mostly build time and not runtime
  maybe -O0 on arm64 only
  I'm rebulding -O2 again to recheck if that really is it
  and then -O1 to check the in between
  it might "just" need a rebuild

  -O2 re-build segfault
  -O1 (for completeness) rebuild ... seems to hang?
  probably not really relevant
  agreed, but I want to rebuild -O0 again just to see it builds 
and then works
  -O0 on arm64 really seems to be a good choice

  I can try if rebuilding makes it fail on sid
  cpaelzer: recompiling openjade in arm64/sid doesn't make it 
segfault
  so it seems this needs a focal-only fix
  cpaelzer: the openjade segfault is also present in pgpool2, so 
not just in ancient PostgreSQL :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjade/+bug/1869734/+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 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher

[Alan Pope  濾]

This doesn't seem properly fixed...

dpkg: dependency problems prevent configuration of minecraft-launcher:
 minecraft-launcher depends on libpango1.0-0 (>= 1.14.0); however:
  Package libpango1.0-0 is not installed.
  Version of libpango1.0-0 on system, provided by libpango-1.0-0:amd64, is 
.

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

Title:
  Removing  libpango1.0-0  broke Minecraft Launcher

Status in pango1.0 package in Ubuntu:
  Fix Committed

Bug description:
  I just updated my machine, and when I did libpango1.0-0 was removed.
  This removed minecraft-launcher - the (very) popular launcher for
  Minecraft Java edition.

  I have reported this upstream, in case they can update their package
  https://bugs.mojang.com/browse/MCL-13512

  I am filing this bug so we can track it internally. I personally think
  this shouldn't have been done this late in the cycle, but there may
  well have been good reasons for it.

  As a result of the change though, it's now not possible to install
  Minecraft on Ubuntu 20.04.

  $ sudo apt install ./Minecraft\(1\).deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1869734] Re: openjade segfaults on arm (due to gcc optimization)

[Christian Ehrhardt ]

If I run this with the -O0 build it never ever reaches
  OpenSP::Vector::erase
So the code is still broken, but we just don't reach it.
-O0 isn't even a good mitigation.

Tracking the root cause further.

Very late in the -O0 build it then hits it like:
::erase (this=0xab027250, p1=0xaaeb5cf0, p2=0xaaeb5cf8)
::erase (this=0xab46cf10, p1=0xab883120, p2=0xab883128)
...
All that looks reasonable.
The other call we see in -O2 builds is broken:
::erase (p1=0x1, p2=0x2, ...

But this is actually a header in: src:opensp

Defines in
/usr/include/OpenSP/Vector.cxx:331

for (const T *p = p1; p != p2; p++)
  # works on pointer p

But for any type that does not surely increase the right way.
E.g. p1 = 0x1, p2 = 0x2 but increment = 4 (due to pointer arithmetic)
Then it will increment p forever.

If we use <= it will stop as soon as we would run over.

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

Title:
  openjade segfaults on arm (due to gcc optimization)

Status in openjade package in Ubuntu:
  Triaged

Bug description:
  cpaelzer: fun, openjade segfaulting on focal/arm64
  I beg your pardon for my ignorance of the ecosystem, but how is 
this related to postgresql-apt
  for doc generation?
  cpaelzer: the postgresql-9.5 and -9.6 builds fail during doc 
generation on focal/arm64
  everything else (other archs, other dists) is fine
  
https://pgdgbuild.dus.dg-i.net/job/postgresql-9.5-binaries/architecture=arm64,distribution=focal/55/console

  Myon: only on arm64?
  only there, yes

  ./configure && make -C doc/src/sgml all  should reproduce it
  clone and build this branch ? 
https://github.com/postgres/postgres/tree/REL9_5_STABLE
  the crash is in /usr/lib/libostyle.so.1 from libostyle1c2
  here it is
  segfault

  I have this now http://paste.debian.net/1136839/
  https://paste.ubuntu.com/p/CfzrfWkqzs/

  well I wanted to get -O0 to see more int he debugger
  my build worked as well now
  the -O0 openjade installed doesn't segfault
  oh so like my -O0 then
  so maybe we should just always -O0 openjade then?
  TBH who cares about optimization in that
  But its usage is mostly build time and not runtime
  maybe -O0 on arm64 only
  I'm rebulding -O2 again to recheck if that really is it
  and then -O1 to check the in between
  it might "just" need a rebuild

  -O2 re-build segfault
  -O1 (for completeness) rebuild ... seems to hang?
  probably not really relevant
  agreed, but I want to rebuild -O0 again just to see it builds 
and then works
  -O0 on arm64 really seems to be a good choice

  I can try if rebuilding makes it fail on sid
  cpaelzer: recompiling openjade in arm64/sid doesn't make it 
segfault
  so it seems this needs a focal-only fix
  cpaelzer: the openjade segfault is also present in pgpool2, so 
not just in ancient PostgreSQL :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjade/+bug/1869734/+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 1869787] Re: libpango1.0-0 has been removed from 20.04 and is not installable

[Sebastien Bacher]

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

** This bug has been marked a duplicate of bug 1869716
   Removing  libpango1.0-0  broke Minecraft Launcher

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

Title:
  libpango1.0-0 has been removed from 20.04 and is not installable

Status in pango1.0 package in Ubuntu:
  New

Bug description:
  Upon update on 30 March 2020 libpango1.0-0 was removed from the
  system.

  Package libpango1.0-0 is not available, but is referred to by another package.
  This may mean that the package is missing, has been obsoleted, or
  is only available from another source
  However the following packages replace it:
libpangox-1.0-0

  However applications such as balena-etcher require libpango1.0-0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869787/+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 1869787] Re: libpango1.0-0 has been removed from 20.04 and is not installable

[Bill (franksmcb)]

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

https://packages.ubuntu.com/bionic/libpango1.0-0

** Package changed: ubuntu => pango1.0 (Ubuntu)

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

Title:
  libpango1.0-0 has been removed from 20.04 and is not installable

Status in pango1.0 package in Ubuntu:
  New

Bug description:
  Upon update on 30 March 2020 libpango1.0-0 was removed from the
  system.

  Package libpango1.0-0 is not available, but is referred to by another package.
  This may mean that the package is missing, has been obsoleted, or
  is only available from another source
  However the following packages replace it:
libpangox-1.0-0

  However applications such as balena-etcher require libpango1.0-0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869787/+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 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher

[Rik Mills]

** Changed in: pango1.0 (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Removing  libpango1.0-0  broke Minecraft Launcher

Status in pango1.0 package in Ubuntu:
  Fix Committed

Bug description:
  I just updated my machine, and when I did libpango1.0-0 was removed.
  This removed minecraft-launcher - the (very) popular launcher for
  Minecraft Java edition.

  I have reported this upstream, in case they can update their package
  https://bugs.mojang.com/browse/MCL-13512

  I am filing this bug so we can track it internally. I personally think
  this shouldn't have been done this late in the cycle, but there may
  well have been good reasons for it.

  As a result of the change though, it's now not possible to install
  Minecraft on Ubuntu 20.04.

  $ sudo apt install ./Minecraft\(1\).deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher

[Mason Loring Bliss]

And RikMills notes:

https://launchpad.net/ubuntu/+source/pango1.0/1.44.7-2ubuntu1

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

Title:
  Removing  libpango1.0-0  broke Minecraft Launcher

Status in pango1.0 package in Ubuntu:
  Fix Committed

Bug description:
  I just updated my machine, and when I did libpango1.0-0 was removed.
  This removed minecraft-launcher - the (very) popular launcher for
  Minecraft Java edition.

  I have reported this upstream, in case they can update their package
  https://bugs.mojang.com/browse/MCL-13512

  I am filing this bug so we can track it internally. I personally think
  this shouldn't have been done this late in the cycle, but there may
  well have been good reasons for it.

  As a result of the change though, it's now not possible to install
  Minecraft on Ubuntu 20.04.

  $ sudo apt install ./Minecraft\(1\).deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher

[Mason Loring Bliss]

Note: In Bionic - I haven't checked exhaustively - libpango1.0-0 is a 
transitional package, and
libpango-1.0-0 is the actual package. Perhaps Focal Fossa should continue to 
ship the transitional
package to keep Minecraft folk from encountering this. Not sure what policy 
applies.

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

Title:
  Removing  libpango1.0-0  broke Minecraft Launcher

Status in pango1.0 package in Ubuntu:
  Fix Committed

Bug description:
  I just updated my machine, and when I did libpango1.0-0 was removed.
  This removed minecraft-launcher - the (very) popular launcher for
  Minecraft Java edition.

  I have reported this upstream, in case they can update their package
  https://bugs.mojang.com/browse/MCL-13512

  I am filing this bug so we can track it internally. I personally think
  this shouldn't have been done this late in the cycle, but there may
  well have been good reasons for it.

  As a result of the change though, it's now not possible to install
  Minecraft on Ubuntu 20.04.

  $ sudo apt install ./Minecraft\(1\).deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1869787] [NEW] libpango1.0-0 has been removed from 20.04 and is not installable

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Upon update on 30 March 2020 libpango1.0-0 was removed from the system.

Package libpango1.0-0 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  libpangox-1.0-0

However applications such as balena-etcher require libpango1.0-0

** Affects: pango1.0 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
libpango1.0-0 has been removed from 20.04 and is not installable
https://bugs.launchpad.net/bugs/1869787
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to pango1.0 in Ubuntu.

-- 
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 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

[Dariusz Gadomski]

** Changed in: network-manager (Ubuntu Eoan)
 Assignee: Dariusz Gadomski (dgadomski) => (unassigned)

** Changed in: network-manager (Ubuntu Focal)
 Assignee: Dariusz Gadomski (dgadomski) => (unassigned)

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  New
Status in network-manager source package in Focal:
  New

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock. Adding a sleep before calling nmcli fixes the issue.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  
  [Test Case]

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

  
  [Regression Potential]

  No regression potential. The fix touches only the testcase shipped
  with the source package and it doesn't change the binary package. The
  sleep time added is very small, so no possibility of causing testcase
  timeout.

  
  [Other Info]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+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 1869734] Re: openjade segfaults on arm (due to gcc optimization)

[Christian Ehrhardt ]

Ok, now things make sense.
src:openjade also builds libostyle1c2 and updating that to the -O0 build made 
it work.
So overall this would be a good fix still.

Drawback, I'd love to know what is going on under the covers ... :-/

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

Title:
  openjade segfaults on arm (due to gcc optimization)

Status in openjade package in Ubuntu:
  Triaged

Bug description:
  cpaelzer: fun, openjade segfaulting on focal/arm64
  I beg your pardon for my ignorance of the ecosystem, but how is 
this related to postgresql-apt
  for doc generation?
  cpaelzer: the postgresql-9.5 and -9.6 builds fail during doc 
generation on focal/arm64
  everything else (other archs, other dists) is fine
  
https://pgdgbuild.dus.dg-i.net/job/postgresql-9.5-binaries/architecture=arm64,distribution=focal/55/console

  Myon: only on arm64?
  only there, yes

  ./configure && make -C doc/src/sgml all  should reproduce it
  clone and build this branch ? 
https://github.com/postgres/postgres/tree/REL9_5_STABLE
  the crash is in /usr/lib/libostyle.so.1 from libostyle1c2
  here it is
  segfault

  I have this now http://paste.debian.net/1136839/
  https://paste.ubuntu.com/p/CfzrfWkqzs/

  well I wanted to get -O0 to see more int he debugger
  my build worked as well now
  the -O0 openjade installed doesn't segfault
  oh so like my -O0 then
  so maybe we should just always -O0 openjade then?
  TBH who cares about optimization in that
  But its usage is mostly build time and not runtime
  maybe -O0 on arm64 only
  I'm rebulding -O2 again to recheck if that really is it
  and then -O1 to check the in between
  it might "just" need a rebuild

  -O2 re-build segfault
  -O1 (for completeness) rebuild ... seems to hang?
  probably not really relevant
  agreed, but I want to rebuild -O0 again just to see it builds 
and then works
  -O0 on arm64 really seems to be a good choice

  I can try if rebuilding makes it fail on sid
  cpaelzer: recompiling openjade in arm64/sid doesn't make it 
segfault
  so it seems this needs a focal-only fix
  cpaelzer: the openjade segfault is also present in pgpool2, so 
not just in ancient PostgreSQL :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjade/+bug/1869734/+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 1869755] Re: No web browser launches in Ubuntu 20.04

[Brian Murray]

The directory /var/crash is the right place to look for a core file. If
you don't see one there you might check /var/log/apport.log to see if
any information exists there.

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

Title:
  No web browser launches in Ubuntu 20.04

Status in firefox package in Ubuntu:
  New

Bug description:
  I am getting a segmentation fault when I attempt to launch any web
  browser:

  
  $uname -ar
  Linux  5.4.0-18-generic #22-Ubuntu SMP Sat Mar 7 18:13:06 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux
  $lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  
  Segmentation errors
  Web Content[8352]: segfault at 0 ip 7f2157d07742 sp 7ffda17b9bb0 
error 6 in libxul.so[7f2156f62000+489e000]
  Mar 29 20:53:56 localhost kernel: [23017.036763] Code: 48 3b 44 24 10 75 0d 
b0 01 48 83 c4 18 5b 41 5e 41 5f 5d c3 e8 7f af 25 ff 48 8d 05 51 87 7a 04 48 
8b 0d 81 be d5 05 48 89 01  04
   25 00 00 00 00 cb 01 00 00 e8 c6 3e 26 ff 66 2e 0f 1f 84 00
  Mar 29 20:53:56 localhost kernel: [23017.464295] traps: firefox[8297] trap 
int3 ip:7f8f2feaf0d5 sp:7ffe63b051f0 error:0 in 
libglib-2.0.so.0.6400.1[7f8f2fe73000+84000]
  Mar 29 20:56:30 localhost kernel: [23171.349753] rfkill: input handler enabled
  Mar 29 20:56:34 localhost kernel: [23175.671063] ibus-ui-gtk3[6013]: segfault 
at 7ffe4caeafd0 ip 7f6661e1bfa2 sp 7ffe4caeaed0 error 6 in 
libc-2.31.so[7f6661dc4000+178000]
  Mar 29 20:56:34 localhost kernel: [23175.671074] Code: 31 c0 8b 87 c0 00 00 
00 48 89 fb 85 c0 0f 85 05 02 00 00 c7 87 c0 00 00 00 ff ff ff ff 48 8d 84 24 
20 01 00 00 48 8d 7c 24 20 <48> 89
   9c 24 00 01 00 00 66 48 0f 6e c0 48 8d 84 24 20 21 00 00 c7


  
  Mar 30 06:09:53 localhost kernel: [30608.774632] traps: bijiben-shell-s[6791] 
trap int3 ip:7f78bc38f0d5 sp:7ffc61c652c0 error:0 in 
libglib-2.0.so.0.6400.1[7f78bc353000+84000]
  Mar 30 06:09:54 localhost kernel: [30608.874646] traps: nautilus[6777] trap 
int3 ip:7feefe0c90d5 sp:7ffc5978d400 error:0 in 
libglib-2.0.so.0.6400.1[7feefe08d000+84000]
  Mar 30 06:10:15 localhost kernel: [30629.848436] brave[6882]: segfault at 18 
ip 55a0be321f27 sp 7fff3aa5ca20 error 4 in brave[55a0b99d8000+7824000]
  Mar 30 06:10:15 localhost kernel: [30629.848447] Code: 48 83 ec 78 4c 89 c3 
49 89 cf 49 89 f4 49 89 fd 89 55 d4 f6 05 d9 c3 5e 03 19 4c 89 4d b0 0f 85 2b 
02 00 00 31 c0 48 89 45 c8 <49> 8b
   45 18 48 89 45 b8 48 8d 35 af 8e 9b fa 48 8d 15 cd b5 ac fa
  Mar 30 06:10:16 localhost kernel: [30631.629120] traps: brave[6910] trap int3 
ip:55c49796accf sp:7ffedc8b31e0 error:0 in brave[55c4949f5000+7824000]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1869755/+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 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen

[Jarno Kaikkonen]

I didn't notice to mention this earlier as I had no windows open on the
top monitor at the time of writing, but it is fair to mention that the
top monitor's app overview works flawlessly, only the bottom monitor is
broken. Attached picture for clarification.

** Attachment added: "Top monitor has the app overview working as expected, 
bottom is running at tiny scale"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869571/+attachment/5343512/+files/Kuvakaappaus%20-%202020-03-30%2021-49-43.png

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

Title:
  Vertical dual monitor setup with main monitor on bottom causes
  overview to only use one eigth of screen

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

Bug description:
  Very recently I have started experiencing a constant bug of the app
  overview / search functions of gnome shell being entirely unusable
  because shell operates at such a tiny scale that barely anything is
  shown on screen.

  I managed to narrow the problem down to having something to do with
  dual monitors, and then played around a bit with the settings. My
  results are that no matter what other configuration I set my two
  monitors in, gnome-shell operates perfectly. That is, if my secondary
  monitor is on the left, right or below my primary one, all is well.

  If, however, the secondary monitor is set to be on top of the primary
  one (As it physically is in my current setup), then the overview and
  app search functionality starts using some very weird kind of vertical
  scaling and becomes unusable. The window previews are so small that
  the (most of the time invisible) X button is bigger than the window
  itself, thus only making me able to close the windows instead of
  switching to them or moving them. Application search only shows half
  of the first row, the other half fading away.

  I am running Ubuntu 20.04 Focal Fossa (development branch) and version
  3.36.0-2ubuntu1 of gnome-shell.

  Here are screenshots of my problem:
  The overview screen barely showing my open windows
  https://i.ibb.co/bJZFdR8/Kuvakaappaus-2020-03-29-14-14-22.png
  The search function only showing the top half of first row of icons
  https://i.ibb.co/g4qV3wP/Kuvakaappaus-2020-03-29-14-14-40.png
  When you mouse-over the windows many times over and over you might get the X 
button to show
  https://i.ibb.co/QjRKZr1/Kuvakaappaus-2020-03-29-14-18-07.png
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-02-25 (33 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220)
  Package: gnome-shell 3.36.0-2ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  Tags: third-party-packages focal
  Uname: Linux 5.4.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo tty uucp
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1869571/+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 1869769] Re: gnome-terminal regularly becomes corrupted

[Edward Schwartz]

I managed to track this down to a particular option in weechat,
eat_newline_glitch.  The problem occurs when there are lines that are
_exactly_ as long as the terminal width.  Here is the script:

https://gist.github.com/edmcman/8fa071e68af14c288bf1801ffc142f61

At this point, I believe it unlikely to be a gnome-terminal bug.  But
I'll dig in a little more.

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

Title:
  gnome-terminal regularly becomes corrupted

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I regularly run weechat inside gnome-terminal, and it routinely
  becomes corrupted.  It's hard to say whether this is a gnome-terminal
  bug, but I've seen it on different machines.

  The problem is perhaps best shown through a screenshot (attached).
  You can see the statusbar in the second to last row incorrectly
  contains the words "I would" that were displayed elsewhere in the
  terminal but weechat at some point.

  Normal usage of weechat results in tabs that have corruption in other
  rows, but I wasn't readily able to find an example with non-sensitive
  information.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
  Uname: Linux 5.5.0-050500rc6-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Mar 30 13:25:03 2020
  InstallationDate: Installed on 2020-01-03 (86 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1869769/+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 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

[Dariusz Gadomski]

Sure Dan, I'm looking into it.

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  New
Status in network-manager source package in Focal:
  New

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock. Adding a sleep before calling nmcli fixes the issue.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  
  [Test Case]

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

  
  [Regression Potential]

  No regression potential. The fix touches only the testcase shipped
  with the source package and it doesn't change the binary package. The
  sleep time added is very small, so no possibility of causing testcase
  timeout.

  
  [Other Info]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+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 1866498] Re: [Snap] Libreoffice Snap is not available in Hungarian

[Adolfo Jayme]

** Changed in: libreoffice (Ubuntu)
   Importance: Undecided => Wishlist

** Tags added: snap

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

Title:
  [Snap] Libreoffice Snap is not available in Hungarian

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Could you please add Hungarian language to libreoffice snap. I want to change 
all my deb applications to snaps but this isn'T possible without correct 
localization. Thanks
  I know it adds ~ 8mb overhead to the snap but I think it's an acceptable size 
compared to nowadays HDD sizes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1866498/+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 1868915] Re: [focal] nm-online -s --timeout=10 timeout every time

[Lee Trager]

NetworkManager isn't installed in the base MAAS Focal image.

Are you using the default image from images.maas.io?

What cloud-init user-data are you sending to the install?

Have you modified the preseed file at all?

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

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

Title:
  [focal] nm-online -s --timeout=10 timeout every time

Status in MAAS:
  Incomplete
Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Also created bug on upstream :
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/398

  
  This issue will cause "NetworkManager-wait-online.service: Failed with result 
'exit-code'."
  And cloud-init.service is counting on this service for network status.

  So this issue will finally cause MaaS deploying failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1 [modified: 
lib/systemd/system/NetworkManager-wait-online.service]
  ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8
  Uname: Linux 5.4.0-1002-oem x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  Date: Wed Mar 25 12:43:13 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200316-60+fossa-staging+X09
  IfupdownConfig: source /etc/network/interfaces.d/*.cfg
  InstallationDate: Installed on 2020-03-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200316-08:40
  IpRoute:
   default via 192.168.101.1 dev eno1 proto static metric 100
   10.101.46.0/24 via 192.168.101.1 dev eno1 proto static metric 200
   169.254.0.0/16 dev eno1 scope link metric 1000
   192.168.101.0/24 dev eno1 proto kernel scope link src 192.168.101.85 metric 
100
  NetDevice.bonding_masters:
   Error: command ['udevadm', 'info', '--query=all', '--path', 
'/sys/class/net/bonding_masters'] failed with exit code 1: Unknown device 
"/sys/class/net/bonding_masters": No such device

   X: INTERFACE_MAC=Error: command ['cat', 
'/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: 
/sys/class/net/bonding_masters/address: Not a directory
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL  AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE  FILENAME
   netplan-eno1  10838d80-caeb-349e-ba73-08ed16d4d666  ethernet  158577  
廿廿年三月廿五日 (週三) 十二時39分37秒  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes eno1activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/run/NetworkManager/system-connections/netplan-eno1.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP   CONNECTIVITY  NETWORKING  WIFI-HW   
WIFI  WWAN-HW  WWAN
   running  1.22.10  connected  starting  full  enabled disabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1868915/+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 1869774] Re: libpango1.0-0 package missing in focal

[Juhani Numminen]

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

Hi, the developers are fixing this, please follow
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716.

** Package changed: ubuntu => pango1.0 (Ubuntu)

** This bug has been marked a duplicate of bug 1869716
   Removing  libpango1.0-0  broke Minecraft Launcher

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

Title:
  libpango1.0-0 package missing in focal

Status in pango1.0 package in Ubuntu:
  New

Bug description:
  18.04 has libpango1.0-0 (potentially as a transitional package)
  20.04 doesn't appear to have it.

  Perhaps libpango1.0-0 could be added to 20.04 as a transitional
  package?

  This issue presented itself when installing Minecraft.deb on 20.04

  minecraft-launcher does function on 20.04, but is removed during an
  "apt --fix-broken install"

  
  On 18.04:

  
  gamecage@steam:~$ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04
  gamecage@steam:~$ sudo dpkg -i Minecraft.deb
  Selecting previously unselected package minecraft-launcher.
  (Reading database ... 187796 files and directories currently installed.)
  Preparing to unpack Minecraft.deb ...
  Unpacking minecraft-launcher (2.1.13086) ...
  dpkg: dependency problems prevent configuration of minecraft-launcher:
   minecraft-launcher depends on gconf-service; however:
Package gconf-service is not installed.
   minecraft-launcher depends on libgconf-2-4 (>= 2.31.1); however:
Package libgconf-2-4 is not installed.
   minecraft-launcher depends on libpango1.0-0 (>= 1.14.0); however:
Package libpango1.0-0 is not installed.
   minecraft-launcher depends on libcurl3 | libcurl4; however:
Package libcurl3 is not installed.
Package libcurl4 is not installed.

  dpkg: error processing package minecraft-launcher (--install):
   dependency problems - leaving unconfigured
  Processing triggers for gnome-menus (3.13.3-11ubuntu1) ...
  Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.1) ...
  Processing triggers for mime-support (3.60ubuntu1) ...
  Processing triggers for hicolor-icon-theme (0.17-2) ...
  Errors were encountered while processing:
   minecraft-launcher
  gamecage@steam:~$ sudo apt --fix-broken install 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following additional packages will be installed:
gconf-service gconf-service-backend gconf2-common libcurl3 libgconf-2-4
libpango1.0-0 libpangox-1.0-0
  The following NEW packages will be installed:
gconf-service gconf-service-backend gconf2-common libcurl3 libgconf-2-4
libpango1.0-0 libpangox-1.0-0
  0 upgraded, 7 newly installed, 0 to remove and 236 not upgraded.
  1 not fully installed or removed.
  Need to get 1,104 kB of archives.
  After this operation, 8,897 kB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Get:1 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 gconf2-common 
all 3.2.6-4ubuntu1 [700 kB]
  Get:2 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 libgconf-2-4 
amd64 3.2.6-4ubuntu1 [84.8 kB]
  Get:3 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 
gconf-service-backend amd64 3.2.6-4ubuntu1 [58.1 kB]
  Get:4 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 gconf-service 
amd64 3.2.6-4ubuntu1 [2,036 B]
  Get:5 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 
libpangox-1.0-0 amd64 0.0.2-5 [41.7 kB]
  Get:6 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
libpango1.0-0 amd64 1.40.14-1ubuntu0.1 [3,344 B]
  Get:7 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 libcurl3 
amd64 7.58.0-2ubuntu2 [214 kB]
  Fetched 1,104 kB in 1s (1,406 kB/s)   
  Selecting previously unselected package gconf2-common.
  (Reading database ... 187866 files and directories currently installed.)
  Preparing to unpack .../0-gconf2-common_3.2.6-4ubuntu1_all.deb ...
  Unpacking gconf2-common (3.2.6-4ubuntu1) ...
  Selecting previously unselected package libgconf-2-4:amd64.
  Preparing to unpack .../1-libgconf-2-4_3.2.6-4ubuntu1_amd64.deb ...
  Unpacking libgconf-2-4:amd64 (3.2.6-4ubuntu1) ...
  Selecting previously unselected package gconf-service-backend.
  Preparing to unpack .../2-gconf-service-backend_3.2.6-4ubuntu1_amd64.deb ...
  Unpacking gconf-service-backend (3.2.6-4ubuntu1) ...
  Selecting previously unselected package gconf-service.
  Preparing to unpack .../3-gconf-service_3.2.6-4ubuntu1_amd64.deb ...
  Unpacking gconf-service (3.2.6-4ubuntu1) ...
  Selecting previously unselected package libpangox-1.0-0:amd64.
  Preparing to unpack .../4-libpangox-1.0-0_0.0.2-5_amd64.deb ...
  Unpacking libpangox-1.0-0:amd64 (0.0.2-5) ...
  Selecting previously unselected package libpango1.0-0:amd64.

[Desktop-packages] [Bug 1869774] [NEW] libpango1.0-0 package missing in focal

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

18.04 has libpango1.0-0 (potentially as a transitional package)
20.04 doesn't appear to have it.

Perhaps libpango1.0-0 could be added to 20.04 as a transitional package?

This issue presented itself when installing Minecraft.deb on 20.04

minecraft-launcher does function on 20.04, but is removed during an "apt
--fix-broken install"


On 18.04:


gamecage@steam:~$ lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04
gamecage@steam:~$ sudo dpkg -i Minecraft.deb
Selecting previously unselected package minecraft-launcher.
(Reading database ... 187796 files and directories currently installed.)
Preparing to unpack Minecraft.deb ...
Unpacking minecraft-launcher (2.1.13086) ...
dpkg: dependency problems prevent configuration of minecraft-launcher:
 minecraft-launcher depends on gconf-service; however:
  Package gconf-service is not installed.
 minecraft-launcher depends on libgconf-2-4 (>= 2.31.1); however:
  Package libgconf-2-4 is not installed.
 minecraft-launcher depends on libpango1.0-0 (>= 1.14.0); however:
  Package libpango1.0-0 is not installed.
 minecraft-launcher depends on libcurl3 | libcurl4; however:
  Package libcurl3 is not installed.
  Package libcurl4 is not installed.

dpkg: error processing package minecraft-launcher (--install):
 dependency problems - leaving unconfigured
Processing triggers for gnome-menus (3.13.3-11ubuntu1) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.1) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Errors were encountered while processing:
 minecraft-launcher
gamecage@steam:~$ sudo apt --fix-broken install 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  gconf-service gconf-service-backend gconf2-common libcurl3 libgconf-2-4
  libpango1.0-0 libpangox-1.0-0
The following NEW packages will be installed:
  gconf-service gconf-service-backend gconf2-common libcurl3 libgconf-2-4
  libpango1.0-0 libpangox-1.0-0
0 upgraded, 7 newly installed, 0 to remove and 236 not upgraded.
1 not fully installed or removed.
Need to get 1,104 kB of archives.
After this operation, 8,897 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 gconf2-common 
all 3.2.6-4ubuntu1 [700 kB]
Get:2 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 libgconf-2-4 
amd64 3.2.6-4ubuntu1 [84.8 kB]
Get:3 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 
gconf-service-backend amd64 3.2.6-4ubuntu1 [58.1 kB]
Get:4 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 gconf-service 
amd64 3.2.6-4ubuntu1 [2,036 B]
Get:5 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 libpangox-1.0-0 
amd64 0.0.2-5 [41.7 kB]
Get:6 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
libpango1.0-0 amd64 1.40.14-1ubuntu0.1 [3,344 B]
Get:7 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 libcurl3 amd64 
7.58.0-2ubuntu2 [214 kB]
Fetched 1,104 kB in 1s (1,406 kB/s)   
Selecting previously unselected package gconf2-common.
(Reading database ... 187866 files and directories currently installed.)
Preparing to unpack .../0-gconf2-common_3.2.6-4ubuntu1_all.deb ...
Unpacking gconf2-common (3.2.6-4ubuntu1) ...
Selecting previously unselected package libgconf-2-4:amd64.
Preparing to unpack .../1-libgconf-2-4_3.2.6-4ubuntu1_amd64.deb ...
Unpacking libgconf-2-4:amd64 (3.2.6-4ubuntu1) ...
Selecting previously unselected package gconf-service-backend.
Preparing to unpack .../2-gconf-service-backend_3.2.6-4ubuntu1_amd64.deb ...
Unpacking gconf-service-backend (3.2.6-4ubuntu1) ...
Selecting previously unselected package gconf-service.
Preparing to unpack .../3-gconf-service_3.2.6-4ubuntu1_amd64.deb ...
Unpacking gconf-service (3.2.6-4ubuntu1) ...
Selecting previously unselected package libpangox-1.0-0:amd64.
Preparing to unpack .../4-libpangox-1.0-0_0.0.2-5_amd64.deb ...
Unpacking libpangox-1.0-0:amd64 (0.0.2-5) ...
Selecting previously unselected package libpango1.0-0:amd64.
Preparing to unpack .../5-libpango1.0-0_1.40.14-1ubuntu0.1_amd64.deb ...
Unpacking libpango1.0-0:amd64 (1.40.14-1ubuntu0.1) ...
Selecting previously unselected package libcurl3:amd64.
Preparing to unpack .../6-libcurl3_7.58.0-2ubuntu2_amd64.deb ...
Unpacking libcurl3:amd64 (7.58.0-2ubuntu2) ...
Setting up gconf2-common (3.2.6-4ubuntu1) ...
Setting up libcurl3:amd64 (7.58.0-2ubuntu2) ...
Setting up libgconf-2-4:amd64 (3.2.6-4ubuntu1) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Setting up libpangox-1.0-0:amd64 (0.0.2-5) ...
Setting up libpango1.0-0:amd64 (1.40.14-1ubuntu0.1) ...
Setting up gconf-service-backend (3.2.6-4ubuntu1) ...
Setting up gconf-service (3.2.6-4ubuntu1) ...
Setting up minecraft-launcher (2.1.13086) ...
Processing 

[Desktop-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

[Dariusz Gadomski]

** Changed in: network-manager (Ubuntu Eoan)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

** Changed in: network-manager (Ubuntu Focal)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  New
Status in network-manager source package in Focal:
  New

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock. Adding a sleep before calling nmcli fixes the issue.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  
  [Test Case]

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

  
  [Regression Potential]

  No regression potential. The fix touches only the testcase shipped
  with the source package and it doesn't change the binary package. The
  sleep time added is very small, so no possibility of causing testcase
  timeout.

  
  [Other Info]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+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 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

[Dario Jorge Vázquez Arguija]

This is also happening in Ubuntu 20.04 with Gnome 3.36 and is very
annoying

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

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

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

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.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/gnome-shell/+bug/1181666/+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 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

[Dan Streetman]

** Tags added: sts-sponsor-volunteer

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  New
Status in network-manager source package in Focal:
  New

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock. Adding a sleep before calling nmcli fixes the issue.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  
  [Test Case]

  2.1. Download network-manager package source code
  $ apt-get source network-manager

  2.2. Run killswitches-no-urfkill testcase
  $ cd network-manager-1.8.4
  $ sudo ./debian/tests/killswitches-no-urfkill

  
  [Regression Potential]

  No regression potential. The fix touches only the testcase shipped
  with the source package and it doesn't change the binary package. The
  sleep time added is very small, so no possibility of causing testcase
  timeout.

  
  [Other Info]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

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