-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
More info:
Am Do den 17. Mai 2018 um 8:08 schrieb Klaus Ethgen:
> But what I see is, that dhcpcd seems to delay IPv4 setup. I believe that
> this is stopping wicd from working correct.
When I configure dhcpcd to only configure ipv4 it works. But o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
I have another strange problem that I found today.
I use wicd on my laptop and it was working fine on debian before.
Now, when I use it on Gentoo with exact the same config, it doesn't work
in a strange way. The network (wired or wireless) is
On my amd64 laptop, on resume from hibernation, wicd almost always
fails to restart. This problem goes back to when I set up the machine,
over a year ago, but it seems to have gotten a lot worse in the last
month or so.
I'm using openrc and sys-power/hibernate-script. I run mostly stable;
AFAIK
On 6/25/12 6:01 PM, Neil Bothwick wrote:
On Mon, 25 Jun 2012 11:20:42 -0400, Valmor de Almeida wrote:
udev persistent rules strike again
The contents of /var/log/wicd/wicd.log below do indicate a mess up
with eth1 and eth0. Any idea on how to fix this?
Yep. All I needed to do was to change
On Mon, 25 Jun 2012 11:20:42 -0400, Valmor de Almeida wrote:
> >> udev persistent rules strike again
> >
> > The contents of /var/log/wicd/wicd.log below do indicate a mess up
> > with eth1 and eth0. Any idea on how to fix this?
>
> Yep. All I needed to do was to change the wired interface fr
On Mon, Jun 25, 2012 at 10:45 AM, Valmor de Almeida
wrote:
> On 6/24/12 7:24 PM, Alan McKinnon wrote:
>> On Sun, 24 Jun 2012 19:04:25 -0400
>> Valmor de Almeida wrote:
>>
>>>
>>> Hello,
>>>
>>> I am having a hard time getting wicd to work on gentoo guest. Thought
>>> that it was a simple matter o
On 6/24/12 7:24 PM, Alan McKinnon wrote:
> On Sun, 24 Jun 2012 19:04:25 -0400
> Valmor de Almeida wrote:
>
>>
>> Hello,
>>
>> I am having a hard time getting wicd to work on gentoo guest. Thought
>> that it was a simple matter of emerge and run wicd-client -n to
>> configure. I have compiled the c
On Sun, 24 Jun 2012 19:04:25 -0400
Valmor de Almeida wrote:
>
> Hello,
>
> I am having a hard time getting wicd to work on gentoo guest. Thought
> that it was a simple matter of emerge and run wicd-client -n to
> configure. I have compiled the correct ethernet driver in the kernel
> (at least
Hello,
I am having a hard time getting wicd to work on gentoo guest. Thought
that it was a simple matter of emerge and run wicd-client -n to
configure. I have compiled the correct ethernet driver in the kernel (at
least I think so). Does anyone have some experience with this or could
point m
On Mon, 27 Feb 2012 15:58:59 +
James Broadhead wrote:
> On 26 February 2012 17:00, Dan Johansson wrote:
> > On Sunday 26 February 2012 13.43:13 Dan Johansson wrote:
> >> On Sunday 26 February 2012 10.52:58 Willie WY Wong wrote:
> >> >
> >> > You guys are almost certainly running into the sam
On 26 February 2012 17:00, Dan Johansson wrote:
> On Sunday 26 February 2012 13.43:13 Dan Johansson wrote:
>> On Sunday 26 February 2012 10.52:58 Willie WY Wong wrote:
>> >
>> > You guys are almost certainly running into the same problem as the one
>> > I mentioned in the thread I just started.
>>
On Sun, Feb 26, 2012 at 07:09:26PM +0100, Penguin Lover Willie WY Wong squawked:
> I wonder if it would be advisable to file a bug to have wicd provide
> net? (Is there any reason why this would be a bad idea?)
>
Ah, in fact it seems that having wicd provide net is already in the
works:
https://
On Sun, Feb 26, 2012 at 06:00:46PM +0100, Penguin Lover Dan Johansson squawked:
> > Yes, that was it, killing the dhcpcd made it possible to bring the
> > interface up and associate with the AP.
> > As openrc was one of the packages upgraded yesterday (0.9.8.4 -> 0.9.9.1) I
> > assume (guess) tha
On Sunday 26 February 2012 13.43:13 Dan Johansson wrote:
> On Sunday 26 February 2012 10.52:58 Willie WY Wong wrote:
> > On Sun, Feb 26, 2012 at 11:34:01AM +0200, Penguin Lover Alan McKinnon
> > squawked:
> > > On Sun, 26 Feb 2012 10:19:56 +0100
> > > Dan Johansson wrote:
> > > > After running an
On Sunday 26 February 2012 10.52:58 Willie WY Wong wrote:
> On Sun, Feb 26, 2012 at 11:34:01AM +0200, Penguin Lover Alan McKinnon
> squawked:
> > On Sun, 26 Feb 2012 10:19:56 +0100
> > Dan Johansson wrote:
> > > After running an update yesterday (about 50 packages) on my ~x86
> > > laptop, wicd s
On Sun, Feb 26, 2012 at 11:34:01AM +0200, Penguin Lover Alan McKinnon squawked:
> On Sun, 26 Feb 2012 10:19:56 +0100
> Dan Johansson wrote:
> > After running an update yesterday (about 50 packages) on my ~x86
> > laptop, wicd stopped working, and no wicd was not updated neither was
> > any other n
On Sun, 26 Feb 2012 10:19:56 +0100
Dan Johansson wrote:
> Hi,
>
> After running an update yesterday (about 50 packages) on my ~x86
> laptop, wicd stopped working, and no wicd was not updated neither was
> any other network related packages. Today after a reboot my wireless
> network refused to s
Hi,
After running an update yesterday (about 50 packages) on my ~x86 laptop, wicd
stopped working, and no wicd was not updated neither was any other network
related packages.
Today after a reboot my wireless network refused to start from wicd, starting
it manually works.
This is a part of the w
On Mon, Dec 26, 2011 at 8:19 AM, Fernando Antunes wrote:
>
>
> On Sun, Dec 25, 2011 at 4:01 PM, Michael Mol wrote:
>
>> So, after having plenty of trouble working on getting Gentoo set up to
>> work with my new laptop, I'm finally able to run 'iwlist wlan0 scan'
>> and see the 15 or so cells in i
On Sun, Dec 25, 2011 at 4:01 PM, Michael Mol wrote:
> So, after having plenty of trouble working on getting Gentoo set up to
> work with my new laptop, I'm finally able to run 'iwlist wlan0 scan'
> and see the 15 or so cells in immediate area.
>
> Rather than going straight wpa_supplicant or usin
So, after having plenty of trouble working on getting Gentoo set up to
work with my new laptop, I'm finally able to run 'iwlist wlan0 scan'
and see the 15 or so cells in immediate area.
Rather than going straight wpa_supplicant or using NetworkManager on
this machine, I thought I'd give wicd a try
On Nov 28, 2011 6:18 AM, "Neil Bothwick" wrote:
>
> On Sun, 27 Nov 2011 13:27:59 +0100, Dan Johansson wrote:
>
> > I had the same issue after upgrading net-tools, wicd stoped working.
> > While googling for a solution I found a workaround: Use the "ioctl"
> > backend instead of the "external" back
On Sun, 27 Nov 2011 13:27:59 +0100, Dan Johansson wrote:
> I had the same issue after upgrading net-tools, wicd stoped working.
> While googling for a solution I found a workaround: Use the "ioctl"
> backend instead of the "external" backend.
> For me this workaround works.
>
That explains why I
On Sun, Nov 27 2011, Dan Johansson wrote:
> On Sunday 27 November 2011 02.02:54 Paul Hartman wrote:
>> On Fri, Nov 25, 2011 at 4:58 PM, Allan Gottlieb wrote:
>> > In the last day or two wicd broke badly due to a net-tools upgrade.
>> >
>> > The recommended workarounds are to specify USE=old-outp
On Sunday 27 November 2011 02.02:54 Paul Hartman wrote:
> On Fri, Nov 25, 2011 at 4:58 PM, Allan Gottlieb wrote:
> > In the last day or two wicd broke badly due to a net-tools upgrade.
> >
> > The recommended workarounds are to specify USE=old-output
> > for net-tools or to downgrade net-tools o
On Fri, Nov 25, 2011 at 4:58 PM, Allan Gottlieb wrote:
> In the last day or two wicd broke badly due to a net-tools upgrade.
>
> The recommended workarounds are to specify USE=old-output
> for net-tools or to downgrade net-tools one version (I am ~amd64).
>
> Neither of these have helped me. Wicd
On Fri, Nov 25 2011, Mark Knecht wrote:
> On Fri, Nov 25, 2011 at 2:58 PM, Allan Gottlieb wrote:
>> In the last day or two wicd broke badly due to a net-tools upgrade.
>>
>> The recommended workarounds are to specify USE=old-output
>> for net-tools or to downgrade net-tools one version (I am ~amd
On Fri, Nov 25, 2011 at 2:58 PM, Allan Gottlieb wrote:
> In the last day or two wicd broke badly due to a net-tools upgrade.
>
> The recommended workarounds are to specify USE=old-output
> for net-tools or to downgrade net-tools one version (I am ~amd64).
>
> Neither of these have helped me. Wicd
In the last day or two wicd broke badly due to a net-tools upgrade.
The recommended workarounds are to specify USE=old-output
for net-tools or to downgrade net-tools one version (I am ~amd64).
Neither of these have helped me. Wicd cannot start either the
wired or wireless interface.
When I type
On Tuesday 05 Jul 2011 09:32:44 Peter Weilbacher wrote:
> Since yesterday I cannot use wicd any more to get a wireless connection
> (wired still works fine). I think this has to do with a dbus update, but
> I'm not sure.
If you have emerged python recently and switched to 2.7, did you remember to
On Tuesday 05 July 2011 10:32:44 Peter Weilbacher did opine thusly:
> Since yesterday I cannot use wicd any more to get a wireless
> connection (wired still works fine). I think this has to do with a
> dbus update, but I'm not sure. I have done several restarts,
> re-emerged all relevant packages (
Since yesterday I cannot use wicd any more to get a wireless connection (wired
still works fine). I think this has to do with a dbus update, but I'm not sure.
I have done several restarts, re-emerged all relevant packages (dbus,
dbus-python,
wicd) but still it stops shortly after clicking the con
Neil Bothwick writes:
> On Wed, 01 Dec 2010 08:46:20 -0500, Allan Gottlieb wrote:
>
>> However version 1.7.1 (with the fix) hasn't been released yet.
>> I am surprised since the released version doesn't work with
>> python 2.7.
>
> 1.7.1_beta2 is in portage and working with 2.7.
Yes indeed it is
On Wed, 01 Dec 2010 08:46:20 -0500, Allan Gottlieb wrote:
> However version 1.7.1 (with the fix) hasn't been released yet.
> I am surprised since the released version doesn't work with
> python 2.7.
1.7.1_beta2 is in portage and working with 2.7.
--
Neil Bothwick
Everywhere is walking distanc
Alan McKinnon writes:
> Apparently, though unproven, at 15:46 on Wednesday 01 December 2010, Allan
> Gottlieb did opine thusly:
>
>> However version 1.7.1 (with the fix) hasn't been released yet.
>> I am surprised since the released version doesn't work with
>> python 2.7.
>>
>> Should I file a
Apparently, though unproven, at 15:46 on Wednesday 01 December 2010, Allan
Gottlieb did opine thusly:
> However version 1.7.1 (with the fix) hasn't been released yet.
> I am surprised since the released version doesn't work with
> python 2.7.
>
> Should I file a gentoo bug to have them apply the
Alan McKinnon writes:
> Apparently, though unproven, at 14:51 on Wednesday 01 December 2010, Allan
> Gottlieb did opine thusly:
>
>> Yesterday my ~amd64 machine updated python. I ran the
>> python-updater and all seemed well.
>>
>> However, this morning wicd is failing. The first indication w
Apparently, though unproven, at 14:51 on Wednesday 01 December 2010, Allan
Gottlieb did opine thusly:
> Yesterday my ~amd64 machine updated python. I ran the
> python-updater and all seemed well.
>
> However, this morning wicd is failing. The first indication was a
> never-seen-before popup st
Yesterday my ~amd64 machine updated python. I ran the
python-updater and all seemed well.
However, this morning wicd is failing. The first indication was a
never-seen-before popup stating "Granted permissions without asking for
password" (full text below)
I re-installed wicd in case python-upda
Neil Bothwick writes:
> On Mon, 08 Nov 2010 18:48:09 -0500, Allan Gottlieb wrote:
>
>> I am a happy user of wicd, but recently a problem has arisen.
>>
>> The daemon starts and runs and at home it connects me to the wireless
>> network.
>>
>> The problem is that the applet icon no longer appear
Alan McKinnon writes:
> Apparently, though unproven, at 01:48 on Tuesday 09 November 2010, Allan
> Gottlieb did opine thusly:
>
>> I am a happy user of wicd, but recently a problem has arisen.
>>
>> The daemon starts and runs and at home it connects me to the wireless
>> network.
>>
>> The pro
Apparently, though unproven, at 01:48 on Tuesday 09 November 2010, Allan
Gottlieb did opine thusly:
> I am a happy user of wicd, but recently a problem has arisen.
>
> The daemon starts and runs and at home it connects me to the wireless
> network.
>
> The problem is that the applet icon no lon
On Mon, 08 Nov 2010 18:48:09 -0500, Allan Gottlieb wrote:
> I am a happy user of wicd, but recently a problem has arisen.
>
> The daemon starts and runs and at home it connects me to the wireless
> network.
>
> The problem is that the applet icon no longer appears in my gnome
> panel.
Try runni
I am a happy user of wicd, but recently a problem has arisen.
The daemon starts and runs and at home it connects me to the wireless
network.
The problem is that the applet icon no longer appears in my gnome panel.
As I result I have no easy way to connect to another network.
I checked main-menu
On Wednesday 25 Feb 2009, Neil Bothwick wrote:
> On Wed, 25 Feb 2009 19:01:20 +0700, Robin Atwood wrote:
> > I have just upgraded my laptop to kernel 2.2.28-r2 and have enabled the
> > ath5k drivers for its Aetheros PC wireless card. Using the scripts to
> > activate net.wlan0 works fine and the wi
On Wed, 25 Feb 2009 19:01:20 +0700, Robin Atwood wrote:
> I have just upgraded my laptop to kernel 2.2.28-r2 and have enabled the
> ath5k drivers for its Aetheros PC wireless card. Using the scripts to
> activate net.wlan0 works fine and the wicd client can see the interface
> correctly. But when
On Wednesday 25 Feb 2009, Saphirus Sage wrote:
> On Feb 25, 2009, at 10:01 AM, Robin Atwood
>
> wrote:
> > On Wednesday 25 Feb 2009, Saphirus Sage wrote:
> >> Robin Atwood wrote:
> >>> I have just upgraded my laptop to kernel 2.2.28-r2 and have
> >>> enabled the
> >>> ath5k drivers for its Aethero
On Feb 25, 2009, at 10:01 AM, Robin Atwood
wrote:
On Wednesday 25 Feb 2009, Saphirus Sage wrote:
Robin Atwood wrote:
I have just upgraded my laptop to kernel 2.2.28-r2 and have
enabled the
ath5k drivers for its Aetheros PC wireless card. Using the scripts
to
activate net.wlan0 works f
On Wednesday 25 Feb 2009, Saphirus Sage wrote:
> Robin Atwood wrote:
> > I have just upgraded my laptop to kernel 2.2.28-r2 and have enabled the
> > ath5k drivers for its Aetheros PC wireless card. Using the scripts to
> > activate net.wlan0 works fine and the wicd client can see the interface
> >
Robin Atwood wrote:
> I have just upgraded my laptop to kernel 2.2.28-r2 and have enabled the ath5k
> drivers for its Aetheros PC wireless card. Using the scripts to activate
> net.wlan0 works fine and the wicd client can see the interface correctly. But
> when I try to activate wlan0 with wicd
I have just upgraded my laptop to kernel 2.2.28-r2 and have enabled the ath5k
drivers for its Aetheros PC wireless card. Using the scripts to activate
net.wlan0 works fine and the wicd client can see the interface correctly. But
when I try to activate wlan0 with wicd it repeatedly fails. I still
On Thu, 19 Feb 2009 11:11:04 +0800, Chuanwen Wu wrote:
> > It looks like the dependencies are wrong,have you filed a bug?
> Not yet, do you mean in bugzilla?
Yes
--
Neil Bothwick
Top Oxymorons Number 9: Political science
signature.asc
Description: PGP signature
>
> It looks like the dependencies are wrong,have you filed a bug?
Not yet, do you mean in bugzilla?
--
wcw
On Wed, 18 Feb 2009 13:46:30 -0200, Alejandro wrote:
> Are you installing wicd from portage?
Yes, and it works fine. But that could be because that unspecified
dependencies were pulled in by something else.
--
Neil Bothwick
"I laugh in the face of danger, then I hide until it goes away"
sig
2009/2/18 Neil Bothwick
> On Wed, 18 Feb 2009 22:24:15 +0800, Chuanwen Wu wrote:
>
> > > Do you have pygobject installed?
> >
> > I have updated pygobject to 2.14.2, then updated dbus-python to
> > 0.82.4, now the problem is fixed :)
>
> It looks like the dependencies are wrong,have you filed a b
On Wed, 18 Feb 2009 22:24:15 +0800, Chuanwen Wu wrote:
> > Do you have pygobject installed?
>
> I have updated pygobject to 2.14.2, then updated dbus-python to
> 0.82.4, now the problem is fixed :)
It looks like the dependencies are wrong,have you filed a bug?
--
Neil Bothwick
Yes, I am an
Hi, thanks for your tips!
> Do you have pygobject installed?
I have updated pygobject to 2.14.2, then updated dbus-python to
0.82.4, now the problem is fixed :)
--
wcw
On Tue, 17 Feb 2009 23:51:39 +0800, Chuanwen Wu wrote:
> # wicd
> Traceback (most recent call last):
> File "/usr/lib/wicd/wicd-daemon.py", line 45, in
> import gobject
> ImportError: No module named gobject
Do you have pygobject installed?
--
Neil Bothwick
If you think that there is g
Hi,
Several day ago, someone in this list recommended wicd to configure
the net interface. And I tried it but failed.
# wicd
Traceback (most recent call last):
File "/usr/lib/wicd/wicd-daemon.py", line 45, in
import gobject
ImportError: No module named gobject
# wicd-client
Traceback (most
puyhon-updater solved my problem.
Cheers,
Arnau
Hi,
after changing some use and removing some packages
from /etc/portage/package.keywords, I get this error when I run wicd
aplication (gtk based).
I tried to rebuild pygtk, but did not help.
I only found some old solution in forums, talking about python 2.4.
I'm on python 2.5.2.
On Sat, 31 Jan 2009 14:33:09 -0500
Saphirus Sage wrote:
> You could just use iwconfig, set up the interface for WEP from the
> command line, and join the network with "dhcpcd "
yes, or I could also use "scripts"... but I'd like to have wicd
working at 100%. it's a network manager, and should be
On Jan 31, 2009, at 2:35 PM, Arnau Bria wrote:
On Sat, 31 Jan 2009 18:01:54 +
Neil Bothwick wrote:
Hi,
You need to set the interface name in the preferences. It's probably
set to wlan0 now, when you are using wlan1.
now it hangs at validating authentication... I see all newts, but I
On Sat, 31 Jan 2009 19:35:59 +
Arnau Bria wrote:
> Any idea?
Really strange, going to contact wicd list.
If I set key in command line:
iwconfig wlan1 key open s:FX
then wicd is able to connect...
Thanks,
Arnau
On Sat, 31 Jan 2009 18:01:54 +
Neil Bothwick wrote:
Hi,
> You need to set the interface name in the preferences. It's probably
> set to wlan0 now, when you are using wlan1.
now it hangs at validating authentication... I see all newts, but I
cannot conect.
I set WEP encription, passphrase, b
On Sat, 31 Jan 2009 18:01:54 +
Neil Bothwick wrote:
> On Sun, 1 Feb 2009 01:52:17 +, Arnau Bria wrote:
>
> > Maybe I did not explain myself correctly, but my biggest problem is
> > that I do not see any wireless interface/netwrok... only my wired
> > one is avalible
>
> You need to s
On Sun, 1 Feb 2009 01:52:17 +, Arnau Bria wrote:
> Maybe I did not explain myself correctly, but my biggest problem is
> that I do not see any wireless interface/netwrok... only my wired one
> is avalible
You need to set the interface name in the preferences. It's probably set
to wlan0 no
On Sat, 31 Jan 2009 12:32:33 -0500
Saphirus Sage wrote:
Hi,
> Just click the tab next to each BSSID, and check "enable
> encryption". Then, click the tab on what type of encryption, select
> WEP(hex), as ASCII support is a bit limited. Enter in the relevent
> information and join the network.
Ma
On Jan 31, 2009, at 7:41 PM, Arnau Bria wrote:
Hi,
I've installed wicd and configured as
http://wicd.sourceforge.net/moinmoin/Wicd on Fedora says.
*Just starting its daemon
But when I open it I only see my wired conection.
My wireless interface is avaliable via ifconfig:
# iwconfig
lo
Hi,
I've installed wicd and configured as
http://wicd.sourceforge.net/moinmoin/Wicd on Fedora says.
*Just starting its daemon
But when I open it I only see my wired conection.
My wireless interface is avaliable via ifconfig:
# iwconfig
lono wireless extensions.
eth0 no wireless e
70 matches
Mail list logo
