8:12 a.m.
After updating from f12 + kde-testing -> f13, kdm is having troubles.
For example:
Cannot load library /usr/lib64/kde4/kcm_keyboard_layout.so
(libxklavier.so.15: cannot open shared object file)
11 a.m.
Neal Becker wrote:
After updating from f12 + kde-testing -> f13, kdm is having
troubles.
For example:
Cannot load library /usr/lib64/kde4/kcm_keyboard_layout.so
(libxklavier.so.15: cannot open shared object file)
Following a full yum update, these problems are gone.
Remaining problems:
* nm-applet does not start automatically (used to on f12)
* pulseaudio does not start automatically - same thing I reported under F12
* fonts all look different - not really a kde thing.
11:41 a.m.
On Sat, 29 May 2010, Neal Becker wrote:
Remaining problems:
* nm-applet does not start automatically (used to on f12)
knetworkmanager is used by default in f13 instead.
If you want to re-enable nm-applet, see
http://fedoraproject.org/wiki/KDE/Using_nm_applet_instead_of_knetworkmanager
-- Rex>
1:07 p.m.
On Sat, 2010-05-29 at 11:41 -0500, Rex Dieter wrote:
On Sat, 29 May 2010, Neal Becker wrote:
> Remaining problems:
>
> * nm-applet does not start automatically (used to on f12)
knetworkmanager is used by default in f13 instead.
I also updated from F12 to F13. nm-applet is not started, but the
network is up (NetworkManager is running). Also, knetworkmanager was not
installed during the update process.
I'm coming to the conclusion that "update" doesn't mean what I thought.
Instead of meaning "install new stuff and remove old stuff which it
functionally replaces" it seems to mean "replace already installed stuff
with the newest versions of the same stuff". I'm not saying this is
always wrong, it's just not what I expected.
poc
4:09 p.m.
On 05/29/2010 03:07 PM, Patrick O'Callaghan wrote:
On Sat, 2010-05-29 at 11:41 -0500, Rex Dieter wrote:
>
> On Sat, 29 May 2010, Neal Becker wrote:
>
>> Remaining problems:
>>
>> * nm-applet does not start automatically (used to on f12)
>
> knetworkmanager is used by default in f13 instead.
I also updated from F12 to F13. nm-applet is not started, but the
network is up (NetworkManager is running). Also, knetworkmanager was not
installed during the update process.
I'm coming to the conclusion that "update" doesn't mean what I
thought.
Instead of meaning "install new stuff and remove old stuff which it
functionally replaces" it seems to mean "replace already installed stuff
with the newest versions of the same stuff". I'm not saying this is
always wrong, it's just not what I expected.
How did you upgrade? With yum or anaconda?
poc
_______________________________________________
kde mailing list
kde(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/kde
New to KDE4? - get help from http://userbase.kde.org
5:11 p.m.
On Sat, 2010-05-29 at 18:09 -0300, Patrick Boutilier wrote:
> I'm coming to the conclusion that "update"
doesn't mean what I
thought.
> Instead of meaning "install new stuff and remove old stuff which it
> functionally replaces" it seems to mean "replace already installed
stuff
> with the newest versions of the same stuff". I'm not saying this is
> always wrong, it's just not what I expected.
How did you upgrade? With yum or anaconda?
Anaconda.
poc
4:48 p.m.
On 05/29/2010 01:07 PM, Patrick O'Callaghan wrote:
On Sat, 2010-05-29 at 11:41 -0500, Rex Dieter wrote:
>
> On Sat, 29 May 2010, Neal Becker wrote:
>
>> Remaining problems:
>>
>> * nm-applet does not start automatically (used to on f12)
>
> knetworkmanager is used by default in f13 instead.
I also updated from F12 to F13. nm-applet is not started, but the
network is up (NetworkManager is running). Also, knetworkmanager was not
installed during the update process.
I'm coming to the conclusion that "update" doesn't mean what I thought.
After doing fedora version upgrades, it's always a good idea to refresh
the default pkg list via
yum groupinstall kde-desktop
(repeat process for any installed desktops) to ensure you have all the
newest, default package set installed.
-- Rex
7:26 a.m.
Rex Dieter wrote:
After doing fedora version upgrades, it's always a good idea to
refresh
the default pkg list via
yum groupinstall kde-desktop
(repeat process for any installed desktops) to ensure you have all the
newest, default package set installed.
I always follow your advice ...
so I did the above, and found it installed 100MB (70 packages).
But I don't understand why?
Why didn't "yum update" (which I run every couple of days) find them?
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
8:39 a.m.
On Sun, May 30, 2010 at 2:26 PM, Timothy Murphy <gayleard(a)eircom.net> wrote:
Rex Dieter wrote:
> After doing fedora version upgrades, it's always a good idea to refresh
> the default pkg list via
> yum groupinstall kde-desktop
> (repeat process for any installed desktops) to ensure you have all the
> newest, default package set installed.
I always follow your advice ...
so I did the above, and found it installed 100MB (70 packages).
But I don't understand why?
Why didn't "yum update" (which I run every couple of days) find them?
The groupinstall installs a bit more as what is in a default
installation. Or did you mean it updated this 70 packages?
--
LG Thomas
Dubium sapientiae initium
10:19 a.m.
Thomas Janssen wrote:
>> After doing fedora version upgrades, it's always a good
idea to refresh
>> the default pkg list via
>> yum groupinstall kde-desktop
>> (repeat process for any installed desktops) to ensure you have all the
>> newest, default package set installed.
>
> I always follow your advice ...
> so I did the above, and found it installed 100MB (70 packages).
> But I don't understand why?
> Why didn't "yum update" (which I run every couple of days) find them?
The groupinstall installs a bit more as what is in a default
installation. Or did you mean it updated this 70 packages?
I thought at first it had updated the packages,
because it said that it was updating them,
but now I see that they were actually installed,
and that yum always says it is updating, even when it isn't ...
But "yum grouplist" actually said this group was installed,
after installing from the KDE Live CD.
Maybe that is a quirk of the KDE Live CD?
It claimed to have installed a bizarre selection of groups.
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
8:53 a.m.
On 05/30/2010 07:26 AM, Timothy Murphy wrote:
Rex Dieter wrote:
> After doing fedora version upgrades, it's always a good idea to refresh
> the default pkg list via
> yum groupinstall kde-desktop
> (repeat process for any installed desktops) to ensure you have all the
> newest, default package set installed.
I always follow your advice ...
so I did the above, and found it installed 100MB (70 packages).
But I don't understand why?
Why didn't "yum update" (which I run every couple of days) find them?
at least 2 reasons.
1. if you installed via fedora kde live image, the live cd is only a
subset of what is included in the full kde-desktop group (to make it cd
sized)
2. if you do a fedora release upgrade, e.g. fedora 12 -> fedora 13, the
default packageset sometimes changes a little. One of the changes
highlighted in this thread was the addition of installing and using
knetworkmanager (by default) in f13.
-- Rex
1:46 p.m.
On 05/30/2010 09:26 AM, Timothy Murphy wrote:
Rex Dieter wrote:
> After doing fedora version upgrades, it's always a good idea to refresh
> the default pkg list via
> yum groupinstall kde-desktop
> (repeat process for any installed desktops) to ensure you have all the
> newest, default package set installed.
I always follow your advice ...
so I did the above, and found it installed 100MB (70 packages).
But I don't understand why?
Why didn't "yum update" (which I run every couple of days) find them?
"yum update" only updates installed packages. It won't install new
packages unless the updated packages have new dependencies that require
new packages to be installed.
5072
days inactive
5073
days old
11 comments
7 participants
participants (7)
-
Neal Becker -
Patrick Boutilier -
Patrick O'Callaghan -
Rex Dieter -
Rex Dieter -
Thomas Janssen -
Timothy Murphy