GNOME Bugzilla – Bug 641289
Gnome-Pilot Applet crashes when sending PDA info
Last modified: 2018-07-02 10:32:03 UTC
The Gnome applet crashes every time I hit the "Send to PDA" button in the Configure PDA Window. If I just edit the PDA info (proprietary for example) and hit "OK" the applet freezes for about 30 seconds and then nothing is recorded. I keep getting the "Unknown PDA ID ..." if i try to sync with this default values: Propietary: *username* PDA ID: 1000 PDA name: MyPDA Even if I erase data and reinstall gnome-pilot and conduits, the initial wizard crashes or ends with an error like above in the PDA info step. Sometimes i got an "Unable to send data to gpilotd... " (or something like that) kind of error and crash afterwards. In earlier versions i could sync my palm TX with no issues (except for the missing conduits) and for the evolution conduits i had to upgrade to this version. Im using the upstream solution for missing conduits in Launchpad for this bug: https://bugs.launchpad.net/ubuntu/+source/gnome-pilot/+bug/569601 I think is a bad link between the daemon and the applet itself. i don't know if i can configure the daemon from command line, the documentation shipped with gpilotd does not say anything about it.
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
I got a serious problem here... I've installed again the gnome-pilot application and it got stucked in the wizard. After a few tries (killing the process every time) i managed to bypass the wizard and got to the applet (when the wizard exits it just won't open the applet). After struggling for about 20 minutes finally i could recover the info from the PDA but was incorrect (now i see some strange characters in the proprietary name). Then i tried to reproduce the bug, same as above: go to PDAs, edit..., change the name of the proprietary and click in "Send to PDA" >> crash. I've installed bug-buddy but nothing seems to happen. What i'm doing wrong? Is there a "gpilot-dbg" package I'm missing? Anyway, i think there is a problem with character encoding: I've seen that whenever I use my name without any accents (á, é, í, ó, ú characters) everything "seems" to work fine, except for some freezes about 5 to 10 secs. In earlier versions 2.0.17 (or 2.0.15 i don't remember exactly) I've got no trouble with this char problem. Obviously i WANT my name correctly spelled. Hope this could help you in any way, but I'm curious about the bug-buddy thing. TIA and thanks for the quick answer.
See the link in comment 1 - there's a Details section for using gdb if bug-buddy does not work.
Created attachment 180006 [details] Stack Trace after crash
Created attachment 180007 [details] output after "run" to the crash
I've attached two files containing the output in the console for gdb gpilot-applet BTW I'm experiencing some "hang-ups" in every window-change in the applet. Sometimes bug-buddy pops-up but it says it has no useful info.
Here is something I think may be useful. Related to comunication between applet and PDA. When I trie to configure the conduits the applet crashes again. Here are the steps: # Open the gpilotd-control-applet from it's panel icon. I got the Applet window. # Co to Conduits > Try to configure the EToDo conduit, sometimes here crashes. # If I haven't got the crash allready, i get the crash when I try to change a value (for instance the "One time action" dropbox) or when I apply the changes. I'm attaching the stack trace from gdb.
Created attachment 180175 [details] Stack Trace after conduit configure crash
Joaquin, Thanks for the bug report. I can confirm I'm able to reproduce the bug: 8-bit ascii characters are not being handled correctly. Until this is fixed, I recommend you avoid the accented characters. I suspect your crash in comment 7 is unrelated to this issue. I haven't reproduced that yet.
Created attachment 180946 [details] [review] patch to fix dbus crash with non-utf8 characters This patch will be committed now. It should fix this issue.
Joaquín, any chance you could test this fix?
Tell me how (or link me to a manual or something) and i will.
It requires downloading the attachment in comment 10, applying the patch to the gnome-pilot source using, and recompiling. I'll try and document at the weekend.
I've tested it and here are my impressions. I've managed to change the name with non-ASCII characters but it requires a tweak to work: If you use the charset for the PDA as CP then the character 'í' is passed as '~A' in the handheld. So, I've changed the charset to BIG5 then sent the info data and back to CP--- (can't remember the numbers). If the charset remains at BIG5 I'm unable to sync, and if the 'í' char is passed as '~A' can't sync either (maybe a typo in the charset selection?). Then there was another issue: the status window that pops up every time I sync my palm gone away. Never showed up anymore. I'm opening a new issue on the conduits configure (specially the EToDo conduit that works as a copier) but unfortunately my Palm is gone for service for about a week or so, so I'm unavailable for testing in the meantime. The issue is "partially" solved but i have no clue on the gone status window. Thanks for your time Matt. I hope i can use this software on daily basis.
After trying the patch above for a while i've noticed that all Evolution conduits stopped working. I can't even configure them cos everytime i click on "configure" on each conduit the applet crashes. I don't know what to do now. Should I upload a new stack trace or open a new issue (I tought it's approppriate to post it here cos I'm using the patch attached on comment 10)
gnome-pilot is not under active development anymore and has not seen code changes for seven years. Its codebase has been archived: https://gitlab.gnome.org/Archive/gnome-pilot/commits/master Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again.