Author Topic: Mac beta (35600) constantly needs to be repaired  (Read 4401 times)

0 Members and 1 Guest are viewing this topic.

Offline Uh_Clem

  • Jr. Member
  • **
  • Posts: 27
Mac beta (35600) constantly needs to be repaired
« on: November 20, 2011, 06:13:16 AM »
Since installing beta 35600, I keep getting a message that avast! needs to be repaired.  Clicking the Repair button successfully revives the application but it seems likely that avast! has not been providing protection for some time.  Updates occur regularly and appear to be successful.  The first indication of a problem is when I select "Show Shield Statistics" from the drop-down menu and get a display that is essentially blank.  When I select "Open avast!", I get the repair message.  It has happened four times so far.  Since I've only been checking irregularly up to now, I can't really say how often it actually breaks down.  More news as it develops...

Update:  The repair is required after every reboot.
« Last Edit: November 20, 2011, 11:41:48 PM by Uh_Clem »

Offline Uh_Clem

  • Jr. Member
  • **
  • Posts: 27
Re: Mac beta (35600) constantly needs to be repaired
« Reply #1 on: November 20, 2011, 06:20:11 AM »
Checking the system log shows the following messages repeating until the avast! repair takes place:

Nov 19 20:14:26 ek-macbkpro com.apple.launchd[1] (com.avast.proxy): Throttling respawn: Will start in 5 seconds
Nov 19 20:14:26 ek-macbkpro proxy[52138]: Error: Packet forwarding KEXT not loaded
Nov 19 20:14:26 ek-macbkpro proxy[52138]: Fatal error. Exiting.
Nov 19 20:14:31 ek-macbkpro proxy[52155]: Starting daemon.
Nov 19 20:14:31 ek-macbkpro proxy[52155]: kextstat -l -b com.avast.PacketForwarder | grep com.avast.PacketForwarder error (1)
Nov 19 20:14:36: --- last message repeated 4 times ---
Nov 19 20:14:36 ek-macbkpro proxy[52155]: Error: Packet forwarding KEXT not loaded
Nov 19 20:14:36 ek-macbkpro proxy[52155]: Fatal error. Exiting.
Nov 19 20:14:36 ek-macbkpro com.apple.launchd[1] (com.avast.proxy): Throttling respawn: Will start in 5 seconds
Nov 19 20:14:41 ek-macbkpro proxy[52172]: Starting daemon.
Nov 19 20:14:41 ek-macbkpro proxy[52172]: kextstat -l -b com.avast.PacketForwarder | grep com.avast.PacketForwarder error (1)
Nov 19 20:14:46: --- last message repeated 4 times ---
Nov 19 20:14:46 ek-macbkpro proxy[52172]: Error: Packet forwarding KEXT not loaded
Nov 19 20:14:46 ek-macbkpro proxy[52172]: Fatal error. Exiting.
Nov 19 20:14:46 ek-macbkpro com.apple.launchd[1] (com.avast.proxy): Throttling respawn: Will start in 5 seconds
Nov 19 20:14:51 ek-macbkpro proxy[52188]: Starting daemon.
Nov 19 20:14:51 ek-macbkpro proxy[52188]: kextstat -l -b com.avast.PacketForwarder | grep com.avast.PacketForwarder error (1)

Offline zilog

  • Avast team
  • Advanced Poster
  • *
  • Posts: 957
  • or #f0; daa; add a,#a0; adc a,#40
Re: Mac beta (35600) constantly needs to be repaired
« Reply #2 on: November 21, 2011, 01:33:49 PM »
Checking the system log shows the following messages repeating until the avast! repair takes place:

Nov 19 20:14:26 ek-macbkpro com.apple.launchd[1] (com.avast.proxy): Throttling respawn: Will start in 5 seconds
Nov 19 20:14:26 ek-macbkpro proxy[52138]: Error: Packet forwarding KEXT not loaded
Nov 19 20:14:26 ek-macbkpro proxy[52138]: Fatal error. Exiting.
Nov 19 20:14:31 ek-macbkpro proxy[52155]: Starting daemon.
Nov 19 20:14:31 ek-macbkpro proxy[52155]: kextstat -l -b com.avast.PacketForwarder | grep com.avast.PacketForwarder error (1)
Nov 19 20:14:36: --- last message repeated 4 times ---
Nov 19 20:14:36 ek-macbkpro proxy[52155]: Error: Packet forwarding KEXT not loaded
Nov 19 20:14:36 ek-macbkpro proxy[52155]: Fatal error. Exiting.
Nov 19 20:14:36 ek-macbkpro com.apple.launchd[1] (com.avast.proxy): Throttling respawn: Will start in 5 seconds
Nov 19 20:14:41 ek-macbkpro proxy[52172]: Starting daemon.
Nov 19 20:14:41 ek-macbkpro proxy[52172]: kextstat -l -b com.avast.PacketForwarder | grep com.avast.PacketForwarder error (1)
Nov 19 20:14:46: --- last message repeated 4 times ---
Nov 19 20:14:46 ek-macbkpro proxy[52172]: Error: Packet forwarding KEXT not loaded
Nov 19 20:14:46 ek-macbkpro proxy[52172]: Fatal error. Exiting.
Nov 19 20:14:46 ek-macbkpro com.apple.launchd[1] (com.avast.proxy): Throttling respawn: Will start in 5 seconds
Nov 19 20:14:51 ek-macbkpro proxy[52188]: Starting daemon.
Nov 19 20:14:51 ek-macbkpro proxy[52188]: kextstat -l -b com.avast.PacketForwarder | grep com.avast.PacketForwarder error (1)


Hallo,
this is probably known bug, which was already fixed in 35600b (it's the package which is available for download currently on this forum). So just try to update to the new version. And in the case that the problem is still persisting, let me know.

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

Offline Uh_Clem

  • Jr. Member
  • **
  • Posts: 27
Re: Mac beta (35600) constantly needs to be repaired
« Reply #3 on: November 22, 2011, 01:52:45 AM »
PC, 35600b did indeed fix the problem!  Thanks.

It would be helpful if there were some posting of any such update available -- especially on the GUI window -- to help avoid your spending time on redundant issues and my running unnecessary tests to try to troubleshoot what turns out to be a known (and resolved) bug.  I now have three iterations of what is called 35600 -- the original 35600, something downloaded as 35600-2 but displaying 35600 on the Application Version line, and the latest 35600b which downloads as 35600 but displays the 'b' in the Version.  Each of the latter two fixed a problem I was having and I wouldn't have known either existed by looking anywhere on the forum or in the application.

Now let's see what else I can find... 8)

Offline zilog

  • Avast team
  • Advanced Poster
  • *
  • Posts: 957
  • or #f0; daa; add a,#a0; adc a,#40
Re: Mac beta (35600) constantly needs to be repaired
« Reply #4 on: November 23, 2011, 12:30:02 PM »
PC, 35600b did indeed fix the problem!  Thanks.

It would be helpful if there were some posting of any such update available -- especially on the GUI window -- to help avoid your spending time on redundant issues and my running unnecessary tests to try to troubleshoot what turns out to be a known (and resolved) bug.  I now have three iterations of what is called 35600 -- the original 35600, something downloaded as 35600-2 but displaying 35600 on the Application Version line, and the latest 35600b which downloads as 35600 but displays the 'b' in the Version.  Each of the latter two fixed a problem I was having and I wouldn't have known either existed by looking anywhere on the forum or in the application.

Now let's see what else I can find... 8)

Hallo,
you're right. The 35600 was fixed in 2 consecutive iterations, the fist one solved the lock-up, the second one the problem with kext loading. Because the bug vas very rare and there was only one known victim (you:), I decided to adjust the present beta, to avoid confusion between all those unaffected users.

You stated that everything is OK, so I supposed you have installed the second iteration, that was the misunderstanding. Btw. you seem to be pretty pedantic beta-tester, able to create pretty acurate reports, and that's really good and appreciated, thanks and keep testing!

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