[grisbi-bugs] [Grisbi-0.6.0 0000652]: Freeze after "1st time run" wizard when launched graphically (double-click) or via Powershell

bugtracker at grisbi.org bugtracker at grisbi.org
Wed Oct 7 14:53:52 CEST 2009


The following issue has been CONFIRMED. 
====================================================================== 
http://grisbi.tuxfamily.org/mantis/view.php?id=652 
====================================================================== 
Reported By:                guneeyoufix
Assigned To:                guneeyoufix
====================================================================== 
Project:                    Grisbi-0.6.0
Issue ID:                   652
Category:                   Main
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     confirmed
Plateforme:                 Windows 
OS:                         Windows 
Version OS:                 Vista Familiale Premium 
Unstable Impact:            Yes 
Version GTK:                 
====================================================================== 
Date Submitted:             09-30-2009 21:11 UTC
Last Modified:              10-07-2009 12:53 UTC
====================================================================== 
Summary:                    Freeze after "1st time run" wizard when launched
graphically (double-click) or via Powershell
Description: 
Grisbi freezes on completion of the 1st time run wizard (when there is no
configuration file), and when Grisbi is launched graphically with a
double-click in explorer.exe, or by a command line in Powershell.

Basically, it only works when launched from cmd.exe
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0000665 Grisbi can't found hiColor theme
====================================================================== 

---------------------------------------------------------------------- 
 guneeyoufix - 10-04-09 15:32  
---------------------------------------------------------------------- 
Launching Grisbi for the first time only works if launched with the command
line "grisbi" (as such in the Windows Processes Explorer). It fails when
launched with the full path command line ("c:\grisbi6b1\grisbi.exe").

I also tried adding "."(current directory) and the full path of my Grisbi
build to my Path, and it didn"t help; so it doesn't seem to ba a
PATH-related issue.

 

---------------------------------------------------------------------- 
 guneeyoufix - 10-05-09 17:09  
---------------------------------------------------------------------- 
Located the problem.
The call to
     gdk_pixbuf_new_from_file(string, NULL), in file
gsb_currency_config.c; line 1251
freezes when string is a full path to a file that doesn't exist (which
happens when grisbi is launched graphically).

If the path is relative to the grisbi.exe folder, then the call ends
normally, and the exec carries on.

I believe this is a gtk+ bug, so I tried compiling with a newer version of
the bundle
(http://ftp.gnome.org/pub/gnome/binaries/win32/gtk+/2.16/gtk+-bundle_2.16.6-20090910_win32.zip
), but it didn't help.

 

---------------------------------------------------------------------- 
 talapoga - 10-06-09 12:21  
---------------------------------------------------------------------- 
I try to launch Grsibi as said in this report, it work. It is really the
same bug as 0000665 

---------------------------------------------------------------------- 
 guneeyoufix - 10-07-09 12:52  
---------------------------------------------------------------------- 
Found the real source of the problem.

It seems that on Windows Vista, in a given directory, all files beginning
with the "CON." string exist, and are protected. However, they do NOT
appear in explorer, even when system files are shown. (Just try creating
CON.txt on you desktop, and you'll see)

Therefore, when gdk_pixbuf_new_from_file tries to load the png, it doesn't
stop because the file doesn't exits (because windows says it does), but
crashes because windows won't let gdk touch the file.

The only working solution I can think of is to change the congo flag
filename to "CO_.png" (or something else that doesn't start with "CON.") in
gsb_currency_config.c, so that gdk_pixbuf_new_from_file can fail properly.

 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
09-30-09 21:11  guneeyoufix    New Issue                                    
09-30-09 21:11  guneeyoufix    Plateforme                => Windows         
09-30-09 21:11  guneeyoufix    OS                        => Windows         
09-30-09 21:11  guneeyoufix    Version OS                => Vista Familiale
Premium
09-30-09 21:11  guneeyoufix    Unstable Impact           => Yes             
09-30-09 21:55  guneeyoufix    Note Added: 0001165                          
10-04-09 15:31  guneeyoufix    Note Added: 0001173                          
10-04-09 15:32  guneeyoufix    Note Edited: 0001165                         
10-04-09 15:33  guneeyoufix    Note Deleted: 0001173                        
10-05-09 17:06  guneeyoufix    Note Added: 0001176                          
10-05-09 17:06  guneeyoufix    Status                   new => confirmed    
10-05-09 17:09  guneeyoufix    Note Edited: 0001176                         
10-06-09 10:53  guneeyoufix    Relationship added       has duplicate 0000665
10-06-09 12:21  talapoga       Note Added: 0001181                          
10-06-09 21:27  guneeyoufix    Status                   confirmed => assigned
10-06-09 21:27  guneeyoufix    Assigned To               => guneeyoufix     
10-07-09 10:17  guneeyoufix    Note Added: 0001184                          
10-07-09 12:52  guneeyoufix    Note Edited: 0001184                         
10-07-09 12:53  guneeyoufix    Status                   assigned => confirmed
======================================================================



More information about the bugsreports mailing list