From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 3F8FE1381F3 for ; Sun, 11 Nov 2012 12:35:36 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D095621C06A; Sun, 11 Nov 2012 12:35:17 +0000 (UTC) Received: from mail-we0-f181.google.com (mail-we0-f181.google.com [74.125.82.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 5B8C121C067 for ; Sun, 11 Nov 2012 12:33:31 +0000 (UTC) Received: by mail-we0-f181.google.com with SMTP id u54so2425427wey.40 for ; Sun, 11 Nov 2012 04:33:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:organization :x-mailer:mime-version:content-type:content-transfer-encoding; bh=qZQLYgxZtpXbMNDHuyYFw+di6FcDvMbi/ZHOiDL/oCA=; b=Hrxkg61rr8nemW6euOGAEq/ihkiI2UcGQMbRfmrGt9XJBcLNauEJ6qKr+tlT3fdn61 jF7TUz9nDV/b6ZlRmDnHozFTAr6RO8Knur8Dndy0YT2K81ee3rgyiYchHDRoIqTxpptW FGkEcpZ/h8uzscHqdnMJr3x59zpxa+4FZiN1UAnY8UbzIeNPdZQfOfFrzw6hmpqg4cUL mlb0Fd6XTuPzwQCxssVJt95J+wi3xSDnAjzcAl9JVMVStTq6xxsiRw/bfrcGoA+zuscB l8obDUWyzefjDPkQhHxqjQrs37q8vE2wSIfEFQ4zqitooBArh3p0/Ntypif013K7CnsX Quqg== Received: by 10.180.94.41 with SMTP id cz9mr10679693wib.2.1352637209977; Sun, 11 Nov 2012 04:33:29 -0800 (PST) Received: from khamul.example.com (196-210-100-105.dynamic.isadsl.co.za. [196.210.100.105]) by mx.google.com with ESMTPS id i6sm10109699wix.5.2012.11.11.04.33.27 (version=SSLv3 cipher=OTHER); Sun, 11 Nov 2012 04:33:29 -0800 (PST) Date: Sun, 11 Nov 2012 14:31:06 +0200 From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] kde splash screen won't show up when loading kde Message-ID: <20121111143106.70e088a1@khamul.example.com> In-Reply-To: <509EE347.2000909@gmail.com> References: <20121110174910.65bfdb4d@amoxsoft> <509EE347.2000909@gmail.com> Organization: Internet Solutions X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.13; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 94c5bf82-dff3-4af8-b8b0-ff9ec68580c8 X-Archives-Hash: f645b9016cd1a39ecbf05f3531392a3b On Sat, 10 Nov 2012 17:29:11 -0600 Dale wrote: > John Walters wrote: > > On Sat, 10 Nov 2012 13:58:42 +0100 > > Pau Peris wrote: > > > >> i've just upgraded kde through a custom @set, the same i used over > >> the last years, but this time although kde-base/ksplash is > >> installed kde splash screen does not appear anymore while loading > >> kde. > >> > >> Do someone know which single package could i missed? Thx :) > > Can't really say without looking at your system, but you can try: > > > > 1) revdep-rebuild > > > > If that doesn't find any problem, then: > > > > 2) emerge -e world > > > > I know it will take a long while, but I have found it necessary to > > do this on a regular basis, especially with upgraded packages. > > > > JW > > > > > > > I have noticed that when I do a KDE upgrade and something acts a > little funny, a emerge -e world generally fixes it. I do wish there > was a way to know what needed to be emerged again without doing > everything. > > OP, you could try doing a emerge -e ksplash with the -t option and > sort of see what it depends on that way. Then try to emerge those > packages first to see if it helps. > > For what it is worth, I did the upgrade and the only problem I ran > into was my saved session got messed up. I had to set things up and > save it again, I haven't logged out and back in yet so I hope that > fixes that problem. > > Any Linux geeks know how to fix this sort of thing without a emerge -e > world? short answer: usually, you can't longer answer: you can't, because software usually can't detect the answer. revdep-rebuild does a fine job of finding what it was designed to do - reverse dependencies that are now broken. So if app A uses lib B directly which uses lib C directly, and lib C got updated, revdep-rebuild will discover if the new C is incompatible with the current B. Re-emerge B and it usually just manages to do the right thing. Weird issues often crop up when you have plug-in modules that are loaded dynamically at runtime. Revdep-rebuild can't find these as they don't show up in ldd, the app itself figures out what modules it wants to load then tries, so if something is broken there, well you find that out when you run the app. emerge -e world is the only way I know to to fix these things with any certainty. Binary distro by the way usually don't have this problem happen to them, because with those lib C doesn't suddenly get ripped out underneath B and replaced ;-) -- Alan McKinnon alan.mckinnon@gmail.com