date:20210302

Is there a reason you use the word "crash"? If there is any evidence of
a crash then please clarify where it is. It might be helpful to check
for crashes using these instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

Certainly there's a lot of freezing I can see in your log. Some of it
looks like old bug 1867639 and bug 1824855 (which are closed). Please
try uninstalling fingerprint support with:

  sudo apt remove fprintd

then reboot and tell us if the problem reoccurs.


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

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

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

Title:
  gnome-shell freeze

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in libfprint package in Ubuntu:
  Incomplete

Bug description:
  System
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  Description:
  Plugging in USB hub with peripherals while system is running causes gradual 
lag of a visual response, until freezing. usually takes < 1 min.  Only work 
around is to sleep system between plugging in hub.

  I thought I fixed it by change DM but the issue has persisted.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78
  Uname: Linux 5.4.0-64-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 27 14:27:12 2021
  DistUpgraded: 2020-04-28 14:42:33,856 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-62-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-64-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-65-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa]
  InstallationDate: Installed on 2018-12-25 (763 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 2324AS7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic 
root=UUID=957184f1-8feb-4ca9-ac97-3fb70937b4ac ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-04-28 (274 days ago)
  dmi.bios.date: 04/11/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETB2WW (2.72 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324AS7
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB2WW(2.72):bd04/11/2018:svnLENOVO:pn2324AS7:pvrThinkPadX230:rvnLENOVO:rn2324AS7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2324AS7
  dmi.product.sku: LENOVO_MT_2324
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~ppa1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  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
  xserver.bootTime: Tue Nov 24 16:32:27 2020
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.8-2ubuntu2.4
  xserver.video_driver: modeset
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2018-12-25 (792 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78

[Desktop-packages] [Bug 1845163] Re: The cancel button of the paring dialog does not work during pairing a bluetooth keyboard

2021-03-02 Thread Yuan-Chen Cheng

** Tags added: hwe-bluetooth

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

Title:
  The cancel button of the paring dialog does not work during pairing a
  bluetooth keyboard

Status in gnome-control-center:
  Fix Released
Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  The cancel button of the paring dialog does not work during pairing a 
bluetooth keyboard.
  The dialog can be cancel via press the "ESC" on the keyboard.
  But, sometimes after around 1 minute, the gnome-control-center is crashed.

  Reproduce steps:
  1. On bluetooth tab in Settings, click a unpaired bluetooth keyboard
  2. When the pairing XXX dialog show up
  3. click the Cancel button (on the top left of the dialog).

  Expected: the Cancel button is work. And, the pairing is canceled normally.
  Actually: the Cancel button does not work. The pairing action can not be 
canceled via the button.

  Ubuntu: 18.04
  gnome-control-center: 1:3.28.2-0ubuntu0.18.04.3

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

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

[Desktop-packages] [Bug 1912246] Re: [nvidia] gnome-shell freezes randomly after upgrading to groovy

Since you said in comment #18 when it happened again, and your log shows
upstream issue mutter#1516 happened around that time, I am going to
assume that's the problem and will link it to
https://gitlab.gnome.org/GNOME/mutter/-/issues/1516

However, to be sure we're not looking at the wrong problem, please next
time:

1. Confirm the exact time of day the problem occurred; and

2. Check for crashes using these instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

** No longer affects: gnome-shell-extension-ubuntu-dock (Ubuntu)

** Summary changed:

- [nvidia] gnome-shell freezes randomly after upgrading to groovy
+ [nvidia] gnome-shell freezes randomly

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1516
   Importance: Unknown
   Status: Unknown

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

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

Title:
  [nvidia] gnome-shell freezes randomly

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I recently upgrading from Focal to Groovy, and use proprietary NVIDIA
  drivers with X11 with otherwise standard GNOME, but some extensions
  installed. I see frequently errors relating to the dash-to-dock
  extension which I'm not sure are related, but I also see that gnome-
  shell freezes up for a minute or so, and the logs have this to say:
  https://pastebin.ubuntu.com/p/trWJZfZ77Z/

  BTW this is the error from the dash-to-dock extension if relevant:

  Jan 18 07:50:24 gnome-shell[10186]: == Stack trace for context 0x565369c02220 
==
  Jan 18 07:50:24 gnome-shell[10186]: #0   7ffc8e0a3c00 I   
/home/ijohnson/.local/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:2036
 (e02dce21a0 @ 208)
  Jan 18 07:50:24 gnome-shell[10186]: Object St.Bin (0x56537221ac80), has been 
already deallocated — impossible to set any property on it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.

  however that seems to be an issue reported upstream at
  https://github.com/micheleg/dash-to-dock/issues/1360

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.1-1ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 18 09:51:15 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-05 (563 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to groovy on 2021-01-16 (2 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-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 resized with the mouse (Xorg sessions)

Nevermind. I do still experience this in Chrome on 20.04 at least.

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

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

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

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

Status in GNOME Shell:
  Unknown
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server 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.

  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/gnome-shell/+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 1896627] Re: Windows flicker when being resized with the mouse (Xorg sessions)

Thanks for the update. If the bug can't be confirmed by anyone again in
the next 60 days then it will close automatically...

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

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

** No longer affects: mutter

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

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

Status in GNOME Shell:
  Unknown
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server 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.

  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/gnome-shell/+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 1905969] Re: Asus Zephyrus G14 microphone not works

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

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

** Summary changed:

- Asus Zephyrus G14 microphone not works
+ Asus Zephyrus G14 microphone does not work in kernel 5.9.8, but does in 5.10.9

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

Title:
  Asus Zephyrus G14 microphone does not work in kernel 5.9.8, but does
  in 5.10.9

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  I got an Asus Zephyrus G14 GA401IH-HE003 with AMD Ryzen 7 4800HS and a NVIDIA 
GeForce GTX 1650.
  I am use 5.9.8-050908-generic kernel from 
(kernel.ubuntu.com/~kernel-ppa/mainline/v5.9.8/)

  dmamchyts@ga401ih:~$ cat /etc/os-release
  NAME="Ubuntu"
  VERSION="20.10 (Groovy Gorilla)"

  I have some problem with notebook microphone.
  When I use headphones via 3.5 jack - all works fine.
  But without headphones - system doesn't see any microphone device in settings.
  I am using KDE

  
dmamchyts@ga401ih:/sys/class/hwmon/hwmon6$ aplay -l
 List of PLAYBACK Hardware Devices 
card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: Generic_1 [HD-Audio Generic], device 0: ALC289 Analog [ALC289 
Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

  
  Also, I try to report issue into kernel team (they help me to fix issue with 
speakers), you can find some into it: 
https://bugzilla.kernel.org/show_bug.cgi?id=210359

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  Uname: Linux 5.9.8-050908-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Nov 27 17:13:59 2020
  InstallationDate: Installed on 2020-11-10 (17 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   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: 11/05/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GA401IH.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GA401IH
  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.ec.firmware.release: 3.13
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGA401IH.210:bd11/05/2020:br5.16:efr3.13:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA401IH_GA401IH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA401IH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG Zephyrus G14
  dmi.product.name: ROG Zephyrus G14 GA401IH_GA401IH
  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/linux/+bug/1905969/+subscriptions

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

[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)

This bug is closed. If you experience any problems at all still then
please open a new bug by running:

  ubuntu-bug mutter

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

Title:
  Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
  on Nvidia)

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

Bug description:
  [ Impact ]

  GNOME Shell starts with a wrong text size

  
  [ Test case ]

  In a terminal run:
- Xephyr :2

  In another one:
- env DISPLAY=:2 dbus-run-session gnome-shell --x11

  The shell should run in the embedded window, with the correct text
  size, running it again (without closing Xephyr window, but stopping
  the shell execution) should not bigger than expected.

  -- Other test case (hw dependant)

  - Login, ensure that the Shell text size matches the configured one.

  
  [ Regression potential ]

  Initial UI scaling when fractional scaling is enabled is wrong.

  
  [ Workaround ]

  Run on startup:
   - gsettings set org.gnome.desktop.interface scaling-factor \
   $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' 
-f2)

  
  ---

  See also bug 1892521.

  The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04
  causes small text in GNOME Shell menu with  NVIDIA cards.

  With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem 
is after update to the (3.36.4-0ubuntu0.20.04.2).
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.36.4-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  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
  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

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

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

[Desktop-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

This bug is closed. If you continue to experience any problems then
please open a new bug by running:

ubuntu-bug pulseaudio

--
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 Released
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 1905168] Re: PipeWire conflicts with PulseAudio and hides audio devices

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

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 1897965, 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.


** This bug has been marked a duplicate of bug 1897965
   PulseAudio doesn't work when pipewire is installed (ie. KDE)

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

Title:
  PipeWire conflicts with PulseAudio and hides audio devices

Status in pipewire package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Kubuntu 20.04 to 20.10, PipeWire gets installed
  and started along with PulseAudio. As a result, upon system startup
  some audio output and input devices are not visible in PulseAudio. For
  example, a Builtin audio device might not have analog output or duplex
  modes - only digital output. Another audio device might not have 5.1
  analog output + analog stereo input mode, but have other modes (e.g.
  stereo duplex or digital output). This may not happen the same way
  every time - on some start ups some of the devices may be fully
  visible in PulseAudio, on others - not.

  Presumably, PulseAudio cannot access these devices fully because
  PipeWire grabs these devices on startup.

  The problem is solved if pipewire and dependent packages are purged
  from system.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pipewire (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-29.31-lowlatency 5.8.14
  Uname: Linux 5.8.0-29-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun Nov 22 15:06:10 2020
  InstallationDate: Installed on 2015-05-01 (2031 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to groovy on 2020-11-22 (0 days ago)

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

-- 
Mailing list: https://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 1917191] Re: firefox will not start after it crashed unexpectedly

2021-03-02 Thread John F. Godfrey

Is there a bug fix out there?

On Tue, Mar 2, 2021, 8:10 PM Bug Watch Updater <1917...@bugs.launchpad.net>
wrote:

> Launchpad has imported 13 comments from the remote bug at
> https://bugzilla.mozilla.org/show_bug.cgi?id=1694670.
>
> If you reply to an imported comment from within Launchpad, your comment
> will be sent to the remote bug automatically. Read more about
> Launchpad's inter-bugtracker facilities at
> https://help.launchpad.net/InterBugTracking.
>
> 
> On 2021-02-24T14:51:58+00:00 Aryx-bugmail wrote:
>
> 90 crashes with various Linux distributions in the last 6 weeks, some
> have beta 0 as version (distros testing?).
>
> Crash report: https://crash-stats.mozilla.org/report/index/2a7dee73
> -3a4d-490a-96fd-4af7f0210224
> 
>
> MOZ_CRASH Reason: ```OOB```
>
> Top 10 frames of crashing thread:
> ```
> 0 libxul.so RustMozCrash mozglue/static/rust/wrappers.cpp:17
> 1 libxul.so mozglue_static::panic_hook mozglue/static/rust/lib.rs:89
> 2 libxul.so core::ops::function::Fn::call
> /builds/worker/fetches/rustc/lib/rustlib/src/rust/library/core/src/ops/
> function.rs:70
> 3 libxul.so std::panicking::rust_panic_with_hook library/std/src/
> panicking.rs:595
> 4 libxul.so std::panicking::begin_panic::{{closure}}
> /builds/worker/fetches/rustc/lib/rustlib/src/rust/library/std/src/
> panicking.rs:520
> 5 libxul.so std::sys_common::backtrace::__rust_end_short_backtrace
> /builds/worker/fetches/rustc/lib/rustlib/src/rust/library/std/src/sys_common/
> backtrace.rs:141
> 6 libxul.so std::panicking::begin_panic
> /builds/worker/fetches/rustc/lib/rustlib/src/rust/library/std/src/
> panicking.rs:519
> 7 libxul.so qcms_data_create_rgb_with_gamma gfx/qcms/src/c_bindings.rs:287
> 8 libxul.so gfxPlatformGtk::GetPlatformCMSOutputProfileData
> gfx/thebes/gfxPlatformGtk.cpp:483
> 9 libxul.so gfxPlatform::Init gfx/thebes/gfxPlatform.cpp:1005
> ```
>
> Reply at:
> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917191/comments/0
>
> 
> On 2021-02-24T14:55:19+00:00 Jmuizelaar wrote:
>
> It doesn't seem like this should be a security bug as it is just a rust
> panic on startup.
>
> Reply at:
> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917191/comments/1
>
> 
> On 2021-02-24T15:37:38+00:00 Jmuizelaar wrote:
>
> Created attachment 9205116
> Bug 1694670 - Fix qcms_data_create_rgb_with_gamma.
>
> This fixes a number of problems:
>
> 1. The check around get_rgb_colorants was inverted. This caused us to
>only continue if the colorants were wrong.
>
> 2. get_rgb_colorants can just return the Matrix instead of taking
>a reference to it.
>
> 3. The OOBs checks in write_u32 and write_u16 had their conditions
>inverted.
>
> 4. No tests
>
> Reply at:
> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917191/comments/2
>
> 
> On 2021-02-24T15:42:48+00:00 Jmuizelaar wrote:
>
> We should just fix the reversed OOB checks here and do the other stuff
> elsewhere.
>
> Reply at:
> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917191/comments/3
>
> 
> On 2021-02-24T22:16:13+00:00 Dveditz wrote:
>
> So these particular crashes may not be scary, but
> `qcms_data_create_rgb_with_gamma` is a very large unsafe function so are
> we sure there aren't potentially vulnerable crashes if we've reversed
> the conditions?
>
> Reply at:
> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917191/comments/4
>
> 
> On 2021-02-25T02:03:23+00:00 Jmuizelaar wrote:
>
> `qcms_data_create_rgb_with_gamma` is only called on system local data
> (i.e information from the user's window server). There shouldn't be any
> way to exploit it. Further, the out of bounds checks were only added
> recently, previously there was no check at all.
>
> Reply at:
> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917191/comments/5
>
> 
> On 2021-02-25T02:03:52+00:00 Jmuizelaar wrote:
>
> Created attachment 9205268
> Bug 1694670. Fix the OOB check in write_u32/u16.
>
> Reply at:
> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917191/comments/6
>
> 
> On 2021-02-25T13:21:29+00:00 Jmuizelaar wrote:
>
> Comment on attachment 9205268
> Bug 1694670. Fix the OOB check in write_u32/u16.
>
> ### Beta/Release Uplift Approval Request
> * **User impact if declined**: This fixes a startup crash that happens
> when users have an invalid color profile on Linux
> * **Is this code

[Desktop-packages] [Bug 1917554] Re: VGA driver not available for download

2021-03-02 Thread Chris Guiver

If you believe I'm in error, please leave a comment as to why, and you
can change the status back to "New".

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

Title:
  VGA driver not available for download

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  as VGA driver not available for download for dell latitude 3410 please
  help me to install VGA driver for the same laptop

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Wed Mar  3 08:24:57 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics [1028:09ec]
  InstallationDate: Installed on 2021-03-02 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. 
FingerPrint
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3410
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=46ff8419-3c77-44f1-833c-0dbf4a00389b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2020
  dmi.bios.release: 1.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0J6VTW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd07/17/2020:br1.3:svnDellInc.:pnLatitude3410:pvr:rvnDellInc.:rn0J6VTW:rvrA03:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3410
  dmi.product.sku: 09EC
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  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/+bug/1917554/+subscriptions

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

[Desktop-packages] [Bug 1917554] Re: VGA driver not available for download

2021-03-02 Thread Chris Guiver

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

Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.

I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org, or for more support options please look at
https://discourse.ubuntu.com/t/community-support/709

I'm marking this bug incomplete, as it appears to be a support request,
and not a bug report.

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

Title:
  VGA driver not available for download

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  as VGA driver not available for download for dell latitude 3410 please
  help me to install VGA driver for the same laptop

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Wed Mar  3 08:24:57 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics [1028:09ec]
  InstallationDate: Installed on 2021-03-02 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. 
FingerPrint
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3410
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=46ff8419-3c77-44f1-833c-0dbf4a00389b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2020
  dmi.bios.release: 1.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0J6VTW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd07/17/2020:br1.3:svnDellInc.:pnLatitude3410:pvr:rvnDellInc.:rn0J6VTW:rvrA03:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3410
  dmi.product.sku: 09EC
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  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/+bug/1917554/+subscriptions

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

[Desktop-packages] [Bug 1917191] Re: firefox will not start after it crashed unexpectedly

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

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


On 2021-02-24T14:51:58+00:00 Aryx-bugmail wrote:

90 crashes with various Linux distributions in the last 6 weeks, some
have beta 0 as version (distros testing?).

Crash report: https://crash-stats.mozilla.org/report/index/2a7dee73
-3a4d-490a-96fd-4af7f0210224

MOZ_CRASH Reason: ```OOB```

Top 10 frames of crashing thread:
```
0 libxul.so RustMozCrash mozglue/static/rust/wrappers.cpp:17
1 libxul.so mozglue_static::panic_hook mozglue/static/rust/lib.rs:89
2 libxul.so core::ops::function::Fn::call 
/builds/worker/fetches/rustc/lib/rustlib/src/rust/library/core/src/ops/function.rs:70
3 libxul.so std::panicking::rust_panic_with_hook 
library/std/src/panicking.rs:595
4 libxul.so std::panicking::begin_panic::{{closure}} 
/builds/worker/fetches/rustc/lib/rustlib/src/rust/library/std/src/panicking.rs:520
5 libxul.so std::sys_common::backtrace::__rust_end_short_backtrace 
/builds/worker/fetches/rustc/lib/rustlib/src/rust/library/std/src/sys_common/backtrace.rs:141
6 libxul.so std::panicking::begin_panic 
/builds/worker/fetches/rustc/lib/rustlib/src/rust/library/std/src/panicking.rs:519
7 libxul.so qcms_data_create_rgb_with_gamma gfx/qcms/src/c_bindings.rs:287
8 libxul.so gfxPlatformGtk::GetPlatformCMSOutputProfileData 
gfx/thebes/gfxPlatformGtk.cpp:483
9 libxul.so gfxPlatform::Init gfx/thebes/gfxPlatform.cpp:1005
```

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917191/comments/0


On 2021-02-24T14:55:19+00:00 Jmuizelaar wrote:

It doesn't seem like this should be a security bug as it is just a rust
panic on startup.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917191/comments/1


On 2021-02-24T15:37:38+00:00 Jmuizelaar wrote:

Created attachment 9205116
Bug 1694670 - Fix qcms_data_create_rgb_with_gamma.

This fixes a number of problems:

1. The check around get_rgb_colorants was inverted. This caused us to
   only continue if the colorants were wrong.

2. get_rgb_colorants can just return the Matrix instead of taking
   a reference to it.

3. The OOBs checks in write_u32 and write_u16 had their conditions
   inverted.

4. No tests

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917191/comments/2


On 2021-02-24T15:42:48+00:00 Jmuizelaar wrote:

We should just fix the reversed OOB checks here and do the other stuff
elsewhere.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917191/comments/3


On 2021-02-24T22:16:13+00:00 Dveditz wrote:

So these particular crashes may not be scary, but
`qcms_data_create_rgb_with_gamma` is a very large unsafe function so are
we sure there aren't potentially vulnerable crashes if we've reversed
the conditions?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917191/comments/4


On 2021-02-25T02:03:23+00:00 Jmuizelaar wrote:

`qcms_data_create_rgb_with_gamma` is only called on system local data
(i.e information from the user's window server). There shouldn't be any
way to exploit it. Further, the out of bounds checks were only added
recently, previously there was no check at all.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917191/comments/5


On 2021-02-25T02:03:52+00:00 Jmuizelaar wrote:

Created attachment 9205268
Bug 1694670. Fix the OOB check in write_u32/u16.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917191/comments/6


On 2021-02-25T13:21:29+00:00 Jmuizelaar wrote:

Comment on attachment 9205268
Bug 1694670. Fix the OOB check in write_u32/u16.

### Beta/Release Uplift Approval Request
* **User impact if declined**: This fixes a startup crash that happens when 
users have an invalid color profile on Linux
* **Is this code covered by automated tests?**: No
* **Has the fix been verified in Nightly?**: No
* **Needs manual test from QE?**: No
* **If yes, steps to reproduce**: 
* **List of other uplifts needed**: None
* **Risk to taking this patch**: Low
* **Why is the change risky/not risky? (and alternatives if risky)**: This code 
path is very rare as evidenced by the low crash rate. This patch restores the 
behaviour to what it was prior to

[Desktop-packages] [Bug 1917554] [NEW] VGA driver not available for download

2021-03-02 Thread sanket

Public bug reported:

as VGA driver not available for download for dell latitude 3410 please
help me to install VGA driver for the same laptop

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Wed Mar  3 08:24:57 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics [1028:09ec]
InstallationDate: Installed on 2021-03-02 (0 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
 Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. 
FingerPrint
 Bus 001 Device 004: ID 8087:0026 Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude 3410
ProcEnviron:
 LANGUAGE=en_IN:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=46ff8419-3c77-44f1-833c-0dbf4a00389b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/17/2020
dmi.bios.release: 1.3
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.0
dmi.board.name: 0J6VTW
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd07/17/2020:br1.3:svnDellInc.:pnLatitude3410:pvr:rvnDellInc.:rn0J6VTW:rvrA03:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 3410
dmi.product.sku: 09EC
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
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

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


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

Title:
  VGA driver not available for download

Status in xorg package in Ubuntu:
  New

Bug description:
  as VGA driver not available for download for dell latitude 3410 please
  help me to install VGA driver for the same laptop

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Wed Mar  3 08:24:57 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics [1028:09ec]
  InstallationDate: Installed on 2021-03-02 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 002: ID 27c6:538d Shenzhen Goodix Technology Co.,Ltd. 
FingerPrint
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3410
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=46ff8419-3c77-44f1-833c-0dbf4a00389b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2020
  dmi.bios.release: 1.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0J6VTW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd07/17/2020:br1.3:svnDellInc.:pnLatitude3410:pvr:rvnDellInc.:rn0J6VTW:rvrA03:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3410
  dmi.product.sku:

[Desktop-packages] [Bug 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context

glib2.0 (2.67.5-1) experimental; urgency=medium


** Changed in: glib2.0 (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  glib2.0 >=2.67.3 breaks include from an extern C context

Status in glib2.0 package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Triaged
Status in ukui-control-center package in Ubuntu:
  New

Bug description:
  qemu now breaks in Hirsute (it didn't 23h ago)
  Broken:
  
https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz

  Good before:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages

  Error:

  ../../disas/arm-a64.cc
  In file included from /usr/include/glib-2.0/glib/gmacros.h:241,
   from 
/usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9,
   from /usr/include/glib-2.0/glib/gtypes.h:32,
   from /usr/include/glib-2.0/glib/galloca.h:32,
   from /usr/include/glib-2.0/glib.h:30,
   from /<>/qemu-5.2+dfsg/include/glib-compat.h:32,
   from /<>/qemu-5.2+dfsg/include/qemu/osdep.h:126,
   from ../../disas/arm-a64.cc:21:
  /usr/include/c++/10/type_traits:56:3: error: template with C linkage
     56 |   template
    |   ^~~~
  ../../disas/arm-a64.cc:20:1: note: ‘extern "C"’ linkage started here
     20 | extern "C" {
    | ^~

  Also in disas/nanomips.cpp, ...

  And indeed disas/arm-a64.cc has:
   20 extern "C" {
   21 #include "qemu/osdep.h"
   22 #include "disas/dis-asm.h"
   23 }

  Through the chain of headers as reported above this gets to the templates
  in /usr/include/c++/10/type_traits which fails due to that.

  So C++ constructs within a C scope which is this bug.

  Upstream qemu has not recently changed yet for this.
  The code is the same since 2016 via commit e78490c44: "disas/arm-a64.cc:
  Include osdep.h first" by Peter Maydell.

  But what was different before to break it now?
  To find that I was comparing Hirsute vs Hirsute-proposed ...

  It is indeed failing in -proposed but working in hirsute-release.

  10.2.1-20ubuntu1 : bad

  repro in broken build:
  $ cd /root/qemu-5.2+dfsg/b/qemu
  $ c++ -Ilibcommon.fa.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader 
-I/usr/include/pixman-1 -I/usr/include/virgl -I/usr/include/libpng16 
-I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/libusb-1.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/cacard -I/usr/include/nss -I/usr/include/nspr 
-I/usr/include/PCSC -I/usr/include/slirp -fdiagnostics-color=auto -pipe -Wall 
-Winvalid-pch -Wnon-virtual-dtor -std=gnu++11 -O2 -g -D__STDC_LIMIT_MACROS 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -U_FORTIFY_SOURCE -m64 -mcx16 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef 
-Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -g -O2 
-ffile-prefix-map=/root/qemu-5.2+dfsg=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits 
-Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body 
-Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs 
-Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem 
/root/qemu-5.2+dfsg/linux-headers -isystem linux-headers -iquote 
/root/qemu-5.2+dfsg/tcg/i386 -iquote . -iquote /root/qemu-5.2+dfsg -iquote 
/root/qemu-5.2+dfsg/accel/tcg -iquote /root/qemu-5.2+dfsg/include -iquote 
/root/qemu-5.2+dfsg/disas/libvixl -pthread -fPIE -DSTRUCT_IOVEC_DEFINED 
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ 
libcommon.fa.p/disas_nanomips.cpp.o -MF libcommon.fa.p/disas_nanomips.cpp.o.d 
-o libcommon.fa.p/disas_nanomips.cpp.o -c ../../disas/nanomips.cpp

  With that I have a test env...

  Doko asked me to test
  
https://launchpad.net/ubuntu/+source/gcc-10/10.2.1-19ubuntu1/+build/20995220/+files/g++-10_10.2.1-19ubuntu1_amd64.deb
  That fails as well, but also good as well as bad case have 10.10.2.1-20ubuntu1
  It must be something else.

  The difference were ~340 packages I was upgrading them to spot what broke it.
  I eventually found glib 2.66 -> 2.67 to break it.

  libglib2.0-0/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
  libglib2.0-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
  libglib2.0-data/hirsute-proposed 2.67.4-1 all [upgradable from: 2.66.4-1]
  libglib2.0-dev-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
  libglib2.0-dev/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]

  Old:
  /*
   * We can only use __typeof__ on GCC >= 4.8, and not when compiling C++. Since
   * __typeof__ is used in a few places in GLib,

[Desktop-packages] [Bug 1887652] Re: Wayland not available with proprietary Nvidia drivers even when nvidia-drm.modeset=1 is set

The rule to disable Wayland support on Nvidia is important right now,
because it prevents bug 1705369 which hurt a lot of users. Although I
have made an attempt to fix that properly (comment #3), upstream did not
like it and currently prefers using 61-gdm.rules.

I'm hopeful a magical solution to this issue will appear in driver
version 470 but have no evidence to support that. More likely I think I
will need to revisit or patch
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/625

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

Title:
  Wayland not available with proprietary Nvidia drivers even when
  nvidia-drm.modeset=1 is set

Status in gdm3 package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  With Ubuntu 20.04, GDM 3.34.1 (bundled with Focal), and the
  proprietary NVIDIA drivers, I am unable to use Wayland to login, and
  can only use XOrg. Debugging this a little, I found that wayland
  support is wholesale disabled when proprietary NVIDIA drivers are used
  by this rule: /lib/udev/rules.d/61-gdm.rules (coming from the gdm3
  package), however it seems there may be more to this as well in
  upstream so this seems to affect mutter as well.

  To be clear, my system only has NVIDIA graphics, I do not also have an
  Intel integrated GPU, so this is not a duplicate of
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862531.

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

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

[Desktop-packages] [Bug 1911921] Re: auto-move-windows extension crashes gnome-shell with SIGABRT in src/core/workspace.c:375:meta_workspace_add_window: assertion failed: (g_list_find (workspace->mru_

This bug is still missing SRU information.

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

Title:
  auto-move-windows extension crashes gnome-shell with SIGABRT in
  src/core/workspace.c:375:meta_workspace_add_window: assertion failed:
  (g_list_find (workspace->mru_list, window) == NULL)

Status in Mutter:
  Unknown
Status in gnome-shell-extensions package in Ubuntu:
  Fix Committed
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/issues/97
  https://gitlab.gnome.org/GNOME/mutter/-/issues/992

  ---

  As in bug 1864052, putting a Chrome video into PiP mode crashes gnome-
  shell, although this time, in a different location.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.10.0-12.13-generic 5.10.6
  Uname: Linux 5.10.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Fri Jan 15 16:04:30 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-03-14 (1037 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libmutter-7.so.0
   () at /lib/x86_64-linux-gnu/libmutter-7.so.0
   meta_window_stick () at /lib/x86_64-linux-gnu/libmutter-7.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild 
sudo
  separator:

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

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

[Desktop-packages] [Bug 1865838] Re: no error displayed on failed fingerprint authentication

Hello Alex, or anyone else affected,

Accepted gnome-shell into groovy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.38.3-2ubuntu0.20.10.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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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-shell (Ubuntu Groovy)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-groovy

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

Title:
  no error displayed on failed fingerprint authentication

Status in gdm:
  New
Status in OEM Priority Project:
  New
Status in fprintd package in Ubuntu:
  Triaged
Status in gdm package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in fprintd source package in Focal:
  Triaged
Status in gdm source package in Focal:
  New
Status in gnome-shell source package in Focal:
  In Progress
Status in gnome-shell source package in Groovy:
  Fix Committed

Bug description:
  [ Impact ]

  No fingerprint errors are exposed on fingerprint login failures.

  from journalctl, gdm-fingerprint shows error there after retried 5
  times of fingerprint login failed, so I open this issue here.

  
  [ Test case ]

  1. enroll fingerprint for your right index finger.
  2. logout
  3. login and try login by incorrect finger e.g. middle finger
  4. Each time the wrong finger is used an error is shown
  5. After 3 times retries, an authentication error is shown, suggesting
 to use another method.

  [ Regression potential]

  Wrong errors are shown during both fingerprint auth and other kinds of 
authentications.
  Password failures aren't properly exposed. Verification can't restart on 
error.

  ---

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.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
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  3 15:32:00 2020
  InstallationDate: Installed on 2020-03-02 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200301)SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1915066] Re: Authentication is cancelled (and immediately restarted) hitting Escape causing fingerprint to stop working and multiple stale gdm working

Hello Marco, or anyone else affected,

Accepted gnome-shell into groovy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.38.3-2ubuntu0.20.10.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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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-shell (Ubuntu Groovy)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-groovy

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

Title:
  Authentication is cancelled (and immediately restarted) hitting Escape
  causing fingerprint to stop working and multiple stale gdm working

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

Bug description:
  [ Test case ]

  In the user session lockscreen (gdm login screen is fine):

  - Lock the screen
  - Hit Enter
  - Hit Escape
  - Repeat

  Checking watch -n1 "ps aux |grep gdm-session-worker" (or just ps'ing
  after unlocked) gdm workers should not be running (a part the one used
  for logging in).

  Fingerprint unlocking is particularly hit by this as the service may
  prevent further authentication to happen until the PAM module times
  out.

  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3654

  [ Regression potential ]

  Authenticating at login screen or at unlock screen stops working after
  wrong credentials have been used once or the request has been
  cancelled via escape key.

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

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

[Desktop-packages] [Bug 1910235] Re: The mouse stops working after trying to take an area screenshot in some apps on Xorg

Hello Andrey, or anyone else affected,

Accepted gnome-shell into groovy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.38.3-2ubuntu0.20.10.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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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-shell (Ubuntu Groovy)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-groovy

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

Title:
  The mouse stops working after trying to take an area screenshot in
  some apps on Xorg

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

Bug description:
  [ Impact ]

  Mouse stops working after taking an area screenshot

  [ Test case ]

  1. Open Chromium browser.
  2. Go to the page with the form in which there is a standard browser 
drop-down menu (form select)
  3. Open it
  4. Try to take a screenshot with the keyboard shortcut: Ctrl+Shift+PrintScreen
  5. Try to switch between applications using the panel and check the operation 
of the mousein other applications besides browser (in my case Slack)

  [ Regression potential ]

  Grab events don't happen or pointer isn't ungrabbed when required.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-10-26 (71 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-58-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1915089] Re: Update to 3.38.3 and SRU it

Hello Marco, or anyone else affected,

Accepted gnome-shell into groovy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.38.3-2ubuntu0.20.10.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-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. 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-shell (Ubuntu Groovy)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-groovy

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

Title:
  Update to 3.38.3 and SRU it

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

Bug description:
  [ Impact ]

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

  [ Test case ]

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

  GNOME Shell and its components should continue working

  Ideally the verification should include checking those extensions before and 
after the update to ensure the SRU isn't creating regressions
  https://launchpadlibrarian.net/511426552/gse

  [ Regression potential ]

  Icon grid behavior has some changes reverted which may lead to slight 
difference in look.
  Workspace switch fixes have been included, so workspace behavior should be 
checked.

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

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

[Desktop-packages] [Bug 1885344] Re: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build (oem 5.6 kernel)

2021-03-02 Thread stergios papathanasiou

Thank you Page (repager) ,
 I have also switched to x.org X SERVER -Nouveau display driver.
Now the system ;is booting from the new kernel 5.8 and I do not'  need to boot 
from the old kernel as i did for 3 days.

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

Title:
  nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build
  (oem 5.6 kernel)

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

Bug description:
  Nvidia kernel module fails to build with linux kernel 5.6.0. Exits
  with error code 2.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  linux-image-unsigned-5.6.0-1018-oem:
Installed: 5.6.0-1018.18
Candidate: 5.6.0-1018.18
Version table:
   *** 5.6.0-1018.18 500
  500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 340.108-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  DKMSKernelVersion: 5.6.0-1018-oem
  Date: Sat Jun 27 02:15:51 2020
  DuplicateSignature: 
dkms:nvidia-340:340.108-0ubuntu2:/var/lib/dkms/nvidia-340/340.108/build/nv-drm.c:54:25:
 error: implicit declaration of function ‘drm_pci_init’; did you mean 
‘drm_mm_init’? [-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2020-04-24 (63 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageVersion: 340.108-0ubuntu2
  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.3
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1893738] Re: libwayland-dev missing dependency on libffi-dev

** Changed in: wayland (Debian)
   Status: Unknown => Fix Released

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

Title:
  libwayland-dev missing dependency on libffi-dev

Status in wayland package in Ubuntu:
  Fix Released
Status in wayland package in Debian:
  Fix Released

Bug description:
  The version of wayland-client.pc in groovy has a Requires.private:
  libffi, which means “pkg-config --static --libs wayland-client”
  requires libffi.pc to be installed, but libwayland-dev does not depend
  on libffi-dev.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: libwayland-dev 1.18.0-2~exp1build2
  ProcVersionSignature: Ubuntu 5.7.0+bcachefs.git20200813.86fa1258-1-generic 
5.7.10
  Uname: Linux 5.7.0+bcachefs.git20200813.86fa1258-1-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Sep  1 07:01:09 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: wayland
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC

2021-03-02 Thread Balint Reczey

@stgraber Thank you. I'm including the originally proposed patch in the
next systemd upload and will switch to v248 when it is out to include
the full fix. Most likely final v248 will be out in a few weeks.


** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Balint Reczey (rbalint)

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

Title:
  NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start
  in LXC

Status in lxd package in Ubuntu:
  Won't Fix
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  This regresses systemd's autopkgtest because it expects the system in
  the container to reach running state, but the system ends up in
  degraded state due to the service failing.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz
  ...

  ==
  FAIL: test_no_failed (__main__.ServicesTest)
  No failed units
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", 
line 68, in test_no_failed
  self.assertEqual(failed, [])
  AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 
chars]ine'] != []

  First list contains 1 additional elements.
  First extra element 0:
  '● NetworkManager-wait-online.service loaded failed failed Network Manager 
Wait Online'

  + []
  - ['● NetworkManager-wait-online.service loaded failed failed Network Manager 
'
  -  'Wait Online']

  --
  Ran 23 tests in 4.435s
  ...

  Reproducible locally by installing n-m from -proposed, then restarting
  the system in the LXC container.

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

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

[Desktop-packages] [Bug 1915498] Re: Copy / paste in Firefox randomly broken

2021-03-02 Thread Olivier Tilloy

I have updated the affected package.

** Package changed: firefox (Ubuntu) => gedit (Ubuntu)

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

Title:
  Copy / paste in Firefox randomly broken

Status in gedit package in Ubuntu:
  New

Bug description:
  Most of the time (but not always), when i copy content from an
  application (for example Gedit) to Firefox, the pasted content doesn't
  match what was copied. If I then try to paste in another application,
  the right content is pasted.

  I have to copy / paste the same content several times before the right
  content finally gets pasted to Firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: firefox 85.0.1+build1-0ubuntu0.20.10.1
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  juloliv5429 F pulseaudio
   /dev/snd/controlC0:  juloliv5429 F pulseaudio
  BuildID: 20210204182252
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Fri Feb 12 09:22:04 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:353
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  EcryptfsInUse: Yes
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-02-07 (370 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.2.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.2.0/24 dev wlp2s0 proto kernel scope link src 192.168.2.22 metric 600
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:353
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=85.0.1/20210204182252 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to groovy on 2020-10-22 (112 days ago)
  dmi.bios.date: 06/28/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X570DD.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X570DD
  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.:bvrX570DD.300:bd06/28/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX570DD_D570DD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX570DD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X570DD_D570DD
  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/gedit/+bug/1915498/+subscriptions

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

[Desktop-packages] [Bug 1917147] Re: firefox crashes after ubuntu 20.04.2 update.

2021-03-02 Thread Olivier Tilloy

Thanks Andy.

Andy, Theodore, would you mind trying to get a full backtrace of the
crash, to help diagnose and fix the problem? See the instructions in
https://bugs.launchpad.net/firefox/+bug/1917191/comments/17. Thanks in
advance!

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

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

Title:
  firefox crashes after ubuntu 20.04.2 update.

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Firefox instantly crashes when I open it after Ubuntu 20.04.2 update.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 86.0+build3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  NonfreeKernelModules: wl
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ted 857 F pulseaudio
  BuildID: 20210222142601
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 27 10:07:58 2021
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:348
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  InstallationDate: Installed on 2021-02-06 (20 days ago)
  InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204)
  IpRoute:
   default via 192.168.40.1 dev wlp3s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.40.0/24 dev wlp3s0 proto kernel scope link src 192.168.40.83 metric 
600
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:348
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=86.0/20210222142601
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/16
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP81.88Z.0047.B2D.1610201938
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-94245B3640C91C81
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro8,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-94245B3640C91C81
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B2D.1610201938:bd10/20/16:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro8,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Desktop-packages] [Bug 1917191] Re: firefox will not start after it crashed unexpectedly

2021-03-02 Thread Olivier Tilloy

Thanks John, that's very useful indeed. The backtrace points to a known 
upstream bug (https://bugzilla.mozilla.org/show_bug.cgi?id=1694670), which is 
fixed in the upcoming firefox 
87.0 (currently beta).
I'll consider cherry-picking the upstream patch for an Ubuntu update.

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

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

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

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

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

Title:
  firefox will not start after it crashed unexpectedly

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  firefox crashed unexpectedly, and it will not start or restart.  I am running 
the latest ubuntu-20.04.2 LTS, all updates applied.  firefox 86.0+build3
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  johnfg 1725 F pulseaudio
   /dev/snd/controlC1:  johnfg 1725 F pulseaudio
  BuildID: 20210222142601
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:348
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 20.04
  ForcedLayersAccel: False
  InstallationDate: Installed on 2020-02-22 (371 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.1.1 dev wlp10s0 proto dhcp metric 600 
   10.8.0.0/24 via 10.8.0.17 dev tun0 
   10.8.0.17 dev tun0 proto kernel scope link src 10.8.0.18 
   169.254.0.0/16 dev wlp10s0 scope link metric 1000 
   192.168.1.0/24 dev wlp10s0 proto kernel scope link src 192.168.1.8 metric 600
  NonfreeKernelModules: openafs
  Package: firefox 86.0+build3-0ubuntu0.20.04.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Profile0Extensions: extensions.sqlite corrupt or missing
  Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile0Locales: extensions.sqlite corrupt or missing
  Profile0PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:348
  Profile0PrefSources: prefs.js
  Profile0Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile1 (Default) - LastVersion=80.0/20200818235255 (Out of date)
   Profile0 - LastVersion=86.0/20210222142601
  RunningIncompatibleAddons: False
  Tags:  focal
  Uname: Linux 5.4.0-66-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-24 (309 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/05/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V4.00L12
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: CF52-4
  dmi.board.vendor: Panasonic Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Panasonic Corporation
  dmi.chassis.version: 001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV4.00L12:bd07/05/2011:svnPanasonicCorporation:pnCF-52SLGDD1M:pvr004:rvnPanasonicCorporation:rnCF52-4:rvr1:cvnPanasonicCorporation:ct10:cvr001:
  dmi.product.family: CF52-4
  dmi.product.name: CF-52SLGDD1M
  dmi.product.sku: CF-52SLGDD1M
  dmi.product.version: 004
  dmi.sys.vendor: Panasonic Corporation

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

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

[Desktop-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC

2021-03-02 Thread Balint Reczey

** Changed in: systemd (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start
  in LXC

Status in lxd package in Ubuntu:
  Won't Fix
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  This regresses systemd's autopkgtest because it expects the system in
  the container to reach running state, but the system ends up in
  degraded state due to the service failing.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz
  ...

  ==
  FAIL: test_no_failed (__main__.ServicesTest)
  No failed units
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", 
line 68, in test_no_failed
  self.assertEqual(failed, [])
  AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 
chars]ine'] != []

  First list contains 1 additional elements.
  First extra element 0:
  '● NetworkManager-wait-online.service loaded failed failed Network Manager 
Wait Online'

  + []
  - ['● NetworkManager-wait-online.service loaded failed failed Network Manager 
'
  -  'Wait Online']

  --
  Ran 23 tests in 4.435s
  ...

  Reproducible locally by installing n-m from -proposed, then restarting
  the system in the LXC container.

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

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

[Desktop-packages] [Bug 1912282] Re: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1

2021-03-02 Thread Nelly

I have a similar problem with tex-common in Ubuntu 20.04.
I tried to install a babel language, and got as result (part of the text is in 
Dutch):

sudo apt-get install texlive-lang-european
[sudo] wachtwoord voor nelly: 
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd   
De statusinformatie wordt gelezen... Klaar
De volgende pakketten zijn automatisch geïnstalleerd en zijn niet langer nodig:
  libllvm10 libllvm10:i386
Gebruik 'sudo apt autoremove' om ze te verwijderen.
De volgende NIEUWE pakketten zullen geïnstalleerd worden:
  texlive-lang-european
0 opgewaardeerd, 1 nieuw geïnstalleerd, 0 te verwijderen en 9 niet 
opgewaardeerd.
Er moeten 14,1 MB aan archieven opgehaald worden.
Na deze bewerking zal er 23,3 MB extra schijfruimte gebruikt worden.
Ophalen:1 http://nl.archive.ubuntu.com/ubuntu focal/universe amd64 
texlive-lang-european all 2019.20200218-1 [14,1 MB]
14,1 MB opgehaald in 2s (9.049 kB/s)  
Voorheen niet geselecteerd pakket texlive-lang-european wordt geselecteerd.
(Database wordt ingelezen ... 262758 bestanden en mappen momenteel 
geïnstalleerd.)
Uitpakken van .../texlive-lang-european_2019.20200218-1_all.deb wordt 
voorbereid...
Bezig met uitpakken van texlive-lang-european (2019.20200218-1) ...
Instellen van texlive-lang-european (2019.20200218-1) ...
Bezig met afhandelen van triggers voor tex-common (6.13) ...
Running mktexlsr. This may take some time... done.
Running updmap-sys. This may take some time... 
updmap-sys failed. Output has been stored in
/tmp/updmap.bXyswVXM
Please include this file if you report a bug.

Sometimes, not accepting conffile updates in /etc/texmf/updmap.d
causes updmap-sys to fail.  Please check for files with extension
.dpkg-dist or .ucf-dist in this directory

dpkg: fout bij verwerken van pakket tex-common (--configure):
 subproces van pakket tex-common werd script post-installation geïnstalleerd 
gaf de foutwaarde 1 terug
Fouten gevonden tijdens verwerken van:
 tex-common
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  package tex-common 6.13 failed to install/upgrade: installed tex-
  common package post-installation script subprocess returned error exit
  status 1

Status in tex-common package in Ubuntu:
  Confirmed

Bug description:
  That is all.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: tex-common 6.13
  ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78
  Uname: Linux 5.4.0-62-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Jan 18 15:47:15 2021
  ErrorMessage: installed tex-common package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2019-06-13 (585 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.2
  SourcePackage: tex-common
  Title: package tex-common 6.13 failed to install/upgrade: installed 
tex-common package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to focal on 2021-01-18 (0 days ago)

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

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

[Desktop-packages] [Bug 1912282] Re: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1

2021-03-02 Thread Launchpad Bug Tracker

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

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

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

Title:
  package tex-common 6.13 failed to install/upgrade: installed tex-
  common package post-installation script subprocess returned error exit
  status 1

Status in tex-common package in Ubuntu:
  Confirmed

Bug description:
  That is all.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: tex-common 6.13
  ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78
  Uname: Linux 5.4.0-62-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Jan 18 15:47:15 2021
  ErrorMessage: installed tex-common package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2019-06-13 (585 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.2
  SourcePackage: tex-common
  Title: package tex-common 6.13 failed to install/upgrade: installed 
tex-common package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to focal on 2021-01-18 (0 days ago)

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

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

[Desktop-packages] [Bug 1796187]

2021-03-02 Thread László Németh

@Xisco: According to your data, loading the test document is not only 25
times faster, but we finally have a reasonable load time. :) Many thanks
for verifying and closing the duplicates!

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

Title:
  [upstream] Writer hangs for over 20 minutes loading a 3MB, 450-page
  DOCX

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

Bug description:
  Trying to load the attached DOCX results in a hang.  I force-quit
  after 20 minutes.  The DOCX was created in MS Word (2013 I think), and
  is about 450 pages, thousands of footnotes, but no graphics AFAIK.

  I am using the latest package provided by snap. LibreOffice 6.1.2.1.
  Ubuntu 18.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-writer (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  4 23:50:54 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-06-03 (488 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-06-06 (119 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1796187/+subscriptions

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

[Desktop-packages] [Bug 1915712] Re: [snap] configure hook fails because the gnome-3-28-1804 platform snap isn't connected

2021-03-02 Thread Sergio Schvezov

** Changed in: snapcraft
   Status: Fix Committed => Fix Released

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

Title:
  [snap] configure hook fails because the gnome-3-28-1804 platform snap
  isn't connected

Status in Snapcraft:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Incomplete
Status in snapcraft package in Ubuntu:
  In Progress
Status in snapd package in Ubuntu:
  Incomplete

Bug description:
  happened on do-release-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: chromium-browser 87.0.4280.66-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18
  Uname: Linux 4.15.0-135-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEcmOt9h4RchURAQMIJh546JrlplhJmSMRUFS/7wABAQEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAeC0RAAAe/QA4Sx5TDgAKICAgICAg/wBMNzgwQzA1NDQwNDQK/ABBTDE5MTYKICAgICAgAGE=
   modes: 1280x1024 1280x1024 1024x768 1024x768 1024x768 832x624 800x600 
800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400
  Date: Mon Feb 15 13:26:20 2021
  Desktop-Session:
   'None'
   'None'
   '/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  Env:
   'None'
   'None'
  ErrorMessage: »neues chromium-browser-Skript des Paketes 
pre-installation«-Unterprozess gab den Fehlerwert 1 zurück
  InstallationDate: Installed on 2017-06-27 (1328 days ago)
  InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  InstalledPlugins:
   
  Load-Avg-1min: 0.61
  Load-Processes-Running-Percent:   0.2%
  MachineType: Hewlett-Packard HP Pro3500 Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-135-generic 
root=UUID=093e88ea-7b5e-4e39-b56c-03b28ad06dd2 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  SourcePackage: chromium-browser
  Title: package chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 failed to 
install/upgrade: »neues chromium-browser-Skript des Paketes 
pre-installation«-Unterprozess gab den Fehlerwert 1 zurück
  UpgradeStatus: Upgraded to focal on 2021-02-15 (0 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: AMI
  dmi.bios.version: 8.17
  dmi.board.name: 2ABF
  dmi.board.vendor: Foxconn
  dmi.board.version: 3.20
  dmi.chassis.asset.tag: CZC34935PY
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr8.17:bd10/25/2013:svnHewlett-Packard:pnHPPro3500Series:pvr:rvnFoxconn:rn2ABF:rvr3.20:cvnHewlett-Packard:ct3:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Pro3500 Series
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height

2021-03-02 Thread Péter Prőhle

The bug is still there in Ubuntu 20.10, see the riport in
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916890

each maximisation + un-maximisation cycle of a gnome-termial windows
will shrink the terminal by 1 row and by 1 column

two such a sycles (maximize, unmaximize, maximize, unmaximize) shrinks
from 80x42 to 78x40

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

Title:
  Terminal height shrinks - repeatedly restored shorter than the
  previous height

Status in GNOME Terminal:
  New
Status in gnome-terminal package in Ubuntu:
  Triaged

Bug description:
  1. Open a gnome-terminal window (from the launcher or by pressing Ctrl + Alt 
+ T)
  2. "stty -a | grep rows" reports "rows 24; columns 80;"
  3. Maximize the window (by clicking on the maximize button, or double 
clicking the title bar, or dragging the window up to the panel)
  4. Do the same again to un-maximize the window
  5. Now "stty -a | grep rows" reports "rows 23; columns 79;"

  Each time I do this, the window keeps getting one character shorter
  and one character narrower!

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-terminal 3.6.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Thu Mar  6 10:22:46 2014
  InstallationDate: Installed on 2010-04-15 (1421 days ago)
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
  MarkForUpload: True
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to saucy on 2013-10-29 (128 days ago)

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

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

[Desktop-packages] [Bug 1915003] Re: SRU: Always update the initramfs when changing power profile

2021-03-02 Thread Erich Eickmeyer 

Meant to say groovy in #15 (oops)

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

Title:
  SRU: Always update the initramfs when changing power profile

Status in NVIDIA Drivers Ubuntu:
  New
Status in OEM Priority Project:
  Triaged
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Committed
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in nvidia-prime source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Focal:
  Fix Committed
Status in nvidia-prime source package in Groovy:
  Fix Committed
Status in nvidia-settings source package in Groovy:
  Fix Committed

Bug description:
  Since we introduced support for dynamic power management, on systems
  with hybrid graphics (LP: #1904583), the need to load drivers with
  different options has become more evident.

  We need to make sure that the files in the initramfs are in sync with
  the current user selection.

  This is also a chance to update the old nvidia-settings release in the
  archive.

  
  [Impact]

  * If the modules list is not in sync with the selected power profile,
  users may experience a black screen or increased power consumption.

  * Updating the initramfs can take a few seconds, and we need to
  provide users with some form of visual feedback.

  [Fix]

  * The prime-select tool shoud update the initramfs when switching
  between power profiles, and provide visual feedback.

  * The nvidia-settings panel should provide a progress dialog, since
  profile switching would otherwise freeze the UI until update-initramfs
  completes.

  [Test Case]

  Make sure a supported nvidia driver is installed (450, 460), then
  install nvidia-prime and nvidia-settings from proposed, and check the
  following:

  1) prime-select query (to check your current profile)

  2) sudo prime-select on-demand (or "intel", or "nvidia", depending on
  your current power profile)

  3) Check that the operation completes successfully.

  4) Reboot your system

  5) Launch the nvidia-setting panel.

  6) Select a different profile from the PRIME tab, and check that a
  progress dialog is correctly displayed.

  7) Close the nvidia-settings panel, and reboot.

  
  [Regression Risk]
  Medium, while the changes in prime-select are trivial, nvidia-settings needs 
careful testing.

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

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

[Desktop-packages] [Bug 1915003] Re: SRU: Always update the initramfs when changing power profile

2021-03-02 Thread Erich Eickmeyer 

Verified on a Kubuntu Focus M1 running focal:

erich@erich-KFocus:~$ apt-cache policy nvidia-settings
nvidia-settings:
  Installed: 460.39-0ubuntu0.20.10.1
  Candidate: 460.39-0ubuntu0.20.10.1
  Version table:
 *** 460.39-0ubuntu0.20.10.1 100
100 /var/lib/dpkg/status

Works exactly as expected complete with a "Please wait for the operation
to complete" progress indicator.

** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy

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

Title:
  SRU: Always update the initramfs when changing power profile

Status in NVIDIA Drivers Ubuntu:
  New
Status in OEM Priority Project:
  Triaged
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Committed
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in nvidia-prime source package in Focal:
  Fix Committed
Status in nvidia-settings source package in Focal:
  Fix Committed
Status in nvidia-prime source package in Groovy:
  Fix Committed
Status in nvidia-settings source package in Groovy:
  Fix Committed

Bug description:
  Since we introduced support for dynamic power management, on systems
  with hybrid graphics (LP: #1904583), the need to load drivers with
  different options has become more evident.

  We need to make sure that the files in the initramfs are in sync with
  the current user selection.

  This is also a chance to update the old nvidia-settings release in the
  archive.

  
  [Impact]

  * If the modules list is not in sync with the selected power profile,
  users may experience a black screen or increased power consumption.

  * Updating the initramfs can take a few seconds, and we need to
  provide users with some form of visual feedback.

  [Fix]

  * The prime-select tool shoud update the initramfs when switching
  between power profiles, and provide visual feedback.

  * The nvidia-settings panel should provide a progress dialog, since
  profile switching would otherwise freeze the UI until update-initramfs
  completes.

  [Test Case]

  Make sure a supported nvidia driver is installed (450, 460), then
  install nvidia-prime and nvidia-settings from proposed, and check the
  following:

  1) prime-select query (to check your current profile)

  2) sudo prime-select on-demand (or "intel", or "nvidia", depending on
  your current power profile)

  3) Check that the operation completes successfully.

  4) Reboot your system

  5) Launch the nvidia-setting panel.

  6) Select a different profile from the PRIME tab, and check that a
  progress dialog is correctly displayed.

  7) Close the nvidia-settings panel, and reboot.

  
  [Regression Risk]
  Medium, while the changes in prime-select are trivial, nvidia-settings needs 
careful testing.

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

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

[Desktop-packages] [Bug 1917497] Re: package system-config-printer-common 1.5.12-0ubuntu1.1 failed to install/upgrade: installed system-config-printer-common package post-installation script subproces

2021-03-02 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package system-config-printer-common 1.5.12-0ubuntu1.1 failed to
  install/upgrade: installed system-config-printer-common package post-
  installation script subprocess returned error exit status 1

Status in system-config-printer package in Ubuntu:
  New

Bug description:
  package system-config-printer-common 1.5.12-0ubuntu1.1 failed to
  install/upgrade: installed system-config-printer-common package post-
  installation script subprocess returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: system-config-printer-common 1.5.12-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Feb 28 18:13:14 2021
  ErrorMessage: installed system-config-printer-common package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2021-02-28 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc. Inspiron N4050
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=c60c1b8a-ed2d-43a2-92aa-a528e8e3adcc ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: system-config-printer
  Title: package system-config-printer-common 1.5.12-0ubuntu1.1 failed to 
install/upgrade: installed system-config-printer-common package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2012
  dmi.bios.release: 0.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0GGRV5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.ec.firmware.release: 0.7
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd03/23/2012:br0.7:efr0.7:svnDellInc.:pnInspironN4050:pvrNotSpecified:rvnDellInc.:rn0GGRV5:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N4050
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1917497/+subscriptions

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

[Desktop-packages] [Bug 1917497] [NEW] package system-config-printer-common 1.5.12-0ubuntu1.1 failed to install/upgrade: installed system-config-printer-common package post-installation script subproc

2021-03-02 Thread sajadadineh

Public bug reported:

package system-config-printer-common 1.5.12-0ubuntu1.1 failed to
install/upgrade: installed system-config-printer-common package post-
installation script subprocess returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: system-config-printer-common 1.5.12-0ubuntu1.1
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Feb 28 18:13:14 2021
ErrorMessage: installed system-config-printer-common package post-installation 
script subprocess returned error exit status 1
InstallationDate: Installed on 2021-02-28 (2 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Dell Inc. Inspiron N4050
PackageArchitecture: all
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=c60c1b8a-ed2d-43a2-92aa-a528e8e3adcc ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: system-config-printer
Title: package system-config-printer-common 1.5.12-0ubuntu1.1 failed to 
install/upgrade: installed system-config-printer-common package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/23/2012
dmi.bios.release: 0.7
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0GGRV5
dmi.board.vendor: Dell Inc.
dmi.board.version: A07
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.ec.firmware.release: 0.7
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd03/23/2012:br0.7:efr0.7:svnDellInc.:pnInspironN4050:pvrNotSpecified:rvnDellInc.:rn0GGRV5:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron N4050
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

** Affects: system-config-printer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package system-config-printer-common 1.5.12-0ubuntu1.1 failed to
  install/upgrade: installed system-config-printer-common package post-
  installation script subprocess returned error exit status 1

Status in system-config-printer package in Ubuntu:
  New

Bug description:
  package system-config-printer-common 1.5.12-0ubuntu1.1 failed to
  install/upgrade: installed system-config-printer-common package post-
  installation script subprocess returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: system-config-printer-common 1.5.12-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Feb 28 18:13:14 2021
  ErrorMessage: installed system-config-printer-common package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2021-02-28 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc. Inspiron N4050
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=c60c1b8a-ed2d-43a2-92aa-a528e8e3adcc ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: system-config-printer
  Title: package system-config-printer-common 1.5.12-0ubuntu1.1 failed to 
install/upgrade: installed system-config-printer-common package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2012
  dmi.bios.release: 0.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0GGRV5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.ec.firmware.release: 0.7
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd03/23/2012:br0.7:efr0.7:svnDellInc.:pnInspironN4050:pvrNotSpecified:rvnDellInc.:rn0GGRV5:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N4050
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage

[Desktop-packages] [Bug 1917499] [NEW] hplip

2021-03-02 Thread Sergio Sánchez López

Public bug reported:

Hello.

I have downloaded and i have tried to install hplip 3.21.2 on Ubuntu
20.04 but this show this error:

READY TO BUILD AND INSTALL
--
Ready to perform build and install. Press  to continue or 'q' to quit: 


PRE-BUILD COMMANDS
--
OK


BUILD AND INSTALL
-
Running './configure --with-hpppddir=/usr/share/ppd/HP --libdir=/usr/lib 
--prefix=/usr --disable-qt4 --disable-qt5 --disable-doc-build 
--disable-cups-ppd-install --disable-foomatic-drv-install 
--disable-libusb01_build --disable-foomatic-ppd-install --disable-hpijs-install 
--disable-class-driver --disable-udev_sysfs_rules --disable-policykit 
--enable-cups-drv-install --enable-hpcups-install --enable-network-build 
--disable-dbus-build --enable-scan-build --disable-fax-build 
--enable-apparmor_build'
Please wait, this may take several minutes...
Command completed successfully.

Running 'make clean'
Please wait, this may take several minutes...
Command completed successfully.

Running 'make'
Please wait, this may take several minutes...
error: 'make' command failed with status code 2

And then exit of installation.

If i execute make in console, i see this:

# make

/bin/bash ./libtool  --tag=CC   --mode=compile gcc -DPACKAGE_NAME=\"HP\ Linux\ 
Imaging\ and\ Printing\" -DPACKAGE_TARNAME=\"hplip\" 
-DPACKAGE_VERSION=\"3.21.2\" -DPACKAGE_STRING=\"HP\ Linux\ Imaging\ and\ 
Printing\ 3.21.2\" -DPACKAGE_BUGREPORT=\"3.21.2\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"hplip\" -DVERSION=\"3.21.2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 
-DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_LIBDL=1 -DHAVE_PTHREAD_H=1 
-DHAVE_JPEGLIB_H=1 -DHAVE_UINT32_T=1 -DHAVE_LIBHPIP=1 -DHAVE_LIBHPIP=1 
-DHAVE_LIBCRYPTO=1 -DHAVE_LIBNETSNMP=1 -DHAVE_NET_SNMP_NET_SNMP_CONFIG_H=1 
-DHAVE_LIBAVAHI=1 -DHAVE_LIBAVAHI_CLIENT=1 -DHAVE_LIBAVAHI_COMMON=1 
-DHAVE_AVAHI_CLIENT_CLIENT_H=1 -DHAVE_AVAHI_COMMON_MALLOC_H=1 
-DHAVE_CUPS_CUPS_H=1 -DHAVE_LIBUSB_1_0_LIBUSB_H=1 -DHAVE_PYTHON2_7_PYTHON_H=1 
-I. -Iip -Iio/hpmud -Iscan/sane -Iprnt/hpijs -Icommon/   -DCONFDIR=\"/etc/hp\" 
-I/usr/include/avahi-client -I/usr/include/avahi-core 
-I/usr/include/avahi-common  -DCONFDIR=\"/etc/hp\" -MT 
libhpdiscovery_la-avahiDiscovery.lo -MD -MP -MF 
.deps/libhpdiscovery_la-avahiDiscovery.Tpo -c -o 
libhpdiscovery_la-avahiDiscovery.lo `test -f 
'protocol/discovery/avahiDiscovery.c' || echo 
'./'`protocol/discovery/avahiDiscovery.c
libtool: compile:  gcc "-DPACKAGE_NAME=\"HP Linux Imaging and Printing\"" 
-DPACKAGE_TARNAME=\"hplip\" -DPACKAGE_VERSION=\"3.21.2\" "-DPACKAGE_STRING=\"HP 
Linux Imaging and Printing 3.21.2\"" -DPACKAGE_BUGREPORT=\"3.21.2\" 
-DPACKAGE_URL=\"\" -DPACKAGE=\"hplip\" -DVERSION=\"3.21.2\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_LIBDL=1 
-DHAVE_PTHREAD_H=1 -DHAVE_JPEGLIB_H=1 -DHAVE_UINT32_T=1 -DHAVE_LIBHPIP=1 
-DHAVE_LIBHPIP=1 -DHAVE_LIBCRYPTO=1 -DHAVE_LIBNETSNMP=1 
-DHAVE_NET_SNMP_NET_SNMP_CONFIG_H=1 -DHAVE_LIBAVAHI=1 -DHAVE_LIBAVAHI_CLIENT=1 
-DHAVE_LIBAVAHI_COMMON=1 -DHAVE_AVAHI_CLIENT_CLIENT_H=1 
-DHAVE_AVAHI_COMMON_MALLOC_H=1 -DHAVE_CUPS_CUPS_H=1 
-DHAVE_LIBUSB_1_0_LIBUSB_H=1 -DHAVE_PYTHON2_7_PYTHON_H=1 -I. -Iip -Iio/hpmud 
-Iscan/sane -Iprnt/hpijs -Icommon/ -DCONFDIR=\"/etc/hp\" 
-I/usr/include/avahi-client -I/usr/include/avahi-core 
-I/usr/include/avahi-common -DCONFDIR=\"/etc/hp\" -MT 
libhpdiscovery_la-avahiDiscovery.lo -MD -MP -MF 
.deps/libhpdiscovery_la-avahiDiscovery.Tpo -c 
protocol/discovery/avahiDiscovery.c  -fPIC -DPIC -o 
.libs/libhpdiscovery_la-avahiDiscovery.o
protocol/discovery/avahiDiscovery.c:22:10: fatal error: dbus/dbus.h: No such 
file or directory
   22 | #include 
  |  ^
compilation terminated.
make: *** [Makefile:6163: libhpdiscovery_la-avahiDiscovery.lo] Error 1


How can i fix it?

Thanks!

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

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

Title:
  hplip

Status in hplip package in Ubuntu:
  New

Bug description:
  Hello.

  I have downloaded and i have tried to install hplip 3.21.2 on Ubuntu
  20.04 but this show this error:

  READY TO BUILD AND INSTALL
  --
  Ready to perform build and install. Press  to continue or 'q' to quit: 

  
  PRE-BUILD COMMANDS
  --
  OK

  
  BUILD AND INSTALL
  -
  Running './configure --with-hpppddir=/usr/share/ppd/HP --libdir=/usr/lib 
--prefix=/usr --disable-qt4 --disable-qt5 --disable-doc-build 
--disable-cups-ppd-install

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

2021-03-02 Thread Niv Goldenberg

I'm still getting this bug.
Following this workaround:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1874513
solve the issue for me, but I need to repeat it each time I'm connecting my
Bose Q35 II via Bluetooth.

Specs:
pulseaudio 13.99.1
Ubuntu 20.04, 5.8.0-44-generic
Lenovo Thinkpad T14 Gen1 Intel

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

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]

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

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.

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

Re: [Desktop-packages] [Bug 1917191] Re: firefox will not start after it crashed unexpectedly

2021-03-02 Thread John F. Godfrey

Oliver,
I did what you said and sent the terminal output.  Hope it helps you fix
the bug!

john

On Mon, Mar 1, 2021 at 10:35 AM Olivier Tilloy <1917...@bugs.launchpad.net>
wrote:

> If you don't mind installing debug packages that use a substantial
> amount of space, could you do the following:
>
> sudo apt install firefox-dbg
> firefox -g
>
> At the (gdb) prompt, type "r" then return. When the crash happens, you
> should be getting another (gdb) prompt, type "t a a bt" then return,
> press the return key until there is no more of the backtrace to display,
> then copy-paste the contents of the terminal to a text file and attach
> it here.
>
> This would be very helpful to understand where the crash is occuring.
> Many thanks in advance!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1917191
>
> Title:
>   firefox will not start after it crashed unexpectedly
>
> Status in firefox package in Ubuntu:
>   Incomplete
>
> Bug description:
>   firefox crashed unexpectedly, and it will not start or restart.  I am
> running the latest ubuntu-20.04.2 LTS, all updates applied.  firefox
> 86.0+build3
>   ---
>   ProblemType: Bug
>   AddonCompatCheckDisabled: False
>   ApportVersion: 2.20.11-0ubuntu27.16
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  johnfg 1725 F pulseaudio
>/dev/snd/controlC1:  johnfg 1725 F pulseaudio
>   BuildID: 20210222142601
>   CasperMD5CheckResult: skip
>   Channel: Unavailable
>   CurrentDesktop: ubuntu:GNOME
>   DefaultProfileExtensions: extensions.sqlite corrupt or missing
>   DefaultProfileIncompatibleExtensions: Unavailable (corrupt or
> non-existant compatibility.ini or extensions.sqlite)
>   DefaultProfileLocales: extensions.sqlite corrupt or missing
>   DefaultProfilePrefErrors: Unexpected character ',' before close
> parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:348
>   DefaultProfilePrefSources: prefs.js
>   DefaultProfileThemes: extensions.sqlite corrupt or missing
>   DistroRelease: Ubuntu 20.04
>   ForcedLayersAccel: False
>   InstallationDate: Installed on 2020-02-22 (371 days ago)
>   InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
>   IpRoute:
>default via 192.168.1.1 dev wlp10s0 proto dhcp metric 600
>10.8.0.0/24 via 10.8.0.17 dev tun0
>10.8.0.17 dev tun0 proto kernel scope link src 10.8.0.18
>169.254.0.0/16 dev wlp10s0 scope link metric 1000
>192.168.1.0/24 dev wlp10s0 proto kernel scope link src 192.168.1.8
> metric 600
>   NonfreeKernelModules: openafs
>   Package: firefox 86.0+build3-0ubuntu0.20.04.1
>   PackageArchitecture: amd64
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
>   Profile0Extensions: extensions.sqlite corrupt or missing
>   Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant
> compatibility.ini or extensions.sqlite)
>   Profile0Locales: extensions.sqlite corrupt or missing
>   Profile0PrefErrors: Unexpected character ',' before close parenthesis @
> /usr/lib/firefox/omni.ja:greprefs.js:348
>   Profile0PrefSources: prefs.js
>   Profile0Themes: extensions.sqlite corrupt or missing
>   Profiles:
>Profile1 (Default) - LastVersion=80.0/20200818235255 (Out of date)
>Profile0 - LastVersion=86.0/20210222142601
>   RunningIncompatibleAddons: False
>   Tags:  focal
>   Uname: Linux 5.4.0-66-generic x86_64
>   UpgradeStatus: Upgraded to focal on 2020-04-24 (309 days ago)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 07/05/2011
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: V4.00L12
>   dmi.board.asset.tag: No Asset Tag
>   dmi.board.name: CF52-4
>   dmi.board.vendor: Panasonic Corporation
>   dmi.board.version: 1
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Panasonic Corporation
>   dmi.chassis.version: 001
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrV4.00L12:bd07/05/2011:svnPanasonicCorporation:pnCF-52SLGDD1M:pvr004:rvnPanasonicCorporation:rnCF52-4:rvr1:cvnPanasonicCorporation:ct10:cvr001:
>   dmi.product.family: CF52-4
>   dmi.product.name: CF-52SLGDD1M
>   dmi.product.sku: CF-52SLGDD1M
>   dmi.product.version: 004
>   dmi.sys.vendor: Panasonic Corporation
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1917191/+subscriptions
>


-- 
John F. Godfrey, Pastor
Belgrade Christian Assembly
Belgrade, Montana  USA
"Jesus said to him, 'I am the Way, the Truth, and the Life; no one comes to
the Father, except through Me'" (John 14:6).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.

Re: [Desktop-packages] [Bug 1917191] Re: firefox will not start after it crashed unexpectedly

2021-03-02 Thread John F. Godfrey

Thread 43 (Thread 0x7fffda6bd700 (LWP 48369)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x7fffec3dd63c) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x7fffec3dd5e0, cond=0x7fffec3dd610) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x7fffec3dd610, mutex=0x7fffec3dd5e0) at
pthread_cond_wait.c:638
#3  0x555a8e67 in
mozilla::detail::ConditionVariableImpl::wait(mozilla::detail::MutexImpl&)
(this=0x7fffec3dd63c, lock=...) at
/build/firefox-ZHFUPw/firefox-86.0+build3/mozglue/misc/ConditionVariable_posix.cpp:108
#4  0x7fffed6aec4a in mozilla::OffTheBooksCondVar::Wait()
(this=0x7fffec3dd608) at
/build/firefox-ZHFUPw/firefox-86.0+build3/obj-x86_64-linux-gnu/dist/include/mozilla/CondVar.h:58
#5  mozilla::ThreadEventQueue::GetEvent(bool,
mozilla::BaseTimeDuration*)
(this=, aMayWait=,
aLastEventDelay=0x7fffe49bfb58) at
/build/firefox-ZHFUPw/firefox-86.0+build3/xpcom/threads/ThreadEventQueue.cpp:161
#6  0x7fffed6b6480 in nsThread::ProcessNextEvent(bool, bool*)
(this=0x7fffe49bfac0, aMayWait=true, aResult=0x7fffda6bcc07) at
/build/firefox-ZHFUPw/firefox-86.0+build3/xpcom/threads/nsThread.cpp:1144
#7  0x7fffed6b9a16 in NS_ProcessNextEvent(nsIThread*, bool)
(aThread=0x7fffec3dd63c, aMayWait=true) at
/build/firefox-ZHFUPw/firefox-86.0+build3/xpcom/threads/nsThreadUtils.cpp:548
#8  0x7fffedc1f0ea in
mozilla::ipc::MessagePumpForNonMainThreads::Run(base::MessagePump::Delegate*)
(this=0x7fffdaaceb80, aDelegate=0x7fffda6bcc90) at
/build/firefox-ZHFUPw/firefox-86.0+build3/ipc/glue/MessagePump.cpp:332
#9  0x7fffedbdf5d8 in MessageLoop::RunInternal() (this=0x80) at
/build/firefox-ZHFUPw/firefox-86.0+build3/ipc/chromium/src/base/message_loop.cc:334
#10 MessageLoop::RunHandler() (this=0x80) at
/build/firefox-ZHFUPw/firefox-86.0+build3/ipc/chromium/src/base/message_loop.cc:327
#11 MessageLoop::Run() (this=0x80) at
/build/firefox-ZHFUPw/firefox-86.0+build3/ipc/chromium/src/base/message_loop.cc:309
#12 0x7fffed6b483f in nsThread::ThreadFunc(void*) (aArg=) at
/build/firefox-ZHFUPw/firefox-86.0+build3/xpcom/threads/nsThread.cpp:441
#13 0x77a35c89 in _pt_root (arg=0x7fffe485d940) at
/build/firefox-ZHFUPw/firefox-86.0+build3/nsprpub/pr/src/pthreads/ptthread.c:201
#14 0x77f98609 in start_thread (arg=) at
pthread_create.c:477
#15 0x77b6e293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 42 (Thread 0x7fffd8dff700 (LWP 48368)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x7fffda9f42d8) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x7fffda9f4400, cond=0x7fffda9f42b0) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x7fffda9f42b0, mutex=0x7fffda9f4400) at
pthread_cond_wait.c:638
#3  0x71c8ab25 in std::sys::unix::condvar::Condvar::wait () at
/build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/sys/unix/
condvar.rs:69
#4  std::sys_common::condvar::Condvar::wait () at
/build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/sys_common/
condvar.rs:50
#5  std::sync::condvar::Condvar::wait () at
/build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/sync/
condvar.rs:199
#6  rayon_core::sleep::Sleep::sleep () at
/build/firefox-ZHFUPw/firefox-86.0+build3/third_party/rust/rayon-core/src/sleep/
mod.rs:226
#7  0x71c8a2fe in rayon_core::sleep::Sleep::no_work_found () at
/build/firefox-ZHFUPw/firefox-86.0+build3/third_party/rust/rayon-core/src/sleep/
mod.rs:120
--Type  for more, q to quit, c to continue without paging--
#8  rayon_core::registry::WorkerThread::wait_until_cold () at
/build/firefox-ZHFUPw/firefox-86.0+build3/third_party/rust/rayon-core/src/
registry.rs:733
#9  0x71c8bd76 in rayon_core::registry::WorkerThread::wait_until ()
at
/build/firefox-ZHFUPw/firefox-86.0+build3/third_party/rust/rayon-core/src/
registry.rs:704
#10 rayon_core::registry::main_loop () at
/build/firefox-ZHFUPw/firefox-86.0+build3/third_party/rust/rayon-core/src/
registry.rs:837
#11 rayon_core::registry::ThreadBuilder::run () at
/build/firefox-ZHFUPw/firefox-86.0+build3/third_party/rust/rayon-core/src/
registry.rs:56
#12 ::spawn::{{closure}} () at
/build/firefox-ZHFUPw/firefox-86.0+build3/third_party/rust/rayon-core/src/
registry.rs:101
#13 std::sys_common::backtrace::__rust_begin_short_backtrace () at
/build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/sys_common/
backtrace.rs:137
#14 0x71c8b55d in
std::thread::Builder::spawn_unchecked::{{closure}}::{{closure}} () at
/build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/thread/
mod.rs:458
#15  as
core::ops::function::FnOnce<()>>::call_once () at
/build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/panic.rs:308
#16 std::panicking::try::do_call () at
/build/rustc-n7HJ8w/rustc-1.47.0+dfsg1+llvm/library/std/src/panicking.rs:373
#17 std::panicking::try () at

[Desktop-packages] [Bug 1902829] Re: Missing "Mobile Broadband" menu item

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

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

Title:
  Missing "Mobile Broadband" menu item

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Groovy:
  Fix Released
Status in gnome-shell package in Debian:
  Fix Released

Bug description:
  [Impact]

  gnome-shell does not show the "Mobile Broadband" menu item in Ubuntu
  20.10, which practically prevents net access for users who depend on
  mobile broadband. An upstream fix has recently been pushed.

  [Test case]

  * Install the binaries built by the gnome-shell source package from
  groovy-proposed

  * Reboot

  * Confirm with a USB dongle for mobile broadband that it's recognized
  in the system menu and allows you to connect.

  [Regression risk]

  The issue was triggered by a change to gjs, and the fix simply adds
  two property getters. Low regression risk.

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

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

[Desktop-packages] [Bug 1883886] Re: Print dialogue's height in Libreoffice Writer is too high to see and click buttons.

2021-03-02 Thread Ken VanDine

** Tags removed: rls-ff-incoming

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

Title:
   Print dialogue's height in Libreoffice Writer is too high to see and
  click buttons.

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  In Progress

Bug description:
  Hello,

  I have the bug that is denoted here
  https://ask.libreoffice.org/en/question/240651/print-dialogue-too-
  large-to-select-ok-to-print/ and here
  https://bugs.documentfoundation.org/show_bug.cgi?id=127782#c67.

  Essentially, the libreoffice writer print's dialog box is too high for
  me to view and press the buttons with the mouse. A workaround is to
  just press ENTER to print.

  Please see the following screenshot for an example:
  https://snipboard.io/vc1X0f.jpg

  My information is as follows:

  Results of lsb_release -rd

  Description: Ubuntu 20.04 LTS
  Release: 20.04

  Results of apt-cache policy libreoffice-writer

  libreoffice-writer:
Installed: 1:6.4.3-0ubuntu0.20.04.1
Candidate: 1:6.4.3-0ubuntu0.20.04.1
Version table:
   *** 1:6.4.3-0ubuntu0.20.04.1 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:6.4.2-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  Just FYI in case it is necessary: I am using Lubuntu 20.04 LTS with LXQt. 

  Best regards,

  
  Owen Charles

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-writer 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Wed Jun 17 12:47:56 2020
  InstallationDate: Installed on 2020-06-05 (11 days ago)
  InstallationMedia: Lubuntu 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/df-libreoffice/+bug/1883886/+subscriptions

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

[Desktop-packages] [Bug 1883886] Re: Print dialogue's height in Libreoffice Writer is too high to see and click buttons.

2021-03-02 Thread Heather Ellsworth

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

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

Title:
   Print dialogue's height in Libreoffice Writer is too high to see and
  click buttons.

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  In Progress

Bug description:
  Hello,

  I have the bug that is denoted here
  https://ask.libreoffice.org/en/question/240651/print-dialogue-too-
  large-to-select-ok-to-print/ and here
  https://bugs.documentfoundation.org/show_bug.cgi?id=127782#c67.

  Essentially, the libreoffice writer print's dialog box is too high for
  me to view and press the buttons with the mouse. A workaround is to
  just press ENTER to print.

  Please see the following screenshot for an example:
  https://snipboard.io/vc1X0f.jpg

  My information is as follows:

  Results of lsb_release -rd

  Description: Ubuntu 20.04 LTS
  Release: 20.04

  Results of apt-cache policy libreoffice-writer

  libreoffice-writer:
Installed: 1:6.4.3-0ubuntu0.20.04.1
Candidate: 1:6.4.3-0ubuntu0.20.04.1
Version table:
   *** 1:6.4.3-0ubuntu0.20.04.1 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:6.4.2-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  Just FYI in case it is necessary: I am using Lubuntu 20.04 LTS with LXQt. 

  Best regards,

  
  Owen Charles

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-writer 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Wed Jun 17 12:47:56 2020
  InstallationDate: Installed on 2020-06-05 (11 days ago)
  InstallationMedia: Lubuntu 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/df-libreoffice/+bug/1883886/+subscriptions

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

[Desktop-packages] [Bug 1915161] Re: deja dup won't restore a folder where name contains apostrophe and space

2021-03-02 Thread Ken VanDine

** Changed in: deja-dup (Ubuntu Groovy)
   Status: Triaged => Won't Fix

** Changed in: duplicity (Ubuntu Groovy)
   Status: Triaged => Won't Fix

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

Title:
  deja dup won't restore a folder where name contains apostrophe and
  space

Status in deja-dup package in Ubuntu:
  Fix Released
Status in duplicity package in Ubuntu:
  Fix Released
Status in deja-dup source package in Groovy:
  Won't Fix
Status in duplicity source package in Groovy:
  Won't Fix

Bug description:
  I have a folder entitled Mothers' Union. I use Deja-Dup to backup it
  up (along with many other folders) on Ubuntu 20.10. When I open Deja-
  Dup and click on the restore option and pick a back-up date it shows
  all the folders in the backup except this one (Mothers' Union). If I
  remove the apostrophe from the folder name it backs it up fine and can
  be restored. Other folders where the apostrophe is in the name but not
  followed by a space (e.g. John's Documents) also backup and restore
  correctly. Not sure if this is a bug but it's unfortunate that with
  this combination of an apostrophe and a space in the name I can't
  restore the folder.

  1. Ubuntu 20.10
  2. deja-dup 42.2-1ubuntu1
  3. I expected to be able to restore the folder with the apostrophe and space 
in the name (Mothers' Union)
  4. The folder is not available in any of the restore points.

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

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

[Desktop-packages] [Bug 1914374] Re: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image

2021-03-02 Thread Ken VanDine

** Changed in: ubiquity (Ubuntu Groovy)
   Status: Triaged => Won't Fix

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

Title:
  Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image

Status in OEM Priority Project:
  Fix Released
Status in ubiquity package in Ubuntu:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubiquity source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Released
Status in ubiquity source package in Groovy:
  Won't Fix
Status in ubuntu-drivers-common source package in Groovy:
  New

Bug description:
  I've installed the focal-desktop-amd64.iso image with SHA-256 sum
  b928163990d9e148605c230c5d3e7bc563bb67269d551f741abc804553f3477c from
  http://cdimage.ubuntu.com/focal/daily-live/20210202.1/ on the HP ZBook
  15 G7 laptop (CID 202009-28216).

  There are multiple issues:

  * The graphical desktop isn't launched. The screen remains black except for a 
cursor blinking erratically in the top left corner of the screen. If I hammer 
Control+Alt+F[12345] for a while, the graphical desktop starts eventually.
  * The screen resolution is 3840x2160 but there is no scaling, so everything 
is tiny.
  * The touchpad does not work.
  * WLAN does not work.
  * Ethernet does not work. I tried two dongles (a USB A as well as a USB C 
dongle).
  * No sound.

  $ cat /proc/version_signature
  Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18

  $ lsb_release -rd
  Description:Ubuntu 20.04.2 LTS
  Release:20.04

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

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

[Desktop-packages] [Bug 1904547] Re: gnome-control-center crashed with SIGSEGV in cc_display_config_get_panel_orientation_managed() from reset_current_config() from on_screen_changed() from on_screen_