[Desktop-packages] [Bug 1863801] Re: [snap] chromium crashes when file picker is called to upload files or folders

[Olivier Tilloy]

Paul, Chris: can you make sure your systems are fully up-to-date (debs
and snaps), and let me know if the problem persists?

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

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

Title:
  [snap] chromium crashes when file picker is called to upload files or
  folders

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  First noted today, the snap version of Chromium will crash while
  trying to upload files or folders. I've noted this on my personal
  filespace at my email provider, with Google Drive and Apple's iCloud.
  This is on a freshly booted system and I have logged out and back in
  again but I continue to reproduce the crash each time.

  To reproduce
  
  Log on to Google drive: https://drive.google.com/drive/my-drive
  Click on the 'New' button
  Click on either 'File upload' or 'Folder upload'
  Chromium crashes immediately. The file/folder picker isn't displayed.

  I've verified that Google Chrome and Firefox can upload files to
  Google Drive. I don't see this problem when using Xubuntu 20.04.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1863801/+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 1863801] Re: [snap] chromium crashes when file picker is called to upload files or folders

[Olivier Tilloy]

Looks like this problem affects only 20.04 ?
I briefly had a similar issue on Monday where saving any PDF file open in 
chromium would crash the browser before the save as dialog got a chance to 
appear. But it's now gone, and I have verified that I can upload files too. 
Tested on my work laptop running a rather bloated 20.04, and in a clean 20.04 
VM.

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

Title:
  [snap] chromium crashes when file picker is called to upload files or
  folders

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  First noted today, the snap version of Chromium will crash while
  trying to upload files or folders. I've noted this on my personal
  filespace at my email provider, with Google Drive and Apple's iCloud.
  This is on a freshly booted system and I have logged out and back in
  again but I continue to reproduce the crash each time.

  To reproduce
  
  Log on to Google drive: https://drive.google.com/drive/my-drive
  Click on the 'New' button
  Click on either 'File upload' or 'Folder upload'
  Chromium crashes immediately. The file/folder picker isn't displayed.

  I've verified that Google Chrome and Firefox can upload files to
  Google Drive. I don't see this problem when using Xubuntu 20.04.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1863801/+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 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it

[Seyeong Kim]

I uploaded patch for bionic sru. but I didn't subscribe sru-sponsors yet
because I'm still confirming reproducer.

I'll update description after reproducing this issue in my local.

Thanks.

** Tags added: sts

** Changed in: network-manager (Ubuntu Bionic)
 Assignee: (unassigned) => Seyeong Kim (xtrusia)

** Patch added: "lp1794478_bionic.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1794478/+attachment/5329464/+files/lp1794478_bionic.debdiff

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

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Confirmed

Bug description:
  [Impact]
  [Test Case]
  [Potential Regression]

  [Other informations]

  * Upstream bug and fix:

  https://bugzilla.redhat.com/show_bug.cgi?id=1575944
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35

  * Only affecting Bionic:

  $ git describe --contains f03ae35
  1.10.8~2

  $ rmadison network-manager
  ==> network-manager | 1.10.6-2ubuntu1.2   | bionic-updates
  network-manager | 1.20.4-2ubuntu2.2   | eoan-updates
  network-manager | 1.22.4-1ubuntu2 | focal

  [Original description]

  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.

  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux

  Machine Type = s390x

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after 
maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan 
interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=auto

  From /var/log/syslog, we can see ip got assigned:

  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 
255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on 
test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 
10.2.3.1
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1

  root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  28: test_bond:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
  link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
  inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute 
test_bond
     valid_lft 353sec preferred_lft 353sec
  inet6 fe80::ff:feb3:b522/64 scope link
     valid_lft forever preferred_lft forever

  
+++
  Bond interface, ipv4 automatic mode and ipv6 manual mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
  [connection]
  id=test_bond
  uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537943300

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  address1=fe81::32a5:bc5f:287f:8db8/64
  dns-search=
  method=manual

  No automatic ip assigned to ipv4 and no requests to dhcp server seen in 
/var/log/syslog
  root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  29: test_bond:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
  link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
  inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute
  

[Desktop-packages] [Bug 1863724] Please test proposed package

[Timo Aaltonen]

Hello Timo, or anyone else affected,

Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/19.2.8-0ubuntu0~18.04.3 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Add missing pci-id's for Comet Lake (CML)

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Bionic:
  Fix Committed
Status in mesa source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

  After rebasing mesa to 19.2.x debian/patches/i965-sync-pciids.diff was
  updated but some parts of it got accidentally dropped, losing a couple
  of pci-id's for CML. They need to be restored.

  [Test case]

  Install the updates on an affected machine, check with glxinfo -B that
  the proper driver is loaded.

  [Regression potential]

  none, this just adds pci-id's

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1863724/+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 1863724] Re: Add missing pci-id's for Comet Lake (CML)

[Timo Aaltonen]

Hello Timo, or anyone else affected,

Accepted mesa into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/19.2.8-0ubuntu0~19.10.3 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed verification-needed-eoan

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

** Tags added: verification-needed-bionic

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

Title:
  Add missing pci-id's for Comet Lake (CML)

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Bionic:
  Fix Committed
Status in mesa source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

  After rebasing mesa to 19.2.x debian/patches/i965-sync-pciids.diff was
  updated but some parts of it got accidentally dropped, losing a couple
  of pci-id's for CML. They need to be restored.

  [Test case]

  Install the updates on an affected machine, check with glxinfo -B that
  the proper driver is loaded.

  [Regression potential]

  none, this just adds pci-id's

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1863724/+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 1863454] Re: gnome-shell assert failure: gnome-shell: ../src/evdev-mt-touchpad.c:532: tp_process_absolute: Assertion `tp->nactive_slots >= 1' failed.

[Daniel van Vugt]

** Changed in: libinput (Ubuntu)
   Status: Confirmed => Triaged

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

** Tags added: fixed-in-1.15.2 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/1863454

Title:
  gnome-shell assert failure: gnome-shell: ../src/evdev-mt-
  touchpad.c:532: tp_process_absolute: Assertion `tp->nactive_slots >=
  1' failed.

Status in libinput:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in libinput package in Ubuntu:
  Triaged

Bug description:
  I'm getting error on startup.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AssertionMessage: gnome-shell: ../src/evdev-mt-touchpad.c:532: 
tp_process_absolute: Assertion `tp->nactive_slots >= 1' failed.
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Feb 14 17:49:49 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-02-04 (11 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __assert_fail_base (fmt=0x7f8f2042dfb8 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=0x7f8f1de1a260 "tp->nactive_slots >= 1", 
file=0x7f8f1de1a0f1 "../src/evdev-mt-touchpad.c", line=532, function=) at assert.c:92
   __GI___assert_fail (assertion=0x7f8f1de1a260 "tp->nactive_slots >= 1", 
file=0x7f8f1de1a0f1 "../src/evdev-mt-touchpad.c", line=532, 
function=0x7f8f1de1a9f0 "tp_process_absolute") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libinput.so.10
   ?? () from /usr/lib/x86_64-linux-gnu/libinput.so.10
   libinput_dispatch () from /usr/lib/x86_64-linux-gnu/libinput.so.10
  Title: gnome-shell assert failure: gnome-shell: 
../src/evdev-mt-touchpad.c:532: tp_process_absolute: Assertion 
`tp->nactive_slots >= 1' failed.
  UpgradeStatus: Upgraded to focal on 2020-02-14 (1 days ago)
  UserGroups:
   
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/libinput/+bug/1863454/+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 1863454] Re: gnome-shell assert failure: gnome-shell: ../src/evdev-mt-touchpad.c:532: tp_process_absolute: Assertion `tp->nactive_slots >= 1' failed.

[Bug Watch Updater]

** Changed in: libinput
   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/1863454

Title:
  gnome-shell assert failure: gnome-shell: ../src/evdev-mt-
  touchpad.c:532: tp_process_absolute: Assertion `tp->nactive_slots >=
  1' failed.

Status in libinput:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in libinput package in Ubuntu:
  Confirmed

Bug description:
  I'm getting error on startup.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AssertionMessage: gnome-shell: ../src/evdev-mt-touchpad.c:532: 
tp_process_absolute: Assertion `tp->nactive_slots >= 1' failed.
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Feb 14 17:49:49 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-02-04 (11 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __assert_fail_base (fmt=0x7f8f2042dfb8 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=0x7f8f1de1a260 "tp->nactive_slots >= 1", 
file=0x7f8f1de1a0f1 "../src/evdev-mt-touchpad.c", line=532, function=) at assert.c:92
   __GI___assert_fail (assertion=0x7f8f1de1a260 "tp->nactive_slots >= 1", 
file=0x7f8f1de1a0f1 "../src/evdev-mt-touchpad.c", line=532, 
function=0x7f8f1de1a9f0 "tp_process_absolute") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libinput.so.10
   ?? () from /usr/lib/x86_64-linux-gnu/libinput.so.10
   libinput_dispatch () from /usr/lib/x86_64-linux-gnu/libinput.so.10
  Title: gnome-shell assert failure: gnome-shell: 
../src/evdev-mt-touchpad.c:532: tp_process_absolute: Assertion 
`tp->nactive_slots >= 1' failed.
  UpgradeStatus: Upgraded to focal on 2020-02-14 (1 days ago)
  UserGroups:
   
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/libinput/+bug/1863454/+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 1858857] Re: gnome-calendar: Hits assert when timezone set to Etc/UTC

[Matthew Ruffell]

** Information type changed from Private to Public

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

Title:
  gnome-calendar: Hits assert when timezone set to Etc/UTC

Status in gnome-calendar package in Ubuntu:
  In Progress
Status in gnome-calendar source package in Focal:
  In Progress

Bug description:
  [Impact]

  When the system timezone is set to Etc/UTC, most notably in the 20.04
  Live CD environment, gnome-calendar fails to start, as it hits an
  assert.

  ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: 
assertion failed: (ical_tz != NULL)
  Bail out! 
ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: 
assertion failed: (ical_tz != NULL)
  Aborted (core dumped)

  This is reproducible in focal with: gnome-calendar 3.34.2-1build1
  This is NOT reproducible in eoan with: gnome-calendar 3.34.2-1

  More seriously, this bug is triggered when a user presses the Super
  key in the Live CD test environment and searches for an application,
  as dbus will attempt to start the gnome-calendar service, and gnome-
  calendar will crash due to this bug.

  [Test Case]

  Change system timezone to Etc/UTC and attempt to launch gnome-
  calendar:

  ubuntu@ubuntu:/var/log$ sudo timedatectl set-timezone Etc/UTC
  ubuntu@ubuntu:/var/log$ timedatectl
     Local time: Tue 2020-02-18 02:49:21 UTC
     Universal time: Tue 2020-02-18 02:49:21 UTC
   RTC time: Tue 2020-02-18 02:49:22
  Time zone: Etc/UTC (UTC, +)
  System clock synchronized: yes
    NTP service: active
    RTC in local TZ: no
  ubuntu@ubuntu:/var/log$ gnome-calendar
  **
  ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: 
assertion failed: (ical_tz != NULL)
  Bail out! 
ERROR:../src/utils/gcal-date-time-utils.c:249:gcal_timezone_to_icaltimezone: 
assertion failed: (ical_tz != NULL)
  Aborted (core dumped)

  [Regression Potential]

  The risk of regression is low due to the assert being removed and
  replaced with a default to UTC time if the previous timezone pointer
  is NULL. This is also only going to the focal development release,
  where any impact to real users will be low.

  [Other Information]

  There is an upstream issue open:

  https://gitlab.gnome.org/GNOME/gnome-calendar/issues/485

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1858857/+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 1856516] Re: Excessive memory usage by gnome-shell in 19.10

[Daniel van Vugt]

And to avoid affecting all other programs, instead of 'export' try
moving gnome-shell to gnome-shell.bin and creating a gnome-shell script
to set up the environment.

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

Title:
  Excessive memory usage by gnome-shell in 19.10

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The gnome-shell process on my system is currently at 5473M VIRT 1224M
  RSS 566M SHR; this seems a bit excessive.

  This session has been up for >4 days with a number of suspend/resume
  cycles in there, so this might be a slow leak?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic 
5.3.10
  Uname: Linux 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 16 16:50:10 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-08-29 (109 days ago)
  InstallationMedia: Ubuntu 19.10 bcachefs (20190828)
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   SHELL=/usr/bin/fish
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856516/+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 1856516] Re: Excessive memory usage by gnome-shell in 19.10

[Daniel van Vugt]

Maybe I gave the wrong advice. Try: HEAP_PROFILE_ONLY_MMAP=true

I know that once you successfully have that set then the performance
overhead goes away.

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

Title:
  Excessive memory usage by gnome-shell in 19.10

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The gnome-shell process on my system is currently at 5473M VIRT 1224M
  RSS 566M SHR; this seems a bit excessive.

  This session has been up for >4 days with a number of suspend/resume
  cycles in there, so this might be a slow leak?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic 
5.3.10
  Uname: Linux 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 16 16:50:10 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-08-29 (109 days ago)
  InstallationMedia: Ubuntu 19.10 bcachefs (20190828)
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   SHELL=/usr/bin/fish
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856516/+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 1856516] Re: Excessive memory usage by gnome-shell in 19.10

[Chris Halse Rogers]

Hm. The gperftools profiler appears to have a catastrophic performance
impact on gnome-shell - it takes multiple minutes to go from login
screen to an idle desktop (there's also the problem that setting the
environment variable means *all* programs in the session profiled,
because they're all children of the shell?).

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

Title:
  Excessive memory usage by gnome-shell in 19.10

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The gnome-shell process on my system is currently at 5473M VIRT 1224M
  RSS 566M SHR; this seems a bit excessive.

  This session has been up for >4 days with a number of suspend/resume
  cycles in there, so this might be a slow leak?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic 
5.3.10
  Uname: Linux 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 16 16:50:10 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-08-29 (109 days ago)
  InstallationMedia: Ubuntu 19.10 bcachefs (20190828)
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, user)
   SHELL=/usr/bin/fish
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856516/+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 1863797] Re: gdk-pixbuf-thumbnailer fails to create thumbnails for CR2 100% of the time.

[Bug Watch Updater]

** Changed in: gdk-pixbuf
   Status: Unknown => New

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

Title:
  gdk-pixbuf-thumbnailer fails to create thumbnails for CR2 100% of the
  time.

Status in gdk-pixbuf:
  New
Status in gdk-pixbuf package in Ubuntu:
  Confirmed

Bug description:
  I have been adding "image/x-xpixmap;image/x-canon-cr2;image/x-adobe-
  dng" to the end of the line starting with "MimeType=" in the file
  "/usr/share/thumbnailers/gdk-pixbuf-thumbnailer.thumbnailer" since
  Ubuntu 18.10 for the thumbnailer to create the thumbnails primarily
  for the ".CR2" raw files from my Canon 77D and 80D cameras.

  Unfortunately I have to report that as of Ubuntu 19.10 this solution doesn’t 
work on my machine anymore.
  The thumbnailer tries to create the thumbnails but fails and instead creates 
1 pixel png images that it all puts in 
"~/.cache/thumbnails/fail/gnome-thumbnail-factory".

  Is there any solution? Should I test something?

  I've attached a CR2 photo of mine that anyone can use for testing.

  I've also created a bug report on gnome gitlab here:
  https://gitlab.gnome.org/GNOME/gdk-pixbuf/issues/144

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1863797/+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 1863797] Re: gdk-pixbuf-thumbnailer fails to create thumbnails for CR2 100% of the time.

[Kristijan Žic ]

Edited the original report to link to a new issue upstream:
https://gitlab.gnome.org/GNOME/gdk-pixbuf/issues/144

** Bug watch added: gitlab.gnome.org/GNOME/gdk-pixbuf/issues #144
   https://gitlab.gnome.org/GNOME/gdk-pixbuf/issues/144

** Changed in: gdk-pixbuf
   Status: New => Unknown

** Changed in: gdk-pixbuf
 Remote watch: gitlab.gnome.org/GNOME/gnome-desktop/issues #133 => 
gitlab.gnome.org/GNOME/gdk-pixbuf/issues #144

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

Title:
  gdk-pixbuf-thumbnailer fails to create thumbnails for CR2 100% of the
  time.

Status in gdk-pixbuf:
  Unknown
Status in gdk-pixbuf package in Ubuntu:
  Confirmed

Bug description:
  I have been adding "image/x-xpixmap;image/x-canon-cr2;image/x-adobe-
  dng" to the end of the line starting with "MimeType=" in the file
  "/usr/share/thumbnailers/gdk-pixbuf-thumbnailer.thumbnailer" since
  Ubuntu 18.10 for the thumbnailer to create the thumbnails primarily
  for the ".CR2" raw files from my Canon 77D and 80D cameras.

  Unfortunately I have to report that as of Ubuntu 19.10 this solution doesn’t 
work on my machine anymore.
  The thumbnailer tries to create the thumbnails but fails and instead creates 
1 pixel png images that it all puts in 
"~/.cache/thumbnails/fail/gnome-thumbnail-factory".

  Is there any solution? Should I test something?

  I've attached a CR2 photo of mine that anyone can use for testing.

  I've also created a bug report on gnome gitlab here:
  https://gitlab.gnome.org/GNOME/gdk-pixbuf/issues/144

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1863797/+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 1862229] Re: gnome session crash on boot with kernel 5.3.0-29-generic

[Daniel van Vugt]

Thanks. Those unfortunately failed. Next time the problem happens please
send us a new link.

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

Title:
  gnome session crash on boot with kernel 5.3.0-29-generic

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  apt-cache policy gnome-shell
  gnome-shell:
    Installato: 3.34.1+git20191024-1ubuntu1~19.10.1
    Candidato:  3.34.1+git20191024-1ubuntu1~19.10.1
    Tabella versione:
   *** 3.34.1+git20191024-1ubuntu1~19.10.1 500
  500 http://it.archive.ubuntu.com/ubuntu eoan-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.34.1-1ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  First there was an issue with hibernation: after resuming, the gnome
  session was not restored and a new one was created (I had to login
  again from start). Here are some relevant log lines:

  [   21.375254] PM: Image signature found, resuming
  [   21.375255] PM: resume from hibernation
  [   21.375607] Freezing user space processes ... (elapsed 0.001 seconds) done.
  [   21.376719] OOM killer disabled.
  [   21.376832] PM: Marking nosave pages: [mem 0x-0x0fff]
  [   21.376834] PM: Marking nosave pages: [mem 0x0004f000-0x0004]
  [   21.376834] PM: Marking nosave pages: [mem 0x0009d000-0x0009efff]
  [   21.376835] PM: Marking nosave pages: [mem 0x000a-0x000f]
  [   21.376837] PM: Marking nosave pages: [mem 0xae7a8000-0xae7aefff]
  [   21.376838] PM: Marking nosave pages: [mem 0xaf18c000-0xaf66afff]
  [   21.376856] PM: Marking nosave pages: [mem 0xb7db3000-0xb7ff]
  [   21.376865] PM: Marking nosave pages: [mem 0xb8759000-0xb87f]
  [   21.376868] PM: Marking nosave pages: [mem 0xb8f9d000-0xb8ff]
  [   21.376870] PM: Marking nosave pages: [mem 0xba6f5000-0xba7f]
  [   21.376875] PM: Marking nosave pages: [mem 0xbbcec000-0x]
  [   21.377562] PM: Basic memory bitmaps created
  [   24.367114] PM: Using 3 thread(s) for decompression
  [   24.367115] PM: Loading and decompressing image data (1585416 pages)...
  [   24.367127] Hibernate inconsistent memory map detected!
  [   24.367138] fbcon: Taking over console
  [   24.367139] PM: Image mismatch: architecture specific data
  [   24.367141] PM: Read 6341664 kbytes in 0.01 seconds (634166.40 MB/s)
  [   24.368077] PM: Error -1 resuming
  [   24.368079] PM: Failed to load hibernation image, recovering.
  [   24.368347] PM: Basic memory bitmaps freed
  [   24.368347] OOM killer enabled.
  [   24.368347] Restarting tasks ... done.
  [   24.384357] Console: switching to colour frame buffer device 240x67
  [   24.404345] PM: resume from hibernation failed (-1)

  Then, since next restart I cannot login anymore, as the session keeps 
