Firefox will not start under vnc

Bug #173196 reported by Joe Harrington on 2007-12-01
8
Affects Status Importance Assigned to Milestone
vnc4 (Ubuntu)
Medium
Unassigned

Bug Description

This is similar to Bug #115529, except that the fix posted there does not work and the errors are different.

I start vnc4server, latest patched Feisty on intel 64, with -extension XFIXES, Gnome environment. I start a client looking at it. I type firefox. Firefox dies. Generally it dumps core. Once it exited with an X error, same one as in the referenced bug, but it's gone now and I can't make it do that again. It is 100% reproducible, on several different machines and by about 5 different users. It's been this way since I switched to Ubuntu in the Spring (still on Feisty), so it's not an issue that changed in the latest firefox update.

--jh--

Alexander Sack (asac) wrote :

please submit a crash report by clicking on the firefox .crash file that should be available in /var/crash after core dump.

 - Alexander

Changed in firefox:
status: New → Invalid
Joe Harrington (joeharr) wrote :

This crash dump is with the new version of firefox that updated last night. It's from a 64-bit intel machine running updated feisty. What happens is the window appears (see next attachment, which is the screenshot of the window's state), hangs out for about a minute, and disappears with a segfault message. Before this test, I moved my .mozilla directory to a different name. It made a fresh .mozilla, whose files are named in the third attachment.

--jh--

Joe Harrington (joeharr) wrote :
Doug Schaefer (doug-schaefer) wrote :

I've run into the same issue on a 64-bit intel machine. I was wondering why this was marked invalid.

Joe Harrington (joeharr) wrote :

Yes, I posted the requested data but it appears nobody did anything with it. Does it work in current ubuntu? Why was it invalidated? Is it not reproducible?

Thanks,

--jh--

Alexander Sack (asac) wrote :

reassigning to vnc. anyone can reproduce this?

Changed in firefox:
importance: Undecided → Medium
status: Invalid → Incomplete
tun3r (i-m-albert) wrote :

I'm still seeing this. It crashes (core dumps - behaves just like Joe Harrington described) when trying to launch firefox from vnc on AMD 64 bit.

tun3r (i-m-albert) wrote :

I have 7.10 ubuntu (gutsy).

Mirar (launchpad-sort) wrote :

Firefox works me under vnc4server 4.1.1+xorg1.0.2-0ubuntu7, running fvwm, i86_64 (AMD64) system.
Maybe not a simple vnc4 bug but Gnome in combination with VNC?

Duane Hinnen (duanedesign) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Joe Harrington (joeharr) wrote :

This was fixed in 8.04. Thanks!

--jh--

Changed in vnc4:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers