[Bug 2062967] [NEW] ubuntu-drivers no longer offers nvidia 550 drivers

[Jack Howarth]

Public bug reported:

While I am unclear which package update impacted the video drivers
detected by ubuntu-drivers, the nvidia 545 and nvidia 550 video drivers
are no longer shown as an option on NVIDIA GeForce GTX 1050 video card.
I can understand the removal of the nvidia 545 drivers as the current
kernel's linux-signatures-nvidia-6.8.0-28-generic package lacks
signatures for the nvidia 545 kernel modules for secure boot but the
nvidia 550 kernel modules signatures are available. So while it would be
acceptable to downgrade the 'tested' default nvidia driver to 535,
ubuntu-drivers and Additional Drivers should be offering the nvidia 550
drivers as an untested option.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062967

Title:
  ubuntu-drivers no longer offers nvidia 550 drivers

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061036] Re: pymol 2.5.0+dfsg-1build6 fails to start on noble

[Jack Howarth]

It appears that the following does find the pymol module when executed
within python3.12.

% python3.12
Python 3.12.2 (main, Feb 10 2024, 11:33:20) [Clang 15.0.0 (clang-1500.1.0.2.5)] 
on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> from importlib.util import find_spec
>>> print(f".libs imports {find_spec('pymol')}")
.libs imports ModuleSpec(name='pymol', 
loader=<_frozen_importlib_external.SourceFileLoader object at 0x1035b81a0>, 
origin='/opt/local/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/pymol/__init__.py',
 
submodule_search_locations=['/opt/local/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/pymol'])

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061036

Title:
  pymol 2.5.0+dfsg-1build6 fails to start on noble

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061036] Re: pymol 2.5.0+dfsg-1build6 fails to start on noble

[Jack Howarth]

I am a bit confused as to why simply commenting out the import of imp
works as find_module() should be removed in python 3.12 under Ubuntu
24.04. There doesn't appear to be any fixes yet upstream in Debian Sid
which uses the same 22_fix_pymol_import.patch. Debian doesn't have a bug
report yet against python3-pymol which isn't surprising as their python3
is still at 3.11.8 in Sid.

Upstream python claims the workaround is to replace find_module with
find_spec() but I can't find a clear concise example of that coding.
Here is the relavent section of the documentation.

5.3.4. The meta path
When the named module is not found in sys.modules, Python next searches 
sys.meta_path, which contains a list of meta path finder objects. These finders 
are queried in order to see if they know how to handle the named module. Meta 
path finders must implement a method called find_spec() which takes three 
arguments: a name, an import path, and (optionally) a target module. The meta 
path finder can use any strategy it wants to determine whether it can handle 
the named module or not.

If the meta path finder knows how to handle the named module, it returns
a spec object. If it cannot handle the named module, it returns None. If
sys.meta_path processing reaches the end of its list without returning a
spec, then a ModuleNotFoundError is raised. Any other exceptions raised
are simply propagated up, aborting the import process.

The find_spec() method of meta path finders is called with two or three
arguments. The first is the fully qualified name of the module being
imported, for example foo.bar.baz. The second argument is the path
entries to use for the module search. For top-level modules, the second
argument is None, but for submodules or subpackages, the second argument
is the value of the parent package’s __path__ attribute. If the
appropriate __path__ attribute cannot be accessed, a ModuleNotFoundError
is raised. The third argument is an existing module object that will be
the target of loading later. The import system passes in a target module
only during reload.

The meta path may be traversed multiple times for a single import
request. For example, assuming none of the modules involved has already
been cached, importing foo.bar.baz will first perform a top level
import, calling mpf.find_spec("foo", None, None) on each meta path
finder (mpf). After foo has been imported, foo.bar will be imported by
traversing the meta path a second time, calling mpf.find_spec("foo.bar",
foo.__path__, None). Once foo.bar has been imported, the final traversal
will call mpf.find_spec("foo.bar.baz", foo.bar.__path__, None).

Some meta path finders only support top level imports. These importers
will always return None when anything other than None is passed as the
second argument.

Python’s default sys.meta_path has three meta path finders, one that
knows how to import built-in modules, one that knows how to import
frozen modules, and one that knows how to import modules from an import
path (i.e. the path based finder).

Changed in version 3.4: The find_spec() method of meta path finders
replaced find_module(), which is now deprecated. While it will continue
to work without change, the import machinery will try it only if the
finder does not implement find_spec().

Changed in version 3.10: Use of find_module() by the import system now
raises ImportWarning.

Changed in version 3.12: find_module() has been removed. Use find_spec()
instead.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061036

Title:
  pymol 2.5.0+dfsg-1build6 fails to start on noble

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061036] [NEW] pymol 2.5.0+dfsg-1build6 fails to start on noble

[Jack Howarth]

Public bug reported:

The python 3.12 in use on noble causes pymol in the pymol
2.5.0+dfsg-1build6 to fail on the command line with the error...

Traceback (most recent call last):
  File "", line 189, in _run_module_as_main
  File "", line 112, in _get_module_details
  File "/usr/lib/python3/dist-packages/pymol/__init__.py", line 81, in 
from imp import find_module
ModuleNotFoundError: No module named 'imp'

Commenting out the line...

# from imp import find_module

in /usr/lib/python3/dist-packages/pymol/__init__.py appears to be
sufficient to allow pymol to run.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061036

Title:
  pymol 2.5.0+dfsg-1build6 fails to start on noble

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060655] [NEW] linux-signatures-nvidia-6.8.0-22-generic missing default nvidia 550 drivers

[Jack Howarth]

Public bug reported:

The linux-signatures-nvidia-6.8.0-22-generic package only contains
nvidia drivers as new as nvidia-driver-450 despite the current
additional drivers in Software & Updates having nvidia-driver-550 as the
tested topmost choice.

** Affects: linux-restricted-signatures (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060655

Title:
  linux-signatures-nvidia-6.8.0-22-generic missing default nvidia 550
  drivers

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2060394] [NEW] do-release-upgrade -d currently non-functional

[Jack Howarth]

Public bug reported:

Under both current 22.04.4 and 23.10, the command 'sudo do-release-
upgrade -d' is non-functional and can't upgrade a system to the current
24.04 development release. I've never witnessed this behavior in the
past and assume that the development release has been hidden from the
update manager due to the mass rebuild that appears to have been
completed. Please re-expose the development release so that 'do-release-
upgrade -d' is functional again.

Note that I do have Prompt=normal set in /etc/update-manager/release-
upgrades so it should be able to see the development release as in all
prior ubuntu release cycles.

$ sudo do-release-upgrade -d
[sudo] password for howarth: 
Checking for a new Ubuntu release
Upgrades to the development release are only 
available from the latest supported release.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060394

Title:
  do-release-upgrade -d currently non-functional

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2060394/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971558] Re: dropbox menu icon often replaced with three dots under Jammy

[Jack Howarth]

** Attachment added: "screen shot of the three dot icon instead of the expected 
dropbox one."
   
https://bugs.launchpad.net/ubuntu/+source/nautilus-dropbox/+bug/1971558/+attachment/5586601/+files/Screenshot%20from%202022-05-04%2006-01-59.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971558

Title:
  dropbox menu icon often replaced with three dots under Jammy

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971558] Re: dropbox menu icon often replaced with three dots under Jammy

[Jack Howarth]

** Attachment added: "screen shot of the three dot icon instead of the expected 
dropbox one."
   
https://bugs.launchpad.net/ubuntu/+source/nautilus-dropbox/+bug/1971558/+attachment/5586602/+files/Screenshot%20from%202022-05-04%2006-01-59.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971558

Title:
  dropbox menu icon often replaced with three dots under Jammy

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971558] [NEW] dropbox menu icon often replaced with three dots under Jammy

[Jack Howarth]

Public bug reported:

Often when logging back into after workstation sleeping, the dropbox
icon in the top menu bar is replaced with three dots instead of its
normal dropbox icon.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nautilus-dropbox 2019.02.14-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-28.29-generic 5.15.35
Uname: Linux 5.15.0-28-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed May  4 05:58:51 2022
InstallationDate: Installed on 2022-03-31 (33 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus-dropbox
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971558

Title:
  dropbox menu icon often replaced with three dots under Jammy

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969447] Re: 42.0-1ubuntu6 doesn't recongize the presence of NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1

[Jack Howarth]

Daniel, I disagree. This bug is actually about the fact that the test
crafted in /lib/udev/rules.d/61-gdm.rules doesn't parse as expected in
udev. We also should probably file a bug report against upstream udev as
the changes added to support escaped quotes in #6890 aren't robust
enough.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969447

Title:
  42.0-1ubuntu6 doesn't recongize the presence of
  NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969447] Re: 42.0-1ubuntu6 doesn't recongize the presence of NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1

[Jack Howarth]

Note that I stumbled onto the above fix after noticing the example shown
for the udev escaped quoting support showed an example with double
quotes surrounded by single quotes which in turn surrounded escaped
double quotes...

https://git.alternativebit.fr/NinjaTrappeur/Systemd/commit/7e760b79ad143b26a5c937afa7666a7c40508f85

udev-rules: all values can contain escaped double quotes now (#6890)
This is primarly useful to support escaped double quotes in PROGRAM or
IMPORT{program} directives.

The only possibilty before this patch was to use an external shell script but
this seems too cumbersome for trivial logics such as

 PROGRAM=="/bin/sh -c 'FOO=\"%s{model}\"; echo ${FOO:0:4}'"

or any similar shell constructs that needs to deals with patterns including
whitespaces.

As it's the case for single quote and for directives running a program, words
within escaped double quotes will be considered as a single argument.

Fixes: #6835

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969447

Title:
  42.0-1ubuntu6 doesn't recongize the presence of
  NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969447] Re: 42.0-1ubuntu6 doesn't recongize the presence of NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1

