GNOME Bugzilla – Bug 122138
Weird GTK crasher in 1.1.20
Last modified: 2004-12-22 21:47:04 UTC
I found a way of making Gnumeric 1.1.20 crash every time it is started: - Open an Epiphany-1.0 window - Pull out your network cable - Type in a URL and wait for the "timed out" dialog; **leave the dialog open** - double-click on an XLS file, with Gnumeric associated to XLSs - Gnumeric will crash, and Bug Buddy can't get a backtrace from it - Plug the cable back in, close the Epiphany dialog, and hit refresh - Double-click on the XLS -- Gnumeric will open fine. Some weird GTK stuff going on here...
Put down the crack pipe. I don't even know where to start looking at this. I tried it on my laptop with xd2 epiphany but never saw any sort of network error dialog. Usually I'd call any crasher a critical bug, but since I can not replicate and there is no back trace, I'll ignore this as a _very_ unlikely confluence of events.
If you don't get the network error dialog, it doesn't cause the problem -- you need to either connect to a site that will give you a "connection refused" dialog, or try browsing to a website without the cable plugged in, and wait 30 seconds or so for the connection attempt to fail. Then leave the epiphany modal error dialog open, while you try to start Gnumeric. It works, honest!! :o)
I got a stacktrace, finally. I will mark it as a dup below. Here's a much more reliable way of getting the Epiphany dialog: disable your NIC, then bring up Epiphany with a remote homepage. (Then bring up Gnumeric -- you can actually run it from a terminal, i.e. without double-clicking on a file.) This is what I get on the terminal: $ gnumeric Bonobo accessibility support initialized GTK Accessibility Module initialized Atk Accessibilty bridge initialized ** ERROR **: error condition on server fd is 0 aborting... Bonobo accessibility support initialized GTK Accessibility Module initialized Atk Accessibilty bridge initialized I hope this is more informative than it looks! Reopening -- I hope you don't mind -- since I can finally provide more info.
Hmm, bugzilla hasn't come back with the backtrace report yet. Here's another bt, this time I upgraded to 1.1.90: Backtrace was generated from '/usr/bin/gnumeric' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 1089768720 (LWP 7450)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x4001544e in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 40153
Thread 1 (Thread 1089768720 (LWP 7450))
Interestingly, if another error dialog pops up, you can't click anywhere in the desktop (mouse clicks are disabled), but keyboard nav works. Maybe this is the wrong place to report this, but Gnumeric seems to be the only app to actually crash in this situation.
*** Bug 122217 has been marked as a duplicate of this bug. ***
Ahh, you have atk enabled. Which version of atk (and related packages) do you have installed?
In fact comparing your bt with the bt from 121675 indicates that it has nothing to do with epiphany and network etc but with atk.
*** This bug has been marked as a duplicate of 121675 ***
My lib versions are the latest xd2-unstable libs: atk-1.4.0-0.ximian.6.1 at-spi-1.3.6-0.ximian.6.1 gail-1.4.0-0.ximian.6.1 gnumeric-1.1.90-0.ximian.6.1
OK, I disabled ATK and logged back in -- it fixed the problem. Sorry for the trouble, Jody!