** Changed in: gnome-desktop
Importance: Unknown = Medium
--
apps-wont-open-due-to-maximum-clients-reached-error
https://bugs.launchpad.net/bugs/263211
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
** Changed in: gnome-screensaver (Ubuntu)
Status: New = Fix Released
--
apps-wont-open-due-to-maximum-clients-reached-error
https://bugs.launchpad.net/bugs/263211
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
** Changed in: gnome-screensaver (Ubuntu)
Status: Fix Released = New
--
apps-wont-open-due-to-maximum-clients-reached-error
https://bugs.launchpad.net/bugs/263211
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
Not fixed in Ubuntu 10.04 Lucid. Is there any way (besides disabling the
screensaver) to avoid this? Like manually removing the
pixmaps/unknown's from X?
** Changed in: gnome-screensaver (Ubuntu Intrepid)
Status: Fix Released = Incomplete
** Changed in: gnome-screensaver (Ubuntu Intrepid)
Please don't reopen old bugs. This particular bug was fixed a long time
ago, and it's most likely that you are experiencing a completely
unrelated issue
** Changed in: gnome-screensaver (Ubuntu)
Status: Incomplete = Fix Released
--
apps-wont-open-due-to-maximum-clients-reached-error
Hello, I got a same problem after update from Karmic to Lucid.
Maximum number of clients reachedxwininfo: unable to open display
':0.0'
--
apps-wont-open-due-to-maximum-clients-reached-error
https://bugs.launchpad.net/bugs/263211
You received this bug notification because you are a member of
It looks like that it is not really related to the kdelibs because even not
using any kde apps after a fresh start the problem occured. Maybe the root
cause is firefox cf:
http://www.karakas-online.de/forum/viewtopic.php?t=10494
I have a lot of :
0x401417d Firefox: (Popup Namoroka)
Hi,
I'm also affected by this bug with ubuntu 9.10.
Maybe it goes faster to trigger in my case as I have 2 monitors.
It could be related to kdelibs as i installed them to be able to use Kate.
And I noticed that kate used 1 client connection for each file opened as a tab
in my kate window.
interfasys: something in kde is leaking/creating client connections, and
the limit (256) is reached. File a bug against kde.
--
apps-wont-open-due-to-maximum-clients-reached-error
https://bugs.launchpad.net/bugs/263211
You received this bug notification because you are a member of Ubuntu
Desktop
This problem has started to affect me today.
I'm using a backport of KDE 4.4.1 on Karmic.
Applications in use are Skype, Jungledisk, Chromium, Firefox, Terminal and
Dolphin.
All the sudden Dolphin can't open any of my files and if I try from the
terminal I'm giving the message described in this
This report says fix released - where is this fix? How can i get it?
I've now got this problem on my new laptop, it started as soon as I
plugged it into a second screen this afternoon - my main three screen PC
uses nvidia, this uses ATI but i've only ever had these symptoms when
using more than
I believe I have this problem in Intrepid, new things stop spawning -
which also means if I go to system - shutdown a box appears but all the
buttons (restart/shutdown/log out etc.) can't appear - makes the system
largely unusable.
w.r.t. the workaround suggested, I have at the moment about 10
On Saturday 22 November 2008, Chris Purves wrote:
I did try something similar, but for me all the extra clients were
opened shortly after login, so not enough time to kill processes before
they would spawn multiple instances. I found that I had 183 instances
of python running after logging in
Are there any tips on how to troubleshoot this problem and isolate which
application is not releasing resources. I am running kubuntu intrepid
and when running xrestop see that the number of clients goes to 210 on
startup.
--
apps-wont-open-due-to-maximum-clients-reached-error
On Saturday 22 November 2008, Chris Purves wrote:
Are there any tips on how to troubleshoot this problem and isolate which
application is not releasing resources. I am running kubuntu intrepid
and when running xrestop see that the number of clients goes to 210 on
startup.
I find that it's a
I did try something similar, but for me all the extra clients were
opened shortly after login, so not enough time to kill processes before
they would spawn multiple instances. I found that I had 183 instances
of python running after logging in to KDE. Removing as many startup
apps as I could did
Where is the KDE version of this? How many of these bugs can there be,
since it just started impacting me within the past year... and I don't
run Gnome... I run KDE starting with Kubuntu-base-install.
And how do I know which bug is impacting me, since there seem to be many
which have the same
You might start by disabling your screen saver (though you can leave
your power saving features on). Even before this bug patch was
committed, I disabled the screen saver and stopped experiencing the
problem.
This is just a helpful suggestion, not a verified solution by any means.
--
On Thursday 30 October 2008, Brion Swanson wrote:
You might start by disabling your screen saver (though you can leave
your power saving features on). Even before this bug patch was
committed, I disabled the screen saver and stopped experiencing the
problem.
This is just a helpful
In KDE, the knetworkmanager seems to increment the count of
xwininfo -root -children
every time you interact with the rt-click menu.
At first it raises the count a few... and when you make the menu
disappear, it's always one greater that the count before...
Should this be added as a
This increase in numbers is consistent, and was caused simply by Right-
Clicking on knetworkmanager and hitting escape... over and over again.
1425
1425
1425
1425
1426
1430
1434
1438
1442
1444
1448
1453
1458
1466
1472
1474
1474
1474
It seems that Maximum clients reached is more a symptom of
** Changed in: gnome-desktop
Status: New = Fix Released
--
apps-wont-open-due-to-maximum-clients-reached-error
https://bugs.launchpad.net/bugs/263211
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
gnome-screensaver (2.24.0-0ubuntu2) intrepid; urgency=low
* debian/patches:06_dont-leak-root-windows.patch:
- Don't create the GNOME background pixmap with root=TRUE, since that
results in a permanent client connection and unfreeable foreign image;
the leak of these causes you
the bug was not closed by the changelog because the component were
different
** Changed in: gnome-screensaver (Ubuntu Intrepid)
Sourcepackagename: gnome-desktop = gnome-screensaver
--
apps-wont-open-due-to-maximum-clients-reached-error
https://bugs.launchpad.net/bugs/263211
You received this
** Changed in: gnome-desktop (Ubuntu Intrepid)
Target: None = ubuntu-8.10
--
apps-wont-open-due-to-maximum-clients-reached-error
https://bugs.launchpad.net/bugs/263211
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
It seems that the number of clients consumed by each GNOME ScreenSaver
activation is equal to the number of monitors you have. Those with more
than one monitor are getting bitten by this somewhat quicker!
--
apps-wont-open-due-to-maximum-clients-reached-error
A little digging gives the following:
libgnome-desktop/gnome-bg.c - both the gnome_bg_create_pixmap() and
make_root_pixmap() function it calls are largely unchanged since this
code was added - however that was only in November 2007 - previously
libegg was used
The change to use this function
That commit has the following ChangeLog entry:
* configure.ac:
* src/Makefile.am:
* src/debug-screensaver.sh:
* src/gs-manager.c (gs_manager_init),
(apply_background_prefs_to_window), (manager_show_window):
* src/gs-window-x11.c
An obvious patch appears to be:
--- src/gs-manager.c.orig 2008-10-10 18:28:13.0 +0100
+++ src/gs-manager.c2008-10-10 18:28:21.0 +0100
@@ -1281,9 +1281,9 @@
pixmap = gnome_bg_create_pixmap (manager-priv-bg,
** Changed in: gnome-desktop (Ubuntu)
Sourcepackagename: xorg = gnome-desktop
Importance: Undecided = High
--
apps-wont-open-due-to-maximum-clients-reached-error
https://bugs.launchpad.net/bugs/263211
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
the issue is an upstream one, could somebody send it to
bugzilla.gnome.org?
--
apps-wont-open-due-to-maximum-clients-reached-error
https://bugs.launchpad.net/bugs/263211
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in
I'll file it on bugzilla.gnome.org.
--
apps-wont-open-due-to-maximum-clients-reached-error
https://bugs.launchpad.net/bugs/263211
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in ubuntu.
--
desktop-bugs mailing list
OK, filed as gnome bug 555701
(http://bugzilla.gnome.org/show_bug.cgi?id=555701)
** Bug watch added: GNOME Bug Tracker #555701
http://bugzilla.gnome.org/show_bug.cgi?id=555701
** Also affects: gnome-desktop via
http://bugzilla.gnome.org/show_bug.cgi?id=555701
Importance: Unknown
** Changed in: gnome-desktop
Status: Unknown = New
--
apps-wont-open-due-to-maximum-clients-reached-error
https://bugs.launchpad.net/bugs/263211
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in ubuntu.
--
Thank you for sending the bug to GNOME
** Changed in: gnome-desktop (Ubuntu)
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
Status: Confirmed = Triaged
--
apps-wont-open-due-to-maximum-clients-reached-error
https://bugs.launchpad.net/bugs/263211
You received this bug
35 matches
Mail list logo
