PlaneShift

Support => Linux Specific Issues => Topic started by: grayFalcon on June 19, 2008, 08:31:47 am

Title: Crash when opening inventory
Post by: grayFalcon on June 19, 2008, 08:31:47 am
Hello!

After a long time (~2 or 3 years?) I tried to give PlaneShift another shot. Now, when I log on with my old char and try to open the inventory, the game freezes for a few seconds and then crashes.

The character is Rouror Miraparer.

The error message I get is:
Quote
planeshift.application.client:
  PSLoader: step 5: success
   64402) <src/client/psclientdr.cpp:214 HandleDeadReckon>
   64403) Got DR message for unknown entity 29615.
   64666) <src/client/charapp.cpp:523 Attach>
   64667) Mesh Factory helms#helm03_dermf not found
   64684) <src/client/gui/pawsignore.cpp:130 LoadIgnoreList>
   64685) No ignore.xml file found. Assuming empty
   64685)
   64791) <src/common/paws/pawsborder.cpp:60 UseBorder>
   64792) Invalid dimensions on border drawable: >UpperLeftMap<
  PSLoader: step 6: success
   74306) <src/client/psclientdr.cpp:214 HandleDeadReckon>
   74307) Got DR message for unknown entity 29615.
   78981) <src/client/charapp.cpp:523 Attach>
   78982) Mesh Factory helms#helm03_dermf not found

This is happening on Ubuntu 8.04/gnome with the newest, updated client. In case it matters, my graphics card is a GeForce FX 5200

May it be that I just have some too-old item on me that some really nice admin could delete so I can play? ;)

Thanks a lot in advance!
Title: Re: Crash when opening inventory
Post by: Rizin on June 19, 2008, 10:05:32 am
http://hydlaa.com/smf/index.php?topic=32084.from368441#new
Title: Re: Crash when opening inventory
Post by: grayFalcon on June 19, 2008, 11:24:23 pm
Thanks! I got fooled by the message into thinking I had some kind of non-working helmet :(
Title: Re: Crash when opening inventory
Post by: Caarrie on June 20, 2008, 12:09:38 am
Thanks! I got fooled by the message into thinking I had some kind of non-working helmet :(

well there is http://www.hydlaa.com/flyspray_upgrade/index.php?do=details&task_id=1214 but it does not seem to be fully your issue and is fixed in the comming release.