Evolution crashed on takeoff this morning. I tried to report the bug with ABRT, and was surprised when it automatically contacted the retrace server without asking me what to do first. I've already got huge piles of debuginfo packages installed, so it would probably have been fine to generate the backtrace locally. Well, okay, I'll watch the retrace server run: --- Running report_uReport --- (exited with 0) --- Running analyze_RetraceServer --- Querying server settings Preparing an archive to upload Uploading 722960 bytes Upload successful Retrace job started Initializing virtual root Initializing virtual root Initializing virtual root Initializing virtual root Initializing virtual root Initializing virtual root Initializing virtual root Retrace job failed Retrace failed. Try again later and if the problem persists report this issue please. Analyzing crash data OK Initializing virtual root Error 25: === OUTPUT === INFO: mock.py version 1.1.18 starting... State Changed: init plugins INFO: selinux enabled State Changed: start State Changed: lock buildroot State Changed: clean State Changed: unlock buildroot State Changed: init State Changed: lock buildroot Mock Version: 1.1.18 INFO: Mock Version: 1.1.18 INFO: calling preinit hooks State Changed: running yum ERROR: Command failed: # ['/usr/bin/yum', '--installroot', '/var/lib/mock/154164959/root/', '--skip-broken', 'install', 'evolution-3.4.4-1.fc17', 'GConf2-debuginfo-3.2.5-1.fc17.x86_64', 'PackageKit-debuginfo-0.7.5-1.fc17.x86_64', 'PackageKit-gtk3-module-0.7.5-1.fc17.x86_64', 'adwaita-gtk3-theme-3.4.2-1.fc17.x86_64', 'atk-debuginfo-2.4.0-1.fc17.x86_64', 'cairo-debuginfo-1.10.2-7.fc17.x86_64', 'cyrus-sasl-debuginfo-2.1.23-31.fc17.x86_64', 'db4-debuginfo-4.8.30-10.fc17.x86_64', '1:dbus-debuginfo-1.4.10-4.fc17.x86_64', 'dbus-glib-debuginfo-0.98-2.fc17.x86_64', '1:dbus-libs-1.4.10-4.fc17.x86_64', 'dconf-0.12.1-1.fc17.x86_64', 'dconf-debuginfo-0.12.1-1.fc17.x86_64', 'e2fsprogs-debuginfo-1.42.3-2.fc17.x86_64', '1:enchant-debuginfo-1.6.0-4.fc17.x86_64', 'evolution-3.4.4-1.fc17.x86_64', 'evolution-NetworkManager-3.4.4-1.fc17.x86_64', 'evolution-bogofilter-3.4.4-1.fc17.x86_64', 'evolution-data-server-debuginfo-3.4.4-2.fc17.x86_64', 'evolution-debuginfo-3.4.4-1.fc17.x86_64', 'evolution-devel-3.4.4-1.fc17.x86_64', 'evolution-perl-3.4.4-1.fc17.x86_64', 'evolution-pst-3.4.4-1.fc17.x86_64', 'evolution-spamassassin-3.4.4-1.fc17.x86_64', 'expat-2.1.0-1.fc17.x86_64', 'expat-debuginfo-2.1.0-1.fc17.x86_64', 'fontconfig-debuginfo-2.8.0-7.fc17.x86_64', 'freetype-debuginfo-2.4.8-3.fc17.x86_64', 'gcc-base-debuginfo-4.7.0-5.fc17.x86_64', 'gdk-pixbuf2-debuginfo-2.26.1-1.fc17.x86_64', 'glib2-debuginfo-2.32.4-1.fc17.x86_64', 'glibc-2.15-56.fc17.x86_64', 'glibc-debuginfo-2.15-56.fc17.x86_64', 'desktop-backgrounds-gnome', 'gnome-desktop3-debuginfo-3.4.2-1.fc17.x86_64', 'desktop-backgrounds-gnome', 'gnome-themes-standard-debuginfo-3.4.2-1.fc17.x86_64', 'gtk3-debuginfo-3.4.4-1.fc17.x86_64', 'gtkhtml3-debuginfo-4.4.4-1.fc17.x86_64', 'gvfs-1.12.3-1.fc17.x86_64', 'gvfs-debuginfo-1.12.3-1.fc17.x86_64', 'keyutils-debuginfo-1.5.5-2.fc17.x86_64', 'keyutils-libs-1.5.5-2.fc17.x86_64', 'krb5-debuginfo-1.10.2-6.fc17.x86_64', 'krb5-libs-1.10.2-6.fc17.x86_64', 'libICE-debuginfo-1.0.8-1.fc17.x86_64', 'libSM-debuginfo-1.2.1-1.fc17.x86_64', 'libX11-debuginfo-1.5.0-2.fc17.x86_64', 'libXau-debuginfo-1.0.6-3.fc17.x86_64', 'libXcomposite-debuginfo-0.4.3-3.fc17.x86_64', 'libXcursor-debuginfo-1.1.13-1.fc17.x86_64', 'libXdamage-debuginfo-1.1.3-3.fc17.x86_64', 'libXext-debuginfo-1.3.1-1.fc17.x86_64', 'libXfixes-debuginfo-5.0-2.fc17.x86_64', 'libXi-debuginfo-1.6.1-1.fc17.x86_64', 'libXinerama-debuginfo-1.1.2-1.fc17.x86_64', 'libXrandr-debuginfo-1.3.1-3.fc17.x86_64', 'libXrender-0.9.7-1.fc17.x86_64', 'libXrender-debuginfo-0.9.7-1.fc17.x86_64', 'libbluray-debuginfo-0.2.2-1.fc17.x86_64', 'libcanberra-debuginfo-0.28-6.fc17.x86_64', 'libcanberra-gtk3-0.28-6.fc17.x86_64', 'libcom_err-1.42.3-2.fc17.x86_64', 'libcroco-debuginfo-0.6.5-1.fc17.x86_64', 'libffi-debuginfo-3.0.10-2.fc17.x86_64', 'libgcc-4.7.0-5.fc17.x86_64', 'libgcrypt-1.5.0-3.fc17.x86_64', 'libgcrypt-debuginfo-1.5.0-3.fc17.x86_64', 'libgnome-keyring-debuginfo-3.4.1-2.fc17.x86_64', 'libgpg-error-1.10-2.fc17.x86_64', 'libgpg-error-debuginfo-1.10-2.fc17.x86_64', 'libical-debuginfo-0.48-2.fc17.x86_64', '2:libogg-debuginfo-1.3.0-1.fc17.x86_64', '2:libpng-debuginfo-1.5.10-1.fc17.x86_64', 'librsvg2-debuginfo-2.36.1-1.fc17.x86_64', 'libselinux-debuginfo-2.1.10-3.fc17.x86_64', 'libsoup-debuginfo-2.38.1-3.fc17.x86_64', 'libtdb-debuginfo-1.2.10-15.fc17.x86_64', 'libtool-debuginfo-2.4.2-3.fc17.x86_64', '1:libvorbis-debuginfo-1.3.3-1.fc17.x86_64', 'libxcb-debuginfo-1.8.1-1.fc17.x86_64', 'libxml2-debuginfo-2.7.8-7.fc17.x86_64', 'nspr-debuginfo-4.9.1-2.fc17.x86_64', 'nss-debuginfo-3.13.5-1.fc17.x86_64', 'nss-softokn-debuginfo-3.13.5-1.fc17.x86_64', 'nss-util-debuginfo-3.13.5-1.fc17.x86_64', '1:openssl-1.0.0j-2.fc17.x86_64', '1:openssl-debuginfo-1.0.0j-2.fc17.x86_64', 'pango-debuginfo-1.30.0-1.fc17.x86_64', 'pixman-0.24.4-2.fc17.x86_64', 'pixman-debuginfo-0.24.4-2.fc17.x86_64', 'sqlite-debuginfo-3.7.11-3.fc17.x86_64', 'util-linux-debuginfo-2.21.2-2.fc17.x86_64', 'zlib-1.2.5-7.fc17.x86_64', 'zlib-debuginfo-1.2.5-7.fc17.x86_64', 'shadow-utils', 'gdb', 'rpm', '--setopt=tsflags=nocontexts'] Error: Protected multilib versions: PackageKit-glib-0.7.5-1.fc17.i686 != PackageKit-glib-0.7.6-1.fc17.x86_64 You could try running: rpm -Va --nofiles --nodigest Error: Protected multilib versions: PackageKit-0.7.5-1.fc17.i686 != PackageKit-0.7.6-1.fc17.x86_64 (exited with 1) This appears to be https://bugzilla.redhat.com/show_bug.cgi?id=855731. I've got a few complaints about this. First, why is the update server looking at PackageKit-0.7.6-1, which is in -updates-testing, when I have no packages from -updates-testing installed on my machine? Second, a remote action was initiated without any permission from me, even though a local action would have worked just as well (and, in this case, better). Third, even after the retrace server failed to do its job, ABRT still isn't giving me any option to process the backtrace locally. I used to have that option, so this is a user-visible change to an important desktop component in a stable release, in violation of https://fedoraproject.org/wiki/Updates_Policy#Stable_Releases. Why was this allowed? -- Jerry James http://www.jamezone.org/ -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
