[Desktop-packages] [Bug 902661] Re: Chromium unsets preferred webbrowser

[Launchpad Bug Tracker]

[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Chromium unsets preferred webbrowser

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  I'm running XUbuntu 11.10 (actually Ubuntu 11.10 with the xubuntu
  packages installed on top).

  When I select Chromium to be my preferred web browser from
  settings->setting manager->preferred application, Chromium will be
  launched when I select Web Browser from the main pull-down menu.

  However, when Chromium starts, it produces a message stating "Chromium
  is not your default browser" (or words of that nature). When I select
  "yes", and then reopen preferred applications, Chromium is no longer
  selected as the default web browser.

  It would seem that Chromium doesn't understand how to interpret the
  default settings in xfce4 - or muddles them up when it tries to make
  itself the default browser.

  The work-around is easy - tell Chromium not to ask anymore, and don't
  allow it to set itself as the default browser (use preferred
  applications instead to select the preferred browser).

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: chromium-browser 15.0.874.106~r107270-0ubuntu0.11.10.1
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Sat Dec 10 19:44:50 2011
  Desktop-Session:
   DESKTOP_SESSION = xubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg
   XDG_DATA_DIRS = /usr/share/xubuntu:/usr/local/share/:/usr/share/:/usr/share
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to oneiric on 2011-12-03 (7 days ago)
  chromium-default: CHROMIUM_FLAGS=""

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/902661/+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 987468] Re: no link to the requested plugin

[Launchpad Bug Tracker]

