kpackagekit's sister

dth2 · November 1, 2011, 9:43pm

Like many I suspect I always uninstall kpackagekit. As I find it cloggs up my system on starting-up, takes too long and isn’t very good.

When I did an factory update to rc1 yesterday I ended up with it’s new friend (which is much the same) called ‘apper’. You’ve been warned!

nrickert · November 1, 2011, 9:58pm

I just disable the startup of kpackagekit in the service manager (Personal Settings → Startup and Shutdown). That seems to be sufficient.

DenverD · November 2, 2011, 8:47am

On 11/01/2011 10:06 PM, nrickert wrote:
>
> I just disable the startup of kpackagekit

yes that sounds great…but, do we expect all new comers to be born
knowing to do that??

why can’t this be fixed or removed from the distro by the devs??

i can see no good reason to continue to allow the noobs to KILL their
system just because package kit (and now ‘apper’ ?) is upstream broken
when meshed with YaST…

the least they could do is run a script in the first update to “just
disable the startup of kpackagekit”…

this is pure madness!

perhaps the devs need a few thousand bug inputs?

–
DD
openSUSE®, the “German Automobiles” of operating systems

lwfinger · November 2, 2011, 3:17pm

On 11/02/2011 02:47 AM, DenverD wrote:
> On 11/01/2011 10:06 PM, nrickert wrote:
>>
>> I just disable the startup of kpackagekit
>
> yes that sounds great…but, do we expect all new comers to be born knowing to
> do that??
>
> why can’t this be fixed or removed from the distro by the devs??
>
> i can see no good reason to continue to allow the noobs to KILL their system
> just because package kit (and now ‘apper’ ?) is upstream broken when meshed with
> YaST…
>
> the least they could do is run a script in the first update to “just disable the
> startup of kpackagekit”…
>
> this is pure madness!
>
> perhaps the devs need a few thousand bug inputs?

As you note, it is being worked on. Why don’t you fix it if it bothers you so much?

Romanator · November 2, 2011, 5:28pm

You know the drill. The more people test “apper” and submit bug reports. We can have it ready for 12.1 GM

Most likely if you update to the final release, kpackagekit will get removed and replaced by apper. Yes?

DenverD · November 2, 2011, 7:35pm

On 11/02/2011 03:17 PM, Larry Finger wrote:
> As you note, it is being worked on. Why don’t you fix it if it bothers
> you so much?

believe me! i wish i had the patience to learn programming…

no, i can’t fix it…but, it doesn’t actually bother me at all
(directly) because i long ago deleted kpackage kit…but, we do get a
fair number of new guys whose first trouble post here (if not wireless)
is something is blamo due to kpackagekit suggesting 300 updates or
whatever…

and, it is kinda embarrassing (to me) to say disable it, it broken,
known broken since release and though it affects every new user it is
still not fixed…but, hang on because someone is working on adding
another bell, whistle, winky blinky or . . .

–
DD
openSUSE®, the “German Automobiles” of operating systems

Sagemta · November 2, 2011, 8:53pm

Like so many here I just disable the thing. However until today I didn’t know it could be deleted I thought I was stuck with it.
Thanks for the info guys!

Cloddy · November 2, 2011, 9:49pm

On Wed, 02 Nov 2011 16:36:05 +0000, Romanator wrote:

> Most likely if you update to the final release, kpackagekit will get
> removed and replaced by apper. Yes?

Apper is only a KDE front-end to kpackagekit so I don’t see it being a
total replacement.

–
Graham Davis, Bracknell, Berks.
openSUSE 11.4 (64-bit); KDE 4.7.2; AMD Phenom II X2 550 Processor;
Video: nVidia GeForce 210 (using nVidia driver);
Sound: ATI SBx00 Azalia (Intel HDA); Wireless: BCM4306

martin_helm · November 2, 2011, 10:21pm

Cloddy wrote:
> Apper is only a KDE front-end to kpackagekit so I don’t see it being a
> total replacement.
>
>
kpackagekit is the kde frontend to packagekit, so how can apper be a kde
frontend to another kde frontend? Just curious.

dth2 · November 2, 2011, 10:32pm

apper does the same thing as kpackagekit. the only difference i noticed (in the brief period that it was installed on my system) was that when it runs in the background checking for updates and blocking yast - when you ask it to quit it does.

creatura85 · November 3, 2011, 7:51am

For me apper under openSUSE 11.4 was trouble, eats a lot of ram and cpu. When i did install kpackagekit i noticed a VERY SMALL drop in resources used by it, so kpackagekit is for me the best “worst” thing

hcvv · November 3, 2011, 11:36am

My personal opinion is the best (not worst at all) thing is to use the admin tool that is one of the great things of openSUSE: YaST. I do not understand the need for something different. And thus I do not see why they, apperently being somethimg coming with KDE, aren’t remmoved from the openSUSE distribution as superfluous and diverting (new) users from the main task of our main admin tool: Software management.

Just my 2 cents.

martin_helm · November 3, 2011, 1:56pm

hcvv wrote:
> My personal opinion is the best (not worst at all) thing is to use the
> admin tool that is one of the great things of openSUSE: YaST. I do not
> understand the need for something different. And thus I do not see why
> they, apperently being somethimg coming with KDE, aren’t remmoved from
> the openSUSE distribution as superfluous and diverting (new) users from
> the main task of our main admin tool: Software management.
>
> Just my 2 cents.
>
+1 for yast

martin_helm · November 3, 2011, 2:11pm

martin_helm wrote:
> +1 for yast
>
To be a bit more verbose. The very first time I saw kpackagekit instead of
the old updater applet I was very surprised why we have some updating
feature which bypasses yast, while yast is one of the strongest points of
openSUSE from my point of view.
Ok, if you have something made in a more generic way like kpackagekit, which
works the same on all distros and can handle the different package
management systems, why not.
But fact is it never worked as it should. And to introduce a buggy feature
to replace an allmost perfect system (YOU - which is of course still there
but without a notifier or applet) is something I will never understand.

DenverD · November 3, 2011, 3:16pm

On 11/03/2011 11:46 AM, hcvv wrote:
>
> superfluous and diverting (new) users from
> the main task of our main admin tool: Software management.

+1

–
DD

Romanator · November 3, 2011, 4:31pm

I really like Yast and zypper.

Then, there’s the introduction of an Ubuntu-like Software Center over the next two versions of openSUSE.
That’s three ways to install, remove and update. Not sure about the Software Center.

robin_listas · November 3, 2011, 4:33pm

On 2011-11-02 08:47, DenverD wrote:
> perhaps the devs need a few thousand bug inputs?

They know it is bad, so they wrote a new one. Why don’t you give it the
benefit of the doubt and try it, before removing it?

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

Romanator · November 3, 2011, 4:38pm

You are working with an older rpm. A newer one will be released in Factory with fixes.

DenverD · November 3, 2011, 6:15pm

On 11/03/2011 04:33 PM, Carlos E. R. wrote:
> They know it is bad, so they wrote a new one. Why don’t you give it the
> benefit of the doubt and try it, before removing it?

did they put it though to users as an update?

–
DD
openSUSE®, the “German Automobiles” of operating systems

martin_helm · November 3, 2011, 6:25pm

DenverD wrote:

> On 11/03/2011 04:33 PM, Carlos E. R. wrote:
>> They know it is bad, so they wrote a new one. Why don’t you give it the
>> benefit of the doubt and try it, before removing it?
>
> did they put it though to users as an update?
>
I updated some hours ago to 12.1 RC2 and see now that kpackagekit
disappeared from my machine and apper is there. I do not disable it and will
see how it behaves.