[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#691114: marked as done (marble: dangling process after the application was closed)

Your message dated Wed, 30 Jul 2014 12:53:40 +0200
with message-id <20140730105340.GP3410@gnuservers.com.ar>
and subject line Re: Bug#691114: marble: dangling process after the application was closed
has caused the Debian Bug report #691114,
regarding marble: dangling process after the application was closed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
691114: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691114
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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.

--- End Message ---
--- Begin Message --- 
¡Hola intrigeri!

El 2014-07-27 a las 21:20 +0200, intrigeri escribió:
> I can't reproduce the bug in sid anymore => feel free to close.

Closing the bug.

-- 
"pi seconds is a nanocentury" -- Tom Duff
Saludos /\/\ /\ >< `/

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: