kpat uses 100% CPU for a while when selecting game type

Bug #367062 reported by Graham Menhennitt
2
Affects Status Importance Assigned to Milestone
kde4libs (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: kde4libs

I've done a fresh install of Kubuntu Jaunty on a Dell Inspiron 6400 notebook. I then added kpat (KDE patience card games) via KPackageKit. I start kpat and it asks for the game type (shows the 4 x 3 grid of the games). When I click on one of the games to select it, kpat starts using 100% of the CPU time. It stays like this for between 15 and 40 seconds. Eventually, it deals the cards for the game and the CPU usage drops to normal.

Kubuntu 9.04
Linux chief 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux
kpat:
  Installed: 4:4.2.2-0ubuntu1
  Candidate: 4:4.2.2-0ubuntu1
  Version table:
 *** 4:4.2.2-0ubuntu1 0
        500 http://au.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

Revision history for this message
Graham Menhennitt (graham-menhennitt) wrote :

I was wrong above. The problem happens whenever it deals a new hand - not just the first time on starting the program.

Revision history for this message
Graham Menhennitt (graham-menhennitt) wrote :

Sorry, it seems this was my mistake. Please close this as "not a bug".

For the benefit of anybody who makes the same mistake, it appears that it happens if there are files in /var/tmp/kdecache-<username> that are not owned by <username>. I suggest removing this directory and letting it be recreated.

I had changed my UID (to match my UID on a NFS server). I changed the ownership of all files in my home directory to match the new UID and then rebooted. But I didn't realise that there were files elsewhere that persisted across reboots.

Revision history for this message
Myriam Schweingruber (myriam) wrote :

Closed by request of the reporter.

Changed in kde4libs (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.