*** This bug is a duplicate of bug 371291 ***
https://bugs.launchpad.net/bugs/371291
My System : Aspire One ZG5
OS : Ubuntu 10.10 (Maverick)
3G Device : Gobi 2000 (inbuilt)
sorry i seem to have been hit with this bug
The first connection throws up an almost connected log. (Attached File :
*** This bug is a duplicate of bug 371291 ***
https://bugs.launchpad.net/bugs/371291
a very minimal log on second and subsequent connection attempts !!!
** Attachment added: Second 3G connection attempt
*** This bug is a duplicate of bug 371291 ***
https://bugs.launchpad.net/bugs/371291
not sure why on second/subsequent attempts the log is not as detailed as
the first attempt at connecting after bootup
help most appreciated.
thanks
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 371291 ***
https://bugs.launchpad.net/bugs/371291
dupe of bug 371291 ... see the official workaround in that bugs
summary.
** Changed in: network-manager (Ubuntu)
Status: New = Triaged
** This bug has been marked a duplicate of bug 371291
MASTER
My NM now connects. I've noticed the following in /var/log/auth.log:
Apr 25 01:43:41 home dbus-daemon: Rejected send message, 1 matched
rules; type=method_call, sender=:1.42 (uid=1000 pid=6083
comm=/usr/lib/indicator-applet/indicator-applet --oaf-a)
interface=org.freedesktop.DBus.Properties
Same problem with a Huawei E180. My handmade PPP configuration simply
works, Network Manager connects, then disconnects:
Apr 25 00:24:13 home pppd[17936]: Using interface ppp0
Apr 25 00:24:13 home pppd[17936]: Connect: ppp0 -- /dev/ttyUSB2
Apr 25 00:24:13 home pppd[17936]: Unable to obtain CHAP
I get this occasionally too. However, for me this usually happens when
the connection I'm using just stops working. Network Manager (NM) thinks
it's fine, but it's not so I disconnect and try to reconnect. At this
point, the connection process takes twice as long and the NM applet
spins for a bit
I have the same problem like posted above with an Huawei E180
(Identified as E220).
pppd_timed_out(): Looks like pppd didn't initialize our dbus module is
the only thing I can see in the syslog.
I had it fixed until by installing the latest DBUS package. But that helped
exactly until the next
Tristan, thanks for your comment. I finally got around trying your
solution to have the modem inserted at boot time, but for me this didn't
solve the problem. I can do anything with the modem (including sending
SMS messages), but I cannot get a connection.
--
Network-manager Looks like pppd
I get this much less often now as long as I plug the USB Modem in before
boot time. This seems to have fixed it for 99% of the time. Occasionally
when disconnected (due to signal or handover) it will not re-connect
because of this, however in this instance I tend to get away with
unplugging and
I have not been able to use my new Huawei E620 umts USB stick (lspci
info: 12d1:1001 Huawei Technologies Co., Ltd. E620 USB Modem) with the
same error many times. I have tried it on three machines, two of them
ran AMD64 Intrepid, the other one is an Asus eeepc with an up to date
i386 Intrepid
I got the same error on different hardware (Novatel Merlin UMTS modem).
Posted logs as follow-up to bug#248630, which was open to deal with the
specifics of that pcmcia card.
--
Network-manager Looks like pppd didn't initialize our dbus module with Huawei
E160G (E220) on amd64 Intrepid
12 matches
Mail list logo
