[Bug 420752] Re: KFLog crashes when loading a waypoint file.

[Andrew Walsh]

Thanks for your response!

I've tried the new version since I posted the bug report, and you're
right, I can't reproduce the bug either (so presumably it has been
fixed).

I was reporting the bug because that was the version that was
available in Ubuntu... I don't how about how the maintainers do
things, but should the version available in the Ubuntu repositories be
updated? Or removed if it is not supported?

Cheers,

Andrew Walsh.


2009/9/2 Conjacq <cjneeteson at hotmail.com>:
> There is a new version of KFLog: 2.2.0. You can download it from http://www.kflog.org/kflog/download/
> I can't reproduce the bug in the new version. Does this bug also occur when you use the new version?
>
> --
> KFLog crashes when loading a waypoint file.
> https://bugs.launchpad.net/bugs/420752
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “kflog” package in Ubuntu: New
>
> Bug description:
> Binary package hint: kflog
>
> When loading a waypoint file from the Worldwide Soaring Turnpoint Exchange (specifically the file with URL <http://soaringweb.org/TP/BGA/bga_2009.kflogwp>, which I have downloaded) into KFLog, a crash occurs. This is done by clicking the button to the right of the Waypoints drop-down in the Waypoints window (at the bottom left on the default installation). I am using Ubuntu 9.04, and the KFLog package version 2.1.1-3.1. I have tried another waypoint file (<http://soaringweb.org/TP/Bayreuth/bayerth8.kflogwp>) with a similar result. The KDE Crash Handler appears, with the message as follows:
>
> A Fatal Error Occurred
> The application KFLog (kflog) crashed and caused the signal 11 (SIGSEGV)."
>
> It also includes the details appended to the end of this message. Thanks for your help!
>
> DETAILS OF CRASH REPORT:
>
> This backtrace appears to be of no use.
> This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.
>
> (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)
> (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 0x7f7351025750 (LWP 3869)]
> (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)
> 0x00007f734a006cf0 in nanosleep () from /lib/libc.so.6
> [Current thread is 0 (process 3869)]
>
> Thread 1 (Thread 0x7f7351025750 (LWP 3869)):
> #0  0x00007f734a006cf0 in nanosleep () from /lib/libc.so.6
> #1  0x00007f734a006b47 in sleep () from /lib/libc.so.6
> #2  0x00007f734e0296dd in KCrash::startDrKonqi () from /usr/lib/libkdecore.so.4
> #3  0x00007f734e02fdff in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4
> #4  <signal handler called>
> #5  0x00007f734cffe283 in operator== () from /usr/lib/libqt-mt.so.3
> #6  0x00007f734ce289d5 in QListViewItem::setText () from /usr/lib/libqt-mt.so.3
> #7  0x000000000043c109 in ?? ()
> #8  0x000000000043c671 in ?? ()
> #9  0x000000000043c78b in ?? ()
> #10 0x000000000052f2ac in ?? ()
> #11 0x00007f734cd4be3f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
> #12 0x00007f734cd4e162 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
> #13 0x00007f734cd80706 in QWidget::event () from /usr/lib/libqt-mt.so.3
> #14 0x00007f734ccee4a5 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
> #15 0x00007f734ccef497 in QApplication::notify () from /usr/lib/libqt-mt.so.3
> #16 0x00007f734e0f03f2 in KApplication::notify () from /usr/lib/libkdecore.so.4
> #17 0x00007f734cc8cffc in QETWidget::translateMouseEvent () from /usr/lib/libqt-mt.so.3
> #18 0x00007f734cc8bc4e in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
> #19 0x00007f734cc9e82a in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
> #20 0x00007f734cd04ec1 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
> #21 0x00007f734cd04d82 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
> #22 0x0000000000529753 in ?? ()
> #23 0x00007f7349f7d5a6 in __libc_start_main () from /lib/libc.so.6
> #24 0x0000000000425d4a in ?? ()
> #25 0x00007fff59167708 in ?? ()
> #26 0x000000000000001c in ?? ()
> #27 0x0000000000000001 in ?? ()
> #28 0x00007fff5916872f in ?? ()
> #29 0x0000000000000000 in ?? ()
> #0  0x00007f734a006cf0 in nanosleep () from /lib/libc.so.6
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>

-- 
KFLog crashes when loading a waypoint file.
https://bugs.launchpad.net/bugs/420752
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs