Author Topic: ubuntu 10.04 avast problem  (Read 13825 times)

0 Members and 1 Guest are viewing this topic.

garegin

  • Guest
ubuntu 10.04 avast problem
« on: June 03, 2010, 09:24:19 PM »
i installed avast home and get an error when i try to open it. i put the registration key and get another error. its stock ubuntu, which latest updates. i didnt mess with any configs or crazy stuff like gcc or gtk settings.
they say that you can use ubuntu without touching the terminal. yeah right.

when i open
03:14:37 PM: can't open file '/home/macman/.avast/avastrc' (error 13: Permission denied)
03:14:37 PM: can't open user configuration file '/home/macman/.avast/avastrc'.
03:14:37 PM: Failed to inspect the lock file '/home/macman/.avast/lockfile-macman' (error 2: No such file or directory)
03:14:37 PM: Unable to detect whether another instance of avast! is running.

after putting the key
03:16:43 PM: Directory '/home/macman/.avast/chest' couldn't be created (error 13: Permission denied)
03:16:43 PM: Couldn't create chest in directory '/home/macman/.avast/chest'.
03:16:43 PM: Error while initializing avast! chest.



Offline zilog

  • Avast team
  • Advanced Poster
  • *
  • Posts: 957
  • or #f0; daa; add a,#a0; adc a,#40
Re: ubuntu 10.04 avast problem
« Reply #1 on: June 04, 2010, 12:58:16 PM »
i installed avast home and get an error when i try to open it. i put the registration key and get another error. its stock ubuntu, which latest updates. i didnt mess with any configs or crazy stuff like gcc or gtk settings.
they say that you can use ubuntu without touching the terminal. yeah right.

when i open
03:14:37 PM: can't open file '/home/macman/.avast/avastrc' (error 13: Permission denied)
03:14:37 PM: can't open user configuration file '/home/macman/.avast/avastrc'.
03:14:37 PM: Failed to inspect the lock file '/home/macman/.avast/lockfile-macman' (error 2: No such file or directory)
03:14:37 PM: Unable to detect whether another instance of avast! is running.

after putting the key
03:16:43 PM: Directory '/home/macman/.avast/chest' couldn't be created (error 13: Permission denied)
03:16:43 PM: Couldn't create chest in directory '/home/macman/.avast/chest'.
03:16:43 PM: Error while initializing avast! chest.




Hallo, just delete the .avast hidden directory.

regards,
pc
May's Law: Software efficiency halves every 18 months, compensating Moore's Law. (David May, INMOS)

garegin

  • Guest
Re: ubuntu 10.04 avast problem
« Reply #2 on: June 04, 2010, 06:51:53 PM »
deep breath before using an rm -rf command. is that hidden folder important. i saw another person had the same problem on these forums.

Offline zilog

  • Avast team
  • Advanced Poster
  • *
  • Posts: 957
  • or #f0; daa; add a,#a0; adc a,#40
Re: ubuntu 10.04 avast problem
« Reply #3 on: June 05, 2010, 01:09:16 PM »
deep breath before using an rm -rf command. is that hidden folder important. i saw another person had the same problem on these forums.

the folder is avast-specific and will be re-created, this time with correct rights hopefully, when deleted. that's why this should help.

regards,
pc
May's Law: Software efficiency halves every 18 months, compensating Moore's Law. (David May, INMOS)

jmmk

  • Guest
Re: ubuntu 10.04 avast problem
« Reply #4 on: June 14, 2010, 08:44:14 PM »
When booting into Avast on my Ubuntu system I get:  Lock File '/home/jmmk6/.avast/lockfile-jmmk6' has incorrect permissions -  what is the fix?

Offline zilog

  • Avast team
  • Advanced Poster
  • *
  • Posts: 957
  • or #f0; daa; add a,#a0; adc a,#40
Re: ubuntu 10.04 avast problem
« Reply #5 on: June 15, 2010, 10:06:48 AM »
When booting into Avast on my Ubuntu system I get:  Lock File '/home/jmmk6/.avast/lockfile-jmmk6' has incorrect permissions -  what is the fix?

hello,
delete the file. that's the generic fix for any lock-files :).

regards,
pc
May's Law: Software efficiency halves every 18 months, compensating Moore's Law. (David May, INMOS)

abmunguia

  • Guest
Re: ubuntu 10.04 avast problem
« Reply #6 on: July 20, 2010, 09:00:42 PM »
Shared memory is too short by default.
Do as root: sysctl -w kernel.shmmax=100000000

 ;)