From: Joao Ferreira gmail on
On Mon, 2010-08-02 at 22:39 +0100, Brad Rogers wrote:
> On Mon, 02 Aug 2010 17:13:03 -0400
> "John A. Sullivan III" <jsullivan(a)opensourcedevel.com> wrote:
>
> Hello John,
>
> > I wonder if this is why there are some many problems with Evolution
> > 2.30 breaking. From those threads, it seems that Evolution is looking
>
> I don't use Evo, but from what you say, it seems highly likely that
> Network Manager's bug is the problem.

I use Evolution and yes, Evolutio relies on NM to determine if a
connection is up or not....

If NM says there is no connection, then Evo will go into Offline mode;
sometimes I need to tell it to "Work Online" in order to have it work.

jmf


>


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/1280824920.4921.3.camel(a)debj5n.critical.pt
From: Osamu Aoki on
Hi,

On Mon, Aug 02, 2010 at 11:12:45AM +0000, Camaleón wrote:
> On Mon, 02 Aug 2010 10:48:14 +0100, Joao Ferreira gmail wrote:
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530024
...
> Mmm, if the bug is that ethernet cards are not detected/recognized by
> default by NM, yes, the "problem" is still there, at least for me.
>
> (not really a "problem" because I never use NM :-P)
>
> Side note: ethernet card is fully available/operative, just NM detects
> nothing.

Is this bug? This seems to me user configuration issue. I am basically
follwing: README.Debian NEWS.Debian.gz of network-manager Just disable
eth0 in /etc/network/interfaces like:

----
# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
#allow-hotplug eth0
#iface eth0 inet dhcp
-----

Then NM will detect eth0




--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/20100803152959.GA12301(a)debian.org
From: Camaleón on
On Wed, 04 Aug 2010 00:29:59 +0900, Osamu Aoki wrote:

> Hi,
>
> On Mon, Aug 02, 2010 at 11:12:45AM +0000, Camaleón wrote:
>> On Mon, 02 Aug 2010 10:48:14 +0100, Joao Ferreira gmail wrote:
>> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530024
> ...
>> Mmm, if the bug is that ethernet cards are not detected/recognized by
>> default by NM, yes, the "problem" is still there, at least for me.
>>
>> (not really a "problem" because I never use NM :-P)
>>
>> Side note: ethernet card is fully available/operative, just NM detects
>> nothing.
>
> Is this bug?

Not for me. But having the NM applet started by default and seeing no
ethernet device there (but working) is a bit confusing for users who want
to use NM.

> This seems to me user configuration issue. I am basically
> follwing: README.Debian NEWS.Debian.gz of network-manager Just disable
> eth0 in /etc/network/interfaces like:
>
> ----
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> #allow-hotplug eth0
> #iface eth0 inet dhcp
> -----
>
> Then NM will detect eth0

Yes, and that's quite similar to the information that the bug report
(comment #1) refers to.

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/pan.2010.08.03.16.15.45(a)gmail.com
From: Joao Ferreira gmail on
On Tue, 2010-08-03 at 16:15 +0000, Camale�n wrote:
> > Is this bug?
>
> Not for me. But having the NM applet started by default and seeing no
> ethernet device there (but working) is a bit confusing for users who
> want
> to use NM.

agree ! :)

if NM is a feature in Debian (and affects other SW components) then it
should be operating properly on a fresh install...

.... or fully disabled !

but, no... I would also not call it a bug... just an issue :)

jmf



--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/1280853429.4921.35.camel(a)debj5n.critical.pt