[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#403681: marked as done (kpilot: KPilot no longer works with Handspring Visor)

Your message dated Tue, 27 Mar 2007 18:52:33 +0200
with message-id <200703271852.46716.debian@pusling.com>
and subject line Bug#403681: kpilot: KPilot no longer works with Handspring Visor
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: kpilot
Version: 4:3.5.5.dfsg.1-2
Severity: important


I use KPilot with a Handspring Visor. Everything works fine with Debian
sarge.

With Debian etch KPilot does not work anymore. The assistant fails to detect
the PDA. After manually inserting /dev/ttyUSB1 as device and starting
the syncronization the Visor instantly gives an error message about a
failed connection and kpilotDaemon uses all the CPU.
The interesting part is that synchronization with jpilot actually works
under Debian etch (but this is not what I want).

I did a fairly long debugging session with one of the KPilot authors. At
first it was very difficult to get a useful backtrace because gdb in
Debian etch is horribly broken (but this is another story). Result of
this debugging session was that the error is not within KPilot but
somewhere else in the system.

I did test some other distributions regarding this problem. Here are the
results:
Fedora 6     - works
Suse 10.1    - works
Suse 10.2    - BROKEN!
Debian sarge - works
Debian etch  - BROKEN!

There seem to be some changes in current Linux releases that are
breaking KPilot.

I did a fresh install of Debian etch (and downgraded gdb to v6.3) and
generated a backtrace (gdb kpilotDaemon, run --nofork, hotsync button,
crash, Ctrl+C, bt):

#0  0xb7ba73ec in pi_serial_impl_init () from /usr/lib/libpisock.so.9
#1  0x0000000e in ?? ()
#2  0xb7bc5c75 in slp_rx () from /usr/lib/libpisock.so.9
#3  0xb7bbf9f6 in padp_tx () from /usr/lib/libpisock.so.9
#4  0xb7bc722c in pi_send () from /usr/lib/libpisock.so.9
#5  0xb7bc7291 in pi_write () from /usr/lib/libpisock.so.9
#6  0xb7bae8cd in dlp_request_write () from /usr/lib/libpisock.so.9
#7  0xb7bae985 in dlp_exec () from /usr/lib/libpisock.so.9
#8  0xb7bb8bad in dlp_ReadSysInfo () from /usr/lib/libpisock.so.9
#9  0xb7b93c72 in KPilotDeviceLink::acceptDevice (this=0x80d8970) at kpilotlink.cc:785
#10 0xb7b94d2f in KPilotDeviceLink::qt_invoke (this=0x80d8970, _id=7, _o=0xbfa76278) at kpilotdevicelink.moc:88
#11 0xb6efecb3 in QObject::activate_signal (this=0x8142df8, clist=0x8100cf8, o=0xbfa76278) at kernel/qobject.cpp:2356
#12 0xb6eff5ba in QObject::activate_signal (this=0x8142df8, signal=2, param=14) at kernel/qobject.cpp:2449
#13 0xb7288a87 in QSocketNotifier::activated (this=0x8142df8, t0=14) at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85
#14 0xb6f2145e in QSocketNotifier::event (this=0x8142df8, e=0xbfa765d0) at kernel/qsocketnotifier.cpp:258
#15 0xb6e96bd6 in QApplication::internalNotify (this=0xbfa76858, receiver=0x8142df8, e=0xbfa765d0) at kernel/qapplication.cpp:2635
#16 0xb6e989f3 in QApplication::notify (this=0xbfa76858, receiver=0x8142df8, e=0xbfa765d0) at kernel/qapplication.cpp:2358
#17 0xb75bee0e in KApplication::notify (this=0xbfa76858, receiver=0x8142df8, event=0xbfa765d0) at kapplication.cpp:550
#18 0xb6e2a3d1 in QApplication::sendEvent (receiver=0x8142df8, event=0xbfa765d0) at qapplication.h:520
#19 0xb6e88f89 in QEventLoop::activateSocketNotifiers (this=0x80929c8) at kernel/qeventloop_unix.cpp:578
#20 0xb6e3e704 in QEventLoop::processEvents (this=0x80929c8, flags=4) at kernel/qeventloop_x11.cpp:383
#21 0xb6eb1129 in QEventLoop::enterLoop (this=0x80929c8) at kernel/qeventloop.cpp:198
#22 0xb6eb0f4a in QEventLoop::exec (this=0x80929c8) at kernel/qeventloop.cpp:145
#23 0xb6e9876f in QApplication::exec (this=0xbfa76858) at kernel/qapplication.cpp:2758
#24 0x0806fccd in main (argc=65925054, argv=0xe000203) at pilotDaemon.cc:1415
#25 0xb792dea8 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#26 0x08053d71 in _start () at ../sysdeps/i386/elf/start.S:119

I hope this helps.

Greetings and thank you very much

Ronny Standtke

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8)

Versions of packages kpilot depends on:
ii  debconf [debconf-2.0]  1.5.8             Debian configuration management sy
ii  kdelibs4c2a            4:3.5.5a.dfsg.1-5 core libraries and binaries for al
ii  libc6                  2.3.6.ds1-8       GNU C Library: Shared libraries
ii  libgcc1                1:4.1.1-19        GCC support library
ii  libkcal2b              4:3.5.5.dfsg.1-2  KDE calendaring library
ii  libpisock9             0.12.1-5          library for communicating with a P
ii  libqt3-mt              3:3.3.7-1         Qt GUI Library (Threaded runtime v
ii  libstdc++6             4.1.1-19          The GNU Standard C++ Library v3

kpilot recommends no packages.

-- debconf information:
  shared/pilot/port: None

--- End Message ---
--- Begin Message --- 
On Tuesday 27 March 2007, Colin Tuckley wrote:
> I have been using a Handspring Visor with KPilot in Etch since January.
>
> I can confirm that it works.

Thanks. I will close it.

/Sune


-- 
How to save a space bar of the space bar from Mac and from the preferences 
menu within Photoshop NT?

You neither must mount a Internet address, nor should ever disable a AGP 
connector to reset the window.

Attachment: pgpNxqFHW5FMM.pgp
Description: PGP signature


--- End Message ---
Reply to: