Hide Forgot
Description of problem: I have purchased BSNL Broadband hardware long back. Previous I had Fedora 12 OS on that Join_Air(3rd Party software, Provided by Hardware) as well as wvdial working perfectly. but I hard formatted harddisk and installed Fedora 15 and now I can't able connect neither by Join_Air nor by wvdial nor by Control-centre. When I connect hardware (USB stick) I waited for few minutes to get Cellone get detected. once its detected and when I try to click on connection, then after that control-centre gets crashed. When I see wvdial.conf file it shows username as null and password as null Might it is ok...as BSNL doesn't come with username and password. its get connected without username password. first I thought it was SElinux problem. but with help of SE-Troubleshooting I have fixed that issue so log file is reported with following message. ----------------- May 23 19:16:39 localhost pppd[7650]: /usr/lib/./pppd/2.4.5/passwordfd.so: undefined symbol: eaptls_check_hook May 23 19:16:39 localhost pppd[7650]: Couldn't load plugin passwordfd.so May 23 19:16:42 localhost NetworkManager[6977]: <info> (em1): device state change: activated -> disconnected (reason 'user-requested') [100 30 39] ----------------- So when I commented line in file /etc/ppp/peers/wvdial #plugin passwordfd.so and manually added one line in file /etc/wvdial.conf APN = bsnlnet Then with the command line its get connected but the problem is that with no bandwidth. I mean its connected but we can't able to browse internet. I am not sure what is the issue in it? whether its bug or configuration issue? Version-Release number of selected component (if applicable): My Control-centre version : 3.0.1.1-6fc15 kernel : 2.6.38.6-27.fc15 lsusb shows Bus 001 Device 004: ID 19d2:0108 ONDA Communication S.p.A. How reproducible: connect BSNL mobile broadband hardware. wait till Cellone(India,3g) get detected. once cellone detected then from control-centre try to connect mobile broadband and suddenly it gets crashed Steps to Reproduce: 1.Connect USB hardware 2. Wait till cellone network detected 3. Try to connect mobile broadband 4. Control-centre crashed. Actual results: Control-centre gets crashed. Expected results: Control-centre should get connected with some bandwidth for usability. Additional info: Let me know if you need any. I have tried to report this thr' ABRT but kernel-debug-bebuginfo taking large time to download from current wired internet. so reported that manually.
Hello Guys, If you need any more information from me then I would like to forward you in that. I have search on net...but didn't found solution. so please help me.
is their any way...this point should be taken on priority? I am keenly looking for solution for this point.
network manager applet crashes after creation of mobile broadband settings Steps to Reproduce: 1. Connect USB hardware 2. Wait until mobile network is detected 3. Turn-on mobile broadband 4. Click Auto broadband to configure 5. After pressing apply on the mobile broadband configuration, the network manager applet crashes Deleting the mobile broadband connection info at "/etc/NetworkManager/system-connections" restores the network manager applet after re-login. Mobile broadband works before update. NetworkManager.i686 1:0.8.999-3.git20110526.fc15
For me it was not even working from alpha phase.
Created attachment 502962 [details] Related Crash Log Similar issue is encountered on NetworkManager-0.8.999-3.git20110526.fc15.i686 This is the piece of info I grabbed from /var/log/messages. I use a Mobile Broadband dongle connected via USB.
Created attachment 502963 [details] Related Dmesg Info This is the dmesg regarding to the USB mobile broadband modem. For the record, this modem works pretty well under Fedora 14. Meanwhile, I suggest to change the component to NetworkManager.
Created attachment 503230 [details] Messages from log
happening to me too. I removed the connection and created another one but its still the same. It was working fine before the NetworkManager update couple of days back. my current NetworkManager version: NetworkManager-0.8.9997-1.git20110531.fc15.i686
Recently I have updated all updates along with NetworkManager still got this backtrace ============= #0 __kernel_vsyscall () at arch/x86/vdso/vdso32/int80.S:16 #1 0x42b9fb7e in __poll (fds=0x905b628, nfds=9, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #2 0x450edaac in g_poll (fds=0x905b628, nfds=9, timeout=-1) at gpoll.c:132 #3 0x450dec36 in g_main_context_poll (n_fds=9, fds=0x42c665a0, priority=<optimized out>, timeout=<optimized out>, context=0x8f851f0) at gmain.c:3405 #4 g_main_context_iterate (context=0x8f851f0, block=1158601344, dispatch=1, self=0x8f7d9b0) at gmain.c:3087 #5 0x450df457 in g_main_loop_run (loop=0x8ff8ff0) at gmain.c:3300 #6 0x080590d6 in main (argc=1, argv=0xbfa67bf4) at main.c:106 ================== and Please see attached /var/log/messages
Created attachment 503695 [details] /var/log/messages file.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping