Bug 848505
Summary: | [abrt] jpilot-1.8.1-3.fc17: __GI_raise: Process /usr/bin/jpilot was killed by signal 6 (SIGABRT) | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Adam Stein <adam> | ||||||||||||
Component: | jpilot | Assignee: | Peter Schiffer <pschiffe> | ||||||||||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||
Priority: | unspecified | ||||||||||||||
Version: | 17 | CC: | pschiffe, varekova | ||||||||||||
Target Milestone: | --- | ||||||||||||||
Target Release: | --- | ||||||||||||||
Hardware: | x86_64 | ||||||||||||||
OS: | Unspecified | ||||||||||||||
Whiteboard: | abrt_hash:22751ca7f034186fabe4bcd7fa4d123410c16dac | ||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||
Clone Of: | Environment: | ||||||||||||||
Last Closed: | 2012-12-15 19:30:24 UTC | Type: | --- | ||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||
Documentation: | --- | CRM: | |||||||||||||
Verified Versions: | Category: | --- | |||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
Embargoed: | |||||||||||||||
Attachments: |
|
Description
Adam Stein
2012-08-15 19:16:06 UTC
Created attachment 604669 [details]
File: core_backtrace
Created attachment 604670 [details]
File: environ
Created attachment 604671 [details]
File: backtrace
Created attachment 604672 [details]
File: maps
Created attachment 604673 [details]
File: dso_list
Hi Adam, thanks for the report. Do you still see this problem? I'm not able to reproduce it.. What kind of notifications with alarms do you have in palm? How long before the event is alarm set? Or if you can think of some other useful information how to reproduce this, just let me know.. Thanks, peter Sorry I didn't get back sooner. I need to test this at home and I keep forgetting. I did at least want you to know I received your message. I need to test at home because, for some reason, when I upgraded Fedora at work, I lost the ability to connect to my Palm. At work, I'm also running under VirtualBox while at home, Fedora is the boot OS, so I wanted to see if VirtualBox was somehow causing me not to be able to connect anymore. If I can't connect at home, then there's no point in continuing. I used to connect fine (jpilot, pilot-sync). Doesn't work anymore (even thought the setup hasn't changed and I can see the device when I run 'lsusb' after the hotsync button is pressed). As for alarms, I have the typical 15 minutes before appointment alarms. Nothing else. Hopefully, I will get to trying to connect at home to see if VirtualBox is affecting it somehow. That's OK Adam. When running under VirtualBox, you might need to add USB filter with Palm device in the USB section of virtual machine settings. This works for me under Fedora 17. peter I do have the USB filter so that the Palm passes thru to Fedora. At some point, I just couldn't connect to the device anymore (could be the device itself I guess). Running 'lsusb' does show the device, so I know Fedora under VirtualBox knows it's there. You might as well close this. I can't connect at home either. Not with JPilot, not with pilot-link. Syncing with the Palm was nice while it lasted. I am sorry to hear that Adam. Feel free to reopen if something changes. |