[Jack Howarth]

I have found that current /lib/udev/rules.d/61-gdm.rules can be fixed by
swapping the order of the single and escaped double quotes from...

IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e
's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e
's/^/NVIDIA_/' /proc/driver/nvidia/params\""

which fails to parse correctly to...

IMPORT{program}="/bin/sh -c 'sed -e \"s/: /=/g\" -e
\"s/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g\" -e \"s/[[:lower:]]/\U&/g\"
-e \"s/^/NVIDIA_/\" /proc/driver/nvidia/params'"

which parses properly and allows the test for

ENV{NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS}!="1",
GOTO="gdm_disable_wayland"

to succeed when /etc/modprobe.d/nvidia-power-management.conf contains...

options nvidia NVreg_PreserveVideoMemoryAllocations=1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969447

Title:
  42.0-1ubuntu6 doesn't recongize the presence of
  NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969447] Re: 42.0-1ubuntu6 doesn't recongize the presence of NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1

[Jack Howarth]

I am wondering if the use of escaped quotes in the failing rule of
/lib/udev/rules.d/61-gdm.rules is really being honored. There don't seem
to be any other examples of deployed udev rules which actually use such
escaped quotes.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969447

Title:
  42.0-1ubuntu6 doesn't recongize the presence of
  NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969447] [NEW] 42.0-1ubuntu6 doesn't recongize the presence of NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1

[Jack Howarth]

Public bug reported:

The current /lib/udev/rules.d/61-gdm.rules has a broken rule for
detecting the presence of NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1.

This issue can be seen by adding a file /etc/modprobe.d/nvidia-power-
management.conf containing the line...

options nvidia NVreg_PreserveVideoMemoryAllocations=1

and then rebooting. Manually executing the test used in
/lib/udev/rules.d/61-gdm.rules as...

/bin/sh -c "sed -e 's/: /=/g' -e
's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e
's/^/NVIDIA_/' /proc/driver/nvidia/params"

produces the desired...

NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1

for the actual test in /lib/udev/rules.d/61-gdm.rules of...

IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e 
's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e 
's/^/NVIDIA_/' /proc/driver/nvidia/params\""
ENV{NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS}!="1", GOTO="gdm_disable_wayland"

However, this test still is treated as failing as seen by the absence of
Wayland on Nvidia at that point. Currently, the only workaround is to
disable this particular test.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gdm3 42.0-1ubuntu6
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 19 05:20:49 2022
InstallationDate: Installed on 2022-03-31 (18 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm3.custom.conf: 2022-04-01T05:39:42.178574

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


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

** Description changed:

  The current /lib/udev/rules.d/61-gdm.rules has a broken rule for
  detecting the presence of NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1.
  
  This issue can be seen by adding a file /etc/modprobe.d/nvidia-power-
  management.conf containing the line...
  
  options nvidia NVreg_PreserveVideoMemoryAllocations=1
  
- and then rebooting. Since manually executing the test used in
+ and then rebooting. Manually executing the test used in
  /lib/udev/rules.d/61-gdm.rules as...
  
  /bin/sh -c "sed -e 's/: /=/g' -e
  's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e
  's/^/NVIDIA_/' /proc/driver/nvidia/params"
  
  produces the desired...
  
  NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1
  
  for the actual test in /lib/udev/rules.d/61-gdm.rules of...
  
  IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e 
's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e 
's/^/NVIDIA_/' /proc/driver/nvidia/params\""
  ENV{NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS}!="1", GOTO="gdm_disable_wayland"
  
  However, this test still is treated as failing as seen by the absence of
  Wayland on Nvidia at that point. Currently, the only workaround is to
  disable this particular test.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu6
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 19 05:20:49 2022
  InstallationDate: Installed on 2022-03-31 (18 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2022-04-01T05:39:42.178574

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969447

Title:
  42.0-1ubuntu6 doesn't recongize the presence of
  NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968929] Re: No Wayland support on my NVIDA laptop

[Jack Howarth]

How can we even know whether the Nvidia power mananagement support is
broken or working if the Ubuntu Nvidia packaging never starts nvidia-
hibernate.service, nvidia-powerd.service, nvidia-resume.service and
nvidia-suspend.service like rpmfusion on Fedora? Of course, we would
need a /etc/modprobe.d/nvidia-power-management.conf to get
NVreg_PreserveVideoMemoryAllocations=1. However, I'm still unconvinced
that the current check for NVreg_PreserveVideoMemoryAllocations=1 in
61-gdm.rules is really functional. In my hands, even though I had
NVreg_PreserveVideoMemoryAllocations=1 present from addition of a
/etc/modprobe.d/nvidia-power-management.conf  contaiining

options nvidia NVreg_PreserveVideoMemoryAllocations=1

the test...

IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e 
's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e 
's/^/NVIDIA_/' /proc/driver/nvidia/params\""
ENV{NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS}!="1", GOTO="gdm_disable_wayland"

in 61-gdm.rules never recognized its presence. It seems like the rule
might not be properly parsing the escaped quotes.

Also, I looked at the Debian packaging for nvidia and I don't see any
evidence that they have ever started those power management related
services.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968929

Title:
  No Wayland support on my NVIDA laptop

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option

[Jack Howarth]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969243

Title:
  gdm 42.0-1ubuntu4 no longer shows Wayland option

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option

[Jack Howarth]

As importantly, how can we even know whether the Nvidia power
mananagement support is broken or working if the Ubuntu Nvidia packaging
never starts nvidia-hibernate.service, nvidia-powerd.service, nvidia-
resume.service and nvidia-suspend.service like rpmfusion on Fedora. Of
course, we would need a /etc/modprobe.d/nvidia-power-management.conf to
get NVreg_PreserveVideoMemoryAllocations=1. However, I'm still
unconvinced that the current check for
NVreg_PreserveVideoMemoryAllocations=1 in 61-gdm.rules is really
functional.  I looked at the Debian packaging for nvidia and I don't see
any evidence that they have ever started those services.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969243

Title:
  gdm 42.0-1ubuntu4 no longer shows Wayland option

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968929] Re: No Wayland support on my NVIDA laptop

[Jack Howarth]

"gdm3 (42.0-1ubuntu6) jammy; urgency=medium

  * Fix Wayland no longer being available for everyone
- Fix by adding a separate revert patch instead of trying to
  rebase the cherry-picked patches (LP: #1969243)
  * Please note that Wayland is not currently available for
systems using the Nvidia graphics drivers because those drivers
don't properly handle suspend and resuming from suspend. It is
intended for those drivers to be fixed in a future stable release
update for Ubuntu 22.04 LTS. See bug 1968929"

Does this imply that restoration of Wayland support for Nvidia will be
treated like the upgrades to new major kernel releases and only occur
after the 22.10 Ubuntu release?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968929

Title:
  No Wayland support on my NVIDA laptop

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option

[Jack Howarth]

What is Ubuntu's definition of a 'stable release update' in this case
regarding Nvidia driver support for Wayland? Does this imply, as I fear,
an update only after the fix has been deployed in another full Ubuntu
release? If so, this would imply that we won't have Nvidia Wayland
support until 22.10 is released.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969243

Title:
  gdm 42.0-1ubuntu4 no longer shows Wayland option

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option

[Jack Howarth]

Looks like Fedora 36 won't have this problem with Wayland on Nvidia
because their associated rpmfusion packaging for xorg-x11-drv-nvidia
adds a nvidia-power-management.conf with the following contents into
/etc/modprobe.d...

#
# Save and restore all video memory allocations.
options nvidia NVreg_PreserveVideoMemoryAllocations=1
#
# The destination should not be using tmpfs, so we prefer
# /var/tmp instead of /tmp
options nvidia NVreg_TemporaryFilePath=/var/tmp

https://github.com/rpmfusion/xorg-x11-drv-nvidia/blob/master/nvidia-power-management.conf
https://github.com/rpmfusion/xorg-x11-drv-nvidia/blob/master/xorg-x11-drv-nvidia.spec

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969243

Title:
  gdm 42.0-1ubuntu4 no longer shows Wayland option

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option

[Jack Howarth]

gdm3 42.0-1ubuntu6 is in proposed and Wayland is apparently going to be
unavailable for the 22.04 LTS release. Cnet is going to have to rewrite
its review.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969243

Title:
  gdm 42.0-1ubuntu4 no longer shows Wayland option

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option

[Jack Howarth]

So this isn't a single bug but multiple points of failure.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969243

Title:
  gdm 42.0-1ubuntu4 no longer shows Wayland option

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option

[Jack Howarth]

Alternatively, you can add a /etc/modprobe.d/nvidia-hack.conf file
containing the line...

options nvidia NVreg_PreserveVideoMemoryAllocations=1

and work around the apparently broken line...

IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e
's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e
's/^/NVIDIA_/' /proc/driver/nvidia/params\""

by adding...

ENV{NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS}="1"

after it in order to restore the use of Wayland under Nvidia.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969243

Title:
  gdm 42.0-1ubuntu4 no longer shows Wayland option

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option

[Jack Howarth]

Does the line...

IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e
's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e
's/^/NVIDIA_/' /proc/driver/nvidia/params\""

in /lib/udev/rules.d/61-gdm.rules parse correctly?

Adding /etc/modprobe.d/nvidia-hack.conf containing 'options nvidia
NVreg_PreserveVideoMemoryAllocations=1', doesn't seem to make
NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS available as an environmental
despite the fact that manually executing...

/bin/sh -c "sed -e 's/: /=/g' -e
's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e
's/^/NVIDIA_/' /proc/driver/nvidia/params"

produces "NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS=1"

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969243

Title:
  gdm 42.0-1ubuntu4 no longer shows Wayland option

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968929] Re: No Wayland support on my NVIDA laptop

