date:20211103

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

Public bug reported:

If booted with the monitor turned off then there is only one login
option 'Ubuntu' and it is a Xorg session.

This appears to be a result of GDM's normal "try Wayland and if it
doesn't work then hide it". But since Xorg seems to be more resilient in
this case it suggests we can do better for Wayland too. But I'm not sure
if only gdm3 or only mutter (Wayland) needs fixing.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gdm3 41~rc-0ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
Date: Thu Nov  4 12:38:22 2021
InstallationDate: Installed on 2021-05-11 (176 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210510)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug impish

** This bug has been marked a duplicate of bug 1919400
   Wayland login option is missing if booted with the monitor turned off

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

Title:
  Only one login option 'Ubuntu' and it is a Xorg session, if booted
  with the monitor turned off

Status in gdm3 package in Ubuntu:
  New

Bug description:
  If booted with the monitor turned off then there is only one login
  option 'Ubuntu' and it is a Xorg session.

  This appears to be a result of GDM's normal "try Wayland and if it
  doesn't work then hide it". But since Xorg seems to be more resilient
  in this case it suggests we can do better for Wayland too. But I'm not
  sure if only gdm3 or only mutter (Wayland) needs fixing.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gdm3 41~rc-0ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Nov  4 12:38:22 2021
  InstallationDate: Installed on 2021-05-11 (176 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210510)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1949572] Re: freeze after back-to-back left and right click on the app in the dock

Also, next time the problems happens, after rebooting please run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.


** Changed in: gnome-shell-extension-ubuntu-dock (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/1949572

Title:
  freeze after back-to-back left and right click on the app in the dock

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

Bug description:
  When you click the icon of the app in the dock to open it for the
  first time and then immediately right click to see options, everything
  freezes and you are forced to reboot.

  I'm using Ubuntu 21.10. I installed it today.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-11-03 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1949572] Re: freeze after back-to-back left and right click on the app in the dock

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

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

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

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

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

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

Title:
freeze after back-to-back left and right click on the app in the dock

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

Bug description:
When you click the icon of the app in the dock to open it for the
first time and then immediately right click to see options, everything
freezes and you are forced to reboot.

I'm using Ubuntu 21.10. I installed it today.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2021-11-03 (0 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
PackageArchitecture: all
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Tags: impish wayland-session
Uname: Linux 5.13.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

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

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

[Desktop-packages] [Bug 1949598] Re: Wrong resolution on second monitor after resume from suspend

Thanks for the bug report.

Does the same bug occur if you log into 'Ubuntu on Xorg'?

Does the same bug occur if you run the Ubuntu kernel instead of the
generic one you have installed?


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

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

Title:
  Wrong resolution on second monitor after resume from suspend

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 21.10 on wayland.

  I have two monitors connected to a AMD 5500xt, one via HDMI and
  another, the secondary, via DP, with an DP->VGA adaptor. This setup
  worked just fine on Ubuntu 21.04, also on wayland.

  After updating to 21.10, often (but not always) the secondary monitor
  wakes up showing a wrong, lower resolution. Instead of the normal
  1280x1024, it starts at 800x600. Despite this, in Gnome Settings the
  resolution is still reported as 1280x1024.

  I can solve this issue by changing the resolution in settings and
  reverting back to 1280x1024.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  Uname: Linux 5.13.0-051300-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  3 11:44:16 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-11-04 (364 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-03 (30 days ago)

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


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

[Desktop-packages] [Bug 1949352] Re: [vmware] Removable drives are not auto-mounted after screen lock/unlock

https://github.com/micheleg/dash-to-dock/pull/1576/

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

** Also affects: gnome-shell-extension-dashtodock (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: gnome-shell-extension-dashtodock (Ubuntu)
   Status: New => In Progress

** Summary changed:

- [vmware] Removable drives are not auto-mounted after screen lock/unlock
+ Removable drives are not auto-mounted after screen lock/unlock

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

Title:
  Removable drives are not auto-mounted after screen lock/unlock

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

Bug description:
  If I lock and then unlock the screen, and then connect a removable
  drive, it is not recognized by the GNOME shell. The kernel logs show
  the drive, I can mount it manually, but it is not mounted
  automatically. The logged errors are attached.

  I could fix the issue by modifying the source code as given in the attached 
patch.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-11-01 (1 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell 40.5-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 397269] Re: HDMI audio cuts out intermittently while normal audio plays fine

This bug has been closed for 12 years. Please open a new one if you have
any ongoing issues.

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

Title:
  HDMI audio cuts out intermittently while normal audio plays fine

Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: pulseaudio

  I have my audio set up to play through my laptop speakers and over
  HDMI to my television. In Jaunty this works fine while in Karmic the
  HDMI audio will intermittently cut out for a split second a few times
  a minute. During this time however the audio over the laptop speakers
  plays just fine. It just seems as if a frame of the HDMI audio gets
  dropped randomly. The video over the HDMI is perfectly fine, FYI.

  ProblemType: Bug
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael4942 f mixer_applet2
michael7360 F npviewer.bin
   /dev/snd/pcmC0D0p:   michael7360 F...m npviewer.bin
   /dev/snd/timer:  michael7360 F npviewer.bin
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf6ffc000 irq 21'
 Mixer name : 'SigmaTel STAC9228'
 Components : 'HDA:83847616,10280209,00100402'
 Controls  : 28
 Simple ctrls  : 18
  Date: Wed Jul  8 21:20:16 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia wl
  Package: pulseaudio 1:0.9.15-4ubuntu1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.30-10.12-generic
  SourcePackage: pulseaudio
  Uname: Linux 2.6.30-10-generic x86_64

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


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

[Desktop-packages] [Bug 1949647] [NEW] When changing the driver for any printer the driver program just continues searching infinitely

2021-11-03 Thread Charles McColm

Public bug reported:

Description:Ubuntu 20.04.3 LTS
Release:20.04

system-config-printer:
  Installed: 1.5.12-0ubuntu1.1
  Candidate: 1.5.12-0ubuntu1.1
  Version table:
 *** 1.5.12-0ubuntu1.1 500
500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages
100 /var/lib/dpkg/status
 1.5.12-0ubuntu1 500
500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
500 http://ca.archive.ubuntu.com/ubuntu focal/main i386 Packages

I first experienced this at work on an Asus machine with an i7-3770 CPU,
16GB of RAM. I connected an HP Laserjet 1020. Xubuntu appeared to
configure and install a driver, but wouldn't print a test page. (Not an
issue with other printers on the same system) So I tried changing the
Make and Model of the printer. When I clicked Change beside the Make and
Model dialog box the Change Driver "Searching" dialog appeared, but it
just sits infinitely looking for drivers.

I thought it might be some odd relationship between the machine and
printer so I tried a different system at work and a different printer (a
brother printer which Xubuntu found and printing worked). Same issue
trying to change the Make and Model. Also tried at home thinking it
might be an issue with our PXE installed Xubuntu, but same issue (USB
installed).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: system-config-printer 1.5.12-0ubuntu1.1
ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Wed Nov  3 19:14:48 2021
ExecutablePath: /usr/share/system-config-printer/system-config-printer.py
InterpreterPath: /usr/bin/python3.8
Lpstat: device for DYMO-LabelWriter-450: 
usb://DYMO/LabelWriter%20450?serial=01010112345600
MachineType: To be filled by O.E.M. To be filled by O.E.M.
PackageArchitecture: all
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DYMO-LabelWriter-450.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DYMO-LabelWriter-450.ppd: Permission denied
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic 
root=UUID=3380cfa0-cebe-4249-b891-a500fa13528d ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
SourcePackage: system-config-printer
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/17/2019
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Intel X79
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/17/2019:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:skuTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnIntelX79:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

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


** Tags: amd64 apport-bug focal

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

Title:
  When changing the driver for any printer the driver program just
  continues searching infinitely

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

Bug description:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  system-config-printer:
Installed: 1.5.12-0ubuntu1.1
Candidate: 1.5.12-0ubuntu1.1
Version table:
   *** 1.5.12-0ubuntu1.1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1.5.12-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://ca.archive.ubuntu.com/ubuntu focal/main i386 Packages

  I first experienced this at work on an Asus machine with an i7-3770
  CPU, 16GB of RAM. I connected an HP Laserjet 1020. Xubuntu appeared to
  configure and install a driver, but wouldn't print a test page. (Not
  an issue with other printers on the same system) So I tried changing
  the

[Desktop-packages] [Bug 1853977] Re: nvidia-340 dpkg: error: version '-' has bad syntax: revision number is empty

2021-11-03 Thread Seth Arnold

Users are still finding this issue. In #ubuntu, 3 November 2021:

 https://justpaste.it/97emx

Thanks

** Also affects: nvidia-graphics-drivers-340 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  nvidia-340 dpkg: error: version '-' has bad syntax: revision number is
  empty

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

Bug description:
  Hello,

  When installing `nvidia-340` there is an error is the postinst script:

  philippe@pv-desktop:~$ sudo apt install --reinstall nvidia-340
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 to upgrade, 0 to newly install, 1 reinstalled, 0 to remove and 7 not to 
upgrade.
  Need to get 0 B/51.9 MB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 309892 files and directories currently installed.)
  Preparing to unpack .../nvidia-340_340.107-0ubuntu0.18.04.4_amd64.deb ...
  Stopping nvidia-persistenced
  nvidia-persistenced: no process found
  Done.
  (snip)
  Setting up nvidia-340 (340.107-0ubuntu0.18.04.4) ...
  dpkg: error: version '-' has bad syntax: revision number is empty
  dpkg: error: version '-' has bad syntax: revision number is empty
  update-initramfs: deferring update (trigger activated)
  INFO:Enable nvidia-340
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
  Loading new nvidia-340-340.107 DKMS files...
  Building for 4.15.0-70-generic
  Building for architecture x86_64
  Building initial module for 4.15.0-70-generic
  Done.

  The comment at https://askubuntu.com/questions/969352/uninstalling-
  and-then-reinstalling-nvidia-384-kills-colord tells us that
  /var/lib/dpkg/info/nvidia-340.postinst has a typo: replace $KERNELS
  with $CURRENT_KERNEL then `dpkg-reconfigure nvidia-340` works as
  expected.

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


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

[Desktop-packages] [Bug 1949637] Re: Libreoffice crash

2021-11-03 Thread svenmeier

When opening a document, some popups are flashing and then nothing
happens:

sven@~/Documents$ libreoffice Sample.ods 
sven@~/Documents$

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

Title:
  Libreoffice crash

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Libreoffice crashed on startup:

  sven@:~/$ libreoffice 
  terminate called after throwing an instance of 
'com::sun::star::lang::IllegalArgumentException'
  Unspecified Application Error

  I've removed Libreoffice completely, installed it again via the
  Software-Center and it crashes again.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: libreoffice 1:7.2.2-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  3 21:25:16 2021
  InstallationDate: Installed on 2019-10-03 (762 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to impish on 2021-10-17 (17 days ago)

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


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

[Desktop-packages] [Bug 1949637] [NEW] Libreoffice crash

2021-11-03 Thread svenmeier

Public bug reported:

Libreoffice crashed on startup:

sven@:~/$ libreoffice 
terminate called after throwing an instance of 
'com::sun::star::lang::IllegalArgumentException'
Unspecified Application Error

I've removed Libreoffice completely, installed it again via the
Software-Center and it crashes again.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: libreoffice 1:7.2.2-0ubuntu0.21.10.1
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  3 21:25:16 2021
InstallationDate: Installed on 2019-10-03 (762 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
SourcePackage: libreoffice
UpgradeStatus: Upgraded to impish on 2021-10-17 (17 days ago)

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


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

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

Title:
  Libreoffice crash

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Libreoffice crashed on startup:

  sven@:~/$ libreoffice 
  terminate called after throwing an instance of 
'com::sun::star::lang::IllegalArgumentException'
  Unspecified Application Error

  I've removed Libreoffice completely, installed it again via the
  Software-Center and it crashes again.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: libreoffice 1:7.2.2-0ubuntu0.21.10.1
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  3 21:25:16 2021
  InstallationDate: Installed on 2019-10-03 (762 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to impish on 2021-10-17 (17 days ago)

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


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

[Desktop-packages] [Bug 1949621] Re: libmbim cannot make use of Quectel EM120

2021-11-03 Thread Pirouette Cacahuète

** Description changed:

  As reported on https://gitlab.freedesktop.org/mobile-
  broadband/ModemManager/-/issues/402, this modem (shipped in many new
  Lenovo ThinkPad laptops) requires some specific handling as others new
  modems to performs FCC unlock procedure.
  
  A fix has been merged upstream: https://gitlab.freedesktop.org/mobile-
  broadband/libmbim/-/merge_requests/125/diffs
  
  Can we expect to see that merged in the current Ubuntu 21.10 ?
+ 
+ I understand it might require a backport, since they merged it against
+ 1.26 and it does not seems to apply cleanly on 1.24. I also suspect
+ upgrading libmbim to 1.26 is not acceptable for impish release.

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

Title:
  libmbim cannot make use of Quectel EM120

Status in libmbim package in Ubuntu:
  New

Bug description:
  As reported on https://gitlab.freedesktop.org/mobile-
  broadband/ModemManager/-/issues/402, this modem (shipped in many new
  Lenovo ThinkPad laptops) requires some specific handling as others new
  modems to performs FCC unlock procedure.

  A fix has been merged upstream: https://gitlab.freedesktop.org/mobile-
  broadband/libmbim/-/merge_requests/125/diffs

  Can we expect to see that merged in the current Ubuntu 21.10 ?

  I understand it might require a backport, since they merged it against
  1.26 and it does not seems to apply cleanly on 1.24. I also suspect
  upgrading libmbim to 1.26 is not acceptable for impish release.

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


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

[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.

2021-11-03 Thread Treviño

** Also affects: mutter (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

** Changed in: mutter (Ubuntu Impish)
   Status: New => In Progress

** Changed in: mutter (Ubuntu Impish)
 Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn)

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

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

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

** Changed in: mutter (Ubuntu Focal)
 Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn)

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

Title:
  Xwayland crash in gdm as screen off and touchscreen detach.

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  In Progress
Status in mutter package in Ubuntu:
  In Progress
Status in mutter source package in Focal:
  In Progress
Status in mutter source package in Impish:
  In Progress

Bug description:
  [Impact]

   * Gdm crashed and user need to be an expert to know how to work around,
 or need to reboot to fix.

   * OEM projects got certain SKU that can reliably reproduce this
  issue.

   * A merged patch in upstream fix the race condition.

  [Test Plan]

   * Use the SKU that can reliably reproduce this issue.
   * Do a cold boot, and wait for 5 mins. The monitor should turned-black 
 but showing the Machine Vendor logo that was previously
 displayed by plythmouth.
   * Try to dog-food the deb from the proposed channel and make sure
 all input events still properly propagate.

  [Where problems could occur]

   * If the patch is not properly working as expected, per the file this
 patch touch, the user desktop session could stop responding to
 mouse, keyboard, and touch screen input.

  [Other Info]
   
   * Can't think of any for now.

  

  This is a reproducible issue. Step to reproduce
  1. cold boot into gdm login screen.
  2. wait for 5 mins, and the screen will be turned off. (also observed that 
the touchscreen USB device drop of a USB bus on the target machine)

  Note: this bug seems to be timing sensitive. I got an OEM project
  machine that can reproduce this issue (reproducible on several
  machines with the same HW design). The machine is using ADL CPU, which
  needs a patched 5.14 kernel. So I can't reproduce this on impish. With
  the backported mutter, I verified an upstream patch seems to fix this
  issue.

  Expected result:
  The screen just turns black.

  Actual result:
  Saw Vendor boot logo on the monitor (previous draw by plymouth during booting)

  Analysis as it happens:
  1. Saw "LGDisplay Incell Touch" drop off the USB bus.
     Kernel message like: "usb 1-9: USB disconnect, device number 6"
     as the screen turned black.
  2. There is no switch on virtual tty.
  3. journal log from Xwayland "wl_display@1: error 0: invalid object 24"
  4. Xwayland and gnome-shell process both die as this happens.
  5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and
     gnome-shell stop there for 30 more seconds.
  6. backtrace as Xwayland crashed:

  ```
  #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6
  #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6
  #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351
  #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872
  #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at 
../../../../os/log.c:1010
  #5 0x56437429c8b0 in xwl_log_handler (format=, 
args=) at ../../../../../hw/xwayland/xwayland.c:1312
  #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error 
%d: %s\n") at ../src/wayland-util.c:404
  #7 0x7f447c3cb78b in display_handle_error (data=, 
display=0x56437639f000, object=0x56437639f000, code=0, message=)
  at ../src/wayland-client.c:911
  #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7
  #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7
  #10 0x7f447c3cf3a8 in wl_closure_invoke 
(closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=,
  target@entry=0x56437639f000, opcode=opcode@entry=0, data=) 
at ../src/connection.c:1018
  #11 0x7f447c3cbc48 in dispatch_event 
(display=display@entry=0x56437639f000, queue=) at 
../src/wayland-client.c:1445
  #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, 
display=0x56437639f000) at ../src/wayland-client.c:1584
  #13 wl_display_dispatch_queue_pending (display=0x56437639f000, 
queue=0x56437639f0d0) at ../src/wayland-client.c:1833
  #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896
  #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at

[Desktop-packages] [Bug 1941752]

2021-11-03 Thread Cs-a

Mee too! Can't no longer view my photos saved by darktable...

Gwenview 21.08.2
Kubuntu 21.10
KDE Frameworks Version 5.87.0
Qt 5.15.2
libexiv2-27 0.27.3-3ubuntu4

$ gwenview dsc_0013_jf.jpg
org.kde.kdegraphics.gwenview.lib: Unresolved mime type  "image/x-mng"
org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type  "image/x-nikon-nrw"
org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type  
"image/x-samsung-srw"
terminate called after throwing an instance of 'std::out_of_range'
  what():  basic_string::at: __n (which is 19) >= this->size() (which is 19)
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = gwenview path = /usr/bin pid = 235591
KCrash: Arguments: /usr/bin/gwenview dsc_0013_jf.jpg 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi

[1]+  Angehalten  gwenview dsc_0013_jf.jpg


Application: Gwenview (gwenview), signal: Aborted

[KCrash Handler]
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140084165356608) 
at pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=140084165356608) at 
pthread_kill.c:80
#6  __GI___pthread_kill (threadid=140084165356608, signo=signo@entry=6) at 
pthread_kill.c:91
#7  0x7f67e85db476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
#8  0x7f67e85c17b7 in __GI_abort () at abort.c:79
#9  0x7f67e885ea31 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x7f67e886a4ec in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x7f67e886a557 in std::terminate() () from 
/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x7f67e886a7f9 in __cxa_throw () from 
/lib/x86_64-linux-gnu/libstdc++.so.6
#13 0x7f67e8861448 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#14 0x7f67e83967fd in ?? () from /lib/x86_64-linux-gnu/libexiv2.so.27
#15 0x7f67e833612d in Exiv2::Xmpdatum::write(std::ostream&, Exiv2::ExifData 
const*) const () from /lib/x86_64-linux-gnu/libexiv2.so.27
#16 0x7f67ea8fa6d6 in 
Gwenview::ImageMetaInfoModel::setExiv2Image(Exiv2::Image const*) () from 
/lib/x86_64-linux-gnu/libgwenviewlib.so.5
#17 0x7f67ea8bfcd0 in 
Gwenview::Document::setExiv2Image(std::unique_ptr >) () from 
/lib/x86_64-linux-gnu/libgwenviewlib.so.5
#18 0x7f67ea8cacab in ?? () from /lib/x86_64-linux-gnu/libgwenviewlib.so.5
#19 0x7f67e8cc6a53 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7f67e8aacec5 in QFutureWatcherBase::event(QEvent*) () from 
/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x7f67e99f66b3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x7f67e8c8f16a in QCoreApplication::notifyInternal2(QObject*, QEvent*) 
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7f67e8c92257 in QCoreApplicationPrivate::sendPostedEvents(QObject*, 
int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7f67e8ce8ef7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x7f67e63708bb in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7f67e63c3f08 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x7f67e636e003 in g_main_context_iteration () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x7f67e8ce8548 in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x7f67e8c8da9b in 
QEventLoop::exec(QFlags) () from 
/lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x7f67e8c96024 in QCoreApplication::exec() () from 
/lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x5646e78c5553 in ?? ()
#32 0x7f67e85c2fd0 in __libc_start_call_main 
(main=main@entry=0x5646e78c4fe0, argc=argc@entry=2, 
argv=argv@entry=0x7ffcec921388) at ../sysdeps/nptl/libc_start_call_main.h:58
#33 0x7f67e85c307d in __libc_start_main_impl (main=0x5646e78c4fe0, argc=2, 
argv=0x7ffcec921388, init=, fini=, 
rtld_fini=, stack_end=0x7ffcec921378) at ../csu/libc-start.c:409
#34 0x5646e78c5b75 in ?? ()
[Inferior 1 (process 235591) detached]

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

Title:
  Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening
  images exported by darktable

Status in Gwenview:
  Unknown
Status in exiv2 package in Ubuntu:
  Confirmed
Status in gwenview package in Ubuntu:
  Confirmed

Bug description:
  Since the recent security update of exiv2, Gwenview crashes when
  trying to open image files that got exported by darktable.

  Steps to reproduce:

  * Make a test installation of Kubuntu 21.04 in VirtualBox
  * Install all updates
  * Install darktable
  * Copy one of the images in /usr/share/wallpapers (or any other image) to 
your home directory and open it with darktable
  * Within darktable, export a copy of the image (no need to do any actual 
modifications)
  * Try to open that copy with Gwenview. Gwenview will crash.

  I'm attaching

[Desktop-packages] [Bug 1941752]

2021-11-03 Thread PascalC

Created attachment 143150
New crash information added by DrKonqi

gwenview (21.08.1) using Qt 5.15.2

- What I was doing when the application crashed:
I clicked on a PNG file on dolphin
gwenview opened the image
I cropped this image 
closed gwenview

clicked on another image on the same dir
gwenview opened the image
clicked on next image button on gwenview ==> this crash

- Unusual behavior I noticed:
now each time I click on an image on dolphin, gwenview crashes

-- Backtrace (Reduced):
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=139983886013632) 
at pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=139983886013632) at 
pthread_kill.c:80
#6  __GI___pthread_kill (threadid=139983886013632, signo=signo@entry=6) at 
pthread_kill.c:91
#7  0x7f508f3f7476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
#8  0x7f508f3dd7b7 in __GI_abort () at abort.c:79

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

Title:
  Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening
  images exported by darktable

Status in Gwenview:
  Unknown
Status in exiv2 package in Ubuntu:
  Confirmed
Status in gwenview package in Ubuntu:
  Confirmed

Bug description:
  Since the recent security update of exiv2, Gwenview crashes when
  trying to open image files that got exported by darktable.

  Steps to reproduce:

  * Make a test installation of Kubuntu 21.04 in VirtualBox
  * Install all updates
  * Install darktable
  * Copy one of the images in /usr/share/wallpapers (or any other image) to 
your home directory and open it with darktable
  * Within darktable, export a copy of the image (no need to do any actual 
modifications)
  * Try to open that copy with Gwenview. Gwenview will crash.

  I'm attaching a crash report hinting that this is related to exiv2.

  Temporary workaround:
  If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so 
it seems the crash is related to changes in 0.27.3-3ubuntu1.5.

  I don't know if the underlying cause is actually some bug in exiv2,
  Gwenview or darktable.

  Kind regards, Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libexiv2-27 0.27.3-3ubuntu1.5
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Aug 26 15:16:47 2021
  InstallationDate: Installed on 2021-08-26 (0 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: exiv2
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1949116] Re: libgl1-mesa-dri depends on libllvm12 from universe

2021-11-03 Thread Brian Murray

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

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

Title:
  libgl1-mesa-dri depends on libllvm12 from universe

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Hirsute:
  Fix Released

Bug description:
  It's not possible to install libgl1-mesa-dri from hirsute-updates (SRU
  bug 1932311) on a system that does not have universe enabled because
  it depends on libllvm12 from universe. This was not the case with the
  version of libgl1-mesa-dri in the release pocket because it depended
  upon libllvm11.

  (hirsute-amd64)root@impulse:~# apt-get install libgl1-mesa-dri
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgl1-mesa-dri : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

  (hirsute-amd64)root@impulse:~# apt-cache show libgl1-mesa-dri
  Package: libgl1-mesa-dri
  Architecture: amd64
  Version: 21.0.3-0ubuntu0.3
  Multi-Arch: same
  Priority: optional
  Section: libs
  Source: mesa
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian X Strike Force 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 37016
  Depends: libc6 (>= 2.33), libdrm-amdgpu1 (>= 2.4.100), libdrm-intel1 (>= 
2.4.38), libdrm-nouveau2 (>= 2.4.66), libdrm-radeon1 (>= 2.4.31),
  libdrm2 (>= 2.4.75), libelf1 (>= 0.142), libexpat1 (>= 2.0.1), libgcc-s1 (>= 
3.4), libglapi-mesa (= 21.0.3-0ubuntu0.3), libllvm12 (>= 1:9~s
  vn298832-1~), libsensors5 (>= 1:3.5.0), libstdc++6 (>= 5.2), libvulkan1 (>= 
1.2.131.2), libzstd1 (>= 1.3.2), zlib1g (>= 1:1.1.4)
  Filename: pool/main/m/mesa/libgl1-mesa-dri_21.0.3-0ubuntu0.3_amd64.deb

  This is blocking some CPC builds:
  
https://launchpad.net/~cloud-images/+livefs/ubuntu/hirsute/cpc-development/+build/306039

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


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

[Desktop-packages] [Bug 1949621] [NEW] libmbim cannot make use of Quectel EM120

2021-11-03 Thread Pirouette Cacahuète

Public bug reported:

As reported on https://gitlab.freedesktop.org/mobile-
broadband/ModemManager/-/issues/402, this modem (shipped in many new
Lenovo ThinkPad laptops) requires some specific handling as others new
modems to performs FCC unlock procedure.

A fix has been merged upstream: https://gitlab.freedesktop.org/mobile-
broadband/libmbim/-/merge_requests/125/diffs

Can we expect to see that merged in the current Ubuntu 21.10 ?

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


** Tags: hw-specific impish patch-accepted-upstream

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

Title:
  libmbim cannot make use of Quectel EM120

Status in libmbim package in Ubuntu:
  New

Bug description:
  As reported on https://gitlab.freedesktop.org/mobile-
  broadband/ModemManager/-/issues/402, this modem (shipped in many new
  Lenovo ThinkPad laptops) requires some specific handling as others new
  modems to performs FCC unlock procedure.

  A fix has been merged upstream: https://gitlab.freedesktop.org/mobile-
  broadband/libmbim/-/merge_requests/125/diffs

  Can we expect to see that merged in the current Ubuntu 21.10 ?

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


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

[Desktop-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

2021-11-03 Thread Olivier Tilloy

I can confirm that the chromium snap, as well as the official chrome
deb, are similarly affected (tested on stock Ubuntu 21.10).

** Summary changed:

- Saving downloads or pages is difficult because of unfocused file chooser 
dialog
+ [upstream] Saving downloads or pages is difficult because of unfocused file 
chooser dialog

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

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

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

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


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

[Desktop-packages] [Bug 1949598] Re: Wrong resolution on second monitor after resume from suspend

2021-11-03 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  Wrong resolution on second monitor after resume from suspend

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I am running Ubuntu 21.10 on wayland.

  I have two monitors connected to a AMD 5500xt, one via HDMI and
  another, the secondary, via DP, with an DP->VGA adaptor. This setup
  worked just fine on Ubuntu 21.04, also on wayland.

  After updating to 21.10, often (but not always) the secondary monitor
  wakes up showing a wrong, lower resolution. Instead of the normal
  1280x1024, it starts at 800x600. Despite this, in Gnome Settings the
  resolution is still reported as 1280x1024.

  I can solve this issue by changing the resolution in settings and
  reverting back to 1280x1024.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gnome-shell 40.5-1ubuntu2
  Uname: Linux 5.13.0-051300-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  3 11:44:16 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-11-04 (364 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to impish on 2021-10-03 (30 days ago)

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


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

[Desktop-packages] [Bug 1949598] [NEW] Wrong resolution on second monitor after resume from suspend

You have been subscribed to a public bug:

I am running Ubuntu 21.10 on wayland.

I have two monitors connected to a AMD 5500xt, one via HDMI and another,
the secondary, via DP, with an DP->VGA adaptor. This setup worked just
fine on Ubuntu 21.04, also on wayland.

After updating to 21.10, often (but not always) the secondary monitor
wakes up showing a wrong, lower resolution. Instead of the normal
1280x1024, it starts at 800x600. Despite this, in Gnome Settings the
resolution is still reported as 1280x1024.

I can solve this issue by changing the resolution in settings and
reverting back to 1280x1024.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.5-1ubuntu2
Uname: Linux 5.13.0-051300-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  3 11:44:16 2021
DisplayManager: gdm3
InstallationDate: Installed on 2020-11-04 (364 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
RelatedPackageVersions: mutter-common 40.5-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to impish on 2021-10-03 (30 days ago)

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


** Tags: amd64 apport-bug impish third-party-packages wayland-session
-- 
Wrong resolution on second monitor after resume from suspend
https://bugs.launchpad.net/bugs/1949598
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

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

[Desktop-packages] [Bug 1948778] Re: [Notebook N7x0WU] Random black flickers in gnome-shell Wayland sessions

2021-11-03 Thread lotuspsychje

Not sure if this would be relevant to this bug
but i can seem to reproduce a glitch inside gnomes systemsettings
toggle enable/disable the dock autohiding makes it glitch inside the 
systemsettings window

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

Title:
  [Notebook N7x0WU] Random black flickers in gnome-shell Wayland
  sessions

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.04 development branch up to date to latest @ 26/10/2021
  kernel 5.13.0-19-generic

  While working around on the desktop i'm getting short screen flashes like a 
screenshot style
  i cant reproduce them, they seem to come on random like every few minutes
  journal logs dont record anything while they occur

  this only happens on wayland, tested a long session on xorg where they
  dont occur

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 26 11:12:30 2021
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2021-10-23T19:12:47.175230

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


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

[Desktop-packages] [Bug 1949352] Re: [vmware] Removable drives are not auto-mounted after screen lock/unlock

2021-11-03 Thread István Váradi

Merge request created: https://gitlab.gnome.org/GNOME/gnome-
shell/-/merge_requests/2020

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

Title:
  [vmware] Removable drives are not auto-mounted after screen
  lock/unlock

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  If I lock and then unlock the screen, and then connect a removable
  drive, it is not recognized by the GNOME shell. The kernel logs show
  the drive, I can mount it manually, but it is not mounted
  automatically. The logged errors are attached.

  I could fix the issue by modifying the source code as given in the attached 
patch.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-11-01 (1 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell 40.5-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

2021-11-03 Thread Olivier Tilloy

The update to thunderbird 91 is tracked in bug #1949605.

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

Title:
  Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

Status in enigmail package in Ubuntu:
  Fix Released
Status in thunderbird package in Ubuntu:
  Fix Released
Status in enigmail source package in Bionic:
  Fix Released
Status in jsunit source package in Bionic:
  Fix Released
Status in thunderbird source package in Bionic:
  Fix Released
Status in enigmail source package in Focal:
  Fix Released
Status in jsunit source package in Focal:
  Fix Released
Status in thunderbird source package in Focal:
  Fix Released
Status in tinyjsd source package in Focal:
  Fix Released
Status in thunderbird source package in Groovy:
  Fix Released

Bug description:
  Upstream Thunderbird version 78.2.2 should be a candidate for
  backporting to stable Ubuntu releases.

  I've successfully built 78.2.1 against both with forcing nodejs
  version (20.04, 18.04) and disabling AV1 support due to too old nasm
  (18.04). Attaching debdiffs here.

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


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

[Desktop-packages] [Bug 1949352] Re: [vmware] Removable drives are not auto-mounted after screen lock/unlock

2021-11-03 Thread István Váradi

Please note, that while I created the apport report in a VM (actually
VirtualBox, no VMWare), the problem originally occurred on a native
installation. So I am not sure the vmware tag is relevant.

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

Title:
  [vmware] Removable drives are not auto-mounted after screen
  lock/unlock

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  If I lock and then unlock the screen, and then connect a removable
  drive, it is not recognized by the GNOME shell. The kernel logs show
  the drive, I can mount it manually, but it is not mounted
  automatically. The logged errors are attached.

  I could fix the issue by modifying the source code as given in the attached 
patch.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-11-01 (1 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell 40.5-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1949605] Re: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS

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

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

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

Title:
  Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS

Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Bionic:
  Confirmed
Status in thunderbird source package in Focal:
  Confirmed
Status in thunderbird source package in Hirsute:
  Confirmed

Bug description:
  Similarly to bug #1895643, which was about upgrading thunderbird from
  68 to 78 in all supported Ubuntu releases, this bug is to track the
  update from thunderbird 78 to 91 in hirsute, focal and bionic.

  The rationale is that series 78 will soon be out of support (the last
  release, 78.14.0, was made public on September 7, 2021).

  Thunderbird follows the Firefox ESR release cycle, and the
  next/current series is 91 (already available in impish and jammy).

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


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

[Desktop-packages] [Bug 1949605] Re: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS

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

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

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

Title:
  Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS

Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Bionic:
  Confirmed
Status in thunderbird source package in Focal:
  Confirmed
Status in thunderbird source package in Hirsute:
  Confirmed

Bug description:
  Similarly to bug #1895643, which was about upgrading thunderbird from
  68 to 78 in all supported Ubuntu releases, this bug is to track the
  update from thunderbird 78 to 91 in hirsute, focal and bionic.

  The rationale is that series 78 will soon be out of support (the last
  release, 78.14.0, was made public on September 7, 2021).

  Thunderbird follows the Firefox ESR release cycle, and the
  next/current series is 91 (already available in impish and jammy).

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


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

[Desktop-packages] [Bug 1949605] Re: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS

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

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

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

Title:
  Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS

Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Bionic:
  Confirmed
Status in thunderbird source package in Focal:
  Confirmed
Status in thunderbird source package in Hirsute:
  Confirmed

Bug description:
  Similarly to bug #1895643, which was about upgrading thunderbird from
  68 to 78 in all supported Ubuntu releases, this bug is to track the
  update from thunderbird 78 to 91 in hirsute, focal and bionic.

  The rationale is that series 78 will soon be out of support (the last
  release, 78.14.0, was made public on September 7, 2021).

  Thunderbird follows the Firefox ESR release cycle, and the
  next/current series is 91 (already available in impish and jammy).

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


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

[Desktop-packages] [Bug 1949605] [NEW] Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS

2021-11-03 Thread Olivier Tilloy

Public bug reported:

Similarly to bug #1895643, which was about upgrading thunderbird from 68
to 78 in all supported Ubuntu releases, this bug is to track the update
from thunderbird 78 to 91 in hirsute, focal and bionic.

The rationale is that series 78 will soon be out of support (the last
release, 78.14.0, was made public on September 7, 2021).

Thunderbird follows the Firefox ESR release cycle, and the next/current
series is 91 (already available in impish and jammy).

** Affects: thunderbird (Ubuntu)
 Importance: Undecided
 Assignee: Olivier Tilloy (osomon)
 Status: Fix Released

** Affects: thunderbird (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Olivier Tilloy (osomon)
 Status: Confirmed

** Affects: thunderbird (Ubuntu Focal)
 Importance: Undecided
 Assignee: Olivier Tilloy (osomon)
 Status: Confirmed

** Affects: thunderbird (Ubuntu Hirsute)
 Importance: Undecided
 Assignee: Olivier Tilloy (osomon)
 Status: Confirmed

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

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

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

** Also affects: thunderbird (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: thunderbird (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS

Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Bionic:
  Confirmed
Status in thunderbird source package in Focal:
  Confirmed
Status in thunderbird source package in Hirsute:
  Confirmed

Bug description:
  Similarly to bug #1895643, which was about upgrading thunderbird from
  68 to 78 in all supported Ubuntu releases, this bug is to track the
  update from thunderbird 78 to 91 in hirsute, focal and bionic.

  The rationale is that series 78 will soon be out of support (the last
  release, 78.14.0, was made public on September 7, 2021).

  Thunderbird follows the Firefox ESR release cycle, and the
  next/current series is 91 (already available in impish and jammy).

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


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

[Desktop-packages] [Bug 1948933] Re: [SRU] libreoffice 7.1.7 for hirsute

2021-11-03 Thread Rico Tzschichholz

** Description changed:

  [Impact]
  
-  * LibreOffice 7.1.7 is in its sixth bugfix release of the 7.1 line:
+  * LibreOffice 7.1.7 is in its seventh bugfix release of the 7.1 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.1#7.1.7_release
  
-  * Version 7.1.6 is currently released in hirsute. For a list of fixed bugs 
compared to 7.1.6 see the list of bugs fixed in the release candidates of 7.1.7 
(that's a total of ?? bugs):
+  * Version 7.1.6 is currently released in hirsute. For a list of fixed bugs 
compared to 7.1.6 see the list of bugs fixed in the release candidates of 7.1.7 
(that's a total of 27 bugs):
   https://wiki.documentfoundation.org/Releases/7.1.7/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.1.7/RC2#List_of_fixed_bugs
  
   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU a
  minor release rather than cherry-pick selected bug fixes.
  
  [Testing]
  
   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).
  
    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_71/1460/
  
    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests
    https://wiki.documentfoundation.org/Development/UITests
  * Regression tests
    https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
  * Feature tests
    https://wiki.documentfoundation.org/QA/Testing/Feature_Tests
  
   * Launchpad testing. The libreoffice packages include autopkgtests that were 
run and verified as passing.
  * [amd64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-ricotz-ppa/hirsute/amd64/libr/libreoffice/20211028_194503_1ee54@/log.gz
  * [arm64] 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-ricotz-ppa/hirsute/arm64/libr/libreoffice/20211028_113740_b763e@/log.gz
  * [armhf] 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-ricotz-ppa/hirsute/armhf/libr/libreoffice/20211029_170024_1bc17@/log.gz
  * [ppc64el] 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-ricotz-ppa/hirsute/ppc64el/libr/libreoffice/20211028_225613_de9da@/log.gz
  * [s390x] 
https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-ricotz-ppa/hirsute/s390x/libr/libreoffice/20211028_104330_62f27@/log.gz
  
   * General smoke testing of all the applications in the office suite
  were carried out by going through the manual testplan as documented by:
  https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice
  
  [Regression Potential]
  
-  * A minor release with a total of ?? bug fixes always carries the
+  * A minor release with a total of 27 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.
  
   * A combination of autopkgtests and careful smoke testing as described
  above should provide reasonable confidence that no regressions sneaked
  in.

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

Title:
   [SRU] libreoffice 7.1.7 for hirsute

Status in libreoffice package in Ubuntu:
  Triaged
Status in libreoffice source package in Hirsute:
  Triaged

Bug description:
  [Impact]

   * LibreOffice 7.1.7 is in its seventh bugfix release of the 7.1 line:
   https://wiki.documentfoundation.org/ReleasePlan/7.1#7.1.7_release

   * Version 7.1.6 is currently released in hirsute. For a list of fixed bugs 
compared to 7.1.6 see the list of bugs fixed in the release candidates of 7.1.7 
(that's a total of 27 bugs):
   https://wiki.documentfoundation.org/Releases/7.1.7/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/7.1.7/RC2#List_of_fixed_bugs

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

  [Testing]

   * Upstream testing. Bugs fixed upstream typically include
  unit/regression tests, and the release itself is extensively exercised
  (both in an automated manner and manually).

    * A recent set of upstream's automated jenkins testing can be found here:
  https://ci.libreoffice.org/job/gerrit_71/1460/

    * More information about the upstream QA testing can be found here:
  * Automated tests
    https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
  * Automated UI tests

[Desktop-packages] [Bug 1949116] Re: libgl1-mesa-dri depends on libllvm12 from universe

2021-11-03 Thread Łukasz Zemczak

Ok, promoted both the source and the one binary package:

$ change-override -c main -s hirsute-updates -t llvm-toolchain-12 
Override component to main
llvm-toolchain-12 1:12.0.0-3ubuntu1~21.04.2 in hirsute: universe/misc -> main
Override [y|N]? y
1 publication overridden.
$ change-override -c main -s hirsute-updates libllvm12 
Override component to main
libllvm12 1:12.0.0-3ubuntu1~21.04.2 in hirsute amd64: 
universe/libs/optional/100% -> main
libllvm12 1:12.0.0-3ubuntu1~21.04.2 in hirsute arm64: 
universe/libs/optional/100% -> main
libllvm12 1:12.0.0-3ubuntu1~21.04.2 in hirsute armhf: 
universe/libs/optional/100% -> main
libllvm12 1:12.0.0-3ubuntu1~21.04.2 in hirsute i386: 
universe/libs/optional/100% -> main
libllvm12 1:12.0.0-3ubuntu1~21.04.2 in hirsute ppc64el: 
universe/libs/optional/100% -> main
libllvm12 1:12.0.0-3ubuntu1~21.04.2 in hirsute riscv64: 
universe/libs/optional/100% -> main
libllvm12 1:12.0.0-3ubuntu1~21.04.2 in hirsute s390x: 
universe/libs/optional/100% -> main
Override [y|N]? y
7 publications overridden.

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

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

Title:
  libgl1-mesa-dri depends on libllvm12 from universe

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Hirsute:
  Fix Committed

Bug description:
  It's not possible to install libgl1-mesa-dri from hirsute-updates (SRU
  bug 1932311) on a system that does not have universe enabled because
  it depends on libllvm12 from universe. This was not the case with the
  version of libgl1-mesa-dri in the release pocket because it depended
  upon libllvm11.

  (hirsute-amd64)root@impulse:~# apt-get install libgl1-mesa-dri
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgl1-mesa-dri : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

  (hirsute-amd64)root@impulse:~# apt-cache show libgl1-mesa-dri
  Package: libgl1-mesa-dri
  Architecture: amd64
  Version: 21.0.3-0ubuntu0.3
  Multi-Arch: same
  Priority: optional
  Section: libs
  Source: mesa
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian X Strike Force 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 37016
  Depends: libc6 (>= 2.33), libdrm-amdgpu1 (>= 2.4.100), libdrm-intel1 (>= 
2.4.38), libdrm-nouveau2 (>= 2.4.66), libdrm-radeon1 (>= 2.4.31),
  libdrm2 (>= 2.4.75), libelf1 (>= 0.142), libexpat1 (>= 2.0.1), libgcc-s1 (>= 
3.4), libglapi-mesa (= 21.0.3-0ubuntu0.3), libllvm12 (>= 1:9~s
  vn298832-1~), libsensors5 (>= 1:3.5.0), libstdc++6 (>= 5.2), libvulkan1 (>= 
1.2.131.2), libzstd1 (>= 1.3.2), zlib1g (>= 1:1.1.4)
  Filename: pool/main/m/mesa/libgl1-mesa-dri_21.0.3-0ubuntu0.3_amd64.deb

  This is blocking some CPC builds:
  
https://launchpad.net/~cloud-images/+livefs/ubuntu/hirsute/cpc-development/+build/306039

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


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

[Desktop-packages] [Bug 1949116] Re: libgl1-mesa-dri depends on libllvm12 from universe

2021-11-03 Thread Łukasz Zemczak

Ok, promoting this, but I'll also make sure that the security team is
aware of that. Let's ping them.

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

Title:
  libgl1-mesa-dri depends on libllvm12 from universe

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Hirsute:
  Fix Committed

Bug description:
  It's not possible to install libgl1-mesa-dri from hirsute-updates (SRU
  bug 1932311) on a system that does not have universe enabled because
  it depends on libllvm12 from universe. This was not the case with the
  version of libgl1-mesa-dri in the release pocket because it depended
  upon libllvm11.

  (hirsute-amd64)root@impulse:~# apt-get install libgl1-mesa-dri
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgl1-mesa-dri : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

  (hirsute-amd64)root@impulse:~# apt-cache show libgl1-mesa-dri
  Package: libgl1-mesa-dri
  Architecture: amd64
  Version: 21.0.3-0ubuntu0.3
  Multi-Arch: same
  Priority: optional
  Section: libs
  Source: mesa
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian X Strike Force 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 37016
  Depends: libc6 (>= 2.33), libdrm-amdgpu1 (>= 2.4.100), libdrm-intel1 (>= 
2.4.38), libdrm-nouveau2 (>= 2.4.66), libdrm-radeon1 (>= 2.4.31),
  libdrm2 (>= 2.4.75), libelf1 (>= 0.142), libexpat1 (>= 2.0.1), libgcc-s1 (>= 
3.4), libglapi-mesa (= 21.0.3-0ubuntu0.3), libllvm12 (>= 1:9~s
  vn298832-1~), libsensors5 (>= 1:3.5.0), libstdc++6 (>= 5.2), libvulkan1 (>= 
1.2.131.2), libzstd1 (>= 1.3.2), zlib1g (>= 1:1.1.4)
  Filename: pool/main/m/mesa/libgl1-mesa-dri_21.0.3-0ubuntu0.3_amd64.deb

  This is blocking some CPC builds:
  
https://launchpad.net/~cloud-images/+livefs/ubuntu/hirsute/cpc-development/+build/306039

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


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

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

2021-11-03 Thread Kreaninw

@JackyOhh and @dharman

I didn't do anything at all. It just works out of the box for me.
However, you might try to increase the mic volume with PulseAudio Volume
Control.

And now, I have another problem (which I had never tested it before),
there is no audio output through HDMI. I reported the bug here:
https://bugzilla.kernel.org/show_bug.cgi?id=214923


** Bug watch added: Linux Kernel Bug Tracker #214923
   https://bugzilla.kernel.org/show_bug.cgi?id=214923

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

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

Status in alsa-driver package in Ubuntu:
  Confirmed

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

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

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

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

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

  Here's some info:

  lspci | grep -I audio:

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

  cat /proc/asound/cards:

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

  And a clip from dmesg | grep snd:

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

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

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

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


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

[Desktop-packages] [Bug 397269] Re: HDMI audio cuts out intermittently while normal audio plays fine

2021-11-03 Thread Dee Winthrop

For the record I have the same problem on a Huawei Matebook Pro using
Ubuntu 20.04 - fully upgraded. But the computer uses an HDMI adapter.
Could that be the problem?

Again for the record, on another computer with Ubuntu 21.04 (Waylabd),
everything works fine.

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

Title:
  HDMI audio cuts out intermittently while normal audio plays fine

Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: pulseaudio

  I have my audio set up to play through my laptop speakers and over
  HDMI to my television. In Jaunty this works fine while in Karmic the
  HDMI audio will intermittently cut out for a split second a few times
  a minute. During this time however the audio over the laptop speakers
  plays just fine. It just seems as if a frame of the HDMI audio gets
  dropped randomly. The video over the HDMI is perfectly fine, FYI.

  ProblemType: Bug
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael4942 f mixer_applet2
michael7360 F npviewer.bin
   /dev/snd/pcmC0D0p:   michael7360 F...m npviewer.bin
   /dev/snd/timer:  michael7360 F npviewer.bin
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf6ffc000 irq 21'
 Mixer name : 'SigmaTel STAC9228'
 Components : 'HDA:83847616,10280209,00100402'
 Controls  : 28
 Simple ctrls  : 18
  Date: Wed Jul  8 21:20:16 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia wl
  Package: pulseaudio 1:0.9.15-4ubuntu1
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.30-10.12-generic
  SourcePackage: pulseaudio
  Uname: Linux 2.6.30-10-generic x86_64

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


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

[Desktop-packages] [Bug 1948392] Re: [MIR] wsl-setup

2021-11-03 Thread Didier Roche

$ ./change-override -c main -S wsl-setup
Override component to main
wsl-setup 0.1.1 in jammy: universe/admin -> main
wsl-setup 0.1.1 in jammy amd64: universe/admin/optional/100% -> main
wsl-setup 0.1.1 in jammy arm64: universe/admin/optional/100% -> main
wsl-setup 0.1.1 in jammy armhf: universe/admin/optional/100% -> main
wsl-setup 0.1.1 in jammy i386: universe/admin/optional/100% -> main
wsl-setup 0.1.1 in jammy ppc64el: universe/admin/optional/100% -> main
wsl-setup 0.1.1 in jammy riscv64: universe/admin/optional/100% -> main
wsl-setup 0.1.1 in jammy s390x: universe/admin/optional/100% -> main
Override [y|N]? y
8 publications overridden.


** Changed in: wsl-setup (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [MIR] wsl-setup

Status in wsl-setup package in Ubuntu:
  Fix Released

Bug description:
  [Availability]

  Built for all supported architectures. starting from jammy. It is a
  simple arch-independent package.

  [Rationale]
  On WSL, we have an out of the box experience UI. This one is based on 
ubuntu-desktop-installer (which includes subiquity) on a classic snap.
  However, WSL doesn’t have systemd/apparmor (and so snap) support. For 22.04 
LTS, we plan thus on mimicking a snap environment before executing the binaries 
in the snap itself. There is no confinement planned here, just shipping all 
dependencies that way before being able to switch to a more classic snap 
behavior in future WSL releases.

  This script is thus preparing this, mounting all needed snaps
  (core/theme/installer) before exporting needed environment variables
  for the snap and chaining to the binary within the snap. There is no
  specific changes for this in the snap.

  This package will be seeded on WSL.

  [Security]

  No known security issues

  There is no CVE, as being a new package, as of today. The script, even
  if ran as root on first setup, is using set -eu, and does basic things
  like mounting, bind mount, directory creation and export environment
  variables.

  [Quality assurance]

  There is no tests for this script, but we plan as part of our 22.04 LTS 
roadmap to have automated installation tests as part of our CI and daily builds.
  This will thus provision the machine, execute the Windows launcher executable 
which will chain into that script, which will itself chain to the snap, 
proceeding the OOBE experience. Consequently, failures will be quickly detected.

  There is no bugs opened as of today, as it’s a new package, and it’s
  only used by devs localy until we can seed it.

  On the packaging itself, this one is really trivial, and only ship one 
script. No postinst, no debconf questions.
  Note about the false lintian positive W: wsl-setup source: unknown-field 
wsl-setup_0.1.dsc Description, which is supported to fill the binary packages 
description with it.

  [UI standards]

  No UI as part of this script itself.

  [Dependencies]

  No dependency. Note that we don’t install the needed snaps on purpose
  in postinst. The snaps will be directly seeded. This is to prevent
  installation failure on system without snap support.

  
  [Standards compliance]

  Use current Standards-Version and dh 13

  [Maintenance]

  The desktop team, as being responsible for WSL will maintain this
  package.

  
  [Background information]
  This script is called by the Windows launcher directly and should not be 
called directly by the user. This is why it ends up in libexec.

  The plan is to phase out this script once we get snap support on WSL
  (but this is dependent on Microsoft’s roadmap).

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


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

[Desktop-packages] [Bug 1949490] Re: Grub doesn’t fully revert ZFS snapshots

2021-11-03 Thread Julian Andres Klode

Reassigning to zsys, but also closing tentatively as opinion, as the
snapshot has not been made using zsys, so this seems like it is out of
scope.

** Package changed: grub2 (Ubuntu) => zsys (Ubuntu)

** Changed in: zsys (Ubuntu)
   Status: New => Opinion

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

Title:
  Grub doesn’t fully revert ZFS snapshots

Status in zsys package in Ubuntu:
  Opinion

Bug description:
  To reproduce this bug, take the following steps

  Install Ubuntu 20.04.3 using a ZFS-based root.
  Boot into it and get past the initial startup screens.
  Take a manual recursive zfs snapshot like so

  zfs snapshot -r rpool@beforeanything

  Now touch a file on the desktop and install a package like htop.

  You should see the file and htop should be able to run.

  Reboot and hit escape to enter the grub screen. Choose the history
  menu and choose the snapshot you just created. Then hit enter and then
  choose the option to revert system and user data and then enter again.

  If it were working correctly, everything should be reverted. There’d
  be no file on the desktop and no trace of htop.

  That’s not what occurs. The file on the desktop is still there, and
  while htop is no longer installed, the package management seems to
  think it is.

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


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

[Desktop-packages] [Bug 1949490] [NEW] Grub doesn’t fully revert ZFS snapshots

You have been subscribed to a public bug:

To reproduce this bug, take the following steps

Install Ubuntu 20.04.3 using a ZFS-based root.
Boot into it and get past the initial startup screens.
Take a manual recursive zfs snapshot like so

zfs snapshot -r rpool@beforeanything

Now touch a file on the desktop and install a package like htop.

You should see the file and htop should be able to run.

Reboot and hit escape to enter the grub screen. Choose the history menu
and choose the snapshot you just created. Then hit enter and then choose
the option to revert system and user data and then enter again.

If it were working correctly, everything should be reverted. There’d be
no file on the desktop and no trace of htop.

That’s not what occurs. The file on the desktop is still there, and
while htop is no longer installed, the package management seems to think
it is.

** Affects: zsys (Ubuntu)
 Importance: Undecided
 Status: Opinion

-- 
Grub doesn’t fully revert ZFS snapshots
https://bugs.launchpad.net/bugs/1949490
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to zsys in Ubuntu.

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

[Desktop-packages] [Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.

2021-11-03 Thread Robie Basak

OK, so you currently have nothing in your Test Plan to verify this part
of the changes you're proposing? Please either fix the Test Plan, or if
testing this is impractical for some reason then we can discuss that and
decide what mitigation might be appropriate, but in this case the
omission and conclusion should be documented in this bug - presumably in
the "Where problems could occur" section.

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

Title:
Support manual firmware upgrading for Foxconn and Quectel modems.

Status in OEM Priority Project:
In Progress
Status in modemmanager package in Ubuntu:
New

Bug description:
[Impact]

The modem certification requires that different modem firmware is used for
different network carrier.
This needs the firmware upgrading capability during the modem certification
process.

The modem manufacture vendors (Foxconn and Quectel) provided utilities to do
modem's firmware upgrading manually.(LP#1943774, LP#1943780)
These utilities are verified to be working when the recent versions(> v
1.18.2) of ModemManager are used with.

To support manual firmware upgrading on the current Focal release which is
using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2.
The requested upstream patches are listed as below:
* for Quectel EM160 4G
**
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2
* for Foxconn T99W175
**
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9
**https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b
**
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371
**
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a
**
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154

The firmware upgrading was verified using the patched ModemManager v 1.16.6
with the following 2 modems:
* Foxconn SDX55 T99W175 5G sub6 PCIE Modem
* Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

[Test Plan]

1. Install the Ubuntu image.
2. Boot and login the system.
3. Prepare the modem’s firmware and install the firmware upgrading
application provided by Foxconn and Quectel
4. Using the firmware upgrading application to upgrade the modem’s firmware
5. Verify if the modem’s firmware upgrading is successful
6. Reboot
7. Verify if the upgraded modem firmware is still working

[Where problems could occur]

The requested upstream patches are for these 2 specific modems.
This should not affect existing generic functions and other modems.

[Other Info]

The firmware and the upgrading utilities can be downloaded from the following
link:
* LP#1943774 for Quectel modems
* LP#1943780 for Foxconn modems

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

[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

2021-11-03 Thread Simon Iremonger

For what it is worth, this problem is now back -- very soon need the
Thunderbird 91.3 installed into Ubuntu as 78.x is about at EOL.  Debian
have already prepared their packages in Sid (91.2.1 and 91.3.x no doubt
shortly to follow).  They also offer firefox-esr and do similar work
with that packaging.

I recall there was a suggestion/bug/discussion about sharing resources on ESR 
for at least Thunderbird, to save duplicate resources, not sure where that got 
to.
I am writing to this bug just to notify likely-relevant people, but if this 
isn't happening and needs a bug-report, please start a new bug report and link 
it to this bug, as this has got long and complex already!.

With many thanks,

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

Title:
  Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

Status in enigmail package in Ubuntu:
  Fix Released
Status in thunderbird package in Ubuntu:
  Fix Released
Status in enigmail source package in Bionic:
  Fix Released
Status in jsunit source package in Bionic:
  Fix Released
Status in thunderbird source package in Bionic:
  Fix Released
Status in enigmail source package in Focal:
  Fix Released
Status in jsunit source package in Focal:
  Fix Released
Status in thunderbird source package in Focal:
  Fix Released
Status in tinyjsd source package in Focal:
  Fix Released
Status in thunderbird source package in Groovy:
  Fix Released

Bug description:
  Upstream Thunderbird version 78.2.2 should be a candidate for
  backporting to stable Ubuntu releases.

  I've successfully built 78.2.1 against both with forcing nodejs
  version (20.04, 18.04) and disabling AV1 support due to too old nasm
  (18.04). Attaching debdiffs here.

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


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

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

2021-11-03 Thread dharman

@Kreaninw, I've your same device but as @JackyOhh, I've tried a fresh
USB-Live 21.10 without sound nor mic working. Can you say us how it
worked for you? Thanks!

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

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

Status in alsa-driver package in Ubuntu:
  Confirmed

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

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

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

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

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

  Here's some info:

  lspci | grep -I audio:

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

  cat /proc/asound/cards:

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

  And a clip from dmesg | grep snd:

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

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

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

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


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

[Desktop-packages] [Bug 1949572] HookError_ubuntu.txt

apport information

** Attachment added: "HookError_ubuntu.txt"
   
https://bugs.launchpad.net/bugs/1949572/+attachment/5537863/+files/HookError_ubuntu.txt

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

Title:
  freeze after back-to-back left and right click on the app in the dock

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

Bug description:
  When you click the icon of the app in the dock to open it for the
  first time and then immediately right click to see options, everything
  freezes and you are forced to reboot.

  I'm using Ubuntu 21.10. I installed it today.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-11-03 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

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

apport information

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

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

Title:
  freeze after back-to-back left and right click on the app in the dock

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

Bug description:
  When you click the icon of the app in the dock to open it for the
  first time and then immediately right click to see options, everything
  freezes and you are forced to reboot.

  I'm using Ubuntu 21.10. I installed it today.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-11-03 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

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

2021-11-03 Thread JackyOhh

No luck here. I booted a fresh Ubuntu 21.10 from USB. Although internal mic 
showed up, no sound was recognized on Acer Aspire VN7-592G. 
@Kreaninw Did you change anything in /etc/modprobe.d/alsa-base.conf or 
elsewhere?

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

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

Status in alsa-driver package in Ubuntu:
  Confirmed

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

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

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

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

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

  Here's some info:

  lspci | grep -I audio:

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

  cat /proc/asound/cards:

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

  And a clip from dmesg | grep snd:

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

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

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

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


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

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

apport information

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

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

Title:
  freeze after back-to-back left and right click on the app in the dock

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

Bug description:
  When you click the icon of the app in the dock to open it for the
  first time and then immediately right click to see options, everything
  freezes and you are forced to reboot.

  I'm using Ubuntu 21.10. I installed it today.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-11-03 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1949572] Re: freeze after back-to-back left and right click on the app in the dock

apport information

** Tags added: apport-collected impish wayland-session

** Description changed:

  When you click the icon of the app in the dock to open it for the first
  time and then immediately right click to see options, everything freezes
  and you are forced to reboot.
  
  I'm using Ubuntu 21.10. I installed it today.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu71
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 21.10
+ InstallationDate: Installed on 2021-11-03 (0 days ago)
+ InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
+ Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
+ PackageArchitecture: all
+ ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
+ Tags:  impish wayland-session
+ Uname: Linux 5.13.0-20-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  freeze after back-to-back left and right click on the app in the dock

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

Bug description:
  When you click the icon of the app in the dock to open it for the
  first time and then immediately right click to see options, everything
  freezes and you are forced to reboot.

  I'm using Ubuntu 21.10. I installed it today.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-11-03 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Tags:  impish wayland-session
  Uname: Linux 5.13.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 1949572] Re: freeze after back-to-back left and right click on the app in the dock

2021-11-03 Thread lotuspsychje

Thank you to report this bug and make Ubuntu better!

In order to be able to debug your better, please use apport-collect 1949572 
from a terminal
to pull relevant info into your bug.

Thank you!

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

Title:
  freeze after back-to-back left and right click on the app in the dock

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

Bug description:
  When you click the icon of the app in the dock to open it for the
  first time and then immediately right click to see options, everything
  freezes and you are forced to reboot.

  I'm using Ubuntu 21.10. I installed it today.

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


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

[Desktop-packages] [Bug 1949572] [NEW] freeze after back-to-back left and right click on the app in the dock

Public bug reported:

When you click the icon of the app in the dock to open it for the first
time and then immediately right click to see options, everything freezes
and you are forced to reboot.

I'm using Ubuntu 21.10. I installed it today.

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

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

Title:
  freeze after back-to-back left and right click on the app in the dock

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

Bug description:
  When you click the icon of the app in the dock to open it for the
  first time and then immediately right click to see options, everything
  freezes and you are forced to reboot.

  I'm using Ubuntu 21.10. I installed it today.

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


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

[Desktop-packages] [Bug 1948778] Re: [Notebook N7x0WU] Random black flickers in gnome-shell Wayland sessions

2021-11-03 Thread lotuspsychje

I tried booting with quiet splash intel_idle.max_cstate=4 like my old
flickering bug, but no luck the flashes seem to persist

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

Title:
  [Notebook N7x0WU] Random black flickers in gnome-shell Wayland
  sessions

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.04 development branch up to date to latest @ 26/10/2021
  kernel 5.13.0-19-generic

  While working around on the desktop i'm getting short screen flashes like a 
screenshot style
  i cant reproduce them, they seem to come on random like every few minutes
  journal logs dont record anything while they occur

  this only happens on wayland, tested a long session on xorg where they
  dont occur

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 26 11:12:30 2021
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2021-10-23T19:12:47.175230

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


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

[Desktop-packages] [Bug 1917037] Re: Frozen screen (NVidia GM107 card with large 3840 × 2160 screen)

2021-11-03 Thread Dimitri Papadopoulos

Dell also changed the motherboard of the workstation last week. No more
freezing since that change, fingers crossed 爛

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

Title:
  Frozen screen (NVidia GM107 card with large 3840 × 2160 screen)

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

Bug description:
  Just after the screen freezes, I am sometimes able to log in with SSH
  and the log file typically reads:

  Feb 26 11:18:15 is233895 kernel: [15385.625416] nouveau :01:00.0: fifo: 
SCHED_ERROR 0a [CTXSW_TIMEOUT]
  Feb 26 11:18:15 is233895 kernel: [15385.625436] nouveau :01:00.0: fifo: 
runlist 0: scheduled for recovery
  Feb 26 11:18:15 is233895 kernel: [15385.625453] nouveau :01:00.0: fifo: 
channel 6: killed
  Feb 26 11:18:15 is233895 kernel: [15385.625462] nouveau :01:00.0: fifo: 
engine 5: scheduled for recovery
  Feb 26 11:18:15 is233895 kernel: [15385.625467] nouveau :01:00.0: fifo: 
engine 0: scheduled for recovery
  Feb 26 11:18:15 is233895 kernel: [15385.626095] nouveau :01:00.0: 
Xorg[2366]: channel 6 killed!

  However, the machine eventually locks up and I cannot log in with SSH
  any more. Then I need to power down the computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 26 11:45:55 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed
   virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GM107GL [Quadro K1200] [10de:13bc] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GM107GL [Quadro K1200] [10de:1140]
  InstallationDate: Installed on 2020-04-09 (322 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Dell Inc. Precision Tower 3620
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-66-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.16.2
  dmi.board.name: 0MWYPT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.16.2:bd08/13/2020:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn0MWYPT:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision Tower 3620
  dmi.product.sku: 06B7
  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/xserver-xorg-video-nouveau/+bug/1917037/+subscriptions


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

[Desktop-packages] [Bug 1949116] Re: libgl1-mesa-dri depends on libllvm12 from universe

** Also affects: mesa (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

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

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

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

Title:
  libgl1-mesa-dri depends on libllvm12 from universe

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Hirsute:
  New

Bug description:
  It's not possible to install libgl1-mesa-dri from hirsute-updates (SRU
  bug 1932311) on a system that does not have universe enabled because
  it depends on libllvm12 from universe. This was not the case with the
  version of libgl1-mesa-dri in the release pocket because it depended
  upon libllvm11.

  (hirsute-amd64)root@impulse:~# apt-get install libgl1-mesa-dri
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgl1-mesa-dri : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

  (hirsute-amd64)root@impulse:~# apt-cache show libgl1-mesa-dri
  Package: libgl1-mesa-dri
  Architecture: amd64
  Version: 21.0.3-0ubuntu0.3
  Multi-Arch: same
  Priority: optional
  Section: libs
  Source: mesa
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian X Strike Force 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 37016
  Depends: libc6 (>= 2.33), libdrm-amdgpu1 (>= 2.4.100), libdrm-intel1 (>= 
2.4.38), libdrm-nouveau2 (>= 2.4.66), libdrm-radeon1 (>= 2.4.31),
  libdrm2 (>= 2.4.75), libelf1 (>= 0.142), libexpat1 (>= 2.0.1), libgcc-s1 (>= 
3.4), libglapi-mesa (= 21.0.3-0ubuntu0.3), libllvm12 (>= 1:9~s
  vn298832-1~), libsensors5 (>= 1:3.5.0), libstdc++6 (>= 5.2), libvulkan1 (>= 
1.2.131.2), libzstd1 (>= 1.3.2), zlib1g (>= 1:1.1.4)
  Filename: pool/main/m/mesa/libgl1-mesa-dri_21.0.3-0ubuntu0.3_amd64.deb

  This is blocking some CPC builds:
  
https://launchpad.net/~cloud-images/+livefs/ubuntu/hirsute/cpc-development/+build/306039

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


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

[Desktop-packages] [Bug 1943816] Re: "ubuntu-drivers install" needs to be used when installing nvidia-driver if enabling "third-party packages"

2021-11-03 Thread Ubuntu Foundations Team Bug Bot

The attachment "ubuntu-drivers-common_0.9.0~0.20.04.3.debdiff" seems to
be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug
report so that they can review and hopefully sponsor the debdiff.  If
the attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  "ubuntu-drivers install" needs to be used when installing nvidia-
  driver if enabling "third-party packages"

Status in OEM Priority Project:
  Confirmed
Status in subiquity:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released

Bug description:
  ubiquity calls
  ```
  ubuntu-drivers install $FREEONLY $NOOEM --package-list 
/run/ubuntu-drivers.autoinstall
  ```
  to generate package list during live system but "ubuntu-drivers install" not 
only install packages but also create some config files for switching nvidia 
mode (e.g. on-demand) and change the runtime config as well (e.g. modify the 
iniramfs).

  Thus, not only package list needs to be referred but also the
  configuration.

  ---

  In ubuntu-drivers-common, which read the "/run/ubuntu-drivers.autoinstall" to 
install package. It also skipping the nvidia-mode changing (made by 
ubuntu-drivers install).
  ```
  $ cat ubiquity/target-config/31ubuntu_driver_packages
  #!/bin/sh
  set -e

  # install all packages that "ubuntu-drivers autoinstall" installed into the
  # live system. Ubiquity calls this with --package-list 
/run/ubuntu-drivers.autoinstall

  PKGLIST=/run/ubuntu-drivers.autoinstall
  [ -e $PKGLIST ] || exit 0

  for p in `cat $PKGLIST`; do
  apt-install $p
  done
  ```

  ---

  We need to use a same approach to make sure the nvidia mode is same on
  a same system (either all handing by ubuntu-drivers install or change
  the logic to maintainer script in each package).

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


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

[Desktop-packages] [Bug 1943816] Re: "ubuntu-drivers install" needs to be used when installing nvidia-driver if enabling "third-party packages"

debdiff for focal

** Patch added: "ubuntu-drivers-common_0.9.0~0.20.04.3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1943816/+attachment/5537831/+files/ubuntu-drivers-common_0.9.0~0.20.04.3.debdiff

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

Title:
  "ubuntu-drivers install" needs to be used when installing nvidia-
  driver if enabling "third-party packages"

Status in OEM Priority Project:
  Confirmed
Status in subiquity:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released

Bug description:
  ubiquity calls
  ```
  ubuntu-drivers install $FREEONLY $NOOEM --package-list 
/run/ubuntu-drivers.autoinstall
  ```
  to generate package list during live system but "ubuntu-drivers install" not 
only install packages but also create some config files for switching nvidia 
mode (e.g. on-demand) and change the runtime config as well (e.g. modify the 
iniramfs).

  Thus, not only package list needs to be referred but also the
  configuration.

  ---

  In ubuntu-drivers-common, which read the "/run/ubuntu-drivers.autoinstall" to 
install package. It also skipping the nvidia-mode changing (made by 
ubuntu-drivers install).
  ```
  $ cat ubiquity/target-config/31ubuntu_driver_packages
  #!/bin/sh
  set -e

  # install all packages that "ubuntu-drivers autoinstall" installed into the
  # live system. Ubiquity calls this with --package-list 
/run/ubuntu-drivers.autoinstall

  PKGLIST=/run/ubuntu-drivers.autoinstall
  [ -e $PKGLIST ] || exit 0

  for p in `cat $PKGLIST`; do
  apt-install $p
  done
  ```

  ---

  We need to use a same approach to make sure the nvidia mode is same on
  a same system (either all handing by ubuntu-drivers install or change
  the logic to maintainer script in each package).

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


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

[Desktop-packages] [Bug 1947820] Re: [SRU] Backport xorg-server 1.20.13 to focal

** Project changed: xorg-server => xorg-server (Ubuntu)

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

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

** Changed in: xorg-server (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  [SRU] Backport xorg-server 1.20.13  to focal

Status in OEM Priority Project:
  Triaged
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server source package in Focal:
  New

Bug description:
  [Impact]
  The delay phenomenon is serious in 'External display mode' during the 
'On-demand' mode working.
  Please reference lp:1940247 and lp:1919118.

  [Fix]
   I installed 21.10 on Raptor12(ThinkPad-P15-Gen-2i), with xorg-server 
2:1.20.13-1ubuntu1 and nvidia-495.38 test driver, this issue is solved. But in 
20.04, it's still 2:1.20.11-1ubuntu1~20.04.2.

  [Test]
  On Raptor12(ThinkPad-P15-Gen-2i), P17 Gen 2 and P1 Gen 4, with latest 20.04, 
it could be reproduced.

  [Where problems could occur]
  Although the nvidia driver is not released, I thought it's no harm to upgrade 
xorg-server first.

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


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

[Desktop-packages] [Bug 1949558] [NEW] Lesstif has been replaced by LGPL Motif, please update package description

2021-11-03 Thread Janne Blomqvist

Public bug reported:

The package description for the libxt-* packages says:

 libXt provides the X Toolkit Intrinsics, an abstract widget library upon
 which other toolkits are based.  Xt is the basis for many toolkits, including
 the Athena widgets (Xaw), and LessTif (a Motif implementation).

Lesstif was abandoned after Motif was open sourced in 2012, and indeed
the Lesstif library is no longer packaged in either Debian or Ubuntu as
Lesstif-using packages have been updated to link to motif (libxm4).
Please remove mention of Lesstif.

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

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

Title:
  Lesstif has been replaced by LGPL Motif, please update package
  description

Status in libxt package in Ubuntu:
  New

Bug description:
  The package description for the libxt-* packages says:

   libXt provides the X Toolkit Intrinsics, an abstract widget library upon
   which other toolkits are based.  Xt is the basis for many toolkits, including
   the Athena widgets (Xaw), and LessTif (a Motif implementation).

  Lesstif was abandoned after Motif was open sourced in 2012, and indeed
  the Lesstif library is no longer packaged in either Debian or Ubuntu
  as Lesstif-using packages have been updated to link to motif (libxm4).
  Please remove mention of Lesstif.

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


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

[Desktop-packages] [Bug 1947820] Re: [SRU] Backport xorg-server 1.20.13 to focal

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

** Changed in: xorg-server (Ubuntu)
   Status: New => 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/1947820

Title:
  [SRU] Backport xorg-server 1.20.13  to focal

Status in OEM Priority Project:
  Triaged
Status in xorg-server package in Ubuntu:
  Invalid
Status in xorg-server source package in Focal:
  New

Bug description:
  [Impact]
  The delay phenomenon is serious in 'External display mode' during the 
'On-demand' mode working.
  Please reference lp:1940247 and lp:1919118.

  [Fix]
   I installed 21.10 on Raptor12(ThinkPad-P15-Gen-2i), with xorg-server 
2:1.20.13-1ubuntu1 and nvidia-495.38 test driver, this issue is solved. But in 
20.04, it's still 2:1.20.11-1ubuntu1~20.04.2.

  [Test]
  On Raptor12(ThinkPad-P15-Gen-2i), P17 Gen 2 and P1 Gen 4, with latest 20.04, 
it could be reproduced.

  [Where problems could occur]
  Although the nvidia driver is not released, I thought it's no harm to upgrade 
xorg-server first.

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


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

[Desktop-packages] [Bug 1946434] Re: SRU: Set on-demand as default, enable RTD3 only on laptops and decouple on-demand with RTD3

** Description changed:

  [Impact]
  
   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
  
  [Test Plan]
  
-  * Install 20.04.3 with "Third-party packages". After the installation, 
reboot the system. Execute "prime-select query" should get "on-demand"
+  * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU 
driver. After the installation, reboot the system. Execute "prime-select query" 
should get "on-demand"
   * On non-laptop machine. Can set GPU mode to on-demand
   * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
  
  [Where problems could occur]
  
   * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
   * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.
  
  [Other Info]
  
  Changelogs:
  
  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium
  
-   [ Jeremy Szu ]
-   * Set on-demand mode as default nvidia mode (LP: #1942307)
+   [ Jeremy Szu ]
+   * Set on-demand mode as default nvidia mode (LP: #1942307)
  
-   [ Alberto Milone ]
-   * prime-select:
- - Detect chassis type and enable RTD3 only
-   on laptops (LP: #1942788).
- - on-demand mode doesn't need to depend on
-   RTD3 (LP: #1942789).
- - Use bootvga detection when last_gfx_boot
-   is not available.
- - Don't check the current profile when setting
-   a profile (LP: #1946476).
- - Catch BrokenPipeError.
- - Use bootvga detection when last_gfx_boot is
-   not available.
- 
+   [ Alberto Milone ]
+   * prime-select:
+ - Detect chassis type and enable RTD3 only
+   on laptops (LP: #1942788).
+ - on-demand mode doesn't need to depend on
+   RTD3 (LP: #1942789).
+ - Use bootvga detection when last_gfx_boot
+   is not available.
+ - Don't check the current profile when setting
+   a profile (LP: #1946476).
+ - Catch BrokenPipeError.
+ - Use bootvga detection when last_gfx_boot is
+   not available.
  
  nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium
  
-   [ Jeremy Szu ]
-   * Set on-demand mode as default nvidia mode (LP: #1942307)
+   [ Jeremy Szu ]
+   * Set on-demand mode as default nvidia mode (LP: #1942307)
  
-   [ Alberto Milone ]
-   * prime-select:
- - Detect chassis type and enable RTD3 only
-   on laptops (LP: #1942788).
- - on-demand mode doesn't need to depend on
-   RTD3 (LP: #1942789).
- - Use bootvga detection when last_gfx_boot
-   is not available.
- - Don't check the current profile when setting
-   a profile (LP: #1946476).
+   [ Alberto Milone ]
+   * prime-select:
+ - Detect chassis type and enable RTD3 only
+   on laptops (LP: #1942788).
+ - on-demand mode doesn't need to depend on
+   RTD3 (LP: #1942789).
+ - Use bootvga detection when last_gfx_boot
+   is not available.
+ - Don't check the current profile when setting
+   a profile (LP: #1946476).

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

Title:
  SRU: Set on-demand as default, enable RTD3 only on laptops and
  decouple on-demand with RTD3

Status in OEM Priority Project:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  Invalid
Status in nvidia-prime source package in Focal:
  In Progress
Status in nvidia-prime source package in Hirsute:
  In Progress

Bug description:
  [Impact]

   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine

  [Test Plan]

   * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU 
driver. After the installation, reboot the system. Execute "prime-select query" 
should get "on-demand"
   * On non-laptop machine. Can set GPU mode to on-demand
   * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"

  [Where problems could occur]

   * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
   * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.

  [Other Info]

  Changelogs:

  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium

    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)

    [ Alberto Milone ]
    * prime-select:
  - Detect

[Desktop-packages] [Bug 1947820] [NEW] [SRU] Backport xorg-server 1.20.13 to focal

You have been subscribed to a public bug:

[Impact]
The delay phenomenon is serious in 'External display mode' during the 
'On-demand' mode working.
Please reference lp:1940247 and lp:1919118.

[Fix]
 I installed 21.10 on Raptor12(ThinkPad-P15-Gen-2i), with xorg-server 
2:1.20.13-1ubuntu1 and nvidia-495.38 test driver, this issue is solved. But in 
20.04, it's still 2:1.20.11-1ubuntu1~20.04.2.

[Test]
On Raptor12(ThinkPad-P15-Gen-2i), P17 Gen 2 and P1 Gen 4, with latest 20.04, it 
could be reproduced.

[Where problems could occur]
Although the nvidia driver is not released, I thought it's no harm to upgrade 
xorg-server first.

** Affects: oem-priority
 Importance: Critical
 Assignee: Bin Li (binli)
 Status: Triaged

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


** Tags: oem-priority originate-from-1919118 sutton
-- 
[SRU] Backport xorg-server 1.20.13  to focal
https://bugs.launchpad.net/bugs/1947820
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg-server in Ubuntu.

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

[Desktop-packages] [Bug 1942307] Re: ubiquity uses performance mode for nvidia driver

** Description changed:

  [Steps to reproduce]
  1. Install 20.04.3 with "Third-party packages" on a system which containing a 
RTD3 supported nvidia card.
  2. After the installation, press enter to reboot system
  3. prime-select query
  
  [Expected result]
  on-demand
  
  [Actual result]
  performance
  
  ---
  
  It's because ubiquity launches `ubuntu-drivers install --packages-list
  ...` in live system but install each package to target storage.
  
  When installing nvidia-prime, the preinst set "on" to "/etc/prime-
  discrete" which will be referred by gpu-manager. The gpu-manager will
  set to performance mode.
  
  After confirming with Alberto on Mattermost, since we don't have a
  nvidia driver which lower than 450 version since focal.
  
  I think we are ok to switch to on-demand mode.
  
  ---
  
  [Impact]
  
   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
  
  [Test Plan]
  
-  * Install 20.04.3 with "Third-party packages". After the installation, 
reboot the system. Execute "prime-select query" should get "on-demand"
+  * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU 
driver. After the installation, reboot the system. Execute "prime-select query" 
should get "on-demand"
   * On non-laptop machine. Can set GPU mode to on-demand
   * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
  
  [Where problems could occur]
  
   * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
   * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.
  
  [Other Info]
  
  X-HWE-Bug: Bug #1946434
  
  Changelogs:
  
  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium
  
    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)
  
    [ Alberto Milone ]
    * prime-select:
  - Detect chassis type and enable RTD3 only
    on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
    RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
    is not available.
  - Don't check the current profile when setting
    a profile (LP: #1946476).
  - Catch BrokenPipeError.
  - Use bootvga detection when last_gfx_boot is
    not available.
  
  nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium
  
    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)
  
    [ Alberto Milone ]
    * prime-select:
  - Detect chassis type and enable RTD3 only
    on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
    RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
    is not available.
  - Don't check the current profile when setting
    a profile (LP: #1946476).

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

Title:
  ubiquity uses performance mode for nvidia driver

Status in OEM Priority Project:
  Triaged
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Focal:
  Incomplete
Status in nvidia-prime source package in Hirsute:
  Incomplete

Bug description:
  [Steps to reproduce]
  1. Install 20.04.3 with "Third-party packages" on a system which containing a 
RTD3 supported nvidia card.
  2. After the installation, press enter to reboot system
  3. prime-select query

  [Expected result]
  on-demand

  [Actual result]
  performance

  ---

  It's because ubiquity launches `ubuntu-drivers install --packages-list
  ...` in live system but install each package to target storage.

  When installing nvidia-prime, the preinst set "on" to "/etc/prime-
  discrete" which will be referred by gpu-manager. The gpu-manager will
  set to performance mode.

  After confirming with Alberto on Mattermost, since we don't have a
  nvidia driver which lower than 450 version since focal.

  I think we are ok to switch to on-demand mode.

  ---

  [Impact]

   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine

  [Test Plan]

   * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU 
driver. After the installation, reboot the system. Execute "prime-select query" 
should get "on-demand"
   * On non-laptop machine. Can set GPU mode to on-demand
   * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver

[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated

** Description changed:

  RTD3 is a nvidia GPU feature to support runtime suspend.
  
  On-demand would be a X offloading feature.
  
  They are independent, according to discussion on
  https://github.com/tseliot/ubuntu-drivers-common/issues/55.
  
  Some parts need to be adjusted, e.g.
  
  ```
  # If we are dealing with NVIDIA PRIME, and runtimepm
  # is supported, enable it
  if (os.path.isfile('/run/nvidia_runtimepm_supported') and
  os.path.isfile('/usr/bin/prime-select')):
  print('Trying to select the on-demand PRIME profile')
  try:
  subprocess.call(['prime-select', 'on-demand'])
  except:
  pass
  
  # Create the override file for gpu-manager
  with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:
  f.write('# File created by ubuntu-drivers\n')
  ```
  
  ---
  
  [Impact]
  
   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
  
  [Test Plan]
  
-  * Install 20.04.3 with "Third-party packages". After the installation, 
reboot the system. Execute "prime-select query" should get "on-demand"
+  * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU 
driver. After the installation, reboot the system. Execute "prime-select query" 
should get "on-demand"
   * On non-laptop machine. Can set GPU mode to on-demand
   * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
  
  [Where problems could occur]
  
   * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
   * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.
  
  [Other Info]
  
  X-HWE-Bug: Bug #1946434
  
  Changelogs:
  
  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium
  
    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)
  
    [ Alberto Milone ]
    * prime-select:
  - Detect chassis type and enable RTD3 only
    on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
    RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
    is not available.
  - Don't check the current profile when setting
    a profile (LP: #1946476).
  - Catch BrokenPipeError.
  - Use bootvga detection when last_gfx_boot is
    not available.
  
  nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium
  
    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)
  
    [ Alberto Milone ]
    * prime-select:
  - Detect chassis type and enable RTD3 only
    on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
    RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
    is not available.
  - Don't check the current profile when setting
    a profile (LP: #1946476).

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

Title:
  On-demand and RTD3 need to be separated

Status in OEM Priority Project:
  Triaged
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress
Status in nvidia-prime source package in Focal:
  New
Status in ubuntu-drivers-common source package in Focal:
  New
Status in nvidia-prime source package in Hirsute:
  New
Status in ubuntu-drivers-common source package in Hirsute:
  New

Bug description:
  RTD3 is a nvidia GPU feature to support runtime suspend.

  On-demand would be a X offloading feature.

  They are independent, according to discussion on
  https://github.com/tseliot/ubuntu-drivers-common/issues/55.

  Some parts need to be adjusted, e.g.

  ```
  # If we are dealing with NVIDIA PRIME, and runtimepm
  # is supported, enable it
  if (os.path.isfile('/run/nvidia_runtimepm_supported') and
  os.path.isfile('/usr/bin/prime-select')):
  print('Trying to select the on-demand PRIME profile')
  try:
  subprocess.call(['prime-select', 'on-demand'])
  except:
  pass

  # Create the override file for gpu-manager
  with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:
  f.write('# File created by ubuntu-drivers\n')
  ```

  ---

  [Impact]

   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine

  [Test Plan]

   * Install Ubuntu, and then execute

[Desktop-packages] [Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled

** Description changed:

  As per LP: #1942307 we now set on-demand as the default. This however,
  causes "prime-select on-demand", called by ubuntu-drivers, not to even
  try to detect RTD3 and to enable it, since "on-demand" is already set.
  
  We cannot make informed choices about RTD3 in the postinstallation
  script of nvidia-prime, therefore we should simply drop the check that
  prime-select makes to abort if the new profile is determined to be the
  same as the current profile.
  
  ---
  
  [Impact]
  
   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
  
  [Test Plan]
  
-  * Install 20.04.3 with "Third-party packages". After the installation, 
reboot the system. Execute "prime-select query" should get "on-demand"
+  * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU 
driver. After the installation, reboot the system. Execute "prime-select query" 
should get "on-demand"
   * On non-laptop machine. Can set GPU mode to on-demand
   * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
  
  [Where problems could occur]
  
   * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
   * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.
  
  [Other Info]
  
  X-HWE-Bug: Bug #1946434
  
  Changelogs:
  
  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium
  
    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)
  
    [ Alberto Milone ]
    * prime-select:
  - Detect chassis type and enable RTD3 only
    on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
    RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
    is not available.
  - Don't check the current profile when setting
    a profile (LP: #1946476).
  - Catch BrokenPipeError.
  - Use bootvga detection when last_gfx_boot is
    not available.
  
  nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium
  
    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)
  
    [ Alberto Milone ]
    * prime-select:
  - Detect chassis type and enable RTD3 only
    on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend on
    RTD3 (LP: #1942789).
  - Use bootvga detection when last_gfx_boot
    is not available.
  - Don't check the current profile when setting
    a profile (LP: #1946476).

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

Title:
  New on-demand default causes RTD3 never to be enabled

Status in OEM Priority Project:
  New
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Focal:
  Incomplete
Status in nvidia-prime source package in Hirsute:
  Incomplete
Status in nvidia-prime source package in Impish:
  Fix Released

Bug description:
  As per LP: #1942307 we now set on-demand as the default. This however,
  causes "prime-select on-demand", called by ubuntu-drivers, not to even
  try to detect RTD3 and to enable it, since "on-demand" is already set.

  We cannot make informed choices about RTD3 in the postinstallation
  script of nvidia-prime, therefore we should simply drop the check that
  prime-select makes to abort if the new profile is determined to be the
  same as the current profile.

  ---

  [Impact]

   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine

  [Test Plan]

   * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU 
driver. After the installation, reboot the system. Execute "prime-select query" 
should get "on-demand"
   * On non-laptop machine. Can set GPU mode to on-demand
   * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"

  [Where problems could occur]

   * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
   * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.

  [Other Info]

  X-HWE-Bug: Bug #1946434

  Changelogs:

  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium

    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)

    [ Alberto Milone ]
    *

[Desktop-packages] [Bug 1949553] Re: Backport packages for 20.04.4 HWE stack

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

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

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

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

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

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

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

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

** Changed in: xorg-server (Ubuntu Focal)
   Status: New => In Progress

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

** Changed in: libdrm (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: xorg-server (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Backport packages for 20.04.4 HWE stack

Status in libdrm package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libdrm source package in Focal:
  In Progress
Status in mesa source package in Focal:
  In Progress
Status in xorg-server source package in Focal:
  In Progress

Bug description:
  [Impact]

  These are needed for 20.04.4 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  libdrm: adds some new api, no changes to old stuff

  llvm-13: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

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


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

[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated

** Description changed:

  RTD3 is a nvidia GPU feature to support runtime suspend.
  
  On-demand would be a X offloading feature.
  
  They are independent, according to discussion on
  https://github.com/tseliot/ubuntu-drivers-common/issues/55.
  
  Some parts need to be adjusted, e.g.
  
  ```
  # If we are dealing with NVIDIA PRIME, and runtimepm
  # is supported, enable it
  if (os.path.isfile('/run/nvidia_runtimepm_supported') and
  os.path.isfile('/usr/bin/prime-select')):
  print('Trying to select the on-demand PRIME profile')
  try:
  subprocess.call(['prime-select', 'on-demand'])
  except:
  pass
  
  # Create the override file for gpu-manager
  with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:
  f.write('# File created by ubuntu-drivers\n')
  ```
  
  ---
  
  [Impact]
  
-  * Ubuntu will set GPU mode to performance as default which may use more power
-  * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
-  * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
+  * Ubuntu will set GPU mode to performance as default which may use more power
+  * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
+  * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
  
  [Test Plan]
  
-  * Install 20.04.3 with "Third-party packages". After the installation, 
reboot the system. Execute "prime-select query" should get "on-demand"
-  * On non-laptop machine. Can set GPU mode to on-demand
-  * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
+  * Install 20.04.3 with "Third-party packages". After the installation, 
reboot the system. Execute "prime-select query" should get "on-demand"
+  * On non-laptop machine. Can set GPU mode to on-demand
+  * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
  
  [Where problems could occur]
  
-  * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
-  * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.
+  * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
+  * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.
  
  [Other Info]
+ 
+ X-HWE-Bug: Bug #1946434
  
  Changelogs:
  
  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium
  
-   [ Jeremy Szu ]
-   * Set on-demand mode as default nvidia mode (LP: #1942307)
+   [ Jeremy Szu ]
+   * Set on-demand mode as default nvidia mode (LP: #1942307)
  
-   [ Alberto Milone ]
-   * prime-select:
- - Detect chassis type and enable RTD3 only
-   on laptops (LP: #1942788).
- - on-demand mode doesn't need to depend on
-   RTD3 (LP: #1942789).
- - Use bootvga detection when last_gfx_boot
-   is not available.
- - Don't check the current profile when setting
-   a profile (LP: #1946476).
- - Catch BrokenPipeError.
- - Use bootvga detection when last_gfx_boot is
-   not available.
+   [ Alberto Milone ]
+   * prime-select:
+ - Detect chassis type and enable RTD3 only
+   on laptops (LP: #1942788).
+ - on-demand mode doesn't need to depend on
+   RTD3 (LP: #1942789).
+ - Use bootvga detection when last_gfx_boot
+   is not available.
+ - Don't check the current profile when setting
+   a profile (LP: #1946476).
+ - Catch BrokenPipeError.
+ - Use bootvga detection when last_gfx_boot is
+   not available.
  
  nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium
  
-   [ Jeremy Szu ]
-   * Set on-demand mode as default nvidia mode (LP: #1942307)
+   [ Jeremy Szu ]
+   * Set on-demand mode as default nvidia mode (LP: #1942307)
  
-   [ Alberto Milone ]
-   * prime-select:
- - Detect chassis type and enable RTD3 only
-   on laptops (LP: #1942788).
- - on-demand mode doesn't need to depend on
-   RTD3 (LP: #1942789).
- - Use bootvga detection when last_gfx_boot
-   is not available.
- - Don't check the current profile when setting
-   a profile (LP: #1946476).
- 
- X-HWE-Bug: Bug #1946434
+   [ Alberto Milone ]
+   * prime-select:
+ - Detect chassis type and enable RTD3 only
+   on laptops (LP: #1942788).
+ - on-demand mode doesn't need to depend on
+   RTD3 (LP: #1942789).
+ - Use bootvga detection when last_gfx_boot
+   is not available.
+ - Don't check the current profile when setting
+   a profile (LP: #1946476).

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

[Desktop-packages] [Bug 1942788] Re: Nvidia doesn't support RTD3 on non-laptops

** Description changed:

  According to Nvidia README, the RTD3 doesn't support on non-laptop
  machine.
  
  https://github.com/tseliot/ubuntu-drivers-common/issues/55
  
  We need to check chassis type before enabling RTD3.
  
  ---
  
  [Impact]
  
-  * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on 
non-laptop machine
-  * Patch make system not enable RTD3 unless it's a laptop
+  * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on 
non-laptop machine
+  * Patch make system not enable RTD3 unless it's a laptop
  
  [Test Plan]
  
-  * Install Ubuntu on machine
-  * Install GPU driver via 'ubuntu-drivers install'
-  * On laptop with Nvidia RTD3 supported GPU. The configuration file 
'/run/nvidia_runtimepm_supported' will be created
+  * Install Ubuntu on machine
+  * Install GPU driver via 'ubuntu-drivers install'
+  * On laptop with Nvidia RTD3 supported GPU. The configuration file 
'/run/nvidia_runtimepm_supported' will be created
  
  [Where problems could occur]
  
-  * With non-laptop machine use RTD3 supported GPU may use more power.
- But based on Nvidia READ, such case should not happen
+  * With non-laptop machine use RTD3 supported GPU may use more power
  
  [Other Info]
  
  X-HWE-Bug: Bug #1946440

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

Title:
  Nvidia doesn't support RTD3 on non-laptops

Status in OEM Priority Project:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Incomplete
Status in ubuntu-drivers-common source package in Hirsute:
  Incomplete

Bug description:
  According to Nvidia README, the RTD3 doesn't support on non-laptop
  machine.

  https://github.com/tseliot/ubuntu-drivers-common/issues/55

  We need to check chassis type before enabling RTD3.

  ---

  [Impact]

   * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on 
non-laptop machine
   * Patch make system not enable RTD3 unless it's a laptop

  [Test Plan]

   * Install Ubuntu on machine
   * Install GPU driver via 'ubuntu-drivers install'
   * On laptop with Nvidia RTD3 supported GPU. The configuration file 
'/run/nvidia_runtimepm_supported' will be created

  [Where problems could occur]

   * With non-laptop machine use RTD3 supported GPU may use more power

  [Other Info]

  X-HWE-Bug: Bug #1946440

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


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

[Desktop-packages] [Bug 1946440] Re: SRU: enable RTD3 only on laptops

** Description changed:

  [Impact]
  
   * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on 
non-laptop machine
-  * Patch make system not enable RTD3 unless it's a laptop
+  * Patch make system not enable RTD3 unless it's a laptop
  
  [Test Plan]
  
   * Install Ubuntu on machine
-  * Install GPU driver via 'ubuntu-drivers install'
+  * Install GPU driver via 'ubuntu-drivers install'
   * On laptop with Nvidia RTD3 supported GPU. The configuration file 
'/run/nvidia_runtimepm_supported' will be created
  
  [Where problems could occur]
  
   * With non-laptop machine use RTD3 supported GPU may use more power.
- But based on Nvidia READ, such case should not happen
  
  [Other Info]

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

Title:
  SRU: enable RTD3 only on laptops

Status in OEM Priority Project:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Invalid
Status in ubuntu-drivers-common source package in Focal:
  In Progress
Status in ubuntu-drivers-common source package in Hirsute:
  In Progress

Bug description:
  [Impact]

   * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on 
non-laptop machine
   * Patch make system not enable RTD3 unless it's a laptop

  [Test Plan]

   * Install Ubuntu on machine
   * Install GPU driver via 'ubuntu-drivers install'
   * On laptop with Nvidia RTD3 supported GPU. The configuration file 
'/run/nvidia_runtimepm_supported' will be created

  [Where problems could occur]

   * With non-laptop machine use RTD3 supported GPU may use more power.

  [Other Info]

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


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

[Desktop-packages] [Bug 1942307] Re: ubiquity uses performance mode for nvidia driver

** Description changed:

  [Steps to reproduce]
  1. Install 20.04.3 with "Third-party packages" on a system which containing a 
RTD3 supported nvidia card.
  2. After the installation, press enter to reboot system
  3. prime-select query
  
  [Expected result]
  on-demand
  
  [Actual result]
  performance
  
  ---
  
  It's because ubiquity launches `ubuntu-drivers install --packages-list
  ...` in live system but install each package to target storage.
  
  When installing nvidia-prime, the preinst set "on" to "/etc/prime-
  discrete" which will be referred by gpu-manager. The gpu-manager will
  set to performance mode.
  
  After confirming with Alberto on Mattermost, since we don't have a
  nvidia driver which lower than 450 version since focal.
  
  I think we are ok to switch to on-demand mode.
  
  ---
  
  [Impact]
  
-  * Ubuntu will set GPU mode to performance as default which may use more power
-  * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
-  * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
+  * Ubuntu will set GPU mode to performance as default which may use more power
+  * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
+  * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
  
  [Test Plan]
  
-  * Install 20.04.3 with "Third-party packages". After the installation, 
reboot the system. Execute "prime-select query" should get "on-demand"
-  * On non-laptop machine. Can set GPU mode to on-demand
-  * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
+  * Install 20.04.3 with "Third-party packages". After the installation, 
reboot the system. Execute "prime-select query" should get "on-demand"
+  * On non-laptop machine. Can set GPU mode to on-demand
+  * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
  
  [Where problems could occur]
  
-  * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
-  * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.
+  * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
+  * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.
  
  [Other Info]
+ 
+ X-HWE-Bug: Bug #1946434
  
  Changelogs:
  
  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium
  
-   [ Jeremy Szu ]
-   * Set on-demand mode as default nvidia mode (LP: #1942307)
+   [ Jeremy Szu ]
+   * Set on-demand mode as default nvidia mode (LP: #1942307)
  
-   [ Alberto Milone ]
-   * prime-select:
- - Detect chassis type and enable RTD3 only
-   on laptops (LP: #1942788).
- - on-demand mode doesn't need to depend on
-   RTD3 (LP: #1942789).
- - Use bootvga detection when last_gfx_boot
-   is not available.
- - Don't check the current profile when setting
-   a profile (LP: #1946476).
- - Catch BrokenPipeError.
- - Use bootvga detection when last_gfx_boot is
-   not available.
+   [ Alberto Milone ]
+   * prime-select:
+ - Detect chassis type and enable RTD3 only
+   on laptops (LP: #1942788).
+ - on-demand mode doesn't need to depend on
+   RTD3 (LP: #1942789).
+ - Use bootvga detection when last_gfx_boot
+   is not available.
+ - Don't check the current profile when setting
+   a profile (LP: #1946476).
+ - Catch BrokenPipeError.
+ - Use bootvga detection when last_gfx_boot is
+   not available.
  
  nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium
  
-   [ Jeremy Szu ]
-   * Set on-demand mode as default nvidia mode (LP: #1942307)
+   [ Jeremy Szu ]
+   * Set on-demand mode as default nvidia mode (LP: #1942307)
  
-   [ Alberto Milone ]
-   * prime-select:
- - Detect chassis type and enable RTD3 only
-   on laptops (LP: #1942788).
- - on-demand mode doesn't need to depend on
-   RTD3 (LP: #1942789).
- - Use bootvga detection when last_gfx_boot
-   is not available.
- - Don't check the current profile when setting
-   a profile (LP: #1946476).
- 
- X-HWE-Bug: Bug #1946434
+   [ Alberto Milone ]
+   * prime-select:
+ - Detect chassis type and enable RTD3 only
+   on laptops (LP: #1942788).
+ - on-demand mode doesn't need to depend on
+   RTD3 (LP: #1942789).
+ - Use bootvga detection when last_gfx_boot
+   is not available.
+ - Don't check the current profile when setting
+   a profile (LP: #1946476).

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

[Desktop-packages] [Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled

** Description changed:

  As per LP: #1942307 we now set on-demand as the default. This however,
  causes "prime-select on-demand", called by ubuntu-drivers, not to even
  try to detect RTD3 and to enable it, since "on-demand" is already set.
  
  We cannot make informed choices about RTD3 in the postinstallation
  script of nvidia-prime, therefore we should simply drop the check that
  prime-select makes to abort if the new profile is determined to be the
  same as the current profile.
  
  ---
  
  [Impact]
  
-  * Ubuntu will set GPU mode to performance as default which may use more power
-  * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
-  * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
+  * Ubuntu will set GPU mode to performance as default which may use more power
+  * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
+  * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
  
  [Test Plan]
  
-  * Install 20.04.3 with "Third-party packages". After the installation, 
reboot the system. Execute "prime-select query" should get "on-demand"
-  * On non-laptop machine. Can set GPU mode to on-demand
-  * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
+  * Install 20.04.3 with "Third-party packages". After the installation, 
reboot the system. Execute "prime-select query" should get "on-demand"
+  * On non-laptop machine. Can set GPU mode to on-demand
+  * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
  
  [Where problems could occur]
  
-  * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
-  * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.
+  * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
+  * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.
  
  [Other Info]
+ 
+ X-HWE-Bug: Bug #1946434
  
  Changelogs:
  
  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium
  
-   [ Jeremy Szu ]
-   * Set on-demand mode as default nvidia mode (LP: #1942307)
+   [ Jeremy Szu ]
+   * Set on-demand mode as default nvidia mode (LP: #1942307)
  
-   [ Alberto Milone ]
-   * prime-select:
- - Detect chassis type and enable RTD3 only
-   on laptops (LP: #1942788).
- - on-demand mode doesn't need to depend on
-   RTD3 (LP: #1942789).
- - Use bootvga detection when last_gfx_boot
-   is not available.
- - Don't check the current profile when setting
-   a profile (LP: #1946476).
- - Catch BrokenPipeError.
- - Use bootvga detection when last_gfx_boot is
-   not available.
+   [ Alberto Milone ]
+   * prime-select:
+ - Detect chassis type and enable RTD3 only
+   on laptops (LP: #1942788).
+ - on-demand mode doesn't need to depend on
+   RTD3 (LP: #1942789).
+ - Use bootvga detection when last_gfx_boot
+   is not available.
+ - Don't check the current profile when setting
+   a profile (LP: #1946476).
+ - Catch BrokenPipeError.
+ - Use bootvga detection when last_gfx_boot is
+   not available.
  
  nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium
  
-   [ Jeremy Szu ]
-   * Set on-demand mode as default nvidia mode (LP: #1942307)
+   [ Jeremy Szu ]
+   * Set on-demand mode as default nvidia mode (LP: #1942307)
  
-   [ Alberto Milone ]
-   * prime-select:
- - Detect chassis type and enable RTD3 only
-   on laptops (LP: #1942788).
- - on-demand mode doesn't need to depend on
-   RTD3 (LP: #1942789).
- - Use bootvga detection when last_gfx_boot
-   is not available.
- - Don't check the current profile when setting
-   a profile (LP: #1946476).
- 
- X-HWE-Bug: Bug #1946434
+   [ Alberto Milone ]
+   * prime-select:
+ - Detect chassis type and enable RTD3 only
+   on laptops (LP: #1942788).
+ - on-demand mode doesn't need to depend on
+   RTD3 (LP: #1942789).
+ - Use bootvga detection when last_gfx_boot
+   is not available.
+ - Don't check the current profile when setting
+   a profile (LP: #1946476).

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

Title:
  New on-demand default causes RTD3 never to be enabled

Status in OEM Priority Project:
  New
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Focal:
  Incomplete
Status in nvidia-prime source package in Hirsute:
  Incomplete
Status in nvidia-prime source package in

[Desktop-packages] [Bug 1698083] Re: Maximize vertically/horizontally doesn't work (in some apps)

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1996
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1996

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

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

Title:
  Maximize vertically/horizontally doesn't work (in some apps)

Status in GTK+:
  Unknown
Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539

  In Gnome Tweak Tool you can configure vertical maximizing for:
    Windows > Titlebar Actions > Middle-Click
  However this feature seems to get ignored in Wayland sessions (it just 
maximizes fully instead). It only works correctly in Xorg Gnome sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 15 14:46:04 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-05-03 (43 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled

** Changed in: oem-priority
 Assignee: jeremyszu (os369510) => Dirk Su (dirksu)

** Description changed:

  As per LP: #1942307 we now set on-demand as the default. This however,
  causes "prime-select on-demand", called by ubuntu-drivers, not to even
  try to detect RTD3 and to enable it, since "on-demand" is already set.
  
  We cannot make informed choices about RTD3 in the postinstallation
  script of nvidia-prime, therefore we should simply drop the check that
  prime-select makes to abort if the new profile is determined to be the
  same as the current profile.
  
+ ---
+ 
+ [Impact]
+ 
+  * Ubuntu will set GPU mode to performance as default which may use more power
+  * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
+  * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
+ 
+ [Test Plan]
+ 
+  * Install 20.04.3 with "Third-party packages". After the installation, 
reboot the system. Execute "prime-select query" should get "on-demand"
+  * On non-laptop machine. Can set GPU mode to on-demand
+  * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
+ 
+ [Where problems could occur]
+ 
+  * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
+  * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.
+ 
+ [Other Info]
+ 
+ Changelogs:
+ 
+ nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium
+ 
+   [ Jeremy Szu ]
+   * Set on-demand mode as default nvidia mode (LP: #1942307)
+ 
+   [ Alberto Milone ]
+   * prime-select:
+ - Detect chassis type and enable RTD3 only
+   on laptops (LP: #1942788).
+ - on-demand mode doesn't need to depend on
+   RTD3 (LP: #1942789).
+ - Use bootvga detection when last_gfx_boot
+   is not available.
+ - Don't check the current profile when setting
+   a profile (LP: #1946476).
+ - Catch BrokenPipeError.
+ - Use bootvga detection when last_gfx_boot is
+   not available.
+ 
+ nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium
+ 
+   [ Jeremy Szu ]
+   * Set on-demand mode as default nvidia mode (LP: #1942307)
+ 
+   [ Alberto Milone ]
+   * prime-select:
+ - Detect chassis type and enable RTD3 only
+   on laptops (LP: #1942788).
+ - on-demand mode doesn't need to depend on
+   RTD3 (LP: #1942789).
+ - Use bootvga detection when last_gfx_boot
+   is not available.
+ - Don't check the current profile when setting
+   a profile (LP: #1946476).
+ 
  X-HWE-Bug: Bug #1946434

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

Title:
  New on-demand default causes RTD3 never to be enabled

Status in OEM Priority Project:
  New
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Focal:
  Incomplete
Status in nvidia-prime source package in Hirsute:
  Incomplete
Status in nvidia-prime source package in Impish:
  Fix Released

Bug description:
  As per LP: #1942307 we now set on-demand as the default. This however,
  causes "prime-select on-demand", called by ubuntu-drivers, not to even
  try to detect RTD3 and to enable it, since "on-demand" is already set.

  We cannot make informed choices about RTD3 in the postinstallation
  script of nvidia-prime, therefore we should simply drop the check that
  prime-select makes to abort if the new profile is determined to be the
  same as the current profile.

  ---

  [Impact]

   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine

  [Test Plan]

   * Install 20.04.3 with "Third-party packages". After the installation, 
reboot the system. Execute "prime-select query" should get "on-demand"
   * On non-laptop machine. Can set GPU mode to on-demand
   * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"

  [Where problems could occur]

   * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
   * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.

  [Other Info]

  X-HWE-Bug: Bug #1946434

  Changelogs:

  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium

    [ Jeremy Szu ]
    * Set on-demand mode as default nvidia mode (LP: #1942307)

    [ Alberto Milone ]
    * prime-select:
  - Detect chassis type and enable RTD3 only
    on laptops (LP: #1942788).
  - on-demand mode doesn't need to depend

[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated

** Changed in: oem-priority
 Assignee: jeremyszu (os369510) => Dirk Su (dirksu)

** Description changed:

  RTD3 is a nvidia GPU feature to support runtime suspend.
  
  On-demand would be a X offloading feature.
  
  They are independent, according to discussion on
  https://github.com/tseliot/ubuntu-drivers-common/issues/55.
  
  Some parts need to be adjusted, e.g.
  
  ```
- # If we are dealing with NVIDIA PRIME, and runtimepm  

- # is supported, enable it 

- if (os.path.isfile('/run/nvidia_runtimepm_supported') and 

- os.path.isfile('/usr/bin/prime-select')): 

- print('Trying to select the on-demand PRIME profile') 

  
- try:  

- subprocess.call(['prime-select', 'on-demand'])

- except:   

- pass  

-   

- # Create the override file for gpu-manager

- with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:  

- f.write('# File created by ubuntu-drivers\n')
+ # If we are dealing with NVIDIA PRIME, and runtimepm
+ # is supported, enable it
+ if (os.path.isfile('/run/nvidia_runtimepm_supported') and
+ os.path.isfile('/usr/bin/prime-select')):
+ print('Trying to select the on-demand PRIME profile')
+ try:
+ subprocess.call(['prime-select', 'on-demand'])
+ except:
+ pass
+ 
+ # Create the override file for gpu-manager
+ with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:
+ f.write('# File created by ubuntu-drivers\n')
  ```
  
+ ---
+ 
+ [Impact]
+ 
+  * Ubuntu will set GPU mode to performance as default which may use more power
+  * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
+  * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
+ 
+ [Test Plan]
+ 
+  * Install 20.04.3 with "Third-party packages". After the installation, 
reboot the system. Execute "prime-select query" should get "on-demand"
+  * On non-laptop machine. Can set GPU mode to on-demand
+  * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
+ 
+ [Where problems could occur]
+ 
+  * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
+  * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.
+ 
+ [Other Info]
+ 
+ Changelogs:
+ 
+ nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium
+ 
+   [ Jeremy Szu ]
+   * Set on-demand mode as default nvidia mode (LP: #1942307)
+ 
+   [ Alberto Milone ]
+   * prime-select:
+ - Detect chassis type and enable RTD3 only
+   on laptops (LP: #1942788).
+ - on-demand mode doesn't need to depend on
+   RTD3 (LP: #1942789).
+ - Use bootvga detection when last_gfx_boot
+   is not available.
+ - Don't check the current profile when setting
+   a profile (LP: #1946476).
+ - Catch BrokenPipeError.
+ - Use bootvga detection when last_gfx_boot is
+   not available.
+ 
+ nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium
+ 
+   [ Jeremy Szu ]
+   * Set on-demand mode as default nvidia mode (LP: #1942307)
+ 
+   [ Alberto Milone ]
+   * prime-select:
+ - Detect chassis type and enable RTD3 only
+   on laptops (LP: #1942788).
+ - on-demand mode doesn't need to depend on
+   RTD3 (LP: #1942789).
+ - Use bootvga detection when last_gfx_boot
+   is not available.
+ - Don't check the current profile when setting
+   a profile (LP: #1946476).
+ 
  X-HWE-Bug: Bug #1946434

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

Title:
  On-demand and RTD3 need to be separated

Status in OEM Priority Project:
  Triaged
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  In Progress
Status in nvidia-prime source

[Desktop-packages] [Bug 1942788] Re: Nvidia doesn't support RTD3 on non-laptops

** Changed in: oem-priority
 Assignee: jeremyszu (os369510) => Dirk Su (dirksu)

** Description changed:

  According to Nvidia README, the RTD3 doesn't support on non-laptop
  machine.
  
  https://github.com/tseliot/ubuntu-drivers-common/issues/55
  
  We need to check chassis type before enabling RTD3.
  
+ ---
+ 
+ [Impact]
+ 
+  * Ubuntu will set GPU mode to performance as default which may use more power
+  * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
+  * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
+ 
+ [Test Plan]
+ 
+  * Install 20.04.3 with "Third-party packages". After the installation, 
reboot the system. Execute "prime-select query" should get "on-demand"
+  * On non-laptop machine. Can set GPU mode to on-demand
+  * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
+ 
+ [Where problems could occur]
+ 
+  * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
+  * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.
+ 
+ [Other Info]
+ 
+ Changelogs:
+ 
+ nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium
+ 
+   [ Jeremy Szu ]
+   * Set on-demand mode as default nvidia mode (LP: #1942307)
+ 
+   [ Alberto Milone ]
+   * prime-select:
+ - Detect chassis type and enable RTD3 only
+   on laptops (LP: #1942788).
+ - on-demand mode doesn't need to depend on
+   RTD3 (LP: #1942789).
+ - Use bootvga detection when last_gfx_boot
+   is not available.
+ - Don't check the current profile when setting
+   a profile (LP: #1946476).
+ - Catch BrokenPipeError.
+ - Use bootvga detection when last_gfx_boot is
+   not available.
+ 
+ nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium
+ 
+   [ Jeremy Szu ]
+   * Set on-demand mode as default nvidia mode (LP: #1942307)
+ 
+   [ Alberto Milone ]
+   * prime-select:
+ - Detect chassis type and enable RTD3 only
+   on laptops (LP: #1942788).
+ - on-demand mode doesn't need to depend on
+   RTD3 (LP: #1942789).
+ - Use bootvga detection when last_gfx_boot
+   is not available.
+ - Don't check the current profile when setting
+   a profile (LP: #1946476).
+ 
  X-HWE-Bug: Bug #1946434
  
  X-HWE-Bug: Bug #1946440

** Description changed:

  According to Nvidia README, the RTD3 doesn't support on non-laptop
  machine.
  
  https://github.com/tseliot/ubuntu-drivers-common/issues/55
  
  We need to check chassis type before enabling RTD3.
  
  ---
  
  [Impact]
  
-  * Ubuntu will set GPU mode to performance as default which may use more power
-  * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
-  * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
+  * Ubuntu will set GPU mode to performance as default which may use more power
+  * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
+  * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
  
  [Test Plan]
  
-  * Install 20.04.3 with "Third-party packages". After the installation, 
reboot the system. Execute "prime-select query" should get "on-demand"
-  * On non-laptop machine. Can set GPU mode to on-demand
-  * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
+  * Install 20.04.3 with "Third-party packages". After the installation, 
reboot the system. Execute "prime-select query" should get "on-demand"
+  * On non-laptop machine. Can set GPU mode to on-demand
+  * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
  
  [Where problems could occur]
  
-  * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
-  * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.
+  * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
+  * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.
  
  [Other Info]
  
  Changelogs:
  
  nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium
  
-   [ Jeremy Szu ]
-   * Set on-demand mode as default nvidia mode (LP: #1942307)
+   [ Jeremy Szu ]
+   * Set on-demand mode as default nvidia mode (LP: #1942307)
  
-   [ Alberto Milone ]
-   * prime-select:
- - Detect chassis type and enable RTD3 only
-   on laptops (LP: #1942788).
- - on-demand mode doesn't need to depend on
-   RTD3 (LP: #1942789).
- - Use bootvga detection when last_gfx_boot
-   is

[Desktop-packages] [Bug 1948589] Re: JS ERROR: Error: Expected an object of type ClutterActor for argument 'sibling' but got type undefined _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimat

Tracking upstream in https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/4749

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

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

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

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

Title:
  JS ERROR: Error: Expected an object of type ClutterActor for argument
  'sibling' but got type undefined
  _syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18

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

Bug description:
  Ubuntu 22.04 development branch with kernel 5.13.0-19-generic @
  24/10/2021 (wayland)

  Testing 4 apps on 4 dynamic workspaces, on switching the apps by clicking 
their icons
  from the dock, im getting a lot of JS ERRORS in the journal logs, the more i 
switch
  between the apps, the more the errors reproduce:

  okt 24 18:54:15 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an 
object of type ClutterActor for argument 'sibling' but got type undefined

_syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18
  okt 24 18:54:15 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an 
object of type ClutterActor for argument 'sibling' but got type undefined

_syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18
  okt 24 18:54:16 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an 
object of type ClutterActor for argument 'sibling' but got type undefined

_syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18
  okt 24 18:54:16 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an 
object of type ClutterActor for argument 'sibling' but got type undefined

_syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18
  okt 24 18:54:29 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an 
object of type ClutterActor for argument 'sibling' but got type undefined

_syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18
  okt 24 18:54:29 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an 
object of type ClutterActor for argument 'sibling' but got type undefined

_syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18
  okt 24 18:54:31 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an 
object of type ClutterActor for argument 'sibling' but got type undefined

_syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18
  okt 24 18:54:32 R00TB00K gnome-shell[271529]: JS ERROR: Error: Expected an 
object of type ClutterActor for argument 'sibling' but got type undefined

_syncStacking@resource:///org/gnome/shell/ui/workspaceAnimation.js:80:18

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 24 18:56:39 2021
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2021-10-23T19:12:47.175230

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


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

[Desktop-packages] [Bug 1942307] Re: ubiquity uses performance mode for nvidia driver

** Changed in: oem-priority
 Assignee: jeremyszu (os369510) => Dirk Su (dirksu)

** Description changed:

  [Steps to reproduce]
  1. Install 20.04.3 with "Third-party packages" on a system which containing a 
RTD3 supported nvidia card.
  2. After the installation, press enter to reboot system
  3. prime-select query
  
  [Expected result]
  on-demand
  
  [Actual result]
  performance
  
  ---
  
  It's because ubiquity launches `ubuntu-drivers install --packages-list
  ...` in live system but install each package to target storage.
  
  When installing nvidia-prime, the preinst set "on" to "/etc/prime-
  discrete" which will be referred by gpu-manager. The gpu-manager will
  set to performance mode.
  
  After confirming with Alberto on Mattermost, since we don't have a
  nvidia driver which lower than 450 version since focal.
  
  I think we are ok to switch to on-demand mode.
  
+ ---
+ 
+ [Impact]
+ 
+  * Ubuntu will set GPU mode to performance as default which may use more power
+  * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
+  * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
+ 
+ [Test Plan]
+ 
+  * Install 20.04.3 with "Third-party packages". After the installation, 
reboot the system. Execute "prime-select query" should get "on-demand"
+  * On non-laptop machine. Can set GPU mode to on-demand
+  * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
+ 
+ [Where problems could occur]
+ 
+  * on-demand mode supported after nvidia driver 450. And focal does not have 
nvidia driver lower than 450.
+  * With GPU supported RTD3 not able enable runtime PM on non-laptop. But 
based on the Nvidia README, this case shall not happened.
+ 
+ [Other Info]
+ 
+ Changelogs:
+ 
+ nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium
+ 
+   [ Jeremy Szu ]
+   * Set on-demand mode as default nvidia mode (LP: #1942307)
+ 
+   [ Alberto Milone ]
+   * prime-select:
+ - Detect chassis type and enable RTD3 only
+   on laptops (LP: #1942788).
+ - on-demand mode doesn't need to depend on
+   RTD3 (LP: #1942789).
+ - Use bootvga detection when last_gfx_boot
+   is not available.
+ - Don't check the current profile when setting
+   a profile (LP: #1946476).
+ - Catch BrokenPipeError.
+ - Use bootvga detection when last_gfx_boot is
+   not available.
+ 
+ nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium
+ 
+   [ Jeremy Szu ]
+   * Set on-demand mode as default nvidia mode (LP: #1942307)
+ 
+   [ Alberto Milone ]
+   * prime-select:
+ - Detect chassis type and enable RTD3 only
+   on laptops (LP: #1942788).
+ - on-demand mode doesn't need to depend on
+   RTD3 (LP: #1942789).
+ - Use bootvga detection when last_gfx_boot
+   is not available.
+ - Don't check the current profile when setting
+   a profile (LP: #1946476).
+ 
  X-HWE-Bug: Bug #1946434

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

Title:
  ubiquity uses performance mode for nvidia driver

Status in OEM Priority Project:
  Triaged
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-prime source package in Focal:
  Incomplete
Status in nvidia-prime source package in Hirsute:
  Incomplete

Bug description:
  [Steps to reproduce]
  1. Install 20.04.3 with "Third-party packages" on a system which containing a 
RTD3 supported nvidia card.
  2. After the installation, press enter to reboot system
  3. prime-select query

  [Expected result]
  on-demand

  [Actual result]
  performance

  ---

  It's because ubiquity launches `ubuntu-drivers install --packages-list
  ...` in live system but install each package to target storage.

  When installing nvidia-prime, the preinst set "on" to "/etc/prime-
  discrete" which will be referred by gpu-manager. The gpu-manager will
  set to performance mode.

  After confirming with Alberto on Mattermost, since we don't have a
  nvidia driver which lower than 450 version since focal.

  I think we are ok to switch to on-demand mode.

  ---

  [Impact]

   * Ubuntu will set GPU mode to performance as default which may use more power
   * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not 
supported
   * According to Nvidia README, the RTD3 doesn't support on non-laptop machine

  [Test Plan]

   * Install 20.04.3 with "Third-party packages". After the installation, 
reboot the system. Execute "prime-select query" should get "on-demand"
   * On non-laptop machine. Can set GPU mode to on-demand
   * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand 
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"

  [Where problems could occur]

   * on-demand mode supported after nvidia driver

[Desktop-packages] [Bug 1949553] [NEW] Backport packages for 20.04.4 HWE stack

Public bug reported:

[Impact]

These are needed for 20.04.4 images.

[Test case]

Boot a daily image, see that it still has the necessary stack installed
and working.

[What could go wrong]

libdrm: adds some new api, no changes to old stuff

llvm-13: a new package, no regression potential on it's own

mesa: a new major release, but we'll pull the final stable release of
21.2.x series, so there shouldn't be any regressions left at that point

xserver: a new point-release, 1.20.x series is in deep maintenance mode,
so there should be little chance of breakage

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

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

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

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

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

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

Title:
  Backport packages for 20.04.4 HWE stack

Status in libdrm package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  [Impact]

  These are needed for 20.04.4 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  libdrm: adds some new api, no changes to old stuff

  llvm-13: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

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


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

[Desktop-packages] [Bug 1949116] Re: libgl1-mesa-dri depends on libllvm12 from universe

yes it should, promotion is fine

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

Title:
  libgl1-mesa-dri depends on libllvm12 from universe

Status in mesa package in Ubuntu:
  New

Bug description:
  It's not possible to install libgl1-mesa-dri from hirsute-updates (SRU
  bug 1932311) on a system that does not have universe enabled because
  it depends on libllvm12 from universe. This was not the case with the
  version of libgl1-mesa-dri in the release pocket because it depended
  upon libllvm11.

  (hirsute-amd64)root@impulse:~# apt-get install libgl1-mesa-dri
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgl1-mesa-dri : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

  (hirsute-amd64)root@impulse:~# apt-cache show libgl1-mesa-dri
  Package: libgl1-mesa-dri
  Architecture: amd64
  Version: 21.0.3-0ubuntu0.3
  Multi-Arch: same
  Priority: optional
  Section: libs
  Source: mesa
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian X Strike Force 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 37016
  Depends: libc6 (>= 2.33), libdrm-amdgpu1 (>= 2.4.100), libdrm-intel1 (>= 
2.4.38), libdrm-nouveau2 (>= 2.4.66), libdrm-radeon1 (>= 2.4.31),
  libdrm2 (>= 2.4.75), libelf1 (>= 0.142), libexpat1 (>= 2.0.1), libgcc-s1 (>= 
3.4), libglapi-mesa (= 21.0.3-0ubuntu0.3), libllvm12 (>= 1:9~s
  vn298832-1~), libsensors5 (>= 1:3.5.0), libstdc++6 (>= 5.2), libvulkan1 (>= 
1.2.131.2), libzstd1 (>= 1.3.2), zlib1g (>= 1:1.1.4)
  Filename: pool/main/m/mesa/libgl1-mesa-dri_21.0.3-0ubuntu0.3_amd64.deb

  This is blocking some CPC builds:
  
https://launchpad.net/~cloud-images/+livefs/ubuntu/hirsute/cpc-development/+build/306039

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


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

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

2021-11-03 Thread Kreaninw

Acer Swift SF514-52T here, this is fixed in Ubuntu 21.10.

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

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

Status in alsa-driver package in Ubuntu:
  Confirmed

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

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

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

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

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

  Here's some info:

  lspci | grep -I audio:

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

  cat /proc/asound/cards:

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

  And a clip from dmesg | grep snd:

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

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

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

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


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

[Desktop-packages] [Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init

Seems my development (impish) machine encountered the crash only once,
yesterday, and logged:

Nov 02 13:40:39 kab gnome-shell[1614]: Connection to xwayland lost
Nov 02 13:40:39 kab pulseaudio[1472]: X11 I/O error handler called
Nov 02 13:40:39 kab pulseaudio[1472]: X11 I/O error exit handler called, 
preparing to tear down X11 modules
Nov 02 13:40:39 kab gnome-shell[1614]: Xwayland just died, attempting to recover
Nov 02 13:40:39 kab systemd[1463]: org.gnome.SettingsDaemon.XSettings.service: 
Failed with result 'exit-code'.
Nov 02 13:40:39 kab gnome-shell[1614]: invalid unclassed pointer in cast to 
'GObject'
Nov 02 13:40:39 kab gnome-shell[1614]: g_object_get_data: assertion 
'G_IS_OBJECT (object)' failed
Nov 02 13:40:39 kab gnome-shell[1614]: gdk_screen_get_display: assertion 
'GDK_IS_SCREEN (screen)' failed
Nov 02 13:40:39 kab gnome-shell[1614]: gdk_display_get_name: assertion 
'GDK_IS_DISPLAY (display)' failed
Nov 02 13:40:39 kab gnome-shell[1614]: gdk_screen_get_number: assertion 
'GDK_IS_SCREEN (screen)' failed
Nov 02 13:40:39 kab gnome-shell[1614]: gtk_settings_get_for_screen: assertion 
'GDK_IS_SCREEN (screen)' failed
Nov 02 13:40:39 kab gnome-shell[1614]: invalid unclassed pointer in cast to 
'GObject'
Nov 02 13:40:39 kab gnome-shell[1614]: g_object_set_data_full: assertion 
'G_IS_OBJECT (object)' failed
Nov 02 13:40:39 kab gnome-shell[1614]: Can't create a GtkStyleContext without a 
display connection

But errors.ubuntu.com failed to associate it with a known error ID.
Maybe we also need to make sure PulseAudio isn't doing any X11.

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

Title:
  gnome-shell crashed with SIGTRAP from error "Can't create a
  GtkStyleContext without a display connection" in
  gtk_style_context_init

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  GNOME Shell isn't meant to use GTK at all, but it's repeatedly
  crashing in GTK since the introduction of GNOME 40.

  https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0
  https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844
  https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu72
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 29 15:11:43 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2021-10-27 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 40.5-1ubuntu2
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_writer_default()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


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

[Desktop-packages] [Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init