Clicking on Codes of Conduct link in Launchpad crashes X

Using Firefox, the system completely hung! I know for a fact a great deal of the Brazilian Translators are experiencing the same problem. Don't know what other piece of relevant info I can provide.

And here's the link: https://launchpad.net/people/omaciel/+codesofconduct

Sorry for the 4 messages but I messed up with the link:

https://launchpad.net/people/ogmaciel/+codesofconduct

Using Firefox and Epiphany too...
:(

I talked with Fábio over IRC, and he said when he tries to access that page (people/$person/+codesofconduct) the screen goes black and then returns to the login screen.
Don't seem to be a launchpad related bug, more likely a bug on Ubuntu and that page is triggering it.
The page works fine for me both on production and on sample data. I tested on Firefox and Epiphany.
Fábio do you have any other information to add here?

Og and Fábio, I talked with one of the Ubuntu developers (fabbione) and he said this is most likely a Xorg bug.
Which graphic card and drivers you're using?

It's happens when using Flock Web browser too :(
What happen is the X (or gdm) is killed as process, and goes to the first console terminal (tty1).
Possibles relateds:
* Gnome 2.14
* Ubuntu 6.06
* Nvidia GLX package
* X.org 7 package
* Launchpad
* or the combination of then all (or some of them).

When it happen, you need restart the computer, and after login, may take some time to starts GNOME correctly.

I had the same problem...
after i signed i can't read the Codes of Conduct again...
it simply makes my screen go black and return to login screen.

Computer Specs:
* Ubuntu Dapper Drake LTS
* Nvidia GeForce FX 5200
* AMD Athlon XP 2600+
* 768mb DDR
* 160gb SATA on RaiserFS
* Mozilla Firefox 1.5.0.4

I was having the same problem with breezy.
Now with dapper and firefox 1.5.04 it worked.
see the link:
https://launchpad.net/people/birula/+codesofconduct

Hey Diogo,

Thanks for getting back... I have a NVidia FX 5200 as you can see from the output of lspci:

0000:01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1)

I'm sure Fabio has the same model as well. I can't really think of anything else that may be relevant... :(

Cheers,

Og

Hi Diogo,

Found this on my /var/log/Xorg.0.log.old:

Backtrace:
0: /usr/bin/X(xf86SigHandler+0x86) [0x80b4a56]
1: [0xffffe420]
2: /lib/tls/i686/cmov/libc.so.6(__libc_free+0x8a) [0xb7dc234a]
3: /usr/bin/X(Xfree+0x21) [0x819672a]
4: [0xb73c2c1a]
5: /usr/bin/X [0x8146ebd]
6: /usr/bin/X(CompositeGlyphs+0x94) [0x813a90f]
7: /usr/bin/X [0x813d1a9]
8: /usr/bin/X [0x813e70e]
9: /usr/bin/X(Dispatch+0x19e) [0x8085d26]
10: /usr/bin/X(main+0x47c) [0x806e0a8]
11: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xd2) [0xb7d73ea2]
12: /usr/bin/X(FontFileCompleteXLFD+0x81) [0x806d611]

Fatal server error:
Caught signal 11. Server aborting

Hope it helps shed some light.

Cheers,

Og

Hi Og,

The final of my /var/log/gdm/:0.log.1 is the same:

Fatal server error:
Caught signal 11. Server aborting

It's a kill signal.

Same problem for me.

+ Epiphany (Gecko); and,
+ Firefox (Gecko too).

I was using Ubuntu 6.06 and Xorg with nvidia driver.

Matsubara,

This page is evil ...

It renders sig/signedcontent inside a <label> for each valid signature,
which scrolls the window horizontally (this may cause the bug in nvidia
drivers).

If you really want to render sig/signedcontent in that page, you should
do it outside the label, in a <pre>, for instance.

I'm not sure we can tweak CSS properly to have floating/adaptable
<label>s, ask mpt.

ping me on IRC.
--
Celso Providelo <email address hidden>
Gwyddion Intelligent Devices - http://www.gwyddion.com

It crashed my X too...
I was using firefox and tried three times...
It crashed three times but after this I saw three signatures...

--
Andre Noel

I just tried it with an nvidia card, using both the open source and the nvidia-glx-legacy driver and it didn't crash. What video card and driver are you guys using?

I didn't trigger the bug here. I'm using the nv driver with a Geforce2 GTS Pro.
I will try with the nvidia driver later, but since it already is triggering other issues here ( https://launchpad.net/distros/ubuntu/+source/nvidia-kernel-common/+bug/6279 ), I sense it will trigger this one too.

If this indeed turns out to be a driver issue, I think there is nothing we can do other than work around the issue.
My vote would be to enable the wrapping on the text, or better, having a link to display the contents.

Can anyone confirm this could be an nVidia driver bug? Anyone with a different video card having this issue?

I am also using the nvidia driver and viewing a signed code of conduct page causes X to restart immediately. I experience the same behavior in both Firefox and Epiphany (seems to be generally related to gecko). I do not have the same problem when I visit the page using Opera.

0000:01:00.0 VGA compatible controller: nVidia Corporation NV37GL [Quadro FX 330] (rev a2)

I've landed a fix for the bug in Launchpad (bug 39995), so it should be fixed on launchpad.net sometime in the next week or so. Obviously that won't fix the bug in Xorg, it will just become harder to reproduce. So if you want to retain a test case, I suggest that one of you use wget or similar to download a complete copy of the crashy Launchpad page, verify that the bug happens with your downloaded copy, and attach it to this bug report, before launchpad.net is next updated.

As per instructions from last comment, here's the original source file that caused the problem (obtained via wget).

I had the same problem when using nvidia driver.
I only obtained to solve when I changed of nvidia for nv in xorg.conf.

I am using a GeForce 4 MX 440 SE

Is this issue still present with gutsy-beta?

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!