System used: Xubuntu Feisty Fawn (7.04) beta with xfce 188.8.131.52 and xfce4-terminal 0.2.6
Hardware: Laptop with i810 video chipset (using i810 X.org driver)
The X server crashes when opening xfce4-terminal.
This bug was reported in https://bugs.launchpad.net/ubuntu/+source/xfce4-terminal/+bug/91849 and we were advised to file it to xfce bugzilla.
Something like this happens to me too; on Gentoo. Also using xorg-server 1.3 and i810.
The crash happens for me when I open a new tab or right click, so maybe it's a gtk issue (using borderless windows). The new tab or right click menu shows for about a second, and then crashes.
Steffan, I'm also using Xfce on Gentoo, with the i810 driver and xorg-server 1.3. The issue for me seems to be that the Xfce startup scripts get run twice, causing all the Xfce processes to believe there are two screens available, and draw everything twice on the same screen. This caused massive slowdowns in certain applications, but I cannot find anything in any of the startup scripts to cause this. The situation only occurs with xorg-server 1.3; reverting back to a previous version eliminates the issue. I'm still not sure whether this is an X.org bug or an Xfce bug.
I've also seen occasional window borders disappearing, but only when using Beryl, and that was down to Beryl segfaulting under the above conditions.
(In reply to comment #2)
> Steffan, I'm also using Xfce on Gentoo, with the i810 driver and xorg-server 1.3. The issue for me seems to be that the Xfce startup scripts get run twice, causing all the Xfce processes to believe there are two screens available, and draw everything twice on the same screen. This caused massive slowdowns in certain applications, but I cannot find anything in any of the startup scripts to cause this. The situation only occurs with xorg-server 1.3; reverting back to a previous version eliminates the issue. I'm still not sure whether this is an X.org bug or an Xfce bug.
I don't think that the startup script is run twice; at least the Xfce processes are only showing up once in `ps -ef | grep $USER`. How do you check that the startup is not run twice?
Wrt slow redraws, firefox and gaim have been significant slower at scrolling.
The terminal crash stil only happens for me when opening a new tab or right clicking, and it's just the terminal that crashes (not Xfce). This is with Xorg-server 1.3 and i810-driver 2.0.0, not with xorg-server 1.2 and i810-driver 1.7.4.
(In reply to comment #3)
Sorry about the linewrap... :)
The processes only exist once for me too, but it was the fact that Xfce was convinced I had two screens, the fact that the screen flickered twice when starting X, and the fact that the Xfce splash screen flickered as two copies fought for the display that led me to realise that something was being duplicated. After digging through the process list and checking through /usr/bin/startxfce4 and /etc/xdg/xfce4/xinitrc, it became clear that at least one of them (if not both) was being run at least twice, and Xfce was getting very confused. I'm suspecting that it's down to changes in how Xfce and xinit coordinate in xorg-server 1.3.. something for X and Xfce devs to communicate on?
See also the following Ubuntu bugs:
(In reply to comment #0)
See also the thread in Ubuntu Forums:
Another bug from Launchpad which may have something to do with this one:
Ok, the 'running twice' thing is a red herring. For starters, there's no way running startxfce4 (or xinitrc) twice can make anything believe that there are two screens.
As for 'xfce crashes'. what crashes? Does Xorg crash? Does xfce4-session crash?
The Ubuntu bug referenced in comment #1 seems to indicate to me that this is an Xorg problem, and has nothing to do with Xfce.
For fun, try launching an xterm, and from there, start Xfce terminal, but before that, run (in the xterm): "export XLIB_SKIP_ARGB_VISUALS=1". Does that work, or does X still crash?
But really, most important bit of information: WHAT exactly is crashing?
For me, at least, it's only Terminal that is crashing. I downgraded to xorg server 1.2 for the moment, but I could probably find time to install 1.3 and Xfce libraries with debug symbols this weekend.
From what I read, it's Xorg that crashes, right?
I'm using Xorg 7.2 on Ubuntu Feisty with another driver (Open Source nv driver and proprietary driver nvidia). I tried all kinds of configurations and I have not experienced any crash.
So, to summarize things:
- Xorg 7.2 crashes with the Intel i810 driver (and possibly others, SiS?),
- Xorg 7.2 does not crash with other drivers (at least not with all),
- Downgrading the driver fixes the issue for at lest one user (Steffen),
- A client application should never be able to crash the X server.
That really looks like a bug in Xorg. What makes you think that the problem lies in Xfce?
(In reply to comment #10)
> That really looks like a bug in Xorg. What makes you think that the problem
> lies in Xfce?
I have this same problem - running terminal in Xfce crash the X server (Slackware 11.0, kernel v.2.6, Xface v 4.4.1) But if I run terminal without Xfce f.i. from xterm level just after only start X server using xinit command, the problem doesn't appear and the executing terminal command doesn't crach the X server, it runs normaly. Even without change the resoluton of screen. This issue didn't appear when I used Xfce 4.2.3.
Can you guys try the vte terminal (command: vte) and the gnome terminal (command: gnome-terminal), to see if this is caused by the vte widget.
If one of the apps above can reproduce the problem, you can report the problem to Gnome's vte component.
(In reply to comment #11)
> (In reply to comment #10)
> > That really looks like a bug in Xorg. What makes you think that the problem
> > lies in Xfce?
> I have this same problem - running terminal in Xfce crash the X server
> (Slackware 11.0, kernel v.2.6, Xface v 4.4.1) But if I run terminal without
> Xfce f.i. from xterm level just after only start X server using xinit command,
> the problem doesn't appear and the executing terminal command doesn't crach
> the X server, it runs normaly.
This doesn't prove anything. Xorg crashes *with* Xfce doesn't mean that it crashes *because of* Xfce. Xorg crashes, then it's a bug in Xorg unless proven different.
> Even without change the resoluton of screen. This
> issue didn't appear when I used Xfce 4.2.3.
Xfde 4.2 did not support ARGB32...
Just an idea, can you try with Cairo clock? It uses ARGB32 too.
I just compiled the following packages with debug support:
and I can't reproduce the Terminal crash any longer. Compiling them again without debug support still leaves the crash unreproducible.
I don't know what else has changed, maybe Xfce just needed to be compiled against xorg-server 1.3. But anyway, Terminal now works just as perfect for me under 1.3 as it did under 1.2.
(In reply to comment #14)
> Just an idea, can you try with Cairo clock? It uses ARGB32 too.
Cairo clock worked fine. I tried all the options.
Gnome Terminal works fine too.
(In reply to comment #16)
> (In reply to comment #14)
> > Just an idea, can you try with Cairo clock? It uses ARGB32 too.
> Cairo clock worked fine. I tried all the options.
If cairo clock works fine, then it tends to prove the bug () if any) is not in the compositor code at least :þ
Feisty i386 i810e
From other box I'm connecting over ssh and:
# /etc/init.d/gdm stop
- and here i'm wathing Xorg messages.
Then I'm running another ssh-client and in it:
- and here i'm wathing win-manager messages.
Then I'm running onother one ssh-client and in it:
# xfce4-terminal --display :0
- and here I'm reproducing bug !!
in xfce4-terminal - is nothing interesting.
in xfwm4 - is nothing interesting.
BUT in X - here we have Backtrace:
0: X(xf86SigHandler+0x81) [0x80c5d91]
2: X [0x815b8a4]
3: /usr/lib/xorg/modules/extensions//libextmod.so [0xb7c67c00]
4: X [0x8137a4f]
5: X(ChangeWindowAttributes+0xd35) [0x807b9a5]
6: X(ProcChangeWindowAttributes+0xa0) [0x808c2e0]
7: X [0x8142531]
8: X(Dispatch+0x19f) [0x808c61f]
9: X(main+0x495) [0x8074785]
10: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7d9aebc]
11: X(FontFileCompleteXLFD+0x1e1) [0x8073ab1]
And another one Backtrace for full xfce-session:
in second ssh-client:
# sh /etc/xdg/xfce4/xinitrc
0: X(xf86SigHandler+0x81) [0x80c5d91]
2: /usr/lib/xorg/modules//libxaa.so [0xb7b74fbd]
3: X [0x8109799]
4: X [0x815fea7]
5: X [0x815b0f0]
6: X(ValidateGC+0x25) [0x809a135]
7: X [0x816067c]
8: X [0x8160aaf]
9: X [0x815c211]
10: X(compPaintWindowBackground+0x6d) [0x80f614d]
11: X(miWindowExposures+0xfa) [0x8111a1a]
12: X [0x80daf7c]
13: X(miHandleValidateExposures+0x78) [0x8129388]
14: X(MapWindow+0x3aa) [0x8078fda]
15: X(ProcMapWindow+0x59) [0x808bf69]
16: X [0x8142531]
17: X(Dispatch+0x19f) [0x808c61f]
18: X(main+0x495) [0x8074785]
19: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7db4ebc]
20: X(FontFileCompleteXLFD+0x1e1) [0x8073ab1]
It seems to be bug in X signal handler - xf86SigHandler.
when i turn off 119_ubuntu_enable_composite.diff - patch
bug is off
So this is not a bug in Terminal then.
Created attachment 1576
funky terminal colors and layout
I just ran into probably the same thing with terminal.
With cirrus driver on kvm and qemu, X crashes.
gdm-binary: WARNING: gdm_slave_xioerror_handler: Critical X-Error - :0 restart
vesa driver doesn't crash, but makes terminal look "funky".
But only with qemu/kvm/virtualbox afaik. Seems to work on real boxes.
Both issues are fixed with "export XLIB_SKIP_ARGB_VISUALS=1" as pointed out by Brian in #8.
Still -- X crashing is, by definition, a bug in X or the video driver. If Terminal (or vte) is the "cause," it's still X's fault that it crashes.
Btw, your screenshot looks like a classic example of a video driver bug.
(In reply to comment #22)
> I just ran into probably the same thing with terminal.
> With cirrus driver on kvm and qemu, X crashes.
I tried Xorg 7.4, and with the cirrus driver under qemu it doesn't crash anymore, the composite extension is even working.