Posting quickly as I'll be away for a couple of days. Live session on the BETA1. On startup when the desktop comes up I get a message about dbus and wicd having some kind of problem getting together. As vector I can't get wicd to run at all, after brief attempts. Logged out and back in as root - still get the error message but wicd will run and allow a wireless connection after being told the interface is eth1. Afraid I didn't record the exact text. Hmmm, will just have quick look for a wicd log. Nope, can't see anything relevant there right now. This is a ThinkPad z60m with i915 integrated graphics and Intel Corporation PRO/Wireless 2915ABG [Calexico2] wifi. So there may be some glitch around wifi connections and wicd. User permissions?

It would be nice if wicd could autoconfigure, ie pick up the wired and wireless interfaces and write them into its config as seen in prefs pane. wicd log presently shows lots of hunting about for an interface, wired eth0 not present or configured I think it was repeatedly. Believe I have seen this auto config done elsewhere.

When I try to start Inkscape on either of the two desktop computers, I get this:inkscape: error while loading shared libraries: libpoppler.so.12: cannot open shared object file: No such file or directory

I copied the library and symlink from my VL7 b2.1 partition and things are now working.

Do I remember correctly that we can expect K3B in the final release of VL7 Standard? I hope we can have a package *now* as I really miss K3B. I don't want any more of KDE than I need for K3B.

I've installed lots of packages and a few third-party programs and so far things are doing well on RC1.--GrannyGeek

I think our spanish translation in the installer maybe the problem................if you could try another install in english see if that goes right...........appreciate it

Thanks Vec, you were right, after i installed it in english the everything went right.

could someone else try to reproduce this? I don't see how a difference in the rendered strings could cause this when the underlying code is exactly the same. As a suggestion maybe try the keyboard layout in the provided test box to make sure all keys work as expected.