#28 Wireless Assistant crashes when signal gets lost

open
nobody
None
5
2007-11-09
2007-11-09
Jack Omen
No

After associating with a wireless network, if I move my laptop to any place where the signal is too weak (i.e. the AP is hidden by some obstacle), the application crashes as soon as the signal gets lost.

I am using Wireless Assistant 0.5.7 on Kubuntu Gutsy.
Kernel version: 2.6.22.9-custom #1 SMP Sun Oct 28 15:51:06 CET 2007 i686 GNU/Linux
libc6 Version: 2.6.1-1ubuntu10

Kcrash report:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1229498688 (LWP 20061)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0x0806be5e in ?? ()
#7 0x080795df in ?? ()
#8 0x0806c717 in ?? ()
#9 0xb7725893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#10 0xb7726338 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0xb7ab39b2 in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#12 0xb774d5ba in QTimer::event () from /usr/lib/libqt-mt.so.3
#13 0xb76bcaf0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#14 0xb76be91f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#15 0xb70f4ca2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#16 0xb764f209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#17 0xb76af53b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#18 0xb7663d49 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#19 0xb76d71ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#20 0xb76d6fde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#21 0xb76be699 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#22 0x0805290f in ?? ()
#23 0xb7190050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#24 0x08052571 in ?? ()

Discussion

  • Mitch Golden

    Mitch Golden - 2008-01-20

    Logged In: YES
    user_id=688530
    Originator: NO

    I see a very similar crash. However, mine wasn't caused by the loss of signal. I had signal, and hibernated the machine when connected. When I restored from the hibernation, I would *sometimes* see this crash. My backtrace looks very similar, but not identical to the one reported (see below).

    ~> wlassistant -v
    Qt: 3.3.7
    KDE: 3.5.8
    Wireless Assistant: 0.5.7

    The machine is a Dell Inspiron 6400, with a broadcom chip running on ndiswrapper under Kubuntu Gutsy.

    [KCrash handler]
    #6 0xb7a51257 in QString::QString () from /usr/lib/libqt-mt.so.3
    #7 0x0806de41 in ?? ()
    #8 0x08078a37 in ?? ()
    #9 0x08079678 in ?? ()
    #10 0x0806c717 in ?? ()
    #11 0xb7739893 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
    #12 0xb773a338 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
    #13 0xb7ac79b2 in QTimer::timeout () from /usr/lib/libqt-mt.so.3
    #14 0xb77615ba in QTimer::event () from /usr/lib/libqt-mt.so.3
    #15 0xb76d0af0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
    #16 0xb76d291f in QApplication::notify () from /usr/lib/libqt-mt.so.3
    #17 0xb7108ca2 in KApplication::notify () from /usr/lib/libkdecore.so.4
    #18 0xb7663209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
    #19 0xb76c353b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
    #20 0xb7677d49 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
    #21 0xb76eb1ce in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
    #22 0xb76eafde in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
    #23 0xb76d2699 in QApplication::exec () from /usr/lib/libqt-mt.so.3
    #24 0x0805290f in ?? ()
    #25 0xb71a4050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
    #26 0x08052571 in ?? ()

     
  • Nobody/Anonymous

    Logged In: NO

    Hi,

    I added my bugtrace, it is very similar to both earlier. I have no problem with signal. No hibernation. No problems at all. I do not know why it is happening. Maybe, it is caused by driver iwlwifi-3945, because after rmmod and modprobe the driver and starting the wlassistant everything works fine. it is usual that application crashes 3 times in minutes, but on the other hand application is able to run almost more than one day and does not crash.

    <bugtrace>
    [?1034h(no debugging symbols found)
    Using host libthread_db library "/lib64/libthread_db.so.1".
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    [Thread debugging using libthread_db enabled]
    [New Thread 46912496293360 (LWP 5977)]
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    [KCrash handler]
    #5 0x0000003e7ce37fb0 in QString::QString ()
    from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
    #6 0x000000000042507c in ?? ()
    #7 0x000000000042f8f7 in ?? ()
    #8 0x00000000004304bc in ?? ()
    #9 0x0000000000423a5b in ?? ()
    #10 0x0000003e7cb63c29 in QObject::activate_signal ()
    from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
    #11 0x0000003e7cb64900 in QObject::activate_signal ()
    from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
    #12 0x0000003e7cb87345 in QTimer::event ()
    from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
    #13 0x0000003e7cb02b75 in QApplication::internalNotify ()
    from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
    #14 0x0000003e7cb03e40 in QApplication::notify ()
    from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
    #15 0x0000003b31dc7e38 in KApplication::notify ()
    from /usr/lib64/libkdecore.so.4
    #16 0x0000003e7caf7d8c in QEventLoop::activateTimers ()
    from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
    #17 0x0000003e7cab10d1 in QEventLoop::processEvents ()
    from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
    #18 0x0000003e7cb1a321 in QEventLoop::enterLoop ()
    from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
    #19 0x0000003e7cb1a202 in QEventLoop::exec ()
    from /usr/lib64/qt-3.3/lib/libqt-mt.so.3
    #20 0x000000000040cbd0 in QWidget::setUpdatesEnabled ()
    #21 0x000000342921e074 in __libc_start_main () from /lib64/libc.so.6
    #22 0x000000000040c889 in QWidget::setUpdatesEnabled ()
    #23 0x00007fff518abbb8 in ?? ()
    #24 0x0000000000000000 in ?? ()

    </bugtrace>

     
  • Jack Omen

    Jack Omen - 2008-05-30

    Logged In: YES
    user_id=1100438
    Originator: YES

    The bug persists on Kubuntu Hardy, with kernel 2.6.24.
    Why is this bug still unassigned, after more than 6 months?? Will anyone take care?
    We cannot go on using a tool which crashes randomly all the times, even when iwconfig reports Signal level:-76 dBm...

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks