Bug#1059339: nv-codec-headers: Version mismatch with nvidia-driver package

2023-12-22 Thread Tim H.
Source: nv-codec-headers
Version: 12.1.14.0-1
Severity: important

Dear Maintainer,

After I updated FFmpeg to version 7:6.1-5 hardware accelerated encoding
via h264_nvenc stopped working.

FFmpeg reports:
Driver does not support the required nvenc API version. Required: 12.1
Found: 12.0

[1] states that the minimum required nvidia driver version to support
nvenc 12.1 is 530.41.03 or higher. Yet the most recent version
available in trixie is currently 525.147.05-1.

I managed to compile FFmpeg against an older version (12.0.16.1) of the
headers which fixed the bug for me. Please note that my graphics card
is quite old (NVIDIA Corporation GM206 [GeForce GTX 960]), so I'm not
sure if this bug affects people with more up to date cards.

~ Tim

[1]: 
https://docs.nvidia.com/video-technologies/video-codec-sdk/12.1/read-me/index.html


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'oldoldstable'), (500,
'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64) Foreign Architectures: i386

Kernel: Linux 6.1.68-1 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE
not set Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)



Bug#1053199: liferea does not show feed item contents after 1.15.2-1->1.15.3-1 update

2023-10-10 Thread Tim H.
Hi.

Same error here.

$ liferea
eglExportDMABUFImageMESA failed
eglExportDMABUFImageMESA failed
eglExportDMABUFImageMESA failed
sys:1: Warning: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
sys:1: Warning: g_uri_is_valid: assertion 'uri_string != NULL' failed

I'm also using the nvidia proprietary driver (525.125.06-2). Window
manager is Fluxbox. Downgrading liferea to the previous version doesn't
fix the error though.

I also tested downgrading all libwebkit2gtk related packages to version
2.40.5-1. After that the content window works again.

~Tim



Bug#729535: general: mouse sometimes slow upon boot. must reboot to fix.

2013-11-13 Thread Tim H
Package: general
Severity: important

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these lines ***
Rebooted system after work (cold boot), and logged into my user name, started
up X and my mouse was very slow and unresponsive. Sometimes freezing. If frozen
I have to switch to another virtual terminal, and then switch back to X to un-
freeze it.  When it's slow, switching between the terminal and X does nothing.
I have to reboot the entire system and log back in, fire up X and the mouse is
then responsive again. I do this a few times a day and it's quite a pest.

-- System Information:
Debian Release: 7.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org