[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Windows status line: Script must have permissions "06
From: |
Sebastian Hilbert |
Subject: |
Re: [Gnumed-devel] Windows status line: Script must have permissions "0600" |
Date: |
Sun, 8 May 2011 21:23:09 +0200 |
User-agent: |
KMail/1.13.6 (Linux/2.6.38.4-23-desktop; KDE/4.6.0; i686; ; ) |
Am Sonntag, 8. Mai 2011, 19:58:43 schrieb LuisCapriles:
> Thaks for your prompt reply.
>
> But, ignoring it would not disable the hooking framework? Not that I want
> to use it right now...
>
That is not impossible. Karsten will have the details and I am sure it can be
made to work on Windows if it does not already.
Sebastian
> I will download 0.9.4 and try it.
>
> Regards
>
> Sebastian Hilbert wrote:
> > Am Sonntag, 8. Mai 2011, 18:57:57 schrieb LuisCapriles:
> >
> >
> > On Windows this can be ignored I think but Karsten will comment as well.
> >
> > I posted client 0.9.4. Please test
> >
> > Sebastian
> >
> >> Hi!
> >> I am new to GNUmed and I am having several issues. I will be posting
> >> them
> >> one at a time. Sorry to post about this problem; I saw that it
> >> appeared before in the forum.
> >>
> >> I am getting this message when the client screen open for the first
> >> time. Also, with the debug mode on, I can see that the message is
> >> generated every
> >> time a clic outside the GNUmed client window, as when bringing the focus
> >> of
> >> other window application.
> >>
> >> I read that the "\scripts\hook_script.py" must have 0600 permission.
> >> But I
> >> am on a Windows XP environment so I do not know if this setting is
> >> posible.
> >> I changed the file persission adding my self and removing everybody else
> >> (Administrators, System) to no gain. If I remove the file, it is
> >> recreated
> >> with group "Administrators" and user "SYSTEM" with full permission over
> >> the
> >> file.
> >>
> >> Following is the portion of the log when the hook script is recreated,
> >> where appears other errors:
> >> 2011-05-08 11:57:51 WARNING gm.hook
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmhooks::import_hook_module() #94): creating default hook
> >> script 2011-05-08 12:01:02 CRITICAL gm.logging
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmlog2::flush() #116): -------- synced log file
> >> -------------------------------
> >> 2011-05-08 12:01:02 DEBUG gm.shell
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmshellapi::detect_external_binary() #18): detecting
> >> [xdg-open] 2011-05-08 12:01:02 DEBUG gm.shell
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmshellapi::detect_external_binary() #30): [which xdg-open]
> >> failed, exit code: 1
> >> 2011-05-08 12:01:02 DEBUG gm.shell
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmshellapi::detect_external_binary() #18): detecting
> >> [kfmclient] 2011-05-08 12:01:02 DEBUG gm.shell
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmshellapi::detect_external_binary() #30): [which
> >> kfmclient] failed, exit code: 1
> >> 2011-05-08 12:01:02 DEBUG gm.shell
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmshellapi::detect_external_binary() #18): detecting
> >> [gnome-open]
> >> 2011-05-08 12:01:02 DEBUG gm.shell
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmshellapi::detect_external_binary() #30): [which
> >> gnome-open] failed, exit code: 1
> >> 2011-05-08 12:01:02 DEBUG gm.shell
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmshellapi::detect_external_binary() #18): detecting
> >> [exo-open] 2011-05-08 12:01:02 DEBUG gm.shell
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmshellapi::detect_external_binary() #30): [which exo-open]
> >> failed, exit code: 1
> >> 2011-05-08 12:01:02 DEBUG gm.shell
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmshellapi::detect_external_binary() #18): detecting [op]
> >> 2011-05-08 12:01:02 DEBUG gm.shell
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmshellapi::detect_external_binary() #30): [which op]
> >> failed, exit
> >> code: 1
> >> 2011-05-08 12:01:02 DEBUG gm.shell
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmshellapi::detect_external_binary() #18): detecting [open]
> >> 2011-05-08 12:01:02 DEBUG gm.shell
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmshellapi::detect_external_binary() #30): [which open]
> >> failed, exit code: 1
> >> 2011-05-08 12:01:02 ERROR gm.docs
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\logg
> >> ing
> >>
> >> ::exception() #1021): Python wrapper for libextractor not installed.
> >>
> >> Traceback (most recent call last):
> >> File
> >>
> >> "C:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outPYZ1.pyz/Gnum
> >> ed. pycommon.gmMimeLib", line 34, in guess_mimetype
> >>
> >> File "C:\workplace\pyinstaller-1.4-rc1\iu.py", line 455, in importHook
> >>
> >> ImportError: No module named extractor
> >> 2011-05-08 12:01:02 ERROR gm.docs
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmmimelib::guess_mimetype() #62): [file -i -b "C:\Documents
> >> and Settings\LuisCapriles\.gnumed\gnumed-5356.log"] on nt (win32):
> >> failed with
> >> exit(1)
> >> 2011-05-08 12:01:02 ERROR gm.docs
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmmimelib::guess_mimetype() #77): [extract -p mimetype
> >> "C:\Documents and
> >> Settings\LuisCapriles\.gnumed\gnumed-5356.log"] on nt (win32): failed
> >> with
> >> exit(1)
> >> 2011-05-08 12:01:02 INFO gm.docs
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmmimelib::guess_mimetype() #83): OS level mime detection
> >> failed,
> >> falling back to built-in magic 2011-05-08 12:01:02 DEBUG gm.docs
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmmimelib::guess_mimetype() #89): "C:\Documents and
> >> Settings\LuisCapriles\.gnumed\gnumed-5356.log" -> <ASCII text>
> >> 2011-05-08 12:01:02 DEBUG gm.docs
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmmimelib::get_viewer_cmd() #105): <ASCII text> viewer:
> >> [None] 2011-05-08 12:01:02 WARNING gm.docs
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmmimelib::call_viewer_on_file() #232): no viewer found via
> >> standard mailcap system
> >> 2011-05-08 12:01:02 INFO gm.docs
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmmimelib::call_viewer_on_file() #235): let's see what the
> >> OS can
> >> do about that
> >> 2011-05-08 12:01:02 DEBUG gm.docs
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmmimelib::call_viewer_on_file() #255): file C:\Documents
> >> and Settings\LuisCapriles\.gnumed\gnumed-5356.log <type ASCII text>
> >> (ext .log)
> >> -> file C:\Documents and
> >> Settings\LuisCapriles\.gnumed\gnumed-5356.log
> >>
> >>
> >>
> >> About my environment:
> >> 2011-05-08 11:52:05 INFO gm.launcher (<string>::log_startup_info()
> >> #201): Starting up as main module ($Revision: 1.169 $).
> >> 2011-05-08 11:52:05 INFO gm.launcher (<string>::log_startup_info()
> >> #202): GNUmed client version [0.9.1] on branch [0.9]
> >> 2011-05-08 11:52:05 INFO gm.launcher (<string>::log_startup_info()
> >> #203): Platform: ('Windows', 'LNV-96D29028', 'XP', '5.1.2600', '', '')
> >> 2011-05-08 11:52:05 INFO gm.launcher (<string>::log_startup_info()
> >> #204): Python 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC v.1310 32
> >> bit
> >> (Intel)] on win32 (nt)
> >> 2011-05-08 11:52:05 INFO gm.cfg
> >> (c:\workplace\gnumed-client.0.9.1\build\pyi.win32\setup\outpyz1.pyz\gnum
> >> ed. pycommon.gmcfg2::<module>() #19): $Revision: 1.20 $
> >>
> >> GNUmed Server is LOCAL on same PC, version 15.
> >>
> >> Regards
> >
> > _______________________________________________
> > Gnumed-devel mailing list
> > address@hidden
> > https://lists.gnu.org/mailman/listinfo/gnumed-devel
Re: [Gnumed-devel] Windows status line: Script must have permissions "0600", Karsten Hilbert, 2011/05/09
Re: [Gnumed-devel] Windows status line: Script must have permissions "0600", Karsten Hilbert, 2011/05/09