firefox crashes Xorg

(this maybe should have been in my earlier post...)
From the first post in the thread, I'd guess either the problem might be located by trying to similarly run *other* qt4 applications outside of X, or rebuilding the qt4 stuff that specifically depends on cairo that you have installed. (Just a guess though.)
 
I have similar problems with the launch of firefox.

Code:
firefox -v
Mozilla Firefox 12.0
uname -pro
FreeBSD 9.0-RELEASE amd64

With cairo-1.12.2,1 firefox crashes Xorg and with cairo-1.10.2_3,1 all fine.
I have a Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) rev 12.
 
mlinuxgada said:
It's not a FreeBSD problem, but was cairo even tested before inserting into ports?
Yes. I (other users and jb_fvwm2 in here too) can't reproduce any of problems with all ports that what users have reported in here thread. It's specific to some certain driver or/and xorg-server stuff that I don't know. It's not a cairo bug, btw.

Anyway, guys, you do not need to rebuild anything. It will not solve your problem, because here is no ABI/API break.

Here's patch available for you to test: http://lists.freebsd.org/pipermail/freebsd-ports/2012-May/075103.html
 
Hi, guys.

Applied this xorg-server patch but didn't work for me. Almost all of my GTK-based apps are crashing. Other ones like xterm, even Okular (QT4-based) run normally.
 
Hello,

I upgraded cairo back to 1.12. Placed the patch in the right directory. Reinstalled Xserver. But still if I start up Firefox X crashes. And this started after updating cairo.

Roelof

Edit 1: Can it be a help if I dumped the dumped core files of the crash somewhere?
 
Other people have reported that the patch doesn't help either. It means that I will have to back out cairo this weekend. Future versions of Firefox will need a newer cairo.

roelof said:
Edit 1: Can it be a help if I put dumped the dumped core files of the crash somewhere.
No need to. Linux folks already knew and most or all fixes are already in the Xorg. Our Xorg stuff is out of date.
 
As a temporary solution, I'm using tightvnc. After the traditional startx I just log to localhost:1 in fullscreen mode. As I'm using fluxbox it's pretty straightforward to set up. Inside VNC, everything runs fine.
 
So, you're using a VNC for using your own desktop? And weird that inside that everything works fine.

@mezz:

Is it then not better to update X instead of dropping cairo 1.12?
 
Yes. TightVNC doesn't run any Xorg server code at all. Maybe that's the reason why Firefox and other GTK-based are working.

I agree that it's better to wait for a patch than downgrade the system. Has anyone tried different video cards?
 
Yes, it's best to update Xorg instead of dropping Cairo 1.12. But with broken Xorg for a week is unacceptable to me as I care about the quality very much. I do not think updating Xorg is easy. If it was easy we would already have the latest Xorg. Although I have never worked with Xorg stuff before so I am probably wrong about it.

