date:20190731

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

** Package changed: linux (Ubuntu) => linux-hwe (Ubuntu)

** Tags added: regression-update

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

Title:
  kernel update 5.0.0-23 breaks scroll mouse in xorg

Status in linux-hwe package in Ubuntu:
  New

Bug description:
  Just updated 18.04 to kernel 5.0.0-23 and scrolling with mouse wheel
  does not work or works very slowly. Mouse is Microsoft Wireless
  Optical Mouse 3000 connected via USB to wireless receiver.

  Rebooting system into kernel 4.18.0-25 and everything works correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  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: MATE
  Date: Wed Jul 31 22:53:44 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.18.0-24-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-25-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3]
  InstallationDate: Installed on 2019-04-05 (118 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 2347GBU
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic 
root=UUID=c840a596-f648-4a82-98f4-70137859c633 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/19/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET73WW (2.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2347GBU
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET73WW(2.09):bd10/19/2012:svnLENOVO:pn2347GBU:pvrThinkPadT430:rvnLENOVO:rn2347GBU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2347GBU
  dmi.product.sku: LENOVO_MT_2347
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  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/linux-hwe/+bug/1838601/+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 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox

2019-07-31 Thread Mathew Hodson

** Changed in: ibus (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Ibus causes gnome-shell to freeze when password fields are selected in
  Firefox

Status in ibus package in Ubuntu:
  Confirmed
Status in ibus source package in Bionic:
  In Progress

Bug description:
  [Impact]

  The following has been seen in a VMware Horizon VDI. I cannot reproduce this
  issue myself.

  When a user interacts with any password field in Firefox, gnome-shell
  and Firefox both freeze and the system becomes unusable. If you ssh
  into the system and terminate Firefox, gnome-shell unfreezes.

  This only happens when the environment variable GTK_IM_MODULE is set to 
"ibus". If you unset the variable, or change it to
  GTK_IM_MODULE=gtk-im-context-simple and then start Firefox, everything works 
as intended.

  This has been seen before with gnome-shell 3.28.4-0ubuntu18.04.1, ibus
  1.5.17-3ubuntu4 and Firefox versions starting with 
68.0+build3-0ubuntu0.18.04.1

  Note: Chrome[ium] and other applications do not trigger it, and it cannot be
  reproduced in other desktop environments.

  This seems to be an interaction issue between ibus and gnome-shell.

  [Fix]

  When ibus is built with the patch ibus-xx-f19-password.patch which was
  dropped in ibus-1.5.17-2, the problem is solved.

  Instead of using ibus-xx-f19-password.patch, we will instead fix it with
  upstream commit f328fd67f479faa46ca87bf3c85eed7080ec5ec0:

  https://github.com/ibus/ibus/commit/f328fd67f479faa46ca87bf3c85eed7080ec5ec0

  Subject: client/gtk2: Add IBUS_DISCARD_PASSWORD for firefox and chrome 
  Author: fujiwarat 

  This implements the password discard functionality found in 
  ibus-xx-f19-password.patch and places it behind two environment variables,
  IBUS_DISCARD_PASSWORD and IBUS_DISCARD_PASSWORD_APPS.

  IBUS_DISCARD_PASSWORD is for a single process, and IBUS_DISCARD_PASSWORD_APPS
  lets you set a regex of process names to filter and enable the fix for.

  If IBUS_DISCARD_PASSWORD is set or IBUS_DISCARD_PASSWORD_APPS is set with the
  process name which input is being placed into password fields, ibus will pass
  through the input to the application without any processing.

  [Testcase]

  Launch firefox from within a gnome-session, making sure the
  GTK_IM_MODULE is set to "ibus". Note, this is the default value.

  $ env GTK_IM_MODULE="ibus" firefox

  Navigate to any website which has a password field. Wikipedia or
  Reddit will do.

  Click a password field and attempt to enter text. Firefox and gnome-
  shell both lock up and stay frozen for an extended period of time.

  Now, try it with the fix by enabling:

  $ env IBUS_DISCARD_PASSWORD=1 firefox

  When you enter text into a password field, ibus should directly pass through
  the text and the problem will be solved.

  We can also ask it to always apply for a specific application with:

  $ export IBUS_DISCARD_PASSWORD_APPS="firefox"
  $ firefox 

  Again, when you enter text into a password input field, the problem will be
  solved.

  Test package is available here:

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

  Please test with the revised version,
  1.5.17-3ubuntu4+sf235370v20190731b1.

  [Regression Potential]

  This change has a low risk of regression, because the default behaviour is
  unchanged. To be able to use the password input field discard functionality,
  a user has to explicitly set an environment variable for the specific 
process, or set a regex that matches a process name.

  This means the fix is not enabled by default on any machines, and will
  only be utilised by those suffering problems and go and manually set
  environment variables or have their system administrator enable the
  environment variables permanently.

  This commit is present in upstream ibus from version ibus-1.5.19 onward, and
  is currently present in cosmic, disco and eoan. 

  If a regression occurs, users can ensure that the environment variables are
  unset and continue working.

  [Notes]

  This patch is functionally the same as ibus-xx-f19-password.patch, but just
  hides the features behind environment variables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1838358/+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 1838601] [NEW] kernel update 5.0.0-23 breaks scroll mouse in xorg

2019-07-31 Thread FranksMCB

Public bug reported:

Just updated 18.04 to kernel 5.0.0-23 and scrolling with mouse wheel
does not work or works very slowly. Mouse is Microsoft Wireless Optical
Mouse 3000 connected via USB to wireless receiver.

Rebooting system into kernel 4.18.0-25 and everything works correctly.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
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: MATE
Date: Wed Jul 31 22:53:44 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.18, 4.18.0-24-generic, x86_64: installed
 virtualbox, 5.2.18, 4.18.0-25-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3]
InstallationDate: Installed on 2019-04-05 (118 days ago)
InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
MachineType: LENOVO 2347GBU
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic 
root=UUID=c840a596-f648-4a82-98f4-70137859c633 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/19/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: G1ET73WW (2.09 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2347GBU
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET73WW(2.09):bd10/19/2012:svnLENOVO:pn2347GBU:pvrThinkPadT430:rvnLENOVO:rn2347GBU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T430
dmi.product.name: 2347GBU
dmi.product.sku: LENOVO_MT_2347
dmi.product.version: ThinkPad T430
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
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

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


** Tags: amd64 apport-bug bionic 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/1838601

Title:
  kernel update 5.0.0-23 breaks scroll mouse in xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  Just updated 18.04 to kernel 5.0.0-23 and scrolling with mouse wheel
  does not work or works very slowly. Mouse is Microsoft Wireless
  Optical Mouse 3000 connected via USB to wireless receiver.

  Rebooting system into kernel 4.18.0-25 and everything works correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  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: MATE
  Date: Wed Jul 31 22:53:44 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.18.0-24-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-25-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3]
  InstallationDate: Installed on 2019-04-05 (118 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 2347GBU
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic 
root=UUID=c840a596-f648-4a82-98f4-70137859c633 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade

[Desktop-packages] [Bug 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox

2019-07-31 Thread Matthew Ruffell

Revised debdiff for bionic which enables the environment variables
IBUS_DISCARD_PASSWORD and IBUS_DISCARD_PASSWORD_APPS

** Patch added: "revised debdiff for bionic"

https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1838358/+attachment/5280261/+files/lp1838358_bionic_revised.debdiff

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

Title:
Ibus causes gnome-shell to freeze when password fields are selected in
Firefox

Status in ibus package in Ubuntu:
Confirmed
Status in ibus source package in Bionic:
In Progress

Bug description:
[Impact]

The following has been seen in a VMware Horizon VDI. I cannot reproduce this
issue myself.

When a user interacts with any password field in Firefox, gnome-shell
and Firefox both freeze and the system becomes unusable. If you ssh
into the system and terminate Firefox, gnome-shell unfreezes.

This only happens when the environment variable GTK_IM_MODULE is set to
"ibus". If you unset the variable, or change it to
GTK_IM_MODULE=gtk-im-context-simple and then start Firefox, everything works
as intended.

This has been seen before with gnome-shell 3.28.4-0ubuntu18.04.1, ibus
1.5.17-3ubuntu4 and Firefox versions starting with
68.0+build3-0ubuntu0.18.04.1

Note: Chrome[ium] and other applications do not trigger it, and it cannot be
reproduced in other desktop environments.

This seems to be an interaction issue between ibus and gnome-shell.

[Fix]

When ibus is built with the patch ibus-xx-f19-password.patch which was
dropped in ibus-1.5.17-2, the problem is solved.

Instead of using ibus-xx-f19-password.patch, we will instead fix it with
upstream commit f328fd67f479faa46ca87bf3c85eed7080ec5ec0:

https://github.com/ibus/ibus/commit/f328fd67f479faa46ca87bf3c85eed7080ec5ec0

Subject: client/gtk2: Add IBUS_DISCARD_PASSWORD for firefox and chrome
Author: fujiwarat

This implements the password discard functionality found in
ibus-xx-f19-password.patch and places it behind two environment variables,
IBUS_DISCARD_PASSWORD and IBUS_DISCARD_PASSWORD_APPS.

IBUS_DISCARD_PASSWORD is for a single process, and IBUS_DISCARD_PASSWORD_APPS
lets you set a regex of process names to filter and enable the fix for.

If IBUS_DISCARD_PASSWORD is set or IBUS_DISCARD_PASSWORD_APPS is set with the
process name which input is being placed into password fields, ibus will pass
through the input to the application without any processing.

[Testcase]

Launch firefox from within a gnome-session, making sure the
GTK_IM_MODULE is set to "ibus". Note, this is the default value.

$ env GTK_IM_MODULE="ibus" firefox

Navigate to any website which has a password field. Wikipedia or
Reddit will do.

Click a password field and attempt to enter text. Firefox and gnome-
shell both lock up and stay frozen for an extended period of time.

Now, try it with the fix by enabling:

$ env IBUS_DISCARD_PASSWORD=1 firefox

When you enter text into a password field, ibus should directly pass through
the text and the problem will be solved.

We can also ask it to always apply for a specific application with:

$ export IBUS_DISCARD_PASSWORD_APPS="firefox"
$ firefox

Again, when you enter text into a password input field, the problem will be
solved.

Test package is available here:

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

Please test with the revised version,
1.5.17-3ubuntu4+sf235370v20190731b1.

[Regression Potential]

This change has a low risk of regression, because the default behaviour is
unchanged. To be able to use the password input field discard functionality,
a user has to explicitly set an environment variable for the specific
process, or set a regex that matches a process name.

This means the fix is not enabled by default on any machines, and will
only be utilised by those suffering problems and go and manually set
environment variables or have their system administrator enable the
environment variables permanently.

This commit is present in upstream ibus from version ibus-1.5.19 onward, and
is currently present in cosmic, disco and eoan.

If a regression occurs, users can ensure that the environment variables are
unset and continue working.

[Notes]

This patch is functionally the same as ibus-xx-f19-password.patch, but just
hides the features behind environment variables.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1838358/+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 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox

2019-07-31 Thread Matthew Ruffell

Hi Oliver,

Full details from the environment which has the problem:

Affected machines are all running Bionic and are fully patched.
firefox: 68.0.1+build1-0ubuntu0.18.04.1
gnome-shell: 3.28.4-0ubuntu18.04.1
ibus: 1.5.17-3ubuntu4

Machines are accessed as a VDI through VMware Horizon 7.9.0, and users who have
problems are using Gnome 3.

After discussing this with Eric D, we agreed that it might be a better idea to
not restore the old ibus-xx-f19-password.patch and instead go with the upstream
solution of 
https://github.com/ibus/ibus/commit/f328fd67f479faa46ca87bf3c85eed7080ec5ec0
which implements the same functionality, but hides it behind two environment
variables, IBUS_DISCARD_PASSWORD and IBUS_DISCARD_PASSWORD_APPS.

To be honest, I think this approach is better since it doesn't change any
default behaviour and the fix is opt in for environments which need it. Plus
this is present in cosmic, disco and eoan, and will be available in the future 
20.04 LTS.

I have tried my best to reproduce this, but I have not had any luck. I think
this solution is probably the best for all parties, and this has been tested
successfully in the affected environment, so I have made a new debdiff with the
above patch.

I would like to determine and fix the root cause, but that might be a little
challenging, and this is a sufficient workaround.

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

Title:
  Ibus causes gnome-shell to freeze when password fields are selected in
  Firefox

Status in ibus package in Ubuntu:
  Confirmed
Status in ibus source package in Bionic:
  In Progress

Bug description:
  [Impact]

  The following has been seen in a VMware Horizon VDI. I cannot reproduce this
  issue myself.

  When a user interacts with any password field in Firefox, gnome-shell
  and Firefox both freeze and the system becomes unusable. If you ssh
  into the system and terminate Firefox, gnome-shell unfreezes.

  This only happens when the environment variable GTK_IM_MODULE is set to 
"ibus". If you unset the variable, or change it to
  GTK_IM_MODULE=gtk-im-context-simple and then start Firefox, everything works 
as intended.

  This has been seen before with gnome-shell 3.28.4-0ubuntu18.04.1, ibus
  1.5.17-3ubuntu4 and Firefox versions starting with 
68.0+build3-0ubuntu0.18.04.1

  Note: Chrome[ium] and other applications do not trigger it, and it cannot be
  reproduced in other desktop environments.

  This seems to be an interaction issue between ibus and gnome-shell.

  [Fix]

  When ibus is built with the patch ibus-xx-f19-password.patch which was
  dropped in ibus-1.5.17-2, the problem is solved.

  Instead of using ibus-xx-f19-password.patch, we will instead fix it with
  upstream commit f328fd67f479faa46ca87bf3c85eed7080ec5ec0:

  https://github.com/ibus/ibus/commit/f328fd67f479faa46ca87bf3c85eed7080ec5ec0

  Subject: client/gtk2: Add IBUS_DISCARD_PASSWORD for firefox and chrome 
  Author: fujiwarat 

  This implements the password discard functionality found in 
  ibus-xx-f19-password.patch and places it behind two environment variables,
  IBUS_DISCARD_PASSWORD and IBUS_DISCARD_PASSWORD_APPS.

  IBUS_DISCARD_PASSWORD is for a single process, and IBUS_DISCARD_PASSWORD_APPS
  lets you set a regex of process names to filter and enable the fix for.

  If IBUS_DISCARD_PASSWORD is set or IBUS_DISCARD_PASSWORD_APPS is set with the
  process name which input is being placed into password fields, ibus will pass
  through the input to the application without any processing.

  [Testcase]

  Launch firefox from within a gnome-session, making sure the
  GTK_IM_MODULE is set to "ibus". Note, this is the default value.

  $ env GTK_IM_MODULE="ibus" firefox

  Navigate to any website which has a password field. Wikipedia or
  Reddit will do.

  Click a password field and attempt to enter text. Firefox and gnome-
  shell both lock up and stay frozen for an extended period of time.

  Now, try it with the fix by enabling:

  $ env IBUS_DISCARD_PASSWORD=1 firefox

  When you enter text into a password field, ibus should directly pass through
  the text and the problem will be solved.

  We can also ask it to always apply for a specific application with:

  $ export IBUS_DISCARD_PASSWORD_APPS="firefox"
  $ firefox 

  Again, when you enter text into a password input field, the problem will be
  solved.

  Test package is available here:

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

  Please test with the revised version,
  1.5.17-3ubuntu4+sf235370v20190731b1.

  [Regression Potential]

  This change has a low risk of regression, because the default behaviour is
  unchanged. To be able to use the password input field discard functionality,
  a user has to explicitly set an environment variable for the specific 
process, or set a regex that matches a process name.

  This means the fix is not enabled

[Desktop-packages] [Bug 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox

2019-07-31 Thread Matthew Ruffell

** Description changed:

  [Impact]
  
  The following has been seen in a VMware Horizon VDI. I cannot reproduce this
  issue myself.
  
  When a user interacts with any password field in Firefox, gnome-shell
  and Firefox both freeze and the system becomes unusable. If you ssh into
  the system and terminate Firefox, gnome-shell unfreezes.
  
- This only happens when the environment variable GTK_IM_MODULE is set to 
"ibus". If you unset the variable, or change it to 
+ This only happens when the environment variable GTK_IM_MODULE is set to 
"ibus". If you unset the variable, or change it to
  GTK_IM_MODULE=gtk-im-context-simple and then start Firefox, everything works 
as intended.
  
  This has been seen before with gnome-shell 3.28.4-0ubuntu18.04.1, ibus
  1.5.17-3ubuntu4 and Firefox versions starting with 
68.0+build3-0ubuntu0.18.04.1
  
  Note: Chrome[ium] and other applications do not trigger it, and it cannot be
  reproduced in other desktop environments.
  
  This seems to be an interaction issue between ibus and gnome-shell.
  
  [Fix]
  
  When ibus is built with the patch ibus-xx-f19-password.patch which was
  dropped in ibus-1.5.17-2, the problem is solved.
  
- ibus-xx-f19-password.patch checks to see if the GTK version is at or
- above 3.6, and if it is, checks to see if the input purpose is for a
- password field. If it is, then no further action is taken by ibus.
+ Instead of using ibus-xx-f19-password.patch, we will instead fix it with
+ upstream commit f328fd67f479faa46ca87bf3c85eed7080ec5ec0:
+ 
+ https://github.com/ibus/ibus/commit/f328fd67f479faa46ca87bf3c85eed7080ec5ec0
+ 
+ Subject: client/gtk2: Add IBUS_DISCARD_PASSWORD for firefox and chrome 
+ Author: fujiwarat 
+ 
+ This implements the password discard functionality found in 
+ ibus-xx-f19-password.patch and places it behind two environment variables,
+ IBUS_DISCARD_PASSWORD and IBUS_DISCARD_PASSWORD_APPS.
+ 
+ IBUS_DISCARD_PASSWORD is for a single process, and IBUS_DISCARD_PASSWORD_APPS
+ lets you set a regex of process names to filter and enable the fix for.
+ 
+ If IBUS_DISCARD_PASSWORD is set or IBUS_DISCARD_PASSWORD_APPS is set with the
+ process name which input is being placed into password fields, ibus will pass
+ through the input to the application without any processing.
  
  [Testcase]
  
  Launch firefox from within a gnome-session, making sure the
  GTK_IM_MODULE is set to "ibus". Note, this is the default value.
  
  $ env GTK_IM_MODULE="ibus" firefox
  
  Navigate to any website which has a password field. Wikipedia or Reddit
  will do.
  
  Click a password field and attempt to enter text. Firefox and gnome-
  shell both lock up and stay frozen for an extended period of time.
  
- With the test package which includes ibus-xx-f19-password.patch, gnome-shell
- and Firefox do not lock up and everything works as intended.
+ Now, try it with the fix by enabling:
+ 
+ $ env IBUS_DISCARD_PASSWORD=1 firefox
+ 
+ When you enter text into a password field, ibus should directly pass through
+ the text and the problem will be solved.
+ 
+ We can also ask it to always apply for a specific application with:
+ 
+ $ export IBUS_DISCARD_PASSWORD_APPS="firefox"
+ $ firefox 
+ 
+ Again, when you enter text into a password input field, the problem will be
+ solved.
  
  Test package is available here:
  
  https://launchpad.net/~mruffell/+archive/ubuntu/sf235370-test
  
+ Please test with the revised version,
+ 1.5.17-3ubuntu4+sf235370v20190731b1.
+ 
  [Regression Potential]
  
- This has a low to medium risk of regression, and is limited to inputs to
- password fields in all applications, including the gnome-shell lock screen.
+ This change has a low risk of regression, because the default behaviour is
+ unchanged. To be able to use the password input field discard functionality,
+ a user has to explicitly set an environment variable for the specific 
process, or set a regex that matches a process name.
  
- This patch has been extensively tested and it is present in the
- following Ubuntu releases:
+ This means the fix is not enabled by default on any machines, and will
+ only be utilised by those suffering problems and go and manually set
+ environment variables or have their system administrator enable the
+ environment variables permanently.
  
- artful: 1.5.14-2ubuntu1
- zesty: 1.5.14-2ubuntu1
- yakkety: 1.5.11-1ubuntu3
- xenial: 1.5.11-1ubuntu2
- wily: 1.5.10-1ubuntu1
- vivid: 1.5.9-1ubuntu3
- utopic: 1.5.8-2ubuntu2
- trusty: 1.5.5-1ubuntu3.2
+ This commit is present in upstream ibus from version ibus-1.5.19 onward, and
+ is currently present in cosmic, disco and eoan. 
  
- The patch was introduced in trusty, and removed in bionic. I feel that the 
risk of reintroducing the patch is low, since the use case of the software is 
the same as previous releases in regards to input software and input language
- selection.
- 
- I still acknowledge a potential risk of regression when users change their
- input engines to non

[Desktop-packages] [Bug 1838599] [NEW] alsa/sof: need to update the firmware of sound sof driver

2019-07-31 Thread Hui Wang

Public bug reported:

This bug is for tracking purpose.

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Assignee: Hui Wang (hui.wang)
 Status: New


** Tags: originate-from-1837853 somerville

** Package changed: pulseaudio (Ubuntu) => linux-firmware (Ubuntu)

** Tags added: originate-from-1837853 somerville

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

Title:
  alsa/sof: need to update the firmware of sound sof driver

Status in HWE Next:
  New
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  This bug is for tracking purpose.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1838599/+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 1837834] Re: Add support for Linux 5.0-5.2

2019-07-31 Thread Doug Brown

I installed the new proposed 340.107-0ubuntu0.18.04.3 version, and now
nvidia-340 properly builds and works for me on kernel 5.0.0 in Ubuntu
18.04. Thanks!

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

Title:
  Add support for Linux 5.0-5.2

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Bionic:
  Fix Committed

Bug description:
  Backport the compatibility patches available in 19.10.

  SRU Request:

  [Impact]
  Linux 5.0 is not supported by nvidia-driver-340 in bionic.

  [Test Case]
  1) Enable the -proposed repository, and install the new 340 NVIDIA driver 
(340.107-0ubuntu0.16.04.3).

  2) Check that the kernel module can be built against the new kernel.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low. The update only fixes build issues with Linux versions 5.0 - 5.2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1837834/+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 1838577] Re: Default audio device changes on reboot; audio still outputs using my previously-selected device

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Medium

