Gnome-ppp fails under ubuntu 10.04, works under 9.04

Bug #555442 reported by jkohler2 on 2010-04-05
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned

Bug Description

Please see bug #469881. I used the apt-get command to install gnome-ppp
in the latest version of ubuntu 10.04, Lucid Linx. The installation was successful
as with previous versions, I started the usb modem program and set values.
Neither my US Robotics nor my Zoom 3095 modem was located with the
"detect modem" command. I entered my ISP phone number, login and password.
When I clicked "connect" there was no modem connected.

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/modem: No such file or directory
GNOME PPP: STDERR: --> Cannot open /dev/modem: No such file or directory
GNOME PPP: STDERR: --> Cannot open /dev/modem: No such file or directory
GNOME PPP: Unable to KILL wvdial process!
john@john-laptop:~$

jkohler2 (jkohler2) wrote :

Under Ubuntu 9.04, gnome-ppp (sudo user level) allows these choices for
a modem device ttyS0 to ttyS3 and ACM0.
Under 10.04 gnome-ppp allows the tty choices and USB0 to USB3, none of
which recognizes my usb modems, neither the Zoom nor the US Robitics.
It could be that a USB device is different than an ACM device.

jkohler2 (jkohler2) wrote :

The following is the listing of a successful dial up session (Ubuntu 9.04):

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,,835-1941
GNOME PPP: STDERR: --> Waiting for carrier.
GNOME PPP: STDERR: ATM1L3DT*70,,835-1941
GNOME PPP: STDERR: CONNECT 115200
GNOME PPP: STDERR: --> Carrier detected. Waiting for prompt.
GNOME PPP: STDERR: ** O1 Communications TermServ **
GNOME PPP: STDERR: Login:
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)
GNOME PPP: STDERR: Entering PPP Session.
GNOME PPP: STDERR: IP address is 69.19.240.46
GNOME PPP: STDERR: MTU is 1524.
GNOME PPP: STDERR: --> Looks like a welcome message.
GNOME PPP: STDERR: --> Starting pppd at Tue Apr 6 15:45:37 2010
GNOME PPP: STDERR: --> Pid of pppd: 6257
GNOME PPP: STDERR: --> Using interface ppp0
GNOME PPP: STDERR: --> local IP address 69.19.240.46
GNOME PPP: STDERR: --> remote IP address 69.19.217.6
GNOME PPP: STDERR: --> primary DNS address 66.81.1.250
GNOME PPP: STDERR: --> secondary DNS address 66.81.1.252

jkohler2 (jkohler2) wrote :
Download full text (11.5 KiB)

I just tried Gnome-ppp under Ubuntu 10.04 at the root level, then at the user level.

At the root level, it worked, first time, every time.

At the user level, starting from the Applications>Internet>Gnome-ppp, I received the following
dialog windo with a failure to connect the Zoom Modem 3095 (usb):

--> WvDial: Internet dialer version 1.60
--> Cannot get information for serial port.
--> Initializing modem.
--> Sending: ATZ
ATZ
OK
--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
OK
--> Modem initialized.
--> Sending: ATM1L3DT*70,,9841940
--> Waiting for carrier.
ATM1L3DT*70,,9841940
CONNECT 57600
--> Carrier detected. Waiting for prompt.
** O1 Communications TermServ **
Login:
--> Looks like a login prompt.
--> Sending: jkohler2
jkohler2
Password:
--> Looks like a password prompt.
--> Sending: (password)
    Entering PPP Session.
    IP address is 66.81.37.53
    MTU is 1524.
--> Looks like a welcome message.
--> Unable to run /usr/sbin/pppd.
--> Check permissions, or specify a "PPPD Path" option in wvdial.conf.
--> Looks like a welcome message.
--> Unable to run /usr/sbin/pppd.
--> Check permissions, or specify a "PPPD Path" option in wvdial.conf.
--> Looks like a welcome message.
--> Unable to run /usr/sbin/pppd.
--> Check permissions, or specify a "PPPD Path" option in wvdial.conf.
--> Looks like a welcome message.
--> Unable to run /usr/sbin/pppd.
--> Check permissions, or specify a "PPPD Path" option in wvdial.conf.
--> Looks like a welcome message.
--> Unable to run /usr/sbin/pppd.
--> Check permissions, or specify a "PPPD Path" option in wvdial.conf.
--> Looks like a welcome message.
--> Unable to run /usr/sbin/pppd.
--> Check permissions, or specify a "PPPD Path" option in wvdial.conf.
--> Looks like a welcome message.
--> Unable to run /usr/sbin/pppd.
--> Check permissions, or specify a "PPPD Path" option in wvdial.conf.
--> Looks like a welcome message.
--> Unable to run /usr/sbin/pppd.
--> Check permissions, or specify a "PPPD Path" option in wvdial.conf.
--> Looks like a welcome message.
--> Unable to run /usr/sbin/pppd.
--> Check permissions, or specify a "PPPD Path" option in wvdial.conf.
--> Looks like a welcome message.
--> Unable to run /usr/sbin/pppd.
--> Check permissions, or specify a "PPPD Path" option in wvdial.conf.
--> Looks like a welcome message.
--> Unable to run /usr/sbin/pppd.
--> Check permissions, or specify a "PPPD Path" option in wvdial.conf.
--> Looks like a welcome message.
--> Unable to run /usr/sbin/pppd.
--> Check permissions, or specify a "PPPD Path" option in wvdial.conf.
--> Looks like a welcome message.
--> Unable to run /usr/sbin/pppd.
--> Check permissions, or specify a "PPPD Path" option in wvdial.conf.
--> Looks like a welcome message.
--> Unable to run /usr/sbin/pppd.
--> Check permissions, or specify a "PPPD Path" option in wvdial.conf.
--> Looks like a welcome message.
--> Unable to run /usr/sbin/pppd.
--> Check permissions, or specify a "PPPD Path" option in wvdial.conf.
--> Looks like a welcome message.
--> Unable to run /usr/sbin/pppd.
--> Check permissions, or specify a "PPPD Path" option in wvdial.conf.
--> Looks like a welcome message.
--> Unable to ru...

jkohler2 (jkohler2) wrote :

Gnome-ppp still fails at the user level as shown above. At the super user level, my Acer laptop with a Zoom usb modem
 connects with the following messages marked critical:

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: 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,,984-1940
GNOME PPP: STDERR: --> Waiting for carrier.
GNOME PPP: STDERR: ATM1L3DT*70,,984-1940
GNOME PPP: STDERR: CONNECT 57600
GNOME PPP: STDERR: --> Carrier detected. Starting PPP immediately.
GNOME PPP: STDERR: --> Starting pppd at Mon Apr 26 11:48:21 2010
GNOME PPP: STDERR: --> Pid of pppd: 1608
GNOME PPP: STDERR: --> Using interface ppp0
GNOME PPP: STDERR: --> pppd: 0$�

(gnome-ppp:1605): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion `g_utf8_validate (text, len, NULL)' failed
GNOME PPP: STDERR: --> pppd: 0$�

(gnome-ppp:1605): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion `g_utf8_validate (text, len, NULL)' failed
GNOME PPP: STDERR: --> pppd: 0$�

(gnome-ppp:1605): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion `g_utf8_validate (text, len, NULL)' failed
GNOME PPP: STDERR: --> pppd: 0$�

(gnome-ppp:1605): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion `g_utf8_validate (text, len, NULL)' failed
GNOME PPP: STDERR: --> local IP address 66.81.36.230
GNOME PPP: STDERR: --> pppd: 0$�

(gnome-ppp:1605): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion `g_utf8_validate (text, len, NULL)' failed
GNOME PPP: STDERR: --> remote IP address 69.19.217.21
GNOME PPP: STDERR: --> pppd: 0$�

(gnome-ppp:1605): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion `g_utf8_validate (text, len, NULL)' failed
GNOME PPP: STDERR: --> primary DNS address 66.81.1.250
GNOME PPP: STDERR: --> pppd: 0$�

(gnome-ppp:1605): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion `g_utf8_validate (text, len, NULL)' failed
GNOME PPP: STDERR: --> secondary DNS address 66.81.1.252
GNOME PPP: STDERR: --> pppd: 0$�

(gnome-ppp:1605): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion `g_utf8_validate (text, len, NULL)' failed

I am glad I can connect with the dial up modem, but confused by these messages.

John

Jeremy Foshee (jeremyfoshee) wrote :

Hi jkohler2,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 555442

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete

Thanks for the suggestion. I did use the ISO cd and did the upgrade online
from
a mirror site. I think I have the latest version, but I'll use the command
you wrote below to confirm it.

John

On Tue, Apr 27, 2010 at 6:46 PM, Jeremy Foshee
<email address hidden>wrote:

> Hi jkohler2,
>
> Please be sure to confirm this issue exists with the latest development
> release of Ubuntu. ISO CD images are available from
> http://cdimage.ubuntu.com/releases/ . If the issue remains, please run
> the following command from a Terminal (Applications->Accessories->Terminal).
> It will automatically gather and attach updated debug information to this
> report.
>
> apport-collect -p linux 555442
>
> Also, if you could test the latest upstream kernel available that would be
> great. It will allow additional upstream developers to examine the issue.
> Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've
> tested the upstream kernel, please remove the 'needs-upstream-testing' tag.
> This can be done by clicking on the yellow pencil icon next to the tag
> located at the bottom of the bug description and deleting the
> 'needs-upstream-testing' text. Please let us know your results.
>
> Thanks in advance.
>
> [This is an automated message. Apologies if it has reached you
> inappropriately; please just reply to this message indicating so.]
>
>
> ** Tags added: needs-kernel-logs
>
> ** Tags added: needs-upstream-testing
>
> ** Tags added: kj-triage
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
> --
> Gnome-ppp fails under ubuntu 10.04, works under 9.04
> https://bugs.launchpad.net/bugs/555442
> You received this bug notification because you are a direct subscriber
> of the bug.
>

AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0p: john 1727 F...m pulseaudio
 /dev/snd/controlC0: john 1727 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0x98300000 irq 22'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,10250136,00100003 HDA:14f12c06,10250136,00100000'
   Controls : 11
   Simple ctrls : 8
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=5f14c57d-6fec-4c11-9fd2-08d57bc55702
MachineType: Acer Aspire 5315
Package: linux (not installed)
ProcCmdLine: root=UUID=d4bcc633-cedd-4e1a-8c24-99ebafcb8ae5 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-21.59-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-21-generic N/A
 linux-firmware 1.26
Uname: Linux 2.6.31-21-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WpaSupplicantLog:

dmi.bios.date: 11/10/2008
dmi.bios.vendor: Acer
dmi.bios.version: V1.45
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Acadia
dmi.board.vendor: Acer
dmi.board.version: V1.45
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.45
dmi.modalias: dmi:bvnAcer:bvrV1.45:bd11/10/2008:svnAcer:pnAspire5315:pvrV1.45:rvnAcer:rnAcadia:rvrV1.45:cvnAcer:ct1:cvrV1.45:
dmi.product.name: Aspire 5315
dmi.product.version: V1.45
dmi.sys.vendor: Acer

tags: removed: needs-kernel-logs
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
importance: Undecided → Medium
Stefan Leitner (s-o-l) wrote :

This bug seems to be related to this bug: https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/292203

Try to add your user to the group dip ... maybe it helps...

jkohler2 (jkohler2) wrote :

Gnome-ppp works now with Ubuntu 10.04, with the following connection text:

 Here is the listing for my Ubuntu Linux
program "Gnome-PPP:"

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: 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,,14157021941
GNOME PPP: STDERR: --> Waiting for carrier.
GNOME PPP: STDERR: ATM1L3DT*70,,14157021941
GNOME PPP: STDERR: CONNECT 48000/ARQ/V92/LAPM/V42BIS
GNOME PPP: STDERR: --> Carrier detected. Starting PPP immediately.
GNOME PPP: STDERR: --> Starting pppd at Sat Nov 13 07:30:50 2010
GNOME PPP: STDERR: --> Pid of pppd: 5412
GNOME PPP: STDERR: --> Using interface ppp0
GNOME PPP: STDERR: --> pppd: 0d{
GNOME PPP: STDERR: --> pppd: 0d{
GNOME PPP: STDERR: --> pppd: 0d{
GNOME PPP: STDERR: --> pppd: 0d{
GNOME PPP: STDERR: --> local IP address 69.19.240.117
GNOME PPP: STDERR: --> pppd: 0d{
GNOME PPP: STDERR: --> remote IP address 69.19.217.21
GNOME PPP: STDERR: --> pppd: 0d{
GNOME PPP: STDERR: --> primary DNS address 66.81.1.250
GNOME PPP: STDERR: --> pppd: 0d{
GNOME PPP: STDERR: --> secondary DNS address 66.81.1.252
GNOME PPP: STDERR: --> pppd: 0d These appear to be errors but I don't really know...

jkohler2 (jkohler2) wrote :

This is a new listing of GNOME-PPP (wvdial) when I dialed up tonight.
The connection was successful, but the listing confuses me.

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: 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,,14157021941
GNOME PPP: STDERR: --> Waiting for carrier.
GNOME PPP: STDERR: ATM1L3DT*70,,14157021941
GNOME PPP: STDERR: CONNECT 48000/ARQ/V92/LAPM/V42BIS
GNOME PPP: STDERR: --> Carrier detected. Starting PPP immediately.
GNOME PPP: STDERR: --> Starting pppd at Fri Nov 19 22:01:54 2010
GNOME PPP: STDERR: --> Pid of pppd: 2943
GNOME PPP: STDERR: --> Using interface ppp0
GNOME PPP: STDERR: --> pppd: 0�

(gnome-ppp:2940): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion `g_utf8_validate (text, len, NULL)' failed
GNOME PPP: STDERR: --> pppd: 0�

(gnome-ppp:2940): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion `g_utf8_validate (text, len, NULL)' failed
GNOME PPP: STDERR: --> pppd: 0�

(gnome-ppp:2940): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion `g_utf8_validate (text, len, NULL)' failed
GNOME PPP: STDERR: --> pppd: 0�

(gnome-ppp:2940): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion `g_utf8_validate (text, len, NULL)' failed
GNOME PPP: STDERR: --> local IP address 69.19.240.7
GNOME PPP: STDERR: --> pppd: 0�

(gnome-ppp:2940): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion `g_utf8_validate (text, len, NULL)' failed
GNOME PPP: STDERR: --> remote IP address 69.19.217.21
GNOME PPP: STDERR: --> pppd: 0�

(gnome-ppp:2940): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion `g_utf8_validate (text, len, NULL)' failed
GNOME PPP: STDERR: --> primary DNS address 66.81.1.250
GNOME PPP: STDERR: --> pppd: 0�

(gnome-ppp:2940): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion `g_utf8_validate (text, len, NULL)' failed
GNOME PPP: STDERR: --> secondary DNS address 66.81.1.252
GNOME PPP: STDERR: --> pppd: 0�

(gnome-ppp:2940): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion `g_utf8_validate (text, len, NULL)' failed

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers