KDE 4.1.1 Upadate Checkerboard Problem

[mingus725]

It's the Qt/44 repo that's needed.

I doubt if you'll get much traction on the KDE Runtime request. The 4.1 repo is Factory; there is on-going development so there is always the risk of something being (temporarily) broken. Of course, as you found, overlooking the dependencies will break something.

[sosaudio1]

Originally Posted by mingus725

It's the Qt/44 repo that's needed.

I doubt if you'll get much traction on the KDE Runtime request. The 4.1 repo is Factory; there is on-going development so there is always the risk of something being (temporarily) broken. Of course, as you found, overlooking the dependencies will break something.

Yeah true but the bad thing is...the dep issue was only flagging for the runtime....

OK so next question....Is this the right repo for the latest 4.1.1 KDE? or is this the bleeding edge? or is this the stable repo?

Thanks for being quick!!!! You guys all rock!!!

Rich

[Psquared]

Originally Posted by sosaudio1

So maybe one day I will learn to listen to KDE and YaST when the dependency issues jump out at me...LOL I sat there for a good uh...30 seconds and then say....ehh what the heck...that'll teach me LOL...

OK but on the flip side of this, is there a way we could get the pkg managers to set up a dependency to where when KDE Runtime is not going to be updated it throws a flag?

One more question....

Resolve the repo addy. Is it QT44 or is it KDE:QT?

If there are two we need to know the correct one before delving into a possible dependecncy hell.

I love openSuse!!!!!

L8R
Rich

Ehhh... don't feel bad. I sat there and looked at the big Red Astericks warning me about dependency issues with QT4 and decided to ignore and update anyway. (And I've been fooling around with Linux for 4 years!!)

However, on my machine I haven't logged off and logged back in so I can do the zypper update thing and all should be well. (I hope)

Funny I came on here specifically for this problem and found this thread which explains what happened -- first go around.

I swear that's the first time I did a search and came up with a thread with the solution the first time.

[sosaudio1]

LOL Good stuff...

On a related note...are we posilutely absotivly on the url for the update for Qt????

If you look here it shows the KDE:QT non 44 repo....

I have updated and I have a sys that works...but like someone else said, no panels no desktop icons/widgets, wrong wallpaper...it was like someone did a reinstall removed my kde folders and such...

I can put icons and widgets back but now there are no labels to what they are...just icons...properties tells me what they are...no name under the icon...

So to go back to the other question...I have been to both URL's what is the diff between the two repos??

Rich

[Prexy]

I used the non-QT44 repo because that was the last post in the other thread - no one contradicted it. There were dependency problems with a couple (2 or maybe 3) apps that I use rarely or not at all. I told yast to not update them. A couple of repos were not accessible. They had nothing to do with this issue, but I said skip the problem updates.

Bottom line is: the non-QT44 repo worked fine for me; no checkerboard, no lost settings.

[mingus725]

I set up the KDE:QT repo first, and still had the dependency problem. Then I saw the QT/44 repo, added that, and dependencies resolved. I checked before the update in the summary listing and it showed that QT/44 was the upgrade source. I was surprised because the initial dependency error was on libqt4-x11-4.4.1, which KDE:QT satisfies.

Usually it's not worth the bother to wrack one's brain figuring out these discrepancies. This is development, after all, and so everything is always in flux. Even the dependencies can't be 100% guaranteed as correct - note that the plasma updates were allowed without the necessary KDE base and runtime libraries.

One thing I don't think has been clear for many is that the 4.1 repo ref'd on the KDE4 page and sourced in the 1-click, is not static. It is not a frozen 4.1 release. It is continually updated, and while most of the time it is in sync with itself, not always. Like today.

Having said that, I have been updating 4.1 with every new wave of changes, 2-3 times a week. I've had a few individual package dependency issues, but this is the first time a major dependency was missed with a serious consequence. YMMV.

[Havoc65]

you know i had the same problem with kde 4.1.1 and resloved it by all the solutions here on the forums, but my problem was i use konsole to update my 4.1.1 and didn't get any dependency issues so my question is what is the best command to use to update your system in konsole?
i've been using zypper up -t package

[mingus725]

Originally Posted by Havoc65

you know i had the same problem with kde 4.1.1 and resloved it by all the solutions here on the forums, but my problem was i use konsole to update my 4.1.1 and didn't get any dependency issues so my question is what is the best command to use to update your system in konsole?
i've been using zypper up -t package

AFAIK zypper should be fine. Dependencies are built into the packages. So YaST and zypper will both miss the dependencies if they aren't properly built in the first place, as happened today.

[Psquared]

zypper would not work for me so I added the QT44 repo in Yast and then updated. I now have a working KDE4.1.1 system and my wireless has been restored.

I still have this weird problem in FF in KDE that is not present in Opera in KDE or FF in Gnome. It's the disappearing checkmarks on webmail such as google or hotmail. If I place an "x" in a box to delete particular email or move it, the "x" does not appear until I click outside the box somewhere. I've tried it with compositing on and off. Makes no difference. I don't have Compiz-Fusion installed.

I like KDE better than Gnome because of the plasmoids and this isn't a huge issue, but it would be nice to know what is causing it.

[Sagemta]

OK,
I have the QT repos installed not the QT44.
So for best results should I install QT44 alongside the QT?