** Changed in: pulseaudio (Ubuntu)
   Status: New => Triaged

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

Title:
  Default audio device changes on reboot; audio still outputs using my
  previously-selected device

Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  This is present in Ubuntu 18.04, 18.10, 19.04, and 19.10 daily build.
  It was not present in Ubuntu 16.04.

  I have a USB microphone which also appears to pulse as a speaker.
  Pulse keeps picking it as the default audio device. I can switch audio
  devices to my analog line out, which works as expected until I reboot.

  After reboot, my audio device switches back to the USB "speaker", and
  Gnome shell / Gnome settings volume control adjusts the USB speaker
  volume. Despite  seeing the USB device as the current output device, I
  still hear sound from my line-out.

  In the interest of narrowing down this bug, I have found that
  disabling "module-switch-on-connect" fixes the problem (my line-out
  stays as the default audio device and I hear sound).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 31 17:39:38 2019
  InstallationDate: Installed on 2019-07-31 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4207
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B350M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4207:bd12/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1838577/+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 1838577] [NEW] Default audio device changes on reboot; audio still outputs using my previously-selected device

2019-07-31 Thread Ben

Public bug reported:

This is present in Ubuntu 18.04, 18.10, 19.04, and 19.10 daily build. It
was not present in Ubuntu 16.04.

