I have a problem with GetBundles: When I start it, it basically hangs while connecting to the server. It has been like this for some time (I do not remember if it ever actually worked for me).
I have tried removing all my TextMate application support folder but it did not seem to help.
After I close GetBundles, I all the options in the "GetBundles" menu are greyed out. If I quit TextMate, a ruby process is left, which I kill manually.
Any suggestions?
I am on 10.6.2, ruby 1.8.7.
Thanks.
I'm having the same problem. Anybody got any pointers as to what is going wrong?
Regards
James
On 18 Mar 2010, at 21:58, Achilleas Lazarides wrote:
I have a problem with GetBundles: When I start it, it basically hangs while connecting to the server. It has been like this for some time (I do not remember if it ever actually worked for me).
I have tried removing all my TextMate application support folder but it did not seem to help.
After I close GetBundles, I all the options in the "GetBundles" menu are greyed out. If I quit TextMate, a ruby process is left, which I kill manually.
Any suggestions?
I am on 10.6.2, ruby 1.8.7.
Thanks.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
Hi,
sorry for the delay.
Well, could you please check firstly the environment. Go to Bundles > GetBundles > Help item 1 Requirements and press the button "Check Requirements" if it comes up with right data esp. the correct ruby version < 1.9 ?
While GetBundles is trying to connect the server, please open the Log Drawer ⇧⌥⌘L or go to the gear menu. Are there any relevant error messages ?
--Hans
Hello,
The console only says ~/Library/Application Support/TextMate/Bundles/GetBundles.tmbundle/Support/getBundles.rb:1143: warning: Insecure world writable dir ~/Library/Application Support in PATH, mode 040706
Check requirements returns the following: ====================================================== “svn” client found in: /usr/bin/svn svn, version 1.6.5 (r38866)
“TM_SVN” set to:
“unzip” found in: /usr/bin/unzip
“tar” found in: /usr/bin/tar
“ruby”: ruby 1.8.7 (2008-08-11 patchlevel 72) [universal-darwin10.0]
“ping textmate.org”: PING textmate.org (208.78.96.139): 56 data bytes 64 bytes from 208.78.96.139: icmp_seq=0 ttl=46 time=2460.008 ms
“ping github”: PING github.com (207.97.227.239): 56 data bytes 64 bytes from 207.97.227.239: icmp_seq=0 ttl=48 time=83.506 ms ======================================================
After I try to use GetBundles and fail, if I then quit TextMate, a ruby process stays running until I kill that too.
Thanks for the help.
On 22/3/10 at 12:55, bibiko@eva.mpg.de (Hans-Jörg Bibiko) wrote:
Hi,
sorry for the delay.
Well, could you please check firstly the environment. Go to Bundles > GetBundles > Help item 1 Requirements and press the button "Check Requirements" if it comes up with right data esp. the correct ruby version < 1.9 ?
While GetBundles is trying to connect the server, please open the Log Drawer ⇧⌥⌘L or go to the gear menu. Are there any relevant error messages ?
--Hans
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On Mar 22, 2010, at 6:25 PM, Achilleas Lazarides wrote:
The console only says ~/Library/Application Support/TextMate/Bundles/GetBundles.tmbundle/Support/getBundles.rb:1143: warning: Insecure world writable dir ~/Library/Application Support in PATH, mode 040706
Hmm, this indicates that your dir '~/Library/Application Support' has the wrong permissions set. It should only have read/write/execute right of the user. To change this you can use the Finder or the Terminal command:
chmod og-w ~/Library/Application Support
This could explain why GetBundles stalls here, but not in line 1143. Do you have the latest version 1.2 (look into GetBundles' Console Drawer first line)
After I try to use GetBundles and fail, if I then quit TextMate, a ruby process stays running until I kill that too.
Hmm, if something went wrong you can kill GetBundles via Bundles > GetBundles > Close Dialog.
Which TextMate version plus SupportFolder version(write into an empty TM win: cat "$TM_SUPPORT_PATH/version" and press ^R) do you have?
I have TM Version 1.5.9 (1589) and 11850
--Hans
Thanks! See below.
On 22/3/10 at 21:42, bibiko@eva.mpg.de (Hans-Jörg Bibiko) wrote:
On Mar 22, 2010, at 6:25 PM, Achilleas Lazarides wrote:
The console only says ~/Library/Application
Support/TextMate/Bundles/GetBundles.tmbundle/Support/getBundles.rb:1143: warning: Insecure world writable dir ~/Library/Application Support in PATH, mode 040706
Hmm, this indicates that your dir '~/Library/Application Support' has the wrong permissions set. It should only have read/write/execute right of the user. To change this you can use the Finder or the Terminal command:
chmod og-w ~/Library/Application Support
Hmm, that fixed it. This is not good, as I have specific reasons to set the permissions so.
And looking at line 1143, I don't understand why those permissions should matter.
At any rate thanks again for the help; I'll see how I'll work this out. GetBundles is excellent.
Achilleas
This is the contents of my log file after I tried - chmod og-w ~/Library/Application\ Support
/Users/james/Library/Application Support/TextMate/Bundles/GetBundles.tmbundle/Support/lib/globalVariables.rb:1: warning: Insecure world writable dir /usr/local/bin in PATH, mode 040777
03/23/2010 18:15:05 TextMate[GetBundles] GetBundles – version 1.2 – Hans-Jörg Bibiko - bibiko@eva.mpg.de
03/23/2010 18:15:05 TextMate[GetBundles] GetBundles' DIALOG runs at token 1
Regards
James
On 22 Mar 2010, at 20:42, Hans-Jörg Bibiko wrote:
On Mar 22, 2010, at 6:25 PM, Achilleas Lazarides wrote:
The console only says ~/Library/Application Support/TextMate/Bundles/GetBundles.tmbundle/Support/getBundles.rb:1143: warning: Insecure world writable dir ~/Library/Application Support in PATH, mode 040706
Hmm, this indicates that your dir '~/Library/Application Support' has the wrong permissions set. It should only have read/write/execute right of the user. To change this you can use the Finder or the Terminal command:
chmod og-w ~/Library/Application Support
This could explain why GetBundles stalls here, but not in line 1143. Do you have the latest version 1.2 (look into GetBundles' Console Drawer first line)
After I try to use GetBundles and fail, if I then quit TextMate, a ruby process stays running until I kill that too.
Hmm, if something went wrong you can kill GetBundles via Bundles > GetBundles > Close Dialog.
Which TextMate version plus SupportFolder version(write into an empty TM win: cat "$TM_SUPPORT_PATH/version" and press ^R) do you have?
I have TM Version 1.5.9 (1589) and 11850
--Hans
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On Mar 23, 2010, at 7:17 PM, James Raybould wrote:
This is the contents of my log file after I tried - chmod og-w ~/Library/Application\ Support
/Users/james/Library/Application Support/TextMate/Bundles/GetBundles.tmbundle/Support/lib/globalVariables.rb:1: warning: Insecure world writable dir /usr/local/bin in PATH, mode 040777
Hi James,
the same here. As far as I know /usr/local/bin owns root ie only root is allowed to write something in that directory. All other users/groups should only read and execute stuff in there; otherwise it's a security hole.
Why did you set this?
Thus try as root: chmod og-w /usr/local/bin
to remove the writing access for other and group
--Hans
Rather scarily I'm not sure I ever have…
All of the subdirectories also seemed to have the same (wrong) permissions set and changing them all using .
Thanks for your help
James
On 23 Mar 2010, at 19:47, Hans-Jörg Bibiko wrote:
On Mar 23, 2010, at 7:17 PM, James Raybould wrote:
This is the contents of my log file after I tried - chmod og-w ~/Library/Application\ Support
/Users/james/Library/Application Support/TextMate/Bundles/GetBundles.tmbundle/Support/lib/globalVariables.rb:1: warning: Insecure world writable dir /usr/local/bin in PATH, mode 040777
Hi James,
the same here. As far as I know /usr/local/bin owns root ie only root is allowed to write something in that directory. All other users/groups should only read and execute stuff in there; otherwise it's a security hole.
Why did you set this?
Thus try as root: chmod og-w /usr/local/bin
to remove the writing access for other and group
--Hans
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
the same here. As far as I know /usr/local/bin owns root ie only root is allowed to write something in that directory. All other users/groups should only read and execute stuff in there; otherwise it's a security hole.
Actually the [homebrew][1] project seems to have other ideas, which one may or may not agree with.
But in any case it is probably not a good idea to make assumptions or to impersonate the local hard disk sherif.
Gerd
On Mar 23, 2010, at 10:41 PM, Gerd Knops wrote:
the same here. As far as I know /usr/local/bin owns root ie only root is allowed to write something in that directory. All other users/groups should only read and execute stuff in there; otherwise it's a security hole.
Actually the [homebrew][1] project seems to have other ideas, which one may or may not agree with.
But in any case it is probably not a good idea to make assumptions or to impersonate the local hard disk sherif.
Hi Gerd,
of course, I agree and I revoke it. It was not my intention to make assumptions or to impersonate the local hard disk sherif. Solely the user is responsible about her/his hard disk.
The point here was that Ruby's popen routine is aware of such cases (I do not know why - but anyway) which cause the malfunction.
_Personally_ I think to assign writing access permission for all users to eg /usr/local/bin could cause trouble regarding eg the accidental deletion of files etc. esp. if you have a multi-user machine.
Cheers, --Hans
-
Achilleas Lazarides -
Gerd Knops -
Hans-Jörg Bibiko -
James Raybould