Sorry for not getting back with you. It appears that the new version of
Ubuntu corrects the problem I reported.
Mike
On 8/11/07, Lionel Le Folgoc <[EMAIL PROTECTED]> wrote:
>
> We are closing this bug report as it lacks the information, described in
> the previous comments, we need to investigat
We are closing this bug report as it lacks the information, described in
the previous comments, we need to investigate the problem further.
However, please reopen it if you can give us the missing information and
don't hesitate to submit bug reports in the future. To reopen the bug
report you can c
Hi,
Is this bug still present on feisty (or gutsy)?
Thanks.
--
last round of updates and now firestarter will not start
https://bugs.launchpad.net/bugs/47662
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ub
I don't think that it is bug 30291. The last upgrade (6.10) seams to
have broken firestarter. It worked fine before the upgrade, and
immediately after the upgrade it didn't. I did some background checking
on my system. It appears that the only way to run the program now is to
enter a terminal (
Could this be bug 30291?
--
last round of updates and now firestarter will not start
https://launchpad.net/bugs/47662
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
If you will look at the initial comments, you will see that this was tried
(gksu, gksudo, etc.). This is STILL a problem, and every time I restart GDM, I
must input the xhost+local command in a terminal to start firestarter.
This was NOT a problem until release day. (murphy's law or what?)
--
Try gksudo?
--
last round of updates and now firestarter will not start
https://launchpad.net/bugs/47662
--
ubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
