Akregator fails to fully close?

[bra|10n]

I have noticed when I close Akregator and then attempt to launch it again, Akregator fails to start. When it's first launched all is well but I suspect this is a case of 'Akregator is already running' though I don't receive any such prompt.

Ideas?

[SteveRiley]

Any clues if you start it from a Konsole? Here's mine...

steve@x1:~$ [B]akregator[/B]

{...starting...}

QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
steve@x1:~$ QPainter::begin: Widget painting can only begin as a result of a paintEvent
QPainter::translate: Painter not active
QPainter::setClipRect: Painter not active

{...running...}

steve@x1:~$ [B]ps -ef | grep akregator[/B]
steve     2167     1  6 20:33 pts/0    00:00:00 akregator
steve     2168  1253  0 20:33 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-steve/klauncherMT1254.slave-socket local:/tmp/ksocket-steve/akregatorXF2167.slave-socket
steve     2170  1253  0 20:33 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-steve/klauncherMT1254.slave-socket local:/tmp/ksocket-steve/akregatorhZ2167.slave-socket
steve     2171  1253  0 20:33 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-steve/klauncherMT1254.slave-socket local:/tmp/ksocket-steve/akregatorKP2167.slave-socket
steve     2172  1253  0 20:33 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-steve/klauncherMT1254.slave-socket local:/tmp/ksocket-steve/akregatorab2167.slave-socket
steve     2173  1253  0 20:33 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-steve/klauncherMT1254.slave-socket local:/tmp/ksocket-steve/akregatorVE2167.slave-socket
steve     2175  1749  0 20:33 pts/0    00:00:00 grep --color=auto akregator

{...closing...}

akregator(2167)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
akregator(2167)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
akregator(2167)/kdeui (kdelibs) KXMLGUIClient::~KXMLGUIClient: 0x1b9a6e0 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. 
akregator(2167)/kdeui (kdelibs) KXMLGUIClient::~KXMLGUIClient: 0x19a8ff0 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. 

{...stopped...}

steve@x1:~$ [B]ps -ef | grep akregator[/B]
steve     2177  1749  0 20:33 pts/0    00:00:00 grep --color=auto akregator

[bra|10n]

kubuntu@kubuntu-Aspire-5750:~$ akregator

{...starting...}

QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kubuntu@kubuntu-Aspire-5750:~$ ps -ef | grep akregator

{...running...}

kubuntu   1972     1  3 13:38 pts/1    00:00:01 akregator
kubuntu   1974  1364  0 13:38 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-kubuntu/klauncherMT1365.slave-socket local:/tmp/ksocket-kubuntu/akregatorXF1972.slave-socket
kubuntu   1976  1364  0 13:38 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-kubuntu/klauncherMT1365.slave-socket local:/tmp/ksocket-kubuntu/akregatorZb1972.slave-socket
kubuntu   1977  1364  0 13:38 ?        00:00:00 kdeinit4: kio_http [kdeinit] http local:/tmp/ksocket-kubuntu/klauncherMT1365.slave-socket local:/tmp/ksocket-kubuntu/akregatorEt1972.slave-socket
kubuntu   1978  1364  0 13:38 ?        00:00:00 kdeinit4: kio_http [kdeinit] http local:/tmp/ksocket-kubuntu/klauncherMT1365.slave-socket local:/tmp/ksocket-kubuntu/akregatorKP1972.slave-socket
kubuntu   1979  1364  0 13:38 ?        00:00:00 kdeinit4: kio_http [kdeinit] http local:/tmp/ksocket-kubuntu/klauncherMT1365.slave-socket local:/tmp/ksocket-kubuntu/akregatorbZ1972.slave-socket
kubuntu   1982  1364  0 13:38 ?        00:00:00 kdeinit4: kio_http [kdeinit] http local:/tmp/ksocket-kubuntu/klauncherMT1365.slave-socket local:/tmp/ksocket-kubuntu/akregatorEa1972.slave-socket
kubuntu   1984  1364  0 13:38 ?        00:00:00 kdeinit4: kio_http [kdeinit] http local:/tmp/ksocket-kubuntu/klauncherMT1365.slave-socket local:/tmp/ksocket-kubuntu/akregatorqV1972.slave-socket
kubuntu   1986  1364  0 13:38 ?        00:00:00 kdeinit4: kio_http [kdeinit] http local:/tmp/ksocket-kubuntu/klauncherMT1365.slave-socket local:/tmp/ksocket-kubuntu/akregatoraq1972.slave-socket
kubuntu   1989  1364  0 13:38 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-kubuntu/klauncherMT1365.slave-socket local:/tmp/ksocket-kubuntu/akregatorVs1972.slave-socket
kubuntu   1990  1364  0 13:38 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-kubuntu/klauncherMT1365.slave-socket local:/tmp/ksocket-kubuntu/akregatorhc1972.slave-socket
kubuntu   1991  1364  0 13:38 ?        00:00:00 kdeinit4: kio_file [kdeinit] file local:/tmp/ksocket-kubuntu/klauncherMT1365.slave-socket local:/tmp/ksocket-kubuntu/akregatorQb1972.slave-socket
kubuntu   1995  1916  0 13:39 pts/1    00:00:00 grep --color=auto akregator

{...closing...}

kubuntu@kubuntu-Aspire-5750:~$ QPainter::begin: Widget painting can only begin as a result of a paintEvent
QPainter::translate: Painter not active
QPainter::setClipRect: Painter not active
akregator(1972)/kdeui (kdelibs) KXMLGUIClient::~KXMLGUIClient: 0x19305c0 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. 
akregator(1972)/kdeui (kdelibs) KXMLGUIClient::~KXMLGUIClient: 0x15c7060 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes. 

{...stopped...}

ps -ef | grep akregator
kubuntu   1998  1916  0 13:41 pts/1    00:00:00 grep --color=auto akregator
kubuntu@kubuntu-Aspire-5750:~$

Identical.

I was looking in SystemMonitor before and I confirmed it was still running after I closed Akregator.
But since starting it from a Konsole it now behaves perfectly.
The only thing to note is at the moment there are no new feeds available if that should make any difference?

ADD:

A restart of the system is fine also. Don't know what starting from the konsole fixed but thanks. I'll keep my eye on it, fingers crossed.

[SteveRiley]

Don't know what starting from the konsole fixed but thanks.

And now, for my next trick...!

[bra|10n]

Ok, confirmed. Here is the message in a Konsole,

kubuntu@kubuntu-Aspire-5750:~$ akregator
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
unnamed app(4382) main: akregator is already running, exiting. 
kubuntu@kubuntu-Aspire-5750:~$

[SteveRiley]

SWAG... how are you exiting the program -- do you click the X button in the window, or do you choose File | Quit?

Technically speaking, the X button instructs the KWin to close the window, not to terminate the application. Now, in nearly all cases, these are equivalent operations, because applications should detect a window close and treat it as a termination. I wonder if something's messed up on your machine here. If you change your habit and use only File | Quit for Akgregator, does the problem persist?

[Snowhog]

I launched akregator from the CLI and then closed it with File > Close and this is what was left in the console:

akregator(22093)/kdeui (kdelibs) KXMLGUIClient::~KXMLGUIClient: 0x10582f0 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes.
akregator(22093)/kdeui (kdelibs) KXMLGUIClient::~KXMLGUIClient: 0xc5f2c0 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes.

I did not have my prompt. Had to press Ctrl+C to get the prompt back.

[SteveRiley]

Yep, I see the leak error messages, too, but am unable to duplicate bra|10n's problem on my computer.

[bra|10n]

SWAG... how are you exiting the program -- do you click the X button in the window, or do you choose File | Quit?

SWAG rofl,

Oh, I want that as my User title, "Contributing SWAG"

Well to answer your question, all manner of ways. Click X, Close from the titlebar or panel, but never Quit.

I will try Quit and see how that goes lol

[SteveRiley]

Oh, I want that as my User title, "Contributing SWAG"

Done