Aaron Griffin wrote:

On Thu, Jan 22, 2009 at 6:19 PM, Dan Vratil wrote:

...

Also, could please someone confirm me, that KDE 4.1 freezes when updating? After some package was updated, Plasma went frozen and I had to shutdown the X server and finnish the update from console.

This could be serious. If, for some reason, you are updating something like bash and dependent libraries at the same time, the upgrade could be aborted when bash is updated but dependent libs are not, breaking bash. It's probably not likely, but is a possibility (it did happen to be once a long time ago)

Isn't it usually recommended to be outside your DE when doing a major DE upgrade. Allan

Aaron Griffin wrote:

On Thu, Jan 22, 2009 at 6:19 PM, Dan Vratil wrote:

...

Also, could please someone confirm me, that KDE 4.1 freezes when updating? After some package was updated, Plasma went frozen and I had to shutdown the X server and finnish the update from console.

This could be serious. If, for some reason, you are updating something like bash and dependent libraries at the same time, the upgrade could be aborted when bash is updated but dependent libs are not, breaking bash. It's probably not likely, but is a possibility (it did happen to be once a long time ago)

Dunno if I'm being superstitious or not, but I always make sure to not be running an app when pacman goes to update it. (e.g., exit X when updating X or KDE, shut down a daemon like cups or ssh when updating it, dropping to single user mode when updating the kernel, etc.) DR

Nicolas Bigaouette wrote:

I installed it (and with everything from testing... is there a way to _just_ update testing/kde and not all packages??).

Maybe: pacman -S kde ? DR

So I checked in systemsettings under "Keyboard & Mouse/Global Shortcuts" but "KDE Components" is empty... I cannot change de shortcuts... I tried importing the default kde4 one or resetting to defaults, but did not changed anything... 2009/1/23 Nicolas Bigaouette

I installed it (and with everything from testing... is there a way to _just_ update testing/kde and not all packages??). I switched to run level 3, backed up my ~/.kde4, updated, then switched back to rl 5.

It looks really nice! Here are my comments: 1) Strigi is said to be suspended, but I can hear my HD going crazy... Is it really suspended? nicolas 17488 1.6 0.7 320124 27600 ? SNl 12:06 0:06 /usr/bin/nepomukservicestub nepomukstrigiservice

2) Theme is dark... See http://nbigaouette.inrs-emt.homelinux.net/linux/arch/kde42.png The menu is unreadable... Its hard also on the task bar. But the menu is really bad.

3) Alt-Tab, Alt+F1, Alt+F2, ctrl+alt+left/right stopped working.

The rest seems _really_ nice! :)

2009/1/22 David Rosenstrauch

Aaron Griffin wrote:

...

...

On Thu, Jan 22, 2009 at 6:19 PM, Dan Vratil wrote:

...

Also, could please someone confirm me, that KDE 4.1 freezes when updating? After some package was updated, Plasma went frozen and I had to shutdown the X server and finnish the update from console.

This could be serious. If, for some reason, you are updating something like bash and dependent libraries at the same time, the upgrade could be aborted when bash is updated but dependent libs are not, breaking bash. It's probably not likely, but is a possibility (it did happen to be once a long time ago)

Dunno if I'm being superstitious or not, but I always make sure to not be running an app when pacman goes to update it. (e.g., exit X when updating X or KDE, shut down a daemon like cups or ssh when updating it, dropping to single user mode when updating the kernel, etc.)

DR

On Friday 23 January 2009 02:04:34 Pierre Schmitz wrote:

Am Freitag 23 Januar 2009 01:19:26 schrieb Dan Vratil:

...

Some of my old desktop settings (wallpaper, size of icons etc) were replace by KDE 4.2 default settings. But it's probably only about Plasma config, because Kopete, KMail and all other applications kept their settings.

Didn't you change the defaults of 4.1? In that case you'll get the new defaults. If not see next point. No, I was using my own wallpaper properly set via Desktop settings dialog, icons resized using configuration somewhere else (maybe some minor config was just modification of default settings). But it could be caused by the update I made from running DE. On the other hand - pacman does not touch ~/.kde4 folder, does it? It is only used by KDE. The change could be done automaticaly by KDE when I fist logged in after the update.

...

Also, could please someone confirm me, that KDE 4.1 freezes when updating? After some package was updated, Plasma went frozen and I had to shutdown the X server and finnish the update from console.

Never update KDE while it is running. 4.1 -> 4.2 is not a minor update and will break things when you try to update it while its still running.

...

There is also problem with plasmoids from AUR. After update, they didn't run so I tried to rebuilt them but because of some changes in KDE, any of them will compile, but it seems to be a problem in their source codes not in PKGBUILDs.

