To clear up some confusion for anyone following this via the Debian Bugs
website (I also got confused by this myself) - the last two messages:
#25 and #30, are displayed out of order.
My #25:
>That log is from my initial message, when I still had libvdpau-va-gl1
was a reply on Rémi's #30:
>Your
That log is from my initial message, when I still had libvdpau-va-gl1
installed. Since then, I have uninstalled it and VLC no longer uses
vdpau. I'm attaching the updated crash log for you to see.
Note that VLC successfully uses vaapi_vld for hardware accelerated
decoding when the video first play
and I assume similar would happen if I try to downgrade
libav*.
On Fri, Jul 12, 2024 at 11:47 AM Rémi Denis-Courmont
wrote:
> Hi,
>
> Le perjantaina 12. heinäkuuta 2024, 3.02.16 EEST nurupo a écrit :
> > Seeing how there is no reply, I decided to clarify things a bit.
> > Ho
Seeing how there is no reply, I decided to clarify things a bit.
Hopefully you find it useful.
As you can see from the attached vlc-crash.log.gz, my iGPU is Intel
Sandybridge Mobile, and I'm using "Intel i965 driver for Intel(R)
Sandybridge Mobile - 2.4.1 for hardware decoding". It might be an old
Package: vlc
Version: 3.0.21-0+deb11u1
Severity: important
X-Debbugs-Cc: t...@security.debian.org
Dear Maintainer,
I have recently updated packages on my Debian Bullseye system, which
also updated VLC from 3.0.20 to 3.0.21. After the update, I noticed that
whenever I try to seek in a video, VLC c
It looks like starting with 4.0.0, C and C++ libraries got split in
separate codebases and their version numbers have decoupled -- the
latest msgpack-c release is 4.0.0, while C++ had 4.0.0, 4.0.1, 4.0.2,
4.0.3 and 4.1.0 releases[1].
[1] https://github.com/msgpack/msgpack-c/releases
Package: libmsgpack-dev
Version: 3.3.0-4
Severity: wishlist
Dear Maintainer,
MessagePack provides separate C and C++ APIs. If all you want is the C
API, having to install around 150MiB of C++ boost libraries is rather
undesired. It would be nice if the package was split into two -- one
providing
Package: apt-listbugs
Version: 0.1.35
In my syslog I see apt-listbugs.service running every hour, claiming
it runs a *daily* job:
Jun 16 08:38:18 debian systemd[1]: Starting Daily apt-listbugs
preferences cleanup...
Jun 16 08:38:18 debian systemd[1]: apt-listbugs.service: Succeeded.
Jun 16 08:38:
Interestingly enough, ffmpeg package in Ubuntu 20.04 LTS has NVENC enabled:
>ffmpeg (7:4.2.2-1ubuntu1) focal; urgency=medium
>
> * Build with external nv-codec-headers for NVENC accelerated video
>encoding. (LP: #1810649)
>- debian/control:
> + Add B-D libffmpeg-nvenc-dev
>- debi
Package: ferm
Version: 2.5-1.1
Severity: serious
Tags: upstream
Dear Maintainer,
Ferm got updated from v2.4 to v2.5, which brought a regression of @ipfilter()
function, when used, resulting in an error.
I believe the serious severity is warranted. The error makes it so that ferm
doesn't apply an
Since the VAAPI patch is originally taken from Arch Linux, it might be
worth while to check if they had any issues with it on Chromium 79.
Looking at the comments and changes in
https://aur.archlinux.org/packages/chromium-vaapi it looks like they
did, and they have fixed those issues by updating th
No point in reporting this bug upstream, they will not be able to
reproduce it as it's related to the hardware video acceleration patch
that Debian has recently started applying on top of the upstream
Chromium:
https://salsa.debian.org/chromium-team/chromium/blob/c88b97a6dc183a6a7f8a05aee9e9995728
The patch added in 78.0.3904.97-1 works.
There is an extra step you must do to enable it though. You need to
start Chromium with --ignore-gpu-blacklist flag. I have added it to my
/etc/chromium.d/default-flags.
Also, if your GPU doesn't support vp9 video decoding, you can use
h264ify or enhanced-
Thanks for the reply, I have identified the issue.
I was trying to build it on a NTFS fs and it setup to set 0777 on all files.
On Thu, Dec 13, 2018 at 11:21 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:
> This is an automatic notification regarding your Bug report
> which was fil
Looks like this bug got resolved. Had the same issue before, but it got
fixed in the latest (4:17.08.3-1) version of the package.
This is also happening for me. Whenever I start Gwenview, I get a message
box:
"There are two actions (Cut, Delete) that want to use the same shortcut
(Shift+Del). This is most probably a bug. Please report it in bugs.kde.org"
It's minor bug as clicking Ok in the message box takes you to Gwenview
16 matches
Mail list logo
