X crashes on RV370 with firefox + gnash visiting certain urls (no desktop effects)

I am using gutsy and I get the same error when I try to run gnome screensaver applet while having desktop effects preferences enabled.

Geforce 8600 GT drivers installed with envy

OK. So I am still getting seemingly random crashes. Again I am not running desktop effects. I think that may be a different and should be reported/added to accordingly.

Usually the crash happens when running firefox.

Also, it is not reproducible reliably. For example twice in a row when clicking on this link: http://krazydad.com/blog/ from this link: http://battellemedia.com/archives/003952.php in the comments section, i got the crash. But the third time i clicked on the link (yeah, you would think i would have learned) it didn't crash. So it is not completely reproducible.

So, I didn't know what the problem was so i decided to run a memory test (memtest). Which passed many many times with no errors. This also required a reboot, and just after booting it fresh today I got another crash. This time the crash happened when closing a tab in firefox.

I was trying to think about what I might have installed or any changes to the system. I remembered install the gnash mozilla plugin, so i just uninstalled that.

I will continue to report any finding or logs as I can think of them.

This occurred for me some time in the middle of last night (after I went to bed) on the latest gutsy. I had left some downloads open over night, and woke up this morning to find myself greeted the gdm login screen.

I am using compiz and the nvidia_new drivers. This is the first time I've noticed this problem since I got this machine (about a month and a half ago)

For me, I have uninstalled gnash. And since then I haven't seen a crash.

Do you have gnash installed? If not I think this two issues might not be the same issue.

No, this is on a i386 install, and I have the "real" flash installed.

I found out that this particular error is very generic and just means that the X server restarted for _some_ reason. That's why I attached the gdm log, which has an Xorg backtrace.

This happened to me three times today, running Gutsy (installed RC and all updates since then). I am running GNOME and Compiz-Fusion on an Intel GMA-950 with the intel driver.

I only had Firefox running in one session of the three, so this might be unrelated.

However, all three times it happened was when I was switching workspaces with Ctrl+Alt+arrows (Compiz Desk Wall plug-in). I have added the line "VideoRam 131072" to my xorg.conf Device section yesterday in hope of increased performance (like I did in Feisty). I haven't come accross this problem since the day Gutsy RC was released, so I removed that line and I will see if that was somehow related.

Removing the VideoRam line from xorg.conf did not solve the problem and the restart happened again just now.

I do not have gnash installed.

Same problem here. It even happened once in the live CD environment while only using firefox and trying to copy some files.
I am using Ubuntu Gutsy (release), nvidia binary drivers (restricted drivers), although in the live cd environment these where obviously not loaded, and it also happened there.

I think this bug should be confirmed and taken seriously. I am going back to Gutsy

I get randomly something similar. I'm running a fresh install of Gutsy on a NC6220 Laptop with all updates applied. I can't really reproduce it, sometimes X is just restarting out of a sudden. Today i got i twice, at first while running apt-get and firefox. 20 minutes later while searching in LP and crawling through the logs with gedit to get this bug. that really sucks, as you can see in my syslog ;).

Oct 28 09:57:19 Moon gdm[5209]: WARNING: gdm_slave_xioerror_handler: Schwerwiegender X-Fehler - :0 wird neu gestartet
Oct 28 09:57:36 Moon hcid[5161]: Default passkey agent (:1.32, /org/bluez/passkey) registered
Oct 28 09:57:36 Moon hcid[5161]: Default authorization agent (:1.32, /org/bluez/auth) registered
Oct 28 09:57:39 Moon NetworkManager: <info> Updating allowed wireless network lists.
Oct 28 10:17:01 Moon /USR/SBIN/CRON[9086]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Oct 28 10:19:59 Moon gdm[7419]: WARNING: gdm_slave_xioerror_handler: Schwerwiegender X-Fehler - :0 wird neu gestartet

I have an Intel 915GM and the "intel" driver running. During today's crashes Compiz was disabled.

We must get this Bug fixed or we can't work seriously with Gutsy. This is too unreliable.

My problems had always been in feisty, not gusty. Also, we can't expect that this type of bug will be fixed unless it is something that is reproducible in some way. I, for one, am not getting these crashes anymore, getting rid of gnash solved my problem. I would recommend that someone who is, should run the debug versions of the key packages and try to capture more output about and relating to the crashes. We would need something that is reproducible in order to fix either fix or give enough information to developers to fix it.

Can you tell me a bit more about running debug versions ?

Since upgrading to Gutsy, I'm suffering from +- daily freezes. Sometimes X crashes with the above error, sometimes everything freezes with blinking keyboard LEDs..
I'd like to isolate the problem somehow, I just don't know how. I find no pattern, my PC will run for days with no problems, then lock up 3 times in an hour. I already tried updating BIOS, I replaced my harddisk(s), it still happens, even using a live CD, no accelerated video drivers, never mind desktop effects. Same machine is perfectly stable under XP and Feisty.

FWIW, my hardware:
- Asrock Dual VSTA 775 with Core2 Duo (Via chipset)
- onboard Va VT6102 Rhine II nic
- 2GB DDR2
- various SATA and PATA harddisks and optical drive
- nVidia 7900GS (but Im ruling out drivers, as it has happened with VESA drivers)
- Logitech Revolution MX mouse (you never know :) )

It could be worth if you guys post your hardware specs, maybe we can find something in common?

Almost forgot, ALC883 onboard audio

I am not an expert on this, so others please jump in.. but there are dbg packages for many, if not all, open source applications. They have the same package name, but with -dbg at the end.

So for example:
xserver-xorg-core-dbg - Xorg - the X.Org X server (debugging symbols)

This may be helpful, specific to python, but should give you an idea about dbg packages. Seems like the basic idea is that they have been complied with debugging symbols enabled, which means that you can debug them easier with tools like gdb.
https://wiki.ubuntu.com/PyDbgBuilds?highlight=%28dbg%29

I am not having problems currently. My bug was software specific, the bug others have found may or may not be.

I am experiencing the same problem. X will crash randomly and i will be back at the gdm login screen. Sometimes this will not happen for days at a time, sometimes it happens while im away from the machine, and sometimes it will happen so rapidly that i will bomb back to gdm 3 or 4 times in 10 minutes. At times X will crash and throw me back to gdm while attempting to log back in from a crash, before i can even interact with my desktop. My gdm log is the same as the one posted above. There seem to be many bugs posted descibing similar errors but attributing them to specific apps, but i just reinstalled fresh gutsy and i see no change in the problem over when i was using accelerated nvidia, gnash, and compiz. The only seemingly related item is that firefox crashes a lot with the error message "core dumped" -- it even crashed on the live cd.

asus p5n-e sli
core 2 duo 6450
4gb ram
single 500gb sata drive
geforce 7900gs

I have similar problems.

When a second user logins, played with it and logs of, my first session is logged of, and I get back at a clean GDM screen. The strange thing is that it doesn't seem to happen always. User1 has 3D effects enabled.

In the error logs this message appears: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0

My System:
Macbook, with Intel GMA 950, Gutsy

it just starting going that after I some how fixed my pc from locking up ever since i upgraded to 7.10 x64

Nov 18 01:36:30 AMD64 kernel: [10216.881103] Bad page state in process 'wcg_hpf2_rosett'
Nov 18 01:36:31 AMD64 kernel: [10216.881105] page:ffff810000c82350 flags:0x010000000000001c mapping:ffff810016572110 mapcount:0 count:0
Nov 18 01:36:31 AMD64 kernel: [10216.881108] Trying to fix it up, but a reboot is needed
Nov 18 01:36:31 AMD64 kernel: [10216.881109] Backtrace:
Nov 18 01:36:31 AMD64 kernel: [10216.881114]
Nov 18 01:36:31 AMD64 kernel: [10216.881115] Call Trace:
Nov 18 01:36:31 AMD64 kernel: [10216.881133] [bad_page+96/160] bad_page+0x60/0xa0
Nov 18 01:36:31 AMD64 kernel: [10216.881140] [free_hot_cold_page+337/352] free_hot_cold_page+0x151/0x160
Nov 18 01:36:31 AMD64 kernel: [10216.881147] [unmap_vmas+1578/1984] unmap_vmas+0x62a/0x7c0
Nov 18 01:36:31 AMD64 kernel: [10216.881166] [unmap_region+204/368] unmap_region+0xcc/0x170
Nov 18 01:36:31 AMD64 kernel: [10216.881175] [do_munmap+554/752] do_munmap+0x22a/0x2f0
Nov 18 01:36:31 AMD64 kernel: [10216.881181] [__down_write_nested+18/176] __down_write_nested+0x12/0xb0
Nov 18 01:36:31 AMD64 kernel: [10216.881189] [sys_munmap+77/128] sys_munmap+0x4d/0x80
Nov 18 01:36:31 AMD64 kernel: [10216.881197] [ia32_sysret+0/10] ia32_sysret+0x0/0xa
Nov 18 01:36:31 AMD64 kernel: [10216.881206]
Nov 18 07:36:25 AMD64 kernel: [22738.730441] audit(1195389384.877:4): type=1502 operation="inode_create" requested_mask="w" denied_mask="w" name="/var/run/samba/namelist.debug" pid=5732 profile="/usr/sbin/nmbd"
Nov 18 08:02:16 AMD64 kernel: [23749.365812] VM: killing process Xorg
Nov 18 08:02:16 AMD64 kernel: [23749.366673] swap_free: Unused swap offset entry 00010a0e

the same problem random affect my computer ,which fresh installed gutsy，for a long time.
it is as noticed above, not reproducible reliably. and it is mostly relate the open and close of firefox, the switch between workspaces.

