Bug 559970 - [abrt] crash in syncevolution-gtk-0.9.2-1.fc12
Summary: [abrt] crash in syncevolution-gtk-0.9.2-1.fc12
Keywords:
Status: CLOSED DUPLICATE of bug 559345
Alias: None
Product: Fedora
Classification: Fedora
Component: syncevolution
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f9eae3196ab7d5c25de112b0701...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-29 14:17 UTC by Patrick C. F. Ernzer
Modified: 2010-01-30 00:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-30 00:13:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (11.03 KB, text/plain)
2010-01-29 14:17 UTC, Patrick C. F. Ernzer
no flags Details

Description Patrick C. F. Ernzer 2010-01-29 14:17:34 UTC
abrt 1.0.4 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: sync-ui-gtk
component: syncevolution
executable: /usr/bin/sync-ui-gtk
kernel: 2.6.31.12-174.2.3.fc12.x86_64
package: syncevolution-gtk-0.9.2-1.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. configure syncevolution for use with an in-house funambol server
2. use it happily from the command line
3. try to use the GTK gui, now that bug 538127 is fixed
4. ** (sync-ui-gtk:12846): WARNING **: Server configuration has suspect URL ''
5. quit the GUI, delete ~/.config/syncevolution
6. start the GUI, configure funambol server again
7. click apply and use (at this point the server was not reachable, but that should not matter)
8. GTK gui crashes and from then on crashes at each launch. (the backtrace is from one of these subsequent launches(

Comment 1 Patrick C. F. Ernzer 2010-01-29 14:17:37 UTC
Created attachment 387574 [details]
File: backtrace

Comment 2 Peter Robinson 2010-01-30 00:13:10 UTC

*** This bug has been marked as a duplicate of bug 559345 ***


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