trying to reply to your specific statements:
On Tue, 15 May 2012 02:06:01 +0530, Sven Burmeister
Did you not read the thread? It was about a specific error message and as I suspected zypper patch showed the same error. Packagkitd dies after some time if nothing calls it again. Just to be clear, there are bugs in all apps, including packagkit and apper.
i'm pretty sure that what basil c. experienced was not another zypper bug that may make the rounds now. i'm not running 12.1 very often these days, doing all my work on 12.2. there's a zypper & YAST bug there, too, but that may be something completely different. i've looked into the bug tracker re. that factory bug, but not into 12.1 bugs.
Yet blaming apper by default (as it was done here and has become a common habit on forums by people like Carlos) is completely useless.
it's useless for people trying to fix the bug, but for the user in this situation it enables him to use his packagemanagement system again. that's something. not everybody feels equally motivated to put time & energy into any bug that appears anywhere. in my opinion, the automatic apper reminding thing isn't required. since you obviously feel different, you should go ahead and help fix it -- but you can't expect people who aren't interested in the feature to help very much.
It hinders bugfixing and it demotivates devs that are not at fault etc.
well, if the recommendation to not use something that often doesn't work is evil, then i'm afraid that's what i am.
The only useful approach is to help people debugging and that way find out > where the bug is acutally at. That's why I asked to try zypper patch instead of zypper up in order to make sure it is actually a packagekit or apper bug.
just read the whole conversation again. it looks as if he got the option to try to kill packagekit, which he did, and then zypper patch could run. i still see the same bug, that packagekit, being called by apper, blocks access for other package management tools, and after it's asked to quit, via dialog or kill command, things work again. that's always been there, but a nuisance, so for those who don't care for apper, uninstalling is still the easiest way to solve the problem -- personally, not for the whole part of humanity that uses openSUSE or SLES/D. that's cold-hearted and uncaring, i know, but what to do. i've got limited time for this and i prefer to spend it on things that are important for me, too. -- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org