[Jack Howarth]

The fact that a /etc/modprobe.d/nvidia-hack.conf file with 'options
nvidia NVreg_PreserveVideoMemoryAllocations=1' doesn't bring back the
Wayland option suggests that the line...

IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e
's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e
's/^/NVIDIA_/' /proc/driver/nvidia/params\""

in /lib/udev/rules.d/61-gdm isn't parsing as expected.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968929

Title:
  No Wayland support on my NVIDA laptop

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968929] Re: No Wayland support on my NVIDA laptop

[Jack Howarth]

On an X570 motherboard with 5600X processor and GTX 1050 graphics card,
I was able to restore Wayland by simply commenting out the lines...

IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e 
's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e 
's/^/NVIDIA_/' /proc/driver/nvidia/params\""
ENV{NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS}!="1", GOTO="gdm_disable_wayland"

in  /lib/udev/rules.d/61-gdm /lib/udev/rules.d/61-gdm. I would note that
logging out back to gdm doesn't make these changes to
/lib/udev/rules.d/61-gdm take effect. I always have to restart the
system when I edit /lib/udev/rules.d/61-gdm.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968929

Title:
  No Wayland support on my NVIDA laptop

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969198] Re: 42.0-1ubuntu4 blocks usage of Wayland on GTX 1050 graphics card

[Jack Howarth]

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

I am able to get Wayland back under gdm3 42.0-1ubuntu4 by commenting out
the following two new lines that were added to
/lib/udev/rules.d/61-gdm.rules

IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e 
's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e 
's/^/NVIDIA_/' /proc/driver/nvidia/params\""
ENV{NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS}!="1", GOTO="gdm_disable_wayland"

So this is the failing test.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969198

Title:
  42.0-1ubuntu4 blocks usage of Wayland on GTX 1050 graphics card

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969243] Re: gdm 42.0-1ubuntu4 no longer shows Wayland option

[Jack Howarth]

gdm3 (42.0-1ubuntu4) breaks using Wayland on a X570 UD v1.1 motherboard
with 5600X processor and Nvidia GTX 1050 graphics card that worked
perfectly under gdm3 (42.0-1ubuntu2). I filed a bug against gdm3
(42.0-1ubuntu4) while it was in proposed updates but the bug report was
ignored and gdm3 (42.0-1ubuntu4) got pushed into the development release
anyway.

42.0-1ubuntu4 blocks usage of Wayland on GTX 1050 graphics card
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969198

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969243

Title:
  gdm 42.0-1ubuntu4 no longer shows Wayland option

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968809] Re: Verify that the gdm cherry-picks are wanted for jammy

[Jack Howarth]

gdm3 42.0-1ubuntu4 still blocks use of wayland on a X570 UD v1.1
motherboard with an AMD 5600X and Nvidia 1050 graphics card.
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969198

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968809

Title:
  Verify that the gdm cherry-picks are wanted for jammy

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969197] [NEW] 42.0-1ubuntu4 blocks usage of Wayland on GT 1050 graphics card

[Jack Howarth]

Public bug reported:

Like the previous proposed 42.0-1ubuntu3 packaging of gdm3, the proposed
42.0-1ubuntu4 prevents Wayland from being used on a X570 UD v1.1
motherboard with 5600X processor and Nvidia GT 1050 graphics card. This
proposed change in the gdm3 should be considered a blocker as it defeats
the upgrade to using Wayland in 20.04 LTS.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gdm3 42.0-1ubuntu4
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 15 05:13:37 2022
InstallationDate: Installed on 2022-03-31 (14 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm3.custom.conf: 2022-04-01T05:39:42.178574

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


** Tags: amd64 apport-bug jammy package-from-proposed third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969197

Title:
  42.0-1ubuntu4 blocks usage of Wayland on GT 1050 graphics card

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969198] [NEW] 42.0-1ubuntu4 blocks usage of Wayland on GTX 1050 graphics card

[Jack Howarth]

Public bug reported:

Like the previous proposed 42.0-1ubuntu3 packaging of gdm3, the proposed
42.0-1ubuntu4 prevents Wayland from being used on a X570 UD v1.1
motherboard with 5600X processor and Nvidia GTX 1050 graphics card. This
proposed change in the gdm3 should be considered a blocker as it defeats
the upgrade to using Wayland in 20.04 LTS.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gdm3 42.0-1ubuntu4
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 15 05:13:37 2022
InstallationDate: Installed on 2022-03-31 (14 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm3.custom.conf: 2022-04-01T05:39:42.178574

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


** Tags: amd64 apport-bug jammy package-from-proposed third-party-packages

** Summary changed:

- 42.0-1ubuntu4 blocks usage of Wayland on GT 1050 graphics card
+ 42.0-1ubuntu4 blocks usage of Wayland on GTX 1050 graphics card

** Description changed:

  Like the previous proposed 42.0-1ubuntu3 packaging of gdm3, the proposed
  42.0-1ubuntu4 prevents Wayland from being used on a X570 UD v1.1
- motherboard with 5600X processor and Nvidia GT 1050 graphics card. This
+ motherboard with 5600X processor and Nvidia GTX 1050 graphics card. This
  proposed change in the gdm3 should be considered a blocker as it defeats
  the upgrade to using Wayland in 20.04 LTS.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu4
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 15 05:13:37 2022
  InstallationDate: Installed on 2022-03-31 (14 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2022-04-01T05:39:42.178574

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969198

Title:
  42.0-1ubuntu4 blocks usage of Wayland on GTX 1050 graphics card

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968809] Re: Verify that the gdm cherry-picks are wanted for jammy

[Jack Howarth]

gdm3 42.0-1ubuntu3 blocks use of wayland on a X570 UD v1.1 motherboard
with an AMD 5600X and Nvidia 1050 graphics card.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968809

Title:
  Verify that the gdm cherry-picks are wanted for jammy

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04

[Jack Howarth]

I can confirm that rebuilding the current 41.1-1build1 cheese packaging
with the offending commit reverted...

https://gitlab.gnome.org/GNOME/cheese/-/commit/58de82b3d463b69f4c0bef75667e47020924e28b.patch
 
...allows my Logitech C525 webcam to operate properly again.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967843

Title:
  cheese display corrupted under  Ubuntu 22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04

[Jack Howarth]

Matthew, do you see the same corruption if you boot the same machine
with the Logitech C270 camera under a Fedora 36 Beta live image? It
would be interesting to know if their Fedora cheese 41.1 package doesn't
show the same artifact like it doesn't on my hardware.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967843

Title:
  cheese display corrupted under  Ubuntu 22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04

[Jack Howarth]

It is very odd that Fedora 36 beta also uses a build of cheese 41.1 with
minimal patching and the apparently the same optimizations yet it
doesn't exhibit this artifact.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967843

Title:
  cheese display corrupted under  Ubuntu 22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04

[Jack Howarth]

I also can confirm that the warnings...

(cheese:2554): cheese-WARNING **: 16:50:13.024: A lot of buffers are being 
dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:
There may be a timestamping problem, or this computer is too slow.

and associated rendering artifacts in the cheese display occur for both
the nouveau and nvidia 510 drivers.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967843

Title:
  cheese display corrupted under  Ubuntu 22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04

[Jack Howarth]

** Attachment added: "screenshot of the rendering artifact in cheese under 
22.04"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967843/+attachment/5577395/+files/Screenshot%20from%202022-04-05%2016-53-06.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967843

Title:
  cheese display corrupted under  Ubuntu 22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967843] lspci.txt

[Jack Howarth]

apport information

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967843

Title:
  cheese display corrupted under  Ubuntu 22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04

[Jack Howarth]

Unlike cheese, 'ST_V4L2_USE_LIBV4L2=1 gst-launch-1.0 v4l2src !
xvimagesink' displays the webcam image fine.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967843

Title:
  cheese display corrupted under  Ubuntu 22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967843] lsusb.txt

[Jack Howarth]

apport information

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967843

Title:
  cheese display corrupted under  Ubuntu 22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967843] ProcCpuinfo.txt

[Jack Howarth]

apport information

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967843

Title:
  cheese display corrupted under  Ubuntu 22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967843] ProcCpuinfoMinimal.txt

[Jack Howarth]

apport information

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967843

Title:
  cheese display corrupted under  Ubuntu 22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967843] Dependencies.txt

[Jack Howarth]

apport information

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967843

Title:
  cheese display corrupted under  Ubuntu 22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04

[Jack Howarth]

apport information

** Tags added: apport-collected

** Description changed:

  The cheese application produces a corrupted display under Ubuntu 22.04
  with a Logitech C525 webcam. When started from the command line, cheese
  produces repeated warnings of the form...
  
  (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being 
dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:
  There may be a timestamping problem, or this computer is too slow.
  
  Adding /etc/modprobe.d/uvcvideo.conf
  
  with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue
  is not seen in either Ubuntu 21.10 or under Fedora-Workstation-
  Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both
  Wayland and X11 displays with the Nvidia drivers.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cheese 41.1-1build1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  5 05:15:35 2022
  ExecutablePath: /usr/bin/cheese
  InstallationDate: Installed on 2022-03-31 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  MachineType: Gigabyte Technology Co., Ltd. X570 UD
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  RelatedPackageVersions:
   cheese41.1-1build1
   cheese-common 41.1-1build1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F32
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 UD
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 UD
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu80
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-03-31 (4 days ago)
+ InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
+ MachineType: Gigabyte Technology Co., Ltd. X570 UD
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: cheese 41.1-1build1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
+ RelatedPackageVersions:
+  cheese41.1-1build1
+  cheese-common 41.1-1build1
+ Tags: wayland-session third-party-packages jammy gstreamer-error
+ Uname: Linux 5.15.0-25-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 01/18/2021
+ dmi.bios.release: 5.17
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: F32
+ dmi.board.asset.tag: Default string
+ dmi.board.name: X570 UD
+ dmi.board.vendor: Gigabyte Technology Co., Ltd.
+ dmi.board.version: x.x
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Default string
+ dmi.chassis.version: Default string
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
+ dmi.product.family: X570 MB
+ dmi.product.name: X570 UD
+ dmi.product.sku: Default string
+ dmi.product.version: Default string
+ dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967843

Title:
  cheese display corrupted under  Ubuntu 22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967843] [NEW] cheese display corrupted under Ubuntu 22.04

[Jack Howarth]

Public bug reported:

The cheese application produces a corrupted display under Ubuntu 22.04
with a Logitech C525 webcam. When started from the command line, cheese
produces repeated warnings of the form...

(cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being 
dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): 
/GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:
There may be a timestamping problem, or this computer is too slow.

Adding /etc/modprobe.d/uvcvideo.conf

with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue
is not seen in either Ubuntu 21.10 or under Fedora-Workstation-
Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both
Wayland and X11 displays with the Nvidia drivers.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cheese 41.1-1build1
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  5 05:15:35 2022
ExecutablePath: /usr/bin/cheese
InstallationDate: Installed on 2022-03-31 (4 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
MachineType: Gigabyte Technology Co., Ltd. X570 UD
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
RelatedPackageVersions:
 cheese41.1-1build1
 cheese-common 41.1-1build1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F32
dmi.board.asset.tag: Default string
dmi.board.name: X570 UD
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: X570 MB
dmi.product.name: X570 UD
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug gstreamer-error jammy third-party-packages 
wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967843

Title:
  cheese display corrupted under  Ubuntu 22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1947829] Re: Cannot identified WLAN card MT7921 in Ubunut OS with Install OS complete first OOBE Boot OS

[Jack Howarth]

The changes made to linux-firmware 1.201.1 on impish has destablized use
of a Gigabyte GC-WB867D-I REV Bluetooth 4.0/Wireless AC/B/G/N Band Dual
Frequency 2.4Ghz/5.8Ghz Expansion Card. Under the new linux-firmware
1.201.1, no wifi is available under Gnome in about 80-90% of the boots.
Under the prior linux-firmware 1.201 release, the wifi always appears
under Gnome. Below are the differences in syslog for the broken linux-
firmware 1.201.1 release...

Nov  3 04:27:07 home kernel: [   13.045691] iwlwifi :4d:00.0: enabling 
device ( -> 0002)
Nov  3 04:27:07 home kernel: [   13.055795] iwlwifi :4d:00.0: loaded 
firmware version 36.ca7b901d.0 8265-36.ucode op_mode iwlmvm
Nov  3 04:27:07 home kernel: [   13.112172] iwlwifi :4d:00.0: Detected 
Intel(R) Dual Band Wireless AC 8265, REV=0x230

versus the stable linux-firmware 1.201 release...
Nov  3 04:36:53 home kernel: [   14.482126] iwlwifi :4d:00.0: enabling 
device ( -> 0002)
Nov  3 04:36:53 home kernel: [   14.492179] iwlwifi :4d:00.0: loaded 
firmware version 36.ca7b901d.0 8265-36.ucode op_mode iwlmvm
Nov  3 04:36:53 home kernel: [   14.548114] iwlwifi :4d:00.0: Detected 
Intel(R) Dual Band Wireless AC 8265, REV=0x230
Nov  3 04:36:53 home kernel: [   14.606163] iwlwifi :4d:00.0: base HW 
address: 00:28:f8:f9:16:e0
Nov  3 04:36:53 home kernel: [   14.722166] iwlwifi :4d:00.0 wlp77s0: 
renamed from wlan0

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947829

Title:
  Cannot identified WLAN card MT7921 in Ubunut OS with Install OS
  complete first OOBE Boot OS

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1947829/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1695651] Re: GNOME Weather: "Forecast not available"

[Jack Howarth]

Does this need to get refiled against libgweather in order to get this
issue fixed? I can confirm that building local
libgweather_3.36.1-2~ubuntu20.04.1 packages with the four patches
referenced in comment 6 eliminates this bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1695651

Title:
  GNOME Weather: "Forecast not available"

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1876632] Re: [nvidia] Corrupted shell textures when switching users or resuming from suspend

[Jack Howarth]

I've seen the same issue with focal and System76 Stable PPA's
460.32.03-1pop0~1611601564~20.04~11a4029~dev nvidia packaging. All text
was corrupted after waking from suspend but it has only occurred once so
far.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876632

Title:
  [nvidia] Corrupted shell textures when switching users or resuming
  from suspend

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

[Jack Howarth]

My experience with focal-proposed and accountsservice
0.6.55-0ubuntu12~20.04.1 has been that the update causes the currently
executing 'sudo apt-get update' to prematurely abort when the gnome
shell crashes. In my case, this left the linux-kerrnel packages only
half configured. My understanding is that 'sudo apt-get update' doesn't
fully run as a background process when executed from a Gnome Terminal
window. So when the gnome shell crashes back to gdm, the current update
is stopped at that point.

I believe the proper way to test this package is on a machine currently
on focal-updates that is then switched to focal-proposed so that the
update occurs against a real-world set of packages and not just the
accountsservice packages alone.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843982

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

[Jack Howarth]

Looking at the syslog for the failed upgrade to accountsservice
0.6.55-0ubuntu12~20.04.1 with autologin enabled, I find that the first
failure appears at...

May 13 17:04:50 howarth-MacPro systemd[1]: Stopping Accounts Service...
May 13 17:04:50 howarth-MacPro systemd[1]: accounts-daemon.service: Succeeded.
May 13 17:04:50 howarth-MacPro systemd[1]: Stopped Accounts Service.
May 13 17:04:50 howarth-MacPro systemd[1]: Starting Accounts Service...
May 13 17:04:50 howarth-MacPro accounts-daemon[12151]: started daemon version 
0.6.55
May 13 17:04:50 howarth-MacPro systemd[1]: Started Accounts Service.
May 13 17:04:50 howarth-MacPro kernel: [  311.779519] gsd-keyboard[2260]: 
segfault at 0 ip 7f330b6b1494 sp 7ffed49c6f88 error 4 in 
libglib-2.0.so.0.6400.2[7f330b68d000+84000]
May 13 17:04:50 howarth-MacPro kernel: [  311.779530] Code: f8 5b 5d c3 66 90 
f3 0f 1e fa 48 83 ec 08 e8 a3 cf fd ff 85 c0 0f 94 c0 48 83 c4 08 0f b6 c0 c3 
66 0f 1f 44 00 00 f3 0f 1e fa <
0f> be 07 41 b8 05 15 00 00 84 c0 74 1d 0f 1f 80 00 00 00 00 44 89
May 13 17:04:50 howarth-MacPro kernel: [  311.779639] gdm3[1405]: segfault at 0 
ip 7f719bbe3494 sp 7ffc4861af48 error 4 in 
libglib-2.0.so.0.6400.2[7f719bbbf000+84000]
May 13 17:04:50 howarth-MacPro kernel: [  311.779650] Code: f8 5b 5d c3 66 90 
f3 0f 1e fa 48 83 ec 08 e8 a3 cf fd ff 85 c0 0f 94 c0 48 83 c4 08 0f b6 c0 c3 
66 0f 1f 44 00 00 f3 0f 1e fa <
0f> be 07 41 b8 05 15 00 00 84 c0 74 1d 0f 1f 80 00 00 00 00 44 89
May 13 17:04:50 howarth-MacPro kernel: [  311.779653] gdm-session-wor[1519]: 
segfault at 0 ip 7f6a8d633494 sp 7ffe7b13c2a8 error 4 in 
libglib-2.0.so.0.6400.2[7f6a8d60f000+84000]
May 13 17:04:50 howarth-MacPro kernel: [  311.779662] Code: f8 5b 5d c3 66 90 
f3 0f 1e fa 48 83 ec 08 e8 a3 cf fd ff 85 c0 0f 94 c0 48 83 c4 08 0f b6 c0 c3 
66 0f 1f 44 00 00 f3 0f 1e fa <
0f> be 07 41 b8 05 15 00 00 84 c0 74 1d 0f 1f 80 00 00 00 00 44 89
May 13 17:04:50 howarth-MacPro gnome-shell[1882]: GNOME Shell crashed with 
signal 11
May 13 17:04:50 howarth-MacPro gnome-shell[1882]: == Stack trace for context 
0x55ed1ab076e0 ==
May 13 17:04:50 howarth-MacPro systemd[1534]: Stopped target GNOME Keyboard 
handling.
May 13 17:04:50 howarth-MacPro systemd[1534]: gsd-keyboard.service: Main 
process exited, code=dumped, status=11/SEGV
May 13 17:04:50 howarth-MacPro /usr/lib/gdm3/gdm-x-session[1562]: (II) 
modeset(0): Disabling kernel dirty updates, not required.
May 13 17:04:50 howarth-MacPro systemd[1534]: gsd-keyboard.service: Failed with 
result 'core-dump'.
May 13 17:04:50 howarth-MacPro systemd[1534]: Stopped GNOME Keyboard handling.
May 13 17:04:50 howarth-MacPro systemd[1534]: gsd-keyboard.service: Triggering 
OnFailure= dependencies.
May 13 17:04:50 howarth-MacPro systemd[1534]: Started GNOME Session Failed 
lockdown screen (user).
May 13 17:04:50 howarth-MacPro systemd[1534]: Reached target GNOME Session 
Failed.
May 13 17:04:50 howarth-MacPro systemd[1534]: Starting Notification regarding a 
crash report...
May 13 17:04:50 howarth-MacPro update-notifier-crash[12175]: /usr/bin/whoopsie
May 13 17:04:50 howarth-MacPro systemd[1534]: gnome-shell-x11.service: Main 
process exited, code=dumped, status=11/SEGV
May 13 17:04:50 howarth-MacPro systemd[1534]: gnome-shell-x11.service: Failed 
with result 'core-dump'.
May 13 17:04:50 howarth-MacPro systemd[1534]: gnome-shell-x11.service: 
Scheduled restart job, restart counter is at 1.
May 13 17:04:50 howarth-MacPro systemd[1534]: Stopped target GNOME X11 Session 
(session: ubuntu).
May 13 17:04:50 howarth-MacPro systemd[1534]: Stopping GNOME X11 Session 
(session: ubuntu).
May 13 17:04:50 howarth-MacPro systemd[1534]: Stopped target GNOME X11 Session.
May 13 17:04:50 howarth-MacPro systemd[1534]: Stopping GNOME X11 Session.
May 13 17:04:50 howarth-MacPro systemd[1534]: Stopped target GNOME Shell on X11.
May 13 17:04:50 howarth-MacPro systemd[1534]: Stopping GNOME Shell on X11.
May 13 17:04:50 howarth-MacPro systemd[1534]: Stopped GNOME Shell on X11.
May 13 17:04:50 howarth-MacPro systemd[1534]: Starting GNOME Shell on X11...
May 13 17:04:51 howarth-MacPro /usr/lib/gdm3/gdm-x-session[1562]: (II) 
modeset(0): EDID vendor "APP", prod id 37404
May 13 17:04:51 howarth-MacPro /usr/lib/gdm3/gdm-x-session[1562]: (II) 
modeset(0): Printing DDC gathered Modelines:
May 13 17:04:51 howarth-MacPro /usr/lib/gdm3/gdm-x-session[1562]: (II) 
modeset(0): Modeline "1920x1200"x0.0  154.00  1920 1968 2000 2080  1200 1203 
1209 1235 +hsync -vsync (74.0 kHz eP)
May 13 17:04:51 howarth-MacPro update-notifier-crash[12190]: gdm-session-worker
May 13 17:04:51 howarth-MacPro update-notifier-crash[12190]: gdm3
May 13 17:04:51 howarth-MacPro gsd-media-keys[2262]: Failed to grab 
accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such 
interface “org.gnome.Shell” on object at pa
th /org/gnome/Shell
May 13 17:04:51 howarth-MacPro systemd[1]: gdm.service: Main process exited, 
code=dumped, status=11/SEGV
May 13 17:04:51 

[Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

[Jack Howarth]

I can also confirm that if I disable autologin, reboot and then update
to the current packages in focal-proposed updates that the installation
of accountsservice 0.6.55-0ubuntu12~20.04.1 from the current
accountsservice 0.6.55-0ubuntu11 package completes normally.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843982

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878611] Re: accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into greeter

[Jack Howarth]

I can also confirm that if I disable autologin, reboot and then update
to the current packages in focal-proposed updates that the installation
of accountsservice 0.6.55-0ubuntu12~20.04.1 from the current
accountsservice 0.6.55-0ubuntu11 package completes normally.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878611

Title:
  accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into  greeter

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

[Jack Howarth]

I am seeing crashes back into the greeter when updating the current
accountsservice 0.6.55-0ubuntu11 package to the accountsservice
0.6.55-0ubuntu12~20.04.1 update in the focal proposed-updates. An
autologin is currently set for this machine. Since the changes describe
this fix as...

 * Add patch to not crash in the library when the daemon goes away
(Closes: #948228) (LP: #1843982)

Doesn't that imply that the crashes will only be fixed for future
updates of accountsservice rather than for the current one that
implements that fix?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843982

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878611] Re: accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into greeter

[Jack Howarth]

Done. I forget to note that I do have autologin set.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878611

Title:
  accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into  greeter

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878611] [NEW] accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into greeter

[Jack Howarth]

Public bug reported:

When updating Ubuntu 20.04 to the current proposed updates with the
accountsservice 0.6.55-0ubuntu12~20.04.1 update, the current gnome
session crashes out reproducibly into the the gdm3 greeter. At that
point, when you try to log back in, only the background color is
displayed but no desktop or menus ever appears. One has to perform a
hard reboot at this point to get back to a greeter that will
successfully login.

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

** Description changed:

  When updating Ubuntu 20.04 to the current proposed updates with the
  accountsservice 0.6.55-0ubuntu12~20.04.1 update, the current gnome
  session crashes out reproducibly into the the gdm3 greeter. At that
- point, when you try to log back in, the only background color is
+ point, when you try to log back in, only the background color is
  displayed but no desktop or menus ever appears. One has to perform a
  hard reboot at this point to get back to a greeter that will
  successfully login.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878611

Title:
  accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into  greeter

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878611] Re: accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into greeter

[Jack Howarth]

I noticed that one of the changes in accountsservice
0.6.55-0ubuntu12~20.04.1 is...

 * Add patch to not crash in the library when the daemon goes away
(Closes: #948228) (LP: #1843982)

Does this imply that the existing accountsservice 0.6.55-0ubuntu11
package in 20.04 will crash during upgrades to the newer version due to
the absence of this bug fix in the currently running daemon?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878611

Title:
  accountsservice 0.6.55-0ubuntu12~20.04.1 update crashes into  greeter

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873965] Re: booting into recovery mode hangs under 20.04

[Jack Howarth]

This offending package for bug is proving very difficult to pin down. I
have tried to sequentially regress all the packages that the recovery
kernel boot are likely to use back to their eoan versions on a 20.04
installation. In each case, I reinstalled the kernels afterwards to
insure that the initrd.img files were full regenerated and reinstalled.
The installed packages from the following have been regression tested...

plymouth
busybox
udev
kmod
grub
initramfs
libklibc

and none of these eliminate the breakage in nomodeset under 20.04 on a
Mac ROMed GTX680.

The only 'workaround' that I have found is to append 'nouveau.modeset=1'
after 'nomodeset' in grub's recovery kernel entry.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873965

Title:
  booting into recovery mode hangs under 20.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873965] Re: booting into recovery mode hangs under 20.04

[Jack Howarth]

This issue extends to the daily desktop cd image for focal. When booted
from a usb memory stick and the safe graphics (which uses nomodeset) is
selected from grub, the screen remains black and never completes
booting. This issue doesn't exist with the current 19.10 cd images which
boot without issue on a GTX680.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873965

Title:
  booting into recovery mode hangs under 20.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873965] Re: booting into recovery mode hangs under 20.04

[Jack Howarth]

I have been able to eliminate the focal 5.4.0-26-generic kernel packages
as the origin of this bug. Manually installing those onto an
installation of Ubuntu 19.10, produced a fully functional boot. More
importantly the recovery mode boot from grub worked fine. So the problem
under 20.04 would appear to be something outside of the kernel itself.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873965

Title:
  booting into recovery mode hangs under 20.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873937] Re: nvidia-340 prevents booting into single user mode under Ubuntu 20.04

[Jack Howarth]

This bug doesn't exist on the same hardware (a 2008 MacPro with Mac
ROM'd GTX680) under current Ubuntu 19.10 with the nvidia-340 package
installed. In that case, booting the default 5.3.0-46-generic kernel in
single user mode produces the expected prompt.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873937

Title:
  nvidia-340 prevents booting into single user mode under Ubuntu 20.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873965] Re: booting into recovery mode hangs under 20.04

[Jack Howarth]

This problem doesn't exist for current Ubuntu 19.10 under its
5.3.0-46-generic kernel. The recovery mode boots fine on the same
hardware.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873965

Title:
  booting into recovery mode hangs under 20.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873965] Re: booting into recovery mode hangs under 20.04

[Jack Howarth]

Oddly, so far I have not found a Ubuntu mainline kernel build that
doesn't show the problem.

5.3.18-050318-generic
5.4.0-050400-generic
5.4.25-050425-generic
5.4.28-050428-generic
5.6.6-050606-generic

all produce the hang at loading the ramdisk when booting the recovery
kernel with the default use of nomodesetunder Ubuntu 18.04. The stock
5.3.0-46-generic kernel installed by bionics updates doesn't have this
problem.

So I am guessing this problem must be either a dropped patch in the
kernels used by Ubuntu 20.04 or a change in configuration options in the
kernels between 18.04 and 20.04.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873965

Title:
  booting into recovery mode hangs under 20.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873965] Re: booting into recovery mode hangs under 20.04

[Jack Howarth]

Interestingly, installing the mainline Ubuntu 5.4.25 generic kernel
packages on Ubuntu 18.04 produces the same bug of nomodeset preventing
the recovery dialog from appearing.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873965

Title:
  booting into recovery mode hangs under 20.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873965] Re: booting into recovery mode hangs under 20.04

[Jack Howarth]

If I remove 'nomodeset' from the grub kernel options for the recovery
kernel under 20.04, the hang in booting at loading the ramdisk is
eliminated. The recovery dialog appears as expected.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873965

Title:
  booting into recovery mode hangs under 20.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873965] [NEW] booting into recovery mode hangs under 20.04

[Jack Howarth]

Public bug reported:

On a 2008 MacPro with GTX680 under Ubuntu 20.04, selecting the recovery
mode from grub hangs on loading of the ramdisk with the Recovery Menu
dialog never appearing. This problem doesn't exist for a fresh install
of Ubuntu 18.04 updated to the current package updates. In that case,
the Recovery Menu appears as expected. This bug in Ubuntu 20.04 was
reproduced for both an existing Ubuntu 19.10 installation dist-upgraded
to Ubuntu 20.04 as well as for a fresh install of Ubuntu 20.04.

