Issues with gnome2-2.30.2 on a 8.1-RELEASE amd64

Hello,
after upgrading to 8.1-RELEASE, and doing a fresh install of gnome2-2.30.2 i have the following problems:

1)
Code:
(gpk-update-icon:17004): Gtk-WARNING **: cannot open display: :0.0
Maximum number of clients reached
after i get the above sequence of messages, i am unable to start any new window.
[CMD="killall"]gpk-update-icon[/CMD]
seems to remedy this

2) when i move windows (even "simple" ones, like gnome-terminal) the redrawing happens in a very slow manner.

Anyone has any ideas on anything similar?
 
DutchDaemon said:
So does this thread survive? ;)

sorry, i wasn't clear enough. The speed problem is solved, by rebooting. The gnome (gpk-update-icon) problem still persists.
 
I wonder from where this message came from, I've scanned the whole sources of xauth, gdm, etc.
I'll run grep over the all packages that I have and FreeBSD sources to track it down. I don't see any other solution.
 
Some hint: I'm using Opera browser, when using Chrome or Firefox, it's crashing after few minutes of usage.
Code:
kenorb# zgrep -R "Maximum number of clients reached" /usr/ports/distfiles/
kenorb# bzgrep -R "Maximum number of clients reached" /usr/ports/distfiles/
Binary file /usr/ports/distfiles/xorg/xserver/xorg-server-1.7.5.tar.bz2 matches
Jupi!
 
Code:
work/xorg-server-1.7.5/os/connection.c:#define NOROOM "Maximum number of clients reached"

# grep -Rw NOROOM *
os/connection.c:#define NOROOM "Maximum number of clients reached"
os/connection.c:	csp.lengthReason = sizeof(NOROOM) - 1;
os/connection.c:	csp.length = (sizeof(NOROOM) + 2) >> 2;
os/connection.c:	iov[1].iov_base = NOROOM;
--
#define NOROOM "Maximum number of clients reached"

/************
 *   ErrorConnMax
 *     Fail a connection due to lack of client or file descriptor space
 ************/
static void ErrorConnMax(XtransConnInfo trans_conn)
---
        csp.lengthReason = sizeof(NOROOM) - 1;
...
        iov[0].iov_len = sz_xConnSetupPrefix;
        iov[0].iov_base = (char *) &csp;
        iov[1].iov_len = csp.lengthReason;
        iov[1].iov_base = NOROOM;
        iov[2].iov_len = (4 - (csp.lengthReason & 3)) & 3;
...
        if (!AllocNewConnection (new_trans_conn, newconn, connect_time))
        {
            ErrorConnMax(new_trans_conn);
            _XSERVTransClose(new_trans_conn);
        }
---
 
It's because MAXCLIENTS is hardcoded in xorg to 256.
Code:
./include/misc.h:#define MAXCLIENTS	256
See more: http://www.google.co.uk/search?q=unix+MAXCLIENTS+"Maximum+number+of+clients+reached"

We can increase this limit by recompiling, or find the reason of many conections.
Code:
> netstat -naf unix | grep X11 | wc -l
     232
> sudo netstat -naf unix | wc -l
    3688
> sudo netstat -naAL -f unix | head
unix  0/0/10         /var/tmp/orbit-kenorb/linc-5abc-0-64675600881f1
unix  0/0/50         /tmp/mysql.sock
unix  0/0/10         /var/tmp/orbit-kenorb/linc-a63-0-544447e52555c
unix  0/0/10         /var/tmp/orbit-kenorb/linc-8ed-0-6392f401e5c66
unix  0/0/10         /var/tmp/orbit-kenorb/linc-92c-0-6652e8bbe4c37
unix  0/0/10         /var/tmp/orbit-kenorb/linc-8f7-0-d9c3c3fe2694
unix  0/0/10         /var/tmp/orbit-kenorb/linc-934-0-43a20b68df10e
unix  0/0/10         /var/tmp/orbit-kenorb/linc-943-0-5cb97210df10d
unix  0/0/10         /var/tmp/orbit-kenorb/linc-8ee-0-57152184d9df9
unix  0/0/10         /var/tmp/orbit-kenorb/linc-973-0-1f74f8ebcf811
> sudo netstat -naAL -f unix | grep orbit | wc -l
     222
Found the app which doing the mess:
http://orbit-resource.sourceforge.net/

Code:
> sudo lsof -R | grep linc | head
lsof: WARNING: compiled for FreeBSD release 8.1-RELEASE; this is 8.1-STABLE.
gnome-ses  1792  1758     kenorb   14u    unix 0xffffff0004ce0000                0t0          /var/tmp/orbit-kenorb/linc-700-0-e9c56834d5c6
gnome-ses  1792  1758     kenorb   15u    unix 0xffffff0036af5d48                0t0          /var/tmp/orbit-kenorb/linc-700-0-e9c56834d5c6
gnome-ses  1792  1758     kenorb   14u    unix 0xffffff0004ce0000                0t0          /var/tmp/orbit-kenorb/linc-700-0-e9c56834d5c6
gnome-ses  1792  1758     kenorb   15u    unix 0xffffff0036af5d48                0t0          /var/tmp/orbit-kenorb/linc-700-0-e9c56834d5c6
seahorse-  1810  1792     kenorb   16u    unix 0xffffff00365a77f8                0t0          /var/tmp/orbit-kenorb/linc-712-0-eac0ea84d5f2
seahorse-  1810  1792     kenorb   17u    unix 0xffffff003672fd48                0t0          /var/tmp/orbit-kenorb/linc-712-0-eac0ea84d5f2
gconfd-2   1815     1     kenorb   13u    unix 0xffffff0036372000                0t0          /var/tmp/orbit-kenorb/linc-717-0-6c1c95ad78d0
gconfd-2   1815     1     kenorb   16u    unix 0xffffff00a48117f8                0t0          /var/tmp/orbit-kenorb/linc-717-0-6c1c95ad78d0
gconfd-2   1815     1     kenorb   17u    unix 0xffffff003672ad48                0t0          /var/tmp/orbit-kenorb/linc-717-0-6c1c95ad78d0
gconfd-2   1815     1     kenorb   18u    unix 0xffffff00363702a8                0t0          /var/tmp/orbit-kenorb/linc-717-0-6c1c95ad78d0
Code:
$ ps `lsof -R | grep linc | awk '{print $2}' | xargs`
...
 2443  ??  S      0:01.31 /usr/local/bin/gpk-update-icon
 2444  ??  S      0:01.35 /usr/local/bin/gpk-update-icon
 2445  ??  S      0:01.34 /usr/local/bin/gpk-update-icon
 2448  ??  S      0:01.34 /usr/local/bin/gpk-update-icon
 2452  ??  S      0:01.32 /usr/local/bin/gpk-update-icon
 2454  ??  S      0:01.31 /usr/local/bin/gpk-update-icon
 2458  ??  S      0:01.36 /usr/local/bin/gpk-update-icon
 2466  ??  S      0:01.33 /usr/local/bin/gpk-update-icon
 2659  ??  S      0:01.96 /usr/local/bin/gpk-update-icon
Code:
> pkg_info -W gpk-update-icon
/usr/local/bin/gpk-update-icon was installed by package gnome-packagekit-2.30.3
 
Workaround?
Code:
> cd /usr/ports/*/gnome-packagekit
> more pkg-descr
gnome-packagekit is the name of the collection of graphical
tools for PackageKit to be used in the GNOME desktop.
make deinstall clean
===>  Deinstalling for ports-mgmt/gnome-packagekit
===>   Deinstalling gnome-packagekit-2.30.3
pkg_delete: package 'gnome-packagekit-2.30.3' is required by these other packages
and may not be deinstalled (but I'll delete it anyway):
gnome2-2.30.2
$ sudo killall gpk-update-icon
Bye GNOME!
 
The fact is that currently gnome2-2.30.2 depends on gnome-packagekit-2.30.3 as
[CMD="pkg_info"] -R gnome-packagekit-2.30.3[/CMD] shows.
IMHO we should tell (submit a PR via send-pr(1)) gnome@FreeBSD.org who maintain this port.

PS
kenorb, a fast way to determine the bad port would be:
[CMD="which"]gpk-update-icon[/CMD]
Code:
/usr/local/bin/gpk-update-icon
[CMD="pkg_info"] -W `which gpk-update-icon`[/CMD]
Code:
/usr/local/bin/gpk-update-icon was installed by package gnome-packagekit-2.30.3
 
The problem was that I didn't know that gpk-update-icon is messing around, till today when you post the link to this thread. Then I didn't read second part of your message about gpk-update-icon, I thought that it's another software which can't run because of those limits. I was debugging it from the source of the problem, that's from the error message, through analysing source how this limit is applied, then checking which PID is using those sockets.
 
I run in same problem, after a search I found firefox cause that, if I close it and start an application I don't see the error message above, so my question why firefox do that!
 
Well I run FreeBSD 8.2 - amd64, and haven't had this issue. And I use firefox an awfull lot when lying in bed next to my server. So perhaps an upgrade might be in order?

Cheers,
Jonathan.
 
Back
Top