502442 - 'Start Shirekoto' in the profile manager does not work(x window error)

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Hariharan]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.1pre) Gecko/20090704 Ubuntu/9.04 (jaunty) Shiretoko/3.5.1pre
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.1pre) Gecko/20090704 Ubuntu/9.04 (jaunty) Shiretoko/3.5.1pre

Clicking start shirekoto in profile manager causes the profilemanager to crash.



  

Reproducible: Always

Steps to Reproduce:
1.Open profilemanager(firefox -ProfileManager in terminal)
2.Change the current profile or even simply click start shirekoto
Actual Results:  
The following text appears in the terminal and profilemanager crashes.
The program 'firefox-3.5' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 891 error_code 3 request_code 20 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)


Expected Results:  
The firefox window has to open with the selected profile

Comment 1

[Ryan Fugger]

I am also experiencing this bug.  It does not always happen, but quite often.  My error is:

The program 'firefox-3.5' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 971 error_code 3 request_code 20 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

I am running Ubuntu 9.04, and have installed the firefox-3.5 package.  My browser string is:

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1) Gecko/20090701 Ubuntu/9.04 (jaunty) Shiretoko/3.5

Comment 2

[Ryan Fugger]

If I run firefox with the --sync command:

firefox -p --sync

it seems to fix the problem.

Comment 3

[Maiko Cezar]

Hi, I have the same problem. I can't use the profile manager without the arg --sync.

Ubuntu 9.04
Firefox 3.5.1

Comment 4

[Ryan Fugger]

Actually, sometimes this crash happens even with --sync.  A better workaround is to just start firefox normally (without -p) after having chosen the profile you want, and having had profilemanager crash after clicking 'Start Shiretoko'.

Comment 5

[Wolfgang Breyha]

I can confirm this bug. I've 2 or 3 profiles on some FF3.5 installations and sometimes FF3.5 crashes exactly after selecting the profile or pressing start with

The program 'firefox' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 2015 error_code 3 request_code 20 minor_code 0)

Starting Firefox with -P <profile> always works find. This bug accours since I use 3.1beta versions on Fedora 10 and it still occurs less frequently on F11 and FF3.5.3. Currently I'm using Fedora RPM versions.

FF3.0.x worked pretty well using the ProfileManager.

Comment 6

[Tyler Downer [He/Him]]

Reporter, are you still seeing this issue with Firefox 3.6.12 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
Also, please consider using the most recent Firefox 4 beta build, your bug may be resolved there.

Comment 7

[Ryan Fugger]

Not seeing this in 3.6.  Not sure about safe mode...

Comment 8

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.