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 it could after
being supposedly closed, but I'm not sure if this happens every time,
so I'll open a separate bug report once that one is closed.
Reply to: