[Desktop-packages] [Bug 2064535] [NEW] jammy update from 23.0.4 to 23.2.1 dropped transitional packages

[dann frazier]

Public bug reported:

I happened to notice that the bump from 23.0.4 to 23.2.1 in jammy
included a change that dropped a number of transitional packages:

mesa (23.1.4-1) unstable; urgency=medium

  [ Diederik de Haas ]
  * Drop transitional libegl1-mesa package (Closes: #1032712)
  * Drop transitional libgles2-mesa package (Closes: #1032718)
  * Drop transitional libwayland-egl1-mesa package (Closes: #1032737)
  * Drop transitional libgl1-mesa-glx package (Closes: #1032738)
  * d/README.source: Update git repo location to Salsa


Since I did not see that discussed in the SRU bug 2037604, I thought I'd call 
attention to it. No objection to this being closed as Won't Fix.

I don't think this impacts any supported upgrade paths - focal GA'd w/
20.0.4-2ubuntu1 which seems to have already had these transitional
packages in place. This is presumably a practical regression for someone
upgrading an old bionic install straight to jammy but that, of course,
is not supported.

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

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

Title:
  jammy update from 23.0.4 to 23.2.1 dropped transitional packages

Status in mesa package in Ubuntu:
  New

Bug description:
  I happened to notice that the bump from 23.0.4 to 23.2.1 in jammy
  included a change that dropped a number of transitional packages:

  mesa (23.1.4-1) unstable; urgency=medium

[ Diederik de Haas ]
* Drop transitional libegl1-mesa package (Closes: #1032712)
* Drop transitional libgles2-mesa package (Closes: #1032718)
* Drop transitional libwayland-egl1-mesa package (Closes: #1032737)
* Drop transitional libgl1-mesa-glx package (Closes: #1032738)
* d/README.source: Update git repo location to Salsa

  
  Since I did not see that discussed in the SRU bug 2037604, I thought I'd call 
attention to it. No objection to this being closed as Won't Fix.

  I don't think this impacts any supported upgrade paths - focal GA'd w/
  20.0.4-2ubuntu1 which seems to have already had these transitional
  packages in place. This is presumably a practical regression for
  someone upgrading an old bionic install straight to jammy but that, of
  course, is not supported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2064535/+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 1991553] Re: can't add a private PPA

[dann frazier]

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

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

Title:
  can't add a private PPA

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Jammy:
  New

Bug description:
  As per today's discussion in ~is :

  add-apt-repository has a bug when adding a private PPA. Quoting
  ~cjwatson :

  ===
  It asks Launchpad for all your personal archive subscriptions _that have 
tokens_.  But `Person:+archivesubscriptions` also shows subscriptions without 
tokens - the token is generated when you click on Viewt here for the first time.

  Instead, `add-apt-repository` should call `getArchiveSubscriptionURL` (not 
`getArchiveSubscriptionURLs`) for the archive it's interested in.  That 
generates tokens on-demand.  Either it will get an HTTP 401, or it will get a 
URL which it can parse for the username and password.
  ===

  Thanks !

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1991553/+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 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]

[dann frazier]

Upstream bug: https://gitlab.gnome.org/GNOME/gdm/-/issues/808

** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #808
   https://gitlab.gnome.org/GNOME/gdm/-/issues/808

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

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

Title:
  systemd refuses to start secondary Xorg logins
  [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]

Status in gdm:
  Unknown
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I have three accounts and I need all three to run on xorg instead of
  wayland.

  For some reason, when switching accounts, two of them consistently
  start wayland even when I select plain gnome from the gdm menu. To get
  xorg, I need to log out and log in a second time.

  A solution that is supposed to work consists in customizing
  /etc/gdm3/custom.conf (see  https://docs.fedoraproject.org/en-
  US/quick-docs/configuring-xorg-as-default-gnome-session/). This
  solution does not work.

  I have also experimented with the following options:
  DefaultSession=gnome-xorg.desktop
  and
  PreferredDisplayServer=xorg
  Neither appears to set xorg as the default...

  I have found the following bug reported upstream against gdm:
  https://gitlab.gnome.org/GNOME/gdm/-/issues/733.
  It looks like this was fixed a year ago but my system is still affected.

  Note that I am using the gnome-session package. I doubt whether it
  makes any difference but I am adding it for the sake of completeness.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu7
  ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9
  Uname: Linux 6.0.0-1010-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Sun Feb  5 19:44:53 2023
  InstallationDate: Installed on 2022-03-27 (315 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2023-01-30T07:57:48.574915

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/2006059/+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 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]

[dann frazier]

I could not reproduce with kinetic (see my steps in bug 2016193). I went
back to a clean jammy install, reproduced, then upgraded just the gdm3
packages to kinetic's versions, and the problem went away, so it seems
gdm3 in isolation is the relevant difference. I took a look at the
differences between the jammy and kinetic gdm3 source, and there really
isn't that much different. One piece that stood out is the following,
which appears to be a typo:

diff -urpN gdm3-42.0/daemon/gdm-local-display-factory.c 
gdm3-43.0/daemon/gdm-local-display-factory.c
--- gdm3-42.0/daemon/gdm-local-display-factory.c2023-04-17 
15:07:42.0 -0600
+++ gdm3-43.0/daemon/gdm-local-display-factory.c2022-09-20 
09:22:21.0 -0600
@@ -402,7 +402,7 @@ gdm_local_display_factory_create_transie
 display = gdm_local_display_new ();
 g_object_set (G_OBJECT (display),
   "session-type", session_types[0],
-  "supported-session-tyes", session_types,
+  "supported-session-types", session_types,
   NULL);
 is_initial = TRUE;
 }

On a lark, I rebuilt the jammy version of gdm3 to use "supported-
session-types" here, and that seems to have fixed the problem for me. I
can reliable downgrade to the jammy version of gdm3 and reproduce, and
reliably *not* reproduce the bug after installing my patched version.

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

Title:
  systemd refuses to start secondary Xorg logins
  [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I have three accounts and I need all three to run on xorg instead of
  wayland.

  For some reason, when switching accounts, two of them consistently
  start wayland even when I select plain gnome from the gdm menu. To get
  xorg, I need to log out and log in a second time.

  A solution that is supposed to work consists in customizing
  /etc/gdm3/custom.conf (see  https://docs.fedoraproject.org/en-
  US/quick-docs/configuring-xorg-as-default-gnome-session/). This
  solution does not work.

  I have also experimented with the following options:
  DefaultSession=gnome-xorg.desktop
  and
  PreferredDisplayServer=xorg
  Neither appears to set xorg as the default...

  I have found the following bug reported upstream against gdm:
  https://gitlab.gnome.org/GNOME/gdm/-/issues/733.
  It looks like this was fixed a year ago but my system is still affected.

  Note that I am using the gnome-session package. I doubt whether it
  makes any difference but I am adding it for the sake of completeness.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu7
  ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9
  Uname: Linux 6.0.0-1010-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Sun Feb  5 19:44:53 2023
  InstallationDate: Installed on 2022-03-27 (315 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2023-01-30T07:57:48.574915

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2006059/+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 2015386] Re: NVIDIA quad-GPU system crashes starting Wayland session

[dann frazier]

The .crash file from comment 11 has been submitted via ubuntu-bug in bug
2016299 - I'll leave it to the developers to determine which one should
be the dupe.

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

Title:
  NVIDIA quad-GPU system crashes starting Wayland session

Status in mutter package in Ubuntu:
  New

Bug description:
  When logged into a desktop session, I created a new user account and
  then tried to "switch to" it. A new gnome session started for that
  user (test1), but after a few seconds, gnome-shell appears to have
  crashed. This only seems to happen on the first attempt to "switch to"
  a new user.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
  Uname: Linux 5.15.0-69-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..08.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0f.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.89.02  Wed Feb  1 
23:23:25 UTC 2023
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Apr  5 17:23:28 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  MachineType: NVIDIA DGX Station
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic 
root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2018
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0406
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-E-10G WS
  dmi.board.vendor: EMPTY
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: EMPTY
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000:
  dmi.product.family: DGX
  dmi.product.name: DGX Station
  dmi.product.sku: 920-22587-2510-000
  dmi.product.version: System Version
  dmi.sys.vendor: NVIDIA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9
  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/mutter/+bug/2015386/+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 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login

[dann frazier]

Attached

** Attachment added: "_usr_bin_gnome-shell.1001.crash"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015386/+attachment/5663851/+files/_usr_bin_gnome-shell.1001.crash

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

Title:
  gnome-shell crashes after "switching to" a new user from an existing
  login

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When logged into a desktop session, I created a new user account and
  then tried to "switch to" it. A new gnome session started for that
  user (test1), but after a few seconds, gnome-shell appears to have
  crashed. This only seems to happen on the first attempt to "switch to"
  a new user.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
  Uname: Linux 5.15.0-69-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..08.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0f.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.89.02  Wed Feb  1 
23:23:25 UTC 2023
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Apr  5 17:23:28 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  MachineType: NVIDIA DGX Station
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic 
root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2018
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0406
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-E-10G WS
  dmi.board.vendor: EMPTY
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: EMPTY
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000:
  dmi.product.family: DGX
  dmi.product.name: DGX Station
  dmi.product.sku: 920-22587-2510-000
  dmi.product.version: System Version
  dmi.sys.vendor: NVIDIA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9
  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/gnome-shell/+bug/2015386/+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 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login

[dann frazier]

I reset all the relevant packages back to the versions used when I
originally filed this bug (luckily I stashed an sosreport), and I was
able to reproduce.

https://errors.ubuntu.com/user/b18128bc669a4a4d1f371a58f4f5d719833ab52c5ab794dbbc9d9e55b45d12516efcc5085f9d93e4d219bc6948f530cdaa31ddf8e34b7e9242e050c269d729c3

Let me know if that is what you needed.

This is using the UDA (non-server) drivers, but the user for originally
reported the bug to me appears to have been using the -server drivers as
you surmised. I tried switching to the 525-server driver and I still
experienced an issue with switch user, but the symptoms are different.
Instead of entering a new login for a few seconds followed by a gnome-
shell crash, this seemed to immediately kick me out of the switched-to
session with no gnome-shell crash. Since this is likely a different
issue, I reported it as bug 2016193 to keep the threads separate.

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

Title:
  gnome-shell crashes after "switching to" a new user from an existing
  login

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When logged into a desktop session, I created a new user account and
  then tried to "switch to" it. A new gnome session started for that
  user (test1), but after a few seconds, gnome-shell appears to have
  crashed. This only seems to happen on the first attempt to "switch to"
  a new user.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
  Uname: Linux 5.15.0-69-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..08.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0f.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.89.02  Wed Feb  1 
23:23:25 UTC 2023
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Apr  5 17:23:28 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  MachineType: NVIDIA DGX Station
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic 
root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2018
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0406
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-E-10G WS
  dmi.board.vendor: EMPTY
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: EMPTY
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000:
  dmi.product.family: DGX
  dmi.product.name: DGX Station
  dmi.product.sku: 920-22587-2510-000
  dmi.product.version: System Version
  dmi.sys.vendor: NVIDIA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9
  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/gnome-shell/+bug/2015386/+subscriptions


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

[Desktop-packages] [Bug 2016193] [NEW] "switch to" a new user immediately aborts, returns to previous user's session

[dann frazier]

Public bug reported:

Split out from https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/2015386/comments/9 .

I'm using the nvidia 525-server drivers.

When I create a new user, then attempt to "switch to" that user from
another user's GNOME session, the new session immediately aborts and
returns me to the original user's session.

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

** Attachment added: 
"sosreport-nvidia-dgx-station-c25989-2023-04-13-lncndqw.tar.xz"
   
https://bugs.launchpad.net/bugs/2016193/+attachment/5663793/+files/sosreport-nvidia-dgx-station-c25989-2023-04-13-lncndqw.tar.xz

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

Title:
  "switch to" a new user immediately aborts, returns to previous user's
  session

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Split out from https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/2015386/comments/9 .

  I'm using the nvidia 525-server drivers.

  When I create a new user, then attempt to "switch to" that user from
  another user's GNOME session, the new session immediately aborts and
  returns me to the original user's session.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2016193/+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 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login

[dann frazier]

I need to deploy the machine from scratch each time I access it, so I
won't be able to run that command in the same install. I tried
reproducing again from scratch, but this time "switch user" immediately
aborted w/o generating a gnome-shell crash. I'm not sure what was
different - I do know that the nvidia driver I was using has been
updated in the distro, so at least that had changed.

Re: nouveau_dri.so - I realized that I'd only installed the nvidia
driver packages and not the "full stack" - i.e. nvidia-driver-525 and
dependencies. Perhaps I was running with an unsupported config the first
time. I tried installing that stack and reproducing again, but this time
I saw no problem doing "switch user" at all. At that point my
reservation expired and I was unable to collect logs from this session.

Next I'll try to do this all over again, making sure to install both
nvidia-driver-525 linux-modules-nvidia-525-generic and see if I can
reproduce.

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

Title:
  gnome-shell crashes after "switching to" a new user from an existing
  login

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  When logged into a desktop session, I created a new user account and
  then tried to "switch to" it. A new gnome session started for that
  user (test1), but after a few seconds, gnome-shell appears to have
  crashed. This only seems to happen on the first attempt to "switch to"
  a new user.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
  Uname: Linux 5.15.0-69-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..08.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0f.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.89.02  Wed Feb  1 
23:23:25 UTC 2023
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Apr  5 17:23:28 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  MachineType: NVIDIA DGX Station
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic 
root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2018
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0406
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-E-10G WS
  dmi.board.vendor: EMPTY
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: EMPTY
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000:
  dmi.product.family: DGX
  dmi.product.name: DGX Station
  dmi.product.sku: 920-22587-2510-000
  dmi.product.version: System Version
  dmi.sys.vendor: NVIDIA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9
  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/gnome-shell/+bug/2015386/+subscriptions


-- 
Mailing list: 

[Desktop-packages] [Bug 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login

[dann frazier]

** Attachment added: "_usr_bin_gnome-shell.1002.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2015386/+attachment/5661328/+files/_usr_bin_gnome-shell.1002.crash

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: 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/2015386

Title:
  gnome-shell crashes after "switching to" a new user from an existing
  login

Status in gnome-shell package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  When logged into a desktop session, I created a new user account and
  then tried to "switch to" it. A new gnome session started for that
  user (test1), but after a few seconds, gnome-shell appears to have
  crashed. This only seems to happen on the first attempt to "switch to"
  a new user.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
  Uname: Linux 5.15.0-69-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..08.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..0f.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.89.02  Wed Feb  1 
23:23:25 UTC 2023
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Apr  5 17:23:28 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  MachineType: NVIDIA DGX Station
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic 
root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2018
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0406
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-E-10G WS
  dmi.board.vendor: EMPTY
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: EMPTY
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000:
  dmi.product.family: DGX
  dmi.product.name: DGX Station
  dmi.product.sku: 920-22587-2510-000
  dmi.product.version: System Version
  dmi.sys.vendor: NVIDIA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9
  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/gnome-shell/+bug/2015386/+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 2015386] [NEW] gnome-shell crashes after "switching to" a new user from an existing login

[dann frazier]

Public bug reported:

When logged into a desktop session, I created a new user account and
then tried to "switch to" it. A new gnome session started for that user
(test1), but after a few seconds, gnome-shell appears to have crashed.
This only seems to happen on the first attempt to "switch to" a new
user.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
Uname: Linux 5.15.0-69-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file.
.proc.driver.nvidia.gpus..08.00.0: Error: path was not a regular file.
.proc.driver.nvidia.gpus..0e.00.0: Error: path was not a regular file.
.proc.driver.nvidia.gpus..0f.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.89.02  Wed Feb  1 23:23:25 
UTC 2023
 GCC version:
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed Apr  5 17:23:28 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
MachineType: NVIDIA DGX Station
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic 
root=UUID=88df95a6-4fd9-475a-8b59-ad14df1ada5a ro
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/27/2018
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0406
dmi.board.asset.tag: Default string
dmi.board.name: X99-E-10G WS
dmi.board.vendor: EMPTY
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: EMPTY
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0406:bd08/27/2018:br5.11:svnNVIDIA:pnDGXStation:pvrSystemVersion:rvnEMPTY:rnX99-E-10GWS:rvrRev1.xx:cvnEMPTY:ct3:cvrDefaultstring:sku920-22587-2510-000:
dmi.product.family: DGX
dmi.product.name: DGX Station
dmi.product.sku: 920-22587-2510-000
dmi.product.version: System Version
dmi.sys.vendor: NVIDIA
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.9
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: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug crash jammy ubuntu uec-images

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

Title:
  gnome-shell crashes after "switching to" a new user from an existing
  login

Status in gnome-shell package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  When logged into a desktop session, I created a new user account and
  then tried to "switch to" it. A new gnome session started for that
  user (test1), but after a few seconds, gnome-shell appears to have
  crashed. This only seems to happen on the first attempt to "switch to"
  a new user.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
  Uname: Linux 5.15.0-69-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu2: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.gpu3: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..07.00.0: Error: path was not a regular file.
  

[Desktop-packages] [Bug 1958583] Re: entering gnome lockscreen causes astfb displays to hang

[dann frazier]

** Attachment added: "sosreport-starbuck-2022-01-20-ziauesz.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1958583/+attachment/972/+files/sosreport-starbuck-2022-01-20-ziauesz.tar.xz

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

Title:
  entering gnome lockscreen causes astfb displays to hang

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I install ubuntu-desktop on servers with an AMI BMC, I find a
  remote desktop running on the BMC's virtual KVM display hangs when I
  transition to the lock screen. The screen either goes blank and fails
  to wake up on keyboard/mouse input - or the lock screen appears but
  freezes, leaving the clock display frozen in time.

  Correlated with the issue are the following messages in
  /var/log/syslog, which are emitted when I move the mouse cursor while
  the lock screen is frozen:

  Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: 
drmModeAtomicCommit: Invalid argument
  Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: 
drmModeAtomicCommit: Invalid argument
  Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: 
drmModeAtomicCommit: Invalid argument
  Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: 
drmModeAtomicCommit: Invalid argument
  Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: 
drmModeAtomicCommit: Invalid argument
  Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: 
drmModeAtomicCommit: Invalid argument
  Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: 
drmModeAtomicCommit: Invalid argument

  A commonality of these systems is that they use the astfb driver.

  I've found that this issue follows the kernel version. If I run a
  jammy desktop with jammy's 5.15 kernel, this issue occurs. If I
  downgrade just the kernel back to focal's 5.4, the issue vanishes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1958583/+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 1958583] Re: entering gnome lockscreen causes display to hang

[dann frazier]

I found that this issue also impacts upstream kernels, so I bisected and
found that the problem was introduced in this commit:

commit d6ddbd5c97d1b9156646ac5c42b8851edd664ee2
Author: Thomas Zimmermann 
Date:   Thu May 7 11:06:40 2020 +0200

drm/ast: Don't check new mode if CRTC is being disabled

I verified that this issue can still be reproduced with current upstream
(currently between v5.16 & v5.17-rc1), and that reverting the above
patch[*] causes it to go away.

[*] The patch doesn't cleanly revert because the underlying code has
evolved a bit, but it's straightforward to back out:

diff --git a/drivers/gpu/drm/ast/ast_mode.c b/drivers/gpu/drm/ast/ast_mode.c
index 956c8982192b..336c545c46f5 100644
--- a/drivers/gpu/drm/ast/ast_mode.c
+++ b/drivers/gpu/drm/ast/ast_mode.c
@@ -1012,9 +1012,6 @@ static int ast_crtc_helper_atomic_check(struct drm_crtc 
*crtc,
const struct drm_format_info *format;
bool succ;
 
-   if (!crtc_state->enable)
-   return 0; /* no mode checks if CRTC is being disabled */
-
ast_state = to_ast_crtc_state(crtc_state);
 
format = ast_state->format;


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

** Summary changed:

- entering gnome lockscreen causes display to hang
+ entering gnome lockscreen causes astfb displays to hang

** Description changed:

  When I install ubuntu-desktop on servers with an AMI BMC, I find a
- remote desktop running over BMC's virtual KVM display hangs when I
+ remote desktop running on the BMC's virtual KVM display hangs when I
  transition to the lock screen. The screen either goes blank and fails to
  wake up on keyboard/mouse input - or the lock screen appears but
  freezes, leaving the clock display frozen in time.
  
  A commonality of these systems is that they use the astfb driver.
  
  I've found that this symptom follows the kernel. If I run a jammy
  desktop with jammy's 5.15 kernel, this issue occurs. If I downgrade just
  the kernel back to focal's 5.4, the issue vanishes.
  
  Correlated with the issue are the following messages in /var/log/syslog,
  which are emitted when I move the mouse cursor while the lock screen is
  frozen:
  
  Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: 
drmModeAtomicCommit: Invalid argument
  Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: 
drmModeAtomicCommit: Invalid argument
  Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: 
drmModeAtomicCommit: Invalid argument
  Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: 
drmModeAtomicCommit: Invalid argument
  Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: 
drmModeAtomicCommit: Invalid argument
  Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: 
drmModeAtomicCommit: Invalid argument
  Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: 
drmModeAtomicCommit: Invalid argument

** Description changed:

  When I install ubuntu-desktop on servers with an AMI BMC, I find a
  remote desktop running on the BMC's virtual KVM display hangs when I
  transition to the lock screen. The screen either goes blank and fails to
  wake up on keyboard/mouse input - or the lock screen appears but
  freezes, leaving the clock display frozen in time.
- 
- A commonality of these systems is that they use the astfb driver.
- 
- I've found that this symptom follows the kernel. If I run a jammy
- desktop with jammy's 5.15 kernel, this issue occurs. If I downgrade just
- the kernel back to focal's 5.4, the issue vanishes.
  
  Correlated with the issue are the following messages in /var/log/syslog,
  which are emitted when I move the mouse cursor while the lock screen is
  frozen:
  
  Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: 
drmModeAtomicCommit: Invalid argument
  Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: 
drmModeAtomicCommit: Invalid argument
  Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: 
drmModeAtomicCommit: Invalid argument
  Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: 
drmModeAtomicCommit: Invalid argument
  Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: 
drmModeAtomicCommit: Invalid argument
  Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: 
drmModeAtomicCommit: Invalid argument
  Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: 
drmModeAtomicCommit: Invalid argument
+ 
+ A commonality of these systems is that they use the astfb driver.
+ 
+ I've found that this issue follows the kernel version. If I run a jammy
+ desktop with jammy's 5.15 kernel, this issue occurs. If I downgrade just
+ the kernel back to focal's 5.4, the issue vanishes.

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

[Desktop-packages] [Bug 1902898] Re: power-button action inconsistent between user session and greeter

[dann frazier]

Verified - I do now get the prompt! Thanks laney & didrocks!

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

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

Title:
  power-button action inconsistent between user session and greeter

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-settings source package in Focal:
  Fix Committed
Status in ubuntu-settings source package in Hirsute:
  Fix Released

Bug description:
  [Impact] 
  When a user is logged in to the Ubuntu desktop, a power button event will 
cause the user to be prompted to choose if they'd like to proceed with a 
shutdown. However, if the system is sitting at a greeter screen, a power button 
event will instead attempt a suspend w/o prompting. This is due to a different 
set of defaults for the greeter and the user.
  This is a fix for this, aligning all power actions between the greeter 
behaviour and the user session one on the user session.

  [Test Plan] 
  1. Install new package and reboot
  2. On the greeter screen (gdm), press the physical power button of your 
machine.
  3. You should be now prompted about what to do, like shutdown. You can 
dismiss it.
  4. Clicking on the physical suspend button should suspend the machine 
immediatly.

  [Where problems could occur]
  We change the scope of when we applied those settings: we were only applying 
them to the GNOME session ran by the user, and it will now be applied as 
default to the GNOME session ran by gdm.
  Impacts is thus limited to the greeter screen.

  
  Diff is available on this commit: 
https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/ubuntu-settings/commit/?h=focal=ca2f9aa9b03862ff044b64d7ef9506ca87e3dd89

  --
  Original report content:

  For a logged-in desktop user, they
  see:

  $ gsettings get org.gnome.settings-daemon.plugins.power
  power-button-action 'interactive'

  But the gdm user sees:
  $ sudo machinectl shell gdm@ /bin/bash
  Connected to the local host. Press ^] three times within 1s to exit session.
  gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power 
power-button-action
  'suspend'

  Changing the gdm user's setting to "interactive" using gsettings
  causes the greeter to begin prompting, consistent with the logged in
  user experience.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1902898/+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 1920791] Re: KeyError: 'metapackage'

[dann frazier]

** Attachment added: "sosreport-akis-2021-03-22-hgypyvd.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1920791/+attachment/5479223/+files/sosreport-akis-2021-03-22-hgypyvd.tar.xz

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

Title:
  KeyError: 'metapackage'

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  On an Nvidia DGX2 system running bionic w/ ubuntu-drivers-common
  1:0.5.2.5:

  $ sudo ubuntu-drivers list --gpgpu
  nvidia-headless-no-dkms-450, (kernel modules provided by 
linux-modules-nvidia-450-generic)
  nvidia-headless-no-dkms-460, (kernel modules provided by 
linux-modules-nvidia-460-generic)
  Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 267, in 
  sys.exit(list_gpgpu(args))
File "/usr/bin/ubuntu-drivers", line 81, in list_gpgpu
  candidate = packages[package]['metapackage']
  KeyError: 'metapackage'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1920791/+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 1920791] [NEW] KeyError: 'metapackage'

[dann frazier]

Public bug reported:

On an Nvidia DGX2 system running bionic w/ ubuntu-drivers-common
1:0.5.2.5:

$ sudo ubuntu-drivers list --gpgpu
nvidia-headless-no-dkms-450, (kernel modules provided by 
linux-modules-nvidia-450-generic)
nvidia-headless-no-dkms-460, (kernel modules provided by 
linux-modules-nvidia-460-generic)
Traceback (most recent call last):
  File "/usr/bin/ubuntu-drivers", line 267, in 
sys.exit(list_gpgpu(args))
  File "/usr/bin/ubuntu-drivers", line 81, in list_gpgpu
candidate = packages[package]['metapackage']
KeyError: 'metapackage'

** Affects: ubuntu-drivers-common (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  KeyError: 'metapackage'

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  On an Nvidia DGX2 system running bionic w/ ubuntu-drivers-common
  1:0.5.2.5:

  $ sudo ubuntu-drivers list --gpgpu
  nvidia-headless-no-dkms-450, (kernel modules provided by 
linux-modules-nvidia-450-generic)
  nvidia-headless-no-dkms-460, (kernel modules provided by 
linux-modules-nvidia-460-generic)
  Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 267, in 
  sys.exit(list_gpgpu(args))
File "/usr/bin/ubuntu-drivers", line 81, in list_gpgpu
  candidate = packages[package]['metapackage']
  KeyError: 'metapackage'

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

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

Re: [Desktop-packages] [Bug 1902898] Re: power-button action inconsistent between user session and greeter

[dann frazier]

On Tue, Nov 10, 2020 at 7:45 AM Sebastien Bacher
<1902...@bugs.launchpad.net> wrote:
>
> is it important enough to justify doing the SRU work?

>From my myopic (server-oriented) point-of-view, changing the default
in 20.04 to prompt is a good idea. I've found that users often install
Ubuntu Desktop on their server-class hardware, using their BMC virtual
KVM as a head. These systems tend to support suspend, but suspend
rarely works well. Some systems will go to sleep just fine - but have
no way to wake them up[*]. Others will try to suspend, only to
immediately come back out of suspend (presumably after trying to sleep
a device that doesn't support it), so it looks like the system failed
to react at all. Both seem like a non-intuitive reaction to an "IPMI
power off soft" command.

[*] https://bugs.launchpad.net/bugs/1862559

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

Title:
  power-button action inconsistent between user session and greeter

Status in ubuntu-settings package in Ubuntu:
  Confirmed
Status in ubuntu-settings source package in Focal:
  Incomplete
Status in ubuntu-settings source package in Groovy:
  Incomplete
Status in ubuntu-settings source package in Hirsute:
  Confirmed

Bug description:
  When a user is logged in to the Ubuntu desktop, a power button event
  will cause the user to be prompted to choose if they'd like to proceed
  with a shutdown. However, if the system is sitting at a greeter
  screen, a power button event will instead attempt a suspend w/o
  prompting. This is due to a different set of defaults for the greeter
  and the user:

  For a logged-in desktop user, they
  see:

  $ gsettings get org.gnome.settings-daemon.plugins.power
  power-button-action 'interactive'

  But the gdm user sees:
  $ sudo machinectl shell gdm@ /bin/bash
  Connected to the local host. Press ^] three times within 1s to exit session.
  gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power 
power-button-action
  'suspend'

  Changing the gdm user's setting to "interactive" using gsettings
  causes the greeter to begin prompting, consistent with the logged in
  user experience.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1902898/+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 1902898] [NEW] power-button action inconsistent between user session and greeter

[dann frazier]

Public bug reported:

When a user is logged in to the Ubuntu desktop, a power button event
will cause the user to be prompted to choose if they'd like to proceed
with a shutdown. However, if the system is sitting at a greeter screen,
a power button event will instead attempt a suspend w/o prompting. This
is due to a different set of defaults for the greeter and the user:

For a logged-in desktop user, they
see:

$ gsettings get org.gnome.settings-daemon.plugins.power
power-button-action 'interactive'

But the gdm user sees:
$ sudo machinectl shell gdm@ /bin/bash
Connected to the local host. Press ^] three times within 1s to exit session.
gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power power-button-action
'suspend'

Changing the gdm user's setting to "interactive" using gsettings causes
the greeter to begin prompting, consistent with the logged in user
experience.

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: ubuntu-settings (Ubuntu Focal)
 Importance: Undecided
 Status: Confirmed

** Affects: ubuntu-settings (Ubuntu Groovy)
 Importance: Undecided
 Status: New

** Affects: ubuntu-settings (Ubuntu Hirsute)
 Importance: Undecided
 Status: New

** Also affects: ubuntu-settings (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-settings (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-settings (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-settings (Ubuntu Focal)
   Status: New => Confirmed

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

Title:
  power-button action inconsistent between user session and greeter

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Focal:
  Confirmed
Status in ubuntu-settings source package in Groovy:
  New
Status in ubuntu-settings source package in Hirsute:
  New

Bug description:
  When a user is logged in to the Ubuntu desktop, a power button event
  will cause the user to be prompted to choose if they'd like to proceed
  with a shutdown. However, if the system is sitting at a greeter
  screen, a power button event will instead attempt a suspend w/o
  prompting. This is due to a different set of defaults for the greeter
  and the user:

  For a logged-in desktop user, they
  see:

  $ gsettings get org.gnome.settings-daemon.plugins.power
  power-button-action 'interactive'

  But the gdm user sees:
  $ sudo machinectl shell gdm@ /bin/bash
  Connected to the local host. Press ^] three times within 1s to exit session.
  gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power 
power-button-action
  'suspend'

  Changing the gdm user's setting to "interactive" using gsettings
  causes the greeter to begin prompting, consistent with the logged in
  user experience.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1902898/+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 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server

[dann frazier]

gdm3 is being pulled in via a "Recommends" chain. Disabling recommends will 
avoid it[*]. 
On my groovy system it reduced new packages installed from 452/291MB of 
archives to 56/165MB of archives. Seems like the right thing to do for at least 
--gpgpu installs - but maybe for all?

[*]
--- /usr/bin/ubuntu-drivers.orig2020-07-29 15:24:08.0 +
+++ /usr/bin/ubuntu-drivers 2020-10-06 19:18:53.208559657 +
@@ -155,7 +155,8 @@
 return
 
 ret = subprocess.call(['apt-get', 'install', '-o',
-'DPkg::options::=--force-confnew', '-y'] + to_install)
+   'DPkg::options::=--force-confnew', '-y',
+   '--no-install-recommends'] + to_install)
 
 oem_meta_to_install = fnmatch.filter(to_install, 'oem-*-meta')

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

Title:
  'ubuntu-drivers --gpgpu install' installs a lot of unnecessary
  packages, including a full desktop environment on Ubuntu Server

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  When I install the packaged nVidia drivers using --gpgpu, I expect
  that I am getting compute related GPGPU drivers.  Instead, I find that
  on a fresh Focal installation of Ubuntu Server, I also get a full
  desktop environment.

  This sets us up nicely for this bug:
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559

  because this pulls in gdm3 and a whole host of unnecessary desktop
  packages but does nothing to mitigate the gdm3 propensity to
  autosuspend, which makes the server become unresponsive when there is
  no user activity (even when it's running workloads on the GPGPU, the
  server can still autosuspend).

  Additionally, this adds a software stack that causes unnecessary CPU
  and memory usage on a machine that is meant to run headless and devote
  all resources to handling GPGPU compute activities.

  This is gpgpu mode
  
  Reading package lists... Done 
  
  Building dependency tree  
   
  Reading state information... Done 
  
  The following additional packages will be installed:  

apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils 
bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 
dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common 
enchant-2
evolution-data-server evolution-data-server-common fprintd gcr gdm3 
geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 
gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 
gir1.2-gnomebluetooth-1.0
gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 
gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 
gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 
gir1.2-upowerglib-1.0
gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center 
gnome-control-center-data gnome-control-center-faces gnome-desktop3-data 
gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts 
gnome-session-bin gnome-session-common
gnome-settings-daemon gnome-settings-daemon-common gnome-shell 
gnome-shell-common gnome-startup-applications gnome-user-docs 
gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 
iio-sensor-proxy im-config ippusbxd
language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 
libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 
libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 
libcolord-gtk1
libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 
libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 
libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 
libedataserverui-1.2-2
libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 
libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 
libgdm1 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g libgles2
libgnome-autoar-0-0 libgnome-bluetooth13 libgnome-desktop-3-19 
libgnomekbd-common libgnomekbd8 libgoa-1.0-0b libgoa-1.0-common 
libgoa-backend-1.0-1 libgphoto2-6 libgphoto2-l10n libgphoto2-port12 libgsound0 
libgssdp-1.2-0 libgtk2.0-0
libgtk2.0-bin libgtk2.0-common libgtop-2.0-11 libgtop2-common 
libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libgweather-3-16 
libgweather-common libharfbuzz-icu0 libhunspell-1.7-0 libhyphen0 

[Desktop-packages] [Bug 1862559] Re: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min

[dann frazier]

I asked our desktop team about this, and Iain Lane mentioned that Ubuntu
overrides the GNOME default of auto-suspending, but that override only
takes effect if you have the ubuntu-settings package installed. I tested
this out on a Saber system, and I can confirm that it does seem to only
happen when gdm is installed/running and ubuntu-settings is *not*
installed. And that explains why I was unable to reproduce in Comment
#5. There I had installed ubuntu-desktop which would bring in ubuntu-
settings. It also explains why the CUDA-11 dependency chain *did* cause
the problem on the x86 server in Comment #8. In that case, gdm3 is
getting installed as a Recommends somewhere in the dependency chain -
but it does not pull in gnome-settings.

I'll therefore go ahead and close the 'linux' task as Invalid - this
isn't a kernel bug. I'll mark the gdm3 bug as "Won't Fix" because, in
theory, we could change the defaults inside of gdm3 itself - but we
instead recommend users install ubuntu-settings to override the
defaults.

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

** Changed in: gdm3 (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for
  ~22min

Status in gdm3 package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Invalid

Bug description:
  UBUNTU 19.10 installed on ThunderX2 saber ARM64 machine. If the system
  left idle for ~22min it becomes unresponsive. The system will not take
  any inputs like from UART, ping ..etc.  The system will completely
  freeze and we need to hard reset the system.  It could be possible the
  system goes to hibernate state and could not able to come out of the
  state.

  Dmesg log when system halts/no response on Saber boards (TX2)

  Ubuntu 19.10 ubuntu ttyAMA0

  ubuntu login: ubuntu
  Password:
  Last login: Wed Jan 29 20:08:22 PST 2020 on ttyAMA0
  Welcome to Ubuntu 19.10 (GNU/Linux 5.3.0-26-generic aarch64)

  * Documentation:  https://help.ubuntu.com
  * Management: https://landscape.canonical.com
  * Support:https://ubuntu.com/advantage

  ubuntu@ubuntu:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu 19.10
  Release: 19.10
  Codename: eoan

  
  [  +0.732512] audit: type=1400 audit(1580358920.412:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="lsb_release" pid=3087 
comm="apparmor_parser"
  [  +0.64] audit: type=1400 audit(1580358920.412:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/sbin/ippusbxd" 
pid=3091 comm="apparmor_parser"
  [  +0.000168] audit: type=1400 audit(1580358920.412:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=3086 
comm="apparmor_parser"
  [  +0.05] audit: type=1400 audit(1580358920.412:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" 
pid=3086 comm="apparmor_parser"
  [  +0.000546] audit: type=1400 audit(1580358920.412:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=3085 
comm="apparmor_parser"
  [  +0.06] audit: type=1400 audit(1580358920.412:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_filter" pid=3085 
comm="apparmor_parser"
  [  +0.05] audit: type=1400 audit(1580358920.412:8): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_groff" pid=3085 
comm="apparmor_parser"
  [  +0.000854] audit: type=1400 audit(1580358920.412:9): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=3089 
comm="apparmor_parser"
  [  +0.002667] audit: type=1400 audit(1580358920.416:10): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=3093 
comm="apparmor_parser"
  [  +0.04] audit: type=1400 audit(1580358920.416:11): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=3093 
comm="apparmor_parser"
  [  +1.382579] igb :92:00.1 enp146s0f1: igb: enp146s0f1 NIC Link is Up 
1000 Mbps Full Duplex, Flow Control: RX
  [  +0.000299] IPv6: ADDRCONF(NETDEV_CHANGE): enp146s0f1: link becomes ready
  [  +3.131173] mpt3sas_cm0: port enable: SUCCESS
  [Jan29 20:36] random: crng init done
  [  +0.04] random: 7 urandom warning(s) missed due to ratelimiting
  *[Jan29 20:37] rfkill: input handler disabled*
  *[Jan29 20:57] PM: suspend entry (deep)*

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

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

[Desktop-packages] [Bug 1862559] Re: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min

[dann frazier]

@Naresh: see my comment #4, asking if you are running Ubuntu Desktop.
dmesg doesn't tell me that - but an sosreport would, if you can attach
that.

We've recently hit this on an x86 server, and did tie that back to the
system having a desktop installed (Nvidia CUDA 11 somehow brings in gdm
as a dependency), so I'm still suspecting the same here.

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

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

Title:
  ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for
  ~22min

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

Bug description:
  UBUNTU 19.10 installed on ThunderX2 saber ARM64 machine. If the system
  left idle for ~22min it becomes unresponsive. The system will not take
  any inputs like from UART, ping ..etc.  The system will completely
  freeze and we need to hard reset the system.  It could be possible the
  system goes to hibernate state and could not able to come out of the
  state.

  Dmesg log when system halts/no response on Saber boards (TX2)

  Ubuntu 19.10 ubuntu ttyAMA0

  ubuntu login: ubuntu
  Password:
  Last login: Wed Jan 29 20:08:22 PST 2020 on ttyAMA0
  Welcome to Ubuntu 19.10 (GNU/Linux 5.3.0-26-generic aarch64)

  * Documentation:  https://help.ubuntu.com
  * Management: https://landscape.canonical.com
  * Support:https://ubuntu.com/advantage

  ubuntu@ubuntu:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu 19.10
  Release: 19.10
  Codename: eoan

  
  [  +0.732512] audit: type=1400 audit(1580358920.412:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="lsb_release" pid=3087 
comm="apparmor_parser"
  [  +0.64] audit: type=1400 audit(1580358920.412:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/sbin/ippusbxd" 
pid=3091 comm="apparmor_parser"
  [  +0.000168] audit: type=1400 audit(1580358920.412:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=3086 
comm="apparmor_parser"
  [  +0.05] audit: type=1400 audit(1580358920.412:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" 
pid=3086 comm="apparmor_parser"
  [  +0.000546] audit: type=1400 audit(1580358920.412:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=3085 
comm="apparmor_parser"
  [  +0.06] audit: type=1400 audit(1580358920.412:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_filter" pid=3085 
comm="apparmor_parser"
  [  +0.05] audit: type=1400 audit(1580358920.412:8): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_groff" pid=3085 
comm="apparmor_parser"
  [  +0.000854] audit: type=1400 audit(1580358920.412:9): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=3089 
comm="apparmor_parser"
  [  +0.002667] audit: type=1400 audit(1580358920.416:10): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=3093 
comm="apparmor_parser"
  [  +0.04] audit: type=1400 audit(1580358920.416:11): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=3093 
comm="apparmor_parser"
  [  +1.382579] igb :92:00.1 enp146s0f1: igb: enp146s0f1 NIC Link is Up 
1000 Mbps Full Duplex, Flow Control: RX
  [  +0.000299] IPv6: ADDRCONF(NETDEV_CHANGE): enp146s0f1: link becomes ready
  [  +3.131173] mpt3sas_cm0: port enable: SUCCESS
  [Jan29 20:36] random: crng init done
  [  +0.04] random: 7 urandom warning(s) missed due to ratelimiting
  *[Jan29 20:37] rfkill: input handler disabled*
  *[Jan29 20:57] PM: suspend entry (deep)*

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559/+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 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed

[dann frazier]

The ubuntu-drivers-common task here appears to be to change it to prefer
the pre-built/signed drivers (linux-modules-nvidia-*) over the DKMS
counterparts. I'd recommend at that point that we start seeding linux-
modules-nvidia-[0-9]+-generic onto the desktop ISO instead of the DKMS
counterparts, so the offline install experiences matches.

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  nvidia-435 is in eoan, linux-restricted-modules only builds against
  430, ubiquity gives me the self-signed modules experience instead of
  using the Canonical-signed modules

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  New
Status in linux source package in Eoan:
  Fix Released
Status in linux-restricted-modules source package in Eoan:
  Fix Released
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed
Status in ubuntu-drivers-common source package in Eoan:
  Confirmed
Status in ubuntu-meta source package in Eoan:
  New

Bug description:
  SRU Justification

  Impact: The nvidia-435 drivers are missing from linux-restricted-
  modules in eoan. On install ubuntu-drivers picks 435 as the newest
  version, and users must use self-signed dkms drivers and enroll a MOK.

  Fix: Add nvidia-435 dkms builds to linux and l-r-m for eoan.

  Test Case: A test build is available in ppa:sforshee/test-builds.
  Verify that signed drivers for nvidia-435 can be installed for eoan
  via the linux-modules-nvidia-435-{generic,lowlatency} packages.

  Regression Potential: The nvidia-435 l-r-m drivers are new packages
  built from the same source as the nvidia-435 dkms driver, so
  regressions are unlikely.

  ---

  The linux-restricted-modules package exists so that users who install
  the nvidia drivers can get known-good, signed modules instead of
  having to locally self-sign and enroll a signing key through MOK.  But
  lrm in eoan is only building driver packages for nvidia 390 and 430,
  and nvidia 435 is present in eoan.

  So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
  newest driver instead of using the signed 430 driver.

  We should never allow the archive to get into this situation.  We
  should be enforcing that any version of the nvidia driver that we
  expect ubuntu-drivers to install by default on any hardware is
  integrated into linux-restricted-modules, and we should ensure that
  ubuntu-drivers always prefers the signed drivers over other options.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+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 1863812] Re: tells me an update is available, but i'm running a newer version

[dann frazier]

I suspect it did autorefresh, but didn't confirm. But yeah, the issue
IMO is the UI one. Once I click update, I'd expect gnome-software to see
that it was already up to date and respond as though the update was
complete - i.e., go away :)

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

Title:
  tells me an update is available, but i'm running a newer version

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Today I noticed that the software manager is telling me there's a juju
  update available (2.7.1), with an option to update. When I click
  update, it says "Unable to update juju: snap has no updates
  available". Sure enough, `snap info` confirms that I'm already on
  2.7.*2*:

  channels:
stable:2.7.2 2020-02-18 (10671) 72MB classic
candidate: ↑ 
beta:  ↑ 
edge:  2.8-beta1+develop-29900ab 2020-02-18 (10690) 81MB classic
2.7/stable:2.7.2 2020-02-18 (10671) 72MB classic
2.7/candidate: 2.7.3+2.7-aa61342 2020-02-18 (10691) 81MB classic
2.7/beta:  ↑ 
2.7/edge:  2.7.3+2.7-aa61342 2020-02-18 (10691) 81MB classic
2.6/stable:2.6.102019-10-30  (9484) 69MB classic
2.6/candidate: ↑ 
2.6/beta:  ↑ 
2.6/edge:  2.6.11+2.6-b96e1222020-01-22 (10408) 75MB classic
2.5/stable:2.5.8 2019-06-27  (8361) 67MB classic
2.5/candidate: ↑ 
2.5/beta:  ↑ 
2.5/edge:  2.5.9+2.5-36af233 2019-07-24  (8546) 73MB classic
2.4/stable:2.4.7 2019-05-23  (6012) 58MB classic
2.4/candidate: ↑ 
2.4/beta:  ↑ 
2.4/edge:  ↑ 
2.3/stable:2.3.9 2018-09-19  (5267) 55MB classic
2.3/candidate: ↑ 
2.3/beta:  ↑ 
2.3/edge:  2.3.10+2.3-41313d12019-03-25  (7080) 55MB classic
  installed:   2.7.2(10671) 72MB classic

  gnome-software 3.35.2-0ubuntu2
  snapd 2.43.3+git1.8109f8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1863812/+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 1863812] [NEW] tells me an update is available, but i'm running a newer version

[dann frazier]

Public bug reported:

Today I noticed that the software manager is telling me there's a juju
update available (2.7.1), with an option to update. When I click update,
it says "Unable to update juju: snap has no updates available". Sure
enough, `snap info` confirms that I'm already on 2.7.*2*:

channels:
  stable:2.7.2 2020-02-18 (10671) 72MB classic
  candidate: ↑ 
  beta:  ↑ 
  edge:  2.8-beta1+develop-29900ab 2020-02-18 (10690) 81MB classic
  2.7/stable:2.7.2 2020-02-18 (10671) 72MB classic
  2.7/candidate: 2.7.3+2.7-aa61342 2020-02-18 (10691) 81MB classic
  2.7/beta:  ↑ 
  2.7/edge:  2.7.3+2.7-aa61342 2020-02-18 (10691) 81MB classic
  2.6/stable:2.6.102019-10-30  (9484) 69MB classic
  2.6/candidate: ↑ 
  2.6/beta:  ↑ 
  2.6/edge:  2.6.11+2.6-b96e1222020-01-22 (10408) 75MB classic
  2.5/stable:2.5.8 2019-06-27  (8361) 67MB classic
  2.5/candidate: ↑ 
  2.5/beta:  ↑ 
  2.5/edge:  2.5.9+2.5-36af233 2019-07-24  (8546) 73MB classic
  2.4/stable:2.4.7 2019-05-23  (6012) 58MB classic
  2.4/candidate: ↑ 
  2.4/beta:  ↑ 
  2.4/edge:  ↑ 
  2.3/stable:2.3.9 2018-09-19  (5267) 55MB classic
  2.3/candidate: ↑ 
  2.3/beta:  ↑ 
  2.3/edge:  2.3.10+2.3-41313d12019-03-25  (7080) 55MB classic
installed:   2.7.2(10671) 72MB classic

gnome-software 3.35.2-0ubuntu2
snapd 2.43.3+git1.8109f8

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

** Attachment added: "Screenshot from 2020-02-18 15-50-41.png"
   
https://bugs.launchpad.net/bugs/1863812/+attachment/5329403/+files/Screenshot%20from%202020-02-18%2015-50-41.png

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

Title:
  tells me an update is available, but i'm running a newer version

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Today I noticed that the software manager is telling me there's a juju
  update available (2.7.1), with an option to update. When I click
  update, it says "Unable to update juju: snap has no updates
  available". Sure enough, `snap info` confirms that I'm already on
  2.7.*2*:

  channels:
stable:2.7.2 2020-02-18 (10671) 72MB classic
candidate: ↑ 
beta:  ↑ 
edge:  2.8-beta1+develop-29900ab 2020-02-18 (10690) 81MB classic
2.7/stable:2.7.2 2020-02-18 (10671) 72MB classic
2.7/candidate: 2.7.3+2.7-aa61342 2020-02-18 (10691) 81MB classic
2.7/beta:  ↑ 
2.7/edge:  2.7.3+2.7-aa61342 2020-02-18 (10691) 81MB classic
2.6/stable:2.6.102019-10-30  (9484) 69MB classic
2.6/candidate: ↑ 
2.6/beta:  ↑ 
2.6/edge:  2.6.11+2.6-b96e1222020-01-22 (10408) 75MB classic
2.5/stable:2.5.8 2019-06-27  (8361) 67MB classic
2.5/candidate: ↑ 
2.5/beta:  ↑ 
2.5/edge:  2.5.9+2.5-36af233 2019-07-24  (8546) 73MB classic
2.4/stable:2.4.7 2019-05-23  (6012) 58MB classic
2.4/candidate: ↑ 
2.4/beta:  ↑ 
2.4/edge:  ↑ 
2.3/stable:2.3.9 2018-09-19  (5267) 55MB classic
2.3/candidate: ↑ 
2.3/beta:  ↑ 
2.3/edge:  2.3.10+2.3-41313d12019-03-25  (7080) 55MB classic
  installed:   2.7.2(10671) 72MB classic

  gnome-software 3.35.2-0ubuntu2
  snapd 2.43.3+git1.8109f8

To manage notifications about this bug go to:

Re: [Desktop-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

[dann frazier]

On Thu, Jun 1, 2017 at 7:27 AM, Zhanglei Mao  wrote:
> Daniel,
>
> It is really good. For patch driver and new kernel buiding, I cc Dann on the
> mail too, he is our engineer for this enablement project with Hisilicon.
> This is pearl kernel was build by him too.
>
> Dann,
>
> Can you patch and build out a new kernel for us or help Daniel to build a
> new testing kernel.

The latest zesty kernel works fine on the HiSilicon board, I'd suggest
patching that for your testing.

  -dann

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

Title:
  Xorg Segmentation fault on Hisilicon D05 board (arm64)

Status in xorg package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ sudo /usr/lib/xorg/Xorg 
  [sudo] password for ubuntu: 

  X.Org X Server 1.18.4
  Release Date: 2016-07-19
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-45-generic aarch64 Ubuntu
  Current Operating System: Linux ubuntu 4.10.0-20.22-generic 
#22+pearl.2-Ubuntu SMP Thu Apr 27 20:23:08 UTC 2017 aarch64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20.22-generic 
root=UUID=eee681c5-04ce-4cd0-a004-cae6717961ce ro debug 
earlycon=pl011,mmio,0x602B console=tty0
  Build Date: 02 November 2016  10:05:28PM
  xorg-server 2:1.18.4-0ubuntu0.2 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 19 18:10:13 2017
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  pci id for fd 10: 19e5:1711, driver (null)
  EGL_MESA_drm_image required.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x58) [0xd7f1cc48]
  (EE) 
  (EE) Segmentation fault at address 0xa0
  (EE) 
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.
  Aborted (core dumped)
  ubuntu@ubuntu:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691991/+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 1398898] Re: [armhf] segfaults when trying to save a file

[dann frazier]

This was brought to my attention on the Linaro cross-distro list:
  http://lists.linaro.org/pipermail/cross-distro/2014-December/000765.html

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

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

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

Title:
  [armhf] segfaults when trying to save a file

Status in The Mozilla Firefox Browser:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in iceweasel package in Debian:
  Unknown

Bug description:
  I reproduced by:

  1) starting firefox on an armhf system
  2) browsing to http://us.archive.ubuntu.com
  3) right clicking on the folder image, clicking Save Image As...
  4) then selecting a folder. 

  ubuntu@hb06-22:/tmp$ firefox

  (process:23506): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
  Gtk-Message: Failed to load module canberra-gtk-module

  (firefox:23506): LIBDBUSMENU-GLIB-WARNING **: Unable to get session
  bus: Failed to execute child process dbus-launch (No such file or
  directory)

  ### THIS IS WHERE I SELECT SAVE IMAGE AS ###

  
   1417625318797GMPInstallManager.simpleCheckAndInstall INFOLast 
check was: 1417625319 seconds ago, minimum seconds: 86400
  1417625318798 GMPInstallManager._getURL   INFOUsing url: 
https://aus4.mozilla.org/update/3/GMP/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml
  1417625318800 GMPInstallManager._getURL   INFOUsing url (with 
replacement): 
https://aus4.mozilla.org/update/3/GMP/33.0/20141013200607/Linux_arm-eabi-gcc3/en-US/release/Linux%203.13.0-37-generic%20(GTK%202.24.23)/canonical/1.0/update.xml
  1417625318805 GMPInstallManager.checkForAddonsINFOsending request 
to: 
https://aus4.mozilla.org/update/3/GMP/33.0/20141013200607/Linux_arm-eabi-gcc3/en-US/release/Linux%203.13.0-37-generic%20(GTK%202.24.23)/canonical/1.0/update.xml

  (firefox:23506): Gtk-WARNING **: Attempting to store changes into 
`/home/ubuntu/.local/share/recently-used.xbel', but failed: Failed to create 
file '/home/ubuntu/.local/share/recently-used.xbel.ECJTPX': No such file or 
directory

  (firefox:23506): Gtk-WARNING **: Attempting to set the permissions of 
`/home/ubuntu/.local/share/recently-used.xbel', but failed: No such file or 
directory
  ubuntu@hb06-22:/tmp$

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1398898/+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 1398898] [NEW] [armhf] segfaults when trying to save a file

[dann frazier]

Public bug reported:

I reproduced by:

1) starting firefox on an armhf system
2) browsing to http://us.archive.ubuntu.com
3) right clicking on the folder image, clicking Save Image As...
4) then selecting a folder. 

ubuntu@hb06-22:/tmp$ firefox

(process:23506): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size 
== 0' failed
Gtk-Message: Failed to load module canberra-gtk-module

(firefox:23506): LIBDBUSMENU-GLIB-WARNING **: Unable to get session bus:
Failed to execute child process dbus-launch (No such file or
directory)

### THIS IS WHERE I SELECT SAVE IMAGE AS ###


 1417625318797  GMPInstallManager.simpleCheckAndInstall INFOLast check was: 
1417625319 seconds ago, minimum seconds: 86400
1417625318798   GMPInstallManager._getURL   INFOUsing url: 
https://aus4.mozilla.org/update/3/GMP/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml
1417625318800   GMPInstallManager._getURL   INFOUsing url (with 
replacement): 
https://aus4.mozilla.org/update/3/GMP/33.0/20141013200607/Linux_arm-eabi-gcc3/en-US/release/Linux%203.13.0-37-generic%20(GTK%202.24.23)/canonical/1.0/update.xml
1417625318805   GMPInstallManager.checkForAddonsINFOsending request 
to: 
https://aus4.mozilla.org/update/3/GMP/33.0/20141013200607/Linux_arm-eabi-gcc3/en-US/release/Linux%203.13.0-37-generic%20(GTK%202.24.23)/canonical/1.0/update.xml
  
(firefox:23506): Gtk-WARNING **: Attempting to store changes into 
`/home/ubuntu/.local/share/recently-used.xbel', but failed: Failed to create 
file '/home/ubuntu/.local/share/recently-used.xbel.ECJTPX': No such file or 
directory

(firefox:23506): Gtk-WARNING **: Attempting to set the permissions of 
`/home/ubuntu/.local/share/recently-used.xbel', but failed: No such file or 
directory
ubuntu@hb06-22:/tmp$

** Affects: firefox
 Importance: Unknown
 Status: Unknown

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

** Affects: iceweasel (Debian)
 Importance: Unknown
 Status: Unknown

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

** Also affects: iceweasel (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756426
   Importance: Unknown
   Status: Unknown

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

Title:
  [armhf] segfaults when trying to save a file

Status in The Mozilla Firefox Browser:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in iceweasel package in Debian:
  Unknown

Bug description:
  I reproduced by:

  1) starting firefox on an armhf system
  2) browsing to http://us.archive.ubuntu.com
  3) right clicking on the folder image, clicking Save Image As...
  4) then selecting a folder. 

  ubuntu@hb06-22:/tmp$ firefox

  (process:23506): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
  Gtk-Message: Failed to load module canberra-gtk-module

  (firefox:23506): LIBDBUSMENU-GLIB-WARNING **: Unable to get session
  bus: Failed to execute child process dbus-launch (No such file or
  directory)

  ### THIS IS WHERE I SELECT SAVE IMAGE AS ###

  
   1417625318797GMPInstallManager.simpleCheckAndInstall INFOLast 
check was: 1417625319 seconds ago, minimum seconds: 86400
  1417625318798 GMPInstallManager._getURL   INFOUsing url: 
https://aus4.mozilla.org/update/3/GMP/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml
  1417625318800 GMPInstallManager._getURL   INFOUsing url (with 
replacement): 
https://aus4.mozilla.org/update/3/GMP/33.0/20141013200607/Linux_arm-eabi-gcc3/en-US/release/Linux%203.13.0-37-generic%20(GTK%202.24.23)/canonical/1.0/update.xml
  1417625318805 GMPInstallManager.checkForAddonsINFOsending request 
to: 
https://aus4.mozilla.org/update/3/GMP/33.0/20141013200607/Linux_arm-eabi-gcc3/en-US/release/Linux%203.13.0-37-generic%20(GTK%202.24.23)/canonical/1.0/update.xml

  (firefox:23506): Gtk-WARNING **: Attempting to store changes into 
`/home/ubuntu/.local/share/recently-used.xbel', but failed: Failed to create 
file '/home/ubuntu/.local/share/recently-used.xbel.ECJTPX': No such file or 
directory

  (firefox:23506): Gtk-WARNING **: Attempting to set the permissions of 
`/home/ubuntu/.local/share/recently-used.xbel', but failed: No such file or 
directory
  ubuntu@hb06-22:/tmp$

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1398898/+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 1398898] Re: [armhf] segfaults when trying to save a file

[dann frazier]

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

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

Title:
  [armhf] segfaults when trying to save a file

Status in The Mozilla Firefox Browser:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in iceweasel package in Debian:
  Unknown

Bug description:
  I reproduced by:

  1) starting firefox on an armhf system
  2) browsing to http://us.archive.ubuntu.com
  3) right clicking on the folder image, clicking Save Image As...
  4) then selecting a folder. 

  ubuntu@hb06-22:/tmp$ firefox

  (process:23506): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
  Gtk-Message: Failed to load module canberra-gtk-module

  (firefox:23506): LIBDBUSMENU-GLIB-WARNING **: Unable to get session
  bus: Failed to execute child process dbus-launch (No such file or
  directory)

  ### THIS IS WHERE I SELECT SAVE IMAGE AS ###

  
   1417625318797GMPInstallManager.simpleCheckAndInstall INFOLast 
check was: 1417625319 seconds ago, minimum seconds: 86400
  1417625318798 GMPInstallManager._getURL   INFOUsing url: 
https://aus4.mozilla.org/update/3/GMP/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml
  1417625318800 GMPInstallManager._getURL   INFOUsing url (with 
replacement): 
https://aus4.mozilla.org/update/3/GMP/33.0/20141013200607/Linux_arm-eabi-gcc3/en-US/release/Linux%203.13.0-37-generic%20(GTK%202.24.23)/canonical/1.0/update.xml
  1417625318805 GMPInstallManager.checkForAddonsINFOsending request 
to: 
https://aus4.mozilla.org/update/3/GMP/33.0/20141013200607/Linux_arm-eabi-gcc3/en-US/release/Linux%203.13.0-37-generic%20(GTK%202.24.23)/canonical/1.0/update.xml

  (firefox:23506): Gtk-WARNING **: Attempting to store changes into 
`/home/ubuntu/.local/share/recently-used.xbel', but failed: Failed to create 
file '/home/ubuntu/.local/share/recently-used.xbel.ECJTPX': No such file or 
directory

  (firefox:23506): Gtk-WARNING **: Attempting to set the permissions of 
`/home/ubuntu/.local/share/recently-used.xbel', but failed: No such file or 
directory
  ubuntu@hb06-22:/tmp$

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1398898/+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 1398898] Re: [armhf] segfaults when trying to save a file

[dann frazier]

I've verified that the upstream patch applies cleanly to firefox in
trusty, and that it does resolve the problem.


** Patch added: tested patch w/ dep-3 headers
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1398898/+attachment/4273747/+files/armhf-xpcom-correct-argument-passing.patch

** Also affects: firefox (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: firefox (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: firefox (Ubuntu Vivid)
   Importance: High
   Status: Confirmed

** Also affects: firefox (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  [armhf] segfaults when trying to save a file

Status in The Mozilla Firefox Browser:
  Fix Released
Status in firefox package in Ubuntu:
  Confirmed
Status in firefox source package in Precise:
  New
Status in firefox source package in Trusty:
  New
Status in firefox source package in Utopic:
  New
Status in firefox source package in Vivid:
  Confirmed
Status in iceweasel package in Debian:
  Confirmed

Bug description:
  I reproduced by:

  1) starting firefox on an armhf system
  2) browsing to http://us.archive.ubuntu.com
  3) right clicking on the folder image, clicking Save Image As...
  4) then selecting a folder. 

  ubuntu@hb06-22:/tmp$ firefox

  (process:23506): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
  Gtk-Message: Failed to load module canberra-gtk-module

  (firefox:23506): LIBDBUSMENU-GLIB-WARNING **: Unable to get session
  bus: Failed to execute child process dbus-launch (No such file or
  directory)

  ### THIS IS WHERE I SELECT SAVE IMAGE AS ###

  
   1417625318797GMPInstallManager.simpleCheckAndInstall INFOLast 