Downgrading cairo today then working on Xorg/cairo stuff in the different tree (prefer in x11@'s unstable tree) is the best way to do it.
 
Confirmed here as well. Cairo 1.12 causes Xorg to die. Simply reverting to Cairo 1.10 with pkg_add -r cairo brings firefox back to life. A parallel machine without port upgrades within the past week runs firefox without incident.
 
mezz:

I agree with you. For now downgrade is the best option and after that a developer can try to solve this.
And I'm happy that quality is important.
 
I think I have the same issue with firafox crashing Xorg, but What I noticed is, it happens only when I login to DWM or fluxbox (I did not tested other window managers).
When I was logged in to MATE session, everything works fine without any issue.
 
I am still struggling with the xorg crash when starting firefox and chromium in window managers (DWM and fluxbox).

My system is running FreeBSD 12.1-RELEASE-p6

I have Intel(R) Core(TM) i5-4300U CPU @ 1.90GHz (2494.28-MHz K8-class CPU)
and Intel Haswell-ULT Integrated Graphics Controller.


I have these drm related packages installed

Code:
drm-legacy-kmod-g20200306      Legacy DRM modules for the linuxkpi-based KMS components
libdrm-2.4.99,1                Userspace interface to kernel Direct Rendering Module services

In my /etc/rc.conf I have:
Code:
kld_list="drm2.ko /boot/modules/i915kms.ko fuse"

And this is the error I got in /var/log/Xorg.0.log
Code:
[   877.849] (EE)
[   877.849] (EE) Backtrace:
[   877.853] (EE) 0: /usr/local/bin/Xorg (?+0x0) [0x41bc20]
[   877.857] (EE) 1: /lib/libthr.so.3 (pthread_sigmask+0x53e) [0x800b1d82e]
[   877.861] (EE) 2: /lib/libthr.so.3 (pthread_getspecific+0xdef) [0x800b1d63f]
[   877.863] (EE) 3: ? (?+0x0) [0x7ffffffff193]
[   877.867] (EE) 4: /usr/local/lib/dri/i965_dri.so (?+0x0) [0x802778ae0]
[   877.870] (EE) 5: /usr/local/lib/dri/i965_dri.so (?+0x0) [0x802778540]
[   877.872] (EE) 6: /usr/local/lib/dri/i965_dri.so (?+0x0) [0x8024a7e10]
[   877.874] (EE) 7: /usr/local/lib/dri/i965_dri.so (?+0x0) [0x8024a7010]
[   877.877] (EE) 8: /usr/local/lib/dri/i965_dri.so (?+0x0) [0x8024ae790]
[   877.879] (EE) 9: /usr/local/lib/dri/i965_dri.so (?+0x0) [0x8021a1930]
[   877.882] (EE) 10: /usr/local/lib/dri/i965_dri.so (?+0x0) [0x8021a1d60]
[   877.884] (EE) 11: /usr/local/lib/dri/i965_dri.so (?+0x0) [0x8024aff50]
[   877.887] (EE) 12: /usr/local/lib/dri/i965_dri.so (?+0x0) [0x8024af140]
[   877.889] (EE) 13: /usr/local/lib/dri/i965_dri.so (?+0x0) [0x8021939d0]
[   877.892] (EE) 14: /usr/local/lib/dri/i965_dri.so (?+0x0) [0x80218d020]
[   877.894] (EE) 15: /usr/local/lib/dri/i965_dri.so (?+0x0) [0x80218d230]
[   877.896] (EE) 16: /usr/local/lib/xorg/modules/libglamoregl.so (?+0x0) [0x801c0ac50]
[   877.899] (EE) 17: /usr/local/lib/xorg/modules/libglamoregl.so (?+0x0) [0x801bf9c20]
[   877.901] (EE) 18: /usr/local/bin/Xorg (?+0x0) [0x3f6f30]
[   877.904] (EE) 19: /usr/local/bin/Xorg (?+0x0) [0x3f7400]
[   877.906] (EE) 20: /usr/local/lib/xorg/modules/libglamoregl.so (?+0x0) [0x801bfaaa0]
[   877.909] (EE) 21: /usr/local/bin/Xorg (?+0x0) [0x390f70]
[   877.911] (EE) 22: /usr/local/bin/Xorg (?+0x0) [0x298a60]
[   877.913] (EE) 23: /usr/local/bin/Xorg (?+0x0) [0x295fd0]
[   877.916] (EE) 24: /usr/local/bin/Xorg (?+0x0) [0x2a04e0]
[   877.918] (EE) 25: /usr/local/bin/Xorg (?+0x0) [0x289000]
[   877.920] (EE) 26: ? (?+0x0) [0x800457000]
[   877.921] (EE)
[   877.921] (EE) Segmentation fault at address 0xa0030
[   877.921] (EE)
Fatal server error:
[   877.921] (EE) Caught signal 11 (Segmentation fault). Server aborting
[   877.921] (EE)
[   877.921] (EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
for help.
[   877.921] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[   877.921] (EE)
[   877.921] (II) AIGLX: Suspending AIGLX clients for VT switch
[   877.922] (EE) Server terminated with error (1). Closing log file.

Can some one explain me what is wrong with my configs , drivers or anything ?
 
What is "drm2.ko"? Also, what graphics do you have, Intel? If so, do you have "libva-intel-driver" installed?

EDIT - forgot to add: this is an 8 year old necrobump. Best to start your own thread with your specific issue than bumping an old one.
 
I have Intel(R) Core(TM) i5-4300U CPU @ 1.90GHz (2494.28-MHz K8-class CPU)
and Intel Haswell-ULT Integrated Graphics Controller.

Code:
jacek@thinkpad-x240:~ % sudo pkg info | grep driver
libva-2.6.1_2                  VAAPI wrapper and dummy driver
mesa-dri-18.3.2_10             OpenGL hardware acceleration drivers for DRI2+
xdriinfo-1.0.6_3               Query configuration information of DRI drivers
xf86-input-keyboard-1.9.0_4    X.Org keyboard input driver
xf86-input-libinput-0.29.0     X.Org libinput input driver
xf86-input-mouse-1.9.3_3       X.Org mouse input driver
xf86-video-scfb-0.0.5_2        X.Org syscons display driver
xf86-video-vesa-2.4.0_3        X.Org vesa display driver
xorg-drivers-7.7_6             X.org drivers meta-port
jacek@thinkpad-x240:~ %

I found somewhere in the forum that drm2.ko may be required if system is reporting that some old drm driver is used .
 
I saw that post as well but I have a modern Intel GPU and have never used legacy so can't speak to that. Maybe someone else has and can chime in.
 
Hmm, Funny and strange , for Intel Haswell I should be using drm-legacy-kmod (it was stated if few threads at this forum) but I am getting this crash.

I tried something stupid - I installed drm-kmod package (drm-legacy-kmod was automatically removed) and now it is working fine.
Logitech Mouse is a bit sluggish but everything works and there is no crash.

The solution for my system with FreeBSD 12.1-RELEASE-p6 was to use drm-kmod instead of drm-legacy-kmod.


Code:
drm-fbsd12.0-kmod-4.16.g20200221 DRM modules for the linuxkpi-based KMS components
drm-kmod-g20190710             Metaport of DRM modules for the linuxkpi-based KMS components
libdrm-2.4.99,1                Userspace interface to kernel Direct Rendering Module services

I do not know how to explain it.
 
Have you installed libva-intel-driver as well? Not sure why your mouse is sluggish and not sure if it will help but I needed to install that package as well.
 
According to the wiki https://wiki.freebsd.org/Graphics,
Furthermore, if you notice high CPU usage or excessive tearing while viewing HD video it is reported that installing the libva-intel-driver is helpful, as it enables VAAPI support on these systems. This package should be installed in addition to the drm-kmod, mesa-libs and mesa-dri packages.

Not sure that will help with your mouse issue but I always installed that package on my system. I did game on it though so not sure your use case.
 
Back
Top