** Affects: linux-meta (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Required info on kernel used"
   
https://bugs.launchpad.net/bugs/1873965/+attachment/5357409/+files/kernel_info.tar.gz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873965

Title:
  booting into recovery mode hangs under 20.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873937] [NEW] nvidia-340 prevents booting into single user mode under Ubuntu 20.04

[Jack Howarth]

Public bug reported:

Steps to reproduce this bug...

1) Install the current nvidia-340 340.108-0ubuntu2 package.
2) Reboot to confirm nvidia graphics drivers are functional.
3) Reboot and edit the default kernel options to have 'single' before 'quiet 
splash'
4) Boot the edited kernel options

The single user mode is broken under 20.04 with the nvidia 340 drivers.
A black screen appears with no single user prompts. If you remove the
nvidia-340 package and reboot, single user mode works as expected under
the nouveau drivers.

I have confirmed with current Ubuntu 18.04 that this bug with the
nvidia-340 drivers doesn't exist and single user mode works properly.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873937

Title:
  nvidia-340 prevents booting into single user mode under Ubuntu 20.04

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873604] [NEW] nvidia-340 should prune 'splash' from grub.cfg

[Jack Howarth]

Public bug reported:

Currently the Nvidia driver packages break the autologin feature of gdm3
whenever the 'splash' option is present on GRUB_CMDLINE_LINUX_DEFAULT in
/etc/config/grub.

https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801

This breakage can be avoided by removing 'splash' from
GRUB_CMDLINE_LINUX_DEFAULT in  /etc/config/grub, regenerating
/boot/grub/grub.cfg with 'sudo update-grub' and then regenerating the
initrd.img files such that the Nvidia drivers aren't loaded prior to
gdm3.

The nvidia-340 package should be modified to prune 'splash' from
/etc/config/grub and regenerate /boot/grub/grub.cfg prior to building
the Nvidia kernel modules.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873604

Title:
  nvidia-340 should prune 'splash' from grub.cfg

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Jack Howarth]

Couldn't the nvidia packages all be modified to prune 'splash' from
/boot/grub/grub.cfg prior to rebuilding its kernel modules and thus
regenerating the initrd.img files?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845801

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Jack Howarth]

This bug is definitely triggered by the built kernel image loading the
nvidia drivers. The autologin failures and associated hangs on restarts
can be suppressed as follows...

1) Edit /etc/config/grub to remove 'splash' from GRUB_CMDLINE_LINUX_DEFAULT
2) Regenerate /boot/grub/grub.cfg with 'sudo update-grub'
3) Regenerate the initrd.img files by using 'sudo apt-get --reinstall install' 
to reinstall the currently installed kernel packages.

After rebooting, the autologin feature in gdm3 can be reselected and on
the next reboot, it will autologin as expected. No loading the nvidia
module through initrd.img also eliminates the hangs on restarting while
autologin is enabled.

I suspect the folks who thought removing splash from grub.cfg didn't
work had failed to rebuild the initrd.img files after regenerating
grub.cfg.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845801

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Jack Howarth]

Confirmed that setting 'WaylandEnable=false' in /etc/gdm3/custom.conf
under 20.04 has no impact on the autologin bug with nvidia-340.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845801

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Jack Howarth]

20.04 RC shows the same problem with the nvidia-340 drivers on a MacPro
3,1 with Mac ROM'd GTX680. The autologin is ignored and the greeter is
shown instead. While the login works fine at the point, restarting then
causes the system to hang rather than completing the restart.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845801

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873411] [NEW] steam installs generic Desktop icons for games that require an explicit 'Allow Launching'

[Jack Howarth]

Public bug reported:

The 1.0.0.61-2ubuntu3 steam package installs a steam which creates
generic icons on the Desktop for games. These Desktop game icons open in
gedit rather than launching when double clicked. One has to explicitly
right-click on the icon and select 'Allow Launching' for the Desktop
icons that steam creates upon game installation to become usable for
launching.

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

** Description changed:

  The 1.0.0.61-2ubuntu3 steam package installs a steam which creates
  generic icons on the Desktop for games. These Desktop game icons open in
  gedit rather than launching when double clicked. One has to explicitly
  right-click on the icon and select 'Allow Launching' for the Desktop
- icons that steam creates u[on game installation to become usable for
+ icons that steam creates upon game installation to become usable for
  launching.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873411

Title:
  steam installs generic Desktop icons for games that require an
  explicit 'Allow Launching'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873313] [NEW] linux-image-5.4.0-24-generic 5.4.0.24.29 missing from repo

[Jack Howarth]

Public bug reported:

The most recent kernel updates resulted in...

ii  linux-image-5.4.0-24-generic   5.4.0-24.28  
  amd64Signed kernel image generic
ii  linux-image-generic5.4.0.24.29  
  amd64Generic Linux kernel image

where the 5.4.0.24.29 build of linux-image-5.4.0-24-generic didn't get
moved into the repository. Likewise we have...

ii  linux-headers-5.4.0-24 5.4.0-24.28  
  all  Header files related to Linux kernel version 5.4.0
ii  linux-headers-5.4.0-24-generic 5.4.0-24.28  
  amd64Linux kernel headers for version 5.4.0 on 64 bit x86 SMP
ii  linux-image-5.4.0-24-generic   5.4.0-24.28  
  amd64Signed kernel image generic
ii  linux-libc-dev:amd64   5.4.0-24.28  
  amd64Linux Kernel Headers for development
ii  linux-modules-5.4.0-24-generic 5.4.0-24.28  
  amd64Linux kernel extra modules for version 5.4.0 on 64 bit 
x86 SMP
ii  linux-modules-extra-5.4.0-24-generic   5.4.0-24.28  
  amd64Linux kernel extra modules for version 5.4.0 on 64 bit 
x86 SMP

** Affects: linux-signed (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873313

Title:
  linux-image-5.4.0-24-generic 5.4.0.24.29 missing from repo

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1872109] Re: blacking listing of nouveau should be removed from __init__.py

[Jack Howarth]

I checked with pymol upstream and the 2.4.0 release, which will contain
the removal of the nouveau blacklisting, is slated for a May release.
This change isn't associated with any fixes in pymol but just a
recognition that recent nouveau now has usable shader support.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872109

Title:
  blacking listing of nouveau should be removed from __init__.py

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1872109] Re: blacking listing of nouveau should be removed from __init__.py

[Jack Howarth]

diff --git a/modules/pymol/__init__.py b/modules/pymol/__init__.py
index fe299fbff..aaf978ade 100644
--- a/modules/pymol/__init__.py
+++ b/modules/pymol/__init__.py
@@ -332,8 +332,7 @@ def adapt_to_hardware(self):
 print(" Disabling shaders for Intel Express graphics")
 cmd.set("use_shaders", 0)
 
-elif (vendor == 'nouveau'
-or ' R300 ' in vendor # V: X.Org R300 Project, R: Gallium 0.4 on 
ATI RV370
+elif (' R300 ' in vendor # V: X.Org R300 Project, R: Gallium 0.4 on ATI 
RV370
 ):
 if invocation.options.show_splash:
 print(" Detected blacklisted graphics driver.  Disabling shaders.")

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872109

Title:
  blacking listing of nouveau should be removed from __init__.py

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1797791] Re: nvidia-440 installation issues need to be resolved and the package marked as 'tested'

[Jack Howarth]

I can also confirm that the nvidia-340 package in 20.04 builds usable
kernel modules and works fine on the same 2008 MacPro with Mac rom'd
GTX680.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797791

Title:
  nvidia-440 installation issues need to be resolved and the package
  marked as 'tested'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1872109] Re: blacking listing of nouveau should be removed from __init__.py

[Jack Howarth]

Note that this issue is always fixed in pymol trunk with...

https://github.com/schrodinger/pymol-open-
source/commit/af8c2e09c3ff45eaaeaac76a9fb89b9359340336


** Patch added: "do not blacklist "nouveau" driver"
   
https://bugs.launchpad.net/ubuntu/+source/pymol/+bug/1872109/+attachment/5351641/+files/af8c2e09c3ff45eaaeaac76a9fb89b9359340336.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872109

Title:
  blacking listing of nouveau should be removed from __init__.py

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1872109] [NEW] blacking listing of nouveau should be removed from __init__.py

[Jack Howarth]

Public bug reported:

The current pymol package for 2.3.0+dfsg-1build1 has upstream's code to
disable shader support on nouveau drivers in /usr/lib/python3/dist-
packages/pymol/__init__.py. This causes pymol to render very slowly
compared to the non-free nvidia drivers. Disabling this code...

#elif (vendor == 'nouveau'
#or ' R300 ' in vendor # V: X.Org R300 Project, R: Gallium 0.4 on 
ATI RV370
#):
#if invocation.options.show_splash:
#print(" Detected blacklisted graphics driver.  Disabling shaders.")
#cmd.set("use_shaders", 0)

restores the shader support under nouveau. Since Ubuntu's nouveau and
mesa are modern compared to the range of linux releases that the stock
pymol binaries have to run on, it is probably safe to make this change
for 20.04.

Filed a bug report on this upstream at...

https://github.com/schrodinger/pymol-open-source/issues/87

"shaders disabled on nouveau #87"

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872109

Title:
  blacking listing of nouveau should be removed from __init__.py

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 704763] Re: boot loader not installed to target disk

[Jack Howarth]

I ran into this problem under Ubuntu 20.04 Beta on my 2008 MacPro while
attempting to have the boot loader installed on the same drive as the
linux installation rather than the drive with my macOS installation.
Using the Custom Partitioning option to install / on /dev/sde2 (ext4)
and the device for the boot loader installation set to /dev/sde, the
following glitch occurred. The boot loader was still erroneously
installed on the EFI partition of the macOS drive (/dev/sda1) and worse
the installer recreated the EFI partition on /dev/sde1 with the
identical blkid name as that used by /dev/sda1. So it left my system
with two physical drives having identical blkids for separate
partitions.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/704763

