Ubuntu 9.04 gnome-ppp/dgc1.11....deb works, Ubuntu 9.10 does not

Bug #479242 reported by jkohler2
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
WvDial
Invalid
Undecided
Unassigned
gnome-ppp (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: firefox-3.0

Here is the command line terminal record of a successful usbmodem dialup connection:

john@john-laptop:~$ sudo gnome-ppp
[sudo] password for john:
WVCONF: /root/.wvdial.conf
GNOME PPP: Connecting...
GNOME PPP: STDERR: --> Ignoring malformed input line: ";Do NOT edit this file by hand!"
GNOME PPP: STDERR: --> WvDial: Internet dialer version 1.60
GNOME PPP: STDERR: --> Cannot get information for serial port.
GNOME PPP: STDERR: --> Initializing modem.
GNOME PPP: STDERR: --> Sending: ATZ
GNOME PPP: STDERR: ATZ
GNOME PPP: STDERR: OK
GNOME PPP: STDERR: --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
GNOME PPP: STDERR: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
GNOME PPP: STDERR: OK
GNOME PPP: STDERR: --> Modem initialized.
GNOME PPP: STDERR: --> Sending: ATM1L3DT*70,,8351941
GNOME PPP: STDERR: --> Waiting for carrier.
GNOME PPP: STDERR: ATM1L3DT*70,,8351941
GNOME PPP: STDERR: CONNECT 57600
GNOME PPP: STDERR: --> Carrier detected. Waiting for prompt.
GNOME PPP: STDERR: ** O1 Communications TermServ **
GNOME PPP: STDERR: Login:
GNOME PPP: STDERR: --> Looks like a login prompt.
GNOME PPP: STDERR: --> Sending: jkohler2
GNOME PPP: STDERR: jkohler2
GNOME PPP: STDERR: Password:
GNOME PPP: STDERR: --> Looks like a password prompt.
GNOME PPP: STDERR: --> Sending: (password) r
GNOME PPP: STDERR: Entering PPP Session.
GNOME PPP: STDERR: IP address is 69.85.136.125
GNOME PPP: STDERR: MTU is 1524.
GNOME PPP: STDERR: --> Looks like a welcome message.
GNOME PPP: STDERR: --> Starting pppd at Mon Nov 9 07:31:42 2009
GNOME PPP: STDERR: --> Pid of pppd: 10655
GNOME PPP: STDERR: --> Using interface ppp0
GNOME PPP: STDERR: --> local IP address 69.85.136.125
GNOME PPP: STDERR: --> remote IP address 69.19.217.21
GNOME PPP: STDERR: --> primary DNS address 66.81.1.250
GNOME PPP: STDERR: --> secondary DNS address 66.81.1.252
^C
john@john-laptop:~$

I will send a failure command line record soon

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: firefox-3.0 3.0.15+nobinonly-0ubuntu0.9.04.1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: firefox-3.0
Uname: Linux 2.6.28-16-generic i686

Revision history for this message
jkohler2 (jkohler2) wrote :
Revision history for this message
jkohler2 (jkohler2) wrote :

I use this to install gnome-ppp:

sudo apt-get install gnome ppp

I use this to install the linuxant driver:

dpkg -i dgc_1.11.......................deb

...under both Ubuntu 9.04 and 9.10

John

Revision history for this message
John Vivirito (gnomefreak) wrote :

Changed to gnome-ppp since this is not a firefox problem

affects: firefox-3.0 (Ubuntu) → gnome-ppp (Ubuntu)
Changed in gnome-ppp (Ubuntu):
status: New → Incomplete
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Could you please attach your /var/log/dmesg and /root/.wvdial.conf files?

Remove the username and password out of .wvdial.conf first though.

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Also, paste the output of "sudo lsusb"

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

(see bug #479353 for log when if fails under 9.10)

Revision history for this message
jkohler2 (jkohler2) wrote : Re: [Bug 479242] Re: Ubuntu 9.04 gnome-ppp/dgc1.11....deb works, Ubuntu 9.10 does not

Hello Marc,

I need to know, in simple terms, how to include the information for which
you asked.
Do i copy, cut, and paste from the terminal screen to the report?
John

On Wed, Nov 11, 2009 at 12:59 PM, Marc Deslauriers <
<email address hidden>> wrote:

> Also, paste the output of "sudo lsusb"
>
> --
> Ubuntu 9.04 gnome-ppp/dgc1.11....deb works, Ubuntu 9.10 does not
> https://bugs.launchpad.net/bugs/479242
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
jkohler2 (jkohler2) wrote :

Hi Marc,

[ 0.450823] libata version 3.00 loaded.
[ 0.450899] usbcore: registered new interface driver usbfs
[ 0.450917] usbcore: registered new interface driver hub
[ 0.450942] usbcore: registered new device driver usb
[ 0.451149] ACPI: WMI: Mapper loaded
[ 0.451152] PCI: Using ACPI for IRQ routing
[ 0.451346] Bluetooth: Core ver 2.15
[ 0.451376] NET: Registered protocol family 31
[ 0.451378] Bluetooth: HCI device and connection manager initialized
[ 0.451381] Bluetooth: HCI socket layer initialized
[ 0.451383] NetLabel: Initializing
[ 0.451385] NetLabel: domain hash size = 128
[ 0.451387] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.451400] NetLabel: unlabeled traffic allowed by default
[ 0.451431] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 0.451436] hpet0: 3 comparators, 64-bit 14.318180 MHz counter
[ 0.457540] pnp: PnP ACPI init
[ 0.457563] ACPI: bus type pnp registered
[ 0.458842] pnp 00:01: io resource (0x164e-0x164f) overlaps 0000:00:1c.3
BAR 13 (0x1000-0x1fff), disabling
[ 0.504010] Switched to high resolution mode on CPU 0
[ 0.612309] pnp: PnP ACPI: found 9 devices
[ 0.612312] ACPI: ACPI bus type pnp unregistered
[ 0.612316] PnPBIOS: Disabled by ACPI PNP
[ 0.612331] system 00:01: ioport range 0x600-0x60f has been reserved

