After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 315475 - gpilotd crash: kernel: usb 3-2: device not accepting address 5, error -75
gpilotd crash: kernel: usb 3-2: device not accepting address 5, error -75
Status: RESOLVED DUPLICATE of bug 274032
Product: gnome-pilot
Classification: Other
Component: gpilotd
2.0.x
Other All
: High critical
: ---
Assigned To: gnome-pilot Maintainers
gnome-pilot Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-09-07 18:41 UTC by Ken
Modified: 2005-09-11 09:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Ken 2005-09-07 18:41:06 UTC 
Steps to reproduce:
Steps to reproduce the crash:
1. Login as a regular user (not root)
2. run gpilotd-control-applet
3. Specify USB, 56Kbps, /dev/USB1
4. Connect a handspring treo 600 to the USB port
5. Press the SYNC button on the treo cable


Stack trace:
Backtrace was generated from '/usr/libexec/gpilotd'

(no debugging symbols found)
Using host libthread_db library "/lib/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)
[Thread debugging using libthread_db enabled]
[New Thread -1208371520 (LWP 7360)]
(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)
(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)
0x0055d402 in ?? ()

+ Trace 62763

Thread 1 (Thread -1208371520 (LWP 7360))

  • #0 ??
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 pi_listen
    from /usr/lib/libpisock.so.9
  • #5 device_equal_by_io
  • #6 network_device_err
  • #7 g_main_context_wakeup
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_context_iteration
    from /usr/lib/libglib-2.0.so.0
  • #11 main 



Other information:
This worked in fedora FC3 until approx Aug 16, 2005.  Now it is failing
in FC3.  Upgrading to FC4 does not seem to help.

from rpm -qa:
gnome-pilot-devel-2.0.13-2
pilot-link-0.12.0-0.pre3.0.fc4.1
gnome-pilot-2.0.13-2
pilot-link-devel-0.12.0-0.pre3.0.fc4.1

from lsmod | grep visor :
visor                  20813  0
usbserial              29737  1 visor

from  modprobe -l visor | 
/lib/modules/2.6.12-1.1447_FC4/kernel/drivers/usb/serial/visor.ko
Comment 1 Christian Kirbach 2005-09-11 09:47:24 UTC 
Thanks for the bug report. This particular bug has already been reported into 
our bug tracking system, but please feel free to report any further bugs you 
find.

*** This bug has been marked as a duplicate of 274032 ***