# Problems after installing RoboEarth [closed]

After i intalled roboearth and what was said in the installation instructions, every time i open a terminal before i could write anything y get

bash: /bin/sed: Argument list too long
bash: /bin/sed: Argument list too long
bash: /usr/bin/env: Argument list too long


after a while i found out it was due to the .bashrc file because when it run

source /opt/ros/fuerte/setup.bash


it got stuck. Now my ROS does not work, when i put echo \$ROS_PACKAGE_PATH i dont get the path i get a blank space and cant call anything related to ROS. When the process of installing finished it said it was over-writing the setup.bash and other files, could this have ruined my enviorment? Im really stuck and any help would be really helpfull, thanks really apreciate it

edit retag reopen merge delete

### Closed for the following reason question is not relevant or outdated by tfoote close date 2016-08-08 01:44:49.958790

@tbn thanks for the help, so do you know why this problem happend? or a clue any idea would be of great help. Thanks

( 2013-08-27 15:10:16 -0500 )edit

sed is the stream editor program and env is a program to run things in a different environment. I'm really not sure, but I'd think that either 1)your setup file was edited incorrectly, 2)your .bashrc file is somehow wrong, or 3)you're on a system that can't process a lot of arguments. You need the setup file sourced in order to use all the ROS commands, so in the case of 1) or 2), I'd probably save your current setup file to a backup and replace it with a fresh, unmodified one and try again.

( 2013-08-28 03:36:18 -0500 )edit

@tbn thanks a lot , where can i get the fresh setup file?? to test it? thanks

( 2013-08-29 04:13:36 -0500 )edit

So I just looked at my setup.* file, and it's actually auto-built by catkin, not downloaded as I originally thought. My apologies for the incorrect info. This is actually beyond my current expertise.

( 2013-08-29 04:48:28 -0500 )edit

@tbn a little question this error appeared after i left my computer running a ROS node (openni_camera) for a entire weekend (did not realize it until i got back to work) and when i closed the running terminal and open a new one this problem started could this have generated the problem? or is it just coincidence? Thanks

( 2013-08-29 05:19:24 -0500 )edit