Am 11.08.2016 um 15:46 schrieb Nicolas Chauvet:
2016-08-11 15:37 GMT+02:00 Reindl Harald
<h.reindl(a)thelounge.net>:
> vlc-core-3.0.0-0.5.fc24.x86_64
> vlc-3.0.0-0.5.fc24.x86_64
>
> crashs on intel graphics at least with modesetting driver, without palying a
> video, just start it from a konsole window and it will crash on close
> _________________________
>
> 3.0.0-0.2.fc24
>
> don't crash but have below a video a second VLC with a small, black video
> part and the complete controls below disabled
Weird, vlc-3.0.0-0.5 has fixed the module registration, so it could be
possible that some module wasn't registered properly and would have
caused the same crash
no idea
Reverting to vlc-3.0.0-0.2 without recreation of the module cache
(with /usr/lib64/vlc/vlc-cache-gen /usr/lib64/vlc ) seems an unsafe
test.
how is that my job - anyways it don't crash
Can you attach a backstrace to bugzilla?
that below is just "/usr/bin/strace -s 256 -q -y -f -v vlc", wait some
seconds and close VLC without playing any file with vlc-3.0.0-0.5
[pid 4312] poll([{fd=10<socket:[475459]>, events=POLLIN}], 1, -1) = 1
([{fd=10, revents=POLLIN}])
[pid 4312] recvmsg(10<socket:[475459]>, {msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="\241
\255\2\21\0\240\0@\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\34\0\256\2\304\0\0\0008\1\0\0\roG\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 64
[pid 4312] close(11<anon_inode:[eventfd]>) = 0
[pid 4312] futex(0x7f87e401a2ac, FUTEX_CMP_REQUEUE_PRIVATE, 1,
2147483647, 0x7f87e401a280, 2) = 1
[pid 4311] <... futex resumed> ) = 0
[pid 4311] futex(0x7f87e401a280, FUTEX_WAKE_PRIVATE, 1 <unfinished ...>
[pid 4312] madvise(0x7f87e1fa1000, 8368128, MADV_DONTNEED <unfinished ...>
[pid 4311] <... futex resumed> ) = 0
[pid 4312] <... madvise resumed> ) = 0
[pid 4312] exit(0) = ?
[pid 4311] poll([{fd=10<socket:[475459]>, events=POLLIN|POLLOUT}], 1,
-1 <unfinished ...>
[pid 4312] +++ exited with 0 +++
[pid 4311] <... poll resumed> ) = 1 ([{fd=10, revents=POLLOUT}])
[pid 4311] writev(10<socket:[475459]>,
[{iov_base=".\0\2\0\2\0\240\0_\0\2\0\r\0\240\0", iov_len=16}], 1) = 16
[pid 4311] poll([{fd=10<socket:[475459]>, events=POLLIN|POLLOUT}], 1,
-1) = 1 ([{fd=10, revents=POLLOUT}])
[pid 4311] writev(10<socket:[475459]>,
[{iov_base="<0\2\0\0\0\240\0+\0\1\0", iov_len=12}, {iov_base=NULL,
iov_len=0}, {iov_base="", iov_len=0}], 3) = 12
[pid 4311] poll([{fd=10<socket:[475459]>, events=POLLIN}], 1, -1) = 1
([{fd=10, revents=POLLIN}])
[pid 4311] recvmsg(10<socket:[475459]>, {msg_name=NULL, msg_namelen=0,
msg_iov=[{iov_base="\34\0\256\2\304\0\0\0008\1\0\0\roG\1\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\1\262\2\0\0\0\0\5\0\340\3\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 64
[pid 4311] --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR,
si_addr=0x108} ---
[pid 4313] +++ killed by SIGSEGV (core dumped) +++
[pid 4311] +++ killed by SIGSEGV (core dumped) +++
[pid 4310] +++ killed by SIGSEGV (core dumped) +++
+++ killed by SIGSEGV (core dumped) +++
Speicherzugriffsfehler (Speicherabzug geschrieben)
also any reason why using
the modesetting driver with intel?
because i have enough of the random screen flickering on IvyBridge
Can you reproduce with the intel DDX?
most likely, i guess that's the reason why my co-developer installed
"kaffeine" (identical hardware) while we normally maintain meta-packages
with packages intended to be installed