crashing immediately after entering user's password.
  The only way I could login back was by selecting the previous kernel version 
on boot (5.3.0-26-generic instead of 5.3.0-29-generic).

  I also noticed all gnome extensions (Applications Menu and Hibernate
  Status Button ) stopped working and were disabled.

  Boot journal attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862229/+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 1863797] Re: gdk-pixbuf-thumbnailer fails to create thumbnails for CR2 100% of the time.

[Kristijan Žic ]

** Description changed:

  I have been adding "image/x-xpixmap;image/x-canon-cr2;image/x-adobe-dng"
  to the end of the line starting with "MimeType=" in the file
  "/usr/share/thumbnailers/gdk-pixbuf-thumbnailer.thumbnailer" since
  Ubuntu 18.10 for the thumbnailer to create the thumbnails primarily for
  the ".CR2" raw files from my Canon 77D and 80D cameras.
  
  Unfortunately I have to report that as of Ubuntu 19.10 this solution doesn’t 
work on my machine anymore.
  The thumbnailer tries to create the thumbnails but fails and instead creates 
1 pixel png images that it all puts in 
"~/.cache/thumbnails/fail/gnome-thumbnail-factory".
  
  Is there any solution? Should I test something?
  
  I've attached a CR2 photo of mine that anyone can use for testing.
  
  I've also created a bug report on gnome gitlab here:
- https://gitlab.gnome.org/GNOME/gnome-desktop/issues/133
+ https://gitlab.gnome.org/GNOME/gdk-pixbuf/issues/144

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

Title:
  gdk-pixbuf-thumbnailer fails to create thumbnails for CR2 100% of the
  time.

Status in gdk-pixbuf:
  Unknown
Status in gdk-pixbuf package in Ubuntu:
  Confirmed

Bug description:
  I have been adding "image/x-xpixmap;image/x-canon-cr2;image/x-adobe-
  dng" to the end of the line starting with "MimeType=" in the file
  "/usr/share/thumbnailers/gdk-pixbuf-thumbnailer.thumbnailer" since
  Ubuntu 18.10 for the thumbnailer to create the thumbnails primarily
  for the ".CR2" raw files from my Canon 77D and 80D cameras.

  Unfortunately I have to report that as of Ubuntu 19.10 this solution doesn’t 
work on my machine anymore.
  The thumbnailer tries to create the thumbnails but fails and instead creates 
1 pixel png images that it all puts in 
"~/.cache/thumbnails/fail/gnome-thumbnail-factory".

  Is there any solution? Should I test something?

  I've attached a CR2 photo of mine that anyone can use for testing.

  I've also created a bug report on gnome gitlab here:
  https://gitlab.gnome.org/GNOME/gdk-pixbuf/issues/144

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1863797/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

[Daniel van Vugt]

** Also affects: pulseaudio via
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/776
   Importance: Unknown
   Status: Unknown

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

Status in PulseAudio:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1819890] Re: Restarting gnome-shell displays images of applications running on other workspaces

[Daniel van Vugt]

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

** Changed in: mutter (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Restarting gnome-shell displays images of applications running on
  other workspaces

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Restarting gnome-shell with 'Alt-F2,r and enter' displays images of
  applications running on other workspaces which are not clickable.

  Steps to reproduce:

  1) Enable multiple workspaces
  2) Start an application on each workspace
  3) From any workspace, restart gnome-shell with 'Alt-F2, r and enter'

  Expected outcome:

  As with Ubuntu 18.04, each application is displayed only the workspace
  on which it was started.

  Actual outcome:

  All applications are displayed on the current workspace. The
  applications running on other workspaces are displayed as images, i.e.
  they cannot be 'clicked' but he 'wanted' application, the dock, top
  bar etc all function correctly.

  Workaround:

  To remove the unwanted images move to another workspace and return.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 13 10:15:45 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-20 (51 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190120)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1819890/+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 1852900] Re: Gnome-shell restart-refresh causes minimized applications to become unresponsive and unminimized

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1819890
   Restarting gnome-shell displays images of applications running on other 
workspaces

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

Title:
  Gnome-shell restart-refresh causes  minimized applications to become
  unresponsive and unminimized

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Let's say you have minimized one or more applications such as Firefox,
  Gnome Tweaks or even Nautilus File Manager. These applications will be
  become unminimized after gnome-shell restart and also become
  unresponsive, unless I press to minimize/maximize them, these
  applications stay permanently unresponsive.

  No matter what is your method of restarting Gnome Shell:

  Either combination of ALT+F2+R

  Or a command line command:

  busctl --user call org.gnome.Shell /org/gnome/Shell org.gnome.Shell
  Eval s 'Meta.restart("Restarting…")'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov 17 12:22:21 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-20 (119 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1852900/+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 1860540] Re: Password entry has no way of displaying what you type

[Daniel van Vugt]

Ignore the "notfixing" part then. A solution is already released and a
_better_ solution is still coming in gnome-shell 3.36.

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

Title:
  Password entry has no way of displaying what you type

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

Bug description:
  In Focal the network password / passphrase entry form has no way of
  displaying what is being typed.

  I'd expect a checkbox or something...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.442
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CasperVersion: 1.438
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 22 11:13:41 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1860540/+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 1725180] Re: Shell animations are not smooth

[Daniel van Vugt]

^^^
That's fixed in gjs 1.63.91

** Description changed:

  Upstream fixes required to make all the overview/window/icon animations
  much smoother (at least halving render times):
  
  https://gitlab.gnome.org/GNOME/gjs/merge_requests/390
  https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/948
  https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/936
- https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/949
+ https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/1002
  
  __
  
  +++UBUNTU RELEASE+++
  
  Description:  Ubuntu 17.10
  Release:  17.10
  
  +++PACKAGE VERSION+++
  
  xwayland:
    Installed: 2:1.19.5-0ubuntu2
    Candidate: 2:1.19.5-0ubuntu2
    Version table:
   *** 2:1.19.5-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status
  
  Bug found on Dell XPS 9560 4K model with GTX1050/Intel HD 630. Currently
  using Intel HD Graphics 630 as Nvidia seems to have no support for
  xwayland.
  
  The window/dock/launcher animations are lagging/shaky (not smooth).
  
  __
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xwayland 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:
  
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 19:09:27 2017
  DistUpgraded: 2017-10-20 04:51:46,123 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-387, 387.12, 4.13.0-16-generic, x86_64: installed
   v4l2loopback, 0.10.0, 4.10.0-37-generic, x86_64: installed
   v4l2loopback, 0.10.0, 4.13.0-16-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:07be]
     Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
  InstallationDate: Installed on 2017-05-24 (149 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc.
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=38514616-2735-4966-91f7-71f1d60beb73 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 08/30/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

Title:
  Shell animations are not smooth

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

Bug description:
  Upstream fixes required to make all the overview/window/icon
  animations much smoother (at least halving render times):

  https://gitlab.gnome.org/GNOME/gjs/merge_requests/390
  https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/948
  https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/936
  

[Desktop-packages] [Bug 1863400] Re: gnome-shell reports problem on boot

[Daniel van Vugt]

I forgot to mention: Please also:

  sudo rm /var/crash/*

as those old files may prevent recurrences from being reported.

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

Title:
  gnome-shell reports problem on boot

Status in gnome-shell package in Ubuntu:
  Incomplete

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

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

  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18
  Uname: Linux 4.15.0-76-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 15 06:21:53 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-17 (454 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1175882] Re: Hangs while modifying document (after completion of paste from Wep Page with Multiple Images)

[Bug Watch Updater]

** Bug watch added: Document Foundation Bugzilla #130759
   https://bugs.documentfoundation.org/show_bug.cgi?id=130759

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

Title:
  Hangs while modifying document (after completion of paste from Wep
  Page with Multiple Images)

Status in LibreOffice:
  New
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  Follow these steps to bring LibreOffice writer to a crawl:

  1) Allow this page to fully load in firefox (in a new tab):
  http://www.amorosity.com/SlingBlade/

  2) Click on the page and hit ctrl-a, then ctrl-c (coping the entire
  page's contents into memory).

  3) Open LibreOffice writer, and paste your clipboard into it.

  I don't mind waiting for all the images to get loaded. The main point
  here, is that performance is not only slow during the initial paste.
  After the images get fully loaded into the word processing document,
  interacting with the document becomes impractical. Everything you try
  to do makes the application hang for several seconds.

  I have 4 gigabytes of RAM available for LibreOffice writer to use as
  it wishes, but it must be using some type of swap file (instead) while
  I'm modifying this large document. However, I have a really fast
  solid-state hard drive, so you'd think that even that would be fast on
  my machine.

  My machine should have the specs to enable me the ability to handle
  converting this large web page into a word processing document.

  Yes there are other ways to achieve what I'm trying to do, but this
  bug is about how LibreOffice can't handle the job. If it was
  programmed just right, it would make use of the resources my computer
  would gladly provide it, and scale up to this rather intensive task.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libreoffice-writer 1:4.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Thu May  2 23:09:24 2013
  InstallationDate: Installed on 2013-04-02 (31 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130401)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Lonnie Lee Best]

BTW, when I first reported this bug, in 2013, the web page (referenced
in step 1) contained only png images.

Today, it contains webp images exclusively:
http://www.amorosity.com/SlingBlade/

All modern web browsers support webp images:
https://developers.google.com/speed/webp

However, Libre Office doesn't support webp.

Despite this lack of webp support, it is not the cause of the bug being
reported here. The bug would still happen even if those images were
still PNGs.

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

Title:
  Hangs while modifying document (after completion of paste from Wep
  Page with Multiple Images)

Status in LibreOffice:
  New
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  Follow these steps to bring LibreOffice writer to a crawl:

  1) Allow this page to fully load in firefox (in a new tab):
  http://www.amorosity.com/SlingBlade/

  2) Click on the page and hit ctrl-a, then ctrl-c (coping the entire
  page's contents into memory).

  3) Open LibreOffice writer, and paste your clipboard into it.

  I don't mind waiting for all the images to get loaded. The main point
  here, is that performance is not only slow during the initial paste.
  After the images get fully loaded into the word processing document,
  interacting with the document becomes impractical. Everything you try
  to do makes the application hang for several seconds.

  I have 4 gigabytes of RAM available for LibreOffice writer to use as
  it wishes, but it must be using some type of swap file (instead) while
  I'm modifying this large document. However, I have a really fast
  solid-state hard drive, so you'd think that even that would be fast on
  my machine.

  My machine should have the specs to enable me the ability to handle
  converting this large web page into a word processing document.

  Yes there are other ways to achieve what I'm trying to do, but this
  bug is about how LibreOffice can't handle the job. If it was
  programmed just right, it would make use of the resources my computer
  would gladly provide it, and scale up to this rather intensive task.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libreoffice-writer 1:4.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Thu May  2 23:09:24 2013
  InstallationDate: Installed on 2013-04-02 (31 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130401)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Lonnie Lee Best]

A separate bug, related to webp support, has been submitted here:
https://bugs.documentfoundation.org/show_bug.cgi?id=130759

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

Title:
  Hangs while modifying document (after completion of paste from Wep
  Page with Multiple Images)

Status in LibreOffice:
  New
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  Follow these steps to bring LibreOffice writer to a crawl:

  1) Allow this page to fully load in firefox (in a new tab):
  http://www.amorosity.com/SlingBlade/

  2) Click on the page and hit ctrl-a, then ctrl-c (coping the entire
  page's contents into memory).

  3) Open LibreOffice writer, and paste your clipboard into it.

  I don't mind waiting for all the images to get loaded. The main point
  here, is that performance is not only slow during the initial paste.
  After the images get fully loaded into the word processing document,
  interacting with the document becomes impractical. Everything you try
  to do makes the application hang for several seconds.

  I have 4 gigabytes of RAM available for LibreOffice writer to use as
  it wishes, but it must be using some type of swap file (instead) while
  I'm modifying this large document. However, I have a really fast
  solid-state hard drive, so you'd think that even that would be fast on
  my machine.

  My machine should have the specs to enable me the ability to handle
  converting this large web page into a word processing document.

  Yes there are other ways to achieve what I'm trying to do, but this
  bug is about how LibreOffice can't handle the job. If it was
  programmed just right, it would make use of the resources my computer
  would gladly provide it, and scale up to this rather intensive task.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libreoffice-writer 1:4.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Thu May  2 23:09:24 2013
  InstallationDate: Installed on 2013-04-02 (31 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130401)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1175882/+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 1863817] [NEW] Firefox Location Sharing Has Stopped Working

[Stephen Rynas]

Public bug reported:

Using Ubuntu 16.04. Firefox Version 72.0.2. Both HULU and Google maps
now state that my location could not be determined. Location sharing
previously worked, so I assume that it is a bug. Mozilla Technical
Support believes that the problem resides in the Ubuntu repository
version of Firefox.

"That appears to be a problem with Firefox from the repositories that
doesn't seem to include the Mozilla Location Service Key and doesn't
offer an alternative. You can check that on the "Help -> Troubleshooting
Information" (about:support) page.

You will have to use Firefox from the Mozilla server. Note that current
is Firefox 73.0.1."

Hopefully, by updating the version of Firefox in the repository, this
problem will be fixed.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 72.0.2+build1-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
Uname: Linux 4.4.0-131-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  steve  2157 F pulseaudio
 /dev/snd/controlC0:  steve  2157 F pulseaudio
BuildID: 20200117190643
Channel: Unavailable
CurrentDesktop: Unity
Date: Tue Feb 18 18:25:23 2020
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2016-07-30 (1298 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IpRoute:
 default via 192.168.1.1 dev enp3s0  proto static  metric 100 
 169.254.0.0/16 dev enp3s0  scope link  metric 1000 
 192.168.1.0/24 dev enp3s0  proto kernel  scope link  src 192.168.1.12  metric 
100
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-b5844b18-6c0d-40d3-babe-d58410190308
PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:727
PrefSources: prefs.js
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=72.0.2/20200117190643 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
SubmittedCrashIDs:
 bp-b5844b18-6c0d-40d3-babe-d58410190308
 bp-175bf043-8a30-4e88-9eb8-158740180514
 bp-cde17737-5d2d-4b88-a84b-afbf31180316
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/06/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0906
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8B75-M LX PLUS
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.:bvr0906:bd08/06/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8B75-MLXPLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


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

Title:
  Firefox Location Sharing Has Stopped Working

Status in firefox package in Ubuntu:
  New

Bug description:
  Using Ubuntu 16.04. Firefox Version 72.0.2. Both HULU and Google maps
  now state that my location could not be determined. Location sharing
  previously worked, so I assume that it is a bug. Mozilla Technical
  Support believes that the problem resides in the Ubuntu repository
  version of Firefox.

  "That appears to be a problem with Firefox from the repositories that
  doesn't seem to include the Mozilla Location Service Key and doesn't
  offer an alternative. You can check that on the "Help ->
  Troubleshooting Information" (about:support) page.

  You will have to use Firefox from the Mozilla server. Note that
  current is Firefox 73.0.1."

  Hopefully, by updating the version of Firefox in the repository, this
  problem will be fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 72.0.2+build1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
  Uname: Linux 4.4.0-131-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  steve  2157 F pulseaudio
   /dev/snd/controlC0:  steve  2157 F pulseaudio
  BuildID: 20200117190643
  Channel: Unavailable
  

[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

[Launchpad Bug Tracker]

This bug was fixed in the package dballe - 8.6-1ubuntu1

---
dballe (8.6-1ubuntu1) focal; urgency=medium

  * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8.
(LP: #1863026)

 -- Andreas Hasenack   Wed, 12 Feb 2020 20:11:06
-0300

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

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

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

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  Fix Released
Status in asterisk package in Ubuntu:
  Fix Released
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  Fix Released
Status in dballe package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gearmand package in Ubuntu:
  In Progress
Status in gerbera package in Ubuntu:
  In Progress
Status in gnokii package in Ubuntu:
  In Progress
Status in gnunet package in Ubuntu:
  In Progress
Status in hoel package in Ubuntu:
  In Progress
Status in isc-kea package in Ubuntu:
  In Progress
Status in jabberd2 package in Ubuntu:
  In Progress
Status in kannel package in Ubuntu:
  In Progress
Status in libgda5 package in Ubuntu:
  In Progress
Status in libodb-mysql package in Ubuntu:
  In Progress
Status in lyricue package in Ubuntu:
  In Progress
Status in motion package in Ubuntu:
  In Progress
Status in mysql-8.0 package in Ubuntu:
  In Progress
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  In Progress
Status in opendnssec package in Ubuntu:
  In Progress
Status in opensmtpd-extras package in Ubuntu:
  In Progress
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  In Progress
Status in pvpgn package in Ubuntu:
  In Progress
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  In Progress
Status in tntdb package in Ubuntu:
  In Progress
Status in voms-mysql-plugin package in Ubuntu:
  In Progress
Status in vtk7 package in Ubuntu:
  In Progress
Status in w1retap package in Ubuntu:
  In Progress
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+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 1863026] Re: Remove my_bool typedef workaround

[Launchpad Bug Tracker]

This bug was fixed in the package cppdb - 0.3.1+dfsg-8ubuntu2

---
cppdb (0.3.1+dfsg-8ubuntu2) focal; urgency=medium

  * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8.
(LP: #1863026)

 -- Andreas Hasenack   Wed, 12 Feb 2020 20:06:29
-0300

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

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  Fix Released
Status in asterisk package in Ubuntu:
  Fix Released
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  Fix Released
Status in dballe package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gearmand package in Ubuntu:
  In Progress
Status in gerbera package in Ubuntu:
  In Progress
Status in gnokii package in Ubuntu:
  In Progress
Status in gnunet package in Ubuntu:
  In Progress
Status in hoel package in Ubuntu:
  In Progress
Status in isc-kea package in Ubuntu:
  In Progress
Status in jabberd2 package in Ubuntu:
  In Progress
Status in kannel package in Ubuntu:
  In Progress
Status in libgda5 package in Ubuntu:
  In Progress
Status in libodb-mysql package in Ubuntu:
  In Progress
Status in lyricue package in Ubuntu:
  In Progress
Status in motion package in Ubuntu:
  In Progress
Status in mysql-8.0 package in Ubuntu:
  In Progress
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  In Progress
Status in opendnssec package in Ubuntu:
  In Progress
Status in opensmtpd-extras package in Ubuntu:
  In Progress
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  In Progress
Status in pvpgn package in Ubuntu:
  In Progress
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  In Progress
Status in tntdb package in Ubuntu:
  In Progress
Status in voms-mysql-plugin package in Ubuntu:
  In Progress
Status in vtk7 package in Ubuntu:
  In Progress
Status in w1retap package in Ubuntu:
  In Progress
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+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 1863026] Re: Remove my_bool typedef workaround

[Launchpad Bug Tracker]

This bug was fixed in the package gambas3 - 3.14.3-1ubuntu1

---
gambas3 (3.14.3-1ubuntu1) focal; urgency=medium

  * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8.
(LP: #1863026)

 -- Andreas Hasenack   Wed, 12 Feb 2020 19:31:06
-0300

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

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

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  Fix Released
Status in asterisk package in Ubuntu:
  Fix Released
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  Fix Released
Status in dballe package in Ubuntu:
  Fix Released
Status in gambas3 package in Ubuntu:
  Fix Released
Status in gearmand package in Ubuntu:
  In Progress
Status in gerbera package in Ubuntu:
  In Progress
Status in gnokii package in Ubuntu:
  In Progress
Status in gnunet package in Ubuntu:
  In Progress
Status in hoel package in Ubuntu:
  In Progress
Status in isc-kea package in Ubuntu:
  In Progress
Status in jabberd2 package in Ubuntu:
  In Progress
Status in kannel package in Ubuntu:
  In Progress
Status in libgda5 package in Ubuntu:
  In Progress
Status in libodb-mysql package in Ubuntu:
  In Progress
Status in lyricue package in Ubuntu:
  In Progress
Status in motion package in Ubuntu:
  In Progress
Status in mysql-8.0 package in Ubuntu:
  In Progress
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  In Progress
Status in opendnssec package in Ubuntu:
  In Progress
Status in opensmtpd-extras package in Ubuntu:
  In Progress
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  In Progress
Status in pvpgn package in Ubuntu:
  In Progress
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  In Progress
Status in tntdb package in Ubuntu:
  In Progress
Status in voms-mysql-plugin package in Ubuntu:
  In Progress
Status in vtk7 package in Ubuntu:
  In Progress
Status in w1retap package in Ubuntu:
  In Progress
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+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 1863812] [NEW] tells me an update is available, but i'm running a newer version

[dann frazier]

Public bug reported:

Today I noticed that the software manager is telling me there's a juju
update available (2.7.1), with an option to update. When I click update,
it says "Unable to update juju: snap has no updates available". Sure
enough, `snap info` confirms that I'm already on 2.7.*2*:

channels:
  stable:2.7.2 2020-02-18 (10671) 72MB classic
  candidate: ↑ 
  beta:  ↑ 
  edge:  2.8-beta1+develop-29900ab 2020-02-18 (10690) 81MB classic
  2.7/stable:2.7.2 2020-02-18 (10671) 72MB classic
  2.7/candidate: 2.7.3+2.7-aa61342 2020-02-18 (10691) 81MB classic
  2.7/beta:  ↑ 
  2.7/edge:  2.7.3+2.7-aa61342 2020-02-18 (10691) 81MB classic
  2.6/stable:2.6.102019-10-30  (9484) 69MB classic
  2.6/candidate: ↑ 
  2.6/beta:  ↑ 
  2.6/edge:  2.6.11+2.6-b96e1222020-01-22 (10408) 75MB classic
  2.5/stable:2.5.8 2019-06-27  (8361) 67MB classic
  2.5/candidate: ↑ 
  2.5/beta:  ↑ 
  2.5/edge:  2.5.9+2.5-36af233 2019-07-24  (8546) 73MB classic
  2.4/stable:2.4.7 2019-05-23  (6012) 58MB classic
  2.4/candidate: ↑ 
  2.4/beta:  ↑ 
  2.4/edge:  ↑ 
  2.3/stable:2.3.9 2018-09-19  (5267) 55MB classic
  2.3/candidate: ↑ 
  2.3/beta:  ↑ 
  2.3/edge:  2.3.10+2.3-41313d12019-03-25  (7080) 55MB classic
installed:   2.7.2(10671) 72MB classic

gnome-software 3.35.2-0ubuntu2
snapd 2.43.3+git1.8109f8

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

** Attachment added: "Screenshot from 2020-02-18 15-50-41.png"
   
https://bugs.launchpad.net/bugs/1863812/+attachment/5329403/+files/Screenshot%20from%202020-02-18%2015-50-41.png

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

Title:
  tells me an update is available, but i'm running a newer version

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Today I noticed that the software manager is telling me there's a juju
  update available (2.7.1), with an option to update. When I click
  update, it says "Unable to update juju: snap has no updates
  available". Sure enough, `snap info` confirms that I'm already on
  2.7.*2*:

  channels:
stable:2.7.2 2020-02-18 (10671) 72MB classic
candidate: ↑ 
beta:  ↑ 
edge:  2.8-beta1+develop-29900ab 2020-02-18 (10690) 81MB classic
2.7/stable:2.7.2 2020-02-18 (10671) 72MB classic
2.7/candidate: 2.7.3+2.7-aa61342 2020-02-18 (10691) 81MB classic
2.7/beta:  ↑ 
2.7/edge:  2.7.3+2.7-aa61342 2020-02-18 (10691) 81MB classic
2.6/stable:2.6.102019-10-30  (9484) 69MB classic
2.6/candidate: ↑ 
2.6/beta:  ↑ 
2.6/edge:  2.6.11+2.6-b96e1222020-01-22 (10408) 75MB classic
2.5/stable:2.5.8 2019-06-27  (8361) 67MB classic
2.5/candidate: ↑ 
2.5/beta:  ↑ 
2.5/edge:  2.5.9+2.5-36af233 2019-07-24  (8546) 73MB classic
2.4/stable:2.4.7 2019-05-23  (6012) 58MB classic
2.4/candidate: ↑ 
2.4/beta:  ↑ 
2.4/edge:  ↑ 
2.3/stable:2.3.9 2018-09-19  (5267) 55MB classic
2.3/candidate: ↑ 
2.3/beta:  ↑ 
2.3/edge:  2.3.10+2.3-41313d12019-03-25  (7080) 55MB classic
  installed:   2.7.2(10671) 72MB classic

  gnome-software 3.35.2-0ubuntu2
  snapd 2.43.3+git1.8109f8

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1819890] Re: Restarting gnome-shell displays images of applications running on other workspaces

[Bug Watch Updater]

** Changed in: mutter
   Status: New => Fix Released

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

Title:
  Restarting gnome-shell displays images of applications running on
  other workspaces

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Restarting gnome-shell with 'Alt-F2,r and enter' displays images of
  applications running on other workspaces which are not clickable.

  Steps to reproduce:

  1) Enable multiple workspaces
  2) Start an application on each workspace
  3) From any workspace, restart gnome-shell with 'Alt-F2, r and enter'

  Expected outcome:

  As with Ubuntu 18.04, each application is displayed only the workspace
  on which it was started.

  Actual outcome:

  All applications are displayed on the current workspace. The
  applications running on other workspaces are displayed as images, i.e.
  they cannot be 'clicked' but he 'wanted' application, the dock, top
  bar etc all function correctly.

  Workaround:

  To remove the unwanted images move to another workspace and return.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 13 10:15:45 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-20 (51 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190120)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1819890/+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 1863797] Re: gdk-pixbuf-thumbnailer fails to create thumbnails for CR2 100% of the time.

[Bug Watch Updater]

** Changed in: gdk-pixbuf
   Status: Unknown => New

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

Title:
  gdk-pixbuf-thumbnailer fails to create thumbnails for CR2 100% of the
  time.

Status in gdk-pixbuf:
  New
Status in gdk-pixbuf package in Ubuntu:
  Confirmed

Bug description:
  I have been adding "image/x-xpixmap;image/x-canon-cr2;image/x-adobe-
  dng" to the end of the line starting with "MimeType=" in the file
  "/usr/share/thumbnailers/gdk-pixbuf-thumbnailer.thumbnailer" since
  Ubuntu 18.10 for the thumbnailer to create the thumbnails primarily
  for the ".CR2" raw files from my Canon 77D and 80D cameras.

  Unfortunately I have to report that as of Ubuntu 19.10 this solution doesn’t 
work on my machine anymore.
  The thumbnailer tries to create the thumbnails but fails and instead creates 
1 pixel png images that it all puts in 
"~/.cache/thumbnails/fail/gnome-thumbnail-factory".

  Is there any solution? Should I test something?

  I've attached a CR2 photo of mine that anyone can use for testing.

  I've also created a bug report on gnome gitlab here:
  https://gitlab.gnome.org/GNOME/gnome-desktop/issues/133

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1863797/+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 1852900] Re: Gnome-shell restart-refresh causes minimized applications to become unresponsive and unminimized

[Bug Watch Updater]

** Changed in: mutter
   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/1852900

Title:
  Gnome-shell restart-refresh causes  minimized applications to become
  unresponsive and unminimized

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Let's say you have minimized one or more applications such as Firefox,
  Gnome Tweaks or even Nautilus File Manager. These applications will be
  become unminimized after gnome-shell restart and also become
  unresponsive, unless I press to minimize/maximize them, these
  applications stay permanently unresponsive.

  No matter what is your method of restarting Gnome Shell:

  Either combination of ALT+F2+R

  Or a command line command:

  busctl --user call org.gnome.Shell /org/gnome/Shell org.gnome.Shell
  Eval s 'Meta.restart("Restarting…")'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov 17 12:22:21 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-20 (119 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1856160] Re: Bar between bread crumbs and search icon.

[Bug Watch Updater]

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

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

Title:
  Bar between bread crumbs and search icon.

Status in Nautilus:
  New
Status in nautilus package in Ubuntu:
  Triaged

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

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

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

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

[Desktop-packages] [Bug 1863801] Re: [snap] chromium crashes when file picker is called to upload files or folders

[Chris Guiver]

I'll add my primary desktop (20.04 where I had this issue) is bloated
with lubuntu, xubuntu, ubuntu-mate & ubuntu desktops installed. It's
because of this that I test first on a 'clean' (or near clean) system as
well.  I was using LXQt on both

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

Title:
  [snap] chromium crashes when file picker is called to upload files or
  folders

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  First noted today, the snap version of Chromium will crash while
  trying to upload files or folders. I've noted this on my personal
  filespace at my email provider, with Google Drive and Apple's iCloud.
  This is on a freshly booted system and I have logged out and back in
  again but I continue to reproduce the crash each time.

  To reproduce
  
  Log on to Google drive: https://drive.google.com/drive/my-drive
  Click on the 'New' button
  Click on either 'File upload' or 'Folder upload'
  Chromium crashes immediately. The file/folder picker isn't displayed.

  I've verified that Google Chrome and Firefox can upload files to
  Google Drive. I don't see this problem when using Xubuntu 20.04.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1863801/+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 1863801] Re: [snap] chromium crashes when file picker is called to upload files or folders

[Chris Guiver]

It's been doing this since Monday for me (it's Wednesday my local time)
but I usually like confirming the issue on another box before I bug
report. On my other (qa-test install so almost untouched; nfs-common &
some very minor changes) box it uploads without issue? hence I didn't
file bug report.  On this my primary box though, it's been unable to
since Monday 17-Feb (Wed 19-Feb now).

The reason I was trying to upload was because of a user reporting issues
on https://discourse.lubuntu.me/ with 20.04, and whilst this wasn't the
exact issue the user was reporting, it had me testing too (the issue
there was different $HOME folder showing and not the real $HOME which
had wanted files; https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/1798450)

For me, the moment I click upload (before I get to navigate to file to
upload), chromium windows close. When I re-open it resumes as it was a
few days before (not the place it was before crash).  To confirm for
this entry, I tried to upload photo to mewe; it crashed - and history
only shows the 'restore session' for today, not whatever I did earlier
today.

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

Title:
  [snap] chromium crashes when file picker is called to upload files or
  folders

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  First noted today, the snap version of Chromium will crash while
  trying to upload files or folders. I've noted this on my personal
  filespace at my email provider, with Google Drive and Apple's iCloud.
  This is on a freshly booted system and I have logged out and back in
  again but I continue to reproduce the crash each time.

  To reproduce
  
  Log on to Google drive: https://drive.google.com/drive/my-drive
  Click on the 'New' button
  Click on either 'File upload' or 'Folder upload'
  Chromium crashes immediately. The file/folder picker isn't displayed.

  I've verified that Google Chrome and Firefox can upload files to
  Google Drive. I don't see this problem when using Xubuntu 20.04.

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

[Desktop-packages] [Bug 1863801] Re: [snap] chromium crashes when file picker is called to upload files or folders

[Launchpad Bug Tracker]

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

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

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

Title:
  [snap] chromium crashes when file picker is called to upload files or
  folders

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  First noted today, the snap version of Chromium will crash while
  trying to upload files or folders. I've noted this on my personal
  filespace at my email provider, with Google Drive and Apple's iCloud.
  This is on a freshly booted system and I have logged out and back in
  again but I continue to reproduce the crash each time.

  To reproduce
  
  Log on to Google drive: https://drive.google.com/drive/my-drive
  Click on the 'New' button
  Click on either 'File upload' or 'Folder upload'
  Chromium crashes immediately. The file/folder picker isn't displayed.

  I've verified that Google Chrome and Firefox can upload files to
  Google Drive. I don't see this problem when using Xubuntu 20.04.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1863801/+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 1487534] Re: Unable to set Alt+Shift for switching keyboard layout

[Erich Eickmeyer]

** Changed in: ubuntustudio
   Status: Won't Fix => Invalid

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

Title:
  Unable to set Alt+Shift for switching keyboard layout

Status in Ubuntu Studio:
  Invalid
Status in ibus package in Ubuntu:
  Expired

Bug description:
  I used to Alt+Shift combination for switching keyboard layouts. but I
  can't find where to do this. Right clicking on language indicator and
  choosing Preferences open IBus configuration window. But when I set
  Alt+Shift, it just hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntustudio/+bug/1487534/+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 1798450] Re: [snap] File dialogs show snap's home directory instead of user's

[Fritz Hudnut]

Just adding that this issue has recently affected my work flow trying to
upload a file to social media site in hopes of generating actual deniro
. . . but could not get my own files to show up in what I was hoping
would be my /home directory . . . but was instead a "snap" "virtual
home" directory, so that it showed as "empty" . . . ??  very disruptive
to routine uses . . . ???  I posted to wxl that if this was to prevent
me from uploading his files to my social media then that "makes sense" .
. . but to prevent me from simply uploading my own files n the system
I'm booted and logged into . . . non-sensical . . .

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

Title:
  [snap] File dialogs show snap's home directory instead of user's

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:

  - Find a web page that has a file chooser (you can just paste `` into an empty HTML page)
  - Click the "Choose File" button
  - Click "Home" if you didn't start here
  - See that Chromium uses `/home/$USER/snap/chromium/500` as the home folder

  Expected behavior:

  The file picker should use the user's home folder, not the snap's,
  because everything else would be confusing for end users.

  Versions:

  snap2.35.4+18.10
  snapd   2.35.4+18.10
  series  16
  ubuntu  18.10
  kernel  4.18.11-surface-linux-surface

  Chromium 70.0.3538.67 snap

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1798450/+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 1863801] Re: [snap] chromium crashes when file picker is called to upload files or folders

[Paul White]

** Description changed:

  First noted today, the snap version of Chromium will crash while trying
  to upload files or folders. I've noted this on my personal filespace at
- my email provider, with Google Drive and Apple's iCloud.
+ my email provider, with Google Drive and Apple's iCloud. This is on a
+ freshly booted system and I have logged out and back in again but I
+ continue to reproduce the crash each time.
  
  To reproduce
  
  Log on to Google drive: https://drive.google.com/drive/my-drive
  Click on the 'New' button
  Click on either 'File upload' or 'Folder upload'
  Chromium crashes immediately. The file/folder picker isn't displayed.
  
  I've verified that Google Chrome and Firefox can upload files to Google
- Drive.
+ Drive. I don't see this problem when using Xubuntu 20.04.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 80.0.3987.87-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: GNOME
  DRM.card0-DP-1:
-  enabled: enabled
-  dpms: On
-  status: connected
-  edid-base64: 
AP///wAdZRUCAQAAACoVAQSlNB544gywoldRnycKUFS/zwDRwLMAlQCBgIGKgQCBSgEBAjqAGHE4LUBYLEUACSUhAAAe/wAwMDAwMDAwMQogICAg/QA4Sx5TDwAKICAgICAg/ABFRjIyMGEKICAgICAgAGI=
-  modes: 1920x1080 1680x1050 1280x1024 1280x1024 1280x1024 1440x900 1280x960 
1280x800 1024x768 1024x768 1024x768 800x600 800x600 800x600 800x600 640x480 
640x480 640x480 640x480 720x400
+  enabled: enabled
+  dpms: On
+  status: connected
+  edid-base64: 
AP///wAdZRUCAQAAACoVAQSlNB544gywoldRnycKUFS/zwDRwLMAlQCBgIGKgQCBSgEBAjqAGHE4LUBYLEUACSUhAAAe/wAwMDAwMDAwMQogICAg/QA4Sx5TDwAKICAgICAg/ABFRjIyMGEKICAgICAgAGI=
+  modes: 1920x1080 1680x1050 1280x1024 1280x1024 1280x1024 1440x900 1280x960 
1280x800 1024x768 1024x768 1024x768 800x600 800x600 800x600 800x600 640x480 
640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-1:
-  enabled: disabled
-  dpms: Off
-  status: disconnected
-  edid-base64: 
-  modes:
+  enabled: disabled
+  dpms: Off
+  status: disconnected
+  edid-base64:
+  modes:
  DRM.card0-HDMI-A-2:
-  enabled: disabled
-  dpms: Off
-  status: disconnected
-  edid-base64: 
-  modes:
+  enabled: disabled
+  dpms: Off
+  status: disconnected
+  edid-base64:
+  modes:
  DRM.card0-HDMI-A-3:
-  enabled: disabled
-  dpms: Off
-  status: disconnected
-  edid-base64: 
-  modes:
+  enabled: disabled
+  dpms: Off
+  status: disconnected
+  edid-base64:
+  modes:
  DRM.card0-eDP-1:
-  enabled: enabled
-  dpms: On
-  status: connected
-  edid-base64: 
AP///wANrsQVACgXAQSVIhN4Au8FkFRSkyklUFQBAQEBAQEBAQEBAQEBAQEBXjWAlnA4FEAsHCQAWMEQAAAY/gBOMTU2SEdFLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTU2SEdFLUVBQgogAB0=
-  modes: 1920x1080
+  enabled: enabled
+  dpms: On
+  status: connected
+  edid-base64: 
AP///wANrsQVACgXAQSVIhN4Au8FkFRSkyklUFQBAQEBAQEBAQEBAQEBAQEBXjWAlnA4FEAsHCQAWMEQAAAY/gBOMTU2SEdFLUVBQgog/gBDTU4KICAgICAgICAg/gBOMTU2SEdFLUVBQgogAB0=
+  modes: 1920x1080
  Date: Tue Feb 18 20:49:46 2020
  DiskUsage:
-  Filesystem Type   Size  Used Avail Use% Mounted on
-  /dev/sda2  ext473G   17G   53G  24% /home
-  tmpfs  tmpfs  3.9G   22M  3.9G   1% /dev/shm
-  /dev/sda2  ext473G   17G   53G  24% /home
+  Filesystem Type   Size  Used Avail Use% Mounted on
+  /dev/sda2  ext473G   17G   53G  24% /home
+  tmpfs  tmpfs  3.9G   22M  3.9G   1% /dev/shm
+  /dev/sda2  ext473G   17G   53G  24% /home
  InstallationDate: Installed on 2019-05-17 (277 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  MachineType: Novatech N350DW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=35cc812a-75e8-4a5a-83d0-bd336006d2f6 ro quiet splash vt.handoff=7
  Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium'] 
failed with exit code 1: error: no changes found
  Snap.ChromeDriverVersion: ChromeDriver 80.0.3987.100 
(3f00c26d457663a424865bbef1179f72eec1b9fe-refs/branch-heads/3987@{#864})
  Snap.ChromiumVersion: Chromium 80.0.3987.100 snap
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to focal on 2019-11-08 (101 days ago)
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N350DW
  dmi.board.vendor: Novatech
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Novatech
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd03/10/2017:svnNovatech:pnN350DW:pvrNotApplicable:rvnNovatech:rnN350DW:rvrNotApplicable:cvnNovatech:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N350DW
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Novatech

-- 
You received this bug notification 

[Desktop-packages] [Bug 1863468] Re: Libreoffice Snap is not available in Turkish

[Olivier Tilloy]

The snap is currently built with a limited set of languages, see the
list here: https://git.launchpad.net/~libreoffice/+git/libreoffice-
snap/tree/snapcraft.yaml?h=6.4#n75 (--with-lang config flag). This is a
tradeoff to avoid increasing too much the size of the snap, but if there
is demand for it the Turkish translations could certainly be included
(if so it would be interesting to note the size increment here for
future reference).

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

Title:
  Libreoffice Snap is not available in Turkish

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Libreoffice Snap is not available in Turkish. Although there are many
  other language packs available, there is no Turkish language support.
  I am having difficulty using it because I do not speak English. I was
  able to write this message through Google Translate anyway. I request
  the addition of Turkish language for the Libreoffice Snap package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1863468/+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 1863801] [NEW] [snap] chromium crashes when file picker is called to upload files or folders

[Paul White]

Public bug reported:

First noted today, the snap version of Chromium will crash while trying
to upload files or folders. I've noted this on my personal filespace at
my email provider, with Google Drive and Apple's iCloud.

To reproduce

Log on to Google drive: https://drive.google.com/drive/my-drive
Click on the 'New' button
Click on either 'File upload' or 'Folder upload'
Chromium crashes immediately. The file/folder picker isn't displayed.

I've verified that Google Chrome and Firefox can upload files to Google
Drive.

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

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


** Tags: amd64 apport-bug focal snap

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

Title:
  [snap] chromium crashes when file picker is called to upload files or
  folders

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  First noted today, the snap version of Chromium will crash while
  trying to upload files or folders. I've noted this on my personal
  filespace at my email provider, with Google Drive and Apple's iCloud.

  To reproduce
  
  Log on to Google drive: https://drive.google.com/drive/my-drive
  Click on the 'New' button
  Click on either 'File upload' or 'Folder upload'
  Chromium crashes immediately. The file/folder picker isn't displayed.

  I've verified that Google Chrome and Firefox can upload files to
  Google Drive.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 80.0.3987.87-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: GNOME
  DRM.card0-DP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAdZRUCAQAAACoVAQSlNB544gywoldRnycKUFS/zwDRwLMAlQCBgIGKgQCBSgEBAjqAGHE4LUBYLEUACSUhAAAe/wAwMDAwMDAwMQogICAg/QA4Sx5TDwAKICAgICAg/ABFRjIyMGEKICAgICAgAGI=
   modes: 1920x1080 1680x1050 1280x1024 1280x1024 1280x1024 1440x900 1280x960 

[Desktop-packages] [Bug 1863714] Re: package libevdocument3-4:amd64 3.18.2-1ubuntu4.6 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd

[Sebastien Bacher]

the issue is not with evince there

dpkg: fout bij verwerken van pakket libdjvulibre-text (--configure):

** Changed in: evince (Ubuntu)
   Status: New => Invalid

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

Title:
  package libevdocument3-4:amd64 3.18.2-1ubuntu4.6 failed to
  install/upgrade: vereistenproblemen - blijft ongeconfigureerd

Status in evince package in Ubuntu:
  Invalid

Bug description:
  Don't have any

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libevdocument3-4:amd64 3.18.2-1ubuntu4.6
  ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208
  Uname: Linux 4.4.0-173-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  Date: Mon Feb 10 19:38:30 2020
  DpkgHistoryLog:
   Start-Date: 2020-02-10  19:35:55
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: libsystemd0:amd64 (229-4ubuntu21.21, 229-4ubuntu21.27), 
libsystemd0:i386 (229-4ubuntu21.21, 229-4ubuntu21.27), sudo:amd64 
(1.8.16-0ubuntu1.8, 1.8.16-0ubuntu1.9), udev:amd64 (229-4ubuntu21.21, 
229-4ubuntu21.27), libudev1:amd64 (229-4ubuntu21.21, 229-4ubuntu21.27), 
libudev1:i386 (229-4ubuntu21.21, 229-4ubuntu21.27), systemd-sysv:amd64 
(229-4ubuntu21.21, 229-4ubuntu21.27), firefox-locale-en:amd64 
(72.0.1+build1-0ubuntu0.16.04.1, 72.0.2+build1-0ubuntu0.16.04.1), 
firefox-locale-nl:amd64 (72.0.1+build1-0ubuntu0.16.04.1, 
72.0.2+build1-0ubuntu0.16.04.1), libpam-systemd:amd64 (229-4ubuntu21.21, 
229-4ubuntu21.27), systemd:amd64 (229-4ubuntu21.21, 229-4ubuntu21.27), 
firefox:amd64 (72.0.1+build1-0ubuntu0.16.04.1, 72.0.2+build1-0ubuntu0.16.04.1), 
libexiv2-14:amd64 (0.25-2.1ubuntu16.04.5, 0.25-2.1ubuntu16.04.6)
  ErrorMessage: vereistenproblemen - blijft ongeconfigureerd
  InstallationDate: Installed on 2017-02-14 (1098 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-173-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: evince
  Title: package libevdocument3-4:amd64 3.18.2-1ubuntu4.6 failed to 
install/upgrade: vereistenproblemen - blijft ongeconfigureerd
  UpgradeStatus: Upgraded to xenial on 2020-02-18 (0 days ago)

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

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

[Desktop-packages] [Bug 1856160] Re: Bar between bread crumbs and search icon.

[Sebastien Bacher]

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

** Also affects: nautilus via
   https://gitlab.gnome.org/GNOME/nautilus/issues/1387
   Importance: Unknown
   Status: Unknown

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

Title:
  Bar between bread crumbs and search icon.

Status in Nautilus:
  Unknown
Status in nautilus package in Ubuntu:
  Triaged

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

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

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

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

[Desktop-packages] [Bug 1863797] Re: gdk-pixbuf-thumbnailer fails to create thumbnails for CR2 100% of the time.

[Sebastien Bacher]

Thank you for your bug report, looks like you reported it upstream to
the wrong place though as it's a gdk-pixbuf issue rather than a gnome-
desktop one

** Changed in: gdk-pixbuf (Ubuntu)
   Importance: Undecided => Low

** Changed in: gdk-pixbuf (Ubuntu)
   Status: New => Confirmed

** Bug watch added: gitlab.gnome.org/GNOME/gnome-desktop/issues #133
   https://gitlab.gnome.org/GNOME/gnome-desktop/issues/133

** Also affects: gdk-pixbuf via
   https://gitlab.gnome.org/GNOME/gnome-desktop/issues/133
   Importance: Unknown
   Status: Unknown

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

Title:
  gdk-pixbuf-thumbnailer fails to create thumbnails for CR2 100% of the
  time.

Status in gdk-pixbuf:
  Unknown
Status in gdk-pixbuf package in Ubuntu:
  Confirmed

Bug description:
  I have been adding "image/x-xpixmap;image/x-canon-cr2;image/x-adobe-
  dng" to the end of the line starting with "MimeType=" in the file
  "/usr/share/thumbnailers/gdk-pixbuf-thumbnailer.thumbnailer" since
  Ubuntu 18.10 for the thumbnailer to create the thumbnails primarily
  for the ".CR2" raw files from my Canon 77D and 80D cameras.

  Unfortunately I have to report that as of Ubuntu 19.10 this solution doesn’t 
work on my machine anymore.
  The thumbnailer tries to create the thumbnails but fails and instead creates 
1 pixel png images that it all puts in 
"~/.cache/thumbnails/fail/gnome-thumbnail-factory".

  Is there any solution? Should I test something?

  I've attached a CR2 photo of mine that anyone can use for testing.

  I've also created a bug report on gnome gitlab here:
  https://gitlab.gnome.org/GNOME/gnome-desktop/issues/133

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1863797/+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 1863468] Re: Libreoffice Snap is not available in Turkish

[İbrahim Ethem Göl]

Although Libreoffice officially supports Turkish, there are no Turkish
among the selectable languages in Options> Language Settings> Languages>
Locale Setting in the snap package. There are a limited number of
languages in this section. There is no problem with Flatpak package and
other .deb packages. However, I would like to use the snap package for
faster and automatic updating. The Libreoffice package in the 18.04
store is too old. If Turkish language support is added to the Snap
package, many Turkish users will be grateful.

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

Title:
  Libreoffice Snap is not available in Turkish

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Libreoffice Snap is not available in Turkish. Although there are many
  other language packs available, there is no Turkish language support.
  I am having difficulty using it because I do not speak English. I was
  able to write this message through Google Translate anyway. I request
  the addition of Turkish language for the Libreoffice Snap package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1863468/+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 1859926] Re: fonts-noto-color-emoji not making pretty emojis in google chrome

[BoQsc]

Ubuntu 19.10 here.

Happens to me as well, it is possible to temporary quick-fix by
reinstalling the package. The problem comes back randomly after hours,
days, weeks.

sudo apt-get install --reinstall fonts-noto-color-emoji


Link to the related stackoverflow thread proving that problem still persist: 
https://askubuntu.com/questions/1029661/18-04-color-emoji-not-showing-up-at-all-in-chrome-only-partially-in-firefox

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

Title:
  fonts-noto-color-emoji not making pretty emojis in google chrome

Status in fonts-noto-color-emoji package in Ubuntu:
  Confirmed

Bug description:
  Google-Chrome and emoji's is being a weird headache. Something's causing it 
not to find the right font to make emoji's:
  
"[13743:1:0115/225907.016533:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1859926/+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 1863468] Re: Libreoffice Snap is not available in Turkish

[Heather Ellsworth]

What happens if you set the language to Turkish in the Tools > Options >
Language Settings > Languages > Locale Setting ?

Also, have you tried the libreoffice deb package available from apt? If
so, did that work?

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

** Changed in: libreoffice (Ubuntu)
 Assignee: (unassigned) => Heather Ellsworth (hellsworth)

** Changed in: libreoffice (Ubuntu)
   Importance: Undecided => Low

** Changed in: libreoffice (Ubuntu)
   Importance: Low => Wishlist

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

Title:
  Libreoffice Snap is not available in Turkish

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  Libreoffice Snap is not available in Turkish. Although there are many
  other language packs available, there is no Turkish language support.
  I am having difficulty using it because I do not speak English. I was
  able to write this message through Google Translate anyway. I request
  the addition of Turkish language for the Libreoffice Snap package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1863468/+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 1487534] Re: Unable to set Alt+Shift for switching keyboard layout

[anatoly techtonik]

It was Ubuntu Studio, but I switched to i3 since then.

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

Title:
  Unable to set Alt+Shift for switching keyboard layout

Status in Ubuntu Studio:
  Won't Fix
Status in ibus package in Ubuntu:
  Expired

Bug description:
  I used to Alt+Shift combination for switching keyboard layouts. but I
  can't find where to do this. Right clicking on language indicator and
  choosing Preferences open IBus configuration window. But when I set
  Alt+Shift, it just hangs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntustudio/+bug/1487534/+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 1863797] Re: gdk-pixbuf-thumbnailer fails to create thumbnails for CR2 100% of the time.

[Kristijan Žic ]

** Description changed:

  I have been adding "image/x-xpixmap;image/x-canon-cr2;image/x-adobe-dng"
  to the end of the line starting with "MimeType=" in the file
  "/usr/share/thumbnailers/gdk-pixbuf-thumbnailer.thumbnailer" since
  Ubuntu 18.10 for the thumbnailer to create the thumbnails primarily for
  the ".CR2" raw files from my Canon 77D and 80D cameras.
  
  Unfortunately I have to report that as of Ubuntu 19.10 this solution doesn’t 
work on my machine anymore.
  The thumbnailer tries to create the thumbnails but fails and instead creates 
1 pixel png images that it all puts in 
"~/.cache/thumbnails/fail/gnome-thumbnail-factory".
  
  Is there any solution? Should I test something?
  
  I've attached a CR2 photo of mine that anyone can use for testing.
+ 
+ I've also created a bug report on gnome gitlab here:
+ https://gitlab.gnome.org/GNOME/gnome-desktop/issues/133

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

Title:
  gdk-pixbuf-thumbnailer fails to create thumbnails for CR2 100% of the
  time.

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  I have been adding "image/x-xpixmap;image/x-canon-cr2;image/x-adobe-
  dng" to the end of the line starting with "MimeType=" in the file
  "/usr/share/thumbnailers/gdk-pixbuf-thumbnailer.thumbnailer" since
  Ubuntu 18.10 for the thumbnailer to create the thumbnails primarily
  for the ".CR2" raw files from my Canon 77D and 80D cameras.

  Unfortunately I have to report that as of Ubuntu 19.10 this solution doesn’t 
work on my machine anymore.
  The thumbnailer tries to create the thumbnails but fails and instead creates 
1 pixel png images that it all puts in 
"~/.cache/thumbnails/fail/gnome-thumbnail-factory".

  Is there any solution? Should I test something?

  I've attached a CR2 photo of mine that anyone can use for testing.

  I've also created a bug report on gnome gitlab here:
  https://gitlab.gnome.org/GNOME/gnome-desktop/issues/133

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1863797/+subscriptions

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

[Desktop-packages] [Bug 1856160] Re: Bar between bread crumbs and search icon.

[Clinton H]

Reported to Gnome:

https://gitlab.gnome.org/GNOME/nautilus/issues/1387

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1387
   https://gitlab.gnome.org/GNOME/nautilus/issues/1387

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

Title:
  Bar between bread crumbs and search icon.

Status in nautilus package in Ubuntu:
  Confirmed

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

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

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

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

[Desktop-packages] [Bug 1863797] [NEW] gdk-pixbuf-thumbnailer fails to create thumbnails for CR2 100% of the time.

[Kristijan Žic ]

Public bug reported:

I have been adding "image/x-xpixmap;image/x-canon-cr2;image/x-adobe-dng"
to the end of the line starting with "MimeType=" in the file
"/usr/share/thumbnailers/gdk-pixbuf-thumbnailer.thumbnailer" since
Ubuntu 18.10 for the thumbnailer to create the thumbnails primarily for
the ".CR2" raw files from my Canon 77D and 80D cameras.

Unfortunately I have to report that as of Ubuntu 19.10 this solution doesn’t 
work on my machine anymore.
The thumbnailer tries to create the thumbnails but fails and instead creates 1 
pixel png images that it all puts in 
"~/.cache/thumbnails/fail/gnome-thumbnail-factory".

Is there any solution? Should I test something?

I've attached a CR2 photo of mine that anyone can use for testing.

** Affects: gdk-pixbuf (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "IMG_1716.CR2"
   
https://bugs.launchpad.net/bugs/1863797/+attachment/5329360/+files/IMG_1716.CR2

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

Title:
  gdk-pixbuf-thumbnailer fails to create thumbnails for CR2 100% of the
  time.

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  I have been adding "image/x-xpixmap;image/x-canon-cr2;image/x-adobe-
  dng" to the end of the line starting with "MimeType=" in the file
  "/usr/share/thumbnailers/gdk-pixbuf-thumbnailer.thumbnailer" since
  Ubuntu 18.10 for the thumbnailer to create the thumbnails primarily
  for the ".CR2" raw files from my Canon 77D and 80D cameras.

  Unfortunately I have to report that as of Ubuntu 19.10 this solution doesn’t 
work on my machine anymore.
  The thumbnailer tries to create the thumbnails but fails and instead creates 
1 pixel png images that it all puts in 
"~/.cache/thumbnails/fail/gnome-thumbnail-factory".

  Is there any solution? Should I test something?

  I've attached a CR2 photo of mine that anyone can use for testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1863797/+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 1856927] Re: totem crashed with SIGSEGV in build_flavored_key() from insert_key_mapping()

[Bill (franksmcb)]

@seb128 this is working correctly now after the grilo update.
Thanks

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

Title:
  totem crashed with SIGSEGV in build_flavored_key() from
  insert_key_mapping()

Status in Grilo Plugins:
  Fix Released
Status in grilo-plugins package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/55095074fb3c3335c19f63f3c91d3a8231be2034

  ---

  Test case:
  Fresh 20.04 install, updated
  Open totem
  What happens: segfault

  Installing grilo-plugins-0.3-extra allows totem to open fine.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: totem 3.34.1-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu14
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 18 19:51:40 2019
  ExecutablePath: /usr/bin/totem
  ExecutableTimestamp: 1570435741
  InstallationDate: Installed on 2019-12-19 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcCwd: /home/doug
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f76b92f6dd6:movzbl (%rax),%eax
   PC (0x7f76b92f6dd6) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so
   grl_tracker_setup_key_mappings () from 
/usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so
   ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so
   ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so
   ?? () from /lib/x86_64-linux-gnu/libtracker-sparql-2.0.so.0
  Title: totem crashed with SIGSEGV in grl_tracker_setup_key_mappings()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/grilo-plugins/+bug/1856927/+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 1855434] Re: Vino VNC connection has wrong keyboard layout

[Peter Valdemar Mørch]

Oh, and I just tried x11vnc. It does *not* have this problem. I'm pretty
sure this is a vino problem.

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

Title:
  Vino VNC connection has wrong keyboard layout

Status in vino package in Ubuntu:
  Confirmed

Bug description:
  After upgrading a machine from 16.04.3 LTS to 18.04.3 Vino VNC connections 
use the wrong keyboard layout.
  By default I use "DE" keyboard layout.

  If I connect from another 18.04.3 machine to said vino on the upgraded 
18.04.3 machine, the keyboard layout seems to be "kind of" US, not other keys 
are as well not correct.
  I can only fix this by running
   sudo dpkg-reconfigure keyboard-configuration
  in a console (pressing Enter all the way through and confirm settings) and 
rebooting. If I connect to vino VNC after issueing this command and rebooting, 
the layout is correct until next reboot. Then I have to issue this command 
again and so on.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vino 3.22.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Dec  6 12:52:22 2019
  InstallationDate: Installed on 2017-12-29 (707 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: vino
  UpgradeStatus: Upgraded to bionic on 2019-10-29 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1855434/+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 1855434] Re: Vino VNC connection has wrong keyboard layout

[Peter Valdemar Mørch]

I'm using Xubuntu (XFCE) version 18.04 on both ends.

sudo dpkg-reconfigure keyboard-configuration

is configured for a danish keyboard on both ends.

Hitting the 'æ' key in a terminal on the local side produces an 'æ' in
the terminal.

Hitting the 'æ' key in a terminal on the remote vnc side produces an ';'
in the terminal. The placement of an 'æ' on a danish keyboard is in the
same place as ';' on a US keyboard (I think).

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

Title:
  Vino VNC connection has wrong keyboard layout

Status in vino package in Ubuntu:
  Confirmed

Bug description:
  After upgrading a machine from 16.04.3 LTS to 18.04.3 Vino VNC connections 
use the wrong keyboard layout.
  By default I use "DE" keyboard layout.

  If I connect from another 18.04.3 machine to said vino on the upgraded 
18.04.3 machine, the keyboard layout seems to be "kind of" US, not other keys 
are as well not correct.
  I can only fix this by running
   sudo dpkg-reconfigure keyboard-configuration
  in a console (pressing Enter all the way through and confirm settings) and 
rebooting. If I connect to vino VNC after issueing this command and rebooting, 
the layout is correct until next reboot. Then I have to issue this command 
again and so on.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vino 3.22.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Dec  6 12:52:22 2019
  InstallationDate: Installed on 2017-12-29 (707 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: vino
  UpgradeStatus: Upgraded to bionic on 2019-10-29 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1855434/+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 1725180] Re: Shell animations are not smooth

[Bug Watch Updater]

** Changed in: gjs
   Status: New => Fix Released

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

Title:
  Shell animations are not smooth

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

Bug description:
  Upstream fixes required to make all the overview/window/icon
  animations much smoother (at least halving render times):

  https://gitlab.gnome.org/GNOME/gjs/merge_requests/390
  https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/948
  https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/936
  https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/949

  __

  +++UBUNTU RELEASE+++

  Description:  Ubuntu 17.10
  Release:  17.10

  +++PACKAGE VERSION+++

  xwayland:
    Installed: 2:1.19.5-0ubuntu2
    Candidate: 2:1.19.5-0ubuntu2
    Version table:
   *** 2:1.19.5-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  Bug found on Dell XPS 9560 4K model with GTX1050/Intel HD 630.
  Currently using Intel HD Graphics 630 as Nvidia seems to have no
  support for xwayland.

  The window/dock/launcher animations are lagging/shaky (not smooth).

  __

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xwayland 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 19:09:27 2017
  DistUpgraded: 2017-10-20 04:51:46,123 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-387, 387.12, 4.13.0-16-generic, x86_64: installed
   v4l2loopback, 0.10.0, 4.10.0-37-generic, x86_64: installed
   v4l2loopback, 0.10.0, 4.13.0-16-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:07be]
     Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
  InstallationDate: Installed on 2017-05-24 (149 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc.
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=38514616-2735-4966-91f7-71f1d60beb73 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 08/30/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/gjs/+bug/1725180/+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 1855434] Re: Vino VNC connection has wrong keyboard layout

[Launchpad Bug Tracker]

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

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

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

Title:
  Vino VNC connection has wrong keyboard layout

Status in vino package in Ubuntu:
  Confirmed

Bug description:
  After upgrading a machine from 16.04.3 LTS to 18.04.3 Vino VNC connections 
use the wrong keyboard layout.
  By default I use "DE" keyboard layout.

  If I connect from another 18.04.3 machine to said vino on the upgraded 
18.04.3 machine, the keyboard layout seems to be "kind of" US, not other keys 
are as well not correct.
  I can only fix this by running
   sudo dpkg-reconfigure keyboard-configuration
  in a console (pressing Enter all the way through and confirm settings) and 
rebooting. If I connect to vino VNC after issueing this command and rebooting, 
the layout is correct until next reboot. Then I have to issue this command 
again and so on.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vino 3.22.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Dec  6 12:52:22 2019
  InstallationDate: Installed on 2017-12-29 (707 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: vino
  UpgradeStatus: Upgraded to bionic on 2019-10-29 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1855434/+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 1863785] [NEW] Error adding rows to data table

[Cliff Carson]

Public bug reported:

Have a simple two item chart and when I try to add rows to the data
table the columns expand.  Display the data table and try to move the
cursor to the bottom so that I can add a row and as soon as I go to the
second row two empty columns are added.  When I get to the bottom the
screen fills with empty columns.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libreoffice-impress 1:6.4.0-0ubuntu4
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 18 12:01:31 2020
InstallationDate: Installed on 2019-11-12 (98 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191112)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Try to add rows to the Volvo V60 Mileage chart"
   
https://bugs.launchpad.net/bugs/1863785/+attachment/5329340/+files/UsageCharts.odp

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

Title:
  Error adding rows to data table

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Have a simple two item chart and when I try to add rows to the data
  table the columns expand.  Display the data table and try to move the
  cursor to the bottom so that I can add a row and as soon as I go to
  the second row two empty columns are added.  When I get to the bottom
  the screen fills with empty columns.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-impress 1:6.4.0-0ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 18 12:01:31 2020
  InstallationDate: Installed on 2019-11-12 (98 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191112)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1863785/+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 1772537] Re: Wrong combining sequence in Compose for the Finnish locale

[Bug Watch Updater]

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

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

Title:
  Wrong combining sequence in Compose for the Finnish locale

Status in xlibs:
  New
Status in libx11 package in Ubuntu:
  Triaged

Bug description:
  The Compose file for the fi_FI.UTF-8 locale at
  /usr/share/X11/locale/fi_FI.UTF-8/Compose contains the following
  lines:

  :  "Ệ"  U1EC6  #  LATIN CAPITAL 
LETTER E WITH CIRCUMFLEX AND ACUTE
   :  "Ệ"  U1EC6  #  LATIN CAPITAL 
LETTER E WITH CIRCUMFLEX AND DOT BELOW

  Thus the codepoint "Ệ" U1EC6 is produced with two different sequences.
  Based on the key sequences and the comments at the ends of the lines,
  it is clear that the first line is a mistake. Instead of "Ệ"  U1EC6,
  the line should read "Ế"  U1EBE, a character which cannot be produced
  with the current Compose file otherwise at all.

  Description:  Ubuntu 17.10
  Release:  17.10

  libx11-data:
Installed: 2:1.6.4-3
Candidate: 2:1.6.4-3
Version table:
   *** 2:1.6.4-3 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://mr.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/xlibs/+bug/1772537/+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 1863724] Re: Add missing pci-id's for Comet Lake (CML)

[Timo Aaltonen]

** Changed in: mesa (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: mesa (Ubuntu Eoan)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Add missing pci-id's for Comet Lake (CML)

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Bionic:
  New
Status in mesa source package in Eoan:
  New

Bug description:
  [Impact]

  After rebasing mesa to 19.2.x debian/patches/i965-sync-pciids.diff was
  updated but some parts of it got accidentally dropped, losing a couple
  of pci-id's for CML. They need to be restored.

  [Test case]

  Install the updates on an affected machine, check with glxinfo -B that
  the proper driver is loaded.

  [Regression potential]

  none, this just adds pci-id's

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1863724/+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 1863733] Re: Bubblewrap upstream-as-root test fails on libcap2 1:2.31-1 and later

[Sebastien Bacher]

Bisecting the failing it started with this commit
https://git.kernel.org/pub/scm/libs/libcap/libcap.git/commit/?id=afef3ef1

'Change the definition of 'all' to be all named capabilities.
[This will be included in libcap-2.29.]

This change concerns the text formating functions:

  C:  cap_to_text(), cap_from_text()
 Go:  cap.FromText() and cap.Set.String()

Prior to this commit, "all" meant every bit of the capability vector
was raised - both named, and unnamed capabilities.'

** Bug watch added: github.com/containers/bubblewrap/issues #353
   https://github.com/containers/bubblewrap/issues/353

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

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

Status in bubblewrap package in Ubuntu:
  New
Status in libcap2 package in Ubuntu:
  New

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

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

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

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

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

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

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

[Sebastien Bacher]

Reported to bubblewrap upstream on
https://github.com/containers/bubblewrap/issues/353 let's see what they
say

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

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

Status in bubblewrap package in Ubuntu:
  New
Status in libcap2 package in Ubuntu:
  New

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

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

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

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

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

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

[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

[Jan Dageförde]

There is an upstream issue in PulseAudio:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/776.

** Bug watch added: PulseAudio #776
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/776

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+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 1848951] Re: High CPU when just moving the mouse

[Martin Wimpress]

** Tags removed: champagne

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

Title:
  High CPU when just moving the mouse

Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I have installed fresh Ubuntu 18.04.03 on my PC. Previously I had
  Ubuntu 16.04 version but didn't have any such problems with the cpu
  usage.

  But I have saw in terminal that somehow the processes Xorg and gnome-
  shell use always 20% when just moving the mouse around for 18.04
  version.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 20:54:50 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / 
R7 250X] [1002:683d] (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 
[1462:2710]
  InstallationDate: Installed on 2019-10-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D2V
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D2V
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1848951/+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 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic

[Richard Smith]

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

Same with a Bose Noise Canceling 700. Have the profile but nothing shows
up on the list of capture devices.

Device 60:AB:D2:02:00:B4 (public)
Name: Bose NC 700 HP
Alias: Bose NC 700 HP
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Vendor specific   (-deca-fade-deca-deafdecacaff)
UUID: Serial Port   (1101--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: Vendor specific   (81c2e72a-0591-443e-a1ff-05f988593351)
UUID: Vendor specific   (931c7e8a-540f-4686-b798-e8df0a2ad9f7)
UUID: Vendor specific   (f8d1fbe4-7966-4334-8024-ff96c9330e15)
Modalias: bluetooth:v009Ep4024d1211
ManufacturerData Key: 0x0f03
ManufacturerData Value:
  c2 12 8c c8 86 2f 04 73  ./.s
ServiceData Key: fe2c--1000-8000-00805f9b34fb
ServiceData Value:
  84 c3 1b ...

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

Title:
  Bluetooth headset HSP/HFP mode not working in Bionic

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  There is a previous bug with almost the same title, but for Xenial
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I
  have had this issue in Artful, and when commented on the old bug, I
  was asked to raise a new one instead. I waited to see if Bionic fixed
  it for me, but it does not seem to work still. So!

  Steps to reproduce:
  1. enable bluetooth on computer and switch on the headset.
  2. pair and connect the headset
  3. go to settings to switch headset to HSP/HFP mode to enable mic
  4. save and close window.

  Expected behaviour:
  1. mic should be enabled and headset should be usable to attend calls on 
laptop.

  Behaviour in error:
  1. Headset profile switches back to A2DP and mic is not enabled.

  I am using a generic bluetooth headset on a fresh updated Kubuntu
  18.04 bionic with plasma DE.

  Software versions:
  Kernel: 4.15.0-20-generic
  Bluez version: 5.48-0ubuntu3
  pulseaudio: 1:11.1-1ubuntu7
  pulseaudio-module-bluetooth: 1:11.1-1ubuntu7

  
  Additional information:
  Running "pacmd list-cards" says that HSF/HFP is 'not available' on the 
headset:

  Output from Headset section:
  profiles:
  a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, 
available: unknown)
  headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, 
available: no)
  off: Off (priority 0, available: yes)
  active profile: 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

[Martin Wimpress]

** Tags removed: champagne
** Tags added: desktop-lts-wishlist rls-ff-notfixing

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+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 1860540] Re: Password entry has no way of displaying what you type

[Treviño]

It's actually fixed also in previous version, just right-click the entry
(or press down-arrow) and you will be able to see the password.

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

Title:
  Password entry has no way of displaying what you type

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

Bug description:
  In Focal the network password / passphrase entry form has no way of
  displaying what is being typed.

  I'd expect a checkbox or something...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.442
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CasperVersion: 1.438
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 22 11:13:41 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1860540/+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 1861310] Re: Overlay with shortcut numbers not showing on dock with pressing Super+0 or Super+Q

[Martin Wimpress]

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

** Tags removed: champagne

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

Title:
  Overlay with shortcut numbers not showing on dock with pressing
  Super+0 or Super+Q

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

Bug description:
  The dock no longer shows the overlay with digits corresponding to
  shortcuts to launch apps (with ). It stopped appearing after I
  upgraded to Eoan.

  The numbers are show neither with q nor by holding .
  Unlike #1846718, no overlay appears when hitting +0 either (or
  some other number), although the corresponding item is
  launched/focused.

  I have tried changing a number of things in org.gnome.shell.extensions
  .dash-to-dock, including setting hot-keys to false, as advised
  [here](https://askubuntu.com/questions/1082772/keyboard-shortcut-for-
  launching-application-from-dock-in-ubuntu-18). Alas, I couldn't make
  it work.

  Not sure if it matters, but this is the second upgrade (install was on
  Cosmic originally). Here is the output of some commands that may be
  relevant:

  $ gsettings get org.gnome.shell enabled-extensions
  ['appindicatorsupp...@rgcjonas.gmail.com', 'gnomeGlobalAppMenu@lestcape', 
'systemmoni...@gnome-shell-extensions.gcampax.github.com', 
'remove-activities-but...@missoft.fr', 
'notifications-alert-on-user-m...@hackedbellini.gmail.com', 
'ubuntu-appindicat...@ubuntu.com', 
'alternate-...@gnome-shell-extensions.gcampax.github.com', 
'custom-hot-corn...@janrunx.gmail.com', 'openweather-extens...@jenslody.de', 
'OverviewAllWindows@amiller27', 'system-moni...@paradoxxx.zero.gmail.com', 
'clipboard-indica...@tudmotu.com', 'gTile@vibou', 
'hide-activities-but...@gnome-shell-extensions.bookmarkd.xyz', 
'ubuntu-d...@ubuntu.com', 
'drive-m...@gnome-shell-extensions.gcampax.github.com']

  $ ls ~/.local/share/gnome-shell/extensions/
  alternate-...@gnome-shell-extensions.gcampax.github.com
  clipboard-indica...@tudmotu.com
  custom-hot-corn...@janrunx.gmail.com
  drive-m...@gnome-shell-extensions.gcampax.github.com
  gTile@vibou
  hide-activities-but...@gnome-shell-extensions.bookmarkd.xyz
  notifications-alert-on-user-m...@hackedbellini.gmail.com
  openweather-extens...@jenslody.de
  system-moni...@paradoxxx.zero.gmail.com

  $ ls /usr/share/gnome-shell/extensions/
  apps-m...@gnome-shell-extensions.gcampax.github.com
  auto-move-wind...@gnome-shell-extensions.gcampax.github.com
  desktop-icons@csoriano
  drive-m...@gnome-shell-extensions.gcampax.github.com
  horizontal-workspa...@gnome-shell-extensions.gcampax.github.com
  launch-new-insta...@gnome-shell-extensions.gcampax.github.com
  native-window-placem...@gnome-shell-extensions.gcampax.github.com
  places-m...@gnome-shell-extensions.gcampax.github.com
  screenshot-window-si...@gnome-shell-extensions.gcampax.github.com
  ubuntu-appindicat...@ubuntu.com
  ubuntu-d...@ubuntu.com
  user-th...@gnome-shell-extensions.gcampax.github.com
  window-l...@gnome-shell-extensions.gcampax.github.com
  windowsnaviga...@gnome-shell-extensions.gcampax.github.com
  workspace-indica...@gnome-shell-extensions.gcampax.github.com

  $ gsettings list-recursively org.gnome.shell.extensions.dash-to-dock
  org.gnome.shell.extensions.dash-to-dock transparency-mode 'FIXED'
  org.gnome.shell.extensions.dash-to-dock shortcut-text 'q'
  org.gnome.shell.extensions.dash-to-dock apply-custom-theme false
  org.gnome.shell.extensions.dash-to-dock show-favorites true
  org.gnome.shell.extensions.dash-to-dock click-action 'focus-or-previews'
  org.gnome.shell.extensions.dash-to-dock app-hotkey-9 ['9']
  org.gnome.shell.extensions.dash-to-dock custom-background-color false
  org.gnome.shell.extensions.dash-to-dock app-shift-hotkey-1 ['1']
  org.gnome.shell.extensions.dash-to-dock multi-monitor false
  org.gnome.shell.extensions.dash-to-dock height-fraction 0.90002
  org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-1 ['1']
  org.gnome.shell.extensions.dash-to-dock isolate-workspaces false
  org.gnome.shell.extensions.dash-to-dock shift-click-action 'launch'
  org.gnome.shell.extensions.dash-to-dock shortcut-timeout 2.0
  org.gnome.shell.extensions.dash-to-dock show-delay 0.25
  org.gnome.shell.extensions.dash-to-dock custom-theme-shrink true
  org.gnome.shell.extensions.dash-to-dock app-shift-hotkey-2 ['2']
  org.gnome.shell.extensions.dash-to-dock show-windows-preview true
  org.gnome.shell.extensions.dash-to-dock show-trash true
  org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-2 ['2']
  org.gnome.shell.extensions.dash-to-dock autohide-in-fullscreen false
  org.gnome.shell.extensions.dash-to-dock icon-size-fixed true
  org.gnome.shell.extensions.dash-to-dock scroll-action 'switch-workspace'
  

[Desktop-packages] [Bug 1862531] Re: [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use

[Sebastien Bacher]

The wayland session isn't a critical feature, that doesn't need to be
rls tracked

** Tags added: rls-ff-notfixing

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

Title:
  [focal] Wayland session is not available when a laptop has an Nvidia
  card an Intel card is in use

Status in gdm3 package in Ubuntu:
  Incomplete
Status in nvidia-prime package in Ubuntu:
  Invalid

Bug description:
  A Wayland session present at /usr/share/wayland-sessions/ubuntu-
  wayland.desktop is not displayed at the login screen when a system has
  an iGPU (Intel) and dGPU (Nvidia) and Intel iGPU is used:

  prime-select query 
  intel

  Only sessions at /usr/share/xsessions are present.

  
  ➜  ~ ls /usr/share/xsessions 
  remmina-gnome.desktop  ubuntu.desktop

  ➜  ~ ls /usr/share/wayland-sessions 
  ubuntu-wayland.desktop

  
  The root cause is the existence of a udev rule in 61-gdm.rules that runs 
gdm-disable-wayland when an nvidia driver is loaded in combination with LP: 
#1848326 (see this comment specifically 
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/comments/7).

  dpkg -S /lib/udev/rules.d/61-gdm.rules 
  gdm3: /lib/udev/rules.d/61-gdm.rules

  grep nvidia /lib/udev/rules.d/61-gdm.rules
  # disable Wayland when using the proprietary nvidia driver
  DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"

  When I comment it out and reboot, I get the right menu entry and am
  able to observe the right session type:

  ➜  ~ grep nvidia /lib/udev/rules.d/61-gdm.rules
  # disable Wayland when using the proprietary nvidia driver
  #DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"

  ➜  ~ loginctl
  SESSION  UID USER SEAT  TTY 
2 1000 dima seat0 tty2

  1 sessions listed.

  ➜  ~ loginctl show-session 2 -p Type
  Type=wayland

  
  System info:

  
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  Codename: focal

  
  ➜  ~ dpkg -l | grep gdm3
  ii  gdm3  3.34.1-1ubuntu1 
   amd64GNOME Display Manager

  ➜  ~ dpkg -l | grep nvidia-prime
  ii  nvidia-prime  0.8.13  
   all  Tools to enable NVIDIA's Prime

  ➜  ~ dpkg -l | grep nvidia-driver
  ii  nvidia-driver-440 440.59-0ubuntu1 
   amd64NVIDIA driver metapackage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862531/+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 1860540] Re: Password entry has no way of displaying what you type

[Martin Wimpress]

** Tags removed: champagne

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

Title:
  Password entry has no way of displaying what you type

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

Bug description:
  In Focal the network password / passphrase entry form has no way of
  displaying what is being typed.

  I'd expect a checkbox or something...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.442
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CasperVersion: 1.438
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 22 11:13:41 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1860540/+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 1860540] Re: Password entry has no way of displaying what you type

[Sebastien Bacher]

** Tags added: rls-ff-notfixing

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

Title:
  Password entry has no way of displaying what you type

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

Bug description:
  In Focal the network password / passphrase entry form has no way of
  displaying what is being typed.

  I'd expect a checkbox or something...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.442
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CasperVersion: 1.438
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 22 11:13:41 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1860540/+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 1861310] Re: Overlay with shortcut numbers not showing on dock with pressing Super+0 or Super+Q

[Iain Lane]

** Tags removed: champagne

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

Title:
  Overlay with shortcut numbers not showing on dock with pressing
  Super+0 or Super+Q

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

Bug description:
  The dock no longer shows the overlay with digits corresponding to
  shortcuts to launch apps (with ). It stopped appearing after I
  upgraded to Eoan.

  The numbers are show neither with q nor by holding .
  Unlike #1846718, no overlay appears when hitting +0 either (or
  some other number), although the corresponding item is
  launched/focused.

  I have tried changing a number of things in org.gnome.shell.extensions
  .dash-to-dock, including setting hot-keys to false, as advised
  [here](https://askubuntu.com/questions/1082772/keyboard-shortcut-for-
  launching-application-from-dock-in-ubuntu-18). Alas, I couldn't make
  it work.

  Not sure if it matters, but this is the second upgrade (install was on
  Cosmic originally). Here is the output of some commands that may be
  relevant:

  $ gsettings get org.gnome.shell enabled-extensions
  ['appindicatorsupp...@rgcjonas.gmail.com', 'gnomeGlobalAppMenu@lestcape', 
'systemmoni...@gnome-shell-extensions.gcampax.github.com', 
'remove-activities-but...@missoft.fr', 
'notifications-alert-on-user-m...@hackedbellini.gmail.com', 
'ubuntu-appindicat...@ubuntu.com', 
'alternate-...@gnome-shell-extensions.gcampax.github.com', 
'custom-hot-corn...@janrunx.gmail.com', 'openweather-extens...@jenslody.de', 
'OverviewAllWindows@amiller27', 'system-moni...@paradoxxx.zero.gmail.com', 
'clipboard-indica...@tudmotu.com', 'gTile@vibou', 
'hide-activities-but...@gnome-shell-extensions.bookmarkd.xyz', 
'ubuntu-d...@ubuntu.com', 
'drive-m...@gnome-shell-extensions.gcampax.github.com']

  $ ls ~/.local/share/gnome-shell/extensions/
  alternate-...@gnome-shell-extensions.gcampax.github.com
  clipboard-indica...@tudmotu.com
  custom-hot-corn...@janrunx.gmail.com
  drive-m...@gnome-shell-extensions.gcampax.github.com
  gTile@vibou
  hide-activities-but...@gnome-shell-extensions.bookmarkd.xyz
  notifications-alert-on-user-m...@hackedbellini.gmail.com
  openweather-extens...@jenslody.de
  system-moni...@paradoxxx.zero.gmail.com

  $ ls /usr/share/gnome-shell/extensions/
  apps-m...@gnome-shell-extensions.gcampax.github.com
  auto-move-wind...@gnome-shell-extensions.gcampax.github.com
  desktop-icons@csoriano
  drive-m...@gnome-shell-extensions.gcampax.github.com
  horizontal-workspa...@gnome-shell-extensions.gcampax.github.com
  launch-new-insta...@gnome-shell-extensions.gcampax.github.com
  native-window-placem...@gnome-shell-extensions.gcampax.github.com
  places-m...@gnome-shell-extensions.gcampax.github.com
  screenshot-window-si...@gnome-shell-extensions.gcampax.github.com
  ubuntu-appindicat...@ubuntu.com
  ubuntu-d...@ubuntu.com
  user-th...@gnome-shell-extensions.gcampax.github.com
  window-l...@gnome-shell-extensions.gcampax.github.com
  windowsnaviga...@gnome-shell-extensions.gcampax.github.com
  workspace-indica...@gnome-shell-extensions.gcampax.github.com

  $ gsettings list-recursively org.gnome.shell.extensions.dash-to-dock
  org.gnome.shell.extensions.dash-to-dock transparency-mode 'FIXED'
  org.gnome.shell.extensions.dash-to-dock shortcut-text 'q'
  org.gnome.shell.extensions.dash-to-dock apply-custom-theme false
  org.gnome.shell.extensions.dash-to-dock show-favorites true
  org.gnome.shell.extensions.dash-to-dock click-action 'focus-or-previews'
  org.gnome.shell.extensions.dash-to-dock app-hotkey-9 ['9']
  org.gnome.shell.extensions.dash-to-dock custom-background-color false
  org.gnome.shell.extensions.dash-to-dock app-shift-hotkey-1 ['1']
  org.gnome.shell.extensions.dash-to-dock multi-monitor false
  org.gnome.shell.extensions.dash-to-dock height-fraction 0.90002
  org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-1 ['1']
  org.gnome.shell.extensions.dash-to-dock isolate-workspaces false
  org.gnome.shell.extensions.dash-to-dock shift-click-action 'launch'
  org.gnome.shell.extensions.dash-to-dock shortcut-timeout 2.0
  org.gnome.shell.extensions.dash-to-dock show-delay 0.25
  org.gnome.shell.extensions.dash-to-dock custom-theme-shrink true
  org.gnome.shell.extensions.dash-to-dock app-shift-hotkey-2 ['2']
  org.gnome.shell.extensions.dash-to-dock show-windows-preview true
  org.gnome.shell.extensions.dash-to-dock show-trash true
  org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-2 ['2']
  org.gnome.shell.extensions.dash-to-dock autohide-in-fullscreen false
  org.gnome.shell.extensions.dash-to-dock icon-size-fixed true
  org.gnome.shell.extensions.dash-to-dock scroll-action 'switch-workspace'
  org.gnome.shell.extensions.dash-to-dock shift-middle-click-action 'minimize'
  org.gnome.shell.extensions.dash-to-dock 

[Desktop-packages] [Bug 1861310] Re: Overlay with shortcut numbers not showing on dock with pressing Super+0 or Super+Q

[Sebastien Bacher]

** Tags added: champagne rls-ff-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/1861310

Title:
  Overlay with shortcut numbers not showing on dock with pressing
  Super+0 or Super+Q

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

Bug description:
  The dock no longer shows the overlay with digits corresponding to
  shortcuts to launch apps (with ). It stopped appearing after I
  upgraded to Eoan.

  The numbers are show neither with q nor by holding .
  Unlike #1846718, no overlay appears when hitting +0 either (or
  some other number), although the corresponding item is
  launched/focused.

  I have tried changing a number of things in org.gnome.shell.extensions
  .dash-to-dock, including setting hot-keys to false, as advised
  [here](https://askubuntu.com/questions/1082772/keyboard-shortcut-for-
  launching-application-from-dock-in-ubuntu-18). Alas, I couldn't make
  it work.

  Not sure if it matters, but this is the second upgrade (install was on
  Cosmic originally). Here is the output of some commands that may be
  relevant:

  $ gsettings get org.gnome.shell enabled-extensions
  ['appindicatorsupp...@rgcjonas.gmail.com', 'gnomeGlobalAppMenu@lestcape', 
'systemmoni...@gnome-shell-extensions.gcampax.github.com', 
'remove-activities-but...@missoft.fr', 
'notifications-alert-on-user-m...@hackedbellini.gmail.com', 
'ubuntu-appindicat...@ubuntu.com', 
'alternate-...@gnome-shell-extensions.gcampax.github.com', 
'custom-hot-corn...@janrunx.gmail.com', 'openweather-extens...@jenslody.de', 
'OverviewAllWindows@amiller27', 'system-moni...@paradoxxx.zero.gmail.com', 
'clipboard-indica...@tudmotu.com', 'gTile@vibou', 
'hide-activities-but...@gnome-shell-extensions.bookmarkd.xyz', 
'ubuntu-d...@ubuntu.com', 
'drive-m...@gnome-shell-extensions.gcampax.github.com']

  $ ls ~/.local/share/gnome-shell/extensions/
  alternate-...@gnome-shell-extensions.gcampax.github.com
  clipboard-indica...@tudmotu.com
  custom-hot-corn...@janrunx.gmail.com
  drive-m...@gnome-shell-extensions.gcampax.github.com
  gTile@vibou
  hide-activities-but...@gnome-shell-extensions.bookmarkd.xyz
  notifications-alert-on-user-m...@hackedbellini.gmail.com
  openweather-extens...@jenslody.de
  system-moni...@paradoxxx.zero.gmail.com

  $ ls /usr/share/gnome-shell/extensions/
  apps-m...@gnome-shell-extensions.gcampax.github.com
  auto-move-wind...@gnome-shell-extensions.gcampax.github.com
  desktop-icons@csoriano
  drive-m...@gnome-shell-extensions.gcampax.github.com
  horizontal-workspa...@gnome-shell-extensions.gcampax.github.com
  launch-new-insta...@gnome-shell-extensions.gcampax.github.com
  native-window-placem...@gnome-shell-extensions.gcampax.github.com
  places-m...@gnome-shell-extensions.gcampax.github.com
  screenshot-window-si...@gnome-shell-extensions.gcampax.github.com
  ubuntu-appindicat...@ubuntu.com
  ubuntu-d...@ubuntu.com
  user-th...@gnome-shell-extensions.gcampax.github.com
  window-l...@gnome-shell-extensions.gcampax.github.com
  windowsnaviga...@gnome-shell-extensions.gcampax.github.com
  workspace-indica...@gnome-shell-extensions.gcampax.github.com

  $ gsettings list-recursively org.gnome.shell.extensions.dash-to-dock
  org.gnome.shell.extensions.dash-to-dock transparency-mode 'FIXED'
  org.gnome.shell.extensions.dash-to-dock shortcut-text 'q'
  org.gnome.shell.extensions.dash-to-dock apply-custom-theme false
  org.gnome.shell.extensions.dash-to-dock show-favorites true
  org.gnome.shell.extensions.dash-to-dock click-action 'focus-or-previews'
  org.gnome.shell.extensions.dash-to-dock app-hotkey-9 ['9']
  org.gnome.shell.extensions.dash-to-dock custom-background-color false
  org.gnome.shell.extensions.dash-to-dock app-shift-hotkey-1 ['1']
  org.gnome.shell.extensions.dash-to-dock multi-monitor false
  org.gnome.shell.extensions.dash-to-dock height-fraction 0.90002
  org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-1 ['1']
  org.gnome.shell.extensions.dash-to-dock isolate-workspaces false
  org.gnome.shell.extensions.dash-to-dock shift-click-action 'launch'
  org.gnome.shell.extensions.dash-to-dock shortcut-timeout 2.0
  org.gnome.shell.extensions.dash-to-dock show-delay 0.25
  org.gnome.shell.extensions.dash-to-dock custom-theme-shrink true
  org.gnome.shell.extensions.dash-to-dock app-shift-hotkey-2 ['2']
  org.gnome.shell.extensions.dash-to-dock show-windows-preview true
  org.gnome.shell.extensions.dash-to-dock show-trash true
  org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-2 ['2']
  org.gnome.shell.extensions.dash-to-dock autohide-in-fullscreen false
  org.gnome.shell.extensions.dash-to-dock icon-size-fixed true
  org.gnome.shell.extensions.dash-to-dock scroll-action 'switch-workspace'
  org.gnome.shell.extensions.dash-to-dock shift-middle-click-action 'minimize'
  org.gnome.shell.extensions.dash-to-dock 

[Desktop-packages] [Bug 1861913] Re: "Strict" tracking protection sometimes causes _all_ content to fail to display on browser launch

[Dan Watkins]

This just happened again (on 73.0+build3-0ubuntu1) and I've noticed that
the issue appears to apply _per window_.  So if I launch Firefox and
this is happening, then I can open a new window and, provided I don't
open any websites, the menus function correctly (to allow me to disable
Strict tracking protection).  Once disabled, tabs within the first
window still fail to display content (until the browser is restarted),
but tabs within a new window work as expected (without a restart).

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

Title:
  "Strict" tracking protection sometimes causes _all_ content to fail to
  display on browser launch

Status in firefox package in Ubuntu:
  New

Bug description:
  This morning I booted my machine and launched Firefox.  I restored my
  tabs from my previous session, and _none of them_ displayed any
  content.  The tabs included pins, regular sites, and extension dialogs
  (specifically, a couple of instances of the LastPass 2FA prompt).
  Further to that, Firefox menus also wouldn't display; either via
  right-click on tabs, or via the "hamburger" menu in the top-right.  (I
  could still close tabs via Ctrl-W for non-pinned tabs, or via middle-
  click for pinned tabs.)

  favicons were displayed correctly, and I confirmed that the pages were
  actually being fetched from the remote sites because I typed the
  address for a page I know redirects and the redirect happened
  (specifically, "!g foo" in my address bar caused DuckDuckGo to
  redirect me to Google).

  Restarting the browser did not fix this.  Closing all of my tabs and
  restarting the browser did not fix this.  Closing all of my tabs and
  restarting the browser, however, _did_ allow the Firefox menus to
  render (provided I didn't try to open any web pages before using
  them), which allowed me to switch "Enhanced Tracking Protection" from
  Strict to Standard, fixing the problem.

  (This is the second time I've experienced this exact behaviour, which
  is how I knew to try modifying the tracking protection setting.  The
  last time was on an older version of Firefox in August:
  https://wrestle.town/@Odd_Bloke/102655281770357045)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 72.0.2+build1-0ubuntu1
  Uname: Linux 5.4.5-050405-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  BuildID: 20200117190643
  Channel: Unavailable
  CurrentDesktop: i3
  Date: Tue Feb  4 13:01:53 2020
  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-05-07 (273 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-94f8002b-6eb0-4faf-98c0-257a62150805
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:724
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=72.0.2/20200117190643 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to focal on 2019-11-15 (80 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-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.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1861913/+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 1862531] Re: [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use

[Martin Wimpress]

** Tags removed: champagne

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

Title:
  [focal] Wayland session is not available when a laptop has an Nvidia
  card an Intel card is in use

Status in gdm3 package in Ubuntu:
  Incomplete
Status in nvidia-prime package in Ubuntu:
  Invalid

Bug description:
  A Wayland session present at /usr/share/wayland-sessions/ubuntu-
  wayland.desktop is not displayed at the login screen when a system has
  an iGPU (Intel) and dGPU (Nvidia) and Intel iGPU is used:

  prime-select query 
  intel

  Only sessions at /usr/share/xsessions are present.

  
  ➜  ~ ls /usr/share/xsessions 
  remmina-gnome.desktop  ubuntu.desktop

  ➜  ~ ls /usr/share/wayland-sessions 
  ubuntu-wayland.desktop

  
  The root cause is the existence of a udev rule in 61-gdm.rules that runs 
gdm-disable-wayland when an nvidia driver is loaded in combination with LP: 
#1848326 (see this comment specifically 
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/comments/7).

  dpkg -S /lib/udev/rules.d/61-gdm.rules 
  gdm3: /lib/udev/rules.d/61-gdm.rules

  grep nvidia /lib/udev/rules.d/61-gdm.rules
  # disable Wayland when using the proprietary nvidia driver
  DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"

  When I comment it out and reboot, I get the right menu entry and am
  able to observe the right session type:

  ➜  ~ grep nvidia /lib/udev/rules.d/61-gdm.rules
  # disable Wayland when using the proprietary nvidia driver
  #DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"

  ➜  ~ loginctl
  SESSION  UID USER SEAT  TTY 
2 1000 dima seat0 tty2

  1 sessions listed.

  ➜  ~ loginctl show-session 2 -p Type
  Type=wayland

  
  System info:

  
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  Codename: focal

  
  ➜  ~ dpkg -l | grep gdm3
  ii  gdm3  3.34.1-1ubuntu1 
   amd64GNOME Display Manager

  ➜  ~ dpkg -l | grep nvidia-prime
  ii  nvidia-prime  0.8.13  
   all  Tools to enable NVIDIA's Prime

  ➜  ~ dpkg -l | grep nvidia-driver
  ii  nvidia-driver-440 440.59-0ubuntu1 
   amd64NVIDIA driver metapackage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862531/+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 1560090] Re: Multilingual support in libenchant_voikko is missing

[Timo Jyrinki]

(also install libenchant-2-voikko)

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

Title:
  Multilingual support in libenchant_voikko is missing

Status in enchant package in Ubuntu:
  Fix Released
Status in enchant-2 package in Ubuntu:
  Fix Released

Bug description:
  libenchant_voikko has one hardcoded language (Finnish, fi_FI).
  libenchant_voikko depends on libvoikko, which over the last couple of
  years have been extended to support multiple languages and multiple
  backends, mainly through the libhfstospell backend. A number of
  languages using this backend are available from divvun.no, divvun.org,
  giellatekno.uit.no and apertium.org, and it would be very desirable to
  make these languages available also via enchant, to broaden the
  language coverage of spell checking services in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/enchant/+bug/1560090/+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 1856927] Re: totem crashed with SIGSEGV in build_flavored_key() from insert_key_mapping()

[Sebastien Bacher]

the issue should be fixed with https://launchpad.net/ubuntu/+source
/grilo-plugins/0.3.11-1ubuntu1

** Changed in: grilo-plugins (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  totem crashed with SIGSEGV in build_flavored_key() from
  insert_key_mapping()

Status in Grilo Plugins:
  Fix Released
Status in grilo-plugins package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/55095074fb3c3335c19f63f3c91d3a8231be2034

  ---

  Test case:
  Fresh 20.04 install, updated
  Open totem
  What happens: segfault

  Installing grilo-plugins-0.3-extra allows totem to open fine.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: totem 3.34.1-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu14
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 18 19:51:40 2019
  ExecutablePath: /usr/bin/totem
  ExecutableTimestamp: 1570435741
  InstallationDate: Installed on 2019-12-19 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcCwd: /home/doug
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f76b92f6dd6:movzbl (%rax),%eax
   PC (0x7f76b92f6dd6) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so
   grl_tracker_setup_key_mappings () from 
/usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so
   ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so
   ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so
   ?? () from /lib/x86_64-linux-gnu/libtracker-sparql-2.0.so.0
  Title: totem crashed with SIGSEGV in grl_tracker_setup_key_mappings()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/grilo-plugins/+bug/1856927/+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 1862169] Re: rhythmbox crashed with SIGSEGV in build_flavored_key()

[Sebastien Bacher]

the issue should be fixed with https://launchpad.net/ubuntu/+source
/grilo-plugins/0.3.11-1ubuntu1

** Package changed: rhythmbox (Ubuntu) => grilo-plugins (Ubuntu)

** Changed in: grilo-plugins (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  rhythmbox crashed with SIGSEGV in build_flavored_key()

Status in grilo-plugins package in Ubuntu:
  Fix Released

Bug description:
  Fresh Focal installation (amd64 deCusktop), after enabling the grilo
  framework from the plugins dialog. Currently every attempt to start
  rhythmbox again results in an immedate crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: rhythmbox 3.4.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  6 14:30:21 2020
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2020-02-04 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200204)
  ProcCmdline: rhythmbox
  SegvAnalysis:
   Segfault happened at: 0x7fc7aade7dd6:movzbl (%rax),%eax
   PC (0x7fc7aade7dd6) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so
   grl_tracker_setup_key_mappings () from 
/usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so
   ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so
   ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: rhythmbox crashed with SIGSEGV in grl_tracker_setup_key_mappings()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1862169/+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 1776447] Re: Xorg's Indirect GLX broken from upstream regression

[Sebastien Bacher]

Tagging rls-ff-notfxing, the bug is not important enough to be rls
tracked. Still it's in the sponsoring queue and hopefully gets fixed
before focal is out

** Tags removed: champagne
** Tags added: rls-ff-notfixing

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

Title:
  Xorg's Indirect GLX broken from upstream regression

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

Bug description:
  [Impact]

   * IGLX is a way for an opengl application sending the 3D drawing GLX
  commands to the Xorg server for rendering instead of using the DRI
  infrastructure it is commonplace for High Performance Compute and
  Scientific institutions to use this feature of the Xorg server. (ref:
  https://www.phoronix.com/scan.php?page=news_item=Xorg-IGLX-
  Potential-Bye-Bye)

   * The feature is completely broken, currently, and any attempt to use
  it will cause the Xorg server to crash. This feature has been broken
  since a commit upstream in 2016.

   * The attached patch is from the revert commit entered into the
  upstream repository on 28 Jan 2020 following a git bisect of the bug
  discovering the offending commit.

  [Test Case]

   * Create a new file at /etc/X11/xorg.conf.d/99-IGLX.conf with the
  following contents:

  ```
  Section "ServerFlags"
  Option "IndirectGLX" "on"
  EndSection
  ```

   * Log out of your Xorg session
   * Switch to a VT (Ctrl+Alt+F2) and login
   * Run `sudo systemctl restart gdm` to restart Xorg
   * Login to the graphical session
   * If you do not have mesa-utils installed, then install it with the terminal 
command `sudo apt install mesa-utils`
   * Open a terminal and execute `LIBGL_ALWAYS_INDIRECT=1 glxgears`
   * If the fix is successful then glxgears should start and remain active 
without the Xorg server or glxgears crashing/segfaulting

  [Regression Potential]

   * This change is within DRI-related functionality and so might break
  all 3D accelerated applications.

   * There is a potential that the change is insufficient to fix the
  IGLX feature and so attempts to use it may still have undesirable and
  undefined results.

   * Upstream has run the patch through their CI system, which passed
  with no errors. This does not necessarily mean the patch will achieve
  the desired results, but at least indicates that the code does compile
  cleanly and can start an Xvfb headless instance.

  [Other Info]

   * This bug affects Ubuntu releases all the way back to, and
  including, Bionic 18.04.

   Original Bug Report Follows 

  There's already an upstream bug report here:

  https://bugs.freedesktop.org/show_bug.cgi?id=99555

  Basically, with Option "IndirectGLX" "True" and
  LIBGL_ALWAYS_INDIRECT=1 I get immediate crashes e.g. with glxgear:

  steved@xubuntu:~$ LIBGL_ALWAYS_INDIRECT=true glxgears
  Running synchronized to the vertical refresh.  The framerate should be
  approximately the same as the monitor refresh rate.
  X Error of failed request:  255
    Major opcode of failed request:  155 (GLX)
    Minor opcode of failed request:  1 (X_GLXRender)
    Serial number of failed request:  42
    Current serial number in output stream:  936

  I am trying to run what is effectively a traditional X Terminal, but
  as the hardware I am using has a 3D accelerated chipset it seems
  sensible to try to use it..

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Tue Jun 12 10:09:30 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-22-generic, x86_64: installed
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:2212]
  InstallationDate: Installed on 2018-05-31 (11 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: AZW S I
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/xubuntu--vg-root ro noresume
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 00.12
  dmi.board.asset.tag: Default string
  dmi.board.name: AB1
  dmi.board.vendor: IP3 Tech
  dmi.board.version: Default string
  dmi.chassis.asset.tag: 

[Desktop-packages] [Bug 1830336] Re: [needs-packaging] enchant 1.6.0 outdated, pipe command '*' (save personal dictionary) does nothing

[Timo Jyrinki]

Enchant 2 is now in Ubuntu 20.04:
https://launchpad.net/ubuntu/+source/enchant-2

It's also installed as default. Finnish support libenchant-2-voikko is
going to be installed by default from tomorrow onwards
(https://launchpad.net/ubuntu/+source/language-selector/0.201).

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

** Also affects: enchant-2 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: enchant-2 (Ubuntu)
   Status: New => Fix Released

** Changed in: enchant-2 (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  [needs-packaging] enchant 1.6.0 outdated, pipe command '*' (save
  personal dictionary) does nothing

Status in enchant package in Ubuntu:
  Fix Released
Status in enchant-2 package in Ubuntu:
  Fix Released

Bug description:
  [needs-packaging] enchant

  enchant is a meta-spellchecker supporting multiple spellchecking
  backends (hunspell, GNU aspell, hspell, Voikko, Zemberek, Apple Spell
  (on Mac OS)), with an ispell-compatible pipe mode for use within
  applications.

  URL: https://github.com/AbiWord/enchant
  License: LGPL 2.1
  Notes: Enchant homepage has moved to GitHub. The old homepage at 
abisource.com was last updated in 2010.

  The build steps for a released version seem standard; for details, see
  e.g.
  http://www.linuxfromscratch.org/blfs/view/svn/general/enchant.html

  Ubuntu currently has a package for enchant 1.6.0, but it is seriously
  out of date (2010); latest release is 2.2.3 (2018).

  Why this is important:

  Enchant is the recommended interface for Voikko, the spellchecker for
  Finnish. The older tmispell interface (that comes with Voikko) is
  deprecated by the developers of Voikko, so Enchant is currently the
  only supported option for checking both Finnish and English using the
  same frontend. A common frontend is important for easy switching of
  spellcheck language within applications such as Emacs and LyX.

  Finnish is an agglutinative language. This prevents common
  spellcheckers such as aspell from working properly, so Voikko itself
  is really necessary.

  The old version lacks support for the '*' command in pipe mode, so it
  is unable to update the personal dictionary. This is important
  especially in Emacs, because Emacs's flyspell (on-the-fly spell
  checker) package uses the pipe mode and sends this command to save new
  words into the personal dictionary.

  With Enchant 2.2.3, this works properly. (Does not even need
  configuration in Emacs other than telling it to use enchant as "the
  ispell program"; Enchant itself knows where its personal dictionaries
  are (~/.config/enchant), as well as which file to use for each
  language.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/enchant/+bug/1830336/+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 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]

[Bruce Copeland]

Last night I encountered similar bug behavior with a different message.
Several hours after a printing related crash, another orphaned
authentication dialog was painted on top of the gnome shell with the
message:

Please enter your password to access problem reports of system programs

In light of this related problem and Sergey's suggestion of PAM
involvement, I now believe the original bug in this thread is caused by
incorrect handling of PAM by gnome shell. There could also be threading
problems, insofar as the incorrect painting of an orphaned dialog window
seems to occur long after the action that is referenced in the dialog
window.

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

Title:
  undismissable, unclickable authentication dialog left on screen (top-
  left corner) after policykit authentication [pushModal: invocation of
  begin_modal failed]

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  In disco, when policykit prompted me for a password in order for
  update-manager to dispatch instructions to aptdaemon to perform
  package updates, the password dialog remained on the screen after I
  clicked 'authenticate'.

  The window is not clickable, it appears not to even be a window -
  mouse presses are received by the window underneath.  The exception is
  that the 'cancel' button is active and receives mouse events - but
  clicking it does nothing.

  This may be a gnome-shell issue rather than policykit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: policykit-1 0.105-25
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 13:14:33 2019
  InstallationDate: Installed on 2010-09-24 (3125 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: policykit-1
  UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824874/+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 1861409] Re: searching for irc takes more than 10 minutes

[Martin Wimpress]

** Tags removed: champagne

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

Title:
  searching for irc takes more than 10 minutes

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  A fresh install, searching for IRC and still waiting for the results
  after 10 minutes.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.34.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 30 10:58:56 2020
  InstallationDate: Installed on 2020-01-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.34.2-1ubuntu1
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1861409/+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 1776447] Re: Xorg's Indirect GLX broken from upstream regression

[Martin Wimpress]

** Changed in: xorg-server (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Xorg's Indirect GLX broken from upstream regression

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

Bug description:
  [Impact]

   * IGLX is a way for an opengl application sending the 3D drawing GLX
  commands to the Xorg server for rendering instead of using the DRI
  infrastructure it is commonplace for High Performance Compute and
  Scientific institutions to use this feature of the Xorg server. (ref:
  https://www.phoronix.com/scan.php?page=news_item=Xorg-IGLX-
  Potential-Bye-Bye)

   * The feature is completely broken, currently, and any attempt to use
  it will cause the Xorg server to crash. This feature has been broken
  since a commit upstream in 2016.

   * The attached patch is from the revert commit entered into the
  upstream repository on 28 Jan 2020 following a git bisect of the bug
  discovering the offending commit.

  [Test Case]

   * Create a new file at /etc/X11/xorg.conf.d/99-IGLX.conf with the
  following contents:

  ```
  Section "ServerFlags"
  Option "IndirectGLX" "on"
  EndSection
  ```

   * Log out of your Xorg session
   * Switch to a VT (Ctrl+Alt+F2) and login
   * Run `sudo systemctl restart gdm` to restart Xorg
   * Login to the graphical session
   * If you do not have mesa-utils installed, then install it with the terminal 
command `sudo apt install mesa-utils`
   * Open a terminal and execute `LIBGL_ALWAYS_INDIRECT=1 glxgears`
   * If the fix is successful then glxgears should start and remain active 
without the Xorg server or glxgears crashing/segfaulting

  [Regression Potential]

   * This change is within DRI-related functionality and so might break
  all 3D accelerated applications.

   * There is a potential that the change is insufficient to fix the
  IGLX feature and so attempts to use it may still have undesirable and
  undefined results.

   * Upstream has run the patch through their CI system, which passed
  with no errors. This does not necessarily mean the patch will achieve
  the desired results, but at least indicates that the code does compile
  cleanly and can start an Xvfb headless instance.

  [Other Info]

   * This bug affects Ubuntu releases all the way back to, and
  including, Bionic 18.04.

   Original Bug Report Follows 

  There's already an upstream bug report here:

  https://bugs.freedesktop.org/show_bug.cgi?id=99555

  Basically, with Option "IndirectGLX" "True" and
  LIBGL_ALWAYS_INDIRECT=1 I get immediate crashes e.g. with glxgear:

  steved@xubuntu:~$ LIBGL_ALWAYS_INDIRECT=true glxgears
  Running synchronized to the vertical refresh.  The framerate should be
  approximately the same as the monitor refresh rate.
  X Error of failed request:  255
    Major opcode of failed request:  155 (GLX)
    Minor opcode of failed request:  1 (X_GLXRender)
    Serial number of failed request:  42
    Current serial number in output stream:  936

  I am trying to run what is effectively a traditional X Terminal, but
  as the hardware I am using has a 3D accelerated chipset it seems
  sensible to try to use it..

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Tue Jun 12 10:09:30 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-22-generic, x86_64: installed
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:2212]
  InstallationDate: Installed on 2018-05-31 (11 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: AZW S I
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/xubuntu--vg-root ro noresume
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 00.12
  dmi.board.asset.tag: Default string
  dmi.board.name: AB1
  dmi.board.vendor: IP3 Tech
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Desktop-packages] [Bug 1560090] Re: Multilingual support in libenchant_voikko is missing

[Timo Jyrinki]

This is now fixed in Ubuntu 20.04 (focal fossa). Installing voikko-fi
and giella-sme gives one access to use Voikko with multiple languages.

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

** Also affects: enchant-2 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: enchant-2 (Ubuntu)
   Status: New => Fix Released

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

Title:
  Multilingual support in libenchant_voikko is missing

Status in enchant package in Ubuntu:
  Fix Released
Status in enchant-2 package in Ubuntu:
  Fix Released

Bug description:
  libenchant_voikko has one hardcoded language (Finnish, fi_FI).
  libenchant_voikko depends on libvoikko, which over the last couple of
  years have been extended to support multiple languages and multiple
  backends, mainly through the libhfstospell backend. A number of
  languages using this backend are available from divvun.no, divvun.org,
  giellatekno.uit.no and apertium.org, and it would be very desirable to
  make these languages available also via enchant, to broaden the
  language coverage of spell checking services in Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/enchant/+bug/1560090/+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 1772537] Re: Wrong combining sequence in Compose for the Finnish locale

[Timo Jyrinki]

** Bug watch added: gitlab.freedesktop.org/xorg/lib/libx11/issues #70
   https://gitlab.freedesktop.org/xorg/lib/libx11/issues/70

** Also affects: xlibs via
   https://gitlab.freedesktop.org/xorg/lib/libx11/issues/70
   Importance: Unknown
   Status: Unknown

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

Title:
  Wrong combining sequence in Compose for the Finnish locale

Status in xlibs:
  Unknown
Status in libx11 package in Ubuntu:
  Triaged

Bug description:
  The Compose file for the fi_FI.UTF-8 locale at
  /usr/share/X11/locale/fi_FI.UTF-8/Compose contains the following
  lines:

  :  "Ệ"  U1EC6  #  LATIN CAPITAL 
LETTER E WITH CIRCUMFLEX AND ACUTE
   :  "Ệ"  U1EC6  #  LATIN CAPITAL 
LETTER E WITH CIRCUMFLEX AND DOT BELOW

  Thus the codepoint "Ệ" U1EC6 is produced with two different sequences.
  Based on the key sequences and the comments at the ends of the lines,
  it is clear that the first line is a mistake. Instead of "Ệ"  U1EC6,
  the line should read "Ế"  U1EBE, a character which cannot be produced
  with the current Compose file otherwise at all.

  Description:  Ubuntu 17.10
  Release:  17.10

  libx11-data:
Installed: 2:1.6.4-3
Candidate: 2:1.6.4-3
Version table:
   *** 2:1.6.4-3 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://mr.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/xlibs/+bug/1772537/+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 1863716] Re: cups-browsed crashed with SIGSEGV in __strncasecmp_l_avx()

[Till Kamppeter]

I have added some crash guards to the is_local_hostname() function in
cups-browsed:

https://github.com/OpenPrinting/cups-
filters/commit/4157690bf0a40be1030ed19da7f70d41b9f27f86

I hope this helps.

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

Title:
  cups-browsed crashed with SIGSEGV in __strncasecmp_l_avx()

Status in cups-filters package in Ubuntu:
  In Progress

Bug description:
  seen with current focal

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: cups-browsed 1.27.0-2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CupsErrorLog:
   
  Date: Fri Feb 14 07:21:58 2020
  ExecutablePath: /usr/sbin/cups-browsed
  InstallationDate: Installed on 2019-01-12 (401 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lpstat:
   device for Canon_MG2900_series_Martin_s_MacBook: ///dev/null
   device for DYMO_LabelWriter_4XL_Lily_s_MacBook_Pro: ///dev/null
   device for EPSON_Epson_Stylus_Office_BX925_MacBook_Pro_de_Justine: 
///dev/null
   device for HP_LaserJet_MFP_M129_M134_Akilesh_s_MacBook_Air: ///dev/null
   device for IBC_Bur_7_MacBook_Pro_de_gregory: ///dev/null
  MachineType: LENOVO 20MFCTO1WW
  Papersize: letter
  ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
  ProcCmdline: /usr/sbin/cups-browsed
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7fab29a23c5f <__strncasecmp_l_avx+91>:   vmovdqu 
(%rdi),%xmm1
   PC (0x7fab29a23c5f) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%xmm1" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: cups-filters
  StacktraceTop:
   __strncasecmp_l_avx () at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:199
   ?? ()
   ?? ()
   avahi_service_resolver_event () from 
/usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
  Title: cups-browsed crashed with SIGSEGV in __strncasecmp_l_avx()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET43W (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  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:bvrN2EET43W(1.25):bd10/28/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1863716/+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 1863164] Re: ImportError: could not import gobject (error was: ImportError('/usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so: undefined symbol: PyExc_NotImp

[Sebastien Bacher]

What version of python3-gi do you have installed?

** Changed in: pygobject (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  ImportError: could not import gobject (error was:
  ImportError('/usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64
  -linux-gnu.so: undefined symbol: PyExc_NotImplementedError'))

Status in pygobject package in Ubuntu:
  Incomplete
Status in python3.8 package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 20.04 LTS
  2. Start first terminal with `tail -f ~/.xsession-errors`
  3. Start second terminal and run `caja -q` from here

  Expected results:
  * there are no error messages or warnings in 1st terminl

  Actual results:
  * there are several error messages and warnings:

  
  (caja:14755): Gtk-WARNING **: 22:55:26.070: Failed to register client: 
GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register 
client
  ImportError: could not import gobject (error was: 
ImportError('/usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so:
 undefined symbol: PyExc_NotImplementedError'))
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in 
apport_excepthook
  from apport.fileutils import likely_packaged, get_recent_crashes
File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in 

  from apport.report import Report
File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in 
  import apport.fileutils
File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in 

  from apport.packaging_impl import impl as packaging
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 23, in 

  import apt
File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in 
  import apt_pkg
  ImportError: 
/usr/lib/python3/dist-packages/apt_pkg.cpython-38-x86_64-linux-gnu.so: 
undefined symbol: PyExc_ValueError

  Original exception was:
  ImportError: could not import gobject (error was: 
ImportError('/usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so:
 undefined symbol: PyExc_NotImplementedError'))

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3-apt 1.9.5
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Feb 13 22:52:33 2020
  InstallationDate: Installed on 2020-02-11 (1 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200211)
  SourcePackage: python-apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1863164/+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 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]

[Phuc Minh Cai]

Hi Kai Heng Feng,

Still same black screen. Please see the attachment.

Btw, do you have article about how to check status and enable
CONFIG_PMIC_OPREGION? Thank you.

** Attachment added: "log boot kernel 5.5.0-7"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860754/+attachment/5329301/+files/prevboot4.txt

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

Title:
  ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to
  submit batchbuffer: Input/output error]

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't 
recognize graphic driver.
  - run udo apt-get install xserver-xorg-video-intel
  0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 14:29:01 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd]
  InstallationDate: Installed on 2020-01-24 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. T100HAN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T100HAN.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: T100HAN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: T
  dmi.product.name: T100HAN
  dmi.product.sku: ASUS-TabletSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860754/+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 1862053] Re: Compiler gets stuck (or extremely slow) on ppc64el

[Matthias Klose]

this is only *worked around* in ghostscript, not fixed.


** Changed in: ghostscript (Ubuntu)
   Status: Fix Released => Confirmed

** Also affects: gcc-9 (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: gcc (Ubuntu)

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

Title:
  Compiler gets stuck (or extremely slow) on ppc64el

Status in gcc:
  Confirmed
Status in gcc-9 package in Ubuntu:
  New
Status in ghostscript package in Ubuntu:
  Confirmed

Bug description:
  I have uploaded Ghostscript 9.50 to focal and it built without any
  problem on all architectures but ppc64el. On ppc64el the compiler
  seems to get stuck (or extremely slow) on one of the files of
  Ghostscript (devices/vector/gdevpdfb.c, I tried twice). This leads to
  the build process being killed after 150 minutes.

  See

  https://launchpad.net/ubuntu/+source/ghostscript/9.50~dfsg-5/+build/18661407

  and

  https://launchpadlibrarian.net/463662514/buildlog_ubuntu-focal-
  ppc64el.ghostscript_9.50~dfsg-5_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1862053/+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 1863370] Re: problem opening settings

[Sebastien Bacher]

What desktop environment do you use also?

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

Title:
  problem opening settings

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  i Have problem opening settings in ubuntu disco 19 destop

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Feb 14 14:05:32 2020
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Microsoft Corporation Haswell-ULT Integrated Graphics 
Controller [1414:0005]
  InstallationDate: Installed on 2020-02-11 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181115)
  MachineType: Microsoft Corporation Surface Pro 3
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-38-generic 
root=UUID=a63a3048-e668-4ab7-afe7-71e98c06872b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.11.2650
  dmi.board.asset.tag: 0
  dmi.board.name: Surface Pro 3
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: 0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.11.2650:bd04/30/2019:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 3
  dmi.product.sku: Surface_Pro_3
  dmi.product.version: 1
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1863370/+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 1863370] Re: problem opening settings

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks! 

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (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/1863370

Title:
  problem opening settings

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  i Have problem opening settings in ubuntu disco 19 destop

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Feb 14 14:05:32 2020
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Microsoft Corporation Haswell-ULT Integrated Graphics 
Controller [1414:0005]
  InstallationDate: Installed on 2020-02-11 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181115)
  MachineType: Microsoft Corporation Surface Pro 3
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-38-generic 
root=UUID=a63a3048-e668-4ab7-afe7-71e98c06872b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.11.2650
  dmi.board.asset.tag: 0
  dmi.board.name: Surface Pro 3
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: 0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.11.2650:bd04/30/2019:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 3
  dmi.product.sku: Surface_Pro_3
  dmi.product.version: 1
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1863370/+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 1863716] Re: cups-browsed crashed with SIGSEGV in __strncasecmp_l_avx()

[Sebastien Bacher]

** Changed in: cups-filters (Ubuntu)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

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

Title:
  cups-browsed crashed with SIGSEGV in __strncasecmp_l_avx()

Status in cups-filters package in Ubuntu:
  In Progress

Bug description:
  seen with current focal

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: cups-browsed 1.27.0-2
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CupsErrorLog:
   
  Date: Fri Feb 14 07:21:58 2020
  ExecutablePath: /usr/sbin/cups-browsed
  InstallationDate: Installed on 2019-01-12 (401 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lpstat:
   device for Canon_MG2900_series_Martin_s_MacBook: ///dev/null
   device for DYMO_LabelWriter_4XL_Lily_s_MacBook_Pro: ///dev/null
   device for EPSON_Epson_Stylus_Office_BX925_MacBook_Pro_de_Justine: 
///dev/null
   device for HP_LaserJet_MFP_M129_M134_Akilesh_s_MacBook_Air: ///dev/null
   device for IBC_Bur_7_MacBook_Pro_de_gregory: ///dev/null
  MachineType: LENOVO 20MFCTO1WW
  Papersize: letter
  ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
  ProcCmdline: /usr/sbin/cups-browsed
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7fab29a23c5f <__strncasecmp_l_avx+91>:   vmovdqu 
(%rdi),%xmm1
   PC (0x7fab29a23c5f) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%xmm1" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: cups-filters
  StacktraceTop:
   __strncasecmp_l_avx () at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:199
   ?? ()
   ?? ()
   avahi_service_resolver_event () from 
/usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
  Title: cups-browsed crashed with SIGSEGV in __strncasecmp_l_avx()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET43W (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  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:bvrN2EET43W(1.25):bd10/28/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1863716/+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 1863763] [NEW] gnome-shell/Wayland on vmware/vmwgfx misrenders with large windows

[Thomas Hellström]

Public bug reported:

There is a bug in mesa version 19.2.x where x>2, manifesting itself as
window contents in large windows on 4K display renders with an incorrect
vertical offset, making the desktop largely unusable for some customers.

The bug is fixed in latest 19.3 series and 20.0 rc series, but since
Ubuntu 18.04.1 still uses 19.2 series, a manual backport is needed.

Please cherry-pick mesa master commit
451cf228d53ba8f51beb3dcf04370e126fb7ccb6 ("svga: Fix banded DMA upload")
to fix the issue, alternatively switch to mesa 19.3 series.

Thanks,

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
Uname: Linux 5.5.0+ x86_64
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 18 05:53:02 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2020-02-17 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: VMware, Inc. VMware Virtual Platform
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.0+ 
root=UUID=3fa8a33e-bea4-42a8-9e5b-6a0b922e77d9 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/30/2019
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd10/30/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
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

** Affects: mesa (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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1863763

Title:
  gnome-shell/Wayland on vmware/vmwgfx misrenders with large windows

Status in mesa package in Ubuntu:
  New

Bug description:
  There is a bug in mesa version 19.2.x where x>2, manifesting itself as
  window contents in large windows on 4K display renders with an
  incorrect vertical offset, making the desktop largely unusable for
  some customers.

  The bug is fixed in latest 19.3 series and 20.0 rc series, but since
  Ubuntu 18.04.1 still uses 19.2 series, a manual backport is needed.

  Please cherry-pick mesa master commit
  451cf228d53ba8f51beb3dcf04370e126fb7ccb6 ("svga: Fix banded DMA
  upload") to fix the issue, alternatively switch to mesa 19.3 series.

  Thanks,

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
  Uname: Linux 5.5.0+ x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 18 05:53:02 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2020-02-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.0+ 
root=UUID=3fa8a33e-bea4-42a8-9e5b-6a0b922e77d9 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: Phoenix 

[Desktop-packages] [Bug 1624485] Re: Nettle: Enable AES-NI instructions on amd64.

[Vladimír Čunát]

There's also SHA* acceleration in --enable-fat and some 32-bit ARM
assembler IIRC.  In pure crypto the speedup can be quite significant
(like 5x in one of my tests).

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

Title:
  Nettle: Enable AES-NI instructions on amd64.

Status in nettle package in Ubuntu:
  New

Bug description:
  The current build of libnettle6 does not have AES-NI enabled. There's
  two configure options for enabling it:

  --enable-x86-aesni: Use AES-NI instructions instead of the standard 
implementation. This will break on systems that don't have AES-NI.
  --enable-fat: Build a "fat" library that has the standard implementation and 
the AES-NI implementation. This allows the library to continue working on older 
systems while providing faster performance on systems that have AES-NI.

  Note that Nettle's AES-NI implementation as of v3.2 is only supported
  on amd64, not i386, so this would only affect the 64-bit package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nettle/+bug/1624485/+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 1862229] Re: gnome session crash on boot with kernel 5.3.0-29-generic

[giacof]

Sorry for delay. I found the following related links:

https://errors.ubuntu.com/oops/b749b11e-485f-11ea-a808-fa163ee63de6
https://errors.ubuntu.com/oops/70a4e6e4-4a75-11ea-a63e-fa163ee63de6

Many thanks.

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

Title:
  gnome session crash on boot with kernel 5.3.0-29-generic

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  apt-cache policy gnome-shell
  gnome-shell:
    Installato: 3.34.1+git20191024-1ubuntu1~19.10.1
    Candidato:  3.34.1+git20191024-1ubuntu1~19.10.1
    Tabella versione:
   *** 3.34.1+git20191024-1ubuntu1~19.10.1 500
  500 http://it.archive.ubuntu.com/ubuntu eoan-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.34.1-1ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  First there was an issue with hibernation: after resuming, the gnome
  session was not restored and a new one was created (I had to login
  again from start). Here are some relevant log lines:

  [   21.375254] PM: Image signature found, resuming
  [   21.375255] PM: resume from hibernation
  [   21.375607] Freezing user space processes ... (elapsed 0.001 seconds) done.
  [   21.376719] OOM killer disabled.
  [   21.376832] PM: Marking nosave pages: [mem 0x-0x0fff]
  [   21.376834] PM: Marking nosave pages: [mem 0x0004f000-0x0004]
  [   21.376834] PM: Marking nosave pages: [mem 0x0009d000-0x0009efff]
  [   21.376835] PM: Marking nosave pages: [mem 0x000a-0x000f]
  [   21.376837] PM: Marking nosave pages: [mem 0xae7a8000-0xae7aefff]
  [   21.376838] PM: Marking nosave pages: [mem 0xaf18c000-0xaf66afff]
  [   21.376856] PM: Marking nosave pages: [mem 0xb7db3000-0xb7ff]
  [   21.376865] PM: Marking nosave pages: [mem 0xb8759000-0xb87f]
  [   21.376868] PM: Marking nosave pages: [mem 0xb8f9d000-0xb8ff]
  [   21.376870] PM: Marking nosave pages: [mem 0xba6f5000-0xba7f]
  [   21.376875] PM: Marking nosave pages: [mem 0xbbcec000-0x]
  [   21.377562] PM: Basic memory bitmaps created
  [   24.367114] PM: Using 3 thread(s) for decompression
  [   24.367115] PM: Loading and decompressing image data (1585416 pages)...
  [   24.367127] Hibernate inconsistent memory map detected!
  [   24.367138] fbcon: Taking over console
  [   24.367139] PM: Image mismatch: architecture specific data
  [   24.367141] PM: Read 6341664 kbytes in 0.01 seconds (634166.40 MB/s)
  [   24.368077] PM: Error -1 resuming
  [   24.368079] PM: Failed to load hibernation image, recovering.
  [   24.368347] PM: Basic memory bitmaps freed
  [   24.368347] OOM killer enabled.
  [   24.368347] Restarting tasks ... done.
  [   24.384357] Console: switching to colour frame buffer device 240x67
  [   24.404345] PM: resume from hibernation failed (-1)

  Then, since next restart I cannot login anymore, as the session keeps 
crashing immediately after entering user's password.
  The only way I could login back was by selecting the previous kernel version 
on boot (5.3.0-26-generic instead of 5.3.0-29-generic).

  I also noticed all gnome extensions (Applications Menu and Hibernate
  Status Button ) stopped working and were disabled.

  Boot journal attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862229/+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 1825623] Re: [AppIndicatorSupport-FATAL] unable to update overlay icon

[André Lanouette]

Same issue here. This appears to cause major freezes during several
seconds every time I receive a desktop notification and unlock my
computer.

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

Title:
  [AppIndicatorSupport-FATAL] unable to update overlay icon

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed

Bug description:
  After startup or login, An error occurs that just states cancel or
  report... but does not open a detail dialog

  Error messages in the syslog:

  ...
  Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-DEBUG] 
Registering 
StatusNotifierItem:1.95/org/ayatana/NotificationItem/software_update_available
  Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  ...

  It seems that the update notifier cannot register its icon in the top
  bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 10:49:27 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-30 (354 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1825623/+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 1856504] Re: [AppIndicatorSupport-FATAL] unable to update overlay icon

[André Lanouette]

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

Same issue here. This appears to cause major freezes during several
seconds every time I receive a desktop notification and unlock my
computer.

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

Title:
  [AppIndicatorSupport-FATAL] unable to update overlay icon

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) 3.34.1
  3) No error in log app.
  4) Error in log app.

  
   5:30:57 PM gnome-shell: [AppIndicatorSupport-FATAL] unable to update overlay 
icon
   5:30:57 PM gnome-shell: [AppIndicatorSupport-FATAL] unable to update overlay 
icon
   5:30:57 PM gnome-shell: [AppIndicatorSupport-FATAL] unable to update overlay 
icon
   5:30:57 PM gnome-shell: [AppIndicatorSupport-FATAL] unable to update overlay 
icon
   5:30:57 PM gnome-shell: [AppIndicatorSupport-DEBUG] Registering 
StatusNotifierItem :1.105/StatusNotifierItem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1856504/+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 1856504] Re: [AppIndicatorSupport-FATAL] unable to update overlay icon

[Launchpad Bug Tracker]

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

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

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: New => Confirmed

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

Title:
  [AppIndicatorSupport-FATAL] unable to update overlay icon

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 19.10
  2) 3.34.1
  3) No error in log app.
  4) Error in log app.

  
   5:30:57 PM gnome-shell: [AppIndicatorSupport-FATAL] unable to update overlay 
icon
   5:30:57 PM gnome-shell: [AppIndicatorSupport-FATAL] unable to update overlay 
icon
   5:30:57 PM gnome-shell: [AppIndicatorSupport-FATAL] unable to update overlay 
icon
   5:30:57 PM gnome-shell: [AppIndicatorSupport-FATAL] unable to update overlay 
icon
   5:30:57 PM gnome-shell: [AppIndicatorSupport-DEBUG] Registering 
StatusNotifierItem :1.105/StatusNotifierItem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1856504/+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 1863370] Re: problem opening settings

[Mike Salvatore]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  problem opening settings

Status in xorg package in Ubuntu:
  New

Bug description:
  i Have problem opening settings in ubuntu disco 19 destop

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Feb 14 14:05:32 2020
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Microsoft Corporation Haswell-ULT Integrated Graphics 
Controller [1414:0005]
  InstallationDate: Installed on 2020-02-11 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181115)
  MachineType: Microsoft Corporation Surface Pro 3
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-38-generic 
root=UUID=a63a3048-e668-4ab7-afe7-71e98c06872b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.11.2650
  dmi.board.asset.tag: 0
  dmi.board.name: Surface Pro 3
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: 0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.11.2650:bd04/30/2019:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 3
  dmi.product.sku: Surface_Pro_3
  dmi.product.version: 1
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1863370/+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 1849859] Re: smb printing fails

[Mario]

@jan.dolezal The solution worked for me as well. However, the printer
credentials dialogue in 19.10 doesn't show me a "password remember"
checkbox so that I have to re-enter my credentials every time I want to
print something.

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

Title:
  smb printing fails

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1863724] Re: Add missing pci-id's for Comet Lake (CML)

[Timo Aaltonen]

** No longer affects: linux-oem-osp1 (Ubuntu)

** Description changed:

  [Impact]
  
- Needs a commit for the kernel:
- 
- commit bfc4c359b2822bd2c457ccab271baeb33181c7c9
- Author: Anusha Srivatsa 
- Date: Mon Aug 12 15:27:37 2019 -0700
- 
- drm/i915/cml: Add Missing PCI IDs
- 
- and mesa:
- 
- commit e5ddbd7a3c5051351806e6f145d9352a673bd9db
- Author: Lionel Landwerlin 
- Date:   Wed Sep 25 17:43:07 2019 +0300
- 
- intel: Add new Comet Lake PCI-ids
+ After rebasing mesa to 19.2.x debian/patches/i965-sync-pciids.diff was
+ updated but some parts of it got accidentally dropped, losing a couple
+ of pci-id's for CML. They need to be restored.
  
  [Test case]
  
- install the updates on an affected machine, check with glxinfo -B that
+ Install the updates on an affected machine, check with glxinfo -B that
  the proper driver is loaded.
  
  [Regression potential]
  
  none, this just adds pci-id's

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

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

** Changed in: mesa (Ubuntu)
   Status: New => Invalid

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

Title:
  Add missing pci-id's for Comet Lake (CML)

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Bionic:
  New
Status in mesa source package in Eoan:
  New

Bug description:
  [Impact]

  After rebasing mesa to 19.2.x debian/patches/i965-sync-pciids.diff was
  updated but some parts of it got accidentally dropped, losing a couple
  of pci-id's for CML. They need to be restored.

  [Test case]

  Install the updates on an affected machine, check with glxinfo -B that
  the proper driver is loaded.

  [Regression potential]

  none, this just adds pci-id's

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