1 |
On Sat, Mar 21, 2020 at 9:35 PM Grant Edwards <grant.b.edwards@×××××.com> wrote: |
2 |
> |
3 |
> On 2020-03-22, Grant Edwards <grant.b.edwards@×××××.com> wrote: |
4 |
> |
5 |
> > VLC suddenly stopped working this week. Last week it worked fine, but |
6 |
> > now I get this: |
7 |
> > |
8 |
> > $ vlc |
9 |
> > VLC media player 3.0.8 Vetinari (revision 3.0.8-0-gf350b6b5a7) |
10 |
> > [000055814c41d3e0] main xml reader error: XML reader not found |
11 |
> > [000055814c399580] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. |
12 |
> > Segmentation fault |
13 |
> > |
14 |
> > I re-emerged it, but no change. Why is VLC suddenly looking for an |
15 |
> > XML reader and segfaulting when it doesn't find one? |
16 |
> > |
17 |
> > A few days ago, I did plug in a second monitor and used xrandr to |
18 |
> > configure a single display with two screens. Does that have something |
19 |
> > to do with VLC suddenly blowing a gasket about XML? |
20 |
> |
21 |
> It doesn't appear to be related. I switched back to my old single-monitor |
22 |
> configuration, and VLC still segfaults the same way. |
23 |
> |
24 |
> -- |
25 |
> Grant |
26 |
> |
27 |
> |
28 |
Is the xml use flag enabled? |
29 |
|
30 |
-- |
31 |
David Abbott (dabbott) |