NM 0.7 GSM/3G signal strength is not reported by NM

Bug #262232 reported by Thomas Novin
28
This bug affects 2 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

Binary package hint: network-manager

Previous to NM 0.7 I used comgt and wvdial for 3G. I could report my signal strength with comgt. If there is a standardized way to do this, it could be reported in NM just as it is for wireless.

$ comgt help
comgt Usage: comgt [options] [built in script]'|[external script]

Built in scripts -
  comgt [default] Checks SIM status (requests PIN if required),
                           registration and signal strength reported by
                           datacard.
  comgt info Display configuration of datacard.
  comgt sig Report Signal strength.
  comgt reg Report Registration status.
  comgt PIN Set PIN using COMGTPIN env variable.
  comgt APN Set APN using COMGTAPN env variable.

http://sourceforge.net/projects/comgt

$ apt-cache policy network-manager
network-manager:
  Installed: 0.7~~svn20080818t061112+eni1-0ubuntu1~nm1~hardy1
  Candidate: 0.7~~svn20080818t061112+eni1-0ubuntu1~nm1~hardy1
  Version table:
 *** 0.7~~svn20080818t061112+eni1-0ubuntu1~nm1~hardy1 0
        500 http://ppa.launchpad.net hardy/main Packages
        100 /var/lib/dpkg/status
     0.6.6-0ubuntu5 0
        500 http://se.archive.ubuntu.com hardy/main Packages

Changed in network-manager:
status: New → Confirmed
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

 Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in network-manager:
status: Confirmed → Incomplete
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

 We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in network-manager:
status: Incomplete → Invalid
Revision history for this message
Thomas Novin (thomasn80) wrote :

Yes, this is still an issue.

Changed in network-manager:
status: Invalid → New
Revision history for this message
Alexander Sack (asac) wrote :

this will be fixed by modemmanager (will be there for 0.8)

Changed in network-manager:
importance: Undecided → Wishlist
status: New → Triaged
Revision history for this message
Thomas Novin (thomasn80) wrote :

modemmanager is in karmic. Fix released?

Revision history for this message
Przemek K. (azrael) wrote :

It's still an issue in karmic (9.10).
Can anyone forward this bug upstream?
https://wiki.ubuntu.com/Bugs/Upstream/GNOME

Revision history for this message
Przemek K. (azrael) wrote :

Hmm, according to this blog post by one of NM devs, this should work now.
http://blogs.gnome.org/dcbw/2010/04/07/networkmanager-0-8-the-taste-of-a-new-generation/
I'll have to recheck this...

Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

network-manager 0.8 is in Ubuntu 10.04, but not in Ubuntu 9.10. Given comment #4 from Alexander, this may now be fixed in Ubuntu 10.04, so maybe someone can test it with a live CD of the development release. Thanks.

Changed in network-manager (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

It doesn't seem to be fixed in any obvious way in karmic...

Revision history for this message
Thomas Novin (thomasn80) wrote :

It's fxed now at least (Maverick). I'll try to close this.

Changed in network-manager (Ubuntu):
status: Incomplete → Fix Released
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.