First, I know 2.2.2 is still beta so I expect everything to not work properly just yet. I've tried to find bug-reports related to this but can't find any, and the problem is so conspicuous that I find it hard to believe no one else would have noticed it.

Anyway, what happens is that the context view is completely empty except for the background wallpaper, and Amarok refuses to let me add the applets I want there. I'm using a package from a personal openSUSE build-service user, so it may be a packaging error but I can't be sure. Everything else seems to work though.

So, my question is: is this a known problem or should I file a bug for it (not sure exactly which revision it is. The package manager only says 20100108 which may be either the build-date or the checkout-date)?

That sounds like a packaging issue, because Amarok can't find the contextview and it's plugins, which need to be installed to your KDE prefix (wherever that is). You can also try running kbuildsycoca4 to see if kde will pick up your new files.

What you are using is a build from trunk, which is already beyond 2.2.2.

This was a bug in the code shortly after we re-opened trunk and should be solved with the next checkout. It definitely is corrected here in 2.2-git.

Mamarok wrote:What you are using is a build from trunk, which is already beyond 2.2.2.

How do you know? By the date-only? If so, when was trunk frozen for the 2.2.2 release?

I guess I must have read the description and/or version-number wrong then, because I thought it was a snapshot of what was to become 2.2.2.

Oh well. Guess that should teach me to not be as impatient as I usually am...not to mention checking that my backup WORKS before I update...since I can't downgrade to 2.2.1. It claims my database is too new, and I get CRC errors on the backup...

Well, for the time being I've decided to just turn off the context view (it is, after all, kinda useless without any applets...) and lock the amarok-package to avoid a further upgrade of the database. As soon as 2.2.2 final I'll check if the trunk database can be used in it, and if it can't: well, I'll probably continue using trunk instead since I don't really feel like starting afresh.

Or can the database be downgraded to an earlier version somehow?

lfranchi wrote:That sounds like a packaging issue, because Amarok can't find the contextview and it's plugins, which need to be installed to your KDE prefix (wherever that is). You can also try running kbuildsycoca4 to see if kde will pick up your new files.

Hm. All of my amarok-related .so files are in /usr/lib64/kde4 together with the rest of kde-specific files such as krunner-plugins and plasma-applets, so it really should be able to locate the contextview and it's plugins.

Which .so file would be the main one? I see a couple of dataengines and applets (among other things) but I can't see one that sticks out as being the contextview itself. At a guess I would say it is amarok_containment_vertical.so. Is that correct?

Kryten2X4B wrote:

Mamarok wrote:What you are using is a build from trunk, which is already beyond 2.2.2.

How do you know? By the date-only? If so, when was trunk frozen for the 2.2.2 release?

By the build date. Tagging was on January 6th and your build says 8th, so you have a checkout of git that is post 2.2.2.

Kryten2X4B wrote:Well, for the time being I've decided to just turn off the context view (it is, after all, kinda useless without any applets...) and lock the amarok-package to avoid a further upgrade of the database. As soon as 2.2.2 final I'll check if the trunk database can be used in it, and if it can't: well, I'll probably continue using trunk instead since I don't really feel like starting afresh.

This doesn't seem logical to me, since your package is already beyond 2.2.2 final. Just try the next checkout, as I said, that is already fixed. It was actually fixed about 30 minutes after the commit causing it, you just had some bad luck the checkout was done at that time. I guess it is automated and the packagers did not check it.

If you really want to use Amarok 2.2.2, you will need to remove that package, reinstall Amarok and do a fresh collection scan, there is no support for downgrading.

Hi.
I'm using Amarok 2.2.2.90. I know, that's beta, but I thought it'll be go to say something about it.

First of all: as Kryten2X4B said: "context viewer" doesn't work for me since 2.2.2. I've install it from sources, then from packages, but still it doesn't work. So I figured maybe the new one will work properly, but it showed up, the viewer doesn't show a thing.

So I wonder if it's a problem with amarok (seems not to be, 'cause should be fixed as Mamarok said), or is the problem with KDE, or something is wrong with openSUSE.

Now should I post a bug, or just paste some debug info here, maybe I don't see something obvious.

PS.
I've compiled it without this modules:
libgpod
curl
loudmouth
which I found useless.

with regards
Rafał.

filozof wrote:Hi.
So I wonder if it's a problem with amarok (seems not to be, 'cause should be fixed as Mamarok said), or is the problem with KDE, or something is wrong with openSUSE.

There does indeed seem to be some issue with the openSUSE package. We've had several users (all openSUSE) with the same issue.

Could you do us a favor, and ask the openSUSE packagers (IRC, forums, etc) about this?

Sure I can, but still it seems to be some Amarok's problem to, 'cause now I use version, that I compiled myself.

Anyway, I ask the packagers and post here if I know something new.

Thanks.

markey wrote:There does indeed seem to be some issue with the openSUSE package. We've had several users (all openSUSE) with the same issue.

The current package in KDE4_factory works though (2.2.90). The problem I had earlier was caused by, as far as I can tell, a build from a personal repo which may have been either a flawed build or as suggested by Mamarok, a check-out from git at the wrong time).

However, that build changed something in the config-files. So when I switched to another amarok-package, even the final version of 2.2.2 refused to utilize the context view. At a hunch, I moved the config-files out of the way and started from scratch .

So, to those with this problem using 2.2.2 final or later I'd suggest to do this:

1. Quit amarok if it's running.
2. Make a backup of the three amarok-files in .kde/share/config
3. Make a backup of .kde/share/apps/amarok
4. Remove the three amarok-files in .kde/share/config
5. Start Amarok and see if the default context-view applets are in place.
6. If they are, configure which folders should be included in the collection. The database and all statistics should remain the same.
7. Play something rated/played before and see if the database remembers that.
8. If it does remember that, configure the rest of Amarok to your liking.

@Kryten2X4B
You are the good among men.
It worked.
The thing was, that in config file were some coordinates for panels. In the new file there's no sign after that.

Thanks for that.
Regards
Rafał.

PS.
Is it possible to mark the post as solved, if so please do