date:20200929

** Summary changed:

- Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing wide 
band speech support (Bluetooth A2DP codecs ).
+ Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing wide 
band speech support (Bluetooth A2DP codecs).

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

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

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  In Progress
Status in Arch Linux:
  New

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

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

That's probably more relevant to bug 1838151 than this one.

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

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

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

[Desktop-packages] [Bug 1897681] [NEW] [Satellite C55-A, Intel Valleyview2 HDMI, Digital Out, HDMI] Playback problem

2020-09-29 Thread philip turner

Public bug reported:

There is an echo and gaps in the sound when playing you tube either with
firefox or chrome.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  philip 1327 F pulseaudio
 /dev/snd/pcmC0D0c:   philip 1327 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 29 19:55:29 2020
InstallationDate: Installed on 2020-09-28 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_NZ:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Digital Out, HDMI
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_SpeakerTestPulseStderr:
 W r i t e   e r r o r :   - 3 2 , B r o k e n   p i p e 
  W r i t e   e r r o r :   - 3 2 , B r o k e n   p i p e 
  W r i t e   e r r o r :   - 3 2 , B r o k e n   p i p e 
  W r i t e   e r r o r :   - 3 2 , B r o k e n   p i p e
Symptom_Type: None of the above
Title: [Satellite C55-A, Intel Valleyview2 HDMI, Digital Out, HDMI] Playback 
problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/03/2013
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.10
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: MP
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.10:bd12/03/2013:svnTOSHIBA:pnSatelliteC55-A:pvrPSCJEU-00K018:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.family: Durban 10BT
dmi.product.name: Satellite C55-A
dmi.product.sku: PSCJEU-00K018
dmi.product.version: PSCJEU-00K018
dmi.sys.vendor: TOSHIBA

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1897681

Title:
  [Satellite C55-A, Intel Valleyview2 HDMI, Digital Out, HDMI] Playback
  problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  There is an echo and gaps in the sound when playing you tube either
  with firefox or chrome.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philip 1327 F pulseaudio
   /dev/snd/pcmC0D0c:   philip 1327 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 19:55:29 2020
  InstallationDate: Installed on 2020-09-28 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_SpeakerTestPulseStderr:
   W r i t e   e r r o r :   - 3 2 , B r o k e n   p i p e 
W r i t e   e r r o r :   - 3 2 , B r o k e n   p i p e 
W r i t e   e r r o r :   - 3 2 , B r o k e n   p i p e 
W r i t e   e r r o r :   - 3 2 , B r o k e n   p i p e
  Symptom_Type: None of the above
  Title: [Satellite C55-A, Intel Valleyview2 HDMI, Digital Out, HDMI] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2013
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.10
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.10:bd12/03/2013:svnTOSHIBA:pnSatelliteC55-A:pvrPSCJEU-00K018:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Durban 10BT
  dmi.product.name: Satellite C55-A
  dmi.product.sku: PSCJEU-00K018
  dmi.product.version: PSCJEU-00K018
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launc

[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.

Sujit, your comments #62 and #64 suggest you are experiencing a
different bug. Mostly because deleting ~/.config/pulse should eliminate
this bug. If it doesn't then that's a different issue. Please open a new
bug.

--
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/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 PulseAudio:
Fix Released
Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Focal:
Fix Committed
Status in pulseaudio source package in Groovy:
Fix Released

Bug description:
[Impact]

Selected audio output device in Settings is ignored after upgrading to
Ubuntu 20.04.

[Test Case]

Start with an older version of Ubuntu like 19.04 or 19.10 and upgrade
to 20.04. When done, attempt to connect a Bluetooth or USB audio
device and use it via Settings.

[Regression Potential]

Unknown/low. The fix is from upstream and has already been released to
Ubuntu 20.10 without any problems. Only worth noting it works by
detecting and removing audio configurations made via older versions of
PulseAudio. So upon upgrading some old settings may be reset to
defaults, but the idea is that's less bad than audio devices being
unusable (this bug).

[Original Bug Report]

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/pulseaudio/+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 1878105] Re: [nvidia] Xorg crashes in ?? from FreeCursor() from ChangeWindowAttributes()

2020-09-29 Thread SR

I must add to the previous comment : when I am in UHD resolution, with
200% zoom.

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

Title:
  [nvidia] Xorg crashes in ?? from FreeCursor() from
  ChangeWindowAttributes()

Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Crash is caused when visiting websites that attempt to customize the
  cursor layout. (Tested with Firefox 76.0 (64-bit))

  The website on which the crash first occurred was the following:
  https://www.yellibeanz.com/
  the crash is triggered after moving the cursor around. 

  To test the hypothesis of the cursor causing the bug I also tested the
  following website with identical outcome:

  http://www.flockofsiegel.tv/

  I am sure that one can find more examples here:

  https://onextrapixel.com/10-websites-that-replace-mouse-cursors-for-a
  -better-cause/

  lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  apt-cache policy xorg
  xorg:
Installed: 1:7.7+19ubuntu14
Candidate: 1:7.7+19ubuntu14
Version table:
   *** 1:7.7+19ubuntu14 500
  500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-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  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 11 23:58:41 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.4.0-28-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Mobile) [1043:1fc0]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:1fc0]
  InstallationDate: Installed on 2020-05-03 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 13d3:56a2 IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X580GD_N580GD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=04dedfb2-c5a9-4447-af72-16999d76fce2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X580GD.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X580GD
  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.:bvrX580GD.309:bd10/18/2018:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX580GD_N580GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX580GD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X580GD_N580GD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  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.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git202002

[Desktop-packages] [Bug 1884850] Re: Xorg server uses unacceptably large amounts of memory (and keep growing) when LibreOffice is running

** Summary changed:

- Xorg server uses unacceptably large amounts of memory (and keep growing)
+ Xorg server uses unacceptably large amounts of memory (and keep growing) when 
LibreOffice is running

** No longer affects: xorg-server (Ubuntu)

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

Title:
  Xorg server uses unacceptably large amounts of memory (and keep
  growing) when LibreOffice is running

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Description: Xorg server uses unacceptably large amounts of memory
  (and keep growing)

  Ever since I upgraded to Ubuntu 20.04 (with fresh install) on my
  laptop (Lenovo T450s, Intel Core i5-5200U, Intel HD5500 graphics), I
  have been troubled by the way Xorg process uses memory.

  Here is an example of memory usage of Xorg as a function of time. I
  rebooted the laptop on June 17:

  Xorg-usage-20200617a.txt:root1224  1.9  0.8 948408 98848 tty7 
Rsl+ 10:38   0:05  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200617b.txt:root1224  2.2  0.8 978264 105180 tty7
Ssl+ 10:38   0:22  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200618a.txt:root1224  0.3  1.3 1143064 162584 tty7   
Ssl+ Jun17   3:15  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200619a.txt:root1224  0.3  2.9 1432232 360700 tty7   
Ssl+ Jun17  12:30  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200619b.txt:root1224  0.3  2.7 1313120 338656 tty7   
Ssl+ Jun17  12:39  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  Xorg-usage-20200623a.txt:root1224  0.3  6.0 1944364 738596 tty7   
Ssl+ Jun17  31:55  \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch

  The filename indicates the date the "ps fuxa" command was run.
  Contrast this against the memory usage of another Xorg process run for XPRA:

  Xorg-usage-20200617b.txt:wirawan 4452  2.4  2.0 1106920 244984 ?  
Ssl  10:46   0:12  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
  Xorg-usage-20200618a.txt:wirawan 4452  0.2  2.0 1108572 246616 ?  
Ssl  Jun17   2:25  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
  Xorg-usage-20200619a.txt:wirawan 4452  0.2  2.0 1112460 249516 ?  
Ssl  Jun17   8:34  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
  Xorg-usage-20200619b.txt:wirawan 4452  0.2  2.0 1112964 250020 ?  
Ssl  Jun17   8:40  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100
  Xorg-usage-20200623a.txt:wirawan 4452  0.1  2.0 1113092 250544 ?  
Ssl  Jun17  11:22  \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch 
-nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth 
/home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir 
/run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100

  My desktop usage pattern:

  * MATE desktop
  * 4-desktop setting (standard default MATE when shipped)
  * GNUCASH
  * about 3 windows of terminal (each about 5-10 tabs)
  * XPRA running Firefox web browser (to isolate web browser pixmap memory 
usage, if that was the culprit)
  * LibreOffice (several windows open at any time)
  * using "redshift" to change the desktop color to red at night

  I have never seen this before using Ubuntu 20.04 on this machine.
  Before, when I was running Debian 8, I could run this machine for months 
literally without Xorg memory bloating rapidly like this (but then I was using 
xfce instead of MATE).
  I viewed the output of xrestop, the pi

[Desktop-packages] [Bug 1833116] Re: [chtmax98090 on Bay Trail Chromebooks] audio not working, shows "Dummy Output"

2020-09-29 Thread Gabriele Tettamanzi

For Focal Fossa 20.04 and newer releases, check bug 1871306 out:

https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1871306

The bug has been assigned, the priority is now high: we're going to have
it fixed.

Temporary work around: get the missing config UCM2 files from alsa
project github or install alsa-ucm-conf 1.2.3 from Debian testing.

Links

alsa-project github:
https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/chtmax98090
https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/codecs/max98090

debian testing package:
https://packages.debian.org/bullseye/all/alsa-ucm-conf/download

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

Title:
  [chtmax98090 on Bay Trail Chromebooks] audio not working, shows "Dummy
  Output"

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  chtmax98090 intel HD audio device doesn't work out of the box after
  installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on
  audio devices.

  Audio options shows device and it works if I do this:

   git clone https://github.com/plbossart/UCM.git
   cd UCM
   cp -r chtmax98090/ /usr/share/alsa/ucm/
   alsactl store

  It would be great if there were a solution to make it works out of the
  box. The device (Chromebook Acer CB3-111 has it's end of life for
  chromeOS in July-August, so I suppose more people with this device
  will change OS perhaps to Ubuntu).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jaime  1293 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 17 20:32:35 2019
  InstallationDate: Installed on 2019-06-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Desktop-packages] [Bug 1883174] Re: Some desktop icons disappear

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
 Assignee: (unassigned) => Sergio Costas (rastersoft-gmail)

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Some desktop icons disappear

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  In Progress

Bug description:
  OS: Ubuntu 20.04
  GNOME: 3.36.2
  Extension: 3.36.2

  Sometimes, some icons in my Desktop folder just don't appear on the
  desktop. The missing icons aren't invisible, it's like they're not in
  the folder. Clicking on the empty space where they should be does
  nothing. Mousing over the empty space does nothing. See attached
  screenshot. As you can see, there are many missing.

  Not consistently reproducible, but frequent.

  This isn't great info, I know. Let me know what else I can provide.

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

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

[Desktop-packages] [Bug 1892747] Re: [Dell Vostro 3446] Ubuntu hangs while changing display brightness from keyboard shortcut

Bugs like this are model-specific. And since the above link is about a
different model of laptop, this bug is not yet confirmed. It's still
open and valid, so don't worry.

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

Title:
  [Dell Vostro 3446] Ubuntu hangs while changing display brightness from
  keyboard shortcut

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Whenever I change my display's brightness using keyboard shortcuts (For me 
F11 & F12), Ubuntu hangs a little, the brightness is changed immediately, but 
everything (except the mouse) hangs while it is being changed and sometimes for 
quite some time after. There is no problem doing it through the system. 
Changing volume using keyboard shortcuts works perfectly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-22 (3 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  NonfreeKernelModules: nvidia
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1894400] Re: Establishing connection to PulseAudio. Please wait...

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

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

Title:
  Establishing connection to PulseAudio. Please wait...

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Sometimes when i start up firefox in the morning i can't hear any
  audio.  Or sometimes a page that wants to play audio will freeze,
  waiting.  When these happen i'll launch pavucontrol next and it'll say
  "Establishing connection to PulseAudio. Please wait..." and just keep
  waiting.  i look for the pulseaudio process, it's there as usual.
  Even so i just launch an additional pulseaudio process, and then
  pavucontrol is immediately all happy.  Firefox might also immediately
  become all happy, or less often i'll also need to restart firefox
  before i can play audio.

  i usually shut off my computer at night.  Starting it up each morning,
  manifestations as described above might be separated by a couple
  weeks, or might happen a couple times within a week.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.4 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/steelseries-arctis-7-output-mono.conf]
  ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
  Uname: Linux 4.15.0-88-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Sat Sep  5 16:45:50 2020
  ProcEnviron:
   LC_TIME=en_DK.utf8
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PU052
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd04/30/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0PU052:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1893969] Re: Screen corruption and delayed update using onboard Intel video

** No longer affects: mutter (Ubuntu)

** Summary changed:

- Screen corruption and delayed update using onboard Intel video
+ Characters are rendered with a slight border when using custom xrandr scaling

** Changed in: xorg-server (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Characters are rendered with a slight border when using custom xrandr
  scaling

Status in xorg-server package in Ubuntu:
  New

Bug description:
  I frequently get screen corruption or delayed screen updates using
  onboard Intel video (i7-10710U in a Dell XPS 13 7390).  I am attaching
  a screen shot of an example of this in Emacs, where you can see echoes
  of past cursor locations (center right side of screen, the highlighted
  word "boolean").

  A frequent failure is that an application updates its window, but the
  updates do not appear on screen until I take some action to disturb
  the window (move or resize it, change focus, change desktops, etc.),
  after which it cleans itself up.  Small changes (such as selecting
  text) will often clean up the image where the change is made without
  repainting the entire window.

  My display panel is 4K UHD+, and I have attached two external Full HD
  DisplayPort monitors using chaining with 2x2 scale using XrandR.  This
  corruption appears to happen on all three surfaces.  The configuration
  for my desktop is:

  HIX=3840
  HIY=2160
  HI=${HIX}x${HIY}
  xrandr --fb $(($HIX * 3))x$HIY \
 --output eDP-1 --auto --panning ${HI}+$(($HIX * 2))+0 \
 --output DP-2-8 --auto --panning ${HI}+$HIX+0 \
 --scale-from $HI --left-of eDP-1 --scale 2x2 \
 --output DP-2-1 --auto --panning $HI+0+0 \
 --scale-from $HI --left-of DP-2-8 --scale 2x2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop:
   
  Date: Wed Sep  2 11:48:03 2020
  DistUpgraded: 2020-06-21 15:36:52,619 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: v4l2loopback, 0.12.3, 5.4.0-42-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0962]
  MachineType: Dell Inc. XPS 13 7390
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=UUID=aeb9197c-491f-493d-9a7a-7094efd5023c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-06-21 (72 days ago)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0377MH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-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/xorg-server/+bug/1893969/+subscriptions

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

[Desktop-packages] [Bug 1895486] Re: [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock" keyboards

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

** Changed in: xkeyboard-config (Ubuntu)
 Assignee: (unassigned) => Cristiano Nunes (cfgnunes)

** Changed in: xkeyboard-config (Ubuntu)
   Status: New => Fix Committed

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

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

Title:
  [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll
  Lock" keyboards

Status in GNOME Shell:
  Unknown
Status in xkeyboard-config package in Ubuntu:
  Fix Committed

Bug description:
  I use Ubuntu 20.04.1.

  After some use, I noticed a delay when using keyboard media controls
  (for example: increase volume audio).

  The first time I push these key Gnome hangs for a short time before
  display the action on the screen.

  (This problem is still happening in Ubuntu 18.04 too. Even worse some
  times, the system crashes when using media keys.)

  For some reason, my Gnome freezes when using Fn keys, or when I try to
  use two keyboards. A friend of mine pointed to me that it occurs when
  switching to a keyboard layout that has Scroll Lock enabled, so I
  disabled it in the X11 keyboard layout file for my language, and it
  solved the problem.

  
  A workaround to solve the problem is:

  1) Opened the keyboard layout file for my language, in my case:

  sudo nano /usr/share/X11/xkb/symbols/br

  2) Commented the line:

  modifier_map Mod3 { Scroll_Lock };

  3) Logged out and logged in again or run command setxkbmap.

  These steps are specific for the Brazilian Portuguese ABNT2 Layout and
  may not work for other layouts, but it can help you find a similar
  solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: x11-xkb-utils 7.7+5
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-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  440.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 13 21:52:03 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Subsystem: Dell UHD Graphics 630 (Desktop) [1028:0859]
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Dell GP107 [GeForce GTX 1050 Ti] [1028:3512]
  InstallationDate: Installed on 2020-08-15 (29 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  MachineType: Dell Inc. XPS 8930
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=706721d5-f527-41fe-98ca-96706a36bb42 ro quiet splash
  SourcePackage: x11-xkb-utils
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.15
  dmi.board.name: 0T88YD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.15:bd07/01/2020:svnDellInc.:pnXPS8930:pvr1.1.15:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.sku: 0859
  dmi.product.version: 1.1.15
  dmi.sys.vendor: Dell Inc.
  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-08-15T17:44:36
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  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.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@li

[Desktop-packages] [Bug 1894666] Re: Gnome high CPU preventing login after screen lock

Do you mean the 'Ubuntu Dock' extension or some other dock?

Either way, I can't think of any existing bug for this. It wouldn't be
bug 1849142.

** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
ubuntu-dock (Ubuntu)

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

Title:
  Gnome high CPU preventing login after screen lock

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

Bug description:
  I have configured my PC to lock the screen automatically after a
  period of inactivity. Often when I come back to my PC I'm unable to
  login due to gnome shell running at 100% CPU (according to htop).

  The only way I can log in is to SSH to the machine from another PC and
  kill the gnome shell task running at 100%

  Other than noting this only happens when I try and unlock the screen I
  haven't been able to find any pattern which can explain this
  behaviour. I've never had problems with gnome shell while using the
  PC.

  Some info about the machine Ubuntu 20.04, Nvidia drivers, 4k monitors

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55
  Uname: Linux 5.4.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  7 22:01:37 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-09-05 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
  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-extension-ubuntu-dock/+bug/1894666/+subscriptions

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

[Desktop-packages] [Bug 1897681] Re: [Satellite C55-A, Intel Valleyview2 HDMI, Digital Out, HDMI] Playback problem

2020-09-29 Thread philip turner

stuttering on audio also ocurs with built in speakers of laptop

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

Title:
  [Satellite C55-A, Intel Valleyview2 HDMI, Digital Out, HDMI] Playback
  problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  There is an echo and gaps in the sound when playing you tube either
  with firefox or chrome.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philip 1327 F pulseaudio
   /dev/snd/pcmC0D0c:   philip 1327 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 19:55:29 2020
  InstallationDate: Installed on 2020-09-28 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_SpeakerTestPulseStderr:
   W r i t e   e r r o r :   - 3 2 , B r o k e n   p i p e 
W r i t e   e r r o r :   - 3 2 , B r o k e n   p i p e 
W r i t e   e r r o r :   - 3 2 , B r o k e n   p i p e 
W r i t e   e r r o r :   - 3 2 , B r o k e n   p i p e
  Symptom_Type: None of the above
  Title: [Satellite C55-A, Intel Valleyview2 HDMI, Digital Out, HDMI] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2013
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.10
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.10:bd12/03/2013:svnTOSHIBA:pnSatelliteC55-A:pvrPSCJEU-00K018:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Durban 10BT
  dmi.product.name: Satellite C55-A
  dmi.product.sku: PSCJEU-00K018
  dmi.product.version: PSCJEU-00K018
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 1897690] [NEW] ping: socket: Address family not supported by protocol

2020-09-29 Thread Martin Vysny

Public bug reported:

The ping utility prints this curious error/warning message:

```
ping: socket: Address family not supported by protocol
```

Otherwise seems to be working just fine:

```
> ping 127.0.0.1
ping: socket: Address family not supported by protocol
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.048 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.050 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.043 ms
64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.046 ms
```

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: iputils-ping 3:20200821-2
ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
Uname: Linux 5.8.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu48
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 29 10:42:17 2020
InstallationDate: Installed on 2016-09-05 (1484 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
SourcePackage: iputils
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy wayland-session

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

Title:
  ping: socket: Address family not supported by protocol

Status in iputils package in Ubuntu:
  New

Bug description:
  The ping utility prints this curious error/warning message:

  ```
  ping: socket: Address family not supported by protocol
  ```

  Otherwise seems to be working just fine:

  ```
  > ping 127.0.0.1
  ping: socket: Address family not supported by protocol
  PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
  64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.048 ms
  64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.050 ms
  64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.043 ms
  64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.046 ms
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: iputils-ping 3:20200821-2
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 10:42:17 2020
  InstallationDate: Installed on 2016-09-05 (1484 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: iputils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2020-09-29 Thread SirJuan

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

Same issue here with Sony Sony WH-CH510 on a fresh install of Ubuntu
20.04.1 LTS kernel 5.4.0-48-generic (buildd@lcy01-amd64-010)

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

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

[Desktop-packages] [Bug 1896627] Re: Windows flicker when being reized with the mouse

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

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

Title:
  Windows flicker when being resized with the mouse (Xorg sessions in
  groovy)

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  When resizing a window with the mouse by dragging the edge or corner,
  the window begins to flicker.  It only flickers when actively being
  resized, and when I stop dragging, it looks normal.  This behavior is
  does not occur on same pc in 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Tue Sep 22 10:21:51 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2231]
  InstallationDate: Installed on 2020-09-22 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 
(20200921)
  MachineType: LENOVO 20FJS0AJ00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=72bd1806-98fb-4fa6-be5b-638dec36ebc9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2016
  dmi.bios.release: 1.13
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET26W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS0AJ00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET26W(1.13):bd10/07/2016:br1.13:efr1.5:svnLENOVO:pn20FJS0AJ00:pvrThinkPadT560:rvnLENOVO:rn20FJS0AJ00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T560
  dmi.product.name: 20FJS0AJ00
  dmi.product.sku: LENOVO_MT_20FJ_BU_Think_FM_ThinkPad T560
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.7-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/mutter/+bug/1896627/+subscriptions

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

[Desktop-packages] [Bug 1897632] Re: Can't see fully Print Dialogue Box in Libre Office

2020-09-29 Thread Dave Goldsbrough

Just spotted
https://bugs.launchpad.net/df-libreoffice/+bug/1883886

Could this be a duplicate?
How exactly do I fix?

** Tags added: a11y libreoffice writer

** Description changed:

  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  
- 
- I am unsure whether the problem I am suffering is related to 
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440
+ I am unsure whether the problem I am suffering is related to
+ https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440
  
  In LibreOffice Version: 6.4.6.2 Build ID: 1:6.4.6-0ubuntu0.20.04.1 when
  I try to print a document I cannot see the bottom part of the print
  dialogue window, making it impossible to print. There is no scroll bar
  to scroll down. The More Options, Cancel and OK boxes are not visible so
  I cannot actually print.
  
  As I have Low Vision I must have Large Text on.
  
  However, if I switch Large Text off hen I can see(just) the  More
  Options, Cancel and OK boxes at the bottom and can then print.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-core 1:6.4.6-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 28 22:56:02 2020
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2020-04-27 (154 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

** Tags added: gnome

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

Title:
  Can't see fully Print Dialogue Box in Libre Office

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  I am unsure whether the problem I am suffering is related to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440

  In LibreOffice Version: 6.4.6.2 Build ID: 1:6.4.6-0ubuntu0.20.04.1
  when I try to print a document I cannot see the bottom part of the
  print dialogue window, making it impossible to print. There is no
  scroll bar to scroll down. The More Options, Cancel and OK boxes are
  not visible so I cannot actually print.

  As I have Low Vision I must have Large Text on.

  However, if I switch Large Text off hen I can see(just) the  More
  Options, Cancel and OK boxes at the bottom and can then print.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-core 1:6.4.6-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 28 22:56:02 2020
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2020-04-27 (154 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1896627] Re: Windows flicker when being reized with the mouse

2020-09-29 Thread 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/1896627

Title:
  Windows flicker when being resized with the mouse (Xorg sessions in
  groovy)

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  When resizing a window with the mouse by dragging the edge or corner,
  the window begins to flicker.  It only flickers when actively being
  resized, and when I stop dragging, it looks normal.  This behavior is
  does not occur on same pc in 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Tue Sep 22 10:21:51 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2231]
  InstallationDate: Installed on 2020-09-22 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 
(20200921)
  MachineType: LENOVO 20FJS0AJ00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=72bd1806-98fb-4fa6-be5b-638dec36ebc9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2016
  dmi.bios.release: 1.13
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET26W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS0AJ00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET26W(1.13):bd10/07/2016:br1.13:efr1.5:svnLENOVO:pn20FJS0AJ00:pvrThinkPadT560:rvnLENOVO:rn20FJS0AJ00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T560
  dmi.product.name: 20FJS0AJ00
  dmi.product.sku: LENOVO_MT_20FJ_BU_Think_FM_ThinkPad T560
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.7-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/mutter/+bug/1896627/+subscriptions

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

[Desktop-packages] [Bug 1896416] Re: screen locking no longer works

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

** This bug has been marked a duplicate of bug 1851992
   Lock screen not locking upon resume (org.gnome.desktop.lockdown 
disable-lock-screen set to true for some reason)

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

Title:
  screen locking no longer works

Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  in the last week, the gnome screen locking functionality stopped
  working. I'm under the impression this is handled by gdm3, but if not,
  please point me at the correct package.

  in any case, now there's no lock icon in the power menu in the top
  right, win-L does nothing, and trying to invoke manually with the
  gnome-screensaver package times out after about a minute with the
  following error:

  $ gnome-screensaver-command -l

  ** (gnome-screensaver-command:212161): WARNING **: 18:46:25.014: unable to 
send message: Timeout was reached
  ** Message: 18:46:25.014: Did not receive a reply from the screensaver.

  
  as well, if I suspend the system, on resume it dumps right back to the 
desktop without a prompt to re-authenticate, so this is a security issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-47.51-lowlatency 5.4.55
  Uname: Linux 5.4.0-47-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 20 18:47:40 2020
  InstallationDate: Installed on 2020-07-15 (67 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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/1896416/+subscriptions

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

[Desktop-packages] [Bug 1896627] Re: Windows flicker when being reized with the mouse

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

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

** Summary changed:

- Windows flicker when being reized with the mouse
+ Windows flicker when being resized with the mouse (Xorg sessions in groovy)

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

Title:
  Windows flicker when being resized with the mouse (Xorg sessions in
  groovy)

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  When resizing a window with the mouse by dragging the edge or corner,
  the window begins to flicker.  It only flickers when actively being
  resized, and when I stop dragging, it looks normal.  This behavior is
  does not occur on same pc in 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Tue Sep 22 10:21:51 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2231]
  InstallationDate: Installed on 2020-09-22 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 
(20200921)
  MachineType: LENOVO 20FJS0AJ00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=72bd1806-98fb-4fa6-be5b-638dec36ebc9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2016
  dmi.bios.release: 1.13
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET26W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS0AJ00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET26W(1.13):bd10/07/2016:br1.13:efr1.5:svnLENOVO:pn20FJS0AJ00:pvrThinkPadT560:rvnLENOVO:rn20FJS0AJ00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T560
  dmi.product.name: 20FJS0AJ00
  dmi.product.sku: LENOVO_MT_20FJ_BU_Think_FM_ThinkPad T560
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.7-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/mutter/+bug/1896627/+subscriptions

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

[Desktop-packages] [Bug 1896654] Re: Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie)

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

** This bug has been marked a duplicate of bug 1896627
   Windows flicker when being reized with the mouse

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

Title:
  Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie)

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When resizing a window with the mouse by dragging the edge or corner,
  the window begins to flicker. It only flickers when actively being
  resized, and when I stop dragging, it looks normal. This behavior is
  does not occur on same pc in 20.04. Sometimes the flickering is black,
  sometimes the flickering makes the wallpaper visible, even when there
  is a window behind the window being resized.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Tue Sep 22 14:48:00 2020
  InstallationDate: Installed on 2020-09-22 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 
(20200921)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1896637] Re: system booting is too slow. Application like chrome, spotify, Libre Office, etc open too slow.

The system booting too slow is different to applications launching too
slow. Which issue would you like this bug to be about?

If you would like the bug to be about the system booting too slow then
please provide a shorter, cleaner boot log by rebooting, logging in and
then immediately running:

  journalctl -b0 > freshboot.txt

and attach the resulting file here.

If you would like the bug to be about apps launching slowly then please
run:

  top

and tell us what processes are using the most CPU.

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

Title:
  system booting is too slow. Application like chrome, spotify, Libre
  Office, etc  open too slow.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This OS(Ubuntu 20.04 LTS) installed in Lenovo v310-15ISK laptop. It
  has 4GB RAM and core i3 6th gen processor. The main issue is booting
  time too slow about 3-4 minutes and all apps take time to open and
  sometimes after long uptime when I poweroff, it freezes for sometime
  then start shut down after 1-2 minutes.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 22 21:07:25 2020
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
  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/1896637/+subscriptions

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

[Desktop-packages] [Bug 1896645] Re: Dual screen window size problem

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

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


** Package changed: xorg (Ubuntu) => qtbase-opensource-src (Ubuntu)

** This bug has been marked a duplicate of bug 1810346
   VLC interface not displayed correctly on external display

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

Title:
  Dual screen window size problem

Status in qtbase-opensource-src package in Ubuntu:
  Incomplete

Bug description:
  Certain programs don't seem to co-operate well with a dual monitor
  setup. If it is of any importance, my setup is a laptop with a TV
  plugged in via HDMI. So far I've found that VLC media player and
  Oracle Virtualbox won't play nicely with two monitors. When both
  monitors are in use, virtualbox crashes before it can open, and vlc
  tends to freeze the entire system, requiring a hard reboot. If I run
  these programs while only one monitor is being used and plug in the
  second one, they'll start misbehaving if moved to the other monitor.
  virtualbox and vlc will both become way too huge to be usable.

  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04

  xorg:
Installed: 1:7.7+19ubuntu7.1
Candidate: 1:7.7+19ubuntu7.1
Version table:
   *** 1:7.7+19ubuntu7.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 22 12:02:21 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:8364]
  InstallationDate: Installed on 2020-02-21 (214 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: HP HP Pavilion Laptop 15-cc0xx
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=da68f1b9-ec5f-4962-8098-08f28713396e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8364
  dmi.board.vendor: HP
  dmi.board.version: 46.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd11/03/2017:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cc0xx
  dmi.product.sku: 1KU17UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1896645/+subscriptions

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

[Desktop-packages] [Bug 1896646] Re: bluetooth no longer installed

bluez has not been updated since April. And regardless, the Bluetooth
hardware detection is a kernel responsibility.

** Summary changed:

- bluetooth no longer installed
+ [ASUS X556UAM] Bluetooth no longer detected

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

** Tags added: regression-update

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

Title:
  [ASUS X556UAM] Bluetooth no longer detected

Status in linux package in Ubuntu:
  New

Bug description:
  22 september 2020 update removed bluetooth capability.  No Bluetooth
  hardware detected by system, cannot turn on or add devices.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65
  Uname: Linux 5.4.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 22 12:53:31 2020
  InstallationDate: Installed on 2019-12-07 (290 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InterestingModules: bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57de Realtek Semiconductor Corp. USB2.0 VGA UVC 
WebCam
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 5: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 
480M
   |__ Port 6: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
   |__ Port 6: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M
  MachineType: ASUSTeK COMPUTER INC. X556UAM
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-49-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X556UAM.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X556UAM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX556UAM.305:bd07/06/2016:svnASUSTeKCOMPUTERINC.:pnX556UAM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UAM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X556UAM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

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

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

[Desktop-packages] [Bug 1896644] Re: Dual screen window size problem

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

** This bug is no longer a duplicate of bug 1896645
   Dual screen window size problem
** This bug has been marked a duplicate of bug 1810346
   VLC interface not displayed correctly on external display

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

Title:
  Dual screen window size problem

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Certain programs don't seem to co-operate well with a dual monitor
  setup. If it is of any importance, my setup is a laptop with a TV
  plugged in via HDMI. So far I've found that VLC media player and
  Oracle Virtualbox won't play nicely with two monitors. When both
  monitors are in use, virtualbox crashes before it can open, and vlc
  tends to freeze the entire system, requiring a hard reboot. If I run
  these programs while only one monitor is being used and plug in the
  second one, they'll start misbehaving if moved to the other monitor.
  virtualbox and vlc will both become way too huge to be usable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 22 12:02:21 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:8364]
  InstallationDate: Installed on 2020-02-21 (214 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: HP HP Pavilion Laptop 15-cc0xx
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=da68f1b9-ec5f-4962-8098-08f28713396e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8364
  dmi.board.vendor: HP
  dmi.board.version: 46.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd11/03/2017:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cc0xx
  dmi.product.sku: 1KU17UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1896774] Re: [ASUS UX430UQ] Headphone output stopped working after perfoming dist-upgrade

** Summary changed:

- Headphone output stopped working after perfoming dist-upgrade
+ [ASUS UX430UQ] Headphone output stopped working after perfoming dist-upgrade

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

Title:
  [ASUS UX430UQ] Headphone output stopped working after perfoming dist-
  upgrade

Status in alsa-driver package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  # What happened:

  - Upgraded packages using: sudo apt-get update && sudo apt-get dist-
  upgrade

  - Following packages were installed:
  pulseaudio-utils:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14
  pulseaudio-module-x11:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14
  pulseaudio-module-bluetooth:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14
  pulseaudio:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14

  - Find the complete update log attached (dpkg.log written to
  update_log_23_09_20.txt)

  # Bug description:

  - Loudspeaker works fine. Inserting headphones is detected correctly
  in sound settings but no physical output is generated on the headphone
  port.


  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-118.119~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-118-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pascal 2210 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep 23 15:32:02 2020
  InstallationDate: Installed on 2018-01-11 (986 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pascal 2210 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [UX430UQ, Realtek ALC295, Black Headphone Out, Left] No sound at all
  UpgradeStatus: Upgraded to xenial on 2018-09-20 (734 days ago)
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UQ.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UQ
  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.:bvrUX430UQ.302:bd07/05/2017:svnASUSTeKCOMPUTERINC.:pnUX430UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX430UQ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1897693] [NEW] Fingerprint enroll progress is NOT displayed for immediate 2nd fingerprint enrollment

Public bug reported:

Fingerprint enroll progress is NOT displayed for immediate 2nd fingerprint 
enrollment with out closing the FP GUI.
2nd finger enrollment: After first swipe of 2nd FP, even though progress is not 
displayed on circle for 2nd fingerprint, it is properly enrolled after 
continuous swipe and later it will be identified, but user will have confusion 
about appearance that is the 2nd finger enrollment is happening or not.

Steps to reproduce:
Enroll 1st FP ==> enrollment progress is shown on circle, after it completes, 
don't close GUI, proceed with 2nd finger enrollment
Enroll the second FP ==> observe that enrollment progress is NOT shown on 
circle, but if we keep on placing finger, after few attempts, finger will be 
enrolled.

verified on two DELL models
model-1: latitude 7300: 2nd fp enrollment progress is shown for 1 or 2 swipes, 
but didn't completed the progress circle.
model-2: latitude 7520: 2nd fp enrollment progress is NOT shown at all

Both cases 2nd FP enrollment is done and later it is also identified,
only progress is NOT displayed.

journlctl --unit fprintd.service was shown the messages of fingerprint
enroll swipes properly with out any issues

"Capture initiated, please place your finger now n the sensor now" for all 
swipes.
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-09-24 (5 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Package: gnome-control-center 1:3.36.4-0ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Tags:  focal
Uname: Linux 5.4.0-48-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

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


** Tags: apport-collected focal

** Tags added: apport-collected focal

** Description changed:

  Fingerprint enroll progress is NOT displayed for immediate 2nd fingerprint 
enrollment with out closing the FP GUI.
  2nd finger enrollment: After first swipe of 2nd FP, even though progress is 
not displayed on circle for 2nd fingerprint, it is properly enrolled after 
continuous swipe and later it will be identified, but user will have confusion 
about appearance that is the 2nd finger enrollment is happening or not.
  
  Steps to reproduce:
  Enroll 1st FP ==> enrollment progress is shown on circle, after it completes, 
don't close GUI, proceed with 2nd finger enrollment
  Enroll the second FP ==> observe that enrollment progress is NOT shown on 
circle, but if we keep on placing finger, after few attempts, finger will be 
enrolled.
  
  verified on two DELL models
  model-1: latitude 7300: 2nd fp enrollment progress is shown for 1 or 2 
swipes, but didn't completed the progress circle.
  model-2: latitude 7520: 2nd fp enrollment progress is NOT shown at all
  
  Both cases 2nd FP enrollment is done and later it is also identified,
  only progress is NOT displayed.
  
  journlctl --unit fprintd.service was shown the messages of fingerprint
  enroll swipes properly with out any issues
  
- "Capture initiated, please place your finger now n the sensor now" for
- all swipes.
+ "Capture initiated, please place your finger now n the sensor now" for all 
swipes.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.4
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-09-24 (5 days ago)
+ InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
+ Package: gnome-control-center 1:3.36.4-0ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
+ Tags:  focal
+ Uname: Linux 5.4.0-48-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

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

Title:
  Fingerprint enroll progress is NOT displayed for immediate 2nd
  fingerprint enrollment

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

Bug description:
  Fingerprint enroll progress is NOT displayed for immediate 2nd fingerprint 
enrollment with out closing the FP GUI.
  2nd finger enrollment: After first swipe of 2nd FP, even though progress is 
not displayed on circle for 2nd fingerprint, it is properly enrolled after 
continuous swipe and later it will be identified, but user will have confusion 
about appearance that is the 2nd finger enrollment is happening or not.

  Steps to reproduce:
  Enroll 1st FP ==> enrollment progress is shown on circle, af

[Desktop-packages] [Bug 1896815] Re: Old Arabic Fonts are not working

Can you list some apps without and *without* the problem?

I wonder if the issue is specific to KDE apps, or if it extends to GNOME
apps and Xorg in general.

** Summary changed:

- Xorg freeze? Old Arabic Fonts are not working
+ Old Arabic Fonts are not working

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

Title:
  Old Arabic Fonts are not working

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Old Arabic Fonts (not MS fonts) were running on MS Word.

  they can not working on ubuntu.

  they listed in LO Writer , but they are not running in all kubuntu
  20.10 applications.

  I used fc-cache for install them. but they are not configured for
  running.

  Thank You

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CasperVersion: 1.452
  CompositorRunning: None
  CurrentDesktop: KDE
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Wed Sep 23 18:31:51 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th 
Gen Core Processor Integrated Graphics Controller [1462:7850]
  LiveMediaBuild: Kubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200922)
  MachineType: MSI MS-7850
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ar_EG.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85-G41 PC Mate(MS-7850)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd12/02/2013:br4.6:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7850
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.7-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/xorg/+bug/1896815/+subscriptions

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

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

apport information

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

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

Title:
  Fingerprint enroll progress is NOT displayed for immediate 2nd
  fingerprint enrollment

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

Bug description:
  Fingerprint enroll progress is NOT displayed for immediate 2nd fingerprint 
enrollment with out closing the FP GUI.
  2nd finger enrollment: After first swipe of 2nd FP, even though progress is 
not displayed on circle for 2nd fingerprint, it is properly enrolled after 
continuous swipe and later it will be identified, but user will have confusion 
about appearance that is the 2nd finger enrollment is happening or not.

  Steps to reproduce:
  Enroll 1st FP ==> enrollment progress is shown on circle, after it completes, 
don't close GUI, proceed with 2nd finger enrollment
  Enroll the second FP ==> observe that enrollment progress is NOT shown on 
circle, but if we keep on placing finger, after few attempts, finger will be 
enrolled.

  verified on two DELL models
  model-1: latitude 7300: 2nd fp enrollment progress is shown for 1 or 2 
swipes, but didn't completed the progress circle.
  model-2: latitude 7520: 2nd fp enrollment progress is NOT shown at all

  Both cases 2nd FP enrollment is done and later it is also identified,
  only progress is NOT displayed.

  journlctl --unit fprintd.service was shown the messages of fingerprint
  enroll swipes properly with out any issues

  "Capture initiated, please place your finger now n the sensor now" for all 
swipes.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-09-24 (5 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-control-center 1:3.36.4-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

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

apport information

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

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

Title:
  Fingerprint enroll progress is NOT displayed for immediate 2nd
  fingerprint enrollment

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

Bug description:
  Fingerprint enroll progress is NOT displayed for immediate 2nd fingerprint 
enrollment with out closing the FP GUI.
  2nd finger enrollment: After first swipe of 2nd FP, even though progress is 
not displayed on circle for 2nd fingerprint, it is properly enrolled after 
continuous swipe and later it will be identified, but user will have confusion 
about appearance that is the 2nd finger enrollment is happening or not.

  Steps to reproduce:
  Enroll 1st FP ==> enrollment progress is shown on circle, after it completes, 
don't close GUI, proceed with 2nd finger enrollment
  Enroll the second FP ==> observe that enrollment progress is NOT shown on 
circle, but if we keep on placing finger, after few attempts, finger will be 
enrolled.

  verified on two DELL models
  model-1: latitude 7300: 2nd fp enrollment progress is shown for 1 or 2 
swipes, but didn't completed the progress circle.
  model-2: latitude 7520: 2nd fp enrollment progress is NOT shown at all

  Both cases 2nd FP enrollment is done and later it is also identified,
  only progress is NOT displayed.

  journlctl --unit fprintd.service was shown the messages of fingerprint
  enroll swipes properly with out any issues

  "Capture initiated, please place your finger now n the sensor now" for all 
swipes.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-09-24 (5 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-control-center 1:3.36.4-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1896815] Re: Old Arabic Fonts are not working

Can you list some apps with and *without* the problem?

I wonder if the issue is specific to KDE apps, or if it extends to GNOME
apps and Xorg in general.

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

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

Title:
  Old Arabic Fonts are not working

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  Old Arabic Fonts (not MS fonts) were running on MS Word.

  they can not working on ubuntu.

  they listed in LO Writer , but they are not running in all kubuntu
  20.10 applications.

  I used fc-cache for install them. but they are not configured for
  running.

  Thank You

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CasperVersion: 1.452
  CompositorRunning: None
  CurrentDesktop: KDE
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Wed Sep 23 18:31:51 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th 
Gen Core Processor Integrated Graphics Controller [1462:7850]
  LiveMediaBuild: Kubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200922)
  MachineType: MSI MS-7850
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ar_EG.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2013
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85-G41 PC Mate(MS-7850)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd12/02/2013:br4.6:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7850
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.7-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/xorg/+bug/1896815/+subscriptions

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

[Desktop-packages] [Bug 1896825] Re: Mutter 3.28 doesn't compile with mesa 20

** Tags added: bionic

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

Title:
  Mutter 3.28 doesn't compile with mesa 20

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  In Progress

Bug description:
  [ Impact ]

  Mesa 20 update broke mutter builds, as visible in
  https://launchpad.net/ubuntu/+source/mutter/3.28.4+git20200505-0ubuntu18.04.1

  [ Test case ]

  Mutter should build cleanly in a bionic chroot

  [ Regression potential ]

  Wayland components aren't included in the final mutter build

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

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

[Desktop-packages] [Bug 1897693] Dependencies.txt

apport information

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

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

Title:
  Fingerprint enroll progress is NOT displayed for immediate 2nd
  fingerprint enrollment

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

Bug description:
  Fingerprint enroll progress is NOT displayed for immediate 2nd fingerprint 
enrollment with out closing the FP GUI.
  2nd finger enrollment: After first swipe of 2nd FP, even though progress is 
not displayed on circle for 2nd fingerprint, it is properly enrolled after 
continuous swipe and later it will be identified, but user will have confusion 
about appearance that is the 2nd finger enrollment is happening or not.

  Steps to reproduce:
  Enroll 1st FP ==> enrollment progress is shown on circle, after it completes, 
don't close GUI, proceed with 2nd finger enrollment
  Enroll the second FP ==> observe that enrollment progress is NOT shown on 
circle, but if we keep on placing finger, after few attempts, finger will be 
enrolled.

  verified on two DELL models
  model-1: latitude 7300: 2nd fp enrollment progress is shown for 1 or 2 
swipes, but didn't completed the progress circle.
  model-2: latitude 7520: 2nd fp enrollment progress is NOT shown at all

  Both cases 2nd FP enrollment is done and later it is also identified,
  only progress is NOT displayed.

  journlctl --unit fprintd.service was shown the messages of fingerprint
  enroll swipes properly with out any issues

  "Capture initiated, please place your finger now n the sensor now" for all 
swipes.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-09-24 (5 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-control-center 1:3.36.4-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1897192] Re: Put search box in top center of Activities panel, move date/time to right corner of panel.

** Tags added: focal

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Wishlist

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

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

Title:
  Put search box in top center of Activities panel, move date/time to
  right corner of panel.

Status in gnome-shell package in Ubuntu:
  Opinion

Bug description:
  1) Ubuntu 20.04
  2) Gnome 3.36
  3) If there was a search box in the top center of the Activities panel, it 
would make it easy for a user to quickly search for an app or information on 
the internet. Canonical could collect referral fees from Google or another 
search provider, when users search and buy products. The referral fees could be 
used to improve Ubuntu.
  4) There is not a search box in the top center of the Activities panel.

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

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

[Desktop-packages] [Bug 1897189] Re: External Monitor No Longer detected

You don't seem to have a kernel driver loaded for the Nvidia GPU, so any
ports attached to that GPU (like HDMI usually is) won't be usable.

This can happen if the Nvidia driver was installed and compiled for the
old kernel version but somehow failed to rebuilt for the new kernel
version.

Please try using the 'Additional Drivers' app to reinstall the Nvidia
driver and tell us what version it is.

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers (Ubuntu)

** Changed in: nvidia-graphics-drivers (Ubuntu)
   Status: New => Incomplete

** Summary changed:

- External Monitor No Longer detected
+ [nvidia] External Monitor No Longer detected

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

Title:
  [nvidia] External Monitor No Longer detected

Status in nvidia-graphics-drivers package in Ubuntu:
  Incomplete

Bug description:
  I noticed that a new kernel was available and booted into it today,
  after booting previous issues (display font size on login, and laptop
  touchpad/trackpoint not working) were resolved.

  However, my external monitor no longer displays in the settings, and
  can't appear to be used.

  I suspect the kernel update coincides with an nvidia driver update,
  but haven't looked into that yet.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] 許可がありません: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 25 09:29:55 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo GP107M [GeForce GTX 1050 Ti Mobile] [17aa:2266]
  InstallationDate: Installed on 2020-09-08 (16 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 20MFCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=50c34368-0155-42cc-a9a9-5520bb25778a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET49W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET49W(1.31):bd07/08/2020:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-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/nvidia-graphics-drivers/+bug/1897189/+subscriptions

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

[Desktop-packages] [Bug 1897211] Re: Ubuntu not loading/detecting discrete GPU after update

Similar to the above comment, I am not sure this is a bug or just a
change in GUI.

If you think it is a bug then please help us to identify the issue by
running these commands:

  lspci -kv > lspci.txt
  journalctl -b0 > journal.txt

and attach the resulting text files here.


** Changed in: gnome-control-center (Ubuntu)
   Status: Invalid => Incomplete

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

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

Title:
  Ubuntu not loading/detecting discrete GPU after update

Status in Ubuntu:
  Incomplete

Bug description:
  After the most recent update Ubuntu 20.04.1 no longer detects or lists the 
Radeon 560X dedicated GPU in my laptop (the About sections lists the Vega 8 
iGPU twice...). Even after a complete clean reinstall the issue persists. Even 
clicking "Launch using Dedicated Graphics Card" is broken, and it crashes X, 
which reloads itself. 
  I'm not the most knowledgeable on the graphics stack, so not sure what I need 
to provide!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.4-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 25 05:43:36 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-09-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1897259] Re: Xorg crash

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

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

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

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

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


** Tags added: amdgpu

** Summary changed:

- Xorg crash
+ Crash

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

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

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

Title:
  Crash

Status in Ubuntu:
  Incomplete

Bug description:
  System get crashed after few hour of working.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 25 15:55:58 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev ea) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Stoney [Radeon R2/R3/R4/R5 Graphics] 
[103c:8330]
  InstallationDate: Installed on 2018-09-29 (726 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Laptop 15-bw0xx
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=f3968aa1-700a-436c-91b4-b7139739a0d6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8330
  dmi.board.vendor: HP
  dmi.board.version: 27.28
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd09/07/2017:svnHP:pnHPLaptop15-bw0xx:pvrType1ProductConfigId:rvnHP:rn8330:rvr27.28:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-bw0xx
  dmi.product.sku: 2EY94PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-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/+bug/1897259/+subscriptions

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

[Desktop-packages] [Bug 1897315] Re: xdiagnose

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

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

Title:
  xdiagnose

Status in Ubuntu:
  Incomplete

Bug description:
  xdiagnose

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-119.120-generic 4.15.18
  Uname: Linux 4.15.0-119-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Sep 25 18:10:02 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1462:2127]
  InstallationDate: Installed on 2017-12-18 (1012 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-119-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: G31M-GS.
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd05/20/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnG31M-GS.:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Feb 28 10:53:55 2019
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputGenius Optical Mouse MOUSE, id 8
   inputCHICONY USB Keyboard KEYBOARD, id 9
   inputCHICONY USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1897242] Re: Xorg crash

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

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

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

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

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


** Summary changed:

- Xorg crash
+ Crash

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

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

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

Title:
  Crash

Status in Ubuntu:
  Incomplete

Bug description:
  when opening software source

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Sat Sep 26 08:36:17 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:0767]
 Subsystem: Dell Radeon R7 M445 [1028:0767]
  InstallationDate: Installed on 2020-09-25 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  MachineType: Dell Inc. Inspiron 5567
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=488db7bf-9ea8-4ae7-bc7e-8a245481d9e2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.10
  dmi.board.name: 02YHJP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.10:bd02/24/2020:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn02YHJP:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5567
  dmi.product.sku: 0767
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-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/+bug/1897242/+subscriptions

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

[Desktop-packages] [Bug 1897295] Re: freeze display and no more toothead wheel high&right of the screen for parameters

This looks like a problem with the 'nouveau' kernel driver.

First we need to check to see if it's already fixed in a newer version
so please try booting Ubuntu 20.04.1 or 18.04.5 from
https://releases.ubuntu.com/

** Tags added: nouveau

** Summary changed:

- freeze display and no more toothead wheel high&right of the screen for 
parameters
+ [nouveau] freeze display and no more toothead wheel high&right of the screen 
for parameters

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

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

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

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

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

Title:
  [nouveau] freeze display and no more toothead wheel high&right of the
  screen for parameters

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  -often I need several reboot for a clean ubuntu installation, the courant 
problem is 
  sceen freeze in the middle of ubuntu installation 
  -often ubuntu freeze during the session, and I must restart the computer
  -parameters wheel is lost
  -I don't understand very well english

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18
  Uname: Linux 4.15.0-118-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Sep 25 16:08:51 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK208 [GeForce GT 710] [10de:1289] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GK208 [GeForce GT 710] [1043:866f]
  InstallationDate: Installed on 2013-08-27 (2586 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  MachineType: Hewlett-Packard HP Compaq 8000 Elite CMT PC
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic 
root=UUID=53e6c79d-4a52-4722-8a07-22762747982a ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G7 v01.02
  dmi.board.asset.tag: CZC1058ZQF
  dmi.board.name: 3647h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC1058ZQF
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G7v01.02:bd10/22/2009:svnHewlett-Packard:pnHPCompaq8000EliteCMTPC:pvr:rvnHewlett-Packard:rn3647h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq 8000 Elite CMT PC
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Fri Sep 25 09:16:47 2020
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.6

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

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

[Desktop-packages] [Bug 1897530] Re: The modesetting driver does not gracefully handle missing connectors on EnterVT

There are lots of similar bug reports and crash reports that might be
related to this. Please help to link up and de-duplicate them as
appropriate...

https://bugs.launchpad.net/ubuntu/+source/xorg-
server?field.searchtext=EnterVT

https://errors.ubuntu.com/?release=Ubuntu%2020.04&package=xorg-
server&period=year

** Tags added: bionic

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

Title:
  The modesetting driver does not gracefully handle missing connectors
  on EnterVT

Status in xorg-server package in Ubuntu:
  New
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg-server source package in Bionic:
  Invalid
Status in xorg-server-hwe-18.04 source package in Bionic:
  New
Status in xorg-server source package in Focal:
  New
Status in xorg-server-hwe-18.04 source package in Focal:
  Invalid

Bug description:
  Expectation: on removal of external display during S3, after resume eDP 
rendering should still continue by Nvidia.
  Symptom description: Plug out DP cable when suspension, when resume, X will 
crash.

  1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but 
NV was rendering for eDP.
  2. After S3 entry dock was removed.
  3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails 
resume of TB3 devices and logs confirm that.
  4. X fails to enter VT due to Null meta mode.

  
  To address the explanation, X is not failing to enter the VT due to NVIDIA’s 
NULL MetaMode. It’s the Intel (modesetting) driver that is failing to enter the 
VT. It’s expected that NVIDIA would have a NULL MetaMode, since there are no 
displays connected to it. Our driver is pretty robust to head state changes – 
even if we have to fall back to a NULL MetaMode, we will still enter the VT 
successfully.

  The logs clearly show that the failure is originating from the Intel
  (modesetting) driver, not the NVIDIA driver. The relevant path in X is
  driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes().
  In this function, the Intel driver tries to set a mode on each of the
  previously connected/enabled displays, and it tries to find the
  closest possible mode using xf86OutputFindClosestMode(). This is
  similar to our driver’s functionality, but unlike us, they don’t
  support a NULL fallback. If there are no modes supported on one of the
  displays, it simply fails, which causes X to terminate:

  DisplayModePtr mode = xf86OutputFindClosestMode(output,
  pScrn->currentMode);

  if (!mode)
  return FALSE;

  Since we removed one of the displays via the dock, it fails. It
  doesn’t matter if the internal panel is still available, Intel will
  fail if it can’t re-enable ANY of the previously connected displays.

  Technically the modesetting driver isn’t specifically an Intel driver,
  it’s a generic driver that can be used by any DRM device – it’s just
  that Intel has chosen to use the modesetting driver as their standard
  Linux X driver going forward.

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

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

[Desktop-packages] [Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("EnterVT failed for gpu screen %d\n") from xf86VTEnter() from WakeupHandler()

** Summary changed:

- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no 
screens found") from dix_main()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from 
FatalError("EnterVT failed for gpu screen %d\n") from xf86VTEnter() from 
WakeupHandler()

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

Title:
  Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError("EnterVT failed for gpu screen %d\n") from xf86VTEnter()
  from WakeupHandler()

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530
  https://errors.ubuntu.com/problem/4c203db78dea0a68c29cbd981d4abbd4aef31851

  ---

  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.17.3-2ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  Date: Mon Feb  8 17:07:23 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21da]
  InstallationDate: Installed on 2015-04-30 (283 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 429149G
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic 
root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0 
panic=-1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x557f8180ff00, argc=11, argv=0x7fffc9e34fd8, 
init=, fini=, rtld_fini=, 
stack_end=0x7fffc9e34fc8) at libc-start.c:289
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 05/18/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET46WW (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 429149G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 429149G
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.66-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160127-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
  xserver.bootTime: Mon Feb  8 17:08:14 2016
  xserver.configfile: default
  xserver.errors: systemd-logind: failed to get session: PID 9847 does not 
belong to any known session
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728
   vendor LGD
  xserver.version: 2:1.17.3-2ubuntu2

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

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

[Desktop-packages] [Bug 1897659] Re: Memory issues hangs the whole graphic system

** Summary changed:

- Xorg memory issues hangs the whole graphic system
+ Memory issues hangs the whole graphic system

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-450
(Ubuntu)

** Tags added: nvidia

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

Title:
  Memory issues hangs the whole graphic system

Status in nvidia-graphics-drivers-450 package in Ubuntu:
  New

Bug description:
  This happens to me around once per week. The first line I found in
  syslog is:

  Xorg: page allocation failure: order:5,
  mode:0x40cc0(GFP_KERNEL|__GFP_COMP),
  nodemask=(null),cpuset=/,mems_allowed=0

  Attached is the whole syslog extract for the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:07: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  450.66  Wed Aug 12 19:42:48 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Sep 28 23:58:11 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 450.66, 5.4.0-48-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GT 740] [10de:0fc8] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GK107 [GeForce GT 740] [10de:1099]
  InstallationDate: Installed on 2020-07-11 (79 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=3d184b61-094a-475b-b817-3f588547fea1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/07/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4602
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4602:bd03/07/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  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.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-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/nvidia-graphics-drivers-450/+bug/1897659/+subscriptions

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

[Desktop-packages] [Bug 1897638] Re: Unable to open gnome-system-settings in 20.04

Please try reinstalling the package the missing file comes from:

  sudo apt install --reinstall gnome-control-center-data

and then reboot.

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

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

Title:
  Unable to open gnome-system-settings in 20.04

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

Bug description:
  Unable to open gnome-system-settings in Ubuntu 20.04

  error message 
  (gnome-control-center:19643): GLib-GIO-ERROR **: 04:14:16.060: Settings 
schema 'org.gnome.ControlCenter' is not installed
  Trace/breakpoint trap (core dumped)
  I have tried almost every fix still didn't get solved

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.4-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 04:17:10 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+bolt-l+X43
  InstallationDate: Installed on 2019-07-17 (439 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1896577] Re: FFE: new upstream release 20.2 and migrate to llvm 11

2020-09-29 Thread Iain Lane

Already said on IRC, but mentioning here for other RT members:

I'd like to see (1) an analysis of the risks of this update, and (2) a
description of what testing you've done, please.

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

Title:
  FFE: new upstream release 20.2 and migrate to llvm 11

Status in mesa package in Ubuntu:
  New

Bug description:
  Mesa 20.2.0 has been delayed by upstream, but we still want it in
  20.10. It's currrently at rc4, final was supposed to be out a month
  ago. It's been in debian experimental since rc1.

  The packaging in debian also migrates to use llvm 11.

  packages for groovy are available on ppa:canonical-x/x-staging

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

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

[Desktop-packages] [Bug 1895897] Re: Xorg assert failure: hw/xfree86/common/xf86Helper.c:1743: xf86ScreenToScrn: Assertion `pScreen->myNum < xf86NumScreens' failed.

** Summary changed:

- Xorg assert failure: Xorg: 
../../../../../../hw/xfree86/common/xf86Helper.c:1743: xf86ScreenToScrn: 
Assertion `pScreen->myNum < xf86NumScreens' failed.
+ Xorg assert failure: hw/xfree86/common/xf86Helper.c:1743: xf86ScreenToScrn: 
Assertion `pScreen->myNum < xf86NumScreens' failed.

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

Title:
  Xorg assert failure: hw/xfree86/common/xf86Helper.c:1743:
  xf86ScreenToScrn: Assertion `pScreen->myNum < xf86NumScreens' failed.

Status in xorg-server package in Ubuntu:
  New

Bug description:
  I got this crash report but I don't know what exactly triggered it.
  I'm willing to provide more info when needed.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: xserver-xorg-core 2:1.20.8-2ubuntu6
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AssertionMessage: Xorg: 
../../../../../../hw/xfree86/common/xf86Helper.c:1743: xf86ScreenToScrn: 
Assertion `pScreen->myNum < xf86NumScreens' failed.
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Wed Sep 16 23:19:51 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:506a]
  InstallationDate: Installed on 2020-09-16 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 002: ID 0461:4e57 Primax Electronics, Ltd HID compliant device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20LTS01800
  ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/1000/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty 
-novtswitch -verbose 3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=301ac90f-9a29-425d-9b75-b6b2a43bf00a ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   __assert_fail_base (fmt=0x7fa38d729588 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=0x55dc8d338b00 "pScreen->myNum < xf86NumScreens", 
file=0x55dc8d338a90 "../../../../../../hw/xfree86/common/xf86Helper.c", 
line=1743, function=) at assert.c:92
   __GI___assert_fail (assertion=0x55dc8d338b00 "pScreen->myNum < 
xf86NumScreens", file=0x55dc8d338a90 
"../../../../../../hw/xfree86/common/xf86Helper.c", line=1743, 
function=0x55dc8d338d20 "xf86ScreenToScrn") at assert.c:101
   xf86ScreenToScrn ()
  Title: Xorg assert failure: Xorg: 
../../../../../../hw/xfree86/common/xf86Helper.c:1743: xf86ScreenToScrn: 
Assertion `pScreen->myNum < xf86NumScreens' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 12/18/2019
  dmi.bios.release: 1.37
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET60W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LTS01800
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.37
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:br1.37:efr1.37:svnLENOVO:pn20LTS01800:pvrThinkPadL480:rvnLENOVO:rn20LTS01800:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L480
  dmi.product.name: 20LTS01800
  dmi.product.sku: LENOVO_MT_20LT_BU_Think_FM_ThinkPad L480
  dmi.product.version: ThinkPad L480
  dmi.sys.vendor: LENOVO
  separator:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.5-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notificatio

[Desktop-packages] [Bug 1897273] Re: booting ubuntu groovy daily; display unusuable

2020-09-29 Thread Chris Guiver

Changed to INCOMPLETE... (likely INVALID)

I'm so used to very old cards I don't need SAFE GRAPHICS, thus forgot
it's there..

The install completes when that SAFE GRAPHICS is used.

Issues on first boot.. but that needs exploration..

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Incomplete

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

Title:
  booting ubuntu groovy daily; display unusuable

Status in ubuntu-meta package in Ubuntu:
  Incomplete

Bug description:
  booting Ubuntu daily on
  dell [optiplex] 990 (i7-2600, 16gb, nvidia geforce gt 6600 gt)

  Media validation occurs as expected, passes the Ubuntu logo is as
  expected then I get a Ubuntu background type color and the session is
  now unusable

  The first display (after checks etc) occur is

  https://photos.app.goo.gl/gHgb98LTgGiWtMEw7

  If left, i'll eventually get a purple screen and cursor, however
  nothing that responds as expected.

  No usable session, but screen is there, background a solid Ubuntu
  color, with normal cursor; alas nothing more.

  By switching to a terminal,  I can check that no squashfs errors
  occurred & explore the system (including file this bug), however
  switching back gets me screens like

  https://photos.app.goo.gl/LJg4qvS7VajRny4e8

  followed by hitting CTRL+ALT+T to open a terminal and the screen
  changes to

  https://photos.app.goo.gl/PJQxSABrNwg6UNGW9

  The CTRL+ALT+T was recognized, as the terminal can be seen in the
  pinky area top left of screen, but it's not usable...

  I wonder if it's the screensaver kicking in that screws up the
  session, but I've not worked that up yet.  I've been unable to watch
  the machine the whole time so I've not worked out pattern.

  ( FYI:  this is not the first boot or attempt. This has occurred now
  three times tried (same iso, just rebooting machine).  My intention
  tonight was explore
  https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1897173 via
  install on this box alas I can't install with it performing like this.
  A number of QA-test installs have been run on this system today,
  Lubuntu had no issues, Xubuntu failed due 1897173 with readable
  screens )

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-desktop 1.457
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu47
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  Date: Fri Sep 25 11:58:18 2020
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200925)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1870356] Re: Can't connect to paired bluetooth devices via g-c-c

thanks, that's a known issue and reported as bug #1870356

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

Title:
  Can't connect to paired bluetooth devices via g-c-c

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  I have a paired bluetooth device listed as "Disconnected" in the
  Bluetooth section of gnome-control-center. In order to connect to it I
  click on the device name and switch the "Connection" slider to the
  "on" position. The slider moves but immediately bounces back to the
  "off" position, and nothing happens: the connection is not
  established. It never works even if I try several times.

  This happens on an up-to-date Focal system and it's always
  reproducible across reboots and power cycles of the device. I don't
  think it's a problem of the device itself or of the underlying
  bluetooth stack, as connecting/disconnecting to the device works
  perfectly if I use blueman-manager instead of gnome-control-center.

  I don't know if this is a regression as I was not using bluetooth before 
installing Focal. FWIW (very little), the device connects/disconnects perfectly 
to Android phones.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-02-26 (400 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: gnome-control-center 1:3.36.1-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27
  Tags: focal uec-images wayland-session third-party-packages
  Uname: Linux 5.4.0-20-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-21 (72 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lpadmin lxd plugdev 
sambashare sbuild sudo utah
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1870356] Re: Can't connect to paired bluetooth devices via g-c-c

(sorry the previous comment was obviously on the wrong bug)

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

Title:
  Can't connect to paired bluetooth devices via g-c-c

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  I have a paired bluetooth device listed as "Disconnected" in the
  Bluetooth section of gnome-control-center. In order to connect to it I
  click on the device name and switch the "Connection" slider to the
  "on" position. The slider moves but immediately bounces back to the
  "off" position, and nothing happens: the connection is not
  established. It never works even if I try several times.

  This happens on an up-to-date Focal system and it's always
  reproducible across reboots and power cycles of the device. I don't
  think it's a problem of the device itself or of the underlying
  bluetooth stack, as connecting/disconnecting to the device works
  perfectly if I use blueman-manager instead of gnome-control-center.

  I don't know if this is a regression as I was not using bluetooth before 
installing Focal. FWIW (very little), the device connects/disconnects perfectly 
to Android phones.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-02-26 (400 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: gnome-control-center 1:3.36.1-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27
  Tags: focal uec-images wayland-session third-party-packages
  Uname: Linux 5.4.0-20-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-21 (72 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lpadmin lxd plugdev 
sambashare sbuild sudo utah
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend

2020-09-29 Thread Phil

@Daniel, is it possible to add a repo for this fix early ahead of coming
down in the release repos?

On the release repos I have the latest version.

mutter is already the newest version (3.36.4-0ubuntu0.20.04.2).

Cheers for any advice

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

Title:
  [nvidia] Background image corrupted after standby or resume from
  suspend

Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix
Status in mutter source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-390 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-435 source package in Focal:
  Won't Fix

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  9 10:58:35 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed
   nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c]
  InstallationDate: Installed on 2019-11-29 (10 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTek Computer Inc. G60JX
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G60JX
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.family: PEGA Family
  dmi.product.name: G60JX
  dmi.product.sku: 0
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTek Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1897569] Re: package libx11-6 2:1.6.9-2ubuntu1 failed to install/upgrade: el subproceso dpkg-deb --control devolvió el código de salida de error 2

THank you for your bug report. It does sound a corrupted download or a
local problem though, could you try downloading the update again?

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

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

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

Title:
  package libx11-6 2:1.6.9-2ubuntu1 failed to install/upgrade: el
  subproceso dpkg-deb --control devolvió el código de salida de error 2

Status in libx11 package in Ubuntu:
  Incomplete

Bug description:
  I was doing things in mu ubuntu,when this problem appears,i don't know
  more about that problem,thats the problem i had

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libx11-6 2:1.6.9-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Mon Sep 28 15:15:50 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgTerminalLog:
   [1mdpkg-deb:[0m [1;31merror:[0m 
`/tmp/apt-dpkg-install-aFUkKT/00-libx11-6_2%3a1.6.9-2ubuntu1.1_amd64.deb' no es 
un archivo en formato Debian
   [1mdpkg:[0m error al procesar el archivo 
/tmp/apt-dpkg-install-aFUkKT/00-libx11-6_2%3a1.6.9-2ubuntu1.1_amd64.deb 
(--unpack):
el subproceso dpkg-deb --control devolvió el código de salida de error 2
  ErrorMessage: el subproceso dpkg-deb --control devolvió el código de salida 
de error 2
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050 3GB] [10de:1c83] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP107 [GeForce GTX 1050 3GB] 
[1458:379d]
  InstallationDate: Installed on 2020-09-28 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Micro-Star International Co., Ltd. MS-7A38
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic 
root=UUID=7fd02831-c266-4953-a0c3-f9d33241485c ro quiet splash vt.handoff=7
  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.2ubuntu0.1
  SourcePackage: libx11
  Title: package libx11-6 2:1.6.9-2ubuntu1 failed to install/upgrade: el 
subproceso dpkg-deb --control devolvió el código de salida de error 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P.60
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M BAZOOKA V2 (MS-7A38)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP.60:bd07/22/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A38:pvr5.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MBAZOOKAV2(MS-7A38):rvr5.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr5.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A38
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 5.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-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/libx11/+bug/1897569/+subscriptions

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

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

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

** This bug has been marked a duplicate of bug 1897570
   PCI/internal sound card not detected

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  ubuntu 20.04.01 clean install.
  thanks in advance for your attention. polite comment, no yelling here. going 
thru transfer and setup machine previous install ubuntu 16.04 when sound was 
working.

  lspci lists all sources. internal intel ada card not intialized. only
  option in sound is hdmi. all worked before clean install.

  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA)
  01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio 
[Radeon HD 5400/6300/7300 Series]

  william@william-Studio-XPS-7100:~$ cat /proc/asound/cards
   0 [SB ]: HDA-Intel - HDA ATI SB
HDA ATI SB at 0xfe8f4000 irq 16
   1 [HDMI   ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xfe9bc000 irq 26

  william@william-Studio-XPS-7100:~$ cat /proc/asound/card0/codec* | grep Codec
  Codec: Realtek ALC887

  same audio issue, settings and pavucontrol only see hdmi audio out and not 
intel hda audio
  older dell desktop with 4 years previous use ubuntu. audio worked on morning 
of my fresh install ubuntu 20.04.01. oddly virtualbox install ubuntu 20.04 and 
other dist same linux, but broke my base machine. base machine restart and 
messing with pavucontrol allowed my to select appropriate settings to restore 
audio after exit virutalbox session. all else works and i do not want to risk 
all my transfer/setup trying to fix this one issue, as important as it may be 
to me.

  just politely adding my experience to thread in case future update may
  address this issue.

  william@william-Studio-XPS-7100:~$ lspci
  00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS880 Host Bridge
  00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI 
bridge (ext gfx port 0)
  00:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI 
bridge (PCIE port 2)
  00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode]
  00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB 
OHCI1 Controller
  00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB 
OHCI1 Controller
  00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller 
(rev 3c)
  00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 IDE Controller
  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA)
  00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 
LPC host controller
  00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI 
Bridge
  00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
  00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
HyperTransport Configuration
  00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Address Map
  00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
DRAM Controller
  00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Miscellaneous Control
  00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor 
Link Control
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cedar [Radeon HD 5000/6000/7350/8350 Series]
  01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio 
[Radeon HD 5400/6300/7300 Series]
  02:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetLink BCM57788 
Gigabit Ethernet PCIe (rev 01)
  03:05.0 Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax 
Modem

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  william1432 F pulseaudio
   /dev/snd/controlC0:  william1

[Desktop-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend

It already exists in focal-proposed. So you can enable 'proposed'
updates or just download the new packages:

https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2/+build/19963778

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

Title:
  [nvidia] Background image corrupted after standby or resume from
  suspend

Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix
Status in mutter source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-390 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-435 source package in Focal:
  Won't Fix

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  9 10:58:35 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed
   nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c]
  InstallationDate: Installed on 2019-11-29 (10 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTek Computer Inc. G60JX
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G60JX
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.family: PEGA Family
  dmi.product.name: G60JX
  dmi.product.sku: 0
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTek Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1897613] Re: fprint hangs after first finger scan (fprintd-enroll - fprintd_demo)

Thank you for the report, it sounds like Marco requested for the
launchpad bug so I'm assigning to him

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

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