I have a USB microphone which also appears to pulse as a speaker. Pulse
keeps picking it as the default audio device. I can switch audio devices
to my analog line out, which works as expected until I reboot.

After reboot, my audio device switches back to the USB "speaker", and
Gnome shell / Gnome settings volume control adjusts the USB speaker
volume. Despite  seeing the USB device as the current output device, I
still hear sound from my line-out.

In the interest of narrowing down this bug, I have found that disabling
"module-switch-on-connect" fixes the problem (my line-out stays as the
default audio device and I hear sound).

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: pulseaudio 1:12.2-2ubuntu3
ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
Uname: Linux 5.0.0-21-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 31 17:39:38 2019
InstallationDate: Installed on 2019-07-31 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/07/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4207
dmi.board.asset.tag: Default string
dmi.board.name: PRIME B350M-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4207:bd12/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug bionic cosmic disco eoan

** Description changed:

  This is present in Ubuntu 18.04, 18.10, 19.04, and 19.10 daily build. It
  was not present in Ubuntu 16.04.
  
  I have a USB microphone which also appears to pulse as a speaker. Pulse
  keeps picking it as the default audio device. I can switch audio devices
  to my analog line out, which works as expected until I reboot.
  
  After reboot, my audio device switches back to the USB "speaker", and
- volume control adjusts the USB speaker volume. Despite pulse seeing the
- USB device as the current output device, I still hear sound from my
- line-out.
+ Gnome shell / Gnome settings volume control adjusts the USB speaker
+ volume. Despite  seeing the USB device as the current output device, I
+ still hear sound from my line-out.
  
  In the interest of narrowing down this bug, I have found that disabling
  "module-switch-on-connect" fixes the problem (my line-out stays as the
  default audio device and I hear sound).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15
  Uname: Linux 5.0.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 31 17:39:38 2019
  InstallationDate: Installed on 2019-07-31 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4207
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B350M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4207:bd12/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

Title:
  Default audio device changes on reboot; audio still outputs

[Desktop-packages] [Bug 1330232] Re: remmina opens then closes immesiately. Trying to connect win win 8 server. Has been working fine until 3 days ago. same problem on 2 seperate machines

2019-07-31 Thread Zachary J. Fields

I experienced similar behavior. It turned out to be the color depth was
8bpp, instead of 16bpp. There was no error message indicating this, I
only discovered it after a web search and a couple hours of frustration.

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

Title:
  remmina opens then closes immesiately. Trying to connect win win 8
  server. Has been working fine until 3 days ago. same problem on 2
  seperate machines

Status in remmina package in Ubuntu:
  Invalid

Bug description:
  source package the bug is in : /usr/bin/remmina
  1 : Ubuntu 12.04
  2 : remmina-common 1.0.0-1ubuntu6.3
  3 : I expected to log into a remote desktop environment hosted on a Win8 
Server using RDP
  4 : It opens briefely then closes or freezes. Only when the security setting 
is set to "Negotiate" or "NLA" will I get that far. Using "RDP" or "TLA" I just 
get a window saying "Unable to connect to RDP server"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1330232/+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 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox

Thanks for the report Matthew. I appreciate all the work to prepare a
SRU bug and a debdiff, but the very first step would be to reliably
reproduce the issue. As far as I can tell this hasn't been reported by
anyone else, which makes it likely to be an isolated issue on a very
specific setup, and thus not necessarily a good candidate for a SRU. Can
you get the person who reported the issue to provide more details on
their setup (is it stock Ubuntu or a derivative, is it fully up-to-date,
which desktop environment, what are the exact versions of gnome-shell,
firefox and ibus). Thanks!

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

Title:
  Ibus causes gnome-shell to freeze when password fields are selected in
  Firefox

Status in ibus package in Ubuntu:
  Confirmed
Status in ibus source package in Bionic:
  In Progress

Bug description:
  [Impact]

  The following has been seen in a VMware Horizon VDI. I cannot reproduce this
  issue myself.

  When a user interacts with any password field in Firefox, gnome-shell
  and Firefox both freeze and the system becomes unusable. If you ssh
  into the system and terminate Firefox, gnome-shell unfreezes.

  This only happens when the environment variable GTK_IM_MODULE is set to 
"ibus". If you unset the variable, or change it to 
  GTK_IM_MODULE=gtk-im-context-simple and then start Firefox, everything works 
as intended.

  This has been seen before with gnome-shell 3.28.4-0ubuntu18.04.1, ibus
  1.5.17-3ubuntu4 and Firefox versions starting with 
68.0+build3-0ubuntu0.18.04.1

  Note: Chrome[ium] and other applications do not trigger it, and it cannot be
  reproduced in other desktop environments.

  This seems to be an interaction issue between ibus and gnome-shell.

  [Fix]

  When ibus is built with the patch ibus-xx-f19-password.patch which was
  dropped in ibus-1.5.17-2, the problem is solved.

  ibus-xx-f19-password.patch checks to see if the GTK version is at or
  above 3.6, and if it is, checks to see if the input purpose is for a
  password field. If it is, then no further action is taken by ibus.

  [Testcase]

  Launch firefox from within a gnome-session, making sure the
  GTK_IM_MODULE is set to "ibus". Note, this is the default value.

  $ env GTK_IM_MODULE="ibus" firefox

  Navigate to any website which has a password field. Wikipedia or
  Reddit will do.

  Click a password field and attempt to enter text. Firefox and gnome-
  shell both lock up and stay frozen for an extended period of time.

  With the test package which includes ibus-xx-f19-password.patch, gnome-shell
  and Firefox do not lock up and everything works as intended.

  Test package is available here:

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

  [Regression Potential]

  This has a low to medium risk of regression, and is limited to inputs to
  password fields in all applications, including the gnome-shell lock screen.

  This patch has been extensively tested and it is present in the
  following Ubuntu releases:

  artful: 1.5.14-2ubuntu1
  zesty: 1.5.14-2ubuntu1
  yakkety: 1.5.11-1ubuntu3
  xenial: 1.5.11-1ubuntu2
  wily: 1.5.10-1ubuntu1
  vivid: 1.5.9-1ubuntu3
  utopic: 1.5.8-2ubuntu2
  trusty: 1.5.5-1ubuntu3.2

  The patch was introduced in trusty, and removed in bionic. I feel that the 
risk of reintroducing the patch is low, since the use case of the software is 
the same as previous releases in regards to input software and input language
  selection.

  I still acknowledge a potential risk of regression when users change their
  input engines to non defaults and pair it with non default input languages.

  In the event of regression ibus can be temporarily be disabled via an
  environment variable and the patch dropped in any subsequent packages.

  [Notes]

  This patch will not be needed in newer versions of ibus as an official
  workaround has been implemented as of ibus-1.5.19.

  https://github.com/ibus/ibus/commit/f328fd67f479faa46ca87bf3c85eed7080ec5ec0

  If problems arise with password input fields in ibus versions 1.5.19
  or later, which are found in cosmic onward, environment variables can
  be set that have the same effect as ibus-xx-f19-password.patch.

  env IBUS_DISCARD_PASSWORD=1 firefox
  or
  export IBUS_DISCARD_PASSWORD_APPS='firefox,.*chrome.*'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1838358/+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 1827953] Re: when you have "world clocks" configured (e.g. from the Gnome Clocks application), Gnome Shell crashes on login, resulting in a login loop

This bug was fixed in the package gnome-shell -
3.32.2-2ubuntu1~ubuntu19.04.1

