date:20230301

Thanks for the bug report.

Next time the problem happens, please reboot and then run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

** Tags added: amdgpu

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

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

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

Title:
  Ubuntu 22.04 on Lenovo Legion 5 Laptop occasional boot freeze and and
  unexpected reboots

Status in Ubuntu:
  Incomplete

Bug description:
  Problem occurs with "ubuntu-drivers install" beforehand, and in trying
  to resolve resorted to manual nvidia drivers install approach. Problem
  recurs anyway.

  Now not sure is nvidia issue as sometimes bluetooth does not get
  recognized as now (in this session).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.5-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  1 18:33:58 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-11-18 (103 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2008977] Re: Make Wayland sessions work with fbdev

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

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

Title:
  Make Wayland sessions work with fbdev

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New

Bug description:
  Make Wayland sessions work with fbdev. For when KMS/DRM support is
  missing in the kernel but the device still has legacy graphics.

  Currently Xorg already does this with a custom driver that allows it
  to fall back to using fbdev. We could do the same with mutter but it's
  unlikely to be accepted by upstream since Fedora opted to solve it by
  just enabling SimpleDRM in the kernel:

  https://fedoraproject.org/wiki/Changes/ReplaceFbdevDrivers

  This started out being a personal goal for me but will also be a
  business requirement in future as Ubuntu Core Desktop does not ship
  Xorg (but does ship Xwayland). So we need to give mutter some way of
  using fbdev graphics.

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


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

[Desktop-packages] [Bug 2008853] Re: Notifications block the view. Small size tweak needed to fix the bug

2023-03-01 Thread Nav

Thank you Paul. I've reported it on GitLab now:
https://gitlab.gnome.org/GNOME/nautilus/-/issues/2854

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

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

Title:
  Notifications block the view. Small size tweak needed to fix the bug

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Various notifications are shown in Nautilus, when files are deleted
  etc. These notification boxes (as shown in the attached screenshot)
  are a UI/UX nightmare, since each time such an action is performed,
  the box blocks part of the screen, forcing the User to either pause
  until the box disappears or forcing the User to click the close button
  of the message. It is a poor UI/UX design, to block the view with such
  a message. A simple temporary fix for this UI/UX bug, is to simply
  reduce the height of the message box (as shown in the bottom of the
  screenshot). I have requested for this earlier too. Please implement
  it at least this time, and please release the fix for Ubuntu 20.04
  too.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1.20.04.2
  ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  1 10:11:59 2023
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'205'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(899, 826)'
   b'org.gnome.nautilus.preferences' b'click-policy' b"'single'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
  InstallationDate: Installed on 2023-01-16 (43 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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


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

[Desktop-packages] [Bug 2008977] Missing required logs.

2023-03-01 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 2008977

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Make Wayland sessions work with fbdev

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  Make Wayland sessions work with fbdev. For when KMS/DRM support is
  missing in the kernel but the device still has legacy graphics.

  Currently Xorg already does this with a custom driver that allows it
  to fall back to using fbdev. We could do the same with mutter but it's
  unlikely to be accepted by upstream since Fedora opted to solve it by
  just enabling SimpleDRM in the kernel:

  https://fedoraproject.org/wiki/Changes/ReplaceFbdevDrivers

  This started out being a personal goal for me but will also be a
  business requirement in future as Ubuntu Core Desktop does not ship
  Xorg (but does ship Xwayland). So we need to give mutter some way of
  using fbdev graphics.

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


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

[Desktop-packages] [Bug 2008977] Re: Make Wayland sessions work with fbdev

We will also need to fix bug 1919400 before Xorg is ever retired. But
this is all in the distant future.

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

Title:
  Make Wayland sessions work with fbdev

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  Make Wayland sessions work with fbdev. For when KMS/DRM support is
  missing in the kernel but the device still has legacy graphics.

  Currently Xorg already does this with a custom driver that allows it
  to fall back to using fbdev. We could do the same with mutter but it's
  unlikely to be accepted by upstream since Fedora opted to solve it by
  just enabling SimpleDRM in the kernel:

  https://fedoraproject.org/wiki/Changes/ReplaceFbdevDrivers

  This started out being a personal goal for me but will also be a
  business requirement in future as Ubuntu Core Desktop does not ship
  Xorg (but does ship Xwayland). So we need to give mutter some way of
  using fbdev graphics.

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


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

[Desktop-packages] [Bug 2008977] [NEW] Make Wayland sessions work with fbdev

Public bug reported:

Make Wayland sessions work with fbdev. For when KMS/DRM support is
missing in the kernel but the device still has legacy graphics.

Currently Xorg already does this with a custom driver that allows it to
fall back to using fbdev. We could do the same with mutter but it's
unlikely to be accepted by upstream since Fedora opted to solve it by
just enabling SimpleDRM in the kernel:

https://fedoraproject.org/wiki/Changes/ReplaceFbdevDrivers

This started out being a personal goal for me but will also be a
business requirement in future as Ubuntu Core Desktop does not ship Xorg
(but does ship Xwayland). So we need to give mutter some way of using
fbdev graphics.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

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

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

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

Title:
  Make Wayland sessions work with fbdev

Status in linux package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  New

Bug description:
  Make Wayland sessions work with fbdev. For when KMS/DRM support is
  missing in the kernel but the device still has legacy graphics.

  Currently Xorg already does this with a custom driver that allows it
  to fall back to using fbdev. We could do the same with mutter but it's
  unlikely to be accepted by upstream since Fedora opted to solve it by
  just enabling SimpleDRM in the kernel:

  https://fedoraproject.org/wiki/Changes/ReplaceFbdevDrivers

  This started out being a personal goal for me but will also be a
  business requirement in future as Ubuntu Core Desktop does not ship
  Xorg (but does ship Xwayland). So we need to give mutter some way of
  using fbdev graphics.

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


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

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure/5.15.0-1035.42)

2023-03-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-restricted-modules-azure 
(5.15.0-1035.42) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-azure

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

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


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

[Desktop-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.15.0-1032.36)

2023-03-01 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted linux-restricted-modules-aws 
(5.15.0-1032.36) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-restricted-modules-aws

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

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


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

[Desktop-packages] [Bug 2008958] [NEW] please backport 0.12 to jammy

2023-03-01 Thread Dimitri John Ledkov

Public bug reported:

The below significant bugfixes are implemented, which would enable more
power & energy efficient modes on our supported laptops, as well as
enable for the kernel default to change.

0.12

This release adds support for the Intel "Energy Performance Bias" feature, which
can be used on hardware that doesn't have a platform_profile or doesn't support
HWP. It will also be used to eke out a bit more performance, or power, on
systems
which already supported HWP.

More information is available in the README.

0.11.1
--

This release stops power-profiles-daemon from modifying the cpufreq driver when
driver when the user/administrator has chosen to disable the Intel P-State
scaling
governor (eg. forcing a passive operation mode).

More information is available in the README.

0.11

This release fixes problems on Intel machines when the CPUs didn't support
turbo at
all, or the performance scaling governor was built as default in the kernel.

It also adds better end-user documentation, fixes in the command-line tool to
not
cause bug report tools to popup on not-uncommon errors, and a bug fix for
running
on some systems with controllable charge speeds.

** Affects: power-profiles-daemon (Ubuntu)
Importance: Undecided
Status: New

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

Title:
please backport 0.12 to jammy

Status in power-profiles-daemon package in Ubuntu:
New

Bug description:
The below significant bugfixes are implemented, which would enable
more power & energy efficient modes on our supported laptops, as well
as enable for the kernel default to change.

0.12

This release adds support for the Intel "Energy Performance Bias" feature,
which
can be used on hardware that doesn't have a platform_profile or doesn't
support
HWP. It will also be used to eke out a bit more performance, or power, on
systems
which already supported HWP.

More information is available in the README.

0.11.1
--

This release stops power-profiles-daemon from modifying the cpufreq driver
when
driver when the user/administrator has chosen to disable the Intel P-State
scaling
governor (eg. forcing a passive operation mode).

More information is available in the README.

0.11

This release fixes problems on Intel machines when the CPUs didn't support
turbo at
all, or the performance scaling governor was built as default in the kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/2008958/+subscriptions

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

