This is happening to me too with Hardy. Very annoying thing, when using
"network-admin" to configure an interface (wireless), two instances of
SystemToolsBackend.pl get executed and one of them seems to enter a busy
loop for about one minute, and configuration settings don't seem to
apply completel
Marking unconfirmed, that works fine for me. Somebody having the problem
should probably forward it upstream
** Changed in: system-tools-backends (Ubuntu)
Importance: Undecided => Low
Status: Needs Info => Unconfirmed
** Also affects: system-tools-backends (upstream)
Importance: Unde
Thank you for your bug. What do you call a busy loop? How do you notice
it? Are you speaking about network-manager or network-admin? Maybe you
could stop the running instance and restart one by running "sudo
/usr/share/system-tools-backends-2.0/scripts/SystemToolsBackends.pl -n
--report" and note w
Hi,
after re-starting the above-cited script I get the enclosed report (a bit
lengthy :-). Then I try to start network-admin again from the gnome system
administration desktop menu (network-manager version = 0.6.3-2ubuntu6), which
results in a high cpu activity caued by the process executing the
This is happening to me too with Hardy. Very annoying thing, when using
"network-admin" to configure an interface (wireless), two instances of
SystemToolsBackend.pl get executed and one of them seems to enter a busy
loop for about one minute, and configuration settings don't seem to
apply completel
Thank you for your bug. What do you call a busy loop? How do you notice
it? Are you speaking about network-manager or network-admin? Maybe you
could stop the running instance and restart one by running "sudo
/usr/share/system-tools-backends-2.0/scripts/SystemToolsBackends.pl -n
--report" and note w
Hi,
after re-starting the above-cited script I get the enclosed report (a bit
lengthy :-). Then I try to start network-admin again from the gnome system
administration desktop menu (network-manager version = 0.6.3-2ubuntu6), which
results in a high cpu activity caued by the process executing the
Marking unconfirmed, that works fine for me. Somebody having the problem
should probably forward it upstream
** Changed in: system-tools-backends (Ubuntu)
Importance: Undecided => Low
Status: Needs Info => Unconfirmed
** Also affects: system-tools-backends (upstream)
Importance: Unde
This is happening to me too with Hardy. Very annoying thing, when using
"network-admin" to configure an interface (wireless), two instances of
SystemToolsBackend.pl get executed and one of them seems to enter a busy
loop for about one minute, and configuration settings don't seem to
apply completel
Thank you for your bug. What do you call a busy loop? How do you notice
it? Are you speaking about network-manager or network-admin? Maybe you
could stop the running instance and restart one by running "sudo
/usr/share/system-tools-backends-2.0/scripts/SystemToolsBackends.pl -n
--report" and note w
Hi,
after re-starting the above-cited script I get the enclosed report (a bit
lengthy :-). Then I try to start network-admin again from the gnome system
administration desktop menu (network-manager version = 0.6.3-2ubuntu6), which
results in a high cpu activity caued by the process executing the
Marking unconfirmed, that works fine for me. Somebody having the problem
should probably forward it upstream
** Changed in: system-tools-backends (Ubuntu)
Importance: Undecided => Low
Status: Needs Info => Unconfirmed
** Also affects: system-tools-backends (upstream)
Importance: Unde
This is happening to me too with Hardy. Very annoying thing, when using
"network-admin" to configure an interface (wireless), two instances of
SystemToolsBackend.pl get executed and one of them seems to enter a busy
loop for about one minute, and configuration settings don't seem to
apply completel
Marking unconfirmed, that works fine for me. Somebody having the problem
should probably forward it upstream
** Changed in: system-tools-backends (Ubuntu)
Importance: Undecided => Low
Status: Needs Info => Unconfirmed
** Also affects: system-tools-backends (upstream)
Importance: Unde
Thank you for your bug. What do you call a busy loop? How do you notice
it? Are you speaking about network-manager or network-admin? Maybe you
could stop the running instance and restart one by running "sudo
/usr/share/system-tools-backends-2.0/scripts/SystemToolsBackends.pl -n
--report" and note w
Hi,
after re-starting the above-cited script I get the enclosed report (a bit
lengthy :-). Then I try to start network-admin again from the gnome system
administration desktop menu (network-manager version = 0.6.3-2ubuntu6), which
results in a high cpu activity caued by the process executing the
Thank you for your bug. What do you call a busy loop? How do you notice
it? Are you speaking about network-manager or network-admin? Maybe you
could stop the running instance and restart one by running "sudo
/usr/share/system-tools-backends-2.0/scripts/SystemToolsBackends.pl -n
--report" and note w
Hi,
after re-starting the above-cited script I get the enclosed report (a bit
lengthy :-). Then I try to start network-admin again from the gnome system
administration desktop menu (network-manager version = 0.6.3-2ubuntu6), which
results in a high cpu activity caued by the process executing the
This is happening to me too with Hardy. Very annoying thing, when using
"network-admin" to configure an interface (wireless), two instances of
SystemToolsBackend.pl get executed and one of them seems to enter a busy
loop for about one minute, and configuration settings don't seem to
apply completel
Marking unconfirmed, that works fine for me. Somebody having the problem
should probably forward it upstream
** Changed in: system-tools-backends (Ubuntu)
Importance: Undecided => Low
Status: Needs Info => Unconfirmed
** Also affects: system-tools-backends (upstream)
Importance: Unde
Thank you for your bug. What do you call a busy loop? How do you notice
it? Are you speaking about network-manager or network-admin? Maybe you
could stop the running instance and restart one by running "sudo
/usr/share/system-tools-backends-2.0/scripts/SystemToolsBackends.pl -n
--report" and note w
Hi,
after re-starting the above-cited script I get the enclosed report (a bit
lengthy :-). Then I try to start network-admin again from the gnome system
administration desktop menu (network-manager version = 0.6.3-2ubuntu6), which
results in a high cpu activity caued by the process executing the
Marking unconfirmed, that works fine for me. Somebody having the problem
should probably forward it upstream
** Changed in: system-tools-backends (Ubuntu)
Importance: Undecided => Low
Status: Needs Info => Unconfirmed
** Also affects: system-tools-backends (upstream)
Importance: Unde
This is happening to me too with Hardy. Very annoying thing, when using
"network-admin" to configure an interface (wireless), two instances of
SystemToolsBackend.pl get executed and one of them seems to enter a busy
loop for about one minute, and configuration settings don't seem to
apply completel
24 matches
Mail list logo
