** Changed in: willowng (Ubuntu)
Assignee: glenstewart (glen-stewart) => (unassigned)
--
willowng will not start
https://bugs.launchpad.net/bugs/313163
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
WillowNG 0.5 is now released, resolving this reported bug. See
https://launchpad.net/willowng to download this release.
** Changed in: willowng
Assignee: (unassigned) => glenstewart (glen-stewart)
** Changed in: willowng (Ubuntu)
Assignee: (unassigned) => glenstewart (glen-stewart)
**
Modifications to WillowNG are in the works, to resolve startup and
performance issues. A working prototype is already in testing. I'm now
focusing on administration issues related to the changes made to the
filtering engine.
This is an interesting project, as the original Willow and WillowNG bot
Behavior is still observed in Lucid.
--
willowng will not start
https://bugs.launchpad.net/bugs/313163
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mai
I have the same problem always saying the same message if click "yes" and if
run from terminal this is the message (either click yes or no):
Traceback (most recent call last):
File "/usr/bin/willowng-config", line 178, in on_mainwindow_destroy
gtk.main_quit()
RuntimeError: called outside of
Maybe this WillowNG internet filter startup problem is related to bug
#318766 (D-Bus policy needs checking)?
** Also affects: baltix
Importance: Undecided
Status: New
--
willowng will not start
https://bugs.launchpad.net/bugs/313163
You received this bug notification because you are a
Issue still there in Ubuntu 9.10
Each time you ask it to start the message keeps re-appearing and so
willowng won't start. Tried with gksudo willowng-config and still had
the error.
** Also affects: willowng (Ubuntu)
Importance: Undecided
Status: New
--
willowng will not start
https: