[Desktop-packages] [Bug 1874379] Re: 20.04 Software installer is not installing .deb file that it installed on 19.4

[Chris Guiver]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Please answer these questions:

what are the packages?
where did they come from?

(it could be dependency related, but no details are currently available)

Please execute the following command only once, as it will automatically
gather debugging information, in a terminal:

apport-collect 1874379

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  20.04 Software installer is not installing .deb file that it installed
  on 19.4

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I installed 3 different applications from their downloaded .deb files
  via Ubuntu Software app in 19.4. Attempting to reinstall them on 20.04
  using the same steps has failed

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

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

[Desktop-packages] [Bug 1874379] Re: 20.04 Software installer is not installing .deb file that it installed on 19.4

[Steve Langasek]

** Project changed: ubuntu-cdimage => gnome-software (Ubuntu)

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

Title:
  20.04 Software installer is not installing .deb file that it installed
  on 19.4

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I installed 3 different applications from their downloaded .deb files
  via Ubuntu Software app in 19.4. Attempting to reinstall them on 20.04
  using the same steps has failed

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

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

[Desktop-packages] [Bug 1874379] [NEW] 20.04 Software installer is not installing .deb file that it installed on 19.4

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I installed 3 different applications from their downloaded .deb files
via Ubuntu Software app in 19.4. Attempting to reinstall them on 20.04
using the same steps has failed

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

-- 
20.04 Software installer is not installing .deb file that it installed  on 19.4
https://bugs.launchpad.net/bugs/1874379
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-software in Ubuntu.

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

[Desktop-packages] [Bug 1873685] Re: Wallpaper not updated to 20.04 default after upgrade

[Chris Guiver]

I'll add the link
http://iso.qa.ubuntu.com/qatracker/milestones/408/builds/23/testcases/1701/results/
(in case wanted/needed)

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

Title:
  Wallpaper not updated to 20.04 default after upgrade

Status in Lubuntu Artwork:
  New
Status in ubuntu-wallpapers package in Ubuntu:
  New

Bug description:
  Wallpaper not updated to 20.04 default after upgrade.

  After GUI upgrade from Lubuntu version 19.10 to Lubuntu Focal 20.04
  the desktop still showing the 19.10 default wallpaper.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-wallpapers-focal (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Sun Apr 19 17:44:01 2020
  InstallationDate: Installed on 2020-04-19 (0 days ago)
  InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1)
  SourcePackage: ubuntu-wallpapers
  UpgradeStatus: Upgraded to focal on 2020-04-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-artwork/+bug/1873685/+subscriptions

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

[Desktop-packages] [Bug 1873685] Re: Wallpaper not updated to 20.04 default after upgrade

[Chris Guiver]

I just did a install of Lubuntu 20.04 (2020-04-22 ISO) where I used
manual partitioning, and replaced a prior SDA3 install of focal (I'm
guessing last performed before wallpapers were added) with the newer
install.

I opted to not-format the partition, and the install looks great,
however I was surprised by the 19.10 wallpaper there.

When I went into the edit desktop preferences (wallpaper image file),
what shows there points to the correct 20.04 image (when filename
copy/pasted & viewed in lximage-qt), but I didn't expect to see that
image.

As I didn't format, my $HOME was left untouched, which would likely
explain what I found, however I was surprised & remembered this bug.

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

Title:
  Wallpaper not updated to 20.04 default after upgrade

Status in Lubuntu Artwork:
  New
Status in ubuntu-wallpapers package in Ubuntu:
  New

Bug description:
  Wallpaper not updated to 20.04 default after upgrade.

  After GUI upgrade from Lubuntu version 19.10 to Lubuntu Focal 20.04
  the desktop still showing the 19.10 default wallpaper.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-wallpapers-focal (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Sun Apr 19 17:44:01 2020
  InstallationDate: Installed on 2020-04-19 (0 days ago)
  InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1)
  SourcePackage: ubuntu-wallpapers
  UpgradeStatus: Upgraded to focal on 2020-04-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-artwork/+bug/1873685/+subscriptions

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

[Desktop-packages] [Bug 1871618] Re: Switching playing youtube video to full-screen mode and to default mode lag on Chromium

[Tony Thuitai]

comment#4 In X11 session and not using any dpi scaling because my
laptop's screen does not require scaling.

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

Title:
  Switching playing youtube video to full-screen mode and to default
  mode lag on Chromium

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  The switching of a playing youtube video to fullscreen mode and also
  from fullscreen mode to normal mode lags.

  Ubuntu version: 19:10
  Chromium version: 80.0.3987.163 (Official Build) snap (64-bit)

  Steps to reproduce
  1. Launch Chromium and open Youtube.
  2. Select/search for a video and play.
  3. Switch the playing video to full-screen mode and back to normal view.

  When playing a video using chromium the switch to full-screen mode and
  back is expected to be smooth but instead, the switching is laggy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1871618/+subscriptions

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

[Desktop-packages] [Bug 1874373] Re: pacmd list sinks writes 65536 bytes, doesn't complete

[gregrwm]

** Attachment added: "pacmd list sinks"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1874373/+attachment/5358286/+files/pmdlsi

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

