abrt 1.1.0 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/libexec/syncevo-dbus-server component: syncevolution crash_function: dbus_error_is_set executable: /usr/libexec/syncevo-dbus-server global_uuid: 05ba06bc969192359840271ef61ec91c95346d1c kernel: 2.6.33.3-85.fc13.x86_64 package: syncevolution-1.0beta3-1.fc13 rating: 4 reason: Process /usr/libexec/syncevo-dbus-server was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) How to reproduce: Execute syncevolution and wait
Created attachment 413648 [details] File: backtrace
Package: syncevolution-1.0beta3-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- run syncevo-dbus-server
Package: syncevolution-1.0beta3-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Plug in my iPhone. 2. 3.
Package: syncevolution-1.0beta3-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Booted 2. Plugged in my iPhone 3.
*** Bug 591417 has been marked as a duplicate of this bug. ***
*** Bug 597745 has been marked as a duplicate of this bug. ***
*** Bug 597881 has been marked as a duplicate of this bug. ***
*** Bug 598030 has been marked as a duplicate of this bug. ***
Package: syncevolution-1.0beta3-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- Crashes immediately at startup
Package: syncevolution-1.0beta3-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- Crashes at startup
*** Bug 599321 has been marked as a duplicate of this bug. ***
Package: syncevolution-1.0beta3-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- login and wait or execute /usr/libexec/syncevo-dbus-server
Package: syncevolution-1.0beta3-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) Comment ----- I did nothing that I am aware of that generated this error. Was in the process of installing the entire Yum Fedora respository on system.
syncevolution-1.0-2.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/syncevolution-1.0-2.fc13
Running the new syncevolution I get: fm@thinkpad:~ # gdb /usr/libexec/syncevo-dbus-server GNU gdb (GDB) Fedora (7.1-26.fc13) Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/libexec/syncevo-dbus-server...Reading symbols from /usr/lib/debug/usr/libexec/syncevo-dbus-server.debug...done. done. (gdb) r Starting program: /usr/libexec/syncevo-dbus-server [Thread debugging using libthread_db enabled] Program received signal SIGSEGV, Segmentation fault. dbus_error_is_set (error=0x1) at dbus-errors.c:330 330 return error->name != NULL; Missing separate debuginfos, use: debuginfo-install GConf2-2.28.1-1.fc13.i686 ORBit2-2.14.18-1.fc13.i686 atk-1.30.0-1.fc13.i686 cairo-1.8.10-1.fc13.i686 cppunit-1.12.1-3.fc12.i686 cyrus-sasl-lib-2.1.23-11.fc13.i686 dbus-glib-0.84-3.fc13.i686 evolution-data-server-2.30.1-3.fc13.i686 expat-2.0.1-10.fc13.i686 fontconfig-2.8.0-1.fc13.i686 freetype-2.3.11-3.fc13.i686 gnutls-2.8.6-2.fc13.i686 gtk2-2.20.1-1.fc13.i686 keyutils-libs-1.2-6.fc12.i686 krb5-libs-1.7.1-10.fc13.i686 libX11-1.3.1-3.fc13.i686 libXau-1.0.5-1.fc12.i686 libXcomposite-0.4.1-2.fc13.i686 libXcursor-1.1.10-4.fc13.i686 libXdamage-1.1.2-2.fc13.i686 libXext-1.1-2.fc13.i686 libXfixes-4.0.4-2.fc13.i686 libXi-1.3-2.fc13.i686 libXinerama-1.1-2.fc13.i686 libXrandr-1.3.0-5.fc13.i686 libXrender-0.9.5-1.fc13.i686 libcom_err-1.41.10-6.fc13.i686 libgcrypt-1.4.5-4.fc13.i686 libgnome-keyring-2.30.1-1.fc13.i686 libgpg-error-1.7-1.fc13.i686 libical-0.43-5.fc12.i686 libnotify-0.4.5-4.fc13.i686 libproxy-0.3.1-4.fc13.i686 libselinux-2.0.90-5.fc13.i686 libsoup-2.30.1-1.fc13.i686 libtasn1-2.4-2.fc13.i686 libxcb-1.5-1.fc13.i686 libxml2-2.7.7-1.fc13.i686 nspr-4.8.4-2.fc13.i686 nss-3.12.6-7.fc13.i686 nss-softokn-freebl-3.12.6-3.fc13.i686 nss-util-3.12.6-1.fc13.i686 openssl-1.0.0a-1.fc13.i686 pango-1.28.0-1.fc13.i686 pcre-7.8-3.fc12.i686 pixman-0.18.0-1.fc13.i686 sqlite-3.6.22-1.fc13.i686 (gdb) bt #0 dbus_error_is_set (error=0x1) at dbus-errors.c:330 #1 0x00969ff6 in internal_bus_get (type=DBUS_BUS_SESSION, private=0, error=0x1) at dbus-bus.c:435 #2 0x00a9169d in g_dbus_setup_bus (type=DBUS_BUS_SESSION, name=0x80c0c91 "org.syncevolution", error=0x1) at mainloop.c:458 #3 0x0809d739 in main (argc=1, argv=0xbffff3e4) at syncevo-dbus-server.cpp:5869 fm@thinkpad:~ # rpm -qa syncev* syncevolution-debuginfo-1.0-2.fc13.i686 syncevolution-libs-1.0-2.fc13.i686 syncevolution-gtk-1.0-2.fc13.i686 syncevolution-perl-1.0-2.fc13.i686 syncevolution-1.0-2.fc13.i686
Package: syncevolution-1.0beta3-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. started evolution 2. cklicked on calendar 3. waited 2 minutes
syncevolution-1.0-2.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update syncevolution'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/syncevolution-1.0-2.fc13
The problem persists in syncevolution-1.0-2.fc13 from testing repository... The bug is still open..
I am still having the same problems. 'syncevolution --template ?' fails, as does 'syncevolution --help'
syncevolution-1.0-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
Do you even read the comments on this bug? The update did NOT fix the problem...
(In reply to comment #22) > Do you even read the comments on this bug? The update did NOT fix the > problem... Yes actually I do. But the way the fedora build system work it closes it off. Its now being tracked against the new bug report against the new version. Do you even read the fedora documentation.