On 2020-08-14 16:53 +0100, Ken Moffat via blfs-support wrote: > On Fri, Aug 14, 2020 at 10:39:44AM -0500, Douglas R. Reno via blfs-support > wrote: > > On 8/9/20 6:35 PM, Ken Moffat via blfs-support wrote: > > > Two or three weeks ago I noticed a problem with parole on my latest > > > build on my haswell (LFS from 25th July, BLFS from the next day). > > > Whatever I try to view, the screen broken into horizontal stripes, > > > rather like venetian blinds but with a mix of colours not apparently > > > related to the video which should be visible. > > > > > > On a machine using radeon (R600-series) video, parole works fine. > > > > > > On my haswell, the following all work fine: ffplay, gst-play-1.0, > > > vlc. > > > > > > Other things have, of course, got in the way, but I'm now ready to > > > document what has changed between working and broken versions, and > > > to ask for suggestions. > > > > > > Looking back at previous builds on this machine, a build in May was > > > fine, the intermediate build in June showed the same problem. > > > > > > The following packages, and versions, are common to both the good > > > and bad builds: running kernel 5.7.2, gcc-10.1.0, gstreamer-1.16.2, > > > fdk-aac-2.0.1, freetype-2.10.2, lame-3.100, libtheora-1.1.1, > > > libvorbis-1.3.7 (I upgraded older systems to that version), > > > libvpx-1.8.2, opus-1.3.1, x264-20200218, yasm-1.3.0, libvdpau-1.4, > > > libvdpau-va-gl-0.4.0, SDL2-2.0.12. > > > > > > Looking at what had changed: > > > > > > ffmpeg 4.2.2 on previous good systems, 4.3 and 4.3.1 on current. > > > > > > libva-2.7.1 on last working system and on June non-working, 2.8.0 on > > > latest. > > > > > > x265 3.3 on working, 3.4 on latest (now reverted to 3.3, symlink > > > fixed, gst-plugins-bad rebuilt) > > > > > > intel-vaapi-driver 2.4.0 on good, 2.4.1 on latest, now reverted to > > > 2.4.0. > > > > > > xf86-video-intel 20200218 on good, 20200518 on latest, now reverted > > > to 20200218. > > > > > > Before Bruce asks: I've used the same CFLAGS, CXXFLAGS throughout > > > these builds. > > > > > > At this stage, this is just a request for suggestions, and a > > > question whether parole is working on anyone's current intel > > > machiens with integrated graphics ? > > > > > > TIA > > > > > > ĸen > > > > I would say that I was able to get Parole working, but unfortunately I'm not > > able to: > > > > [Current thread is 1 (Thread 0x7fb5315b2a00 (LWP 6876))] > > (gdb) bt > > #0 0x00007fb5325379c2 in _XInternAtom > > (dpy=dpy@entry=0x7fb524003ee0, name=name@entry=0x438f75 > > "_NET_WM_WINDOW_OPACITY_LOCKED", onlyIfExis > > ts=onlyIfExists@entry=1, psig=psig@entry=0x7ffedf8e53b8, > > pidx=pidx@entry=0x7ffedf8e53b0, pn=pn@entry=0x > > 7ffedf8e53b4) at IntAtom.c:76 > > #1 0x00007fb532537cfb in XInternAtom > > (dpy=dpy@entry=0x7fb524003ee0, name=name@entry=0x438f75 > > "_NET_WM_WINDOW_OPACITY_LOCKED", onlyIfExis > > ts=onlyIfExists@entry=1) at IntAtom.c:175 > > #2 0x000000000041f4f6 in parole_player_set_wm_opacity_hint > > (widget=0x1a28510 [GtkWindow]) > > at parole-player.c:3071 > > #3 parole_player_init (player=0x1e98480 [ParolePlayer]) at > > parole-player.c:3734 > > #4 0x00007fb5327d1571 in g_type_create_instance (type=<optimized out>) at > > ../gobject/gtype.c:1867 > > #5 0x00007fb5327b8125 in g_object_new_internal > > (class=class@entry=0x1a77ed0, params=params@entry=0x7ffedf8e56a0, > > n_params=n_params@entry=1) > > at ../gobject/gobject.c:1937 > > #6 0x00007fb5327b9bb4 in g_object_new_valist > > (object_type=<optimized out>, > > first_property_name=first_property_name@entry=0x438348 "client-id", v > > ar_args=var_args@entry=0x7ffedf8e57e8) at ../gobject/gobject.c:2262 > > #7 0x00007fb5327b9f0c in g_object_new > > (object_type=<optimized out>, > > first_property_name=first_property_name@entry=0x438348 "client-id") > > at ../gobject/gobject.c:1780 > > #8 0x000000000042127e in parole_player_new (client_id=0x0) at > > parole-player.c:3739 > > #9 0x00000000004182af in main (argc=<optimized out>, argv=<optimized out>) > > at main.c:340 > > (gdb) > > > > When I launch Parole, it crashes with a segmentation fault. This is on my > > Intel system, with Mesa-20.1.5, gst-*-1.16.2 of course, and > > libxfce4ui-4.14.1 with the rest of the stack. > > > > > > I'm not sure what's causing this. > > > > Ken, you are able to get it to start at least without a segfault, right? > > > > Yes. On elogind and i965. > > > I'll be building this on my elogind system later, will verify that it works > > there. Maybe it's something with the Iris driver. I'll research how to back > > down to i965 to see if I can fix it that way, but it's acting like its > > elsewhere.
According to Arch wiki, i965 is still used by default on Haswell. Iris is the default on Broadwell and newer. So I don't think it's an Iris problem. -- Xi Ruoyao <xry...@mengyan1223.wang> School of Aerospace Science and Technology, Xidian University -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
