Hi, yes: use of gnome-ppp/wvdial instead of modemmanager (i.e. disable
mobile broadband on networkmanager applet). With a direct dialer and
correct ttyUSB port, the modem's response is immediate as the LED
changes from red to flashing green. Anyway it seems already fixed in
later versions -correct
About 11.10 the only change is that the pin ask (on sim) is disabled
now. I do not know if it has installed any software updates (I'm using
11.04 so I'm not sure). If no other reason the failure was due to
mismanagement of the unlocking pin. Regards.
--
You received this bug notification because
Hi, today I try (xubuntu 11.10) with networkmanagar and I don't have any
problem connecting. I don't understand why :) but it seems fixed in
11.10. Regards.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
** Summary changed:
- ZTE MF190, try to connect on bad ttyUSB2 (ubuntu 11.04), no connection -wrong
dial number- (ubuntu 11.10)
+ ZTE MF190, try to connect on bad ttyUSB2 (ubuntu 11.04)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi, perhaps interesting to note that this modem hangs when trying to
connect to wrong port (such as ttyUSB1 or ttyUSB2). And any further
attempt on ttyUSB4 not get any results (except a confusing "invalid dial
command"). So with this modem does not serve the "trick" to try to
connect to all availab
Screenshots about this translatios bug on:
https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-es/+bug/889966
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875224
Title:
nautilus shows th
** Attachment added: "MiB-nautilus.png"
https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-es/+bug/889966/+attachment/2596276/+files/MiB-nautilus.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
MiB on same file, thunar and nautilus at ubuntu 11.10
** Attachment added: "MiB-thunar.png"
https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-es/+bug/889966/+attachment/2596275/+files/MiB-thunar.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
However, in Ubuntu 11.04 connects, although this use an incorrect dial.
Modem-manger log with ttyUSB2 wrong on first attempt, followed by unplug
and proper connection on ttyUSB4.
** Attachment added: "modem-manager.txt"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/875441/+attach
Here we see that is properly configured, but it dial an incorrect value:
modem-manager[3148]: [1319209492.490204] [mm-generic-gsm.c:5099]
simple_connect(): (ttyUSB4): number => "*99#"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
** Summary changed:
- ZTE MF190, try to connect on bad ttyUSB2 (ubuntu 11.04), no connection
(ubuntu 11.10)
+ ZTE MF190, try to connect on bad ttyUSB2 (ubuntu 11.04), no connection -wrong
dial number- (ubuntu 11.10)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I see on ubuntu 11.10 log:
modem-manager[3148]: [1319209523.188058] [mm-at-serial-port.c:298]
debug_log(): (ttyUSB4): --> 'ATD*99***1#'
modem-manager[3148]: [1319209523.206031] [mm-at-serial-port.c:298]
debug_log(): (ttyUSB4): <-- 'ERROR'
modem-manager[3148]: [1319209523.206076] [mm-serial-pa
Disabling network manager (and/or modem-manager) I don't have any
problem with wvdial over ttyUSB4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875441
Title:
ZTE MF190, try to connect on bad ttyUS
Hi, I can always include more logs, just say so. With modem-manager
forcing to restart (with killall) on ubuntu 11.10, I get that ttyUSB4 to
be used, but it gets stuck and fails to finish connection process.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
** Attachment added: "Log on Ubuntu 11.10 Modem manager"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/875441/+attachment/2564621/+files/modem.log.ubuntu.11.10.txt
** Summary changed:
- ZTE MF190, try to connect on bad ttyUSB2
+ ZTE MF190, try to connect on bad ttyUSB2 (ubuntu 1
** Attachment added: "Log on Ubuntu 11.10 Netwok Manager"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/875441/+attachment/2564620/+files/nm.log.ubuntu.11.10.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Hi, 11.10 problem: another correction (may be no ttyUSB2, it try any
port except ttyUSB4): I could debug minimally modemmanager while I did
the installation and gives me the feeling that the problem is that no
cracks modemmanager, ie a stability problem :D. When it restarts at
11.04, ttyUSB4 port i
Hi, regression: on Ubuntu 11.10 always try to connect over bad ttyUSB2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875441
Title:
ZTE MF190, try to connect on bad ttyUSB2
To manage notifications a
Hi, sorry, correct segfault on modem-manager debug log is:
Oct 16 16:53:04 almursi kernel: [ 1145.974365] modem-manager[3317]:
segfault at ip b76dfa7f sp bfa5c020 error 4 in
libglib-2.0.so.0.2800.6[b76b3000+d5000]
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "modem-manager debug output to console, faiil on ttyUSB2"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/875441/+attachment/2554695/+files/modem.log2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Hi, It seem duplicate of ZTE MF190 and bad ttyUSB2
(https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/875441)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764576
Title:
network-manager ca
** Attachment added: "output on mm-test"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/875441/+attachment/2553042/+files/mm-test.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/8754
** Description changed:
Hi,
- This USB ADSL modem is connected properly on ttyUSB4 only. But the connection
is attempted on ttyUSB2 mostly, although the possibility is reduced after
canceling the request PIN useless (in an automatic connection, see
https://bugs.launchpad.net/ubuntu/+source/ne
A comment that I found interesting (about another ZTE MF190 variant):
http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?t=719
Josh
Posted: Thu Aug 11, 2011 7:27 am
It's the old problem of Network Manager, or more precisely the helper component
modem-manager, sometimes not using the
(the name of the machine was modified by hand on logs; as well as
personal data)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875441
Title:
ZTE MF190, try to connect on bad ttyUSB2
To manage notif
(registered -> disabled)
Oct 16 08:31:50 almursi36 modem-manager[2489]: Modem
/org/freedesktop/ModemManager/Modems/1: state changed (disabled -> registered)
Oct 16 08:31:50 almursi NetworkManager[957]: (ttyUSB2): now unmanaged
Oct 16 08:31:50 almursi init: modemmanager main process
** Summary changed:
- ZTE MF190, try to connet on bad ttyUSB2
+ ZTE MF190, try to connect on bad ttyUSB2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875441
Title:
ZTE MF190, try to connect on bad
** Attachment added: "Extract of 3er. fail attempt and next good"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/875441/+attachment/2549275/+files/syslog_extract.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
** Description changed:
- Hi,
+ Hi,
This USB ADSL modem is connected properly on ttyUSB4 only. But the connection
is attempted on ttyUSB2 mostly, although the possibility is reduced after
canceling the request PIN useless (in an automatic connection, see
https://bugs.launchpad.net/ubuntu/+so
** Tags removed: compilation ldz link
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/598691
Title:
Incorrect symbolic link
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
Public bug reported:
Hi,
This USB ADSL modem is connected properly on ttyUSB4 only. But the connection
is attempted on ttyUSB2 mostly, although the possibility is reduced after
canceling the request PIN useless (in an automatic connection, see
https://bugs.launchpad.net/ubuntu/+source/network-
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875441
Title:
ZTE MF190, try to connet on bad ttyUSB2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanag
Hi, I have a similar problem (useless request of pin), but together with
other related to the console device, because my ZTE MF190 successfully
connect only on ttyUSB4, but usually when I did not cancel the request
for pin, it tries to connect to ttyUSB2 (fortunately seems to be
alternating between
Hi, seeing similar errors, it seems a mistake not to open the
translations-file. As the translation is completely gone (which is
usually half the start of the release) the problem is solved (though not
definitive, because this possibility should be envisaged). Now I do not
use amd64 (because i386 w
** Description changed:
Binary package hint: liblz0
Symbolic link liblz.so generated is incorrect, over liblz.so.0.7
Fix very easy :). (but however cause a lot of stupid warnings on
compilation...)
Thanks
+
+ EDITED: On Ubuntu-lucid, version 0.8-1
** Description changed:
Binary p
Public bug reported:
Binary package hint: liblz0
Symbolic link liblz.so generated is incorrect, over liblz.so.0.7
Fix very easy :). (but however cause a lot of stupid warnings on
compilation...)
Thanks
EDITED: On Ubuntu-lucid (version 0.8-1)
** Affects: lzlib (Ubuntu)
Importance: Undecid
It seems that the package would be affected by the error is upstart
and/or plymouth. If I have time I check it...
--
system hang on init, start screen (automatic check 80%)
https://bugs.launchpad.net/bugs/554753
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Alberto Milone
Yes, it's possible! (I fear that this was the rush of my first day here ;-))
Thanks.
--
fglrx fails at startup because of missing amdpcsdb.default + removal leaves
bad settings in Xorg.conf
https://bugs.launchpad.net/bugs/440233
You received this bug notification because you ar
In the Beta 2 still see the problem. I have reduced the number of mounts so at
this log at least three crashes (solved with ctrl-alt-supr = signal 15). On
normal log, rtkit-daemon start.
I think it would be nice to correctly identify the location (cron?, Runlevel?,
Init.d?) of the error, and cha
Again he was hanged. The system log ends at two seconds to start, so it
does not add much information, except that fails to boot graphic (no
mention of any operation in auth.log). But do find a strange thing:
after you boot in recovery mode is not possible to return to normal boot
(gdm graph), but
Right now I have doubts about the package involved (boot.log say: "fsck
from util-linux-ng 2.17.2"). The message about the broken link was a
little confusing (especially when I fail to translate correctly, because
of the rush ...), so maybe it relates to what I saw today one of the re-
start the sy
sorry, I forgot this detail
In 10.4 beta1:
disk 1 root = ext4
disk 2 home = ext3 (on check system hang)
In 9.4:
disk 1 root = ext3
disk 2 home = ext4
disk 3 user data (same disk 2 on 10.4) = ext3 (any problem report)
--
system hang on init, start scre
Public bug reported:
Binary package hint: e2fsprogs
In the first automatic check of my 10.4 beta1 the system crashes while
performing the analysis of HD (80%). Start screen (without the possibility of
more information.)
In a boot in recovery mode, to check the disks I get the message "broken li
Sorry, previous message at 10.4 beta1 (lucid), updated today.
--
fglrx fails at startup because of missing amdpcsdb.default + removal leaves
bad settings in Xorg.conf
https://bugs.launchpad.net/bugs/440233
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
I had been same problem. Incorrect device loader from org.conf after
installation.
___
# Bad org.conf:
Section "Screen"
Identifier "Default Screen"
DefaultDepth24
EndSection
Section "Module"
Load"glx"
EndSection
Section "Device"
I
45 matches
Mail list logo
