Depends what you are doing.
If you are just assigning some unpartitioned space (or are commandeering the recovery partition or something) then yeah that is a long time. If you are shrinking a fairly full and fairly fragmented partition* on a slow drive (and a search says this is a 4200 rpm drive on an older atom processor so slow is likely) then 5 hours is not unreasonable, though it should hopefully at least have told you what start it is on (maybe some more if you click a little triangle to get more info).
Depending upon what stage the thing has crashed on will vary how troublesome it is -- stopping it in the middle of reallocating files is generally bad news if you wanted the data on the drive, probably not beyond recovery but certainly not a quick session with photorec or recuva or something.
It might be something as simple as the drive refused to unmount -- if you have one still mounted somewhere try closing any file manager windows/running programs and forcing it to unmount. Gparted will usually fail gracefully in that situation but who knows.
For what it is worth the diskmgmt.msc program would not have been able to do much of this -- it is pretty much only useful for deleting, creating and formatting new ones. Resizing partitions is a bit outside its ability.
*if you are having trouble visualising it then if you have 80 gigs and it was full then the files will be scattered all over it, the tool then has to take all the files and put them all into one part of the disk so as to give it an unbroken chunk to call a new partition.
I would leave it a while longer (perhaps overnight), after checking it is not still mounted, and if nothing has happened then turn it off and prepare to have lost the XP partition's data.