[Desktop-packages] [Bug 1863463] [NEW] Firefox 75 requires nodejs >= 10.19

[Rico Tzschichholz]

Public bug reported:

Firefox trunk, to become version 75.0 in April 2020, has bumped its
nodejs requirement to 10.19
(https://bugzilla.mozilla.org/show_bug.cgi?id=1547823).

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

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

Title:
  Firefox 75 requires nodejs >= 10.19

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox trunk, to become version 75.0 in April 2020, has bumped its
  nodejs requirement to 10.19
  (https://bugzilla.mozilla.org/show_bug.cgi?id=1547823).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1863463/+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 1863460] [NEW] no more keyboard on snap apps

[Benoit]

Public bug reported:

Dear support team,

I have chromium, gnome-calculator and darktable installed via snap.
Keyboard does not work anymore since yesterday when i dist-upgraded.

snapd package has not been updated for a while. i do regular upgrades,
and this only happened since yesterday.

i am running ubuntu 20.04, apport report attached

Thanks,
Benoit.

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

** Attachment added: "snapd-apport"
   
https://bugs.launchpad.net/bugs/1863460/+attachment/5328631/+files/snapd-apport

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

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

Title:
  no more keyboard on snap apps

Status in snapd package in Ubuntu:
  New

Bug description:
  Dear support team,

  I have chromium, gnome-calculator and darktable installed via snap.
  Keyboard does not work anymore since yesterday when i dist-upgraded.

  snapd package has not been updated for a while. i do regular upgrades,
  and this only happened since yesterday.

  i am running ubuntu 20.04, apport report attached

  Thanks,
  Benoit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1863460/+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: New => Fix Committed

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

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 1856710] Re: Gnome's window manager put Firefox's window on the left half of the screen when Firefox was on the right side of the screen when I gave the PC a reboot command via

[Launchpad Bug Tracker]

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

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

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

Title:
  Gnome's window manager put Firefox's window on the left half of the
  screen when Firefox was on the right side of the screen when I gave
  the PC a reboot command via the Menu Bar

Status in gnome-shell package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  The Firefox Window was "Clipped" to the right side of the screen, as I
  dragged the window to the right screen border and the window changed
  size automatically. When I reopened Firefox after I rebooted, Firefox
  opened while snapped to the LEFT side of the screen before correcting
  itself later.

  Ubuntu 19.10

  gnome-shell:
Installed: 3.34.1+git20191024-1ubuntu1~19.10.1
Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1
Version table:
   *** 3.34.1+git20191024-1ubuntu1~19.10.1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.34.1-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Tue Dec 17 08:51:29 2019
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edwin  1403 F pulseaudio
  BuildID: 20191205203726
  Channel: Unavailable
  DistroRelease: Ubuntu 19.10
  ForcedLayersAccel: False
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NoProfiles: True
  Package: firefox 71.0+build5-0ubuntu0.19.10.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RunningIncompatibleAddons: False
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: mutter 3.34.1+git20191107-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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

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

[Desktop-packages] [Bug 1856710] Re: Gnome's window manager put Firefox's window on the left half of the screen when Firefox was on the right side of the screen when I gave the PC a reboot command via

[Launchpad Bug Tracker]

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

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

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

Title:
  Gnome's window manager put Firefox's window on the left half of the
  screen when Firefox was on the right side of the screen when I gave
  the PC a reboot command via the Menu Bar

Status in gnome-shell package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired

Bug description:
  The Firefox Window was "Clipped" to the right side of the screen, as I
  dragged the window to the right screen border and the window changed
  size automatically. When I reopened Firefox after I rebooted, Firefox
  opened while snapped to the LEFT side of the screen before correcting
  itself later.

  Ubuntu 19.10

  gnome-shell:
Installed: 3.34.1+git20191024-1ubuntu1~19.10.1
Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1
Version table:
   *** 3.34.1+git20191024-1ubuntu1~19.10.1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.34.1-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Tue Dec 17 08:51:29 2019
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edwin  1403 F pulseaudio
  BuildID: 20191205203726
  Channel: Unavailable
  DistroRelease: Ubuntu 19.10
  ForcedLayersAccel: False
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NoProfiles: True
  Package: firefox 71.0+build5-0ubuntu0.19.10.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RunningIncompatibleAddons: False
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: mutter 3.34.1+git20191107-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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

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

[Desktop-packages] [Bug 1848148] Re: Routes editing dialog is incorrectly displayed

[spike speigel]

Fixes accepted upstream with:

https://gitlab.gnome.org/GNOME/network-manager-
applet/commit/2ebefe2595d723e2fd3d7aeaf6eec3bfd962c085

https://gitlab.gnome.org/GNOME/network-manager-
applet/commit/8fbcbcece414cc583d380c2fcb2a45925d39dbbb

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

Title:
  Routes editing dialog is incorrectly displayed

Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  When I open the routes editing dialog, parts of the window are transparent 
(see attachment).
  That's obviously not by design.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager-gnome 1.8.22-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1
  Uname: Linux 5.3.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Oct 15 10:29:43 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2019-09-26 (18 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  IpRoute:
   default via 192.168.111.2 dev ens33 proto dhcp metric 100 
   10.20.10.0/24 dev ens38 proto kernel scope link src 10.20.10.100 metric 101 
   169.254.0.0/16 dev ens38 scope link metric 1000 
   192.168.111.0/24 dev ens33 proto kernel scope link src 192.168.111.130 
metric 100
  IwConfig:
   ens33 no wireless extensions.
   
   lono wireless extensions.
   
   ens38 no wireless extensions.
  RfKill:
   
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE  IP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH   
   CONNECTIONCON-UUID   
   CON-PATH
   ens33   ethernet  connected  full  full  
/org/freedesktop/NetworkManager/Devices/2  NAT   
52e7dfdb-10e3-3dc1-b53b-c314a602ae48  
/org/freedesktop/NetworkManager/ActiveConnection/22 
   ens38   ethernet  connected  limited   limited   
/org/freedesktop/NetworkManager/Devices/3  CPE - 10.20.10.1  
984da49a-f0b1-3e7d-8bec-031736b5c2fd  
/org/freedesktop/NetworkManager/ActiveConnection/23 
   lo  loopback  unmanaged  unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
  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-applet/+bug/1848148/+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 1861481] Re: language-options causes live CD sessions to be untranslated

[Martin Wimpress]

** Changed in: lightdm (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  language-options causes live CD sessions to be untranslated

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call 
/usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly 
updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking 
that Greek aren't supported; while they're all there, since e.g. MATE doesn't 
rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1861481/+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 540751] Re: Unable to use dead keys with java and ibus

[Johny]

I've created a new bug report here:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1863080

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

Title:
  Unable to use dead keys with java and ibus

Status in ibus package in Ubuntu:
  Invalid
Status in openjdk-6 package in Ubuntu:
  Invalid
Status in openjdk-7 package in Ubuntu:
  Invalid

Bug description:
  Using latest Lucid packages, I am unable to use ^ key to generate ê
  french character in every Java programs (jEdit, Netbeans, etc.).

  Typing ^ + e give just the e character.
  Typing ^ + Space and nothing appears.

  I've tried with Sun JDK (6u18, 6u20, 7) and the bug is still present.

  I've tried to remove ibus and everything works again (I've just unset
  XMODIFIERS and GTK_IM_MODULE).

  I don't know if it's an ibus bug or openjdk one.

  ProblemType: Bug
  Architecture: amd64
  Date: Thu Mar 18 09:03:11 2010
  DistroRelease: Ubuntu 10.04
  ExecutablePath: /usr/lib/jvm/java-6-openjdk/jre/bin/java
  InstallationMedia: Error: [Errno 13] Permission non accordée: 
