Seamonkey won't start on X with error "The program 'seamonkey-bin' received an X Window System error"

RESOLVED WORKSFORME

Status

--
critical
RESOLVED WORKSFORME
10 years ago
9 years ago

People

(Reporter: misak.bugzilla, Unassigned)

Tracking

Trunk
x86
Linux

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 years ago
SeaMonkey bring profile selection window, then quits with message on console:
The program 'seamonkey-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 2946 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.)

./seamonkey --sync starts ok

Mozilla/5.0 (X11; U; Linux i686; rv:1.9.1a2pre) Gecko/20080818123433 SeaMonkey/2.0a1pre ID:20080818123433
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1a2pre) Gecko/20080818000659 SeaMonkey/2.0a1pre

Works for me.
- Do you get this every time when starting without --sync ?
- Is this a tinderbox-build (hourly), localized (non-en-US) or own-compiled build you're using? If localized, which language? If own-compiled, what's your about:buildconfig?
(Reporter)

Comment 2

10 years ago
Actually, it happens once, and disappears after system restart. It seems X/Nvidia driver related.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → WORKSFORME
(Reporter)

Comment 3

10 years ago
I'm reopening this bug, this happening several times per day. running ./seamonkey --sync then exiting and running again fixes it. Sometime this should be repeated several times. Also i mentioned that this bug occurs when seamonkey exits with segmentation fault. Here is my console output for couple of sessions:

[misak@misak bin]$ ./seamonkey 
cz-service: No windows, starting new one.

(seamonkey-bin:31654): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed

(seamonkey-bin:31654): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed

(seamonkey-bin:31654): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed

(seamonkey-bin:31654): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed

(seamonkey-bin:31654): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed

(seamonkey-bin:31654): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed

(seamonkey-bin:31654): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed

(seamonkey-bin:31654): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed
./run-mozilla.sh: line 131: 31654 Segmentation fault      "$prog" ${1+"$@"}
[misak@misak bin]$ ./seamonkey
The program 'seamonkey-bin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 2056 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.)
[misak@misak bin]$ ./seamonkey --sync
[misak@misak bin]$ ./seamonkey
cz-service: No windows, starting new one.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Does that "cz-service" line mean that you're starting ChatZilla first? I rarely use ChatZilla, but when I do, my mail and browser windows are already open. Could that make a difference?

Or could it be a race condition between ChatZilla and whatever other windows you are opening at the same time (via preferences in the profile, set by Edit => Preferences => Appearance => When Seamonkey starts up, open...)?
(Reporter)

Comment 5

10 years ago
Yes, i have turned on chatzilla, mailnews and browser on start, but it's not related IMHO. This based on timing. Error appears right after i choose profile, but if seamonkey starts normally cz-service message appears after some seconds. Anyway i'll try to disable chatzilla to see what happens.
(In reply to comment #5)
> Yes, i have turned on chatzilla, mailnews and browser on start, but it's not
> related IMHO. This based on timing. Error appears right after i choose profile,
> but if seamonkey starts normally cz-service message appears after some seconds.
> Anyway i'll try to disable chatzilla to see what happens.
> 

I never get the bug; but by default I start the mail client first, the browser manually by clicking the icon at bottom left once the mailer has finished "getting mail at startup" and ChatZilla only when needed (which is rarely).

Another possible difference between you (who get the bug) and I (who don't) could be how we choose a profile: the above seems to imply that you select it manually in the Profile Manager; I usually don't set it manually (reusing the same profile as the time before) but when I do I usually set it on the command-line, e.g.:

    LC_TIME=en_GB seamonkey -P default >> ~/seamonkey.log 2>&1
or
    seamonkey -P clean -browser
etc.
(Reporter)

Comment 7

10 years ago
Also there other players - I'm running Fedora 9, KDE 4.1, X server 1.4.99 and nvidia driver 173.14.12-1
(In reply to comment #7)
> Also there other players - I'm running Fedora 9, KDE 4.1, X server 1.4.99 and
> nvidia driver 173.14.12-1
> 

openSUSE 11.0, KDE 3.5.9 (with this login name), Xorg 1.4.0.90, video card SiS 660, X11 driver sis version 4, monitor Samsung SyncMaster 570B TFT driven at 1024x768, 16777216 colors.
Assignee: general → nobody
Component: General → GFX: Gtk
Product: SeaMonkey → Core
QA Contact: general → gtk
(Assignee)

Updated

10 years ago
Product: Core → Core Graveyard
(Reporter)

Comment 9

9 years ago
This never happens now.
Status: REOPENED → RESOLVED
Last Resolved: 10 years ago9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.