From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] vdpauinfo: segfault
Date: Fri, 29 Apr 2022 04:13:15 +0200 [thread overview]
Message-ID: <20220429021315.pDV7sDhd68gn6508VQgp5zPFr-Xuj-Xl8doID0NlF8Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12717@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1497 bytes --]
Closed issue by ackalker on void-packages repository
https://github.com/void-linux/void-packages/issues/12717
Description:
### System
* xuname:
Void 5.1.15_1 x86_64 GenuineIntel uptodate rrrrmdFFFFFFFFF
* package:
vdpauinfo-1.0_3
### Expected behavior
Running `vdpauinfo` should output VDPAU capabilities without crashing.
### Actual behavior
Running `vdpauinfo` on my system produces a segmentation fault without any other output.
### Steps to reproduce the behavior
* While running X, in a terminal run the command `vdpauinfo`
### Additional notes
* Graphics card
NVIDIA GM107 [GeForce GTX 750]
* Video driver
nouveau
I suspected that this could be a library issue, so I ran the tool again using `LD_DEBUG=libs`. The last bit of output on my system is (full output [here](https://gist.github.com/b58b979e3859d4862d96e15e06809758)):
```sh
$ LD_DEBUG=libs vdpauinfo
[...]
3793: calling init: /usr/lib/vdpau/libvdpau_nouveau.so.1
3793:
3793: find library=libnss_files.so.2 [0]; searching
3793: search cache=/etc/ld.so.cache
3793: trying file=/usr/lib/libnss_files.so.2
3793:
3793:
3793: calling init: /usr/lib/libnss_files.so.2
3793:
Segmentation fault
```
So it looks like the crash occurs while trying to init `libnss_files.so.2`, and in any case before control is transferred to `vdpauinfo` binary.
I'm wondering: could the recent `glibc` update be the culprit?
prev parent reply other threads:[~2022-04-29 2:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 15:37 [ISSUE] " voidlinux-github
2019-07-01 16:49 ` voidlinux-github
2021-02-15 5:50 ` ericonr
2022-04-15 2:12 ` github-actions
2022-04-29 2:13 ` github-actions [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220429021315.pDV7sDhd68gn6508VQgp5zPFr-Xuj-Xl8doID0NlF8Q@z \
--to=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).