On Thursday 24 July 2008 12:49:30 pm Konstantin Svist wrote:
> Christoph Höger wrote:
> > Am Mittwoch, den 23.07.2008, 16:18 -0700 schrieb Konstantin Svist:
> >> Hi,
> >>
> >> I've noticed a problem with NM recently (might've happened after a
> >> system update, not 100% sure when it started).
> >>
Christoph Höger wrote:
Am Mittwoch, den 23.07.2008, 16:18 -0700 schrieb Konstantin Svist:
Hi,
I've noticed a problem with NM recently (might've happened after a
system update, not 100% sure when it started).
When I log into KDE, NM starts connecting to the network. It used to
connect eth0
Christoph Höger wrote:
Am Mittwoch, den 23.07.2008, 16:18 -0700 schrieb Konstantin Svist:
Hi,
I've noticed a problem with NM recently (might've happened after a
system update, not 100% sure when it started).
When I log into KDE, NM starts connecting to the network. It used to
connect eth0
Am Mittwoch, den 23.07.2008, 16:18 -0700 schrieb Konstantin Svist:
> Hi,
>
> I've noticed a problem with NM recently (might've happened after a
> system update, not 100% sure when it started).
> When I log into KDE, NM starts connecting to the network. It used to
> connect eth0 if it was availab
Hi,
I've noticed a problem with NM recently (might've happened after a
system update, not 100% sure when it started).
When I log into KDE, NM starts connecting to the network. It used to
connect eth0 if it was available, but nowadays it seems to both do that
and attempt connecting to the wifi
