Whole gnome session crashes when click on a link in epiphany

Thanks for your bug. No such issue on my edgy installation but I doubt that's a gnome-session bug, maybe you could try from an another environment with the same browser? Do you have anything to ~/.xsession-errors or /var/log/messages or /var/log/syslog about that?

Sorry, it's the second console.log file ;) I've just downloaded that file (http://test.kernel.org/abat/42770/debug/console.log) with wget, to /tmp. If I try open file with gedit /tmp/console.log, guess what? Gnome crashes again ... So it's not epiphany related it seems. /var/log/messages and syslog does not contain any important I guess you would have tried to interpret this as some kind of kernel bug? No, there is no other message than netfilter log since the boot.

Additional information: I found this message:

*** glibc detected *** free(): invalid next size (normal): 0x0000000000c474d0 ***

on virtual console 7.

.xsession-errors is attached

Btw, as I've said it's Ubuntu Dapper 6.06, AMD64 and not edgy. I've just tried to gdb gedit when opening file from a virtual screen created by screen but got:

(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 1074006368 (LWP 6235)]
(no debugging symbols found)
[New Thread 1082399072 (LWP 6236)]
[Thread 1082399072 (LWP 6236) exited]
[New Thread 1082399072 (LWP 6237)]
[Thread 1082399072 (LWP 6237) exited]
gedit: Fatal IO error 104 (Connection reset by peer) on X server :0.0.

Program exited with code 01.
(gdb) bt
No stack.

The interesting part for me why crashing a gnome app (like gedit or epiphany casue to crash whole gnome).

I would rather they than xorg goes away, maybe you could try from a small environment like xfce or wmaker to note if they crash the same way?

Just tried with both of KDE and icewm session selected at GDM, gedit /tmp/console.log from terminal window result in crash again, returning to GDM. I've tried to strace gedit but I can't see any usefull information. But I've attached the file maybe it helps.

Maybe it's an X bug which is triggered by GTK/gnome apps (for example my /tmp/console.log file contains something which when rendered for the display)? Just because at least epiphany and gedit can triggers it, and KDE, gnome, icewm does not matter (so it does not look like a gnome-session problem for me, but maybe I'm wrong). Also please note that glibc warning about free() I've written about before.

not a gnome-session issue, might be that opening it asks for too much ressources and linux decide to close xorg then?

Dunno, but it seems quite dangerous for me to having files cause crash the whole desktop of a user when clicking on it eg on a homepage presented as a link ... Like for me when reading about automated Linux kernel testing and click on that link (while I had got several running terminal, applications etc). So you can inmagine :) These console.log files aren't so big in size so I can't understand what is the problem. I thing some point before the kernel (X server, gtk, gnome or whatever) should deny requests cannot be served at deeper level then. Sure, it cannot be handled so properly, but since this kind of issues are quite rare (according my practice at least) something can be and should be done here. Errr, sorry, I wouldn't use bug tracker as a blog, though :)

This is the last 1000 lines of strace'ing X. Donnu it's usefull or not.

 unsubscribe ubuntu-security

Please help! This bugs turns into a very serious one! Serious enough to disturb my daily work on my Ubuntu box. Now, it's on another machine: it's an i386 based P4 32 bit system and AMD64, but it's also Ubuntu 6.06 dapper. I'm using this box at my workplace to some web development. Today I would like to view the source of a web page (epiphany: view -> page source), which result in the same crash I've described above, and quite large amount of my work lost. I've saved the file I'm talking about (attached to this comment) into /tmp/index. If I want to open it with gedit, the same crash occur.

Please note that this bug occured with more applications, and on different architectures (x86 and x86_64) ... What can I do now?

The only common between the two machines that I'm using dapper-backports and dapper-updates repositories as well to dist-upgrade. Can this cause problems?

Thanks. Thanks in advance.

Do you still get that bug?

I'm using feisty since then, I can't reproduce this bug at least. On my AMD64 desktop machine, it does load, on x86 notebook it saturates the CPU usage at 100%, however no crash just very slow.

Assigning to nautilus, was on Ubuntu.
Because of:
---
(gnome-panel:5523): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `dest_width > 0' failed
seahorse nautilus module initialized
Initializing nautilus-open-terminal extension
Window manager warning: Lost connection to the display ':0.0';
most likely the X server was shut down or you killed/destroyed
the window manager.
---
Seems X was closed just after 'Initializing nautilus-open-terminal extension'.
Not sure it is related, but looks better than keeping it on Ubuntu.

The crash seems to be fixed on feisty for the submitter, closing. Feel free to reopen if you get the bug again though