evince crashes the X server
Eyal Lebedinsky
eyal at eyal.emu.id.au
Wed Jul 30 13:40:40 UTC 2025
On 30/7/25 18:08, Enrico Weigelt, metux IT consult wrote:
> On 10.07.25 05:50, Eyal Lebedinsky wrote:
>
> Hi,
>
>> [163563.414] (EE) Backtrace:
>> [163563.416] (EE) unw_get_proc_name failed: no unwind info found [-10]
>> [163563.416] (EE) 0: /usr/lib64/xorg/modules/drivers/intel_drv.so (? +0x0) [0x7f3b716deede]
>
> Yet another segfault in the buggy intel driver. It's unmaintained for
> aeons. Tried to upstream lots of patches some time ago, nobody actually
> cared.
>
> Unless you've got really specific reaons to use this one, better use
> generic modesetting. For most cases, the intel driver is obsolete.
>
> Nevertheless, feel free to file a bug report @Xlibre, maybe somebody
> of us has the time to look into it:
>
> https://github.com/X11Libre/xf86-video-intel/issues
>
> For the time being, just use the generic modesetting driver.
Thanks Enrico,
I am not familiar with the modesetting driver. Nevertheless, after doing some reading,
I understand that it is a generic driver (maybe using a frame buffer?) and avoiding
specific intel acceleration primitives.
I modified
/etc/X11/xorg.conf
and replaced
Driver "intel"
with
Driver "modesetting"
then logged out/in.
So far it looks mostly OK. Reinstalled evince and it does not crash.
MythTV seems to perform fine.
Watching youtube in a resolution of FHD or UHD (full screen) does show some artifacts.
I need to learn what settings modesetting accepts (if any) to tune its performance. I will keep it for the moment.
> --mtx
--
Eyal at Home (eyal at eyal.emu.id.au)
More information about the xorg
mailing list