plasmoids are the only exception that I know of that have to be recompiled or updated for 4.2. Everything else should work fine.

That's pitty - wifi signal strength meter was my favourite and now it's not working :-) -- --------------------------------- Dan Vrátil progdan@progdansoft.com ICQ 249163429 Jabber progdan@jabber.cz Tel. +420 732 326 870

Please let me know of any problems during the upgrade. I think about collecting them for a samll upgrade guide.

Sir, if you do that, I will be eternally grateful. I have been awaiting 4.2 for quite a while, but am sort of anxious about the upgrade given the number of problems people have reported.

On Sunday 25 January 2009 22:09:02 Gilles CHAUVIN wrote:

On Fri, Jan 23, 2009 at 00:37, Pierre Schmitz wrote:

...

If you notice any regression, showstopper or problems during the update, please report them.

Ooops, sorry for the previous (incomplete) e-mail... :(

Hi,

While trying to add a Jabber account within Kopete I get a popup window saying "Cannot load the Jabber protocol plugin".

Am I the only one having this issue ?

Regards, Gilles.

Hi, same here, neither I can create Jabber account in Kopete. Using PSI, I can connect without any problems. Dan -- --------------------------------- Dan Vrátil progdan@progdansoft.com ICQ 249163429 Jabber progdan@jabber.cz Tel. +420 732 326 870

On Sunday 25 January 2009 23:54:42 Andrea Scarpino wrote:

2009/1/25 Dan Vratil :

...

On Sunday 25 January 2009 22:09:02 Gilles CHAUVIN wrote:

...

Hi,

While trying to add a Jabber account within Kopete I get a popup window saying "Cannot load the Jabber protocol plugin".

Am I the only one having this issue ?

Regards, Gilles.

Hi, same here, neither I can create Jabber account in Kopete. Using PSI, I can connect without any problems.

Dan

Hi, jabber works for me with Kopete, none problems. I've 2 accounts, one on jabber.org, the other on talk.google.com.

Regards

Well, that's strange. Could it depend on arch? I'm running x86_64 system. When starting Kopete from terminal, it outputs this: Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. kopete(12348)/libkopete Kopete::PluginManager::loadPluginInternal: Unable to find a plugin named ' "" '! Calling appendChild() on a null node does nothing. Then, no more reports, even when trying to add Jabber account. Cheers, Dan -- --------------------------------- Dan Vrátil progdan@progdansoft.com ICQ 249163429 Jabber progdan@jabber.cz Tel. +420 732 326 870

2009/1/26 Dan Vratil :

When starting Kopete from terminal, it outputs this:

Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. Calling appendChild() on a null node does nothing. kopete(12348)/libkopete Kopete::PluginManager::loadPluginInternal: Unable to find a plugin named ' "" '! Calling appendChild() on a null node does nothing.

If I try to disable kde wallet I get the same messages but my jabber accounts still work -- Andrea `BaSh` Scarpino Arch Linux Developer

Am Sonntag 25 Januar 2009 22:09:02 schrieb Gilles CHAUVIN:

While trying to add a Jabber account within Kopete I get a popup window saying "Cannot load the Jabber protocol plugin".

Am I the only one having this issue ?

Could you try this with a new user (clean config)? Jabber seems to work here (even if Kopete is wuite bad for Jabber (no TLS support for example) -- Pierre Schmitz Clemens-August-Straße 76 53115 Bonn Telefon 0228 9716608 Mobil 0160 95269831 Jabber pierre@jabber.archlinux.de WWW http://www.archlinux.de

Hi, I've found where the problem was.... $ ldd /usr/lib/kde4/kopete_jabber.so | grep 'not found' libortp.so.5 => not found $ pacman -Q ortp ortp 0.14.0-1 $ pacman -Ql ortp | grep '\.so\.' ortp /usr/lib/libortp.so.7 ortp /usr/lib/libortp.so.7.0.0 $ pacman -Ss ortp testing/ortp 0.13.1-1 A Real-time Transport Protocol (RTP) library community/ortp 0.14.0-1 A Real-time Transport Protocol stack If I install ortp 0.13.1 it is now working. I guess this happened because, after I installed KDE 4.2 from [testing], I commented the [testing] repo in my /etc/pacman.conf. I guess pacman then updated ortp with the more recent version it found in [community]. The question here is.... Isn't [testing] supposed to be more up-to-date than the other repos ?! Cheers, Gilles.

On Mon, Jan 26, 2009 at 23:21, Andrea Scarpino wrote:

I don't see ortp-0.14 here[1], but I see 0.15 so I'm building and I'll put it to [testing].

ortp-0.14 comes from here http://aur.archlinux.org/packages.php?ID=8578 and seems to be included in the linphone tarball. Better use the latest version though :). Thanks. Cheers, Gilles.