From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: puzzled over why xrdb process hangs
Date: Thu, 23 Feb 2006 14:48:30 +0000 (UTC) [thread overview]
Message-ID: <loom.20060223T152647-869@post.gmane.org> (raw)
In-Reply-To: 200602222113.41144.krakrjak@volumehost.net
Zac Slade <krakrjak <at> volumehost.net> writes:
> > quickly running 'top' I find the culprit:
> > krdb. I can kill it off and the sequence completes and the system is fine.
> >
> > But 'eix xrdb' reveals:
> > x11-apps/xrdb
> > Available versions: [M]1.0.1
> > Installed: none
> > If it's not installed how can it be running (hung)?
> > I've tried all sorts of things to fix this and nothing
> > works, including revdep-rebuild...
> Are you using the monolithic or split ebuilds for kde?
got me on this one. Not Sure? I'd guess both is a bad idea?
> That is, did you emerge kde or emerge kde-meta?
yes, but it has been 'unmerge'd.
> If you using the monolithic ebuilds, this binary will be provided by a
> different package. If you'll locate the actual binary, you can find which
> package provides it with equery b /path/to/xrdb. You might be able to
> recompile that package.
This package is not there:
/# equery b /path/to/xrdb
[ Searching for file(s) /path/to/xrdb in *... ]
just like:
* x11-apps/xrdb
Available versions: [M]1.0.1
Installed: none
I can kill off the hung xrdb process, as user james.
I do not have to sudo or be root, so it's definately a kde thing
(outta wack)...
What's the best way to rebuild kde?
other ideas?
James
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-23 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 20:59 [gentoo-user] puzzled over why xrdb process hangs James
2006-02-23 3:13 ` Zac Slade
2006-02-23 14:48 ` James [this message]
2006-02-23 15:26 ` [gentoo-user] " Boyd Stephen Smith Jr.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20060223T152647-869@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox