discuss-gnustep
[Top][All Lists]
Advanced

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

Re: problem loading GWorkspace DesktopPreferences Gorm file


From: Fred Kiefer
Subject: Re: problem loading GWorkspace DesktopPreferences Gorm file
Date: Mon, 16 Apr 2012 23:46:50 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120312 Thunderbird/11.0

On 15.04.2012 20:03, Sebastian Reitenbach wrote:
Hi,

I'm testing GWorkspace for a new release, and found, that the DesktopPrefs Gorm 
file doesn't load anymore:

2012-04-15 19:41:40.380 GWorkspace[7146] Exception occured while loading model: 
expected array count 8 and got 134479950
2012-04-15 19:41:40.381 GWorkspace[7146] Failed to load Gorm
2012-04-15 19:41:40.381 GWorkspace[7146] Exception occured while loading model: 
expected array count 8 and got 134479950
2012-04-15 19:41:40.381 GWorkspace[7146] Failed to load Gorm
2012-04-15 19:41:40.381 GWorkspace[7146] failed to load DesktopPref!
2012-04-15 19:41:41.036 GWorkspace[7146] prfsname {"fsn_info_type" = 0; geometry = "508 93 450 675 0 0  1024 768 "; 
"hligh_table_col" = 0; iconposition = 5; iconsize = 48; labeltxtsize = 12; lastselection = ("/"); "list_view_columns" = 
{0 = {identifier = 0; minwidth = 80; position = 0; width = 140; }; 1 = {identifier = 1; minwidth = 80; position = 3; width = 129; }; 2 = {identifier 
= 2; minwidth = 80; position = 1; width = 90; }; 3 = {identifier = 3; minwidth = 50; position = 2; width = 50; }; }; shelfdicts = ({index = 0; paths 
= ("/home/sebastia"); }, {index = 1; paths = ("/usr/local/libexec/GNUstep"); }); shelfheight = 77; singlenode = 0; spatial = 0; 
viewtype = Browser; }

Riccardo said, this file was edited lately.
When I see those large numbers I guess, it may be that while editing that file 
on amd64, after the NSNotFound change with Gorm, that Gorm did encode some 
garbage in it?

I have seen a similar problem with a Gorm file of PRICE too while testing that.
The problem with GWorkspace only tested on i386 so far, the problem with PRICE 
I have seen on i386 and amd64.

Any idea where this could come from and what to do about it?

Sebastian

Which version of GNUstep are you using here? I think Richard fixed this decoding bug on 2012-02-28. The file was recently changed from version 12.3.1 to 12.4.2 maybe your GNUstep version is to old for that, but as you generate a completely different version number this doesn't get detected?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]