reporting bug / cpu 100%

Asked by Lauren Matheson

Hello, I tried to report this bug
bug-buddy --appname gnome-pilot --pid 6700, but bug buddy reports that it does not know the application, how can I file a bug?

What I'm seeing is that the palm does not begin syncing, and following an attempt gpilotd goes to 100% cpu and has to be killed off. devices seem to be created properly, and it looks like some communication begins:

syslog after pressing sync:
Nov 10 17:05:12 bic kernel: [17181523.676000] usb 3-1: new full speed USB device using uhci_hcd and address 7
Nov 10 17:05:12 bic kernel: [17181523.844000] usb 3-1: configuration #1 chosen from 1 choice
Nov 10 17:05:12 bic kernel: [17181523.852000] visor 3-1:1.0: Handspring Visor / Palm OS converter detected
Nov 10 17:05:12 bic kernel: [17181523.852000] usb 3-1: Handspring Visor / Palm OS converter now attached to ttyUSB0
Nov 10 17:05:12 bic kernel: [17181523.852000] usb 3-1: Handspring Visor / Palm OS converter now attached to ttyUSB1

gpilotd after pressing sync:
gpilotd-Message: gnome-pilot 2.0.14 starting...
gpilotd-Message: compiled for pilot-link version 0.12.1
gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network]
gpilotd-Message: Activating CORBA server
gpilotd-Message: bonobo_activation_active_server_register = 0
gpilotd-Message: Watching Cradle (/dev/pilot)
gpilotd-Message: corba: get_pilots(...)
gpilotd-Message: corba: get_pilots(...)
gpilotd-Message: Client seems ok
gpilotd-Message: Client seems ok
gpilotd-Message: monitor_on(pilot_name="MyPilot",client_id = IOR:010000001b000000...)
gpilotd-Message: corba: notify_on(event_type=CONNECT,callback=IOR:010000001b000000...)
gpilotd-Message: corba: notify_on(event_type=CONDUIT,callback=IOR:010000001b000000...)
gpilotd-Message: corba: notify_on(event_type=DISCONNECT,callback=IOR:010000001b000000...)
gpilotd-Message: Found 4766, 0001
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0502, 0736
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 091e, 0004
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 115e, f100
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 082d, 0100
gpilotd-Message: Using net FALSE
gpilotd-Message: Found 082d, 0200
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 082d, 0300
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0c88, 0021
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0001
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0002
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0003
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0020
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0031
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0040
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0050
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0060
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0061
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0070
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 0830, 0080
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 04e8, 8001
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 04e8, 6601
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0038
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0066
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0095
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 009a
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 00c9
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 00da
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 00e9
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0144
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 054c, 0169
gpilotd-Message: Using net TRUE
gpilotd-Message: Found 12ef, 0100
gpilotd-Message: Using net TRUE
gpilotd-Message: setting PILOTRATE=57600

Question information

Language:
English Edit question
Status:
Answered
For:
Gnome-Pilot Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:

This question was reopened

Revision history for this message
Lauren Matheson (inan-coldsnap) said :
#1

mysteriously it works today like it used to. will repost if the problem re-exhibits.

Revision history for this message
Lauren Matheson (inan-coldsnap) said :
#2

it re-exhibited today, rebooted and still doesn't work. perhaps will go away as before.

if anyone knows how to post a gnome-pilot bug please let me know.

Revision history for this message
Lauren Matheson (inan-coldsnap) said :
#3

I left the computer on overnight (as I usually do) and it worked this morning. I use IMAP with evolution, which sometimes blocks for a little while waiting for locks -- is it possible that a busy evolution backend could stop the pilot sync from starting?

Revision history for this message
Lauren Matheson (inan-coldsnap) said :
#4

This 100% CPU usage issue continues. Fairly consistent, occasionally a sync works.

Revision history for this message
Dave Walker (davewalker) said :
#5

Thank you for trying to report a bug.

Is this problem still existing?

If it is then you need to report the bug upstream with gnome.

http://bugzilla.gnome.org/

Can you help with this problem?

Provide an answer of your own, or ask Lauren Matheson for more information if necessary.

To post a message you must log in.