[Bug 2076497] [NEW] pip list WARNING: Skipping /usr/lib/python3.12/dist-packages/charset_normalizer-3.3.2.dist-info due to invalid metadata entry 'name'

2024-08-10 Thread berglh
Public bug reported:

I recently upgraded from 23.10 to 24.04 of Ubuntu. When running pip3
list installed or sudo pip3 list installed I get the warning:

WARNING: Skipping /usr/lib/python3.12/dist-
packages/charset_normalizer-3.3.2.dist-info due to invalid metadata
entry 'name'

Navigating to this path, it is a directory with only one file called
"INSTALLER" with the contents "Debian". None of the other files
regarding the package info are in this folder.

This is the only folder in the /usr/lib/python3.12/dist-packages
directory as well.

I then attempted to reinstall the python-charset-normalizer package.
This made no change.

Removing the /usr/lib/python3.12/dist-
packages/charset_normalizer-3.3.2.dist-info directory resolves the
error, and I can still see the charset_normalizer pip module is
installed.

The package seems to be completely installed in /usr/lib/python3/dist-
packages/charset_normalizer-3.3.2.dist-info and /usr/lib/python3/dist-
packages/charset_normalizer.

As further troubleshooting, I installed the package on my additional
Ubuntu 24.04 machine, and the same behaviour is occurring.

This warning is a little annoying but, I don't think it's causing any
issues other than a warning in pip output. My guess is that it's a deb
packaging issue copying this file to the /usr/lib/python3.12/dist-
packages/charset_normalizer-3.3.2.dist-info directory inadvertently
during deb install.

** Affects: python-charset-normalizer (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/2076497

Title:
  pip list WARNING: Skipping /usr/lib/python3.12/dist-
  packages/charset_normalizer-3.3.2.dist-info due to invalid metadata
  entry 'name'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-charset-normalizer/+bug/2076497/+subscriptions


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

[Bug 2076479] Re: package anacron 2.3-39ubuntu2 failed to install/upgrade: installed anacron package post-installation script subprocess stalled, sent QUIT signal to subprocess to finish release upgra

2024-08-09 Thread berglh
Note: I am aware I have a failing drive, sorry for the log spam in
dmesg.

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

Title:
  package anacron 2.3-39ubuntu2 failed to install/upgrade: installed
  anacron package post-installation script subprocess stalled, sent QUIT
  signal to subprocess to finish release upgrade

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


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

[Bug 2076479] [NEW] package anacron 2.3-39ubuntu2 failed to install/upgrade: installed anacron package post-installation script subprocess stalled, sent QUIT signal to subprocess to finish release upg

2024-08-09 Thread berglh
Public bug reported:

This error occurred during a release upgrade from 23.10 to 24.04 of
Ubuntu server.

anacron seems to have upgraded, but the postinst script hangs. I tried
to stop the cron service, but it doesn't continue.

After the upgrade finished, the setup of anacron 2.3-39 continued again,
but was also stuck on the postinst script.

ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: anacron 2.3-39ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-44.44-generic 6.5.13
Uname: Linux 6.5.0-44-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Sat Aug 10 10:39:48 2024
ErrorMessage: installed anacron package post-installation script subprocess was 
killed by signal (Quit), core dumped
Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.22.6ubuntu6
 apt  2.7.14build2
SourcePackage: anacron
Title: package anacron 2.3-39ubuntu2 failed to install/upgrade: installed 
anacron package post-installation script subprocess was killed by signal 
(Quit), core dumped
UpgradeStatus: Upgraded to noble on 2024-08-10 (0 days ago)

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


** Tags: amd64 apport-package noble

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

Title:
  package anacron 2.3-39ubuntu2 failed to install/upgrade: installed
  anacron package post-installation script subprocess stalled, sent QUIT
  signal to subprocess to finish release upgrade

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


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

[Bug 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10

2022-02-04 Thread berglh
Hi Daniel,

Now it's the weekend here, I've created a new profile for my user and
the problem is gone.

I think we can safely close this as; "not a package bug". I will update
my comments on NVIDIA forums for people who may come across the same
issues.

Many thanks for your support,
Berg

** Changed in: nvidia-graphics-drivers-495 (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  GSYNC bug regression in 495.44 Ubuntu 21.10

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


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

[Bug 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10

2022-02-03 Thread berglh
Hi Daniel,

Thanks for the heads up! I went ahead and installed that driver from the
testing PPA, being careful not to install any other packages, and then
immediately disabled it. I'm not sure how I should be installing the
packages you linked, so the PPA seemed like the way to go.

Initially, I thought it had been solved, as I opened a few kitty
terminals and steam without the signal loss occurring for the first
minute or two. I was just in the process of replying to this thread in
Chrome, and thought I'd test once more, and it returned.

This got me thinking though, and I am now quite sheepish to admit that
creating a new Ubuntu user and logging in, I am unable to reproduce the
issue with both of the settings enabled. No doubt I should have tried
this first, rather than endlessly hoping driver upgrades would fix it.

I'm about 95% confident the issue is now with my existing Ubuntu user
profile, some program starting on login perhaps, or likely some
configuration which is not correct. My profile has gone through a few
distribution upgrades in this time, it normally should be fine, but no
doubt I've broken some configuration or have some Gnome extension, dconf
setting or something else that is responsible.

I am sorry for wasting your time. I will try to make time tomorrow to
backup and recreate my profile from scratch, testing as I go along. I am
quite confident that this signal loss issue, as strange as it is, is
related to my user profile.

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

Title:
  GSYNC bug regression in 495.44 Ubuntu 21.10

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


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

[Bug 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10

2022-02-02 Thread berglh
Thanks for the response,

The G-SYNC mode does work for applications that utilise it, such as
games. It just drops sync like that. I've commented on this thread which
has since gone cold:
https://forums.developer.nvidia.com/t/nvidia-470-74-breaks-gsync-
compatible-support-monitor-modulates-between-0-or-144hz-and-flickers-
black/189716/39

I'm not really sure what to say, other than it was drivers changing that
changed the behaviour. Guess I can try to start a new thread to see if
it gets some attention. I'd add, I've been using G-SYNC on Linux for
quite some time, so it's strange it's affecting me. I do have another
G-SYNC display at work, however, we're currently on WFH orders with
COVID-19 etc. I'll try this out when I am allowed back in the office.

I'm not sure if there is anything I can do to debug the mode changes to
see if I can get more info, I'm guessing that there are limited options
with proprietary drivers.

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

Title:
  GSYNC bug regression in 495.44 Ubuntu 21.10

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


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

[Bug 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10

2022-02-01 Thread berglh
** Description changed:

  [ Description ]
  
  Video of signal loss with flipping enabled: https://youtu.be/V5DGcHN-BJs
  
- In NVIDIA the 495 driver for Ubuntu 21.10, with G-SYNC enabled in OpenGL
- Settings of NVIDIA Settings, the G-SYNC compatible monitor loses sync
- momentarily (1~2 seconds) when switching to GPU accelerated application.
- Examples of this are; when launching a game full-screen game, launching
- a GPU accelerated Windows game, launching Steam, launching kitty
- terminal https://sw.kovidgoyal.net/kitty/.
+ In NVIDIA the 495 driver for Ubuntu 21.10, with G-SYNC enabled in OpenGL 
Settings of NVIDIA Settings, the G-SYNC compatible monitor loses sync 
momentarily (1~2 seconds) when switching to GPU accelerated application. 
Examples of this are:
+  - When launching a game full-screen
+  - Launching a GPU accelerated game in Window mode
+  - Launching Steam
+  - Launching kitty terminal https://sw.kovidgoyal.net/kitty/
  
  This issue happens at all refresh rates: 60 Hz, 120 Hz, 144 Hz and 165
  Hz.
  
- Note: that this example doesn't explicitly show G-SYNC being enabled,
- rather when G-SYNC is enabled in the settings, it will produce this
- behaviour. If I disable G-SYNC, but leave flipping enabled, the issue is
+ Note: This example doesn't explicitly show G-SYNC being enabled in the
+ onscreen indicator, rather what happens when G-SYNC is enabled in the
+ settings. If I disable G-SYNC, but leave flipping enabled, the issue is
  not present. If I enabled G-SYNC, but disable flipping, the issue is not
- present.
+ present. If both are enabled, then the issue occurs.
  
  [ Hardware ]
  
  - NVIDIA GeForce RTX 2080 Super
  - Dell 27" S2721DGF G-Sync Compatible monitor
  - High quality DisplayPort cable
  
  [ Settings ]
  
- In OpenGL the following settings are enabled:
+ In the NVIDIA OpenGL settings, the following settings are enabled:
  - Sync to VBlank Enabled
  - Allow Flipping Enabled
  - Image Setting: High Performance
  - Allow G-SYNC-/G-SYNC Compatible Enabled
  - Use Conformant Texture Clamping Enabled
  
  [ Observations ]
  
  When I disable Allow Flipping, the issue goes away. No signal is lost
  when changing to different GPU accelerated applications. Sometimes there
  is a brief flicker when opening a GPU accelerated program with flipping
- disabled, but it's not a single loss, rather a very fast few frame
- flicker. Flipping is required for G-SYNC to function, therefore losing
- the benefit of G-SYNC if I were to disable flipping.
+ disabled, but it's not a signal loss, rather a very fast momentary flick
+ of the display, but it's does not impact usability. As flipping is
+ required for G-SYNC to function, therefore losing the benefit of G-SYNC
+ if I were to disable flipping.
  
  [ Correlation to previous bug ]
  
- This issue was present in 21.04, eventually driver 495.44 resolve this
- problem on the 5.14.1 kernel. I will add that when I first had this
- machine and screen in 21.04, it was not experiencing the flipping issue.
+ This issue was present in Ubuntu 21.04, eventually driver 495.44
+ resolved this problem on the 5.14.1 kernel. I will add that when I first
+ had this machine and screen in 20.10 and 21.04, it was not experiencing
+ the signal loss issue.
  
- The bug described in the launchpad bug seems to reference the type of
- regression I experienced https://launchpad.net/bugs/1950665.
+ The bug described in the change log in this launchpad bug seems to
+ reference the type of regression I am experiencing
+ https://launchpad.net/bugs/1950665.
  
  [ Troubleshooting ]
  
  Full driver purges between trying different drivers:
  
  - Tried downgrading to 470.82
  - Went back to the standard kernel for 21.10 (5.13.0-21-generic) at the time
  - Tried deleting ~/.nv, ~/.cache/nvidia
  - Reverted to previous X11 conf
  - Tried 5.14.1 which was working in Ubuntu 21.04
  - Tried kernels 5.14.17, 5.15.6
  - Persists in 470.94 (NVIDIA bundle and Graphics Drivers PPA)
  - Persists in 495.46 (NVIDIA bundle and Graphics Drivers PPA)
  - Persists in 510.39.01 (NVIDIA bundle)

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

Title:
  GSYNC bug regression in 495.44 Ubuntu 21.10

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


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

[Bug 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10

2022-02-01 Thread berglh
Hi Daniel,

I've updated the description and added a video of the behaviour for your
reference.

Hopefully it's a bit clearer for you now.

Thanks


** Description changed:

- Similar to bug https://launchpad.net/bugs/1950665, the GSYNC regression
- bug has returned in 495.44 on Ubuntu 21.10. I have tried the standard
- kernel and 5.14.1 and 5.14.17, but they are all experiencing the same
- bug again.
+ [ Description ]
  
- Hardware is:
- - NVIDIA GeForce RTX 2080 Super
- - Dell 27" S2721DGF G-Sync Compatible monitor
- - High quality DisplayPort cable (This was replaced previously under 
suspicion)
+ Video of signal loss with flipping enabled: https://youtu.be/V5DGcHN-BJs
+ 
+ In NVIDIA the 495 driver for Ubuntu 21.10, with G-SYNC enabled in OpenGL
+ Settings of NVIDIA Settings, the G-SYNC compatible monitor loses sync
+ momentarily (1~2 seconds) when switching to GPU accelerated application.
+ Examples of this are; when launching a game full-screen game, launching
+ a GPU accelerated Windows game, launching Steam, launching kitty
+ terminal https://sw.kovidgoyal.net/kitty/.
  
  This issue happens at all refresh rates: 60 Hz, 120 Hz, 144 Hz and 165
  Hz.
  
- Prior to upgrading to Ubuntu 21.10, I had upgraded to 495.44 on Ubuntu
- 21.04 and kernel 5.14.1, and this problem was not present.
+ Note: that this example doesn't explicitly show G-SYNC being the issue,
+ rather when G-SYNC is enabled in the settings, it will produce this
+ behaviour.
  
- I then upgraded to Ubuntu 21.10, and the problem didn't seem to be
- present, but as of today I've noticed again.
+ [ Hardware ]
  
- I'm not sure what the cause is, but I have tried full driver purges,
- returned to 470.82, went back to the standard kernel for 21.10
- (5.13.0-21-generic), 5.14.1 and 5.14.17, and the problem continues to
- occur when any GPU accelerated application starts, in some cases when
- switching between applications (i.e. alt tabbing out of a game). A
- second or so of no signal occurs as it re-syncs.
+ - NVIDIA GeForce RTX 2080 Super
+ - Dell 27" S2721DGF G-Sync Compatible monitor
+ - High quality DisplayPort cable
  
- I am unsure if X11 has been updated in this time, I know there was work
- happening on GBM support, wondering if X11 has switched to using this
- instead of the EGL Streams direct approach that was used previously.
- Either-way, I'm still running X11 in all of these tests.
+ [ Settings ]
  
- Let me know if there are any tests you'd like me to try.
+ In OpenGL the following settings are enabled:
+ - Sync to VBlank Enabled
+ - Allow Flipping Enabled
+ - Image Setting: High Performance
+ - Allow G-SYNC-/G-SYNC Compatible Enabled
+ - Use Conformant Texture Clamping Enabled
+  
+ [ Observations ]
+ 
+ When I disable Allow Flipping, the issue goes away. No signal is lost
+ when changing to different GPU accelerated applications. However,
+ Flipping is required for G-SYNC to function, therefore losing the
+ benefit of G-SYNC.
+ 
+ [ Correlation to previous bug ]
+ 
+ This issue was present in 21.04, eventually driver 495.44 resolve this
+ problem on the 5.14.1 kernel. I will add that when I first had this
+ machine and screen in 21.04, it was not experiencing the flipping issue.
+ 
+ The bug described in the launchpad bug seems to reference the type of
+ regression I experienced https://launchpad.net/bugs/1950665.
+ 
+ [ Troubleshooting ]
+ 
+ Full driver purges between trying different drivers:
+ 
+ - Tried downgrading to 470.82
+ - Went back to the standard kernel for 21.10 (5.13.0-21-generic) at the time
+ - Tried deleting ~/.nv, ~/.cache/nvidia
+ - Reverted to previous X11 settings
+ - Tried 5.14.1 which was working in Ubuntu 21.04
+ - Tried kernels 5.14.17, 5.15.6
+ - Persists in 470.94 (NVIDIA bundle and Graphics Drivers PPA)
+ - Persists in 495.46 (NVIDIA bundle and Graphics Drivers PPA)
+ - Persists in 510.39.01 (NVIDIA bundle)

** Description changed:

  [ Description ]
  
  Video of signal loss with flipping enabled: https://youtu.be/V5DGcHN-BJs
  
  In NVIDIA the 495 driver for Ubuntu 21.10, with G-SYNC enabled in OpenGL
  Settings of NVIDIA Settings, the G-SYNC compatible monitor loses sync
  momentarily (1~2 seconds) when switching to GPU accelerated application.
  Examples of this are; when launching a game full-screen game, launching
  a GPU accelerated Windows game, launching Steam, launching kitty
  terminal https://sw.kovidgoyal.net/kitty/.
  
  This issue happens at all refresh rates: 60 Hz, 120 Hz, 144 Hz and 165
  Hz.
  
- Note: that this example doesn't explicitly show G-SYNC being the issue,
+ Note: that this example doesn't explicitly show G-SYNC being enabled,
  rather when G-SYNC is enabled in the settings, it will produce this
- behaviour.
+ behaviour. If I disable G-SYNC, but leave flipping enabled, the issue is
+ not present. If I enabled G-SYNC, but disable flipping, the issue is not
+ present.
  
  [ Hardware ]
  
  - NVIDIA GeForce RTX 2080 Super
  - Dell 27" S2721DGF G-Sync Compatible monitor
 

[Bug 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10

2022-02-01 Thread berglh
Bug persists in beta driver 510.39.01 from NVIDIA website.

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

Title:
  GSYNC bug regression in 495.44 Ubuntu 21.10

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


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

[Bug 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10

2021-12-17 Thread berglh
This problem persists on driver 495.46 from NVIDIA website which stated
the same regression fix in the patch notes, there was no change in the
flickering on G-SYNC mode change.

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

Title:
  GSYNC bug regression in 495.44 Ubuntu 21.10

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


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

[Bug 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10

2021-11-22 Thread berglh
I installed 495.44 from the NVIDIA website, and it predictably suffers
from the same issues as the Ubuntu graphics drivers package. I'm
guessing this specific fix is still not addressing the issue in 495.44.
I also tried 470.86, and it also has the same issue.

Previously in Ubuntu 21.04, I had downgraded to 460.xx, and the issue
was not present. I think my only option is to keybind the AllowFlipping
option as a toggle in via a bash script to enable/disable GSYNC when
desired. Disabling flipping, which in turn disables GSYNC as far as I
can tell, resolves this loss of sync issue. I  will just have to wait
for future NVIDIA drivers that hopefully fix this regression.

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

Title:
  GSYNC bug regression in 495.44 Ubuntu 21.10

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


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

[Bug 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10

2021-11-22 Thread berglh
@vanvugt, I just had a look at the 495.44 download page as I was looking
for new driver releases, and this same fix is mentioned on the NVIDIA
driver download page:
https://www.nvidia.com/Download/driverResults.aspx/181274/en-us

Third from the bottom:
"Fixed a regression which prevented DisplayPort and HDMI 2.1 variable refresh 
rate (VRR) G-SYNC Compatible monitors from functioning correctly in variable 
refresh rate mode, resulting in issues such as flickering."

I guess I should try to install it using the NVIDIA installer to see if
it's still present?

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

Title:
  GSYNC bug regression in 495.44 Ubuntu 21.10

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


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

[Bug 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10

2021-11-16 Thread berglh
Hi Daniel,

Thanks for looking into this. I saw the same commit message in the
proposed build for 470.86 by Alberto Milone. Just waiting for this to
replace 470.82 after I assume testing is completed.

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

Title:
  GSYNC bug regression in 495.44 Ubuntu 21.10

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


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

[Bug 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10

2021-11-13 Thread berglh
-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950720

Title:
  GSYNC bug regression in 495.44 Ubuntu 21.10

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


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

[Bug 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10

2021-11-12 Thread berglh
** Description changed:

  Similar to bug https://launchpad.net/bugs/1950665, the GSYNC regression
  bug has returned in 495.44 on Ubuntu 21.10. I have tried the standard
  kernel and 5.14.1 and 5.14.17, but they are all experiencing the same
  bug again.
  
  Hardware is:
  - NVIDIA GeForce RTX 2080 Super
  - Dell 27" S2721DGF G-Sync Compatible monitor
  - High quality DisplayPort cable (This was replaced previously under 
suspicion)
  
  This issue happens at all refresh rates: 60 Hz, 120 Hz, 144 Hz and 165
  Hz.
  
  Prior to upgrading to Ubuntu 21.10, I had upgraded to 495.44 on Ubuntu
  21.04 and kernel 5.14.1, and this problem was not present.
  
  I then upgraded to Ubuntu 21.10, and the problem didn't seem to be
  present, but as of today I've noticed again.
  
  I'm not sure what the cause is, but I have tried full driver purges,
  returned to 470.82, went back to the standard kernel for 21.10
  (5.13.0-21-generic), 5.14.1 and 5.14.17, and the problem continues to
  occur when any GPU accelerated application starts, in some cases when
  switching between applications (i.e. alt tabbing out of a game). A
  second or so of no signal occurs as it re-syncs.
  
  I am unsure if X11 has been updated in this time, I know there was work
  happening on GBM support, wondering if X11 has switched to using this
  instead of the EGL Streams direct approach that was used previously.
  Either-way, I'm still running X11 in all of these tests.
  
- Let me know if there are any test you'd like me to try.
+ Let me know if there are any tests you'd like me to try.

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

Title:
  GSYNC bug regression in 495.44 Ubuntu 21.10

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


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

[Bug 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10

2021-11-11 Thread berglh
** Description changed:

  Similar to bug https://launchpad.net/bugs/1950665, the GSYNC regression
  bug has returned in 495.44 on Ubuntu 21.10. I have tried the standard
  kernel and 5.14.1 and 5.14.17, but they are all experiencing the same
  bug again.
  
  Prior to upgrading to Ubuntu 21.10, I had upgraded to 495.44 on Ubuntu
  21.04 and kernel 5.14.1, and this problem was not present.
  
  I then upgraded to Ubuntu 21.10, and the problem didn't seem to be
  present, but as of today I've noticed again.
  
- I'm not sure what the cause is, but I have tried full driver purge,
+ I'm not sure what the cause is, but I have tried full driver purges,
  returned to 470.82, went back to the standard kernel for 21.10
  (5.13.0-21-generic), 5.14.1 and 5.14.17, and the problem continues to
- occur when any GPU accelerated application grabs focus of the screen. A
+ occur when any GPU accelerated application starts, in some cases when
+ switching between applications (i.e. alt tabbing out of a game). A
  second or so of no signal occurs as it re-syncs.
  
- I am unsure if X11 has been updated in this time, I know there was
- working GBM support, wondering if X11 has switched to using this instead
- of the EGL Streams direct approach that was used previously. Either-way,
- I'm still running X11.
+ I am unsure if X11 has been updated in this time, I know there was work
+ happening on GBM support, wondering if X11 has switched to using this
+ instead of the EGL Streams direct approach that was used previously.
+ Either-way, I'm still running X11 in all of these tests.
  
  Let me know if there are any test you'd like me to try.

** Description changed:

  Similar to bug https://launchpad.net/bugs/1950665, the GSYNC regression
  bug has returned in 495.44 on Ubuntu 21.10. I have tried the standard
  kernel and 5.14.1 and 5.14.17, but they are all experiencing the same
  bug again.
+ 
+ Hardware is:
+ - NVIDIA GeForce RTX 2080 Super
+ - Dell 27" S2721DGF G-Sync Compatible monitor
  
  Prior to upgrading to Ubuntu 21.10, I had upgraded to 495.44 on Ubuntu
  21.04 and kernel 5.14.1, and this problem was not present.
  
  I then upgraded to Ubuntu 21.10, and the problem didn't seem to be
  present, but as of today I've noticed again.
  
  I'm not sure what the cause is, but I have tried full driver purges,
  returned to 470.82, went back to the standard kernel for 21.10
  (5.13.0-21-generic), 5.14.1 and 5.14.17, and the problem continues to
  occur when any GPU accelerated application starts, in some cases when
  switching between applications (i.e. alt tabbing out of a game). A
  second or so of no signal occurs as it re-syncs.
  
  I am unsure if X11 has been updated in this time, I know there was work
  happening on GBM support, wondering if X11 has switched to using this
  instead of the EGL Streams direct approach that was used previously.
  Either-way, I'm still running X11 in all of these tests.
  
  Let me know if there are any test you'd like me to try.

** Description changed:

  Similar to bug https://launchpad.net/bugs/1950665, the GSYNC regression
  bug has returned in 495.44 on Ubuntu 21.10. I have tried the standard
  kernel and 5.14.1 and 5.14.17, but they are all experiencing the same
  bug again.
  
  Hardware is:
  - NVIDIA GeForce RTX 2080 Super
  - Dell 27" S2721DGF G-Sync Compatible monitor
+ - High quality DisplayPort cable (This was replaced previously under 
suspicion)
+ 
+ This issue happens at all refresh rates: 60 Hz, 120 Hz, 144 Hz and 165
+ Hz.
  
  Prior to upgrading to Ubuntu 21.10, I had upgraded to 495.44 on Ubuntu
  21.04 and kernel 5.14.1, and this problem was not present.
  
  I then upgraded to Ubuntu 21.10, and the problem didn't seem to be
  present, but as of today I've noticed again.
  
  I'm not sure what the cause is, but I have tried full driver purges,
  returned to 470.82, went back to the standard kernel for 21.10
  (5.13.0-21-generic), 5.14.1 and 5.14.17, and the problem continues to
  occur when any GPU accelerated application starts, in some cases when
  switching between applications (i.e. alt tabbing out of a game). A
  second or so of no signal occurs as it re-syncs.
  
  I am unsure if X11 has been updated in this time, I know there was work
  happening on GBM support, wondering if X11 has switched to using this
  instead of the EGL Streams direct approach that was used previously.
  Either-way, I'm still running X11 in all of these tests.
  
  Let me know if there are any test you'd like me to try.

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

Title:
  GSYNC bug regression in 495.44 Ubuntu 21.10

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


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

[Bug 1950720] [NEW] GSYNC bug regression in 495.44 Ubuntu 21.10

2021-11-11 Thread berglh
Public bug reported:

Similar to bug https://launchpad.net/bugs/1950665, the GSYNC regression
bug has returned in 495.44 on Ubuntu 21.10. I have tried the standard
kernel and 5.14.1 and 5.14.17, but they are all experiencing the same
bug again.

Prior to upgrading to Ubuntu 21.10, I had upgraded to 495.44 on Ubuntu
21.04 and kernel 5.14.1, and this problem was not present.

I then upgraded to Ubuntu 21.10, and the problem didn't seem to be
present, but as of today I've noticed again.

I'm not sure what the cause is, but I have tried full driver purge,
returned to 470.82, went back to the standard kernel for 21.10
(5.13.0-21-generic), 5.14.1 and 5.14.17, and the problem continues to
occur when any GPU accelerated application grabs focus of the screen. A
second or so of no signal occurs as it re-syncs.

I am unsure if X11 has been updated in this time, I know there was
working GBM support, wondering if X11 has switched to using this instead
of the EGL Streams direct approach that was used previously. Either-way,
I'm still running X11.

Let me know if there are any test you'd like me to try.

** Affects: nvidia-graphics-drivers-495 (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/1950720

Title:
  GSYNC bug regression in 495.44 Ubuntu 21.10

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


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

[Bug 1786575] Re: Dell XPS 15 9570 - Thermal Shutdown Event & Annoying Full-Speed Fan Spin Up

2021-08-27 Thread berglh
** Bug watch added: github.com/intel/thermal_daemon/issues #161
   https://github.com/intel/thermal_daemon/issues/161

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

Title:
  Dell XPS 15 9570 - Thermal Shutdown Event & Annoying Full-Speed Fan
  Spin Up

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


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

Re: [Bug 1786575] Re: Dell XPS 15 9570 - Thermal Shutdown Event & Annoying Full-Speed Fan Spin Up

2021-08-27 Thread berglh
Hi Colin,

I ended up creating some scripts to reduce the maximum turbo boost of my
CPU during heavy loads including the GPU. I just have a gnome key binding
to flick between normal boost and GPU+reduced boost. I've managed to avoid
these instabilities and things have been just fine.

> echo "60" | sudo tee /sys/devices/system/cpu/intel_pstate/max_perf_pct

In addition to this, I installed some thermal pads on the CPU MOSFETs to
bridge them thermally to the laptop aluminum cover (rather than just being
air cooled). I'm not sure that this was necessary, but there were some
examples of thermal imaging of them getting quite toasty above 80 degrees
on the internet, and this seemed like a good solution with minimal cost.

Anyway; the machine is on 21.04 now, so I keep it pretty up to date. I'm
not sure if this continues to be a problem, but I am happy to reduce my CPU
freq during GPU loads as I'm usually GPU bound anyways, it makes sense to
keep things from getting too hot.

Cheers,
Berg

On Fri, 27 Aug 2021 at 00:20, Colin Ian King <1786...@bugs.launchpad.net>
wrote:

> Thermald in bionic is relatively ancient. One may see better results
> with newer LTS versions of Ubuntu, such as focal. If this is still and
> issue perhaps upgrading to Focal 21.04 is worth trying.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1786575
>
> Title:
>   Dell XPS 15 9570 - Thermal Shutdown Event & Annoying Full-Speed Fan
>   Spin Up
>
> Status in thermald package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Main Problems:
>
>   - Incorrect performance throttling results in Thermal Shutdown Event
> (~100C on CPU) as reported in BIOS log
>   - System fan during system idle powers at full speed for 1 second every
> minute or so (could also be GPU fan)
>
>   Environment:
>
>   Dell BIOS: 1.3.0 (Also present in 1.2.0, 1.1.3)
>   CPU: Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
>   Operating Systems: Ubuntu 18.04.1 LTS
>   Thermald Version: 1.7
>   Ubuntu Thermald Package: 1.7.0-5ubuntu1
>   Kernel: 4.17.14-041714-generic (Also present with 4.15.0-29, 4.15.0-30,
> 4.17.11-041711)
>   Intel Microcode: 3.20180425.1~ubuntu0.18.04.2
>   Nvidia Driver: 396.51-0ubuntu0~gpu18.04.1
>   TLP Package: 1.1-2ubuntu1
>
>   I've documented this issue on the thermald Github page with thermald
>   debug logs and configuration:
>   https://github.com/intel/thermal_daemon/issues/161
>
>   Basically, I've attempted to set the temperature for B0D4 to as low as
>   85000 and while the debug log seems to indicate the trip has be made,
>   the CPU scailing isn't working to keep the CPU from thermal shutdown.
>   Disabling Turbo Boost prevents shutdown of the system.
>
>   I'd expect thermald to performance throttle the CPU correctly to
>   prevent it from a thermal overheat event.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1786575/+subscriptions
>
>

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

Title:
  Dell XPS 15 9570 - Thermal Shutdown Event & Annoying Full-Speed Fan
  Spin Up

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


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

[Bug 1928917] Re: 21.04 - MOK signed custom kernel not booting "invalid signature"

2021-06-10 Thread berglh
I am experiencing the same issue when using the Ubuntu generated MOK
cert to sign Ubuntu mainline kernels on Hirsute. I receive the exact
same error as the OP: "invalid signature" when grub tries to start the
manually signed kernel. The regular linux images from the Ubuntu PPAs
work just fine as they're signed by Canonical certs.

I have correctly enrolled the certificate as it's needed for the nvidia
driver kernel modules (DKMS) and these are loading correctly.

MOK_DIRECTORY="/var/lib/shim-signed/mok"
sbsign --key "$MOK_DIRECTORY/MOK.priv" --cert "$MOK_DIRECTORY/MOK.pem" --output 
"$KERNEL_IMAGE" "$KERNEL_IMAGE"

Running "sudo openssl x509 -in /var/lib/shim-signed/mok/MOK.pem -text"
shows the Extended Key Usage:

X509v3 Extended Key Usage:
Code Signing, 1.3.6.1.4.1.2312.16.1.2

My understanding is that this Code Signing value is very important to
describe what a MOK private key is allowed to sign. I believe that shim
checks the Linux image that is signed with the correct Code Signing
codes and if it doesn't match what it expects it returns the "invalid
signature" error. Anyway, for whatever reason, Ubuntu 21.04 does not
allow me to boot these signed kernels like 20.10 did. I do seem to be
loading the Grub2 Shim EFI boot loader which should validate the signed
image, but it does not.

I have now validated the same error on two different machines: Dell
Precision laptop and an AMD 5900X workstation on 21.04. So, I'm pretty
confident it's not limited to just my specific upgraded instance.

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

Title:
  21.04 - MOK signed custom kernel not booting "invalid signature"

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

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

[Bug 1857271] Re: Focal 440.44-0ubuntu1 PRIME Sync not working

2020-09-23 Thread berglh
Problem still exists with 450 drivers on Ubuntu 20.04.1.

Linux bdp 5.4.0-49-generic #53-Ubuntu SMP Fri Sep 18 09:54:57 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux
TU117GLM [Quadro T1000 Mobile]
450.66-0ubuntu0.20.04.1

eDP-1-1 connected (normal left inverted right x axis y axis)
PRIME Synchronization: 0 
DP-1-1 disconnected (normal left inverted right x axis y axis)
PRIME Synchronization: 1 
DP-1-2 connected primary 2560x1440+0+0 (0x29e) normal (normal left inverted 
right x axis y axis) 597mm x 336mm
PRIME Synchronization: 0 
DP-1-3 disconnected (normal left inverted right x axis y axis)
PRIME Synchronization: 1 
DP-1-1-1 disconnected (normal left inverted right x axis y axis)
PRIME Synchronization: 1 
DP-1-1-2 disconnected (normal left inverted right x axis y axis)
PRIME Synchronization: 1 
DP-1-1-3 connected 1080x1920+2560+0 (0x29f) left (normal left inverted right x 
axis y axis) 527mm x 296mm
PRIME Synchronization: 0 

** Summary changed:

- Focal 440.44-0ubuntu1 PRIME Sync not working
+ Focal PRIME Synchronization not Working

** Summary changed:

- Focal PRIME Synchronization not Working
+ Focal PRIME Synchronization still not eorking (450.x)

** Summary changed:

- Focal PRIME Synchronization still not eorking (450.x)
+ Focal PRIME Synchronization still not working (450.x)

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

Title:
  Focal PRIME Synchronization still not working (450.x)

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

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

[Bug 1857271] Re: Focal 440.44-0ubuntu1 PRIME Sync not working

2020-09-23 Thread berglh
** Also affects: nvidia-graphics-drivers-450 (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/1857271

Title:
  Focal 440.44-0ubuntu1 PRIME Sync not working

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

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

[Bug 1857271] Re: Focal 440.44-0ubuntu1 PRIME Sync not working

2020-07-19 Thread berglh
I am seeing this again on the latest stable release on Ubuntu 20.04 on a
Dell Precision with attached displays.

Linux bdp 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux
TU117GLM [Quadro T1000 Mobile]
nvidia-driver-440  440.100-0ubuntu0.20.04.1

xrandr output:
eDP-1-1 connected (normal left inverted right x axis y axis)
PRIME Synchronization: 0 
DP-1-1 disconnected (normal left inverted right x axis y axis)
PRIME Synchronization: 1 
DP-1-2 connected primary 2560x1440+0+0 (0x29e) normal (normal left inverted 
right x axis y axis) 597mm x 336mm
PRIME Synchronization: 0 
DP-1-3 disconnected (normal left inverted right x axis y axis)
PRIME Synchronization: 1 
DP-1-1-1 disconnected (normal left inverted right x axis y axis)
PRIME Synchronization: 1 
DP-1-1-2 disconnected (normal left inverted right x axis y axis)
PRIME Synchronization: 1 
DP-1-1-3 connected 1080x1920+2560+0 (0x29f) left (normal left inverted right x 
axis y axis) 527mm x 297mm
PRIME Synchronization: 0

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

Title:
  Focal 440.44-0ubuntu1 PRIME Sync not working

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

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

[Bug 1857271] Re: Focal 440.44-0ubuntu1 PRIME Sync not working

2020-05-19 Thread berglh
** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  Focal 440.44-0ubuntu1 PRIME Sync not working

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

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