TonP Posted January 15, 2009 Report Share Posted January 15, 2009 Thanks for the Linux support. However I have serious issue. I can't install the OpenG dynamic palletes. What's even worse if I retry this, the rights on the /TMP folder are changed (I don't know why I am not a linux geek). But effictively I cannot acces my .Xauthority file (which is not in my tmp), and after a boot I cannot start the GDM environment and am stuck in terminal mode (I am not a freaking C programmer). I know the fix: chown root:root /tmpchmod 1777 /tmp The why however I don't know. Here's the log from the VIPM error file: ========= START of VIPM Error Message =========An internal VIPM Error has occured on: Thursday January 15, 2009 at 09:49:51 PM = Automated Message Start = Error 7 occurred at Get File Size in 179C4B83ABA1064362020813817DB8B5.lvlib:7734C96F08F3926DF34983DA1B56D354->179C4B83ABA1064362020813817 DB8B5.lvlib:EA8084745D26072B152728A52407A64C->179C4B83ABA1064362020813817DB8B5.lvlib:13367D38B392068 5B294751893E04624->79DB56B455840F26E4C53234B4284FB6->VIPM Main Window.vi Possible reason(s): LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux. Verify that the path is correct using the command prompt or file explorer. ========================= NI-488: Nonexistent GPIB interface. = Automated Message End = = Call Chain Start = VIPM Main Window.vi = Call Chain End = ========= END of VIPM Error Message ========= ========= START of VIPM Error Message ========= An internal VIPM Error has occured on: Thursday January 15, 2009 at 09:56:29 PM = Automated Message Start = Error 7 occurred at Get File Size in 179C4B83ABA1064362020813817DB8B5.lvlib:7734C96F08F3926DF34983DA1B56D354->179C4B83ABA1064362020813817 DB8B5.lvlib:EA8084745D26072B152728A52407A64C->179C4B83ABA1064362020813817DB8B5.lvlib:13367D38B392068 5B294751893E04624->79DB56B455840F26E4C53234B4284FB6->VIPM Main Window.vi Possible reason(s): LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux. Verify that the path is correct using the command prompt or file explorer. ========================= NI-488: Nonexistent GPIB interface. = Automated Message End = = Call Chain Start = VIPM Main Window.vi = Call Chain End = ========= END of VIPM Error Message ========= EDIT: OS: Ubunut 8.10 LabVIEW 8.2 VIPM 2.0.3 Ton (minor issue I cannot close the little legend, I see the glyph on the X change however it does not close. Link to comment Share on other sites More sharing options...
Philippe Guerit Posted January 16, 2009 Report Share Posted January 16, 2009 ...What's even worse if I retry this, the rights on the /TMP folder are changed (I don't know why I am not a linux geek).But effictively I cannot acces my .Xauthority file (which is not in my tmp), and after a boot I cannot start the GDM environment and am stuck in terminal mode (I am not a freaking C programmer)... I have had this happen to me as well even when I was not using VIPM. So I am not entirely sure that the /tmp access right changed is due to VIPM (although I do not discard it). Like you I was confused when I could not reboot back to my KDE. But thanks for the information. we will look into it. PJM Link to comment Share on other sites More sharing options...
Jim Kring Posted January 17, 2009 Report Share Posted January 17, 2009 Hi Ton, I just heard a similar story from another Linux user who said the following: On Linux RedHat WS4, installing VIPM changed the permission and owner of files contained in /home/users and in /tmp. After this we are unable to login with the user who've install VIPM (the problem occurs also when we did the VIPM installation logged as root). Changing owner and permission fixed the problem. Thanks, -Jim Link to comment Share on other sites More sharing options...
Jim Kring Posted January 17, 2009 Report Share Posted January 17, 2009 Hi Ton, I have added this to the known issues: Known Issue (Case 6782): VIPM installer on Linux can alter home and tmp permissions Thanks, Link to comment Share on other sites More sharing options...
TonP Posted January 17, 2009 Author Report Share Posted January 17, 2009 I had the same thing when installing packages (after an install and reboot after fixing things). However I run VIPM as root to be able to write to usr/local. Ton Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted May 6, 2014 Report Share Posted May 6, 2014 Just wanted to let you know that we're currently working on a new release of VIPM 2014 with better Linux support. See here for more info: VIPM 2014 for Linux Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.