[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  no link to the requested plugin

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  I load a site which requires a plugin to be viewed. I get the message about 
plugin requested but no link to the plugin itself.
  See attached screen shot.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 18.0.1025.151~r130497-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
  Uname: Linux 3.2.0-23-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: i386
  CasperVersion: 1.315
  ChromiumPrefs:
   browser/check_default_browser = True
   extensions/settings =
- 'ahfgeienlihckogmohjhadlkjgocpleb'
manifest/* = *undef*
  Date: Mon Apr 23 19:01:54 2012
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  LiveMediaBuild: Edubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/987468/+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 978635] Re: chromium-browser icon not working properly in Unity Launcher

[Launchpad Bug Tracker]

[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  chromium-browser icon not working properly in Unity Launcher

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  Expected Result:
  When you launch a session of Chromium the icon in the Unity Launcher should 
have a white arrow to the left of it to show a Chromium instance is running and 
when you click said icon it should switch to Chromium instead of opening a new 
session of Chromium.

  Actual Result: Chromium icon does not show existing chromium windows
  running and clicking it has behavior inconsistent with other apps.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 18.0.1025.151~r130497-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  ApportVersion: 2.0-0ubuntu5
  Architecture: amd64
  Date: Wed Apr 11 00:21:09 2012
  EcryptfsInUse: Yes
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120325)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  chromium-default: CHROMIUM_FLAGS=""

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/978635/+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 1987911] Re: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

[Launchpad Bug Tracker]

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package firefox 104.0+build3-0ubuntu0.20.04.1 failed to
  install/upgrade: new firefox package pre-installation script
  subprocess returned error exit status 1

Status in firefox package in Ubuntu:
  Expired

Bug description:
  eerror

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 104.0+build3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: aufs
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  europassistance   2340 F pulseaudio
   /dev/snd/controlC0:  europassistance   2340 F pulseaudio
  BuildID: 20220818191623
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  Date: Fri Aug 26 20:59:33 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  ForcedLayersAccel: False
  InstallationDate: Installed on 2022-03-09 (170 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  IpRoute:
   default via 192.168.1.254 dev wlp1s0 proto dhcp metric 600 
   169.254.0.0/16 dev br-b0b9255f7446 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   172.18.0.0/16 dev br-b0b9255f7446 proto kernel scope link src 172.18.0.1 
linkdown 
   192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.124 metric 
600
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to 
install/upgrade: new firefox package pre-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-08-26 (0 days ago)
  dmi.bios.date: 11/12/2021
  dmi.bios.release: 7.1
  dmi.bios.vendor: HP
  dmi.bios.version: T82 Ver. 01.07.01
  dmi.board.name: 8895
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 43.25.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 67.37
  dmi.modalias: 
dmi:bvnHP:bvrT82Ver.01.07.01:bd11/12/2021:br7.1:efr67.37:svnHP:pnHPEliteBook845G8NotebookPC:pvr:rvnHP:rn8895:rvrKBCVersion43.25.00:cvnHP:ct10:cvr:sku458Z6EA#ABF:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 845 G8 Notebook PC
  dmi.product.sku: 458Z6EA#ABF
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1987911/+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 1988437] Re: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1

[Launchpad Bug Tracker]

[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package firefox 104.0+build3-0ubuntu0.20.04.1 failed to
  install/upgrade: new firefox package pre-installation script
  subprocess returned error exit status 1

Status in firefox package in Ubuntu:
  Expired

Bug description:
  same as #1987911

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 104.0+build3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-125.141-generic 5.4.195
  Uname: Linux 5.4.0-125-generic x86_64
  NonfreeKernelModules: wl
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  matti  1806 F pulseaudio
   /dev/snd/controlC2:  matti  1806 F pulseaudio
   /dev/snd/controlC0:  matti  1806 F pulseaudio
   /dev/snd/controlC1:  matti  1806 F pulseaudio
  BuildID: 20220818191623
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  Date: Thu Sep  1 13:53:52 2022
  ErrorMessage: new firefox package pre-installation script subprocess returned 
error exit status 1
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-09-01 (1461 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 192.168.100.1 dev wlp7s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp7s0 scope link metric 1000 
   192.168.100.0/24 dev wlp7s0 proto kernel scope link src 192.168.100.10 
metric 600
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to 
install/upgrade: new firefox package pre-installation script subprocess 
returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2022-09-01 (0 days ago)
  dmi.bios.date: 02/24/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0FWKV7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd02/24/2014:svnDellInc.:pnVostro2520:pvrNotSpecified:rvnDellInc.:rn0FWKV7:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Vostro 2520
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1988437/+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 1995317] Re: (X11) New application window doesn't appear on a dock

[Bug Watch Updater]

** Changed in: dash-to-dock
   Status: Unknown => 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/1995317

Title:
  (X11) New application window doesn't appear on a dock

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

Bug description:
  Sometimes programs launch new windows and destroy old ones. Those new
  windows may not appear on dock until you launch some new windows,
  reload shell etc.

  I can give a reproducible example with LibreOffice (7.3.x, 7.4.x).
  Tested on Ubuntu 22.04 with both "Ubuntu Dock" and "Dash to Dock" v75

  Steps to reproduce
  1) Create simple CSV file with content
  "entity_id","type_id"
  2) Open it with LibreOffice Calc
  3) On "Text Import" dialog press "OK"
  4) "Text import" window closes, new LibreOffice window appears
  5) LibreOffice Calc icon is missing until you enter "Dash to Dock Settings", 
reload shell etc

  I wasn't able to reproduce this issue on a Wayland session and with
  the original dash

  Video demonstration attached bellow

  Upstream bug report: https://github.com/micheleg/dash-to-
  dock/issues/1867

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  1 03:12:13 2022
  InstallationDate: Installed on 2022-10-20 (11 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1995317/+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 1995320] [NEW] intermittent green static

[Kai Groner]

Public bug reported:

After upgrading from 22.04 to 22.10 I've been seeing some display
glitches.

- green static appears, usually when scrolling, regular sized green blocks, 
like giant pixels
- firefox not refreshing when full screen video plays (separate windows, 
separate screens)

I would guess I probably have the wrong package here, but there's no way
for me to tell if it's mesa, the kernel, gnome-shell, or something else.

Radeon 6700XT
Dual displays
Wayland

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 31 21:46:03 2022
DisplayManager: gdm3
InstallationDate: Installed on 2019-06-18 (1231 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 TERM=tmux-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago)

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


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

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

Title:
  intermittent green static

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrading from 22.04 to 22.10 I've been seeing some display
  glitches.

  - green static appears, usually when scrolling, regular sized green blocks, 
like giant pixels
  - firefox not refreshing when full screen video plays (separate windows, 
separate screens)

  I would guess I probably have the wrong package here, but there's no
  way for me to tell if it's mesa, the kernel, gnome-shell, or something
  else.

  Radeon 6700XT
  Dual displays
  Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 31 21:46:03 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-18 (1231 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1995320/+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 1995319] [NEW] Nautilus (Files program) window slides itself behind the programs-taskbar on left every once in a while.

[Joonas Höglund]

Public bug reported:

No further information.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: nautilus 1:43.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  1 03:44:58 2022
InstallationDate: Installed on 2021-06-07 (511 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
SourcePackage: nautilus
UpgradeStatus: Upgraded to kinetic on 2022-10-26 (6 days ago)
usr_lib_nautilus:
 file-roller   43.0-1
 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
 nautilus-share0.7.5-0.1

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


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

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

Title:
  Nautilus (Files program) window slides itself behind the programs-
  taskbar on left every once in a while.

Status in nautilus package in Ubuntu:
  New

Bug description:
  No further information.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: nautilus 1:43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  1 03:44:58 2022
  InstallationDate: Installed on 2021-06-07 (511 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to kinetic on 2022-10-26 (6 days ago)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
   nautilus-share0.7.5-0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1995319/+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 1995317] [NEW] (X11) New application window doesn't appear on a dock

[xalt7x]

Public bug reported:

Sometimes programs launch new windows and destroy old ones. Those new
windows may not appear on dock until you launch some new windows, reload
shell etc.

I can give a reproducible example with LibreOffice (7.3.x, 7.4.x).
Tested on Ubuntu 22.04 with both "Ubuntu Dock" and "Dash to Dock" v75

Steps to reproduce
1) Create simple CSV file with content
"entity_id","type_id"
2) Open it with LibreOffice Calc
3) On "Text Import" dialog press "OK"
4) "Text import" window closes, new LibreOffice window appears
5) LibreOffice Calc icon is missing until you enter "Dash to Dock Settings", 
reload shell etc

I wasn't able to reproduce this issue on a Wayland session and with the
original dash

Video demonstration attached bellow

Upstream bug report: https://github.com/micheleg/dash-to-
dock/issues/1867

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov  1 03:12:13 2022
InstallationDate: Installed on 2022-10-20 (11 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: dash-to-dock
 Importance: Unknown
 Status: Unknown

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


** Tags: amd64 apport-bug jammy

** Attachment added: "Demonstration of the issue"
   
https://bugs.launchpad.net/bugs/1995317/+attachment/5628152/+files/dash-to-dock-x11.webm

** Bug watch added: github.com/micheleg/dash-to-dock/issues #1867
   https://github.com/micheleg/dash-to-dock/issues/1867

** Also affects: dash-to-dock via
   https://github.com/micheleg/dash-to-dock/issues/1867
   Importance: Unknown
   Status: Unknown

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

Title:
  (X11) New application window doesn't appear on a dock

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

Bug description:
  Sometimes programs launch new windows and destroy old ones. Those new
  windows may not appear on dock until you launch some new windows,
  reload shell etc.

  I can give a reproducible example with LibreOffice (7.3.x, 7.4.x).
  Tested on Ubuntu 22.04 with both "Ubuntu Dock" and "Dash to Dock" v75

  Steps to reproduce
  1) Create simple CSV file with content
  "entity_id","type_id"
  2) Open it with LibreOffice Calc
  3) On "Text Import" dialog press "OK"
  4) "Text import" window closes, new LibreOffice window appears
  5) LibreOffice Calc icon is missing until you enter "Dash to Dock Settings", 
reload shell etc

  I wasn't able to reproduce this issue on a Wayland session and with
  the original dash

  Video demonstration attached bellow

  Upstream bug report: https://github.com/micheleg/dash-to-
  dock/issues/1867

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  1 03:12:13 2022
  InstallationDate: Installed on 2022-10-20 (11 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dash-to-dock/+bug/1995317/+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 1995313] [NEW] No sound with Pipewire - mod.rt: Can't find xdg-portal: (null)

[L30N4RD]

Public bug reported:

Pipewire is not porperly working, sound devices are listed in alsamixer,
aplay and system settings but there is no audio from the pc.

The only info i got is from journalctl is this output:

oct 31 19:33:09 leo-zenbook pipewire-pulse[1095]: mod.rt: Can't find 
xdg-portal: (null)
oct 31 19:33:09 leo-zenbook pipewire-pulse[1095]: mod.rt: found session bus but 
no portal
oct 31 19:33:09 leo-zenbook pipewire[1091]: mod.rt: Can't find xdg-portal: 
(null)
oct 31 19:33:09 leo-zenbook pipewire[1091]: mod.rt: found session bus but no 
portal
oct 31 19:33:09 leo-zenbook dbus-daemon[709]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.31' (uid=125 pid=1095 comm="/usr/bin/pipewire-pulse")
oct 31 19:33:09 leo-zenbook pipewire-pulse[1162]: 536870912
oct 31 19:33:16 leo-zenbook pipewire[1618]: mod.rt: Can't find xdg-portal: 
(null)
oct 31 19:33:16 leo-zenbook pipewire[1618]: mod.rt: found session bus but no 
portal
oct 31 19:33:16 leo-zenbook pipewire-pulse[1622]: mod.rt: Can't find 
xdg-portal: (null)
oct 31 19:33:16 leo-zenbook pipewire-pulse[1622]: mod.rt: found session bus but 
no portal
oct 31 19:33:16 leo-zenbook pipewire-pulse[1691]: 536870912
oct 31 19:33:29 leo-zenbook wireplumber[1094]: disconnected from pipewire
oct 31 19:39:40 leo-zenbook polkitd(authority=local)[721]: Operator of 
unix-session:2 successfully authenticated as unix-user:leo to gain ONE-SHOT 
authorization for action com.ubuntu.apport.root-info for 
unix-process:4109:40542 [/usr/bin/python3 /usr/share/apport/apport-gtk 
pipewire] (owned by unix-user:leo)

I've tried to google if there is a workaround and there isn't any.
Looks like it's not a kernel issue as i've tested this with 5.18, 5.19 and even 
6 for testing purposes and the result was the same.

$ lsb_release -rd
Description:Ubuntu 22.10
Release:22.10

$ apt-cache policy pipewire
pipewire:
  Instalados: 0.3.58-2ubuntu1
  Candidato:  0.3.58-2ubuntu1
  Tabla de versión:
 *** 0.3.58-2ubuntu1 500
500 http://ar.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
100 /var/lib/dpkg/status

Expected: To get audio from sound device
Actual result: Audio is not working, as pipewire throws errors.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: pipewire 0.3.58-2ubuntu1
Uname: Linux 6.0.6-060006-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 31 19:39:34 2022
InstallationDate: Installed on 2022-10-31 (0 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
ProcEnviron:
 LANGUAGE=es_AR:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
SourcePackage: pipewire
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  No sound with Pipewire - mod.rt: Can't find xdg-portal: (null)

Status in pipewire package in Ubuntu:
  New

Bug description:
  Pipewire is not porperly working, sound devices are listed in
  alsamixer, aplay and system settings but there is no audio from the
  pc.

  The only info i got is from journalctl is this output:

  oct 31 19:33:09 leo-zenbook pipewire-pulse[1095]: mod.rt: Can't find 
xdg-portal: (null)
  oct 31 19:33:09 leo-zenbook pipewire-pulse[1095]: mod.rt: found session bus 
but no portal
  oct 31 19:33:09 leo-zenbook pipewire[1091]: mod.rt: Can't find xdg-portal: 
(null)
  oct 31 19:33:09 leo-zenbook pipewire[1091]: mod.rt: found session bus but no 
portal
  oct 31 19:33:09 leo-zenbook dbus-daemon[709]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.31' (uid=125 pid=1095 
comm="/usr/bin/pipewire-pulse")
  oct 31 19:33:09 leo-zenbook pipewire-pulse[1162]: 536870912
  oct 31 19:33:16 leo-zenbook pipewire[1618]: mod.rt: Can't find xdg-portal: 
(null)
  oct 31 19:33:16 leo-zenbook pipewire[1618]: mod.rt: found session bus but no 
portal
  oct 31 19:33:16 leo-zenbook pipewire-pulse[1622]: mod.rt: Can't find 
xdg-portal: (null)
  oct 31 19:33:16 leo-zenbook pipewire-pulse[1622]: mod.rt: found session bus 
but no portal
  oct 31 19:33:16 leo-zenbook pipewire-pulse[1691]: 536870912
  oct 31 19:33:29 leo-zenbook wireplumber[1094]: disconnected from pipewire
  oct 31 19:39:40 leo-zenbook polkitd(authority=local)[721]: Operator of 
unix-session:2 successfully authenticated as unix-user:leo to gain ONE-SHOT 
authorization for action com.ubuntu.apport.root-info for 
unix-process:4109:40542 [/usr/bin/python3 /usr/share/apport/apport-gtk 
pipewire] (owned by unix-user:leo)

  I've tried to google if there is a workaround and 

[Desktop-packages] [Bug 1995311] [NEW] seahorse-nautilus not working on ubuntu 22.10

[Jean-Luc Botto]

Public bug reported:

impossible to install seahorse-nautilus on ubuntu 22.10
so I cannot encrypt/decrypt files (except with line commands)

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

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

Title:
  seahorse-nautilus not working on ubuntu 22.10

Status in nautilus package in Ubuntu:
  New

Bug description:
  impossible to install seahorse-nautilus on ubuntu 22.10
  so I cannot encrypt/decrypt files (except with line commands)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1995311/+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 1993634] Re: network-manager-openvpn: --cipher option deprecated in OpenVPN 2.6, no option to set suggested --data-ciphers flag instead

[Bug Watch Updater]

** Changed in: network-manager-openvpn
   Status: Unknown => New

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

Title:
  network-manager-openvpn: --cipher option deprecated in OpenVPN 2.6, no
  option to set suggested --data-ciphers flag instead

Status in NetworkManager-OpenVPN:
  New
Status in network-manager-openvpn package in Ubuntu:
  Confirmed

Bug description:
  Latest network-manager-openvpn still uses the deprecated --cipher
  option, and offers no way to set the new --data-ciphers option.

  nm-openvpn[257279]: OPTIONS ERROR: failed to negotiate cipher with server.  
Add the server's cipher ('AES-256-CBC') to --data-ciphers (currently 
'AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305') if you want to connect to this 
server.
  nm-openvpn[257279]: ERROR: Failed to apply push options
  nm-openvpn[257279]: Failed to open tun/tap interface

  Using the command line and passing --data-ciphers option works.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: network-manager-openvpn 1.10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Oct 20 09:50:10 2022
  InstallationDate: Installed on 2022-02-05 (256 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220119)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1993634/+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 1995199] Re: Renaming home folders corrupts side panel behavior

[Sebastien Bacher]

Thank you for your bug report. How do you rename the home folder?

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

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

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

Title:
  Renaming home folders corrupts side panel behavior

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Hi!

  Renamed home folder is not synchronized with side panel.
  So, side panel's link does not work after renaming home folders.

  Expected, opening renamed folder from side panel.
  Due to lack of customization of side panel, links can not
  be changed to the new renamed location.

  It is not only my opinion that the side panel must have more
  customization features, including resizing and disabling it. 

  Ubuntu 22.10
  5.19.0-23-generic

  nautilus-data/kinetic,kinetic,now 1:43.0-1ubuntu1 all [installed,automatic]
  nautilus-extension-gnome-terminal/kinetic,now 3.46.2-1ubuntu1 amd64 
[installed,automatic]
  nautilus/kinetic,now 1:43.0-1ubuntu1 amd64 [installed,automatic]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1995199/+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 1995134] Re: WiFi captive portals stopped working after Kinetic upgrade

[Sebastien Bacher]

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

** Tags added: rls-kk-incoming

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

Title:
  WiFi captive portals stopped working after Kinetic upgrade

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After an upgrade from Ubuntu 22.04 to 20.10 NetworkManager no longer
  recognizes captive portals.

  Attempting to run /usr/libexec/gnome-shell-portal-helper produces this
  output:

  (process:166068): Gjs-CRITICAL **: 19:25:08.053: JS ERROR: ImportError: No JS 
module 'fileUtils' found in search path
  @resource:///org/gnome/shell/portalHelper/main.js:13:30
  @:1:14

  
  This may be normal because of the environment, but it is the best I have to 
go on now.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 28 19:26:44 2022
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37
  InstallationDate: Installed on 2019-08-06 (1179 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-10-24 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1995134/+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 1995298] Re: Cheese error after long time to start

[Sebastien Bacher]

Thank you for your bug report. Do you get a similar issue under an xorg
session? Is the webcam working on other software?

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

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

Title:
  Cheese error after long time to start

Status in cheese package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 22.10 Wayland session I start cheese from terminal, after more than 
1 minute cheese starts and displays a black screen with 'There was an error 
playing video from the webcam'
  See attached screencast.
  corrado@corrado-n6-kinetic:~$ apt policy cheese
  cheese:
Installed: 43~alpha-1
Candidate: 43~alpha-1
Version table:
   *** 43~alpha-1 500
  500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n6-kinetic:~$ inxi -SCGx
  System:
Host: corrado-n6-kinetic Kernel: 5.19.0-23-generic arch: x86_64 bits: 64
  compiler: N/A Desktop: GNOME v: 43.0 Distro: Ubuntu 22.10 (Kinetic Kudu)
  CPU:
Info: dual core model: Intel Core i3-7100 bits: 64 type: MT MCP
  arch: Kaby Lake rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 2350 high: 3900 min/max: 800/3900 cores: 1: 3900
  2: 3900 3: 800 4: 800 bogomips: 31199
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
  arch: Gen-9.5 bus-ID: 00:02.0
Device-2: Logitech QuickCam Pro 9000 type: USB
  driver: snd-usb-audio,uvcvideo bus-ID: 1-7:5
Display: wayland server: X.Org v: 1.22.1.3 with: Xwayland v: 22.1.3
  compositor: gnome-shell driver: gpu: i915 resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 22.2.1
  direct render: Yes
  corrado@corrado-n6-kinetic:~$ 

  corrado@corrado-n6-kinetic:~$ cheese

  (cheese:38766): cheese-WARNING **: 17:15:32.022: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)

  
  (cheese:38766): Clutter-CRITICAL **: 17:15:57.413: Unable to create dummy 
onscreen: No foreign surface, and wl_shell unsupported by the compositor
  corrado@corrado-n6-kinetic:~$ 

  Note: I don't use 'ubuntu-bug' because cheese captures the command and
  produces an unusable bug report.

  Problem happens on 3 different PC with different webcams.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-25 (6 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: cheese 43~alpha-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   cheese43~alpha-1
   cheese-common 43~alpha-1
  Tags:  wayland-session kinetic gstreamer-error
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1995298/+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 1993634] Re: network-manager-openvpn: --cipher option deprecated in OpenVPN 2.6, no option to set suggested --data-ciphers flag instead

[Sebastien Bacher]

which is reported upstream as
https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/issues/110

** Also affects: network-manager-openvpn via
   https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/issues/110
   Importance: Unknown
   Status: Unknown

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

Title:
  network-manager-openvpn: --cipher option deprecated in OpenVPN 2.6, no
  option to set suggested --data-ciphers flag instead

Status in NetworkManager-OpenVPN:
  Unknown
Status in network-manager-openvpn package in Ubuntu:
  Confirmed

Bug description:
  Latest network-manager-openvpn still uses the deprecated --cipher
  option, and offers no way to set the new --data-ciphers option.

  nm-openvpn[257279]: OPTIONS ERROR: failed to negotiate cipher with server.  
Add the server's cipher ('AES-256-CBC') to --data-ciphers (currently 
'AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305') if you want to connect to this 
server.
  nm-openvpn[257279]: ERROR: Failed to apply push options
  nm-openvpn[257279]: Failed to open tun/tap interface

  Using the command line and passing --data-ciphers option works.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: network-manager-openvpn 1.10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Oct 20 09:50:10 2022
  InstallationDate: Installed on 2022-02-05 (256 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220119)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1993634/+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 1993634] Re: network-manager-openvpn: --cipher option deprecated in OpenVPN 2.6, no option to set suggested --data-ciphers flag instead

[Sebastien Bacher]

Detail from one of the other reports

'It has been fixed in 1.10.0-1ubuntu2. However, GUI settings does not
process .ovpn correctly, so data-ciphers=AES-256-CBC has to be added to
your connection in /etc/NetworkManager/system-connections.'

** Bug watch added: gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/issues #110
   https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/issues/110

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

Title:
  network-manager-openvpn: --cipher option deprecated in OpenVPN 2.6, no
  option to set suggested --data-ciphers flag instead

Status in NetworkManager-OpenVPN:
  Unknown
Status in network-manager-openvpn package in Ubuntu:
  Confirmed

Bug description:
  Latest network-manager-openvpn still uses the deprecated --cipher
  option, and offers no way to set the new --data-ciphers option.

  nm-openvpn[257279]: OPTIONS ERROR: failed to negotiate cipher with server.  
Add the server's cipher ('AES-256-CBC') to --data-ciphers (currently 
'AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305') if you want to connect to this 
server.
  nm-openvpn[257279]: ERROR: Failed to apply push options
  nm-openvpn[257279]: Failed to open tun/tap interface

  Using the command line and passing --data-ciphers option works.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: network-manager-openvpn 1.10.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Oct 20 09:50:10 2022
  InstallationDate: Installed on 2022-02-05 (256 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220119)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1993634/+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 1969707] Re: DEPRECATED OPTION: --cipher set to 'AES-128-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM).

[Sebastien Bacher]

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

** This bug is no longer a duplicate of bug 1988301
   Does not implement data-ciphers, only cipher which OpenVPN 2.5+ ignores, 
hence can fail to connect
** This bug has been marked a duplicate of bug 1993634
   network-manager-openvpn: --cipher option deprecated in OpenVPN 2.6, no 
option to set suggested --data-ciphers flag instead

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

Title:
  DEPRECATED OPTION: --cipher set to 'AES-128-CBC' but missing in
  --data-ciphers (AES-256-GCM:AES-128-GCM).

Status in OEM Priority Project:
  Invalid
Status in network-manager-openvpn package in Ubuntu:
  Invalid

Bug description:
  Try to enable vpn, but the vpn is not able to enable. The config file
  under /etc/NetworkManager input a deprecated option. Try to change
  cipher to data-cipher, the network can be enabled successfully.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager-openvpn 1.8.18-1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 21 10:19:15 2022
  InstallationDate: Installed on 2022-04-21 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1969707/+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 1988301] Re: Does not implement data-ciphers, only cipher which OpenVPN 2.5+ ignores, hence can fail to connect

[Sebastien Bacher]

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

** This bug has been marked a duplicate of bug 1993634
   network-manager-openvpn: --cipher option deprecated in OpenVPN 2.6, no 
option to set suggested --data-ciphers flag instead

** This bug is no longer a duplicate of bug 1993634
   network-manager-openvpn: --cipher option deprecated in OpenVPN 2.6, no 
option to set suggested --data-ciphers flag instead

** This bug has been marked a duplicate of bug 1993634
   network-manager-openvpn: --cipher option deprecated in OpenVPN 2.6, no 
option to set suggested --data-ciphers flag instead

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

Title:
  Does not implement data-ciphers, only cipher which OpenVPN 2.5+
  ignores, hence can fail to connect

Status in network-manager-openvpn package in Ubuntu:
  Confirmed

Bug description:
  It's no longer possible to use the cipher option in NetworkManager as
  it's ignored by OpenVPN; and the default list of data-ciphers is
  applied, making it impossible to connect to an AES-128-CBC endpoint
  from NetworkManager.

  There does not appear any way to forward the data-ciphers config, even
  if I hand edited the nmconnection file to add a data-ciphers line it
  is ignored.

  More insight is available to Canonical folks in
  https://rt.admin.canonical.com/Ticket/Display.html?id=153000

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1988301/+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 1994141] Re: incompatible versions of network-manager-openvpn and openvpn delivered in ubuntu22.10

[Sebastien Bacher]

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

** This bug has been marked a duplicate of bug 1993634
   network-manager-openvpn: --cipher option deprecated in OpenVPN 2.6, no 
option to set suggested --data-ciphers flag instead

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

Title:
  incompatible versions of network-manager-openvpn and openvpn delivered
  in ubuntu22.10

Status in network-manager-openvpn package in Ubuntu:
  Confirmed

Bug description:
  After installing  network-manager-openvpn(1.10.0-1ubuntu2),
  openvpn(2.6.0~git20220818-1ubuntu1) is installed as a dependency.

  Mentioned NM plugin uses openvpn option `--cipher` instead of `--data-
  ciphers`. With openvpn2.6.0+ this breaks existing setups - connection
  never establishes and fails with message like:

  ```
  DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in 
--data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores 
--cipher for cipher negotiations.
  ```
  and
  ```
  Connection reset, restarting [0]
  ```

  reproducer: configure openVPN client against openVPN server with
  cipher set to 'AES-256-CBC'.

  workaround: manually install openvpn 2.5.x from sources and mask
  distribution-provided openvpn 2.6.x.

  proposed solution:

  deliver compatible combination of network-manager-openvpn and openvpn.

  
  system info:
  Description:Ubuntu 22.10
  Release:22.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1994141/+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 1993809] Re: Update gnome-shell to 42.5

[Sebastien Bacher]

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

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

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

Title:
  Update gnome-shell to 42.5

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

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 42 series.

  https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.5/NEWS

  The version currently in Ubuntu 22.04.1 LTS is 42.4

  Test Case
  -
  Complete all the test cases at 
https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell

  What Could Go Wrong
  ---
  GNOME Shell is the heart of the Ubuntu desktop experience.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  GNOME Shell is included in the GNOME micro release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Other Info
  --
  I also cherry-picked a fix from kinetic:
  gsettings org.gnome.settings-daemon.peripherals.mouse
  no longer exists in Ubuntu 22.04 LTS so I updated the apport script to stop 
trying to report customizations for that gsettings schema.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993809/+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 1993581] Re: [snap] posix_spawn: No such file or directory

[Alexander Browne]

$ chromium
[215800:215800:1031/155854.374117:FATAL:spawn_subprocess.cc(221)] posix_spawn: 
No such file or directory (2)
Trace/breakpoint trap (core dumped)

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

Title:
  [snap] posix_spawn: No such file or directory

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Chromium from the edge channel fails to launch with

% chromium
[17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)] 
posix_spawn: No such file or directory (2)

% snap info chromium
channels:
  latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB -
  latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB -
  latest/beta:  107.0.5304.36  2022-10-13 (2135) 152MB -
  latest/edge:  108.0.5355.0   2022-10-18 (2146) 153MB -
installed:  108.0.5355.0  (2146) 153MB -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993581/+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 1993581] Re: [snap] posix_spawn: No such file or directory

[Alexander Browne]

Seeing this with the today's beta build: 108.0.5359.22 (2177).

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

Title:
  [snap] posix_spawn: No such file or directory

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Chromium from the edge channel fails to launch with

% chromium
[17618:17618:1019/163156.976437:FATAL:spawn_subprocess.cc(221)] 
posix_spawn: No such file or directory (2)

% snap info chromium
channels:
  latest/stable:106.0.5249.119 2022-10-14 (2136) 150MB -
  latest/candidate: 106.0.5249.119 2022-10-13 (2136) 150MB -
  latest/beta:  107.0.5304.36  2022-10-13 (2135) 152MB -
  latest/edge:  108.0.5355.0   2022-10-18 (2146) 153MB -
installed:  108.0.5355.0  (2146) 153MB -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1993581/+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 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)

[vodopad27]

+ added xserver-xorg-video-intel to related packages. Probably related
with isse. As far as i know xserver-xorg-video-intel package contain
intel driver package.

** Also affects: xserver-xorg-video-intel (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Can not login after new kernel installed (nvidia driver crashed)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-515 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  New
Status in linux source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-510 source package in Jammy:
  Confirmed
Status in nvidia-graphics-drivers-515 source package in Jammy:
  Confirmed
Status in xserver-xorg-video-intel source package in Jammy:
  New

Bug description:
  Hello. Today i have installed new kernel from. I installed 5.15.0-50
  and after that i can not login to system... I see boot text, but after
  booting i see black log screen and can not login. I able boot and
  login with old kernel  (5.15.0-48).

  I updated these packages:
  Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), 
linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), 
linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic)
  Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), 
google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), 
linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 
(5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 
5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50)

  Updated logs see in attachement.

  Logs from journalctl see in attachements.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-50-generic 5.15.0-50.56
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vodka  1819 F pulseaudio
   /dev/snd/controlC1:  vodka  1819 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Wed Oct 12 19:56:43 2022
  InstallationDate: Installed on 2018-05-02 (1623 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device
   Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-48-generic N/A
   linux-backports-modules-5.15.0-48-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  RfKill:

  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago)
  dmi.bios.date: 03/28/2022
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F7a
  dmi.board.asset.tag: Default string
  dmi.board.name: H610M S2H DDR4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: H610 MB
  dmi.product.name: H610M S2H DDR4
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


-- 
Mailing list: 

[Desktop-packages] [Bug 1994027] Re: Can't move window by drag and drop by using touch screen

[Bug Watch Updater]

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

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

Title:
  Can't move window by drag and drop by using touch screen

Status in Mutter:
  New
Status in OEM Priority Project:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  [Summary]
  For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed.

  [Steps to reproduce]
  1. Install the 22.04
  2. Boot and login
  3. Open a folder
  4. Drag-n-drop the folder with finger touch
  5. Drag-n-drop the folder with the Wacom Pen

  [Expected result]
  Both finger touch and wacom pen work normally.

  [Actual result]
  Wacom Pen works normally, finger touch can not move the folder.

  [Failure rate]
  100%

  [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop`
  output]

  [Other Information]
  xorg  1:7.7+23ubuntu2
  mutter-common 42.2-0ubuntu1
  gnome-shell 42.4-0ubuntu0.22.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1994027/+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 1994519] Re: DisplayLink display is black on plug-in and mutter crash after moving cursor on DisplayLink display.

[Bug Watch Updater]

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

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

Title:
  DisplayLink display is black on plug-in and mutter crash after moving
  cursor on DisplayLink display.

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  
  This is recent regression with reproduction rate 100%.
  This is regression mutter-43, Ubuntu 22.04 works fine.

  Bug is raised on Gnome/mutter:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2481
  Fix is under review:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2676

  
  ### Steps to reproduce

  1. Login
  2. Attach DisplayLink device with display connected
  3. Notice that display is visible in Display Preferences but display stays 
blank.
  4. Move cursor over DisplayLink display.
  5. Mutter crashes.

  
  ### What happened

  Mutter crashes, user is asked to log-in again.

  ### What did you expect to happen

  Mutter does not crash.

  ### Relevant logs, screenshots, screencasts etc.
  Crash in line:
  
https://gitlab.gnome.org/GNOME/mutter/-/blob/main/src/backends/native/meta-renderer-native.c#L226

  Crash backtrace:
  ```
  Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) at 
../src/backends/native/meta-renderer-native.c:204
  204   render_device = renderer_gpu_data->render_device;
  (gdb) bt
  #0  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) 
at ../src/backends/native/meta-renderer-native.c:204
  #1  0x7f9209c06674 in create_cursor_drm_buffer (gpu_kms=0x55eb13bc9e00, 
device_file=0x55eb15eaa860, pixels=0x7f91b4bb9700 "", width=24, height=24, 
stride=96, cursor_width=64, cursor_height=64, format=875713089, 
error=0x7ffda9443108) at 
../src/backends/native/meta-cursor-renderer-native.c:1329
  #2  0x7f9209c068b9 in load_cursor_sprite_gbm_buffer_for_gpu 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
pixels=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, 
gbm_format=875713089) at 
../src/backends/native/meta-cursor-renderer-native.c:1399
  #3  0x7f9209c06f98 in load_scaled_and_transformed_cursor_sprite 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
relative_scale=1, relative_transform=META_MONITOR_TRANSFORM_NORMAL, 
data=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, gbm_format=875713089)
  at ../src/backends/native/meta-cursor-renderer-native.c:1574
  #4  0x7f9209c07293 in realize_cursor_sprite_from_wl_buffer_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, 
sprite_wayland=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1670
  #5  0x7f9209c07788 in realize_cursor_sprite_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00) 
at ../src/backends/native/meta-cursor-renderer-native.c:1836
  #6  0x7f9209c077cf in realize_cursor_sprite (renderer=0x55eb1617f580, 
cursor_sprite=0x55eb1918fb00, gpus=0x55eb16345a20 = {...}) at 
../src/backends/native/meta-cursor-renderer-native.c:1854
  #7  0x7f9209c05dd4 in meta_cursor_renderer_native_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1087
  #8  0x7f9209aac8fa in meta_cursor_renderer_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/meta-cursor-renderer.c:413
  #9  0x7f9209aaca07 in meta_cursor_renderer_force_update 
(renderer=0x55eb1617f580) at ../src/backends/meta-cursor-renderer.c:448
  #10 0x7f9209bc4dc6 in update_cursor_sprite_texture 
(cursor_surface=0x55eb1924d880) at 
../src/wayland/meta-wayland-cursor-surface.c:79
  #11 0x7f9209bc512a in meta_wayland_cursor_surface_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-cursor-surface.c:179
  #12 0x7f9209be3774 in meta_wayland_surface_role_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:1938
  #13 0x7f9209be14b6 in meta_wayland_surface_apply_state 
(surface=0x55eb16305e60, state=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:882
  #14 0x7f9209be19c7 in meta_wayland_surface_commit 
(surface=0x55eb16305e60) at ../src/wayland/meta-wayland-surface.c:1038
  #15 0x7f9209be1e9f in wl_surface_commit (client=0x55eb191d7150, 
resource=0x55eb191f1eb0) at ../src/wayland/meta-wayland-surface.c:1191
  #16 0x7f9209d1ae2e in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #17 0x7f9209d17493 in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #18 0x7f920aea42a0 in  () at /lib/x86_64-linux-gnu/libwayland-server.so.0
  #19 0x7f920aea8694 in  () at /lib/x86_64-linux-gnu/libwayland-server.so.0
  #20 0x7f920aea70fa in 

[Desktop-packages] [Bug 1994141] Re: incompatible versions of network-manager-openvpn and openvpn delivered in ubuntu22.10

[Sergio Durigan Junior]

Thank you for your bug report.  This seems to be a problem with network-
manager-openvpn, so I took the liberty to remove Ubuntu and the openvpn
package from the list of affected projects.  I also pinged the person
that backported the upstream fixes to Kinetic.

** No longer affects: ubuntu

** No longer affects: openvpn (Ubuntu)

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

Title:
  incompatible versions of network-manager-openvpn and openvpn delivered
  in ubuntu22.10

Status in network-manager-openvpn package in Ubuntu:
  Confirmed

Bug description:
  After installing  network-manager-openvpn(1.10.0-1ubuntu2),
  openvpn(2.6.0~git20220818-1ubuntu1) is installed as a dependency.

  Mentioned NM plugin uses openvpn option `--cipher` instead of `--data-
  ciphers`. With openvpn2.6.0+ this breaks existing setups - connection
  never establishes and fails with message like:

  ```
  DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in 
--data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores 
--cipher for cipher negotiations.
  ```
  and
  ```
  Connection reset, restarting [0]
  ```

  reproducer: configure openVPN client against openVPN server with
  cipher set to 'AES-256-CBC'.

  workaround: manually install openvpn 2.5.x from sources and mask
  distribution-provided openvpn 2.6.x.

  proposed solution:

  deliver compatible combination of network-manager-openvpn and openvpn.

  
  system info:
  Description:Ubuntu 22.10
  Release:22.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1994141/+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 1993800]

[Aaronpuchert]

(In reply to OBSbugzilla Bot from comment #12)
> This is an autogenerated message for OBS integration:
> This bug (1204267) was mentioned in
> https://build.opensuse.org/request/show/1031948 Factory / llvm15

This made it into snapshot 20221029 released today, and it fixes the
compilation failure for the reproducer from attachment 862276.
Factory:ARM hasn't released a new snapshot yet. Feel free to close once
you're able to confirm that this fixes the original issue.

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

Title:
  LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8,
  Constant:i32<2>

Status in LLVM:
  New
Status in llvm-toolchain-15 package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in llvm-toolchain-15 package in openSUSE:
  Unknown

Bug description:
  LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, 
Constant:i32<2>
    0x2f696b8: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 0x2aad434, 
0x2f84090:1, Constant:i32<4>
  0x2f84090: i32,i32,ch = load<(load (s32) from %ir.209, align 8), 
> 0x2aad434, 0x2f63a30, Constant:i32<64>
    0x2f63a30: i32,ch = CopyFromReg 0x2aad434, Register:i32 %23
  0x2f51c10: i32 = Register %23
    0x2f82500: i32 = Constant<64>
  0x2f81b28: i32 = Constant<4>
    0x2f81e40: i32 = Constant<2>
  In function: fs_variant_partial

  [https://launchpadlibrarian.net/629171689/buildlog_ubuntu-kinetic-
  armhf.mutter_43.0-1ubuntu3_BUILDING.txt.gz]

  Although "LLVM ERROR: Cannot select" seems to be from LLVM, I can't
  determine what project "fs_variant_partial" is in. Sounds like it
  might be in some old version of Mesa? The start of the log suggests
  it's running on focal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/llvm/+bug/1993800/+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 1995298] lsusb.txt

[corrado venturini]

apport information

** Attachment added: "lsusb.txt"
   https://bugs.launchpad.net/bugs/1995298/+attachment/5628074/+files/lsusb.txt

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

Title:
  Cheese error after long time to start

Status in cheese package in Ubuntu:
  New

Bug description:
  On Ubuntu 22.10 Wayland session I start cheese from terminal, after more than 
1 minute cheese starts and displays a black screen with 'There was an error 
playing video from the webcam'
  See attached screencast.
  corrado@corrado-n6-kinetic:~$ apt policy cheese
  cheese:
Installed: 43~alpha-1
Candidate: 43~alpha-1
Version table:
   *** 43~alpha-1 500
  500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n6-kinetic:~$ inxi -SCGx
  System:
Host: corrado-n6-kinetic Kernel: 5.19.0-23-generic arch: x86_64 bits: 64
  compiler: N/A Desktop: GNOME v: 43.0 Distro: Ubuntu 22.10 (Kinetic Kudu)
  CPU:
Info: dual core model: Intel Core i3-7100 bits: 64 type: MT MCP
  arch: Kaby Lake rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 2350 high: 3900 min/max: 800/3900 cores: 1: 3900
  2: 3900 3: 800 4: 800 bogomips: 31199
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
  arch: Gen-9.5 bus-ID: 00:02.0
Device-2: Logitech QuickCam Pro 9000 type: USB
  driver: snd-usb-audio,uvcvideo bus-ID: 1-7:5
Display: wayland server: X.Org v: 1.22.1.3 with: Xwayland v: 22.1.3
  compositor: gnome-shell driver: gpu: i915 resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 22.2.1
  direct render: Yes
  corrado@corrado-n6-kinetic:~$ 

  corrado@corrado-n6-kinetic:~$ cheese

  (cheese:38766): cheese-WARNING **: 17:15:32.022: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)

  
  (cheese:38766): Clutter-CRITICAL **: 17:15:57.413: Unable to create dummy 
onscreen: No foreign surface, and wl_shell unsupported by the compositor
  corrado@corrado-n6-kinetic:~$ 

  Note: I don't use 'ubuntu-bug' because cheese captures the command and
  produces an unusable bug report.

  Problem happens on 3 different PC with different webcams.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-25 (6 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: cheese 43~alpha-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   cheese43~alpha-1
   cheese-common 43~alpha-1
  Tags:  wayland-session kinetic gstreamer-error
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1995298/+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 1995298] ProcCpuinfoMinimal.txt

[corrado venturini]

apport information

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

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

Title:
  Cheese error after long time to start

Status in cheese package in Ubuntu:
  New

Bug description:
  On Ubuntu 22.10 Wayland session I start cheese from terminal, after more than 
1 minute cheese starts and displays a black screen with 'There was an error 
playing video from the webcam'
  See attached screencast.
  corrado@corrado-n6-kinetic:~$ apt policy cheese
  cheese:
Installed: 43~alpha-1
Candidate: 43~alpha-1
Version table:
   *** 43~alpha-1 500
  500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n6-kinetic:~$ inxi -SCGx
  System:
Host: corrado-n6-kinetic Kernel: 5.19.0-23-generic arch: x86_64 bits: 64
  compiler: N/A Desktop: GNOME v: 43.0 Distro: Ubuntu 22.10 (Kinetic Kudu)
  CPU:
Info: dual core model: Intel Core i3-7100 bits: 64 type: MT MCP
  arch: Kaby Lake rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 2350 high: 3900 min/max: 800/3900 cores: 1: 3900
  2: 3900 3: 800 4: 800 bogomips: 31199
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
  arch: Gen-9.5 bus-ID: 00:02.0
Device-2: Logitech QuickCam Pro 9000 type: USB
  driver: snd-usb-audio,uvcvideo bus-ID: 1-7:5
Display: wayland server: X.Org v: 1.22.1.3 with: Xwayland v: 22.1.3
  compositor: gnome-shell driver: gpu: i915 resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 22.2.1
  direct render: Yes
  corrado@corrado-n6-kinetic:~$ 

  corrado@corrado-n6-kinetic:~$ cheese

  (cheese:38766): cheese-WARNING **: 17:15:32.022: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)

  
  (cheese:38766): Clutter-CRITICAL **: 17:15:57.413: Unable to create dummy 
onscreen: No foreign surface, and wl_shell unsupported by the compositor
  corrado@corrado-n6-kinetic:~$ 

  Note: I don't use 'ubuntu-bug' because cheese captures the command and
  produces an unusable bug report.

  Problem happens on 3 different PC with different webcams.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-25 (6 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: cheese 43~alpha-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   cheese43~alpha-1
   cheese-common 43~alpha-1
  Tags:  wayland-session kinetic gstreamer-error
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1995298/+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 1995298] lspci.txt

[corrado venturini]

apport information

** Attachment added: "lspci.txt"
   https://bugs.launchpad.net/bugs/1995298/+attachment/5628073/+files/lspci.txt

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

Title:
  Cheese error after long time to start

Status in cheese package in Ubuntu:
  New

Bug description:
  On Ubuntu 22.10 Wayland session I start cheese from terminal, after more than 
1 minute cheese starts and displays a black screen with 'There was an error 
playing video from the webcam'
  See attached screencast.
  corrado@corrado-n6-kinetic:~$ apt policy cheese
  cheese:
Installed: 43~alpha-1
Candidate: 43~alpha-1
Version table:
   *** 43~alpha-1 500
  500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n6-kinetic:~$ inxi -SCGx
  System:
Host: corrado-n6-kinetic Kernel: 5.19.0-23-generic arch: x86_64 bits: 64
  compiler: N/A Desktop: GNOME v: 43.0 Distro: Ubuntu 22.10 (Kinetic Kudu)
  CPU:
Info: dual core model: Intel Core i3-7100 bits: 64 type: MT MCP
  arch: Kaby Lake rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 2350 high: 3900 min/max: 800/3900 cores: 1: 3900
  2: 3900 3: 800 4: 800 bogomips: 31199
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
  arch: Gen-9.5 bus-ID: 00:02.0
Device-2: Logitech QuickCam Pro 9000 type: USB
  driver: snd-usb-audio,uvcvideo bus-ID: 1-7:5
Display: wayland server: X.Org v: 1.22.1.3 with: Xwayland v: 22.1.3
  compositor: gnome-shell driver: gpu: i915 resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 22.2.1
  direct render: Yes
  corrado@corrado-n6-kinetic:~$ 

  corrado@corrado-n6-kinetic:~$ cheese

  (cheese:38766): cheese-WARNING **: 17:15:32.022: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)

  
  (cheese:38766): Clutter-CRITICAL **: 17:15:57.413: Unable to create dummy 
onscreen: No foreign surface, and wl_shell unsupported by the compositor
  corrado@corrado-n6-kinetic:~$ 

  Note: I don't use 'ubuntu-bug' because cheese captures the command and
  produces an unusable bug report.

  Problem happens on 3 different PC with different webcams.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-25 (6 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: cheese 43~alpha-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   cheese43~alpha-1
   cheese-common 43~alpha-1
  Tags:  wayland-session kinetic gstreamer-error
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1995298/+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 1995298] ProcCpuinfo.txt

[corrado venturini]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1995298/+attachment/5628070/+files/ProcCpuinfo.txt

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

Title:
  Cheese error after long time to start

Status in cheese package in Ubuntu:
  New

Bug description:
  On Ubuntu 22.10 Wayland session I start cheese from terminal, after more than 
1 minute cheese starts and displays a black screen with 'There was an error 
playing video from the webcam'
  See attached screencast.
  corrado@corrado-n6-kinetic:~$ apt policy cheese
  cheese:
Installed: 43~alpha-1
Candidate: 43~alpha-1
Version table:
   *** 43~alpha-1 500
  500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n6-kinetic:~$ inxi -SCGx
  System:
Host: corrado-n6-kinetic Kernel: 5.19.0-23-generic arch: x86_64 bits: 64
  compiler: N/A Desktop: GNOME v: 43.0 Distro: Ubuntu 22.10 (Kinetic Kudu)
  CPU:
Info: dual core model: Intel Core i3-7100 bits: 64 type: MT MCP
  arch: Kaby Lake rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 2350 high: 3900 min/max: 800/3900 cores: 1: 3900
  2: 3900 3: 800 4: 800 bogomips: 31199
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
  arch: Gen-9.5 bus-ID: 00:02.0
Device-2: Logitech QuickCam Pro 9000 type: USB
  driver: snd-usb-audio,uvcvideo bus-ID: 1-7:5
Display: wayland server: X.Org v: 1.22.1.3 with: Xwayland v: 22.1.3
  compositor: gnome-shell driver: gpu: i915 resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 22.2.1
  direct render: Yes
  corrado@corrado-n6-kinetic:~$ 

  corrado@corrado-n6-kinetic:~$ cheese

  (cheese:38766): cheese-WARNING **: 17:15:32.022: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)

  
  (cheese:38766): Clutter-CRITICAL **: 17:15:57.413: Unable to create dummy 
onscreen: No foreign surface, and wl_shell unsupported by the compositor
  corrado@corrado-n6-kinetic:~$ 

  Note: I don't use 'ubuntu-bug' because cheese captures the command and
  produces an unusable bug report.

  Problem happens on 3 different PC with different webcams.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-25 (6 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: cheese 43~alpha-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   cheese43~alpha-1
   cheese-common 43~alpha-1
  Tags:  wayland-session kinetic gstreamer-error
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1995298/+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 1995298] ProcEnviron.txt

[corrado venturini]

apport information

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

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

Title:
  Cheese error after long time to start

Status in cheese package in Ubuntu:
  New

Bug description:
  On Ubuntu 22.10 Wayland session I start cheese from terminal, after more than 
1 minute cheese starts and displays a black screen with 'There was an error 
playing video from the webcam'
  See attached screencast.
  corrado@corrado-n6-kinetic:~$ apt policy cheese
  cheese:
Installed: 43~alpha-1
Candidate: 43~alpha-1
Version table:
   *** 43~alpha-1 500
  500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n6-kinetic:~$ inxi -SCGx
  System:
Host: corrado-n6-kinetic Kernel: 5.19.0-23-generic arch: x86_64 bits: 64
  compiler: N/A Desktop: GNOME v: 43.0 Distro: Ubuntu 22.10 (Kinetic Kudu)
  CPU:
Info: dual core model: Intel Core i3-7100 bits: 64 type: MT MCP
  arch: Kaby Lake rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 2350 high: 3900 min/max: 800/3900 cores: 1: 3900
  2: 3900 3: 800 4: 800 bogomips: 31199
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
  arch: Gen-9.5 bus-ID: 00:02.0
Device-2: Logitech QuickCam Pro 9000 type: USB
  driver: snd-usb-audio,uvcvideo bus-ID: 1-7:5
Display: wayland server: X.Org v: 1.22.1.3 with: Xwayland v: 22.1.3
  compositor: gnome-shell driver: gpu: i915 resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 22.2.1
  direct render: Yes
  corrado@corrado-n6-kinetic:~$ 

  corrado@corrado-n6-kinetic:~$ cheese

  (cheese:38766): cheese-WARNING **: 17:15:32.022: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)

  
  (cheese:38766): Clutter-CRITICAL **: 17:15:57.413: Unable to create dummy 
onscreen: No foreign surface, and wl_shell unsupported by the compositor
  corrado@corrado-n6-kinetic:~$ 

  Note: I don't use 'ubuntu-bug' because cheese captures the command and
  produces an unusable bug report.

  Problem happens on 3 different PC with different webcams.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-25 (6 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: cheese 43~alpha-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   cheese43~alpha-1
   cheese-common 43~alpha-1
  Tags:  wayland-session kinetic gstreamer-error
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1995298/+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 1995298] CheeseDebug.txt.gz

[corrado venturini]

apport information

** Attachment added: "CheeseDebug.txt.gz"
   
https://bugs.launchpad.net/bugs/1995298/+attachment/5628068/+files/CheeseDebug.txt.gz

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

Title:
  Cheese error after long time to start

Status in cheese package in Ubuntu:
  New

Bug description:
  On Ubuntu 22.10 Wayland session I start cheese from terminal, after more than 
1 minute cheese starts and displays a black screen with 'There was an error 
playing video from the webcam'
  See attached screencast.
  corrado@corrado-n6-kinetic:~$ apt policy cheese
  cheese:
Installed: 43~alpha-1
Candidate: 43~alpha-1
Version table:
   *** 43~alpha-1 500
  500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n6-kinetic:~$ inxi -SCGx
  System:
Host: corrado-n6-kinetic Kernel: 5.19.0-23-generic arch: x86_64 bits: 64
  compiler: N/A Desktop: GNOME v: 43.0 Distro: Ubuntu 22.10 (Kinetic Kudu)
  CPU:
Info: dual core model: Intel Core i3-7100 bits: 64 type: MT MCP
  arch: Kaby Lake rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 2350 high: 3900 min/max: 800/3900 cores: 1: 3900
  2: 3900 3: 800 4: 800 bogomips: 31199
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
  arch: Gen-9.5 bus-ID: 00:02.0
Device-2: Logitech QuickCam Pro 9000 type: USB
  driver: snd-usb-audio,uvcvideo bus-ID: 1-7:5
Display: wayland server: X.Org v: 1.22.1.3 with: Xwayland v: 22.1.3
  compositor: gnome-shell driver: gpu: i915 resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 22.2.1
  direct render: Yes
  corrado@corrado-n6-kinetic:~$ 

  corrado@corrado-n6-kinetic:~$ cheese

  (cheese:38766): cheese-WARNING **: 17:15:32.022: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)

  
  (cheese:38766): Clutter-CRITICAL **: 17:15:57.413: Unable to create dummy 
onscreen: No foreign surface, and wl_shell unsupported by the compositor
  corrado@corrado-n6-kinetic:~$ 

  Note: I don't use 'ubuntu-bug' because cheese captures the command and
  produces an unusable bug report.

  Problem happens on 3 different PC with different webcams.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-25 (6 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: cheese 43~alpha-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   cheese43~alpha-1
   cheese-common 43~alpha-1
  Tags:  wayland-session kinetic gstreamer-error
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1995298/+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 1995298] Dependencies.txt

[corrado venturini]

apport information

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

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

Title:
  Cheese error after long time to start

Status in cheese package in Ubuntu:
  New

Bug description:
  On Ubuntu 22.10 Wayland session I start cheese from terminal, after more than 
1 minute cheese starts and displays a black screen with 'There was an error 
playing video from the webcam'
  See attached screencast.
  corrado@corrado-n6-kinetic:~$ apt policy cheese
  cheese:
Installed: 43~alpha-1
Candidate: 43~alpha-1
Version table:
   *** 43~alpha-1 500
  500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n6-kinetic:~$ inxi -SCGx
  System:
Host: corrado-n6-kinetic Kernel: 5.19.0-23-generic arch: x86_64 bits: 64
  compiler: N/A Desktop: GNOME v: 43.0 Distro: Ubuntu 22.10 (Kinetic Kudu)
  CPU:
Info: dual core model: Intel Core i3-7100 bits: 64 type: MT MCP
  arch: Kaby Lake rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 2350 high: 3900 min/max: 800/3900 cores: 1: 3900
  2: 3900 3: 800 4: 800 bogomips: 31199
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
  arch: Gen-9.5 bus-ID: 00:02.0
Device-2: Logitech QuickCam Pro 9000 type: USB
  driver: snd-usb-audio,uvcvideo bus-ID: 1-7:5
Display: wayland server: X.Org v: 1.22.1.3 with: Xwayland v: 22.1.3
  compositor: gnome-shell driver: gpu: i915 resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 22.2.1
  direct render: Yes
  corrado@corrado-n6-kinetic:~$ 

  corrado@corrado-n6-kinetic:~$ cheese

  (cheese:38766): cheese-WARNING **: 17:15:32.022: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)

  
  (cheese:38766): Clutter-CRITICAL **: 17:15:57.413: Unable to create dummy 
onscreen: No foreign surface, and wl_shell unsupported by the compositor
  corrado@corrado-n6-kinetic:~$ 

  Note: I don't use 'ubuntu-bug' because cheese captures the command and
  produces an unusable bug report.

  Problem happens on 3 different PC with different webcams.
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2022-10-25 (6 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: cheese 43~alpha-1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   cheese43~alpha-1
   cheese-common 43~alpha-1
  Tags:  wayland-session kinetic gstreamer-error
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1995298/+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 1995298] [NEW] Cheese error after long time to start

[corrado venturini]

Public bug reported:

On Ubuntu 22.10 Wayland session I start cheese from terminal, after more than 1 
minute cheese starts and displays a black screen with 'There was an error 
playing video from the webcam'
See attached screencast.
corrado@corrado-n6-kinetic:~$ apt policy cheese
cheese:
  Installed: 43~alpha-1
  Candidate: 43~alpha-1
  Version table:
 *** 43~alpha-1 500
500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
100 /var/lib/dpkg/status
corrado@corrado-n6-kinetic:~$ inxi -SCGx
System:
  Host: corrado-n6-kinetic Kernel: 5.19.0-23-generic arch: x86_64 bits: 64
compiler: N/A Desktop: GNOME v: 43.0 Distro: Ubuntu 22.10 (Kinetic Kudu)
CPU:
  Info: dual core model: Intel Core i3-7100 bits: 64 type: MT MCP
arch: Kaby Lake rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
  Speed (MHz): avg: 2350 high: 3900 min/max: 800/3900 cores: 1: 3900
2: 3900 3: 800 4: 800 bogomips: 31199
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
arch: Gen-9.5 bus-ID: 00:02.0
  Device-2: Logitech QuickCam Pro 9000 type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 1-7:5
  Display: wayland server: X.Org v: 1.22.1.3 with: Xwayland v: 22.1.3
compositor: gnome-shell driver: gpu: i915 resolution: 1920x1080~60Hz
  OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 22.2.1
direct render: Yes
corrado@corrado-n6-kinetic:~$ 

corrado@corrado-n6-kinetic:~$ cheese

(cheese:38766): cheese-WARNING **: 17:15:32.022: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
streaming stopped, reason not-negotiated (-4)


(cheese:38766): Clutter-CRITICAL **: 17:15:57.413: Unable to create dummy 
onscreen: No foreign surface, and wl_shell unsupported by the compositor
corrado@corrado-n6-kinetic:~$ 

Note: I don't use 'ubuntu-bug' because cheese captures the command and
produces an unusable bug report.

Problem happens on 3 different PC with different webcams.
--- 
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.10
InstallationDate: Installed on 2022-10-25 (6 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: cheese 43~alpha-1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
RelatedPackageVersions:
 cheese43~alpha-1
 cheese-common 43~alpha-1
Tags:  wayland-session kinetic gstreamer-error
Uname: Linux 5.19.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/11/2017
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: H110M-G/M.2
dmi.board.vendor: ASRock
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: apport-collected gstreamer-error kinetic wayland-session

** Attachment added: "Screencast from 2022-10-31 17-14-18.webm"
   
https://bugs.launchpad.net/bugs/1995298/+attachment/5628067/+files/Screencast%20from%202022-10-31%2017-14-18.webm

** Tags added: apport-collected gstreamer-error kinetic wayland-session

** Description changed:

  On Ubuntu 22.10 Wayland session I start cheese from terminal, after more than 
1 minute cheese starts and displays a black screen with 'There was an error 
playing video from the webcam'
  See attached screencast.
  corrado@corrado-n6-kinetic:~$ apt policy cheese
  cheese:
Installed: 43~alpha-1
Candidate: 43~alpha-1
Version table:
   *** 43~alpha-1 500
  500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-n6-kinetic:~$ inxi -SCGx
  System:
Host: corrado-n6-kinetic Kernel: 5.19.0-23-generic arch: x86_64 bits: 64
  compiler: N/A Desktop: GNOME v: 43.0 Distro: Ubuntu 22.10 (Kinetic Kudu)
  CPU:
Info: dual core model: Intel Core i3-7100 bits: 64 type: MT MCP
  arch: Kaby Lake rev: 9 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB
Speed (MHz): avg: 2350 high: 3900 min/max: 800/3900 cores: 1: 3900
  2: 3900 3: 800 4: 

[Desktop-packages] [Bug 1995297] [NEW] Wi-Fi and bluetooth appear as disabled

[José Rojas]

Public bug reported:

According to rfkill, my Bluetooth (and Wi-Fi) devices are "blocked by
hardware". Nonetheless, bluetooth is functional, when connected to a
device.

When there's no active connection, bluetooth appears as disabled in the panel.
When I turn on a device that's already peered, it gets automatically connected 
and the popout message when I place the cursor in the panel's icon reads 
"bluetooth active- One active connection". 
But when I click on the bluetooth icon on the panel, an error message appears 
that reads that bluetooth is OFF, but in reality it is ON and CONNECTED to a 
device.

Something similar might be happening to the Wi-Fi as it is also shown as
"disabled" and can't be enabled.

PS. Some days they have worked fine. I mean, I have turned on the laptop
and "magically" both bluetooth and wifi were working.

But, unfortunately they aren't working now and haven't been working for
a few days already.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: network-manager 1.40.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Mon Oct 31 12:01:24 2022
InstallationDate: Installed on 2022-03-01 (244 days ago)
InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
IpRoute:
 default via 192.168.42.129 dev enx025505083162 proto dhcp src 192.168.42.54 
metric 100 
 169.254.0.0/16 dev enx025505083162 scope link metric 1000 
 192.168.42.0/24 dev enx025505083162 proto kernel scope link src 192.168.42.54 
metric 100
SourcePackage: network-manager
UpgradeStatus: Upgraded to kinetic on 2022-10-22 (9 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
WWAN-HW  WWAN
 running  1.40.0   connected  started  full  enabled enabled  
disabled  missing  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug kinetic

** Attachment added: "3.png"
   https://bugs.launchpad.net/bugs/1995297/+attachment/5628051/+files/3.png

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

Title:
  Wi-Fi and bluetooth appear as disabled

Status in network-manager package in Ubuntu:
  New

Bug description:
  According to rfkill, my Bluetooth (and Wi-Fi) devices are "blocked by
  hardware". Nonetheless, bluetooth is functional, when connected to a
  device.

  When there's no active connection, bluetooth appears as disabled in the panel.
  When I turn on a device that's already peered, it gets automatically 
connected and the popout message when I place the cursor in the panel's icon 
reads "bluetooth active- One active connection". 
  But when I click on the bluetooth icon on the panel, an error message appears 
that reads that bluetooth is OFF, but in reality it is ON and CONNECTED to a 
device.

  Something similar might be happening to the Wi-Fi as it is also shown
  as "disabled" and can't be enabled.

  PS. Some days they have worked fine. I mean, I have turned on the
  laptop and "magically" both bluetooth and wifi were working.

  But, unfortunately they aren't working now and haven't been working
  for a few days already.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: network-manager 1.40.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Mon Oct 31 12:01:24 2022
  InstallationDate: Installed on 2022-03-01 (244 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  IpRoute:
   default via 192.168.42.129 dev enx025505083162 proto dhcp src 192.168.42.54 
metric 100 
   169.254.0.0/16 dev enx025505083162 scope link metric 1000 
   192.168.42.0/24 dev enx025505083162 proto kernel scope link src 
192.168.42.54 metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to kinetic on 2022-10-22 (9 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
disabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1995297/+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 1995201] Re: remote desktop screen sharing does not work

[Pascal Nowack]

Screen sharing with RDP was indeed advertised with the Ubuntu 22.04 release, 
because it is part of GNOME 42 (see the release notes).
This uses the RDP backend in GNOME Remote Desktop (g-r-d) and has nothing to do 
with xrdp, which you apparently installed additionally.

With the extra installation of xrdp, you basically fucked up your system, since 
both g-r-d and xrdp are RDP servers and they are fighting over the RDP port 
(3389).
Screen sharing with g-r-d is literally a one-click-experience, meaning it just 
needs to be turned on g-c-c. g-r-d is also not limited to x11 and works in 
Wayland too.

What you did here was mixing g-r-d with xrdp (same with the links you
posted) and blaming this on Ubuntu. This is a classic example of a
PICNIC issue (Problem In Chair, Not In Computer).

I suggest you to look up what the RDP protocol is (you apparently don't
know (protocol vs implementation(s))), and look into the respective
Ubuntu help, as it tells how to connect to an RDP server (and especially
g-r-d) with an RDP client.

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

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

Title:
  remote desktop screen sharing does not work

Status in remmina package in Ubuntu:
  Invalid

Bug description:
  https://www.omgubuntu.co.uk/2022/06/use-ipad-as-second-monitor-
  ubuntu-22-04 and

  
https://www.reddit.com/r/gnome/comments/uz5as7/gnome_has_made_it_super_simple_to_extend_your/

  https://ubuntuhandbook.org/index.php/2022/04/ubuntu-22-04-remote-
  desktop-control/

  advertise screen sharing via rdp on Ubuntu 22.04 and I hoped to be
  able to use it.

  Unfortunately on multiple machines i was not able to get it working
  and it seems for various reasons. On the other hand i couldn't find
  proper bug reports yet.

  There are quite a few stackexhange questons out there related to 22.04 remote 
desktop sharing such as
  * https://askubuntu.com/questions/1407444/ubuntu-22-04-remote-deskop-headless
  * 
https://askubuntu.com/questions/1403943/22-04-remote-desktop-sharing-authentication-password-changes-every-reboot
  * 
https://askubuntu.com/questions/1406292/remote-desktop-via-vnc-is-black-mouse-keyboard-works
  * 
https://askubuntu.com/questions/1404245/remote-desktop-from-windows-onto-ubuntu-22-04-takes-me-to-a-xrdp-login-then-a-bl
  * 
https://askubuntu.com/questions/1404245/remote-desktop-from-windows-onto-ubuntu-22-04-takes-me-to-a-xrdp-login-then-a-bl

  I'd expect that the remote desktop sharing works out of the box and needs no 
further configuration and fiddling. Especially it should work if already logged 
in. There seem to be so many parts involved in this that 
  there is IMHO a need to have a look at this from an overarching enduser 
viewpoint instead of assuming that users have to take a sysadmin course to use 
Ubuntu 22.04 LTS remote desktop sharing. After all this is version 22 of the 
system and not trying to implement bug #1 of Ubuntu.

  
  Let's start with the machine where i think things are getting close to 
working and the message in /var/log/syslog is:
  ```
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [WARN ] Timed out waiting for X 
server on display 11 to startup
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Session started 
successfully for user wf on display 11
  Oct 30 11:02:57 capri xrdp-sesman[102029]: [INFO ] Starting the xrdp channel 
server for display 11
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Session in progress on 
display 11, waiting until the window manager (pid 101543) exits to end the 
session
  Oct 30 11:02:57 capri xrdp-sesman[101543]: [WARN ] Timed out waiting for X 
server on display 11 to startup
  Oct 30 11:02:57 capri xrdp-sesman[101543]: [ERROR] There is no X server 
active on display 11
  Oct 30 11:02:57 capri xrdp-sesman[101543]: [ERROR] A fatal error has occured 
attempting to start the window manager on display 11, aborting connection
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [WARN ] Window manager (pid 
101543, display 11) exited quickly (0 secs). This could indicate a window 
manager config problem
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Calling auth_stop_session 
and auth_end from pid 101542
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Terminating X server (pid 
101544) on display 11
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Terminating the xrdp 
channel server (pid 102029) on display 11
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] X server on display 11 
(pid 101544) returned exit code 1 and signal number 0
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] xrdp channel server for 
display 11 (pid 102029) exit code 0 and signal number 0
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] cleanup_sockets:
  Oct 30 11:02:57 capri xrdp-sesman[1287]: [INFO ] ++ terminated session:  
username wf, display :11.0, session_pid 

[Desktop-packages] [Bug 1993809] Re: Update gnome-shell to 42.5

[Nathan Teodosio]

I verified the SRU by installing the gnome-shell from proposed,
42.5-0ubuntu1. The test succeeded.

I followed the test cases in
https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell.

For the test case 1, I couldn't notice any problem in any of the 4
sessions, with moving windows, tiling, application panel etc.

For the test case 2, I enabled all the extensions without error. To the
best of my knowledge of their functionality, they behaved fine. I also
installed Hexchat and confirmed that the tray icon showed up, so the
Appindicator extension is working.

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

Title:
  Update gnome-shell to 42.5

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

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 42 series.

  https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.5/NEWS

  The version currently in Ubuntu 22.04.1 LTS is 42.4

  Test Case
  -
  Complete all the test cases at 
https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell

  What Could Go Wrong
  ---
  GNOME Shell is the heart of the Ubuntu desktop experience.

  A severe enough bug could mean that people are unable to use their
  desktop version of Ubuntu.

  Smaller bugs could interrupt people's workflows.

  GNOME Shell is included in the GNOME micro release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Other Info
  --
  I also cherry-picked a fix from kinetic:
  gsettings org.gnome.settings-daemon.peripherals.mouse
  no longer exists in Ubuntu 22.04 LTS so I updated the apport script to stop 
trying to report customizations for that gsettings schema.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993809/+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 1994697] Re: 1440x900 (3:2) resolution mismatch

[Daniel van Vugt]

Thanks for the bug report. I would like to establish if this is a bug in
the Xorg driver or the bad(?) resolution is coming from the kernel.

Please run:

  grep . /sys/class/drm/*/modes

and tell us if you see the correct resolution there.


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

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

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

Title:
  1440x900 (3:2) resolution mismatch

Status in Ubuntu:
  Incomplete

Bug description:
  The listed resolution 1440x900 (3:2) it's not correct: my monitor is 16:10 
and I can see black bars.
  I suppose the real resolution is 1440x960 (3:2), but the actual 1440x900 
(16:10) is missing.

  I updated some packages today and the issue came after reboot:

  2022-10-26 16:48:06 upgrade google-chrome-stable:amd64 106.0.5249.119-1 
107.0.5304.68-1
  2022-10-26 16:48:14 upgrade tzdata:all 2022c-0ubuntu0.22.04.0 
2022e-0ubuntu0.22.04.0
  2022-10-26 16:48:14 upgrade alsa-ucm-conf:all 1.2.6.3-1ubuntu1 
1.2.6.3-1ubuntu1.1
  2022-10-26 16:48:14 upgrade docker-ce-cli:amd64 5:20.10.20~3-0~ubuntu-jammy 
5:20.10.21~3-0~ubuntu-jammy
  2022-10-26 16:48:18 upgrade docker-ce:amd64 5:20.10.20~3-0~ubuntu-jammy 
5:20.10.21~3-0~ubuntu-jammy
  2022-10-26 16:48:20 upgrade docker-ce-rootless-extras:amd64 
5:20.10.20~3-0~ubuntu-jammy 5:20.10.21~3-0~ubuntu-jammy
  2022-10-26 16:48:20 upgrade docker-compose-plugin:amd64 2.12.0~ubuntu-jammy 
2.12.2~ubuntu-jammy
  2022-10-26 16:48:21 upgrade docker-scan-plugin:amd64 0.17.0~ubuntu-jammy 
0.21.0~ubuntu-jammy
  2022-10-26 16:48:22 upgrade fwupd:amd64 1.7.5-3 1.7.9-1~22.04.1
  2022-10-26 16:48:22 upgrade libfwupdplugin5:amd64 1.7.5-3 1.7.9-1~22.04.1
  2022-10-26 16:48:22 upgrade libfwupd2:amd64 1.7.5-3 1.7.9-1~22.04.1
  2022-10-26 16:48:22 upgrade gdb:amd64 12.0.90-0ubuntu1 12.1-0ubuntu1~22.04
  2022-10-26 16:48:22 upgrade grub-efi-amd64:amd64 2.06-2ubuntu7 2.06-2ubuntu10
  2022-10-26 16:48:22 upgrade grub-efi-amd64-signed:amd64 1.180+2.06-2ubuntu7 
1.182~22.04.1+2.06-2ubuntu10
  2022-10-26 16:48:22 upgrade grub-efi-amd64-bin:amd64 2.06-2ubuntu7 
2.06-2ubuntu10
  2022-10-26 16:48:22 upgrade linux-firmware:all 
20220329.git681281e4-0ubuntu3.5 20220329.git681281e4-0ubuntu3.6
  2022-10-26 16:48:26 upgrade qemu-system-gui:amd64 1:6.2+dfsg-2ubuntu6.4 
1:6.2+dfsg-2ubuntu6.5
  2022-10-26 16:48:26 upgrade qemu-block-extra:amd64 1:6.2+dfsg-2ubuntu6.4 
1:6.2+dfsg-2ubuntu6.5
  2022-10-26 16:48:26 upgrade qemu-system-x86:amd64 1:6.2+dfsg-2ubuntu6.4 
1:6.2+dfsg-2ubuntu6.5
  2022-10-26 16:48:26 upgrade qemu-system-common:amd64 1:6.2+dfsg-2ubuntu6.4 
1:6.2+dfsg-2ubuntu6.5
  2022-10-26 16:48:26 upgrade qemu-utils:amd64 1:6.2+dfsg-2ubuntu6.4 
1:6.2+dfsg-2ubuntu6.5
  2022-10-26 16:48:26 upgrade qemu-system-data:all 1:6.2+dfsg-2ubuntu6.4 
1:6.2+dfsg-2ubuntu6.5
  2022-10-26 16:48:27 upgrade snapd:amd64 2.57.4+22.04 2.57.5+22.04
  2022-10-26 16:48:27 upgrade teamviewer:amd64 15.34.4 15.35.5
  2022-10-26 16:48:34 upgrade xserver-common:all 2:21.1.3-2ubuntu2.1 
2:21.1.3-2ubuntu2.2
  2022-10-26 16:48:34 upgrade xserver-xephyr:amd64 2:21.1.3-2ubuntu2.1 
2:21.1.3-2ubuntu2.2
  2022-10-26 16:48:35 upgrade xserver-xorg-legacy:amd64 2:21.1.3-2ubuntu2.1 
2:21.1.3-2ubuntu2.2
  2022-10-26 16:48:35 upgrade xserver-xorg-core:amd64 2:21.1.3-2ubuntu2.1 
2:21.1.3-2ubuntu2.2
  2022-10-26 16:48:35 upgrade sssd:amd64 2.6.3-1ubuntu3.1 2.6.3-1ubuntu3.2
  2022-10-26 16:48:35 upgrade python3-sss:amd64 2.6.3-1ubuntu3.1 
2.6.3-1ubuntu3.2
  2022-10-26 16:48:35 upgrade sssd-proxy:amd64 2.6.3-1ubuntu3.1 2.6.3-1ubuntu3.2
  2022-10-26 16:48:35 upgrade sssd-krb5:amd64 2.6.3-1ubuntu3.1 2.6.3-1ubuntu3.2
  2022-10-26 16:48:35 upgrade sssd-ad:amd64 2.6.3-1ubuntu3.1 2.6.3-1ubuntu3.2
  2022-10-26 16:48:35 upgrade sssd-ldap:amd64 2.6.3-1ubuntu3.1 2.6.3-1ubuntu3.2
  2022-10-26 16:48:35 upgrade sssd-ipa:amd64 2.6.3-1ubuntu3.1 2.6.3-1ubuntu3.2
  2022-10-26 16:48:35 upgrade sssd-krb5-common:amd64 2.6.3-1ubuntu3.1 
2.6.3-1ubuntu3.2
  2022-10-26 16:48:35 upgrade sssd-ad-common:amd64 2.6.3-1ubuntu3.1 
2.6.3-1ubuntu3.2
  2022-10-26 16:48:35 upgrade sssd-common:amd64 2.6.3-1ubuntu3.1 
2.6.3-1ubuntu3.2
  2022-10-26 16:48:35 upgrade libnss-sss:amd64 2.6.3-1ubuntu3.1 2.6.3-1ubuntu3.2
  2022-10-26 16:48:36 upgrade libpam-sss:amd64 2.6.3-1ubuntu3.1 2.6.3-1ubuntu3.2
  2022-10-26 16:48:36 upgrade libsss-certmap0:amd64 2.6.3-1ubuntu3.1 
2.6.3-1ubuntu3.2
  2022-10-26 16:48:36 upgrade libsss-nss-idmap0:amd64 2.6.3-1ubuntu3.1 
2.6.3-1ubuntu3.2
  2022-10-26 16:48:36 upgrade libsss-idmap0:amd64 2.6.3-1ubuntu3.1 
2.6.3-1ubuntu3.2
  2022-10-26 16:48:36 upgrade libipa-hbac0:amd64 2.6.3-1ubuntu3.1 
2.6.3-1ubuntu3.2
  2022-10-26 16:48:36 upgrade ovmf:all 2022.02-3 2022.02-3ubuntu0.22.04.1

  I suppose this bug is here:

  2022-10-26 16:48:34 upgrade xserver-common:all 2:21.1.3-2ubuntu2.1 
2:21.1.3-2ubuntu2.2
  2022-10-26 16:48:34 upgrade xserver-xephyr:amd64 

[Desktop-packages] [Bug 1989964] Re: Segmentation fault crocus_dri.so (X server dies)

[Simon IJskes]

is this read/followed by upstream? or should i find upstream myself to
report it?

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

Title:
  Segmentation fault crocus_dri.so (X server dies)

Status in mesa package in Ubuntu:
  New

Bug description:
  The desktop session is running for 0 or more days. Suddenly the X
  server dies, and login screen reappears.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Sep 16 14:45:54 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:18e4]
  MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic 
root=/dev/mapper/sun--vg-root ro
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2015
  dmi.bios.release: 2.59
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.59
  dmi.board.name: 18E4
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.59:bd03/16/2015:br2.59:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:skuC8N27AV:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G1 TWR
  dmi.product.sku: C8N27AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1989964/+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 1994519] Re: DisplayLink display is black on plug-in and mutter crash after moving cursor on DisplayLink display.

[Daniel van Vugt]

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

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

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

Title:
  DisplayLink display is black on plug-in and mutter crash after moving
  cursor on DisplayLink display.

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

Bug description:
  
  This is recent regression with reproduction rate 100%.
  This is regression mutter-43, Ubuntu 22.04 works fine.

  Bug is raised on Gnome/mutter:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2481
  Fix is under review:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2676

  
  ### Steps to reproduce

  1. Login
  2. Attach DisplayLink device with display connected
  3. Notice that display is visible in Display Preferences but display stays 
blank.
  4. Move cursor over DisplayLink display.
  5. Mutter crashes.

  
  ### What happened

  Mutter crashes, user is asked to log-in again.

  ### What did you expect to happen

  Mutter does not crash.

  ### Relevant logs, screenshots, screencasts etc.
  Crash in line:
  
https://gitlab.gnome.org/GNOME/mutter/-/blob/main/src/backends/native/meta-renderer-native.c#L226

  Crash backtrace:
  ```
  Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) at 
../src/backends/native/meta-renderer-native.c:204
  204   render_device = renderer_gpu_data->render_device;
  (gdb) bt
  #0  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) 
at ../src/backends/native/meta-renderer-native.c:204
  #1  0x7f9209c06674 in create_cursor_drm_buffer (gpu_kms=0x55eb13bc9e00, 
device_file=0x55eb15eaa860, pixels=0x7f91b4bb9700 "", width=24, height=24, 
stride=96, cursor_width=64, cursor_height=64, format=875713089, 
error=0x7ffda9443108) at 
../src/backends/native/meta-cursor-renderer-native.c:1329
  #2  0x7f9209c068b9 in load_cursor_sprite_gbm_buffer_for_gpu 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
pixels=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, 
gbm_format=875713089) at 
../src/backends/native/meta-cursor-renderer-native.c:1399
  #3  0x7f9209c06f98 in load_scaled_and_transformed_cursor_sprite 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
relative_scale=1, relative_transform=META_MONITOR_TRANSFORM_NORMAL, 
data=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, gbm_format=875713089)
  at ../src/backends/native/meta-cursor-renderer-native.c:1574
  #4  0x7f9209c07293 in realize_cursor_sprite_from_wl_buffer_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, 
sprite_wayland=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1670
  #5  0x7f9209c07788 in realize_cursor_sprite_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00) 
at ../src/backends/native/meta-cursor-renderer-native.c:1836
  #6  0x7f9209c077cf in realize_cursor_sprite (renderer=0x55eb1617f580, 
cursor_sprite=0x55eb1918fb00, gpus=0x55eb16345a20 = {...}) at 
../src/backends/native/meta-cursor-renderer-native.c:1854
  #7  0x7f9209c05dd4 in meta_cursor_renderer_native_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1087
  #8  0x7f9209aac8fa in meta_cursor_renderer_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/meta-cursor-renderer.c:413
  #9  0x7f9209aaca07 in meta_cursor_renderer_force_update 
(renderer=0x55eb1617f580) at ../src/backends/meta-cursor-renderer.c:448
  #10 0x7f9209bc4dc6 in update_cursor_sprite_texture 
(cursor_surface=0x55eb1924d880) at 
../src/wayland/meta-wayland-cursor-surface.c:79
  #11 0x7f9209bc512a in meta_wayland_cursor_surface_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-cursor-surface.c:179
  #12 0x7f9209be3774 in meta_wayland_surface_role_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:1938
  #13 0x7f9209be14b6 in meta_wayland_surface_apply_state 
(surface=0x55eb16305e60, state=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:882
  #14 0x7f9209be19c7 in meta_wayland_surface_commit 
(surface=0x55eb16305e60) at ../src/wayland/meta-wayland-surface.c:1038
  #15 0x7f9209be1e9f in wl_surface_commit (client=0x55eb191d7150, 
resource=0x55eb191f1eb0) at ../src/wayland/meta-wayland-surface.c:1191
  #16 0x7f9209d1ae2e in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #17 0x7f9209d17493 in  () at 

[Desktop-packages] [Bug 1994485] Re: Suspend screen bug Gnome and Gnome with video card AMD RX6500XT

[Daniel van Vugt]

If no evidence of a crash can be found then next time it happens please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.


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

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

Title:
  Suspend screen bug Gnome  and Gnome  with video card AMD RX6500XT

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Suspend screen bug Gnome 42 and Gnome 43 with video card AMD RX6500XT

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 26 09:35:26 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-10-26 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994485/+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 1991709] Re: gnome-shell memory leak (when Ubuntu AppIndicators is enabled)

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  gnome-shell memory leak (when Ubuntu AppIndicators is enabled)

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

Bug description:
  over day gnome-shell memory usage increase to 1GB and more. I have 2 enabled 
extensions:
  gnome-extensions list --enabled
  ubuntu-appindicat...@ubuntu.com
  ubuntu-d...@ubuntu.com

  other info: 
  lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  4 22:35:24 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-07-03 (93 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1991709/+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 1994485] Re: Suspend screen bug Gnome and Gnome with video card AMD RX6500XT

[Daniel van Vugt]

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

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

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

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

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

Title:
  Suspend screen bug Gnome  and Gnome  with video card AMD RX6500XT

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Suspend screen bug Gnome 42 and Gnome 43 with video card AMD RX6500XT

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 26 09:35:26 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-10-26 (0 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994485/+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 1994144] Re: External display monitor not recognized

[Daniel van Vugt]

Do you experience the same issue if you log into a Wayland session?

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

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

** Tags added: multimonitor

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

Title:
  External display monitor not recognized

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  xrandr lists four disconnected DPs (though my laptop has zero Display
  Ports) but does not list an HDMI, which is what I use to connect
  external monitor. Cable is sound b/c I have a dual boot setup and
  Windows recognizes the display without issue.

  Using Ubuntu 22.04.1 LTS
  I expected OS to recognize that I have a an HDMI port or alternatively that 
something is plugged into it
  OS does not seem to acknowledge same

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 25 08:45:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: rtl8821ce/5.5.2.1, 5.15.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:899b]
  InstallationDate: Installed on 2022-10-24 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 0bda:b00e Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 002: ID 30c9:0064 Luxvisions Innotech Limited HP TrueVision 
HD Camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 17-cn2xxx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=ec82dd33-2985-40cd-a295-49463eb8e698 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2022
  dmi.bios.release: 15.2
  dmi.bios.vendor: AMI
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 899B
  dmi.board.vendor: HP
  dmi.board.version: 06.26
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 6.26
  dmi.modalias: 
dmi:bvnAMI:bvrF.02:bd08/02/2022:br15.2:efr6.26:svnHP:pnHPLaptop17-cn2xxx:pvr:rvnHP:rn899B:rvr06.26:cvnHP:ct10:cvrChassisVersion:sku641G6UA#ABA:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 17-cn2xxx
  dmi.product.sku: 641G6UA#ABA
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1994144/+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 1994125] Re: [Solved] Gnome desktop freezes after reboot or resume after sleep

[Daniel van Vugt]

Sounds similar but different to bug 1908429. The "offending"
signal/callbacks are different.

** Summary changed:

- [Solved] Gnome desktop freezes after reboot or resume after sleep
+ Attempting to call back into JSAPI during the sweeping phase of GC 
[resource:///org/gnome/shell/ui/calendar.js:320]

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

Title:
  Attempting to call back into JSAPI during the sweeping phase of GC
  [resource:///org/gnome/shell/ui/calendar.js:320]

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After a reboot or resuming from sleep, the desktop appears and is
  fully functional for about 20 seconds. Then the desktop freezes, the
  fan spins up but the mouse still moves. Now click around, open
  programs, execute  to switch programs does nothing. The
  system stays this way for 60 seconds. Then the desktop becomes
  responsive again and all click and keystrokes executed during this
  time are executed. After that the system stays responsive and normal.
  The system log fills up with the following lines (many of them) during
  this period, pointing at a gnome javascript / message queue issue :

  ```
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on 
GDBusProxy 0x559e48c700d0.
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during 
garbage collection. This is most likely
  caused by destroying a Clutter actor or GTK widget with ::destroy signal 
connected, or using the destroy(), dispose(),
  or remove() vfuncs. Because it would crash the application, it has been 
blocked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was 
DBusSignalCallback().
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is mos
  t likely caused by not destroying a Clutter actor or Gtk+ widget with 
::destroy signals connected, but can also be cau
  sed by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked
  and the JS callback not invoked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on 
GDBusProxy 0x559e48c700d0.
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during 
garbage collection. This is most likely
  caused by destroying a Clutter actor or GTK widget with ::destroy signal 
connected, or using the destroy(), dispose(),
  or remove() vfuncs. Because it would crash the application, it has been 
blocked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was 
DBusSignalCallback().
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is mos
  t likely caused by not destroying a Clutter actor or Gtk+ widget with 
::destroy signals connected, but can also be cau
  sed by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked
  and the JS callback not invoked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on 
GDBusProxy 0x559e48c700d0.
  Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during 
garbage collection. This is most likely
  caused by destroying a Clutter actor or GTK widget with ::destroy signal 
connected, or using the destroy(), dispose(),
  or remove() vfuncs. Because it would crash the application, it has been 
blocked.
  Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was 
DBusSignalCallback().
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: linux-image-5.19.0-23-generic 5.19.0-23.24
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robert 2224 F wireplumber
   /dev/snd/controlC1:  robert 2224 F wireplumber
   /dev/snd/seq:robert 2221 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 25 09:49:23 2022
  InstallationDate: Installed on 2022-10-23 (1 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1038:1122 SteelSeries ApS SteelSeries KLC
   Bus 001 Device 002: ID 1d57:ad03 Xenta [T3] 2.4GHz and IR Air Mouse Remote 
Control
   Bus 001 Device 008: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 

[Desktop-packages] [Bug 1995000] Re: gnome-shell is logging excessively to rsyslogd

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1908429
   gnome-shell fills syslog: Attempting to run a JS callback during garbage 
collection. This is most likely caused by destroying a Clutter actor or GTK 
widget with ::destroy signal connected, or using the destroy(), dispose(), or 
remove() vfuncs. Because it would crash the application, it has been blocked. 
The offending callback was SourceFunc().

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

Title:
  gnome-shell is logging excessively to rsyslogd

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I think this is related/already known:
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1868

  Seeing the same logs posted by Kirill:

  Nov 26 04:07:11 ulegion gnome-shell[3001]: The offending callback was 
SourceFunc().
  Nov 26 04:07:11 ulegion gnome-shell[3001]: == Stack trace for context 
0x561e0c0b71c0 ==
  Nov 26 04:07:11 ulegion gnome-shell[3001]: Attempting to run a JS callback 
during garbage collection. This is most likely caused by destroying a Clutter 
actor or GTK widget with ::destroy si

  I was low on disk space, making this problem worse. However I've seen
  this happen before with plenty of disk space just not to the degree I
  couldn't use gnome (100%+ CPU). I'm currently using ubuntu 22.04.01
  LTS. But this is an upgrade from 18.04 LTS so perhaps a config/plugin
  carrier over I need to remove. Don't need this solved but reporting in
  case it helps narrow  the issue.

  Release: 22.04.01 LTS
  Package ver: 42.4-0ubuntu0.22.04.1
  Expectation: CPU usage < 10%, not log errors excessively to rsyslogd
  Issue: excessive logging (like 10-100 lines/sec) when an app or plugin 
crashed?

  Thanks!

  -Hagan

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Oct 27 09:57:05 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-07 (1238 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-07-13 (105 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1995000/+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 1994027] Re: Can't move window by drag and drop by using touch screen

[Daniel van Vugt]

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

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

Title:
  Can't move window by drag and drop by using touch screen

Status in Mutter:
  Unknown
Status in OEM Priority Project:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  [Summary]
  For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed.

  [Steps to reproduce]
  1. Install the 22.04
  2. Boot and login
  3. Open a folder
  4. Drag-n-drop the folder with finger touch
  5. Drag-n-drop the folder with the Wacom Pen

  [Expected result]
  Both finger touch and wacom pen work normally.

  [Actual result]
  Wacom Pen works normally, finger touch can not move the folder.

  [Failure rate]
  100%

  [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop`
  output]

  [Other Information]
  xorg  1:7.7+23ubuntu2
  mutter-common 42.2-0ubuntu1
  gnome-shell 42.4-0ubuntu0.22.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1994027/+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 1994031] Re: Calendar in the top gets bugged after clicking a date from next month

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1970800
   Clicking a calendar date in the bottom row of the panel calendar causes a 
graphical glitch

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

Title:
  Calendar in the top gets bugged after clicking a date from next month

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Can be easily repeatable. As i said in the summary, calendar at the
  top gets bugged when you click a date from the next month. Restart
  solves it but when i open any app it happens again. If you click a day
  from the present month and then click on a day from the next month, it
  won't happen.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 24 13:27:41 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-10-21 (2 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994031/+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 1994019] Re: Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple

[Daniel van Vugt]

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

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

Title:
  Black screen after login with MUTTER_DEBUG_FORCE_KMS_MODE=simple

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  The same as in bug 1994000. I removed the oibaf PPAs altogether and
  now should be running the standard distro packages. The situation has
  not been solved.

  I also attach the prevboot file.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 24 11:27:47 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-09-26 (27 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-10-20 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994019/+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 1993892] Re: Window area is unusable

[Daniel van Vugt]

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

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

Title:
  Window area is unusable

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  The window area becomes unusable without warning and the same visual
  artefacts are seen (see attached). The system taskbar is still
  responsive, so I can logout/login, which resolves the issues
  temporarily.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 16:10:38 2022
  DistUpgraded: 2022-10-21 06:47:07,363 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:2081]
  InstallationDate: Installed on 2022-10-14 (7 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Intel(R) Client Systems NUC10i5FNH
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_6w0xyh@/vmlinuz-5.19.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_6w0xyh ro quiet splash vt.handoff=1
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago)
  dmi.bios.date: 04/09/2021
  dmi.bios.release: 5.16
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FNCML357.0052.2021.0409.1144
  dmi.board.asset.tag: Default string
  dmi.board.name: NUC10i5FNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M38063-307
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 3.9
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFNCML357.0052.2021.0409.1144:bd04/09/2021:br5.16:efr3.9:svnIntel(R)ClientSystems:pnNUC10i5FNH:pvrM38014-308:rvnIntelCorporation:rnNUC10i5FNB:rvrM38063-307:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC10i5FNHN:
  dmi.product.family: FN
  dmi.product.name: NUC10i5FNH
  dmi.product.sku: BXNUC10i5FNHN
  dmi.product.version: M38014-308
  dmi.sys.vendor: Intel(R) Client Systems
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1993892/+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 1991709] Re: gnome-shell memory leak (when Ubuntu AppIndicators is enabled)

[Daniel van Vugt]

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

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

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

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

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

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

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

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

Title:
  gnome-shell memory leak (when Ubuntu AppIndicators is enabled)

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell-extension-appindicator package in Ubuntu:
  New

Bug description:
  over day gnome-shell memory usage increase to 1GB and more. I have 2 enabled 
extensions:
  gnome-extensions list --enabled
  ubuntu-appindicat...@ubuntu.com
  ubuntu-d...@ubuntu.com

  other info: 
  lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.4-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  4 22:35:24 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-07-03 (93 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1991709/+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 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(

[Daniel van Vugt]

Brad,

I am unable to confirm if that's the same crash but the package you need
to get the fix is 'libmutter-10-0'
https://launchpad.net/ubuntu/jammy/amd64/libmutter-10-0/42.5-0ubuntu1

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

Title:
  gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from
  meta_drm_buffer_gbm_finalize() from g_object_unref() from
  g_object_unref() from g_set_object()

Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Fix Committed
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Committed
Status in mutter source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

  On dual-GPU systems, gnome-shell may crash in
  gbm_surface_release_buffer() during display config changes, like when
  rearranging monitor positions.

  [ Test Plan ]

  1. Find a dual GPU system where both use open source drivers (like Intel + 
AMD).
  2. Ideally also attach one monitor to each GPU.
  3. Open Settings and repeatedly change the monitor layout pressing Apply each 
time.

  Expect: System does not crash.

  [ Where problems could occur ]

  Anywhere to do with screen updates since the entire triple buffering
  patch has been updated.

  [ Other Info ]

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.0-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1969422/+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 1993874] Re: Settings and Quick Menu apply Dark style differently

[ccdisle]

Just reposted the attachment for my message above. I don't get dark bars
when I change to light mode.

** Attachment removed: "Screenshot from 2022-10-31 12-43-53.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993874/+attachment/5628027/+files/Screenshot%20from%202022-10-31%2012-43-53.png

** Attachment added: "Dark mode.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993874/+attachment/5628029/+files/Dark%20mode.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/1993874

Title:
  Settings and Quick Menu apply Dark style differently

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

Bug description:
  I just upgraded to Ubuntu 22.10 and noticed that some of my apps were
  no longer in Dark mode including gedit/chrome. When setting the style
  through the quick menu however, these apps go to Dark mode (presumably
  due to gtk theme being applied). Likewise for the quick menu itself,
  setting the style to Dark in gnome-control-settings doesn't change it
  to dark, it remains light.

  see screenshot attached, you will see that when setting the style to
  Dark in Settings, gedit and the quick menu remain light. I tried to
  logout in case it was an issue with how the settings are applied but
  it didn't help. it's also clear that the toggle in the quick menu
  works as intended so there seems to be an issue with the way gnome-
  control-center applies the Dark style.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 10:21:40 2022
  InstallationDate: Installed on 2022-04-06 (198 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993874/+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 1993874] Re: Settings and Quick Menu apply Dark style differently

[ccdisle]

Light mode screenshot

** Attachment added: "light mode.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993874/+attachment/5628031/+files/light%20mode.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/1993874

Title:
  Settings and Quick Menu apply Dark style differently

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

Bug description:
  I just upgraded to Ubuntu 22.10 and noticed that some of my apps were
  no longer in Dark mode including gedit/chrome. When setting the style
  through the quick menu however, these apps go to Dark mode (presumably
  due to gtk theme being applied). Likewise for the quick menu itself,
  setting the style to Dark in gnome-control-settings doesn't change it
  to dark, it remains light.

  see screenshot attached, you will see that when setting the style to
  Dark in Settings, gedit and the quick menu remain light. I tried to
  logout in case it was an issue with how the settings are applied but
  it didn't help. it's also clear that the toggle in the quick menu
  works as intended so there seems to be an issue with the way gnome-
  control-center applies the Dark style.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 10:21:40 2022
  InstallationDate: Installed on 2022-04-06 (198 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993874/+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 1993874] Re: Settings and Quick Menu apply Dark style differently

[ccdisle]

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

Title:
  Settings and Quick Menu apply Dark style differently

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

Bug description:
  I just upgraded to Ubuntu 22.10 and noticed that some of my apps were
  no longer in Dark mode including gedit/chrome. When setting the style
  through the quick menu however, these apps go to Dark mode (presumably
  due to gtk theme being applied). Likewise for the quick menu itself,
  setting the style to Dark in gnome-control-settings doesn't change it
  to dark, it remains light.

  see screenshot attached, you will see that when setting the style to
  Dark in Settings, gedit and the quick menu remain light. I tried to
  logout in case it was an issue with how the settings are applied but
  it didn't help. it's also clear that the toggle in the quick menu
  works as intended so there seems to be an issue with the way gnome-
  control-center applies the Dark style.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 10:21:40 2022
  InstallationDate: Installed on 2022-04-06 (198 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993874/+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 1981863] Re: gnome calendar does not sync with google calendar

[Parmanand Patidar]

same bug affected ubuntu 22.04

** Changed in: gnome-calendar (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  gnome calendar does not sync with google calendar

Status in gnome-calendar package in Ubuntu:
  Confirmed

Bug description:
  In the newest Ubuntu stable release (22.04), gnome 42.2, gnome
  calendar 41.2 does not sync calendar events from google calendar
  through GOA. But when an event is created in gnome calendar, it is
  synchronized with google calendar. So the synchronization works only
  in one direction.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1981863/+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 1993874] Re: Settings and Quick Menu apply Dark style differently

[Batwam]

Looks like the app itself has a custom dark theme but your window theme
is still light. You would probably get something similar if you used a
custom dark theme in something like chrome/arduino/libreoffice/… . Do
you get a dark top bar when setting to dark in the quick menu?

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

Title:
  Settings and Quick Menu apply Dark style differently

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

Bug description:
  I just upgraded to Ubuntu 22.10 and noticed that some of my apps were
  no longer in Dark mode including gedit/chrome. When setting the style
  through the quick menu however, these apps go to Dark mode (presumably
  due to gtk theme being applied). Likewise for the quick menu itself,
  setting the style to Dark in gnome-control-settings doesn't change it
  to dark, it remains light.

  see screenshot attached, you will see that when setting the style to
  Dark in Settings, gedit and the quick menu remain light. I tried to
  logout in case it was an issue with how the settings are applied but
  it didn't help. it's also clear that the toggle in the quick menu
  works as intended so there seems to be an issue with the way gnome-
  control-center applies the Dark style.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 10:21:40 2022
  InstallationDate: Installed on 2022-04-06 (198 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993874/+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 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop

[Daniel van Vugt]

** Changed in: gtk+3.0 (Ubuntu)
   Status: Confirmed => Incomplete

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

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

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

Title:
  Embedded browser display corruption under Wayland on Pi desktop

Status in gtk+3.0 package in Ubuntu:
  Incomplete
Status in webkit2gtk package in Ubuntu:
  Incomplete
Status in yelp package in Ubuntu:
  Incomplete

Bug description:
  On the jammy Pi desktop, under a wayland session, the body of a window
  containing an HTML renderer (e.g. help text or a login page) displays
  corruption.

  These reproduction cases may not be entirely reliable given that
  *some* pages appear to render correctly, but I'll include a couple in
  the hopes of making it reliably reproducible:

  1. Open the Lights Off game
  2. Select "Help" from the menu
  3. In the help window that appears, select any link

  "Basics", "Rules", and "Strategy" all reliably reproduce the issue for
  me, but "Help Translate" doesn't so you may need to click around some
  links until the corruption appears -- however, once it does even
  navigating back to the prior page which rendered happily now displays
  the same corruption.

  Another reproduction case:

  1. Open the Settings application
  2. Select the Online Applications option from the left
  3. Select the Google entry in the list
  4. The login window that appears always displays corruption for me

  The Microsoft option always reliably corrupts for me, but the Facebook
  one doesn't so again I wonder how reproducible this may be for others
  (might be worth trying several options if the first doesn't display
  corruption).

  The corruption appears in the form of "shredded" content as if a
  horizontal stride is set incorrectly somewhere, but only appears in
  the body of the window; the window decorations are unaffected. I'll
  attach a screenshot of the corrupted help window to illustrate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+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 1993874] Re: Settings and Quick Menu apply Dark style differently

[ccdisle]

In addition to what's mentioned above, I noticed some apps are partially
in dark mode. The top bar is in light mode, while the rest of the window
is in dark mode. See attached screen shot.

** Attachment added: "Screenshot from 2022-10-31 12-43-53.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993874/+attachment/5628027/+files/Screenshot%20from%202022-10-31%2012-43-53.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/1993874

Title:
  Settings and Quick Menu apply Dark style differently

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

Bug description:
  I just upgraded to Ubuntu 22.10 and noticed that some of my apps were
  no longer in Dark mode including gedit/chrome. When setting the style
  through the quick menu however, these apps go to Dark mode (presumably
  due to gtk theme being applied). Likewise for the quick menu itself,
  setting the style to Dark in gnome-control-settings doesn't change it
  to dark, it remains light.

  see screenshot attached, you will see that when setting the style to
  Dark in Settings, gedit and the quick menu remain light. I tried to
  logout in case it was an issue with how the settings are applied but
  it didn't help. it's also clear that the toggle in the quick menu
  works as intended so there seems to be an issue with the way gnome-
  control-center applies the Dark style.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 10:21:40 2022
  InstallationDate: Installed on 2022-04-06 (198 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993874/+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 1995236] Re: Xsessions has_option code error with fix

[Peter D.]

And now OPTIONS has to be exported, 
and probably should be protected against being empty in the new file. So it 
becomes ${OPTIONS:-} and ${1:-}

What else have I missed?

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

Title:
  Xsessions has_option code error with fix

Status in xorg package in Ubuntu:
  New

Bug description:
  Jammy Jellyfish 22.04.1 LTS and others. There have been numerous bug
  reports and failed fixes for this over several years and releases.

  There are a couple of problems in /etc/X11/Xsessions where it fails to
  handle options, causing bogus error messages and, doubtless, many
  errors.

  The first bug is that the entire options file, including comments, is
  read into a variable.

  Where the variable "OPTIONS" is assigned;

  Replacing "cat" with "grep" strips out comments and blank lines;

  $ diff Xsession Xsession.orig 
  65c65
  < grep -v "^\s*\#\|^\s*$" "$OPTIONFILE"
  ---
  > cat "$OPTIONFILE"

  The second problem is that checking for a non-existent directory
  inside a command substitution does not work.  It just appends garbage
  onto the output string.

  That is probably a bug in BASH, but I defer to your opinion there.

  The immediate work around is to create an empty directory so that the
  test does not fail.  Better still, force the creation of the directory
  and remove the test.

  
  eg. change this;

  OPTIONS="$(
if [ -r "$OPTIONFILE" ]; then
  cat "$OPTIONFILE"
fi
if [ -d /etc/X11/Xsession.options.d ]; then
  run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d 
'\n' cat
fi
  )"

  to this;

  OPTIONSDIR=/etc/X11/Xsession.options.d
  mkdir --parents ${OPTIONSDIR}
  OPTIONS="$(
if [ -r "$OPTIONFILE" ]; then
  grep -v "^\s*\#\|^\s*$" "$OPTIONFILE"
fi
run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d 
'\n' cat
  )"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Oct 31 16:33:14 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.38, 5.15.0-362206031516-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  InstallationDate: Installed on 2022-10-20 (11 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Micro-Star International Co., Ltd. MS-7B89
  ProcKernelCmdLine: ro root=PARTUUID=1c70e394-574c-46cc-a65e-a402f0e077d4 
fbcon=rotate:2 initrd=\initrd.img
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.C0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M MORTAR MAX (MS-7B89)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.C0:bd02/01/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B89
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about 

[Desktop-packages] [Bug 1993874] Re: Settings and Quick Menu apply Dark style differently

[Batwam]

There is, set the style to Dark using the quick menu toggle and don’t
use the Appearance tab in Settings. As long as you don’t go in that
Settings section, the theme will stay dark. I’ve been doing this since I
first noticed the issue and the windows have remained dark.

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

Title:
  Settings and Quick Menu apply Dark style differently

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

Bug description:
  I just upgraded to Ubuntu 22.10 and noticed that some of my apps were
  no longer in Dark mode including gedit/chrome. When setting the style
  through the quick menu however, these apps go to Dark mode (presumably
  due to gtk theme being applied). Likewise for the quick menu itself,
  setting the style to Dark in gnome-control-settings doesn't change it
  to dark, it remains light.

  see screenshot attached, you will see that when setting the style to
  Dark in Settings, gedit and the quick menu remain light. I tried to
  logout in case it was an issue with how the settings are applied but
  it didn't help. it's also clear that the toggle in the quick menu
  works as intended so there seems to be an issue with the way gnome-
  control-center applies the Dark style.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 10:21:40 2022
  InstallationDate: Installed on 2022-04-06 (198 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993874/+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 1993874] Re: Settings and Quick Menu apply Dark style differently

[jl]

Hi, is there a solution(like an update or an extension or something)
this really bothers me a lot

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

Title:
  Settings and Quick Menu apply Dark style differently

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

Bug description:
  I just upgraded to Ubuntu 22.10 and noticed that some of my apps were
  no longer in Dark mode including gedit/chrome. When setting the style
  through the quick menu however, these apps go to Dark mode (presumably
  due to gtk theme being applied). Likewise for the quick menu itself,
  setting the style to Dark in gnome-control-settings doesn't change it
  to dark, it remains light.

  see screenshot attached, you will see that when setting the style to
  Dark in Settings, gedit and the quick menu remain light. I tried to
  logout in case it was an issue with how the settings are applied but
  it didn't help. it's also clear that the toggle in the quick menu
  works as intended so there seems to be an issue with the way gnome-
  control-center applies the Dark style.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-control-center 1:43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 22 10:21:40 2022
  InstallationDate: Installed on 2022-04-06 (198 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to kinetic on 2022-10-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993874/+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 1995134] Re: WiFi captive portals stopped working after Kinetic upgrade

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  WiFi captive portals stopped working after Kinetic upgrade

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After an upgrade from Ubuntu 22.04 to 20.10 NetworkManager no longer
  recognizes captive portals.

  Attempting to run /usr/libexec/gnome-shell-portal-helper produces this
  output:

  (process:166068): Gjs-CRITICAL **: 19:25:08.053: JS ERROR: ImportError: No JS 
module 'fileUtils' found in search path
  @resource:///org/gnome/shell/portalHelper/main.js:13:30
  @:1:14

  
  This may be normal because of the environment, but it is the best I have to 
go on now.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 28 19:26:44 2022
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37
  InstallationDate: Installed on 2019-08-06 (1179 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-10-24 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1995134/+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 1995201] Re: remote desktop screen sharing does not work

[Wolfgang Fahl]

Out of three Ubuntu 22.04 LTS target machines i got remote desktop
working so far on just one.

I had to switch the configuration to wayland as explained in
https://linuxconfig.org/how-to-enable-disable-wayland-on-
ubuntu-22-04-desktop and fix the login keyring by removing it as
described in https://forums.linuxmint.com/viewtopic.php?t=348117

This issue is about avoiding such strange procedures and get a working
remote desktop experience "out of the box".

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

Title:
  remote desktop screen sharing does not work

Status in remmina package in Ubuntu:
  New

Bug description:
  https://www.omgubuntu.co.uk/2022/06/use-ipad-as-second-monitor-
  ubuntu-22-04 and

  
https://www.reddit.com/r/gnome/comments/uz5as7/gnome_has_made_it_super_simple_to_extend_your/

  https://ubuntuhandbook.org/index.php/2022/04/ubuntu-22-04-remote-
  desktop-control/

  advertise screen sharing via rdp on Ubuntu 22.04 and I hoped to be
  able to use it.

  Unfortunately on multiple machines i was not able to get it working
  and it seems for various reasons. On the other hand i couldn't find
  proper bug reports yet.

  There are quite a few stackexhange questons out there related to 22.04 remote 
desktop sharing such as
  * https://askubuntu.com/questions/1407444/ubuntu-22-04-remote-deskop-headless
  * 
https://askubuntu.com/questions/1403943/22-04-remote-desktop-sharing-authentication-password-changes-every-reboot
  * 
https://askubuntu.com/questions/1406292/remote-desktop-via-vnc-is-black-mouse-keyboard-works
  * 
https://askubuntu.com/questions/1404245/remote-desktop-from-windows-onto-ubuntu-22-04-takes-me-to-a-xrdp-login-then-a-bl
  * 
https://askubuntu.com/questions/1404245/remote-desktop-from-windows-onto-ubuntu-22-04-takes-me-to-a-xrdp-login-then-a-bl

  I'd expect that the remote desktop sharing works out of the box and needs no 
further configuration and fiddling. Especially it should work if already logged 
in. There seem to be so many parts involved in this that 
  there is IMHO a need to have a look at this from an overarching enduser 
viewpoint instead of assuming that users have to take a sysadmin course to use 
Ubuntu 22.04 LTS remote desktop sharing. After all this is version 22 of the 
system and not trying to implement bug #1 of Ubuntu.

  
  Let's start with the machine where i think things are getting close to 
working and the message in /var/log/syslog is:
  ```
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [WARN ] Timed out waiting for X 
server on display 11 to startup
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Session started 
successfully for user wf on display 11
  Oct 30 11:02:57 capri xrdp-sesman[102029]: [INFO ] Starting the xrdp channel 
server for display 11
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Session in progress on 
display 11, waiting until the window manager (pid 101543) exits to end the 
session
  Oct 30 11:02:57 capri xrdp-sesman[101543]: [WARN ] Timed out waiting for X 
server on display 11 to startup
  Oct 30 11:02:57 capri xrdp-sesman[101543]: [ERROR] There is no X server 
active on display 11
  Oct 30 11:02:57 capri xrdp-sesman[101543]: [ERROR] A fatal error has occured 
attempting to start the window manager on display 11, aborting connection
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [WARN ] Window manager (pid 
101543, display 11) exited quickly (0 secs). This could indicate a window 
manager config problem
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Calling auth_stop_session 
and auth_end from pid 101542
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Terminating X server (pid 
101544) on display 11
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Terminating the xrdp 
channel server (pid 102029) on display 11
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] X server on display 11 
(pid 101544) returned exit code 1 and signal number 0
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] xrdp channel server for 
display 11 (pid 102029) exit code 0 and signal number 0
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] cleanup_sockets:
  Oct 30 11:02:57 capri xrdp-sesman[1287]: [INFO ] ++ terminated session:  
username wf, display :11.0, session_pid 101542, ip :::2.0.0.10:59651 - 
socket: 12
  ```

  And i get a black screen in the rdp client on my mac os machine from
  which i try to connect with Microsoft Remote Desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1995201/+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 1995201] Re: remote desktop screen sharing does not work

[Wolfgang Fahl]

This bug is indeed overlapping multiple packages which i think should
not be an obstacle to improving ubuntu.

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

Title:
  remote desktop screen sharing does not work

Status in remmina package in Ubuntu:
  New

Bug description:
  https://www.omgubuntu.co.uk/2022/06/use-ipad-as-second-monitor-
  ubuntu-22-04 and

  
https://www.reddit.com/r/gnome/comments/uz5as7/gnome_has_made_it_super_simple_to_extend_your/

  https://ubuntuhandbook.org/index.php/2022/04/ubuntu-22-04-remote-
  desktop-control/

  advertise screen sharing via rdp on Ubuntu 22.04 and I hoped to be
  able to use it.

  Unfortunately on multiple machines i was not able to get it working
  and it seems for various reasons. On the other hand i couldn't find
  proper bug reports yet.

  There are quite a few stackexhange questons out there related to 22.04 remote 
desktop sharing such as
  * https://askubuntu.com/questions/1407444/ubuntu-22-04-remote-deskop-headless
  * 
https://askubuntu.com/questions/1403943/22-04-remote-desktop-sharing-authentication-password-changes-every-reboot
  * 
https://askubuntu.com/questions/1406292/remote-desktop-via-vnc-is-black-mouse-keyboard-works
  * 
https://askubuntu.com/questions/1404245/remote-desktop-from-windows-onto-ubuntu-22-04-takes-me-to-a-xrdp-login-then-a-bl
  * 
https://askubuntu.com/questions/1404245/remote-desktop-from-windows-onto-ubuntu-22-04-takes-me-to-a-xrdp-login-then-a-bl

  I'd expect that the remote desktop sharing works out of the box and needs no 
further configuration and fiddling. Especially it should work if already logged 
in. There seem to be so many parts involved in this that 
  there is IMHO a need to have a look at this from an overarching enduser 
viewpoint instead of assuming that users have to take a sysadmin course to use 
Ubuntu 22.04 LTS remote desktop sharing. After all this is version 22 of the 
system and not trying to implement bug #1 of Ubuntu.

  
  Let's start with the machine where i think things are getting close to 
working and the message in /var/log/syslog is:
  ```
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [WARN ] Timed out waiting for X 
server on display 11 to startup
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Session started 
successfully for user wf on display 11
  Oct 30 11:02:57 capri xrdp-sesman[102029]: [INFO ] Starting the xrdp channel 
server for display 11
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Session in progress on 
display 11, waiting until the window manager (pid 101543) exits to end the 
session
  Oct 30 11:02:57 capri xrdp-sesman[101543]: [WARN ] Timed out waiting for X 
server on display 11 to startup
  Oct 30 11:02:57 capri xrdp-sesman[101543]: [ERROR] There is no X server 
active on display 11
  Oct 30 11:02:57 capri xrdp-sesman[101543]: [ERROR] A fatal error has occured 
attempting to start the window manager on display 11, aborting connection
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [WARN ] Window manager (pid 
101543, display 11) exited quickly (0 secs). This could indicate a window 
manager config problem
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Calling auth_stop_session 
and auth_end from pid 101542
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Terminating X server (pid 
101544) on display 11
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Terminating the xrdp 
channel server (pid 102029) on display 11
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] X server on display 11 
(pid 101544) returned exit code 1 and signal number 0
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] xrdp channel server for 
display 11 (pid 102029) exit code 0 and signal number 0
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] cleanup_sockets:
  Oct 30 11:02:57 capri xrdp-sesman[1287]: [INFO ] ++ terminated session:  
username wf, display :11.0, session_pid 101542, ip :::2.0.0.10:59651 - 
socket: 12
  ```

  And i get a black screen in the rdp client on my mac os machine from
  which i try to connect with Microsoft Remote Desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1995201/+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 1995134] Re: WiFi captive portals stopped working after Kinetic upgrade

[Daniel van Vugt]

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

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

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

Title:
  WiFi captive portals stopped working after Kinetic upgrade

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

Bug description:
  After an upgrade from Ubuntu 22.04 to 20.10 NetworkManager no longer
  recognizes captive portals.

  Attempting to run /usr/libexec/gnome-shell-portal-helper produces this
  output:

  (process:166068): Gjs-CRITICAL **: 19:25:08.053: JS ERROR: ImportError: No JS 
module 'fileUtils' found in search path
  @resource:///org/gnome/shell/portalHelper/main.js:13:30
  @:1:14

  
  This may be normal because of the environment, but it is the best I have to 
go on now.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 28 19:26:44 2022
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37
  InstallationDate: Installed on 2019-08-06 (1179 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-10-24 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1995134/+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 1995238] Re: repeatedly crashes on attempting to load "bumble.com" or "web.whatsapp.com"

[Olivier Tilloy]

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

** Also affects: snapd
   Importance: Undecided
   Status: New

** Summary changed:

- repeatedly crashes on attempting to load "bumble.com" or "web.whatsapp.com"
+ snaps randomly crash after some time

** Description changed:

+ This is https://forum.snapcraft.io/t/unsupported-version-0-of-verneed-
+ record-linux-6-0/32160.
+ 
  When I load the web interfaces to these two services, firefox will 
immediately crash. Attempting to run from the command-line produces an error 
message as follows:
  Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: 
/snap/firefox/2015/usr/lib/firefox/firefox: error while loading shared 
libraries: /lib/x86_64-linux-gnu/libdl.so.2: unsupported version 0 of Verneed 
record
  Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: message repeated 2 times: [ 
/snap/firefox/2015/usr/lib/firefox/firefox: /lib/x86_64-linux-gnu/libdl.so.2: 
unsupported version 0 of Verdef record]
  
  The only way to restart firefox is to restart the computer! Logging out
  and in again, then running firefox, produces the same errors.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  Uname: Linux 6.0.6-060006-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Mon Oct 31 19:41:21 2022
  InstallationDate: Installed on 2019-05-26 (1253 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (184 days ago)

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

Title:
  snaps randomly crash after some time

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

Bug description:
  This is https://forum.snapcraft.io/t/unsupported-version-0-of-verneed-
  record-linux-6-0/32160.

  When I load the web interfaces to these two services, firefox will 
immediately crash. Attempting to run from the command-line produces an error 
message as follows:
  Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: 
/snap/firefox/2015/usr/lib/firefox/firefox: error while loading shared 
libraries: /lib/x86_64-linux-gnu/libdl.so.2: unsupported version 0 of Verneed 
record
  Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: message repeated 2 times: [ 
/snap/firefox/2015/usr/lib/firefox/firefox: /lib/x86_64-linux-gnu/libdl.so.2: 
unsupported version 0 of Verdef record]

  The only way to restart firefox is to restart the computer! Logging
  out and in again, then running firefox, produces the same errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  Uname: Linux 6.0.6-060006-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Mon Oct 31 19:41:21 2022
  InstallationDate: Installed on 2019-05-26 (1253 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (184 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1995238/+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 1993308] Re: Update gnome-calendar to 43.1

[Jeremy Bicha]

I installed gnome-calendar 43.1-0ubuntu1 and successfully completed the
test case.

I noticed that dragging an event to a different time slot didn't save to
the correct time, depending on the system timezone. I reported that
issue to GNOME. I verified that the issue also affects Calendar 43.0
currently in Kinetic so this is not a regression. Therefore, I am
marking this SRU as verified.

https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/903

** Bug watch added: gitlab.gnome.org/GNOME/gnome-calendar/-/issues #903
   https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/903

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

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

Title:
  Update gnome-calendar to 43.1

Status in gnome-calendar package in Ubuntu:
  Fix Committed
Status in gnome-calendar source package in Kinetic:
  Fix Committed

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 43 series.
  https://gitlab.gnome.org/GNOME/gnome-calendar/-/blob/43.1/NEWS

  This includes several fixes for recurring calendar events. These bugs
  were considered a release blocker for Fedora 37.

  https://qa.fedoraproject.org/blockerbugs/milestone/37/final/buglist

  Test Case
  -
  Complete the test case from

  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Calendar

  What Could Go Wrong
  ---
  GNOME Calendar is included by default only in the Ubuntu Desktop flavor.

  If there are bugs in GNOME Calendar, Evolution (not installed by
  default) could be used instead.

  GNOME Calendar can sync with Google or Microsoft online calendars.
  Therefore, bugs in editing calendar events can by synced to those
  services.

  GNOME Calendar is part of GNOME Core and is included in the GNOME
  micro release exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1993308/+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 1995238] Re: repeatedly crashes on attempting to load "bumble.com" or "web.whatsapp.com"

[Donald H Locker]

My only recourse seems to be rebooting. Once Firefox crashes, there
seems to be no mechanism to restart it (the Chromium snap fails too)
from the snap binary. For whatever reason, Firefox running from my
Startup Applications succeeds. Once the tabs start crashing, no more web
activity will be possible until I reboot.

lsof -p [Firefox PID] | grep -E '(COMMAND|libdl)'

returns:
COMMAND PID  USERFD   TYPE DEVICE  SIZE/OFF NODE NAME
firefox 3239 donald  mem  REG  7,7 6024 
/usr/lib/x86_64-linux-gnu/libdl-2.31.so (stat: No such file or directory)

sudo grep libdl /proc/3239/maps | less
7f1ecaf5f000-7f1ecaf6 r--p  07:07 6024   
/usr/lib/x86_64-linux-gnu/libdl-2.31.so
7f1ecaf6-7f1ecaf62000 r-xp 1000 07:07 6024   
/usr/lib/x86_64-linux-gnu/libdl-2.31.so
7f1ecaf62000-7f1ecaf63000 r--p 3000 07:07 6024   
/usr/lib/x86_64-linux-gnu/libdl-2.31.so
7f1ecaf63000-7f1ecaf64000 r--p 3000 07:07 6024   
/usr/lib/x86_64-linux-gnu/libdl-2.31.so
7f1ecaf64000-7f1ecaf65000 rw-p 4000 07:07 6024   
/usr/lib/x86_64-linux-gnu/libdl-2.31.so

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

Title:
  repeatedly crashes on attempting to load "bumble.com" or
  "web.whatsapp.com"

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  When I load the web interfaces to these two services, firefox will 
immediately crash. Attempting to run from the command-line produces an error 
message as follows:
  Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: 
/snap/firefox/2015/usr/lib/firefox/firefox: error while loading shared 
libraries: /lib/x86_64-linux-gnu/libdl.so.2: unsupported version 0 of Verneed 
record
  Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: message repeated 2 times: [ 
/snap/firefox/2015/usr/lib/firefox/firefox: /lib/x86_64-linux-gnu/libdl.so.2: 
unsupported version 0 of Verdef record]

  The only way to restart firefox is to restart the computer! Logging
  out and in again, then running firefox, produces the same errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  Uname: Linux 6.0.6-060006-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Mon Oct 31 19:41:21 2022
  InstallationDate: Installed on 2019-05-26 (1253 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (184 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1995238/+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 1995201] Re: remote desktop screen sharing does not work

[Brian Murray]

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

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

Title:
  remote desktop screen sharing does not work

Status in remmina package in Ubuntu:
  New

Bug description:
  https://www.omgubuntu.co.uk/2022/06/use-ipad-as-second-monitor-
  ubuntu-22-04 and

  
https://www.reddit.com/r/gnome/comments/uz5as7/gnome_has_made_it_super_simple_to_extend_your/

  https://ubuntuhandbook.org/index.php/2022/04/ubuntu-22-04-remote-
  desktop-control/

  advertise screen sharing via rdp on Ubuntu 22.04 and I hoped to be
  able to use it.

  Unfortunately on multiple machines i was not able to get it working
  and it seems for various reasons. On the other hand i couldn't find
  proper bug reports yet.

  There are quite a few stackexhange questons out there related to 22.04 remote 
desktop sharing such as
  * https://askubuntu.com/questions/1407444/ubuntu-22-04-remote-deskop-headless
  * 
https://askubuntu.com/questions/1403943/22-04-remote-desktop-sharing-authentication-password-changes-every-reboot
  * 
https://askubuntu.com/questions/1406292/remote-desktop-via-vnc-is-black-mouse-keyboard-works
  * 
https://askubuntu.com/questions/1404245/remote-desktop-from-windows-onto-ubuntu-22-04-takes-me-to-a-xrdp-login-then-a-bl
  * 
https://askubuntu.com/questions/1404245/remote-desktop-from-windows-onto-ubuntu-22-04-takes-me-to-a-xrdp-login-then-a-bl

  I'd expect that the remote desktop sharing works out of the box and needs no 
further configuration and fiddling. Especially it should work if already logged 
in. There seem to be so many parts involved in this that 
  there is IMHO a need to have a look at this from an overarching enduser 
viewpoint instead of assuming that users have to take a sysadmin course to use 
Ubuntu 22.04 LTS remote desktop sharing. After all this is version 22 of the 
system and not trying to implement bug #1 of Ubuntu.

  
  Let's start with the machine where i think things are getting close to 
working and the message in /var/log/syslog is:
  ```
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [WARN ] Timed out waiting for X 
server on display 11 to startup
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Session started 
successfully for user wf on display 11
  Oct 30 11:02:57 capri xrdp-sesman[102029]: [INFO ] Starting the xrdp channel 
server for display 11
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Session in progress on 
display 11, waiting until the window manager (pid 101543) exits to end the 
session
  Oct 30 11:02:57 capri xrdp-sesman[101543]: [WARN ] Timed out waiting for X 
server on display 11 to startup
  Oct 30 11:02:57 capri xrdp-sesman[101543]: [ERROR] There is no X server 
active on display 11
  Oct 30 11:02:57 capri xrdp-sesman[101543]: [ERROR] A fatal error has occured 
attempting to start the window manager on display 11, aborting connection
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [WARN ] Window manager (pid 
101543, display 11) exited quickly (0 secs). This could indicate a window 
manager config problem
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Calling auth_stop_session 
and auth_end from pid 101542
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Terminating X server (pid 
101544) on display 11
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Terminating the xrdp 
channel server (pid 102029) on display 11
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] X server on display 11 
(pid 101544) returned exit code 1 and signal number 0
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] xrdp channel server for 
display 11 (pid 102029) exit code 0 and signal number 0
  Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] cleanup_sockets:
  Oct 30 11:02:57 capri xrdp-sesman[1287]: [INFO ] ++ terminated session:  
username wf, display :11.0, session_pid 101542, ip :::2.0.0.10:59651 - 
socket: 12
  ```

  And i get a black screen in the rdp client on my mac os machine from
  which i try to connect with Microsoft Remote Desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1995201/+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 1900679] Re: [snap] Apparmor audit messages for calls to sched_setaffinity

[Alberto Mardegan]

Thanks Simon for confirming.

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

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

Title:
  [snap] Apparmor audit messages for calls to sched_setaffinity

Status in chromium-browser package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Fix Released

Bug description:
  [T okt   20 12:25:09 2020] audit: type=1326 audit(1603185912.099:210734): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:09 2020] audit: type=1326 audit(1603185912.099:210735): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:12 2020] audit: type=1326 audit(1603185915.095:210736): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:12 2020] audit: type=1326 audit(1603185915.095:210737): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:14 2020] audit: type=1326 audit(1603185917.419:210738): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5
  [T okt   20 12:25:14 2020] audit: type=1326 audit(1603185917.419:210739): 
auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" 
exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e 
syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5

  Things like these just get repeated endlessly and very often, making
  any potential debugging very annoying.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900679/+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 1995238] Re: repeatedly crashes on attempting to load "bumble.com" or "web.whatsapp.com"

[Launchpad Bug Tracker]

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

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

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

Title:
  repeatedly crashes on attempting to load "bumble.com" or
  "web.whatsapp.com"

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  When I load the web interfaces to these two services, firefox will 
immediately crash. Attempting to run from the command-line produces an error 
message as follows:
  Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: 
/snap/firefox/2015/usr/lib/firefox/firefox: error while loading shared 
libraries: /lib/x86_64-linux-gnu/libdl.so.2: unsupported version 0 of Verneed 
record
  Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: message repeated 2 times: [ 
/snap/firefox/2015/usr/lib/firefox/firefox: /lib/x86_64-linux-gnu/libdl.so.2: 
unsupported version 0 of Verdef record]

  The only way to restart firefox is to restart the computer! Logging
  out and in again, then running firefox, produces the same errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  Uname: Linux 6.0.6-060006-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Mon Oct 31 19:41:21 2022
  InstallationDate: Installed on 2019-05-26 (1253 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (184 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1995238/+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 1995201] [NEW] remote desktop screen sharing does not work

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

https://www.omgubuntu.co.uk/2022/06/use-ipad-as-second-monitor-
ubuntu-22-04 and

https://www.reddit.com/r/gnome/comments/uz5as7/gnome_has_made_it_super_simple_to_extend_your/

https://ubuntuhandbook.org/index.php/2022/04/ubuntu-22-04-remote-
desktop-control/

advertise screen sharing via rdp on Ubuntu 22.04 and I hoped to be able
to use it.

Unfortunately on multiple machines i was not able to get it working and
it seems for various reasons. On the other hand i couldn't find proper
bug reports yet.

There are quite a few stackexhange questons out there related to 22.04 remote 
desktop sharing such as
* https://askubuntu.com/questions/1407444/ubuntu-22-04-remote-deskop-headless
* 
https://askubuntu.com/questions/1403943/22-04-remote-desktop-sharing-authentication-password-changes-every-reboot
* 
https://askubuntu.com/questions/1406292/remote-desktop-via-vnc-is-black-mouse-keyboard-works
* 
https://askubuntu.com/questions/1404245/remote-desktop-from-windows-onto-ubuntu-22-04-takes-me-to-a-xrdp-login-then-a-bl
* 
https://askubuntu.com/questions/1404245/remote-desktop-from-windows-onto-ubuntu-22-04-takes-me-to-a-xrdp-login-then-a-bl

I'd expect that the remote desktop sharing works out of the box and needs no 
further configuration and fiddling. Especially it should work if already logged 
in. There seem to be so many parts involved in this that 
there is IMHO a need to have a look at this from an overarching enduser 
viewpoint instead of assuming that users have to take a sysadmin course to use 
Ubuntu 22.04 LTS remote desktop sharing. After all this is version 22 of the 
system and not trying to implement bug #1 of Ubuntu.


Let's start with the machine where i think things are getting close to working 
and the message in /var/log/syslog is:
```
Oct 30 11:02:57 capri xrdp-sesman[101542]: [WARN ] Timed out waiting for X 
server on display 11 to startup
Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Session started successfully 
for user wf on display 11
Oct 30 11:02:57 capri xrdp-sesman[102029]: [INFO ] Starting the xrdp channel 
server for display 11
Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Session in progress on 
display 11, waiting until the window manager (pid 101543) exits to end the 
session
Oct 30 11:02:57 capri xrdp-sesman[101543]: [WARN ] Timed out waiting for X 
server on display 11 to startup
Oct 30 11:02:57 capri xrdp-sesman[101543]: [ERROR] There is no X server active 
on display 11
Oct 30 11:02:57 capri xrdp-sesman[101543]: [ERROR] A fatal error has occured 
attempting to start the window manager on display 11, aborting connection
Oct 30 11:02:57 capri xrdp-sesman[101542]: [WARN ] Window manager (pid 101543, 
display 11) exited quickly (0 secs). This could indicate a window manager 
config problem
Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Calling auth_stop_session 
and auth_end from pid 101542
Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Terminating X server (pid 
101544) on display 11
Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] Terminating the xrdp channel 
server (pid 102029) on display 11
Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] X server on display 11 (pid 
101544) returned exit code 1 and signal number 0
Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] xrdp channel server for 
display 11 (pid 102029) exit code 0 and signal number 0
Oct 30 11:02:57 capri xrdp-sesman[101542]: [INFO ] cleanup_sockets:
Oct 30 11:02:57 capri xrdp-sesman[1287]: [INFO ] ++ terminated session:  
username wf, display :11.0, session_pid 101542, ip :::2.0.0.10:59651 - 
socket: 12
```

And i get a black screen in the rdp client on my mac os machine from
which i try to connect with Microsoft Remote Desktop

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


** Tags: bot-comment
-- 
remote desktop screen sharing does not work
https://bugs.launchpad.net/bugs/1995201
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to remmina in Ubuntu.

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

[Desktop-packages] [Bug 1995245] [NEW] Update gnome-remote-desktop to 43.1

[Jeremy Bicha]

Public bug reported:

Impact
--
This is a new stable release in the GNOME 43 series

It fixes some crashes reported to errors.ubuntu.com

https://gitlab.gnome.org/GNOME/gnome-remote-
desktop/-/compare/43.0...43.1

Test Cases
--
Complete all the test cases from
https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop

except for the "New Audio Forwarding Feature" test case.

What Could Go Wrong
---
RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. 
(Previously only VNC Sharing was offered.)

RDP Sharing can be used for providing remote support so it's important
that this feature works well because it may be difficult for the remote
admin to fix issues in person.

gnome-remote-desktop is part of GNOME Core and falls under the GNOME
Stable Release Update microrelease exception

https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

** Affects: gnome-remote-desktop (Ubuntu)
 Importance: High
 Status: Fix Committed

** Affects: gnome-remote-desktop (Ubuntu Kinetic)
 Importance: High
 Status: Triaged


** Tags: upgrade-software-version

** Also affects: gnome-remote-desktop (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Changed in: gnome-remote-desktop (Ubuntu Kinetic)
   Status: New => Triaged

** Changed in: gnome-remote-desktop (Ubuntu Kinetic)
   Importance: Undecided => High

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

Title:
  Update gnome-remote-desktop to 43.1

Status in gnome-remote-desktop package in Ubuntu:
  Fix Committed
Status in gnome-remote-desktop source package in Kinetic:
  Triaged

Bug description:
  Impact
  --
  This is a new stable release in the GNOME 43 series

  It fixes some crashes reported to errors.ubuntu.com

  https://gitlab.gnome.org/GNOME/gnome-remote-
  desktop/-/compare/43.0...43.1

  Test Cases
  --
  Complete all the test cases from
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop

  except for the "New Audio Forwarding Feature" test case.

  What Could Go Wrong
  ---
  RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. 
(Previously only VNC Sharing was offered.)

  RDP Sharing can be used for providing remote support so it's important
  that this feature works well because it may be difficult for the
  remote admin to fix issues in person.

  gnome-remote-desktop is part of GNOME Core and falls under the GNOME
  Stable Release Update microrelease exception

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1995245/+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 1995236] Re: Xsessions has_option code error with fix

[Peter D.]

Bother.  There is a third problem, a scope issue of some sort. 
The errors in ~/.xsession.error go away if "has_options" is moved from Xsession 
to its own file in Xsession.d

I don't see why sourceing it should make any difference, but it does.

$ cat /etc/X11/Xsession.d/00
has_option () {
  # Ensure that a later no-foo overrides an earlier foo
  if [ "$(echo "$OPTIONS" | grep -Eo "^(no-)?$1\>" | tail -n 1)" == "$1" ]; then
return 0
  else
return 1
  fi
}

Also I changed a "=" to "==", but that should be cosmetic.

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

Title:
  Xsessions has_option code error with fix

Status in xorg package in Ubuntu:
  New

Bug description:
  Jammy Jellyfish 22.04.1 LTS and others. There have been numerous bug
  reports and failed fixes for this over several years and releases.

  There are a couple of problems in /etc/X11/Xsessions where it fails to
  handle options, causing bogus error messages and, doubtless, many
  errors.

  The first bug is that the entire options file, including comments, is
  read into a variable.

  Where the variable "OPTIONS" is assigned;

  Replacing "cat" with "grep" strips out comments and blank lines;

  $ diff Xsession Xsession.orig 
  65c65
  < grep -v "^\s*\#\|^\s*$" "$OPTIONFILE"
  ---
  > cat "$OPTIONFILE"

  The second problem is that checking for a non-existent directory
  inside a command substitution does not work.  It just appends garbage
  onto the output string.

  That is probably a bug in BASH, but I defer to your opinion there.

  The immediate work around is to create an empty directory so that the
  test does not fail.  Better still, force the creation of the directory
  and remove the test.

  
  eg. change this;

  OPTIONS="$(
if [ -r "$OPTIONFILE" ]; then
  cat "$OPTIONFILE"
fi
if [ -d /etc/X11/Xsession.options.d ]; then
  run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d 
'\n' cat
fi
  )"

  to this;

  OPTIONSDIR=/etc/X11/Xsession.options.d
  mkdir --parents ${OPTIONSDIR}
  OPTIONS="$(
if [ -r "$OPTIONFILE" ]; then
  grep -v "^\s*\#\|^\s*$" "$OPTIONFILE"
fi
run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d 
'\n' cat
  )"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Oct 31 16:33:14 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.38, 5.15.0-362206031516-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  InstallationDate: Installed on 2022-10-20 (11 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Micro-Star International Co., Ltd. MS-7B89
  ProcKernelCmdLine: ro root=PARTUUID=1c70e394-574c-46cc-a65e-a402f0e077d4 
fbcon=rotate:2 initrd=\initrd.img
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 2.C0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M MORTAR MAX (MS-7B89)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.C0:bd02/01/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B89
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 

[Desktop-packages] [Bug 1995238] Re: repeatedly crashes on attempting to load "bumble.com" or "web.whatsapp.com"

[robin]

It may be related to this:
https://forum.snapcraft.io/t/unsupported-version-0-of-verneed-record-linux-6-0/32160

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

Title:
  repeatedly crashes on attempting to load "bumble.com" or
  "web.whatsapp.com"

Status in firefox package in Ubuntu:
  New

Bug description:
  When I load the web interfaces to these two services, firefox will 
immediately crash. Attempting to run from the command-line produces an error 
message as follows:
  Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: 
/snap/firefox/2015/usr/lib/firefox/firefox: error while loading shared 
libraries: /lib/x86_64-linux-gnu/libdl.so.2: unsupported version 0 of Verneed 
record
  Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: message repeated 2 times: [ 
/snap/firefox/2015/usr/lib/firefox/firefox: /lib/x86_64-linux-gnu/libdl.so.2: 
unsupported version 0 of Verdef record]

  The only way to restart firefox is to restart the computer! Logging
  out and in again, then running firefox, produces the same errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  Uname: Linux 6.0.6-060006-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Mon Oct 31 19:41:21 2022
  InstallationDate: Installed on 2019-05-26 (1253 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (184 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1995238/+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 1995238] [NEW] repeatedly crashes on attempting to load "bumble.com" or "web.whatsapp.com"

[robin]

Public bug reported:

When I load the web interfaces to these two services, firefox will immediately 
crash. Attempting to run from the command-line produces an error message as 
follows:
Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: 
/snap/firefox/2015/usr/lib/firefox/firefox: error while loading shared 
libraries: /lib/x86_64-linux-gnu/libdl.so.2: unsupported version 0 of Verneed 
record
Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: message repeated 2 times: [ 
/snap/firefox/2015/usr/lib/firefox/firefox: /lib/x86_64-linux-gnu/libdl.so.2: 
unsupported version 0 of Verdef record]

The only way to restart firefox is to restart the computer! Logging out
and in again, then running firefox, produces the same errors.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: firefox 1:1snap1-0ubuntu2
Uname: Linux 6.0.6-060006-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME-Flashback:GNOME
Date: Mon Oct 31 19:41:21 2022
InstallationDate: Installed on 2019-05-26 (1253 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: firefox
UpgradeStatus: Upgraded to jammy on 2022-04-29 (184 days ago)

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


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

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

Title:
  repeatedly crashes on attempting to load "bumble.com" or
  "web.whatsapp.com"

Status in firefox package in Ubuntu:
  New

Bug description:
  When I load the web interfaces to these two services, firefox will 
immediately crash. Attempting to run from the command-line produces an error 
message as follows:
  Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: 
/snap/firefox/2015/usr/lib/firefox/firefox: error while loading shared 
libraries: /lib/x86_64-linux-gnu/libdl.so.2: unsupported version 0 of Verneed 
record
  Oct 31 18:15:47 darwin gnome-panel.desktop[6771]: message repeated 2 times: [ 
/snap/firefox/2015/usr/lib/firefox/firefox: /lib/x86_64-linux-gnu/libdl.so.2: 
unsupported version 0 of Verdef record]

  The only way to restart firefox is to restart the computer! Logging
  out and in again, then running firefox, produces the same errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: firefox 1:1snap1-0ubuntu2
  Uname: Linux 6.0.6-060006-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Mon Oct 31 19:41:21 2022
  InstallationDate: Installed on 2019-05-26 (1253 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: firefox
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (184 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1995238/+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 1995236] [NEW] Xsessions has_option code error with fix

[Peter D.]

Public bug reported:

Jammy Jellyfish 22.04.1 LTS and others. There have been numerous bug
reports and failed fixes for this over several years and releases.

There are a couple of problems in /etc/X11/Xsessions where it fails to
handle options, causing bogus error messages and, doubtless, many
errors.

The first bug is that the entire options file, including comments, is
read into a variable.

Where the variable "OPTIONS" is assigned;

Replacing "cat" with "grep" strips out comments and blank lines;

$ diff Xsession Xsession.orig 
65c65
< grep -v "^\s*\#\|^\s*$" "$OPTIONFILE"
---
> cat "$OPTIONFILE"

The second problem is that checking for a non-existent directory inside
a command substitution does not work.  It just appends garbage onto the
output string.

That is probably a bug in BASH, but I defer to your opinion there.

The immediate work around is to create an empty directory so that the
test does not fail.  Better still, force the creation of the directory
and remove the test.


eg. change this;

OPTIONS="$(
  if [ -r "$OPTIONFILE" ]; then
cat "$OPTIONFILE"
  fi
  if [ -d /etc/X11/Xsession.options.d ]; then
run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d 
'\n' cat
  fi
)"

to this;

OPTIONSDIR=/etc/X11/Xsession.options.d
mkdir --parents ${OPTIONSDIR}
OPTIONS="$(
  if [ -r "$OPTIONFILE" ]; then
grep -v "^\s*\#\|^\s*$" "$OPTIONFILE"
  fi
  run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d 
'\n' cat
)"

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Oct 31 16:33:14 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 virtualbox/6.1.38, 5.15.0-362206031516-generic, x86_64: installed
 virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
InstallationDate: Installed on 2022-10-20 (11 days ago)
InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: Micro-Star International Co., Ltd. MS-7B89
ProcKernelCmdLine: ro root=PARTUUID=1c70e394-574c-46cc-a65e-a402f0e077d4 
fbcon=rotate:2 initrd=\initrd.img
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/01/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 2.C0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450M MORTAR MAX (MS-7B89)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.C0:bd02/01/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B89
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu

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

Title:
  Xsessions has_option code error with fix

Status in xorg package in Ubuntu:
  New

Bug description:
  Jammy Jellyfish 22.04.1 LTS and others. There have been numerous bug
  reports and failed fixes for this over several years and releases.

  There are a couple of problems in /etc/X11/Xsessions where it fails to
  handle options, causing bogus error messages