Bug 175334 - kpilotDaemon crashes on startup
Summary: kpilotDaemon crashes on startup
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: pilot-link
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-12-08 22:51 UTC by Jesse Barnes
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-04-21 11:00:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Backtrace from the kpilot daemon crash on my machine (3.33 KB, text/plain)
2006-04-15 16:02 UTC, Paul S. Bains
no flags Details

Description Jesse Barnes 2005-12-08 22:51:44 UTC
When I start kpilot, it complains that it can't find the device node for my  
Treo, then kpilotDaemon crashes.  And even after I hit the 'sync' button on my 
Treo, I don't get a device node created, so maybe the udev visor rules are 
broken somehow? 
 
Jesse

Comment 1 Jesse Barnes 2005-12-15 23:54:26 UTC
Installing the new pilot-link package fixed the creation of the device nodes 
(I see /dev/pilot now when I hit the 'sync' button), but kpilotDaemon still 
crashes on startup unless it exists (IOW I have to hit the sync button before 
I start kpilot or I get a nasty SEGV message). 
 

Comment 2 Paul S. Bains 2006-04-15 16:02:38 UTC
Created attachment 127782 [details]
Backtrace from the kpilot daemon crash on my machine

Comment 3 Paul S. Bains 2006-04-15 16:03:45 UTC
Kpilot daemon crashes for me on startup also. I have a Palm Zire 31. It doesn't
matter whether or not I have the sync button on the device pressed before I
start kpilot or not. As soon as I start kpilot or kontact, the kpilot daemon
crashes. I have attached a backtrace.

Comment 4 Than Ngo 2006-04-21 11:00:48 UTC
it seems the same bug #186779 and it's fixed now in 0.11.8-15. It will be
available in rawhide soon. Thanks for your report.


Note You need to log in before you can comment on or make changes to this bug.