Bug 753377

Summary: caribou prerequisite missing after upgrade
Product: [Fedora] Fedora Reporter: Stefan Seefeld <stefan>
Component: caribouAssignee: Parag Nemade <pnemade>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 16CC: pnemade
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-14 05:50:27 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:

Description Stefan Seefeld 2011-11-12 03:33:50 UTC
I just upgraded from Fedora 15 to Fedora 16, using the preupgrade tool. After the upgrade was complete the system rebooted. Right after starting gdm, an error screen appeared telling me something had gone wrong...

Reading the message logs I noticed some error messages related to a "caribou" component. Googling around for the specific error I saw got me to https://bugs.archlinux.org/task/26212. `yum install caribou` bailed out with an error, because caribou.i686 was already installed but caribou.x86_64 couldn't be installed due to file conflicts (with the i686 version).

I then uninstalled caribou.i686 and reinstalled caribou.x86_64. After that point and an 'init 3; init 5' the gdm startup completed and I was able to log in.

Thus I think there are really two problems here:

1) Some packaging error yields conflicts when attempting to install both 32-bit and 64-bit versions of the caribou package.

2) The caribou.x86_64 package should have been installed, not caribou.i686

Oh, and as the other bug report (https://bugs.archlinux.org/task/26212) noted, there is no point in dragging in a dependency on a touchscreen support library for a desktop system. This may be an optional add-on at best. :-)

Thanks,
         Stefan

Comment 1 Parag Nemade 2011-11-14 05:50:27 UTC
Let's discuss this in a single bug 753149

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