Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: Couldn't execute command: evolution Verify that this is a valid command

  1. #11
    Join Date
    Aug 2005
    Location
    Sydney
    Beans
    7

    Smile Re: Couldn't execute command: evolution Verify that this is a valid command

    Thanks Takkuso for taking the effort to come back and post your solution. Worked for me and saved me time/effort.

  2. #12
    Join Date
    May 2007
    Beans
    5

    Re: Couldn't execute command: evolution Verify that this is a valid command

    The real problem is that ACPI is getting confused; when you plug the AC power in it's triggering both a power event and a mail event. Here's what I see in /var/log/acpid when I plug the power in:

    [Thu Sep 11 00:11:56 2008] BEGIN HANDLER MESSAGES
    [Thu Sep 11 00:11:57 2008] END HANDLER MESSAGES
    [Thu Sep 11 00:11:57 2008] action exited with status 0
    [Thu Sep 11 00:11:57 2008] completed event "ac_adapter AC0 00000080 00000001"
    [Thu Sep 11 00:11:57 2008] received event "battery BAT0 00000080 00000001"
    [Thu Sep 11 00:11:57 2008] notifying client 5295[111:123]
    [Thu Sep 11 00:11:57 2008] notifying client 5442[0:0]
    [Thu Sep 11 00:11:57 2008] executing action "/etc/acpi/power.sh"
    [Thu Sep 11 00:11:57 2008] BEGIN HANDLER MESSAGES
    [Thu Sep 11 00:11:57 2008] END HANDLER MESSAGES
    [Thu Sep 11 00:11:57 2008] action exited with status 0
    [Thu Sep 11 00:11:57 2008] completed event "battery BAT0 00000080 00000001"
    [Thu Sep 11 00:11:57 2008] received event "hotkey ATKD 00000050 0000000a"
    [Thu Sep 11 00:11:57 2008] notifying client 5295[111:123]
    [Thu Sep 11 00:11:57 2008] notifying client 5442[0:0]
    [Thu Sep 11 00:11:57 2008] executing action "/etc/acpi/mailbtn.sh"
    [Thu Sep 11 00:11:57 2008] BEGIN HANDLER MESSAGES
    [Thu Sep 11 00:11:57 2008] END HANDLER MESSAGES
    [Thu Sep 11 00:11:57 2008] action exited with status 0
    [Thu Sep 11 00:11:57 2008] completed event "hotkey ATKD 00000050 0000000a"

    Note that in addition to running /etc/acpi/power.sh it runs /etc/acpi/mailbtn.sh. As a quick fix I deleted the contents of /etc/acpi/mailbtn.sh. The eeePc has no email button anyway, so it's no loss.

    This is probably better than disabling the preferred mail client.

  3. #13
    Join Date
    May 2005
    Location
    Scottsdale, AZ
    Beans
    43
    Distro
    Ubuntu 13.10 Saucy Salamander

    Re: Couldn't execute command: evolution Verify that this is a valid command

    Thanks Andy. You nailed the concern correctly. I also was having the same problem. I do have evolution installed so no error message, but just don't want it to start when I plug-in the AC adapter.

  4. #14
    Join Date
    Jul 2007
    Beans
    1

    Re: Couldn't execute command: evolution Verify that this is a valid command

    Quote Originally Posted by Andy Armstrong View Post
    "

    Note that in addition to running /etc/acpi/power.sh it runs /etc/acpi/mailbtn.sh. As a quick fix I deleted the contents of /etc/acpi/mailbtn.sh. The eeePc has no email button anyway, so it's no loss.

    This is probably better than disabling the preferred mail client.
    Thanks a lot, this has been driving me crazy.
    Still happens with 8.10.0, using array.org eeepc kernel version 2.6.27-7.

    It's less annoying when you don't have evolution installed as you can quickly dispatch the error message. What sucks is waiting for it to load every time you plug in your eee

  5. #15
    Join Date
    Oct 2005
    Beans
    7

    Re: Couldn't execute command: evolution Verify that this is a valid command

    This occurs because the asus-acpi module sends hotkey events when connecting to AC power with the wrong code (for the Eee; it's surely the right one on other Asus laptops).

    Comment out all lines in /etc/acpi/events/asus-mail (by prepending a #), and restart acpid with sudo /etc/init.d/acpid restart.

  6. #16
    Join Date
    Feb 2009
    Beans
    6

    Re: Couldn't execute command: evolution Verify that this is a valid command

    Quote Originally Posted by 3guk View Post
    This occurs because the asus-acpi module sends hotkey events when connecting to AC power with the wrong code (for the Eee; it's surely the right one on other Asus laptops).

    Comment out all lines in /etc/acpi/events/asus-mail (by prepending a #), and restart acpid with sudo /etc/init.d/acpid restart.
    Thanks this worked perfectly. I was really annoyed that this kept happening because I uninstalled the bloated evolution software.

Page 2 of 2 FirstFirst 12

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •