Red Hat Bugzilla – Full Text Bug Listing
|Product:||[Fedora] Fedora||Reporter:||Arthur Kriewald <akriewal>|
|Component:||yumex||Assignee:||Tim Lauridsen <tla>|
|Status:||CLOSED NOTABUG||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2007-06-12 08:03:13 EDT||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Arthur Kriewald 2007-04-17 15:47:22 EDT
Description of problem: upon launching yumex, a Exception Occured message comes up. This happened after I compiled a new release of snort (Snort 126.96.36.199) Version-Release number of selected component (if applicable): How reproducible: Reproduce everytime. Steps to Reproduce: 1.Application Menu 2.System tools 3.Yumex Actual results: Expected results: Additional info:
Comment 1 Arthur Kriewald 2007-04-17 15:47:22 EDT
Created attachment 152849 [details] This is the crash report
Comment 2 Tim Lauridsen 2007-04-18 02:45:31 EDT
This trace generated by pirut, not yumex, but you will get the same error in yumex,yum & other tools using the yum API. It look like there is some kind of problem with sqlite. Try running the attach file with 'python test-yum.py' and paste the output
Comment 3 Tim Lauridsen 2007-04-18 02:46:34 EDT
Created attachment 152873 [details] yum test python script
Comment 4 Arthur Kriewald 2007-04-18 10:36:37 EDT
Created attachment 152910 [details] PDF containing script output This is the ouput of the test script.
Comment 5 Dawid Zamirski 2007-04-24 10:33:28 EDT
What do you get if you run the following: rpm -qa | grep -i sqlite It should show at least these two: sqlite-3.3.6-2 python-sqlite-1.1.7-1.2.1 If you have them installed already, try to remove and install again using rpm.
Comment 6 Tim Lauridsen 2007-06-12 03:11:23 EDT
Does it work now
Comment 7 Arthur Kriewald 2007-06-12 07:18:22 EDT
sorry for the delay, I thought I had already replied to this. Yes, removing and reinstalling sqlite did fix this problem. This was a test machine in a R&D environment and has since been removed, but your advice did fix my problem. thanks again for all of your advice and patience.