** Changed in: libfprint (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Bug watch added: gitlab.freedesktop.org/libfprint/libfprint/-/issues #306
   https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/306

** Also affects: libfprint via
   https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/306
   Importance: Unknown
   Status: Unknown

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

Title:
  fprint hangs after first finger scan (fprintd-enroll - fprintd_demo)

Status in libfprint:
  Unknown
Status in libfprint package in Ubuntu:
  Triaged

Bug description:
  Hi, I don't know if this problem is related to fprintd or libfprint, but I am 
happy to help debugging.
  I have got an APC BIOPOD EC fingerprint reader, sporting an AuthenTec, Inc. 
AES3500 TruePrint Sensor (lsusb gives 08ff:5731).
  My system is:
  LSB Version:  
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic
  Kernel: 4.15.0-111-generic
  Installed fprintd via APT and compiled libfprint after git cloning.
  I looked around in the different open issues, and I saw it is a problem 
experienced by many.
  It doesn't matter if I use gnome fingerprint authentication setup

  Opened a bug on libfprint here
  https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/306

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

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

[Desktop-packages] [Bug 1897644] Re: gengal missing from libreoffice-dev in 7.X

the issue has been fixed now in

https://launchpad.net/ubuntu/+source/openclipart/1:0.18+dfsg-19ubuntu2

the files are installed in libreoffice-dev-gui now

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

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

Title:
  gengal missing from libreoffice-dev in 7.X

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  
  In libreoffice 6.4.6-0ubuntu0.20.04.1, when the libreoffice-dev package is 
installed, we have /usr/lib/libreoffice/program/{gengal, gengal.bin}. However 
for any 7.x version of libreoffice, these gengal files are missing.

  This causes a failure in openclipart, affecting the groovy build:
  https://lists.ubuntu.com/archives/ubuntu-devel/2020-September/041198.html

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

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

[Desktop-packages] [Bug 1897690] Re: ping: socket: Address family not supported by protocol

Thank you for the bug report, that's an upstream issue and has been
reported there

https://github.com/iputils/iputils/issues/293

** Bug watch added: github.com/iputils/iputils/issues #293
   https://github.com/iputils/iputils/issues/293

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

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

** Also affects: iputils via
   https://github.com/iputils/iputils/issues/293
   Importance: Unknown
   Status: Unknown

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

Title:
  ping: socket: Address family not supported by protocol

Status in Iputils:
  Unknown
Status in iputils package in Ubuntu:
  Triaged

Bug description:
  The ping utility prints this curious error/warning message:

  ```
  ping: socket: Address family not supported by protocol
  ```

  Otherwise seems to be working just fine:

  ```
  > ping 127.0.0.1
  ping: socket: Address family not supported by protocol
  PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
  64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.048 ms
  64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.050 ms
  64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.043 ms
  64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.046 ms
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: iputils-ping 3:20200821-2
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 10:42:17 2020
  InstallationDate: Installed on 2016-09-05 (1484 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: iputils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1897693] Re: Fingerprint enroll progress is NOT displayed for immediate 2nd fingerprint enrollment

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

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

Title:
  Fingerprint enroll progress is NOT displayed for immediate 2nd
  fingerprint enrollment

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

Bug description:
  Fingerprint enroll progress is NOT displayed for immediate 2nd fingerprint 
enrollment with out closing the FP GUI.
  2nd finger enrollment: After first swipe of 2nd FP, even though progress is 
not displayed on circle for 2nd fingerprint, it is properly enrolled after 
continuous swipe and later it will be identified, but user will have confusion 
about appearance that is the 2nd finger enrollment is happening or not.

  Steps to reproduce:
  Enroll 1st FP ==> enrollment progress is shown on circle, after it completes, 
don't close GUI, proceed with 2nd finger enrollment
  Enroll the second FP ==> observe that enrollment progress is NOT shown on 
circle, but if we keep on placing finger, after few attempts, finger will be 
enrolled.

  verified on two DELL models
  model-1: latitude 7300: 2nd fp enrollment progress is shown for 1 or 2 
swipes, but didn't completed the progress circle.
  model-2: latitude 7520: 2nd fp enrollment progress is NOT shown at all

  Both cases 2nd FP enrollment is done and later it is also identified,
  only progress is NOT displayed.

  journlctl --unit fprintd.service was shown the messages of fingerprint
  enroll swipes properly with out any issues

  "Capture initiated, please place your finger now n the sensor now" for all 
swipes.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-09-24 (5 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Package: gnome-control-center 1:3.36.4-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Tags:  focal
  Uname: Linux 5.4.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 505065] Re: Bad behavior with unreadable files

The issue described there doesn't seem to exist anymore in the current
version

** Changed in: totem (Ubuntu)
 Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned)

** Changed in: totem (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Bad behavior with unreadable files

Status in Totem:
  Expired
Status in totem package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: totem

  If a user does not have read permissions for a file s/he is trying to
  open, while it is already playing something, Totem becomes
  unresponsive to his/her commands until it is closed and restarted.

  Prerequisites:

  1. Have the package example-content installed, or two media files of your 
choosing.
  2. Designate one as ReadableFile. Make sure it's readable (chown me:me 
ReadableFile; chmod u+r ReadableFile).
  3. Designate one as UnreadableFile. Make sure it's NOT readable (chown 
root:root UnreadableFile; chmod o-rwx UnreadableFile).

  Steps to reproduce:

  1. Open Totem.
  2. Menu File/Open, choose ReadableFile.
  3. Menu File/Open, choose UnreadableFile.
  4. Four dialog boxes appear on top of each other, each saying the same thing 
about an unreadable file. (Expected: one dialog is enough ;)
  5. Menu File/Open, choose ReadableFile.
  6. Nothing happens. (Expected: ReadableFile starts playing again)

  This also happens if the File menu's recent entries are used to play
  UnreadableFile.

  ProblemType: Bug
  Architecture: amd64
  Date: Sat Jan  9 05:12:57 2010
  DistroRelease: Ubuntu 10.04
  LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20091209)
  Package: totem 2.28.4-0ubuntu4
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-7.10-generic
  SourcePackage: totem
  Tags: lucid
  Uname: Linux 2.6.32-7-generic x86_64

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

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

[Desktop-packages] [Bug 1897690] Re: ping: socket: Address family not supported by protocol

2020-09-29 Thread Bug Watch Updater

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

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

Title:
  ping: socket: Address family not supported by protocol

Status in Iputils:
  New
Status in iputils package in Ubuntu:
  Triaged

Bug description:
  The ping utility prints this curious error/warning message:

  ```
  ping: socket: Address family not supported by protocol
  ```

  Otherwise seems to be working just fine:

  ```
  > ping 127.0.0.1
  ping: socket: Address family not supported by protocol
  PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
  64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.048 ms
  64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.050 ms
  64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.043 ms
  64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.046 ms
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: iputils-ping 3:20200821-2
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 10:42:17 2020
  InstallationDate: Installed on 2016-09-05 (1484 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: iputils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1897613] Re: fprint hangs after first finger scan (fprintd-enroll - fprintd_demo)

2020-09-29 Thread Treviño

** Also affects: libfprint (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

** Changed in: libfprint (Ubuntu Focal)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  fprint hangs after first finger scan (fprintd-enroll - fprintd_demo)

Status in libfprint:
  Unknown
Status in libfprint package in Ubuntu:
  Triaged
Status in libfprint source package in Focal:
  Triaged

Bug description:
  Hi, I don't know if this problem is related to fprintd or libfprint, but I am 
happy to help debugging.
  I have got an APC BIOPOD EC fingerprint reader, sporting an AuthenTec, Inc. 
AES3500 TruePrint Sensor (lsusb gives 08ff:5731).
  My system is:
  LSB Version:  
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic
  Kernel: 4.15.0-111-generic
  Installed fprintd via APT and compiled libfprint after git cloning.
  I looked around in the different open issues, and I saw it is a problem 
experienced by many.
  It doesn't matter if I use gnome fingerprint authentication setup

  Opened a bug on libfprint here
  https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/306

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

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

[Desktop-packages] [Bug 1893300] Re: The status of cups still shows idle when the printer has been unplugged

2020-09-29 Thread hugh chao

** Description changed:

  [ Impact ]
  After printers (non-ippusb protocal) have been disconnected, the status of 
cups still shows "idle" instead of "disabled", so seems the disconnected 
procedure hasn't worked well.
  
  [ Test Case ]
  1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 
20.04 machine
  2. Wait for the status of cups became "Idle" (lpstat -p)
  3. Unplug the cable of the printer
  4. Check the status of cups again. (lpstat -p)
  
  [Expected result]
  The status should show disabled.
  
  [Actual result]
  The status shows idle.
  
  [info]
  Target:
  HP LaserJet Pro203dw
  HP Officejet 100 Mobile Printer
  HP Officeject 200 Mobile Printer
  Brother HL-2250DN
  Samsung ML-331x
+ 
+ Upstream Bug: https://github.com/OpenPrinting/system-config-
+ printer/issues/182

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

Title:
  The status of cups still shows idle when the printer has been
  unplugged

Status in OEM Priority Project:
  In Progress
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  [ Impact ]
  After printers (non-ippusb protocal) have been disconnected, the status of 
cups still shows "idle" instead of "disabled", so seems the disconnected 
procedure hasn't worked well.

  [ Test Case ]
  1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 
20.04 machine
  2. Wait for the status of cups became "Idle" (lpstat -p)
  3. Unplug the cable of the printer
  4. Check the status of cups again. (lpstat -p)

  [Expected result]
  The status should show disabled.

  [Actual result]
  The status shows idle.

  [info]
  Target:
  HP LaserJet Pro203dw
  HP Officejet 100 Mobile Printer
  HP Officeject 200 Mobile Printer
  Brother HL-2250DN
  Samsung ML-331x

  Upstream Bug: https://github.com/OpenPrinting/system-config-
  printer/issues/182

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1893300/+subscriptions

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

[Desktop-packages] [Bug 1896332] Re: SRU 3.36.6

2020-09-29 Thread Tim Passingham

Hi. My mistake.  I had, some time ago, needed to install one package
from focal-proposed, and to do this had turned off letting synaptic etc
from showing all proposed updates by adding a file in
/etc/apt/preference.d.  I'd forgotten about this.

sudo aptitude -t focal-proposed

showed that mutter updates did indeed exist, so I manually installed
mutter/focal-proposed and gir1.2-mutter-6/focal-proposed (which each
installed one other file).

So far all my testing has been good - no cut/copy/paste errors.

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

Title:
  SRU 3.36.6

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.6

  [ Test case ]

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  GNOME Shell and its components should continue working

  [ Regression potential ]

  There have been fixes in X11 device management, desktop background
  image handling, screen-casting and night-switch.

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

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

[Desktop-packages] [Bug 1879968] Re: Copy/paste still sometimes fails in LibreOffice and Wine apps

2020-09-29 Thread Tim Passingham

3.36.6-1 tested on my focal system using focal-proposed. All seems OK
thus far.

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

Title:
  Copy/paste still sometimes fails in LibreOffice and Wine apps

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed

Bug description:
  In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste
  operations to fail pretty often: the text that was pasted was not the
  text that was just copied.  See the long discussion at bug #1852183.
  The bug was recently marked closed, since the package mutter -
  3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug
  occur much less frequently.

  Unfortunately the bug still exists, and is not difficult to reproduce.
  I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1
  version of mutter.  I just opened two LibreOffice Writer windows side
  by side, and repeatedly selected some text in the left window, copied
  it, then attempted to paste it into the right window.  In my
  experiment, approximately 1 in every 20 paste operations failed: it
  did not paste the text that was just copied, but instead the text that
  was copied before that.

  Now, an error rate of 1 in 20 may not seem so bad.  On the other hand,
  if you spend all day writing a document and copy and paste dozens of
  times during the day, then you may hit this bug multiple times per day
  (as I have been recently), which is a significant annoyance.

  I tested in LibreOffice since that is where I have seen the bug most
  often, but I have also seen it occur in other applications as well.

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

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

[Desktop-packages] [Bug 1876083] Re: chromium snap from focal fails DNS lookups, or delays them (ipv6)

2020-09-29 Thread 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/1876083

Title:
  chromium snap from focal fails DNS lookups, or delays them (ipv6)

Status in snapd:
  Triaged
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  When working with the chromium snap included in focal, it sometimes
  takes a few seconds to lookup an URL, sometimes it cannot resolve the
  hostname of the URL at all.

  Doing the same browsing using firefox doesn't show such behavior, no
  timeouts, no failed lookups, no delays.

  Any way how to debug that?  That is using IPv6 only.

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

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

[Desktop-packages] [Bug 1850282] Re: snap cannot be run while being upgraded − no user feedback

2020-09-29 Thread Zygmunt Krynicki

This is still in development but there's some actual progress recently.
Complete development history is visible in
https://github.com/snapcore/snapd/projects/3

We are aiming to release a, still disabled by default, but much improved
version of this as either 2.47 or 2.48, depending on when the reviews
arrive.

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

Title:
  snap cannot be run while being upgraded − no user feedback

Status in snapd:
  In Progress
Status in chromium-browser package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I've just upgraded to Ubuntu 19.10 with the new snap version of
  Chromium a week or two ago

  On starting my system today, I found that Chromium had disappeared
  from the launcher and wasn't even in the apps list.   using the
  command 'chromium' didn't work either, giving me the message that
  chromium wasn't installed.   "You can install it using snap install
  chromium".  Then when I try to install it, I get the message "chromium
  is already installed".

  After about 10 minutes of digging around, I discovered that the
  chromium snap was disabled.  I couldn't enable it because it was being
  refreshed.

  Come on!  this is unacceptable behaviour for any tool but especially a
  browser which must be one of the most heavily used applications on
  Ubuntu.  This will really hit the reputation of ubuntu with any user
  who has to take maybe more than 10 minutes to discover the problem, or
  may never discover it - Chromium may just mysteriously reappear some
  time later.

  Desired behaviour:   Never disappear.  Allow refresh to happen under the 
covers, transparently (as it used to with apt).
  Minimally acceptable behaviour: never disappear, but display a message 
"chromium is being refreshed.  Please try later".

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
An open-source browser project that aims to build a safer, faster, and more
stable way for all Internet users to experience the web.
  commands:
- chromium.chromedriver
- chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: stable
  channels:
stable:78.0.3904.70 2019-10-29 (920) 160MB -
candidate: 78.0.3904.70 2019-10-29 (920) 160MB -
beta:  78.0.3904.70 2019-10-22 (907) 165MB -
edge:  79.0.3941.4  2019-10-21 (905) 159MB -
  installed:   78.0.3904.70(917) 167MB disabled

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

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

[Desktop-packages] [Bug 1897281] Re: evince suicides in 20.04 but not in 18.04

2020-09-29 Thread buggycub

Following the http://wiki.ubuntu.com/DebuggingProgramCrash, I had teh usual
total computer freeze after starting evince and trying to open the CBR file.
Everything stood still, even the digital clock stopped. Waited 7 minutes. Since
+ did not help, I had to hard-switch off the computer. Here is my
gdb-evince.txt report:
?field.comment=Following the http://wiki.ubuntu.com/DebuggingProgramCrash, I
had teh usual total computer freeze after starting evince and trying to open
the CBR file. Everything stood still, even the digital clock stopped. Waited 7
minutes. Since + did not help, I had to hard-switch off the computer.
Here is my gdb-evince.txt report:

** Attachment added: "gdb-evince bug report"

https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1897281/+attachment/5415282/+files/gdb-evince.txt

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

Title:
evince suicides in 20.04 but not in 18.04

Status in evince package in Ubuntu:
Incomplete

Bug description:
Description: Ubuntu 20.04.1 LTS
Release: 20.04

Evince does a suicide trip after unsuccessfully trying to open a CBR
file. After a while it is killed. Here is my terminal output:

$ evince TheCartoons.cbr
Killed
$

And between the line "$ evince TheCartoons.cbr" and the final
"Killed", are passing many minutes.

Please note that I started my report in
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1785060
not knowing exactly what "expired" there means. I did "apport-collect
1785060" there, too.

Please note also that my error message (see above) is quite different
from seb128 in bug 1785060. In fact, there is no error message just
the statement "Killed".

What gets me is that in 18.04 it is working so smooth and fast and
that in 20.04 it is such a mess!

P.S. I do not know whether this helps, but with Debian 11 Xfce (Buster sid,
testing), evince loads and opens this CBR file correctly, albeit slowly, but
okular (installed in Buster sid) yields a similar error message like that of
seb128 with evince in bug 1785060:
"Could not open file TheCartoons.cbr. The version of unrar on your system is
not suitable for opening comicbooks"
Inverted world ;-)

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

[Desktop-packages] [Bug 1897281] Re: evince suicides in 20.04 but not in 18.04

2020-09-29 Thread buggycub

Would it not be easier for you, if you downloaded this CBR file and
tried to open it in Ubuntu 20.04 yourself? After all, Ubuntu 20.04 and
Debian Buster Xfce pose no problems with this file.

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

Title:
  evince suicides  in 20.04 but not in 18.04

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  Evince does a suicide trip after unsuccessfully trying to open a CBR
  file. After a while it is killed. Here is my terminal output:

  $ evince TheCartoons.cbr
  Killed
  $ 

  And between the line "$ evince TheCartoons.cbr" and the final
  "Killed", are passing many minutes.

  Please note that I started my report in 
  https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1785060
  not knowing exactly what "expired" there means. I did "apport-collect 
1785060" there, too.

  Please note also that my error message (see above) is quite different
  from seb128 in bug 1785060. In fact, there is no error message just
  the statement "Killed".

  What gets me is that in 18.04 it is working so smooth and fast and
  that in 20.04 it is such a mess!

  P.S. I do not know whether this helps, but with Debian 11 Xfce (Buster sid, 
testing), evince loads and opens this CBR file correctly, albeit slowly, but 
okular (installed in Buster sid) yields a similar error message like that of 
seb128 with evince in bug 1785060: 
  "Could not open file TheCartoons.cbr. The version of unrar on your system is 
not suitable for opening comicbooks"
  Inverted world ;-)

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

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

[Desktop-packages] [Bug 1897644] Re: gengal missing from libreoffice-dev in 7.X

2020-09-29 Thread Heather Ellsworth

wonderful thanks!!

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

Title:
  gengal missing from libreoffice-dev in 7.X

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  
  In libreoffice 6.4.6-0ubuntu0.20.04.1, when the libreoffice-dev package is 
installed, we have /usr/lib/libreoffice/program/{gengal, gengal.bin}. However 
for any 7.x version of libreoffice, these gengal files are missing.

  This causes a failure in openclipart, affecting the groovy build:
  https://lists.ubuntu.com/archives/ubuntu-devel/2020-September/041198.html

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

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

[Desktop-packages] [Bug 1883174] Re: Some desktop icons disappear

2020-09-29 Thread John Hoff

@rastersoft-gmail

Sergio, I went back through the merge request in more detail and have
tried these steps :

- Download the patch code from the merge request
- Installed Meson
- Deleted the folder
($HOME/.local/share/gnome-shell/extensions/desktop-icons@csoriano)
- Unzipped the patch and built the patch with Meson/Ninja (it did recreate the
local directory)
- Rebooted
- Went into tweaks and re-enabled the extension

After all this I did not notice any change in behavior. The problem is
very easy to replicate in Ubuntu 20.04. Just place a simple text file
on the desktop. Double click to open it and then change the file. When
you hit save it breaks/hides all the icons and you must reboot or hit
ALT+F2 then R to fix. Let me know if I missed any steps or if there is
anything else I can do to help with the investigation...

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

Title:
Some desktop icons disappear

Status in gnome-shell-extension-desktop-icons:
Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
In Progress

Bug description:
OS: Ubuntu 20.04
GNOME: 3.36.2
Extension: 3.36.2

Sometimes, some icons in my Desktop folder just don't appear on the
desktop. The missing icons aren't invisible, it's like they're not in
the folder. Clicking on the empty space where they should be does
nothing. Mousing over the empty space does nothing. See attached
screenshot. As you can see, there are many missing.

Not consistently reproducible, but frequent.

This isn't great info, I know. Let me know what else I can provide.

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

[Desktop-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

2020-09-29 Thread Philippe

@bjo81 : I'm using AMD Radeon RX 5600 XT (NAVI10 DRM 3.38.0
5.8.9-050809-generic LLVM 10.0.1) v: 4.6 Mesa 20.3.0-devel (git-a3543ad
2020-09-26 focal-oibaf-ppa) and I still have issue. It's worst, no
stairs but whole display broken. I will post a screencast video soon

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

Title:
  Regression: block staircase display with side-by-side monitors of
  different pixel widths

Status in Linux:
  Unknown
Status in libxcb package in Ubuntu:
  Confirmed
Status in xfwm4 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Update based on further research.

  This only happens when the secondary external display is operating at
  a different pixel width to the internal. In this case eDP is 1920x1080
  whereas the external HDMI-A-0 is natively 1680x1050.

  It is caused by xfwm4's recent switch from using glx to xpresent for
  AMD GPUs.

  The underlying bug is in the AMD driver.

  I was able to reproduce on an external 1920x1200 display only when it
  was set to a non-native 1680x1050 resolution.

  ---
  Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred 
initially on the laptop that is having package upgrades applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET32W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NECTO1WW
  dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
  dmi.product.version: ThinkPad E495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-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/linux/+bug/1873895/+subscriptions

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

[Desktop-packages] [Bug 1859308] Re: software-properties-gtk erroneously reports that certain Intel wireless adapter cards are not working

** Tags added: rls-gg-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/1859308

Title:
  software-properties-gtk erroneously reports that certain Intel
  wireless adapter cards are not working

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common source package in Groovy:
  Confirmed

Bug description:
  On Ubuntu 20.04 (development branch), as of today, Additional Drivers
  (software-properties-gtk 0.98.6) reports that the device "Intel
  Corporation: Wireless-AC 9260" is not working, and suggests using a
  manually installed driver (cf. screenshot).

  However the device is working correctly:

    * lsmod | grep iwlwifi, lspci -v, lshw, dmesg | grep iwlwifi all show
  that its driver iwlwifi is in use
    * ls /lib/firmware/*9260* show that the appropriate firmware files
  are present

  And I am indeed writing this bug report connected to an ac (5 GHz)
  wifi network, where I can verify a ~130-160 Mbps download speed, so
  software-properties-gtk shouldn't report the device as not working and
  suggest manually installing a driver. Not sure why it says so?

  EDIT: bug confirmed as affecting the following Intel wireless adapter
  cards, and assumedly more to come:

Intel Wi-Fi 6 AX200
Intel Dual Band Wireless-AC 3165
Intel Dual Band Wireless-AC 7260
Intel Dual Band Wireless-AC 8260
Intel Wireless-AC 9260

  Also for reference here are the specs of Intel adapter cards:

ark.intel.com/content/www/us/en/ark.html#@WirelessNetworking

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.6
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 12 00:53:43 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-12-29 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191226)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 
3.7.5-1ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1897632] Re: Can't see fully Print Dialogue Box in Libre Office

2020-09-29 Thread Heather Ellsworth

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

Dave, it looks like upstream is working on this actively (and it is a
duplicate of the bug you pointed out so thank you). The only ways to
really work around it are to either lower the font scale factor or to
keep your large font but just hit enter to print with the print dialog
up. Sorry those aren't ideal but the upstream work is promising. Good
luck!

** This bug has been marked a duplicate of bug 1883886
Print dialogue's height in Libreoffice Writer is too high to see and click 
buttons.

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

Title:
  Can't see fully Print Dialogue Box in Libre Office

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  I am unsure whether the problem I am suffering is related to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440

  In LibreOffice Version: 6.4.6.2 Build ID: 1:6.4.6-0ubuntu0.20.04.1
  when I try to print a document I cannot see the bottom part of the
  print dialogue window, making it impossible to print. There is no
  scroll bar to scroll down. The More Options, Cancel and OK boxes are
  not visible so I cannot actually print.

  As I have Low Vision I must have Large Text on.

  However, if I switch Large Text off hen I can see(just) the  More
  Options, Cancel and OK boxes at the bottom and can then print.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-core 1:6.4.6-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 28 22:56:02 2020
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2020-04-27 (154 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1897754] [NEW] The icon does not appear in the GNOME bar

2020-09-29 Thread El jinete sin cabeza

Public bug reported:

When upgrading from gnome-shell-extension-appindicator_33-3_all.deb to
gnome-shell-extension-appindicator_34-1_all.deb the icon does not appear
in the GNOME toolbar.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: flameshot 0.8.1-1
Uname: Linux 5.8.12-050812-generic x86_64
ApportVersion: 2.20.11-0ubuntu48
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 29 11:55:57 2020
InstallationDate: Installed on 2020-06-19 (102 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609)
SourcePackage: flameshot
UpgradeStatus: No upgrade log present (probably fresh install)

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

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


** Tags: amd64 apport-bug groovy

** Also affects: gnome-shell-extension-appindicator (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  The icon does not appear in the GNOME bar

Status in flameshot package in Ubuntu:
  New
Status in gnome-shell-extension-appindicator package in Ubuntu:
  New

Bug description:
  When upgrading from gnome-shell-extension-appindicator_33-3_all.deb to
  gnome-shell-extension-appindicator_34-1_all.deb the icon does not
  appear in the GNOME toolbar.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: flameshot 0.8.1-1
  Uname: Linux 5.8.12-050812-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 11:55:57 2020
  InstallationDate: Installed on 2020-06-19 (102 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609)
  SourcePackage: flameshot
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1897754] Re: The icon does not appear in the GNOME bar

2020-09-29 Thread El jinete sin cabeza

** Description changed:

+ https://github.com/flameshot-org/flameshot/issues/1009
+ 
+ ---
+ 
  When upgrading from gnome-shell-extension-appindicator_33-3_all.deb to
  gnome-shell-extension-appindicator_34-1_all.deb the icon does not appear
  in the GNOME toolbar.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: flameshot 0.8.1-1
  Uname: Linux 5.8.12-050812-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 11:55:57 2020
  InstallationDate: Installed on 2020-06-19 (102 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609)
  SourcePackage: flameshot
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  The icon does not appear in the GNOME bar

Status in flameshot package in Ubuntu:
  New
Status in gnome-shell-extension-appindicator package in Ubuntu:
  New

Bug description:
  https://github.com/flameshot-org/flameshot/issues/1009

  ---

  When upgrading from gnome-shell-extension-appindicator_33-3_all.deb to
  gnome-shell-extension-appindicator_34-1_all.deb the icon does not
  appear in the GNOME toolbar.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: flameshot 0.8.1-1
  Uname: Linux 5.8.12-050812-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 11:55:57 2020
  InstallationDate: Installed on 2020-06-19 (102 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609)
  SourcePackage: flameshot
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

2020-09-29 Thread Mauro Gaspari

I tested both Xubuntu 20.04 and Ubuntu MATE 20.04 And I had the very
same issue, however I have a single display, 3440x1440, using AMD RADEON
VII GPU. Kubuntu 20.04 and Ubuntu Budgie 20.04 do not have this issue.

Originally I opened a separate bug but it was marked as duplicate. I
wanted to confirm the same issue is still there. After testing 20.04.1,
making both xubuntu and ubuntu MATE unusable unless compositor is
disabled as suggested in this bug report:
https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1876480

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

Title:
  Regression: block staircase display with side-by-side monitors of
  different pixel widths

Status in Linux:
  Unknown
Status in libxcb package in Ubuntu:
  Confirmed
Status in xfwm4 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Update based on further research.

  This only happens when the secondary external display is operating at
  a different pixel width to the internal. In this case eDP is 1920x1080
  whereas the external HDMI-A-0 is natively 1680x1050.

  It is caused by xfwm4's recent switch from using glx to xpresent for
  AMD GPUs.

  The underlying bug is in the AMD driver.

  I was able to reproduce on an external 1920x1200 display only when it
  was set to a non-native 1680x1050 resolution.

  ---
  Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred 
initially on the laptop that is having package upgrades applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET32W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NECTO1WW
  dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
  dmi.product.version: ThinkPad E495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0

[Desktop-packages] [Bug 1897638] Re: Unable to open gnome-system-settings in 20.04

2020-09-29 Thread anush krishna

Hmm... It worked now I tried installing the gnome-control-center-data
before didn't work . Anyway all good form now thanks

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

Title:
  Unable to open gnome-system-settings in 20.04

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

Bug description:
  Unable to open gnome-system-settings in Ubuntu 20.04

  error message 
  (gnome-control-center:19643): GLib-GIO-ERROR **: 04:14:16.060: Settings 
schema 'org.gnome.ControlCenter' is not installed
  Trace/breakpoint trap (core dumped)
  I have tried almost every fix still didn't get solved

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.4-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 04:17:10 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+bolt-l+X43
  InstallationDate: Installed on 2019-07-17 (439 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1897632] Re: Can't see fully Print Dialogue Box in Libre Office

2020-09-29 Thread Dave Goldsbrough

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

okies, tx Helen

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

Title:
  Can't see fully Print Dialogue Box in Libre Office

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  I am unsure whether the problem I am suffering is related to
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440

  In LibreOffice Version: 6.4.6.2 Build ID: 1:6.4.6-0ubuntu0.20.04.1
  when I try to print a document I cannot see the bottom part of the
  print dialogue window, making it impossible to print. There is no
  scroll bar to scroll down. The More Options, Cancel and OK boxes are
  not visible so I cannot actually print.

  As I have Low Vision I must have Large Text on.

  However, if I switch Large Text off hen I can see(just) the  More
  Options, Cancel and OK boxes at the bottom and can then print.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-core 1:6.4.6-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 28 22:56:02 2020
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2020-04-27 (154 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1897765] [NEW] gnome-shell crashed with signal 5 in g_log_structured_array()

2020-09-29 Thread Timo Aaltonen

Public bug reported:

Launching terminator crashes gnome-shell, happens on two separate
machines.

ProblemType: Crash
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
Uname: Linux 5.8.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu48
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 29 18:05:57 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1600706451
InstallationDate: Installed on 2019-10-14 (350 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /home/tjaalton
ProcEnviron:
 LANG=fi_FI.UTF-8
 PATH=(custom, user)
 SHELL=/bin/zsh
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with signal 5 in g_log_structured_array()
UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:

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


** Tags: amd64 apport-crash groovy third-party-packages

** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with signal 5 in g_log_structured_array()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Launching terminator crashes gnome-shell, happens on two separate
  machines.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 18:05:57 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1600706451
  InstallationDate: Installed on 2019-10-14 (350 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/tjaalton
  ProcEnviron:
   LANG=fi_FI.UTF-8
   PATH=(custom, user)
   SHELL=/bin/zsh
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_structured_array()
  UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log_structured_array()

2020-09-29 Thread Apport retracing service

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5 in g_log_structured_array()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Launching terminator crashes gnome-shell, happens on two separate
  machines.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 18:05:57 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1600706451
  InstallationDate: Installed on 2019-10-14 (350 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/tjaalton
  ProcEnviron:
   LANG=fi_FI.UTF-8
   PATH=(custom, user)
   SHELL=/bin/zsh
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_structured_array()
  UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

I'd prefer to have something more concrete than this regression
potential "please test that the corresponding feature still works fine
with the different configuration values.". Could you add details about
what exactly would be done? For example:

Set Wake on Wireless to off
Send magic packet to the system
Ensure it does not wake up

Set Wake on Wirless to on
Send magic packet to the system
Ensure it does wake up


** Changed in: network-manager (Ubuntu Focal)
   Status: In Progress => Incomplete

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

Title:
  The network manager does not check the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  Invalid
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Focal:
  Incomplete

Bug description:
  [Impact]

   In some cases, the wow is not configured and the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable
  management of wake-on-LAN in NetworkManager).

   The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE 
bit.
   But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
   So, the management of wake-on-LAN still is done by NetworkManager.

   The killer 500s Wi-Fi does not want the network-manger to manager the
  wake-on-LAN so the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set.
  (The driver will manager itself.) When the network-manager managers
  the wake-on-LAN, all of the Wi-Fi functions will be lost after the OS
  resumed from suspend.

  [Test Case]

   On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
   Step 1. Enter suspend (s2idle)
   Setp 2. Resume from suspend

   After resume from suspend, the Wi-Fi function still is normal.

   You can download the kernel and linux-firmware that backport the Qucalcomm's 
dirver fro focal from below link:
   https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633

  [Regression Potential]

   * This patch modifies the wake on lan parameters, please test that
  the corresponding feature still works fine with the different
  configuration values.

  [Other Info]

   * None

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1891632/+subscriptions

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

[Desktop-packages] [Bug 1879183] Re: Cheese does not show preferences/options/menus to non-GNOME Users

Hello Daniel, or anyone else affected,

Accepted cheese into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/cheese/3.34.0-1ubuntu1
in a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: cheese (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed

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

Title:
  Cheese  does not show preferences/options/menus to non-GNOME Users

Status in cheese package in Ubuntu:
  Fix Released
Status in cheese source package in Focal:
  Fix Committed
Status in cheese package in Debian:
  New

Bug description:
  [Impact] 
  Cheese no longer displays its menu button on non-GNOME desktop environments.
  https://gitlab.gnome.org/GNOME/cheese/-/issues/62

  Xubuntu uses cheese as its default camera program. Advanced users can
  still change these settings through dconf-editor, but this is neither
  convenient nor intuitive.

  [Test Case]

  Use the cheese program in Xubuntu/xfce, Kubuntu/KDE or other non-GNOME
  desktop environments. Notice missing menu in titlebar.

  [Regression Potential]

  The most likely regression would be if the patch disabled the menu in
  GNOME. Testing has not shown this to be an issue.

  
  [ORIGINAL REPORT]
  Cheese has removed the GUI method of accessing preferences for non-GNOME 
users.
  
https://github.com/GNOME/cheese/commit/48882da6a6dc4fc1c19e15f5210c9e10feb67ff5#diff-b2b45275b16940829b5f6f068943108d

  I'm not sure if upstream cheese devs care enough to fix it:
  https://gitlab.gnome.org/GNOME/cheese/-/issues/62
  https://gitlab.gnome.org/GNOME/cheese/-/issues/52

  Should Xubuntu default to a different camera program, such as
  guvcview?

  (Partial?) WORKAROUND is to use dconf-editor:
  dconf-editor /org/gnome/cheese

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

-- 
Mailing list: https://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 1891684] Re: [amdgpu] Screen flickers after resuming from suspend

2020-09-29 Thread Ryan

wow ok. i actually have a a acer aspire 5 with a 4500u
i couldnt get ubuntu to boot on it so i abandoned it and re installed
windows.
is there a 20.10 iso available for download?

On Mon, Sep 28, 2020 at 4:01 PM Richard Elkins <1891...@bugs.launchpad.net>
wrote:

> This could very well be an issue with the amdgpu kernel module or the
> kernel itself.  20.04 uses kernel 5.4  I fixed my situation (similar) by
> upgrading to 20.10 (beta) which uses 5.8 packages.  Now, my power
> management and suspend/resume actually work.
>
> My laptop (different than the nitro): Acer Aspire 5 4700U octacore APU
> with built-in graphics.
>
> Good luck.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1891684
>
> Title:
>   [amdgpu] Screen flickers after resuming from suspend
>
> Status in linux package in Ubuntu:
>   Incomplete
> Status in xserver-xorg-video-amdgpu package in Ubuntu:
>   Incomplete
>
> Bug description:
>   when computer is coming out of suspension mode, i get terrible screen
>   flickers. Only way i have worked around this is a reboot.
>
>   This video card is from sapphire
>   Nitro + SE 5700xt
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: xorg 1:7.7+19ubuntu14
>   ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
>   Uname: Linux 5.4.0-42-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.6
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: skip
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Aug 14 12:16:42 2020
>   DistUpgraded: Fresh install
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600
> XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
>  Subsystem: Sapphire Technology Limited Navi 10 [Radeon RX 5600
> OEM/5600 XT / 5700/5700 XT] [1da2:e410]
>   InstallationDate: Installed on 2020-06-08 (66 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   MachineType: System manufacturer System Product Name
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic
> root=UUID=de7b87e0-cf04-4f9f-978e-3646f7e7266d ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 06/17/2020
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 2203
>   dmi.board.asset.tag: Default string
>   dmi.board.name: TUF GAMING X570-PLUS
>   dmi.board.vendor: ASUSTeK COMPUTER INC.
>   dmi.board.version: Rev X.0x
>   dmi.chassis.asset.tag: Default string
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Default string
>   dmi.chassis.version: Default string
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr2203:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
>   dmi.product.family: To be filled by O.E.M.
>   dmi.product.name: System Product Name
>   dmi.product.sku: SKU
>   dmi.product.version: System Version
>   dmi.sys.vendor: System manufacturer
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.101-2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20200226-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/1891684/+subscriptions
>

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

Title:
  [amdgpu] Screen flickers after resuming from suspend

Status in linux package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  when computer is coming out of suspension mode, i get terrible screen
  flickers. Only way i have worked around this is a reboot.

  This video card is from sapphire 
  Nitro + SE 5700xt

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  Compos

[Desktop-packages] [Bug 1897530] Re: The modesetting driver does not gracefully handle missing connectors on EnterVT

2020-09-29 Thread Timo Aaltonen

this is a follow-up for bug 1879893, fixes an issue found in it and
replaces the old commit with what was added upstream

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

Title:
  The modesetting driver does not gracefully handle missing connectors
  on EnterVT

Status in xorg-server package in Ubuntu:
  New
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in xorg-server source package in Bionic:
  Invalid
Status in xorg-server-hwe-18.04 source package in Bionic:
  New
Status in xorg-server source package in Focal:
  New
Status in xorg-server-hwe-18.04 source package in Focal:
  Invalid

Bug description:
  Expectation: on removal of external display during S3, after resume eDP 
rendering should still continue by Nvidia.
  Symptom description: Plug out DP cable when suspension, when resume, X will 
crash.

  1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but 
NV was rendering for eDP.
  2. After S3 entry dock was removed.
  3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails 
resume of TB3 devices and logs confirm that.
  4. X fails to enter VT due to Null meta mode.

  
  To address the explanation, X is not failing to enter the VT due to NVIDIA’s 
NULL MetaMode. It’s the Intel (modesetting) driver that is failing to enter the 
VT. It’s expected that NVIDIA would have a NULL MetaMode, since there are no 
displays connected to it. Our driver is pretty robust to head state changes – 
even if we have to fall back to a NULL MetaMode, we will still enter the VT 
successfully.

  The logs clearly show that the failure is originating from the Intel
  (modesetting) driver, not the NVIDIA driver. The relevant path in X is
  driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes().
  In this function, the Intel driver tries to set a mode on each of the
  previously connected/enabled displays, and it tries to find the
  closest possible mode using xf86OutputFindClosestMode(). This is
  similar to our driver’s functionality, but unlike us, they don’t
  support a NULL fallback. If there are no modes supported on one of the
  displays, it simply fails, which causes X to terminate:

  DisplayModePtr mode = xf86OutputFindClosestMode(output,
  pScrn->currentMode);

  if (!mode)
  return FALSE;

  Since we removed one of the displays via the dock, it fails. It
  doesn’t matter if the internal panel is still available, Intel will
  fail if it can’t re-enable ANY of the previously connected displays.

  Technically the modesetting driver isn’t specifically an Intel driver,
  it’s a generic driver that can be used by any DRM device – it’s just
  that Intel has chosen to use the modesetting driver as their standard
  Linux X driver going forward.

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

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

[Desktop-packages] [Bug 1889152] Re: Introduction of detailed S3 parameters breaks existing AWS setups

2020-09-29 Thread Kenneth Loafman

** Changed in: duplicity
   Status: Fix Committed => Fix Released

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

Title:
  Introduction of detailed S3 parameters breaks existing AWS setups

Status in Duplicity:
  Fix Released
Status in duplicity package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  I just got an update of duplicity via snap to version 0.8.15.

  Running my backup script running duplicity as follows:
  ```
  duplicity incremental 
  --include-filelist backup_include.lst.txt \
  --exclude-filelist backup_exclude.lst.txt \
  --exclude-other-filesystems \
  --exclude-device-files \
  --progress \
  --full-if-older-than 45D \
  $HOME \
  boto3+s3:///
  ```

  ...resulted in the following error:
  ```
  Traceback (innermost last):
    File "/snap/duplicity/111/bin/duplicity", line 104, in 
  with_tempdir(main)
    File "/snap/duplicity/111/bin/duplicity", line 90, in with_tempdir
  fn()
    File 
"/snap/duplicity/111/lib/python3.6/site-packages/duplicity/dup_main.py", line 
1518, in main
  action = commandline.ProcessCommandLine(sys.argv[1:])
    File 
"/snap/duplicity/111/lib/python3.6/site-packages/duplicity/commandline.py", 
line 1200, in ProcessCommandLine
  backup, local_pathname = set_backend(args[0], args[1])
    File 
"/snap/duplicity/111/lib/python3.6/site-packages/duplicity/commandline.py", 
line 1071, in set_backend
  config.backend = backend.get_backend(bend)
    File 
"/snap/duplicity/111/lib/python3.6/site-packages/duplicity/backend.py", line 
223, in get_backend
  obj = get_backend_object(url_string)
    File 
"/snap/duplicity/111/lib/python3.6/site-packages/duplicity/backend.py", line 
209, in get_backend_object
  return factory(pu)
    File 
"/snap/duplicity/111/lib/python3.6/site-packages/duplicity/backends/s3_boto3_backend.py",
 line 85, in __init__
  self.reset_connection()
    File 
"/snap/duplicity/111/lib/python3.6/site-packages/duplicity/backends/s3_boto3_backend.py",
 line 93, in reset_connection
  self.s3 = boto3.resource(u's3', region_name=config.s3_region_name, 
endpoint_url=config.s3_endpoint_url)
   AttributeError: module 'duplicity.config' has no attribute 's3_region_name'
  ```

  *Actual behaviour*
  It seems like the changes introduced via 
https://gitlab.com/duplicity/duplicity/-/merge_requests/19 made the parameters 
`s3-region-name` and `s3-endpoint-url` mandatory, which breaks existing AWS S3 
setups.

  *Expected behaviour*
  These parameters should be optional.

  *Duplicity version*: 0.8.15
  *Python version*: 3.6
  *OS distro and version*: Ubuntu 20.04
  *Target filesystem*: Linux to AWS S3

  Thanks for your work!

  EDIT: Added duplicity command.

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

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

[Desktop-packages] [Bug 1896397] Re: [UIFe] Tweak Arabic font

Hello Gunnar, or anyone else affected,

Accepted language-selector into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/language-
selector/0.204.2 in a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: language-selector (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  [UIFe] Tweak Arabic font

Status in language-selector package in Ubuntu:
  Fix Released
Status in language-selector source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  This is a follow-up of bug #1891733. After the new default font for
  Arabic had made it to focal, we got some additional feedback at
  . After further discussion,
  trial and error, and multiple changes in groovy it has landed in a
  consensus to make these adjustments:

  * Rename the .conf file from 69- to 56-

  * Drop binding="strong"

  * Drop the specification for monospace, and with that fall back
to DejaVu for Arabic monospace

  The significance of the changes, which motivates the proposed SRU, is
  made up of:

  1. Use DejaVu Sans Mono as default Arabic font for monospace
 instead of the previous non-mono font

  2. No longer conflicts with Kubuntu's custom font configuration

  [Test case]

  * Install the language-selector-{gnome,common} packages
from focal-proposed.

  * Open the Language Support tool and install Arabic.

  * Open a terminal window, run the below commands and confirm
that you get the same output:

$ LC_CTYPE=ar_EG.UTF-8 fc-match
NotoSansArabicUI-Regular.ttf: "Noto Sans Arabic UI" "Regular"
$ LC_CTYPE=ar_EG.UTF-8 fc-match monospace
DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"

  [Regression risk]

  For some users this will change the default monospace font for
  rendering Arabic. That's the point. :)

  The change will only affect users with an Arabic locale. The risk that
  other users would be affected by the change is low.

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

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

[Desktop-packages] [Bug 1896919] Re: [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the combo list after selecting the hdmi/dp audio in the g-c-c

Hello Hui, or anyone else affected,

Accepted gnome-control-center into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.36.4-0ubuntu2 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Tags added: verification-needed verification-needed-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/1896919

Title:
  [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the
  combo list after selecting the hdmi/dp audio in the g-c-c

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  Fix Committed
Status in gnome-control-center source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  After we plugging a hdmi/dp monitor with audio capability, we could
  select hdmi audio as output device in the g-c-c, but after we do
  that, the profile combo list will show up in the g-c-c and this combo
  list is empty, it should be stereo-hdmi by default according to 18.04

  [Fix]
  Backport a fix from g-c-c upstream, after applying this patch, the
  combo list update signals will be recevied after the pa finishes the
  changing active profile.

  [Test Case]
  Plug the hdmi/dp monitor with audio capability, then choose hdmi audio
  as active output device from g-c-c, we will find the profile combo list
  has hdmi-steoreo as the default profile. This is same as 18.04.

  [Regression Risk]
  It is possible to make the output and input device can't work after
  applying this patch, that is because the active profile is not set as
  our expected. But this possibility is very low, I tested this patch on
  2 lenovo and 2 dell laptops, there is no regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1896919/+subscriptions

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

[Desktop-packages] [Bug 1887731] Re: gnome-control-center crashes in cc_display_config_manager_get_current -> get_valid_monitors -> get_dock_monitor -> update_dock_placement_combo_selection

Hello errors.ubuntu.com, or anyone else affected,

Accepted gnome-control-center into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.36.4-0ubuntu2 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Tags added: verification-needed verification-needed-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/1887731

Title:
  gnome-control-center crashes in cc_display_config_manager_get_current
  -> get_valid_monitors -> get_dock_monitor ->
  update_dock_placement_combo_selection

Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-control-center source package in Focal:
  Fix Committed

Bug description:
  * Impact

  The appearance settings hit a segfault sometime

  * Test case

  The error reports should stop on
  https://errors.ubuntu.com/problem/3487635236c89796577edeb6ef9f37282267abb8 

  * Regression potential

  Check that that appearance settings still work correctly, including
  configuring on which screen the dock should be displayed

  

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

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

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

[Desktop-packages] [Bug 1873184] Re: Wired and wireless connection details have not enough height and items overlap

Hello Olivier, or anyone else affected,

Accepted gnome-control-center into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.36.4-0ubuntu2 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Tags added: verification-needed verification-needed-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/1873184

Title:
  Wired and wireless connection details have not enough height and items
  overlap

Status in gnome-control-center:
  Unknown
Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Focal:
  Fix Committed
Status in gnome-control-center source package in Groovy:
  Fix Released

Bug description:
  * Impact

  The details of the connection settings sometime overlap

  * Test case

  Connect the computer to a wired ethernet, go to settings and check the
  connection details, the items should be displayed separated and not
  overlapping

  * Regression potential

  Check that the connection details dialog is correctly displayed on
  different typo of connections, the change is in the layout of the
  elements so it could impact the layout in other cases

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

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

[Desktop-packages] [Bug 1873378] Re: gnome-control-center crashed with SIGSEGV in _g_utf8_normalize_wc()

Hello z_killemall, or anyone else affected,

Accepted gnome-control-center into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.36.4-0ubuntu2 in a few hours, and then in the
-proposed repository.

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

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

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

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

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

** Tags added: verification-needed verification-needed-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/1873378

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

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-control-center source package in Focal:
  Fix Committed

Bug description:
  * Impact

  The user panel hits a segfault sometimes

  * Test case

  Check that reports stop on 
  https://errors.ubuntu.com/problem/af55dc0f4cb3abb5f2c5632d1195450e44db98ca

  * Regression potential

  The change is in the user panel's user initial avatar generation,
  check that the default image for profiles without an avatar is still
  generated

  ---

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

  Package version: 1:3.36.1-1ubuntu4

  The application was running in the background, with only Chrome running at 
the same time.
  It's a mid-2014 MacBook Pro, so some drivers are not very stable and can 
cause this kind of issues.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu4
  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: Thu Apr 16 23:41:09 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-08-10 (250 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcCmdline: gnome-control-center
  SegvAnalysis:
   Segfault happened at: 0x7f303176e6e4:movzbl (%r14),%r15d
   PC (0x7f303176e6e4) ok
   source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%r15d" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_utf8_normalize () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   generate_default_avatar ()
   ?? ()
   ?? ()
  Title: gnome-control-center crashed with SIGSEGV in g_utf8_normalize()
  UpgradeStatus: Upgraded to focal on 2020-04-09 (7 days ago)
  UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1887707] Re: Disabling fractional scaling after selecting another integer scaling may unselect user choice

Hello Marco, or anyone else affected,

Accepted gnome-control-center into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.36.4-0ubuntu2 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Tags added: verification-needed verification-needed-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/1887707

Title:
  Disabling fractional scaling after selecting another integer scaling
  may unselect user choice

Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in gnome-control-center source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  If selecting another integer scaling after disabling fractional
  scaling

  [ Test case ]

  When running Ubuntu session under X11, in gnome-control-center, display panel:
   - Ensure 100% scaling is selected and applied
   - Enable fractional scaling
   - Select 200% scaling (or bigger integer scaling)
     - Green "Apply" button should be visible and clickable
   - Deactivate fractional scaling
     - Green "Apply" button stays and fractional scaling isn't disabled until 
applied

  Repeat with inverted scaling orders (applying 200% and then selecting
  100%)

  Currently, once another integer value is selected, we just deselect
  the user choice and restore the previous one, deactivating the
  fractional scaling promtply.

  [ Regression potential ]

  - Displays are wrongly disposed and configured when fractional scaling is 
enabled
  - Configurations are not applicable.

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

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

[Desktop-packages] [Bug 1897784] [NEW] /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::

2020-09-29 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

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


** Tags: focal groovy

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

Title:
  
/usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData

Status in libreoffice package in Ubuntu:
  New

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

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

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

[Desktop-packages] [Bug 1897170] Re: SRU the current 3.36.3 stable update

Hello Sebastien, or anyone else affected,

Accepted file-roller into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/file-
roller/3.36.3-0ubuntu1 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: file-roller (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-focal

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

Title:
  SRU the current 3.36.3 stable update

Status in file-roller package in Ubuntu:
  Fix Released
Status in file-roller source package in Focal:
  Fix Committed

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/file-roller/-/blob/master/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that opening archives of different type still works correctly

  * Regression potential

  The update includes some fixes around drag and drop so that needs some
  extra testing

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

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

[Desktop-packages] [Bug 1894593] Re: Fractional scaling switch doesn't work

2020-09-29 Thread Kai Mast

Any progress on this? Is there an upstream bug report?

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

Title:
  Fractional scaling switch doesn't work

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

Bug description:
  Hitting the “fractional scaling” toggle in the “Screen Display” tab in
  gnome-control-centre page doesn't work - although the toggle changes
  to the “enabled” state there's no visible effect, and if I switch to a
  different page (or close g-c-c) and then switch back (or reopen g-c-c)
  then the toggle is back in the disabled state.

  Running from the command line, I see;
  (gnome-control-center:171131): display-cc-panel-WARNING **: 13:34:19.407: no 
sunset data, using 16.00

  (gnome-control-center:171131): display-cc-panel-WARNING **:
  13:34:19.407: no sunrise data, using 8.00

  (gnome-control-center:171131): display-cc-panel-CRITICAL **:
  13:34:21.972: file ../panels/display/cc-display-config.c: line 452
  (get_fractional_scaling_key): should not be reached

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-control-center 1:3.37.90-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0+bcachefs.git20200701.7e04f345-1-generic 
5.8.4
  Uname: Linux 5.8.0+bcachefs.git20200701.7e04f345-1-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  7 13:34:44 2020
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to groovy on 2020-06-22 (76 days ago)

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

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

[Desktop-packages] [Bug 1897638] Re: Unable to open gnome-system-settings in 20.04

unsure how that happened but it sounds like it was a locally corrupted
installation, closing

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Unable to open gnome-system-settings in 20.04

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

Bug description:
  Unable to open gnome-system-settings in Ubuntu 20.04

  error message 
  (gnome-control-center:19643): GLib-GIO-ERROR **: 04:14:16.060: Settings 
schema 'org.gnome.ControlCenter' is not installed
  Trace/breakpoint trap (core dumped)
  I have tried almost every fix still didn't get solved

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.4-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 29 04:17:10 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+bolt-l+X43
  InstallationDate: Installed on 2019-07-17 (439 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1896825] Re: Mutter 3.28 doesn't compile with mesa 20