On Wed, Nov 11, 2009 at 12:56 PM, Marc Deslauriers <
<email address hidden>> wrote:

> Could you please attach your /var/log/dmesg and /root/.wvdial.conf
> files?
>
> Remove the username and password out of .wvdial.conf first though.
>
> --
> Ubuntu 9.04 gnome-ppp/dgc1.11....deb works, Ubuntu 9.10 does not
> https://bugs.launchpad.net/bugs/479242
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Hi,

dmesg is a file. Reboot your computer with the modem plugged in. After, you can either reply to this email or go directly to the bug web page. Click to attach a file, and browse to the /var/log directory where you will find it.

For the "sudo lsusb", simply open a teminal from Applications/Accessories/terminal. Type "sudo lsusb", without the quotes. It will ask you for your password, and then you can copy and paste the results directly from the terminal screen.

Let me know if you need more information.

Thanks.

Revision history for this message
jkohler2 (jkohler2) wrote :
Download full text (29.4 KiB)

Here is the dmesg, after reboot.

[ 0.338775] SCSI subsystem initialized
[ 0.338833] libata version 3.00 loaded.
[ 0.338910] usbcore: registered new interface driver usbfs
[ 0.338928] usbcore: registered new interface driver hub
[ 0.338952] usbcore: registered new device driver usb
[ 0.339162] ACPI: WMI: Mapper loaded
[ 0.339165] PCI: Using ACPI for IRQ routing
[ 0.339358] Bluetooth: Core ver 2.15
[ 0.339388] NET: Registered protocol family 31
[ 0.339391] Bluetooth: HCI device and connection manager initialized
[ 0.339394] Bluetooth: HCI socket layer initialized
[ 0.339396] NetLabel: Initializing
[ 0.339398] NetLabel: domain hash size = 128
[ 0.339399] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.339412] NetLabel: unlabeled traffic allowed by default
[ 0.339443] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 0.339449] hpet0: 3 comparators, 64-bit 14.318180 MHz counter
[ 0.345539] pnp: PnP ACPI init
[ 0.345562] ACPI: bus type pnp registered
[ 0.346842] pnp 00:01: io resource (0x164e-0x164f) overlaps 0000:00:1c.3
BAR 13 (0x1000-0x1fff), disabling
[ 0.448288] pnp: PnP ACPI: found 9 devices
[ 0.448291] ACPI: ACPI bus type pnp unregistered
[ 0.448295] PnPBIOS: Disabled by ACPI PNP
[ 0.448310] system 00:01: ioport range 0x600-0x60f has been reserved
[ 0.448313] system 00:01: ioport range 0x610-0x610 has been reserved
[ 0.448316] system 00:01: ioport range 0x800-0x80f has been reserved
[ 0.448319] system 00:01: ioport range 0x810-0x817 has been reserved
[ 0.448322] system 00:01: ioport range 0x400-0x47f has been reserved
[ 0.448325] system 00:01: ioport range 0x500-0x53f has been reserved
[ 0.448328] system 00:01: ioport range 0xff2c-0xff2f has been reserved
[ 0.448333] system 00:01: iomem range 0xe0000000-0xefffffff has been
reserved
[ 0.448336] system 00:01: iomem range 0xfed1c000-0xfed1ffff has been
reserved
[ 0.448339] system 00:01: iomem range 0xfed14000-0xfed17fff has been
reserved
[ 0.448343] system 00:01: iomem range 0xfed18000-0xfed18fff has been
reserved
[ 0.448346] system 00:01: iomem range 0xfed19000-0xfed19fff has been
reserved
[ 0.448349] system 00:01: iomem range 0xfec00000-0xfec00fff could not be
reserved
[ 0.448352] system 00:01: iomem range 0xfee00000-0xfee00fff has been
reserved
[ 0.448355] system 00:01: iomem range 0x32000000-0x320000ff could not be
reserved
[ 0.483046] AppArmor: AppArmor Filesystem Enabled
[ 0.483124] pci 0000:00:1c.0: PCI bridge, secondary bus 0000:02
[ 0.483129] pci 0000:00:1c.0: IO window: 0x4000-0x4fff
[ 0.483137] pci 0000:00:1c.0: MEM window: 0x97300000-0x982fffff
[ 0.483142] pci 0000:00:1c.0: PREFETCH window:
0x00000090000000-0x00000090ffffff
[ 0.483151] pci 0000:00:1c.1: PCI bridge, secondary bus 0000:04
[ 0.483156] pci...

Revision history for this message
jkohler2 (jkohler2) wrote :

Here it is.....

john@john-laptop:~$ sudo lsusb
[sudo] password for john:
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 0803:3095 Zoom Telephonics, Inc.
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
john@john-laptop:~$

On Wed, Nov 11, 2009 at 12:59 PM, Marc Deslauriers <
<email address hidden>> wrote:

> Also, paste the output of "sudo lsusb"
>
> --
> Ubuntu 9.04 gnome-ppp/dgc1.11....deb works, Ubuntu 9.10 does not
> https://bugs.launchpad.net/bugs/479242
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

OK, your modem is being detected by the Karmic kernel. No need to install the driver anymore. These lines show it being detected:

[ 19.606165] cdc_acm 5-1:2.0: ttyACM0: USB ACM device
[ 19.607937] usbcore: registered new interface driver cdc_acm
[ 19.607941] cdc_acm: v0.26:USB Abstract Control Model driver for USB
modems and ISDN adapters

Open GnomePPP, click the setup button, and under "device", manually enter "/dev/ttyACM0" (that's a zero, not the letter O)

Click on close and see if that works for you.

Revision history for this message
jkohler2 (jkohler2) wrote :
Download full text (3.6 KiB)

I did that, and here is the response:

john@john-laptop:~$ sudo gnome-ppp
[sudo] password for john:
WVCONF: /root/.wvdial.conf
GNOME PPP: STDOUT: Editing `/dev/null'.
GNOME PPP: STDERR: Modem Port Scan<*1>: Scanning ttyACM0 first, /dev/modem
is a link to it.
GNOME PPP: STDOUT:
GNOME PPP: STDERR: WvModem<*1>: Cannot get information for serial port.
GNOME PPP: STDOUT: Scanning your serial ports for a modem.
GNOME PPP: STDERR: ttyACM0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next
try: 9600 baud
GNOME PPP: STDOUT:
GNOME PPP: STDERR: ttyACM0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next
try: 115200 baud
GNOME PPP: STDERR: ttyACM0<*1>: ATQ0 V1 E1 -- and failed too at 115200,
giving up.
GNOME PPP: STDOUT:
GNOME PPP: STDERR: Modem Port Scan<*1>: S0 S1 S2 S3
GNOME PPP: STDOUT:
GNOME PPP: STDOUT: Sorry, no modem was detected! Is it in use by another
program?
GNOME PPP: STDOUT: Did you configure it properly with setserial?
GNOME PPP: STDOUT:
GNOME PPP: STDOUT: Please read the FAQ at http://open.nit.ca/wiki/?WvDial
GNOME PPP: STDOUT:
GNOME PPP: STDOUT: If you still have problems, send mail to <
<email address hidden>>.
GNOME PPP: STDOUT: Editing `/dev/null'.
GNOME PPP: STDERR: Modem Port Scan<*1>: Scanning ttyACM0 first, /dev/modem
is a link to it.
GNOME PPP: STDOUT:
GNOME PPP: STDERR: WvModem<*1>: Cannot get information for serial port.
GNOME PPP: STDOUT: Scanning your serial ports for a modem.
GNOME PPP: STDERR: ttyACM0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next
try: 9600 baud
GNOME PPP: STDOUT:
GNOME PPP: STDERR: ttyACM0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next
try: 115200 baud
GNOME PPP: STDERR: ttyACM0<*1>: ATQ0 V1 E1 -- and failed too at 115200,
giving up.
GNOME PPP: STDOUT:
GNOME PPP: STDERR: Modem Port Scan<*1>: S0 S1 S2 S3
GNOME PPP: STDOUT:
GNOME PPP: STDOUT: Sorry, no modem was detected! Is it in use by another
program?
GNOME PPP: STDOUT: Did you configure it properly with setserial?
GNOME PPP: STDOUT:
GNOME PPP: STDOUT: Please read the FAQ at http://open.nit.ca/wiki/?WvDial
GNOME PPP: STDOUT:
GNOME PPP: STDOUT: If you still have problems, send mail to <
<email address hidden>>.
GNOME PPP: Connecting...
GNOME PPP: STDERR: --> WvDial: Internet dialer version 1.60
GNOME PPP: STDERR: --> Cannot open /dev/tty/ACM0: Not a directory
GNOME PPP: STDERR: --> Cannot open /dev/tty/ACM0: Not a directory
GNOME PPP: STDERR: --> Cannot open /dev/tty/ACM0: Not a directory
^C
john@john-laptop:~$ CLEAR
CLEAR: command not found
john@john-laptop:~$ clear

john@john-laptop:~$ sudo gnome-ppp
WVCONF: /root/.wvdial.conf
GNOME PPP: Connecting...
GNOME PPP: STDERR: --> WvDial: Internet dialer version 1.60
GNOME PPP: STDERR: --> Cannot open /dev/tty/ACM0: Not a directory
GNOME PPP: STDERR: --> Cannot open /dev/tty/ACM0: Not a directory
GNOME PPP: STDERR: --> Cannot open /dev/tty/ACM0: Not a directory

On Thu, Nov 12, 2009 at 5:05 AM, Marc Deslauriers <
<email address hidden>> wrote:

> OK, your modem is being detected by the Karmic kernel. No need to
> install the driver anymore. These lines show it being detected:
>
> [ 19.606165] cdc_acm 5-1:2.0: ttyACM0: USB ACM device
> [ 19.607937] usbcore: registered new in...

Read more...

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

That's odd...maybe the unneeded linuxant driver is now conflicting with it.

Could you remove it with "dpkg -P dgcmodem" and reboot with the modem plugged in?

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Actually, they say to remove it with: "sudo dgcconfig --uninstall", so try that first and then do the "dpkg -P dgcmodem"

Revision history for this message
jkohler2 (jkohler2) wrote :

I'll try....
John

On Thu, Nov 12, 2009 at 10:40 AM, Marc Deslauriers <
<email address hidden>> wrote:

> That's odd...maybe the unneeded linuxant driver is now conflicting with
> it.
>
> Could you remove it with "dpkg -P dgcmodem" and reboot with the modem
> plugged in?
>
> --
> Ubuntu 9.04 gnome-ppp/dgc1.11....deb works, Ubuntu 9.10 does not
> https://bugs.launchpad.net/bugs/479242
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
jkohler2 (jkohler2) wrote :

Hi Marc,
Here is what I got:

john@john-laptop:~$ sudo dgcconfig --uninstall
[sudo] password for john:
Conexant DGC USB modem driver, version 1.11

If you need assistance or more information, please go to:
    http://www.linuxant.com/

When reporting a problem for the first time, please send
us the file generated by "dgcconfig --dumpdiag".

Uninstallation was successful.
john@john-laptop:~$

On Thu, Nov 12, 2009 at 10:42 AM, Marc Deslauriers <
<email address hidden>> wrote:

> Actually, they say to remove it with: "sudo dgcconfig --uninstall", so
> try that first and then do the "dpkg -P dgcmodem"
>
> --
> Ubuntu 9.04 gnome-ppp/dgc1.11....deb works, Ubuntu 9.10 does not
> https://bugs.launchpad.net/bugs/479242
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
jkohler2 (jkohler2) wrote :

Here is what I got:

john@john-laptop:~$ sudo dgcconfig --uninstall
[sudo] password for john:
Conexant DGC USB modem driver, version 1.11

If you need assistance or more information, please go to:
    http://www.linuxant.com/

When reporting a problem for the first time, please send
us the file generated by "dgcconfig --dumpdiag".

Uninstallation was successful.
john@john-laptop:~$ sudo dpkg -P dgcmodem
(Reading database ... 126512 files and directories currently installed.)
Removing dgcmodem ...
Purging configuration files for dgcmodem ...
Removing old /etc/dgcmodem
john@john-laptop:~$

On Thu, Nov 12, 2009 at 5:35 PM, John Kohler <email address hidden> wrote:

> I'll try....
> John
>
>
> On Thu, Nov 12, 2009 at 10:40 AM, Marc Deslauriers <
> <email address hidden>> wrote:
>
>> That's odd...maybe the unneeded linuxant driver is now conflicting with
>> it.
>>
>> Could you remove it with "dpkg -P dgcmodem" and reboot with the modem
>> plugged in?
>>
>> --
>> Ubuntu 9.04 gnome-ppp/dgc1.11....deb works, Ubuntu 9.10 does not
>> https://bugs.launchpad.net/bugs/479242
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

After uninstalling the driver, and rebooting, does gnome-ppp detect your modem now?

Revision history for this message
jkohler2 (jkohler2) wrote :

Hi Marc,

Here is the dialog box from my terminal window:

john@john-laptop:~$ sudo gnome-ppp
[sudo] password for john:
WVCONF: /root/.wvdial.conf
GNOME PPP: STDOUT: Editing `/dev/null'.
GNOME PPP: STDERR: Modem Port Scan<*1>: Scanning ttyACM0 first, /dev/modem
is a link to it.
GNOME PPP: STDOUT:
GNOME PPP: STDERR: Modem Port Scan<*1>: ACM0 S0 S1 S2 S3 ACM1
GNOME PPP: STDOUT: Scanning your serial ports for a modem.
GNOME PPP: STDERR: WvModem<*1>: Cannot get information for serial port.
GNOME PPP: STDOUT:
GNOME PPP: STDERR: ttyACM2<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next
try: 9600 baud
GNOME PPP: STDERR: ttyACM2<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next
try: 115200 baud
GNOME PPP: STDERR: ttyACM2<*1>: ATQ0 V1 E1 -- and failed too at 115200,
giving up.
GNOME PPP: STDOUT:
GNOME PPP: STDOUT:
GNOME PPP: STDOUT: Sorry, no modem was detected! Is it in use by another
program?
GNOME PPP: STDOUT: Did you configure it properly with setserial?
GNOME PPP: STDOUT:
GNOME PPP: STDOUT: Please read the FAQ at http://open.nit.ca/wiki/?WvDial
GNOME PPP: STDOUT:
GNOME PPP: STDOUT: If you still have problems, send mail to <
<email address hidden>>.
john@john-laptop:~$

John

On Thu, Nov 12, 2009 at 7:55 PM, Marc Deslauriers <
<email address hidden>> wrote:

> After uninstalling the driver, and rebooting, does gnome-ppp detect your
> modem now?
>
> --
> Ubuntu 9.04 gnome-ppp/dgc1.11....deb works, Ubuntu 9.10 does not
> https://bugs.launchpad.net/bugs/479242
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
jkohler2 (jkohler2) wrote :

Just tried again; upgrade from 9.04 which worked with modem to 9.10 which did not. Is it a kernel problem?

Here is the failure output :

john@john-laptop:~$ sudo gnome-ppp
[sudo] password for john:
WVCONF: /root/.wvdial.conf
GNOME PPP: Connecting...
GNOME PPP: STDERR: --> WvDial: Internet dialer version 1.60
GNOME PPP: STDERR: --> Cannot get information for serial port.
GNOME PPP: STDERR: --> Initializing modem.
GNOME PPP: STDERR: --> Sending: ATZ
GNOME PPP: STDERR: --> Sending: ATQ0
GNOME PPP: STDERR: --> Re-Sending: ATZ
GNOME PPP: STDERR: --> Modem not responding.
GNOME PPP: Unable to KILL wvdial process!
john@john-laptop:~$

Revision history for this message
G4JC (gaming4jc2) wrote :

Confirming, tested my Trendnet TFM-560X modem on Jaunty (laptop) and Karmic (desktop). Jaunty works perfectly, but the karmic computer sometimes fails to control the wvdial process. A fairly insane work around which works for me. Reboot computer, open a terminal type sudo gnome-ppp, enter root password and wait exactly 5secs - I count it by tapping the Entery key 5x lightly, and then push enter! It will usually start up, if not wait 4secs, and hit enter again to cancle. Then quickly hit enter again and it will redial. If this fails you will need to reboot and try it again. :P

Crazy I know but that's how I've been using my gnome-ppp even now as we speak. ^_^

Changed in gnome-ppp (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
G4JC (gaming4jc2) wrote :

After disconnecting and reconnecting we see this bug reallyyy begins to affect any attempt at reconnecting without restarting the computer. Log attached.

Revision history for this message
jkohler2 (jkohler2) wrote :

This issue is not even addressed in the latest edition of "Official Ubuntu Book." :-(
Not only that; no reference is even made to dialup modem, Gnome modem
drivers..

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Could you please try uninstalling the modemmanager package and rebooting, then try again.
The modemmanager package in karmic ties up the serial ports.

Changed in gnome-ppp (Ubuntu):
status: Confirmed → Incomplete
Changed in wvdial:
status: New → Incomplete
Revision history for this message
G4JC (gaming4jc2) wrote :

"The modemmanager package in karmic ties up the serial ports."

Confirming, I uninstalled it and now "finally!" it is working fine, even during redialing and such. Thanks man. :-)

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

@jkohler2: do you still have this problem after uninstalling modemmanager?

Revision history for this message
jkohler2 (jkohler2) wrote :

The last time I ran karmic and uninstalled modemmanager, it worked for a while
on dialup and then failed.

John

On Sat, Mar 13, 2010 at 5:27 PM, Marc Deslauriers
<email address hidden> wrote:
> @jkohler2: do you still have this problem after uninstalling
> modemmanager?
>
> --
> Ubuntu 9.04 gnome-ppp/dgc1.11....deb works, Ubuntu 9.10 does not
> https://bugs.launchpad.net/bugs/479242
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

It worked for a while and then failed? How long did it work for? What did it do when it failed?

Are you still interested in trying to debug this issue?

Revision history for this message
jkohler2 (jkohler2) wrote :

Hi Marc,

It worked for a day, almost. I went back to DSL/ethernet, and tried to
do another dialup with Gnome-ppp and it would not recognize the
U.S. Robotics modem (usb). I am away from home now, and can't try
Karmic with the dialup routine for a while.

Yes, I am still interested in trying to debug the issue, but will have to
return home to do so, after Wednesday.

John

P.S. I thought I documented this failure on "launchpad" bug# 469881.
I must be getting senile.

j

On Sat, Mar 13, 2010 at 5:55 PM, Marc Deslauriers
<email address hidden> wrote:
> It worked for a while and then failed? How long did it work for? What
> did it do when it failed?

> Are you still interested in trying to debug this issue?
>
> --
> Ubuntu 9.04 gnome-ppp/dgc1.11....deb works, Ubuntu 9.10 does not
> https://bugs.launchpad.net/bugs/479242
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

OK, I am closing this bug. Please continue with bug #469881.

Changed in wvdial:
status: Incomplete → Invalid
Changed in gnome-ppp (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.