Re: [Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap

2023-03-01 Thread bamyasi

Hi Nathan,

Quick update: I have tried modifying Chromium profile file per your 
instructions and indeed this silenced the error message. But it had zero 
effect on the GPU bug. I also installed updated kernel which arrived 
today and observed no changes either.

$ uname -a
Linux xx 5.19.0-35-generic #36-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 3 
18:36:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

I am less interested in chromium, which I do not normal use, so haven't 
tried installing from beta channel yet. But I doubt this would be 
different since Firefox shows the same issue with the GPU acceleration 
enabled.

Thanks,

Ivan

On 2/24/23 16:11, Nathan Teodosio wrote:
> Given the error message from chromium.log,
>
>> amdgpu: os_same_file_description couldn't determine if two DRM fds reference 
>> the same file description.
>> If they do, bad things may happen!
> I think this might be the kcmp's denial fault.
>
> Can you please execute the following commands to whitelist the
> syscall[1], restart Chromium and see if the problem persists?
>
> --->
> #Append kcmp to the seccomp profile source
> sudo sh -c 'echo kcmp >> 
> /var/lib/snapd/seccomp/bpf/snap.chromium.chromium.src'
> #Recompile it
> sudo /usr/lib/snapd/snap-seccomp compile 
> /var/lib/snapd/seccomp/bpf/snap.chromium.chromium.src 
> /var/lib/snapd/seccomp/bpf/snap.chromium.chromium.bin
> #Kill chromium and launch it again
> pkill chrom
> chromium
> <---
>
> If you followed the steps correctly, you shouldn't see the syscall being
> denied anymore when launching Chromium.
>
> After testing you can revert the change with
>
> --->
> sudo sed -i '$d' /var/lib/snapd/seccomp/bpf/snap.chromium.chromium.src
> sudo /usr/lib/snapd/snap-seccomp compile 
> /var/lib/snapd/seccomp/bpf/snap.chromium.chromium.src 
> /var/lib/snapd/seccomp/bpf/snap.chromium.chromium.bin
> <---
>
> [1]https://snapcraft.io/docs/debug-snaps
>
-- 
Ivan Adzhubey, Ph.D.
Research Associate
Dept of Biomedical Informatics
Harvard Medical School
10 Shattuck Street, Suite 514
Boston, MA 02115
tel: (617) 432-2144
fax: (617) 432-0693
web:http://genetics.bwh.harvard.edu/wiki/sunyaevlab/

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

Title:
  Hardware acceleration broken for amdgpu/mesa in snap

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

Bug description:
  Snap packages which use hardware accelerated graphics are broken after
  the last routine system upgrade via apt. My system is using AMD Radeon
  RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers.
  Two snap packages which are now unusable are Mozilla Firefox and
  Chromium browsers. Both display animated speckled color garbage inside
  their windows, overlayed with the correct image. Disabling hardware
  acceleration in the settings for the snap version of Firefox fixed it.
  Also, Firefox version installed from the original Mozilla tarball into
  /opt/ works just fine with the acceleration enabled on the same
  system, as well as glmark2 benchmark. Looks like the issue is only
  affecting snap packages.

  $ snap list firefox chromium
  Name  Version Rev   Tracking   Publisher   Notes
  chromium  109.0.5414.119  2295  latest/stable  canonical✓  -
  firefox   109.0.1-1   2311  latest/stable  mozilla✓-

  $ dpkg -l snapd|grep ^ii
  ii  snapd  2.58+22.10   amd64Daemon and tooling that enable 
snap packages

  $ dpkg -l mesa\* | grep ^ii
  ii  mesa-utils8.5.0-1   amd64Miscellaneous 
Mesa utilities -- symlinks
  ii  mesa-utils-bin:amd64  8.5.0-1   amd64Miscellaneous 
Mesa utilities -- native applications
  ii  mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API 
video acceleration drivers
  ii  mesa-vdpau-drivers:amd64  22.2.5-0ubuntu0.1 amd64Mesa VDPAU video 
acceleration drivers
  ii  mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan 
graphics drivers

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 22.10
  Release:22.10
  Codename:   kinetic

  $ uname -a
  Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 
12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: snap (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Feb  1 22:55:48 2023
  InstallationDate: Installed on 2020-08-02 (913 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: snap
  UpgradeStatus: Upgraded to kinetic on

[Desktop-packages] [Bug 1978980] Re: [amdgpu] Wrong external screen resolution after wake up from sleep

2023-03-01 Thread Dyson Lu

Experiencing this as well.

22.04 LTS
Lenovo Lenovo YOGA 720-15IKB
Intel® HD Graphics 630 
External Dell monitor native resolution 2560x1440, connected through USB-C

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

Title:
  [amdgpu] Wrong external screen resolution after wake up from sleep

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  After the Ubuntu distro upgrade (upgrade from LTS 20.04 to LTS 22.04,
  running KDE) I started experiencing a problem with external screen
  resolution after the wake up from sleep. The monitor resolution is
  small (1280x768) and doesn't respect the setting prior the sleep
  (1920x1200).

  After the wake up from sleep:

  ```
  > xrandr
  HDMI-A-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x 
axis y axis) 535mm x 339mm
 1280x768  59.94* 
 # a list of lower resolutions
  ```

  There is an error when trying to change the setting to the highest
  resolution supported by the monitor (which is not included in the
  above list).

  ```
  > xrandr --output DisplayPort-1 --mode 1920x1200
  xrandr: cannot find mode 1920x1200
  ```

  After the turn off and turn on of the external monitor, the resolution
  is somehow added to the xrandr list:

  ```
  > xrandr
  HDMI-A-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x 
axis y axis) 535mm x 339mm
 1920x1200 59.95 +
 # a list of resolutions
 1280x768  59.94* 
 # a list of lower resolutions
  ```

  Now it is possible to change the resolution:

  ```
  > xrandr --output DisplayPort-1 --mode 1920x1200
  # no output, the resolution was successfully changed
  ```   

  After the change, the resolution is successfully changed and xrandr
  gives proper output:

  ```
  > xrandr
  HDMI-A-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-0 disconnected (normal left inverted right x axis y axis)
  DisplayPort-1 connected primary 1920x1200+0+0 (normal left inverted right x 
axis y axis) 535mm x 339mm
 1920x1200 59.95*+
 # a list of lower resolutions
  ```

  The problem is not present on fresh start. However, it is consistently
  present after the wake up from sleep.

  What can cause the problem and how may I fix it?

  Running AMD based laptop (Ryzen 7 3700U with integrated graphics), the
  external monitor is connected via USB-C. There are no problems with
  laptop screen resolution, only external monitor is affected.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
  Uname: Linux 5.15.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Jun 16 18:12:05 2022
  DistUpgraded: 2022-05-08 07:52:25,560 DEBUG icon theme changed, re-reading
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2019-08-21 (1030 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20NE000BMC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic 
root=UUID=0fff4104-4909-4124-b8b0-8430281f24be ro open splash iommu=soft 
vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-05-08 (39 days ago)
  dmi.bios.date: 01/26/2022
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET44W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NE000BMC
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR11ET44W(1.24):bd01/26/2022:br1.24:efr1.24:svnLENOVO:pn20NE000BMC:pvrThinkPadE495:rvnLENOVO:rn20NE000BMC:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NE_BU_Think_FM_ThinkPadE495:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NE000BMC
  dmi.product.sku:

[Desktop-packages] [Bug 2008951] [NEW] Ubuntu 22.04 on Lenovo Legion 5 Laptop occasional boot freeze and and unexpected reboots

2023-03-01 Thread pd71sat

Public bug reported:

Problem occurs with "ubuntu-drivers install" beforehand, and in trying
to resolve resorted to manual nvidia drivers install approach. Problem
recurs anyway.

Now not sure is nvidia issue as sometimes bluetooth does not get
recognized as now (in this session).

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.5-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-32-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar  1 18:33:58 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-11-18 (103 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.5-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  Ubuntu 22.04 on Lenovo Legion 5 Laptop occasional boot freeze and and
  unexpected reboots

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Problem occurs with "ubuntu-drivers install" beforehand, and in trying
  to resolve resorted to manual nvidia drivers install approach. Problem
  recurs anyway.

  Now not sure is nvidia issue as sometimes bluetooth does not get
  recognized as now (in this session).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.5-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  1 18:33:58 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-11-18 (103 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps

@Jeremy: I figured out the nature of the issue you originally reported
in this bug. With this combo:

$ dpkg-query -W libglib2.0-0 gnome-settings-daemon
gnome-settings-daemon   44~beta-1ubuntu1
libglib2.0-0:amd64  2.75.3-3

and as long as no IBus IM has been added to the list of input sources,
you can successfully run the Firefox snap in a wayland session. I.e.
with that upstream gnome-settings-daemon commit reverted.

If you had tried an x11 session, you'd have found that the reversal
didn't help (because of im-config 0.55-1).

And if you had added some IBus IM (and re-logged in), you'd likewise
have found that the reversal didn't help.

What does help in all cases ATM is to downgrade the glib2.0 packages to
2.74. So somehow the snaps need to be able to talk with ibus also when
glib2.0 2.75 is present.

** Tags removed: update-excuse

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

Title:
  glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps

Status in glib2.0 package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New

Bug description:
  While preparing the gnome-settings-daemon 44 Beta update for Ubuntu
  23.04, I noticed that I could no longer enter text in the address bars
  for the Chromium or Firefox snaps.

  Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/commit/27bc0889c so that we could continue with the update.
  See https://salsa.debian.org/gnome-team/gnome-settings-
  daemon/-/commit/baeeed93

  Before I did that, I tested disabling our patches but it didn't make a
  difference.

  I was unable to reproduce the issue on Debian Testing but there may
  have been differences in how snap was configured there.

  I'm filing this bug since ideally we would not be diverging from
  upstream here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions


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

[Desktop-packages] [Bug 2008892] Re: "Gave up waiting for root file system device" after fresh installation of Ubuntu 22.04

2023-03-01 Thread Steve Langasek

plymouth is only responsible for the splash screen, it has nothing to do
with why you've ended up at a shell.  Reassigning to mdadm as a starting
point.

What is /dev/mapper/isw_behfgagcfc_ASUS_OS?  I don't recognize this as a
standard name and don't know what package is supposed to configure it at
boot time.

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

** Package changed: plymouth (Ubuntu) => mdadm (Ubuntu)

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

Title:
  "Gave up waiting for root file system device" after fresh installation
  of Ubuntu 22.04

Status in mdadm package in Ubuntu:
  Incomplete

Bug description:
  After running the 22.04 installer, my laptop would restart and after
  seeing the initial loading screen I'm dropped to a busybox shell. It
  makes no difference what boot option I use from my UEFI or installing
  with or without disk encrpytion.

  The installer finds my disk without problems, but afer rebooting the
  Ubuntu screen hangs for around a minute before dropping me into a
  busybox shell.

  In this shell I do the following:

  ```
  # ls /dev/mapper
  control   isw_behfgagcfc_ASUS_OS

  # kpartx -av /dev/mapper/isw_behfgagcfc_ASUS_OS
  add map isw_behfgagcfc_ASUS_OS1 (253:1): 0 1048576 linear 253:0 2048
  add map isw_behfgagcfc_ASUS_OS2 (253:2): 0 3500032 linear 253:0 1050624
  add map isw_behfgagcfc_ASUS_OS3 (253:3): 0 495579136 linear 253:0 4550656

  # cryptsetup luksOpen /dev/mapper/isw_behfgagcfc_ASUS_OS3 WHYEVER
  Enter passphrase for /dev/mapper/isw_behfgagcfc_ASUS_OS3: ***

  # exit
  ```

  After which the Ubuntu loading screen re-appears and I have to enter
  the disk decrypt key again. Then my system boots fine, but I think
  it's a bug to have these commands to manually every time.

  If I install without disk-encryption, I still have to run "kpartx -av
  /dev/mapper/isw_behfgagfc_ASUS_OS" in the busybox shell before I'm
  able to continue.

  Attached the log from apport inside the finally booted Ubuntu
  installation with disk-encryption on.

  PS: The same error occurs when upgrading from from 21.10 to 22.04.

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


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

[Desktop-packages] [Bug 1988836] Re: LRMv7: Enable the open NVIDIA kernel modules

This bug was fixed in the package linux-restricted-modules -
5.19.0-35.36

---
linux-restricted-modules (5.19.0-35.36) kinetic; urgency=medium

  * Master version: 5.19.0-35.36

  * LRMv7: Enable the open NVIDIA kernel modules (LP: #1988836)
- [Packaging] convert to v7.2 autogen form

  * Miscellaneous Ubuntu changes
- debian/tracking-bug -- update from master

linux-restricted-modules (5.19.0-34.35+3) kinetic; urgency=medium

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (adhoc/2023.01.30)
- update spin to 2023.01.30-2

  * LRMv7: Enable the open NVIDIA kernel modules (LP: #1988836)
- [Packaging] convert to direct ancillaries
- [Packaging] convert to v7.1 autogen form

linux-restricted-modules (5.19.0-34.35) kinetic; urgency=medium

  * Master version: 5.19.0-34.35

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2023.01.30)

  * Miscellaneous Ubuntu changes
- debian/tracking-bug -- update from master

 -- Luke Nowakowski-Krijger   Fri,
03 Feb 2023 10:19:12 -0800

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

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

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


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

[Desktop-packages] [Bug 1988836] Re: LRMv7: Enable the open NVIDIA kernel modules

This bug was fixed in the package linux-restricted-modules -
5.15.0-67.74

---
linux-restricted-modules (5.15.0-67.74) jammy; urgency=medium

  * Master version: 5.15.0-67.74

  * Miscellaneous Ubuntu changes
- debian/tracking-bug -- update from master

linux-restricted-modules (5.15.0-66.73) jammy; urgency=medium

  * Master version: 5.15.0-66.73

  * LRMv7: Enable the open NVIDIA kernel modules (LP: #1988836)
- [Packaging] convert to v7.2 autogen form

  * Miscellaneous Ubuntu changes
- debian/tracking-bug -- update from master

linux-restricted-modules (5.15.0-65.72+3) jammy; urgency=medium

  * Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (adhoc/2023.01.30)
- update spin to 2023.01.30-2

  * LRMv7: Enable the open NVIDIA kernel modules (LP: #1988836)
- [Packaging] convert to direct ancillaries
- [Packaging] convert to v7.1 autogen form

linux-restricted-modules (5.15.0-65.72) jammy; urgency=medium

  * Master version: 5.15.0-65.72

  * Packaging resync (LP: #1786013)
- [Packaging] update variants
- debian/dkms-versions -- update from kernel-versions (main/2023.01.30)

  * Miscellaneous Ubuntu changes
- debian/tracking-bug -- update from master

 -- Stefan Bader   Wed, 22 Feb 2023 15:03:25
+0100

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

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

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

Title:
  LRMv7: Enable the open NVIDIA kernel modules

Status in linux-restricted-modules package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in linux-restricted-modules source package in Focal:
  In Progress
Status in nvidia-graphics-drivers-515 source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in linux-restricted-modules source package in Jammy:
  Fix Released
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

   * The 515 series introduced open kernel modules for the NVIDIA driver. They 
come with an open source licence, and should be provided as an option for 
datacenter GPUs:
 
https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/

 Currently, this is only production-ready (and enabled) on
  datacenter GPUs.

   * We should enable signed modules for the 515-open drivers, giving
  users the option to try the drivers.

   * The ubuntu-drivers tool should set a lower priority for the -open
  flavour, so that we do not end up recommending it over the plain 515
  flavour.

  [ Test Plan ]

   * [ubuntu-drivers-common]:
 "sudo ubuntu-drivers install (to make sure the driver is not installed by 
default)"

   * [nvidia driver]

 "sudo ubuntu-drivers install nvidia:515-open" to make sure that the
  driver can be installed manually.

 Please make sure that this installs the correct linux-restricted-
  modules.

 Note: support for GeForce and Workstation GPUs is alpha-quality,
  and is disabled by default. This means that desktop testing is not
  needed at the moment.

  [ Where problems could occur ]

   * This adds a new driver combination, which is not meant to be default, and 
is only enabled for a limited amount of devices (datacenter GPUs).
   * We need to be sure that the driver is not recommended over the other 
drivers.

  [ Other Info ]
   
  -

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


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

[Desktop-packages] [Bug 2007743] Re: intramfs Failed: ZSTD-compressed data

2023-03-01 Thread Julian Andres Klode

Regressions have been reported from the additional fixes in another
distribution so I am hesitating a bit and I'm still waiting to hear back
about which path to take for fixing a bug on bionic (missing
efibootmgr).

So I pivoted to apt work in the meantime while these threads get more
clear.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2007743

Title:
  intramfs Failed: ZSTD-compressed data

Status in grub2-unsigned package in Ubuntu:
  Triaged

Bug description:
  The current updates of Ubuntu 22.04.2 LTS results on boot (black
  screen) the message "not enough memory, press any key" and after comes
  any others "error messages" too and then Ubuntu starts!

  Maybe this Bug results from the current AMD Kernel Updates on "modern"
  Prozessors or Update for the Grub or something - i'don't know - there
  are many System-Updates yesterday and all comes over Ubuntu Store as
  package

  # lsb_release -rd
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04

  # dpkg -l | grep init
  ii  busybox-initramfs  1:1.30.1-7ubuntu3  
  amd64Standalone shell setup for initramfs
  ii  gnome-initial-setup42.0.1-1ubuntu2.3  
  amd64Initial GNOME system setup helper
  ii  init   1.62   
  amd64metapackage ensuring an init system is installed
  ii  init-system-helpers1.62   
  all  helper tools for all init systems
  ii  initramfs-tools0.140ubuntu13.1
  all  generic modular initramfs generator (automation)
  ii  initramfs-tools-bin0.140ubuntu13.1
  amd64binaries used by initramfs-tools
  ii  initramfs-tools-core   0.140ubuntu13.1
  all  generic modular initramfs generator (core tools)
  ii  libatopology2:amd641.2.6.1-1ubuntu1   
  amd64shared library for handling ALSA topology definitions
  ii  libklibc:amd64 2.0.10-4   
  amd64minimal libc subset for use with initramfs
  ii  lsb-base   11.1.0ubuntu4  
  all  Linux Standard Base init script functionality
  ii  ncurses-base   6.3-2  
  all  basic terminal type definitions
  ii  sysvinit-utils 3.01-1ubuntu1  
  amd64System-V-like utilities
  ii  xinit  1.4.1-0ubuntu4 
  amd64X server initialisation tool

  # dpkg -l | grep zfs
  -> brings no information here

  # zfs list
  -> zfs is not installed here

  if you need more system-infos to solve this Bug, please let me know!
  The first error means "Not Enough Memory, Please press any key" - you can 
press any key (but you don't need) and it comes the "intramfs Failed: 
ZSTD-compressed data ..." and then the Ubuntu Login screen comes up.

  Please be patient with me, I'm new to Ubuntu and Launchpad and don't
  know much about it yet

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


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

[Desktop-packages] [Bug 2008920] [NEW] Brltty does not permit Arduino devices to run on ubuntu

2023-03-01 Thread Alexandre Felipe Muller de Souza

Public bug reported:

Every time I start a new ubuntu installation from zero I get some errors
on Arduino devices that does not recognize with the following error:

[  561.144042] usb 1-2: new full-speed USB device number 15 using xhci_hcd
[  561.293021] usb 1-2: New USB device found, idVendor=1a86, idProduct=7523, 
bcdDevice= 2.54
[  561.293028] usb 1-2: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[  561.293031] usb 1-2: Product: USB2.0-Ser!
[  561.294936] ch341 1-2:1.0: ch341-uart converter detected
[  561.295634] ch341-uart ttyUSB0: break control not supported, using simulated 
break
[  561.295695] usb 1-2: ch341-uart converter now attached to ttyUSB0
[  561.845448] input: BRLTTY 6.5 Linux Screen Driver Keyboard as 
/devices/virtual/input/input28
[  561.961485] usb 1-2: usbfs: interface 0 claimed by ch341 while 'brltty' sets 
config #1
[  561.961910] ch341-uart ttyUSB0: ch341-uart converter now disconnected from 
ttyUSB0
[  561.961937] ch341 1-2:1.0: device disconnected


So I have to remove brltty manually (apt remove brltty), that just no problem. 
But I think this modulo shouldn't disable others serial devices by default. In 
summary its sad that, for default, ubuntu does not work with arduino. For me 
this is a bug, or brltty should be default if it can't live with others devices.

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

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

Title:
  Brltty does not permit Arduino devices to run on ubuntu

Status in brltty package in Ubuntu:
  New

Bug description:
  Every time I start a new ubuntu installation from zero I get some
  errors on Arduino devices that does not recognize with the following
  error:

  [  561.144042] usb 1-2: new full-speed USB device number 15 using xhci_hcd
  [  561.293021] usb 1-2: New USB device found, idVendor=1a86, idProduct=7523, 
bcdDevice= 2.54
  [  561.293028] usb 1-2: New USB device strings: Mfr=0, Product=2, 
SerialNumber=0
  [  561.293031] usb 1-2: Product: USB2.0-Ser!
  [  561.294936] ch341 1-2:1.0: ch341-uart converter detected
  [  561.295634] ch341-uart ttyUSB0: break control not supported, using 
simulated break
  [  561.295695] usb 1-2: ch341-uart converter now attached to ttyUSB0
  [  561.845448] input: BRLTTY 6.5 Linux Screen Driver Keyboard as 
/devices/virtual/input/input28
  [  561.961485] usb 1-2: usbfs: interface 0 claimed by ch341 while 'brltty' 
sets config #1
  [  561.961910] ch341-uart ttyUSB0: ch341-uart converter now disconnected from 
ttyUSB0
  [  561.961937] ch341 1-2:1.0: device disconnected

  
  So I have to remove brltty manually (apt remove brltty), that just no 
problem. But I think this modulo shouldn't disable others serial devices by 
default. In summary its sad that, for default, ubuntu does not work with 
arduino. For me this is a bug, or brltty should be default if it can't live 
with others devices.

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


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

[Desktop-packages] [Bug 2008919] [NEW] [FFe] Implement support for "buttercup_eval"

2023-03-01 Thread Sergio Durigan Junior

Public bug reported:

dh-elpa supports the "ert_eval" directive inside d/elpa-test, which
allows the package to provide custom Elisp code to be executed before
ERT is invoked.  Unfortunately, a similar feature is missing for
buttercup tests.  This means that, whenever a package uses buttercup to
run its tests, the maintainer needs to override dh_elpa_test and invoke
buttercup by hand.  This, however, only works during build time; dh-elpa
is also used to run autopkgtest, and in that specific scenario it's not
possible to execute custom Elisp code using buttercup at all.

Why is this important, you might ask.  Well, I've been investigating a
bug in Emacs 28.2's native compilation mechanism which affects a bunch
of packages (see bug #2006963 for more details).  One of those affected
packages is flycheck, which uses buttercup.  I uploaded a fix for a
flycheck FTBFS which addresses the problem, but the package still fails
its autopkgtest because of the problem mentioned above.

Long story short, I've implemented the support for a new dh-elpa
directive called "buttercup_eval" and would like it to Lunar.  I also
proposed the feature to Debian here: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1032202

** Affects: dh-elpa (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: dh-elpa (Debian)
 Importance: Unknown
 Status: Unknown

** Bug watch added: Debian Bug tracker #1032202
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032202

** Also affects: dh-elpa (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032202
   Importance: Unknown
   Status: Unknown

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

Title:
  [FFe] Implement support for "buttercup_eval"

Status in dh-elpa package in Ubuntu:
  New
Status in dh-elpa package in Debian:
  Unknown

Bug description:
  dh-elpa supports the "ert_eval" directive inside d/elpa-test, which
  allows the package to provide custom Elisp code to be executed before
  ERT is invoked.  Unfortunately, a similar feature is missing for
  buttercup tests.  This means that, whenever a package uses buttercup
  to run its tests, the maintainer needs to override dh_elpa_test and
  invoke buttercup by hand.  This, however, only works during build
  time; dh-elpa is also used to run autopkgtest, and in that specific
  scenario it's not possible to execute custom Elisp code using
  buttercup at all.

  Why is this important, you might ask.  Well, I've been investigating a
  bug in Emacs 28.2's native compilation mechanism which affects a bunch
  of packages (see bug #2006963 for more details).  One of those
  affected packages is flycheck, which uses buttercup.  I uploaded a fix
  for a flycheck FTBFS which addresses the problem, but the package
  still fails its autopkgtest because of the problem mentioned above.

  Long story short, I've implemented the support for a new dh-elpa
  directive called "buttercup_eval" and would like it to Lunar.  I also
  proposed the feature to Debian here: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1032202

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


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

[Desktop-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps

ibus in lunar-release was built against glib2.0 2.74.5-1. I tried a no-
change rebuild of ibus against glib2.0 2.75.3-3, but it didn't help.

(Such a rebuild may still be motivated later.)

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

Title:
  glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps

Status in glib2.0 package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New

Bug description:
  While preparing the gnome-settings-daemon 44 Beta update for Ubuntu
  23.04, I noticed that I could no longer enter text in the address bars
  for the Chromium or Firefox snaps.

  Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/commit/27bc0889c so that we could continue with the update.
  See https://salsa.debian.org/gnome-team/gnome-settings-
  daemon/-/commit/baeeed93

  Before I did that, I tested disabling our patches but it didn't make a
  difference.

  I was unable to reproduce the issue on Debian Testing but there may
  have been differences in how snap was configured there.

  I'm filing this bug since ideally we would not be diverging from
  upstream here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions


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

[Desktop-packages] [Bug 1969315] Re: text in torrent info tabs change after opening it to gibberish

2023-03-01 Thread houdini68

On Ubuntu 22.04, I have switched 'temporarily' to transmission-qt.
sudo apt install transmission-qt
Then you can create an alias to temporarily replace the faulty 
'transmission-gtk'.
alias transmission='/usr/bin/transmission-qt'
transmission-qt doesn't exhibit the faulty behaviour (and CTRL+S is back).

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

Title:
  text in torrent info tabs change after opening it to gibberish

Status in transmission package in Ubuntu:
  Confirmed

Bug description:
  on transmission-gtk

  after opening the torrent's properties panel, the text at first it's showing 
ok, buy on mouse hover it changes to random text
  worked fine on 21.10

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: transmission-gtk 3.00-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 17 19:28:03 2022
  SourcePackage: transmission
  UpgradeStatus: Upgraded to jammy on 2022-03-26 (22 days ago)

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


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

[Desktop-packages] [Bug 2008907] Re: Ubuntu 22.04.2 Update GNOME-Software fails

the problem solved itself by unknown reason. Unfortunately i can't close
or delete this bug.

** Changed in: gnome-software (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2008907

Title:
  Ubuntu 22.04.2 Update GNOME-Software fails

Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  I have currently some updates on the Ubuntu Store, but i can't install
  them, the Ubuntu Store results

  Prepared update not found: /var/lib/PackageKit/prepared-update

  If i run

  # sudo apt-get update && sudo apt-get dist-upgrade

  I get this (sorry german only):

  Die folgenden Pakete sind zurückgehalten worden:
    chromium-codecs-ffmpeg-extra evince evince-common fonts-opensymbol
    gir1.2-pango-1.0 isc-dhcp-client isc-dhcp-common libevdocument3-4
    libevview3-3 libmbim-glib4 libmbim-proxy libmm-glib0 libpango-1.0-0
    libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libqmi-glib5
    libqmi-proxy libreoffice-base-core libreoffice-calc libreoffice-common
    libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk3
    libreoffice-help-common libreoffice-help-de libreoffice-help-en-us
    libreoffice-impress libreoffice-l10n-de libreoffice-math
    libreoffice-ogltrans libreoffice-pdfimport libreoffice-style-breeze
    libreoffice-style-colibre libreoffice-style-elementary
    libreoffice-style-yaru libreoffice-writer libsasl2-2 libsasl2-modules
    libsasl2-modules-db libsasl2-modules-gssapi-mit libsnmp-base libsnmp40
    libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3
    libuno-salhelpergcc3-3 modemmanager python3-macaroonbakery
    python3-software-properties python3-uno software-properties-common
    software-properties-gtk uno-libs-private ure

  and yes, indeed, this file /var/lib/PackageKit/prepared-update really
  don't exists but why?

  I have also tried to stop the gnome-software and restart, in this case
  the Ubuntu Store fetch the data new, but this also do not help - the
  same updates come up but i can't install them.

  https://abload.de/img/bildschirmfotovom20237pdzo.png

  Or is this a result of this:
  https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2007743

  And i have little investigated this error, and i found out, that Red Hat had 
in 2021 a similar issue
  https://bugzilla.redhat.com/show_bug.cgi?id=1995817

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


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

[Desktop-packages] [Bug 2008907] Re: Ubuntu 22.04.2 Update GNOME-Software fails

sorry, please ignore this BUG here, i don't know why but now i was able
to download the updates and install it successfully.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2008907

Title:
  Ubuntu 22.04.2 Update GNOME-Software fails

Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  I have currently some updates on the Ubuntu Store, but i can't install
  them, the Ubuntu Store results

  Prepared update not found: /var/lib/PackageKit/prepared-update

  If i run

  # sudo apt-get update && sudo apt-get dist-upgrade

  I get this (sorry german only):

  Die folgenden Pakete sind zurückgehalten worden:
    chromium-codecs-ffmpeg-extra evince evince-common fonts-opensymbol
    gir1.2-pango-1.0 isc-dhcp-client isc-dhcp-common libevdocument3-4
    libevview3-3 libmbim-glib4 libmbim-proxy libmm-glib0 libpango-1.0-0
    libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libqmi-glib5
    libqmi-proxy libreoffice-base-core libreoffice-calc libreoffice-common
    libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk3
    libreoffice-help-common libreoffice-help-de libreoffice-help-en-us
    libreoffice-impress libreoffice-l10n-de libreoffice-math
    libreoffice-ogltrans libreoffice-pdfimport libreoffice-style-breeze
    libreoffice-style-colibre libreoffice-style-elementary
    libreoffice-style-yaru libreoffice-writer libsasl2-2 libsasl2-modules
    libsasl2-modules-db libsasl2-modules-gssapi-mit libsnmp-base libsnmp40
    libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3
    libuno-salhelpergcc3-3 modemmanager python3-macaroonbakery
    python3-software-properties python3-uno software-properties-common
    software-properties-gtk uno-libs-private ure

  and yes, indeed, this file /var/lib/PackageKit/prepared-update really
  don't exists but why?

  I have also tried to stop the gnome-software and restart, in this case
  the Ubuntu Store fetch the data new, but this also do not help - the
  same updates come up but i can't install them.

  https://abload.de/img/bildschirmfotovom20237pdzo.png

  Or is this a result of this:
  https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2007743

  And i have little investigated this error, and i found out, that Red Hat had 
in 2021 a similar issue
  https://bugzilla.redhat.com/show_bug.cgi?id=1995817

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


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

[Desktop-packages] [Bug 2007743] Re: intramfs Failed: ZSTD-compressed data

what is the current status of progress here? it would be really nice, if
a bugfix will be released soon.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2007743

Title:
  intramfs Failed: ZSTD-compressed data

Status in grub2-unsigned package in Ubuntu:
  Triaged

Bug description:
  The current updates of Ubuntu 22.04.2 LTS results on boot (black
  screen) the message "not enough memory, press any key" and after comes
  any others "error messages" too and then Ubuntu starts!

  Maybe this Bug results from the current AMD Kernel Updates on "modern"
  Prozessors or Update for the Grub or something - i'don't know - there
  are many System-Updates yesterday and all comes over Ubuntu Store as
  package

  # lsb_release -rd
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04

  # dpkg -l | grep init
  ii  busybox-initramfs  1:1.30.1-7ubuntu3  
  amd64Standalone shell setup for initramfs
  ii  gnome-initial-setup42.0.1-1ubuntu2.3  
  amd64Initial GNOME system setup helper
  ii  init   1.62   
  amd64metapackage ensuring an init system is installed
  ii  init-system-helpers1.62   
  all  helper tools for all init systems
  ii  initramfs-tools0.140ubuntu13.1
  all  generic modular initramfs generator (automation)
  ii  initramfs-tools-bin0.140ubuntu13.1
  amd64binaries used by initramfs-tools
  ii  initramfs-tools-core   0.140ubuntu13.1
  all  generic modular initramfs generator (core tools)
  ii  libatopology2:amd641.2.6.1-1ubuntu1   
  amd64shared library for handling ALSA topology definitions
  ii  libklibc:amd64 2.0.10-4   
  amd64minimal libc subset for use with initramfs
  ii  lsb-base   11.1.0ubuntu4  
  all  Linux Standard Base init script functionality
  ii  ncurses-base   6.3-2  
  all  basic terminal type definitions
  ii  sysvinit-utils 3.01-1ubuntu1  
  amd64System-V-like utilities
  ii  xinit  1.4.1-0ubuntu4 
  amd64X server initialisation tool

  # dpkg -l | grep zfs
  -> brings no information here

  # zfs list
  -> zfs is not installed here

  if you need more system-infos to solve this Bug, please let me know!
  The first error means "Not Enough Memory, Please press any key" - you can 
press any key (but you don't need) and it comes the "intramfs Failed: 
ZSTD-compressed data ..." and then the Ubuntu Login screen comes up.

  Please be patient with me, I'm new to Ubuntu and Launchpad and don't
  know much about it yet

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


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

[Desktop-packages] [Bug 2007743] [NEW] intramfs Failed: ZSTD-compressed data

You have been subscribed to a public bug by Marc Püschel (newcomer-01):

The current updates of Ubuntu 22.04.2 LTS results on boot (black screen)
the message "not enough memory, press any key" and after comes any
others "error messages" too and then Ubuntu starts!

Maybe this Bug results from the current AMD Kernel Updates on "modern"
Prozessors or Update for the Grub or something - i'don't know - there
are many System-Updates yesterday and all comes over Ubuntu Store as
package

# lsb_release -rd
Description:Ubuntu 22.04.2 LTS
Release:22.04

# dpkg -l | grep init
ii  busybox-initramfs  1:1.30.1-7ubuntu3
amd64Standalone shell setup for initramfs
ii  gnome-initial-setup42.0.1-1ubuntu2.3
amd64Initial GNOME system setup helper
ii  init   1.62 
amd64metapackage ensuring an init system is installed
ii  init-system-helpers1.62 
all  helper tools for all init systems
ii  initramfs-tools0.140ubuntu13.1  
all  generic modular initramfs generator (automation)
ii  initramfs-tools-bin0.140ubuntu13.1  
amd64binaries used by initramfs-tools
ii  initramfs-tools-core   0.140ubuntu13.1  
all  generic modular initramfs generator (core tools)
ii  libatopology2:amd641.2.6.1-1ubuntu1 
amd64shared library for handling ALSA topology definitions
ii  libklibc:amd64 2.0.10-4 
amd64minimal libc subset for use with initramfs
ii  lsb-base   11.1.0ubuntu4
all  Linux Standard Base init script functionality
ii  ncurses-base   6.3-2
all  basic terminal type definitions
ii  sysvinit-utils 3.01-1ubuntu1
amd64System-V-like utilities
ii  xinit  1.4.1-0ubuntu4   
amd64X server initialisation tool

# dpkg -l | grep zfs
-> brings no information here

# zfs list
-> zfs is not installed here

if you need more system-infos to solve this Bug, please let me know!
The first error means "Not Enough Memory, Please press any key" - you can press 
any key (but you don't need) and it comes the "intramfs Failed: ZSTD-compressed 
data ..." and then the Ubuntu Login screen comes up.

Please be patient with me, I'm new to Ubuntu and Launchpad and don't
know much about it yet

** Affects: grub2-unsigned (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: bot-comment intramfs
-- 
intramfs Failed: ZSTD-compressed data
https://bugs.launchpad.net/bugs/2007743
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to the bug report.

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

[Desktop-packages] [Bug 2008907] Re: Ubuntu 22.04.2 Update GNOME-Software fails

** Description changed:

  I have currently some updates on the Ubuntu Store, but i can't install
  them, the Ubuntu Store results
  
  Prepared update not found: /var/lib/PackageKit/prepared-update
  
  If i run
  
  # sudo apt-get update && sudo apt-get dist-upgrade
  
  I get this (sorry german only):
  
  Die folgenden Pakete sind zurückgehalten worden:
    chromium-codecs-ffmpeg-extra evince evince-common fonts-opensymbol
    gir1.2-pango-1.0 isc-dhcp-client isc-dhcp-common libevdocument3-4
    libevview3-3 libmbim-glib4 libmbim-proxy libmm-glib0 libpango-1.0-0
    libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libqmi-glib5
    libqmi-proxy libreoffice-base-core libreoffice-calc libreoffice-common
    libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk3
    libreoffice-help-common libreoffice-help-de libreoffice-help-en-us
    libreoffice-impress libreoffice-l10n-de libreoffice-math
    libreoffice-ogltrans libreoffice-pdfimport libreoffice-style-breeze
    libreoffice-style-colibre libreoffice-style-elementary
    libreoffice-style-yaru libreoffice-writer libsasl2-2 libsasl2-modules
    libsasl2-modules-db libsasl2-modules-gssapi-mit libsnmp-base libsnmp40
    libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3
    libuno-salhelpergcc3-3 modemmanager python3-macaroonbakery
    python3-software-properties python3-uno software-properties-common
    software-properties-gtk uno-libs-private ure
  
  and yes, indeed, this file /var/lib/PackageKit/prepared-update really
  don't exists but why?
  
  I have also tried to stop the gnome-software and restart, in this case
  the Ubuntu Store fetch the data new, but this also do not help - the
  same updates come up but i can't install them.
  
  https://abload.de/img/bildschirmfotovom20237pdzo.png
+ 
+ Or is this a result of this:
+ https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2007743

** Description changed:

  I have currently some updates on the Ubuntu Store, but i can't install
  them, the Ubuntu Store results
  
  Prepared update not found: /var/lib/PackageKit/prepared-update
  
  If i run
  
  # sudo apt-get update && sudo apt-get dist-upgrade
  
  I get this (sorry german only):
  
  Die folgenden Pakete sind zurückgehalten worden:
    chromium-codecs-ffmpeg-extra evince evince-common fonts-opensymbol
    gir1.2-pango-1.0 isc-dhcp-client isc-dhcp-common libevdocument3-4
    libevview3-3 libmbim-glib4 libmbim-proxy libmm-glib0 libpango-1.0-0
    libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libqmi-glib5
    libqmi-proxy libreoffice-base-core libreoffice-calc libreoffice-common
    libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk3
    libreoffice-help-common libreoffice-help-de libreoffice-help-en-us
    libreoffice-impress libreoffice-l10n-de libreoffice-math
    libreoffice-ogltrans libreoffice-pdfimport libreoffice-style-breeze
    libreoffice-style-colibre libreoffice-style-elementary
    libreoffice-style-yaru libreoffice-writer libsasl2-2 libsasl2-modules
    libsasl2-modules-db libsasl2-modules-gssapi-mit libsnmp-base libsnmp40
    libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3
    libuno-salhelpergcc3-3 modemmanager python3-macaroonbakery
    python3-software-properties python3-uno software-properties-common
    software-properties-gtk uno-libs-private ure
  
  and yes, indeed, this file /var/lib/PackageKit/prepared-update really
  don't exists but why?
  
  I have also tried to stop the gnome-software and restart, in this case
  the Ubuntu Store fetch the data new, but this also do not help - the
  same updates come up but i can't install them.
  
  https://abload.de/img/bildschirmfotovom20237pdzo.png
  
  Or is this a result of this:
  https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2007743
+ 
+ And i have little investigated this error, and i found out, that Red Hat had 
in 2021 a similar issue
+ https://bugzilla.redhat.com/show_bug.cgi?id=1995817

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2008907

Title:
  Ubuntu 22.04.2 Update GNOME-Software fails

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I have currently some updates on the Ubuntu Store, but i can't install
  them, the Ubuntu Store results

  Prepared update not found: /var/lib/PackageKit/prepared-update

  If i run

  # sudo apt-get update && sudo apt-get dist-upgrade

  I get this (sorry german only):

  Die folgenden Pakete sind zurückgehalten worden:
    chromium-codecs-ffmpeg-extra evince evince-common fonts-opensymbol
    gir1.2-pango-1.0 isc-dhcp-client isc-dhcp-common libevdocument3-4
    libevview3-3 libmbim-glib4 libmbim-proxy libmm-glib0 libpango-1.0-0
    libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libqmi-glib5
    libqmi-proxy libreoffice-base-core libreoffice-calc libreoffice-common

[Desktop-packages] [Bug 2007746] Re: [SRU] xserver crashes when hyperv_drm kernel module is loaded on azure NV series instances w/ nvidia grid driver

2023-03-01 Thread Dariusz Gadomski

** Tags added: se-sponsor-dgadomski

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

Title:
  [SRU] xserver crashes when hyperv_drm kernel module is loaded on azure
  NV series instances w/ nvidia grid driver

Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Focal:
  In Progress

Bug description:
  [ Impact ]

   * Microsoft Azure NV-series instances with NVidia GRID drivers
  started to experience xserver crashes while following Microsoft's
  official guide to installing Nvidia drivers [1].

   * Root cause analysis showed that it was due to having a device with
  BusID "PCI:0@:0:0", where domain id is >= 32767 while the
  hyperv_drm kernel module is loaded.

   * Removing either the BusID specification or unloading the hyperv_drm
  kernel module seems to fix the crash.

   * The crash is happening while X.server is trying to enumerate PCI
  devices. X.server dereferences a NULL pointer while trying to access
  to the PCI device info.

   * The reason why it only happens while the hyperv_drm kernel module
  is loaded is that the hyperv_drm module does not expose PCI hardware
  information since it's a virtual device.

   * The upstream patch [2] addresses the issue and it's confirmed that
  the xserver with the patch does not experience the crash.

   * Ubuntu Focal `xorg-server` package does not include the patch [2]
  at the moment (xserver-xorg-core=2:1.20.13-1ubuntu1~20.04.6).

   [1]: 
https://learn.microsoft.com/en-us/azure/virtual-machines/linux/n-series-driver-setup#install-grid-drivers-on-nv-or-nvv3-series-vms
   [2]: 
https://github.com/freedesktop/xorg-xserver/commit/0d93bbfa2cfacbb73741f8bed0e32fa1a656b928

  [ Test Plan ]

  Part (a) is quoted from Microsoft's official guide [1].

  Part (a):

   * Spawn a Microsoft Azure NV-series instance with an NVidia GRID-supported 
GPU
     - e.g. `NV36adms A10`
   * Install updates, required tooling, and the desktop environment:
     - sudo apt-get update
     - sudo apt-get upgrade -y
     - sudo apt-get dist-upgrade -y
     - sudo apt-get install build-essential ubuntu-desktop -y
     - sudo apt-get install linux-azure -y
   * Disable nouveau kernel driver:
     # Create a blacklist file /etc/modprobe.d/nouveau.conf with following 
contents:
     blacklist nouveau
     blacklist lbm-nouveau
   * Reboot the VM, re-connect, and then stop X server:
     - sudo reboot
     # wait for the reboot, reconnect, and continue:
     - sudo systemctl stop lightdm.service
   * Download and install the NVidia GRID driver:
     - wget -O NVIDIA-Linux-x86_64-grid.run 
https://go.microsoft.com/fwlink/?linkid=874272
     - chmod +x NVIDIA-Linux-x86_64-grid.run
     - sudo ./NVIDIA-Linux-x86_64-grid.run
     - # When the setup asks whether you want to run the nvidia-xconfig utility 
to update your X configuration file, select Yes.
   * Copy /etc/nvidia/gridd.conf.template to /etc/nvidia/gridd.conf
     - sudo cp /etc/nvidia/gridd.conf.template /etc/nvidia/gridd.conf
   * Edit /etc/nvidia/grid.conf
     - sudo nano /etc/nvidia/grid.conf
     # Append the following lines:
     IgnoreSP=FALSE
     EnableUI=FALSE
     # Remove this line if present:
     FeatureType=0
     # And save.
   * Reboot the VM

   Part (b):

    * Ensure that the hyperv_drm kernel module is loaded:
  - sudo modprobe hyperv_drm
    * Use the attached xorg.conf file to override /etc/X11/xorg.conf file
    * try to start the `xserver`:
  - sudo startx
    * `xserver` should crash with a similar output to the following:
    X.Org X Server 1.20.13
    X Protocol Version 11, Revision 0
    Build Operating System: linux Ubuntu
    Current Operating System: Linux a10test 5.15.0-1031-azure 
#38~20.04.1-Ubuntu SMP Mon Jan 9 18:23:48 UTC 2023 x86_64
    Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1031-azure 
root=PARTUUID=4cac852b-afba-447b-b3e7-c002155c1305 ro console=tty1 
console=ttyS0 earlyprintk=ttyS0 panic=-1
    Build Date: 07 February 2023  12:48:13PM
    xorg-server 2:1.20.13-1ubuntu1~20.04.6 (For technical support please see 
http://www.ubuntu.com/support)
    Current version of pixman: 0.38.4
  Before reporting problems, check http://wiki.x.org
  to make sure that you have the latest version.
    Markers: (--) probed, (**) from config file, (==) default setting,
  (++) from command line, (!!) notice, (II) informational,
  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.1.log", Time: Sat Feb 18 10:54:26 2023
    (==) Using config file: "/etc/X11/xorg.conf"
    (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    (EE)
    (EE) Backtrace:
    (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55e7787c5ecc]
    (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) 
[0x7f9576cac420]
    (EE) 2: /usr/lib/xorg/Xorg

[Desktop-packages] [Bug 2008907] Re: Ubuntu 22.04.2 Update fails

** Description changed:

  I have currently some updates on the Ubuntu Store, but i can't install
  them, the Ubuntu Store results
  
  Prepared update not found: /var/lib/PackageKit/prepared-update
  
  If i run
  
  # sudo apt-get update && sudo apt-get dist-upgrade
  
  I get this (sorry german only):
  
  Die folgenden Pakete sind zurückgehalten worden:
    chromium-codecs-ffmpeg-extra evince evince-common fonts-opensymbol
    gir1.2-pango-1.0 isc-dhcp-client isc-dhcp-common libevdocument3-4
    libevview3-3 libmbim-glib4 libmbim-proxy libmm-glib0 libpango-1.0-0
    libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libqmi-glib5
    libqmi-proxy libreoffice-base-core libreoffice-calc libreoffice-common
    libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk3
    libreoffice-help-common libreoffice-help-de libreoffice-help-en-us
    libreoffice-impress libreoffice-l10n-de libreoffice-math
    libreoffice-ogltrans libreoffice-pdfimport libreoffice-style-breeze
    libreoffice-style-colibre libreoffice-style-elementary
    libreoffice-style-yaru libreoffice-writer libsasl2-2 libsasl2-modules
    libsasl2-modules-db libsasl2-modules-gssapi-mit libsnmp-base libsnmp40
    libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3
    libuno-salhelpergcc3-3 modemmanager python3-macaroonbakery
    python3-software-properties python3-uno software-properties-common
    software-properties-gtk uno-libs-private ure
  
  and yes, indeed, this file /var/lib/PackageKit/prepared-update really
  don't exists but why?
  
  I have also tried to stop the gnome-software and restart, in this case
  the Ubuntu Store fetch the data new, but this also do not help - the
  same updates come up but i can't install them.
  
  https://abload.de/img/bildschirmfotovom20237pdzo.png
- 
- @Julian Andres Klode (juliank):
- 
- ich habe absichtlich dich hier hinzugefügt, weil ich weiß, dass du
- deutsch sprichst ;-)

** Summary changed:

- Ubuntu 22.04.2 Update fails
+ Ubuntu 22.04.2 Update GNOME-Software fails

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2008907

Title:
  Ubuntu 22.04.2 Update GNOME-Software fails

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I have currently some updates on the Ubuntu Store, but i can't install
  them, the Ubuntu Store results

  Prepared update not found: /var/lib/PackageKit/prepared-update

  If i run

  # sudo apt-get update && sudo apt-get dist-upgrade

  I get this (sorry german only):

  Die folgenden Pakete sind zurückgehalten worden:
    chromium-codecs-ffmpeg-extra evince evince-common fonts-opensymbol
    gir1.2-pango-1.0 isc-dhcp-client isc-dhcp-common libevdocument3-4
    libevview3-3 libmbim-glib4 libmbim-proxy libmm-glib0 libpango-1.0-0
    libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libqmi-glib5
    libqmi-proxy libreoffice-base-core libreoffice-calc libreoffice-common
    libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk3
    libreoffice-help-common libreoffice-help-de libreoffice-help-en-us
    libreoffice-impress libreoffice-l10n-de libreoffice-math
    libreoffice-ogltrans libreoffice-pdfimport libreoffice-style-breeze
    libreoffice-style-colibre libreoffice-style-elementary
    libreoffice-style-yaru libreoffice-writer libsasl2-2 libsasl2-modules
    libsasl2-modules-db libsasl2-modules-gssapi-mit libsnmp-base libsnmp40
    libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3
    libuno-salhelpergcc3-3 modemmanager python3-macaroonbakery
    python3-software-properties python3-uno software-properties-common
    software-properties-gtk uno-libs-private ure

  and yes, indeed, this file /var/lib/PackageKit/prepared-update really
  don't exists but why?

  I have also tried to stop the gnome-software and restart, in this case
  the Ubuntu Store fetch the data new, but this also do not help - the
  same updates come up but i can't install them.

  https://abload.de/img/bildschirmfotovom20237pdzo.png

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


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

[Desktop-packages] [Bug 2008907] Re: Ubuntu 22.04.2 Update fails

** Description changed:

  I have currently some updates on the Ubuntu Store, but i can't install
  them, the Ubuntu Store results
  
  Prepared update not found: /var/lib/PackageKit/prepared-update
  
  If i run
  
  # sudo apt-get update && sudo apt-get dist-upgrade
  
  I get this (sorry german only):
  
  Die folgenden Pakete sind zurückgehalten worden:
    chromium-codecs-ffmpeg-extra evince evince-common fonts-opensymbol
    gir1.2-pango-1.0 isc-dhcp-client isc-dhcp-common libevdocument3-4
    libevview3-3 libmbim-glib4 libmbim-proxy libmm-glib0 libpango-1.0-0
    libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libqmi-glib5
    libqmi-proxy libreoffice-base-core libreoffice-calc libreoffice-common
    libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk3
    libreoffice-help-common libreoffice-help-de libreoffice-help-en-us
    libreoffice-impress libreoffice-l10n-de libreoffice-math
    libreoffice-ogltrans libreoffice-pdfimport libreoffice-style-breeze
    libreoffice-style-colibre libreoffice-style-elementary
    libreoffice-style-yaru libreoffice-writer libsasl2-2 libsasl2-modules
    libsasl2-modules-db libsasl2-modules-gssapi-mit libsnmp-base libsnmp40
    libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3
    libuno-salhelpergcc3-3 modemmanager python3-macaroonbakery
    python3-software-properties python3-uno software-properties-common
    software-properties-gtk uno-libs-private ure
  
  and yes, indeed, this file /var/lib/PackageKit/prepared-update really
  don't exists but why?
  
  I have also tried to stop the gnome-software and restart, in this case
  the Ubuntu Store fetch the data new, but this also do not help - the
  same updates come up but i can't install them.
  
+ https://abload.de/img/bildschirmfotovom20237pdzo.png
+ 
  @Julian Andres Klode (juliank):
  
  ich habe absichtlich dich hier hinzugefügt, weil ich weiß, dass du
  deutsch sprichst ;-)

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

Title:
  Ubuntu 22.04.2 Update fails

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I have currently some updates on the Ubuntu Store, but i can't install
  them, the Ubuntu Store results

  Prepared update not found: /var/lib/PackageKit/prepared-update

  If i run

  # sudo apt-get update && sudo apt-get dist-upgrade

  I get this (sorry german only):

  Die folgenden Pakete sind zurückgehalten worden:
    chromium-codecs-ffmpeg-extra evince evince-common fonts-opensymbol
    gir1.2-pango-1.0 isc-dhcp-client isc-dhcp-common libevdocument3-4
    libevview3-3 libmbim-glib4 libmbim-proxy libmm-glib0 libpango-1.0-0
    libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libqmi-glib5
    libqmi-proxy libreoffice-base-core libreoffice-calc libreoffice-common
    libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk3
    libreoffice-help-common libreoffice-help-de libreoffice-help-en-us
    libreoffice-impress libreoffice-l10n-de libreoffice-math
    libreoffice-ogltrans libreoffice-pdfimport libreoffice-style-breeze
    libreoffice-style-colibre libreoffice-style-elementary
    libreoffice-style-yaru libreoffice-writer libsasl2-2 libsasl2-modules
    libsasl2-modules-db libsasl2-modules-gssapi-mit libsnmp-base libsnmp40
    libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3
    libuno-salhelpergcc3-3 modemmanager python3-macaroonbakery
    python3-software-properties python3-uno software-properties-common
    software-properties-gtk uno-libs-private ure

  and yes, indeed, this file /var/lib/PackageKit/prepared-update really
  don't exists but why?

  I have also tried to stop the gnome-software and restart, in this case
  the Ubuntu Store fetch the data new, but this also do not help - the
  same updates come up but i can't install them.

  https://abload.de/img/bildschirmfotovom20237pdzo.png

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


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

[Desktop-packages] [Bug 2008907] [NEW] Ubuntu 22.04.2 Update fails

You have been subscribed to a public bug by Marc Püschel (newcomer-01):

I have currently some updates on the Ubuntu Store, but i can't install
them, the Ubuntu Store results

Prepared update not found: /var/lib/PackageKit/prepared-update

If i run

# sudo apt-get update && sudo apt-get dist-upgrade

I get this (sorry german only):

Die folgenden Pakete sind zurückgehalten worden:
  chromium-codecs-ffmpeg-extra evince evince-common fonts-opensymbol
  gir1.2-pango-1.0 isc-dhcp-client isc-dhcp-common libevdocument3-4
  libevview3-3 libmbim-glib4 libmbim-proxy libmm-glib0 libpango-1.0-0
  libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libqmi-glib5
  libqmi-proxy libreoffice-base-core libreoffice-calc libreoffice-common
  libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk3
  libreoffice-help-common libreoffice-help-de libreoffice-help-en-us
  libreoffice-impress libreoffice-l10n-de libreoffice-math
  libreoffice-ogltrans libreoffice-pdfimport libreoffice-style-breeze
  libreoffice-style-colibre libreoffice-style-elementary
  libreoffice-style-yaru libreoffice-writer libsasl2-2 libsasl2-modules
  libsasl2-modules-db libsasl2-modules-gssapi-mit libsnmp-base libsnmp40
  libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3
  libuno-salhelpergcc3-3 modemmanager python3-macaroonbakery
  python3-software-properties python3-uno software-properties-common
  software-properties-gtk uno-libs-private ure

and yes, indeed, this file /var/lib/PackageKit/prepared-update really
don't exists but why?

I have also tried to stop the gnome-software and restart, in this case
the Ubuntu Store fetch the data new, but this also do not help - the
same updates come up but i can't install them.

https://abload.de/img/bildschirmfotovom20237pdzo.png

@Julian Andres Klode (juliank):

ich habe absichtlich dich hier hinzugefügt, weil ich weiß, dass du
deutsch sprichst ;-)

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

-- 
Ubuntu 22.04.2 Update fails
https://bugs.launchpad.net/bugs/2008907
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to the bug report.

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

[Desktop-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps

Want to mention that the issue is not present with glib2.0 2.75.3-3 if
fcitx5 is used instead of ibus. :/

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

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

Title:
  glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps

Status in glib2.0 package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New

Bug description:
  While preparing the gnome-settings-daemon 44 Beta update for Ubuntu
  23.04, I noticed that I could no longer enter text in the address bars
  for the Chromium or Firefox snaps.

  Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/commit/27bc0889c so that we could continue with the update.
  See https://salsa.debian.org/gnome-team/gnome-settings-
  daemon/-/commit/baeeed93

  Before I did that, I tested disabling our patches but it didn't make a
  difference.

  I was unable to reproduce the issue on Debian Testing but there may
  have been differences in how snap was configured there.

  I'm filing this bug since ideally we would not be diverging from
  upstream here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions


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

[Desktop-packages] [Bug 2008907] Re: Ubuntu 22.04.2 Update fails

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

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

Title:
  Ubuntu 22.04.2 Update fails

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I have currently some updates on the Ubuntu Store, but i can't install
  them, the Ubuntu Store results

  Prepared update not found: /var/lib/PackageKit/prepared-update

  If i run

  # sudo apt-get update && sudo apt-get dist-upgrade

  I get this (sorry german only):

  Die folgenden Pakete sind zurückgehalten worden:
    chromium-codecs-ffmpeg-extra evince evince-common fonts-opensymbol
    gir1.2-pango-1.0 isc-dhcp-client isc-dhcp-common libevdocument3-4
    libevview3-3 libmbim-glib4 libmbim-proxy libmm-glib0 libpango-1.0-0
    libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libqmi-glib5
    libqmi-proxy libreoffice-base-core libreoffice-calc libreoffice-common
    libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk3
    libreoffice-help-common libreoffice-help-de libreoffice-help-en-us
    libreoffice-impress libreoffice-l10n-de libreoffice-math
    libreoffice-ogltrans libreoffice-pdfimport libreoffice-style-breeze
    libreoffice-style-colibre libreoffice-style-elementary
    libreoffice-style-yaru libreoffice-writer libsasl2-2 libsasl2-modules
    libsasl2-modules-db libsasl2-modules-gssapi-mit libsnmp-base libsnmp40
    libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3
    libuno-salhelpergcc3-3 modemmanager python3-macaroonbakery
    python3-software-properties python3-uno software-properties-common
    software-properties-gtk uno-libs-private ure

  and yes, indeed, this file /var/lib/PackageKit/prepared-update really
  don't exists but why?

  I have also tried to stop the gnome-software and restart, in this case
  the Ubuntu Store fetch the data new, but this also do not help - the
  same updates come up but i can't install them.

  https://abload.de/img/bildschirmfotovom20237pdzo.png

  @Julian Andres Klode (juliank):

  ich habe absichtlich dich hier hinzugefügt, weil ich weiß, dass du
  deutsch sprichst ;-)

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


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

[Desktop-packages] [Bug 2008907] [NEW] Ubuntu 22.04.2 Update fails

You have been subscribed to a public bug:

I have currently some updates on the Ubuntu Store, but i can't install
them, the Ubuntu Store results

Prepared update not found: /var/lib/PackageKit/prepared-update

If i run

# sudo apt-get update && sudo apt-get dist-upgrade

I get this (sorry german only):

Die folgenden Pakete sind zurückgehalten worden:
  chromium-codecs-ffmpeg-extra evince evince-common fonts-opensymbol
  gir1.2-pango-1.0 isc-dhcp-client isc-dhcp-common libevdocument3-4
  libevview3-3 libmbim-glib4 libmbim-proxy libmm-glib0 libpango-1.0-0
  libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 libqmi-glib5
  libqmi-proxy libreoffice-base-core libreoffice-calc libreoffice-common
  libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk3
  libreoffice-help-common libreoffice-help-de libreoffice-help-en-us
  libreoffice-impress libreoffice-l10n-de libreoffice-math
  libreoffice-ogltrans libreoffice-pdfimport libreoffice-style-breeze
  libreoffice-style-colibre libreoffice-style-elementary
  libreoffice-style-yaru libreoffice-writer libsasl2-2 libsasl2-modules
  libsasl2-modules-db libsasl2-modules-gssapi-mit libsnmp-base libsnmp40
  libuno-cppu3 libuno-cppuhelpergcc3-3 libuno-purpenvhelpergcc3-3 libuno-sal3
  libuno-salhelpergcc3-3 modemmanager python3-macaroonbakery
  python3-software-properties python3-uno software-properties-common
  software-properties-gtk uno-libs-private ure

and yes, indeed, this file /var/lib/PackageKit/prepared-update really
don't exists but why?

I have also tried to stop the gnome-software and restart, in this case
the Ubuntu Store fetch the data new, but this also do not help - the
same updates come up but i can't install them.

@Julian Andres Klode (juliank):

ich habe absichtlich dich hier hinzugefügt, weil ich weiß, dass du
deutsch sprichst ;-)

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

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

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

[Desktop-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps

With glib2.0 2.75.3-3 installed and when starting the Firefox snap from
terminal I see these warning messages:

[Parent 3792, Main Thread] WARNING: Unable to connect to ibus: Could not
connect: Permission denied: 'glib warning', file
/build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167

(firefox:3792): IBUS-WARNING **: 15:23:11.814: Unable to connect to
ibus: Could not connect: Permission denied

FTR the issue is present on both wayland and x11.

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

Title:
  glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  While preparing the gnome-settings-daemon 44 Beta update for Ubuntu
  23.04, I noticed that I could no longer enter text in the address bars
  for the Chromium or Firefox snaps.

  Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/commit/27bc0889c so that we could continue with the update.
  See https://salsa.debian.org/gnome-team/gnome-settings-
  daemon/-/commit/baeeed93

  Before I did that, I tested disabling our patches but it didn't make a
  difference.

  I was unable to reproduce the issue on Debian Testing but there may
  have been differences in how snap was configured there.

  I'm filing this bug since ideally we would not be diverging from
  upstream here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions


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

[Desktop-packages] [Bug 1834378] Re: two-finger scrolling "jumps" unpredictably

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

** Changed in: xserver-xorg-input-synaptics (Ubuntu)
   Status: New => Confirmed

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

Title:
  two-finger scrolling "jumps" unpredictably

Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  When attempting 2-finger scrolling, it often happens that the document
  / webpage will scroll down by more than a full screen height at the
  instant I first lay fingers on the touchpad. This happens across
  multiple apps (text editors, web browsers).

  Note: the system (Dell Inspiron 7380) came pre-installed with Windows;
  I erased the HD and installed Xubuntu 18.04 in its place.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-input-synaptics 1.9.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18
  Uname: Linux 4.15.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: XFCE
  Date: Wed Jun 26 14:23:35 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  InstallationDate: Installed on 2018-12-23 (185 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  LightdmDisplayLog: (II) AIGLX: Suspending AIGLX clients for VT switch
  Lsusb:
   Bus 002 Device 002: ID 706b:6b31  
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:6715 Microdia 
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7380
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-52-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0GW3KR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd08/23/2018:svnDellInc.:pnInspiron7380:pvr:rvnDellInc.:rn0GW3KR:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7380
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1834378/+subscriptions


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

[Desktop-packages] [Bug 2008905] [NEW] Two-finger scrolling on touchpad not working as expected

2023-03-01 Thread Andrew Constantinescu

Public bug reported:

My touchpad works normally except for two-finger scrolling, where it
frequently jumps/skips instead of scrolling smoothly. I was originally
using libinput drivers and switched to synaptics drivers, but it did not
resolve the issue. I am hoping to get some help identifying the root
cause

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
NonfreeKernelModules: falcon_lsm_serviceable falcon_nf_netcontain falcon_kal 
falcon_lsm_pinned_14713
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar  1 09:29:29 2023
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
InstallationDate: Installed on 2022-11-07 (113 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: Dell Inc. Precision 5560
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic 
root=UUID=c80e66ed-7a8a-4922-9819-2e31d3312e40 ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-input-synaptics
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/16/2022
dmi.bios.release: 1.16
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.16.0
dmi.board.name: 0G06MM
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd11/16/2022:br1.16:svnDellInc.:pnPrecision5560:pvr:rvnDellInc.:rn0G06MM:rvrA00:cvnDellInc.:ct10:cvr:sku0A62:
dmi.product.family: Precision
dmi.product.name: Precision 5560
dmi.product.sku: 0A62
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xserver-xorg-input-synaptics (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Two-finger scrolling on touchpad not working as expected

Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  My touchpad works normally except for two-finger scrolling, where it
  frequently jumps/skips instead of scrolling smoothly. I was originally
  using libinput drivers and switched to synaptics drivers, but it did
  not resolve the issue. I am hoping to get some help identifying the
  root cause

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  NonfreeKernelModules: falcon_lsm_serviceable falcon_nf_netcontain falcon_kal 
falcon_lsm_pinned_14713
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  1 09:29:29 2023
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  InstallationDate: Installed on 2022-11-07 (113 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Dell Inc. Precision 5560
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic 
root=UUID=c80e66ed-7a8a-4922-9819-2e31d3312e40 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/16/2022
  dmi.bios.release: 1.16
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.0
  dmi.board.name: 0G06MM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd11/16/2022:br1.16:svnDellInc.:pnPrecision5560:pvr:rvnDellInc.:rn0G06MM:rvrA00:cvnDellInc.:ct10:cvr:sku0A62:
  dmi.product.family: Precision
  dmi.product.name: Precision 5560
  dmi.product.sku: 0A62
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.6

[Desktop-packages] [Bug 1985057] Re: Camera output freeze when using pipewiresrc

2023-03-01 Thread Bin Li

The below two patches in Description could cause the screencast
regression, so they were reverted, if we want add them again we need two
gstreamer's patches in comment #51.

  * d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch
d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch
- Camera output freeze when using pipewiresrc (LP: #1985057)

I also added another pipewire patch, d/p/0003-gst-copy-buffer-memory-in-
dequeue_buffer-using-gst_m.patch from comment #51 .

** Also affects: gst-plugins-base1.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gstreamer1.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Camera output freeze when using pipewiresrc

Status in OEM Priority Project:
  New
Status in gst-plugins-base1.0 package in Ubuntu:
  New
Status in gstreamer1.0 package in Ubuntu:
  New
Status in pipewire package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 source package in Jammy:
  New
Status in gstreamer1.0 source package in Jammy:
  New
Status in pipewire source package in Jammy:
  Triaged

Bug description:
  [Impact]
  On Dell platform with Microdia Integrated webcam, the Cheese preview is stuck 
on jammy. The gst-launch-1.0 command suggested by gst-device-monitor-1.0 can 
reproduce it too.

  [Test Plan]
  1. Install Jammy on the hardware issue reported, and hardware didn't report 
the issue to avoid the regression
     hardware list:
     a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD
     b. 0c45:6747 Microdia Integrated_Webcam_HD
     c. 0c45:6a14 Microdia Integrated_Webcam_HD
     d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M
     e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera
     f. 0408:545a Quanta Computer, Inc. HP 5MP Camera
     g. 0408:5483 Quanta Computer, Inc. HP HD Camera
     h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4)
     i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a)
     j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD
  2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2)
  3. $ sudo reboot
  4. Check if gst-launch-1.0 work
     a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest 
gst-launch-1.0 command
     b. $ gst-launch-1.0 pipewiresrc path= !  ! decodebin ! 
videoconvert ! glimagesink
     c. Check if the result ok
  5. Check the screencast function by pressing 'prt sc'
     a. the screenshot of all screen/selected region should work good
     b. the screenrecord of all screen/selected region should work good
  6. Check that video recording in gnome-shell works
     - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, 
verify that there is a new entry in ~/Video
  7. Check that screen sharing is working
     - go to settings, screen sharing and enable the feature
     - try to connect using rdp/vnc from another client

  do those steps under wayland and unset X

  [Where problems could occur]
  The patches try to dequeue the shared buffer, instead of pool buffer to 
prevent the pool buffer being corrupted. it might cause some camera preview 
failed if shared buffer is corrupted.
  It is in upstream from 0.3.52 to 0.3.56, and there is no regression found,
  so the risk is low.

  [Other Info]
  Upstream commits:
  
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92
  
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f

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


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

[Desktop-packages] [Bug 1987631] Re: Screencast only records one second

2023-03-01 Thread Bin Li

For comment #38, currently it sounds good, if we upgrade the gstreamer
to 1.20.4, we need backport below patch.

commit d7b443197bcc0789305d6a8722bca1fdd182070b
Author: Sebastian Keller 
Date:   Thu Oct 6 00:20:16 2022 +0200

screencast: Don't force buffer copies on recent gstreamer versions

Gstreamer 1.20.4 includes a fix in the videoconvert element that makes
it no longer necessary to always copy buffers in pipewiresrc to have
smooth recordings. This change now skips those otherwise unnecessary
copies when using a new enough videoconvert.

Related: 
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/2928
Part-of: 

diff --git a/js/dbusServices/screencast/screencastService.js 
b/js/dbusServices/screencast/screencastService.js
index 5ff5aff52..bb5387428 100644
--- a/js/dbusServices/screencast/screencastService.js
+++ b/js/dbusServices/screencast/screencastService.js
@@ -231,7 +231,8 @@ var Recorder = class {
 _ensurePipeline(nodeId) {
 const framerate = this._framerate;
 const needsCopy =
-Gst.Registry.get().check_feature_version('pipewiresrc', 0, 3, 57);
+Gst.Registry.get().check_feature_version('pipewiresrc', 0, 3, 57) 
&&
+!Gst.Registry.get().check_feature_version('videoconvert', 1, 20, 
4);

** Changed in: oem-priority
   Status: In Progress => Fix Released

** Changed in: oem-priority
 Assignee: Bin Li (binli) => (unassigned)

** No longer affects: gst-plugins-base1.0 (Ubuntu)

** No longer affects: gst-plugins-base1.0 (Ubuntu Jammy)

** No longer affects: gstreamer1.0 (Ubuntu Jammy)

** No longer affects: gstreamer1.0 (Ubuntu)

** Changed in: pipewire (Ubuntu Jammy)
 Assignee: Bin Li (binli) => (unassigned)

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

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

Title:
  Screencast only records one second

Status in GNOME Shell:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in pipewire package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Jammy:
  Fix Released
Status in pipewire source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  When recording a screencast with gnome on kinetic the resulting video will 
play for one second and then freeze. It looks like the same bug was discussed 
upstream at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585

  This issue is caused by the new two patches in 0.3.48-1ubuntu2 which is fixed 
the Cheese preview stuck issue on jammy
* d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch
  d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch
  - Camera output freeze when using pipewiresrc (LP: #1985057)

  Here is a comment from 
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057/comments/51 .
  ===
  So that's a regression of one of the cherrypicked commits, details are in 
https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d32c03488

  the issue is fixed in Kinetic through a combination of the shell fix
  and a new pipewire.

  In 22.04 the shell issue is fixed in the recent 42.5 update but we will need 
to cherrypick 
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 in pipewire 
to be working.
  ===

  [Test Plan]
  1. Install Jammy on the hardware issue reported, and hardware didn't report 
the issue to avoid the regression
 hardware list:
 a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD
 b. 0c45:6747 Microdia Integrated_Webcam_HD
 c. 0c45:6a14 Microdia Integrated_Webcam_HD
 d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M
 e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera
 f. 0408:545a Quanta Computer, Inc. HP 5MP Camera
 g. 0408:5483 Quanta Computer, Inc. HP HD Camera
 h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4)
 i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a)
 j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD
  2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2)
  3. $ sudo reboot
  4. Check if gst-launch-1.0 work
 a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest 
gst-launch-1.0 command
 b. $ gst-launch-1.0 pipewiresrc path= !  ! decodebin ! 
videoconvert ! glimagesink
 c. Check if the result ok
  5. Check the screencast function by pressing 'prt sc'
 a. the screenshot of all screen/selected region should work good
 b. the screenrecord of all screen/selected region should work good
  6. Check that video recording in gnome-shell works
 - use Ctrl+Shift+Alt+R to start a recording, stop it from the

[Desktop-packages] [Bug 1987631] Re: Screencast only records one second

2023-03-01 Thread Bin Li

@seb128,

I went through this issue again.

On 22.04.2, it works fine. With pipewire 0.3.48-1ubuntu3, because it
revert the patches for Bug #1985057 , so currently we don't need to do
SRU for this issue.

To make this issue clear, let's focus on the SRU process on Bug
#1985057.

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

Title:
  Screencast only records one second

Status in GNOME Shell:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in pipewire package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Jammy:
  Fix Released
Status in gst-plugins-base1.0 source package in Jammy:
  In Progress
Status in gstreamer1.0 source package in Jammy:
  In Progress
Status in pipewire source package in Jammy:
  In Progress

Bug description:
  [Impact]
  When recording a screencast with gnome on kinetic the resulting video will 
play for one second and then freeze. It looks like the same bug was discussed 
upstream at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585

  This issue is caused by the new two patches in 0.3.48-1ubuntu2 which is fixed 
the Cheese preview stuck issue on jammy
* d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch
  d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch
  - Camera output freeze when using pipewiresrc (LP: #1985057)

  Here is a comment from 
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057/comments/51 .
  ===
  So that's a regression of one of the cherrypicked commits, details are in 
https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d32c03488

  the issue is fixed in Kinetic through a combination of the shell fix
  and a new pipewire.

  In 22.04 the shell issue is fixed in the recent 42.5 update but we will need 
to cherrypick 
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 in pipewire 
to be working.
  ===

  [Test Plan]
  1. Install Jammy on the hardware issue reported, and hardware didn't report 
the issue to avoid the regression
 hardware list:
 a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD
 b. 0c45:6747 Microdia Integrated_Webcam_HD
 c. 0c45:6a14 Microdia Integrated_Webcam_HD
 d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M
 e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera
 f. 0408:545a Quanta Computer, Inc. HP 5MP Camera
 g. 0408:5483 Quanta Computer, Inc. HP HD Camera
 h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4)
 i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a)
 j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD
  2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2)
  3. $ sudo reboot
  4. Check if gst-launch-1.0 work
 a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest 
gst-launch-1.0 command
 b. $ gst-launch-1.0 pipewiresrc path= !  ! decodebin ! 
videoconvert ! glimagesink
 c. Check if the result ok
  5. Check the screencast function by pressing 'prt sc'
 a. the screenshot of all screen/selected region should work good
 b. the screenrecord of all screen/selected region should work good
  6. Check that video recording in gnome-shell works
 - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, 
verify that there is a new entry in ~/Video
  7. Check that screen sharing is working
 - go to settings, screen sharing and enable the feature
 - try to connect using rdp/vnc from another client

  do those steps under wayland and unset X

  [Where problems could occur]
  The patches try to dequeue the shared buffer, instead of pool buffer to 
prevent the pool buffer being corrupted. it might cause some camera preview 
failed if shared buffer is corrupted.
  It is from upstream and there is no regression found, so the risk is low.

  [Other Info]
  Upstream commits for pipewire:
  
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92
  
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f
  
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525c1ac946a915599c6bee813e88e8cee12
  Upstream commits for gstreamer:
  
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/3b900e1fa4fd888012dc005fa26ae2532a89b7a7

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


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

[Desktop-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps

** Summary changed:

- xsettings ibus commit broke text input for Firefox & Chromium snaps
+ glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps

** No longer affects: gnome-settings-daemon (Ubuntu)

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => High

** Tags added: rls-ll-incoming

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

Title:
  glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  While preparing the gnome-settings-daemon 44 Beta update for Ubuntu
  23.04, I noticed that I could no longer enter text in the address bars
  for the Chromium or Firefox snaps.

  Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/commit/27bc0889c so that we could continue with the update.
  See https://salsa.debian.org/gnome-team/gnome-settings-
  daemon/-/commit/baeeed93

  Before I did that, I tested disabling our patches but it didn't make a
  difference.

  I was unable to reproduce the issue on Debian Testing but there may
  have been differences in how snap was configured there.

  I'm filing this bug since ideally we would not be diverging from
  upstream here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions


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

[Desktop-packages] [Bug 2008279] Re: xsettings ibus commit broke text input for Firefox & Chromium snaps

Hmm.. Suddenly I could no longer type in the address bar of the Firefox
snap. But I think the culprit is glib2.0 2.75.3-3, which I installed
from -proposed yesterday in order to test build g-c-c from
ubuntu/master. After having downgraded glib2.0 to 2.74.5-1 the issue is
no longer present.

** Also affects: glib2.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: block-proposed update-excuse

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

Title:
  xsettings ibus commit broke text input for Firefox & Chromium snaps

Status in glib2.0 package in Ubuntu:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  While preparing the gnome-settings-daemon 44 Beta update for Ubuntu
  23.04, I noticed that I could no longer enter text in the address bars
  for the Chromium or Firefox snaps.

  Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/-/commit/27bc0889c so that we could continue with the update.
  See https://salsa.debian.org/gnome-team/gnome-settings-
  daemon/-/commit/baeeed93

  Before I did that, I tested disabling our patches but it didn't make a
  difference.

  I was unable to reproduce the issue on Debian Testing but there may
  have been differences in how snap was configured there.

  I'm filing this bug since ideally we would not be diverging from
  upstream here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions


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

[Desktop-packages] [Bug 2008892] Re: "Gave up waiting for root file system device" after fresh installation of Ubuntu 22.04

2023-03-01 Thread Floris Luiten

** Description changed:

  After running the 22.04 installer, my laptop would restart and after
  seeing the initial loading screen I'm dropped to a busybox shell. It
  makes no difference what boot option I use from my UEFI or installing
  with or without disk encrpytion.
  
  The installer finds my disk without problems, but afer rebooting the
  Ubuntu screen hangs for around a minute before dropping me into a
  busybox shell.
  
  In this shell I do the following:
  
  ```
  # ls /dev/mapper
  control   isw_behfgagcfc_ASUS_OS
  
  # kpartx -av /dev/mapper/isw_behfgagcfc_ASUS_OS
  add map isw_behfgagcfc_ASUS_OS1 (253:1): 0 1048576 linear 253:0 2048
  add map isw_behfgagcfc_ASUS_OS2 (253:2): 0 3500032 linear 253:0 1050624
  add map isw_behfgagcfc_ASUS_OS3 (253:3): 0 495579136 linear 253:0 4550656
  
  # cryptsetup luksOpen /dev/mapper/isw_behfgagcfc_ASUS_OS3 WHYEVER
  Enter passphrase for /dev/mapper/isw_behfgagcfc_ASUS_OS3: ***
  
  # exit
  ```
  
  After which the Ubuntu loading screen re-appears and I have to enter the
  disk decrypt key again. Then my system boots fine, but I think it's a
  bug to have these commands to manually every time.
  
  If I install without disk-encryption, I still have to run "kpartx -av
  /dev/mapper/isw_behfgagfc_ASUS_OS" in the busybox shell before I'm able
  to continue.
  
  Attached the log from apport inside the finally booted Ubuntu
  installation with disk-encryption on.
+ 
+ PS: The same error occurs when upgrading from from 21.10 to 22.04.

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

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

Title:
  "Gave up waiting for root file system device" after fresh installation
  of Ubuntu 22.04

Status in plymouth package in Ubuntu:
  New

Bug description:
  After running the 22.04 installer, my laptop would restart and after
  seeing the initial loading screen I'm dropped to a busybox shell. It
  makes no difference what boot option I use from my UEFI or installing
  with or without disk encrpytion.

  The installer finds my disk without problems, but afer rebooting the
  Ubuntu screen hangs for around a minute before dropping me into a
  busybox shell.

  In this shell I do the following:

  ```
  # ls /dev/mapper
  control   isw_behfgagcfc_ASUS_OS

  # kpartx -av /dev/mapper/isw_behfgagcfc_ASUS_OS
  add map isw_behfgagcfc_ASUS_OS1 (253:1): 0 1048576 linear 253:0 2048
  add map isw_behfgagcfc_ASUS_OS2 (253:2): 0 3500032 linear 253:0 1050624
  add map isw_behfgagcfc_ASUS_OS3 (253:3): 0 495579136 linear 253:0 4550656

  # cryptsetup luksOpen /dev/mapper/isw_behfgagcfc_ASUS_OS3 WHYEVER
  Enter passphrase for /dev/mapper/isw_behfgagcfc_ASUS_OS3: ***

  # exit
  ```

  After which the Ubuntu loading screen re-appears and I have to enter
  the disk decrypt key again. Then my system boots fine, but I think
  it's a bug to have these commands to manually every time.

  If I install without disk-encryption, I still have to run "kpartx -av
  /dev/mapper/isw_behfgagfc_ASUS_OS" in the busybox shell before I'm
  able to continue.

  Attached the log from apport inside the finally booted Ubuntu
  installation with disk-encryption on.

  PS: The same error occurs when upgrading from from 21.10 to 22.04.

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


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

[Desktop-packages] [Bug 2008892] [NEW] "Gave up waiting for root file system device" after fresh installation of Ubuntu 22.04

You have been subscribed to a public bug:

After running the 22.04 installer, my laptop would restart and after
seeing the initial loading screen I'm dropped to a busybox shell. It
makes no difference what boot option I use from my UEFI or installing
with or without disk encrpytion.

The installer finds my disk without problems, but afer rebooting the
Ubuntu screen hangs for around a minute before dropping me into a
busybox shell.

In this shell I do the following:

```
# ls /dev/mapper
control   isw_behfgagcfc_ASUS_OS

# kpartx -av /dev/mapper/isw_behfgagcfc_ASUS_OS
add map isw_behfgagcfc_ASUS_OS1 (253:1): 0 1048576 linear 253:0 2048
add map isw_behfgagcfc_ASUS_OS2 (253:2): 0 3500032 linear 253:0 1050624
add map isw_behfgagcfc_ASUS_OS3 (253:3): 0 495579136 linear 253:0 4550656

# cryptsetup luksOpen /dev/mapper/isw_behfgagcfc_ASUS_OS3 WHYEVER
Enter passphrase for /dev/mapper/isw_behfgagcfc_ASUS_OS3: ***

# exit
```

After which the Ubuntu loading screen re-appears and I have to enter the
disk decrypt key again. Then my system boots fine, but I think it's a
bug to have these commands to manually every time.

If I install without disk-encryption, I still have to run "kpartx -av
/dev/mapper/isw_behfgagfc_ASUS_OS" in the busybox shell before I'm able
to continue.

Attached the log from apport inside the finally booted Ubuntu
installation with disk-encryption on.

PS: The same error occurs when upgrading from from 21.10 to 22.04.

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


** Tags: bot-comment
-- 
"Gave up waiting for root file system device" after fresh installation of 
Ubuntu 22.04
https://bugs.launchpad.net/bugs/2008892
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to plymouth 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 2008791] Re: Disk properties in Gnome Files (Nautilus) shows a black chart for disk usage on Ubuntu 22.04

2023-03-01 Thread Paul White

** Package changed: texinfo (Ubuntu) => nautilus (Ubuntu)

** Tags added: jammy

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

Title:
  Disk properties in Gnome Files (Nautilus) shows a black chart for disk
  usage on Ubuntu 22.04

Status in nautilus package in Ubuntu:
  New

Bug description:
  if I open the Properties window for a disk (not a plain folder) the
  pie chart intended to show disk usage is all black (screenshot
  attached). On previous versions it used to have different colors for
  "used" and "free" space.

  Testing a clean install on a virtual machine gives the same results so
  it's not an issue related to the upgrade process. I guess it's related
  to the theming features added to Ubuntu 22.04.

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


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

[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage

2023-03-01 Thread Andrew

Noting 4.0.1 stable has now been released, perhaps we could have an
update to fix this issue now (if not in 22.10, perhaps in 23.04?).

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

Title:
  transmission-daemon high RAM usage

Status in transmission package in Ubuntu:
  Confirmed

Bug description:
  Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign
  on a Raspberry Pi 4.

  It "eats" RAM and the RAM usage grows each hour until it crashes the
  system.

  I sideloaded transmission-daemon and its dependancies from debian 11
  (arm64) locked the packages so apt won't update them and, ever since,
  this issue hasn't happened.

  
  Description:Ubuntu 22.04 LTS
  Release:22.04

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


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

[Desktop-packages] [Bug 2008853] Re: Notifications block the view. Small size tweak needed to fix the bug

2023-03-01 Thread Paul White

I've seen this too.

Issue needs to be reported upstream to https://gitlab.gnome.org
as not an Ubuntu issue but a GNOME bug that probably affects
all distributions.

** Tags added: jammy

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

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

Title:
  Notifications block the view. Small size tweak needed to fix the bug

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Various notifications are shown in Nautilus, when files are deleted
  etc. These notification boxes (as shown in the attached screenshot)
  are a UI/UX nightmare, since each time such an action is performed,
  the box blocks part of the screen, forcing the User to either pause
  until the box disappears or forcing the User to click the close button
  of the message. It is a poor UI/UX design, to block the view with such
  a message. A simple temporary fix for this UI/UX bug, is to simply
  reduce the height of the message box (as shown in the bottom of the
  screenshot). I have requested for this earlier too. Please implement
  it at least this time, and please release the fix for Ubuntu 20.04
  too.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: nautilus 1:3.36.3-0ubuntu1.20.04.2
  ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  1 10:11:59 2023
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'205'
   b'org.gnome.nautilus.window-state' b'initial-size' b'(899, 826)'
   b'org.gnome.nautilus.preferences' b'click-policy' b"'single'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
  InstallationDate: Installed on 2023-01-16 (43 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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


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

[Desktop-packages] [Bug 2008433] Re: Request to enable WidevineCDM checking on ARM64

2023-03-01 Thread Nathan Teodosio

Can you please test the snap from the edge channel (snap refresh
--channel edge chromium) and report whether it solves the issue?

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

Title:
  Request to enable WidevineCDM checking on ARM64

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  If possible, could you please include a patch to enable widevinecdm
  checking on ARM64 linux? currently BUNDLE_WIDEVINE_CDM does not get
  set for arm64 linux (but does on amd64 linux) so chromium does not
  even check for widevine even if we have it available and placed in the
  directory manually.

  I am currently using the attached patch of my making when testing
  locally to correct this issue.

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


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

[Desktop-packages] [Bug 1930769] Re: When enabled, Firefox AppArmor profile prevents U2F devices from working

2023-03-01 Thread Michael T

Hi Don Rico!

This is actually fixed for me on 22.04

22.04 moved Firefox into snap, and snap has a whitelist of permitted U2F
tokens:
https://github.com/snapcore/snapd/blob/2.58.3/interfaces/builtin/u2f_devices.go#L43

That's a list of USB VID and PID, which you can find for your device
using the lsusb command. If your U2F device isn't on that list, you can
raise an MR like https://github.com/snapcore/snapd/pull/10642 to get it
enabled.

Some might debate the wisdom of the OS vendor maintaining a list of
blessed devices - but it is what it is.

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

Title:
  When enabled, Firefox AppArmor profile prevents U2F devices from
  working

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Summary:

  If you enable the apparmor profile that comes in Ubuntu's Firefox
  package, it prevents USB U2F tokens from being used.

  To reproduce:

  1. Obtain a USB FIDO/U2F token - such as a Yubikey; and a clean
  install of Ubuntu 20.04 with Firefox installed, but the AppArmor
  profile for firefox disabled (As is the default).

  2. Confirm the correct function of your U2F token - such as at
  https://demo.yubico.com/webauthn-technical

  3. Enable the AppArmor profile with the following command, then
  restart firefox.

   sudo aa-enforce /etc/apparmor.d/usr.bin.firefox

  4. Repeat your test of your U2F token. You will find Firefox is unable
  to access your U2F token. Any accounts you need U2F to log into are
  now inaccessible.

  5. Disabling the apparmor profile and restarting firefox will make U2F
  work again.

  To work around:

  Edit /etc/apparmor.d/usr.bin.firefox and replace these lines:

# Doesn't seem to be required, but noisy. Maybe allow 'r' for 'b*' if 
needed.
# Possibly move to an abstraction if anything else needs it.
deny /run/udev/data/** r,

  Instead allowing access to udev data, and to hidraw devices:

/run/udev/data/** r,
/dev/hidraw[0-9] rw,

  I haven't checked the security implications of this change; some might
  feel it grants overly broad access. Chromium, which in 20.04 is
  delivered as a snap, includes udev rules (70-snap.chromium.rules)
  which I suspect grant access in a device-id-whitelisted way.

  This is me resubmitting #1930768 this time with all the info attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 88.0.1+build1-0ubuntu0.20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-53-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mtandy 1757 F pulseaudio
   /dev/snd/controlC1:  mtandy 1757 F pulseaudio
  BuildID: 20210504152106
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  3 23:34:55 2021
  ForcedLayersAccel: False
  IncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2021-05-31 (3 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  IpRoute:
   default via 192.168.0.1 dev enp3s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp3s0 scope link metric 1000 
   192.168.0.0/24 dev enp3s0 proto kernel scope link src 192.168.0.2 metric 100
  MostRecentCrashID: bp-4122b123-9c74-4baf-b817-c8a771171216
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:352
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=88.0.1/20210504152106 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2014
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2202
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  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.:bvr2202:bd07/11/2014:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-K:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  mtime.conffile..etc.apparmor.d.usr.bin.firefox: 2021-06-03T23:25:44.143815

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


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

[Desktop-packages] [Bug 1930768] Re: When enabled, Firefox AppArmor profile prevents U2F devices from working

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

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

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

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

Title:
  When enabled, Firefox AppArmor profile prevents U2F devices from
  working

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Summary:

  If you enable the apparmor profile that comes in Ubuntu's Firefox
  package, it prevents USB U2F tokens from being used.

  To reproduce:

  1. Obtain a USB FIDO/U2F token - such as a Yubikey; and a clean
  install of Ubuntu 20.04 with Firefox installed, but the AppArmor
  profile for firefox disabled (As is the default).

  2. Confirm the correct function of your U2F token - such as at
  https://demo.yubico.com/webauthn-technical

  3. Enable the AppArmor profile with the following command, then
  restart firefox.

   sudo aa-enforce /etc/apparmor.d/usr.bin.firefox

  4. Repeat your test of your U2F token. You will find Firefox is unable
  to access your U2F token. Any accounts you need U2F to log into are
  now inaccessible.

  5. Disabling the apparmor profile and restarting firefox will make U2F
  work again.

  To work around:

  Edit /etc/apparmor.d/usr.bin.firefox and replace these lines:

# Doesn't seem to be required, but noisy. Maybe allow 'r' for 'b*' if 
needed.
# Possibly move to an abstraction if anything else needs it.
deny /run/udev/data/** r,

  Instead allowing access to udev data, and to hidraw devices:

/run/udev/data/** r,
/dev/hidraw[0-9] rw,

  I haven't checked the security implications of this change; some might
  feel it grants overly broad access. Chromium, which in 20.04 is
  delivered as a snap, includes udev rules (70-snap.chromium.rules)
  which I suspect grant access in a device-id-whitelisted way.

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


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

[Desktop-packages] [Bug 1867668] Re: Visual artifacts when using the old 'intel' Xorg driver