Thanks for persisting with this issue...I've found something on a virtual 
install of Natty that may be what you're seeing.  Some missed dependency.

More later...


On 03/08/2011 08:23 AM, Mark Cahill wrote:
> The exact traceback is as follows:
>
> Traceback (most recent call last):
>    File "/usr/bin/willowng-config", line 212, in<module>
>      foo = MainWindow()
>    File "/usr/bin/willowng-config", line 71, in __init__
>      os.execvp('willowng-config', ())
>    File "/usr/lib/python2.6/os.py", line 344, in execvp
>      _execvpe(file, args)
>    File "/usr/lib/python2.6/os.py", line 380, in _execvpe
>      func(fullname, *argrest)
> ValueError: execv() arg 2 must not be empty
>
> line 71 of /usr/bin/willowng-config reads:
>                  os.execvp('willowng-config', ())
>
> Per the Python documentation for the os module:
> "The various exec*() functions take a list of arguments for the new program 
> loaded into the process. In each case, the first of these arguments is passed 
> to the new program as its own name rather than as an argument a user may have 
> typed on a command line. For the C programmer, this is the argv[0] passed to 
> a program’s main(). For example, os.execv('/bin/echo', ['foo', 'bar']) will 
> only print bar on standard output; foo will seem to be ignored."
>
> Changing line 71 of /usr/bin/willowng-config to the following allows it to 
> continue:
>                  os.execvp('willowng-config', ['willowng-config'])
>
> This places us in the original state which caused this ticket to be
> opened, that is,
>
> "If I click on System/Administration/Content filter I get a message
> saying the following "Content filter not running! Start content
> filter?". I then click on yes (to start the filter). Then the message
> re-appears and unfortunately WillowNG will not start."
>
> Clicking no causes the following traceback:
> Traceback (most recent call last):
>    File "/usr/bin/willowng-config", line 200, in on_mainwindow_destroy
>      gtk.main_quit()
> RuntimeError: called outside of a mainloop
>
> Also, the process hangs until Ctrl-C is issued.
>

-- 
Associate.com - THE Place to Associate!                  http://freegroups.net
Is Your E-mail Group Here?  See http://freegroups.net/faq/your-group-here.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/313163

Title:
  [SOLVED] willowng will not start

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to