check was: 1417625319 seconds ago, minimum seconds: 86400
  1417625318798 GMPInstallManager._getURL   INFOUsing url: 
https://aus4.mozilla.org/update/3/GMP/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml
  1417625318800 GMPInstallManager._getURL   INFOUsing url (with 
replacement): 
https://aus4.mozilla.org/update/3/GMP/33.0/20141013200607/Linux_arm-eabi-gcc3/en-US/release/Linux%203.13.0-37-generic%20(GTK%202.24.23)/canonical/1.0/update.xml
  1417625318805 GMPInstallManager.checkForAddonsINFOsending request 
to: 
https://aus4.mozilla.org/update/3/GMP/33.0/20141013200607/Linux_arm-eabi-gcc3/en-US/release/Linux%203.13.0-37-generic%20(GTK%202.24.23)/canonical/1.0/update.xml

  (firefox:23506): Gtk-WARNING **: Attempting to store changes into 
`/home/ubuntu/.local/share/recently-used.xbel', but failed: Failed to create 
file '/home/ubuntu/.local/share/recently-used.xbel.ECJTPX': No such file or 
directory

  (firefox:23506): Gtk-WARNING **: Attempting to set the permissions of 
`/home/ubuntu/.local/share/recently-used.xbel', but failed: No such file or 
directory
  ubuntu@hb06-22:/tmp$

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1398898/+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