Title:
  pacmd list sinks writes 65536 bytes, doesn't complete

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ pacmd list sinks|wc
 18306726   65536
  $ pacmd list sinks>/tmp/pmdlsi  #see attachment, 65536 bytes, incomplete

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio-utils 1:13.99.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Apr 22 23:06:17 2020
  InstallationDate: Installed on 2020-03-15 (38 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/20/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ETA2WW (2.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C6008SUS
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C6008SUS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6008SUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Edge E540
  dmi.product.name: 20C6008SUS
  dmi.product.sku: LENOVO_MT_20C6_BU_Think_FM_ThinkPad Edge E540
  dmi.product.version: ThinkPad Edge E540
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1874373] [NEW] pacmd list sinks writes 65536 bytes, doesn't complete

[gregrwm]

Public bug reported:

$ pacmd list sinks|wc
   18306726   65536
$ pacmd list sinks>/tmp/pmdlsi  #see attachment, 65536 bytes, incomplete

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio-utils 1:13.99.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Apr 22 23:06:17 2020
InstallationDate: Installed on 2020-03-15 (38 days ago)
InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/20/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: J9ETA2WW (2.28 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20C6008SUS
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C6008SUS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6008SUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad Edge E540
dmi.product.name: 20C6008SUS
dmi.product.sku: LENOVO_MT_20C6_BU_Think_FM_ThinkPad Edge E540
dmi.product.version: ThinkPad Edge E540
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

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

Title:
  pacmd list sinks writes 65536 bytes, doesn't complete

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ pacmd list sinks|wc
 18306726   65536
  $ pacmd list sinks>/tmp/pmdlsi  #see attachment, 65536 bytes, incomplete

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio-utils 1:13.99.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Apr 22 23:06:17 2020
  InstallationDate: Installed on 2020-03-15 (38 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/20/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ETA2WW (2.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C6008SUS
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C6008SUS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6008SUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Edge E540
  dmi.product.name: 20C6008SUS
  dmi.product.sku: LENOVO_MT_20C6_BU_Think_FM_ThinkPad Edge E540
  dmi.product.version: ThinkPad Edge E540
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1874371] [NEW] disks reports incorrect smart details

[Humphrey van Polanen Petel]

Public bug reported:

the menu-sentry "SMART Data & self-tests" reports attribute values that
do not match the ssd specifications for a Kingston SA400S37

perhaps a hddtemp problem

see also
https://bugs.launchpad.net/ubuntu/+source/gsmartcontrol/+bug/1873546

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-disk-utility 3.18.3.1-1ubuntu1.1
ProcVersionSignature: Ubuntu 4.15.0-96.97~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-96-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.23
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 23 13:06:47 2020
ExecutablePath: /usr/bin/gnome-disks
InstallationDate: Installed on 2018-12-30 (480 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: gnome-disk-utility
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-disk-utility (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 gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1874371

Title:
  disks reports incorrect smart details

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  the menu-sentry "SMART Data & self-tests" reports attribute values
  that do not match the ssd specifications for a Kingston SA400S37

  perhaps a hddtemp problem

  see also
  https://bugs.launchpad.net/ubuntu/+source/gsmartcontrol/+bug/1873546

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-disk-utility 3.18.3.1-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-96.97~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.23
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 23 13:06:47 2020
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2018-12-30 (480 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1872390] Re: 193% CPU usage while using webex with chromium

[Chia-Hao Hsu]

Thank you for your help. Yes, it is an bug report about Webex meeting.

I enable hardware-accelerated video decoding on chromium (80.0.3987.163,
official build, 64-bit) by editing chrome://flags. But, it still use
around 200 % CPU. Noticeably, the process did not turn down when I close
the tab of webex meeting.

The functions enabled was listed below. 
"Graphics Feature Status
Canvas: Hardware accelerated
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Out-of-process Rasterization: Hardware accelerated
OpenGL: Enabled
Hardware Protected Video Decode: Hardware accelerated
Rasterization: Hardware accelerated
Skia Renderer: Enabled
Video Decode: Hardware accelerated
Viz Display Compositor: Enabled
Vulkan: Enabled
WebGL: Hardware accelerated
WebGL2: Hardware accelerated"

I also try chrome (81.0.4044.122, official build, 64-bit) and enable
hardware-accelerated video decoding. It use around 105 % CPU.

The functions enabled was listed below. 
"Graphics Feature Status
Canvas: Hardware accelerated
Flash: Hardware accelerated
Flash Stage3D: Hardware accelerated
Flash Stage3D Baseline profile: Hardware accelerated
Compositing: Hardware accelerated
Multiple Raster Threads: Enabled
Out-of-process Rasterization: Hardware accelerated
OpenGL: Enabled
Hardware Protected Video Decode: Hardware accelerated
Rasterization: Hardware accelerated
Skia Renderer: Enabled
Video Decode: Hardware accelerated
Vulkan: Disabled
WebGL: Hardware accelerated
WebGL2: Hardware accelerated"

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

Title:
  193% CPU usage while using webex with chromium

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  193% CPU usage while using webex with chromium. The process seems
  associated with audio. When the process was killed. The voice was
  muted.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 80.0.3987.163-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEaeIgAQEBASAbAQOAKxh46tr1pFVSnycOUFS/7gCBwAEBAQEBAQEBAQEBAQEBZiFWqlEAHjBGjzMAsuwQAAAe/QAyTB5TDgAKICAgICAg/ABWWDIwNwogICAgICAg/wBIOExNUVMwMTg1ODUKAbQCAxthIwkHB4MBAABnAwwAIACALUOQhALiAA+MCtCKIOAtEBA+lgCgWgAAKQ==
   modes: 1366x768 1920x1080 1920x1080 1280x720 1280x720 1280x720 1024x768 
1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x480 720x480 
720x480 640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGr+1hAAAaAQSlIhN4Alklk1hZkykmUFQBAQEBAQEBAQEBAQEBAQEBeDeAtHA4LkBsMKoAWMEQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTU2SEFOMDYuMSAKANo=
   modes: 1920x1080
  Date: Mon Apr 13 11:01:39 2020
  Desktop-Session:
   'gnome'
   '/etc/xdg/xdg-gnome:/etc/xdg'
   '/usr/share/gnome:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2018-04-29 (714 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  Load-Avg-1min: 6.54
  Load-Processes-Running-Percent:   0.3%
  MachineType: ASUSTeK COMPUTER INC. FX503VD
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=8d5334b6-ef1c-42d3-880c-f5d4c937cba2 ro quiet splash 
tpm_tis.interrupts=0 acpi_osi=Linux i915.preliminary_hw_support=1 idle=nomwait 
mds=full,nosmt quiet splash tpm_tis.interrupts=0 acpi_osi=Linux 
acpi_backlight=vendor i915.preliminary_hw_support=1 idle=nomwait mds=full,nosmt 
vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to bionic on 2019-12-20 (114 days ago)
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX503VD.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX503VD
  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.:bvrFX503VD.308:bd04/29/2019:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming
  dmi.product.name: FX503VD
  dmi.product.version: 1.0
  

[Desktop-packages] [Bug 1874299] Re: PC crashes / freezes when removing application icons in created folders

[Helio Victor]

** Description changed:

- The computer freezes / freezes when several app icons are removed from a 
created folder, it is necessary to manually disconnect to get back to work.
- Folders created in the case would be this gnome function: 
https://www.youtube.com/watch?v=dXIqt7z5e9U
+ The computer freezes / freezes when several app icons are removed from a
+ created folder, it is necessary to manually disconnect to get back to
+ work.
  
- Operating System: Ubuntu 20.04 LTS
- Kernel: Linux 5.4.0-26-generic
- gnome-shell: 3.36.1-5ubuntu1
- --- 
+ Update I: Bug reproduction: https://streamable.com/mzd6th
+ Resolution: 16:9 (1366x768)
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-08-13 (253 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.36.1-5ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-16 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
-  # set this to 0 to disable apport, or to 1 to enable it
-  # you can temporarily override this with
-  # sudo service apport start force_start=1
-  enabled=0
+  # set this to 0 to disable apport, or to 1 to enable it
+  # you can temporarily override this with
+  # sudo service apport start force_start=1
+  enabled=0
  mtime.conffile..etc.default.apport: 2020-04-22T16:09:17.155220

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

Title:
  PC crashes / freezes when removing application icons in created
  folders

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The computer freezes / freezes when several app icons are removed from
  a created folder, it is necessary to manually disconnect to get back
  to work.

  Update I: Bug reproduction: https://streamable.com/mzd6th
  Resolution: 16:9 (1366x768)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-08-13 (253 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.36.1-5ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-16 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-04-22T16:09:17.155220

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

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

[Desktop-packages] [Bug 1874178] Re: Unlocking existing session needs two attempts after selecting Switch User

[Sean Davis]

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

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

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

Title:
  Unlocking existing session needs two attempts after selecting Switch
  User

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  This has been occurring during the Xubuntu post-install test. It's not
  the same as Bug #1776475, as it's not necessary to have logged in as
  another user (or even for another user to exist) for the problem to
  happen.

  My sequence of actions is:

  *Create new user.
  *Open a program (usually Thunar or Terminal).
  *Lock session.
  *Click on "Switch User". <-- This is all that's necessary to trigger it.
  *Enter password to unlock my own session.
  *Then there's a delay and screen goes black, then the unlock prompt appears 
again.
  *The second time, my session unlocks.

  This particular report is from a QEMU/KVM vm, but it's also been
  happening on a bare-metal install.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Apr 22 15:30:29 2020
  InstallationDate: Installed on 2020-04-22 (0 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200421)
  ProcEnviron:
   LANGUAGE=en_NZ:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1874278] Re: Can't install any packages with ubuntu-drivers using ubuntu-drivers when invoked from ubiquity

[Launchpad Bug Tracker]

This bug was fixed in the package linux-restricted-modules -
5.4.0-26.30+2

---
linux-restricted-modules (5.4.0-26.30+2) focal; urgency=medium

  * /bin/in-target check is flawed as it does not tell the difference
between live-session and in-target chroot. (LP: #1874278)

 -- Dimitri John Ledkov   Wed, 22 Apr 2020 22:43:55
+0100

** Changed in: linux-restricted-modules (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Can't install any packages with ubuntu-drivers using ubuntu-drivers
  when invoked from ubiquity

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  We are in the process of switching ubuntu-drivers to installing linux-
  restricted-modules versions of NVidia drivers when it can, but this
  fails when Ubiquity invokes ubuntu-drivers, like:

  Setting up linux-modules-nvidia-440-5.4.0-25-generic (5.4.0-25.29) ...
   /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-25-generic.postinst: 44: 
3: B
  ad file descriptor
   dpkg: error processing package linux-modules-nvidia-440-5.4.0-25-generic 
(--con
  figure):
installed linux-modules-nvidia-440-5.4.0-25-generic package 
post-installation 
  script subprocess returned error exit status 2
   dpkg: dependency problems prevent configuration of 
linux-modules-nvidia-440-gen
  eric-hwe-20.04:
linux-modules-nvidia-440-generic-hwe-20.04 depends on 
linux-modules-nvidia-440
  -5.4.0-25-generic (= 5.4.0-25.29); however:
 Package linux-modules-nvidia-440-5.4.0-25-generic is not configured yet.
   
   dpkg: error processing package linux-modules-nvidia-440-generic-hwe-20.04 
(--configure):
dependency problems - leaving unconfigured

  It's a problem with the nesting of debconf: Ubiquity itself is using
  debconf, and ubuntu-drivers is installing -nvidia- packages which
  themselves also use debconf, and we don't know how to connect ubuntu-
  drivers use of debconf with the ubiquity one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1874278/+subscriptions

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

[Desktop-packages] [Bug 1874345] [NEW] Gnome shell x11 freez after waking from off-locked-screen

[Excited Buddha]

Public bug reported:

using driver nvidia-440. I had a few apps open, transfering large files
as well, went away, screen got turned off after 15 min(intended), screen
got locked auto after further 5 min(intended set by user), then when
waking off screen up after all this, nothing appears, the screen is
black and frozen.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 23 05:19:50 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-04-22 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200420)
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Gnome shell x11 freez after waking from off-locked-screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  using driver nvidia-440. I had a few apps open, transfering large
  files as well, went away, screen got turned off after 15
  min(intended), screen got locked auto after further 5 min(intended set
  by user), then when waking off screen up after all this, nothing
  appears, the screen is black and frozen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 23 05:19:50 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-22 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200420)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  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/1874345/+subscriptions

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

[Desktop-packages] [Bug 1874178] Re: Unlocking existing session needs two attempts after selecting Switch User

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1874178

** Tags added: iso-testing

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

Title:
  Unlocking existing session needs two attempts after selecting Switch
  User

Status in lightdm package in Ubuntu:
  New

Bug description:
  This has been occurring during the Xubuntu post-install test. It's not
  the same as Bug #1776475, as it's not necessary to have logged in as
  another user (or even for another user to exist) for the problem to
  happen.

  My sequence of actions is:

  *Create new user.
  *Open a program (usually Thunar or Terminal).
  *Lock session.
  *Click on "Switch User". <-- This is all that's necessary to trigger it.
  *Enter password to unlock my own session.
  *Then there's a delay and screen goes black, then the unlock prompt appears 
again.
  *The second time, my session unlocks.

  This particular report is from a QEMU/KVM vm, but it's also been
  happening on a bare-metal install.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Apr 22 15:30:29 2020
  InstallationDate: Installed on 2020-04-22 (0 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200421)
  ProcEnviron:
   LANGUAGE=en_NZ:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia

[Launchpad Bug Tracker]

** Branch linked: lp:~kubuntu-dev/ubuntu-seeds/kubuntu.focal

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

Title:
  ubuntu-drivers changes kernel flavour when installing nvidia

Status in linux package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-440 source package in Focal:
  Fix Released
Status in ubiquity source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Released
Status in ubuntu-meta source package in Focal:
  Fix Committed

Bug description:
  $ dpkg-query -W linux-image-*
  linux-image-5.4.0-25-generic  5.4.0-25.29
  linux-image-generic-hwe-20.04 5.4.0.25.31

  $ ubuntu-drivers list
  nvidia-driver-390
  nvidia-driver-435
  nvidia-driver-440

  
  $ sudo ubuntu-drivers install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-kernel-common-440
nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 
screen-resolution-extra xserver-xorg-video-nvidia-440
  Suggested packages:
fdutils linux-doc | linux-source-5.4.0 linux-tools 
linux-headers-5.4.0-25-lowlatency
  Recommended packages:
libnvidia-compute-440:i386 libnvidia-decode-440:i386 
libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 
libnvidia-gl-440:i386
  The following NEW packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-driver-440
nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime 
nvidia-settings nvidia-utils-440 screen-resolution-extra 
xserver-xorg-video-nvidia-440
  0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded.

  I was expecting for it to pick linux-modules-nvidia-440-generic-
  hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04

  As if it sorted things and picked last one?

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

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

[Desktop-packages] [Bug 1869963] Re: Unable to install chromium-browser 20.04

[Paul White]

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

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

Title:
  Unable to install chromium-browser 20.04

Status in cloud-images:
  Incomplete
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce: Create a docker container with the official image
  "ubuntu:focal". Inside of the container, run "apt-get install
  chromium-browser".

  Expected results: Chromium is installed.

  Actual results: Chromium installation fails. The error is telling me
  that it is unable to reach the snap store (probably because snapd is
  not running).

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1869963/+subscriptions

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

[Desktop-packages] [Bug 1869963] [NEW] Unable to install chromium-browser 20.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Steps to reproduce: Create a docker container with the official image
"ubuntu:focal". Inside of the container, run "apt-get install chromium-
browser".

Expected results: Chromium is installed.

Actual results: Chromium installation fails. The error is telling me
that it is unable to reach the snap store (probably because snapd is not
running).

** Affects: cloud-images
 Importance: Undecided
 Status: Incomplete

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


** Tags: docker
-- 
Unable to install chromium-browser 20.04
https://bugs.launchpad.net/bugs/1869963
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to chromium-browser in Ubuntu.

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

[Desktop-packages] [Bug 1874340] Re: Ubuntu Settings app on doesn't collapse to hanheld size

[Paul White]

** Package changed: ubuntu-settings (Ubuntu) => gnome-control-center
(Ubuntu)

** Tags added: focal

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

Title:
  Ubuntu Settings app on doesn't collapse to hanheld size

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

Bug description:
  Ubuntu Settings app is supposed to collapse the sidebar when scaling the down 
the window on the x axis.
  On Ubuntu 20.04 that seems to be broken.

  I've attached the image describing the issue.

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

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

[Desktop-packages] [Bug 1874333] Re: Titlebar buttons are placed in the wrong place

[Paul White]

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

** This bug has been marked a duplicate of bug 1873638
   Titlebar buttons incorrectly placed when set to appear on the left

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

Title:
  Titlebar buttons are placed in the wrong place

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  Titlebar buttons in the Ubuntu Settings app on Ubuntu 20.04 are placed
  in the wrong place when the placement is set to the left side.

  I've attached the image describing the issue.

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

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

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

[Ivan Matyunin]

I never isolated a way to reproduce this bug, and I haven't encountered
it again (even with keeping the extensions enabled). In fact generally
the gnome-shell crashes have largely stopped. I'm not sure at what point
that was, but for at least the past few days, things that would often
crash gnome-shell no longer cause crashes (such as clicking the top-bar
widgets on the lock screen, which before reliably triggered
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868440).

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

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

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I can't really pinpoint the cause because I've had lots of gnome-shell
  crashes during normal use and I can't very well tell them apart.

  One more-common factor is clicking the top-bar, either when logged in
  or when the screen is locked.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 19:22:24 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fa819f2 :  
mov(%rax),%rdi
   PC (0x7fa819f2) ok
   source "(%rax)" (0x223d657079742000) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   st_theme_node_lookup_shadow () from /usr/lib/gnome-shell/libst-1.0.so
   st_theme_node_get_text_shadow () from /usr/lib/gnome-shell/libst-1.0.so
   st_theme_node_get_text_shadow () from /usr/lib/gnome-shell/libst-1.0.so
   st_theme_node_get_text_shadow () from /usr/lib/gnome-shell/libst-1.0.so
   st_theme_node_get_text_shadow () from /usr/lib/gnome-shell/libst-1.0.so
  Title: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow()
  UpgradeStatus: Upgraded to focal on 2020-04-05 (4 days ago)
  UserGroups: adm cdrom dialout dip docker input libvirt lpadmin plugdev 
sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1874278] Re: Can't install any packages with ubuntu-drivers using ubuntu-drivers when invoked from ubiquity

[Launchpad Bug Tracker]

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

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

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

Title:
  Can't install any packages with ubuntu-drivers using ubuntu-drivers
  when invoked from ubiquity

Status in linux-restricted-modules package in Ubuntu:
  Fix Committed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  We are in the process of switching ubuntu-drivers to installing linux-
  restricted-modules versions of NVidia drivers when it can, but this
  fails when Ubiquity invokes ubuntu-drivers, like:

  Setting up linux-modules-nvidia-440-5.4.0-25-generic (5.4.0-25.29) ...
   /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-25-generic.postinst: 44: 
3: B
  ad file descriptor
   dpkg: error processing package linux-modules-nvidia-440-5.4.0-25-generic 
(--con
  figure):
installed linux-modules-nvidia-440-5.4.0-25-generic package 
post-installation 
  script subprocess returned error exit status 2
   dpkg: dependency problems prevent configuration of 
linux-modules-nvidia-440-gen
  eric-hwe-20.04:
linux-modules-nvidia-440-generic-hwe-20.04 depends on 
linux-modules-nvidia-440
  -5.4.0-25-generic (= 5.4.0-25.29); however:
 Package linux-modules-nvidia-440-5.4.0-25-generic is not configured yet.
   
   dpkg: error processing package linux-modules-nvidia-440-generic-hwe-20.04 
(--configure):
dependency problems - leaving unconfigured

  It's a problem with the nesting of debconf: Ubiquity itself is using
  debconf, and ubuntu-drivers is installing -nvidia- packages which
  themselves also use debconf, and we don't know how to connect ubuntu-
  drivers use of debconf with the ubiquity one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1874278/+subscriptions

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

[Desktop-packages] [Bug 1874278] Re: Can't install any packages with ubuntu-drivers using ubuntu-drivers when invoked from ubiquity

[Martin Wimpress]

** Changed in: linux-restricted-modules (Ubuntu)
   Status: Fix Released => Fix Committed

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

Title:
  Can't install any packages with ubuntu-drivers using ubuntu-drivers
  when invoked from ubiquity

Status in linux-restricted-modules package in Ubuntu:
  Fix Committed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  We are in the process of switching ubuntu-drivers to installing linux-
  restricted-modules versions of NVidia drivers when it can, but this
  fails when Ubiquity invokes ubuntu-drivers, like:

  Setting up linux-modules-nvidia-440-5.4.0-25-generic (5.4.0-25.29) ...
   /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-25-generic.postinst: 44: 
3: B
  ad file descriptor
   dpkg: error processing package linux-modules-nvidia-440-5.4.0-25-generic 
(--con
  figure):
installed linux-modules-nvidia-440-5.4.0-25-generic package 
post-installation 
  script subprocess returned error exit status 2
   dpkg: dependency problems prevent configuration of 
linux-modules-nvidia-440-gen
  eric-hwe-20.04:
linux-modules-nvidia-440-generic-hwe-20.04 depends on 
linux-modules-nvidia-440
  -5.4.0-25-generic (= 5.4.0-25.29); however:
 Package linux-modules-nvidia-440-5.4.0-25-generic is not configured yet.
   
   dpkg: error processing package linux-modules-nvidia-440-generic-hwe-20.04 
(--configure):
dependency problems - leaving unconfigured

  It's a problem with the nesting of debconf: Ubiquity itself is using
  debconf, and ubuntu-drivers is installing -nvidia- packages which
  themselves also use debconf, and we don't know how to connect ubuntu-
  drivers use of debconf with the ubiquity one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1874278/+subscriptions

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

[Desktop-packages] [Bug 1874047] Re: 20.04 - Software Boutique - No Filter drop-down placement

[Luke Horwell]

This is a regression introduced in gir1.2-webkit2 2.28.1, which Ubuntu
updated on 16th April 2020 for security updates. This was working fine
in 2.28.0.

This affects other applications that use WebKit2.

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

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

Title:
  20.04 - Software Boutique - No Filter drop-down placement

Status in Ubuntu MATE:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  New

Bug description:
  Open the Software Boutique and click on 'Sound and Video' and then
  click on the drop-down curently set to 'No Filter'.

  Expected result:  menu of options opens immediately below.

  Actual result:  menu for filters appears way off to the right, and
  below, outside of the application window.

  Problem reported originally by lqlarry here - https://ubuntu-
  mate.community/t/software-boutique-filter-menu/21546

  I have confirmed that it affects more than 1 person.

  Ubuntu-MATE RC1 installed and updated from daily since start of Alpha
  test (clean install at that time).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1874047/+subscriptions

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

[Desktop-packages] [Bug 1874340] [NEW] Ubuntu Settings app on doesn't collapse to hanheld size

[Kristijan Žic ]

Public bug reported:

Ubuntu Settings app is supposed to collapse the sidebar when scaling the down 
the window on the x axis.
On Ubuntu 20.04 that seems to be broken.

I've attached the image describing the issue.

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

** Attachment added: "bitmap2.png"
   
https://bugs.launchpad.net/bugs/1874340/+attachment/5358161/+files/bitmap2.png

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

Title:
  Ubuntu Settings app on doesn't collapse to hanheld size

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  Ubuntu Settings app is supposed to collapse the sidebar when scaling the down 
the window on the x axis.
  On Ubuntu 20.04 that seems to be broken.

  I've attached the image describing the issue.

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

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

[Desktop-packages] [Bug 1874278] Re: Can't install any packages with ubuntu-drivers using ubuntu-drivers when invoked from ubiquity

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: New => Confirmed

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

Title:
  Can't install any packages with ubuntu-drivers using ubuntu-drivers
  when invoked from ubiquity

Status in linux-restricted-modules package in Ubuntu:
  Fix Committed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  We are in the process of switching ubuntu-drivers to installing linux-
  restricted-modules versions of NVidia drivers when it can, but this
  fails when Ubiquity invokes ubuntu-drivers, like:

  Setting up linux-modules-nvidia-440-5.4.0-25-generic (5.4.0-25.29) ...
   /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-25-generic.postinst: 44: 
3: B
  ad file descriptor
   dpkg: error processing package linux-modules-nvidia-440-5.4.0-25-generic 
(--con
  figure):
installed linux-modules-nvidia-440-5.4.0-25-generic package 
post-installation 
  script subprocess returned error exit status 2
   dpkg: dependency problems prevent configuration of 
linux-modules-nvidia-440-gen
  eric-hwe-20.04:
linux-modules-nvidia-440-generic-hwe-20.04 depends on 
linux-modules-nvidia-440
  -5.4.0-25-generic (= 5.4.0-25.29); however:
 Package linux-modules-nvidia-440-5.4.0-25-generic is not configured yet.
   
   dpkg: error processing package linux-modules-nvidia-440-generic-hwe-20.04 
(--configure):
dependency problems - leaving unconfigured

  It's a problem with the nesting of debconf: Ubiquity itself is using
  debconf, and ubuntu-drivers is installing -nvidia- packages which
  themselves also use debconf, and we don't know how to connect ubuntu-
  drivers use of debconf with the ubiquity one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1874278/+subscriptions

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

[Desktop-packages] [Bug 1366418] Re: Bluetooth BCM43142A0 doesn’t work

[Gannet]

Kubuntu 20.04 LTS
HP ProBook 455 G3

$ dmesg | grep -i error
[   20.229516] bluetooth hci0: Direct firmware load for 
brcm/BCM43142A0-0a5c-216d.hcd failed with error -2
[ 1242.727869] bluetooth hci0: Direct firmware load for 
brcm/BCM43142A0-0a5c-216d.hcd failed with error -2
[ 5759.316789] bluetooth hci0: Direct firmware load for 
brcm/BCM43142A0-0a5c-216d.hcd failed with error -2

** Tags added: focal

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

** Changed in: bluez (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  Bluetooth BCM43142A0 doesn’t work

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I’ve installed ubuntu 14.04 and my computer’s builtin bluetooth
  (computer is an Asus x550ln) doesn’t work at all. Bluetooth is not
  displayed in the menu bar, if I open the bluetooth UI and switch on,
  nothing happens and the result of “hcitool dev” is empty.

  I have tried to install the windows driver with ndiswrapper, and the
  bluetooth device seems to be detected as an usb bluetooth device but
  still not working. I then add the device to the bluetooth usb device
  and was able to activate bluetooth in the UI but it does not detect
  any other devices (I’ve tested with a smartphone).

  The driver I have installed can be found in asus page =>
  http://www.asus.com/fr/Notebooks_Ultrabooks/X550LN/HelpDesk_Download/
  Select Windows OS, then “bluetooth” section, take the Broadcom driver
  (should be the first one).

  If you extract this archive, you will find a file named “bcbtums-
  win8x64-brcm.inf” which I installed using the following command:

  ndiswrapper -i bcbtums-win8x64-brcm.inf

  Then, the result of “ndiswrapper -l” is:

  bcbtums-win8x64-brcm : driver installed
device (04CA:2006) present

  in usb-devices, I find a device which was not present before
  installation (I might have activated btusb before on this paste):

  T:  Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
  D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=04ca ProdID=2006 Rev=01.12
  S:  Manufacturer=Broadcom Corp
  S:  Product=BCM43142A0
  S:  SerialNumber=B8EE6593D989
  C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
  I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
  I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

  then, “echo "04ca 2006" > /sys/bus/usb/drivers/btusb/new_id”, and I
  can switch usb on, but no device will be detected and I’ve found this
  in the dmesg:

  [2200.843126] Bluetooth: hci0 command 0x1003 tx timeout

  which looks pretty much like a “bluetooth not working” message which I
  don’t understand in details.

  I leave here my full dmesg:

  [0.253889] NetLabel:  domain hash size = 128
  [0.253890] NetLabel:  protocols = UNLABELED CIPSOv4
  [0.253901] NetLabel:  unlabeled traffic allowed by default
  [0.253959] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0
  [0.253965] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
  [0.255995] Switched to clocksource hpet
  [0.260468] AppArmor: AppArmor Filesystem Enabled
  [0.260488] pnp: PnP ACPI init
  [0.260500] ACPI: bus type PNP registered
  [0.260592] system 00:00: [mem 0xfed4-0xfed44fff] has been reserved
  [0.260596] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
  [0.260642] pnp 00:01: [dma 4]
  [0.260658] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
  [0.260678] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
  [0.260782] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
  [0.260924] system 00:04: [io  0x0680-0x069f] has been reserved
  [0.260927] system 00:04: [io  0x] has been reserved
  [0.260928] system 00:04: [io  0x] has been reserved
  [0.260930] system 00:04: [io  0x] has been reserved
  [0.260932] system 00:04: [io  0x1c00-0x1cfe] has been reserved
  [0.260934] system 00:04: [io  0x1d00-0x1dfe] has been reserved
  [0.260935] system 00:04: [io  0x1e00-0x1efe] has been reserved
  [0.260937] system 00:04: [io  0x1f00-0x1ffe] has been reserved
  [0.260939] system 00:04: [io  0x1800-0x18fe] could not be reserved
  [0.260941] system 00:04: [io  0x164e-0x164f] has been reserved
  [0.260943] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
  [0.260969] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
  [0.261012] system 00:06: [io  0x1854-0x1857] has been reserved
  [0.261014] system 00:06: Plug and 

[Desktop-packages] [Bug 1874333] [NEW] Titlebar buttons are placed in the wrong place

[Kristijan Žic ]

Public bug reported:

Titlebar buttons in the Ubuntu Settings app on Ubuntu 20.04 are placed
in the wrong place when the placement is set to the left side.

I've attached the image describing the issue.

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

** Attachment added: "Image describing the issue"
   https://bugs.launchpad.net/bugs/1874333/+attachment/5358154/+files/bitmap.png

** Description changed:

- Titlebar buttons are placed in the wrong place when the placement is set
- to the left side.
+ Titlebar buttons in the Ubuntu Settings app are placed in the wrong
+ place when the placement is set to the left side.
  
  I've attached the image describing the issue.

** Description changed:

- Titlebar buttons in the Ubuntu Settings app are placed in the wrong
- place when the placement is set to the left side.
+ Titlebar buttons in the Ubuntu Settings app on Ubuntu 20.04 are placed
+ in the wrong place when the placement is set to the left side.
  
  I've attached the image describing the issue.

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

Title:
  Titlebar buttons are placed in the wrong place

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  Titlebar buttons in the Ubuntu Settings app on Ubuntu 20.04 are placed
  in the wrong place when the placement is set to the left side.

  I've attached the image describing the issue.

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

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

[Desktop-packages] [Bug 1872146] Re: Audio on Headphones stopped working

[Shaun]

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

HI

I did sudo apt-get install --reinstall alsa-base pulseaudio
sudo alsa force-reload

Did a restart and it sems to be working now.

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

Title:
  Audio on Headphones stopped working

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Audio via my headphones worked yesterday, Today no such luck.

  When I plug in my headphone, Plasma picks it up but no sound.

  Bluetooth headset still works.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Fri Apr 10 23:03:09 2020
  InstallationDate: Installed on 2020-04-05 (5 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200404)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1874207] Re: Compiler warnings in x11-Add-support-for-fractional-scaling-using-Randr.patch

[Launchpad Bug Tracker]

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

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

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

Title:
  Compiler warnings in x11-Add-support-for-fractional-scaling-using-
  Randr.patch

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  There are a couple of compiler warnings apparently caused by x11-Add-
  support-for-fractional-scaling-using-Randr.patch:

  
  [427/1390] Compiling C object 
'src/25a...ends_meta-monitor-config-manager.c.o'.
  ../src/backends/meta-monitor-config-manager.c: In function 
‘assign_monitor_crtc’:
  ../src/backends/meta-monitor-config-manager.c:226:3: warning: enumeration 
value ‘META_LOGICAL_MONITOR_LAYOUT_MODE_GLOBAL_UI_LOGICAL’ not handled in 
switch [-Wswitch]
    226 |   switch (data->config->layout_mode)
    |   ^~
  [471/1390] Compiling C object 
'src/25a..._x11_meta-monitor-manager-xrandr.c.o'.
  ../src/backends/x11/meta-monitor-manager-xrandr.c: In function 
‘meta_monitor_manager_xrandr_get_capabilities’:
  ../src/backends/x11/meta-monitor-manager-xrandr.c:1169:18: warning: 
‘capabilities’ may be used uninitialized in this function 
[-Wmaybe-uninitialized]
   1169 | capabilities |= META_MONITOR_MANAGER_CAPABILITY_TILING;
    | ~^

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

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

[Desktop-packages] [Bug 1874281] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1

[Bill (franksmcb)]

I can install Chromium without issue via Welcome's Browser selector and
Software Boutique.

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

Title:
  package chromium-browser (not installed) failed to install/upgrade:
  new chromium-browser package pre-installation script subprocess
  returned error exit status 1

Status in chromium-browser package in Ubuntu:
  Incomplete
Status in ubuntu-mate-welcome package in Ubuntu:
  New

Bug description:
  Does not install from Ubuntu MATE Welcome.

  Logs:

   
   installArchives() failed:
 
  Selecting previously unselected package chromium-browser.
  (Reading database ... 
  (Reading database ... 5%%
  (Reading database ... 10%%
  (Reading database ... 15%%
  (Reading database ... 20%%
  (Reading database ... 25%%
  (Reading database ... 30%%
  (Reading database ... 35%%
  (Reading database ... 40%%
  (Reading database ... 45%%
  (Reading database ... 50%%
  (Reading database ... 55%%
  (Reading database ... 60%%
  (Reading database ... 65%%
  (Reading database ... 70%%
  (Reading database ... 75%%
  (Reading database ... 80%%
  (Reading database ... 85%%
  (Reading database ... 90%%
  (Reading database ... 95%%
  (Reading database ... 100%%
  (Reading database ... 673766 files and directories currently installed.)
  Preparing to unpack .../chromium-browser_80.0.3987.163-0ubuntu1_amd64.deb ...
  => Installing the chromium snap
  ==> Checking connectivity with the snap store
  ==> Installing the chromium snap
  : cannot communicate with server: timeout exceeded while waiting for response
  dpkg: error processing archive 
/var/cache/apt/archives/chromium-browser_80.0.3987.163-0ubuntu1_amd64.deb 
(--unpack):
   new chromium-browser package pre-installation script subprocess returned 
error exit status 1
  Selecting previously unselected package chromium-browser-l10n.
  Preparing to unpack .../chromium-browser-l10n_80.0.3987.163-0ubuntu1_all.deb 
...
  Unpacking chromium-browser-l10n (80.0.3987.163-0ubuntu1) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/chromium-browser_80.0.3987.163-0ubuntu1_amd64.deb
  dpkg: dependency problems prevent configuration of chromium-browser-l10n:
   chromium-browser-l10n depends on chromium-browser (>= 
80.0.3987.163-0ubuntu1); however:
Package chromium-browser is not installed.

  dpkg: error processing package chromium-browser-l10n (--configure):
   dependency problems - leaving unconfigured

  
  ---

   Следующие пакеты имеют неудовлетворённые зависимости:

  chromium-browser-l10n: Depends: chromium-browser (>=
  80.0.3987.163-0ubuntu1) но он не установлен

  
  ---

  Следующие пакеты имеют неудовлетворённые зависимости:

  chromium-browser-l10n: Depends: chromium-browser (>=
  80.0.3987.163-0ubuntu1) но он не установлен

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  AptOrdering:
   chromium-browser:amd64: Install
   chromium-browser-l10n:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Apr 22 17:56:36 2020
  ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2020-04-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200421)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: chromium-browser
  Title: package chromium-browser (not installed) failed to install/upgrade: 
new chromium-browser package pre-installation script subprocess returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874281/+subscriptions

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

[Desktop-packages] [Bug 1701047] Re: Renaming of conf file fails

[Bug Watch Updater]

** Changed in: fonts-gujr-extra (Debian)
   Status: New => Fix Released

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

Title:
  Renaming of conf file fails

Status in fonts-beng-extra package in Ubuntu:
  Fix Released
Status in fonts-deva-extra package in Ubuntu:
  Fix Released
Status in fonts-gujr-extra package in Ubuntu:
  Fix Released
Status in fonts-guru-extra package in Ubuntu:
  Fix Released
Status in fonts-orya-extra package in Ubuntu:
  Fix Released
Status in fonts-beng-extra source package in Bionic:
  Fix Released
Status in fonts-deva-extra source package in Bionic:
  Fix Released
Status in fonts-gujr-extra source package in Bionic:
  Fix Released
Status in fonts-guru-extra source package in Bionic:
  Fix Released
Status in fonts-orya-extra source package in Bionic:
  Fix Released
Status in fonts-beng-extra package in Debian:
  Fix Released
Status in fonts-deva-extra package in Debian:
  Fix Released
Status in fonts-gujr-extra package in Debian:
  Fix Released
Status in fonts-guru-extra package in Debian:
  Fix Released
Status in fonts-orya-extra package in Debian:
  Fix Released

Bug description:
  [Impact]
  The fix of  wasn't accomplished properly. 
Renamings of conf files weren't addressed in maintainer scripts, upgrades from 
previous versions fail in this respect, and the package system generates 
warning messages.

  The problem has been reported in Debian, and the purpose of this bug
  report is to keep track of the progress.

  [Justification]
  This config file is broken in xenial and will still be broken on upgrade to 
bionic, which means the fonts in question will not be available to the system 
as intended if the user has upgraded.

  [Test case]
  For each of
  - fonts-beng-extra
  - fonts-deva-extra
  - fonts-gujr-extra
  - fonts-guru-extra
  - fonts-orya-extra
  - fonts-telu-extra:

  * Purge the package if installed and clean up possible leftovers
    due to the issue.

  * Install the Xenial version of the package and find that the symlink
    in /etc/fonts/conf.d incorrectly points to a directory.

  * Install the version in bionic-release and find that the attempt
    to fix the issue fails

  * Install the version in bionic-proposed and find that it fixes the
    issue and that the symlink now correctly points to the conf file.

  [Regression potential]
  Because this modifies maintainer scripts there is possibility of introducing 
a regression that will cause the package to fail to unpack.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-beng-extra/+bug/1701047/+subscriptions

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

[Desktop-packages] [Bug 1866974] Re: The Diffie-Hellman prime sent by the server is not acceptable

[Neil Green]

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

Want to add my thanks as well Simon, I'm still getting a warning abut a
wildcard cert, but it's at least functional now!

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

Title:
  The Diffie-Hellman prime sent by the server is not acceptable

Status in evolution package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  I can no longer connect to my ISP mail server.
  Works in previous version 19.10

  "The reported error was “Failed to get capabilities: Error performing
  TLS handshake: The Diffie-Hellman prime sent by the server is not
  acceptable (not long enough).”."

  I've tried finding a workaround but so far no luck.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: evolution 3.35.92-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 11:07:01 2020
  InstallationDate: Installed on 2020-03-03 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1874299] GsettingsChanges.txt

[Helio Victor]

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1874299/+attachment/5358100/+files/GsettingsChanges.txt

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

Title:
  PC crashes / freezes when removing application icons in created
  folders

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The computer freezes / freezes when several app icons are removed from a 
created folder, it is necessary to manually disconnect to get back to work.
  Folders created in the case would be this gnome function: 
https://www.youtube.com/watch?v=dXIqt7z5e9U

  Operating System: Ubuntu 20.04 LTS
  Kernel: Linux 5.4.0-26-generic
  gnome-shell: 3.36.1-5ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-08-13 (253 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.36.1-5ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-16 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-04-22T16:09:17.155220

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

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

[Desktop-packages] [Bug 1874262] Re: User session does not start: Problem with chrome-remote-desktop

[El jinete sin cabeza]

** Summary changed:

- User session does not start: xkbcomp "Internal error: Could not resolve 
keysym Invalid"
+ User session does not start: Problem with chrome-remote-desktop

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

Title:
  User session does not start: Problem with chrome-remote-desktop

Status in gdm3 package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  New

Bug description:
  https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/14
  https://gitlab.gnome.org/GNOME/gdm/-/issues/593

  ---

  Today I tried to log into my ubuntu session with my personal account
  through Xorg and Xwayland. And I couldn't, I had to install lightdm
  and to be able to enter.

  In my experience, I found this message ($journalctl):
  Apr 22 09:06:44 romanescu gnome-shell [3651]: The XKEYBOARD keymap compiler 
(xkbcomp) reports:
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> Warning: Unsupported maximum 
keycode 569, clipping.
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> X11 cannot support keycodes 
above 255.
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> Internal error: Could not 
resolve keysym Invalid
  Apr 22 09:06:44 romanescu gnome-shell [3651]: Errors from xkbcomp are not 
fatal to the X server

  Attached log of the attempt to log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  Uname: Linux 5.6.6-050606-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 22 09:54:26 2020
  InstallationDate: Installed on 2018-12-02 (506 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1874299] ProcCpuinfoMinimal.txt

[Helio Victor]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1874299/+attachment/5358101/+files/ProcCpuinfoMinimal.txt

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

Title:
  PC crashes / freezes when removing application icons in created
  folders

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The computer freezes / freezes when several app icons are removed from a 
created folder, it is necessary to manually disconnect to get back to work.
  Folders created in the case would be this gnome function: 
https://www.youtube.com/watch?v=dXIqt7z5e9U

  Operating System: Ubuntu 20.04 LTS
  Kernel: Linux 5.4.0-26-generic
  gnome-shell: 3.36.1-5ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-08-13 (253 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.36.1-5ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-16 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-04-22T16:09:17.155220

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

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

[Desktop-packages] [Bug 1874299] ShellJournal.txt

[Helio Victor]

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1874299/+attachment/5358103/+files/ShellJournal.txt

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

Title:
  PC crashes / freezes when removing application icons in created
  folders

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The computer freezes / freezes when several app icons are removed from a 
created folder, it is necessary to manually disconnect to get back to work.
  Folders created in the case would be this gnome function: 
https://www.youtube.com/watch?v=dXIqt7z5e9U

  Operating System: Ubuntu 20.04 LTS
  Kernel: Linux 5.4.0-26-generic
  gnome-shell: 3.36.1-5ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-08-13 (253 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.36.1-5ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-16 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-04-22T16:09:17.155220

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

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

[Desktop-packages] [Bug 1874299] ProcEnviron.txt

[Helio Victor]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1874299/+attachment/5358102/+files/ProcEnviron.txt

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

Title:
  PC crashes / freezes when removing application icons in created
  folders

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The computer freezes / freezes when several app icons are removed from a 
created folder, it is necessary to manually disconnect to get back to work.
  Folders created in the case would be this gnome function: 
https://www.youtube.com/watch?v=dXIqt7z5e9U

  Operating System: Ubuntu 20.04 LTS
  Kernel: Linux 5.4.0-26-generic
  gnome-shell: 3.36.1-5ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-08-13 (253 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.36.1-5ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-16 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-04-22T16:09:17.155220

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

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

[Desktop-packages] [Bug 1874299] Re: PC crashes / freezes when removing application icons in created folders

[Helio Victor]

apport information

** Tags added: apport-collected

** Description changed:

  The computer freezes / freezes when several app icons are removed from a 
created folder, it is necessary to manually disconnect to get back to work.
  Folders created in the case would be this gnome function: 
https://www.youtube.com/watch?v=dXIqt7z5e9U
  
  Operating System: Ubuntu 20.04 LTS
  Kernel: Linux 5.4.0-26-generic
  gnome-shell: 3.36.1-5ubuntu1
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2019-08-13 (253 days ago)
+ InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
+ Package: gnome-shell 3.36.1-5ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
+ RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
+ Tags:  focal
+ Uname: Linux 5.4.0-26-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-04-16 (6 days ago)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ modified.conffile..etc.default.apport:
+  # set this to 0 to disable apport, or to 1 to enable it
+  # you can temporarily override this with
+  # sudo service apport start force_start=1
+  enabled=0
+ mtime.conffile..etc.default.apport: 2020-04-22T16:09:17.155220

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1874299/+attachment/5358099/+files/Dependencies.txt

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

Title:
  PC crashes / freezes when removing application icons in created
  folders

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The computer freezes / freezes when several app icons are removed from a 
created folder, it is necessary to manually disconnect to get back to work.
  Folders created in the case would be this gnome function: 
https://www.youtube.com/watch?v=dXIqt7z5e9U

  Operating System: Ubuntu 20.04 LTS
  Kernel: Linux 5.4.0-26-generic
  gnome-shell: 3.36.1-5ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-08-13 (253 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.36.1-5ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-16 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-04-22T16:09:17.155220

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

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

[Desktop-packages] [Bug 1874299] Re: PC crashes / freezes when removing application icons in created folders

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:

  apport-collect 1874299

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

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

Title:
  PC crashes / freezes when removing application icons in created
  folders

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The computer freezes / freezes when several app icons are removed from a 
created folder, it is necessary to manually disconnect to get back to work.
  Folders created in the case would be this gnome function: 
https://www.youtube.com/watch?v=dXIqt7z5e9U

  Operating System: Ubuntu 20.04 LTS
  Kernel: Linux 5.4.0-26-generic
  gnome-shell: 3.36.1-5ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-08-13 (253 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Package: gnome-shell 3.36.1-5ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-16 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-04-22T16:09:17.155220

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

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

[Desktop-packages] [Bug 1874299] Re: PC crashes / freezes when removing application icons in created folders

[Helio Victor]

** Description changed:

  The computer freezes / freezes when several app icons are removed from a 
created folder, it is necessary to manually disconnect to get back to work.
  Folders created in the case would be this gnome function: 
https://www.youtube.com/watch?v=dXIqt7z5e9U
  
  Operating System: Ubuntu 20.04 LTS
  Kernel: Linux 5.4.0-26-generic
- Architecture: x86-64
  gnome-shell: 3.36.1-5ubuntu1

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

Title:
  PC crashes / freezes when removing application icons in created
  folders

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The computer freezes / freezes when several app icons are removed from a 
created folder, it is necessary to manually disconnect to get back to work.
  Folders created in the case would be this gnome function: 
https://www.youtube.com/watch?v=dXIqt7z5e9U

  Operating System: Ubuntu 20.04 LTS
  Kernel: Linux 5.4.0-26-generic
  gnome-shell: 3.36.1-5ubuntu1

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

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

[Desktop-packages] [Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 and 5.6

[Butterfly]

Which patch?

buildfix_kernel_4.11.patch
buildfix_kernel_5.2.patch
use-kmem_cache_create_usercopy-on-4.16.patch
disable_fstack-clash-protection_fcf-protection.patch
do-not-call-pci_save_state.patch

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

Title:
  Nvidia 340.108 fails to install with kernels 5.5 and 5.6

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  Hi developers,

  thanks for your great work on porting legacy drivers to Ubuntu.

  Anyway I have to complain in not seeing Nvidia 340.108 driver for
  kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4,
  because Nvidia 340.108 fails to install with kernels 5.5 and 5.6.

  Archlinux already has a driver for Kernel 5.6 via AUR
  (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has
  one for kernel 5.5.

  So, the question is: when will we see a new version in repositories?

  Bye and have a nice day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions

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

[Desktop-packages] [Bug 1874299] Re: PC crashes / freezes when removing application icons in created folders

[Helio Victor]

** Description changed:

  The computer freezes / freezes when several app icons are removed from a 
created folder, it is necessary to manually disconnect to get back to work.
  Folders created in the case would be this gnome function: 
https://www.youtube.com/watch?v=dXIqt7z5e9U
  
- Ubuntu 20.04
+ Operating System: Ubuntu 20.04 LTS
+ Kernel: Linux 5.4.0-26-generic
+ Architecture: x86-64
  gnome-shell: 3.36.1-5ubuntu1

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

Title:
  PC crashes / freezes when removing application icons in created
  folders

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The computer freezes / freezes when several app icons are removed from a 
created folder, it is necessary to manually disconnect to get back to work.
  Folders created in the case would be this gnome function: 
https://www.youtube.com/watch?v=dXIqt7z5e9U

  Operating System: Ubuntu 20.04 LTS
  Kernel: Linux 5.4.0-26-generic
  Architecture: x86-64
  gnome-shell: 3.36.1-5ubuntu1

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

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

[Desktop-packages] [Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 and 5.6

[satmandu]

The other patches are needed! For instance, there is display corruption
after sleep without one of the other patches.

(That has returned after the other patches were removed.)

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

Title:
  Nvidia 340.108 fails to install with kernels 5.5 and 5.6

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  Hi developers,

  thanks for your great work on porting legacy drivers to Ubuntu.

  Anyway I have to complain in not seeing Nvidia 340.108 driver for
  kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4,
  because Nvidia 340.108 fails to install with kernels 5.5 and 5.6.

  Archlinux already has a driver for Kernel 5.6 via AUR
  (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has
  one for kernel 5.5.

  So, the question is: when will we see a new version in repositories?

  Bye and have a nice day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions

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

[Desktop-packages] [Bug 1874299] Re: PC crashes / freezes when removing application icons in created folders

[Helio Victor]

** Tags added: focal

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

Title:
  PC crashes / freezes when removing application icons in created
  folders

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The computer freezes / freezes when several app icons are removed from a 
created folder, it is necessary to manually disconnect to get back to work.
  Folders created in the case would be this gnome function: 
https://www.youtube.com/watch?v=dXIqt7z5e9U

  Ubuntu 20.04
  gnome-shell: 3.36.1-5ubuntu1

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

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

[Desktop-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-drivers-common - 1:0.8.1

---
ubuntu-drivers-common (1:0.8.1) focal; urgency=medium

  [ Alberto Milone ]
  * UbuntuDrivers/detect.py,
UbuntuDrivers/kerneldetection.py,
tests/test_ubuntu_drivers.py,
ubuntu-drivers:
- Add tests for the -generic-hwe-20.04 flavour and for
  the -oem-20.04 linux flavour.
- Add detection logic to get the linux metapackage and
  linux-modules for -hwe-20.04 (LP: #1873867).
- List the modules provider when it is either a dkms package
  or a linux-modules package.
- Install linux-modules packages when available.
  This makes the NVIDIA drivers work with Secure Boot.

  [ Dimitri John Ledkov ]
  * UbuntuDrivers/detect.py,
UbuntuDrivers/kerneldetection.py:
- Use exact matching in find_reverse_deps() with both
  installed and candidate.

 -- Alberto Milone   Tue, 21 Apr 2020
21:14:15 +0200

** Changed in: ubuntu-drivers-common (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  ubuntu-drivers changes kernel flavour when installing nvidia

Status in linux package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-440 source package in Focal:
  Fix Released
Status in ubiquity source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Released
Status in ubuntu-meta source package in Focal:
  Fix Committed

Bug description:
  $ dpkg-query -W linux-image-*
  linux-image-5.4.0-25-generic  5.4.0-25.29
  linux-image-generic-hwe-20.04 5.4.0.25.31

  $ ubuntu-drivers list
  nvidia-driver-390
  nvidia-driver-435
  nvidia-driver-440

  
  $ sudo ubuntu-drivers install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-kernel-common-440
nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 
screen-resolution-extra xserver-xorg-video-nvidia-440
  Suggested packages:
fdutils linux-doc | linux-source-5.4.0 linux-tools 
linux-headers-5.4.0-25-lowlatency
  Recommended packages:
libnvidia-compute-440:i386 libnvidia-decode-440:i386 
libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 
libnvidia-gl-440:i386
  The following NEW packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-driver-440
nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime 
nvidia-settings nvidia-utils-440 screen-resolution-extra 
xserver-xorg-video-nvidia-440
  0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded.

  I was expecting for it to pick linux-modules-nvidia-440-generic-
  hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04

  As if it sorted things and picked last one?

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

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

[Desktop-packages] [Bug 1874278] Re: Can't install any packages with ubuntu-drivers using ubuntu-drivers when invoked from ubiquity

[Launchpad Bug Tracker]

This bug was fixed in the package linux-restricted-modules -
5.4.0-26.30+1

---
linux-restricted-modules (5.4.0-26.30+1) focal; urgency=medium

  * Can't install any packages with ubuntu-drivers using ubuntu-drivers when
invoked from ubiquity (LP: #1874278)
- [Packaging] work around lack of debconf in the installer host

 -- Andy Whitcroft   Wed, 22 Apr 2020 17:03:46 +0100

** Changed in: linux-restricted-modules (Ubuntu)
   Status: New => Fix Released

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

Title:
  Can't install any packages with ubuntu-drivers using ubuntu-drivers
  when invoked from ubiquity

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  We are in the process of switching ubuntu-drivers to installing linux-
  restricted-modules versions of NVidia drivers when it can, but this
  fails when Ubiquity invokes ubuntu-drivers, like:

  Setting up linux-modules-nvidia-440-5.4.0-25-generic (5.4.0-25.29) ...
   /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-25-generic.postinst: 44: 
3: B
  ad file descriptor
   dpkg: error processing package linux-modules-nvidia-440-5.4.0-25-generic 
(--con
  figure):
installed linux-modules-nvidia-440-5.4.0-25-generic package 
post-installation 
  script subprocess returned error exit status 2
   dpkg: dependency problems prevent configuration of 
linux-modules-nvidia-440-gen
  eric-hwe-20.04:
linux-modules-nvidia-440-generic-hwe-20.04 depends on 
linux-modules-nvidia-440
  -5.4.0-25-generic (= 5.4.0-25.29); however:
 Package linux-modules-nvidia-440-5.4.0-25-generic is not configured yet.
   
   dpkg: error processing package linux-modules-nvidia-440-generic-hwe-20.04 
(--configure):
dependency problems - leaving unconfigured

  It's a problem with the nesting of debconf: Ubiquity itself is using
  debconf, and ubuntu-drivers is installing -nvidia- packages which
  themselves also use debconf, and we don't know how to connect ubuntu-
  drivers use of debconf with the ubiquity one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1874278/+subscriptions

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

[Desktop-packages] [Bug 1874049] Re: Gnome-shell block

[Emanuele]

Test 2: https://youtu.be/erRt5MIA81o

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

Title:
  Gnome-shell block

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have gnome-shell blocked, when I click on any part of the shell: dock, menu 
etc ... nothing happens. I can only switch between windows with alt + tab.
  This is not the first time it happens, it has done so by replicating these 
steps: Virtual manager with OS started, taken the GNOME screenshot tool on 
Ubuntu (host), I select the screenshot (select area to be captured) I select a 
part of the screen on Virtual Manager, at this point the whole shell freezes, 
becomes non-clickable.

  I hope the explanation is understandable and helpful to improve
  Ubuntu. Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 21 12:53:28 2020
  DisplayManager: gdm3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  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/1874049/+subscriptions

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

[Desktop-packages] [Bug 1874049] Re: Gnome-shell block

[Emanuele]

Update: I tried installing the "gnome-session" session, without extensions 
pre-installed with Ubuntu.
After many attempts, I was unable to reproduce the bug with "gnome-screenshot".

Another test: I installed in VM through the Ubuntu 20.04 daily ISO of
"2020-04-21 20:32", with the default extensions of Ubuntu, I managed to
reproduce the bug.

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

Title:
  Gnome-shell block

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have gnome-shell blocked, when I click on any part of the shell: dock, menu 
etc ... nothing happens. I can only switch between windows with alt + tab.
  This is not the first time it happens, it has done so by replicating these 
steps: Virtual manager with OS started, taken the GNOME screenshot tool on 
Ubuntu (host), I select the screenshot (select area to be captured) I select a 
part of the screen on Virtual Manager, at this point the whole shell freezes, 
becomes non-clickable.

  I hope the explanation is understandable and helpful to improve
  Ubuntu. Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 21 12:53:28 2020
  DisplayManager: gdm3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  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/1874049/+subscriptions

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

[Desktop-packages] [Bug 1874299] [NEW] PC crashes / freezes when removing application icons in created folders

[Helio Victor]

Public bug reported:

The computer freezes / freezes when several app icons are removed from a 
created folder, it is necessary to manually disconnect to get back to work.
Folders created in the case would be this gnome function: 
https://www.youtube.com/watch?v=dXIqt7z5e9U

Ubuntu 20.04
gnome-shell: 3.36.1-5ubuntu1

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

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

Title:
  PC crashes / freezes when removing application icons in created
  folders

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The computer freezes / freezes when several app icons are removed from a 
created folder, it is necessary to manually disconnect to get back to work.
  Folders created in the case would be this gnome function: 
https://www.youtube.com/watch?v=dXIqt7z5e9U

  Ubuntu 20.04
  gnome-shell: 3.36.1-5ubuntu1

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

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

[Desktop-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia

[Dimitri John Ledkov]

I am very happy with the new  ubuntu-drivers-common and l-r-m in
proposed! Installed all the right things, with latelink=false on the
host system, and latelink=true in target.

Just need all of these to migrate, respin, retest, ship.

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

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

Title:
  ubuntu-drivers changes kernel flavour when installing nvidia

Status in linux package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-440 source package in Focal:
  Fix Released
Status in ubiquity source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in ubuntu-meta source package in Focal:
  Fix Committed

Bug description:
  $ dpkg-query -W linux-image-*
  linux-image-5.4.0-25-generic  5.4.0-25.29
  linux-image-generic-hwe-20.04 5.4.0.25.31

  $ ubuntu-drivers list
  nvidia-driver-390
  nvidia-driver-435
  nvidia-driver-440

  
  $ sudo ubuntu-drivers install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-kernel-common-440
nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 
screen-resolution-extra xserver-xorg-video-nvidia-440
  Suggested packages:
fdutils linux-doc | linux-source-5.4.0 linux-tools 
linux-headers-5.4.0-25-lowlatency
  Recommended packages:
libnvidia-compute-440:i386 libnvidia-decode-440:i386 
libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 
libnvidia-gl-440:i386
  The following NEW packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-driver-440
nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime 
nvidia-settings nvidia-utils-440 screen-resolution-extra 
xserver-xorg-video-nvidia-440
  0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded.

  I was expecting for it to pick linux-modules-nvidia-440-generic-
  hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04

  As if it sorted things and picked last one?

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

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

[Desktop-packages] [Bug 1874281] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1

[Norbert]

Of course I was connected to the Internet, I have installed all stuff
from MATE Welcome. It run `apt-get update`'s hundreds of times.

Now I do:

```
$ snap refresh 
Все пакеты актуальны.

sudo apt install --reinstall chromium-browser
[sudo] пароль для mate: 
Чтение списков пакетов… Готово
Построение дерева зависимостей   
Чтение информации о состоянии… Готово

Следующие НОВЫЕ пакеты будут установлены:
  chromium-browser
Обновлено 0 пакетов, установлено 1 новых пакетов, для удаления отмечено 0 
пакетов, и 0 пакетов не обновлено.
Установлено или удалено не до конца 1 пакетов.
Необходимо скачать 0 B/48,3 kB архивов.
После данной операции объём занятого дискового пространства возрастёт на 164 kB.
Предварительная настройка пакетов …
(Чтение базы данных … на данный момент установлено 673769 файлов и каталогов.)
Подготовка к распаковке …/chromium-browser_80.0.3987.163-0ubuntu1_amd64.deb …
=> Installing the chromium snap
==> Checking connectivity with the snap store
==> Installing the chromium snap
snap "chromium" is already installed, see 'snap help refresh'
=> Snap installation complete
Распаковывается chromium-browser (80.0.3987.163-0ubuntu1) …
Настраивается пакет chromium-browser (80.0.3987.163-0ubuntu1) …
Настраивается пакет chromium-browser-l10n (80.0.3987.163-0ubuntu1) …
Обрабатываются триггеры для desktop-file-utils (0.24-1ubuntu2) …
Обрабатываются триггеры для mime-support (3.64ubuntu1) …
Обрабатываются триггеры для hicolor-icon-theme (0.17-2) …
Обрабатываются триггеры для gnome-menus (3.36.0-1ubuntu1) …
Обрабатываются триггеры для bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu2) …
Rebuilding /usr/share/applications/bamf-2.index...

```

And

```
$ sudo apt install chromium-browser-l10n --reinstall 
Чтение списков пакетов… Готово
Построение дерева зависимостей   
Чтение информации о состоянии… Готово
Следующие НОВЫЕ пакеты будут установлены:
  chromium-browser-l10n
Обновлено 0 пакетов, установлено 1 новых пакетов, для удаления отмечено 0 
пакетов, и 0 пакетов не обновлено.
Необходимо скачать 0 B/2 108 B архивов.
После данной операции объём занятого дискового пространства возрастёт на 69,6 
kB.
Выбор ранее не выбранного пакета chromium-browser-l10n.
(Чтение базы данных … на данный момент установлено 673533 файла и каталога.)
Подготовка к распаковке …/chromium-browser-l10n_80.0.3987.163-0ubuntu1_all.deb …
Распаковывается chromium-browser-l10n (80.0.3987.163-0ubuntu1) …
Настраивается пакет chromium-browser-l10n (80.0.3987.163-0ubuntu1) …

```

So something weird is going on here.

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

Title:
  package chromium-browser (not installed) failed to install/upgrade:
  new chromium-browser package pre-installation script subprocess
  returned error exit status 1

Status in chromium-browser package in Ubuntu:
  Incomplete
Status in ubuntu-mate-welcome package in Ubuntu:
  New

Bug description:
  Does not install from Ubuntu MATE Welcome.

  Logs:

   
   installArchives() failed:
 
  Selecting previously unselected package chromium-browser.
  (Reading database ... 
  (Reading database ... 5%%
  (Reading database ... 10%%
  (Reading database ... 15%%
  (Reading database ... 20%%
  (Reading database ... 25%%
  (Reading database ... 30%%
  (Reading database ... 35%%
  (Reading database ... 40%%
  (Reading database ... 45%%
  (Reading database ... 50%%
  (Reading database ... 55%%
  (Reading database ... 60%%
  (Reading database ... 65%%
  (Reading database ... 70%%
  (Reading database ... 75%%
  (Reading database ... 80%%
  (Reading database ... 85%%
  (Reading database ... 90%%
  (Reading database ... 95%%
  (Reading database ... 100%%
  (Reading database ... 673766 files and directories currently installed.)
  Preparing to unpack .../chromium-browser_80.0.3987.163-0ubuntu1_amd64.deb ...
  => Installing the chromium snap
  ==> Checking connectivity with the snap store
  ==> Installing the chromium snap
  : cannot communicate with server: timeout exceeded while waiting for response
  dpkg: error processing archive 
/var/cache/apt/archives/chromium-browser_80.0.3987.163-0ubuntu1_amd64.deb 
(--unpack):
   new chromium-browser package pre-installation script subprocess returned 
error exit status 1
  Selecting previously unselected package chromium-browser-l10n.
  Preparing to unpack .../chromium-browser-l10n_80.0.3987.163-0ubuntu1_all.deb 
...
  Unpacking chromium-browser-l10n (80.0.3987.163-0ubuntu1) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/chromium-browser_80.0.3987.163-0ubuntu1_amd64.deb
  dpkg: dependency problems prevent configuration of chromium-browser-l10n:
   chromium-browser-l10n depends on chromium-browser (>= 
80.0.3987.163-0ubuntu1); however:
Package chromium-browser is not installed.

  dpkg: error processing package chromium-browser-l10n (--configure):
   dependency problems - leaving 

[Desktop-packages] [Bug 1863608] Re: version 80 does not start using remote display (X11)

[Benjamin Cahill]

Olivier,

1. --no-xshm fixes the problem.

2. The following environment variables fix the problem:
export QT_X11_NO_MITSHM=1
export _X11_NO_MITSHM=1
export _MITSHM=0

3. Version 81.0.4044.113-0ubuntu0.16.04.1 from https://launchpad.net
/~canonical-chromium-builds/+archive/ubuntu/stage does not fix the
problem.

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

Title:
  version 80 does not start using remote display (X11)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  chromium-browser version 80.0.3987.87-0ubuntu0.16.04.1_amd64 does not
  work when using remote display; the browser window is a solid pink
  area without any menu (see picture).

  Same with the (existing?) command line option "--disable-gpu"

  Downgrading to 
  chromium-browser_79.0.3945.130-0ubuntu0.16.04.1_amd64.deb
  chromium-browser-l10n_79.0.3945.130-0ubuntu0.16.04.1_all.deb
  chromium-codecs-ffmpeg-extra_79.0.3945.130-0ubuntu0.16.04.1_amd64.deb
  resolve the issue.

  Description: Ubuntu 16.04.6 LTS
  All packages are up to date on 2020-02-17 on xenial, xenial-updates and 
xenial-security

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1863608/+subscriptions

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

[Desktop-packages] [Bug 1871960] Re: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to install/upgrade: pre-dependency problem - not installing libpam-modules:amd64

[Brian Murray]

** Changed in: libgtk3-perl (Ubuntu Focal)
   Status: Confirmed => Invalid

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

Title:
  package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to
  install/upgrade: pre-dependency problem - not installing libpam-
  modules:amd64

Status in libgtk3-perl package in Ubuntu:
  Invalid
Status in pango1.0 package in Ubuntu:
  Fix Released
Status in libgtk3-perl source package in Focal:
  Invalid
Status in pango1.0 source package in Focal:
  Fix Released

Bug description:
  I was updating ubuntu to the 20.04 version. Not all packages were
  updated. I receive new errors every few seconds. what should I do?

  Thanks
  safi

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libpam-modules 1.1.8-3.6ubuntu2.18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  Date: Fri Apr 10 00:36:08 2020
  ErrorMessage: pre-dependency problem - not installing libpam-modules:amd64
  InstallationDate: Installed on 2019-12-28 (102 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.1ubuntu1
  SourcePackage: pam
  Title: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to 
install/upgrade: pre-dependency problem - not installing libpam-modules:amd64
  UpgradeStatus: Upgraded to focal on 2020-04-09 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgtk3-perl/+bug/1871960/+subscriptions

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

[Desktop-packages] [Bug 1872230] Re: The left Ctrl key does not work when using pointer location

[Andy Whitcroft]

Bah wrong bug.

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

Title:
  The left Ctrl key does not work when using pointer location

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

Bug description:
  I am using 20.04 Focal.

  I am using a US international keyboard layout with dead keys, so that
  I can enter text in many different languages. After I had rebooted my
  system today and so loaded the newest GNOME Shell, the left Ctrl key
  stopped working in the terminal windows and also in emacs, while the
  right Ctrl still works. To get the left Ctrl working again I have to
  switch to a plain US English keyboard layout, without dead keys.

  I have also tried the different alternatives of US International
  keyboard layouts, each of them seems to work as intended but the left
  Ctrl key is not working. Only with plain US English layout I get the
  left Ctrl working.

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

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

[Desktop-packages] [Bug 1872230] Re: The left Ctrl key does not work when using pointer location

[Andy Whitcroft]

I am seeing this with Pointer Location turned off; this being the super
key not doing activited.

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

Title:
  The left Ctrl key does not work when using pointer location

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

Bug description:
  I am using 20.04 Focal.

  I am using a US international keyboard layout with dead keys, so that
  I can enter text in many different languages. After I had rebooted my
  system today and so loaded the newest GNOME Shell, the left Ctrl key
  stopped working in the terminal windows and also in emacs, while the
  right Ctrl still works. To get the left Ctrl working again I have to
  switch to a plain US English keyboard layout, without dead keys.

  I have also tried the different alternatives of US International
  keyboard layouts, each of them seems to work as intended but the left
  Ctrl key is not working. Only with plain US English layout I get the
  left Ctrl working.

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

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

[Desktop-packages] [Bug 1639863] Re: Firefox and Thunderbird don't appear in the (new) appstream metadata

[Olivier Tilloy]

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

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

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

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

Title:
  Firefox and Thunderbird don't appear in the (new) appstream metadata

Status in firefox package in Ubuntu:
  In Progress
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  The new generator doesn't understand symlinks unfortunately, so
  Firefox and Thunderbird don't appear.

  http://appstream.staging.ubuntu.com/zesty/main/issues/firefox.html

  laney@nightingale> ls /usr/share/pixmaps/firefox.png
  lrwxrwxrwx 1 root root 46 Oct 25 15:34 /usr/share/pixmaps/firefox.png -> 
../../lib/firefox/browser/icons/mozicon128.png

  To make them work, /usr/share/pixmaps/firefox.png should be a real
  file. It could either be a copy of the file, or
  /usr/lib/firefox/browser/icons/mozicon128.png could be a symlink.

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

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

[Desktop-packages] [Bug 1871723] Re: Provide an Appdata file to allow Firefox to show on application stores

[Olivier Tilloy]

** Changed in: firefox (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Provide an Appdata file to allow Firefox to show on application stores

Status in firefox package in Ubuntu:
  New

Bug description:
  It seems that Firefox itself already provides one upstream
  https://hg.mozilla.org/releases/mozilla-
  release/file/tip/taskcluster/docker/firefox-
  flatpak/org.mozilla.firefox.appdata.xml.in

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

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

[Desktop-packages] [Bug 1639863] Re: Firefox and Thunderbird don't appear in the (new) appstream metadata

[Olivier Tilloy]

slightly related: bug #1871723

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

Title:
  Firefox and Thunderbird don't appear in the (new) appstream metadata

Status in firefox package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  The new generator doesn't understand symlinks unfortunately, so
  Firefox and Thunderbird don't appear.

  http://appstream.staging.ubuntu.com/zesty/main/issues/firefox.html

  laney@nightingale> ls /usr/share/pixmaps/firefox.png
  lrwxrwxrwx 1 root root 46 Oct 25 15:34 /usr/share/pixmaps/firefox.png -> 
../../lib/firefox/browser/icons/mozicon128.png

  To make them work, /usr/share/pixmaps/firefox.png should be a real
  file. It could either be a copy of the file, or
  /usr/lib/firefox/browser/icons/mozicon128.png could be a symlink.

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

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

[Desktop-packages] [Bug 1873321] Re: The Show Applications button should be clickable in the corner or bottom of the screen

[Bug Watch Updater]

** Changed in: dash-to-dock
   Status: New => Fix Released

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

Title:
  The Show Applications button should be clickable in the corner or
  bottom of the screen

Status in Dash to dock:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Committed

Bug description:
  After one of the recent updates, clicking the Show Applications button in the 
very corner of the screen and at its bottom edge doesn't work. This bug applies 
in the cases of left and right positions of the dock and there is no this bug 
in the case of bottom position.
  This issue is very annoying since the mouse pointer runs at the very corner 
of the screen in vast majority of cases as you intent to press the Show Apps 
button.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 16 20:34:32 2020
  InstallationDate: Installed on 2019-04-25 (356 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1873321/+subscriptions

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

[Desktop-packages] [Bug 1874281] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1

[Olivier Tilloy]

This looks similar to bug #1874120.

Were you connected to the internet when installing chromium?

Could you try reinstalling it?

sudo apt install --reinstall chromium-browser

** Changed in: chromium-browser (Ubuntu)
   Status: New => 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/1874281

Title:
  package chromium-browser (not installed) failed to install/upgrade:
  new chromium-browser package pre-installation script subprocess
  returned error exit status 1

Status in chromium-browser package in Ubuntu:
  Incomplete
Status in ubuntu-mate-welcome package in Ubuntu:
  New

Bug description:
  Does not install from Ubuntu MATE Welcome.

  Logs:

   
   installArchives() failed:
 
  Selecting previously unselected package chromium-browser.
  (Reading database ... 
  (Reading database ... 5%%
  (Reading database ... 10%%
  (Reading database ... 15%%
  (Reading database ... 20%%
  (Reading database ... 25%%
  (Reading database ... 30%%
  (Reading database ... 35%%
  (Reading database ... 40%%
  (Reading database ... 45%%
  (Reading database ... 50%%
  (Reading database ... 55%%
  (Reading database ... 60%%
  (Reading database ... 65%%
  (Reading database ... 70%%
  (Reading database ... 75%%
  (Reading database ... 80%%
  (Reading database ... 85%%
  (Reading database ... 90%%
  (Reading database ... 95%%
  (Reading database ... 100%%
  (Reading database ... 673766 files and directories currently installed.)
  Preparing to unpack .../chromium-browser_80.0.3987.163-0ubuntu1_amd64.deb ...
  => Installing the chromium snap
  ==> Checking connectivity with the snap store
  ==> Installing the chromium snap
  : cannot communicate with server: timeout exceeded while waiting for response
  dpkg: error processing archive 
/var/cache/apt/archives/chromium-browser_80.0.3987.163-0ubuntu1_amd64.deb 
(--unpack):
   new chromium-browser package pre-installation script subprocess returned 
error exit status 1
  Selecting previously unselected package chromium-browser-l10n.
  Preparing to unpack .../chromium-browser-l10n_80.0.3987.163-0ubuntu1_all.deb 
...
  Unpacking chromium-browser-l10n (80.0.3987.163-0ubuntu1) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/chromium-browser_80.0.3987.163-0ubuntu1_amd64.deb
  dpkg: dependency problems prevent configuration of chromium-browser-l10n:
   chromium-browser-l10n depends on chromium-browser (>= 
80.0.3987.163-0ubuntu1); however:
Package chromium-browser is not installed.

  dpkg: error processing package chromium-browser-l10n (--configure):
   dependency problems - leaving unconfigured

  
  ---

   Следующие пакеты имеют неудовлетворённые зависимости:

  chromium-browser-l10n: Depends: chromium-browser (>=
  80.0.3987.163-0ubuntu1) но он не установлен

  
  ---

  Следующие пакеты имеют неудовлетворённые зависимости:

  chromium-browser-l10n: Depends: chromium-browser (>=
  80.0.3987.163-0ubuntu1) но он не установлен

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  AptOrdering:
   chromium-browser:amd64: Install
   chromium-browser-l10n:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Apr 22 17:56:36 2020
  ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2020-04-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200421)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: chromium-browser
  Title: package chromium-browser (not installed) failed to install/upgrade: 
new chromium-browser package pre-installation script subprocess returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874281/+subscriptions

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

[Desktop-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

[Dominik]

It also affects Linux Mint 19.3. 
I had problems with audio also, so i had to add two lines:

echo "options snd-hda-intel dmic_detect=0" | sudo tee -a 
/etc/modprobe.d/alsa-base.conf
echo "blacklist snd_soc_skl" | sudo tee -a /etc/modprobe.d/blacklist.conf

After executing these two commands audio is present again but still no
success with internal microphone. Fortunately i have detachable
microphone in my Creative Fatality headphones so after i have inserted
this microphone in microphone socket, microphone has appeared inside
pavucontrol and i am now able to record voice using this site: https
://online-voice-recorder.com/pl/ for example.

I have noticed that there are more discussions about this problem:
- https://online-voice-recorder.com/pl/
- https://github.com/thesofproject/linux/issues/1877

P.S. I have also tried to manually remap pins using: hdajackretask but
with no success.

** Bug watch added: github.com/thesofproject/linux/issues #1877
   https://github.com/thesofproject/linux/issues/1877

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

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[suKo]

Using an NVIDIA GTX 1080 on 20.04 with the latest daily image I can
confirm this bug still exists. Removing the "splash" option from the
/etc/default/grub file variable GRUB_CMDLINE_LINUX_DEFAULT seems to fix
the issue. I too encountered this with automatic boot enabled, and it
also occurs no matter which version of the NVIDIA driver I use (except
for the FOSS driver). Unusually, this does not occur on my laptop which
also has an NVIDIA GPU (in this case, a 1650).

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: 

[Desktop-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia

[Steve Langasek]

** Changed in: ubuntu-drivers-common (Ubuntu Focal)
   Status: Confirmed => Fix Committed

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

Title:
  ubuntu-drivers changes kernel flavour when installing nvidia

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Incomplete
Status in nvidia-graphics-drivers-440 source package in Focal:
  Fix Released
Status in ubiquity source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in ubuntu-meta source package in Focal:
  Fix Committed

Bug description:
  $ dpkg-query -W linux-image-*
  linux-image-5.4.0-25-generic  5.4.0-25.29
  linux-image-generic-hwe-20.04 5.4.0.25.31

  $ ubuntu-drivers list
  nvidia-driver-390
  nvidia-driver-435
  nvidia-driver-440

  
  $ sudo ubuntu-drivers install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-kernel-common-440
nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 
screen-resolution-extra xserver-xorg-video-nvidia-440
  Suggested packages:
fdutils linux-doc | linux-source-5.4.0 linux-tools 
linux-headers-5.4.0-25-lowlatency
  Recommended packages:
libnvidia-compute-440:i386 libnvidia-decode-440:i386 
libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 
libnvidia-gl-440:i386
  The following NEW packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-driver-440
nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime 
nvidia-settings nvidia-utils-440 screen-resolution-extra 
xserver-xorg-video-nvidia-440
  0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded.

  I was expecting for it to pick linux-modules-nvidia-440-generic-
  hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04

  As if it sorted things and picked last one?

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

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

[Desktop-packages] [Bug 1874285] [NEW] [SRU] libreoffice 6.4.3 for focal

[Heather Ellsworth]

Public bug reported:

[Impact]

 * LibreOffice 6.4.3 is in its third bugfix release of the 6.4 line.
   For a list of fixed bugs compared to 6.4.3 see the list of bugs fixed in the 
two release candidates:
 https://wiki.documentfoundation.org/Releases/6.4.3/RC1#List_of_fixed_bugs
 https://wiki.documentfoundation.org/Releases/6.4.3/RC2#List_of_fixed_bugs
   (that's a total of 58 bugs)

 * Given the nature of the project, the complexity of the codebase and
the high level of quality assurance upstream, it is preferable to SRU a
minor release rather than cherry-pick selected bug fixes.

[Test Case]

 * No specific test case, bugs fixed upstream hopefully come with
unit/regression tests, and the release itself is extensively exercised
upstream (both in an automated manner and manually) by a community of
testers. Each minor release normally goes through two release
candidates.

 * The libreoffice packages include autopkgtests, those should be run
and verified to pass.

 * General smoke testing of all the applications in the office suite
should be carried out.

[Regression Potential]

 * A minor release with a total of 58 bug fixes always carries the
potential for introducing regressions, even though it is a bugfix-only
release, meaning that no new features were added, and no existing
features were removed.

 * A combination of autopkgtests and careful smoke testing as described
above should provide reasonable confidence that no regressions sneaked
in.

** Affects: libreoffice (Ubuntu)
 Importance: High
 Assignee: Heather Ellsworth (hellsworth)
 Status: In Progress

** Affects: libreoffice (Ubuntu Focal)
 Importance: High
 Assignee: Heather Ellsworth (hellsworth)
 Status: In Progress

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

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

** Also affects: libreoffice (Ubuntu Focal)
   Importance: High
 Assignee: Heather Ellsworth (hellsworth)
   Status: New

** Changed in: libreoffice (Ubuntu Focal)
   Status: New => In Progress

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

Title:
   [SRU] libreoffice 6.4.3 for focal

Status in libreoffice package in Ubuntu:
  In Progress
Status in libreoffice source package in Focal:
  In Progress

Bug description:
  [Impact]

   * LibreOffice 6.4.3 is in its third bugfix release of the 6.4 line.
 For a list of fixed bugs compared to 6.4.3 see the list of bugs fixed in 
the two release candidates:
   https://wiki.documentfoundation.org/Releases/6.4.3/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/6.4.3/RC2#List_of_fixed_bugs
 (that's a total of 58 bugs)

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release normally goes through two release
  candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 58 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

[Desktop-packages] [Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 and 5.6

[Butterfly]

Hi,

I added new package of nvidia-340 supported up linux 5.7 to PPA
repository.

nvidia-graphics-drivers-340 (340.108-1lmtrbionic3) bionic;
urgency=medium

  * Disabled all Ubuntu PPA and AUR based patches.
  * Added MilhouseVH's LibreELEC based patches for linux 5.5, 5.6 and 5.7 series

Thanks to MilhouseVH for patches. https://forums.developer.nvidia.com/t
/patches-for-340-108-and-5-6-rc-need-help-with-driver-init/111760/12

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

Title:
  Nvidia 340.108 fails to install with kernels 5.5 and 5.6

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  Hi developers,

  thanks for your great work on porting legacy drivers to Ubuntu.

  Anyway I have to complain in not seeing Nvidia 340.108 driver for
  kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4,
  because Nvidia 340.108 fails to install with kernels 5.5 and 5.6.

  Archlinux already has a driver for Kernel 5.6 via AUR
  (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has
  one for kernel 5.5.

  So, the question is: when will we see a new version in repositories?

  Bye and have a nice day.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions

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

[Desktop-packages] [Bug 1872276] Re: Gnome shell huge app's icon size in the app folder

[keshavbhatt]

While size of icons in the launcher app grid looks like this.

** Attachment added: "Screenshot from 2020-04-22 21-05-59.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872276/+attachment/5358012/+files/Screenshot%20from%202020-04-22%2021-05-59.png

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

Title:
  Gnome shell huge app's icon size in the app folder

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:

  Description: Ubuntu Focal Fossa (development branch)
  Release: 20.04

  Bug: Gnome shell while opening app folder created in app launcher, the
  resulting dialog holding apps of app folder are having icon size
  larger than the other apps shown in the app launcher.

  How to reproduce: 1- Click on 9 dots qt bottom corner of dash (the app 
launcher button), wait for the app grid to show up.
  2- Drag app icon to create apps folder.
  3- As the app folder gets created, click to open it and observe the size of 
app icons shown by the folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:48:05 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  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/1872276/+subscriptions

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

[Desktop-packages] [Bug 1872276] Re: Gnome shell huge app's icon size in the app folder

[keshavbhatt]

Check the size of icons in opened apps folder/group view that is huge in
comparison to app launcher grid icon size.

** Attachment added: "Screenshot from 2020-04-22 21-05-49.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872276/+attachment/5358011/+files/Screenshot%20from%202020-04-22%2021-05-49.png

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

Title:
  Gnome shell huge app's icon size in the app folder

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:

  Description: Ubuntu Focal Fossa (development branch)
  Release: 20.04

  Bug: Gnome shell while opening app folder created in app launcher, the
  resulting dialog holding apps of app folder are having icon size
  larger than the other apps shown in the app launcher.

  How to reproduce: 1- Click on 9 dots qt bottom corner of dash (the app 
launcher button), wait for the app grid to show up.
  2- Drag app icon to create apps folder.
  3- As the app folder gets created, click to open it and observe the size of 
app icons shown by the folder.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 12:48:05 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  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/1872276/+subscriptions

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

[Desktop-packages] [Bug 1874262] Re: User session does not start: xkbcomp "Internal error: Could not resolve keysym Invalid"

[El jinete sin cabeza]

https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/14

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

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

** Description changed:

+ https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/14
  https://gitlab.gnome.org/GNOME/gdm/-/issues/593
  
  ---
  
  Today I tried to log into my ubuntu session with my personal account
  through Xorg and Xwayland. And I couldn't, I had to install lightdm and
  to be able to enter.
  
  In my experience, I found this message ($journalctl):
  Apr 22 09:06:44 romanescu gnome-shell [3651]: The XKEYBOARD keymap compiler 
(xkbcomp) reports:
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> Warning: Unsupported maximum 
keycode 569, clipping.
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> X11 cannot support keycodes 
above 255.
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> Internal error: Could not 
resolve keysym Invalid
  Apr 22 09:06:44 romanescu gnome-shell [3651]: Errors from xkbcomp are not 
fatal to the X server
  
  Attached log of the attempt to log in.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  Uname: Linux 5.6.6-050606-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 22 09:54:26 2020
  InstallationDate: Installed on 2018-12-02 (506 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

** Bug watch added: gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues #14
   https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/14

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

Title:
  User session does not start: xkbcomp "Internal error: Could not
  resolve keysym Invalid"

Status in gdm3 package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  New

Bug description:
  https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/14
  https://gitlab.gnome.org/GNOME/gdm/-/issues/593

  ---

  Today I tried to log into my ubuntu session with my personal account
  through Xorg and Xwayland. And I couldn't, I had to install lightdm
  and to be able to enter.

  In my experience, I found this message ($journalctl):
  Apr 22 09:06:44 romanescu gnome-shell [3651]: The XKEYBOARD keymap compiler 
(xkbcomp) reports:
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> Warning: Unsupported maximum 
keycode 569, clipping.
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> X11 cannot support keycodes 
above 255.
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> Internal error: Could not 
resolve keysym Invalid
  Apr 22 09:06:44 romanescu gnome-shell [3651]: Errors from xkbcomp are not 
fatal to the X server

  Attached log of the attempt to log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  Uname: Linux 5.6.6-050606-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 22 09:54:26 2020
  InstallationDate: Installed on 2018-12-02 (506 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1869561] Re: Libreoffice Help does not work

[Olivier Tilloy]

It sounds like the problem is trying to open the local help custom UI,
instead of the expected behaviour (opening the local HTML help in a
browser). The debs produced by TDF do open the help in a browser, so
there is a functional discrepancy here that should be investigated.

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

Title:
  Libreoffice Help does not work

Status in libreoffice package in Ubuntu:
  Confirmed
Status in libreoffice source package in Focal:
  Confirmed

Bug description:
  In the latest PPA release of Libreoffice, the Help does not work.  IN
  version 6.3.5.2 it is OK.  I the version below it returns an error.

  Version: 6.4.2.2
  Build ID: 1:6.4.2-0ubuntu0.19.10.3
  CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: x11; 
  Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB
  Calc: threaded

  
  The Error is:

  Object not accessible.
  The object cannot be accessed
  due to insufficient user rights.

  
  The Help used to open the help in a browser window.  This latest version 
seems to try to open the old type of local help (rather than using a browser).

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

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

[Desktop-packages] [Bug 1874281] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package chromium-browser (not installed) failed to install/upgrade:
  new chromium-browser package pre-installation script subprocess
  returned error exit status 1

Status in chromium-browser package in Ubuntu:
  New
Status in ubuntu-mate-welcome package in Ubuntu:
  New

Bug description:
  Does not install from Ubuntu MATE Welcome.

  Logs:

   
   installArchives() failed:
 
  Selecting previously unselected package chromium-browser.
  (Reading database ... 
  (Reading database ... 5%%
  (Reading database ... 10%%
  (Reading database ... 15%%
  (Reading database ... 20%%
  (Reading database ... 25%%
  (Reading database ... 30%%
  (Reading database ... 35%%
  (Reading database ... 40%%
  (Reading database ... 45%%
  (Reading database ... 50%%
  (Reading database ... 55%%
  (Reading database ... 60%%
  (Reading database ... 65%%
  (Reading database ... 70%%
  (Reading database ... 75%%
  (Reading database ... 80%%
  (Reading database ... 85%%
  (Reading database ... 90%%
  (Reading database ... 95%%
  (Reading database ... 100%%
  (Reading database ... 673766 files and directories currently installed.)
  Preparing to unpack .../chromium-browser_80.0.3987.163-0ubuntu1_amd64.deb ...
  => Installing the chromium snap
  ==> Checking connectivity with the snap store
  ==> Installing the chromium snap
  : cannot communicate with server: timeout exceeded while waiting for response
  dpkg: error processing archive 
/var/cache/apt/archives/chromium-browser_80.0.3987.163-0ubuntu1_amd64.deb 
(--unpack):
   new chromium-browser package pre-installation script subprocess returned 
error exit status 1
  Selecting previously unselected package chromium-browser-l10n.
  Preparing to unpack .../chromium-browser-l10n_80.0.3987.163-0ubuntu1_all.deb 
...
  Unpacking chromium-browser-l10n (80.0.3987.163-0ubuntu1) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/chromium-browser_80.0.3987.163-0ubuntu1_amd64.deb
  dpkg: dependency problems prevent configuration of chromium-browser-l10n:
   chromium-browser-l10n depends on chromium-browser (>= 
80.0.3987.163-0ubuntu1); however:
Package chromium-browser is not installed.

  dpkg: error processing package chromium-browser-l10n (--configure):
   dependency problems - leaving unconfigured

  
  ---

   Следующие пакеты имеют неудовлетворённые зависимости:

  chromium-browser-l10n: Depends: chromium-browser (>=
  80.0.3987.163-0ubuntu1) но он не установлен

  
  ---

  Следующие пакеты имеют неудовлетворённые зависимости:

  chromium-browser-l10n: Depends: chromium-browser (>=
  80.0.3987.163-0ubuntu1) но он не установлен

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  AptOrdering:
   chromium-browser:amd64: Install
   chromium-browser-l10n:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Apr 22 17:56:36 2020
  ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2020-04-22 (0 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200421)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: chromium-browser
  Title: package chromium-browser (not installed) failed to install/upgrade: 
new chromium-browser package pre-installation script subprocess returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874281/+subscriptions

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

[Desktop-packages] [Bug 1874281] [NEW] package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1

[Norbert]

Public bug reported:

Does not install from Ubuntu MATE Welcome.

Logs:

 
 installArchives() failed:
   
Selecting previously unselected package chromium-browser.
(Reading database ... 
(Reading database ... 5%%
(Reading database ... 10%%
(Reading database ... 15%%
(Reading database ... 20%%
(Reading database ... 25%%
(Reading database ... 30%%
(Reading database ... 35%%
(Reading database ... 40%%
(Reading database ... 45%%
(Reading database ... 50%%
(Reading database ... 55%%
(Reading database ... 60%%
(Reading database ... 65%%
(Reading database ... 70%%
(Reading database ... 75%%
(Reading database ... 80%%
(Reading database ... 85%%
(Reading database ... 90%%
(Reading database ... 95%%
(Reading database ... 100%%
(Reading database ... 673766 files and directories currently installed.)
Preparing to unpack .../chromium-browser_80.0.3987.163-0ubuntu1_amd64.deb ...
=> Installing the chromium snap
==> Checking connectivity with the snap store
==> Installing the chromium snap
: cannot communicate with server: timeout exceeded while waiting for response
dpkg: error processing archive 
/var/cache/apt/archives/chromium-browser_80.0.3987.163-0ubuntu1_amd64.deb 
(--unpack):
 new chromium-browser package pre-installation script subprocess returned error 
exit status 1
Selecting previously unselected package chromium-browser-l10n.
Preparing to unpack .../chromium-browser-l10n_80.0.3987.163-0ubuntu1_all.deb ...
Unpacking chromium-browser-l10n (80.0.3987.163-0ubuntu1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/chromium-browser_80.0.3987.163-0ubuntu1_amd64.deb
dpkg: dependency problems prevent configuration of chromium-browser-l10n:
 chromium-browser-l10n depends on chromium-browser (>= 80.0.3987.163-0ubuntu1); 
however:
  Package chromium-browser is not installed.

dpkg: error processing package chromium-browser-l10n (--configure):
 dependency problems - leaving unconfigured


---

 Следующие пакеты имеют неудовлетворённые зависимости:

chromium-browser-l10n: Depends: chromium-browser (>=
80.0.3987.163-0ubuntu1) но он не установлен


---

Следующие пакеты имеют неудовлетворённые зависимости:

chromium-browser-l10n: Depends: chromium-browser (>=
80.0.3987.163-0ubuntu1) но он не установлен

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: chromium-browser (not installed)
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
AptOrdering:
 chromium-browser:amd64: Install
 chromium-browser-l10n:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Apr 22 17:56:36 2020
ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2020-04-22 (0 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200421)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2
SourcePackage: chromium-browser
Title: package chromium-browser (not installed) failed to install/upgrade: new 
chromium-browser package pre-installation script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

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


** Tags: amd64 apport-package focal

** Also affects: ubuntu-mate-welcome (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  package chromium-browser (not installed) failed to install/upgrade:
  new chromium-browser package pre-installation script subprocess
  returned error exit status 1

Status in chromium-browser package in Ubuntu:
  New
Status in ubuntu-mate-welcome package in Ubuntu:
  New

Bug description:
  Does not install from Ubuntu MATE Welcome.

  Logs:

   
   installArchives() failed:
 
  Selecting previously unselected package chromium-browser.
  (Reading database ... 
  (Reading database ... 5%%
  (Reading database ... 10%%
  (Reading database ... 15%%
  (Reading database ... 20%%
  (Reading database ... 25%%
  (Reading database ... 30%%
  (Reading database ... 35%%
  (Reading database ... 40%%
  (Reading database ... 45%%
  (Reading database ... 50%%
  (Reading database ... 55%%
  (Reading database ... 60%%
  (Reading database ... 65%%
  (Reading database ... 70%%
  (Reading database ... 75%%
  (Reading database ... 80%%
  (Reading database ... 85%%
  (Reading database ... 90%%
  (Reading database ... 95%%
  (Reading database ... 100%%
  (Reading database ... 673766 files and directories currently installed.)
  Preparing to unpack 

[Desktop-packages] [Bug 1872515] Re: Nautilus lors de l'affichage de fichiers photos RAW crée des vignettes JPEG ce qui me semble inutile car les dossiers grossisse beaucoup.

[Mike Salvatore]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. Your bug report is more likely to get attention if it is made in
English, since this is the language understood by the majority of Ubuntu
developers.  Additionally, please only mark a bug as "security" if it
shows evidence of allowing attackers to cross privilege boundaries or to
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

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

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

Title:
  Nautilus lors de l'affichage de fichiers photos RAW crée des vignettes
  JPEG ce qui me semble inutile car les dossiers grossisse beaucoup.

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Bonjour,

  Nautilus crée des fichiers JPEG lors de l'ouverture d'un dossier avec des 
fichiers photos RAW
  ça fait grossir rapidement et inutilement les dossiers.

  Cordialement

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.1.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 13 19:07:07 2020
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'201'
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
   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 2020-04-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  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/1872515/+subscriptions

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

[Desktop-packages] [Bug 1874278] [NEW] Can't install any packages with ubuntu-drivers using ubuntu-drivers when invoked from ubiquity

[Iain Lane]

Public bug reported:

We are in the process of switching ubuntu-drivers to installing linux-
restricted-modules versions of NVidia drivers when it can, but this
fails when Ubiquity invokes ubuntu-drivers, like:

Setting up linux-modules-nvidia-440-5.4.0-25-generic (5.4.0-25.29) ...
 /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-25-generic.postinst: 44: 3: B
ad file descriptor
 dpkg: error processing package linux-modules-nvidia-440-5.4.0-25-generic (--con
figure):
  installed linux-modules-nvidia-440-5.4.0-25-generic package post-installation 
script subprocess returned error exit status 2
 dpkg: dependency problems prevent configuration of linux-modules-nvidia-440-gen
eric-hwe-20.04:
  linux-modules-nvidia-440-generic-hwe-20.04 depends on linux-modules-nvidia-440
-5.4.0-25-generic (= 5.4.0-25.29); however:
   Package linux-modules-nvidia-440-5.4.0-25-generic is not configured yet.
 
 dpkg: error processing package linux-modules-nvidia-440-generic-hwe-20.04 
(--configure):
  dependency problems - leaving unconfigured

It's a problem with the nesting of debconf: Ubiquity itself is using
debconf, and ubuntu-drivers is installing -nvidia- packages which
themselves also use debconf, and we don't know how to connect ubuntu-
drivers use of debconf with the ubiquity one.

** Affects: linux-restricted-modules (Ubuntu)
 Importance: Undecided
 Status: New

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

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

** Also affects: ubuntu-drivers-common (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux-restricted-modules (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Can't install any packages via ubuntu-drivers which use debconf
+ Can't install any packages from ubiquity via ubuntu-drivers which use debconf

** Summary changed:

- Can't install any packages from ubiquity via ubuntu-drivers which use debconf
+ Can't install any packages with ubuntu-drivers using ubuntu-drivers when 
invoked from ubiquity

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

Title:
  Can't install any packages with ubuntu-drivers using ubuntu-drivers
  when invoked from ubiquity

Status in linux-restricted-modules package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  We are in the process of switching ubuntu-drivers to installing linux-
  restricted-modules versions of NVidia drivers when it can, but this
  fails when Ubiquity invokes ubuntu-drivers, like:

  Setting up linux-modules-nvidia-440-5.4.0-25-generic (5.4.0-25.29) ...
   /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-25-generic.postinst: 44: 
3: B
  ad file descriptor
   dpkg: error processing package linux-modules-nvidia-440-5.4.0-25-generic 
(--con
  figure):
installed linux-modules-nvidia-440-5.4.0-25-generic package 
post-installation 
  script subprocess returned error exit status 2
   dpkg: dependency problems prevent configuration of 
linux-modules-nvidia-440-gen
  eric-hwe-20.04:
linux-modules-nvidia-440-generic-hwe-20.04 depends on 
linux-modules-nvidia-440
  -5.4.0-25-generic (= 5.4.0-25.29); however:
 Package linux-modules-nvidia-440-5.4.0-25-generic is not configured yet.
   
   dpkg: error processing package linux-modules-nvidia-440-generic-hwe-20.04 
(--configure):
dependency problems - leaving unconfigured

  It's a problem with the nesting of debconf: Ubiquity itself is using
  debconf, and ubuntu-drivers is installing -nvidia- packages which
  themselves also use debconf, and we don't know how to connect ubuntu-
  drivers use of debconf with the ubiquity one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1874278/+subscriptions

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

Re: [Desktop-packages] [Bug 1861631] Re: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information."

[Dan Watkins]

On Wed, Apr 22, 2020 at 02:53:48PM -, Jonathan Kamens wrote:
> I understand that, but in this particular case we're talking about a
> transition from a deb to a snap, not a snap update.

Aha, apologies, I misread your previous comment.

> Apparently there's special logic in update-manager to handle this, and
> perhaps in do- release-upgrade as well, but I don't think either apt
> nor snap auto- updates will handle this.

There has been special logic in update-manager for other cases before,
but this is not my area of expertise so I'll leave others to comment
further. :)

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

Title:
  "The AppStream system cache was updated, but some components were
  ignored. Refer to the verbose log for more information."

Status in appstream package in Ubuntu:
  Invalid
Status in gnome-software package in Ubuntu:
  In Progress

Bug description:
  `apt-get update` and the nightly `apticron --cron` job are reporting:

  "The AppStream system cache was updated, but some components were
  ignored. Refer to the verbose log for more information."

  This is pretty much meaningless to most people who have no idea what
  AppStream is and what "verbose log" is being referred to. I dug around
  and managed to discover `appstreamcli refresh-cache --force
  --verbose`, whose output is attached.

  I don't know what the "bad" output is or how to fix it. All I know is
  that I hope Focal isn't going to be generating this message when it
  ships, because it isn't going to make sense to most people and most
  people won't know how to fix it and it causes annoying emails from
  apticron every night.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: appstream 0.12.10-1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  2 16:01:24 2020
  InstallationDate: Installed on 2019-08-16 (170 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: appstream
  UpgradeStatus: Upgraded to focal on 2020-01-31 (2 days ago)

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

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

[Desktop-packages] [Bug 1861631] Re: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information."

[Jonathan Kamens]

I understand that, but in this particular case we're talking about a
transition from a deb to a snap, not a snap update. Apparently there's
special logic in update-manager to handle this, and perhaps in do-
release-upgrade as well, but I don't think either apt nor snap auto-
updates will handle this.

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

Title:
  "The AppStream system cache was updated, but some components were
  ignored. Refer to the verbose log for more information."

Status in appstream package in Ubuntu:
  Invalid
Status in gnome-software package in Ubuntu:
  In Progress

Bug description:
  `apt-get update` and the nightly `apticron --cron` job are reporting:

  "The AppStream system cache was updated, but some components were
  ignored. Refer to the verbose log for more information."

  This is pretty much meaningless to most people who have no idea what
  AppStream is and what "verbose log" is being referred to. I dug around
  and managed to discover `appstreamcli refresh-cache --force
  --verbose`, whose output is attached.

  I don't know what the "bad" output is or how to fix it. All I know is
  that I hope Focal isn't going to be generating this message when it
  ships, because it isn't going to make sense to most people and most
  people won't know how to fix it and it causes annoying emails from
  apticron every night.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: appstream 0.12.10-1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  2 16:01:24 2020
  InstallationDate: Installed on 2019-08-16 (170 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: appstream
  UpgradeStatus: Upgraded to focal on 2020-01-31 (2 days ago)

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

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

Re: [Desktop-packages] [Bug 1861631] Re: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information."

[Dan Watkins]

On Wed, Apr 22, 2020 at 10:24:41AM -, Jonathan Kamens wrote:
> I'm a bit concerned about that, though, because the reason why I didn't
> get that update is because I pretty much exclusively use apt to do my
> updates, and apparently that's no longer sufficient to get all the
> updates needed on an Ubuntu system. I don't want to have to run the
> graphical update-manager to do updates. I know this is mostly off-topic
> here, but I don't suppose anyone knows whether there is a way to do the
> equivalent of what update-manager does, but from the command line?

Snaps are updated ("refreshed" in snap terms) automatically by snapd,
independent of the other update mechanisms for the system.  If you run
`snap changes` after a system (with snaps installed, of course) has been
up for a few hours, you should see entries like:

ID   Status  Spawn   Ready   Summary
263  Doneyesterday at 17:53 EDT  yesterday at 17:53 EDT  Auto-refresh snap 
"gtk-common-themes"
264  Donetoday at 03:03 EDT  today at 03:04 EDT  Auto-refresh snap 
"lxd"

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

Title:
  "The AppStream system cache was updated, but some components were
  ignored. Refer to the verbose log for more information."

Status in appstream package in Ubuntu:
  Invalid
Status in gnome-software package in Ubuntu:
  In Progress

Bug description:
  `apt-get update` and the nightly `apticron --cron` job are reporting:

  "The AppStream system cache was updated, but some components were
  ignored. Refer to the verbose log for more information."

  This is pretty much meaningless to most people who have no idea what
  AppStream is and what "verbose log" is being referred to. I dug around
  and managed to discover `appstreamcli refresh-cache --force
  --verbose`, whose output is attached.

  I don't know what the "bad" output is or how to fix it. All I know is
  that I hope Focal isn't going to be generating this message when it
  ships, because it isn't going to make sense to most people and most
  people won't know how to fix it and it causes annoying emails from
  apticron every night.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: appstream 0.12.10-1
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb  2 16:01:24 2020
  InstallationDate: Installed on 2019-08-16 (170 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: appstream
  UpgradeStatus: Upgraded to focal on 2020-01-31 (2 days ago)

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

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

[Desktop-packages] [Bug 1874091] Re: ubuntu-release-upgrader should use ubuntu-drivers and migrate people from nvidia-dkms to l-r-m

[Brian Murray]

** Tags added: rls-ff-incoming

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

Title:
  ubuntu-release-upgrader should use ubuntu-drivers and migrate people
  from nvidia-dkms to l-r-m

Status in ubuntu-drivers-common package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  ubuntu-release-upgrader should use ubuntu-drivers and migrate people
  from nvidia-dkms to l-r-m.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1874091/+subscriptions

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

[Desktop-packages] [Bug 1868117] Re: Adapt chromium user agent to avoid "not supported browser"

[Olivier Tilloy]

I know this isn't an out-of-the-box solution for regular users, but I'll
mention it for the sake of completeness:
https://chrome.google.com/webstore/detail/user-agent-switcher-
for-c/djflhoibgkdhkhhcedjiklpkjnoahfmg works well for netflix.com.

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

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

Title:
  Adapt chromium user agent to avoid "not supported browser"

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Currently some websites like netflix.com and web.whatsapp.com does not
  recognize chromium Ubuntu as chrome because of the different user
  agent.

  We need to find a way like vivaldi to avoid such problems for casual
  users.

  Current snap chromium UA :

  Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko)
  snap Chromium/80.0.3987.132 Chrome/80.0.3987.132 Safari/537.36

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1868117/+subscriptions

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

[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04

[Jose-Gadelha]

Great Daniel! Thank you for keeping us updated and thanks to all
developers by their valuable bug-fixing work. I look forward to upgrade
my production machine to ubuntu 20.04 .

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

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

Status in LibreOffice:
  Confirmed
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Eoan:
  Triaged
Status in mutter source package in Focal:
  Fix Committed

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

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

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

  There is some discussion of the problem here:

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

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

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

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

  It seems like that could be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions

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

[Desktop-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

[Matěj Valášek]

Is normal that, when is music(sound) play to external speakers and I
connect wired headset,music is still playing into the external speakers
and into the headset?

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

Title:
  External audio device shows up in the sound output options but the
  sound keeps being emitted from the internal laptop speaker, or none at
  all.

Status in gnome-control-center:
  Unknown
Status in PulseAudio:
  New
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  In Progress
Status in gnome-control-center source package in Focal:
  Invalid
Status in pulseaudio source package in Focal:
  In Progress

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

  1. Connect an audio interface. I tried with BT headphones and speakers as 
well as a USB microphone/output.
  2. Make sure it's the one selected as "Output device"
  3. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  4. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  5. Try to switch back to the BT device and click Test
  -> same result as in step 3

  Tested with 2 different BT devices (one headset and one speaker) as
  well as a USB audio interface (Zoom H2N microphone).

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+subscriptions

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

[Desktop-packages] [Bug 1871618] Re: Switching playing youtube video to full-screen mode and to default mode lag on Chromium

[Olivier Tilloy]

Are you in an X11 or Wayland session?

Do you use fractional scaling for high DPI ?

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

Title:
  Switching playing youtube video to full-screen mode and to default
  mode lag on Chromium

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  The switching of a playing youtube video to fullscreen mode and also
  from fullscreen mode to normal mode lags.

  Ubuntu version: 19:10
  Chromium version: 80.0.3987.163 (Official Build) snap (64-bit)

  Steps to reproduce
  1. Launch Chromium and open Youtube.
  2. Select/search for a video and play.
  3. Switch the playing video to full-screen mode and back to normal view.

  When playing a video using chromium the switch to full-screen mode and
  back is expected to be smooth but instead, the switching is laggy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1871618/+subscriptions

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

[Desktop-packages] [Bug 1616650] Re: snap refresh while command is running may cause issues

[Olivier Tilloy]

Zygmunt mentioned to me on IRC a few days ago that he is working on
snapctl APIs for checking and getting information about updates, which
he hopes will be available in a few weeks' time.

This would allow snaps such as chromium to integrate nicely with
available updates and prompt the user *before* they are automatically
installed.

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

Title:
  snap refresh while command is running may cause issues

Status in snapd:
  In Progress
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  In testing a desktop snap that saves state in $HOME on close, I
  noticed that if I snap refresh the snap while the command is running
  that it will try to save its state to the previous snap version's data
  directory. For the snap I was testing (a browser), this resulted in a
  very poor user experience (the browser on restart complained about an
  improper shutdown).

  What is happening is that:
  1. on launch the snap's HOME is set to SNAP_USER_DATA, which is something 
like /home/user/snap/foo/x1. The security policy correctly allows writes to 
SNAP_USER_DATA
  2. on snap refresh to 'x2', the security policy for the snap is updated for 
the running process such that /home/user/snap/foo/x1 is readonly and 
/home/user/snap/foo/x2 is read/write
  3. the command in '1's environment is not changed and HOME (as well as 
SNAP_USER_DATA and SNAP_DATA) are all still using 'x1' in the path
  4. the command tries to shutdown gracefully and save state to the 'x1' HOME 
and security policy blocks it

  Snappy's design for rollbacks relies on the previous SNAP_DATA and
  SNAP_USER_DATA directories not being writable and IMHO we should not
  change the policy to make other snap version's data dirs writable.

  The design of the snappy state engine ensures (among other things)
  that there is only ever one security policy in place for the snap. In
  snappy 15.04 this problem was (intentionally) avoided because we used
  snap security policy that was versioned such that the new policy would
  not apply until the next app invocation.

  Gustavo and Zygmunt, you both advocated strongly for only one version
  of the policy on disk and loaded in the kernel and I recall bringing
  up this type of bug as a counter-argument, and if IIRC for daemons we
  said that snapd could simply restart them (makes perfect sense). Have
  you thought of the mechanism for restarting non-daemons?

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

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

[Desktop-packages] [Bug 1874262] [NEW] User session does not start: xkbcomp "Internal error: Could not resolve keysym Invalid"

[El jinete sin cabeza]

Public bug reported:

https://gitlab.gnome.org/GNOME/gdm/-/issues/593

---

Today I tried to log into my ubuntu session with my personal account
through Xorg and Xwayland. And I couldn't, I had to install lightdm and
to be able to enter.

In my experience, I found this message ($journalctl):
Apr 22 09:06:44 romanescu gnome-shell [3651]: The XKEYBOARD keymap compiler 
(xkbcomp) reports:
Apr 22 09:06:44 romanescu gnome-shell [3651]:> Warning: Unsupported maximum 
keycode 569, clipping.
Apr 22 09:06:44 romanescu gnome-shell [3651]:> X11 cannot support keycodes 
above 255.
Apr 22 09:06:44 romanescu gnome-shell [3651]:> Internal error: Could not 
resolve keysym Invalid
Apr 22 09:06:44 romanescu gnome-shell [3651]: Errors from xkbcomp are not fatal 
to the X server

Attached log of the attempt to log in.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
Uname: Linux 5.6.6-050606-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 22 09:54:26 2020
InstallationDate: Installed on 2018-12-02 (506 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "gdm.log"
   https://bugs.launchpad.net/bugs/1874262/+attachment/5357963/+files/gdm.log

** Summary changed:

- User session does not start "Internal error: Could not resolve keysym Invalid"
+ User session does not start: xkbcomp "Internal error: Could not resolve 
keysym Invalid"

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

Title:
  User session does not start: xkbcomp "Internal error: Could not
  resolve keysym Invalid"

Status in gdm3 package in Ubuntu:
  New

Bug description:
  https://gitlab.gnome.org/GNOME/gdm/-/issues/593

  ---

  Today I tried to log into my ubuntu session with my personal account
  through Xorg and Xwayland. And I couldn't, I had to install lightdm
  and to be able to enter.

  In my experience, I found this message ($journalctl):
  Apr 22 09:06:44 romanescu gnome-shell [3651]: The XKEYBOARD keymap compiler 
(xkbcomp) reports:
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> Warning: Unsupported maximum 
keycode 569, clipping.
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> X11 cannot support keycodes 
above 255.
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> Internal error: Could not 
resolve keysym Invalid
  Apr 22 09:06:44 romanescu gnome-shell [3651]: Errors from xkbcomp are not 
fatal to the X server

  Attached log of the attempt to log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  Uname: Linux 5.6.6-050606-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 22 09:54:26 2020
  InstallationDate: Installed on 2018-12-02 (506 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1863608] Re: version 80 does not start using remote display (X11)

[Olivier Tilloy]

Good finding! Sébastien, Benjamin, can you try the suggested workaround
and let us know whether it resolves the problem for you?

Could you also test chromium-browser 81.0.4044.113-0ubuntu0.16.04.1 from
the stage PPA at https://launchpad.net/~canonical-chromium-
builds/+archive/ubuntu/stage ? I do not recommend keeping that PPA
enabled, you should use it only for the purpose of testing this specific
version, and then disable it again.

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

Title:
  version 80 does not start using remote display (X11)

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  chromium-browser version 80.0.3987.87-0ubuntu0.16.04.1_amd64 does not
  work when using remote display; the browser window is a solid pink
  area without any menu (see picture).

  Same with the (existing?) command line option "--disable-gpu"

  Downgrading to 
  chromium-browser_79.0.3945.130-0ubuntu0.16.04.1_amd64.deb
  chromium-browser-l10n_79.0.3945.130-0ubuntu0.16.04.1_all.deb
  chromium-codecs-ffmpeg-extra_79.0.3945.130-0ubuntu0.16.04.1_amd64.deb
  resolve the issue.

  Description: Ubuntu 16.04.6 LTS
  All packages are up to date on 2020-02-17 on xenial, xenial-updates and 
xenial-security

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1863608/+subscriptions

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

[Desktop-packages] [Bug 1871009] Re: Firefox doesn't restart after update

[Olivier Tilloy]

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

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

Title:
  Firefox doesn't restart after update

Status in firefox package in Ubuntu:
  New

Bug description:
  After upgrading to firefox amd64 74.0.1+build1-0ubuntu0.18.04.1 (using
  apt-get), a message appeared in the running Firefox session: 'Firefox
  needs to be restarted' (as usual, nothing wrong with that). After
  clicking ok (or 'do it now' or what the exact message was), Firefox
  terminates.

  Expected behaviour: Firefox actually restarts

  Experienced behaviour: Nothing seemed to happen. Firefox terminated
  but never came back. (Starting Firefox again by hand worked
  flawlessly.)

  I have no profiles defined. I don't usually pass any options when
  starting Firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 74.0.1+build1-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fab3616 F pulseaudio
   /dev/snd/controlC1:  fab3616 F pulseaudio
  BrokenPermissions:
   saved-telemetry-pings/a1103722-309c-47da-b9da-2bc9411237b9 (0o600, wrong 
owner)
   saved-telemetry-pings/e1cac187-9dd1-48b9-bb99-8c67374c7212 (0o600, wrong 
owner)
   saved-telemetry-pings/fbf7331c-39a9-4539-97fa-280e7d343563 (0o600, wrong 
owner)
  BuildID: 20200403064753
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  6 03:13:58 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 2015-04-27 (1805 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IpRoute:
   default via 192.168.23.1 dev eth0 proto dhcp metric 100 
   10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 
   169.254.0.0/16 dev eth0 scope link metric 1000 
   192.168.23.0/24 dev eth0 proto kernel scope link src 192.168.23.136 metric 
100
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-f8832267-2764-4f52-b9df-136771180712
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:732
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=74.0.1/20200403064753 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-f8832267-2764-4f52-b9df-136771180712
   bp-f03b7d3e-1a66-441d-be5d-cedc11180201
   bp-610fb53c-4664-4692-8e37-62c501180107
   bp-708689c3-ba2d-427e-a43b-605df2141112
   bp-b2e12bb9-63b8-494d-9390-f5d722140521
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to bionic on 2018-08-18 (596 days ago)
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-UD3P
  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.:bvrF1:bd08/06/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1873989] Re: Please remove wallpaper from Ubuntu

[Brian Murray]

** No longer affects: ubuntu-meta (Ubuntu)

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

Title:
  Please remove wallpaper from Ubuntu

Status in wallpaper package in Ubuntu:
  Fix Released

Bug description:
  Ancient Ubuntu-only package with no rdeps that FTBFS on rebuild. No
  new upstream release since 2002 (https://www.cgarbs.de/stuff.en.html).
  Appears to just check if a given image(s) can be used as wallpaper -
  doesn't seem to merit inclusion as a package to me (the Bash script is
  available on the developer's site if people want it).

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

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

[Desktop-packages] [Bug 1872390] Re: 193% CPU usage while using webex with chromium

[Olivier Tilloy]

I assume you mean Webex Meetings? I'm not able to create a test meeting
here to confirm the problem, but I suppose this might have to do with
chromium not enabling hardware-accelerated video decoding on linux. Can
you by any chance test this with the Chrome deb package
(https://www.google.com/chrome/) and confirm whether it is similarly
affected?

** Changed in: chromium-browser (Ubuntu)
   Status: New => 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/1872390

Title:
  193% CPU usage while using webex with chromium

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  193% CPU usage while using webex with chromium. The process seems
  associated with audio. When the process was killed. The voice was
  muted.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 80.0.3987.163-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEaeIgAQEBASAbAQOAKxh46tr1pFVSnycOUFS/7gCBwAEBAQEBAQEBAQEBAQEBZiFWqlEAHjBGjzMAsuwQAAAe/QAyTB5TDgAKICAgICAg/ABWWDIwNwogICAgICAg/wBIOExNUVMwMTg1ODUKAbQCAxthIwkHB4MBAABnAwwAIACALUOQhALiAA+MCtCKIOAtEBA+lgCgWgAAKQ==
   modes: 1366x768 1920x1080 1920x1080 1280x720 1280x720 1280x720 1024x768 
1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x480 720x480 
720x480 640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGr+1hAAAaAQSlIhN4Alklk1hZkykmUFQBAQEBAQEBAQEBAQEBAQEBeDeAtHA4LkBsMKoAWMEQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTU2SEFOMDYuMSAKANo=
   modes: 1920x1080
  Date: Mon Apr 13 11:01:39 2020
  Desktop-Session:
   'gnome'
   '/etc/xdg/xdg-gnome:/etc/xdg'
   '/usr/share/gnome:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2018-04-29 (714 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  Load-Avg-1min: 6.54
  Load-Processes-Running-Percent:   0.3%
  MachineType: ASUSTeK COMPUTER INC. FX503VD
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=8d5334b6-ef1c-42d3-880c-f5d4c937cba2 ro quiet splash 
tpm_tis.interrupts=0 acpi_osi=Linux i915.preliminary_hw_support=1 idle=nomwait 
mds=full,nosmt quiet splash tpm_tis.interrupts=0 acpi_osi=Linux 
acpi_backlight=vendor i915.preliminary_hw_support=1 idle=nomwait mds=full,nosmt 
vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to bionic on 2019-12-20 (114 days ago)
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX503VD.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX503VD
  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.:bvrFX503VD.308:bd04/29/2019:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming
  dmi.product.name: FX503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1872390/+subscriptions

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

[Desktop-packages] [Bug 1868117] Re: Adapt chromium user agent to avoid "not supported browser"

[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/1868117

Title:
  Adapt chromium user agent to avoid "not supported browser"

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Currently some websites like netflix.com and web.whatsapp.com does not
  recognize chromium Ubuntu as chrome because of the different user
  agent.

  We need to find a way like vivaldi to avoid such problems for casual
  users.

  Current snap chromium UA :

  Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko)
  snap Chromium/80.0.3987.132 Chrome/80.0.3987.132 Safari/537.36

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1868117/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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]

[Kai-Heng Feng]

This requires another system to use SSH client to connect to the
affected system.

However, that's another bug so I'll just enable those configs for now.

-- 
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 1872146] Re: Audio on Headphones stopped working

[Shaun]

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

Still seems to be the same.

I booted from a Manjaro USB Pendrive.
The sounds works then on all devices.

Back in Kubuntu 20.04 only normal speakers works and Bluetooth HEadsets.

Any audio via my Headphone Jack does not.

Any info I can get.

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

Title:
  Audio on Headphones stopped working

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Audio via my headphones worked yesterday, Today no such luck.

  When I plug in my headphone, Plasma picks it up but no sound.

  Bluetooth headset still works.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Fri Apr 10 23:03:09 2020
  InstallationDate: Installed on 2020-04-05 (5 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200404)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1874049] Re: Gnome-shell block

[Emanuele]

I reproduced it without extensions, the cause that triggers the bug seems to be 
the "gnome-screenshot" tool.
It is easy to readjust.
I created a video on how to reproduce the bug.
Hope it helps.
https://www.youtube.com/watch?v=gBQKVUiKbFs

As you can see from the video, once the bug shows up, the mouse can be
clicked on the windows, but not on the iGNOME shell: menu, dock etc ...

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

Title:
  Gnome-shell block

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have gnome-shell blocked, when I click on any part of the shell: dock, menu 
etc ... nothing happens. I can only switch between windows with alt + tab.
  This is not the first time it happens, it has done so by replicating these 
steps: Virtual manager with OS started, taken the GNOME screenshot tool on 
Ubuntu (host), I select the screenshot (select area to be captured) I select a 
part of the screen on Virtual Manager, at this point the whole shell freezes, 
becomes non-clickable.

  I hope the explanation is understandable and helpful to improve
  Ubuntu. Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 21 12:53:28 2020
  DisplayManager: gdm3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  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/1874049/+subscriptions

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

[Desktop-packages] [Bug 1824907] Re: Support graphical applications out of the box in WSL

[Francis Ginther]

** Tags added: id-5e8608f0e6e6395477bfb0a1

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

Title:
  Support graphical applications out of the box in WSL

Status in ubuntu-desktop-lite:
  New
Status in Ubuntu WSL:
  Opinion
Status in X.Org X server:
  New
Status in wslu package in Ubuntu:
  New

Bug description:
  Please add support for opening up application windows in the
  foreground on WSL (Windows Subsystem for Linux) systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-lite/+bug/1824907/+subscriptions

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

[Desktop-packages] [Bug 1874247] [NEW] Don't work wired connection regression focal

[Igor Zubarev]

Public bug reported:

After upgrade to focal I can't connect to wired network. It was ok in
19.10 before

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 22 15:44:52 2020
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 192.168.1.254 dev wlp7s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp7s0 scope link metric 1000 
 192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.67 metric 600
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  Don't work wired connection regression focal

Status in network-manager package in Ubuntu:
  New

Bug description:
  After upgrade to focal I can't connect to wired network. It was ok in
  19.10 before

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 22 15:44:52 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.254 dev wlp7s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp7s0 scope link metric 1000 
   192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.67 metric 600
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1874247/+subscriptions

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

[Desktop-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Francis Ginther]

** Tags added: id-5e988df7fb344884f67bc04f

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Incomplete
Status in gnome-shell source package in Focal:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log file.

  
  It seems like some internal service broke and everything that followed was a 
secondary issue to that:
  Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ...
  Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting.
  Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel ModemManager[1308]:   Caught signal, 
shutting down...
  Apr 08 06:09:19 Keschdeichel systemd[1]: switcheroo-control.service: 
Unexpected error response from 

[Desktop-packages] [Bug 1869734] Re: openjade segfaults on arm (due to gcc optimization)

[Christian Ehrhardt ]

FYI I got reports this might now also affect ppc64 and amd64.
For ppc64 the confirmation is in that -O0 build fixes it.
So this might have to be re-rolled setting -O0 on all architectures.

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

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

Status in openjade package in Ubuntu:
  Triaged

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

  Myon: only on arm64?
  only there, yes

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1873989] Re: Please remove wallpaper from Ubuntu

[Matthias Klose]

Removing packages from focal:
wallpaper 0.1-1ubuntu1 in focal
wallpaper 0.1-1ubuntu1 in focal amd64
wallpaper 0.1-1ubuntu1 in focal arm64
wallpaper 0.1-1ubuntu1 in focal armhf
wallpaper 0.1-1ubuntu1 in focal i386
wallpaper 0.1-1ubuntu1 in focal ppc64el
wallpaper 0.1-1ubuntu1 in focal riscv64
wallpaper 0.1-1ubuntu1 in focal s390x
Comment: LP: #1873989; remove, no rdeps
1 package successfully removed.


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

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

Title:
  Please remove wallpaper from Ubuntu

Status in ubuntu-meta package in Ubuntu:
  New
Status in wallpaper package in Ubuntu:
  Fix Released

Bug description:
  Ancient Ubuntu-only package with no rdeps that FTBFS on rebuild. No
  new upstream release since 2002 (https://www.cgarbs.de/stuff.en.html).
  Appears to just check if a given image(s) can be used as wallpaper -
  doesn't seem to merit inclusion as a package to me (the Bash script is
  available on the developer's site if people want it).

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

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

[Desktop-packages] [Bug 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland

[Ppaalanen]

On Eoan, I was able to trigger a freeze when trying to set the
DisplayLink output as the only output. I have proposed a fix for that in
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1209 , maybe it
could help here as well?

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

Title:
  display (whole computer?) hangs when I attempt to use DisplayLink with
  Wayland

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  New
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  I am using the DisplayLink driver for Ubuntu provided at
  https://www.displaylink.com/downloads/ubuntu

  DisplayLink is working under Xorg, but when I try to use it under
  Wayland my whole display hangs and I can't even switch to a different
  VT with Ctrl-Alt-F3 so I think maybe the whole computer is hung? Not
  certain.

  [ Test case ]

  - Install DisplayLink drivers
  - Start GNOME Shell in wayland mode
  - Connect to a display-link dock
  - Expect the shell to work properly and be visible in the external device

  [ Regression potential ]

  Wayland session won't work even for standard drm devices

  
  

  I am using the DisplayLink driver for Ubuntu provided at
  https://www.displaylink.com/downloads/ubuntu, which I think is the
  only way to get DisplayLink fully working under Ubuntu? That is,
  DisplayLink didn't work when I installed the evdi-dkms and libevdi0
  Ubuntu packages, and I couldn't find any other packages that might be
  relevant (did I miss something?) so as far as I can tell the only way
  to get everything that's needed is from displaylink.com.

  I'm reporting this issue while logged in under Xorg because I can't
  report it when logged in with my DisplayLink monitors plugged in under
  Wayland, for obvious reasons. :-/

  ProblemType: BugDistroRelease: Ubuntu 19.10
  Package: mutter 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: Wed Nov 20 14:08:21 2019
  InstallationDate: Installed on 2019-09-12 (69 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 
(20190416)SourcePackage: mutter
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (61 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596

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

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

[Desktop-packages] [Bug 1874120] Re: package chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error e

[Olivier Tilloy]

Relevant error from DpkgTerminalLog.txt:

cannot perform the following tasks:
- Fetch and check assertions for snap "chromium" (1105) (Get 
https://api.snapcraft.io/api/v1/snaps/assertions/snap-revision/ZYL60XDZb_GBFQnK1SMhZEsGNEuJ_3IOZ5zHZrT2qjQIX8MdOyGfb-onv15dfbj5?max-format=0:
 net/http: request canceled (Client.Timeout exceeded while awaiting headers))

There was a timeout when installing the chromium snap that replaces
chromium-browser. Could you try reinstalling chromium?

sudo apt install --reinstall chromium-browser

** Changed in: chromium-browser (Ubuntu)
   Status: New => 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/1874120

Title:
  package chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 failed to
  install/upgrade: new chromium-browser package pre-installation script
  subprocess returned error exit status 1

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  error appeared when opening chrome

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 80.0.3987.163-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEaTDjAQEBAQkXAQOAMBt47umEpVVImyYSUFQBAQEBAQEBAQEBAQEBAQEBAjqAGHE4LUBYLEUA3w0RAAAe/QAwTBhkCgAKICAgICAg/ABFVDIyMjFJCiAgICAg/wBBU1VTMjAxMzAzMDEKAEI=
   modes: 1920x1080
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-VGA-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Tue Apr 21 23:33:33 2020
  Desktop-Session:
   'None'
   'None'
   'None'
  Env:
   'None'
   'None'
  ErrorMessage: new chromium-browser package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2015-03-28 (1851 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Load-Avg-1min: 3.38
  Load-Processes-Running-Percent:   0.2%
  MachineType: ASUSTeK COMPUTER INC. ET2221I-B85
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic 
root=UUID=e54296a0-874c-412b-9fc6-092c89bdfa74 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  SourcePackage: chromium-browser
  Title: package chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 failed to 
install/upgrade: new chromium-browser package pre-installation script 
subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-04-21 (0 days ago)
  dmi.bios.date: 11/05/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: ET2221I-B85
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0503:bd11/05/2013:svnASUSTeKCOMPUTERINC.:pnET2221I-B85:pvr0503:rvnASUSTeKCOMPUTERINC.:rnET2221I-B85:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: All-In-One
  dmi.product.name: ET2221I-B85
  dmi.product.version: 0503
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874120/+subscriptions

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

[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding

[Olivier Tilloy]

Thanks for the testing and feedback Matt, much appreciated!

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

Title:
  [snap] vaapi chromium no video hardware decoding

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Libva is no longer working for snap installed chromium 72.0.3626.109
  (Official Build) snap (64-bit)

  I followed this instruction
  sudo snap install --channel=candidate/vaapi chromium

  My amdgpu can use libva

  `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileHEVCMain   :   VAEntrypointVLD
VAProfileHEVCMain10 :   VAEntrypointVLD
VAProfileJPEGBaseline   :   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions

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