[Bug 15420] New: breezy gam_server hung using 100% CPU

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=15420
Ubuntu | gamin

           Summary: breezy gam_server hung using 100% CPU
           Product: Ubuntu
           Version: unspecified
          Platform: i386
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gamin
        AssignedTo: seb128 at ubuntu.com
        ReportedBy: dooglus at gmail.com
         QAContact: desktop-bugs at lists.ubuntu.com


Last night after 12 hours of using the latest breezy packages I noticed that the
CPU was 100% busy.  It hadn't been busy for the previous 12 hours, this had only
just started.  'top' showed me that 'gam_server' was the busy process.

Note that gamin hasn't changed for over a month:
http://lists.ubuntu.com/archives/breezy-changes/2005-August/009170.html

I did update breezy from the repositories yesterday, as I do every day.  Perhaps
one of the other changes caused this.

I logged out of the GNOME session and gam_server was still busy (as shown by
'top' in a virtual console.  I dropped down to runlevel 1 and back to 3 and it
restarted OK, and hasn't been a problem since.

$ apt-cache policy gamin
gamin:
  Installed: 0.1.5-0ubuntu1
  Candidate: 0.1.5-0ubuntu1
  Version table:
 *** 0.1.5-0ubuntu1 0
        500 http://archive.ubuntu.com breezy/main Packages
        100 /var/lib/dpkg/status

I've never seen this happen before, but wasn't doing anything unusual at the
time.  I had just modified the sources of DROD, an SDL game
http://www.caravelgames.com/sourcecode.html , compiled it and run it.  But I'd
done that before without problems too.

I know this bug report isn't very useful, since I can't reproduce the problem,
but I thought I should mention it.

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.