on my computer:
nvidia6200 with nvidia-glx-new
even though compiz-fusion is closed

i wish this problem should be recognized as a bug and fixed soon

Same problem for me, but with a twist.

I get

gdm_slave_xioerror_handler: Fatal X error - Restarting :0

as the only message in syslog. It happens at night a few hours after I stop using the machine, but only on nights when I leave firefox running. The machine is a brand new Dell XPS M1330 with an external monitor connected running the binary nvidia drivers and ubuntu 7.10. My best guess is that it is the crash_x_and_die counter in firefox that reaches zero.

hi there,
could anyone who suffers from "this" bug please attach their Xorg.0.log, cause it has more information on the x crash. syslog only tells that there is a x crash ...

this way we maybe can get to the reasons for the x server behaving badly. in my case i always get this backtrace in Xorg.0.log.old:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c9581]
1: [0xffffe420]
2: /usr/bin/X(xf86_reload_cursors+0x70) [0x80fbd60]
3: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb7c26022]
4: /usr/bin/X(xf86CrtcSetMode+0x279) [0x80faf49]
5: /usr/lib/xorg/modules/drivers//intel_drv.so(i830GetLoadDetectPipe+0x151) [0xb7c265e1]
6: /usr/lib/xorg/modules/drivers//intel_drv.so [0xb7c22219]
7: /usr/bin/X(xf86ProbeOutputModes+0x188) [0x80f8f48]
8: /usr/bin/X [0x80feb01]
9: /usr/bin/X(RRGetInfo+0x89) [0x8170619]
10: /usr/bin/X(ProcRRGetScreenSizeRange+0x8a) [0x817415a]
11: /usr/bin/X [0x816dc95]
12: /usr/bin/X [0x815754e]
13: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
14: /usr/bin/X(main+0x495) [0x8076f05]
15: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7dee050]
16: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

but i don't know how to interpret this backtrace correctly, so can someone help me out?

Got this problem today with an Intel 945GM and running Hardy, is there any workaround for it?

I have been experiencing this error as well.
My System Ubuntu 7.10 I386 ATI X850PRO , AMD ATHLON 2500+ XP, 1gb DDR PC2700 RAM.
It occurs when using firefox and either clicking a link or opening a link in a new tab. I have had it happen to me 5 times now.
Not 5 times in a row of course but on and off since the month of November and the second firefox update that Gutsy did.

tayhe,

I think it is unwise to dup evey X-crash bug onto this particular one. This is a very generic problem, an X server crash will kill GDM.

At least one of the bugs you dup'd onto this should be the root bug for the "cursors" crash. I've not seen any cases of similar backtraces appear for the non-intel driver, and those bugs were specifically assigned to the intel driver package. Marking them as dup's of this may make it less likely that people fixing bugs in the intel driver will get to them.

Anyone with the cursors crash should track / add additional information to Bug #153466

Could those able to reproduce this on Hardy please see https://wiki.ubuntu.com/X/Debugging (under "X crash, lockup, freeze, exit, or doesn't start/shutdown") and attach the requested log files? Thanks. Tracking bug for Hardy.

Howto reproduce:

Log in userA: swithc users and log in userB.
userB log out => come in the locked screen dialog. Strange side effect (but maybe doesn't have to do with this): sometimes I can't use my mouse to click on a button here, I have to use the keyboard.
Anyway in the lock screen dialog switch users again. login userB. logout userB => X crash.

It seems to happen nearly always (the time it didn't happen after 2 login/logout sessions I did this:
login userA: switch user and login userB. Logout userB, unlock screen of userA. switch users, login to userB. logout userB (nothing weird happened), swithc users in the lock screen of userA, loging userB, logout userA => same crash.)

nathan@gamma:~$ cat /proc/acpi/video/*/DOS
DOS setting: <4>
nathan@gamma:~$

The attachment is the output of sudo cat /proc/acpi/dsdt

As for me, my nvidia geforce 6200 A-LE does not install properly in ubuntu 7.10 using nvidia version 100.14.19. So decided to revert back to ubuntu 7.04, updated everything in ubuntu first, then installed the nvidia driver and it installs properly but it was still crashing randomly. Then nvidia came with a new release of the nvidia driver (version 169.07), installed it, but X is still crashing randomly (last time it crashed, was not doing anything on firefox, was downloading in the background, listening to music and chatting, then it gave me the login screen again with music still playing though, but as soon as you relogin, playback stopped). Am attaching my Xorg.0.log

here is my Xorg.0.log.old

I've read in a mailing list that the problem might be related to the CPU cooling (see http://people.debian.org/~terpstra/message/20071130.161708.b95eae51.de.html#debian-user-german). In my case it's been true. Is anyone able to confirm it?

Does the problem also occur when you're not using any desktop effects like disabling compiz?

If this doesn't change anything it's probably most likely that the error has been caused by the GDM or are there any reports that the error also occurs on KDE? There are two possibilites; The first one is to use the kDM instead of the GDM (that's the login manager of KDE). And the second one would be not to rely on using any login manager. Therefore we could use rungetty which allows you to login directly.

I am not using any desktop effects at all, I checked and desktop effects are disabled. I do not have KDE installed so I don't know if the same issue happens in KDE.

This is happening on my computer to with the error: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0

Attached is my full xorg log, and syslog which has the error.

In addition to above, this happens when firefox is open and doing something (ex flash).

Yes, when there is some flash playing from within firefox, i noticed that CPU usage shoots even up to 115%, I do not have enough technical expertise to know if at all firefox is related to the X server crashing. Anybody knows if downgrading firefox to a previous version will help? Or downgrading to a previous version of the X windowing system?

I've had those x crashes while using firefox (most of the time), Digitale Bibliothek (with wine), TexMaker and so on. Disabling desktop effects doesn't help. I'm using an AMD with an Ati shared card.

I've had the problem for the first time on my laptop. It occured three times (!) always when I tried to minimize Mozilla Firefox.

I've found this most often caused in Firefox during opacity/alpha transitions. For example, the crossfading 'latest features' javascript on the Shacknews frontpage hangs my machine upteen times each week - but only as the transition starts and is on-screen (scrolling down to hide it avoids the hang). This is quite repeatable reboot-after-reboot on my system.

Similarly, pages with alpha-tested PNGs or stupid javascript popups cause the exact same crash.

(Unfortunately these hangs are so severe I almost never get any output to the logs - the system crashes before it can even write anything. Only once or twice have I managed to get enough output to confirm it's the same issue. This has been happening ever since I upgraded from 7.04 to 7.10, using nVidia binary drivers, both with and without Compiz Fusion.)

Today, just before the X session crashed again, I got the following message (don't know if this is at all related to this discussion here, but I will type it in anyway):

Nautilus can't be used now, due to an unexpected error from Bonobo when attempting to locate the factory.Killing bonobo-activation-server and restarting Nautilus may help fix the problem.

Right after i clicked on the OK button for that message, the X server crashed, logged in but there were no icons and no menu so I had to do a hard reset.

I've using the xserver-xorg-video-intel 2:2.2.0+git20080107-1ubuntu1 and haven't had the problem again, can someone else confirm? thanks.

I got these errors every now and then, once in four, five days or so but it varies enormously. Also using firefox when the system crashes. The file I attached does have a statement about font stuff (concerning Xorg probably?) The /var/log/gdm/:0.log.1 file also mentions this backtrace (identical).

The syslog gives me

Jan 15 18:31:54 desktop gdm[5432]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0

So, it would seem that it could have something to do with fonts? I mean, firefox is probably rendering its fonts using the Xserver? (dont know I am no developer :)) I have no other users installed so I cannot confirm these crashes by logging in as another regular user.

System specs:
Using Ubuntu Gutsy Gibbon 7.10 with much joy and freedom without any problems except this one :)
AMD Athlon XP 2100+
1 GB RAM
NVidia Ti4600/64 mb or so?
compiz fusion enabled
Soundblaster live 5.1, onboard sound disabled
usb 2.0 pci extension card
logitech wireless mouse+kb

i'm using an EVGA e-GForce 6200 A-LE graphics card, installed the latest nvidia drivers(169.09) and the gdm is still crashing and logging me off again. I use ubuntu 7.04 with all updates applied and I still notice that gdm crashes when firefox is open, the crash seems random as mentioned above (no crashes yesterday but three crashes already today and that is why am adding this comment)... it is becoming irritating...

i can confirm that this crash happens for me.

i have a workaround that "works for me"

1. disable starting gdm in the /etc/rcX.d/ scripts
2. reboot
3. computer will start in text-mode
4. login as your user
5. after login, start X via the startx command

this starts X and gnome but without gdm.

for me this error happend when i was away from my computer so i am assuming when the screen saver starts.

without gdm running, i can confirm that i left my computer and X didnt crash.

Still an issue with latest intel driver.

I am sorry to crosspost this message (which I posted in https://bugs.launchpad.net/bugs/165093 but now I look back, I think it is better in this bug ID...)

---
I am experiencing this bug more and more lately, twice today. I have seen an xorg update a few weeks ago, maybe that would be the reason? I am using nvidia TI4600, Compiz fusion and ubuntu gutsy gibbon on AMD Athlon XP2100+ w/ 1G ram. The crash of the x server is experienced when clicking in firefox on a link, and the system crashes before the link is actually opened (after logging in again, and starting firefox with 'resume session', the old page is displayed, not the page of which I clicked the link).

Similar bug as https://bugs.launchpad.net/bugs/140554 in which I posted a similar bug report a few weeks ago (found this thread by searching for the actual error of xorg/X FontFileComplete...., but the main error message in my syslog would be "gdm_slave_xioerror_handler: Fatal X error - Restarting :0"

Could it be firefox?
Could it be flash?
Could it be a bug in Xorg?
Someone tried another browser?
----
Here's a printout of the latter part of /var/log/gdm/:0.log.1

(==) Using config file: "/etc/X11/xorg.conf"
(II) Module already built-in
SetClientVersion: 0 9
nvClipLock: client timed out, taking the lock

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c95d1]
1: [0xffffe420]
2: [0xbffdefe8]
3: /usr/bin/X [0x817ed0c]
4: /usr/bin/X(FreePicture+0x78) [0x8161a18]
5: /usr/bin/X(FreeResource+0x11d) [0x80789fd]
6: /usr/bin/X [0x816960a]
7: /usr/bin/X [0x8164425]
8: /usr/bin/X [0x815765e]
9: /usr/bin/X(Dispatch+0x1aa) [0x808f47a]
10: /usr/bin/X(main+0x495) [0x8076f05]
11: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d08050]
12: /usr/bin/X(FontFileCompleteXLFD+0x1e1) [0x8076241]

Fatal server error:
Caught signal 11. Server aborting

5I can point out that it all started when Ubuntu decided to push the current version of firefox, before firefox version 2.0.0.11, i did not have this problem at all. It could also be related to something else but I don't know. Did somebody test with the previous version of firefox (but applying all the rest of the Ubuntu 7.04 updates, for example)? As for me, stopping gdm and running startx gives the same issues, it crashes as well but gives me the command line interface to retype startx again... I would love to be able to backtrack my firefox to the previous version, but i can't seem to get the previous version anywhere on the Internet.

did you look for older versions here: http://mirrors.kernel.org/ubuntu/pool/main/f/firefox/ ?
(insert a mirror closer to you as needed)

ubuntu released some updates for firefox related to crashing issues, let's see if those firefox updates resolve the issue here.

Il giorno sab, 09/02/2008 alle 22.34 +0000, Gilbert ha scritto:
> ubuntu released some updates for firefox related to crashing issues,
> let's see if those firefox updates resolve the issue here.
>
Well, apparently not... Yesterday, after upgrading firefox, I was bitten
by the bug 4 times in a row. Two times while using the deskbar applet
for doing a web search while trying to minimize the firefox window.
Later, when I'm done doing a couple of things, I'll try to reproduce it.
This is a really annoying bug, and difficult to catch too...

--
Leo'TheHobbit' Cacciari

Hey guys, "gdm_slave_xioerror_handler: Fatal X error - Restarting :0" is a generic error message (like "out of memory" or "syntax error") and can be caused by a myriad of different things. Indeed, it's quite likely each of your issues is due to a separate, unrelated problem (especially given how some people resolved it by not using software A, others notice it with software B, etc.) The underlying problem might be a bug in a driver, or it could be due to a software program doing something unexpected to X.

In any case, X crashes are straightforward (if a bit of work) to debug. There is a fairly good document describing the steps to take here, which I would strongly encourage going through: https://wiki.ubuntu.com/DebuggingXorg

Obviously, being able to recreate the problem is half the battle. "X crashes randomly" are quite tough to deal with. But a technique is to install all the relevant dbg packages, and then ssh into your system from a second machine, and run Xorg from within gdb, and then go about your business. When a crash does occur, go to the 2nd machine and use the directions above to get a full backtrace. (Note that if the system locks so badly that you can't do this, then you may have a kernel issue.) If you've not used gdb before, it may seem a bit daunting at first, but there's only a few steps you need to do, and it's a skill you can reuse when you run into other software that crashes.

The good news is, once you have a full backtrace with proper debug symbols, we can forward these bugs upstream almost immediately.

In addition, since I suspect that everyone's error is independent, when you do this please file a new bug report. In addition to the backtrace, include the usual files (Xorg.0.log, xorg.conf, and the output of lspci -vvnn).

I am going to retitle and refocus this bug report to only the original reporter's issue.

Todd, so it sounds like the issue for you was with gnash triggering a fatal X error on those pages. Would you mind testing against Hardy, which has a newer firefox (and maybe gnash too)?

Henrik: the specific original reported issue (X crash triggered by gnash) has not been confirmed as seen since Feisty. I also double-checked the gnash bug trackers and see there is no mention of X crashes other than this one. In reviewing all the commenters on this bug, they seem to all be experiencing unrelated issues; the bug was titled using a generic error message so I suspect Launchpad was incorrectly pointing them here.

I'm moving it back to incomplete for now - we need confirmation that the gnash-crashes-X issue still occurs on Hardy. If it does, I'll leave it to your judgement as to whether it is critical enough to warrant a distro task, however I suspect the issue would need to be investigated by gnash developers.

I believe I have the same (or a related) bug, although I don't have gnash installed.
Running Hardy Heron, with the latest updates.
Seems to happen when there are a lot of things happening on the display, for instance when minimizing firefox (as others have said), or when a notification window pops up over one of the task bars).
Screen goes totally black, perhaps with a backlight flicker (you know how there is a difference between an LCD which is "off" and one "displaying a black screen"?). Display doesn't recover. The only keyboard shortcut I can get to generate a response is to tap Ctrl-Alt-Del twice, which will reboot the system.

Hardy Heron, 8.04
uname -r: 2.6.24-8-386
Video: Intel 915GM, using "intel" driver
Firefox 3.0b3, although I think this was happening prior to upgrading to Firefox 3

I've looked through the kernel and Xorg logs, but it's hard to tell where exactly the crash is happening. I've attached my Xorg.0.log.old anyhow.

jwinget, can you follow the directions on https://wiki.ubuntu.com/DebuggingXorg to get a full backtrace on this issue?

(I suspect your issue might be unrelated to the original bug, but if you can get a full backtrace, I could investigate it.)

Yes, I will do it ASAP. Thanks.

I have have also had this problem for a while. If I remember right crashes started about a week after the last kernel update. I don't remember if I installed/updated something after that. I have crashes about every other day and they seem to happen randomly (last time when I was typing in terminal and before that when opening link in firefox) though firefox2 is always running at least in different workspace. I decided to test if crashes occur also in KDE, but unfortunately it also crashed. I have two monitors and I am using them in DualView with latest nvidia drivers (GF7800gs) from restricted driver manager (100.14.19), but also tested with older drivers using envy, without success. I use adobe's flash-plugin, but realized just a while ago that I had also gnash installed and removed it immediately... I'll see if it crashes if I switch to ff3 or opera.

Dropping the release task as per my comment #60. We do not have confirmation that the gnash crash still exists in hardy. Feel free to re-open if anyone can confirm the gnash bug is still present in Hardy or newer. (And please be aware that unrelated bugs also generate similar-sounding error messages, so doublecheck there.)

The same thing with me. When I start Amarok I see after 5 sec the LogOn Screen. Also same Log

Mar 25 21:37:22 test gdm[5221]: WARNING: gdm_slave_xioerror_handler: Schwerwiegender X-Fehler - :0 wird neu gestartet
Mar 25 21:37:26 test gdm[9595]: WARNING: gdm_slave_xioerror_handler: Schwerwiegender X-Fehler - :0 wird neu gestartet

PLEAASEE FIX THAT BUG!!! I think it is very important to do this!!

Hello,
for me this bug is easily reproducible on my laptop, when using firefox 3.0b5 and java applets.
I have an Intel 915GM card (using intel driver), and i'm using compiz 0.7.4
When I connect to my vnc server (through a java viewer using http port and firefox), xorg always crashes.

Only workaround that seems to work for the moment, is to disable "correction of java windows" under "solutions" in the "Advanced desktop effects settings" tool for compiz.

Sorry, I don't know if I should open a new bugreport, or if it related to intel + compiz + firefox + xorg combinaison.
But the logs are the same for me as reported by others :

Apr 28 23:37:34 phoenix-5 gdm[12693]: WARNING: gdm_slave_xioerror_handler : erreur X fatale - Redémarrage de :0
Apr 28 23:37:56 phoenix-5 hcid[5830]: Default passkey agent (:1.118, /org/bluez/passkey) registered
Apr 28 23:37:56 phoenix-5 hcid[5830]: Default authorization agent (:1.118, /org/bluez/auth) registered
Apr 28 23:37:57 phoenix-5 NetworkManager: <info> Updating allowed wireless network lists.
Apr 28 23:37:57 phoenix-5 NetworkManager: <WARN> nm_dbus_get_networks_cb(): error received: org.freedesktop.NetworkManagerInfo.NoNetworks - There are no wireless networks stored..

Thank you for your help :)

@titi4u, "gdm_slave_xioerror_handler: Fatal X error - Restarting :0" is a generic error message, it just means "X crashed for some reason". So you probably are not seeing this specific bug. You should report it as a new bug, and please refer to wiki.ubuntu.com/X/Reporting for tips on what information to include in your bug report.

@Ubuntufan94, same thing for you, although you've not given enough information about your crash to really know if it's this bug or a new one, but I suspect it's probably new since the original bug did not get triggered by Amarok.

ok, thank you for your suggestion, Bryce !
I've opened bug 224798 and attached all necessary files.
First I thought that disabling some options in compiz would help X not to crash, but I was wrong.
Hope with bug will be fixed soon ...

For me this bug is easily reproduced.

I have IBM X41 sub-notebook.
Closing and then opening the lid triggers this bug immediately.

Hardy Heron, latest updates, intel integrated card.

(II) Open ACPI successful (/var/run/acpid.socket)
(II) AIGLX: Resuming AIGLX clients after VT switch
(II) I810(0): Detected resume, re-POSTing.
(WW) I810(0): Bad V_BIOS checksum
(II) I810(0): Primary V_BIOS segment is: 0xc000

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x7e) [0x80c780e]
1: [0xb7faa420]
2: /usr/lib/xorg/modules//libint10.so(Mem_rb+0x29) [0xb7b15899]
3: /usr/lib/xorg/modules//libint10.so(fetch_data_byte+0x2f) [0xb7b188af]
4: /usr/lib/xorg/modules//libint10.so [0xb7b1aa38]
5: /usr/lib/xorg/modules//libint10.so(X86EMU_exec+0xa3) [0xb7b2b0f3]
6: /usr/lib/xorg/modules//libint10.so(xf86ExecX86int10+0x55) [0xb7b17955]
7: /usr/lib/xorg/modules/drivers//i810_drv.so [0xb7b658f9]
8: /usr/lib/xorg/modules//libxaa.so [0xb78c58eb]
9: /usr/bin/X [0x80cec6c]
10: /usr/bin/X [0x80dbb38]
11: /usr/lib/xorg/modules/extensions//libglx.so [0xb7c0bc4a]
12: /usr/bin/X(xf86Wakeup+0x3bf) [0x80c84bf]
13: /usr/bin/X(WakeupHandler+0x59) [0x8091719]
14: /usr/bin/X(WaitForSomething+0x1e2) [0x81b1d22]
15: /usr/bin/X(Dispatch+0x8d) [0x808d69d]
16: /usr/bin/X(main+0x48b) [0x807471b]
17: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7d3a450]
18: /usr/bin/X(FontFileCompleteXLFD+0x201) [0x8073a91]

Fatal server error:
Caught signal 11. Server aborting

Ummm

May 21 00:16:11 slime-laptop gdm[8568]: pam_unix(gdm:session): session closed for user slime
May 21 00:16:11 slime-laptop gdm[8568]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0

only errors at that time. :/

Not 100% shure can this be related, but It might pinpoint problem. It has happened 4 times today, with last 3 I was able to pinpoint down the problem. After rebooting I opened old session of firefox, and every single time I try resize window which has heavy Java applet in it, it restared, and in log it said the fatal x error. I am running nVidia graphics with ADM cpu. And firefox was only program opened at that point.

That all I could pinpoint it down, I had some flash aps running in different firefox window as well.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

emis815 wrote:
| Ummm
|
| May 21 00:16:11 slime-laptop gdm[8568]: pam_unix(gdm:session): session
closed for user slime
| May 21 00:16:11 slime-laptop gdm[8568]: WARNING:
gdm_slave_xioerror_handler: Fatal X error - Restarting :0
|
| only errors at that time. :/
|
| Not 100% shure can this be related, but It might pinpoint problem. It
| has happened 4 times today, with last 3 I was able to pinpoint down the
| problem. After rebooting I opened old session of firefox, and every
| single time I try resize window which has heavy Java applet in it, it
| restared, and in log it said the fatal x error. I am running nVidia
| graphics with ADM cpu. And firefox was only program opened at that
| point.
|
| That all I could pinpoint it down, I had some flash aps running in
| different firefox window as well.
|
Bryce, The Nvidia cards look to be a dup of bug #212648 but i have seen
this issue reported with ATI drivers but Wile talking to Timo sounds
like the ATI was cause by the drivers.

Everyone using nvidia card 8xxx series with the latest nvidia drivers
from Ubuntu repos please take a look at the above bug to see if that is
your issue. This bug looks like it has serveral different bugs on it and
would like to weed them out if possible.

- --
Sincerely Yours,
~ John Vivirito

https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFINPUuqig4QTwcPCoRAlIMAJwPUMqehFSg7auF+H8alR/GRJeZZACfZJZ9
vS/gzHOVdfe8zu7bzzHmj1U=
=J0aS
-----END PGP SIGNATURE-----

I have been experiencing this problem as well. It's nasty as I have lost work-in-progress because of it.
My setup is Ubuntu 8.04 with Compiz. I always have Firefox running (3.0.3 right now). The two cents I can add at the moment are that twice I have experienced this problem when I clicked on the edge of the "minimize" button on the titlebar in Firefox. Another other time was after have tabbed over from a full screen app and hit the "X" button on the titlebar. Two two described crashed occured just a few minutes apart. Here is a relavent section of /var/log/syslog:

Oct 14 14:39:01 aries /USR/SBIN/CRON[32483]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/p
hp5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -r -0 rm)
Oct 14 14:39:36 aries ntpd[4581]: synchronized to 213.222.193.35, stratum 1
Oct 14 14:46:41 aries gdm[11148]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Oct 14 14:46:54 aries pulseaudio[32758]: pid.c: Stale PID file, overwriting.
Oct 14 14:46:54 aries pulseaudio[32758]: alsa-util.c: Device front:0 doesn't support 44100 Hz, changed to 4800
0 Hz.
Oct 14 14:46:54 aries pulseaudio[32758]: alsa-util.c: Device front:0 doesn't support 44100 Hz, changed to 4800
0 Hz.
Oct 14 14:46:56 aries hcid[11084]: Default passkey agent (:1.80, /org/bluez/passkey) registered
Oct 14 14:46:56 aries hcid[11084]: Default authorization agent (:1.80, /org/bluez/auth) registered
Oct 14 14:46:58 aries NetworkManager: <info> Updating allowed wireless network lists.
Oct 14 14:46:58 aries NetworkManager: <WARN> nm_dbus_get_networks_cb(): error received: org.freedesktop.Netwo
rkManagerInfo.NoNetworks - There are no wireless networks stored..
Oct 14 14:47:07 aries ntpd[4581]: synchronized to 193.2.4.2, stratum 1
Oct 14 14:47:47 aries ntpd[4581]: synchronized to 213.222.193.35, stratum 1
Oct 14 14:54:49 aries ntpd[4581]: synchronized to 193.79.237.14, stratum 1
Oct 14 14:56:24 aries ntpd[4581]: synchronized to 193.2.4.2, stratum 1
Oct 14 15:00:59 aries gdm[32609]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Oct 14 15:01:09 aries pulseaudio[1078]: pid.c: Stale PID file, overwriting.
Oct 14 15:01:09 aries pulseaudio[1078]: alsa-util.c: Device front:0 doesn't support 44100 Hz, changed to 48000
 Hz.
Oct 14 15:01:09 aries pulseaudio[1078]: alsa-util.c: Device front:0 doesn't support 44100 Hz, changed to 48000
 Hz.
Oct 14 15:01:10 aries hcid[11084]: Default passkey agent (:1.106, /org/bluez/passkey) registered
Oct 14 15:01:10 aries hcid[11084]: Default authorization agent (:1.106, /org/bluez/auth) registered

I'll write more when I get the chance. I just wanted to jot this down before I forget.

I forgot to mention that I do not have gnash installed.

Same here! In addition, I get the same error when starting X via startx, not using gdm or any other login manager! I'm using ion as window manager. In Xorg.0.log I found the following error message:

Backtrace:
0: /usr/bin/X11/X(xf86SigHandler+0x79) [0x80c3009]
1: [0xffffe420]
2: [0xffffe420]
3: /usr/bin/X11/X(ProcGetImage+0x5d1) [0x808a7d1]
4: /usr/bin/X11/X(Dispatch+0x34f) [0x808c89f]
5: /usr/bin/X11/X(main+0x47d) [0x8071d1d]
6: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7bf4685]
7: /usr/bin/X11/X [0x8071101]
Saw signal 11. Server aborting.
(II) Video Bus: Close
(II) UnloadModule: "evdev"
(II) TPPS/2 IBM TrackPoint: Close
(II) UnloadModule: "evdev"
(II) AT Translated Set 2 keyboard: Close
(II) UnloadModule: "evdev"
(II) Logitech Optical USB Mouse: Close
(II) UnloadModule: "evdev"
(II) AIGLX: Suspending AIGLX clients for VT switch
(II) RADEON(0): RADEONRestoreMemMapRegisters() :
(II) RADEON(0): MC_FB_LOCATION : 0xffff0000 0xe3ffe000
(II) RADEON(0): MC_AGP_LOCATION : 0x003fffc0
finished PLL2
Entering Restore TV
Restore TV PLL
Restore TVHV
Restore TV Restarts
Restore Timing Tables
Restore TV standard
Leaving Restore TV

I'm working on a ibm Thinkpad x31 with an ATI Radeon M6 (radeon driver). Th error occured the first time after upgrading to Intrepid.

I forgot to mention that my xserver crashes mostly when I'm browsing with Opera (9.62). Same with firefox and thunderbird.

the same error, with identical descriptions also here...
Bug #412113

Is this still an issue for you? What Ubuntu version do you use? Thank you for telling us!

Thanks for your e-mail.

I do not use this ubuntu version any more.

Best regards
Hannes Pahlke

On Mon, 03 Dec 2012 11:42:17 -0000
Thomas Hotz <email address hidden> wrote:

> Is this still an issue for you? What Ubuntu version do you use? Thank
> you for telling us!
>
> ** Changed in: gnash (Ubuntu Hardy)
> Status: New => Invalid
>
> ** Changed in: gnash (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (178444).
> https://bugs.launchpad.net/bugs/140554
>
> Title:
> X crashes on RV370 with firefox + gnash visiting certain urls (no
> desktop effects)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnash/+bug/140554/+subscriptions

--
Hannes Pahlke <email address hidden>

Arminstraße 37, 64625 Bensheim,
Tel. 06251-580318

[Expired for gnash (Ubuntu) because there has been no activity for 60 days.]