Okay so I successfully got into recovery mode, used "yum erase compiz" and it deleted all of the compiz CSSM stuff. Rebooted, it loads, shows the launch screen with the underwater scene, then immediately goes back to saying "Oh noes, you ****ed up" screen.
I am 100% sure that compiz CSSM did this since it happened the second I installed and launched it, but now that it has been deleted and is still not working, what other recourse do I have?
Edit: Yah I was wondering why there is no code tags on snuson. Not that most would use it but every forum should have code tags, especially considering that we have on more than one occasion discussed python or linux or other things that could benefit from code tags.
You would remove the packages that it lists. Ideally, if you remember the name of the package you installed, you can just use that. Making up a name, say you installed compiz with 'yum install compiz-core,' you would then use 'yum erase compiz-core' to get rid of it. And I'd agree with lx, take your time. When you get things working again, sit out on compiz, it's really just eye candy that doesn't offer any must have functions you can't do somehow else.
Also, lx, does snuson support code tags? If so, might be useful in this thread later, if ever we need him to paste logs or command output.
I believe mutter is the default compositing manager for Gnome3, and that would replace the compiz you used. Getting rid of compiz should work also.
Before you get crazy tweaking out your setup, live with it for a little while, and customize a bit at a time. Recognize a need, and fulfill it, rather than create the need if you get what I'm saying.
Well, since it happened immediately after you install and ran compiz, I'd say try going into single-user mode or rescue mode, whatever they're calling it, and removing compiz. You can run 'rpm -qa | grep compiz' to see what compiz packages you have. Remove them with yum erase packagename. Also, in single user mode you'll have root privileges by default, so you don't need to use sudo. You'll be in a text only environment, and you can scroll by either using pgup/pgdn or shift+ those two, I forget which. Before you hit y to confirm the removal, make sure to look at what it says will get removed. If it tries to remove gnome or something else that you need, make sure to reinstall it before rebooting, thought it really shouldn't. After that runs, try rebooting and see if it's resolved. If you can boot, then compiz is just going to be a no-go for you for the time being.
Well, since it happened immediately after you install and ran compiz, I'd say try going into single-user mode or rescue mode, whatever they're calling it, and removing compiz. You can run 'rpm -qa | grep compiz' to see what compiz packages you have. Remove them with yum erase packagename. Also, in single user mode you'll have root privileges by default, so you don't need to use sudo. You'll be in a text only environment, and you can scroll by either using pgup/pgdn or shift+ those two, I forget which. Before you hit y to confirm the removal, make sure to look at what it says will get removed. If it tries to remove gnome or something else that you need, make sure to reinstall it before rebooting, thought it really shouldn't. After that runs, try rebooting and see if it's resolved. If you can boot, then compiz is just going to be a no-go for you for the time being.
Also, you may want to edit your post on fedora forums to reflect that it's simple CCSM. Really shouldn't have screwed things up the way you described, though. Who knows. Also, grab another computer if you can, fire up IRC, and connect to irc.freenode.net Register your nick (you'll need to register it to get into the channel), and join #fedora. That's the official fedora support channel. They'll help you out, although I warn you that if they link you to instructions and you say it's too technical and looks like Arabic, they may not be too keen on expending further efforts helping you. Those guys are generally pretty knowledgeable, though, and they've helped me out a fair number of times in the past.
How do I get to a command prompt? It won't even load Fedora. And what does mutter --replace do? I will try going in recovery mode and testing it out but what should I be looking for after I enter this command?
I used to use a dual boot system years ago. There were several chat rooms on IRC with Linux nuts and I could usually go there for help. I don't remember any rooms in particular but they are not hard to find. I ended up taking the approach that if I needed a manual to do a simple task, I won't use it. It is fun to play around with though. Maybe I will convert my current computer when I get a new one.
I wouldn't trust geeksquad to fix my blender, let alone anything Linux related lol. But I may have to if I can't figure out how to do it. I havn't tried loading it in safe mode yet because if I did I wouldn't know where to begin looking or what may be causing the problems. I thought maybe it was a graphics card issue since I had the weird thing happen with my screen but I did install the ATI drivers successfully so don't know what else to do.
I installed Compiz Fusion simple-CSSM, went to open it and the screen scrambled. Now Whenever I start my computer it just says "Oh no, something has gone wrong, contact a sys admin".
I installed Compiz Fusion simple-CSSM, went to open it and the screen scrambled. Now Whenever I start my computer it just says "Oh no, something has gone wrong, contact a sys admin".
I don't know about with gnome-terminal, but if you install sakura, there's a config file in ~/.config/sakura/sakura.conf. You can edit that by opening it with nano ~/.config/sakura/sakura.conf. If you install urxvt (yum install rxvt-unicode), you can change the settings via a file called ~/.Xresources. If you feel like being particularly lazy, you can just steal my config from here.
You can just take the the .Xresources file and put it in your home directory, or you can clone it all with git and have all my config files in a directory called Config, and move .Xresources elsewhere. If you use that, after you put .Xresources in your home folder and you've installed rxvt-unicode, run xrdb -merge .Xresources, and you'll be using my config. You'll want to change line five from /home/Shiki/urxvt-to-uzbl to just 'firefox'. This page will give you examples of some of the other things you can customize, and you'll just have to look of the hex values for the colours you want. At the moment, it's set to be transparent. You can make new tabs in urxvt by pressing ctrl+shift+↓, close tabs with ctrl+d.
That tutorial will take care of all the basic stuff. I've never seen the need to bother with something like autoplus. For pasting, click on the terminal window so that you know it's active, and press the middle mouse button/scroll wheel if you have one. If not, shift+insert will work. the insert key will be around your print screen key and stuff. As the /etc/yum.repos.d/ that's probably just bad writing on his part. There won't be a google.repo file there by default. He meant make the file first, and put that in there. You can make the file by type sudo nano /etc/yum.repos.d/google.repo. Also at some point you make want to try playing around with vi/vim for a CLI text editor. It can be more powerful than nano, and vi is helpful to know because prety much no matter what linux distro you use in the future, some form of vi or vim will be included by default. For vim, press 'i' to enter insert mode, type what you want, and hit escape to exit insert mode. Navigation is done with hjkl, and you can exit a file after you're out of insert mode by type :q. To save what you changed and exit, type :wq. For now, nano will suffice to get you up and running quickly, but installing vim can let you play around with it a little bit later on.
Oh, also, install screen. Screen is an amazing program. With screen, you can run any number of terminal program in one window/tab, rather than having to have a separate tab or window open for each.
Yah I figured I had to make the file but it said I didn't have privaledges. It then dawned on me that I would have to create it from within the terminal but I don't know the required code to create a new file in that folder. I will try again now.
Also, is there any way to change the color scheme? For example I want the terminal window to be grey with white letteringinstead of white with black lettering. In the system settings I see the option to change the background but not the color scheme. Is this something that needs to be done in the terminal?
That tutorial will take care of all the basic stuff. I've never seen the need to bother with something like autoplus. For pasting, click on the terminal window so that you know it's active, and press the middle mouse button/scroll wheel if you have one. If not, shift+insert will work. the insert key will be around your print screen key and stuff. As the /etc/yum.repos.d/ that's probably just bad writing on his part. There won't be a google.repo file there by default. He meant make the file first, and put that in there. You can make the file by type sudo nano /etc/yum.repos.d/google.repo. Also at some point you make want to try playing around with vi/vim for a CLI text editor. It can be more powerful than nano, and vi is helpful to know because prety much no matter what linux distro you use in the future, some form of vi or vim will be included by default. For vim, press 'i' to enter insert mode, type what you want, and hit escape to exit insert mode. Navigation is done with hjkl, and you can exit a file after you're out of insert mode by type :q. To save what you changed and exit, type :wq. For now, nano will suffice to get you up and running quickly, but installing vim can let you play around with it a little bit later on.
Oh, also, install screen. Screen is an amazing program. With screen, you can run any number of terminal program in one window/tab, rather than having to have a separate tab or window open for each.
Id just thought Id share a story of my computer journey last night. When I first got my desktop it was a display at the store with windows vista. After...
I'll admit, this is something that's been bugging me for a long time now. I saw a clip about this family just now, who got booted off a flight because...
Leave a comment: