GNOME Bugzilla – Bug 365181
crash in PalmOS Devices: trying to sync a treo 65...
Last modified: 2007-09-14 07:32:10 UTC
What were you doing when the application crashed? trying to sync a treo 650 Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 62988288 vsize: 0 resident: 62988288 share: 0 rss: 13492224 rss_rlim: 0 CPU usage: start_time: 1161836910 rtime: 0 utime: 110 stime: 0 cutime:103 cstime: 0 timeout: 7 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gpilotd-control-applet' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225844544 (LWP 25585)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 78373
Thread 1 (Thread -1225844544 (LWP 25585))
Thanks for the bug report. Please send as much of the following info as you can: What version of gnome-pilot and pilot-link you are using? Is this bug reproducible? Does it happen every time you try to run the gpilotd-control-applet, and does it happen with the same back trace each time (in particular, the 'gnome_pilot_pdialog_get_type' --> 'g_free' pairing)? It would be extremely helpful if you were able to get a full stack trace containing line number information (for the gnome-pilot sections at least). Perhaps there are gnome-pilot 'dbg' packages you can install to add extra information. Many thanks for reporting this bug. It appears to be similar to recently reported bug #356548, but we didn't get enough information on that one to track down the cause.
*** Bug 369800 has been marked as a duplicate of this bug. ***
confirming as per duplicate
*** Bug 371671 has been marked as a duplicate of this bug. ***
*** Bug 372309 has been marked as a duplicate of this bug. ***
*** Bug 372708 has been marked as a duplicate of this bug. ***
I'm not sure that it's correct, but I wrote on terminal (gpilotd --help). It gave me: gpilotd-Message: gnome-pilot 2.0.14 starting... gpilotd-Message: compiled for pilot-link version 0.12.1 I think it's the version number. This bug is reproducible. Every time I try to sync the Palm T5 it happened. Before I start using the Ubuntu 6.10, I test the kurumin 6.1 (www.guiadohardware.net). It's a brazilian linux distribution that uses KDE. I could sync the PDA on kpilot. I really don't know how to answer the other questions. But if you explain-me exactly what should I do. I will be happy to contribute. Thanks for the interesting.
OK, I need some help here. I can't reproduce this bug on my system, so I'm looking for some help. Here's what I like you to try: 1. go to bug #362565, and try building the experimental gnome-pilot package referenced there. You may need to install the 'development' pilot-link package. IMPORTANT: please turn off optimisation when building, by running 'make CFLAGS=-g' when building gnome-pilot. 2. Run the /tmp/gp/bin/gpilotd-control-applet that you just built. See if your problem is fixed. Try changing the 'timeout' value in your configured device. Values in the range 1-10 should be of interest. I'd like to know if that fixes the problem. If it does, then that indicates that we've fixed a problem communicating with the palm device, but I'd still like to prevent gnome-pilot from crashing when this occurs. So, if you have compiled the package above and are still able to trigger the crash (maybe with a timeout set to 1), then I'd like you to do the following: 3. exit any config applet and kill any running gpilotd process (killall gpilotd). 4. start gpilotd with pilot-link debugging enabled: env PILOT_DEBUG="DEV SLP CMP PADP NET SOCK" PILOT_DEBUG_LEVEL="DEBUG" /tmp/gp/libexec/gpilotd 5. in another terminal start gpilotd-control-applet in the debugger: gdb /tmp/gp/bin/gpilotd-control-applet 6. Run until you get the crash. 7. at the gdb prompt, enter the command 'bt' to get a back trace. 8. Grab all output from the gpilotd and gpilotd-control-applet terminal windows and attach to this bug. If you can't trigger the bug with the patched gnome-pilot, please follow all the above steps using the standard 2.0.14 release tarball, which you can get from: http://live.gnome.org/GnomePilot If you need help following the above steps, feel free to mail me. Thanks.
Hi again, I'm still looking for help with this bug. I'd like to have a fix before releasing 2.0.15 (which will roll up a couple of other bugs that have been found in 2.0.14). So, if you are affected by this bug it would be great if you could read the previous comment and help get to the bottom of this issue.
*** Bug 377340 has been marked as a duplicate of this bug. ***
Is anyone out there? A quick question on reproducibility: I have a hunch that this bug may only happen if the "PDA Settings" window is opened more than once. Can anyone confirm or deny this? In particular, if you have this crash, does it happen the first time you try to retrieve the owner name / ID from the PDA, or only on second and subsequent attempts? What I'm investigating is the possibility that if the "PDA settings" window is created twice (i.e. you use the "Add" button on the "PDAs" screen to bring up a "PDA settings" window, do stuff, complete or cancel the window, and then do "Add" again) then the config applet becomes unstable. This theory would be in trouble if someone can produce this bug on first using the "Add" button.
I finally managed to reproduce this, and it appears that my hunch was correct. I have released gnome-pilot 2.0.15 to fix this and a couple of other serious issues found in 2.0.14. Feel free to update this bug with any successes/failures found with 2.0.15 on this issue.
*** Bug 380681 has been marked as a duplicate of this bug. ***
NOTE: To Ubuntu Edgy users: if you are running the 'gnome-pilot-2.0.14-0Ubuntu2' package, you may want to try installing an unofficial package built to fix this problem and another one that caused crashing when attempting to sync. See: http://www.inference.phy.cam.ac.uk/mcdavey/downloads/
*** Bug 381342 has been marked as a duplicate of this bug. ***
*** Bug 383885 has been marked as a duplicate of this bug. ***
*** Bug 386048 has been marked as a duplicate of this bug. ***
*** Bug 386355 has been marked as a duplicate of this bug. ***
*** Bug 387414 has been marked as a duplicate of this bug. ***
*** Bug 387810 has been marked as a duplicate of this bug. ***
*** Bug 388940 has been marked as a duplicate of this bug. ***
*** Bug 389662 has been marked as a duplicate of this bug. ***
*** Bug 390622 has been marked as a duplicate of this bug. ***
*** Bug 390977 has been marked as a duplicate of this bug. ***
*** Bug 391944 has been marked as a duplicate of this bug. ***
*** Bug 393956 has been marked as a duplicate of this bug. ***
*** Bug 393272 has been marked as a duplicate of this bug. ***
*** Bug 396943 has been marked as a duplicate of this bug. ***
*** Bug 399471 has been marked as a duplicate of this bug. ***
*** Bug 400218 has been marked as a duplicate of this bug. ***
*** Bug 400740 has been marked as a duplicate of this bug. ***
*** Bug 401773 has been marked as a duplicate of this bug. ***
*** Bug 402216 has been marked as a duplicate of this bug. ***
*** Bug 404038 has been marked as a duplicate of this bug. ***
*** Bug 404613 has been marked as a duplicate of this bug. ***
*** Bug 406017 has been marked as a duplicate of this bug. ***
*** Bug 409137 has been marked as a duplicate of this bug. ***
*** Bug 414101 has been marked as a duplicate of this bug. ***
*** Bug 430241 has been marked as a duplicate of this bug. ***
*** Bug 430745 has been marked as a duplicate of this bug. ***
*** Bug 443388 has been marked as a duplicate of this bug. ***
*** Bug 451055 has been marked as a duplicate of this bug. ***
*** Bug 476666 has been marked as a duplicate of this bug. ***