zeitgeist team mailing list archive
-
zeitgeist team
-
Mailing list archive
-
Message #00620
Re: [Bug 497140] Re: zeitgeist-daemon errors with "No module named notify"
Oh, apparently that was the issue. Silly me. I didn't realize you had to run
./autogen.sh. I did run ./configure to make sure that wasn't the issue, but
apparently that wasn't enough.
Thanks!
On Tue, Dec 15, 2009 at 4:05 PM, Siegfried Gevatter <rainct@xxxxxxxxxx>wrote:
> 2009/12/15 Markus Korn <thekorn@xxxxxx>:
> > Siegfried, do yo happen to know what's going on here.
>
> No, not really.
>
>
> Jamal, have you run ./autogen.sh before running "make; sudo make install"?
>
> --
> zeitgeist-daemon errors with "No module named notify"
> https://bugs.launchpad.net/bugs/497140
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
zeitgeist-daemon errors with "No module named notify"
https://bugs.launchpad.net/bugs/497140
You received this bug notification because you are a member of Zeitgeist
Developers, which is the registrant for Zeitgeist Framework.
Status in Zeitgeist Framework: Invalid
Bug description:
make install doesn't seem to be copying _zeitgeist/engine/notify.py as it can't be found by zeitgeist-daemon. Copying it manually to /usr/local/share/zeitgeist/_zeitgeist/engine/ fixes the issue.
Traceback (most recent call last):
File "/usr/local/bin/zeitgeist-daemon", line 47, in <module>
from _zeitgeist.engine.remote import RemoteInterface
File "/usr/local/share/zeitgeist/_zeitgeist/engine/remote.py", line 28, in <module>
from _zeitgeist.engine.notify import MonitorManager
ImportError: No module named notify
References