Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 Jul 2005 17:50:37 -0500 (CDT)
From:      Chris <racerx@makeworld.com>
To:        cpghost <cpghost@cordula.ws>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Firefox won't start (again!)
Message-ID:  <20050711174937.D23753@makeworld.com>
In-Reply-To: <20050711153414.GA67497@epia2.farid-hajji.net>
References:  <20050711153414.GA67497@epia2.farid-hajji.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 11 Jul 2005, cpghost wrote:

> On a RELENG_5 system from June 30th (source and ports),
> firefox-1.0.4 won't start. It just hangs in the kserel state.
> This is on a diskless system using NFS.
>
> Running truss(1) on the hanging firefox-bin process shows:
>
> kse_release(0x8065fa4) = 383 (0x17f)
> kse_release(0x8065fa4) = 0 (0x0)
> kse_release(0x8065fa4) = 383 (0x17f)
> kse_release(0x8065fa4) = 383 (0x17f)
> kse_release(0x8065fa4) = 0 (0x0)
> kse_release(0x8065fa4) = 383 (0x17f)
> kse_release(0x8065fa4) = 383 (0x17f)
> kse_release(0x8065fa4) = 0 (0x0)
> ...
>
> When starting, firefox generates a GNOME Warning:
>
> Gdk-WARNING **: gdk_property_get(): length value has wrapped in
> calculation (did you pass G_MAXLONG?)
>
> But thunderbird does the same, though it doesn't hang.
>
> /etc/libmap.conf is empty.
>
> Any idea?
>
> Thanks,
> -cpghost.
>

C'mon - we two can't be the only ones with this issue...

---------------------------------------------------------------------
# firefox
(firefox-bin:80350): Gdk-WARNING **: gdk_property_get(): length value has 
wrappe
d in calculation (did you pass G_MAXLONG?)
The program 'Gecko' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
   (Details: serial 1338 error_code 9 request_code 150 minor_code 4)
   (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.)
#

------------------------------------------------------------------
Best regards,
Chris

When a broken appliance is demonstrated for the repairman,
it will work perfectly.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050711174937.D23753>