[Desktop-packages] [Bug 1846941] Re: Since upgrading to Eoan Ermine the screen doesn't dim progressively before turning off and locking the PC, but at once.

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Fix Released

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

Title:
  Since upgrading to Eoan Ermine the screen doesn't dim progressively
  before turning off and locking the PC, but at once.

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

Bug description:
  It wasn't behaving that way in Disco. Not sure if this issue belongs
  to X.org, but as that was the place for suspend/resume, i decided to
  place this bug here. If it's the wrong package, please help me in
  finding the correct one.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  6 13:46:25 2019
  DistUpgraded: 2019-09-28 01:59:57,153 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:1193]
 Subsystem: Acer Incorporated [ALI] GP108M [GeForce MX150] [1025:119a]
  InstallationDate: Installed on 2019-07-23 (74 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID :0538   USB OPTICAL MOUSE
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A515-51G
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (8 days ago)
  dmi.bios.date: 01/03/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.02
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charmander_KL
  dmi.board.vendor: KBL
  dmi.board.version: V2.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-51G
  dmi.product.sku: 
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.0-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1846941/+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 1524215] Re: Lenovo B50-70 inverted internal microphone

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Lenovo B50-70 inverted internal microphone

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978 
  Attached the alsa-info txt to this bug
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marian 1981 F pulseaudio
   /dev/snd/pcmC1D0c:   marian 1981 F...m pulseaudio
   /dev/snd/pcmC1D0p:   marian 1981 F...m pulseaudio
   /dev/snd/controlC1:  marian 1981 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=10570c82-8e52-4379-9a8e-2e30baae9f63
  InstallationDate: Installed on 2015-09-10 (90 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20384
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=1791e4c1-12de-4fef-88b1-31716c981648 ro quiet splash
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: Upgraded to wily on 2015-10-24 (45 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9DCN34WW(V3.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo B50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9DCN34WW(V3.04):bd07/21/2015:svnLENOVO:pn20384:pvrLenovoB50-70:rvnLENOVO:rnLenovoB50-70:rvrNODPK:cvnLENOVO:ct10:cvrLenovoB50-70:
  dmi.product.name: 20384
  dmi.product.version: Lenovo B50-70
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1524215/+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 1839603] Re: Wifi breaks and needs restart after Laptop's wake up

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Wifi breaks and needs restart after Laptop's wake up

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  This is constant struggle for me, it seems that in the initial days
  after installation of Ubuntu 19.10 this problem of Wifi stopping to
  work after wake up does not happen. I'm sure, I reinstalled Ubuntu
  many times, the issue still persist.

  Breaking of Wifi after computer wake up starts to appear, on average,
  after a week of computer usage.

  On my laptop, this Wifi problem existed in the previous Ubuntu
  versions as well.

  What works: It seems a simple Wifi turn off and turn on is sufficient,
  for the bug to go away. But I'm getting tired of this after years of
  doing it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1839603/+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 1846941] Re: Since upgrading to Eoan Ermine the screen doesn't dim progressively before turning off and locking the PC, but at once.

[Daniel van Vugt]

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

** Changed in: gnome-shell
   Status: New => Unknown

** Changed in: gnome-shell
 Remote watch: gitlab.gnome.org/GNOME/gnome-shell/issues #1463 => 
gitlab.gnome.org/GNOME/gnome-shell/issues #1683

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

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

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

Title:
  Since upgrading to Eoan Ermine the screen doesn't dim progressively
  before turning off and locking the PC, but at once.

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

Bug description:
  It wasn't behaving that way in Disco. Not sure if this issue belongs
  to X.org, but as that was the place for suspend/resume, i decided to
  place this bug here. If it's the wrong package, please help me in
  finding the correct one.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  6 13:46:25 2019
  DistUpgraded: 2019-09-28 01:59:57,153 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] UHD Graphics 620 [1025:1193]
 Subsystem: Acer Incorporated [ALI] GP108M [GeForce MX150] [1025:119a]
  InstallationDate: Installed on 2019-07-23 (74 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID :0538   USB OPTICAL MOUSE
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A515-51G
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (8 days ago)
  dmi.bios.date: 01/03/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.02
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charmander_KL
  dmi.board.vendor: KBL
  dmi.board.version: V2.02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.02:bd01/03/2019:svnAcer:pnAspireA515-51G:pvrV2.02:rvnKBL:rnCharmander_KL:rvrV2.02:cvnAcer:ct10:cvrV2.02:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-51G
  dmi.product.sku: 
  dmi.product.version: V2.02
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.0-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1846941/+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 1846140] Re: Realtek RTL8723BU doesn't work well in ubuntu

[Kai-Heng Feng]

This may fix the issue:
https://lore.kernel.org/lkml/20191002121808.59376-1-c...@endlessm.com/

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

Title:
  Realtek RTL8723BU doesn't work well in ubuntu

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  I have one laptop with Realtek RTL8723BU wifi card. It runs, but
  signal is weak (it only works if the router is less than a meter
  away), and even if it gets signal it's slow and it gets interrupted
  frequently. In windows it works normally, and with a much stronger
  signal. I tested it on Ubuntu 18.04.3 and 19.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846140/+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 1842910] Re: Desktop right click menu appears in the wrong place if a Terminal window is open

[Daniel van Vugt]

** No longer affects: gnome-shell-extension-desktop-icons (Ubuntu)

** No longer affects: gnome-shell-extension-desktop-icons (Ubuntu Eoan)

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

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

Title:
  Desktop right click menu appears in the wrong place if a Terminal
  window is open

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Eoan:
  In Progress

Bug description:
  Desktop right click menu appears in the wrong place if a Terminal
  window is open.

  1. Open a Terminal

  2. Right click on the desktop.

  Expected: The menu appears where you click.
  Observed: The menu appears near the Terminal window instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell-extension-desktop-icons 19.01.3+git20190814.1-1
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Thu Sep  5 18:26:24 2019
  InstallationDate: Installed on 2019-05-02 (126 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1842910/+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 1847021] Re: Cannot input Chinese if only "Chinese (Intelligent Pinyin)" is set

[Peng Wu]

> @Peng Wu: Are you able to summarize the purpose of those reversals? Do
they, as I'm implying, make ibus-libpinyin more stable and prevent
certain crash types?

@Gunnar Hjalmarsson: Yes, it will prevent some kind of file corruption.

> The dictionary built in conjunction with libpinyin 2.2 cannot be ported
> to version 2.3. 

@Gunnar Hjalmarsson: It will only clean up the user data,
and provide better dictionary data in libpinyin.

Please use the tar ball release for packaging, thanks!

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

Title:
  Cannot input Chinese if only "Chinese (Intelligent Pinyin)" is set

Status in ibus-libpinyin package in Ubuntu:
  Invalid

Bug description:
  See also https://github.com/libpinyin/ibus-libpinyin/issues/184

  Ubuntu 19.04. If I only install "Chinese (Intelligent Pinyin)", after
  pressing 'super+space' input is switched to Pinyin (can be seen from
  the icon on system bar). However it still input English directly. Even
  if I tried 'shift' button it's still the same.

  If I install "Chinese (Pinyin)" it works all perfect. If I install
  both "Chinese (Pinyin)" and "Chinese (Intelligent Pinyin)", both
  works.

  So, seems something is missing? Something required by Intelligent
  Pinyin but only installed with Pinyin?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ibus-libpinyin 1.11.0-1ubuntu0.19.04
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  7 17:24:17 2019
  InstallationDate: Installed on 2018-06-07 (487 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: Upgraded to disco on 2019-09-30 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1847021/+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 1847399] Re: Help me

[Daniel van Vugt]

Please describe the kind of problem you are experiencing.

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

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

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

Title:
  Help me

Status in Ubuntu:
  Incomplete

Bug description:
  Sorry I don't understand

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Oct  9 03:56:09 2019
  DistUpgraded: 2018-09-18 19:18:07,768 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio 
"./xorg_fix_proprietary.py" non riuscita (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: No
  GraphicsCard:
   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
   NVIDIA Corporation GF119 [GeForce GT 620 OEM] [10de:1049] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF119 [GeForce GT 620 OEM] [1043:84a3]
  InstallationDate: Installed on 2015-04-17 (1635 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. K30AD_M31AD_M51AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=12b53c52-cdca-4b0e-917f-4f4568ed643a ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-18 (385 days ago)
  dmi.bios.date: 11/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0402
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K30AD_M31AD_M51AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0402:bd11/29/2013:svnASUSTeKCOMPUTERINC.:pnK30AD_M31AD_M51AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnK30AD_M31AD_M51AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: Desktop
  dmi.product.name: K30AD_M31AD_M51AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Sep 18 15:20:24 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1847399/+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 1847400] Re: Printer drivers crashes after printing something

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1845548, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1847400/+attachment/5295704/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1847400/+attachment/5295708/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1847400/+attachment/5295717/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1847400/+attachment/5295719/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1847400/+attachment/5295720/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1847400/+attachment/5295721/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1847400/+attachment/5295722/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1845548
   implicitclass crashed with SIGABRT in __malloc_assert()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Printer drivers crashes after printing something

Status in cups-filters package in Ubuntu:
  New

Bug description:
  Printing anything seems to crash the drivers, after that it simply
  refuses to print anything else unless I reconnect the printer, if it
  helps, the printer is a HP Deskjet Ink Advantage 2546 connected
  wirelessly.

  $lsb_release -rd
  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10

  $ apt-cache policy cups-filters
  cups-filters:
Installed: 1.25.6-1
Candidate: 1.25.6-1
Version table:
   *** 1.25.6-1 500
  500 http://br.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  Launchpad also gave me an automatic summary: implicitclass crashed
  with SIGABRT in __malloc_assert()

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: cups-browsed 1.25.6-1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Tue Oct  8 23:57:43 2019
  ExecutablePath: /usr/lib/cups/backend/implicitclass
  InstallationDate: Installed on 2019-10-01 (7 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  Lpstat: device for Deskjet_2540_series_3429F6_: 
implicitclass://Deskjet_2540_series_3429F6_/
  MachineType: Dell Inc. Inspiron 5566
  Papersize: a4
  PpdFiles: Deskjet_2540_series_3429F6_: Deskjet 2540 series - IPP Everywhere
  ProcCmdline: implicitclass://Deskjet_2540_series_3429F6_/ 3 biguibi Untitled\ 
1 1 PageSize=A4\ job-uuid=urn:uuid:47f56d7d-3740-35e6-5551-31fe1ab13d1a\ 
cups-browsed\ cups-browsed-dest-printer=\\"2\\\ 
ipp://HP5CB9013429F6.local:631/ipp/print\\\ apple-raster\\\ 600dpi\\"\ 
job-originating-host-name=localhost\ date-time-at-creation=\ 
date-time-at-processing=\ time-at-creation=1570589829\ 
time-at-processing=1570589862\ document-name-supplied=jenO2f
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=2beff0e7-4b1e-48a4-8996-a0dc86e9e7f5 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups-filters
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0x7fcfb9d582d8 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0x7fcfb9d5443f "malloc.c", line=line@entry=2379, 
function=function@entry=0x7fcfb9d58a60 <__PRETTY_FUNCTION__.13032> "sysmalloc") 
at malloc.c:298
   sysmalloc (nb=nb@entry=320, av=av@entry=0x7fcfb9d87b80 ) at 
malloc.c:2379
   _int_malloc (av=av@entry=0x7fcfb9d87b80 , bytes=bytes@entry=297) 
at malloc.c:4141
   __GI___libc_malloc (bytes=bytes@entry=297) at malloc.c:3058
   __GI___strdup (s=0x555c5bead9d0 "PageSize=A4 
job-uuid=urn:uuid:47f56d7d-3740-35e6-5551-31fe1ab13d1a cups-browsed 
job-originating-host-name=localhost date-time-at-creation= 
date-time-at-processing= time-at-creation=1570589829 time-at-"...) at 

[Desktop-packages] [Bug 1846692] Re: PCI/internal sound card not detected

[Hui Wang]

If we use 5.0 generic kernel, the kernel should load the legacy hda
driver because there is no sof driver in the 5.0 generic kernel.

For this problem, the legacy hda driver is not loaded, maybe users
forget to install linux-modules-extra-

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  As discussed with Rex Tsai

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  4 09:43:52 2019
  InstallationDate: Installed on 2019-09-23 (10 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET37W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET37W(1.20):bd09/11/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846692/+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 1847399] [NEW] Help me

[Davide]

Public bug reported:

Sorry I don't understand

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Oct  9 03:56:09 2019
DistUpgraded: 2018-09-18 19:18:07,768 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio 
"./xorg_fix_proprietary.py" non riuscita (No such file or directory) (8))
DistroCodename: bionic
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: No
GraphicsCard:
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
 NVIDIA Corporation GF119 [GeForce GT 620 OEM] [10de:1049] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GF119 [GeForce GT 620 OEM] [1043:84a3]
InstallationDate: Installed on 2015-04-17 (1635 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: ASUSTeK COMPUTER INC. K30AD_M31AD_M51AD
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=12b53c52-cdca-4b0e-917f-4f4568ed643a ro splash quiet
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-09-18 (385 days ago)
dmi.bios.date: 11/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0402
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: K30AD_M31AD_M51AD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0402:bd11/29/2013:svnASUSTeKCOMPUTERINC.:pnK30AD_M31AD_M51AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnK30AD_M31AD_M51AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: Desktop
dmi.product.name: K30AD_M31AD_M51AD
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Tue Sep 18 15:20:24 2018
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.8
xserver.video_driver: nouveau

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

Title:
  Help me

Status in xorg package in Ubuntu:
  New

Bug description:
  Sorry I don't understand

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Oct  9 03:56:09 2019
  DistUpgraded: 2018-09-18 19:18:07,768 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio 
"./xorg_fix_proprietary.py" non riuscita (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: No
  GraphicsCard:
   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
   NVIDIA Corporation GF119 [GeForce GT 620 OEM] [10de:1049] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF119 [GeForce GT 620 OEM] [1043:84a3]
  InstallationDate: Installed on 2015-04-17 (1635 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. K30AD_M31AD_M51AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=12b53c52-cdca-4b0e-917f-4f4568ed643a ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-18 (385 days ago)
  dmi.bios.date: 11/29/2013
  

[Desktop-packages] [Bug 1846140] Re: Realtek RTL8723BU doesn't work well in ubuntu

[Roque]

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

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

Title:
  Realtek RTL8723BU doesn't work well in ubuntu

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  I have one laptop with Realtek RTL8723BU wifi card. It runs, but
  signal is weak (it only works if the router is less than a meter
  away), and even if it gets signal it's slow and it gets interrupted
  frequently. In windows it works normally, and with a much stronger
  signal. I tested it on Ubuntu 18.04.3 and 19.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846140/+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 1847222] Re: serverX crashes randomly

[Daniel van Vugt]

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

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

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

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

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

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

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

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

Title:
  serverX crashes randomly

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Crash of X11 and after 0.5 to 2 seconds Ubuntu shutdown.

  This appears randomly, the system journal says nothing at this moment
  and there's no report in /var/crash

  The .xsession-errors.old contains often the line: 
  XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 33 requests (33 known processed) with 0 events remaining.
  Gdk-Message: 01:16:44.392: mate-screensaver: Fatal IO error 11 (Ressource 
temporairement non disponible) on X server :0.

  Note: mate-screensaver is just an example.

  Configuration:
  Ubuntu 18-04.3 LTS 64 bytes
  Environment Mate

  vincent@djoliba:~$ lspci
  00:00.0 Host bridge: Intel Corporation 82Q963/Q965 Memory Controller Hub (rev 
02)
  00:02.0 VGA compatible controller: Intel Corporation 82Q963/Q965 Integrated 
Graphics Controller (rev 02)
  00:03.0 Communication controller: Intel Corporation 82Q963/Q965 HECI 
Controller (rev 02)
  00:03.2 IDE interface: Intel Corporation 82Q963/Q965 PT IDER Controller (rev 
02)
  00:03.3 Serial controller: Intel Corporation 82Q963/Q965 KT Controller (rev 
02)
  00:19.0 Ethernet controller: Intel Corporation 82566DM Gigabit Network 
Connection (rev 02)
  00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #4 (rev 02)
  00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI 
Controller #2 (rev 02)
  00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio 
Controller (rev 02)
  00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #1 (rev 02)
  00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #2 (rev 02)
  00:1d.2 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #3 (rev 02)
  00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI 
Controller #1 (rev 02)
  00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev f2)
  00:1f.0 ISA bridge: Intel Corporation 82801HO (ICH8DO) LPC Interface 
Controller (rev 02)
  00:1f.2 IDE interface: Intel Corporation 82801H (ICH8 Family) 4 port SATA 
Controller [IDE mode] (rev 02)
  00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 
02)
  00:1f.5 IDE interface: Intel Corporation 82801HR/HO/HH (ICH8R/DO/DH) 2 port 
SATA Controller [IDE mode] (rev 02)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1847222/+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 1834967] Re: Activities overview doesn't shrink some windows adequately and they are partially off screen

[Bug Watch Updater]

** Changed in: ubuntu-dock
   Status: Unknown => New

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

Title:
  Activities overview doesn't shrink some windows adequately and they
  are partially off screen

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

Bug description:
  Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  1 20:38:43 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-dock/+bug/1834967/+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 1845205] Re: Cannot submit crash reports from firefox' "this tab crashed" page

[Launchpad Bug Tracker]

This bug was fixed in the package firefox - 69.0.2+build1-0ubuntu2

---
firefox (69.0.2+build1-0ubuntu2) eoan; urgency=medium

  * Install the minidump-analyzer executable (LP: #1845205)
- update debian/firefox.install.in

 -- Olivier Tilloy   Tue, 08 Oct 2019
14:51:08 +0200

** Changed in: firefox (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Cannot submit crash reports from firefox' "this tab crashed" page

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:

  - Launch firefox
  - Enter "about:crashcontent" in the URL bar
  - Upon hitting return, the tab should crash and display the "This tab just 
crashed" page
  - Ensure that the checkmark to send the crash report is ticked
  - Add a comment (anything will do, a non-empty comment ensures that the crash 
is accepted by Mozilla crash reporting back-end)
  - Click on "Restore this tab"
  - Go to the "about:crashes" page

  Expected behaviour:

  In the "about:crashes" page the crash is displayed among the submitted
  crash reports, showing that the crash report was indeed submitted
  correctly.

  Actual behaviour:

  The crash appears among the unsubmitted crashes.

  This bug is specific to the packaged version of Firefox that comes
  with Ubuntu. I've tried reproducing using Mozilla's builds and crash
  submission works correctly there. See this bug
  https://bugzilla.mozilla.org/show_bug.cgi?id=1583247 on Mozilla's
  tracker regarding this behaviour. In Mozilla we noticed the issue
  because we've started properly processing crash reports coming from
  Ubuntu and tab crashes were strangely few. Feel free to contact me
  directly at gsve...@mozilla.com about this issue since I'm in charge
  of Firefox crash reporting machinery.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1845205/+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 1847346] Re: [MIR] nacl: pulled into main via libssh Built-Using

[Launchpad Bug Tracker]

This bug was fixed in the package libssh - 0.9.0-1ubuntu1

---
libssh (0.9.0-1ubuntu1) eoan; urgency=medium

  * Disable libnacl support, which has not gone through an MIR.
LP: #1847346.

 -- Steve Langasek   Tue, 08 Oct 2019
20:31:16 +

** Changed in: libssh (Ubuntu)
   Status: New => Fix Released

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

Title:
  [MIR] nacl: pulled into main via libssh Built-Using

Status in libssh package in Ubuntu:
  Fix Released
Status in nacl package in Ubuntu:
  Incomplete

Bug description:
  The libssh package has a Built-Using: nacl field in its binaries,
  indicating that it is embedding code from nacl.  The changelog
  confirms that this was added because libssh statically links nacl.
  Either nacl needs to go through an MIR process since we're shipping
  the code in main, or libssh needs to not use nacl.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1847346/+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 1838836] Re: network-manager needs to be restarted frequently

[Chelmite]

It's still broken, even though I haven't received any suggestions on what to 
try.
Sometimes the network is lost when resuming after suspend, sometimes, just 
because it feels like it.

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

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

Title:
  network-manager needs to be restarted frequently

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops
  working frequently and the network-manager service needs to be
  restarted. It will die on its own, but can be triggered by switching
  wifi 3 times (sometimes more, sometimes fewer)!

  When it is working, I have:
  ```
  % usr/bin/sudo nmcli device
  DEVICE   TYPE  STATE CONNECTION 
  wlp62s0  wifi  connected ATT964 
  p2p-dev-wlp62s0  wifi-p2p  disconnected  -- 
  enp59s0  ethernet  unavailable   -- 
  lo   loopback  unmanaged --   
  % /usr/bin/sudo lshw -C network
   ...snip...
*-network
 description: Wireless interface
 product: Wireless 8260
 vendor: Intel Corporation
 physical id: 0
 bus info: pci@:3e:00.0
 logical name: wlp62s0
 version: 3a
 serial: e4:b3:18:e3:11:e7
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet 
physical wireless
 configuration: broadcast=yes driver=iwlwifi 
driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:133 memory:dc20-dc201fff
  % /usr/bin/sudo lspci -vnnn | grep -A 9 Network
  3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 
[8086:24f3] (rev 3a)
Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010]
Flags: bus master, fast devsel, latency 0, IRQ 133
Memory at dc20 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7
Capabilities: [14c] Latency Tolerance Reporting
  ```
  If I switch between my two wifi routers three times (sometimes more times) 
using the Select Network command on the taskbar, wifi stops working.

  Issuing the commands above yields the following differences:
  ```
  % /usr/bin/sudo nmcli device
  DEVICE   TYPE  STATECONNECTION 
  enp59s0  ethernet  unavailable  -- 
  wlp62s0  wifi  unavailable  -- 
  p2p-dev-wlp62s0  wifi-p2p  unavailable  -- 
  lo   loopback  unmanaged
  
  % /usr/bin/sudo lshw -C network
   ...snip...
*-network
   ...snip...
  configuration: broadcast=yes driver=iwlwifi 
driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11
  ```
  /var/log/syslog reports the following after failing to switch wifi networks:
  ```
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5482] 
device (wlp62s0): disconnecting for new activation request.
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5482] 
device (wlp62s0): state change: activated -> deactivating (reason 
'new-activation', sys-iface-state: 'managed')
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5485] 
manager: NetworkManager state is now DISCONNECTING
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5548] 
audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" 
name="ATT964" pid=21476 uid=1010 result="success"
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5550] 
device (wlp62s0): state change: deactivating -> disconnected (reason 
'new-activation', sys-iface-state: 'managed')
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5562] 
dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5562] 
dhcp4 (wlp62s0): state changed bound -> done
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5572] 
dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5572] 
dhcp6 (wlp62s0): state changed bound -> done
  Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating 
from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING)
  Jul 16 

[Desktop-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently

[Chelmite]

Network shutdown still happens in Ubuntu 19.10.

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

Title:
  network-manager needs to be restarted frequently

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops
  working frequently and the network-manager service needs to be
  restarted. It will die on its own, but can be triggered by switching
  wifi 3 times (sometimes more, sometimes fewer)!

  When it is working, I have:
  ```
  % usr/bin/sudo nmcli device
  DEVICE   TYPE  STATE CONNECTION 
  wlp62s0  wifi  connected ATT964 
  p2p-dev-wlp62s0  wifi-p2p  disconnected  -- 
  enp59s0  ethernet  unavailable   -- 
  lo   loopback  unmanaged --   
  % /usr/bin/sudo lshw -C network
   ...snip...
*-network
 description: Wireless interface
 product: Wireless 8260
 vendor: Intel Corporation
 physical id: 0
 bus info: pci@:3e:00.0
 logical name: wlp62s0
 version: 3a
 serial: e4:b3:18:e3:11:e7
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet 
physical wireless
 configuration: broadcast=yes driver=iwlwifi 
driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:133 memory:dc20-dc201fff
  % /usr/bin/sudo lspci -vnnn | grep -A 9 Network
  3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 
[8086:24f3] (rev 3a)
Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010]
Flags: bus master, fast devsel, latency 0, IRQ 133
Memory at dc20 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7
Capabilities: [14c] Latency Tolerance Reporting
  ```
  If I switch between my two wifi routers three times (sometimes more times) 
using the Select Network command on the taskbar, wifi stops working.

  Issuing the commands above yields the following differences:
  ```
  % /usr/bin/sudo nmcli device
  DEVICE   TYPE  STATECONNECTION 
  enp59s0  ethernet  unavailable  -- 
  wlp62s0  wifi  unavailable  -- 
  p2p-dev-wlp62s0  wifi-p2p  unavailable  -- 
  lo   loopback  unmanaged
  
  % /usr/bin/sudo lshw -C network
   ...snip...
*-network
   ...snip...
  configuration: broadcast=yes driver=iwlwifi 
driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11
  ```
  /var/log/syslog reports the following after failing to switch wifi networks:
  ```
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5482] 
device (wlp62s0): disconnecting for new activation request.
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5482] 
device (wlp62s0): state change: activated -> deactivating (reason 
'new-activation', sys-iface-state: 'managed')
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5485] 
manager: NetworkManager state is now DISCONNECTING
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5548] 
audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" 
name="ATT964" pid=21476 uid=1010 result="success"
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5550] 
device (wlp62s0): state change: deactivating -> disconnected (reason 
'new-activation', sys-iface-state: 'managed')
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5562] 
dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5562] 
dhcp4 (wlp62s0): state changed bound -> done
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5572] 
dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5572] 
dhcp6 (wlp62s0): state changed bound -> done
  Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating 
from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING)
  Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0: 
CTRL-EVENT-DISCONNECTED bssid=10:7b:ef:cc:ab:a3 reason=3 locally_generated=1
  Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0: 
CTRL-EVENT-SIGNAL-CHANGE 

[Desktop-packages] [Bug 1847176] Re: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card

[Matthew Ruffell]

@gunnarl, did your audio work correctly in kernel 5.0.0-29, and broke when you 
updated to 5.0.0-31?
If you boot 5.0.0-29 by selecting it in grub when you turn your computer on, 
does your audio work?

Might this be related to Bug 1846991?

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

Title:
  [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal]
  Pulseaudio fails to detect card

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

Bug description:
  No Sound on laptop speaker after upgrading ubuntu 19.04 a few days
  ago. Soundcard is found in alsamixer but only "dummy" is available in
  gnome settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  7 20:18:10 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-25 (681 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [HP ENVY Laptop 13-ad1xx, Realtek ALC295, Speaker, Internal] 
Pulseaudio fails to detect card
  UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago)
  dmi.bios.date: 08/07/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83A9
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 39.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY Laptop 13-ad1xx
  dmi.product.sku: 1KT13UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=ec963f21-6d46-4fd7-a5b5-286e29729b6b
  InstallationDate: Installed on 2017-11-25 (681 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:5620 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY Laptop 13-ad1xx
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=d203e9e9-3d32-4223-b420-e5ce61567401 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-31-generic N/A
   linux-backports-modules-5.0.0-31-generic  N/A
   linux-firmware1.178.3
  Tags:  disco
  Uname: Linux 5.0.0-31-generic x86_64
  UpgradeStatus: Upgraded to disco on 2018-05-26 (499 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 08/07/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83A9
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 39.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd08/07/2017:svnHP:pnHPENVYLaptop13-ad1xx:pvrType1ProductConfigId:rvnHP:rn83A9:rvrKBCVersion39.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY Laptop 13-ad1xx
  

[Desktop-packages] [Bug 1847354] [NEW] Update to 69.0.2

[Chris Coulson]

Public bug reported:

https://www.mozilla.org/en-US/firefox/69.0.2/releasenotes/

** Affects: firefox (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Changed in: firefox (Ubuntu)
   Status: New => Fix Released

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

Title:
  Update to 69.0.2

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  https://www.mozilla.org/en-US/firefox/69.0.2/releasenotes/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1847354/+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 1847346] Re: [MIR] nacl: pulled into main via libssh Built-Using

[Steve Langasek]

According to the cmake rules libnacl is used for curve25519 support,
which is optional.  I think for eoan we should address this by disabling
nacl at build time.  I'll upload this libssh change, which takes the
pressure off for eoan release, and the MIR can be revisited in FF.

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

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

Title:
  [MIR] nacl: pulled into main via libssh Built-Using

Status in libssh package in Ubuntu:
  New
Status in nacl package in Ubuntu:
  Incomplete

Bug description:
  The libssh package has a Built-Using: nacl field in its binaries,
  indicating that it is embedding code from nacl.  The changelog
  confirms that this was added because libssh statically links nacl.
  Either nacl needs to go through an MIR process since we're shipping
  the code in main, or libssh needs to not use nacl.

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

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

Re: [Desktop-packages] [Bug 1831295] Re: Firefox freeze when I drag an URL address to a Nautilus window

[J-Paul BERARD]

Hello,

Like I had several problems with 19.04 (mainly the computer which didn't 
stop completly), I've already updated the system to 19.10 RC.

And I have no more this bug : when I drag the adress on the desktop or a 
Nautilus window, nothing happens : the URL is not copied but the app 
doesn't freeze any more.

Firefox 69.02 - Wayland

Good evening.

-- 
Jean-Paul

Le 08/10/2019 à 13:02, Olivier Tilloy a écrit :
> Sorry for the lack of timely feedback J-Paul.
> Are you still seeing the problem with the most recent firefox update?
> I just tested in a fully up-to-date 19.04 virtual machine, and I cannot 
> reproduce it myself.
>
> ** Changed in: firefox (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  Firefox freeze when I drag an URL address to a Nautilus window

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  When a web page is displayed in Firefox, if you select the URL in the address 
bar and try to drag it to the desktop or a Nautilus window, it is not done.
  But, afterwards, the mouse cursor become a hand and nothing is more possible 
with Firefox : you cannot select something, see the menu...
  You can only kill the app.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: firefox 67.0+build2-0ubuntu0.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jpaul  2420 F pulseaudio
   /dev/snd/controlC0:  jpaul  2420 F pulseaudio
   /dev/snd/controlC2:  jpaul  2420 F pulseaudio
  BuildID: 20190517140251
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 31 23:21:34 2019
  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 2019-04-26 (35 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.0.254 dev wlp4s6 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s6 scope link metric 1000 
   192.168.0.0/24 dev wlp4s6 proto kernel scope link src 192.168.0.10 metric 600
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:1151
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=fr_FR:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=67.0/20190517140251 (In use)
  RelatedPackageVersions: adobe-flashplugin 1:20190514.1-0ubuntu0.19.04.1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: 970 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd08/05/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1831295/+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 545778] Re: xul-ext-lightning is only available in English

[Launchpad Bug Tracker]

This bug was fixed in the package thunderbird -
1:60.9.0+build1-0ubuntu0.19.04.1

---
thunderbird (1:60.9.0+build1-0ubuntu0.19.04.1) disco; urgency=medium

  * New upstream stable release (60.9.0build1)

  * Do not attach Wi-Fi syslog to apport reports (LP: #1801383)
- update debian/apport/source_thunderbird.py.in
  * Install the WeTransfer FileLink provider by default (LP: #1823361)
- update debian/thunderbird.install.in
  * Do not exclude calendar translations from the source tarball, and repack
the lightning xpi with all available locales (LP: #545778)
- update debian/config/tarball.conf
- update debian/build/rules.mk
- update debian/rules

 -- Olivier Tilloy   Mon, 07 Oct 2019
10:32:00 +0200

** Changed in: thunderbird (Ubuntu Disco)
   Status: Fix Committed => Fix Released

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

Title:
  xul-ext-lightning is only available in English

Status in One Hundred Papercuts:
  Invalid
Status in Mozilla Thunderbird:
  Invalid
Status in Ubuntu Translations:
  Invalid
Status in lightning-sunbird package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Xenial:
  Fix Released
Status in thunderbird source package in Bionic:
  Fix Released
Status in thunderbird source package in Disco:
  Fix Released

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Change the user session language to other different than English.
  2. In Thunderbird, open the calendar

  EXPECTED BEHAVIOUR

  - The calendar interface to be in the session language.

  REAL BEHAVIOUR

  - The calendar is in English.

  RELEVANT DETAILS

  - None.

  **
   SOLUTION
  **

  WORK-AROUND

  - None known.

  FIX

  - .

  REGRESSION POTENTIAL

  - Since no code needs to be modified, the regression potential is very
  low.

  
   TECHNICAL INFO
  

  Binary package hint: lightning-extension

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/545778/+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 545778] Re: xul-ext-lightning is only available in English

[Launchpad Bug Tracker]

This bug was fixed in the package thunderbird -
1:60.9.0+build1-0ubuntu0.16.04.2

---
thunderbird (1:60.9.0+build1-0ubuntu0.16.04.2) xenial; urgency=medium

  * Enclose the path to the lightning extension XPI in double quotes to ensure
dh_install finds it
- update debian/rules

 -- Olivier Tilloy   Mon, 07 Oct 2019
10:59:57 +0200

** Changed in: thunderbird (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  xul-ext-lightning is only available in English

Status in One Hundred Papercuts:
  Invalid
Status in Mozilla Thunderbird:
  Invalid
Status in Ubuntu Translations:
  Invalid
Status in lightning-sunbird package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Xenial:
  Fix Released
Status in thunderbird source package in Bionic:
  Fix Released
Status in thunderbird source package in Disco:
  Fix Released

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Change the user session language to other different than English.
  2. In Thunderbird, open the calendar

  EXPECTED BEHAVIOUR

  - The calendar interface to be in the session language.

  REAL BEHAVIOUR

  - The calendar is in English.

  RELEVANT DETAILS

  - None.

  **
   SOLUTION
  **

  WORK-AROUND

  - None known.

  FIX

  - .

  REGRESSION POTENTIAL

  - Since no code needs to be modified, the regression potential is very
  low.

  
   TECHNICAL INFO
  

  Binary package hint: lightning-extension

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/545778/+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 1847346] [NEW] [MIR] nacl: pulled into main via libssh Built-Using

[Steve Langasek]

Public bug reported:

The libssh package has a Built-Using: nacl field in its binaries,
indicating that it is embedding code from nacl.  The changelog confirms
that this was added because libssh statically links nacl.  Either nacl
needs to go through an MIR process since we're shipping the code in
main, or libssh needs to not use nacl.

** Affects: nacl (Ubuntu)
 Importance: Critical
 Assignee: Ubuntu Desktop Bugs (desktop-bugs)
 Status: Incomplete

** Changed in: libssh (Ubuntu)
   Importance: Undecided => Critical

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

** Changed in: libssh (Ubuntu)
 Assignee: (unassigned) => Desktop Packages (desktop-packages)

** Changed in: libssh (Ubuntu)
 Assignee: Desktop Packages (desktop-packages) => Ubuntu Desktop Bugs 
(desktop-bugs)

** Package changed: libssh (Ubuntu) => nacl (Ubuntu)

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

Title:
  [MIR] nacl: pulled into main via libssh Built-Using

Status in nacl package in Ubuntu:
  Incomplete

Bug description:
  The libssh package has a Built-Using: nacl field in its binaries,
  indicating that it is embedding code from nacl.  The changelog
  confirms that this was added because libssh statically links nacl.
  Either nacl needs to go through an MIR process since we're shipping
  the code in main, or libssh needs to not use nacl.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nacl/+bug/1847346/+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 1845471] Re: gnome-calendar won't start from Activities Overview

[Paul White]

Also tested gnome-calendar 3.34.1-1 in a live session using daily ISO
20191008 and found that it starts as it should from the Activities
Overview.

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

Title:
  gnome-calendar won't start from Activities Overview

Status in gnome-calendar package in Ubuntu:
  Incomplete

Bug description:
  During ISO testing (live-session) I found that I was unable to start
  gnome-calendar.

  Steps to reproduce:
  Display Activities Overview, search for and select "Calendar"

  Expected outcome:
  Application starts

  Actual outcome:
  Application doesn't start

  Workaround:
  Pin application icon to Ubuntu Dock or start from terminal

  Confirmation of issue:
  I can confirm this issue with a permanent installation on another machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-calendar 3.34.0-1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 26 10:36:08 2019
  InstallationDate: Installed on 2019-05-17 (131 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1845471/+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 545778] Re: xul-ext-lightning is only available in English

[Launchpad Bug Tracker]

This bug was fixed in the package thunderbird -
1:60.9.0+build1-0ubuntu0.18.04.1

---
thunderbird (1:60.9.0+build1-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream stable release (60.9.0+build1)

  * Do not attach Wi-Fi syslog to apport reports (LP: #1801383)
- update debian/apport/source_thunderbird.py.in
  * Install the WeTransfer FileLink provider by default (LP: #1823361)
- update debian/thunderbird.install.in
  * Do not exclude calendar translations from the source tarball, and repack
the lightning xpi with all available locales (LP: #545778)
- update debian/config/tarball.conf
- update debian/build/rules.mk
- update debian/rules

 -- Olivier Tilloy   Mon, 07 Oct 2019
10:03:16 +0200

** Changed in: thunderbird (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  xul-ext-lightning is only available in English

Status in One Hundred Papercuts:
  Invalid
Status in Mozilla Thunderbird:
  Invalid
Status in Ubuntu Translations:
  Invalid
Status in lightning-sunbird package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Xenial:
  Fix Released
Status in thunderbird source package in Bionic:
  Fix Released
Status in thunderbird source package in Disco:
  Fix Committed

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Change the user session language to other different than English.
  2. In Thunderbird, open the calendar

  EXPECTED BEHAVIOUR

  - The calendar interface to be in the session language.

  REAL BEHAVIOUR

  - The calendar is in English.

  RELEVANT DETAILS

  - None.

  **
   SOLUTION
  **

  WORK-AROUND

  - None known.

  FIX

  - .

  REGRESSION POTENTIAL

  - Since no code needs to be modified, the regression potential is very
  low.

  
   TECHNICAL INFO
  

  Binary package hint: lightning-extension

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/545778/+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 1846759] Re: Ubuntu's evolution-data-server package incompatible with gnome-calendar package

[Chris Graham]

Ergh, you're right. It is the other guy in the Gnome thread using 3.34,
not me. I should have checked my own version rather than running with
what was said in there.

I've now mentioned this on the Gnome issue tracker thread.

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

Title:
  Ubuntu's evolution-data-server package incompatible with gnome-
  calendar package

Status in gnome-calendar package in Ubuntu:
  Incomplete

Bug description:
  On reporting an issue in gnome-calendar, I was told "GNOME Calendar
  3.34 requires EDS 3.34 running in the host system.".  Ubuntu has 3.32.

  See:

  https://gitlab.gnome.org/GNOME/gnome-calendar/issues/464#note_617797

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-calendar 3.32.2-1~ubuntu19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  4 08:00:32 2019
  InstallationDate: Installed on 2019-07-31 (64 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: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2019-09-22T11:01:00.065291

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1846759/+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 1845471] Re: gnome-calendar won't start from Activities Overview

[Paul White]

Since I raised this report there's been an update to version 3.34.1-1.
Immediately after updating I confirmed that the calendar still would not
start. Now I find that the calendar starts every time so the problem
seems to be fixed.

I'll leave this to the other affected users to provide the requested
information if the calendar still doesn't start for them.

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

Title:
  gnome-calendar won't start from Activities Overview

Status in gnome-calendar package in Ubuntu:
  Incomplete

Bug description:
  During ISO testing (live-session) I found that I was unable to start
  gnome-calendar.

  Steps to reproduce:
  Display Activities Overview, search for and select "Calendar"

  Expected outcome:
  Application starts

  Actual outcome:
  Application doesn't start

  Workaround:
  Pin application icon to Ubuntu Dock or start from terminal

  Confirmation of issue:
  I can confirm this issue with a permanent installation on another machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-calendar 3.34.0-1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 26 10:36:08 2019
  InstallationDate: Installed on 2019-05-17 (131 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1845471/+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 1834495] Re: Calendar name is not persistent after log out (it changes back to default name)

[Sebastien Bacher]

Thank you for your bug report, could you also submit it to the software 
writters on
https://gitlab.gnome.org/GNOME/gnome-calendar/issues/ ?

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

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

Title:
  Calendar name is not persistent after log out (it changes back to
  default name)

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Steps to reproduce the bug:

  1. Add a Google or a Nextcloud account in gnome-calendar
  2. Activate the calendar component in the account
  3. Open gnome-calendar and go to Calendar Settings
  4. Choose a Google or a Nextcloud calendar
  5. Change the calendar name
  6. Go back, close the app and open it again
  7. The new name is still there
  8. Log out and log back in
  9. Check the calendar name
  10. It's back to the default name

  The new calendar name should always be persistent and does not change
  to the default name.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.28.2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 27 16:45:18 2019
  InstallationDate: Installed on 2018-11-29 (209 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1834495/+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 1843910] Re: cannot add public (unauthenticated) web ics calendar

[Sebastien Bacher]

Thank you for your bug report, could you also report the problem to the 
software writers on 
https://gitlab.gnome.org/GNOME/gnome-calendar/issues ?

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

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

Title:
  cannot add public (unauthenticated) web ics calendar

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  I am trying to import a public agenda in Gnome Calendar, for instance :
https://indico.math.cnrs.fr/export/categ/180.ics?from=-31d
  When adding this URL in the Gnome Calendar settings, I am asked for 
credentials which should not be needed (wget or Firefox download the ics file 
just fine without them).

  In fact, the same problem seems to have been already reported here :
  
https://askubuntu.com/questions/1100027/gnome-calendar-asks-credentials-for-public-ical
  Someone suggests to use evolution as a workaround, but IMO this is still a 
bug of Gnome Calendar which is the default calendar for Ubuntu 18.04...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.28.2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 13 16:12:25 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-09-04 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/zsh
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1843910/+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 1840423] Re: Gnome calendar add events spanning two days, and time of event is incorrect when setting specific time

[Sebastien Bacher]

Thank you for your bug report, could you also submit it to the software 
writters on
https://gitlab.gnome.org/GNOME/gnome-calendar/issues/ ?

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

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

Title:
  Gnome calendar add events spanning two days, and time of event is
  incorrect when setting specific time

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  When I add an event to my calendar (microsoft exchange via office 365)
  The event first spans over two days.

  Then when I change to a specific time, the time is wrong.

  I am in CEST, but it adds one hour to the time. If I correct the time,
  it goes back one hour too much. If I correct the time for a third
  time, it is correct

  https://www.youtube.com/watch?v=zjP5wMGar3I

  See my recording for the problem.

  I use ubuntu 19.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1840423/+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 1845471] Re: gnome-calendar won't start from Activities Overview

[Sebastien Bacher]

Thank you for your bug report, could you add your 'journalctl -b 0' log
after getting the issue?

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

** Changed in: gnome-calendar (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  gnome-calendar won't start from Activities Overview

Status in gnome-calendar package in Ubuntu:
  Incomplete

Bug description:
  During ISO testing (live-session) I found that I was unable to start
  gnome-calendar.

  Steps to reproduce:
  Display Activities Overview, search for and select "Calendar"

  Expected outcome:
  Application starts

  Actual outcome:
  Application doesn't start

  Workaround:
  Pin application icon to Ubuntu Dock or start from terminal

  Confirmation of issue:
  I can confirm this issue with a permanent installation on another machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-calendar 3.34.0-1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 26 10:36:08 2019
  InstallationDate: Installed on 2019-05-17 (131 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1845471/+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 1846541] Re: sigsegv in gtk_widget_get_scale_factor

[Sebastien Bacher]

Thank you for your bug report, what Ubuntu version and gnome-calendar
package are you using? Could you get a debug backtrace as described on
https://wiki.ubuntu.com/DebuggingProgramCrash

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

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

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

Title:
  sigsegv in gtk_widget_get_scale_factor

Status in gnome-calendar package in Ubuntu:
  Incomplete

Bug description:
  Occasionally when launching the calendar from the overview, it
  segfaults at startup. This does not seem to happen when launched from
  the terminal. Logs from journald:

  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Oct 03 11:37:50 pop-os 

[Desktop-packages] [Bug 1846759] Re: Ubuntu's evolution-data-server package incompatible with gnome-calendar package

[Sebastien Bacher]

Thank you for your bug report, but from your description
 Package: gnome-calendar 3.32.2-1~ubuntu19.04.1

You are using 3.32 which is what the 19.04 serie is providing, or are
you using the flatpak as mentioned in the upstream report? (in which
case it's a bug in the flatpak and not Ubuntu)

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

** Changed in: gnome-calendar (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Ubuntu's evolution-data-server package incompatible with gnome-
  calendar package

Status in gnome-calendar package in Ubuntu:
  Incomplete

Bug description:
  On reporting an issue in gnome-calendar, I was told "GNOME Calendar
  3.34 requires EDS 3.34 running in the host system.".  Ubuntu has 3.32.

  See:

  https://gitlab.gnome.org/GNOME/gnome-calendar/issues/464#note_617797

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-calendar 3.32.2-1~ubuntu19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  4 08:00:32 2019
  InstallationDate: Installed on 2019-07-31 (64 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: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2019-09-22T11:01:00.065291

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1846759/+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 1847069] Re: [snap] Chromium snap starts slowly

[chanath]

To compare,

~$ time ~/chromium-browser/chrome
[5072:5072:1008/212843.785778:ERROR:sandbox_linux.cc(369)] InitializeSandbox() 
called with multiple threads in process gpu-process.
[5072:5072:1008/212844.165025:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command

real0m5.087s
user0m6.032s
sys 0m1.318s

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

Title:
  [snap] Chromium snap starts slowly

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  The problem is shown here, https://discourse.ubuntu.com/t/call-for-
  testing-chromium-browser-deb-to-snap-transition/11179/141 more
  graphically.

  Chromium snap takes quite a while to start and doesn't carry the
  system theme, whereas the chromium-browser folder taken off the
  snap/chromium starts practically immediately.

  The libcanberra-gtk3-module is missing inside the snap, and cannot use
  the module in the system.

  The Chromium snap is 607.3 MB, while the standalone Chromium is 237.2
  MB, taken off the snap.

  Conclusion on Chromium snap on Ubuntu Eoan;
  Two bugs and a missing module
  1) Starts slowly,
  2) Cannot carry the system theme,
  3) Doesn't have libcanberra-gtk3-module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1847069/+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 1843733] Re: fftw3 ftbfs in eoan (armhf only)

[Sebastien Bacher]

Reported upstream on https://github.com/FFTW/fftw3/issues/182 , with
some luck they have an idea about the bug

** Bug watch added: github.com/FFTW/fftw3/issues #182
   https://github.com/FFTW/fftw3/issues/182

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

Title:
  fftw3 ftbfs in eoan (armhf only)

Status in fftw3 package in Ubuntu:
  Confirmed
Status in fftw3 source package in Eoan:
  Confirmed

Bug description:
  fftw3 ftbfs in eoan (armhf only).

  https://launchpadlibrarian.net/441265031/buildlog_ubuntu-eoan-
  armhf.fftw3_3.3.8-2_BUILDING.txt.gz

  ( cd tests ; /usr/bin/make smallcheck )
  make[1]: Entering directory '/<>/tests'
  perl -w ./check.pl -r -c=1 -v `pwd`/bench
  Executing "/<>/tests/bench --verbose=1   --verify 
'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify 
'//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' 
--verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' 
--verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 
'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304'"
  ok7e10x12bv29 1.71318e-07 1.44516e-06 2.00887e-07
  ik7e10x12bv29 1.66737e-07 1.44901e-06 1.76717e-07
  Segmentation fault (core dumped)
  FAILED /<>/tests/bench:  --verify 'ok7e10x12bv29' --verify 
'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' 
--verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' 
--verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify 
'//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 
'ofc2304' --verify 'ifc2304'
  make[1]: *** [Makefile:723: smallcheck] Error 1
  make[1]: Leaving directory '/<>/tests'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1843733/+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 1844944] Re: Ubuntu 19.10 switching users broken

[Sebastien Bacher]

Yes, that update is available in the standard archive now

** Changed in: gdm3 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Ubuntu 19.10 switching users broken

Status in gdm:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released

Bug description:
  I've performed an upgrade from Ubuntu 19.04 to 19.10 5 days ago by
  running the command "sudo do-release-upgrade". The upgrade went well,
  without errors. I've installed all updates to date (22 sept 2019). One
  thing seems broken since the upgrade to 19.10: it is not possible to
  switch users when using the Nouveau driver.

  Prerequisites:

  - Use Ubuntu 19.10
  - You need at least 2 users (e.g. user1 and user2)
  - The Nouveau drivers must be used

  Step to reproduce:

  - Start your computer
  - At the graphical login prompt, log in with user1: user1 is able to log in, 
its desktop is shown
  - While logged into the desktop of user1, choose "Switch user"
  - When back at the user selection screen, choose the profile of user2
  - Provide the password for user2 and attempt log in

  RESULT: the desktop of user2 is never shown. Instead, the lock screen
  is shown. After pressing [Enter] to hide the lock screen, the login
  prompt for user1 is displayed. On that screen, it is possible to press
  "Log in as another user" and provide the password for user2 again. A
  login attempt results again in the lock screen being displayed. it is
  never possible to login in as user2.

  NOTE 1: the same happens when user2 was the first to log in after a
  reboot of the system. User2 is able to log in, and user1 is then stuck
  in a login loop.

  NOTE 2: this bug doesn't happen when the proprietary NVidia driver is
  used (the version which can be installed via the Software & updates
  screen, version 340.107).

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1844944/+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 1847316] Re: gnome-calendar crashed with SIGSEGV in gdk_rgba_to_string()

[Sebastien Bacher]

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

** This bug is no longer a duplicate of private bug 1846292
** This bug has been marked a duplicate of bug 1847104
   
/usr/bin/gnome-calendar:11:gdk_rgba_to_string:process_sources:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist

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

Title:
  gnome-calendar crashed with SIGSEGV in gdk_rgba_to_string()

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  I installed the gnome-calendar package and have Google accounts
  syncing. I didn't take any particular action to cause the crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-calendar 3.34.1-1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  8 13:13:50 2019
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2019-10-08 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f7213d038bd :movsd  
0x18(%rdi),%xmm0
   PC (0x7f7213d038bd) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%xmm0" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-calendar
  StacktraceTop:
   gdk_rgba_to_string () from /lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-calendar crashed with SIGSEGV in gdk_rgba_to_string()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1847316/+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 1827842] [pulseaudio/disco] verification still needed

[Brian Murray]

The fix for this bug has been awaiting testing feedback in the -proposed
repository for disco for more than 90 days.  Please test this fix and
update the bug appropriately with the results.  In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed from the -proposed repository.

** Tags added: removal-candidate

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

Title:
  pulseaudio should not load module-x11-bell in gnome-shell

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Committed

Bug description:
  * Impact
  The package force load a bell sound which can conflicts with the user 
configuration

  * Test case
  - Enable a login sound in session
  - Login into a GNOME/Ubuntu session
  -> the configured sound should be played

  * Regression potential
  Try other desktop environments to make sure their login sound behaviour isn't 
changed, it shouldn't since the customization dropped was specific to the 
Ubuntu sound theme

  ---

  The package `pulseaudio` installs a startup script in 
`/etc/xdg/autostart/pulseaudio.desktop`,
  which itself runs `/usr/bin/start-pulseaudio-x11`,
  which loads a number of x11 related modules in `pulseaudio`.

  One of these modules is `module-x11-bell`,
  which makes `pulseaudio` play a sound each time a system bell is emitted
  (usually by terminal applications, such as bash or vim).

  This is redundant with gnome-shell, which is also able to handle the system 
bell
  (through the gsetting key `org.gnome.desktop.sound event-sounds`).

  The gnome system bell is directly configurable by the user (Settings > Sound),
  so it should be preferred over pulseaudio's own system bell.

  I suggest to patch the `/usr/bin/start-pulseaudio-x11`,
  to avoid loading `start-pulseaudio-x11` if it detects it is running in Gnome 
Shell
  (e.g. if GNOME_SHELL_SESSION_MODE is set).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1827842/+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 1843733] Re: fftw3 ftbfs in eoan (armhf only)

[Sebastien Bacher]

Trying to debug a bit on a canonistack instance

==5906== Command: ./bench --verify ofr108*118
==5906== 
==5906== Invalid write of size 8
==5906==at 0x49174A8: vst1_f32 (arm_neon.h:10876)
==5906==by 0x49174A8: ST (simd-neon.h:119)
==5906==by 0x49174A8: n1fv_9 (n1fv_9.c:230)
==5906==by 0x4884F4F: dobatch (direct.c:51)
==5906==by 0x48850B5: apply_buf (direct.c:87)
==5906==by 0x48869B1: fftwf_dft_solve (solve.c:29)
==5906==by 0x4882407: measure (timer.c:136)
==5906==by 0x4882407: fftwf_measure_execution_time (timer.c:159)
==5906==by 0x4880725: evaluate_plan (planner.c:460)
==5906==by 0x48808B9: search0 (planner.c:529)
==5906==by 0x48809B1: search (planner.c:600)
==5906==by 0x48809B1: mkplan (planner.c:711)
==5906==by 0x4880D2D: fftwf_mkplan_d (planner.c:970)
==5906==by 0x48B5A0F: mkplan (ct-hc2c.c:198)
==5906==by 0x48807E3: invoke_solver (planner.c:486)
==5906==by 0x48807E3: search0 (planner.c:529)
==5906==by 0x48809B1: search (planner.c:600)
==5906==by 0x48809B1: mkplan (planner.c:711)
==5906==  Address 0x96bafa8 is not stack'd, malloc'd or (recently) free'd
==5906== 
==5906== 
==5906== Process terminating with default action of signal 11 (SIGSEGV)
==5906==  Access not within mapped region at address 0x96BAFA8
==5906==at 0x49174A8: vst1_f32 (arm_neon.h:10876)
==5906==by 0x49174A8: ST (simd-neon.h:119)
==5906==by 0x49174A8: n1fv_9 (n1fv_9.c:230)
==5906==by 0x4884F4F: dobatch (direct.c:51)
==5906==by 0x48850B5: apply_buf (direct.c:87)
==5906==by 0x48869B1: fftwf_dft_solve (solve.c:29)
==5906==by 0x4882407: measure (timer.c:136)
==5906==by 0x4882407: fftwf_measure_execution_time (timer.c:159)
==5906==by 0x4880725: evaluate_plan (planner.c:460)
==5906==by 0x48808B9: search0 (planner.c:529)
==5906==by 0x48809B1: search (planner.c:600)
==5906==by 0x48809B1: mkplan (planner.c:711)
==5906==by 0x4880D2D: fftwf_mkplan_d (planner.c:970)
==5906==by 0x48B5A0F: mkplan (ct-hc2c.c:198)
==5906==by 0x48807E3: invoke_solver (planner.c:486)
==5906==by 0x48807E3: search0 (planner.c:529)
==5906==by 0x48809B1: search (planner.c:600)
==5906==by 0x48809B1: mkplan (planner.c:711)

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

Title:
  fftw3 ftbfs in eoan (armhf only)

Status in fftw3 package in Ubuntu:
  Confirmed
Status in fftw3 source package in Eoan:
  Confirmed

Bug description:
  fftw3 ftbfs in eoan (armhf only).

  https://launchpadlibrarian.net/441265031/buildlog_ubuntu-eoan-
  armhf.fftw3_3.3.8-2_BUILDING.txt.gz

  ( cd tests ; /usr/bin/make smallcheck )
  make[1]: Entering directory '/<>/tests'
  perl -w ./check.pl -r -c=1 -v `pwd`/bench
  Executing "/<>/tests/bench --verbose=1   --verify 
'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify 
'//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' 
--verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' 
--verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 
'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304'"
  ok7e10x12bv29 1.71318e-07 1.44516e-06 2.00887e-07
  ik7e10x12bv29 1.66737e-07 1.44901e-06 1.76717e-07
  Segmentation fault (core dumped)
  FAILED /<>/tests/bench:  --verify 'ok7e10x12bv29' --verify 
'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' 
--verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' 
--verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify 
'//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 
'ofc2304' --verify 'ifc2304'
  make[1]: *** [Makefile:723: smallcheck] Error 1
  make[1]: Leaving directory '/<>/tests'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1843733/+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 1847069] Re: [snap] Chromium snap starts slowly

[chanath]

Gtk-Message: 21:16:33.373: Failed to load module "canberra-gtk-module"
Gtk-Message: 21:16:33.463: Failed to load module "canberra-gtk-module"
[2727:2897:1008/211636.183693:ERROR:token_service_table.cc(140)] Failed to 
decrypt token for service AccountId-102562585832489293610
[2869:2869:1008/211637.607402:ERROR:sandbox_linux.cc(369)] InitializeSandbox() 
called with multiple threads in process gpu-process.
[2869:2869:1008/211641.021952:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
Slowest 10 exec calls during snap run:
  0.593s snap-update-ns
  1.130s /usr/lib/snapd/snap-confine
  1.472s /snap/chromium/861/bin/desktop-launch
  0.214s /usr/bin/dbus-send
  0.235s /snap/chromium/861/bin/chromium.launcher
  0.278s /usr/bin/dbus-send
  0.361s /usr/bin/xdg-settings
  20.135s /proc/self/exe
  28.398s /snap/chromium/861/usr/lib/chromium-browser/chrome
  20.416s /proc/self/exe
Total time: 31.631s

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

Title:
  [snap] Chromium snap starts slowly

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  The problem is shown here, https://discourse.ubuntu.com/t/call-for-
  testing-chromium-browser-deb-to-snap-transition/11179/141 more
  graphically.

  Chromium snap takes quite a while to start and doesn't carry the
  system theme, whereas the chromium-browser folder taken off the
  snap/chromium starts practically immediately.

  The libcanberra-gtk3-module is missing inside the snap, and cannot use
  the module in the system.

  The Chromium snap is 607.3 MB, while the standalone Chromium is 237.2
  MB, taken off the snap.

  Conclusion on Chromium snap on Ubuntu Eoan;
  Two bugs and a missing module
  1) Starts slowly,
  2) Cannot carry the system theme,
  3) Doesn't have libcanberra-gtk3-module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1847069/+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 1846776] Re: Renaming a desktop item causes the shell to hang

[Bug Watch Updater]

** Changed in: gnome-shell-extension-desktop-icons
   Status: New => Fix Released

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

Title:
  Renaming a desktop item causes the shell to hang

Status in gnome-shell-extension-desktop-icons:
  Fix Released
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  In Progress
Status in gnome-shell-extension-desktop-icons source package in Eoan:
  In Progress

Bug description:
  Right click on a desktop icon and rename it:
   - The shell will hang and there's no way to recover it

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1846776/+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 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME

[Ricardo]

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

Same problem from updating to Ubuntu 19.04

Gnome 3.32.1

#nvidia-smi
Tue Oct  8 20:12:52 2019   
+-+
| NVIDIA-SMI 435.21   Driver Version: 435.21   CUDA Version: 10.1 |
|---+--+--+
| GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute M. |
|===+==+==|
|   0  GeForce 840MOff  | :0A:00.0 Off |  N/A |
| N/A   45CP8N/A /  N/A |332MiB /  2004MiB |  8%  Default |
+---+--+--+

#uname -a
Linux rivendel 5.3.2-050302-generic #201910010731 SMP Tue Oct 1 07:33:48 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Resuming from sleep breaks desktop and lock screen background in GNOME

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  CPU: AMD Ryzen 5 1600
  MOBO: MSI B350M MORTAR
  GPU: NVIDIA GTX 1060

  Ubuntu version: 19.04
  Nvidia driver version: 418.56

  
  The system is updated with the latest updates as today, 28 March 2019

  As the title says, in Ubuntu 19.04 the GNOME lockscreen gets
  corrupted, and the GNOME desktop has blank background after resuming
  from standby/sleep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822179/+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 1843817] Re: Changing input method on webpages requires pressing twice the hotkey

[Yen-Yung Chang]

I have asked one of my friend for help and am waiting for him to
respond. In the meantime, I found I can use other gcin hotkeys normally,
e.g. changing half/full width, switching through different
languages,...etc, without the need of clicking twice but only not the
ctrl+space for switching between En and other gcin languages (in my
case, Mandarin). I suppose this is a useful clue that points to gcin as
the problem?

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

Title:
  Changing input method on webpages requires pressing twice the hotkey

Status in firefox package in Ubuntu:
  Incomplete
Status in gcin package in Ubuntu:
  New

Bug description:
  I'm finding a weird behaviour of changing input method "only on
  webpages." I need to hit hotkey (Ctrl+Space) twice to trigger the
  change if my courser is in text boxes "on the page." If the courser is
  in URL bar or search bar or anywhere firebox window itself, this
  phenomenon doesn't exist. I am using gcin 2.8.9 and is switching
  between English and traditional Chinese. Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 69.0+build2-0ubuntu0.18.04.1
  Uname: Linux 5.2.5-050205-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yenyung_chang   1727 F pulseaudio
  BuildID: 20190828152820
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 12 11:53:04 2019
  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 2019-03-26 (170 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.108 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:997
  PrefSources: prefs.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=69.0/20190828152820 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1843817/+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 1847316] Re: gnome-calendar crashed with SIGSEGV in gdk_rgba_to_string()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1846292, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1847316/+attachment/5295520/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1847316/+attachment/5295522/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1847316/+attachment/5295525/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1847316/+attachment/5295526/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1847316/+attachment/5295527/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1847316/+attachment/5295528/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1847316/+attachment/5295529/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1846292

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-calendar crashed with SIGSEGV in gdk_rgba_to_string()

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  I installed the gnome-calendar package and have Google accounts
  syncing. I didn't take any particular action to cause the crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-calendar 3.34.1-1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  8 13:13:50 2019
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2019-10-08 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f7213d038bd :movsd  
0x18(%rdi),%xmm0
   PC (0x7f7213d038bd) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%xmm0" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-calendar
  StacktraceTop:
   gdk_rgba_to_string () from /lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-calendar crashed with SIGSEGV in gdk_rgba_to_string()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1847316/+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 1647285] Re: SSL trust not system-wide

[Andreas Hasenack]

This isn't "just" a bug, it's a roadmap item in my view, as many
products are affected. It needs a spec, like in the fedora case. I agree
that it would be awesome to have this.

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

Title:
  SSL trust not system-wide

Status in ca-certificates package in Ubuntu:
  Confirmed
Status in nss package in Ubuntu:
  Confirmed
Status in p11-kit package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  When I install a corporate CA trust root with update-ca-certificates,
  it doesn't seem to work everywhere. Various things like Firefox,
  Evolution, Chrome, etc. all fail to trust the newly-installed trusted
  CA.

  This ought to work, and does on other distributions. In p11-kit there
  is a module p11-kit-trust.so which can be used as a drop-in
  replacement for NSS's own libnssckbi.so trust root module, but which
  reads from the system's configured trust setup instead of the hard-
  coded version.

  This allows us to install the corporate CAs just once, and then file a
  bug against any package that *doesn't* then trust them.

  See https://fedoraproject.org/wiki/Features/SharedSystemCertificates
  for some of the historical details from when this feature was first
  implemented, but this is all now supported upstream and not at all
  distribution-specific. There shouldn't be any significant work
  required; it's mostly just a case of configuring and building it to
  make use of this functionality. (With 'alternatives' to let you
  substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+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 1778946] Re: No dns resolution after closing a vpn/pptp connection

[Chris]

Can confirm. Work-around is to turn off WiFi and re-enable it.

Distributor ID: Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04
Codename:   bionic

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

Title:
  No dns resolution after closing a vpn/pptp connection

Status in ppp package in Ubuntu:
  Fix Released
Status in ppp package in Debian:
  New

Bug description:
  step to reproduce

  set a VPN connection configured to connect a Microsoft vpn server
  (pptp)

  internet acces is ok

  enable the vpn connection using the applet on the top right corner of
  the desktop

  internet still ok
  ping works

  disable the vpn connection

  ping doesn't works with a host but works if i specify an ip address

  ping: xx.net: Nom ou service inconnu

  As a workaround, i disable the ethernet link and re-enable it

  name resolution is now ok

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 27 18:09:30 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-06-03 (1484 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.0.254 dev eth0 proto dhcp metric 20100 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Connexion filaire 1  94806bba-1c68-46b6-87f4-a3aff6dd  
/org/freedesktop/NetworkManager/ActiveConnection/6 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  
WIFI-HW  WIFI WWAN-HW  WWAN
   running  1.10.6   connected (site only)  started  limited   enabled 
enabled  enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1778946/+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 1825741] Re: [upstream] Multiple instances of global menu entries

[Bug Watch Updater]

** Changed in: df-libreoffice
   Status: In Progress => Fix Released

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

Title:
  [upstream] Multiple instances  of global menu entries

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  I see 2 instances of each global menu entries.  It's cluttering up my
  top panel.

  This also happens in Plasma.

  Build ID: libreoffice-6.2.2.2-snap1

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1825741/+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 819796]

[Qa-admin-q]

Dear Christopher M. Penalver,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of
LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information 
from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to 
RESOLVED-WORKSFORME and leave a comment that includes the information from Help 
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular 
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a 
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your 
bug pertains to a feature added after 3.3) from 
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: 
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

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

Title:
  [Upstream] overline automatic color incorrect in pdf

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:3.3.3-1ubuntu2
Candidate: 1:3.3.3-1ubuntu2
Version table:
   *** 1:3.3.3-1ubuntu2 0
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  apt-cache policy acroread
  acroread:
Installed: 9.4.2-0natty1
Candidate: 9.4.2-0natty1
Version table:
   *** 9.4.2-0natty1 0
  500 http://archive.canonical.com/ubuntu/ natty/partner i386 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in LibreOffice Writer via the Terminal:

  cd ~/Desktop && wget -c
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/819796/+attachment/2251624/+files/overline%20color%20test.odt
  -O test.odt && lowriter -nologo test.odt

  File -> Export as PDF -> Export button and open in Adobe Reader is the
  overline above B remains red.

  4) What happens is it is black.

  WORKAROUND: Highlight B -> Secondary click -> click character... ->
  Font Effects tab -> change Overline color from Automatic to Light red
  -> OK button

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: libreoffice-core 1:3.3.2-1ubuntu5
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic-pae 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic-pae i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Tue Aug  2 08:34:40 2011
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to natty on 2011-05-30 (63 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/819796/+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 1825741]

[Libreoffice-commits]

Samuel Mehrbrodt committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/1c68ab312c5473ce642f75fc35a1edd6be187489

tdf#124391 Fix doubled menu in global menu

It will be available in 6.4.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

Title:
  [upstream] Multiple instances  of global menu entries

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  I see 2 instances of each global menu entries.  It's cluttering up my
  top panel.

  This also happens in Plasma.

  Build ID: libreoffice-6.2.2.2-snap1

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1825741/+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 1847247] Re: External dictionaries are not loaded

[Bug Watch Updater]

Launchpad has imported 1 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1587101.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-10-08T14:52:06+00:00 Olivier Tilloy wrote:

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
like Gecko) snap Chromium/77.0.3865.90 Chrome/77.0.3865.90 Safari/537.36

Steps to reproduce:

This bug was initially reported against the thunderbird 68.1.1 package
in Ubuntu
(https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1847247).

Thunderbird 68 is not able to make use of external hunspell dictionaries
provided by the distribution in /usr/lib/thunderbird/dictionaries.


Actual results:

This is a regression compared to thunderbird 60.9.0 and earlier, which
locates and uses hunspell dictionaries installed in
/usr/lib/thunderbird/dictionaries.

As far as I can tell, other distributions (such as Fedora 30) are
similarly affected.


Expected results:

It looks like https://hg.mozilla.org/mozilla-
unified/rev/8810007550b1fdeeae0f5d797c4a511818a57be7 is the revision
that removed this ability. The tracking bug with the rationale is
https://bugzilla.mozilla.org/show_bug.cgi?id=1457321, but it doesn't
mention anywhere the way Linux distributions install external hunspell
dictionaries and make them available to thunderbird. I wonder whether
this was an oversight, or whether that use case was indeed considered
but deemed unimportant when compared to the performance improvements
that this change brought.

Either way, would it be possible to consider adding back the ability to
load external dictionaries from the file system, maybe behind a setting
that would be off by default?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1847247/comments/2


** Changed in: thunderbird
   Status: Unknown => New

** Changed in: thunderbird
   Importance: Unknown => Medium

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

Title:
  External dictionaries are not loaded

Status in Mozilla Thunderbird:
  New
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu Eoan and most recent Thunderbird, the external Hunspell
  dictionaries are not available anymore on Thunderbird for spellcheck.

  The symlink is still in place:
  lrwxrwxrwx   1 root root20 dec 15  2017 dictionaries -> 
../../share/hunspell

  But data doesn't get loaded for some reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1847247/+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 1792300] Re: Speech Synthesis Not Working

[Lonnie Lee Best]

You don't need to go to any web page in particular to test this.

Open the browser and hit ctrl-shift-I and then type this into the console and 
press enter:
speechSynthesis.speak(new SpeechSynthesisUtterance("Testing 1 2 3"));