---
gnome-shell (3.32.2-2ubuntu1~ubuntu19.04.1) disco; urgency=medium

  * No-change SRU backport from eoan to disco. (LP: #1834517)

gnome-shell (3.32.2-2ubuntu1) eoan; urgency=medium

  * Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
  - ubuntu-session (| gnome-session) to have the ubuntu session available
  - xserver-xorg-legacy
  - yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
  - add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
  - quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
  - Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
  - Respect Ubuntu's lock-on-suspend setting.
+ ubuntu/gdm.patch
  - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu
styling by default, not impacting the gnome user session though.
+ ubuntu/background_login.patch
  - Change default background color as we modified the default GDM color
for our ubuntu session. Change it as well here, still applying the
background noise loading.
+ ubuntu/gdm_alternatives.patch
  - Add support for GDM3 theme alternatives
+ ubuntu/block_mode_extension_update.patch
  - Don't allow ubuntu mode extension to update
+ optional-hot-corner.patch
  - enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
+ volume-Add-back-sound-feedback-on-scroll.patch
  - Fix regression causing missing feedback on volume slider scroll
+ main-show-an-error-message-on-gnome-shell-crash.patch,
  global-make-possible-to-set-debug-flags-dynamically.patch,
  main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
  main-add-backtrace-crashes-all-and-backtrace-all.patch,
  sessionMode-add-support-for-debugFlags-parameter.patch:
  - Improve debug JS tracing for crash reports
+ st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch,
  st-scroll-view-Remove-scrollbars-references-on-dispose.patch:
  - Fix crash on theme changes
+ ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
  - stop searches when requested from UI
+ magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
  - Show monitor scaled cursor when magnifier is enabled

gnome-shell (3.32.2-2) experimental; urgency=medium

  * debian/source_gnome-shell.py:
+ Add more informations that we might need to debug information in the
  apport retracing (LP: #1722886):
  - All the desktop shared gsettings key
  - Mutter gsettings key and version
  - Settings daemon settings key used by the shell
  - ~/.config/monitors.xml
  - Shell's journalctl since it will include errors and JS stacktrace.
  * d/p/boxpointer-Unset-the-sourceActor-on-destruction.patch:
- Avoid crash on reallocation of dead actors (LP: #1831555)

gnome-shell (3.32.2-1ubuntu1) eoan; urgency=medium

  * Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
  - ubuntu-session (| gnome-session) to have the ubuntu session available
  - xserver-xorg-legacy
  - yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
  - add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
  - quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
  - Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
  -

[Desktop-packages] [Bug 1831555] Re: gnome-shell crashed with SIGTRAP in gjs_callback_closure() from ffi_closure_unix64_inner() from ffi_closure_unix64() from clutter_actor_allocate_internal() from cl

This bug was fixed in the package gnome-shell -
3.32.2-2ubuntu1~ubuntu19.04.1

---
gnome-shell (3.32.2-2ubuntu1~ubuntu19.04.1) disco; urgency=medium

  * No-change SRU backport from eoan to disco. (LP: #1834517)

gnome-shell (3.32.2-2ubuntu1) eoan; urgency=medium

  * Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
  - ubuntu-session (| gnome-session) to have the ubuntu session available
  - xserver-xorg-legacy
  - yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
  - add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
  - quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
  - Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
  - Respect Ubuntu's lock-on-suspend setting.
+ ubuntu/gdm.patch
  - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu
styling by default, not impacting the gnome user session though.
+ ubuntu/background_login.patch
  - Change default background color as we modified the default GDM color
for our ubuntu session. Change it as well here, still applying the
background noise loading.
+ ubuntu/gdm_alternatives.patch
  - Add support for GDM3 theme alternatives
+ ubuntu/block_mode_extension_update.patch
  - Don't allow ubuntu mode extension to update
+ optional-hot-corner.patch
  - enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
+ volume-Add-back-sound-feedback-on-scroll.patch
  - Fix regression causing missing feedback on volume slider scroll
+ main-show-an-error-message-on-gnome-shell-crash.patch,
  global-make-possible-to-set-debug-flags-dynamically.patch,
  main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
  main-add-backtrace-crashes-all-and-backtrace-all.patch,
  sessionMode-add-support-for-debugFlags-parameter.patch:
  - Improve debug JS tracing for crash reports
+ st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch,
  st-scroll-view-Remove-scrollbars-references-on-dispose.patch:
  - Fix crash on theme changes
+ ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
  - stop searches when requested from UI
+ magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
  - Show monitor scaled cursor when magnifier is enabled

gnome-shell (3.32.2-2) experimental; urgency=medium

  * debian/source_gnome-shell.py:
+ Add more informations that we might need to debug information in the
  apport retracing (LP: #1722886):
  - All the desktop shared gsettings key
  - Mutter gsettings key and version
  - Settings daemon settings key used by the shell
  - ~/.config/monitors.xml
  - Shell's journalctl since it will include errors and JS stacktrace.
  * d/p/boxpointer-Unset-the-sourceActor-on-destruction.patch:
- Avoid crash on reallocation of dead actors (LP: #1831555)

gnome-shell (3.32.2-1ubuntu1) eoan; urgency=medium

  * Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
  - ubuntu-session (| gnome-session) to have the ubuntu session available
  - xserver-xorg-legacy
  - yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
  - add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
  - quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
  - Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
  -

[Desktop-packages] [Bug 1809788] Re: Shell dialog messages are truncated and ellipsized...

This bug was fixed in the package gnome-shell -
3.32.2-2ubuntu1~ubuntu19.04.1

---
gnome-shell (3.32.2-2ubuntu1~ubuntu19.04.1) disco; urgency=medium

  * No-change SRU backport from eoan to disco. (LP: #1834517)

gnome-shell (3.32.2-2ubuntu1) eoan; urgency=medium

  * Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
  - ubuntu-session (| gnome-session) to have the ubuntu session available
  - xserver-xorg-legacy
  - yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
  - add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
  - quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
  - Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
  - Respect Ubuntu's lock-on-suspend setting.
+ ubuntu/gdm.patch
  - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu
styling by default, not impacting the gnome user session though.
+ ubuntu/background_login.patch
  - Change default background color as we modified the default GDM color
for our ubuntu session. Change it as well here, still applying the
background noise loading.
+ ubuntu/gdm_alternatives.patch
  - Add support for GDM3 theme alternatives
+ ubuntu/block_mode_extension_update.patch
  - Don't allow ubuntu mode extension to update
+ optional-hot-corner.patch
  - enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
+ volume-Add-back-sound-feedback-on-scroll.patch
  - Fix regression causing missing feedback on volume slider scroll
+ main-show-an-error-message-on-gnome-shell-crash.patch,
  global-make-possible-to-set-debug-flags-dynamically.patch,
  main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
  main-add-backtrace-crashes-all-and-backtrace-all.patch,
  sessionMode-add-support-for-debugFlags-parameter.patch:
  - Improve debug JS tracing for crash reports
+ st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch,
  st-scroll-view-Remove-scrollbars-references-on-dispose.patch:
  - Fix crash on theme changes
+ ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
  - stop searches when requested from UI
+ magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
  - Show monitor scaled cursor when magnifier is enabled

gnome-shell (3.32.2-2) experimental; urgency=medium

  * debian/source_gnome-shell.py:
+ Add more informations that we might need to debug information in the
  apport retracing (LP: #1722886):
  - All the desktop shared gsettings key
  - Mutter gsettings key and version
  - Settings daemon settings key used by the shell
  - ~/.config/monitors.xml
  - Shell's journalctl since it will include errors and JS stacktrace.
  * d/p/boxpointer-Unset-the-sourceActor-on-destruction.patch:
- Avoid crash on reallocation of dead actors (LP: #1831555)

gnome-shell (3.32.2-1ubuntu1) eoan; urgency=medium

  * Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
  - ubuntu-session (| gnome-session) to have the ubuntu session available
  - xserver-xorg-legacy
  - yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
  - add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
  - quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
  - Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
  -

[Desktop-packages] [Bug 1722886] Re: Include logs, monitors.xml and org.gnome.desktop.* settings in the apport-retrace data

This bug was fixed in the package gnome-shell -
3.32.2-2ubuntu1~ubuntu19.04.1

---
gnome-shell (3.32.2-2ubuntu1~ubuntu19.04.1) disco; urgency=medium

  * No-change SRU backport from eoan to disco. (LP: #1834517)

gnome-shell (3.32.2-2ubuntu1) eoan; urgency=medium

  * Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
  - ubuntu-session (| gnome-session) to have the ubuntu session available
  - xserver-xorg-legacy
  - yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
  - add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
  - quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
  - Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
  - Respect Ubuntu's lock-on-suspend setting.
+ ubuntu/gdm.patch
  - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu
styling by default, not impacting the gnome user session though.
+ ubuntu/background_login.patch
  - Change default background color as we modified the default GDM color
for our ubuntu session. Change it as well here, still applying the
background noise loading.
+ ubuntu/gdm_alternatives.patch
  - Add support for GDM3 theme alternatives
+ ubuntu/block_mode_extension_update.patch
  - Don't allow ubuntu mode extension to update
+ optional-hot-corner.patch
  - enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
+ volume-Add-back-sound-feedback-on-scroll.patch
  - Fix regression causing missing feedback on volume slider scroll
+ main-show-an-error-message-on-gnome-shell-crash.patch,
  global-make-possible-to-set-debug-flags-dynamically.patch,
  main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
  main-add-backtrace-crashes-all-and-backtrace-all.patch,
  sessionMode-add-support-for-debugFlags-parameter.patch:
  - Improve debug JS tracing for crash reports
+ st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch,
  st-scroll-view-Remove-scrollbars-references-on-dispose.patch:
  - Fix crash on theme changes
+ ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
  - stop searches when requested from UI
+ magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
  - Show monitor scaled cursor when magnifier is enabled

gnome-shell (3.32.2-2) experimental; urgency=medium

  * debian/source_gnome-shell.py:
+ Add more informations that we might need to debug information in the
  apport retracing (LP: #1722886):
  - All the desktop shared gsettings key
  - Mutter gsettings key and version
  - Settings daemon settings key used by the shell
  - ~/.config/monitors.xml
  - Shell's journalctl since it will include errors and JS stacktrace.
  * d/p/boxpointer-Unset-the-sourceActor-on-destruction.patch:
- Avoid crash on reallocation of dead actors (LP: #1831555)

gnome-shell (3.32.2-1ubuntu1) eoan; urgency=medium

  * Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
  - ubuntu-session (| gnome-session) to have the ubuntu session available
  - xserver-xorg-legacy
  - yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
  - add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
  - quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
  - Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
  -

[Desktop-packages] [Bug 1834517] Re: Update gnome-shell to 3.32.2

This bug was fixed in the package gnome-shell -
3.32.2-2ubuntu1~ubuntu19.04.1

---
gnome-shell (3.32.2-2ubuntu1~ubuntu19.04.1) disco; urgency=medium

  * No-change SRU backport from eoan to disco. (LP: #1834517)

gnome-shell (3.32.2-2ubuntu1) eoan; urgency=medium

  * Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
  - ubuntu-session (| gnome-session) to have the ubuntu session available
  - xserver-xorg-legacy
  - yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
  - add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
  - quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
  - Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
  - Respect Ubuntu's lock-on-suspend setting.
+ ubuntu/gdm.patch
  - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu
styling by default, not impacting the gnome user session though.
+ ubuntu/background_login.patch
  - Change default background color as we modified the default GDM color
for our ubuntu session. Change it as well here, still applying the
background noise loading.
+ ubuntu/gdm_alternatives.patch
  - Add support for GDM3 theme alternatives
+ ubuntu/block_mode_extension_update.patch
  - Don't allow ubuntu mode extension to update
+ optional-hot-corner.patch
  - enable patch proposed by upstream developer already in package (but
not in series) to add a settings for optional hot corner activation.
+ volume-Add-back-sound-feedback-on-scroll.patch
  - Fix regression causing missing feedback on volume slider scroll
+ main-show-an-error-message-on-gnome-shell-crash.patch,
  global-make-possible-to-set-debug-flags-dynamically.patch,
  main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch,
  main-add-backtrace-crashes-all-and-backtrace-all.patch,
  sessionMode-add-support-for-debugFlags-parameter.patch:
  - Improve debug JS tracing for crash reports
+ st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch,
  st-scroll-view-Remove-scrollbars-references-on-dispose.patch:
  - Fix crash on theme changes
+ ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch:
  - stop searches when requested from UI
+ magnifier-Show-cursor-when-magnifier-is-enabled-and-scale.patch:
  - Show monitor scaled cursor when magnifier is enabled

gnome-shell (3.32.2-2) experimental; urgency=medium

  * debian/source_gnome-shell.py:
+ Add more informations that we might need to debug information in the
  apport retracing (LP: #1722886):
  - All the desktop shared gsettings key
  - Mutter gsettings key and version
  - Settings daemon settings key used by the shell
  - ~/.config/monitors.xml
  - Shell's journalctl since it will include errors and JS stacktrace.
  * d/p/boxpointer-Unset-the-sourceActor-on-destruction.patch:
- Avoid crash on reallocation of dead actors (LP: #1831555)

gnome-shell (3.32.2-1ubuntu1) eoan; urgency=medium

  * Merge with Debian. Remaining changes:
+ Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests
  gnome-themes-standard-data, gnome-backgrounds
+ Add some Recommends:
  - ubuntu-session (| gnome-session) to have the ubuntu session available
  - xserver-xorg-legacy
  - yaru-theme-gnome-shell for the default ubuntu theming
+ Update debian/gbp.conf with Ubuntu settings
+ gnome-shell-common.install: Install Ubuntu mode
+ gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative
+ ubuntu/desktop_detect.patch:
  - add caching for desktop detection to avoid querying the current
desktop env variable as iterate through the list each time. For the
time of the Shell process, we can expect this env variable to stay
stable.
+ ubuntu/smarter_alt_tab.patch:
  - quick alt-tab (without showing up the switcher) switch only between
the last window of the last 2 applications to be focused instead of
raising all windows of those apps.
+ ubuntu/lightdm-user-switching.patch:
  - Allow user switching when using LightDM.
+ ubuntu/lock_on_suspend.patch
  -

[Desktop-packages] [Bug 1834517] Update Released

The verification of the Stable Release Update for gnome-shell has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Update gnome-shell to 3.32.2

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Disco:
  Fix Committed

Bug description:
  [ Description ]

  The second stable release in the 3.32 series.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Mostly crash fixes, possibly regression in the menus popping ups,
  images textures aspect ratio, Network interface names, world-clocks in
  calendar, dialog texts, widgets style change

  [ Related bugs ]

  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722886
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1834517
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1831555
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827953
  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809788

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1834517/+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 1722886] Update Released

The verification of the Stable Release Update for gnome-shell has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Include logs, monitors.xml and org.gnome.desktop.* settings in the
  apport-retrace data

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Disco:
  Fix Committed

Bug description:
  [ Description ]

  When the shell crashes missing relevant shell data is not attached.

  [ Test case ]

  Run:
   $ ubuntu-bug --save=/tmp/shell-apport-data gnome-shell
   
  It should return non-empty strings such as:

  grep "monitors\.xml:\|ShellJournal:\|RelatedPackageVersions:" 
/tmp/shell-apport-data  -2
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2-0ubuntu1
  ShellJournal:
   -- Logs begin at Fri 2018-11-16 19:45:37 CET, end at Fri 2019-06-28 13:46:01 
CEST. --
   [306535.951329] tricky gnome-shell[13215]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.2886/org/ayatana/NotificationItem/software_update_available
  --
  UpgradeStatus: Upgraded to disco on 2019-06-20 (8 days ago)
  _MarkForUpload: True
  monitors.xml:
   
 

  
  While monitors.xml: stuff is optional (depending on the presence of the 
file), the other fields should always be there.

  
  [ Regression potential ]

  Nothing know, it won't in anyway affect the shell behavior

  
  ---

  
  When a bug is submitted to ubuntu about gnome-shell it would be convenient to 
have such settings.

  Monitors.xml is quite important to understand the configuration for
  mutter-related crashes, while other desktop settings (to be filtered-
  out) could be needed too.

  Ah, also the logs from
    journalctl /usr/bin/gnome-shell -b -o short-iso

  Proposed fix at https://salsa.debian.org/gnome-team/gnome-
  shell/merge_requests/23/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722886/+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 1831555] Update Released

The verification of the Stable Release Update for gnome-shell has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  gnome-shell crashed with SIGTRAP in gjs_callback_closure() from
  ffi_closure_unix64_inner() from ffi_closure_unix64() from
  clutter_actor_allocate_internal() from clutter_actor_allocate()

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

Bug description:
  [ Description ]

  Shell crashes on clutter_actor_allocate(_internal)

  [ Test case ]

  No clear way to reproduce this, it needs to open pop-up menus although
  we consider fixed monitoring the presence of automatic reports at:

  https://errors.ubuntu.com/problem/7a0ffc1caa388737d61043fd4a0ee45677b63d71
  https://errors.ubuntu.com/problem/66c2476d86f4d697ff373f99f20c6134c6b5fab3

  
  [ Regression potential ]

  A menu might be badly allocated (positioned).

  ---

  This is a regression for GNOME Shell / mutter 3.32.1.

  Tracking upstream at https://gitlab.gnome.org/GNOME/gnome-
  shell/issues/1295

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

  Similar stacktrace at
  https://errors.ubuntu.com/problem/66c2476d86f4d697ff373f99f20c6134c6b5fab3

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1831555/+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 1827953] Update Released

The verification of the Stable Release Update for gnome-shell has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  when you have "world clocks" configured (e.g. from the Gnome Clocks
  application), Gnome Shell crashes on login, resulting in a login loop

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Disco:
  Won't Fix

Bug description:
  [ Description ]

  Gnome Shell crashes just after login, creating a “login loop” where
  the user is locked out of their computer.

  [ Test case ]

  Configure some “world clocks” in Gnome Clocks (or maybe using some
  other tool).

  Expected behaviour (how it worked in cosmic & before): Gnome Shell
  shows the time for the cities you configured when you click on the
  date at the top centre.

  [ Regression potential ]

  World clocks are not shown for some places

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1827953/+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 1838038] Re: [snap] Chromium does not work with .local mdns/avahi name resolution

I just checked and neither nscd nor unscd is installed on my laptop. I
tried again the test in comment #1 for good measure, and it's still
working (rebooted several times and refreshed the chromium snap in the
meantime).

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

Title:
  [snap] Chromium does not work with .local mdns/avahi name resolution

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  (initially reported at https://forum.snapcraft.io/t/chromium-does-not-
  work-with-local-mdns-avahi-name-resolution/12483)

  The current chromium snap does not allow to open any .local urls.

  This is most likely caused by https://forum.snapcraft.io/t/no-mdns-
  support-in-snaps-should-core-have-a-modified-nsswitch-conf/7603.

  With the removal of the chromium deb and the switch to a snap-only
  deployment for this browser this is a pretty solid regression that
  should be addressed…

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838038/+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 1832786] Re: [snap] chromium-browser ignores system password store

@Russ, can you answer the question above?

  > What makes you say that the new snap release passes
  > the --password-store=basic command line argument?

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

Title:
  [snap] chromium-browser ignores system password store

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  The new chromium 75 snap package intentionally ignores the system
  password store:

  
https://chromium.googlesource.com/chromium/src.git/+/master/docs/linux_password_storage.md

  Normally, chromium auto-detects what type of password store to use,
  previously this has resulted in chromium connecting to the gnome
  password store. The new snap release passes the command line argument:

  '--password-store=basic'

  Which bypasses the gnome password storage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1832786/+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 1821765] Re: [snap] Missing icon in indicator

** Changed in: chromium-browser (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [snap] Missing icon in indicator

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Chromium is adding an appindicator, which has a missing icon when
  running from the snap.  I've confirmed with the deb that it shows the
  chromium icon there.  I'm not sure what setting makes it display the
  appindicator, I've had it there for years so must be some setting I
  have that is being synced.

  The only extensions I have installer are:

* The Great Suspender
* Google Drive
* Google Calendar

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1821765/+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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

2019-07-31 Thread Andreas Hasenack

sssd master has pcre2 support via
https://github.com/SSSD/sssd/pull/677#issuecomment-508238642

eoan is getting 2.2.0, which doesn't have that yet, but getting closer!

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in anope package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  Triaged
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Fix Released
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Fix Released
Status in libpam-mount package in Ubuntu:
  Fix Released
Status in libselinux package in Ubuntu:
  Fix Released
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php-defaults package in Ubuntu:
  Triaged
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Invalid
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged
Status in tilix package in Ubuntu:
  New
Status in ubuntu-core-meta package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in wget package in Ubuntu:
  Fix Released
Status in zsh package in Ubuntu:
  Incomplete

Bug description:
  https://people.canonical.com/~ubuntu-
  archive/transitions/html/pcre2-main.html

  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  --
  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just poorly 
named.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1825946] Re: 'nm' autopkgtest fails due to GI stderr output

2019-07-31 Thread Dan Streetman

A fix for this was added for bionic at version 1.10.14-0ubuntu2, but
that was reverted due to regressions, so this is not yet fixed in
bionic-updates

** Changed in: network-manager (Ubuntu Bionic)
   Status: Fix Released => In Progress

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

Title:
  'nm' autopkgtest fails due to GI stderr output

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  New
Status in network-manager source package in Bionic:
  In Progress

Bug description:
  [impact]

  'nm' testcase contains:
  from gi.repository import NetworkManager, NMClient, GLib  


 

  which generates output to stderr:
  /tmp/autopkgtest.naU0ts/build.riU/src/debian/tests/nm:23: PyGIWarning: 
NetworkManager was imported without specifying a version first. Use 
gi.require_version('NetworkManager', '1.0') before import to ensure that the 
right version gets loaded.

  the gi.require_version call has already been added to cosmic and
  disco.

  [test case]

  see http://autopkgtest.ubuntu.com/packages/network-manager bionic test
  results.

  [other info]

  this only fails intermittently, but the failure is clearly not an
  actual problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1825946/+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 1838508] Re: [snap] chromium crashes when opening a URL from an external application

>From chrome/browser/process_singleton_posix.cc:

// When the second process sends the current directory and command line flags to
// the first process, it waits for an ACK message back from the first process
// for a certain time. If there is no ACK message back in time, then the first
// process will be considered as hung for some reason. The second process then
// retrieves the process id from the symbol link and kills it by sending
// SIGKILL. Then the second process starts as normal.

The "read() failed" error message suggests that reading from the socket
fails for some reason, so the second process considers the first one
hung, and it kills it. The timeout isn't reached, because the default
built-in value is 20 seconds, and the problem happens much sooner than
that.

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

Title:
  [snap] chromium crashes when opening a URL from an external
  application

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  This appears to be a rather recent regression. I started observing
  this about a month ago (beginning of July 2019), and it was recently
  reported by another user (https://discourse.ubuntu.com/t/call-for-
  testing-chromium-browser-deb-to-snap-transition/11179/95).

  Steps to reproduce:

  0) Make sure the chromium snap is your default browser
  1) Open the chromium snap, and do your usual browsing activities
  2) Open a terminal, and execute `xdg-open https://example.org`
  2b) Repeat step 2 a few times until you get a notification that chromium 
crashed, offering to restore the previous session

  When the crash happens, I'm seeing this relevant error:

  [ERROR:process_singleton_posix.cc(207)] read() failed: Permission
  denied (13)

  and the corresponding entries in journalctl:

  juil. 31 09:53:07 bribon audit[25535]: AVC apparmor="DENIED" 
operation="file_perm" profile="snap.chromium.chromium" 
name="/run/user/1000/snap.chromium/.org.chromium.Chromium.LWcyoF/SingletonSocket"
 pid=25535 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  juil. 31 09:53:07 bribon audit[25535]: AVC apparmor="DENIED" 
operation="file_perm" profile="snap.chromium.chromium" 
name="/run/user/1000/snap.chromium/.org.chromium.Chromium.LWcyoF/SingletonSocket"
 pid=25535 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838508/+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 1823361] Re: WeTransfer filelink provider is missing

2019-07-31 Thread Jan

Same on Ubuntu 18.04.

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

Title:
  WeTransfer filelink provider is missing

Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Upstream builds of thunderbird include the WeTransfer filelink
  provider. The Ubuntu package doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: thunderbird 1:60.6.1+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  osomon 2794 F pulseaudio
  BuildID: 20190325095516
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  5 17:05:04 2019
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-07-02 (1006 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=60.6.1/20190325095516
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to disco on 2019-03-16 (19 days ago)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.sku: LENOVO_MT_2306
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1823361/+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 1740894] Re: KEY_RFKILL is not passed to userspace

2019-07-31 Thread Shih-Yuan Lee

I have made
https://code.launchpad.net/~fourdollars/ubuntu/+source/systemd/+git/systemd/+merge/370808
for bionic.

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

Title:
  KEY_RFKILL is not passed to userspace

Status in OEM Priority Project:
  New
Status in OEM Priority Project bionic series:
  New
Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in libxkbcommon source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xorgproto source package in Bionic:
  Fix Released
Status in libxkbcommon source package in Cosmic:
  Fix Released
Status in xkeyboard-config source package in Cosmic:
  Fix Released
Status in xorgproto source package in Cosmic:
  Fix Released

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1740894/+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 1837392] Re: "unable to find firefox.desktop" when clicking "Show Details" on the Firefox menu (top)

2019-07-31 Thread EoflaOE

Thanks lotuspsychje and Olivier Tilloy (osomon)! That helped confirm
that was a bug. Testing variety of software... Keep testing...

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

Title:
  "unable to find firefox.desktop" when clicking "Show Details" on the
  Firefox menu (top)

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  When a user tries to open the menu that is on the top, next to
  Activities button, and clicks "Show Details", it opens GNOME Software,
  but stays on the loading bar for a while then it says "Unable to find
  firefox.desktop".

  However, if I opened GNOME Software to search for Firefox, there are
  two entries for Firefox, one from Ubuntu repo, one from Snap. I know
  that Firefox existed on GNOME Software, but it seems weird that it
  won't be able to search for "firefox.desktop."

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu8
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 22 14:59:54 2019
  InstallationDate: Installed on 2019-07-21 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu8
  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/1837392/+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 1838508] [NEW] [snap] chromium crashes when opening a URL from an external application

Public bug reported:

This appears to be a rather recent regression. I started observing this
about a month ago (beginning of July 2019), and it was recently reported
by another user (https://discourse.ubuntu.com/t/call-for-testing-
chromium-browser-deb-to-snap-transition/11179/95).

Steps to reproduce:

0) Make sure the chromium snap is your default browser
1) Open the chromium snap, and do your usual browsing activities
2) Open a terminal, and execute `xdg-open https://example.org`
2b) Repeat step 2 a few times until you get a notification that chromium 
crashed, offering to restore the previous session

When the crash happens, I'm seeing this relevant error:

[ERROR:process_singleton_posix.cc(207)] read() failed: Permission denied
(13)

and the corresponding entries in journalctl:

juil. 31 09:53:07 bribon audit[25535]: AVC apparmor="DENIED" 
operation="file_perm" profile="snap.chromium.chromium" 
name="/run/user/1000/snap.chromium/.org.chromium.Chromium.LWcyoF/SingletonSocket"
 pid=25535 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
juil. 31 09:53:07 bribon audit[25535]: AVC apparmor="DENIED" 
operation="file_perm" profile="snap.chromium.chromium" 
name="/run/user/1000/snap.chromium/.org.chromium.Chromium.LWcyoF/SingletonSocket"
 pid=25535 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

** Affects: chromium-browser (Ubuntu)
 Importance: Critical
 Assignee: Olivier Tilloy (osomon)
 Status: Triaged


** Tags: snap

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

Title:
  [snap] chromium crashes when opening a URL from an external
  application

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  This appears to be a rather recent regression. I started observing
  this about a month ago (beginning of July 2019), and it was recently
  reported by another user (https://discourse.ubuntu.com/t/call-for-
  testing-chromium-browser-deb-to-snap-transition/11179/95).

  Steps to reproduce:

  0) Make sure the chromium snap is your default browser
  1) Open the chromium snap, and do your usual browsing activities
  2) Open a terminal, and execute `xdg-open https://example.org`
  2b) Repeat step 2 a few times until you get a notification that chromium 
crashed, offering to restore the previous session

  When the crash happens, I'm seeing this relevant error:

  [ERROR:process_singleton_posix.cc(207)] read() failed: Permission
  denied (13)

  and the corresponding entries in journalctl:

  juil. 31 09:53:07 bribon audit[25535]: AVC apparmor="DENIED" 
operation="file_perm" profile="snap.chromium.chromium" 
name="/run/user/1000/snap.chromium/.org.chromium.Chromium.LWcyoF/SingletonSocket"
 pid=25535 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  juil. 31 09:53:07 bribon audit[25535]: AVC apparmor="DENIED" 
operation="file_perm" profile="snap.chromium.chromium" 
name="/run/user/1000/snap.chromium/.org.chromium.Chromium.LWcyoF/SingletonSocket"
 pid=25535 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838508/+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 1838345] Re: Support Japanese new era "令和 (Reiwa)"

2019-07-31 Thread Nobuto Murata

Indeed, the upstream of Takao fonts as IPA fonts has a new release, so
we need to release a new one too.

https://ipafont.ipa.go.jp/
> 2019-04-26
> 
> IPAex Fonts (Ver.004.01) were released. Detail information is shown in 
> release notes.
> 
> Note: SQUARE ERA NAME REIWA(U+32FF) has been added. You may need to update 
> the dictionary for your input-method system to enter this character by Kana 
> input. Please refer instruction of your system for that.
> New version of IPAmjMincho with SQUARE ERA NAME REIWA will be available by 
> the end of May.


** Changed in: takao-fonts
   Importance: Undecided => Wishlist

** Changed in: takao-fonts
   Status: New => Triaged

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

Title:
  Support  Japanese new era "令和 (Reiwa)"

Status in Takao Fonts:
  Triaged
Status in fonts-takao package in Ubuntu:
  Triaged
Status in fonts-takao source package in Xenial:
  Triaged

Bug description:
  [Background]
  Many packages are affected by the requirement to support the new era "Reiwa" 
(令和）

  
  [Impact]
  Users who run Ubuntu in Japanese.

  [Test cases]

  == Character maps / font support ==

  1) Search for character "SQUARE ERA NAME"
  2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and 
"SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and 
that the glyphs are readable:

   - SQUARE ERA NAME HEISEI: ㍻
   - SQUARE ERA NAME REIWA: 令和 (in a single glyph)

  Display of the Reiwa square glyph is font-specific; it may show simply
  as a empty square or a square with hex characters. If that is the
  case, the unicode data supports the new character, but the selected
  font does not include the new glyph.

  == Typing / input methods ==

  1) Type in 'heisei'
  2) Verify that the input method in use gives you an option "平成", and 
optionally also the square era glyph.
  3) Type in 'reiwa'
  4) Verify that the input method in use gives you an option that includes 
"令和", and possibly also the square era glyph (if supported for Heisei)

  5) Type in the following strings, and verify that the options are provided in 
the input method:
  * "れいわ"(reiwa) => "令和"
  * "れいわ"(reiwa) => "㋿"
  * "２０１８ねん"(2018nenn) => "平成三十年"
  * "２０１９ねん"(2019nenn) => "平成三十一年"
  * "２０１９ねん"(2019nenn) => "令和元年"
  * "２０２０ねん"(2020nenn) => "令和二年"

  
  [Regression potential]
  This is a potentially large change as it impacts font display, character sets 
as well as date conversions. As such, extreme care should be taken to ensure 
that regressions are avoided, such that dates previous to May 1, 2019 continue 
to display as before, and dates onward are displayed with the new era symbols. 
The included test cases account for verifying the continued behavior or 
previous dates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/takao-fonts/+bug/1838345/+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 1838387] Re: ABI break in libraw 0.19.3 causing crashes in freeimage, and probably elsewhere

** Tags added: i386

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

Title:
  ABI break in libraw 0.19.3 causing crashes in freeimage, and probably
  elsewhere

Status in LibRaw:
  Unknown
Status in freeimage package in Ubuntu:
  Invalid
Status in libraw package in Ubuntu:
  Triaged

Bug description:
  The i386 testAPI in freeimage 3.18.0+ds2 crashes with proposed libraw
  0.19.3-1:

  free(): invalid pointer
  Aborted (core dumped)

  Originally reported at:

  http://autopkgtest.ubuntu.com/packages/f/freeimage/eoan/i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/libraw/+bug/1838387/+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 1838387] Re: ABI break in libraw 0.19.3 causing crashes in freeimage, and probably elsewhere