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 303752 - gpilotd crashes when I sync my pilot
gpilotd crashes when I sync my pilot
Status: RESOLVED DUPLICATE of bug 274032
Product: gnome-pilot
Classification: Other
Component: gpilotd
unspecified
Other other
: Normal normal
: ---
Assigned To: gnome-pilot Maintainers
gnome-pilot Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-05-11 02:34 UTC by Maxwell Bottiger
Modified: 2005-05-12 02:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Maxwell Bottiger 2005-05-11 02:34:18 UTC
Distribution: Fedora Core release 3.91 (Pre-FC4)
Package: gnome-pilot
Severity: normal
Version: GNOME2.10.0 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: gpilotd crashes when I sync my pilot
Bugzilla-Product: gnome-pilot
Bugzilla-Component: gpilotd
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
I press the sync button, then get a message that gpilotd has crashed. 
Gpilotd attempts to reload several times, but crashes each time.

Steps to reproduce the crash:
1. sync pilot
2. 
3. 

Expected Results:
just a normal sync

How often does this happen?
every time

Additional Information:
the /dev/ttyUSB* files are only created once I press the sync button. 
They are not created with permissions that I can read from:
[sleepylight@shaft ~]$ ls -l /dev/ttyU*
crw-rw----  1 root uucp 188, 0 May 10 22:28 /dev/ttyUSB0
crw-rw----  1 root uucp 188, 1 May 10 22:28 /dev/ttyUSB1


Even if I chmod the dev entries after they are built, it still doesn't
work.

I tried adding the file: /etc/udev/rules.d/10-visor.rules 
with the line: BUS="usb", SYSFS{product}="Palm Handheld*",
KERNEL="ttyUSB*", SYMLINK="pilot"
but that didn't appear to help.

Also, I tried to manually load the visor driver, but that made no
difference.

What are the default configuration rules for a USB palm pilot, and why
doesn't udev ship with the correct rules?


Debugging Information:

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 -1209100608 (LWP 5811)]
(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)
(no debugging symbols found)
(no debugging symbols found)
0x005ea402 in ?? ()

Thread 1 (Thread -1209100608 (LWP 5811))

  • #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




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-05-11 02:34 UTC -------

Comment 1 Elijah Newren 2005-05-12 02:11:59 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 ***