Bug#691114: marble: dangling process after the application was closed

Hi, Maximiliano Curia wrote (27 Jul 2014 19:03:05 GMT) : > I can't reproduce the issue in wheezy nor in sid, neither in kde nor in > fluxbox. Can you still reproduce it? What about with a new user? I can't reproduce the bug in sid anymore => feel free to close. Thanks for the heads up, cheers!

Bug#691114: marble: dangling process after the application was closed

Control: tags -1 + unreproducible Hi, I can't reproduce the issue in wheezy nor in sid, neither in kde nor in fluxbox. Can you still reproduce it? What about with a new user? Happy hacking, -- "Programming today is a race between software engineers striving to build bigger and better idiot-proo

Bug#691114: marble: dangling process after the application was closed

Package: marble Version: 4:4.8.4-3 Severity: normal 1. run marble in a shell 2. ctrl-q 3. the GUI is closed (fine) 4. on the terminal: marble(2669)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: 5. the process is still running I've also seen marble consume as much of a CPU core as