Hi I am relatively new to Fedora and to YUM...so I guess that's why I am having these problems
I noticed recently that 18 wasn't updating very often..there was little being updated so I went through the repository list in /etc/yum.repos.d and enabled some rawhide repositories that were disabled. Now when I yum check-update and yum update...I get a bunch of dependency errors because yum is trying to pull in fedora 19 files ?? I sort it out by running yum --skip-broken update....but I'd like to fix what I messed up .
These are the repos.
/etc/yum.repos.d/adobe-linux-i386.repo /etc/yum.repos.d/fedora.repo /etc/yum.repos.d/fedora-updates.repo /etc/yum.repos.d/fedora-updates-testing.repo /etc/yum.repos.d/google-chrome.repo /etc/yum.repos.d/rpmfusion-free-rawhide.repo /etc/yum.repos.d/rpmfusion-free.repo /etc/yum.repos.d/rpmfusion-free-updates.repo /etc/yum.repos.d/rpmfusion-free-updates-testing.repo /etc/yum.repos.d/rpmfusion-nonfree-rawhide.repo /etc/yum.repos.d/rpmfusion-nonfree.repo /etc/yum.repos.d/rpmfusion-nonfree-updates.repo /etc/yum.repos.d/rpmfusion-nonfree-updates-testing.repo
These are the defaults that 18 put in place...but some had been disabled...
Can anyone help ?
Thanks
On 01/09/2013 05:38 PM, FMcCormick wrote:
Hi I am relatively new to Fedora and to YUM...so I guess that's why I am having these problems
welcome to a whole new world.
I noticed recently that 18 wasn't updating very often..there was little being updated so I went through the repository list in /etc/yum.repos.d and enabled some rawhide repositories that were disabled.
rawhide is cause of your problems.
Now when I yum check-update and yum update...I get a bunch of dependency errors because yum is trying to pull in fedora 19 files ?? I sort it out by running yum --skip-broken update....but I'd like to fix what I messed up .
very easy. remove rawhide repos.
reasons being;
long and exact -- http://fedoraproject.org/wiki/Releases/Rawhide
short and simple -- https://en.wikipedia.org/wiki/Rawhide_%28computing%29
it would be nice if you were backed up to before you enabled rawhide. then you could restore and continue along with out rawhide.
because you are new to linux and fedora, i would suggest a complete wipe of hdd and fresh new install of f18.
i know you do do not want to hear such, but it will ensure that you have a *clean* system to work with. besides, it will give you practice of installing fedora. i am sure that with oos, you had plenty of practice of installing an os.
another thing to consider, and that is learning to make backup.
by doing a fresh install, you can configure and customize it, back it up and you will have a *customized backup* handy if you need it again. also, as you add to your custom system, you can make periodic back ups of newly installed software and configs so that you can restore to what ever state you desire.
much luck.
hth.
On Wed, 09 Jan 2013 18:51:03 +0000 g geleem@bellsouth.net wrote:
On 01/09/2013 05:38 PM, FMcCormick wrote:
Hi I am relatively new to Fedora and to YUM...so I guess that's why I am having these problems
welcome to a whole new world.
Thanks....sure is different :)
I noticed recently that 18 wasn't updating very often..there was little being updated so I went through the repository list in /etc/yum.repos.d and enabled some rawhide repositories that were disabled.
rawhide is cause of your problems.
Now when I yum check-update and yum update...I get a bunch of dependency errors because yum is trying to pull in fedora 19 files ?? I sort it out by running yum --skip-broken update....but I'd like to fix what I messed up .
very easy. remove rawhide repos.
Done....BUT I dunno whether I am going to reinstall right now...I have done a lot of customization....we'll see how it goes and whether and how much it's messed up :)
because you are new to linux and fedora, i would suggest a complete wipe of hdd and fresh new install of f18.
Now new to Linux (8 years) but definitely new to Fedora (17 & 18)....takes some getting used to.
much luck.
Thanks...I may need it.
On Wed, Jan 09, 2013 at 16:10:36 -0500, FMcCormick beacon@videotron.ca wrote:
Done....BUT I dunno whether I am going to reinstall right now...I have done a lot of customization....we'll see how it goes and whether and how much it's messed up :)
After you disable the rawhide repos you can get back to f18 by using: yum --releasever=18 distro-sync
Not every package can downgrade cleanly, but most likely this will work better than having a mix of f18 and rawhide packages while not actually using the rawhide repos.
On Wed, 09 Jan 2013 16:37:02 -0600 Bruno Wolff III bruno@wolff.to wrote:
On Wed, Jan 09, 2013 at 16:10:36 -0500, FMcCormick beacon@videotron.ca wrote:
Done....BUT I dunno whether I am going to reinstall right now...I have done a lot of customization....we'll see how it goes and whether and how much it's messed up :)
After you disable the rawhide repos you can get back to f18 by using: yum --releasever=18 distro-sync
Well I had already undone the last few transactions...which erased a lot of packages and apparently downgraded others.
But I figured at this stage...why not ? So I ran your YUM command..the first time it segfaulted ??? But the second time it installed a few new packages and downgraded a bunch others....
But I still have this problem :
[frank@localhost ~]$ gthumb
** (gthumb:2439): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(gthumb:2439): Gdk-ERROR **: The program 'gthumb' received an X Window System error. This probably reflects a bug in the program. The error was 'GLXBadContext'. (Details: serial 143 error_code 167 request_code 152 minor_code 6) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trace/breakpoint trap (core dumped) [frank@localhost ~]$
Gthumb depends on so much it's hard to figure out what is/was going wrong.
Not every package can downgrade cleanly, but most likely this will work better than having a mix of f18 and rawhide packages while not actually using the rawhide repos.
Well....we'll see :)
On 01/10/2013 04:50 AM, FMcCormick wrote: <>
i do not use 'gthumb' because i use 'kde'. i have used 'thumbnail' a couple times to create some thumbnail images.
as for your errors, have you tried an search engines to find a solution?
if you do not get any positive help posting and waiting here, check links under each of your warning and error.
** (gthumb:2439): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
https://duckduckgo.com/?q=%22Couldn%27t+register+with+accessibility+bus%3A+D...
(gthumb:2439): Gdk-ERROR **: The program 'gthumb' received an X Window System error. This probably reflects a bug in the program. The error was 'GLXBadContext'. (Details: serial 143 error_code 167 request_code 152 minor_code 6) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trace/breakpoint trap (core dumped)
https://duckduckgo.com/?q=GLXBadContext
Gthumb depends on so much it's hard to figure out what is/was going wrong.
that is why you should *first* run problem thru a search engine *before* you post to a tsl.
hth.
On 12/01/13 09:20 PM, g wrote:
On 01/10/2013 04:50 AM, FMcCormick wrote: <>
i do not use 'gthumb' because i use 'kde'. i have used 'thumbnail' a couple times to create some thumbnail images.
as for your errors, have you tried an search engines to find a solution?
if you do not get any positive help posting and waiting here, check links under each of your warning and error.
** (gthumb:2439): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
https://duckduckgo.com/?q=%22Couldn%27t+register+with+accessibility+bus%3A+D...
(gthumb:2439): Gdk-ERROR **: The program 'gthumb' received an X Window System error. This probably reflects a bug in the program. The error was 'GLXBadContext'. (Details: serial 143 error_code 167 request_code 152 minor_code 6) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trace/breakpoint trap (core dumped)
https://duckduckgo.com/?q=GLXBadContext
Gthumb depends on so much it's hard to figure out what is/was going wrong.
that is why you should *first* run problem thru a search engine *before* you post to a tsl.
Actually, none of those links were any good to me for a simple reason.
The problem started when I ended up running a mixed system of 18 and rawhide because of some stupid moves on my part. I had managed to undo most of the damage (yum history undo is invaluble) but gthumb kept giving me those errors. I never did pin down the exact cause but decided after spending a few hours working on it to just reinstall 18. The most painful part was updating 18 as the install disk was from last fall !!
BTW I usually google errors before posting to a list.
On 01/13/2013 02:34 AM, Frank McCormick wrote: <>
I never did pin down the exact cause but decided after spending a few hours working on it to just reinstall 18.
now that sounds familiar. :)
it used to be a difficult decision for me to make. after a few years, i have found that if i can not get a new install working within an hour of installation from disk, then i 'byte the bullet' and reinstall.
The most painful part was updating 18 as the install disk was from last fall !!
actually, finding f18 on fedora site would be more painful. you can find the 'fedora-18-alpha' and 'fedora-18-beta' very easy, but 'fedora-18' takes a little bit of brain work to get because it is not linked. at least not that i have found.
BTW I usually google errors before posting to a list.
you had not mentioned, so i was not aware. pfm.
-
Bruno Wolff III -
Frank McCormick -
g