Bug 491789 - I can't Update Fedora Core 11 via command line or GUI
I can't Update Fedora Core 11 via command line or GUI
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: ucarp (Show other bugs)
rawhide
x86_64 Linux
low Severity high
: ---
: ---
Assigned To: Matthias Saou
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-03-23 23:45 EDT by Dale_G
Modified: 2009-03-24 02:12 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-03-24 02:12:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Dale_G 2009-03-23 23:45:23 EDT
Description of problem: Can update Fedora Core 11


Version-Release number of selected component (if applicable): 2.6.29-0.66.rc3.fc11.x86_64 #1 SMP Thu Jan 29 14:44:32 EST 2009 x86_64 x86_64 x86_64 GNU/Linux


How reproducible: 5 or 5


Steps to Reproduce: 
1. Download Fedora Core 11
2. Install Fedora Core 11
3. Select System/Administration/Update System
4. Click on Update System

Steps to Reproduce 3a
3a. From a terminal window enter yum upgrade
result 
[rig@Dales-Test-Kahuna ~]$ yum upgrade
Loaded plugins: dellsysidplugin2, refresh-packagekit
Segmentation fault

  
Actual results: nothing from GUI


Expected results: the System updates


Additional info: unlike windows...  Fedora Core can only run at spec cpu speed ... meaning Linus has a problem with overclocking... OK background. I  know linux and all the cores....not one Fedora Package allows me to over clock my cpu....OpenSolaris works   ..  What I'm saying is why Fedora only works works when I run at 2G.... Open Solaris/Windows will run at 2.8G plus and Windows  so what is up with that ??? AMD Opteron and yes I'm running at 64 bit

Dale G
Comment 1 Ask Bjørn Hansen 2009-03-24 02:12:37 EDT
This doesn't have anything to do with the `ucarp` package.

Besides, it sounds like you have a hardware problem.  Intel/AMD rated your CPU at 2GHz for a reason.

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