'/var/log/installer/media-info'
  NonfreeKernelModules: nvidia
  Package: openjdk-6-jre-headless 6b18~pre2-1ubuntu1
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=fr_FR.utf8
  ProcVersionSignature: Ubuntu 2.6.32-16.25-genUser Name
  SourcePackage: openjdk-6
  Uname: Linux 2.6.32-16-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/540751/+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 1863424] Re: Regression on Canon LiDE 120 by fix for #1731459

[Gunnar Hjalmarsson]

Did you see bug #1862926?

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

Title:
  Regression on Canon LiDE 120 by fix for #1731459

Status in sane-backends package in Ubuntu:
  Invalid

Bug description:
  THIS IS INCORRECT! I mis-remembered it working on 18.04 earlier.

  SANE 1.0.29 properly fixes #1731459 for a LiDE 120 scanner.
  -- original report


  sane-backends (1.0.27-1~experimental3ubuntu2.2) brought a fix for a black 
vertical band on scans
  done with e.g. Canon LiDE 100 and 200 scanners on Ubuntu 18.04 as noted here:

     sane-backends (1.0.27-1~experimental3ubuntu2.2) bionic;
  urgency=medium

   * debian/patches/git-fix-discolored-bar-issue.patch:
     - Upstream commit to fix issue with discolored bar on Genesys GL847
   scanners (LP: #1731459).

  -- Gunnar Hjalmarsson   Thu, 08 Aug 2019
  20:27:00 +0200

  However, on my Canon LiDE 120 it worked fine before that fix in 18.04, but 
now the image shows
  a discolored band at precisely the same location where on an LiDE 100/200 the 
black band
  used to be.

  See attached test scan for an example and compare with the uploads from
  https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1731459 .

  Affected are also daily builds of 20.04 from 2020-02-15.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1863424/+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 1854676] Re: Web Midi API Doesn't Work in Snap-Version of Chromium

[Ryan Frazier]

My current work around is to remove the snap version of Chromium and
replace it with Debian-stable.

You can find the instructions on StackOverflow at
https://askubuntu.com/a/1206502

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

Title:
  Web Midi API Doesn't Work in Snap-Version of Chromium

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  With aspirations of creating a web based Midi tool, using Ubuntu 19.10, I'm 
trying to test out the Web Midi API:
  https://www.w3.org/TR/webmidi/

  Although it is supposed to be supported in Chromium, none of these samples 
work in Ubuntu 19.10's snap-package installation of Chromium:
  https://webaudio.github.io/demo-list/

  In the meantime, please recommend a work-around of how I can work with
  the Web Midi API while using Ubuntu Linux as my operating system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1854676/+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 1863412] Re: [snap] after accepting daily updates Chromium doesn't accept keyboard input

[Cliff Carson]

The work around indeed worked for me but when I tried to recover my
Bookmarks from an archive file after pressing "Choose a file" chromium
terminated.  Think this message in syslog is associated with the error:

Feb 15 13:17:54 cliffps chromium_chromium.desktop[6306]:
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon:
assertion failed (error == NULL): Failed to load /snap/chromium/1026
/data-dir/icons/Adwaita/16x16/status/image-missing.png: Unrecognized
image file format (gdk-pixbuf-error-quark, 3)

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

Title:
  [snap] after accepting daily updates Chromium doesn't accept keyboard
  input

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I booted my laptop this morning and was offered a large number of
  updates. I installed them all and started Chromium only to find that I
  was unable to type any character into the address bar. When using the
  mouse to select a bookmark to load a web page I found that keyboard
  input was also ignored.

  I was running Chromium when last using this Ubuntu installation and
  made no changes before closing down. The only changes since that last
  session were made by the updates that I installed so I have attached
  an extract of apt's history.log.

  Google Chrome and Firefox work perfectly. Xubuntu doesn't seem to be
  affected by recent updates.

  Work around found:
  Remove ~/snap/chromium/common/.cache and restart Chromium

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 80.0.3987.87-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: GNOME
  DRM.card0-DP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAdZRUCAQAAACoVAQSlNB544gywoldRnycKUFS/zwDRwLMAlQCBgIGKgQCBSgEBAjqAGHE4LUBYLEUACSUhAAAe/wAwMDAwMDAwMQogICAg/QA4Sx5TDwAKICAgICAg/ABFRjIyMGEKICAgICAgAGI=
   modes: 1920x1080 1680x1050 1280x1024 1280x1024 1280x1024 1440x900 1280x960 
1280x800 1024x768 1024x768 1024x768 800x600 800x600 800x600 800x600 640x480 
640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-3:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wANrsQVACgXAQSVIhN4Au8FkFRSkyklUFQBAQEBAQEBAQEBAQEBAQEBXjWAlnA4FEAsHCQAWMEQAAAY/gBOMTU2SEdFLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTU2SEdFLUVBQgogAB0=
   modes: 1920x1080
  Date: Sat Feb 15 11:00:22 2020
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sda2  ext473G   16G   54G  23% /home
   tmpfs  tmpfs  3.9G  174M  3.7G   5% /dev/shm
   /dev/sda2  ext473G   16G   54G  23% /home
  InstallationDate: Installed on 2019-05-17 (274 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  MachineType: Novatech N350DW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=35cc812a-75e8-4a5a-83d0-bd336006d2f6 ro quiet splash vt.handoff=7
  Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium'] 
failed with exit code 1: error: no changes found
  Snap.ChromeDriverVersion: ChromeDriver 80.0.3987.100 
(3f00c26d457663a424865bbef1179f72eec1b9fe-refs/branch-heads/3987@{#864})
  Snap.ChromiumVersion: Chromium 80.0.3987.100 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to focal on 2019-11-08 (98 days ago)
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N350DW
  dmi.board.vendor: Novatech
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Novatech
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd03/10/2017:svnNovatech:pnN350DW:pvrNotApplicable:rvnNovatech:rnN350DW:rvrNotApplicable:cvnNovatech:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N350DW
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Novatech

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1863412/+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 1851385] Re: ubuntu 19.10 / print bug : requires authentication

[Alexey Nikitin]

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

I have the same issue on two PCs with HP LaserJet 1020 printer connected
to the Wi-Fi router on Ubuntu 19.10.

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

Title:
  ubuntu 19.10 / print bug : requires authentication

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have 2 computers(one laptop and one desktop) which have a dual boot
  Windows / Ubuntu. My printer (Xerox WorkCentre 6015B) is plugged on a
  USB port from my modem on which my computers are connected using Wi-
  Fi.

  Since the upgrade of Ubuntu to version 19.10, I cannot print. On both
  computers I get the same message : [The printer] requires
  authentication / credentials required in order to print.

  With Ubuntu 19.04, I had absolutely no problem. I tried with a live
  USB with Ubuntu 19.04, there is no problem, the printer works. With a
  Ubuntu live 19.10, it doesn't work.

  If I plug the printer directly on a USB port on my computer, I get the
  same error message : [The printer] requires authentication /
  credentials required in order to print.

  It's the same behaviour on both computers, no I guess it must be a
  bug. Anyway I don't know which authentication I could do, with which
  ID and password ?

  Thank you very much

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  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.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 15:12:07 2019
  Lpstat: device for Xerox_WorkCentre_6015B_Wi-Fi: 
smb://FREEBOX_SERVER/Xerox%20WorkCentre%206015B
  MachineType: Acer Aspire V5-571
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=fb8ccf3e-9970-4066-bae2-26fe4387c122 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V5-571
  dmi.board.vendor: Acer
  dmi.board.version: V2.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.15
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd12/21/2012:svnAcer:pnAspireV5-571:pvrV2.15:rvnAcer:rnAspireV5-571:rvrV2.15:cvnAcer:ct9:cvrV2.15:
  dmi.product.family: Aspire V5-571
  dmi.product.name: Aspire V5-571
  dmi.product.sku: Aspire V5-571_072A_2.15
  dmi.product.version: V2.15
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1851385/+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 1863424] Re: Regression on Canon LiDE 120 by fix for #1731459

[nmaxx]

** Attachment removed: "test scan showing the vertical band"
   
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1863424/+attachment/5328427/+files/lide120.png

** Description changed:

+ THIS IS INCORRECT! I mis-remembered it working on 18.04 earlier.
+ 
+ SANE 1.0.29 properly fixes #1731459 for a LiDE 120 scanner.
+ -- original report
+ 
+ 
  sane-backends (1.0.27-1~experimental3ubuntu2.2) brought a fix for a black 
vertical band on scans
  done with e.g. Canon LiDE 100 and 200 scanners on Ubuntu 18.04 as noted here:
  
-sane-backends (1.0.27-1~experimental3ubuntu2.2) bionic;
+    sane-backends (1.0.27-1~experimental3ubuntu2.2) bionic;
  urgency=medium
  
-  * debian/patches/git-fix-discolored-bar-issue.patch:
-- Upstream commit to fix issue with discolored bar on Genesys GL847
-  scanners (LP: #1731459).
+  * debian/patches/git-fix-discolored-bar-issue.patch:
+    - Upstream commit to fix issue with discolored bar on Genesys GL847
+  scanners (LP: #1731459).
  
- -- Gunnar Hjalmarsson   Thu, 08 Aug 2019
+ -- Gunnar Hjalmarsson   Thu, 08 Aug 2019
  20:27:00 +0200
  
  However, on my Canon LiDE 120 it worked fine before that fix in 18.04, but 
now the image shows
  a discolored band at precisely the same location where on an LiDE 100/200 the 
black band
  used to be.
  
  See attached test scan for an example and compare with the uploads from
  https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1731459 .
  
  Affected are also daily builds of 20.04 from 2020-02-15.

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

Title:
  Regression on Canon LiDE 120 by fix for #1731459

Status in sane-backends package in Ubuntu:
  Invalid

Bug description:
  THIS IS INCORRECT! I mis-remembered it working on 18.04 earlier.

  SANE 1.0.29 properly fixes #1731459 for a LiDE 120 scanner.
  -- original report


  sane-backends (1.0.27-1~experimental3ubuntu2.2) brought a fix for a black 
vertical band on scans
  done with e.g. Canon LiDE 100 and 200 scanners on Ubuntu 18.04 as noted here:

     sane-backends (1.0.27-1~experimental3ubuntu2.2) bionic;
  urgency=medium

   * debian/patches/git-fix-discolored-bar-issue.patch:
     - Upstream commit to fix issue with discolored bar on Genesys GL847
   scanners (LP: #1731459).

  -- Gunnar Hjalmarsson   Thu, 08 Aug 2019
  20:27:00 +0200

  However, on my Canon LiDE 120 it worked fine before that fix in 18.04, but 
now the image shows
  a discolored band at precisely the same location where on an LiDE 100/200 the 
black band
  used to be.

  See attached test scan for an example and compare with the uploads from
  https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1731459 .

  Affected are also daily builds of 20.04 from 2020-02-15.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1863424/+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 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish

[nmaxx]

I tried the genesys backend from the official 1.0.29 release and it
works fine. Please make sure that makes it into 20.04, which right now
is still the broken 1.0.27 experimental version.

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10+,  18.04 LTS and 18.10 Cosmic cuttlefish

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

Bug description:
  [Impact]

  When using a Genesys GL847 scanner, the documents get disfigured by a
  discolored bar. The proposed uploads should fix the issue. They are
  available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends

  [Test case]

  1. Install the libsane (libsane1 in bionic), libsane-common
 and sane-utils packages from {bionic,disco]-proposed.

  2. Use an affected device to scan, and find that the issue is
 no longer present.

  [Regression risk]

  Upstream commit, focused bug fix => low regression risk

  [Original description]

  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+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 1855757] Re: [nvidia] Background image corrupted after standby

[Giles]

Similar problem here, first few resumes only the desktop background
corrupts then after a few more more the entire desktop goes, please see
attached:

01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT
330M] (rev a2)

Using NVIDIA binary driver - version 340.108 from nvidia-340



** Attachment added: "Screenshot from 2020-02-15 16-19-52.png"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+attachment/5328428/+files/Screenshot%20from%202020-02-15%2016-19-52.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/1855757

Title:
  [nvidia] Background image corrupted after standby

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

Bug description:
  Looks similar to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407

  When the computer goes to standby, the background image becomes
  corrupted.

  I am able to fix by "killall Xorg" , change the background image
  (settings > background) and restart.  Haven't tried login logout.

  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
  .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.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   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'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  9 10:58:35 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed
   nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c]
  InstallationDate: Installed on 2019-11-29 (10 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTek Computer Inc. G60JX
  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=65117975-c95f-4406-a7cf-da912cda0e70 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G60JX
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.family: PEGA Family
  dmi.product.name: G60JX
  dmi.product.sku: 0
  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.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  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 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855757/+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 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish

[nmaxx]

nevermind the previous comment, it's no regression it just does not work
properly with the 120

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10+,  18.04 LTS and 18.10 Cosmic cuttlefish

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

Bug description:
  [Impact]

  When using a Genesys GL847 scanner, the documents get disfigured by a
  discolored bar. The proposed uploads should fix the issue. They are
  available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends

  [Test case]

  1. Install the libsane (libsane1 in bionic), libsane-common
 and sane-utils packages from {bionic,disco]-proposed.

  2. Use an affected device to scan, and find that the issue is
 no longer present.

  [Regression risk]

  Upstream commit, focused bug fix => low regression risk

  [Original description]

  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+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 1863424] Re: Regression on Canon LiDE 120 by fix for #1731459

[nmaxx]

I tried with an old 18.04.1 ISO and the same issue appeared, so it was
likely no regression after all just a fix that did not work 100% . I
must have misremembered it working properly...

** Changed in: sane-backends (Ubuntu)
   Status: New => Invalid

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

Title:
  Regression on Canon LiDE 120 by fix for #1731459

Status in sane-backends package in Ubuntu:
  Invalid

Bug description:
  sane-backends (1.0.27-1~experimental3ubuntu2.2) brought a fix for a black 
vertical band on scans
  done with e.g. Canon LiDE 100 and 200 scanners on Ubuntu 18.04 as noted here:

 sane-backends (1.0.27-1~experimental3ubuntu2.2) bionic;
  urgency=medium

   * debian/patches/git-fix-discolored-bar-issue.patch:
 - Upstream commit to fix issue with discolored bar on Genesys GL847
   scanners (LP: #1731459).

  -- Gunnar Hjalmarsson   Thu, 08 Aug 2019
  20:27:00 +0200

  However, on my Canon LiDE 120 it worked fine before that fix in 18.04, but 
now the image shows
  a discolored band at precisely the same location where on an LiDE 100/200 the 
black band
  used to be.

  See attached test scan for an example and compare with the uploads from
  https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1731459 .

  Affected are also daily builds of 20.04 from 2020-02-15.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1863424/+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 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish

[nmaxx]

Note that the released fix caused a regression on Canon LiDE 120
scanners, see https://bugs.launchpad.net/ubuntu/+source/sane-
backends/+bug/1863424

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10+,  18.04 LTS and 18.10 Cosmic cuttlefish

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

Bug description:
  [Impact]

  When using a Genesys GL847 scanner, the documents get disfigured by a
  discolored bar. The proposed uploads should fix the issue. They are
  available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends

  [Test case]

  1. Install the libsane (libsane1 in bionic), libsane-common
 and sane-utils packages from {bionic,disco]-proposed.

  2. Use an affected device to scan, and find that the issue is
 no longer present.

  [Regression risk]

  Upstream commit, focused bug fix => low regression risk

  [Original description]

  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+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 1863424] [NEW] Regression on Canon LiDE 120 by fix for #1731459

[nmaxx]

Public bug reported:

sane-backends (1.0.27-1~experimental3ubuntu2.2) brought a fix for a black 
vertical band on scans
done with e.g. Canon LiDE 100 and 200 scanners on Ubuntu 18.04 as noted here:

   sane-backends (1.0.27-1~experimental3ubuntu2.2) bionic;
urgency=medium

 * debian/patches/git-fix-discolored-bar-issue.patch:
   - Upstream commit to fix issue with discolored bar on Genesys GL847
 scanners (LP: #1731459).

-- Gunnar Hjalmarsson   Thu, 08 Aug 2019
20:27:00 +0200

However, on my Canon LiDE 120 it worked fine before that fix in 18.04, but now 
the image shows
a discolored band at precisely the same location where on an LiDE 100/200 the 
black band
used to be.

See attached test scan for an example and compare with the uploads from
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1731459 .

Affected are also daily builds of 20.04 from 2020-02-15.

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "test scan showing the vertical band"
   
https://bugs.launchpad.net/bugs/1863424/+attachment/5328427/+files/lide120.png

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

Title:
  Regression on Canon LiDE 120 by fix for #1731459

Status in sane-backends package in Ubuntu:
  New

Bug description:
  sane-backends (1.0.27-1~experimental3ubuntu2.2) brought a fix for a black 
vertical band on scans
  done with e.g. Canon LiDE 100 and 200 scanners on Ubuntu 18.04 as noted here:

 sane-backends (1.0.27-1~experimental3ubuntu2.2) bionic;
  urgency=medium

   * debian/patches/git-fix-discolored-bar-issue.patch:
 - Upstream commit to fix issue with discolored bar on Genesys GL847
   scanners (LP: #1731459).

  -- Gunnar Hjalmarsson   Thu, 08 Aug 2019
  20:27:00 +0200

  However, on my Canon LiDE 120 it worked fine before that fix in 18.04, but 
now the image shows
  a discolored band at precisely the same location where on an LiDE 100/200 the 
black band
  used to be.

  See attached test scan for an example and compare with the uploads from
  https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1731459 .

  Affected are also daily builds of 20.04 from 2020-02-15.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1863424/+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 1861345] Re: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1

[Richard Anthony Horan]

sudo alsactl store does not save the headphone volume so I have to re-
adjust every boot.

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

Title:
  Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted
  Front speakers 5.1

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04.3 LTS
  Kernel 5.5.0
  pulseaudio:
Installed: 1:11.1-1ubuntu7.4
  X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound.

  I have surround 5.1 speakers and the Front Left and Right are Muted.  
  I have to unmute Headphones in alsamixer to hear sound from the front left 
and right speakers is the workaround.

  This step should not be required for speakers 5.1 to work.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard2533 F pulseaudio
   /dev/snd/controlC1:  richard2533 F pulseaudio
   /dev/snd/controlC0:  richard2533 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-28 (2 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on 
vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-28-generic N/A
   linux-backports-modules-5.3.0-28-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS MASTER
  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 string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+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 1863412] Re: [snap] after accepting daily updates Chromium doesn't accept keyboard input

[Paul White]

Work around found: Remove ~/snap/chromium/common/.cache after closing
browser. Chromium works as it should when restarted. I'll leave this bug
report in place as the problem shouldn't have happened and needs
investigation.

** Description changed:

  I booted my laptop this morning and was offered a large number of
  updates. I installed them all and started Chromium only to find that I
  was unable to type any character into the address bar. When using the
  mouse to select a bookmark to load a web page I found that keyboard
  input was also ignored.
  
  I was running Chromium when last using this Ubuntu installation and made
  no changes before closing down. The only changes since that last session
  were made by the updates that I installed so I have attached an extract
  of apt's history.log.
  
  Google Chrome and Firefox work perfectly. Xubuntu doesn't seem to be
  affected by recent updates.
+ 
+ Work around found:
+ Remove ~/snap/chromium/common/.cache and restart Chromium
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 80.0.3987.87-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: GNOME
  DRM.card0-DP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAdZRUCAQAAACoVAQSlNB544gywoldRnycKUFS/zwDRwLMAlQCBgIGKgQCBSgEBAjqAGHE4LUBYLEUACSUhAAAe/wAwMDAwMDAwMQogICAg/QA4Sx5TDwAKICAgICAg/ABFRjIyMGEKICAgICAgAGI=
   modes: 1920x1080 1680x1050 1280x1024 1280x1024 1280x1024 1440x900 1280x960 
1280x800 1024x768 1024x768 1024x768 800x600 800x600 800x600 800x600 640x480 
640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-3:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wANrsQVACgXAQSVIhN4Au8FkFRSkyklUFQBAQEBAQEBAQEBAQEBAQEBXjWAlnA4FEAsHCQAWMEQAAAY/gBOMTU2SEdFLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTU2SEdFLUVBQgogAB0=
   modes: 1920x1080
  Date: Sat Feb 15 11:00:22 2020
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sda2  ext473G   16G   54G  23% /home
   tmpfs  tmpfs  3.9G  174M  3.7G   5% /dev/shm
   /dev/sda2  ext473G   16G   54G  23% /home
  InstallationDate: Installed on 2019-05-17 (274 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  MachineType: Novatech N350DW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=35cc812a-75e8-4a5a-83d0-bd336006d2f6 ro quiet splash vt.handoff=7
  Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium'] 
failed with exit code 1: error: no changes found
  Snap.ChromeDriverVersion: ChromeDriver 80.0.3987.100 
(3f00c26d457663a424865bbef1179f72eec1b9fe-refs/branch-heads/3987@{#864})
  Snap.ChromiumVersion: Chromium 80.0.3987.100 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to focal on 2019-11-08 (98 days ago)
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N350DW
  dmi.board.vendor: Novatech
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Novatech
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd03/10/2017:svnNovatech:pnN350DW:pvrNotApplicable:rvnNovatech:rnN350DW:rvrNotApplicable:cvnNovatech:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N350DW
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Novatech

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

Title:
  [snap] after accepting daily updates Chromium doesn't accept keyboard
  input

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I booted my laptop this morning and was offered a large number of
  updates. I installed them all and started Chromium only to find that I
  was unable to type any character into the address bar. When using the
  mouse to select a bookmark to load a web page I found that keyboard
  input was also ignored.

  I was running Chromium when last using this Ubuntu installation and
  made no changes before closing down. The only changes since that last
  session were made by the updates that I installed so I have attached
  an extract of apt's history.log.

  Google Chrome and Firefox work perfectly. Xubuntu doesn't seem to be
  affected by recent updates.

  Work around found:
  Re

[Desktop-packages] [Bug 1863412] Re: [snap] after accepting daily updates Chromium doesn't accept keyboard input

[Launchpad Bug Tracker]

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

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

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

Title:
  [snap] after accepting daily updates Chromium doesn't accept keyboard
  input

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  I booted my laptop this morning and was offered a large number of
  updates. I installed them all and started Chromium only to find that I
  was unable to type any character into the address bar. When using the
  mouse to select a bookmark to load a web page I found that keyboard
  input was also ignored.

  I was running Chromium when last using this Ubuntu installation and
  made no changes before closing down. The only changes since that last
  session were made by the updates that I installed so I have attached
  an extract of apt's history.log.

  Google Chrome and Firefox work perfectly. Xubuntu doesn't seem to be
  affected by recent updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 80.0.3987.87-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: GNOME
  DRM.card0-DP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAdZRUCAQAAACoVAQSlNB544gywoldRnycKUFS/zwDRwLMAlQCBgIGKgQCBSgEBAjqAGHE4LUBYLEUACSUhAAAe/wAwMDAwMDAwMQogICAg/QA4Sx5TDwAKICAgICAg/ABFRjIyMGEKICAgICAgAGI=
   modes: 1920x1080 1680x1050 1280x1024 1280x1024 1280x1024 1440x900 1280x960 
1280x800 1024x768 1024x768 1024x768 800x600 800x600 800x600 800x600 640x480 
640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-3:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wANrsQVACgXAQSVIhN4Au8FkFRSkyklUFQBAQEBAQEBAQEBAQEBAQEBXjWAlnA4FEAsHCQAWMEQAAAY/gBOMTU2SEdFLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTU2SEdFLUVBQgogAB0=
   modes: 1920x1080
  Date: Sat Feb 15 11:00:22 2020
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sda2  ext473G   16G   54G  23% /home
   tmpfs  tmpfs  3.9G  174M  3.7G   5% /dev/shm
   /dev/sda2  ext473G   16G   54G  23% /home
  InstallationDate: Installed on 2019-05-17 (274 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  MachineType: Novatech N350DW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=35cc812a-75e8-4a5a-83d0-bd336006d2f6 ro quiet splash vt.handoff=7
  Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium'] 
failed with exit code 1: error: no changes found
  Snap.ChromeDriverVersion: ChromeDriver 80.0.3987.100 
(3f00c26d457663a424865bbef1179f72eec1b9fe-refs/branch-heads/3987@{#864})
  Snap.ChromiumVersion: Chromium 80.0.3987.100 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to focal on 2019-11-08 (98 days ago)
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N350DW
  dmi.board.vendor: Novatech
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Novatech
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd03/10/2017:svnNovatech:pnN350DW:pvrNotApplicable:rvnNovatech:rnN350DW:rvrNotApplicable:cvnNovatech:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N350DW
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Novatech

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1863412/+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 1863412] Re: [snap] after accepting daily updates Chromium doesn't accept keyboard input

[Paul White]

** Description changed:

  I booted my laptop this morning and was offered a large number of
  updates. I installed them all and started Chromium only to find that I
- was unable to type any character into the address bar. When using a
- bookmark to load a web page I found that keyboard input was also
- ignored.
+ was unable to type any character into the address bar. When using the
+ mouse to select a bookmark to load a web page I found that keyboard
+ input was also ignored.
  
  I was running Chromium when last using this Ubuntu installation and made
  no changes before closing down. The only changes since that last session
  were made by the updates that I installed so I have attached an extract
  of apt's history.log.
  
- Google Chrome and Firefox work perfectly.
+ Google Chrome and Firefox work perfectly. Xubuntu doesn't seem to be
+ affected by recent updates.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 80.0.3987.87-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: GNOME
  DRM.card0-DP-1:
-  enabled: enabled
-  dpms: On
-  status: connected
-  edid-base64: 
AP///wAdZRUCAQAAACoVAQSlNB544gywoldRnycKUFS/zwDRwLMAlQCBgIGKgQCBSgEBAjqAGHE4LUBYLEUACSUhAAAe/wAwMDAwMDAwMQogICAg/QA4Sx5TDwAKICAgICAg/ABFRjIyMGEKICAgICAgAGI=
-  modes: 1920x1080 1680x1050 1280x1024 1280x1024 1280x1024 1440x900 1280x960 
1280x800 1024x768 1024x768 1024x768 800x600 800x600 800x600 800x600 640x480 
640x480 640x480 640x480 720x400
+  enabled: enabled
+  dpms: On
+  status: connected
+  edid-base64: 
AP///wAdZRUCAQAAACoVAQSlNB544gywoldRnycKUFS/zwDRwLMAlQCBgIGKgQCBSgEBAjqAGHE4LUBYLEUACSUhAAAe/wAwMDAwMDAwMQogICAg/QA4Sx5TDwAKICAgICAg/ABFRjIyMGEKICAgICAgAGI=
+  modes: 1920x1080 1680x1050 1280x1024 1280x1024 1280x1024 1440x900 1280x960 
1280x800 1024x768 1024x768 1024x768 800x600 800x600 800x600 800x600 640x480 
640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-1:
-  enabled: disabled
-  dpms: Off
-  status: disconnected
-  edid-base64: 
-  modes:
+  enabled: disabled
+  dpms: Off
+  status: disconnected
+  edid-base64:
+  modes:
  DRM.card0-HDMI-A-2:
-  enabled: disabled
-  dpms: Off
-  status: disconnected
-  edid-base64: 
-  modes:
+  enabled: disabled
+  dpms: Off
+  status: disconnected
+  edid-base64:
+  modes:
  DRM.card0-HDMI-A-3:
-  enabled: disabled
-  dpms: Off
-  status: disconnected
-  edid-base64: 
-  modes:
+  enabled: disabled
+  dpms: Off
+  status: disconnected
+  edid-base64:
+  modes:
  DRM.card0-eDP-1:
-  enabled: enabled
-  dpms: On
-  status: connected
-  edid-base64: 
AP///wANrsQVACgXAQSVIhN4Au8FkFRSkyklUFQBAQEBAQEBAQEBAQEBAQEBXjWAlnA4FEAsHCQAWMEQAAAY/gBOMTU2SEdFLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTU2SEdFLUVBQgogAB0=
-  modes: 1920x1080
+  enabled: enabled
+  dpms: On
+  status: connected
+  edid-base64: 
AP///wANrsQVACgXAQSVIhN4Au8FkFRSkyklUFQBAQEBAQEBAQEBAQEBAQEBXjWAlnA4FEAsHCQAWMEQAAAY/gBOMTU2SEdFLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTU2SEdFLUVBQgogAB0=
+  modes: 1920x1080
  Date: Sat Feb 15 11:00:22 2020
  DiskUsage:
-  Filesystem Type   Size  Used Avail Use% Mounted on
-  /dev/sda2  ext473G   16G   54G  23% /home
-  tmpfs  tmpfs  3.9G  174M  3.7G   5% /dev/shm
-  /dev/sda2  ext473G   16G   54G  23% /home
+  Filesystem Type   Size  Used Avail Use% Mounted on
+  /dev/sda2  ext473G   16G   54G  23% /home
+  tmpfs  tmpfs  3.9G  174M  3.7G   5% /dev/shm
+  /dev/sda2  ext473G   16G   54G  23% /home
  InstallationDate: Installed on 2019-05-17 (274 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  MachineType: Novatech N350DW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=35cc812a-75e8-4a5a-83d0-bd336006d2f6 ro quiet splash vt.handoff=7
  Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium'] 
failed with exit code 1: error: no changes found
  Snap.ChromeDriverVersion: ChromeDriver 80.0.3987.100 
(3f00c26d457663a424865bbef1179f72eec1b9fe-refs/branch-heads/3987@{#864})
  Snap.ChromiumVersion: Chromium 80.0.3987.100 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to focal on 2019-11-08 (98 days ago)
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N350DW
  dmi.board.vendor: Novatech
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Novatech
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd03/10/2017:svnNovatech:pnN350DW:pvrNotApplicable:rvnNovatech:rnN350DW:rvrNotApplicable:cvnNovatech:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N350DW
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  

[Desktop-packages] [Bug 1863412] [NEW] [snap] after accepting daily updates Chromium doesn't accept keyboard input

[Paul White]

Public bug reported:

I booted my laptop this morning and was offered a large number of
updates. I installed them all and started Chromium only to find that I
was unable to type any character into the address bar. When using the
mouse to select a bookmark to load a web page I found that keyboard
input was also ignored.

I was running Chromium when last using this Ubuntu installation and made
no changes before closing down. The only changes since that last session
were made by the updates that I installed so I have attached an extract
of apt's history.log.

Google Chrome and Firefox work perfectly. Xubuntu doesn't seem to be
affected by recent updates.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 80.0.3987.87-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: GNOME
DRM.card0-DP-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: 
AP///wAdZRUCAQAAACoVAQSlNB544gywoldRnycKUFS/zwDRwLMAlQCBgIGKgQCBSgEBAjqAGHE4LUBYLEUACSUhAAAe/wAwMDAwMDAwMQogICAg/QA4Sx5TDwAKICAgICAg/ABFRjIyMGEKICAgICAgAGI=
 modes: 1920x1080 1680x1050 1280x1024 1280x1024 1280x1024 1440x900 1280x960 
1280x800 1024x768 1024x768 1024x768 800x600 800x600 800x600 800x600 640x480 
640x480 640x480 640x480 720x400
DRM.card0-HDMI-A-1:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64:
 modes:
DRM.card0-HDMI-A-2:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64:
 modes:
DRM.card0-HDMI-A-3:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64:
 modes:
DRM.card0-eDP-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: 
AP///wANrsQVACgXAQSVIhN4Au8FkFRSkyklUFQBAQEBAQEBAQEBAQEBAQEBXjWAlnA4FEAsHCQAWMEQAAAY/gBOMTU2SEdFLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTU2SEdFLUVBQgogAB0=
 modes: 1920x1080
Date: Sat Feb 15 11:00:22 2020
DiskUsage:
 Filesystem Type   Size  Used Avail Use% Mounted on
 /dev/sda2  ext473G   16G   54G  23% /home
 tmpfs  tmpfs  3.9G  174M  3.7G   5% /dev/shm
 /dev/sda2  ext473G   16G   54G  23% /home
InstallationDate: Installed on 2019-05-17 (274 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
MachineType: Novatech N350DW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=35cc812a-75e8-4a5a-83d0-bd336006d2f6 ro quiet splash vt.handoff=7
Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium'] 
failed with exit code 1: error: no changes found
Snap.ChromeDriverVersion: ChromeDriver 80.0.3987.100 
(3f00c26d457663a424865bbef1179f72eec1b9fe-refs/branch-heads/3987@{#864})
Snap.ChromiumVersion: Chromium 80.0.3987.100 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to focal on 2019-11-08 (98 days ago)
dmi.bios.date: 03/10/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.12
dmi.board.asset.tag: Tag 12345
dmi.board.name: N350DW
dmi.board.vendor: Novatech
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Novatech
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd03/10/2017:svnNovatech:pnN350DW:pvrNotApplicable:rvnNovatech:rnN350DW:rvrNotApplicable:cvnNovatech:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: N350DW
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Novatech

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal snap

** Attachment added: "update.log"
   https://bugs.launchpad.net/bugs/1863412/+attachment/5328367/+files/update.log

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

Title:
  [snap] after accepting daily updates Chromium doesn't accept keyboard
  input

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I booted my laptop this morning and was offered a large number of
  updates. I installed them all and started Chromium only to find that I
  was unable to type any character into the address bar. When using the
  mouse to select a bookmark to load a web page I found that keyboard
  input was also ignored.

  I was running Chromium when last using this Ubuntu installation and
  made no changes before closing down. The only changes since that last
  session were made by the updates that I installed so I have attached
  an extract of apt's history.log.

  Google Chrome and Firefox work perfectly. Xubuntu doesn't seem to be
  affected by recent updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 80.0.3987.87-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDeskto

[Desktop-packages] [Bug 1862945] Re: Change desktop - select color no longer possible

[corrado venturini]

https://ubuntuforums.org/showthread.php?t=2436328
https://ubuntuforums.org/showthread.php?t=2430791

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

Title:
  Change desktop - select color no longer possible

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

Bug description:
  Open control center - settings - set background - select a solid color
  is not possible also if stated in the help.

  Change the desktop and lock screen backgrounds
  You can change the image used for your backgrounds or set it to be a solid 
color.

  corrado@corrado-x5-ff-0104:~$ inxi -Fxx
  System:Host: corrado-x5-ff-0104 Kernel: 5.4.0-12-generic x86_64 bits: 64 
compiler: gcc v: 9.2.1 
 Desktop: Gnome 3.34.3 wm: gnome-shell dm: GDM3 Distro: Ubuntu 
20.04 LTS (Focal Fossa) 
  Machine:   Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial:  UEFI: American Megatrends v: P1.10 
 date: 05/11/2017 
  CPU:   Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT 
MCP arch: Kaby Lake rev: 9 
 L2 cache: 3072 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 
800 3: 800 4: 803 
  Graphics:  Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: 
kernel bus ID: 00:02.0 chip ID: 8086:5912 
 Display: x11 server: X.Org 1.20.7 driver: i915 compositor: 
gnome-shell resolution: 1920x1080~60Hz 
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) 
v: 4.6 Mesa 19.3.3 compat-v: 3.0 
 direct render: Yes 
  Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: 
ASRock driver: snd_hda_intel v: kernel 
 bus ID: 00:1f.3 chip ID: 8086:a170 
 Device-2: Logitech QuickCam Pro 9000 type: USB driver: 
snd-usb-audio,uvcvideo bus ID: 1-10:5 
 chip ID: 046d:0990 
 Sound Server: ALSA v: k5.4.0-12-generic 
  Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 
3.2.6-k port: f040 bus ID: 00:1f.6 
 chip ID: 8086:15b8 
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86 
  Drives:Local Storage: total: 2.05 TiB used: 12.48 GiB (0.6%) 
 ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 
232.89 GiB speed: 31.6 Gb/s lanes: 4 
 serial: 50026B72823D1475 
 ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
speed: 6.0 Gb/s serial: 37PYNGAFS 
 ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 
GiB speed: 3.0 Gb/s 
 serial: JP2940J80Z3D3V 
  Partition: ID-1: / size: 31.25 GiB used: 12.48 GiB (39.9%) fs: ext4 dev: 
/dev/nvme0n1p5 
 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/sda2 
  Sensors:   System Temperatures: cpu: 27.0 C mobo: 29.5 C 
 Fan Speeds (RPM): fan-1: 0 fan-2: 2343 fan-3: 0 fan-4: 2268 fan-5: 
0 fan-6: 0 
 Voltages: 12v: N/A 5v: N/A 3.3v: 3.49 vbat: 3.15 
  Info:  Processes: 219 Uptime: 24m Memory: 7.49 GiB used: 1.24 GiB (16.6%) 
Init: systemd v: 244 runlevel: 5 
 Compilers: gcc: 9.2.1 alt: 9 Shell: bash v: 5.0.11 running in: 
gnome-terminal inxi: 3.0.37 
  corrado@corrado-x5-ff-0104:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.35.90-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 12 14:30:09 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-01-04 (39 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104)
  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/1862945/+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 1863391] Re: GNOME fractional scaling: fullscreen video misbehaves

[Dmitry Shachnev]

Reassigning to gnome-shell. If needed it can be further reassigned to
mutter or some other component.

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

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

Title:
  GNOME fractional scaling: fullscreen video misbehaves

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When scaling the desktop to e.g. 150%, fullscreen video does seem to
  trigger constant changes of the scaling factor: the system switches
  every 0.5s from 150% to 100% to 200% or things like those.

  The problem does not occur, when there is another windows present
  (e.g. a "always-on-top" terminal windows).

  Also, KDE doesn't have this problem.

  The problem exists in freshly installed 19.10 and 20.04, too. I couldn't find 
any reason, why sometimes firefox fullscreen videos do work and sometimes not. 
  Video playback (e.g. GNOME video player or VLC) does not work properly in 
19.10, whereas it works most of the time in 20.04.

  How can I help to dig into this?

  1) Ubuntu 19.10, 20.04
  2) latest available (problem exists since several weeks)
  3) What you expected to happen: fullscreen video playback in scaled mode
  4) What happened instead: screen starts changing (randomly?) the scaling 
factor or at least this is the impression one gets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1863391/+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 1863400] Re: gnome-shell reports problem on boot

[Dave Goldsbrough]

** Description changed:

  Problem reported at boot but does not seem to collect data and send, just 
does nothing.
+ See attached screenshot of window.
  Still able to use laptop.
  This file exists in /var/crash
  -rw-r-  1 gdm  whoopsie 21900809 Feb 14 22:01 
_usr_bin_gnome-shell.121.crash
  
  The time of this file must have been at last shutdown which did take a
  little longer than usual.
  
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  
  gnome-shell:
-   Installed: 3.28.4-0ubuntu18.04.3
-   Candidate: 3.28.4-0ubuntu18.04.3
-   Version table:
-  *** 3.28.4-0ubuntu18.04.3 500
- 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  3.28.3+git20190124-0ubuntu18.04.2 500
- 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
-  3.28.1-0ubuntu2 500
- 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
+   Installed: 3.28.4-0ubuntu18.04.3
+   Candidate: 3.28.4-0ubuntu18.04.3
+   Version table:
+  *** 3.28.4-0ubuntu18.04.3 500
+ 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  3.28.3+git20190124-0ubuntu18.04.2 500
+ 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
+  3.28.1-0ubuntu2 500
+ 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18
  Uname: Linux 4.15.0-76-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 15 06:21:53 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-17 (454 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

** Attachment added: "Screenshot of window on boot"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1863400/+attachment/5328366/+files/Screenshot%20from%202020-02-15%2010-06-14.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/1863400

Title:
  gnome-shell reports problem on boot

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Problem reported at boot but does not seem to collect data and send, just 
does nothing.
  See attached screenshot of window.
  Still able to use laptop.
  This file exists in /var/crash
  -rw-r-  1 gdm  whoopsie 21900809 Feb 14 22:01 
_usr_bin_gnome-shell.121.crash

  The time of this file must have been at last shutdown which did take a
  little longer than usual.

  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  gnome-shell:
    Installed: 3.28.4-0ubuntu18.04.3
    Candidate: 3.28.4-0ubuntu18.04.3
    Version table:
   *** 3.28.4-0ubuntu18.04.3 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.3+git20190124-0ubuntu18.04.2 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   3.28.1-0ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18
  Uname: Linux 4.15.0-76-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 15 06:21:53 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-17 (454 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  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/1863400/+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 1863391] Re: GNOME fractional scaling: fullscreen video misbehaves

[pheidrias]

Hi Dmitry,

my bad - I'm using the default GNOME session! What would be the
corresponding package to file the bug against?

Sorry and thanks,
pheidrias

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

Title:
  GNOME fractional scaling: fullscreen video misbehaves

Status in metacity package in Ubuntu:
  New

Bug description:
  When scaling the desktop to e.g. 150%, fullscreen video does seem to
  trigger constant changes of the scaling factor: the system switches
  every 0.5s from 150% to 100% to 200% or things like those.

  The problem does not occur, when there is another windows present
  (e.g. a "always-on-top" terminal windows).

  Also, KDE doesn't have this problem.

  The problem exists in freshly installed 19.10 and 20.04, too. I couldn't find 
any reason, why sometimes firefox fullscreen videos do work and sometimes not. 
  Video playback (e.g. GNOME video player or VLC) does not work properly in 
19.10, whereas it works most of the time in 20.04.

  How can I help to dig into this?

  1) Ubuntu 19.10, 20.04
  2) latest available (problem exists since several weeks)
  3) What you expected to happen: fullscreen video playback in scaled mode
  4) What happened instead: screen starts changing (randomly?) the scaling 
factor or at least this is the impression one gets

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