Akregrator starts automatically in Feisty

Bug #82594 reported by Scott Kitterman
8
Affects Status Importance Assigned to Milestone
kdepim (Ubuntu)
Fix Released
Medium
Rich Johnson

Bug Description

Binary package hint: kdepim

Step to reproduce:

1. Update to latest Feisty version of kdepim
2. Restart the system
3. Notice Akgregator running

Trying to stop Akgregator results in all of kdepim being stopped. There does not appear to be a way to prevent this new behaviour.

This clutters the system and uses up additional memory, CPU, and bandwidth. Akregator ought not be imposed on people that don't want it. RSS feeds, while popular, are not really a core PIM function.

Revision history for this message
John Vivirito (gnomefreak) wrote :

I can confirm this as i didnt have kdepim installed and Akgregator doesnt run until you start it. I than installed kdepim for this bug and Akgregator runs without starting it. They only way i have found to get by this is to remove kdepim.

Changed in kdepim:
status: Unconfirmed → Confirmed
Revision history for this message
Anthony Mercatante (tonio) wrote :

I just tested and I can't confirm...
Installed kdepim, created a new user, and logon with it, no akregator.
I also checked at the /usr/share/autostart files eventually installed by kdepim or its deps, nothing related to akregator...

Revision history for this message
Scott Kitterman (kitterman) wrote :

I did some additional testing and it doesn't happen every time.

So far, if I start KDE and then start Kontact, I don't get akregator, but if I leave Kontact open and restart the computer so that Kontact starts automatically on login to KDE, then akregator starts.

Changed in kdepim:
importance: Undecided → Medium
Revision history for this message
Scott Kitterman (kitterman) wrote :

Still occurs with the test version of kdepim_3.5.6-0ubuntu7.

Revision history for this message
Rich Johnson (nixternal) wrote :

This only occurs for me if I have KDE save the state when I log off and Akregator is running. If I don't have Akregator running then it doesn't start up automatically. There is another trick by the way that I just noticed in the latest KDEPIM packages that I hadn't really paid attention to before. This is in Hardy with KDE 3.5.9 by the way.

In Akregator settings, you can set the 2 following options to prevent the behavior you want, they are:

Uncheck 'Show tray icon'
Uncheck 'Fetch all feeds on startup'

This totally prevents what you are referring to from happening. You can keep the tray icon, that is nothing, but unchecking 'Fetch all feeds on startup' prevent Akregator from doing anything, therefor not acting the way you have noticed in the past.

If you feel this is still an issue with 3.5.9, I urge you to go ahead and reopen this report. If I have made a mistake in this assumption I apologize ahead of time. Thank you!

Changed in kdepim:
assignee: nobody → nixternal
status: Confirmed → Fix Released
Revision history for this message
Scott Kitterman (kitterman) wrote :

Nope. Same behaviour for me with 3.5.9. Start Kontact (no Akregator). Reboot. Kontact starts and Akregator is running. That's not right.

Changed in kdepim:
status: Fix Released → Confirmed
Revision history for this message
Rich Johnson (nixternal) wrote :

OK, if I have the icon showing set in my configs, then yes, I can confirm the icon shows up after logging back in. However, setting it to not check doesn't fire akregator for me, it will not check until I click on one of the buttons. I even ran ps and top to see if it started up and it didn't, not until I clicked the download button did I briefly see akregator fire in both top and with a quick ps. Need to locate an upstream report and hope this gets fixed for KDE 4.1 as they stopped all work on the KDE 3 branch of Akregator unless of course it is a CRASH bug.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Is this still a problem in Kubuntu 8.10?

Changed in kdepim:
status: Confirmed → Incomplete
Revision history for this message
Rich Johnson (nixternal) wrote :

I am marking this fixed because it is no longer happening for me in Jaunty or Intrepid with KDE 4.2.

Changed in kdepim:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.