Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[xinelo]

Hello,

I use Ubuntu Dapper and I have recently upgraded from Hoary and switched from Gnome to KDE. aMule worked more or less fine in Gnome but now when I try to execute it I get a message that says "Bad permissions on Temp directory!"

My permissions are:

Code: [Select]

xinelo@micho:~$ ls -als | grep aMule
4 drwx------  4 xinelo xinelo   4096 2006-06-20 00:21 .aMule

xinelo@micho:~/.aMule$ ls -ls
total 3968
   4 -rw-r--r-- 1 xinelo xinelo    3278 2006-06-04 15:52 amule.conf
1100 -rw-r----- 1 xinelo xinelo 1120271 2006-06-04 15:52 clients.met
1100 -rw-r----- 1 xinelo xinelo 1119200 2006-06-04 14:15 clients.met.BAK
   4 -rw-r--r-- 1 xinelo xinelo     365 2006-01-28 02:22 cryptkey.dat
   4 -rw-r----- 1 xinelo xinelo       5 2006-06-04 15:52 emfriends.met
   4 drwxr-x--- 2 xinelo xinelo    4096 2006-06-19 02:10 Incoming
   0 -rw-r--r-- 1 xinelo xinelo       0 2006-06-04 15:52 ipfilter.dat
1620 -rw-r----- 1 xinelo xinelo 1652062 2006-06-04 15:10 known2.met
  36 -rw-r----- 1 xinelo xinelo   33929 2006-06-04 15:52 known.met
   4 -rw-r--r-- 1 xinelo xinelo       6 2006-06-04 14:15 lastversion
   4 -rw-r--r-- 1 xinelo xinelo     207 2006-06-20 00:21 logfile
   4 -rw------- 1 xinelo xinelo       6 2006-06-20 00:21 muleLock
   4 -rw-r----- 1 xinelo xinelo      17 2006-06-04 15:52 preferences.dat
  32 -rw-r----- 1 xinelo xinelo   32406 2006-06-04 15:52 server.met
  40 -rw-r----- 1 xinelo xinelo   39915 2006-06-04 14:16 server_met.old
   0 -rw-r--r-- 1 xinelo xinelo       0 2006-06-04 15:52 shareddir.dat
   8 drwxr-x--- 2    750 xinelo    8192 2006-05-28 18:32 TempMy /etc/fstab file looks like:

Code: [Select]

# /etc/fstab: static file system information.
#
#            
proc            /proc           proc    defaults        0       0
/dev/hda7       /               ext3    defaults,errors=remount-ro 0       1
/dev/hda5       /boot           ext3    defaults        0       2
/dev/hda2       /windows        vfat    defaults        0       0
/dev/hda6       none            swap    sw              0       0
/dev/hdc        /media/cdrom0   udf,iso9660 ro,user,noauto  0       0
/dev/scd0       /media/cdrom1   udf,iso9660 ro,user,noauto  0       0
/dev/sda        /media/usb0     auto    rw,user,noauto  0       0I don't know if I need to send some more information about my system.

Does anyone see where the problem may be?

Thanks a lot! xinelo

PS: By the way, I've just seen my version is not the latest: if someone replies to my problem above, could you also say what should be done to update the program to the latest version?

[wuischke]

Welcome xinelo!

As you can see in this line only the owner has the right to write in this folder, but instead of you the owner is '750'.

8 drwxr-x--- 2    750 xinelo    8192 2006-05-28 18:32 Temp

To solve this type sudo chown xinelo Temp in the terminal whilst your active directory is the ~/.aMule folder.

To update, take a look at the distro specific packages forum and see the ubuntu-thread. There are several packages which you can install either with sudo dpkg -i package or with the graphical installer of Dapper.

I wish you a nice Tuesday!

[xinelo]

Hey Wulschke, thank you so much for your prompt reply!

You're absolutely right that the owner of Temp is wrong. However I put that wrong unwittingly when trying to solve the problem of bad permissions. That's because I did a chown 750 Temp instead of a chmod 750 Temp, ups! That's solved now:

Code: [Select]

  8 drwxr-x--- 2 xinelo xinelo    8192 2006-05-28 18:32 TempHowever the message still appears, the same as before chowing the Temp directory. Any other clues? (it would have been too easy otherwise )

Thanks a lot again, and have a great Tuesday too!

PS Thanks too for your help with the updating of the package.

[wuischke]

Well, if the permissions seem to be OK, I would try to rename the old temp-directory and let aMule create a new one. If it works then just move the files into the new folder.

And just to ensure, that everything were dealing with the correct folder: cat amule.conf | grep TempDir

[xinelo]

Well, if the permissions seem to be OK, I would try to rename the old temp-directory and let aMule create a new one. If it works then just move the files into the new folder.

That looked like a good idea, but it didn't work for me. I even tried desinstalling (sudo aptitude purge amule) the program and installing it again, but the result is the same!

And just to ensure, that everything were dealing with the correct folder: cat amule.conf | grep TempDir

Then I tried that one.

Code: [Select]

xinelo@micho:~/.aMule$ cat amule.conf | grep TempDir
TempDir=/media/SDA1/tmp/_tmpI supose that line in the amule.conf file shows where the Temp dir is. And it is not where I thought it was (it's not in the .aMule directory)! I had changed it to an external hard disk, and I didn't remember any more. However, the problem persist although the permissions of that directory seem to be fine. Eventually I've realized the disk is full. I'll find out whether that's the reason when I do a bit of clean-up and free up some space.

THank you so much!

[wuischke]

OK, then it doesn't matter anyway what we're doing in your homedir, when the affected temp-dir is somewhere else...
I guess you know what you could do now to get it working...

[xinelo]

Yes, I guess so. Otherwise I'll come back with more feed-back.

Thank you, I wouldn't have realized that I had changed the Temp directory if I hadn't look at the amule.conf file (which I didn't know it existed). And sorry about my absent-mindedness.

But, the good thing of having problems is that you always learn something!

Have a nice Thursday! xinelo

[chiagod]

Just wanted to add I was having the same issue though there was a slightly different cause.   My temp directory had the right permissions, issue was when I compared the directory path to the actual location of the temp directory I realized my .aMule directory was called .amule (lower case M).  Fixed that and I'm back in business!

[sliekas_kanibalas]

look carefully to config - i had same problem and it works after i fixed one mistake - IncomingDir=/home/some_user/.aMule/Incoming in this line aMule word was without dot. i added dot, removed amulelock file (or smth like this) and ran again - and it works good luck thanx all people, you helped me to find a solution to problem

p.s. my eglish speech is terrible, so sorry if i made mistakes :|