Comment 15 for bug 827030

It is unlikely that anyone who is subscribed to this bug has tried a clean reinstall with the packages from raring (I certainly haven't), since if they had, they would probably have reported the result to this bug thread. So I presume that what you (Kai Mast) really mean is "please try again with raring packages"?

That's all very well, only up to now, the only action from maintainers has been to suggest trying the latest version (resp. 11.10, 12.04, 12.10 and now 13.04), and none has addressed the precise description of the problem, nor the apparent error in the location of the startup file. That gives me no confidence that the original bug report has been understood, or that when various people have said "it works OK for me", the "it" is the same "it" as in the report, namely Rygel autostarting on login (for example, "it" could also mean "system instance of Rygel starting on boot").

Since it hasn't worked before on four occasions, and since the desktop file is still apparently in the wrong place in the raring package of Rygel, I see no reason to try again at least until I've installed raring (which I will do when it's released), when it will be just a moment's work. On the other hand, it would be nice to see the bug fixed in raring, so if a maintainer would like actually to address the report, rather than just saying "it works for me, try the latest packages", I'd be happy to perform further experiments.

Let me be clear: the suggestion to simply try the latest packages is not in itself a bad idea, and often has a place. The difference in this bug is that the suggestion has already been made (without success) four times, while no attempt seems to have been made to look at a diagnosis of and partial solution to the actual problem.