[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, where is the solution?
xhost +
Maximum number of clients reachedxhost: unable to open display :0.0
???
I'm using gdm (Gnome 2.30).
I've the same problem, but on FreeBSD 8.1-STABLE
See: http://forums.freebsd.org/showthread.php?p=106367
--
Warning: Unable to open display ':0' and
to solve the X forwarding problem i googled a lot as i wanted to install
Oracle 11g on my kubuntu 9.10 machine
i found out the solution that did work
To resolve this problem, you have to let X server listen on tcp port
modify file /etc/kde4/kdm/kdmrc
You will see
“ServerArgsLocal=-br
xhost + is not the solution, xhost + is another problem.. undid the
status change, this is definitely not fixed.
** Changed in: network-manager (Ubuntu)
Status: Fix Committed = Incomplete
--
Warning: Unable to open display ':0' and cannot connect to X server :0
I saw the same thing Traksius reported a few comments above. I
couldn't open any gui app w/ root priviledges with gksudo or gksu.
I could not open Synaptic from the menu after entering my password,
either. However, after stopping networking, I could successfully use
gksudo, gksu, and open
My sympathies. I finally gave up and started running a little shell
script in the background that does an 'ls $HOME /dev/null 21' every
60 seconds. Total kludge, but it eliminates the symptoms. Clearly none
of the maintainers feel this is of any particular importance so I guess
I'll have to
I also have this bug and it drives me crazy...
It started when I changed to Intrepid. I still used KDE 3 for a while
and thought that it may be connected to that. Now I changed to KDE4,
meanwhile changed hardware but still got this.
I tried to nail it down to any application, no success. In
Same problem as in
https://bugs.launchpad.net/ubuntu/+bug/250712/comments/23
** Changed in: network-manager (Ubuntu)
Sourcepackagename: None = network-manager
--
Warning: Unable to open display ':0' and cannot connect to X server :0
https://bugs.launchpad.net/bugs/250712
You received this bug
I'm running Intrepid Ibex (gnome) and noticed this issue after
reinstalling NetworkManager. After logging into gnome, not able to get
anything requiring a window to run. I stopped networking (via
networkmanager-applet) and everything is ok. Turn on networking, no
programs allowed.
Workaround
(copied from my comment to bug 263211:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/263211
)
It seems that Maximum clients reached is more a symptom of it's own bug
classification, which is indicative of any application not managing its X
resources carefully.
All
Then there are definitely two underlying issues producing similar
symptoms. In my case: When the NFS automount times out, the next X
client that tries to check .Xauthority is unable to do so. I can only
assume that it used to attempt a read (which would trigger the mounter)
and has been changed
this is not a bug in X, but some client that fails to clean up the
connections. gnome-screensaver suffered from this recently.
** Changed in: ubuntu
Sourcepackagename: xorg = None
--
Warning: Unable to open display ':0' and cannot connect to X server :0
https://bugs.launchpad.net/bugs/250712
Well I certainly can.
$ lspci -vvnn
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML
and 945GT Express Memory Controller Hub [8086:27a0] (rev 03)
Subsystem: Hewlett-Packard Company Unknown device [103c:30bb]
Control: I/O- Mem+ BusMaster+ SpecCycle-
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/19095155/Xorg.0.log
--
Warning: Unable to open display ':0' and cannot connect to X server :0
https://bugs.launchpad.net/bugs/250712
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Still happening here, just had to kill off nspluginviewer to release
some file descriptors. :-(
Maximum number of clients reached
--
Warning: Unable to open display ':0' and cannot connect to X server :0
https://bugs.launchpad.net/bugs/250712
You received this bug notification because you are a
I think we have two distinct underlying issues. In some cases, the
problem is related to running out of file descriptors. In others (mine,
for example) it's due to the automounter timing out the users's home
directory, rendering .Xauthority unreachable.
But, since it's getting no attention from
xorg.conf and lspci -vvnn included in the attachment. As said, i can't
reproduce this any more.
** Attachment added: x.txt
http://launchpadlibrarian.net/18532348/x.txt
--
Warning: Unable to open display ':0' and cannot connect to X server :0
https://bugs.launchpad.net/bugs/250712
You
Hi Bruce!
I haven't faced this problem for a while now so it might be that the
report doesn't apply to me any more. But I'll try to remember to post
the information you requested when I go back to work on Monday.
--
Warning: Unable to open display ':0' and cannot connect to X server :0
Hi risto.kurppa,
Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log
file from after reproducing this issue. If you've made any customizations to
your /etc/X11/xorg.conf please attach that as well.
** Changed in: xorg (Ubuntu)
Status: New = Incomplete
--
I am running ubuntu 8.04 on amd64 box. I have the same problem and I
confirmed that reloading the automounter (/etc/init.d/autofs reload)
recovers and I am able to start X applications.
--
Warning: Unable to open display ':0' and cannot connect to X server :0
I've gotten in the habit of periodically doing an 'ls' in my home
directory whenever an X app fails to appear. Not holding my breath for
a fix.
--
Warning: Unable to open display ':0' and cannot connect to X server :0
https://bugs.launchpad.net/bugs/250712
You received this bug notification
Question - is everyone affected here using KDE 4 (I'm using 4.1 for
example) ?
I've noticed my work box (32-bit Hardy install) which runs KDE 3.5.9 is
reports less file descriptors open by the X server:
# ls -1 /proc/`pidof X`/fd | wc -l
53
Both are Intel graphics with the same up to date
On Aug 9, 2008, at 9:31 AM, Chris Samuel wrote:
Question - is everyone affected here using KDE 4 (I'm using 4.1 for
example) ?
No, we're using Gnome under Hardy. (I work for the same organization
as Tom Hallman, who posted to the ubuntuforums thread referenced here
using the name
I'm running KDE 3.5.9 on x86_64 Hardy.
Is KDE the common thread? I seem to be the only person using the
automounter, for example.
--
Warning: Unable to open display ':0' and cannot connect to X server :0
https://bugs.launchpad.net/bugs/250712
You received this bug notification because you are
** Changed in: xorg (Ubuntu)
Sourcepackagename: None = xorg
--
Warning: Unable to open display ':0' and cannot connect to X server :0
https://bugs.launchpad.net/bugs/250712
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I'm now starting to come across this too having moved to KDE 4.1
recently. I get the same error just doing:
[EMAIL PROTECTED]:~$ xhost
Maximum number of clients reachedxhost: unable to open display :0
That error is being returned by the X server when the client tries to
send it the xauth
Looking at my X server it has 256 open file descriptors at present,
could that be related ?
# ls -1 /proc/`pidof X`/fd | wc -l
256
cheers,
Chris
--
Warning: Unable to open display ':0' and cannot connect to X server :0
https://bugs.launchpad.net/bugs/250712
You received this bug notification
I have conclusively traced this down. It starts happening as soon as
the automounter times out (typically 10 minutes of inactivity) and
unmounts my home directory (accessed over NFS v3). I have no idea what
changed in 8.04 to cause this symptom, as I've been using an NFS home
directory for over
No NFS or automounter here, just a local home directory using XFS.
--
Warning: Unable to open display ':0' and cannot connect to X server :0
https://bugs.launchpad.net/bugs/250712
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Started happening almost immediately after new install of Kubuntu 8.04.1
'Hardy Heron'. Never seen this with any prior release, and I've been
using Ubuntu/Kubuntu for almost 2 years.
A quick:
$ xhost +MY_HOSTNAME
fixes it, but what is causing the loss in permissions in the first
place?
--
Can confirm similar behavior on Ubuntu Hardy 32 bit. Suddenly connection
to the X server is lost and I am unable to open any application. Trying
to open xterm from the command line results in:
#$ xterm
No protocol specified
xterm Xt error: Can't open display: :1.0
However, I don't see anything
I'm not sure if it is the same problem, but lately I have been getting
this error in .xsession-errors:
Maximum number of clients reachedkonqueror: cannot connect to X server
:1.0
which I can only guess means:
Maximum number of clients reached
konqueror: cannot connect to X server :1.0
replace
32 matches
Mail list logo