This works in Ubuntu Firefox and in MS Windows Chrome, but it does not
work in Ubuntu Chromium. This is true for the apt repository Chromium
and for the snap repository Chromium in Ubuntu.

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

Title:
  Speech Synthesis Not Working

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 16.04.5, Firefox supports Speech Synthesis by utilizing
  Text-To-Speech voices provided by default from the operating system.

  In Windows 10, both both Firefox and Chrome support Speech Synthesis
  by utilizing Text-To-Speech voices provided by default from the
  operating system.

  However,in Chromium 68 and 69, although the API is supported, Chromium
  cannot speak, because it doesn't seem to know how to load those Text-
  To-Speech voices that Firefox is successfully utilizing.

  Here's what users said at Ask Ubuntu, regarding the issue:
  https://askubuntu.com/questions/761975/

  For example, this page should speak the text is shows:
  http://www.lonniebest.com/CardTrick/

  The link above does not work in Chromium 69 on Ubuntu, however it does
  work in the following browser/os combinations:

  - Firefox (Ubuntu 16.04.5)
  - Chrome (Windows 10)
  - Firefox (Windows 10)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 69.0.3497.81-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 13 00:38:53 2018
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
   
'/usr/share/ubuntu:/usr/share/gnome:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2018-09-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  Load-Avg-1min: 0.51
  Load-Processes-Running-Percent:   0.1%
  MachineType: System76 Bonobo WS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=c57c4be3-fe0f-4162-804e-627e28920546 ro acpi_backlight=vendor quiet 
splash vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RSA5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Bonobo WS
  dmi.board.vendor: System76
  dmi.board.version: bonw13
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Bonobo WS
  dmi.product.version: bonw13
  dmi.sys.vendor: System76
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1792300/+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 1844797] Re: Need a Pipe-A quirk for 8086:5a85

[Thees Flatow]

Ping!  If this bug was filed against the wrong package, please point me
to the correct one.

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

Title:
  Need a Pipe-A quirk for 8086:5a85

Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  Following https://wiki.ubuntu.com/X/Quirks#Force_Pipe_A_Quirk I can
  confirm that the following hardware is affected by a blank screen
  after lid closing and reopening.

  Laptop: Lenovo 120s 11IAP

  $ lspci -vvnn | grep -A1 "VGA compat"
  00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:5a85] (rev 0b) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device [17aa:39fd]

  I can confirm that adding "ForceEnablePipeA" solves the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1844797/+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 1845548] Re: implicitclass crashed with SIGABRT in __malloc_assert()

[Launchpad Bug Tracker]

This bug was fixed in the package cups-filters - 1.25.7-0ubuntu1

---
cups-filters (1.25.7-0ubuntu1) eoan; urgency=medium

  * New upstream bug fix release
- Several bug fixes in pdftoraster (crash, monochrome jobs, ...,
  LP: #1845286)
- Fixes on printing intp queues generated by cups-browsed, especially
  also Apple Raster output (LP: #1845286)
- Crash in implicitclass backend (LP: #1845548, upstream issue #162).
- Added 1 new symbol to libcupsfilters1

 -- Till Kamppeter   Mon, 07 Oct 2019 16:38:58
+0200

** Changed in: cups-filters (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  implicitclass crashed with SIGABRT in __malloc_assert()

Status in cups-filters package in Ubuntu:
  Fix Released

Bug description:
  This crashed when attempting to print from firefox

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: cups-browsed 1.25.6-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Thu Sep 26 14:23:48 2019
  ExecutablePath: /usr/lib/cups/backend/implicitclass
  InstallationDate: Installed on 2019-09-11 (14 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lpstat: device for HP_OfficeJet_Pro_8720_BA2C6F_: 
implicitclass://HP_OfficeJet_Pro_8720_BA2C6F_/
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:c024 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 003: ID 04ca:7070 Lite-On Technology Corp. Integrated Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 4810CT0100
  Papersize: letter
  PpdFiles: HP_OfficeJet_Pro_8720_BA2C6F_: OfficeJet Pro 8720 - IPP Everywhere
  ProcCmdline: implicitclass://HP_OfficeJet_Pro_8720_BA2C6F_/ 2 ken VanDine\ 
Family\ Mail\ -\ Your\ Crucial.com\ Return\ Instructions 1 ColorModel=RGB\ 
cupsPrintQuality=Normal\ MediaType=Stationery\ number-up=1\ noCollate\ 
PageSize=Letter\ Duplex=None\ 
job-uuid=urn:uuid:011f0db5-151a-337b-78c0-2af327efcc22\ cups-browsed\ 
cups-browsed-dest-printer=\\"1\\\ ipps://HP1062E5BA2C6F.local:443/ipp/print\\\ 
raster\\\ 300dpi\\"\ job-originating-host-name=localhost\ 
date-time-at-creation=\ date-time-at-processing=\ time-at-creation=156958\ 
time-at-processing=156958\ print-quality=4
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic 
root=UUID=f9d6b524-56b4-475b-a2a2-97e20145f088 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups-filters
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0x7f9b1a1512d8 "(old_top == 
initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && 
prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)", 
file=file@entry=0x7f9b1a14d43f "malloc.c", line=line@entry=2379, 
function=function@entry=0x7f9b1a151a60 <__PRETTY_FUNCTION__.13032> "sysmalloc") 
at malloc.c:298
   sysmalloc (nb=nb@entry=384, av=av@entry=0x7f9b1a180b80 ) at 
malloc.c:2379
   _int_malloc (av=av@entry=0x7f9b1a180b80 , bytes=bytes@entry=375) 
at malloc.c:4141
   __GI___libc_malloc (bytes=bytes@entry=375) at malloc.c:3058
   __GI___strdup (s=0x55ed9340a050 "ColorModel=RGB cupsPrintQuality=Normal 
MediaType=Stationery number-up=1 noCollate PageSize=Letter Duplex=None 
job-uuid=urn:uuid:011f0db5-151a-337b-78c0-2af327efcc22 cups-browsed 
job-originating-host-n"...) at strdup.c:42
  Title: implicitclass crashed with SIGABRT in __malloc_assert()
  UpgradeStatus: Upgraded to eoan on 2019-09-12 (14 days ago)
  UserGroups:
   
  dmi.bios.date: 09/07/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0RET08L (0.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4810CT0100
  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: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0RET08L(0.08):bd09/07/2017:svnLENOVO:pn4810CT0100:pvrThinkPad133rdGen:rvnLENOVO:rn4810CT0100:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad 13 3rd Gen
  dmi.product.name: 4810CT0100
  dmi.product.sku: LENOVO_MT_4810_BU_Think_FM_ThinkPad 13 3rd Gen
  dmi.product.version: ThinkPad 13 3rd Gen
  dmi.sys.vendor: LENOVO
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1845548/+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 1845286] Re: pdftoraster crashed with SIGSEGV in convert8to16()

[Launchpad Bug Tracker]

This bug was fixed in the package cups-filters - 1.25.7-0ubuntu1

---
cups-filters (1.25.7-0ubuntu1) eoan; urgency=medium

  * New upstream bug fix release
- Several bug fixes in pdftoraster (crash, monochrome jobs, ...,
  LP: #1845286)
- Fixes on printing intp queues generated by cups-browsed, especially
  also Apple Raster output (LP: #1845286)
- Crash in implicitclass backend (LP: #1845548, upstream issue #162).
- Added 1 new symbol to libcupsfilters1

 -- Till Kamppeter   Mon, 07 Oct 2019 16:38:58
+0200

** Changed in: cups-filters (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  pdftoraster crashed with SIGSEGV in convert8to16()

Status in cups-filters package in Ubuntu:
  Fix Released

Bug description:
  Tried to print a pdf via an auto configured cups printer - pdftoraster
  crashed nothing was printed.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: cups-filters-core-drivers 1.25.6-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Wed Sep 25 06:49:10 2019
  ExecutablePath: /usr/lib/cups/filter/pdftoraster
  InstallationDate: Installed on 2018-09-06 (383 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lpstat:
   device for Brother_HL_L2300D_series_MacBook_de_Yasser: ///dev/null
   device for cespu_geral_MacBook_Air_de_Jo_o: ///dev/null
   device for Deskjet_3050A_J611_series_MacBook_Air: ///dev/null
   device for HP-Officejet-Pro-8620: 
dnssd://HP%20Officejet%20Pro%208620%20%5B794B2D%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-3863bb794b2d
   device for HP_Officejet_Pro_8620_794B2D_: 
implicitclass://HP_Officejet_Pro_8620_794B2D_/
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:7054 Lite-On Technology Corp. HP HD Camera
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteBook 840 G3
  Papersize: a4
  PpdFiles:
   HP-Officejet-Pro-8620: HP Officejet Pro 8620, driverless, cups-filters 1.25.4
   HP_Officejet_Pro_8620_794B2D_: HP Officejet Pro 8620, driverless, 
cups-filters 1.25.6
  ProcCmdline: implicitclass://HP_Officejet_Pro_8620_794B2D_/ 109 z003te9p 
Lauf\ gegen\ Krebs\ 2019.pdf 1 print-content-optimize=auto\ 
print-rendering-intent=auto\ ColorModel=DeviceGray\ Duplex=DuplexNoTumble\ 
MediaType=Stationery\ number-up=1\ PageSize=A4\ print-scaling=auto\ noCollate\ 
cupsPrintQuality=4\ job-uuid=urn:uuid:1166fa02-95cc-3560-7cd2-f256658917ad\ 
cups-browsed\ job-originating-host-name=localhost\ date-time-at-creation=\ 
date-time-at-processing=\ time-at-creation=1569386949\ 
time-at-processing=1569386949\ print-quality=4\ output-format=apple-raster\ 
Resolution=300dpi\ media-class=pwg\ page-logging=on
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic 
root=UUID=a8dfd19d-7ac8-43b7-bb4d-41c72407226f ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x55e344d74b9b:movzbl (%rdx),%r9d
   PC (0x55e344d74b9b) ok
   source "(%rdx)" (0x55e346c168af) not located in a known VMA region (needed 
readable region)!
   destination "%r9d" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: cups-filters
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x55e344d71b90, argc=6, argv=0x7ffcb779bdc8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffcb779bdb8) at ../csu/libc-start.c:308
   ?? ()
  Title: pdftoraster crashed with SIGSEGV in __libc_start_main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/01/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.13
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.74
  dmi.chassis.asset.tag: 5CG7060XN6
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.13:bd11/01/2016:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.74:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 840 G3
  dmi.product.sku: W0Q03EC#ABD
  dmi.sys.vendor: HP
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1845286/+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 1847285] Re: package gnome-keyring-pkcs11 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so', which is al

[Sebastien Bacher]

Thank you for your bug report. What did you upgrade exactly? The log
hints that gnome-keyring has been updated from 3.20.0-3ubuntu2 ,
which is the version which was in zesty and that it was updated to the
disco version. Did you try to dist-upgrade between those series? If so
that's not a supported upgrade path, you should have updated to the
bionic LTS first (which had the correct transitionnal support for that
file move between binaries)

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

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

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

Title:
  package gnome-keyring-pkcs11 (not installed) failed to
  install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkcs11
  /gnome-keyring-pkcs11.so', which is also in package libp11-kit-gnome-
  keyring:amd64 3.20.0-3ubuntu2

Status in gnome-keyring package in Ubuntu:
  Incomplete

Bug description:
  i just update as usual

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: gnome-keyring-pkcs11 (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Fri Oct 11 14:57:47 2019
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so', which is also in 
package libp11-kit-gnome-keyring:amd64 3.20.0-3ubuntu2
  Python3Details: /usr/bin/python3.5, Python 3.5.3, python3-minimal, 3.5.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions:
   dpkg 1.19.6ubuntu1
   apt  1.8.0
  SourcePackage: gnome-keyring
  Title: package gnome-keyring-pkcs11 (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so', which is also in 
package libp11-kit-gnome-keyring:amd64 3.20.0-3ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1847285/+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 1847285] [NEW] package gnome-keyring-pkcs11 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so', which is

[M. Khari Secario]

Public bug reported:

i just update as usual

ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: gnome-keyring-pkcs11 (not installed)
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
Date: Fri Oct 11 14:57:47 2019
ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so', which is also in 
package libp11-kit-gnome-keyring:amd64 3.20.0-3ubuntu2
Python3Details: /usr/bin/python3.5, Python 3.5.3, python3-minimal, 3.5.3-1
PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
RelatedPackageVersions:
 dpkg 1.19.6ubuntu1
 apt  1.8.0
SourcePackage: gnome-keyring
Title: package gnome-keyring-pkcs11 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so', 
which is also in package libp11-kit-gnome-keyring:amd64 3.20.0-3ubuntu2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package disco

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

Title:
  package gnome-keyring-pkcs11 (not installed) failed to
  install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkcs11
  /gnome-keyring-pkcs11.so', which is also in package libp11-kit-gnome-
  keyring:amd64 3.20.0-3ubuntu2

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  i just update as usual

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: gnome-keyring-pkcs11 (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Fri Oct 11 14:57:47 2019
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so', which is also in 
package libp11-kit-gnome-keyring:amd64 3.20.0-3ubuntu2
  Python3Details: /usr/bin/python3.5, Python 3.5.3, python3-minimal, 3.5.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions:
   dpkg 1.19.6ubuntu1
   apt  1.8.0
  SourcePackage: gnome-keyring
  Title: package gnome-keyring-pkcs11 (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so', which is also in 
package libp11-kit-gnome-keyring:amd64 3.20.0-3ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1847285/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1

[Timo Aaltonen]

no-one knows what to backport

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

Title:
  Kodi package crash after the update of libdrm-amdgpu1

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Greetings,

  The last update of libdrm-amdgpu1 caused a bug on Kodi package, making
  it to crash after loading any video or reproduce a black image.

  Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC

libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium

* Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111)

   -- Timo Aaltonen  Wed, 10 Apr 2019 13:54:06
  +0300

  
  Kodi gives this error:

  #3  0x7f47676c60aa in ?? () from 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
  #4  0x7f47676c5dd7 in ?? () from 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so

  Repeated several times

  #3  0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1
  #4  0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1

  Team-Kodi stated these errors are in relation to 'Not supported GPU
  drivers', when Kodi can't find these files.

  
  I've found the cause, and a temporary solution:

  This bug was caused after an update for the latest version of libdrm-
  amdgpu1 2.4.97-1ubuntu1~18.04.1

  So I grabbed the previous version from 
  https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/

  installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb

  and now Kodi returns.

  
  I created a bug report, the problem affects multiple users.

  https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828

  
  We have a PointRelease coming soon, would we have time to fix this package?

  Thank you for your assistance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1837170/+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 1847247] Re: External dictionaries are not loaded

[Olivier Tilloy]

I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1587101 to track
the bug upstream.

** Bug watch added: Mozilla Bugzilla #1587101
   https://bugzilla.mozilla.org/show_bug.cgi?id=1587101

** Also affects: thunderbird via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1587101
   Importance: Unknown
   Status: Unknown

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

Title:
  External dictionaries are not loaded

Status in Mozilla Thunderbird:
  Unknown
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu Eoan and most recent Thunderbird, the external Hunspell
  dictionaries are not available anymore on Thunderbird for spellcheck.

  The symlink is still in place:
  lrwxrwxrwx   1 root root20 dec 15  2017 dictionaries -> 
../../share/hunspell

  But data doesn't get loaded for some reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1847247/+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 1847247] Re: External dictionaries are not loaded

[Olivier Tilloy]

It seems the ability to load external hunspell dictionaries was removed
in https://hg.mozilla.org/mozilla-
unified/rev/8810007550b1fdeeae0f5d797c4a511818a57be7.

The tracking bug upstream is
https://bugzilla.mozilla.org/show_bug.cgi?id=1457321.

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

** Changed in: thunderbird (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

** Bug watch added: Mozilla Bugzilla #1457321
   https://bugzilla.mozilla.org/show_bug.cgi?id=1457321

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

Title:
  External dictionaries are not loaded

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu Eoan and most recent Thunderbird, the external Hunspell
  dictionaries are not available anymore on Thunderbird for spellcheck.

  The symlink is still in place:
  lrwxrwxrwx   1 root root20 dec 15  2017 dictionaries -> 
../../share/hunspell

  But data doesn't get loaded for some reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1847247/+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 1847044] Re: gnome-shell crashed with SIGSEGV in meta_output_kms_read_edid() from meta_monitor_manager_handle_get_resources() from ffi_call_unix64() from ffi_call() from g_cclo

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: New => Fix Released

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

Title:
  gnome-shell crashed with SIGSEGV in meta_output_kms_read_edid() from
  meta_monitor_manager_handle_get_resources() from ffi_call_unix64()
  from ffi_call() from g_cclosure_marshal_generic()

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1847044/+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 1846210] Re: gnome-control-center crashed with SIGSEGV in place_query_info_ready()

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-control-center -
1:3.34.1-1ubuntu1

---
gnome-control-center (1:3.34.1-1ubuntu1) eoan; urgency=medium

  * Merge with debian unstable. Remaining changes:
+ debian/control.in:
  - Depend on language-selector-gnome and whoopsie-preferences
  - Depend on instead of Recommend system-config-printer
  - Recommend ibus and ubuntu-system-service
  - Suggest instead of Recommend gnome-user-share, realmd and rygel
  - Build-Depend on dh-migrations and libwhoopsie-preferences-dev
  - Don't recommend libnss-myhostname since systemd-resolved handles this
functionality
  - Bump dep on g-s-d and schema
+ Split gnome-control-center-faces to a separate package so that it can be
  used by unity-control-center & recommend this
+ Install apport hook
+ debian/gnome-control-center-data.install:
  - Don't install gnome-control-center.pkla since we use
policykit-desktop-privileges instead
  - Install additional assets used by unity-control-center
+ debian/ubuntu-logo-icon.png, debian/source/include-binaries,
  debian/gnome-control-center-data.install: Include an Ubuntu logo
+ debian/gnome-control-center-data.links:
  - Link audio-speaker-center* to audio-speaker-mono* so that an
icon is shown in the test speaker panel.
+ debian/rules: Enable whoospie integration
+ Add migration script to transition from old user settings to new one.
+ debian/patches:
  - 52_region_language.patch:
 Adapt region panel to use Ubuntu style regions
  - 64_restore_terminal_keyboard_shortcut.patch
 Bring back terminal shortcut
  - 70_allow_sound_above_100.patch:
 Allow setting volume above 100% in the Ubuntu session
  - 71_ubuntu_dock_settings.patch
 Add Dock panel for Ubuntu session
  - 99_add_lock-on-suspend.patch
 Add option to lock on suspend
  - auto_quit_after_goa_add.patch
 Hide window after adding an online account from another app.
  - connectivity-switch.patch
 Add Connectivity Checking switch to Privacy panel
  - privacy-panel-whoopsie.patch
 Support Ubuntu's whoopsie service in the Privacy panel
  - ubuntu-default-height.patch:
 Ensure all items fit in sidebar without scrolling with Yaru theme
  - ubuntu-language-support.patch
 Add Language Support button to Region & Language panel to work around
  - ubuntu-legacy-notifications.patch
 Ubuntu ships compatibility names for .desktop that got renamed
 upstream, those use NoDisplay but the panel doesn't respect that key,
 skip known buggy entries for file-roller and nautilus
  - ubuntu-printer-support.patch
 Add Advanced Printer Settings button to work around missing printer
 sharing feature
  - ubuntu-region-langpack-install.patch:
 Check for missing language packs when loading region panel to pull
 in packs that aren't included with the installer
  - ubuntu-region-packagekit.patch
 Fix detection of installed language packs
  * debian/patches/online_accounts_segfault.patch:
- removed, the issue is fixed in the new version

gnome-control-center (1:3.34.1-1) unstable; urgency=medium

  * New upstream release
- Fix crash on clicking 'Search Locations' (lp: #1846210)

gnome-control-center (1:3.34.0.1-2) unstable; urgency=medium

  * Team upload.
  * Upload to unstable

 -- Sebastien Bacher   Mon, 07 Oct 2019 17:26:09
+0200

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

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

Title:
  gnome-control-center crashed with SIGSEGV in place_query_info_ready()

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  Open Settings => Search. Click on 'Search Locations' button, 
gnome-control-center window crashes.
  Ubuntu 19.10

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.0.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 15:21:38 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-09-11 (19 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
  ProcCmdline: gnome-control-center
  SegvAnalysis:
   Segfault happened at: 0x556a3c0c112d:mov0x40(%rax),%rdi
   PC (0x556a3c0c112d) ok
   source "0x40(%rax)" (0x0040) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  

[Desktop-packages] [Bug 1846776] Re: Renaming a desktop item causes the shell to hang

[Sebastien Bacher]

** Also affects: gnome-shell-extension-desktop-icons (Ubuntu Eoan)
   Importance: High
 Assignee: Marco Trevisan (Treviño) (3v1n0)
   Status: In Progress

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

Title:
  Renaming a desktop item causes the shell to hang

Status in gnome-shell-extension-desktop-icons:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  In Progress
Status in gnome-shell-extension-desktop-icons source package in Eoan:
  In Progress

Bug description:
  Right click on a desktop icon and rename it:
   - The shell will hang and there's no way to recover it

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1846776/+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 1847102] Re: Dragging icons around the dock only fully works once. After that they stick to the mouse pointer.

[Sebastien Bacher]

** Tags removed: rls-ee-incoming
** Tags added: rls-ee-notfixing

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

Title:
  Dragging icons around the dock only fully works once. After that they
  stick to the mouse pointer.

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

Bug description:
  The first time it seemed to work fine, then I stopped being able to
  drop the icon and had to hit escape.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell-extension-ubuntu-dock 66ubuntu19.10.2
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  7 15:29:20 2019
  InstallationDate: Installed on 2019-09-27 (10 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1847102/+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 1847102] Re: Dragging icons around the dock only fully works once. After that they stick to the mouse pointer.

[Treviño]

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

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

Title:
  Dragging icons around the dock only fully works once. After that they
  stick to the mouse pointer.

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

Bug description:
  The first time it seemed to work fine, then I stopped being able to
  drop the icon and had to hit escape.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell-extension-ubuntu-dock 66ubuntu19.10.2
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  7 15:29:20 2019
  InstallationDate: Installed on 2019-09-27 (10 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1847102/+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 1847102] Re: Dragging icons around the dock only fully works once. After that they stick to the mouse pointer.

[Sebastien Bacher]

Tagging notfixing because while annoying launcher reordering isn't the
most common action and esc is an easy enough workaround (also Marco said
he has a fix so it's likely to be resolved anyway)

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

Title:
  Dragging icons around the dock only fully works once. After that they
  stick to the mouse pointer.

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

Bug description:
  The first time it seemed to work fine, then I stopped being able to
  drop the icon and had to hit escape.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell-extension-ubuntu-dock 66ubuntu19.10.2
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  7 15:29:20 2019
  InstallationDate: Installed on 2019-09-27 (10 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1847102/+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 1846858] Re: Media keys stopped working

[Sebastien Bacher]

** Tags removed: rls-ee-incoming

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

Title:
  Media keys stopped working

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Media keys (volume keys or CTRL+Alt+T) stopped working on october 4th.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  5 07:49:58 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-07-15 (1907 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2018-03-24 (559 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846858/+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 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too

[Hui Wang]

According to the logs in the #1, there is no obvious errors.

Please open the gnome-sound-setting, then plug a headphone, does the
headphone shows up in the UI after you plug the headphone.

If a headphone shows up, then select that headphone from UI, and play
some sound to headphone, if there is no sound from headphone, please run
alsa-info and pactl list, then upload two logs to lp.

thx.

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

Title:
  [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio
  record at all too

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Any progress? Cannot hear anything nor record anything out my asrock
  fm2a75m-dgs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hh 1267 F pulseaudio
   /dev/snd/controlC0:  hh 1267 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Oct  6 09:27:53 2019
  InstallationDate: Installed on 2019-03-31 (188 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hh 1267 F pulseaudio
   /dev/snd/controlC0:  hh 1267 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-25T18:19:18.090642

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846930/+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 1845205] Re: Cannot submit crash reports from firefox' "this tab crashed" page

[Launchpad Bug Tracker]

** Branch linked: lp:~mozillateam/firefox/firefox.disco

** Branch linked: lp:~mozillateam/firefox/firefox.bionic

** Branch linked: lp:~mozillateam/firefox/firefox.xenial

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

Title:
  Cannot submit crash reports from firefox' "this tab crashed" page

Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  Steps to reproduce:

  - Launch firefox
  - Enter "about:crashcontent" in the URL bar
  - Upon hitting return, the tab should crash and display the "This tab just 
crashed" page
  - Ensure that the checkmark to send the crash report is ticked
  - Add a comment (anything will do, a non-empty comment ensures that the crash 
is accepted by Mozilla crash reporting back-end)
  - Click on "Restore this tab"
  - Go to the "about:crashes" page

  Expected behaviour:

  In the "about:crashes" page the crash is displayed among the submitted
  crash reports, showing that the crash report was indeed submitted
  correctly.

  Actual behaviour:

  The crash appears among the unsubmitted crashes.

  This bug is specific to the packaged version of Firefox that comes
  with Ubuntu. I've tried reproducing using Mozilla's builds and crash
  submission works correctly there. See this bug
  https://bugzilla.mozilla.org/show_bug.cgi?id=1583247 on Mozilla's
  tracker regarding this behaviour. In Mozilla we noticed the issue
  because we've started properly processing crash reports coming from
  Ubuntu and tab crashes were strangely few. Feel free to contact me
  directly at gsve...@mozilla.com about this issue since I'm in charge
  of Firefox crash reporting machinery.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1845205/+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 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf

[Laurent Bonnaud]

** Tags added: eoan

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

Title:
  wpasupplicant: unknown keys in no-mac-addr-change.conf

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  NetworkManager warns that no-mac-addr-change.conf contains unknown
  configuration directives:

  # journalctl | grep no-mac-addr-change
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] Read 
config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 
20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 
10-globally-managed-devices.conf, default-wifi-powersave-on.conf)
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'wifi.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'ethernet.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: wpasupplicant 2:2.6-21ubuntu3
  Uname: Linux 5.0.9-050009-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr 27 13:15:27 2019
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+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 1845205] Re: Cannot submit crash reports from firefox' "this tab crashed" page

[Launchpad Bug Tracker]

** Branch linked: lp:firefox/stable

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

Title:
  Cannot submit crash reports from firefox' "this tab crashed" page

Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  Steps to reproduce:

  - Launch firefox
  - Enter "about:crashcontent" in the URL bar
  - Upon hitting return, the tab should crash and display the "This tab just 
crashed" page
  - Ensure that the checkmark to send the crash report is ticked
  - Add a comment (anything will do, a non-empty comment ensures that the crash 
is accepted by Mozilla crash reporting back-end)
  - Click on "Restore this tab"
  - Go to the "about:crashes" page

  Expected behaviour:

  In the "about:crashes" page the crash is displayed among the submitted
  crash reports, showing that the crash report was indeed submitted
  correctly.

  Actual behaviour:

  The crash appears among the unsubmitted crashes.

  This bug is specific to the packaged version of Firefox that comes
  with Ubuntu. I've tried reproducing using Mozilla's builds and crash
  submission works correctly there. See this bug
  https://bugzilla.mozilla.org/show_bug.cgi?id=1583247 on Mozilla's
  tracker regarding this behaviour. In Mozilla we noticed the issue
  because we've started properly processing crash reports coming from
  Ubuntu and tab crashes were strangely few. Feel free to contact me
  directly at gsve...@mozilla.com about this issue since I'm in charge
  of Firefox crash reporting machinery.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1845205/+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 1845205] Re: Cannot submit crash reports from firefox' "this tab crashed" page

[Olivier Tilloy]

** Changed in: firefox (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Cannot submit crash reports from firefox' "this tab crashed" page

Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  Steps to reproduce:

  - Launch firefox
  - Enter "about:crashcontent" in the URL bar
  - Upon hitting return, the tab should crash and display the "This tab just 
crashed" page
  - Ensure that the checkmark to send the crash report is ticked
  - Add a comment (anything will do, a non-empty comment ensures that the crash 
is accepted by Mozilla crash reporting back-end)
  - Click on "Restore this tab"
  - Go to the "about:crashes" page

  Expected behaviour:

  In the "about:crashes" page the crash is displayed among the submitted
  crash reports, showing that the crash report was indeed submitted
  correctly.

  Actual behaviour:

  The crash appears among the unsubmitted crashes.

  This bug is specific to the packaged version of Firefox that comes
  with Ubuntu. I've tried reproducing using Mozilla's builds and crash
  submission works correctly there. See this bug
  https://bugzilla.mozilla.org/show_bug.cgi?id=1583247 on Mozilla's
  tracker regarding this behaviour. In Mozilla we noticed the issue
  because we've started properly processing crash reports coming from
  Ubuntu and tab crashes were strangely few. Feel free to contact me
  directly at gsve...@mozilla.com about this issue since I'm in charge
  of Firefox crash reporting machinery.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1845205/+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 1845205] Re: Cannot submit crash reports from firefox' "this tab crashed" page

[Olivier Tilloy]

I built test packages that include the minidump-analyzer executable, and
I can confirm that with those crash reports are now submitted as
expected.

Gabriele, please share the link to that bug on your side here.

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

Title:
  Cannot submit crash reports from firefox' "this tab crashed" page

Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  Steps to reproduce:

  - Launch firefox
  - Enter "about:crashcontent" in the URL bar
  - Upon hitting return, the tab should crash and display the "This tab just 
crashed" page
  - Ensure that the checkmark to send the crash report is ticked
  - Add a comment (anything will do, a non-empty comment ensures that the crash 
is accepted by Mozilla crash reporting back-end)
  - Click on "Restore this tab"
  - Go to the "about:crashes" page

  Expected behaviour:

  In the "about:crashes" page the crash is displayed among the submitted
  crash reports, showing that the crash report was indeed submitted
  correctly.

  Actual behaviour:

  The crash appears among the unsubmitted crashes.

  This bug is specific to the packaged version of Firefox that comes
  with Ubuntu. I've tried reproducing using Mozilla's builds and crash
  submission works correctly there. See this bug
  https://bugzilla.mozilla.org/show_bug.cgi?id=1583247 on Mozilla's
  tracker regarding this behaviour. In Mozilla we noticed the issue
  because we've started properly processing crash reports coming from
  Ubuntu and tab crashes were strangely few. Feel free to contact me
  directly at gsve...@mozilla.com about this issue since I'm in charge
  of Firefox crash reporting machinery.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1845205/+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 1847247] [NEW] External dictionaries are not loaded

[Jean-Louis Dupond]

Public bug reported:

On Ubuntu Eoan and most recent Thunderbird, the external Hunspell
dictionaries are not available anymore on Thunderbird for spellcheck.

The symlink is still in place:
lrwxrwxrwx   1 root root20 dec 15  2017 dictionaries -> 
../../share/hunspell

But data doesn't get loaded for some reason.

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

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

Title:
  External dictionaries are not loaded

Status in thunderbird package in Ubuntu:
  New

Bug description:
  On Ubuntu Eoan and most recent Thunderbird, the external Hunspell
  dictionaries are not available anymore on Thunderbird for spellcheck.

  The symlink is still in place:
  lrwxrwxrwx   1 root root20 dec 15  2017 dictionaries -> 
../../share/hunspell

  But data doesn't get loaded for some reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1847247/+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 1830416] Re: Firefox shows multiple master password prompts on startup when user has multiple home tabs that require passwords

[Olivier Tilloy]

Sorry for the lack of timely feedback Steve.
I just tested the scenario you describe in a fully up-to-date 18.04 virtual 
machine, and I am only getting one master password prompt.
Is this problem still affecting you with the latest firefox update?

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

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

Title:
  Firefox shows multiple master password prompts on startup when user
  has multiple home tabs that require passwords

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.04.2 LTS

  I have two URLs configured for Firefox startup.  They are for
  different sites.  Each one will go to a login page.  I have a master
  password configured in Firefox.  When I start Firefox, two tabs will
  open to the two URLs, and up until recently, I was prompted once for
  my master password.  Once I entered it, my credentials would auto-fill
  on both tabs as expected.  Today I noticed that on Firefox startup, I
  was getting two master password prompts.  Although entering the master
  password for one would suffice, it is annoying to have to close out
  the second one.  Also, the second one often pops up and steals focus
  from the first when I am entering the master password (depending on
  the relative page load times of the two tabs).

  I was running Firefox 66.0.5+build1-0ubuntu0.18.04.1 when I first
  noticed this.  I updated to 67.0+build2-0ubuntu0.18.04.1 and the
  problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 67.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BuildID: 20190517140819
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Fri May 24 12:09:21 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePlugins: Shockwave Flash - 
[HomeDir]/.mozilla/plugins/libflashplayer.so
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:1151
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-12-12 (527 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IpRoute:
   default via 10.55.12.1 dev enx9cebe8551508 proto dhcp metric 100 
   default via 10.55.216.1 dev wlp3s0 proto dhcp metric 600 
   10.55.12.0/23 dev enx9cebe8551508 proto kernel scope link src 10.55.13.57 
metric 100 
   10.55.216.0/21 dev wlp3s0 proto kernel scope link src 10.55.217.198 metric 
600
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1Plugins: Shockwave Flash - 
[HomeDir]/.mozilla/plugins/libflashplayer.so
  Profile1PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:1151
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 - LastVersion=67.0/20190517140819 (In use)
   Profile0 (Default) - LastVersion=67.0/20190517140819 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to bionic on 2018-10-30 (206 days ago)
  dmi.bios.date: 09/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.4
  dmi.board.name: 0FH6CJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: L05248
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.4:bd09/12/2017:svnDellInc.:pnLatitude5580:pvr:rvnDellInc.:rn0FH6CJ:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5580
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1830416/+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 1845205] Re: Cannot submit crash reports from firefox' "this tab crashed" page

[Gabriele Svelto]

Interesting, that shouldn't happen. The minidump-analyzer executable
greatly improves our crash telemetry but it's not strictly needed for
crash reporting. I'll file a bug on our side to fix that issue.

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

Title:
  Cannot submit crash reports from firefox' "this tab crashed" page

Status in firefox package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:

  - Launch firefox
  - Enter "about:crashcontent" in the URL bar
  - Upon hitting return, the tab should crash and display the "This tab just 
crashed" page
  - Ensure that the checkmark to send the crash report is ticked
  - Add a comment (anything will do, a non-empty comment ensures that the crash 
is accepted by Mozilla crash reporting back-end)
  - Click on "Restore this tab"
  - Go to the "about:crashes" page

  Expected behaviour:

  In the "about:crashes" page the crash is displayed among the submitted
  crash reports, showing that the crash report was indeed submitted
  correctly.

  Actual behaviour:

  The crash appears among the unsubmitted crashes.

  This bug is specific to the packaged version of Firefox that comes
  with Ubuntu. I've tried reproducing using Mozilla's builds and crash
  submission works correctly there. See this bug
  https://bugzilla.mozilla.org/show_bug.cgi?id=1583247 on Mozilla's
  tracker regarding this behaviour. In Mozilla we noticed the issue
  because we've started properly processing crash reports coming from
  Ubuntu and tab crashes were strangely few. Feel free to contact me
  directly at gsve...@mozilla.com about this issue since I'm in charge
  of Firefox crash reporting machinery.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1845205/+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 1831295] Re: Firefox freeze when I drag an URL address to a Nautilus window

[Olivier Tilloy]

Sorry for the lack of timely feedback J-Paul.
Are you still seeing the problem with the most recent firefox update?
I just tested in a fully up-to-date 19.04 virtual machine, and I cannot 
reproduce it myself.

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

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

Title:
  Firefox freeze when I drag an URL address to a Nautilus window

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  When a web page is displayed in Firefox, if you select the URL in the address 
bar and try to drag it to the desktop or a Nautilus window, it is not done.
  But, afterwards, the mouse cursor become a hand and nothing is more possible 
with Firefox : you cannot select something, see the menu...
  You can only kill the app.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: firefox 67.0+build2-0ubuntu0.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jpaul  2420 F pulseaudio
   /dev/snd/controlC0:  jpaul  2420 F pulseaudio
   /dev/snd/controlC2:  jpaul  2420 F pulseaudio
  BuildID: 20190517140251
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 31 23:21:34 2019
  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 2019-04-26 (35 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.0.254 dev wlp4s6 proto dhcp metric 600 
   169.254.0.0/16 dev wlp4s6 scope link metric 1000 
   192.168.0.0/24 dev wlp4s6 proto kernel scope link src 192.168.0.10 metric 600
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:1151
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=fr_FR:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=67.0/20190517140251 (In use)
  RelatedPackageVersions: adobe-flashplugin 1:20190514.1-0ubuntu0.19.04.1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: 970 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd08/05/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

Re: [Desktop-packages] [Bug 1846930] Re: [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio record at all too

[nicola]

None of them, I cannot also record anything, the alc662 rev 2 analog realtek 
audio device does not work at all 
Il lunedì 7 ottobre 2019, 06:25:41 CEST, Hui Wang  
ha scritto:  
 
 Do you mean the you can't hear sound from headphone or lineout jack?

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1846930

Title:
  [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio
  record at all too

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Any progress? Cannot hear anything nor record anything out my asrock
  fm2a75m-dgs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
  USER        PID ACCESS COMMAND
  /dev/snd/controlC1:  hh        1267 F pulseaudio
  /dev/snd/controlC0:  hh        1267 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Oct  6 09:27:53 2019
  InstallationDate: Installed on 2019-03-31 (188 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  ProcEnviron:
  LANGUAGE=it
  PATH=(custom, no user)
  XDG_RUNTIME_DIR=
  LANG=it_IT.UTF-8
  SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
  Symptom_DevicesInUse:
  USER        PID ACCESS COMMAND
  /dev/snd/controlC1:  hh        1267 F pulseaudio
  /dev/snd/controlC0:  hh        1267 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-04-25T18:19:18.090642

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846930/+subscriptions

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

Title:
  [HDA-Intel - HD-Audio Generic, playback] No sound at all nor audio
  record at all too

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Any progress? Cannot hear anything nor record anything out my asrock
  fm2a75m-dgs

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hh 1267 F pulseaudio
   /dev/snd/controlC0:  hh 1267 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Oct  6 09:27:53 2019
  InstallationDate: Installed on 2019-03-31 (188 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: GP107GL High Definition Audio Controller - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hh 1267 F pulseaudio
   /dev/snd/controlC0:  hh 1267 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HD-Audio Generic, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 

[Desktop-packages] [Bug 1843733] Re: fftw3 ftbfs in eoan (armhf only)

[Matthias Klose]

persists:
https://launchpad.net/ubuntu/+archive/test-rebuild-20190906/+build/17546506


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

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

Title:
  fftw3 ftbfs in eoan (armhf only)

Status in fftw3 package in Ubuntu:
  Confirmed
Status in fftw3 source package in Eoan:
  Confirmed

Bug description:
  fftw3 ftbfs in eoan (armhf only).

  https://launchpadlibrarian.net/441265031/buildlog_ubuntu-eoan-
  armhf.fftw3_3.3.8-2_BUILDING.txt.gz

  ( cd tests ; /usr/bin/make smallcheck )
  make[1]: Entering directory '/<>/tests'
  perl -w ./check.pl -r -c=1 -v `pwd`/bench
  Executing "/<>/tests/bench --verbose=1   --verify 
'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify 
'//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' 
--verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' 
--verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 
'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304'"
  ok7e10x12bv29 1.71318e-07 1.44516e-06 2.00887e-07
  ik7e10x12bv29 1.66737e-07 1.44901e-06 1.76717e-07
  Segmentation fault (core dumped)
  FAILED /<>/tests/bench:  --verify 'ok7e10x12bv29' --verify 
'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' 
--verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' 
--verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify 
'//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 
'ofc2304' --verify 'ifc2304'
  make[1]: *** [Makefile:723: smallcheck] Error 1
  make[1]: Leaving directory '/<>/tests'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1843733/+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 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation

[Diego]

Hello, Daniel. I've experienced it in 18.04 and 19.04 both with nvidia-390.129 
in a XPS with hybrid intel x nvidia.
I hope had contributed. If you need some thing let me know.

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

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend or
  hibernation

Status in GNOME Shell:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Invalid
Status in mutter source package in Disco:
  In Progress
Status in mutter source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  The Nvidia (Xorg) driver corrupts the desktop wallpaper (by design
  (1)) upon resuming from suspend. This creates a poor user experience
  and gives the impression of severe memory corruption.

  (1)
  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  [Test Case]

  0. Set up an Nvidia-only system using the proprietary Nvidia Xorg driver.
  1. Suspend and resume the machine.
  Expect: The wallpaper still looks like it did before suspending.

  [Regression Potential]

  Low. The exact same patch is in Gnome 3.34 (Ubuntu 19.10) already and
  has been used for a couple of months without issue.

  [Original Report]

  https://trello.com/c/i5hENxSO

  Every other wake from sleep presents a corrupted screen with no unlock
  app.  There's a dock and system menu on a black background with pixel
  garbage.  Some personal information in the dock's large window
  thumbnails.  Bitmap garbage flashes on the screen when interacting
  with anything.  Only workaround is doing another sleep-wake cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:4b:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 20 22:19:29 2018
  DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-11-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-12-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
  InstallationDate: Installed on 2018-10-28 (54 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: X99P-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 

[Desktop-packages] [Bug 1847092] Re: Sandboxing Chromium Snap without FireJail

[Olivier Tilloy]

The root filesystem that the chromium snap sees is the one provided by
the core18 snap.

Exceptions granted by the connected interfaces can be inspected by
reading the generated apparmor profile, stored at
/var/lib/snapd/apparmor/profiles/snap.chromium.chromium.

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

Title:
  Sandboxing Chromium Snap without FireJail

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  I'm a Firefox user who uses Chromium for certain google websites.

  I like to run Chromium in a sandbox so that the "Downloads" folder is
  the only file system location Chromium can see.

  In Ubuntu 19.04, I could achieve this with:
  sudo apt install chromium-browser firejail ; firejail chromium-browser

  In Ubuntu 19.10, Chromium is only offered as a snap package:
  https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1847092

  Firejail, doesn't work with Chromium's snap package installation:
  https://askubuntu.com/questions/1178995

  The snap installation's degree of isolation seems to be controlled by
  the developer of snap package.

  Since firejail no longer works for achieving this degree of isolation,
  I'm requesting that the Snap Package Maintainer (of Chromium), provide
  an alternative installation that only gives Chromium access to the
  "Downloads" folder exclusively.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  7 08:15:38 2019
  InstallationDate: Installed on 2019-10-06 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191001.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1847092/+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 1792300] Re: Chromium Speech Synthesis Not Working

[Olivier Tilloy]

I can confirm this doesn't work in chromium, neither snap (tested in
19.10) nor deb (tested in 18.04).

Note that with the deb, I'm seeing the following message:

INFO:CONSOLE(765) "speechSynthesis.speak() without user activation
is no longer allowed since M71, around December 2018. See
https://www.chromestatus.com/feature/5687444770914304 for more details"

Lonnie, your CardTrick page will need to be updated to speak only upon
user activation.

This isn't the root cause of the problem though, speech synthesis
doesn't work in chromium even if user activated.

** Summary changed:

- Chromium Speech Synthesis Not Working
+ Speech Synthesis Not Working

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Speech Synthesis Not Working

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 16.04.5, Firefox supports Speech Synthesis by utilizing
  Text-To-Speech voices provided by default from the operating system.

  In Windows 10, both both Firefox and Chrome support Speech Synthesis
  by utilizing Text-To-Speech voices provided by default from the
  operating system.

  However,in Chromium 68 and 69, although the API is supported, Chromium
  cannot speak, because it doesn't seem to know how to load those Text-
  To-Speech voices that Firefox is successfully utilizing.

  Here's what users said at Ask Ubuntu, regarding the issue:
  https://askubuntu.com/questions/761975/

  For example, this page should speak the text is shows:
  http://www.lonniebest.com/CardTrick/

  The link above does not work in Chromium 69 on Ubuntu, however it does
  work in the following browser/os combinations:

  - Firefox (Ubuntu 16.04.5)
  - Chrome (Windows 10)
  - Firefox (Windows 10)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 69.0.3497.81-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep 13 00:38:53 2018
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
   
'/usr/share/ubuntu:/usr/share/gnome:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2018-09-12 (0 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  Load-Avg-1min: 0.51
  Load-Processes-Running-Percent:   0.1%
  MachineType: System76 Bonobo WS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=c57c4be3-fe0f-4162-804e-627e28920546 ro acpi_backlight=vendor quiet 
splash vt.handoff=7
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RSA5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Bonobo WS
  dmi.board.vendor: System76
  dmi.board.version: bonw13
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA5:bd12/12/2017:svnSystem76:pnBonoboWS:pvrbonw13:rvnSystem76:rnBonoboWS:rvrbonw13:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Bonobo WS
  dmi.product.version: bonw13
  dmi.sys.vendor: System76
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1792300/+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 1843817] Re: Changing input method on webpages requires pressing twice the hotkey

[Olivier Tilloy]

Thanks. Do you know of other gcin/firefox users who experience the same
problem, or does it seems confined to your setup?

** Summary changed:

- Weird behavior of chaning input method on webpages
+ Changing input method on webpages requires pressing twice the hotkey

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

Title:
  Changing input method on webpages requires pressing twice the hotkey

Status in firefox package in Ubuntu:
  Incomplete
Status in gcin package in Ubuntu:
  New

Bug description:
  I'm finding a weird behaviour of changing input method "only on
  webpages." I need to hit hotkey (Ctrl+Space) twice to trigger the
  change if my courser is in text boxes "on the page." If the courser is
  in URL bar or search bar or anywhere firebox window itself, this
  phenomenon doesn't exist. I am using gcin 2.8.9 and is switching
  between English and traditional Chinese. Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 69.0+build2-0ubuntu0.18.04.1
  Uname: Linux 5.2.5-050205-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yenyung_chang   1727 F pulseaudio
  BuildID: 20190828152820
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 12 11:53:04 2019
  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 2019-03-26 (170 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.108 metric 
600
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:997
  PrefSources: prefs.js
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=69.0/20190828152820 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0KTW76
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9380
  dmi.product.sku: 08AF
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1843817/+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 1845205] Re: Cannot submit crash reports from firefox' "this tab crashed" page

[Olivier Tilloy]

** Changed in: firefox (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Cannot submit crash reports from firefox' "this tab crashed" page

Status in firefox package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:

  - Launch firefox
  - Enter "about:crashcontent" in the URL bar
  - Upon hitting return, the tab should crash and display the "This tab just 
crashed" page
  - Ensure that the checkmark to send the crash report is ticked
  - Add a comment (anything will do, a non-empty comment ensures that the crash 
is accepted by Mozilla crash reporting back-end)
  - Click on "Restore this tab"
  - Go to the "about:crashes" page

  Expected behaviour:

  In the "about:crashes" page the crash is displayed among the submitted
  crash reports, showing that the crash report was indeed submitted
  correctly.

  Actual behaviour:

  The crash appears among the unsubmitted crashes.

  This bug is specific to the packaged version of Firefox that comes
  with Ubuntu. I've tried reproducing using Mozilla's builds and crash
  submission works correctly there. See this bug
  https://bugzilla.mozilla.org/show_bug.cgi?id=1583247 on Mozilla's
  tracker regarding this behaviour. In Mozilla we noticed the issue
  because we've started properly processing crash reports coming from
  Ubuntu and tab crashes were strangely few. Feel free to contact me
  directly at gsve...@mozilla.com about this issue since I'm in charge
  of Firefox crash reporting machinery.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1845205/+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 1847021] Re: Cannot input Chinese if only "Chinese (Intelligent Pinyin)" is set

[Gunnar Hjalmarsson]

On 2019-10-08 09:35, Ping-Wu wrote:
> My experience is, ibus-libpinyin still has stability problems in 19.04.

Yeah, we did improve it significantly, but crashes still happen.

I see that soon after the release of 2.2.2, upstream reverted three
commits from 2017, and those reversals basically make up the difference
between 2.2.2 and 2.3.0. Maybe 2.3.0 is what we should have
backported... The simple reason why we didn't is that 2.3.0 was not yet
in Debian at the time of the backports.

@Peng Wu: Are you able to summarize the purpose of those reversals? Do
they, as I'm implying, make ibus-libpinyin more stable and prevent
certain crash types?

> The dictionary built in conjunction with libpinyin 2.2 cannot be ported
> to version 2.3.

If that's the case, those reversals wouldn't be suitable for a stable
release update.

Let's hope that this IM has matured in 19.10 and will keep being stable
in 20.04.

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

Title:
  Cannot input Chinese if only "Chinese (Intelligent Pinyin)" is set

Status in ibus-libpinyin package in Ubuntu:
  Invalid

Bug description:
  See also https://github.com/libpinyin/ibus-libpinyin/issues/184

  Ubuntu 19.04. If I only install "Chinese (Intelligent Pinyin)", after
  pressing 'super+space' input is switched to Pinyin (can be seen from
  the icon on system bar). However it still input English directly. Even
  if I tried 'shift' button it's still the same.

  If I install "Chinese (Pinyin)" it works all perfect. If I install
  both "Chinese (Pinyin)" and "Chinese (Intelligent Pinyin)", both
  works.

  So, seems something is missing? Something required by Intelligent
  Pinyin but only installed with Pinyin?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ibus-libpinyin 1.11.0-1ubuntu0.19.04
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  7 17:24:17 2019
  InstallationDate: Installed on 2018-06-07 (487 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: ibus-libpinyin
  UpgradeStatus: Upgraded to disco on 2019-09-30 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1847021/+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 1845205] Re: Cannot submit crash reports from firefox' "this tab crashed" page

[Olivier Tilloy]

It appears crashes are not submitted because the minidump-analyzer
executable is missing.

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

Title:
  Cannot submit crash reports from firefox' "this tab crashed" page

Status in firefox package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:

  - Launch firefox
  - Enter "about:crashcontent" in the URL bar
  - Upon hitting return, the tab should crash and display the "This tab just 
crashed" page
  - Ensure that the checkmark to send the crash report is ticked
  - Add a comment (anything will do, a non-empty comment ensures that the crash 
is accepted by Mozilla crash reporting back-end)
  - Click on "Restore this tab"
  - Go to the "about:crashes" page

  Expected behaviour:

  In the "about:crashes" page the crash is displayed among the submitted
  crash reports, showing that the crash report was indeed submitted
  correctly.

  Actual behaviour:

  The crash appears among the unsubmitted crashes.

  This bug is specific to the packaged version of Firefox that comes
  with Ubuntu. I've tried reproducing using Mozilla's builds and crash
  submission works correctly there. See this bug
  https://bugzilla.mozilla.org/show_bug.cgi?id=1583247 on Mozilla's
  tracker regarding this behaviour. In Mozilla we noticed the issue
  because we've started properly processing crash reports coming from
  Ubuntu and tab crashes were strangely few. Feel free to contact me
  directly at gsve...@mozilla.com about this issue since I'm in charge
  of Firefox crash reporting machinery.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1845205/+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 1847222] [NEW] serverX crashes randomly

[VinsS]

Public bug reported:

Crash of X11 and after 0.5 to 2 seconds Ubuntu shutdown.

This appears randomly, the system journal says nothing at this moment
and there's no report in /var/crash

The .xsession-errors.old contains often the line: 
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
  after 33 requests (33 known processed) with 0 events remaining.
Gdk-Message: 01:16:44.392: mate-screensaver: Fatal IO error 11 (Ressource 
temporairement non disponible) on X server :0.

Note: mate-screensaver is just an example.

Configuration:
Ubuntu 18-04.3 LTS 64 bytes
Environment Mate

vincent@djoliba:~$ lspci
00:00.0 Host bridge: Intel Corporation 82Q963/Q965 Memory Controller Hub (rev 
02)
00:02.0 VGA compatible controller: Intel Corporation 82Q963/Q965 Integrated 
Graphics Controller (rev 02)
00:03.0 Communication controller: Intel Corporation 82Q963/Q965 HECI Controller 
(rev 02)
00:03.2 IDE interface: Intel Corporation 82Q963/Q965 PT IDER Controller (rev 02)
00:03.3 Serial controller: Intel Corporation 82Q963/Q965 KT Controller (rev 02)
00:19.0 Ethernet controller: Intel Corporation 82566DM Gigabit Network 
Connection (rev 02)
00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #4 (rev 02)
00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI 
Controller #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio 
Controller (rev 02)
00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #3 (rev 02)
00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI 
Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev f2)
00:1f.0 ISA bridge: Intel Corporation 82801HO (ICH8DO) LPC Interface Controller 
(rev 02)
00:1f.2 IDE interface: Intel Corporation 82801H (ICH8 Family) 4 port SATA 
Controller [IDE mode] (rev 02)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 02)
00:1f.5 IDE interface: Intel Corporation 82801HR/HO/HH (ICH8R/DO/DH) 2 port 
SATA Controller [IDE mode] (rev 02)

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

** Attachment added: "xsession-error_08_10_19"
   
https://bugs.launchpad.net/bugs/1847222/+attachment/5295376/+files/xsession-error_08_10_19

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

Title:
  serverX crashes randomly

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Crash of X11 and after 0.5 to 2 seconds Ubuntu shutdown.

  This appears randomly, the system journal says nothing at this moment
  and there's no report in /var/crash

  The .xsession-errors.old contains often the line: 
  XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 33 requests (33 known processed) with 0 events remaining.
  Gdk-Message: 01:16:44.392: mate-screensaver: Fatal IO error 11 (Ressource 
temporairement non disponible) on X server :0.

  Note: mate-screensaver is just an example.

  Configuration:
  Ubuntu 18-04.3 LTS 64 bytes
  Environment Mate

  vincent@djoliba:~$ lspci
  00:00.0 Host bridge: Intel Corporation 82Q963/Q965 Memory Controller Hub (rev 
02)
  00:02.0 VGA compatible controller: Intel Corporation 82Q963/Q965 Integrated 
Graphics Controller (rev 02)
  00:03.0 Communication controller: Intel Corporation 82Q963/Q965 HECI 
Controller (rev 02)
  00:03.2 IDE interface: Intel Corporation 82Q963/Q965 PT IDER Controller (rev 
02)
  00:03.3 Serial controller: Intel Corporation 82Q963/Q965 KT Controller (rev 
02)
  00:19.0 Ethernet controller: Intel Corporation 82566DM Gigabit Network 
Connection (rev 02)
  00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #4 (rev 02)
  00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI 
Controller #2 (rev 02)
  00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio 
Controller (rev 02)
  00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #1 (rev 02)
  00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #2 (rev 02)
  00:1d.2 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #3 (rev 02)
  00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI 
Controller #1 (rev 02)
  00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev f2)
  00:1f.0 ISA bridge: Intel Corporation 82801HO (ICH8DO) LPC Interface 
Controller (rev 02)
  00:1f.2 IDE interface: Intel Corporation 82801H (ICH8 Family) 4 port SATA 
Controller [IDE mode] (rev 02)
  00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus 

[Desktop-packages] [Bug 1847219] Re: HDMI audio lost function after the dGPU did runtime suspend. (AMD RX 580)

[Leon Liao]

There is a workaround solution to avoid this bug. 
It is to disable the amdgpu runtime suspend.
Just add amdpug.runpm=0 on the kernel command line.

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

Title:
  HDMI audio lost function after the dGPU did runtime suspend. (AMD RX
  580)

Status in OEM Priority Project:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  On Dell Precision 7740, after installed amdgpu-pro 19.10-793418, the
  HDMI audio will lose function after the dGPU did runtime suspend.

  How to check the AMD dGPU is in runtime suspend:
   $ lspci -s 01:00.0 -xxvv
  When the AMD dGPU is in runtime suspend, all of the registers will be 0xf.

  Release: 18.04 LTS
  kernel: 4.15.0-1037-oem
  amdgpu-pro: 19.10-793418

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1847219/+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 1847219] Re: HDMI audio lost function after the dGPU did runtime suspend. (AMD RX 580)

[Leon Liao]

There is a workaround solution to avoid this bug.
It is to disable the amdgpu runtime suspend.
Just add amdgpu.runpm=0 on the kernel command line.

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

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

Title:
  HDMI audio lost function after the dGPU did runtime suspend. (AMD RX
  580)

Status in OEM Priority Project:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  On Dell Precision 7740, after installed amdgpu-pro 19.10-793418, the
  HDMI audio will lose function after the dGPU did runtime suspend.

  How to check the AMD dGPU is in runtime suspend:
   $ lspci -s 01:00.0 -xxvv
  When the AMD dGPU is in runtime suspend, all of the registers will be 0xf.

  Release: 18.04 LTS
  kernel: 4.15.0-1037-oem
  amdgpu-pro: 19.10-793418

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1847219/+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 1847219] [NEW] HDMI audio lost function after the dGPU did runtime suspend. (AMD RX 580)

[Leon Liao]

Public bug reported:

On Dell Precision 7740, after installed amdgpu-pro 19.10-793418, the
HDMI audio will lose function after the dGPU did runtime suspend.

How to check the AMD dGPU is in runtime suspend:
 $ lspci -s 01:00.0 -xxvv
When the AMD dGPU is in runtime suspend, all of the registers will be 0xf.

Release: 18.04 LTS
kernel: 4.15.0-1037-oem
amdgpu-pro: 19.10-793418

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

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

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

Title:
  HDMI audio lost function after the dGPU did runtime suspend. (AMD RX
  580)

Status in OEM Priority Project:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  On Dell Precision 7740, after installed amdgpu-pro 19.10-793418, the
  HDMI audio will lose function after the dGPU did runtime suspend.

  How to check the AMD dGPU is in runtime suspend:
   $ lspci -s 01:00.0 -xxvv
  When the AMD dGPU is in runtime suspend, all of the registers will be 0xf.

  Release: 18.04 LTS
  kernel: 4.15.0-1037-oem
  amdgpu-pro: 19.10-793418

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1847219/+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 1828790] Re: On a Wyse system, if Intel DP is connected before the AMD one, there's a 50% chance the AMD one would have no output

[Timo Aaltonen]

https://bugs.freedesktop.org/show_bug.cgi?id=101998

** Bug watch added: freedesktop.org Bugzilla #101998
   https://bugs.freedesktop.org/show_bug.cgi?id=101998

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

Title:
  On a Wyse system, if Intel DP is connected before the AMD one, there's
  a 50% chance the AMD one would have no output

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server source package in Xenial:
  Won't Fix
Status in xorg-server-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Bionic:
  Triaged
Status in xorg-server-hwe-16.04 source package in Bionic:
  Invalid

Bug description:
  Summary:
  On extended SKU (AMD SKU), boot to OS with monitor connecting to Intel DP, 
then connect another monitor to AMD DP, there is a 50% chance AMD DP has no 
video output to monitor.

  Step to reproduce:
  1. Attached a 2k/4K monitor to Intel UMA DP port.
  2. Power on system and boot to desktop.
  3. Attach another 2k/4K monitor to AMD Graphics DP port.

  Expect result:
  Both monitors can display correctly

  Actually result:
  AMD DP monitor will be black screen. (Intel DP output still normal)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1828790/+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 1828790] Re: On a Wyse system, if Intel DP is connected before the AMD one, there's a 50% chance the AMD one would have no output

[Timo Aaltonen]

cd19a752f8bbc6c modesetting: code refactor for PRIME sync

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

Title:
  On a Wyse system, if Intel DP is connected before the AMD one, there's
  a 50% chance the AMD one would have no output

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server source package in Xenial:
  Won't Fix
Status in xorg-server-hwe-16.04 source package in Xenial:
  New
Status in xorg-server source package in Bionic:
  Triaged
Status in xorg-server-hwe-16.04 source package in Bionic:
  Invalid

Bug description:
  Summary:
  On extended SKU (AMD SKU), boot to OS with monitor connecting to Intel DP, 
then connect another monitor to AMD DP, there is a 50% chance AMD DP has no 
video output to monitor.

  Step to reproduce:
  1. Attached a 2k/4K monitor to Intel UMA DP port.
  2. Power on system and boot to desktop.
  3. Attach another 2k/4K monitor to AMD Graphics DP port.

  Expect result:
  Both monitors can display correctly

  Actually result:
  AMD DP monitor will be black screen. (Intel DP output still normal)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1828790/+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 1847190] Re: kubectl install : error: snap "kubectl" requires classic confinement which is only available on classic systems

[Jayashree]

Ok if I want to install kubectl or other classic snaps, what I need to do??
Any solution?

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

Title:
  kubectl install : error: snap "kubectl" requires classic confinement
  which is only available on classic systems

Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  Hi,

  I am trying to install kubernetes using the command: "sudo snap
  install kubectl --classic"

  But I am getting error and not able to install "snap "kubectl"
  requires classic confinement which is only available on classic
  systems"

  Can you please help in resolving this.

  snap version:
  
  admin@localhost:~$ snap version
  snap2.41
  snapd   2.41
  series  16
  kernel  4.4.0-164-generic

  
  admin@localhost:~$ sudo snap install kubectl --classic
  error: snap "kubectl" requires classic confinement which is only available on 
classic systems
  admin@localhost:~$ sudo snap install kubectl
  error: snap "kubectl" requires classic confinement which is only available on 
classic systems
  admin@localhost:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1847190/+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 1843652] Re: The bootmenu for zfs based Ubuntu does partly not work

[Sebastien Bacher]

the issue there doesn't have anything to do with the desktop login
screen though and there seems to be no real/concrete bug, best to use
discourse for discussions and suggestions, closing this ticket

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

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

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

Title:
  The bootmenu for zfs based Ubuntu does partly not work

Status in gdm3 package in Ubuntu:
  Invalid

Bug description:
  I had a triple boot since April:
  - Ubuntu 19.04 on ext4
  - Ubuntu Mate 19.04 on zfs
  - Xubuntu 19.04 on zfs

  Each zfs based system is stored completely in its own dataset, all folders 
are in that dataset; var; usr; home and all others.
  I have upgraded all systems to 19.10 and it went reasonably well, but I 
produced a few bug reports for some minor errors or typical transition 
problems. I did reinstall Ubuntu 19.10 on ext4 to solve one of those transition 
issues.

  All systems work fine now and I can boot all from Linux 5.2.

  Since the Software-Updater does not work anymore, I had to do the updates 
using apt in the terminal, but I created two snapshots for both zfs systems one 
190908 and one 190911.
  After running update-grub and grub-install those snapshots appear in the boot 
menu, hurrah!

  However except the main Linux 5.2 one for each OS, none of the menu entries 
is working:
  - The memory test ends up with a blank screen and nothing seems to happen. 
That entry has been added by the main zfs based system;
  - The history entries tell me "wrong dnode type" and "the correct kernel must 
be loaded first" and then it returns to the boot menu;
  - The advanced entries
  Both Linux 5.2 and 5.0 recovery modes stop after loading the RAM disk. The 
system hangs, but the disk light blinks each 5 seconds.

  Linux 5.0 normal mode says: it will not load due an incompatibility with the 
datapool. That happens because I decided to upgrade the datapool itself.
  In the release notes you need a strong warning about the consequences of 
updating the datapool!! Also during upgrading dual or multi boot systems. I did 
run into problems with it; even when I initially only updated the pool with the 
data and left the pool with systems and VMs unchanged.
  The last pool (systems and VMs) has been updated, when I completed the 
upgrade of the systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1843652/+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 1843659] Re: No unique names in the bootmenu created on ZFS based system

[Sebastien Bacher]

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

** Changed in: grub (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  No unique names in the bootmenu created on ZFS based system

Status in grub package in Ubuntu:
  New

Bug description:
I have a triple boot:
- Ubuntu 19.10 on ext4
- Ubuntu Mate 19.10 on zfs
- Xubuntu 19.10 on zfs

  All names for those 3 system in the boot menus are the same, which is
  confusing. Only the ext4 system is recognizable because the system
  adds "on sda1". Didier Roche did explain in the "Ubuntu Community Hub]
  [Desktop] Enhancing our ZFS support on Ubuntu 19.10 - an
  introduction", that you considered to add a version number. Then my
  boot menu would contain 3 times "Ubuntu 19.10". If you add the Ubuntu
  flavor it would be more useful, one entry would look like "Xubuntu
  19.10".

  However on e.g. my desktop I will have two times Ubuntu 19.10, once with 
Virtualbox and once with QEMU/KVM, so even flavor and version would still be 
insufficient. Other people might want to reserve a OS exclusively for Banking 
in addition to an OS for Office Work. 
  So I propose to add instead of distro nams and version; the hostname or the 
dataset name to the grub menu entry to give the user a way to create 
recognizable names in that menu. Dataset name would be ZFS specific, while 
hostname will be useful for ext4, btrfs and others too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub/+bug/1843659/+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 1846858] Re: Media keys stopped working

[Jean-Baptiste Lallement]

The problem seems to have fixed itself. Leaving incomplete just in case
it happens again and let it expire.

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

Title:
  Media keys stopped working

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Media keys (volume keys or CTRL+Alt+T) stopped working on october 4th.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  5 07:49:58 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-07-15 (1907 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2018-03-24 (559 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846858/+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 1844422] Re: WPA3-SAE support

[Sebastien Bacher]

Those fixes are in 1.20.4 which has been uploaded/is in the review
queue, unsubscribing sponsors

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

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  WPA3-SAE support

Status in gnome-shell package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  After some user feedback WPA3 support for NetworkManager has been
  finalized upstream:

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85

  At this time NetworkManager will not associate with Wifi-networks using WPA3.
  Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with 
NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1.

  It would be great if the aforementioned commits where backported to
  Eoan before release, so that Eoan based systems will associate with
  WiFi-networks using WPA3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+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 545778] Re: xul-ext-lightning is only available in English

[Peter]

Ok. Great! Thanks a lot.

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

Title:
  xul-ext-lightning is only available in English

Status in One Hundred Papercuts:
  Invalid
Status in Mozilla Thunderbird:
  Invalid
Status in Ubuntu Translations:
  Invalid
Status in lightning-sunbird package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Xenial:
  Fix Committed
Status in thunderbird source package in Bionic:
  Fix Committed
Status in thunderbird source package in Disco:
  Fix Committed

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Change the user session language to other different than English.
  2. In Thunderbird, open the calendar

  EXPECTED BEHAVIOUR

  - The calendar interface to be in the session language.

  REAL BEHAVIOUR

  - The calendar is in English.

  RELEVANT DETAILS

  - None.

  **
   SOLUTION
  **

  WORK-AROUND

  - None known.

  FIX

  - .

  REGRESSION POTENTIAL

  - Since no code needs to be modified, the regression potential is very
  low.

  
   TECHNICAL INFO
  

  Binary package hint: lightning-extension

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/545778/+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 1711538] Re: Tap-to-click does not work on the GDM login screen

[Bug Watch Updater]

Launchpad has imported 3 comments from the remote bug at
https://bugzilla.gnome.org/show_bug.cgi?id=694304.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-02-20T20:14:53+00:00 Diazbastian wrote:

I introduced this bug in fedora,
(https://bugzilla.redhat.com/show_bug.cgi?id=912886) and I've seen other
distros that use GNOME with this capability enabled by default, but
suggested I leave the bug in GNOME Bugzilla.

As I write in the fedora bug left as is customary for this ability (tap
to click) is enabled by default in other systems (OS X, Windows and
other linux distros). This leaves the feeling that something is not
working.

I suggest that this capability is enabled by default.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1711538/comments/0


On 2013-05-24T04:17:58+00:00 Diazbastian wrote:

I have in mind that this idea was discussed along with other bug 651134
, however, not clear to me its not included as default feature.

I hope they can discuss this idea for Gnome 3.10.


- Contrary to what I said in the comment above, OS X computers do not 
necessarily have this feature enabled by default, but consider that Apple has a 
grip on your hardware and how this is controlled.

- It may be an argument of "habit", but if this feature is enabled on
other systems (Windows and Linux), there is customary to use (although
there are physical buttons)

- I'm not expert in user interface design or usability, in the case that
this is due to a "particular workflow," When "tap to click", could
activate automatically in GDM?

thanks

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1711538/comments/1


On 2015-04-10T15:51:03+00:00 Bugzilla-x wrote:

http://wayland.freedesktop.org/libinput/doc/latest/tapping.html says:
"
Tapping is disabled by default, see this commit because:
- if you don't know that tapping is a thing (or enabled by default), you get 
spurious button events that make the desktop feel buggy.
- if you do know what tapping is and you want it, you usually know where to 
enable it, or at least you can search for it.
"

So the default won't be changed I'm afraid.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1711538/comments/2


** Changed in: gnome-settings-daemon
   Status: Unknown => Won't Fix

** Changed in: gnome-settings-daemon
   Importance: Unknown => Medium

** Bug watch added: Red Hat Bugzilla #912886
   https://bugzilla.redhat.com/show_bug.cgi?id=912886

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

Title:
  Tap-to-click does not work on the GDM login screen

Status in gnome-control-center:
  New
Status in GNOME Settings Daemon:
  Won't Fix
Status in gdm3 package in Ubuntu:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  Tap-to-click does not work in GDM login

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.25.90.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Aug 18 16:16:56 2017
  InstallationDate: Installed on 2017-05-04 (105 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1711538/+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