from:"Robert"

** Tags added: rls-ll-incoming

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

Title:
  Dock displaying over window after resuming from blank screen

Status in Dash to dock:
  Unknown
Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in gnome-desktop package in Fedora:
  Confirmed

Bug description:
  I have Blank Screen set to happen after 2 minutes of inactivity.

  When resuming from a Blank Screen (by moving the mouse or touching the
  keyboard), the Dock is displayed over the top of the current program.

  To get it back to normal I need to click "Restore Down" on the current
  programs window and then "Maximize" so that the Dock no longer
  overlaps it.

  (Note: I have Auto-hide dock turned off.)

  This only happens sometimes. I can't reproduce the bug it every time.

  -

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  - Ubuntu 21.10

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  - Not sure (I guess the Dock is part of the Gnome interface?)

  3) What you expected to happen
  - Dock should not overlap the current program on resume from screen blank.

  4) What happened instead
  - The Dock overlaps the current program on resume from screen blank.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2022-02-18 (24 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: gnome-shell-extension-ubuntu-dock
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1
  Tags:  wayland-session impish
  Uname: Linux 5.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-02-18 (328 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  Tags: wayland-session third-party-packages kinetic
  Uname: Linux 5.19.0-28-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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


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

[Desktop-packages] [Bug 2012996] [NEW] Editing device name doesn't cancel when pressing escape

Public bug reported:

The device name in the Sharing or About panels can be changed by
clicking the icon to the right of the name (see screenshot). Pressing
escape doesn't cancel the edit and re-show this icon.

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


** Tags: rls-ll-incoming

** Attachment added: "Screenshot of device name widget"
   
https://bugs.launchpad.net/bugs/2012996/+attachment/5658049/+files/Screenshot%20from%202023-03-28%2014-46-06.png

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

Title:
  Editing device name doesn't cancel when pressing escape

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

Bug description:
  The device name in the Sharing or About panels can be changed by
  clicking the icon to the right of the name (see screenshot). Pressing
  escape doesn't cancel the edit and re-show this icon.

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


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

[Desktop-packages] [Bug 2012994] [NEW] Automatic Date & Time switch shows as insensitive when enabled

Public bug reported:

Go to Settings > Date & Time and toggle the "Automatic Date & Time"
switch. When enabled it shows as insensitive (i.e. grey instead of
orange). The "Automatic Time Zone" switch below behaves as expected.

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


** Tags: rls-ll-incoming

** Attachment added: "Screenshot showing automatic date & time enabled with 
insensitive switch"
   
https://bugs.launchpad.net/bugs/2012994/+attachment/5658048/+files/Screenshot%20from%202023-03-28%2014-41-08.png

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

Title:
  Automatic Date & Time switch shows as insensitive when enabled

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

Bug description:
  Go to Settings > Date & Time and toggle the "Automatic Date & Time"
  switch. When enabled it shows as insensitive (i.e. grey instead of
  orange). The "Automatic Time Zone" switch below behaves as expected.

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


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

[Desktop-packages] [Bug 2012991] Re: Insensitive items in system tray menus not visible

Changing the theme to dark makes the text visible.

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

Title:
  Insensitive items in system tray menus not visible

Status in gnome-shell-extension-appindicator package in Ubuntu:
  New

Bug description:
  If you use the multicast system tray menu the text on the items that
  are insensitive aren't visible. It appears they have the same colour
  as the background.

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


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

[Desktop-packages] [Bug 2012991] [NEW] Insensitive items in system tray menus not visible

Public bug reported:

If you use the multicast system tray menu the text on the items that are
insensitive aren't visible. It appears they have the same colour as the
background.

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


** Tags: rls-ll-incoming

** Attachment added: "Screenshot of multipass system tray menu"
   
https://bugs.launchpad.net/bugs/2012991/+attachment/5658046/+files/Screenshot%20from%202023-03-28%2014-11-35.png

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

Title:
  Insensitive items in system tray menus not visible

Status in gnome-shell-extension-appindicator package in Ubuntu:
  New

Bug description:
  If you use the multicast system tray menu the text on the items that
  are insensitive aren't visible. It appears they have the same colour
  as the background.

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


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

[Desktop-packages] [Bug 1998267] Re: glib not aware of snap confinement

2023-03-22 Thread Robert Ancell

** Changed in: glib2.0 (Ubuntu Kinetic)
   Status: New => Won't Fix

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

Title:
  glib not aware of snap confinement

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Jammy:
  New
Status in glib2.0 source package in Kinetic:
  Won't Fix
Status in glib2.0 source package in Lunar:
  Fix Released

Bug description:
  [ Impact]

  glib is not aware of snap confinement and this causes the internal
  logic to decide when to use portals to not work as designed. One
  important case is the gsettings backend, which should use a keyfile
  when confined rather than using dconf. When using a fully confined
  desktop this is required, as dconf is not suitable for sharing between
  snaps.

  This has been fixed in glib main:
  https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020

  [ Test Plan ]

  (requires a core snap running the updated glib).

  1. Install gnome-calculator snap:
  $ snap install gnome-calculator
  2. Disconnect gsettings interface:
  $ snap disconnect gnome-calculator:gsettings
  3. Run gnome-calculator
  4. Change mode from basic to advanced
  5. Close and re-open gnome-calculator

  Expected result:
  Mode change remembered on second run. gnome-calculator settings written to 
~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile

  Observed result:
  Mode change not remembered on second run, errors shown in console about 
accessing dconf:
  (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create 
file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied.  
dconf will not work properly.

  [ Where problems could occur ]

  - New bug introduced in glib causing a crash.
  - Security issue introduced in glib due to accessing snapctl.
  - Unexpected behaviour change when running snaps with updated glib.

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


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

[Desktop-packages] [Bug 1998267] Re: glib not aware of snap confinement

2023-03-22 Thread Robert Ancell

** Description changed:

  [ Impact]
  
  glib is not aware of snap confinement and this causes the internal logic
  to decide when to use portals to not work as designed. One important
  case is the gsettings backend, which should use a keyfile when confined
  rather than using dconf. When using a fully confined desktop this is
  required, as dconf is not suitable for sharing between snaps.
  
  This has been fixed in glib main:
  https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020
  
  [ Test Plan ]
+ 
+ (requires a core snap running the updated glib).
  
  1. Install gnome-calculator snap:
  $ snap install gnome-calculator
  2. Disconnect gsettings interface:
  $ snap disconnect gnome-calculator:gsettings
  3. Run gnome-calculator
  4. Change mode from basic to advanced
  5. Close and re-open gnome-calculator
  
  Expected result:
  Mode change remembered on second run. gnome-calculator settings written to 
~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile
  
  Observed result:
  Mode change not remembered on second run, errors shown in console about 
accessing dconf:
  (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create 
file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied.  
dconf will not work properly.
  
  [ Where problems could occur ]
  
  - New bug introduced in glib causing a crash.
  - Security issue introduced in glib due to accessing snapctl.
  - Unexpected behaviour change when running snaps with updated glib.

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

Title:
  glib not aware of snap confinement

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Jammy:
  New
Status in glib2.0 source package in Kinetic:
  New
Status in glib2.0 source package in Lunar:
  Fix Released

Bug description:
  [ Impact]

  glib is not aware of snap confinement and this causes the internal
  logic to decide when to use portals to not work as designed. One
  important case is the gsettings backend, which should use a keyfile
  when confined rather than using dconf. When using a fully confined
  desktop this is required, as dconf is not suitable for sharing between
  snaps.

  This has been fixed in glib main:
  https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020

  [ Test Plan ]

  (requires a core snap running the updated glib).

  1. Install gnome-calculator snap:
  $ snap install gnome-calculator
  2. Disconnect gsettings interface:
  $ snap disconnect gnome-calculator:gsettings
  3. Run gnome-calculator
  4. Change mode from basic to advanced
  5. Close and re-open gnome-calculator

  Expected result:
  Mode change remembered on second run. gnome-calculator settings written to 
~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile

  Observed result:
  Mode change not remembered on second run, errors shown in console about 
accessing dconf:
  (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create 
file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied.  
dconf will not work properly.

  [ Where problems could occur ]

  - New bug introduced in glib causing a crash.
  - Security issue introduced in glib due to accessing snapctl.
  - Unexpected behaviour change when running snaps with updated glib.

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


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

[Desktop-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

2023-03-13 Thread Robert Pearson

Will Ubuntu fix kernel 5.19.0-35 or just do another update with a
working kernel?

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

Title:
  HDMI Output sound has disappeared after Ubuntu update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After months using the HDMI output without problems, it has stopped working 
after a system update two days ago.
  HDMI output is not listed in the list of available output devices.
  Same computer works with this sound output perfectly when booting with 
Windows or an older installation of Ubuntu (18.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  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: Tue Feb 21 08:12:58 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-30 (296 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M01EWR120
  dmi.board.asset.tag: OEM Default string000
  dmi.board.name: OEM Default string000
  dmi.board.vendor: OEM Default string000
  dmi.board.version: OEM Default string000
  dmi.chassis.asset.tag: OEM Default string000
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Default string000
  dmi.chassis.version: OEM Default string000
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
  dmi.product.family: OEM Default string000
  dmi.product.name: CoreBox
  dmi.product.sku: OEM Default string000
  dmi.product.version: OEM Default string000
  dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127

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


-- 
Mailing list: https://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 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

2023-03-13 Thread Robert Pearson

Thank you so much!
I have two disk drives; one with 22.04 and one with 18.04.3. When the
update rendered 22.04 useless, I switched to 18.04.3. I got your
explanation on how to use different kernels. When 18.04.3 crashed, I tried
using a different kernel. In grub, I selected Advanced options and selected
the previous generic kernel linux-image-5.19.0-31-generic. That immediately
fixed the problem.
Apparently, the linux-image-5.19.0-35-generic has the bug.
Until they get around to fixing the defective 5.19.0-35 kernel, I will use
5.19.0-31 kernel.
Thank you so much, yet again.
This is the first time that I have gotten a work-around for defective code
since I started using Ubuntu MATE.
Robert Pearson

On Tue, Mar 7, 2023 at 4:20 PM William <2007...@bugs.launchpad.net>
wrote:

> You select your kernel in the grub boot menu. There is an option for
> alternative boot configurations. I have a dual boot environment set up
> so grub comes up every time for me. I think you hit esc to bring it up
> if it normally boots straight into windows. If you have any trouble it
> should come up in a search pretty quick.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2007913
>
> Title:
>   HDMI Output sound has disappeared after Ubuntu update
>
> Status in alsa-driver package in Ubuntu:
>   Confirmed
>
> Bug description:
>   After months using the HDMI output without problems, it has stopped
> working after a system update two days ago.
>   HDMI output is not listed in the list of available output devices.
>   Same computer works with this sound output perfectly when booting with
> Windows or an older installation of Ubuntu (18.04).
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu7
>   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: Tue Feb 21 08:12:58 2023
>   EcryptfsInUse: Yes
>   InstallationDate: Installed on 2022-04-30 (296 days ago)
>   InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
> (20220419)
>   PackageArchitecture: all
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=ca_ES.UTF-8
>SHELL=/bin/bash
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Title: USB sound card not detected
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 10/20/2021
>   dmi.bios.release: 5.13
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: M01EWR120
>   dmi.board.asset.tag: OEM Default string000
>   dmi.board.name: OEM Default string000
>   dmi.board.vendor: OEM Default string000
>   dmi.board.version: OEM Default string000
>   dmi.chassis.asset.tag: OEM Default string000
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: OEM Default string000
>   dmi.chassis.version: OEM Default string000
>   dmi.ec.firmware.release: 1.2
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
>   dmi.product.family: OEM Default string000
>   dmi.product.name: CoreBox
>   dmi.product.sku: OEM Default string000
>   dmi.product.version: OEM Default string000
>   dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
>   mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+subscriptions
>
>

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

Title:
  HDMI Output sound has disappeared after Ubuntu update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After months using the HDMI output without problems, it has stopped working 
after a system update two days ago.
  HDMI output is not listed in the list of available output devices.
  Same computer works with this sound output perfectly when booting with 
Windows or an older installation of Ubuntu (18.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  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
  CurrentDesk

Re: [Desktop-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

2023-03-07 Thread Robert Pearson

"Booting with linux-image-5.19.0-21-generic lists the audio
devices again."

So how do I do that?

On Tue, Mar 7, 2023 at 5:20 AM William <2007...@bugs.launchpad.net>
wrote:

> Booting with linux-image-5.19.0-35-generic appears to be the problem in
> 22.10. Booting with linux-image-5.19.0-21-generic lists the audio
> devices again.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2007913
>
> Title:
>   HDMI Output sound has disappeared after Ubuntu update
>
> Status in alsa-driver package in Ubuntu:
>   Confirmed
>
> Bug description:
>   After months using the HDMI output without problems, it has stopped
> working after a system update two days ago.
>   HDMI output is not listed in the list of available output devices.
>   Same computer works with this sound output perfectly when booting with
> Windows or an older installation of Ubuntu (18.04).
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu7
>   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: Tue Feb 21 08:12:58 2023
>   EcryptfsInUse: Yes
>   InstallationDate: Installed on 2022-04-30 (296 days ago)
>   InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
> (20220419)
>   PackageArchitecture: all
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=ca_ES.UTF-8
>SHELL=/bin/bash
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Title: USB sound card not detected
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 10/20/2021
>   dmi.bios.release: 5.13
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: M01EWR120
>   dmi.board.asset.tag: OEM Default string000
>   dmi.board.name: OEM Default string000
>   dmi.board.vendor: OEM Default string000
>   dmi.board.version: OEM Default string000
>   dmi.chassis.asset.tag: OEM Default string000
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: OEM Default string000
>   dmi.chassis.version: OEM Default string000
>   dmi.ec.firmware.release: 1.2
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
>   dmi.product.family: OEM Default string000
>   dmi.product.name: CoreBox
>   dmi.product.sku: OEM Default string000
>   dmi.product.version: OEM Default string000
>   dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
>   mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+subscriptions
>
>

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

Title:
  HDMI Output sound has disappeared after Ubuntu update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After months using the HDMI output without problems, it has stopped working 
after a system update two days ago.
  HDMI output is not listed in the list of available output devices.
  Same computer works with this sound output perfectly when booting with 
Windows or an older installation of Ubuntu (18.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  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: Tue Feb 21 08:12:58 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-30 (296 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M01EWR120
  dmi.board.asset.tag: OEM Default string000
  dmi.board.name: OEM Default string000
  dmi.board.vendor: OEM Default string000
  dmi.board.version: OEM Default string000
  dmi.chassis.asset.tag: OEM Default string000
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Default string000
  dmi.chassis.version: OEM Default string000
  dmi.ec.firmware.release: 1.2
  dmi.modalias:

[Desktop-packages] [Bug 1970050] Re: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all because of upgrade from 20.04 LTS to 22.04

2023-03-04 Thread Robert Pearson

This leaves those of us with AMD processors out in the cold. Should I
roll back to Ubuntu MATE 18.04 for a working system until you fix your
update bug?

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

Title:
  [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all
  because of upgrade from 20.04 LTS to 22.04

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After upgrading today from 20.04 LTS to 22.04
  HDMI Audio does not work at all.
  Audio from speakers from a headphone jack works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  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: Sat Apr 23 21:13:23 2022
  InstallationDate: Installed on 2020-04-24 (729 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Built-in Audio - HDA Intel HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all
  UpgradeStatus: Upgraded to jammy on 2022-04-23 (0 days ago)
  dmi.bios.date: 04/21/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H97M-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnH97M-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97M-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: H97M-HD3
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Desktop-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

2023-03-04 Thread Robert Pearson

When I run lspci it lists
00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri HDMI/DP 
Audio Controller.

The latest update to Ubuntu MATE 22.04 just ignores it.

In the control center/sound/output it only sees the IEC958 built-in
audio digital stereo.

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

Title:
  HDMI Output sound has disappeared after Ubuntu update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After months using the HDMI output without problems, it has stopped working 
after a system update two days ago.
  HDMI output is not listed in the list of available output devices.
  Same computer works with this sound output perfectly when booting with 
Windows or an older installation of Ubuntu (18.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  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: Tue Feb 21 08:12:58 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-30 (296 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M01EWR120
  dmi.board.asset.tag: OEM Default string000
  dmi.board.name: OEM Default string000
  dmi.board.vendor: OEM Default string000
  dmi.board.version: OEM Default string000
  dmi.chassis.asset.tag: OEM Default string000
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Default string000
  dmi.chassis.version: OEM Default string000
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
  dmi.product.family: OEM Default string000
  dmi.product.name: CoreBox
  dmi.product.sku: OEM Default string000
  dmi.product.version: OEM Default string000
  dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127

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


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

[Desktop-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update

2023-03-04 Thread Robert Pearson

My system is an ASUS A88XM-A with AMD A8-7600 Radeon R7. Video and audio
output are via HDMI.

As soon as I installed the latest update to Ubuntu MATE 22.04 the audio
broke. When I went to the control center, the entry for HDMI audio
wasn't there.

Apparently, the coder assumed everybody was using the motherboard audio
and nobody uses HDMI or Display Port output.

Please restore the HDMI audio output.

This is a previously reported bug, just different hardware.

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

Title:
  HDMI Output sound has disappeared after Ubuntu update

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After months using the HDMI output without problems, it has stopped working 
after a system update two days ago.
  HDMI output is not listed in the list of available output devices.
  Same computer works with this sound output perfectly when booting with 
Windows or an older installation of Ubuntu (18.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  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: Tue Feb 21 08:12:58 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2022-04-30 (296 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M01EWR120
  dmi.board.asset.tag: OEM Default string000
  dmi.board.name: OEM Default string000
  dmi.board.vendor: OEM Default string000
  dmi.board.version: OEM Default string000
  dmi.chassis.asset.tag: OEM Default string000
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Default string000
  dmi.chassis.version: OEM Default string000
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000:
  dmi.product.family: OEM Default string000
  dmi.product.name: CoreBox
  dmi.product.sku: OEM Default string000
  dmi.product.version: OEM Default string000
  dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127

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


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

[Desktop-packages] [Bug 1998765] Re: libnl3 3.4.0 doesn't work with WCN3980

2023-01-17 Thread Robert Liu

I installed the updated version on the platform which needs this patch.
After updating the packages, the platform can scan and connect to a WiFi
network correctly.

I also tried other amd64, armhf and arm64 platforms which don't require
the patch originally and their wifi device still work after upgrading.

$ dpkg -l |grep libnl
ii  libnl-3-200:armhf  3.4.0-1ubuntu0.1  armhf  
  library for dealing with netlink sockets
ii  libnl-genl-3-200:armhf 3.4.0-1ubuntu0.1  armhf  
  library for dealing with netlink sockets - generic netlink
ii  libnl-route-3-200:armhf3.4.0-1ubuntu0.1  armhf  
  library for dealing with netlink sockets - route interface

$ sudo netplan apply
$ ip a
  ...
3: wlan0:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
link/ether dc:a6:32:37:fa:a7 brd ff:ff:ff:ff:ff:ff
inet 10.102.138.56/22 brd 10.102.139.255 scope global dynamic wlan0
   valid_lft 600sec preferred_lft 600sec
inet6 fe80::dea6:32ff:fe37:faa7/64 scope link 
   valid_lft forever preferred_lft forever

$ sudo ping -I wlan0 8.8.8.8
PING 8.8.8.8 (8.8.8.8) from 10.102.138.56 wlan0: 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=10.4 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=5.64 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=5.73 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=6.09 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=57 time=6.98 ms


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

** Changed in: oem-priority/focal
   Status: New => Fix Committed

** Changed in: oem-priority/focal
   Importance: Undecided => High

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

Title:
  libnl3 3.4.0 doesn't work with WCN3980

Status in OEM Priority Project:
  Fix Committed
Status in OEM Priority Project focal series:
  Fix Committed
Status in libnl3 package in Ubuntu:
  Fix Released
Status in libnl3 source package in Focal:
  Fix Committed
Status in libnl3 source package in Jammy:
  Invalid

Bug description:
  [ Impact ] 
  When testing Qualcomm qcs410 with WCN3980 with 20.04 and UC20, WCN3980 is not 
able connect to an AP.

  However, with the libnl3 (3.5.0) from BSP, WCN3980 can work correctly.

  After bisecting the commits from 3.4.0 to 3.5.0, this commit[1] is
  identified as the root cause.

  According to the commit, the "NLA_F_NESTED" flag should be set for
  kernel later than 5.2.

  [ Test Plan ]
  Verify with the updated version, the WIFI module can:
1. scan WIFI networks
2. connect to an available network
3. access to the connected network

  [ Where problems could occur ]
  1. kernel versions without NLA_F_NESTED flag defined
This flag is introduced before Linux kernel v5 (checked v3.x and v4.x have 
it). It would not be a problem for an older kernel to understand/work with this 
change. Since the GA kernel is 5.4, so a generic image would still work.

  2. Drivers don't use the NESTED flag.
According to hui.wang's input, this change should not affect drivers which 
don't use the NESTED flag. But, it'd be better to cover more Wifi modules.

  [ Other Info ]
  22.04 is using libnl3 3.0.5-0.1, so only 20.04 needs this patch.

  
  [1] 
https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133

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


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

[Desktop-packages] [Bug 2002212] [NEW] Outdated version of libglib2.0-dev in Ubuntu Jammy

2023-01-07 Thread Bajcsi Elias-Robert

Public bug reported:

The version of libglib2.0-dev that is currently included in the
repositories for Ubuntu is 2.72.1-1, which is outdated and missing
important features and bug fixes. In particular, the
G_APPLICATION_DEFAULT_FLAGS macro, which was added in GTK+ 3.22, is not
available in this version of libglib2.0-dev. This is causing issues with
my application, which requires the use of this macro.

I request that the package be updated to the latest version (currently
2.74) in order to resolve this issue.

Steps to reproduce:
  1. Install libglib2.0-dev version 2.72.1-1 on an Ubuntu system
  2. Attempt to compile an application that uses the 
G_APPLICATION_DEFAULT_FLAGS macro
  3. Observe the compilation error due to the missing macro

Expected result:
The application compiles successfully and can be run.

Actual result:
The application fails to compile due to the missing G_APPLICATION_DEFAULT_FLAGS 
macro.

Release:
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

Using version:
2.72.1-1

Requested version:
2.74(+)

** Affects: glib2.0 (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/2002212

Title:
  Outdated version of libglib2.0-dev in Ubuntu Jammy

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  The version of libglib2.0-dev that is currently included in the
  repositories for Ubuntu is 2.72.1-1, which is outdated and missing
  important features and bug fixes. In particular, the
  G_APPLICATION_DEFAULT_FLAGS macro, which was added in GTK+ 3.22, is
  not available in this version of libglib2.0-dev. This is causing
  issues with my application, which requires the use of this macro.

  I request that the package be updated to the latest version (currently
  2.74) in order to resolve this issue.

  Steps to reproduce:
1. Install libglib2.0-dev version 2.72.1-1 on an Ubuntu system
2. Attempt to compile an application that uses the 
G_APPLICATION_DEFAULT_FLAGS macro
3. Observe the compilation error due to the missing macro

  Expected result:
  The application compiles successfully and can be run.

  Actual result:
  The application fails to compile due to the missing 
G_APPLICATION_DEFAULT_FLAGS macro.

  Release:
Description:Ubuntu 22.04.1 LTS
Release:22.04

  Using version:
  2.72.1-1

  Requested version:
  2.74(+)

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


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

[Desktop-packages] [Bug 1970389] Re: [nvidia] Janky text entry and frames appear out of order in Xwayland apps

2022-12-20 Thread Robert Carroll

I'm experiencing this too.  No idea how to replicate it as it seems
pretty random.  Were you able to find a solution?

I find it happens on almost any "Chromium-based" application like
Discord and Brave Browser.

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

Title:
  [nvidia] Janky text entry and frames appear out of order in Xwayland
  apps

Status in X.Org X server:
  New
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed
Status in xwayland package in Ubuntu:
  Confirmed

Bug description:
  When writing into text fields in some applications (Firefox, VS Code)
  on Jammy in a GNOME / Wayland session, I can see an effect best
  described as the glyphs appearing / disappearing sometimes repeatedly.
  I have attached a recording from my phone (since attempting to record
  a screencast fails).

  This doesn't happen always, and it appear somehow sensitive to some
  environmental condition (load?) since for example when I'm on a video
  call, the effect seems to not be happening so often.

  I have also experienced a few instances of a currently not-focused
  window disappearing (seeing through to a window that is below that
  window), but cannot reproduce that reliably.

  I have the NVIDIA driver 510 in use, RTX3090-only 16-core Zen1
  Threadripper system with no integrated GPU.

  No similar effects visible when in a GNOME / Xorg session.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 12:17:02 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-11-08 (168 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-22 (3 days ago)

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


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

[Desktop-packages] [Bug 1998765] Re: libnl3 3.4.0 doesn't work with WCN3980

2022-12-12 Thread Robert Liu

** Description changed:

- When testing WCN3980 with 20.04 and UC20, WCN3980 is not able connect to
- an AP.
+ [ Impact ] 
+ When testing Qualcomm qcs410 with WCN3980 with 20.04 and UC20, WCN3980 is not 
able connect to an AP.
  
- I tried a different libnl3 from BSP and found that WCN3980 can work
- correctly. The version used in BSP is 3.5.0.
+ However, with the libnl3 (3.5.0) from BSP, WCN3980 can work correctly.
  
- I bisected the commits from 3.4.0 to 3.5.0 and found this commit[1] is the 
root cause.
- According to the commit, it seems that the flag should be set for kernel 
later than 5.2.
+ After bisecting the commits from 3.4.0 to 3.5.0, this commit[1] is
+ identified as the root cause.
+ 
+ According to the commit, the "NLA_F_NESTED" flag should be set for
+ kernel later than 5.2.
+ 
+ [ Test Plan ]
+ Verify with the updated version, the WIFI module can:
+   1. scan WIFI networks
+   2. connect to an available network
+   3. access to the connected network
+ 
+ [ Where problems could occur ]
+ 1. kernel versions without NLA_F_NESTED flag defined
+   This flag is introduced before Linux kernel v5 (checked v3.x and v4.x have 
it). It would not be a problem for an older kernel to understand/work with this 
change. Since the GA kernel is 5.4, so a generic image would still work.
+ 
+ 2. Drivers don't use the NESTED flag.
+   According to hui.wang's input, this change should not affect drivers which 
don't use the NESTED flag. But, it'd be better to cover more Wifi modules.
+ 
+ [ Other Info ]
+ 22.04 is using libnl3 3.0.5-0.1, so only 20.04 needs this patch.
  
  
  [1] 
https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133

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

Title:
  libnl3 3.4.0 doesn't work with WCN3980

Status in OEM Priority Project:
  New
Status in libnl3 package in Ubuntu:
  New

Bug description:
  [ Impact ] 
  When testing Qualcomm qcs410 with WCN3980 with 20.04 and UC20, WCN3980 is not 
able connect to an AP.

  However, with the libnl3 (3.5.0) from BSP, WCN3980 can work correctly.

  After bisecting the commits from 3.4.0 to 3.5.0, this commit[1] is
  identified as the root cause.

  According to the commit, the "NLA_F_NESTED" flag should be set for
  kernel later than 5.2.

  [ Test Plan ]
  Verify with the updated version, the WIFI module can:
1. scan WIFI networks
2. connect to an available network
3. access to the connected network

  [ Where problems could occur ]
  1. kernel versions without NLA_F_NESTED flag defined
This flag is introduced before Linux kernel v5 (checked v3.x and v4.x have 
it). It would not be a problem for an older kernel to understand/work with this 
change. Since the GA kernel is 5.4, so a generic image would still work.

  2. Drivers don't use the NESTED flag.
According to hui.wang's input, this change should not affect drivers which 
don't use the NESTED flag. But, it'd be better to cover more Wifi modules.

  [ Other Info ]
  22.04 is using libnl3 3.0.5-0.1, so only 20.04 needs this patch.

  
  [1] 
https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133

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


-- 
Mailing list: https://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 1341155] Re: Xorg crashed with SIGABRT in pci_device_next() with mesa utils

2022-12-06 Thread Robert Avant

Hi,

That is fine, having updated I have not had a recurrence of this bug to my
knowledge.

Regards

R. Avant

On Mon, 5 Dec 2022, 6:48 pm Paul White, <1341...@bugs.launchpad.net>
wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. We are sorry that we do not always have the capacity to
> review all reported bugs in a timely manner.
>
> Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
>
> I'm setting the status of this bug to 'Incomplete' as it's not seen any
> activity for some time. If this issue is still relevant when using a
> currently maintained release of Ubuntu then please let us know which
> one(s) otherwise this bug report can be left to expire in approximately
> 60 days time.
>
> ** Changed in: xorg-server (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1378665).
> https://bugs.launchpad.net/bugs/1341155
>
> Title:
>   Xorg crashed with SIGABRT in pci_device_next() with mesa utils
>
> Status in xorg-server package in Ubuntu:
>   Incomplete
>
> Bug description:
>   came up when i installed mesa utils with nvidia optimus graphic card
>   and i was testing it happend when i change from nvidia to intel after
>   i tested glxgears
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 14.10
>   Package: xserver-xorg-core 2:1.15.1-0ubuntu8
>   ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4
>   Uname: Linux 3.16.0-3-generic x86_64
>   .tmp.unity.support.test.0:
>
>   ApportVersion: 2.14.4-0ubuntu2
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   CrashCounter: 1
>   Date: Sat Jul 12 18:22:19 2014
>   DistUpgraded: Fresh install
>   DistroCodename: utopic
>   DistroVariant: ubuntu
>   ExecutablePath: /usr/bin/Xorg
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>Intel Corporation Mobile 4 Series Chipset Integrated Graphics
> Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller])
>  Subsystem: ASUSTeK Computer Inc. Device [1043:1af2]
>   InstallationDate: Installed on 2014-07-10 (1 days ago)
>   InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
>   MachineType: ASUSTeK Computer Inc. UL30VT
>   ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth
> /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
>   ProcEnviron:
>
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-3-generic
> root=UUID=b797dc1a-0cba-433f-89ce-7fb6e4f6d4c9 ro quiet splash vt.handoff=7
>   Signal: 6
>   SourcePackage: xorg-server
>   StacktraceTop:
>pci_device_next () from /usr/lib/x86_64-linux-gnu/libpciaccess.so.0
>pci_device_find_by_slot () from
> /usr/lib/x86_64-linux-gnu/libpciaccess.so.0
>pci_device_vgaarb_init () from
> /usr/lib/x86_64-linux-gnu/libpciaccess.so.0
>?? ()
>xf86BusConfig ()
>   Title: Xorg crashed with SIGABRT in pci_device_next()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups:
>
>   dmi.bios.date: 07/14/2010
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 211
>   dmi.board.asset.tag: ATN12345678901234567
>   dmi.board.name: UL30VT
>   dmi.board.vendor: ASUSTeK Computer Inc.
>   dmi.board.version: 1.0
>   dmi.chassis.asset.tag: ATN12345678901234567
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: ASUSTeK Computer Inc.
>   dmi.chassis.version: 1.0
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr211:bd07/14/2010:svnASUSTeKComputerInc.:pnUL30VT:pvr1.0:rvnASUSTeKComputerInc.:rnUL30VT:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
>   dmi.product.name: UL30VT
>   dmi.product.version: 1.0
>   dmi.sys.vendor: ASUSTeK Computer Inc.
>   version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.54-1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.8.2-1ubuntu2
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu4
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.910-0ubuntu1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.10-1ubuntu2
>   xserver.bootTime: Sat Jul 12 18:22:34 2014
>   xserver.configfile: default
>   xserver.errors:
>
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.outputs:
>product id4140
>vendor AUO
>   xserver.version: 2:1.15.1-0ubuntu8
>
> To manage notifications about this bug go to:
>
>

[Desktop-packages] [Bug 1998765] Re: libnl3 3.4.0 doesn't work with WCN3980

this issue was discovered in an OEM project.

** Package changed: libnl3 (Ubuntu) => oem-priority

** Changed in: oem-priority
 Assignee: (unassigned) => Robert Liu (robertliu)

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

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

Title:
  libnl3 3.4.0 doesn't work with WCN3980

Status in OEM Priority Project:
  New
Status in libnl3 package in Ubuntu:
  New

Bug description:
  When testing WCN3980 with 20.04 and UC20, WCN3980 is not able connect
  to an AP.

  I tried a different libnl3 from BSP and found that WCN3980 can work
  correctly. The version used in BSP is 3.5.0.

  I bisected the commits from 3.4.0 to 3.5.0 and found this commit[1] is the 
root cause.
  According to the commit, it seems that the flag should be set for kernel 
later than 5.2.

  
  [1] 
https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133

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


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

[Desktop-packages] [Bug 1998765] Re: libnl3 3.4.0 doesn't work with WCN3980

** Tags added: orignate-from-lp1998578

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

Title:
  libnl3 3.4.0 doesn't work with WCN3980

Status in libnl3 package in Ubuntu:
  New

Bug description:
  When testing WCN3980 with 20.04 and UC20, WCN3980 is not able connect
  to an AP.

  I tried a different libnl3 from BSP and found that WCN3980 can work
  correctly. The version used in BSP is 3.5.0.

  I bisected the commits from 3.4.0 to 3.5.0 and found this commit[1] is the 
root cause.
  According to the commit, it seems that the flag should be set for kernel 
later than 5.2.

  
  [1] 
https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133

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


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

[Desktop-packages] [Bug 1998765] Re: libnl3 3.4.0 doesn't work with WCN3980

I made a test build (debdiff attached) and tried it on the target
device. This version works correctly.


** Patch added: "libnl3_3.4.0-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1998765/+attachment/5634558/+files/libnl3_3.4.0-1ubuntu1.debdiff

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

Title:
  libnl3 3.4.0 doesn't work with WCN3980

Status in libnl3 package in Ubuntu:
  New

Bug description:
  When testing WCN3980 with 20.04 and UC20, WCN3980 is not able connect
  to an AP.

  I tried a different libnl3 from BSP and found that WCN3980 can work
  correctly. The version used in BSP is 3.5.0.

  I bisected the commits from 3.4.0 to 3.5.0 and found this commit[1] is the 
root cause.
  According to the commit, it seems that the flag should be set for kernel 
later than 5.2.

  
  [1] 
https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133

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


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

[Desktop-packages] [Bug 1998765] [NEW] libnl3 3.4.0 doesn't work with WCN3980

Public bug reported:

When testing WCN3980 with 20.04 and UC20, WCN3980 is not able connect to
an AP.

I tried a different libnl3 from BSP and found that WCN3980 can work
correctly. The version used in BSP is 3.5.0.

I bisected the commits from 3.4.0 to 3.5.0 and found this commit[1] is the root 
cause.
According to the commit, it seems that the flag should be set for kernel later 
than 5.2.


[1] 
https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133

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

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

Title:
  libnl3 3.4.0 doesn't work with WCN3980

Status in libnl3 package in Ubuntu:
  New

Bug description:
  When testing WCN3980 with 20.04 and UC20, WCN3980 is not able connect
  to an AP.

  I tried a different libnl3 from BSP and found that WCN3980 can work
  correctly. The version used in BSP is 3.5.0.

  I bisected the commits from 3.4.0 to 3.5.0 and found this commit[1] is the 
root cause.
  According to the commit, it seems that the flag should be set for kernel 
later than 5.2.

  
  [1] 
https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133

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


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

[Desktop-packages] [Bug 1998267] Re: glib not aware of snap confinement

2022-11-29 Thread Robert Ancell

Targeting 22.04 so this can become part of the core22 snap fixing the
issue for most modern snaps.

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

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

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

** Changed in: glib2.0 (Ubuntu Jammy)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: glib2.0 (Ubuntu Kinetic)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: glib2.0 (Ubuntu Lunar)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  glib not aware of snap confinement

Status in glib2.0 package in Ubuntu:
  New
Status in glib2.0 source package in Jammy:
  New
Status in glib2.0 source package in Kinetic:
  New
Status in glib2.0 source package in Lunar:
  New

Bug description:
  [ Impact]

  glib is not aware of snap confinement and this causes the internal
  logic to decide when to use portals to not work as designed. One
  important case is the gsettings backend, which should use a keyfile
  when confined rather than using dconf. When using a fully confined
  desktop this is required, as dconf is not suitable for sharing between
  snaps.

  This has been fixed in glib main:
  https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020

  [ Test Plan ]

  1. Install gnome-calculator snap:
  $ snap install gnome-calculator
  2. Disconnect gsettings interface:
  $ snap disconnect gnome-calculator:gsettings
  3. Run gnome-calculator
  4. Change mode from basic to advanced
  5. Close and re-open gnome-calculator

  Expected result:
  Mode change remembered on second run. gnome-calculator settings written to 
~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile

  Observed result:
  Mode change not remembered on second run, errors shown in console about 
accessing dconf:
  (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create 
file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied.  
dconf will not work properly.

  [ Where problems could occur ]

  - New bug introduced in glib causing a crash.
  - Security issue introduced in glib due to accessing snapctl.
  - Unexpected behaviour change when running snaps with updated glib.

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


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

[Desktop-packages] [Bug 1998267] [NEW] glib not aware of snap confinement

2022-11-29 Thread Robert Ancell

Public bug reported:

[ Impact]

glib is not aware of snap confinement and this causes the internal logic
to decide when to use portals to not work as designed. One important
case is the gsettings backend, which should use a keyfile when confined
rather than using dconf. When using a fully confined desktop this is
required, as dconf is not suitable for sharing between snaps.

This has been fixed in glib main:
https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020

[ Test Plan ]

1. Install gnome-calculator snap:
$ snap install gnome-calculator
2. Disconnect gsettings interface:
$ snap disconnect gnome-calculator:gsettings
3. Run gnome-calculator
4. Change mode from basic to advanced
5. Close and re-open gnome-calculator

Expected result:
Mode change remembered on second run. gnome-calculator settings written to 
~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile

Observed result:
Mode change not remembered on second run, errors shown in console about 
accessing dconf:
(gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create 
file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied.  
dconf will not work properly.

[ Where problems could occur ]

- New bug introduced in glib causing a crash.
- Security issue introduced in glib due to accessing snapctl.
- Unexpected behaviour change when running snaps with updated glib.

** Affects: glib2.0 (Ubuntu)
 Importance: High
 Assignee: Robert Ancell (robert-ancell)
 Status: New

** Affects: glib2.0 (Ubuntu Jammy)
 Importance: High
 Assignee: Robert Ancell (robert-ancell)
 Status: New

** Affects: glib2.0 (Ubuntu Kinetic)
 Importance: High
 Assignee: Robert Ancell (robert-ancell)
 Status: New

** Affects: glib2.0 (Ubuntu Lunar)
 Importance: High
 Assignee: Robert Ancell (robert-ancell)
 Status: New

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

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

** Also affects: glib2.0 (Ubuntu Jammy)
   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/1998267

Title:
  glib not aware of snap confinement

Status in glib2.0 package in Ubuntu:
  New
Status in glib2.0 source package in Jammy:
  New
Status in glib2.0 source package in Kinetic:
  New
Status in glib2.0 source package in Lunar:
  New

Bug description:
  [ Impact]

  glib is not aware of snap confinement and this causes the internal
  logic to decide when to use portals to not work as designed. One
  important case is the gsettings backend, which should use a keyfile
  when confined rather than using dconf. When using a fully confined
  desktop this is required, as dconf is not suitable for sharing between
  snaps.

  This has been fixed in glib main:
  https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3020

  [ Test Plan ]

  1. Install gnome-calculator snap:
  $ snap install gnome-calculator
  2. Disconnect gsettings interface:
  $ snap disconnect gnome-calculator:gsettings
  3. Run gnome-calculator
  4. Change mode from basic to advanced
  5. Close and re-open gnome-calculator

  Expected result:
  Mode change remembered on second run. gnome-calculator settings written to 
~/snap/gnome-calculator/current/.config/glib-2.0/settings/keyfile

  Observed result:
  Mode change not remembered on second run, errors shown in console about 
accessing dconf:
  (gnome-calculator:1031938): dconf-CRITICAL **: 14:08:56.034: unable to create 
file '/run/user/1000/snap.gnome-calculator/dconf/user': Permission denied.  
dconf will not work properly.

  [ Where problems could occur ]

  - New bug introduced in glib causing a crash.
  - Security issue introduced in glib due to accessing snapctl.
  - Unexpected behaviour change when running snaps with updated glib.

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


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

[Desktop-packages] [Bug 1950094]

2022-11-23 Thread Nv4y-robert

No bug also in
Version: 7.1.5.2 / LibreOffice Community
Build ID: 85f04e9f809797b8199d13c421bd8a2b025d52b5
CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5
Locale: de-DE (de_DE.UTF-8); UI: en-US
Calc: threaded

on OpenSUSE 15.3 64 bit rpm.

This is (nearly) one of the versions tested for the bug description.

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

Title:
  libreoffice base zone liste choix impossible

Status in LibreOffice:
  Incomplete
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:

  Bonjour,

  Ce phénomène existait déjà sous UbuntuMate 20.04. J'ai donc chargé
  UbuntuMate 21.10 afin de voir si une modification avait été apporté à
  un éventuel bogue que je vous soumets.

  Le souci est avec la zone de liste dans LibreOffice Base avec la macro
  ci-dessous sur Événement "A réception du focus".

  Sub ActualiserListe(oEv as Object)
  oEv.Source.Model.Refresh
  End Sub

  pour mettre à jour la zone de liste après modification d'un élément.

  La mise à jour fonctionne bien mais je ne peux pas choisir une
  nouvelle entrée dans la liste. Alors que si je choisis un autre
  événement, comme "souris déplacée alors qu'une touche est pressée"
  beaucoup moins pratique, je ne rencontre pas ce problème.

  Après plusieurs recherches sur le forum OpenOffice il s'avère que la
  fonction marche bien mais que le problème pourrait venir de
  l'environnement Ubuntu.

  Sauriez-vous m'aider pour débloquer ma situation ?

  Dommage que je ne puisse pas joindre mon fichier pour des essais sur
  vos propres machines ce serait plus "parlant".

  Merci.
  Éric

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


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

[Desktop-packages] [Bug 1950094]

2022-11-23 Thread Nv4y-robert

Have tested this:
Opened "fbooks"
Entered new row with 'Informatik'.
Switched to previous row to save the data in table control.
Closed by button.
Switched to listbox.
'Informatik' will be shown.

So: No bug detected on
Version: 7.4.3.2 / LibreOffice Community
Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890
CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb)
Locale: de-DE (de_DE.UTF-8); UI: en-US
Calc: threaded

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

Title:
  libreoffice base zone liste choix impossible

Status in LibreOffice:
  Incomplete
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:

  Bonjour,

  Ce phénomène existait déjà sous UbuntuMate 20.04. J'ai donc chargé
  UbuntuMate 21.10 afin de voir si une modification avait été apporté à
  un éventuel bogue que je vous soumets.

  Le souci est avec la zone de liste dans LibreOffice Base avec la macro
  ci-dessous sur Événement "A réception du focus".

  Sub ActualiserListe(oEv as Object)
  oEv.Source.Model.Refresh
  End Sub

  pour mettre à jour la zone de liste après modification d'un élément.

  La mise à jour fonctionne bien mais je ne peux pas choisir une
  nouvelle entrée dans la liste. Alors que si je choisis un autre
  événement, comme "souris déplacée alors qu'une touche est pressée"
  beaucoup moins pratique, je ne rencontre pas ce problème.

  Après plusieurs recherches sur le forum OpenOffice il s'avère que la
  fonction marche bien mais que le problème pourrait venir de
  l'environnement Ubuntu.

  Sauriez-vous m'aider pour débloquer ma situation ?

  Dommage que je ne puisse pas joindre mon fichier pour des essais sur
  vos propres machines ce serait plus "parlant".

  Merci.
  Éric

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


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

[Desktop-packages] [Bug 1950094]

2022-11-23 Thread Nv4y-robert

… and new book types could also be saved in both versions of LO, tested
with OpenSUSE 15.3 64bit rpm Linux.

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

Title:
  libreoffice base zone liste choix impossible

Status in LibreOffice:
  Incomplete
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:

  Bonjour,

  Ce phénomène existait déjà sous UbuntuMate 20.04. J'ai donc chargé
  UbuntuMate 21.10 afin de voir si une modification avait été apporté à
  un éventuel bogue que je vous soumets.

  Le souci est avec la zone de liste dans LibreOffice Base avec la macro
  ci-dessous sur Événement "A réception du focus".

  Sub ActualiserListe(oEv as Object)
  oEv.Source.Model.Refresh
  End Sub

  pour mettre à jour la zone de liste après modification d'un élément.

  La mise à jour fonctionne bien mais je ne peux pas choisir une
  nouvelle entrée dans la liste. Alors que si je choisis un autre
  événement, comme "souris déplacée alors qu'une touche est pressée"
  beaucoup moins pratique, je ne rencontre pas ce problème.

  Après plusieurs recherches sur le forum OpenOffice il s'avère que la
  fonction marche bien mais que le problème pourrait venir de
  l'environnement Ubuntu.

  Sauriez-vous m'aider pour débloquer ma situation ?

  Dommage que je ne puisse pas joindre mon fichier pour des essais sur
  vos propres machines ce serait plus "parlant".

  Merci.
  Éric

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


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

[Desktop-packages] [Bug 1969891] Re: Firefox snap can't be added to Dock favorites

2022-10-27 Thread Robert

Hey all,

I have the same issue.

My favourites setting lists the following:

:~$ gsettings get org.gnome.shell favorite-apps
['org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 
'virt-manager.desktop', 'libreoffice-calc.desktop', 
'signal-desktop_signal-desktop.desktop', 'firefox_firefox.desktop', 
'vivaldi-stable.desktop']


Please let me know if you require any further information as this is 
surprisingly annoying!

Thanks!

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

Title:
  Firefox snap can't be added to Dock favorites

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

Bug description:
  After upgrading from 21.10 to 22.04 the old Firefox was removed from
  my Dock favorites. I readded Firefox to my favorites which adds the
  Firefox icon to the favorites as expected.

  However, clicking on it will open the Firefox snap on the bottom of
  the Dock. So now I have 2 Firefox symbols in my Dock.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.0-2ubuntu1
  Uname: Linux 5.17.0-4.1-liquorix-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 08:49:32 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2021-05-31 (325 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  RelatedPackageVersions: mutter-common 42.0-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago)

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


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

[Desktop-packages] [Bug 1993284] Re: Dash-to-dock shows blank black screen after computer locked for some time (Ubuntu 22.04)

2022-10-20 Thread Robert Bartko

After some testing issue appeared even with Intelligent Autohide
functi0on on Dash to Dock disabled.

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

Title:
Dash-to-dock shows blank black screen after computer locked for some
  time (Ubuntu 22.04)

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

Bug description:
  Happening in Ubuntu 22.04

  How to reproduce:

  Left computer idle and locked for quite some time
  Unlock the computer
  Only Show Applications icon is shown in dash-to-dock
  When clicked, blank black screen with no application is shown. And can't 
return to desktop or do any other navigations.

  Log out / restart menu still works so I usually restart my computer to
  fix this.

  Affected application: micheleg-dash-to-dock

  ~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

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


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

[Desktop-packages] [Bug 1993284] Re: Dash-to-dock shows blank black screen after computer locked for some time (Ubuntu 22.04)

2022-10-20 Thread Robert Bartko

Additionally it seems to affect only when Intelligent Autohide is on on
the Dash to dock Extension.

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

Title:
Dash-to-dock shows blank black screen after computer locked for some
  time (Ubuntu 22.04)

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

Bug description:
  Happening in Ubuntu 22.04

  How to reproduce:

  Left computer idle and locked for quite some time
  Unlock the computer
  Only Show Applications icon is shown in dash-to-dock
  When clicked, blank black screen with no application is shown. And can't 
return to desktop or do any other navigations.

  Log out / restart menu still works so I usually restart my computer to
  fix this.

  Affected application: micheleg-dash-to-dock

  ~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

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


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

[Desktop-packages] [Bug 1993284] Re: Dash-to-dock shows blank black screen after computer locked for some time (Ubuntu 22.04)

2022-10-19 Thread Robert Bartko

The screen is rather grey, the "start menu" works - in the upper right
corner. One can reboot the Computer. The icon at the bottom can be only
clicked but nothing happens, open applications not shown in the dock on
bottom as usual. Add-on as open weather is responsive.

Shortcuts don't work, can't launch any applications or switch between
them. Also launching terminal doesn't work or making printscreen
(shortcuts).

** Attachment added: "darkscreen.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1993284/+attachment/5625172/+files/darkscreen.png

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

Title:
Dash-to-dock shows blank black screen after computer locked for some
  time (Ubuntu 22.04)

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

Bug description:
  Happening in Ubuntu 22.04

  How to reproduce:

  Left computer idle and locked for quite some time
  Unlock the computer
  Only Show Applications icon is shown in dash-to-dock
  When clicked, blank black screen with no application is shown. And can't 
return to desktop or do any other navigations.

  Log out / restart menu still works so I usually restart my computer to
  fix this.

  Affected application: micheleg-dash-to-dock

  ~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

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


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

[Desktop-packages] [Bug 1993284] Re: Dash-to-dock shows blank black screen after computer locked for some time (Ubuntu 22.04)

2022-10-18 Thread Robert Bartko

As seen in the attachment, after unlocking the screen only the dots menu
appears, after clicking it, the screen goes dark and only search is
active but not much else. One can still access reboot menu and restart
PC to fix the issue.

** Attachment added: "dashtodockBUG.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1993284/+attachment/5624834/+files/dashtodockBUG.png

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

Title:
Dash-to-dock shows blank black screen after computer locked for some
  time (Ubuntu 22.04)

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

Bug description:
  Happening in Ubuntu 22.04

  How to reproduce:

  Left computer idle and locked for quite some time
  Unlock the computer
  Only Show Applications icon is shown in dash-to-dock
  When clicked, blank black screen with no application is shown. And can't 
return to desktop or do any other navigations.

  Log out / restart menu still works so I usually restart my computer to
  fix this.

  Affected application: micheleg-dash-to-dock

  ~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

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


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

[Desktop-packages] [Bug 1993284] [NEW] Dash-to-dock shows blank black screen after computer locked for some time (Ubuntu 22.04)

2022-10-18 Thread Robert Bartko

Public bug reported:

Happening in Ubuntu 22.04

How to reproduce:

Left computer idle and locked for quite some time
Unlock the computer
Only Show Applications icon is shown in dash-to-dock
When clicked, blank black screen with no application is shown. And can't 
return to desktop or do any other navigations.

Log out / restart menu still works so I usually restart my computer to
fix this.

Affected application: micheleg-dash-to-dock

~$ lsb_release -rd
Description:Ubuntu 22.04.1 LTS
Release:22.04

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

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

Title:
Dash-to-dock shows blank black screen after computer locked for some
  time (Ubuntu 22.04)

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

Bug description:
  Happening in Ubuntu 22.04

  How to reproduce:

  Left computer idle and locked for quite some time
  Unlock the computer
  Only Show Applications icon is shown in dash-to-dock
  When clicked, blank black screen with no application is shown. And can't 
return to desktop or do any other navigations.

  Log out / restart menu still works so I usually restart my computer to
  fix this.

  Affected application: micheleg-dash-to-dock

  ~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

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


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

[Desktop-packages] [Bug 1987976]

Hm, this pretty much sounds like Gnome-Shell bug around Xwayland-on-
demand to me - so maybe a better place for that would be
https://gitlab.gnome.org/GNOME/mutter/-/issues (or a Ubuntu bug, in case
they ship some custom patches).

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

Title:
  firefox black window

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

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1987976]

So the fact that even software rendering (`gfx.webrender.software:true`)
is broken strongly suggest that something with the affected setup is
deeply broken - disabling hardware acceleration is usually our last
resort for such issues.

Alan, have you tested a few other Xwayland apps and do they all work
correctly? And is this on a clean system without weird modifications? :P

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

Title:
  firefox black window

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

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1987976]

Oh, that's really interesting...so does launching with
`MOZ_GTK_TITLEBAR_DECORATION=system` also solve the issue?

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

Title:
  firefox black window

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

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1987976]

(In reply to Alan Jenkins from comment #35)
> Weird!

Indeed :( But thanks for testing!

> I can run glxgears, xeyes, and xvidtune ok :-). (Didn't bother trying
those immediately after login).

I think these are all apps with server side decorations (SSD). Could you
try `GDK_BACKEND=x11 cheese` or `GDK_BACKEND=x11 gedit`? So we have GTK
apps with client side decorations (CSD)?

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

Title:
  firefox black window

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

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1987976]

Also, I suppose `gfx.webrender.software:true` works around the issue?

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

Title:
  firefox black window

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

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1987976]

Another interesting point would be if setting `gfx.x11-egl.force-
disabled` (in `about:config`) to `true` helps with the issue.

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

Title:
  firefox black window

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

Bug description:
  nicolas@nicolas-fixe:~$ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  nicolas@nicolas-fixe:~$ apt-cache policy firefox
  firefox:
    Installé : 1:1snap1-0ubuntu2
    Candidat : 1:1snap1-0ubuntu2
   Table de version :
   *** 1:1snap1-0ubuntu2 500
  500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  When I boot Ubuntu and start Firefox, the Firefox's window is totally
  black. See attachment.

  I am at your disposal to answer any question you have.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 28 12:42:29 2022
  InstallationDate: Installed on 2022-08-25 (2 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Snap.Changes: aucun changement trouvé
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1991472] [NEW] simple-scan does not work with hp5200

2022-10-01 Thread Robert Dinse

Public bug reported:

 Prior to upgrading from 22.04 to 22.10, simple-scan properly
supported my HP5200, now it fails saying cannot connect to scanner and
cannot connect to dbus.

 I attempted to install HP's version of hplip from their support
site, a fix that previously worked, but it does not work as it is
dependent upon qt4 which apparently is not available under 22.10.

 I attempted to contact their support but could not get through
their online filtering, same for calling them voice, so I was
unsuccessful.  Now I have to boot Win1o to scan documents and to put it
mildly I'm not a happy camper.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: simple-scan 42.0-1
Uname: Linux 5.19.12 x86_64
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Sat Oct  1 22:42:43 2022
MachineType: ASUS System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.12 
root=UUID=38243130-3d68-4f18-9973-08b9e226299f ro quiet splash 
i915.enable_gvt=1 intel_iommu=on iommu=pt vt.handoff=7
SourcePackage: simple-scan
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2020
dmi.bios.release: 18.2
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1802
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z390-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1802:bd12/01/2020:br18.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_CNL:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: ASUS_MB_CNL
dmi.product.version: System Version
dmi.sys.vendor: ASUS

** Affects: simple-scan (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug kinetic third-party-packages

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

Title:
  simple-scan does not work with hp5200

Status in simple-scan package in Ubuntu:
  New

Bug description:
   Prior to upgrading from 22.04 to 22.10, simple-scan properly
  supported my HP5200, now it fails saying cannot connect to scanner and
  cannot connect to dbus.

   I attempted to install HP's version of hplip from their support
  site, a fix that previously worked, but it does not work as it is
  dependent upon qt4 which apparently is not available under 22.10.

   I attempted to contact their support but could not get through
  their online filtering, same for calling them voice, so I was
  unsuccessful.  Now I have to boot Win1o to scan documents and to put
  it mildly I'm not a happy camper.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: simple-scan 42.0-1
  Uname: Linux 5.19.12 x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Sat Oct  1 22:42:43 2022
  MachineType: ASUS System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.12 
root=UUID=38243130-3d68-4f18-9973-08b9e226299f ro quiet splash 
i915.enable_gvt=1 intel_iommu=on iommu=pt vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2020
  dmi.bios.release: 18.2
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1802
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z390-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1802:bd12/01/2020:br18.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuASUS_MB_CNL:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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


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

[Desktop-packages] [Bug 1990448] Re: Show Ubuntu Pro settings

2022-09-21 Thread Robert Ancell

** Also affects: software-properties (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

Title:
  Show Ubuntu Pro settings

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New
Status in software-properties source package in Jammy:
  New
Status in software-properties source package in Kinetic:
  New

Bug description:
  Expose more of the Ubuntu Pro (aka Ubuntu Advantage) services instead
  of just Livepatch.

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


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

[Desktop-packages] [Bug 1990448] [NEW] Show Ubuntu Pro settings

2022-09-21 Thread Robert Ancell

Public bug reported:

Expose more of the Ubuntu Pro (aka Ubuntu Advantage) services instead of
just Livepatch.

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

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

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

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

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

** Also affects: software-properties (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: software-properties (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: software-properties (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: software-properties (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  Show Ubuntu Pro settings

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New
Status in software-properties source package in Jammy:
  New
Status in software-properties source package in Kinetic:
  New

Bug description:
  Expose more of the Ubuntu Pro (aka Ubuntu Advantage) services instead
  of just Livepatch.

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


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

[Desktop-packages] [Bug 1980781] Re: SRU of ubuntu-advantage-desktop-daemon to older series

2022-09-19 Thread Robert Ancell

** Also affects: ubuntu-advantage-desktop-daemon (Ubuntu Bionic)
Importance: Undecided
Status: New

** Changed in: ubuntu-advantage-desktop-daemon (Ubuntu Bionic)
Status: New => Fix Committed

** Changed in: ubuntu-advantage-desktop-daemon (Ubuntu Bionic)
Importance: Undecided => High

** Changed in: ubuntu-advantage-desktop-daemon (Ubuntu Bionic)
Assignee: (unassigned) => Sebastien Bacher (seb128)

** Also affects: ubuntu-advantage-desktop-daemon (Ubuntu Xenial)
Importance: Undecided
Status: New

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

Title:
SRU of ubuntu-advantage-desktop-daemon to older series

Status in ubuntu-advantage-desktop-daemon package in Ubuntu:
Fix Released
Status in ubuntu-advantage-desktop-daemon source package in Xenial:
New
Status in ubuntu-advantage-desktop-daemon source package in Bionic:
Fix Committed
Status in ubuntu-advantage-desktop-daemon source package in Focal:
Fix Committed

Bug description:
[Impact]

ubuntu-advantage-desktop-daemon is a service we added in 22.04 to let
desktop application interact easily with Ubuntu Advantage

adsys makes use of is to check if the system is connected to UA. This is
supported in 20.04 LTS but until now the daemon was not available there.
Installing the daemon enables advanced usages (scripts, privilege
delegation…) which require an Ubuntu Pro account

Ubuntu Pro integration is being added to software-properties which
also require the service to be available.

[Test Plan]

A. Verify the service

1. Install:
$ sudo apt install ubuntu-advantage-desktop-daemon
2. Check able to access daemon
$ gdbus call --system --dest com.canonical.UbuntuAdvantage --object-path
/com/canonical/UbuntuAdvantage/Manager --method
org.freedesktop.DBus.Properties.GetAll 'com.canonical.UbuntuAdvantage.Manager'
({'Attached': , 'DaemonVersion': <'1.8'>},)

B. Software-properties

Verify that the new 'Ubuntu Pro' page is working as expected, SRU bug
#, especially that it reflects the correct status and that
attaching/detaching a token and enabling/disabling services is working

C. Adsys (focal)

1. Ensure that you have an Ubuntu Advantage subcription enabled.
2. Setup some scripts under AD to be executed, one for machine scripts (on
startup), one for user scripts (on login). Those scripts can create some
temporary files under /tmp for instance.
3. Reboot and login on the Ubuntu laptop connected with AD by adsys.
4. Check that the scripts were executed by testing that the created file
under /tmp are present.

[Where problems could occur]

This is a code that has not previously been used on 20.04 and thus
could trigger new bugs. It has been used for since jammy though
without major issues.

A. The service itself

The service shouldn't be active unless it's needed. If you don't have ubuntu
advantage nor adsys configured check that the service is not loaded.
The service should low on resource usage, check that it's the case by
checking the RAM and CPU consumption.

B. Software-properties

The Ubuntu Pro tab didn't exist before so there should be no
regression possible there due to the service. The livepatch enablement
is handled through the service as part of UA now so check that
livepatch is correctly working still on upgraded systems

C. Adsys (focal)

The behaviour change in adsys should be limited to enabling features
which weren't available in focal before but we should ensure those are
correctly working and not providing a buggy user experience

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-desktop-daemon/+bug/1980781/+subscriptions

[Desktop-packages] [Bug 1917941] Re: System-config-printer keeps asking for network printer credentials

2022-09-15 Thread Robert

Storing the password from printer system dialog was running well for me
with ubuntu 20.04 lts.

Now, with ubuntu 22.04 lts the dialog is looking the same: with the
'remember password' checkbox. But, the password will be not stored any
more.

The dialog appears every time you print, regardless of whether you save
the password.

I have tested the behavior with a newly installed ubuntu 20.04 and
22.04. I printed from firefox with the printer system dialog.

Any ideas how to make this work again?

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

Title:
  System-config-printer keeps asking for network printer credentials

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

Bug description:
  Hello.

  I think I found a small bug in the printing process of Xubuntu
  20.04.02 LTS. I have a networked laser printer (Xerox Phaser 3250)
  that requires username/password credentials to print. The device is
  present in the CUPS page (see the Printers page in
  http://localhost:631) and uses the IPP protocol set to
  "ipp://192.168.1.10:631/ipp" URI. It is also visible in the system-
  config-printer window (XFCE Start button => Settings => Printers) and
  is set as default printer. The printer username/password are different
  than my PC username/password.

  Anyway, I noticed that the OS will sometimes pester me to enter the
  same credentials each time I try to print something. I recall the
  printing authorization window does have a "Remember password" checkbox
  that seemingly does nothing. Now why I am mentioning that this happens
  only sometimes? It's because I noticed that different programs will
  use different authorization windows to get printer credentials. For
  example, Mousepad will try to get credentials by using a CUPS popup
  dialog (I think). LibreOffice seems to popup its own small password
  entry window. This bug only applies to the cases where the printing is
  done via system-config-printer that uses its own authorization dialog.
  The printing works fine after credentials are entered though.

  So, after a short debug session I managed to narrow down the problem
  to this file: /usr/share/system-config-printer/jobviewer.py. I ran the
  applet.py and scp-dbus-service.py with the --debug option from command
  line to get some extra debug messages. Printing from Mousepad did not
  trigger any debug messages, but it did bring up the printing
  authorization dialog regardless. Like I've previously stated, Mousepad
  seems to use a different auth dialog, and I've verified (via seahorse)
  that this dialog works properly because it correctly stores the
  credentials into the keyring, and, if the Remember password checkbox
  is ticked, remembers them next time I try to print something. The
  problem only applies to the auth dialog triggered from jobviewer.py of
  system-config-printer. I managed to trigger the jobviewer auth dialog
  by trying to print something in LibreOffice Writer and then hitting
  Cancel in the small window that pops up. This will then trigger the
  *proper* jobviewer.py auth window to show up. It also triggers upon
  boot when there is something queued to be printed.

  It can also be reliably triggered queueing a print job, killing 
scp-dbus-service.py and applet.py and re-running them in this order:
  1) /usr/share/system-config-printer/scp-dbus-service.py --debug
  2) /usr/share/system-config-printer/applet.py --debug

  
  Though this jobviewer.py auth dialog will successfully save the printer 
credentials to the keyring, if the checkbox is ticked (verified with Seahorse), 
it will fail to read them next time, assume the credentials are missing, and 
ask the user to enter them. The error appears to happen in jobviewer.py:

  Line 1056: search_obj = ItemSearch(service, attrs)

  This line causes the following error to appear in the terminal:
  GLib-GIO-CRITICAL **: 19:28:31.663: g_dbus_connection_call_internal: 
assertion 'G_IS_DBUS_CONNECTION (connection)' failed

  The call fails to fetch any credentials and instead returns an empty
  result. I've written a short python script (see test.py) that
  reproduces the issue and triggers the same error.

  
  Related libsecret documentation:
  https://developer.gnome.org/libsecret/0.20/

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: system-config-printer 1.5.12-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CupsErrorLog:
   
  CurrentDesktop: XFCE
  Date: Fri Mar  5 19:34:54 2021
  InstallationDate: Installed on 2020-01-20 (409 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Phaser-3250: ipp://192.168.1.10:631/ipp

[Desktop-packages] [Bug 1987342] [NEW] package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: installed nvidia-340 package post-installation script subprocess returned error exit statu

2022-08-22 Thread Robert Simpson

Public bug reported:

This was an automated message during an upgrade:

package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade:
installed nvidia-340 package post-installation script subprocess
returned error exit status 10

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-340 340.108-0ubuntu5.20.04.2
ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Aug 22 20:09:15 2022
ErrorMessage: installed nvidia-340 package post-installation script subprocess 
returned error exit status 10
InstallationDate: Installed on 2021-09-10 (345 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.9
SourcePackage: nvidia-graphics-drivers-340
Title: package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: 
installed nvidia-340 package post-installation script subprocess returned error 
exit status 10
UpgradeStatus: Upgraded to focal on 2022-08-22 (0 days ago)

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


** Tags: amd64 apport-package focal third-party-packages

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

Title:
  package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade:
  installed nvidia-340 package post-installation script subprocess
  returned error exit status 10

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

Bug description:
  This was an automated message during an upgrade:

  package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade:
  installed nvidia-340 package post-installation script subprocess
  returned error exit status 10

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: nvidia-340 340.108-0ubuntu5.20.04.2
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Aug 22 20:09:15 2022
  ErrorMessage: installed nvidia-340 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2021-09-10 (345 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: 
installed nvidia-340 package post-installation script subprocess returned error 
exit status 10
  UpgradeStatus: Upgraded to focal on 2022-08-22 (0 days ago)

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


-- 
Mailing list: https://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 1987137] Re: Migrating chromium-browser to core22 has libwayland-client0 issues

2022-08-22 Thread Robert P. J. Day

Thanks, I'll check it out.

On Mon, Aug 22, 2022 at 9:50 AM Olivier Tilloy <1987...@bugs.launchpad.net>
wrote:

> This upstream bug seems relevant:
> https://bugs.chromium.org/p/chromium/issues/detail?id=1340181
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1987137
>
> Title:
>   Migrating chromium-browser to core22 has libwayland-client0 issues
>
> Status in chromium-browser package in Ubuntu:
>   New
>
> Bug description:
>   Following on an earlier bug report that related to simple core22
>   migration for chromium-browser, here is a blocker that I don't know
>   how to deal with.
>
>   After checking out the core22 branch from
>   git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
>   (which already contains the early, easy migration commits), doing a
>   build eventually generates (snippet here):
>
>   2022-08-19 20:15:05.809 :: In file included from
> ../../third_party/wayland/src/src/wayland-client.h:40:
>   2022-08-19 20:15:05.809 ::
> /usr/include/wayland-client-protocol.h:1038:13: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.809 :: callback =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>   2022-08-19 20:15:05.809 ::^
>   2022-08-19 20:15:05.809 ::
> /usr/include/wayland-client-protocol.h:1062:13: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: registry =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>   2022-08-19 20:15:05.810 ::^
>   2022-08-19 20:15:05.810 ::
> /usr/include/wayland-client-protocol.h:1175:7: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_registry,
>   2022-08-19 20:15:05.810 ::  ^
>   2022-08-19 20:15:05.810 ::
> /usr/include/wayland-client-protocol.h:1291:7: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_compositor,
>
>   and lots more of the same; it seems pretty clear that the relevant
>   wayland library is simply not new enough, and I don't know what to
>   add/modify to add core22 support to the mix, so I am open to
>   suggestions.
>
>   I do notice the file
>
> parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json,
>   which contains package version manifests for various distros, but not
>   Ubuntu 22.04, so I'm *guessing* that might need enhancement. But
>   that's just a guess.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1987137/+subscriptions
>
>

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

Title:
  Migrating chromium-browser to core22 has libwayland-client0 issues

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Following on an earlier bug report that related to simple core22
  migration for chromium-browser, here is a blocker that I don't know
  how to deal with.

  After checking out the core22 branch from
  git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
  (which already contains the early, easy migration commits), doing a
  build eventually generates (snippet here):

  2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
  2022-08-19 20:15:05.809 ::^
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
  2022-08-19 20:15:05.810 ::^
  2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_registry,
  2022-08-19 20:15:05.810 ::  ^
  2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1291:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_compositor,

  and lots more of the same; it seems pretty clear that the relevant
  wayland library is simply not new enough, and I don't know what to
  add/modify to add core22 support to the mix, so I am open to
  suggestions.

  I do notice the file

Re: [Desktop-packages] [Bug 1987137] Re: Migrating chromium-browser to core22 has libwayland-client0 issues

2022-08-22 Thread Robert P. J. Day

OK, I'll take a look at that when time permits.

On Mon, Aug 22, 2022 at 8:36 AM Nathan Teodosio <1987...@bugs.launchpad.net>
wrote:

> > Can I adjust snapcraft.yaml to override 1.20.0 and specifically
> request 1.18.0?
>
> We used override-build to get newer versions of Libva:
> https://git.launchpad.net/~nteodosio/chromium-
> browser/tree/snapcraft.yaml?h=hwacc#n362
>
> I wonder if you could do the same for libwayland-client0, but this could
> be more difficult if it is in a dependency tree...
>
> > Or maybe I can check if there is a development version of chromium
> that has already moved up to 1.20.0.
>
> According to that README file, I would try the "To import a new snapshot
> of wayland:" instructions with git checkout 1.20.0.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1987137
>
> Title:
>   Migrating chromium-browser to core22 has libwayland-client0 issues
>
> Status in chromium-browser package in Ubuntu:
>   New
>
> Bug description:
>   Following on an earlier bug report that related to simple core22
>   migration for chromium-browser, here is a blocker that I don't know
>   how to deal with.
>
>   After checking out the core22 branch from
>   git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
>   (which already contains the early, easy migration commits), doing a
>   build eventually generates (snippet here):
>
>   2022-08-19 20:15:05.809 :: In file included from
> ../../third_party/wayland/src/src/wayland-client.h:40:
>   2022-08-19 20:15:05.809 ::
> /usr/include/wayland-client-protocol.h:1038:13: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.809 :: callback =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>   2022-08-19 20:15:05.809 ::^
>   2022-08-19 20:15:05.809 ::
> /usr/include/wayland-client-protocol.h:1062:13: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: registry =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>   2022-08-19 20:15:05.810 ::^
>   2022-08-19 20:15:05.810 ::
> /usr/include/wayland-client-protocol.h:1175:7: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_registry,
>   2022-08-19 20:15:05.810 ::  ^
>   2022-08-19 20:15:05.810 ::
> /usr/include/wayland-client-protocol.h:1291:7: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_compositor,
>
>   and lots more of the same; it seems pretty clear that the relevant
>   wayland library is simply not new enough, and I don't know what to
>   add/modify to add core22 support to the mix, so I am open to
>   suggestions.
>
>   I do notice the file
>
> parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json,
>   which contains package version manifests for various distros, but not
>   Ubuntu 22.04, so I'm *guessing* that might need enhancement. But
>   that's just a guess.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1987137/+subscriptions
>
>

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

Title:
  Migrating chromium-browser to core22 has libwayland-client0 issues

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Following on an earlier bug report that related to simple core22
  migration for chromium-browser, here is a blocker that I don't know
  how to deal with.

  After checking out the core22 branch from
  git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
  (which already contains the early, easy migration commits), doing a
  build eventually generates (snippet here):

  2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
  2022-08-19 20:15:05.809 ::^
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
  2022-08-19 20:15:05.810 ::^
  2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_registry,
  2022-08-19

Re: [Desktop-packages] [Bug 1987137] Re: Migrating chromium-browser to core22 has libwayland-client0 issues

2022-08-22 Thread Robert P. J. Day

Well, yes, that would be the problem. What would be the for-the-moment
hacky workaround (if any)? Can I adjust snapcraft.yaml to override 1.20.0
and specifically request 1.18.0? Or maybe I can check if there is a
development version of chromium that has already moved up to 1.20.0. This
is not a high priority, it would just be nice to have.

On Mon, Aug 22, 2022 at 5:46 AM Olivier Tilloy <1987...@bugs.launchpad.net>
wrote:

>
> parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json
> isn't used by the snap build process, so that's not the right thing to
> look at.
>
> There appears to be an incompatibility between the version of libwayland
> in Ubuntu 22.04 (1.20.0) and the version vendored into the chromium
> source tree (1.18.0 according to
>
> https://source.chromium.org/chromium/chromium/src/+/main:third_party/wayland/README.chromium
> ).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1987137
>
> Title:
>   Migrating chromium-browser to core22 has libwayland-client0 issues
>
> Status in chromium-browser package in Ubuntu:
>   New
>
> Bug description:
>   Following on an earlier bug report that related to simple core22
>   migration for chromium-browser, here is a blocker that I don't know
>   how to deal with.
>
>   After checking out the core22 branch from
>   git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
>   (which already contains the early, easy migration commits), doing a
>   build eventually generates (snippet here):
>
>   2022-08-19 20:15:05.809 :: In file included from
> ../../third_party/wayland/src/src/wayland-client.h:40:
>   2022-08-19 20:15:05.809 ::
> /usr/include/wayland-client-protocol.h:1038:13: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.809 :: callback =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>   2022-08-19 20:15:05.809 ::^
>   2022-08-19 20:15:05.809 ::
> /usr/include/wayland-client-protocol.h:1062:13: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: registry =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>   2022-08-19 20:15:05.810 ::^
>   2022-08-19 20:15:05.810 ::
> /usr/include/wayland-client-protocol.h:1175:7: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_registry,
>   2022-08-19 20:15:05.810 ::  ^
>   2022-08-19 20:15:05.810 ::
> /usr/include/wayland-client-protocol.h:1291:7: error: use of undeclared
> identifier 'wl_proxy_marshal_flags'
>   2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_compositor,
>
>   and lots more of the same; it seems pretty clear that the relevant
>   wayland library is simply not new enough, and I don't know what to
>   add/modify to add core22 support to the mix, so I am open to
>   suggestions.
>
>   I do notice the file
>
> parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json,
>   which contains package version manifests for various distros, but not
>   Ubuntu 22.04, so I'm *guessing* that might need enhancement. But
>   that's just a guess.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1987137/+subscriptions
>
>

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

Title:
  Migrating chromium-browser to core22 has libwayland-client0 issues

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Following on an earlier bug report that related to simple core22
  migration for chromium-browser, here is a blocker that I don't know
  how to deal with.

  After checking out the core22 branch from
  git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
  (which already contains the early, easy migration commits), doing a
  build eventually generates (snippet here):

  2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
  2022-08-19 20:15:05.809 ::^
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
  2022-08-19 20:15:05.810 ::^
  2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier

[Desktop-packages] [Bug 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake

2022-08-21 Thread Robert Rongen

Solved by executing amixer -q -D pulse sset Master toggle
https://askubuntu.com/a/1341471

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

Title:
  Pulseaudio breaks HDMI audio on sleep/wake

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs
  with pulseaudio after putting my system to sleep and then waking it
  up. these bugs aren't present on a fresh boot, only after resuming
  from sleep:

  - it forgets which sound output device it's set to, and always reverse to the 
motherboard's S/PDIF output.
  - I have two devices connected to my video card, one is a displayport 
monitor, and one is a home theater receiver via HDMI. it confuses the two, and 
randomly switches which device it thinks is capable of surround sound.
  - it sometimes refuses to switch to the correct audio device, and just resets 
any choice back to the internal S/PDIF, until the system is rebooted.

  as you can imagine, this a pretty frustrating state of affairs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.4
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa  3387 F pulseaudio
   /dev/snd/pcmC1D7p:   tessa  3387 F...m pulseaudio
   /dev/snd/controlC2:  tessa  3387 F pulseaudio
   /dev/snd/controlC0:  tessa  3387 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 22 18:38:42 2020
  InstallationDate: Installed on 2020-07-15 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: GRYPHON Z97
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx: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

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


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

[Desktop-packages] [Bug 1987137] Re: Migrating chromium-browser to core22 has libwayland-client0 issues

** Description changed:

  Following on an earlier bug report that related to simple core22
  migration for chromium-browser, here is a blocker that I don't know how
  to deal with.
  
  After checking out the core22 branch from
  git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22 (which
  already contains the early, easy migration commits), doing a build
  eventually generates (snippet here):
  
+ 2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:
+ 2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
+ 2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
+ 2022-08-19 20:15:05.809 ::^
+ 2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
+ 2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display,
+ 2022-08-19 20:15:05.810 ::^
+ 2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
+ 2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_registry,
+ 2022-08-19 20:15:05.810 ::  ^
+ 2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1291:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
+ 2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_compositor,
  
- 2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:  

- 2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  
- 2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display, 

- 2022-08-19 20:15:05.809 ::^   

   
- 2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  
- 2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display, 

- 2022-08-19 20:15:05.810 ::^   

   
- 2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
   
- 2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_registry,
  
- 2022-08-19 20:15:05.810 ::  ^ 

   
- 2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1291:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
   
- 2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_compositor, 
+ and lots more of the same; it seems pretty clear that the relevant
+ wayland library is simply not new enough, and I don't know what to
+ add/modify to add core22 support to the mix, so I am open to
+ suggestions.
  
- 
- and lots more of the same; it seems pretty clear that the relevant wayland 
library is simply not new enough, and I don't know what to add/modify to add 
core22 support to the mix, so I am open to suggestions.
+ I do notice the file
+ parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json,
+ which contains package version manifests for various distros, but not
+ Ubuntu 22.04, so I'm *guessing* that might need enhancement. But that's
+ just a guess.

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

Title:
  Migrating chromium-browser to core22 has libwayland-client0 issues

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Following on an earlier bug report that related to simple core22
  migration for chromium-browser, here is a blocker that I don't know
  how to deal with.

  After checking out the core22 branch

[Desktop-packages] [Bug 1987137] [NEW] Migrating chromium-browser to core22 has libwayland-client0 issues

Public bug reported:

Following on an earlier bug report that related to simple core22
migration for chromium-browser, here is a blocker that I don't know how
to deal with.

After checking out the core22 branch from
git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22 (which
already contains the early, easy migration commits), doing a build
eventually generates (snippet here):


2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:  

2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  
2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display, 

2022-08-19 20:15:05.809 ::^ 

 
2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  
2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display, 

2022-08-19 20:15:05.810 ::^ 

 
2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
   
2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct wl_proxy 
*) wl_registry, 
 
2022-08-19 20:15:05.810 ::  ^   

 
2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1291:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
   
2022-08-19 20:15:05.810 :: id = wl_proxy_marshal_flags((struct wl_proxy 
*) wl_compositor, 


and lots more of the same; it seems pretty clear that the relevant wayland 
library is simply not new enough, and I don't know what to add/modify to add 
core22 support to the mix, so I am open to suggestions.

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

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

Title:
  Migrating chromium-browser to core22 has libwayland-client0 issues

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Following on an earlier bug report that related to simple core22
  migration for chromium-browser, here is a blocker that I don't know
  how to deal with.

  After checking out the core22 branch from
  git+ssh://git.launchpad.net/~chromium-core22/+git/chromium-core22
  (which already contains the early, easy migration commits), doing a
  build eventually generates (snippet here):

  
  2022-08-19 20:15:05.809 :: In file included from 
../../third_party/wayland/src/src/wayland-client.h:40:  

  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1038:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  
  2022-08-19 20:15:05.809 :: callback = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display, 

  2022-08-19 20:15:05.809 ::^   

   
  2022-08-19 20:15:05.809 :: /usr/include/wayland-client-protocol.h:1062:13: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
  
  2022-08-19 20:15:05.810 :: registry = wl_proxy_marshal_flags((struct 
wl_proxy *) wl_display, 

  2022-08-19 20:15:05.810 ::^   

   
  2022-08-19 20:15:05.810 :: /usr/include/wayland-client-protocol.h:1175:7: 
error: use of undeclared identifier 'wl_proxy_marshal_flags'
   
  2022-08-19

[Desktop-packages] [Bug 1986922] Re: snapcraft build fails on second run as "ln -s libdrm.pc libdrm-uninstalled.pc" already done

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

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

Title:
  snapcraft build fails on second run as "ln -s libdrm.pc libdrm-
  uninstalled.pc" already done

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  I'm trying to migrate the chromium browser snapcraft.yaml file to
  core22 and Snapcraft 7 and, after a build error on the first test
  (more on that later), I cleaned and re-ran the build to make sure the
  build error was reproducible, and got:

  ... big snip ...
  2022-08-18 08:50:45.224 :: + OUT=out/Release  
 
  2022-08-18 08:50:45.224 :: + mkdir -p out/Release 
 
  2022-08-18 08:50:45.243 :: + cp 
/root/snaps/snap-from-source/stage/build/args.gn out/Release/  
  2022-08-18 08:50:45.259 :: + '[' amd64 = armhf ']'
 
  2022-08-18 08:50:45.260 :: + '[' amd64 = armhf ']'
 
  2022-08-18 08:50:45.260 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig   
 
  2022-08-18 08:50:45.260 :: + ln -s libdrm.pc libdrm-uninstalled.pc
 
  2022-08-18 08:50:45.269 :: ln: failed to create symbolic link 
'libdrm-uninstalled.pc': File exists 
  2022-08-18 08:50:45.431 'override-build' in part 'chromium' failed with code 
1.
  Review the scriptlet and make sure it's correct. 

  Naturally, since that symlink had been created during the first run
  (in a persistent 22.04 LXD container), it was still there for the
  second run. Operations like that should be idempotent so one can run
  multiple builds.

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


-- 
Mailing list: https://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 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

Ok, thanks.

On Fri, Aug 19, 2022 at 8:10 AM Nathan Teodosio <1986...@bugs.launchpad.net>
wrote:

> > Perhaps one should create a core 22 branch where I can submit my
> changes.
>
> I think that is only possible with a team. See if you can push to
> https://code.launchpad.net/~chromium-core22/+git/chromium-core22. If
> yes, just force push your current work to it.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1986925
>
> Title:
>   [snap] Trying to build chromium snap for core22: pkg-config fails.
>
> Status in chromium-browser package in Ubuntu:
>   New
>
> Bug description:
>   I checked out the "dev" branch of chromium-browser from launchpad and
>   did what seemed necessary to update snapcraft.yaml to build with
>   snapcraft 7 for core22. The only change of any significance was to
>   change the extension from "gnome-3-38" to the core22-specific "gnome"
>   extension. I started the build and it ran for quite some time (in a
>   persistent 22.04 LXD container) until:
>
>   2022-08-18 09:11:00.869 :: + OUT=out/Release
>
>   2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>
>   2022-08-18 09:11:00.888 :: + cp /root/snaps/snap-from-source/stage/build/
> args.gn out/Release/
>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
>   2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>
>   2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>
>   2022-08-18 09:11:00.935 :: + cd -
>
>   2022-08-18 09:11:00.935 ::
> /root/snaps/snap-from-source/parts/chromium/build
>
>   2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>
>   2022-08-18 09:11:07.112 :: ERROR at
> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
> code.
>
>   2022-08-18 09:11:07.112 :: pkgresult =
> exec_script(pkg_config_script, args, "value")
>   2022-08-18 09:11:07.113 :: ^--
>
>   2022-08-18 09:11:07.113 :: Current dir:
> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
>   2022-08-18 09:11:07.113 :: Command: python3
> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
>
>   2022-08-18 09:11:07.113 :: Returned 1.
>
>   2022-08-18 09:11:07.113 :: stderr:
>
>   2022-08-18 09:11:07.113 ::
>
>   2022-08-18 09:11:07.113 :: Could not run pkg-config.
>
>   2022-08-18 09:11:07.113 ::
>
>   2022-08-18 09:11:07.113 :: See
> //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
>   2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
>
>   2022-08-18 09:11:07.113 :: ^--
>
>   2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file
> to be included.
>   2022-08-18 09:11:07.114 ::
>  "//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
>   2022-08-18 09:11:07.114 ::
>  ^---
>   2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with
> code 1.
>   Review the scriptlet and make sure it's correct.
>
>   I verified that the pkg-config utility is installed in the container;
>   I can only suspect that this error is related to switching to the
>   core22 gnome extension. I am open to suggestions.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions
>
>

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

Title:
  [snap] Trying to build chromium snap for core22: pkg-config fails.

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I checked out the "dev" branch of chromium-browser from launchpad and
  did what seemed necessary to update snapcraft.yaml to build with
  snapcraft 7 for core22. The only change of any significance was to
  change the extension from "gnome-3-38" to the core22-specific "gnome"
  extension. I started the build and it ran for quite some time (in a
  persistent 22.04 LXD container) until:

  2022-08-18 09:11:00.869 :: + OUT=out/Release  
 
  2022-08-18 09:11:00.869 :: + mkdir -p out/Release 
 
  2022-08-18 09:11:00.888 :: + cp 
/root/snaps/snap-from-source/stage/build/args.gn out/Release/  
  2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
 
  2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
 
  2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig   
 
  2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

My interest in this is that I'm stress testing migrating snaps to core
22/snapcraft 7 as part of the update for the Snapcraft 101 course, and when
I asked my team for an example of a snap that would be challenging to
migrate, one of them immediately suggested chromium, so that's why I'm
working on this. So far, the necessary changes were fairly minimal, until
this issue, which I don't know what to do with.

Perhaps one should create a core 22 branch where I can submit my
changes.

In terms of getting more output, with Snapcraft 7, I'm running "snapcraft
--verbosity=trace" for tons of output.

Anyway, this wl_proxy* stuff is the current bottleneck.

On Fri, Aug 19, 2022 at 7:25 AM Nathan Teodosio <1986...@bugs.launchpad.net>
wrote:

> For a matter of fact, wl_proxy_marshal_flags is declared in wayland-
> client-core.h, provided by libwayland-dev, which is specified in the
> build-packages of chromium in snapcraft.yaml. As long as it is version
> >=1.20, I'd think it should work, but reality shows otherwise.
>
> I'm trying to build the snap too so I can see full logs, but weirdly
> they are much less verbose than what I'm used to (e.g.
>
> https://launchpadlibrarian.net/618908242/buildlog_snap_ubuntu_jammy_amd64_chromium-
> browser-core22_BUILDING.txt.gz
> ),
> and I don't want to believe that would
> be caused by a mere switch to core22.
>
> > P.S. Thanks for your patience with all of this.
>
> No such thing, it's a pleasure :). This is both useful and a great
> chance to better understand snaps.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1986925
>
> Title:
>   [snap] Trying to build chromium snap for core22: pkg-config fails.
>
> Status in chromium-browser package in Ubuntu:
>   New
>
> Bug description:
>   I checked out the "dev" branch of chromium-browser from launchpad and
>   did what seemed necessary to update snapcraft.yaml to build with
>   snapcraft 7 for core22. The only change of any significance was to
>   change the extension from "gnome-3-38" to the core22-specific "gnome"
>   extension. I started the build and it ran for quite some time (in a
>   persistent 22.04 LXD container) until:
>
>   2022-08-18 09:11:00.869 :: + OUT=out/Release
>
>   2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>
>   2022-08-18 09:11:00.888 :: + cp /root/snaps/snap-from-source/stage/build/
> args.gn out/Release/
>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
>   2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>
>   2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>
>   2022-08-18 09:11:00.935 :: + cd -
>
>   2022-08-18 09:11:00.935 ::
> /root/snaps/snap-from-source/parts/chromium/build
>
>   2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>
>   2022-08-18 09:11:07.112 :: ERROR at
> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
> code.
>
>   2022-08-18 09:11:07.112 :: pkgresult =
> exec_script(pkg_config_script, args, "value")
>   2022-08-18 09:11:07.113 :: ^--
>
>   2022-08-18 09:11:07.113 :: Current dir:
> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
>   2022-08-18 09:11:07.113 :: Command: python3
> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
>
>   2022-08-18 09:11:07.113 :: Returned 1.
>
>   2022-08-18 09:11:07.113 :: stderr:
>
>   2022-08-18 09:11:07.113 ::
>
>   2022-08-18 09:11:07.113 :: Could not run pkg-config.
>
>   2022-08-18 09:11:07.113 ::
>
>   2022-08-18 09:11:07.113 :: See
> //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
>   2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
>
>   2022-08-18 09:11:07.113 :: ^--
>
>   2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file
> to be included.
>   2022-08-18 09:11:07.114 ::
>  "//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
>   2022-08-18 09:11:07.114 ::
>  ^---
>   2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with
> code 1.
>   Review the scriptlet and make sure it's correct.
>
>   I verified that the pkg-config utility is installed in the container;
>   I can only suspect that this error is related to switching to the
>   core22 gnome extension. I am open to suggestions.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions
>
>

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

Title:
  [snap] Trying

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

Last comment for the day ... from what little I've seen, it seems like it
might require defining a lengthy list of packages relative to 22.04 to
migrate this snap to 22.04. Or maybe I'm misreading it. In any event, I'd
still like to make this happen.

On Thu, Aug 18, 2022 at 3:56 PM Robert Day 
wrote:

> Actually, another part of my grep search produced the following, which
> seems to suggest that an older version of libwayland-client0 is being used:
>
>
> parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.mips64el:
> https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_mips64el.deb
>
> parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.arm64:
> https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_arm64.deb
>
> parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.i386:
> https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_i386.deb
>
> parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.armel:
> https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_armel.deb
>
> parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.mipsel:
> https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_mipsel.deb
>
> parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.arm:
> https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_armhf.deb
>
> parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.amd64:
> https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_amd64.deb
>
> At least that's the way I read it.
>
> rday
>
> On Thu, Aug 18, 2022 at 3:43 PM Robert Day 
> wrote:
>
>> A comprehensive grep includes the lines:
>>
>> parts/launcher/state/build:  - libwayland-client0=1.20.0-1
>> parts/va-drivers/state/build:  - libwayland-client0=1.20.0-1
>> parts/pipewire/state/build:  - libwayland-client0=1.20.0-1
>> parts/chromium-build/state/build:  - libwayland-client0=1.20.0-1
>> parts/manpage/state/build:  - libwayland-client0=1.20.0-1
>>
>> Oh, wait, there we
>> go: 
>> parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json
>> appears to be a version manifest that does not include anything for 22.04.
>> Does that sound like the problem?
>>
>> P.S. Thanks for your patience with all of this.
>>
>> On Thu, Aug 18, 2022 at 3:30 PM Nathan Teodosio <
>> 1986...@bugs.launchpad.net> wrote:
>>
>>> What is libwayland-client0 version in your logs? Focal has 1.18.0, but
>>>
>>> wayland-1.21.0/debian/libwayland-client0.symbols:
>>> wl_proxy_marshal_flags@Base 1.20.0
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https://bugs.launchpad.net/bugs/1986925
>>>
>>> Title:
>>>   [snap] Trying to build chromium snap for core22: pkg-config fails.
>>>
>>> Status in chromium-browser package in Ubuntu:
>>>   New
>>>
>>> Bug description:
>>>   I checked out the "dev" branch of chromium-browser from launchpad and
>>>   did what seemed necessary to update snapcraft.yaml to build with
>>>   snapcraft 7 for core22. The only change of any significance was to
>>>   change the extension from "gnome-3-38" to the core22-specific "gnome"
>>>   extension. I started the build and it ran for quite some time (in a
>>>   persistent 22.04 LXD container) until:
>>>
>>>   2022-08-18 09:11:00.869 :: + OUT=out/Release
>>>
>>>   2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>>>
>>>   2022-08-18 09:11:00.888 :: + cp
>>> /root/snaps/snap-from-source/stage/build/args.gn out/Release/
>>>
>>>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>>
>>>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>>
>>>   2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>>>
>>>   2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>>>
>>>   2022-08-18 09:11:00.935 :: + cd -
>>>
>>>   2022-08-18 09:11:00.935 ::
>>> /root/snaps

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

Actually, another part of my grep search produced the following, which
seems to suggest that an older version of libwayland-client0 is being used:

parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.mips64el:
https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_mips64el.deb
parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.arm64:
https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_arm64.deb
parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.i386:
https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_i386.deb
parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.armel:
https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_armel.deb
parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.mipsel:
https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_mipsel.deb
parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.arm:
https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_armhf.deb
parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.amd64:
https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_amd64.deb

At least that's the way I read it.

rday

On Thu, Aug 18, 2022 at 3:43 PM Robert Day 
wrote:

> A comprehensive grep includes the lines:
>
> parts/launcher/state/build:  - libwayland-client0=1.20.0-1
> parts/va-drivers/state/build:  - libwayland-client0=1.20.0-1
> parts/pipewire/state/build:  - libwayland-client0=1.20.0-1
> parts/chromium-build/state/build:  - libwayland-client0=1.20.0-1
> parts/manpage/state/build:  - libwayland-client0=1.20.0-1
>
> Oh, wait, there we
> go: 
> parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json
> appears to be a version manifest that does not include anything for 22.04.
> Does that sound like the problem?
>
> P.S. Thanks for your patience with all of this.
>
> On Thu, Aug 18, 2022 at 3:30 PM Nathan Teodosio <
> 1986...@bugs.launchpad.net> wrote:
>
>> What is libwayland-client0 version in your logs? Focal has 1.18.0, but
>>
>> wayland-1.21.0/debian/libwayland-client0.symbols:
>> wl_proxy_marshal_flags@Base 1.20.0
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1986925
>>
>> Title:
>>   [snap] Trying to build chromium snap for core22: pkg-config fails.
>>
>> Status in chromium-browser package in Ubuntu:
>>   New
>>
>> Bug description:
>>   I checked out the "dev" branch of chromium-browser from launchpad and
>>   did what seemed necessary to update snapcraft.yaml to build with
>>   snapcraft 7 for core22. The only change of any significance was to
>>   change the extension from "gnome-3-38" to the core22-specific "gnome"
>>   extension. I started the build and it ran for quite some time (in a
>>   persistent 22.04 LXD container) until:
>>
>>   2022-08-18 09:11:00.869 :: + OUT=out/Release
>>
>>   2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>>
>>   2022-08-18 09:11:00.888 :: + cp
>> /root/snaps/snap-from-source/stage/build/args.gn out/Release/
>>
>>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>
>>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>
>>   2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>>
>>   2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>>
>>   2022-08-18 09:11:00.935 :: + cd -
>>
>>   2022-08-18 09:11:00.935 ::
>> /root/snaps/snap-from-source/parts/chromium/build
>>
>>   2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>>
>>   2022-08-18 09:11:07.112 :: ERROR at
>> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
>> code.
>>
>>   2022-08-18 09:11:07.112 :: pkgresult =
>> exec_script(pkg_config_script, args, "value")
>>   2022-08-18 09:11:07.113 :: ^--
>>
>>   2022-08-18 09:11:07.113 :: Current dir:
>> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
>>   2022-08-18 09:11:07.113 :: Command: python3
>> /root/snaps/snap-from-source/parts/chromium/bui

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

A comprehensive grep includes the lines:

parts/launcher/state/build:  - libwayland-client0=1.20.0-1
parts/va-drivers/state/build:  - libwayland-client0=1.20.0-1
parts/pipewire/state/build:  - libwayland-client0=1.20.0-1
parts/chromium-build/state/build:  - libwayland-client0=1.20.0-1
parts/manpage/state/build:  - libwayland-client0=1.20.0-1

Oh, wait, there we
go: 
parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json
appears to be a version manifest that does not include anything for 22.04.
Does that sound like the problem?

P.S. Thanks for your patience with all of this.

On Thu, Aug 18, 2022 at 3:30 PM Nathan Teodosio <1986...@bugs.launchpad.net>
wrote:

> What is libwayland-client0 version in your logs? Focal has 1.18.0, but
>
> wayland-1.21.0/debian/libwayland-client0.symbols:
> wl_proxy_marshal_flags@Base 1.20.0
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1986925
>
> Title:
>   [snap] Trying to build chromium snap for core22: pkg-config fails.
>
> Status in chromium-browser package in Ubuntu:
>   New
>
> Bug description:
>   I checked out the "dev" branch of chromium-browser from launchpad and
>   did what seemed necessary to update snapcraft.yaml to build with
>   snapcraft 7 for core22. The only change of any significance was to
>   change the extension from "gnome-3-38" to the core22-specific "gnome"
>   extension. I started the build and it ran for quite some time (in a
>   persistent 22.04 LXD container) until:
>
>   2022-08-18 09:11:00.869 :: + OUT=out/Release
>
>   2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>
>   2022-08-18 09:11:00.888 :: + cp /root/snaps/snap-from-source/stage/build/
> args.gn out/Release/
>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>
>   2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>
>   2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>
>   2022-08-18 09:11:00.935 :: + cd -
>
>   2022-08-18 09:11:00.935 ::
> /root/snaps/snap-from-source/parts/chromium/build
>
>   2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>
>   2022-08-18 09:11:07.112 :: ERROR at
> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit
> code.
>
>   2022-08-18 09:11:07.112 :: pkgresult =
> exec_script(pkg_config_script, args, "value")
>   2022-08-18 09:11:07.113 :: ^--
>
>   2022-08-18 09:11:07.113 :: Current dir:
> /root/snaps/snap-from-source/parts/chromium/build/out/Release/
>   2022-08-18 09:11:07.113 :: Command: python3
> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py
> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb
>
>   2022-08-18 09:11:07.113 :: Returned 1.
>
>   2022-08-18 09:11:07.113 :: stderr:
>
>   2022-08-18 09:11:07.113 ::
>
>   2022-08-18 09:11:07.113 :: Could not run pkg-config.
>
>   2022-08-18 09:11:07.113 ::
>
>   2022-08-18 09:11:07.113 :: See
> //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called.
>   2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") {
>
>   2022-08-18 09:11:07.113 :: ^--
>
>   2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file
> to be included.
>   2022-08-18 09:11:07.114 ::
>  "//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan",
>   2022-08-18 09:11:07.114 ::
>  ^---
>   2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with
> code 1.
>   Review the scriptlet and make sure it's correct.
>
>   I verified that the pkg-config utility is installed in the container;
>   I can only suspect that this error is related to switching to the
>   core22 gnome extension. I am open to suggestions.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions
>
>

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

Title:
  [snap] Trying to build chromium snap for core22: pkg-config fails.

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I checked out the "dev" branch of chromium-browser from launchpad and
  did what seemed necessary to update snapcraft.yaml to build with
  snapcraft 7 for core22. The only change of any significance was to
  change the extension from "gnome-3-38" to the core22-specific "gnome"
  extension. I started the build and it ran for quite some time (in a
  persistent 22.04 LXD container) until:

  2022-08-18 09:11:00.869 :: + OUT=out/Release  
 
  2022-08-18 09:11:00.869 :: + mkdir -p out/Release 
 
  2022-08-18 09:11:00.888 :: + cp

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.

This appears to describe precisely this issue:

https://github.com/libsdl-org/SDL/pull/5092

On Thu, Aug 18, 2022 at 1:06 PM Robert Day 
wrote:

> Yup, same errors ... lots of "wl "and "marshal" undefined references.
> Here's just a small sample:
>
> 2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1038:13:
> error: use of undeclared identifier 'wl_proxy_marshal_flags'
>
>
> 2022-08-18 17:03:57.646 :: callback =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>
>
> 2022-08-18 17:03:57.646 ::^
>
>
>
> 2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1062:13:
> error: use of undeclared identifier 'wl_proxy_marshal_flags'
>
>
> 2022-08-18 17:03:57.646 :: registry =
> wl_proxy_marshal_flags((struct wl_proxy *) wl_display,
>
>
> 2022-08-18 17:03:57.646 ::^
>
>
>
> 2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1175:7:
> error: use of undeclared identifier 'wl_proxy_marshal_flags'
>
>
> 2022-08-18 17:03:57.646 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_registry,
>
>
> 2022-08-18 17:03:57.646 ::  ^
>
>
>
> 2022-08-18 17:03:57.646 :: /usr/include/wayland-client-protocol.h:1291:7:
> error: use of undeclared identifier 'wl_proxy_marshal_flags'
>
>
> 2022-08-18 17:03:57.646 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_compositor,
>
>
> 2022-08-18 17:03:57.647 ::  ^
>
>
>
> 2022-08-18 17:03:57.647 :: /usr/include/wayland-client-protocol.h:1307:7:
> error: use of undeclared identifier 'wl_proxy_marshal_flags'
>
>
> 2022-08-18 17:03:57.647 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_compositor,
>
>
> 2022-08-18 17:03:57.647 ::  ^
>
>
>
> 2022-08-18 17:03:57.647 :: /usr/include/wayland-client-protocol.h:1371:7:
> error: use of undeclared identifier 'wl_proxy_marshal_flags'
>
>
> 2022-08-18 17:03:57.647 :: id = wl_proxy_marshal_flags((struct
> wl_proxy *) wl_shm_pool,
>
>
> 2022-08-18 17:03:57.647 ::  ^
>
>
> On Thu, Aug 18, 2022 at 1:04 PM Robert Day 
> wrote:
>
>> That's what I did, but that's also when I got the errors I included in my
>> previous comment. I'm rebuilding just to make sure those errors are
>> reproducible.
>>
>> On Thu, Aug 18, 2022 at 12:45 PM Nathan Teodosio <
>> 1986...@bugs.launchpad.net> wrote:
>>
>>> > but that appears to be because this newer gnome does not supply such
>>> an executable; there is no "pkg-config" under
>>> /snap/gnome-42-2204/current/usr/bin/, as I assume there must have been
>>> under gnome-3-38.
>>>
>>> Oh, so this time pkg-config in build-packages could solve it? Probably
>>> you will have to remove the pkg_config line from args.gn, though.
>>>
>>> --
>>> You received this bug notification because you are subscribed to the bug
>>> report.
>>> https://bugs.launchpad.net/bugs/1986925
>>>
>>> Title:
>>>   [snap] Trying to build chromium snap for core22: pkg-config fails.
>>>
>>> Status in chromium-browser package in Ubuntu:
>>>   New
>>>
>>> Bug description:
>>>   I checked out the "dev" branch of chromium-browser from launchpad and
>>>   did what seemed necessary to update snapcraft.yaml to build with
>>>   snapcraft 7 for core22. The only change of any significance was to
>>>   change the extension from "gnome-3-38" to the core22-specific "gnome"
>>>   extension. I started the build and it ran for quite some time (in a
>>>   persistent 22.04 LXD container) until:
>>>
>>>   2022-08-18 09:11:00.869 :: + OUT=out/Release
>>>
>>>   2022-08-18 09:11:00.869 :: + mkdir -p out/Release
>>>
>>>   2022-08-18 09:11:00.888 :: + cp
>>> /root/snaps/snap-from-source/stage/build/args.gn out/Release/
>>>
>>>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>>
>>>   2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']'
>>>
>>>   2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig
>>>
>>>   2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc
>>>
>>>   2022-08-18 09:11:00.935 :: + cd -
>>>
>>>   2022-08-18 09:11:00.935 ::
>>> /root/snaps/snap-from-source/parts/chromium/build
>>>
>>>   2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release
>>>
>>>   2022-0

Re: [Desktop-packages] [Bug 1986925] Re: [snap] Trying to build chromium snap for core22: pkg-config fails.