After running the Mageia 3 Gnome Live DVD for a few hours, opening and closing lots of applications, installing gnome extensions, etc, now I can no longer launch any new applications. If I try to launch them at the command line, I get the following: [live@localhost ~]$ gnome-tweak-tool Maximum number of clients reached ** (gnome-tweak-tool:5069): WARNING **: Could not open X display Maximum number of clients reachedTraceback (most recent call last): File "/usr/bin/gnome-tweak-tool", line 74, in <module> from gtweak.mainwindow import MainWindow File "/usr/lib/python2.7/site-packages/gtweak/mainwindow.py", line 20, in <module> from gi.repository import Gtk File "/usr/lib64/python2.7/site-packages/gi/importer.py", line 76, in load_module dynamic_module._load() File "/usr/lib64/python2.7/site-packages/gi/module.py", line 244, in _load overrides_modules = __import__('gi.overrides', fromlist=[self._namespace]) File "/usr/lib64/python2.7/site-packages/gi/overrides/Gtk.py", line 1624, in <module> raise RuntimeError("Gtk couldn't be initialized") RuntimeError: Gtk couldn't be initialized [live@localhost ~]$ shotwell Maximum number of clients reached ** (shotwell:5297): WARNING **: Could not open X display Maximum number of clients reachedCannot open display: Run 'shotwell --help' to see a full list of available command line options. [live@localhost ~]$ rhythmbox Maximum number of clients reached ** (rhythmbox:5339): WARNING **: Could not open X display Maximum number of clients reachedCannot open display: Run 'rhythmbox --help' to see a full list of available command line options. Reproducible: Steps to Reproduce:
CC: (none) => sysadmin-bugs, tmbComponent: RPM Packages => Release (media or process)Summary: Cannot launch more applications -- Maximum Number of Clients Reached => Cannot launch more applications -- Maximum Number of Clients Reached (live mode)
I ran into a similar problem and found a fix for it. A similar bug was reported: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/910539 The bug report blames fglrx-installer. Renaming /etc/ati/atiapfuser.blb to something else does seem to fix on my end. If something else is causing this for you, try running as root: lsof -p `pidof X` If there's an overabundance of open files towards the end. See what package it came from.
CC: (none) => fcs
I have encountered the same problem. Just file the bug report. Any help? (In reply to William Murphy from comment #1) > I ran into a similar problem and found a fix for it. > > A similar bug was reported: > https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/910539 > > The bug report blames fglrx-installer. Renaming /etc/ati/atiapfuser.blb to > something else does seem to fix on my end. > > If something else is causing this for you, try running as root: > lsof -p `pidof X` > > If there's an overabundance of open files towards the end. See what package > it came from. Can anyone ensures me about renaming the file? I have do google and found that it's a file from ati-installer. Is this file needed?
CC: (none) => elegant.pegasus
(In reply to Chih Wei Yao from comment #2) > I have encountered the same problem. Just file the bug report. Any help? > > (In reply to William Murphy from comment #1) > > I ran into a similar problem and found a fix for it. > > > > A similar bug was reported: > > https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/910539 > > > > The bug report blames fglrx-installer. Renaming /etc/ati/atiapfuser.blb to > > something else does seem to fix on my end. > > > > If something else is causing this for you, try running as root: > > lsof -p `pidof X` > > > > If there's an overabundance of open files towards the end. See what package > > it came from. > > Can anyone ensures me about renaming the file? I have do google and found > that it's a file from ati-installer. Is this file needed? http://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg4074154.html I found this and do as following: lsof -p 'pid of X' | grep atiapfuser I got about 199 entries of /etc/ati/atiapfuser. Seems we could confirm that this file is the origin of the bug. Should we just remove it?
Source RPM: (none) => x11-driver-video-fglrx-13.101-0.2.mga4.nonfree.i586.rpm, x11-driver-video-fglrx-13.101-0.2.mga4.nonfree.x86_64.rpm
*** Bug 10625 has been marked as a duplicate of this bug. ***
It's an empty file. Shouldn't hurt anything to remove it. I renamed it the first time (just in case), but the last update put it back. This time I deleted it.
Adding Anssi who may know more about it. * Wed Jun 06 2012 tmb <tmb> 8.980-1.mga3.nonfree + Revision: 256554 - fix filelist - fix version in readme.upgrade.urpmi - update README.upgrade.urpmi with changed hw support info - update to 8.98 (Catalyst 12.6beta) * supports x11-server 1.12 * NOTE! supports only HD5xxx and newer cards - drop P11, P12 (merged) + anssi <anssi> - add empty /etc/ati/atiapfuser.blb as per AMD suggestion
CC: (none) => anssi.hannula, eeeemail
I had removed the file for more than 2 weeks. It works very well. So the solution seems clear: Remove this empty file?
Ping!. Just ran into this one again, on a test install where I'd forgotten to remove the file. This is with x11-driver-video-fglrx-12.104-3.mga3.nonfree
CC: (none) => davidwhodgins
Release media for M3/M4 will not change. There is a newer rpm in M5 which I assume fixes the problem. This BR is unchanged for 15 months so I am closing as OLD. Anyone with good cause: please reopen against current release media (M5+). Thanks.
Status: NEW => RESOLVEDHardware: x86_64 => AllResolution: (none) => OLDSource RPM: x11-driver-video-fglrx-13.101-0.2.mga4.nonfree.i586.rpm, x11-driver-video-fglrx-13.101-0.2.mga4.nonfree.x86_64.rpm => x11-driver-video-fglrx-13.101-0.2.mga4