Bug 333254

Summary: Gwenview creates new process every time it is opened, old processes are not closed.
Product: [Applications] gwenview Reporter: Gavin77
Component: generalAssignee: Gwenview Bugs <gwenview-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: h6zb8-kdebugs20120801, myriam
Priority: NOR    
Version: 4.13.0 rc1   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In: 4.13.1
Sentry Crash Report:

Description Gavin77 2014-04-10 00:32:13 UTC
Viewing with the System Activity monitor I can see a process listed for every time I have opened Gwenview each using up approx 12-14 MB of ram. This is after exiting the app.

Reproducible: Always

Steps to Reproduce:
1. Open Gwenview
2. Use System Activity monitor and notice a new Gwenview process has been created.
3. Close Gwenview then open it again.  You will now have 2 processes.
4. Repeat step 3 and new processes will be created and they don't close causing them to stack up.
Actual Results:  
I now have multiple Gwenview processes running.

Expected Results:  
I should only have 1 instance running.

This is the terminal output when starting and then exiting the program.

gwenview
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
Bus::open: Can not get ibus-daemon's address. 
IBusInputContext::createInputContext: no connection to ibus-daemon 
gwenview(10608)/kdeui (kdelibs): Attempt to use QAction "edit_redo" with KXMLGUIFactory! 
gwenview(10608)/kdeui (kdelibs): Attempt to use QAction "edit_undo" with KXMLGUIFactory! 
gwenview(10608) Gwenview::MainWindow::Private::sideBarConfigGroupName: mCurrentMainPageId == 'StartMainPageId'
Comment 1 Gavin77 2014-04-11 20:11:47 UTC
Problem still remains in version 4.13 final.
Comment 2 Christoph Feck 2014-04-19 17:10:51 UTC
Reproducible. Just starting gwenview from terminal, then closing it, does not exit the process.
Comment 4 Christoph Feck 2014-06-18 22:09:51 UTC
*** Bug 336339 has been marked as a duplicate of this bug. ***