openSUSE Tumbleweed build 20130527.
Fresh clean install. First program that is a must is Google Chrome.
DLed RPM… Go to instal with Apper. and I get a unresolved dependency for LSB 4.0 right of the bat.
Pretty much a show stopper unless this can be brought in I won’t be testing Tumbleweed.
How to resolve?
Thanks Steven
On Fri 29 May 2015 04:06:01 AM CDT, FlameBait wrote:
openSUSE Tumbleweed build 20130527.
Fresh clean install. First program that is a must is Google Chrome.
DLed RPM… Go to instal with Apper. and I get a unresolved dependency
for LSB 4.0 right of the bat.
Pretty much a show stopper unless this can be brought in I won’t be
testing Tumbleweed.
How to resolve?
Thanks Steven
Hi
Is lsb installed? More likely a chrome issue with it’s dependencies or
maybe apper? Install with zypper and see if you get the same errors?
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.39-47-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
malcolmlewis Thanks.
I don’t know zypper but I have Lsb installed from yast2 now. It is not installed by default.
I added the Packman Factory Essentials and set it to 98 in the repos in yast2. It dragged in a bunch of other stuff when I installed smplayer.
Chromium was one of them. So Chrome should install with Apper I hope once yast lets go of it’s locks on the system.
Since this seem to be the place the people that do have decided to take openSUSE I want to see if it’s usable or if I’ll be shopping a new distro once 13.1 runs out of support.
Not hanging out on the forums at all and as you know just lurking in IRC.
So far Tumbleweed is not to bad or too buggy though. Tumbleweed doesn’t like my KVM.
I had to disable all energy saving and screen blanking and locking.
If I changed KVM focus and came back I had no display and no amount of keyboard mashing or mouse wiggling would bring it back.
Flailing my way around until I get to the KDE desktop settings I think I fixed that.
Peace.