Title:
  boot loader not installed to target disk

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1870937] [NEW] 3.8.2-0ubuntu2 produces SyntaxWarning

[Jack Howarth]

Public bug reported:

The installation of the new 3.8.2-0ubuntu2 update in Ubuntu 20.04
produces a series of warning...

Setting up python3 (3.8.2-0ubuntu2) ...
running python rtupdate hooks for python3.8...
/usr/share/hplip/base/utils.py:2060: SyntaxWarning: "is" with a literal. Did 
you mean "=="?
  if weburl is "" or weburl is None:
/usr/share/hplip/check-plugin.py:116: SyntaxWarning: "is" with a literal. Did 
you mean "=="?
  if log_level is 'debug':
/usr/share/hplip/check.py:685: SyntaxWarning: "is not" with a literal. Did you 
mean "!="?
  if 'getfacl' not in g and '' is not g and 'file' not in g:
/usr/share/hplip/installer/core_install.py:2037: SyntaxWarning: "is" with a 
literal. Did you mean "=="?
  if home_dir is "":
/usr/share/hplip/ui5/devmgr_ext.py:15: SyntaxWarning: "is not" with a literal. 
Did you mean "!="?
  if self.latest_available_version is not "":
/usr/share/hplip/ui5/devmgr_ext.py:37: SyntaxWarning: "is not" with a literal. 
Did you mean "!="?
  if self.latest_available_version is not "":
running python post-rtupdate hooks for python3.8...

** Affects: python3.8 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870937

Title:
  3.8.2-0ubuntu2 produces SyntaxWarning

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.8/+bug/1870937/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1797791] Re: nvidia-440 installation issues need to be resolved and the package marked as 'tested'

[Jack Howarth]

I can confirm, on a 2008 MacPro with Apple ROMed GTX680, that the nvidia
440 drivers bundled with the 20.04 beta release show the same behavior.
The Apple Cinema HD display LED comes on (indicating that the driver
loses contact with the display) as nvidia drivers are loaded and nvidia-
modeset executes.

Apr  4 14:35:03 howarth-MacPro kernel: [   57.436235] nvidia-modeset:
WARNING: GPU:0: Lost display notification (0:0x); continuing.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797791

Title:
  nvidia-440 installation issues need to be resolved and the package
  marked as 'tested'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1797791] Re: nvidia-440 installation issues need to be resolved and the package marked as 'tested'

[Jack Howarth]

** Summary changed:

- nvidia-340 installation issues need to be resolved and the package marked as 
'tested'
+ nvidia-440 installation issues need to be resolved and the package marked as 
'tested'

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797791

Title:
  nvidia-440 installation issues need to be resolved and the package
  marked as 'tested'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1845979] Re: Eoan Ermine's sysprof should be 3.34.0

[Jack Howarth]

Note that the Gnome press release specifically mentions the sysprof
improvements.

https://www.gnome.org/press/2019/09/gnome-3-34-released/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845979

Title:
  Eoan Ermine's sysprof should be 3.34.0

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1845979] [NEW] Eoan Ermine's sysprof should be 3.34.0

[Jack Howarth]

Public bug reported:

The sysprof in eoan is still based on 3.32.0. Since the improvements to
sysprof are considered one of the significant improvements in gnome
3.34.0, it should be upgraded to the matching new version.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845979

Title:
  Eoan Ermine's sysprof should be 3.34.0

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1796534] Re: plymouthd crashed with SIGSEGV in ply_renderer_set_handler_for_input_source()

[Jack Howarth]

I was able to suppress these fatal crashes in plymouth that launched the
bug reporter on that package under current 18.10 Cosmic by building and
installing the 0.9.3-1ubuntu12 release on launchpad

https://launchpad.net/ubuntu/+source/plymouth

from the disco dingo proposed updates. There are no obvious problems
with plymouth now.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796534

Title:
  plymouthd crashed with SIGSEGV in
  ply_renderer_set_handler_for_input_source()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1798807] [NEW] bcmwl-kernel-source fails to install if Nvidia card present in the absence of a network connection

[Jack Howarth]

Public bug reported:

When enabling the proprietary packages option on the Ubuntu installation
of xenial, bionic or cosmic x86_64 on a machine with both a wireless
card requiring the bcmwl-kernel-source package and an additional Nvidia
card present, the installation of the bcmwl-kernel-source package
doesn't occur. While the current installer doesn't allow the selected
proprietary driver packages to be viewed priorto completing their
installation, I assume the problem is, for a machine without a network
connection, that only the bcmwl-kernel-source package is available on
the Live iso image and that the absence of the nvidia packages is
fouling the installation of the bcmwl-kernel-source package.

This issue was discovered on a MacPro 3,1 which originally had a ATI
HD2600-XT graphics card as well as an Airport Extreme card. For that
combination, the xenial, bionic and cosmic installers all were able to
install the bcmwl-kernel-source package when proprietary driver package
installation was enabled in the installer. After swapping out that ATI
graphics card for a Nvidia GTX-680, I found that the xenial, bionic and
cosmic installers now failed to install the bcmwl-kernel-source package
in the presence of the Nvidia card without access to a network
connection during the installation. So I believe that the installer
needs to be more careful not to demand installation of proprietary
driver packages that are not present on the Live image in the absence of
a network connection.

Currently, one has to either connect the machine to the ethernet to
allow for network access to the repos for the installation of the bcmwl-
kernel-source package to succeed or manually install the  bcmwl-kernel-
source package and its dependencies from the appropriate sub-directories
in the pool directory of the Live usb image afterwards.

** Affects: ubuntu
 Importance: Undecided
 Status: New

** Summary changed:

- bcmwl-kernel-source fails to install if Nvidia card present
+ bcmwl-kernel-source fails to install if Nvidia card present in the absence of 
a network connection

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798807

Title:
  bcmwl-kernel-source fails to install if Nvidia card present in the
  absence of a network connection

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1797791] Re: nvidia-340 installation issues need to be resolved and the package marked as 'tested'

[Jack Howarth]

I believe that I have identified why the newer nvidia drivers which
depend on the new nvidia_drm kernel module fail on Mac hardware. That
new module depends on the ipmi modules. On Mac hardware, unsurprisingly,
the ipmi_si module fails to load and the ipmi device is not created.
Motherboards with issues supporting on the PC probably explain the
similar errors reported at...

https://devtalk.nvidia.com/default/topic/1037997/xid-61-black-screen-on-
startup-ubuntu-18-04-gtx-1060-mobile/

So Ubuntu should definitely hold onto the nvidia-340 package as long as
possible to support that hardware.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797791

Title:
  nvidia-340 installation issues need to be resolved and the package
  marked as 'tested'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1797791] [NEW] nvidia-340 installation issues need to be resolved and the package marked as 'tested'

[Jack Howarth]

Public bug reported:

The nvidia-graphics-drivers-340 is essential to many users. For example,
on my MacPro 3,1 equipped with an EVGA GTX-680 Mac version graphic card,
the nvidia 360, 390 and 396 drivers all fail due to issues with the new
nvidia_drm module resulting in no video output on DVI and HDMI.

https://devtalk.nvidia.com/default/topic/1042691/linux/black-screen-
with-mac-version-of-gtx-680/1

Similiar issues exist for a number of PC users as well...

https://devtalk.nvidia.com/default/topic/1037997/xid-61-black-screen-on-
startup-ubuntu-18-04-gtx-1060-mobile/

of which only some have been resolved. The nvidia-340 drivers are the
recommended fall back according to the Nvidia linux developers.

Unfortunately, the installation of the current nvidia-340
340.107-0ubuntu2 packaging is in really bad shape. The first error one
sees while attempting to install it are dpkg-divert errors like those
described in https://askubuntu.com/questions/419304/dpkg-divert-error-
rename-involves-overwriting-usr-lib-xorg-protocol-txt-wit but for the
files...

/usr/lib/x86_64-linux-gnu/libEGL.so.1.distrib
/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1.distrib
/usr/lib/x86_64-linux-gnu/libGLESv2.so.2.distrib.
/usr/lib/x86_64-linux-gnu/libGL.so.1.distrib

Currently one has to manually move these aside under a .bak suffix to
get past these post-removal script errors. I believe these issues may be
already addressed in the current nvidia-340 packaging residing on the
ppa:graphics-drivers/ppa repo.

The second installation issue that occurs is the same as that described
in https://askubuntu.com/questions/969352/uninstalling-and-then-
reinstalling-nvidia-384-kills-colord where currently the fix is the
same. One has to edit the installed nvidia-340.postinst file and change

NEWEST_KERNEL=$(get_newest_kernel "$(KERNEL")

to 
NEWEST_KERNEL=$(get_newest_kernel "$CURRENT_KERNEL")

following executing

sudo dpkg-reconfigure nvidia-340

to allow the installation to cleanly complete. Lastly, there seems to be
a missing dependency on the nvidia-340-dev that prevents akmods from
building the kernel modules which should be fixed.

The nvidia-340 drivers are supported until the end of 2019 by which time
hopefully Nvidia will finally clean up their current issues with the
newer drivers on problematic hardware.

https://nvidia.custhelp.com/app/answers/detail/a_id/3142

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: nvidia-340 340.107-0ubuntu2
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: wl nvidia
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 14 12:41:21 2018
InstallationDate: Installed on 2018-04-26 (170 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nvidia-graphics-drivers-340
UpgradeStatus: Upgraded to cosmic on 2018-09-30 (14 days ago)

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


** Tags: amd64 apport-bug cosmic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797791

Title:
  nvidia-340 installation issues need to be resolved and the package
  marked as 'tested'

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1764005] Re: Black-screen on boot with nvidia 390 for Budgie, MATE, Xubuntu, Kubuntu

[Jack Howarth]

I am seeing the same problem with current cosmic 18.10. The stock
nouveau drivers work fine but using 'sudo ubuntu-drivers autoinstall' to
install either the nvidia-390 or nvidia-396 drivers produces a black
screen (backlighting completely off) after the ubuntu splash screen has
been displayed on rebooting.

MacPro 2008
GPU: EVGA GTX 680 flashed with the Mac ROM images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764005

Title:
  Black-screen on boot with nvidia 390 for Budgie, MATE, Xubuntu,
  Kubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1764005/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1795516] [NEW] cosmic 18.10 beta installs grub-pc instead of grub-efi-amd64 on MacPro 3, 1

[Jack Howarth]

Public bug reported:

The bionic 18.04 installer used the grub-efi-amd64 package for grub on a
MacPro 3,1, however the cosmic 18.10 installer on the same machine
installs grub-pc instead (despite this being an EFI-64 machine).

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795516

Title:
  cosmic 18.10 beta installs grub-pc instead of grub-efi-amd64 on MacPro
  3,1

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1765960] [NEW] nautilus fails to insert disk with eject key

[Jack Howarth]

Public bug reported:

The nautilus handling of removable media capable of automated insertion
is flawed. On a MacPro 3,1, running bionic for instance, the first use
of the eject key on the keyboard ejects the SuperDrive DVD tray but the
second use of the eject key doesn't cause the tray to auto-insert. This
should be possible to fix as the manual execution of 'eject -t' on the
command line does cause the ejected tray to auto-insert back into the
drive.

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

** Project changed: lubuntu-tweaks => nautilus (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765960

Title:
  nautilus  fails to insert disk with eject key

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1763992] Re: pymol should be updated to 2.1.0 to use PyQt interface

[Jack Howarth]

Just to be clear, the changes required to the existing packaging are...

--- pymol-1.8.4.0+dfsg/debian/control   2016-10-20 11:33:21.0 -0400
+++ pymol-2.1.0+dfsg/debian/control 2018-04-14 13:57:37.0 -0400
@@ -24,6 +24,8 @@
 Package: pymol
 Architecture: any
 Depends: python-numpy,
+ python-pyqt5,
+ python-pyqt5.qtopengl,
  python-pmw,
  python-tk,
  ${misc:Depends},

--- pymol-1.8.4.0+dfsg/debian/patches/series2016-10-20 11:33:21.0 
-0400
+++ pymol-2.1.0+dfsg/debian/patches/series  2018-04-14 14:04:52.0 
-0400
@@ -4,8 +4,8 @@
 #24_autodock_plugin.patch
 27_fix_pymol_path_in_setup.patch
 28_no_data_install_in_python_path.patch
-29_fix_path_to_splash.patch
 31_fix_format-security.patch
 32_fix_spelling_lintian_warnings.patch
 33_fix_relative_paths_in_example_scripts.patch
 34_fix_examples_add_fetch_instead_of_load.patch
+40_fix_apbstools_search_path.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763992

Title:
  pymol should be updated to 2.1.0 to use PyQt interface

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1763992] [NEW] pymol should be updated to 2.1.0 to use PyQt interface

[Jack Howarth]

Public bug reported:

It is trivial to update the current pymol packaging in 18.04 to the
newest pymol 2.1.0 tarball at available on
https://sourceforge.net/projects/pymol/files/pymol/2/. The 2.1.0 release
now runs under a PyQt when present so the control file for the deb build
only needs...

 python-pyqt5,
 python-pyqt5.qtopengl,

added for the Depends of the pymol Package section to insure that the
PyQt support is available for use.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763992

Title:
  pymol should be updated to 2.1.0 to use PyQt interface

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1763992] Re: pymol should be updated to 2.1.0 to use PyQt interface

[Jack Howarth]

Add additional 40_fix_apbstools_search_path.patch should be added to
solve the long standing issue of the apbstools plugin not being able to
find the required psize.py and pdb2pqr.py files from the pdb2pqr package
in ubuntu. Trivial to fix.

** Patch added: "40_fix_apbstools_search_path.patch"
   
https://bugs.launchpad.net/ubuntu/+source/pymol/+bug/1763992/+attachment/5115693/+files/40_fix_apbstools_search_path.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763992

Title:
  pymol should be updated to 2.1.0 to use PyQt interface

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1763992] Re: pymol should be updated to 2.1.0 to use PyQt interface

[Jack Howarth]

The 33_fix_relative_paths_in_example_scripts.patch has to be regenerated
to cope with context changes in the pymol 2.1.0 sources.

** Patch added: "33_fix_relative_paths_in_example_scripts.patch"
   
https://bugs.launchpad.net/ubuntu/+source/pymol/+bug/1763992/+attachment/5115692/+files/33_fix_relative_paths_in_example_scripts.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763992

Title:
  pymol should be updated to 2.1.0 to use PyQt interface

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1763992] Re: pymol should be updated to 2.1.0 to use PyQt interface

[Jack Howarth]

The 22_fix_pymol_import.patch has to be regenerated to cope with context
changes in the pymol 2.1.0 sources.


** Patch added: "22_fix_pymol_import.patch"
   
https://bugs.launchpad.net/ubuntu/+source/pymol/+bug/1763992/+attachment/5115691/+files/22_fix_pymol_import.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763992

Title:
  pymol should be updated to 2.1.0 to use PyQt interface

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1763992] Re: pymol should be updated to 2.1.0 to use PyQt interface

[Jack Howarth]

The 02_test-suite.patch has to be regenerated to cope with context
changes in the pymol 2.1.0 sources.

** Patch added: "02_test-suite.patch"
   
https://bugs.launchpad.net/ubuntu/+source/pymol/+bug/1763992/+attachment/5115690/+files/02_test-suite.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763992

Title:
  pymol should be updated to 2.1.0 to use PyQt interface

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1763992] Re: pymol should be updated to 2.1.0 to use PyQt interface

[Jack Howarth]

The PyQt GUI for pymol appears as shown in the attached screen shot
under 18.04.

** Attachment added: "Screenshot from 2018-04-14 15-09-08.png"
   
https://bugs.launchpad.net/ubuntu/+source/pymol/+bug/1763992/+attachment/5115694/+files/Screenshot%20from%202018-04-14%2015-09-08.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763992

Title:
  pymol should be updated to 2.1.0 to use PyQt interface

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1760449] [NEW] pymol can't find ubuntu pdb2pqr files

[Jack Howarth]

Public bug reported:

The current pymol 1.8.4.0+dfsg-1build1 packaging fails to set the
APBS_PSIZE_LOCATION and APBS_PDB2PQR_LOCATION variables in
modules/pmg_tk/startup/apbs_tools.py which breaks the ability to perform
electrostatic surface calculations in the APBS Tools 2.1 plugin. The fix
is to apply the trivial patch...

diff -uNr a/modules/pmg_tk/startup/apbs_tools.py 
b/modules/pmg_tk/startup/apbs_tools.py
--- a/modules/pmg_tk/startup/apbs_tools.py  2018-04-01 11:54:24.156233715 
-0400
+++ b/modules/pmg_tk/startup/apbs_tools.py  2018-04-01 12:00:35.510665069 
-0400
@@ -167,8 +167,8 @@
 #
 APBS_BINARY_LOCATION = None # corresponding environment variable: 
APBS_BINARY_DIR
 APBS_WEB_LOCATION = None # corresponding environment variable: APBS_WEB_DIR
-APBS_PSIZE_LOCATION = None # corresponding environment variable: APBS_PSIZE_DIR
-APBS_PDB2PQR_LOCATION = None # corresponding environment variable: 
APBS_PDB2PQR_DIR
+APBS_PSIZE_LOCATION = '/usr/share/pdb2pqr/src/' # corresponding environment 
variable: APBS_PSIZE_DIR
+APBS_PDB2PQR_LOCATION = '/usr/share/pdb2pqr/' # corresponding environment 
variable: APBS_PDB2PQR_DIR
 TEMPORARY_FILE_DIR = tempfile.gettempdir() # corresponding environment 
variable: TEMP
 
 apbs_plea = ("IMPORTANT REQUEST: If you have not already done so, please 
register\n"

Note that with pymol, apbs and pdb2pqr installed the APBS Tools 2.1
plugin functionality can be tested with the steps

1) Enter the following in the Pymol command line window

Download: examples/apbsplugin_1.pml
This code has been put under version control in the project Pymol-script-repo
reinitialize 
fetch 3IG7, async=0
#load 3ig7.pdb, 3IG7
create cdk2, 3IG7 and polymer
create EFP, 3IG7 and organic and not resn ACE
delete 3IG7
 
hide everything, all
#h_add cdk2
#h_add EFP
show_as cartoon, cdk2
show_as sticks, EFP
util.cbay EFP
 
select flexible, byres cdk2 within 3.5 of EFP
show sticks, flexible
util.cbag flexible
disable flexible
zoom cdk2

2) Open the "APBS Tool2.1..." plugin.

3) Click in "Selection to use", and write "cdk2".

4) Click "Set grid"

5) To the left in "Molecular Surface", click "Show".

Currently the location of the required psize.py and pdb2pqr.py scripts
can't be found.

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


** Tags: patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760449

Title:
  pymol can't find ubuntu pdb2pqr files

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1760449] Re: pymol can't find ubuntu pdb2pqr files

[Jack Howarth]

To clarify, the steps to reproduce the functionality of the patched
pymol, the correct steps are described for Example 1 at
https://pymolwiki.org/index.php/Apbsplugin

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760449

Title:
  pymol can't find ubuntu pdb2pqr files

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs